Defining a new vNet via GUI
Create a vNet and name it "vNet-PROD"
•
Login to Virtual Connect, if a Domain has not been created, create it now, but cancel out of the
network and profile wizards.
•
On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet
•
Ether the Network Name of "vNet-PROD"
a.
•
Select Add Port, then add the following ports;
a.
b.
•
Leave Connection Mode as Auto
•
Select Apply
Note: By connecting TWO Uplinks from this vNet we have provided a redundant path to the network. As
each uplink originates from a different VC module, one uplink will be Active and the second will be in
Standby. This configuration provides the ability to lose an uplink cable, network switch or depending on
how the NICs are configured at the server (teamed or un-teamed), even a VC module.
Note: Smart Link – In this configuration Smartlink should NOT be enabled. Smartlink is used to turn off
downlink ports within Virtual Connect, if ALL available uplinks to a vNet or SUS are down. We will use
Smartlink in a later scenario.
Defining a new vNet via CLI
The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect
# Create the vNet "vNet-PROD" and configure uplinks as discussed above
add Network vNet-PROD
add uplinkport enc0:1:1 Network=vNet-PROD speed=auto
add uplinkport enc0:2:1 Network=vNet-PROD speed=auto
set network vNet-PROD SmartLink=Disabled
Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 17
Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.)
Enclosure 1, Bay 1, Port 1
Enclosure 1, Bay 2, Port 1