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

NE40E-M2 V800R010C10SPC500 Configuration Guide - WAN Access 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - WAN Access
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 TDMoPSN

Configuring TDMoPSN

Local CCC, SVC, and PWE3 pseudo wires (PWs) can be established to transmit TDMoPSN services.

Applicable Environment

Services of the 2G RAN network, mainly a small number of voice services, are transmitted over TDM links. Generally, one to three E1 interfaces on a BTS are connected to a BSC. Some mobile carriers do not own fixed network infrastructure, and therefore have to lease E1 lines of the fixed network at a high price.

With the introduction of TDMoPSN services, the services between the CEs in the same city can be transparently transmitted over TDM links in a Metro Ethernet (ME) network. Data of the Fractional E1 interface can be transmitted from the BTS to BSC in the mode of structuralized TDM circuit emulation.

A PW is established between Router through VLL or PWE3 to transparently transmit TDM frames.

Pre-configuration Tasks

Before configuring a TDMoPSN service, complete the following tasks on the routers at both ends of the PW:

  • Configure static routes or an IGP protocol on PEs and Ps on the MPLS backbone network to ensure IP connectivity.

  • Configure basic MPLS functions on PEs and Ps of the MPLS backbone network.

  • Set up LDP sessions among PEs (if the PEs are indirectly connected, set up remote LDP sessions between them).

  • Establish tunnels between PEs based on the tunnel policy (if no tunnel policy is configured, the default tunnel policy LDP is used).

  • Configure synchronous serial interfaces and TDM link protocols.

Configuring a Local TDMoPSN Service

To configure the local TDMoPSN Service, you need to create a local CCC connection and only configure the incoming and outgoing interfaces of the CCC connection on a local PE. The local CCC connection is bidirectional and only one such connection needs to be created.

Context

The local CCC connection is bidirectional, and only one connection is required.

Perform the following steps on PEs:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls l2vpn

    MPLS L2VPN is enabled.

  3. Run quit

    Return to the system view.

  4. Run ccc ccc-connection-name interface interface-type1 interface-number1 out-interface interface-type2 interface-number2 [ jitter-buffer depth | idle-code idle-code-value | rtp-header | tdm-encapsulation number ]

    A local CCC connection is created.

  5. Run commit

    The configuration is committed.

Follow-up Procedure

After the configuration mentioned above on the PE, a local CCC connection is created.

Configuring a Remote TDMoPSN Service

TDMoPSN supports the establishment of local SVC and PWE3 PWs to transmit CES services.

Context

At the edge of a PSN, PE1 on the user side is connected downstream to CE1, and PE2 on the network side is connected to upstream CE2. Both PEs require the following configurations, whereas devices inside the PSN do not.

The following PW types are supported:

  • SVC

  • PWE3

Referring to the configuration of a PW, take the dynamic PWE3 as an example.

The procedures for configuring the preceding parameters in the two views are as follows:

Procedure

  • Create a PW in the PW template view.
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run pw-template pw-template-name

      A PW template is created and the PW template view is displayed.

    4. Run peer-address ip-address

      An IP address is assigned to the peer PE of the PW.

    5. Run tnl-policy policy-name

      A policy is configured for the PW template to select tunnels.

    6. (Optional) Run jitter-buffer depth depth

      The depth of the jitter buffer is set.

    7. (Optional) Run tdm-encapsulation-number number

      The number of TDM frames encapsulated in a CESoPSN or SAToP packet is set.

    8. (Optional) Run rtp-header

      The RTP header carried in the TDM transparent transmission encapsulation is configured.

    9. Run quit

      Exit from the PW template view.

    10. Run interface controller-number : set-number

      The serial interface view is displayed.

    11. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ | tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | rtp-header | ignore-standby-state ] *

      A dynamic PW is created.

    12. (Optional) Run trap-threshold { ces-jtrovr-exc | ces-jtrudr-exc | ces-lospkt-exc | ces-malpkt-exc | ces-misorderpkt-exc | ces-straypkt-exc } trigger-threshold trigger-threshold-value resume-threshold resume-threshold-value

      The alarm and clear alarm thresholds of CES service performance are set.

    13. (Optional) Run pw-control-word rml-bit enable

      The serial interface is enabled to use RML bits in PW control words to transparently transmit alarms.

    14. Run commit

      The configuration is committed.

  • Creating a PW in the interface view
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run interface controller-number : set-number

      The serial interface view is displayed.

    4. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ | tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | rtp-header | ignore-standby-state ] *

      A dynamic PW is created.

    5. (Optional) Run trap-threshold { ces-jtrovr-exc | ces-jtrudr-exc | ces-lospkt-exc | ces-malpkt-exc | ces-misorderpkt-exc | ces-straypkt-exc } trigger-threshold trigger-threshold-value resume-threshold resume-threshold-value

      The alarm and clear alarm thresholds of CES service performance are set.

    6. (Optional) Run pw-control-word rml-bit enable

      The serial interface is enabled to use RML bits in PW control words to transparently transmit alarms.

    7. Run commit

      The configuration is committed.

Configuring a Local CES Service

To configure the local CEP Service, you need to create a local CCC connection and only configure the incoming and outgoing interfaces of the CCC connection on a local PE. The local CCC connection is bidirectional and only one such connection needs to be created.

Context

The local CCC connection is bidirectional, and only one connection is required.

Perform the following steps on PEs:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls l2vpn

    MPLS L2VPN is enabled.

  3. Run quit

    Return to the system view.

  4. Run controller cpos cpos-number

    The CPOS interface view is displayed.

  5. Run using vc4

    The CPOS interface is configured to work in clear channel mode, and a synchronous serial interface is created on the CPOS interface.

  6. Run quit

    Return to the system view.

  7. Run ccc ccc-connection-name interface interface-type1 interface-number1 out-interface interface-type2 interface-number2 [ jitter-buffer depth | rtp-header ]

    A local CCC connection is created.

  8. Run interface serial

    The Serial interface view created in step 5 is displayed.

  9. (Optional) Run cep soh-transport enable

    Enable SOH transport on a CEP interface.

  10. Run commit

    The configuration is committed.

Follow-up Procedure

After the configuration mentioned above on the PE, a local CCC connection is created.

Configuring a Remote CEP Service

TDMoPSN supports the establishment of local SVC and PWE3 PWs to transmit CEP services.

Context

At the edge of a PSN, PE1 on the user side is connected downstream to CE1, and PE2 on the network side is connected to upstream CE2. Both PEs require the following configurations, whereas devices inside the PSN do not.

The following PW types are supported:

  • SVC

  • PWE3

Referring to the configuration of a PW, take the dynamic PWE3 as an example.

The procedures for configuring the preceding parameters in the two views are as follows:

Procedure

  • Create a PW in the PW template view.
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run pw-template pw-template-name

      A PW template is created and the PW template view is displayed.

    4. Run peer-address ip-address

      An IP address is assigned to the peer PE of the PW.

    5. Run tnl-policy policy-name

      A policy is configured for the PW template to select tunnels.

    6. (Optional) Run jitter-buffer depth depth

      The depth of the jitter buffer is set.

    7. (Optional) Run rtp-header

      The RTP header carried in the TDM transparent transmission encapsulation is configured.

    8. Run quit

      Exit from the PW template view.

    9. Run controller cpos cpos-number

      The CPOS interface view is displayed.

    10. Run using vc4

      The CPOS interface is configured to work in clear channel mode, and a synchronous serial interface is created on the CPOS interface.

    11. Run interface serial

      The Serial interface view created in is displayed.

    12. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ | tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | rtp-header | ignore-standby-state ] *

      A dynamic PW is created.

    13. (Optional) Run trap-threshold { ces-jtrovr-exc | ces-jtrudr-exc | ces-lospkt-exc | ces-malpkt-exc | ces-misorderpkt-exc | ces-straypkt-exc } trigger-threshold trigger-threshold-value resume-threshold resume-threshold-value

      The alarm and clear alarm thresholds of CES service performance are set.

    14. (Optional) Run pw-control-word rml-bit enable

      The serial interface is enabled to use RML bits in PW control words to transparently transmit alarms.

    15. Run commit

      The configuration is committed.

  • Creating a PW in the interface view
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run controller cpos cpos-number

      The CPOS interface view is displayed.

    4. Run using vc4

      The CPOS interface is configured to work in clear channel mode, and a synchronous serial interface is created on the CPOS interface.

    5. Run interface serial

      The Serial interface view created in is displayed.

    6. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ | tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | rtp-header | ignore-standby-state ] *

      A dynamic PW is created.

    7. (Optional) Run trap-threshold { ces-jtrovr-exc | ces-jtrudr-exc | ces-lospkt-exc | ces-malpkt-exc | ces-misorderpkt-exc | ces-straypkt-exc } trigger-threshold trigger-threshold-value resume-threshold resume-threshold-value

      The alarm and clear alarm thresholds of CES service performance are set.

    8. (Optional) Run pw-control-word rml-bit enable

      The serial interface is enabled to use RML bits in PW control words to transparently transmit alarms.

    9. Run commit

      The configuration is committed.

Verifying the TDM Service Configuration

After a TDM service is configured, you cannot only view configurations and statuses of E1/CE1 interfaces, but also view information about the static PW and dynamic PW.

Context

Run the following commands to check the previous configuration.

Procedure

  • Run the display controller e1 controller-number command to check the configuration and status of the E1/CE1 interface.
  • Run the display mpls static-l2vc [ vc-id |interface interface-type interface-number |state { down | up } ] or display mpls static-l2vc brief command to check information about the static PW.
  • Run the display mpls l2vc [ vc-id | interface interface-type interface-number ] or display mpls l2vc brief command to check information about the dynamic PW.
Download
Updated: 2019-01-02

Document ID: EDOC1100058399

Views: 13883

Downloads: 37

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