Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 502)

478 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
show mpls vpls detail
3
Brocade(config-mpls-vpls-test_10)# vlan 100
Brocade(config-mpls-vpls-test_10-vlan-100)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test_10-vlan-100)# exit
Brocade(config-mpls-vpls-test_10)# exit
Brocade(config-mpls)# vpls test_20 20
Brocade(config-mpls-vpls-test_20)# vlan 100 inner-vlan 300
Brocade(config-mpls-vpls-test_20-vlan-100-inner-vlan-300)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test_20-vlan-100-inner-vlan-300)# exit
Example of a less-specific and more-specific VLAN mapped to the same VPLS instance
The following example shows a less-specific VLAN and more-specific VLAN (with the same outer
VLAN ID) of the same port in the same VPLS instance.
Brocade(config-mpls)# vpls test_10 10
Brocade(config-mpls-vpls-test_10)# vlan 100
Brocade(config-mpls-vpls-test_10-vlan-100)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test_10-vlan-100)# exit
Brocade(config-mpls-vpls-test_10)# vlan 100 inner-vlan 300
Brocade(config-mpls-vpls-test_10-vlan-100-inner-vlan-300)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test_10-vlan-100-inner-vlan-300)# exit
In the above example, when packets are received on interface ethernet 2/1 with outer VLAN ID 100
and an inner VLAN ID other than 300, the packets are handled as part of VPLS instance 10. In this
case, the inner VLAN is treated as payload.
Specifying a LAG group as the endpoint of a VPLS instance
The endpoint of a VPLS instance can be a static or a dynamic LAG. When the endpoint of a VPLS
instance is a LAG, the VPLS traffic load is distributed to the CE device across all of the LAG’s ports
by way of a hashing mechanism that utilizes the source and destination MAC addresses.
For example, to configure a LAG, enter commands such as the following.
Brocade(config)# lag blue dynamic
Brocade(config-lag-blue)# ports ethernet 1/1 to 1/2
Brocade(config-lag-blue)# primary-port 1/1
To configure a VPLS instance that uses the LAG defined as the endpoint by the previous example
commands, enter the commands as in the following example.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls test1 40000
Brocade(config-mpls-vpls-test1)# vpls-peer 10.10.10.10
Brocade(config-mpls-vpls-test1)# vlan 200
Brocade(config-mpls-vpls-test1)# tagged e 1/1
When the user first creates a LAG and then configure a VPLS instance, the port the user specifies
as the VPLS endpoint must also be the port the user specified as the primary port of the LAG group:
• When the user first configures a VPLS instance and then create a LAG, all ports of the LAG
must be specified as endpoints of the VPLS instance. The VPLS instance uses all the ports of
the LAG.
• When the user later deletes the LAG from the configuration, all ports in the LAG become
independent endpoints in the VPLS instance.
• When the user specified a tagged endpoint for the VPLS instance, all of the ports in the LAG
must be tagged.