Configuring an SVC VLL
The SVC VLL is a simplified Martini mode, in which inner labels are manually specified. The SVC mode makes planning of label resources on VLL networks easier, but it increases configuration workload and is not easy to extend.
Pre-configuration Tasks
Before configuring the SVC VLL, complete the following tasks:
Configure static routes or an IGP protocol for the PE and P devices on the MPLS backbone network to implement IP connectivity.
Enable MPLS for PEs and Ps.
Set up an LSP tunnel or a TE tunnel between the PEs
You also need to configure tunnel policies when VLL services need to be transmitted over TE tunnels or when VLL services need to be load balanced among multiple tunnels to fully use network resources. For details, see step 1 in Configuring and Applying a Tunnel Policy.
Procedure
Perform the following operations on the PE devices at both ends of a VC:
Run system-view
The system view is displayed.
Run mpls l2vpn
MPLS L2VPN is enabled and the MPLS L2VPN view is displayed.
Run quit
Return to the system view.
Run interface interface-type interface-number
The AC interface view is displayed.
The SVC VLL can use the following interfaces as AC interfaces: GE interfaces, GE sub-interfaces, XGE interfaces, XGE sub-interfaces, 25GE interfaces, 25GE sub-interfaces, 40GE interfaces, 40GE sub-interfaces, 100GE interfaces, 100GE sub-interfaces, MultiGE interfaces, MultiGE sub-interfaces, Eth-Trunk sub-interfaces, VLANIF interfaces, and Eth-Trunk interfaces.
The sub-interfaces can be dot1q sub-interfaces, QinQ sub-interfaces, QinQ mapping sub-interfaces or QinQ stacking sub-interfaces.
To use an XGE interface, a GE interface, a 25GE interface, a MultiGE interface, a 40GE interface, a 100GE interface, or an Eth-Trunk interface of the device as the AC interface of the PE, run the undo portswitch command to change a Layer 2 interface to a Layer 3 interface.
Run mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value tunnel-policy tnl-policy-name | [ [ control-word | no-control-word ] | [ raw | tagged ] ] *
The SVC VLL is created.
A PW template must be configured before you can use the SVC VLL. For details on how to configure a PW template, see Creating a PW Template and Setting Attributes for the PW Template.
If virtual circuit connectivity verification (VCCV) is not required for a static VC, vc-id does not need to be specified. vc-id is mandatory when VCCV needs to be performed.
The incoming label of the CCC and receive label of the SVC all range from 16 to 1023. They are in the same label space with those reserved for static LSPs. However, the outgoing label of the CCC and the transmit label of the SVC range from 0 to 1048575 because they are used for interworking.
(Optional) Run mpls l2vpn service-name service-name
A name is configured for the L2VPN service. You can now monitor the L2VPN service by clicking the name directly on the NMS GUI.
Verifying the Configuration
After completing the SVC VLL configuration, run the following commands to check information about the SVC connection and interfaces used by the SVC connection.
- Run the display mpls static-l2vc [ interface interface-type interface-number ] command to check the SVC L2VPN connection information on the PE.
- Run the display mpls static-l2vc brief command to check the SVC L2VPN connection brief information on the PE.
- Run the display l2vpn ccc-interface vc-type static-vc [ down | up ] command to check the interface information of the SVC connections in Up/Down state.