HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

VLAN Capacity pre and post VC Manager v3.30

 
chuckk281
Trusted Contributor

VLAN Capacity pre and post VC Manager v3.30

Vinay was looking for some Virtual Connect VLAN info:

 

*************************

 

Is there any specific bits used in VLAN tagging that is causing these limitation Pre 3.3 and post 3.3 versions of Virtual Connect Manager 

 

  • legacy VLAN capacity mode. That mode has these limitations:
  • • 320 VLANs per Ethernet module
  • • 128 VLANs per shared uplink set
  • • 28 VLANs per server connection

 

  • Expanded VLAN capacity mode raises support limits:
  • • Up to 1000 VLANs per domain
  • • Up to 1000 VLANs per shared uplink set
  • • Up to 162 VLANs per physical server port, with no restriction on how those VLANs are distributed among the server connections mapped to the same physical server port
  • • Up to 162 VLANs per server connection

**************

 

Input from Ken:

 

***************

 

If you mean ‘is there any change to the Ethernet frame?’, the answer is no.  The frame format is defined by IEEE standards.

 

The change was to the VLAN handling logic in the VC firmware.

 

************

 

Comments or questions?