vdocuments.mx_client-tnms

NOKIA SIEMENS NETWORKS
TNMS Core/CDM V11.1

TNMS Client Help
i
Contents
Contents
NOKIA SIEMENS NETWORKS TNMS Core/CDM V11.1.................................................................i
TNMS Client Help ..............................................................................................................................i
Contents ..........................................................................................................................................iii
Introduction .......................................................................................................................................
1
Application - TNMS Core/CDM.....................................................................................................2
Changing passwords ....................................................................................................................
3
Logon ............................................................................................................................................4
User class .....................................................................................................................................
5
Help on help......................................................................................................................................
7
Changing the font of a help topic ..................................................................................................8
Printing a help topic ......................................................................................................................
9
Using help ..................................................................................................................................10
Operating information ....................................................................................................................11
Client operation..........................................................................................................................12
Calling up context menus .......................................................................................................12
Network Management View ...................................................................................................13
Switching between different modes........................................................................................15
TNMS Client main window .....................................................................................................16
TNMS Client menu bar...........................................................................................................17
View options ...........................................................................................................................20
General operating information ...................................................................................................21
Setting the toolbar view..........................................................................................................21
Using the keyboard ................................................................................................................22
Icons...........................................................................................................................................23
Icons: DCN components ........................................................................................................23
Icons: Filter and sort icons in lists ..........................................................................................25
Icons: Link connection............................................................................................................26
Icons: Network elements ........................................................................................................28
Icons: Network infrastructure and protection..........................................................................30
Icons: Network Plan ...............................................................................................................32
Icons: Port Connections, Path Wizard and Connection Assistant .........................................34
Icons: Routing.........................................................................................................................38
Icons: Services, subscribers and paths..................................................................................39
Lists and logs handling ..............................................................................................................44
General log management information....................................................................................44
Print preview ...........................................................................................................................45
Printing logs ............................................................................................................................46
Setting time filters for lists and logs........................................................................................47
Setting columns ......................................................................................................................48
Setting filters and sorting lists.................................................................................................49
System message log ..............................................................................................................51
Viewing logs ...........................................................................................................................53
Performance Log Export Tool (PLET)........................................................................................56
iii
TNMS Core/CDM 11.0 TNMS Client Help
Configuring the Performance Log Export Tool (PLET) ..........................................................56

Exporting logs using PLET .....................................................................................................57
TNMS OTS-4000 Performance Add On Tool (TOPAT).............................................................58
TOPAT - General Information ................................................................................................58
TOPAT GUI ............................................................................................................................59
PMP Configuration .................................................................................................................62
Launching TNMS ASON / Ethernet Manager GUI.....................................................................64
Technical background information on............................................................................................65
Concatenation............................................................................................................................66
Floating TPs ...............................................................................................................................70
Floating TPs: Behaviour of the Connection Assistant................................................................71
Layer Restrictions at Optical Protection.....................................................................................72
Scalable Ethernet Paths & Generic Framing Procedure ...........................................................73
Support of Loopbacks ................................................................................................................76
Technologies and Transport Layers ..........................................................................................78
Client functions ..............................................................................................................................87
Alarms ........................................................................................................................................88
Acknowledging alarms ...........................................................................................................88
Alarm correlation for a path ....................................................................................................89
Alarm and path statistics ........................................................................................................91
Alarm log ................................................................................................................................92
Alarm severities and alarm states ..........................................................................................94
Alarm statistics .......................................................................................................................95
Alarm suppression for a path .................................................................................................96
Current alarm list ....................................................................................................................97
Defining filters for alarm displays ...........................................................................................99
Displaying alarms .................................................................................................................100
Event forwarding...................................................................................................................101
Fault settings ........................................................................................................................102
Localizing alarms..................................................................................................................104
Printing the alarm list............................................................................................................105
Redirecting alarms for a network element............................................................................106
Saving the current alarms ....................................................................................................107
Updating alarm information ..................................................................................................108
DCN management ...................................................................................................................109
DCN channels ......................................................................................................................109
Displaying and processing alarms of a DCN component.....................................................110
General channel properties..................................................................................................111
General NetServer properties ..............................................................................................112
Listing DCN objects..............................................................................................................113
Resynchronizing the data of a DCN channel .......................................................................115
Lists and logs handling ............................................................................................................116
Creating a performance log..................................................................................................116
Displaying a performance log...............................................................................................119
Deleting performance logs ...................................................................................................122
iv
Contents
Handling performance logs ..................................................................................................123

Handling performance logs ..................................................................................................123
Menu entries for alarms........................................................................................................125
Modifying configuration settings for performance logs.........................................................126
Notification Log .....................................................................................................................127
Network Event Log ...............................................................................................................129
Permanent logs ....................................................................................................................131
Starting and stopping performance logs ..............................................................................132
Tandem connection monitoring............................................................................................133
NE containers...........................................................................................................................134
Adding a new network element or subnetwork to an NE container .....................................134
Assigning a background bitmap ...........................................................................................135
Changing the background bitmap ........................................................................................136
Controlling access rights to NE containers ..........................................................................137
Deleting an NE container .....................................................................................................138
Displaying and processing alarms for an NE container .......................................................139
Displaying the properties of NE containers..........................................................................140
Handling NE containers........................................................................................................141
Properties of a NE container ................................................................................................142
Resynchronizing the data of an NE container......................................................................143
Network elements ....................................................................................................................144
Connecting/disconnecting a network element to/from TNMS Core/CDM............................144
Context menus on the Network Plan....................................................................................145
Controlling write access to a network element.....................................................................146
Creating a DCN status list ....................................................................................................148
Creating a scheduled DCN status list ..................................................................................149
List Contents.........................................................................................................................150
Deleting network elements ...................................................................................................156
Displaying alarm redirections for a network element ...........................................................157
Displaying and processing alarms of a network element.....................................................158
Displaying the properties of network elements ....................................................................159
Exclude NE from routing ......................................................................................................160
File transfer...........................................................................................................................161
Finding network elements ....................................................................................................162
General network element properties ....................................................................................163
Locking/unlocking a network element ..................................................................................164
Modifying the properties of a subnetwork ............................................................................165
NE distinctions ......................................................................................................................166
Port types .............................................................................................................................167
Resynchronize data ..............................................................................................................168
Selecting network elements .................................................................................................169
Starting the network element manager ................................................................................170
Suppressing alarms and events for a network element or a subnetwork ............................171
Paths ........................................................................................................................................172
Activating/Deactivating a path ..............................................................................................172
v
Adopting the actual route .....................................................................................................173

Adopting the actual topology ................................................................................................174
Automatic Analyzer Mode ....................................................................................................175
Automatic Routing Preferences............................................................................................176
Choose link connection ........................................................................................................177
Connection Assistant............................................................................................................178
Create/Modify Group TP ......................................................................................................181
Creating a path container .....................................................................................................182
Creating a path.....................................................................................................................183
Deleting a path .....................................................................................................................185
Disabled Paths .....................................................................................................................186
Handling server paths and client paths ................................................................................188
Hybrid routing .......................................................................................................................189
Listing paths .........................................................................................................................190
Listing client paths................................................................................................................194
Modifying a path ...................................................................................................................195
Path Overhead Monitoring ...................................................................................................197
Paths under test ...................................................................................................................198
Path Wizard: define topology ...............................................................................................199
Path Wizard: properties........................................................................................................202
Path Wizard: routing results .................................................................................................203
Release Required Resources ..............................................................................................207
Rerouting a path...................................................................................................................208
Preferences and routing options ..........................................................................................209
ToolTips for path creation.....................................................................................................211
Path bundles.........................................................................................................................212
Path bundles - general information...................................................................................212
Clone Edges .....................................................................................................................213
Creating a path bundle .....................................................................................................214
Creating a path bundle using a path template..................................................................216
Modifying routes of a path bundle.....................................................................................217
Moving the endpoints of a path bundle.............................................................................218
Ports, port connections and termination points........................................................................219
Creating a port connection ...................................................................................................219
Displaying the properties of port connections ......................................................................220
Editing/Deleting port connections.........................................................................................221
Link detection view ...............................................................................................................225
Listing ports ..........................................................................................................................227
Listing port connections........................................................................................................229
Disabled Port Connections...................................................................................................232
Listing termination points......................................................................................................234
Port and TP filter settings .....................................................................................................236
Creating VLAN assignment..................................................................................................237
Remove VLAN Assignment..................................................................................................238
Protection .................................................................................................................................239
vi
Contents
Adding protection to a path automatically ............................................................................239

Adding protection to a path manually...................................................................................240
Creating BSHR or line protection .........................................................................................241
Displaying / modifying the properties of MSP ......................................................................242
Listing protection groups ......................................................................................................245
Removing path protection automatically ..............................................................................246
Removing path protection manually.....................................................................................247
Services ...................................................................................................................................248
Creating a service.................................................................................................................248
Deleting a service.................................................................................................................249
Locking/unlocking a path or a service ..................................................................................250
Modifying the properties of a service....................................................................................251
Service / Path properties......................................................................................................252
Service / Path properties: alarms .........................................................................................256
Service / Path properties: history .........................................................................................257
Service / Path properties: info ..............................................................................................258
Service / Path properties: routing.........................................................................................259
Service / Path properties: topology ......................................................................................264
Service / Path properties: scheduling...................................................................................267
Creating an Ethernet Service with LCAS .............................................................................269
Performance Thresholds Configuration ...............................................................................271
Subscribers ..............................................................................................................................272
Listing subscribers ................................................................................................................272
Subscriber management ......................................................................................................273
TNMS server administration ....................................................................................................274
Distributing TNMS Server time .............................................................................................274
Universal objects ......................................................................................................................275
Creating and modifying a CC of a universal object..............................................................275
Creating and modifying a module of a universal object .......................................................276
Creating and modifying a port of a universal object.............................................................277
Creating and modifying a TP of a universal object...............................................................279
Element manager for universal objects................................................................................280
Modifying a universal object.................................................................................................282
Glossary and Abbreviations.........................................................................................................285
Index ............................................................................................................................................293
vii
Introduction
1
Appl ic ation - TNMS Core/CDM

The Transport Network Management System Core/CDM (TNMS Core/CDM) is designed
for small to medium-sized and large networks which are tailored to specific customer
requirements.
It offers integrated management for WDM, PDH and SDH devices together with central
monitoring and configuration of the entire network, including the DCN. Management at
network and network element level is also supported, thus enabling convenient
configuration and management of end-to-end connections.
TNMS Core/CDM offers two user interfaces: TNMS SysAdm in and TNMS Client.
- TNMS SysAdmi n is a management interface which is used by the administrator for
managing and configuring the TNMS Core/CDM NetServer and the TNMS Core/CDM
Server. It is also used for managing central data shared by all clients.
- TNMS Client is an interface to the managed network where users can perform
monitoring and management functions.
TNMS Core/CDM supports different user classes. This means that if you are not an
administrator, and certain functions are not available to you, you may not belong to the
required user class. If certain functions are not available, you should also check that you
are in the correct window / operating mode for the function you wish to perform. More
information is provided under User class.
2
Introduction
Changing passwords
If you want to change your password, call the Change Passwor d window.
• In TNMS SysAdm in you will find the window under Security -> Password….
• In TNMS Cli ent you will find the window under Security -> Password….
In the field Old Password enter your current password.
In the field New Passwo rd enter your new password. For protection, the password is
displayed in the form of asterisks (*). You must ensure that you enter upper case and lower
case letters correctly as passwords in TNMS are case-sensitive.
In the field Confirm New Password enter the new password again. This ensures that
there are no typing errors in your password.
Note:
If the system does not accept a new password, ensure that the password observes the
account policy or user property requirements defined by the TNMS administrator for the
user account in the TNMS SysAdmin interface.
3
Logon
You must log on to the TNMS Server before you can obtain access according to your user
class.
Press the tabulator key to toggle between the fields in the dialog field.
Logon as follows:
1. In the Server field enter the name or the IP address of the TNMS Server which
administers the network to be monitored. By default the name of the TNMS Server at
which the last logon took place is displayed. Further TNMS Servers at which
successful logons have already been undertaken are available for selection.
If the TNMS Server you want to log on to is on the local system, the server name is "."
(period).
2. In the User Name field enter your user name. By default, the name of the last logged
on user is displayed. You are assigned a user name by your TNMS administrator.
Generally this user name is independent of your Windows user name.
3. In the Password field enter your password. For protection, the password is displayed
as asterisks (*). Passwords in TNMS are case-sensitive, i.e. the use of
uppercase/lower case letters must be observed.
Note:
When you log on for the first time after installing the software, you do not need to enter
a password.
4. Click on Logon or press the enter key.
Note:
The usage of different versions on Clients and Servers machines can be the cause for a
high load on the Server. Also, Server load permanently at nearly 100% leads to the
following error message: "Client login not possible".
4
Introduction
User c lass
To access the TNMS Server functionalities, six user classes are available. These user
classes are classified in accordance with the scope of access rights. The higher user class
in each case covers all access rights of the classes below it.
Bellow are the TNMS user classes in order of increasing user rights:
- TNMS CDM class

This user class enables the internal connection between TNMS CDM and TNMS Core. It
provides the TNMS CDM user to access TNMS Core by using his TNMS CDM account.
This is not visible to the user.
The access rights of a user that connects TNMS Core from TNMS CDM depends on the
following:
- User class controlled by TNMS CDM.
- TNMS CDM account administrated by TNMS SysAdmin.
- Supervision class
A user with supervision rights is allowed to monitor the complete network information.
All information relating to TNMS is read-only for users of this class, i.e., they are not
able to change the configuration in any way. They also have read access to the GUI of
the element managers.
The user is able to:
- Monitor all network information.
- Enable/disable alarms.
- Have read access to alarm toggle filters.
- Upload an NE.
- Enable automatic alarm correlation.
- Create a Remote Inventory List.
- Create a DCN Status List.
- Have read access to the GUI of the Element Managers.
The user is not able to:
- Configure or modify TNMS Core/CDM.
- Acknowledge current alarms.
- Maint enance class

A user with maintenance class is authorized to maintain a configured system. The user
can also start element manager applications with read-only access for further analysis.
In addition, a user of this class can acknowledge current alarms, create, modify and
delete performance logs to supervise specific parts of the DCN connected to TNMS.
- Have read access to the GUI of the Element Managers.
- Acknowledge current alarms.
- Create, modify and delete performance logs.
- Operation class
A user with operating rights can operate a configured system, create, modify or cancel
additional services.
- Create, modify or delete services.
- Create, modify or delete protection groups.
- Create, modify or delete multiplex section protections.
- Configure severity.
- Re-direct TIF alarms.
- Disable unused TPs.
- Refresh alarm masks.
- Configuration class
A user with configuration rights can delete and modify the network information shown
5
in the TNMS Client. In Network Editor mode, users of this class can also perform all
the steps required to configure, operate and supervise the TNMS network
- Use the network editor.
- Lock of network resources.
- Create, modify or delete port connections.
Note:
By default, a user with configuration rights has no access to the TNMS SysAdmin
software. To have access to the TNMS SysAdmin software, a special key has to be
activated in the computer registry file. This access to the TNMS SysAdmin software is
limited to the user’s access rights as already mentioned. For further information please
contact your Siemens representative.
- Admini st ration c lass

An administrator user has access to all system or user-relevant configuration data for
TNMS, and has full access to the TNMS administration software - TNMS SysAdmin.
- Add, modify or delete NE addresses.
- Configure TNMS Core/CDM components.
- Add, modify or delete TNMS Core/CDM user accounts.
- Use the TNMS Core/CDM SysAdmin tool.
- Have read and write access to alarm toggle filters.
- Have write access to the GUI of the Element Managers.
- Configure the polling interval for the current alarm list.
-
6
Help on help
7
Changing t he font of a help top ic

1. Click Options in the window of the help topic.
2. To change the font, go to Font, and click Small, Normal or Large.
Note:
The font change only applies to the current help file.
8
Help on help
Printing a help topic

Click File -> Print Topic... in the help topic window.
You can also select a help topic from the help table of contents and then click onPrint.
9
Using help
In TNMS Core/CDM there are various ways of obtaining help:
1. You can open the online help using the menuHelp -> Help Topics … in the menu bar
or by pressing the Help button in the toolbar. You can then search for a particular topic
using Contents , Index or Find.
2. Most windows contain a Help button. Click this button to display help on the active
window.
3. You can usually press F1 to display help on the active window.
10
Operating inf ormation
11
Client operation
Calling up cont ext menus
Each object on the TNMS user interface has what are known as context menus. If you click
with the right mouse button on the object, the most important actions for this object will
then be shown and can be selected with the left mouse button.
12
Operating information
Network Management View

The Network Management View window, offering the management functions of the
TNMS Client is opened automatically after logon. The title of the window shows which
mode has been set.
To swap between the different modes use View -> Network View Mode ->
Surveillance/Network Editor /Services or use the buttons provided at the bottom edge of
the window. Depending on the selected mode and the user group you are assigned to,
various TNMS functions are available for you.
In the left area of the window five different tree views are shown:
- Subscribers & Services
Tree view of the subscribers and the services.
Subscribers and services can only be processed in Services mode. If you click on this
area of the window, the network view automatically switches toServices mode.
- Network Infrastruct ure
Tree view of all MS protections and Client Paths
- Network Elements
Tree view of the NE container structure with the network elements assigned to it in
each case.
- DCN Components
Tree view of the administered TNMS Core/CDM NetServers, their communication
interfaces and associated network elements and the administered CDM NetServers
and associated TNMS Core/CDM Servers.
- Unmanaged Paths
Tree view of all unmanaged paths in the network.
Unmanaged paths can only be processed in Services mode. If you click on this area of
the window, the network view automatically switches to Services mode.
Optionally there is a table view that can be showed and attached to the other tree views,
that is:
- Disabled Paths
Table view of all disabled paths in the network. The window is available through:
TNMS Client -> Fault -> Disabled Paths...
Depending on the table settings, several path information can be displayed, namelly:
Index, Path, Service, Subscriber, Layer, Required Bandwith [Mbps], Actual
Bandwith [Mbps], Bandwith State, Direction, Operational State, Alarm Mask,
Operator, Creation Time (Local), ACS, RCS, Connecti on Type, Connect ion Class,
Admi n State, Admin State Type, Next Ac ti vatio n Time, Next Deacti vatio n Time,
#NEs, Endpoin ts, Last Dis abled Time and Server Path.
Note:
The spl itt er bars between the five tree views c an be adjus ted usin g the mous e. Each
of them has its ow n context menu.
The cursor turns into a gap icon when it reaches the edge of a view area. By holding down
the left mouse button and shifting the edges you can adjust the size of the individual tree
views. To expand one of the tree views quickly to its maximum size, simply click on the
small button located at the right side of the splitter bar. If the view is already expanded,
clicking the small button restores the tree view in its previous size and position. Moreover
you can drag a tree view freely over the Network Plan or dock it on the left hand side of the
TNMS GUI.
The right area of the window represents the Network Plan. By working inNetwork Editor
mode you can create NE containers in the Network Plan and drag and drop one or more
13
DCN objects on the Network Plan. You can then perform actions on various objects
(network elements, port connections, paths) by double-clicking or using a context menu.
TNMS Core/CDM uses a variety of icons to display objects and to indicate their status.
See also :
Disabled Paths
Icons: DCN components
Icons: Network elements
Icons: Network Plan
Icons: Services, subscribers and paths
14
Switching between dif ferent mo des

TNMS Client has three different modes. These affect its functionality and in particular its
context menus:
- Surveillance: alarm and fault management function
- Network Editor : configuration of new port connections, new NE containers and new
connections of NEs to NE containers
- Services: configuration of subscribers and services
You can change from one mode to another as follows:

- View -> Network View Mode -> Surveillance/Network Editor /Services
- Context menu of NE container or network element -> Network View Mode ->
Surveillance/Network Editor /Services
- By activating the relevant Surveillance/Network Editor /Services button in the bottom
left corner of the Network Management View .
Note:
When you select an object in the Subscribers and Services tree window or in the
Unmanaged Path window the function mode of the Network Management View window
automatically switches to Services mode.
15
TNMS Client main wi ndow

The basic elements of the main window are:
- Menu bar and toolbar in the upper window area. More information is provided under
Menu bar functions.
- Work area in the center of the window in which the Notification Log window and further
sub-windows, in particular the Network Management View are shown.
- Status bar in the lower area of the window.
Information from left to right: Help information, user logged on, server name, icon for
connection status to the server, free memory on the local hard disk, icon for highest
alarm level of the supervised network, number of active/stopped performance logs,
number of pending task orders.
There is also a colored TNMS Core/CDM icon (TNMS Core/CDM indicator) on the top
right, which revolves as soon as data is being exchanged between theTNMS Client
application and the TNMS Core/CDM Server application.
16
TNMS Client m enu bar
Menu item Function

File -> Save... Stores lists and logs in TSF format, which can be
opened in MS-Access and MS-Excel.
File -> Print... Prints lists and logs in TSF format.
File -> Print er Settings ... Printer settings (Windows XP Professional standard).
File -> Exit Terminates the TNMS Core/CDM Client.
View -> Find... Finds network element using a unique identifier

(address part or labeling part) and localizes it in the
NE container. The network element is then highlighted
in color in the Network Plan and in the Network
Elements tree.
View -> Lists ... Displays the lists for port connections, subscribers,
paths, protection groups, ports, termination points,
DCN objects.
View -> CDM Lists… Displays the lists for the Sub NEs ,Sub Paths and Sub
Alarms.
View -> Tables... Opens the overview window for tables and logs. In this
window, all available Standard Logs (i.e. Network
Event Log, System Message Log, Alarm Log and
Current Alarms), Archived Standard Logs and
Performance Logs are shown in separate tabs.
View -> Network Event Opens the Network Event Log window.
Log…
View -> Syst em Message Opens the System Message Log window.
Log…
View -> Task Orders… Opens the Task Order window.
View -> Options ... Optional settings for display of Icons, Infobar
Al ignment , Infobar Settings, Layout Guides and
Infobar Transparency.
View -> Time Display -> Displays timestamps as Local Time or Greenwich
Local Time / GMT Mean Time.
View -> Networ k View Mode Switches between the different network view modes
(Surveillance mode, Network Editor mode or
Services mode).
View -> Networ k View Trees Display or hide the tree view for Subscribers and
Services, Network Elements, Network
Infrastructure, DCN Components, Unmanaged
Paths. Restore to Default Positi ons is also possible.
View -> Window Style Opens a submenu with the following commands:
- MDI (Default)
- Popup
Shows lists and logs as MDI or Popup window. Popup
windows can be moved outside the applications frame
and consequently to another monitor if present (Multi-
monitoring under Windows XP Professional).
Note: this menu entry becomes only active after a
restart of the TNMS Client!
17
View -> Toolbar Shows/hides the toolbar.

View -> Statusbar Shows/hides the status bar. Information on the status
bar reading from left to right: help information, user
logged on, server name, icon for connection status to
server, free storage space on local hard disk, icon for
highest alarm level in the supervised network, number
of active/stopped performance logs and number of
pending tasks.
Fault -> Current A larms… Opens the Current Alarms window. Filter setting are
reset to no filter.
Fault -> Alarm Log… Opens the Alarm Log window. Filter settings are reset
to no filter.
Fault -> Disabled Port Opens the Disabled Port Connections window
Connections…
Fault -> Disabled Paths… Opens the Disabled Paths window.
Fault -> Alarm and Path Opens the Alarms and Path Statist ic s window.
Statistics…
Fault -> Refresh Alarms ... Requests current alarm information for all reachable
network elements and update of the alarm list and
alarm log.
Fault -> Automatic Alarm Activates/deactivates the automatic alarm correlation.
Correlation
Fault -> Event Forwardi ng Activates or deactivates the forwarding of alarms and
path protection switching events from the NE controller
to the TNMS Core/CDM Server.
Note:
This menu should be used carefully as a kind of
emergency switch, e.g. in order to keep TNMS
Core/CDM operable even in cases of an excessive
alarm flow.
Fault -> Settings ... Fault settings for the audible signal and polling
interval.
Configuration -> Opens subscriber management.

Subscribers...
Config uration -> Create NE Creates a new NE container.
Container...
Configuration -> Create Port Creates a new port connection.
Connection...
Configuration -> Engage Starts an automatic link detection.
Link Detection
Config uration -> Create Creates a new service.
Service…
Config uration -> Create Creates a new path.
Path…
Configuration -> Opens the Routing Options window where you can
Preferences & Routing edit the options for automatic routing.
Options…
Configuration -> Distribute Initially the system clock of the TNMS Core/CDM
Time... Server is shown. After confirmation the clocks of all
reachable system components and network elements
18
are set to this time.

More information is provided under Distribute TNMS
Server time.
Performance -> Opens the overview window for viewing logs for
Performance Logs ... performance logs.
Security -> Login... Login to a TNMS Core/CDM Server.

Security -> Logout Logout from a TNMS Core/CDM Server.
Security -> Passwor d... Changes the password (for the logged in user).
Window -> Cascade Cascades the open windows, with one window partly
overlapping the other.
Window -> Tile Arranges the open windows next to one another.
Window -> Arrange Icons Rearranges the icons of all minimized windows.
Window -> Notific ation Log Restores the Notification Log window.
Window -> Network Opens the Network Management View window.
Management View
Help -> Help Topic s Opens the online help.

Help -> Help on Window Opens the online help on the currently selected
window.
Help -> Printable Opens a submenu with the following commands:
Documents - Technical Description (TED)
- Operator Guidelines (OGL)
- Installation Manual (IMN)
- Online Help
Each of these menu entries represents a part of the
TNMS Core/CDM documentation delivered as a *.pdf
file. The chosen documentation opens within the
Acrobat Reader application for reading or printing.
(Acrobat Reader is not part of TNMS Core/CDM, but
will be installed during the TNMS Core/CDM
installation.)
Help -> About TNMS Version information.
Client...
19
View optio ns
TNMS Client -> View -> Options... in the window View Options (in the Network Editor
mode) enables a number of settings to be made for displaying icons or info bars (indicators
for elements in the network view) to suit your personal preferences.
The following settings are possible:
Symbols:
The choice of icons is as follows:
- graphical: graphical icons
- technical: technical icons
- small: very small icons
Layout Guides:
If you activate the Snap to g rid option, icons are positioned according to the grid.
Value range for grid spacing: 1 to 100 pixels (default: 25 pixels)
Infobar Settings :
Choices for display of info bars (of the network elements in the Network Plan):
- hide: info bar is hidden,
- minimize: only first line of info bar will be displayed,
- maximize: info bar will be displayed fully.
Note: For a single network element in the Network Plan you can modify this setting
using the shift key and a click with the right mouse button.
Infobar Alignment:
For alignment of the info bar relative to the network element of theNetwork Editor view the
choices are as follows:
- left: to the left of the icon,
- right: to the right of the icon,
- to p: above the icon,
- bottom: below the icon.
Note:
For a single network element in the Network Plan you can modify these settings using the
ctrl key and clicking the right mouse button.
Infobar Transparency:
- With this adaptive controller you can adapt the transparency of the network element info
bars in the network map
- With the check box Portconnections snap to symbols the displayed port connection in
the network map can be snapped from the network element symbol to the network
element info bar.
Button:
- The button Ap ply is used to put the settings into effect.
20
General operating inform ation

Setting the toolbar view
You can set the view of the toolbar using the toolbar context menu. Simply right-click on
the toolbar anywhere except on an icon. The following options are provided:
- Pictures and Text (Bottom)
Icons are shown with text below them.
- Pictures and Text (Right)
Icons are shown with text to the right.
- Pictures only
Only icons are shown.
- Text o nly
Only text is shown.
You can hide the toolbar and show it again using View -> Toolbar .
Note:
A menu command corresponding to each icon is provided in the toolbar of the main
window.
21
Using t he keyboard
The TNMS user interface is menu-driven. The main menu commands can be accessed via
the main menu bar. Context menus are also provided, and to access these menus, you
must click with the right mouse button on the relevant object in the user interface. The
instructions in this online help have therefore been written with mouse users in mind.
Short Cuts:
It is also possible to use the keyboard to perform the actions listed in the main menus. Hold
down the alt key and press the underlined letters for the menu items you want to use.
Examples in TNMS Client:

• In order to open the Subscriber Management window either select the menu
entry Configuration -> Subscriber or use the shortcut Alt + C + S. As
"Configuration" has no underlined letter visible, press Alt.
• In order to open a context menu you can also use Shift + F10.
Some newer keyboards have a special key for opening context menus.
• In order to reach a button via a shortcut use Shift + Ctrl + <underlined letter of the
button>.
22
Icons
Icons: DCN components
Example of a network element.
Example of an UNO network element.

Example of an MSN.
Example of a TNMS Core/CDM subnetwork.

The NetServer is active.
Network element with access state ready.
The color of the icon shows the alarm of the highest severity of
the network element (TNMS Client only).
The NE resource (NE, NE container, service, performance logs
and fault locations) is locked meaning the user does not have
access to the NE resource. The access is dependent on the
user class or on the restrictions applied to the user group.
Network element with access state starting up. The DCN object
is initializing its data.
Network element with access state shutting down. The DCN
object is saving its data and is releasing its subcomponents.
Network element with access state disconnected. The DCN
object is known to the system but there is no connection
established to it.
Network element with access state disconnected. The TNMS
Server has lost the connection to the DCN object or a
connection cannot be established.
Other status (i.e. none of the above states apply).
At least on network element of this DCN channel with access
state ready. The highest alarm severity is displayed (TNMS
Client only).
All network elements of this DCN channel with access state
starting up or at least one network element with access state
starting up and all others with access state disconnected or
unknown.
All network elements of this DCN channel with access state
shutting down or at least one network element with access state
shutting down and all others with access state disconnected or
unknown.
Not all network element resources could be initialized. This
network element could not be used for operation. Use
Reinitialize and try to make this network element operable.
State that cannot be displayed by one of the states above
(TNMS Client only).
The DCN object is deactivated, i.e. the object is not in use by
the system. A connection is not established to this object.
The DCN object in question is being deactivated.
23
The DCN object in question is being activated.

The system is establishing a connection to the DCN object.
The connection to the DCN object is successfully established.
The DCN object has successfully completed its initialization and
is ready for operation.
The system is closing the connection to the DCN object.
At least one property of the DCN object is invalid (DCN object
cannot be used) The operator has to complete or correct the
properties accordingly.
24
Icons: Filter and sort icons i n lists

The following filter and sort icons are used in lists:
If information in a column of a list or log is filtered, a gray funnel

icon is shown in column header.
If information in a column of a list or log can neither be sorted
nor filtered, a red prohibition sign is shown in column header.
If information in a column of a list or log is sorted, a green arrow
is shown in column header.
25
Icons: Link connection

The following icons can appear in the Choose Link Connection window:
Link connection not yet existing, direction left
Link connection not yet existing, bi-directional
Link connection not yet existing, direction right
Link connection existing, direction left
Link connection existing, bi-directional
Link connection existing, direction right
Li nk connect i on t hr ough f l oat i ng TPs and SNCs i n

CDM, di r ect i on l ef t
Li nk connect i on t hr ough f l oat i ng TPs and SNCs i n
CDM, di r ect i on r i ght
Fragment path, direction right
Fragment path, bi-directional
Fragment path, direction left
Fragment path not yet existing, bi-directional
Fragment path not yet existing, direction left
Fragment path not yet existing, direction right
Half open server path
Half open fragment path
Server path
Fragment path
26
27
Icons: Network elements

(Surveillance and Network Editor mode)
Example of a network element.
Example of a subnetwork element.

Network element locked for routing (Administrative State
locked).
The color of the icon shows the alarm of the highest severity of
the network element.
Network element with access state ready and operational state
enabled (Services mode).
Network element with access state ready and operational state
disabled (Services mode).
Network element with access state starting up.
Network element with access state shutting down.
Network element with access state disconnected.
Network element with a transition state. This state may apply

(only for a short time) during initialization of a network element
when alarm information from this network element is not yet
available.
Not all network element resources could be initialized. This
network element could not be used for operation. Use
Reinitialize and try to make this network element operable.
None of the above states apply.
NE container
User and user group with access to the whole network managed
by TNMS.
User with access to specific NE container.
NE container contains at least one network element with access
state ready. The highest alarm severity in the NE container is
displayed.
In this NE container all network elements with access state
ready have the operational state enabled.
In this NE container at least one network element with access
state ready has the operational state disabled (Services mode).
28

In this NE container all network elements have the access state
starting up or at least one network element has the access state
starting up and all others have the access state disconnected or
unknown.
In this NE container all network elements have the access state
shutting down or at least one network element has the access
state shutting down and all others have the access state
disconnected or unknown.
Network element with access state disconnected (there is no
DCN connection to the network elements).
Network element with access state disconnected (the TNMS
Core/CDM Server has lost the connection to the NetServer of
the network elements).
29
Icons: Network infrastructur e and protection

Protection in the Network Infrastructure tree
BSHR-2/4
Operational state: enabled
Administrative state: unlocked
Provisioning state: provisioned
BSHR-2/4
Operational state: disabled
BSHR-2/4
Administrative state: locked
BSHR-2/4
Provisioning state: unprovisioned
MSP
Operational state: enabled
MSP
Operational state: disabled
MSP
Administrative state: locked
MSP
Provisioning state: unprovisioned
Protection in the MSP Properties wind ow

Icon Protection Protection State
BSHR-2/4 No protection
MSP
BSHR-2/4 Does not function correctly
BSHR-2/4 Normal
BSHR-2/4 East ring
BSHR-2/4 West ring
BSHR-4 Both rings (temporarily)
BSHR-4 West span
BSHR-4 East span
BSHR-4 Both spans
BSHR-4 West span east ring
BSHR-4 East ring west span
st
MSP The protection does not work correctly.
(1 PG)
30
nd
(2 PG)
st
MSP Working
(1 PG)
nd
(2 PG)
st
MSP Protecting
(1 PG)
nd
(2 PG)
31
Icons: Network Plan
Network Plan
Network element (example).
Universal network element (example).

Subnetwork (example).
Virtual port.
NE container.
The icon is shown in the upper left corner in the Network Editor view of the
TNMS Client. You can move one step upwards into the parent NE container
(if it exists) by clicking onto the icon.
Network element in NE mode Maintenance.
Network element locked for routing (Administrative Statelocked).
The DCN object is being deactivated.

The DCN object is being activated.
The system is establishing a connection to the DCN object.
The system is closing the connection to the DCN object.
The connection to the DCN object is successfully established.
Not all network element resources could be initialized. This network element
could not be used for operation. Use Reinitialize and try to make this
network element operable.
At least one property of the DCN object is invalid (DCN object cannot be
used). The operator has to complete or correct the properties
correspondingly.
The connection to the NE could not be established.
Icons in Operatio nal state Acc ess state

infobar
enabled ready
disabled ready
unknown disconnected
unknown failure
unknown starting up
unknown shutting down
32

The color of the icon shows the alarm of the highest severity of the
network element. More information is provided under Alarm severities
and alarm states.
Button to collapse info bar
Button to enlarge info bar
Write access (see also Controlling write access to a network element ).

state
Unknown
No write access
External OS/LCT
NEC
Element manager of this TNMS Core/CDM
Element manager of this TNMS Core/CDM and NE controller
No write access and External Access
This TNMS and External Access
This TNMS, EM of this TNMS and External Access
Port
Connections
Unlocked, provisioned port connection with alarms on both ends
(highest alarm severity is shown on both ends of the port connection)
Unlocked, provisioned port connection, alarm-free
Unlocked, unprovisioned port connection
Locked, unprovisioned port connection
Locked, provisioned port connection
33
Icons: Port Connections, Path Wizard and Connection As sistant

Connection Types
The window Connection Assistant and the window Path Wizard – Define Topology
provide different templates for connection type representation:
Connection Assistant Path Wizard – Define Description
Templates Topology Templates
bidirectional cross connection
bidirectional cross connection with protected

head end
bidirectional cross connection with protected

tail end
unidirectional cross connection
unidirectional cross connection, reverse

direction
unidirectional cross connection with protected

head end

tail end

tail end

head end
double add drop
double add drop (A to Z)
double add drop (Z to A)
tandem protection simple:

simple protection in reverse direction
tandem protection double:

double protection in reverse direction
drop_continue # 1:
drop and continue cross connection
34
drop_continue # 2:
drop_continue # 3:
drop_continue # 2-1:
drop_continue # 3-1:
unconnected startpoint:
Used to monitor ports outside the start point of
a cross connection (in the case of server
paths)
unconnected endpoint:
Used to monitor ports outside the end point of
a cross connection (in the case of server
paths).
loopback at all TPs:
Used to loop back the path within the switching
network.
Bord er Crossin g Mode (e.g. in: Path Wizard – Define Topology )

A- Z-End Descriptio
End n
Exit point
Entry point
Resilience (e.g. in: Path Wizard – Define Topolog y)

Indicates the path protection for the direction A to Z.
Unprotected
path
Protected path
Port / TP Icons (e.g. in Connecti on As sis tant and Path Wizard – Define Topology)
Note: The display of icons for ports, TPs and cross connections represents only a
snapshot. The state of these resources is not updated according to the changes in the
network. To avoid differences regarding the display of icons between the window, simply
re-open the concerned window.
Icon Icon Descript ion

Overlay for ports that are locked for routing
35
Floating port
Floating TP enabled
Floating TP disabled
CTP, disabled
CTP, enabled
CTP, unavailable
TTP, disabled
TTP, enabled
TTP, unavailable
Indication of existing port connection (at TP items), bidirectional
Indication of existing port connection (at TP items), unidirectional sink
Indication of existing port connection (at TP items), unidirectional source and sink
Indication of existing port connection (at TP items), unidirectional source
Indication of existing server path reference (at TP items), bidirectional
Indication of existing server path reference (at TP items), unidirectional sink
Indication of existing server path reference (at TP items), unidirectional source
Indication of existing fragment path reference (at TP items), bidirectional
Indication of existing fragment path reference (at TP items), unidirectional sink
Indication of existing fragment path reference (at TP items), unidirectional source
Indication of existing fragment path reference with ACS = defined (at TP items),
bidirectional
unidirectional sink
unidirectional source
Card enabled
Card disabled
Overlay for cross connections
Blue frame overlay: If this TP is used by this path
Brown frame overlay: If this TP is used by another path (Note, that there is no
difference in visibility if the referenced path is managed or unmanaged)
Port connection (at port items), bidirectional
Port connection (at port items), unidirectional sink
Port connection (at port items), unidirectional source and sink
36
Port connection (at port items), unidirectional source
Electrical port, disabled
Electrical port, disabled Rx
Electrical port, disabled TX
Electrical port, enabled
Optical port, disabled
Optical port, disabled Rx
Optical port, disabled Tx
Optical port, enabled
Radio port, disabled
Radio port, disabled Rx
Radio port, disabled Tx
Radio port, enabled
Subscriber port
Subscriber port connected bidirectionally
Subscriber port, connected unidirectionally
Bidirectional CC with border crossing mode (BCM) Exit-Exit

Bidirectional CC with border crossing mode (BCM) Exit-Entry
Bidirectional CC with border crossing mode (BCM) Entry-Exit
Bidirectional CC with border crossing mode (BCM) Entry-Entry
Unidirectional CC sink with border crossing mode (BCM) Exit-Exit
Unidirectional CC sink with border crossing mode (BCM) Exit-Entry
Unidirectional CC sink with border crossing mode (BCM) Entry-Exit
Unidirectional CC sink with border crossing mode (BCM) Entry-Entry
Unidirectional CC source with border crossing mode (BCM) Exit-Exit
Unidirectional CC source with border crossing mode (BCM) Exit-Entry

Unidirectional CC source with border crossing mode (BCM) Entry-Exit
Unidirectional CC source with border crossing mode (BCM) Entry-Entry
37
Icons: Routing
Routing View Icons
(in: Service / Path Properties – Routing and in: Path Wizard – Routing Results)
The state icon, which is displayed under a node in the routing view, depends on the ACS of
the route element and the RCS of the path or the RCS of the route element if the ACS is
under test. The possible icons are shown in the following table:
Icon Route Element-ACS Path-RCS Operatio nal State

*
In deletion *
undefined or = undefined or
not routed or = not routed or *
not active = not active
= undefined or <> undefined and
= not routed or <> not routed and *
= not active <> not active
RE-RCS
<> under test *
= under test
RE-RCS
= under test *
= under test
* = active or disabled
= unmanaged
* = active or enabled
= unmanaged
38

General
The table shows all other main icons used in the Subscribers and Services tree view:
Enabled Disabled Protection Object
Disturbed
Subscriber
Simple Path Container

Can be created by the user and be used
as additional structure element for the
tree. Container symbol is yellow.
See: Creating a path container.
System Container
Will be created by TNMS within the default
Path Container and can neither be
renamed or deleted by the user. Container
symbol is grey.
Service
State Icon
The following state icons are used in the Subsribers and Services view and in the
Unmanaged Paths tree view:
Note:
For unmanaged paths shown in the Unmanaged Paths tree view there exists no alarm
correlation (i.e. the automatic alarm correlation is set toOff ).
Icon
Icon Administrative Has Al arm Correlation
State Clients? Method
- unlocked no automatic
unlocked no extended automatic
unlocked no disabled
unlocked yes automatic
unlocked yes extended automatic
unlocked yes disabled
locked no automatic
locked no extended automatic
locked no disabled
locked yes automatic
locked yes extended automatic
locked yes disabled
39
Termination Points: Endpoint s

This sub-icon indicates the number of the path endpoints (1 or more) and their termination
mode for each side (a and z).
Note:
If the connection type is unknown, e.g. if there are more than two endpoints at one side of
a path, then the type and number of endpoints will not be visible in the path icon.
The following TP sub-icons are defined:
st nd
Enable Disable Path i s Connection 1 Endpoint 2 Endpoint
d Path d Path Protection Type
Disturbed
<not existing> <not existing> <not existing>
(Path topology is
undefined)
= unknown <don't care> <don't care>
≠ unknown non- <not existing>

terminated
≠ unknown terminated <not existing>
≠ unknown terminated non-

terminated
≠ unknown non- non-

terminated terminated
≠ unknown terminated terminated
≠ unknown non- terminated

terminated
Termination Points: Border Sub-Icon

This sub-icon indicates the border crossing mode by an open frame hinting the boundary of
the terminating MLSN for each side (a or z).
Note:
If TPs of the same side have different border crossing mode, then this difference will not be
visible in the path icon.
Icon Border Crossing Mode
a-side: entry
z-side: entry
a-side: entry
z-side: exit
a-side: exit
z-side: entry
a-side: exit
40
z-side: exit
Undefined path topology.
In this case, the connection type might be
unknown or there are different border crossing
modes for TPs on the same side.
Enable primary Alarms

Enable secondary Alarms
Disable all Alarms
Bandwidth Ok
Bandwidth Mismatch
Trail Overbooked
Trail Underbooked
Connection Arrow Sub-icon

This sub-icon indicates the direction and type of path. The following icons are defined:
Opera Ena Ena Disa Disa Protecti Protecti Connec Resili
tional bled bled bled bled on on tion ence
State Disturb Disturb Type
ed ed
Direct bi uni bi uni bi uni
ion
complex any
simple protect
ed
simple unprot
ected
head any
double any
tail any
Overlay Icon
The overlay icon is used for path objects and their container objects in order to indicate the
worst creation state, i.e. combination of actual (ACS) and required creation state (RCS).
The icon color expresses the assumed degree of the operator's problem about the path
being in this state (the more red the more problematic).
At container objects (service, simple path container, subscriber) this state indication is also
given, reflecting the worst creation state of all subordinate paths (the one with the lowest
order number).
Order Icon RCS ACS Comment
1 active not routed Path is required to be activated.
Problem indication: There is possibly a route
mismatch or a topology mismatch
41
2 not active not routed Topology and route are defined, but are not
activated.
mismatch or a topology mismatch.
3 under test not routed Path is required to be under test.
mismatch or a topology mismatch.
4 active not active Path is required to be activated.
Problem indication: There is a discrepancy
between actual and required resources.
5 active under test Path is required to be activated.
Problem indication: ... but is actually for some
reason under test.
6 under test not active Path is required to be under test .
Problem indication: There is a discrepancy
between actual and required resources.
7 under test active Path is required to be under test.
Problem indication: ... but is actually not under
test.
8 in deletion in deletion The path is being deleted.
9 undefined undefined No topology has been defined.
10 not routed not routed Only a topology has been defined.
11 not active not active Topology and route are defined, but are not
activated.
12 not active under test Topology and route are defined, but are not
activated.
13 not active active Topology and route are defined and activated.
14 under test under test Path is required and actually under test.
15 unmanaged under test Path is unmanaged and under test.
16 no active active Path is required and actually activated.

overl
ay
icon
17 no unmanaged active Path is unmanaged and actually activated.
overl
ay
icon
State Icons in the Service Properties window

Note:
These are the default colors of state icons which are used in theService Properties
window. The colors can be changed under TNMS SysAdmin.
Critical
Major
Minor
42
Warning
Indeterminate
Cleared
43
Lists and logs handling

General log management information
TNMS provides the following logs:
Name TNMS TNMS Log class

Client SysAdmin
Alarm log X permanent

System message log X X permanent
Network event log X permanent
Security event log X permanent
Operator input log X non-persistent
Performance log X custom
Notifications log X X non-persistent
Permanent logs
Permanent logs are created automatically when the system starts up. There is always only
one permanent log for each log type.
In TNMS Client you can call up a list with the permanent logs via View -> Tables. You can
also call the logs selectively from the View menu.
In TNMS SysAdmin you can open the security event log and system message log directly
via View -> Securit y Event Log/System Message Log. You can also select the required
log via View -> Tables.
Custom logs
Custom logs are operator-defined The performance log is the only type of custom log,
however several performance logs are possible.
In TNMS Client you can display performance logs using Perfo rmance -> Performance
Logs. You can also open performance logs via View -> Tables, or by right-clicking a
service and selecting View Performance Log... from the context menu which appears.
Non-persistent logs
Non-persistent logs only exist for the duration of a client session. The log content is deleted
when the client session is closed.
You can open the operator input log in TNMS SysAdmin via View -> Operator Input Log
or via
View -> Tables. Once TNMS SysAdmin and the TNMS Server have been started, the
notifications log is displayed in both TNMS SysAdmin and TNMS Client. It can be
minimized but not closed.
More information on displaying logs is provided under Viewing logs.
44
Print preview
The Print... context menu provided in various logs and lists opens thePrint preview
window showing the content of the log/list as it will be printed when activating the printer
icon of the toolbar.
The menu bar of the Print preview window is displayed as follows:
Four arrow buttons are provided for browsing through the list:
(from left to right: go to first page, move one page back, move one page forward, go to last
page.
Between the arrow buttons you can see which page is currently displayed.
The square stop button can be used to halt the reading in of list entries in the preview. For
example, if the list contains 9500 entries you can stop list entries being read in after the
first 500 entries.
Clicking on the printer icon prints the displayed content.
The zoom factor for the displayed list can be set in the field beside the printer icon.
45
Printing logs
If you have opened a log window, you open the context menu and select thePrint... entry
(click in the window with the right mouse button). A print preview is created first for viewing
the possible print result. Using the printer icon you can now print out the displayed print
preview.
With the log window active you can also use File -> Print....
More information is provided under Print preview.
46
Setting ti me filters for lists and logs

All display windows for events (current alarms and all logs) provide the option of specifying
a time from which entries are to be considered for display.
1. To do this, click the right mouse button on the Time (Local) column.
2. Activate the Filter With the Current Cell context menu in order to display the Filter
Date Time window.
3. Select the Show Log Entries Since checkbox to specify a start time for the log entries
to be displayed.
4. Select the Show Log Entries Until checkbox to specify an end time for the log entries
to be displayed.
5. Click the Apply button to confirm your settings.
47
Setting columns
Activating the Column Settings... context menu of lists and logs opens a small window in
which you can select / deselect the columns to be displayed.
More information is provided under Icons: Lists and Setting filters and sorting lists.
48
Setting fi lters and sorting li sts

Filtering lists
To restrict the number of entries shown in a list or log on the basis of certain criteria, click
with the right mouse button in the list/log. The context menu which appears will offer a
selection of the following functions (not all of them will always be available or sensitive):
- Browse Archived...
Shows the different archived logs.
- Details…
The information of the selected line is displayed in a Details window.
- Column Settings...
Opens a list where you can select/deselect columns for display.
- Copy
Copies the information of the selected row into the clipboard.
- Filter For Path Switching Events (Network Event Log)
Only entries of switching events of the paths. The list shows the paths that changed
state. One line for the paths state "enabled" and one line for the state "disabled".
- Filter With the Current Cell
Only entries which have the same content of the selected field in this column are
displayed. In the Time (Local) column, a window for selecting a time period appears.
Current filter settings are displayed by a icon in the relevant column header.
- Exclude the Current Cell
Only entries which do not have the same content of the selected field in this column
are displayed. In the Time (Local) column, a window for excluding a time period
appears.
Current filter settings are displayed by a icon in the relevant column header.
- Filter...
Opens the Set Filter window.
- Filter for Empty Cells
Filters for empty cells, i.e. only records with empty cells are displayed.
- Filter for Non Empty Cells
Filters for non empty cells, i.e. only records with non empty cells are displayed.
- Freeze
Freezes the rows of the current log. If you select one or more row with your mouse,
they will stay selected even if more entries are added to the log.
- Load Filter...
Loads the filter settings from a file.
- Print...
Opens a print preview window where the list is displayed and filtered in accordance
with the filter and sort criteria which have been set. The preview shown can be printed
out using the printer icon.
- Print With Details...
Prints a list of the contents (according to the current filter and sort settings) including
the information displayed when the Route or Usage Details context menu is activated.
- Refresh
Updates the contents of the current window.
- Reset All Filters
Use this context menu to switch off all filters. Note that this command does not exist in
all list and log windows.
- Set Filt er...
Initiates a new data collection for the operator input log, i.e. open the Set Filter to
Operator Input Log window, specify new filter settings and request new data.
49
- Save As...
Saves the log as an *.tsf file which can then be read in MS Access and MS Excel. The
current filter and sort settings are retained in the *.tsf file.
- Save As With Details ...
Saves the list in TSF format (to allow reading in MS-Access and MS-Excel) according
to the current filter and sort settings including the information displayed when the
Details context menu is activated.
- Save Filter...
Saves the filter settings into a file.
- Toggle Index On/Off
Shows/hides the index.
- Undo Filter
To undo a filter, click on the column in which the filter was set.
The list of port connections, services, ports and termination points can be further
filtered using the Scope Type selection at the top of the window.
Sorting li sts
By left-clicking the column title, individual columns can be sorted in ascending or
descending order. The sort sequence selected only applies to the data display. The data
itself is not modified.
Click once to sort in ascending order and twice to sort in descending order. A third click
restores the original list sequence.
Multiple sorting of the lists are also possible via the following:
1. Click on specific column to initiate the sorting in the sequence upwards or
downwards.
2. Click on specific column with pressed CTRL button to extend the sorting to the next
column.
Maximum 3 sortings shall be possible in parallel.
More information is provided under Icons: Lists.
Note:
Every permanent log is split up into an active part and a log archive. New log entries are
written to both the active log and the log archive. When an active log reaches its limit, the
oldest log entry is deleted. For permanent log types, the active log and the archived log
can be viewed in separate windows. The log archive only shows a snapshot and is not
updated automatically for performance reasons. The log archive can be updated manually.
50
System message log

The System Message Log window displays a history of relevant administrative events.
Events logged in this log are:
- DCN channel connect and disconnect notifications.
- Scheduled job activation and deactivation.
- Scheduled job error messages and notifications.
- Administrative configuration changes.
- Timeouts of telegrams sent to network elements.
- Notifications regarding system anomalies (internal components faults, database errors,
etc.).
- Faults regarding received telegrams (unexpected responses, invalid address, syntactic
errors, etc.).
To display the system message log from the TNMS Client you can e.g. use View ->
System Message Log.... For each system message displayed you will find the following
information:
- Index
Number of the row in the list.
- Icon
To the left of the system message there is a icon showing three different severities for
system messages:
= Message
= Warning
= Error
- Time (Local)
Indicates the time at which the system message arrived. The time stamp is generated
by the TNMS Server. In this case the time value is marked with an asterisk (*).
Severity
There are three different severities for system messages:message, warning and
error.
- Source Type
Original source of the event (e.g. NE, TNMS Server, database, controller, etc.).
- Source
Component which has detected the event (e.g. NE name, server name, etc.).
- Description
Description of the event which lead to the preceding system message.
- State
The status of system message is displayed as either Acknowledged or
Unacknowledged.
- Operator
Identification of the operator who acknowledged or initiated the event.
- Computer
Computer where the operator in question has logged in or from where the event was
initiated, e.g. a Create Backup.
By right-clicking in the window, you can activate a context menu with various filter and sort
functions.
51
More information on these functions is provided in Setting filters and sorting lists and Icons:
Lists.
52
Viewing log s
Logs can be viewed both from the TNMS Client and from the TNMS SysAdmin. However,
the logs accessible from the TNMS Client differ from the logs accessible from TNMS
SysAdmin.
In TNMS Client, View -> Tables... opens a list window with tabs for viewing standard logs,
archived logs and performance logs. Alternatively, click the buttonLogs in the TNMS
Client toolbar.
In TNMS SysAdmin, View -> Tables... opens a list window with tabs for viewing standard
logs and archived logs. Alternatively, click the button Tables in the TNMS SysAdmin
toolbar.
In each case, logs can be viewed by selecting a log entry from the displayed list and
clicking View.
Standard Logs
Clicking on the Standard Logs tab opens the Standard Logs window where existing
standard logs are displayed.
The following standard logs can be viewed from TNMS Client:
Active alarm log, active network event log, active system message log, current alarms.
The following standard logs can be viewed from TNMS SysAdmin:
Active system message log, active security event log, operator input log.
- Index
Counter for each standard log.
- Name
Name of the displayed standard log
- Current Log Size
Current log size of the displayed standard log.
- Maximum Log Size
Maximum log size of the displayed standard log.
- Fill state
Fill state in percent of the displayed standard log.
Arch ived Logs

Clicking on the Arch ived Logs tab opens the Ar chived Logs window where existing
archived logs are displayed.
The following archived logs can be viewed from TNMS Client:
Alarm log, network event log, system message log.
The following archived logs can be viewed from SysAdmin:
System message log, security event log.
- Index
Counter for each archived log.
- Name
Name of the displayed archived log
- Current Log Size
Current log size of the displayed archived log.
- Maximum Log Size
Maximum log size of the displayed archived log.
- Fill state
Fill state in percent of the displayed archived log.
53
Performance Logs (this tab is only visible in TNMS Client)

Clicking on the Performance Logs tab opens the Performance Logs window where
existing performance logs are displayed. You can also open this window by selecting
Performance -> Performance Logs: Performance Logs . Performance logs can only be
viewed in TNMS Client.
For each performance log the following information is displayed:
- Index
- Log name
Name of the performance log set by the operator during configuration of the
performance log.
- Log type
The log type can be 'Performance Log' or 'TCM Log'.
- Created By
Operator who created the performance log.
- Creatio n Time (Local)
Time the performance log was created.
- Current Log Size
Number of entries.
- Log full warning threshold
During configuration of the performance log the operator specifies whether a warning
should be signaled when a certain percentage of entries has been exceeded. Here the
specified threshold is displayed.
- Interval
Shows the period of time used for collecting the performance data, either 15min or
24h.
- Admin State
Active for a log that is started (performance data is currently being measured).
Standby for a log that has been stopped.
- Provision State
The provisioning state shows if assigned PMPs can be monitored (provisioned,
unprovisioned) .
Notes:
The following holds for the provisioning state if a TNMS Core/CDM system runs
standalone (without CDM):
- A PMP contained in a PM Log is unprovisioned if it does not exist anymore (e.g.
because of card deletion or the corresponding TP is no longer valid).
- A PM Log is unprovisioned if at least one contained PMP is unprovisioned or
the administrative of at least one contained PMP is locked.
- Path
If a path is assigned to a performance log, the name of this path is displayed here.
- Service
If the performance log has been created including a service in the PMP container, the
name of this service is displayed here.
- Subscriber Name
Subscriber to whom the above service is assigned.
Using the buttons at the top of the window you can:

- Update the selected performance log. The table of all performance logs is, however,
not updated. To update the table of all performance logs, press <F5>. The Admin State
must be Active.
54
- View the current data of a selected performance log.

- Print the selected performance log. A print preview is created first for viewing the
possible print result.
- Modify the configuration of a selected performance log. The Admin State must be
Standby.
- Add (create) a further performance log.
- Delete a selected performance log. The Admin State must be Standby.
- Start the measurement for a selected performance log.
- Stop the measurement for a selected performance log.
- Close the window.
- Threshold allows you to configure the threshold for the selected performance log.
- Help open the help for this window.
By right-clicking in the list, you can activate a context menu in order to setFilters for the
current data, and also to view, print and save the table details.
descending order.
More information on filter and sort functions is provided in Setting filters and sorting lists
and Icons: Lists.
See also:
Permanent logs
55
Perfo rmance Log Export Tool (PLET)

Configuring the Performance Log Export Tool (PLET)
1. When you start PLET for the first time, a configuration window appears providing a
default configuration. You can change this configuration now or open the configuration
window later by either
- selecting Options -> Set Schedule to save, or
- pressing the button in the PLET main window.
You can configure the following parameters:
- Saving Schedule
This specifies how often the logs should be exported: every 15 minutes, every
hour or every 24 hours (default value).
- Database Locatio n
The computer where the SQL database is located is entered here. The default
computer is the computer where PLET is installed.
- Export Path
The directory to which the export files should be written is specified here. The
default directory is the directory where TnmsPerfLog.exe is located.
- Export Format
The format of the export files is specified here.
- Set Start Time
You can specify what time the logs should be exported at here. The default
value is 00:00. If the specified start time has already passed, the export
procedure will start immediately.
2. To save your configuration, press the Start button in the configuration window.
56
Exporting lo gs using PLET

PLET allows you to export the following logs:
- TNMS performance logs
- TNMS system message log
- TNMS network event log
- TNMS alarm log
1. Select the required log(s) in the PLET main window by clicking the appropriate
checkboxes. To select all displayed logs at once, select Edit -> Select A ll.
2. Press the button Apply Selection to confirm your selection. The list of performance
logs displayed in PLET is not automatically updated. To synchronize the displayed list
with the database, press the button in the PLET main window or select View ->
Refresh.
You can export performance logs either at a scheduled time or immediately. More
information on scheduling an export is provided under Configuring the Performance
Log Tool (PLET).
Scheduled Export
You can start the scheduled export by one of the following actions:
- pressing the button in the PLET main window,
- selecting Start scheduled save from the context menu,
- selecting Options -> Set Schedule to save... -> Start.
Note:
The first two options are only active if the scheduled export is not yet running.
You can stop the scheduled export by one of the following actions:
- pressing the button in the PLET main window, or
- selecting Stop scheduled save from the context menu.
Note:
The these options are only active if the scheduled export has been started.
Immediate Export
As well as scheduling an export, you can also store the selected logs immediately in the
configured export directory. You can do this by one of the following actions:
- pressing the button in the PLET main window,
- selecting Save from the context menu, or
- selecting File -> Save.
57
TNMS OTS-4000 Perf ormance Add On Tool (TOPAT)

TOPAT - General Informati on
TOPAT (TNMS OTS-4000 Performance Add On Tool) allows the configuration and
maintenance of the performance log information collected from the OTS-4000 surveyed
NEs. This is done with a network where OTS-4000 surveyed NEs send their performance
log information through a FTP session to a FTP-Server hosted in the TNMS-Server.
TOPAT software is an add-on tool for the TNMS Core/CDM. TOPAT runs alone with no
interaction with TNMS Core/CDM and is composed of two different software applications,
TOPAT-Server and TOPAT-Client.
TOPAT-Server
TOPAT-Server is installed in TNMS-Server host computer, and periodically processes the
performance log information collected from the NEs, generating a separate file for each
path.
TOPAT-Client
TOPAT-Client is located in TNMS-Client host computers, and provides a Graphical User
Interface (GUI) for configuration and management of NEs performance log information.
Note:
It must be possible to establish a FTP-session between TNMS Server and all the surveyed
OTS-4000 NEs. It must be possible to log into the web interfaces through the TNMS
Clients Internet Explorer of all the surveyed OTS-4000 NEs.
See also:
TOPAT GUI
PMP Configuration
58
TOPAT GUI
This window enables the server connection configuration and the access to general
performance log operations of the OTS-4000 NEs.
Establishing paths t o NEs

1. Insert the server name in the Connect to TOPAT-Server field. This holds the
processed OTS-4000 performance log information.
2. Click the Connect button.
After the server connection has been configured, you can access the various performance
log settings through the available tabs.
You can switch between three different views by clicking the available tabs at the bottom of
the window, namely Configure, Modify and Show tabs.
Configure Tab
Clicking on the Configure tab opens the Configuration window which enables to
create a new performance log definition.
The performance logs collect the relevant performance information from the OTS-
4000 paths.
Creating a performance log d efinition

1. Fill in the available fields as follows:
- Performance Log Name
Use this entry to identify the new log with a name.
- Measure in terval
Use this radio button to establish the time interval between measurements.
Available values are 15 minutes and 24 hours.
- Date of Recording
Use this field to define the start date when the first measurement is
executed.
- Start Hour of Recording
Use this field to define the start time when the first measurement is
executed.
- Correlating to Path
Use this field to identify the path assigned to the performance log.
- Correlating to Service
Use this field to identify the service assigned to the created performance
log.
- Correlating to Subscriber
Use this field to identify the subscriber to whom the above service is
assigned to.
- OTS-4000 #1
Use this field to select one OTS-4000 NE where performance logs are
collected.
- Click the Choose PMP button to open the PMP conf iguration window
where the performance log settings are configured.
- OTS-4000 #2
Use this field to select a second OTS-4000 NE where performance logs
are collected. This second NE is optional.
59
- Click the Choose PMP button to open the PMP conf iguration
window.
2. After the performance log has been configured, click theSave Perform ance Log
Definition button to save the information.
Modify Tab
Clicking on the Modify tab opens the Modify window which enables to modify and
delete an existing performance log.
Modifying a performance log definiti on

1. Select the performance log using the Performance Log field.
2. Click the Request Performance Log Definition button so that the available
fields are automatically filled with the actual performance log definition values.
3. Fill in the fields you want to modify with the new values as described in the
4. Click the Modify Performance Log Definition button. The performance log is
saved with the modifications.
Deleting a performance log

2. Click the Request Performance Log Definition button so that the available
fields are filled with the actual performance log definition values.
3. Click the Delete Performance Log Definition button. The performance log is
deleted.
Show Tab
Clicking on the Show tab opens the Show window which enables to display the
performance log information, and to save this information into a file.
Showing performance log information

2. Click the Request Performance Data button so that the Performance Log Data
can be showed. The performance Log Data includes the correlated path, service
and subscriber and all the PMP collected values displayed in a table.
Saving performance log information

1. Follow the steps required for showing performance log information as described
before.
2. Click the Save Performance Data button. The information is saved under the
name "<log_name>_<date>.dat".
Note:
If some monitor values available at the table have information in brackets, means that
some monitor values are invalid in a certain measurement interval. Inside the brackets
is displayed the measurement interval holding valid monitor values.
Click the Exit button to close TOPAT Client application.
60
See also:
TOPAT - General Information
PMP Configuration
61
PMP Configuration
Open the PMP conf iguration window via: TOPAT Client -> Configure -> Choose PMP
button (from OTS-4000 #1 or #2).
In this window, the OTS-4000 NE communication port is configured and the PMP
parameters are selected in order to define which information from the OTS-4000 NE is
included in every performance log entry.
At the left side of the window, OTS-4000 NE communication port is configured:
Entry Option Descripti on

PMP Shelf OTS-4000 shelf number of the module.
Slot OTS-4000 slot position of the module.
Equipment 4010 OTS-4010 module is used.
Type
4040 OTS-4040 module is used.
Port Type Line OTS-4000 Line-PMP port is used.
Trib #1 OTS-4000 Trib nr.1-PMP port is used.
Direction Tx Transmitter port direction is used.
Rx Receiver port direction is used.
Location Near Near end location connection is used.
Far Far end location connection is used.
At the right side of the window, PMP parameters are defined using the following available
options:
- Optical Power – min [ OP-Min]
Minimum optical power level.
- Optical Power – max [ OP-Max]
Maximum optical power level.
- Optical Power – avg [OP-Avg]
Average optical power level.
- Code Violation [CV]
Number of Code Violation occurrences.
- Errored Seconds [ES]
Number of accumulated Errored Seconds (ER) during the measurement interval.
An ES occurs when during that second one or more Background Block Error
occurred or at least one defect occurred.
- Severely Erro red Seconds [ SES]
Number of accumulated Severely Errored Seconds during the measurement
interval. An ES occurs when during that second the number of Errored Blocks (EB)
has crossed a determined threshold that is configurable by the operator.
- Severely Err ored Frame Seconds [SEFS]
Number of accumulated Severely Errored Frame Seconds during the
measurement interval.
62
- FEC Corrected Bi ts [FEC-CB]

Errored bits corrected with FEC.
- FEC Uncor rected Word s [ FEC-UW]
Detected errored words that weren’t corrected with FEC.
- Bit Error Rate [BER]
Rate of errors occurred.
The following buttons are available at the bottom of the window:

- Save
Saves the current PMP configuration.
- Prev. PMP
Jumps to the next PMP configuration window associated with the same
performance log.
- Next PMP
Jumps to the previous PMP configuration window associated with the same
performance log.
- Delete
Deletes the current PMP configuration, returning to the default configuration.
- Close
Closes the PMP configuration window and returns to the TOPAT-Client main
window.
Note:
Always start by the OTS-4000 NE communication port configuration, as the available PMP
options depend on the configured OTS-4000 NE communication port.
After the desired settings are configured, press the Save button before pressing any other
button, avoiding the configuration lost.
See also :
TOPAT - General Information
TOPAT GUI
63
Launc hing TNMS ASON / Ethernet Manager GUI

It is possible to launch the GUI of TNMS ASON / Ethernet Manager directly from the TNMS
Core/CDM GUI.
Prerequisites
The following prerequisites must be met before you can launch the GUI of TNMS ASON /
Ethernet Manager from the TNMS Core/CDM GUI:
- The TNMS Core/CDM client application and the TNMS ASON / Ethernet Manager client
application are running on the same machine.
Launching the GUI of TNMS ASON / Ethernet Manager from the TNMS Core/CDM GUI
1. Open the main window of the TNMS Core/CDM client.

2. On the Client AddIn menu, click ETH/ASON Manager .
The TNMS ASON / Ethernet Manager GUI is launched.
64
Technical background inf ormation on
65
Concatenation
This topic contains general information on concatenation within TNMS Core/CDM.
Concatenation (synonymous notion is Inverse Multiplexing) allows the transport of a
tributary signal with a higher bandwidth than the nominal path transport capacity.
TNMS Core/CDM supports following concatenation types, whereby the supported

concatenation types and layers depend on the NE:
• Contiguous Concatenation
means that e.g. X VC4 signals do not float independently from each other in the STM-
N frame. They are concatenated to one VC4-Xc signal. That means that there is only
one AU-4 pointer which points to the first concatenated VC4. The path overhead
(POH) is only valid for the first VC4.
• Virtual Concatenation
means that e.g. for a VCN-Xv that X VCN signals float independently from each other
in the same STM frame. They are concatenated virtually to one VC4-Xv signal. There
are still X AU pointers and X path overheads (POH) valid for each VC. The maximum
delay between the first and the last VC must not exceed 125 ms.
As si gnment of Termi nation Points to Group Termination Point s:

A number X of TPs of transport layer N are assigned to a Group of TPs denoted as
Group TP (GTP). Depending on their termination mode there are:
- Group TTP (GTTP) and
- Group CTP (GCTP).
TPs of transport layer N assigned to Group TPs are denotedfragment TPs (fragment CTP
or fragment TTP). The Transport layer N of a fragment TP is denoted fragment Layer.
According to the concatenation types virtual and contiguous there are:

- contiguous Group TPs and
- virtual Group TPs.
Configuration of Termination Points:

The termination points can be configured either via EM/LCT or via TNMS Core/CDM:
TP configuration via EM/LCT:

Contiguous and virtual Group TPs ca be created / deleted for all NE types, which support
concatenation.
Creation of Group TPs causes deletion of the corresponding normal TPs, which are
replaced by fragment TPs. After deletion of Group TPs the normal TPs are
created/deblocked again.
In case of contiguous Group TPs some NE types do not replace the corresponding normal
TPs by fragment TPs, but they block them.
For virtual Group TPs the number of contained fragment TPs is stored in the Nx-Count
attribute of the virtual Group TP. I.e., NX-Count is not only relevant for PDH paths with
FMX, etc.
TP configuration via TNMS Core/CDM:
66
Technical background information on...
Contiguous Group TPs can be automatically created/deleted only for speciall NE types.
These Group TPs do not contain fragment TPs. The contiguous Group TPs and the normal
TPs are provided simultaneously on the GUI. A Group TP used in a cross connection is
automatically created within the NE and blocks the corresponding normal TPs and vice
versa.
a) Transport Layer for Group TPs:

Depending on
- the number X of fragment TPs
- the fragment layer N of the fragment TPs and
- the concatenation type
there are the following transport layers:
1. Contiguous concatenation: VCN-Xc (for N = 4, X = 4, 16, 64)
2. Virtual concatenation: VCN-Xv VC4-Xv (for X=2…8, 16,64)

VC3-2v
VC12-Xv (for X=2…21)
In addition, TP objects with VCN-Xv (N = 4, X = 2, 3, 5, 6, 8) may appear on TNMS

Core/CDM GUI, but they cannot be used for traffic connections.
b) Connectio ns / Paths:
Contiguous concatenated paths:
There are only VCN-Xc Group TPs used within the path. The path transport layer is
"VCN-Xc". Path management of contiguous concatenated paths is the same as for other
paths.
Virtual concatenated paths – Virtual Group paths:

There are only VCN-Xv Group TPs used within the path. The path transport layer is VG
(VCN-Xv), where VG stands for Virtual Concatenation Group. The path properties show
furthermore the fragment transport layer according to the involved fragment TPs and the
Nx-Count according to the Number X of involved fragment TPs within each Group TP.
Contiguous and virtual concatenated paths:

Contiguous and virtual concatenated paths are treated by a client/server relation between
VG as server layer and contiguous concatenated layer as client layer, that means virtual
concatenated paths are server paths/server trails for contiguous concatenated paths.
Note:
The transition between contiguous concatenation and virtual concatenation within one path
needs a conversion between both concatenation types. This required conversion capability
is only supported by special NE types.
Concatenated paths with NEs in between, which do not support concatenation:

VCN-Xv Group TPs and normal TPs are existing within neighboring NEs. There have to be
created X fragment paths between the fragment TPs of virtual Group TPs over the normal
TPs.
67
For fragment paths there were introduced new Connection Classes according to the
following 3 possible configurations:
Fragment LC/TC (Link or Tandem Connection):

- Configuration 1: the path edge connects two fragment TPs
It is used if two virtual Group TPs can not be directly connected by a Group Link
Connection.
- Configuration 2: the path edge connects a fragment TP with a normal TP (BCM =
Entry)
(similar to configuration 3)
Fragment Open SNC (Subnetwork Connection):
- Configuration 3: the path edge connects a fragment TP with a normal TP (BCM =
Exit)
It is used if only one virtual Group TP is endpoint of a virtual group path, but this
virtual Group TP is not located at the border of the management domain.
Fragment paths are server paths/server trails for virtual concatenated paths. Within a
virtual concatenated path there is one server path reference for each fragment path. The
server path references are denoted Fragment Path Reference in case of configuration 1
and Half Open Fragment Path Reference in case 2 and 3.
Notes:
- Creation of a fragment path between fragment TPs contained in Group TPs
(Configuration 1) always implies the creation of a virtual group path, if not yet
existing.
- Creation of a fragment path between a fragment TP contained in a Group TP and a
normal TP (Configuration 2 and 3) does not imply the creation of a virtual group
path.
c) Routin g of Fragment Paths:

Routing of a fragment path bundle (consisting of X fragment paths) according configuration
1 is possible via the hybrid routing function provided by theConnection A ssist ant. Right
clicking on navigation button/shift button offers a context menu with menu itemPrepare
hybrid routing …. To let the auto-router find the same way through the network for all
fragment paths the routing option Use Same Trail (Path Wizard -> Toolb ar butt on
Options -> Tab 'Aut omatic Routing Options' or TNMS Client -> Config uration ->
Preferences and Routing Options -> Tab 'Aut omatic Routing Options' ).
d) Effects of Paths Operatio n on Group Paths and Fragment Paths:

These are operations on a group path that automatically cause the same operation on the
used fragment paths:
• Activate
• Deactivate (this is reasonable, because a fragment path may be used by one group
path only)
• Manage
• Unmanage
These are operations on a group path that do not automatically cause the same operation
on the used fragment paths:
• Adopt Actual Route
68
• Adopt Actual Topology

• Re-Route
69
Floating TPs
This topic contains general information on the floating TPs introduced since TNMS
Core/CDM V8.5.
A Floating TP is a higher order TP (contained in an internal interface of Ethernet Tributary
Cards, RPR Switch Cards and Lower Order Switching Fabric of hiT 7070 and hiT 7050)
that can be cross connected and has connectable child TPs at the same time.
If a floating TP has the Termination Mode Terminated, it must be used with BCM = Entry,
when creating paths using it!
The behavior of the Automatic Router in conjunction with Floating TPs depends on the
actual network situation. If for example, a VC12 path is to be routed through a hiT 7070,
there are obviously two possibilities to do this (see picture and description under a. and b.):
a. Create just a VC4 connection:

Waste of bandwidth; capacity on precious NE resources – the LO SF – is saved.
b. Terminate the VC4 trails bearing th e VC12 and c reate a LO connect ion:
A limited resource – the LO SF – is consumed; bandwidth is saved.
Note that depending on the actual requirements in relation with the current network
situation, there may be cases where saving bandwidth is more precious than the usage of
the LO SF and vice versa.
See also :
Floating TPs: Behaviour of the Connection Assistant
70
Floating TPs: B ehaviour of t he Connection Assistant

This topic contains general information on the behaviour of the Connection Assistant
concerning the floating TPs introduced since TNMS Core/CDM V8.5.
The Connection Assistant provides a particular Shift mechanism in case of floating TPs.
Example:
Connection from PDH Tributary to SDH Line, i.e. two separate LO and HO CCs are be
created in hiT707:
First the LO CC PDH Tributary – SF2G5 VC12 is defined, the Shift button is used to enter
the next page of the Connection A ssist ant, where the parent TP is automatically pre-
selected and allows the creation of HO CC SF2G5 VC4 – SDH Line. Unless there is
already a VC4 server trail, it is implicitly created when the first LO-CC is created. Sincethe
Connection Assistant is aware of server paths, it would directly guide the operator to the
exit of a closed server path, whenever an LO path is routed over an already existing VC4.
See also:
Floating TPs
71
Layer Restrictions at Optical Protection

The creation of link connections between network elements with OCP cards on the one
hand and PM cards on the other hand has to be done carefully; i.e. the Layer Set must be
selected carefully. The Layer Set must be chosen in theCreate Port Connecti on window.
The following network elements are concerned:
• FSP 3000, Waveline MN: (equipped with PM card)

• OCUs: (equipped with OCP cards)
For link connections with these network elements terminating at OCP/PM cards, the
operator must restrict the layer of the port connections. The following rules should be
applied for creating link connections between such network elements:
• Port connections terminating at the same OCP/PM card must be restricted to the
same layer.
• No paths must pass the port connection when changing the layer restriction. This
applies to managed and unmanaged paths.
• If the other network element is a SDH NE, no adjustments have to be made (you
can check using the tool tip for the other network element). However, it would be
possible to restrict the terminated layer set of port connections in this case in order
to reduce the number of server paths.
• If the other network element is not a SDH NE, restrict the layer toOCH.
• Restrict the layer set to OPTICAL, if you have no other choice. This is the case for
network elements like WLs, MTS, hiT7550.
See also :
Creating a port connection
Editing/deleting port connections
72
Scalable Ethernet Paths & Generic Framing Procedure

This topic contains general information about Scalable Ethernet Paths andGeneric
Framing Procedure (GFP).
GFP provides a standard mapping / framing technique for Layer 1 / 2 signals into SDH /
OTN / SONET. The bandwidth of paths using GFP can be defined in TNMS Core/CDM
during path creation: The bandwidth of a path edge appears as an additional parameter of
in the window Path Properties – Topology. It is available for both directions A -> Z and A
<- Z and it is scalable in steps of 1 Mbps.
Scalable Ethernet paths are handled in TNMS Core/CDM in analogy to paths on any other
transmission layers. New layers are introduced for GFP Channel (GFPC) and GFP Group
(GFPG). Automatic and Manual Routing can be applied as usual for the creation of GFPC
and GFPG trails as well as for the creation of ethernet paths using these trails.
Notes:
- The Automatic Router will create automatically suitable SDH trails depending on the
bandwidth defined for the client path. This includes Virtual Concatenation Group
paths without fragment paths. Fragment bundle paths within a Virtual Concatenation
Group can be routed manually as usual. In case of automatic routing, the bundle
(but not necessarily every single fragment) has to be routed separately in advance,
i.e. before it can be used for further automatic routing operations: Define GTPs as
start- and endpoint for the Automatic Router and set BCM =Entry. Also bundle
routing between one GTP and a number of not concatenated end TPs is supported.
- While creating the path manually, the TP object GFP-Group-TTP (BCM = Entry) has
to be connected with a GFP-Group-CTP which appears as child of its assigned SDH
TP, e.g. VC4-TTP. The SDH TP does not occur within the route of the GFPG trail,
but it serves as start- / end-point of its SDH server trail. Only GFP-TPs belonging to
the same card can be connected directly.
- Assignments of GFP-groups to VC-groups interrupt the traffic < 50ms if there is

already traffic switched via the ethernet card where the assignment is configured.
No message will appear to inform the operator.
- In order to avoid traffic interruption it is recommended that the complete SDH-

structure on one ethernet card as well as all assignments to GFP-groups have to be
configured with the LCT. This must be done before the first service is activated via a
ethernet card.
Definiti on of required bandwidth for a path during path creation or modi fication:
• The bandwidth can be defined for each topology template (use the bandwidth
definition box) as well as for each edge and direction separately (set separate
values in list of path edges per direction) in the Path Wizard – Define Topolog y
window resp. in the Path Properties – Topology window. During the activation of a
path for which the bandwidth is defined, TNMS Core/CDM overwrites existing
configurations in the network. In analogy if Activate is performed in the meaning of
re-activate, all attributes are set in the network as defined in TNMS Core/CDM.
• If no particular bandwidth is to be defined for a path, this is expressed by means of a
bandwidth value of "0". TNMS Core/CDM automatically takes over the bandwidth
configured in the network, e.g. if bandwidth has already been set before with EM.
The value "0" does not explicitly mean that the path is deactivated or similar.
It is possible, to modify the path bandwidth after path creation (in dependence on the
capacity available in the server trail) in EM or in Path Properties – Topology window. In
order to do so, use either the bandwidth definition box inPath Properties – Routing
window in order to set the new bandwidth for both directions A -> Z and A <- Z of the
edge(s) or define as well as for each edge and direction separately (set new values in list
73
of path edges) in Path Wizard – Define Topolog y window resp. in Path Prop erties –
Topology window. If the bandwidth is to be enlarged, the Capacity Management in TNMS
Core/CDM checks, if enough capacity is available in the server trail used by this ethernet
path. If the bandwidth is to be reduced, the capacity is reduced in the NE without further
checks.
Note:
Server trails are not modified automatically, in case the bandwidth of a scalable ethernet
path is enlarged and the bandwidth left in an SDH-server trail is less than the additional
bandwidth needed or vice versa. In this case, the server trail has to be modified or deleted
and a new server trail with an appropriate bandwidth has to be re-created manually. This
may require an adaptation of GFPG trails as well by means of the functionAdopt Actual
Topology.
Similar to path creation states, mismatches between required (as defined for the path in
TNMS Core/CDM) and actual bandwidth (according to the actual configuration of the
specific port) will be detected automatically and lead to a path creation state change. The
reason is given in Info Area of the Path Properties. In order to re-align the Path Properties
in TNMS Core/CDM with the actual network situation, it is possible either to set the values
defined in TNMS Core/CDM within the network again (by means of an additional Activate
for the corresponding path) or to adopt the changes within the network into the TNMS
Core/CDM database. Since the bandwidth attribute belongs to the path topology, the
function Adopt Actual Topology has to be applied in this case.
GFP Groups provide a sub-channeling, which allows a multiplexing of ethernet signals

from more than one ethernet port (per card) in order to transport them using a single VC.
Sub-channeling can be switched OFF and ON using the LCT. The Automatic Router tries
to create paths using sub-channeling (if available, i.e. if supported by involved cards). By
means of Manual Routing, the operator can explicitly decide whether or not to use sub-
channeling simply by choosing different TPs.
Note:
Without sub-channeling, the bandwidth of the GFPG trail equals the bandwidth of the
corresponding SDH trail. When using sub-channeling, due to an additional internal
overhead, the SDH trail bandwidth is not completely available for etherent traffic. Only 64 /
76 of the SDH bandwidth is available in worst case, see examples below. Note, that the
Sum of all Committed Interface Rate is not explicitly indicated in TNMS Core/CDM, e.g. a
GFPG path with sub-channelling using a VC4 shows a bandwidth of 150 Mbps in its path
properties, although it provides only a reduced capacity of 126 Mbps for all its client paths.
However, capacity checks in TNMS Core/CDM regard the Sum of all Committed Interface
Rate, i.e. it is checked that the bandwidth of all GFPC paths using the VC4 with sub
channelling does not exceed 126 Mbps in this exemplary case. Otherwise, the ACS of
these paths would fall to Not active because of overbooking.
Physical Network Rate of Sum of all Committed Interface Rate

Interface Rate Service (as us ed in when us ing Sub-Channelling
TNMS Core/CDM)
100Mb/s VC3: 49 Mbps 41 Mbps = 49 Mbps x 64 / 76
VC3-2v: 98 Mbps 82 Mbps = 98 Mbps x 64 / 76
VC4: 150 Mbps 126 Mbps = 150 Mbps x 64 / 76

1000Mb/s VC4: 150 Mbps 126 Mbps = 150 Mbps x 64 / 76
74
Restrictions:
• All virtually concatenated GTPs to be used for ETH paths must be created explicitly
with EM before
• SNCP for GFP Channel or Group Trails is not supported.
• TNMS Core/CDM supports symmetric configurations of the sub-channeling mode
only. However, traffic is transmitted by the NEs even if the configuration is
asymmetric provided that only one ETH port is connected with a GFP Group with
sub-channeling ON.
• If the channel index is changed in the NE with EM, at first the assignment ETH –
GFP Group is deleted and a new assignment to the new GFP Sub-Channel with the
new index is created. Note: The GFP Sub-Channel TPs, which have been available
before, are still available.
• There are no bandwidth checks performed by the NE, i.e. it is possible to overbook
GFP Group trails via the LCT.
• For GFP paths, TNMS Core/CDM does not support overbooking, although this is an
NE feature. Though an overbooking check is provided, which takes all managed
GFPC paths (with RCS = Active and Not active) using a GFPG trail into account.
Overbooking resulting from unmanaged paths is not checked. Overbooked GFPG
trails as well as their client GFPC paths appear in ACS = Not active. The reason for
this ACS is provided in Info Area of Path Properties after applying a "Path Check".
See also:
Connection Assistant
Floating TPs
75
Support of Loopbacks
This topic contains general information on loopback within TNMS Core/CDM, which
supports both loopbacks on TPs and on ports on the network layer:
• Loopback on TPs
By means of uni-directional CCs in switching matrix with TP A = TP B, the traffic is
looped back on the actual TP transmission level. Creation of a path loop-back is done
by changing the connection template to “Loop-back at all TPs” in theConnection
As si st ant window. It is supported for bi-directional paths only.
• Create Loopback on Ports

By means of a special switch on the port of tributary or line interface cards (Ethernet,
PDH, SDH) the traffic is looped back, i.e. the traffic received by this port is sent back
directly to its origin.
Loopback on ports is supported by the following network elements hiT 7070, hiT 7050,
SMA16 (not for all cards), FSP150 (only on network FSP150 LE ports), FSP1500
(supports inward and outward loopbacks in both remote and local interfaces) and
FSP3000 R7.
The window List of Ports allows configuring port loopbacks via context menu. See
description in the Port List window (link is given below).
If a path is running via a port for which a loopback is configured (it does not matter
whether this was done locally using an LCT or using the windowList of Ports), the ACS
is set to Under Test. This holds for paths with ACS, RCS = Active.
For a path with ACS < Active, RCS = Active its ACS is indicated as usual according to
its priority (which is higher than Under Test). Therefore for a path in ACS = Not Active, a
port loopback for one of the participating ports is not indicated by means of the ACS).
Within the Path Properties itself, the Path Check function provides information, which
ports are affected by port loopbacks.
Note: More information on the combinations of the creation states ACS and RCS is
given in icons. Services, subscribers and paths
• Create Lo opback on Ports usi ng LCT of Surpass hiT7020/25/30/35/60/60HC when
direct integration is us ed
When changing the loopback configurations using the LCT of Surpass
hiT7020/25/30/35/60/60HC, you have to resynchronize the NE in TNMS Core/CDM
(when direct integration is being used).
To resynchronize the NE in TNMS Core/CDM do the following:
1. In the Network Plan of TNMS Core/CDM client change toNetwork Editor mode.
2. Open the context menu of the NE and selectResynchro nize Data… option.
• Remove Loopback on Ports
Create Loopback on Ports
Note: When applying the command End Test, both TP loopbacks and port loopbacks (if
existing) are removed. When deleting a path affected by a loopback (it does not matter
whether uni- or bi-directional, and whether affected by TP loopback or port loopback), the
operator is asked in a message box whether or not the probably existing port loopbacks
shall be removed too.
Restrictions:
- Port loopbacks are not considered by all routing operations on paths.
- Port loopbacks are not indicated in context of Port Connection lines in the windows
Network Plan, Port Connection Properties, List of Port Connections, Create
Port Connection, Path Wizard, Connection Ass istant.
See also:
76
Listing ports
77
Technologies and Transport Layers

This topic contains information about the kinds of technologies and their transport layers
within TNMS Core/CDM:
List of Technologies
Technology Descript ion Transport Layers
Data GFPG, GFPC, ESCON, FICON, FC
Ethernet Ethernet 10GbE, 1000Basef, RPR, 1000Base, 100Base

OTH Optical Transport OTU3, ODU3, OTU2, ODU2, OTU1, ODU1
Hierarchy
PDH Plesiochronous P4, P32, P31, P22, P21, P12, P11, P0
Digital Hierarchy
SDH Synchronous RS256, MS256, RS64, MS64, RS16, MS16, VC4-
Digital Hierarchy 16f, RS4, MS4, RS1, MS1, VC4, RS0, MS0, VC3,
VC2, VC12, VC11, VG, VC4-64c, VC4-16c, VC4-4c
unspecified unspecified GENP, ELECTRICAL, MEDIALESS, OPTICAL,
GENC
WDM Wavelength OTS, OMS, OCH
Division
Multiplexing
List o f Transport L ayers

Layer Technology Descriptio Band Server Layers Client Layers
Name n width (Multiplicity) (Multiplicity)
(Mbps
)
OTS WDM Optical OMS(1)
Transmissi
on Section
GENP unspecified Generic GENC(1)
Physical
Interface
ELECTRIC unspecified Generic 1000Base(1), 1000Basef(1),
AL Electrical 100Base(1), 10GbE(1),
Interface ESCON(1), FC(1),
FICON(1), MS0(1), MS1(1),
MS16(1), MS256(1), MS4(1),
MS64(1), ODU1(1),
ODU2(1), ODU3(1),
OTU1(1), OTU2(1),
OTU3(1), P0(1), P11(1),
P12(1), P21(1), P22(1),
P31(1), P32(1), P4(1),
RS0(1), RS1(1), RS16(1),
RS256(1), RS4(1), RS64(1),
VC11(1), VC12(1), VC2(1),
VC3(1), VC4(1), VC4-16c(1),
VC4-4c(1), VC4-64c(1)
MEDIALES unspecified Generic 1000Base(1), 1000Basef(1),
S Medialess 100Base(1), 10GbE(1),
(e.g. radio) FICON(1), MS0(1), MS1(1),
78
MS16(1), MS256(1), MS4(1),

MS64(1), ODU1(1),
ODU2(1), ODU3(1),
OTU1(1), OTU2(1),
OTU3(1), P0(1), P11(1),
P12(1), P21(1), P22(1),
P31(1), P32(1), P4(1),
RS0(1), RS1(1), RS16(1),
RS256(1), RS4(1), RS64(1),
VC11(1), VC12(1), VC2(1),
VC3(1), VC4(1), VC4-16c(1),
VC4-4c(1), VC4-64c(1)
OPTICAL unspecified Generic 1000Base(1), 1000Basef(1),
Optical 100Base(1), 10GbE(1),
FICON(1), MS0(1), MS1(1),
MS16(1), MS256(1), MS4(1),
MS64(1), OCH(1), ODU1(1),
ODU2(1), ODU3(1),
OTU1(1), OTU2(1),
OTU3(1), P0(1), P11(1),
P12(1), P21(1), P22(1),
P31(1), P32(1), P4(1),
RS0(1), RS1(1), RS16(1),
RS256(1), RS4(1), RS64(1),
VC11(1), VC12(1), VC2(1),
VC3(1), VC4(1), VC4-16c(1),
VC4-4c(1), VC4-64c(1)
OMS WDM Optical OTS(1) OCH()
Multiplex
Section
OCH WDM Optical OMS(), 1000Base(1), 1000Basef(1),
Channel OPTICAL(1) 100Base(1), 10GbE(1),
ESCON(1), FC(1),
FICON(1), GENC(1),
MS0(1), MS1(1), MS16(1),
MS256(1), MS4(1), MS64(1),
ODU1(1), ODU2(1),
ODU3(1), OTU1(1),
OTU2(1), OTU3(1), P0(1),
P11(1), P12(1), P21(1),
P22(1), P31(1), P32(1),
P4(1), RS0(1), RS1(1),
RS16(1), RS256(1), RS4(1),
RS64(1), VC11(1), VC12(1),
VC2(1), VC3(1), VC4(1),
VC4-16c(1), VC4-4c(1),
VC4-64c(1)
OTU3 OTH Optical 43000 ELECTRICAL( ODU3(1)
Transport 1),
Unit 3 MEDIALESS(1
), OCH(1),
OPTICAL(1)
ODU3 OTH Optical 43000 ELECTRICAL( ODU1(16), ODU2(4),
Digital Unit 1), RS256(1)
3 MEDIALESS(1
), OCH(1),
OPTICAL(1),
79
OTU3(1)
RS256 SDH Regenerat 40000 ELECTRICAL( MS256(1)
or Section 1),
STM-256 MEDIALESS(1
), OCH(1),
ODU3(1),
OPTICAL(1)
MS256 SDH Multiplex 40000 ELECTRICAL( RS64(4), VC3(768),
Section 1), VC4(256), VC4-16c(16),
STM-256 MEDIALESS(1 VC4-16f(16), VC4-4c(64),
), OCH(1), VC4-64c(4)
OPTICAL(1),
RS256(1)
OTU2 OTH Optical 10700 ELECTRICAL( ODU2(1)
Transport 1),
Unit 2 MEDIALESS(1
), OCH(1),
OPTICAL(1)
ODU2 OTH Optical 10700 ELECTRICAL( GENC(1), ODU1(4), RS64(1)
Digital Unit 1),
2 MEDIALESS(1
), OCH(1),
ODU3(4),
OPTICAL(1),
OTU2(1)
or Section 1),
STM-64 MEDIALESS(1
), MS256(4),
OCH(1),
ODU2(1),
OPTICAL(1)
MS64 SDH Multiplex 10000 ELECTRICAL( RS16(4), VC3(192),
Section 1), VC4(64), VC4-16c(4), VC4-
STM-64 MEDIALESS(1 16f(4), VC4-4c(16), VC4-
), OCH(1), 64c(1)
OPTICAL(1),
RS64(1)
10GbE Ethernet 10 Gigabit 10000 ELECTRICAL( GENC(1)
Ethernet 1),
Signal (full MEDIALESS(1
capacity) ), OCH(1),
OPTICAL(1)
OTU1 OTH Optical ELECTRICAL( ODU1(1)
Transport 1),
Unit 1 MEDIALESS(1
), OCH(1),
OPTICAL(1)
ODU1 OTH Optical ELECTRICAL( 1000Base(1), 1000Basef(1),
Digital Unit 1), 100Base(1), ESCON(1),
1 MEDIALESS(1 FC(1), FICON(1), P4(1),
), OCH(1), RS0(1), RS1(1), RS16(1),
ODU2(4), RS4(1)
ODU3(16),
OPTICAL(1),
OTU1(1)
80
RS16 SDH Regenerat 2500 ELECTRICAL( 1000Base(32),

or Section 1), 1000Basef(32),
STM-16 MEDIALESS(1 100Base(32), ESCON(32),
), MS64(4), FC(32), FICON(32),
OCH(1), MS16(1), RS1(16), RS4(4)
ODU1(1),
OPTICAL(1)
MS16 SDH Multiplex 2500 ELECTRICAL( GENC(1), VC3(48), VC4(16),
Section 1), VC4-16c(1), VC4-16f(1),
STM-16 MEDIALESS(1 VC4-4c(4)
), OCH(1),
OPTICAL(1),
RS16(1)
VC4-16f SDH VC4-16c 2400 MS16(1), 1000Base(32),
contiguous MS256(16), 1000Basef(32), FC(32),
concatenat MS64(4) FICON(32), RS4(32)
ion path
(FSP)
1000Basef Ethernet Gigabit 1000 ELECTRICAL( 100Base(32), ESCON(32),
Ethernet 1), GENC(1), RS1(32)
Signal MEDIALESS(1
(FSP) ), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(32),
VC4-16f(32)
or Section 1),
STM-4 MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(4), VC4-
16f(32)
MS4 SDH Multiplex 622 ELECTRICAL( VC3(12), VC4(4), VC4-4c(1)
Section 1),
STM-4 MEDIALESS(1
), OCH(1),
OPTICAL(1),
RS4(1)
RS1 SDH Regenerat 155 1000Basef(32) MS1(1)
or Section ,
STM-1 ELECTRICAL(
1),
MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(16)
MS1 SDH Multiplex 155 ELECTRICAL( VC3(3), VC4(1)
Section 1),
STM-1 MEDIALESS(1
), OCH(1),
OPTICAL(1),
RS1(1)
VC4 SDH VC4 150 ELECTRICAL( 1000Base(1), 100Base(1),
81
higher 1), GFPG(1), P4(1), RPR(1),

order path MEDIALESS(1 VC11(84), VC12(63),
), MS1(1), VC2(21), VC3(3), VG(0)
MS16(16),
MS256(256),
MS4(4),
MS64(64),
OCH(1),
OPTICAL(1)
or Section 1),
STM-0 MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1)
MS0 SDH Multiplex 52 ELECTRICAL( VC3(1)
Section 1),
STM-0 MEDIALESS(1
), OCH(1),
OPTICAL(1),
RS0(1)
VC3 SDH VC3 49 ELECTRICAL( 100Base(1), GFPG(1),
higher/low 1), P31(1), P32(1), VC11(28),
er order MEDIALESS(1 VC12(21), VC2(7), VG(0)
path ), MS0(1),
MS1(3),
MS16(48),
MS256(768),
MS4(12),
MS64(192),
OCH(1),
OPTICAL(1),
VC4(3)
VC2 SDH VC2 lower 7 ELECTRICAL(
order path 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
VC3(7),
VC4(21)
VC12 SDH VC12 2 ELECTRICAL( 100Base(1), P11(1), P12(1)
lower 1),
order path MEDIALESS(1
), OCH(1),
OPTICAL(1),
VC3(21),
VC4(63)
VC11 SDH VC11 1.5 ELECTRICAL( P11(1)
lower 1),
order path MEDIALESS(1
), OCH(1),
OPTICAL(1),
VC3(28),
VC4(84)
VG SDH Virtual VC3(0), GFPG(1), VC4-16c(1), VC4-
Concatena VC4(0) 4c(1), VC4-64c(1)
tion Group
82
VC4-64c SDH VC4-64c 9600 ELECTRICAL(

contiguous 1),
concatenat MEDIALESS(1
ion path ), MS256(4),
MS64(1),
OCH(1),
OPTICAL(1),
VG(1)
VC4-16c SDH VC4-16c 2400 ELECTRICAL(
contiguous 1),
MS256(16),
MS64(4),
OCH(1),
OPTICAL(1),
VG(1)
VC4-4c SDH VC4-4c 600 ELECTRICAL( 1000Base(1), RPR(1)
contiguous 1),
MS256(64),
MS4(1),
MS64(16),
OCH(1),
OPTICAL(1),
VG(1)
GFPG Data Generic VC3(1), GFPC(256)
Framing VC4(1), VG(1)
Procedure
(GFP)
Group
GFPC Data Generic GFPG(256) 1000Base(1), 100Base(1),
Framing RPR(1)
Procedure
(GFP)
Channel
P4 PDH path layer 140 ELECTRICAL( P31(4)
140Mbps 1),
MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
VC4(1)
P32 PDH path layer 45 ELECTRICAL( 100Base(1), P21(4)
45Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
VC3(1)
34Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P4(4), VC3(1)
83

8Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P31(4)
6Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P32(4)
2Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P22(4),
VC12(1)
P11 PDH path layer 1.5 ELECTRICAL( P0(24)
1,5Mbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P21(4),
VC11(1),
VC12(1)
P0 PDH path layer 0.064 ELECTRICAL(
64Kbps 1),
MEDIALESS(1
), OCH(1),
OPTICAL(1),
P11(24),
P12(31)
RPR Ethernet Resilient GFPC(1),
Packet VC4(1), VC4-
Ring 4c(1)
1000Base Ethernet Gigabit 1000 ELECTRICAL( GENC(1)
Ethernet 1), GFPC(1),
Signal MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(32),
VC4(1), VC4-
16f(32), VC4-
4c(1)
100Base Ethernet (Fast) 100 1000Basef(32) GENC(1)
Ethernet ,
Signal ELECTRICAL(
1), GFPC(1),
MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
P12(1),
84
P31(1),
P32(1),
RS16(32),
VC12(1),
VC3(1),
VC4(1)
ESCON Data IBM 200 1000Basef(32) GENC(1)
protocol ,
for ELECTRICAL(
mainframe 1),
s 200Mbps MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(32)
FICON Data IBM 1062.5 ELECTRICAL( GENC(1)
protocol 1),
for MEDIALESS(1
mainframe ), OCH(1),
s ODU1(1),
1062Mbps OPTICAL(1),
RS16(32),
VC4-16f(32)
FC Data Fiber 1062.5 ELECTRICAL( GENC(1)
Channel 1),
MEDIALESS(1
), OCH(1),
ODU1(1),
OPTICAL(1),
RS16(32),
VC4-16f(32)
GENC Unspecified Generic 1000Base(1),
Client 1000Basef(1),
Layer 100Base(1),
10GbE(1),
ESCON(1),
FC(1),
FICON(1),
GENP(1),
MS16(1),
OCH(1),
ODU2(1)
85
Client functions
87
Al arm s
Ac kn ow ledgin g al arm s
There are several ways of acknowledging alarms (in addition to the examples shown below
you can also acknowledge alarms in the properties windows for port connections and
multiplex section protections).
Example 1:
1. Open the window Current Alarms in the TNMS Client via Fault -> Current Alarms....
2. Select the alarms that you wish to acknowledge (you can select multiple alarms by
holding down the Ctrl+Shift keys).
3. Acknowledge the alarms by clicking with the right mouse button in the window to
activate the Ac know ledge Selec ted Al arms context menu.
Example 2:
1. Switch to the Surveillance mode of the TNMS Client.
2. Select an NE container or a network element.
3. Acknowledge all alarms for the selected object using its Al arms -> Ac kn owledge All
context menu.
Example 3:
1. Select a service or a path in the Subscribers and Services tree of the TNMS Client.
2. Use the Properties... context menu to open the Service window.
3. Select the Al arms tab.
4. Acknowledge alarms for the selected object using the Ac kn ow ledg e Selected Al arms
context menu.
Example 4:
1. Open the window Al arm Statis ti cs from the context menus of the object whose alarms
you want to acknowledge, i.e. network element, subnetwork, DCN channel, NE
container, via Al arms -> Alarm Statis ti cs ...
2. Open the context menu of an alarm counter and select Ac kn ow ledg e all Al arms to
acknowledge all alarms represented by the counter.
Example 5:
1. Select Properties…from the Network Infrastruct ure tree.
2. Now select an object and choose the context menu with the entryAl arms ->
Ac know ledge Selec ted Al arms to acknowledge the alarms for the object.
Alarm acknowledging can be a long lasting operation, in the event of this operation lasting
a long time, a message box is displayed informing the user.
See also :
Alarm statistics
Current alarm list
Service / Path Properties: alarms
88
Client functions
Al arm co rrelatio n for a path

The operator is able to define the type of automatic alarm correlation for each path.
- The automatic alarm correlation is set in the Service / Path Properties window. In
order to open this window, select the path you want to modify in theSubscribers and
Services tree and open the context menu -> Properties…. Now you can choose
between Off , Normal or Extended alarm correlation. Alternatively, you can choose the
Manual Correlatio n.
- Alternatively you can select a path in the Subscribers and Services tree and invoke
the context menu Al arm Co rrelatio n for the path.
Notes:
- Equipment alarms shown in the alarm list are not correlated to paths, i.e. though an
equipment alarm exists in the alarm list, the icon in the Subscribers and Services
tree does not change its color accordingly.
- The following operational states for paths are possible:Enabled, Disabled, Protection
disturbed. See Operational state.
- The operational state = enabled.
- Normal: The operational state = disabled or enabled, depending on the alarm
situation.
- The operational state = enabled or disabled or protection disturbed.
TNMS Core/CDM supports the following alarm correlation methods which are indicated as
an overlay icon at the path object at the GUI:
Correlation Method Path overlay icon Descripti on

(Automatic) Alarm - Default alarm correlation, only path
Correlation: Normal endpoints (TP/ports) are considered for
the alarm correlation.
(Automatic) Alarm All TPs/ports are correlated along the
Correlation: Extended active path route.
(Automatic) Alarm Alarm correlation is switched off, no
Correlation: Off evaluation of operational state is
performed. The automatic alarm
correlation can be switched off globally or
per path.
Manual Correlation - Manual alarm correlation can be executed
independently of the automatic alarm
correlation. It is only done for a individual
path when requested by a user.
Note: Manual alarm correlation is only
static, i.e. a change of the alarm state is
only visible after an update has been
performed.
Via TNMS Client -> Fault you can select Auto matic Al arm Correlati on to switch on / off
the function globally.
The type of automatic alarm correlation can be viewed / configured in theSubscribers
and Services tree via the path context menu -> Al arm Correlati on .
The settings for automatic alarm correlation (On, Off , Extended) can also be viewed /
configured in the Servi ce / Path Prop erties window. In this window the manual alarm
89
correlation can be requested by pressing the Manual Correlatio n button. As a result of the
action the alarm severity and the operation state are displayed.
Notes:
For the automatic alarm correlation, the on/off switching is useful in the case of alarm
bursts or network wide maintenance to avoid loss of TNMS Core/CDM Server performance
due to high alarm load in connection with the alarm correlation to the affected paths. The
automatic correlation can be switched off to increase the system performance.
When using manual alarm correlation, TNMS Core/CDM analyzes the alarms of all ports,
termination points and additionally all equipment alarms of all modules of theactual traffic
route. Note that the alarms of all server paths are considered in the relevant client paths
too, independently of the operational state of the server paths.
The result of the correlation (if path-affecting alarms exist) is displayed by a overlay symbol
in the operational state of the path.
Enable the (Automatic) Alarm correlation Extended, if the layer set of a client path does not
contain an SDH layer. The alarms of server paths are not displayed in alarm list of the
corresponding client paths.
See also:
Service / Path Properties Icons_Services
90
Client functions
Al arm and pat h s tat is ti cs

In order to open the Alarm and Service Statisti cs window select Fault -> Alarm and
Path Statistic s…. The window opens with the Overview register. Two more views of this
window are available by selecting the registers Al arms St ates and Paths States at the
bottom of the window.
Overview
For the alarms this view provides an overview of all acknowledged alarms and of all not
acknowledged alarms; each of them divided into the existing alarm categories (critical,
major, minor, warning and indeterminate) and the sum of the individual and total alarms.
Tool tips are available for the bar charts. In the list below the individual alarms with their
alarm categories are listed.
For the paths this view provides the number of disabled paths, protection disturbed paths,
enabled paths and the sum of all disabled, protection disturbed and enabled paths. In the
list below the individual disabled or enabled paths are listed.
The alarm overview refresh interval of this list can be defined underTNMS SysAdmin
under "General Settings".
Al arms St ates
The alarm states list provides an overview of the existing alarm states for a network; i.e.
the number of existing:
- acknowledged/unacknowledged warnings
- acknowledged/unacknowledged minor alarms
- acknowledged/unacknowledged major alarms
- acknowledged/unacknowledged critical alarms
- acknowledged/unacknowledged indeterminate alarms
Paths States
The paths states list provides an overview of the existing paths states:
- Index
Number of the row in the list
- Subscriber
Name of the subscriber
- Network
Name of TNMS Server controlling the network
- Operatio nal State
Shows the operational state of all paths belonging to the subscriber, eitherenabled,
disabled or protection disturbed.
- Enabled/Protection Disturbed/Disabled paths
Shows the number of enabled, protection disturbed and disabled paths for this
subscriber.
- Disabled paths / last change
Shows the date and time when the last path belonging to this subscriber changed its
Operational state to disabled.
See also :
Setting filters and sorting lists
91
Al arm log
The Al arm Log window displays a history of the alarm events which have occurred in the
supervised network. Every alarm can appear only once in the alarm log with three different
timestamps:
If an alarm was raised, a new alarm with a timestamp (raised) appears in the alarm log
(mandatory).
If an alarm was cleared, the timestamp is updated with cleared (may be empty).
If an alarm was acknowledged, the acknowledge time will be given (may be empty).
Note:
As the alarm log is a static log, it will not update automatically. To refresh this log, press
the F5 key.
You can display the alarm log either via TNMS Client -> Fault -> Alarm Log..., or via
TNMS Client -> View -> Tables… and clicking Acti ve Alarm Log . Furthermore you can
open the alarm log via the context menu of several items in the network view. In the latter
case the alarm log is filtered for these items.
For each alarm displayed, the maximum information to be displayed is as follows:
- Index
- Color icon
To the left of the alarm message there is a LED icon for which the color iconizes the
severity of the alarm. The severity colors are configurable inTNMS SysAdmin. More
information is provided in the SysAdmin online help. More information is provided
under Icons: Services, subscribers and paths.
- Time (Local)
Indicates the time at which the alarm message arrived (entry displayed either as
Greenwich Mean Time or local time). If the alarm message does not include time
stamp information, the time stamp will be generated by the TNMS Server. In this case
the time value is marked with an asterisk (*). The < sign indicates that the TNMS
Server has given the time stamp for an alarm and the raise time of that alarm cannot
be exactly evaluated, but for sure the alarm was raised before the displayed time (e.g.
provisioning of a NE in TNMS with current alarms).
- Object Name
Name of the object (e.g. a NE) from which the alarm is sent.
- Object Type
Identifies the type of the alarming object inside the NE.
- Location
Specifies the identity of the alarming object inside the network element with up to four
dot-separated numbers in the following format (only if all four numbers are displayed):
<Shelf-Nr>-<Slot-Nr>.<Port-Nr>.<TP-Id>
Note that not always all four numbers are displayed.
- Cause
Apparent reason for the alarm message.
- Severity
Alarm level in accordance with the five severities warning, minor, major, critical or
indeterminate.
- Al arm Class
Further entry for classifying the alarm.
Communication: Communication problem, e.g. error in data transmission.
Quality: Performance problem: e.g. transmission quality.
Processing: Processing problem: e.g. timeout exceeded.
92
Client functions
Equipment: Problems with technical equipment: e.g. internal clock not synchronized,
hardware error in interface module.
Environment: customer-specific error in the environment: e.g. operating room door
open, fire alarm.
- Cleared Tim e (Local)
Shows the time when the alarm was cleared.
- Parent Node
Indicates the name of the parent node (e.g. MSN) which contains the NE.
- Ac know ledged b y
Identification of the operator who acknowledged the alarm message.
- Computer
Computer where the operator mentioned above has logged in.
- Ac know ledge Tim e (Loc al)
Time when the operator acknowledged the alarm message.
- Addi ti onal Info
Additional information added by the operator to the specific alarm message. The
additional information is added through the current alarm lis t window.
By right-clicking in the list, you can activate a context menu in order to filter the list.
descending order.
More information on filter and sort functions is provided inSetting filters and sorting lists
and Icons: Lists.
93
Al arm severiti es and alarm st ates

At various places/windows in the TNMS Client LED icons are provided which are color-
coded to show the highest alarm severity within the object in question or the status of
current alarms.
This color coding is also used for displaying alarms in the Current Al arm List and the
Al arm Log.
Al arm severiti es in order of decreasing seriousness. According to the ITU standards, the
default colors for alarms are as follows:
Cleared = green
Warning = blue
Minor = yellow
Major = orange
Critical = red
Indeterminate = white
Display of Alarm Severity at the Graphical User Interface

- An LED in the status bar of the TNMS Client shows the currently highest severity
for all reachable NEs.
- An LED in the information bar of an NE container and an NE shows the highest
severity of the object and all contained objects. The same information is shown by
the state icon of a NE container and an NE in the Network Elements tree and in the
DCN Component s tree (depending on the network view, i.e. Surveillance or
Network Editor ).
- An LED as state icon of a port connection in the Port connection window or in the
Service / Path Properties window shows the highest severity of all port-related
alarms for a port connection.
- An LED is shown in the Current alarm window and in the Al arm log for every alarm
entry.
- The current alarm entries can be filtered and sorted with a pull down menu for
current cells.
Existing Al arm states

- No alarm
- Acknowledged
- Unacknowledged
The color codes for the different alarm severities and alarm statuses are configurable.
More information is provided in the SysAdmin online help.
94
Client functions
Al arm st ati st ic s
From various context menus (network element, DCN channel, NE container, NetServer, all
NetServers, all NE Containers) you can use Alarms -> Al arm Statistics... to open the
window Alarm statistics (Surveillance/Services mode).
The left area of the window displays an icon for the selected network object.
The right area of the window under Statisti cs shows the alarm statistics for the selected
network object. A summary of both acknowledged (=Ack) and unacknowledged (=Unack)
alarms for each alarm severity (indeterminate, warning, minor, major, critical), the summary
of alarms for each alarm severity and the total of acknowledged, unacknowledged alarms
and the total of both.
The bottom line shows a summary of all acknowledged alarms, unacknowledged alarms
and the total for both categories. The alarm severity is not taken into account here.
You can set the following options:

- Statistic s follow Mouse: If you leave the Alarm statistics window open and click on
another NE or NE container on the Network Plan, the Alarm statistics window will
display the alarm statistics of the object currently selected.
- Flash on Change: If a change in the alarm statistics occurs, the appropriate field
blinks. You can also set how long the flashing should last using a predefined list.
Possible values range from 1 second to 20 minutes, and also continually.
The context menu of the counters offers the following entries:

- Ac know ledge all Al arms: acknowledges the unacknowledged alarms for the selected
counter.
- Current Alarms…: displays an alarm list for the selected network element/NE
container and applies a filter according to the counter (e.g. unacknowledged major
alarms).
- Disable Flashing: stops the counter blinking.
The alarm statistics correspond to the Current alarm list with a filter for the network
element, DCN channel or a NE container in question.
Note:
If an operator suspects that there are inconsistencies in the alarm statistics (or alarm list)
after switching to the standby system, it is sufficient to activate the Reinitialize Alarms
function.
95
Al arm su ppressi on fo r a path

The alarm level is used in order to distinguish between:
- Primary alarm: This alarm is assumed to be directly related to the primary cause of
the problem. The problem is detected by the alarming entity itself.
- Secondary alarm: This alarm is generated as a consequence of primary alarms. The
primary cause lies in an object other than the alarming entity of this alarm and in most
cases lies outside of the reporting network element.
Via the context menu of a path the TNMS Client Subscibers and Services tree offers the
following types of alarm suppression for a path:
- Al arm mask -> Enable Primary alarms: For all termination points of the path, primary
alarms for the traffic direction of the path are enabled and secondary alarms are
disabled.
Example: LOS, LOP.
- Al arm mask -> Enable Secondary alarms at endpoints : For all termination points of
the path, primary alarms for the traffic direction of the service are enabled. For all
endpoints of the path secondary alarms for the traffic direction of the path are also
enabled. If the endpoint is a CTP, the secondary alarms of the next cross connected
termination points are also enabled.
Example: AIS, RDI.
- Al arm mask -> Disable all alarms: For all termination points of the traffic direction of
the path and of the same transmission layer as the path all alarms (not: port alarms
and equipment alarms) are disabled. You might use this in order to prevent alarms
before locking or reconfiguring a path.
Line port alarms (as opposed to tributary port alarms) are not treated by the path alarm
mask mechanism, since this could affect other clients’ paths.
96
Client functions
Current alarm list

The Current Al arms window displays all currently raised alarms. If invoked as described
below, the current alarm list is global (global, because it may show alarms of more than
one object), in contrast to the NE or subnetwork specific alarm list for example which only
shows alarms for a specific NE or subnetwork.
You can display a current alarm list via TNMS Client -> Fault -> Current Alarms...
Note:
If an operator suspects after switching to the standby system that there are inconsistencies
in the current alarm list (or alarm statistics), it is sufficient to perform aReinitialize Alarms.
For each alarm displayed, the maximum information to be displayed is as follows:

- Index
- Color icon
On the left side of the alarm message there is a LED icon for which the color iconizes
the severity of the alarm.
- Time (Local)
Indicates the time at which the alarm message arrived (entry displayed either as
Greenwich Mean Time or local time). If the alarm message does not include time
stamp information, the time stamp will be generated by the TNMS Server. In this case
the time value is marked with an asterisk (*). The < sign indicates that the TNMS
Server has given the time stamp for an alarm and the raise time of that alarm cannot
be exactly evaluated, but for sure the alarm was raised before the displayed time (e.g.
provisioning of a NE in TNMS with current alarms).
- Object Name
Name of the object (e.g. a NE) from which the alarm is sent.
- Object Type
Identifies the type of the alarming object inside the NE.
- Location
Specifies the identity of the alarming object inside the network element with up to four
dot-separated numbers in the following format (only if all four numbers are displayed):
<Shelf-Nr>-<Slot-Nr>.<Port-Nr>.<TP-Id>
Note that not always all four numbers are displayed.
- Cause
Apparent cause of the alarm message.
- Severity
Alarm level in accordance with the five severities warning, minor, major, critical and
indeterminate. According to ITU standards there are default colors for alarm severities,
see Alarm severities and alarm states:
- Al arm Class
Further entry for classifying the alarm.
Communication: Communication problem, e.g. error in data transmission.
Quality: Performance problem: e.g. transmission quality.
Processing: Processing problem: e.g. timeout exceeded.
Equipment: Problems with technical equipment: e.g. internal clock not synchronized,
hardware error in interface module.
Environment: customer-specific error in the environment: e.g. operating room door
open, fire alarm.
- Parent Node
Indicates the name of the parent node (e.g. MSN) which contains the NE.
- State
Unacknowledged or acknowledged.
97
- Ac know ledged b y
Identification of the operator who acknowledged the alarm message.
- Computer
Computer from where the alarm was acknowledged.
- Ac know ledge Tim e (Loc al)
Time when the operator acknowledged the alarm message.
- Addi ti onal Info
Additional information added by the operator to the specific alarm message. The
additional information is added by double clicking the cell or via context menu. The
field has a maximum size of 64 characters.
functions.
The main alarm-related functions are:
- Ac know ledge Selec ted Al arms
Acknowledges the selected alarm(s).
- Clear Alarms
Clears the selected alarms(s). The function is enabled for system alarms.
- Localize Reporting NE
Localizes the network element which is reporting the alarm in the Network Plan and the
tree views.
- Show Path Lis t
TNMS is able to generate a services list in the scope of an alarm. This functionality is
provided for all types of alarms. TNMS does not check, whether or not the alarm is
service affecting. The resulting list depends on the (internal) relation of the selected
alarm to other objects. The following relations are possible:
- TP related alarm: the list contains all services which use the affected TP
direction.
- Port related alarm: the list contains all services which use the affected port
direction.
- Equipment related alarm: the list contains all services which use the ports or
TPs implemented by the equipment.
- NE related alarms: the list contains all services which use this NE.
- Always on to p
Set whether the current alarm sub-window is always on top or free within the main
window. This is only available if the window style of the child windows is set to popup
in the View ->Window Style Menu.
descending order.
and Icons: Lists.
Note:
In case of multi-port cards with lower order TPs and more than a single AU4 per port (as
it is the case with O622-2 Card in hiT 7050 FP1 1.0) the alarm locations of lower order
TPs displayed in the Current Alarms… window should be read as follows:
Examplary location: 202.1.30012 is to be read as slot 202, port 1, AU 3, channel 12.
See also:
Fault settings
98
Client functions
Defining f ilters for alarm displays

By right-clicking in the Al arm List , you can activate a context menu in order to filter the list.
descending order.
and Icons: Lists.
99
Displaying alarms
In the TNMS Client there are various ways of displaying alarms:
- Switch to Surveillance mode.

- Use the context menu of a selected network element (Al arms -> Current Alarms...) to
display the current alarms filtered for the selected network element (seeCurrent alarm
list).
- To obtain the alarm list for a specific port connection, double-click on a port
connection or activate the Port connections ... context menu of an involved network
element to open the Port/Path Information window. In this case you have to select
the port connection in the left area of the window first. (SeeDisplaying the properties of
port connections). Then select the Al arms tab to display all port-related alarms.
- To obtain the alarm list for a specific MS protection, click on network element in the
Network Plan and in the context menu choose MS Protections… The MS Protection
window opens where you must select the tab Al arm to display all port-related alarms.
(See Displaying / modifying the properties of a MSP).
- To obtain the alarm list for a path, open the relevant properties window, e.g. by using
the context menu Properties... Select the path in the left area of the window, then
select the Al arms tab to display all path-related alarms (see Service / Path Properties).
- TNMS Core/CDM is also able to generate a path list in the scope of an alarm. You can
open this list via the context menu Show Path Li st of the Current Alarm List window
(see also Listing paths).
- You can view alarm statistics for the following objects by activating the relevant
Al arms -> Al arm Statis ti cs ... context menu (see Alarm statistics):
- a network element (select network element)
- a subnetwork (select subnetwork)
- a NE container (select NE container)
- one DCN channel (click on the concerning DCN channel)
- all DCN channels (click on DCN Compon ents)
- the entire network (click on Network Elements, i.e. on the caption of the
Network Elements tree)
- NetServer (click on the NetServer icon in the DCN Compon ents tree view.
100
Client functions
Event f orwarding
The event forwarding function can be enabled/disabled as follows:
- From the TNMS Client using the menu Fault -> Event Forwarding. This activates /
deactivates the function network wide.
- Select a network element or NE container in th e Network Plan and choose Event
Forwarding from the context menu. This activates / deactivates the function on NE/NE
container basis.
When disabled (tick is removed), a warning appears that no alarms or switching events are
reported to the TNMS Core/CDM Server. Due to the fact that disabling the event
forwarding affects all other clients, the client users are informed by a pop up window that
the global event forwarding is disabled and that no alarms or switching events are
forwarded anymore to the TNMS Server.
When disabled, the NE icon is provided with a supplementary overlay icon to indicate the
disabled status.
When enabled again (tick is visible again), it is recommended to reinitialize all NEs/NE
containers (e.g. reinitialize the NE container) in order to get the exact view of the network
status.
When enabled, a resynchronization will be executed automatically.
Note:
In case an overload situation is detected by the TNMS Server, the global event forwarding
is disabled automatically in order to protect the TNMS Server from overload.
Event forwarding feature as no function for FSP500.
101
Fault s ettings
TNMS Client -> Fault -> Settings... opens the Fault Settings window in which an audible
alarm signal for new alarms received and the polling interval of the current alarm list can be
set.
To set the sound, activate the option Sound on.
When you have activated Sound on, you can select the severity class for the alarm under
Start fr om severity class. The options Warning, Minor , Major , Critical and
Indeterminate are possible.
You can also choose the sound emitted when an alarm of this type is generated:
- Single
A single short acoustic signal is output if an alarm-raised event occurs. In order to
avoid performance problems for alarm bursts, the system waits for about one second
after issuing a sound signal before issuing the next one. All alarm events which have
occurred during this second are represented by that sound.
- Permanent
A periodic short acoustic signal is output every second, as long as there is at least one
unacknowledged alarm.
The setting is put into effect immediately with Ap ply.
Note:
The kind of sound can be set via Settings -> Control Panel -> Sounds in Windows XP
Professional. You can assign any audio file (*.wav) here.
External alarm output

The TNMS Client is able to put out the global alarm state via an I/O card (manufactured by
Meilhaus). The I/O card must be installed on the TNMS Client PC.
Preconditions for alarm output:
- The Meilhaus card is installed at the TNMS Client PC (i.e. the ME9X_32.DLL can be
loaded).
- Permanent is selected.
- Ext. alarm is activated (this option is only available if the Meilhaus interface card has
been installed).
- The highest current alarm severity reaches or exceeds the severity threshold of the
fault settings.
- There is at least one unacknowledged alarm (with corresponding severity) of a
managed NE (i.e. a NE contained in the Network Elements tree).
- The alarm output ends when all alarms are acknowledged or theext. alarm is
deactivated again.
The Current Alarm List Configuration allows operators of the user class Administrator to
change the polling interval for alarms. The Polling Interval specifies the time interval after
which the Current Alarm Li st window is updated. Thus, entering "5" (default) means that
the clients refreshes the current alarm list every 5 seconds.
Notes:
- The polling interval for Current Alarm List window is configured in the Fault
Settings window of the TNMS Client.
- The alarm overview refresh interval for the Al arm & Path Stati st ic s window is
configured in the General Settin gs window for alarms which can be invoked from
the TNMS SysAdmin tree.
- A very small value increases the load in your network and might decrease the
performance of your client. A different value can be specified for each client.
102
Client functions
- Information on probable causes and on user defined object types is given in the
Online-Help for TNMS SysAdm in.
103
Localizing alarms
1. Open the Current Alarms window in the TNMS Client via Fault -> Current Alarms….
2. Select an alarm from the list.
3. Localize the network element that reported the alarm using the context menu of the
Localize Reporting NE. This selects the network element icon in the Network
Elements tree view and in the DCN Compon ents tree view and the network map and
highlights it in color.
104
Client functions
Printing the alarm lis t

- Open the Current Alarm Li st in the TNMS Client via Fault -> Current Alarms....
- Click with the right mouse button on the contents of the window.
- Activate the Print... context menu.
Alternatively, after opening the Current Alarms... window activate the Print button in the
toolbar or use the File -> Print... menu.
The printout will include all information provided in the list, as well as the scope type that
has been applied.
105
Redirecting alarms for a network element

1. Switch to Surveillance or Services mode.
2. Use the Al arms -> Redirect Alarms... context menu of a network element to open the
Alarm Redirecti ons f or NE <xy> window.
3. a) Select an alarm redirection item and press the Modify button to modify the settings
for alarm redirection or
b) Press Ad d to configure a new alarm redirection for the network element.
This opens the Modify Alarm Redirection/Add Alarm Redirect ion window.
4. You now have to specify the following redirection parameters:
- Reporting NE
Network elements the alarms of which are to be redirected (already pre-defined
when the NE context menu Al arms -> Redirect Alarms... is activated).
- Original Pro bable Cause
Original probable cause = one of the possible TIF alarms of the network
element the alarms of which are redirected. Just use the arrow button to select
one of the pre-defined causes. You may only modify this entry when adding a
new alarm redirection (not for Modify).
- Map to NE
Target network element to which the alarm type in question is to be redirected.
Network elements can be dragged and dropped to this input field.
- Map t o Probabl e Cause
System-defined or user-defined probable cause which is to contain more
descriptive information than the original probable cause. Just use the arrow key
to select one of the pre-defined causes.
- Map to Object Type
System-defined or user-defined object type = name of a location where an
alarm may occur. Just use the arrow key to select one of the pre-defined
objects.
- Shelf
The shelf name is entered in this field. The name may comprise digits with a
value of between 0 and 4094. If you wish, you may also choose one letter
between a – o and append this to the digit sequence.
The value 4095o is also possible but with this value no information about the
rack will be given.
- Slot
The slot number of the shelf (digits only) is entered in this field. A value between
0 and 65535 is allowed.
- Container
The number of the container within the slot (digits only) is entered in this field. A
value between 0 and 4294967294 is allowed.
- Object
The number of the object within the container (digits only) is entered in this field.
A value between 0 and 63 is allowed.
Note:
To redefine objects and causes of this type, refer to theSysAdmin online help.
Press Appl y to confirm your settings.
106
Client functions
Saving the current alarms

- Open the window Current Alarms in the TNMS Client via Fault -> Current Alarms....
- Click with the right mouse button at the content of the window.
- Activate the Save As... context menu.
- Enter the path and the file name under which you wish to save the alarm list. The
alarm list will be saved in TSF format so that its content can be read in MS Access and
MS Excel.
107
Updating alarm i nformation

Alarms are generally updated automatically. Nevertheless network elements in
maintenance mode (displayed with a spanner) do not report changes in alarm state
spontaneously. For this case, in particular, you can manually update alarms for various
objects.
Switch to the Surveillance or Services mode of the TNMS Client and activate the Al arms
-> Refresh context menu.
This option is available for the following objects:
- a network element (select network element)
- a subnetwork (select subnetwork)
- a NE container (select NE container)
- one DCN channel (click on the according DCN channel)
- all DCN channels (click on DCN Compon ents)
- the entire network (click on Network Elements)
After activating the Al arms -> Refresh context menu you can either Refresh (display all
new alarm changes up to now = delta information) or Reinitialize the alarms (display all
new alarm information for the selected objects).
Note:
TNMS Core/CDM has a built-in alarm configuration counter for each managed NE in order
to recognize a misalignment of alarms stored in the TNMS Core/CDM server database and
the presentation in the physical network. If a mismatch of this alarm configuration counter
between TNMS Core/CDM server and TNMS Core/CDM NetServer is detected, an
automatic synchronization is performed.
For example, an automatic synchronization is done in the case of worker server outage
and a switch over to the standby system is done. If during the TNMS Core/CDM server
outage alarms are generated and detected by the TNMS Core/CDM NetServer, an
automatic alarm synchronization is performed during the start up phase.
108
Client functions
DCN management
DCN channels
The Data Communications Network is a network which allows the components of the
Telecommunication Management Network to communicate.
The TNMS NetServer establishes connections to the DCN network using various DCN
channels, several of which can be operated simultaneously.
The following DCN channels exist in TNMS:
- EMOS
- PDH
- QB3M
- SNMP
- TNMS-SX over ELI
- UNO
109
Displaying and processing alarms of a DCN component

1. In the DCN Compon ents tree view of the TNMS Client, select a single DCN channel
or all DCN channels (by clicking on DCN Compon ents).
2. The context menu enables you to perform actions relating to alarms for one DCN
channel or all DCN channels. More information is provided underMenu entries for
alarms.
110
Client functions
General channel properties

General settings for DCN channels can be displayed and edited using two tab pages.
General t ab
General settings for communication channels can be configured and modified in the
General property page provided in the <DCN Channel Obj ect> window:
Note: The General page (except the Description field) can only be modified under TNMS
SysAdmin!
Tab page Field Name Description

General ID Name A unique name for the DCN channel is entered in this
field.
Channel Type The type of DCN is shown in this field.
Description Additional user-defined information can be entered in
this field.
Scheduled Startup tab

The number of NEs which can be uploaded simultaneously can be specified in the NE
Initializing
property page provided in the <DCN Channel Object> window. A different value can be
configured for each channel.
Tab Page Field Name Description

Scheduled Limit If the Enable Schedul ed Startup checkbox is
Startup activated, you can enter the maximum number of
NEs to be started simultaneously in this field.
Once the specified number of NEs has been uploaded, the system uploads the next batch
of NEs (up to the specified limit). This process may be repeated several times until all NEs
have been started.
Confirm your settings by pressing Ap pl y in the main menu and exit the window by pressing
Close.
For more information, press Help.
111
General NetServer pr operti es

General settings can be configured and modified for the NetServer in theGeneral property
page provided in the <NetServer > window.
Note: The General page (except the Description field) can only be modified under TNMS
SysAdmin!

General ID Name A unique name for the NetServer is entered in this
field.
Computer name The computer name or IP address is shown in this
field.
Retry Interval The interval before attempting to re-establish an
(min) aborted connection is entered in this field.
this field.
Confirm your settings by pressing Ap pl y in the main menu and exit the window by pressing
Close.
For more information, press Help.
112
Client functions
Listin g DCN objects

The List of DCN Objects provides DCN information of one object, a selected set of objects
or all objects of a network. TNMS Client -> View -> Lists... opens the list window. Clicking
on the DCN Objects tab on the bottom displays the List of DCN Objects window.
The DCN Objects window shows a list of DCN objects existing in TNMS with their
available attributes. You can invoke the window e.g. from
- TNMS SysAdm in by clicking the button DCN Management. This opens the DCN
Management window where you must click the button Lists.
- TNMS SysAdmin via Configuration -> DCN Management. This opens the DCN
Management window where you must click the button Lists.
- TNMS Client via View -> Lists. This opens the Port Connections window where you
must click the DCN Objects tab at the bottom.
- TNMS Client via View -> Find. This opens the DCN Object Li st window
Depending on the chosen column settings, the following information is displayed in the
DCN Object s window:
- Index
Number of the rows in the list.
- DCN Type
Displays the type of the DCN object, e.g. server, netserver, channel or NE.
- Name
Displays the name of the DCN object.
- Address
Displays the address of the DCN object.
- State
Displays the state of the DCN object, e.g. running, deactivated, connection failed,
invalid, etc.
- NE Name
Displays the NE name.
- NE Location
Displays the location of the NE.
- Write Access
Displays the write access of the DCN object.
- Highest Alarm Severity
Displays the highest alarm severity existing for the DCN object.
- Alarm Stat e
Displays the alarm state of the DCN object.
- Event Forwarding
Indicates, whether event forwarding for this DCN object is enabled or not.
- Operation al State
Displays the operational state of the DCN object.
In the default state, the list of DCN objects in TNMS Client contains more columns than
the corresponding list in SysAdmin.
functions.
More information on these functions is provided in Setting filters and sorting lists and Icons:
Lists.
In order to jump to an NE in the Network Plan, select e.g. the NE and click the Find button
in the toolbar.
113
In order to jump to an NE in the DCN Management, select the NE and click the Localize
DCN-Object entry in the context menu.
114
Client functions
Resynchronizing the data of a DCN channel

1. Select a DCN channel or all DCN channels (by clicking onDCN Component s) in the
DCN Component s tree view of the TNMS Client.
2. Use the context menu to activate Resynchronize Data. A dialog window opens.
3. In the dialog window
- click Resynchronize to realign the database with the current data of network
element(s) in TNMS Core/CDM;
- click Reinitialize to delete the current data of network element(s) in TNMS
Core/CDM and to transfer and accept all data from network element(s).
During resynchronization, the data in the TNMS Server database is matched to the
data newly polled.
When resynchronizing data you can choose if you want to load all new data from the
network element(s) into the TNMS Core/CDM or if you want to update the differing
data only.
115
Lists and logs handling

Creating a performance log
The menu command TNMS Client -> Performance -> Performance Logs... opens the
Tables window with the Performance Logs register. Use Ad d to create a new
performance log.
You can also reach the Performance Log Configuration window directly via the Create
Performance Log... context menu of a network element (in the Network Elements tree or
in the Network Plan), or of a path in the Surveillance mode or Services mode:
Note:
- If the system displays the message
" No quota defined for custom l ogs" ,
the space required for custom logs is full. In order to create the log it will be necessary
to resize the logspace. Please contact the system administrator.
1. Under Log Name allocate a name to the performance log (max. 31 characters).
Under Log Size specify the maximum number of entries. The size you can specify
here is limited by storage space connections made by the TNMS Core/CDM
administrator. More information is provided in the SysAdmin online help.
2. Under Log Full Condition you can specify the system behavior when the log is full.
The following options are provided:
Wrap around: if the performance log is full, new entries are still recorded by deleting
the oldest entries.
Stop logging: New events/measured values are not taken into account. The file
remains unmodified.
3. Under Log Full Warning Threshold , you can configure a warning to be displayed
when a specific percentage of the log size has been reached. UseNo to skip this
option. If you do so, note that under certain circumstances you may not notice when
the log is being overwritten or no longer maintained.
4. By activating the Start option, you create and activate the log immediately after the log
wizard has been closed with Finish (in the next window).
5. By activating the Virtual Tandem Connection Monitoring option, the performance
measurement will be processed from two measurement points.
6. Use Next to go to the second window in order to define the PMP parameters and the
measurement interval for the performance log and afterwards to create the
performance log.
In the second window you can define performance measurement points now:
a) Use drag-and-drop to include a network element from theNetwork Elements tree
view (or from the Network Plan) or to include one or more path(s) from the
Subscribers and Services tree view in the field PMP Container . Note that multiple
selection of several paths in the Subscribers and Services tree is supported.
Alternatively you can also open the Routing tab of the Service / Path Properties
window (e.g. via the Properties... context menu of a path) and move termination points
(each termination point in the TPA, TPB and TPB columns is selectable) via drag and
drop into the PMP Container .
b) Under Measurement Interval, select whether 15-minute counters or 24-hours
counters are to be recorded.
Note:
For NEs using the QD2 interface, the counters are limited to 255 counts per interval
116
Client functions
when the 15-minute interval is selected, and to 65535 counts when the 24-hours
interval is selected.
c) Under Update After N x Measurement Interval enter the desired numeric value:
0: means data transfer if the memory of the NE is full.
1: means data transfer every 15 min or 24 hours.
N: means a multiple (of measurement intervals).
d) Via the Unlock Button you can unlock PMPs of the PMP List (of the lower right-hand
area).
e) In the lower left-hand area of the window under PMP Tree, all performance
measurement points of a selected network element and important performance
measurement points of a selected path or explicitly input TPs (from the path properties
in the Service / Path Properties window) are displayed. You can now use the arrow
buttons to determine which PMPs (Performance Measurement Points) are to be
recorded in the log. Simply select these points and transfer them with the right arrow
button into the lower center area of the window. Note that TNMS Core/CDM does not
check whether a selected measurement point is relevant for the traffic direction of the
path. This is especially true in the case of unidirectional services. A measurement point
may no longer belong to a service if the path is changed (re-routed).
Notes:
- There might be ports to be displayed that do not contain any PMPs.
- In the lower center area of the window under PMP List you have a permanent
overview of all performance measurement points which will be taken into
consideration for the performance log. Several parameters can be selected
(context menu -> Column Selection…).
- In the right-hand area of the window you see the PMP parameters of a selected
PMP of the PMP List, which can be activated or deactivated.
- Once selected, it is not possible to change the PM parameters when modifying
the PM log.
- If a Performance Log is to be created for MS or RS trails starting at ports (i.e. for
section monitoring), the offered PMPs in the PMP tree of the Performance Log
Configuration window may include PMPs of lower order TPs (e.g. AU4-CTP,
TU12-CTP etc.), although they are basically not needed. These PMPs can be
ignored.
- If a single Performance Log is created for more than one path then this log will
be assigned to the first path only. Also, this log will display in case of a
modification of the log, all existing PMPs of the first path plus the already
included PMPs of the additional paths.
Each PMP (Performance Measurement Point) is defined by the following specifications

(depending on the chosen column settings):
- Index
- NE
Network element.
- Port
Identification of the port within the network element.
- TP
Termination Point; Identification of the termination point within the port.
- PMP
Performance Measurement Point; Identification of the Performance
Measurement Point within the termination point or port.
- Location
Location of the PMP.
117
- Admin St ate
The administrative state of the performance measurement point controls
performance data acquisition. If shown as unlocked (active), data acquisition in
a network element is enabled. If shown as locked (standby), data acquisition for
this performance measurement point is blocked. TNMS Core/CDM periodically
requests performance data from a performance measurement point only if its
administrative state is set to unlocked and if the performance measurement
point belongs to an active performance log.
- Provision State
The provisional state of a performance measurement point shows whether the
PMP exists in the NE or not (a PMP can disappear after e.g. deactivation of the
multiplex structure. de-configuring of card, etc.).
- End Point
In the case of Tandem Connection Monitoring, the End Point entry will display
the start point (i.e. A-End) and the end point (i.e. Z-End) of the performance
measurement.
The width of the columns can be adjusted by clicking in the column header and
dragging with the left mouse button. In addition, the list content offers a context
menu for copying (Copy) list contents, selecting the columns to be displayed
(Column Selection) or for saving the list contents (Save As...).
Use Ap ply to create the performance log. Provided you have activated theStart option in
the previous window, the log is started immediately. Otherwise you must still explicitly
select and start the log in the Performance Log s window. Make sure that TNMS
Core/CDM has write access to all network elements involved in this performance log.
Otherwise the affected performance measurement points will remain in thelocked state. In
this case you can try to unlock them again by using the buttonUnlock PMPs f rom PMP
list once NE write access has been requested or enforced.
118
Client functions
Displaying a performance log

You can display a performance log either via TNMS Client -> Performance ->
Performance Logs... or via TNMS Client -> View -> Tables -> Performance Log .
To request the latest performance data from the NEs, press theUpdate button.
(The Update button does not update the list of performance logs shown. It only updates
the data which these logs contain. If you wish to update the list of performance logs, press
F5.)
Now select the required performance log and click the buttonView.
Suppressed Intervals
In case that during a performance interval no data has been received, because no
problems concerning the performance data have occurred, this interval will also be stated
in the performance log. The duration of an suppressed interval will be 900 times the
number of suppressed intervals for any 15 min log or 86,400 times the number of
suppressed interval for any 24 hour log.
This feature is supported by Q3 network elements, such as MTS1.1E and OCU network
elements.
For each displayed performance entry you will find the following information (see notes
below):
- Index: Number of the row in the list.
- Time (Local): Specifies in GMT the time (NE clock) at which the measurement interval
ends.
- NE: NE name.
- Port: Port name.
- TP: Termination point name (optional).
- PMP: Performance Measurement Point name.
- Location: Indicates Near End or Far End.
- Direction: Indicates the direction of a port. Values are Tx for sender, Rx for receiver
and unknown (for migrated PMPs).
- TMP [sec]: total measurement period, i.e. the monitoring time in seconds. As Q3 NEs
cannot deliver the measurement period, the default period is used.
- BB E: background block errors, i.e. errored blocks (EB) not occurring as part of a SES.
An EB is a block with one or more errored bits.
- ES [sec]: errored seconds. An ES is a one-second period with one or more errored
blocks.
- SES [sec]: severely errored seconds. An SES is a one-second period which contains >
30% errored blocks or at least one Severely Disturbed Period (SDP). SES is a subset
of ES.
- UAS [sec]: unavailable seconds. All seconds within the unavailable time are
accumulated, i.e. the number of 1-second intervals for which the connection is not
available. During unavailable time only the UAS count is accumulated.
- PJEplus: This PM parameter counts the number of positive pointer justifications.
- PJEminus : This PM parameter counts the number of negative pointer justifications.
- Collisions: This PM parameter counts collisions detected on physical.
- SEFS [sec]: This PM parameter counts the number of Severely Errored Framing
Seconds.
- CV [bit]: This PM parameter counts the bit errors not occurring during a SES.
- LoCT [sec]: This PM parameter counts the seconds the carrier is not available (loss of
carrier time).
119
- Plmin [dB/10]: This PM parameter calculates the minimum power level.

- Plmax [d B/10]: This PM parameter calculates the maximum power level.
- Plavg [d B/10]: This PM parameter calculates the average power level.
- Qmin [1/100]: This PM parameter calculates the minimum quality (i.e. indication of the
estimated BER of the received signal).
- Qmax [ 1/100]: This PM parameter calculates the maximum quality (i.e. indication of
the estimated BER of the received signal).
- Qavg [ 1/100]: This PM parameter calculates the average quality (i.e. indication of the
estimated BER of the received signal).
- SNRmin [dB /10]: This PM parameter calculates the minimum signal to noise ratio.
- SNRmax [dB/10]: This PM parameter calculates the maximum signal to noise ratio.
- SNRavg [dB/10]: This PM parameter calculates the average signal to noise ratio.
- BadPacketsRx: This PM parameter counts the received errored packets.
- GoodPacketsRx: This PM parameter counts the received error-free packets.
- GoodPacketsTx: This PM parameter counts the transmitted error-free packets.
- PSC: This PM parameter counts the protection switches.
- CBES [sec]: This PM parameter counts the corrected bit error seconds.
- LostFramesQueueOverflowRx : This PM parameter counts the lost frames of the
receiver side due to Rx Queue Overflow at a Ethernet access port.
- BadFramesCrcErrorRx: This PM parameter counts the bad frames (CRC Error) of the
receiver at a Ethernet access port or at a Ethernet internal port.
- MultiBroadcastFramesRx : This PM parameter counts the Multi-/Broadcast Frames of
the receiver side at a Ethernet access port.
- MultiBroadcastFramesTx : This PM parameter counts the Multi-/Broadcast Frames of
the sender side at a Ethernet access port.
- MultiBroadcastThroughputRx: This PM parameter counts the Multi-/Broadcast
Throughput of the receiver side at a Ethernet access port.
- MultiBroadcastThroughputTx: This PM parameter counts the Multi-/Broadcast
Throughput of the sender side at a Ethernet access port.
- UnicastThroughputRx: This PM parameter counts the Unicast Throughput of the
receiver side at a Ethernet access port.
- UnicastThroughputTx: This PM parameter counts the Unicast Throughput of the
sender side at a Ethernet access port.
- UnicastFramesRx: This PM parameter counts the Unicast Frames of the receiver side
at a Ethernet access port.
- UnicastFramesTx: This PM parameter counts the Unicast Frames of the sender side
at a Ethernet access port.
- GoodFramesStreamTrafficRx: This PM parameter counts the good frames stream
traffic of the receiver side at a Ethernet internal port.
- GoodFramesBestEffortTrafficRx : This PM parameter counts the good frames best
effort traffic of the receiver side at a Ethernet internal port.
- GoodFramesThroughputStreamTrafficRx : This PM parameter counts the good
frames throughput stream traffic of the receiver side at a Ethernet internal port.
- GoodFramesThroughputBestEffortTrafficRx : This PM parameter counts the good
frames throughput best effort traffic of the receiver side at a Ethernet internal port.
- CollisionsCSMA: This PM parameter counts collisions detected on physical.
- BERmax: BERmax is a gauge value. It can increase and decrease its value in contrast
to the PM value in near End PM parameter (ES, SES, BER and UAS) which can only
increase and always one at a time. Also instead of summation value, a maximum value
is calculated over seconds where BER measurement is available.
120
Client functions
- BERavg: BERavg is a gauge value. It can increase and decrease its value in contrast
to the PM value in near End PM parameter (ES, SES, BER and UAS) which can only
increase and always one at a time. Also instead of summation value, an average value
is calculated over seconds where BER measurement is available.
- AISS: This PM parameter counts alarm indication signal seconds.
- B1CVS: This PM parameter counts B1 code violation seconds.
- ESTA: This PM parameter counts the errored seconds type A.
- ESTB: This PM parameter counts the errored seconds type B.
- FC: This PM parameter counts the failure count.
- FEBE: This PM parameter counts the far end bit errors.
- LSS: This PM parameter counts the loss of signal seconds.
- LBIASN: This PM parameter indicates the Laser BIAS Current Normalized
(percentage).
- RPLN: This PM parameter indicates the Received Power Level Normalized
(percentage).
- TPL [dB /10]: This PM parameter indicates the Current Transmit Power Level.
- BBER: This PM parameter indicates the Background Block Errors Ratio.
- ESR: This PM parameter indicates the Errored Seconds Ratio.
- SESR: This PM parameter indicates the Severely Errored Seconds Ratio.
- SuspectIntervalFlag: This PM parameter indicates if a PM record is to be regarded as
suspect (incorrect), i.e. the interval (15 min or 24hrs) for collecting the performance
data was disturbed. Suspect = 1, Unsuspect = 0.
- Average Throughput Rx (Bytes /s): This PM parameter indicates the average data
throughput in Receive direction
- Average Throughput Tx (Bytes /s): This PM parameter indicates the average
throughput in Transmit direction.
descending order.
and Icons: Lists.
Notes:
PM parameters which are not selected by the operator are not included in the performance
record.
Counters that are not supported by a specific network element are set to zero by TNMS.
The title of each column also contains the measurement unit.
121
Deleting performance logs

1. To delete user-defined logs (performance logs), open thePerformance Log window in
the TNMS Client e.g. via Performance -> Performance Logs....
2. Select the performance log you want to remove.
3. Stop log recording using Stop if necessary.
4. Press Delete.
122
Client functions
Handling performance logs

The menu command TNMS Client -> Performance -> Performance Logs... displays the
Tables window. This window provides an overview of the performance logs which have
already been created.
For each performance log the following information is displayed:

- Index
- Log name
Name of the performance log set by the operator during configuration of the
performance log.
- Log type
The log type is performance log or TCM log.
- Created By
Operator who created the performance log.
- Creation Time (Local)
Time the performance log was created.
- Current Log Size
Number of entries.
- Log full warning threshold
During configuration of the performance log the operator specifies whether a warning
should be signaled when a certain percentage of entries has been exceeded. Here the
specified threshold is displayed.
- Interval
Shows the used period of time used for collecting the performance data, either 15min
or 24h.
- Admi n State
Active for a log that is started (performance data is currently being measured).
Standby for a log that has been stopped.
- Provision State
The provisioning state shows if assigned PMPs can be monitored (provisioned,
unprovisioned) .
Notes:
- A PMP contained in a PM Log is unprovisioned if it does not exist anymore (e.g.
because of card deletion or the corresponding TP is no longer valid).
- A PM Log is unprovisioned if at least one contained PMP is unprovisioned or
the administrative of at least one contained PMP is locked.
- Path
If a path is assigned to a performance log, the name of this path is displayed here.
- Service
If the performance log has been created including a service in the PMP container, the
name of this service is displayed here.
- Subscriber Name
Subscriber to whom the above service is assigned.

- Update the selected performance log. The table of all performance logs is, however,
not updated. To update the table of all performance logs, press <F5>. The Admin State
must be Active.
- View the current data of a selected performance log.
- Modify the configuration of a selected performance log. The Admin State must be
Standby.
123
- Add (create) a further performance log.

- Delete a selected performance log. The Admin State must be Standby.
- Start the measurement for a selected performance log.
- Stop the measurement for a selected performance log.
- Close the window.
descending order.
and Icons: Lists.
124
Client functions
Menu entri es for alarms

- Al arms -> Al arm Statis ti cs ... Show alarm statistics for the selected network element, NE
container or DCN channel. (See Alarm statistics).
- Al arms -> Current Alarms... Show the current alarms with a filter for the selected network
element, NE container or DCN channel. (See Current alarm
list).
- Al arms -> Al arm Log Shows the alarm log with a filter for the selected network
element, NE container or DCN channel. (See Alarm log).
- Al arms -> Ac know ledge All Acknowledges all alarms relating to the selected network
element, NE container or DCN channel. (See
Acknowledging alarms).
- Al arms -> Redirect Alarms Opens the Al arms Redirect ions for <NE> window. (See
Displaying alarms redirections for a network element).
- Al arms -> Refresh... Updates the alarm information for the selected network
element, NE container or DCN channel. This may be
necessary, for example, if the network element is in a state
in which it cannot send unsolicited messages (e.g.
maintenance mode or idle). The data is polled directly from
the network element. (See Updating alarm information).
See also:
Displaying and processing alarms of a DCN component
Displaying and processing the alarms of a network element
Displaying and processing the alarms for an NE container
Displaying alarms redirections for a network element
125
Modifying configu ration settings for performance logs

1. To change the configuration settings for performance logs, open thePerformance
Logs window in the TNMS Client via Performance -> Performance Logs....
2. Select the log for which you want to change the recording conditions.
3. Stop log recording using Stop if necessary. Close the log if it is currently open.
4. Press Modify.
5. Make your changes. (Move through the Performance Log Configuration windows
with Next.)
6. Press Ap ply.
7. You can now restart your log using Start.
Note:
When a PM log is modified it is not possible to include additional PMP parameter - in
addition to those originally configured - into the log.
126
Client functions
Notification Log
The Notification Log window is opened automatically when you log into TNMS Client and
TNMS SysAdmin as an operator.
This window contains feedback for user actions and is displayed on top as an alternative to
message boxes, if necessary.
The objective of this window is to group together a number of message boxes so that
interruptions to work at the TNMS Core/CDM are avoided as far as possible.
The Notification Log window contains the columns:
- Index
- Icon
The following icons can be displayed:
{bmc event_mess.bmp} Message
{bmc event_warn.bmp} Warning
{bmc event_error.bmp} Error
- Time (Local)
Date and time at which the message was sent.
- Service
The operation relates to the area in which the action occurred (Example: Service:
Performance Log, Action: Save As).
- Operation
Action to which the message refers.
- Description
Content of the message sent.
The following table shows some information about some examples for events being
logged (the shown text is of exemplary character and may differ from the exact text
being displayed):
Service Operatio n Descript ion
Communication Communication TNMS Client was logged off by TNMS Server!
Communication Communication TNMS Server shutdown in progress! TNMS Client will
be automatically logged off in %1!d! minutes!
User Interface LCT Application not found:
User Interface LCT Problem running application - application already
started or incomplete installation or missing DLL!
Log Service LOG Service No quota defined for custom logs!
[Create custom log]
Log Service LOG Service The termination point does not belong to the associated
service!
[Create custom log]
Path Service Manual Path Routing Crossconnection >>ID %d<< not available!
Path Service Manual Path Routing Crossconnection >>ID %d<< - NE not ready for creating
CC.
Net Service Network Distribution of TNMS server time failed due to
communication problems.
descending order.
and Icons: Lists.
127
128
Client functions
Network Event Log

The network event log contains a history of configurations on the network management
layer (i.e. creation or activation of a service). In contrast to the system message log, the
network event log documents actions directly initiated or triggered by the network or single
network components.
The following events are recorded in the Network Event L og:
- Creation, modification, deletion and state changes of services and NE containers.
- Creation, modification, deletion of subscribers and path containers
- Creation, modification, deletion and state changes of port connections.
- Creation and deletion of network elements in the Network Map or in the Network
Element tree.
- Connection loss or re-establishment of network elements.
- Module configuration changes.
- Network element reset messages.
- Protection switching events: Multiplex Section Linear Trail Protection, Bidirectional
Self-Healing Ring, Equipment Protection.
- Protection switching events for paths.
- Maintenance mode changes.
You can display a network event log directly using TNMS Client -> View -> Network
Event Log or use TNMS Client -> View -> Tables... -> select Ac ti ve Netw ork Ev ent Log.
A list is displayed of all the events specified by the TNMS Core/CDM operator when
configuring the log, and which actually occurred during the recording period.
Each list entry comprises the following data:
- Index
- Time (Local)
Specifies the time at which the event was recorded (entry displayed either as
Greenwich Mean Time or local time).
- Event Type
Depending on the settings in the Network Event Lo g Configuration window the
following events are recorded.
Icon Event type Event output Applicable to
Object in <container> NE, NE Container,
created Subscriber, Module
for <container> Service, Path
between <NE1> and <NE2> PC
Object in <container> NE, NE Container,
deleted Subscriber, PC, Module
from the database / from the Service, Path
network
Attribute <attribute name> changed NE (type, name, location),
value from <old value> to <new NE Container (name,
changed value> inscription, description,
assigned operator/user
group)
Service (name, write
protection, protection),
Path, Subscriber, PC
129
Icon Event type Event output Applicable to

(name),
Probable Alarm Causes,
Alarm Object Types, Alarm
Redirections
<attribute name> changed NE (HW configuration,
date/time)
State <state attribute name> NE (access state, EM write
changed changed from <old value> to access state, Operating
<new value> mode, operational state)
Service (operational state,
administrative state,
provisioning state, protection
state)
Path (operational state,
provisioning state, protection
state)
<state transition description NE (protection switching of
delivered by CEC> MSLTP, BSHR, Equipment
Protection)
<state transition name> NE (reset)
Path (manually re-routed)
Relationship moved from <container> NE, NE Container, Service
changed <name> to <container> Paths <-> Service
<name>
Services <-> Subscriber
- Source Type
Depending on the settings in the Network Event Lo g Configuration window, events
for the following objects are recorded: network element, module, NE container, path
container, subscriber, port connection, service, path.
- Source
Identification of the object which reported the event.
- Description
Plain text describing the event.
- Operator
Identification of the operator who initiated the event.
- Computer
Computer where the operator mentioned above has logged in.
descending order.
and Icons: Lists.
130
Client functions
Permanent logs
Every permanent log is split up into an active log and a log archive which can be viewed in
separate windows. New log entries are written to both the active log and the log archive.
When an active log reaches its limit, the oldest log entry is deleted. The log archive only
shows a snapshot and is not updated automatically for performance reasons. It can,
however, be updated manually.
There is always only one permanent log for each log type. Each permanent log contains
information for the whole TNMS network. Permanent logs are backed up automatically
together with the databases. When restoring a backup set you can select which backup set
should be restored.
TNMS supports three types of permanent log:
- Al arm Log
The alarm log contains historical alarm information for the supervised network.
- Network Event Log
The network event log contains a history of configuration changes on the network
management layer, for example the creation or activation of a service. The network
event log documents actions directly initiated or triggered by the network or single
network components.
- System Message Log
The system message log contains a history of relevant administrative events.
- Security Event Lo g
The security event log contains security relevant operator events like login/logout time,
operator name, computer name, etc.
An overview of available permanent logs is provided in theTables window which can be
opened via View -> Tables... in TNMS Client.
More information on the contents of the tabs Standard Logs and Archiv ed Logs (shown
in the Tables window) is provided under Viewing logs.
General log management information is provided under General log management
information.
Information on the filter and sort options available is provided under Icons: Lists and
Setting filters and sorting lists.
131
Starting and stopping performance logs

Once you have configured a performance log you must start recording in order to obtain
the relevant performance data.
1. Go to the Performance Log window of the TNMS Client e.g. via Performance ->
Performance Logs....
2. Select a performance log.
3. Press Start.
If you wish to stop recording for a performance log file, perform steps 1 and 2 and then
click on the Stop button.
Note:
In case you activated the Start option when you created or modified the performance log,
the log is automatically started when you terminate the configuration with Ap ply.
See also:
Displaying logs
132
Client functions
Tandem connection monitori ng

Tandem connection monitoring (TCM) allows you to collect performance data from two
different performance measurement points (PMPs). TCM is an attribute that can be set at
log creation for a regular performance log; the log type is then set toTCM log. The TCM-
data are provided as a report to the operator.
The measurement data will be displayed in the performance log. The performance log
displays:
- End-PMP
- length of measurement interval
- TCM data, i.e. the difference of all values. Negative values are set to zero.
Note:
Although the TCM performance log displays the same entries as an ordinary performance
log, the values represent the difference between the two measurement points. The
operator should this keep in mind when reading the log files.
When creating a performance log you must set TCM as an attribute. More information is
provided under Creating a performance log. The log type created is set to TCM log.
It is possible to monitor bidirectional and unidirectional connections . The following rules

apply:
In the case of a unidirectional connection, the following rules apply:
- Both selected PMPs have to belong to the same service
- Both selected PMPs have to belong to the same transmission layer
- Both selected PMPs have to measure the same transmission directions.
Since TCM values are calculated for one direction only within one TCM log, it is necessary
to create two TCM logs (direction A->Z and A<- Z) in order to monitor a bi-drectional
connection.
As tandem connection monitoring in TNMS Core/CDM is different to TCM in individual
NEs, the output generated by TNMS Core/CDM may also differ.
133
NE cont ainers
Addi ng a new netw ork element or subnetw ork t o an NE c ontainer
When opening the TNMS Cli ent for the first time, all network elements/subnetworks which
have ever had a DCN connection to TNMS are displayed in theDCN Compon ents tree
view. You must now modify the data in the Network Elements tree view and Network Plan
to reflect your network structure. Once you have created a proper network structure with
NE containers you can start adding network elements or subnetworks to the relevant NE
containers.
To add a network element to an NE container just drag the network element from theDCN
Components tree view into the Network Elements tree view or into the Network Plan.
Drop the network element/subnetwork on the relevant NE container.
134
Client functions
As si gnin g a bac kground bit map

You can use a background bitmap to assign a background illustration (e.g. map of a
country, building plan) to your NE container. You can assign one background illustration
per NE container.
To do this, switch to the Network Editor mode. NE Container -> Background Bitmap...
takes you to the As si gn Backg round Bit map window. In this window you can perform the
following actions:
Use Ad d to insert a new bitmap into the list of available bitmaps already displayed in the
window.
Use Modify to edit the name of a bitmap already accepted into the list and update the
storage location of the bitmap.
Use Ap pl y to send a bitmap selected in the list to the TNMS Core/CDM Server for storage.
The illustration now appears in the background of your Network Plan.
In order to suspend the assignment of a bitmap to a NE Container, selectnone as
background and click Ap ply.
Use Delete to remove a selected bitmap from the list.
Note:
TNMS Core/CDM does not provide the option of editing a bitmap or resizing a bitmap. The
bitmap must be edited with a special image processing tool.
135
Changing the background bitmap

To change the name of a background bitmap for the Network Plan, update its path or add a
new bitmap, switch to the Network Editor mode. Right-click an NE Container and select
Background Bitmap....
The Assign Background Bitmap window is opened.
You can now chose to Modify the name of an existing bitmap or Add a new bitmap.
Modify opens the Change Bitmap window, Add opens the Add Bit map window.
In order to suspend the assignment of a bitmap to a NE Container, selectnone as
background and click Apply.
Both windows contain the following fields:
- Description
Here you can specify a name for the background bitmap.
- Path and Filename
Here you can browse to the correct path for the bitmap using the… button.
Click Apply to save your changes.
136
Client functions
Controlling access rig hts to NE containers

TNMS Core/CDM supports the limitation of access rights for an operator or a user group
assigned to a certain NE container. The whole network is visible to all operators (read-only
access), but only the NE resources (i.e. NEs, NE containers, services, performance logs
and fault locations) included in the NE container assigned to the current user/user group
are allowed to be modified by the same.
Additionally, the visibility of the NE containers may be restricted viaTNMS SysAdmi n so

that the current user or user group only sees the NE containers they are assigned to. Only
operators of the user class Ad mini st rator may change access rights to NE containers and
have access to the menu described below.
1. In case you want to restrict the visibility of the NE containers, openTNMS SysAdmi n
and double-click Container Access in the tree view. Here, select Restricted.
2. In order to control the access rights to individual NE containers, open TNMS Client,
switch to the Network Editor mode and use the Permissions ... context menu of a NE
container. This opens the User Permissions for NE Containers window which
provides an overview of the current NE container structure and the users/user groups
currently assigned.
3. Select the User or User Group to Assign . You may select any user or user group
configured in TNMS SysAdmi n via User Management.
4. Then tick the NE container you want to assign to the user or user group.
5. Click Apply to confirm the settings.
Note:
It is not possible to assign more than one user or user group to the same NE container. For
this reason, the definition of user groups and NE container has to be planned well.
To remove the user/user group connection to an NE container, simply deactivate the small
checkbox at the left side of the NE container item in the tree and press theApply button to
confirm the changes. Changes may be performed for more than one NE container at a
time.
See also:
User class
137
Deletin g an NE container
1. Switch to the Network Editor mode of the TNMS Client.
2. Select the NE container to be deleted in the Network Elements tree or Network Plan
view.
3. Use the Delete context menu to delete the NE container.
Notes:
- When an NE container is deleted only the relevant structuring is removed. Any existing
network elements/subnetworks are removed from the NE container but not from TNMS
database and will remain available in the DCN Components tree.
- An NE container that still contains network elements or subnetworks can only
be deleted if there are no port connections configured at any of these network
elements/subnetworks.
138
Client functions
Displaying and processing alarms f or an NE container

1. Switch to the Surveillance mode of the TNMS Client.
2. Select a NE container in the Network Elements tree or Network Plan view.
3. The context menu enables you to perform actions relating to alarms for the NE
container. More information is provided under Menu entries for alarms.
139
Displaying the properties of NE containers

An NE container acts a container for a set of network elements. It can also contain one or
more NE containers. NE containers are used for structuring the network and thereby allow
a clear overview of the Network Plan for a large number of network elements.
1. Select the NE container in the Network Elements tree or Network Map of the TNMS
Client.
2. Use the Properties... context menu to open the Properties of NE Container window.
The following information will be displayed:
- Line 1
Contents of the first line of the icon label (max. 64 characters).
- Line 2
Contents of the second line of the icon label (max. 64 characters).
- Line 3
Contents of the third line of the icon label (max. 64 characters).
- Object Descripti on
Additional description text (max. 79 characters) for the NE container.
- Icons
The currently chosen icon for the NE container is shown here; you can choose a
different icon here if you want.
Entries made under Line 1, 2, 3 will be included in the Network Elements tree view.
140
Client functions
Handling NE containers
NE containers are shown in the hierarchical structure of theNetwork Elements tree view
in TNMS Client.
In the Network Management View you can:
- drag and drop network elements from the DCN Compon ents tree view to the Network
Elements tree or to the Network Plan view,
- drag and drop NE containers to different locations within theNetwork Elements tree
view (nesting),
- assign a bitmap to any NE container using the context menu in theNetwork Elements
tree view; see Assigning a background bitmap,
- position network elements in the Network Plan view by clicking on them with the left
mouse button and dragging them (only in Network Editor mode),
- double-click on an NE container icon in the Network Plan to open the NE container (i.e.
display its contents),
- click an NE container in the Network Elements tree view to switch to this NE
container.
- move up one hierarchy level by clicking the arrow in the left upper corner of the
Network Map.
141
Properties of a NE container
Use this window to create or modify a NE container as described below:
Creatin g a NE cont ainer:

2. Select an NE container in the Network Elements tree or Network Plan view if you wish
to create a new NE container in the hierarchy level below this NE container, or call up
the context menu of the entire Network Elements tree (click the right mouse button on
Network Elements).
Alternatively you can create an NE container via Configuration -> Create NE
Container...
3. In either case, use the Create NE Container... context menu to call up a window of the
same name.
4. Enter information at least in the first inscription line (Line 1).
5. Choose an icon for the NE container to be created.
6. Click Create. The new NE container then appears in your Network Elements tree view.
If you need to move the NE container use drag-and-drop. In order to move a NE
container to the highest level activate the context menu Move to Firs t Tree Level.
7. In the Properties of NE Container window please click Ap ply to confirm the settings
(see: Displaying the Properties of NE containers).
Modifying t he Properties of a NE container:

2. Select the NE container in the Network Elements tree or Network Plan view.
3. Use the Properties... context menu to open the Properties of NE Container window.
4. Edit the information you want to modify, e.g. the Object Inscription, Object Description or
choose a different icon for the NE container.
5. Press Appl y to confirm the changes.
142
Client functions
Resynchronizing the data of an NE container

1. Select the NE container in the Network Elements tree or Network Plan view of the
TNMS Client.
2. Resynchronize the data of all the network elements in TNMS Core/CDM (polling of all
network elements) of the selected NE container via theResynchronize Data context
menu.
3. When re-synchronizing data you can choose if you want to load all new data from the
network element into the TNMS Core/CDM database or if you want to update differing
data only.
- Click Resynchronize to realign the database with the current data of network
element(s)/subnetwork(s).
- Click Reinitialize to delete the current data of network element(s)/subnetwork(s)
from the database and to transfer and accept all data from network
element(s)/subnetwork(s).
143
Netwo rk elements
Connecting/disconnecting a network element to/from TNMS Core/CDM
Select the network element in any view of the TNMS Client.
Connectin g a network element to TNMS Core/CDM:

Usually the DCN channel automatically tries to reconnect network elements (retry interval).
Nevertheless, if a network element is not connected to TNMS Core/CDM (because of
reconfiguration, for example) you can connect it via the Ac cess Cont rol -> Connect
context menu. Resynchronization with the TNMS Core/CDM database takes place.
Disco nnecti ng a network element from TNMS Core/CDM:

If, for example, you wish to prevent the numerous alarms from a network element notifying
you about known problems, you can disconnect the network element from TNMS
Core/CDM.
Use the Access Control -> Disconnect context menu of the network element.
Note:
In the DCN Compon ents tree view, network elements can be connected to the TNMS
NetServer or disconnected from it. For MSN, this is the only possibility because, the MSN
GUI does not provide a connection function.
144
Client functions
Context menus on t he Network Plan

In TNMS Client, the contents of each context menu depend on the mode set
(Surveillance, Network Editor or Services).
Click with the right mouse button on an object that you need for a configuration or for which
you require information, etc.
145
Controlling write access to a network element

The write access state of a network element is reflected by the write access state attribute
which is displayed by a icon in the NE info bar on the Network Plan and which may have
the following values:
Unknown It is not known whether there is an operating station

or local craft terminal connected to this network
element.
No write access There is no operating system or local craft terminal
with write access connected to this network element.
External OS/LCT An external operating system or local craft terminal
has write access to this network element. Typically
only one element manager is allowed to have write
access by the network element.
This TNMS Write access to this network element is captured by
the TNMS Core/CDM internal network element
controller.
EM of this TNMS Write access to this network element is captured by
an internal EM application at a TNMS Client.
EM of this TNMS and Both the network element controller and the element
NEC manager have write access.
No write access and There is no operating system or local craft terminal,
External Access only External write access.
This TNMS and External An external operating system or local craft terminal
Access has write access. The access is captured by the
TNMS Core/CDM internal network element
controller.
This TNMS, EM of this All the network element controller, the element
TNMS and External manager, and external OS/LCT have write access.
Access
There may also be any number of element managers connected to this network element
with read access. This is not reflected either by this or any other state attribute.
If several TNMS Clients are installed, the TNMS Core/CDM Server avoids concurrent write
access. Objects accessible by TNMS Clients have exclusive write access.
In the TNMS Cli ent you can control the write access to a network element using the
Ac ces s Control context menu of a network element in the tree view or the Network Plan
view. Depending on the initial write access state of the network element you can choose
between the following menus:
Ac ces s Control -> Disconnect
Ac ces s Control -> Request Write Access
Ac ces s Control -> Enforce Write Access
Ac ces s Control -> Release Write Acc ess
In any case you should be aware of the fact that some commands might fail if TNMS
Core/CDM does not have write access to a network element in the following situations:
146
Client functions
a) Creating a service would result in an unprovisioned service a cross connection cannot

be created for this service because write access to the appropriate network element is
not available. You have the opportunity to activate this service once write access to
this network element has been requested/enforced.
b) Creating a performance log might fail, if performance measurement points could not be
activated for a network element without write access. This may result in performance
log that does not contain all the measurement data you require.
c) Changing alarm suppressions.
147
Creating a DCN status list

The purpose of the functions Create DCN Status Lis t, Create Synchronization Data List
and Create Remote Invento ry Li st is to generate an XML file with the NE list of
information, making it available for further processing via external tools. TNMS client
requests the list of information of individual NE or all NEs of a container.
The following description shows how to create a DCN Status Lis t, a Synchronization
Data Lis t or a Remote Inventory L ist :
1. In TNMS Core/CDM, switch to the Network Editor mode.
2. Right click the NE or NE container and depending on the desired list, click one of the
following items of the context menu:
- Create DCN Status List
- Create Sync Data List
- Create Remote Inventory List
This opens the corresponding window of the NE or container.
3. Select the destination where the list is to be saved via the provided radio button.
This can be one of the following:
Server - In this case the folder is selected by default C:\Program
Files\Siemens\TNMS\data\<…>
Client - In this case, specify the folder directly or via the Browse button.
4. Select whether to Notify on completion of DCN Status List request even if this
window is closed via the provided check box. This option is only available in the
Client destination.
A progress bar is shown and this process may take some minutes to complete.
The results are saved as *.xml files which can be viewed in Internet Explorer in the
selected directory.
To schedule the creation of NEs lists of information click theSchedule button.
Notes:
When requesting the list from the context menu of a NE container, an *.xml file is
generated for each NE. If no inventory data is available for a NE, the *.xml file remains
empty apart from the file header.
Important: Some network elements do not support all of the entries possible with this
TNMS function!
See also:
Creating a Scheduled DCN status list
List contents
148
Client functions
Creatin g a scheduled DCN status l ist

This description applies to the DCN Status List Scheduled window, Synchronization
Data List Scheduled window and Remote Inventory List Scheduled window.
These windows allow you to schedule the creation of NEs lists of information, i.e. provides
means to automate the creation of several NEs lists of information distributed in time. It is
possible to specify the next export date/time and its update frequency.
You can open these windows via the following:
TNMS Client -> NE/NE cont ainer context menu -> Create DCN Status Li st ->
Scheduled toolbar button
TNMS Client -> NE/NE cont ainer context menu -> Create Synchronization Data List ->
TNMS Client -> NE/NE cont ainer context menu -> Create Remote Inventor y Lis t ->
The scheduler is configured to an NE or an NE container. The results are saved as XML

files which are located in the selected directory.
When configured to an NE container, the scheduler list configuration is replicated
individually to all the NEs and NEs of the sub-containers, i.e. for each NE an individual
XML file is generated.
Scheduled List Act ivation

- Enable Scheduling
Activates the scheduling export of the NE list of information.
- Period of Export
Displays the period between consecutive scheduled exports.
- Next Export
Displays the time and date in which the next scheduled export will take place.
- Destination Folder f or Scheduled Export
Displays the folder where to save the XML file with the NE list of information.
Note:
Folders available through the Browse button are the folders available in TNMS Client.
Ensure that the TNMS Server machine has access to the destination folder that you
are configuring.
Click Apply to save the changes.
See also:
List contents
149
List Contents
Content of the Data Files

The Data File consists of two parts, General Part and Specific Part. The TNMS server is
responsible for filling the general part of the file whereas the related NEC is responsible for
providing the specific part to TNMS server, so that the TNMS server can fill the Data file.
The following table belongs to the General Part of the Data file:
ID Name The ID Name is the unique identifier of the NE.
NE Name The NE Name is the supplier’s name of the NE.
NE Type The NE Type is the type of the NE.
NE The location of the NE (as component within the TNMS-Core/CDM) is the
Location own location (postal address or the geographical co-ordinates with the X-
Position and Y-Position) or any other appropriate information delivered by
the responsible NEC.
NE The address is the usually the NSAP-Address or the TCP/IP address of the
Address NE.
The following tables belong to the Specific Part:
The General Table includes all data presented within one line for each available OSI-
stack. Most of the supported NEs provide only one stack.
Notation of OSI-stack Each OSI-Stack is uniquely identified.
If only one stack is available the value
of this entry is ‘NE’. This holds also for
the OSI-stack of the MSCU card. The
value for any OSI-stack of a DPS card
is ‘DPS’ with additional information
e.g., shelf and slot. An example could
be ‘DPS 1/18’ that is DPS card in
shelf 1 and slot 18.
NSAP-Address
MAC-Address The MAC-address is given if
available. It may be omitted if a NE
does not provide a MAC address via
its interface.
L1- or L2-Routing This entry returns weather L1- or L2-
routing is active. This parameter is
mandatory but it is not available for
the OSI-stack of the MSCU card of
SXA/SXD.
Retransmission Timer (s) Layer 4 Timers - The values for the
Retransmission Counter timer parameters are given using the
same unit (of measurement). These
Inactivity timer or parameters are mandatory but they
Time out window timer are not available for the OSI-stack of
the DPS cards of SXA/SXD.
Additional Manual Areas This entry is optional and is used in
order to prevent interoperability
problems or misconfigurations on
intermediate systems.
150
Client functions
Maximum Area Address parameter This entry is optional and is used in

order to prevent interoperability
problems or misconfigurations on
intermediate systems.
The Channel Table holds the status and if appropriate the assigned SDH-Interface for
each DCC channel and the Q-port. Since there are up to 32 DCC channel per NE it is
useful to provide it in a separate table. Each entry of the table holds the following
parameters if applicable:
DCC Channel No / Q-Port This entry identifies either a DCC

Channel by its number or the Q-Port by
its name.
Operational State The Operational State related to the
DCC Channel or the Q-Port is given by
the state enabled or disabled. This is
the operational state related to the
Schuster stack, which is common for
QST and QD2 NEs.
Adjacency State The Adjacency State related to the
the state enabled or disabled.
Interface Type The Interface Type related to the DCC
Channel or the Q-Port is given by
Network or User.
Metric Represents the metric related to the
DCC Channel or the Q-Port.
SDH Interface The SDH Interface related to the DCC
Channel or the Q-Port is given either by
DCCm, DCCr or not applicable. Not
applicable is set if there is no SDH
Interface.
WDM Interface The WDM Interface belongs to the
OTS/OMS layer, is related to the DCC
Channel or the Q-Port is given by
DCCOo, DCCMo or not applicable. Not
applicable is set if there is no WDM
Interface.
OTN Interface The OTN Interface belongs to the
ODU/OTU layer and is related to the
one of gcc0, gcc1, gcc2 or not
applicable. Not applicable is set if there
is no OTN Interface.
Port Location This parameter gives information about
the port used in equipment format
(subrack, slot and port number as given
at the related (Q-) interface for the
given channel. The equipment format is
subrack-slot-port, e.g., 1-3-5.
The Static Routing Table collects all static routing information related to DCC channels
each shown as a single entry. The static routing information is all RAPs. Each RAP
consists of the following parameters:
151
Interface This is the interface to which the RAP is

associated with.
Address Prefix Address information.
NSAP Address This is the target MAC address, if the
interface is LAN.
Operational State The Operational state indicates
whether the RAP is active.
Default Metric This indicates the metric for the path
and may be a value from the range
0...63.
Default Metric Type The value range may be internal or
external.
Mapping Type The value is ‘explicit’, if the interface is
‘LAN’.
Notes: The parameter ‘Operational
State’ and ‘Mapping Type’ are used for
monitoring at the LAN and are only
available at the DCP (Schuster-) Stack.
The Marben Stack does not offer such
parameters. Currently the Marben
Stack is available in optical NEs.
The Adjacencies Table for an NE are the set of DCN neighbors that are directly reachable
via P2P (DCC, SDH Overhead, WDM Overhead) or via broadcast linkage (Ethernet). This
table holds level1 and level 2 adjacencies. There is a single entry for each adjacency in the
adjacencies table. Each entry has the following parameter:
AdjacencyId Unique ID to identify the adjacency.

Neighbour SNPA Address The Neighbour SNPA Address is
only available for Marben Stack in
WDM systems.
Neighbour System Type The Neighbour System Type Id is
one of unknown, endSystem,
intermediateSystem,
l1IntermediateSystem or
l2IntermediateSystem.
Neighbour System Ids For Intermediate system neighbours:
Contains the single of the
neighbouring Intermediate system
obtained from the Source ID field of
the neighbour IIH PDU.
For End system neighbours:
Contains the set of system ID(2) of a
neighbour End system.
Linkage Id This parameter holds the linkage Id
of the related linkage. All linkages of
the NE can be found in the linkage
table. The linkage Id given is the
same as the related entry in the
linkage table.
Note: For QST there is only one
possible linkage for Ethernet.
152
Client functions
The Destination Systems Table for an NE are the set of reachable systems within the
same area that can be reached. There is at least a single entry for each reachable system
in the destination system table. Each entry has the following parameters:
Network Entity Title The NSAP address of the destination

system related to the entry of the
destination system table.
Default Metric Path Cost The sum of costs to reach the given
destination system for level 1. The
value is between 0 and 1023.
Default Metric Output Adjacencies This is the set of Adjacency (or
Reachable Address) identifiers
representing the forwarding decisions
based upon the default metric for the
destination.
Default Metric SNPA Adjacencies This is the SNPA address belonging to
this destination. The Default Metric
SNPA Adjacencies are only available
for Marben Stack in WDM systems.
The Destination Area Table contains all areas that are reachable by level 2 systems. The
destination areas table shows all destination areas that can be reached from this level 2
NE. Note: This table exists only for level 2 NEs. There is a single entry for each destination
area in the destination areas table. Each entry has the following parameters:
Address Prefix Adjacency Indicates an area address of a

destination area. This octet string has a
minimum length of 1 and maximum
length of 20 characters.
Default Metric Path Cost This is the sum of costs to reach the
given destination area for level 2. The
value is between 0 and 1023.
Default Metric Output Adjacencies This is the set of Adjacency (or
Reachable Address) identifiers
representing the forwarding decisions
based upon the default metric for the
destination.
Default Metric SNPA Adjacencies This is the SNPA address belonging to
this destination. The Default Metric
SNPA Adjacencies is only available for
Marben Stack in WDM systems.
The Link age Table shows all linkages. The following parameters are supported:
Linkage Id This is the identifier for the linkage.
Rejected Adjacency The Rejected Adjacency is
generated when an attempt to
create a new adjacency is rejected
because of a lack of resources (Q3).
When a new adjacency cannot
created because of a lack of
resources, the value of this attribute
is increased (QST).
153
Version Skew The Version Skew is generated

when an attempt to initialize with an
adjacent system fails as a result of
the versions of the protocol is not
compatible.
Id Field Length Mismatch The Id Field Length Mismatch is
generated when a PDU is received
with a different value for ID field
length to that of the receiving
Intermediate system.
Maximum Area Addresses Mismatch The Maximum Area Addresses
Mismatch is generated when a PDU
is received with a different value for
maximumAreaAddresses from that
of the receiving Intermediate
system.
Area Mismatches The Area Mismatches is generated
when an attempt to initialize with an
adjacent system fails as a result of
two level 1 ISS not sharing any area
addresses in common.
Linkage State This attribute shows whether the
mcfLinkage is enabled or disabled.
This attribute is not available for
Marben Stack.
The OSC Table shows additional parameters only valid for OSC (Optical Supervisory
Channel). The table may be omitted if a NE does not support an OSC. For each OSC laser
there is a separate entry. The following Parameters for each entry are supported:
OSC Laser Address This parameter identifies the OSC

laser within the NE. If there is only one
OSC parameter within the NE the
parameter may be omitted. If there is
only one OSC laser per card the
address may be given by e.g.,
subracknumber and slotnumber. If
there is a card with more than one
OSC laser the address must identify
each OSC laser e.g. by subrack
number, slot number and OSC laser
number.
Laser Enabled State The attribute laser enabled state
shows if the related OSC laser has
been active (running) or not at the time
of request. The values are ‘enabled’
for running and ‘disabled’ otherwise. If
the parameter cannot retrieved from
the NE it may be omitted.
Laser Current The parameter indicates the current at
the time of request. The parameter in
given in milliAmp. If the parameter
cannot retrieved from the NE it may be
omitted.
154
Client functions
The Inventory obj ects show the smallest replaceable unit for service purpose. The
inventory objects are generally hard and siftware modules of the supported NE:
PID Shows the complete Product

Identification Data
Subrack Hardware data
Card Hardware data / software data
Controller card Hardware data / software data.
The controller card is a special case of
a card. As software data the active and
inactive APS label are shown.
Exception: If the SMA1K series has
only one card the software running on
this card is addressed.
Port Hardware data.
This holds only for plug-in units on
subequipped cards.
If a port label is part of a card label,
this port label is covered by the PID of
the card label. No extra PID is created
for such ports. This holds for hiT 7070
/ hiT 7050 V1.0
Backplane Hardware data.
The backplane label (e.g. from SMA1K
and from SMA1K-cp NEs) is always
treated as information from a subrack.
A Backplane is always indicated with
subracknumber “B”.
Powersupply Only information of the attribute
redundantPowerSupply (Siemens-
WDM) or powerSupplyDuplication
(Siemens-SDH) or a similar attribute
mapped to the set {NotApplicable,
Enabled, Disabled} is available. ‘Not
applicable‘ is used if the attribute is not
existent.
See also:
Creating a scheduled DCN status list
155
Deleting network elements

In TNMS Core/CDM Client, network elements can be deleted from the Network Map only.
They will not be deleted from the TNMS database and will stay available in the DCN
Components tree.
Deleting a network element from the TNMS database must be done via DCN Management
in TNMS SysAdmin. Further information is provided in the SysAdmin online help.
To delete a network element from the Network Map proceed as follows:

1. Delete all performance logs, especially performance logs related to services (in the
Performance Logs list window).
2. Delete all paths and services using the network element ( in Service Mode).
3. Delete the port connections of this network element (in Network Editor Mode).
4. Switch to the Network Editor mode, select the desired NE in the Network Map and
open the context menu -> Delete. The network element will be removed from the
Network Map.
See also:
Viewing logs
Deleting a service
Deleting a path
Editing/deleting a port connection.
156
Client functions
Displaying alarm redirections for a network element

Switch to Surveillance or Services mode.
Use the Alarms -> Redirect Alarms... context menu of a network element to open the
Alarm Redirections for NE <xy> window.
If you have already configured alarm redirections for the relevant network element, the
following information is displayed:
- Probable Cause
Original probable cause = one of the possible TIF alarms of the network element the
alarms of which are redirected.
- Map to Probable Cause
System-defined or user-defined probable cause which contains more detailed
information than the original probable cause. More information is provided in the
SysAdmin online help.
- Map to NE
Target network element to which the alarm type in question is to be redirected.
- Map to Object Type
System-defined or user-defined object type = name of a location where an alarm may
occur. More information on redefining these objects is provided in the SysAdmin
online help.
- Map to Location
Numeric values are displayed here for Shelf, Slot, Container and Object providing
information where the device is located.
Using the buttons at the top of the window you can

- Modify the configuration of a selected alarm redirection item.
- Ad d (create) a further alarm redirection.
- Delete a selected alarm redirection.
See also:
Redirecting alarms for a network element or a subnetwork.
157
Displaying and processing alarms of a network element

In Network Editor mode of the TNMS Client you can select a network element from the
DCN Compon ents tree and, using the context menu, perform actions relating to alarms.
More information is provided under Menu entries for alarms.
In Surveillance and Services mode you can perform these alarm-related actions in the:
- Network Plan
- DCN Compon ents tree
- Network Elements tree
158
Client functions
Displaying the properties of network elements

The properties of network elements can be displayed as follows:
In the TNMS Client select a network element in the network plan, in theNetwork
Elements tree or in the DCN Channels tree. In the context menu choose -> Properties….
159
Exclude NE from rou ting

The Exclude NEs from routing window opens when clicking the option Exclusion Of
NEs From Autorouti ng in the Routing Options window.
The NEs, which you want to exclude from automatic routing must be dragged into the
window. Click the Apply button in the toolbar and the NEs will be excluded from
autorouting.
Another possibility to exclude an NE from routing is to set its ADMIN state to locked. This
can be done via the context menu in the Network Plan or Network Tree with the option
Lock for Routing.
See also:
Routing options
Locking/unlocking a network element
160
Client functions
File transfer
For a few network elements (e.g. SMA 1/4) the File Transfer window can be opened via
TNMS Client -> network element (context menu)-> File Transfer... This offers the option
of transferring files from/to the network element.
The lower area of the window shows you the file transfer messages.
Transfer to network element:

In the upper area of the window you are shown the file system of your client system. Select
the files to be transferred and press the button with the arrow pointing towards the network
element.
Transfer from network element:

In the lower area of the window you are shown the files of the network element from which
you called the File Transfer window. Select the files to be transferred and press the button
with the arrow pointing away from the network element.
If you are going to perform a file transfer between a network element and your local system
you can create a new directory on the target medium.
Specify the name of the new directory to which you wish to transfer data.
You can use the Create or Delete actions to create or delete files and directories on the
client system. Use Rename to change the name of a file.
Using Delete you can also delete files on the network element itself.
Note:
The equivalent functionality to file transfer is offered by the element manager for PDH
network elements.
161
Finding network elements

To find a specific network element, use e.g. TNMS Client -> View -> Find... or use the
button Find from the toolbar. The DCN Objects window opens where you can search for
specific NEs.
It is also possible to use the command Locali ze NE in the context menus of many lists and
logs.
162
Client functions
General network element properties

General settings can be configured and modified for network elements in theGeneral
property page provided in the <DCN NE Object> window.
Note: The General page (except the User Text (..) fields and the Description field) can
only be modified under TNMS SysAdmi n!

General ID Name A unique name for the NE is displayed in this field.
NE Name The name of the NE reported by the NE controller is
shown in this field.
NE Type The type of NE is displayed in this field.
NE Location The location of the NE reported by the NE controller is
shown in this field.
User Text (1) A user-defined name can be entered in this field.
User Text (2) A user-defined name can be entered in this field.
Write Access by The write access state reported by the NE controller
is displayed in this field.
Admi n State The current admin state, undefined, locked or
unlocked, is shown in this field.
this field.
Exit the window by pressing Close. For more information, press Help.
163
Locking/unlock ing a network element

In order to exclude an unlocked network element or a port connection from routing, switch
to Services mode. Select the NE you want to exclude in the Network Plan and open the
context menu -> Lock for Routing. The entry Lock for Routing appears with a red
prohibited symbol which also appears over the NE icon.
In order to include a locked network element or a port connection in routing, switch to
Services mode. Select the NE you want to include in the Network Plan and open the
context menu -> Lock for Routing. The entry Lock for Routing is not ticked (default).
See also:
Icons: Network Plan
164
Client functions
Modifying the properties of a subnetwork

In TNMS Core/CDM, complete the following steps to modify the properties of a
subnetwork.
1. Open the context menu of the title bar of the Network Elements tree ->Northbound
Subnetwork Properties…
The Northbound Subnetwork Properties window contains the following information:

- Subnetwork Name
Edit the label of the subnetwork that is to be displayed in the second line of the
subnetwork icon on the TNMS CDM Network Plan.
- Subnetwork Type
Display the type of the subnetwork.This information is set when creating a subnetwork
via TNMS SysAdmin.
- Subnetwork L ocation
Edit the location of the subnetwork.
165
NE distinctions
This chapter contains some important notes for NEs used under TNMS Core/CDM, other
NE specific characteristics may be described in the relevant topics:
Note: usually NE specific characteristics are not part of the TNMS documentation!
hiT7050 / hiT 7070:

• TP indices of GFP-Group-CTPs in list views may appear as not unique (contrary
to tree views). Example: The same location might appear for a GFP-Group-CTP
01 related to a VC3-TTP as well as for a GFP-Group-CTP 01 related to e.g. VC4-
4v GTTP within the same module.
• Only hiT7050: TP indices of VC3-TTPs on ETH Cards do not take into account
the position within its VC4-TTP. Example: An object appearing as VC3-TTP 08
has to be interpreted as VC3-TTP 02.02.
• Only hiT7070: TNMS Core/CDM NEC may report PMP states for TU12, TU3-
CTPs on SF10G Card as "undefined".
In the uploadVcdb telegram (which should contain the attribute in which the NEC
bases the state of a PMP) not all QST objects contained this attribute. This is due
to a change in the NE SW regarding NE833 of the MultiNE database. For the
QST objects that don't have this attribute, it means that it doesn't exist a
Performance Unit created in the NE.
Ulaf+:
For the PDH NE Ulaf+ three types of signalling can be distinguished. All data are packed
into time slots (1 TS = 64 kbit/s), the maximum numbers of TS are 32 per signal (TS0 –
TS31). TS0 is always used for synchronisation. TS1 – TS31 can be used for transfer of
data. For signalling TS16 is used.
Note: As a modern PDH NE, the Ulaf+ is managed by the SNMP channel, not by the PDH
channel.
Via the Ulaf+LCT the TS for data transfer and the signalling is configured.
Exceptions : For add/drop operation, STU and STU2, if the combo boxTime Slot 16 is
used for Data, is selected, then 1. – 3. do not apply.
1. No Signalling (TS16 with no signalling, no data transfer):

TS >= 15, 1 TS must be subtracted from the computed bandwidth
TS <= 14, no correction of the bandwidth is necessary
2. Normal Signalling (TS16 is used for signalling, no data transfer):

TS <= 14, no correction of the bandwidth is necessary
3. Fast Signalling (TS16 + TS31 are used for signalling, no data transfer):
TS <= 14, 1 TS must be subtracted from the computed bandwidth
TS = 16 used for data transfer (settings are made in the LCT, only for STU and STU2),
1 TS must be subtracted from the computed bandwidth
Event forwarding feature as no function for FSP500.
166
Client functions
Port types
GUI Label Descript ion
Analog 64kbps port for POTS services

DATA 64k 64kbps port for Data services
DATA n64k n x 64kbps port for Data services with n = 1..32
DATA Sub 64k port for Data sub 64kbps bit rates
E11-TTP 1.5 Mbps PDH port
E12-TTP 2 Mbps PDH port
E12-TTP (HDSL) 2 Mbps PDH port (HDSL)
ETH1000-TTP 1000 Mbps Gigabit Ethernet port
ETH100-TTP 100 Mbps Fast Ethernet port
ETH10-TTP 10 Mbps Ethernet port
GPI-TTP Generic Physical Interface (e.g. optical tributary port at DWDM
multiplexer)
ISDN Access ISDN Access port
OTS-TTP Optical Transmission Section port (DWDM section)
SPI-OS16-TTP Optical STM16 port (SPI-OS = synchronous physical interface /
optical section)
SPI-ES-TTP Electrical STM1 port (SPI-ES = synchronous physical interface /
electrical section)
SPI-OS1-TTP Optical STM1 port
SPI-RadioSTM1-TTP Radio STM1 port
SPI-ES4-TTP Electrical STM4 port
SPI-RadioSTM4-TTP Radio STM4 port
167
Resynchronize data
When re-synchronizing data you can choose if you want to load all new data from the
selected object into the TNMS Core/CDM (Reinitialize) or if you want to update modified
or new data only (Resynchronize).
See also:
Resynchronizing the data of a DCN channel
Resynchronizing the data of an NE container
168
Client functions
Selecting network elements

In the TNMS Client a network element can be selected in the Network Management View
by clicking on the network element with the left mouse button:
- in the Network Plan
- in the Network Elements tree view
- in the DCN Compon ents tree view
Selecting in the Network Plan view also selects the appropriate network element in the
Network Elements tree view and in the DCN Channels view.
Selecting in the Network Elements tree view also selects the appropriate network element
in the Network Plan view.
169
Starting the network element manager

1. Select a network element in the TNMS Client, e.g. in the Network Map, in the DCN
Components tree or in the Network Elements tree.
2. Use the Start Element Manager... context menu (depending on the network element,
the menu entry may differ from the entry above, e.g. WaveLine/FSP Start if installed,
etc.) to start the LCT application of the network element.
The full functionality of this application is now available, depending upon your user
class. You may need to consult the Help file and documentation.
Alternatively, double-click the network element icon in the Network Map.
Notes:
- The network element manager application must be installed together with the
TNMS Core/CDM Client.
- For SSU2000e e.g. the SynCraft application will be used as a specific element
manager. It is not sufficient to enter the file runSynCraftNT2K.bat in the property
page. To make sure that the correct working directory is used, the following
information must be added at the beginning of the filerunSynCraftNT2K.bat,
otherwise a wrong working directory will be used.
1st line: "D:" -> where D is the local disk or network drive, on which
SynCraft is
installed:
2nd line: "cd D:\Programme\Datum\SynCraft"
-> directory containing the file runSynCraftNT2K.bat.
An X Server application is used to access the TNMS SX GUI.
170
Client functions
Suppressing alarms and events for a network element or a subn etwork

In the TNMS Client it is possible to modify alarm/event suppression for network elements.
1. Switch to the Surveillance or Services mode.
2. Select a network element.
3. Use the following context menu:
Event mask -> Disable all alarms of unused TPs :
All alarms of all termination points of the network element that are not cross-connected
for the relevant traffic direction and not used by paths are suppressed. This means:
termination points that are cross-connected (bidirectional) are ignored.
Termination points that are cross connected (unidirectional) as data source alarms of
the sending direction are not changed.
Termination points that are cross connected (unidirectional) as data sink alarms of the
receiving direction are not changed. All other alarms are suppressed.
Note:
Suppressing alarms of unused TPs makes sense from time to time. Doing this has no
impact on services which will be switched afterwards because, when creating services
the required alarms will be activated again.
The event mask can also be updated as follows:

- Event mask -> Refresh Alarm Mask:
Selecting this command synchronizes the alarm mask for the NE/subnetwork in
question (incl. all termination points) with the requested alarm mask configured for the
relevant path.
171
Paths
Ac tiv ati ng /Deactivat in g a p ath
Ac ti vating a path (for a single path or a path co ntainer):
Activating a path means that the cross connections will be created.
You can activate all paths of a path container by selecting the path container in the
Subscribers and Services tree and then choosing the context menu Ac ti vate. The RCS
changes from not active to active.
Deactivating a path (for a single path or path container):

Deactivating a path means that cross connections will be deleted.
You can deactivate all paths of a path container by selecting the path container in the
Subscribers and Services and then choosing the context menu Deactivate. The RCS
changes from active to not active.
Overview of t he Path Creation States:
Creation States Descript ion

Active The path is routed and the actual route is created in the NML
database (RCS) or is completely created in the network (ACS).
Not active The path is defined and has a well-defined (checked) required
route, i.e. the paths route is stored and allocated in the NWL and
successfully checked against its topology (SNC type and
endpoints). In this state the required route matches to the required
path topology.
Not routed The path exists with well-defined (checked) topology, i.e., the
required path topology is checked and stored.
Unmanaged The path exists in the network but has never been created as a
managed path by the operator. A unmanaged path will be split,
merged or deleted spontaneously, without operator confirmation
after changes of the network resources.
Under test The path is activated but a test configuration has been set by
changing at least one cross connection or port to loop-back.
RCS: the test configuration has been requested.
ACS: the test configuration is actually created.
In Deletion The path is being deleted.
Undefined The path is created, any attributes may be stored, but no
assumption about the object state can be made.
172
Client functions
Adopti ng the actual rout e

In order to adopt a new route of a path without changing the topology, e.g. because of a
route mismatch in case of network augmentation, select a path in theSubscriber and
Services tree, open the context menu and select Adopt Ac tual Route.
An analysis of the actual connections in the network between the defined topology
endpoints of the path will be performed. If these connections form a route matching the
topology endpoints, then the connections are adopted as required route for the path (i.e.
route elements between path endpoints may change). The results will be displayed inPath
Properties window and are to be applied by the user before the new route is stored.
If no route is found (e.g. because of missing cross connections in a network element or the
result of the network analysis does not match the defined topology anymore), the user is
prompted to choose between the following options; their meanings are explained in the
window.
- Close detected gap
- Adopt Topology
- Re-Route
- Restore/Activate
Note:
The Adopt A ct ual Route command is not available if the TNMS Network Analyzer mode
is set to disabled.
See also:
Service / Path Properties: routing
173
Adopti ng the actual to polo gy

In order to adopt the network topology of a path, e.g. in case of a topology mismatch
(problem indication in Servi ce / Path Prop erties window "The actual route extends the
required route"),
1. Select a path in the Subscriber and Services tree.
2. Open the context menu and select Adopt A ct ual Topo logy .
A local analysis for each topology endpoint, based on the actual connections in the
network will be performed. The results will be displayed inPath Properties window
and are to be applied by the user before the modified topology information (e.g.
changed endpoint) is stored.
Note:
Ad opt A ct ual Topol ogy is not available if the TNMS Network Analyzer mode is set to
disabled.
See also:
174
Client functions
Auto matic Analyzer Mod e

Via the context menu in the Unmanaged Path tree, you can select the menu entry
Auto matic Analyzer Mod e.
The following modes are possible:
- Automatic:
The unmanaged path tree is continuously updated. Changes in the network result in
appropriate changes in the unmanaged path tree.
- Manual:
Only the states of existing unmanaged paths are updated. Neither the route of existing
paths is not updated nor new paths are automatically created.
- Disabled:
The unmanaged path tree and the tree contained in it will not be updated if changes in
the network occur.
By default, the Manual A nalyzer Mode is turned on. When activated, TNMS checks and
refreshes the Unmanaged Path tree for existing unmanaged paths.
175
Auto matic Routi ng Preferenc es

This topic contains a general description on the built-in preferences of the Automatic
Router, also in consideration of the newly introduced floating TPs. The preferences of the
Automatic Router are as follows:
1. By default the Automatic Router of TNMS Core/CDM prefers the cheapest or shortest
path based on the cost factors, which are defined on the traversed port connections: In
this case the path route avoids floating TPs. For hiT 7070 this means that a VC12 path
will not be routed via the lower order switching matrix.
Note: this preference will be in effect if there are no server trails connected to the
floating TPs or if using these server trails would make the path more expensive.
2. The Automatic Router prefers to route as close as possible to the layer, which is
defined for the path being routed.
Note: in combination with floating TPs this preference is in effect as soon as there is a
server trail connected to the floating TPs.
3. The Automatic Router prefers to use existing server trails rather than creating new
trails. Only if using these existing trails would lead to a higher cost for the path, then
new trails are created.
Usual calculation of co sts for server trails:

– When routing with least hops, every server trail is regarded as one hop.
– When routing with cost factors, the cost of a server trail is the sum of costs of all
traversed port connections. The cost of the server trail is automatically updated
when the port connection cost is changed.
Subsumption:
It is completely within the responsibility of the network operator to decide on multi-hop VC4
server trails when he creates a multi-hop LO path. As well known, VC4 server trails are a
powerful element in network optimization. Their use cannot be decided on a per network
element basis.
See also:
Routing options
176
Client functions
Choose link connection

During manual routing the Choose Link Connection window is used for choosing the link
connections to be used by the paths. This window is useful if there is more than one
possible link connection at the TP of the currently selected cross connection. Possible
scenarios are:
- At the port of the selected TP there exist two port connections in opposite
directions
- There exists a server path reference with the current ACSnot routed, e.g. because
a resource is missing in the server path. The user can recognize this and and can
use the additional existing port connection references at the selected TP
- Manual routing of path fragments at a group TP
- Manual routing using floating TPs
You open the window e.g. from the Connection As sistant by pressing the Ctrl key and
clicking the green navigation button with the left mouse tab.
For an explanation of the icons used in this window please see the link below.
See also:
Icons: Link connection
Floating TPs
Floating TPS: Behaviour of the Connection Assistant
177
The Connection As sistant window is primarily used in TNMS Core/CDM for manual path
creation and hybrid routing. In addition, it can be used e.g. for modifying cross connections
of a path. The window allows to define the type of connection of a path or SNC, the
termination points and path protection.
The Connection As sistant window is invoked from the Path Wizard - Define Topolog y
window by clicking the black arrow right of the Next button and selecting the Route
Manually... entry.
Bear in mind that changes only take effect if the Modify button is clicked afterwards.
- Port / TP A (1)
Shows the start NE which was dragged and dropped into this field with start port / TP.
On the left, the Exit / Entry points for this NE can be defined through a button.
Filtering is also possible; see filtering description below. For the icons available here
please see Icons: Port Connections, Path Wizard and Connection Assistant..
Note: For information on the usage of floating TPs, please refer to the link list at the
end of the topic.
- Port / TP Z (1)
Shows the end NE which was dragged and dropped into this field with end port / TP.
On the right, the Exit / Entry points for this NE can be defined through a button.
please see Icons: Port Connections, Path Wizard and Connection Assistant
end of the topic.
- <Connection Templates>
Contains templates for the connection type. See: Icons: Port Connections, Path Wizard
and Connection Assistant
- Port / TP A (2)
Used for protection only. Shows the start NE for protection which was dragged and
dropped into this field with start port / TP. On the left, the Exit / Entry points for this NE
can be defined through a button.
please see Icons: Port Connections, Path Wizard and Connection Assistant
end of the topic.
- Port / TP Z (2)
Used for protection only. Shows the end NE for protection which was dragged and
dropped into this field with end port / TP. On the right, the Exit / Entry points for this NE
can be defined through a button.
please see Icons: Port Connections, Path Wizard and Connection Assistant.
end of the topic.
Navigation Button :
- The navigation button is next to the selection fields for the ports/TPs. The button
allows you to move to the next network element that is link-connected to that port.
- When you click the navigation button of a TP the Connection As si st ant window is re-
initialized with the contents of the new network element. The navigation button is only
enabled if there is a port connection connected to the selected port and if data of the
cross connection is valid (see Info Area).
- When you click the navigation button of a fragment TP a selection list opens where you
must select a link connection.
178
Client functions
- When the Ctrl key is pressed and the navigation button is selected with the mouse the
Choose Link Connection window opens.
Filtering Descript ion for Port / TP fields:

Each Port / TP field allows filtering using predefined filter criterias. They are displayed as
icons; tooltips show the meaning of icons. The filter criteria are:
- No Filter
No filter will be used.
- Port Connection Filter
The port connection filter will be used.
- Cross Connection Filter
The cross connection filter will be used.
- Operatio nal State Filter
The operational state filter will be used.
- Subscriber Filter
Here the Port / TP Filter window opens with the tab Subscriber .
- Layer Filter
Here the Port / TP Filter window opens with the tab Layer .
- Settings Filter
Here the Port / TP Filter window opens with the tab Settings.
- Bandwidth (n*64Kbit/s)
This selection field only appears below the cross connection type button if both working
TPs with an Nx-count > 1 are selected (usually PDH network elements with n*64Kbit/s
cards).
In the lower area of the Connection Ass istant window the following information is
displayed:
- Info Area
Help on the current operating step is displayed here. Generally this includes hints as to
why specific cross connections could not be created and information on further
procedure.
- Connection
For the currently selected cross connection container the definitions of the cross
connections defined within this container are shown.
- Comment
You can use these two text fields here if you want to enter comments for the
connection; first enter the connection name and then enter your comment on this
connection.
Using the buttons of the Connection Ass istant window you can perform the following
actions:
- Create
Creates a cross connection with the defined parameters with the currently selected
cross connection container. A new connection is created if none is selected.
- Modify
Modifies a selected cross connection.
- Check
Use this button if you are not sure whether resources have been modified by another
operator since you last opened the window or activated theCreate, Modify or
navigation button .
179
- Remove
Removes a selected cross connection from the currently selected cross connection
container.
- Route
Initiates the hybrid routing, either to the Z-end of the defined topology or to the port/TP,
which was selected in the NE previously drawn into the relevant field of the
Connection Ass istant.
See also:
Choose link connection
Creating a path
Floating TPs
Floating TPs: Behaviour of the Connection Assistant
Hybrid routing
Icons: Port Connections, Path Wizard and Connection Assistant
Icons: Routing
NE distinctions
Port and TP filter setting
ToolTips for path creation
Scalable Ethernet Paths d Generic Framing Procedure
180
Client functions
Create/Modif y Grou p TP
The Create/Modify Group TP window enables the creation and modification of virtual
group TPs integrated in the routing process.
The Create/Modify Group TP window is available via context menu of a port supporting
GTPs in port/TP tree. The port/TP tree is available in the Service / Path properties:
Topology window or via the Connection assistant window.
To create a virtual group TP proceed as follows:

1. Open the context menu of the port of the server TP and selectCreate Group TP.
Concatenation Type
2. Select option whether to use LCAS or fixed virtual concatenation (without LCAS).
3. Select layer of the fragments in the Type field.
Avail able/Selected TPs

4. Select the VCx-TTPs from the Avail able TPs list and with the right arrow button insert
them in the Selected TPs list.
The VCx-TTPs inserted in the Selected TPs list are assigned to the GTP/GTTP.
By clicking the Appl y button, you create the desired GTP/GTTP.
Repeat the same procedure in the Z-end of the trail.
To modify a virtual group TP proceed as follows:

The operation to modify a virtual group TP is available for GTTPs with LCAS (GTTP-Ls).
Add VCx-TTPs to a GTTP-L
1. Open the context menu of the GTTP and selectModify Group TP option.
2. Select the VCx-TTPs from the Avail able TPs list and with the right arrow button insert
them in the Selected TPs list
The VCx-TTPs inserted in the Selected TPs list are assigned to the GTP/GTTP.
Remove VCx-TTPs from a GTTP-L
1. Open the context menu of the GTTP and select Modify Group TP option.
2. Select the VCx-TTPs from the Selected TPs list and with the left arrow button remove
them from the list.
After the modification is complete the VCx-TTPs in the Avail able TPs list become
available to be used in other GTP/GTTPs.
By clicking the Appl y button, you apply the modifications to the selected GTP/GTTP.
Remember to repeat the same procedure in the Z-end of the trail.
Note:
The Create Group TP window is restricted to certain NE types.
181
Creating a path container

Depending from where this window is invoked, it can either be used to create a path
container or it simply shows the container properties.
A path container is a folder in which one or more paths can be contained. By default there
exists only the Default Path Container , shown at the top of the Subscribers and
Services tree of the TNMS client.
In order to create a path container:
1. Select a service or a path in the Subscribers and Services tree.
2. Open the context menu with the right mouse tab and selectCreate Path Container…
The Create Con tainer windows opens where you must enter the name for the path
container.
3. Then click Create. You will see the newly created path container in theSubscribers
and Services tree. You can also move a path from one container to another. The
color of the container symbol for such user created path containers is yellow.
Note:
- Other path containers will be created by TNMS Core/CDM if required, e.g. path
containers for SDH, VC4, VC12 will be created below the default path container. The
color of the container symbol for such path containers created by TNMS Core/CDM is
grey.
- The Analyzer Toggler Detecti on Container is created by TNMS Core/CDM when
errors exist in paths being analyzed. Possible reasons are dynamical problems, NEC
errors or configuration errors. If such a path toggler is detected, it will be automatically
moved to the Analyzer Toggler Detecti on Contai ner and therefore it won’t be
analyzed anymore. In this way the system performance remains the same.
182
Client functions
Creatin g a path
In order to create a path, port connections must have been created before. Then complete
the following steps:
1. Switch to Services mode and open the menu bar entry Configuration -> Create
Path… The Path Wizard: properties window is opened.
2. Define the path properties.
3. Click the Next button in the toolbar. The Path Wizard: Define Topolo gy window is
opened.
4. Select the template for the topology type via the button in the center of the window.
For information on the templates see Icons: Port Connections, Path Wizard and
Connection Assistant.
5. If you are working in TNMS Core/CDM, drag and drop the source and destination
NEs from the Network Plan or the Network Elements tree into the corresponding
fields.
6. Set a filter via the filter button.
7. Define the endpoints, i.e. Port/TP A (1) for the source NE and Port/TP Z (1) for the
destination NE.
In case of protection, also define the additional endpoints, i.e. Port/TP A (2) and
Port/TP Z (2).
8. Select the Resilience for your protection via the button.
Note: The resilience is only required as start option for the auto-router, i.e. for end-
to-end protection and for automatic routing the resilience must be defined as
protected. Due to internal computing this parameter will retrospectively always be
shown with its actual value.
9. Click the Add button in the toolbar and the created route elements are displayed in
the list below.
10. Click the arrow next to the Next button and choose between automatic or manual
routing.
Note: It is also possible to create CCs in UNOs automatically using TNMS Client and the
automatic routing feature. The possibility to add/remove a protection/worker to a CC
automatically is available.
Auto matic routin g…

a) In the Path Wizard: routing results window the routed path is displayed.
b) Click the Ac ti vate button in the toolbar.
Manual rout ing…

a) The Connection Ass istant window is opened. Select the template for the
topology type via the button in the center of the window, and define the
endpoints, i.e. Port/TP A (1) and Port/TP Z (1).
In case of protection, also define the additional endpoints, i.e. Port/TP A (2) and
Port/TP Z (2).
b) Navigate via the green arrow button to the next NE and repeat step a) for this
NE.
c) Click the Create button to create the line topology for the NEs.
d) Close the Connection Ass istant.
e) In the Path Wizard: routing results window the routed path is displayed.
f) Click the Acti vate button in the toolbar.
183
Creating a path without a topology:

If you leave out the steps 7. till 11. (see above) by just pressing the button Next in the
Path Wizard: Defin e Topol ogy window, you have to drag the desired NE from the
Network Plan into the Path Wizard: routing results window. The Connection Ass istant
window opens where you can define the route (see above under Manual routing..., steps a)
to d)).
In the Path Wizard: routing results window open the context menu in the graphical area
and open the context menu selecting Route -> Take Topolog y fro m Required Route .
Finally activate the path.
See also :
Automatic Routing Preferences
Creating a service
Path Wizard: define topology
Path Wizard: properties
Path Wizard: routing results
184
Client functions
Deleting a path
When deleting a path, flexible cross connections will be deleted in the NE, and parts of a
path with static CCs will be moved to the Unmanaged Paths tree.
If you want to delete a path from the TNMS databaseincluding its corresponding cross
connections, complete the following steps below. For deletion of paths with disconnected
NEs: A warning is issued and the paths will only be deleted after starting the deletion
process a second time:
1. Select the path to be deleted in the Services & Subscribers tree of the TNMS Client.
2. Open the context menu with the right mouse tab and selectDelete. As a result, the
path is deleted permanently from the database.
If you want to delete a path from the TNMS databasebut keep its corresponding cross
connections, complete the following steps below. In order to keep CCs in the NEs it is
possible to release write access to all concerned NEs and afterwards start the deletion
process two times:
1. Select the path to be deleted in the Services & Subscribers tree of the TNMS Client.
2. Open the context menu with the right mouse tab and selectUnmanage. As a result,
the path is deleted permanently from the database. If there are any cross connections
still in existence, they will be moved to the Unmanaged Paths tree.
Warning:
Although the path or parts of it are moved to the Unmanaged Paths tree, the
unmanaging process might be irreversible!
Note:
When deleting a client path starting at PDH Microshelf of e.g. hiT 7020 2.1, the
corresponding server path (VC4 trail) is not deleted implicitly (even if the check box "Delete
implicit server-paths" is marked in the Confirm Path Deletion pop-up-window). If it is no
longer in use, which is to be checked carefully, you might modify or delete it manually.
185
Disabled Paths
Disabled Paths window is available through TNMS Client -> Fault -> Disabled Paths....
This window shows a table view of all the disabled paths in the network.
The operational state of a path is set to disabled, when the Required Creation State (RCS)
is in the state active or under test and a traffic affecting alarm exists.
The List of Disabled Paths contains the following information:

- Index
Counter for each service.
- Path
Name of the path.
- Service
Name of the service.
- Subscriber
Subscriber to which the service is assigned.
- Layer
Transmission layer (e.g. VC4, MS16).
- Required Bandwidth (Mbps)
Shows the required bandwidth (Mbps) for the path.
- Ac tu al Bandw idth (Mbps )
Shows the actual bandwidth (Mbps) for the path. By default this field is empty.
- Bandwidth State
Displays the actual state of the bandwidth. Possible values are:OK, Mismatch, Trail
Overbooked or Trail Underbooked.
- Direction
Unidirectional or bidirectional.
Operational state is: enabled, disabled or protection disturbed.
- Al arm Mask
Shows the type of alarm suppression applied to the path. Possible values are:Enable
Primary alarms, Enable Secondary alarms at service endpoints and Disable all alarms.
More information is provided under Alarm suppression for a path.
- Operator
Name of the operator who created the service.
Date and time, when the service was created.
- ACS
Actual Creation State. ACS reflects the creation state according the corresponding
infrastructure. ACS is the summary of the ACS of its route elements. Possible values
are: active, not active, not routed or under test.
- RCS
Required Creation State. RCS is set by the path operations and reflects the requested
creation state. Possible values are: active or under test.
- Connection Type
Possible values are e.g. simple, add drop head, add drop tail, double add drop,
unknown.
- Connection Class
Possible values are: Trail, Half-Open SNC, Open SNC, LC/TC (Link or Tandem
connection), Trail And Half Open SNC, Trail And Open SNC or unknown. If all path
edges have the same connection class, this is also the connection class of the path,
else unknown.
186
Client functions
- Admi n State
Administrative state: locked, unlocked or undefined.
- Admi n State Typ e
If the Administrative state is locked, the type can be implicit, explicit or explicit/implicit.
- Next Activation Time
Displays the time in which the activation will take place.
- Next Deactivation Time
Displays the time in which the deactivation will take place.
- #NEs
Number of NEs the path is routed over.
- Endpoints
Description of the endpoints of the path.
- Last Disabled Time
Displays the time in which the path was disabled.
- Server Path
Name of the Server Path used by the path.
- Ac know ledged St ate
Displays the acknowledgement of a port connection. Possible values are:
acknowledged or unacknowledged.
- Ac know ledged B y
Displays who the acknowledgement was performed by.
- Ac know ledge Time (Lo cal Time)
Displays the time in which the acknowledgement took place.
By right-clicking in the list, you can activate a context menu with several functions, e.g.
filter functions and displaying path alarms function.
By activating the context menu and choosing the Column Settings… menu item you can
choose which columns are displayed and their order.
and Icons: Lists.
See Als o
Service / Path properties
187
Handling server paths and client paths

A server path is defined as a path with a high bandwidth that can be used by another path.
Server paths may have unconnected endpoints, i.e. a server path does not have a cross
connection at its endpoint and leads away from a port. A server path provides transport
capacity of layer X to transparently transport one or more client paths of layer Y.
Half open server trails usually have the termination points in different domains managed by
another TNMS Core/CDM system.
A client path is defined as a path with a low bandwidth that is partly routed over a
previously created server path.
Icon Route Element Type
Server path reference
Half open server path reference
Note:
Implicitly created server paths, for which the option "Allow Implicit Deletion" has been set
(this is the default for these kind of paths) will be deleted.
Explicitly created paths used by clients (and thus become server paths) will indeed loose
their "has clients" attribute after deletion of the last managed or unmanaged path, but they
will not be deleted.
See also:
Creating a path
188
Client functions
Hybrid routing
A combination of manual and automatic path creation, also known as partial automatic
routing or hybrid routing, is also possible.
First of all the path topology has to be defined, the endpoints of the path are then shown in
the routing view. Now the Connection As sistant can be opened to define the exact route.
This can be done either manually (step-by-step, i.e. cross connection by cross connection),
partly automatically (= hybrid routing) or automatically.
General Proceeding for Hybrid Routing

For defining the route partly automatically (= hybrid routing) you have to drag the target NE
into one of the enabled TP Z combo boxes of the Connection Ass istant. Now the
Connection Ass istant is be initialized with more than one NE. If the desired endpoint is
selected within the combo box the user is able to press theRoute toolbar button of the
Connection Ass istant for starting the automatic routing between the endpoints defined in
Connection Ass istant.
Note that at the end of an automatic route process the cross connections will not be
created within the network elements automatically. The user has to apply the results for
creating them after the desired route is defined.
Within the Connection Ass istant (opened by the cross connections context menu or by
double clicking on one) the user can extend or modify the found route manually or
automatically again and again.
If you decide during the manual routing process in theConnection As sistant to continue
automatically, you must define the endpoints for a partial route. Simply drag the required
endpoint NE into the enabled TP Z combo box.
If no TP Z endpoint is defined in the Connection Ass istant the automatic router will try to
close from defined TP A to the endpoint as defined by the topology when pressing the
Route button. The Info Area gives some user hints during parameter definitions.
If a TP Z endpoint is defined in the Connection As sistant the automatic router will try to
find a route with the given parameters, i.e. with the defined endpoints when pressing the
Route button.
If a route is found it is merged into the graphical view. If no route could be found the view
will be changed to the Connection As sistant and a message will be displayed in the Info
Area indicating the failure of the partial (hybrid) routing process. In this case change the
parameters for another trial or continue with manual routing.
See also:
Creating a path
189
Listing paths
TNMS Client -> View -> Lists... opens a list window. Clicking on the Paths tab on the
bottom displays the List of Paths window.
You may alternatively access this window via the List of Client Paths... context menu of a
path, List of Paths... context menu of a network element or port connection or theShow
Paths Li st context menu in the Current Alarm Li st .
In these cases the scope is pre-selected correctly and the list is updated immediately.
To change the scope of the list use the Scope Type field to select the kind of filter you
want to set. You may also edit the Scope field to filter the list if required.
Scope Type Descript ion

Global No filter is set.
Using server trail You can move the server trail per drag & drop
from the Subscribers & Services tree.
Using server trail name Enter the server trail name.
Used by path You can move the path per drag & drop from
the Subscribers & Services tree.
Used by path name Enter the path name.
Owned by subscriber You can move the subscriber per drag & drop
from the Subscribers & Services tree.
Owned by subscriber name Enter the subscriber name.
Using port connection Enter the port connection.
Using port connection line Can only be chosen from the context menu.
Using NE You can move the NE per drag & drop from
the Network Elements tree.
Using NE name Enter the NE name.
Alarm Open the alarm list, select an alarm, and open
Show Path Li st via the context menu.
Disabled Paths Shows all disabled paths.
Protection Disturbed Shows all disturbed path protections.
Using MS Protection You can move the protection per drag & drop
from the Network Elements tree.
Using MS Protection Name Enter the protection name.
Unmanaged Paths Paths with the state RCS will be shown.
Fragment Paths Shows all fragment paths.
Group Paths Shows all group paths.
Note:
There is a difference between the scopes Owned by s ubscriber and Owned by
subscri ber name:
If you use Owned by subscriber name, all paths of all subscribers with this name are
displayed.
If you use Owned by s ubscriber , only the paths of one subscriber are displayed. The
same applies for all scope types including name in their designation or not.
When opening the window for the first time, use the Request button to show the current
contents of the list; the list only contains a snapshot of the current database content and is
not updated automatically.
190
Client functions
Use the Update button to update the list content. After dropping a valid source in the
Scope field the list is updated automatically.
Using the Print button you can print the list content according to the current filter and sort
settings.
Upper List: The List of Paths contains the following information:

- Index
Counter for each service.
- Path
Name of the path.
- Service
Name of the service.
- Subscriber
Subscriber to which the service is assigned.
- Layer
Transmission layer (e.g. VC4, MS16).
- Bandwidth (Mbps)
Shows the bandwidth (Mbps) for the path.
- Direction
Unidirectional or bidirectional.
Operational state: disabled, enabled, Protection disturbed or unknown.
- Operator
Name of the operator who created the service.
Date and time, when the service was created.
- ACS
Actual Creation State. ACS reflects the creation state according the corresponding
infrastructure. ACS is the summary of the ACS of its route elements. Possible values
are: active, not active, not routed, unmanaged, under test or in deletion.
- RCS
Required Creation State. RCS is set by the path operations and reflects the requested
creation state. Possible values are: active, not active, not routed, unmanaged, under
test or in deletion.
- Connection Type
Possible values are e.g. simple, add drop head, add drop tail, double add drop,
unknown.
- Connection Class
Possible values are: Trail, Half-Open SNC, Open SNC, LC/TC (Link or Tandem
connection), Trail And Half Open SNC, Trail And Open SNC or unknown. If all path
edges have the same connection class, this is also the connection class of the path,
else unknown.
- Admi n State
Administrative state: locked, unlocked or undefined.
- Admin St ate Typ e
If the Administrative state is locked, the type can be implicit, explicit or explicit/implicit.
- #NEs
Number of NEs the path is routed over.
- Endpoints
Description of the endpoints of the path topology: NE, port, TP (TNMS Core/CDM).
- Ac know ledged St ate
Displays the acknowledgement of a path. Possible values are: acknowledged or
unacknowledged.
191
- Ac know ledge Tim est amp
Note:
If the path consists of more than one edge, endpoints belonging to more than one edge
are described only once.
By right-clicking in the list, you can activate a context menu with the following functions
(among other entries for filter and sort functions):
- Route Details
Select a path. Once you have activated the Route Details context menu, a List of
cross c onnections for selected path is displayed in the lower section of the window.
With the Details context menu you can show the contents of the selected log in a
separate Details window.
- Path Properties…
Shows the properties of a selected path.
- Context Menu of t he Path
Shows the context menu of a selected path.
- Locali ze Path
Marks all routing elements of the path within the tree windows.
- Print Wit h Route Details...
Prints a list of the contents (according to the current filter and sort settings) including
the information displayed when the Details context menu is activated.
- Save As With Route Details...
Saves the list in TSF format (to allow reading in MS-Access and MS-Excel) according
to the current filter and sort settings including the information displayed when the
Details context menu is activated.
descending order.
and Icons: Lists.
Lower List: Route: - List of route details for selected path:

Once you have activated the Route Details context menu of a selected service, the
following information is displayed:
- Index
Counter for each route element of selected path, e.g. cross connections, port
connections, server paths, etc.
- RE Type
The type of route element is displayed, e.g. CC, PC Reference, SP Reference, etc.
- Name
Names of the route element. It can be NE Name (for CCs) path name (for server
paths), PC name (for PC references), etc.
- A End NE
Name of the network element at the A end.
- A End Port
Identification of the start port for the cross connection within the network element:
name of the port, number of the slot, number of the port within the module.
- A End TP
Layer (e.g. VC4) and type of the start termination point A. The types are:CTP or TTP.
192
Client functions
- Z End NE
Name of the network element at the Z end.
- Z End Port
Identification of the end port for the cross connection within the network element:port
types, number of the slot, number of the port within the module.
- Z End TP
Layer (e.g. VC4) and type of the end termination point A (CTP: connection termination
point or TTP: trail termination point).
- Layer
Transmission layer (e. g. VC4).
- Bandwi dth A --> Z (Mbps)
Displays the bandwidth per edge for A --> Z.
- Bandwi dth Z --> A (Mbps)
Displays the bandwidth per edge for Z --> A.
Enabled or disabled.
- Location
Working or Protecting, depends on the location of the path within the main working or
protecting branch.
- ACS
Actual Creation State: active, not active, not routed, unmanaged, under test or in
deletion.
- Protect State
Protection state: none, working or protecting.
- Direction
Unidirectional or Bidirectional.
filter functions and a function for displaying path details.
descending order.
and Icons: Lists.
See also:
193
Listing client paths

By selecting List of Client Paths… from the context menu of a path in the Subscribers
and Services tree, the Paths list window is opened. Simultaneously, a filter is applied,
displaying client paths only.
See also:
Listing Paths
194
Client functions
Modifying a path
If the intended modification of a path influences the path topology, there are two modification
possibilities for the path. Either
• modify the route of the path first (e.g. modify the end-TPs, extend the path, etc.) and
then invoke the context menu Apply routed topolo gy . This way the topology
information will be updated, afterwards you can approve the modifications by clicking
Appl y.
Or
• adapt the path topology first on the topology side and then modify the route on the
routing side. If the modified route matches the previously modified path topology, you
can approve the modifications by clicking Ap ply.
In order to modify a path:

Select the path you want to modify in the Subscribers and Services tree and open the
context menu -> Properties… The Service / Path Prop erties window is opened.
Depending on the desired modifications, select the according tab in the window, i.e.
Properties , Topology, or Routing.
When you want to change the route of the path, you have to open theConnection
As si st ant. Complete the following steps:
1. Select the Routing tab in the Service / Path Properties window.
2. Switch to Edit mode by clicking the Edit button in the toolbar.
3. Open the context menu of a route element in the graphical display and select ->
Connection Ass istant. The Connection Assistant opens where you can modify the
route.
Notes:
- In case of a network augmentation, there might be a route mismatch or topology
mismatch indicated by the path icon in the Subscribers and Services tree. In this
case, you have to adopt the network route and/or the network topology. For
information of the contents of adopting the actual route / actual topology please click
to the links below.
- Changing the layer for a path (e.g. from VC12 to VC3) can only be done after the path
has been deactivated before (this suspends the blocking of previously switched TPs).
Also modifications concerning the direction of CCs (uni-directional, bi-directional
inclusivly Drop-and-Continue CC templates) are only possible after the path has been
deactivated before.
See also :
Adopting a network route
Adopting a network topology
Service / Path Properties
Service / Path Properties: topology
195
Name Generation Algorithm

Via the context menu in the Unmanaged Path tree you can select the menu entry Name
Generation Algorit hm. Three types of name generation algorithms can be chosen:
- End Object Name (recommended for server trails)
- Server Object Name (recommended for paths)
- Time Stamp (default setting)
Notes:
If the length of the automatic generated name exceeds the maximal length, it will be
reduced accordingly. The names are checked for uniqueness and modified to a unique
name if necessary.
Service names will not be generated and the server trail/path will not be assigned to a
subscriber but in all cases the server trail/path is moved into a path container.
196
Client functions
Path Overhead Monitoring
The network element function Path Overhead Monitoring is necessary for the following
functions:
- Path alarm monitoring
- Performance monitoring
- SNCP switching criteria
It will be enabled/disabled by TNMS Core/CDM depending on the following criterias:

- Path-Overhead-Monitoring of higher and lower order SDH Termination Points
(HPOM and LPOM) is automatically enabled when a Performance Measurment
Point associated with this TP gets used by a PM-Log or when the TP gets involved
in a protected Cross Connection.
- For lower order TPs, LPOM is automatically disabled when the last protected CC as
described above is removed (even if there is still an active PMP associated with this
TP. Disabling of LPOM is necessary because the number of enabled LPOM
functions is currently limited by hardware to a max. of 32 per VC4.
197
Paths under test

A path that is under test has been created in the Connection As sistant window with the
Loopback connection template or the path is affected by a port loopback. By selecting
End Test from the context menu of a path, path container or subscriber bothTP loopbacks
and port loopbacks (if existing) are removed. When deleting a path affected by a loopback
(it does not matter whether uni- or bi-directional, and whether affected by TP loopback or
port loopback), the operator is asked in a message box whether or not the probably
existing port loopbacks shall be removed too.
See also:
198
Client functions

In the Path Wizard window you define the topology of a path:
Note:
For the Port / TP <X> fields a context menu entry Refresh TP-Resources is available:
Use this entry to update the TP-resources, e.g. the TP-connection states. This menu entry
is available by clicking into the Port / TP <X> field with the right mouse button.
Such a manual update may become necessary after a change of the switching state (e.g.
after CC creation or deletion or add / remove protection). The opened window does not
automatically update such a change of the switching state.
- Port / TP A (1)
On the left, the Exit / Entry points for this NE can be defined through a button. Filtering
is also possible; see filtering description below.
- Port / TP Z (1)
Filtering is also possible; see filtering description below.
- Restrict Layer
If displayed, this field offers specific layer selection, depending on the chosen NE
above.
Note:
This field is only visible when in the Options window the check box Show Layer
Restrict ion Control is clicked. The Options window is invoked through the button
Options.
- <Topol ogy Templates>
Contains templates for the connection type. More information is provided underIcons:
Port Connections, Path Wizard and Connection Assistant
Note:
In case a topology is not defined through the topology templates (e.g. broadcast), a
warning message will be displayed. In TNMS Core/CDM, however, you can use the
undefined topology although it is not part of the template.
- Resilience
Shows what kind of path protection exists for the direction A to Z. The possible values
are: don’t use, least, low or high.
- Bandwidth (Mbps)
If displayed, this field offers selectable values for the bandwidth of ethernet paths.
Note:
This field is only visible when in the Options window the check box Show Bandwidth
Options.
- Port / TP A (2)
can be defined through a button. Filtering is also possible; see filtering description
below.
- Port / TP Z (2)
below.
- Filter
Each Port / TP field allows filtering using predefined filter criterias. They are displayed
as icons; tooltips show the meaning of icons. The filter criteria are:
o No Filter
199
o Port Connection Filter

o Cross Connection Filter
o Operatio nal State Filter
o Subscriber Filter
o Layer Filter
o Settings Filter
a) Info Ar ea
This is a text area where information, hints, warnings and errors are described.
b) Edges
Note:
Some of fields in the Edges view may be changed. After having changed a displayed value
in the list field you must click the Modify button to accept the modification!
- Index
- Direction
Bidirectional/Unidirectional.
- NE
Shows the name of the used start NE.
- Port / TP A
Shows the name of the start port / TP.
- NE
Shows the name of the used end NE.
- Port / TP Z
Shows the name of the end port / TP.
- BCM (A)
Border Crossing Mode A, the field shows the Exit / Entry points as a text field
chosen before for the Port / TP.
- BCM (Z)
Border Crossing Mode Z, the text field resembles the Exit / Entry points as a text
field chosen before for the Port / TP.
- Resilience A-Z
Shows what kind of protection exists for the direction A to Z. The possible
values are: don’t use, least, low or high.
- .
- Resilience Z-A
Shows what kind of protection exists for the direction Z to A. The possible
values are: don’t use, least, low or high.
- Layer
Displays the transmission capacity of the service, e.g. VC4.
- Bandwidth A-Z
Shows the bandwidth for the direction A -> Z
- Bandwidth Z-A
Shows the bandwidth for the direction Z -> A
200
Client functions
Buttons
- Previous opens the Path Wizard: properties window.
- Next either manual or automatic routing can be chosen when clicking the arrow on the
right of this button. You should always use click the arrow, not directly on the button in
order to see whether manual or automatic routing is selected.
- Modify accepts the modifications done.
- Add inserts the elements of the port / TP fields into the list below.
Note: This button is only available, when the first edge has been defined.
- Remove removes the elements of the port / TP fields and from the list below.
- Clone is used for bundle routing. It clones the given path topology. After clicking this
button the Clone Edges window opens where you must enter the amount of edges you
want to create.
- Move is used for bundle routing. It automatically moves the endpoints from the old NE
(B) to the new NE (C).
Note:The port and TP selection will not be changed. This means that the “Move”
operation can only be successful if the NE type of the old NE is identical to the NE type
of the new NE; i.e. the required ports and TPs are available and free on both NEs.
- Options opens the Options window for defining window preferences and automatic
routing options.
See also:
Creating a path
Port and TP filter settings
Preferences & Routing Options
NE distinctions
201

The window will be opened when selecting the menu entryCreate Path.... or Create
Service... Depending on your selection made, some fields may be greyed out.
Service Properties
- Subscriber
Use drag-and-drop to drag a subscriber from the Subscribers and Services tree into
the field or select the subscriber from the combo box.
- Service Label
Description of a service defined by the user (max. 63 characters). If you do not define a
service label, TNMS Core/CDM generates a default label containing the creation date
and time.
Path Properties
- Path Label
The path is identified by a label defined by the user (max. 63 characters). If you do not
define a path label, TNMS Core/CDM generates a default label containing the creation
date and time.
- Comment
You can enter a comment for this path.
- Write protected
Clicking the check box for activating write protection for this path.
- Admi n State
Shows the administration state of the paths; possible values arelocked and unlocked.
Locked means that the path is excluded from routing.
Using the Buttons at the top of the window you can:

- Click Next in order to move to the Path Wizard: define topology window where you
can continue creating the path.
- Click Create (only visible when creating a service) to create the service.
See also :
Creating a path
Creating a path bundle
202
Client functions
Path Wizard: rout ing results

Buttons
- Previous jumps back to the previous window, i.e. to the Path Wizard: define
topology window.
- Create is shown if the route has already been defined and is identical with the
topology, this implies that RCS is set to "Not Active". You can select Save from the
menu in order to save the defined path, this implies RCS is set to "Not Routed". See
system information in the Info Area.
- Check performs a route check. See system information in theInfo Area.
- Ac ti vate activates the route, this implies RCS is set to "Active". See system
information in the Info Area.
- Deactivate deactivates the route. This is only possible for previously activated routes.
It implies RCS is set to " "Not Active". See system information in the Info Area.
- Route starts the automatic routing for the specific topology according to the
parameters set in the Options window under the Automatic Routi ng Options tab.
Note: not all topologies allow automatic routing; only if the check boxExclude NEs
from routing has been selected, the Exclude NEs from routing window opens,
otherwise not.
- Options opens the Automatic Routing Options window.
Graphical display of t he routing results

The graphical view in the upper part of the window shows the routing results for the
involved route elements. Tooltips provide extensive information on the status of the
involved route elements when moving the mouse on the route elements. You can also use
the check boxes to handle tooltips.
Context menu entries in th e graphical view

A context menu of the route elements is available in the graphical view with the following
entries:
- Remove Connection
Use this entry if you want to remove the selected route elements (cross connection,
port connection reference, server path reference, etc.) from the path route.
- Route
- Remove Route
Use this entry if you want to remove the complete route. Only the endpoints as
defined in the topology will remain.
- Bundle Route Elements
Use this entry if you want to bundle route elements.
- Stretch Route Elements
Use this entry if you want to stretch route elements.
- Refresh all TP-Resour ces
Use this entry to update the TP-resources, e.g. the TP-connection states. This
entry is reachable by clicking into the white area of the window.
Note:
Such a manual update may become necessary after a change of the switching
state (e.g. after CC creation or deletion or add / remove protection). The opened
window does not automatically update such a change of the switching state.
- Take Topology from Required Route
Use this entry if you want to take the topology from the (modified) route.
- Re-route
203
- Common routing
For this option, the start and end points of the whole route are automatically
taken as start and end point for the new route. Locked resources will be
excluded.
- Diverse Re-routing
taken as start and end point for the new route. Locked resources and the path
belonging to the selected service will be excluded.
- Specific Re-routing
By selecting this option you are able to manually define the start and end cross
connection for diverse re-routing. Locked resources and the path belonging to
the selected route will be excluded. Additionally, you have to perform the
following steps:
a) Exclude NE: Drag the NEs you want to exclude from the routing process
from the Network Plan into the box. Click Next to confirm your selection.
b) Routing optimization: Specify the cost factors.
c) Protection options: Select NE diverse or cable diverse path protection. Click
Next to confirm your selection.
- Global Re-routing
By selecting this option you initiate a global re-routing order.
- Protection
- Add Prot ectio n
Use this entry to add a protection, either Port diverse, Cable diverse or NE
diverse.
- Remove Protecting Path
Use this entry if you want to remove a protecting path.
- Remove Worki ng Path
Use this entry if you want to remove the working path.
a) Info Ar ea
b) Route Elements
- RE Type
Shows the type of the route element, e.g. Cross Connection.
- Name
Shows the name of the route element.
- A-End
Start point of the route element.
- Z-End
End point of the route element.
- Layer
Displays the transmission capacity, e.g. VC4.
disabled: The resources are not in a position to make the service available and
corrections are necessary. I.e. there are alarms at ports or termination points of this
path which are identified as affecting the service. The system knows or assumes that
these alarms will either lead to or signal a service interruption. Another reason may
be the failure or deletion of resources which are required for the path (e.g. cards,
modules) even if there are no alarms for these resources or the corresponding alarms
cannot be directly assigned to a port or termination point.
enabled: The resources are operable and available.
204
Client functions
unknown: The current operational state cannot be determined, i.e. the network
element currently is not available.
- Ac tu al Creation State
Shows the actual creation state of the route element. Possible values areactive, not
active, not routed, undefined, under test.
- Location
The location state of the path can be working or protecting indicating whether the
route element is situated on the required working or protecting path route.
- Protection State
The protection state can be none, working or protecting.
- Direction
Shows the direction of the route, either or bi-directional , unidirectional A-Z,
unidirectional Z-A.
- Bandwidth A -> Z
Shows the bandwidth for the direction A -> Z.
- Bandwidth Z -> A
Shows the bandwidth for the direction Z -> A.
c) Path Edges:
- Index
- Direction
Direction of the service, unidirectional or bi-directional .
- NE
Name of the source network element.
- Port / TP(A)
Start port / end termination point for the path.
- NE
Name of the sink network element.
- Port / TP(Z)
End port / end termination point for the path.
- BCM(A)
The border crossing mode A indicates entry or exit point as a text field.
- BCM(Z)
The border crossing mode Z indicates entry or exit point as a text field.
- Resilience A-Z
- Resilience Z-A
Shows what kind of path protection exists for the direction Z to A. The possible values
- Layer
Displays the transmission capacity of the service, e.g. VC4, STM-16, etc.
- Bandwidth A-Z
Displays the bandwidth per edge for A->Z.
- Bandwidth Z-A
Displays the bandwidth per edge for Z->A.
205
See also:
Creating a path
Exclude NE from routing
Hybrid routing
Icons: Routing
NE distinction
206
Client functions
Release Required Resources

The command Release Required Resources deactivates (=disconnects) all CCs
belonging to a path and allows TNMS to use the resources of this path for other paths. In
this way common use of network resources is possible. Activation makes sense only for
one of these paths at a time. Before activation of a second path a path merge is
announced.
If you want to release required resources; complete the following steps below:
1. Select the path to be deleted in theServices & Subscribers tree of the TNMS
Client.
2. Open the context menu with the right mouse tab and selectRelease Required
Resources. As a result, the CCs will be deleted permanently from network elements,
but not from the TNMS database.
3. Afterwards a confirm window appears. A checkbox is available for the deletion of the
implicit server paths. Click it or not according to your needs.
207
Rerouting a path
In order to re-route a path, the Service / Path Properties window (it will be opened as
Path Properties window when no service exists for the selected path) for the path to be
re-routed must be open, the tab Routing must be clicked and the Edit mode must be set
(via the Edit button).
In the graphical display move the mouse onto a route element and open the context menu
with the right mouse tab. The menu entry Re-Route will be displayed with the following
sub-entries:
- Common Re-Routing
For this option, the start and end points of the whole route are automatically taken as
start and end point for the new route. Locked resources will be excluded.
Paths with unconnected endpoints (server paths) do not allow "Diverse Re-routing",
because the start/end TPs are the unconnected endpoints and they are strongly
correlated with their "neighborhood" TPs.
- Diverse Re-Routin g
For this option, the start and end points of the whole route are automatically taken as
start and end point for the new route. Locked resources and the route belonging to the
selected path will be excluded.
- Specific R Global Re-routing
By selecting this option you initiate a global re-routing order.e-Routing
connection for diverse re-routing. Locked resources and the route belonging to the
selected path will be excluded. Additionally, you have to perform the following steps:
a) Exclude NE: Drag the NEs you want to exclude from the routing process from the
Network Plan into the box.
Click Next to confirm your selection.
c) Protection options: Select NE diverse or cable diverse path protection. ClickNext to
confirm your selection.
1. Confirm the dialog Proceed routing operation with selected st art- and end-
cross connection by clicking Yes.
2. As soon as the automatic routing is finished a graphical representation of the
path and a list of NEs and TPs is displayed.
- Global Re-Routin g
208
Client functions
Preferences and routi ng opti ons

The Options window is opened from the Path Wizard – Define Topolog y window and
offers two tabs: Preferences and Au tomatic Routi ng Options . The following settings can
be made:
Preferences:
Enhanced Controls:
- Show Layer Restriction Control
Clicking this check box here will hide / display the field Layer Restrictio n in the Path
Wizard – Define Topolo gy window and in the Service/Path Properties – Topology
window.
- Show Bandwidth Restric tion Control
Clicking this check box here will hide / display the field Bandwidth in the Path Wizard
– Define Top ol ogy.
Connection Assistant:
- Show BCM always
Clicking this check box will make available the selection list for the Border Crossing
Mode (Exit / Entry) in the Connection Ass istant. The selection list is displayed next to
the Port / TP <X> fields.
- Use Enhanced Tooltips
Clicking this check box here enhanced tooltips can be made available in the
Connection As sistant.
Full Route Expansion:

- Configures the timeout for full route expansion of complex paths by entering a value
between 5…36000s. This action defines a timeout for the graphical expansion of the
paths.
Auto matic Routi ng Options :

Routing Optimization
- Least Hops
Choose this option if the desired route of a service should have as little hops as
possible.
- Cost Factors #1, #2, #3
These are the cost factors that have been defined previously in theTNMS SysAdmin
component.
- User defined
Click this option if you want to adapt the cost factors individually, from low (-) to high
(+).
Protection Options
- Port di verse
The protection route never uses port resources used by the working route.
- Cable diverse
The protection route never uses a port connection on the same cable layer used by
the working route (includes port diversity).
- NE diverse
The protection route never uses NE resources used by the working route, except for
those NEs where the A and Z endpoints are located.
209
General
- Exclude Resources not in Operation
If this option is set, TNMS Core/CDM ensures that all ports used for the path (the end
ports also) are enabled, i.e. all cards implementing these ports are present and
operational and there are no (service) alarms on these ports. If the option isnot set it
is not possible to define cross connections for ports of the operational state disabled.
If this option is not set, the operability of resources has no influence on the path that
can be routed by the operator. In this case, the system might fail to provision the path
until all resources used by the path are enabled. The path will be unprovisioned. All
disabled ports and TPs are marked in the list and you cannot proceed with the next
step. To proceed - also with disabled ports - you must set the option.
Exclusion of NEs from Autorouting
When clicking Appl y here and activating the automatic routing option in the Path
Wizard: define topology window, the window Exclud e NEs will be opened. You can
drag the NEs to be excluded from autorouting from the Network map into this window.
Use Same Trail
If this routing option is set, the automatic router will try to find a route with enough
spare capacity to create all paths within the bundle, using the same route but different
TPs. If the router cannot find any route with enough capacity for all bundle paths, the
routing fails. The user can switch-off this option and try again to route the path
bundle.
Don’t change timeslot
In BSHR rings with multiple fault support, timeslot interchanges must be avoided. In
cases of protection switching the destination of the traffic will end on a wrong TP
when timeslot interchanges occur on the route, by avoiding this the traffic will not be
lost.
If this option is set it will prevent the automatic router from doing timeslot interchanges
on the whole path.Routing of paths with this option set will slightly influence the
performance of automatic routing. Routing of paths with this optionnot set will
execute with the same performance as before.
An existing crossconnection or a server path that does a timeslot interchange may not
be used by the automatic router. The result in this case will be a failed routing order
or a path which does not meet the resource minimization usage rules.
Enforce low order switchi ng fabric
The “Enforce low order switching fabric” checkbox disables possible connections from
the HO Switch to the Lineport for the automatic router.
The new Option is only valid for the automatic router. Manual routing is not affected.
See also:
Exclude NE from routing
Automatic Routing Preferences
210
Client functions

You may activate the following options within the Service / Path Properties window ->
Routing tab and the Path Wizard: routing results window at the top of the window:
- Show Tooltips on Route Element
Placing the cursor on one or more RE icon(s) in the graphical routing view displays
information about: Name, A-End, Z-End, Layer, Direction, Connection Class and
NxCount.
- Follow Path in t he Network Plan
Using this option you can easily follow a path in the Network Plan view. If you have
activated this option, the displayed path will be highlighted in the Network Plan view.
Moreover, the network element that is related to the cross connection that has been
selected in the routing view will be selected in the Network Plan as well. Note that
highlighting the path is only possible if the path already exists (i.e. it is not possible if
the manual routing process has not yet been completed).
- Show Traffic
You can use this option to display the type of traffic configured for this path. The
connecting line between the two CCs is then highlighted accordingly:
Magenta = unidirectional RxTx
Red-orange = unidirectional TxRx
Green = bidirectional path
The display is not automatically updated. To refresh the display, deactivate and then
reactivate Show Traffic.
Additionally, the ToolTips provided for the Port/TP fields in theService / Path Prop erties
window -> Topology tab, the Path Wizard: Topology window and in the Connection
As si st ant are enhanced with various functions.
The different ToolTips can be displayed the following ways:
- Moving your mouse over the icon displays basic information, such as resource
name, layer set and additional attributes.
- Moving your mouse over the icon and pressing the <Shift> key displays the name
of the used port connection and the partner port/TP of the used port connection.
- Moving your mouse over the icon and pressing the <Alt> key displays the name of
the CC(s) or SNC(s) and their route elements.
211
Path bundles
Path bundles - general information
A path bundle is an unordered collection of paths used to concentrate identical operations
on multiple paths into one bulk operation, i.e. for providing automated operations on a set
of paths. This saves effort on handling the basic path scenarios like
• Creating several paths

• Changing the route of several path
• Moving the endpoints of several paths
Bundled paths have some attributes in common:

• No commonly used TPs, i.e. the path routes are disjunctive
• Requi r ed Cr eat i on St at e ( RCS) i s not unmanaged
• The maximum number of participating paths in a bundle is 63, due to performance
aspects
Only path with the outlined preconditions as listed below should be grouped together in a
path container or a service. It is the operator’s responsibility to name the path container or
service in a way that it is clear that here a path bundle is contained.
Preconditio ns for paths bundles:

• Connection class must be identical for all paths used in path bundle.
• Connection type must be simple.
• Resilience must be protected.
• Direction must be identical for all paths, i.e. all paths must have the same A – Z
direction.
• LayerSet must be identical for all paths, i.e. only VC12 or only VC4, etc.
• A-End of all paths is on the same NE.
• Z-End of all paths is on the same NE.
• All paths use the same NEs and sub bundles use the same multiplex sections.
• There is no relationship between the paths: e.g. one path is server path to one or
more other paths in the bundle.
See also :
Creating a path bundle using a path template
Modifying routes of a path bundle
Moving the endpoints of a path bundle
212
Client functions
Clone Edges
The Clone Edges window opens from the Path Wizard – Define Topolog y window when
clicking the button Clone.
You are prompted to enter the amount of edges you want to clone from the original edge
shown in the Path Wizard – Define Topolog y window. E.g. entering "3" and clicking OK
creates two additional path edges, i.e., a total of three path edges will be created.
213

Creating a path bundle means creating a set of paths using a path topology with n
independent path edges. It is not necessary that a simple path already exists; if it does
exist this path can be used as a template for the routing of the other bundle paths.
Create the first path edge as usual:

1. From the Network Map in the Services Mode, select the source NE with an existing
port connection and open the Path Wizard – Properties window. Enter the general
attributes for the path and click the button Next.
Note: It is recommended to keep all path of a path bundle under the same service /
path container. This is not a mandatory requirement, but it will help editing path
bundles later.
2. In the Path Wizard – Define Topolo gy window now define the topology for the first
path edge, i.e. for the first path edge of the bundle:
Select TP A(1) and TP Z (1) and click Add to add the path edge to the topology. The
Connection Type must be simple and Resilience must be unprotected.
Clone the edges of the first path edge:

3. In the Path Wizard – Define Topolo gy window use the button Clone to automatically
create n new path edges by generating the new end TPs in increasing order.
The Clone Edges window opens where you are asked to enter the amount of path
edges you want to create. E.g. entering “3” and clickingOK creates two additional path
edges, i.e., a total of three path edges will be created.
An information message is shown in the Info Area of the Path Wizard - Define
Topology window.
Route the path bundle:

4. By clicking the button Next the path edges are now shown in the Path Wizard –
Routing Results window. Now click the button Route in order to route the existing
path edges of the bundle.
Notes:
- This command is available if the topology is complex and consists of path edges
according to the definition given in the topic description “Path bundles - general
information”, Preconditi ons for specific tasks on path bundles.
- If the routing option Use same trail is set, the automatic router will try to find a
route with enough spare capacity to create all paths within the bundle, using the
same route but different TPs. If the router cannot find any route with enough
capacity for all bundle paths, the routing fails. The user can switch-off this option
and try again to route the path bundle.
- The automatic router will give a feedback about the routing steps (number of
bundle paths to be routed, number of bundle paths already routed). All found
routes of the bundle path will be shown as parallel path edges in the same routing
view. The user can inspect the route of each bundle path (path edge) before he
decides to create the paths of the bundle.
- If not all bundle paths (path edges) could be routed, the bundle cannot be created,
but it can be saved with RCS not routed. In this case you can delete the path
edges that could not be routed, or you can delete routed path edges to reduce the
bundle and try to route the bundle again.
5. If all path edges have been routed successfully, execute the commandCreate or
Ac ti vate in the Path Wizard – Routing Results window in order to create
independent paths from the path bundle. These individual bundle paths will be created
214
Client functions
under the same service / path container and are visible in theSubscribers and
Services tree.
Notes:
- If the command Route… is executed on a path bundle and the first path edge is
already routed this path edge will be used as a pattern for the routing of all other
path edges of the path bundle as „near" as possible to the given pattern.
- It is recommended to keep all path of a path bundle under the same service / path
container. This is not a mandatory requirement, but it is will help editing path
bundles.
See also:
Moving the endpoints of a path bundlePath Wizard: properties
Path Wizard: routing results
Clone Edges
215

You can also choose an existing path as a template for <n> additional other paths you
want to define as a path bundle.
1. Choose an existing path as a template path from theSubscribers and Services tree
and select the context menu entry Properties… The Path Properties window with its
four registers Properties , Topology, Routing and Al arms opens.
2. Select the Topology view and click the Clone button. The Clone Edges window
opens where you must enter the amount of edges you want to clone from the original
path.
3. In the Path Properties window select the Routing view; the chosen path with its
clones is displayed graphically in the View Mode.
4. Select the Edit Mode and then click the Route toolbar button.
See also:
Moving the endpoints of a path bundleService / Path properties
Service / Path properties: routing
Service / Path properties: topology
Clone Edges
216
Client functions

Modifying routes of a path bundle means that for two or more paths of a path bundle new
routes must be found, e.g. due to intended maintenance works on a network element.
1. In the Subscribers and Services tree you can select any path of the bundle path for
modifications (having grouped all paths of the bundle path under one single service or
path container when creating the bundle path makes handling of individual paths of a
bundle path easier).
You can either:
- select several paths which and click the context menu entryMultiple Path
Properties… The selected paths will be added to the Path Properties window; or
- select the properties of a service. In this case all paths belonging to the service are
shown in Service Properties window.
2. Now click the button Bundle. This groups the chosen paths in a bundle path object.
Instead of the selected independent paths only a single bundle path object is now
shown in the Path Properties window.
3. You can view the independent path routes of the bundle in theRouting View of the
Path Prop erties window.
4. Select the path here you want to re-route, open the context menu and select the kind
of re-route entry you need, e.g. Re-route -> Global Re-routing.
5. By clicking the button Apply the new routes found are assigned to the original paths of
the bundle. The dismantled path bundle will be displayed on the left in theRouting
View of the Path Properties window.
Note:
If only one path is to be re-routed, this can simply be done via locking a specific network
element. Then start re-routing this path as usual.
See also :
Creating a path bundle g a path template
217

It is possible to move the endpoints of all paths of a path bundle. In order to do that the
topology of the original path bundle must be changed. Assuming that the path bundle is
routed between NE A and NE B and you want to move the endpoints from NE B to NE C.
Note:
Moving the endpoints of a path bundle should only be applied to one end of a path bundle,
not to both ends at the same time. In this case the search operation could possibly fail.
In order to move the endpoints to another NE you have to do proceed as follows::

1. In the Path Wizard – Define Topolog y window replace the old NE (B) with the new
NE (C).
2. Click the button Move to automatically move the endpoints from the old NE (B) to the
new NE (C). Note: The port and TP selection will not be changed. This means that the
“Move” operation can only be successful if the NE type of the old NE is identical to the
NE type of the new NE; i.e. the required ports and TPs are available and free on both
NEs.
3. When all endpoints are moved, the path bundle can be re-routed. Select the displayed
path in the Path Prop erties window and with a right mouse click the context menu
entry, e.g. Route -> Globally Re-route.
4. Finally the changes must be applied by using the Appl y or Ac ti vate button.
See also:
Path Wizard - define topology
218
Client functions
Ports, port connections and termination poin ts

To create a port connection, switch to the Network Editor mode and then open the Create
Port Connection window via TNMS Client -> Configuration -> Create Port
Connection...
You can also reach the Create Port Connecti on window directly via the Create Port
Connection... context menu of a selected network element both in theNetwork Elements
tree and in the Network Plan.
1. Drag a network element into the Source field (if you have called the window from the
context menu of the network element, this step is omitted - the network element has
been automatically transferred as the source network element).
2. In the same way, drag a network element from theNetwork Elements tree view or the
Network Plan view into the Destination field.
3. Under Direction specify whether a transmission is to take place in both directions (<- -
>),only from the source to the destination element (->) or from the destination to the
source element (<-).
4. Under Layer choose the transmission capacity of the port connection by selecting one
of the selectable bandwidths.
Note: For NEs, which support optical protection, please see the topic Layer
Restrictions at Optical Protection.
5. In the pull-down Port fields, select the network element port for the connection in each
case. The port selection offered already corresponds to the options specified by the
bandwidth selection. Moreover, protected ports are also indicated, see Displaying /
modifying the properties of MSP.
6. If you intend later on in the path wizard to optimize the cost aspects of the route, you
can specify under Parameters for Automatic Routing which cost factors are relevant
and to what degree when the port connection is used.
Cost factors can be defined by the TNMS Core/CDM administrator. More information
on cost factors is provided in the SysAdmin online help.
7. In the At trib utes area at the bottom right of the window you can enter a name for the
port connection in the Name field, and a description of the cable type used in the
Cable Conduits field. note that more than on cable conduit can be defined; they must
be separated by a comma or a semicolon.
The pull-down Admi ni st rativ e State field at the bottom allows you to select the
appropriate value Locked or Unlocked for the port connection to be created. Locked
means that this port connection cannot be used for automatic routing.Unlocked means
that this port connection can be used for automatic routing.
8. In the Comment field, you can enter a comment for the port connection to be created.
9. Use the Create button to create the port connection. The created port connection will
be visible in the Network Map.
Note:
You can also create port connections for universal objects (e.g. objects integrated via TIF
interface) as well as for EMOS managed network elements, if appropriate ports have been
created before using the UNO element manager application.
See also:
Editing / Deleting port connections
Layer Restrictions at Optical Protection
219
Displaying the properties of port c onnections

1. In the Network Editor view of the TNMS Cli ent, switch to the NE container that
contains the relevant port connection or, in the case of port connections that extend
across NE containers, switch to a NE container involved in the port connection.
2. Use tooltips (moving the cursor to a port connection) to obtain the following
information: maximum bandwidth provided on this port/these ports, number of port
connections emanating from these ports.
Port connections that extend across NE container boundaries are indicated by the icon for
virtual ports .
In the Network Editor you can also use the Port Connections... context menu for a port
connection to open the Edit/Delete Port Connection window. This window contains
detailed information on the selected port connection.
See also:
Icons: Network Plan
Editing/deleting port connections
220
Client functions
Editing/Deleting port connections

In order to edit/delete an already configured port connection you must open the
Edit/Delete Port Connection window:
- Switch to the Network Editor mode and use the Port Connection... context menu of
an involved network element in the Network Elements tree view or double-click on a
port connection in the Network Plan in order to open the Edit/Delete Port
Connection window for editing/deleting port connections.
- In the left area of the window you can select the port connections. Via the tabs
Properties , Paths or Al arms you determine, which properties of the port connection
are to be displayed.
- In the lower part of the window you can now edit the Parameter for Automatic Router
and the At tr ibut es for the port connection. Click Apply to confirm your changes.
- Click Delete in order to delete the selected port connection. You are asked to confirm
the deletion. If you confirm with Yes the port connection will be deleted and the ACS of
all paths using it will be set to defined.
In case managed paths use the port connection, a warning will be displayed. After
deleting the port connection the ACS will be "Not Routed".
Note:
If you have created a port connection between two NEs and configured a write-
protected service via this port connection, you may experience problems when you try
to delete the port connection. In this case the window Port Connection Used By
Write Protected Paths is displayed. You should remove the write-protection for this
service before attempting to delete the corresponding port connection.
Presentation of Port Connections:

In the Network Plan, you can click on a port connection and change the shape of the line
by dragging the mouse. The resulting nodes can be deleted using theRemove All Nodes
or Remove Selected Nodes context menu of the port connection.
Unusable Port Connection:

The Network Plan displays unusable port connections by changing the color of the
concerned ends to gray. In the Port Connection window, the Direction arrow changes its
color to red on the side of the unavailable port if a port connection is unusable. If a port
connection is unusable, this means that at least one of the ports involved is either disabled
or missing.
Deleting Port Connections Stored in NEs:

It may happen that you want to delete a port connection to a network element to which
TNMS has currently no access. This may result from missing write access or an
interruption of the NE. In this case a warning might pop up informing you that you are
deleting a port connection stored in an NE without write access. Such a port connection
may be deleted. It will be removed from the TNMS database, and you can create a new
port connection using the same ports if desired. However, if the participating ports are left
unused, the previously deleted port connection will be recreated automatically e.g. after a
reintialization of the NEs. This behaviour results from the information stored in some NEs
during the creation of the port connections. To erase this information stored in the NE, you
have to delete the port connection when you have access to the NE.
Instead of deleting the port connection while you do not have access to it, set the
administrative state of the port connection to locked. Consequently, the automatic router
will exclude this port connection from routing.
Operators with good element manager knowledge may delete the information stored in the
NE via the element manager. The corresponding attribute in the element manager is called
differently depending on the element manager. Common names areConnector Location
or Trail Identifier.
221
Warning:
Do not confuse Trail Identifier with Trace Identif ier . The Trace Identif ier may not be
manipulated!
If you delete these attributes via the element manager while the port connection in TNMS
is still available, a warning will be written into the Network Event Log . Additionally, the
port connection property Stored in NE is set to no. This has absolutely no influence on the
management functionality. The port connection may be used by TNMS as before.
Deleting Static Port Connections:

The deletion of static port connections via the TNMS-GUI will not be indicated by a special
note. Nevertheless they are deleted from the TNMS database. However, the
corrresponding static PC related information in the NEs is not deleted. Additionally, an
error response in forwarded back from the NECs to TNMS that these static PCs cannot be
deleted in the NEs afterwards. Please note that this response is not directly visible for the
TNMS operator but only stored in the TNMS system message log.
Note:
After a reinitialization in TNMS or an upload/synchronization of NEC data to TNMS this
deleted PC is recreated automatically in TNMS!. Please see above how to delete port
connections stored in NEs.
Overview of information for the Edit/Delete Port Connection window:

This window provides information concerning the operational state of a port connection.
The operational state is indicated by a red (disabled) or green (enabled) arrow head.
Properties
- Source NE (displayed at the top left side of the main window)
Description of the source network element. Is sometimes taken from the network
element from which the window was opened.
- Destination NE (displayed at the top right side of the main window)
Description of the destination network element. You have a choice of all network
elements to which port connections are created from the above source network
element.
- Ports
Source network element port and destination network element port for the outgoing
port connection.
- Direction
Shows the direction for which the port connection is to be used. TheDirection arrow
changes its color from green to red on the side of the unavailable port if a port
connection is unusable.
- Terminated Layer Set
Terminated layers (TL) of a path edge according the generic rules.
- Nontermin ated Layer Set
Non-terminated layers (NTL) of a path edge according the generic rules.
- Cost Factor #1 - #3
This parameter is necessary if you intend later on in the automatic path wizard (Create
Path) to optimize the cost aspects of the route, you can specify under Attr ibut es
which cost factors are relevant and to what degree when the port connection is used.
Cost factors can be defined by the TNMS administrator. More information on cost
factors is provided in the SysAdmin online help.
- Admi ni st rative State
This parameter is used for locking / unlocking a port connection.Locked means that
this port connection cannot be used for automatic routing.Unlocked means that this
port connection can be used for automatic routing.
Select the appropriate value Locked or Unlocked for the port connection to be created.
222
Client functions
- Name
This attribute shows the label for the port connection. It can be modified here.
- Cable Conduits
This attribute is a parameter to create e.g. a cable diverse protection. Please note that
the names for cable layers are unique. The same name may not be used for different
cable layers since TNMS Core/CDM will assume they are the same.
- Stored in NE
This attribute indicates whether the port connection information is stored in the
participating NEs (yes) or not (no).
- Comment
You can enter a textual description for the port connection here.
Paths
- Source NE (displayed at the top left side of the main window)
Description of the source network element. Is sometimes taken from the network
element from which the window was opened.
- Destination NE (displayed at the top right side of the main window)
Description of the destination network element. You have a choice of all network
elements to which port connections are created from the above source network
element.
- Index
Counter for each path.
- Paths
Path labels of the paths used for the selected port connection.
- Service
Name of the associated service.
- Subscriber
Name of the subscriber for whom the path was set.
- Layer
Transmission layer (e.g. VC4).
- Type
unidirectional or bidirectional.
- Admi n State
Administrative state: locked, shutting down or unlocked.
- Operational state
Operational state: disabled, enabled or unknown.
- RCS
Displays the Required Creation State of the port connection. Possible values are:
active, not active, not routed, unmanaged, under test or in deletion.
- ACS
Displays the actual creation state of the port connection. Possible values areactive,
not active, not routed, unmanaged, under test or in deletion.
Al arms
After selecting Al arms all equipment and port alarms relevant for the selected port
connection are displayed. (TP alarms of the path layers are not displayed.)
The alarms for the source NE are shown above the destination NE. You may select a
destination NE for which alarms are to be displayed.
Further details of the alarm entries are similar as in the Alarm list.
See also:
223
Layer Restrictions at Optical ProtectionIcons: Network Plan
224
Client functions
Link detection view

In the Network Editor mode, the command TNMS Client -> Configuration -> Engage
Link Detection... starts the automatic link detection. The Link Detection View window is
opened.
The target of the automatic link detection is to detect directly physical connected ports, i.e.
port connections not yet known by the TNMS Core/CDM. The auto link detection is only
possible if the following preconditions are fulfilled:
• The NE has been created in TNMS Core/CDM.
• The DCN connection to each NE is established including a successful login
procedure.
Notes:
• The link detection mechanism is only supported by a restricted number of NEs,
e.g. hiT7070.
• The link detection uses path trace information, which must be configured in the
NEs. For SDH transmission, the actually sent RS path trace and the received path
trace are compared.
The following information is displayed in the list in the upper part of the window:
- Index
Number of the rows in the list.
- Link Type
Shows the link type of the found link. Examples for link types are:
• Potential PC: the link detection found a valid connection, which does not exist yet
and which is not in conflict with any other object in TNMS NWL. Double click on
the list entry or push the Create button in order to open the Create Port
Connection window.
• Existing PC: link detection found a connection, which has already been created in
the TNMS NWL.
• Conflicting: link detection found a connection, which is in conflict with an existing
connection in TNMS. The conflicting object must be deleted in TNMS before the
found connection can be created. Please note: it may happen that link detection
found a uni-directional connection, but in TNMS a bi-directional connection exists.
This results in a conflict for the link detection mechanism although there may be
no true conflict.
• Trail: The connection between two ports found by link detection is already
existing in TNMS. However, the connection in TNMS is not a simple port
connection but a trail. This can happen if the connection crosses a transparent
network element like an optical amplifier.
- A End NE
Name of the network element at the A end.
- A End Port
Identification of the A end port within the network element.
- Z End NE
Name of the network element at the Z end.
- Z End Port
Identification of the Z end port within the network element.
- Description
Possible values are e.g.
• Potential PC: the detected port connections is not in conflict with any existing port
connection or trail.
225
• Existing PC: the detected port connection already exists.

• Conflicting direction: there is already an existing port connection, which connects
both ports but the directionality is different from the detected port connection.
• Conflict PC A: the A-end of the detected port connection is in conflict with an
existing one.
• Conflict PC Z: the Z-end of the detected port connection is in conflict with an
existing one.
- Object
If a conflict is displayed under the Description column then the found object causing
the conflict is displayed here.
Buttons:
- Print out the displayed list of detected port connections not yet known by TNMS
Core/CDM.
- Create opens Create Port Connection window with the default values for this port
connection if the detected port connection is in conflict with an existing one.
- Close the window.
- Cancel aborts the link detection process.
226
Client functions
Listing ports
TNMS Client -> View -> Lists... opens a list window. Clicking on the Ports tab on the
bottom displays the List of Ports window.

Per NE Can be selected via the context menu of an
NE or by dragging a NE from the Network
Elements tree.
Per NE name Enter the NE name.
Per port connection line Can only be chosen from the context menu.
Per port connection Enter the name of the port connection in the
Scope field.
The list of Ports contains the following information:

- Index
Counter for each port.
- NE
Name of the network element to which the port belongs.
- Port
Name of the port.
- Port Label
The port label is an additional port information field. The field is only editable here in
the Port List window, i.e. by a double click you can make the field editable and then
start entering a port label.
Note that the Port Label shown here will also be displayed as part of the port name in
other windows, e.g. in the Port / TP fields of the Connection As sistant.
- Subscriber
Subscriber to which the port is assigned.
- Direction
Possible values are source, sink or bidirectional.
- Operatio nal State Tx
Operational state of the sender. Possible values are enabled, disabled.
- Operatio nal State Rx
Operational state of the receiver. Possible values areenabled, disabled.
- Protecting Type
Depending on the protection scheme, e.g. Unprotected, BSHR2 West, BSHR2 East,
MS-LPT Working, etc.
- Loopback State
The following loopback states exist:
Outwards:
loop back the incoming signal from another external device / NE to the external origin.
Inwards:
loopback the outgoing signal to the matrix, i.e., the signal from the NE internal matrix is
sent back to this matrix.
Disabled
for this port there is no switched loopback exists.
Unknown
a loopback is not possible for this port.
227
- Loopback Mode
Port loopback is supported by hiT7050 and hiT7070 and partly by SMA4 Rel. 4 and
SMA 16 Rel. 4.
Port loopback is also supported by FSP150 (only on network FSP150 LE ports),
FSP1500 (supports inward and outward loopbacks in both remote and local interfaces)
and FSP3000 R7.
Two forwarding modes in the case of a port loopback are possible:
Transparent mode:
on a transparent loopback the signal is looped back but also forwarded to its
destination point.
Non-transparent mode:
the signal is looped back but AIS signal is sent towards the original destination point.
Unknown
means that port loopback is not supported.
- Managed by
Shows the management system managing this port. If the port is not managed by a
management system, the text No is displayed.
- Interface Type
Shows the interface type, can be Electrical, Optical or Radio.
Loopback Configuration:
A context menue entry allows configuring port loopbacks. Only the supported configuration
modes are offerd. Once created, the current loopback state as well as other port attributes
are available in the port list, which updates automatically.
The Loopback Mode offers the following sub-entries:
1. Inwards:
Loop back the outgoing signal to the matrix, i.e. the signal from the NE internal matrix
is sent back to this matrix.
- Transparent Mode:
On a transparent loopback the signal is looped back but also forwarded to its
destination point.
- Non-Transparent Mode:
On a non-transparent loopback the signal is looped back but AIS signal is sent
towards the original destination point.
2. Outwards:
Loop back the incoming signal from another external device/NE to the external origin.
- Transparent Mode:
On a transparent loopback the signal is looped back but also forwarded to its
destination point.
- Non-Transparent Mode:
On a non-transparent loopback the signal is looped back but AIS signal is sent
towards the original destination point.
descending order.
and Icons: Lists.
See also:
Support of Loopbacks
228
Client functions
Listing port connections

TNMS Client -> View -> Lists... opens a list window. Clicking on the Port Connections
tab on the bottom displays the List of Port Connections window.
You can also reach the List of Port Connections window directly via:
- the List of Port Connections... context menu of a selected network element
(both in the Network Elements tree and in the Network Plan)
- the List of Port Connections... context menu of a port connection in the Network Plan
When opening the window, use the Request button to show the current contents of the list;
the list only contains a snapshot of the current database content and is not updated
automatically.
Use the Update button to update the list content. After dropping a valid source in the
Scope field the list is updated automatically.
settings.
Use the Capacity option, to calculate total allocated capacity A<->B and B<->A for all port
connections. A Request is necessary to display the information.
When you open the window from the context menu of a port connection line the scope is
automatically set. All port connections belonging to this line are displayed in the list.
When you open the list from the context menu of a network element, the scope is
automatically set. All port connections beginning or ending in this network element are
displayed in the list.

Used by path You can move the path per drag & drop from the
service tree.
Used by path name Enter the path name.
Per NE Can be selected via the context menu of an NE or
by dragging a NE from the Network Elements
tree.
Per NE name Enter the NE name.
Per port connection line Can only be chosen from the context menu.
Note:
The scope type Per port connection line can only be listed from the context menu of a
port connection line.
The list of Port connections contains the following information:

- Index
Counter for each port connection.
- Description
The description of a port connection can be set deliberately by the operator. If a
description is not entered, TNMS Core/CDM suggests a description as follows:
Identification of the start and the end port of the port connection within the relevant
network element, port types, number of the slot, number of the port within the module.
229
- Source NE
NE to which the source port belongs.
- Source Port
Port (of the Start NE) where the port connection starts.
- Destination NE
Network element where the port connection ends.
- Destination Port
Port (of the End NE) where the port connection ends.
- Layer
Displays the transmission capacity.
- Direction
Bidirectional or Unidirectional.
- Stored in NE
Indicates whether the port connection is managed by an NE (yes) or by TNMS (no).
- Admi n State
Locked means that this port connection cannot be used for automatic routing.
Unlocked means it can be used for automatic routing.
- Costs <n>
Weighting according to the cost factors defined in TNMS SysAdm in. More information
- Total Allocated Capacity A->B and B->A
Indicates the capacity of the port connection that is allocated by managed and
unmanaged open and half open paths. The displayed allocation is independent of the
selected capacity layer. The capacity information is provided in separate columns for
each signal direction.
- Cable Conduits
Displays the name of the cable conduits in which the port connection is running. In
order to achieve a high availability of protected services working path and standby path
should not use the same cable conduit.
Operational State of the displayed port connection.
- Ac know ledge State
- Ac know ledge Time (Lo cal Time)
By right-clicking in the window, you can activate a context menu with the following
functions:
- Capacity
Calculate the total allocated capacity A->B and B->A for the selected port
connection(s). The total allocated capacity is defined as the SDH occupied bandwidth.
When Ethernet services use a specific SDH path it is assumed that the SDH capacity
of the path is fully used.
- Port Connection Info…
In Network Editor mode the window Edit/Delete Port Connection is opened. The
user can edit the port connection in this window. In Surveillance and in Service mode,
however, the window Port/Path Information is opened. This is a read-only window
which provides information about the port connection.
and Icons: Lists. By left-clicking the column title, individual columns can be sorted in
230
Client functions
ascending or descending order.
See also:
231
Disabled Port Connections

Disabled Port Connections window is available through TNMS Client -> Fault ->
Disabled Port Connections.... This window shows a table view of all the disabled port
connections in the network.
The list of Disabled Port Connections contains the following information:

- Index
- Description
The description of a port connection can be set deliberately by the operator. If a
description is not entered, TNMS Core/CDM suggests a description as follows:
Identification of the start and the end port of the port connection within the relevant
network element, port types, number of the slot, number of the port within the module.
- Source NE
NE to which the source port belongs.
- Source Port
Port (of the Start NE) where the port connection starts.
- Destination NE
Network element where the port connection ends.
- Destination Port
Port (of the End NE) where the port connection ends.
- Layer
Displays the transmission capacity.
- Direction
Bidirectional or Unidirectional.
- Stored in NE
Indicates whether the port connection is managed by an NE (yes) or by TNMS (no).
- Costs <n>
Weighting according to the cost factors defined in TNMS SysAdm in. More information
- Cable Conduits
Displays the name of the cable conduits in which the port connection is running. In
order to achieve a high availability of protected services working path and standby path
should not use the same cable conduit.
Operational State of the displayed port connection.
- Ac know ledge State
Ac know ledge Time (Lo cal Time)
Displays the time in which the acknowledgement took place
filter functions and displaying port connection functions.
By activating the context menu and choosing the Column Settings… menu item you can
choose which columns are displayed and their order.
By left-clicking the column title, the columns are sorted in ascending or descending order.
232
Client functions
and Icons: Lists.
See Als o
233
Listing termination points

TNMS Client -> View -> Lists... opens a list window. Clicking on the Termination Points
tab on the bottom displays the List of Termination Points window. You may alternatively
access this window via the List of Termination Points... context menu of a network
element or a port connection.

- Per port connection When selected, enter the name of the port connection in the
Scope field.
- Per port connection Can only be chosen from the context menu.
line
- Per NE When selected, you can move the NE per drag & drop from
the Network Elements tree into the Scope field.
- Per NE name Enter the NE name in the Scope field.
Scope: To change the Scope of the list use the Scope Type field
and select the kind of filter you want to set (Per port
connection, Per port connection line, Per NE, Per NE name).
You may also edit the Scope field to filter the list if required.
In the latter cases, the Scope Type is preselected.
Layer: The drop down menu for possible layers to choose.
When opening the window for the first time, use the Request button to show the current
contents of the list; the list only contains a snapshot of the current database content and is
not updated automatically; use the Update button to update the list content. After dropping
a valid source in the Scope field the list is updated automatically.
settings.
Upper List: The List o f Termination Points contains the following information:
- Index
Counter for each termination point.
- NE
Name of the network element to which the termination point belongs.
- Port
Identification of the port within the network element: port types, number of the slot,
number of the port within the module.
- TP
Layer (e.g. VC4) and type of the termination point. Existing Types:
CTP: Connection Termination Point; TTP: Trail Termination Point; CGTP: Contiguous
Group Termination Point, VGTP: Virtual Group Termination Point.
- Usage
Usage state: idle, active or busy.
- Layer
Indicates the transport layer.
- Termination Mode
Indicates the Termination Mode: terminated, non terminated or mapped.
Indicates the Operational State: enable or disabled.
- Bandwidth Sink (Mbps)
Shows the bandwidth (Mbps) of the sink.
234
Client functions
- Bandwidth Source (Mbps)

Shows the bandwidth (Mbps) of the source.
functions (among other entries for filter and sort functions):
- Usage Details
Select a termination point. Once you have activated theUsage Details context menu,
a list of subscribers, services and paths related to the selected termination point is
displayed in the lower section of the window (see below).
- Subelements
Shows the TP structure below the selected TP. If a VC4 TP is selected, for example,
all TPs (VC3/VC2, etc.) are listed.
descending order.
and Icons: Lists.
Lower List: Subscriber/services/paths related to selected TP

Once you have activated the Usage Details context menu of a TP, the following
information is displayed in the list. With the Details context menu you can show the
contents of the selected log in a separate Details window.
- Index
Counter for each path related to selected termination point.
- Subscriber
Name of the subscriber to whom the related service is assigned.
- Service
User friendly name of the related service.
- Path
User friendly name of related path.
- Layer
Transmission layer (e.g. VC4).
- Direction
Bidirectional or unidirectional .
- ACS
Actual Creation State: active, not active, not routed, unmanaged, under test or in
deletion.
By right-clicking in the window, you can activate a context menu with several functions, e.g.
filter functions and a function for displaying termination point details.
Path Properti es….
Opens the Path Properties window.
descending order.
and Icons: Lists.
See also:
235

Port and TP filter settings are available e.g. in the windowsPath Wizard - Define
Topology, Port Connection and Connection Ass istant by selecting the Subscriber ,
Layer or Settings filter in TNMS Core/CDM.
Multiple selection of filter options is possible via the <Ctrl> or <Shift> key.
You can set the filters below from the drop down menu:
Symbol Description
No filter.
Port connection filter.
Cross connection filter.
Operational state filter.
Subscriber filter: Enter the exact name of the subscriber you want to filter.
Layer filter: Select the transmission layer from the drop down menu.
Gateport filter
External NE ID filter
Settings: Set the display settings.
Note:
When clicking the button Ap ply to all the actual filter settings are applied to
all route elements that have previously been drawn into thePort / TP fields
of the concerned windows (e.g. Path Wizard - Define Topolog y window,
Connection As sistant, Create Port Connection window, etc).
You can activate / deactivate the following filter settings:
- Show structured TP list
Clicking this box will show a structured TP list (tree structure) in the
Connection Assistant.
- Show modules with ports only
Clicking this box will show only these modules in the Connection
Assistant, which can be used for routing, instead of showing all the
modules of the NE.
- Use alphabetical sorting (also sorted NE)
Clicking this box will show the alphabetical sorting in the Connection
Assistant instead of numerical sorting (numerical sorting means:
sorting with the slot number).
- Use enhanced Tooltips
Clicking this box shows the tooltips for the ports / TPs in the
Connection Assistant in a packed manner, i.e. only the relevant
information will be shown.
You can also select the filter settings from the Port Filter Settings window:
The window is invoked e.g. by clicking on the Subscriber filter entry. In the window, you
can select values from the drop down list for:
Subscriber , Layer and External Sub NE ID and de-/select tree structure settings under
Display Settings.
See also:
Editing/Deleting a port connection
236
Client functions
Creating VLAN assignment

Assigning a VLAN-Id can be made via port/TP-tree of the path wizard. When an Eth port is
in VLAN concentrator mode the context menu for its contained GFPC-TPs offers the entry
"Create VLAN Assignment" allowing you to enter the VLAN-Id.
As a prerequisite, the port must be in VLAN concentrator mode. This can be performed via
the NE Element Manager.
- Choose VLAN Identifiers

When creating an Eth path using VLAN concentrator, assign a VLAN-Id out of the
value range 1 – 4094 and specify the required bandwidth (for both directions) of the
path.
The path bandwidth is treated in the same way as for other Eth paths running over GFP
group trails however with one difference: The required bandwidth for the Eth TPs of the
VLAN concentrator is not configured in the NE but it will be treated as actual bandwidth of
this TP in the following: If you don’t specify a required bandwidth (setting the required
bandwidth to 0 while creating the path) TNMS sets the required bandwidth to the
bandwidth provided by the net (e.g. 1000 Mbps for 1000Base).
However, it is recommended that you specify known limitations of the bandwidth to use the
capabilities of TNMS bandwidth management. Changes of bandwidth limitations shall be
entered as changes of the required bandwidth of the path topology.
The VLAN Assignment is supported by the Surpass hiT 7070 and Surpass hiT 7050 NEs.
Bandwith Management:
In a scenario of a Packet Device (PD) acting as counterpart of the VLAN concentrator, PD
multiplexes all VLANs in one physical line.
Policing of bandwidth is performed in the input ports of PD (representing individual VLAN-
Ids) for the transmission direction from PD to the VLAN concentrator, and in Eth port of
other hiT for the opposite direction.
In order to make use of the TNMS bandwidth management capabilities (control of
overbooking, bandwidth mismatch), the bandwidth values configured for PD shall be
entered as required bandwidth values (in the according direction) for the Eth paths at the
VLAN concentrator.
See also:
Remove VLAN Assignment
237
Remove VLAN Assignment

When a VLAN is no longer in use, you have to remove the assignment of the according
VLAN-Id. The function for removal of VLAN assignment is offered in the context menu of
the Eth-TP belonging to the VLAN-Id.
To modify a VLAN-Id, remove the assignment and create a new one.
See also:
Create VLAN assignment
238
Client functions
Protection
Addi ng protect io n to a path automatical ly
In order to add protection to a path automatically you have to perform the following steps:
1. In the TNMS Core/CDM Client, select the desired path in the Subscribers and
Services tree.
2. From the context menu of the path select Properties… The Service / Path Properties
window of the respective path appears.
3. Here, select the Routing tab.
4. Select a path from the list on the left and switch to theEdit Mode.
5. In the graphical view select the head NE and open the context menu ->Add
Protection -> <protection item>. Please note that during the routing operation
disabled resources will not be used.
Three Add Prot ectio n items will be offered:
- Port di verse
The protection route never uses port resources used by the working route.
- Cable diverse
The protection route never uses a port connection on the same cable layer used
by the working route (includes port diversity).
- NE diverse
The protection route never uses NE resources used by the working route,
except for those NEs where the A and Z endpoints are located.
6. Press the Appl y button in the toolbar to confirm your modifications.
See also:
Adding protection to a path manually
239
Addi ng protect io n to a path manually

Protection can be added manually to a cross connection via theConnection As si st ant
window of the TNMS Client.
1. Open the Service / Path Properti es... window and select the Routing tab.
2. Click the button Edit Mode.
3. In the graphical view at the top of the Service / Path Pro perties window click the head
NE, i.e. the NE where the protection path should start, and open theConnection
As si st ant window via the context menu.
4. In the center of the window a large icon indicates the current type of cross connection.
Click the arrow on the right of this icon and select the protection template for the head
NE, e.g. for a bidirectional protection:
For more information on the protection types available, see Connection Assistant.
5. Select a Protecting Port/TP for this cross connection, i.e. Port / TP Z(2) and click the
button Modify to redefine the cross connection.
Alternative: use the Shift & Modify Existi ng context menu of the navigation button to
proceed with the next network element. Note that the modified cross connection is
displayed as unprovisioned because at this stage your changes have not yet been
applied to the network element.
6. After you have switched to the next network element via the green arrow the default
connection template for this network element is shown. Continue by routing the
protecting path in the same way as for an unprotected path (seeCreating a path until
you reach the point where the path protection is to be terminated again. Usually this is
the rightmost NE of the unprotected path).
7. For the tail NE, i.e. for the NE where the protection path should finish, select a new
protection template in the center, e.g. for a bidirectional protection:
8. Select a Protecting Port/TP for this cross connection, i.e. Port / TP A (2) and click the
button Modify to redefine the cross connection.
9. Finally, close the Connection Ass istant and click Appl y in the Service / Path
Properties window.
See also:
Adding protection to a path automatically
Creating a path
Routing options
240
Client functions
Creating BSHR or line pr otection

Before creating any Multiplex Section Protection (MSP) with TNMS Core/CDM, you need
to equip the network element with the appropriate cards and assign protection to them via
the LCT or EM. If using the EM from TNMS Core/CDM use the context menu of the card
and select Protection… A list of possible protection methods (e.g. BSHR or Line) is
displayed. Select the desired protection and confirm withCreate.
In the TNMS Core/CDM Client you have to perform the following steps for each NE you
want to include in the protection group:
1. Create a port connection between the NEs you want to protect. More information is
provided under Creating a port connection.
2. Create a protection group for each NE. In the Network Plan change toNetwork Editor
mode and select Protection Groups… from the context menu of the NE. A list of
possible protections methods for the NE appears. The following entries are displayed:
Index: number of row in the list
Scheme: BSHR or Line
Layer: transmission layer
Identity: card and slot of NE
As si gnment: assigned or unassigned
3. Assign protection to each NE. Select an unassigned protection and pressCreate. The
protection is assigned to the NE and the MS Protection window appears.
4. Select the Protection Group tab. With the green arrows you can navigate through the
NEs for which you have performed the previous steps. The Node Ids within the BSHR
are then added to the list on the left. For more information on the possible settings see
Displaying / modifying the properties of MSP.
5. Press Apply to complete the protection process.
BSHR groups fo r direct integration of Surpass hiT7020/25/30/35/60/60HC

When changing the configurations of BSHR protection groups using the LCT of Surpass
hiT7020/25/30/35/60/60HC, you have to resynchronize the NE in TNMS Core/CDM (when
direct integration is being used).
To resynchronize the NE in TNMS Core/CDM do the following:
3. In the Network Plan of TNMS Core/CDM client change to Network Editor mode.
4. Open the context menu of the NE and selectResynchro nize Data… option.
Perform this operation on each of the NEs of the ring.
241
Displaying / modifyi ng the properties of MSP

In order to modify the settings of an existing MSP, open TNMS Client and proceed as
follows to open the MSP properties page:
- Select the protection in the Network Infrastructure tree and choose Properties… from
the context menu.
- Switch to Network Editor mode and select MS-Protections… from the context menu
of the NE.
Any changes in this window have to be confirmed with the Appl y button.
In the MS Protection window you can modify several settings. On the left of the window,
the selected protections, NEs and node IDs are displayed. For information of the used
icons see: Icons: Network infrastructure and protection.
Examples of protection types are explained below:
SPI-OS16-TTP 503 Without protection

SPI-OS16-TTP-W 503 Working port in a MS-LTP
SPI-OS16-TTP-P 503 Protecting port in a MS-LTP
SPI-OS16-TTP-e 503 East port in a 2-fibre BSHR
SPI-OS16-TTP-ex 503 East port in a 2-fibre BSHR with extra traffic
SPI-OS16-TTP-w 503 West port in a 2-fibre BSHR
SPI-OS16-TTP-wx 503 West port in a 2-fibre BSHR with extra traffic
SPI-OS16-TTP-eW 503 Working east port in a 4-fibre BSHR
SPI-OS16-TTP-wW 503 Working west port in a 4-fibre BSHR
SPI-OS16-TTP-eP 503 Protecting east port in a 4-fibre BSHR
SPI-OS16-TTP-wP 503 Protecting west port in a 4-fibre BSHR
The MS Protection w indow cons ists of three different tabs:

Properties
- MS-Protections: Displays the name of the selected protection.
MS-Protection Properties
- Label: Name of the selected protection. Can be changed by the operator.
- Layer : Displays the transmission layer.
- Admini st rative State: Locked or unlocked. Can be changed by the operator.
- Operational State: Enabled or disabled.
- Provisioning State: Provisioned or unprovisioned.
Protection-Group Summary Properties
- Scheme: Display of protection scheme, e.g. Bshr2, MsLtp
- Switch Mode: Dual-ended or single-ended.
- Protection State: Depending on the protection scheme, e.g. working, protecting.
- Wait To Restore [sec]: Time interval in seconds that indicates when the protecting
line is switched back to the working line recovered from the failure. Can be changed
by the operator.
- Reversal Mode: Option to indicate whether protection can be reversed.
- Segmentation: Option only for BSHR. Can be changed by the operator.
242
Client functions
Protection Group
- MS-Protections: Displays the name of the selected protection.
- NE: Displays the name of the selected NE.
- Node-ID: Node ID of the current NE. Can be changed by the operator.
MS-Protection Group
- Working/Protecting fields: Depending on the protection scheme (ring or line), the
affected ports of the protection are displayed.
- Operator Command: Depending on the protection scheme (ring or line), the operator
can set several commands, e.g. force to protecting.
- Ad minist rative State: Locked or unlocked. Can be changed by the operator.
- Avail abili ty : Available or unavailable.
- Provisioning State: Provisioned or unprovisioned.
- Scheme: Display of protection scheme, e.g. Bshr2, MsLtp
- Switch Mode: Dual-ended or single-ended.
- Protection State: Depending on the protection scheme, e.g. working, protecting.
- Wait To Restore [sec]: Time interval in seconds that indicates when the protecting
line is switched back to the working line recovered from the failure. Note that QST and
QD2 NEs can only handle full minutes (min. 60 sec. to max. 720 sec. If you enter a
value that is not a multiple of 60 sec. it will be rounded off. Can be changed by the
operator.
- Reversal Mode: Option to indicate whether protection can be reversed.
- Segmentation: Option only for BSHR. Can be changed by the operator.
Al arms
- Index: Number of the row in the list.
- Time (Local): Indicates the time at which the alarm message was sent by the network
element (entry displayed either as Greenwich Mean Time or local time). If the alarm
message does not include time stamp information, the time stamp will be generated by
the TNMS Core/CDM Server. In this case the time value is marked with an asterisk (*).
- NE: Name of the network element from which the alarm is sent.
- Object Type: Identifies the type of the alarming object inside the NE.
- Location: Specifies the identity of the alarming object inside the network element with
up to three dot-separated numbers. The first number usually refers to the mounting
position (slot number) of the equipment that is implementing the object. The second
and third numbers refer to the logical object container inside the equipment in question
(e.g. port index, TP index inside the port).
- Cause: Apparent cause of the alarm message.
- Severity: Alarm level in accordance with the five severities warning, minor, major,
critical or indeterminate.
- Al arm Class: Further entry for classifying the alarm (Communication, Quality,
Performance, Processing, Equipment or Environment).
- Parent Node: Indicates the name of the parent node (e.g. MSN) which contains the
NE.
- State: Status of the alarm message (acknowledged or unacknowledged).
- Ac know ledged b y: Identification of the operator who acknowledged the alarm
message.
- Computer: Computer where the operator mentioned above has logged in.
- Ac know ledge Time (Local): Time when the operator acknowledged the alarm
message.
243
The commands offered in the context menu of the Alarms tab are similar to those of Alarm
list context menu. Only the option Freeze is not supported by the Al arms tab.
By right-clicking in one of the lists, you can activate a context menu in order to filter the list.
descending order.
and Icons: Lists.
See also:
Creating BSHR or line protection
Icons: Network infrastructure and protection
244
Client functions
Listing protection groups

TNMS Client -> View -> Lists... opens a list window. Clicking on the Protection Groups
tab on the bottom displays the List of Protection Groups window.
Alternatively, a list of protection groups assigned to a certain NE can be opened by
selecting an NE in the Network Plan -> context menu -> Protection Groups…
automatically.
Use the Update button to update the list content.
settings.
The list of Protection Groups contains the following information:

- Index
- Scheme
Type of protection, e.g. BSHR 2, 1+1 MS Line Protection.
To see and manage 1:N protection groups, please access the LCT of the specific NE.
- NE
NEs that are assigned to the protection group. This entry is not available when the list
of protection groups is created via the context menu of the NE.
- Layer
Transmission layer of the protection group.
- Identity
Identification of the NE card slot.
- Admi n State
Locked or unlocked. This entry is not available when the list of protection groups is
created via the context menu of the NE.
- Protecting State
Depending on the protection scheme, e.g. working, protecting. This entry is not
available when the list of protection groups is created via the context menu of the NE.
- As si gnement
Indicates whether the protection group is assigned or unassigned to a network
element.
- Operator Command
Shows the MSP/BSHR state as initiated by the operator. Possible values are e.g.
Clear, Locked/Forced to Worker , Forced to Standby, etc. In the case of a BSHR4
protection there are two commands possible. In this case the two command strings are
shown within the column delimited by a slash "/".
descending order.
and Icons: Lists.
245
Removing path protection automatically

In order to remove protection from a path automatically you have to perform the following
steps:
1. In the TNMS Core/CDM Client, select the desired path in theSubscribers and
Services tree.
2. From the context menu of the path select Properties… The Service / Path
Properties window of the respective service appears.
3. Here, select the Routing tab.
4. Select a path from the list and switch to the Edit Mode.
5. Select the head NE, open the context menu -> Protection and select Remove
Protecting Path.
6. Select the tail NE and open the context menu -> Protection. A dialog box will appear:
Proceed removing selected protection path?. Confirm the question with Yes.
7. Click the Apply button in the toolbar to confirm your modifications.
See also:
Removing path protection manually
246
Client functions
Removing path protection manually

Protection can be removed manually from a path via theConnection As si st ant window of
the TNMS Client.
1. Open the Service window via Properties... context menu of the service to which the
protecting path to be removed is assigned.
2. Select the Routing tab.
3. Select one of the protected cross connections in the graphical view at the top of the
Service window.
4. Open the Connection Ass istant window.
5. Click the button Remove of the toolbar and select Remove Protecting. You can
remove the working Port/TP in the same way.
6. Select the other cross connection at the end of the protecting path in the graphical
routing view of the Service window.
7. Click the button Remove in the toolbar of the Connection As si st ant window again,
and select Remove Protecting.
8. To remove the remaining protection path which is no longer connected to the working
path, switch to the Service window again. Select this path in the graphical view in the
Service window and press Delete.
Note:
Protection (closed and half-open) can also be removed automatically from a path.
See also :
Removing path protection automatically
247
Services
Creating a service
A service is defined as structuring element of the Subscribers and Services tree that can
contain one or more paths.
In order to create a service,
1. open the context menu of the Subscribers and Services tree title bar and select
Create Service… The Path Wizard - Properties window is opened.
2. Define the service label.
3. Click the Create button in the toolbar.
If you want to create a path for this service, do not clickCreate but Next and follow the
instructions for creating a path.
See also:
Creating a path
248
Client functions
Deleting a service
1. Select the service to be deleted in the Subscribers and Services tree of the TNMS
Client.
2. Click Delete in the context menu. As a result, the service is deleted including all
existing paths assigned to the service.
249
Locking/unlock ing a path or a service

Locking a service:
Select the service in the Subscribers and Services tree and open the context menu.
Select lock and all path belonging to the service will be locked.
Unlocking a service:
Select the locked service in the Subscribers and Services tree and open the context
menu. Select unlock and all path belonging to the service will be unlocked.
Locking a path:
Select the path in the Subscribers and Services tree and open the context menu. Select
lock and the path will be locked. A locked path is excluded from autorouting.
Unlocking a path:
Select the locked path in the Subscribers and Services tree and open the context menu.
Select unlock and all path will be unlocked. A unlocked path is not excluded from
autorouting.
Note:
The administrative state of a service/path is displayed by an icon shown on the left of each
service in the Subscribers and Services tree.
Resources can be explicitly or implicitly locked.
See also:
250
Client functions
Modifying th e properties of a service

1. Switch to the Services mode of the TNMS Client.
2. Open the Service / Path Properties window using the Properties... context menu of a
service.
3. The Servic e / Path Properties window shows the general attributes of the service.
Some attributes can be edited (e.g. Service Label or Path Label and Admi nist rative
State). For further information please refer to Service / Path Properties.
4. Press Appl y.
See also :
Creating a service
251

For detailed information about a service or a path:
1. Switch to the Services mode.
2. Select a service from the Subscriber and Services tree and then Properties... from
the context menu. The Service / Path Prop erties window (also named Path
Properties window when invoked from a path without a service) opens in the
Properties view.
If only a service exists but no path for the service, you can get information on the
selected service. Only the tab Properties is visible at the bottom of the window.
If the service is already in use by another client a lock symbol is shown near the
service.
If you pass the mouse pointer over the lock symbol the tooltip associated with this
symbol will display the operator’s name and the workstation’s name from which the
lock is being applied.
If at least one path belongs to the selected service, you can get information on the
selected service and on the path. Select a path on the left to display the service and
path information for the selected path.
If the path is already in use by another client a lock symbol is shown near the path.
If you pass the mouse pointer over the lock symbol the tooltip associated with this
symbol will display the operator’s name and the workstation’s name from which the
lock is being applied.
You can switch between the following views by clicking the Tabs at the bottom of the
window:
- Tab: Properties showing general service / path properties.
- Tab: Info showing general information of the selected service / path.
- Tab: Topology giving topology information of the service / path.
- Tab: Routing giving the route information for this service / path.
- Tab: Scheduling giving scheduled information for the service activation.
- Tab: Alarms giving information about alarms by which the service / path may be
affected.
- Tab: Performance Logs giving information about performance logs.
- Tab: History giving history information of the selected service / path.
In the Properties view the following buttons are provided in the button area:
- Ap ply
Applies changes in the current window.
- Check Path
Checks the selected path and displays the result of the route check in the Info Area at
the bottom of the window.
- Delete
Removes the service/a path.
- Bundle
It is used for bundle routing. It bundles the selected paths in the left part of window to
one path bundle. It is also used to group or bundle paths during the process of
applying an activation and/or deactivation schedule to multiple paths.
The left part of the window with the path tree contains the following information:
- Paths
Path list on the left side of the window to select an existing path and show and modify
its information.
252
Client functions
The right part of the window contains the following information:

- Services
Shows the creation date of the selected service where the path belongs to.
(Under certain conditions the drop down menu can show more than one service entry:
If in the Path Li st window at least two paths of two different services belonging to the
same NE container were selected and the context menu entryMultiple Path
Properties… were clicked. In this case you can choose whether to display only the
path(s) of a single service or the paths of all services).
Service Properties
- Service Label
Label for the service. It is allocated when the service is set up.
- Subscriber
Subscriber for whom the service was set up.
Path Prop erties

- Path Label
Label of a path. It is allocated when the service is created.
Disabled: The resources are not in a position to make the path available and
path which are identified as affecting the path. The system knows or assumes that
these alarms will either lead to or signal a service interruption. Another reason may be
the failure or deletion of resources which are required for the path (e.g. cards,
cannot be directly assigned to a port or termination point. All in all, the operational state
of a path is set to disabled, when the RCS is in the stateactive or under test and a
traffic affecting alarm exists.
Enabled: The resources are operable and available.
Protection disturbed: Indicates that a path-disabling alarm is located on the inactive
part of the route.
unknown: The current operational state cannot be determined, i.e. the network element
currently is not available.
- Creatio n State
- Required: Displays the required creation state for the path: Possible values are:
active, not active, not routed, unmanaged, under test or in deletion.
- Actual: Displays the actual creation state of the path. Possible values are:active,
not active, not routed, under test or in deletion.
- Bandwidth State
Displays the actual state of the bandwidth. Possible values are:OK, Mismatch, Trail
Overbooked or Trail Underbooked.
- Bandwidth
- Required: Shows the required bandwidth (Mbps) for the path.
- Actual: Shows the actual bandwidth (Mbps) for the path.
- Admin. State
Locked: The path was locked administratively and will not be used for further
autorouting.
Unlocked: The resources are administratively enabled for the path. To lock this path,
change to Lock and press the Ap ply button.
- Write Protected
If this option is checked, only an operator with administrative user rights may modify or
253
delete this path. All users who are allowed to create services may set the write
protection.
- Allow Impli ci t Deleti on
This option is only relevant if the path is a client path, i.e. the path uses a server path.
If the check box is activated the server path will be deleted when the last client path
using the server path will be deleted. This option is only relevant if the path is a server
path, i.e. the path is used by at least one client path.
- Performance Log
This checkbox allows full control about path related performance logs.
If the option is activated, a path log exists or the performance log wizard will be started
which allows creating a log for the path.
If the option deactivated, the existing path log will be deleted or no path related PM log
exists at all.
- Direction
The direction of the path can be uni-directional or Bidirectional.
- Connection Type
Connection type Illustration Building Rules

simple one edge,
bidirectional: {[A1,Z1]}
unidirectional: {(A1,Z1)}
add drop head 2 edges, common A
bidirectional:
• {[A1,Z1], [A1,Z2]}
unidirectional:
• {(A1,Z1), (A1,Z2)} (default for unidirectional)
• {[A1,Z1], (A1,Z2)}
• {(A1,Z1), [A1,Z2]}
add drop tail 2 edges, common Z
bidirectional:
• {[A1,Z1], [A2,Z1]}
unidirectional:
• {(A1,Z1), (A2,Z1)} (default for unidirectional)
• {[A1,Z1], (A2,Z1)}
• {(A1,Z1), [A2,Z1]}
double add drop 4 edges, pair wise common A / Z
bidirectional:
(not fo r CC) • {[A1,Z1], [A1,Z2], [A2,Z1], [A2,Z2]}
unidirectional:
• {(A1,Z1), (A1,Z2), (A2,Z1), (A2,Z2)} (default for
unidirectional)
• {[A1,Z1], (A1,Z2), (A2,Z1), (A2,Z2)}
• {[A1,Z1], [A1,Z2], (A2,Z1), (A2,Z2)}
• {[A1,Z1], [A1,Z2], [A2,Z1], (A2,Z2)}
• …
15 unidirectional variants.
unknown all other arrangements
254
Client functions
- Connection Class
Possible values are: Trail, Half Open SNC, Open SNC, LC_TC (Link or Tandem
Connection), Trail And Half Open SNC, Trail And Open SNC or unknown.
- Path Layer
Path layer based on Terminated and Non-terminated layers of the path and on its
Connection Class. E.g. P12 on VC12, RS1, 10/100Base, ESCON on OCH, VC4, VG
(VC4-4v), MS64, P0 x 2.
- Fragment Layer
The fragment layer is dependant from the Terminated Layer Set. If the Terminated
Layer contains concatenated signals, e.g. VC4-4c, then the fragment layer field
contains the layer from which the concatenated signal is composed.
- Nx Count
Relevant for virtual concatenation and for PDH network elements with n*64Kbit/s
cards. For a path with 64Kbit/s the Nx Count value is 1, for e.g. 256Kbit/s the NX Count
value is 4.
- Termin ated Layer Set
Terminated layers of a path edge according the generic rules, e.g. VC12.
- Nontermin ated Layer Set
Non-terminated layers of a path edge according the generic rules, e.g. P12.
See also:
Alarm correlation for a path
Service / Path Properties: scheduling
Concatenation
Handling Server Paths and Client Paths
255
Service / Path properties: alarms

After selecting Al arms all alarms of all TPs relevant for the traffic direction of the selected
service/path are displayed – irrespective of the actual states of protection switches. I.e. for
paths with protection it may occur that alarms are displayed which usually would affect the
traffic, but nevertheless the operational state is displayed asenabled.
The following information is available:

- Services
- Path Label
Path can be in state Disabled, Enabled, Protection disturbed and unknown.
- Al arm Correlation
TNMS supports several alarm correlation methods; choose the appropriate method
according to the following meaning:
- Off: Automatic Alarm Correlation is switched off.
- Normal: This is the default alarm correlation, only path endpoints are considered
for the alarm correlation.
- Extended: All TPs/ports are correlated along the active path route. The operational
state of all server paths is considered too.
- Manual Correlation: In most cases the primary alarms are not likely to occur at the
path endpoint. Since secondary alarms might be suppressed, the reliability of the
automatically correlated operational state is limited. Therefore manual alarm
correlation can be chosen to avoid the limitations of the automatic alarm
correlation.
Note: Manual alarm correlation is only static, i.e. a change of the alarm state is
only visible after an update has been performed.
- Al arm Mask
Setting box with predefined filters for alarm suppression. Following possible filters can
be chosen: Enable Primary alarms, Enable Secondary alarms at service endpoints,
Disable all alarms. More information is provided under Alarm suppression for a path.
The commands offered in the context menu of the Alarms tab are similar to those of the
Alarm list context menu. Only the option Freeze is not supported by the Al arms tab.
In general the alarms of server paths are not displayed in alarm list of the corresponding
client paths.
256
Client functions
Service / Path properties: hist ory

The window shows the history of occurred event types for a selected path. The information
is transferred from the Network Event L og to the history window. The information about
the occurred event types may be useful e. g. in case of fault analysis concerning path
management.
Paths
Path list on the left side of the window to select an existing path and show and modify its
information.

- Services
- Index
- Time (local)
Shows the local date and time when the event type occurred.
- Event Type
Shows the occurred event of the path, e.g. Object created or Attribute value changed,
etc.
- Description
Shows a more detailed description of the occurred event type.
- Operator
Shows the name of the operator who originally initiated the event.
- Computer
Shows the computer name where the operator mentioned above was logged in.
A double-click into one of the fields above opens the Details window with the historical
path information.
Button
The Delete button at the top of the window deletes the selected path.
257
Service / Path properties: info

The window provides general information for the selected Service/Path.
- Paths
its information.

- Services
- Path Label
- Info Message
- Comment
You can enter a textual description for the Service/Path here.
See also:
258
Client functions

Buttons
- Ap ply saves your modifications and applys them.
- Edit Mode toggles between Edit and View mode. Only in Edit mode you can modify
your settings.
- Check performs a route check. See system information in theInfo Area.
- Ac ti vate activates the route, this implies RCS is set to "Active". See system
information in the Info Area.
- Deactivate deactivates the route. This is only possible for previously activated routes.
It implies RCS is set to " "Not Active". See system information in the Info Area.
- Expand toggles between the view modes collapsed, optimized, full.
View mode “Expand full” is not supported for LCAS Services. Selecting this view may
lead to wrong displayed paths. Use the collapsed view mode for LCAS paths.
- Route starts the auto router for the given topology depending on the context either for
one protected or unprotected edge or for more than one edge (“bundled” path
creation). If configured in Options -> Automatic Routing Options , the Exclud e NE
from Routing window is opened to exclude NEs from routing.
- Bundle is used for bundle routing. It bundles the selected paths in the left part of
window to one path bundle.
Paths
Path list on the left side of the window to select an existing path and show and modify its
information.
The upper part of the window contains the following information:

Services
(Under certain conditions the drop down menu can show more than one service entry: If in
the Path Li st window at least two paths of two different services belonging to the same NE
container were selected and the context menu entry Multiple Path Properties… were
clicked. In this case you can choose whether to display only the path(s) of a single service
or the paths of all services).
The centre part of the window contains the following information:

Graphical display of t he routing results
The graphical view in the upper part of the window shows the routing results for the
involved route elements. Tooltips provide extensive information on the status of the
involved route elements when moving the mouse on the route elements. You can also use
the check boxes to handle tooltips. More information is provided underToolTips for path
creation.
If the complete route consists of route elements with location "Protecting" only, this might
indicate an erroneous configuration of desired working and protecting path. As long as
there is no continous desired working route between edge endpoints, all route elements
appear with location "Protecting".
Context menu entries in th e graphical view
259
Note:
The route elements might appear to be too closely situated next to each other so that you
rather select them in the route elements list and open thePath Prop erties window by
double-clicking.
A context menu of the route elements is available in the graphical view with the following
entries:
- Connection Ass istant
Open the Connection Assistant to edit the selected cross connection
- Remove Connection
Use this entry if you want to remove the connection.
- Edit Mode
Use this entry to toggle between Edit and View mode.
- Route
- Remove Route
Use this entry if you want to remove the route.
- Bundle Route Elements
Use this entry if you want to bundle route elements.
- Stretch Route Elements
Use this entry if you want to stretch route elements.
- Refresh all TP-Resour ces
Use this entry to update the TP-resources, e.g. the TP-connection states. This
entry is reachable by clicking into the white area of the window.
Note:
Such a manual update may become necessary after a change of the switching
state (e.g. after CC creation or deletion or add / remove protection). The opened
window does not automatically update such a change of the switching state.
- Take Topology from Required Route
Use this entry if you want to take the topology from the (modified) route.
Notes:
After completion of the action, the topology is presented to the operator and the
Appl y button is released.
If the route can be split into two or more subroutes which are not connected with
each other, one or more new path(s) is (are) created.
- Re-route
- Common Re-routing
taken as start and end point for the new route. Locked resources will be
excluded.
- Diverse Re-routing
taken as start and end point for the new route. Locked resources and the route
belonging to the selected path will be excluded.
- Specific Re-routing
connection for diverse re-routing. Locked resources and the route belonging to
the selected path will be excluded. Additionally, you have to perform the
following steps:
a) Exclude NE: Drag the NEs you want to exclude from the routing process
from the Network Plan into the box. Click Next to confirm your selection.
c) Protection options: Select NE diverse or cable diverse path protection. Click
Next to confirm your selection.
- Global Re-routing
260
Client functions
- Global Re-Routing with Template

By sel ecti ng t hi s opt i on you i ni t i at e a gl obal - r e- r out i ng
or der wi t h t empl at e. Thi s opt i on i s avai l abl e i n case of
al r eady bundl ed pat hs.
- Protection
- Add Prot ectio n
Use this entry to add a protection.
- Remove Protecting Path
Use this entry if you want to remove a protecting path.
- Remove Worki ng Path
Use this entry if you want to remove the working path.
The lower part of the window contains the tabs Info Area, Route Elements and Path
Edges:
a) Info Area
b) Route Elements
- RE Type
Shows the type of the route element, e.g. Cross Connection.
- Name
Shows the name of the route element.
- A-End
Start point of the route element.
- BCM (A)
The border crossing mode A indicates entry or exit point as a text field for the port /
TP.
- Z-End
End point of the route element.
- BCM (Z)
The border crossing mode Z indicates entry or exit point as a text field for the port /
TP.
- Layer
Displays the transmission capacity, e.g. VC4.
disabled: The resources are not in a position to make the service available and
path which are identified as affecting the service. The system knows or assumes that
these alarms will either lead to or signal a service interruption. Another reason may
be the failure or deletion of resources which are required for the path (e.g. cards,
cannot be directly assigned to a port or termination point.
enabled: The resources are operable and available.
unknown: The current operational state cannot be determined, i.e. the network
element currently is not available.
- Ac tu al Creation State
Shows the actual creation state of the route element. Possible values areactive, not
active, not routed, undefined, under test.
- Location
The location state of the path can be working/protecting.
261
- Protection State
The protection state can be none/working/protecting.
- Direction
Shows the direction of the route, either uni-directional or bi-directional.
- Bandwidth A -> Z
Shows the bandwidth for the direction A -> Z.
- Bandwidth Z -> A
Shows the bandwidth for the direction Z -> A.
c) Path Edges:
- Index
- Direction
- NE
- Port / TP(A)
Start port / end termination point for the path.
- NE
Name of the sink network element.
- Port / TP(Z)
- BCM(A)
- BCM(Z)
- Resilience A-Z
- Resilience Z-A
- Layer
Displays the transmission capacity of the service, e.g. VC4, MS16, etc.
- Bandwidth A-Z
- Bandwidth Z-A
By double-clicking on a route element, the Path Properties window will be opened.

By right-clicking in the lists, you can activate a context menu in order to filter the list.
descending order.
More information is provided in Setting filters and sorting lists and Icons: Lists.
See also:
Activating/Deactivating a path
262
Client functions

Icons: Routing
263

- Paths
its information.
The upper part of the window contains the following fields:

- Services
Note:
For the Port / TP <X> fields a context menu entry Refresh TP-Resources is available:
Use this entry to update the TP-resources, e.g. the TP-connection states. This menu
entry is available by clicking into the Port / TP <X> field with the right mouse button.
Such a manual update may become necessary after a change of the switching state
(e.g. after CC creation or deletion or add / remove protection). The opened window
does not automatically update such a change of the switching state.
- Port / TP A (1)
On the left, the Exit / Entry points for this NE can be defined through a button. Filtering
is also possible; see filtering description below.
- Port / TP Z (1)
Filtering is also possible; see filtering description below.
- Port / TP A (2)
below.
- Port / TP Z (2)
below.
- Filter
Each Port / TP field allows filtering using predefined filter criterias. They are displayed
as icons. Tooltips show the meaning of icons. The filter criteria are:
- No Filter
- Port Connection Filter
- Cross Connection Filter
- Operation al State Filt er
264
Client functions
- Subscriber Filter
- Layer Filter
- Settings Filter
- Restrict Layer
If displayed, this field offers specific layer selection, depending on the chosen NE
above.
Note:
This field is only visible when in the Options window the check box Show Layer
Options.
- <Topology template>
Contains templates for the connection type. More information is provided underIcons:
Port Connections, Path Wizard and Connection Assistant
Note:
In case a topology is not defined through the topology templates (e.g. broadcast), a
warning message will be displayed. In TNMS Core/CDM, however, you can use the
undefined topology although it is not part of the template.
- Resilience
are: unprotected or protected.
The lower part of the window contains the tabs Info Area and Edges:
a) Info A rea
b) Edges:
- Index
- Direction
- NE
- Port/TP (A):
Start port / start termination point for the path.
- NE
Name of the destination network element.
- Port/TP (B)
- BCM (A)
- BCM (Z)
- Resilience A-Z
- Resilience Z-A
265
- Layer
Displays the transmission capacity of the service, e.g. VC4, STM-16, etc.
- Bandwidth A-Z
- Bandwidth Z-A
descending order.
and Icons: Lists.
Buttons
- Modify modifies the selected topology edges.
- Ad d the selected edges to the topology.
- Remove removes the selected edges from the topology.
- Delete deletes the selected path.
- Move is used for bundle routing. It automatically moves the endpoints from the old NE
(B) to the new NE (C). Note that the button only appears, if a suitable path bundle
exists.
- Clone is used for bundle routing. It clones the given path topology. After clicking this
button the Clone Edges window opens where you must enter the amount of edges you
want to create.
- Bundle is used for bundle routing. It bundles the selected paths in the left part of
window to one path bundle.
See also:
266
Client functions
Service / Path properties: scheduling

The window provides a way for activating and deactivating paths in a scheduled way. It is
possible to specify the enabling of the schedule, a certain activation/deactivation date/time
and its repetition.
- Paths
its information.

- Services
- Path Label
Scheduled Path Ac tivation

- Enable scheduling fo r path activation or deactivation
Check button to activate the scheduling procedure.
- Ac ti vation Date
Displays the date in which the activation will take place.
- Ac ti vatio n Time
Displays the time in which the activation will take place.
- Deacti vation Date
Displays the date in which the deactivation will take place.
- Deactivation Time
Displays the time in which the deactivation will take place.
- Period
Displays the repetition of the activating and deactivating procedure as Once, Daily,
Weekly or Monthly.
In case of multiple selected paths with different individual configured schedules, the dialog
stays empty. A warning is displayed informing that the configuration will overwrite the
existing schedules.
It is possible to select multiple paths by opening Multiple Path Properties when selecting
multiple paths in the Subscribers & Services tr ee or in the List of Paths followed by
“Bundle”.
See also:
Service / Path properties: alarms
267
268
Client functions
Creating an Ethernet Servic e with LCAS

The following description shows how to configure an Ethernet service using the Link
Capacity Adjustment Scheme (LCAS). The following description uses two Surpass hiT7070
with Fast Ethernet cards.
Prerequisites
The following prerequisites must be met in the two NEs before you begin configuring the
LCAS in TNMS-Core/CDM:
- Ethernet cards available.
- Multiplex structure prepared, e.g., SDH signal subdivided into constituent PDH signals
as VC4(Mux)#1 and VC4(Mux)#2 configured with both TUG-3#1 into 21xTU-12. This is
configured in the NE Element Manager.
- Added concatenation group, in this example, type LCAS VC12-nv and 2 members (TU-
12 1.1.1 and 1.1.2).
- General Framing Procedure (GFP) group assigned, in this case ETH Port #1 as LCAS
VC12-2v #01.
- In TNMS-Core/CDM the NEs must be created with Port Connections defined.
Configuring the Ethernet service w ith LCAS:

1. In the Network Management View window, click in the Service tab.
2. Right click in the first NE and then click Create Servic e in the context menu.
3. In the Path Wizard - Properties window, configure the service and path properties.
4. Click the Next button. This opens the Path Wizard - Define Topolog y window.
5. Drag-and-drop the NEs into the Port/TP A and Port/TP Z fields, and select the
VC12-2v LCAS group in the SDH Interface ports of the Ethernet cards.
6. Press the Add toolbar button to add the selected edges to the topology.
7. Chose Create Automatically when clicking Next. The autorouter searches a
corresponding path with the parameters defined in theRouting Options window.
These can be:
- Routing Optimization (Least hops or cost factors).
- Diverse Routing (NE Diverse, Cable diverse or Port Diverse).
- General Settings
The path route is presented in the Path Wizard - Routin g Results window.
8. Click the Ac ti vate toolbar button.
9. Create the Ethernet service between two Ethernet ports of the IFOFES-E cards.
In the Network Management View window Service tab, right click in the first NE
and then click Create Servic e in the context menu.
10. In the Path Wizard - Properties window, configure the service and path properties.
11. Drag-and-drop the NEs into the Port/TP A and Port/TP Z fields, and select the
Ethernet CTPs.
12. Click the Add toolbar button to add the selected edges to the topology.
13. Chose Create Automatically when clicking Next in the Path Wizard - Define
Topology window.
14. Click the Ac ti vate toolbar button to activate the service and then Close.
See Als o
Creating a service
Deleting a service
269

270
Client functions
Performance Thresholds Configuration

The Performance Thresholds Configuration window allows you to configure the threshold
for the selected performance log.
You can access this window via: TNMS Cli ent -> View -> Tables -> Performance Log
Buttons
- Appl y confirms your settings and leaves the window.
- Close leaves the window.
- Help displays help on this window.
This window has the following panels:
PMP Container
Displays the container that holds the Service / Path.
PMP Tree
Displays the PMPs associated with TPs which are used along the routes, and the PMPs
that belong to the NEs along the route between the path edges.
PMP Lis t
The columns of the PMP list contain the description of the PM parameters and the actual
values of the Supervision for 15min and 24hour and the threshold values for 15minHigh,
15minLow and 24hour.
The columns are:
- Index
- Name
- Descripti on
- Unit
- 15min
- Low
- High
- 24hour
271
Subscribers
Listing subscribers
TNMS Client -> View -> Lists... opens a list window. Clicking on the Subscribers tab on
the left bottom displays the List of Subscribers window.
automatically.
Use the Update button to update the list content.
settings.
For each Subscriber chosen from the list on the left the following Subscriber Information is
displayed:
- Index
Counter for each subscriber.
- Name
Name of the subscriber.
- Organization
Organizational unit to which this subscriber belongs.
- Contact Person
Support contact for the subscriber.
- Address
Address of the subscriber.
- Phone
Telephone number of the subscriber.
- Fax
Fax number of the subscriber.
- Email
E-mail address of the subscriber.
- External ID
External ID of the subscriber (e.g. for an external database).
- URL
URL of the subscriber (e.g. for accessing an external database via internet).
functions:
- Subscr iber Management…
Opens the Subscriber Management window with a list of the created subscribers.
descending order.
and Icons: Lists.
272
Client functions
Subscriber management
To add new subscribers or to manage existing subscribers switch to theServices mode.
Then open the Subscr iber Management window using:
- Configuration -> Subscribers...
- Subscribers & Services -> Create Subs cri ber... (context menu)
- Selection of a subscriber -> Subscr iber Management...
The left area of the window displays a list of the subscribers set up so far. When a
subscriber is selected the associated data is displayed to the right of the entry.
You can perform the following actions:
- Lists
Displays the list of subscribers.
- Ap ply
Saves newly-created/modified data of a subscriber.
- Edit
Edits, i.e. modifies data for the selected subscriber.
- Add
Inserts a new subscriber into the subscriber list.
- Delete
Deletes the selected subscriber.
- Close
Closes the window.
You can specify the following data for a subscriber, the system merely asks you to specify
a unique subscriber name.
- Subscriber Name
Name of the subscriber, has to be unique within TNMS.
Value range: max. 63 characters
- Organization
Name of the subscriber's organization or company.
- Contact Person
Person by which the subscriber is supported.
- Address
Address of the subscriber.
- Phone
Telephone number of the subscriber.
Value range: Combination of digits 0 ... 9, / , +, - with a maximum of 63 characters
- Fax
Fax number of the subscriber.
Value range: Combination of digits 0 ... 9, / , +, - with a maximum of 63 characters
- Email
E-mail address of the subscriber.
Value range: A ... Z, a ... z, 0 ... 9, @, =, blank
- ExternalID
The attribute can be used as a reference to an external database.
- URL
The attribute can be used as a reference to a home page.
273
TNMS server admini str ation

Distributing TNMS Server time
To distribute the TNMS Server time to all reachable components, open the TNMS Client
and select Configuration -> Distribute Time... to open the window Distr ibut e TNMS
Server Time. The window displays the current TNMS Server time
1. Confirm the date and time with Ap pl y. The clocks of all reachable system components
and network elements are set to this time.
2. Click on Close to close the window.
Notes:
You must have administrator access for Windows XP Professional operating system to use
this function.
The time value can only be changed in TNMS SysAdmin. More information is provided in
the SysAdmin online help.
274
Client functions
Universal objects
Creating and modify ing a CC of a uni versal object
Open the UNO element manager in TNMS Core/CDM and complete one of the following
actions to open the Edit CC Properties window:
- In order to create a new cross connection, choose Create CC from context menu of
the relevant TP in the tree pane. The Select TP Z (1) window is opened. The window
consists of the following information:
o Port: Name of the currently selected port.
o TP A: Name of the currently selected TP.
o Tree Pane: Graphical overview of the UNO and its modules, TPs and
CCs.
Navigate through the tree pane, select the desired TP Z and confirm your selection
with OK.
- In order to modify an existing cross connection, choose Edit TP Properties from the
context menu of the relevant TP in the tree pane.
Note: It is also possible to create CCs in UNOs automatically using TNMS Client and the
automatic routing feature. The possibility to add/remove a protection/worker to a CC
automatically is available.
You can specify the following attributes:
Parents
- TP A
Displays the name of the previously selected TP A.
- TP Z (1)
Displays the name of the previously selected TP Z (1).
- TP Z (2)
Displays the name of the previously selected TP Z (2).
Add Prot ectio n…
Depending on the selected Connection Type, this button is active. It opens theSelect TP Z
(1) window for simple, add drop tail or add drop head protection.
Properties
- Connection Type
Choose between UnprotectedBi, ProtectedUniHeadEnd, ProtectedUniTailEnd and
ProtectedBi.
- Connectivity
Displays the cross connection type (static).
See also :
Element manager for universal objects
Configuring a universal object.
Creating and configuring a module of a universal object
Creating and configuring a port of a universal object
Creating and configuring a TP of a universal object
275
Creating and modifying a module of a universal object

Open the UNO element manager and complete one of the following actions to open the
Edit Module Properties window:
- In order to create a new module, choose Create Modul e from context menu of the
UNO net element in the tree pane.
- In order to modify an existing module, choose Edit Properties from the context menu
of the relevant module in the tree pane.

Module Name
- Object Type
The object type (UNO Module) is inserted automatically and cannot be changed.
Location
- Shelf Number
Enter a unique number for the slot shelf within the range from 1 to 65535.
- Slot Number
Enter a unique number for the slot within the range from 1 to 65535. You can edit this
field at module creation only.
See also:
Creating and configuring a CC of a universal object
Creating and configuring a port of a universal object.
276
Client functions
Creating and modifying a port of a universal object

Edit Port Properties window:
- In order to create a new port, choose Create Port from context menu of the relevant
module in the tree pane.
- In order to modify an existing port, choose Edit Port Properties from the context menu
of the relevant port in the tree pane.

Port Name
- Object Type
Select the desired port from a list of possible ports. You can edit this field at port
creation only.
- Service Type
The service type depends on the previously selected object type. You may modify this
field and choose from the following options: PDH, SDH, ATM, WDM, or Ethernet.
- Interface Type
The interface type depends on the previously selected port description. You may
modify this field and choose from the following options: electrical, optical, or radio.
Location
- NE Name
Displays the name of the UNO.
- Shelf Number
Enter a unique number for the slot shelf within the range from 1 to 65535.
- Slot Number
Enter a unique number for the slot within the range from 1 to 65535. You can edit this
field at module creation only.
- Container Index
Enter a unique number for the port within the range from 1 to 65535 to be used as an
index.
Port Capabilities
You may choose from the following options:
- Bund le NX: The port supports bundled SNCs.
- Unidirection: The port supports unidirectional SNCs.
- Protection: It is possible to create protected SNCs.
- Transmitter: It is possible to create a unidirectional port. If this box is not checked, the
transmission direction will not be available. In TNMS Core/CDM it is not possible to
create a bidirectional connection to and from a unidirectional port.
- Flexible: The port supports flexible SNCs.
- Broadcast: The port supports a broadcast connection.
- Port Connectable: It is possible to connect this port to another one.
- Receiver: The port provides a receiver.
See also :
277
278
Client functions
Creating and modify ing a TP of a univ ersal obj ect

Edit TP Properties window:
- In order to create a new termination point, choose Create TP from context menu of the
relevant port in the tree pane.
- In order to modify an existing termination point, choose Edit TP Properties from the
context menu of the relevant port in the tree pane.

TP Name
- Object Type
Select the desired TP from a list of possible TPs. You can edit this field at TP creation
only.
- Port
The port depends on the previously selected TP type and is inserted automatically.
Properties
- TP Index
Enter a unique number for the TP within the range from 1 to 65535 to be used as an
index.
This field is editable in Create-Mode and in Display-Mode.
- NxCount
Enter a unique number for concatenation within the range from 1 to 65535.
See also:
279
Element manager f or uni versal objects

To start the default element manager for universal objects in TNMS Core/CDM, open the
TNMS Client, go to the Network Plan and select Start UNO EM from the context menu of
the desired UNO.
In the tree view in the left part of this window, a hierarchical overview is provided of the
modules, ports, termination points and cross connections or subnetwork connections of the
universal object. Depending on the element selected in the tree, further information about
the selected element and its available subelements will be displayed in a list in the right
part of the window. For further information on the listed information, please refer to the
relevant topics on the configuration on the single elements.
descending order.
and Icons: Lists.
Each element in the tree view has a unique context menu. TheUNO network element
context menu provides the following entries:
- Create Modul e
Opens the Edit Module Properties window.
- Write Access
Toggle between enforcing write access on the selected UNO (ticked) and releasing
write access (not ticked).
- Edit Properties
Opens the Edit NE Properties window.
- Import Data from XML File
Imports configuration data from an XML file to the UNO.
- Export Data from XML File
Exports configuration data from the UNO to an XML file.
The module context menu provides the following entries:

- Create Port
Opens the Edit Port Properties window.
- Delete Module
Deletes the selected module.
- Edit Properties
Opens the Edit Module Properties window.
The port context menu provides the following entries:

- Create TP
Opens the Edit TP Properties window.
- Delete Port
Deletes the selected port.
- Edit Properties
Opens the Edit Port Properties window.
The TP context menu provides the following entries:

- Create CC
Opens the Select TP window.
- Delete TP
Deletes the selected termination point.
280
Client functions
- Edit Properties
Opens the Edit TP Properties window.
The CC List context menu in TNMS Core/CDM provides the following entries:
- Delete CC List
Deletes the selected cross connection list including all CCs.
The CC context menu provides the following entries:

- Delete CC
Deletes the selected cross connection.
- Edit Properties
Opens the Edit CC Properties window.
- Go to…
Jumps to the associated TP A, TP Z (1) or TP Z (2) in the tree view.
The SNC context menu provides the following entries:

- Delete SNC
Deletes the selected subnetwork connection.
- Edit Properties
Opens the Edit SNC Properti es window.
All previously mentioned functions are also available via the menu bar. Additionally, the
menu bar provides the following entries:
Menu Bar Menu Entry Function

Item
File Open XML Open an XML file containing EM data.
Note:
The Open XML entry opens a new
instance of the EM only. This is not an
import of data. You have to select Appl y
Data to write the data to the EM.
Appl y Data Apply your changes to the EM.
In order to display changes to the overview of the UNOs press theRefresh button in the
toolbar.
See also:
281
Modifying a universal object

Start the UNO element manager and select Edit Properties from the context menu of the
UNO. The Edit NE Properties window will appear. You can specify the following
attributes:
- Name
In this text field, you may enter a short description of the NE.
- NE Type
You cannot change the NE Type. It is set when the NE is added via the DCN
Management in TNMS SysAdmin.
- Location
Enter the location of your UNO.
- Icon
In addition to the default UNO icon, you can select a different one from a list of 20
icons. Your selection will be displayed in the tree pane and Network Plan.
See also:
Creating and configuring a port of a universal object.
282
Client functions
283
Index
Glossary and Abbreviations
ACS Actual Creation State.

Activate When a DCN channel is activated under TNMS SysAdm in, contact to the
relevant network elements is established when the TNMS Server is started.
It is possible to activate / deactivate paths:
Activate paths: cross connections are created / alarm suppression settings
in NEs are adjusted.
Deactivate paths: cross connections belonging to this path alone are
removed / alarm suppression settings in NEs are adjusted.
Administrative state
The administration of managed objects operates independently of the
operability and usage of managed objects and is described by the
administrative state attribute, which has the following values:
Locked: The resource is administratively prohibited from performing services
for its users.
Unlocked: The resource is administratively permitted to perform services for
its users. This is independent of its inherent operability.
For path or server path, NE, port connections: Here the Admin Statelocked
means "exluded from routing". Only for these objects the Admin State can
be set explicitly and implicitly.
For MS Protection: locked, unlocked has the meaning of deactivated,
activated.
For PMP: locked, unlocked has the meaning of deactivated activated resp.
stopped, started.
For PM Log: Active, Standby has the meaning of started, stopped.
Administrative state type
Depending on whether a resource for a path has been locked by the
operator when creating the path or whether an underlying resource has
already been locked before e.g. when a server path is created that makes
use of a client path of which a port connection is locked, the following
administrative states for paths are defined:
implicitely locked: The path is running over a locked resource.
explicitely locked: The operator has set the administrative state to locked.
implicitely and explicitely locked: The path is running over a locked resource
and the operator has set the administrative state to locked.
BCM Border Crossing Mode. Each TP, which is known at a given management
level, is part of the "border" of a multi layer subnetwork of that management
level. Regarding a connection of that management level, each connection
endpoint can be characterized, whether it crosses the multi layer
subnetwork border from outside to inside (BCM = entry), or it crosses the
border from inside to outside (BCM = exit).
BSHR Bidirectional Self-Healing Ring.
285
CC Cross Connection
A cross connection is a special sub-network connection implemented by a
single switching network (switching matrix) inside one network element.
Note that as a special case even a cross connection can be a complete trail.
A cross connection is represented by an individual square in the graphical
path view, however, this square can contain several cross container
connections.
CTP Connection Termination Point
Client Service Connections in adjacent transmission layers have a client/server
relationship, which is defined as follows. A trail in a server layer causes a
number (of at least one) of link connections in adjacent client layers, i.e.
client layers which are adapted to a server layer. This is illustrated by the
following diagram:
CDM Cross Domain Manager
CMX Cross Connect Multiplexer

Concatenation
Concatenation allows the transport of a tributary signal with a higher
bandwidth than the nominal path transport capacity (means higher than one
Virtual Container (VC). These concatenated signals can be used to
transport IP and ATM traffic, for example, over SDH/SONET. TNMS
Core/CDM supports contiguous and virtual concatenation of VC4-16c, VC4-
64c, VC4-Xv (with X=2…8, 16, 64), VC3-2v, VC12-Xv (with X=2…21).
Contiguous concatenation means that e.g. X VC4 signals do not float
independently from each other in the STM-N frame. They are concatenated
to one VC4-Xc signal. That means that there is only one AU-4 pointer which
points to the first concatenated VC4. The path overhead (POH) is only valid
for the first VC4.
Virtual concatenation means that e.g. X VC4 signals float independently
from each other in the STM-N frame. They are concatenated virtually to one
VC-4-Xv signal. There are still X AU-4 pointers and X path overheads (POH)
valid for each VC4. The maximum delay between the first and the last VC4
must not exceed 125 ms.
CSD Customer Services Directory
CTP Connection Termination Point
DCN Data Communications Network

Deactivate The deactivated status of a DCN channel is useful for planning and
configuration. No attempt is then made, when the TNMS Server is started,
to establish a connection to associated network elements.
286
Index
DPRAM Dual Port RAM
Element Manager In order to get detailed information on network element layer the
Element Manager application associated with the corresponding network
element has to be started by the operator. Element Manager applications
give full access to all NE data and provide functionality for configuring and
controlling the behavior of the NE, requesting performance values and
alarms, backup and restore of configuration data and much more,
depending on the actual NE type.
FMX Flexible Multiplexer
GCTP Group Connection Termination Point

GFP Generic Framing Procedure
GFPC Generic Framing Procedure Channel
GFPG Generic Framing Procedure Group
GMT Greenwich Mean Time
GUI Graphical User Interface
GTP Group Termination Point
GTTP Group Trail Termination Point
LAN Local Area Network

LCT Local Craft Terminal
287
LL Leased Lines
MIB Management Information Base

Module The module is a generalization of the network element hardware that
implements the functionality of the managed objects.
MLSN Multi Layer Subnetwork
MSP Multiplex Section Protection
MSN Multi-Service Node
An MSN is an umbrella object which enables individual network elements to
be grouped together in a single manageable cluster.
NE Network Element
NE container Symbol for grouping different elements into the User network.
NMS Network Management System
NSAP Network Service Access Point
NTL Non Terminated Layer. All layers contained in this set are not terminated
within the Port / TP, i.e., for each layer in this set there is no standard TTP
which is embedded in the Port / TP object, only standard CTPs may be
embedded. In case of a Port or a terminated/terminable TP the set of non-
terminated layers is the set of client layers supported by this Port / TP. In
this case these layers are not part of the Port / TP object itself, but are
supported by it.
Operational state
The operability of a resource is described by the operational state attribute
which has the following values:
Disabled: The resource is unable to provide service to the user and there is
some correction required.
Enabled: The resource is at least partially operational and available for use.
Unknown: The current operational state of the resource cannot be
determined (e.g. because of a DCN connection failure).
Protection disturbed: Indicates that a path-disabling alarm is located on the
inactive part of the route.
The operational state is supported by the following objects: network
element, port, cross connection, termination point, path, service.
The operational state is derived from the end-point alarms only (this applies
for paths only).
OSI OSI (Open Systems Interconnection) is a reference model for network
communication in accordance with the X.224 protocol and ISO 8073
288
Index
(transport class 4 via a connection-less network service CLNS). The OSI

Stack implements the communication software for this transport layer.
PDH Plesiochronous Digital Hierarchy

Path A path consists of path edges with the assumption, that a pair of path edges
have always a common route point. A path edge is a contiguous sequence
of route elements (RE). A Route Element has two endpoints on the same
layer which are connected and form a CC, a port connection or a server
path reference.
Path edge A path is defined as a series of cross connections which allow data to flow
through the network from one defined access point to another. Further
attributes describe the type of data traffic, the direction, the path users and
the status management information.
Path (closed) Both endpoints are TTPs on the same layer, in a common sense this is a
trail which is monitored end to end.
Path (half-open)
One endpoint is a TTP, the other endpoint is a CTP, in a common sense this
is a half open trail which is not monitored end to end. (Monitored end to end
means: Supervisory for this path is provided in both directions).
Path (open) Both endpoints are CTPs on the same layer, in a common sense this is a
SNC or LC/TC which is not monitored end to end.
PMP Performance Measurement Point.
Port (virtual) Relates to the view on the TNMS Client interface:
For port connections covering a number of NE containers, a symbol for the
virtual port is shown for the network element which lies outside the NE
container currently shown.
Port connection
Physical port connection between two network elements which must be configured by a
user. Some NEs may provide what are known as 'internal port connections'
within one NE. These port connections are created automatically during NE
upload in accordance with the actual NE configuration, and do not need to
be created manually in the TNMS Client network plan.
If such internal port connections are modified or deleted during
reconfigurations of the NE (typically during changes of optical protection
configurations), they need to be deleted in TNMS by the operator.
Afterwards, a reinitialize of the NE needs to be done.
Internal port connections are accessible via the context menu "Port
Connections..." of the NE icon in the Network Management View ("Network
Editor" mode). The state "Stored in NE" indicates that this internal port
connection corresponds to the NE configuration. "Stored in NE = No"
indicates a mismatch between the true physical configuration and the
internal port connections stored in TNMS. A mismatch can result in wrongly
routed paths.
POTS Plain Old Telephone Service. Data transmission from point to point for voice
data.
Protection The quality of protection is expressed by the protection attribute, which may
have the following values:
unprotected: There is no protection for this path. A path of this type has only
two endpoints and no protected cross connection.
289
End-to-end: The protection is completely enclosed inside this path. Paths of

this type have only one termination point at both ends. A path of this type
has only two endpoints and at least two protected cross connections.
half open: The protection is not completely enclosed inside this path. One
endpoint of the protection is not included in the path. There are one
termination point at one end and two termination points at the other end. A
path of this type has one endpoint at one end and at least two endpoints at
the other end.
open: The protection is not completely enclosed inside this path. None of
the endpoints of the protection is included in this path. There are two
endpoints at both ends. A path of this type has at least two endpoints at
each end.
Protection state
This can either be set to none (there is no protection for this path), working
(the path in question is the worker path) or protecting (the path in question is
the standby path).
P-Selector Presentation selector (Q3 only) for network addressing.
Q Standardized management interface

QB3M Driver for linking SDH network elements
QD2 Driver for linking PDH network elements
RCS Required Creation State

RE Route Element
SDH Synchronous Digital Hierarchy

SDF System Data Format
Service A service links path-related information about one or more paths to
subscriber data and service-specific status management information.
SISA Product designation (DCN): Supervisory and Information System for Local
and Remote Areas
SLR Synchronous FO System (Regenerator)
SONET Synchronous Optical Network
STM Synchronous Transport Module
SMA Synchronous Multiplexer Add/Drop
SNC Subnetwork Connection
SNIF+ Service Network Interface +
SNMP Simple Network Management Protocol
S-Selector Session selector for network addressing.
290
Index
T
Task order A task order is a request from one management system to another to
complete one or more operations. These operations may be performed
either manually or automatically.
TL Terminated Layer. All layers contained in this set are terminated within the
Port / TP, i.e., for each layer in this set there is a standard TTP which is
embedded in the Port / TP object.
TMN Telecommunications Management Network
TNMS Telecommunication Network Management System
TP Termination Point
Trail A trail is a connection with terminated endpoints. In TNMS, this occurs:
either as a port connection where both endpoints are ports or as a path with
terminated endpoints where the endpoints are either ports, terminated TPs,
free terminable TPs or mapped TPs.
A mixture of these endpoint types is also possible.
T-Selector Transport selector for network addressing.
TTP Trail Termination Point
UNO Universal Object

Universal objects enable the integration of unmanaged third-party NE
objects within TNMS. These NE objects can either represent a proxy for an
NE which is not supported by the TNMS Core/CDM system, or a different
device with restricted functionality, for example devices without supervising
interfaces (e.g. patch fields, ventilation systems, etc.).
Universal objects can be created, configured and deleted and included in
the network topology using port connections. For this purpose, modules and
ports can be created and deleted (but not modified) for universal objects
using the universal object element manager.
The resources defined for a universal object are stored persistently and are
secured during a database backup.
TIF alarms for a network element can be redirected to a universal object.
Usage state The usage of a resource is described by the usage state attribute, which can
have one of the following values, not all of which are applicable to every
type of resource:
idle: The resource is currently not in use.
active: The resource is in use and has sufficient spare operating capacity to
provide for additional users simultaneously.
busy: The resource is in use and has no spare operating capacity at this
instant.
The usage state attribute is supported by the termination points.
User class For access to TNMS Server functionality there are five user classes,
graduated according to the degree of access rights granted to the user. The
next-higher user class in each case has all the rights of the classes below it.
User network Network to be administered and defined by the user.
291
VPN Virtual Private Network
WAN Wide Area Network

WDM Wavelength Division Multiplex
XML Extensible Markup Language
292
Index
A secondary 127
abbreviations 4 severities 122, 124, 128, 258, 290
access 4, 5, 171, 178, 180 show 132, 142, 173, 193
acknowledge 116, 124, 126, 128, 142, 173, state 128, 258, 290
193, 258 suppression 127, 207
acoustic signal 134 update 140, 142
ACS 49, 61, 226, 267, 270, 290 application 2
actual creation state 49, 61, 226, 267, 270, TNMS Core 2
290
archive 79, 82, 165
add 168
automatic 118, 219, 225, 247, 277, 286
a new NE or subnetwork to a NE
container 168 alarm correlation 19, 118
protection to a path automatically 277 path creation 219, 225, 247, 286
protection to a path manually 278 protection 277
AddIn for RPR Manager 19 automatic router 212, 245
address 311 automatic routing 219, 225
list subscriber 310 B
subscriber management 311 background bitmap 169, 170
administration user class 5 assigning a background bitmap 169
administrative state 38, 148, 158, 226, 238, changing the background bitmap 170
258, 267, 280, 288, 289, 290 background block error 155
paths & services 226, 238, 288, 289, 290 backup 79, 165
performance logs 148, 158 bandwidth 214, 255, 258, 286
port connections 258, 267 bidirectional 214, 235
protection 38, 280 BSHR 279, 280, 283
adopt 209, 210 C
actual route 209 cause 122, 128
actual topology 210 channels 143
Adopting the endpoints of a path bundle 252 DCN channels 141
alarm 5, 77, 79, 86, 116, 118, 122, 124, 126, general channel properties 143
127, 128, 131, 132, 134, 136, 137, Choose link connection 213
138, 139, 140, 142, 173, 192, 193,
207, 258, 290 Client AddIn 19
acknowledge 116, 128, 173, 258, 290 Clone Edges 249
audible signal 134 columns 29, 77, 78, 79, 81
cause 122, 128, 258, 290 concatenation 224, 290
class 122, 128, 258, 290 Concatenation 94
cleared 122, 124 configuration 2, 5, 24, 81, 82, 85, 161, 165,
313, 315, 316, 321
correlation 118, 290
performance log 161
location 136, 258, 290
UNO 314, 315, 316, 318, 321
mask 127, 133, 290
user class 5
primary 127, 290
confirm alarms 116
print list 137
connect4, 5, 49, 81, 167, 178, 214, 231, 255,
process 173, 193 257, 258, 267
refresh 173 port connection 255, 257, 258, 267
293
connection assistant 214 DWDM 203

contact person 310, 311 E
cost factor 244, 245, 255, 258, 267, 297 edit port connections 258
create219, 224, 247, 286, 314, 315, 316, 318 electrical ports 203
DCN status list 182 element manager 206, 319
path 214, 219 for universal objects 319
path container 218 starting 206
performance log 148 ELI-SXEM 141
port connection 255 email 310, 311
remote inventory list 182 EMOS-SLI 141
RIL 182 end port 267
service 286 errored second 155
synchronization data list 182 ethernet 307
UNO 314, 315, 316, 318 LCAS 307
Create 275, 279, 307 ports 203
BSHR or line protection 279 service 307
Ethernet Service with LCAS 307 event 74, 77, 81, 122, 133, 162, 165, 207
VLAN assignment 275 mask 207
creation states for paths 49 type 162
critical (alarm severity) 124 exclude 195, 199, 288
custom log 74 locking/unlocking a NE 199
D locking/unlocking a path or a service 288
Data Communications Network 141 NE from routing 195
date 77, 313 export 85, 86
DCN channel 2, 5, 25, 81, 141, 142, 143, F
147, 194 faults 81
DCN management 194 fax 310, 311
DCN objects 25 file transfer 196
DCN status list 182 filter 29, 77, 79, 81, 131, 165
delete 154, 172, 191, 258, 287 find NE 197
a service 287 Floating TPs 98, 99, 101
NE container 172 fonts 10
network elements 191 changing the fonts of a help topic 10
performance logs 154 G
port connections 258 generic physical interface 203
destination NE 214, 219, 235, 258, 286 Greenwich Mean Time 81
direction 167, 258 H
Disabled Paths 222 head end 214, 235
disconnect a NE from TNMS Core 178 header error check 155
display22, 131, 132, 142, 155, 173, 192, 193, hybrid routing 214, 219, 225, 235, 286
194, 257
I
alarms 131, 132, 142, 173, 192, 193
icons 22, 25, 29, 30, 34, 38, 42, 49, 59, 61,
logs 155 75, 76, 79, 81
properties 194, 257 ID 143, 144, 198
distribute TNMS Server time 313 identity 283
294
Index
Ientity 279 log full warning 148

indeterminate (alarm severity) 124 modifying configuration settings for
IP 4 performance logs 161
ISDN 203 network event log 162
L performance logs 148, 154, 155, 158, 161,

166
layer 258, 267, 270, 283, 290
permanent logs 165
Layer Restrictions at Optical Protection 100
print preview for lists and logs 75
LCAS 307
printing logs 76
LCT application 206
setting filters and sorting lists 79
line protection 280
setting log columns 78
Line protection 279
setting time filters for lists and logs 77
Link detection view 262
starting performance logs 166
list 74, 78, 86, 182
stopping performance logs 166
client paths 230
system message log 81
current alarm list 128
viewing logs 82
DCN objects 145
logon 4
DCN status list 182
loopback 49, 104, 214, 235
filter and sort icons in lists 29
M
paths 226
maintenance user class 5
port connections 267
major (alarm severity) 124
ports 264
manual routing 219, 225
print alarm list 137
measurement interval 148
protection groups 283
menu bar 19
remote inventory list 182
minor (alarm severity) 124
setting filters for lists and logs 77
mode switching 17
subscribers 310
modify 161, 200, 231, 289, 321
synchronization data list 182
configuration settings for performance
technologies 106 logs 161
termination points 270 path 231
transport layers 106 properties of a service 289
localize reporting NE 128, 136, 290 properties of MSP 280
location 122, 128, 148, 280 subnetwork connection 231
lock 199, 288 universal object 321
a network element 199 Modify a path bundle 253
a path or a service 288 module 162, 315, 316, 319
log 122 monitoring of tandem connection 167
alarm log 122 MSN 25, 141
configuring PLET 85 MSP 279, 280
creating performance log 148 N
deleting performance log 154 NE container168, 171, 172, 173, 174, 175, 177
displaying a performance log 155 NE distinctons 201
exporting logs using PLET 86 NetServer 2, 25, 144
general log management information 74 network editor 17
handling performance log 158 network element2, 25, 34, 42, 81, 138, 142, 143, 147, 168, 177
icons 29 abbreviations 4
295
add 168 label 290

address 4 manual path protection 278
alarms 138, 192, 193, 207 properties 290
connect to TNMS 178 protection 277, 278, 284, 285
delete 191 remove path protection automatically 284
disconnect from TNMS 178 remove path protection manually 285
exclude 286 rerouting 244
gateway software 4 routing 297
glossary 4 topology 302
LCT application 206 under test 234
NE initializing 143 path bundles 248, 249, 250, 252, 253, 254
NE location 198 path creation states 49
NE name 198 Path_Overhead Monitoring 233
NE type 198 PDH 2
path overhead monitoring 233 PDH ports 203
resynchronize 147, 177 performance log 91, 148, 154, 155, 158, 161,
network event log 162 166
exporting logs using PLET 86 performance management 5, 74, 82, 85, 86,
165
general log management information 74
path overhead monitoring 233
network event log 162
performance measurement point 148
permanent logs 165
permanent logs 74, 79, 87, 165
viewing logs 82
phone 310, 311
network management view 15
PLET 85, 86
not acknowledged 124
PMP 148
notification log 74
PMP Configuration 91
O
pointer justification 155
object 192
port 79, 203, 270, 286, 316
type 122, 128, 162
port connection 255, 257, 258, 267
operational state 258, 286, 290
port label 264
operator input log 74, 79, 82
port types 203
optical ports 203
primary alarm 127
Optical Transmission Section port 203
print 11, 75, 76, 137
organization 310, 311
alarm list 137
P
help topic 11
password 3, 4
logs 76
path 219, 296
preview 75
alarm 294
probable cause 192
automatic path protection 277
programs 2
create 219
TNMS Core application 2
delete 221
properties 25, 143, 144, 174, 194, 198, 257,
disabled 222 280, 289
handling server paths and client paths 224 channel properties 143
history 295 MSP properties 280
icons 61 NE containers properties 174, 280
Info 296 NE properties 194, 198
296
Index
NetServer properties 144 retry interval 144

port connection properties 257 routing195, 209, 212, 225, 239, 244, 245, 297
Properties of a NE container 176 RPR Manager AddIn 19
protection 277, 278, 280, 285 S
administrative state 226 Scalable Ethernet Paths & Generic
cross connection 226 Framing Procedure 101
layer 226 schedule 85, 86
list 226 Schedulling 305
operational state 226 scope 5, 79, 267, 270, 283, 310
protecting port 214 SDF-file type 79
protection state 226 SDH 2
provisioning state 226 secondary alarm 127
scope 226 security 3, 74, 82
service 226 server 4, 313
subscriber 226 service 61, 214, 247, 258, 286, 287, 288,
289, 296
Protection 279
create 214, 224, 286
provisioning state 258, 290
icons 61
Q
Info 296
QB3 141
information 290
QD2-SISA 141
label 290
R
list 290
raised alarm 122
lock 288
RCS 49, 61, 226, 267, 270, 290
modify 289
reboot 4
properties 289, 290, 294, 295, 297, 302
redirect alarms 138, 192
remove 287
refresh alarm information 140
scheduling 305
reinitialize 204
unlock 288
Release Required Resources 243
Service / Path properties info 296
Remote Inventory List 182
Services and subscribers tree view 61
remove 154, 221, 284, 285, 287
severity 25, 81, 122, 128
a path 221
show 15, 22, 131, 132, 142, 155, 173, 175,
a service 287 192, 193, 257
path protection automatically 284 alarms 131, 132, 173, 193
path protection manually 285 log 155
performance logs 154 NE container 173, 175
Remove VLAN Assignment 276 port connection 257
required creation state 49, 61, 226, 267, 270, SNMP 141
290
sort 29, 79, 81, 131, 165
rerouting a path 244
source 258, 286
reset all filters 79
source NE 258, 286
restore riginal filter sequence 79, 165
source type 81
resynchronize 147, 177, 204
SQL 85
data 204
standard logs 165
data of a DCN channel 147
start 166, 206
data of an NE container 177
network element manager 206
297
performance logs 166 Transport Layers 106

port 267 U
state 25, 81, 82, 124, 128, 198 unavailable second 155
stop performance logs 166 unconnected endpoint 214
subnetwork 168, 200 unconnected startpoint 214
subscriber 258, 290, 310, 311 unidirectional 214
supervision user class 5 universal object 25, 141, 314, 315, 316, 318,
Support of Loopbacks 104 319, 321
surveillance mode 17 universal subnetwork object25, 141, 319, 321
symbols 25, 29, 34, 38, 42, 49, 61 unlock 199, 288
Synchronization data list 182 a network element 199
synchronous 203 a path or a service 288
system message log 74, 79, 81, 82, 86, 165 unmanaged path 15, 49, 211, 221, 224
T UNO 25, 141, 314, 315, 316, 318, 319, 321
tables 74, 81, 82, 165 update alarm information 140
tail end 214 user 2, 3, 4, 5, 198
tandem connection monitoring 167 change password 3
Technologies 106 class 5
termination point 270 name 4
creating a TP of a universal object 318 property page general NE 198
group termination points 94 USO 25, 141, 319, 321
listing 270 V
modifying a TP of a universal object 318 view 15, 22, 131, 132, 142, 155, 173, 192,
193, 257
port an TP filter settings 273
alarms 131, 132, 142, 173, 192, 193
time 4, 77, 79, 81, 82, 85, 86, 143, 313
disabled path 222
TNMS CDM 5, 25, 141
logs 155
user class 5
options 22
TNMS Client 2, 3, 5, 18, 19, 24, 25, 74, 81,
82, 165, 194, 313 properties 143, 144, 174, 194, 257, 290
TNMS Core 2, 5 virtual path identifier 214
TNMS Server 2, 4, 5, 25, 74, 81, 141, 313 VPI 214
TNMS SysAdmin2, 3, 5, 74, 81, 82, 194, 313 W
ToolTips for path creation 247 warning (alarm severity) 124
TOPAT 87, 88, 91 WDM 2
TOPAT - General Information 87 Windows XP 4
TOPAT Main Window 87, 88 working port 214
topology 210, 214, 235, 302 wrap around 148
TP 49, 235 write access to a NE 180
transfer data 196
298

vdocuments.mx_client-tnms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

vdocuments.mx_client-tnms

Uploaded by

Copyright:

Available Formats

NOKIA SIEMENS NETWORKS

TNMS Core/CDM V11.1

Configuring the Performance Log Export Tool (PLET) ..........................................................56

Handling performance logs ..................................................................................................123

Adopting the actual route .....................................................................................................173

Adding protection to a path automatically ............................................................................239

Appl ic ation - TNMS Core/CDM

- TNMS CDM class

- Maint enance class

- Admini st ration c lass

Changing t he font of a help top ic

Printing a help topic

Network Management View

Switching between dif ferent mo des

You can change from one mode to another as follows:

TNMS Client main wi ndow

TNMS Client m enu bar

Menu item Function

View -> Find... Finds network element using a unique identifier

View -> Toolbar Shows/hides the toolbar.

Configuration -> Opens subscriber management.

are set to this time.

Security -> Login... Login to a TNMS Core/CDM Server.

Help -> Help Topic s Opens the online help.

General operating inform ation

Examples in TNMS Client:

Example of a network element.

Example of an UNO network element.

Example of a TNMS Core/CDM subnetwork.

The DCN object in question is being activated.

Icons: Filter and sort icons i n lists

If information in a column of a list or log is filtered, a gray funnel

Icons: Link connection

Link connection not yet existing, direction left

Link connection not yet existing, bi-directional

Link connection not yet existing, direction right

Link connection existing, direction left

Link connection existing, bi-directional

Link connection existing, direction right

Li nk connect i on t hr ough f l oat i ng TPs and SNCs i n

Fragment path, bi-directional

Fragment path, direction left

Fragment path not yet existing, bi-directional

Fragment path not yet existing, direction left

Fragment path not yet existing, direction right

Half open server path

Half open fragment path

Icons: Network elements

Example of a network element.

Example of a subnetwork element.

Network element with a transition state. This state may apply

user class or on the restrictions applied to the user group.

Icons: Network infrastructur e and protection

Protection in the MSP Properties wind ow

BSHR-2/4 East ring

BSHR-2/4 West ring

BSHR-4 Both rings (temporarily)

BSHR-4 West span

BSHR-4 East span

BSHR-4 Both spans

BSHR-4 West span east ring

BSHR-4 East ring west span

Icons: Network Plan

Universal network element (example).