TNMS-V15 Troubleshooting Manual

TNMS NCT
15.11
Coriant TNMS NCT

Troubleshooting Manual (TSMN)
Issue: 1 Issue date: November 2015
A50023-K4045-X060-01-7673
Coriant is continually striving to reduce the adverse environmental

effects of its products and services. We would like to encourage you as
our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recom-
mendations for power use and proper disposal of our products and their
components.
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Coriant customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be used, reproduced, modified or transmitted in any form or
means without the prior written permission of Coriant. The documentation has been prepared to
be used by professional and properly trained personnel, and the customer assumes full respon-
sibility when using it. Coriant welcomes customer comments as part of the process of contin-
uous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Coriant and the customer. However, Coriant has made
all reasonable efforts to ensure that the instructions contained in the document are adequate
and free of material errors and omissions. Coriant will, if deemed necessary by Coriant, explain
issues which may not be covered by the document. Coriant will correct errors in this documen-
tation as soon as possible.
IN NO EVENT WILL CORIANT BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR
FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO
LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR
DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN
IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Coriant 2015. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the "Legal, Safety
and Environmental Information" part of this document or documentation set.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheit-
sanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentation-
ssatzes.
2 A50023-K4045-X060-01-7673
Table of Contents
Table of Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 TNMS NCT documentation set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Fault analysis overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1 System event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1.1 EM/NE management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.1.2 Topology management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.1.3 User and security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.1.4 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.1.5 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.1.6 GUI Cut-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.1.7 SCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.2.2 Alarm logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2.3 Backup logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4 GUI messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4 Operator hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1 EMS functionalities based on the NE cost are not working well in mixed net-
works (HINT-230). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2 In an auto discover scenario the DCN routes are not automatically updated.
(HINT-286) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3 Error when stopping EmlMediator service (HINT-11) . . . . . . . . . . . . . . 44
4.4 Error when starting EmlMediator service (HINT-12) . . . . . . . . . . . . . . . 44
4.5 Special mapping of static CCs on hiT7065 5.1 and 5.2 126xE1 card in HO
trail mode enabled (HINT-14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.6 TNMS NCT allows changing a user's password that does not differ in 4
chars from last one (HINT-311) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.7 DCN Import from Core (HINT-303) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.8 Not possible to activate an NE in TNMS NCT if an user uses the Configure
exclusive command (HINT-317) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.9 7100 RNEs are not correctly auto discovered if their user/passwords are
different than of the PGNE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
A50023-K4045-X060-01-7673 3
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 A50023-K4045-X060-01-7673
List of Tables
Table 1 Structure of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 2 List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 4 System event log (SEL) entries generated by EM/NE management . . 14
Table 5 SEL entries generated by Topo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 6 SEL entries generated by USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 7 SEL entries generated by Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 8 SEL entries generated by Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 9 SEL entries generated by GCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 10 SEL entries generated by SCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 11 Most frequent alarms generated by TNMS NCT . . . . . . . . . . . . . . . . . . 35
Table 12 Backup entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 13 Errors displayed in the TNMS NCT interface. . . . . . . . . . . . . . . . . . . . . 40
Table 14 Operator Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 15 Static cross-connections on 126xE1 card . . . . . . . . . . . . . . . . . . . . . . . 45
A50023-K4045-X060-01-7673 5
6 A50023-K4045-X060-01-7673
Troubleshooting Manual (TSMN) Preface
1 Preface
This chapter describes the audience, structure, conventions and history of changes of
the Coriant TNMS NCT Troubleshooting Manual (TSMN).
1.1 Intended audience

This document is intended for anyone tasked with clearing fault conditions to restore
normal system operation that may occur in the Coriant TNMS NCT system.
Personnel performing these procedures must have general experience with network
management systems as well as specific experience with network hardware compo-
nents.
1.2 Structure of this document

This document is structured as follows:
Chapter Title Subject

1 Preface Provides an introduction to this document.
2 Troubleshooting Provides procedures and actions to perform when
warning or error messages appear in system logs.
3 Oracle Provides a description on how to clear the trace files.
Abbreviations Contains a list of acronyms used in TNMS NCT.
Glossary Contains a definition of the most important technologies
referred in the TNMS NCT documentation.
Index Contains the index entries for this document.
Table 1 Structure of the manual
A50023-K4045-X060-01-7673 7
Preface Troubleshooting Manual (TSMN)
1.3 Symbols and conventions

The following symbols and mark-up conventions are used in this document:
Representation Meaning
f DANGER! A safety message indicates a dangerous situation where

personal injury is possible.
f WARNING! The keywords denote hazard levels with the following meaning:
f CAUTION! DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.
w NOTICE: A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.
g A note provides important information related to the topic, for

example, not obvious exceptions to a rule or side effects.
t A tip provides additional information related to the topic which is

not essential in the context, but given for convenience.
Bold ವ All names of graphical user interface (GUI) objects, such as
windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
ವ Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively.
ವ Important key words.
Italic ವ Files, folders, and file system paths.
Example: /usr/etc/sbin/ftpd.exe
ವ Emphasized words.
typewriter ವ Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
ವ Output from a command, error messages, content of a status
line, and so on.
ವ File content, such as program sources, scripts, logs, and set-
tings.
<angle brackets> Placeholders, for example as part of a file name or field value.
Examples:
<picture name>.png or <ip address>:<port number>
Table 2 List of symbols and conventions
8 A50023-K4045-X060-01-7673
Representation Meaning
[square brackets] A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a “+”
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].
> The greater than symbol “>” is used to concatenate a series of
GUI items in order to depict a GUI path. This is an abridged pre-
sentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as
A more complex GUI path:
> Main window > File menu > Change Password command >
Change Password dialog box
x For convenience, card names are sometimes listed with a lower
(in card names) case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)
(parentheses) For convenience, card variants are sometimes listed with a
section of their name between parentheses, in order to concisely
represent both card variants.
Example:
CCEP-3(/S) (is to be interpreted as CCEP-3 and CCEP-3/S)
Table 2 List of symbols and conventions (Cont.)
Screenshots of the graphical user interface are examples only to illustrate principles.
This especially applies to a software version number visible in a screenshot.
A50023-K4045-X060-01-7673 9
1.4 TNMS NCT documentation set

See the Documentation Guide for a complete and updated list of all TNMS NCT related
documents and their descriptions.
For your convenience, the operational documents are available via the TNMS NCT help
menu, while all others are stored in the help folder of your TNMS NCT Client installation.
1.5 Other documents

Legacy products and Network Elements
This manual concerns TNMS NCT only. For more detailed information on other legacy
products or the managed network elements (NEs), see the corresponding documenta-
tion.
Release notes
Where applicable, contains installation hints, patch descriptions, list of supported NEs,
list of supported cards and any relevant last-minute information.
10 A50023-K4045-X060-01-7673
1.6 History of changes

This chapter describes the main changes for the current document and since the last
version.
Issue Issue date Remarks

A50023-K4045-X060-01-7673 November 2015
Initial version.
Table 3 History of changes
A50023-K4045-X060-01-7673 11
12 A50023-K4045-X060-01-7673
Troubleshooting Manual (TSMN) Troubleshooting
2 Troubleshooting
This chapter describes procedures and actions to troubleshoot TNMS NCT errors.
2.1 Fault analysis overview

When an error occurs you must perform fault analysis (FA) to detect data inconsistency
or crashed/blocking components. For some scenarios system messages are generated,
which is the entry point to the FA. The message log points you to the likely faulty/con-
cerned component which could be blocking or hanging the system. After one component
is clearly identified, internal component traces help you to analyze the error. To find and
understand the error it is important to understand the scenario in which it occurs. In most
cases the scenario description is part of the error description. However, an overview of
a scenario should be also visible within the traces. To keep persistent FA data, TNMS
NCT provides uniform logging and tracing functions for errors:
ವ Logging, based on information from the application logs.
ವ Tracing, based on diagnostic information like interface or system internal traces.
All information related to the cause of the fault is stored in logs that are available even
if the fault results in a successful recovery action. Furthermore, this information permits
the analysis of the fault after the reset and/or recovery process.
2.2 Logging
TNMS NCT provides the following GUI-viewable application logs for FA:
ವ System event log - used for logging warnings, errors as well as general system infor-
mation, for example startup and shutdown of components.
ವ Alarm log - used to store all alarm data.
The following sections contain logging troubleshooting procedures.
2.2.1 System event logs

The following sections display the log entries in a table format generated by the corre-
sponding TNMS NCT components.
Table structure for SEL entries
ವ Severity - indicates the severity of the event, that is message, warning or error.
ವ Affected object - displays the name of the object in the context where the message
was raised. This can be the "NE Name" in many cases, the name of a PC, the name
of a port, a common function name, connector or server.
ವ Description - displays information on the event.
ವ General information - generic information about the problem.
ವ Troubleshooting information: probable cause (solution) - provides a possible reason
(solution) for the problem.
A50023-K4045-X060-01-7673 13
Troubleshooting Troubleshooting Manual (TSMN)
2.2.1.1 EM/NE management

The table below has troubleshooting information for SEL entries generated by EM/NE
management.
Severity Affected Description General Troubleshooting information

object info Probable cause Solution
Warning EM/NE New NE was found but Internal An alien EM has Trouble with DB or EM was
Manager parent EM is unknown error reported a new deleted, reinstall the EM
EmId=<id> NE types into DB
Warning EM/NE NE initialized, but was Internal NE was reported Check timeout setting for
Manager already initialized. error. as initialized but NE initialization.
was already ini-
tialized.
Warning EM/NE NE initialized unexpect- Internal NE was reported Check timeout setting for
Manager edly. error. as initialized but NE initialization.
no initialization
was running.
Warning EM/NE Could not perform syn- Internal Incorrect installa- If this happens, please
Manager chronization since SCS is error. tion. contact technical support.
not available.
Warning EM/NE New NE was found but Internal An EM was Update EM/NE .xml files or
Manager netype <"NeProxyType> error. reported but this use a proper version of EM.
is unknown under Em type is unknown
<IdName>. by EM/NE.
Error EM/NE Copy NE name to idName Internal Oracle DB is 1. Shutdown application
Manager failed because of trouble error. down. server.
with DB. 2. Restart Oracle DB.
3. Start the application
server.
Error EM/NE Element manager cur- Internal EM is not avail- No connection, EM not
Manager rently not available. error. able. started, verify EM proper-
ties.
Error EM/NE Copy NE name to idName User NE Name must Verify that the local NE
Manager failed because error. be unique but it is name is unique for all
<neName> is already in already in use. managed NEs. Use the EM
use. application to change the
local NE name.
Error EM/NE NE connection failed: Generic Connection to NE Check availability of NE
Manager <Detailed Error Mes- error. could not be and NE properties for
sage>. established or correct address (the
lost. system performs regularly
reconnect tries).
Table 4 System event log (SEL) entries generated by EM/NE management
14 A50023-K4045-X060-01-7673

Error EM/NE NE initialize failed - retry Generic Data upload from See detailed message and
Manager count exceeded: error. NE failed and browse the troubleshooting
<Detailed Error Mes- number of retries guide for this problem.
sage>. exceeded. Deactivate/activate the NE.
Error EM/NE NE initialize failed: Generic Another compo- See detailed message and
Manager <Detailed Error Mes- error. nent reported an browse the troubleshooting
sage>. error to EM/NE. guide for this problem.
Deactivate/activate the NE.
Error EM/NE Error message "Address Generic NSAP/IP address In the NSAP/IP table place
Manager cannot be empty" appears error. cannot be empty the mouse on the second
during NE creation line or press Enter.
Table 4 System event log (SEL) entries generated by EM/NE management (Cont.)
A50023-K4045-X060-01-7673 15
2.2.1.2 Topology management

The table below has troubleshooting information for SEL entries generated by Topo.

object information Probable cause Solution
Warning Topology Failed to syn- Problem in the Failed to acquire Check state of suppliers
Management chronize data for synchronization. data from other (Fault Management, NE
a Topological common func- Object Management,
Symbol tions. Element Management).
Warning Topology Failed to syn- Problem in the Failed to acquire Check state of suppliers
Management chronize data for synchronization. data from other (Fault Management, NE
a Topological common func- Object Management,
Symbol tions. Element Management).
Error Topology Retrieval of Con- Retrieval of the Wrong IDs or Check installed compo-
Management nection IDs failed list of IDs of the database incon- nents (for example
links represented sistency. version numbers, instal-
by the given lation log). Restore
graphical link backup set.
failed.
Error Topology Retrieval of a Retrieval of a Wrong IDs or Check installed compo-
Management Graphical Link Graphical Link database incon- nents (for example
failed failed. sistency. version numbers, instal-
lation log). Restore
backup set.
Error Topology Retrieval of a list Retrieval of Wrong IDs or Check installed compo-
Management of Graphical Graphical Links database incon- nents (for example
Links failed failed. sistency. version numbers, instal-
backup set.
Error Topology Retrieval of a list Retrieval of Wrong IDs or Check installed compo-
Management of Graphical Link Graphical Links database incon- nents (for example
IDs failed failed. sistency. version numbers, instal-
backup set.
Error Topology Modification of a Graphical Link Inconsistent Check the database
Management Graphical Link attributes could parameters, installation.
failed not be written. database mal-
function.
Error Topology Retrieval of an Retrieval of an Wrong IDs or Check installed compo-
Management icon failed icon for second database incon- nents (for example
level Topological sistency. version numbers, instal-
Container failed. lation log). Restore
backup set.
Table 5 SEL entries generated by Topo
16 A50023-K4045-X060-01-7673

Error Topology Retrieval of a list Retrieval of icons Wrong IDs or Check installed compo-
Management of icons failed for second level database incon- nents (for example
Topological Con- sistency. version numbers, instal-
tainer failed. lation log). Restore
backup set.
Error Topology Retrieval of a list Retrieval of icons Wrong IDs or Check installed compo-
Management of icon IDs failed for second level database incon- nents (for example
Topological Con- sistency. version numbers, instal-
tainer failed. lation log). Restore
backup set.
Management background background database incon- nents (for example
image failed image for a sistency. version numbers, instal-
Topological Con- lation log). Restore
tainer failed. backup set.
Possible reason:
The given id is
wrong.
Error Topology Retrieval of a list Retrieval of a Wrong IDs or Check installed compo-
Management of background background database incon- nents (for example
images failed images for a sistency. version numbers, instal-
Error Topology Retrieval of a list Retrieval of a Wrong IDs or Check installed compo-
Management of background background database incon- nents (for example
image IDs failed images for a sistency. version numbers, instal-
Error Topology Retrieval of the Retrieval of the Database incon- Check your installation.
Management root container root container sis- Restore backup set.
failed (top level Topo- tency.Required
logical Con- database entry is
tainer) failed. missing.
Management Physical Trail Physical Trail database incon- nents (for example
failed failed. sistency. version numbers, instal-
backup set.
Error Topology Retrieval of a list Wrong IDs or Check installed compo-
Management of Physical Trails database incon- nents (for example
failed sistency. version numbers, instal-
backup set.
Table 5 SEL entries generated by Topo (Cont.)
A50023-K4045-X060-01-7673 17

Error Topology Retrieval of a list Wrong IDs or Check installed compo-
Management of Physical Trail database incon- nents (for example
IDs failed sistency. version numbers, instal-
backup set.
Error Topology Creation of a Creation of a PTPs could not Check installed compo-
Management Physical Trail Physical Trail be retrieved from nents (for example
failed failed. the element man- version numbers, instal-
agement. PT lation log). Check NE
already exists. resources.
PTP already in
use. Incompati-
ble layers,...
Error Topology Deletion of a Deletion of a TP Insufficient user Check security settings.
Management Physical Trail failed. rights.
failed
Error Topology Modification of a - Insufficient user Check security settings.
Management Physical Trail rights.
failed
Management Topological Con- Topological Con- database incon- nents (for example
tainer failed tainer failed. sistency. version numbers, instal-
backup set.
Error Topology Retrieval of a list - Wrong IDs or Check installed compo-
Management of Topological database incon- nents (for example
Containers failed sistency. version numbers, instal-
backup set.
Container IDs sistency. version numbers, instal-
failed lation log). Restore
backup set.
Error Topology Creation of a Creation of a A container with Create container with
Management Topological Con- Topological Con- the given name different name.
tainer failed tainer failed. already exists
Error Topology Deletion of a The container Check container. Check
Management Topological Con- does not exist or security settings.
tainer failed insufficient user
rights.
18 A50023-K4045-X060-01-7673

Error Topology Modification of a - The container Check container. Check
Management Topological Con- does not exist or security settings.
tainer failed insufficient user
rights.
Management Topological Topological database incon- nents (for example
Symbol failed Symbol failed. sistency. version numbers, instal-
Possible reason: lation log). Restore
The given id is backup set.
wrong.
Symbols failed sistency. version numbers, instal-
backup set.
Symbol IDs failed sistency. version numbers, instal-
backup set.
Error Topology Creation of a Creation of a A symbol for the -
Management Topological Topological given NE already
Symbol failed Symbol failed. exists.
Error Topology Deletion of a - The symbol does Check symbol. Check
Management Topological not exist or insuffi- security settings.
Symbol failed cient user rights.
Error Topology Modification of a - The symbol does Check symbol. Check
Management Topological not exist or insuffi- security settings.
Symbol failed cient user rights.
Error Topology Retrieval of the - - Check element manage-
Management Potential ment.
Physical Trails
failed
Error Topology Retrieval of the - Database Check your database
Management Topology problem installation.
Manager failed
Error Topology Modification of - Database Check your database
Management the Topology problem installation.
Manager failed
Error Topology Registration of a - Database Check your database
Management Network problem installation.
Manager failed
A50023-K4045-X060-01-7673 19

Error Topology De-registration of - Database Check your database
Management a Network problem installation.
Manager failed
Error Topology Deletion of a icon The container The icon does not Check database
Management failed icon could not be exist or database
deleted. problem
Error Topology Deletion of a The background The image does Check database
Management background image could not not exist or
image failed be deleted. database
problem
Error Topology Retrieval of the The element - Check element manage-
Management ports of an NE management ment.
failed reported an error,
when the PTPs
were requested.
Error Topology Retrieval of a list The list of poten- Internal error. Contact Coriant support.
Management of potential tial parents of a
parents failed TS could not be
retrieved.
Error Topology Addition of a icon A new container Database Check your database
Management failed icon could not be problem installation.
created.
Error Topology Addition of a A new container Database Check your database
Management background background problem installation.
image failed image could not
be created.
Error Topology Retrieval of a list - Database Check your database
Management of background problem installation.
image names
failed
Error Topology Storage of a Topology man- - Check the element man-
Management Physical Trail to agement tried to agement by looking for
the element layer store the PT info "down" alarms of failed
failed in the element system components and
layer. The try again once they are
element man- back. Check also the
agement LAN connection to the
reported an error. NEs.
20 A50023-K4045-X060-01-7673

Error Topology Adoption of a Topology man- Check the element man-
Management Physical Trail agement tried to agement by looking for
from the element adopt the PT info "down" alarms of failed
layer failed from the element system components and
layer. The try again once they are
element man- back. Check also the
agement LAN connection to the
reported an error. NEs.
Error Topology Retrieval of The list of PTs Database Check your database
Management Physical Trail list could not be problem. installation.
failed retrieved from
the database.
Error Topology Retrieval of The layout data Installation Check your installation.
Management Physical Trail of the PT list problem.
filter data failed could not be
retrieved.
Error Topology Retrieval of the The number of Database Check your database
Management row count failed rows in the PT list problem. installation.
could not be
retrieved.
Error Topology Retrieval of The layout data Installation Check your installation.
Management Physical Trail list of the PT list problem.
schema info could not be
failed retrieved.
Error Topology Retrieval of the The SCS compo- Installation Check your installation.
Management component state nent reported an problem.
failed error.
Error Topology Synchronization The SCS compo- Installation Check your installation.
Management failed nent reported an problem.
error.
Error Topology Forced synchro- The SCS compo- Installation Check your installation.
Management nization failed nent reported an problem.
error.
Error Topology Data access General Database Check your database
Management error. database error. problem. installation.
A50023-K4045-X060-01-7673 21

Error Topology Specified owner An attempt was Internal error Contact Coriant support.
Management not found in list of made to create a
potential owners. Topological Con-
tainer, which
bounces are not
inside the
bounces of the
specified parent
container.
Error Topology Missing specified Retrieval of a Wrong IDs or Check installed compo-
Management topological con- Topological Con- database incon- nents (for example
tainer in data- tainer failed. sistency. version numbers, instal-
base. Possible reason: lation log). Restore
wrong.
Error Topology Topological con- An attempt was Create container with a
Management tainer with speci- made to create a different name.
fied name TC with a TC
already exists. name, that
already exists.
Error Topology Topological root An attempt was Wrong IDs or Check installed compo-
Management container is man- made to delete database incon- nents (for example
datory. the root con- sistency. version numbers, instal-
tainer. lation log). Restore
backup set.
Error Topology Topological root An attempt was Internal error Contact support.
Management container must made to change
comprise all the container
other container size bound the
and symbols. root container
size, which is not
valid.
Management topological Topological database incon- nents (for example
symbol in data- Symbol failed. sistency. version numbers, instal-
base. Possible reason: lation log). Restore
wrong.
Error Topology Topological An attempt was User error.
Management symbol (TS) for made to create a
specified NE TS for an NE, for
already exists. which a TS
already exists.
22 A50023-K4045-X060-01-7673

Error Topology Topological An attempt was User error. -
Management symbol for speci- made to create a
fied NE {0} TS for an NE, for
already exists. which a TS
already exists.
Error Topology Topological An attempt was - Check installed compo-
Management Symbol not made to create a nents (for example
found. Graphical Link version numbers, instal-
for not existing lation log)
TS.
Error Topology Missing specified The specified PT Wrong IDs or Check installed compo-
Management physical trail in is not available database incon- nents (for example
database. on the database. sistency. version numbers, instal-
backup set.
Error Topology Incompatible An attempt was - Check installed compo-
Management layers for made to create a nents (for example
physical trail end- PT with incom- version numbers, instal-
points. patible layers. lation log).
Error Topology Specified An attempt was - Check NE resources in
Management physical termina- made to create a the element manage-
tion point already PT with PTPs, ment.
used in a which are not
physical trail. available.
Error Topology Specified An attempt was - Check NE resources in
Management physical termina- made to create a the element manage-
tion point not PT with PTPs, ment.
available. which are not
available.
Management graphical link in Graphical Link database incon- nents (for example
database. failed. sistency. version numbers, instal-
backup set.
Error Topology Permission on The security - Check your security set-
Management NE is denied configuration tings.
does not allows
access to this NE
Error Topology Permission for The security con- - Check your security set-
Management operation is figuration allows tings.
denied not access for
this operation
A50023-K4045-X060-01-7673 23

Management image in data- container back- database incon- nents (for example
base. ground image sistency. version numbers, instal-
failed. Possible lation log). Restore
reason: the given backup set.
id is wrong.
Management icon pair in data- second level con- database incon- nents (for example
base. tainer icon failed. sistency. version numbers, instal-
Possible reason: lation log). Restore
the given id is backup set.
wrong.
24 A50023-K4045-X060-01-7673
2.2.1.3 User and security management

The table below has troubleshooting information for SEL entries generated by user and
security management.

Warning User and Client not - 1. The Client associ- 1. Restart the Client
security man- responding. ated with the given 2. Check if the machine
agement System cleaned user name has on which the user has
up the Client's crashed. logged in is still reach-
session for <login 2. The machine on able.
name>. which the Client is
running is no longer
reachable.
Error User and Could not create a - - -
security man- security log
agement record.
Table 6 SEL entries generated by USM
A50023-K4045-X060-01-7673 25
2.2.1.4 Fault management

The table below has troubleshooting information for SEL entries generated by fault man-
agement.

Error Fault Problems occurred Internal 1. Database connection 1. Restart the applica-
Manager during Create alarm problem. problems or Application tion server.
counter for {counter server lacking resources. 2. Contact Coriant
name}. Create alarm 2. Application problem. support.
counter could not be
finished.
Manager during Delete alarm problem. problems or Application tion server.
id}. Delete alarm 2. Application problem. support.
finished.
Manager during Modify alarm problem. problems or Application tion server.
id}. Modify alarm 2. Application problem. support.
finished.
Error Fault Problems occurred Internal 1. Connection to NE 1. Confirm that the NE is
Manager during Synchroniza- problem. failed. connected and restart
tion for {component}. 2. Database connection synchronization.
Synchronization could problems or Application 2. Restart the applica-
not be finished. server lacking resources. tion server.
3. Application problem. 3. Contact Coriant
support.
Error Fault Problems occurred Fault 1. Connection to Sched- Restart the application
Manager during Initialization. Manager uler failed. server.
Initialization could not could not
be finished. be initial-
ized.
Error Fault Problems occurred Internal 1. Transient problem. 1. Wait 5 minutes
Manager during Process problem. 2. Database connection 2. Restart the applica-
counter timer. problems. tion server.
Process counter timer
could not be finished.
Table 7 SEL entries generated by Fault
26 A50023-K4045-X060-01-7673
2.2.1.5 Log management

The table below has troubleshooting information for SEL entries generated by log man-
agement.

Error Server <Log name> export Log Log export ended but Check the detailed error
completed but with Export. errors occurred. The message. Repeat the
errors. <Detailed export output files were not export operation. If the
Error Message>. created. problem persists, contact
Coriant support.
Table 8 SEL entries generated by Log
A50023-K4045-X060-01-7673 27
2.2.1.6 GUI Cut-Through

The table below has troubleshooting information for SEL entries generated by GCT.

Warning GUI Cut- The GCT needs The Registry is The Windows Restart the Windows
Through the Windows needed to find the Registry is not avail- Operating System.
Registry to find LCT location and able Contact your Windows
and launch any parameters neces- Operation System
LCT sary to it execution support team. If this
does not work Contact
Coriant support.
Warning GUI Cut- The GCT cannot The GCT tried to The LCT was closed 1. Ignore it
Through deliver the deliver a message to but is still receiving 2. Contact Coriant
Telegram the LCT but it wasn’t telegrams: support.
because the present to receive it. 1. Due to Topic over-
Session for the This is rare and could load, the delivery was
LCT is closed. happen when the delayed.
LCT is closed before
the Telegram Tunnel 2. The Mediator did
not close the Session.
due to a communica-
tion problem or over-
loaded Server.
Error GUI Cut- The GCT cannot The Windows Please install and run Try to run the Client on
Through open the LCT in Registry is needed to the Client on a a non-Windows oper-
a non-Windows find the LCT location Windows operating ating system.
Operating and parameters nec- system.
System. essary to it execu-
tion.
Error GUI Cut- The GCT cannot The Registry is 1. The Windows 1. Please see solution
Through read the needed to find the Registry is not avail- for problem: “The GCT
Windows Regis- LCT location and able. needs the Windows
try. parameters neces- 2. Tried to run the Registry to find and
sary to it execution. Client on a non- launch any LCT”.
Windows operating 2. Please install and
system. run the Client on a
3. The Registry is Windows operating
corrupt. system.
4. GCT Windows 3. and 4. Reinstall the

Dynamic Link Library Client.
(DLL) file is missing.
Table 9 SEL entries generated by GCT
28 A50023-K4045-X060-01-7673

Error GUI Cut- The GCT cannot The Registry is 1. The Windows 1. Please see solution
Through find the LCT needed to find the Registry is not avail- for problem: "The GCT
Software. LCT location and able. needs the Windows
parameters neces- 2. Tried to run the Registry to find and
sary to it execution. Client on a non launch any LCT".
Windows operating 2. Please install and
system. run the Client on a
3. The LCT Registry Windows operating
entries are corrupt. system.
3. Reinstall the LCT.
Error GUI Cut- Registry The Registry Keys The LCT Registry Reinstall the LCT.
Through problem. LCT are needed to find entries are corrupt.
Keys not found the LCT location and
in this machine. parameters neces-
sary to it execution.
Error GUI Cut- The GCT cannot The GCT uses a The Proxy Service Check if the Windows
Through start the Proxy proxy service to cannot open and user has permissions
Service. launch the Java close ports in this PC. to use ports in this PC.
Virtual Machine and Check the firewall set-
to communicate with tings. Check the anti-
the LCTs. virus settings.If this
does not work Contact
Coriant support.
Error GUI Cut- Cannot sub- The GCT uses the 1. Topic overloaded. 1. Wait and repeat the
Through scribe the GCT Topic to receive tele- 2. Topic is not avail- Command.
Topic. The GCT grams and notifica- able. 2. Restart the Client.
will not process tions from the NEs. If this does not work
incoming tele- Contact Coriant
grams or notifi- support.
cations.
Error GUI Cut- Invalid Session When the LCT is Problem with GM. Activate/deactivate
Through number. The opened a Telegram the NE (GM) in the
GCT cannot Tunnel between the DCN Management
create a Client and the window and issue the
Telegram Server/Mediator is command again.
Tunnel Session created. This tunnel If this does not work
with the Media- is identified with a Contact Coriant
tor. session ID number. support.
Table 9 SEL entries generated by GCT (Cont.)
A50023-K4045-X060-01-7673 29

Error GUI Cut- A GCT Job did The Client uses Jobs The Client cannot Wait and issue the
Through not finish cor- to make Asynchro- finish a Job correctly. command again.
rectly nous calls to the If this does not work
Server. restart the Client.
If nothing works
Contact Coriant
support.
Error GUI Cut- GCT received The GCT asked 1. EM does not exist 1. Ignore it
Through invalid data information about an anymore. 2. Restart the EM and
about the EM. EM, but the info 2. EM could be dis- issue the command
The GCT cannot didn’t arrive due to connected. again
launch the EMS. some delay, is cor-
3. Problem with the 3. Contact Coriant
rupted or is empty.
EM, GM. support.
Error GUI Cut- GCT received The GCT asked 1. NE does not exist 1. Ignore it
Through invalid data information about an anymore. 2. Restart the NE and
about the NE. NE, but the info didn’t 2. NE could be dis- issue the command
The GCT cannot arrive due to some connected. again
launch the LCT. delay, is corrupted or
3. Problem with the 3. Contact Coriant
is empty.
EM, GM. support.
Error GUI Cut- GCT Info invalid. The GCT asked Invalid data returned Activate/deactivate
Through Mediator information about an by server. the NE (GM) in the
returned wrong NE/EM Client, but DCN Management
data. The GCT the info didn’t arrive, window and issue the
cannot launch is corrupted or is command again.
the LCT. empty. If this does not work
Contact Coriant
support.
Error GUI Cut- Invalid GCT The GCT asked 1. Invalid data 1. Activate/deactivate
Through Capacity information about an returned by server the NE (GM) in the
detected. The NE/EM Client 2. The GCT does not DCN Management
GCT cannot Launch Capacity, but support the opening of window and issue the
launch the LCT. the info didn’t arrive, the Software this type command again
is corrupted or is of EM or NE requires. 2. Contact Coriant
empty. support.
Error GUI Cut- Failed to start The GCT needs the 1. Java is not 1. and 2. Check if the
Through the Java Shared Java Virtual Machine installed. Java Virtual Machine
Virtual Machine. to open the LCT. The 2. Java version is is installed and if it is
LCT is a Java based wrong. the version recom-
Software. mended by Coriant
3. Problem opening
ports. 3. Check the firewall
settings
30 A50023-K4045-X060-01-7673

Error GUI Cut- Failed to start The Registry is The Registry is cor- Reinstall the TNMS
Through the Java Shared needed to find the rupted. NCT Client
Virtual Machine Java Virtual Machine
(JVM) location of
TNMS NCT Client
Error GUI Cut- Failed to start or The GCT needs the 1. Java not installed. 1. and 2. Check if the
Through connect to the Java Virtual Machine 2. Java version is Java Virtual Machine
Java Shared to open the LCT. The wrong. is installed and if it is
Virtual Machine LCT is a Java based the version recom-
3. Problem opening
Software. mended by Coriant.
ports.
3. Check the firewall
settings
Error GUI Cut- Failed to send a The GCT needs the 1. Java Virtual 1. Kill the process of
Through command to the Java Virtual Machine Machine is dead. the Shared Java
Shared Java to open the LCT. The 2. Problem opening Virtual Machine
Virtual Machine. LCT is a Java based ports. affected and log-
Software. out/login the Client
again
2. Check the firewall
settings
Error GUI Cut- Could not The GCT asked 1. EM does not exist 1. Ignore it
Through perform the Get information about an anymore. 2. Activate/deactivate
Single Element EM, but the info 2. EM could be dis- the NE (GM) in the
Manager call. didn’t arrive due to connected. DCN Management
some delay, is cor- window and issue the
3. EM or the GM is
rupted or is empty. command again
unavailable.
3. Contact Coriant
support.
Error GUI Cut- Could not The GCT asked for 1. NE does not exist 1. ignore it
Through perform the Get information about an anymore 2. activate/deactivate
Single NE call. NE, but the info didn’t 2. NE could be dis- the NE (GM) in the
arrive due to some connected DCN Management
delay, is corrupted or window and issue the
3. Element Manager
is empty. command again
or the GM is unavail-
able 3. Contact Coriant
support.
A50023-K4045-X060-01-7673 31

Error GUI Cut- Could not The GCT asked for 1. NE does not exist 1. ignore it
Through perform the Get information about an anymore 2. activate/deactivate
NE Proxy call NE, but the info didn’t 2. NE could be dis- the NE (GM) in the
arrive due to some connected DCN Management
delay, is corrupted or window and issue the
3. EM or the GM is
is empty command again
unavailable
3. Contact Coriant
support.
Error GUI Cut- Could not GCT Manager. 1. NE does not exist 1. ignore it
Through perform the When the LCT is anymore 2. activate/deactivate
Advise Session opened a Telegram 2. NE could be dis- the NE (GM) in the
call Tunnel between the connected DCN Management
Client and the window and issue the
Server/Mediator is 3. EM or the GM is
unavailable command again
created. This tunnel
3. Contact Coriant
is identified with a
support.
session ID number
Error GUI Cut- Could not When the EMS is 1. EM or NE does not 1. ignore it
Through perform the opened a command exist anymore 2. activate/deactivate
Server Launch with the launch 2. EM or NE could be the NE (GM) in the
Session call instructions is sent to disconnected DCN Management
the Server/Mediator window and issue the
3. Data filled by user
is invalid command again
4. EM is unavailable 3. issue the command

again and correct the
data
4. log out from the
Client and back in.
If the error persists,
Contact Coriant
support.
Error GUI Cut- Get User Class The GCT Menus 1. Security Manager is 1. log out from the
Through Call Failed. availability is associ- unavailable Client and back in
The GCT menus ated to the security 2. The Server did not 2. wait for the Server
are not avail- permissions. finish the startup pro- to finish the Startup,
able. cedure yet then log out from the
Client and back in
32 A50023-K4045-X060-01-7673

Error GUI Cut- GCT call to the The GCT keeps a 1. the Server did not 1. wait for the Server
Through Database failed registry of open finish the startup pro- to finish the Startup,
LCTs on the cedure yet then log out from the
database 2. database is Client and back in
unavailable 2. check for database
3. database internal connectivity
error 3. Contact Coriant
support.
Error GUI Cut- Timeout After the LCT is 1. JVM is overloaded 1. Kill the affected
Through detected: the launched in the JVM, 2. The JVM or the Shared JVM, then log
LCT failed to the GCT waits 30 LCT cannot open out from the Client and
start. Open seconds for the con- ports in this PC back in
command was nection to be made 2. Check the firewall
aborted. 3. Client PC is too
and them gives a settings
slow
timeout.
3. Check if the PC
complies with the
minimum require-
ments.
If the error persists,
Contact Coriant
support.
Error GUI Cut- The Element All communication The Element Manager Restart the Server.
Through Manager is not with the Mediator is is not running. If the error persists,
available. No done through the Contact Coriant
GCT calls are Element Manager. support.
possible at this
time.
Error GUI Cut- The Security The GCT needs the The Security Manager Restart the Server.
Through Manager is not Security Manager to is not running. If the error persists,
available. No check the security Contact Coriant
GCT calls are permissions of the support.
possible at this user.
time.
Error GUI Cut- SFTP details are On opening LCT, SFTP details are not Provide the SFTP
Through not provided. GCT checks for the provided details before opening
Please enter existence of SFTP LCT
SFTP details details
A50023-K4045-X060-01-7673 33
2.2.1.7 SCS
The table below has troubleshooting information for SEL entries generated by SCS.
Severity Source Description General information Troubleshooting information

type Probable cause Solution
Error Daemon Request to Message received by An operator has Restart the SCS
stop the SCS the SCS Daemon to made a shutdown Daemon.
Daemon shutdown the Server. request.
received.
Error Daemon Abnormal child A supervised program Supervised program The SCS Daemon
termination. terminated. crash. automatically restarts
the failed process.
Error Daemon SCS Daemon Mismatch between the Crash of the SCS Check that the SCS
not found. SCS lock file informa- Daemon. Daemon is running. If
tion and the SCS not, restart it.
Daemon state (not
available).
Error Daemon Supervised A STOP signal has An operator has sent If the process exists,
program being sent to one a STOP signal to the send a CONT signal to
stopped. supervised program. supervised program. the stopped process.
Table 10 SEL entries generated by SCS
34 A50023-K4045-X060-01-7673
2.2.2 Alarm logs

The table below has troubleshooting information for alarm log/list entries generated by
TNMS NCT’s components.
Table structure for alarm log entries
ವ Object type - indicates the type of the alarming object inside the NE.
ವ Severity - indicates the severity of the alarm, for example major, minor, critical.
ವ Cause - indicates the reason for the alarm.
ವ General information - indicates the nature of the alarm at hand.
ವ Possible cause(s) - provides a possible reason for the problem.
ವ Troubleshooting - provides a possible solution for the problem.
Object Severity Cause General Possible cause(s) Troubleshooting

type information
Security Major Unsuccessful Login status The number of attempts Wait one hour and login
Logins that a user made for again.
Exceeded login with wrong Unlock the user after ascer-
(EXCLOGIN) password is greater then taining that the user tried to
the allowed limit login with wrong password.
Contact your administrator or
Coriant.
SCS Major Software Not enough One or all Oracle Check Oracle instance pro-
processes process are down cesses, including the listener
SCS Major File System File system The reported file system In the reported file system
out of space has reached a certain delete unused files.
disk occupation level
SCS Critical Software Jboss down The Jboss inside the Check the running processes
JVM is not available using the emsstarterdae-
mon.sh status command.
Also check server.log for
more details
SCS Critical Software Generic The Jboss inside the Check the running processes
mediator JVM is not available using the emsstarterdae-
down mon.sh status command.
Also check gm_server.log for
more details
Table 11 Most frequent alarms generated by TNMS NCT
A50023-K4045-X060-01-7673 35

type information
Generic Major Connection Loss of con- ವ The GNE is con- Reestablish the connectivity
Mediator Loss to GNE nectivity to nected via the pro- between TNMS NCT and the
(GNELOSS) the DCN tection path or the GNE:
Master Agent GNE ವ Check DCN Network
is not connectable. infrastructure.
ವ A LAN cable con- ವ Check connection on Q-
necting the Master interface of MA/SA/SC
Agent GNE and controller cards.
Slave Agent GNE is
disconnected. The
NEs connected via
that SA GNE lose
communication and,
if no TNEF Alarm is
Active (raised),
TNMS NCT raises
this alarm.
ವ A lower cost NE that
is configured to com-
municate with the
GNE via the working
path is connecting
via the protection
path. If no TNEF
Alarm is Active
(raised), TNMS NCT
raises this alarm.
Table 11 Most frequent alarms generated by TNMS NCT (Cont.)
36 A50023-K4045-X060-01-7673

type information
Backup Critical File system Full Database ವ Invalid file permis- ವ Make sure you have the
and and/or Backup sions, or no permis- correct set of permis-
Restore software failure sions to write the sions to perform a full
output file; backup;
ವ Not enough avail- ವ Make sure you have
able space in the file enough space available.
system. Older Manually trigger a full backup
archive logs can only operation:
be deleted after a
successful backup ವ Windows:
operation On TNMS NCT Server
machine, run as adminis-
trator: <TNMS installa-
tion folder>\Coriant\
TNMS\backuprestore\
oracle_full_backup.bat
ವ Solaris/Linux:
On TNMS NCT Server
machine, run as oracle
user: /opt/cori-
ant/tnms/backupre-
store/oracle_full_backup
.sh
Backup Major File system Partial ವ Incorrect file path; ವ The backup path must
and and/or Database ವ Invalid file permis- already exist;
Restore software Backup sions, or no permis- ವ Make sure you have the
failure sions to write the correct set of permis-
output file; sions to perform a partial
ವ Not enough avail- backup;
able space in the file ವ Make sure you have
system. enough space available.
Refer to the Administration
Manual, Backup and Restore
chapter for more information
about the backup path as
well as for the procedures to
perform a partial backup.
Table 11 Most frequent alarms generated by TNMS NCT (Cont.)
A50023-K4045-X060-01-7673 37
2.2.3 Backup logs

The table below has troubleshooting information for Backup operations log/list entries.
Table structure for backup log entries
ವ Severity - indicates the severity of the event, that is message, warning or error.
ವ Description - displays information on the event.
ವ General information - indicates the nature of the alarm at hand.
ವ Possible cause(s) - provides a possible reason for the problem.
ವ Solution - provides a possible solution for the problem.
Severity Description General Troubleshooting information

information Probable cause Solution
Error TNMS lost the Oracle database D Backup operation D Check Backup operation
connection to refuses new connec- did not run daily using the following steps:
the database tions when the disk as expected. To know the status of the
due to disk full in quota is full. Running out of Backup operation, inspect
the server. In normal conditions, disk space due to the file RMAN_TNMS.log,
Oracle performs undeleted archive stored in the B&R applica-
maintenance opera- logs. tion folder to verify that it
tions to reclaim disk has been running daily as
space by: E Wrong configura- expected (refer to chapter
tion of Oracle Backing up the Oracle
ವ Performing a
short and long database in the Installa-
daily backup
term policies tion Manual for details).
operation which
To delete the archive logs,
deletes the
manually run the Backup
archive logs, and
by using the script
ವ Purging trace
oracle_full_backup.
and dump files
bat, (or
according to the
oracle_full_backup.
corresponding
sh) stored in the B&R
retention poli-
application folder.
cies.
To understand why
Backup operation did not
run as expected, contact
Coriant technical support.
E Check that Oracle short and

long term policy is defined
according to the Oracle
chapter in the Administration
Manual.
Table 12 Backup entries
38 A50023-K4045-X060-01-7673
2.3 Tracing
The goal of tracing is to analyze errors out of the tracing information and possible
database backup sets (database dumps). The following traces are supported:
ವ Client.
All the Client components use log4j.xml for tracing.
ವ Server.
Components like Topo, Fault, Log, EM/NE, USM, SCS and others, use log-
ging.properties for tracing.
The components use the unix syslog daemon for tracing. The log files can be found in
/coriant and /opt/coriant:
ವ Mediator: the mediator provides an internal system tracing as well as persistent spy-
traces containing interface traces to the GM and NEs.
ವ Supervision processes: that is emsstarterdaemon and wrappers.
ವ SCS server.
Trace level definition
The system supports the following trace levels which are managed via the menu Admin-
istration > System > Debug Settings:
ವ Debug level - all function entry and exit (public) are traced at DEBUG level. All infor-
mation exchanged between components (including parameter values) must be
logged at DEBUG level. This will be used in worst case when no other error trace or
symptoms help in diagnosing the error. It will be like a debug call stack trace for
developers. Please note, trace level "DEBUG" is not support by the spy trace.
ವ Info level - At info level we will trace all information that a developer feels is going
to be useful for diagnosing errors. All information which is exchanged between com-
ponents (without parameter values) must mandatory logged at INFO level. This
should be done by the receiver Common Function (CF). Information exchanged
between client and server are only logged in the Client-sided ServiceLocator.
ವ Warning level - WARNING will be minor errors from which the system can recover
on its own without manual intervention for example PM gives LogM some log setting
values during initialization from db scripts, but if LogM finds them out of valid range
it can set it to a suitable default but logs this as a warning.
ವ Error level - Error is something from which the system cannot recover from the
error, however it can proceed with other operations. All exceptions are logged as
ERROR. Under J2EE also Stack traces might be logged.
The default trace settings are:
ವ Interface traces activated with info trace level.
ವ System internal traces activated with warning trace level.
A50023-K4045-X060-01-7673 39
2.4 GUI messages

The TNMS NCT interface provides relevant information to the user through the status
bar or popup messages. These messages are usually triggered by system performance
issues, since most task-related messages are displayed in the System Event Log
window instead.
Popup message Status bar Probable cause Solution

message
“A queue for “Message overflow” If the rate of notifi- Logoff and login
incoming messages cations sent from again in the client.
had an overflow the server is too
condition. All high or sustained
queued messages for too long, the
have been dis- client queue fills up
carded. The dis- before the client is
played data is out of able to process
sync. Do you want them, eventually
to logoff?” leading to a notifica-
tion being lost.
“JMS Connection - The notification Check if all NTP
Loss” synchronism servers configured
between TNMS on the machine
NCT Client and hosting the TNMS
TNMS NCT Server NCT Server and
fails. Client are all cor-
rectly
configured and that
the deviation
between them (in
case more than 1 is
configured) is not
greater than 1
minute.
Table 13 Errors displayed in the TNMS NCT interface
40 A50023-K4045-X060-01-7673
Troubleshooting Manual (TSMN) Oracle
3 Oracle
Oracle has policies for controlling the information-retention period of its trace files. In
some runtime scenarios Oracle can write information at such a rate that its file system
runs out of capacity, at which point those policies become inadequate.
When this happens, an alarm is generated. You must respond by cleaning up the trace
files as user Oracle with Data Base Administrator (DBA) rights.
Proceed as follows:
ವ Issue
# su - oracle
ವ Issue
$ adrci
ವ Issue
adrci> purge -age 8640 -type TRACE
adrci> quit
g The argument figure to purge is time in minutes.

For your convenience:
4 hours = 240; 6 hours = 360; 8 hours = 480; 12 hours = 720;
1 day = 1440; 3 days = 4320; 5 days = 7200;
6 days = 8640; 7 days = 10080; 14 days = 20160; 30 days = 43200.
A50023-K4045-X060-01-7673 41
Oracle Troubleshooting Manual (TSMN)
42 A50023-K4045-X060-01-7673
Troubleshooting Manual (TSMN) Operator hints
4 Operator hints
The following chapter describes general operational hints that were described in the
Customer Release Notes (CRN) in former versions.
To get the full list of limitations affecting the release, please read the List of Generic
Faults (LGF). This chapter contains the limitations not currently planned for future
releases.
Hint Id Functional Limitation/Restriction Title Related Related With Work-

Area Feature MRs around
HINT-230 Generic EMS functionalities based on the NE TD016098 Yes
Mediator cost are not working well in mixed
networks
HINT-286 Generic In an auto discover scenario the DCN TD015481 Yes
Mediator routes are not automatically updated.
HINT-11 NEC- Error when stopping EmlMediator TD007875 Yes
DWDM service
HINT-12 NEC- Error when starting EmlMediator TD007875 Yes
DWDM service
HINT-14 NEC-NGM Special mapping of static CCs on TD012380 Yes
hiT7065 5.1 and 5.2 126xE1 card in
HO trail mode enabled
HINT-310 NEC-NGM hiT 7080 - Swap from 4.15 to 4.2 TD020813 Yes
needs a manual step which leads to
wrong Swap state
HINT-303 DCN Import from Core TNMS-42 TD021532 Yes
HINT-317 Not possible to activate an NE in TNMS-742 TD020869 Yes
TNMS if an user uses the Configure
exclusive command
HINT-329 EM/NE 7100 RNEs are not correctly auto dis- TNMS-1349 TD021963 Yes
MVM covered if their user/passwords are
different than of the PGNE
Table 14 Operator Hints
4.1 EMS functionalities based on the NE cost are not working

well in mixed networks (HINT-230)
In mixed networks where hiT7300 5.30.xx and 5.10.xx are present, the functionalities
based on the route costs calculated by the NE are not working well.
In 5.10.xx the costs are calculated by the NE distance (hops). Typical values for costs
calculated by this method are less than 20.
In 5.30.xx the costs are calculated by OSPF. Typical values for costs calculated by this
method are greater than 100.
Operator impact / Consequences
A50023-K4045-X060-01-7673 43
Operator hints Troubleshooting Manual (TSMN)
In a mixed network where a DCN have gateways in different versions, the cost of client
NEs are calculated by different criteria causing the following issues in the EMS:
Sort By Connectivity: The NEs are sorted by its route cost in the Domain, however the
cost has a different meaning causing wrong connectivity order
Load Balance: The costs calculated by a gateway 5.30.50 or higher versions are always
bigger than the costs calculated by a gateway 5.10.2x or lower versions. Due to this dif-
ference, the EMS will consider the gateway 5.10.2x the route with less cost connecting
all client NEs via the gateway 5.10.2x and none via the gateway 5.30.xx.
Working Instruction
For Sort By Connectivity issue there is no workaround.
For Load Balance issue in mixed networks, the update must be done manually.
4.2 In an auto discover scenario the DCN routes are not auto-
matically updated. (HINT-286)
In an auto discover scenario (and only for hiT7300), when a change occurs in the
network that affects the routes, the DCN info (NEs table) is not automatically updated.
This leads to several failures in the DCN in cases of switches, because EMNE tries to
connect to non-existing routes.
Old and new routes are present in the NEs table leading to NEs connection failure.
Working Instruction
The old routes must be deleted manually from the NEs table.
4.3 Error when stopping EmlMediator service (HINT-11)

Try to stop the EmlMediator service
SCM returns error 1053.
Working Instruction
Close the error window.
If the service is in state "stopped", then no action is required.
If the service is in state "stopping", open "Task Manager" and kill the EmlMediator.exe
process.
If you were not able to kill the process, a reboot to the machine is required.
4.4 Error when starting EmlMediator service (HINT-12)

Try to start the EmlMediator service
SCM returns error 1067.
Working Instruction
If failed to start, try again.
44 A50023-K4045-X060-01-7673
If the fail persists after several attempts, reboot the machine.
4.5 Special mapping of static CCs on hiT7065 5.1 and 5.2

126xE1 card in HO trail mode enabled (HINT-14)
Special mapping of static CCs on hiT7065 5.1 and 5.2 126xE1 card in HO trail mode
enabled.
Due to special mapping of static CCs, the operator may not be able to manually route
the path/service correctly as desired. (for example, if the operator would expect, follow-
ing common sense, that first E1 TP is statically connected to first VC12 TP of SDH Inter-
face, manual routing may end up with error).
Working Instruction
For manual routing when using 126xE1 card on hiT7065 5.1 and 5.2 in HO trail mode,
operator should always check static cross-connections end points directly in TNMS or
check statically connected TPs in CRN in order to create correct route.
The table bellow shows all static cross-connections on 126xE1 card. First column rep-
resents A-End (PDH ports) and remaining columns represents Z-End (SDH Interface).
PDH Port # VC4 K L M TP index

1 1 1 1 3 3
2 1 2 1 3 24
3 1 3 1 3 45
4 1 1 2 3 6
5 1 2 2 3 27
6 1 3 2 3 48
7 1 1 3 3 9
8 1 2 3 3 30
9 1 3 3 3 51
10 1 1 4 3 12
11 1 2 4 3 33
12 1 3 4 3 54
13 1 1 5 3 15
14 1 2 5 3 36
15 1 3 5 3 57
16 1 1 6 3 18
17 1 2 6 3 39
18 1 3 6 3 60
19 1 1 7 3 21
Table 15 Static cross-connections on 126xE1 card
A50023-K4045-X060-01-7673 45

20 1 2 7 3 42
21 1 3 7 3 63
22 2 1 1 3 3
23 2 2 1 3 24
24 2 3 1 3 45
25 2 1 2 3 6
26 2 2 2 3 27
27 2 3 2 3 48
28 2 1 3 3 9
29 2 2 3 3 30
30 2 3 3 3 51
31 2 1 4 3 12
32 2 2 4 3 33
33 2 3 4 3 54
34 2 1 5 3 15
35 2 2 5 3 36
36 2 3 5 3 57
37 2 1 6 3 18
38 2 2 6 3 39
39 2 3 6 3 60
40 2 1 7 3 21
41 2 2 7 3 42
42 2 3 7 3 63
43 1 1 1 2 2
44 1 2 1 2 23
45 1 3 1 2 44
46 1 1 2 2 5
47 1 2 2 2 26
48 1 3 2 2 47
49 1 1 3 2 8
50 1 2 3 2 29
51 1 3 3 2 50
52 1 1 4 2 11
53 1 2 4 2 32
46 A50023-K4045-X060-01-7673

54 1 3 4 2 53
55 1 1 5 2 14
56 1 2 5 2 35
57 1 3 5 2 56
58 1 1 6 2 17
59 1 2 6 2 38
60 1 3 6 2 59
61 1 1 7 2 20
62 1 2 7 2 41
63 1 3 7 2 62
64 2 1 1 2 2
65 2 2 1 2 23
66 2 3 1 2 44
67 2 1 2 2 5
68 2 2 2 2 26
69 2 3 2 2 47
70 2 1 3 2 8
71 2 2 3 2 29
72 2 3 3 2 50
73 2 1 4 2 11
74 2 2 4 2 32
75 2 3 4 2 53
76 2 1 5 2 14
77 2 2 5 2 35
78 2 3 5 2 56
79 2 1 6 2 17
80 2 2 6 2 38
81 2 3 6 2 59
82 2 1 7 2 20
83 2 2 7 2 41
84 2 3 7 2 62
85 1 1 1 1 1
86 1 2 1 1 22
87 1 3 1 1 43
A50023-K4045-X060-01-7673 47

88 1 1 2 1 4
89 1 2 2 1 25
90 1 3 2 1 46
91 1 1 3 1 7
92 1 2 3 1 28
93 1 3 3 1 49
94 1 1 4 1 10
95 1 2 4 1 31
96 1 3 4 1 52
97 1 1 5 1 13
98 1 2 5 1 34
99 1 3 5 1 55
100 1 1 6 1 16
101 1 2 6 1 37
102 1 3 6 1 58
103 1 1 7 1 19
104 1 2 7 1 40
105 1 3 7 1 61
106 2 1 1 1 1
107 2 2 1 1 22
108 2 3 1 1 43
109 2 1 2 1 4
110 2 2 2 1 25
111 2 3 2 1 46
112 2 1 3 1 7
113 2 2 3 1 28
114 2 3 3 1 49
115 2 1 4 1 10
116 2 2 4 1 31
117 2 3 4 1 52
118 2 1 5 1 13
119 2 2 5 1 34
120 2 3 5 1 55
121 2 1 6 1 16
48 A50023-K4045-X060-01-7673

122 2 2 6 1 37
123 2 3 6 1 58
124 2 1 7 1 19
125 2 2 7 1 40
126 2 3 7 1 61
4.6 TNMS NCT allows changing a user's password that does

not differ in 4 chars from last one (HINT-311)
TNMS NCT and NE user password rules (e.g. complexity rules) are generally aligned.
Anyhow when changing a hiT 7300 user password the LCT/NE will make sure that the
new password differs in at least 4 characters. TNMS NCT does not do this. TNMS NCT
only verifies that the password is not the same as the previous. So via TNMS NCT it is
possible to define passwords for hiT 7300 NE users, which are very similar to the
previous password.
TNMS NCT will allows to modify hiT 7300 NE user password to a password, which is
very similar (less than 4 character difference) to the previous one.
Working Instruction
Though TNMS NCT checks for many password complexity rules, it is up to the user to
not choose a password very similar to the previous one when modifying the NE user
password for hiT 7300 NEs.
4.7 DCN Import from Core (HINT-303)

For large networks, it's recommended that the operator exports only the DCN from core
or use the "Import from Core => Scheduled DCN" option. If the export from Core has
more than 500 NEs it's also recommended use the Schedule Import option
Manual import from Core might end without success.
Working Instruction
Configure a schedule import from Core (that runs entirely in the server).
4.8 Not possible to activate an NE in TNMS NCT if an user

uses the Configure exclusive command (HINT-317)
When there is an user connected on the CLI with configuration on exclusive mode the
Juniper Provider(MVM) will not be able to connect.
A message will be displayed to the System Event Log about the configuration being
locked and who is locking it.
A50023-K4045-X060-01-7673 49
TNMS NCT will not be able to connect to Juniper MX/PTX when there is a user with con-
figuration exclusive mode already logged in the command line.
Working Instruction
In order to assure that there are no conflicts between TNMS NCT and any command line
that the operator is using, it is advised that the former uses private and shared sessions.
4.9 7100 RNEs are not correctly auto discovered if their

user/passwords are different than of the PGNE
When making an automatic network discovery, if some of the 7100 RNEs in the ring
have different authentication settings than the ones used by the GNEs (user/password)
of that network, they are discovered with the same settings and type as the GNE.
Because these setting don't match the current RNE configuration, the NE is not acti-
vated in the DCN and the operator should set them according to the RNE.
Working Instruction
When managing a discovered network the operator should take this issue into account
when there are some RNE which are not automatically connected. The operator should
verify and correct the credentials set in those NEs property pages.
50 A50023-K4045-X060-01-7673
Abbreviations
Abbreviations
These abbreviations are intended for the entire TNMS product range and may not apply
to this document in particular.
ACS Actual Creation State
ALS Automatic Laser Shutdown
ASON Automatic Switched Optical Network
ASAP Alarm Severity Assignment Profile
BFD Bidirectional Forward Direction
BSHR Bidirectional Self Healing Ring
CAM Common Array Manager
CBS Committed Burst Size
CC Cross Connection
CDM Cross-domain Manager
CIR Committed Information Rate
CFM Connectivity Fault Management
CLI Console Interactive
CLFI Common Language Facility Identification
CORBA Common Object Request Broker Architecture
CPU Central Processing Unit
CSPF Constrained Shortest Path First
CST Central Standard Time
CSV Comma-Separated Values
DA (Oracle’s Sun Storage) Disk Array
DB Database
DCN Data Communications Network
DHCP Dynamic Host Configuration Protocol
DNS Domain Naming Service
DSR Dynamic Source Routing
DWDM Dense Wavelength Division Multiplexing
ELP Ethernet Linear Protection
EM Element Manager
EML Element Manager Layer
Issue date: November 2015

Abbreviations
EM/NE Element Manager/Network Element object management
EON Embedded Optical Network
FA-LSP Forwarding Adjacency LSP
FEC Forward Error Correction
FTP File Transfer Protocol
GBE Gigabit Ethernet
GCT GUI Cut-Through
GFPG Generic Framing Procedure Group
GM Generic Mediator
GmbH Gesellschaft mit beschränkter Haftung (Company with limited liability)
GMPLS Generalized Multi-Protocol Label Switching
GMT Greenwich Mean Time
GNE Gateway Network Element
GPS Global Positioning System
GUI Graphical User Interface
HW Hardware
IMA Independent Management Architecture
IMN Installation Manual
IP Internet Protocol
JRE Java Runtime Environment
LACP Link Aggregation Control Protocol
LAG Link Aggregation
LAN Local Area Network
LAPS Linear Automatic Protection Switching
LE Load Equivalent
LCT Local Craft Terminal
LDAP Lightweight Directory Access Protocol
LO Low Order
LoQ List of Quantities
LoM List of Materials
LSP Label Switched Path
LSR Label Switch Router

Abbreviations
MDI Multiple Document Interface
MIB Management Information Base
MLO Multi-Layer Optimization
MPLS-TP Multiprotocol Label Switching Transport Profile
MSDE Microsoft SQL Server Desktop Engine
MSP Multiplex Section Protection
MTOSI Multi Technology Operations System Interface
MVM Multi-Vendor Mediator
NBI Northbound Interface
NE Network Element
NEC NE Controller
NG Next Generation
NIC Network Interface Card
NMS Network Management System
NNI Network to Network Interface
NTFS (Microsoft’s) New Technology File System
NTI Northbound TMF Interface
NTP Network Time Protocol
NW Network
OAM Operation, Administration and Maintenance
OCH Optical Channel
ODU Optical Data Unit - transport technology
OM Optical Manager or Optical Management
OMS Optical Multiplex Section
OMT Object Model Template
OS Operating System
OPU Optical Payload Unit - transport technology
OTN Optical Transport Network
OTS Optical Transport Section - transport technology
OTU Optical Transport Unit - transport technology
PBS Peak Burst Size

Abbreviations
PC Personal Computer
PCEP Path Computation Engine Protocol
PDF Portable Document Format
PIR Peak Information Rate
PMP Performance Measurement Point
PT Physical Trail
PTC Planning Tool Connector
PTP Physical Termination Point
RAID Redundant Array of Independent Disks
RE Route Element
RNE Remote Network Element
SBI Southbound interface
SCP Secure Copy
SCSI Small Computer System Interface
SDH Synchronous Digital Hierarchy
SEL System Event Log
SFTP Secure File Transfer Protocol, or Secure Shell File Transfer Protocol
SLA Service-Level Agreement
SNC SubNetwork Connection
SNCP SubNetwork Connection Protection
SNMP Simple Network Management Protocol
SONET Synchronous Optical Networking
SPC Soft Permanent Connection
SQL Structured Query Language
SRLG Shared Risk Link Group
SSH Secure Shell
STP Spanning Tree Protocol
SVID Service Virtual Local Area Network Identifier
SW Software
TC Topological Container or TransConnect
TCP/IP Transport Control Protocol/Internet Protocol
TL1 Transaction Language 1

Abbreviations
TE-Link Traffic Engineering-Link
TMN Telecommunications Management Network
TN TransNet
TNMS Telecommunications Network Management System
TNMS NCT Telecommunications Network Management System Network Craft Terminal
TP Terminal Point
USB Universal Serial Bus
UMN User Manual
UNI User-to-Network Interface
UNI-S User-to-Network Interface-Service
UNO Universal Network Object
UPS Uninterruptible Power Supply
UPSR Unidirectional path-switched ring
VC Virtual Container
VLAN Virtual LAN
WAN Wide Area Network
WLAN Wireless LAN
XC Cross Connection
X-NE Cross-NE
XML eXtended Markup Language

Abbreviations

Glossary
Glossary
These glossary entries are intended for the entire TNMS product range and may not
apply to this document in particular.
@CT @CT is a web-based craft terminal (that is, element manager) software which provides
web access to hiT 7300 network elements (NEs) in the customer network without the
use of a management system. It communicates via SNMP with the NEs and uses the
FTPS for upload/download of software or other data configuration (for example, log
files).
3DES Triple DES is the common name for the Triple Data Encryption Algorithm (TDEA or
Triple DEA) symmetric-key block cipher, which applies the Data Encryption Standard
(DES) cipher algorithm three times to each data block.
Actual Creation Is the current state of the path which results from the accumulation of the actual creation
State (ACS) states of the path’s route elements.
Advanced Encryp- Is a specification for the encryption of electronic data. AES is based on a design principle
tion Standard (AES) known as a substitution-permutation network, and is fast in both software and hardware.
Alarm An alarm is a management mechanism intended to inform the user that there is a
standing fault condition in the system.
Alarm log An alarm log provides a list of the alarms associated with a managed object, and
provides the following information about each of the alarms:
ವ the identification of the affected object
ವ the identification of the failed NE or the NE in which the failed unit resides
ವ the alarm severity
ವ the time the event occurred
ವ the indication whether the alarmed event is service affecting or not
ವ the location and the affected traffic
Alarm severity Each failure is assigned a severity. The following values are used:
ವ indeterminate
ವ critical
ವ major
ವ minor
ವ warning
ವ cleared alarms
ವ not Existent
ವ not Alarmed
Element Manager (EM) can configure the severity which is assigned to each fault cause
by an alarm severity assignment profile. In addition, EM can specify that a fault cause
shall not be alarmed. These fault causes will be blocked, hence do not lead to any LED
alarm indications, log entries or alarm reporting.
Alien wavelength A wavelength that does not originate from a transponder or muxponder card, but is still
allowed to be multiplexed into the aggregate line signal for transport as an optical
channel by the system.
Issue date: November 2015 57

Glossary
Automatic Laser Is a technique used to automatically shut down the output power of the transmitter in
Shutdown (ALS) case of fiber break. This is a safety feature that prevents dangerous levers of laser light
from leaking out of a broken fiber, provided ALS is provisioned on both ends of the fiber
pair.
Alarm Severity The Alarm Severity Assignment Profile is a feature that allows the management of Alarm
Assignment Profile Severity profiles in TNMS and also at the NE side. .
(ASAP)
Automatically- ASON domains are built on the VC4 layer of hiT 7065, 7070 or 7080, and on OCh layer
Switched Optical of hiT 7300 and on ODU2 layer of hiT 7100, which have a Control Plane. The Control
Networks (ASON) Plane uses network-generated signaling and routing protocols to set up or release a
connection, and can restore one when it fails. ASON domains can be built up as part of
the transport network. They provide the benefit of easy end-to-end provisioning, and
fault and protection management. Soft permanent connections (SPCs) connect both
endpoints (NE1 and NE2) within an ASON domain. If a path fails, an alternative path is
automatically used.
ASON Call A Call is a Soft Permanent Connection between two end-points (inside the same domain
or between different domains) and defines the type and attributes of the connection. The
establishment of a Call leads to having a path (and/or multiple alternative paths) con-
necting the end-points that respect the constraints and attributes defined in the Call.
Bidirectional Self- Is a telecommunications term for loop network topology, a common configuration in tele-
healing Ring (BSHR) communications transmission systems, this loop or ring is used to provide redundancy.
The system consists of a ring of bidirectional links between a set of stations. In normal
use, traffic is dispatched in the direction of the shortest path towards its destination. In
the event of the loss of a link, or of an entire station, the two nearest surviving stations
"loop back" their ends of the ring. In this way, traffic can still travel to all surviving parts
of the ring, even if it has to travel "the long way round".
Capacity Planning Capacity planning is the process of determining the capacity needed by a system to
meet future needs.
Card A card is a plug-in unit that occupies one (or multiple) shelf slots. Cards perform specific
electrical and/or optical functions within an NE.
Each card has a faceplate with information LEDs and, in most cases, several ports for
interconnection of optical fibers and/or optical interfaces.
Card slot A card slot is the insertion facility for a card in a shelf. Each card slot is designed for one
or several particular card types.
Mechanical coding elements make sure that each card can be fully inserted only into a
card slot that is suitable for the given card type. Therefore, fundamental shelf equipping
errors (which might cause hardware damage or fatal malfunctions) are impossible.
Ethernet Connectiv- Is an end-to-end perservice Ethernet layer OA&M protocol. IEEE 802.1ag CFM is a
ity Fault Manage- service level OA&M protocol that provides tools for detecting and isolating connectivity
ment (CFM) failures in the network. This includes proactive connectivity monitoring, fault verification
and fault isolation for large Ethernet Metropolitan Area Networks (MANs) and WANs.
Committed Informa- Is the guaranteed average rate (in Mbit/s) at which the information units are transferred
tion Rate (CIR) through the port over a measurement interval.
CLFI CLFI Codes provide a standard, mnemonic naming scheme to uniquely identify cable
58 Issue date: November 2015

Glossary
and transmission facilities between two standardized locations within a network. It

comprises facility designation, facility type, channel/pair/time slot, location of facility
terminal A and location of facility terminal Z.
Commissioning Commissioning an network element (NE) is the process of taking an installed NE and
bringing it in to an operational state. The NE commissioning phase is performed after
the NE is installed and powered-up.
Controller card NE controller cards provide the central monitoring and controlling functions of the
system, as well as the MCF to operate the Q and QF Ethernet interfaces.
The controller card performs the following main functions: Fault Management, Perfor-
mance Management, Configuration Management, Security Management, Equipment
Management, Communication Management, Software Management (performing all
software downloads, uploads, and software integrity functions) and controlling the NE
alarm LEDs.
Data Communica- Data Communications Network is a management network for telecommunication trans-
tion Network (DCN) port systems.
A DCN domain interconnects several NEs for the purpose of network management. The
communication is established via the Optical Supervisory Channel (OSC) of the optical
links and an Ethernet/L2 switching network implemented by the NEs.
Dense Wavelength In fiber-optic communications, wavelength-division multiplexing (WDM) is a technology

Division Multiplex- which multiplexes a number of optical carrier signals onto a single optical fiber by using
ing (DWDM) different wavelengths (colors) of laser light, that is, simultaneously places a large
number of optical signals (in the 1550 nm band) on a single optical fiber. This technique
enables bidirectional communications over one strand of fiber, as well as multiplication
of capacity.
Data Encryption Is a widely-used method of data encryption using a private key. DES applies a 56-bit key
Standard (DES) to each 64-bit block of data. The process can run in several modes and involves 16
rounds or operations.
Dynamic Host Con- Is a standardized networking protocol used on IP networks that dynamically configures
figuration Protocol IP addresses and other information that is needed for Internet communication. DHCP
(DHCP) allows computers and other devices to receive an IP address automatically from a
central DHCP server, reducing the need for a network administrator or a user from
having to configure these settings manually.
Domain TNMS allows you to restrict user groups to operate only a set of NEs or DCN subnets
instead of the entire network. This partitioning is called a “Domain” and limits the oper-
ation on nodes outside of their partitions by assigning user groups to domains. Further,
you can also assign policies to domains for further control and security, limiting the user
groups to specific menu entries and actions.This arrangement is required, for example,
in network centers that are responsible for maintaining only a subset of the nodes. The
main purpose is security: it avoids that a login to the system grants access to the entire
network.TNMS now supports the creation, modification or deletion of multiple domains,
granting or restricting their accesses. By default, all NEs belong to the GLOBAL domain
which cannot be modified or deleted.
Ethernet Linear Pro- Is a protection scheme defined in the ITU-T G.8031 standard designed to protect point-
tection (ELP) to-point Ethernet paths such as VLAN based Ethernet networks. To achieve protection
ELP uses two disjointed paths, a working path and a protection path, traffic is carried

Glossary
firstly on the active path (working path) andin case of failure, traffic is switched to the
protection path. Both paths can be monitored using OAM protocols like CFM.ELP
provides 1:1 bi-directional protection switching with revertive mode capabilities.ELP
must first be configured at the NE side via the LCT, only then they are visible in TNMS
so that you can use it in the E-LAN and E-Line service creation via the New Ethernet
Service wizard.ELP is supported in specific network elements and cards only. Refer to
the NE dedicated documentation fore more information.
Element Manager Network elements enable the user to perform operation, administration and mainte-
(EM) nance tasks with the NE system in a GUI environment.
Ethernet Ethernet is a family of frame-based computer networking technologies for LANs. It

defines a number of wiring and signaling standards for the physical layer, through
means of network access at the MAC/Data Link Layer, and a common addressing
format.
Fault management Fault management reports all hardware and software malfunctions within an NE, and
monitors the integrity of all incoming and outgoing digital signals.
Forward Error Cor- Forward Error Correction (FEC) or channel coding is a technique used for controlling
rection errors in data transmission over unreliable or noisy communication channels.
File Transfer FTP is a network protocol used to transfer files from one computer to an NEand vice-
Protocol (FTP) versa through the network.
Frequency Frequency is a physical attribute of a wave (for example, an optical wave), defined as
the number of wave cycles per time unit. The frequency is directly related to the wave-
length.
Generalized Multi- Is a protocol suite extending MPLS to manage further classes of interfaces and switch-
Protocol Label ing technologies other than packet interfaces and switching, such as time division mul-
Switching (GMPLS) tiplex, layer-2 switch, wavelength switch and fiber-switch.
Internet Protocol (IP) Is the principal communications protocol in the Internet protocol suite for relaying data-
grams across network boundaries. Its routing function enables internetworking, and
essentially establishes the Internet.
Internet Protocol Is a connectionless protocol for use on packet-switched networks. It operates on a best
version 4 (IPV4) effort delivery model, in that it does not guarantee delivery, nor does it assure proper
sequencing or avoidance of duplicate delivery. These aspects, including data integrity,
are addressed by an upper layer transport protocol, such as the Transmission Control
Protocol (TCP).
Job A schedule load that must be processed by the system.
Link Aggregation Within the IEEE specification the Link Aggregation Control Protocol (LACP) provides a
Control Protocol method to control the bundling of several physical ports together to form a single logical
(LACP) channel. LACP allows a network device to negotiate an automatic bundling of links by
sending LACP packets to the peer (directly connected device that also implements
LACP).
Link Aggregation Allows a bridge to treat multiple physical links between two end-points as a single logical
(LAG) link, referred to also as a port-channel. The feature can be used to directly connect two
switches when the traffic between them requires high bandwidth and/or reliability, or to
provide a higher bandwidth connection to a public network. For this purpose, all the

Glossary
physical links in a given port-channel must operate in full-duplex mode and at the same
speed.If a physical port or the related link of a LAG fails, the traffic previously carried
over the failed link automatically is switched to the remaining link(s) of the LAG (rapid
reconfiguration). Bandwidth degradation is an obvious impact if the sum of throughput
of the two/multiple aggregated links are higher than the throughput of the remaining
link(s). Be aware that certain link failures are not always visible to both ends of a link.
Link Aggregation Control Protocol (LACP) and Automatic Laser Shutdown (ALS)
enabled, guarantees that both ends of a link properly detect all failures and perform the
correct response.LAG groups must first be created at the NE side via the LCT, only then,
they are visible in TNMS so that you can use it in the E-LAN and E-Line service creation
via the New Ethernet Service wizard. LAG is supported in specific network elements and
cards only. Refer to the NE dedicated documentation fore more information.
Laser A laser is a device that generates an intense narrow beam of light by stimulating the
emission of photons from excited atoms or molecules.
Laser safety Laser safety rules are a group of mechanisms and actions necessary to protect all users
from harmful laser light emissions.
Local Craft network LCT is a client-based craft terminal (that is, element manager) software which provides
(LCT) access to network elements (NEs) in the customer network without the use of a man-
agement system.
Lightweight Direc- Is an application protocol for accessing and maintaining distributed directory information
tory Access Protocol services over an Internet Protocol network.
(LDAP)
Line interface A line interface is a transponder interface that faces the line side of the link. Contrast
with “client interface” which faces the client equipment side of the link.
Long Haul (LH) hiT 7300 LH segment is a DWDM application characterized by a reach of more than 500
km and up to 1200 km.
Label Switched Path Is a path through an MPLS network, set up by a signaling protocol such as LDP, RSVP-
(LSP) TE, BGP or CR-LDP. The path is set up based on criteria in the forwarding equivalence
class (FEC).
Label switch router Sometimes called transit router, is a type of a router located in the middle of a Multipro-
(LSR) tocol Label Switching (MPLS) network. It is responsible for switching the labels used to
route packets. When an LSR receives a packet, it uses the label included in the packet
header as an index to determine the next hop on the Label Switched Path (LSP) and a
corresponding label for the packet from a look-up table. The old label is then removed
from the header and replaced with the new label before the packet is routed forward.
MD5 Message-digest algorithm is a widely used cryptographic hash function producing a

128-bit (16-byte) hash value, typically expressed as a 32 digit hexadecimal number
Maintenance Associ- Are points at the edge of the domain that define the boundaries and sends and receives
ation End Points CFM frames through the wire side (physical port) or relay function side.
(MEP)
Management Infor- Is used for backup purposes where you can plan automatic upload jobs.
mation Base (MIB)

Glossary
Multiprotocol Label Multiprotocol Label Switching (MPLS) is a mechanism in high-performance telecommu-

Switching nications networks that directs data from one network node to the next based on short
path labels rather than long network addresses, avoiding complex lookups in a routing
table. The labels identify virtual links (paths) between distant nodes rather than end-
points.
MX Juniper MX Series Universal Edge Routers are Ethernet-centric services routers that
are purpose-built for demanding carrier and enterprise applications (font: Juniper web-
site).
NetConf Network Configuration Protocol (NETCONF), is an IETF network management protocol.

NETCONF provides mechanisms to install, manipulate, and delete the configuration of
network devices. Its operations are realized on top of a simple Remote Procedure Call
(RPC) layer. The NETCONF protocol uses an Extensible Markup Language (XML)
based data encoding for the configuration data as well as the protocol messages. This
in turn is realized on top of the transport protocol.
NetServer A set of TNMS Mediation sub-systems that runs in a machine.
Network Craft NCT is a network management craft terminal (that is, element manager) software which
Terminal (NCT) is used for either local or remote network management.
Network Element A network element (NE) is a self-contained logical unit within the network. The NE can
(NE) be uniquely addressed and individually managed via software.
Each NE consists of hardware and software components to perform given electrical and
optical functions within the network.
Network Manage- The network management layer includes all the required functions to manage the optical
ment network in an effective and user-friendly way, such as the visualization of the network
topology, creation of services, and correlation of alarms to network resources.
Network topologies A topology of a network is defined by the list of NEs included in the network and the list
of links that connect those NEs (for example, point-to-point, chain, ring, and so on).
Network to Network Is an interface which specifies signaling and management functions between two net-
Interface (NNI) works. NNI circuit can be used for interconnection of IP (e.g. MPLS) networks.
Optical Channel A predefined wavelength that can be used to transmit a bit stream by means of a mod-
ulated light signal.
Optical Network An ONN is an NE where the incoming channels are either dropped or routed to a line in
Node (ONN) a different direction, outgoing channels can also be added locally. Apart from multiplex-
ing and demultiplexing an ONN NE implements optical or 3R signal regeneration and
dispersion compensation.
Optical path The path followed by an optical channel from the first multiplexer to the last demulti-
plexer.
Path Computation Implements, sets up and manages PCEP, while also notifying OM when PCEP is avail-
Engine Protocol able or unavailable to send/receive PCEP Route messages.
(PCEP)
Performance man- Performance monitoring and signal quality analysis provide information for detecting
agement and alerting, a cause that could lead to a degraded performance before a failure is
declared.

Glossary
Peak Information Is a burstable rate set on routers and/or switches that allows throughput overhead.
Rate (PIR) Related to Committed Information Rate which is a committed rate speed guaran-
teed/capped. For example, a CIR of 10 Mbit/s PIR of 12 Mbit/s allows you access to 10
Mbit/s minimum speed with burst/spike control that allows a throttle of an additional 2
Mbit/s.
Pseudo-Random Is a known sequence of bits that can be used as a test signal to measure transmission
Binary Sequence delay and bit error rate of a channel. In this test, one port inserts the PRBS signal in the
(PRBS) channel (source port) and another detects if the sequence was received correctly (sink
port). This kind of test is traffic affecting since the test sequence is inserted into the
OPUk until the test is stopped.
Physical Trails (PT) Trails are represented as Physical Trails (PTs). They connect two Physical Termination
Points (PTP) on a physical layer rate, but can also contain non-physical layers.
Planning Tool Con- Interfaces Coriant TransNet/Intelligent Optical Control DWDM network planning tool.
nector (PTC)
PMP A Performance Measurement Point is a metric represented by a set of counters for a

specific point in the network. It provides data for monitoring the performance and avail-
ability of the network.
PTX Juniper Packet Transport Routers are Converged Supercore platforms that deliver
powerful capabilities based on the Junos Express chipset and forwarding architectures
optimized for MPLS and Ethernet, with integrated, coherent 100GbE technology (font:
Juniper website).
Qualitative System Quality System Requirements are non-functional requirements that must be meet by a
Requirements System such as Reliability, Availability, Performance, Scalability, Security, Maintainabil-
ity, Portability, etc.
Required Creation Is the desired state of the path, which is set by the user upon creation.
State (RCS)
Optical Signal to OSNR is the ratio of an optical signal power to the noise power in the signal.
Noise Ratio (OSNR)
Ring network A ring network is a network topology in which each NE connects to exactly two other
NEs, forming a circular optical path for signals (that is, a ring).
Synchronous Digital Is a standardized protocol that transfer multiple digital bit streams over optical fiber using
Hierarchy (SDH) lasers or highly coherent light from light-emitting diodes. At low transmission rates data
can also be transferred via an electrical interface. The method was developed to replace
the Plesiochronous Digital Hierarchy system for transporting large amounts of telephone
calls and data traffic over the same fiber without synchronization problems.
Security manage- Security Management controls the individual access to particular NE functions via the
ment network management system and/or via a craft terminal, using a hierarchical security
management user ID, and password concept.
State Event Machine In computation, a finite-state machine is event driven if the transition from one state to
(SEM) another is triggered by an event or a message.
Service Provisioning Provisioning mode in hiT 7300.

via NMS

Glossary
The core equipment is provisioned by downloading and swapping NCFs, while

services are manually provisioned via the NMS.
When adding new services or expanding an existing network, the relevant line cards,
cross connections and internal port connections between line cards and multiplex-
ers/demultiplexers are provisioned via the NMS.
Secure Hash Algo- Is a family of cryptographic hash functions that takes an arbitrary block of data and
rithm (SHA) returns a fixed-size bit string, the cryptographic hash value, such that any (accidental or
intentional) change to the data will (with very high probability) change the hash value.
The data to be encoded are often called the message, and the hash value is sometimes
called the message digest or simply digest.
Simple Network SNMP is used in network management systems to monitor network-attached devices for
Management conditions that warrant administrative control. It consists of a set of standards for
Protocol (SNMP) network management, including an application layer protocol, a database schema, and
a set of data objects.
Software manage- Software management performs all software downloads, uploads, and software integrity
ment functions.
Secure Shell (SSH) Is a cryptographic network protocol for secure data communication, remote command-
line login, remote command execution, and other secure network services between two
networked computers that connects, via a secure channel over an insecure network, a
server and a client (running SSH server and SSH client programs, respectively).
Subsystem A subsystem is a set of shelves and cards in multicontroller NE that is controlled by a

subagent. All subagents within a multicontroller NE are controlled by the master agent.
Subsystem is defined for the HW only. In software, the concept is different. A major com-
ponent of a system. It is made up of two or more interacting and interdependent compo-
nents. Subsystems of a system interact in order to attain their own purpose(s) and the
purpose(s) of the system in which they are embedded.
Synchronous Synchronous Optical Networking and Synchronous Digital Hierarchy are standardized
Optical Networking protocols that transfer multiple digital bit streams over optical fiber using lasers or highly
(SONET) coherent light from light-emitting diodes.
Throughput Throughput measures the number of work units performed in a given time unit.
Topological Con- Defines a containment relationship between other topological container and/or NEs.
tainer (TC) This means they can contain NE symbols and other TCs. The network map is always
associated with one TC, which corresponds to a network view.
Tandem Connection TCMs are configurable parameters (via Element Manager) of the transponders. They
Monitoring (TCM) provide a Performance Management of all the Optical Transport Network (that is, end-
to-end connection) or specific sections only and implement an Optical channel Data Unit
(ODU) termination provisioned to support up to six TCM levels.
Transmission Is one of the core protocols of the Internet protocol suite (IP), and is so common that the
Control Protocol entire suite is often called TCP/IP. TCP provides reliable, ordered, error-checked
(TCP) delivery of a stream of octets between programs running on computers connected to a
local area network, intranet or the public Internet. It resides at the transport layer.
TL1 Transaction Language 1 (TL1) is a widely used management protocol in telecommuni-

cations. It is a cross-vendor, cross-technology man-machine language, and is widely

Glossary
used to manage optical (SONET) and broadband access infrastructure in North

America. TL1 is used in the input and output messages that pass between Operations
Systems (OSs) and Network Elements (NEs). Operations domains such as surveillance,
memory administration, and access and testing define and use TL1 messages to
accomplish specific functions between the OS and the NE.
TNMS Telecommunications Network Management System - is a standalone application that

provides a full range of network-management functions, from the transport network’s
physical structure and its NEs to those required for Automatically-Switched Optical
Networks (ASON), SW management (also referred to as X-NE or Cross-NE), Optical
Management and Ethernet Management.
TNMS Core TNMS Core is an integrated solution designed for large, medium and small size net-
works. It supports NEs with DWDM, OTH, SDH, PDH, Ethernet in line, star, ring and
mesh network configurations. TNMS Core can be used to manage networks in the
access, edge, metro, core and backbone levels.
TNMS CT TNMS CT is a transparent software platform for SDH and DWDM NEs using QD2, QST,
QST V2, Q3 or SNMP telegram protocols. It supports line, star, ring and mesh networks
and provides access to NEs via Ethernet interface or via a serial line interface (RS232).
TNMS DX TNMS DX is a telecommunications network management system to operate, administer

and maintain hiT 7300 NEs. It allows remote operation and control of these network ele-
ments.
TNMS NCT TNMS NCT is a lighter version of TNMS for smaller networks. It uses GM or MVM-based
mediations and includes the basic functionalities for network management.
TransNet Planning of a hiT 7300 network is done by the Coriant TransNet tool. Coriant TransNet
is a sophisticated software simulation tool developed specifically for designing and/or
upgrading optical DWDM networks with hiT 7300. It runs on PCs using Microsoft
Windows operating systems.
Trail Trace Identifier TTI is a transponder card parameter (configurable via Element Manager) of which is
(TTI) used to verify correct cabling or correct Tandem Connection Monitoring (TCM) configu-
ration. The basic principle is that specific overhead bytes are reserved for Trace
Messages of the user's choosing. By specifying the Actually Sent (transmitted) and the
Expected (received) trace messages, the system can automatically verify that fiber con-
nections have been made as intended. This is accomplished by comparing the expected
Trace Message to that actually received. If they differ, an alarm is raised, alerting per-
sonnel of the incorrect connections.
Transponder card A transponder card receives an optical input signal and converts it to an optical output
signal suitable for DWDM multiplexing and transmission.
Transponder Loopbacks are diagnostic tests that can be activated via Element Manager. Loopbacks
loopback return the transmitted signal back to the sending device after the signal has passed
across a particular link. The returned signal can then be compared to the transmitted
one. Any discrepancy between the transmitted and the returned signal helps to trace
faults.
User Datagram Is one of the core members of the Internet protocol suite (the set of network protocols
Protocol (UDP) used for the Internet). With UDP, computer applications can send messages, in this
case referred to as datagrams, to other hosts on an Internet Protocol (IP) network
without prior communications to set up special transmission channels or data paths.

Glossary
UDP uses a simple transmission model with a minimum of protocol mechanism. It has
no handshaking dialogues, and thus exposes any unreliability of the underlying network
protocol to the user's program. As this is normally IP over unreliable media, there is no
guarantee of delivery, ordering or duplicate protection. UDP provides checksums for
data integrity, and port numbers for addressing different functions at the source and des-
tination of the datagram.
Ultra Long Haul hiT 7300 ULH segment is a DWDM application characterized by long path lengths of up
(ULH) to 1600 km.
User-to-Network Is a demarcation point between the responsibility of the service provider and the respon-
Interface (UNI) sibility of the subscriber. This is distinct from a Network to Network Interface (NNI) that
defines a similar interface between provider networks.
Universal Network Universal Network Objects are software NEs that can be configured and used to repre-
Object (UNO) sent network elements which are not supported by TNMS. UNO also supports devices
with restricted functionalities, for example, without supervising interfaces.
They are also used to represent network services between third parties and TNMS net-
works.
Virtual Local Area In computer networking, a single layer-2 network may be partitioned to create multiple
Networks (VLAN) distinct broadcast domains, which are mutually isolated so that packets can only pass
between them via one or more routers; such a domain is referred to as a Virtual Local
Area Network, Virtual LAN or VLAN.
Wavelength Wavelength is a physical attribute of a wave (for example, an optical wave), defined as
the distance between corresponding points of two consecutive wave cycles.
The wavelength is directly related to the frequency of the wave.
Wait to restore time The time in minutes that TNMS waits until it tries to switch to the working path again,
(WTR) assuming the Revertive option is selected.
workload Model Representation of the typical load to be processed by the system.
eXtensible Markup Is a markup language that defines a set of rules for encoding documents in a format that
Language (XML) is both human-readable and machine-readable. The design goals of XML emphasize
simplicity, generality, and usability over the Internet. It is a textual data format with strong
support via Unicode for the languages of the world. Although the design of XML focuses
on documents, it is widely used for the representation of arbitrary data structures, for
example in web services.

Index
A
Alarm logs 35
B
Backup logs 38
C
Customer Release Notes 43
E
EM/NE management 14
F
Fault 13
analysis 13
G
GCT 28
GUI Cut-Through 28
GUI messages 40
L
List of Generic Faults 43
Log management 27
Logging 13
system event 13
table structure 13
O
Operator hints 43
Oracle 41
S
SCS 34
System Control and Supervision 34
T
Topology management 16
Tracing 39
level definition 39
U
User and security management 25
A50023-K4045-X060-01-7673 67
68 A50023-K4045-X060-01-7673
A50023-K4045-X060-01-7673 69
70 A50023-K4045-X060-01-7673

TNMS-V15 Troubleshooting Manual

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

TNMS-V15 Troubleshooting Manual

Uploaded by

Copyright:

Available Formats

TNMS NCT

Coriant TNMS NCT

Issue: 1 Issue date: November 2015

Coriant is continually striving to reduce the adverse environmental

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

1.1 Intended audience

1.2 Structure of this document

Chapter Title Subject

Table 1 Structure of the manual

1.3 Symbols and conventions

f DANGER! A safety message indicates a dangerous situation where

w NOTICE: A property damage message indicates a hazard that may result

g A note provides important information related to the topic, for

t A tip provides additional information related to the topic which is

Table 2 List of symbols and conventions

Table 2 List of symbols and conventions (Cont.)

1.4 TNMS NCT documentation set

1.5 Other documents

1.6 History of changes

Issue Issue date Remarks

Table 3 History of changes

2.1 Fault analysis overview

2.2.1 System event logs

2.2.1.1 EM/NE management

Severity Affected Description General Troubleshooting information

Table 4 System event log (SEL) entries generated by EM/NE management

Severity Affected Description General Troubleshooting information

2.2.1.2 Topology management

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

Severity Affected Description General Troubleshooting information

Table 5 SEL entries generated by Topo (Cont.)

2.2.1.3 User and security management

Severity Affected Description General Troubleshooting information

Table 6 SEL entries generated by USM

2.2.1.4 Fault management

Severity Affected Description General Troubleshooting information

Table 7 SEL entries generated by Fault

2.2.1.5 Log management

Severity Affected Description General Troubleshooting information

Table 8 SEL entries generated by Log

2.2.1.6 GUI Cut-Through

Severity Affected Description General Troubleshooting information

4. GCT Windows 3. and 4. Reinstall the

Table 9 SEL entries generated by GCT

Severity Affected Description General Troubleshooting information

Table 9 SEL entries generated by GCT (Cont.)

Severity Affected Description General Troubleshooting information