Modifying 802.1Q Groups
Page 16-14
Modifying 802.1Q Groups for Gigabit Ethernet Ports
To modify the configuration of an 802.1Q group for Gigabit ports, use the mas command as
shown:
mas <slot>/<port> <instance>
where <slot> is the slot number of the module on the switch, <port> is the port number where
the service was created, and <instance> is the identifier for the service on this port. For exam-
ple, to modify 802.1Q service instance 1 on port 5 of slot 2, enter:
mas 2/5 1
If this is a legacy Ethernet module, the screen appears as shown:
Slot 2 Port 5 Ethernet 802.1Q Service
1) Tag : 3
2) Priority : 0
If this is a Kodiak ASIC-based module, the screen appears as shown:
Slot 2 Port 5 Ethernet 802.1Q Service
1. Description (30 chars max) :
2. Tag : 0
3. Priority Remap Values :
30. 0 - 0
31. 1 - 1
32. 2 - 2
33. 3 - 3
34. 4 - 4
35. 5 - 5
36. 6 - 6
37. 7 - 7
To change a field setting, enter the line number, an equal sign, and the new value. For exam-
ple, to change the Priority setting to 7, you would enter a 3 (the line number for priority), an
equal sign (=), and a 37, as shown:
3=37
♦ Important Notes ♦
ESX-K and GSX-K Kodiak ASIC-based modules support
802.1p traffic prioritization. For chassis configurations
that include only ESX-K, GSX-K and/or WSX series
modules, 802.1p priority bits can be carried inbound on
a tagged port (configured with multiple spanning tree
802.1Q) across the backplane. This priority information
is used at the egress port to queue the packet, and is
sent out in the packet whether the egress port is tagged
or not.
The ESX-K and GSX-K modules can also remap incom-
ing priority on an ingress port. If priority remapping
has been configured, the new priority will be carried
across the backplane. The priority information is used
to queue the packet, and is sent out in the packet if the
egress port is tagged.
To Next Page
Loading...
Need help?
General
