Table of Contents
Advertisement
The restrictions are as follows:
• A PoS port cannot be added to a VLAN if the VLAN is a protocol-based VLAN.
• A VLAN cannot be configured to be a protocol-based VLAN if the VLAN contains a
PoS port.
• A MAC address VLAN cannot be enabled on a PoS port.
The
config vlan <name> protocol any
used to configure the default VLAN for PoS ports.
In the
config vlan <name> [add | delete] ports <portlist> {tagged |
untagged} {nobroadcast}
untagged
IPCP and BCP are mutually exclusive configuration options for a given PoS port: they
cannot both be enabled simultaneously on the same PoS port. Generally, when IPCP is
enabled on a port, the port must be a member of one and only one VLAN. Furthermore,
no other ports may be members of this VLAN, and IP routing is the only protocol
supported on the VLAN. The one exception to this rule occurs when APS is enabled. A
single VLAN may contain two IPCP-enabled ports if they are members of the same APS
group.
Configuring Tagged VLAN 802.1p and 802.1Q Functions
The dot1q tag mapping and tag nesting commands are supported only by PoS
ports and apply only when BCP is enabled on the PoS port.
The following ExtremeWare commands are supported for the PoS module:
•
config dot1q ethertype <ethertype>
•
config dot1p type dot1p_priority <priority> qosprofile <qosprofile>
If a PoS port receives a frame with a priority value "n" that is not mapped to a
profile in the range from qp1 through qp8, the frame is assigned to QoS profile
qp
n+1
The following commands provide PoS module support for managing 802.1Q tags:
•
config dot1q tagmapping
•
config dot1q tagnesting
Packet Over SONET Module Installation and User Guide
command, PoS ports support the optional
keywords when BCP is enabled, and ignore them when IPCP is enabled.
.
Configuring VLAN-Related Attributes
command is supported, because it can be
and
tagged
3-39
Advertisement
Table of Contents
