1830 PSS Control Plane Management

06.07.
2017 1830 PSS control plane management
1830 PSS control plane management
Contents
1. Purpose
2. 11. 1830 PSS GMRE control plane management
2.1. Purpose
2.2. Control plane management
2.2.1. Overview
2.2.1.1. General information
2.2.1.2. GMPLS
2.2.1.3. ASON
2.2.1.4. Layer 1 GMRE control plane support
2.2.2. Workflow to manage the 1830 PSS layer 1 GMRE
2.2.2.1. Workflow
2.2.2.2. Process
2.3. ASON domain management
2.3.1. Overview
2.3.1.1. Introduction
2.3.2. Procedure 111: To configure an ASON domain
2.3.2.1. Steps
2.3.3. Procedure 112: To view the default ASON domain
2.3.3.1. Steps
2.4. CP node — GMRE installation and discovery
2.4.1. GMRE
2.4.1.1. Installation
2.4.2. Discovery
2.4.2.1. CP node discovery
2.4.3. Procedure 113: To discover a CP node
2.4.3.1. Steps
2.4.4. CP node discovery of an already managed OCS device
2.4.4.1. Overview
2.4.5. Procedure 114: To configure GMRE software on an OCS device managed by the 5620 SAM
2.4.5.1. Steps
2.4.6. ASON licensing and adding the GMREenabled OCS nodes to the ASON domain
2.4.6.1. Overview
2.4.7. Procedure 115: To add the GMREenabled OCS nodes to ASON domain
2.4.7.1. Steps
2.5. ASON domain infrastructure
2.5.1. Data bearers
2.5.1.1. Overview
2.5.2. L1 OTU drop data bearers
2.5.2.1. L1 OTU drop data bearers
2.5.3. Procedure 116: To configure an L1 OTU drop data bearer
2.5.3.1. Steps
2.5.4. L1 client transparent drop data bearers
2.5.4.1. L1 client transparent
2.5.5. INNI data bearers
2.5.5.1. INNI
2.5.6. TE links
2.5.6.1. Overview
2.5.6.2. Data bearer links
2.5.6.3. Unterm ODU trail
2.5.7. Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links
2.5.7.1. Steps
2.5.8. Procedure 118: To configure the missing Unterm ODU trails
2.5.8.1. Steps
2.5.9. Procedure 119: To discover the Unterm ODU trails
2.5.9.1. Steps
2.5.10. Procedure 1110: To modify the properties on an Unterm ODU trail
2.5.10.1. Steps
2.5.11. Shared risk groups
2.5.11.1. Overview
2.5.12. Procedure 1111: To configure SRGs
2.5.12.1. Steps
2.6. OGLSP
2.6.1. Overview
2.6.1.2. Nominal path
2.6.1.3. Softpermanent connection type
2.6.1.4. Restore OGLSP nominal paths
2.6.1.5. Discovery of OGLSP
2.6.1.6. Discovery of the control plane ODU trail
2.6.2. Protection and restoration
2.6.2.2. Unprotected
2.6.2.3. Source based restoration (SBR)
https://infocenter.alcatellucent.com/public/5620SAM130R6A/advanced/print.jsp?topic=/SAM_OUG/html/qzx54.html&cp=10_6 1/16
06.07.2017 1830 PSS control plane management
2.6.2.4. Guaranteed restoration (GR)
2.6.2.5. Subnetwork connection protection (SNCP)
2.6.2.6. Protection and restoration combined (PRC)
2.6.3. Procedure 1112: To configure an OGLSP
2.6.3.1. Steps
2.6.4. Procedure 1113: To discover the OGLSPs
2.6.4.1. Steps
2.6.5. Procedure 1114: To discover the ODU trails
2.6.5.1. Steps
2.6.6. GMRE protection switching
2.6.6.1. Overview
2.6.7. Procedure 1115: To perform protection switching from main to spare or spare to main
2.6.7.1. Steps
2.7. ASON color management
2.7.1. Overview
2.7.2. Procedure 1116: To modify color description
2.7.2.1. Steps
2.8. GMRE software upgrade
2.8.1. Overview
2.8.2. Procedure 1117: View the software version of the CP node
2.8.2.1. Steps
2.8.3. Procedure 1118: Upgrade the active network version of the CP node
2.8.3.1. Steps
2.9. GMRE alarm management and correlation
2.9.1. Overview
Part IV: 1830 PSS control plane management
Overview
Purpose
This part provides information about the control plane management.
Contents
Chapter 11, 1830 PSS GMRE control plane management
2. Chapter 11: 1830 PSS GMRE control plane
management
Overview
Purpose
This chapter provides information about the control plane management.
Contents
Control plane management
Workflow to manage the 1830 PSS layer 1 GMRE
ASON domain management
Procedure 111: To configure an ASON domain
Procedure 112: To view the default ASON domain
CP node — GMRE installation and discovery
GMRE
Discovery
Procedure 113: To discover a CP node
CP node discovery of an already managed OCS device
Procedure 114: To configure GMRE software on an OCS device managed by the 5620 SAM
ASON licensing and adding the GMREenabled OCS nodes to the ASON domain
Procedure 115: To add the GMREenabled OCS nodes to ASON domain
ASON domain infrastructure
Data bearers
L1 OTU drop data bearers
Procedure 116: To configure an L1 OTU drop data bearer
L1 client transparent drop data bearers
INNI data bearers
TE links
Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links
Procedure 118: To configure the missing Unterm ODU trails
Procedure 119: To discover the Unterm ODU trails
Procedure 1110: To modify the properties on an Unterm ODU trail
Shared risk groups
Procedure 1111: To configure SRGs
OGLSP
Protection and restoration
Procedure 1112: To configure an OGLSP
Procedure 1113: To discover the OGLSPs
Procedure 1114: To discover the ODU trails
GMRE protection switching
Procedure 1115: To perform protection switching from main to spare or spare to main
ASON color management
Procedure 1116: To modify color description
GMRE software upgrade
Procedure 1117: View the software version of the CP node
Procedure 1118: Upgrade the active network version of the CP node
GMRE alarm management and correlation
2.2. Control plane management
Overview
Workflow to manage the 1830 PSS layer 1 GMRE
2.2.1. Overview
General information
The evolution of data applications and the increasing need for ondemand network bandwidth services has put networks
under pressure, challenging operators with service provisioning and management simplification. The challenge is to
manage all of the different transport layers: circuit, packet, and photonic layers. An intelligent control plane using ASON
and GMPLS technologies increases network availability, while protecting services against failures.
The ASON and GMPLS control plane coordinates the operations and provisioning of multilayer networks that provide the
capacity and scale to support innovative services while optimizing network resources. The ASON and GMPLS control plane
gives service providers the ability to build and manage networks efficiently, control operating costs, and support emerging
traffic demands.
GMPLS
GMPLS is a set of protocols that extends MPLS to provide the control plane (signaling and routing) for devices that switch
in different domains, including wavelength and fiber. The common control plane simplifies network operation and
management by automating endtoend provisioning of connections, managing network resources, and providing the level
of QoS.
ASON
An Automatically Switched Optical Network (ASON) is a an architecture that enables the automatic delivery of transport
services. In an ASON architecture, each device should be equipped with a control plane. The control plane sets up and
releases connections and may restore a connection in case of a failure.
The ASON relies on the GMPLS protocol to reroute traffic dynamically around a failure. When the failure in the network is
repaired, the connection is returned to its original route automatically or upon demand, depending on the connection
settings.
Layer 1 GMRE control plane support
The AlcatelLucent GMPLS Routing Engine (GMRE) is a software package which contains the GMPLS control plane
application. The software package is installed on the First Level Controller (FLC) card of an OCS device and activated on
each node in the network using CLI commands.
The GMREenabled OCS device functions as the control plane and executes the GMPLS protocol suite. The resources of
the GMREenabled OCS devices are stored in a topology database, and used for routing, link, and alarm administration.
The 5620 SAM supports the configuration of the layer 1 GMRE network for 1830 PSS OCS devices. The 5620 SAM supports
the configuration and management of:
control plane connections—originate and terminate in the ASON network
managed plane connections—provisioned outside of the ASON network, which is the traditional method of managing
connections within a network.
2.2.2. Workflow to manage the 1830 PSS layer 1 GMRE
Workflow
Figure 111: GMRE management workflow
The following workflow describes the sequence of highlevel tasks required to manage and configure the 1830 PSS layer 1
GMRE.
Process

1 Install the GMRE software on 1830 PSS OCS devices. See the AlcatelLucent 1830 PSS GMPLS/GMRE Guide for more
information about GMRE configuration on the 1830 PSS OCS devices.
2 Configure the ASON domain; see ASON domain management .
3 Discover the GMREenabled OCS nodes by the 5620 SAM; see CP node — GMRE installation and discovery .
4 Add the GMREenabled OCS nodes to the ASON domain; see ASON licensing and adding the GMREenabled OCS
nodes to the ASON domain .
5 Set up the layer 1 ASON domain infrastructure:
1. Configure the data bearers; see ASON domain infrastructure .
2. Configure the TE links and data bearer links; see TE links .
3. Configure the SRGs; see Shared risk groups .
6 Configure the OGLSPs; see OGLSP .
7 As required, configure the GMRE protection; see GMRE protection switching .
8 As required, configure the color for the GMRE entities; see ASON color management .
9 As required, update the software version of the CP nodes; see GMRE software upgrade .
2.3. ASON domain management
Overview
Procedure 111: To configure an ASON domain
Procedure 112: To view the default ASON domain
2.3.1. Overview
Introduction
The 5620 SAM supports the configuration of the ASON domain. See Procedure 111: To configure an ASON domain for
more information about how to configure the ASON domain. The default ASON domain is configured when you configure
the GMRE for the first time. The default ASON domain cannot be deleted.
The 5620 SAM allows you to manage all of the ASON domain objects from the default ASON domain. See Procedure 112:
To view the default ASON domain for more information about how to navigate to the default ASON domain.
You can perform the following functions from the ASON Domain (Edit) form:
view control plane node properties
view subnode properties
configure data bearers; see ASON domain infrastructure
manage TE links and data bearer links; see TE links
configure SRGs; see Shared risk groups
configure OGLSPs; see OGLSP
color management; see ASON color management
2.3.2. Procedure 111: To configure an ASON domain
Steps

1 Perform one of the following:
a. Configure the ASON domain from the Manage menu:
1. Choose Manage→GMPLS→ASON GMPLS Topology from the 5620 SAM main menu. The ASON GMPLS Topology
form opens.
2. Click Create→Create ASON Domain. The ASON Domain (Create) form opens.
b. Choose Create→ASON GMPLS Topology→ASON Domain from the 5620 SAM main menu. The ASON Domain
(Create) form opens.
2 Configure the required parameters, save your changes, and close the form.
EȀ往� �� �憀�ȀȀ�
2.3.3. Procedure 112: To view the default ASON domain
Steps

1 Choose Manage→GMPLS→ASON GMPLS Topology from the 5620 SAM main menu. The ASON GMPLS Topology form
opens.
2 Click Search to view the default ASON domain.
3 Choose the default ASON domain entry and click Properties. The ASON Domain (Edit) form opens.
4 View the GMRE entities and close the forms.
EȀ往� �� �憀�ȀȀ�
2.4. CP node — GMRE installation and discovery
GMRE
Discovery
Procedure 113: To discover a CP node
CP node discovery of an already managed OCS device
Procedure 114: To configure GMRE software on an OCS device managed by the 5620 SAM
ASON licensing and adding the GMREenabled OCS nodes to the ASON domain
Procedure 115: To add the GMREenabled OCS nodes to ASON domain
2.4.1. GMRE
Installation
The GMRE software package is installed on the controller card, that is, the FirstLevel Controller (FLC) of the 1830 PSS
OCS device software. See the AlcatelLucent 1830 PSS GMPLS/GMRE Guide for more information about GMRE
configuration on the 1830 PSS OCS devices.
A CP node is an OCS node with GMRE installed. The CP node has an IP address and a node ID called the control plane
node ID (CPNodeId). The IP address and node ID must be unique in the network. The node ID and IP address can be
assigned with the same value, but they are independently used by the GMRE.
A CP node is divided into logical subnodes. The subnodes are each of the OCS shelves. Each subnode is identified in the
network by a data plane node ID (DPNodeId).
2.4.2. Discovery
CP node discovery
The CP node is discovered by the 5620 SAM and the procedure is similar to the OCS device discovery procedure. See
Procedure 113: To discover a CP node for more information about how to discover the CP node.
2.4.3. Procedure 113: To discover a CP node
Steps

1 Install the GMRE software package on the controller card. See the AlcatelLucent 1830 PSS GMPLS/GMRE Guide for
more information about GMRE installation on the 1830 PSS OCS devices.
2 Configure the mediation policy. See Procedure 76: To configure NE mediation .
3 Configure the discovery rule. See Procedure 77: To configure a discovery rule .
The GMREenabled OCS device appears on the physical topology map and on the equipment tree.
Note: The GMRE is not discovered until the CP node is added to the ASON domain.
4 Add the GMREenabled OCS node to the ASON domain. See Procedure 115: To add the GMREenabled OCS nodes to
ASON domain .
The CP node is synchronized.
The CP node object display the “G” character on the physical topology map and “GMPLS” label on the equipment tree.
EȀ往� �� �憀�ȀȀ�
2.4.4. CP node discovery of an already managed OCS device
Overview
If the 1830 PSS OCS device is already managed by the 5620 SAM, the GMRE configuration is carried out from the GMRE
CLI cutthrough and the OCS device is resynchronized on the 5620 SAM. See Procedure 114: To configure GMRE
software on an OCS device managed by the 5620 SAM for more information about how to configure the GMRE on the OCS
device that is managed by the 5620 SAM.
2.4.5. Procedure 114: To configure GMRE software on an OCS
device managed by the 5620 SAM
Steps

1 Rightclick on the OCS device in the topology map and choose NE Sessions→SSH Session. The SSH Session form and
a dialog box opens.
2 Enter the login credentials in the dialog box.
3 Enter the Port parameter value as 22 and click OK. The dialog box closes and the SSH Session form appears.
4 Enter the following at the command prompt:
cli ↵
5 Install the GMRE software package. See the AlcatelLucent 1830 PSS GMPLS/GMRE Guide for more information about
GMRE installation on the 1830 PSS OCS devices.
6 Rightclick on the 1830 PSS OCS device object on the equipment tree or in the physical topology map, and choose
Resync→Customized Resync. The Resync Site(s) step form opens.
7 Select Choose MIB Entries and click Next. The Choose MIB Entries form opens.
8 Enter optical.CpMgrDataTableEntry in the MIB Entry field and click Search. The MIB entry is listed.
9 Choose the MIB entry, click Finish to resynchronize the MIB, and close the form.
10 Add the GMREenabled OCS nodes to the ASON domain. See Procedure 115: To add the GMREenabled OCS nodes
to ASON domain .
The CP node is synchronized.
The CP node object displays the “G” character on the physical topology map and “GMPLS” label on the equipment
tree.
EȀ往� �� �憀�ȀȀ�
2.4.6. ASON licensing and adding the GMREenabled OCS nodes
to the ASON domain
Overview
The 5620 SAM supports the licensing of the CP nodes. A 5620 SAM NElevel license is required before the 5620 SAM
enables the control plane part of the node that has GMRE installed.
The license information is displayed on the Devices and Quantities Licensed tab of the Help→5620 SAM License
Information→5620 SAM License (Edit) form. If the Remaining table entry count for the 1830 GMPLS Node table entry is
less than one, the CP node is not discovered by the 5620 SAM.
The GMRE entities are synchronized after the GMREenabled OCS nodes are added to the ASON domain. See Procedure
115: To add the GMREenabled OCS nodes to ASON domain for more information about adding the GMREenabled OCS
nodes to the ASON domain . One NElevel license is used for each OCS node that is added to the ASON domain. The count
of the licenses used is also displayed in the Manage→GMPLS→ASON GMPLS Topology→ASON GMPLS Topology form.
After adding the GMREenabled OCS nodes to the ASON domain:
the GMRE entities are populated in the ASON Domain (Edit) form
the “GMPLS” label appears against the device object in the equipment tree
the “G” character appears on the device icon in physical topology map
2.4.7. Procedure 115: To add the GMREenabled OCS nodes to
ASON domain
Steps

1 Perform Procedure 112: To view the default ASON domain to open the ASON Domain (Edit) form.
2 Click on the GMREenabled NEs tab and click ADD.
3 Choose the GMREenabled OCS nodes that need to be added to the ASON domain.
EȀ往� �� �憀�ȀȀ�
2.5. ASON domain infrastructure
Data bearers
Procedure 116: To configure an L1 OTU drop data bearer
INNI data bearers
TE links
Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links
Procedure 118: To configure the missing Unterm ODU trails
Procedure 119: To discover the Unterm ODU trails
Procedure 1110: To modify the properties on an Unterm ODU trail
Shared risk groups
Procedure 1111: To configure SRGs
2.5.1. Data bearers
Overview
The 5620 SAM supports the configuration of the following data bearers:
Drop
INNI
2.5.2. L1 OTU drop data bearers
L1 drop data bearers assign a client port to the control plane and L1 drop data bearers provide endpoints for SPC
services. Therefore, L1 drop data bearers are also called SPC endpoints. Signaling and routing protocols are not run on L1
drop data bearers. See Procedure 116: To configure an L1 OTU drop data bearer for more information about how to
configure L1 drop data bearers.
Configure the L1 OTU drop data bearer on an OTU port of an I/O card in an 1830 PSS OCS GMRE device.
2.5.3. Procedure 116: To configure an L1 OTU drop data bearer
Steps

a. Configure an L1 OTU drop data bearer from the equipment tree:
1. On the equipment tree, expand Network→1830 PSS OCS (GMPLS)→Shelf→I/O card→OTU port.
2. Rightclick on the port object and choose Create DROP data Bearer. The Data Bearer (Create) form opens
with all the parameters configured.
b. Configure an L1 OTU drop data bearer from the ASON default domain:
1. Perform Procedure 112: To view the default ASON domain to open the ASON Domain (Edit) form.
2. Click on the Data Bearers tab and click Create. The Data Bearer (Create) form opens.
3. Select a subnode in the ASON SubNode DP Node ID panel and a port in the Local Port Pointer panel.
c. Configure an L1 OTU drop data bearer from the 5620 SAM main menu:
1. Choose Create→ASON GMPLS Topology→DROP data Bearer from the 5620 SAM main menu. The Data Bearer
(Create) form opens.
2. Select a subnode in the ASON SubNode DP Node ID panel and a port in the Local Port Pointer panel.
2 Save your changes and close the forms.
EȀ往� �� �憀�ȀȀ�
2.5.4. L1 client transparent drop data bearers
L1 client transparent
The L1 client transparent drop data bearer is configured on a nonOTU port, for example, SONET, SDH, or GbE port, of an
I/O card in an 1830 PSS OCS GMRE device. Perform Procedure 116: To configure an L1 OTU drop data bearer to
configure an L1 client transparent drop data bearer by choosing the nonOTU port.
2.5.5. INNI data bearers
INNI
INNI data bearers assign a line port to the control plane. When INNI data bearers are discovered, a data bearer link is
configured between the OTU ports of the OCS uplink or I/O cards of two 1830 PSS OCS subnodes that point to each
other. See Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links for more
information about how to configure the data bearer links.
2.5.6. TE links
Overview
A traffic engineering link is a GMRE entity that is configured by grouping the other GMRE entities like data bearer link,
SRGs, or metrics. The grouping reduces the amount of information sent through the network.
The 5620 SAM supports the configuration of TE links. You can configure metric (cost), color, data bearer link, and assign
SRGs for a TE link.
See Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links for more information
about how to configure the TE links and data bearer links.
Data bearer links
The 5620 SAM supports the configuration of data bearer links between the OTU line ports of the OCS uplink or I/O cards.
A physical or logical link needs to be configured between the OTU ports of the OCS uplink or I/O cards before the
configuration of the data bearer links.
A physical link is established when you configure an optical link between OTU ports. See Procedure 919: To configure an
optical link between ports for more information about how to configure optical links.
A logical link is established when you configure OTU trails between OTU ports. See Procedure 136: To configure an OTU
trail for more information about how to configure OTU trails.
See Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links for more information
about how to configure the TE links and data bearer links.
If a physical link is established between two OCS INNI ports, the corresponding OTU trails and ODUk crossconnects are
autoconfigured during the data bearer link configuration. The 5620 SAM performs a path search and if there is a path
between the two ports, an Unterm ODU trail is autoconfigured. If no path is found, the data bearer link configuration fails.
The data bearer links need to be assigned to a TE link, so that the data bearer link is made available for a service. You
can add the data bearer links to an existing or a new TE link. See Procedure 117: To configure a TE link, a data bearer
link, and assign SRGs with the TE links for more information about how to configure data bearer links.
Unterm ODU trail
The 5620 SAM automatically configures the underlying HO Unterm ODU trail, when the data bearer link is configured
between the INNI ports. See Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE
links for more information about how to configure the data bearer links and TE links.
The 5620 SAM supports the configuration of the missing Unterm ODU trails, for the data bearer links that do not have
associated Unterm ODU trails. See Procedure 118: To configure the missing Unterm ODU trails for more information
about how to configure the missing Unterm ODU trails.
The 5620 SAM supports the discovery of Unterm ODU trails for the data bearer links when the CP nodes are discovered or
the Unterm ODU trail is unmanaged. See Procedure 119: To discover the Unterm ODU trails for more information about
how to discover the Unterm ODU trails.
Note: Ensure that the Unterm ODU trail discovery is performed every time the CP nodes are added to the ASON domain,
The 5620 SAM allows you to modify the attributes of the Unterm ODU trails. See Procedure 1110: To modify the
properties on an Unterm ODU trail for more information about how to modify the attributes of an Unterm ODU trail.
2.5.7. Procedure 117: To configure a TE link, a data bearer link,
and assign SRGs with the TE links
Steps

a. Configure TE links from the ASON default domain:
1. Perform Procedure 112: To view the default ASON domain to open the ASON Domain (Edit) form.
2. Click on the TE Links tab and click Create. The TE Link (Create) form opens.
b. Choose Create→ASON GMPLS Topology→TE Link from the 5620 SAM main menu. The TE Link (Create) form
opens.
Configure cost and latency

2 Configure the required parameters.
3 Select the sites in the Endpoint A TE Link Endpoint and Endpoint Z TE Link Endpoint panels.
4 Configure the parameters in the Traffic Engineering Parameters panel to manage cost and latency.
Assign colors

5 Click on the Colors tab and assign a color ID to the TE link to identify the TE link in the network.
6 Click on the States tab and configure the Administrative State parameter.
Assign SRGs

7 Click on the SRGs tab and click Add. The Select SRG form opens.
8 Choose SRGs and click OK to assign the SRGs to the TE link.
Configure a data bearer link

9 Click on the Databearer Links tab and click Create. The Data Bearer Link (Create) form opens.
10 Configure the required parameters and the parameters in the Unterm ODU Trail panel.
11 Select the ports in the Endpoint A and Endpoint Z panels.
Note: Ensure that a physical connectivity exists between the ports. See Procedure 919: To configure an optical link
between ports for more information about how to configure an optical link.
12 If a path constraint needs to be configured, click on the Path Constraints tab and click Create. The Optical Path
Constraint (Create) form opens.
13 Configure the required parameters and select the port, site, trail, ODUk timeslot, or optical link, depending on the
constraint element
EȀ往� �� �憀�ȀȀ�
2.5.8. Procedure 118: To configure the missing Unterm ODU
trails
Steps

2 Click on the Databearer Links tab.
3 Choose the data bearer link with the missing Unterm ODU trail and click Properties.
4 Click Create Unterm ODU Trail.
The Create Unterm ODU Trail button is dimmed for the data bearer links that have an associated Unterm ODU trail.
5 Choose an entry and click Properties. The Unterm ODU Trail (Edit) form opens.
EȀ往� �� �憀�ȀȀ�
2.5.9. Procedure 119: To discover the Unterm ODU trails
Steps

1 Perform Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links to configure the
data bearer links between the INNI ports.
2 Choose Manage→OTN→OTN Trails. The Manage OTN trails form opens.
3 Choose Unterm ODU Trail (Optical Management) from the object contextual menu and click Discover Optical Trails.
The Discover Optical Trails form opens.
4 Choose the equipment group and click OK. The Unterm ODU trails are listed.
One Unterm ODU trail is autoconfigured for each data bearer link that is configured.
EȀ往� �� �憀�ȀȀ�
2.5.10. Procedure 1110: To modify the properties on an Unterm
ODU trail
Steps

1 Perform Procedure 117: To configure a TE link, a data bearer link, and assign SRGs with the TE links to configure the
data bearer links between the INNI ports.
2 Choose Manage→OTN→OTN Trails. The Manage OTN trails form opens.
3 Choose Unterm ODU Trail (Optical Management) from the object contextual menu. The Unterm ODU trails are listed.
4 Choose an entry and click Properties. The Unterm ODU Trail (Edit) form opens.
5 If a path constraint needs to be configured, click on the Path Constraints tab and click Create. The Optical Path
Constraint (Create) form opens.
6 Configure the required parameters and select the port, site, trail, ODUk timeslot, or optical link depending on the
constraint element
7 Save your changes, wait for the changes to be populated in the forms, and close the forms.
EȀ往� �� �憀�ȀȀ�
2.5.11. Shared risk groups
Overview
An SRG is a set of physical connections and objects that share a common risk. The failure of one of the objects can cause
the failure of all the elements in the group. The SRGs provide a redundant route through the network for an existing
route, avoiding the same problem; for example, a link failure that disturbs both the routes.
SRGs are identified by SRG IDs, which need to be unique in a GMRE domain. The 5620 SAM supports the configuration of
the SRGs with unique IDs.
See Procedure 1111: To configure SRGs for more information about how to configure SRGs, and Procedure 117: To
configure a TE link, a data bearer link, and assign SRGs with the TE links for more information about how to assign SRGs
to a TE link.
2.5.12. Procedure 1111: To configure SRGs
Steps

2 Click on the SRGs tab and click Create.The SRG (Create) form opens.
3 Configure the required parameters.
Note: The SRGs are deployed when they are assigned to a TE link. One or more SRGs have to be assigned to the TE
links in the ASON network that share at least one risk.
EȀ往� �� �憀�ȀȀ�
2.6. OGLSP
Overview
Protection and restoration
Procedure 1112: To configure an OGLSP
Procedure 1113: To discover the OGLSPs
Procedure 1114: To discover the ODU trails
GMRE protection switching
Procedure 1115: To perform protection switching from main to spare or spare to main
2.6.1. Overview
Introduction
OGLSP is a layer 1 service between two GMRE nodes in a subnetwork. See Procedure 1112: To configure an OGLSP for
information about configuration of an OGLSP.
Nominal path
A nominal path is established when an OGLSP is configured. According to the GMRE, the nominal path is the best path
available under ideal network conditions. When a failure occurs in the nominal path, a backup path is created by the
GMRE. The backup path is not the best path. The GMRE finds a backup path to keep the traffic flow up, until the nominal
path is fixed.
Softpermanent connection type
The 5620 SAM supports the configuration of the softpermanent connection. A softpermanent connection is an end to end
service between a source node and destination node which may or may not go through intermediate nodes. See
Procedure 1112: To configure an OGLSP for information about configuration of an OGLSP.
Restore OGLSP nominal paths
You can configure the following Reversion Mode parameter options to switch traffic to the nominal path when the failure is
fixed.
Manual—The reversion process involves manual intervention to reroute the carried services, before switching to the
nominal path. Choose Switch Route→Nominal or Registered Backup at the bottom of the Optical OGLSP (Edit) form to
perform this task. See Procedure 1112: To configure an OGLSP for information about configuration of an OGLSP.
Automatic—Within five minutes of nominal path restoration, the 5620 SAM automatically switches to the nominal path.
By default, the 5620 SAM sets the path reversion to automatic mode.
SoftAutomatic—The reversion process involves triggering the carried services to reroute. The rerouting is monitored
for timeout. When the path does not have any services, the path reversion is initiated.
Discovery of OGLSP
The 5620 SAM supports the discovery of the OGLSPs configured on the CP nodes. See Procedure 1113: To discover the
OGLSPs for more information about how to discover the OGLSPs.
Discovery of the control plane ODU trail
The CP node ODU trail is automatically configured when an Active OGLSP (that is, with a valid path) is configured. The
5620 SAM supports the discovery of the ODU trail configured on the CP nodes. See Procedure 1114: To discover the ODU
trails for more information about how to discover the ODU trails.
2.6.2. Protection and restoration
Introduction
This topic describes the OGLSP protection and restoration methods using the 5620 SAM.
Unprotected
There is no backup path available if a failure occurs in the nominal path.
Source based restoration (SBR)
If a failure occurs in the nominal path, a backup path is created. If the backup path fails, another backup path is created
until no more backups can be found. After the nominal path failure is fixed, one of the following occurs to switch the traffic
to nominal path:
If the reversion mode is set as automatic, the GMRE switches the traffic to the nominal path.
If the reversion mode is set as manual, you need to choose Switch Route→Nominal on the Optical OGLSP (Edit) form
to switch the traffic to the nominal path. See Procedure 1112: To configure an OGLSP for information about
configuration of an OGLSP.
Guaranteed restoration (GR)
If a failure occurs in the nominal path, the precalculated backup path is activated as the backup path, and another
backup is calculated by the GMRE. The precalculated backup path is always different from the nominal path. After the
nominal path failure is fixed, the GMRE switches the traffic to the nominal path.
Subnetwork connection protection (SNCP)
The two paths of a protected service in a GMRE domain are referred to as main and spare paths. If a failure occurs in the
nominal main path, the traffic is switched to the nominal spare path. However, no restoration is supported. The traffic path
is automatically switched through the control plane APS group.
Note: Internal SNCP
In a GMRE domain, internal SNCP is a service of protection type SNCP between GMRE domainboundary nodes.
In a unidirectional operation, traffic is bridged in the source node, also known as the headend node. In the destination
node, also known as the tailend node, a selector switch is implemented. The selector switch selects the traffic received
through either of the two paths, the main or spare path.
In a bidirectional operation, each of the end nodes of the SNCP works as a bridge for one direction and as a selector
switch for the opposite direction.
Protection and restoration combined (PRC)
If a failure occurs in the nominal main path or the nominal spare path, main and spare backup paths are created. After
the failure in the nominal main or spare paths is fixed, the GMRE switches the traffic to the nominal main or spare paths.
The path is switched through the control plane APS group.
2.6.3. Procedure 1112: To configure an OGLSP
Before you begin
You must configure an INNI data bearer link before you configure an OGLSP. To configure an OGLSP with restoration
method, ensure there are sufficient INNI links available. See TE links for more information about data bearer link
configuration.
Steps

1 Perform one of the following to open the Optical GLSP (Create) form.
a. Choose Create→ASON GMPLS Topology→OGLSP from the 5620 SAM main menu. The Optical GLSP (Create) form
opens.
b. Perform Procedure 112: To view the default ASON domain to open the ASON Domain (Edit) form and click
Create→Create OGLSP. The Optical GLSP (Create) form opens.
c. Rightclick on the GMRE device on the Physical Topology map or equipment tree and choose Create OGLSP. The
Optical GLSP (Create) form opens with Site (Z End) object configured.
2 Configure the general OGLSP parameters.
3 Configure the required parameters in the Protection and Restoration panel.
4 Configure the required parameters in the Constraints and Violations panel.
5 Rightclick on the Sites object on the navigation tree and choose Create OGLSP Site. The Select Network Element
form opens.
6 Choose the sites and click OK. The Site objects are listed under the Optical GLSP tree.
7 Rightclick on the Site (A End) object and choose Create OGLSP Termination Point. The Select Termination Point form
opens.
8 Choose the termination point and click OK.
9 Repeat Step 7 to Step 8 to configure the termination point on the Site (Z End).
10 Click Apply to save your changes.
Configure path constraints

11 Click on the Path Constraints tab and click Create. The Optical Path Constraint (Create) form opens.
12 Configure the Constraint Element parameter.
13 Select the TE link or the OGLSP, depending on the value configured for the Constraint Element parameter in Step 12
, and click OK.
Note: You can configure paths constraints when you configure an OGLSP or modify the path constraints after you
configure the OGLSP.
Configure color

14 Click on the Colors tab.
15 Choose one or more colors from the unassigned list of the Included Colors and Excluded Colors panels and click on
the right arrow.
View hops

16 Click on the Nominal path object on the Optical GLSP tree and click on the Connections tab to view the OGLSP hops.
17 Click Apply to save your changes, and close the forms.
EȀ往� �� �憀�ȀȀ�
2.6.4. Procedure 1113: To discover the OGLSPs
Steps

1 Add the GMREenabled OCS nodes in the ASON domain. See Procedure 115: To add the GMREenabled OCS nodes
to ASON domain .
2 Click on the OGLSPs tab to view the list of the discovered OGLSPs.
EȀ往� �� �憀�ȀȀ�
2.6.5. Procedure 1114: To discover the ODU trails
Steps

1 Add the GMREenabled OCS nodes in the ASON domain. See Procedure 115: To add the GMREenabled OCS nodes
to ASON domain .
Wait until the node resynchronization completes.
2 Choose Administration→Discovery Manager. The Discovery Manager (Edit) form opens.
3 Click on the Resync Status tab and click Search.
Check the resynchronization status of the GMREenabled OCS nodes.
4 Choose Manage→OTN→OTN Trails. The Manage OTN Trails form opens.
5 Click Discover Optical Trails. The Discover Optical Trails form opens.
6 Choose the equipment group and click OK. The ODU trails are listed in the Manage OTN trails form.
Each OGLSP that is configured will have a corresponding ODU trail autoconfigured.
EȀ往� �� �憀�ȀȀ�
2.6.6. GMRE protection switching
Overview
The 5620 SAM allows switching from the main to the spare path and from the spare to the main for internal SNCP and PRC
configurations. See Procedure 1115: To perform protection switching from main to spare or spare to main for more
information about how to perform protection switching from main to spare or spare to main paths.
2.6.7. Procedure 1115: To perform protection switching from
main to spare or spare to main
Steps

a. To configure from the subnode, click on the Sub Nodes tab, choose a subnode, and click Properties. The Sub
node (Edit) form opens.
b. To configure from the OGLSP, click on the OGLSPs tab, choose an SNCP or PRC entry, and click Properties. The
Optical GLSP (Edit) form opens.
3 Click on the APS tab, choose an entry, and click Properties. The Protection Switch (Edit) form opens.
4 Configure the Switch Command parameter and switch to main or spare paths.
5 Save the changes and close the forms.
EȀ往� �� �憀�ȀȀ�
2.7. ASON color management
Overview
Procedure 1116: To modify color description
2.7.1. Overview
Introduction
The 5620 SAM autoconfigures 28 predefined colors during the ASON domain configuration. The colors can be assigned
to TE links, physical connections, logical connections, and OGLSPs.
2.7.2. Procedure 1116: To modify color description
Steps

1 Perform the Procedure 112: To view the default ASON domain to open the ASON Domain (Edit) form.
2 Click on the Colors tab. The 28 predefined color IDs are listed.
3 Click on a color ID and click Properties. The Color (Edit) form opens.
4 Configure the Description parameter, click Apply to save the changes, and close the form.
EȀ往� �� �憀�ȀȀ�
2.8. GMRE software upgrade
Overview
Procedure 1117: View the software version of the CP node
Procedure 1118: Upgrade the active network version of the CP node
2.8.1. Overview
Introduction
The 5620 SAM supports the upgrade of the GMRE software. See Procedure 1117: View the software version of the CP
node for more information about how to view the GMRE software version.
The active network version is the GMRE software version that is currently in use. The installed network version is the
GMRE software version at the time of GMRE activation. Only the GMRE features supported by the active network version
of the GMRE software are available on the 1830 PSS OCS GMRE device.
During the software upgrade of the 1830 PSS OCS device, the installed network version is upgraded, but not the active
network version. The 5620 SAM allows you to upgrade the GMRE software to the installed version. See Procedure 1118:
Upgrade the active network version of the CP node for more information about how to upgrade the active network
version.
2.8.2. Procedure 1117: View the software version of the CP
node
Steps

1 Choose Manage→GMPLS→ASON GMPLS Topology from the 5620 SAM main menu. The ASON GMPLS Topology form
opens.
2 Click Search to view the default ASON domain.
3 Choose the default ASON domain and click Properties. The ASON Domain (Edit) form opens.
4 Click on the Control Plane Nodes tab, choose an entry, and click Properties. The Control Plane Node (Edit) form
opens.
The GMRE Software panel displays the active and installed network version.
EȀ往� �� �憀�ȀȀ�
2.8.3. Procedure 1118: Upgrade the active network version of
the CP node
Steps

1 Choose Administration→NE Maintenance→Software Upgrade from the 5620 SAM main menu. The Software Upgrade
form opens.
2 Click on the Software Images tab, then on the OCS Software Images tab, and click Activate GMRE. The Select ASON
Domain form opens.
3 Choose the ASON domain and click OK to upgrade the active network version of the GMRE software.
Note: Ensure that all the GMRE nodes have the same network version installed.
Ensure that all the GMRE nodes in the ASON domain are reachable from the 5620 SAM.
EȀ往� �� �憀�ȀȀ�
2.9. GMRE alarm management and correlation
Overview
2.9.1. Overview
Introduction
The 5620 SAM supports alarm management and alarm correlation of the alarms generated from the CP node. See Alarm
correlation for more information about how to view alarm correlation in the 5620 SAM fault management application.

1830 PSS Control Plane Management

Uploaded by

Document Information

Original Title

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

1830 PSS Control Plane Management

Uploaded by

Copyright:

Available Formats

06.07.

You might also like