Professional Documents
Culture Documents
(Packet Domain)
ISSUE 1.10
OptiX RTN 900 Data Configuration(Packet Domain) Contents
Contents
Course Instruction ........................................................................................................................1
About this course .........................................................................................................................1
Course objectives ........................................................................................................................1
Relevant Materials .......................................................................................................................1
Chapter 1 MPLS Tunnels Configuration ......................................................................................2
1.1 Configuring LSR IDs ..............................................................................................................2
1.2 Configuring NNI Port Parameters (Ethernet Port) .................................................................3
1.3 Configuring NNI Port Parameters (IF Port)............................................................................5
1.4 Creating MPLS Tunnels .........................................................................................................6
1.5 Configuring MPLS Protection ................................................................................................8
Chapter 2 CES Services Configuration ......................................................................................10
2.1 Configuring MPLS Tunnels ................................................................................................. 10
2.2 Configuring UNI Port Parameters ....................................................................................... 11
2.3 Creating CES Services ....................................................................................................... 13
2.4 (Optional) Configuring PW APS .......................................................................................... 14
2.5 Configuring MS-PW CES Services ..................................................................................... 15
Chapter 3 ATM/IMA Services Configuration ..............................................................................16
3.1 Configuring MPLS Tunnels ................................................................................................. 16
3.2 Configuring UNI Port Parameters ....................................................................................... 16
3.3 Configuring IMA Groups ..................................................................................................... 18
3.4 Configuring ATM QoS ......................................................................................................... 20
3.5 Configuring ATM Services .................................................................................................. 22
Chapter 4 E-LINE and E-AGGR Services Carried by PWs Configuration ................................ 24
4.1 Configuring E-Line Services Carried by PWs ..................................................................... 25
4.2 Configuring QoS ................................................................................................................. 27
4.3 Configuring E-AGGR Services Carried by PWs ................................................................. 29
Task1 MPLS Tunnel Configuration ............................................................................................ 31
1. Knowledge requirement .................................................................................................... 31
2. Scenario description .......................................................................................................... 31
3. Configuration requirement ................................................................................................. 31
Task2 CES Services Configuration ............................................................................................ 32
1. Knowledge requirement .................................................................................................... 32
2. Scenario description .......................................................................................................... 32
3. Configuration requirement ................................................................................................. 32
Task3 Fractional CES Services Configuration ...........................................................................33
1. Knowledge requirement .................................................................................................... 33
2. Scenario description .......................................................................................................... 33
3. Configuration requirement ................................................................................................. 33
Task4 MS-PW-based CES Services Configuration ...................................................................34
1. Knowledge requirement .................................................................................................... 34
Course Instruction
Course objectives
Upon completion of this course, you will be able to:
Configure Packet services of the OptiX RTN 900 via NMS
Relevant Materials
Configuration guide of OptiX RTN 900 product manual
Step Action
LSR ID: Specifies or displays the LSR ID of an NE. On a PSN, each NE is assigned a
unique LSR ID. This parameter must be set in IPv4 address format. The LSR ID
should be in different IP range of NE IP and NNI Port IP.
Start of Global Label Space: The OptiX RTN 900 supports a step of 2048. The
start value of a global label space is the smallest unicast tunnel label. When Start
of Global Label Space is 0, the smallest unicast tunnel label is 16, with values 0 to
15 reserved. On an MPLS-enabled network, global label spaces of NEs are
recommended to overlap each other if possible.
Step Action
2 Ethernet Interface: When Port Mode is set to Layer 3, Encapsulation Type can be
set to 802.1Q only. In this case, the port can be used to carry tunnels. You need to
configure tunnels when you create PW-carried Ethernet, CES, or ATM services.
Enable Tunnel: If Enable Tunnel is set Enabled, a port identifies and processes MPLS
labels. Enable Tunnel is available if you set Port Mode to Layer 3 in the General
Attributes tab.
Specify IP Address: The value Unspecified indicates that the IP addresses do not
need to be configured. The value Manually indicates that the IP address of the port
can be manually configured.
IP Address: This parameter is available when Specify IP Address is Manually. The IP
addresses of different ports on the NE cannot be in the same network segment, but
the IP addresses of the ports at both ends of a fiber must be in the same network
segment.
Step Action
Step Action
Tunnel ID: The total number of tunnels and PWs must be equal to or less than
1024. The number of tunnels that carry PWs is not included in the total.
Node Type: If the value is Ingress in the forward direction, the value is Egress for
the reverse direction. If value is Transit in the forward direction, the value is Transit
for the reverse direction.
CIR(kbit/s): Specifies the committed information rate (CIR) of a tunnel. Generally,
it is recommended that you set this parameter to No Limit. If you need to enable
the CES CAC function or limit the PW bandwidth, set this parameter to be the same
as the planned tunnel bandwidth.
In Board/Logic Interface Type: Specifies the board where the ingress port of a
forward tunnel is located.
In Port: Specifies the ingress port of a forward tunnel, which is also the egress port
of the mapping reverse tunnel.:
Forward In Label: Specifies the MPLS label that data carries when entering a
forward tunnel. This parameter can be set for only egress and transit nodes.
Reverse Out Label: Specifies the MPLS label that data carries when leaving a
reverse tunnel. This parameter can be set for only ingress and transit nodes.
Tunnel Type: The value E-LSP indicates that the EXP field is used to identify packet
scheduling priorities of PWs. An E-LSP tunnel can contain PWs of eight packet
scheduling priorities. The value L-LSP indicates that the MPLS label value is used to
identify packet scheduling priorities of PWs. An L-LSP tunnel can contain PWs of
the same packet scheduling priority.
EXP: This parameter cannot be set if Node Type is Transit. If this parameter is set
to a value from 0 to 7, the EXP field assumes the fixed value. If this parameter
takes the default value None, the EXP field is set based on the DiffServ mappings
Step Action
2 Protection Type: The OptiX RTN 900 supports only the value 1:1.
Switching Mode: The value Single-End indicates that services are switched only
in the direction where faults occur. The value Dual-End indicates that services
are switched to the protection channel in both directions when faults occur. The
value Dual-End is recommended.
BDI Status: This parameter is available only when Switching Mode is set to
Single-End. If BDI Status is set to Enabled, the egress node notifies the ingress
node of any detected faults by sending BDI packets; upon receiving BDI packets,
the ingress node triggers the protection switching.
Revertive Mode: can be set to Non-Revertive or Revertive.
Hold-off Time(100ms): The unit of this parameter is 100 milliseconds. The
value can be set from 0 to 100 (that is, 0 to 10 seconds).
Protocol Status: During the creation of a protection group, set Protocol Status
to Disabled. After the APS protection group is configured at both ends, set
Protocol Status to Enabled.
Step Action
1 NOTES: On a PSN network, an MPLS tunnel carries PWs where various services are
encapsulated. In this manner, data packets can be transparently transmitted
between NEs. An MPLS tunnel can carry several PWs. Before configuring a service,
you need to configure the MPLS tunnel that carries the service.
Step Action
Port Mode: When this parameter is set to Layer 1, the port can transmit TDM
signals. A port can transmit CES and serial services only if this parameter is set to
Layer 1. When this parameter is set to Layer 2, the port can transmit ATM signals.
For a PDH port, this parameter cannot be set to Layer 3.
Encapsulation Type: When Port Mode is Layer 1, Encapsulation Type takes its
default value Null. When Port Mode is Layer 2, Encapsulation Type takes its default
value ATM.
Frame Format: If a CES service uses the emulation mode of CESoPSN, this
parameter can assume the value CRC-4 Multiframe or Double Frame. The value
CRC-4 Multiframe is recommended. If a CES service uses the emulation mode of
SAToP, this parameter needs to assume the value Unframe. The value of Frame
Format must be the same at the local and opposite ends.
Clock Mode:
Master Mode: The system clock is used as the output clock of services.
Slave Mode: The CES ACR clock is used as the output clock of services. The
port inputting E1 clocks on Slave is set to Slave Mode.
System Clock Mode: The upstream E1 line clock of the opposite equipment is
used as the output clock of services. The port inputting E1 clocks on Master is
set to System Clock Mode.
Frame Mode:
30 timeslots: In an E1 frame format, timeslots 1 to 15 and 17 to 31 are used to
transmit service data, and timeslot 16 is used to transmit signaling.
31 timeslots: In an E1 frame format, timeslots 1 to 31 are used to transmit
service data.
This parameter is unavailable if Frame Format is Unframe. The port frame modes
need to be the same at the local and opposite ends.
Step Action
Mode: The value UNI-NNI indicates that the CES service is carried by a PW.
Therefore, the information about the PW needs to be configured.
Source Low Channel (e.g.1,3-6): If Level is set to E1, this parameter indicates the
E1 port where the service source is located. If Mode is set to UNI-NNI, this
parameter can assume only one value.
Source 64K Timeslot (e.g.1,3-6): This parameter can assume multiple values. The
values of this parameter must include 16 if Frame Mode is 30. On the two ends of a
radio link, the timeslot lists can be different but the numbers of timeslots must the
same. This parameter does not need to be set if Mode is UNI-NNI and PW Type is
SAToP.
PW Type: CESoPSN Indicates structure-aware TDM circuit emulation service over
packet switched network. Timeslot compression can be set; SAToP Indicates
structure-agnostic TDM over packet. Timeslot compression cannot be set.
Protection Type: If this parameter is set to PW APS, working and protection PWs
need to be configured. When this parameter is set to Slave Protection Pair, you
need to bind the slave PW APS protection group with the master PW APS
protection group. The switching of the master PW APS protection group triggers
the switching of the slave PW APS protection group simultaneously.
Tunnel: A tunnel needs to be selected. If no tunnel is available, creation of a PW
will fail.
Step Action
If you set Protection Type to PW APS, configure the working and protection PWs.
Step Action
Step Action
1 NOTES: On a PSN network, an MPLS tunnel carries PWs where various services are
encapsulated. In this manner, data packets can be transparently transmitted
between NEs. An MPLS tunnel can carry several PWs. Before configuring a service,
you need to configure the MPLS tunnel that carries the service.
Step Action
Port Mode: In this case, this parameter is set to Layer 2, the port can transmit ATM
signals.
Encapsulation Type: In this case, the Port Mode is Layer 2, Encapsulation Type
takes its default value ATM.
The E1 frame format and frame mode must be the same as those of service access
equipment. As specified in ITU-T G.804, ATM service ports use the CRC-4
multiframe format and PCM30 frame mode by default. The frame format and
frame mode must be the same as those at the opposite end.
Level: If ATM/IMA services need to be mapped into the ATM TRUNK that binds one
or more E1 ports, select E1 in Level. If ATM/IMA services need to be mapped into
the ATM TRUNK that binds one or more serial ports, select Fractional E1 in Level.
IMA Protocol Enable Status: Set to Enabled if the links bound in the ATM TRUNK
require the IMA protocol; otherwise, set this parameter to Disabled.
Policy Name: You can select one of the five ATM service policy names from the
drop-down list or enter the policy name.
Service Type: The UBR service is characterized by non-real-time applications and
many bursts. The UBR service does not specify traffic-related service guarantees.
To be specific, the UBR service only requires that the network side provides the
service with the best effort. The network side does not provide any assured QoS for
the UBR service. In the case of network congestion, the UBR cells are discarded
first.
The CBR service requires tightly constrained delay variation and requires that data
be transmitted at a constant rate. In addition, the CBR service requests a static
amount of bandwidth and the highest priority. The CBR service is characterized by
stable traffic and few bursts.
The rt-VBR service requires tightly constrained delay and delay variation.
Compared with the CBR service, the rt-VBR service allows sources to transmit data
at a rate that varies with time. Equivalently, the sources can be described as bursty.
In addition, the rt-VBR service does not require a static amount of bandwidth.
Compared with the rt-VBR service, the nrt-VBR service does not require tightly
constrained delay or delay variation, and is intended for non-real-time applications.
The UBR+ service is supplementary to the UBR service and is intended for
applications that require assured minimum cell rate, which is indicated by the
minimum cell rate (MCR) parameter. The other characteristics of the UBR+ service
are the same as the corresponding characteristics of the UBR service.
Discard Traffic Frame: Specifies the frame discarding mark in ATM policies. This
parameter is effective to AAL5 traffic.
UPC/NPC: UPC is user-side parameter control and NPC is network-side parameter
control. After UPC/NPC is enabled, the cells with a frame discarding mark will be
discarded in network congestion.
Confidential Information of Huawei. No Spreading without Permission 21
OptiX RTN 900 Data Configuration (Packet Domain) Error! Use the Home tab to apply 标题 1 to
the text that you want to appear here.
2 Service Type: UNIs-NNI: This value applies to ATM PWE3 services. The attributes
in Connection, PW, and CoS Mapping need to be configured. UNI-UNI: This value
applies to common ATM services. Only the attributes in Connection need to be
configured.
Connection Type: For common ATM services (UNI-UNI):
PVP: Only the VPIs of the source and sink are exchanged.
PVC: The VPIs and VCIs of the source and sink are exchanged.
For ATM PWE3 services (UNIs-NNI):
PVP: This value applies to the N-to-1/1-to-1 VPC encapsulation mode. It is
recommended that you set the VPIs to the same value on the two ends of the
ATM connection.
PVC: This value applies to the N-to-1/1-to-1 VCC encapsulation mode. It is
recommended that you set the VPIs/VCIs to the same value on the two ends
of the ATM connection.
Protection Type: This parameter is available only when Service Type is UNIs-NNI.
3
PW Type: Specifies the type of the PW. In the case of ATM 1_to_1 encapsulation,
one PW carries one VPC or VCC. In the case of ATM n_to_1 encapsulation, one PW
carries one or more VPCs or VCCs.
CoS Mapping: Specifies the policy for mapping different ATM service levels to CoS
priorities. By setting this parameter, different quality measures are provided for
different ATM services.
Step Action
Step Action
If one default DiffServ domain exists on the OptiX RTN 900 equipment,
Mapping Relation ID is set to 1, and Mapping Relation Name is set to
Default Map. If these parameters are not set, all the ports belong to this
domain.
Notes: For an E-AGGR service aggregating services from multiple UNI ports
to a PW, the NNI port must be configured as the sink. If for an E-AGGR service
aggregating services from multiple PWs to a UNI port, the UNI port must be
configured as the sink.
Notes: You can set Location to Source or Sink. You can configure one or
more source ports but only one sink port for an E-AGGR service. Otherwise,
configuration of the E-AGGR service will fail.
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure MPLS tunnels between NEA and NEB, between NEA and NEC, and
between NEA and NED.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure bidirectional MPLS tunnels between NEA and NED.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
d) Configure 2×CES services between NEA and NED.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and
Qos base one the network in the lab.
b) Configure bidirectional MPLS tunnels between NEA and NEC.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
d) Configure Fractional CES Services between NEA and NEC, using the first to 15th
timeslots.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN
910/950/980, and the links between the NEA, NEB and NEC are FE/GE links; the link
between NEC and NED is Radio link.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and QOS
base one the network in the lab.
b) Configure bidirectional MPLS tunnel with No-Protection between NEC and NED.
c) Configure bidirectional MPLS tunnel with MPLS APS protection between NEA
and NEC.
d) Configure CES Services between NEA and NED, using the first to 21st timeslots.
e) Configure CES Services between NEB and NED, using the first to 21st timeslots.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure bidirectional MPLS tunnels between NEA and NED.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and
QOSbase one the network in the lab.
b) Configure bidirectional MPLS tunnels between NEA and NEC.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
d) Configure Fractional ATM Services between NEA and NEC, using the first to 15th
timeslots.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN
910/950/980, and the links between the NEA, NEB and NEC are FE/GE links; the link
between NEC and NED is Radio link.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure bidirectional MPLS tunnel with No-Protection between NEC and NED.
c) Configure bidirectional MPLS tunnel with MPLS APS protection between NEA
and NEC.
d) Configure ATM Services between NEA and NED, using the first to 21st timeslots.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN 950/980,
and the links between the NEs are FE/GE links.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure bidirectional MPLS tunnels between NEA and NED.
c) Configure MPLS APS protection for each tunnel on the packet ring to ensure
service availability upon a tunnel fault.
d) Configure the E-LINE services (VLAN ID: 100) between NEA and NED.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
2. Scenario description
There are 4 NEs (NE A to NE D) in the network, the equipment can be RTN
910/950/980, and the links between the NEA, NEB and NEC are FE/GE links; the link
between NEC and NED is Radio link.
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3. Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and Qos
base one the network in the lab.
b) Configure bidirectional MPLS tunnel with No-Protection between NEC and NED.
c) Configure bidirectional MPLS tunnel with MPLS APS protection between NEA
and NEC.
d) Configure E-LINE Services (VLAN ID: 100) between NEA and NED.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;
1. Knowledge requirement
You need to familiar with the operations in charter 1&2.
2. Scenario description
There are 3 NEs (NE A to NE C) in the network, the equipment can be RTN
905/910/950/980, and the links between the NEA, NEB and NEC are radio links;
It is recommended to use the NE default ID and IP.
The transmitting freq. range and T/R spacing of ODU can be got from the label on
the ODUs.
3 Configuration requirement
a) Record the service planning (NNI port 、MPLS Tunnel、MPLS Tunnel APS and
QoS base one the network in the lab.
b) Configure bidirectional MPLS tunnel with No-Protection between NEA and
NEB.
c) Configure bidirectional MPLS tunnel with MPLS APS protection between
NEB and NEC.
d) Configure E-AGGR Services (VLAN ID: 100,200) between NEA, NEB and
NEC.
NOTES: Please make sure there is no abnormal alarm happens; Delete the previous
protection data after finish each requirement;