04 Tr3272eu00tr 0401 Operating Term

Operating terminal: advanced topics Siemens
Operating terminal: advanced topics
Contents
1 General features 3
1.1 Introduction 4
1.2 Network architecture 8
1.3 System architecture 10
2 Administration 15
2.1 Security management 16
2.2 DCN management 26
3 Installation of TNMS CT 37
3.1 Before you begin 38
3.2 Installing TNMS CT software 44
3.3 De-installation of TNMS CT 72
3.4 PPP dial-up setup for Q3 network elements 81
4 Exercises 97
5 Solution 105
TR3272EU00TR_0401
1
© 2005 Siemens AG
Siemens Operating terminal: advanced topics
2 TR3272EU00TR_0401
© 2005 Siemens AG
1 General features
Fig. 1
TR3272EU00TR_0401
3
© 2005 Siemens AG
1.1 Introduction
TNMS CT is a common platform solution for different Network Element (NE) types.
This management system basically consists of a PC hardware (standard PC) and an
Operation, Administration and Maintenance (OAM) PC software, which provides a
high performance supervision and control tool using the internal supervision and
control software implemented in the Network Elements. TNMS CT is a transparent
software platform for SDH and WDM network elements using QD2, QST, Q3 or
SNMP telegram protocols. TNMS CT provides access to network elements via a
network interface (Ethernet) or via a serial line interface (RS232).
TNMS CT allows local as well as remote operation and control. It is possible to open
more than one NE application at the same time. This way there is the additional
possibility to have a graphical network view, concerning fault detection and network
management.
The TNMS CT menu items and dialogues allow the supported communication
channels to be set up. The network element to be operated is selected by a simple
procedure, adapted to the requirements of the connected communication channel.
TNMS CT enables addresses to be assigned to the network elements. The program
icons for these applications are used to present the assigned network elements in the
network view.
4 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT (Craft Terminal)

TNMS CT
Remote
Server
client
WAN / Internet
WAN / Internet
Remote TNMS CT
client Server
LAN
LCT
hiT 7500
LCT
hiT 7070 hiT 7070
STM-16 STM-16
BSHR/4 BSHR/4
hiT 7050 hiT 7050
hiT 7070 MSP 1+1 hiT 7070

MSP 1+1
Fig. 2 TNMS CT (Craft Terminal)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
5
© 2005 Siemens AG
1.1.1 LCT and NCT modes

Depending on the needs, two different modes are available for TNMS CT.
LCT Mode:
The Local Craft Terminal (LCT) is used for local management and commissioning of
network elements. The MSN Manager, organizational relationships between network
elements in the network and network alarms are not available for the LCT. The LCT
can communicate with a maximum of 150 network elements. Via Q-interface up to
three element managers may be open at the same time only.
NCT Mode:
The Network Craft Terminal (NCT) is used for local or remote management of
network elements. In addition to the LCT functions, the monitoring of all the alarms
reported from each accessible network element is allowed. The NCT can
communicate with a maximum of 150 network elements (including alarm monitoring).
Up to 50 element managers or up to five MSN Managers may be open at the same
time only.
6 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT: Client/server architecture

TNMS CT
Remote
TNMS CT Client & Server Server
client
components
TNMS CT Client
component WAN / Internet
WAN / Internet
Local TNMS CT
client Server
TNMS CT Server
component
LAN
hiT 7500
hiT 7070 hiT 7070
STM-16 STM-16
BSHR/4 BSHR/4
hiT 7050 hiT 7050
hiT 7070 MSP 1+1 hiT 7070

MSP 1+1
Fig. 3 TNMS CT: Client/Server architecture
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
7
© 2005 Siemens AG
1.2 Network architecture

The diagram below shows the general structure of a transmission network managed
by TNMS CT.
The network elements (NE's) provide various management interfaces. They can be
connected via the DCN to the management system in several ways.
Telegram Protocols
TNMS CT supports the following telegram protocols to communicate with NEs:
QD2; e.g. SMA 1/4, SMA1K
QST; e.g. SMA16, SL16, SL64
QSTV2; e.g. hiT 7070, hiT 7050
Q3; e.g. hiT75xx
SNMP; e.g. FSP series equipment
TNMS CT is capable of using these protocols simultaneously.
Element management functions are executed via the element managers (LCT's,
MSN manager) provided by the TNMS CT system. TNMS CT can support line, star,
ring and mesh networks comprising of WDM, SDH and network elements and Multi
NE devices.
WARNING
Some NEs, such as QST and QD2 NEs, allow the connection to several
management system levels. If a management system like TNMS Core enforces write
access on a network element, it will override the TNMS CT write access.
8 TR3272EU00TR_0401
© 2005 Siemens AG
Network architecture
TNMS CT
Integrated element managers
(EMs) and MSN manager
Management
interfaces
MSN MSN
SMA1/4, SMA4/1, SMA1K, SMA1K-CP,

DCN
SMA16, SMA16/4, SL16, SLR16, SL64,

QB3M
MTS, WL, WLS, OCU, WTTR, hiT 7070,
hiT 7050, hiT 75xx
SNMP FSP
QF Local connection to Q3, QD2

and QST network elements
Fig. 4 Network architecture
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
9
© 2005 Siemens AG
1.3 System architecture

TNMS CT is a scalable single-user system with a client/server architecture
comprising several industry standard PCs with the Windows 2000 operating system
and various software applications. External devices such as printers, tape units and
remote clients are not dealt with here.
1.3.1 Hardware components

The table below provides an overview of hardware recommendations for TNMS CT
installations. However other configurations are possible, depending on the network
size. Planning for hardware, software and licenses should be undertaken on a
project-specific basis.
HARDWARE RECOMENDATIONS
CPU Pentium IV 3 GHz
Memory 1 GB
Hard Disk 80 GB
LAN Ethernet card 2x 3COM (3C982-TXM)
Monitor 17" Color Monitor
Operating System Windows 2000 Professional or Microsoft
Windows XP Professional
TIP
A more detailed hardware list is given in the installation section of this training
manual.
10 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT: System architecture
"
17
Standard
IBM Compatible PC
TNMS CT - Software
Windows 2000 Professional
Ethernet Ethernet
Adapter N1 Memory CPU Hard Disk Adapter N2
Fig. 5 TNMS CT: System architecture
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
11
© 2005 Siemens AG
1.3.2 Software components

The TNMS CT software comprises of a Client and a Server component. The Client
component provides a network management user interface. Via this GUI all TNMS
CT management functions, e.g. invoking of element managers, are available. The
Server component holds the EML packages and the NetServer frame, which provides
the environment for running EML servers, DCN connectors and NE controllers.
Element Manager:
In order to obtain detailed information about an NE, the operator can open the
element manager application associated with the corresponding network element.
TNMS CT starts the corresponding process and provides the interface of the
associated NE controller to the element manager. Element manager applications
provide full access to all NE data and also enable the configuration and control of NE
behavior. This way, depending on the actual NE type, performance values and
alarms can be requested, and the backup and restore of configuration and other data
initiated.
NetServer Frame:
The NetServer frame is essentially a proxy for the TNMS CT Server. It facilitates the
management of EML packages.
EML Packages:
A EML package is an installation package, which contain all relevant components
(e.g. the NE controller) needed to run a family of NEs within TNMS CT. The
combination of EML packages required for a given TNMS CT system depends on the
NE types that TNMS system configuration is required to support.
NE Controllers:
The main task of an NE controller is to convert NE-specific management interfaces to
a simple internal TNMS CT element management interface. In this way, network
layer management in the TNMS CT Server only receives the necessary information
from the element management layer. A corresponding NE controller must be
registered in the system for every NE type to be managed by TNMS CT. Each NE
controller class can support different NE types, but each NE can only be controlled by
one type of NE controller.
TIP
All software components can be installed on one PC.
12 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT: Software components

TNMS CT Client Components
Element
Element Import/Export
Element
Manager
Manager ... MSN
Files as
Manager Manager
Export *.xml
Files as
TNMS CT Frame
*.sdf
Network Management User Interface
TNMS CT Server Components

TNMS CT Netserver Frame
EML Package
NE
NE
... EML Package
NE
NE
Controller
Controller Controller
Controller
D C N
...
Network Elements
Fig. 6 TNMS CT: Software components
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
13
© 2005 Siemens AG
14 TR3272EU00TR_0401
© 2005 Siemens AG
2 Administration
TBD
Pas
sw
or d
Us
er
ID
Us
er
Cla
ss
Fig. 7
TR3272EU00TR_0401
15
© 2005 Siemens AG
2.1 Security management

To protect against any unauthorized access or incorrect inputs by an operator,
management systems are in place for checking the user's access level and
authorization.
Each user has to be assigned to one user class. Functions that are not allocated to a
specific user class won't be accessible to the operator belonging to that class.
TNMS CT supports 5 different User Classes
The 5 classes are:
• Class 0: Supervision
• Class1: Maintenance
• Class2: Operation
• Class3: Configuration
• Class4: Administrator
A full list of User class definitions is given on the next page.
WARNING
Although users can be assigned different User Classes using the User
Administration window; the function (definition) to any given User Class
cannot be changed.
16 TR3272EU00TR_0401
© 2005 Siemens AG
Function 0 - Supervision 1 - Maintenance 2 - Operation 3- Configuration 4 - Administrator

Assignment to Q3 classes no access to EM 5 8 9 10
Start EM in offline mode access access access access access
Start EM no access read-only access access access
Connect/disconnect NEs no access no access access access access
File transfer no access no access access access access
XML import/export no access no access no access no access access
Access to DCN Management read-only read-only read-only access access
Activate Server access access access access access
Deactivate Server no access no access no access access access
Activate/deactivate selected DCN objects no access no access no access access access
Create/duplicate NEs no access no access no access access access
Edit NE address no access no access no access access access
Delete NE no access no access no access access access
Print/save access access access access access
Print/save DCN information no access no access access access access
Background no access access access access access
Settings (alarm, performance, general) no access read-only read-only access access
Alarm list, alarm log access access access access access
Alarm acknowledgement no access access access access access
Access control (release/request write access) no access no access no access access access
Localize NE access access access access access
Filter access access access access access
Toggle filter settings no access no access no access access access
Column settings no access access access access access
Clear/resize/request list/log data no access no access no access access access
Link window no access access access access access
Create/delete port connection read-only read-only read-only access access
Trace windows no access no access read-only access access
System Message Log access access access access access
Performance management no access no access access access access
Backup settings no access no access no access access access
Backup browser no access no access no access access access
Security log no access no access no access no access access
Advisory message window no access no access no access access access
Archive logs (except for Security Archive Log) no access no access access access access
Security Archive Log no access no access no access no access access
Change password access access access access access
Broadcast NE user configuration no access no access no access no access access
User administration no access no access no access no access access
Fig. 8 TNMS CT User Classes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
17
© 2005 Siemens AG
2.1.1 User administration

The User administration window allows the "Administrator" to manage the users of
the TNMS CT system. The window shows a scroll list of all users present in the
database and allows to:
• Add a new user account
• View the properties of a user account
• Edit an existing user account
• Delete a user account previously selected in the user list
2.1.1.1 Add a new user account

Function: User Administration. Add a new user.
Step Name of the Window Used Menu or Command Remarks
1 "TNMS CT Main" From the main menu bar select "User
window. (LMB) "Security" and from pop- Administration"
up menu choose "User window is
Administration..." . opened.
2 "User Administration" Click "Add" button. "Edit User"
window. window is
opened.
3 "Edit User" window. Type in the user "Name". Select
the required "User Class" and
insert the valid "Password".
Select additional properties as
required.
4 "Edit User" window. Click "OK" button.
About passwords
The following rules for passwords apply:
Choose a password with at least six characters:
At least two of them have to be alphabetic.
At least one character has to be numeric.
At least one character has to be a special one, but #, $, *, /, @ are not allowed.
Do not use your user ID as password.
Do not use a previously used password.
18 TR3272EU00TR_0401
© 2005 Siemens AG
2 1
4
Fig. 9 Add a new user
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
19
© 2005 Siemens AG
2.1.1.2 View/edit the properties of a user account
Function: User Administration. View/edit properties.

2 "User Administration" Select user account from the list.
window.
3 "User Administration" Click "Properties" button. "Edit User"
window. window is
opened.
4 "Edit User" window. Change the required "User
Class" and insert a valid
"Password". Select additional
properties as required.
5 "Edit User" window. Click "OK" button.
2.1.1.3 Delete a user account
Function: User Administration. Delete a user.

2 "User Administration" Select user account from the list.
window.
3 "User Administration" Click "Delete" button.
window.
20 TR3272EU00TR_0401
© 2005 Siemens AG
3 1
2 5
Fig. 10 View/edit the properties of a user account
3 1
Fig. 11 Delete a user account
TR3272EU00TR_0401
21
© 2005 Siemens AG
2.1.1.4 Change password

The user can change own password. "Change Password" window can be invoked
from "Security -> Password..." menu.
TIP
The new password must differ by at least 3 characters from the previous password.
2.1.1.5 Security settings

Users assigned to user classes "Administrator" or "Configuration" may configure
global security settings. "Security Settings" window can be invoked from "Security -
> Settings..." menu.
The following settings can be done:
Global Security Settings
• Initial Password Change Interval
Define a time limit for changing a new assigned password for the first time from 1
to 30 days. The default value is 14 days.
• Inactivity Time-out
Define a time limit to log out the operator after inactivity from 1 to 999 minutes.
Use 0 to disable this function. The default value is 60 minutes.
Startup
• Display advisory message text during application startup
Check this option to display a message at login, which the operator has to confirm.
Enter the message in the field below.
22 TR3272EU00TR_0401
© 2005 Siemens AG
Fig. 12 Change Password
Fig. 13 Security settings
TR3272EU00TR_0401
23
© 2005 Siemens AG
2.1.1.6 NE user configuration

TNMS CT supports the NE user configuration (create, modify, delete) for a group of
NEs.
This Function is supported over the menu bar "Tools -> NE User Configuration..."
and is only reachable for the user class administrator.
TIP
The Broadcast User Configuration is only supported for Q3 NEs (e.g. SURPASS hiT
75xx).
24 TR3272EU00TR_0401
© 2005 Siemens AG
Fig. 14 NE User configuration
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
25
© 2005 Siemens AG
2.2 DCN management

The DCN Management covers the definition and administration of DCN channels and
network elements in a similar manner. The administration can be done without having
the corresponding components activated. The DCN connection to the network
elements is administered in the DCN Management window.
The managed DCN objects (DCN channels and network elements) are in a
hierarchical relation and are displayed in a tree. Elements can be added, deleted and
modified.
The current connection state is also displayed in the DCN Management tree.
The user can open the window via the main menu "Configuration -> DCN
Management…" or via a corresponding toolbar button "DCN Mgmt" in the main
toolbar.
26 TR3272EU00TR_0401
© 2005 Siemens AG
Fig. 15 DCN management
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
27
© 2005 Siemens AG
2.2.1 DCN management view

The DCN Management tree consists of the following objects in hierarchical order:
• Server.
• DCN Channel.
• Multi NE.
• NE.
In the DCN Management tree, there are two Server nodes available:
• Serial Line Server contains pre-configured DCN channels and network elements
for local connections via RS232.
• TNMS CT Server allows configuring DCN channels and network elements for local
and remote connections via Ethernet/DCC.
The managed DCN objects are displayed in their current connection state and
hierarchical relation in a tree.
Server nodes
The Server nodes provides for the following functions:
• Handling the connection to one or more different network element(s).
• Direct source for all NE data to be uploaded by the TNMS CT Server.
• Loading the NE data required by the TNMS CT Server and maintaining data
consistency while the Server is connected to the NE.
• Acting as a mediation device by standardizing the data transferred from the
different NE interfaces to the TNMS CT Server and vice versa.
• Activating or deactivating all subordinated objects at once.
28 TR3272EU00TR_0401
© 2005 Siemens AG
Fig. 16 DCN management view
DCN Channel
The DCN channel nodes provide the following functions:
• Handling the connection to one or more different NE's of the same DCN channel
type.
• Activating or deactivating all subordinated objects at once.
Network Element
The NE nodes provide the following functions:
• Handling the connection to one network element.
• Activating or deactivating a network element. When an NE node has been
activated, a corresponding NE symbol is displayed on the network map.
TR3272EU00TR_0401
29
© 2005 Siemens AG
2.2.2 Display of DCN object states

Each DCN object displays its own DCN object state. If a DCN object is a parent of
other DCN objects the parent object does not represent a "cumulated" state of its
children!
The following DCN object states are displayed in the tree view by their corresponding
icon.
Icon State Description

deactivated DCN object is deactivated (configuration state), i.e. the object is not in use
by the system (means also that no connection will be established to this
object)
deactivating Instances of objects corresponding to the resp. DCN object are being
destroyed (e.g. if a NE is deactivated the corresponding NE Controller
instance is destroyed)
activating Instances of objects corresponding to the resp. DCN object are being
created (e.g. if a DCN channel is activated the corresponding EML Server
is created).
disconnected DCN object is in use by the system but there is no connection established
to this object (e.g. after "disconnect" or "activate" command by the
operator).
connecting System is establishing a connection to the DCN object
connected Connection to the DCN object is successfully established
starting up DCN object is initializing its data
running DCN object has successfully finished its initialization and is ready for
operation
init failed DCN object has not successfully finished its initialization and is inoperable;
only reinitialize is available via TNMS Client
shutting down DCN object is saving its data and is releasing its subcomponents
disconnecting System is closing the connection to the DCN object
connection failure Connection to the DCN object has been lost (in contrary to "disconnected"
initiated by the operator) or connection cannot be established
invalid properties At least one property of the DCN object is invalid (DCN object cannot be
used) The operator has to complete or correct the properties
correspondingly
Fig. 17 Icons used in the DCN management view
30 TR3272EU00TR_0401
© 2005 Siemens AG
2.2.3 Working with DCN objects
2.2.3.1 DCN object properties

To view or modify the properties of a DCN object there is a property dialog with the
corresponding property pages.
The operator must assign for each DCN object a unique name (field "ID Name" of the
DCN object's general property page).
The property window of the different DCN Objects are reachable over their context
menus or over double click on an DCN Object entry of the DCN Management
window.
Example of
Properties window of
the NE
Example of
Properties window of
the DCN channel
Fig. 18 DCN object properties
TR3272EU00TR_0401
31
© 2005 Siemens AG
2.2.3.2 Activating / deactivating DCN object

There is a checkbox for each item to activate / deactivate the object. This checkbox
has a double meaning:
• Generally: by selecting a DCN object's checkbox (or by applying "Activate" from
the DCN object's context menu) the operator determines, that a connection to this
DCN object shall be established. In this sense the checkbox represents a
configuration state (the target).
• The actual initiation for establishing this connection depends on the configuration
state (checkbox state) and additionally on the state of the DCN object's parent (in
case of NE: the DCN channel).
• If the parent object's checkbox is selected too and the parent object is in state
"running", selecting the checkbox of the child DCN object immediately initiates the
establishing of the connection to this DCN object and to all of its children whose
checkbox is selected too. In this sense the checkbox likewise initiates an
operation.
• For being used by the system (i.e. a connection to the DCN object will be
established) a DCN object has to be activated by the operator by selecting the
corresponding item's checkbox in the DCN tree or by selecting the menu item
"Activate" in the item's context menu.
In order to deactivate a DCN object, the operator deselects the corresponding item's
checkbox in the DCN tree or selects the menu item "Deactivate" in the item's context
menu. Deactivating implicitly closes a possibly existing DCN connection to the DCN
object. Children of a deactivated DCN object will be deactivated too. However, the
children's' checkbox representing the configuration state (target) will remain selected
(marked for next time activation).
32 TR3272EU00TR_0401
© 2005 Siemens AG
Check boxes
are selected
Fig. 19 Activated DCN objects
Check box of
DCN channel
is deselected
NE’s are
deactivated
Fig. 20 Deactivated DCN objects
TR3272EU00TR_0401
33
© 2005 Siemens AG
2.2.3.3 Adding a new DCN object

Adding a new DCN element is only possible in its parent object’s context:
DCN channel can be created in the context of the appropriate Server node and a NE
in the context of the appropriate DCN channel.
The property dialog of the DCN object opens automatically and the user has to check
and complete all mandatory properties. The operator must assign for each DCN
object a unique name (field "ID Name" of the related DCN object's general property
page).
1. Add a DCN Channel
A new DCN channel can be created in the context of a Server node . The user has to
choose the type of DCN from a list of available types. After that an empty property
page opens where the operator has to enter the properties for the new DCN Channel.
2. Add a NE
A new NE can be created in the context of a DCN channel. The user has to choose
the type of NE from a list of NE types available for the related DCN channel. An
empty property page opens where the operator has to enter the properties for the
new NE.
To create a DCN object e.g. new NE for your network, complete the following steps:
Function: DCN Management. Create a New DCN Object.

1 "DCN Management" Select (RMB) the parent DCN "Add Network
window. object (e.g. DCN channel) where Element"
the new child object to be added. window is
From the Pull Down menu select opened.
(LMB) "Add...".
2 "Add Network Select the type of NE to be added NE "Properties"
Element" window and press "OK" button. window is
opened.
3 "Properties" window. Complete the required information In "QST" Tab
in all tabs and click "Apply" enter either a 20
button. digit NSAP Addr.
or an IP Addr. in
"dotted decimal
format"
4 "DCN Management" Tick the check-box next to the
window. newly created object to activate it
34 TR3272EU00TR_0401
© 2005 Siemens AG
Or enter IP Addr.
e.g.: 172.16.3.1
3
Fig. 21 Create a new DCN object
The QB3 DCN channel supports several types of NE controllers:

Specific NE Controllers, e.g. hiT7070 3.0, are used to fully manage a network
element. The type supported by the controller must match the type of the NE. It
can be used in NCT mode only.
Default NE Controllers, e.g. Default Q3, can be used to automatically detect the
type of a network element and switch to the appropriate specific controller. The
telegram protocol supported by the default controller must match the telegram
protocol of the NE. It can be used in NCT mode only.
Universal NE Controllers, e.g. Universal MSI QST NE, are used to manage a
network element without alarm information, but with faster start-up. The telegram
protocol supported by the universal controller must match the telegram protocol of
the NE. It is used for all connections in LCT mode and for serial line connections in
NCT mode.
TR3272EU00TR_0401
35
© 2005 Siemens AG
2.2.3.4 Deleting a DCN object

The user can delete a DCN object by using the context menu, the respective button
of the DCN Management window’s toolbar or by pressing the delete key of the
keyboard. The user has to confirm the operation before the deletion takes place.
Deletion is only possible when the DCN object is deactivated.
The DCN object is not needed in the network layer. I.e. a NE must not have any port
connections, and DCN Channel must not have any NEs.
Fig. 22 Deleting a DCN object
36 TR3272EU00TR_0401
© 2005 Siemens AG
3 Installation of TNMS CT
NE
NE
NE TNMS CT
Fig. 23
TR3272EU00TR_0401
37
© 2005 Siemens AG
3.1 Before you begin

The TNMS CT software includes a number of applications and feature components. It
is supplied on CD-ROM, which includes a convenient master installation program for:
• Installing the TNMS CT software components on the user’s hard disk,
• Modifying an existing installation by adding or removing selected components or
subcomponents,
• Removing the TNMS CT software completely from the user’s hard disk.
WARNING
In order to use the TNMS CT software, the import of corresponding license
keys is required. Depending on functionality, the TNMS software is divided into
several software packages, which are provided on a separate CD-ROM with
individual licenses.
TIP
The TNMS CT software supports subsequent integration of new network elements or
new network element versions. The software components for managing a new
network element or a new network element version are provided with a TNMS CT
upgrade installation package on a separate CD. Using this package, a TNMS CT
system can be upgraded with the element management components required for the
new network element or network element version.
3.1.1 Installation software

WARNING
All software parts mentioned below must be released for the appropriate TNMS
software version. This holds for the initial installation and for service or
upgrade package installations as well.
WARNING
If additional software is installed which is not required for TNMS CT, correct
functionality of TNMS CT cannot be guaranteed.
38 TR3272EU00TR_0401
© 2005 Siemens AG
File with TNMS CT SW includes :

license keys Server and Client components;
Windows 2000 Professional Internet Explorer EML packages;
incl. Service Pack 4 6.0 SP 1 JAVA Runtime Environment;
or OSI stack;
Windows XP Professional Acrobat Reader 5.0.
incl. Service Pack 2
Fig. 24
The following software is generally required for the installation. The corresponding
CD order numbers are provided in the TNMS CT release documentation.
1. Windows 2000 Professional incl. Service Pack 4: The Windows 2000

Professional operating system is required for the Client and Server machines.
The Installation instructions for the operating system is provided in TNMS CT
User Manual, however, pre-installed machines can also be used.
2. Internet Explorer 6.0 SP 1: The Internet Explorer must be installed on the Server
to enable MSN functionality, and on the client machine. If this is not already pre-
installed, it can be downloaded from the Internet.
3. TNMS CT SW. This installation program contains the following software
components for installation:
Integrated TNMS CT software installation package includes the Server and Client
components. These can be installed either individually or together as required.
The EML packages for QB3M, FSP (via an additional CD) and MSN. The EML
packages are installed on the Server PC.
Additionally to the TNMS CT installation, the following 3rd-party software components
are also included on this CD:
• JavaSoft JAVA Runtime Environment: The JRE is installed on the client machine
to provide an environment for the Java based applications.
• OSI stack: The OSI stack software must be installed on Server PC before the
Server software itself.
• Acrobat Reader 5.0: Acrobat Reader is required for using the User Manual, which
is delivered as PDF.
TR3272EU00TR_0401
39
© 2005 Siemens AG
3.1.2 Hardware requirements

The TNMS CT is installed on a IBM compatible PC. The following table lists an
example configuration for that PC.
Example Configuration:
TNMS CT V3.0: TNMS CT V3.0:

Notebook PC (Recommended Mini-tower PC
HW for LCT Mode) (Recommended HW for
NCT Mode)
Processor Pentium 4 1,6 GHz Pentium 4 3 GHz
RAM 512 MB 1 GB
Hard disk 40 GB E-Series 80 GB Ultra DMA-100
Floppy disk drive 3.5" / 1.44 MB 3.5" / 1.44 MB
CD ROM 24x E-Series 48x ATAPI
Graphics ATI Mobility-Radeon 7500 with Matrox Millenium G450
32 MB Video RAM 32 MB, DH/DVI
GUI LCD 14.1” TFT XGA 21T3
Interfaces card for Modem /LAN E-Series LAN RJ-45
Remote access
Interfaces card for V24/RS232 V24/RS232
local access
Pointer device Microsoft serial mouse or Microsoft serial mouse or
compatible compatible
A printer can be connected to the PC via the parallel interface for documentation.
TIP
Siemens releases the TNMS CT software only for the official TNMS CT hardware
supplied. Due to the rapid changes of PC hardware an equal or better follow up
model may be delivered.
40 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT
NCT
TNMS CT
LCT
Processor: Pentium 4 3 GHz
RAM: 1 GB
Hard disk: 80 GB Ultra DMA-100
Processor: Pentium 4 1,6 GHz Floppy disk drive: 3.5" / 1.44 MB
RAM: 512 MB CD ROM: 48x ATAPI
Hard disk: 40 GB Graphics: Matrox Millenium
Floppy disk drive: 3.5" / 1.44 MB G450 32 MB, DH/DVI
CD ROM: 24x E-Series GUI: 21T3
Graphics: ATI Mobility-Radeon LAN Card: LAN RJ-45
7500 with 32 MB RAM Local Access V24/RS232
GUI: LCD 14.1” TFT XGA Pointer Device Microsoft serial
LAN Card: Modem /LAN E-Series mouse or compatible
Local Access V24/RS232
Pointer Device Microsoft serial
mouse or compatible
Fig. 25 HW configuration example
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
41
© 2005 Siemens AG
3.1.3 Preparation for installation

Prior to installing TNMS CT check the following to ensure that all requirements are
met:
Component Delivery
Before installation, ensure that:
• The delivery is complete in accordance with the delivery units specified in the
delivery note (hardware, software and documentation).
• The components are not damaged in any way.
Installation and Cabling

Before installing the operating system, the following steps should be completed:
• The Client and Server PCs should be set up and cabled in accordance with the
project-specific installation documents supplied.
• The applicable recommendations for screen-based workstations should be
observed.
• To guarantee 24-hour operation, an uninterrupted power supply must be available.
42 TR3272EU00TR_0401
© 2005 Siemens AG
Preparation for Installation

done
Component Delivery
Hardware Recommendations
Installation and Cabling
Installation Software
Fig. 26 Preparation for Installation
TR3272EU00TR_0401
43
© 2005 Siemens AG
3.2 Installing TNMS CT software

3.2.1 Installation sequence
The system should be commissioned as follows:
1. Install the operating system and additional hardware components, and configure
the system under Windows 2000 Professional or Windows XP Professional.
2. Install Microsoft Internet Explorer.
3. Install JavaSoft Runtime Environment.
4. Install the OSI stack on the Server PC.
5. Install Adobe Acrobat Reader.
6. Install the TNMS CT software components on the corresponding machines:
TNMS CT Client;
TNMS CT Server;
7. Additional TNMS software, such as optional EML packages.
8. Configure the TNMS CT components and connect network elements.
9. Perform system testing in accordance with the test cases described in the
acceptance test protocol.
TIP
Before install any software component, have a look at the associated "readme" file.
Here you can find the latest information concerning installation.
WARNING
The displayed screenshots within this manual are examples only and the
contents may differ depending from the actual situation.
TIP
For more information, contact Siemens Technical Sales.
44 TR3272EU00TR_0401
© 2005 Siemens AG
TNMS CT: SW installation sequence
WIN 2000 Windows XP Operation

Operation System
System
1
& & and
and Internet
Internet Browser
Browser
Service pack 4 Service pack 2
or
Internet
Explorer 6.0
2
3 Prerequisits
Prerequisits
JavaSoft
4 TNMS
TNMS CT
CT Software
Software
OSI
STACK 6
7
Adobe 5
Acrobat Reader 8
TNMS CT
9
Fig. 27 TNMS CT: SW installation sequence
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TR3272EU00TR_0401
45
© 2005 Siemens AG
3.2.2 Installing Windows OS and service packs

The Windows 2000 Professional or the Windows XP installations are supported by an
installation wizard, which will guide you through the installation process. Detailed
information on how to install the OS is provided in the Microsoft Windows
documentation delivered with the Windows OS installation CD-ROM.
After the operating system is installed, the corresponding Service Pack must be
installed also:
• Windows 2000 Professional Service Pack 4 (SP4), or
• Windows XP Service Pack 2 (SP2)
TIP
It is recommended, to install the available security patches as well.
TIP
The more detailed information about installation sequence for all software parts is
described in the TNMS CT User Manual.
46 TR3272EU00TR_0401
© 2005 Siemens AG
3.2.3 Installation of the Microsoft Internet Explorer

To install the Internet Explorer, double-click on the executable file containing in the
directory with Internet Explorer SW. An installation wizard will guide you through the
installation process.
For further installation information consult the Microsoft Internet Explorer
documentation.
3.2.4 Installation of JavaSoft JAVA runtime environment

To install Java Runtime Environment, double-click the executable file in the JRE
directory on the TNMS CT V3.0 software CD. An installation wizard will guide you
through the installation process.
During the installation, you will be asked to select a browser. If nothing is selected,
only Java applets designed for the Java Plug-in are executed by the Java Runtime
Environment, all other applets are executed by the browsers internal Java VM. To
have all Java applets to be executed by the Java Runtime Environment, select the
appropriate browser. The necessity to do so depends on the Java applets to be run.
TNMS CT is not affected by this setting.
TIP
For further installation information consult the Sun Microsystems JRE documentation.
TR3272EU00TR_0401
47
© 2005 Siemens AG
3.2.5 Installation of the OSI stack

TIP
During the installation process you will be asked for an NSAP address. Ask your
system administrator how the NSAP address is handled in your company’s network
and have it determined.
To install an OSI stack, proceed as follows:

1. To install an OSI stack, double-click the setup.exe file in the OSI Stack directory
on the TNMS CT V3.0 software CD.
2. A welcome window is now displayed. Press "Next" to continue.
Fig. 28 Setup OSI Stack: Welcome window
48 TR3272EU00TR_0401
© 2005 Siemens AG
3. In the "Choose Destination Location" window, a default installation directory is

offered for the OSI stack. Press "Next" to continue.
Fig. 29 Setup OSI Stack: Choose Destination Location
TR3272EU00TR_0401
49
© 2005 Siemens AG
4. In the "Please select:" window, select the option best suited to your company’s
network.
Fig. 30 Setup OSI Stack: NSAP address
a) "My company has own NSAP management", when your system

administrator can provide you with an NSAP address.
b) "NSAP address should be derived from MAC address of Ethernet card",
when your system administrator cannot provide you with an NSAP address.
c) "I do not have an Ethernet card", to have TNMS CT assigning an NSAP
address.
50 TR3272EU00TR_0401
© 2005 Siemens AG
5. After selection e.g. "My company has own NSAP management" press "Next"
button, the "Getting NSAP" window is opened.
6. Enter the local NSAP address and press "Next" button.
Fig. 31 Setup OSI Stack: Getting NSAP
TR3272EU00TR_0401
51
© 2005 Siemens AG
7. In the "Start Copying Files" window ensure that the settings displayed are
correct, and if so, press "Next" to continue.
Fig. 32 Setup OSI Stack: Start Copying Files
52 TR3272EU00TR_0401
© 2005 Siemens AG
8. A "Setup Status" window is now displayed, showing the progress of the OSI
stack installation.
Fig. 33 Setup OSI Stack: Setup Status
TR3272EU00TR_0401
53
© 2005 Siemens AG
9. The window "InstallShield Wizard Complete" is now shown. Select the option
for restarting the computer, and press "Finish" to complete the OSI stack
installation.
Fig. 34 Setup OSI Stack: InstallShield Wizard Complete
54 TR3272EU00TR_0401
© 2005 Siemens AG
10. Once the computer has rebooted, open the OSI stack via "Start -> Settings ->
Control Panel -> OSI Stack".
a <Ctrl> + <I>
Fig. 35 OSI Stack Configuration
WARNING
The settings for the "OSI Stack Configuration" window are specified by the
Network Planning Department. All data in this window should not be changed
after commissioning, unless it is specified in the planning documents. If in
doubt, the default values should be retained.
WARNING
When stack parameters are changed, the stack needs to be stopped and
started manually.
TR3272EU00TR_0401
55
© 2005 Siemens AG
11. You can now check the OSI stack settings as follows:
a) Note the settings of the ES-IS and IS-IS parameters (the IS-IS parameters can
be displayed by pressing "<Ctrl> + <I> ").
b) Set the value for "Number of Channels and Ctx" to greater than/equal to
"140". This is the number of OSI stack connections, which can be established
simultaneously. The recommended value is 500.
c) Note the MAC address of the network interface card to which the OSI is
connected and check this against the LAN card settings in the Control Panel.
d) Activate the options "Open Stack, when Operator starts" and "Start stack
as service".
WARNING
Attention: For connections with the serial line interface without connected LAN
cable, you need to specify the IP loop back address (127.0.0.1) in the OSI Stack
configuration applet.
56 TR3272EU00TR_0401
© 2005 Siemens AG
3.2.6 Installation of the Adobe Acrobat Reader

To install Acrobat Reader, double-click the executable file in the Adobe directory on
the TNMS CT software CD. An installation wizard will guide you through the
TIP
For further installation information consult the Adobe Acrobat Reader documentation.
3.2.7 Installing TNMS CT

1. To install TNMS CT, double-click the setup.exe file in the main directory of the
TNMS CT software CD. A welcome window appears, press "Next" to continue.
Fig. 36 TNMS CT Setup: Welcome window
TR3272EU00TR_0401
57
© 2005 Siemens AG
2. In the "Setup Type" window, select the desired mode, depending on your needs
and licenses. Press "Next" to continue.
Fig. 37 TNMS CT Setup: Setup Type I
Tip
Next step is only performed when NCT has been selected.
58 TR3272EU00TR_0401
© 2005 Siemens AG
3. In the "Setup Type" window, indicate the components you want to install on this
machine. Press "Next" to continue.
Fig. 38 TNMS CT Setup: Setup Type II
TR3272EU00TR_0401
59
© 2005 Siemens AG
4. A notification window is displayed indicating a registration process.
Fig. 39 TNMS CT Setup: Setup Status
60 TR3272EU00TR_0401
© 2005 Siemens AG
5. In the License Agreement window, scroll down to read the complete text. Press
"Yes" to accept the license agreement.
Fig. 40 TNMS CT Setup: License Agreement
TR3272EU00TR_0401
61
© 2005 Siemens AG
6. In the Choose Destination Location window, a default installation directory is

offered. Press "Next" to continue.
Fig. 41 TNMS CT Setup: Choose Destination Location
62 TR3272EU00TR_0401
© 2005 Siemens AG
7. In the "Please choose Net Elements to install" window, select the desired
network elements to be installed, and press "Next" to continue.
Fig. 42 TNMS CT Setup: Choose NetElements to install
TR3272EU00TR_0401
63
© 2005 Siemens AG
8. In the "Start Copying Files" window ensure that the settings displayed are
correct, and if so, press "Next" to continue.
Fig. 43 TNMS CT Setup: Start Copying Files
64 TR3272EU00TR_0401
© 2005 Siemens AG
9. A "Setup Status" window is now displayed, showing the progress of the TNMS
CT installation. Various system messages are also output during this part of the
installation, for example indicating that LCTs are being installed.
This part of the installation may take some time.
TR3272EU00TR_0401
65
© 2005 Siemens AG
10. Once all system components are installed, the "Install Shield Wizard Complete"
window is displayed. Select the option for restarting the computer, and press
"Finish" to complete the installation.
Fig. 45 TNMS CT Setup: InstallShield Wizard Complete
TIP
The computer is rebooted and the installation completed.
66 TR3272EU00TR_0401
© 2005 Siemens AG
3.2.8 Initial configuration of TNMS CT

Once the TNMS CT software has been installed, and the computer restarted, the
TNMS CT system can be configured. The main steps to be completed during
configuration are listed below. Additional information is provided in the online help
under "Initial Configuration. Start TNMS CT".
3.2.8.1 Start TNMS CT

1. Start the TNMS CT interface via "Start -> Programs -> TNMS CT -> CT Client.
Login"
Fig. 46 Start TNMS CT
TR3272EU00TR_0401
67
© 2005 Siemens AG
2. Log on TNMS CT via the displayed login dialogue or by clicking the Login icon in
the TNMS CT toolbar. When starting the TNMS CT application, the Login dialog
is opened automatically.
a) In the field Server, enter the name of the PC where the TNMS CT Server is
installed.
TIP
If you login directly to the PC where the TNMS CT Server is installed, enter
"localhost".
b) In the field User name enter the default value "Administrator". This account
is created automatically during the installation of TNMS CT.
c) When you log on for the first time, the field "Password" is not completed.
Click the "Login" button.
d) Click "OK" to confirm advisory message
e) Change the password for the default administrator account as requested.
b
e
c
Fig. 47 TNMS CT: Initial Login
WARNING
In the training class Lab exercises please use only the following password:
"siemens-00".
68 TR3272EU00TR_0401
© 2005 Siemens AG
3.2.8.2 Import licenses

Before working with TNMS CT, its components have to be licensed. The following
license types are distinguished:
• Basic license;
Each TNMS CT system requires its own license.
• NE license;
Each NEC managed by TNMS CT requires its own license.
• Optional feature license
In case of additionally installed optional features, further licenses are required as
well.
1. In the message box with the request to import the licenses press "OK" button,
follow by an installation wizard open the license XML file and start import of
licenses. Depending on whether SW and/or HW have been pre-installed by
Siemens staff, you have been provided with the necessary license file, or you
have to request it via e-mail.
Fig. 48 TNMS CT: Import Licenses
TR3272EU00TR_0401
69
© 2005 Siemens AG
3.2.8.3 Configure user accounts

A default administrator account is created during installation. Additional accounts can
now be created as required.
TIP
More detailed information about user account management is described in the User
Administration part of this manual or in the TNMS CT User Manual.
3.2.8.4 Define log configuration settings

The available size of the various log files on the hard disk should be determined.
Settings can be entered for the size of the Alarm Log and System Message Log.
All log files are installed in the TNMS installation directory under Logs. On the HD
partition where the TNMS is installed there should be at least 1 GB free disk space
during operation. If the log file size will be changed (expanded) check the necessary
disk space again.
TIP
For more information please refer to the TNMS CT User Manual.
70 TR3272EU00TR_0401
© 2005 Siemens AG
3.2.8.5 Configure and activate DCN channels and network elements

DCN channels and network elements are configured in the DCN Management View.
Select the TNMS CT Server and add the appropriate DCN channels. Once
configured, the channel settings should be checked, e.g. for scheduling
communication. Then network elements can be added to the DCN channels. The
required network element type can be selected from the list. The NE's are configured
by completing each tab page as described in the Online Help.
TIP
If you are use TNMS CT in LCT mode, the field Server will not be active as Client and
Server are always installed on the same machine.
TIP
More detailed information about DCN channels and network elements activation is
described in the DCN Management part of this manual and/or in the TNMS CT User
Manual.
3.2.8.6 Setup the network map

The network map can now be set up using the TNMS CT Network View. This must
be done on the basis of planning data (when installing the system the first time) or by
migration of data used in formerly software versions (in case of software updates).
The Serial Line View allows the establishment of a connection to a single NE using
the Serial Line Interface (F-Interface).
3.2.8.7 Further settings
Further setting can be done depending on the individual customers needs, e.g. color
settings for alarms.
TR3272EU00TR_0401
71
© 2005 Siemens AG
3.3 De-installation of TNMS CT

The TNMS CT software can be de-installed using the Windows 2000 control panel.
The following information is removed during de-installation:
• All information used by the TNMS CT application from the Windows 2000 Registry.
• All program files of the TNMS CT components.
• All empty TNMS CT component directories.
• Shared files such as OLE-Dlls are not removed.
WARNING
The displayed screenshots within this manual are examples only and the
contents may differ depending from the actual situation.
TIP
For more information, contact Siemens Technical Sales.
WARNING
Before uninstalling TNMS CT software, complete the following steps:
1. Export the configuration data to an XML file via File -> Export Configuration.
2. Store the local NSAP address of the Server in a text file.
3. Close all open element managers.
4. Log off the TNMS CT software and exit.
5. Stop the services TNMS CT Server and OSI stack on the Server computer
(optional).
72 TR3272EU00TR_0401
© 2005 Siemens AG
Do not Forget !!!

done
Export the configuration

Data.
Store NSAP Address.
Close element managers.
Log off the TNMS CT
and exit.
Stop TNMS CT and
OSI services.
Fig. 49 Preparing to Uninstall TNMS CT SW
TR3272EU00TR_0401
73
© 2005 Siemens AG
3.3.1 De-installation of TNMS CT component

1. Stop the TNMS CT service on the Server computer. Select the menus:
a) "Start -> Settings -> Control Panel"
b) From "Control Panel" window select "Administrative Tools".
c) -> From "Administrative Tools" window select "Services".
d) In the "Services" window stop TNMS CT services.
Fig. 50 Stop TNMS CT Server
74 TR3272EU00TR_0401
© 2005 Siemens AG
2. Complete the following steps to de-install the software:

Open the "Add/Remove Programs" window via "Start -> Settings -> Control
Panel" and after that "Add/Remove Programs". Select "TNMS CT" and press
"Change/Remove" button.
Fig. 51 Remove TNMS CT Programs
TR3272EU00TR_0401
75
© 2005 Siemens AG
3. In the "Welcome" window, press "Next".
Fig. 52 TNMS CT Setup: Welcome window
76 TR3272EU00TR_0401
© 2005 Siemens AG
4. In the "Uninstall TNMS CT" window select "Yes" and press "Next".
Fig. 53 TNMS CT Setup: Uninstall TNMS CT
TR3272EU00TR_0401
77
© 2005 Siemens AG
5. The de-installation starts and information windows displays the software parts,
which are currently de-installed. This will take some minutes.
78 TR3272EU00TR_0401
© 2005 Siemens AG
6. The "InstallShield Wizard Complete" window is now displayed. If certain folders

could not be deleted, this is indicated here. Press "Finish" to complete the de-
3.0
Fig. 55 TNMS CT Setup: InstallShield Wizard Complete
TR3272EU00TR_0401
79
© 2005 Siemens AG
7. The computer is rebooted. Delete any remaining folders manually in the Windows
Explorer e.g. "C:\Program files\Siemens\TNMS CT\". Check that the TNMS
service mentioned above is removed from the services list.
80 TR3272EU00TR_0401
© 2005 Siemens AG
3.4 PPP dial-up setup for Q3 network elements

In order to connect to a Q3 network element via RS232, complete the following steps
to setup a new dial-up network connection:
1. Open "Start -> Settings -> Network and Dial-up Connections". The "Network
and Dial-up Connections Window is opened".
Double-click on the "Make New Connection" icon, to open the "Network
Connection Wizard".
Click "Next" to continue.
Fig. 56
TR3272EU00TR_0401
81
© 2005 Siemens AG
2. In the "Network Connection Type" window, select "Connect directly to

another computer".
Fig. 57
82 TR3272EU00TR_0401
© 2005 Siemens AG
3. In the "Host or Guest" window, select "Guest".

Fig. 58
TR3272EU00TR_0401
83
© 2005 Siemens AG
4. In the "Select a Device" window, select either "Communications Port (COM1)"

or "Communications cable between two computers (COM1)". The availability
of both these options depends on whether a “Communications cable” modem
has already been installed or not. If it is necessary, Windows 2000 will
automatically install this modem for you.
Fig. 59
84 TR3272EU00TR_0401
© 2005 Siemens AG
5. In the "Connection Availability" window, select "For all users".

Fig. 60
TR3272EU00TR_0401
85
© 2005 Siemens AG
6. In the "Completing the Network Connection Wizard" window, enter a name for
the new connection, e.g. “MPU-F”.
Click "Finish" to complete your settings.
Fig. 61
TIP
If a connection dialog appears, cancel it.
86 TR3272EU00TR_0401
© 2005 Siemens AG
7. Open "Start -> Settings -> Network and Dial-up Connections". The "Network
and Dial-up Connections" window is opened. Select the icon representing the
previously configured new connection, and select from it's context menu
"Properties". The "Connection Properties: General" window is opened.
Click "Configure" to setup the modem.
Fig. 62
TR3272EU00TR_0401
87
© 2005 Siemens AG
8. In the "Modem Configuration" window, select “19200” for Maximum speed and
uncheck the feature "Enable hardware flow control".
Click "OK" to confirm your settings.
Fig. 63
88 TR3272EU00TR_0401
© 2005 Siemens AG
9. In the "Connection Properties" window select the "Networking" tab and

uncheck all protocols except for "Internet Protocol (TCP/IP)". Select "Internet
Protocol (TCP/IP)" from the list and click "Properties".
Fig. 64
TR3272EU00TR_0401
89
© 2005 Siemens AG
10. In the "Internet Protocol (TCP/IP) Properties" window, click "Advanced..."
Fig. 65
90 TR3272EU00TR_0401
© 2005 Siemens AG
11. In the "Advanced TCP/IP Settings" window, uncheck "Use default gateway on
remote network" if you are connected to a LAN and the serial connection at the
same time. This way your LAN connection will still be available while your are
connected via serial line.
Click "OK" to confirm your settings and close all open windows.
Fig. 66
TR3272EU00TR_0401
91
© 2005 Siemens AG
12. In "TNMS CT Main" window from "Configuration" menu open "DCN

Management" entry.
In the "DCN Management" view navigate to the "Serial Line Server -> QST V2
Serial Line Channel" and open the context menu "Properties..."
In the "Properties" window open the "QB3 Channel" tab. Check the "Use PPP"
option and enter the name of the Phonebook Entry as defined previously in Step 6
"MPU-F".
Click "Apply" to confirm your settings.
Fig. 67
92 TR3272EU00TR_0401
© 2005 Siemens AG
13. In the "DCN Management" view navigate to the "Serial Line Server -> QST V2
Serial Line NE" and open the context menu "Properties..."
In the "Properties" window open the "Security" tab. Check the "User Name" field
and enter the user name e.g. "LCT", check the "Password" field and enter the
password e.g. "NEPASSWORD".
Open then "QST" tab. Check the "NSAP/IP" field and enter IP address "195.0.0.1".
Check the "QST" field and enter "QST".
Click "Apply" to confirm your settings.
Fig. 68
TR3272EU00TR_0401
93
© 2005 Siemens AG
14. To activate connections via serial interface select in the "DCN Management"
view check boxes at "QST V2 Serial Line Channel" and "QST V2 Serial Line
NE"
Fig. 69
94 TR3272EU00TR_0401
© 2005 Siemens AG
15. To login to the NE select in the tool bar of the "TNMS CT Main" window "Serial
Line" button, then in the opened "Serial Line View" window select NE icon and
from the context menu select "Start Element Manager".
Fig. 70
TR3272EU00TR_0401
95
© 2005 Siemens AG
96 TR3272EU00TR_0401
© 2005 Siemens AG
4 Exercises
Fig. 71
TR3272EU00TR_0401
97
© 2005 Siemens AG
98 TR3272EU00TR_0401
© 2005 Siemens AG
Exercise 1
Title: Installation and Administration of TNMS CT
Objectives: The participant shall be able to:

• install TNMS CT SW
• administrate user accounts
• administrate DCN objects
Pre-requisite: Pre-read chapter "Operating terminal: advanced topics"
Task1
Ask your instructor for the name of your team (e.g. student01), name and NSAP
address of the PC, which will be used for TNMS CT installation (as a reference for
the PC names and NSAP addresses use the tables below), name and the type of the
NE which will be used for the exercise (e.g. NE name: Muenchen; NE type: hiT 7070
DC) and write it down in the fields below:
I am working with the team: student _ _

Name of the PC: ___________________
Type of the NE: ___________________
Name of the NE: ____________________
Fig. 72 Login information
PC Name NSAP Address

LCT08001 470099002760000C000000004008000608001C01
LCT08002 470099002760000C000000004008000608002C01
LCT08003 470099002760000C000000004008000608003C01
LCT08004 470099002760000C000000004008000608004C01
LCT08005 470099002760000C000000004008000608005C01
Table: NSAP addresses for operating terminals hit 70xx in Row 8
TR3272EU00TR_0401
99
© 2005 Siemens AG
PC Name NSAP Address

LCT03001 470099002760000C000000004008000603001C01
LCT03002 470099002760000C000000004008000603002C01
LCT03003 470099002760000C000000004008000603003C01
LCT03004 470099002760000C000000004008000603004C01
LCT03005 470099002760000C000000004008000603005C01
Table: NSAP addresses for operating terminals hit 70xx in Row 3
WARNING
On the PC for TNMS CT installation, Windows 2000 together with Windows SP4
and Microsoft Internet Explorer V6.0 SP1 has been already preinstalled.
Perform the following steps:
1. Start PC and login Windows 2000 use the following data;
User id: "Administrator"
Password: "siemens"
2. Following the procedure described in the chapter "Operating terminal:
advanced topics" install TNMS CT with all SW components required.
TIP
The SW for TNMS CT installation can be found on the local HD in the
C:\TNMS_CT_Install directory. Additionally to the TNMS CT installation SW, the
following 3rd-party software components also can be found in the
C:\TNMS_CT_Install\Prerequisites directory:
• JavaSoft JAVA Runtime Environment.

• OSI stack.
• Acrobat Reader 5.0.
Fill in the following table
Task: Installation TNMS CT and SW components.
Parameter Achieved Result
JavaSoft JAVA Runtime Environment Installed Yes
OSI stack Installed Yes
Acrobat Reader 5.0 Installed Yes
TNMS CT Installed Yes
When you finished the SW installation reboot the PC.
100 TR3272EU00TR_0401
© 2005 Siemens AG
Task2
Once the TNMS CT software has been installed, and the computer restarted, start up
the TNMS CT system to perform the initial configurations.
TIP
Refer to the procedure "Initial configuration of TNMS CT" described in the chapter
"Operating terminal: advanced topics".
1. When you will be asked to change the password for the default administrator
account use the password: "siemens-00".
2. To install TNMS CT licenses ask your instructor for the CD with required license
files.
3. Create additional user account for the user class "Configuration". Use the
following data:
User id: "Configurator1"
Password: "config-01"
4. Configure and activate QB3M DCN channel.
5. Configure and activate NE that has been assigned to your team. Refer the
following table to obtain the NSAP address of the NE.
NE Name NSAP Address

Muenchen 470099002760000C000000004008000608007001
Nuernberg 470099002760000C000000004008000608012001
Ulm 470099002760000C000000004008000608002001
Erding 470099002760000C000000004008000608002101
Augsburg 470099002760000C000000004008000608012101
Table: NSAP addresses for Network Elements hit 70xx in Row 8
NE Name NSAP Address

Dortmund 470099002760000C000000004008000603007001
Mainz 470099002760000C000000004008000603012001
Essen 470099002760000C000000004008000603002001
Giessen 470099002760000C000000004008000603002101
Paderborn 470099002760000C000000004008000603012101
Table: NSAP addresses for Network Elements hit 70xx in Row 3
TR3272EU00TR_0401
101
© 2005 Siemens AG
6. To verify functionality of new installed TNMS CT SW logoff and logon again to

the TNMS CT with the new installed user account "Configurator1".
7. Login into the new connected NE:
"Start Element Manager".
8. Perform some simple operations (e.g. request alarms; create/delete cross-
connections).

Task: Initial configuration of TNMS CT.
TNMS CT licenses. Installed Yes
User account Created Yes
DCN channel and NE Activated Yes
TNMS CT functionality Proved Yes
102 TR3272EU00TR_0401
© 2005 Siemens AG
Task3 (optional)
PPP dial-up setup for Q3 network elements

In order to connect to a SURPASS hiT 70xx series network element via RS232 a new
dial-up network connection needs to be preconfigured. To configure a new dial-up
network connection and prove functionality of the serial interface proceed the
following steps:
1. Ask your instructor for the null modem cable and using the cable connect NE
assigned to your team with the TNMS CT PC.
2. Configure a new dial-up network connection.
TIP
Refer to the procedure "PPP dial-up setup for Q3 network elements" described in
the chapter "Operating terminal: advanced topics".
To verify functionality of new configured dial-up network connection:

3. Activate the connection to the NE assigned to your team.
4. Login into the new connected NE:
"Start Element Manager".
5. Perform some simple operations (e.g. request alarms; create/delete cross-
connections).

Task: PPP dial-up setup for Q3 network elements.
PPP dial-up network connection. Configured Yes
Functionality of the serial interface. Proved Yes
TR3272EU00TR_0401
103
© 2005 Siemens AG
104 TR3272EU00TR_0401
© 2005 Siemens AG
5 Solution
Fig. 73
TR3272EU00TR_0401
105
© 2005 Siemens AG
106 TR3272EU00TR_0401
© 2005 Siemens AG
Solution 1
Title: Installation and Administration of TNMS CT
Objectives: The participant shall be able to:

• install TNMS CT SW
• administrate user accounts
• administrate DCN objects
Pre-requisite: Pre-read chapter "Operating terminal: advanced topics"
(No solution).
TR3272EU00TR_0401
107
© 2005 Siemens AG
108 TR3272EU00TR_0401
© 2005 Siemens AG

04 Tr3272eu00tr 0401 Operating Term

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

04 Tr3272eu00tr 0401 Operating Term

Hochgeladen von

Copyright:

Verfügbare Formate

Operating terminal: advanced topics Siemens

Operating terminal: advanced topics

TNMS CT (Craft Terminal)

hiT 7070 hiT 7070

hiT 7050 hiT 7050

hiT 7070 MSP 1+1 hiT 7070

Fig. 2 TNMS CT (Craft Terminal)

1.1.1 LCT and NCT modes

TNMS CT: Client/server architecture

hiT 7070 hiT 7070

hiT 7050 hiT 7050

hiT 7070 MSP 1+1 hiT 7070

Fig. 3 TNMS CT: Client/Server architecture

1.2 Network architecture

SMA1/4, SMA4/1, SMA1K, SMA1K-CP,

SMA16, SMA16/4, SL16, SLR16, SL64,

QF Local connection to Q3, QD2

Fig. 4 Network architecture

1.3 System architecture

1.3.1 Hardware components

TNMS CT: System architecture

Fig. 5 TNMS CT: System architecture

1.3.2 Software components

TNMS CT: Software components

TNMS CT Server Components

Fig. 6 TNMS CT: Software components

2.1 Security management

Function 0 - Supervision 1 - Maintenance 2 - Operation 3- Configuration 4 - Administrator

Fig. 8 TNMS CT User Classes

2.1.1 User administration

2.1.1.1 Add a new user account

Fig. 9 Add a new user

2.1.1.2 View/edit the properties of a user account

Function: User Administration. View/edit properties.

2.1.1.3 Delete a user account

Function: User Administration. Delete a user.

Fig. 10 View/edit the properties of a user account

Fig. 11 Delete a user account

2.1.1.4 Change password

2.1.1.5 Security settings

Fig. 12 Change Password

Fig. 13 Security settings

2.1.1.6 NE user configuration

Fig. 14 NE User configuration

2.2 DCN management

Fig. 15 DCN management

2.2.1 DCN management view

Fig. 16 DCN management view

2.2.2 Display of DCN object states

Icon State Description

Fig. 17 Icons used in the DCN management view

2.2.3 Working with DCN objects

2.2.3.1 DCN object properties

Fig. 18 DCN object properties

2.2.3.2 Activating / deactivating DCN object

Fig. 19 Activated DCN objects

Fig. 20 Deactivated DCN objects

2.2.3.3 Adding a new DCN object

Function: DCN Management. Create a New DCN Object.

Fig. 21 Create a new DCN object

The QB3 DCN channel supports several types of NE controllers:

2.2.3.4 Deleting a DCN object

Fig. 22 Deleting a DCN object