Configuring Tunnels and Tunnel Protection

Configuring Tunnels and Tunnel Protection http://support.huawei.com/enterprise/docinforeader!loadDocument1.ac...
Contents
4 Configuring Tunnels and Tunnel Protection
4.1 Configuring an MPLS Tunnel
4.1.1 MPLS Tunnel Overview
4.1.1.1 MPLS and MPLS Tunnel
4.1.1.2 Application of the MPLS Tunnel
4.1.2 MPLS Tunnel Functions Supported by Chassis-shaped PTN Devices
4.1.3 MPLS Tunnel Functions Supported by Chase-shaped PTN Devices
4.1.4 Creating MPLS Tunnels in End-to-End Mode
4.1.4.1 Creating MPLS Tunnels One by One
4.1.4.2 Creating Tunnels in Batches
4.1.4.3 Parameter Description
4.1.5 Creating an MPLS Tunnel on a Per-NE Basis
4.1.6 Managing and Maintaining MPLS Tunnels
4.1.6.1 Modifying the Interface of the Static Unicast MPLS Tunnel
4.1.6.2 Deleting an MPLS Tunnel on a Per-NE Basis
4.1.6.3 Testing Tunnel Connectivity on a Per-NE Basis
4.1.6.4 Checking the Correctness of the Tunnel Configuration in End-to-End Mode
4.2 Configuring an IP Tunnel
4.2.1 IP Tunnel Overview
4.2.2 IP Tunnel Functions Supported by Chassis-shaped PTN Devices
4.2.3 IP Tunnel Functions Supported by Case-shaped PTN Devices
4.2.4 Creating an IP Tunnel in End-to-End Mode
4.2.5 Creating IP Tunnels on a per-NE basis
4.3 Configuring a GRE Tunnel
4.3.1 GRE Tunnel Overview
4.3.2 GRE Tunnel Functions Supported by Chassis-shaped PTN Devices
4.3.3 GRE Tunnel Functions Supported by Case-shaped PTN Devices
4.3.4 Creating GRE Tunnels
4.3.5 Parameter Description
4.4 Unified E2E Tunnel Management and Maintenance
4.4.1 Modifying a Tunnel
4.4.2 Deleting a Tunnel
4.4.3 Deleting a tunnel from the network Side
4.4.4 Undeploying a tunnel
4.4.5 Viewing a Discrete Tunnel
4.4.6 Delete a Discrete Tunnel
4.4.7 Duplicating a Tunnel
4.4.8 Reoptimizing an RSVP TE Tunnel
4.4.9 Adjusting the Route for a Tunnel
4.4.10 Perform Tunnel Protection Group Switching
4.4.11 Querying Tunnels Carried by a Fiber
4.4.12 Viewing the VPN Service Carried on a Tunnel
4.4.13 Viewing the Topology of a Tunnel
4.4.14 Viewing the LSP Topology of a Tunnel
4.4.15 Monitoring the Running Status of a Tunnel
4.4.16 Monitoring the Alarms of a Tunnel
4.4.17 Viewing Tunnel Alarms
4.4.18 Monitoring the Performance of a Tunnel
4.4.19 Diagnosing a Tunnel
4.4.20 Diagnosing Tunnel Services Rapidly
4.5 Configuring a QinQ Link
4.5.1 Introduction to QinQ Links
4.5.2 QinQ Link Functions Supported by Chassis-shaped PTN Devices
4.5.3 QinQ Link Functions Supported by Case-shaped PTN Devices
4.5.4 Configuring a QinQ Link Interface
4.5.5 Creating a QinQ Link
4.6 Configuring the MPLS Tunnel APS Protection
4.6.1 MPLS Tunnel APS Functions Supported by Chassis-shaped PTN Devices
4.6.2 MPLS Tunnel APS Functions Supported by Case-shaped PTN Devices
4.6.3 Configuration Flow for the Tunnel APS Protection
4.6.4 Creating an MPLS Tunnel APS Protection Group
4.6.4.1 Creating an MPLS Tunnel APS Protection Group on a Per-NE Basis
4.6.4.2 Creating an MPLS Tunnel APS Protection Group in End-to-End Mode
4.6.4.3 Configuring an APS Receiving Mode
4.6.5 Managing and Maintaining the MPLS Tunnel APS Protection Groups
4.6.5.1 Deleting a Tunnel APS Protection Group
4.6.5.2 Testing MPLS Tunnel APS Protection
4.7 Configuring Offload Protection
4.7.1 Offload Protection Functions Supported by Chassis-shaped PTN Devices
4.7.2 Offload Protection Functions Supported by Case-shaped PTN Devices
4.7.3 Creating an Offload Protection Group
4.8 MPLS-TP Ring Protection Configuration
4.8.1 MPLS-TP Ring Network Protection Functions Supported by Chassis-shaped PTN Devices
4.8.2 MPLS-TP Ring Network Protection Functions Supported by Case-shaped PTN Devices
4.8.3 MPLS-TP Ring Protection Configuration Process
4.8.4 Creating MPLS-TP Ring Protection
4.8.4.1 Creating an MPLS-TP Ring
4.8.4.2 Configuring Intersecting Nodes for MPLS-TP Ring Protection
4.8.4.3 Configuring an MPLS-TP Ring Binding
4.8.5 Managing and Maintaining MPLS-TP Ring Protection
4.8.5.1 Checking the Correctness of MPLS-TP Protection Ring
4.8.5.2 Test on Ring Protection Switching
4.8.5.3 Creating a Ring VPLS Service on an MPLS-TP Protection Ring
4.9 Configuring PW APS
4.9.1 PW APS Functions Supported by Chassis-shaped PTN Devices
4.9.2 PW APS Functions Supported by Case-shaped PTN Devices
4.9.3 PW APS Configuration Flow
4.9.4 Creating a PW APS Protection Group
4.9.5 Starting the PW APS protocol
4.9.6 Binding PW APS Pairs
4.9.7 Testing PW APS
4.10 Configuring PW FPS
4.10.1 PW FPS Functions Supported by Chassis-shaped PTN Devices
4.10.2 PW FPS Functions Supported by Case-shaped PTN Devices
4.10.3 Configuring a PW FPS 1:1
4.10.4 Configuring a PW FPS 1+1
4 Configuring Tunnels and Tunnel Protection
1 of 43 13-May-19, 7:41 PM

In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In this way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carry several PWs. Before configuring a service, first configure
an MPLS tunnel that carries the service. On the U2000, you can use the end-to-end function or per-NE configuration scheme to configure an MPLS tunnel.

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying PWs over the IP tunnel. In this way, services can be transparently transmitted in an IP network.

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying ATM PWE3 services over generic routing encapsulation (GRE) tunnels. In this way, services can be transparently transmitted in an IP
network.

This topic describes the concepts, application, and configuration method of a QinQ link.

This chapter describes the concept, application, and configuration method of the MPLS tunnel APS protection.

In the Offload solution, the IP/GRE tunnel in the wholesale managed service (WMS) network should be configured with protection to ensure that the service is protected if the IP/GRE tunnel becomes faulty.

MPLS-TP ring protection applies to a single ring and intersecting rings, which has incomparable advantages over linear protection. This topic describes basic concepts and configuration methods of MPLS-TP ring protection.

The PTN equipment supports 1:1 PW APS protection. This chapter describes PW APS in terms of concept, application, and configuration.

The PTN equipment supports 1:1 PW FPS and 1+1 PW FPS protection. This chapter describes PW FPS 1:1 and PW FPS 1+1 configuration.

In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In this way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carry several PWs. Before configuring a service, first configure an
MPLS tunnel that carries the service. On the U2000, you can use the end-to-end function or per-NE configuration scheme to configure an MPLS tunnel.
4.1.1 MPLS Tunnel Overview

Before configuring the MPLS tunnel, familiarize yourself with the MPLS and MPLS tunnel, and application scenarios of the MPLS tunnel.
4.1.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS protocol. Independent from the service, the MPLS tunnel
realizes the end-to-end transmission and carries the PWs related to the service.
Figure 4-1 shows how the MPLS tunnel is used as the service transmission channel.
Figure 4-1 MPLS tunnel in the MPLS network
The MPLS tunnel only provides an end-to-end channel, and does not care which service is encapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuck with an MPLS label and sent to the MPLS tunnel for transmission.
At the sink end, data packets are recovered and retain the original service features. In the tunnel, the intermediate nodes are called Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.
4.1.1.2 Application of the MPLS Tunnel

As the carrier of PWs in the network, the MPLS tunnel provides the service tunnel to transmit service packets. The MPLS tunnel can carry various services, such as CES services, ATM/IMA services, Ethernet service and protocol packets. The MPLS
tunnel is mainly used for transparent transmission of point-to-point data service packets.
Transparent Transmission of Point-to-Point Data Packets

Commonly, the MPLS tunnel is used to provide a point-to-point service channel for services such as the E-Line service. In this way, provider edges (PEs) in a PSN network can transparently transmit services. Figure 4-2 shows how point-to-point data
packets are transparently transmitted.
Figure 4-2 Transparent transmission of point-to-point data packets
An edge node in one network accesses the services from Node B, and transports the services to the RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can be used.
On the U2000, two schemes can be used to create such a unicast tunnel.
Configuration on a per-NE basis: Configure the ingress port and the IP address of the next hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel is created.
Configuration by end-to-end function: This configuration is classified into static configuration and dynamic configuration.
Static configuration: Specify the source and sink NEs for the MPLS tunnel, and each NE involved in the tunnel. In this way, one unicast MPLS tunnel is created.
Dynamic configuration: Only specify the source and sink NEs of the MPLS tunnel. The equipment then creates a unicast MPLS tunnel through signaling.
Tunnel Protection Group

The MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1+1 or 1:1 protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, the tunnel protection group ensures that services can still normally
run.
By using the U2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carry important services.
Figure 4-3 shows the protection principle for unicast tunnels.
Figure 4-3 Protection principle for unicast tunnels
4.1.2 MPLS Tunnel Functions Supported by Chassis-shaped PTN Devices
Specifications
√ indicates that the PTN device supports this function, and × indicates that the PTN device does not support this function.
Table 4-1 MPLS tunnel specifications
Function Description PTN 3900 PTN 3900-8 PTN 1900
Static MPLS tunnel - √ √ √
Dynamic RSVP-TE tunnel - √ √ √
2 of 43 13-May-19, 7:41 PM
4.1.3 MPLS Tunnel Functions Supported by Chase-shaped PTN Devices
Specifications
Table 4-2 MPLS tunnel specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Function Description PTN 910 PTN 910-F PTN 950 PTN 960
Static MPLS tunnel - √ √ √ √
Dynamic RSVP-TE tunnel - √ √ √ √
Table 4-3 MPLS tunnel specifications (on the PTN 905A, PTN 905B,PTN 906A and PTN 906B)
Function Description PTN 905A PTN 905B PTN 906A PTN 906B
Static MPLS tunnel - √ √ √ √
Dynamic RSVP-TE tunnel - × × × ×
4.1.4 Creating MPLS Tunnels in End-to-End Mode

4.1.4.1 Creating MPLS Tunnels One by One
Prerequisites
You are an NMS user with "Maintenance Group" authority or higher.

Port attributes are configured correctly.
LSR IDs are set correctly for all NEs.
The control plane is configured for RSVP-TE, and IP tunnels.
Context
During the creation of a tunnel configured with an APS group, the values of routes for the working tunnel cannot be all the same as those for the protection tunnel. Otherwise, the protection does not take effect.
Procedure
1. Choose Service > Tunnel > Create Tunnel from the Main Menu.
2. Configure basic information.
NOTE:
When you create a reverse tunnel, the U2000 automatically sets Tunnel Name to Forward Tunnel Name+_RVS.
If Signaling Type is set to Static CR, Direction is set to Unidirectional, and Create Reverse Tunnel is selected, the U2000 will create two unidirectional tunnels in two opposite directions. If Service Direction is set to Bidirectional, the U2000 will create a bidirectional tunnel.
If Signaling Type is set to Static CR and Protection Type is set to 1+1 or 1:1, a tunnel and a tunnel protection group will be created at the same time.
The Template parameter can be set only when Signaling Type is set to RSVP TE. You can use a template to configure tunnel details.
If you select the Configure As Bypass Tunnel check box when creating an RSVP TE tunnel , a bypass protection tunnel will be created.
3. Configure the NE list.
a. Select the source and sink NEs or transit NEs. In the NE Role column, specify their locations on a tunnel.
Use any of the following methods to select an NE:

Method 1: In the topology view, right-click the desired NE and choose Add from the shortcut menu.
Method 2: In the topology view, double-click the desired NE.
Method 3:
i. Click Add and choose NE.

ii. In the dialog box, select the desired NE and click OK.
NOTE:
If you create an IP tunnel or RSVP TE, , specify the source and sink NEs for the tunnel. If you create a static CR tunnel, specify the source and sink NEs or transit NEs for the tunnel.
Click Add and choose Virtual Node to specify the virtual nodes that the tunnel traverses. A virtual node refers to an NE not managed by the U2000. Virtual nodes are used to create a tunnel with an unterminated sink.
b. Optional: If you create a static CR tunnel, perform the following operations:

Configure route calculation on the U2000.
i. Optional: Select Auto-Calculate route. Then the U2000 automatically calculates the route for the tunnel after 2 and 3 are performed.
ii. Set Restriction Bandwidth.
iii. Specify route constraint nodes, that is, explicit and excluded nodes, by clicking Route Restriction or right-clicking the desired NEs in the topology view.
iv. Optional: If Auto-Calculate route is not selected, click Calculate Route to manually start route calculation on the U2000.
v. Optional: PTN 3900/3900-8/1900/910/910-F/950/960: Select Configure MPLS-TP OAM. In the dialog box, set MPLS-TP OAM parameters for the service.
NOTE:
A Layer 2 link must be configured before route calculation.
NEs or ports can be configured as route constraint nodes as needed. In the Layer 2 link topology view, selecting an NE or a port closest to the inbound node as a route constraint node is recommended.
If an NE is selected as a route constraint node, select the NE closest to the inbound node. Otherwise, route calculation fails.
By default, the shortest route is selected from the routes that are calculated based on Restriction Bandwidth and route constraints.
Tunnel loopbacks do not support automatic route calculation.
The service to be configured with MPLS-TP OAM must meet the following requirements:
Signaling is set to Static CR.
c. Optional: Use any of the following methods to configure route constraints for RSVP TE tunnels:
Method 1(PTN 3900/3900-8/1900/910/910-F/950/960): In the Main Topology, right-click an NE and choose Set Positive Primary Path Explicit Route > NE or Set Positive Primary Path Explicit Route > Interface from the
shortcut menu.
Method 2:
3 of 43 13-May-19, 7:41 PM
Click Add on the right of Route Constraint, and set Interface IP Address and Restriction Type.
NOTE:
PTN NEs support route constraints only for primary paths.
4. PTN 3900/3900-8/1900/910/910-F/950: If you create an IP tunnel, configure tunnel information in the left-hand pane. If you create an MPLS tunnel, click Details to configure tunnel information.
NOTE:
Using a template to configure an RSVP TE tunnel is recommended.
For a static CR tunnel, Next Hop is the IP address of the inbound port of the next node on the tunnel.
For a static CR tunnel, double-click Out Interface or In Interface. In the dialog box, select an interface and click Configure to configure interface attributes or click Add VLN to create an Ethernet virtual interface.
For the TND1CXP board on a PTN 950, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been reserved for OAM
packets.
For the TNC1CXPA/B/G/H/I board on a PTN 910, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been reserved
for OAM packets.
For the TND3CXPA/B board on a PTN 960, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been reserved for
OAM packets.
If the Deploy check box is not selected, the configuration data is stored only on the U2000. If the Deploy check box is selected, the configuration data is stored on the U2000 and applied to NEs. By default, the Deploy check box is selected.
If the Deploy and Enable check boxes are selected, tunnels on NEs are available only when the tunnels are enabled.
If the Deploy check box is not selected during tunnel creation, right-click the tunnel on the Manage Tunnel tab page and choose Deploy from the shortcut menu after the tunnel has been created.
5. Optional: If Protection Type of a static CR tunnel is set to 1+1 or 1:1, click Configure Protection Group. In the dialog box, set protection group parameters. Click Details and Configure OAM. In the dialog box, set tunnel OAM parameters.
6. Click OK.
NOTE:
If Source Node, Sink Node, and Tunnel Interface for the working and protection tunnels are set to the same value, The same route is used for the working tunnel and protection tunnel in the protection group. is displayed after you click OK.
Click Yes. The U2000 then configures working and protection tunnels whose routes are the same.
Click No. The U2000 does not perform any operations.
4.1.4.2 Creating Tunnels in Batches

The U2000 supports batch creation of RSVP-TE tunnels.
Prerequisites

Port attributes are configured correctly.
LSR IDs are set correctly for all NEs.
The control plane is configured.
Procedure
1. Choose Service > Tunnel > Batch Create Tunnel from the Main Menu.
2. Configure basic information, such as Network Type and Signaling Type.
NOTE:
Currently, the U2000 supports the following networking modes:
1. Full-Mesh: All NEs are bidirectionally and fully connected.
2. Hub-Spoke: All spoke nodes are bidirectionally connected to any of the hub nodes, the hub nodes are bidirectionally and fully connected, and the spoke nodes are not connected with each other.
3. Ring: Bidirectional connections are generated based on rings.
Template can be set only when Signaling Type is set to RSVP TE.
3. Configure the NE list.
a. Select NEs.

Method 3:
i. Click Add and choose NE.

ii. In the dialog box, select the desired NE and click OK.
b. Optional: NE Role can be set when Network Type is set to Hub-Spoke.
4. Click Auto-Assign. The U2000 then automatically assigns IDs to the tunnels created in batches.
NOTE:
Tunnel IDs can also be manually specified.
5. Configure tunnel details.
NOTE:
If an RSVP-TE tunnel needs to be created, set General, TE Information, Trail Information, Protection Attribute, QoS Information, and Advanced.
6. Select the Deploy check box and click OK.
NOTE:
If the Deploy check box is selected, the configuration data is stored on the U2000 and applied to NEs. By default, the Deploy check box is selected.
If the Deploy and Enable check boxes are selected, tunnels on NEs are available only when the tunnels are enabled.
4 of 43 13-May-19, 7:41 PM

This section describes the parameters related to the tunnel configuration in the end to end mode.
Table 4-4 Parameters relevant to the general information about the tunnel creation
Parameter Description Settings
Tunnel Name Definition: Setting method:

Specifies the name of a tunnel. Enter a value.
Protocol Type Definition: Setting method:

Specifies the type of the protocol that a tunnel uses. Select a value from the drop-down list.
Protocol Type: MPLS
Signaling Type Definition: Setting method:

Specifies the signaling type of a tunnel. This parameter can be set only when Protocol Type is set to MPLS.
When the protocol type is MPLS, Signaling Type can be RSVP TE, LDP, Static CR, or
Static.
NOTE:
OptiX PTN 960 equipment do not support RSVP TE Tunnel, LDP Tunnel and Static Tunnel
NOTE:
OptiX PTN equipment support Static CR, and RSVP TE.
Template Definition: Setting method:

Indicates the application template. Click the ... button.
You can configure the details of a tunnel by using a template.
Auto-Calculate route Definition: Setting method:

Enables or disables the automatic route calculation function. If you select this parameter, Set it through the check box.
the U2000 immediately calculates routes after you specify the source and sink nodes and
explicit and excluded nodes in the physical topology.
Restriction Bandwidth (Kbit/s) Definition: Setting method:

When calculating the route automatically, the U2000 checks whether the calculated route Select a value from the drop-down list.
can provide this bandwidth.
Create reverse tunnel Definition: Setting method:

When this parameter is selected, a reverse tunnel is created when a positive tunnel is Set it through the check box.
created. When this parameter is not selected, only a positive tunnel is created.
Configure As Bypass Tunnel Definition: Setting method:

Sets the tunnel as a bypass tunnel. Set it through the check box.
A bypass tunnel can protect the working that has the same source and sink nodes, creation
priority, hold priority, and color setting as the bypass tunnel.
NOTE:
Only the dynamic tunnel can be configured as the bypass tunnel.
Create Bidirectional Tunnel Definition: Setting method:

Sets the tunnel as a bidirectional tunnel. Set it through the check box.
If you select this check box, both forward and reverse tunnels are created at the same time Only one of Create reverse tunnel and Create Bidirectional Tunnel can be selected.
and you do not need to configure ports.
The PTN equipment supports the setting of the parameter.
Create Protection Group Definition: Setting method:

If you select this check box, a protection group is created during the creation of a tunnel. Set it through the check box.
Remarks Definition: Setting method:

Specifies remarks for special tunnels. This makes the management and maintenance of Enter a value.
tunnels easier.
Deploy Definition: Setting method:

Deploys a tunnel. A tunnel is saved on the U2000 and delivered to NEs. Set it through the check box.
Enable Definition: Setting method:

Enables a tunnel automatically when the tunnel is deployed. Set it through the check box.
Table 4-5 NE list
NE Name Definition: -
Indicates the name of the NE.
LSR ID Definition: -
Indicate the ID of an LSR.
Node Role Definition: Setting method:

Ingress indicates the direction of an ingress tunnel; Egress indicates the direction of an A source node is set to Ingress; a sink node is set to Egress; PTN 3900/3900-8/1900/910
egress tunnel; PTN 3900/3900-8/1900/910/910-F/950/960: Transit indicates a pass- /910-F/950/960: a transit node is set to Transit.
through intermediate node.
Table 4-6 Parameters relevant to the configuration of a static CR tunnel
Tunnel ID Definition: Setting method:

Specifies the ID of a tunnel. The tunnel ID can be allocated automatically. Enter a value, or click Auto-Assign to automatically allocate an ID to a tunnel.
Tunnel Interface Definition: Setting method:

Specifies the interface of a tunnel. Click the ... button.
NOTE:
The PTN equipment does not support the setting of this parameter.
Bandwidth Type Definition: Setting method:

Specifies the bandwidth type. Select a value from the drop-down list.
NOTE:
CIR (kbit/s) Definition: Setting method:

Commit the information rate for the service to pass. Enter a value or set the parameter through the drop-down list.
CBS(bytes) Definition: Setting method:

The CBS parameter indicates the committed burst size (CBS). When the bandwidth is Enter a value or set the parameter through the drop-down list.
insufficient, certain packets cannot enter the queue for forwarding in time. In this case, a
buffer, where these packets are stored, is required. Then, after the bandwidth is sufficient,
these packets are forwarded. Hence, the CBS indicates the ensured size of the buffer
space. When the size of data need be buffered is smaller than the CBS, this data that are
temporarily buffered can be fully transmitted without packet loss.
PIR(kbit/s) Definition: Setting method:
The PIR parameter indicates the maximum rate at which the packet is allowed to be Enter a value or set the parameter through the drop-down list.
transmitted.
PBS(bytes) Definition: Setting method:

The PBS parameter indicates the peak burst size. Enter a value or set the parameter through the drop-down list.
LSP Type Definition: Setting method:

Specifies the type of the LSP that a node belongs to. Select a value from the drop-down list.
EXP Definition: Setting method:

Specifies the Level of EXP that a node belongs to. 7 indicates the highest level. Select a value from the drop-down list.
MTU(bytes) Definition: Setting method:

The MTU parameter indicates the maximum transmitted packet length, which is the length Enter a value.
of the packet payload.
LSP Mode Definition: Setting method:

The LSP mode of the tunnel determines whether to use the tunnel priority for scheduling. Select a value from the drop-down list.
Uniform: Uses the EXP values of the tunnel for scheduling.
Pipe: Uses the EXP values of the PW for scheduling.
Node Definition: -
Indicates the node where a tunnel is created.
5 of 43 13-May-19, 7:41 PM
Node Type Definition: -

Indicates the type of a node.
LSP Name Definition: -

Indicates the name of the Tunnel that a node belongs to.
In Interface/Ring Definition: Setting method:

Indicates the ingress interface. Specify the ingress interface for a transit node or an egress node.
NOTE:
An ingress node does not support setting the ingress interface.
In Label Definition: Setting method:

Indicates the ingress label of a tunnel. In addition, the label value is unique on an NE. Enter a value, or click Auto-assign Label to automatically allocate a label to a tunnel.
Reverse In Label Definition: Setting method:

Indicates the reverse ingress label of a bidirectional tunnel. In addition, the label value is Enter a value, or click Auto-assign Label to automatically allocate a label to a tunnel.
unique on an NE.
Out Interface Definition: Specify the egress interface for a transit node or an ingress node.
Indicates the egress interface.
Out Label/Ring Definition: Setting method:

Indicates the egress label of a tunnel. In addition, the label value is unique on an NE. Enter a value, or click Auto-assign Label to automatically allocate a label to a tunnel.
Reverse Out Label Definition: Setting method:

Indicates the reverse egress label of a bidirectional tunnel. In addition, the label value is Enter a value, or click Auto-assign Label to automatically allocate a label to a tunnel.
unique on an NE.
Next Hop Definition: Setting method:

Indicates the IP address of the next hop. Specifically, the IP address of the next hop of the Specify the ingress interface of the next node and the IP address of the next hop is set
local node is the IP address of the ingress interface of the next node in the direction of a automatically.
tunnel.
Reverse Next Hop Definition: Setting method:

Indicates the IP address of the reverse next hop. Specifically, the IP address of the reverse Specify the output interface of the ingress node of bidirectional and the IP address of the
next hop of the local node is the IP address of the out interface of the ingress node of a reverse next hop is set automatically.
bidirectional tunnel.
Table 4-7 Parameters relevant to the Route Constraint of a Static CR tunnel
Source Node Definition: -

Set the source node of tunnel.
Sink Node Definition: -

Set the sink node of tunnel.
Restriction Type Definition: -

Display the restriction type.
Node Definition: Setting method:

The route restriction node for tunnel Click Add, In the Set Route Restriction window displayed, set the node.
Interface Name Definition: Setting method:

The interface name of route restriction node Click Add, In the window displayed, set the interface name.
Interface IP Address Definition: -

The interface IP Address of route restriction node.
Table 4-8 Parameters relevant to the configuration of an RSVP TE tunnel

Specifies the source node of a tunnel.

Specifies the sink node of a tunnel.
Destination IP Address Definition: -

Specifies the destination address of a tunnel.

Allocates the ID to a tunnel. Enter a value.
Tunnel Interface Definition: Setting method:

Specifies the interface of a tunnel. Enter a value, or click the ... button. In the dialog box that is displayed, select a record and
click OK.
NOTE:
Bind Tunnel Policy Definition: Setting method:

Specifies tunnel policy to be bound. Set it through the check box.
Reverse Style Definition: Setting method:

Specifies the resource reservation style. Select a value from the drop-down list.
Bandwidth Type Definition: Setting method:

Specifies the type of the bound bandwidth for a tunnel. Select a value from the drop-down list.
Bandwidth (kbit/s) Definition: Setting method:

Specifies the size of the bound bandwidth for a tunnel. Enter a value.
Tie Breaking Definition: Setting method:

Specifies the arbitration policy. Select a value from the drop-down list.
Trail Type Definition: Setting method:

Specifies the type of a trail. Select a value from the drop-down list.
Enable Affinity Definition: Setting method:

Enables the affinity of a tunnel. Set it through the check box.
The links with the same route color are preferred during a rerouting.
Color (0x) Definition: Setting method:

Specifies the route color that a static tunnel uses. Enter a value.
The links with the same route color are preferred during a rerouting.
Mask (0x) Definition: Setting method:

Specifies the mask of a dynamic tunnel. Enter a value.
You can select the link color based on the number of the bits of the mask during rerouting.
The route that matches the link color is selected.
Trail Type Definition: Setting method:

Enable Hop Limit Definition: Setting method:

After Enable Hop Limit is selected, the corresponding hop limitation function for routing Select a value from the drop-down list.
is enabled.
Max Hops Definition: Setting method:

Specifies the maximum hops allowed during routing. Enter a value.
Explicit Trail Name Definition: Setting method:

Specifies the required explicit trail. In the dialog box displayed, if the explicit trail is not Click the ... button.
required, you can click Create to create an explicit trail.
IP Address Definition: Setting method:

Specifies the IP address of the next hop of an explicit trail. Enter a value, or click the ... button. In the dialog box that is displayed, select a record and
click OK.
Hop Type Definition: Setting method:

Specifies the policy especially for the IP address of the next hop. Select a value from the drop-down list.
Strictly include: Specifies an explicit node that the trail must traverse.
Moreover, the specified node must be directly connected to its previous hop and
6 of 43 13-May-19, 7:41 PM
next hop. By specifying a strict explicit route, you can control exactly the route
of an LSP.
Loosely include: Specifies an explicit node that the trail must traverse, but other
routers are allowed between the specified node and the previous hop.
Exclude: The LSP cannot contain the preceding IP address.
Backup Type Definition: Setting method:

Specifies the backup type. Select a value from the drop-down list.
NOTE:
Reversion Interval (s) Definition: Setting method:

You can set the reversion time when the backup type is set to Cold standby. Enter a value.
NOTE:
The PTN equipment do not support the setting of this parameter.
Configure Escape Trail Definition: Setting method:

Enables or disables the emergency trail. Set it through the check box.
NOTE:
Protected BW Type Definition: Setting method:

Specifies the bandwidth type of a bypass tunnel. Select a value from the drop-down list.
Protected BW (kbit/s) Definition: -

Specifies the bandwidth of a bypass tunnel.
Protection BW Unlimited Definition: Setting method:
Sets whether the bandwidth of a bypass tunnel is limited. Set it through the check box.
NOTE:
Protect Interface Definition: Setting method:

Sets the protect interface of a bypass tunnel. Enter a value, or click the ... button. In the dialog box that is displayed, select a record and
click OK.
LSP Type Definition: Setting method:

Currently, an LSP can be set to the E-LSP only. Select a value from the drop-down list.

7 indicates the highest priority. Select a value from the drop-down list.
Enable Reroute Definition: Setting method:

Enables or disables the rerouting function of a tunnel. Set it through the check box.
Record Route Type Definition: -

Displays the type of record route.
Loop Detection Definition: Setting method:

Sets whether to perform a loop detection on a tunnel. Select a value from the drop-down list.
Setup Priority Definition: Setting method:

The setup priority indicates the sequence of setting up tunnels in a link. The tunnel of Select a value from the drop-down list.
higher setup priority can preempt the bandwidth resources of other tunnels when the
resources are insufficient.
0 indicates the highest priority.
Hold Priority Definition: Setting method:

When resources are insufficient, it is of the low probability that the bandwidth resources of Select a value from the drop-down list.
a tunnel of higher hold priority are preempted by other tunnels.
0 indicates the highest priority. NOTE:
The hold priority of a tunnel should be higher than or equal to the corresponding setup priority.
Retry Interval (s) Definition: Setting method:

Specifies the interval for transmitting data again. If the transmit end fails to receive a Enter a value.
response after the retry interval set, the transmit end transmits the data again to ensure the
reliability of the data transmitting.
Retry Times Definition: Setting method:

Specifies the maximum retry times. Enter a value.
Route Pinning Definition: Setting method:

After the route pinning function is enabled, the LSP does not vary with the route. This Set it through the check box.
function cannot be enabled when the route reoptimization and automatic bandwidth
adjustment functions are enabled.
Enable Reoptimization Definition: Setting method:

After the reoptimization function is enabled, an LSP calculates route periodically. If the Select a value from the drop-down list.
new route is better than the original route of the LSP, another LSP is created and the
original LSP is deleted. This function cannot be enabled when the route lockout and
automatic bandwidth adjustment functions are enabled.
Reoptimization Frequency Definition: Setting method:

This parameter can be set when the reoptimization function is enabled. Enter a value.
Auto BW Adjust Type Definition: Select a value from the drop-down list.
This function cannot be enabled when the route lockout and route reoptimization functions
are enabled.
Frequency Definition: Setting method:

Specifies the frequency of automatically adjusting the bandwidth. Enter a value.
Max Bandwidth (kbit/s) Definition: Setting method:

Specifies the maximum bandwidth that can be configured for a tunnel. Enter a value.
Min Bandwidth (kbit/s) Definition: Setting method:

Specifies the minimum bandwidth that can be configured for a tunnel. Enter a value.
IGP Shortcut Definition: Setting method:

Specifies the IGP that the tunnel creation supports. If the value is set to none, it indicates Select a value from the drop-down list.
that the IS-IS protocol and OSPF protocol are supported.
IGP Advertise Definition: Setting method:

Enables or disables the IGP advertisement. Set it through the check box.
Hold Time (s) Definition: Setting method:

The parameter can be set only when IGP advertisement is enabled. Enter a value.
Trail Metric Type Definition: Setting method:

IGP Metric Type Definition: Setting method:

Metric Definition: Setting method:

The smaller the metric value, the higher the link priority is. Enter a value.
Table 4-9 Parameters relevant to the configuration of an IP-based tunnel (PTN 3900/3900-8/1900/910/910-F/950)

Indicates the source node of a tunnel.

Indicates the sink node of a tunnel.

Allocates an ID to a tunnel. Enter a value.
Out Interface Definition: Setting method:

Specifies the egress interface. Enter a value, or click the ... button. In the dialog box that is displayed, select a record and
click OK.
7 of 43 13-May-19, 7:41 PM
Destination IP Address Definition: Setting method:

Specifies the destination IP address. Enter a value, or click the ... button. In the dialog box that is displayed, select a record and
click OK.
4.1.5 Creating an MPLS Tunnel on a Per-NE Basis

You can create a unicast MPLS tunnel on a per-NE basis. To create such a tunnel, create a tunnel at each node involved in the tunnel.
Prerequisites
You are an NMS user with "Operator Group" authority or higher.

You must complete the correct configuration of the port attributes.
You must complete the correct setting of the LSR ID for each NE. For configuration method, see 2.6.5.1 Configuring Basic Attributes of the Control Plane.
Procedure
1. Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree.
2. Optional: Create a unidirectional tunnel.
a. Click New > Unidirectional Tunnel. The New Unicast Tunnel dialog box is displayed.
b. Select Create Reverse Tunnel to set parameters for the forward and reverse tunnels. When creating an MPLS tunnel on a per-NE basis, see Table 4-10 for details on the related parameters.
NOTE:
When Node Type is set to Egress, Bandwidth (kbit/s) must be consistent with the tunnel bandwidth in the Ingress direction and cannot be set.
For Next Hop Address, select the IP address of the interface of the next node.
When the value of MTU is 0, there is no restriction. If the MTU value needs to be restricted, the value should not be greater than the MTU value of the physical port where the tunnel resides.
For the TND1CXP board on a PTN 950, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been reserved
for OAM packets.
For the TNC1CXPA/B/G/H/I board on a PTN 910, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has
been reserved for OAM packets.
For the TND3CXPA/B board on a PTN 960, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been
reserved for OAM packets.
3. Optional: Create bidirectional tunnel.
a. Click New > Bidirectional Tunnel. The New Bidirectional Tunnel dialog box is displayed.
b. Set parameters for the bidirectional tunnel.
4. Click OK to finish creation of the static tunnel.

5. Follow 1 - 4 to create static tunnels for Transit nodes and the Egress node.

This section describes the parameters related to the MPLS Tunnel configuration.
Table 4-10 Descriptions of the parameters of the static tunnel
Field Value Description
Tunnel Key Tunnel ID(Source Node:LSR ID,Sink Node:LSR ID) Indicates the tunnel.
Name Example: name1 Indicates and specifies the name of the static tunnel.
Maximum length: 64 bytes
8 of 43 13-May-19, 7:41 PM
Enable State Enabled, Disabled Indicates and specifies the state of the static tunnel.
Disabled: A tunnel is unreachable on the management plane, whereas tunnel NOTICE:
OAM is reachable. Although APS is configured for the tunnel, APS switching is Disabling the tunnel is risky, which may interrupt all services transmitted along the tunnel.
not performed, causing services transmitted along the tunnel to be interrupted. Evaluation the impact on the live network before your operation.
Enabled: A tunnel is reachable on the management plane and properly
transmitting services.
Node Type Ingress, Egress, Transit Indicates the node type. If the tunnel where the node resides is bound to the MPLS-TP
shared protection ring, the attributes configured for the ring vary with the Node Type.
Ingress: ingress node
Egress: egress node
Transit: pass-through node
Direction Unidirectional, Bidirectional Indicates the direction of the tunnel.
Inbound Bearer Type MPLS-TP Shared Protection Ring, Port Specifies whether the tunnel is carried on an MPLS-TP shared protection ring or a port.
You can configure the attributes for the MPLS-TP shared protection ring or port according
to the value of Inbound Bearer Type.
NOTE:
If one end of a tunnel fails to be bound to the ring, the U2000 will try to roll back the
tunnel. For the tunnel that fails to be rolled back, you need to modify the inbound bearer
type to port for binding nodes.
When binding the tunnel to a port, update the remaining ring bandwidth of all nodes on
the tunnel.
Outbound Ring Example: 665 Indicates the outbound ring ID. When Node Type is Egress or Transit, you can configure
the shared protection ring ID after a service is bridged from one ring to another.
Outbound Ring Direction Westbound, Eastbound Eastbound: A service goes clockwise after being bridged from one ring to
another.
Westbound: A service goes counterclockwise after being bridged from one ring
to another.
CIR (kbit/s) For PTN 1900/3900/3900-8/910/950: No Limit, 1 to 2147483647 Commit the information rate for the service to pass
CBS (bytes) No Limit, 64 to 131072 Set the committed burst size for the traffic to pass in a short time.
PIR (kbit/s) For PTN 1900/3900/3900-8/910/950: No Limit, 64 to 2147483647 Set the maximum rate for the service to pass.
PBS (bytes) No Limit, 64 to 16777216 Set the maximum burst size for the traffic to pass in a short time.
In Board/Logic Interface Type Slot-Board Name Indicates and specifies the ingress card or logical port type.
In Port Port (Port No.) Indicates and specifies the ingress port of the static tunnel.
The egress node and transmit node support the setting of the ingress port, but the ingress
node does not.
Forward In Label 16 to 1048575 Indicates and specifies the ingress label of the tunnel.
The egress node and transmit node support the setting of the forward ingress label, but the
ingress node does not.
Reverse Out Label 16 to 1048575 Indicates and specifies the egress label of the tunnel.
0 The egress node and transmit node support the setting of the reverse egress label, but the
Inbound Ring Node ID Example: 8 Indicates the ID of the ring node where the service enters the shared protection ring.
Outbound Bearer Type MPLS-TP Shared Protection Ring, Port Specifies whether the tunnel is carried on an MPLS-TP shared protection ring or a port.
Inbound Ring Direction Westbound, Eastbound Eastbound: A service goes clockwise after being transmitted to a ring.
Eastbound: A service goes counterclockwise after being transmitted to a ring.
Inbound Ring Example: 821 Indicates the inbound ring ID. When the Node Type is Ingress or Transit, you need to
configure the shared protection ring ID for the service inbound node of a ring.
Out Board/Logic Interface Type Slot-Board Name Indicates and specifies the egress or logic interface type.
Out Port Port (Port No.) Indicates and specifies the egress port of the static tunnel.
The ingress node and transmit node support the setting of the egress port, but the egress
node does not.
Forward Out Label 16 to 1048575 Indicates and specifies the egress label of the tunnel.
The ingress node and transmit node support the setting of the forward egress label, but the
egress node does not.
Reverse In Label 16 to 1048575 Indicates and specifies the ingress label of the tunnel.
The ingress node and transmit node support the setting of the reverse ingress label, but the
Forward Next Hop Address Example: 192.168.0.2 Indicates and specifies the IP address of the egress next hop of the tunnel.
The ingress node and transmit node support the setting of the egress next hop address, but
the egress node does not.
Reverse Next Hop Address Example: 192.168.0.3 Indicates and specifies the IP address of the egress next hop of the tunnel.
The egress node and transmit node support the setting of the egress next hop address, but
the egress node does not.
Sink Node Example: 192.168.0.2 Indicates and specifies the sink node of the tunnel.
The egress node and transmit node support the setting of the sink node, but the ingress
node does not.
Source Node Example: 192.168.0.1 Indicates and specifies the source node of the tunnel.
The ingress node and transmit node support the setting of the source node, but the egress
node does not.
Tunnel Type E-LSP Indicates the type of the static tunnel.
Ingress PW Priority 0, 1, 2, 3, 4, 5, 6, 7, None The E-LSP supports the ingress PW priority. The number 7 indicates the highest priority.
LSP Mode Pipe, Uniform The LSP mode of the tunnel determines whether to use the tunnel priority for scheduling.
Uniform: Uses the EXP values of the tunnel for scheduling.
Pipe: Uses the EXP values of the PW for scheduling.
MTU (bytes) No Limit, 1 to 9000 When the MTU value needs to the restricted, the value cannot be larger than the MTU
value of the physical port that houses the tunnel.
Protection Group Example: 5 Indicates the protection group that the tunnel belongs to.
VLAN ID Example: 3 Indicates the VLAN ID. In the case of an ingress tunnel, the VLAN ID can be set.
Deployment Status Deployed, Undeployed Display the deployment status of the tunnel.
Loopback Status No loopback, Bidirectional loopback A packet loss fault on a static bidirectional tunnel can be located by using the hop-by-hop
loopback test on the tunnel and the PRBS function of CES services.
NOTE:
This parameter applies to only the transit nodes on a static bidirectional tunnel.
This parameter applies to only the transit nodes on a static bidirectional tunnel.
OAM Recommendation MPLS OAM(Y.1711), MPLS-TP OAM(Y.1731) Display the OAM recommendation of the tunnel.
New Reverse Tunnel Checked, Unchecked Specifies a new reverse tunnel to set parameters of the forward and reverse tunnels.
Deploy Checked, Unchecked Set the deployment status of the tunnel.

Default: Checked (not available)
Query Actual Bandwidth Checked, Unchecked When this parameter is specified, the actual effective bandwidth is queried. When this
parameter is not specified, the configured bandwidth is queried.
The OptiX PTN 950 does not support the query of actual bandwidth.
Outbound Ring Node ID Example: 10 Indicates the ID of the ring node where the service enters the shared protection ring.
Remote Tunnel ID Example: 398 Each of the two intersecting nodes has a tunnel. One tunnel works as the active tunnel
while the other works as the standby tunnel. Since the two tunnel IDs are different, the
remote tunnel ID will be saved for a tunnel at each node for unified management.
NOTE:
This parameter can be set when Node Type is Transit, and Outbound Bearer Type and
9 of 43 13-May-19, 7:41 PM
Inbound Bearer Type are MPLS-TP Shared Protection Ring.
Role Active, Standby Only two intersecting nodes are configured on the two-fiber bidirectional intersecting
rings. The two tunnels that pass through the two intersecting nodes separately are
configured as active and standby tunnels, so that if one intersecting node fails, services can
pass through the other intersecting node. Services will choose the standby tunnel when the
active tunnel is not available.
NOTE:
This parameter can be set when Node Type is Transit, and Outbound Bearer Type and
Inbound Bearer Type are MPLS-TP Shared Protection Ring.
The active and standby roles are configured for management convenience. The actual
service direction depends on the switching status of the shared protection ring other than
the role configurations.
Secondary Forward Label 16 to 1048575 Specifies the forward label of the standby tunnel.
Secondary Reverse Label 16 to 1048575 Specifies the reverse label of the standby tunnel.
4.1.6 Managing and Maintaining MPLS Tunnels

4.1.6.1 Modifying the Interface of the Static Unicast MPLS Tunnel
In this user interface, you can modify the static unicast MPLS tunnel that is created successfully. You can modify the following: Bandwidth, In Board/Logic interface Type, In Port, Incoming Label, Out Board/Logic Interface Type, Out Port,
Outgoing Label, and Next Hop Address.
Prerequisites

A static unicast MPLS tunnel must be created successfully.
Context
This operation may interrupt services. Exercise caution with this operation.
Procedure
1. In the NE Explorer, select an NE and then choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab.
2. Optional: Modify the interface of the unidirectional tunnel.
a. Select a created unidirectional tunnel. Click Modify and the Modify Unicast Unidirectional Tunnel dialog box is displayed.
b. Modify the interface of the static tunnel.
NOTE:
In the case of an ingress tunnel, the Out Board/Logic Interface Type, Out Port, Outgoing Label, and Next Hop Address can be changed.
In the case of a transit tunnel, the In Board/Logic Interface Type, In Port, Incoming Label, Out Board/Logic Interface Type, Out Port, Outgoing Label, and Next Hop Address can be changed.
In the case of an egress tunnel, the In Board/Logic Interface Type, In Port, and Incoming Label can be changed.
If a static MPLS tunnel is configured on a port, when changing the IP address of the port, you also need to change the next hop address of the tunnel.
3. Optional: Modify the interface of the bidirectional tunnel.
a. Select a created bidirectional tunnel. Click Modify and the Modify Unicast Bidirectional Tunnel dialog box is displayed.
b. Modify the interface of the static tunnel.
4. Click OK. The Warning dialog box is displayed, indicating that the operation may interrupt services.
5. Click OK. The Operation Result dialog box is displayed.
10 of 43 13-May-19, 7:41 PM
6. Click Close.
4.1.6.2 Deleting an MPLS Tunnel on a Per-NE Basis

To delete an MPLS tunnel using the single-station scheme, delete the MPLS tunnel at each node involved in the tunnel.
Prerequisites
Procedure
1. Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree.
2. Click the Static Tunnel tab. Select the tunnel to be deleted from the static MPLS tunnel list.
3. Click Delete. A dialog box is displayed for confirmation.
4. Follow Steps 1 - 3 to delete static tunnels for Transit nodes and the Egress node.
4.1.6.3 Testing Tunnel Connectivity on a Per-NE Basis

After a tunnel is configured, you should test tunnel connectivity by using the tunnel OAM function. This ensures that the subsequent service configuration and verification are successful.
Prerequisites

An MPLS tunnel must be configured.
The MPLS OAM function must be enabled.
Context
PTN 910/950: Table 4-11 list the Mapping between MPLS Tunnel types and Tunnel Ping/Tunnel Traceroute reply modes.
Table 4-11 Mapping between MPLS Tunnel types and Tunnel Ping/Tunnel Traceroute reply modes
MPLS Tunnel types Supported reply modes Recommended reply modes
Static Unidirectional MPLS Tunnel No Response No Response
Static Bidirectional MPLS Tunnel Application Control Channel Application Control Channel
No Response
Dynamic Tunnel IPv4 UDP Response IPv4 UDP Response

No Response
Procedure
1. Conduct a Tunnel ping test.
a. Select the NE in the NE Explorer. From the Function Tree, choose Configuration > MPLS Mangagement > Unicast Tunnel Management.
b. Click the OAM Parameters tab, and select a tunnel. Then, click OAM Operation, and select Ping Test. The Ping Test dialog box is displayed.
NOTE:
To support the ping test, Node Type of a unidirectional tunnel must be Ingress.
c. Set the related parameters. Table 4-12 lists the parameters for the ping test.
Table 4-12 Parameters for the ping test
Field Value Remarks
Packet Count For example: 3 Specifies the number of packets.
EXP Value 0-7 Specifies the EXP value.

The packet priority increases with the EXP value.
TTL 1-255 Specifies the time to live (TTL).
Transmit Interval (10ms) 10-1000 Specifies the interval of transmitting packets.
Packet Length 65-1400 Specifies the length of packets with a step of 4.
Wait-to-Response Timeout Time (10ms) 50-6000 Specifies the wait-to-response timeout time.
Response Mode No Response No Response: The peer NE receives ping packets but do not send reply
IPv4 UDP Response packets. Instead, it directly reports an event.
Application Control Channel IPv4 UDP Response: The peer NE receives ping packets and sends reply
packets over dynamic links.
Application Control Channel: The peer NE receives ping packets and
sends reply packets over static tunnels.
Test Result A character string Displays the test results.
d. Click Start Test to start the test.

e. In the test results, check the ping test data to determine whether the tunnel is successfully created.
If the test data is normal, it indicates that the tunnel is successfully created.
If the test data is abnormal, it indicates that the tunnel creation fails. Then, go to the next step.
If one of the following situations occurs, it is determined that the tunnel creation fails.
The number of response ping packets is different from the number of transmitted ping packets.
The packet loss ratio is excessively high.
2. Conduct a tunnel traceroute test.
a. Select the NE in the NE Explorer. From the Function Tree, choose Configuration > MPLS Mangagement > Unicast Tunnel Management.
b. Click the OAM Parameters tab, and select a tunnel. Then, click OAM Operation , and select Test. The Traceroute Test dialog box is displayed.
NOTE:
To support the traceroute test, Node Type of a tunnel must be Ingress.
c. Set the related parameters. Table 4-13 lists the parameters for the traceroute test.
11 of 43 13-May-19, 7:41 PM
Table 4-13 Parameters for the traceroute test
Field Value Remarks
EXP Value 0-7 Specifies the EXP value.

The packet priority increases with the EXP value.
TTL 1-255 Specifies the TTL.
Packet Length 89-1400 Specifies the length of packets with a step of 4.
Wait-to-Response Timeout Time (10ms) 50-6000 Specifies the wait-to-response timeout time.
NOTE:
The range of the wait-to-response timeout time varies according to the equipment type. If
the wait-to-response timeout time is beyond the range, an error message is displayed on the
NMS.
Response Mode No Response,IPv4 UDP Response, Application Control Channel Specifies the response mode.
Test Result A character string Displays the test results.
d. Click Start Test to start the test.

e. According to the traceroute test results, you can locate a fault and rectify the fault. If the ping test data is normal, it indicates that the tunnel creation is successful and tunnel connectivity is good.
In the case of a dynamic tunnel, the possible faults are as follows:
Hardware faults, such as board or fiber faults
Incorrect parameter setting for a dynamic tunnel, such as incorrect RSVP parameter setting, or RSVP parameter setting inconsistent with the parameters in the network planning
Incorrect dynamic routing protocol configuration, such as incorrect IS-IS configuration, or IS-IS configuration inconsistent with the parameters in the network planning
In the case of a static tunnel, the possible faults are as follows:

Hardware faults, such as board or fiber faults
Incorrect parameter setting for a static tunnel, such as incorrect setting of the incoming label, outgoing label, next hop address, source node, or sink node, or setting of these parameters inconsistent with the
parameters in the network planning
4.1.6.4 Checking the Correctness of the Tunnel Configuration in End-to-End Mode

After configuring a tunnel, you can check the connectivity of the tunnel by using the Test and Check function.
Prerequisites

Only deployed tunnels support this operation.
Procedure
1. Choose Service > Tunnel > Manage Tunnel from the Main Menu.
2. In the Set Filter Criteria dialog box, set filter criteria as required. Then click Filter. The services meeting the filter criteria are displayed in the query result area.
3. Right-click a service and choose Test and Check from the shortcut menu.
4. On the Configuration tab, select the paths to be commissioned. Click Options and select the path construction mode for the tunnel.
To check the tunnel based on the predefined check items and sequence, select Fault Check for one-key service fault location. Alternatively, select one or more check items, for example, Service Configuration Check and LSP Ping to check
the tunnel.
Select Fault Check and click Run. Then you can query the reason why the running status of the deployed dynamic tunnel is Down.
5. Click Run to check default items for the selected paths.
NOTE:
Information displayed on the Result tab page varies according to check items. The following figure shows the diagnosis results for Fault Check. The results for other check items are simple and not described here.
Check steps are ordered in logical sequence. You can reference the order for troubleshooting.
The check items vary according the static or dynamic tunnel type. For example, Service Configuration Check is applicable to static tunnels and static CR tunnels. Whether Out Interface and In Interface for the neighboring nodes of a tunnel are on the same network segment can
be checked. If they are on different network segments, Out Interface IP Address and In Interface IP Address are highlighted in red.
After completing the fault location, you can perform the following operations on the Result tab page:
In Check Result, check whether the test is successful. To view more information, click under Details.
When the check item is Service Configuration Check, click under Details to modify service attributes.
The following topology view shows the navigation path to OAM Tools. You can select the NE to be checked, right-click, and choose desired check items from the shortcut menu for further check.
Follow-up Procedure
You can save or print the test and check result.

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying PWs over the IP tunnel. In this way, services can be transparently transmitted in an IP network.
12 of 43 13-May-19, 7:41 PM
4.2.1 IP Tunnel Overview

IP tunnel can be used to carry the ATM service, the CES service or the Ethernet service.
If ATM or CES emulation service that travels through an IP network is required, the PTN equipment can use the IP tunnel to carry the service. Figure 4-4 shows the protocol stack model of the ATM service. In the case of IP tunnel, the situation is a case
where "IP header" replaces the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network. An ATM emulation service can be provided between NE A and NE B, even though the IP network between NE A and NE B does not
support the MPLS.
Figure 4-4 ATM PWE3 over IP tunnel
4.2.2 IP Tunnel Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-14 IP tunnel specifications
Configuring an IP tunnel - √ √ √
4.2.3 IP Tunnel Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-15 IP tunnel specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring an IP tunnel - √ √ √ ×
Table 4-16 IP tunnel specifications (on the PTN 905A, PTN 905B, PTN 906A and PTN 906B)
Configuring an IP tunnel - × × × ×
4.2.4 Creating an IP Tunnel in End-to-End Mode

To create an IP tunnel in end-to-end mode, directly select the source NE and sink NE for the IP tunnel on the physical topology.
Prerequisites

You must complete the correct configuration of the port attributes.
You must complete the correct setting of the LSR ID for each NE.
The control plane must be configured for the RSVP-TE,IP tunnels.
Procedure
1. Choose Service > Tunnel > Create Tunnel from the Main Menu.
2. Configure basic information. Set Protocol Type to IP.
NOTE:
When you create a reverse tunnel, the U2000 automatically allocates different Tunnel Name to the forward and reverse tunnels. If you manually set Tunnel Name for the forward tunnel, the U2000 automatically set Tunnel Name to forward tunnel name+_RVS for the reverse
tunnel.
When the Protocol Type parameter is set to IP, the Signaling Type and Template parameters are not available.
3. Configure the NE list. Click the ADD button and select the source and sink NEs from the drop-down list. Then, click OK.
NOTE:
In the case of an IP tunnel, you need to specify only the source and sink nodes of the tunnel.
You can choose Add and select Virtual Node from the drop-down list to specify virtual nodes through which a tunnel travels. A virtual node simulates an NE beyond the management range of the U2000. The virtual node is used for creating a tunnel whose source NE is on the U2000 but the
sink NE is not on the U2000.
4. Configure details such as tunnel ID, egress, and destination IP address for the IP tunnel.
5. Select the Deploy check box and click OK.
NOTE:
If you clear the Deploy check box, the configuration data information is stored only on the U2000. If you select the Deploy check box, the configuration data information is stored on the U2000 and applied to NEs. By default, the Deploy check box is selected.
When you select the Deploy and Enable check box, A tunnel is available on NEs only when it is enabled.
4.2.5 Creating IP Tunnels on a per-NE basis

In the offload scenario of a mobile communication system, you can transmit the client services by connecting an IP tunnel to the DSLAM.
Prerequisites

The static route must be configured.
Procedure
1. In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel Management > IP Tunnel Management from the Function Tree.
2. Click New and the Create IP Tunnel dialog box is displayed.
NOTE:
Destination IP Address must be consistent with Sink Node IP Address in Static Route Management.
3. Set parameters.
4. Click OK. A prompt appears indicating that the operation was successful. Click Close.
13 of 43 13-May-19, 7:41 PM

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying ATM PWE3 services over generic routing encapsulation (GRE) tunnels. In this way, services can be transparently transmitted in an IP network.
4.3.1 GRE Tunnel Overview

GRE tunnel can be used to carry the ATM service, the CES service or Ethernet service.
If ATM or CES emulation service that travels through an IP network is required, the PTN equipment can use the GRE tunnel to carry the service. Figure 4-5 shows the protocol stack model of the ATM service. In the case of GRE tunnel, "GRE
encapsulation + IP header" replaces the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network. An ATM emulation service can be provided between NE A and NE B, even though the IP network between NE A and NE B does
not support the MPLS.
Figure 4-5 ATM PWE3 over GRE tunnel
4.3.2 GRE Tunnel Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-17 GRE tunnel specifications
Configuring a GRE tunnel - √ √ √
4.3.3 GRE Tunnel Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-18 GRE tunnel specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring a GRE tunnel - √ √ √ ×
Table 4-19 GRE tunnel specifications (on the PTN 905A, PTN 905B, PTN 906A and PTN 906B)
Configuring a GRE tunnel - × × × ×
4.3.4 Creating GRE Tunnels

In the offload scenario of a mobile communication system, you can transmit the client services by connecting a GRE tunnel to the digital subscriber line access multiplexer (DSLAM).
Prerequisites

The static route must be configured.
Procedure
1. In the NE Explorer, click an NE. Choose Configuration > IP/GRE Tunnel Management > GRE Tunnel Management from the Function Tree.
2. Click New and the Create GRE Tunnel dialog box is displayed.
NOTE:
Destination IP Address must be consistent with Sink Node IP Address in Static Route Management. It is the IP address of the sink port.
Only OptiX PTN 910 and OptiX PTN 950 support setting Loopback Port. When Loopback Port is set to Used, Source Board and Source Port, is unavailable. In this case, Destination IP Address is set to the LSR ID of the sink NE.
3. Set parameters.For details on the parameters for GRE tunnel, see Table 4-20.
4. Click OK. A prompt is displayed indicating that the operation is successful. Click Close.

This section describes the parameters related to the GRE Tunnel configuration.
Table 4-20 Descriptions of the parameters for GRE Tunnel Management
Tunnel ID 1-512 Display and set the tunnel ID. You can also select the automatic allocation.
Loopback Port
NOTE:
Only OptiX PTN 910 and OptiX PTN 950 support setting Loopback Port.
Source Board Example: Slot-Board Name Display and set the source board.
Source Port Example: Port (Port No.) Display and set the source port.
Destination IP Address Example: 1.16.0.3 Destination IP Address must be consistent with Sink Node IP Address in Static Route
Management. It is the IP address of the sink port.
VLAN ID Example: 5 Display and set the VLAN ID.
Protection Group Example: 1 Display the protection group.

4.4.1 Modifying a Tunnel
This topic describes how to modify a tunnel.
Prerequisites
Context
Modifying configurations of a service may interrupt the service running. Exercise caution with this operation.
Procedure
14 of 43 13-May-19, 7:41 PM
3. Select a tunnel, and then click the related tabs to modify the related parameters.
NOTE:
If Source Node, Sink Node, and Tunnel Interface for the working and protection tunnels are set to the same value, The same route is used for the working tunnel and protection tunnel in the protection group. is displayed after you click OK.
Click Yes. The U2000 configures the working and protection tunnels whose routes are the same.
Click No. The U2000 does not perform any operation.
4. Optional: If you need to modify only the basic information about a tunnel, right-click the tunnel and choose Details from the shortcut menu. In the dialog box that is displayed, modify basic information about the tunnel.
5. Click Apply.
4.4.2 Deleting a Tunnel

This topic describes how to delete a tunnel.
Prerequisites

The service must be in the undeployed state.
Context
If the service has been deployed or partially deployed, undeploy the service. Service deletion and undeloyment are potentially service-affecting. Exercise caution when you perform these operations.
Procedure
3. Right-click one or more services and choose Delete from the shortcut menu. Alternatively, select one or more services and choose Delete > Delete.
4. In the Confirm dialog box, click Yes.
4.4.3 Deleting a tunnel from the network Side

This topic describes how to delete a tunnel from the network side.
Prerequisites
Context
Deleting a tunnel from the NMS is to delete a tunnel from only the NMS. In this case, the tunnel data configured on the equipment still exists. The deleted tunnel is displayed as a discrete tunnel on the NMS.
Procedure
3. Right-click one or more services and choose Delete from Network Side from the shortcut menu. Alternatively, select one or more services and choose Delete > Delete from Network Side.
4.4.4 Undeploying a tunnel

This topic describes how to undeploy a tunnel.
Prerequisites
You are an NMS user with "Monitor Group" authority or higher.
Context
Service undeployment is potentially service-affecting. Exercise caution when you perform this operation.
Procedure
3. Right-click a service with Deployment Status being Deployed or Partially Deployment and choose Undeploy from the shortcut menu.
After the service is undeployed, the value of Deployment Status changes from Deployed or Partially Deployment to Undeployed.
Follow-up Procedure
After the service is undeployed, you can redeploy the service. If the service fails to be undeployed, you can modify the service based on the error message and undeploy the service again.
4.4.5 Viewing a Discrete Tunnel

To view a discrete tunnel facilitates the management of discrete tunnels.
Prerequisites

A discrete tunnel must exist on the U2000.
Context
Discrete tunnels are generated on the U2000 in the following situations:
Tunnel parameters are modified in the NE Explorer. The parameters include In Port, In Label, Out Port, Out Label, and Next Hop Address.
Tunnels are deleted using the Delete from Network Side button or shortcut menu option.
Discrete services can be discovered as services by using the automatic IP service discovery function.
Procedure
1. Choose Service > Tunnel > Manage Discrete Tunnel from the Main Menu.
2. In the dialog box that is displayed, set filtering criteria and click Filter.
3. On the discrete tunnel management window, select a discrete tunnel, click the corresponding tab to view details.
4. Optional: Select a discrete tunnel, click Delete button and click Yes in the dialog box displayed.
NOTE:
After tunnel parameters are modified in the NE Explorer, two discrete tunnels are displayed on the Manage Discrete Tunnel tab page, not the Manage Tunnel tab page.
4.4.6 Delete a Discrete Tunnel

You can delete a discrete tunnel.
Prerequisites

A discrete tunnel must exist on the U2000.
Context
When you delete a discrete tunnel, the service carried by the tunnel may be interrupted. Exercise caution with this operation.
Procedure
15 of 43 13-May-19, 7:41 PM
1. Choose Service > Tunnel > Manage Discrete Tunnel from the Main Menu.
2. Click Filter Criteria. In the dialog box that is displayed, set filtering criteria and click OK.
3. On the discrete tunnel management window, select one or more discrete services, click Delete. Alternatively, right-click and choose Delete from the shortcut menu.
4. In the confirm dialog box, click OK.
4.4.7 Duplicating a Tunnel

This topic describes how to quickly deploy tunnels whose configurations are similar in batches by using the tunnel attribute duplication, automatic route calculation, and label resource allocation functions.
Prerequisites

You can duplicate only static CR tunnels.
Context
The tunnel duplication function is applicable to typical IP RAN networks, such as the multipoint-point network, tangent ring, and intersecting ring. By using this function, you can quickly create and deploy tunnels whose configurations are similar.
You can duplicate a tunnel as follows:
Duplicate only a tunnel: When the original tunnel does not belong to a tunnel protection group, you can duplicate only the tunnel.
Duplicate a tunnel by protection group: The original tunnel belongs to a tunnel protection group. In this case, the U2000 automatically duplicates a tunnel protection group that is similar to the original tunnel protection group when you duplicate
such a tunnel. Only static CR tunnels can be duplicated in this mode.
Take the duplication of a tunnel as an example. As shown in Figure 4-6, a tunnel is deployed between PE1 and PE6. You can select this tunnel as the source tunnel and then duplicate multiple similar tunnels between PE2 and PE6, between PE3 and PE6,
and between PE1 and PE6. During the duplication, you can also modify the basic parameters of the new tunnels.
Figure 4-6 The Scene of copying tunnel
Procedure
2. Right-click a tunnel to be duplicated and choose Copy from the shortcut menu. The Copy Tunnel window is displayed.
If the tunnel to be duplicated does not belong to a protection group, the U2000 automatically generates two unidirectional tunnels or a bidirectional tunnel, whose direction is reverse and share the same source and sink nodes with the
tunnel to be duplicated.
If the tunnel to be duplicated belongs to a protection group, the U2000 automatically generates the tunnel who shares the same source and sink nodes with the tunnel to be duplicated and a new protection group that contains the two
tunnels.
3. Optional: Duplicate a tunnel.
a. Set Tunnel Number of Copying and click Refresh. The U2000 automatically generates the specified number of tunnels that shares the same source and sink nodes.
b. Select Create Reverse Tunnel as required. By default, Create Reverse Tunnel is selected.
c. Adjust the source and sink nodes.

Select a tunnel. In the physical topology, right-click an NE and choose Set As Source or Set As Sink from the shortcut menu.
d. Optional: In the case of a static CR tunnel, configure the route calculation for the U2000 as follows:
i. Optional: Select Auto-Calculate route. Then the U2000 automatically calculates the routes for a tunnel after you finish Steps 2 and 3.
ii. Set Restriction Bandwidth (Kbit/s).
iii. Specify route constraint nodes. Specifically, you can click Route Restriction and specify route constraint nodes in the dialog box that is displayed. Alternatively, you can specify the explicit and excluded nodes using
shortcut menu options in the physical topology.
iv. Optional: If you do not select Auto-Calculate route, click Calculate Route to calculate the routes for a tunnel in the U2000.
NOTE:
By default, the shortest route is selected from the routes that are calculated according to Restriction Bandwidth (Kbit/s) and route constraints.
e. Select a tunnel and click Details to set the detailed parameters of the tunnel.
4. Optional: Duplicate tunnels by protection group.
a. Copy Protection Group is selected by default. For details about how to duplicate a tunnel when Copy Protection Group is not selected, see 3.
b. By referring to 3.c and 3.d, adjust the source and sink nodes and configure the automatic route calculation.
NOTE:
After you change the source or sink node of a forward tunnel, the source or sink node of the reverse tunnel changes automatically.
c. Click Details. In the right-hand pane, click Hops Informationand Protection Group Information to configure details about the tunnels and parameters relevant to the protection group.
5. Select Deploy and Enable. Click OK.
4.4.8 Reoptimizing an RSVP TE Tunnel

When you reoptimize a tunnel, the trails of the tunnel are recalculated.
Prerequisites

Only deployed RSVP TE tunnels can be reoptimized and the running status of tunnel is UP.
Context
When you reoptimize a tunnel, the service may be interrupted. Exercise caution with this operation.
Procedure
3. Right-click the required tunnel and choose Reoptimize from the shortcut menu. The Reoptimization dialog box is displayed.
4. Click Add or Delete to set the route constraints for the reoptimization of the tunnel.
5. In the Confirm dialog box, click Yes. In the Reoptimization dialog box, click OK.
6. Right-click the tunnel and choose View LSP Topology from the shortcut menu to view the actual route of the tunnel after optimization.
4.4.9 Adjusting the Route for a Tunnel

This topic describes how to modify a static CR tunnel service. When certain existing Tunnel services need to be adjusted, you need to modify the related attributes.
Prerequisites

You can adjust the routes for only static CR tunnels.
Procedure
16 of 43 13-May-19, 7:41 PM
3. Right-click the tunnel to be adjusted and choose Adjust Route from the shortcut menu. In the Confirm dialog box that indicates this operation is potentially service-affecting and may affect service operation, click Yes.
4. Adjust the route for a tunnel in the Adjust Tunnel Route window.
a. Optional: Select Auto-Calculate route. Then the U2000 automatically calculates the routes for a tunnel after you finish Steps 2 and 3.
b. Set Restriction Bandwidth.
c. Specify route constraint nodes. Specifically, you can click Route Restriction and specify route constraint nodes in the dialog box that is displayed. Alternatively, you can specify the explicit and excluded nodes using shortcut menu
options in the physical topology.
d. Optional: If you do not select Auto-Calculate route, click Calculate Route to calculate the routes for a tunnel in the U2000.
NOTE:
A Layer 2 link must be configured before route calculation. For details about how to configure a Layer 2 link, see the chapter topology management section.
By default, the shortest route is selected from the routes that are calculated according to Restriction Bandwidth and route constraints.
The configured In Interface and Out Interface can be deleted using the Delete shortcut key.
5. Optional: If the tunnel belongs to a protection group, adjust the route for the protection tunnel according to Step 4.
6. Optional: Adjust the route for a non-Layer 2 link tunnel.
a. Optional: On the Hop Information tab page, click Add, and select the transit node for the tunnel in the window that is displayed.
b. Optional: Select the related transit node for the tunnel, click Delete, and click OK in the window that is displayed to delete the node.
c. Optional: If there are two or more transit nodes, select a transit node and click UP or Down to adjust its location without changing its role.
d. Click Apply.
7. Click OK. The Management Tunnel window is displayed.

8. Click Topology to view the adjusted route for the tunnel in the topology view.
4.4.10 Perform Tunnel Protection Group Switching

On the U2000, you can perform tunnel protection switching.
Prerequisites

You must complete the creation of the tunnel protection group and enable the protocol status.
Context
1+1 protection (PTN 3900/3900-8/1900/910/910-F/950)

Services are transmitted over the working tunnel and protection tunnel at the same time. Then, the receive end selects a tunnel according to the status of the two tunnels and receives the services from the tunnel. That is, the services are dually fed
and selectively received. When the receive end detects loss of signals over the working tunnel or when the working tunnel is detected as faulty by the MPLS OAM, the receive end receives the signals from the protection tunnel. In this manner,
the services are switched.
1:1 protection
Normally, services are transmitted over the working tunnel. That is, the services are singly fed and received. When the working tunnel is faulty, the equipment at the two ends negotiates through the APS protocol. Then, the transmit end transmits
the services over the protection tunnel and the receive end receives the services from the protection tunnel. In this manner, the services are switched.
When other switching operations, excluding the exercise switching, are performed, the services may be interrupted.
Procedure
1. Choose Service > Tunnel > Manage Protection Group from the Main Menu.
2. Check the switching status of the tunnel protection group. Right-click the protection group under test, and choose Query Switching Status from the shortcut menu to refresh the status of the tunnel protection group.
3. Optional: When the Protocol Status is Disabled for the protection group, click Hop Information tab, set Protocol Status to Enabled for the device of protection group, click Apply.
NOTE:
When the Protocol Status is Enabled, you can perform tunnel protection switching.
4. Perform tunnel protection group switching.
a. Optional: Right-click one or more protection groups under test, and choose Switch > Clear.
b. Optional: Right-click one or more protection groups under test, and choose Switch > Force Switching.
c. Optional: Right-click one or more protection groups under test, and choose Switch > Manual Switching To Working.
d. Optional: Right-click one or more protection groups under test, and choose Switch > Manual Switching To Protection.
e. Optional: Right-click one or more protection groups under test, and choose Switch > Exercise Switching.
f. Optional: Right-click one or more protection groups under test, and choose Switch > Lockout of Protection.
5. Repeat step 2, Query the switching status of the protection group.
4.4.11 Querying Tunnels Carried by a Fiber

This topic describes how to query tunnels carried by a fiber. This operation helps you manage tunnels and query bandwidth usage on ports at both ends of a fiber and bandwidth usage of a tunnel carried by a fiber.
Prerequisites
Procedure
1. In the Main Topology, right-click a fiber and choose Browse Relevant Tunnels from the shortcut menu. In the window that is displayed, view the information about the tunnels.
NOTE:
In the window that is displayed, the tunnels that pass through the fiber port are displayed. The table headings can be ordered.
You can click Filter Criteria to filter the tunnels again.
2. Click Port BW Utilization. In the window that is displayed, query the bandwidth usage of the tunnels of the port and bandwidth usage of the PWs carried by the tunnels.
3. Optional: In the tunnel list, select a tunnel that carries a service, and click Correlated Services to view the information about the service.
4. Optional: On the Correlated Services tab page, click Utilization of Tunnel Bandwidth. In the window that is displayed, view bandwidth usage of the tunnel and of the PW carried by the tunnel.
4.4.12 Viewing the VPN Service Carried on a Tunnel

After viewing VPN services that are transmitted in a tunnel, you can conveniently manage the tunnel and the VPN services.
Prerequisites
Procedure
3. Right-click a required tunnel and choose View VPN from the shortcut menu.
NOTE:
You can view the VPN service of only one tunnel at a time.
You can view the end-to-end services that are transmitted in a tunnel, but not the discrete services that are transmitted in the tunnel.
4. View information of the VPN service carried on the tunnel in View VPN window.
5. Optional: Select a required VPN service, click View Details. In the relevant service management window, you can view or modify parameters of the VPN service.
4.4.13 Viewing the Topology of a Tunnel

This topic describes how to view the topology of a tunnel.
Prerequisites
17 of 43 13-May-19, 7:41 PM
Procedure
3. Select a required tunnel and view the topology of the tunnel on the Topology tab.
4. View Layer 2 link information.
a. In the Topology window, click .
b. Click .
5. In the service topology, you can perform the following operations:
a. Select an NE in the service topology, right-click, and then perform the following steps:
i. Choose Current Alarm from the shortcut menu to view current alarms.
ii. Choose History Alarm from the shortcut menu to view historical alarms.
iii. Choose NE Explorer from the shortcut menu to jump to the NE management window of the selected NE.
iv. Choose View Real-Time Performance from the shortcut menu to view real-time performance.
NOTE:
Real-time performance of only tunnels in the deployed state can be viewed.
b. Select a tunnel in the service topology, right-click, and then perform the following steps:
i. Choose Fast Diagnose from the shortcut menu to diagnose the selected tunnel.
ii. Choose View VPN from the shortcut menu to view the VPN service bound to the selected tunnel.
iii. Choose View LSP Topology from the shortcut menu to view the LSP topology of the selected tunnel.
NOTE:
LSP topologies of only RSVP TE tunnels in the running state can be viewed.
iv. Choose Current Alarm from the shortcut menu to view current alarms.
v. Choose History Alarm from the shortcut menu to view historical alarms.
c. Perform one of the following operations without selecting any NE or link:

Right-click in the blank area and choose Legend from the shortcut menu. The legend is displayed in the topology view.
Right-click in the blank area and choose Toolbar from the shortcut menu. The toolbar is displayed in the topology view.
Right-click in the blank area and choose Synchronize the Main Topology Coordinates to refresh the current topology view according to the NE layout in the Main Topology.
Right-click in the blank area and choose Save Position from the shortcut menu to save the current NE layout.
Right-click in the blank area and choose Show Service Panel from the shortcut menu to display tunnel and Layer 2 link information in the left pane.
6. Optional: In the window for creating a tunnel, click the Service Topology tab to view topology information about the new tunnel.
4.4.14 Viewing the LSP Topology of a Tunnel

This topic describes how to view the LSP topology of a tunnel. To view the actual routing information about a tunnel, you can perform this operation. If alarms are generated for multiple tunnels, you can query the LSP topologies of the tunnels in batches
to check whether the alarms are generated because of the same node fault.
Prerequisites

Only Static Tunnel, Static CR Tunnel, RSVP TE tunnels for which Deployment Status is set to Deployed support this function.
Procedure
1. Query the LSP topology of a single tunnel.
a. Choose Service > Tunnel > Manage Tunnel from the Main Menu.
b. In the Set Filter Criteria dialog box, set filter criteria as required. Then click Filter. The services meeting the filter criteria are displayed in the query result area.
c. Select the desired tunnel and click View LSP Topology on the Topology tab page to view the routing information about the tunnel. The routing information is displayed in a table on the left and in a topology view on the right.
2. Query LSP topologies of tunnels in batches.
a. Choose Service > Tunnel > Manage Tunnel from the Main Menu.
b. In the dialog box that is displayed, set filter criteria and click Filter.
c. Select one or more tunnels, right-click, and choose View LSP Topology from the shortcut menu.
d. In the Confirm dialog box, click OK. The window switches to the Main Topology and routing information about the tunnels is displayed.
4.4.15 Monitoring the Running Status of a Tunnel

By using this function, you can view the running status of a tunnel in real time.
Prerequisites

Only RSVP TE tunnel support this operation.
Procedure
3. Right-click the tunnel and select Update Running Status, view the Running Status parameter of a tunnel.
4.4.16 Monitoring the Alarms of a Tunnel

This topic describes how to monitor alarms of a PWE3 service. By creating a service monitoring template, you can monitor the service alarms concerned by users, know the service running status in time, and guarantee the normal service running.
Prerequisites
Procedure
18 of 43 13-May-19, 7:41 PM
1. Choose Fault > Service Monitoring > IP Service Monitoring Template from the main menu.
2. Right-click in the list area and choose Select Monitoring Group from the shortcut menu. Alternatively, click Select Monitoring Group in the lower right corner.
3. In the dialog box that is displayed, select the desired monitoring group and then click OK.
NOTE:
If no desired monitoring group is available, you can click Add in the dialog box that is displayed to create a monitoring group.
4. Right-click the selected monitor group and choose Add Monitoring Service from the shortcut menu.
5. In the dialog box that is displayed, select the service to be monitored, and then click Add.
NOTE:
After adding the service to be monitored, double-click the cell in the row of the service to switch to the service.
Choose Service > Tunnel > Manage Tunnel from the Main Menu. In the Manage Tunnel dialog box, select a service, right-click, and choose Add To Monitoring Group from the shortcut menu. In this manner, you can also add a service to the monitor group.
4.4.17 Viewing Tunnel Alarms

This topic describes how to view the alarms of a tunnel.
Prerequisites
Procedure
2. In the Set Filter Criteria dialog box, set filter criteria as required. Then click Filter. The services meeting the filter criteria are displayed in the query result area. View the service of tunnel by 3 or 4.
3. Optional: View the relevant alarm of tunnel.
Right-click the tunnel with the alarm and choose Alarm > Current Alarm from the shortcut menu to view the current alarms of the tunnel.
Right-click the tunnel and choose Alarm > History Alarm from the shortcut menu to view the history alarms of the tunnel.
4. Optional: View the alarms of tunnels by layer.
a. Expand the service panel.

You can expand the service panel with any of the following methods:
Method 1: Select a service. In the Topology window, click .

Method 2: Select a service. In the Topology window, right-click the blank area and choose Show Service Panel from the shortcut menu.
b. Click to view Alarm Severity of links that carries tunnel.
c. Right-click the link where an alarm is generated and choose Current Alarm/History Alarm from the shortcut menu to view current/history alarms.
5. Select the service alarm in the alarm list and view the detailed alarm information in the details area.
4.4.18 Monitoring the Performance of a Tunnel

This topic describes how to monitor the performance of a Tunnel service. A PWE3 service may be abnormal during the daily running. The abnormality can be known through the performance data of the Tunnel service. This helps to take measures in time
to prevent faults.
Prerequisites

Only support the deployed tunnel.
Procedure
3. View the runtime performance of a tunnel. Right-click the NE and choose View Real-Time Performance from the shortcut menu in the topology view.
NOTE:
Only the source node of RSVP TE tunnel support this operation.
Only the source and sink node of Static CR tunnel support this operation.
4. Create a monitoring instance for a tunnel. For detailed operations, see Enabling the Performance Monitoring and Management Function in the "Supporting Tasks".
5. View the history performance of a tunnel. Right-click a required tunnel and choose Performance > View History Data from the shortcut menu.
4.4.19 Diagnosing a Tunnel

This topic describes how to diagnose a tunnel by performing the LSP ping and LSP tracert tests. This topic describes how to diagnose Tunnel services rapidly. If a Tunnel service alarm is generated or you need to learn running conditions of a Tunnel
service, no diagnosis task is required and you can directly use this function to learn Tunnel service connectivity and locate the fault rapidly in the Tunnel service.
Prerequisites

In the case of a static CR tunnel, the IS-IS protocol must be enabled on the source and sink ports of an MPLS tunnel. Alternatively, a diagnose test must be initiated at the local NE and a static route in control plane must be configured on the opposite NE.
Only the deployed tunnel support this function.
Procedure
3. Configure a scheduled test.
a. Right-click a required tunnel and choose Diagnose > Create Test Suite from the shortcut menu.
b. Select the tunnel to be diagnosed and click Next.
c. Select the LSP Ping check box and click Details. In the dialog box that is displayed, set advance test parameters and click OK.
d. Set parameters in the Test Time field, click Add, and then click Finish.
4. View the test strategy.
a. Right-click a required tunnel and choose Diagnose > View Test Strategy from the shortcut menu.
b. Click Condition. In the dialog box that is displayed, set relevant criteria and click OK. Click Query.
c. Select a record and click Task Information and Associated Test Suite to view relevant information.
5. View the result of a scheduled test.
a. Right-click a required tunnel and choose Diagnose > View Test Result from the shortcut menu.
b. Click Query to view the result of a scheduled test.
c. Optional: Click Export Result to export the result of the scheduled test to local computer.
NOTE:
The result of a scheduled test can be exported in a .cvs, .html, .xls, .pdf or .txt file.
6. Configure a manual test.
a. Right-click a required tunnel and choose Test and Check from the shortcut menu.
b. Optional: Select Service Check or Collect Information.
c. Optional: Select the VCCV ping, LSP Ping or ICMP Ping check box and click . In the dialog box that is displayed, set parameters of the ping test and click OK.
d. Optional: Select the VCCV Traceroute, LSP Traceroute or ICMP Traceroute check box and click . In the dialog box that is displayed, set parameters of the traceroute test and click OK.
e. Click Run and view the test result on the right pane.
19 of 43 13-May-19, 7:41 PM
4.4.20 Diagnosing Tunnel Services Rapidly

This topic describes how to diagnose tunnel services rapidly. If a tunnel service alarm is generated or you need to learn running conditions of a tunnel service, no diagnosis task is required and you can directly use this function to learn network
connectivity and locate the fault rapidly by detecting the tunnel service.
Prerequisites

Deployment Status for the tunnel service to be diagnosed must be set to Deployed.
Context
The U2000 supports multiple types of diagnosis tasks for tunnel services. You can choose to locate faults in a segment-by-segment (such as PE-PE or PE-CE) or layer-by-layer manner according to service requirements or fault symptoms. The
deployment scenarios for different types of diagnosis tasks are as follows.
Table 4-21 Deployment scenarios
Diagnosis Type Function Deployment Scenario
LSP Ping This task is used to check whether an LSP is reachable. Perform this task to check connectivity of LSPs on a tunnel service.
ICMP Ping This task is used to check service connectivity at the network layer. Information such as packet loss ratio and This task is used to detect connectivity of a public network after you rectify VPN service faults.
delay in the operation results helps you learn the current network condition.
In addition, Tunnel services support LSP Traceroute, and ICMP Traceroute. The deployment scenarios are similar to those of the Ping diagnosis. The only difference is that Traceroute supports detection of transit NEs between the source and sink NEs to
obtain the packet loss ratio and delay between the source NE and each of the transit NE and determine the fault point, while Ping can check only the connectivity between the source and sink NEs.
In real-world scenarios, Ping can be performed to check the connectivity between the source and sink NEs, and then Traceroute can be used to determine the fault point.
Procedure
2. In the Set Filter Criteria dialog box, set the filter criteria. Then, click Filter. The tunnels meeting the filter criteria are displayed in the query result area.
3. Select the service to be viewed from the service list and click the Topology tab.
4. In the service topology, select the tunnel between NEs, right-click, and then choose Fast Diagnosis from the shortcut menu.
5. Set Test Type.
6. Click Run to start diagnosis. A progress bar is displayed showing the diagnosis progress. After diagnosis is complete, the diagnosis results are displayed on the Detail tab page.
Packet information such as packet loss ratio and delay is displayed in the diagnosis results. These information helps you learn the network connectivity and evaluate network path quality based on delay values.
7. Click Cancel to close the dialog box.

This topic describes the concepts, application, and configuration method of a QinQ link.
4.5.1 Introduction to QinQ Links

A QinQ link means that a VLAN tag is stuck onto the accessed packets encapsulated in QinQ mode in the egress direction of NNI-side port. With help of QinQ links, multiple UNI-side VLAN packets are encapsulated onto a VLAN on a transport
network for transport. This reduces VLAN resources on the transport network. E-Line services and E-LAN services can be carried over a QinQ link.
Basic Concepts
QinQ provides a Layer 2 virtual private network (VPN) solution. With the VLAN stacking and nesting technology, data packets carry two different VLAN tags to identify different data packets. This clears the limitation of the original solution in which
only one VLAN tag is used to identify different data packets. As a result, VLAN IDs are extended. The internal VLAN tag is referred to as C-VLAN, indicating the user VLAN; the external VLAN tag is referred to as S-VLAN, indicating the carrier
VLAN.
The main functions of the QinQ technology are as follows:
With help of the QinQ technology, the number of VLAN IDs is increased to 4094x4094. This greatly extends the VLAN ID resources.
The QinQ technology simplifies network configuration and maintenance as users and carriers can independently and flexibly plan VLAN resources.
Through the QinQ technology, the Ethernet service scale extends from the LAN to WAN.
Frame Format
The QinQ technology defines three Ethernet frame formats, including the Ethernet frame format with only a C-TAG, Ethernet frame format with a C-TAG and an S-TAG, and Ethernet frame format with only an S-TAG.
Ethernet frame with only a C-TAG
As shown in Figure 4-7, the Ethernet frame with only a C-TAG has the same format as that of the tagged frame defined in IEEE 802.1q. Hence, the tagged frame defined in IEEE 802.1q is equivalent to the Ethernet frame with only a C-TAG.
TAG has the following fields:
TPID: tagged protocol ID, which indicates TAG type, such as S-TAG and C-TAG.
Pri: priority, which indicates optimization priority.
CFI: canonical format indicator, which indicates an Ethernet frame or FDDI frame.
VLAN ID, which indicates the VLAN that the frame derives from.
Figure 4-7 Ethernet frame format with only a C-TAG
Ethernet frame format with a C-TAG and an S-TAG
As shown in Figure 4-8, in the case of the Ethernet frame with a C-TAG and an S-TAG, the S-TAG is added before the C-TAG. The differences between the S-TAG and C-TAG are as follows:
TPIDs are different.

IEEE 802.1ad defines that the TPID in an S-TAG is 0x88a8, but the TPID in a C-TAG is 0x8100.
NOTE:
The TPID in the S-TAG can be set by modifying the type domain of the QinQ frame.
The drop eligible indicator (DEI) replaces the canonical format indicator (CFI).
DEI and Pri are used together to identify the priority of an S-TAG.
Figure 4-8 Ethernet frame format with a C-TAG and an S-TAG
Ethernet frame format with only an S-TAG

As shown in Figure 4-9, the Ethernet frame has only an S-TAG.
Figure 4-9 Ethernet frame format with only an S-TAG
Application of QinQ
20 of 43 13-May-19, 7:41 PM
Application of QinQ is shown in Figure 4-10.

Figure 4-10 Application of QinQ
On this network, user packets are processed using the following procedure:
1. Assume that all CE equipment carries user packets of C-VLAN1. Then, every PE equipment sticks S-TAGs onto the data packets received from CE equipment: S-VLAN1, S-VLAN2, and S-VLAN3.
2. The PTN equipment identifies and forwards user packets by S-VLAN.
Compliant Standards and Protocols

The QinQ technology complies with the following standards and protocols:
IEEE 802.1q
IEEE 802.1ad
4.5.2 QinQ Link Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-22 QinQ link specifications
Configuring a QinQ link - √ √ √
4.5.3 QinQ Link Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-23 QinQ link specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring a QinQ link - √ √ √ √
Table 4-24 QinQ link specifications (on the PTN 905A, PTN 905B,PTN 906A and PTN 906B)
Configuring a QinQ link - √ √ √ √
4.5.4 Configuring a QinQ Link Interface

This topic describes how to configure the Ethernet port that is used to carry QinQ links.
Prerequisites
Procedure
1. On the U2000 Main Topology, select and right-click the NE. In the shortcut menu, choose NE Explorer to display the NE Explorer window.
2. In the NE Explorer, select an NE, and choose Configuration > Interface Management > Ethernet Interface from the Function Tree.
3. Click the Basic Attributes tab page, select a port to be configured. Then, set Port Mode to Layer 2 and Encapsulation Type to QinQ. Click Apply. For details on the parameters for Basic Attributes of Ethernet interfaces, see Table 3-25.
4. Click the Layer 2 Attributes tab page, set QinQ Type Domain according to the network planning. Click Apply. For details on the parameters for Layer 2 Attributes of Ethernet interfaces, see Table 3-26.
5. Click Apply to display the Operation Result dialog box, indicating that the operation is successful.
6. Click Closein the Operation Result dialog box.
4.5.5 Creating a QinQ Link

The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ encapsulation mode. In this way, multiple VLAN packets from the user-side network are encapsulated into a VLAN in the transport network for transport. The
VLAN resources in the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ link at the network side.
Prerequisites

The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must be the QinQ mode. For configuration method, see 3.5.3 Setting the General Attributes of Ethernet Interfaces.
PTN 3900/3900-8/1900: If the QoS parameters of the QinQ link need be configured, the QinQ policy must be configured first. For configuration method, see 6.5.9 Creating the QinQ Policy.
Procedure
1. In the NE Explorer, click the NE and choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree.
2. Click New. The New QinQ Link window is displayed.
3. Click the Basic Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID.
4. Click the QoS tab to set the QoS-related parameters.
NOTE:
If Bandwidth Limit is set to Enabled, you can set CIR (kbit/s) and PIR (kbit/s) for the QinQ Link. You can also select a QinQ policy in Policy. Before selecting a policy, create a policy.
For the TND1CXP board on PTN 950, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128kbps.
For the TNC1CXPG/H/I board on PTN 910, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128kbps.
For the TND3CXPA/B board on PTN 960, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128kbps.
5. Click OK.

This section describes the parameters related to the QinQ Link configuration.
Table 4-25 Descriptions of the parameters for QinQ Link Management
QinQ Link ID Example: 5 Display and set the QinQ link ID.
Board Example: 3-ETFC Display and set the board.
21 of 43 13-May-19, 7:41 PM
Port Example: Port (Port No.) Display and set the port.
S-VLAN ID Example: 4 Display and set the S-VLAN ID.
Direction Ingress, Egress Display the direction.
Bandwidth Limit Enabled, Disabled Set and display the bandwidth limit.
If Bandwidth Limit is enabled, Committed Information Rate and Peak Information
Rate can be set.
CIR(kbit/s) Example: 16000 Set and display the committed information rate.
CBS (bytes) - This parameter is not supported.
PIR (kbit/s) Example: 20000 Set and display the peak information rate.
PBS (bytes) - This parameter is not supported.
Policy 64 bytes Set and display the policy.
Query Actual Bandwidth Checked, Unchecked When this parameter is selected, the actual effective bandwidth is queried. When this
parameter is not selected, the configured bandwidth is queried.

This chapter describes the concept, application, and configuration method of the MPLS tunnel APS protection.
4.6.1 MPLS Tunnel APS Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-26 MPLS tunnel APS specifications
Creating MPLS tunnel APS protection groups on a - √ √ √

per-NE basis
Creating MPLS tunnel APS protection groups in end- - √ √ √

to-end mode
Configuring an APS receiving mode - √ √ √
Deleting an MPLS tunnel APS protection group - √ √ √
Testing MPLS tunnel APS - √ √ √
4.6.2 MPLS Tunnel APS Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-27 MPLS tunnel APS specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Creating MPLS tunnel APS protection - √ √ √ √

groups on a per-NE basis

groups in end-to-end mode
Configuring an APS receiving mode - × × × ×
Deleting an MPLS tunnel APS protection - √ √ √ √

group
Testing MPLS tunnel APS - √ √ √ √
Table 4-28 MPLS tunnel APS specifications (on the PTN 905A, PTN 905B, PTN 906A and PTN 906B)

groups on a per-NE basis

groups in end-to-end mode
Configuring an APS receiving mode - × × × ×
Deleting an MPLS tunnel APS protection - √ √ √ √

group
Testing MPLS tunnel APS - √ √ √ √
4.6.3 Configuration Flow for the Tunnel APS Protection

This section describes the configuration flow for the tunnel APS protection, involving the configuration tasks and description of each task.
Figure 4-11 shows the configuration flow for the tunnel APS protection. For details of each step, see the related sections.
Figure 4-11 Configuration flow for the tunnel APS protection
Table 4-29 Configuration tasks for the tunnel APS protection
Operation Remarks
1. Creating Network To create a network, you need to create NEs, uploading NE Data, create fibers, and configure the clock.
2.Creating a Tunnel on a Per-NE Basis An MPLS tunnel is created on a per-NE basis and the MPLS tunnel OAM function is enabled.
3.Creating an MPLS APS Protection Group An APS protection group should be respectively configured at the source and sink of a tunnel.
4.Enable APS Protocol When an MPLS APS protection group is configured, the APS protocol must be disabled. After the MPLS APS protection group is
created, enable the APS protocol.
4.6.4 Creating an MPLS Tunnel APS Protection Group

4.6.4.1 Creating an MPLS Tunnel APS Protection Group on a Per-NE Basis
You can create a tunnel protection group to protect tunnels. You can configure 1+1 protection and 1:1 protection in a tunnel protection group. To create a tunnel protection group, the tunnel protection group must be configured at the source and sink NEs
of the tunnel.
Prerequisites

The working and protection tunnels must be created.
The MPLS OAM function must be enabled for each tunnel in the protection group. For details, see 5.1.4.3.2 Enabling the CV/FFD of an MPLS Tunnel.
22 of 43 13-May-19, 7:41 PM
The MPLS OAM packet type must be set to FFD and the Detection Packet Period must be set to 3.3 ms. For details, see 5.1.4.3.2 Enabling the CV/FFD of an MPLS Tunnel.
NOTE:
Detection Packet Period (ms) must be set to 3.3 ms for MPLS OAM so that the protection switching time is within 50 ms. Extensive delay variation on a network, however, results in repeated protection switching. Hence, the detection packet period must be larger than the maximum network
delay variation.
Configuration Guide
The configuration of tunnel APS protection group must be consistent at the source and sink ends.
NOTE:
The working and protection channels should be configured on different paths. For the source and sink nodes, the working and protection channels should be configured on different processing boards or interface boards corresponding to different processing boards.For intermediate nodes, the working and
protection channels should be configured on different NEs. If the working and protection channels are configured on the same NE, the working and protection channels will fail simultaneously when the NE is faulty.
Procedure
1. Select the source NE of the tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree.
2. Click New. The New Tunnel Protection Group dialog box is displayed.
3. Set parameters for the tunnel protection group. For details on the parameters for the tunnel protection group, see Table 4-30.
Protection Type: The protection type can be 1:1 or 1+1
Switching Mode: The switching mode can be single-ended or dual-ended.
Revertive Mode: The revertive mode can be non-revertive or revertive.
Hold-off Time (100 ms): The unit is 100 milliseconds. You can enter an integer from 0 to 100, that is, 0 to 10 seconds.
Working Tunnel Type and Protection Tunnel Type can be set to tunnel, IP Tunnel, or GRE Tunnel.
NOTE:
Either bidirectional MPLS tunnels or unidirectional MPLS tunnels can be configured in an APS protection group.
One bidirectional LSP and a pair of unidirectional LSPs can protect each other.
Bidirectional MPLS tunnels can protect each other.
For OptiX PTN 3900/3900-8/1900/910/910-F/950, bidirectional MPLS tunnels and IP/GRE tunnels can protect each other.
When Transmit and Receive Status of Protocol Packet is enabled, the protection group can receive and transmit APS protocol packets and supports the APS alarm function.
When the protection and working tunnels are the MPLS tunnels, Transmit and Receive Status of Protocol Packet is set to Enabled.
For OptiX PTN 3900/3900-8/1900/910/910-F/950, when the protection tunnel is the IP/GRE tunnel, Transmit and Receive Status of Protocol Packet is set to Disabled.
When Switching upon FD/FDV is enabled, the protection group supports switching upon FD/FDV.
NOTE:
Before you enable and configure switching upon FD/FDV, be sure to configure tunnel performance monitoring. For configuration details, see Enabling the Performance Monitoring and Management Function.
NOTICE:
When creating the protection group, you must set the Protocol Status to Disabled. If you enable the APS protocol at the local NE first and then the opposite NE when configuring the MPLS APS protection, the opposite NE may have an
anomaly in receiving services.
4. Click OK. The tunnel protection group is successfully configured.
NOTE:
The bandwidth of the protection tunnel should be not less than that of the working tunnel. To increase the bandwidth of the working tunnel after the protection group is created, increase the bandwidth of the protection tunnel first.
5. Configure the protection group on the sink NE of the tunnel by following 1 to 4.

6. Enable the APS protocol for the MPLS APS protection group.
a. Select the source NE of the tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree.
b. Right-click the APS protection group that is already created to choose Start Protocol from the shortcut menu.
c. A dialog box is displayed indicating that the operation is successful. Then, the Protocol Status of the APS protection group changes to Enabled.
4.6.4.2 Creating an MPLS Tunnel APS Protection Group in End-to-End Mode

You can create an MPLS tunnel APS protection group to protect MPLS tunnels. You can configure 1+1 protection or 1:1 protection for an MPLS tunnel APS protection group.
Prerequisites

The working and protection tunnels must be created.
Configuration Guide
NOTE:
Procedure
1. Choose Service > Tunnel > Create Protection Group from the Main Menu.
23 of 43 13-May-19, 7:41 PM
2. In the Basic Information area, set basic information about the protection group. That is, set Group Name, Protection Type, and Switching Mode.For details on the parameters, see Table 4-30.
Group Name: This parameter indicates the protection group name.
Protection Type: The protection type can be 1:1 or 1+1.
Switching Mode: The switching mode can be single-ended or double-ended.
3. Click Add. In the dialog box that is displayed, select the working and protection tunnels and then click OK.
4. Set the tunnel type.
Set Protection Type to Forward Working, Backward Working, Forward Protecting, and Backward Protecting.
5. In the Attributes area, set the following protection group attributes.
Protocol Status: This parameter indicates the protocol status. A protection group takes effect only after its status is set to Enabled.
Revertive Mode: The revertive mode can be non-revertive or revertive.
WTR Time: The WTR time can be set to an integer in the range of 60 to 720 (unit: second, and 60 as the spacing). The default value of the WTR time is 300.
Hold-off Time: The hold-off time can be set to an integer in the range of 0 to 100 (0s to 10s; unit: 100 ms). The default value is 0.
Switching upon FD: Switching upon FD can be either enabled or disabled. If it is enabled, a protection group supports switching upon FD.
FD Direction: The FD direction can be either unidirectional or bidirectional.
Switching Condition: This parameter indicates the switching priorty and can be set to FD or FDV.
Enable FD Difference: This option can be either selected or not selected.
FD Difference Threshold: The FD difference threshold is an integer in the range of 100 to 65535, in microseconds.
Enable FDV Difference: This option can be either selected or not selected.
FDV Difference Threshold: The FDV difference threshold is an integer in the range of 100 to 65535, in microseconds.
6. In the Tunnel area, click Configure OAM to display the Configure OAM dialog box. Set OAM Status to Enabled, Detection Packet Type to FFD, and Detection Packet Period (ms) to 3.3 for the protection group.
OAM Status: OAM can be set to Enable Send And Receive or Disabled. OAM must be set to Enable Send And Receive when MPLS tunnel APS is configured.
Detection Packet Type: The detection packet type can be CV or FFD. When the detection packet type is CV, the packet detection period is fixed; when the detection packet type is FFD, you can set the detection packet period.
Detection Packet Period (ms): This parameter indicates the detection packet period. The detection packet period can be set to 3.3, 10, 20, 50, 100, 200, 500, or 1000 (unit: ms). When the detection packet type is FFD, this parameter
can be set; when the detection packet type is CV, this parameter is always 1000.
NOTE:
Detection Packet Type must be set to 3.3 to ensure that the switching time is within 50 ms. When delay variation on a network is large, switching occurs frequently. Detection Packet Type must be set to a value greater than the maximum delay variation on the network.
4.6.4.3 Configuring an APS Receiving Mode

MPLS tunnel APS supports either the dual receiving or selective receiving mode.
Prerequisites
Procedure
1. In the NE Explorer, select the NE from the Function Tree and choose Configuration > APS Receiving Mode.
2. Set Receiving Mode toFast, and click Apply.
NOTE:
Fast indicates the dual receiving. Normal indicates the selective receiving. The default Receiving Mode is Fast.
4.6.5 Managing and Maintaining the MPLS Tunnel APS Protection Groups
4.6.5.1 Deleting a Tunnel APS Protection Group
To delete a tunnel APS protection group, the tunnel protection groups must be deleted at the source NE and sink NE.
Prerequisites
Procedure
24 of 43 13-May-19, 7:41 PM
1. Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree.
2. Select a protection group that you want to delete.
3. Click Delete. A dialog box is displayed for confirmation.
4. Click Yes. The Operation Result dialog box is displayed.
5. Click Close.
6. On the NE Explorer, select the sink NE, and repeat the previous operations.
4.6.5.2 Testing MPLS Tunnel APS Protection

The OptiX PTN equipment supports 1+1 and 1:1 protection for MPLS tunnels, with an intention to improve the reliability of end-to-end connections through the PSN. This section describes how to test 1+1 or 1:1 MPLS tunnel protection.
Prerequisites
An MPLS tunnel protection group must be created.

You must be an NM user with "Operator Group" authority or higher.
Tools, Equipment and Materials

U2000
Context
1+1 protection
Services are transmitted over the working tunnel and protection tunnel at the same time. Then, the receive end selects a tunnel according to the status of the two tunnels and receives the services from the tunnel. That is, the services are dually fed
and selectively received. When the receive end detects loss of signals over the working tunnel or when the working tunnel is detected as faulty by the MPLS OAM, the receive end receives the signals from the protection tunnel. In this manner,
the services are switched.
1:1 protection
Normally, services are transmitted over the working tunnel. That is, the services are singly fed and received. When the working tunnel is faulty, the equipment at the two ends negotiates through the APS protocol. Then, the transmit end transmits
the services over the protection tunnel and the receive end receives the services from the protection tunnel. In this manner, the services are switched.
Procedure
1. Check the switching status of the 1+1 or 1:1 MPLS tunnel protection group.
a. On the Main Topology of the U2000, right-click the source NE of the tunnels under test. Choose NE Explorer from the shortcut menu to display the NE Explorer window.
b. In the Function Tree of NE Explorer, choose Configuration > APS Protection Management.
c. Click the Tunnel APS Configuration tab, right-click the protection group under test, and choose Query Switching Status from the shortcut menu to refresh the status of the MPLS tunnel protection group configured on the NE.
d. Select the MPLS tunnel protection group under test and check the switching status of the MPLS tunnel protection group. Normally, the status of the protection group is No Request (Working Active).
2. Switch the services to the protection tunnel.
a. In the Function Tree of NE Explorer, choose Configuration > APS Protection Management.
b. Click the Tunnel APS Configuration tab and select the protection group for service switching.
c. Right-click the protection group under test and choose Forced Switching from the shortcut menu. In this case, a message indicating that this operation will interrupt service is displayed. Then, click OK to perform the manual
switching.
3. Right-click the protection group under test and choose Query Switching Status from the shortcut menu. Check Switching Status of the protection group, which should be in Forced Switching state normally. Then, query Active Tunnel of the
protection group. After a normal switching, Working matches Standby and Protection matches Active.
NOTE:
If Forced Switching is performed at the previous step, the state of the protection group should be Forced Switching.
If Manual Switching to Protection is performed at the previous step, the state of the protection group should be Manual Switching to Protection.
4. Right-click the protection group under test and choose Clear from the shortcut menu to revert the services to the working tunnel.

This section describes the parameters related to the MPLS APS configuration.
Table 4-30 Descriptions of the parameters for APS protection
Protection Group ID Example: 1 Indicates the ID of the protection group.

The system automatically allocates IDs to protection groups according to the sequence for creating them.
Protection Type 1+1, 1:1 Specifies the protection type.

1+1 protection can work in single-ended/dual-ended revertive/non-revertive mode.
NOTE:
OptiX PTN 960 equipment support 1:1 protection. 1:1 protection can work in dual-ended revertive/non-revertive mode.
In the case of the offload protection, the OptiX PTN 910/910-F/950 support only the 1:1 protection.
Switching Mode Single-Ended, Dual-Ended Specifies the switching mode, which is adopted in the case of a fault on the tunnel.
Revertive Mode Non-Revertive, Revertive Specifies whether the service reverts to the original working tunnel after the fault is rectified. In the case of the Revertive mode, the service reverts to the original working tunnel. In
the case of the Non-Revertive mode, the service does not revert to the original working tunnel.
When the protection tunnel is the IP/GRE tunnel, Revertive Mode is always Revertive.
BDI Status Enabled, Disabled Specifies whether to enable the BDI.
WTR Time (min) 1 to 12 Specifies the wait-to-restore (WTR) time for the protection group.
Default value for MPLS APS protection: 5 WTR Time (min) for offload protection is 1 min by default.
Default value for offload protection: 1
25 of 43 13-May-19, 7:41 PM
Hold-off Time (100 ms) 0 to 100 Specifies the hold-off time of the protection group.
Default: 0 The hold-off time indicates the waiting time for the protection group after it detects trigger conditions for protection switching. During the hold-off time, the protection group stops
checking for trigger conditions for protection switching and protection switching does not occur. After the hold-off time times out, the protection group checks for trigger conditions
for protection switching again. If the protection group detects trigger conditions for protection switching, protection switching occurs.
The hold-off time is used to resolve the conflict between the protection group at the service layer and that at the upper layer when protection groups at multiple layers are coupled.
That is, the hold-off time is configured to prevent concurrent switching of protection groups at multiple layers. The value of the hold-off time must be larger than the switching time
of the protection group at the service layer.
For example, the tunnel APS protection is coupled with the LMSP protection, the LMSP protection is configured for the link carrying the working tunnel, and the LMSP protection
belongs to service-layer protection. In the case of a link fault, it is expected that the LMSP protection switching occurs first to rectify the link fault. After the LMSP protection
switching, if the working tunnel is normal, the tunnel APS protection switching does not occur. The LMSP protection switching requires a certain period of time, so you need to set
the hold-off time for the tunnel APS protection group to ensure that the LMSP can resolve problems at the service layer. The hold-off time for the tunnel APS protection group must
be larger than the LMSP protection switching time.
When the protection tunnel is the IP/GRE tunnel, Hold-off Time (100 ms) is always 0 ms.
Protocol Status Enabled, Disabled Specifies whether to enable the protocol.

When Protocol Status is enabled, the protection group takes effect.
Transmit and Receive Status of Enabled, Disabled Specifies whether to receive and transmit the APS protocol packets. If this parameter is enabled, the APS alarm can be detected.
Protocol Packet When the protection tunnel is the MPLS tunnel and the working tunnel is the IP/GRE tunnel, Transmit and Receive Status of Protocol Packet is always Enabled.
When both the protection tunnel and working tunnel are the MPLS tunnel, Transmit and Receive Status of Protocol Packet is always Enabled.
When both the protection tunnel and working tunnel are the IP/GRE Tunnel, Transmit and Receive Status of Protocol Packet is always Disabled.
Switching Status No Request (Working Active), No Request Indicates the switching status of the protection group.
(Protection Active), Lockout (Working Active),
Forced Switching(Protection Active), Working
Signal Failure (Protection Active), Protection
Signal Failure (Working Active), Protection Signal
Degrade (Working Active), Working Signal
Degrade (Protection Active), Manual Switch to
Working path, Manual Switch to Protection path,
Wait-to-Restore (Protection Active), Do Not Revert
(Protection Active), Exercise Switching (Working
Active), Exercise Switching (Protection Active),
Reverse Request (Working Active), Reverse
Request (Protection Active)
Unit Working, Protection Specifies whether a tunnel is the working or protection tunnel.
Active Tunnel Active, Standby Indicates the tunnel that is currently used.
Tunnel Status Available, Unavailable Indicates the status of the working or protection tunnel.
Tunnel Type MPLS Tunnel, IP Tunnel, GRE Tunnel Specifies the type of the working tunnel.
Tunnel Direction Unidirectional, Bidirectional Displays the direction of tunnel.
Ingress Tunnel Example: IP Tunnel-1 Specifies the working and protection ingress tunnels.
Egress Tunnel Example: Tunnel005-MPLS Tunnel-5(Source Specifies the working and protection egress tunnels.
Node:1.0.0.14,Sink Node:1.1.1.2)
Switching upon FD/FDV Enabled, Disabled Specifies whether to enable switching upon FD/FDV.
FD Direction Unidirectional, Bidirectional Specifies the FD difference.
Switching Condition FD, FDV Specifies the FD/FDV priority.
FD Difference Never trigger switching, 100-65535 Specifies the FD difference.
FDV Difference Never trigger switching, 100-65535 Specifies the FDV difference.

In the Offload solution, the IP/GRE tunnel in the wholesale managed service (WMS) network should be configured with protection to ensure that the service is protected if the IP/GRE tunnel becomes faulty.
4.7.1 Offload Protection Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-31 Offload protection specifications
Configuring offload protection - √ √ √
4.7.2 Offload Protection Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-32 Offload protection specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring offload protection - √ √ √ ×
Table 4-33 Offload protection specifications (on the PTN 905A, PTN 905B,PTN 906A and PTN 906B)
Configuring offload protection - × × × ×
4.7.3 Creating an Offload Protection Group

An offload protection group protects the HSDPA service in the leased wholesale network.
Prerequisites

The working tunnel (IP/GRE tunnel) must be created and bound to the BFD session.
The protection tunnel (MPLS/IP/GRE tunnel) must be created, the settings in 5.1.4.3.2 Enabling the CV/FFD of an MPLS Tunnel must be configured for the MPLS tunnel, and the IP/GRE tunnel must be bound to the BFD session.
Configuration Guide
NOTE:
Procedure
1. Select the source NE of the tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree.
2. Click New, the New Tunnel Protection Group dialog box is displayed.
3. Set parameters for the tunnel protection group. Select the working tunnel and protection tunnel.For details on the parameters for protection group, see Table 4-35.
NOTE:
The offload supports only the 1:1 protection.
26 of 43 13-May-19, 7:41 PM
4. Click OK. The tunnel protection group is successfully configured.

5. Display the NE Explorer of the opposite NE and perform Steps 1-4 to create a protection group on the opposite NE.

This section describes the parameters related to the Offload protection configuration.
Table 4-34 Descriptions of the parameters for BFD Management
Parameter Value Description
Session Type Single-Hop, Multi-Hop Selects the BFD session type.

Single-Hop: Establish the BFD session for the link with one hop.
Multi-Hop: Establish the BFD session for the link with multiple hops.
Session ID Example: 5 Displays the ID of the BFD session.
Board Example: 23-ETFC Selects the board that transmits BFD packets.
Port Example: 1(PORT-1) Selects the port that transmits BFD packets.
Source Port IP Address Example: 10.70.12.33 Sets the IP address of the source port.
Sink Port IP Address Example: 10.70.12.34 Sets the IP address of the sink port.
Local Identifier Automatically Assign Displays the local identifier.
Remote Identifier Automatically Assign Displays the remote identifier.
Bound Port Example: Slot-Board Name-Port (Port No.) Configures the port bound with the BFD session status.
Bound Tunnel IP Tunnel:Tunnel ID(Sink Port IP Address), GRE Tunnel ID(Sink Port IP Address) Configures the bound tunnel for offload Protection.
Session Status Up, Down, AdminDown, Init Displays the BFD session status.
Admin Status Up, Down Configures the administration status.

Up: BFD session supported.
Down: BFD session not supported. If Admin Status is set to Down, Session
Status is displayed only as Down.
Local Send Interval of Packets(ms) 3 to 1000 Sets the local send interval of packets.
NOTE:
The interval between sending/receiving packets that PTN devices actually support is 3.3 ms, 10 ms,
20 ms, 50 ms, 100 ms, and 1s. If a configured value is different from the actually supported values,
a value close to and greater than the configured value is used by default. For example, if the
configured value is 150 ms, 1s is used by default.
Local Receive Interval of Packets(ms) 3 to 1000 Sets the local receive interval of packets.
NOTE:
The interval between sending/receiving packets that PTN devices actually support is 3.3 ms, 10 ms,
20 ms, 50 ms, 100 ms, and 1s. If a configured value is different from the actually supported values,
a value close to and greater than the configured value is used by default. For example, if the
configured value is 150 ms, 1s is used by default.
Local Detection Multiple of Packets 3 to 10 Sets the BFD packet detection multiples at the local end.
Negotiated Local Send Interval of Packets(ms) Example: 568 Displays the negotiated interval of transmitting packets at the local end.
Negotiated Local Receive Interval of Packets(ms) Example: 568 Displays the negotiated interval of receiving packets at the local end.
Negotiated Detection Time of Packets(ms) Example: 5 Displays the negotiated packet detection time at the local end.
Diagnosis Word 0 to 9 Indicates the cause of the state change of the latest session in the local BFD system.
0: indicates that no diagnosis word is available.
1: indicates that the detection time expires.
2: indicates that detection for echo packets fails.
3: indicates that neighbor notification fails.
4: indicates that the forwarding plane restarts.
5: indicates that the trail is down.
6: indicates that the concatenated trail fails.
7: indicates that the BFD session is administratively disabled.
8: indicates that the reverse concatenated trail fails.
9: indicates that ADMIN_DOWN packets are received.
VRF Example: vpn1 If Session Type is set to Multi-Hop, the VRF is supported to be set.
Displays the name of the public network VPN routes by default.
NOTICE:
For the OptiX PTN equipment, multi-hop BFDs can be bound to public VPN routes only.
VRF ID Example: 1 Sets the ID for the VRF.
VPN Name Example: vpn1 Sets the name of the VPN.
RD Example: 100 Specifies the RD of a VPN instance. RDs are used to isolate VPN address spaces. A VPN
instance takes effect only after being configured with an RD.
Table 4-35 Descriptions of the parameters for APS protection
Protection Group ID Example: 1 Indicates the ID of the protection group.

The system automatically allocates IDs to protection groups according to the sequence for creating them.
Protection Type 1+1, 1:1 Specifies the protection type.

1+1 protection can work in single-ended/dual-ended revertive/non-revertive mode.
NOTE:
OptiX PTN 960 equipment support 1:1 protection. 1:1 protection can work in dual-ended revertive/non-revertive mode.
In the case of the offload protection, the OptiX PTN 910/910-F/950 support only the 1:1 protection.
Switching Mode Single-Ended, Dual-Ended Specifies the switching mode, which is adopted in the case of a fault on the tunnel.
Revertive Mode Non-Revertive, Revertive Specifies whether the service reverts to the original working tunnel after the fault is rectified. In the case of the Revertive mode, the service reverts to the original working tunnel. In
the case of the Non-Revertive mode, the service does not revert to the original working tunnel.
When the protection tunnel is the IP/GRE tunnel, Revertive Mode is always Revertive.
BDI Status Enabled, Disabled Specifies whether to enable the BDI.
27 of 43 13-May-19, 7:41 PM
WTR Time (min) 1 to 12 Specifies the wait-to-restore (WTR) time for the protection group.
Default value for MPLS APS protection: 5 WTR Time (min) for offload protection is 1 min by default.
Default value for offload protection: 1
Hold-off Time (100 ms) 0 to 100 Specifies the hold-off time of the protection group.
Default: 0 The hold-off time indicates the waiting time for the protection group after it detects trigger conditions for protection switching. During the hold-off time, the protection group stops
checking for trigger conditions for protection switching and protection switching does not occur. After the hold-off time times out, the protection group checks for trigger conditions
for protection switching again. If the protection group detects trigger conditions for protection switching, protection switching occurs.
The hold-off time is used to resolve the conflict between the protection group at the service layer and that at the upper layer when protection groups at multiple layers are coupled.
That is, the hold-off time is configured to prevent concurrent switching of protection groups at multiple layers. The value of the hold-off time must be larger than the switching time
of the protection group at the service layer.
For example, the tunnel APS protection is coupled with the LMSP protection, the LMSP protection is configured for the link carrying the working tunnel, and the LMSP protection
belongs to service-layer protection. In the case of a link fault, it is expected that the LMSP protection switching occurs first to rectify the link fault. After the LMSP protection
switching, if the working tunnel is normal, the tunnel APS protection switching does not occur. The LMSP protection switching requires a certain period of time, so you need to set
the hold-off time for the tunnel APS protection group to ensure that the LMSP can resolve problems at the service layer. The hold-off time for the tunnel APS protection group must
be larger than the LMSP protection switching time.
When the protection tunnel is the IP/GRE tunnel, Hold-off Time (100 ms) is always 0 ms.
Protocol Status Enabled, Disabled Specifies whether to enable the protocol.

When Protocol Status is enabled, the protection group takes effect.
Transmit and Receive Status of Enabled, Disabled Specifies whether to receive and transmit the APS protocol packets. If this parameter is enabled, the APS alarm can be detected.
Protocol Packet When the protection tunnel is the MPLS tunnel and the working tunnel is the IP/GRE tunnel, Transmit and Receive Status of Protocol Packet is always Enabled.
When both the protection tunnel and working tunnel are the MPLS tunnel, Transmit and Receive Status of Protocol Packet is always Enabled.
When both the protection tunnel and working tunnel are the IP/GRE Tunnel, Transmit and Receive Status of Protocol Packet is always Disabled.
Switching Status No Request (Working Active), No Request Indicates the switching status of the protection group.
(Protection Active), Lockout (Working Active),
Forced Switching(Protection Active), Working
Signal Failure (Protection Active), Protection
Signal Failure (Working Active), Protection Signal
Degrade (Working Active), Working Signal
Degrade (Protection Active), Manual Switch to
Working path, Manual Switch to Protection path,
Wait-to-Restore (Protection Active), Do Not Revert
(Protection Active), Exercise Switching (Working
Active), Exercise Switching (Protection Active),
Reverse Request (Working Active), Reverse
Request (Protection Active)
Unit Working, Protection Specifies whether a tunnel is the working or protection tunnel.
Active Tunnel Active, Standby Indicates the tunnel that is currently used.
Tunnel Status Available, Unavailable Indicates the status of the working or protection tunnel.
Tunnel Type MPLS Tunnel, IP Tunnel, GRE Tunnel Specifies the type of the working tunnel.
Tunnel Direction Unidirectional, Bidirectional Displays the direction of tunnel.
Ingress Tunnel Example: IP Tunnel-1 Specifies the working and protection ingress tunnels.
Egress Tunnel Example: Tunnel005-MPLS Tunnel-5(Source Specifies the working and protection egress tunnels.
Node:1.0.0.14,Sink Node:1.1.1.2)

MPLS-TP ring protection applies to a single ring and intersecting rings, which has incomparable advantages over linear protection. This topic describes basic concepts and configuration methods of MPLS-TP ring protection.
4.8.1 MPLS-TP Ring Network Protection Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-36 MPLS-TP ring network protection specifications
Creating an MPLS-TP ring - √ √ √
Creating an intersecting node for MPLS-TP ring - √ √ √

network protection
Configuring an MPLS-TP ring network binding - √ √ √
Testing connectivity of an MPLS-TP ring network - √ √ √
Testing the ring protection switching - √ √ √
Configuring ring network protection for VPLS - √ √ √

services
4.8.2 MPLS-TP Ring Network Protection Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-37 MPLS-TP ring network protection specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Creating an MPLS-TP ring - √ √ √ √
Creating an intersecting node for MPLS-TP - √ √ √ √

ring network protection
Configuring an MPLS-TP ring network - √ √ √ √

binding
Testing connectivity of an MPLS-TP ring - √ √ √ √

network
Testing the ring protection switching - √ √ √ √
Configuring ring network protection for - × × × ×

VPLS services
Table 4-38 MPLS-TP ring network protection specifications (on the PTN 905A, PTN 905B, PTN 906A and PTN 906B)
Creating an MPLS-TP ring - × × × ×
Creating an intersecting node for MPLS-TP - × × × ×

ring network protection
Configuring an MPLS-TP ring network - × × × ×

binding
Testing connectivity of an MPLS-TP ring - × × × ×

network
Testing the ring protection switching - × × × ×
Configuring ring network protection for - × × × ×

VPLS services
4.8.3 MPLS-TP Ring Protection Configuration Process
28 of 43 13-May-19, 7:41 PM
This topic describes the process of configuring MPLS-TP ring protection.
NOTICE:
Before configuring MPLS-TP ring binding, ensure that the MPLS-TP ring protection group is functioning properly, avoiding service interruption after the binding. For details, see 4.8.5.1 Checking the Correctness of MPLS-TP Protection Ring.
Figure 4-12 shows the configuration process of MPLS-TP single-ring protection. For details on each task, see the corresponding topic.
Figure 4-12 Configuration process of MPLS-TP single-ring protection
Table 4-39 Configuration tasks for MPLS-TP single-ring protection
Task Remarks
2. Configuring the Interface Set the Basic Attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying.
3. Configuring the Tunnel Configure a static MPLS tunnel.
Configure an MPLS tunnel in the per-NE or end-to-end mode. Specify the tunnel ID, set signaling type to static CR, name the tunnel, and specify the ingress node, egress node, and transit node.
4. Creating an MPLS-TP Protection Ring Set the ring name, east/west interfaces, OAM attributes, APS attributes, and advanced attributes.
5. Configuring an MPLS-TP Ring Binding Bind a static MPLS tunnel to the MPLS-TP ring protection.
Figure 4-13 shows the configuration process of MPLS-TP intersecting-ring protection. You are advised to configure and manage the MPLS-TP ring protection based on this process.
Figure 4-13 Configuration process of MPLS-TP intersecting-ring protection
Table 4-40 Configuration tasks for MPLS-TP intersecting-ring protection
Task Remarks
2. Configuring the Interface Set the Basic Attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying.
3. Configuring the Tunnel Configure a static MPLS tunnel.
Configure an MPLS tunnel in the per-NE or end-to-end mode. Specify the tunnel ID, set signaling type to static CR, name the tunnel, and specify the ingress node, egress node, and transit node.
4. Creating MPLS-TP Protection Rings Set the ring names, east/west interfaces, OAM attributes, APS attributes, and advanced attributes.
5. Configuring Intersecting Nodes for MPLS-TP Ring Protection Configure intersecting nodes to achieve cross-ring protection.
6. Configuring an MPLS-TP Ring Binding Bind a static MPLS tunnel to the MPLS-TP ring protection.
4.8.4 Creating MPLS-TP Ring Protection

4.8.4.1 Creating an MPLS-TP Ring
This topic describes how to create an MPLS-TP ring in end-to-end mode to protect static MPLS tunnels.
Prerequisites

Ports must be configured in Layer 3 mode or VLAN sub-interfaces must be created. In addition, the tunnel enabling status must be set to enabled and IP address must be set for the ports.
PTN 910/910-F/950/960: Each node on the ring must have the same OAM standard.
PTN 3900/3900-8/1900: Each node on the ring must work in dual-stack mode and have the same OAM standard.
Context
It is recommended that you add NEs clockwise or anti-clockwise on the main topology. Then the NMS creates an MPLS protection ring according to the sequence in which NEs are added.
Each node on a ring network uses two ports to transmit and receive data. The two ports are referred to as east or west ports according to their roles on the ring topology. The west or east attribute is independent of the NE positions on the physical
topology, but depends on the order in which NEs are added .East and west interfaces are generated as follows:
If NEs are added to a ring network clockwise, the clockwise inbound interfaces are east interfaces, and the clockwise outbound interfaces are west interfaces.
If NEs are added to a ring network clockwise, the clockwise inbound interfaces are east interfaces, and the counterclockwise outbound interfaces are west interfaces.
Configuration Guide
29 of 43 13-May-19, 7:41 PM
NOTE:
PTN 3900/3900-8/1900/910/950/960: On a ring network, the east and west ports on the same NE should be configured on different processing boards or interface boards corresponding to different processing boards. If the east and west ports on the same NE are configured on the same board,
ring network protection will fail when the NE is faulty.
Table 4-41 lists the interface groups for OptiX PTN 1900. When TN73CXP is used to configure ring network protection, if an interface in one group is used as an east port, the west port must be a port in the other group. If the interface board corresponding to TN73CXP is housed in slot 3, ring
network protection cannot be configured.
Before creating a ring network, choose Service > IP Protection Subnet > Search for Ring-bindable Tunnel to search for the tunnels that can be bound. After creating the ring network, re-search for the tunnels that can be bound and compare the two search results to determine the tunnels that
are bound to the ring network.
Table 4-41 Interface groups (PTN 1900)
Interface Group Port on TN73CXP Port on Interface Board (Used with TN73CXP)
1 Port 3 and 4 (GE) Ports on interface boards housed in slots 4 and 6
2 Ports 5 and 6 (GE) Ports on interface boards housed in slots 5 and 7
Procedure
1. Choose Service > IP Protection Subnet > Create MPLS Protection Ring from the main menu.
2. Configure basic information. For details on the parameters for MPLS-TP protection ring, see Descriptions of the parameters for creating MPLS-TP protection ring.
NOTE:
PTN equipment only supports ring protection of wrapping type. In wrapping mode, protection switching is triggered by a fault detection point and auto-loopback is performed on the fault node.
3. Configure the NE list. Set Ring Name, and other parameters.
a. Select an NE and set East Interface and West Interface.

Method 3: Click Add and choose NE. In the dialog box, select the desired NE and click OK.
NOTE:
If the position of an NE needs to be changed after it is added on the ring network, click Up or Down to move the NE on the MPLS protection ring.
4. Click Detail. Set the advanced parameters, OAM parameters, and APS parameters.
a. Optional: Click the Advanced Properties tab and set the bandwidth parameters.
NOTE:
The CIR of all the tunnels bound to a ring cannot exceed half of the CIR of the ring. The CIR of all the tunnels that are not bound to any ring on the port plus the CIR of all the rings on the port cannot be larger than the maximum CIR reserved for the port. The CIR of a
ring minus the CIR of all the tunnels bound to the ring is the remaining bandwidth of the ring.
The PIR of the tunnels bound to a ring must not exceed the PIR of the ring.
For the TND1CXP board on a PTN 950, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been reserved
for OAM packets.
For the TNC1CXPA/B/G/H/I board on a PTN 910, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has
been reserved for OAM packets.
For the TND3CXPA/B board on a PTN 960, when rings, tunnels (excluding tunnels in ring networks) and QinQ bandwidth are configured, ensure that the total bandwidth of all CIRs does not exceed the port bandwidth minus 128 kbit/s and the bandwidth has been
reserved for OAM packets.
Reserved bandwidth can be specified for a tunnel. To specify reserve bandwidth for a tunnel, select the desired NE in the NE Explorer, click Configuration > MPLS Management > MPLS-TP Shared Protection Ring Management, and choose the Reserved
Bandwidth tab. For related parameters, see Table 4-54.
b. Optional: Click the OAM tab and set the OAM parameters.
NOTE:
Enable the OAM function to detect the network continuity.
Set Frequency to 3.3 ms to ensure that protection switching time is within 50 ms.
The SD Threshold (%) is smaller than or equal to the SF Threshold (%).
c. Optional: Click the APS tab and set the APS parameters.
NOTE:
Enable the APS function so that protection switching can be triggered when a fault is detected using OAM packets.
5. Click OK.
Follow-up Procedure
An unrequired protection ring can be deleted during network adjustment.
NOTICE:
Before deleting a protection ring, delete the service-free tunnels and intersecting nodes on a protection ring.
1. Choose Service > IP Protection Subnet > Manage MPLS Protection Ring from the main menu.
30 of 43 13-May-19, 7:41 PM
3. Select one or more protection rings to be deleted, right-click, and choose Delete ServiceDelete.
4. The Warning dialog box is displayed, indicating that this operation may interrupt services. Click Yes.
5. The Rewarning dialog box is displayed. Click Yes.
4.8.4.2 Configuring Intersecting Nodes for MPLS-TP Ring Protection

When MPLS-TP ring protection is applied to intersecting rings, intersecting nodes need to be configured. If intersecting nodes are not configured, the services carried over the tunnels traversing a faulty inserting node cannot be protected.
Prerequisites

MPLS-TP protection rings have been created. For details, see 4.8.4.1 Creating an MPLS-TP Ring.
Procedure
3. Select a ring and click the Intersecting MPLS Ring tab in the lower-left corner.
4. Click Add Virtual Node. In the Add Virtual Node dialog box, select a protection ring that intersects with the selected ring.
NOTE:
If two intersecting rings have multiple intersecting nodes, the NMS automatically selects the two intersecting nodes that are farthest apart as the intersecting node for ring protection.
5. Click OK.
6. The Result dialog box is displayed, indicating that the operation succeeds. Click Close.
Follow-up Procedure
Unrequired intersecting nodes can be deleted during network adjustment.
3. Select a ring and click the Intersecting MPLS Ring tab in the lower-left corner.
4. Select an intersecting ring to be deleted, and click Delete Virtual Node.
5. The Prompt dialog box is displayed. Click Yes.
4.8.4.3 Configuring an MPLS-TP Ring Binding

This topic describes how to configure an MPLS-TP ring binding to add static tunnels that traverse the ring to the ring protection group for protection.
Prerequisites

A static tunnel has been created.
For a single ring, an MPLS ring network has been configured. For details, see 4.8.4.1 Creating an MPLS-TP Ring. For intersecting rings, an MPLS ring network and intersecting nodes have been configured. For details, see 4.8.4.2 Configuring
Intersecting Nodes for MPLS-TP Ring Protection.
NOTICE:
Before configuring MPLS-TP ring binding, ensure that the MPLS-TP ring protection group is functioning properly, avoiding service interruption after the binding. For details, see 4.8.5.1 Checking the Correctness of MPLS-TP Protection Ring.
NOTE:
An MPLS protection ring can be bound to a tunnel only when at least two intersecting points are available for the ring and tunnel.
Procedure
1. Choose Service > Tunnel > Manage Tunnel from the main menu.
NOTE:
Alternatively, you can choose Service > IP Protection Subnet > Search for Ring-bindable Tunnel to access the Manage Tunnel window.
3. Right-click one or more static tunnels and choose Bind MPLS Ring from the shortcut menu. The Binding MPLS protection ring dialog box is displayed.
NOTE:
Select the tunnel to be bound to the ring network, right-click, and choose Protection Group > Query Switching Status from the shortcut menu to check whether tunnel protection is configured and whether the status is normal. If the status is abnormal, troubleshoot it.
The ring network does not support 1+1 APS protection. If 1+1 APS protection is configured for the tunnel, right-click the tunnel, choose Protection Group > View Protection Group from the shortcut menu to access the Manage Protection Group window, and change the
protection mode to 1:1.
4. In the Binding MPLS protection ring dialog box, select a desired tunnel and click the Ring Binding tab. On the Ring Binding tab, select a protection ring to be bound.
NOTE:
You can select one or more tunnels and bound the tunnels to rings in batches,A maximum of 200 tunnels can be selected.
The default optimal ring is selected by observing the following rule: Service traffic must be switched to the ring from the first possible node and leaves the ring at the farthest node after traveling along an as-long-as-possible path.
The U2000 allows you to specify a required protection ring based on the following rule: A newly bound ring cannot overwrite or be overwritten by the ring that has been bound to the specific tunnel.
If ring binding fails, the tunnel automatically rolls back to the status before the binding.
5. Click OK.
31 of 43 13-May-19, 7:41 PM
Follow-up Procedure
Unrequired ring bindings can be deleted during network adjustment.
Method 1:
3. Select a ring and click the Binded Tunnel tab in the lower-left corner.
4. Select one or more tunnels to be unbinded. Click Unbind MPLS Protection Ring.
5. The Confirm dialog box is displayed, indicating that this operation may interrupt services. Click OK.
Method 2:
1. Choose Service > Tunnel > Manage Tunnel from the main menu.
3. Select a static tunnel and click the MPLS Protection Ring tab in the lower-left corner.
4. select a ring binded and click Unbind MPLS Protection Ring.
4.8.5 Managing and Maintaining MPLS-TP Ring Protection

4.8.5.1 Checking the Correctness of MPLS-TP Protection Ring
After configuring the MPLS-TP protection ring, you can check the connectivity by using the Test and Check function.
Prerequisites

MPLS-TP protection ring must be created.
Procedure
3. Optional: Select related MPLS-TP protection ring, and query and correct the attributes of the protection ring in the Topology, Bound Tunnel, Intersecting MPLS Ring, Protection Attribute, and Advanced Attribute tabs below. For the
relevant parameters, refer to Descriptions of the parameters for MPLS protection ring management.
4. Right-click an MPLS-TP protection ring and choose Test and Check from the shortcut menu.
5. In the dialog box that is displayed, select the trail to be checked.
6. Set Diagnosis Option.
Set diagnosis parameters as needed. The meaning of each option is as follows:

Ring Ping: detect the connectivity of an MPLS protection ring.
Ring Traceroute: locate the fault point on an MPLS protection ring.
NOTICE:
The ping and tracert operations cannot be initiated at the same time. If ping and tracert operations are initiated at the same time, the operation results may be incorrect.
7. Click Run.
8. View the check results.
4.8.5.2 Test on Ring Protection Switching

Ring protection applies to a single two-fiber bidirectional ring and two-fiber bidirectional intersecting rings. Ring protection protects services. This section describes how to test the ring protection function.
Prerequisites
The ring protection is created properly.

You must be an NM user with "Operator Group" authority or higher.
Tools, Meters, and Materials

U2000
Procedure
1. Check the switching status of the ring protection to be tested.
a. Choose Service > IP Protection Subnet > Manage MPLS Protection Ring from the main menu, and then the Manage MPLS Protection Ring and Set Filter Criteria windows are displayed.
b. Enter the filter criteria in the Set Filter Criteria window to filter the ring protection to be tested, and click Filter.
c. Right-click on the ring protection to be tested, and choose a window is displayed. Choose the Topo tab, and check West Status or East Status of the ring protection to be tested. Normally, the status is Idle State.
32 of 43 13-May-19, 7:41 PM
2. Perform a forced switching to the east or west ring protection and check its status after the switching.
a. Select the ring node to be tested, click East Maintance or West Maintance at the right bottom of the Topo tab, and select Manual Switching from the drop-down list. A warning dialog box is displayed prompting that services will
be interrupted by this action, and click OK to proceed the Manual switching.
b. Check West Status or East Status of the ring node to be tested. If the status is Manual switch, the Manual switching succeeds.
3. Click Clear All at the right bottom of the window, and then the ring protection is restored to normal status.
4.8.5.3 Creating a Ring VPLS Service on an MPLS-TP Protection Ring

After binding tunnels to a multiprotocol label switching transport profile (MPLS-TP) protection ring, you can create virtual private LAN services (VPLSs) on the ring so that the services can be protected by MPLS-TP ring protection switching. This
section describes how to create a VPLS service on an MPLS-TP protection ring.
Prerequisites
You are an NM user with Administrators rights or higher.

Tunnels have been created and bound to the MPLS-TP protection ring, for details you can refer to 4.8.4.3 Configuring an MPLS-TP Ring Binding.
NOTE:
If no tunnel is created before you create a VPLS service, choose Service > VPLS Service > Create VPLS Service > Details > PW Configuration > PW Configuration and click Create and Fill Tunnel to create tunnels. Note that you need to manually bind the created tunnels to the MPLS-
TP protection ring. If the tunnels are not bound to the ring, the created VPLS service cannot be protected by MRPS.
Procedure
1. Choose Service > VPLS Service > Create VPLS Service from the main menu.
2. In the Create VPLS Service dialog box, set Networking Mode to Ring and click Add. In the Select Ring dialog box, select the MPLS-TP protection ring for carrying the VPLS service.
3. Click Details, and set parameters on the VSI Configuration, PW Configuration, and SAI Configuration tab pages based on the plan.
NOTE:
Only In Block Point or Out Block Point of one PW on the PW Configuration sub-tab page that is on the PW Configuration tab page can be set to Enable, because only one block point can be configured for an MPLS-TP protection ring.
The values of In Block Point and Out Block Point of a PW are associated as follows: When In Block Point of a PW is set to Enable, Out Block Point of the PW is automatically set to Disable and cannot be changed; the opposite is also true.
After you set block points on a PW, the services carried on the PW and configure OAM are interrupted. Therefore, when you enable PW OAM for the PW, OAM alarms are reported. These alarms do not actually indicate that the services are affected as the PW normally does not
carry services. It is recommended that you disable PW OAM before setting block points on a PW.
Only one PW can be configured between intersecting nodes of intersecting rings.
4. Click OK.
7. The Result dialog box is displayed, indicating that the operation is successful. Click Close.

This section describes the parameters related to the MPLS-TP ring protection configuration.
Descriptions of the parameters for creating MPLS-TP protection ring

Table 4-42 Description of basic parameters for creating an MPLS protection ring
Ring Name Definition: Setting method:

Specifies the name of an MPLS protection ring. This parameter is set by default. You can also enter a name as required.
Ring Type Definition: Value:

Indicates the switching mode of an MPLS protection ring. In wrapping mode, an NE that detects At present, the U2000 only supports MPLS protection rings for which the ring type is wrapping.
a failure initiates a switching, and services are switched to the reverse protection path. On Therefore, Ring Type is dimmed and cannot be set.
another NE, services are switched back to the original working path and transmitted to the
destination NE.
Remark Definition: Rule:

Adds remarks to a specific MPLS protection ring to facilitate MPLS protection ring Enter any description that can help you locate the MPLS protection ring easily.
maintenance.
Table 4-43 NE list
Node Name Definition: -

Indicates the name of an NE on an MPLS protection ring.
East Interface Definition: Setting method:

Specifies an NE interface adjacent to the eastbound NE on an MPLS protection ring. The U2000 automatically assigns an eastbound/westbound interface to an NE according to the
Layer 2 link between NEs. You can also configure an eastbound/westbound interface by clicking
the ... button.
West Interface Definition: NOTE:
Specifies an NE interface adjacent to the westbound NE on an MPLS protection ring. An NE interface that an MPLS protection ring is using can be used by a service, such as the tunnel service,
as long as the available bandwidth of the NE interface is sufficient.
LSR ID Definition: -
Indicates the LSR ID of an NE. The ID must be unique on the network.
Table 4-44 Advanced Properties
CIR Definition: Rule:
33 of 43 13-May-19, 7:41 PM
Indicates the committed information rate for a service that traverses the tunnel. The packets The committed bandwidth must be smaller than or equal to the remaining uplink bandwidth on a
within this bandwidth range can be completely forwarded. If the rate of the packets entering the link.
queue is smaller than or equal to the CIR, all the packets are forwarded. If the rate of the packets Example:
entering the queue is bigger than the CIR, the scheduling algorithm discards packets according to 100 Mbit/s
a certain packet loss policy.
CBS Definition: Rule:

Indicates the committed burst size. Packets that require less bandwidth than CIR+CBS can pass through the MPLS protection ring at
any time.
Example:
4K byte
PIR Definition: Rule:

Specifies the maximum rate of a service. The value must be no less than the CIR.
PBS Definition: Rule:

Indicates the peak burst size available for a service. Packets that require less bandwidth than CIR+PBS can pass through the MPLS protection ring
only at specified time.
Example:
4M byte
MTU Definition: Rule:

Indicates the maximum transmitted packet length, which is the length of the packet payload. The MTU cannot be less than the maximum length of the user packet payload. Otherwise,
packets with the payload greater than the MTU will be discarded.
Path EXP Definition: Rule:

Specifies the EXP of an MPLS protection ring. The EXP field is used as a CoS to carry DiffServ Indicates the level of EXP. 7 indicates the highest level.
information, functioning similar to Ethernet 802.1p.
Table 4-45 OAM
OAM Mode Definition: -

Specifies an OAM detection mode. The available options are Y.1711 and Y.1731. The default
value is Y.1711.
NOTE:
Only one OAM mode takes effect, even if the NE supports both OAM modes. To modify the OAM mode,
choose Configuration > NE Batch Configuration > MPLS OAM Configuration from the main menu.
Enable Status Definition: Value:

Specifies whether to enable OAM. OAM is enabled by default.
NOTE:
This parameter is associated with Enable Status on the APS tab page. When this parameter is set to
Enabled, Enable Status on the APS tab page is set to Enabled automatically.
Frequency Definition: Example:

Specifies the frequency of sending OAM detection packets. 10 ms
EXP Definition: Rule:

Specifies the EXP value for OAM. The EXP field is used as a CoS to carry DiffServ information, Indicates the level of EXP. 7 indicates the highest level.
functioning similar to Ethernet 802.1p.
Relation to other parameters:
When OAM Mode is set to Y.1711, the value of EXP can't be set.
SD Definition: Rule:
Specifies an SD threshold. An SD alarm is reported if the packet loss ratio of OAM packets on The SF threshold must be equal to or greater than the SD threshold.
the detection path exceeds the SD threshold.
SF Definition:
Specifies an SF threshold. An SF alarm is reported if the packet loss ratio of OAM packets on the
detection path exceeds the SF threshold.
Table 4-46 APS
Enable Status Definition: Value:

Specifies whether to enable APS. APS is enabled by default.
NOTE:
This parameter is associated with Enable Status on the OAM tab page. When this parameter is set to
Enabled, Enable Status on the OAM tab page is set to Enabled automatically.
WTR Time Definition: Value:

Specifies a period after which services are switched back to the working path that has recovered. The default value is 5.
Hold-off Time Definition: Value:

When a fault of the working PW is detected, protection switching does not occur immediately. The default value is 0.
Instead, protection switching occurs only on the condition that the fault persists when the hold-
off time expires.
When equipment is configured with PW APS and other protection, you can set the hold-off time
to ensure that other protection switching is performed first.
Hold-off time helps avoid protection switching caused by the fault that lasts transiently.
Descriptions of the parameters for MPLS protection ring management

Table 4-47 Description of parameters for top information
Parameter Description
Node Name Definition:

Eastbound Interface Definition:

Indicates an NE interface connected to the next NE in the eastbound direction.
Eastbound Result Definition:

Indicates the switching results of an NE in the eastbound direction.
Eastbound Status Definition:

Indicates the switching status of an NE in the eastbound direction. The parameter value is updated only when the switching status changes, for example, from Unswitched to Switched or
from Switched to Unswitched. To update the switching status, right-click the required ring in the upper table and choose Refresh Switch Status from the shortcut menu.
Idle State: status of every NE when the entire ring is functioning properly.
Pass Through: status displayed when one NE on an MPLS protection ring is in switching state but the other NEs are functioning properly.
WTR: status displayed when the working path recovers and services wait for the switchback to the working path from the protection path.
Westbound Interface Definition:

Indicates an NE interface connected to the next NE in the westbound direction.
Westbound Result Definition:

Indicates the switching results of an NE in the westbound direction.
Westbound Status Definition:

Indicates the switching status of an NE in the westbound direction. The parameter value is updated only when the switching status changes, for example, from Unswitched to Switched or
from Switched to Unswitched. To update the switching status, right-click the required ring in the upper table and choose Refresh Switch Status from the shortcut menu.
Idle State: switching status of every NE when the entire ring is functioning properly.
Pass Through: status displayed when one NE on an MPLS protection ring is in switching state but the other NEs are functioning properly.
WTR: status displayed when the working path recovers and services wait for the switchback to the working path from the protection path.
Table 4-48 Button Description
Button Description
Lock All Locks all NEs on an MPLS protection ring to the working path.
Clear All Clears the switching on the entire MPLS protection ring to restore the MPLS protection ring to the initial state.
East Maintance Clear Switching To restore an MPLS protection ring to the initial state, perform any of the following operations before clearing switching.
West Maintance
Lock Switching If lockout of switching is configured, an interface is not switched when it should be switched but is recovered when it should be recovered. Services are locked to the working path no matter
whether the working or protection path is functioning properly.
34 of 43 13-May-19, 7:41 PM
Button Description
Force Switching Force switching is to forcibly switch services from the working path to the protection path, regardless of the MPLS protection ring status.
Manual Switching Manual switching is to switch services from the working path to the protection path. If the protection path is functioning properly, the switching can be performed. If the protection path is
faulty or is serving a high-priority switching, the switching cannot be performed.
Exercise Switching Exercise switching is to simulate a switching to test the protection function of a protection group. Services are not interrupted.
Table 4-49 Description of parameters for tunnel binded information
Tunnel Name Definition:

Indicates the name of a tunnel.
Direction Definition:
Indicates the direction of a tunnel. The available options are Unidirectional and Bidirectional.
Running Status Definition:

Indicates tunnel running status that is reported to the U2000.
Alarm Status Definition:

Indicates the alarm status of a tunnel. This parameter is bound to the alarms of tunnel objects and ports.
Source Node Definition:

Indicates the source NE of a tunnel.
Sink Node Definition:

Indicates the sink NE of a tunnel.
Tunnel ID Definition:
Indicates the ID of a tunnel. Tunnels are queried based on their IDs. A tunnel ID must be unique on the network.
Destination IP Address Definition:

Indicates the destination IP address for service transmission.
Table 4-50 Description of parameters for virtual node information
Intersecting Ring Network Definition:

Name Indicates the name of an MPLS protection ring that intersects with an existing MPLS protection ring.
Intersecting Ring Network ID Definition:

Indicates the ID of an MPLS protection ring that intersects with an existing MPLS protection ring.
Intersecting Node 1 Definition:

Indicates the name of the first node at which two MPLS protection rings intersect.
Intersecting Node 2 Definition:

Indicates the name of the second node at which two MPLS protection rings intersect.
Table 4-51 Protection Parameters
OAM Mode Definition: -

Specifies an OAM detection mode. The available options are Y.1711 and Y.1731. The
supported OAM detection mode is automatically reported to the U2000 and cannot be
changed.
Hold-off Time Definition: Value:

When a fault of the working PW is detected, protection switching does not occur The default value is 0.
immediately. Instead, protection switching occurs only on the condition that the fault persists
when the hold-off time expires.
When equipment is configured with PW APS and other protection, you can set the hold-off
time to ensure that other protection switching is performed first.
Hold-off time helps avoid protection switching caused by the fault that lasts transiently.
WTR Time Definition: Value:

Specifies a period after which services are switched back to the working path that has The default value is 5.
recovered.
Table 4-52 Protection Properties
Node Definition: -
East OAM Enable Status Definition: Setting method:

Specifies whether to enable OAM in the east direction. The U2000 uses OAM to detect path One or multiple NEs are supported. Select one or more NE records, right-click in the East
faults on a ring. OAM Enable Status column, and choose Enabled or Disabled from the shortcut menu.
West OAM Enable Status Definition: NOTE:

Specifies whether to enable OAM in the west direction. The U2000 uses OAM to detect path East OAM Enable Status or West Enable Status for an NE is associated with West OAM
faults on a ring. Enable Status or East Enable Status for the next-hop NE on the same ring. This feature is
similar to that for APS Enable Status.
East APS Enable Status Definition: East OAM Enable Status or West OAM Enable Status of an NE is associated with East
Specifies whether to enable APS in the east direction. The U2000 uses APS to perform APS Enable Status or West APS Enable Status of the same NE. If APS Enable Status is
automatic switching. set to Enabled, the value of OAM Enable Status is also Enabled. If OAM Enable Status
is set to Disabled, the value of APS Enable Status is also Disabled.
West APS Enable Status Definition:
Specifies whether to enable APS in the west direction. The U2000 uses APS to perform
automatic switching.
Frequency Definition: Setting method:

Specifies the frequency of sending and receiving OAM detection packets. One or multiple NEs are supported. Select one or more NE records, right-click in the
Frequency column, and choose an option from the shortcut menu.

Specifies an EXP value. The EXP field is used as a CoS to carry DiffServ information, One or multiple NEs are supported. Select one or more NE records, right-click in the EXP
functioning similar to Ethernet 802.1p. column, and choose an option from the shortcut menu.
Relation to other parameters: Rule:
When OAM Mode is set to Y.1711, the value of EXP can be set to - only. Indicates the level of EXP. 7 indicates the highest level.
SD Definition: Setting method:

Specifies an SD threshold. One or multiple NEs are supported. Select one or more NE records, right-click in the SD
column, and choose an option from the shortcut menu.
SF Definition: Rule:
Specifies an SF threshold. The SF threshold must be equal to or greater than the SD threshold.
Table 4-53 Advanced Properties
CIR Definition: Rule:

Indicates the committed information rate for a service that traverses the tunnel. The packets The committed bandwidth must be smaller than or equal to the remaining uplink bandwidth on a
within this bandwidth range can be completely forwarded. If the rate of the packets entering the link.
queue is smaller than or equal to the CIR, all the packets are forwarded. If the rate of the packets Example:
entering the queue is bigger than the CIR, the scheduling algorithm discards packets according to 100 Mbit/s
a certain packet loss policy.
CBS Definition: Rule:

Indicates the committed burst size. Packets that require less bandwidth than CIR+CBS can pass through the MPLS protection ring at
any time.
Example:
4K byte
PIR Definition: Rule:

Specifies the maximum rate of a service. The value must be no less than the CIR.
PBS Definition: Rule:

Indicates the peak burst size available for a service. Packets that require less bandwidth than CIR+PBS can pass through the MPLS protection ring
only at specified time.
Example:
4M byte
35 of 43 13-May-19, 7:41 PM
MTU Definition: Rule:

Indicates the maximum transmitted packet length, which is the length of the packet payload. The MTU cannot be less than the maximum length of the user packet payload. Otherwise,
packets with the payload greater than the MTU will be discarded.
Path EXP Definition: Rule:

Specifies the EXP of an MPLS protection ring. The EXP field is used as a CoS to carry DiffServ Indicates the level of EXP. 7 indicates the highest level.
information, functioning similar to Ethernet 802.1p.
Table 4-54 Descriptions of the parameters for reserved bandwidth
Tunnel ID Example: 10 Indicates the ID of a tunnel.
Source Node ID Example: 35.10.81.1 Indicates the source node ID of a tunnel.
Sink Node ID Example: 35.10.83.1 Indicates the sink node ID of a tunnel.
Reserved Bandwidth on Eastern Interface(kbit/s) Example: 125 Specifies the reserved bandwidth on the east port.
NOTE:
Do not set reserved bandwidth on both the east port and the west port to 0.
Reserve bandwidth on the east and west ports for a bidirectional tunnel and reserve bandwidth only on the
outgoing port for a unidirectional tunnel.
Reserved Bandwidth on Western Interface(kbit/s) Example: 214 Specifies the reserved bandwidth on the west port.
PIR(kbit/s) Example: 248 Specifies the peak information rate (PIR) of a tunnel. The PIR of each tunnel cannot be higher
than the PIR of the ring.

The PTN equipment supports 1:1 PW APS protection. This chapter describes PW APS in terms of concept, application, and configuration.
4.9.1 PW APS Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-55 PW APS specification
Configuring PW APS - √ √ √
4.9.2 PW APS Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-56 PW APS specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring PW APS - √ √ √ √
Table 4-57 PW APS specifications (on the PTN 905A, PTN 905B,PTN 906A and PTN 906B)
Configuring PW APS - √ √ √ √
4.9.3 PW APS Configuration Flow

This section describes the flow of configuring PW APS, with focuses on the configuration tasks included in the configuration of PW APS and the details on each configuration task.
Figure 4-14 shows the flowchart for configuring PW APS. For details on each step, see the related sections.
Figure 4-14 Flowchart for configuring PW APS
Table 4-58 PW APS configuration tasks
Task Remarks
1. Create a working PW, a protection PW, and a PW APS protection group. Mandatory
1. When creating a service, create a working PW and a protection PW for the service. Set the parameters such as PW signal type, egress/incoming label, and bearer tunnel.
2. Create a protection group and set parameters such as protection group ID, WTR time (min), and hold-off time (ms).
NOTE:
For an MS PW, create an MS PW cross-connection. Set the parameters such as MS PW ID, forward PW, and backward PW. For configuration details see 7.13.4 Configuring an MS-PW.
2. Start the PW APS protocol. Mandatory

Start the PW APS protocol at the source and sink sites to validate the protection group.
3. Attach protection pairs to the protection group. Optional
When configuring protection for PWs with the same source and sink, attach the PW pairs to a PW APS protection group to save the OAM resources.
Specify the ID of the PW APS protection group to which the protection pairs are attached.
4.9.4 Creating a PW APS Protection Group

The PTN equipment provides PW APS protection for single-segment pseudo wires (SS-PWs) and multi-segment pseudo wires (MS-PWs). A PW APS protection group can be configured to protect PWs.
Prerequisites

The bearer tunnels for the working PW and protection PW must be created.
Configuration Guide
PW APS protection can be created for the CES service, ATM service, E-Line service, IP over PW service, or E-LAN service that is transported over PWs. You can also configure a PW APS protection group for a service either before or after creation of
the service.
When configuring a service, set Protection to PW APS, and create a working PW, a protection PW, and a PW APS protection group.
To create a PW APS protection group to an existing service, click the Protect Group tab.
To configure PW APS protection for SS-PWs or MS-PWs, create a PW APS protection group at the source and sink NEs.
NOTE:
This section considers the configuration of PW APS for an E-Line service as an example to show how to create a PW APS protection group.
PTN 3900/3900-8/1900/910/910-F/950/960/905A: For creation process of a CES service, see 7.4.5.4 Creating a UNI-NNI CES Service on a Per-NE Basis.
PTN 3900/3900-8/1900/910/910-F/950/960: For creation process of an ATM service, see 7.5.5.5 Creating ATM Services on a Per-NE Basis.
For creation process of an E-Line service, see 7.6.5.4 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE Basis.
For creation process of an E-LAN service, see 7.7.5 Configuring a UNI-NNI E-LAN Service.
NOTE:
36 of 43 13-May-19, 7:41 PM
Procedure
Create a PW APS protection group for a new service.
1. In the NE Explorer, select an NE and choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
2. Click the UNI tab and click New. Then, the New E-Line Service dialog box is displayed.
3. Set the parameters related to the E-Line service according to the networking planning. Set Direction to UNI-NNI, Protection Type to PW APS.
4. Click Configure PW, the Configure PW dialog box is displayed.
5. Set the parameters related to working PW and protection PW in the Basic Attributes tab.
6. Set the parameters related to the PW APS protection group in the Protect Group tab.
NOTE:
Enabling Status: When creating a PW APS protection group, set this parameter to Disabled. After creating APS protection groups on the nodes at both ends, start the APS protocol. For details, see 4.9.5 Starting the PW APS protocol.
Switchover WTR Time (min): indicates the time from recovery of the working PW to service switchover from the protection PW to the working PW. The WTR time setting helps avoid frequency switching caused by unstable quality of the working PW.
Switchover Hold-off Time (100 ms): When the SF state of the working PW is detected, protection switching does not occur immediately. Instead, protection switching occurs only on the condition that the SF state persists when the hold-off time expires. The hold-off time setting
helps avoid protection switching caused by the SF state that lasts transiently.
Enable PW OAM: When creating a PW APS protection group, also enable PW OAM to detect the status of a PW.
When Switching upon FD/FDV is enabled, the protection group supports switching upon FD/FDV. Before you enable and configure switching upon FD/FDV, be sure to configure PW performance monitoring. For configuration details, see Enabling the Performance Monitoring
and Management Function.
7. Click OK .
8. Refer to the preceding steps to configure the protection group on the sink NE.
9. Set Detection Packet Type to FFD and Detection Packet Period (ms) to 3.3 ms for PW OAM of the working PW and protection PW. For details, see 5.1.5.3.1 Starting the CV/FFD Check for a PW.
NOTE:
Detection Packet Period (ms) must be set to 3.3 ms for PW OAM so that the protection switching time is within 50 ms. Extensive delay variation on a network, however, results in repeated protection switching. Hence, the detection packet period must be larger than the maximum
network delay variation.
Create a PW APS protection group for an existing service.
2. Click Query, the created E-Line service is displayed on the interface.
3. Select the E-Line service flow which the protection group is to be configured, click the Protect Group tab, and click PW APS.
4. Click New, the Configure PW dialog box is displayed.
5. Set the parameters related to protection PW in the Basic Attributes tab.
6. Optional: Set the parameters related to QoS according to the networking planning in the QoS tab.
NOTE:
Bandwidth Limit: When you set this parameter to Enabled, you can set CIR(kbit/s) and PIR(kbit/s).
Policy: Select a policy from the created PW policy template.
7. Set the parameters related to the PW APS protection group in the Protection tab.
8. Click OK.
9. Refer to the preceding steps to configure the protection group on the sink NE.
10. Set Detection Packet Type to FFD and Detection Packet Period (ms) to 3.3 ms for PW OAM of the working PW and protection PW. For details, see 5.1.5.3.1 Starting the CV/FFD Check for a PW.
NOTE:
Detection Packet Period (ms) must be set to 3.3 ms for PW OAM so that the protection switching time is within 50 ms. Extensive delay variation on a network, however, results in repeated protection switching. Hence, the detection packet period must be larger than the maximum
network delay variation.
Result
Check whether the working PW and protection PW are normal.
2. Click Query in the Protect Group > PW APS tab, to check the status of the working PW and protection PW.
37 of 43 13-May-19, 7:41 PM
3. Click the Working PW ID or Protection PW ID parameter field, the PW Management interface is displayed.
4. Click Query, and close the Operation Result window.
5. Check Local Operating Status, Remote Operating Status, and Overall Operating Status of the working and protection PWs.
If the status is displayed as Up, the PW is normal.
If the status is displayed as Down, the PW is faulty. For details on how to rectify a PW fault, see the Troubleshooting.
Check whether the protection group is normal. For details, see 4.9.7 Testing PW APS.
4.9.5 Starting the PW APS protocol

When creating a PW APS protection group is complete, you need to enable the APS protocol to validate the protection group.
Prerequisites

Creating a PW APS Protection Group must be complete.
Procedure
1. In the NE Explorer, select an NE and choose Configuration > APS Protection Management from the Function Tree.
2. Click the PW APS Management tab, right-click the created APS protection group, and choose Start Protocol.
3. A dialog box is displayed, indicating that the operation is successful. In this case, Protection Group Status is displayed as Enabled.
4. Display the NE Explorer of the opposite NE and repeat the preceding steps to enable the PW APS protocol.
4.9.6 Binding PW APS Pairs

When the working PWs and protection PWs of multiple PW APS protection pairs share the same source and sink with the working PW and protection PW of a PW APS protection group, you can bind the protection pairs to the protection group to
achieve synchronous detection and switching, and to save OAM resources on equipment.
Prerequisites

Creating a PW APS protection group must be complete.
Context
In the case of CES service, ATM service, E-Line services or E-LAN services carried over PWs, you can create PW APS protection pairs for them and bind the protection pairs to a PW APS protection group. You can bind the protection pairs during or
after creation of the services.
To bind a protection pair during service creation, set Protection Type to Slave Protection Pair, create the working PW and protection PW, and bind the protection pair to a PW APS protection group.
To bind a protection pair after service creation, choose Protection Group > Slave Protection Pair and add the protection pair to a PW APS protection group.
For PW APS binding of SS-PW or MS-PW, bind the protection pair at both the source NE and sink NE.
This section describes how to bind a protection pair for an E-Line service. Binding a protection group for other services is similar.
Procedure
Create a PW APS pair when configuring a service.
2. Click the New. Then, the New E-Line Service dialog box is displayed.
3. Set the parameters related to the E-Line service according to the networking planning. Set the Direction to UNI-NNI and Protection Type to Slave Protection Pair.
4. Click Configure PW to display the Configure PW dialog box.
5. Set the parameters related to working PW and protection PW on the General Attributes tab
6. On the Protect Group tab, select the protection group to which the protection pair is to be bound.
7. Click OK.
Create a PW APS pair after configuring a service.
2. Click Query to display the created E-Line service.
3. Select the E-Line service for which a PW APS pair is to be created. Then, click Slave Protection Pair on the Protection Group tab.
4. Click New to display the Configure PW dialog box.
5. Set the parameters related to protection PW according to the networking planning on the General Attributes tab.
6. Optional: Set the parameters related to QoS according to the networking planning on the QoS tab.
NOTE:
Policy: Select a policy from a created PW policy template.
38 of 43 13-May-19, 7:41 PM
7. On the Protection Group tab, select the protection group to which the protection pair is to be bound.
8. Click OK.
9. Display the NE Explorer of the opposite NE and repeat the preceding steps to create a protection pair on the opposite NE.
Result
2. Click Query on the Protection Group > Slave Protection Pair tab to check the status of the working PW and protection PW.
4.9.7 Testing PW APS

When creating a PW APS protection group is complete, test the protection group to ensure that the protection functions normally in case of a fault. This section describes how to test PW APS.
Prerequisites

A PW APS protection group must be created and the PW APS protocol must be enabled.
The working and protection PWs work normally.
Context
You can check the PW connectivity through the PW OAM. For details, see 5.1.5.3 Configuring the MPLS PW OAM.
Procedure
1. In the NE Explorer, select an NE and choose Configuration > APS Protection Group from the Function Tree.
2. Click the PW APS Management tab, select the PW to be Queried, and right-click Query Switching Status. Normally, Working Path Availability and Protection Path Availability are displayed as Valid, Switchover Status as working and
Protocol Status as No Request(Working Active).
NOTE:
When both the working PW and protection PW are normal, the status is displayed as Valid. In case of a PW exception, the status is displayed as Invalid. In this case, rectify the PW fault. Double-click PW ID to display the PW Management interface. In the interface, check the status of the
PW and rectify the fault according to the PW status information.
3. Select a created protection group and choose Function > Manual Switching to Protection to switch the service to the protection PW.
4. Select the PW to be Queried, and right-click Query Switching Status,Switchover Status is displayed as Protecting and Protocol Status is displayed as Forced Switching(Protecting Active). This indicates that the service is switched to the
protection PW.
5. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
6. Choose the service protected by the protection group, right-click it, and choose Browse Current Alarms from the shortcut menu. Then, check whether alarms are generated after the switching.
NOTE:
If alarms are generated, see Alarm Handling to handle the alarms.
If no alarm is generated, proceed to the next step.
7. Perform the service connectivity check through the Ethernet service OAM and check whether the services after switching are normal.
NOTE:
If the services are normal, the PW APS protection group is normal.
If the services are abnormal, the protection switching fails. For how to handle this fault, see Troubleshooting.
Follow-up Procedure
In the NE Explorer, select an NE and choose Configuration > APS Protection Group from the Function Tree.
Right-click the protection group under test and choose Clear from the shortcut menu to revert the services to the original working PW.

This section describes the parameters related to the PW APS configuration.
Table 4-59 Descriptions of the parameters for PW APS Management
Protection Group ID OptiX PTN 3900(TN81SCA):1-1024 Specifies the ID of a protection group.

OptiX PTN 3900(TN82SCA):1-4096
NOTE:
OptiX PTN 3900-8:1-2048 If a protection pair is bound to a PW APS protection group, the ID of the protection pair is the ID
OptiX PTN 1900: 1-512 of the PW APS protection group.
PTN 910/910-F/950: 1-256
PTN 910-F: 1-256
PTN 960: 1-500
Peer Protection Group ID For example: 12 Specifies the ID of a peer protection group.
NOTE:
For the inter-NE protection, you need to specify the ID of the protection group of the peer NE. In
this way, the protection groups on both ends can negotiate and together implement the inter-NE PW
protection.
Protection Type No Protection, PW APS, MC PW APS, PW FPS, Slave Protection Pair Indicates the protection type of a protection group.
Protection PW ID For example: 321 Indicates the ID of the protection group.
Working PW ID For example: 123 Indicates the ID of the working PW.
DNI PW ID For example: 4321 Indicates the ID of a DNI PW.
Protection Mode 1:1 When the protection type is 1:1 protection, the service is in the single-fed and single-
receiving mode.
Switchover Mode Dual-ended switching Indicates the switching status of a protection group.
NOTE:
OptiX PTN equipment support only the dual-ended switching.
Revertive Mode Non-Revertive, Revertive Determines whether the services are restored to the original working PW after the fault is
removed.
Revertive: In this mode, services are switched from the protection PW back to the
working PW after the working PW recovers. Generally, the revertive mode is
recommended, because the working PW has better performance than the protection PW.
Non-Revertive: In this mode, services keep traveling along the protection PW after the
working PW recovers. Because services will be temporarily interrupted during revertive
switching, using the non-revertive mode for services that require high reliability is
recommended.
Switchover WTR Time (min) 0 to 12 Specifies a delay in switching services back to the working PW after the working PW
recovers.
The switchover WTR time helps prevent services from frequently switching between the
working and protection PWs when the working PW is unstable.
Swtichover Hold-Off Time (100 ms) 0 to 100 Specifies a delay in switching services to the protection PW after the working PW fails.
If PW protection couples with another protection mechanism, an appropriately configured
switchover hold-off time can prevent switching conflicts between the two protection
mechanisms when a fault occurs.
Enabling Status Enabled, Disabled Indicates whether a protection group is enabled.
Switchover Status In Working, In Protection Indicates the switching status of a protection group.
39 of 43 13-May-19, 7:41 PM
Protocol Status No Request (Working Active), No Request (Protection Active), Lockout (Working Indicates the protocol status.
Active), Forced Switching(Protection Active), Working Signal Failure (Protection Active),
Protection Signal Failure (Working Active), Protection Signal Degrade (Working Active),
Working Signal Degrade (Protection Active), Manual Switch to Working path, Manual
Switch to Protection path, Wait-to-Restore (Protection Active), Do Not Revert (Protection
Active), Exercise Switching (Working Active), Exercise Switching (Protection Active),
Reverse Request (Working Active), Reverse Request (Protection Active)
Working Path Availability Available, Unavailable Indicates the status of the working channel in a protection group.
Protection Path Availability Available, Unavailable Indicates the status of the protection channel in a protection group.
PW Type For example: CESoPSN Display the PW encapsulation type.
Deployment Status Deployed, Undeployed Display the deployment status of the protection group.

The PTN equipment supports 1:1 PW FPS and 1+1 PW FPS protection. This chapter describes PW FPS 1:1 and PW FPS 1+1 configuration.
4.10.1 PW FPS Functions Supported by Chassis-shaped PTN Devices
Specifications
Table 4-60 PW FPS specification
Configuring a PW FPS 1:1 - √ √ √
Configuring a PW FPS 1+1 - × × ×
4.10.2 PW FPS Functions Supported by Case-shaped PTN Devices
Specifications
Table 4-61 PW FPS specifications (on the PTN 910, PTN 910-F, PTN 950, and PTN 960)
Configuring a PW FPS 1:1 - √ √ √ √
Configuring a PW FPS 1+1 - × × × √
Table 4-62 PW FPS specifications (on the PTN 905A, PTN 905B, PTN 906A and PTN 906B)
Configuring a PW FPS 1:1 - √ √ √ √
Configuring a PW FPS 1+1 - × × × ×
4.10.3 Configuring a PW FPS 1:1

In a dual-homing scenario where dual-homing nodes does not support APS but support PW OAM, PW FPS 1:1 can be configured on access nodes (PTN equipment), which then work with dual-homing nodes to protect services. If the working PW or
master dual-homing node is faulty or the link between the master dual-homing node and RNC is broken, FPS functions to switch services from the working PW to the protection PW. In this manner, services are protected.
Prerequisites

If a QoS policy is required, configure the V-UNI ingress policy based on the data plan. For details, see 6.5.6 Creating the V-UNI Ingress Policy.
Context
PW FPS 1:1 is applicable only to E-Line services.

You can also configure a PW FPS 1:1 protection group for an E-Line service either before or after creation of the E-Line service.
Configure PW FPS 1:1 when you configure services. For details, see the procedure.
Configure PW FPS 1:1 for unprotected Ethernet services.
2. Click the Protect Group tab and then select PW FPS tab.
3. Click New. The Configure PW dialog box is displayed. Set parameters for the protection PW and PW FPS based on 5 to 8.
Procedure
2. Click New. Then, the New E-Line Service dialog box is displayed.
3. Set the parameters related to the E-Line service according to the networking planning. Set Direction to UNI-NNI, Protection Type to PW FPS.
4. Click Configure PW. The Configure PW dialog box is displayed.
6. Optional: Set the parameters related to QoS according to the networking planning in the QoS tab.
NOTE:
7. Set the parameters related to the PW FPS protection group in the Protect Group tab.
40 of 43 13-May-19, 7:41 PM
NOTE:
PW FPS is configured only on the access side of PTN equipment. When creating a PW FPS protection group, set Enabling Status to Enabled.
Switchover Hold-off Time (100 ms): When the SF state of the working PW is detected, protection switching does not occur immediately. Instead, protection switching occurs only on the condition that the SF state persists when the hold-off time expires. The hold-off time setting helps avoid
protection switching caused by the SF state that lasts transiently.
8. Set the parameters related to the PW OAM in the PW OAM tab.
NOTE:
Detection Packet Type of working PW must be set to FFD, and Detection Packet Period (ms) of working PW must be set to 3.3 ms for PW OAM so that the protection switching time is within 50 ms. Extensive delay variation on a network, however, results in repeated protection
switching. Hence, the detection packet period must be larger than the maximum network delay variation.
9. Click OK. Then the New E-Line Service dialog box is displayed.
10. Optional: Configure a QoS policy.
a. Click Configure QoS. The Configure QoS dialog box is displayed. Click the blank area below Policy. Then a dialog box for selecting a V-UNI ingress policy is displayed.
b. Click OK to close the active dialog box and display the New E-Line Service dialog box.
11. Click OK to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close.
Result
2. Click Query in the Protection Group > PW FPS tab, to check the status of the working PW and protection PW.
Check whether the protection group is normal. For details, see 4.9.7 Testing PW APS.
4.10.4 Configuring a PW FPS 1+1

In a dual-homing scenario where dual-homing nodes does not support APS but support PW OAM, PW FPS 1+1 can be configured on access nodes (PTN equipment), which then work with dual-homing nodes to protect services. If the working PW or
master dual-homing node is faulty or the link between the master dual-homing node and RNC is broken, FPS functions to switch services from the working PW to the protection PW. In this manner, services are protected.
Prerequisites

Context
PW FPS 1+1 is applicable only to CES services.
You can also configure a PW FPS 1+1 protection group for a CES service either before or after creation of the CES service.
Configure PW FPS 1+1 when you configure services. For details, see the procedure.
Configure PW FPS 1+1 for unprotected CES services.
1. In the NE Explorer, select an NE and choose Configuration > CES Service Management.
2. Click the Protect Group tab and then select PW FPS tab.
3. Click New. The Configure PW dialog box is displayed. Set parameters for the protection PW and PW FPS based on 5 to 9.
Procedure
2. Click New. Then, the Create CES Service dialog box is displayed.
3. Set the parameters related to the CES service according to the networking planning. Set Mode to UNI-NNI, Protection Type to PW FPS. For details on the parameters for UNI-NNI service of CES, see Table 7-13.
41 of 43 13-May-19, 7:41 PM
4. Click Configure PW. The Configure PW dialog box is displayed.

6. Optional: Click QoS tab and set the related parameters. For details on the parameters for QoS, see Table 7-14.
NOTE:
EXP: Set the Ingress value only. 7 indicates the highest priority.
7. Click Advanced Attributes tab, and configure the related parameters. For details on the parameters for advanced attributes, see Table 7-15.
8. Click Protect Group tab and set the parameters related to the PW FPS protection group.
NOTE:
PW FPS is configured only on the access side of PTN equipment. When creating a PW FPS protection group, set Enabling Status to Enabled.
Switchover Hold-off Time (100 ms): When the SF state of the working PW is detected, protection switching does not occur immediately. Instead, protection switching occurs only on the condition that the SF state persists when the hold-off time expires. The hold-off time setting helps avoid
protection switching caused by the SF state that lasts transiently.
9. Click PW OAM tab and set the parameters related to the PW OAM.
42 of 43 13-May-19, 7:41 PM
10. Click OK. Then the Create CES Service dialog box is displayed.
11. Click OK to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close.
Result
2. Click Query in the Protection Group > PW FPS tab, to check the status of the working PW and protection PW.
4. Click Query in the PW Management page, the Operation Result dialog box is displayed. Then, click Close.
43 of 43 13-May-19, 7:41 PM

Configuring Tunnels and Tunnel Protection

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Tunnels and Tunnel Protection

Uploaded by

Copyright:

Available Formats

Configuring Tunnels and Tunnel Protection http://support.huawei.com/enterprise/docinforeader!loadDocument1.ac...

4 Configuring Tunnels and Tunnel Protection

4.1 Configuring an MPLS Tunnel

4.2 Configuring an IP Tunnel

4.3 Configuring a GRE Tunnel

4.4 Unified E2E Tunnel Management and Maintenance

4.5 Configuring a QinQ Link

4.6 Configuring the MPLS Tunnel APS Protection

4.7 Configuring Offload Protection

4.8 MPLS-TP Ring Protection Configuration

4.9 Configuring PW APS

4.10 Configuring PW FPS

4.1 Configuring an MPLS Tunnel

4.1.1 MPLS Tunnel Overview

4.1.1.1 MPLS and MPLS Tunnel

4.1.1.2 Application of the MPLS Tunnel

Transparent Transmission of Point-to-Point Data Packets

Tunnel Protection Group

4.1.2 MPLS Tunnel Functions Supported by Chassis-shaped PTN Devices

Function Description PTN 3900 PTN 3900-8 PTN 1900

Static MPLS tunnel - √ √ √

Dynamic RSVP-TE tunnel - √ √ √

4.1.3 MPLS Tunnel Functions Supported by Chase-shaped PTN Devices

Static MPLS tunnel - √ √ √ √

Dynamic RSVP-TE tunnel - √ √ √ √

Static MPLS tunnel - √ √ √ √

Dynamic RSVP-TE tunnel - × × × ×

4.1.4 Creating MPLS Tunnels in End-to-End Mode

You are an NMS user with "Maintenance Group" authority or higher.

2. Configure basic information.

3. Configure the NE list.

Use any of the following methods to select an NE:

i. Click Add and choose NE.

b. Optional: If you create a static CR tunnel, perform the following operations:

4.1.4.2 Creating Tunnels in Batches

You are an NMS user with "Maintenance Group" authority or higher.

2. Configure basic information, such as Network Type and Signaling Type.

3. Configure the NE list.

Use any of the following methods to select an NE:

i. Click Add and choose NE.

b. Optional: NE Role can be set when Network Type is set to Hub-Spoke.

5. Configure tunnel details.

6. Select the Deploy check box and click OK.

4.1.4.3 Parameter Description

Parameter Description Settings

Tunnel Name Definition: Setting method:

Protocol Type Definition: Setting method:

Signaling Type Definition: Setting method:

Template Definition: Setting method:

Auto-Calculate route Definition: Setting method:

Restriction Bandwidth (Kbit/s) Definition: Setting method:

Create reverse tunnel Definition: Setting method:

Configure As Bypass Tunnel Definition: Setting method:

Create Bidirectional Tunnel Definition: Setting method:

Create Protection Group Definition: Setting method:

Remarks Definition: Setting method:

Deploy Definition: Setting method:

Enable Definition: Setting method:

Table 4-5 NE list

Parameter Description Settings

Node Role Definition: Setting method:

Table 4-6 Parameters relevant to the configuration of a static CR tunnel

Parameter Description Settings

Tunnel ID Definition: Setting method: