siemens tnms (technical descriptions)

Information

TNMS Core 6.0

TED

A42022-L5938-B51-1-7618

2 A42022-L5938-B51-1-7618

TED InformationTNMS Core 6.0

! Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts can also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.

Therefore only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950. All equipment connected has to comply with theapplicable safety standards.

Copyright (C) Siemens AG 2001.

Issued by the Information and Communication Networks GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A42022-L5938-B51-1-7618 3

InformationTNMS Core 6.0

TED

This document consists of a total of 41 pages. All pages are issue 1.

Contents

1 Introductory Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Available Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Symbols Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Network Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.1 Network Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.2 Data Communication Networks (DCN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.2.1 PDH Access Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1.2.2 SDH Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1.2.3 WDM Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 Network Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.1 TNMS Core NetServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.2 TNMS Core Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.3 TNMS Core Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.4 TNMS Core SysAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5 Interfaces to Higher-Ranking Management Systems . . . . . . . . . . . . . . . . . 213.5.1 Data Import/Export Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5.2 DCN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.1 Licensed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3 Additional Backup Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.1 Features of TNMS Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.2 Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2.1 TNMS Core NetServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2.2 TNMS Core Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2.3 TNMS Core Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.3 Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.3.1 Log Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.3.2 Log Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6 Client Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.1 Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.1.1 Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.1.2 Universal Objects (UNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.1.2.1 Network Augmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 A42022-L5938-B51-1-7618


6.1.3 Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.1.4 Subscriber Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.2 Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.3 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.4 Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7 SysAdmin Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.1 TNMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.2 Alarm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.3 Cost Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.4 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.5 Date / Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.6 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.6.1 SNMP Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.6.2 OCA Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.6.3 SNIF Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.7 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.8 NE Inscription Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.9 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.9.1 Account Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.9.2 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.10 DCN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

A42022-L5938-B51-1-7618 5


TED

1 Introductory Notes

1.1 Available DocumentationAll TNMS Core manuals are available both in hardcopy form and on CD-ROM, and canbe ordered either in German or in English.

• Technical Description (TED)The Technical Description provides an overview of the applications, features, systemarchitecture and functions of TNMS Core.

• Installation Manual (IMN)The Installation Manual contains instructions on installing the TNMS Core software.

• Operator Guidelines (OGL)The Operator Guidelines contain a general description of the TNMS Core Client andTNMS Core SysAdmin user interfaces, as well as the necessary background infor-mation.

You may also consult the online help which is delivered with the software. It providescomprehensive instructions on the functions offered by the Client and SysAdmin userinterfaces. The ‘Contents’, ‘Index’ and ‘Search’ tabs enable the online help to besearched quickly and conveniently. Individual help topics can be printed, and context-sensitive help texts called up directly from the user interface.

The complete online help and the individual instruction manuals are also provided as*.pdf files under the Help menu. These files can be viewed and printed using AdobeAcrobat Reader.

Manual Type Order Number(English)

Order Number(German)

Technical Description(TED)

A42022-L5938-B51-*-7618 A42022-L5938-B51-*-18

Installation Manual(IMN)

A42022-L5938-B52-*-76D1 A42022-L5938-B52-*-D1

Operator Guidelines(OGL)

A42022-L5938-B53-*-7619 A42022-L5938-B53-*-19

CD-ROM (containsTED, IMN and OGL)

A42022-L5938-B10-*-76K5 A42022-L5938-B10-*-K5

Table 1.1 TNMS Core Manuals

6 A42022-L5938-B51-1-7618


1.2 Symbols Used in This ManualThe following symbols are used in this manual:

1.3 FeedbackWe aim to provide you with documentation which is easy to understand and user-friendly. Your practical experience is very important to us in achieving this objective.

We are particularly interested in your opinion on the following issues:• Where is too much/not enough detail provided?• Where do you find these instructions difficult to understand?• Where would additional graphics be useful to improve understanding?• What improvements could be made to the basic layout of the TNMS Core

documentation?

Please enter your comments, suggestions and corrections in the questionnaireon the following page. If necessary, this questionnaire can also be photocopiedor printed out from your documentation CD.So that we can contact you and discuss your comments at greater length if neces-sary, do not forget to enter your contact details.

Thank you in advance for your support!

iAdditional information

!Warnings

Table 1.2 Symbols

A42022-L5938-B51-1-7618 7


TED

QuestionnaireCompleted questionnaires can be returned:by fax: +49 89 722 57315or by post:SIEMENS AKTIENGESELLSCHAFTInformation and Communication Networks GroupICN ON CS C2Hofmannstrasse 51D-81359 München

Company/Name:

Address:

Department: Telephone:Fax:

Date: Signed:

I am using this documentation My duties include

(...) As service documentation (...) Commissioning

(...) As an installation/commissioning guide (...) Operation

(...) As a general introduction (...) Maintenance

(...) For reference purposes (...) Sales

(...) As training material (...) Training activities

(...) _______________________________ (...) _______________________________

Page Remarks

8 A42022-L5938-B51-1-7618


2 Network OverviewFig. 2.1 shows the general structure of a transmission network managed by TNMS Core.The network elements (NE) provide various management interfaces. This means thatthey can be connected via the DCN to the management system in several ways.

Fig. 2.1 General Structure of a TNMS Core Network

Element management functions are executed via the element managers (LCTs, TNMS-SX, EM-OS) provided by the TNMS Core system.

For network elements managed via EM-OS, network management is restricted to faultmanagement (alarm mapping). These network elements are displayed as universalobjects in the TNMS Core network plan.

Managementinterface

TNMS CoreD

CN

Type of network element

QD2SISA

QB3

TNMS-SX

EM-OSEMOS-SLI

ELI-SXEM

FMX, CMX

SMA1/4, SL16, MTS, MODIF, SMA1K,SMA1K-CP, SLR16, Infinity WL, InfinityWLS, OSN, OCU, Infinity MTS , WTTR,SMA16, SMA4, SLD16, SL64

SXA, SXD

SLxx, SMAxx, etc.

Integrated element manager (EM):LCTs, TNMS-SX, EM-OS

Waveline (SNMP)Waveline EL2

UNO

TNMPV2SRT 1C

(logical interface)

e. g. NEs supported via TIF,e. g. ERX700/1400, SSU-2000e

A42022-L5938-B51-1-7618 9


TED

2.1 Network ArchitectureTNMS Core can be used universally in all kinds of transport networks. The seamlessintegration of WDM, SDH and PDH equipment significantly increases the number ofapplication scenarios, not all of which are described here.

2.1.1 Network ElementsTNMS Core supports line, star and ring networks comprising the network elementslisted in Table 2.1.

NE class Device Version Note

WDM Infinity WL 2.1, 2.2, 2.3,2.35

Infinity WLS 1.0, 2.0-1, 2.0-2,2.0-5

PM is not supported.

Infinity MTS 1.1E, 1.1 ANSI,2.0-1, 2.0-2

1.1.ANSI: Only thesubtypes OTT8, OTT16and OLR are supported.2.0-1: Only the subtypesOTTU and OLRU aresupported.2.0-2: Only the subtypesOADMU, OTTU andOLRU are supported.

OSN OCU 1.0E, 1.2.5,2.0.1 (TEX),2.1 (OCR)

SRC

OSN MODIF 1.0

Table 2.1 List of Supported Network Elements

10 A42022-L5938-B51-1-7618


SDH OSN WTTR 2.0

SMA1/4 2.2.3, 2.3, 2.3E Includes 45 M tributary

SMA 4 2.3E

SMA1K 3.2, 3.3

SMA1K-CP 3.2, 3.3

SMA16 4.1, 4.2

SMA16/4 4.2

SL16 2.3, 2.4, 2.5

SL64 3.2, 3.25, 3.26,3.27

SLR 2.2

SXA 3.2.30, 3.2.50,3.3.10

SXD 3.1.20, 3.1.30

ISDH

PDH FMX2 (MXS19 and CMXSsubrack)

2

CC64kr

LTO-LT, LTO-NT

ASA32 SUE

LTCOH-LT, LTCOH-NT LTC(LT), LTC(NT)

SISA-V SISA-KGwd SISAK

SISA-V/LMX CUA/CUD

SISA-V/LMX-V2 SUE

SISA-V LTC(LT, LTO(LT)

SISA GK V11 asynchron EM only

SISA GK G703 EM only

SISA GK E EM only


Table 2.1 List of Supported Network Elements (Cont.)

A42022-L5938-B51-1-7618 11


TED

TNMS Core can manage large, medium and small transport networks. Networkdimensioning with the TMN system is influenced by the following factors:– Network criteria, e.g. size, topology, simple/complex network elements– Operational criteria, e.g. number of services, number of PMPs– Fault criteria, e.g. alarm bursts

As these criteria can vary considerably from network to network, separate planning isfor each customer.

2.1.2 Data Communication Networks (DCN)Data communication networks play an important role in managed transmissionnetworks. DCN faults therefore have a considerable effect on the functionality of thenetwork as a whole. The transmission rate of each DCN also influences the generalnetwork performance.

Settings for the various DCN interfaces to the network elements (e.g. addresses) aremade in TNMS Core SysAdmin. For more information, see Section 3.5.2.

Other Waveline EL 2

ERX700/1400 Screen-level integrationof EM

SSU-2000E Screen-level integrationof EM

ULAF+ Screen-level integrationof EM

Microsens GBE Screen-level integrationof EM


Table 2.1 List of Supported Network Elements (Cont.)

12 A42022-L5938-B51-1-7618


2.1.2.1 PDH Access NetworksTNMS Core supports n x 64-Kbit PDH access services using tributary cards such asFMX/CMX. End-to-end management for PDH equipment is implemented via TNMSCore at the network layer (NWL). Other tributary cards such as ISDN and 64-Kbit sub-bitrate cards are configured via the LCT application and implemented at the elementmanagement layer (EML). Administration of these services is therefore performeddirectly via the element managers. For the purposes of fault management, however, allalarms are written to a global alarm log maintained in TNMS Core.Fig. 2.2 shows a typical application scenario with FMX/CMX in interaction with a SDHnetwork.

Fig. 2.2 PDH Access Network

STM-4

SMASMA SMA

SMA

SMA

SMA

DCN

STM-4

Managed network

TNMS Core

CMX

FMX

CMX

FMX

SMA

CMX

A42022-L5938-B51-1-7618 13


TED

2.1.2.2 SDH NetworksTMNS Core uses a combination of various SDH devices to enable management ofservices ranging from 2 Mbit/s up to STM-64. Both line and ring structures includingBSHR and MSLTP are supported, depending on the NE version. The combination of fullelement management functionality and extensive network layer capabilities providescomprehensive support for network operator tasks such as end-to-end service and pathprovisioning (see Chapter 6). Additional operations such as supervision, monitoring,maintenance and provisioning of the SDH network can be completed without the needfor auxiliary TMN equipment.

Fig. 2.3 SDH Network

SMA4

DCN

STM-16

Managed network

TNMS Core

SLD16

SLD16

SLD16

SLD16

SMA1

SMA1K SMA1K

SMA4

SMA4 SMA4

MSLTP

SL64 SL64 SL64

SMA16

SXA

STM-64

STM-4

14 A42022-L5938-B51-1-7618


2.1.2.3 WDM NetworksTNMS Core offers comprehensive support for new-generation WDM systems such asWaveline products for metropolitan networks, Infinity MTS for long-haul applications,Infinity WL/WLS and Optical Service Node OSN. These systems are used in ultra-highcapacity (UHC) networks as well as in metropolitan networks. Fig. 2.4 shows a simpleexample of a UHC network. The 10 Gbit/s connections represent interfaces to a lowertransport layer (comprising SDH systems, for example).

Fig. 2.4 WDM Network

DCN

Managed network

TNMS Core

InfinityOSN OSN

OSN OSN

Infinity

Infinity Infinity

Infinity

Infinity

Infinity

Infinity

n x 10 Gbit/s n x 10 Gbit/s

n x 10 Gbit/sn x 10 Gbit/s

A42022-L5938-B51-1-7618 15


TED

2.2 Network ProtectionProtection mechanisms are used to ensure the continued availability of a service evenif a connection or part of a connection fails. Services can be protected using either pathprotection (for the transmission path) or trail protection (for the physical networkelements and lines). Various network structures are supported such as meshednetworks, line structures, and rings.

A path comprises a sequence of port connections and cross connections. Both pathends may have either one or two endpoints. The path endpoints may lie on the same oron different network element layers. The route and endpoints can be modified by theoperator.

A trail comprises a defined number of connections between termination points on thesame network layer. Connections in adjacent transmission layers have a client/serverrelationship. The individual trails are known as client trails, and if located on adjacenttransmission layers, they can be linked to create a server trail.

Path Protection

Path protection is configured in TNMS Core using a series of dedicated windows whichcreate a standby path for every working path selected. The option for sub-networkconnection protection (SNCP) provides protection at every transmission level and cantherefore be used to protect either an entire path or parts of a path across a network.

Trail Protection

Trail protection is performed on the network element layer via an element manager. Thepossibilities include multiplex section protection (MSP), a bi-directional self-healingring (BSHR) or optical protection .

Multiplex section protection is used on lines to protect point-to-point connectionsbetween network elements with multiplex capability. The individual service is notprotected, rather the whole multiplex section between two adjacent nodes with multiplexfunctionality. A two or four-fiber bi-directional self-healing ring (BSHR-2/4) is a specialmultiplex section protection mechanism used within rings. It protects the whole multiplexsection between two adjacent ring nodes, called a span. Optical protection protectsspecifically against failures on the optical layer.

16 A42022-L5938-B51-1-7618


3 System Overview

3.1 General InformationThe telecommunication network management system TNMS Core is an integrated solu-tion designed for large, medium and small networks. It supports network elements withWDM, SDH, PDH and Ethernet interfaces and can be used to monitor and configureentire networks, both in core and backbone applications.

3.2 System ArchitectureTNMS Core is a scalable multi-user system with a client/server architecture comprisingseveral industry standard PCs with the Windows 2000 operating system and varioussoftware applications. External devices such as printers, tape units and remote clientsare not dealt with here.

Fig. 3.1 System Architecture

The TNMS Core software comprises the Client, SysAdmin, Server and NetServer appli-cations. Client and SysAdmin are installed on a client PC. To support distributed oper-ation of the network, up to 20 Client installations can be managed simultaneously.Concurrent access to network resources is regulated by the server PC - only one oper-ator at a time is granted write access to a network element.

The Server software is installed on a server PC. A second SysAdmin installation on theserver PC together with an additional monitor is also recommended as this enablesadministration of the TNMS Core system to continue even if the dataflow between theclient and server PC is interrupted. If the installation of an OCA proxy or SNIF proxy isrequired, additional 3rd-party software must also be installed on the server PC.

TNMS Core Client (max. 20 PCs,3rd-party software) TNMS CoreSysAdmin

TNMS Core Client (1)TNMS Core SysAdmin

Subnetwork A

Large network

TNMS CoreNetServer (1)

TNMS CoreNetServer(max. 10 PCs)

TNMS Core Server(TNMS Core SysAdmin,3rd-party software)

Subnetwork CSubnetwork B

A42022-L5938-B51-1-7618 17


TED

An additional client PC must also be installed with 3rd-party software if an OCA proxy isto be installed or if access to a UNIX PC is required.

The NetServer software is installed on a netserver PC. Depending on the number ofnetwork elements, up to 10 NetServer PCs can be managed simultaneously.

18 A42022-L5938-B51-1-7618


3.3 Software ComponentsThe TNMS Core software architecture is scalable. This means that different softwareapplication groups can be installed on one or more PCs. However, software applicationsof the same group must be installed on the same PC (see diagram below).

Fig. 3.2 Software Components

Open CORBA

TNMS Core Client TNMS Core SysAdmin

TNMS Core Client components

TNMS Core Server

Network managementuser interface

Elementmanager

Elementmanager

SNIF/C

System administrationuser interface

TNMS Core SysAdmincomponents

TNMS Core Server components

Umbrella systeminterface proxy


SNIF

SNMP

TNMS Core NetServer components

TNMS Core NetServer

TNMS CoreConfig database

TNMS CoreServer database

TNMS CoreLog database

TNMS CoreNetServerdatabase


External dataevaluation tool

Export/import

EML server

NE controllerNE controller

DCN connector

DCN connectionDCN connection

EML server

NE controllerNE controller

Protocol stack Protocol stack

NEsNEs

NEsNEs

A42022-L5938-B51-1-7618 19


TED

3.3.1 TNMS Core NetServerTNMS Core NetServer operates as a mediation device for the DCNs connected to it.It processes large volumes of data imported from the DCN and relays this informationto the TNMS Core Server in compressed form. The NetServer supports all NE-specificfunctions, except for the element managers included with TNMS Core Client.

The NE Controllers

The NE controllers are provided with the NetServer application. A corresponding NEcontroller must be registered in the system for every NE type to be managed by TNMSCore. Each NE controller class can support different NE types, but each NE can only becontrolled by one type of NE controller.

The main task of an NE controller is to convert NE-specific management interfaces to asimple internal TNMS Core element management interface. In this way, network layermanagement in the TNMS Core Server only receives the necessary information fromthe element management layer.

The DCN Connectors

The DCN connectors are separate software components included with the NetServer.An associated DCN connector must be provided for each DCN interfacing with TNMSCore.

The DCN connectors provide the interfaces for managing connections and transferringdata between network elements and NE controllers. The main difference between thecraft terminals (LCT and (NCT) and TNMS Core is that TNMS Core can operate all DCNconnectors simultaneously.

The TNMS Core NetServer Database

The NetServer also includes the TNMS Core NetServer database where all relevantnetwork element data is stored.

3.3.2 TNMS Core ServerTNMS Core Server is the central component of TNMS Core and controls the followingFCAPS (Fault, Configuration, Accounting, Performance, Security) functions for thenetwork management layer and element management layer:– Fault Management– Configuration Management– Performance Management– Security Management

Data relating to these processes is written to various databases. The config database(also known as the TNMS Core registry) stores general data, the server database storesnetwork management data and the log database stores log data. More information onTNMS Core databases is provided in Section 5.3.

As well as coordinating DCN management functions such as the administration ofnetwork element addresses, DCN channels and NetServers, TNMS Core Server alsosupports interfaces to higher-ranking network management systems, to TNMS CoreNetServers and to TNMS Core Clients. Up to 20 Clients and 10 NetServers can beconnected to the TNMS Core Server at the same time.

20 A42022-L5938-B51-1-7618


3.3.3 TNMS Core ClientTNMS Core Client provides an intuitive, user-friendly interface for networkmanagement. All TNMS Core Server management functions are accessed via theTNMS Core Client interface. Access is also provided to the element managers using auser interface identical to that of the LCTs. The element managers in turn access theNE via the NE controller provided with TNMS Core NetServer.

TNMS Core Client supports the connection of remote clients via modem or ISDN. Forexternal data evaluation, TNMS Core Client therefore provides a data export functionwhich enables the operator to save the content of each log to a separate file.

Other TNMS Core management functions are called up using the File, View, Fault,Configuration, Performance, Security, Windows and Help menus. Most functions arealso directly accessible via object-oriented context menus.

3.3.4 TNMS Core SysAdminThe SysAdmin application offers a dedicated user interface for performing systemadministration functions. Supported functions include user, database and accountconfiguration, DCN management, system monitoring and system security.

These functions are accessed via the following items in the SysAdmin functional tree:– TNMS Server– Alarm Settings– Cost factors– Database– Date / Time– External Interfaces– Licensing– NE Inscription Settings– Security

Other administration functions can be called up using the File, View, Server, Configura-tion, Security, Window and Help menus, with additional windows also provided forsystem message log management, DCN management and TNMS Core Client moni-toring.

The interface itself is similar to the TNMS Core Client user interface (see Section 3.3.3)and is operated in similar fashion.

iDetailed operating information is provided in the Operator Guidelines (OGL) and in theonline help.

iDetailed information on SysAdmin is provided in the Operator Guidelines (OGL) and inthe online help.

A42022-L5938-B51-1-7618 21


TED

3.4 DatabasesTNMS Core supports the following databases:– NetServer database– Server database– Config database– Log database

The NetServer database is located in the TNMS Core NetServer. It stores all NE datarelevant for TNMS Core management tasks. Since this data can be called up via theNEs at any time, the TNMS Core NetServer database does not include an automaticbackup facility.

The Server database is located in the TNMS Core Server. It stores all network manage-ment data which cannot be assigned to NEs. This includes information on subscribers,services, paths and the resources which these require. Backup and restore functionsare provided.

The Config database is located in the TNMS Core Server. It stores informationconcerning user management, licenses, general settings and DCN settings. Backup andrestore functions are provided.

The Log database is located in the TNMS Core Server. It stores all logs, apart from thenotification log. Backup and restore functions are provided.

The TNMS Core NetServer database and the TNMS Core Server database are createdautomatically the first time TNMS Core NetServer or TNMS Core Server are started.TNMS Core Server also creates a copy of the TNMS Core Server database and a logfile so that the server database can be backed up and restored if necessary.

3.5 Interfaces to Higher-Ranking Management SystemsTNMS Core supports various external interfaces, with the external interfaces supportpackage providing the OCA, SNMP and SNIF components.

The physical arrangement of the external interfaces is illustrated in Figure 3.2.

3.5.1 Data Import/Export InterfacesTNMS Core supports a variety of convenient import/export options. As well as theimport/export of network configuration data using XML, for example, performance logsdefined for services or network elements can also be exported to different applicationsand systems using the Performance Log Export Tool (PLET). In addition to performancelogs, alarm logs and network event logs can also be exported using external tools.

Automatic access to logfile data is also available via the OLE-DB interface (object-linking and embedding database) for active data objects. This interface can also be usedto export performance data for processing by external tools.

Finally, administration users can import and export external configuration data to andfrom the TNMS Core Server database using the import/export interfaces provided.

22 A42022-L5938-B51-1-7618


3.5.2 DCN InterfacesNetwork elements are either connected directly to the TNMS Core NetServer or via anexternal element manager (see Fig. 2.1) and a DCN.

TNMS Core supports the following DCN technologies:

DCNInterface

Physical Interface Protocol Network Elements/Element Managers

QB3 Ethernet (OSI) QD2 SDH e.g. SMA1/4

QST SDH e.g. SL16

Q3 WDM e.g. MTS, MODIF

ELI-SXEM Ethernet (TCP/IP) ELI SXA, SXD

TNMPV2 Ethernet (TCP/IP) TNMP Radio NEs, e.g. SRT 1C

QD2-SISA Ethernet (TCP/IP) SISA PDH (e.g. FMX, CMX) withconnection node type SISA-GKE only

EMOS-SLI RS232 SLI EMOS NEs, e.g. SLxx,SMAxx, etc.

Waveline(SNMP)

Ethernet (TCP/IP) SNMP Waveline EL2

UNO None None Universal objects

Table 3.1 DCN Interfaces

A42022-L5938-B51-1-7618 23


TED

Each type of DCN is assigned to a specific type of network element, an importantconsideration during DCN planning (see Fig. 3.3 below).

Fig. 3.3 Data Connections via Different DCNs

SMA

SMA SMA

SMA

STM-1ring

QB3-DCN (routedvia DCC channels)

Ethernet

TNMS Core

FMX

CMX

FMX

QD2

QD2-DCN routedvia 64-kbit/spayload channel

SISA-GKE

24 A42022-L5938-B51-1-7618


4 Installation NotesThe TNMS Core software includes a number of software applications and featurecomponents. It is supplied on a CD-ROM which includes a convenient master installa-tion program for installing the individual TNMS Core applications, or features such asQB3 Support, Waveline ELI, etc. Each application and feature can also be installedseparately using the relevant package installation program.The master installation program is also used for adding or removing components andsubcomponents and for uninstalling or upgrading the TNMS Core software.

4.1 Licensed SoftwareVarious software products referred to in this manual have been licensed by Siemens AGand are provided together with the TNMS Core software. Any questions concerningthese products should therefore be directed to Siemens AG rather than to the manufac-turer in question.

4.2 Hardware RequirementsThe table below provides an overview of the minimum hardware requirements for TNMSCore. However, as greater capacity may be required depending on the network size,planning for hardware, software and licences should be undertaken on a project-specificbasis.

iFull commissioning and startup details can be found in the Installation Manual (IMN).

Hardware Remarks

TNMS Core NetServer

- Pentium III PC 800 MHz

- Memory 1 GB

- 18 GB SCSI HD

- 1.44 MB floppy disk

- CD-ROM drive

- Ethernet card 2 x

- 17-inch color monitor

TNMS Core Server


- Memory 1 GB

- 36 GB SCSI HD 2 x


- CD-ROM drive

Tab. 4.1 Hardware Requirements

A42022-L5938-B51-1-7618 25


TED

- Ethernet cards 2 x, optional


- RAID controller Optional

- DAT streamer for backup

TNMS Core Client


- Memory 512 MB 2x

- 9 GB SCSI HD


- CD-ROM drive

- Ethernet card


- PC I/O card Optional

Operating System

Windows 2000 Professional/Serverincl. Service Pack 2

Hardware Remarks

Tab. 4.1 Hardware Requirements

26 A42022-L5938-B51-1-7618


4.3 Additional Backup HardwareTNMS Core meets stringent data security requirements by using a multi-stage concept.The TNMS Core configuration can be expanded as required using the following hard-ware options:

– Mirror disks: The TNMS Core Server is equipped with duplicate hard disks and aSCSI RAID controller system. This prevents the failure of individual hard disks frominterrupting operations.

– Warm standby TNMS Core Server: This option can be used if the TNMS CoreServer is no longer available, e.g. due to a fire or complete hardware failure. Thewarm standby server is a second server machine with exactly the same hardwareand software configuration as the active server. The operator registers the warmstandby server at the active TNMS Core Server and activates database replicationmechanisms. Should a failure occur, the operator simply switches manually to thewarm standby server and starts the TNMS Core Server process as normal on thewarm standby computer.

– Cold standby TNMS Core NetServer: This option can be used if the TNMS CoreNetServer is no longer available, e.g. due to a fire or complete hardware failure. Thecold standby NetServer is a second machine with exactly the same hardware andsoftware configuration as the active NetServer. Activating a cold standby NetServerrequires full DCN access at the standby site.

– Additional Archive Server : An additional server at the LAN runs as a file server forthe TNMS Core databases. Should the TNMS Core Server fail, the stored databasebackups can be used to restore the TNMS Core database.

– TNMS Core has an internal DAT system . This allows data to be backed up atregular intervals without interrupting operations.

A42022-L5938-B51-1-7618 27


TED

5 Functional OverviewTNMS Core provides all the major network management functions defined in the ITU-Tstandard M.3010 “Principles for a Telecommunications Management Network”.Fault, configuration and performance management are supported at the elementmanagement layer, with configuration management and fault management alsoprovided at the network management layer. Additional configuration, fault and perfor-mance management features are available at the service management layer, andvarious security management features are also implemented.

5.1 Features of TNMS CoreThe main features of TNMS Core are summarized below:– Integrated management for network elements with WDM, SDH, PDH and Ethernet

interfaces– Management at the network layer, network element layer, and service management

layer– Fault, configuration, performance and security management– End-to-end connection management at the following transmission levels

SDH/SONET: STM-256, STM-64, STM-16, STM-4, STM-1, STM0, STS1( VC4, VC4-4, VC4-16, VC3, VC2, VC11, VC12)PDH: 140, 45, 34, 8, 2; 1.5 Mbit/s, 64 kbit/s, n x 64 kbit/sWDM: OCh, OMS, ODU2

– Support by SNCP during manual routing– Support of VC4 concatenation– Support of virtual private networks (VPN)– Support of domains– Open CORBA interface to umbrella TMN– SNMP interface to umbrella TMN (alarm management only)– IP interface to web/LCT– Import/export interface for configuration data and logs– External alarming via e-mail/SMS– Visual network representation, intuitive operator guidance, detailed and context-

sensitive online help– Scalable system architecture– Multi-user capability (up to 20 clients can be connected to the server)– High system availability– Remote control via public networks– Dedicated configuration windows for automatic and manual routing– Grouping NEs to form NE containers– Straightforward insertion/updating of network elements– Software upgrades without loss of data– Subscriber management– Support of different management interfaces to the NEs– Redundant standby system

These functions are available via the Client and SysAdmin interfaces.For more information, see Chapter 6 and Chapter 7.

28 A42022-L5938-B51-1-7618


5.2 Basic Operation

5.2.1 TNMS Core NetServer

Starting TNMS Core NetServer

TNMS Core NetServer can be started either automatically or manually. When theNetServer is started, all registered DCN connectors are activated. An associated NEcontroller is also detected and started for each accessible network element.

Once started, each NE controller requests from its network element the data requiredfor detecting changes in alarms, port configurations, cross-connections, etc. This infor-mation is then compared with information already stored for the network element on theNetServer.

During the synchronization process which follows, the NetServer compares its existingdata with the data supplied by the NE. The NetServer data is overwritten if it does notcorrelate with the data supplied by the NE - data is not transferred to the networkelement. The operator can manually initiate the resynchronization of NE data andrefresh current alarms. Other operator actions cannot be performed on the NE while thedata request is in progress or during resynchronization.

Stopping TNMS Core NetServer

TNMS Core NetServer can be stopped by the administrator. This action shuts down allcommunication channels and isolates the DCN connectors from the DCN. The TNMSCore NetServer database is also closed.

Deactivating the TNMS Core NetServer

TNMS Core NetServer can also be deactivated by the administrator. This actionsuspends communication between the TNMS Core NetServer, NetServer componentsand the TNMS Core Server.

5.2.2 TNMS Core Server

Starting TNMS Core Server

TNMS Core Server can be either be started automatically or manually. Once it has beenstarted, TNMS Core Server is linked to all active TNMS Core NetServers.

Concurrent Access

Concurrent access to different TNMS Core Clients is managed by the TNMS CoreServer as follows:– Network configuration, creation of port connections and alterations to icons in the

network editor are only permitted for one TNMS Core Client at a time.– Subscriber information can only be changed by one operator at a time.– If selected for service management in the service mode, a network element is not

available to other operators.– Up to 20 Client installations can be operated simultaneously.

Distribution of Date / Time

TNMS Core provides a manual date and time synchronization function for all managedNEs and TNMS Core components. The TNMS Core Server distributes the current

A42022-L5938-B51-1-7618 29


TED

TNMS Core Server time in GMT to every available NE controller. The date and time arealso distributed to all active NetServers and connected Client PCs, with the exception ofNetServer or Client installations running on the TNMS Core Server machine.

Stopping TNMS Core Server

TNMS Core Server can be stopped by the administrator. When the server is stopped,all connected Client PCs are notified and any further login attempts rejected. Once allClients have been isolated from the TNMS Core Server, the NetServers are shut downand the TNMS Core databases closed. The TNMS Core Server can also be stoppedindependently of the NetServers, for example if maintenance work is required.

5.2.3 TNMS Core Client

Starting a TNMS Core Client

Once the TNMS Core Client has been started, the operator can enter the login data.Functions authorized by the operator’s user class can now be accessed (see Section7.9.2).

The Client contacts the Server and requests alarm information, port and connectiondata, and the data required for mapping the network. If complete data is not availablefor certain network elements, these are shown as unavailable on the user interface bya box containing three question marks.

The first time the Client is started, only the notifications log is opened. In subsequentsessions, log windows which were opened when previous sessions were shut down arealso opened. The entries from previous sessions are then displayed.

If the TNMS Core Server is not available, an error message is displayed.

Starting Element Manager Applications

The element manager applications are started via TNMS Core Client. A data connectionis established to the relevant NE which allows the user to execute required functionsdirectly at the NE. The user interface is the same as for operations with the LCT.

Administrating NE Write Access

TNMS Core only administers write access to managed network elements which supportthis feature. Write access to a given network element or set of network elements can berequested, enforced or released. In this way the TNMS Core operator also has limitedcontrol over external LCT write access.

Terminating a TNMS Core Client Session

A TNMS Core Client session is terminated when the user logs off. All windows areclosed and access is only provided to the login function.

30 A42022-L5938-B51-1-7618


5.3 Log ManagementIn TNMS Core, specific operator activities as well as random actions and events arestored in log files on the TNMS Core Server. The Performance Log Export Tool (PLET)exports performance logs defined for services or network elements to different applica-tions and systems. The log contents can also be printed out, saved to a file, or evaluatedvia a standard OLE-DB/ADO interface.

5.3.1 Log ClassesIn TNMS Core, each log is assigned one of the following classes:– Permanent– Custom– Non-persistent

Permanent logs are fixed, global logs administered by the TNMS Core system. Theoperator can however specify certain attributes such as the type of event to be included,maximum log size, etc.

Custom logs are created and administered entirely by the operator. Operators cancreate or delete custom logs according to their individual access rights. Attributes suchas log capacity and scope can be defined as required, and logs of this type can alsostarted or stopped at any time.

Non-persistent logs are maintained by the TNMS Core Client and TNMS CoreSysAdmin and only exist for the duration of a client session. The log content is deletedwhen the client session is terminated.

5.3.2 Log TypesThe following log types are possible in TNMS Core:

The alarm log contains a chronological list of alarms which have occurred. Togglingalarms, i.e. identical alarms which are triggered repeatedly, are entered once only witha timestamp indicating when they were raised and when they were cleared.

The system message log contains a chronological list of relevant administrativeevents. Critical events are indicated at the user interface.

Log Type TNMS CoreClient

TNMS CoreSysAdmin

Log Class

Alarm log X Permanent log

System message log X X Permanent log

Network event log X Permanent log

Security event log X Permanent log

Performance log X Custom log

Notifications log X X Non-persistent log

Operator input log X Non-persistent log

Table 5.1 Log Types

A42022-L5938-B51-1-7618 31


TED

The network event log documents configuration changes to the network managementlayer. It includes actions initiated or triggered directly by the network or individualnetwork components.

The security event log documents relevant security events in TNMS Core. It providesinformation such as the event type, event severity and the object affected.

The performance log documents the performance records for the measurement pointsdefined by the operator. As there may be several network elements each with a numberof measurement points, special algorithms regulate data collection and ensure that eachvalue is only requested once. These mechanisms prevent the unnecessarily highnetwork loads which can occur when numerous data requests are sent simultaneously.

The notifications log only documents events which are relevant for the current Clientsession, for example communication errors.

An individual operator input log can be created for each operator. Information relevantto the operator, such as executed actions, is collected from the permanent logs andpresented in a report window. The operator input log is a snapshot, and is therefore notupdated automatically.

32 A42022-L5938-B51-1-7618


6 Client Functions

6.1 Configuration ManagementConfiguration management is an umbrella term for the tasks involved in the organizationand modification of the network plan, the creation and modification of services, and theadministration of subscribers to these services.

6.1.1 Network ManagementNetwork elements form the basis of the network topology. Each individual NE is bothclearly identifiable and can also be combined with other NEs to form network structuresknown as NE containers. Further NE containers can then be created for each NEcontainer configured.

Connections between the NEs or between ports of the same network element arereferred to as external port connections. Connections between the various NE modulesare referred to as internal port connections. An internal port connection cannot bedeleted or created by the operator.

Network elements and port connections form the physical network depicted in thenetwork plan. The internal port connections are only visible within the port connectionproperty window.

TNMS Core contains a list of all port connections. The list can be filtered and also printedout or saved to a file for further processing.

6.1.2 Universal Objects (UNO)Where network elements or other devices are not directly supported by TNMS Core oronly offer restricted functionality, universal objects are used to provide the requiredmanagement functions. Universal objects can be created, configured and deleted, andcan be included in the network topology using port connections. For this purpose,modules and ports can be created and deleted for universal objects via a dedicatedelement manager application.

6.1.2.1 Network AugmentationNetwork augmentation refers specifically to the dynamic aspects of network restruc-turing. This includes migration from one protection mechanism to another, the insertionand removal of traffic-carrying network elements, the re-routing of paths, the extensionof managed networks and the merging of fragmented managed networks.

TNMS Core provides the following options for network augmentation:– Re-routing paths: This can be implemented either directly where traffic interruption

is permitted, or using SNCP mechanisms.– Inserting and removing network elements: NEs can be inserted or removed by modi-

fying port connections, even if these are used by services. The services must bedetached beforehand.

A42022-L5938-B51-1-7618 33


TED

6.1.3 Service ManagementService management includes the creation, maintenance and supervision of services.Once the relevant network elements have been selected, services (also known as end-to-end connections or paths) can be established quickly and conveniently in TNMS CoreClient using dedicated configuration windows. These guide the user step-by-stepthrough connection setup. Once they have been configured, services are then assignedto a subscriber.

Services can be created either automatically or manually.With automatic routing, only the endpoints must be selected. Available connections arethen searched for across all network elements between these endpoints. Automaticrouting is not possible in mixed networks.With manual routing, the operator must configure the service step-by-step via the appro-priate network elements from one endpoint to the other endpoint.Services which are created automatically can be configured with additional protectionthe during automatic routing process. For manually-created services, additional protec-tion can be configured after the service has been created.

Supported Services

Unidirectional, bidirectional and broadcast services (consisting of several unidirectionalservices) can be created. The services which TNMS Core can administer are classifiedaccording to the source and destination port, the transmission direction and type of TP,the bitrate, and the type of user data which can be transmitted (WDM, SDH or PDH).

Services are also classified according to whether both endpoints are located within theadministered network (closed path), or whether one endpoint or both endpoints arelocated outside the network (half-open path or open path).

Physical verification of the routed paths can be implemented using the options for pathloopback.

Status Management of Services and Paths

Services and paths are assigned three different operating states:– Operational– Administrative– Provisioning.

The operational state indicates whether sufficient resources are currently available toenable access to the service or path. The administrative state indicates whether thisservice or path has been locked or unlocked by the administrator. The provisioningstate indicates whether the service or path has been correctly configured.

The operational, administrative and provisioning states are shown in the service prop-erties. The provisioning state of a port connection is also indicated by the color of theends of the port connection line which links the ports together.

Showing Services and Paths

The user interface offers various service and path views.

The ‘Service Tree View’ for example contains a complete overview of all services andpaths assigned to particular subscribers. If a path is selected in this view, it can be high-lighted in the network plan. TNMS Core also provides a list of all services and pathstogether with relevant attributes. This list can be filtered according to the given

34 A42022-L5938-B51-1-7618


attributes, and also printed out or saved to a file for further processing. The details of aservice can be displayed or modified both in the service tree view and in the list view.

6.1.4 Subscriber ManagementEach new service is assigned to a subscriber. The subscriber’s name can be added toa subscriber list in TNMS Core Client, together with other relevant contact data. This listcan then be printed out or saved to a file for further processing.

6.2 Performance ManagementTNMS Core enables transmission quality in the network to be monitored at one or morenetwork elements using a series of PMPs (performance measurement points). PMPscan also be defined for a specific path or service.

The performance data collected is stored on the TNMS Core Server machine in user-defined performance logs (see Section 5.3 for details). A new performance log can becreated at any time, however in order to modify or delete an existing performance log,the log in question must be locked first.

A measurement and an update interval is configured for each performance measure-ment log. The measurement interval which determines how often data is collected canbe set to either every 15 minutes or every 24 hours. The update interval which deter-mines when data is actually written to the performance data log is freely configurable.However, in order to minimize the DCN load, it should always be set in accordance withthe measurement interval. The data is evaluated in accordance with ITU-T recommen-dations concerning error performance (G.821 and G.826).

Transmission quality can also be monitored using element managers. For networkelements managed by EM-OS or TNMS-SX, performance management is possible bothvia TNMS Core or directly via the EM-OS or TNMS-SX element managers.

6.3 Fault ManagementFault management comprises all TNMS Core alarm handling functions. These include:– Alarm list– Alarm log– Display of alarm summary– Display of alarm state– Display of alarm severity– Audible alarm– External alarm output

All alarms are administered in the TNMS Core Server and recorded in an alarm list andan alarm log. The alarm list is accessed via the TNMS Core Client. A global alarm listcontains all alarms currently raised for all NEs in the network, with the exception ofalarms which have been suppressed. An individual list of current alarms can also begenerated for each NE. Once an alarm has been cleared it is deleted from the alarm list.

The alarm log, by contrast, is a permanent record containing all network element layeralarms, both raised and cleared. It provides a complete alarm history for the supervisednetwork. The size of this log can be configured as required for up to one million entries.The alarm log and alarm lists can also be filtered and sorted in accordance with specificcriteria.

A42022-L5938-B51-1-7618 35


TED

The operator can localize the network element raising the alarm by referring to the alarmlist. The NE is then highlighted in the network plan and the DCN tree structure. Specificsymbols are used to illustrate the current access state and the highest alarm severity.These can be displayed for both the network as a whole as well as for individual networkelements. This allows the user to quickly assess the importance of the alarm concerned.The alarms at the ports determine the color of the port connection line on the networkplan.

The user can also refresh the alarm information either for an individual network element,for all NEs in an NE container or for all NEs in a DCN.

For further fault localization, the user can also call up the appropriate element manager.The element manager EM-OS, for example, provides an alarm list which can bedisplayed by TNMS Core. Additional functions must be performed via the elementmanager itself. This is simplified by screen-level integration of the EM-OS GUI.

Raised alarms can also be correlated either automatically or manually to the corre-sponding paths. With automatic correlation, alarms are only correlated to the endpointsof the affected path so that the operational state of the path can be determined quickly.Complete manual alarm correlation is also supported for complex paths so that all termi-nation points, ports and modules in the current path are also included.

6.4 Security ManagementSecurity management functions are provided to restrict access to either the TNMS Coreuser interface or to individual network elements.

Access to the TNMS Core user interface is regulated by a user ID password which isinitially configured under the security settings in the SysAdmin application (see Chapter7). If required, this password can subsequently be changed directly in the Client appli-cation.

For NEs which do not have their own security mechanisms, access can be restricted viathe NE write access options (see Section 5.2.3).

36 A42022-L5938-B51-1-7618


7 SysAdmin Functions

7.1 TNMS ServerThe TNMS Server option in the SysAdmin menu tree provides an overview of the TNMSCore Server properties as well as a list of installed sub-components.

7.2 Alarm SettingsSysAdmin supports the following alarm handling features:– Alarm messenger for alarm summary forwarding via email/SMS– Configurable alarm severity colors– Configurable toggle filter to sort alarm events– Configurable alarm objects– Configurable probable causes for alarms

7.3 Cost FactorsCost factors can be used to optimize automatically-routed paths. If cost factors areassigned to port connections, these connections are considered less attractive by theautomatic router which then searches for less expensive options.

7.4 DatabaseSysAdmin provides a comprehensive range of database functions. These functions areavailable to system administrators only, and include database analysis to ensure dataconsistency and integrity, backup and recovery utilities for data restoration in the caseof system failure, and options for importing/exporting network configuration data.TNMS Core system data is distributed across a number of databases (see Chapter 3 fordetails).

Backup

TNMS Core provides a backup facility which enables the administrator to maintainseveral sets for the TNMS Core Server database, TNMS Core Config database andTNMS Core Log database for later restoration. The operator can either implement thebackup manually, or can configure a scheduled backup to be saved to a particular direc-tory at a particular time. During the backup procedure, an analysis function checks thereferential integrity and data consistency of each backup. A browse function is alsoprovided so that the administrator can obtain an overview of existing backup sets.

As part of a manual or scheduled operation, backup sets in the dedicated directory canbe copied by the operator to a SCSI DAT streamer using the Windows 2000 backuputility. This can be completed once a day, preferably at a time of low system and useractivity.

Restore

Stopping the TNMS Server activates a restore option which the operator can use torestore a previously-created backup set from the dedicated backup directory. This oper-ation can only be completed offline and is used to support system migration, forexample. To prevent inconsistent configuration data, the option for NetServer deactiva-

A42022-L5938-B51-1-7618 37


TED

tion should also be selected. Once the restore operation has been completed, the TNMSCore Server and TNMS Core NetServer have to be restarted. Restarting the TNMSCore Server opens the restored databases and restores the backed-up configuration.

Data Replication

To minimize the loss of data after a system component breaks down, the TNMS Coresystem provides an internal database recovery mechanism for all TNMS Core data-bases. This mechanism automatically implements an internal backup at regular intervalsusing a previously-created backup copy of the database. The database itself is notaffected and normal system functionality is still available while database recovery is inprogress. Should a software failure occur, the system uses these database backups torestart the system.

TNMS Core also provides an incremental data replication function which continuouslyreplicates the databases of the active server system to the standby system. Should theactive server fail, the operator can then switch to the standby system. However, opentransactions and queued jobs are lost.

DB Import/Export

With this component the operator can export and import network configuration data.NetServer, DCN channel, network element, NE container or port connection data canbe selected as required, and then imported from a source file or exported to a destina-tion file accordingly. In this way, data can be read into the system automatically so thatthe operator does not need to re-enter configurations manually.

Log Configuration

Several different log types are maintained by the system. The space available on thehard disk for TNMS Core log data can be set using this option. Once this has beencompleted, the system message log can be configured to include a specific level ofentries, for example, and the network event log configured to include particular types ofnetwork event. Display and configuration facilities are also provided for the operatorinput log and security event log in the main SysAdmin menu. For more information onlog management and log types, see Chapter 5.

7.5 Date / TimeThe system date and time configured for the TNMS Server can be viewed and adjustedas required. The server date and time can also be set to the date and time of theSysAdmin PC .

7.6 External Interfaces

7.6.1 SNMP ProxyThe SNMP proxy component provides an SNMP-based interface to the network layer ofthe TNMS Core system and enables access to the TNMS Core management informa-tion base (MIB). It facilitates the integration of TNMS Core with umbrella fault manage-ment systems such as INMS so that any umbrella management system which supportsthe SNMP protocol and which recognizes the TNMS Core MIB can read object proper-

38 A42022-L5938-B51-1-7618


ties and receive traps from the TNMS Core element management layer and networkmanagement layer.

The SNMP proxy is a read-only interface. Once it has been configured under SysAdmin,it can be activated or deactivated as required.

7.6.2 OCA ProxyThe OCA (Open Corba Agent) proxy is an optional module which implements the openCORBA interface, a standardized, multi-technology interface for the management ofmulti-vendor transport networks. The OCA proxy enables the TNMS Core Server toconnect to third-party open CORBA managers and should be installed if TNMS Core isto be connected to a superior network management system. WDM and SDH networkelements are supported, however support is not available for PDH or SISA-V networkelements.

The OCA interface in implemented in line with TMF (TeleManagement Forum).

7.6.3 SNIF ProxyThe SNIF proxy provides access to SNIF (Service Network Interface), a read only,service-oriented interface. Two SNIF interfaces are provided, SNIF/S and SNIF/C.SNIF/S is a CORBA interface between TNMS Core Server and an umbrella manage-ment system. This interface makes the connections of the NE container (paths)managed in the TNMS Core system available to umbrella management systems.SNIF/C is an OLE2 automation interface between TNMS Core Client and an umbrellamanagement GUI client.

7.7 LicensingTNMS Core supports security mechanisms for accessing network elements, if these arealso provided by the network elements. When a connection is created to an NE, loginmust be completed successfully. A password is required for each NE, and if additionalnetwork element licences are required, these can be configured under Licensing.

7.8 NE Inscription SettingsThe network element inscription labels shown in the Network View in TNMS Client canbe adjusted here. The ID name of the network element appears by default, howeverother information such as the NE name, NE type, location, or user-defined texts enteredin the network element property pages can also be included as required.

7.9 SecuritySpecial security features are provided by SysAdmin to regulate access to the TNMSCore interface. An authorized user must have an account with a valid user ID and pass-word.

A42022-L5938-B51-1-7618 39


TED

7.9.1 Account PolicyGlobal account settings which apply for all user accounts are set under Account Policy.These include specific password restrictions and options for account lockout if an incor-rect password is entered.

7.9.2 User ManagementUnder User Management, existing user configurations can be changed and new usersset up by the administrator. The level of user access is determined by the user class,user properties, and password restrictions set by the administrator for the user in ques-tion.

The user class is of particular significance as it determines the range of functions whicha user is permitted to perform:– Supervision : the user can execute supervision functions but cannot configure or

modify element manager applications.– Maintenance : the user can execute supervision functions and start element

manager applications to access specific data on NEs. The user can also acknowl-edge alarms and configure performance logs to monitor system performance.

– Operation : the user can perform maintenance functions and create, modify ordelete services.

– Configuration : the user can perform operation functions and configurationmanagement functions.

– Administration: the user can perform configuration functions and all administrationmanagement functions. In other words, the user has unrestricted access.

If required, the administrator can also assign a user to one or more user groups. Theaccess rights defined by the individual user classes are no longer taken into account inthis case. The user group can be authorized to access one or more NE containers eachof which may represent a network domain. However, each individual NE container canonly be assigned one user or user group. The user’s access rights are limited to the NEcontainer assigned and the NEs which this container comprises.

7.10 DCN ManagementVarious functions can be implemented via DCN Management, including:– Modification of TNMS Server properties– Activation/deactivation of DCN channels– Inclusion of new NetServers– Incorporation/deletion of network elements– Modification of NetServer, network element and DCN channel properties– Display of all QD2 SISA +EMOS network elements

Network elements or other devices which are not directly supported by TNMS Core canbe managed using universal objects (see Chapter 6).

40 A42022-L5938-B51-1-7618


A42022-L5938-B51-1-7618 41


TED

8 AbbreviationsBSHR Bidirectional Self Healing Ring

DCC Data Communication Channel

DCN Data Communications Network (G.784)

ELI External Link Interface

EM Element Manager

EML Element Management Layer

GMT Greenwich Mean Time

ID Indentification (Service Status)

IMN Installation Manual

ISDN Integrated Services Digital Network

ITU-T Telecommunication Standardization Sectorof International Telecommunications Union

LAN Local Area Network

LCT Local Craft Terminal

MSLTP Multiplex Section Linear Trail Protection

NCT Network Craft Terminal

OCA Open Corba Agent

OGL Operator Guidelines

OSI Open Systems Interconnection (G.784)

OSN Optical Service Node

PDH Plesiochronous Digital Hierarchy

RAID Redundancy Array of Independent Disks

SCSI Small Computer System Interface

SDH Synchronous Digital Hierarchy

SNCP Subnetwork Connection Protection

SNMP Simple Network Management Protocol

SONET Synchronous Optical Network

STM Synchronous Transport Module

TED Technical Description

TMN Telecommunication Management Network

TP Termination Point

UHC Ultra-High Capacity

UNO Universal Objects

VC Virtual Container

WDM Wavelength Division Multiplexing

siemens tnms (technical descriptions)

Documents