Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 501
![background image](/manuals/361646/501/background.png)
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
477
53-1003031-02
show mpls vpls detail
3
Brocade(config-mpls)# vpls v1 40000
Brocade(config-mpls-vpls-v1)# vlan 200 inner-vlan 300
Brocade(config-mpls-vpls-v1-vlan-200)# tagged ethernet 3/11
Syntax: [no] vlan VLAN-ID inner-vlan VLAN-ID
Syntax: [no] tagged ethernet slot/port
The vlan VLAN-ID variable, which is the outer VLAN ID, can be in the range from 1 through 4094
and excludes the default VLAN.
The inner-vlan VLAN-ID variable, can be in the range from 1 through 4095 and includes the default
VLAN.
Use the no form of the command to remove the dual-tagged VPLS VLAN configuration and its
associated endpoints. For example, the command no vlan 200 inner-vlan 300 removes the
dual-tagged VLAN and associated endpoints. The single-tagged VLAN, vlan 200, is not deleted.
Similarly, the command no vlan 200 removes the single-tagged VLAN, vlan 200, and associated
endpoints. The dual-tagged VLAN, vlan 200 inner-vlan 300, is not deleted.
Example of dual-tagged endpoints mapped to different VPLS instances
The following example shows two dual-tagged endpoints on the same physical interface with the
same outer VLAN ID and different inner VLAN IDs mapped to different VPLS instances.
Brocade(config-mpls)# vpls test_10 10
Brocade(config-mpls-vpls-test_10)# vlan 100 inner-vlan 200
Brocade(config-mpls-vpls-test_10-vlan-100-inner-vlan-200)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test_10-vlan-100-inner-vlan-200)# 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 dual-tagged endpoints mapped to the same VPLS instance
The following example shows two dual-tagged endpoints on the same physical interface with the
same outer VLAN ID and different inner VLAN IDs mapped to the same VPLS instance.
Brocade(config-mpls)# vpls test 10
Brocade(config-mpls-vpls-test)# vlan 100 inner-vlan 200
Brocade(config-mpls-vpls-test-vlan-100-inner-vlan-200)# tagged ethernet 2/1
Brocade(config-mpls-vpls-test-vlan-100-inner-vlan-200)# exit
Brocade(config-mpls-vpls-test)# vlan 100 inner-vlan 300
Brocade(config-mpls-vpls-test-vlan-100-inner-vlan-300)# tagged ethernet 2/1
In the above example, when packets are received with outer VLAN ID 100 and no inner VLAN ID, the
packets are not handled as part of VPLS instance 10.
Example of a less-specific and more-specific VLAN mapped to different VPLS instances
The following example shows a less-specific VLAN and more-specific VLAN (with the same outer
VLAN ID) of the same port in different VPLS instances.
Brocade(config-mpls)# vpls test_10 10