8021Q
Revision as of 22:15, 12 June 2010 by Infrastation (talk | contribs) (add IOS and XOS setup limitations)
802.1Q VLAN management in RackTables
known limitations
- port naming is fixed and cannot be changed
- importing configuration for a port, which has VLANs 1~4094 allowed, is very slow
- for uplink-downlink reverb feature to work, both ports must have correct markup, have respective records on the Ports tab, and these records must be linked
- there is no support for configuration templates like those in LiveVLANs
- VLAN1 cannot be used on uplink or downlink ports
- VLAN domains require a special setup procedure to work properly
- unbinding of 802.1Q order hides existing 802.1Q ports config, blocking object deletion
- not all hardware supports trunk ports w/o allowed VLANs, and this is not handled by RackTables
- ExtemeOS requires a special VLAN naming scheme
- there is no user interface for the "disabled" deploy queue
- "max VLANs per switch" option of VLAN switch template is stored, but always ignored
- VRP's "hybrid untagged VLANs" (which are not to be confused with "native" VLAN) break normal management until they are "undone"
setup
IOS
Every port, which is intended to perform switching, must have "switchport mode" explicitly set in its "interface" section.
XOS
Every VLAN besides "Default" and "Mgmt" (that is, any VLAN created by the user) must be named "VLANx", where x is VLAN tag ID. For example, "VLAN2", "VLAN123", "VLAN4000".