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

OSN 500 550 580 V100R008C50 Commissioning and Configuration Guide 02

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).
Configuration Example: E-Line Services Carried by PWs (Based on VLAN Switching)

Configuration Example: E-Line Services Carried by PWs (Based on VLAN Switching)

This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs (based on VLAN switching) for each NE according to the networking diagram.

Networking Diagram

The networking diagram shows the requirements for the E-Line services carried by PWs (based on VLAN switching).

On the network shown in Figure 3-14, services from NodeB 1 and services from NodeB 2 have a same VLAN ID, and need VLAN switching before being transported to the RNC. Service requirements are as follows:

  • Services from NodeB 1 and services from NodeB 2 are transported to NE1 through the 4-EM6F-3 and 4-EM6F-4 ports respectively.
  • NE4 converges services from NodeB 1 and NodeB 2, and transports the services to the RNC.
  • Services from NodeB 1 are common Internet access services of which the CIR is 10 Mbit/s and the PIR is 30 Mbit/s.
  • Services from NodeB 2 are data services of which the CIR is 30 Mbit/s and the PIR is 50 Mbit/s.
  • Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100, and are mapped to two PWs. After VLAN switching, the VLAN ID of services from NodeB 1 remains unchanged, whereas the VLAN ID of services from NodeB 2 is changed to 200.
  • Services from NodeB 1 and NodeB 2 are protected by tunnel APS.
    • Working path: NE1-NE2-NE4
    • Protection path: NE1-NE3-NE4
Figure 3-14  Networking diagram of the E-Line services carried by PWs (based on VLAN switching)

NOTE:
  • This topic considers the OptiX OSN 550 as an example to describe the board layout. In the case of other products, the configuration method is the same, except for the slots. For the slot information, see the Hardware Description of the relevant product.
  • On a live data network, an Ethernet service is added to the source NE, passed through the transit NEs, and dropped from the sink NE. Follow instructions in Configuring Transit NEs for Ethernet Services Carried by PWs to configure transit NEs for the Ethernet services carried by PWs.
NE IP Address IP Mask LSR ID
NE1 4-EM6F-1 18.1.1.1 255.255.255.252 130.0.0.1
4-EM6F-2 18.1.2.1 255.255.255.252
NE2 4-EM6F-1 18.1.1.2 255.255.255.252 130.0.0.2
4-EM6F-2 18.1.1.5 255.255.255.252
NE3 4-EM6F-1 18.1.2.2 255.255.255.252 130.0.0.3
4-EM6F-2 18.1.2.5 255.255.255.252
NE4 4-EM6F-1 18.1.1.6 255.255.255.252 130.0.0.4
4-EM6F-2 18.1.2.6 255.255.255.252
NOTE:
  • The IP addresses of the Ethernet ports on an NE must not be in the same network segment.
  • The IP addresses of the ports at both ends of a tunnel must be in the same network segment.

Service Planning

The engineering information for configuring the E-Line services carried by PWs (based on VLAN switching) contains the engineering information for configuring the tunnels carrying the PWs, the engineering information for configuring the PWs, and the engineering information for configuring the UNI-NNI E-Line services carried by the PWs.

The PWs that carry the E-Line services are carried by tunnels. Therefore, you need to plan the tunnels during the service planning. Planning the E-Line services carried by PWs involves the following:
Table 3-76  Basic attributes of a tunnel
Parameter Parameter Planning
Tunnel Name

Auto-Assign

NOTE:
The rule of auto-assigned Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x
Protection Tunnel Name

Auto-Assign

NOTE:
The rule of auto-assigned Protection Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x_PRT
Protocol Type MPLS
Signaling Type Static CR
Service Direction Bidirectional
Protection Type 1:1
Protection Group Name

Auto-Assign

NOTE:
The rule of auto-assigned ProtectionSource NE-Sink NE-PG-0000000x
Switching ModeSingle Single-Ended switching
Table 3-77  Planning information of the tunnels
Tunnel Tunnel ID Node Node Type In Interface In Label Reverse In Label Out Interface Out Label Reverse Out Label Next Hop Reverse Next Hop Source Node Sink Node
Working Tunnel Auto-Assign NE1 Ingress - - 102 4-EM6F-1 100 - 18.1.1.2 - - 130.0.0.4
NE2 Transit 4-EM6F-1 100 103 4-EM6F-2 101 102 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4
NE4 Egress 4-EM6F-1 101 - - - 103 - 18.1.1.5 130.0.0.1 -
Protection Tunnel Auto-Assign NE1 Ingress - - 202 4-EM6F-2 200 - 18.1.2.2 - - 130.0.0.4
NE3 Transit 4-EM6F-1 200 203 4-EM6F-2 201 202 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4
NE4 Egress 4-EM6F-2 201 - - - 203 - 18.1.2.5 130.0.0.1 -
NOTE:
In end-to-end mode, Tunnel ID, In Label, Out Label, Reverse In Label and Reverse Out Label can be use Auto-Assign mode.
Table 3-78  Parameter planning for MPLS tunnel OAM
Parameter Parameter Planning
OAM Status Enable Sending and Receiving Enable Sending and Receiving
Detection Mode Manual Manual
Detection Packet Type FFD
NOTE:
Detection Packet Period can be set only when Detection Packet Type is FFD.
FFD
Detection Packet Period (ms) 3.3
NOTE:
Generally, the OAM packet is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.
3.3
Table 3-79  Parameter planning for MPLS tunnel APS
Parameter Parameter Planning
Protocol Status Enabled
Revertive Mode Revertive
WTR Time(min) 5
Hold-off Time(100ms) 0
NOTE:
Services are not protected with multiple protection schemes. Therefore, the setting of Hold-off Time(100ms) is unnecessary.
Table 3-80  Parameter planning for the PWs

Parameter

NodeB 1 PW

NodeB 2 PW

PW ID

35

45

PW Signaling Type

Static

Static

PW Type

Ethernet Tagged Mode

Ethernet Tagged Mode

PW Direction

Bidirectional

Bidirectional

PW Incoming Label/Source Port

20

30

PW Outgoing Label/Sink Port

20

30

Peer LSR ID

NE1

130.0.0.4

130.0.0.4

NE4

130.0.0.1

130.0.0.1

MPLS Tunnel name

NE1_NE4_working

NE1_NE4_working

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

10240

30720

PIR(kbit/s)

30720

51200

CBS(bytes)

30720

51200

PBS(bytes)

30720

51200

Request VLAN

10

20

TPID

0x8100

0x8100

Table 3-81  Parameter planning for the UNI-NNI E-Line services carried by PWs

Parameter

NodeB 1

NodeB 2

RNC

Service ID

1

2

1

2

Name

E-Line-1

E-Line-2

E-Line-1

E-Line-2

Direction

UNI-NNI

UNI-NNI

UNI-NNI

UNI-NNI

Service Tag Role

User

Service

User

Service

UNI

4-EM6F-3

4-EM6F-4

4-EM6F-3

4-EM6F-3

VLANs

100

100

100

200

Bearer Type

PW

PW

PW

PW

PW ID

35

45

35

45

BPDU

Not Transparently Transmitted

Not Transparently Transmitted

Not Transparently Transmitted

Not Transparently Transmitted

MTU (bytes)

-

-

-

-

Configuration Process (in End-to-End Mode)

This section describes how to configure E-Line services carried by PWs in end-to-end mode.

Prerequisites

  • You must be familiar with the networking requirements and service plan of the E-Line services carried by PWs (in the scenario of based on VLAN switching).
  • You are an NM user with Administrators rights or higher.

Procedure

  1. Follow the instructions in Configuring LSR ID and Configuring the NNIs for Ethernet Services Carried by Static MPLS Tunnels and configure LSR IDs for NEs and NNIs for services carried by MPLS tunnels.

    Table 3-82  Planning information of the LSR ID and port
    NE IP Address IP Mask LSR ID
    NE1 4-EM6F-1 18.1.1.1 255.255.255.252 130.0.0.1
    4-EM6F-2 18.1.2.1 255.255.255.252
    NE2 4-EM6F-1 18.1.1.2 255.255.255.252 130.0.0.2
    4-EM6F-2 18.1.1.5 255.255.255.252
    NE3 4-EM6F-1 18.1.2.2 255.255.255.252 130.0.0.3
    4-EM6F-2 18.1.2.5 255.255.255.252
    NE4 4-EM6F-1 18.1.1.6 255.255.255.252 130.0.0.4
    4-EM6F-2 18.1.2.6 255.255.255.252

  2. Configure the tunnel for carrying services.

    1. Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the Create Tunnel window is displayed.

    2. Configure the tunnel according the parameters Planning.

      Table 3-83  Basic attributes of a tunnel
      Parameter Parameter Planning
      Tunnel Name

      Auto-Assign

      NOTE:
      The rule of auto-assigned Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x
      Protection Tunnel Name

      Auto-Assign

      NOTE:
      The rule of auto-assigned Protection Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x_PRT
      Protocol Type MPLS
      Signaling Type Static CR
      Service Direction Bidirectional
      Protection Type 1:1
      Protection Group Name

      Auto-Assign

      NOTE:
      The rule of auto-assigned ProtectionSource NE-Sink NE-PG-0000000x
      Switching ModeSingle Single-Ended switching
      Table 3-84  Planning information of the tunnels
      Tunnel Tunnel ID Node Node Type In Interface In Label Reverse In Label Out Interface Out Label Reverse Out Label Next Hop Reverse Next Hop Source Node Sink Node
      Working Tunnel Auto-Assign NE1 Ingress - - 102 4-EM6F-1 100 - 18.1.1.2 - - 130.0.0.4
      NE2 Transit 4-EM6F-1 100 103 4-EM6F-2 101 102 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4
      NE4 Egress 4-EM6F-1 101 - - - 103 - 18.1.1.5 130.0.0.1 -
      Protection Tunnel Auto-Assign NE1 Ingress - - 202 4-EM6F-2 200 - 18.1.2.2 - - 130.0.0.4
      NE3 Transit 4-EM6F-1 200 203 4-EM6F-2 201 202 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4
      NE4 Egress 4-EM6F-2 201 - - - 203 - 18.1.2.5 130.0.0.1 -
      Table 3-85  Parameter planning for MPLS tunnel OAM
      Parameter Parameter Planning
      OAM Status Enable Sending and Receiving Enable Sending and Receiving
      Detection Mode Manual Manual
      Detection Packet Type FFD
      NOTE:
      Detection Packet Period can be set only when Detection Packet Type is FFD.
      FFD
      Detection Packet Period (ms) 3.3
      NOTE:
      Generally, the OAM packet is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.
      3.3
      Table 3-86  Parameter planning for MPLS tunnel APS
      Parameter Parameter Planning
      Protocol Status Enabled
      Revertive Mode Revertive
      WTR Time(min) 5
      Hold-off Time(100ms) 0
      NOTE:
      Services are not protected with multiple protection schemes. Therefore, the setting of Hold-off Time(100ms) is unnecessary.

  3. Configure common Internet access services on NodeB 1 in end-to-end mode.
    1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
    2. Set general attributes for the common Internet access services on NodeB 1.

      Table 3-87  General attributes for the common Internet access services on NodeB 1
      Parameter Value in This Example
      Service Type ETH
      Service ID 1
      Service Name E-Line-1
      Protection Type Unprotected

    3. Configure the source and sink NEs of the PWE3 service.

      1. On the Node List tag page, click Configure Source And Sink. A dialog box is displayed.
      2. Select source and sink NEs in Physical Topology on the left.
      3. In SAI Configuration, set the parameters for the service port on NodeB 1 and click Add Node.
      Table 3-88  Parameters for the service port on NodeB 1
      Parameter Value in This Example
      Source ID 1
      VLAN ID 100
      Sink ID 1
      VLAN ID 100

    4. Click the PW tab, and set the general attributes for the PW on NodeB 1.

      Table 3-89  General attributes for the PW on NodeB 1
      Parameter Value in This Example
      PW ID 35
      Signaling Type Static
      Forward Label 20
      Reverse Label 20
      Forward Type Static Binding
      Forward Tunnel NE1_NE4_working
      Reverse Type Static Binding
      Reverse Tunnel NE1_NE4_working
      Encapsulation Type MPLS

    5. Click Detail and set the advanced attributes for the PW on NodeB 1.

      1. Click the PW QoS tab and set the QoS parameters for the PW on NodeB1.
        Table 3-90  QoS parameters for the PW on NodeB 1
        Parameter Value in This Example
        Forward Bandwidth Limited Enabled
        CIR(kbit/s) 10240
        PIR(kbit/s) 30720
        CBS(bytes) 30720
        PBS(bytes) 30720
        Reverse Bandwidth Limited Enabled
        CIR(kbit/s) 10240
        PIR(kbit/s) 30720
        CBS(bytes) 30720
        PBS(bytes) 30720
      2. Click the Advanced PW Attribute tab and set the advanced attributes for the PW on NodeB 1.
        Table 3-91  Advanced attributes for the PW on NodeB 1
        Parameter Value in This Example
        PW Type Ethernet Tagged Mode
        Request VLAN 10
        TPID 0x8100
        NOTE:

        For details on how to configure the TPID, see Configuring NE-Level TPID.

        Other parameters Default values
      3. Click the Service Parameter tab and set the service tags for NodeB 1.
        Table 3-92  Service tags for NodeB 1
        Parameter Value in This Example
        Source Service Tag User
        Sink Service Tag User

    6. Optional: If alarms are automatically configured after the configuration of services, click ETH OAM CC so that the connectivity check can be continuous.

      NOTE:

      E-Line services carried by PWs based on neither VLAN priorities nor VLAN switching support ETH OAM CC tests.

    7. Click OK.
  4. Configure data services on NodeB 2 in end-to-end mode.

    See 3 to configure data services on NodeB 2.

    Table 3-93  General attributes for the data services on NodeB 2
    Parameter Value in This Example
    Service Type ETH
    Service ID 2
    Service Name E-Line-2
    Protection Type Unprotected
    Table 3-94  Parameters for the service port on NodeB 2
    Parameter Value in This Example
    Source ID 2
    VLAN ID 100
    Sink ID 2
    VLAN ID 200
    Table 3-95  General attributes for the PW on NodeB 2
    Parameter Value in This Example
    PW ID 45
    Signaling Type Static
    Forward Label 30
    Reverse Label 30
    Forward Type Static Binding
    Forward Tunnel NE1_NE4_working
    Reverse Type Static Binding
    Reverse Tunnel NE1_NE4_working
    Encapsulation Type MPLS
    Table 3-96  QoS parameters for the PW on NodeB 2
    Parameter Value in This Example
    Forward Bandwidth Limited Enabled
    CIR(kbit/s) 30720
    PIR(kbit/s) 51200
    CBS(bytes) 51200
    PBS(bytes) 51200
    Reverse Bandwidth Limited Enabled
    CIR(kbit/s) 30720
    PIR(kbit/s) 51200
    CBS(bytes) 51200
    PBS(bytes) 51200
    Table 3-97  Advanced attributes for the PW on NodeB 2
    Parameter Value in This Example
    PW Type Ethernet Tagged Mode
    Request VLAN 20
    TPID 0x8100
    NOTE:

    For details on how to configure the TPID, see Configuring NE-Level TPID.

    Other parameters Default values
    Table 3-98  Service tags for NodeB 2
    Parameter Value in This Example
    Source Service Tag Service
    Sink Service Tag Service

Related Task

See Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by PWs are configured correctly.

Configuration Process (Configuration on a Per-NE Basis)

This topic describes the process for configuring the E-Line services carried by PWs.

Prerequisites

  • You must be familiar with the networking requirements and service planning information of the E-Line services carried by PWs (based on VLAN switching).
  • You are an NM user with Administrators rights or higher.

Procedure

  1. On NE1, NE2, NE3, and NE4, configure the tunnels that carry the PWs. For the configuration procedures, see Configuring an MPLS Tunnel.

    Table 3-99  Planning information of the LSR ID and port
    NE IP Address IP Mask LSR ID
    NE1 4-EM6F-1 18.1.1.1 255.255.255.252 130.0.0.1
    4-EM6F-2 18.1.2.1 255.255.255.252
    NE2 4-EM6F-1 18.1.1.2 255.255.255.252 130.0.0.2
    4-EM6F-2 18.1.1.5 255.255.255.252
    NE3 4-EM6F-1 18.1.2.2 255.255.255.252 130.0.0.3
    4-EM6F-2 18.1.2.5 255.255.255.252
    NE4 4-EM6F-1 18.1.1.6 255.255.255.252 130.0.0.4
    4-EM6F-2 18.1.2.6 255.255.255.252
    Table 3-100  Planning information of the tunnels
    Tunnel Tunnel ID Node Node Type In Interface In Label Reverse In Label Out Interface Out Label Reverse Out Label Next Hop Reverse Next Hop Source Node Sink Node
    Working Tunnel Auto-Assign NE1 Ingress - - 102 4-EM6F-1 100 - 18.1.1.2 - - 130.0.0.4
    NE2 Transit 4-EM6F-1 100 103 4-EM6F-2 101 102 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4
    NE4 Egress 4-EM6F-1 101 - - - 103 - 18.1.1.5 130.0.0.1 -
    Protection Tunnel Auto-Assign NE1 Ingress - - 202 4-EM6F-2 200 - 18.1.2.2 - - 130.0.0.4
    NE3 Transit 4-EM6F-1 200 203 4-EM6F-2 201 202 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4
    NE4 Egress 4-EM6F-2 201 - - - 203 - 18.1.2.5 130.0.0.1 -

  2. On NE1 and NE4, configure MPLS tunnel OAM. For the configuration procedures, see Configuring MPLS Tunnel OAM.

    Table 3-101  Parameter planning for MPLS tunnel OAM
    Parameter Parameter Planning
    OAM Status Enable Sending and Receiving Enable Sending and Receiving
    Detection Mode Manual Manual
    Detection Packet Type FFD
    NOTE:
    Detection Packet Period can be set only when Detection Packet Type is FFD.
    FFD
    Detection Packet Period (ms) 3.3
    NOTE:
    Generally, the OAM packet is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.
    3.3

  3. On NE1 and NE4, configure MPLS tunnel APS. For the configuration procedures, see Configuring Tunnel APS.

    Table 3-102  Parameter planning for MPLS tunnel APS
    Parameter Parameter Planning
    Protocol Status Enabled
    Revertive Mode Revertive
    WTR Time(min) 5
    Hold-off Time(100ms) 0
    NOTE:
    Services are not protected with multiple protection schemes. Therefore, the setting of Hold-off Time(100ms) is unnecessary.

  4. On NE1, configure an E-Line service for NodeB 1.
    1. In the NE Explorer, select NE1, and then choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
    2. Click New. Then, the New E-Line Service dialog box is displayed. Set the displayed parameters.

      Table 3-103  Parameters of the E-Line service carried by PWs of NodeB 1
      Parameter Value in This Example
      Service ID 1
      Service Name E-Line-1
      Direction UNI-NNI
      BPDU (STP Packet) Not Transparently Transmitted
      MTU (bytes) -
      Service Tag Role User
      Source Port 4-EM6F-3
      Source VLANs 100
      Bearer Type PW
      Protection Type Unprotected
      Other parameters Default values

    3. Click Configure PW. Then, the Configure PW dialog box is displayed. Set the PW parameters.

      Table 3-104  PW parameters of the E-Line service of NodeB 1
      Parameter Value in This Example
      General Attributes PW ID 35
      PW Signaling Type Static
      PW Type Ethernet Tagged Mode
      PW Direction Bidirectional
      PW Incoming Label/Source Port 20
      PW Outgoing Label/Sink Port 20
      Tunnel Type MPLS
      Tunnel NE1_NE4_working
      Peer LSR ID 130.0.0.4
      QoS Bandwidth Limit Enabled
      CIR(kbit/s) 10240
      PIR(kbit/s) 30720
      CBS(bytes) 30720
      PBS(bytes) 30720
      Other parameters Default values
      Advanced Attributes Request VLAN 10
      TPID

      0x8100

      NOTE:

      For details on how to configure the TPID, see Configuring NE-Level TPID.

      Other parameters Default values

  5. On NE1, configure an E-Line service for NodeB 2.

    Refer to 4 and configure an E-Line service for NodeB 2.

    Table 3-105  Parameters of the E-Line service carried by PWs of NodeB 2
    Parameter Value in This Example
    Service ID 2
    Service Name E-Line-2
    Direction UNI-NNI
    BPDU (STP Packet) Not Transparently Transmitted
    MTU (bytes) -
    Service Tag Role Service
    Source Port 4-EM6F-4
    Source VLANs 100
    Bearer Type PW
    Protection Type Unprotected
    Other parameters Default values
    Table 3-106  PW parameters of the E-Line service of NodeB 2
    Parameter Value in This Example
    General Attributes PW ID 45
    PW Signaling Type Static
    PW Type Ethernet Tagged Mode
    PW Direction Bidirectional
    PW Incoming Label/Source Port 30
    PW Outgoing Label/Sink Port 30
    Tunnel Type MPLS
    Tunnel NE1_NE4_working
    Peer LSR ID 130.0.0.4
    Advanced Attributes Request VLAN 20
    TPID

    0x8100

    NOTE:

    For details on how to configure the TPID, see Configuring NE-Level TPID.

    Other parameters Default values
    Table 3-107  QoS parameters of the E-Line service of NodeB 2
    Parameter Value in This Example
    PW ID 45
    Direction Ingress
    Bandwidth Limit Enabled
    CIR(kbit/s) 30720
    PIR(kbit/s) 51200
    CBS(bytes) 51200
    PBS(bytes) 51200
    Other parameters Default values

  6. On NE4, configure an E-Line service between NodeB 1 and the RNC, and an E-Line service between NodeB 2 and the RNC.

    Refer to 4 and configure the E-Line services.

    Table 3-108  Parameters of the E-Line service carried by PWs between NodeB 1 and the RNC
    Parameter Value in This Example
    Service ID 1
    Service Name E-Line-1
    Direction UNI-NNI
    BPDU (STP Packet) Not Transparently Transmitted
    MTU (bytes) -
    Service Tag Role User
    Source Port 4-EM6F-3
    Source VLANs 100
    Bearer Type PW
    Protection Type Unprotected
    Other parameters Default values
    Table 3-109  PW parameters of the E-Line service between NodeB 1 and the RNC
    Parameter Value in This Example
    General Attributes PW ID 35
    PW Signaling Type Static
    PW Type Ethernet Tagged Mode
    PW Direction Bidirectional
    PW Incoming Label/Source Port 20
    PW Outgoing Label/Sink Port 20
    Tunnel Type MPLS
    Tunnel NE1_NE4_working
    Peer LSR ID 130.0.0.1
    Advanced Attributes Request VLAN 10
    TPID

    0x8100

    NOTE:

    For details on how to configure the TPID, see Configuring NE-Level TPID.

    Other parameters Default values
    Table 3-110  QoS parameters of the E-Line service between NodeB 1 and the RNC
    Parameter Value in This Example
    PW ID 35
    Direction Ingress
    Bandwidth Limit Enabled
    CIR(kbit/s) 10240
    PIR(kbit/s) 30720
    CBS(bytes) 30720
    PBS(bytes) 30720
    Other parameters Default values
    Table 3-111  Parameters of the E-Line service carried by PWs between NodeB 2 and the RNC
    Parameter Value in This Example
    Service ID 2
    Service Name E-Line-2
    Direction UNI-NNI
    BPDU (STP Packet) Not Transparently Transmitted
    Service Tag Role Service
    MTU (bytes) -
    Source Port 4-EM6F-3
    Source VLANs 200
    Bearer Type PW
    Protection Type Unprotected
    Other parameters Default values
    Table 3-112  PW parameters of the E-Line service between NodeB 2 and the RNC
    Parameter Value in This Example
    General Attributes PW ID 45
    PW Signaling Type Static
    PW Type Ethernet Tagged Mode
    PW Direction Bidirectional
    PW Incoming Label/Source Port 30
    PW Outgoing Label/Sink Port 30
    Tunnel Type MPLS
    Tunnel NE1_NE4_working
    Peer LSR ID 130.0.0.1
    Advanced Attributes Request VLAN 20
    TPID

    0x8100

    NOTE:

    For details on how to configure the TPID, see Configuring NE-Level TPID.

    Other parameters Default values
    Table 3-113  QoS parameters of the E-Line service between NodeB 2 and the RNC
    Parameter Value in This Example
    PW ID 45
    Direction Ingress
    Bandwidth Limit Enabled
    CIR(kbit/s) 30720
    PIR(kbit/s) 51200
    CBS(bytes) 51200
    PBS(bytes) 51200
    Other parameters Default values

Relevant Task

See Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by PWs are configured correctly.

Verifying the Correctness of E-Line Service Configuration

After configuring E-Line services, verify the E-Line services by using the SmartBits.

Prerequisites

  • E-Line services carried by PWs are configured.
  • You are an NM user with Administrators rights or higher.
Tools, Equipment, and Materials

SmartBits and U2000

Test Connection Diagram

Figure 3-15 shows the connections for testing E-Line services carried by PWs.

Figure 3-15  Connections for testing E-Line services carried by PWs

NOTE:
In this example, the SmartBits devices are connected to 4-EM6F-3 on NE1 (source) and 4-EM6F-3 on NE3 (sink). In actual situations, determine the source and sink as required, and follow the same testing procedure.

Context

  • During a test, only test personnel are allowed in the testing environment.
  • Exercise caution when touching cables and optical fibers.

Procedure

  1. Connect the SmartBits devices to 4-EM6F-3 on NE1 and 4-EM6F-3 on NE3.
  2. Log in to the U2000. See Enabling NE Performance Monitoring to start the 15-minute and 24-hour performance monitoring on NE1 and NE3.

    NOTE:
    The performance monitoring tasks help analyze and locate a problem during the test.

  3. Use the SmartBits devices to perform a packet transmitting and receiving test.

    NOTE:
    • Packets whose bytes are all 0s are considered as special packets. Do not use those packets for a packet transmitting and receiving test.
    • In the first packet transmitting and receiving period, learning the MAC addresses of the packets may cause packet loss.
    • If the service is normal, the number of received packets is equal to the number of transmitted packets. If it is a VLAN-based service that involves VLAN switching, check whether VLAN switching functions properly for transmitted and received packets.
    • If packet loss occurred, rectify the fault. Then, perform 24-hour tests until no packet loss occurs.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020976

Views: 45858

Downloads: 383

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