ASON Advantage Module

ASON Advantage ModuleIP Transport NMS - Circuit

OPERATING INSTRUCTIONS

1/1551-1/AOM 901 084 Uen C2

Copyright

© Ericsson AB 2011. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

Trademark List

Ericsson and the Ericsson logoare trademarks of Telefonaktiebolaget LM Ericsson.

1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Contents

Contents

1 Introduction To ASON Management 1

1.1 Traditional NMS Management 1

1.2 What Is The ASON 1

1.3 Which Are The Purposes Of ASON 2

1.4 The ASON on IPT NMS - Circuit 2

1.5 Two Types Of Control Planes 3

1.6 Operation Of ASON 4

1.7 ASON Advantage Module 5

2 ASON System Info And Installation 9

2.1 ASTN DD Add-On SW Requirements 9

2.2 ASON Installation And Configuration Procedure 15

3 ASON Traffic And Signalling Management 17

3.1 General 17

3.2 Control Plane Functions 17

3.3 Network Topology 18

3.4 Signalling And Routing Protocols Adopted 19

3.5 ServiceOn/IPT NMS ASON Solution 19

4 Usage Of The IPT NMS - Circuit Graphical Interface 23

4.1 Introduction to the Usage of GUI 23

4.2 Installing The Nodes On IPT NMS - Circuit 25

4.3 Creating The Links 26

4.4 ASTN-DD: Topology Discovery 26

4.5 ASON: Topology discovery 31

4.6 ASON Label Switched Router Query Tool 35

4.7 ASON Link Cluster Query Tool 39

4.8 ASON Link Component Query Tool 50

4.9 ASTN Control Channel Query Tool 55

4.10 Creating The ASTN-DD Circuits 59

4.11 ASTN-DD ERO Management 66

4.12 ASTN-DD Circuit: Safe Disable 75

4.13 Managing The Restore Phase On The ASTN-DD Nodes 76

1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

ASON Advantage Module

4.14 Activating the ASTN-DD Circuits 78

4.15 Deactivating The ASTN-DD Circuits 79

4.16 ASON Circuit Displaying and Details 79

4.17 Modify ASON Circuits 80

4.18 Re-routing An ASTN-DD Circuit 83

4.19 Managing The ASON Protection Switches 85

4.20 Checking The ASON Circuit Working Side 87

4.21 Disassociating An ASON Circuit 88

4.22 Enabling The ASON Protocol On A Circuit 89

4.23 Disabling the ASON Protocol on a Circuit 90

4.24 Managing ASON Alarms From The GUI 91

4.25 Backup And Restore Procedure On ASTN-DD Nodes 91

4.26 Maintenance Pre-Requisites For ASTN-DD NEs 103

4.27 Port operations 105

4.28 Combined Path operations 112

4.29 Control Plane Import Wizard 131

4.30 Control Plane Export Wizard 135

4.31 Control Plane Configuration Wizard 137

4.32 Additional Path Operation 200

4.33 Control Plane Real Time Monitor 201

4.34 Restoration Monitor 209

4.35 Backup and Restore Procedure on WSON Nodes 211

5 Appendix: Common References 213

5.1 ASON: Control Plane Configuration and Main Objects 213

5.2 Standard References 218

5.3 Glossary and Acronyms 219

Reference List 221

1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Introduction To ASON Management

1 Introduction To ASON Management

1.1 Traditional NMS Management

In the traditional NMS management, the Network Management System allowsthe individual configuration of all the nodes involved in the circuit creation. Thefull network is detected by NMS and the request comes directly from S Operator.

Figure 1 Traditional NMS Management

The Operator acts on the GUI Graphical User Interface connected by means ofthe X protocol to the Network Management System.

The Network Manager and the Element Manager can be connected in differentways, according to the network architecture.

The Element Manager is connected to the equipment by means of OSI protocolthrough Q interface.

The commands necessary to make the appropriate configuration start from EM:the NEs do not communicate among them.

See Also:

ASON: Control Plane Configuration and Main Objects

1.2 What Is The ASON

An Automatic Switched Optical Network (ASON) is a type of network basedon equipment supporting GMPLS (Generalized Multi Protocol Label Switch)protocol.

This protocol provides a higher flexibility of the NEs configuration due to thepossibility of SDH NEs to exchange information.

11/1551-1/AOM 901 084 Uen C2 | 2011-12-15


In a network managed by such GMPLS protocol, many operations can be drivendirectly by the Network Elements, in place of the Network Management System.

One Control Plane works among S and all the NEs that support the technology.

The capabilities of the Control Plane can be:

• Distributing the configuration commands to the NEs configured

• Performing the routing calculation for the worker and protection circuit.

• Re-routing circuits when necessary, according to the network operationalstate.

• Activating protections on the basis of Pre-planned resources.

• Notifying the modifications occurred on the NEs.

The availability of the above mentioned features depend on the type of controlplane.

Two types of control plane are supported: Centralized Routing, DistributedSignaling (ASTN-CD) or Distributed Routing, Distributed Signaling (ASTN-DDand WSON).

1.3 Which Are The Purposes Of ASON

The advantages provided by an Automatic Switched Opticla Network are dueto the NEs capability of exchanging information, without the assistance of theNetwork Management System. In this way the speed of the communication ishigher and the network reaction to configuration and switching is faster.

Typical applications are:

• Restoration of a fault in a network element-driven network.

• Dynamic re-routing of the traffic in case of loss of resilience

• NE calculation of routing path on external request.

• Overbooking of the protection bandwidth and better usage of the totalnetwork capability.

1.4 The ASON on IPT NMS - Circuit

Two different technologies are managed through the ASON:

• ASTN: Automatic Switched Transport Network for SDH NEs

• WSON: WDM Switched Optical Network fro WDM NEs

2 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Warning!

Only one of the above mentioned technologies can be enabled on an instanceof IPT NMS - Circuit.

1.5 Two Types Of Control Planes

The implementation of ASTN control plane can be carried out in two differentmodes that depend on the NE and Network Management System configurationand releases.

1.5.1 ASTN CD Control Plane

The architecture of ASTN-CD application is arranged in both Element Managerand Network Manager. Plus, an appropriate application needs to be loadedon the NEs. In the Element Manager a specific process deals with thedistribution of the message towards the NEs. In the Network Manager theusual architecture manages a set of commands to drive the operation. Inthe ASTN-CD the routing takes place on S while the NEs activate the trafficresources by means of the GMPLS signaling. The switches are driven by theNEs through the GMPLS protocol and then notified to S.

The complete routing topology is saved in the IPT NMS - Circuit DB.

See Also:

The two types of Control Planes

1.5.2 ASTN DD Control Plane

The architecture of ASON is mainly based to a distributed GMPLS ControlPlane that is managed by the NEs. On both EM and IPT NMS - Circuit anadditional application is added to the standard architecture, to drive theoperations on Operator commands

In the ASON architecture the routing takes place on the NEs on requestcoming from IPT NMS - Circuit. The approach can be end-to-end as well asnode-by-node. In both cases the control plane provides routing and activation.The Control Plane, according to the configuration provided on IPT NMS- Circuit, directly manages the protection switch and the re-calculation, ifnecessary. The routing topology is stored on the NEs and forwarded to IPTNMS - Circuit on specific customer request (for example: Circuit Details). Thenetwork resources are created and saved on IPT NMS - Circuit DB, on thebasis of their termination points and routing characteristics (type of protectionand diversity). The Control Plane then manages the routing.

31/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:

The two types of Control Planes

1.6 Operation Of ASON

Every Network Element (NE) acts as a router by defining autonomously thecircuit path and the restore options, cooperating with the Network Managementlayer.

By means of this implementation, the network flexibility and the restore timeof a probable crash are significantly improved by means of the auto-discoveryresource of the network.

This mechanism ensures the optimal use without a heavy involvement of theoperator.

The ASON application foresees that the control capability is embedded inevery node, which is able to accept the requests coming directly from IPTNMS - Circuit Graphical User Interface (only the circuit termination points arespecified) and to build a circuit in a totally autonomous way.

Figure 2 Distributed control plan

In this case, the Customer, by means of IPT NMS - Circuit Graphical UserInterface, works directly on the Ingress node that communicates with the nextequipment of the chain.

See Also:


1.6.1 Restoration Protection

One of the main features of the ASON networks is the capability of the nodes toreconfigure themselves autonomously for the implementation of the requiredcircuits, without the need of Central Management System assistance.

When a failure in the network occurs, the circuit termination points (Ingressand Egress) can reconfigure their cross-connections in order to cope with therequirements for the implementation of the new circuit and then immediately

4 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


after to send the reconfiguration command to the adjacent nodes in order tocomplete as faster as possible the rebuilding of the circuit.

The ASON Control Plane is able to manage four basic types of protections:

SNCP At creation time the Control Plane provides both worker and protectionsides. In case of failure on the working side the traffic is routed to the protectionside.

Strong SNCP At creation time the Control Plane provides both working andprotection sides. In case of failure on the protection side the control planeprovides a new route.

On The Fly At creation time the Control Plane provides the working path only.In case of failure of the main route, the control plane calculates an alternativepath and activates it. This protection is revertive; the original working path issaved and restored when the failure goes Off.

Non Revertive On The Fly At creation time the Control Plane provides theworking path only. In case of failure of the main route, the control planecalculates an alternative path and activates it. The new route definitely replacesthe existing one.

See Also:

Modify ASTN-DD Circuits ,Usage of the Graphical Interface

1.7 ASON Advantage Module

The ASON Advantage Module is added on the IP Transport NMS - Circuitapplication. It provides management of the control plane existing among theNEs supporting ASTN-DD or WSON protocol.

After the installation of this Add-On, IPT NMS - Circuit is able to drive theGMPLS distributed control plane either ASTN-DD or WSON

1.7.1 Operating Functions And Options

The ASTN Advantage Module application makes available the followingfunctions:

• Provisioning of Circuits

• Management of protections

• Database management of the trails

• Switch commands

• Circuit and topology discovery from the Control Plane

51/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Bandwidth Management

• Link Cluster Enabling/Disabling

• Alarm Management on the trails

• Circuits Alarm management

• Circuits Restoration event management based on control plane snmp traps

• Circuit History Logging (exportable in excel format)

See Also:

ASON Traffic and Signalling Management

1.7.2 Graphical User Interface

From a general point of view, the Operator uses the same graphical interface ofS to define the network topology and to create the circuits.

The creation of the ASTN-DD/WSON circuits is managed through the AddTrail Wizard, . The management of the protection is performed from the usualRestoration Monitor Window.

The normal circuit management is applied to ASON resources. The JavaGraphical Map distinguishes those commands that are headed to the ASTN-DDControl Plane, those ones that are headed to the WSON Control Plane andthose ones or to legacy network elements.

Some specific commands are modified on IPT NMS - Circuit by the ASONadd-on. This means that the IPT NMS - Circuit is able to drive the correctbehavior of the single command, according to the type of circuit: legacy ratherthan ASTN-DD or WSON.

See Also:

Usage of the Graphical Interface

1.7.3 How to Use This Handbook

This handbook describes the IPT NMS - Circuit GUI windows, which the ASONAdd-On will modify the default layout; the operator is then required havingalready got knowledge about IPT NMS - Circuit GUI.

Where no specific GUI description is reported in this handbook, the procedureto follow is intended as the default one, and then already described in the IPTransport NMS - Circuit User Guide. "Refer To" notes are added when requiredto make reference to the standard procedures.

6 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Warning!

Some of the commands hereby described can be similar as many of themuses the same basic facility, which slightly differ between ASN-DD and WSONapplication.

See Also:

Usage of the Graphical Interface

71/1551-1/AOM 901 084 Uen C2 | 2011-12-15


8 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

ASON System Info And Installation

2 ASON System Info And Installation

2.1 ASTN DD Add-On SW Requirements

Note: The ASTN DD Advantage module is an HP-UX based application.

The following paragraphs describes the installation procedure and the systemmanagement for the ASTN DD Add-On software package.

Following a table containing the software packages that need to be installed,before going on with the ASTN DD Add-On installation:

• OMS-32xx product series Rel. 5.2

• ServiceOn Element Manager R10 (full patch level)

• ServiceOn Element Manager ASTN-DD Configurator Add On

• EM-IMT Plug-in for SO EM

• PEN Interface, for SO EM

• IP Transport NMS - Circuit

ALERT Contact Ericsson Representative to verify which is the latest update foreach of the above package.

2.1.1 ASTN DD Add-On Installation Procedure

Within this section the procedure to enable the ASTN DD Add-On is described.The steps below will guide to a correct installation, in case the softwarerequirements previously listed are already present and correctly working inthe system.

The depot is provided with the following name structure;

IPT-NMS-Circuit-Ason-hpit-<XY>.depot

Where <XY> is the package versioning.

To install it, log in as root and execute the command:

swinstall -s p` wd /` IPT-NMS-Circuit-Ason-hpit-<XY>.depotIPT-NMS-Circuit.ason

Restart the IPT NMS - Circuit processes by means of the Shutdown/Restartutility.

91/1551-1/AOM 901 084 Uen C2 | 2011-12-15


1. Modify the [CPM] section in $MV38/DATA/MV38.ini file by enteringthe Copos Host Name as follows:

[CPM]

CoposAddress = <TheCoposHostName>:12456

2.1.2 ASON Add-On System Architecture

This section will describe the two main ASON engines for both EM and NM:

• The ASTN_DD_Engine on IPT NMS - Circuit so called CPM (Control PlaneManager)

• ASTN_DD_Engine on EM so called COPOS (COntrol Plane Object Server)

Figure 3

2.1.2.1 Control Plane Manager

The Control Plane Manager (CPM) is NE communication protocol independentand mainly consists of:

A data structure to manage ASTN DD networks required object; it managescircuits only. This class contains mainly the following components:

• A collection of objects modeling the single network resources needed forASTN DD management from the Network layer

10 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• A request map

• A free event map

• A promoted resources map

� PEN CORBA IDL Client interfaces to EM system

� DBI CORBA IDL Client Interface to Database (via DBOS process)

� ASN.1 Interfaces for IPT NMS - Circuit Core processes in order toprovide interoperability with current implementation on NM

� A data structure manager object

A core multithreaded Java process to manage the CPM functions, composedby:

• A thread managing requested commands; one thread is started for eachrequest to be sent to different nodes; for multiple requests to the samenode, a queue is used in the dedicated thread to avoid request storming tothe NE SNMP agent; the thread has a static instance of the data structuremanager object.

• A thread to manage the DD Events (Event Manager); it receives specificevents from the DD manager (COntrol Plane Object Server (COPOS)) onEM, through a CORBA callback interface.

� Communication between COPOS and CPM is done by the PEN,therefore via CORBA

� CORBA environment

� A name service definition

The CPM interfaces with the following IPT NMS - Circuit Core processes:

• EH process, for events/fault management purpose

• UM process, to receive requests and send reports after operationcompletion.

111/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 4

2.1.2.2 COntrol Plane Object Server

The COntrol Plane Object Server (COPOS) basically consists of the followingmodules:

• The PEN CORBA IDL Server interfaces

• The PEN_Standard_Manager standard methods implementation

• A MIB adapter in order to translate IPT NMS - Circuit requests in SNMPcommands, through NE MIBs and trap events received via UDP to IPTNMS - Circuit events.

• A data structure composed by:

� A collection of objects modeling the single network resources neededfor ASTN DD management from the EM/NM layer; some translationprocedure is implemented

� A request map

� A free event map

• Common Data Handler

12 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• A core multithreaded Java process to manage the COPOS functionalities,composed by:

� A command manager multithreaded object to manage NMI requestsin parallel; each service request thread is instantiated at NMI requestarrival time and dies when the command data handler request mapshas been updated and the Snmp command has been sent to theNEs; the command manager object contains a static reference to thecommand data handler object.

� A trap server that contains a trap buffer manager by a thread thatpeak the received UDP packet and build the Managed Trap Object; aqueue based multi-threaded trap dispatcher that receives the ManagedTrap Object from the Trap Server and dispatch it to the Common DataHandler / Event Handler object to update NMI request or to forwardControl Plane events to NM layer.

• A set of internal traps is defined in order to check packet loss situations,SNMP agent restart, and so on; these internal events is sent from therelevant GATTO process to the COPOS, in order to perform somespecific actions (for example perform a call back on the client to notify amisalignment/restart event).

Figure 5

131/1551-1/AOM 901 084 Uen C2 | 2011-12-15


2.1.3 Attila: the Shutdown/Restart Utility

The ASTN DD Add-On needs the Practical EM North-bound (PEN) interface tobe installed beside the ServiceOn Element Manager, for the communicationbetween the two applications. When the communication is failing, could beuseful a restart of the PEN interface processes; this can be easily performed bymeans of the Attila Shutdown/Restart Utility, as described in the following steps:

1. Open an HP-UX terminal window.

2. Change the user to Attila:

su - attila

And type the relevant password, if required.

3. Choose the IPT NMS - Circuit Administration sub-menu item:

SAM Routine Tasks ->

Custom IPT NMS - Circuit Administration ->

4. Choose the PEN option:

Custom SO Element Manager

Custom SO EM ASTN-DD Add On

Custom IPT NMS - Circuit & PSB

Custom IPT NMS - Circuit vXX.Y.Z

Custom PEN

Custom SOO_Base Utilities ->

5. Type the desired option and press Enter:

########################### ## PEN SHUTDOWN/RESTART ## ###########################0 - Exit1 - PEN shutdown2 - PEN restart

Enter option (0-2):

6. Exit the Attila utility.

14 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


2.2 ASON Installation And Configuration Procedure

The operation of ASON additional module requires a separate installation andconfiguration procedure.

The ASON additional package is delivered together with the standard IPT NMS- Circuit.

In order to enable the ASON operation on IPT NMS - Circuit, the followingprocedure must be followed.

After IPT NMS - Circuit installation is completed, the new ASON module must beinstalled and some modifications need to be done to MV38.ini configuration file.

Please see Reference to get more information on IPT NMS - Circuit installation.

Proceed as follows:

• Stop the IPT NMS - Circuit processes by means of the Shutdown/Restartutility.

• Log in as nmcman.

• Edit the file MV38.ini

• Add the CPM section in MV38.ini and insert the Copos HostName:

[CPM]

CoposAddress = <the hostname of the EM ASON machine>:12456

• In section [DBOS] remove the entry:

DBOSAddress = <hostname >:12333 (if it is present)

• Both in the [CPM] and [UI] section of the MV38.ini, remove the entry:

FICOPort = <the MICO port> (if they are present)

• Add in [UI] section the following entry:

ORBAddress = <hostname of the host running the SO-EMprocesses>:12333

• Proceed with the package installation.

The depot is provided with the following name structure;

IPT-NMS-Circuit-Ason-hpit-<XY>.depot

Where <XY> is the package versioning.

To install it, log in as root and execute the command:

151/1551-1/AOM 901 084 Uen C2 | 2011-12-15


swinstall -s p` wd /` IPT-NMS-Circuit-Ason-hpit-<XY>.depotIPT-NMS-Circuit.ason

Restart the IPT NMS - Circuit processes by means of the Shutdown/Restartutility.

2.2.1 ASON Installation Check

In order to check if the ASON package is currently installed, log in as rootand then type the following command:

swlist IPT-NMS-Circuit.ason

2.2.2 ASON Removing Procedure

In order to remove the ASON package stop the IPT NMS - Circuit processesthen log in as root and type the following command:

swremove IPT-NMS-Circuit.ason

16 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

ASON Traffic And Signalling Management

3 ASON Traffic And Signalling Management

3.1 General

An ASON network is a transport network including a control plane to provideautomatic switching capability via distributed routing and signaling protocols.

The transport plane management and the control plane management composethe management of an ASTN-DD network.

The procedure and the requirements to build and manage a consistent controlplane in an ASTN network are not described in this handbook. See referencedocuments for more information about the creation and starting-up of theGMPLS control plane.

The NE management and the Network Management System compose thetransport plane management. The NE management is out of the scope ofthis document.

3.2 Control Plane Functions

The main functions of a control plane are the signaling to support the capabilityto establish teardown and maintain connections, and the routing to select themost appropriate path.

The main components of the control plane are:

• The signaling plane containing the signaling protocols

• The routing plane containing the routing protocols

Control plane also supports re-establishing of a failed connection (for examplerestoration), connection state information (for example fault and signal quality)that is detected by the Network and provided to the control plane.

The Control Plane carries (distributes) link status (for example adjacency,available capacity and failure) information to support connectionset-up/teardown and restoration.

Detailed fault management information or performance monitoring informationis transported within the transport plane and via the management plane.

The main function that a control plane has to carry out is to automaticallyset-up circuits. To do this, a database of the entire network is maintained onthe Control Plane. Once the topology and resource database are available,the most convenient routing to satisfy a circuit request is computed. Thiscomputation is often called path selection. The collection of the functions

171/1551-1/AOM 901 084 Uen C2 | 2011-12-15


needed for topology database maintenance and path selection is generallycalled routing.

The path selection is triggered by several events, typically a direct request froma customer of the transport service, a path setup request from the ManagementSystem or a fault in a path that is already providing service.

After the path selection is performed, its result must be communicated to therelevant network elements to perform the cross-connections and actually setupthe circuit and provide connectivity. This operation is called signaling.

3.3 Network Topology

A transport network is a network of flexible nodes with the capability to beconfigured with connections, and a set of transport links connecting pairof nodes. The transport links may sometimes be implemented by complexmultiplexing line systems, but can never be configured.

An ASON network is a transport network including the Control Plane to provideautomatic switching capability via distributed routing and signaling protocols.The nodes able to provide routing and signaling functions are called LabelSwitch Routers (LSR): they implement the Control Plane.

To allow LSRs to communicate, a Data Communication Network (DCN) isimplemented in the ASTN network. Routers and "layer 2 links" connecting therouters compose the DCN. The Layer 2 links can be:

• Dedicated point-to-point link

• Control channels embedded in the transport links

• Local area networks

• Public wide area networks

A layer 2 link must be bi-directional and could be configured in-band toexchange data among directly connected devices (DCC) or out-of-band usingEthernet or IP links to access an external LAN possibly including third partyrouters.

The topology of the DCN and the transport network can be asymmetric orsymmetric. As the transport network and the DCN may be different, the routingprotocols must deal with complete information about both networks. Twodistinct databases are maintained by the LSRs, one representing the DCN, theother representing the transport network. Only the DCN database is relevant forthe router function. The transport network database is used for path selection,while the DCN database provides routing tables compilation. Only the transportnetwork will need resource availability information: a best effort service isassumed in the DCN, for this topology information distribution is sufficient.

18 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


3.4 Signalling And Routing Protocols Adopted

The signaling protocols used for GMPLS in ASTN DD Network are an extensionof the signaling protocols defined for MPLS: the RSVP-TE and the CR-LDPprotocols. Either of these protocols is able to establish an LSP through aGMPLS network and reserve necessary resources to meet pre-defined servicerequirements for the data path. They provide label distribution and labelsassignment.

The routing protocols used for GMPLS are OSPF-TE and IS-IS-TE .

3.5 ServiceOn/IPT NMS ASON Solution

The ServiceOn/IPT NMS ASTN DD solution implements a fully distributedrouting function. This means that every node maintains its own database ofthe entire network: the replicated database may be partly summarized forscalability reasons. This implementation gives the network a high degree ofresiliency, as all the functions are replicated, thus not sensitive to the failureof a single node. Moreover, the network requires less human intervention,being capable of self-reconfiguration.

The main benefits provided by this implementation are:

• Fast on-the-fly restoration

• Automatic and manual topology discovery

• Compatibility with GMPLS standards

The adopted solution allows managing transport networks either via ASTN-DDControl Plane or via TMN on a per circuit basis. Procedures have beendeveloped to transfer circuit control from TMN to ASTN control plane and viceversa without service disruption.

3.5.1 Equipments Supporting the ASTN-DD Control Plane

The ASTN-DD network with distributed signaling and routing (ASTN DD) issupported by the in new generation high order multiplexers and cross connects(SDH and OTN); specifically the OMS3250, the OMS3240, OMS3255.

Refer to:

Equipment documentation for the SW releases supporting such functionality.

3.5.2 Equipments Supporting the WSON Control Plane

The WSON network with distributed signaling and routing is supported by the innew generation high order WDM multiplexers MHL3000.

191/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Refer to:

Equipment documentation for the SW releases supporting such functionality.

3.5.3 Signalling and Routing Protocols

The IETF CCAMP standard protocols have been implemented on the NEs: thementioned LMP for link maintenance, GMPLS-OSPF for routing of the datanetwork and GMPLS-RSVP for signaling. These comply with the general ITU-Tframework for ASON as described in Recommendations G.8080 and G.807(see references). A TCP/IP based control communication network supportsthese protocols. Marconi uses a dual stack DCN (IP and CLNP) to maintaincompatibility and integration of TMN with legacy equipment. This conforms toITU-T recommendation G.7712, with the mixed DCN option. A single routingprotocol is used to distribute routing information for both OSI and IP protocols.The chosen routing protocol is Integrated IS-IS according to RFC1195 withenhancements as suggested by ITU-T G.7712.

3.5.3.1 Interoperability Between ASON And TMN Networks

As mentioned above, both ASON control and TMN management may coexist inthe same network, for differentiated service handling. Transport networks canbe operated either via ASON Control Plane or via TMN on a per circuit basis.Procedures have been developed to transfer circuit control from TMN to ASTNcontrol plane and vice versa without service disruption.

A customary deployment of the transport network can be a large number ofaccess ADM rings connected to a backbone mesh of cross connect equipment.Typically, the backbone is upgraded or expanded first. Moreover, the meshtopology is that where an ASON control plane exhibits most of its benefits.

For these reasons, frequently an ASON backbone shall have to interoperatewith traditional SDH ring protection schemes (SNCP or MS-SPRing). ASTN-DDwill implement this kind of networking to provide end-to-end circuits with thedegree of protection allowed by the parts of the network they traverse.

ASTN control plane is designed to keep into account the underlying protectionschemes, to allow efficient integration with the established standards. Forexample, a circuit that is set up via ASTN control may cross a shared protectionSDH ring (MS-SPRing). The MS-SPRing protection requires information updateat each new circuit, and this is integrated in the ASTN Control Plane.

Beside, a full management of Tandem SNCP (single ring and double ringprotection) is provided from IPT NMS - Circuit in order to have the inter-actionbetween legacy and ASTN DD network driven from IPT NMS - Circuit.

20 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


3.5.4 SNMP MIBs Implemented On The NEs

Most of available GMPLS MIBs, integrated with proprietary objects to completethe ASTN-DD Control Plane management has been implemented on NEs.These make possible the use of SNMP to configure ASTN functions (forexample, protocol parameter setup), as well as to get the useful databaseinformation, such as automatically discovered topology or circuit routing.

3.5.5 Circuit Set-up

A circuit is implemented with a worker LSP and a set of protection/restorationLSPs (if any). Each NE has a list of the circuits "terminated" by itself(Terminated Circuit - TC ), and each TC keeps a list of the LSPs involved in itsimplementation. The term "terminated" means circuits/LSPs where the NE isan endpoint, in both cases: the NE created (originator) the circuit/LSP and theNE "received" (receiver) the circuit/LSP. Keeping track of a circuit and relatedLSPs at both endpoints allows both NEs to perform actions on the circuit or onone of the constituent LSPs (for example teardown, modification, rerouting,management of protection/restoration, and so on).

3.5.5.1 On The Fly Restoration Protection

A circuit restoration in which the alternative route is computed after the faultoccurrence is called on-the-fly restoration. Having knowledge of the faultlocation is a noticeable benefit, in that it allows the optimal computation of thealternate route with minimal resource consumption.

In the ASTN DD, the on-the-fly restoration is performed directly in the networkby the originating node of the circuit: this reduces the communication delays.Alarms are detected and processed directly in the network, avoiding networkmanagement integration. Finally, each node restores only the circuits itoriginates, allowing parallel computation of alternate routes on several nodes.

As a result, the on-the-fly restoration gives restoration times of seconds onthe average and even below one second, depending on network complexity,configuration and load.

211/1551-1/AOM 901 084 Uen C2 | 2011-12-15


22 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Usage Of The IPT NMS - Circuit Graphical Interface

4 Usage Of The IPT NMS - Circuit GraphicalInterface

4.1 Introduction to the Usage of GUI

The operational requirements necessary to correctly operate with ASTN-DDadvantage module are:

• Control Plane correctly configured and running on all the NEs, The correctconfiguration of the Control Plane is performed through the ON Plannerand Configurator applications

• ServiceOn Element Manager running

• ServiceOn EM ASTN-DD add on correctly running (for ASTN DD)

• PEN installed and correctly running

• IPT NMS - Circuit running

See Also:

ASTN DD System Info and Installation

This section is not describing all the features available in IPT NMS - Circuitbut only those one whose operation differs from the standard one, due to theASTN Advantage Module addition.

A set of additional menus and graphical widget are added to the standard IPTNMS - Circuit GUI after ASTN-DD Advantage module is enabled.

The most important GUI differences are:

• Control Plane Query Tools: four specific Network Query Tools, available tosort and manage the ASTN-DD control plane components

• ASTN-DD topology discovery command

• Add trail tool: upgraded with additional commands necessary to managethe ATSN-DD circuit creation (ERO management, Traffic Engineering)

• Restore Phase: the management of Restore steps on the NE, necessaryto drive the procedure to restore the NE database without traffic affectionon ASTN-DD network

• Link Details: the band occupation of ASTN-DD traffic is saved into IPTNMS - Circuit database and can be displayed using the standard linkinquiry commands

231/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Additional information about Link Cluster the link belongs to is given.

• Circuit Linear Display and Circuit Details: the specific information of theASTN DD resource is added in the standard window (for example lockoutstate)

See Also:

How to Use This Handbook

4.1.1 ASTN-DD Main Map Buttons

Four extra Buttons are added to the Map when ASTN-DD Advantage Module isenabled.

Figure 6

They are used for running the additional Network Query Tools specially usedfor the Control Plane resources.

• Label Switched Router Query Tool

• Link Cluster Query Tool

• Link Component Query Tool

• Control Channel Query Tool

See Also:


Each of them provides a list that makes available all the possible commandsthat can be executed on the specific resource type, according to its currentstate, its selection and the current layer.

After an accurate filtering, the specific resources are arranged in a list and anappropriate pop-up menu can be used to select the command to run.

The result of a Network Query tool can be arranged:

• In the Table Area, at the bottom of the Main Map and displayed by meansof an appropriate Toggle button from the Map Menu Bar

• At the bottom of each Network Query tool

24 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This choice can be performed by means of a specific command in the ViewMenu.

Every Network Query Tool allows printing and exporting of the resource list.

See Also:

Introduction to the Usage of GUI

4.1.2 ASON Table Area Management

Four extra buttons are added to the bottom of the Main Map when theAdvantage Module is enabled.

Figure 7

They are used for switching through the additional Network Query Tools.

Each of them switches the table area to the type of result whose operation isdriven by the proper Network Query tool.

See Also:

Introduction to the Usage of GUI

4.2 Installing The Nodes On IPT NMS - Circuit

The ASTN-DD NEs must be installed on IPT NMS - Circuit map by meansof the standard Install NE command.

After the installation, every node is displayed on IPT NMS - Circuit Map bymeans of a specific Icon that identifies the ASON Control Plane operation.

Figure 8

251/1551-1/AOM 901 084 Uen C2 | 2011-12-15


A small triangle appears in the top-right corner of the NE icon with the followingmeaning:

Green ASON Protocol configured and running

Red ASON Protocol Configured but not running

4.3 Creating The Links

The physical internodal links between two ASON nodes is created on IPT NMS- Circuit Map through the standard Add-Link command. While creating theInternodal links, the routing parameters provided (Color, Weight, SRLG) areonly used for the legacy routing entirely managed by S internal process.

The ASTN-DD routing engine provided by the Control Plane could use differentvalues of such parameters.

4.4 ASTN-DD: Topology Discovery

PATH: Configuration-ASTN DD Discovery, Node Query tool/NE Pop UpMenu-Discovery-ASTN DD

This command aligns the Database configuration with the ASTN Control Planeand current traffic setting up.

All the circuits that are present at the Control Plane are refreshed withinthe Database, according to the usual information (name, creation data,routing characteristics). Discovery retrieves the circuits that were previouslydisassociated or lost from the Database.

Before running the command make sure that the Control Plane is correctlyconfigured and running on NEs and the physical SDH/DWDM topology iscompletely built up.

This command can run on the whole network as well as on the basis of a singleNE.

After the discovery is over the discovered resources are listed at the bottom ofthe window in tabs, as follows.

• Label Switched Routers: I-NNI Nodes and UNI Clients (that are shownwith label "Unmanaged" )

• Link Clusters

• Link Components

• Control Channels

• Circuits

26 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The message area contains an "update completed" message in case allthe operations are successful; in case something goes wrong, the messagearea can one of the following message:

• Unreachable node error: if a node is unreachable

• Get operations node error: if a node returns generic snmp errors inretrieving topology information this "read error" is notified.

See Also:

ASON Label Switched Router Query Tool, ASON Link Cluster Query Tool,ASON Link Component Query Tool, ASTN Control Channel Query Tool

4.4.1 ASTN DD global discovery

NOTICE The first time this command runs, the discovery must be performed onthe whole GMPLS network.

To Discover The Whole ASTN-DD Topology:

1. Deselect all the Nodes from the Map.

2. Select the command from the Configuration menu.

271/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 9

3. Use Routeing Area Id to enter the IP address of the OSPF area. Thefirst time the command is run this field must be empty. The value insertedthe first time is afterwards prompted as default. If this value changes allthe information stored on IPT NMS - Circuit is replaced with the new onebelonging to the new Routeing Area.

4. Use Starting Node IP Address to specify the ASTN-DD node the operationhas to start from. The first time the command is run this field must be empty.

After the first time, the Starting Node address can be selected among theone discovered the first time.

5. Press the magnifier button close to the text field to access the list of theaddresses.

28 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 10

6. Select the IP address of the NE to start from.

7. Press Apply.

8. Check that the button Whole ASTN DD Network is selected (it is thedefault when the command is run from the menu bar).

9. Select Trail and Topology Information check-button to have the discoverycommand running on both circuits and control plane configuration. Thisselection is mandatory the first time the command runs.

10. Select Trail Information Only check-button to have discovery commandrunning on circuits only. This selection can be done starting from thesecond time the commands runs.

11. Press Apply.

A confirmation window appears.

291/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 11

12. Press Yes or Yes, do not show again to stop displaying the confirmationnext times.

4.4.2 ASTN DD Single Node Topology Discovery

This type of discovery can be performed after a whole discovery has beenalready executed.

To Discover Topology From One Network Element:

1. Right-click on the Map the NE to check.

2. Select the command from the Pop-up menu.

Alternatively, the command can be run from the Node Query Tool.

3. The name of the NE selected is reported in the ASTN DD Discoverywindow (Node Name). Its IP Address is reported as default in the StartingNode IP Address field.

4. Check that the button Starting Node Only is selected (it is the defaultwhen the command runs from the single node).

5. Select Trail and Topology Information check-button to have the discoverycommand running on both circuits and control plane configuration. In caseof single node the topology information is taken from the selected node andfrom its adjacencies.

30 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Caution!

In case of Point to point Control Channels not directly connected to thenode, this type of discovery could not be able to get them.

Only the Control Channels that are in state currently UP can be successfullydiscovered. In case a control channel cannot be discovered.

6. Select Trail Information Only check-button to have the discoverycommand running on circuits only.

7. Press Apply.

Only the Control Channels that are in state currently UP can be successfullydiscovered. In case a control channel cannot be discovered it is removedfrom the topology saved in the DB.

4.5 ASON: Topology discovery

PATH:(Configuration-Discovery-ASON Discovery)

This command aligns the Database configuration with the ASON Control Planeand current traffic setting up.

All the circuits that are present at the Control Plane are refreshed withindatabase, according to the usual information (name, creation data, routingcharacteristics).

Discovery retrieves the circuits that were previously disassociated or lost fromdatabase.

Before running the command, make sure that the Control Plane is correctlyconfigured and running on NEs and the physical SDH/DWDM topology iscompletely built up.

This command can run on the whole network as well as on the basis of a singleNE. After the discovery is over the discovered resources are listed at the bottomof the window in tabs, as follows:

• Label Switched Routers: I-NNI Nodes and UNI Clients (that are shownwith label Unmanaged)

• Link Clusters

• Link Components


• Circuits

311/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Adjacency

The message area contains an update completed message in case all theoperations are successful; in case something goes wrong, the message areacan one of the following message:

• Unreachable node error: if a node is unreachable

• Get operations node error: if a node returns generic snmp errors inretrieving topology information this read error is notified.

See Also:

ASTN : Topology Discovery

4.5.1 ASON Global Discovery


Note: The ASON topology can be successfully discovered if the NEs areconnected by Link Cluster in status ‘‘UP’’.

To discover the whole ASON topology:

• Deselect all the Nodes from the Map.

• Select the command from the Configuration menu.

Figure 12

32 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Use Routeing Area Idto enter the IP address of the OSPF area. The firsttime the command is run this field must be empty. The value inserted thefirst time is afterwards prompted as default. If this value changes all theinformation stored on IPT NMS - Circuit is replaced with the new onebelonging to the new Routing Area.

• Use Starting Node IP Addressto specify the ASON node the operationhas to start from. The first time the command is run this field must beempty. After the first time, the Starting Node address can be selectedamong the one discovered the first time.

• Press the magnifier button close to the text field to access the list of theaddresses.

Figure 13

• Select the IP address of the NE to start from.

Note: After completing the Whole ASON Network NE Trap Notifications mustbe enabled and Control Plane status must be realigned. See note on ControlPlane Configuration Wizard paragraph.

• Press Apply.

• Check that the button Whole ASON Networkis selected (it is the defaultwhen the command is run from the menu bar).

• Select Trail and Topology Informationcheck-button to have the discoverycommand running on both circuits and control plane configuration. Thisselection is mandatory the first time the command runs.

• Select Trail Information Onlycheck-button to have discovery commandrunning on circuits only. This selection can be done starting from thesecond time the commands runs.

331/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Press Apply.


• Press Yes or Yes, do not show againto stop displaying the confirmationnext times.

See Also:

ASON : Topology discovery

4.5.2 ASTN DD Single Node Topology Discovery


This type of discovery can be performed after a whole discovery has beenalready executed.

To discover Topology from one Network Element:

• Right-click on Map the NE to check.

• Select the command from the Pop-up menu.

Alternatively, the command can be run from the Node Query Tool.

• The name of the NE selected is reported in the ASON Discovery window(Node Name). Its IP Address is reported as default in the Starting NodeIP Addressfield.

• Check that the button Starting Node Onlyis selected (it is the default whenthe command runs from the single node).

• Select Trail and Topology Informationcheck-button to have the discoverycommand running on both circuits and control plane configuration. In caseof single node the topology information is taken from the selected node andfrom its adjacencies.

Only the Control Channels that are in state currently UP can be successfullydiscovered. In case a control channel cannot be discovered

• Select Trail Information Onlycheck-button to have the discovery commandrunning on circuits only.

• Press Apply.

Only the Control Channels that are in state currently UP can be successfullydiscovered. In case a control channel cannot be discovered it is removed fromthe topology saved in the DB.

See Also:

34 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


ASON : Topology discovery

4.6 ASON Label Switched Router Query Tool

PATH: Configuration-Label Switched Router

The Label Switched Router Query tool is a browser for the I-NNI Nodes and UNIClients (that are shown with label "Unmanaged" ). Each of these items is listedin the Query tool in order to be available for further selection and management.

All the commands that could be run on this type of resources are availablefrom the result window.

Before running any command a filtering phase on the database is necessary.

After the filtering phase, items are shown together with their related parameters:

• Name

• Type

• Short Name

• Suffix

• Router Id.

• Routeing Area Id.

• Restore Phase

See Also:


Note: The usage of this Query tool is fully compliant with the standard NMSones.

351/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 14

After the Search is complete, right click in the Result on the item on which acommand must be run. A pop up menu appears.

Figure 15

From this menu the command to run on the item can be selected.

See Also:

36 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


ASON Link Cluster Query Tool, ASON Link Component Query Tool, ASTNControl Channel Query Tool, ASTN-DD: Topology Discovery

4.6.1 ASTN Label Switched Router: Details

PATH: ASON Label Switched Router Query Tool-Details

Details on the selected LSR are shown in a separate window.

Figure 16

1. Press Print to spool the output to the system printer.

2. Press Export to save the output.

3. Press Close to quit the window.

4.6.2 ASTN Label Switched Router: Protocols State

PATH: ASON Label Switched Router Query Tool-Protocol State

Details on the LSR protocol state is shown in a separate window.

371/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 17

38 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15





4.6.3 ASTN Label Switched Router: Modify

PATH: ASON Label Switched Router Query Tool-Modify

This command modifies the identity of the selected LSR.

Figure 18

1. Type in the Long Name the extended identifier of the LSR.

2. Type in the Short Name the acronym of the LSR.

3. Type in the Suffix the numeric identifier of the LSR.

4. Press Apply.

4.7 ASON Link Cluster Query Tool

PATH: Configuration-Link Cluster

The Link Cluster Query tool is a browser for the links cluster currently configuredin database and on the ASTN-DD Control Plane.

This Query Tool is also used for the configuration of the Explicit Routing Objectduring Circuit provisioning. See also:

ASTN-DD ERO Management

391/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Each of these items is listed in the Query tool in order to be available for furtherselection and management.




• Operational State

• Admin State

• Edge Type


40 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 19


411/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 20


See Also:

ASON Link Component Query Tool, ASON Label Switched Router QueryTool, ASTN Control Channel Query Tool

4.7.1 Link Cluster Commands: Details

Details on the selected Link Cluster are shown in a separate window.

42 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 21


431/1551-1/AOM 901 084 Uen C2 | 2011-12-15




4.7.2 Link Cluster Commands: Setting Locking State

PATH: ASON Link Cluster Query Tool-Locking State-Lock

According to this setting the link cluster is included excluded (Locked) fromrouting calculation, performed by the control Plane.

After the link cluster is locked a procedure to empty it for network maintenancescope can be applied. See:

Commands After Setting the Locking State

To Lock A Link Cluster:

Figure 22

44 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


1. Press Apply.


Figure 23

2. Press Yes to confirm.

4.7.2.1 Commands After Setting the Locking State

For each circuit screened on the Circuit Query Tool, depending on theprotection type of the circuit and if the original path can be lost, the operatorcan perform a different set of commands.

In case the original path must be kept, the class of service of the circuit can bemodified and the circuit could achieve resilience major than the original one.

After locking the link cluster, the following procedures can be performed:

Unprotected Circuit: Original Path Can Be Lost

1. Reroute command from the menu.

2. The procedure can be applied even if alarms are present or not.

Unprotected Circuit: Original Path Must Be Kept

1. Modify Circuit: the circuit shall be moved to Revertive On The Fly.

2. Modify Protection: a forced to protection command shall be performed.

3. The procedure can be applied even if alarms are present or not. If an alarmis affecting the circuit, after the Modify Circuit command an LSP shall becreated and the traffic moved on it.

451/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Non-Revertive OTF Circuit: Original Path Can Be Lost


Non-Revertive OTF Circuit: Original Path Must Be Kept

1. Modify Circuit: the circuit shall be moved to Revertive On The Fly.


Revertive OTF Circuit: Original Path Can Be Lost

1. Modify Circuit: the circuit shall be moved to Non-Revertive OTF.


Revertive OTF Circuit: Original Path Must Be Kept


Strong SNCP: Link In Locked State Is Passing Through The Worker Leg


Strong SNCP: Link In Locked State Is Passing Through The Protection Leg

1. Reroute command from the menu [Open Issue] If the link is alreadyblocked, there is no raison to specify the link cluster to avoid.

SNCP: Link In Locked State Is Passing Through The Worker Leg

1. Modify Protection: the circuit must be moved a Strong SNCP to maintainthe original resilience; a forced to protection command shall be performed.

SNCP: Link In Locked State Is Passing Through The Protection Leg

1. Modify Protection: the circuit must be moved a Strong SNCP to maintainthe original resilience.

2. The procedure requiring a Re-route command or a Modify Protection Typecommands must be issued only when the circuit is in an idle state as usual:

• Unprotected: the circuit is always in idle.

• OTF: the circuit must be in OneLsp state, that is, no restorationprocedure is on-going.

• Strong-SNCP: the SNCP must be in NoRequest state, that is, nofailures are affecting the circuit.

4.7.3 Link Cluster Commands: Resetting Locking State

PATH: ASON Link Cluster Query Tool-Locking State-Unlock

46 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


According to this setting the link cluster is included (Unlocked) from routingcalculation, performed by the ASON Control Plane.

After the link cluster is unlocked a procedure to restore the original trafficrouting can be applied. See:

Commands After Re-setting the Locking State

To Unlock A Link Cluster:

Figure 24

1. Press Apply.


471/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 25


4.7.3.1 Commands After Re-setting The Locking State

For each circuit screened on the Circuit Query Tool, depending on the protectiontype of the circuit, the operator shall perform a different set of commands.

After un-locking the link, the following procedures can be performed:

Unprotected Circuit Moved To Revertive OTF:

1. Modify Protection: a clear command shall be performed.

2. Modify Circuit: if no alarms are affecting the circuit, it can be moved toUnprotected circuit.

Non-Revertive OTF Moved To Revertive OTF:


2. Modify Circuit: it can be moved to Non-Revertive OTF. If an alarm isaffecting it, the circuit will be restored and a new LSP will be created andthe traffic moved to it.

Revertive OTF moved to Non-Revertive OTF

1. Modify Circuit: it can be moved to Revertive OTF.

2. A Reroute command can be done to optimize the network or retry to obtainthe original path: it is an optional command.

Revertive OTF


SNCP Moved To Strong SNCP: Link In Locked State Was Passing ThroughThe Worker Leg

1. Modify Circuit: it can be moved to SNCP.

48 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15



SNCP Moved To Strong SNCP: Link In Locked State Was Passing ThroughThe Protection Leg

1. A Reroute command can be done to optimize the network: it is an optionalcommand.

2. Modify Circuit: it can be moved to SNCP.

Strong SNCP: Link In Locked State Was Passing Through The Worker Leg


Strong SNCP: Link In Locked State Was Passing Through The ProtectionLeg

1. A Reroute command can be done to optimize the network: it is an optionalcommand.

4.7.4 Link Cluster Commands: Associated Circuits

PATH: ASON Link Cluster Query Tool- Associated Circuits

This command performs a correlation between the selected Link Cluster and thecircuit that runs through it. The correlation is done by means of the Circuit Querytool window, which is invoked and pre-set to display the circuit in its result area.

See Also:

ASON Link Cluster Query Tool

4.7.5 Link Cluster Commands: Associated Control Channel

PATH: ASON Link Cluster Query Tool- Associated Control Channel

This command performs a correlation between the selected Link Cluster andthe Control Channels currently associated to it. The correlation is done bymeans of the Control Channel Query tool window, which is invoked and pre-setto display the Control Channels in its result area.

See Also:

ASON Link Cluster Query Tool, ASTN Control Channel Query Tool

4.7.6 Link Cluster Commands: Associated Link Components

PATH: ASON Link Cluster Query Tool- Associated Link Components

This command performs a correlation between the selected Link Cluster andthe link components associated to it. The correlation is done by means of the

491/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Link Component Query tool window, which is invoked and pre-set to display theLink Components in its result area.

See Also:

ASON Link Cluster Query Tool, ASON Link Component Query Tool

4.7.7 Link Cluster Commands: Modify

PATH: ASON Link Cluster Query Tool-Modify

This command modifies the identity of the selected Link Cluster.

To modify A Link Cluster:

Figure 26

1. Type the new link cluster Name.

2. Press Apply.

4.8 ASON Link Component Query Tool

PATH: Configuration-Link Component

The Link Component Query tool is a browser for the internodal links physicalcomponents currently configured in database and in the ASON Control Plane.




50 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15



• Name


• Correlated

• Link Cluster

• Forced Up

See Also:



511/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 27


52 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 28


See Also:

ASON Label Switched Router Query Tool, ASON Link Cluster Query Tool,ASTN Control Channel Query Tool

4.8.1 ASTN Link Component Commands: Details

PATH: ASTN Link Component-Details

Details on the selected Link Component are shown in a separate window.

531/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 29




4.8.2 ASTN Link Component Commands: Modify

PATH: ASTN Link Component-Modify

This command modifies the identity of the selected Link Component.

54 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


To modify A Link Component:

Figure 30

1. Type the new link component Name.

2. Press Apply.

4.9 ASTN Control Channel Query Tool

PATH: Configuration-Control Channel

The Control Channel Query tool is a browser for the links currently configuredin database and on the ASON Control Plane.





• Name


• Type

• Forced Up

See Also:


551/1551-1/AOM 901 084 Uen C2 | 2011-12-15



Figure 31


56 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 32


See Also:

ASON Label Switched Router Query Tool, ASON Link Cluster Query Tool,ASON Link Component Query Tool

4.9.1 Control Channel Commands: Details

PATH: ASTN Control Channel Query Tool-Details

Details on the selected Control Channel are shown in a separate window.

571/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 33




See Also:

ASTN Control Channel Query Tool

4.9.2 Control Channel Commands: Associated Link Cluster

PATH: ASTN Control Channel Query Tool-Associated Link Cluster

This command performs a correlation between the selected Control Channeland the link cluster currently associated to it. The correlation is done by meansof the Link Cluster Query tool window, which is invoked and pre-set to displaythe Link Cluster in its result area.

See Also:

58 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


ASTN Control Channel Query Tool

4.9.3 Control Channel Commands: Modify

PATH: ASTN Control Channel Query Tool-Modify

This command modifies the identity of the selected Control Channel.

To Modify A Control Channel:

Figure 34

1. Type the new name.

2. Press Apply.

4.10 Creating The ASTN-DD Circuits

The ASTN-DD circuits are created and managed by the Control Plane uponrequest of GUI. After the creation the Routing and protection information aresaved into database.

After the installation of the nodes and the creation of the Internodal linksbetween them the User can proceed in creating the traffic resource.

The basic operation is equivalent to the creation of a legacy circuit, the end toend approach can be chosen as well as the node-by-node one.

The creation of an ASTN-DD circuits is performed by the Control Plane at theconfirmation of the request made by User.

See Also:

Modify ASTN-DD Circuits, Re-routing an ASTN-DD Circuit

591/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.10.1 Creating the ASTN-DD Circuit Between Two Endpoints

This is the usual procedure to be followed: the control plane calculates the bestrouting path between the termination points specified by User.

The activation of the circuit can be managed in the same way of a legacy circuit;by default an ASTN-DD circuit is routed and activated at the same stage.Anyway the Add Circuit Wizard can drive a creation of the circuit that does notinvolve the Control Plane until the circuit remains in Reserved State.

To Create An ASTN-DD Circuit Between Two Specific Endpoints:

1. Move to HO layer in Map.

2. Select the first node of the circuit.

3. Select the last node of the circuit.

4. Right click in the open space

Figure 35

5. From the Pop-up menu, select the Add-Bidirectional Circuit- ASTN-DDcommand.

60 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command is made available by the ASTN Advantage Module. Thestandard Add-Circuit wizard is run.

Refer to:

Add Trail Wizard description in the IPT NMS - Circuit product handbook.

6. Proceed as for a normal circuit. The management type is set to ASTN-DD.

Figure 36

In the Initial Parameters step select the type of protection requested:

No Protection At creation time, only the working path is created. Thecircuit will be unprotected. This operational conditioncan then be modified by means of the Modify CircuitCommand.

SNCP At creation time, the Control Plane provides both workerand protection sides. In case of failure on the workingside the traffic is routed to the protection side.

On The Fly At creation time, the Control Plane provides the workingpath only. In case of failure of the main route, the controlplane calculates an alternative path and activates it.This protection is revertive; the original working path issaved and restored when the failure goes Off.

Non Revertive On The FlyAt creation time, the Control Plane provides the workingpath only. In case of failure of the main route, the controlplane calculates an alternative path and activates it.The new route definitely replaces the existing one.

611/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Strong SNCP At creation time, the Control Plane provides bothworking and protection sides. In case of failure on theprotection side the control plane provides a new route.

According to the above selection, some parts of the Add Trail tool, FurtherDetails, Routing Constraints and Routing pages change to allow input ofparameters related to the selected protection type. In case of No Protectionselection the Further Details page is skipped.

7. Move to Further Details page.

According to the protection type chosen, this page of the Add Trail Toolprompts the user to input different parameters.

SNCP Only WTR Time can be set.

On-The-FlyWTR

Time and Restoration Priority can be set.

Non RevertiveOn-The-Fly

Only Restoration Priority can be set.

Strong SNCP WTR Time and Restoration Priority can be set.

8. Set the Wait to Restore time, using the proper slider. Range is from 1 to12 minutes.

Figure 37

9. Set the Restoration Priority using the proper slider. The restoration priorityis the time the system wait before starting to restore the circuit, in case offailure. Eight (0 to 7) different levels in steps of 100ms, can be selected.

Figure 38

62 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


10. Move to the Routing Constraints page. In this page some of the widgetsare available or not depending on the type of Protection chosen.

11. Specify the Color for the routing. When Selected the colors for worker andfor the protection get the same value.

12. Use Diversity check buttons (in the Protection Tab) to change level ofdifference that the Control Plane will adopt when calculating a protectionroute for the selected circuit. This is not available for Not Protected circuit.

Figure 39

Node The protection side will be calculated through NEsdifferent from worker.

Link The protection side will be calculated through Linkdifferent from worker.

SRLG The protection side will be calculated through SharedRisk Link Group different from worker.

13. Use Routing Optimization Criteria to set the type of routing calculationon the circuit being Created.

Figure 40

Use Traffic EngineeringThe cost of the routing is obtained by the sum of thecost of the link it crosses. A fixed weight associated tothe link is combined with a dynamic weight that dependson the link occupancy. The higher is the link occupancythe higher is the total cost.

631/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Use Admin Weight(for trial only) The cheapest path is preferred, despitethe occupancy.

Minimize Hops (for trial only) The shortest path is preferred, despitethe cost.

14. Move to the Creation Actions page, use the Auto Activate check button todefine whether the circuit should be created and activated or defined only.

If selected, this command makes the Control plane to calculate and activatedirectly the selected circuit. Otherwise the circuit will be defined as anend-to-end resource in database. The actual calculation and activation ofthe routing path will take place at the Activation command.

15. Use the Set in Service check button to define whether the alarms comingfrom the circuit will be displayed in the Real Time Monitoring Window or not.

16. Define the Cranck Back for setting the activation attempts in case of failure(range from 1 to 20). In case the Crank Back is not enabled, the systemtries to activate the circit the first time only.

17. Complete the circuit definition, by selecting the Termination point andassigning a Name.

18. Select the Explicit Routing Management by pressing Configuration buttonin the ERO Management box.

Figure 41

Proceed as detailed in ASTN-DD ERO Management description:


19. Press Create.

4.10.2 Creating The ASTN-DD Circuit Node-By-Node

ASTN-DD Advantage Module allows the selection of the Explicit Routing of atrial. This type of circuit creation is based on the manual selection of all thenodes that are crossed by the resource. This selection must be performed onMAP before running the circuit creation command.

From the point of view of the Network Manager one circuit created in this wayremains a legacy circuit until activated. After activation the explicit routingis moved to the control plane and removed from Database, where only theendpoints and the routing characteristics are kept.

64 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Note: The explicit routing specified by a User is accepted by the ControlPlane if only the links included are not alarmed.

To Create An ASTN-DD Circuit Node-By-Node:

1. Move to HO layer.

2. Select on by one all the nodes to be crossed by the circuit. The first and thelast selection will be adopted as endpoints of the circuit.

3. Right click in the open space.

Figure 42

4. Select Add-Bidirectional Circuit-VC-4 command. The standardAdd-Circuit window is open showing the selected routing path in the CircuitConstraints.

Refer to:

Add Circuit Window description in the IPT NMS - Circuit User Guide.

5. Proceed as for a legacy VC-4 circuit. Specify the termination points andthe link connections used in the internodal links.

651/1551-1/AOM 901 084 Uen C2 | 2011-12-15


6. The protection type circuit can be chosen via the usual selections availablein the Add-Circuit window. The ASTN-DD circuit can support only some ofthe legacy protection types, so not all the possible choices are allowed afterconfirmation. Here in the following the protection configuration that can becarried out together with an Explicit routed ASTN-DD circuit.

No protection Only the working path is created after confirmation.To get this result the Protection check button must beleft unselected. A further protection can be added bymeans of the Modify Circuit command.

Strong SNCP This is the default for the SNCP, if created throughthe explicit routing selection. To get this result theProtection check button must be selected. Theprotection path must be fully defined as well as theworking path; Use the Other Side button to access theprotection page of the Add-Circuit window.

Revertive Onthe Fly

To get the Revertive on the fly restoration protection,check the Restoration button and the On The Fly type.

The Not Revertive On The Fly restoration type and the SNCP standardprotection can be obtained later by means of the Modify Circuitcommand.

Caution!

The explicit routing can be specified manually or automatically, usingfacility: except the termination point there is no checking between theControl Plane and Database about the resource availability.

7. Specify one name for the circuit and press Apply.

4.11 ASTN-DD ERO Management

The Explicit Routing Object (ERO) management can be applied on all the circuittypes (protected and not protected) during the last creation step.

In order to improve the degree of network control when configuring an ASTNDD circuit, the circuit creation wizard is provided with the capability forinclusion/exclusion of resource at different granularity.

The operator can specify to S to include/exclude the following types ofresources:

• Link Clusters (for both inclusion and exclusion)

• Link Components (for inclusion only)

66 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Label (for inclusion only)

FULL ERO Management information is not stored neither on S database noton the TNE MIBs, therefore the circuit must be created and activated in asingle operation (the Add Trail Tool has been modified to implements thisrequirement).

Note: Auto Activate button must be checked on the Add trail Wizard to allowthe ERO management.

After pressing the Configuration push button on the Add Trail Wizard, the LinkCluster Selection Window is shown.

671/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 43

To select On Or More Link Clusters:

1. Open the Link Cluster Query Tool and execute the searching of the linkcluster., See:

ASON Link Cluster Query Tool

2. Select in the Query Tool Result Table the Link Cluster to manage.

68 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


3. Move on the Link Cluster Selection Window and press Add Link Clusterfrom Query Tool button. The Link Cluster selected on the Query Tool isreported into the ERO management window.

Note: Only one link cluster can be selected at a time.

4. Repeat the selection on the Query Tool and press Add Link Cluster fromQuery Tool button to add other link clusters to the ERO Managementwindow.

To Configure The ERO Constraint Object On The Link Cluster:

1. Right click on the link cluster to see the result entry pop-up menu.

Figure 44

This pop-up contains the following available commands:

• Details: it invokes the same action invoked by the Link Cluster Query toolwhen requesting the details fro a link cluster. See:

Link Cluster Commands: Details

• Remove: it removes the selected Link Cluster from the result area.

• Configure: opens the Link Inclusion/Exclusion configuration windowthat is responsible for the ERO constraint object configuration.

2. Select Configuration. The Link Inclusion/Exclusion configurationappears. Provide the necessary configuration as detailed in:

691/1551-1/AOM 901 084 Uen C2 | 2011-12-15


ERO Management: Object Inclusion and Exclusion Configuration

3. Press OK. The ERO configuration is confirmed for the circuit currentlybeing created. Proceed with the Circuit creation on the Add Trail Tool.

4.11.1 ERO Management: Object Inclusion And Exclusion Configuration

After selecting configure the Link Inclusion/Exclusion configuration appears.

70 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 45

1. Use Include or Exclude to set main action on the link Cluster. This level isthe Link Cluster granularity. For the operation of the algorithm after definingInclusion and Exclusion, see:

ERO Management: Operation of the Routing Algorithm with Inclusionor Exclusion of Resources

711/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The operator selects a link cluster interface; the link components and thelabels on which the circuit will be routed are totally calculated from thecontrol plane. This granularity is available for both resource inclusion andresource exclusion.

2. Use Interface Selection check buttons to choose the correct interface tobe used for the selected resource.

3. Use Bound To check buttons to specify for which side of the circuit theselected resource has to be used (worker or protection). The availabilityof the buttons depends on the type of protection chosen while creatingthe circuit.

4. Use the down arrow button to select and the up arrow button to de-select.

5. Use Optional Link Component selection box to manage the linkcomponent granularity.

The operator can specify the shelf, unit and port for the outgoing linkcomponent to be used. Both the link component and link cluster interfacesmust be specified. This granularity is available for resource inclusion only.

6. Use the down arrow button to select and the up arrow button to de-select.

7. Use Optional Label Selection box to manage the Label Granularity.

The operator can specify the AU4 to be used for a particular outgoing linkcomponent. All the involved resources must be specified, that means thelink cluster interface, the link component interface and the label itself. Thisgranularity is available for resource inclusion only.

8. The button Reset can be used to clear the inclusion or inclusion settingperformed.

9. Press OK. The Object Inclusion and Exclusion setting is confirmed. Afterthis step proceed as indicated on the main ERO Management window.

See Also:


4.11.1.1 ERO Management: Operation Of The Routing Algorithm With InclusionOr Exclusion Of Resources

After the configuration of inclusion or Exclusion is completed, the routingcomputation is instructed to use or not certain network resources. The usage ofthis configuration is summarized below.

72 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Caution!

The automatic GMPLS routing algorithm helps finding a path using both itsown fixed criteria and the customized ERO constraints. If User constraintsare not in compliance with the algorithm rules, this may prevent the correctaccomplishment of the calculation. In this case, please select the path manually.

Inclusion Of Resources

In case of inclusion of resources the HOP can be LK, LC or Label. The usage ishierarchical. For each HOP the configuration schemes can be:

• Only LK: Link Cluster granularity

• LK+LC: Link Component Granularity

• LK+LC+Label: Label Granularity.

In case of protected circuits it is not possible to specify the protection LSP onlywhile only the worker one can be selected.

The HOPs to be included could determine a full specified path from Ingress toEgress NEs or describing a path with some "holes" between the different LSP.

These possible holes are managed by the algorithm as follows:

• The Ingress NE manages the "hole" if it starts from the Ingress NE itself.

• The NE immediately before the one connected to the hole manages it.

• The NE directly connected to the hole manages it, if the NE immediatelybefore fails.

The algorithm tries to find the routing with minimum cost between the startingand the ending points of the "hole" . The constraints that are applied whilecompleting this process are:

• Resources to be excluded, in accordance with Exclusion configuration.

• The ERO part specified with Inclusion configuration and not yet currentlycrossed.

• The part of the routing the algorithm is already gone through.

In case of protection, the LSP tries to avoid the worker path resourcesaccording to the standard routing optimization criteria, if the completion of thepath is performed by the Ingress NE only. This is not allowed on the other NEsthat could complete the routing because usually they do not know the workingpath information.

731/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Lower cost resources that go towards the egress NE could determine a loop inthe routing: in order to achieve the inclusion of resource LSP calculate a paththat use the lowest cost resources for skipping the holes. While doing this theegress node can be reached before the resources that must be included.

In this case the algorithm fails and returns a "Loop Detection" warningmessages.

In order to avoid Routing Loop, please take into account the following EROguidelines:

• Avoid the setting for inclusion two link clusters that are not consecutive.

• Avoid the setting for inclusion link clusters that start from ingress NE. In thiscase the routing is driven by the NE just immediately after the link included.In this case some of the routing parameters that are known by ingress arenot known by the intermediate NE.

• In case a "hole" is present in the routing, check that after the hole theremaining path is completely defined.

• In case of protected circuits: the protection path is calculated after theworker path, hence during the creation of the worker system does not skipresources that could be included in the protection side. This could createan overlapping of working and protection resources.

• In case of protected circuits: when the diversity is Node, set the egressnode for exclusion.

Exclusion Of Resources

The granularity for the exclusion is limited to the Link Cluster because thepath computation does not take into account a lower level of resources to beexcluded.

The resources to be excluded are managed according to the diversity currentlyassigned to the circuit (Link/Node/SRLG).

In case of Node Diversity the NEs on which the excluded LKs are connected,are skipped.

In case of SRLG Diversity, the SRLG of each LK specified on the ERO areskipped.

In case of Crank Back the excluded resources are kept.

The resources to be exclude are taken into account only in case the completionof the path is performed by the ingress NE, because the other NEs do nothave this information.

74 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Persistency Of ERO Settings

Both Inclusion and Exclusion configuration of network resources is notpersistent to the circuit creation since the signaling protocol apply this criterionone time only and it is not saved into the database.

See Also:

ASTN-DD ERO Management, ERO Management: Object Inclusion andExclusion Configuration

4.12 ASTN-DD Circuit: Safe Disable

PATH: Circuit Query Tool-Safe Disable

The Safe Disable command is used for placing an ASTN-DD circuit into a safelegacy state during the Restore of a NE database.

This command is available only for circuits in "DD Restore Phase I" . For theother circuits the command is grayed out.

To circuits that have "DD Restore Phase I" are those one crossing a node inRestore Phase 1.

Figure 46

To Perform The Safe Disable:

1. Select the circuit from Circuit Query tool.

2. Confirm the command.

After the Safe Disable, the circuit state automatically becomes "RestorePhase II".

In this state:

• All operations from NMS GUI (circuit creation, deletion, manualcommands"¦) that involve the NE under restore procedure are denied.

• If the Restored NE is reachable/running, NMS put OSPF of that node ina special operation mode in which it advertises no resource available to

751/1551-1/AOM 901 084 Uen C2 | 2011-12-15


the rest of the network. This assures that no recovery path will traversethe NE under restore during this procedure.

• The only operation available from NMS and involving the node underrestore is the Disable-safe. This operation permits to the operator toselect all the circuits involving the Restored NE (ending on that orpassing through it), and "release" them (that is, transfer control to NMS,by deleting the LSP structures on nodes and transferring ownership ofcross-connections to TMN) with a node-by-node procedure withoutremoving from S DB all the ASTN information about the circuit in orderto be able to adopt them again at the end of the procedure. Thisoperation may fail on the Restored NE, but this is not important; if better,NMS can decide to avoid sending the disable command to that node.

4.13 Managing The Restore Phase On The ASTN-DDNodes

PATH: Node Query Tool-Restore Phase

When a NE database restore is necessary on an ASTN node, a specificsequence of operations need to performed. This command is used to changethe Restore Phase the node is put during the execution of the whole commandsequence.

Some of the commands necessary to accomplish a safe restore must be run onNM, some from the Local Controller application of the NE.

The Restore Phase command is available on nodes with Enabled DD ASTN.

See Also:

Backup and Restore Procedure on ASTN-DD Nodes

76 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


To Change The Restore State Of An ASTN-DD NE:

Figure 47

The different Restore Phases the NE can be:

No Restore This is the standard state of an ASTN node and the statethat must be set back after the restore execution is over.

DD Restore Phase 1When this state is on the NE set the bandwidth availableto 0 in order to be excluded from any routing calculation.All the circuits (both active and reserved) passingthrough the NE and ending on it are put in RestorePhase I.

DD Restore Phase 2When this state is on the Node realignment is madeavailable back. This state must be selected after the NEdatabase is completely over and the Cross-Connectionshave been deleted.

771/1551-1/AOM 901 084 Uen C2 | 2011-12-15


DD Restore Phase 3This state is selected after the NE has been setON-LINE by means of the JCTS. After this commandthe Circuit can be re-enabled as ASTN-DD resources.

The Restore Phase must be set in a hard sequence. Only the state that canbe set can be selected. Default is No Restore.

1. Select the Restore Phase to set.

2. Press Apply.

4.14 Activating the ASTN-DD Circuits

This command applies on those resources that are still in the Reserved State.

On circuit can remains in Reserved State in the following cases:

It has been created by means of the Add-Circuit Wizard, according to theend-to-end approach, but the Auto Activate check button was not selected. Inthis condition the Control Plane has not calculated the routing and informationregarding the circuit is limited to the endpoints and the routing characteristics.

It has been created by means of the Add-Circuit window, according to thenode-by-node approach and saved in database.

In both the above cases the activation command sets the circuit on the ControlPlane.

To Activate An ASTN-DD Circuit:

1. Select the circuit by means of the Circuit Query Tool.

2. Right click on the circuit name in the Circuit Query Tool and selectActivate command. The same command can be selected from thePop-up menu that is made available by a right click on the circuitrepresentation on the Map.

3. Use Force NON-ASTN check button to select which type of activationmust be performed. If selected, the activation will be carried out accordingto legacy operation, when possible. Default value depends on UserPreferences. After this choice, the activate command behaves in differentway depending on the type of circuit being activated:

• In the case a. the activation command sends the request to the ControlPlane for the calculation of the actual routing between the two specifiedendpoints. The information present in database does not change.The Force NON-ASTN activation is not supported for circuits withend-to-end routing. If the circuit is belonging to the type described incase a. do not check the Force NON-ASTN button.

78 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• In the case b. the activation command sends the explicit routing to theControl Plane and erases the circuit information from database, exceptfor the endpoints and routing characteristics. The Force NON-ASTNactivation is supported for the creation of circuits that need to remainlegacy. These circuits can then be modified to ASTN-DD, if necessary,by means of the command ASTN Management-Enable.

4. Press Apply.

4.15 Deactivating The ASTN-DD Circuits

The deactivate command removes the routing from the Control Plane andkeeps saved the endpoints in database.

Note: After a deactivate command a further re-activation on the same circuitcannot ensure that the same routing will be adopted.

One circuit can be changed to legacy before deactivating, by means of theASTN Management-Disable. In this case the deactivate commands removesthe cross connections from the NEs but save them into database.

Note: This command does not apply on circuits belonging to a Group.

To Deactivate ASTN-DD Circuits:

1. Select the circuit by means of the Circuit Query Tool.

2. Right click on the circuit name in the Circuit Query Tool and selectDeactivate command. The same command can be selected fromthe Pop-up menu that is made available by a right click on the circuitrepresentation on the Map.

3. Press Apply.

4.16 ASON Circuit Displaying and Details

The circuit display details for ASON resources depend on their activation state.The explicit routing is retrieved from the Control Plane upon request of theUser. This means that a circuit in Reserved state does not have the completerouting path saved into database. In this case the Details window shows:

• The endpoints

• The name

• The creation date and the creating User

• The routing characteristics

• The protection type.

See Also:

791/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Creating the ASTN-DD Circuits

4.17 Modify ASON Circuits

The Modify Circuit command depends on the type of circuit. The parametersthat can be modify on legacy circuits differ from the one that can be modifiedon ASON circuits.

By means of this command the main characteristics of a circuit can be changedaccording to the operational requirements:

• The alphanumeric name

• The protection setting and type.

• The diversity mode to be applied on the protection.

• The Service State

• Customer optional data

• The priority value

Except the Customer Data and the Service State setting, all the modifications(including the name) are always spooled to the Control Plane.

Some of the modifications allowed by this command need to be executed inmore than one step. Depending on the actual protection state is sometimenecessary to change the circuit to unprotected before setting a new protectionscheme.

80 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 48

811/1551-1/AOM 901 084 Uen C2 | 2011-12-15


To Manage The Modification On The ASON Circuit:

1. Right Click the circuit from the Circuit Query Tool.

2. Select the Modify command.

3. Use the Name text box to modify the label assigned to the ASON circuit.This name is sent to the Control Plane and saved in DB. In case of circuitdiscovery performed by NM, this name is be retrieved from the network.

4. Use the Protection Type scroll down list to change the protection state.When opening the window the Scroll List selection to the current protectiontype.

Figure 49

No Protection Selecting this item makes the circuit to becomeunprotected. The existing protection is fully removedfrom the nodes and the Control Plane. In somecases described below, this state needs to be set asintermediate step when changing the protection from atype to another.

SNCP If coming from a No Protection state, this item makesthe protection to be created and activated by the ControlPlane. This state can be changed directly from StrongSNCP and No protection types.

Strong SNCP If coming from a No Protection state, this item makesthe protection to be created and activated by the ControlPlane. This state can be changed directly from SNCPand No protection types.

82 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


On-The-Fly This state can be changed directly from Non-rev.On-the-fly and No protection types.

Non-rev. On-The-FlyThis state can be changed directly from On-the-fly andNo protection types.

5. Use the proper slider to change the Priority assigned to the circuit, inaccordance with the protection type. This is available only if the circuitis reserved.

6. Use the proper slider to change the Wait To Restore Time, in accordancewith the protection type. This is available only if the circuit is reserved.

7. Use the Routing Optimization Criteria pull down menu to change the typeof routing calculation. This is available only if the circuit is reserved.

See Also:

Creating the ASTN-DD Circuits

8. Use Diversity check buttons to change level of difference that the ControlPlane will adopt when calculating a protection route for the selected circuit.

Node The protection side will be calculated through NEsdifferent from worker.

Link The protection side will be calculated through Linkdifferent from worker.

SRLG The protection side will be calculated through SharedRisk Link Group different from worker.

9. Use Service state check buttons to enable the circuit alarm displayingon the Alarm Monitoring Window.

10. Use Customer Data push button to access the input window for theoptional information of the circuit. This is the only modification that remainson database.

11. Press Apply.

See Also:

Restoration Protection, Backup and Restore Procedure on ASTN-DDNodes

4.18 Re-routing An ASTN-DD Circuit

The ASTN-DD Control Plane provides automatic re-calculation of the circuitrouting path in case of failure on the working or protection side, dependingon the protection type.

831/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command provides a manual re-calculation of routing in the followingcases:

Non-revertive On-The-FlyThe Control Plane calculates an alternative circuitrouting and replaces the current one. In case the currentroute is the actually the best one in the network (thenormal working path), the control plane will select thesecond choice (except the current one). The re-routecommand can be used to move back the circuit to thebest routing path after a failure. If the circuit is protectedwith Non-revertive On the Fly, there is no diversityrestriction to comply with.

Strong SNCP The Control Plane replaces the current protection routewhen the circuit is running on the worker side. Thereroute command can be used to restore the preferredprotection route of a circuit after a fault. In case thisprotection is set on a circuit, the rerouting must becompliant with the diversity criteria set at creation time.If there is no path compliant with the diversity level, thererouting command fails.

Not protected circuitThe Control Plane replaces the current routing of acircuit, according to the actual state of the network. Incase of not alarmed circuit the sequence of operationis: recalculation, activation of the new route as revertiveprotection of the current one, swap, removing theprotection. The command can also be applied onalarmed circuits in order to provide a manual trafficrestoration. The re-route command can be used tooptimize the usage of the bandwidth in case of networkmodifications (that is internodal link addition). If thecircuit is not protected, there are no diversity criteriato be compliant with.

To re-route an ASTN-DD circuit:

1. Right-click the circuit on the Circuit Query Tool.

2. Select the Reroute command. The same command can be selectedfrom the Pop-up menu that is made available by a right click on the circuitrepresentation on the Map.

3. Press Apply. One confirmation message appears.

84 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 50


4.19 Managing The ASON Protection Switches

According to the protection type some switch commands can be send manuallyfrom GUI to the control plane. Depending on the type of protection configuredthe switch could cause a simple changeover to protection side as well as acomplete re-calculation of the routing.

To manage the protection switches:


2. Select the Protection-Modify command. This command is alsoavailable from the pop-up menu.

851/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 51

3. Select the command to send.

Clear This command erases any previous switch commandfrom the circuit.

Forced toprotection

This command makes the circuit to be switched on theprotection side. In case of On-the Fly protection type,this command also makes the control plane to calculatethe protection route.

Lockout This command blocks any switch toward the protectionside and force the switch back to the working sidewhen the traffic is running on protection. To remove aLockout is necessary a Clear command.

4. Press Apply.

86 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.20 Checking The ASON Circuit Working Side

This command applies to circuit whose protection type deals with two routes atthe same time (working and protection).

The information is retrieved from the control plane upon request of .

To Get The Current Circuit Working Side:


Note: This command is supported by circuits with SNCP, Strong SNCPand Rev OTF protection type (Rev. OTF if only switched toprotection side).

2. Select the Protection-Working Side command. The same commandcan be selected from the Pop-up menu that is made available by a rightclick on the circuit representation on the Map.

Figure 52

Information is taken from the Control Plane and includes the following data:

871/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Starting and ending nodes

• Current working side

• Last command performed on the working side

• Last command performed on the protection side

3. Press Print to spool the result to the system printer.

4. Press Export to save the result in a text file.

5. Press Close.

See Also:

Managing the ASON Protection Switches

4.21 Disassociating An ASON Circuit

This command erases database information about an ASON circuit. The wholecircuit information remains on the Control Plane and can be re-associatedwith the same name, by means of the command Configuration-ASTN-DDCircuit Discovery

To Disassociate An ASTN-DD Circuit:


2. Select the Disassociate command. The same command can beselected from the Pop-up menu that is made available by a right click onthe circuit representation on the Map.

A confirmation message appears.

Figure 53


After this command is executed, the protection information based on theGMPLS signaling is removed. The Non revertive On the Fly protectedcircuits become Unprotected and the Strong SNCP become SNCP.

88 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:

ASTN-DD: Topology Discovery

4.22 Enabling The ASON Protocol On A Circuit

This command changes the management protocol of a selected legacy circuitto ASON. The availability of this command depends on the state of the circuitrouting currently saved in database.

If the circuit has been created according to the node-by-node approach, thiscommand sends the explicit routing to the control plane.

In case the circuit is reserved, this command is not applicable.

Note: About this feature, please take into account that: in case the circuitis protected via Revertive On The Fly mechanism AND it iscurrently running on protection leg, this command cannot be executed.The command cannot be executed also in case of SNCP not Revertive.In the latter case, change the protection type and run the Enablecommand.

If the circuit was previously disabled from former ASON management, thisoperation will restore the old parameters that were discarded while disablingASTN. The information below is taken from a system file:

• ASTN DD Protection Type (Strong SNCP and Non Revertive On The Fly)

• ASTN diversity

• Wait to Restore time

• Priority

• Colour

• Routing Criteria Cranck Back

To Enable ASON Protocol On A Circuit:


2. Select the ASTN Management-Enable command. The same commandcan be selected from the Pop-up menu that is made available by a rightclick on the circuit representation on the Map.

3. Press Apply.

See Also:

Disabling the ASON Protocol on a Circuit

891/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.23 Disabling the ASON Protocol on a Circuit

This command changes the management protocol of a selected ASON circuitto legacy.

No command is executed on the cross connections belonging to the circuit.After the command is complete no Control Plane automation is supported onthe selected circuit. About this feature, please take into account that:

• In case the circuit is protected via Revertive On The Fly mechanism ANDit is currently running on protection leg, this command cannot be executed.

• When disabled, the ASON characteristics are saved in a system file that isthen used in case the same circuit is re-adopted. See the paragraph:

Enabling the ASON Protocol on a Circuit

To Disable The ASON Protocol On A Circuit:


2. Select the ASTN Management-Disable command. The same commandcan be selected from the Pop-up menu that is made available by a rightclick on the circuit representation on the Map.

3. Press Apply.

Warning!

Disabling of ASTN DD protocol on Multiple circuit can sometimes create amisalignment between control plane and IPT NMS - Circuit database. This canhappen in case a node restart takes place while un adopting ASTN DD. Alwayscheck the status of the circuits involved in the command after completed.

In case one or more circuit are in state Reserved with ASTN DD protocol stillenabled, perform a discovery command to realign the network.

In case on more circuits are in state Reserved with ASTN DD protocoldisabled, please execute the following command on each of them:

1. Disassociate the circuit.

2. Realign the nodes involved.

3. Associate the circuit by means of the Find command.

4. Enable the ASTN DD back on the circuit (if necessary).

90 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:

Disassociating an ASON Circuit

4.24 Managing ASON Alarms From The GUI

The complete routing of the ASON circuits is saved in database, for this reasonthe full Alarm Monitoring and Correlation is available from the GUI.

The usage of the Alarm Management tools is fully aligned with the standardNMS ones.

4.25 Backup And Restore Procedure On ASTN-DD Nodes

4.25.1 Introduction

The (backup and) restore procedure must be adopted when the existing trafficand control plane configuration is lost on one of the ASTN-DD controlled nodes.This may result in the need of restoring the previous configuration according toinformation last stored in IPT NMS - Circuit database.

The backup on the NE should be periodically performed by means of the JCT orthe EM and saved separately. In specific cases when configuration is lost, thesingle node backup must be restored on the NE by means of the JCT/JCTS.

Once the single NE backup database is restored on the ASTN-DD node, aspecific procedure must be adopted before switching the node back to On-Linestate.

The procedure is due to minimize the possible differences between the restoredASTN-DD node configuration and the state this node is expected to have onIPT NMS - Circuit.

The specific restore procedure may differ according to the type of crash at theorigin of the restore. Four main scenarios can be listed.

• Scenario 1 - Crash NE: a new node must replace the crashed one. NewCompact flash cards, new shelves and new cards must be used

• Scenario 2 - Compact Flash cards Out of Order. Previous shelves andcards can be used

• Scenario 3- Restore after a decommissioning with network element on-line(operator mistake). Previous shelves and cards can be used

• Scenario 4 - Database corruption: IPT NMS - Circuit and NE databasesmisalignment. Previous shelves and cards can be used

911/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The following procedures describe the complete sequence of commandsnecessary to carry out a complete database restore of NE without trafficaffection for each of the above mentioned scenario.

Please, carefully check the scenario and apply the relevant procedure.

Some of the command described below must be executed on NM, some on EMNE JCT. For commands that must be run on IPT NMS - Circuit a reference tothe relevant description is provided.

ALERT The Restore procedure can be carried out on one NE at the time.

4.25.2 Preliminary operation

Before starting this procedure, please check that in MV38.ini, inside the [CPM]section, the following parameters are set as indicated:

IgnoreRealignTrap = true

(Line to be inserted, the hidden default value is false)

AutoRealignNeeded = false

RealignNeeded = false

(Line to be inserted, the hidden default value is true)

Note: Every MV38.ini modification requires a restart of in order to load thenew parameters.

Caution!

In any case, during the B&R procedure and any time a node is not reachablefrom OSS, it is FORBIDDEN to perform a topology discovery. Running it inthis situation shall result in loosing the ASTN configuration for the node, andtherefore the possibility to restore it later.

4.25.3 Restore Procedure On Scenario 1

1. Using the Node Query Tool, put NE in Restore Phase I. See Reference[2], paragraph "Managing the Restore Phase on ASTN-DD Nodes " ,for more details.

This operation must be performed as soon as the crash of the NE hasbeen detected.

92 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


All the ASTN circuits still passing through or terminated on the NE mustbe passed to S (becoming legacy circuits), as described in the first twosteps of the paragraph:

Restore Procedure on Scenario 4

2. Using JCTS, open the Configuration-Ospf Params window and verify thatthe NE parameter Force No Free Band is now selected. This parameteris used by the Restore Phase to get the node excluded from any routingcalculation.

3. Set the Safe Disable command on the Circuit that is in Restore Phase1. See Reference [2], paragraph "ASTN-DD Circuit: Safe Disable" ,for more details.

This operation allows the operator to select all the circuits involving on theRestored NE (ending on it or passing through it), and "œrelease" them (thatis, transfer control to NMS, by deleting the LSP structures on nodes andtransferring ownership of cross-connections to TMN) with a node-by-nodeprocedure without removing from S DB all the ASTN information about thecircuit in order to be able to adopt them again at the end of the procedure.

A part of the procedure in this scenario must be executed at the NElocation, by means of the JCT application.

Once the new node has been installed and the relevant application softwaredownloaded (not needed to download licenses for ASTN or enable theASTN stack as this is performed automatically by the restore procedure,if the node was previously an ASTN node) the following steps must befollowed.

4. Switch on the NE.

5. Configure, via LCT the switch units and the traffic units/ports in the NEcarrying NMS DCCs in order to regain communications with S.

6. Download from the LCT the OSI.ini of the old node (which has beenbacked-up on EM). At this point the NE is reachable by the EM. If this didnot happen, perform a CCU restart.

7. Using JCT/JCTS put the NE to be restored in OFF-LINE mode. This is arequired step, necessary for the actual restore of internal data from externalbackup file.

8. Restore the backup file on the NE, by means of the EM.

When the download is over, the NE reboots.

931/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Caution!

Downloading the MIB does not mean that the information it is sent to PUsor to the matrix, this only happens when the NE is put again in the On-Linestate.

9. Using JCTS, (command is GMPLS Restoration), remove all the (no longerASTN) Cross-connections, using the specific function allowed in Off-linestate, that allows to remove all the ASTN X-connections and all the GMPLSreservation on the termination points.

Perform all the necessary checks between database and the status ofthe NE as detailed in the paragraph:

Specific Checks to Perform After NE Restore

In case some differences are present always proceed using DB as areference.

When the configuration of the NE is perfectly aligned with the configurationon NM, proceed with next step.

10. Using IPT NMS - Circuit set the set the Safe Disable command on thecircuits in Restore Phase I. See Reference [2], paragraph "ASTN-DDCircuit: Safe Disable" , for more details.

11. Using the Node Query Tool on NM, set the Restored NE to the "RestorePhase II" state. See Reference [2], paragraph "Managing the RestorePhase on ASTN-DD Nodes " for more details.

12. Using NM, realign the NE that is in "Restore Phase II" state.

Circuits terminating or crossing the NE being restored go in PartiallyActive state.

Caution!

In case some circuits are in active state after this realignment the followingstep must be skipped, and they can remain in Restore Phase II.

13. Using NM, activate all the circuits involving the Restored NE, selectingthe option Force Non ASTN check button. See Reference [2], paragraph"Activating the ASTN-DD Circuits" , for more details.

94 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


All cross-connections in "reserved" state are activated on the RestoredNE as SDH.

Note: After this activation the circuits get "Restore Phase III" state.

14. Check the ASTN configuration using ASTN JCT Configurator and retrievingthe information from NMS. The configuration on the Restored NE and theconfiguration present in S Database must be aligned.

15. Put the Restored NE in On-line state using JCTS. After this command theCCU reboots.

16. Using IPT NMS - Circuit set the Restored NE in the "Restore Phase III"state. See Reference [2], paragraph Managing the Restore Phase onASTN-DD Nodes, for more details.

17. Using NM, perform the Enable ASTN command on all the circuits involvingthe NE restored.

Note: This command can also be set on those circuits that were in activestate after the realignment.

18. Using IPT NMS - Circuit set the Restored NE in the No Restorestate. See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.

After this command all the circuits involved in the restored NE get back toNo Restore State.

19. Using JCTS, open the Configuration-Ospf Params window and verifythat the NE parameter Force No Free Band is now unselected. Thisparameter is used by the Restore Phase to get the node excluded fromany routing calculation.

See Also:


4.25.4 Restore Procedure On Scenario 2

In this case the CCUs should restart and may end in High Level Boot (orpossibly restart continuously).

There are actually different ways a Compact Flash may get corrupted : if thedamage is in the Sw partitions, then the CCU will end in HLB; if the damageis in the MIB partition then the CCU could keep on restarting (until the CF isextracted). In this situation the following steps must be followed.

A part of the procedure in this scenario must be executed at the NE location, bymeans of the JCT application.

951/1551-1/AOM 901 084 Uen C2 | 2011-12-15


1. Put the NE in Restore Phase 1 status on NM. This operation must beperformed as soon as the failure of Compact Flash has been detected.

All the ASTN circuits still passing through or terminated on the NE mustbe passed to S (becoming legacy circuits), as described in the first twosteps of the paragraph:

Restore Procedure on Scenario 4

2. Using JCTS, open the Configuration-Ospf Params window and verifythat the NE parameter Force No Free Band is now selected. Thisparameter is used by the Restore Phase to get the node excluded fromany routing calculation.

3. Extract the old CFs and substitute them with new ones including the rightversion of SW, but without the MIBs and licences, which shall be recoveredby the restore procedure.

4. Download from the LCT the OSI.ini of the old node (which has beenbacked-up on EM). At this point the NE is reachable by EM.

5. Using JCT put the NE to be restored in OFF-LINE mode. This is a requiredstep, necessary for the actual restore of internal data from external backupfile.



Caution!

Downloading the MIB does not mean that the information it is sent to PUsor to the matrix, this only happens when the NE is put again in the On-Linestate.

7. Using JCTS, remove all the (no longer ASTN) Cross-connections, using thespecific function allowed in Off-line state, that allows to remove all the ASTNX-connections and all the GMPLS reservation on the termination points.





96 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


8. Using IPT NMS - Circuit set the Restored NE to the Restore Phase IIstate. See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.

9. Using NM, realign the NE that is in Restore Phase II state.


Warning!



All cross-connections in reserved state are activated on the RestoredNE as SDH.

Note: After this activation the circuits get Restore Phase III state.



13. Using IPT NMS - Circuit set the Restored NE in the Restore Phase IIIstate. See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.



15. Using IPT NMS - Circuit set the Restored NE in the No Restore state.See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.


16. Using JCTS, open the Configuration-Ospf Params window and verify thatthe NE parameter Force No Free Band is now unselected. This

971/1551-1/AOM 901 084 Uen C2 | 2011-12-15


parameter is used by the Restore Phase to get the node excluded fromany routing calculation.

See Also:


4.25.5 Restore Procedure on Scenario 3

Follow the same actions sequence already described in the Section 4.25.3on page 92.

4.25.6 Restore Procedure on Scenario 4

1. From Node Query Tool on NM, set the Node on Restore Phase 1. SeeReference [2], paragraph "Managing the Restore Phase on ASTN-DDNodes " , for more details

Due to this state the operations on the circuits served by the NE areblocked by NMS.

All operations from NMS GUI (circuit creation, deletion, manual commands...) that involve the NE under restore procedure disabled.

If the Restored NE is reachable/running, NMS put OSPF on the node ina special operation mode: no resources are made available to the rest ofthe network. This assures that no recovery path crosses the NE underrestore during this procedure.

The only operation available from NMS and involving the node underrestore is the Safe Disable.

2. Set the Safe Disable command on the Circuit that is in Restore Phase1. See Reference [2], paragraph "ASTN-DD Circuit: Safe Disable" ,for more details.

This operation allows the operator to select all the circuits involving on theRestored NE (ending on it or passing through it), and release them (thatis, transfer control to NMS, by deleting the LSP structures on nodes andtransferring ownership of cross-connections to TMN) with a node-by-nodeprocedure without removing from S DB all the ASTN information about thecircuit in order to be able to adopt them again at the end of the procedure.

3. Using JCTS, open the Configuration-Ospf Params window and verifythat the NE parameter Force No Free Band is now selected. Thisparameter is used by the Restore Phase to get the node excluded fromany routing calculation.

4. Using JCT, put the NE to be restored in OFF-LINE mode. This is a requiredstep, necessary for the actual restore of internal data from external backupfile.

98 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15




Note: Downloading the MIB does not mean that the information it is sentto PUs or to the matrix, this only happens when the NE is put againin the On-Line state.

6. Using JCTS, remove all the (no longer ASTN) Cross-connections, using thespecific function allowed in Off-line state, that allows to remove all the ASTNX-connections and all the GMPLS reservation on the termination points.





7. Using IPT NMS - Circuit set the Restored NE to the Restore Phase IIstate. See Reference [2], "Managing the Restore Phase on ASTN-DDNodes " , for more details.

8. Using NM, realign the NE that is in Restore Phase II state.


Warning!



All cross-connections in reserved state are activated on the RestoredNE as SDH.

Note: After this activation the circuits get Restore Phase III state.


991/1551-1/AOM 901 084 Uen C2 | 2011-12-15



12. Using IPT NMS - Circuit set the Restored NE in the Restore Phase IIIstate. See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.



14. Using IPT NMS - Circuit set the Restored NE in the No Restore state.See Reference [2], paragraph "Managing the Restore Phase onASTN-DD Nodes " , for more details.


15. Using JCTS, open the Configuration-Ospf Params window and verify thatthe NE parameter Force No Free Band is now unselected. Thisparameter is used by the Restore Phase to get the node excluded fromany routing calculation.

See Also:

Backup and Restore Procedure on ASTN-DD Nodes

4.25.7 Specific Checks to Perform After NE Restore

Some additional checks should be taken into account while performing aRestore operation in order to ensure a successfully restoration.

The Control Plane Configuration and the current traffic matrix existing on themanaged network are correctly saved into database and on the other NEspresent in the ASTN-DD network. Some differences may be present betweenthe restored NE and what is expected by it within the ASTN-DD network.

After the restore a set of check must be executed on specific NE and Networkresource, so as to align the configuration of the NE to the configuration it hadon before the failure.

These checks may result in manual commands to be executed on the NE:

• All the resources that were present on but not present on the NE after therestore must be manually added.

• All the resources that are present on the NE but not present on db mustbe manually removed.

100 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The following network configuration & differences between back-up file andactive configuration must be generally considered:

Network Configuration:

• Restored Node is Ingress, Egress and transit node for SDH and ASTNcircuits.

• Mono-node circuits.

• Tandem SNCP circuits (both legacy and ASTN)

• MSP

Differences Between The Backup And The Current Configuration On NM:

• Backup with circuits on protection path

• New circuits created (VC4, VC4-4c, VC4-16c, Tandem SNCP VC4)

• Previous circuits deleted (some freed resources used by new circuits)

• Tandem SNCP leg added to a SDH circuit

• Tandem SNCP leg added to an ASTN circuit

• ASTN circuit name modified

• SDH circuit migrated to ASTN

• New Links

• Previous Links deleted (some freed resources used by new links)

• New cards plugged in

• Previous cards extracted (some cards replaced by new ones)

• New Ethernet circuit Group using new Ethernet ports

• Add a circuit in an Ethernet circuit Group

• Remove a circuit from an Ethernet circuit Group

According to the above mentioned items, the suggestion and recommendationsbelow should be taken into account before setting the restored NE on-line:

• When a 4 points TSNCP is present, SNCPs are configured asNon-Revertive and therefore they can not be adopted as ASTN circuits.

Workaround: The relevant circuit must be kept legacy until the end of theprocedure. Then from IPT NMS - Circuit it is possible to change manually

1011/1551-1/AOM 901 084 Uen C2 | 2011-12-15


the protection behaviour to Revertive and then it is possible to adoptthe circuit.

• When a 4 points TSNCP is present, sometimes it is shown as active/activeeven if it should be active/partially active.

Workaround: It is always needed to check the details of the relevant circuit,in order to verify the status. In this case the missing cross-connection mustbe recreated manually from MV36 and then a node realignment has to beperformed.

• For TSNCP and non-revertive OTF circuits, if the circuit state is differentfrom the one to be restored, the procedure will fail.

Workaround: The relevant circuit must be kept legacy until the end ofthe procedure. Then, from IPT NMS - Circuit it is possible to remove theTSNCP manually, realign the node again, then recreate the TSNCP andadopt the circuit.

• It is impossible to adopt circuits when their current state is different fromidle (Norequest/OneLsp).

Workaround: the relevant circuit must be kept legacy until the statusbecomes idle again, and then it may be readopted.

• The configuration of MSP, MS-SPRING and Card protection on terminationside are not used by NM, even they are on the NE. This means that in casethey were present on the node at the backup, they will be restored on theNE. This information is anyway not reported by .

Workaround: Verify whether this protections are really needed in theASTN-DD networks or not. In case they are not they must be erased fromthe NE. Check the current operation of the protections since the removal ofa protection may affect the traffic on protection side (if any).

• Check any type of single cross connection not belonging to circuit (Tandemand SNCP) Verify those one that are present on (using the single removeX-Conn command on GUI)

Workaround: Re-create manually the single Tandem SNCP connectionsand the single SNCP protections that are not present in the NE restored.

• Check the Trail Trace Monitoring currently enabled on Links and Circuitsinvolved in the being restored NE.

Workaround: Disable the trail trace monitoring on such resources, in ordernot to have RS-TIM alarm that can interrupt traffic while putting online theNE.

See Also:

Restore Procedure on Scenario 1, Restore Procedure on Scenario 2,Restore Procedure on Scenario 4

102 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.26 Maintenance Pre-Requisites For ASTN-DD NEs

The following procedure must be adopted when an ASTN-DD NE needs to bestopped for maintenance, (for example hardware upgrade) in order to ensurethat the traffic is guaranteed during the NE maintenance activity.

These pre-requisite can be summarized in the following actions:

• Exclude the node from the ASTN Network.

• Connect the JCT PC to the Equipment and launch the control application.

• Check that the system is alarm free or, in any case, not affected by internalalarms that could cause traffic hits.

• Verify that all the protections configured on the system (MSP, CardProtection, MS-SPRing, SNCP, ASTN Protections) have the normal"worker" resource "in service mode" and in "No Request" state.

• If the system is involved in a MS-SPRing, exclude it from participating intothe protection.

• Stop the system provisioning from S.

• Disable the GMPLS protocol management on the system.

• Perform a database backup.

Some of the operations to be performed are executed by EM/JCTS but themain preparation and the further completion needs to be managed from theNetwork Manager.

This procedure applies on all the NE supporting the ASTN-DD protocol.

1. Empty the links cluster (if possible) that are connected to the node to beupgraded. To empty the link put it into a lock state, in order not to beused for routing and re-routing then, using the Re-route command and theprotection switches, move the traffic away from the connection.

See Also:

Link Cluster Commands: Setting Locking State, Commands AfterSetting the Locking State

Note: Re-routing command or protection switches should be selected inaccordance with the type of circuit and protection currently in use.

2. Take note of all the ASTN circuits still crossing the node due to unavailabilityof alternative routes. Take also note of the circuit ending on the NE to beexcluded from network. They are supposed to be in Restore Phase I.

1031/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Note: Take a printout of the list. In order to easily find the circuitsafterwards it is suggested a modification of their name includingASTN indication, Protection Type and Diversity type. Use theModify command on NM, to perform this operation, if necessary.

3. Set the NE to Restore Phase I. All the circuits involved with the nodego on Restore Phase I.

4. Set in sequence the NE to Restore Phase II, Restore Phase IIIand then to No Restore.

5. Disable the ASTN all the ASTN circuits involved in the NE on the basisof the list previously taken. The ASTN circuits still crossing the node orterminating on it become legacy.

6. Set the NE to Restore Phase I. The NE stops the OSPF protocol. Afterthis command the NE is excluded from any routing calculation.

7. Check that no circuit in Restore Phase I are present on that node.

8. Set the NE to Restore Phase II. This is necessary to realign it in afurther step.

Note: After this command the procedure proceeds on the EM and JCT.Refer to EM and NE documentation to get more details on how toaccomplish the commands suggested from now on.

9. Using the NE Data List window, detect the NE id.

10. Stop the OSI communication between EM and NE, using the Start/StopNE command.

After this step the NE is isolated from the Network Managed System,the traffic flowing through it is managed as legacy type. The NE can bemaintained as fully detailed in the relevant documentation.

11. After the Local Node maintenance is completed move on EM applicationand manage the NE in accordance with its new state after the maintenanceoperation.

12. Just in case of NE upgraded to a new ne_type, log in as nmcman andtype the following commands:

csh

source /etc/mv36.cshrc

cd $NCS/script

csh -f oms3255-1K_2_oms3255-2K <OMS3255(160G) ne_id>

The ne_id parameter is previously retrieved in the first part of theprocedure.

104 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


13. Restart the OSI communication on the EM.

14. As soon as the communication is on, run the ASTN-DD Configuratorfrom the EM and check that the Control Plane currently running on theNode is exactly the one saved on Database.

15. In case something is different on the control plane configuration, align theNE with the information stored on database.

See Also:

ASON Label Switched Router Query Tool, ASON Link Cluster QueryTool, ASON Link Component Query Tool, ASTN Control ChannelQuery Tool

Note: After this command the operation proceed back on .

16. Realign the NE from the Network Manager Map.

17. Set the NE to Restore Phase III and then to No Restore.

18. Perform an ASTN-DD topology discovery.

19. According to the circuit list previously saved, select the circuits involvedwith the NE and run the Enable ASTN command on them.

20. Just in case the circuit names were modified before the ASTN Disable,restore them to the original ones.

Note: After this step, the NE can be re-assigned to S and Control Planemanagement. The link clusters set to Locked can now be set tounlocked.

See Also:

Backup and Restore Procedure on ASTN-DD Nodes, Link ClusterCommands: Resetting Locking State

4.27 Port operations

In this section we describe all the operations related to the management ofthe Ports and the Port Query Tool, which is a browser for the Ports currentlyconfigured in the IPT NMS - Circuit database.

4.27.1 Network Query Tool: Port Window

PATH:(Configuration-Port Query Tool)

The Port Query tool is a browser for the Ports currently configured in the IPTNMS - Circuit database.

1051/1551-1/AOM 901 084 Uen C2 | 2011-12-15


These resources are listed in the Port Query tool in order to be available forfurther selection and management.

All the commands that could be run on Ports are available from this window.

Before running any command on Ports, a filtering phase on the databaseis necessary.

To filter the Ports:

Figure 54

• Manage the selection of nodes on the Map (at least one node must beselected), as described in: Network Query Tools: Managing the MapSelection

• Use LinkName, Path Nameand Circuit Nametext boxes and MatchCasecheck button to set an alphanumeric criterion on the filtering.

• Use Port Typescroll down list to set the filtering on the typology of the Port.

• Use ASONscroll down list to set the filtering on the ASON enabling state ofthe Port (All, Yes, No)

• Use Connectedscroll list to set a filtering on the Connection state of thePort (All, Yes, No)

• Use Operational Statescroll list to set a filtering on the Operational Stateof the Port (All, enable, disable)

• Press Searchbutton. All the ports matching with the filtering criteria arelisted in the Resultbox.

• Select View-Resetfrom the Node Query Tool menu bar to reset to default.

106 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


To select the Ports and run a command on them:

• Arrange the resource list, if necessary, as described in:

Network Query Tools: Common Menu Bar and Widgets

• Using the mouse buttons, proceed with the selection of one or more Ports.

left button

Single exclusive selection: every click selects one item only (previousselections are removed). Left button plus SHIFT key extends a selection downto the clicked row.

middle button

Multiple selection: every click adds an item to the current selection. Samebehavior with left button + CRTL key. Also toggles the selection of an alreadyselected item.

right button

Selection and Pop-up menu: the click opens a menu including the commandsapplicable at the current condition on the highlighted items (single or multiple).

• Select the command to run, from the list shown by the Pop-up menu. Thecontent of the Pop-up menu depends on the type of Port selected as wellas on the configuration state. Moreover a certain pop-up menu is given forsingle selection while another one is given for multiple selections, whichmakes available inquiry commands only.

Figure 55

More details in: Map Main Objects: Pop-up Menus

1071/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• The selected command is activated, in accordance with the currentselection.

See Also:

Port Commands ,Configuration Facilities: Network Query Tools

4.27.2 Port Commands

Every Path in the IPT NMS - Circuit domain can be applied with differentcommands, which depend on the actual configuration state. All the commandslisted below can be accessed from the Map or from the proper Network QueryTool.

See Also:

Network Query Tool: Port Window

4.27.2.1 Port Commands: Details

PATH:(Port Query Tool-Details)

This command allows the IPT NMS - Circuit operator to display the informationabout the Port: details are shown in a separate window.

To display the details related to a Port:

• Select the Detailscommand from the Pop up menu.

The following window is displayed.

108 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 56

The port information displayed is:

• the Name,

• the NE Nameandtherelated Short Name,

• the Logical Name,

• the Shelf ID,

• the Card ID,

• the Port ID,

• the Connectedstate(Yes/No),

• the Operational State(Enabled/Disabled),

• the Port Type,

• the ASON enabling state (Yes/No),

• the Bandwidth.

According to the port typology, additional information is displayed, as describedbelow:

• In case of Optical ports, the related Frequencies are displayed.

• In case of Ethernet ports (VCGs), the associated virtual VC4s are displayed.

1091/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• In case of Backplane ports, the related Structuring Mode is displayed:(Flat/Nested).

• In case of Muxponder or dual stage configured Link Mode Transponderports, the related Channels Configuration is displayed, for each channel itis displayed:

• the Name,

• the Timeslot,

• the Channel Type (OTM/SDH, only for Muxponder ports),

• the Operational State.

• If applicable it is displayed the list of Performance Jobs on different layers(OTS, OMS, OCH, OTU, ODU, RS, MS, HO, LO).

• If applicable it is displayed the Trail Trace State on different layers (OTS,OMS, OCH, OTU, ODU, RS, MS, HO, LO).

• If applicable it is displayed the Regeneration information (Optical or SDH).

In case of protection ports involved in MSP/MSP-Ring/Inter-PortProtection/Inter-Card Protection/Intra-Card Protection, it is displayed thefollowing Port Protection Information:

• The Protection Type (Inter-card/Intra-card/Inter-port)

• The Protection Role (Worker/Protection).

• In case of Inter-Port Protection ports, the Connected Port is displayed.

• In case of MSP, the MSP Protection Type is displayed.

• In case of MSP-Ring Protection ports, the MSP-Ring Name is displayed.

• Press Printto spool the output to the system printer.

• Press Exportto save the output.

• Press Closeto quit the window.

4.27.2.2 Port Commands: Connectivities

PATH:(Port Query Tool-Connectivities)

This command allows the IPT NMS - Circuit operator to display informationabout the eventual involvement of the Port in Connectivities (Links, CrossConnections, Circuits and Paths): details are shown in a separate window.

To display information about the connectivities in which a Port is involved:

• Select the Connectivitiescommand from the Pop up menu.

110 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15



Figure 57

This window shows if the port is involved in the following connectivities,displaying the related information:

• Link (the Link Name),

• Cross Connections(the Name, the Life State, the Admin State and theEnd Port Name)

• Circuits (the Circuit Name),

• Paths (the Path name).

See Also:

Port Commands: Details

4.27.2.3 Port Commands: Modify

PATH:(Port Query Tool-Modify)

This command allows the IPT NMS - Circuit operator to modify the logicalname of a Port.

After selecting the command the following window is displayed.

1111/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 58

To modify the logical name of a Port:

• Type in the Logical Nametext boxthe new Port logical name.

• Press Apply.

See Also:

Port Commands: Details

4.28 Combined Path operations

In this section we describe all the operations related to the management of theCombined Paths and the Combined Path Query Tool, which is a browser forthe Combined Path currently configured in the IPT NMS - Circuit database.

4.28.1 Network Query Tool: Combined Path Window

PATH:(Configuration-Combined Path Query Tool)

The Combined Path Query tool is a browser for the Combined Path currentlyconfigured in the IPT NMS - Circuit database.

These resources are listed in the Combined Path Query tool in order to beavailable for further selection and management.

All the commands that could be run on Combined Paths are available fromthis window.

Before running any command on Combined Paths, a filtering phase on thedatabase is necessary.

To filter the Combined Paths:

112 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 59

• Manage the selection of nodes on the Map as described in :

Network Query Tools: Managing the Map Selection

• Use Nameand Link Cluster Nametext boxes and Match Casecheck buttonto set an alphanumeric criterion on the filtering.

• Use Path State scroll down list to set the filtering on the State of theCombined Path (please refer toResource States for details)

• Use Protection Typescroll down list to set the filtering on the protectiontype of the Combined Path (All, No Protection, Safe SNCP, SNCP,Transponder Sharing)

• Use TC Operational Statescroll list to set a filtering on the TerminatedCircuit operational state of the Combined Path (All, Green, Yellow, Red)

• Use ASON Operational Statescroll list to set a filtering on the OperationalState of the Combined Path (All, enable, disable)

• Use Restore Phasescroll list to set a filtering on the Restore Phase of theCombined Path (All, No Restore, DD Restore Phase 1, DD Restore Phase2, DD Restore Phase 3)

• Press Searchbutton. All the combined paths matching with the filteringcriteria are listed in the Resultbox.

• Select View-Resetfrom the Node Query Tool menu bar to reset to default.

To select the Combined Paths and run a command on them:



1131/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Using the mouse buttons, proceed with the selection of one or moreCombined Paths.

left button


middle button


right button


• Select the command to run, from the list shown by the Pop-up menu.The content of the Pop-up menu depends on the type of Combined Pathselected as well as on the configuration state. Moreover a certain pop-upmenu is given for single selection while another one is given for multipleselections, which makes available inquiry commands only.

Figure 60



114 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:

Combined Path Commands ,Configuration Facilities: Network QueryTools

4.28.2 Combined Path Commands

Every Combined Path in the IPT NMS - Circuit domain can be applied withdifferent commands, which depend on the actual configuration state. All thecommands listed below can be accessed from the Map or from the properNetwork Query Tool.

See Also:

Network Query Tool: Port Window

4.28.2.1 Combined Path Commands: Show Path on Map

PATH:(Combined Path Query Tool-Show Path on Map)

This command allows the IPT NMS - Circuit operator to show the CombinedPath on the Map.

All the OCH paths referring to the selected Combined Path are displayed in theactive map in the usual way.

The paths belonging to a SafeSNCP or a TSP and in "pre-plan" state aredisplayed as a dark dashed line in a transparent way.

To display a Combined Path:

• Select the Show Path On Mapcommand from the Pop up menu.

The Combined Path is drawn on the Map.

• Select the option View-Erase Trail From Mapfrom the menu bar to deletethe Combined Path representation from the map. Same option is availablefrom Network Query Tool.

See Also:

Path Commands: Display On Map

4.28.2.2 Combined Path Commands: Linear Display

PATH:(Combined Path Query Tool-Combined Path popup menu-LinearDisplay)

This command allows the IPT NMS - Circuit operator to display the CombinedPath on a separate window (linear display): it allows to display exclusively all

1151/1551-1/AOM 901 084 Uen C2 | 2011-12-15


the OCH paths or the ODU path referring to the selected Combined Path in theactive map in the usual way, by default OCH paths are displayed.

To get the Linear Display of a Combined Path:

• Select the Linear Displaycommand from the Pop up menu.


Figure 61

The IPT NMS - Circuit operator can choose among these two kinds of view, byusing the following apposite buttons:

• Show ODU Path,

• Show OCH Paths.

Here is the window displaying the ODU Paths.

Figure 62

116 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The paths belonging to a SafeSNCP or a TSP and in "pre-plan" state aredisplayed as a dark dashed line in a transparent way.

See Also:

Network Maintenance: Resource Linear Display

4.28.2.3 Combined Path Commands: Erase from Map

PATH:(Combined Path Query Tool-Erase fro Map)

This command allows the IPT NMS - Circuit operator to erase a Combined Pathfrom the map: doing so, all the routes from the system main window are deleted.

To erase a Combined Path from Map:

• Select the Erase from Map command from the Pop up menu.

This action only affects the graphical layout.

See Also:

View Menu: Erase Trail From Map

4.28.2.4 Combined Path Commands: Details

PATH:(Combined Path Query Tool-Details)

This command allows the IPT NMS - Circuit operator to display the informationabout the resources involved in the Combined Path: details are shown in aseparate window.

To display the details related to a Combined Path:



1171/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 63

The information displayed is:

• TC Operational State (Green/Yellow/Red)

• SNCP Status(only upon forced command)

• the Combined Path Name

• the Type

• the ASON State

• the Protection Type

• the Priority

• the WTR

• the Created on data field

• the Created by data field,

• the Routing Info (Type, Trail Diversity and Lambda),

118 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• the Client Info, that consists of the following information data related to thereferring ODU path:

• the Path Name and Type,

• the Path State,

• the Worker Colors,

• the Protection Colors,

• the Operational State (Enabled/Disabled),

• the WSON Operational State (Enabled/Disabled),

• the Trail Trace State,

• the Protection Type,

• the Protection State,

• the Routing Properties,

• the Routing information,

• the Worker information,

• the Protection information.

• the Control Plane Path List, that consists of the list of all the referringInside Control Plane OCH paths, each of them with the following informationdata:

• the LSP ID,

• the Role(original and actual)

• the Priority.

• the Outside Control Plane Path List, that consists of the list of all thereferring Outside Control Plane OCH paths, each of them with the followinginformation data:

• the Path Name and Type,

• the Path State,

• the Worker Colors,

• the Operational State(Enabled/Disabled),

• the WSON Operational State(Enabled/Disabled),

• the In Service State(Yes/No),

1191/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• the Trail Trace State,

• the Client Traffic Type,

• the ASTN Operational State(Enabled/Disabled),

• the Creation Data and the User Creator,

• the Routing information.




4.28.2.5 Combined Path Commands: Activate

PATH:(Combined Path Query Tool-Activate)

This command allows the IPT NMS - Circuit operator to activate a CombinedPath: doing so, all the referring paths are activated.

The result of this action is:

• all the OCH paths are activated;

• the client ODU path is activated automatically by the server and set inthe active state.

To activate a Combined Path:

• Select the Activate command from the Pop up menu.

A new window is displayed, showing the Combined Path selected.

Figure 64

120 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Press Apply.

See Also:

Combined Path Commands: Details

4.28.2.6 Combined Path Commands: Deactivate

PATH: (Combined Path Query Tool-Deactivate)

This command allows the IPT NMS - Circuit operator to deactivate a CombinedPath: doing so, all the referring paths are deactivated. The result of thisoperation is:

• the client ODU path is deactivated;

• all the OCH paths are deactivated.

To deactivate a Combined Path:

• Select the Deactivate command from the Pop up menu.


Figure 65

• Press Apply.

See Also:


4.28.2.7 Combined Path Commands: Modify

PATH:(Combined Path Query Tool-Modify)

1211/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the IPT NMS - Circuit operator to modify the mainparameters of Combined Paths with WSON state Enabled.

After selecting the command the Modify Combined Path window appears.

Figure 66

To modify the Combined Path parameters:

• Type in the Nametextboxthe new Combined Path name.

• Use the Priorityto select the priority level (modifiable only for CombinedPaths protected through Transponder Sharing).

• Use the WTR Timeto select the WTR (modifiable only for Combined Pathprotected through Safe protection or OSNCP protection or TransponderSharing in Reserved state).

• Press Apply.

See Also:


4.28.2.8 Combined Path Commands: Reroute

PATH:(Combined Path Query Tool-Reroute)

It allows the IPT NMS - Circuit operator to reroute only Combined Pathsprotected through Transponder Sharing protection, in Active state and withWSON state Enabled: through this command the IPT NMS - Circuit operator isable to select the LSP on which he wishes to switch the traffic.

To reroute a Combined Path:

122 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Select the Reroute command from the Pop up menu.

A new window is displayed, containing the list of the available LSPs: for each ofthem LSP id, Original Role and Priority are displayed.

Figure 67

• Select the LSP on which to switch the traffic.

• Press Reroute.

See Also:


4.28.2.9 Combined Path Commands: Read from Control Plane

PATH:(Combined Path Query Tool -Read from Control Plane)

This command allows the IPT NMS - Circuit operator to read, from theequipments, the actual values and configuration state of the parameters relatedto the Combined Path.

Eventually the IPT NMS - Circuit operator can perform the realignment ofthe Combined Path with the equipments (please refer to Combined PathCommands: Realign from Control Plane).

To Read from Control Plane:

• Select from the list the Combined Path(s) to be managed and then selectthe Read from Control Planecommandfrom the Pop up menu.

1231/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The following window is displayed, in the Paths area is present the list of theselected Combined Path(s).

Figure 68

• Select the Combined Path(s) to be managed.

A new window is displayed, containing the data, read from the equipments,related to the selected Combined Path(s).

• Press Updateto realign the Combined Path(s).

See Also:

Control Plane Configuration Wizard ,Combined Path Commands: Details

4.28.2.10 Combined Path Commands: Realign from Control Plane

PATH:(Combined Path Query Tool-Realign from Control Plane)

This command allows the IPT NMS - Circuit operator to realign the state of theCombined Path(s) with the equipments.

To Realign from Control Plane:

• Select from the list the Combined Path(s) to be managed and then selectthe Realign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Combined Path(s).

124 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 69

• Select the Combined Path(s) to be realigned.

• Press Applyto realign the Combined Path(s).

See Also:

Control Plane Configuration Wizard ,Combined Path Commands: Details

4.28.2.11 Combined Path Commands: Modify Protection

PATH: (Combined Path Query Tool-Protection-Modify)

This command allows the IPT NMS - Circuit operator to modify the switchparameter of a Combined Path protected through Safe/OSNCP protection.

In case of Combined Path protected through Transponder Sharing protection,the command is grayed out.

To switch the protection of a Combined Path:

• Select the Modify Protection command from the Pop up menu.


1251/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 70

• Select a suitable switching command among the following ones:

Clear

It resets the switching state. This is the default value selected, despite theactual protection state.

LockoutOc

It manually forces the combined path not to switch at all. Traffic remains onworker side if currently active. In case the currently active side is the protection,traffic switches back on worker.

Forced Switch Protection

It switches to the protection side (switching occurs also in presence of alarms).

• Press Apply.

See Also:


4.28.2.12 Combined Path Commands: Working Side

PATH:(Combined Path Query Tool-Protection-Working Side)

It allows the IPT NMS - Circuit operator to obtain the working side of aCombined Path protected through Safe protection or OSNCP protection.

To display the Combined Path working side:

• Select the protected combined path from the list

• Set the command from the Combined Path Query Tool Pop Up menu

• Press Apply.

126 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The Working Side report window is displayed.

Figure 71

The following information is displayed, for each of the two Nodes involved in theCombined Path, respectively From Node and To Node :

• Node Name

• Working Side

• Worker Port Name

• Protection Port Name

• Worker

• Protection

See Also:


4.28.2.13 Combined Path Commands: Enable

PATH:(Combined Path Query Tool-Enable)

This command allows the IPT NMS - Circuit operator to enable a CombinedPath.

To enable a Combined Path:

1271/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Select the Enable command from the Pop up menu


Figure 72

• Press Apply.

See Also:


4.28.2.14 Combined Path Commands: Disable

PATH:(Combined Path Query Tool-Disable)

This command allows the IPT NMS - Circuit operator to disable a CombinedPath.

Note: This command is prevented by the application upon forced command.

To disable a Combined Path:

• Select the Disable command from the Pop up menu


128 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 73

• Press Apply.

See Also:


4.28.2.15 Combined Path Commands: Disassociate

PATH:(Combined Path Query Tool-Disassociate)

This command allows the IPT NMS - Circuit operator to disassociate aCombined Path.

In case of Combined Path in Active state or Combined Path in Reserved statewith WSON state Disabled, besides the Combined Path all the referring pathsare disassociated:

• The client ODU path is disassociated;

• All the OCH paths are disassociated.

In case of Combined Path in Reserved state with WSON state Enabled, onlythe Combined Path is disassociated.

To disassociate a Combined Path:

• Select the Disassociate command from the Pop up menu.


1291/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 74

• Press Apply.

See Also:


4.28.2.16 Combined Path Commands: Remove

PATH:(Combined Path Query Tool-Remove)

This command allows the IPT NMS - Circuit operator to remove a CombinedPath, only if the Combined Path is in Reserved state: removing a CombinedPath, all the referring paths are not removed.

The command is grayed out if the Combined Path is not in Reserved state.

To remove a combined path:

• Select the Remove command from the Pop up menu.


130 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 75

• Press Apply.

See Also:


4.29 Control Plane Import Wizard

4.29.1 Control Plane Import Wizard: Window

PATH:(Configuration-WSON-Import Wizard)

The Control Plane Import Wizard is a tool that allows the user to import sometypology of Control Plane resources and Trails related to an Automatic SwitchedOptical Network, into IPT NMS - Circuit: successively these resources can bemanaged through the Control Plane Configuration Wizard tool (please refer toControl Plane Configuration Wizard).

The typologies of Control Plane resource that can be imported are the followingones:

• Label Switched Routers

• Adjacencies


• Link Clusters

• Link Components.

1311/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 76

When invocated, the Control Plane Import Wizard window displays the followingitems:

Files Area

A table displaying a list of XML files, such that a set of Control Plane resourcesand Trails is associated to each of them: the user can select one or more filesand successively import the associated resources. The table columns arerelated to the following XML files properties:

• File Name,

• Date,

• Size.

By clicking on the column header, the Files list is properly sorted.

Tabs Area

A set of tabs, through which the IPT NMS - Circuit operator can choose theresource typology to display in the Resources Area, after selecting an XML fileand imported the related resources:

• NE Protocols tab

• Adjacencies tab

132 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Control Channels tab

• Link Clusters tab

• Link Components tab

• Trails tab.

The Tab selection is exclusive: only one tab (the one related to the currentlyselected resource typology) is active.

Resources Area

A table displaying the list of the just imported resources, filtered on the resourcetypology, properly selected by the IPT NMS - Circuit operator in the Tabs Area.

The data fields related to the table columns are the following ones:

• Name

• Result

• Operation

• Failure Reason.

By clicking on the column header, the Resources list is properly sorted.

Message Area

A text box where messages about the performed actions appear.

GetFileList Button

This button allows the IPT NMS - Circuit operator to get the XML files list.

Import Button

This button allows the IPT NMS - Circuit operator to import the Control Planeresources related to the selected XML file.

Cancel Button

This button allows the IPT NMS - Circuit operator to close the window.

Help Button

This button allows the IPT NMS - Circuit operator to invoke the Online Helpfunctionality.

To import Control Plane resources:

• Press GetFileListto display the list of XML files.

1331/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 77

• Arrange the XML files list, if necessary, as described in:


• Using the mouse buttons, proceed with the selection of one or more items.

• Press Import to import the Control Plane resources related to the selectedXML files.

The window displays the information related to all the just imported resources.

134 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 78

See Also:

Introduction to ASTN-DD Management, Appendix: Common References

4.30 Control Plane Export Wizard

4.30.1 Control Plane Export Wizard: Window

PATH:(Configuration-WSON-Export Wizard)

The Control Plane Export Wizard is a tool that allows the user to export to a filesome typology of Control Plane resources and Trails related to an AutomaticSwitched Optical Network, currently loaded in IPT NMS - Circuit through theControl Plane Import Wizard tool (please refer to Control Plane ConfigurationWizard).

The typologies of Control Plane resource that can be exported are the followingones:


• Adjacencies


• Link Clusters

1351/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Link Components.

When invocated, the Control Plane Export Wizard window displays the followingitems:

Files Area

A table displaying a list of XML files, such that a set of Control Plane resourcesand Trails is associated to each of them: the user can select one of the files(or alternatively create a new file by properly setting the Name textbox) andsuccessively export to it the Control Plane resources and the Trails currentlyloaded in IPT NMS - Circuit. The table columns are related to the followingXML files properties:

• File Name,

• Date,

• Size.

By clicking on the column header, the Files list is properly sorted.

Name Textbox

A textbox where the can specify the name of the file to which he wants toexport the Control Plane resources and the Trails: if the IPT NMS - Circuit userselects a file in the Files Area, the name of the selected file appears in thetextbox and it is modifiable.

Message Area

A text box where messages about the performed actions appear.

Apply Button

This button allows the IPT NMS - Circuit operator to export to the selectedfile, the Control Plane resources and the Trails, currently loaded in IPT NMS -Circuit through the Control Plane Import Wizard tool.

Cancel Button


Help Button


136 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 79

To export Control Plane resources:

• Arrange the XML files list, if necessary, as described in:


• Using the mouse buttons, proceed with the selection of one item, therelated file name will appear in the Name textbox.

• Eventually insert the file name in the Name textbox.

• Press Apply to export the Control Plane resources.

If the file is already existent, a warning window appears: the can decide tooverwrite or not the file.

See Also:


4.31 Control Plane Configuration Wizard

4.31.1 Control Plane Configuration Wizard: Introduction

The Control Plane Configuration Wizard is a tool that allows the to manage theControl Plane resources related to an Automatic Switched Optical Network: theControl Plane resources can be imported into IPT NMS - Circuit through theImport Wizard tool (please refer to Control Plane Configuration Wizard).

Note: Just after the Label Switched Routers are configured, the NE TrapNotifications configuration must be performed at EM level. Using the SO EMGUI (Stop/Start NE), stop and then restart the EM communication to the NE.

1371/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Pay attention: until this operation is completed the Control Plane Objectstatus updates are not forwarded to IPT NMS - Circuit. To correctly retrievethe correct Control Plane Object status, please execute an ASON Discovery(Whole Network and then Controle Plane and Trail status discovery).

IPT NMS - Circuit deals with the following typologies of Control Plane resources:


• Adjacencies


• Link Clusters

• Link Components

• Combined Paths.

Since each typology is characterized by peculiars features and there arevarious association relationships between them, for each typology IPT NMS -Circuit provides specific commands. All the commands details are described inthe next sections.

See Also:


4.31.2 Control Plane Configuration Wizard: Window General Operation

PATH:(Configuration-WSON-Configuration Wizard)

The Control Plane Configuration Wizard window allows the IPT NMS - Circuitoperator to access to all the IPT NMS - Circuit functionalities related to themanagement and the browsing of the control plane resources, imported intoIPT NMS - Circuit.

Since IPT NMS - Circuit deals with different typologies of control planeresources, the application let the IPT NMS - Circuit operator manage thetypology resources in a specific way: so, the Control Plane ConfigurationWizard window can be displayed in different ways, according to the typology ofresources the IPT NMS - Circuit is managing.

This section describes the general structure of the Control Plane ConfigurationWizard window; some window items can be specific for each resource typology.

Through the Browsing Buttons, described below, the IPT NMS - Circuitoperator can select the typology of control plane resources he wants to manage:the commands the IPT NMS - Circuit operator can run on the displayed controlplane resources depend on the selected typology of control plane resource.

138 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 80

When invocated, the Control Plane Configuration Wizard window displays thefollowing items:

Browsing Tabs Area

A set of tabs, which give access to each typology of control plane resource:

• NE Protocols Configuration

• Adjacencies Configuration

• Control Channels Configuration

• Link Cluster Configuration

• Link Component Configuration

• Combined Path Configuration.

The Tab selection is exclusive: only one tab (the one related to the currentlyselected control plane resource typology) is active.

Query Results Area

1391/1551-1/AOM 901 084 Uen C2 | 2011-12-15


A table, displaying a list of control plane resources, characterized by thesame typology, in which each column gives particular information. The set ofcolumns and the set of the displayed control plane resources depend on thecontrol plane resource typology selected by the user. By clicking on the columnheader, the control plane resources list is properly sorted.

Result Area

A table displaying a list of commands, run on the control plane, in which eachcolumn gives particular information about the performed operation.

The data fields are the following:

• Name

• Result

• Operation

• Failure Reason

By clicking on the column header, the run commands list is properly sorted.

Message Area

A text box where messages about the various actions performed appears.

Browsing Buttons

A Back button and a Next button are displayed to allow the IPT NMS - Circuitoperator to browse the control plane resource typologies, in order to displaythe specific window. The browsing order is the one defined above for theBrowsing Tabs Area.

Cancel Button


Help Button


Refresh Button

This button allows the IPT NMS - Circuit operator to refresh the window.

Configure Buttons

Two buttons allow the IPT NMS - Circuit operator to configure Control PlaneResources:

140 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• The first allows the IPT NMS - Circuit operator to immediately configure allthe Control Plane Resources imported into IPT NMS - Circuit.

• The last allows the IPT NMS - Circuit operator to immediately configureonly the Control Plane Resources of the selected typology, imported intoIPT NMS - Circuit.

Every single Control Plane resources can be applied with specific commandsas above described. Before applying any command a resource selectionis necessary.

To select the Control Plane Resources and run a command on them:



• Using the mouse buttons, proceed with the selection of one or more items.

left button


middle button


right button


• Select the command to run, from the list shown by the Pop-up menu. Thecontent of the Pop-up menu depends on the type of Control Plane Resourceselected as well as on the configuration state. Moreover a certain pop-upmenu is given for single selection while another one is given for multipleselections, which makes available inquiry commands only. More details in:

Map Main Objects: Pop-up Menus


See Also:

Control Plane Configuration Wizard: Introduction

1411/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.3 Control Plane Configuration Wizard: NE Protocols Configuration


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Label Switched Routers.

The window items that characterize it are the following ones:

Browsing Tabs Area

Only the NE Protocols Configuration tab, that results in the first position inthe tabs sequence, is active.

Query Results Area

The columns characterizing the table containing the Label Switched Routerspresent in IPT NMS - Circuit, are related to the following fields:

• Name

• Type

• Short Name

• Suffix

• Router Id

• Routing Area

• Restore Phase

• Configurable

• Configured

Configure all LSRs Button

This button allows the IPT NMS - Circuit operator to configure all the LabelSwitched Routers present in IPT NMS - Circuit.

142 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 81

As previously described in the section Control Plane Configuration Wizard:Window General Operation the IPT NMS - Circuit operator can select onor more items in the Label Switched Router Query Results and successivelychoose the command to run, from the list shown by the Pop-up menu. Thecontent of the Pop-up menu depends on the configuration state of the selecteditems.

1431/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 82

Here is the list of the commands provided by IPT NMS - Circuit that we describein the next sections:

• Details

• Protocols State

• Modify

• Configure

• Deconfigure

• Remove

• Read from Control Plane

• Realign from Control Plane

See Also:

Control Plane Configuration Wizard: Window General Operation

144 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.3.1 NE Protocols Configuration Commands: Details

PATH:(NE Protocols Configuration Window-Details)

This command allows the IPT NMS - Circuit operator to display the informationabout the Label Switched Router in a separate window.

To display the details:

• Select from the list the Label Switched Router(s) and then select theDetailscommand from the Pop up menu.

Here are the displayed details, related to the Label Switched Routers:

• Name Information

• Routing Information

• Configuration Information

• Label Router Switched Information (RSVP, LMP, OSPF, Trap).


Figure 83

The operator is allowed to modify only a subset of the Label SwitchedRouter parameters. Please refer to the section NE Protocols ConfigurationCommands: Modify, where all the editable parameters are listed.




1451/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:


4.31.3.2 NE Protocols Configuration Commands: Protocols State

PATH:(NE Protocols Configuration Window-Protocols State)

This command allows the operator to display the information about theProtocols state related to the Label Switched Router in a separate window.

To get the Protocols State:

• Select from the list the Label Switched Router and then select theProtocols Statecommand from the Pop up menu.


Figure 84




See Also:


4.31.3.3 NE Protocols Configuration Commands: Modify

PATH:(NE Protocols Configuration Window-Modify)

146 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the operator to modify the Label Switched Routerparameters.

Changes are performed only on IPT NMS - Circuit database in case ofnot-configured resources, and on both DB and equipments in case ofconfigured resources. In case of error during configuration on equipment thesystem rollbacks the whole command.

To modify a Label Switched Router:

• Select from the list the Label Switched Router and then select theModifycommand from the Pop up menu.


Figure 85

This window contains the following tabs:

• RSVP

• LMP

1471/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• OSPF

Each of these tabs allows IPT NMS - Circuit to display a specific set ofparameters, that can be modified by the operator, while the Name, ShortNameand Suffix parameters are permanently displayed. The operator canactivate one tab exclusively, by default the RSVP tab is activated (as shown inthe previous window).

• Type in the Name, Short Nameand Suffixtextboxesthe new LabelSwitched Router name.

After activating the RSVP tab, the previous window is displayed.

• Type in the Refresh Interval textbox the new interval of messagesrefreshing.

• Type in the Retransmission Interval textbox the new retransmissioninterval of RSVP messages.

• Type in the Exponential Backup Delta textbox the new LSP exponentialbackup value in RSVP messages retransmission procedure.

• Type in the Purgetime textbox the new LSP Purging Time.

• Type in the ReoptimizationInterval textbox the new reoptimization interval.

• Type in the Retry Limit textbox the new LSP max number of RSVPmessages in retransmission procedure.

After activating the LMP tab, the following window is displayed:

148 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 86

• Use the TCP Keep Alive check button to set the TCP Keep AliveParameter.

• Type in the TCP Keep Alive Timeout textbox the new TCP Keep AliveTimeout value.

• Type in the DCN Mtu textbox the new MTU parameter value.

After activating the OSPF tab, the following window is displayed:

1491/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 87

Use the Force Zero check button to set the Force Zero parameter:

• by setting it to TRUE, the routing protocol on the LSR notifies to all theother resources that the LSR is unusable (all circuits already using theLSR are not affected by this setting),

• by setting it to FALSE the LSR behaves normally.

For each Priority interval, properly type in the Priority Value textboxes thenew Priority values.

Press Apply.

See Also:

Control Plane Configuration Wizard: Window General Operation ,Introduction to ASTN-DD Management, Appendix: Common References

150 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.3.4 NE Protocols Configuration Commands: Configure

PATH:(NE Protocols Configuration Window-Configure)

This command allows the operator to configure a Label Switched Router.

This command includes loopback CIT configuration. In case of error duringconfiguration on equipment the system rollbacks the whole command.

To configure a Label Switched Router:

• Select from the list the Label Switched Router(s) to be configured and thenselect the Configurefrom the Pop up menu.

Another item is inserted in the Result Area, containing the appropriateinformation related to the just run command, while the Message Area is filledwith a message related to the outcome of the command.

See Also:


4.31.3.5 NE Protocols Configuration Commands: Deconfigure

PATH:(NE Protocols Configuration Window-Deconfigure)

This command allows the operator to deconfigure a Label Switched Router.

This command cleans up WSON configuration on equipment. DeconfigureNode command is rejected by the system if there are any Adjacencies/ControlChannels configured on the node.

To deconfigure a Label Switched Router:

• Select from the list the Label Switched Router(s) to be deconfigured andthen select the Deconfigurefrom the Pop up menu.


See Also:


4.31.3.6 NE Protocols Configuration Commands: Remove

PATH:(NE Protocols Configuration Window-Remove)

This command allows the operator to remove the Label Switched Router.

1511/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command is grayed out if the Node WSON stack is still configuredon equipment. If there are any not-configured Adjacency/Control Channelassociated to the Node the remove command is propagated to all of them. Ifany circuit is still present on node, remove command is rejected.

To remove a Label Switched Router:

• Select from the list the Label Switched Router(s) to be removed and thenselect the Removefrom the Pop up menu.

A new window is displayed, showing the Label Switched Router selected.

Figure 88

• Press Apply.

See Also:


4.31.3.7 NE Protocols Configuration Commands: Read from Control Plane

PATH:(NE Protocols Configuration Window-Read from Control Plane)

This command allows the operator to read, from the equipment, the actualvalues and configuration state of the parameters related to the Label SwitchedRouter.

Eventually the operator can perform the realignment of the Label SwitchedRouter with the equipment (please refer to NE Protocols ConfigurationCommands: Realign from Control Plane).

Note: This command is not available for "UNMANAGED" Label Switch Router(the command is grayed out).


152 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Select from the list the Label Switched Router(s) to be managed and thenselect the Read from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Label Switched Router(s).

Figure 89

• Select the Label Switched Router(s) to be managed.

A new window is displayed, containing the data, read from the equipment,related to the selected Label Switched Router(s).

Figure 90

• Press Updateto realign the Label Switched Router(s).

See Also:

1531/1551-1/AOM 901 084 Uen C2 | 2011-12-15



4.31.3.8 NE Protocols Configuration Commands: Realign from Control Plane

PATH:(NE Protocols Configuration Window-Realign from Control Plane)

This command allows the operator to realign the state of the Label SwitchedRouter with the equipment.

Note: This command is not available for "UNMANAGED" Label Switch Router(the command is grayed out).


• Select from the list the Label Switched Router(s) to be managed and thenselect the Realign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Label Switched Router(s).

Figure 91

• Select the Label Switched Router(s) to be realigned.

• Press Applyto realign the Label Switched Router(s).

See Also:


4.31.4 Control Plane Configuration Wizard: Adjacencies Configuration


154 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Adjacencies.


Browsing Tabs Area

Only the Adjacencies tab that results in the second position in the tabssequence, is active.

Query Results Area

The columns characterizing the table containing the Adjacencies present in IPTNMS - Circuit, are related to the following fields:

• Adjacencies Name

• Adjacencies Type

• Operational Status

• Configurable

• Configured

• Restore Phase

Configure all ADJs Button

This button allows the operator to configure all the Adjacencies present in IPTNMS - Circuit.

1551/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 92

As previously described in the section Control Plane Configuration Wizard:Window General Operation the operator can select on or more items in theAdjacency Query Results and successively choose the command to run, fromthe list shown by the Pop-up menu. The content of the Pop-up menu dependson the configuration state of the items selected.

156 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 93

Here is the list of the commands provided by IPT NMS - Circuit, that wedescribe in the next sections:

• Details

• Modify

• Configure

• Deconfigure

• Associated Link Clusters

• Associated Control Channels

• Remove



See Also:


4.31.4.1 Adjacencies Configuration Commands: Details

PATH:(Adjacencies Configuration Window-Details)

This command allows the operator to display the information about theAdjacency in a separate window.

1571/1551-1/AOM 901 084 Uen C2 | 2011-12-15



• Select from the list the Adjacency and then select the Detailscommandfrom the Pop up menu.

Here are the displayed details, related to the Adjacencies:

• Type Information

• The Adjacency Nodes Details.


Figure 94

The operator is allowed to modify only a subset of the Adjacency parameters.Please refer to the section Adjacencies Configuration Commands: Modify,where all the editable parameters are listed.




See Also:


4.31.4.2 Adjacencies Configuration Commands: Modify

PATH:(Adjacencies Configuration Window-Modify)

This command allows the operator to modify the Adjacency parameters.

158 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The modification affects the near and far end nodes representing theadjacencies. Change is performed only on IPT NMS - Circuit database in caseof not-configured resources, on both DB and equipments in case of configuredresources. In case of error during configuration on equipment, the systemrollbacks the whole command.

To modify an Adjacency:

• Select from the list the Adjacency and then select the Modifycommandfrom the Pop up menu.


Figure 95

• Type in the Nametextboxthe new Adjacency name.

• Type in the Retransmission Interval textbox, the new retransmissioninterval of protocol messages on Adjacency (this parameter can bemodified only if the Adjacency is not configured).

• Type in the Retry Limit textbox the new max retry number of protocolmessages on Adjacency (this parameter can be modified only if theAdjacency is not configured).

• Type in the Retransmission Delta textbox, the new retransmission backoffdelta of protocol messages on Adjacency (this parameter can be modifiedonly if the Adjacency is not configured).

• Press Apply.

See Also:

Control Plane Configuration Wizard: Window General Operation,Introduction to ASTN-DD Management, Appendix: Common References

1591/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.4.3 Adjacencies Configuration Commands: Configure

PATH:(Adjacencies Configuration Window-Configure)

This command allows the operator to configure an Adjacency.

Both two nodes on adjacency edges have to be in "configured" state, otherwisethe command is rejected by system. The Adjacency Configure commandaffects both near and far end nodes. In case of error during configuration onequipment the system rollbacks the whole command.

To configure an Adjacency:

• Select from the list the Adjacency to be configured and then select theConfigurecommand from the Pop up menu.


See Also:


4.31.4.4 Adjacencies Configuration Commands: Deconfigure

PATH:(Adjacencies Configuration Window-Deconfigure)

This command allows the operator to deconfigure an Adjacency.

This command cleans up Adjacency configuration on equipments. It is rejectedby the system if there are any LinkCluster/LinkComponent/ControlChannels/WSON Circuits configured on the adjacency, excluding RouterId Control Channel,which are automatically configured and deconfigured with adjacency.

To deconfigure an Adjacency:

• Select from the list the Adjacency to be deconfigured and then select theDeconfigurecommandfrom the Pop up menu.


See Also:


4.31.4.5 Adjacencies Configuration Commands: Associated Link Clusters

PATH:(Adjacencies Configuration Window-Associated Link Clusters)

160 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command performs a correlation between the selected Adjacency and theLink Clusters currently associated to it. The correlation is done by means of theLink Clusters Query tool window, which is invoked and pre-set to display theLink Clusters in its result area.

This command is defined in the document Introduction to ASTN-DDManagement, Appendix: Common References

To get the associated Link Clusters:

Select from the list the Adjacency to be managed and then select theAssociated Link Clusterscommandfrom the Pop up menu.

4.31.4.6 Adjacencies Configuration Commands: Associated Control Channels

PATH:(Adjacencies Configuration Window-Associated Control Channels)

This command performs a correlation between the selected Adjacency and theControl Channels currently associated to it. The correlation is done by meansof the Control Channel Query tool window, which is invoked and pre-set todisplay the Control Channels in its result area.


To get the associated Control Channels:

Select from the list the Adjacency to be managed and then select theAssociated Control Channelscommandfrom the Pop up menu.

4.31.4.7 Adjacencies Configuration Commands: Remove

PATH:(Adjacencies Configuration Window-Remove)

This command allows the operator to remove the Adjacency.

This command is grayed out if the adjacency is still configured on equipments.If there are any not-configured Link Cluster/Link Component/ControlChannels/WSON Circuits associated to the adjacency, excluding RouterIdControl Channel, the remove command is propagated to all of them. If somecircuit is still present on the Adjacency, remove command is rejected.

To remove an Adjacency:

• Select from the list the Adjacency to be removed and then select theRemovecommand from the Pop up menu.

A new window is displayed, showing the Adjacency selected.

1611/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 96

• Press Apply.

See Also:


4.31.4.8 Adjacencies Configuration Commands: Read from Control Plane

PATH:(Adjacencies Configuration Window-Read from Control Plane)

This command allows the operator to read, from the equipments, the actualvalues and configuration state of the parameters related to the Adjacency.

Eventually the operator can perform the realignment of the Adjacency with theequipments (please refer to Adjacencies Configuration Commands: Realignfrom Control Plane).

Note: This command is available only for "Not Applicable" adjacency type, inother cases the command is grayed out.


• Select from the list the Adjacencies to be managed and then select theRead from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Adjacencies.

162 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 97

• Select the Adjacencies to be managed.

A new window is displayed, containing the data, read from the equipments,related to the selected Adjacencies.

Figure 98

• Press Updateto realign the Adjacencies.

See Also:


4.31.4.9 Adjacencies Configuration Commands: Realign from Control Plane

PATH:(Adjacencies Configuration Window-Realign from Control Plane)

1631/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the operator to realign the state of the Adjacency withthe equipments.

Note: This command is available only for "Not Applicable" adjacency type, inother cases the command is grayed out.


• Select from the list the Adjacencies to be managed and then select theRealign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Adjacencies.

Figure 99

• Select the Adjacencies to be realigned.

• Press Applyto realign the Adjacencies.

See Also:


4.31.5 Control Plane Configuration Wizard: Control Channel Configuration


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Control Channels.


Browsing Tabs Area

164 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Only the Control Channel tab, that results in the third position in the tabssequence, is active.

Query Results Area

The columns characterizing the table containing the Control Channels presentin IPT NMS - Circuit, are related to the following fields:

• Name


• Type

• Forced Up

• Configurable

• Configured

• Restore Phase

Configure all CCs Button

This button allows the operator to configure all the Control Channels presentin IPT NMS - Circuit.

1651/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 100

As previously described in the section Control Plane Configuration Wizard:Window General Operation the operator can select on or more items in theControl Channel Query Results and successively choose the command to run,from the list shown by the Pop-up menu. The content of the Pop-up menudepends on the configuration state of the items selected.

166 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 101


• Details

• Modify

• Configure

• Deconfigure

• Associated Link Clusters

• Remove



See Also:


1671/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.5.1 Control Channel Configuration Commands: Details

PATH:(Control Channels Configuration Window-Details)

This command allows the operator to display the information about the ControlChannel in a separate window.


• Select from the list the Control Channel(s) and then select theDetailscommand from the Pop up menu.

Here are the displayed details, related to the Control Channels:

• Type Information

• Source General Information

• Destination General Information

• Protocols Information.


Figure 102

The operator is allowed to modify only a subset of the Label Switched Routerparameters. Please refer to the section Control Channel ConfigurationCommands: Modify, where all the editable parameters are listed.




168 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


See Also:


4.31.5.2 Control Channel Configuration Commands: Modify

PATH:(Control Channels Configuration Window-Modify)

This command allows the operator to modify the Control Channels parameters.

The modification affects the near and far end nodes representing the ControlChannel. Change is performed only on IPT NMS - Circuit database in case ofnot-configured resources, on both DB and equipments in case of configuredresources. In case of error during configuration on equipment the systemrollbacks the whole command.

To modify a Control Channel:

• Select from the list the Control Channel and then select theModifycommand from the Pop up menu.


1691/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 103

• Type in the Nametextboxthe new Control Channel name.

• Type in the Maximum Receivable Unittextboxthe new value of themaximum receivable unit parameter (Range is 512-1531, default valueis 1508).

• Type in the Restart Timertextboxthe new value of the restart timerparameter (Range is 1-255, default value is 3).

• Type in the Max Terminatetextboxthe new value of the max terminateparameter (Range is 1-255, default value is 2).

• Type in the Max Configuretextboxthe new value of the max configureparameter (Range is 1-255, default value is 10).

• Type in the Max Failuretextboxthe new value of the max failure parameter(Range is 1-255, default value is 5).

• Type in the Echo Timertextboxthe new value of the echo timer parameter(Range is 0-255, default value is 5).

170 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Type in the Echo Failure Thresholdtextboxthe new value of the echofailure threshold parameter (Range is 0-255, default value is 5).

• Type in the Configuration Intervaltextboxthe new retransmission intervalof CC Configuration messages on CC (set only during CC creation). Thisparameter can be modified only if the CC is not configured.

• Type in the Configuration Retry Limittextboxthe new max retry numberof CC Configuration messages on CC (set only during CC creation). Thisparameter can be modified only if the CC is not configured.

• Type in the ConfigurationRetransmission Delta textbox the newretransmission backoff delta of CC Configuration messages on CC (setonly during CC creation). This parameter can be modified only if the CC isnot configured.

• Type in the Hello Intervaltextboxthe new retransmission interval of Hellomessages on CC (set only during CC creation). This parameter can bemodified only if the CC is not configured.

• Type in the Hello Deadtextboxthe new timeout interval of Hello messageson CC (set only during CC creation). This parameter can be modified onlyif the CC is not configured.

• Type in the Restart Timetextboxthe interval to wait before restarting CC(set only during CC creation). This parameter can be modified only if theCC is not configured.

• Press Apply.

See Also:

Control Plane Configuration Wizard: Window General Operation,Introduction to ASTN-DD Management, Appendix: Common References

4.31.5.3 Control Channel Configuration Commands: Configure

PATH:(Control Channel Configuration Window-Configure)

This command allows the operator to configure a Control Channel.

The associated adjacency have to be in "configured" state, otherwise thecommand is refused by system. The Control Channel Configure commandaffects both near and far end nodes. The sequence of commands includesDCC creation and CIT configuration. In case of error during configuration onequipment the system rollbacks the whole Control Channel Creation commandon both nodes.

The RouterId Control Channels are automatically configured when the relatedLSPs are configured.

1711/1551-1/AOM 901 084 Uen C2 | 2011-12-15


An indirect Control Channel can be configured only if the associated p2p (PointTo Point) Control Channel is already configured, otherwise the command isrefused by the IPT NMS - Circuit.

To configure a Control Channel:

• Select from the list the Control Channel(s) to be configured and then selectthe Configurefrom the Pop up menu.


See Also:


4.31.5.4 Control Channel Configuration Commands: Deconfigure

PATH:(Control Channel Configuration Window-Deconfigure)

This command allows the operator to deconfigure a Control Channel.

This command cleans up Control Channel configuration on equipments. Itis not available for RouterId Control Channels, automatically configured anddeconfigured with adjacencies. Deconfigure Control Channel command isrejected by the system if there is any undirect Control Channel/Link Clusterconfigured on the Control Channel.

To deconfigure a Control Channel:

• Select from the list the Control Channel(s) to be deconfigured and thenselect the Deconfigurefrom the Pop up menu.


See Also:


4.31.5.5 Control Channel Configuration Commands: Associated Link Clusters

PATH:(Control Channel Configuration Window-Associated Link Cluster)

This command performs a correlation between the selected Control Channeland the Link Cluster currently associated to it. The correlation is done bymeans of the Link Cluster Query tool window, which is invoked and pre-set todisplay the Link Cluster in its result area.

172 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15



To get the associated Link Clusters:

Select from the list the Control Channel to be managed and then select theAssociated Link Clusterscommandfrom the Pop up menu.

4.31.5.6 Control Channel Configuration Commands: Remove

PATH:(Control Channel Configuration Window-Remove)

This command allows the operator to remove the Control Channel.

This command is grayed out if the Control Channel is still configured onequipments. If there is any not-configured undirected Control Channel/LinkCluster associated to the Control Channel, the remove command is propagatedto all the indirect Control Channels and detaches all the Link Clusters.

To remove a Control Channel:

• Select from the list the Control Channel(s) to be removed and then selectthe Removefrom the Pop up menu.

A new window is displayed, showing the Control Channel selected.

Figure 104

• Press Apply.

See Also:


1731/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.5.7 Control Channel Configuration Commands: Read from Control Plane

PATH:(Control Channel Configuration Window-Read from Control Plane)

This command allows the operator to read, from the equipments, the actualvalues and configuration state of the parameters related to the Control Channel.

Eventually the operator can perform the realignment of the Control Channel withthe equipments (please refer to Control Channel Configuration Commands:Realign from Control Plane).


• Select from the list the Control Channel(s) to be managed and then selectthe Read from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Control Channel(s).

Figure 105

• Select the Control Channel(s) to be managed.

A new window is displayed, containing the data, read from the equipments,related to the selected Control Channel(s).

174 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 106

• Press Updateto realign the Control Channel(s).

See Also:


4.31.5.8 Control Channel Configuration Commands: Realign from Control Plane

PATH:(Control Channel Configuration Window-Realign from ControlPlane)

This command allows the operator to realign the state of the Control Channelwith the equipments.


• Select from the list the Control Channel(s) to be managed and then selectthe Realign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Control Channel(s).

1751/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 107

• Select the Control Channel(s) to be realigned.

• Press Applyto realign the Control Channel(s).

See Also:


4.31.6 Control Plane Configuration Wizard: Link Cluster Configuration


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Link Cluster.


Browsing Tabs Area

Only the Link Cluster tab, that results in the fourth position in the tabs sequence,is active.

Query Results Area

The columns characterizing the table containing the Link Clusters present inIPT NMS - Circuit, are related to the following fields:

• Name


• Admin State

• "Edge" Type

176 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Configurable

• Configured

• Restore Phase

• OSPF Admin State

Configure all LKs Button

This button allows the operator to configure all the Link Clusters present inIPT NMS - Circuit.

Figure 108

As previously described in the section Control Plane Configuration Wizard:Window General Operation the operator can select on or more items in theLink Cluster Query Results and successively choose the command to run, fromthe list shown by the Pop-up menu. The content of the Pop-up menu dependson the configuration state of the items selected.

1771/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 109


• Details

• Modify

• Configure

• Deconfigure

• Lock

• Unlock

• Associated Control Channels

• Associated Link Components

• Associated Circuits

• Remove

178 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15




See Also:


4.31.6.1 Link Cluster Configuration Commands: Details

PATH:(Link Clusters Configuration Window-Details)

This command allows the operator to display the information about the LinkCluster in a separate window.


• Select from the list the Link Cluster(s) and then select the Detailscommandfrom the Pop up menu.

Here are the displayed details, related to the Link Clusters:

• General Information

• Protocols Information

• Edge Link Cluster Information

• Traffic Engineering Information.


Figure 110

1791/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The operator is allowed to modify only a subset of the Label SwitchedRouter parameters. Please refer to the section Link Cluster ConfigurationCommands: Modify, where all the editable parameters are listed.




See Also:


4.31.6.2 Link Cluster Configuration Commands: Modify

PATH:(Link Cluster Configuration Window-Modify)

This command allows the operator to modify the Link Cluster parameters.

The modification affects the near and far end nodes representing the LinkCluster. Change is done only on IPT NMS - Circuit database in case ofnot-configured resources, on both DB and equipments in case of configuredresources. In case of error during configuration on equipment, the systemrollbacks the whole command.

To modify a Link Cluster:

• Select from the list the Link Cluster and then select the Modifycommandfrom the Pop up menu.


Figure 111

180 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Type in the Nametextboxthe new Link Cluster name.

• Type in the Retransmission Interval textbox, the new retransmissioninterval of link summary messages (set only during LK creation). Thisparameter can be modified only if the LK is not configured.

• Type in the Retry Limit textbox the new max retry number of link summarymessages (set only during LK creation). This parameter can be modifiedonly if the LK is not configured.

• Type in the Retransmission Delta textbox the new retransmission backoffdelta of link summary messages(set only during LK creation). Thisparameter can be modified only if the LK is not configured.

• Press Apply.

See Also:


4.31.6.3 Link Cluster Configuration Commands: Configure

PATH:(Link Cluster Configuration Window-Configure)

This command allows the operator to configure a Link Cluster: the associatedadjacency and Control Channels have to be in Configured state, otherwisethe command is refused by system.

The Link Cluster Configure command affects both near and far end nodes.The sequence of commands sent to nodes includes Link Cluster associationto Control Channels.

In case of error, during configuration of Link Cluster on equipment, the systemrollbacks the whole command. Otherwise if Link cluster creation on ControlPlane is completed with at least one Control Channel, and some ControlChannel association fails, the Link Cluster is put in partially configured state andonly failed command is rolled-back. Information about command completionstatus is stored on DB map, in order to be able to complete configuration byexecuting only missing steps.

To configure a Link Cluster:

• Select from the list the Link Cluster(s) to be configured and then select theConfigurefrom the Pop up menu.


See Also:

1811/1551-1/AOM 901 084 Uen C2 | 2011-12-15



4.31.6.4 Link Cluster Configuration Commands: Deconfigure

PATH:(Link Cluster Configuration Window-Deconfigure)

This command allows the operator to deconfigure a Link Cluster.

This command detaches Link Cluster from Control Channels and cleans up LinkCluster configuration on equipments. Deconfigure Link Cluster command isrejected by the system if there are Link Component/WSON Circuits configuredon the Link Cluster.

To deconfigure a Link Cluster:

• Select from the list the Link Cluster(s) to be deconfigured and then selectthe Deconfigurefrom the Pop up menu.


See Also:


4.31.6.5 Link Cluster Configuration Commands: Lock

PATH:(Link Cluster Configuration Window-Locking State-Lock)

According to this setting the link cluster is excluded (Locked) from the IPT NMS- Circuit routing calculation, performed by the ASON Control Plane.

After the link cluster is locked a procedure to empty it for network maintenancescope can be applied. See:

Introduction to ASTN-DD Management: Commands After Setting TheLocking State

To lock a Link Cluster:

• Select from the list the Link Cluster(s) to be locked and then select theLockfrom the Pop up menu.


182 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 112

• Press Apply.


Figure 113

• Press Yesto confirm.

See Also:


4.31.6.6 Link Cluster Configuration Commands: Unlock

PATH:(Link Cluster Configuration Window-Locking State-Unlock)

According to this setting the link cluster is included (Unlocked) from the IPTNMS - Circuit routing calculation, performed by the ASON Control Plane.

After the link cluster is unlocked a procedure to restore the original trafficrouting can be applied.

To unlock a Link Cluster:

• Select from the list the Link Cluster(s) to be unlocked and then select theUnlockfrom the Pop up menu.

1831/1551-1/AOM 901 084 Uen C2 | 2011-12-15



Figure 114

• Press Apply.


Figure 115

• Press Yesto confirm.

See Also:


4.31.6.7 Link Cluster Configuration Commands: Associated Control Channels

PATH:(Link Cluster Configuration Window-Associated Control Channels)

This command performs a correlation between the selected Link Cluster andthe Control Channels currently associated to it. The correlation is done bymeans of the Control Channel Query tool window, which is invoked and pre-setto display the Control Channels in its result area.


To get the associated Control Channels:

184 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Select from the list the Link Cluster to be managed and then select theAssociated Control Channelscommandfrom the Pop up menu.

4.31.6.8 Link Cluster Configuration Commands: Associated Link Components

PATH:(Link Cluster Configuration Window-Associated Control Channels)

This command performs a correlation between the selected Link Cluster andthe link components associated to it. The correlation is done by means of theLink Component Query tool window, which is invoked and pre-set to display theLink Components in its result area.


To get the associated Link Components:

Select from the list the Link Cluster to be managed and then select theAssociated Link Componentscommandfrom the Pop up menu.

4.31.6.9 Link Cluster Configuration Commands: Associated Circuits

PATH:(Link Cluster Configuration Window-Associated Circuits)

This command performs a correlation between the selected Link Cluster andthe Circuit that runs through it. The correlation is done by means of the CircuitQuery tool window, which is invoked and pre-set to display the circuit in itsresult area.


To get the associated Circuits:

Select from the list the Link Cluster to be managed and then select theAssociated Circuitscommandfrom the Pop up menu.

4.31.6.10 Link Cluster Configuration Commands: Remove

PATH:(Link Cluster Configuration Window-Remove)

This command allows the operator to remove the Link Cluster.

This command is grayed out if the Link Cluster is still configured on equipments.If there are any not-configured Link Component/WSON Circuits associated tothe Link Cluster, the remove command is propagated to all them. If some circuitis still present on Link Cluster, the remove command is rejected.

To remove a Link Cluster:

1851/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Select from the list the Link Cluster(s) to be removed and then select theRemovefrom the Pop up menu.

A new window is displayed, showing the Link Cluster selected.

Figure 116

• Press Apply.

See Also:


4.31.6.11 Link Cluster Configuration Commands: Read from Control Plane

PATH:(Link Cluster Configuration Window-Read from Control Plane)

This command allows the operator to read, from the equipments, the actualvalues and configuration state of the parameters related to the Link Cluster.

Eventually the operator can perform the realignment of the Link Cluster withthe equipments (please refer to Link Cluster Configuration Commands:Realign from Control Plane).

Note: This command is available only for "Not Applicable" edge type, in othercases the command is grayed out.


• Select from the list the Link Cluster(s) to be managed and then select theRead from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Link Cluster(s).

186 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 117

• Select the Link Cluster(s) to be managed.

A new window is displayed, containing the data, read from the equipments,related to the selected Link Cluster(s).

Figure 118

• Press Updateto realign the Link Cluster(s).

See Also:


4.31.6.12 Link Cluster Configuration Commands: Realign from Control Plane

PATH:(Link Cluster Configuration Window-Realign from Control Plane)

1871/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the operator to realign the state of the Link Cluster withthe equipments.



• Select from the list the Link Cluster(s) to be managed and then select theRealign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Link Cluster(s).

Figure 119

• Select the Link Cluster(s) to be realigned.

• Press Applyto realign the Link Cluster(s).

See Also:


4.31.7 Control Plane Configuration Wizard: Link Component Configuration


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Link Components.


Browsing Tabs Area

188 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Only the Link Component tab, that results in the fifth position in the tabssequence, is active.

Query Results Area

The columns characterizing the table containing the Link Components presentin IPT NMS - Circuit, are related to the following fields:

• Name


• Correlated

• Link Cluster

• Forced Up

• Configurable

• Configured

• Restore Phase

Configure all CCs Button

This button allows the operator to configure all the Link Components presentin IPT NMS - Circuit.

1891/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 120

As previously described in the section Control Plane Configuration Wizard:Window General Operation the operator can select on or more items in theLink Component Query Results and successively choose the command to run,from the list shown by the Pop-up menu. The content of the Pop-up menudepends on the configuration state of the selected items.

190 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 121


• Details

• Configure

• Deconfigure

• Remove



See Also:


4.31.7.1 Link Component Configuration Commands: Details

PATH:(Link Component Configuration Window-Details)

1911/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the operator to display the information about the LinkComponent in a separate window.


• Select from the list the Link Component(s) and then select theDetailscommand from the Pop up menu.

Here are the displayed details, related to the Link Clusters:

• General Information

• Source Information

• Destination Information.


Figure 122

The operator is allowed to modify only a subset of the Label Switched Routerparameters. Please refer to the section Link Component ConfigurationCommands: Modify, where all the editable parameters are listed.




See Also:


192 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.31.7.2 Link Component Configuration Commands: Modify

PATH:(Link component Configuration Window-Modify)

This command allows the operator to modify the Link Component.

To modify a Link Component:

• Select from the list the Link Component and then select theModifycommand from the Pop up menu.

A new window is displayed.

Figure 123

• Type in the Nametextboxthe new Link Component name.

• Press Apply.

See Also:


4.31.7.3 Link Component Configuration Commands: Configure

PATH:(Link Component Configuration Window-Configure)

This command allows the operator to configure a Link Component: theassociated Link Cluster has to be in Configured or Partially Configured state,otherwise the command is refused by the system.

When a Protection Group is created between two tributary ports, it is notpossible to configure the Link Component of the slave port: an error messageis displayed.

The Link Component Configure command affects both near and far end nodes.The sequence of commands sent to nodes includes Link Component insertionin specified Link Cluster.

In case of error during LC configuration on equipments, the system rollbacksthe whole command.

1931/1551-1/AOM 901 084 Uen C2 | 2011-12-15


To configure a Link Component:

• Select from the list the Link Component(s) to be configured and then selectthe Configurefrom the Pop up menu.


See Also:


4.31.7.4 Link Component Configuration Commands: Deconfigure

PATH:(Link Component Configuration Window-Deconfigure)

This command allows the operator to deconfigure a Link Component.

This command removes Link Component from associated Link Cluster andcleans up Link Component configuration on equipments. Deconfigure LinkComponent command is rejected by the system if there are WSON Circuitsactive on the Link Component.

To deconfigure a Link Component:

• Select from the list the Link Component(s) to be deconfigured and thenselect the Deconfigurefrom the Pop up menu.


See Also:


4.31.7.5 Link Component Configuration Commands: Remove

PATH:(Link Component Configuration Window-Remove)

This command allows the operator to remove the Link Component.

This command is grayed out if the Link Component is still configured onequipments. If there are some reserved WSON Circuits associated to the Linkcomponent, the remove command is rejected.

To remove a Link Component:

• Select from the list the Link Component(s) to be removed and then selectthe Removefrom the Pop up menu.

194 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


A new window is displayed, showing the Link Cluster selected.

Figure 124

• Press Apply.

See Also:


4.31.7.6 Link Component Configuration Commands: Read from Control Plane

PATH:(Link Component Configuration Window-Read from Control Plane)

This command allows the operator to read, from the equipments, the actualvalues and configuration state of the parameters related to the Link Component.

Eventually the operator can perform the realignment of the Link Component withthe equipments (please refer to Link Component Configuration Commands:Realign from Control Plane).



• Select from the list the Link Component(s) to be managed and then selectthe Read from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Link Component(s).

1951/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 125

• Select the Link Component(s) to be managed.

A new window is displayed, containing the data, read from the equipments,related to the selected Link Component(s).

Figure 126

• Press Updateto realign the Link Component(s).

See Also:


4.31.7.7 Link Component Configuration Commands: Realign from Control Plane

PATH:(Link Component Configuration Window-Realign from ControlPlane)

196 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


This command allows the operator to realign the state of the Link Componentwith the equipments.



• Select from the list the Link Component(s) to be managed and then selectthe Realign from Control Planecommandfrom the Pop up menu.

The following window is displayed, in the Paths area is present the list of theselected Link Component(s).

Figure 127

• Select the Link Component(s) to be realigned.

• Press Applyto realign the Link Component(s).

See Also:


4.31.8 Control Plane Configuration Wizard: Combined Path Configuration


The Control Plane Configuration Wizard, as previously described, provides aspecific window for the management of the Combined Paths.

Differently from the windows related to the other Control Plane resources, noConfigure button is present in this window since no Configure/Deconfigureoperation is defined for the Combined Path.


1971/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Browsing Tabs Area

Only the Combined Path tab, that results in the sixth position in the tabssequence, is active.

Query Results Area

The columns characterizing the table containing the Combined Paths present inIPT NMS - Circuit, are related to the following fields:

• Name

• Type

• Path State

• TC Operational State

• Protection

• Ason State

• Restore Phase

Figure 128

198 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


As previously described in the section Control Plane Configuration Wizard:Window General Operation the operator can select on or more items in theCombined Path Query Results and successively choose the command to run,from the list shown by the Pop-up menu. The content of the Pop-up menudepends on the state of the selected items.

Figure 129

Here is the list of the commands provided by IPT NMS - Circuit that are theones defined in Combined Path operations related to the management ofthe Combined Path resources:

• Show Path on Map

• Linear Display

• Erase from Map

• Details

• Activate

• Deactivate

• Modify

1991/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Reroute



• Working Side

• Modify Protection

• Enable

• Disable

• Disassociate

• Remove

See Also:


4.32 Additional Path Operation

4.32.1 Additional Path Command

4.32.1.1 Path Commands: Prepare Combined Path

PATH:(Path Query Tool-Prepare Combined Path)

This command allows the operator to prepare a Combined Path, starting froman ODU Path.

This command can be activated only if the selected ODU Path and the relatedOCH paths are in Active state: the resulting Combined Path will be in Activestate and with WSON state Disabled.

Note: IPT NMS - Circuit prevents the Prepare command on a Combined Path ifan OTU Trail Trace is configured on it.

To prepare a Combined Path:

• Select the Prepare Combined Path command from the Pop up menu.

A new window is displayed, showing the ODU Path selected.

200 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 130

• Press Apply

See Also:

Combined Path Commands: Details , Path Commands

4.33 Control Plane Real Time Monitor

4.33.1 Control Plane Real Time Monitor: Window General Operation

PATH:(Management-Control Plane Alarms)

The Control Plane Real Time Monitor is a tool that allows the to manage thealarms traps related to the Control Plane resources of an Automatic SwitchedOptical Network.

When invocated, the following window is displayed:

2011/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 131

This window is made up of the following items:

Buttons Area

The provided buttons allow the operator to define and manage filtering criteria,named Templates, on the set of Alarm Traps he wants to manage in theMonitor Area.

Figure 132

Monitor Area

A table containing alarms traps is displayed, the operator can select one ormore than one of them and activate the commands we successively describe.

4.33.2 Control Plane Real Time Monitor: Buttons Area


On the upper left corner of the window, a small button section is provided, withthe following buttons, that are necessary to define and manage Templates(filtering criteria) on the set of the Alarm Traps, the operator wants to manage inthe Monitor Area:

Show Filter Button

This button opens and closes an additional part of the Window, which displaysall the criteria the operator can define in order to filter the set of the Alarm Traps.

202 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 133

When invocated, the following additional part of the window is displayed:

Figure 134

The filtering criteria are related to the following data fields:

• Resource Name

• Resource Type

• Last Event

• Severity


Export Button

This button allows the operator to export into a file the data contained in theMonitor Area table.

Figure 135

Counter Less Button

This button allows the operator to hide the previously defined counter items.

2031/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 136

Counter More Button

This button allows the operator to display the previously defined counter items.

Figure 137

When invocated, the window layout is updated like this:

Figure 138

Add Counter Button

This button allows the operator to define counter items on the set of themanaged Alarm Traps.

Figure 139

When invocated, the following window is displayed:

204 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 140

The operator can define Counter Items, by setting the following parameters:

• Counter Name

• Color

• Text properties

Save Template Button

This button allows the operator to save Templates (filtering criteria).

Figure 141

Load Template Button

This button allows the operator to load Templates (filtering criteria), previouslysaved.

Figure 142

See Also:

Control Plane Real Time Monitor: Window General Operation

4.33.3 Control Plane Real Time Monitor: Monitor Area


2051/1551-1/AOM 901 084 Uen C2 | 2011-12-15


In this area a table containing Alarm Traps is displayed. The columnscharacterizing the table are related to the following fields:

• Acknowledge Flag

• Event ID

• Resource Name

• Date and Time

• Resource Type

• Last Event

• Severity

• Operational State.

Before running any command on Alarm Traps, the operator can perform afiltering phase by properly invoking the buttons provided by the Buttons Area.

To select the Alarm Traps and run a command on them:



• Using the mouse buttons, proceed with the selection of one or more AlarmTraps.

left button


middle button


right button


• Select the command to run, from the list shown by the Pop-up menu.Moreover a certain pop-up menu is given for single selection whileanother one is given for multiple selections, which makes available inquirycommands only.

206 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 143



See Also:

Control Plane Real Time Monitor: Window General Operation

4.33.3.1 Monitor Area Commands: Details

PATH:(Management-Control Plane Alarms-Details)

This command allows the operator to display the information about the AlarmTrap in a separate window.

To display the alarm trap details:


Here are the displayed details, related to the Alarm Trap:

• Acknowledge Flag

• Event ID

• Resource Name

• Date and Time

• Resource Type

• Last Event

2071/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• Severity


Figure 144

• Press Save as...to save the details information.


See Also:

Control Plane Real Time Monitor: Monitor Area

4.33.3.2 Monitor Area Commands: Remove

PATH:(Management-Control Plane Alarms-Remove)

This command allows the operator to remove Alarm Traps from the MonitorArea.

To remove the alarm trap:

• Select the Removecommand from the Pop up menu.

The window layout is properly updated.

See Also:


4.33.3.3 Monitor Area Commands: Acknowledge

PATH:(Management-Control Plane Alarms-Acknowledge)

This command allows the operator to set/reset the Acknowledge data field.

To acknowledge the alarm trap

• Select the Acknowledgecommand from the Pop up menu.

208 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


The window layout is properly updated.

See Also:


4.34 Restoration Monitor

4.34.1 Restoration Monitor Window: Menu Bar and Main Commands

PATH:(Management-Restoration)

The commands below can be applied on the Combined Path resource typeand are available on the main menu and right click menu of the RestorationMonitor Window.

Figure 145

• List of Alarmed Paths -Display of the list of alarmed paths associated toa restoration protected Combined Path, on which is possible to run theactions List of Alarmed Links and Correlate to EM.

• Display -Display of the restorable Combined Path on Map area.

• Display Linearized -Linearized display of a restorable Combined Path(launches a new window).

Please refer to the Guide for the complete description of the Restoration andthe actions Display and Display Linearized.

See Also:

Restoration Management

2091/1551-1/AOM 901 084 Uen C2 | 2011-12-15


4.34.1.1 Restoration Monitor Window: List of Alarmed Paths

PATH:(Resource-List of Alarmed Paths)

This command allows the operator to display the list of all the alarmed pathsrelated to a Combined Path involved in a IPT NMS - Circuit failure: for eachpath the actions List of Alarmed Links and Correlate To EM are available.

To get the Alarmed Paths related to a Combined Path:

• Select the Alarmed Combined Path to manage.

• Select the option Resource-List of Alarmed Pathsfrom the menu bar.Alternatively, use the mouse to point at the row of interest; then, right clickto launch the pop-up menu that contains this option.

The following window is displayed; containing the list of the associated alarmedpaths, such that for each of them the following actions are available (pleaserefer to the Guide for the complete description):

• Correlate to EM

• List of Alarmed Links

• Details

• Show Alarmed Links.

Figure 146

See Also:

210 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Restoration Monitor Window: Menu Bar and Main Commands ,RestorationManagement

4.35 Backup and Restore Procedure on WSON Nodes

The complete Backup and Restore Procedure for WSOn nodes is reported inthe MHL3000 User Documentation collection.

2111/1551-1/AOM 901 084 Uen C2 | 2011-12-15


212 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Appendix: Common References

5 Appendix: Common References

This chapter provides a general description of the Control Plane main objectsdefinition and ASTN DD Standard References.

5.1 ASON: Control Plane Configuration and Main Objects

The ASON concepts and parameters that need to be configured are brieflydescribed in the following.

See Also:

What is the ASTN, Usage of the Graphical Interface

5.1.1 Adjacencies

A generic telecommunication network may be considered in general as aninterconnected mesh of network elements, also indicated with the term of"node" .

Two nodes are adjacent when there is a direct connectivity between them.

The presence of one or several link induces the presence of an adjacency.As an adjacency is a topological concept, there can be only one adjacencybetween two nodes that may contain any number of links.

See Also:


5.1.2 Link Cluster (LK)

An adjacency may be implemented with a single or with more physicalconnections, indicated with the general term "Link" , or, in ASTN, "LinkComponent" (LC).

For convenience (reducing computation time running automatic path selectionalgorithms, reducing the number of objects to be advertised by routingprotocols, and so on) the links within the same adjacency can be grouped intoLink Clusters. Each Link Cluster models links that share the same attributes.

The common attributes that a Link Component must have in order to be inthe same LK are:

• The same TNEs as and-points; therefore they must be inside the sameadjacency.

2131/1551-1/AOM 901 084 Uen C2 | 2011-12-15


• The same Link Type (for example point-to-point, multicast)

• The same TE metric (that is the administrative cost used by the pathselection engine to compute the cost of a circuit passing through that link).

• The same set of SRLGs (see below for the definition of SRLG).

• The same Switching Capability (PSC-x | L2SC | TDM | LSC | FSC).

• The same Encoding Type (SDH | Dig. Wrapper | Lambda | Fibre)

• The same Protection Type

• The same numbering Type (IPv4 | IPv6 | unnumbered)

• The same technological specific multiplexing capabilities

• The same technological specific concatenation capabilities

Therefore, in general, inside a Link Cluster there are homogeneous types ofports interconnecting the same couple of nodes and sharing the same physicalpath/conduit in the network.

Figure 147

Figure 1 Link Cluster Definition

214 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


In order to be used a LK need to be associated to at least one CC (see belowthe section related to Control Channels) in Up state. More than one CC can beassociated to the same LK.

See Also:


5.1.3 Shared Risk Link Group (SRLG)

Two or more link clusters belong to the same SRLG if they share some failurerisk (for example the same conduit, the same fiber, the same regenerator oroptical system). In general a risk is an object which may be subject to failure,affecting more than one link cluster at the same time. All the link clusterssharing that object, may be assigned an SRLG identifier to indicate that if/whenthe object related to that SRLG will fail, all the link clusters having the relevantSRLG identifier will fail as well. SRLG is a Link Cluster (LK) attribute.

The SRLG concept is used for diversity routing during protected path set-up. Alink can belong to more than one SRLG (for example Link 2 belongs to SRLGC and SRLG B) as shown in the following picture.

Figure 148

2151/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Figure 2 SRLG Definition

See Also:


5.1.4 Link Component (LC)

A LK is made of one or more Link Components. A LC is a bi-directional link andis identified by a LC-Id. This identifier is in our case an unnumbered address(that is an unsigned 32 bit integer number).

See Also:


5.1.5 Network Components Relationships

A summarization of the relationships between adjacency, LK, LK and Channelsis provided in the following picture.

Figure 149

Figure 3 Adjacency, LK, LC and Timeslot relationships

See Also:

216 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15



5.1.6 Control Channel (CC)

Control Channels are communication channels used in order to transportControl Plane packets, that is, packets originated by the following protocols:

• LMP;

• GRSVP-TE;

• GOSPF-TE.

Control Channels may be of two kinds:

• Point-to-point CC.

This kind of control channels are configured over point-to-point connectionsacross optical fibers. They are supported by DCC-based physical connections.DCC-m is the preferred option for this kind of CCs, due to their higher bandwidthand the possibility to bypass non-ASTN network elements link photonics orregenerators.

• Integrated IS-IS routed a.k.a NodeId CC;

This kind of control channels are configured using the NodeId address of theTNE. They are supported by DCC-based physical connections. DCC-r is thepreferred option for this kind of CCs, due to the fact that integrated IS-IS runsover DCCr.

See Also:


5.1.7 Control Interface (CIT)

A CC can be set between a pair of Control Interface (CIT), a couple of CITcan host only one CC.

CITs are created upon DCCx (x = m, r) or NodeId or Ethernet interface for outof band Control Plane.

NOTICE Out of band Control Plane is outside the scope of this description.

See Also:


2171/1551-1/AOM 901 084 Uen C2 | 2011-12-15


5.2 Standard References

For further information on the mentioned recommendations please refer tothe proper organization.

• European Telecommunication Standard EN 300 304 (March 1999),Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH)information model for the Network Element (NE) view.

• European Telecommunication Standard EN 300 371 (March 1999),Transmission and Multiplexing (TM); Plesiochronous Digital Hierarchy(PDH) information model for the Network Element (NE) view.

• ITU-T Recommendation X.738 (1993), Summarization Function

• ITU-T Recommendation G.774 (09/92), Synchronous Digital Hierarchy(SDH) Management Information Model for the Network Element View.

• ITU-T Recommendation G.774-02 (11/94), SDH Configuration of thePayload Structure for the Network Element View.

• ITU-T Recommendation G.774-03 (11/94), SDH Management of theMultiplex Section Protection for the Network Element View.

• ITU-T Recommendation G.774-04 (07/95), SDH Management ofSub-Network Connection Protection for the Network Element View.

• ITU-T Recommendation G.774-05 (07/95), SDH for the Sub-NetworkConnection Supervision Functionality (HCS/LCS) Network Element View.

• ITU-T Recommendation G.875 (1999), Wave Division Multiplexing (WDM)Management Information Model for the Network Element View

• ITU-T Recommendation X.721 (02/92), Open Systems InterconnectionStructure of Management Information: Definition of ManagementInformation, incorporating X.721/Cor.1 (1994).

• ITU-T Recommendation M.3100 (1995), Telecommunications ManagementNetwork: Generic Network Information Model.

• ITU-T Recommendation X.721 (1992), Open Systems InterconnectionStructure of Management Information: Definition of ManagementInformation

218 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15


5.3 Glossary and Acronyms

Table 1

ASON Automatically Switched OpticalNetwork, an optical networkimplementing an automatic controlplane

ASTN Automatically Switched TransportNetwork, a transport networkimplementing an automatic controlplane (generalization of ASON)

ATM Asynchronous Transfer Mode

CLNP Connection Less Network Protocol

Control Plane A function of a telecommunicationnetwork providing automaticconfiguration capabilities

DCN Data Communication Network, inSDH the network facilities to carrymanagement and control information

ERO Explicit Routing Object

E-NNI Exterior Network to Network Interface

GMPLS Generalized Multi Protocol LabelSwitching

IETF Internet Engineering Task Force

I-NNI Interior Network to Network Interface

ISO International Standards Organization

ITU-T International TelecommunicationUnion, TelecommunicationStandardization Sector

LMP Link Management Protocol

MIB Management Information Base

OTN Optical Transport Network

MS-SPRing Multiplex Section Shared ProtectionRing, an SDH technique for ringprotection

NMS Network Management System

OIF Optical Internetworking Forum

OSPF Open Shortest Path First

2191/1551-1/AOM 901 084 Uen C2 | 2011-12-15


Path Selection A function yielding a route givena topology and two access pointsrequesting connectivity on thattopology

Resource Quantitative information on atelecommunication network, such aslink bandwidth

RFC Request For Comments, the standardspecification document in IETF

Routing A function of a control plane providingthe capability to compute a route

RSVP Resource reSerVation Protocol

SDH Synchronous Digital Hierarchy

Signaling A function of a control plane providingthe capability to implement acomputed route

SNCP Sub Network Connection Protection,the most common SDH pathprotection scheme

SNMP Simple Network ManagementProtocol

TCP/IP Transport Control Protocol / InternetProtocol

TMN Telecommunication ManagementNetwork

Topology Qualitative information on atelecommunication network, suchas list of nodes, links and theirrelationships

Topology Discovery A function of a control plane providingthe capability of automaticallyretrieving topology information

UNI User to Network Interface

220 1/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Reference List

Reference List

[1] Marconi OMS 3200 - Rel. 5.2 - JCT Operating Procedures , 1/1543-CSA113 61/5 Uen

[2] Marconi OMS 3200 - Rel. 5.2 - ASTN -JCT Operating Procedures,3/1543-CSA 113 61/5 Uen

[3] IP Transport NMS - Circuit User Guide , 1/1553-AOM 901 084 Uen

[4] IP Transport NMS - Circuit System Administrator Guide , 1/1543-AOM901 084 Uen

[5] Marconi MHL 3000 R5.2 - JCT and JCTS Operating Procedures ,1543-CSA 113 62/52 Uen

2211/1551-1/AOM 901 084 Uen C2 | 2011-12-15

Documents

ASON Advantage Module