Virtual Private LAN Service
210
FD 100/320Gbps NT and FX NT IHub Services Guide
3HH-11985-AAAA-TQZZA Issue: 13
5.8.5.5 Configuring “restricted-tagging” on an SAP
When “restricted-tagging” is enabled on an SAP, only double-vlan-tagged packets
arriving at the SAP will be forwarded. Only packets with outer TPID as 0x8100 and
inner TPID 0x8100 are considered as double-vlan-tagged packets.
The following example displays restricted-tagging configuration:
*A:ALA-Dut-B>configure>service>epipe# info
----------------------------------------------
description "VPLS service 2100"
sap lt:1/1/1:5 create
description "Sap description for service id 2100"
restricted-tagging
exit
no shutdown
----------------------------------------------
*A:ALA-Dut-B>configure>service>epipe#
To disable restricted-tagging, use the no restricted-tagging command.
*A:ALA-Dut-B>configure>service>epipe# info
----------------------------------------------
description "VPLS service 2100"
sap lt:1/1/1:5 create
description "Sap description for service id 2100"
no restricted-tagging
exit
no shutdown
----------------------------------------------
*A:ALA-Dut-B>configure>service>epipe#
5.8.5.6 Configuring Management Points (MEPs/MIPs) for
Ethernet CFM on SAPs
Two steps are required to configure the CFM in a VPLS network:
1 The MD and MA need to be created first
2 The MEP/MIP can be created in the VPLS service instance, associating it to a
SAP and added to the defined MD and MA. The MEP has to be specified with the
“Domain” and “Association” IDs that have been configured already under the
configure eth-cfm context (see “Ethernet Connectivity Fault Management”).
To Next Page
Loading...
Need help?
General
