Dell FORCE10 Open Automation Open Automation Guide - Page 46

Installing VSN, Hypervisor-unaware VLANs

Get Dell FORCE10 Open Automation PDF manuals and user guides View all Dell FORCE10 Open Automation manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

www.dell.com | support.dell.com Enter the show vlan command to display the VSN hypervisor-learned VLANs on the switch. As shown in Figure 5-2, VSN VLANs that have been automatically configured are displayed with a G tag in the left-most column and are associated with ports marked with an H tag. If a VSN VLAN has been manually configured on the switch, the VLAN has no tag; the associated ports are displayed with an H tag. Figure 5-2. Display VSN Hypervisor-learned VLANs: show vlan FTOS(conf-hypervisor)#show config ! Codes: * - Default VLAN, G - GVRP VLANs, R - Remote Port Mirroring VLANs, P - Primary, C - Community, I - Isolated Q: U - Untagged, T - Tagged x - Dot1x untagged, X - Dot1x tagged G - GVRP tagged, M - Vlan-stack, H - VSN tagged i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT tagged NUM Status Description Q Ports * 1 Active U Te 0/0,15,25,27,29,42-43 U Te 11/35-36 G 4001 Active H Te 0/35 G 4002 Active H Te 0/35 4003 Active H Te 0/35 T Te 0/15 Hypervisor-unaware VLANs VSN cannot discover VLAN configurations from a hypervisor. If an application requires a hypervisor-unaware VLAN, you must configure the VLAN manually. User-configured VLANs are not removed when VSN retrieves and updates a network configuration. Installing VSN VSN is installed as a separate Open Automation package, apart from the FTOS image and the downloaded Smart Scripting package. When you install the VSN package, VSN is loaded into FTOS. Note: VSN is not supported in stacked configurations; it is only supported on standalone switches. You install the VSN package file in the same way as you install an FTOS release: directly from local flash memory on a switch or from an external drive on a network server. Because the installation takes time, it is performed in the background. When the download is complete, a message is displayed on the console. The package installation updates the running-configuration file. You must manually configure the interfaces used to connect to hypervisors. Refer to the FTOS Configuration Guide, Interfaces chapter for information on how to configure a VLAN or physical interface. 46 | Virtual Server Networking

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
46
|
Virtual Server Networking
www.dell.com
|
support.dell.com
Enter the
show vlan
command to display the VSN hypervisor-learned VLANs on the
switch. As shown in
Figure 5-2
, VSN VLANs that have been automatically
configured are displayed with a
G
tag in the left-most column and are associated with
ports marked with an
H
tag. If a VSN VLAN has been manually configured on the
switch, the VLAN has no tag; the associated ports are displayed with an
H
tag.
Figure 5-2.
Display VSN Hypervisor-learned VLANs: show vlan
FTOS(conf-hypervisor)#show config
!
Codes: * - Default VLAN, G - GVRP VLANs, R - Remote Port Mirroring VLANs,
P - Primary, C - Community, I - Isolated
Q: U - Untagged, T - Tagged
x - Dot1x untagged, X - Dot1x tagged
G - GVRP tagged, M - Vlan-stack, H - VSN tagged
i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT
tagged
NUM
Status
Description
Q Ports
*
1
Active
U
Te 0/0,15,25,27,29,42-43
U
Te 11/35-36
G
4001
Active
H
Te 0/35
G
4002
Active
H
Te 0/35
4003
Active
H
Te 0/35
T
Te 0/15
Hypervisor-unaware VLANs
VSN cannot discover VLAN configurations from a hypervisor. If an application
requires a hypervisor-unaware VLAN, you must configure the VLAN manually.
User-configured VLANs are not removed when VSN retrieves and updates a network
configuration.
Installing VSN
VSN is installed as a separate Open Automation package, apart from the FTOS image
and the downloaded Smart Scripting package. When you install the VSN package,
VSN is loaded into FTOS.
You install the VSN package file in the same way as you install an FTOS release:
directly from local flash memory on a switch or from an external drive on a network
server. Because the installation takes time, it is performed in the background. When
the download is complete, a message is displayed on the console. The package
installation updates the running-configuration file.
You must manually configure the interfaces used to connect to hypervisors. Refer to
the
FTOS Configuration Guide,
Interfaces
chapter for information on how to
configure a VLAN or physical interface.
Note:
VSN is not supported in stacked configurations; it is only supported on
standalone switches.