astn_jct operationg procedure

3/1543-CSA 113 61/5 Uen A

ASTN-JCT Operating ProceduresMarconi OMS 3200 Release 5.2.x

OPERATING INSTRUCTIONS

ASTN-JCT Operating Procedures Marconi OMS 3200 Release 5.2.x

3/1543-CSA 113 61/5 Uen A 07/31/2008

Refer to Title Page(s)

Page II Commercial in confidence

Since January 2006, Marconi is a member of the Ericsson group.

Copyright

© Ericsson AB and Marconi S.p.A 2006-2008 – All Rights Reserved

Disclaimer

No part may be reproduced, disclosed or used except as authorized by contract or other written permission. The copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied.

The information in this work is the property of Ericsson Limited. Except as specifically authorized in writing by Ericsson Limited, the receiver of this work shall keep the information contained herein confidential and shall protect the same in whole or in part from disclosure and dissemination to third parties. Disclosure and disseminations to the receiver's employees shall only be made on a strict need to know basis. The information in this work is subject to change without notice and Ericsson Limited assumes no responsibility for factual inaccuracies or typographical errors.

Ericsson Limited has used all reasonable endeavors to make sure that the information contained in this work is accurate at the release date but reserves the right to make changes, in good faith, to such information from time to time.

Trademarks

Ericsson and the Ericsson logo are trademarks of Telefonaktiebolaget LM Ericsson.

Acrobat(R) Reader copyright (C) 1987-1996 Adobe Systems Incorporated, - All rights reserved. Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

All trademarks and registered trademarks mentioned in a document of this collection are the property of their respective holders.


Document History

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page III Commercial in confidence

Document History

Issue Record

Issue Date System Release

02JCA00050BAY Issue 01 - 07/06 3.5

02JCA00050BAY Issue 02 - 11/06 3.5.2

02JCA00050CAV Issue 01 3/1543-CSA 113 61/3 Uen A 06/07 5.0.x

02JCA00050DAS Issue 01 3/1543-CSA 113 61/4 Uen A 11/07 5.1.x

- 3/1543-CSA 113 61/5 Uen A 07/08 5.2.x


Document History

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page IV Commercial in confidence

Reason for Updating

• Editorial Review;

• “System Requirements” updated;

• “Start the ASTN-JCT” updated;

• “One Shot Configuration” updated;

• “Add an Adjacent Node” updated;

• “Delete an Adjacent Node” updated;

• “Interfaces” updated;

• “Delete an interface” updated;

• “Reoptimization Time” updated;

• “GMPLS Ports” updated;

• “Tp Data” updated;

• “Link Cluster” updated;

• “Add a Link Cluster” updated;

• “Link Cluster Verification” updated;

• “Create a Link Component” updated;

• “Add a new Control Channel” updated;

• “Force Remove” added.


Contents

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page V Commercial in confidence

Contents

Document History III Issue Record III Reason for Updating IV Contents V 1 General Information 1 1.1 The ASTN-JCT Application 1 1.1.1 General Description 2 1.2 System Requirements 3 1.2.1 Hardware Composition 3 1.2.2 Software Composition (ASTN-JCT) 4 1.2.3 Software Installation (ASTN-JCT) 4 1.2.3.1 Personal Computer Version 4 1.2.3.2 Element Manager Version 5 1.2.4 Preliminary Configuration on the High Capacity SDH

Equipment 6 1.2.5 Start the ASTN-JCT 7 2 ASTN-JCT User Interface 9 2.1 Title Bar and Menu Bar 10 2.1.1 Tool Bar 10 2.1.1.1 Exit Button 10 2.1.1.2 Refresh Button 11 2.1.1.3 ZUI Button 11 2.1.1.4 Help Button 11 2.1.2 Status Bar 11 2.2 Menus 12 2.3 File 13 2.3.1 One Shot Configuration 13 2.3.2 ZUI Console 15 2.3.3 Exit 16 2.4 Configuration 17 2.4.1 Communication Settings 18 2.4.2 System 19 2.4.3 Router Id 20 2.4.4 Adjacent Nodes 21 2.4.4.1 Add an Adjacent Node 22 2.4.4.2 Edit an Adjacent Node 24 2.4.4.3 Delete an Adjacent Node 24 2.4.4.4 See the Adjacent Node Details 25 2.4.5 Interfaces 25 2.4.5.1 Add a new interface 26 2.4.5.2 Delete an interface 27 2.4.6 Protocols 28


Contents

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page VI Commercial in confidence

2.4.7 TE Policy 29 2.4.8 Priority Level 30 2.4.9 OSPF Parameters 31 2.4.10 Reoptimization Time 32 2.4.11 GMPLS Ports 33 2.4.11.1 Tp Data 34 2.5 View 36 2.5.1 Refresh 36 2.6 Link Management 37 2.6.1 Link Cluster 37 2.6.1.1 Add a Link Cluster 39 2.6.1.2 Delete a Link Cluster 41 2.6.1.3 Edit a Link Cluster 41 2.6.1.4 Link Cluster Verification 42 2.6.1.5 See the Link Cluster Details 44 2.6.2 Link Component 45 2.6.2.1 Create a Link Component 47 2.6.2.2 Delete a Link Component 48 2.6.3 Control Channels 48 2.6.3.1 Add a new Control Channel 50 2.6.3.2 Delete a Control Channel 53 2.6.3.3 Show the Link Cluster adopting the Control Channel 53 2.6.3.4 See the Control Channel Details 54 2.6.4 Associations 55 2.6.4.1 Force Remove 57 2.7 Trap Management 58 2.7.1 Trap Enable 59 2.7.2 Trap Configuration 60 2.7.2.1 Create a Target Mib 61 2.7.2.2 Delete a Target Mib 61 2.7.3 Trap Viewer 61 2.7.4 Trap Log Enable 62 2.7.5 Trap Log Configuration 63 2.8 HELP 63 2.8.1 About 63 3 ASTN-JCT Setting Procedure 64 3.1 Commissioning Procedure 64 3.2 How to add a new adjacency 65 3.3 How to remove an adjacency 67 3.4 Decommissioning Procedure 68 3.5 TE Link Cost 69 3.5.1 EXTRA_COST DEFINITION 70 3.5.2 K DEFINITION 70 4 SNMP Traps Description 72 4.1 ASTN Traps 73


Contents

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page VII Commercial in confidence

5 GMPLS Parameters in the OSI.ini file 78 5.1 OSI.ini Example 78 5.1.1 Parameters Meaning 80 5.1.1.1 [IP_CONFIG] 80 5.1.1.2 [IP_ISIS_CONFIG] 81 5.1.1.3 [IP_DCC_CONFIGURATION] 81


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008


Page 1 Commercial in confidence

1 General Information

In this chapter are given some preliminary information about the Java Craft Terminal SNMP for ASTN (JCTS-ASTN) application, managed functions, hardware and software requirements for its installation.

See Also: ASTN-JCT User Interface, ASTN-JCT Setting Procedure, SNMP Traps Description

1.1 The ASTN-JCT Application An Automatic Switched Transport Network (ASTN) is based on equipment supporting GMPLS protocol (Generalized Multi Protocol Label Switch).

GMPLS protocol has been developed to allow “element-driven” fast network restoration and routing.

This means that each NE (Network Element) could act as a router defining circuit path and recovery options autonomously, by integrating the information received from the Network Manager layer.

By means of this implementation, network resilience and disaster recovery times are significantly improved by network resource auto-discovery.

The mechanism ensures that optimal use of any connectivity available is made without a deeply involvement of the network operator.

The degree of control given to the elements is anyway under the full control of a central Network Manager to ensure that the traffic engineering requirements of individual carriers are met.

The GMPLS-NEs are Network Elements able to process the GMPLS protocol, and the connections between these equipments build the ASTN network.

In the following will be described the general features of the ASTN-JCT application. That is necessary to configure the advanced parameters of the GMPLS on the network elements; moreover, to define other used GMPLS parameters, it is necessary to download a configuration file “OSI.ini” into the NEs.

The ASTN-DD is the Automatic Switched Transport Network with Distributed routing and Distributed signaling, where the routing of the traffic in the network and the signaling for the creation/switch/deactivation of the circuit are distributed between all the GMPLS-NEs in the network.

See Also: General Information,


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



1.1.1 General Description

The existing Java Craft Terminal (JCT) is an application that is installed on the local PC and is ported into the Element Management platform. The current JCTs perform several management activities on a Network Element.

Most of its functionalities are extended to the Element Manager application, for a centralized management of the Network Elements.

The ASTN-JCT is an extension of the Equipment JCT for the management, via the SNMP, of the GMPLS parameters on the Network Element.

This application is necessary to configure the parameters of the network connections between the NEs and to route the traffic around the network with a routing protocol. To configure the Control Channels used by the NEs to communicate the routing information.

See Also: The ASTN-JCT Application


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



1.2 System Requirements In the following will be described the hardware and the software requirements of the ASTN-JCT application.

There exists a local version of the application to install on a PC and an add-on tool to the ServiceOn Optical Element Manager application.

See Also: General Information

1.2.1 Hardware Composition

The application operates on a Desktop Computer with the following suggested configuration.

CPU Intel® Pentium® III processor or equivalent

Monitor and VGA 1,024x768 screen resolution or higher

RAM 1GB RAM (minimum) – 2GB (suggested)

Hard Disk 100MB of available hard-disk space

Drive CD-ROM

- Keyboard, mouse and printer connections (PS2, parallel, USB) Interfaces and Peripherals

- Network Interface Card (Ethernet Interface)

The application operates also as an add-on version to the ServiceOn Optical Element Manager. In this case the hardware requirements are the same of the Element Manager application.

See Also: System Requirements

Refer to: ServiceOn Optical Element Manager Handbook


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



1.2.2 Software Composition (ASTN-JCT)

The software requirements of the application for the Desktop Computer are:

• WINDOWS XP™ Operating System

• Java Runtime Environment Installer 1.5 or upper (JRE are available on the Internet site www.java.com)

• Control Application Software (available on CD-ROM)

The software requirements of the application for the EM are the same of the ServiceOn Optical Element Manager.


1.2.3 Software Installation (ASTN-JCT)

Here in the follow the procedure to install the ASTN-JCT application with the two possibilities: for PC and for HP server (EM version).


1.2.3.1 Personal Computer Version

Before starting the software installation check the proper installation of Windows XP Operating System. For more information refer to the relevant handbooks.

To install the Application: 1. Insert CD-ROM in the appropriate drive.

2. Execute the program SETUP.EXE.

Follow the procedure clicking on the Next button. The procedure is self-explaining.

Note The ASTN-JCT can be directly started from the High Capacity JCT but it is necessary to set some parameters as described in the following:

1. Extract the ASTN-JCT package “astn23**.zip” in a temporary folder, e.g. “C:\temp\ ASTN23**”

2. Create a new folder called ASTN in the directory where the High Capacity LCT has been installed (C:\Program Files\Ericsson\Oms3200 Jct 5.2).

3. Move the extracted files from the temporary folder (e.g. C:\temp\ ASTN23**) to the ASTN folder (e.g. (C:\Program Files\Ericsson\Oms3200 Jct 5.2\ASTN).

4. To launch the application, perform a double click on the gmpls.bat file, placed into the ASTN folder.

Note For a faster access to the application, a shortcut on the desktop could be created.


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



To remove the Control Application’s files 1. Make sure the application is not running.

2. Use the Start-> Settings-> Control Panel Window menu. The Control Panel window will be displayed.

3. Double click on the Add/Remove Programs icon.

4. Select the Control Application that must be removed and then click on the Add/Remove… button.

See Also: Software Installation

1.2.3.2 Element Manager Version

The configuration with ServiceOn Optical Element Manager, require that the EM application is already installed and running.

The ASTN-DD add-on application is installed by default in the following directory: /opt/mv36/addon/ASTN-DD

The administrator can decide to change the default destination directory by modifying the configuration file in the installation depot. Let for example the installation file be MV36astn-dd_<ver.>_<plat.>.depot (where “ver.” stands for file version and “plat.” stands for system platform - Itanium© or PA Risc©) and downloaded into the /tmp directory.

To extract the configuration file follow the commands: cd /tmp

tar vxf MV36astn-dd_<ver.>_<plat.>.depot MV36astn-dd_<ver.>/files/opt/mv36/addon/ASTN-DD/install/MV36astn-dd_<ver.>.cfg

gzip -dc < MV36astn-dd_<ver.>/files/opt/mv36/addon/ASTN-DD/install/MV36astn-dd_<ver.>.cfg > /tmp/MV36astn-dd_<ver.>.cfg

Then edit the /tmp/MV36astn-dd_<ver.>.cfg file in order to modify the destination directory. After the indication of a different path, it is possible to proceed with the installation with the swinstall command or the SAM interface.


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



To install the Application: 1. Download the depot file in a temporary directory of the Element Manager

server. Let for example MV36astn-dd_<ver.>_<plat.>.depot (where “ver.” stands for file version and “plat.” stands for system platform - Itanium© or PA Risc©) the installation file downloaded into the /tmp directory.

2. Install the application with the swinstall utility and select as source the /tmp/MV36astn-dd_<ver.>_<plat.>.depot file.

3. Start the application with the attila utility, under the option ASTN-DD.

To remove the Control Application’s files 1. Stop the application with the attila utility, under the option ASTN-DD.

2. Remove the application with the swremove utility and select the MV36astn-dd application.

See Also: Software Installation

1.2.4 Preliminary Configuration on the High Capacity SDH Equipment

Before starting the ASTN-JCT activities check the proper configuration on the corresponding High Capacity SDH Equipment to be managed. The following preliminary setting must be performed on the single equipment:

• The right GMPLS IP address must be inserted in the proper NE protocol setup field (Node Id parameter).

• The right GMPLS licence must be installed.

• The right GMPLS status (GMPLS phase III) must be set in the proper NE GMPLS configuration fields.

NOTICE For more operating information refer to the relevant “JCT Operating Procedures” volume.



General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



1.2.5 Start the ASTN-JCT

To start the ASTN-JCT User Interface from the ServiceOn Optical Element Manager application is sufficient to click, with the right mouse button, on the GMPLS-NE and to select the option: Service ->Addon -> ASTN-DD -> ASTN-DD Configurator.

The ASTN-DD functionality is available only for GMPLS enabled NEs and with the EM provided with the proper add-on application installed.


General Information

3/1543-CSA 113 61/5 Uen A 07/31/2008



The EM will open the ASTN JCTS application with the communication settings already compiled for the selected NE.



ASTN-JCT User Interface

3/1543-CSA 113 61/5 Uen A 07/31/2008



2 ASTN-JCT User Interface

The GUI (Graphical User Interface) of the ASTN-JCT is composed by the following parts: the Title bar, the Menu bar, the Tool bar, and the Status bar.

Title Bar

Menu Bar

Tool Bar

Status Bar



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.1 Title Bar and Menu Bar In the title bar is displayed the IP address of the node which the ASTN-JCT is connected to.

Beneath the Title bar it is present the Menu bar, which is used to access all the menus. The menu bar is always visible during the connection with the Control Application.

To display a menu using a mouse, click the menu title on the menu bar. To close the menu, click another part of the screen.

There are two ways to display a menu using the keyboard:

1. Press <Alt> to activate the menu bar. Use the arrow keys to move to the menu title to select and press <Enter>. To close a menu without selecting a command, press <Esc>.

2. Press <Alt> plus the first letter of the menu title to display. Note that the first letter of each menu title on the menu bar is underlined. Select the required command with the arrow keys and press <Enter>. To close a menu without selecting a command, press <Esc>.

2.1.1 Tool Bar

The Tool bar is a bar of command buttons for reaching in a faster way the main functionalities of the application.

By stopping the mouse pointer on a command button for a few seconds, a pop-up menu will appear, indicating the main functionality that can be activated by using the selected button.

2.1.1.1 Exit Button

This button is used to exit from the application.

(as selecting File ->Exit… from the main menu).



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.1.1.2 Refresh Button

This button is used to perform a new get from the node to refresh the data stored in the ASTN-JCT.

(as selecting View ->Refresh F5 from the main menu).

2.1.1.3 ZUI Button

This button is used to display the ZUI console.

(as selecting File ->ZUI… from the main menu).

2.1.1.4 Help Button

This button is used to access to the ASTN-JCT on-line help.

(as selecting Help->Help Contents from the main menu).

2.1.2 Status Bar

On the right part of the status bar, the progress is located and it indicates the percentage of the current procedure carried out by the ASTN-JCT.



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.2 Menus In the following, a description of all menu functionalities, related to the ASTN-JCT, is supplied; detailed descriptions of each field and window are given in order to correctly understand the way to create, configure or modify the GMPLS on the Network Elements.

This section deals with the following topics:

• File

• Configuration

• View

• Link Management

• Trap Management

• Help

See Also: General Information, ASTN-JCT Setting Procedure, SNMP Traps Description



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.3 File In the File menu are present the following options:

• One shot config…

• Zui Console…

• Exit…

These features are implemented in order to download the configuration of the node, to display the ZUI Console and to close the application.

See Also: ASTN-JCT User Interface

2.3.1 One Shot Configuration

PATH: (File -> One shot config…)

This option is used to set all the GMPLS parameters in the NE by downloading a script file.

1. Click on the … button and a browser window will be displayed.

2. Using the browser select the script file and then click on the Open button, after that the chosen file will be displayed in the Script file field.

3. Check the Interactive box to provide the User the opportunity to interact with the script execution when an error occurs. In this case, it will be possible to Abort, Retry or Skip the command.



3/1543-CSA 113 61/5 Uen A 07/31/2008



4. Click on the Start button to download the file into the NE, a new window will be opened displaying the configuration commands download progress. After the download it will be displayed the report containing the number of successful and the failed commands.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.3.2 ZUI Console

PATH: (File - Zui Console…)

The ZUI Console allows sending “show “commands and other few commands in order to get details regarding the node configuration, it is not possible to send commands that can modify the node configuration. It used for factory test and debugging purpose.

To send a command: 1. Type the desired command in the Command field or select it using the

combo box. In the combo box are present the recent commands typed by the user.

2. Press the Execute button to launch the command, the result will be displayed in the window.

To save the ZUI activity into a log file:

1. Select the log file where the ZUI activity will be saved using the button, for creating a new log file it is sufficient to create a txt file.

2. Press the button to start the logging into the file, and to suspend it

press the button.

3. Press the button to close the log file.



3/1543-CSA 113 61/5 Uen A 07/31/2008




2.3.3 Exit

PATH: (File – Exit…)

This feature is used to close the User Interface (UI) of the ASTN-JCT application.

To Exit The ASTN-JCT Application: 1. Select the Exit item to close the application.

2. Press OK in the confirmation window.

See Also: File



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4 Configuration Within of this menu are present the features necessary to configure the general parameters of the equipment.

The Configuration items are the following:

• Communication Settings…

• System…

• Router Id…

• Adjacent Nodes…

• Interfaces…

• Protocols…

• TE Policy…

• Priority Levels…

• Ospf Params…

• Reop. Time…

• Gmpls ports/tp…




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.1 Communication Settings

PATH: (Configuration - Communication Setting)

This option is used to set the main communication settings of the ASTN-JCT application, in order to connect to the GMPLS-NE for the parameters configuration.

These settings are not necessary in case the interface is launched from the EM-GUI, because they are configured with the address of the selected NE.

1. Insert the Host name or the IP address of the NE by filling the Host (name or IP) field. The IP address must be configured on the NE via LCT, the available fields are: the Node Id parameter and the Ethernet interface address, if it is possible to reach the equipment via Ethernet, it is possible to use the last one to connect to the equipment.

2. Insert the reference port by filling the Port field (normally is automatically inserted). The default port 161 corresponds to the standard UDP port for the SNMP protocol.

3. Verify Read and Write password (normally are automatically inserted). 4. Confirm by clicking the OK button.

See Also: File, Router Id, Configuration



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.2 System

PATH: (Configuration - System)

This function is used to introduce or modify some information available on the NE; these parameters are the equipment name, the contact peoples and its location. They are some optional information to describe the current equipment.

1. Set or modify the name of the equipment, by filling the Name field (optional).

2. Set or modify the contact peoples for the equipment, by filling the System Contact (optional).

3. Set or modify the location of the equipment, by filling the System Location (optional).

4. Click on the OK button to validate the new configuration parameters.

See Also: Configuration



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.3 Router Id

PATH: (Configuration - Router Id)

This option is used to set the GMPLS IPv4 address of the current equipment, this address will be used by the other GMPLS equipments identify the current one.

It is mandatory to configure this address with the ASTN-JCT application and normally correspond to the Node Id parameter configured with the LCT application.

1. Insert the IP address by filling the Enter the Router Id field.

2. Click on the OK button to confirm.

NOTICE It is suggested set the Router ID address equal to the NE node IP address.

Configuration



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.4 Adjacent Nodes

PATH: (Configuration - Adjacent Nodes)

This option is used to insert all the Router ID (RID) addresses of the adjacent nodes (equipments) to the connected equipment.

Each line of the window shows the relevant parameters to a single adjacent node:

Node Router Id It indicates the relevant Router ID address (of the ASTN network) of the adjacent node.

UNI It indicates the UNI status of the adjacent node.

Oper Status It indicates the operational status of the adjacent node.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.4.1 Add an Adjacent Node

PATH: (Configuration - Adjacent Nodes - Create)

To add a new Adjacent Node to the list click on the Create button located into the Adjacent Node window. The Adjacent Nodes: Create window becomes accessible.

1. Insert the IP address (router ID address) of the remote adjacent node by filling the RID Adjacent Node field.

2. Select the adjacent node Type by using the relevant scroll list, the possible values are:

INNI if the adjacent node is in the same GMPLS network.

UNI if the adjacent node is client equipment.

3. In case the adjacent node Type selected is UNI, specify the Unit Type by means of the relevant scroll list. The possible values are: UNSPECIFIED

if the adjacent client equipment is connected via an unspecified client unit type. The UNSPECIFIED Unit Type adapts its behavior depending on what it receives from the Client equipment (remote and local). If the UNSPECIFIED Unit Type detect that the Source Client adopts UNI signaling, it will interface the destination client adopting the same method. If the Source Client does not implement any signaling, it will not use any signaling to interface the destination client. The adoption of the UNI signaling is delegated to what it receives from the Client. This is the default value.

UNI if the adjacent client equipment is connected via a UNI interface. The UNI Unit Type adopts always the UNI signaling, even if the connected client does not.



3/1543-CSA 113 61/5 Uen A 07/31/2008



NOTICE UNI signalling is available for trial purposes only.

DUMB if the adjacent client equipment is connected via a DUMB interface. The DUMB Unit Type never adopts the UNI signaling. The UNI signaling for this interface is disabled.

In Figure 1 a summary representation of the Unit Type behaviour is illustrated.

Source Client (UNI)

Local System

Remote System

Dest. Client (UNI)

UNI Signalling INNI Signalling UNI Signalling

UNI Signalling

No Signalling

UNI Signalling

No Signalling X

X UNSPEC

UNI

DUMB

UNSPEC

UNI

DUMB

UNI Signalling

No Signalling

UNI Signalling

No Signalling X

X

Figure 1 Adjacent Node – Unit Type

4. Select the Verification check box to enable the LMP procedure. The LMP procedure is used to verify the physical connectivity of the data-bearing links between the nodes and exchange the Interface Ids. The Verification option is also used to enable a resynchronization of the LMP state.

5. Insert the retransmit interval of the communication by filling the Retransmit Interval field; by default this interval is set to 2000 ms. This time represent the interval between two checks of the adjacent node.

6. Insert the retransmit timeout of the communication by filling the Retransmit Timeout field; by default this interval is set to 10000 ms. This time represent the timeout to consider the adjacent node no more reachable.


8. Repeat the operation for each Adjacent Node.

See Also: Adjacent Nodes, Edit an Adjacent Node



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.4.2 Edit an Adjacent Node

PATH: (Configuration - Adjacent Nodes - Edit)

To edit an existing Adjacent Node, select it in the Adjacent Node window and click on the Edit button. The Adjacent Nodes: Edit window becomes accessible.

Note This option is available for UNI Adjacent nodes (UNI Type).

The only modifiable parameter is the Unit Type.

For further details, please refer to Add an Adjacent Node.

See Also: Adjacent Nodes, Add an Adjacent Node

2.4.4.3 Delete an Adjacent Node

PATH: (Configuration - Adjacent Nodes - Delete)

To Delete an Adjacent Node select it into the Adjacent Node window and click on the Delete button.

NOTICE In order to delete an Adjacent Node, all the associated resources must be removed. This means that the Adjacent Node, to be removed, must not be involved in any circuit, Link Cluster (LK), Link Component (LC) and Control Channels (CC). For further details, please refer to “Associations” and “Link Cluster” chapters.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.4.4 See the Adjacent Node Details

PATH: (Configuration - Adjacent Nodes - Details)

In order to show a snapshot of the current state of an adjacent node, select it into the Adjacent Node window and click on the Details button.

The Adjacent node Detail window shows all the relevant parameter in read-only status.


2.4.5 Interfaces

PATH: (Configuration - Interfaces)

This option is used to define the CIT (Control Interface) for the current node and defining the type and the encapsulation of the IP protocol for each interface. Most of the interfaces addresses will be associated to the Equipment ports.

Each line of the window shows the relevant parameters to a single interface:

IP address It indicates the relevant IP address.

NOTICE The IP address of the point-to-point type interface is relevant to the port address. While the IP address of the broadcast type interface is relevant to the Ethernet port of the equipment or the Router ID address associated to the Network Element (NE)

type It indicates the type of the interface for each address, e.g. the point-to-point for a simple link connection and broadcast for a multi link connection.



3/1543-CSA 113 61/5 Uen A 07/31/2008



encapsulation It indicates the encapsulation type of the IP protocol used for the specific interface.

Admin Status Operative status of the interface. DOWN means that there are some problems with the interface configuration (interface not ASTN Enable or DCCm not properly configured).

Dcc Status It indicates the operational state of the configured Fast ASTN DCCs. If the App Type (Application Type) of the DCC channel configured on the system in not Fast ASTN, its DCC status will be “undefined” (this is true also for the broadcast channels – Ethernet Interfaces – that cannot be set as Fast ASTN). In case of Fast ASTN DCCs, the DCC status indicates the operational state of the communication channel: “up” for correct operational state, “down” for failed channel.


2.4.5.1 Add a new interface

PATH: (Configuration – Interfaces - Create)

To add a new interface to the list click on the Create button located into the Interfaces window. The interfaces: Create window becomes accessible.

1. Insert the IPv4 address of the interface to define, by filling the IP address field.

2. From the Interface scroll list select the type of the interface of the node. Possible values are:

Broadcast This parameter indicates an interface managed with a broadcast connection towards more destinations. Generally this option is used to configure as interfaces the Node Router Id IP address and the Ethernet interface IP address, because they are able to manage broadcast communications.



3/1543-CSA 113 61/5 Uen A 07/31/2008



Not-Broadcast not implemented

Point-to-Point This parameter indicates an interface managed with a point to point connection towards a single destination. Generally this option is used to configure as interface an IP address for the port identifier.

Point-to-Multipoint not implemented

3. Select the type of the encapsulation by using the relevant scroll list (gre or ip).

ALERT Only the ip encapsulation type has to be used.

NOTICE The gre (Generic Routing Encapsulation) encapsulation used by default to put the IP inside the OSI protocol, is suggested for the embedded communication channels that carries only OSI protocol.

The most used encapsulation is the IP protocol. It is used also for the DCC channels that are able to carry the IP protocol.


5. Repeat the operation for each interface.

2.4.5.2 Delete an interface

To delete an interface select the interface into the Interfaces window and click on the Delete button.

NOTICE In order to delete an Interface, all the associated resources must be removed. This means that the interface, to be removed, must not be involved in any circuit, Link Cluster (LK), Link Component (LC) and Control Channels (CC). For further details, please refer to “Associations” and “Link Cluster” chapters.

See Also: Interfaces



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.6 Protocols

PATH: (Configuration - Protocols)

This option is used to insert the Node addresses and to enable the use of the protocols managed by the node.

1. Insert the OSPF area address in the relevant text field; it contains the network name address where the OSPF routing protocol will collect the routing information (default: 0.0.0.0), the DCN Address is not used yet.

2. Select the protocol types that must be managed by clicking on the relevant check button. The possible options are:

LMP The LMP (Link Management Protocol) establishes and maintains control channel connectivity between neighbors. It mainly manages the link clusters, link component and control channels resources.

OSPF The OSPF (Open Shortest Path First) is a routing protocol using to build the network topology.

GRSVP-TE The GRSVP-TE (Generic Resource reserVation Protocol, with Traffic Engineering extensions) is a transport layer protocol that enables a network to provide differentiated levels of service to specific flows of data. It is mainly dedicated to carry the signaling protocol of the GMPLS network.

UNI The UNI (User to Network Interface) is the communication protocol between transport equipment and client equipment.




3/1543-CSA 113 61/5 Uen A 07/31/2008




2.4.7 TE Policy

PATH: (Configuration – TE Policy)

The TE (Traffic Engineering) policy option allows configuring the K parameter used to define the link extra cost (for further details, please refer to TE Link Cost).

NOTICE These settings affect the path computation result and should be modified only if the Operator has a very good knowledge of the path computation engine.

The K parameter changes depending on the percentage of the link bandwidth occupation (X) and according to the TE Policy thresholds (Figure 2).

K(X)

X 0

K0

Kmax

Xtresh Xmax

Figure 2 K value configuration diagram

To set the TE policy: 1. Specify the K0 value.

2. Specify the Kmax value.

3. Define the Xtres threshold. 4. Press OK to confirm the configuration or Cancel to exit.



3/1543-CSA 113 61/5 Uen A 07/31/2008



See Also: TE Link Cost, ASTN-JCT User Interface

2.4.8 Priority Level

PATH: (Configuration – Priority Level)

The holding priority is a number in the range (0-7) indicating a level of priority for bumping. The circuits with higher priority (0) will be rerouted first on the protection path. Afterwards the circuits with lower priority will be managed. In this way, circuits at higher priority, allocating resources before circuits at lower priority, are in advantage position. In every case, the policy does NOT allow the "bumping", that is "stealing" already allocated resources to a circuit from a higher priority circuit

The “Priority Level” option is used to specify, for every priority level, the time waited before the rerouting takes place.

To modify the priority Level: 1. Specify, by using the spinner buttons or by typing the value directly into the

field, the rerouting hold-off time associated to the priority.

2. Press OK to confirm the configuration or Cancel to exit.

See Also: ASTN-JCT User Interface, Tp Data



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.9 OSPF Parameters

PATH: (Configuration – OSPF Parameters)

The “OSPF Parameters” option is used to set the percentage thresholds that cause the node issuing a LSA (Link State Advertisement) message.

The LSA message could indicate a modification of the “Unreserved Bandwidth”, the “Ls Unreserved Timeslot” or the “Max Lsp Bandwidth”.

Note Currently, these three events occur under the same condition, so, their thresholds correspond to the same value.

In the upper part of the “Ospf Params” window are reported the current OSPF thresholds:

Unreserved Bandwidth Unreserved bandwidth percentage on the link. It takes into account the actual unused bandwidth. The unreserved bandwidth value is obtained by multiplying the number of free (unallocated) timeslots by their associated bandwitdth.

Ls Unreserved Timeslot Unreserved timeslot percentage on the link. It takes into account the actual unused timeslots.

Max Lsp Bandwidth The maximum LSP Bandwidth is the maximum bandwidth an LSP could reserve.

To set the OSPF parameters: 1. Define, by using the spinner buttons or by typing the value directly into the

field, the Threshold Setting for the “Unreserved Bandwidth”, the “Ls Unreserved Timeslot” and “Max Lsp Bandwidth”.

2. Use the Force no Free Band to enable LSA reporting every link state change (no bandwidth thresholds).

3. Press OK to confirm the configuration or Cancel to exit.



3/1543-CSA 113 61/5 Uen A 07/31/2008



See Also: ASTN-JCT User Interface, Protocols

2.4.10 Reoptimization Time

PATH: (Configuration – Reop Time)

The re-optimization time is used to define an interval for an automatic check of those circuits having Strong-SNCP protection scheme, where worker and protection LSP don’t respect the configured diversity. When the interval expires, a re-optimisation attempt is performed by the ingress NE, trying to restore the requested diversity. When the diversity is honored, the reoptimisation process is terminated.

To set the re-optimization time: 1. Specify in the Network Reoptimization Time (s) the interval of time (in

seconds) for the automatic re-routing on lower cost check. The value can be defined by using the spinner buttons or by typing it directly into the relevant field.

2. Press OK to confirm or Cancel to exit.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.4.11 GMPLS Ports

PATH: (Configuration – GMPLS Ports)

The “GMPLS Ports” option is used to report a list of all the GMPLS ports defined in the system together with their configuration details.

The available information are:

Index Internal port identifier.

Descr GMPLS entry description.

Capability Interface type and structuring capability.

MinFramingLevel Minimum frame granularity managed by the GMPLS resource.

MaxFramingLevel Maximum frame structure managed by the GMPLS resource.

MaxVirtualFramingLevel Maximum number of virtual channels managed by the GMPLS resource.

ActualVirtualFramingLevel Actual number of virtual channels managed by the GMPLS resource.

OperationalState Operational status of the port.

ProtectionType Protection type implemented.

ProtectionId Port protection status. It indicated if the port is protected or not.

Node Id Node identifier.



3/1543-CSA 113 61/5 Uen A 07/31/2008



Select a GMPLS entry and press Tp data to access further port details.

See Also: ASTN-JCT User Interface, Tp Data

2.4.11.1 Tp Data

PATH: (Configuration – GMPLS Ports – Tp Data)

The “Tp Data” option is used to display port channel details.

to access the Tp data: 1. Click on the Tp data button located into the GMPLS Entryes window. The

Gmpls Tp entryes window will be displayed. The available information are:

Index Internal channel identifier.

TpLabel Termination Point label associated to the channel.

GmplsLabelType GMPLS label associated to the channel (typically sdhLabel).

Role Channel role (Worker, Protection, Extra Traffic,… ).

Type Channel Type.

Available Availability state.



3/1543-CSA 113 61/5 Uen A 07/31/2008



OperState Channel operation status.

Administate Channel administrative status

RecoveryPriority The recovery priority is a number in the range (0-7) indicating a level of priority during the path signalling. Circuits with higher priority are rerouted first (in case either of failure of the protection or pre-emption of the protection resources by another circuit). In this way, with the same conditions, circuits at higher priority, having the possibility of allocating resources first, are in advantage with respect to lower priority circuits. The priority is NOT used for recalling resources already used by circuits at lower priority.

See Also: ASTN-JCT User Interface, GMPLS Ports, Priority Level



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.5 View In the View menu is present the Refresh item.

2.5.1 Refresh

PATH: (View – Refresh)

The Refresh command is used to perform a new get from the node to update the ASTN-JCT.



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6 Link Management Within of this menu are present the features necessary to define all the link parameters between the nodes of the ASTN network.

The Link Management items are the following:

• Link Cluster

• Link Component

• Control Channel

• Associations


2.6.1 Link Cluster

PATH: (Link Management – Link Cluster)

This option is used to define all the Link Clusters starting from the current node, towards the adjacent nodes in the ASTN network. An IPv4 address is associated to each Link Cluster.

Each line of the window shows the relevant parameters to a single Link Cluster:

Local ID It indicates the identifier of the local Link Cluster, IPv4 address.

Remote rid : Id It indicates the identifier of the remote Link Cluster (Remote Router Id : Remote Link Cluster Id), IPv4 address.

Weight It indicates the Link Cluster administrative cost.



3/1543-CSA 113 61/5 Uen A 07/31/2008



TE metric It is the Traffic Engineering Metric as associated to the link during Link Cluster configuration. This is a configurable parameter which is not affected by dynamic evolution and status of the network.

Color (dec) It indicates the Link Cluster administrative color, in other words it is an administrative restriction associated to the link. During a circuit creation, if the administrative color of the circuit is specified, only Link Cluster have that color highlighted may be used to routing the circuit.

Srlg (Shared Risk Link Group) It indicates the group membership of the link that shares the same failure risk.

Max Res Bw Maximum number of timeslot available on the link.

Unreserved Bw Available timeslots on the link.

Note Not all the timeslots could be available for circuit creation. Some timeslot could be DCN reserved.

LMP Status It indicates the LMP operational status. The possible values are:

• init Data links have been allocated to the LK link, but the configuration has not yet been synchronized with the LMP neighbor.

• up The Link Cluster is in service state with at least one control channel associated active.

• down The Link Cluster is in unserviceable state. The most probable cause of this failure is referable to a loss of all control channels associated.

• degraded In this state, all primary CCs are down, but the TE link still includes some data links that are allocated to data traffic.

Ospf Status It indicates the Ospf operational status.

Grsvp Status It indicates the Grsvp operational status.

See Also: Link Management



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.1.1 Add a Link Cluster

PATH: (Link Management – Link Cluster - Create)

To add a new Link Cluster, click on the Create button located into the Link Cluster window. The Create Link Cluster window becomes accessible.

1. Insert the IP address of the Link Cluster by filling the Id field of the Local area.

NOTICE The Local RID is a read only field and shown the local node IP address

2. From the RID combo box menu of the Remote area select the IP address of the relevant remote node, previously created in the adjacent nodes list.

3. Insert the IP address of the remote Link Cluster by filling the Id field of the Remote area.

4. From the Extra Action combo box menu select the type of the Link Cluster. The possible values are:

commit This parameter indicates the commit capability of the link cluster for nodes both inside the backbone and both supporting the ASTN network. It must be selected for the Link Cluster between two GMPLS nodes (Link Cluster between two backbone nodes)

privcommit This parameter indicate the private commit capability of the link cluster for nodes that are on the border of the ASTN network, that is only one node supports the GMPLS protocol. It must be selected for the Link Cluster on the ASTN network border (Link Cluster between client nodes and backbone nodes)



3/1543-CSA 113 61/5 Uen A 07/31/2008



alwayscommit This option allows adding and removing the Link Components without passing through the correlation procedure. This is not a standard LMP protocol behavior and such facility should be adopted only in specific and critical conditions (for example, degraded Link Cluster without any valid Control Channel, where the Link Components have to be removed).

NOTICE If the commit value is set the Tna field described below is disabled. When the privcommit is set the Tna field will become writable.

5. Insert the Tna (Transport Network Address) address of the relevant field (when that is editable). The default value is the same of the Link Cluster Id (local). It can also be different from the Link Cluster Id and it is used to start the circuit path from the client equipment.

6. Insert the weight of the relevant link by filling the TE Metric field. 7. Specify the Admin Metric used for associate an administrative cost to the

resource. The administrative cost can be used in place of the TE Metric for the path cost computation.

Note The selection of the Admin Metric, rather than the TE Metric, for the path computation, can be performed via the Service On Optical Management System.

8. Insert the color of the relevant link by filling the Color (dec) field.

9. Insert the group membership of the relevant link by filling the Srlg (,srlg) field, separated by a comma.


11. Repeat the operation for each interface Link Cluster.

See Also: Link Cluster



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.1.2 Delete a Link Cluster

PATH: (Link Management – Link Cluster - Delete)

To Delete a Link Cluster, select it in the Link Cluster window and click on the Delete button.

NOTICE In order to delete a Link Cluster, all the associated resources must be removed. This means that the Link Cluster, to be removed, must not be involved in any circuit and it must not have any Link Component (LC) and Control Channels (CC) associated. For further details, please refer to “Associations” chapter.

See Also: Link Cluster, Add a Link Cluster

2.6.1.3 Edit a Link Cluster

PATH: (Link Management – Link Cluster - Edit)

To edit an existing Link Cluster, select it in the Link Cluster window and click on the Edit button. The Edit Link Cluster window becomes accessible.

The modifiable parameters are: TE metric, Admin metric, Color (dec) and Srlg (,srlg). For further details, please refer to Add a Link Cluster.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.1.4 Link Cluster Verification

PATH: (Link Management – Link Cluster – Link Verif.)

The link cluster verification consists on a check of every Link Component constituting the Link Cluster. The check verifies the consistency of the local and remote label identifier for every link component constituting the link cluster and their operational status. The necessary messages are sent via the configured Control Channel (CC).

NOTICE In order to run the test, the Control Channel has to correctly work.

Each line of the window shows the relevant parameters to a single Link Component:

Local Id It indicates the relevant shelf-slot-port on the local equipment of the link.

Remote Id It indicates the relevant shelf-slot-port on the remote equipment of the link.

Test Result It reports the test result.

Correlated It indicates if the LC is associated to a LK, the possible values are:

• true The LC is associated to LK.

• false The link is in unserviceable state. The most probable cause of this failure is referable to a wrong configuration of the Link Cluster



3/1543-CSA 113 61/5 Uen A 07/31/2008



association procedure (e.g. slot not admitted for the specific Link Cluster). In case of FAILED it is necessary to delete the Link Component record related to the failure association and check the local component configuration and/or the Link Cluster association.

NOTICE The correlated values are shown when the association between the Link Cluster and the Link Component is configured.

Operational status It indicates the status of the LC, the possible values are:

• down The LC has not been put in the resource pool.

• test The LC is being tested. An LMP Test message is periodically sent through the LC.

• PasvTes The LC is being checked for incoming test messages.

• UpFree The LC has been successfully tested and is now put in the pool of resources (in-service). The link has not yet been allocated to data traffic.

• UpAllocated The LC is UP and has been allocated for data traffic.

• Degraded The last CC associated with this LC’s LK has gone down, but is still being used for data LSP.

Allocated the possible values are:

• true The LC has been allocated for data traffic.

• false The LC has not been allocated for data traffic.

See Also: Link Cluster, Add a Link Cluster, Association, Link Management, Link Component



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.1.5 See the Link Cluster Details

PATH: (Link Management – Link Cluster - Details)

In order to show a snapshot of the current state of a link cluster, select it into the Link Cluster window and click on the Details button.

The Link Cluster Detail window shows all the relevant parameter in read-only status.

Note All the parameters are described in Add a Link Cluster




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.2 Link Component

PATH: (Link Management – Link Component)

This option is used to define the Link Component of the node, that are the physical interfaces connected between the two nodes.

Each line of the window shows the relevant parameters to a single Link Component:

Local Id It indicates the relevant shelf-slot-port on the local equipment of the link.

Remote Id It indicates the relevant shelf-slot-port on the remote equipment of the link.

Link Cluster Id It indicates the correspondent Link ID address of the port on the local equipment.

NOTICE The lk Id values are shown when the association between the Link Cluster and the Link Component is configured

Correlated It indicates if the LC is associated to a LK, the possible values are:

• true The LC is associated to LK.

• false The link is in unserviceable state. The most probable cause of this failure is referable to a wrong configuration of the Link Cluster association procedure (e.g. slot not admitted for the specific Link Cluster). In case of FAILED it is necessary to delete the Link Component record related to the failure association and check the local component configuration and/or the Link Cluster association.

NOTICE The correlated values are shown when the association between the Link Cluster and the Link Component is configured.



3/1543-CSA 113 61/5 Uen A 07/31/2008



Operational status It indicates the status of the LC, the possible values are:

• down The LC has not been put in the resource pool.

• test The LC is being tested. An LMP Test message is periodically sent through the LC.

• PasvTes The LC is being checked for incoming test messages.

• UpFree The LC has been successfully tested and is now put in the pool of resources (in-service). The link has not yet been allocated to data traffic.

• UpAllocated The LC is UP and has been allocated for data traffic.

• Degraded The last CC associated with this LC’s LK has gone down, but is still being used for data LSP.

Allocated the possible values are:

• true The LC has been allocated for data traffic.

• false The LC has not been allocated for data traffic.

See Also: Association, Link Management, Link Cluster Verification



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.2.1 Create a Link Component

PATH: (Link Management – Link Component - Create)

To create a new Link Component to the list click on the Create button located into the Link Component window. The Link Component: Create window becomes accessible.

1. Insert the values in Shelf, Slot, and Port fields of the Local area, where the link is connected on the local node.

2. Insert the values in Shelf, Slot, and Port field of the Remote area, where the link is connected on the remote node. It is also possible to define the remote Link Component using an unnumbered address, select the Use unnumbered format check box and insert the value in the Unnumbered text field.

Note The “Unnumbered” option is used for ENNI interfaces (available for trial only) where it is not possible to adopt the same identifier used for the local interfaces. This value has to be expressed in hexadecimal format and it represents the identifier of the remote interface.


4. Repeat the operation for each Link Component.

See Also: Link Component



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.2.2 Delete a Link Component

PATH: (Link Management – Link Component - Delete)

To Delete a Link Component select the line of the relevant single Link Component and click on the Delete button.

ALERT To delete the Link Component, it is necessary to have the Link Id field empty, it is possible to proceed with the remove after the de-association of the selected Link Component from the Link Cluster.

See Also: Link Component, Create a Link Component

2.6.3 Control Channels

PATH: (Link Management – Control Channel)

This option is used to define the Control Channel of the node. These channels are used for the signaling protocol, e.g. to create, switch, delete the circuits.

The control channel can be performed via DCC by a tunneling (IP over OSI) procedure.

Moreover, the control channels between two adjacent nodes are no longer required to use the same physical medium as the data-bearing links between those nodes. For example, a control channel could use a separate wavelength or fibre, an Ethernet link, an IP tunnel through a separate management network, or a multi-hop IP network. A consequence of allowing the control channel(s) between two nodes to be physically diverse from the associated data links is that the health of a control channel does not necessarily correlate to the health of the data links, and vice-versa.

The Control Channels can be direct, a connection between the two involved nodes, and indirect, if the communication pass trough another node. In this case is supported one intermediate node between the extreme of the Control Channel.



3/1543-CSA 113 61/5 Uen A 07/31/2008



Each line of the window shows the relevant parameters to a single Control Channel:

id It indicates the relevant identifier of the Control Channel.

interface It indicates the corresponding local interface or local router id IP address.

remote address It indicates the corresponding remote IP address, interface or router id.

operational state It indicates the current control channel operational status. The possible values are the following:

• down This is the initial control channel state. In this state, no attempt is being made to bring the control channel up and no LMP messages are sent.

• config send The control channel is in the parameter negotiation state. In this state the node periodically sends a Config message, and is expecting the other side to reply with either a ConfigAck or ConfigNack message.

• config rcv The control channel is in the parameter negotiation state. In this state, the node is waiting for acceptable configuration parameters from the remote side. Once such parameters are received and acknowledged, the FSM can transition to the Active state.



3/1543-CSA 113 61/5 Uen A 07/31/2008



• active In this state the node periodically sends a Hello message and is waiting to receive a valid Hello message. Once a valid Hello message is received, it can transition to the UP state.

• up The CC is in an operational state. The node receives valid Hello messages and sends Hello messages.

• going down A CC may go into this state because of two reasons: administrative action, and a ControlChannelDown bit received in an LMP message. While a CC is in this state, the node sets the ControlChannelDown bit in all the messages it sends.

See Also: Link Management, Association

2.6.3.1 Add a new Control Channel

PATH: (Link Management – Control Channel - Create)

To add a new Control Channel to the equipment click on the Create button. located into the Control Channel window. The Create Control Channel window becomes accessible.

1. Insert the identifier of the relevant control channel by filling the Id field.



3/1543-CSA 113 61/5 Uen A 07/31/2008



2. From the Interface combo box menu select the IP address of the relevant interface on the local node, previously created in the interface window from configuration menu.

3. Insert the IP address of the relevant interface on the remote node by filling properly the Remote Interface field.

NOTICE The correspondence between the local and remote interface for the control channel can be different to the correspondence between the local and remote interface for the Link Cluster due to the fact the control channels between two adjacent nodes are no longer required to use the same physical medium.

ALERT The Remote Interface value must be identical to the local interface value of the remote node otherwise the Control Channel operative status will return a down value.

4. Check the Forced up box to force the Control Channel operational state to “up”. This option is useful in case the node attached to the remote end of the relevant link cluster does not manage the same set of messages (UNI, NNI boundaries).

5. Insert the Hello Interval value of the communication by filling the relevant field. The local interface will send towards the remote interface a Hello signal with a regular period of retransmission (fixed by the Hello Interval) in order to verify the presence of the control channel.

Note For Control Channels configured on DCC with “Fast ASTN” option enabled, the Hello Interval suggested value is 2000. For Control Channels configured on DCC with “Fast ASTN” option disabled, indirect Control Channels (passing through intermediate nodes) and Control Channels established between Node Id. interfaces, the Hello Interval suggested value is 600. For Control Channels configured on broadcast interfaces (Loopback/Router Id.), the Hello Interval suggested value is 2000.

6. Insert the minimum hello interval value of the communication by filling the Hello Interval Min. field; by default this value is set to 0 ms.

7. Insert the maximum hello interval value of the communication by filling the Hello Interval Max. field; by default this value is set to 4294967295 ms.

8. Insert the Dead Interval value of the communication by filling the relevant field; by default this value is set to 1900 ms. This functionality is used to terminate the control channel when no signal is received for a period of time exceeding the Dead Interval value.

Note For Control Channels configured on DCC with “Fast ASTN” option enabled, the Dead Interval suggested value is 6000. For Control Channels configured on DCC with “Fast ASTN” option disabled, indirect Control Channels (passing through intermediate nodes) and Control Channels established between Node Id. interfaces, by default, the Dead Interval suggested value is 1900. For Control Channels configured on broadcast interfaces (Loopback/Router Id.), the Hello Interval suggested value is 6000.



3/1543-CSA 113 61/5 Uen A 07/31/2008



NOTICE When is necessary to reduce the risk of a Dead Interval event, set the relevant interval to Dead Interval Max default value (4294967295 ms)

9. Insert the minimum dead interval value of the communication by filling the Dead Interval Min. field. By default this value is set to 0 ms.

10. Insert the maximum dead interval value of the communication by filling the Dead Interval Max. field. By default this value is set to 4294967295 ms.

ALERT Remember that for any Link Cluster is mandatory to associate at least a control channel, thus is advisable to configure many control channels for each Link Cluster in order to avoid the loss of the Link Cluster in consequence of a control channel termination

11. Insert the Retransmit Interval value of the communication by filling the relevant field. By default this value is set to 7000ms. This functionality is used to restore the data-exchange on the control channel previously terminated. The local interface will send towards the remote interface a signal with a regular period of retransmission (fixed by the Retransmit Interval) in order to verify the restoration of the control channel.

12. From the Disable Type combo box menu, select the proper value to disable the communication between the two nodes to synchronize the shut of the Control Channel (nice). The possible values are:

nice Soft close of the Control Channel with coordination between the two nodes for the shut procedure.

disabled Hard close of the Control Channel without any notice to the other node about the shut.

13. From the Setup Role scroll list, select the Control Channel role. During the initialization phase (first activation or after a failure), one end of the Control Channel is delegated to send the “Config.” message (Config Send Role) while the other end is delegated to receive and verify it (Config Receive Role).

configSnd Control Channel configured to send the “Config.” Message.

configRcv Control Channel configured to receive and verify the “Config.” message.

14. Insert the retransmit timeout value of the communication by filling the Retransmit Timeout: field; by default this value is set to 4294967295ms.

NOTICE Set the default value (4294967295 ms.) to reduce the risk of timeout for the transmitted packet, during the attempt to restore the Control Channel.

15. Insert the restart time value of the communication by filling the Restart Time: field; by default this value is set to 4294967295ms. This functionality permits to set a limit to resynchronize the LMP state after a control plane restart.



3/1543-CSA 113 61/5 Uen A 07/31/2008



NOTICE Set the default value (4294967295 ms) to reduce the risk of no synchronization between the two nodes during the attempt to restore the Control Channel.

16. Click on the OK button to confirm. 17. Repeat the operation for each Control Channel.

NOTICE It is possible create different control channel for each local interface due to the fact the control channels between two adjacent nodes are no longer required to use the same physical medium of the data.

See Also: Control Channel

2.6.3.2 Delete a Control Channel

PATH: (Link Management – Control Channel - Delete)

To Delete a Control Channel, select it in the Control Channel window and click on the Delete button.

See Also: Add a new Control Channel, Control Channel

2.6.3.3 Show the Link Cluster adopting the Control Channel

PATH: (Link Management – Control Channel – Show lk)

In order show a snapshot of the Link Cluster to which the selected control channel has been associated, click on the Show Lk button in the Control Channel window. Together with Link Cluster information, also its relevant weight will be displayed.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.3.4 See the Control Channel Details

PATH: (Link Management – Control Channel - Details)

In order to show a snapshot of the current state of the Control Channel, click on the Details button in the Control Channel window.

The Control Channel Details window shows all the relevant parameter in read-only status.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.6.4 Associations

PATH: (Link Management – Association)

This option is used to define the Association between the Control Channel and the Link Component for a selected Link Cluster. As consequence the Link Id in the Link Component list is displayed in base of the association created.

In the avail Control Channel area are shown both the available and associate Control Channels, while in the assoc Control Channel only the associated Control Channels are shown.

In the avail Link Component area are shown the available Link Components, while in the assoc Link Component only the associated Link Components are shown.

1. From the Link Cluster combo box menu select the Link Cluster desired (These Link Clusters have been previously created in the Link Cluster function of the Link Management menu).

2. From the avail Control Channel area select the desired Control Channels, represented by means of their Identifier and by using the arrow button icon ( “ < ” ) in the centre of the window move them on the assoc Control Channel area. After this operation will be displayed the Weight window.



3/1543-CSA 113 61/5 Uen A 07/31/2008



3. Insert the weight value in the text field, to set an administrative cost to the current control channel used for that Link Cluster.

NOTICE The avail Control Channel spin is available for the Link Clusters between two backbone nodes only. The arrow button icon ( “ < ” ) in the centre of the window is disabled in case of tributaries

4. From the avail Link Component area select all the desired Link Components and by using the arrow button icon ( “ < ” ) in the centre of the window move them on the assoc Link Component area

NOTICE The avail Link Component area is available only when a least control channel is being associated to the relevant Link Cluster (for Link Clusters between two backbone nodes only). The arrow button icon ( “ < ” ) in the centre of the window is disabled when no Control Channel is associated to the relevant Link Cluster. While for Link Clusters between client nodes and backbone nodes the avail Link Component area is always available

5. Click on the Close button to exit.

How to add a new LC to a LK 1. If the Link Component has not already created please proceed as described

in Link Component

2. From the avail Link Component area select the Link Component to be remove and by using the arrow button icon ( “ < ” ) in the centre of the window move it on the assoc Link Component area.

3. Press the Apply button.

How to remove a LC to a LK 1. From the assoc Link Component area select the desired Link Component

and by using the arrow button icon ( “ > ” ) in the centre of the window move it on the avail Link Component area.

2. Press the Apply button.

Note The de-associated Link Component is also deleted from the Node Database.



3/1543-CSA 113 61/5 Uen A 07/31/2008



How to move a LC from a LK to another one 1. De-associate the Link Component from a Link Cluster (as explained in the

previous steps).

2. Create again the Link Component as described in Link Component paragraph.

3. Associate it with the new Link Cluster as described before in “How to add a new LC to a LK”.

See Also: Control Channels, Link Component, Link Management

2.6.4.1 Force Remove

The de-association event is notified also to the remote node involved. The local node expects that the remote one acknowledges and accepts such operation. If not, the operation cannot be completed and the system refuses the command.

So, in case the remote node involved into the operation is no more reachable, this will result in the impossibility to de-associate some resources.

Force Remove option allows removing a resource without taking into account the remote node feedback.

How to move a LC from a LK to another one 1. Select, into the assoc Control Channel or assoc Link Component areas

respectively, the Control Channel or the Link Component to de-associate.

2. Press the ForceRemove button.

See Also: Control Channels, Link Component, Associations, Link Management



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7 Trap Management Within of this menu are present the features necessary to enable the reporting of the event messages to the ServiceOn Optical Network Management System. In this manner the management system will be informed about changing on the ASTN network.

The Trap Reporting items are the following:

• Trap Enable

• Trap Configuration

• Trap Viewer

• Trap Log Enable

• Trap Log Configuration




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7.1 Trap Enable

PATH: (Trap Management – Trap Enable)

This option is used to define the types of event that must be sent to the ServiceOn Optical Element Manager application.

Here are displayed the enabled or disabled messages, which can be raised by the NEs in case of problems on the GMPLS communications and reported to the management system.

How to select the event category types 1. Select the event category that must be reported by clicking on the relevant

check box. Or unselect the event category in order to disable the reporting.

2. If all event must be reported, then click on the Select All button to select all the events Select the protocol types that must be managed.

NOTICE It is advisable to select all the event categories described above

Note By means of Invert Selection button a NOT-logic inversion selection of the current events previously selected is performed.

3. Confirm the new settings by clicking on the OK button.

See Also: Trap Management, Trap Configuration, Trap Viewer



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7.2 Trap Configuration

PATH: (Trap Management – Trap Configuration)

This option is used to forward the Traps towards one or more application software.

Each line of the window shows the relevant parameters for one application software:

Desciption It indicates the typed name for the application software.

Traget Mib It indicates the IP address of the application software.

Port It indicates the port used by the application software.

See Also: Trap Management



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7.2.1 Create a Target Mib

PATH: (Trap Management – Trap Configuration - Create)

To add a new target MIB click on the Create button located into the Target Mib window. The Target Mib Create window becomes accessible.

1. Select the Create button and the following window will be displayed.

2. Type the name of the application in the Description text field.

3. Insert the IP address and the Port used by the application in the relevant text fields.

4. Click on the Ok button to confirm.

See Also: Trap Configuration

2.7.2.2 Delete a Target Mib

PATH: (Trap Management – Trap Configuration - Delete)

To delete a target MIB, select it in the Target Mib window and click on the Delete button. The Target Mib Create window becomes accessible.

See Also: Create a Target Mib, Trap Configuration

2.7.3 Trap Viewer

PATH: (Trap Management – Trap Viewer)

This option is used to show the traps received from the nodes.

See Also: Trap Configuration



3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7.4 Trap Log Enable

PATH: (Trap Management – Trap Log Enable)

The “Trap Log Enable” option is used to enable/disable the generation of log files for specific trap events.

To enable the log reporting for a specific trap event: 1. Use the Enable check box to enable the log reporting for the relevant trap

event.

Note The Select All button allows enabling the log reporting for all the traps managed. The Invert Selection button is used to invert the Enable state for all the traps managed.

2. Define, by using the spinner buttons or by typing the value directly into the field, the maximum number of log entries (Max Log Entries).

3. Click on the OK button to confirm or Cancel to exit.




3/1543-CSA 113 61/5 Uen A 07/31/2008



2.7.5 Trap Log Configuration

PATH: (Configuration – Trap Log Configuration)

The “Trap Log Configuration” option is used to define trap log general parameters and consequent behavior.

To set the trap log general parameters: 1. Define the maximum number of entries that can be recorded in the log file by

using the Max entry limit field.

2. Define for how long the log data will be stored into the system by using the Age Out (min) field (default: 24 hours – 1440 minutes).

3. Click on the OK button to confirm or Cancel to exit.


2.8 HELP From this menu item it is possible to get information about the currently installed ASTN-JCT application release, the copyrights and the type of software platform are also available.


2.8.1 About

PATH: (Help - About)

Presents a window, with the application summary and copyrights.

See Also: HELP


ASTN-JCT Setting Procedure

3/1543-CSA 113 61/5 Uen A 07/31/2008



3 ASTN-JCT Setting Procedure

In this chapter are described both the procedure to commission a node and how to decommission it.

See Also: General Information, ASTN-JCT User Interface, SNMP Traps Description

3.1 Commissioning Procedure In the following all the steps to configure a new node are described.

Using the LCT:

• Install the GMPLS license.

• Enable the GMPLS status.

• Set the Node ID (GMPLS IP address).

• Set the Ethernet Id.

• Set the DCC parameters when used as CIT.

Using the ASTN-JCT:

• Set the Node Router Id (GMPLS IP address).

See Also: Router Id

• Activate the Protocols.

See Also: Protocols

• Define the Adjacent Nodes.

See Also: Adjacent Nodes

• Define the CIT.


• Create the right Control Channel to exchange the control information between the NEs. It is suggested to configure more alternatives path by creating more Control Channels, at least one, and associate them to the correspondent Link Cluster in the next step.




3/1543-CSA 113 61/5 Uen A 07/31/2008



• Configure the Link Cluster to reach each neighbor.


• Specify the right Link Component for each single part of the link cluster (Shelf – Card Slot – Port).


• Create the final association between the Link Cluster, the Link Component and the corresponding Control Channel. Each LK-CC association must have a priority weight defined (highest priority = 0), there must not exist two association with the same priority.. For the border NE is not possible to associate the Control Channel.

See Also: Association

• Repeat the configuration steps for each GMPLS link in the network.

• Check the status of the GMPLS network, the Link Clusters must be “up”, the Control Channels must be “up” and the Link Component must be “correlated”.

See Also: ASTN-JCT Setting Procedure

3.2 How to add a new adjacency When a new node is inserted in a GMPLS network it is necessary to configure it but also all the adjacent nodes.

In the following all the steps to configure a node with a new adjacency are described.

• Define the CIT.


• Create the right Control Channel to exchange the control information between the NEs. It is suggested to configure more alternatives path by creating more Control Channels, at least one, and associate them to the correspondent Link Cluster in the next step.




3/1543-CSA 113 61/5 Uen A 07/31/2008



• Define the new Adjacent Node.


• Configure the Link Cluster between the node and the new adjacency.


• Create the association between the Link Cluster and the corresponding Control Channel. Each Link Cluster can have more Control Channels depends on the possible path between the two nodes.


• Define the Link Component for each single part of the link cluster (Shelf – Card Slot – Port).


• Create the final association between the Link Cluster and the Link Components.


• Repeat the configuration steps for each GMPLS node involved with the new adjacency.

• Check the status of the GMPLS network, the Link Clusters must be “up”, the Control Channels must be “up” and the Link Component must be “correlated”.




3/1543-CSA 113 61/5 Uen A 07/31/2008



3.3 How to remove an adjacency When a node is removed from a GMPLS network, it is necessary to change the configuration in all the adjacent nodes.

In the following all the steps to remove an old adjacency are described.

ALERT EACH OPERATION MUST BE PERFORMED ON BOTH SIDE OF THE ADJACENCY BEFORE TO PROCEED WITH THE FOLLOWING ONES.

• Dissociate all the Link Components from each Link Cluster involved in the old adjacency by using the Association menu. All the Link Components involved with the associations will be automatically deleted


• Dissociate all the Control Channels from each Link Cluster involved in the old adjacency by using the Association menu.

Note Before removing all the Control Channels from a Link Cluster be sure it does not contain any Link Component.


• Delete all the created Link Clusters by using the Link Cluster menu.


• Delete the old Adjacency by using the Adjacent Nodes menu.


• Delete all the created Control Channels by using the Control Channel menu.


• Delete all the created Control Interfaces by using the Interfaces menu.




3/1543-CSA 113 61/5 Uen A 07/31/2008



• Repeat these steps for each GMPLS node involved with the old adjacency.


3.4 Decommissioning Procedure Using the ASTN-JCT:

• Dissociate all the Control Channels and the Link Components from a Link Cluster by using the Association menu; repeat this step for each created Link Cluster.


• Delete all the created Link Components by using the Link Component menu.


• Delete all the created Link Clusters by using the Link Cluster menu.


• Delete all the created Control Channels by using the Control Channel menu.


• Delete all the created Control Interfaces by using the Interfaces menu.


• Delete all the created Adjacencies by using the Adjacent Nodes menu.


Using the JCT:

• Disable the GMPLS status

Repeat the decommission steps for each GMPLS node that must be removed.




3/1543-CSA 113 61/5 Uen A 07/31/2008



3.5 TE Link Cost The actual cost of a link for the PSE (Path Selection Engine) is the sum of two parameters:

LINK_COST = TEM + TE_EXTRA

Where:

TEM It is the Traffic Engineering Metric as associated to the link during Link Cluster configuration. This is a configurable parameter which is not affected by dynamic evolution and status of the network.

TE_EXTRA It is a parameter that takes into account several considerations aimed at optimizing bandwidth and resources allocation in the network.

The following formula illustrates the cost is:

TE_EXTRA=[base_cost(st)+extra_cost(st,max_mux)] K(bw,bw_unres)

Where:

base_cost depends on required signal type. For example: base_cost(vc4) = 2; base_cost(vc4-4c) = 8; base_cost(vc4-16c) = 32; base_cost(vc4-64c) = 128;

extra_cost depends on required signal type and the maximum multiplexing capability of the link.

K is a further parameter that works as a sort of correction taking into account the degree of occupancy of the link;

st is the signal type of the requested circuit e.g. VC4, VC4_4c, …

max_mux is the maximum multiplexing capability of the Link Cluster;

bw is the maximum bandwidth capability of the Link Cluster;

bw_unres is the unreserved bandwidth of the Link Cluster



3/1543-CSA 113 61/5 Uen A 07/31/2008



3.5.1 EXTRA_COST DEFINITION

Given the signal type (st) and the maximum multiplexing (max_mux) capability the extra_cost function assumes the following values:

st = VC-4 max_mux = VC4_4c: extra_cost(st, max_mux) = 2 max_mux = VC4_16c: extra_cost(st, max_mux) = 3 max_mux = VC4_64c: extra_cost(st, max_mux) = 4 max_mux = VC4_256c: extra_cost(st, max_mux) = 5

st = VC4_4c max_mux = VC4_16c: extra_cost(st, max_mux) = 2 max_mux = VC4_64c: extra_cost(st, max_mux) = 3 max_mux = VC4_256c: extra_cost(st, max_mux) = 4

st = VC4_16c max_mux = VC4_64c: extra_cost(st, max_mux) = 2 max_mux = VC4_256c: extra_cost(st, max_mux) = 3

st = VC4_64c max_mux = VC4_256c: extra_cost(st, max_mux) = 2

3.5.2 K DEFINITION

K is a corrective parameters that depends on the degree of occupancy of the link.

The corrective factor K applies a bias on the calculation based on the amount of already allocated bandwidth on the link.

Let’s call:

max_resv_bw maximum reservable bandwidth on the link (Mb/s) – as announced by GOSPF-TE;

bw_unres unreserved bandwidth on the link (Mb/s) – it takes into account the actual unused bandwidth in Mb/s

bw_unres value is obtained by multiplying the number of free (unallocated) timeslots by their associated bandwitdth.

It is important to notice that if the link has constraints on minimum acceptable framing level the bw_unres is computed multiplying the bandwidth associated to the lowest acceptable framing level signal by the number of available signals.

Example:

• in case of a STM-64 link with no particular framing level costraints the bw_unres is computed multiplying the number of free VC4 by 139.264 Mbps.

• in case the same link can only accept VC4-4C (or higher bandwidth signals) the bw_unres is computed by multiplying the number of free VC4-4C signals by 557,056 Mbps.



3/1543-CSA 113 61/5 Uen A 07/31/2008



If maximum reserve-able bandwidth of the link is equal to unreserved bandwidth (meaning that the available bandwidth on the link is the whole bandwidth of the link) then:

if (bw == bw_unres)

then k = 20;

else k = ((1 + max_resv_bw)/(1 + bw_unres)) * 10);

where bandwidth value are expressed in Mb/s and k is an integer value.


SNMP Traps Description

3/1543-CSA 113 61/5 Uen A 07/31/2008



4 SNMP Traps Description

The Simple Network Management Protocol (SNMP) is an application-layer protocol designed to facilitate the exchange of management information between network devices. It permits to monitor the network devices and their functions.

By using SNMP-transported data (such as packets per second and network error rates), network administrators can more easily manage network performance, find and solve network problems, and plan for network growth.

Most of the interactions between the NMS and managed devices are principally one of the following basic commands:

Reads To monitor managed devices, NMSs read variables maintained by the devices.

Writes To control managed devices, NMSs write variables stored within the managed devices.

Traps Managed devices use traps to asynchronously report certain events to NMSs.

A management information base (MIB) is a formal description of a set of network objects that can be managed using the SNMP. The format of the MIB is defined as part of the SNMP.

See Also: General Information, ASTN-JCT User Interface, ASTN-JCT Setting Procedure



3/1543-CSA 113 61/5 Uen A 07/31/2008



4.1 ASTN Traps Here are described the traps concerned the ASTN network.

lmpLinkPropertyMismatchNotifEnable If this object is true, then it enables the generation of lmpTeLinkPropertyMismatch and lmpDataLinkPropertyMismatch notifications, otherwise these notifications are not emitted.

lmpTeLinkPropertyMismatch This notification is generated when a TE link property mismatch is detected on the node. This notification should not be sent unless lmpLinkPropertyMismatchNotifEnable is true.

lmpDataLinkPropertyMismatch This notification is generated when a data-bearing link property mismatch is detected on the node. This notification should not be sent unless lmpLinkPropertyMismatchNotifEnable is true.

lmpTeLinkNotifEnable If this object is true, then it enables the generation of lmpTeLinkOpStateChange notifications, otherwise these notifications are not emitted.

lmpTeLinkOpStateChange This notification is generated when an lmpTeLinkOperStatus object for a TE link enters the degraded state. This notification should not be sent unless lmpTeLinkNotifEnable is true.

lmpUnprotectedNotifEnable If this object is true, then it enables the generation of lmpUnprotected notifications, otherwise these notifications are not emitted.

lmpUnprotected This notification is generated when there are more than one control channels between LMP neighbours and the last redundant control channel has failed. If the remaining operational control channel fails, then there will be no more control channels between the pair of nodes and all the TE links between the pair of nodes will go to degraded state. This notification should not be sent unless lmpUnprotectedNotifEnable is set to true.

lmpDataLinkNotifEnable If this object is true, then it enables the generation of lmpDataLinkVerificationFailure notification, otherwise these notifications are not emitted.

lmpDataLinkVerificationFailure This notification is generated when a data-bearing link verification fails. This notification should not be sent unless lmpDataLinkNotifEnable is true.



3/1543-CSA 113 61/5 Uen A 07/31/2008



lmpCcUpDownNotifEnable If this object is true, then it enables the generation of lmpControlChannelUp and lmpControlChannelDown notifications, otherwise these notifications are not emitted.

lmpControlChannelUp This notification is generated when a control channel transitions to the up operational state. This notification should not be sent unless lmpCcUpDownNotifEnable is true.

lmpControlChannelDown This notification is generated when a control channel transitions out of the up operational state. This notification should not be sent unless lmpCcUpDownNotifEnable is true.

lspSignalUp (lspSignalUpTrapEnable) If this object is true, then it enables the generation of signal Up trap, otherwise these trap is not emitted.

lspNotifySignalUp This notification is generated at the end of signalling operation for a lsp and report also the result of the operation.

lspTearDown (lspTearDownTrapEnable) If this object is true, then it enables the generation of tear down trap, otherwise this trap is not emitted.

lspNotifyTearDown This notification is generated at the end of tear down operation for a lsp and report also the result of the operation.

lspPathComp (lspPathCompTrapEnable) If this object is true, then it enables the generation of path computation trap, otherwise this trap is not emitted.

lspNotifyPathComputation This notification is generated at the end of path computation operation for a lsp and report also the result of the operation. This trap is emitted only if the lsp is being creating via SNMP.

lspOperStateChange (lspOperStateChangeTrapEnable) If this object is true, then it enables the generation of traps, otherwise these traps are not emitted.

lspNotifyOperStateChange This notification is generated when the lspOperStatus object is changed.

lspOperStatus Indicates the actual operational status of this LSP, which is typically but not limited to, a function of the state of individual segments of this LSP.

ospfVirtIfStateChange An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF virtual interface. This trap should be generated when the



3/1543-CSA 113 61/5 Uen A 07/31/2008



interface state regresses (e.g. goes from Point-to-Point to Down) or progresses to a terminal state (e.g. Point-to-Point).

ospfNbrStateChange An ospfNbrStateChange trap signifies that there has been a change in the state of a non-virtual OSPF neighbour. This trap should be generated when the neighbour state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). The designated router should generate the trap, when there is a neighbour transition from or to Full on non-broadcast multi-access and broadcast networks. A designated router transitioning to Down will be noted by ospfIfStateChange.

ospfVirtNbrStateChange An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF virtual neighbour. This trap should be generated when the neighbour state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).

ospfIfConfigError An ospfIfConfigError trap signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event option mismatch should cause a trap only if it prevents an adjacency from forming.

ospfVirtIfConfigError An ospfConfigError trap signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event option mismatch should cause a trap only if it prevents an adjacency from forming.

ospfIfAuthFailure An ospfIfAuthFailure trap signifies that a packet has been received on a non-virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.

ospfVirtIfAuthFailure An ospfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.

ospfIfRxBadPacket An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.

ospfVirtIfRxBadPacket An ospfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.



3/1543-CSA 113 61/5 Uen A 07/31/2008



ospfTxRetransmit An ospfTxRetransmit trap signifies that an OSPF packet has been retransmitted on a non-virtual interface. All packets that may be re-transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.

ospfVirtIfTxRetransmit An ospfTxRetransmit trap signifies that an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.

ospfTraps.ospfOriginateLsa An ospfOriginateLsa trap signifies that this router has originated a new LSA. This trap should not be invoked for simple refreshes of LSAs (which happens every 30 minutes), but instead will only be invoked when an LSA is (re)originated due to a topology change. Additionally, this trap does not include LSAs that are being flushed because they have reached MaxAge.

ospfMaxAgeLsa An ospfMaxAgeLsa trap signifies that one of the LSAs in the router's link-state database has aged to MaxAge.

ospfLsdbOverflow An ospfLsdbOverflow trap signifies that the number of LSAs in the router's link-state database has exceeded ospfExtLsdbLimit.

ospfLsdbApproachingOverflow An ospfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link-state database has exceeded ninety percent of ospfExtLsdbLimit.

ospfTraps.ospfIfStateChange An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup).

tcSignalUpTrapEnable If this object is true, then it enables the generation of signal Up trap, otherwise this trap is not emitted.

tcNotifySignalUp This notification is generated at the end of signalling operation for a circuit and report also the result of the operation.

tcTearDownTrapEnable If this object is true, then it enables the generation of tear down trap, otherwise this trap is not emitted.

tcNotifyTearDown This notification is generated at the end of tear down operation for a circuit and report also the result of the operation.



3/1543-CSA 113 61/5 Uen A 07/31/2008



tcPathCompTrapEnable If this object is true, then it enables the generation of path computation trap, otherwise this trap is not emitted.

tcNotifyPathComputation This notification is generated at the end of path computation operation for a circuit and report also the result of the operation. This trap is emitted only if the circuit is being creating via SNMP.

tcOperStateChangeTrapEnable If this object is true, then it enables the generation of TC operational change traps, otherwise these traps are not emitted.

tcNotifyOperStateChange This notification is generated when the tcOperationalState object is changed.

tcOperationalState Operational status for this Circuit:

• green: circuit ok; worker LSP is carrying traffic

• yellow: circuit Ok; auto switched to protection due to a fault

• red: loosing traffic.)

See Also: SNMP Traps Description


GMPLS Parameters in the OSI.ini file

3/1543-CSA 113 61/5 Uen A 07/31/2008



5 GMPLS Parameters in the OSI.ini file

The OSI.ini file is a configuration file used to set both the OSI and the GMPLS parameters in the NE, in this chapter is described the GMPLS section only, to get further information about the OSI section and how to download the file into the NE, please refer to the volume “Marconi OMS 3200 JCT Operating Procedures”.

The GMPLS parameters are actually IP parameters, for instance GMPLS as IP addresses.

ALERT Sending a file with wrong parameters can interrupt the communication with the Network Management Centre.

In the following is given an example of IP parameters in the OSI.ini file that the user can eventually change and download on the equipment.

5.1 OSI.ini Example [OSI_CONFIG]

TRANSPORT=2,5,3,3000,180,180,180,160,1,100,4,1;

Q3_TSAP=4,00000006;

NSAP=20,4901020304050607080900012302E4002C070701;

TL1Q3NSAP_SEL=1D;

TARPNSAP_SEL=AF;

NETWORK=1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;

ALLL1IS=6,01800C200014;

ALLL2IS=6,01800C200015;

ALLENDSYS=6,09002B000004;

ALLINTSYS=6,09002B000005;

ISIS_SYS_ID=6,490102030405;

ISIS_MAN_AREA_ADDR_0=13,49010203040506070809000123;

ISIS_MAN_AREA_ADDR_1=0,;

ISIS_MAN_AREA_ADDR_2=0,;

ISIS_NUM_STATIC_ROUTE=0;

STATIC_ROUTE_0=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_1=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_2=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_3=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_4=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_5=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_6=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_7=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_8=0,0,6,490102,20,05B4F8C80000;

STATIC_ROUTE_9=0,0,6,490102,20,05B4F8C80000;

CLNS_PARAM=0,0,1;



3/1543-CSA 113 61/5 Uen A 07/31/2008



ETH_CONFIG=7,0,0,1,1492,10,10,64,64,3,45,20,20,3,1;

MAC_ADDR=02E4002C0707;

LSAP_SEL=FE;

DCC_PROFILE_0=1512,1492,1,7,15,15,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_1=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_2=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_3=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_4=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_5=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_6=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_7=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_8=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_9=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_10=1512,1492,1,7,17,17,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_11=1512,1492,1,7,10,10,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_12=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_13=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_14=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_15=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_16=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_17=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_18=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

DCC_PROFILE_19=1512,1492,1,7,20,20,0,0,0,3,10,10,200,3,7,20,20,3;

SHELF1_SLOT2_PORT1_DCCm=1,1,0,S0L0P0T0;

SHELF1_SLOT2_PORT1_DCCr=1,1,1,S0L0P0T0;








[IP_CONFIG]

NODE_ID=10.10.10.1;

IP_FORWARDING=1;

RIP_ENABLED=0;

LOOPBACK_INTERFACE=10.10.10.1,0;

ETH_CONFIG_IP=2,173.16.78.7,255.255.255.0,1500,0;

[IP_TUNNELING]

IPOSITUNNEL_0=0,4901020304050607080900012402e455072009cc,1500,0;

[IP_STATIC_ROUTES]

ROUTE_0=10.10.10.5,255.255.255.255,10.10.10.6,IPOSITUNNEL_0,20,1;

[IP_ISIS_CONFIG]

ISIS_ROUTER_TYPE=2;

ISIS_AUTO_GRE_TUNNELLING=0;

[IP_DCC_CONFIGURATION]



3/1543-CSA 113 61/5 Uen A 07/31/2008



SHELF1_SLOT2_PORT1_DCCm=1,1,0,0,0,1.2.1.1,255.255.255.255,0.0.0.0,1500,3,1;

SHELF1_SLOT2_PORT1_DCCr=2,0,1,10,5,0.0.0.0,0.0.0.0,0.0.0.0,1500,0,1;








See Also: GMPLS Parameters in the OSI.ini file

5.1.1 Parameters Meaning

5.1.1.1 [IP_CONFIG]

NODE ID = <IpAddress>; IpAddress = Insert IP address of the Node ID.

IP_FORWARDING = <value>; Where the value can be:

• 0 = IP forwarding disabled.

• 1 = IP forwarding enabled.

LOOPBACK_INTERFACE = <value>; IpAddress = Insert IP address of the Loopback Interface

ETH_CONFIG_IP=<NewProtocol>,< IpAddress >,< Mask >,<MTU>; Where:

• NewProtocol (0 = OSI, 1 = ipArp, 2 = ipArpOsi)

• IpAddress (IP address )

• Mask (subntework mask)

• MTU (Maximum Transfer Unit, default value 1500, possible values 500 – 1500)



3/1543-CSA 113 61/5 Uen A 07/31/2008



5.1.1.2 [IP_ISIS_CONFIG]

ISIS_ROUTER_TYPE = <value> Where the value can be:

• 0 = OSI.

• 1 = IP

• 2 = dual

ISIS_AUTO_GRE_TUNNELLING = <value> Where the value can be:

• 0 = disabled.

• 1 = enabled.

5.1.1.3 [IP_DCC_CONFIGURATION]

SHELF<S>_SLOT<L>_PORT<P>_DCC<D> = <NetworkProtocol>,<DataLinkProtocol>,<PPPMode>,<PPPEchoTimer>, <PPPEchoNum>,<Address>,<Mask>,<PeerAddres>,<MTU>; Where:

• S = shelf number where the unit is inserted (1, 2, 3…).

• L = slot number where the unit is inserted (1, 2, 3…).

• P = port number of the unit (1, 2, 3…).

• D = DCC type (R =DCCr, M = DCCm).

• NetworkProtocol (0 = OSI, 1 = IP, 2 = OSIIP).

• DataLinkProtocol (0 = LAPD, 1 = PPP).

• PPPMode (0 = normal, 1 = encaps only).

• PPPEchoTimer (0 = disabled, possible values 0 – 65535).

• PPPEchoNum (0 = disabled, possible values 0 – 65535).

• Address = (IP address of the interface).

• Mask = (subnet mask of the interface).

• PeerAddres = (IP address of the remote interface).

astn_jct operationg procedure

Documents