No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring VPWS Switching

Configuring VPWS Switching

A switching PW can be any of three types, namely, dynamic switching PW, static switching PW, and mixed switching PW.

Usage Scenario

To support Multi-Segment , the VPWS switching is needed. MH-PW requires switching labels at PW label layer while forwarding packets.

VPWS switching must be configured on the S-PE with high performance and capability of setting up large numbers of MPLS LDP sessions.

When configuring MH-PW, you need VPWS switching on the S-PE.

In the following cases, VPWS switching is required:

  • Two PEs are not located in the same AS and no signaling or tunnel can be set up between the two PEs. (If inter-AS tunnel is set up by the BGP labeled route, MH-PW is not required.)

  • The signaling of two PEs differs from each other.

  • If access device supports MPLS, but cannot set up large numbers of LDP session, you can use User Facing Provider Edge (UFPE) as U-PE. And you can use the S-PE as the switching node of LDP session, which is similar to signaling reflector.

VPWS MS-PWs include static MS-PWs, dynamic MS-PWs and static-dynamic MS-PWs. Determine which type of PW to use according to the actual situation.

Pre-configuration Tasks

Before configuring PW switching, complete the following tasks:

Procedure

  • Static PW Switching

    Perform the following steps on the SPEs.

    1. Run system-view

      The system view is displayed.

    2. Run

      The static PWs switching is enabled.

      A PW label must be manually configured on the SPE for static PW switching.

      The conditions of setting up a static MH-PW are as follows:

      • On UPE, once the AC state is up and PSN tunnel exists, the PW state is up.

      • On the SPE, once the PSN tunnels on both sides exist, the PW is in up state. This is regardless of whether the PW encapsulation of SPE is consistent with that of U-PE or not.

      For the sake of management convenience, it is recommended to configure the same PW encapsulation type on the devices along the PW (UPE and SPE).

    3. Run commit

      The configuration is committed.

  • Dynamic PW Switching

    Do as follows on the SPEs.

    1. Run system-view

      The system view is displayed.

    2. Run mpls switch-l2vc [ service-name service-name ] ip-address vc-id [ tunnel-policy policy-name ] [ oam-packet pop flow-label ] between ip-address vc-id [ tunnel-policy policy-name ] [ oam-packet pop flow-label ] encapsulation encapsulation-type [ control-word-transparent ]

      The dynamic PWs switching is configured.

      The configuration of a dynamic switching PW is simple. After a dynamic switching PW is configured, the remote label is sent from two neighboring endpoints (UPE or SPE) to an SPE by signaling. The control word and the VCCV capability are carried in the signaling and sent from two UFPEs to the SPE.

      When configuring dynamic PW switching, ensure that the PW encapsulation type is consistent on the devices (UPE and SPE) along the PW; otherwise, the PW will not enter the Up state.

      NOTE:
      When configuring a dynamic PW, if Huawei devices are connected to non-Huawei devices in internetworking mode, select ip-layer2; if all the devices are Huawei devices, select ip-interworking.

    3. Run commit

      The configuration is committed.

  • Configure hybrid PW switching.

    Perform the following steps on the SPEs.

    1. Run system-view

      The system view is displayed.

    2. Run mpls switch-l2vc [ instance-name instance-name ] ip-address vc-id [ tunnel-policy policy-name ] [ oam-packet pop flow-label ] between ip-address vc-id [ tunnel-policy policy-name ] trans trans-label recv recv-label [ oam-packet pop flow-label ]encapsulation encapsulation-type [ control-word-transparent ]

      A hybrid switching PW consisting of both static and dynamic PWs is configured.

Checking the Configurations

After a switching PW is configured, you can view information about the switching PW.

  • Run the display mpls switch-l2vc [ ip-address vc-id encapsulation encapsulation-type | state { down | up } | brief ] command to check information about the PW switching on S-PEs.

Run the display mpls switch-l2vc command. You can view the VC status is Up.

Total Switch VC : 1, 1 up, 0 down

*Switch-l2vc type             : LDP<---->LDP
 Peer IP Address              : 2.2.2.2, 1.1.1.1
 VC ID                        : 22, 11
 VC Type                      : VLAN
 VC State                     : up
 VC StatusCode                |PSN |OAM | FW |    |PSN |OAM | FW |
                   -Local VC :| UP | UP | UP |    | UP | UP | UP |
                   -Remote VC:| UP | UP | UP |    | UP | UP | UP |
 Session State                : up, up
 Local/Remote Label           : 21504/21504, 21505/21504
 InLabel Status               : 0 , 0 
 Local/Remote MTU             : 1500/1500, 1500/1500
 Local/Remote Control Word    : Enable/Enable, Enable/Enable
 Local/Remote VCCV Capability : cw alert lsp-ping/ cw alert ttl lsp-ping bfd, cw alert ttl lsp-ping bfd/ cw alert lsp-ping
 Switch-l2vc tunnel info      :
                                1 tunnels for peer 2.2.2.2
                                NO.0  TNL Type : ldp   , TNL ID : 0x0000000001004c4b42
                                1 tunnels for peer 1.1.1.1
                                NO.0  TNL Type : ldp   , TNL ID : 0x0000000001004c4b41
 CKey                         : 33, 31
 NKey                         : 32, 30
 Tunnel policy                : --, --
 Control-Word transparent     : NO
 Create time                  : 0 days, 0 hours, 0 minutes, 14 seconds
 UP time                      : 0 days, 0 hours, 0 minutes, 10 seconds
 Last change time             : 0 days, 0 hours, 0 minutes, 14 seconds
 VC last up time              : 2012-03-12 12:31:31
 VC total up time             : 0 days, 2 hours, 12 minutes, 51 seconds
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27880

Downloads: 53

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next