TNMS ASON / Ethernet

Manager 11.0

User Manual (UMN)

A42022-L5981-A051-03-7618
 User Manual (UMN)

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-
TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR
THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2007. All rights reserved.

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-
nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-
zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

2 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN)

Statements of compliance

FCC statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation. Shielded cables must be used with
this unit to ensure compliance with the Class A FCC limits.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. Operation of this equip-
ment in a residential area is likely to cause harmful interference in which case the user will be required
to correct the interference at his own expense.

CE statement

The CE conformity declaration for the product is fulfilled when the system is built and cabled in line with
the information given in the manual and the documentation specified within it, such as installation
instructions, cable lists or the like. Where necessary project-specific documentation should be taken into
consideration. Deviations from the specifications or independent modifications to the layout, such as
use of cable types with lower screening values for example, can lead to violation of the CE protection
requirements. In such cases the conformity declaration is invalidated. The responsibility for any prob-
lems which subsequently arise rests with the party responsible for deviating from the installation spec-
ifications.

A42022-L5981-A051-03-7618 3
Issue: 3 Issue date: August 2007
 User Manual (UMN)

4 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN)

Table of Contents
This document has 113 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Further documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.1 Online help system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.2 TNMS Core/CDM and Network Element documentation . . . . . . . . . . . . . . 13

2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1 Functions and tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.1 Network visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2 Provision of services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.3 Network and service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2 Supported network structures and NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.1 ASON domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.2 EVC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 System description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Client/server architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.1 Distribution of client and server applications. . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.2 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.2.3 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3 Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3.1 Server application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.2 Client application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Function overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4.2 ASON management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4.3 Ethernet management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4.4 EM/NE management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4.5 Topology management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4.6 User and security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4.7 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.4.8 Customer management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.9 Backup and restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.1 Hardware recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Configuring SDH Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4 Installing TNMS ASON / Ethernet Manager . . . . . . . . . . . . . . . . . . . . . . . . 39
4.5 Uninstalling TNMS ASON / Ethernet Manager . . . . . . . . . . . . . . . . . . . . . . 45
4.6 Documentation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

A42022-L5981-A051-03-7618 5
Issue: 3 Issue date: August 2007
 User Manual (UMN)

5 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.1 Starting TNMS ASON / Ethernet Manager server . . . . . . . . . . . . . . . . . . . . 46
5.2 Starting a TNMS ASON / Ethernet Manager client session . . . . . . . . . . . . . 46
5.2.1 Default username and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.2 Changing the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.3 Terminating an TNMS ASON / Ethernet Manager client session . . . . . . . . 48

6 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.1.1 Working with the mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.1.2 Working with the keyboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.2 Graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.2.1 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.2.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.2.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2.4 Status bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.2.5 Filtering and Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.3 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.3.1 EM/NE Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.3.1.1 Handling EM/NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.3.1.2 Information about the EM/NE state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.3.1.3 Operational state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.3.2 Topology Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.3.2.1 Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.3.2.2 Handling NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.3.2.3 Topological Container Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.3.2.4 Physical trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.4 ASON management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.4.1 ASON Logical Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.4.2 NE management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.4.3 Component link management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.4.3.1 Creating a Component Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.4.3.2 Component Link details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.4.4 TE-Link management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.4.4.1 Creating a TE-Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.4.4.2 TE-Link details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.4.5 LSP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.4.5.1 LSP details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.4.5.2 Relocating LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.4.6 Call Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.4.6.1 Creating a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.4.6.2 Call details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4.6.3 Modifying a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4.6.4 Configuring external switch requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.5 Ethernet management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.5.1 Interworking with TNMS Core/CDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.5.2 Activating and Adopting NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.5.3 Element Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN)

6.5.4 EVC Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.5.4.1 Supported scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.5.4.2 Supported VLAN processing modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.5.4.3 Creating an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.5.4.4 EVC Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.5.4.5 Modifying/Activating an EVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.5.4.6 Using Filter and Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.5.5 Viewing the STP map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.6 Viewing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.6.1 Log List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.6.2 Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.6.3 Saving/Loading filter and sort settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.6.4 Saving log and log list records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.6.5 Printing log and log list records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.1 Setting date and time zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.2 Importing and exporting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.3 User and Security administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.3.1 General security rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.3.2 Security alarming and security logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.3.3 User administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.3.4 User group administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.3.5 Policy administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.3.6 Domain administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.3.7 Access rights or mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.4 Log administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.4.1 Log export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.4.1.1 Manual export of logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.4.1.2 Scheduled export of logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.4.1.3 Export file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.4.1.4 Output Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.4.2 Log settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
7.4.2.1 Log full behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
7.4.2.2 Log thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
7.4.3 Alarms and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

8.1 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.2 Backup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.2.1 Backup TNMS ASON / Ethernet Manager information . . . . . . . . . . . . . . . 107
8.2.2 Backup TNMS Core/CDM and TNMS ASON / Ethernet Manager . . . . . . 108
8.3 Restore procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.3.1 Restore TNMS ASON / Ethernet Manager information . . . . . . . . . . . . . . 108
8.3.2 Restore TNMS Core/CDM and TNMS ASON / Ethernet Manager
information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

9 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

A42022-L5981-A051-03-7618 7
Issue: 3 Issue date: August 2007
 User Manual (UMN)

List of Figures
Figure 1 ASON domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 2 ASON domain in a mixed scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 3 EVC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 4 System architecture of TNMS ASON / Ethernet Manager . . . . . . . . . . . 20
Figure 5 Client/server architecture of the TNMS ASON / Ethernet Manager . . . . 21
Figure 6 Distributed TNMS applications (large system) . . . . . . . . . . . . . . . . . . . . 22
Figure 7 Distributed TNMS applications (medium system) . . . . . . . . . . . . . . . . . . 23
Figure 8 TNMS server applications on one machine (small system) . . . . . . . . . . 23
Figure 9 Replication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 10 Backup server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 11 Server and client software components . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 12 SNMP Proxy configuration in TNMS Core/CDM. . . . . . . . . . . . . . . . . . . 37
Figure 13 SNMP Trap communities configuration . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 14 New Trap community settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 15 SNMP Trap Filter settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 16 Installation: choosing the installation folder . . . . . . . . . . . . . . . . . . . . . . 40
Figure 17 Installation: selecting the installation set. . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 18 Installation: selecting components to install . . . . . . . . . . . . . . . . . . . . . . 41
Figure 19 Installation: configuring DB connection. . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 20 Installation: configuring TNMS database and user . . . . . . . . . . . . . . . . . 42
Figure 21 Installation: configuring SDH Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 22 Installation: configuring LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 23 Installation: confirmation of installation settings . . . . . . . . . . . . . . . . . . . 44
Figure 24 TNMS ASON / Ethernet Manager main window . . . . . . . . . . . . . . . . . . . 51
Figure 25 Menu bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 26 Main toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 27 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 28 EM/NE State Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 29 NE Maintenance state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 30 Network Map window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 31 Topological Tree window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 32 NE symbol and small NE symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 33 Topological container representation . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 34 Navigation within topological containers . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 35 Resizing TCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 36 Graphical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 37 ASON logical map window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 38 ASON Ports window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 39 Component-Link Management window. . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 40 New Component-Link window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 41 Component Link details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 42 TE-Link Management window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 43 TE-Link details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 44 LSP Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 45 Call management window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN)

Figure 46 Call details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 47 Ethernet Logical Map window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 48 EM/NE Object Management Tree window. . . . . . . . . . . . . . . . . . . . . . . 82
Figure 49 NE symbol in adoption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 50 “Element Browser” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 51 “EVC Management” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 52 Supported network scenarios: pure hiT70xx NEs.. . . . . . . . . . . . . . . . . 85
Figure 53 Supported network scenarios: mixed hiT70xx NEs. . . . . . . . . . . . . . . . 86
Figure 54 Structure of service scenario with three EVCs. . . . . . . . . . . . . . . . . . . . 86
Figure 55 Structure of service scenario with two EVCs. . . . . . . . . . . . . . . . . . . . . 87
Figure 56 Structure of service scenario with one EVC. . . . . . . . . . . . . . . . . . . . . . 87
Figure 57 “EVC Details” window: EVC ports tab . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 58 “EVC filter and sort” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 59 “Logical Planned STP Tree” window . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 60 Data repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

A42022-L5981-A051-03-7618 9
Issue: 3 Issue date: August 2007
 User Manual (UMN)

List of Tables
Table 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 4 ASON domains: supported network element . . . . . . . . . . . . . . . . . . . . . 18
Table 5 Network elements for EVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 6 Hardware recommendations for TNMS ASON / Ethernet Manager . . . 36
Table 7 Selection of standard keyboard operations . . . . . . . . . . . . . . . . . . . . . . 50
Table 8 Menu Bar Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 9 Main toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 10 Status bar components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 11 Object windows and corresponding “Filter and Sort” window . . . . . . . . 54
Table 12 EM/NE state icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 13 EM/NE state icons correspondence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 14 Write access states icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 15 Communication state icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 16 VLAN processing modes for hiT7020/30/35/60/60HC NEs. . . . . . . . . . 88
Table 17 VLAN processing modes for hiT7050/70 NEs. . . . . . . . . . . . . . . . . . . . 88
Table 18 Output directories for log types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 19 Log full behavior for certain log conditions . . . . . . . . . . . . . . . . . . . . . . 104
Table 20 Messages generated by log management when exporting logs . . . . . 105

10 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Preface

1 Preface
The User Manual (UMN) gives a complete overview of the functions, applications, archi-
tecture and installation of TNMS ASON / Ethernet Manager.

1.1 Intended audience

This document is intended for all users of TNMS ASON / Ethernet Manager.

1.2 Structure of this document

This document is structured as follows:

Chapter Title Subject

Chapter 1 Preface Provides an introduction for this document.
Chapter 2 Introduction Gives a general description of TNMS ASON /
Ethernet Manager.
Chapter 3 System description Provides an overview of the system
architecture, the main features and the
functions of TNMS ASON / Ethernet Manager.
Chapter 4 Installation Contains all instructions for installing TNMS
ASON / Ethernet Manager.
Chapter 5 Getting Started Describes all the steps that must be performed
before TNMS ASON / Ethernet Manager can be
used.
Chapter 6 Operation Contains the functions provided by TNMS
ASON / Ethernet Manager to operate a network.
Chapter 7 Administration Contains the functions provided to administrate
TNMS ASON / Ethernet Manager.
Chapter 8 Backup and Restore Contains the functions to backup, restore and
archiving data.
Chapter 9 Abbreviations Contains a list of all acronyms and their long
form used in this document.

Table 1 Structure of this document

g Some features described in this documentation may not be available. In order to

identify the features released for the product, please refer to the Release Notes
delivered together with the product.

A42022-L5981-A051-03-7618 11
Issue: 3 Issue date: August 2007
Preface User Manual (UMN)

1.3 Symbols and conventions

The following symbols are used in this document.

Symbol Explanation
Notes provide additional useful information.

Warnings give you important information which must be followed in

order to avoid possible equipment damage or data loss.

Table 2 Symbols

The following conventions are used in this document.

Convention Explanation
bold Graphical user interface text, e. g., field names and button descriptions,
are placed in bold.
Example: Click the View menu, and then click New View.
monospace Commands, screen output, file names and paths are placed in a special
font.
Example: $ sqlplus /nolog
italics Place holders for real names and values are represented in italics.
Example: Select the siemens_app policy.
< ... > In monospace placed text place holders for real names and values are
represented in square brackets.
Example: Sequence number is <sequence_number>

Table 3 Conventions

1.4 Further documentation

1.4.1 Online help system

An online help systemis provided with the TNMS ASON / Ethernet Manager software. It
includes comprehensive instructions on the functions offered by the user interface. The
help system contains information on window contents, menus and meaning of used
icons. Via the help table of contents, the user can find the tasks and procedures neces-
sary to operate and administrate TNMS ASON / Ethernet Manager.
Help can be invoked in any of the following ways:
– After invoking help from the menu bar, the user can search for topics via the table of
contents, the index or a word search.
– Clicking the Help button in the current window, which displays information about the
window contents.
– Pressing <F1>, which displays information about the contents of the active window.

12 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Preface

1.4.2 TNMS Core/CDM and Network Element documentation

This manual concerns TNMS ASON / Ethernet Manager only. For more detailed infor-
mation on TNMS Core/CDM as the basis software and on the managed network
elements (NE), please refer to the corresponding documentation.

A42022-L5981-A051-03-7618 13
Issue: 3 Issue date: August 2007
Introduction User Manual (UMN)

2 Introduction
TNMS ASON / Ethernet Manager is an optional application for TNMS Core/CDM, that
enhances the TNMS Core/CDM features by modern technologies. Management func-
tions for two different technologies are provided on a common platform: Automatic
Switched Optical Networks (ASON) and Ethernet.
In addition to Ethernet point-to-point connections provided by TNMS Core/CDM, TNMS
ASON / Ethernet Manager is responsible for logical end-to-end connections and ser-
vices. TNMS ASON / Ethernet Manager uses the functions of TNMS Core/CDM, which
manages the physical structure of the transport network and its conventional network
elements.
One of it’s components, ASON Manager, supports end-to-end provisioning, and protec-
tion management in ASON domains.
The component Ethernet Manager provides a simple and fast provisioning of EVCs
(Ethernet Virtual Connections) with multipoint-to-multipoint connections on network
layer 2.
TNMS ASON / Ethernet Manager allows to integrate modern technologies and services
into the networks managed by TNMS Core/CDM.

2.1 Functions and tasks

TNMS ASON / Ethernet Manager allows to configure, operate and maintain the follow-
ing parts of the overall transport network:
– ASON domains, that are build up with SURPASS hiT 7070, and
– EVC configurations, which are supported by all SURPASS hiT 70xx products.
The following components are provided by TNMS ASON / Ethernet Manager:
– EM/NE management for managing element management systems and network ele-
ments.
– Topology management for the definition and visualization of objects describing the
network structure with its network elements, physical connections and associated
configurations.
– ASON management for end-to-end service provisioning, fault and protection man-
agement in ASON domains.
– Ethernet management for easy configuration and supervision of EVCs.
– for creating a customer database and managing the customers of EVCs according
to the providers’ requirements.
– Log management for storing and viewing operating data.
– User and security management to protect the system against unauthorized access.
The main tasks are briefly described in the following chapters.
TNMS ASON / Ethernet Manager provides a user-friendly graphical user interface which
comprises GUI plug-ins for all the various components.

14 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Introduction

2.1.1 Network visualization

TNMS ASON / Ethernet Manager provides the following functions for a fast and com-
fortable overview of the network and the display of available resources.
The topology management provides the user with graphical network maps which display
the network to be monitored. For each technology the appropriate maps are provided.
– ASON:
A map with all ASON relevant resources such as ASON-capable network elements,
and corresponding links is displayed. The end-to-end connections with their end-
points can also be displayed as well as the resources involved.
– Ethernet:
A map displays all network elements with layer-2-switch. The links between the
network elements (GFPG trails) are shown as well as the end-to-end connections.
Topological containers group network elements in a hierarchical or logical manner.
STP (Spanning Tree Protocol) is applied to ensure a loop free network. Therefore
TNMS ASON / Ethernet Manager provides STP maps with STP trees, where the
end-to-end connections can also be displayed.
The state of the network elements and their links are displayed on the map. The end-to-
end connections can be highlighted.

2.1.2 Provision of services

The configuration of end-to-end services with TNMS ASON / Ethernet Manager requires
a physical network structure which must first be set up with TNMS Core/CDM. The
network elements data, which support either ASON or Ethernet, must then be trans-
ferred to TNMS ASON / Ethernet Manager and can be used to build up the topology of
the ASON domain or EVC configuration and to set up appropriate services for the cus-
tomers.
For that purpose TNMS ASON / Ethernet Manager provides the following functions:
– ASON management
Network provisioning is done by setting up Traffic Engineering-Links (TE-Links), that
are the logical connections between ASON network elements. TE-Links are
composed of Component links, which must be created first.
Service provisioning is done by provisioning Calls, that connect two endpoints. For
each Call, its requested bandwidth, its restoration scheme and its protection scheme
with working path and protecting path can be defined.
The one or more underlying Label Switched Pathes (LSPs) are set up automatically
by the ASON Control Plane of the network element and can be relocated by the
user.
– Ethernet management
End-to-end services are realized by setting up Ethernet Virtual Connections (EVCs).
An EVC uses VLAN mechanisms to separate traffic according to different users and
to connect two or more Ethernet ports of network elements.
An EVC is always specific for a customer, and the provision of a service needs
customer information. Therefore TNMS ASON / Ethernet Manager stores customer
information in an own customer database. The format of the customer entries can
be defined during the database creation.

A42022-L5981-A051-03-7618 15
Issue: 3 Issue date: August 2007
Introduction User Manual (UMN)

2.1.3 Network and service monitoring

TNMS ASON / Ethernet Manager provides the following information for supervising the
operational reliability of the end-to-end services and the logical network. All alarms of
the underlying physical network are handled by TNMS Core/CDM.
– Different current states of network elements and their corresponding links are dis-
played on the map, as well as in a summary window and tables.
– The ASON Manager displays all signaled paths for Calls: the current working path,
the protecting path and signaled but failed paths.
– The Ethernet Manager indicates, by displaying a specific symbol, whether the actual
and required configurations of a network element or an end-to-end connection differ.
To display the actual situation in an STP network the Ethernet Manager provides
maps with the current STP tree.
– Operating data of the system are logged and can be viewed in the corresponding
logs.

2.2 Supported network structures and NEs

TNMS ASON / Ethernet Manager supports end-to-end services in
– ASON domains on VC4 level, and
– in EVC configurations on network layer 2.

2.2.1 ASON domains

ASON domains are built on the VC4 layer of SURPASS hiT 7070, that possess an
ASON Control Plane. The Control Plane sets up and releases connections and may
restore a connection in case of a failure. Thereby the Control Plane uses network gen-
erated signalling and routing protocols.
ASON domains can be built up as part of the transport network. They have the advan-
tage of easy end-to-end provisioning, as well as fault, and protection management. Soft
Permanent Connections (SPC) connect the both endpoints (NE1 and NE2) within the
ASON domain. If a path fails, an alternative path is used automatically. Upon failure,
paths are restored dynamically by rerouting from the source (“Dynamic Source
Reroute”).

16 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Introduction

Private branch

NE 2

ASON domain

n
io
NE

ct
ne
on
tC
en
an
rm
PSTN

Pe
ft
So
SURPASS HiT 7070

Non-ASON-capable network element

Logical trail (TE-Link)

Working path
Protecting path

Figure 1 ASON domain

In detail the following methods are offered to ensure the SPC:
– 1+1 path protection.
The ASON Control Plane computes an alternative path between the endpoints. This
path is ready and will be used as soon as a failure on the working path occurs. Due
to the fast switching time this method suits for time-critical applications.
– Upon failure, paths are restored dynamically by rerouting from the source.
As soon as a failure occurs on the working path the ASON Control Plane computes
a new path from the source endpoint (ingress node) to the target endpoint (egress
node) of the ASON domain. This path considers the current state of the network. If
a failure occurs on this path also, a new path is computed again (multi-failure pro-
tection). The re-computing of an alternative path and the switch to it need a little
time. Therefore this method is suitable for data applications.
– Permanent 1+1 path protection and dynamic source reroute.
This method combines the both methods described above: As soon as a failure
occurs on the working path, the ASON Control Plane switches to the ready protec-
tion path and computes a new protection path from the ingress node. This method
is suitable for time-critical applications.
– Pre-planned shared path restoration and dynamic source reroute.
In contrast to the ready protection paths pre-planned paths are prepared but not
ready (switched). All necessary path information is available in the involved network
elements. As soon as a failure occurs on the working path the pre-planned protec-
tion path is switched and used. The ASON Control Plane computes a new path from
the ingress node to the egress node and provides the network elements with this

A42022-L5981-A051-03-7618 17
Issue: 3 Issue date: August 2007
Introduction User Manual (UMN)

pre-planned path. Pre-planned paths help to save resources because working paths
can share pre-planned paths as protection paths.
Mixed scenario with ASON domain
End-to-end paths can outreach the ASON domain and consist of different parts: perma-
nent connections, which are set up by TNMS Core, and Soft Permanent Connections
(SPCs) beween the ingress node and the egress node, which are managed by TNMS
ASON / Ethernet Manager. At the edge of the ASON domain, TNMS Core combines the
SPC with the permanent connection to an end-to-end path. Concatenated VC4 signals
(contiguous and virtual concatenation) are supported.

ASON domain

NE 2

C NM p b tio t
T tu ec en
or S y n
se onn an
C erm
P

M
D
n

C
N tio

e/
er SO ec
ag A nn

/
an S o
NE 1 M NM t C
et T en
rn by an
he p rm
E t t u Pe
se oft
S
C NM p b tio t
T tu ec en
or S y n
se onn an
C erm
P

M
D
C
e/

SURPASS HiT 7070

Non-ASON-capable network element

Logical trail (TE-Link)

Working path
Protecting path
Permanent connection
Path termination

Figure 2 ASON domain in a mixed scenario

The following nework element is supported to build up ASON domains. Please refer to
the release notes for further current NE versions.

Network element Release

SURPASS hiT 7070 3.3

Table 4 ASON domains: supported network element

18 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Introduction

2.2.2 EVC configurations

EVCs (Ethernet Virtual Connections) are based on GFPG (Generic Framing Procedure
Group) trails and use VLAN mechanisms to establish connectivity. GFPG trails connect
the WAN ports of the network elements and are set up with TNMS Core/CDM. They
require an SDH infrastructure with SDH interfaces.
An EVC represents end-to-end connectivity between two or more Ethernet ports and is
always assigned to a customer. Multipoint-to-multipoint connections are supported. For
each EVC-endpoint, a defined bandwidth and the priority, with which its data are treated,
can be set.

Customer A Customer B

VLAN 1
Customer B

VLAN 2

Customer B Customer A

SURPASS HiT 70xx

Physical trail

Figure 3 EVC configuration

The following network elements are supported to build up EVCs. Please refer to the
release notes for further current NE versions.

Network element Version

SURPASS hiT 7070 3.3
SURPASS hiT 7050 3.21
SURPASS hiT 7060 3.1, 3.2, 3.3, 4.0, 4.1
SURPASS hiT 7060 HC 3.2, 3.3
SURPASS hiT 7035 4.2
SURPASS hiT 7030 3.3, 3.4, 4.0
SURPASS hiT 7025 4.1
SURPASS hiT 7020 3.1

Table 5 Network elements for EVCs

A42022-L5981-A051-03-7618 19
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

3 System description
This chapter provides a description of TNMS ASON / Ethernet Manager architecture
and a functional overview.

3.1 System architecture

TNMS ASON / Ethernet Manager is an optional application, which is based on TNMS
Core/CDM. It uses the communication channels supported by TNMS Core/CDM and
provides end-to-end services on network layer. TNMS ASON / Ethernet Manager is
responsible for the ASON and the EVC (Ethernet Virtual Connection) management.
Figure 4 shows the general structure of TNMS ASON / Ethernet Manager to manage
end-to-end services in a transmission network.

TNMS
ASON / Ethernet
Manager

TNMS
Core/CDM

DCN

NE NE NE

Figure 4 System architecture of TNMS ASON / Ethernet Manager

TNMS ASON / Ethernet Manager has direct access via the network element controllers
used by TNMS ASON / Ethernet Manager itself. Besides this, TNMS ASON / Ethernet
Manager uses TNMS Core/CDM to get and process data of network elements.
The TNMS ASON / Ethernet Manager allows to configure the ressources on the network
elements, which are (additionally to the setup with TNMS Core/CDM) necessary to
setup end-to-end connections. These element management functions are executed via
the managers provided by TNMS ASON / Ethernet Manager.
For a comfortable handling of the two separate applications, a direct access from the
TNMS Core/CDM graphical user interface to the TNMS ASON / Ethernet Manager
graphical user interface is provided.

20 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

3.2 Client/server architecture

TNMS ASON / Ethernet Manager is a scalable multi-user system with client/server
architecture. The client application runs on any Windows PCs with Java Standard
Edition. It provides the graphical user interface of TNMS ASON / Ethernet Manager for
the network operators and interacts with the server application. Up to 40 client PCs can
be connected to one server machine.
The server application is based on the Windows operating system. It is responsible to
process the client requests. To perform these requests, the server application uses the
installed network element controllers to communicates with the network elements itself
via DCN to get and process data.
The server application retrieves system information on the network elements, object
type, hierachical information and status information and stores this information, which is
necessary for the superior network management in an own SQL database.
To manage user data and to authenticate users, the server application uses LDAP
(Lightweight Directory Access Protocol). A LDAP database contains all necessary data
to ensure the system.

TNMS ASON / Ethernet

Manager

TNMS Core/CDM TNMS

GCT
ASON / Ethernet
client
Manager client

SQL
TNMS server
ASON / Ethernet
Manager server LDAP
server

TNMS Core/CDM
server

DCN

NE NE NE

Figure 5 Client/server architecture of the TNMS ASON / Ethernet Manager

3.2.1 Distribution of client and server applications

TNMS ASON / Ethernet Manager supports scalable configurations. Like TNMS
Core/CDM, the client and server applications of TNMS ASON / Ethernet Manager can
be aranged in diffent ways. The same component can run in parallel on different
machines, just as one machine can be shared by different applications.
The interworking with TNMS Core/CDM allows also different arrangements: the TNMS
ASON / Ethernet Manager server application can run on the same machine as the
TNMS Core/CDM server application, as well as on a different one. It can use network

A42022-L5981-A051-03-7618 21
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

element controllers (NECs), which are installed on the same machine as the server
application, as well as network element controllers on other machines.
The client applications of TNMS ASON / Ethernet Manager and TNMS Core/CDM can
be installed on different PCs. If the user wants both client applications integrated with a
cut-through of the graphical user interface, they must run on the same PC.
Large system
Figure 6 gives an example of a large network, where the applications are distributed on
many different machines.

TNMS TNMS
TNMS Core/CDM TNMS Core/CDM
ASON / Ethernet ASON / Ethernet
SysAdmin client
Manager client Manager client

LDAP
server
TNMS
SQL TNMS Core/CDM
ASON / Ethernet SQL
server server
Manager server server

NEC for TNMS

TNMS Core/CDM
ASON / Ethernet
net server
Manager

Figure 6 Distributed TNMS applications (large system)

Medium system
To reduce the amount of machines in medium networks, applications can run in parallel
on the same machine. The example in Figure 7 shows that the network element control-
lers (NECs) run on the same machines as the appropriate server applications.

22 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

TNMS TNMS
TNMS Core/CDM TNMS Core/CDM
ASON / Ethernet ASON / Ethernet
SysAdmin client
Manager client Manager client

LDAP
TNMS server
SQL TNMS Core/CDM
ASON / Ethernet
server server SQL
Manager server
server
NEC for TNMS
TNMS Core/CDM
ASON / Ethernet
net server
Manager

Figure 7 Distributed TNMS applications (medium system)

Small system
If the network is small, all server applications can be installed on the same machine (see
Figure 8). The network element controllers (NECs) cannot be used by TNMS Core/CDM
and TNMS ASON / Ethernet Manager simultaneously. All NECs can run in parallel on
the same machine.

TNMS
TNMS Core/CDM TNMS Core/CDM
ASON / Ethernet
SysAdmin client
Manager client

LDAP
TNMS
SQL TNMS Core/CDM server
ASON / Ethernet
server server
Manager client
SQL
server
NEC for TNMS
TNMS Core/CDM
ASON / Ethernet
net server
Manager

Figure 8 TNMS server applications on one machine (small system)

TNMS ASON / Ethernet Manager cooperates with TNMS Core/CDM, independently if
TNMS-M is in use or not.

A42022-L5981-A051-03-7618 23
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

3.2.2 Replication
Replication is used to sychronize all data automatically between the active ASON /
Ethernet Manager server application and the standby server application.
SQL and/or LDAP replication can be configured between two TNMS ASON / Ethernet
Manager server applications. A replication agreement is established between the active
and the standby database. Both server applications must have the same software com-
ponents installed and configured, and manage the same network elements.
The machines, on which the server applications run, are connected via Ethernet.

LADP LADP
server TNMS TNMS server
ASON / Ethernet ASON / Ethernet
SQL Manager server Manager server SQL
server server

Replication agreement

LAN

Replication agreement

LAN

Figure 9 Replication server

3.2.3 Backup
The backup server stores the backup of the SQL database and the LDAP database. The
backup server is connected to the machine with the ASON / Ethernet server application
via Ethernet.

LADP
TNMS server Backup of TNMS
ASON / Ethernet ASON / Ethernet
Manager server SQL Manager server
server

LAN

Figure 10 Backup server

24 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

3.3 Software components

TNMS ASON / Ethernet Manager uses a component approach. In this approach, each
component provides a distinct function.

System control and supervision GUI client frame

ASON Ethernet ASON Ethernet

management management management management

EM/NE object User security EM/NE object User security

management management management management

Log Topology Log Topology

management management management management

Customer Fault Customer Fault

management management management management

LADP
Backup and server
Restore
SQL
server

SDH Bridge Mediator

TNMS Core/CDM NECs

server

Figure 11 Server and client software components

As shown in Figure 11 the components are:
– ASON management
This component provides the functions to manage all objects for the ASON techno-
logy. Contains the data for end-to-end services as well as the data of appropriate
resources.
– Ethernet management
This component provides the functions to manage all objects for the Ethernet tech-
nology. Contains the data for EVCs.
– EM/NE object management
This component provides administration and management of the NEs. Contains all
addressing data for EM- and NE-Objects e.g., NE-address. Hierarchical information
of EMs and NEs is also provided for the Ethernet technology.

A42022-L5981-A051-03-7618 25
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

– User and security management

This component provides user and security management in TNMS ASON / Ethernet
Manager, e.g., creation and maintenance of users and user groups, user profiles,
security policies. Authentication and authorization of users based on that data.
– Log management
This component provides the functions to maintain logs (log life cycle), to write
records to logs on request of other components and to control access to logs. It also
provides facilities to export logs in a readable format and to display logs according
to filtering and search criteria.
– Topology management
This component provides the functions to provision the end-to-end services
between network entities, e.g., definition of physical connections, graphical render-
ing of these physical connections. It provides network maps and network supervi-
sion (mapping of notifications to connections and logical links). For the Ethernet
technology, it also provides a hierarchical grouping of network elements using con-
tainers.
– Customer management
This component provides the functions to manage customer data. Customer data is
required for the provision of EVCs.
– Fault management
This component provides the functions to process alarms, which are received from
the system and from the components. It correlates alarms with the supervised
objects. Fault management does not process any network element alarms.
– GUI client frame
This component is part of the TNMS ASON / Ethernet Manager client application. It
integrates all the GUI client plug-ins into a common main window and is responsible
for the look & feel of the graphical user interface. It provides the base functions like
saving, printing and importing/exporting of xml files.
– System control and supervision
This component is responsible for the coordination of the components and for the
supervision of the operational status of the TNMS ASON / Ethernet server applica-
tion. It coordinates the processes during migration (import of data from a previous
version), startup, restoration (recovery from a system failure that caused a loss of
data), shut-down of TNMS ASON / Ethernet server application.
– Backup and Restore
This component is responsible for the manual and scheduled backup of persistent
data as well as the restoration of such data.
– SDH Bridge
This component is responsible for the SDH trails. It also receives trail notifications
from TNMS Core/CDM and forwards them to the system.
– Mediator
This component provides communication between the TNMS ASON / Ethernet
Manager server application and the network elements via the network element con-
trollers (NECs) interfaces to manage all the ASON and Ethernet related functionality
of the network elements.

26 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

Components make use of functions and applications provided by other components.

This way, components partially depend on each other.

3.3.1 Server application

The server provides the environment for running the software components e.g., EM/NE
management, Backup and Restore or Mediator. All system information is held on the
server. TNMS ASON / Ethernet Manager uses an SQL database for storing e.g., alarms,
system messages, user data, DCN data, and a security log. Security authorization is
handled via LDAP.
Starting and stopping the server and stack processes are handled by a supervision
process running on the server. This process will automatically restart the server in case
of a failure or system crash.

3.3.2 Client application

The client provides a network management graphical user interface (GUI). Via this GUI
all management functions, e.g., provisioning of end-to-end-services and invoking of
element managers, are available.
The main parts of the TNMS ASON / Ethernet Manager client are the network manage-
ment graphical user interface including the import/export interfaces. The following infor-
mation can be configured on the client:
– Placement of network elements on the network map
– Window customization (size, visible columns, column widths)
– Icon representations and background bitmaps are stored individually for each user.
The network map may thus look different for each user
– Filter configuration
Network management graphical user interface
The TNMS ASON / Ethernet Manager graphical user interface (GUI) provides the
operator with several network views which contain graphical and text information about
current alarms, states and resources. The GUI contains network maps, list and log
windows, as well as specific dialog windows. For complex configuration tasks, e. g., to
configure ASON Calls or EVCs, wizards are available. Depending on the assigned user
access rights, the user’s access can be restricted to certain functions.
Access to element manager applications
In order to obtain detailed information about an NE, the operator can open the associ-
ated element manager application (= LCT) directly from the TNMS ASON / Ethernet
Manager GUI. TNMS ASON / Ethernet Manager starts the corresponding process and
provides the interface of the associated NE controller. Element manager applications
provide access to all NE data and also enable the configuration and control of NE behav-
ior. The availability of access to specific EM functions depends on the access rights
assigned to the user. This way, depending on the actual NE type, performance values
and alarms can be requested, and the backup and restore of configuration and other
data initiated.

A42022-L5981-A051-03-7618 27
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

3.4 Function overview

This chapter contains the main functions and applications of TNMS ASON / Ethernet
Manager. Each sub-chapter describes the main functions of the TNMS TNMS ASON /
Ethernet Manager components.

3.4.1 General
Remote login
TNMS ASON / Ethernet Manager supports remote login from an external machine via
TCP/IP according to the client/server architecture. The TNMS ASON / Ethernet
Manager client runs on a different machine and accesses to the server machine via a
TCP/IP connection.
Automatic reconnection
An automatic reconnection to the network elements is supported in case of a communi-
cations loss. The user may configure the retry interval.

3.4.2 ASON management

The ASON management provides all functions to provision end-to-end connections
between ASON-capable network elements (NEs).
The following objects are managed:
Call
Calls are the relations between two endpoints (with working and protecting path) within
ASON domains. A Call has one or more underlying Label Switched Paths (LSPs).
Label Switched Path (LSP)
A Label Switched Path (LSP) is automatically computed and signaled by the ASON
control plane. It can be affected by the operator. The operator can (optionally) specify
the hops, which the LSP should traverse or not traverse.
TE-Link
TE-Links are connections between ASON nodes. They have traffic-engineering capabil-
ities, which can be configured. A TE-Link consist of one or more Component Links.
Component Link
A Component Link is a connection between two ASON ports.
All these objects are handled via lists. ASON-capable NEs, Calls, TE-Links and LSPs
are displayed on a map, which contains only ASON-related information.
Main features
The ASON management provides the following main features:
– Call management
– Create/modify/delete Calls
– List/filter Calls
– View Call data
– Activate/deactivate Calls
– TE-Link management
– Create/modify/delete TE-Links
– List/filter TE-Links

28 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

– View TE-Link data

– Activate/deactivate TE-Links
– Component Link management
– Create/delete Component Links
– List/filter Component Links
– View Component Link data
– Label Switched Path (LSP) management
– List/filter LSPs
– View LSP data
– Relocate LSPs
– Information on ASON-capable ports of network elements
– List/filter ports
– View port attributes
– Visualization
– Display of a map with ASON-capable network elements and their links
– Highlight Calls and LSPs on the map

3.4.3 Ethernet management

The Ethernet management provides all functions to provision end-to-end connections
with the help of EVCs (Ethernet Virtual Connections).
An EVC connects two or more Ethernet ports over the transport network, through GFPG
trails.
Every EVC uses a route between the EVC endpoints. When the operator creates or
modifies an EVC, planned and (for resilience) alternative routes are computed automa-
tically on base of a planned (fault-free) network tree (STP tree). The computation of a
planned network tree must done by the operator every time when the network topology
or STP parameters have changed. An actual network tree is always updated automati-
cally after STP configuration changes of the network elements
The planned routes are the basis for resource allocation. EVCs are then only enabled,
if there is an actual route (with all necessary network configurations of the referenced
resources) between the EVC endpoints.
The available and used resources (port and routes) can be viewed with the Ethernet
management to monitor the network.
Main features
The Ethernet management provides the following main features:
– STP-based network tree management as prerequisite for creating EVCs and corre-
sponding routes
– Compute planned network trees (STP trees)
– View all available (planned and actual) network trees (STP trees) in the network.
– View a symbol for each actual tree in the network tree list, that indicates, if the
actual tree is the planned tree or not.
– Ethernet Virtual Connection (EVC) management
– Create/modify/delete EVCs
– List/filter EVCs
– View EVC Details
– View the EVC’s operational state according to the actual EVC’s routes.
– Approve EVCs

A42022-L5981-A051-03-7618 29
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

– Activate/deactivate EVCs
– Lock/unlock EVCs
– Information on EVC-related resources
– View the currently available containers, NEs, cards, LAG ports, and ports
– View of symbols for each of these objects, if the actual state is different from the
required one.
– View Ethernet port attributes
– Visualization
– Display of a map with Ethernet-capable network elements and links.
– Display status information concerning network elements and links on the map
– Display of symbols, if the actual status of a NE differs from the required one.
– Display of actual and planned network trees (STP trees)
– Highlight EVCs on the network map and on the STP tree map
– Highlight planned and protecting routes of EVCs on the STP tree map
– Highlight inactive links on the STP tree map

3.4.4 EM/NE management

The EM/NE management covers functions for handling and administering element
managers (EMs) and network elements (NEs).
Handling means moving the NEs from one element manager to another, searching for
EM and NEs and changing their activation state.
Administering means creating, deleting and modifying NE/EM properties. Furthermore,
NEs can be duplicated, e.g., a new NE can be created from an existing one.
The following objects are managed:
Element managers
The Element Manager (EM) represents a DCN channel. It allows a hierarchical organi-
zation of the NEs. An element manager can contain one or more NEs. The number of
NEs managed by an EM depends on the number of NEs the user assigns.
An EM allows activating or deactivating all subordinated NEs at once. It is advised to
enable the scaled start up, to avoid that all the NEs start up at the same time causing an
overload situation.
Network elements
A Network Element (NE) consists of telecommunications equipment (or groups/parts of
telecommunication equipment) and support equipment. An NE performs Network
Element Functions (NEFs) and has one or more standard Q-type interfaces.
The EM/NE objects are handled via a graphical tree structure. The tree provides hierar-
chical information showing which EM manages a specific NE, or which NEs are
managed by a particular EM.
An NE can be activated or deactivated via the "EM/NE Object Management" window.
When an NE is activated its state is changed to running.
Main features
The EM/NE management service provides the following main features:
– EM/NE state summary display
– Export EM/NE configuration data
– Import EM/NE configuration data

30 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

– EM/NE management:
– Create/delete EM/NE
– Modify EM/NE
– Activate/deactivate EM/NE
– Move NE
– Duplicate NE
– Display discovered NEs
– Switch the operational state of NE
– Tree View: display of NE address information and connection state

3.4.5 Topology management

Topology management displays the physical network structure and supports the func-
tions and applications needed for network surveillance and service provisioning. It uses
the following objects:
– Topological Containers (TCs)
– Network element symbols
– Physical Trails (PTs)
Main features
Topology management provides the following main features:
– Network provisioning, the physical network topology is defined via the following
operations:
– Creation/Deletion of topological containers
– Creation/Deletion of network element symbols
– Creation/Deletion of physical trails
– Creation/Deletion of topological user profiles
– Move network element symbols
– Insert a network element into physical trails
– Network map, which is used by topology management to display the physical
network in a graphical mode

3.4.6 User and security management

In order to ensure a secure system, the user and security management component
provides the capability to administer and visualize user and security relevant data by:
– Authenticating - allowing only valid users to, and preventing malicious ones from,
acessing the system
– Authorizing - regulate the operations that can be performed by the authenticated
users by placing restrictions on the kind of operations that a user may carry out
– Auditing - keep track of the operations that a user performs creating a record of the
operations that an authenticated user has performed on the secure system
All the other software components rely on user and security management to ensure a
secure TMN system.
User management

A42022-L5981-A051-03-7618 31
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

User management allows the creation of a user account that belongs to a human user,
who is obligated to authenticate with the system. User accounts are assigned to user
groups that have access rights managed and configured by security management.
User management provides a single login throughout the TMN system, with the capa-
bility to store the user’s credentials and profile. Each user has his own profile that stores
many different settings, e.g., holding the personal GUI preferences of a specific user.
Security management supports the binding of profiles to specific users, but the respon-
sibility of the profile content is not within the scope of security management.
Security management
User authentication and policy management are means of creating a secure TMN
system and authorizing a user to perform a particular action. Each component provides
a command tree with all the possible actions or commands to the security management
administration service.
User authorization is based on policy administration (on a certain action or command).
From a TMN security administrators perspective, security management allows the user
to:
– Retrieve the command tree from a given component
– Retrieve a list of securable objects from that component
– Create policies by assigning the desired actions
– Assign the user groups with the desired policies
Based on this information, the component can query security management and verify
whether a user has permission to execute a specific action on a certain securable object.
Alarming and logging
User and security management supports security and command logging as well as
security alarming. Component commands to be logged or raised alarms, have the same
granularity as defined for the command tree and offered in policy administration. These
functions rely on fault management and log management for implementation.
Main features
User and security management supports the following main features:
User management
– Create, delete and modify user accounts and user groups
– Activate/Deactivate user accounts
– Force a user to logoff
– Unlock user accounts
– View the existing user accounts, the login status and the user groups they belong to
– Assign/Unassign users accounts to user groups
– User profile: user’s workspace settings, such as windows size and positioning, filter
and column settings
Security management
– Configure Security Settings
– Initial password change interval
– Inactivity duration for an operator

32 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

– Automatic de-activation and activation rules for operators

– Display of the advisory message
– Manage the password history
– Domain and Policy operations
– Create, delete and modify policies
– View the existing domains and policies
– Configure and view the access rights or mapping between a user group and policy
– Import/Export of security data: policies, domains, mappings, users and user groups
Alarming and Logging
– Security Alarms
– Security Log
– Command Log

3.4.7 Log management

Log management component provides persistent storage of data in logs as log records.
Other components like fault management and user and security management manage-
ment, post their alarms/notifications/commands and log management automatically
stores them in a specific log as log records.
Overall log management is a passive component which is synchronously invoked
whenever another component needs to log an event. However, it also features an active
behavior when it spontaneously generates system alarms and messages informing the
user of certain log conditions.
To control access to logs, user and security management is used to validate the actions
taken by the user.
Log types
The log structure depends on the data records to be stored. The log structure contains
a common part for record identification/management and a log type specific part for the
structured application data. Log management predefines six log types:
– Alarm log - alarm notifications and associated alarm information
– Network event log - unsolicited messages from network elements and state change
notifications
– System event log - overall system messages. This log is used by all components to
log system wide information, warnings and error messages that occur during the
execution of commands either in the network elements or in the TMN system
– Command log - all types of configuration commands used by other components
– Security logs - specific log for security management, e.g., storage of security alarm
notifications and security configuration commands
Each log type has a responsible component for creating, managing and providing facil-
ities to view and export the log contents:
– Log management - responsible for security, system event, network event and
command log types
– Fault management - responsible for the alarm log type

A42022-L5981-A051-03-7618 33
Issue: 3 Issue date: August 2007
System description User Manual (UMN)

Log management setup phase

During the system setup phase, log management creates a Network Event Log, System
Event Log, Command Log and a Security Log on the server. These logs are always
active while the server is deployed and running. The logs are system wide, e.g., they
can have multiple sources of log record events. In addition, an alarm log is also created.
Log management is not responsible for creating and managing these logs since there is
a strict coupling between any of these logs and the component using them. Each com-
ponent uses the log management interface to create and manage these logs, e.g., they
are created and managed with the support of log management services. In addition, the
access permission is provided by the responsible component that creates them, e.g.,
fault management provides the access permissions for the alarm log.
Main features
Log management provides the following main features:
Operation
– View logs and list of logs
– Filter and sort logs and log list
– Configure columns to be displayed
– Freeze/Update log record list
– Save and print logs
Administration
– Modify existing logs
– Alarm and message generation
– Define maximum size of a log
– Specify log thresholds and full behavior settings
– Manual and scheduled export

34 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) System description

3.4.8 Customer management

Customers are the users of end-to-end connections. They are the customers of the
network provider. TNMS ASON / Ethernet Manager supports the creation of customer
databases, which meet the network providers’ requirements.
Main features
The main features provided by customer management are:
– Create, delete, and modify customer databases as well as list customer database
data.
– Query a customer database based on a user-defined filter criteria
– Create, delete, and modify customers as well as list customer data
– Share a customer in another database

3.4.9 Backup and restore

The TNMS ASON / Ethernet Manager allows to backup and restore the data of the SQL
database and the LDAP database. For this backup and restore the mechanism of SQL
Server and LDAP are used.

A42022-L5981-A051-03-7618 35
Issue: 3 Issue date: August 2007
Installation User Manual (UMN)

4 Installation
This chapter provides a guideline of the procedures to be taken to install TNMS ASON
/ Ethernet Manager, namely in the following order:
– Hardware recommendations (see Chp. 4.1)
– Software requirements (see Chp. 4.2)
– Configuring SDH Bridge (see Chp. 4.3)
– Installing TNMS ASON / Ethernet Manager Client/Server (see Chp. 4.4)
– Uninstalling TNMS ASON / Ethernet Manager (see Chp. 4.5)
– Documentation installation (see Chp. 4.6)

4.1 Hardware recommendations

Table 6 provides an overview of hardware recommendations for TNSM ASON / Ethernet
Manager installations. However other configurations are possible depending on the
network size.

Hardware TNMS ASON / Ethernet TNMS ASON / Ethernet

Manager Client Manager Server
Processor Intel Pentium IV 3.2 GHz Xeon DP 3.0 GHz
Memory 1GB RAM 2GB RAM
Operating System Windows XP or Windows Windows XP or Windows
Server 2003 Server 2003

Table 6 Hardware recommendations for TNMS ASON / Ethernet Manager

Planning for hardware, software and licenses should be undertaken on project-specific

basis.

4.2 Software requirements

The following software is required to install TNMS ASON / Ethernet Manager:
1. Operating system: Microsoft Windows XP (c) (with SP2 minimum) or Microsoft
Windows Server 2003 (c) (with SP1 minimum).
2. TNMS Core/CDM system installed and connected physically with TNMS ASON /
Ethernet Manager server machine.
3. SDH Bridge configured in TNMS Core/CDM (see ch.4.3.)
4. Microsoft SQL Server 2005 (c) installed and synchronized with TNMS Core/CDM
server.
To install TNMS Core/CDM and MS SQL Server 2005 please refer to the installation
manual (IMN) of TNMS Core/CDM.

4.3 Configuring SDH Bridge

The SDH Bridge is responsible to deliver GFPG terminated path information to the
Ethernet Manager server in order to report connectivity between two end points.
TNMS Core/CDM must have the SNMP proxy installed and configured as SDH Bridge
relies on SNMP proxy to retrieve SNC data and receive SNC modification notifications.

36 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Installation

In order to accomplish this task, SNC notifications must be enabled in the SNMP proxy’s
configuration window.
To configure the TNMS Core / CDM SNMP proxy do the following:
1. Open TNMS Core/CDM SysAdmin and login.
2. Start the TNMS Core / CDM server.
3. After the server has been started, activate the SNMP external interface and open
the correspondent “SNMP proxy properties” window.
4. In the “SNMP proxy properties-SNMP Proxy” window configure the available SNMP
Proxy settings ensuring that:
– Trap Mode: select Traps according to SNMP V2.

Figure 12 SNMP Proxy configuration in TNMS Core/CDM

5. In the “SNMP proxy properties-MIBII” window enter the System Group information
namely the location and contact.
6. In the “SNMP proxy properties-SNMP Config” window the SNMP community and the
Trap communities have to be configured.

A42022-L5981-A051-03-7618 37
Issue: 3 Issue date: August 2007
Installation User Manual (UMN)

Figure 13 SNMP Trap communities configuration

– To configure the SNMP community, click the New button and enter the follow-
ing settings:
Community Type: SNMP community
Community Name: Enter a unique community name
IP Address: Enter the TNMS Core/CDM server IP address, e.g. 0.0.0.0
Privileges: Select the privileges of the community, e.g. write
– To configure the Trap communities, for each TNMS ASON / Ethernet Manager
server machine, click the New button and enter the following settings:
Community Type: Trap community
Community Name: Enter a unique community name
IP Address: Enter the TNMS ASON / Ethernet Manager server IP address
followed by the 170 port number, e.g. 150.150.123.11:170

Figure 14 New Trap community settings

7. In the “SNMP proxy properties-SNMP Trap Filter Settings” window enter the types
of traps to be sent by SNMP proxy.

38 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Installation

Figure 15 SNMP Trap Filter settings

8. When finished click the Apply toolbar button to save all settings.
The SNMP Proxy configuration of TNMS Core/CDM is mandatory when Ethernet
Manager is to be used.

4.4 Installing TNMS ASON / Ethernet Manager

In this chapter the user will be informed regarding the steps needed to install TNMS
ASON / Ethernet Manager. The installation is for a complete new system.
Installing TNMS ASON / Ethernet Manager client and server software
To install TNMS ASON / Ethernet Manager client and server software proceed as
follows:
1. Insert the TNMS ASON / Ethernet Manager SW CD.
2. Run the install file on the CD to open the “Introduction” window. The left panel
displays the complete list of steps to install the software.
Click Next to continue.
g If it is necessary to alter some of the options made during the installation, cancel
the installation process and restart from step 1). Do not click the Previous button.
3. In the “License Agreement” window scroll down to read the complete list of steps to
install the software.
Select the I accept the terms of the License Agreement option and click Next to
continue.
4. In the “Choose Install Folder” window select the appropriate installation folder and
click Next to continue.

A42022-L5981-A051-03-7618 39
Issue: 3 Issue date: August 2007
Installation User Manual (UMN)

Figure 16 Installation: choosing the installation folder

5. In the “Choose Install Set” window click the button associated with one of the avail-
able installation packages:

Figure 17 Installation: selecting the installation set

– Full: To install all the SW components in the machine namely Server, Client,
System Administration and NE Controllers.
– Server: To install all the SW components but not the Client.
– Client: To install the Client SW component.
– Custom: To choose specifically which components to install.
g The next steps are available or skipped depending on the selected installa-
tion set.
6. In the “Customize the features to be installed” window select the boxes correspond-
ing to the components you which to install, namely the “Packet Manager Server”
component, the “Packet Manager Client” component, the NE controllers or the
“System Administration” component. Click the Next button.

40 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Installation

Figure 18 Installation: selecting components to install

g This window is available for custom installation set.
7. In the “OS Credentials” window enter the operating system’s password of the current
user, i.e. the password used to login to the computer where the TNMS ASON /
Ethernet is being installed. The password is needed to configure the component ser-
vices.
Click the Next button.
8. In the “Ms SQL database connection” window insert the following database connec-
tion settings:
– SQL Server hostname: Enter the SQL Server IP address/hostname.
– SQL Server port: Enter the SQL Server port number e.g. 1433.
– DBA Database user: Enter the name of the database administrator.
– DBA Database password: Enter the password of the database administrator
user account.

Figure 19 Installation: configuring DB connection

A42022-L5981-A051-03-7618 41
Issue: 3 Issue date: August 2007
Installation User Manual (UMN)

Click the Next button to continue.

g A warning message will be shown to ask about the SQL database usage.
User should prevent that SQL database is not in use by another application,
e.g. TNMS Core/CDM.
Click Ok.
9. In the “Create TNMS PM Database and User” window configure the settings of the
user that will access to TNMS ASON / Ethernet Manager database:
– TNMS PM DB name: Enter a name for the database of TNMS ASON / Ethernet
Manager.
– TNMS PM DB user: Enter a name for the DB user.
– TNMS PM DB password: Enter a password for the DB user.
– Re-enter TNMS PM DB password: Re-Enter the password for the DB user.

Figure 20 Installation: configuring TNMS database and user

g A warning message will be shown asking to test the database connection. Click
Yes to begin the test or click No to proceed with the installation.
10. In the “SDH Bridge configuration” window define the following parameters of the
SDH Bridge connection:
– SNMP Proxy IP: Enter the IP address of the machine where the TNMS
Core/CDM machine is located.
The default value is the local machine IP address.
– SNMP Proxy community string: Enter the SNMP proxy community name as
configured in TNMS Core/CDM SNMP proxy settings e.g. public.
– SNMP Proxy listen port: Enter the listen port. Default value is 161.

42 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Installation

Figure 21 Installation: configuring SDH Bridge

Click the Next button to continue.
11. In the “LDAP Configuration” window introduce the information of the server PC
where to install the LDAP components, namely:
– Computer name: Enter the full server computer name (including it’s domain),
e.g. server1.tnms.nsn.com when the PM server’s computer name is server1 and
the domain where computer belongs is tnms.nsn.com
The target computer must belong to one domain, so that LDAP installation is
successfull.
g When it is not possible to have the server computer in a domain controller,
computer’s host file needs the be edited as follows:
- Using a text editor, open C:\WINNT\system32\drivers\etc\hosts
- Add a text line composed of “<server ip address><space><computer
name.domain>“, e.g. “10.10.10.10 server1.tnms.nsn.com”
- Save the file
– Install directory: Enter the installation directory. Default value is c:\Program
Files\Sun\MPS.
– Server port: Enter the Server port. Default value is 10757.
– Admin port: Enter the Administration Server port. Default value is 10758.
– Admin ID: Enter an administration identification e.g. admin.
– Admin password: Enter a password for the Administration account.
Password has a minimum of eight characters.

A42022-L5981-A051-03-7618 43
Issue: 3 Issue date: August 2007
Installation User Manual (UMN)

Figure 22 Installation: configuring LDAP

Click the Next button to continue.
12. In the “Choose Shortcut Folder” window configure the options of the icons and short-
cuts to be created during installation.
Click the Next button to continue.
13. In the “Pre-Installation Summary” window a summary of the installation settings is
presented. If the settings are correct, click the Install button to start the installation.

Figure 23 Installation: confirmation of installation settings

14. In the “installation Results” window the results of the installation are presented. Click
Done to finish the installation.
g In large configurations where TNMS ASON / Ethernet Manager server and TNMS
Core/CDM server are installed in different machines, the required LCTs must be
manually installed in TNMS ASON / Ethernet Manager server machine.
To complete the installation, please reboot your computer.

44 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Installation

4.5 Uninstalling TNMS ASON / Ethernet Manager

To uninstall TNMS ASON / Ethernet Manager you must use the “Add or Remove Pro-
grams” function from Windows OS.
To remove TNMS ASON / Ethernet Manager components from your machine perform
the following steps:
1. Click the “start” button from Windows OS.
2. Select “Settings>Control Panel” to open the Control Panel.
3. Double-click “Add or Remove Programs” icon.
4. After the entire list of installed programs has been populated, select the TNMS
related programs and click the “Change/Remove” button.
5. Confirm your action when asked to.
The TNMS ASON / Ethernet Manager will be removed from the machine except the
created databases.
In case the “Silent Installer” has been used during the installation, the unistalling process
is also silent.

4.6 Documentation installation

The installation of TNMS ASON / Ethernet Manager documentation enables the user to
access the customer documentation directly through the GUI help menu. The documen-
tation installation is done after TNMS ASON / Ethernet Manager has been installed as
described in chp. 4.4.
To install TNMS ASON / Ethernet Manager documentation, proceed as follows:
1. Insert Documentation CD.
2. Start the documentation installer through "Start” -> "Programs” -> "TNMS” -> "DocIn-
staller”.
3. The installer opens the “TNMS Documentation” window. Click “Next”
g The installation can be canceled, throughout this sequence, using the button
“Cancel”
4. Select, from the displayed list, the drive for the TNMS Documentation CD and click
“Next”.
g .If the wrong location is selected, a warning will indicate the need of a new loca-
tion. Click “Ok” and repeat step 4
5. The install folder is, by default, the path C:\Program Files\Siemens\TNMS. If that
was the folder where TNMS ASON / Ethernet Manager was installed click “Next” or
click “Choose” to select the path to the folder where TNMS ASON / Ethernet
Manager was installed.
g The documentation and TNMS ASON / Ethernet Manager have to be installed
in the same folder
6. Verify the pre-installation summary. Click “Install” to continue or “Previous” to update
the install folder.
7. Click “Done” after the indication of successful installation.

A42022-L5981-A051-03-7618 45
Issue: 3 Issue date: August 2007
Getting Started User Manual (UMN)

5 Getting Started
This chapter provides information on how to start using TNMS ASON / Ethernet
Manager.
After the installation procedures have been executed the TNMS ASON / Ethernet
Manager is ready to be used.
To start using TNMS ASON / Ethernet Manager the following operations must be con-
sidered:
– Starting TNMS ASON / Ethernet Manager server (see Chp. 5.1)
– Starting a TNMS ASON / Ethernet Manager client session (see Chp. 5.2)

5.1 Starting TNMS ASON / Ethernet Manager server

TNMS ASON / Ethernet Manager server needs to be started before making the user
logs in through TNMS ASON / Ethernet Manager client.
Starting TNMS ASON / Ethernet Manager server
The TNMS ASON / Ethernet Manager server is started via the “Services” window of the
installed Windows OS(c).
To start TNMS ASON / Ethernet Manager server do the following:
1. Open the “Control Panel” window of Windows OS(c).
2. Double-click the Administrative Tools option to open the “Administrative tools”
window.
3. Double-click the Services to open the “Services” window.
4. From the available services list, locate the “TNMS Vxx - Packet Manager” service
and select the “start” option from the context menu.
Wait until the status of the service passes to “started”.
5. Close opened windows.
Stopping TNMS ASON / Ethernet Manager server
To stop TNMS ASON / Ethernet Manager server processes open the “Services” window
of Windows OS(c) and select “stop” from the context meu of the “TNMS Vxx - Packet
Manager” service.

5.2 Starting a TNMS ASON / Ethernet Manager client session

The TNMS ASON / Ethernet Manager client session is started by clicking a shortcut icon
created in the desktop (if it was the option select during installation) or by clicking the
TNMS ASON / Ethernet Manager icon in the folder selected for the ASON / Ethernet
Manager installation. Once the TNMS ASON / Ethernet Manager has been started, the
operator can enter the login data. Functions authorized by the user’s access rights can
now be accessed.
– Default available user - Administrator
– Default user group - Administrators
– Default policy - Global
– Default domain - Global
This user has all access rights within the TMN system.

46 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Getting Started

If the TNMS ASON / Ethernet Manager server is not available, an error message is dis-
played.

A42022-L5981-A051-03-7618 47
Issue: 3 Issue date: August 2007
Getting Started User Manual (UMN)

5.2.1 Default username and password

After installation and TNMS ASON / Ethernet Manager server start, the system can be
immediately operated by using the default user and password. Both fields are case sen-
sitive.
– User name: administrator
– Password: administrator
For security reasons, the administrator is requested to change the password.

5.2.2 Changing the password

Changing the user password is done in the “Change Password” window accessible
through the Security menu. The user is asked to enter the old password and the new
password twice as confirmation.
TNMS ASON / Ethernet Manager stores the history of passwords registry in the LDAP
database.
Password complexity rules
New passwords are validated by the system according to the following rules:
– Password should be at least 8 characters.
– Password should not be the same as the user id.
– Password should not contain the user id.
– Password should not contain a rotated version of the user id.
– Password should contain at least 2 alphabetic characters.
– Password should contain at least 1 numeric character.
– Password should contain at least 1 special character other than the ones from the
set #, $, *, / and @.
– Password should contain at most 3 consecutive digits or letters from the alphabet.
– The new password and the old password must differ by at least 3 characters. This
is enforced only if the password is changed through the “Change Password”
window.
– Password should not match any of the previous 12.

5.2.3 Terminating an TNMS ASON / Ethernet Manager client session

A TNMS ASON / Ethernet Manager client session is terminated when the user logs off.
All windows are closed and access is only provided to the login function.

48 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

6 Operation
This chapter provides information on how to operate with TNMS ASON / Ethernet
Manager. The following topics are described in detail:
– General information (see Chp. 6.1)
– Graphical user interface (see Chp. 6.2)
– Network configuration (see Chp. 6.3)
– ASON management (see Chp. 6.4)
– Ethernet management (see Chp. 6.5)
– Viewing logs (see Chp. 6.6)
To start operating TNMS ASON / Ethernet Manager the Installation (see Chp. 4) and
Getting Started (see in Chp. 5) procedures must be taken first.

6.1 General Information

This chapter provides general operation information about TNMS ASON / Ethernet
Manager system. TNMS ASON / Ethernet Manager client graphical user interface is
Microsoft Windows based.

6.1.1 Working with the mouse

Both the left and the right mouse button are used when working with the GUI. The left
mouse button may be used for the following actions:
– Select a function using the features available in a window (buttons, selection menus
etc.)
– Select a menu item
– Select a toolbar button
– Confirm an action (e.g., Apply)
The right mouse button may be used for the following actions:
– Select a context menu in a window
– Select a context menu in the network map
A great number of operations can only be invoked via context menus. A context menu
is called by clicking an object of the graphical user interface with the right mouse button.
This displays a selection of menu items which are relevant for the selected object in the
given situation.
g The offered menus and context menus depend on the user’s access rights.
g Unless the text states otherwise, always use the left mouse button for clicking and
double-clicking.

6.1.2 Working with the keyboard

The TNMS ASON / Ethernet Manager user interface is driven by context menus (click
on objects in the user interface with the right mouse button) and therefore would not be
advised to operate without a mouse. Therefore this manual refers throughout to mouse
control. However, it is possible to use the keyboard to perform the standard operations.
The following table shows a selection of standard keyboard operations:

A42022-L5981-A051-03-7618 49
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Keyboard Action
Operation
Ctrl+Spacebar Displays contextual menu in Multiple Document Interface (MDI)
windows
Ctrl+F6, Navigates among associated internal windows on the backing
Ctrl+Shift+F6 window and between an internal window and an associated
secondary window
Spacebar Switches the setting of the checkbox, activates focused button,
Turns on radio button, Activates toolbar button
Enter, Return Activates default button (does not require keyboard focus)
Escape Activates Cancel button (does not require keyboard focus)
F10 Moves focus to menu bar and posts first menu
Shift+F10 Displays contextual menu
Alt+F6 Navigates into secondary window; when in secondary window,
navigates to the associated higher-level window
F1 Displays context sensitive On-Line help window

Table 7 Selection of standard keyboard operations

g In this manual it is presumed that the operator works with a mouse.

6.2 Graphical user interface

The TNMS ASON / Ethernet Manager client GUI provides access to all the functions of
the network at the logical level.
The TNMS ASON / Ethernet Manager client GUI starts with a main window containing
a menu bar, a toolbar and a status bar. These bars allow to open other windows.

50 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

6.2.1 Main window

Figure 24 shows an example of the TNMS ASON / Ethernet Manager main window indi-
cating some of the available functions.

Figure 24 TNMS ASON / Ethernet Manager main window

6.2.2 Menu bar

Figure 25 shows the menu bar of the TNMS ASON / Ethernet Manager main window
with its menu items. When you click on one of these menu items, the pull-down menu,
specific to the menu item, opens.

Figure 25 Menu bar

Table 8 provides a description of the Menu bar entries.

Menu Description
File Contains functions to export, import configurations, save and print
the presently opened window, and to exit the TNMS ASON / Ethernet
Manager client session.
View Contains items to open different application windows.

Table 8 Menu Bar Entries

A42022-L5981-A051-03-7618 51
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Fault Contains functions of the fault management for TNMS ASON /

Ethernet Manager.
Configuration Contains different functions, e.g. EM/NE, VLAN and service
management as well as customer management.
Security Contains functions of the security management.
Options Opens the "General Settings" window where you can customize
client settings.
Window Contains funtions to arrange the application windows.
Help Contains functions to open the online help and to get further system
and product information.

Table 8 Menu Bar Entries (Cont.)

6.2.3 Toolbar
The toolbar (see Figure 26) runs along the top edge of the main window above the
working area. Clicking on one of these buttons provides access to frequently used func-
tions.

Figure 26 Main toolbar

Table 9 provides a detailed description of the Menu bar entries.

Icon Function Menu Entry Opens Window

Log in or log off the Security menu -> Login... Login
TNMS ASON / entry
Ethernet Manager
client

System log View menu -> System System Event Log

Event Log... entry

Locates an NE on the View menu -> Find NE in Find...

network map or on Physical View... entry
the "EM/NE
Management"
window.
Network map View menu -> Network Network Map
Map... entry

Topological tree View menu -> Topological Topological Tree

Tree... entry

Table 9 Main toolbar icons

52 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Icon Function Menu Entry Opens Window

Displays a list of all Fault menu -> Alarm Alarm List
currently raised List... entry
alarms
Customer Security menu -> Customer
administration Customer Administration
Administration... entry
New Call... Configuration menu -> New Call
Call entry -> New... entry

EVC management Configuration menu -> EVC Management

EVC entry -> Management
entry
EM or NE Configuration menu -> EM/NE
management EM/NE Management entry Management

Online help Help menu -> TNMS TNMS ASON /

ASON/Eth Manager Help Ethernet Manager
entry Help

Table 9 Main toolbar icons (Cont.)

6.2.4 Status bar

The status bar runs along the bottom of the main window. It gives information about the
operating states and displays important messages, in a short form, such as alarms.

Figure 27 Status bar

Area Description
Notification area Displays a short help message when the mouse points
on a main menu item or main toolbar button.
Operator Displays the User ID of the operator currently logged in.

Table 10 Status bar components

A42022-L5981-A051-03-7618 53
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Server IP address Displays the IP address of the connected server.

Time Displays the selected time format i.e., GMT or CST.
Planned Network Status Displays the synchronization status of the actual
network regarding the stored planned network.
Activation Feedback Displays the number of activation notifications that are
stored, in accordance to the user preferences, and the
number of unacknowledged activation notifications.
Global alarm counter Alarm severities and counters for each severity i.e.,
indeterminate, critical, major, minor and warning.
Data semaphore Displays the current client\server connection and
transaction status via different icons.

Table 10 Status bar components (Cont.)

6.2.5 Filtering and Sorting

For windows listing objects, e.g. calls or EVCs, a particular filtering and sorting mecha-
nism exists. When opening such a window first the “Filter and Sort” window appears
allowing to restrict the amount of list entries according to specific criteria and to sort the
entries in a reasonable order.

Object window Filter and Sort window

Component Link Request Component Link data with Filter and Sort
management
TE-Link management Request TE-Link data with Filter and Sort
LSP management Request LSP data with Filter and Sort
Call management Request Call data with Filter and Sort
EVC management Request EVC data with Filter and Sort

Table 11 Object windows and corresponding “Filter and Sort” window

The “Filter and Sort” window is also started via the Filter and Sort button from an
opened list window.

6.3 Network configuration

This chapter explains how to setup the network structure in TNMS ASON / Ethernet
Manager. Network configuration means adopt the physical network structure in the
TNMS ASON / Ethernet database and mapping this network structure to a topology map
showing the managed network in a graphical manner.
To perform these tasks TNMS ASON / Ethernet Manager provides the following func-
tions:
– EM/NE management
– Topology Management

54 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

These functions are described more detailed in the following chapters. For a detailed
description of all GUI windows and functions mentioned in this chapter please refer to
the TNMS ASON / Ethernet Manager online help.

6.3.1 EM/NE Management

EM/NE management covers functions for handling and administering network elements
in TNMS ASON / Ethernet Manager. The management of the EM/NE objects is synchro-
nized with TNMS Core Server, through an internal TNMS Core Bridge connection.
It is mandatory to have the TNMS ASON / Ethernet Manager installed together with the
TNMS Core/CDM to have proper access to the EM/NE Management functions. For
more information on the installation of TNMS ASON / Ethernet Manager and additional
packages, please refer to chapter 4.

6.3.1.1 Handling EM/NE

EM/NE management provides the "EM/NE Management" window (see Figure 48) that
gives an overview of all the EM/NE managed objects and their interrelationship e.g.,
which NEs are managed by a specific DCN channel. The current states of the EM/NE
objects is also provided.
There are several operations that allow the user to handle EM/NE objects, namely:
– Create and delete EMs and modify their properties. In addition, the user can also
duplicate NEs. This operation consists of creating a new NE based on an existing
one.
– Move NEs. It is possible to move NEs easily from one element manager to another
with drag and drop. To do this the NE must be in state “deactivated”.
– Search for an EM/NE object. For operations dealing with a large number of EM/NE
objects, a search mechanism is available. The EM or NE relevant for the intended
user operation to perform can be found via the “Find EM/NE” window
– Change the activation state of each element manager/network element object via an
activation check box. When the user activates an EM/NE object, its state switches
to running. If the server is running, connections will be established or cut off depend-
ing on the user input.
Information for each EM/NE object managed is stored in the database, e.g., object iden-
tifier, hierarchical information, activation state, object type information (i.e. object prop-
erties template, capabilities, containment rules). This information is configured via the
EM/NE property pages.
The possible EM/NE object states are listed in Table 12.

Icon State Description

EM/NE object is deactivated (configuration state), e.g.,
Deactivated the object is not in use by the system (means also that
no connection will be established to this object).

Table 12 EM/NE state icons

A42022-L5981-A051-03-7618 55
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Icon State Description

EM/NE object is in use by the system but there is no
Disconnected connection established to this object (e.g., after
disconnect or activate command by the operator).
System is trying to establish a connection to the EM/NE
Connecting
object.
Connection to the EM/NE object has been successfully
Connected
established.

Starting up EM/NE object is initializing its data.

EM/NE object has successfully finished its initialization

Running
and is ready for operation.
EM/NE object has not successfully finished its
Init Failed initialization and is inoperable; only re initialize is
available via the Client.
EM/NE object is saving its data and releasing its
Shutting down
subcomponents.

Disconnecting System is disconnecting from the EM/NE object.

Connection to the EM/NE object has been lost (contrary

Connection Failed to disconnected initiated by the operator) or connection
cannot be established.
At least one property of the EM/NE object is invalid
Invalid properties (EM/NE object cannot be used). The operator has to
complete or correct the properties.
NE in Maintenance operational state. All alarms are
Maintenance state
suppressed and therefore not reported to the server

Table 12 EM/NE state icons (Cont.)

6.3.1.2 Information about the EM/NE state

The EM/NE Management is responsible for the generation of alarms in case of EM con-
nection, interruption and (re)establishment.
State information is available through the “EM/NE State Summary” window for both EMs
and NEs. This information includes the total number of objects managed, as well as the
number of objects in a particular state. The possible states are Deactivated, Discon-
nected, Failure, Starting Up and Running:

56 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 28 EM/NE State Summary window

The lengths of colored bars reflect the relationships between the total number of EM/NE
objects in particular states to one another. The correspondence between the EM/NE
states described in Table 13 to states considered in the figure Figure 28 are presented
in the following table:

EM/NE state (as defined in “EM/NE EM/NE state icons (as defined in Table 12)
State Summary” window, Figure 28)
Deactivated Deactivated
Disconnected Disconnected
Connecting
Shutting down
Disconnecting
Starting up Connected
Starting up
Running Running
Failure Init Failed
Connection failure
Invalid propertiesFailure

Table 13 EM/NE state icons correspondence

6.3.1.3 Operational state

TNMS ASON / Ethernet Manager provides a direct way to switch the operational state
of the NEs to Maintenance and back to Operation. This feature is used when an NE or
group of NEs needs to be maintained, i.e., all alarms are suppressed and not reported
to the server.
When in Maintenance state, the NE is provided with an overlay icon of a wrench to
indicate its Maintenance operational state.

A42022-L5981-A051-03-7618 57
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Figure 29 NE Maintenance state

The Maintenance and Operation state can be set in the "Network Map" and in the
"EM/NE Management” window via the NE context menu.
The operational state can also be applied simultaneously to a selection of NEs.

6.3.2 Topology Management

Most of the network operators have to regularly perform routine tasks on the network;
e.g., network surveillance, service provisioning. To help perform these tasks topology
management provides a network map.

6.3.2.1 Network Map

The "Network Map" window is represented in Figure 30.

58 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 30 Network Map window

The "Network Map" window offers a physical view of the network and provides the fol-
lowing main functions and applications:
– Network Element (NE) symbols: an NE is displayed in a network with an NE symbol.
These symbols hold specific data for an NE, e.g., position, description, icon, alarm
states. The user can create NEs by dragging NEs into the network map. For details
regarding the definition of NE symbols see chapter 6.3.2.2.
– Hierarchical Topological Container (TC) navigation: a topological container defines
a containment relationship between other topological container and/or network ele-
ments. This means they may contain NE symbols and other TCs. The network map
is always associated with one TC, which corresponds to a network view. A hierar-
chical TC navigation is supported. The operator can change the active topological
container by double clicking on the TC symbol or on the TC delimitation border.
Other TC navigation facilities are also provided, for example, going back to the
previous TC and forwarding to return to the actual TC. These navigation facilities are
similar to the regular Web browsers. For details regarding the definition of TC see
chapter 6.3.2.3.
– Topological container image assigning: The user is able to assign an image to the
TC background. This image can be a map containing real geographical information,
or just another image the operator desires, in order to organize his view.
– Topological container resizing: the network map also provides TC resizing to
include/exclude other TCs or NEs in/from the topological container.
– TC and NE geographical positioning: each NE or TC has a well defined geographical
position, based on an absolute 2-dimensional coordinate system.
– Physical Trails (PT): representation of physical trails between two network elements
or topological containers.
“Network Map” window shows those PTs that are created in TNMS ASON / Ethernet
Manager. For details regarding the definition of PT see chapter 6.3.2.4.

A42022-L5981-A051-03-7618 59
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

g PTs and GFPG trails retrieved by TNMS Core SDH bridge are visible only in the
“Ethernet Logical Map” window (see Figure 47).
– Network map zooming: the network map supports optical zooming, this allows
enlarging/shrinking the background bitmap and scale. The size of the NE symbol is,
however, independent of the zoom factor.
– Topology user profile: The user profile can be considered as a filter that defines
which part of the network the user wants to control. The user selects the TCs which
are relevant and creates the profile. Only the information from the selected TCs is
shown e.g., if the alarm list or alarm log is opened from the context menu of the topo-
logical tree only alarms from relevant NEs are displayed. All TCs and NEs within the
TCs which are not marked are displayed in a grey color.
The information available in the "Network Map" window, e.g. TCs and NEs, is shared by
all the clients connected at the same time.
The set of objects displayed in the actual network map is determined according to the
following rules:
– The geographical position of the objects must reside within the viewed rectangle;
– The objects are logically contained in:
– the actual TC
– or, in one of its direct children TCs.
g It is possible to have an NE logically contained in more than one TC.
Due to the high number of supported NE symbols, the amount of data to be shown in
the content of a TC is filtered. This is done in order to prevent objects from appearing in
such a small size that they are unrecognizable. Therefore, not all the NE symbols and
children TCs residing in the viewed rectangle are displayed.
Topological tree
In addition to the "Network Map" window, a "Topological Tree" window is available. This
tree contains a hierarchical display of the TCs and the NEs. Each item of the tree shows
the TC/NE name, icon and the highest alarm severity.

60 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 31 Topological Tree window

The highest alarm severity of a TC is calculated from its logical children, e.g., a TC
contains several NEs with different alarm severities, the NE with the highest alarm
severity is major, the TC shows the alarm severity: major. The geographic position of
the TCs and NE symbols is not considered in the tree.
The "Topological Tree" window allows to drag and drop:
– NEs into the network map.
– NEs into the "Physical Trails" window
– NEs into the "Physical Trail List" window
It also allows to locate NEs in the network map.
The NE symbols in the "Topological Tree" window can be used as a drag source, and
the TCs can be used as a drop target for NEs. If an NE is dropped into a TC on the
network map, an NE symbol will be created at the center of the target container.
It is possible to focus on a part of the network by marking the relevant TCs. As a conse-
quence, all the TCs and NEs within the topological containers that were filtered out are
displayed in gray. Another result is that if the user opens the alarm list or log, from the
topological tree context menu, only the alarms from relevant NEs are displayed.

6.3.2.2 Handling NEs

Network elements are displayed on the "Network map" window by means of NE symbols
or small NE symbols (see Figure 32), as follows:
– NE symbol - graphical or technical icon (32x32 pixels) containing the following infor-
mation:
– operational state: an overlay icon on the main icon
– communication state: a state icon on the upper left side, if is not connected
– write access state: a state icon on the lower left side

A42022-L5981-A051-03-7618 61
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

– highest alarm severity: a state icon on the upper left side, if the communication
state is connected
– alarm acknowledge state: an overlay icon on the alarm severity state icon
– Small NE symbol - small icon (24x24 pixels). If the alarm acknowledge state is unac-
knowledged a small red box is displayed instead of a small icon.

Figure 32 NE symbol and small NE symbol

Write access state of the NE is provided by the means of small icon in the main icon. A
description of the possible write access states is given in Table 14.

Icons Write access

No write access

External system has write access

NE controller has write access

Element manager has write access

Element manager and NE controller have write access

Table 14 Write access states icons

The communication state information of the NE is provided by the communication state

icon, which is part of the main icon. A description of the possible communication state
icons is given in Table 15.

Icons Communication state

Disabled

Disconnected

Connecting

Disconnecting

Connected

Table 15 Communication state icons

62 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Icons Communication state

Init failed

Running

Table 15 Communication state icons (Cont.)

An NE is displayed as an NE symbol if it is a direct child of the actual TC, or one of its

parent TCs.
An NE is displayed as small NE symbol if it is a direct child of a subsequent TC (level
2). For details regarding the definition of TC (level 2) see Figure 32.
NE symbols, small NE symbols and TC may overlap each other. In this case the appear-
ing order will be: TC, small NE symbol, NE symbol. This ensures that an NE symbol will
never be overlapped by a small NE symbol or TC.
The user can drag and drop NEs from the “EM/NE Management” window to build the
network.

6.3.2.3 Topological Container Properties

A topological container is represented as follows:
– by its window origin and window extent
– by an object of the network map defining a limited region, a so called TC rectangle,
on the network
– by a topological container icon
Figure 33 shows the TC possible representations.

Figure 33 Topological container representation

TCs are created hierarchically (see Figure 33). This means that TCs may contain NEs
and other TCs. All NEs and TCs residing entirely in the TC rectangle are considered

A42022-L5981-A051-03-7618 63
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

geographically contained in the TC. This concept enables the definition of a logical struc-
ture similar to a directory. However, it is important to be aware that the positions of NEs
and TCs are absolute values in the fixed coordinate system of the network map.
There is a TC that is on the highest position on the hierarchical structure: the root-TC.
This TC is automatically created and cannot be deleted. It is the only TC that has no
parent. As a consequence, the root-TC appears as the top TC representing the
complete network view.
Each NE or TC has a well defined geographical position, based on an absolute 2-dimen-
sional coordinate system. All NEs and TCs use the left upper corner of the root-TC as a
reference point. The dimensions (X,Y) are the height and the width of the NE or TC.
A TC has a position and a background image associated with it, as an option, e.g., a
geographical map.
g The background images are not mandatory. The user may provide an image if
desired.
The following rules define the relationship between graphical and logical containment:
– An NE symbol must have an unique topological container owner. The NE symbol
must have at least one TC as a logical parent. Please note that several logical
parents can be assigned to an NE symbol. The TC owner and the logical parents
TCs must contain, geographically, the NE symbol.
– An NE symbol is graphically contained in a TC its position is contained in the area
defined by the origin and extent of the topological container.
– A TC must have another TC as logical parent. The TCs cannot have more than one
logical parent. TCs do not have owner. A logical parent TC must contain, geograph-
ically, the child TC.
– A TC is graphically contained in a TC if its is contained in the area defined by the
origin and extent of the topological container.
– Objects completely contained in a TC do not entail a logically containment in that
TC, e.g., if a TC “A” (or NE “A”) is contained in another TC “B”, this does not mean
that TC “B” is the logical parent of the TC “A” (or NE “A”).
Changing the local parent allows the modification of logical containment, as stated
above: if an object is contained in a TC, it does not mean that the object is a child of that
TC. In order to set an object as the child of a certain TC, a change of local parent oper-
ation has to be performed. The user has to select a new logical parent from a list con-
taining all possible TCs.
Display of topological containers
The actual TC is represented by its window origin and window extent. Inside this con-
tainer TCs can be displayed in the following modes:
– Transparent frame mode: represented by a frame with a size and position according
to the origin and extent of the TC.
– TC icon mode: represented by a graphical icon. It has the following attributes:
– TC name: shown below the icon
– Highest alarm severity: shown as state icon on the left
– Alarm acknowledge state: shown as an overlay icon on the highest alarm
severity state icon.

64 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

The TC is displayed as a transparent frame (level 1), if the TC is the direct child of the
actual TC.
The TC icon mode (level 2) is displayed if the TC is a direct child of a TC displayed as
transparent frame (direct child of the actual TC).
Figure 33 shows three topological containers: The actual TC, a TCs displayed in trans-
parent frame mode and a TC displayed in icon mode, e.g., the actual TC is represented
by its window origin and window extent, the container level 1 has the actual TC as logical
parent; and the container level 2 has the container level 1 as logical parent.
Handling topological containers
To define a topological container the user chooses New Topological Container Item
in the context menu or toolbar of the "Network map" window. The mouse cursor changes
its shape and the operator can expand a rectangle with the mouse to define the TC
boundary. The TC is created, when the mouse button is released. After the creation of
a new topological container the TC properties window is opened automatically.
Scrolling and zooming is not possible while defining a TC. Before creating a TC, be sure
that the total area to be covered by the new TC is well defined and correct.
The user can create overlapping TCs, but must ensure that the owner of the new created
TC is always the active one. To create a TC within another TC, the user has to navigate
through it, e.g., zooming, into this container by double clicking on it.
When zooming to a contained TC, the user double clicks on the area of the container;
this way the user navigates into the selected TC. Other navigation facilities are also pro-
vided:
– The back navigation leads to the container previously shown
– The forward navigation undoes a back navigation
– The up navigation leads to the logical parent of the actual TC
– The root navigation leads to the root TC
Zooming into a TC (by double clicking) enlarges this container and shows all its NEs in
full size. If the destination NE of a Physical Trails (PT) lies outside the visible area, then
this PT is just clipped at the view port edge. In this case, a small text label is displayed
at the view port edge indicating the destination NE of the PT.
g It is also possible for the user to open a new window that shows all the contents of
a TC.
If a PT leads out of the container, the operator can follow this link by clicking on the node
at the end of the link, thus navigating to another TC.

A42022-L5981-A051-03-7618 65
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Figure 34 Navigation within topological containers

Resizing topological containers
If a topological container is reduced and a logical child TC (or NE) of this topological con-
tainer is no longer enclosed completely, the topological container can no longer be a
logical parent for this child TC (or NE). So, if the topological container was the owner of
the NE, the new owner will be automatically the parent of the resized topological con-
tainer. See Figure 35 Example 1.
If a TC is enlarged and now encloses completely another TC (or NE), which has the
same logical parent as the resized TC, then a dialog is opened where the user can add
one additional logical parent to the new enclosed TC (or NE). See Figure 35 Example 2.
If a TC is reduced and its new area is completely enclosed by another TC, then a dialog
is opened where the user can add one additional logical parent to the resized TC. See
Figure 35 Example 3.

66 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 35 Resizing TCs

The TC deletion operation requires confirmation. After confirming the deletion, the NEs
owned by all the deleted TC will have as the new owner the logical parent of the deleted
TC.
g An NE symbol or Topological Container can be geographically contained in more
than one Topological Container. An NE symbol can have more than one logical
parent. Nevertheless there is one, and only one, Topological Container owner for
every NE.

6.3.2.4 Physical trail

Trails are represented as Physical Trails (PT). They connect two Physical Termination
Points (PTP) on a physical layer rate, but may also contain non-physical layers.
The user can create PTs in TNMS ASON / Ethernet Manager and modify those physical
trails.
When a PT is created, it is stored in the database. In addition, it is stored in the partici-
pating NEs, if this is supported by the NEs and if the NE is in running state.
It is also possible to delete physical trails. Before deleting the PT from the database, PT
information is deleted in the NE. If the NE is not in the running state, a warning is given
to the user asking whether the PT should be deleted or not.
PTs retrieved from SDH bridge
There are PTs created in TNMS Core/CDM that are retrieved to TNMS ASON / Ethernet
Manager through the SDH-bridge, i.e. those that support the GFPG trails needed to the
Ethernet related services. These PTs are not visible in the “Network Map” window as
they are managed in TNMS Core/CDM.
The PTs retrieved from TNMS Core/CDM are only visible in the “Ethernet Logical map”

A42022-L5981-A051-03-7618 67
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

window of TNMS ASON / Ethernet Manager.

For ASON related services, all PTs are created in TNMS ASON / Ethernet Manager.
Physical Trail window
The PT window supports graphical creation and display of PTs.
This window can be opened in the global context or in the context of one NE. If it is
opened in the global context, both lists remain empty. If it is opened in the context of an
NE, the left list displays the PTPs of the selected NE. If two NEs were selected, the list
shows the PTPs of one of the NEs.
To fill an empty list, the user must drag and drop an NE into the list. Please note that an
NE can also be chosen twice. To change the list content an NE can be dropped into a
list. For large NEs, it is recommended that the user sets the filter first and then drags the
NEs to the list.
A filter facility with following options is provided at the top of the window:
– Layer: allows filtering of the PTP list for PTPs which contain the selected transport
layer.
– Port Status: allows filtering of the PTP list for connected or unconnected PTPs, as
well as filtering for connection direction.
To create a PT, the user has to select a PTP in the left and right list and press one of
the Connect buttons. After creation of the PT the "Modify Physical Trail" window pops
up automatically, the user can then modify the PT data.
A list is available to inform the user about the PTs that are available in the system.
Because a high number of PTs might be available, the user can define the page size
(number of records, which is transferred from the server to the client per step). To nav-
igate, the user can press next/previous page or jump to the desired record. The total
number of records, which are available in the database, regarding the current filter, is
displayed.
Graphical Links
A Graphical Link (GL) represents one or more PTs between NEs or TCs via a graphical
line. This representation is helpful for storage of additional information, e.g., maximum
bandwidth or geographic coordinates. GLs between TCs exist only if the TCs have the
same grand parent TC and are shown only if both TCs are visible as icons.
If one NE, making part of a GL, is outside the current Topological Container, only a part
of the GL is visible. This is the case that a GL leads out of a container. The operator can
follow this link to the other end by clicking on the node at the end of the link. Thus a nav-
igation to the owning container of the other NE is done.
Graphical Links are displayed as a thick line when connect NEs between TCs that are
children of the actual TC; or if one of the connected NE Symbols is displayed in large
size. Otherwise it is displayed as a thin line. The GLs, which are displayed as a thick
line, contain the alarm severity information and operational state. Graphical links can
never be created nor deleted explicitly:
– They are created implicitly by the topology management component, if the first PT
between two NEs or TCs is created.
– They are deleted implicitly by the topology management component if the last PT
between two NEs or TCs is deleted.
For data reduction reasons not all GLs in the currently visible geographical region are
shown. A GL is shown if at least one of the connected NE symbols is visible or if both
TCs are visible as icons. Figure 36 shows an example of GLs between two TCs visibility.

68 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 36 Graphical links

If a graphical link leads out of the currently displayed TC, a small connection box is
shown at the border of the TC. The operator can follow this link to its other end by double
clicking on the small connection box at the end of the link. The tool tip for the small con-
nection box shows the name of the other NE symbol and the name of its TC owner.

6.4 ASON management

ASON Manager is a component of TNMS ASON / Ethernet Manager that provides all
functions to the provision of end-to-end connections between ASON-capable network
elements.
ASON Manager is used to manage Calls, LSPs, TE-Links and Component Links. It
provides an ASON logical map where the network composed of NEs with ASON capa-
bilities is shown.
As a prerequisite to create an ASON network, all physical interfaces to be used by
GMPLS control plane need to be configured.
General steps before creating Calls
Calls are the relations between two endpoints within ASON domains.
The following general steps must be taken to create calls:
1. Adopt / Create NEs in the ASON logical map.
2. Plan the network and activate the NEs.
3. Create Component Links / TE-Links.
4. Create Calls.
The cover these steps explaining how to operate TNMS ASON / Ethernet Manager con-
cerning its ASON capabilities.

6.4.1 ASON Logical Map

The “ASON logical map” window allows the operator to visualize a logical map contain-
ing only ASON relevant resources, i.e. NEs, links and associated configurations.
The “ASON logical map” window is opened from the View -> ASON -> Logical Map
menu item and has the following functions:
– Show NEs with ASON capable ports
– Display TE-Links as virtual links
– Highlight / Unhighlight call working and protection paths
– Highlight / Unhighlight LSP working and protection paths

A42022-L5981-A051-03-7618 69
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

The NEs in the ASON Logical Map are those NEs shown in the Network map that have
ASON capabilities.

Figure 37 ASON logical map window

The window offers several tools such as highlighting/unhighlighting Calls and LSPs:
Highlight Call
To highlight a call in the ASON logical map, do the following:
1. Click the Highlight pull-down menu on the toolbar and select “Highlight Call”.
The “Call Selection” window is opened.
2. In the “Call Selection” window, select the Call to highlight.
3. Click the Ok toolbar button.
The ASON logical map highlights the corresponding resources of the call, namely the
call working path and the call protection path. Different colors are used to highlight the
working and protection calls. These colors are user configurable.
Alternatively, it is possible to highlight a call using the “Call Management” window.
Highlight LSP
The process to highlight a LSP is identical to the one used to highlight a call.
In the ASON logical map, do the following:
1. Click the Highlight pull-down menu on the toolbar and select “Highlight LSP”.
The “LSP Selection” window is opened.
2. In the “LSP Selection” window, select the LSP to highlight.
3. Click the Ok toolbar button.
The ASON logical map highlights the correspondent resources of the LSP. Different
colors are used to highlight the working and protection LSPs. As in calls, these colors
are user configurable but must be different from the colors used in call highlight.
Alternatively is possible to highlight a LSP using the “LSP Management” window.
Unhighlight Call/LSP
To unhighlight Calls/LSPs click the Unhighlight button on the toolbar.

6.4.2 NE management
The NEs to use in the ASON related connections need to be configured as follows:
– Ports to be used as component links: “Port Classification” as “I-NNI”.
– Ports to be used as call endpoints: Type “Non-GMPLS”.
– Ports for all interfaces: “Administrative state” as “Up”.

70 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

To configure a NE, the operator must open the related LCT, e.g. by double clicking the
NE in the network map.
g To understand how to configure ports please refer to the NE specific documenta-
tion.
List ASON NE Ports
To list all ports of an NE, do the following:
1. Open the ASON logical map.
2. Open the context menu of a selected NE/group of NEs, and select the “List ASON
ports” option. The “ASON NE Ports” window will be opened.
3. Drag the NE from the “TNMS ASON/Ethernet Manager Physical Map” and drop it in
the “NE” field.
The list of ASON ports for the given NE is displayed as shown in the next figure:

Figure 38 ASON Ports window

6.4.3 Component link management

A Component Link is a connection between two ASON ports.
The “Component Link Management” window allows the filtering, creation and deletion
of component links and is opened from the Configuration -> Component Link -> Man-
agement... menu item.
There is also a “Component Link details” window to show the configurations of a partic-
ular Component Link.

A42022-L5981-A051-03-7618 71
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Figure 39 Component-Link Management window

When new network notifications are received and the table needs to be updated, a
warning message is displayed in the status bar. After the operator presses the Update
button the message is cleared.

6.4.3.1 Creating a Component Link

To create a new Component Link you click Configuration -> Component-Link -> New...
menu item and the “New Component Link” window is opened.

Figure 40 New Component-Link window

In the “New Component Link” window do the following:
1. Drag a NE to the “A node:” field
2. In the “A port” field, select the desired port
3. Drag a NE to the “Z node:” field
4. In the “Z port” field, select the desired port
5. In the “Administrate state” field, select the desired administrative state of the Com-
ponent-Link
6. Click the “Create” button in the toolbar
The creation results of the Component-Link are showed.

6.4.3.2 Component Link details

The “Component Link details” window shows the attributes for a selected Component
Link.The “Component Link details” window is opened by first selecting a Component
Link in the “Component Link” management window. After selecting the Component Link
from the available list, click the Details button and the “Component Link details” window
opens.

72 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 41 Component Link details window

Attributes of the selected component link, such as the name, the administrative state
and the actual/required states, are shown in the “Component Link details” window.

6.4.4 TE-Link management

TE-Links are connections between ASON nodes. They have traffic-engineering capabil-
ities which can be configured. A TE-Link consists of one or more Component Links.
The “TE-Link management” window allows the filtering, creation, modification and
deletion of TE-Links and is opened from the Configuration -> TE-Link -> Management...
menu item.
A Traffic Engineering Link (TE Link) groups one or more Component Links. According
to the number of Component Links that a TE-Link aggregates, we may classify a TE-
Link as:
– Unbundled: If the TE Link only has one underlying Component Link.
– Bundled: If the TE Link has more than one underlying Component Link.

Figure 42 TE-Link Management window

The provided table allows multiple selection of the TE-Links.

A42022-L5981-A051-03-7618 73
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

When network notifications arrive, a warning message is displayed in the status bar.
User must click the Update button to display the most recent list of TE-Links.

6.4.4.1 Creating a TE-Link

To create a new TE-Link you click Configuration -> TE-Link -> New... menu item and the
New TE-Link wizard is started.
The New TE-Link wizard consists of the following steps:
– Settings
– Component Links
– SRLG List
– Summary
Settings
In the settings page are configured the general TE-Link properties such as the name of
the TE-Link and the TE metric (used in CSPF calculations).
Component Links
In the Component Links page it is made the selection of the Component Links that
belong to the TE-Link. The operation is executed selecting entries from the “Available
Component links” list which is populated with all the Component Links that are config-
ured between the node A and the node Z (selected in the Settings page).
SRLG List
In the SRLG page are selected the shared risk link groups that the TE-Link is part of.
Summary
In the summary page it presented the status of the TE-Link creation.

6.4.4.2 TE-Link details

The “TE-Link details” window shows the attributes for a selected TE-Link.The “TE-Link
details” window is opened by first selecting a TE-Link in the “TE-Link” management
window. After selecting the TE-Link from the available list, click the Details button and
the “TE-Link Details” window opens.

74 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 43 TE-Link details window

The “TE-Link details” window is composed of the following tabs:
– General: Shows the TE-Link general properties.
– Links: Visualization of a list containing the links that are part of the TE-Link.
– SRLGs: Visualization of a list containing the shared link risk groups that the TE-Link
is part of.

6.4.5 LSP Management

The LSPs are managed in the “LSP Management” window. The “LSP Management”
window allows the filtering and modification of LSPs and is opened from the Configura-
tion -> LSP -> Management... menu item.

Figure 44 LSP Management window

When updates are needed, a message is showed in the status bar. Click the Update
toolbar button to update the current list.

A42022-L5981-A051-03-7618 75
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

6.4.5.1 LSP details

The “LSP details” window shows the attributes for a selected LSP and is opened from
the Configuration -> LSP -> Management... menu item.
The “LSP Details” window is composed of the following tabs:
– LSP: Shows the LSP general properties.
– Parent Call: Shows the LSP properties inherit from the parent call such as the call
name, the ending nodes and the administrative state.
– Hops: Visualization of a list containing the Hops of the LSP.
– Resources: Shows additional parameters of the LSP such as maximum bit rate and
burst sizes.

6.4.5.2 Relocating LSP

The Relocating of a LSP permits to modify a LSP already created. The modification of
a LSP consists in changing its hops or remove hops.
To relocate an LSP, do the following:
1. Select a LSP from the “LSP Management” window and click the Relocate LSP
button in the Toolbar. The “Relocate LSP” window is opened.
2. Add the TE-Links to be used as hops.
3. Add the TPs that are associated to component links and that are to be used as hops.
4. Click the Apply button in the toolbar to modify the LSP without closing the window
or click the Ok button to modify the LSP and close the window in one step.

6.4.6 Call Management

Calls are the relations between two endpoints (with working and protection path) within
ASON domains.
Management of calls is made in the “Call Management” window that lists the available
calls in the full ASON Network. The list of calls comprises calls of all the available ASON
domains connected to the server.
The window allows the creation, modification, filtering and deletion of calls.

Figure 45 Call management window

76 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

The functions are available from the toolbar buttons and from the context menu of a call.
The operator is able to use a filter and sort function to customize the list of calls.

6.4.6.1 Creating a Call

To create a new call you click Call -> New... menu item and the “New Call” window is
opened.
The “New Call” window is a wizard composed of the following steps:
– Settings
– TP Selection
– Setup
– Protection
– Working Path
– Protecting Path
– Summary
The operator, optionally, specifies the hops for working LSP and protecting LSP. The
LSPs are automatically created by GMPLS Controller at the NEs and their creation is
notified to TNMS ASON / Ethernet Manager.
The available path protection and restoration schemes are the following:
– 1+1 path protection
– Permanent 1+1 path protection + dynamic source route upon failure (DSR)
– Permanent pre-planned shared restoration+ dynamic source route upon failure
– Dynamic source route upon failure
TNMS ASON / Ethernet Manager offers a way to specify the hops for a Call. Operator,
when selecting the hops for the working or protecting paths of a call, is able to choose
one or more hops to belong to the path. For the same path, working or protecting, a
mixture of TE-Links or Component Links or TPs (within Component Links) can be
selected.
g Depending on the selected type of call that is being created, some of the attributes
of the “New Call” window are not configurable.
Settings
In the settings page it is made the configuration of the call general properties, such as
the Name and Type.
The call name is defined by the user and has to be unique for the whole TNMS ASON /
Ethernet Manager.
The prefix “TNMS:” is automatically added to the defined call name.
The specific call type depends on the end-points of the ASON Domain, e.g. GMPLS
calls.
TP Selection
In the TP Selection page it is made the selection of the A-End and Z-End nodes of the
Call, ports and labels.

A42022-L5981-A051-03-7618 77
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

The NEs must be dragged, e.g. from the ASON Logical Map or from the “Topological
Tree” window into the A-end and Z-end node fields. After the NEs have been selected,
the specific Ports and TPs must be selected from the available lists.
Setup
In the setup page the call setup properties are configured such as the Setup/Holding pri-
orities, the requested Ethernet bandwidth and the SONET parameters.
Protection
In the protection page the call protection properties are configured.
It is possible to specify which path protection and restoration scheme is used for the call.
The following parameters need to be configured:
– Protection Class
– Call reversion
– Diversity Type
– Wait to restore time
– Maximum number of recoveries for the call
– Protection switching history size
Working Path
In the Working Path page it is made the configuration of the call working path hops.
The user is requested to select the hops to be included on the working path and the hops
to be excluded from the same path.
There are two ways to select hops namely:
– Selecting TE-Links: It generates one hop per TE-Link.
– Selecting TPs:
1. Select a Component Link
2. Select the TPs from the TPs list
3. Select “Add as Hop”
The selected hops are shown in the “Select Hops” list. For each hop of the list the “Hop
Inclusion” and “Hop Type” parameters are editable. The “Select Hops” list enables the
user to order the hops manually.
Protecting Path
In the Protecting Path page it is made the configuration of the call protecting path hops
depending on the selected protection class value configured in the protection page.
The procedure is similar to that of the working path hops selection.
Summary
In the Summary page it is presented the status of the Call creation.
If the creation fails use the Back button to change the configuration and try to create the
call again.
If the creation succeeds, click the Close button to close the window.

78 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

6.4.6.2 Call details

The Call details window shows the attributes for a selected call and is opened from Con-
figuration -> Call -> Management... menu item. After selecting the call from the available
list, click “Details” button and the “Call Details” window opens.

Figure 46 Call details window

The “Call Details” window is composed of the following tabs:
– Description: Shows the call general properties.
– TPs: Visualization of call ingress and call egress nodes, ports and labels.
– Setup: Visualization of call setup properties such as hold off time and priority.
– Protection: Visualization of call protection properties.
– Working Path: Lists the call working path hops.
– Protecting Path: Lists the call protecting path hops.
All the information is read-only. To modify a call please refer to ch.6.4.6.3.

6.4.6.3 Modifying a Call

To modify a Call, do the following:
1. Select a Call from the “Call Management” window and click the Modify button in the
Toolbar.
2. Modify the desired Call attributes in the “Modify Call Wizard”. Non editable fields are
disabled.

A42022-L5981-A051-03-7618 79
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

g It is only possible to modify a call if ACS is not in state “Activating”, “Deactivating” or

RCS is not in state “In Deletion”.
A call of type FA-LSP is not possible to modify.

6.4.6.4 Configuring external switch requests

Different external switch requests are supported for calls.
The following commands are available from the Configuration -> Call -> External Switch
Request... menu item:
– Lockout of protection: is an external request which prevents the control plane from
switching to the protection path.
– Manual switch to working: is an external request which switches the traffic from
the working path to the protection path.
– Manual switch to protection: is an external request which switches the traffic from
the protection path to the working path.
– Clear: clears all the switch commands that were externally initiated. This is the
default value.
Only one external switch request is supported at a time and is visible in the “Protection”
tab of the “Call details” window.
All the listed commands are issued to the ingress node of the call.

6.5 Ethernet management

Ethernet Manager is a component of TNMS ASON / Ethernet Manager to manage
Ethernet services and Ethernet Virtual Circuits (EVC).
Ethernet Manager provides the following:
– NE management: Adopt, activate and synchronize data from NEs and create
network links between them.
– Graphical map visualization on a logical map: Visualize the network map containing
the NEs and the logical connections among them.
– EVC management: Provisioning of EVCs over the transport network, through GFPG
trails, with basic operations such as create, modify and delete.

Figure 47 Ethernet Logical Map window.

The first step to create a Ethernet Network is to classify a number of Physical interfaces
to be used by the control plane of TNMS ASON / Ethernet Manager.
Prerequisites

80 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

– All Port connections created in TNMS Core/CDM system.

– GFPG trails (e.g. transport trail between bridge WAN ports) created in TNMS
Core/CDM system and retrieved through the SDH Bridge.
– NEs adopted in the Topology Map of TNMS ASON / Ethernet Manager.
General procedure to create a new EVC
– Creating the EVC by selecting the end-points: A-end, Z-end.
– Selecting the VLAN processing mode and configuring other EVC attributes
Ethernet manager applies automatically the Ethernet service configurations end to end
in the network.

A42022-L5981-A051-03-7618 81
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

6.5.1 Interworking with TNMS Core/CDM

To handle EVCs and Ethernet Services in TNMS Ethernet Manager, the TNMS
Core/CDM system must be installed. The management of Ethernet services is done at
different levels in TNMS Core/CDM and at the logical level in TNMS Ethernet Manager.
TNMS Ethernet Manager
To create EVCs, Ethernet Manager is informed of the possible GFP Channel transport
paths available for transporting Ethernet EVCs. Ethernet Manager has no configuration
capability of the mapping function (e.g. GFP Channel bandwidth, GFPG to transport trail
assignment).
TNMS Core/CDM
TNMS Core/Element Manager manages the GFP mapping configuration (mapping from
WAN port with GFP Channel through GFP Group) to VC group TPs.

6.5.2 Activating and Adopting NEs

To use NEs under the TNMS Ethernet Manager, the NE has to belong to the list of sup-
ported NEs.
The following generic families of NEs are supported:
– SURPASS hiT7050/70
– SURPASS hiT7020/25/30/35/60/60HC
The NEs are handled as termination nodes of EVCs, containing Ethernet interface ports
on L2 (layer 2) type cards.
g To obtain the detailed list of NEs’ supported versions, please refer to the introduc-
tion chapter.
Adopting NEs
To adopt an NE into TNMS Ethernet Manager perform the following:
1. Open the EM/NE Object Management Tree.
2. Open the Network Map.
3. Drag an NE from the EM/NE Object Management Tree to the Network Map.

Figure 48 EM/NE Object Management Tree window.

82 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

While adopting the following symbol is shown in the Network map:

Figure 49 NE symbol in adoption

After adoption has been completed, the NE needs to be activated to be used with
Ethernet Manager in the creation of services.
Activating NEs
The activation of NEs is made in the “EM/NE Object Management Tree” window. To
activate a NE click in the NE associated checkbox.

A42022-L5981-A051-03-7618 83
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

6.5.3 Element Browser

Several operations in TNMS ASON / Ethernet Manager require a port selection or a NE
selection. The selection is done by means of drag and drop using the “Element Browser”
window.
The “Element Browser” window presents a hierarchy of elements. The top nodes are
containers which aggregate other containers and/or NEs.

Figure 50 “Element Browser” window

The following rules apply to the presented hierarchy:
– NEs can have several cards and logical ports.
– Cards can have several ports.
– NEs can be shown on more that one container.
Element Browser window update
The “Element Browser” window answers to network notifications such as update, delete
or new element. When such notifications’ arrive, the “Element Browser” window auto-
matically reflects the new information, i.e., updates the information for the modified
element, removes a deleted element or inserts a new element.
Element Browser window sort
The elements in the ”Element Browser” window are sorted with the following rules:
– Containers: ascending alphabetic order except for the root container that is the first
in the tree.
– NEs and Cards: ascending alphabetic order.
– Ports: by interface type. The order is UNI, NNi and PNI. Ports without interface type
always appear before the UNI, NNI and PNI ports. The ports without interface type
are ordered between themselves by location.

84 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

6.5.4 EVC Management

Management of EVCs is made in the “EVC Management” window that lists the available
EVCs in the Network. The “EVC Management” window allows the user to create, modify,
activate, deactivate, approve, filter and delete EVCs.

Figure 51 “EVC Management” window

The table of the “EVC Management” window allows multiple selection of the EVCs. The
toolbar buttons are only enabled if available for the selected items.
EVC Management window update
The “EVC Management” window answers to network notifications such as create,
modify and delete EVC infrastructure. Every time a notification is received, a message
is displayed in the status bar of this window warning the operator that the data might not
be updated.
To update the window press the Update button.

6.5.4.1 Supported scenarios

TNMS Core manages completely the Ethernet services of type point to point transparent
Ethernet services.
TNMS ASON / Ethernet Manager manages completely the VLAN Ethernet services and
not the point to point transparent Ethernet services.
Network Scenarios
The following network scenarios are fully supported by TNMS ASON / Ethernet
Manager:

Figure 52 Supported network scenarios: pure hiT70xx NEs.

A42022-L5981-A051-03-7618 85
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

Figure 53 Supported network scenarios: mixed hiT70xx NEs.

Service Scenarios
There are typical service scenarios managed by TNMS ASON / Ethernet Manager, all
based on point to point EVCs In the next sub-topics, some service scenarios examples
are illustrated.
In these scenarios, the VLAN endpoints and configurations are visible and managed by
TNMS ASON / Ethernet Manager.
The endpoints of an Ethernet service are visible and managed in TNMS Core/CDM
when a cross-connection between the LAN and WAN ports (XC) is reported.
Service scenario 1

Figure 54 Structure of service scenario with three EVCs.

In the illustrated scenario only one XC is reported for the first EVC (EVC 1). The subse-
quent configuration of VLANs or configuration of additional VLAN endpoints do not
generate more XCs.
Thus at any L2 switch card (between a pair of LAN and WAN ports where the multiple
Ethernet flows are switched) only one XC is reported between the TPs and only a subset
of the configured Ethernet services is visible at TNMS Core/CDM (in this case, only EVC
1).

86 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Service scenario 2

Figure 55 Structure of service scenario with two EVCs.

In this scenario only one XC for the LAN and WAN ports is reported, namely when the
EVC 1 is created. All other EVCs’ configurations (EVC 2) will not be visible at TNMS
Core/CDM.
Service scenario 3

Figure 56 Structure of service scenario with one EVC.

In this scenario the Ethernet VLAN service endpoints are visible at TNMS Core/CDM
although the VLAN configurations are only visible at the TNMS ASON Ethernet /
Manager.

A42022-L5981-A051-03-7618 87
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

6.5.4.2 Supported VLAN processing modes

A predefined set of VLAN processing modes is established, containing rules to be used
on the expected EVC scenarios and defining the values that must be used for each
parameter.
The following tables describe, for each of the supported NE families, the available pro-
cessing modes and the attributes that must be configured with each one.

VLAN Ingress Processing Egress

Processing processing
Mode
PVID Priority Tagging EtherType Egress
Mode (1) (1) Tagging (2)
None 1 Null IEEE802.1Q 0x8100 Untagged
Tagging [2,4094] [0, 7] IEEE802.1Q 0x8100 Untagged
Stacking [2,4094] [0, 7] Double Tag 0xFFFF Untagged
Adoption 1 Null IEEE802.1Q 0x8100 Tagged
Undefined Used for customized VLAN processing

Table 16 VLAN processing modes for hiT7020/30/35/60/60HC NEs.

g (1) These attributes are configured per L2 switch card.

(2) Egress Tagging is configured per port.

Ingress processing Egress

VLAN processing
Processing PVID Priority Tagging EtherTy VLAN admission Egress Tagging
Mode Mode pe (1) policy (2) (3)
None 1 Null IEEE802.1Q - admitAll Untagged
Tagging [2,4094] [0, 7] IEEE802.1Q - admitAll Untagged
Stacking [2,4094] [0, 7] Double Tag 0xFFFF admitAll (4) Untagged
Adoption 1 Null IEEE802.1Q - admitVlanTagged Tagged
Translation Outgoing VLAN ID [0, 7] IEEE802.1Q - admitVlanTagged Tagged
Undefined Used for customized VLAN processing

Table 17 VLAN processing modes for hiT7050/70 NEs.

g (1) This attribute is configured per L2 switch card and is relevant for processing
mode “Stacking”. Ports that are not in “Double Tag” mode use always “0x8100”.
(2) Not used in hiT7020/30/35/60/60HC NEs.
(3) “Egress Tagging” is configured per port and VLAN.
(4) Enables creation of EVCs for untagged ingress traffic using “EtherType =
0xFFFF”.
Each VLAN processing mode is associated with the EVC scenario proposed.

88 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Processing Mode is “None”

Allow ports to work in basic L2 switch mode, i.e. frames are forwarded based only on
the MAC address. This mode is used for bridge ports not associated with any EVC.
Processing Mode is “Tagging”
Used to create an EVC based on a given VLAN-ID, associated to a customer whose
service frames are untagged.
Frames must be tagged when entering provider network (setting the corresponding
VLAN ID to the value of the PVID attribute on the corresponding port) and untagged
when returning to customer.
When the VLAN processing is determined by the EtherType of the Bridge, this should
have the value 0x8100 (IEEE 802.1q standard).
Processing Mode is “Stacking”
Used to add an additional VLAN Tag (with VLAN ID = PVID) to already tagged traffic
(only one VLAN Tag, expected).
This processing mode might be used for two purposes:
– Create an EVC based on a given VLAN-ID, associated to a customer whose service
frames are expectably tagged. The EVC forwards the customer VLAN Tags, by
stacking the provider VLAN tag (outer VLAN) over the customer VLAN Tags (inner
VLAN), which are therefore preserved.
– Expand the VLAN namespace on large provider Ethernet networks, allowing for a
combination of up to 16M VLAN ID pairs (4094 * 4094), thus defining a QinQ network
area.
Frames should be stacked when entering the outer EVC (becoming double tagged) and
untagged when exiting the outer EVC, but maintaining the inner VLAN Tags (i.e., only
the outer tag should be removed). Note that, due to possible restrictions related to the
underlying NEs, the “Bridge EtherType = 0xFFFF” might enforce the usage of this pro-
cessing mode.
Processing Mode is “Adoption”
Used when the provider VLAN-ID to be used is already contained in the VLAN Tag of
customer incoming frames. Port must be member of the VLAN ID contained by such
VLAN tags on customer frames. When the VLAN processing is determined by the Ether-
Type of the Bridge, it is assumed that incoming frames have Tag Protocol Identifier
(TPID) = 0x8100 (which is meant for standard IEEE 802.1q VLAN tags).
Processing Mode is “Translation”
VLAN ID translation is performed by the port ingress function as it replaces the VLAN ID
on the incoming tagged frames with another VLAN ID. This is possible when VLAN tags
are local to the UNI, meaning that the VLAN tag value, if it exists on one side of the EVC,
is independent of the VLAN tag values on the other side. One scenario is to tie indepen-
dent LANs together where the VLAN assignments of each MAN/WAN/LAN do not
match.
This processing mode enables the creation of a service where the VLANs are removed
from one side of the EVC and are translated to the correct VLANs on the other side of
the EVC.
Processing Mode is “Undefined”
This VLAN Processing Mode is used when different configurations besides the expected
ones (such as choosing a different EtherType). Specially if frames are to be sent in a
different format than the normal.

A42022-L5981-A051-03-7618 89
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

The “Undefined” VLAN processing mode enables the handling of notifications and per-
forming synchronization.
This VLAN processing mode is most relevant when considering the management of
ACS/RCS for custom-defined VLAN processing configurations (e.g., via LCT): if the
EVC is created with VLAN Proc Mode = “Undefined” and the actual VLAN processing
attributes are mapped into VLAN Proc Mode = “Undefined” (as a result of a manual con-
figuration), no mismatch will occur.

6.5.4.3 Creating an EVC

To create a new EVC you click Configuration -> EVC -> New... menu item and the New
EVC wizard is started.
The New EVC wizard consists of the following steps:
– End ports
– EVC Details
– Network Map
– Summary
End ports
In the End ports page you select the end ports for the EVC being created. To see the
available ports in the browsing area, drag and drop NEs from the “Element Browser”
window or from the “Ethernet Logical Map” window.
To select the ports, drag them from the browsing area or from sources outside the “New
EVC wizard” window, such as the “Element Browser” window, and drop them to the
assigned end ports table.
The EVCs’ VLAN processing mode is configured for each port or to all ports in the table.
The following VLAN processing modes are available:
– Tagging (default)
– Translation
– Stacking
– Adoption
– Undefined
The available VLAN processing modes are dynamic and are shown accordingly to the
bridge configurations that affect the port supported modes.
EVC Details
In the EVC details page attributes such as EVC name, VLAN ID, Customer ID, Route
protection and Operation supervision are configured.
Network Map
In the Network Map page a network representation is showed with the NEs for the
selected VLAN and to be part of the EVC. The routes are automatically calculated by
the system.
When the calculation of routes is finished, these routes and corresponding NEs are high-
lighted with different colors.
Summary
In the Summary page the results of the EVC creation are presented.

90 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

If the operation results unsuccessful, use the “Back” button to change the EVC settings
or click “Finish” to retry the operation.

6.5.4.4 EVC Details

The “EVC Details” window shows the attributes for a selected EVC and is opened from
the “EVC Management” window. After selecting the EVC from the available list, click
“Details” button and the “EVC Details” window opens.

Figure 57 “EVC Details” window: EVC ports tab

The “EVC Details” window is composed of the following tabs:
– Parameters: Shows the EVC general parameters.
– Ports: Visualization of EVC ports.
– Routes: Visualization of EVC routes in a map.
All the information is read-only.

A42022-L5981-A051-03-7618 91
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

6.5.4.5 Modifying/Activating an EVC

To modify an EVC, do the following:
1. Select an EVC from the “EVC Management” window and click the “Modify” button in
the Toolbar.
2. Modify the desired EVC attributes in the “Modify EVC Wizard”. Non editable fields
such as the VLAN ID are disabled.
The network map displayed in the “Network Map” page is recalculated based on the
ports that have been chosen and on the selected value of the “Route Protection”
option.
The activation of an EVC is done over an already created EVC that is deactivated.
To activate an EVC, do the following:
1. Select a deactivated EVC from the “EVC Management” window and click the “Acti-
vate” button in the Toolbar. Optionally, use the context menu of the selected EVC.
The EVC state is changed to “activated”.

6.5.4.6 Using Filter and Sort

For the “EVC management” window a filtering and sorting mechanism exists. When
opening the “EVC management” window first a “Filter and Sort” window appears
allowing to restrict the amount of list entries according to specific criteria and to sort the
entries in a reasonable order.The “EVC Filter and Sort” window can also be started via
the Filter and Sort button from an opened “EVC management” window.

92 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

Figure 58 “EVC filter and sort” window

6.5.5 Viewing the STP map

The “Logical Actual/Planned STP Tree” window shows the STP map which represents
the network structure in a hierarchical view. It is possible to view either the actual or
planned STP topology, depending on operator’s option.
To view the “Logical Actual/Planned STP Tree” window for a given NE perform the fol-
lowing:
1. Open the “View STP Tree” window through the View>STP Tree menu item.
2. In the “View STP Tree” window the user selects the scenario (actual or planned) to
represent and selects a bridge.
It is possible to drag and drop a Bridge NE from the “Element Browser” window to
the “Bridge” field. This operation is avoided if the “View STP Tree” window is opened
from a Bridge NE context menu.
The STP parameters are configured at the nodes and ports of the network which permits
to construct the STP Tree.
In the “actual” scenario the network structure reflects the actual network status.
In the “planned” scenario the network shown is the one stored by TNMS ASON /
Ethernet Manager on operator demand.

A42022-L5981-A051-03-7618 93
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

If the “actual” and “planned” tree contents are the same, a failure free network is said to
exists.

Figure 59 “Logical Planned STP Tree” window

Network Configurations
Any change in the network (e.g Ethernet Links, NEs) is reflected in the “Logical Actual
STP Tree” window only. As a consequence, the “operational state” of the affected EVCs
is updated automatically according to the “operational state” of all EVCs’ routes.
To reflect these changes in the “STP map” window, click the Update view button in the
toolbar.

94 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Operation

6.6 Viewing logs

Log management provides a Graphical User Interface (GUI) to list all the existing logs
in the system and view the contents of the corresponding logs. Other operations: filter-
ing, sorting, printing and saving to a file are also supported.

6.6.1 Log List

The log list displays a list of all existing logs and their current state information in a table
format. Log viewing and administration depends on user access rights. The window is
static, an update button allows the user to refresh the log list.
g Administration of logs means exporting logs and configuring log settings (see
Chp.7.4)
Filtering and Sorting
The log list can be sorted by clicking the desired column header or by using the Sort
Settings... menu entry in the context menus. It is possible to filter the table columns
contents by using the Filter with Current Cell... menu entry in the table cell context
menu.

6.6.2 Log View

A log view window displays the contents of a known log type. Log management is
responsible for providing log view windows for the security, system event, command,
and network event log types. The remaining log view windows are provided by the
responsible component.
Each log view window shows a list of all log records as a table. The table columns rep-
resent the different fields of the log record structures. They can be displayed or hidden
by using the "Column Settings" menu entry in the context menus.
The log view windows are implemented according to two different types of behavior con-
cerning log record list updating:
– Static windows: the list of log records shown in the window must be explicitly
requested by the operator. If a new record is added to the log, it will only be dis-
played when the user clicks on the Update toolbar button.
– Dynamic windows: the list of log records is immediately updated when a record is
created, modified or deleted. The current sort and filtering settings configured in the
view is respected every time a log record entry is updated. The user also has the
possibility of stopping the automatic update of the view with "Freeze".
While the "Security Log" window and "System Event Log" window have a dynamic
update behavior, the "Network Event Log" window and "Command Log" window have a
static update behavior.
Filtering and sorting
Given the large number of log records that may exist in the log, an iteration concept is
used to obtain the log records from the server. When a log view window is opened and
no filter was previously defined for that log, the "Request Data with Filter and Sort
window" is automatically displayed so the user can request the log data from the server
with filter and sort settings. The filter information is stored in the user profile and is auto-
matically applied every time the log view window is opened.

A42022-L5981-A051-03-7618 95
Issue: 3 Issue date: August 2007
Operation User Manual (UMN)

The filters support wildcards and use the values of the various table columns as filter
criteria.

6.6.3 Saving/Loading filter and sort settings

The filterand sort settings used in log view windows can be saved to and loaded from
files on the local file system. These files are .xml based and it is possible to share them
between users and machines.The filter and sort settings are also saved and loaded in
the current user profile settings. This functionality is used to display persistent window
settings for each user. For instance, if a user performed a filter query on the system
event log, the next time he tries to open the system event log the last filter settings are
displayed, even if he logged out and logged in.

6.6.4 Saving log and log list records

The filterand sort settings used in log view windows can be saved to and loaded from
files on the local file system. These files are.xml based and it is possible to share them
between users and machines.The filter and sort settings are also saved and loaded in
the current user profile settings. This functionality is used to display persistent window
settings for each user. For instance, if a user performed a filter query on the system
event log, the next time he tries to open the system event log the last filter settings are
displayed, even if he logged out and logged in.

6.6.5 Printing log and log list records

The print operation follows the same principle as the save operation: only the log records
contained in the table view are printed. The data is arranged on the print pages in the
best possible way. If necessary, the printed items (e.g., tables) will automatically be split
into multiple parts so they fit on the paper.

96 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Administration

7 Administration
This chapter provides information that is considered relevant for an administrator of
TNMS ASON / Ethernet Manager. The following topics are described in detail:
– Setting date and time zone (see Chp. 7.1)
– Importing and exporting data (see Chp. 7.2)
– User and security administration (see Chp. 7.3)
– Log administration (see Chp. 7.4)

7.1 Setting date and time zone

TNMS ASON / Ethernet Manager allows the display of time and timestamps to be
switched between Local time and GMT. This is done with the menu bar entry View >
Time Display in the client application.
Choose between:
– Local Time
– GMT
If local time is chosen the time display is based on the time zone settings of the actual
TNMS ASON / Ethernet Manager client.

7.2 Importing and exporting data

The TNM system allows the user to import/export configuration data from items con-
tained in the EM\NE management, user and security management and topology man-
agement. The import/export operation is supported by a wizard, where the user selects
the name and the path items to be imported/exported. This wizard is started in the File
menu of the main window. It guides the user throughout the import/export steps and
displays a summary status.

7.3 User and Security administration

User and security management is based on LDAP (Lightweight Directory Access Pro-
tocol) directory service which manages all user and security relevant data persistently.
The relevant user and security data stored in the LDAP directory service includes:
– Username, Password
– User Group
– Domains
– Policies
– Component command tree
– Group-Domain-Policy mappings
LDAP is used as the basic communication structure for all inter-working TMN systems
which support global authentication and global authorization to achieve global security.
g All user and security configurations must be executed via the TMN system GUI.
Direct manipulation of the user and security database with another tool is not sup-
ported and could damage the system.

A42022-L5981-A051-03-7618 97
Issue: 3 Issue date: August 2007
Administration User Manual (UMN)

The main benefits are a single login for a user and a powerful global security adminis-
tration service, e.g., global user management and global security management for all
inter-working TMN systems.

7.3.1 General security rules

General security settings can be configured in the "Security Settings window":
– Password change interval and inactivity timeout settings
– Account lockout settings
– Advisory message settings
These are settings applied to all user accounts.
Advisory message
The advisory message is edited by an administrator and is displayed to every user
during login. Additionally, the user’s last successful login is also displayed in the "Advi-
sory Message" window. This message can be edited and configured to be displayed
optionally by selecting a checkbox in the "Security Settings" window.

7.3.2 Security alarming and security logging

Security management supports security alarms and two logs, the security log and the
command log. A security alarm is notified to the fault management component, where it
is managed and stored. Any log request is redirected to the log management application
that manages the security and command logs.

7.3.3 User administration

A user account allows the user to authenticate and have access to the TMN system. The
user is authorized to perform actions within a domain depending on the user group(s)
that the user account is assigned to. A user account must be a member of at least one
group.
The "User Administration" window allows the user to:
– View all user accounts and status
– Create, modify and delete user accounts
– Unlock, force logoff, activate and deactivate user accounts

7.3.4 User group administration

A user group comprises a group of users that are granted the same access rights for a
certain domain. If a user belongs to more than one user group, then the effective access
rights are based on all the relevant access rights granted by each user group.
The "User Group Administration" allows the user to:
– View all user groups
– Create, modify and delete user groups

98 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Administration

7.3.5 Policy administration

All GUI based operations that can be performed by the user are menu based. The set
of menu entries to which a user has privileges is called a policy. Therefore, a user must
be assigned a policy in order to perform any action. By adding and removing the menu
entries from a policy, it is effectively possible to control the access level of the user:
– Policy consists of menu entries
– It is possible that the same menu entry can exist in more then one policy
The "Policy Administration" window allows the user to:
– View the list of configured policies
– Create, modify and delete policies
– View the menu entries that are assigned to a policy
By default, all the menu entries belong to the default "GLOBAL" policy, that cannot be
modified or deleted.
Security management imposes a limit of 256 policies (including the "GLOBAL") that can
be available at any point.

7.3.6 Domain administration

A group of Network Elements for administrative means is called a domain. By default,
all the Network Elements belong to the default "GLOBAL" domain that cannot be
modified or deleted.

7.3.7 Access rights or mappings

Mere creation of policies is not sufficient to prevent the use of resources, by a set of
users. To restrict the use of resources, a relationship is created between a policy and a
user group. This relationship is called a mapping:
– Mapping is the relationship between a user group and a policy
– Policies and user groups participating in mappings cannot be deleted without first
deleting the mapping
The mappings can be configured via the "Assign Mapping" window. It is also possible to
view all the mappings in the read-only "Access Rights" window.

7.4 Log administration

Log management allows to administrate logs:
– Configure log settings
– Export log records to the local file system
Even though these actions are provided by log management, the windows are log type
dependent, i.e., they are provided by the responsible component as described in
chapter 3.4.7.

A42022-L5981-A051-03-7618 99
Issue: 3 Issue date: August 2007
Administration User Manual (UMN)

7.4.1 Log export

Log export allows saving log records to a different persistency support for further pro-
cessing; typically with an archive or spreadsheet tool. This operation, which is per-
formed by the log management, consists of accessing the log database, reading a
subset of log records and writing them into files in the server file system.
Export operations can be initialized manually from the log list or automatically via the
scheduled export.

7.4.1.1 Manual export of logs

The "Export Log" window provides a user interface to configure log export settings and
start a manual export operation for one or more files.
Log management has the responsibility for the security, network event, system event
and command log types. The following export settings are provided for these log types:
– File name prefix: a prefix to be used in the complete file name.
– File format: the file format used in the export operation.
– Date format: the date format used in the exported file.
– Maximum file size: the maximum size per file. If there are more records than file
capacity, more than one file is created.
– Number of records: number of records per file. If number of records is greater than
this number, more than one file is created.
– Delete log records after export: the log records are deleted from the database only
if all contents have been successfully written to the file system.
The set of log records to be exported is defined with the filter settings. These settings
can be saved and loaded from the local file system.
Since log management requires access to external persistency storage, unexpected
errors may occur, e.g., insufficient disk space. If an error occurs during the exportation
of a single record, then the whole export operation will be considered as having failed.
Thus, log management generates system event messages and uses fault management
to raise system alarms. For more information please refer to chapter 7.4.3.
The user can only perform manual exports with record deletion if he is sure that it will
not interfere with the scheduled export.

7.4.1.2 Scheduled export of logs

Scheduled exports always have an incremental behavior, i.e., log management auto-
matically defines a time filter for the export operation. The user is able to set scheduled
exports based on fixed time intervals or week/month masks.
g The Export options and Recurrence pattern must be configured to avoid overwrit-
ing the exported log data before being backed up by the BRA framework.
All the export settings described in chapter 7.4.1.1, except for the filter settings, can also
be configured for scheduled exports. Scheduled export is configured in the "Modify Log"
window, which is described in chapter 7.4.1.2.

100 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Administration

7.4.1.3 Export file formats

The following export file formats are supported by log management:
– Comma Separated Values (CSV) - each line (up to the carriage return) is considered
a log record. Fields within each record are divided by a delimiter character (that can
be chosen), typically a comma. Each line must have the same number of fields
(commas). If a comma or leading and/or trailing blanks appear in any field value the
field must be enclosed in quotation marks (") to indicate the information is data and
not a field divider.
– eXtensible Markup Language (XML) - the fields of a log record are described as
XML elements. A log is exported as a collection of log record elements.
– Application specific format ASCII - this format is used to provide backward compat-
ibility. It has the same structure of the CSV format. The only difference is that the
delimiter character is a tab.

A42022-L5981-A051-03-7618 101
Issue: 3 Issue date: August 2007
Administration User Manual (UMN)

Example CSV:

"Field1 Name", "Field2 Name", ... , "FieldN Name"

"Record1 Field1", "Record1 Field2", ... , "Record1 FieldN"
"Record2 Field1", "Record2 Field2", ... , "Record2 FieldN"
...
"RecordN Field1", "RecordN Field2", ... , "RecordN FieldN"

Example XML:

<Log>
<Header>
<Field type="Integer">Field1</Field>
<Field type="Date">Field2</Field>
...
<Field type="String">FieldN</Field>
</Header>
<Body>
<Record>
<Field1>value</Field1>
<Field2>value</Field2>
...
<FieldN>value</FieldN>
</Record>
...
<Record>
<Field1>value</Field1>
<Field2>value</Field2>
...
<FieldN>value</FieldN>
</Record>
</Body>
</Log>

Example ASCII:

"Field1 Name" "Field2 Name" ... "FieldN Name"

"Record1 Field1" "Record1 Field2" ... "Record1 FieldN"
"Record2 Field1" "Record2 Field2" ... "Record2 FieldN"
...
"RecordN Field1" "RecordN Field2" ... "RecordN FieldN"

7.4.1.4 Output Location

Log mangement uses a predefined output directory on the server file system for the
export files. Table 18 shows the output directories for the different types of log and
export operations.

Output Directory
Log Type
Manual export Scheduled export

Table 18 Output directories for log types

102 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Administration

Alarm Log APP_ROOT/Export/Alarm/Manu APP_ROOT/Export/Alarm/

al Scheduled
Performance APP_ROOT/Export/Performanc APP_ROOT/Export/Performanc
Log e/Manual e/Scheduled
Security Log APP_ROOT/Export/Security/Ma APP_ROOT/Export/Security/Sc
nual heduled
System Event APP_ROOT/Export/SysEvent/M APP_ROOT/Export/SysEvent/S
Log anual cheduled
Network Event APP_ROOT/Export/NetEvent/M APP_ROOT/Export/NetEvent/Sc
Log anual heduled

Command APP_ROOT/Export/Command/ APP_ROOT/Export/Command/S

Log Manual cheduled

Table 18 Output directories for log types (Cont.)

Although the operator is free to define a prefix for the name of the export files, the
complete name is generated by log management. This name includes full information
about the time that the export operation was triggered (year, month, day, hour, minute,
second and locale).
Example: "pm_15min_log_export_2004_04_27_16h06m10s_cst.xml"

7.4.2 Log settings

The "Modify Log" window provides a user interface to view and configure all log related
settings:
– Log name: unique name of the log.
– Log type: the type of the log.
– Log max size: maximum number of log record entries available in the log.
– Log full behavior: log management behavior when a new record has to be written in
a log that is already 100% full.
– Log thresholds: threshold values to warn the user for certain conditions.
– Scheduled export: automatic scheduled export of a log.

7.4.2.1 Log full behaviour

A log full behavior defines the action that is taken when the log reaches its maximum
occupancy and a new write log record operation is requested. The following behaviors
are possible:
– Stop logging: no new records are written.
– Wrap around: logging continues when new records arise, the oldest log records are
overwritten.
Two wrap around modes are supported:
– Safe mode: to avoid data loss, the oldest entries of the log are first exported and
then deleted.
– Overwrite mode: the oldest entries are automatically overwritten.

A42022-L5981-A051-03-7618 103
Issue: 3 Issue date: August 2007
Administration User Manual (UMN)

Exports that are spontaneously triggered when the log is set to do wrap around in safe
mode, may cause performance bottlenecks due to the number of log records. To
improve performance, the oldest records are deleted in blocks as configured by log man-
agement.

7.4.2.2 Log thresholds

Each log can have a list of associated threshold values which are used to inform the user
if certain conditions are met. Threshold values can be defined for two different mean-
ings:
– Log occupancy: fill state of the log (full percentage). Indicates that log export oper-
ations with log record deletion are not being done at a sufficient rate. If this situation
continues, the log begins to work in "stop logging" or "wrap around" mode which may
not be acceptable due to operational or performance requirements.
– Unexported records: percentage of log records that were never exported. This
threshold allows the user to be aware that the records are not being exported at an
acceptable frequency. If a database is full of unexported records, and if a "wrap
around / safe mode" behavior takes place, the export operations may cause perfor-
mance problems.
Log management generates system event messages and uses fault management to
raise system alarms based on these thresholds.

7.4.3 Alarms and messages

The following Table 19 details the scenarios on which log management has to raise
alarms or generate messages for certain log conditions depending on the log full behav-
ior.

Log Full Behavior

Senarios/Modes Stop logging Wrap around / Wrap around /
mode Safe mode Overwrite mode
Log gets full Alarm System Event Log Alarm
message
Log occupancy Alarm System Event Log Alarm
threshold is reached message
Unexported records System Event System Event Log System Event Log
threshold is reached Log message message message

Table 19 Log full behavior for certain log conditions

Alarm - log management raises an alarm and is responsible for clearing the alarm when
the condition that led to it no longer exists.
System Event Log message - log management is responsible for logging another
system event message to inform that the condition that led to the threshold exceed no
longer exists.
In some scenarios, log occupancy thresholds may not trigger an alarm, instead they
trigger new log entries in the system event log. In certain situations, log occupancy

104 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Administration

thresholds may reflect the behavior expected by the user, e.g., if the log is configured to
work in wrap around/safe mode, no data is lost.
The following Table 20 details the messages generated by log management when
exporting log records.

Error/Export mode Manual export Scheduled export

Disk space error GUI Message GUI Message
GUI Message + System System Event Log
Other type of error
Event Log

Table 20 Messages generated by log management when exporting logs

GUI Message - if export failed due to insufficient disk space, log administration does not
log a new system event record. The GUI message will be displayed to every user that
has sufficient permissions for log administration.

A42022-L5981-A051-03-7618 105
Issue: 3 Issue date: August 2007
Backup and Restore User Manual (UMN)

8 Backup and Restore

This chapter provides a guideline for the backup and restore procedures for a TNMS
ASON / Ethernet Manager administrator:
– Backup procedures (see chapter 8.2)
– Restore procedures (see chapter 8.3)

8.1 Considerations
Backup and Restore functionality offers a way to maintain the information of the avail-
able network.
Considerations
– The backup and restore operations are executed with a command line by the oper-
ator.
– The operator is able to configure the scheduler of the operating system to create a
scheduler TNMS ASON / Eth Manager backup.
– The operator is responsible for the data consistency of the backups from the TNMS
Servers, i.e. the TNMS Core/CDM server and the TNMS ASON / Ethernet Manager
server.
– The operator is advised to backup the files on a safe repository to prevent failures.
There are several severs and data repositories namely the ones associated with TNMS
Core/CDM and associated with TNMS ASON / Ethernet Manager. The following image
shows the structure of the backup server system:

Figure 60 Data repositories

TNMS ASON / Ethernet Manager must backup and restore the information stored in:
– SQL Server: For EM/NE management and services information.
– LDAP: For user and security information.
Operational concept
– The backup and restore commands are executed using a command promtp of the
Windows OS.
– Create scripts from the backup and restore commands and put them in the start
programs of Windows OS.

106 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Backup and Restore

– The backup command is able to be used in cooperation with the scheduler of the
operating system to create scheduler backups.
Target files
The backup files are stored in a directory with the time stamp that is created in the target
directory chosen by the operator.
The storage directory is chosen to be in the server or in a different server, i.e. a remote
directory.
The TNMS ASON / Ethernet Manager backup files and the TNMS Core/CDM backup
files are possible to be stored in the same server. To execute correctly the backup and
the restore, the SQL Server, the LDAP and the TNMS ASON / Ethernet Manager server
must be online.
The following files are created during backup:
– sqlserver.bak: SQL Server backup file.
– ldap.bak: LDAP backup file.
Data Integrity
Since the Ethernet Manager’s information of TNMS ASON / Ethernet Manager is depen-
dent of TNMS Core / CDM information (namely regarding GFPGs’ trails) the following
considerations must be taken:
– The user is advised to perform the backup of TNMS ASON / Ethernet Manager at
the same time of TNMS Core / CDM backup.
– The user is advised to restore the backup information of TNMS ASON / Ethernet
Manager at the same time of the TNMS Core / CDM restore.
– It is required to restore the backup information of TNMS Core / CDM before the
TNMS ASON / Ethernet Manager restore.
– When using automatic scheduled backups, the time settings for both TNMS ASON
/ Ethernet Manager and TNMS Core / CDM must be configured with the same
values, in order to avoid losing data integrity.

8.2 Backup procedures

This chapter describes the detailed procedures to manually backup the TNMS ASON /
Ethernet Manager system data:
– Backup TNMS ASON / Ethernet Manager information (see chapter 8.2.1)
– Backup TNMS Core/CDM and TNMS ASON / Ethernet Manager (see chapter 8.2.2)
g Make sure there are no automatic backups running before executing a manual
backup. For more information on the default automatic backup schedules please
consult chapter 8.1
Prerequisites
For all the described procedures, the following prerequisites must be considered:
– SQL Server is online
– LDAP is online
– TNMS ASON / Ethernet Server is online

8.2.1 Backup TNMS ASON / Ethernet Manager information

To backup both SQL server and LDAP information of TNMS ASON / Ethernet Manager
do the following:

A42022-L5981-A051-03-7618 107
Issue: 3 Issue date: August 2007
Backup and Restore User Manual (UMN)

1. Open the command line prompt

2. Execute the command:
c:> backup all <directory>
g <directory> specifies the directory where to store the backup files.
<directory> cannot have spaces.
To backup only the SQL server information execute the following command instead:
c:> backup db <directory>
To backup only the LDAP information execute the following command instead:
c:> backup ldap <directory>

8.2.2 Backup TNMS Core/CDM and TNMS ASON / Ethernet Manager

To backup both TNMS Core/CDM and TNMS ASON / Ethernet Manager information,
besides the already mentioned pre-requisites, also TNMS Core/CDM must be online
with TNMS ASON / Ethernet Manager.
The procedure must be taken in the order that follows:
1. Backup TNMS Core/CDM data repositories using TNMS Core SysAdmin.
2. Backup TNMS ASON / Ethernet Manager data repositories using TNMS ASON /
Ethernet Manager.

8.3 Restore procedures

This chapter describes the detailed procedures to manually restore and recover the
system data:
– Restore TNMS ASON / Ethernet Manager information (see chapter 8.3.1)
– Restore TNMS Core/CDM and TNMS ASON / Ethernet Manager information (see
chapter 8.3.2)

8.3.1 Restore TNMS ASON / Ethernet Manager information

To restore both SQL server and LDAP information of TNMS ASON / Ethernet Manager
do the following:
1. Open the command line prompt
2. Execute the command:
c:> restore all <directory> <timestamp>
g <directory> <timestamp> must be present as it specifies the directory where
the backup files (sqlserver.bak and ldap.bak) are stored.
<directory> and <timestamp> cannot have spaces.
To restore only the SQL server information execute the following command instead:
c:> restore db <directory> <timestamp>
To restore only the LDAP information execute the following command instead:
c:> restore ldap <directory> <timestamp>

108 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Backup and Restore

8.3.2 Restore TNMS Core/CDM and TNMS ASON / Ethernet Manager

information
To restore both TNMS Core/CDM and TNMS ASON / Ethernet Manager information, the
following procedure must be taken and in the mentioned order:
1. Restore TNMS Core/CDM data repositories.
2. Restore TNMS ASON / Ethernet Manager data repositories.

A42022-L5981-A051-03-7618 109
Issue: 3 Issue date: August 2007
Abbreviations User Manual (UMN)

9 Abbreviations
ASON Automatic Switched Optical Network

CSPF Constrained Shortest Path First

CST Central Standard Time

CSV Comma Separate Values

DCN Data Communication Network

DSR Dynamic Source Route

EM Element Manager

EM/NE Element Manager/Network Element object management

EVC Ethernet Virtual Connection

FA-LSP Forwarding Adjancency LSP

GCT GUI Cut-Through

GFPG Generic Framing Procedure Group

GMPLS Generalized Multi-Protocol Label Switching

GMT Greenwich Mean Time

GUI Graphical User Interface

LCT Local Craft Terminal

LAN Local Area Network

LDAP Lightweight Directory Access Protocol

LSP Label Switched Path

MDI Multiple Document Interface

NE Network Element

NEC Network Element Controller

NTP Network Time Protocol

PC Personal Computer

PDF Portable Document Format

PT Physical Trail

SDH Synchronous Digital Hierarchy

SONET Synchronous Optical Networking

SPC Soft Permanent Connection

SQL Structured Query Language

110 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN) Abbreviations

SRLG Shared Risk Link Group

STP Spanning Tree Protocol

TC Topological Container

TE-Link Traffic Engineering-Link

TMN Telecommunication Management Network

TNMS Telecommunication Network Management System

TP Terminal Point

UMN User Manual

UNI User to Network Interface

VC Virtual Container

VLAN Virtual LAN

WAN Wide Area Network

XC Cross Connection

XML Extended Markup Language

A42022-L5981-A051-03-7618 111
Issue: 3 Issue date: August 2007
 User Manual (UMN)

Index
A I
Access rights 99 Installation 36
Advisory message 98 Documentation installation 45
Architecture Hardware 36
TNMS ASON / Ethernet Manager 20 Unistallation procedures 45
ASON domain 16
ASON management 14, 28 K
ASON Manager 14
Keyboard 49
Automatic
reconnection 28
L
B LDAP 97
List of logs 95
Backup an Restore 106
Load
107
filter and sort settings 96
Backup server 24
Log export 100
file formats 101
C manual 100
Components output location 102
software 25 scheduled 100
Creating Log full behavior 103
Call 77 Log Management
Component Link 72 alarms and messages 104
EVC 90 Log management 14, 33
TE-Link 74 functional overview 33
Customer management log types 33
main features 35 main features 34
operating tasks 95
D setup phase 34
Log settings 103
Documentation
Log thresholds 104
online help 12
Domain administration 99
Dynamic log view 95 M
Map
E ASON Logical Map 69
Ethernet Logical Map 80
Element manager application 27
Network Map 58
EM/NE management 14, 30
STP Map 93
element manager 30
Mappings 99
network elements 30
Mouse 49
Ethernet management 14, 29
Ethernet Manager 14
N
F NE
ASON-capable 18
Functional overview
Ethernet-capable 19
ASON management 28
EM/NE management 30
Ethernet management 29 P
log management 33 Policy administration 99
topology management 31 Print
user and security management 31 log records 96

112 A42022-L5981-A051-03-7618
Issue: 3 Issue date: August 2007
User Manual (UMN)

R V
Remote login 28 View log contents 95
VLAN
S VLAN ID 90
VLAN processing mode 88
Save
filter and sort settings 96
Security alarms and messages 98
Security management 14
Security settings 98
Software
components 25
Static log view 95
Structure
online help 12
Supported scenarios 85

T
TNMS ASON / Ethernet Manager
architecture 20
client 27
server 27
TNSM-M 23
Topology management 14, 31
functional overview 31
main features 31

U
User administration 98
User and Security management 31
alarming and logging 32
functional overview 31
main features 32
security management 32
user management 32
User Group administration 98
User interface
Call details window 79
Call management window 76
Component Link details window 72
Element Browser window 84
EVC details window 91
EVC management window 85
Filter and Sort window 92
LSP management window 75
Main window 51
Menu bar 51
Status bar 53
TE-Link details window 74
TE-Link management window 73
Toolbar 52
username and password 48
User management 14

A42022-L5981-A051-03-7618 113
Issue: 3 Issue date: August 2007