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 (QinQ-Based E-Line Service)

Configuration Example (QinQ-Based E-Line Service)

This section considers a QinQ-based E-line service as an example to describe how to configure the Ethernet service according to the network planning information.

Networking Diagram

This section describes the networking information about the NEs.

Configure Ethernet services according to the following requirements:

  • NodeB11 to NodeB15 provide FE ports whose port rate is 100 Mbit/s.
  • The VLAN ID used by the services on a NodeB is allocated by the RNC that controls the NodeB. Therefore, the VLAN IDs of services on NodeBs that are controlled by different RNCs may be the same. To solve this problem, an RNC allocates an S-VLAN ID for each NodeB, and the S-VLAN IDs on the entire network are planned in a unified manner.
  • VLAN priorities are configured on each NodeB according to service types.

To meet the preceding requirements, QinQ-based E-Line services are configured for service transmission on each NE; in addition, corresponding QoS processing is configured.

Figure 3-37  Networking diagram (QinQ-based E-Line services)

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.

The connections of Ethernet links shown in Figure 3-37 are described as follows.

Table 3-200  Connections of Ethernet links
NE Link Port Description
NE11 Between NE11 and the RNC 3-EM6T-1 Configure this port to transmit backhaul services from NodeBs.
Between NE11 and NE12 3-EM6T-2

Configure this port to transmit Native Ethernet services.

NE12 Between NE12 and NE13 3-EM6T-1 Configure this port to transmit backhaul services from NodeBs.
Between NE12 and NE11 3-EM6T-2

Configure this port to transmit Native Ethernet services.

Between NE12 and NodeB11 3-EM6T-3 Configure this port to access services from NodeB11.
NE13 Between NE13 and NE14 3-EM6T-1

Configure this port to transmit Native Ethernet services.

Between NE13 and NE15 3-EM6T-2

Configure this port to transmit Native Ethernet services.

Between NE13 and NE12 4-EM6T-1 Configure this port to transmit backhaul services from NodeBs.
NE14 Between NE14 and NE13 3-EM6T-1 Configure this port to transmit Native Ethernet services.
Between NE14 and NodeB12 3-EM6T-3 Configure this port to access services from NodeB12.
NE15 Between NE15 and NE16 3-EM6T-1 Configure this port to transmit Native Ethernet services.
Between NE15 and NE13 3-EM6T-2 Configure this port to transmit Native Ethernet services.
NE16 Between NE16 and NE15 3-EM6T-1 Configure this port to transmit Ethernet services.
Between NE16 and NodeB15 3-EM6T-3 Configure this port to access services from NodeB15.

Service Planning

You need to plan the corresponding parameter information before configuring an Ethernet service.

Service Planning (Ethernet Ports)

The service planning information contains the information about all the parameters required for configuring Ethernet ports.

NOTE:
  • In this example, the FE ports on all the NodeBs work in auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation.
  • In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1620 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.
  • Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends.
  • In this example, all the NNI ports are connected to Huawei equipment. Therefore, the QinQ type domain of the NNI ports assumes the default value of 0x88a8.
Table 3-201  Information about Ethernet ports
Parameter Value
NE NE11 NE12 NE13 NE14 NE15 NE16
Port

3-EM6T-2

3-EM6T-1

3-EM6T-1

3-EM6T-2

3-EM6T-3

3-EM6T-1

3-EM6T-2

4-EM6T-1

3-EM6T-1

3-EM6T-3

3-EM6T-1

3-EM6T-2

3-EM6T-1

3-EM6T-3

Encapsulation type QinQ QinQ 802.1Q QinQ QinQ 802.1Q QinQ QinQ 802.1Q
Port working mode Auto-negotiation
Max Frame Length (bytes) 1620
Flow control Disabled
Tag attribute Tag Aware
QinQ type domain 0x88a8 0x88a8 - 0x88a8 0x88a8 - 0x88a8 0x88a8 -
Service Planning (Ethernet Services)

The service planning information contains the information about all the parameters required for configuring Ethernet services.

Parameter Value
NE NE11 NE12 NE13 NE14 NE15 NE16
NodeB12 to RNC NodeB11 to RNC NodeB15 to RNC NodeB11 to NE11 NodeB12 to NE11 NodeB15 to NE11 NodeB12 to NE12 NodeB15 to NE12 NodeB12 to NE13 NodeB15 to NE13 NodeB15 to NE15
Service ID 1 2 3 1 2 3 1 2 1 1 1
Service name NodeB12toRNC_Qline NodeB11toRNC_Qline NodeB15toRNC2_Qline NodeB11toNE11_Qline NodeB12toNE11_Qline NodeB15toNE11_Qline NodeB12toNE12_Qline NodeB15toNE12_Qline NodeB12toNE13_Qline NodeB15toNE13_Qline NodeB15toNE15_Qline
Service direction UNI-NNI
BPDU Not transparently transmitted
Source port 3-EM6T-2 3-EM6T-2 3-EM6T-2 3-EM6T-3 - - - - 3-EM6T-1 - 3-EM6T-3
Source VLANs - - - - - - - - - - -
QinQ link (source) - - - -

ID: 2

Port: 3-EM6T-1

SVLAN: 201

ID: 4

Port: 3-EM6T-1

SVLAN: 202

ID: 1

Port: 3-EM6T-1

SVLAN: 201

ID: 3

Port: 3-EM6T-2

SVLAN: 202

-

ID: 1

Port: 3-EM6T-1

SVLAN: 202

-
QinQ link (sink)

ID: 1

Port: 3-EM6T-1

SVLAN: 201

ID: 2

Port: 3-EM6T-1

SVLAN: 200

ID: 3

Port: 3-EM6T-1

SVLAN: 202

ID: 1

Port: 3-EM6T-2

SVLAN: 200

ID: 3

Port: 3-EM6T-2

SVLAN: 201

ID: 5

Port: 3-EM6T-2

SVLAN: 202

ID: 2

Port: 4-EM6T-1

SVLAN: 201

ID: 4

Port: 4-EM6T-1

SVLAN: 202

ID: 1

Port: 3-EM6T-1

SVLAN: 201

ID: 2

Port: 3-EM6T-2

SVLAN: 202

ID: 1

Port: 3-EM6T-1

SVLAN: 202

Service Planning (QoS)

The service planning information contains the information about all the parameters required for configuring QoS.

QoS (Diffserv)

DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the NodeB services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration.

In this example, the NodeB services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 3-202. Each Ethernet port involved in the service uses the same DS configuration.

Table 3-202  Service class and PHB service class
PHB Service Class VLAN Priority Corresponding Service Type
CS7 7 -
CS6 6 -
EF 5 Real-time voice service and signaling service (R99 conversational and R99 streaming services)
AF4 4 -
AF3 3 Real-time OM and HSDPA services (OM streaming and HSPA streaming services)
AF2 2 Non-real-time R99 service (R99 interactive and R99 background services)
AF1 1 -
BE 0 HSDPA data service (HSPA interactive and background services)
NOTE:
  • During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
  • The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified.
  • The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority and therefore needs to be modified as required.
QoS (Queue Scheduling Mode)

Generally, all Ethernet port involved in the service use the same queue scheduling mode.

Table 3-203 lists the queue scheduling mode used by each Ethernet port involved in the service in this example.

Table 3-203  Queue scheduling mode
PHB Service Class Queue Scheduling Mode
CS7 SP
CS6 SP
EF SP
AF4 WRR (weight = 5)
AF3 WRR (weight = 60)
AF2 WRR (weight = 30)
AF1 WRR (weight = 5)
BE SP
QoS (CAR or Shaping for a Specified Service Flow)

Normally, flow control is already performed on 2G/3G base stations and BSCs/RNCs and therefore CAR or shaping processing does not need to be performed again on the backhaul network.

QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the aggregation services, you can perform port shaping at the edge node to limit the Ethernet service traffic that travels to the aggregation node, preventing congestion at the aggregation node.

In this example, you do not need to perform port shaping.

Configuration Process (in End-to-End Mode)

This section describes how to configure service parameters in end-to-end mode.

Configuration Process (Ethernet Ports)

This section describes the process for configuring Ethernet ports.

Procedure

  1. See Setting the General Attributes of Ethernet Interfaces and set the basic attributes of Ethernet ports.

    Parameter Value
    NE NE11 NE12 NE13

    NE14

    NE16

    NE15
    Port

    3-EM6T-2

    3-EM6T-1

    3-EM6T-1

    3-EM6T-2

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-1

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    Enable Port Enabled
    Encapsulation Type QinQ QinQ 802.1Q QinQ QinQ 802.1Q QinQ
    Working Mode Auto-Negotiation
    Max Frame Length(bytes) 1620

  2. See Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of Ethernet ports

    Parameter Value
    NE NE11 NE12 NE13

    NE14

    NE16

    NE15
    Port

    3-EM6T-2

    3-EM6T-1

    3-EM6T-1

    3-EM6T-3

    3-EM6T-2

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-3

    3-EM6T-1

    3-EM6T-1

    3-EM6T-2

    TAG Tag Aware

Configuration Process (Service Information)

This section describes the process for configuring service information.

Procedure

  1. See Creating E-Line Services over Native Ethernet in End-to-End Mode to configure Ethernet services between the RNC and NodeB11.

    Table 3-204  Basic attributes of Ethernet services between the RNC and NodeB11
    Parameter Value
    Service Name NodeB11toRNC_Vline
    BPDU Private Service No
    Customer Empty
    Remarks Empty
    Table 3-205  Source and sink parameters of Ethernet services between the RNC and NodeB11
    Parameter Value
    NE12 NE11
    Location Source Sink
    Node NE12 NE11
    Interface 3-EM6T-3 3-EM6T-1
    C-VLAN Empty Empty
    S-VLAN 200 200
    Table 3-206  Explicit node parameters of Ethernet services between the RNC and NodeB11
    Parameter Value
    NE12 NE11
    NE NE12 NE11
    In Interface 3-EM6T-3 3-EM6T-2
    In C-VLAN Empty Empty
    In S-VLAN 200 200
    Out Interface 3-EM6T-2 3-EM6T-1
    Out C-VLAN Empty Empty
    Out S-VLAN 200 200
    MTU (bytes) - -
    Service Tag User User

  2. Repeat 1 to configure Ethernet services between the RNC and NodeB12.

    Table 3-207  Basic attributes of Ethernet services between the RNC and NodeB12
    Parameter Value
    Service Name NodeB12toRNC_Vline
    BPDU Private Service No
    Customer Empty
    Remarks Empty
    Table 3-208  Source and sink parameters of Ethernet services between the RNC and NodeB12
    Parameter Value
    NE14 NE11
    Location Source Sink
    Node NE14 NE11
    Interface 3-EM6T-3 3-EM6T-1
    C-VLAN Empty Empty
    S-VLAN 201 201
    Table 3-209  Explicit node parameters of Ethernet services between the RNC and NodeB12
    Parameter Value
    NE14 NE13 NE12 NE11
    NE NE14 NE13 NE12 NE11
    In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-1 3-EM6T-2
    In C-VLAN Empty Empty Empty Empty
    In S-VLAN 201 201 201 201
    Out Interface 3-EM6T-1 4-EM6T-1 3-EM6T-2 3-EM6T-1
    Out C-VLAN Empty Empty Empty Empty
    Out S-VLAN 201 201 201 201
    MTU (bytes) - - - -
    Service Tag User User User User

  3. Repeat 1 to configure Ethernet services between the RNC and NodeB15.

    Table 3-210  Basic attributes of Ethernet services between the RNC and NodeB15
    Parameter Value
    Service Name NodeB15toRNC_Vline
    BPDU Private Service No
    Customer Empty
    Remarks Empty
    Table 3-211  Source and sink parameters of Ethernet services between the RNC and NodeB15
    Parameter Value
    NE16 NE11
    Location Source Sink
    Node NE16 NE11
    Interface 3-EM6T-3 3-EM6T-1
    C-VLAN Empty Empty
    S-VLAN 202 202
    Table 3-212  Explicit node parameters of Ethernet services between the RNC and NodeB15
    Parameter Value
    NE16 NE15 NE13 NE12 NE11
    NE NE14 NE15 NE13 NE12 NE11
    In Interface 3-EM6T-3 3-EM6T-1 3-EM6T-2 3-EM6T-1 3-EM6T-2
    In C-VLAN Empty Empty Empty Empty Empty
    In S-VLAN 202 202 202 202 202
    Out Interface 3-EM6T-1 3-EM6T-2 4-EM6T-1 3-EM6T-2 3-EM6T-1
    Out C-VLAN Empty Empty Empty Empty Empty
    Out S-VLAN 202 202 202 202 202
    MTU (bytes) - - - - -
    Service Tag User User User User User

Configuration Process (QoS)

This section describes the procedures for configuring QoS.

Procedure

  1. OptiX OSN 500/550 see Modifying the Mapping Relationships for the DS Domain, OptiX OSN 580 see Modifying the Mapping Relationships for the DS Domain, and change the mapping relationships for the DS domain.

    The values for the required parameters that are set in the main interface are as follows.

    Parameter Value
    Mapping Relation ID 2
    Mapping Relation Name Default Map 2

    The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows.

    CVLAN SVLAN IP DSCP MPLS EXP PHB
    0 0 Default value Default value BE
    1 1 AF11
    2 2 AF21
    3 3 AF31
    4 4 AF41
    5 5 EF
    6 6 CS6
    7 7 CS7

    The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows.

    PHB CVLAN SVLAN IP DSCP MPLS EXP
    BE 0 0 Default value Default value
    AF11 1 1
    AF21 2 2
    AF31 3 3
    AF41 4 4
    EF 5 5
    CS6 6 6
    CS7 7 7
    NOTE:
    • The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
    • The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified.

  2. OptiX OSN 500/550 see Changing the Ports in a DS Domain, OptiX OSN 580 see Changing the Ports Applied to a DS Domain and Their Trusted Packet Types, and change the ports that are applied to the DS domain and their trusted packet type.

    NE Selected Port Packet Type

    NE11

    NE15

    3-EM6T-2 SVLAN
    3-EM6T-1 SVLAN
    NE12 3-EM6T-3 CVLAN
    3-EM6T-1 SVLAN
    3-EM6T-2 SVLAN
    NE13 3-EM6T-1 SVLAN
    3-EM6T-2 SVLAN
    4-EM6T-1 SVLAN

    NE14

    NE16

    3-EM6T-3 CVLAN
    3-EM6T-1 SVLAN

  3. OptiX OSN 500/550 see Creating a Port Policy, OptiX OSN 580 see Creating a Port Policy, and create the port policy.

    The values for the related parameters of NE11 to NE16 are provided as follows.

    Parameter Value
    Policy ID 1
    Policy Name Port_Comm
    Grooming Police After Reloading

    SP (CS7, CS6, and EF)

    WRR (AF4 to AF1)

    SP (BE)

    Policy Weight(%)

    5 (AF4)

    60 (AF3)

    30 (AF2)

    5 (AF1)

    Bandwidth Limit

    Disabled (for all PHB service classes)

  4. OptiX OSN 500/550 see Setting the Port That Uses the Port Policy, OptiX OSN 580 see Setting the Port That Uses the Port Policy, and set the ports that use the port policy.

    Parameter Port_Comm (Policy ID=1)
    NE

    NE11

    NE15

    NE12 NE13

    NE14

    NE16

    Port

    3-EM6T-1

    3-EM6T-2

    3-EM6T-1

    3-EM6T-2

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-1

    3-EM6T-3

Configuration Process (Verifying Ethernet Service Configurations)

This section describes the process for verifying Ethernet service configurations.

Procedure

  1. See Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.

    The values for the required parameters are provided as follows.

    Parameter Value
    NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Domain Level 4 4 4 4

  2. See Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Relevant Service 1-NodeB11_Qline 2-NodeB12_Qline 5-NodeB15_Qline 1-NodeB11_Qline 1-NodeB12_Qline 1-NodeB15_Qline
    CC Test Transmit Period 1s 1s 1s 1s 1s 1s

  3. See Creating an MEP Point and create the MEPs.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Board 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T
    Port 3-EM6T-1 3-EM6T-1 3-EM6T-1 3-EM6T-3 3-EM6T-3 3-EM6T-3
    VLAN 100 110 140 - - -
    MEP ID 1 2 3 4 5 6
    Direction Ingress Ingress Ingress Ingress Ingress Ingress
    CC Status Active Active Active Active Active Active

  4. See Creating Remote MEPs in an MA and create the remote MEPs of the MA for NE11, NE12, NE14, and NE16.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Remote Maintenance Point ID(e.g:1,3-6) 4 5 6 1 2 3

  5. On NE1, perform LB tests to test the Ethernet service configurations.

    • Perform the LB test by considering the MEP whose MEP ID is 4 as the source MEP and the MEP whose MEP ID is 1 as the sink MEP.
    • Perform the LB test by considering the MEP whose MEP ID is 5 as the source MEP and the MEP whose MEP ID is 2 as the sink MEP.
    • Perform the LB test by considering the MEP whose MEP ID is 6 as the source MEP and the MEP whose MEP ID is 3 as the sink MEP.


    No packet loss occurs.

Per-NE Configuration Process

This section describes the process for data configuration on a per-NE basis.

Configuration Process (Ethernet Ports)

This section describes the process for configuring Ethernet ports.

Procedure

  1. See Setting the General Attributes of Ethernet Interfaces and set the basic attributes of Ethernet ports.

    Parameter Value
    NE NE11 NE12 NE13

    NE14

    NE16

    NE15
    Port

    3-EM6T-2

    3-EM6T-1

    3-EM6T-1

    3-EM6T-2

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-1

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    Enable Port Enabled
    Encapsulation Type QinQ QinQ 802.1Q QinQ QinQ 802.1Q QinQ
    Working Mode Auto-Negotiation
    Max Frame Length(bytes) 1620

  2. See Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of Ethernet ports

    Parameter Value
    NE NE11 NE12 NE13

    NE14

    NE16

    NE15
    Port

    3-EM6T-2

    3-EM6T-1

    3-EM6T-1

    3-EM6T-3

    3-EM6T-2

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-3

    3-EM6T-1

    3-EM6T-1

    3-EM6T-2

    TAG Tag Aware

Configuration Process (Service Information)

This section describes the process for configuring service information.

Procedure

  1. See Creating a QinQ Link and configure a QinQ link.

    NE QinQ Link ID Board Port S-Vlan ID
    NE11 1 3-EM6T 1 201
    2 3-EM6T 1 200
    3 3-EM6T 1 202
    NE12 1 3-EM6T 2 200
    2 3-EM6T 1 201
    3 3-EM6T 2 201
    4 3-EM6T 1 202
    5 3-EM6T 2 202
    NE13 1 3-EM6T 1 201
    2 4-EM6T 1 201
    3 3-EM6T 2 202
    4 4-EM6T 1 202
    NE14 1 3-EM6T 1 201
    NE15 1 3-EM6T 1 202
    2 3-EM6T 2 202
    NE16 1 3-EM6T 1 202

  2. See Configuring NNI-NNI E-Line Services and configure NNI-NNI E-Line services. The method for configuring UNI-NNI E-Line services is the same as that for configuring NNI-NNI E-Line services.

    NOTE:
    Set Bearer Type to QinQ Link.
    Parameter Value
    NE NE11 NE12 NE13 NE14 NE15 NE16
    NodeB12 to the RNC NodeB11 to the RNC NodeB15 to the RNC NodeB11 to NE11 NodeB12 to NE11 NodeB15 to NE11 NodeB12 to NE12 NodeB15 to NE12 NodeB12 to NE13 NodeB15 to NE13 NodeB15 to NE15
    Service ID 1 2 3 1 2 3 1 2 1 1 1
    Service Name NodeB12toRNC_Qline NodeB11toRNC_Qline NodeB15toRNC_Qline NodeB11toNE11_Qline NodeB12toNE11_Qline NodeB15toNE11_Qline NodeB12toNE12_Qline NodeB15toNE12_Qline NodeB12toNE13_Qline NodeB15toNE13_Qline NodeB15toNE15_Qline
    Direction UNI-NNI UNI-NNI UNI-NNI UNI-NNI NNI-NNI NNI-NNI NNI-NNI NNI-NNI UNI-NNI NNI-NNI UNI-NNI
    BPDU Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted Not Transparently Transmitted
    Source Port 3-EM6T-2 3-EM6T-2 3-EM6T-2 3-EM6T-3 - - - - 3-EM6T-3 - 3-EM6T-3
    Source VLANs - - - - - - - - - - -
    QinQ Link ID 1 2 3 1 - - - - 1 - 1
    QinQ Link ID 1 - - - - 2 4 1 3 - 1 -
    QinQ Link ID 2 - - - - 3 5 2 4 - 2 -
    Bearer Type 1 - - - - QinQ Link QinQ Link QinQ Link QinQ Link - QinQ Link -
    Bearer Type 2 - - - - QinQ Link QinQ Link QinQ Link QinQ Link - QinQ Link -
    Bearer Type QinQ Link QinQ Link QinQ Link QinQ Link - - - - QinQ Link - QinQ Link
    MTU (bytes) - - - - - - - - - - -
    Service Tag Role - - - - - - - - - - -

Configuration Process (QoS)

This section describes the procedures for configuring QoS.

Procedure

  1. OptiX OSN 500/550 see Modifying the Mapping Relationships for the DS Domain, OptiX OSN 580 see Modifying the Mapping Relationships for the DS Domain, and change the mapping relationships for the DS domain.

    The values for the required parameters that are set in the main interface are as follows.

    Parameter Value
    Mapping Relation ID 2
    Mapping Relation Name Default Map 2

    The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows.

    CVLAN SVLAN IP DSCP MPLS EXP PHB
    0 0 Default value Default value BE
    1 1 AF11
    2 2 AF21
    3 3 AF31
    4 4 AF41
    5 5 EF
    6 6 CS6
    7 7 CS7

    The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows.

    PHB CVLAN SVLAN IP DSCP MPLS EXP
    BE 0 0 Default value Default value
    AF11 1 1
    AF21 2 2
    AF31 3 3
    AF41 4 4
    EF 5 5
    CS6 6 6
    CS7 7 7
    NOTE:
    • The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
    • The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified.

  2. OptiX OSN 500/550 see Changing the Ports in a DS Domain, OptiX OSN 580 see Changing the Ports Applied to a DS Domain and Their Trusted Packet Types, and change the ports that are applied to the DS domain and their trusted packet type.

    NE Selected Port Packet Type

    NE11

    NE15

    3-EM6T-2 SVLAN
    3-EM6T-1 SVLAN
    NE12 3-EM6T-3 CVLAN
    3-EM6T-1 SVLAN
    3-EM6T-2 SVLAN
    NE13 3-EM6T-1 SVLAN
    3-EM6T-2 SVLAN
    4-EM6T-1 SVLAN

    NE14

    NE16

    3-EM6T-3 CVLAN
    3-EM6T-1 SVLAN

  3. OptiX OSN 500/550 see Creating a Port Policy, OptiX OSN 580 see Creating a Port Policy, and create the port policy.

    The values for the related parameters of NE11 to NE16 are provided as follows.

    Parameter Value
    Policy ID 1
    Policy Name Port_Comm
    Grooming Police After Reloading

    SP (CS7, CS6, and EF)

    WRR (AF4 to AF1)

    SP (BE)

    Policy Weight(%)

    5 (AF4)

    60 (AF3)

    30 (AF2)

    5 (AF1)

    Bandwidth Limit

    Disabled (for all PHB service classes)

  4. OptiX OSN 500/550 see Setting the Port That Uses the Port Policy, OptiX OSN 580 see Setting the Port That Uses the Port Policy, and set the ports that use the port policy.

    Parameter Port_Comm (Policy ID=1)
    NE

    NE11

    NE15

    NE12 NE13

    NE14

    NE16

    Port

    3-EM6T-1

    3-EM6T-2

    3-EM6T-1

    3-EM6T-2

    3-EM6T-3

    3-EM6T-1

    3-EM6T-2

    4-EM6T-1

    3-EM6T-1

    3-EM6T-3

Verifying Ethernet Service Configurations

This section describes the process for verifying Ethernet service configurations.

Procedure

  1. See Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.

    The values for the required parameters are provided as follows.

    Parameter Value
    NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Domain Level 4 4 4 4

  2. See Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Relevant Service 1-NodeB11_Qline 2-NodeB12_Qline 5-NodeB15_Qline 1-NodeB11_Qline 1-NodeB12_Qline 1-NodeB15_Qline
    CC Test Transmit Period 1s 1s 1s 1s 1s 1s

  3. See Creating an MEP Point and create the MEPs.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Board 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T 3-EM6T
    Port 3-EM6T-1 3-EM6T-1 3-EM6T-1 3-EM6T-3 3-EM6T-3 3-EM6T-3
    VLAN 100 110 140 - - -
    MEP ID 1 2 3 4 5 6
    Direction Ingress Ingress Ingress Ingress Ingress Ingress
    CC Status Active Active Active Active Active Active

  4. See Creating Remote MEPs in an MA and create the remote MEPs of the MA for NE11, NE12, NE14, and NE16.

    Parameter Value
    NE NE11 NE12 NE14 NE16
    Maintenance Domain Name EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE
    Maintenance Association Name 11_Qline 12_Qline 15_Qline 11_Qline 12_Qline 15_Qline
    Remote Maintenance Point ID(e.g:1,3-6) 4 5 6 1 2 3

  5. On NE1, perform LB tests to test the Ethernet service configurations.

    • Perform the LB test by considering the MEP whose MEP ID is 4 as the source MEP and the MEP whose MEP ID is 1 as the sink MEP.
    • Perform the LB test by considering the MEP whose MEP ID is 5 as the source MEP and the MEP whose MEP ID is 2 as the sink MEP.
    • Perform the LB test by considering the MEP whose MEP ID is 6 as the source MEP and the MEP whose MEP ID is 3 as the sink MEP.


    No packet loss occurs.
Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020976

Views: 50162

Downloads: 409

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