Configuring the EVC Model to Carry VPWS Services

Procedure

1. Run system-view

   The system view is displayed.

2. Run interface interface-type interface-number.subinterface-number mode l2

   The EVC Layer 2 sub-interface view is displayed.

3. Run mpls l2vc { ip-address | pw-template template-name } ^* vc-id [ access-port | [ control-word | no-control-word ] | ignore-standby-state | [ raw | tagged | ip-layer2 | ip-interworking ] | tunnel-policy policy-name [ endpoint endpoint-address color color-value ] | [ secondary | bypass ] ] ^*

   A VPWS connection is created.

   

   • The IDs of VCs using the same encapsulation type must be unique.

   • The raw, tagged, and access-port parameters can be specified in this command only when this command is applied to Ethernet links. The access-port parameter applies only to Ethernet main interfaces.

   • The default tunnel policy uses LDP LSPs for VPWS PWs. If you want to use other types of tunnels for a VPWS PW, configure the tunnel-policy policy-name parameter for a VPWS PW to reference the corresponding tunnel policy.

4. (Optional) Run encapsulation vlan pass

   The EVC VPWS tagged mode is enabled.

   In EVC scenarios, if the EVC model is configured to carry VPWS services, PWs work in raw mode (with the VPWS encapsulation type being VLAN). In this case, packets leaving PWs are directly forwarded without having the outer tag removed. To solve this problem, run the encapsulation vlan pass command to configure the PWs to work in tagged mode, so that the outer tag is removed when the packets leave the PWs.

5. Run commit

   The configuration is committed.