Guidelines for Configuring VMANs
The following are VMAN configuration guidelines for all platforms:
- Duplicate customer MAC addresses that ingress from
multiple VMAN access ports on the same VMAN can disrupt the port learning
association process in the switch.
- VMAN names must conform to the guidelines described in
Object Names.
- You must use mutually exclusive names for:
- VMAN ports can belong to load-sharing groups.
- You can enable or disable jumbo frames before
configuring VMANs. You can enable or disable jumbo frames on individual
ports. See Configuring Ports on a Switch for more information on configuring jumbo
frames.
- STP (Spanning Tree Protocol) operation on CVLAN
components in a PEB as described in IEEE 802.1ad is not supported.
- The initial version of this feature does not implement
an XML API.
- Multiple VMAN roles can be combined on one port with
certain VLAN types as shown in Port Support for Combined VMAN Roles and VLANs.
Port Support for Combined VMAN Roles and VLANs
| Platform |
Combined CNP, CEP, and Tagged
VLANa,b |
Combined PNP, CNP, and CEP
a,b,c |
Combined PNP and Tagged
VLAN |
Combined PNP and Untagged
VLAN |
|
ExtremeSwitching
and Summit X460-G2, X670-G2, and
X770
|
X |
X |
X d |
X |
Note
If you already configured VLANs and VMANs
on the same stand-alone switch using
ExtremeXOS 11.4 or later, you cannot change the
VMAN ethertype from 0X8100 without first removing either the VLAN or VMAN
configuration.
a Subsets of this group are also
supported. That is, any two of these items are supported.
b When a CNP is combined with a CEP or
tagged VLAN, any CVIDs not explicitly configured for a CEP or tagged VLAN are
associated with the CNP.
c A PNP
(tagged VMAN) and a CNP (untagged VMAN) or CEP cannot be combined on a port for
which the selected VMAN ethertype is 0x8100.
d If the secondary VMAN ethertype is selected for the port,
it must be set to 0x8100.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB