Virtual connect port mapping and modification

[WFHC-WI]

Server Bay 1:
LOM NIC1 - VC bay 1, port 1
LOM NIC2 - VC bay 2, port 1
LOM NIC3 - VC bay 1, port 9
LOM NIC4 - VC bay 2, port 9

mezzanine1 HBA1 port 1 - VC bay 3, port 1
mezzanine1 HBA1 port 2 - VC bay 4, port 1

mezzanine 2 NIC 1 - VC bay 5, port 1
mezzanine 2 NIC 2 - VC bay 6, port 1
mezzanine 2 NIC 3 - VC bay 7, port 1
mezzanine 2 NIC 4 - VC bay 8, port 1

mezzanine 3 NIC 1 - VC bay 7, port 9
mezzanine 3 NIC 2 - VC bay 8, port 9

To gather port numbers for other servers, simply add the bay number minus 1 to each port value listed.
All of these port mappings are on the internal side of the virtual connect module. The external ports or uplinks are configured from the Virtual Connect Manager page. You can find specific port mappings for any server by clicking it in the Onboard Administrator page and selecting the "Port Mapping" link.

[Adrian Clint]

Uday,
Can you see how the above matches the pdf in my first post.

Also note that this has nothing to do with Virtual Connect. It would be the same with pass-thrus, Cisco, Brocode or Gbe switches as long as they are matched network/SAN in the same positions.

Also - how many NICs are you using for DMZ? If its 2 are they going to come out of Bay 7/8 or 5/6 now?
If you stack all the VCs together then you can still separate DMZs... they can even come out of different VC modules. Our config has DMZs on say NIC1 comming out of VC5.

[UK-Blr]

Yes it is almost clear.
before that, would like to know, lets say, if i configure two different vlan trunks using 2 ports from bay 5 and 6, another 2 vlan trunk using 2 ports from bay 5 and 6 (availale only 4 ports toal in each module), how the mapping will happen inside the VC to blades with above config for a bl680c.

As i need to be very clear , as this should not hinder vmware environment networking later.

[UK-Blr]

Hi,

It would be helpful, if any comments on this, as this config is good enough

[Adrian Clint]

Uday.... you are mixing up Virtual Connect network profile mapping (a configuration to connect specific server NICs to specific VC uplinks) and blade enclosure NIC mapping which links NICs to specific Virtual Connect modules.

For example your
mezzanine 2 NIC 1 - VC bay 5,
That specific NIC on any server can be configured in a profile to uplink out of any NIC on VC5 or V6 as they are stacked internally horizontally.
It cannot be configured to uplink out of VC1/2/7 or 8 if you only have stacking links between 1-7 & 2-8 as you said as the stacking link ring is 1-2-8-7-1. (You said VC 8 & 9 but I think you mean 7 & 8?)

[UK-Blr]

hope so.. would it be possible to discuss over the phone ( UK numbers)..

[UK-Blr]

.