Escolar Documentos
Profissional Documentos
Cultura Documentos
NOTE:
This description is related to the presently implemented and planned functionality. Therefore not all features described here are implemented in every version.
All Rights Reserved File: TNMS-CT_180208.doc Author: Reza Azimi COO_OBS_EO_PMC
Title:
page 1/24
18
18.04.08
1 2
INTRODUCTION TNMS CT
2.1 NCT/LCT mode 2.1.1 NCT mode 2.1.2 LCT mode 2.2 Graphical User Interface 2.3 Fault Management 2.4 Security Management 2.5 Remote access to Networks via Client/Server architecture 2.6 External Application Interfaces 2.7 Topology Discovery
4 5
5 5 5 6 7 9 9 9 9
11
11 11 13 14 14 15 16 17 18 19 20 21 21 21 21
22
22 23
UPGRADE STARTEGY
5.1 Upgrade procedure of old Unigate LCT/NCT into TNMS CT
23
23
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 2/24
18
18.04.08
ABBREVIATIONS
23
Table of Figures: Figure 1: TNMS CT GUI................................................................................................................... 6 Figure 2: Alarm list in TNMS CT GUI ............................................................................................. 8 Figure 3:Alarm statistic in TNMS CT ............................................................................................. 8 Figure 4: Element Manager GUI................................................................................................... 11 Figure 5: NE Info. Line.................................................................................................................. 12 Figure 6: Alarm list/attributes view in Element manager .......................................................... 13 Figure 7: Traffic View in Element Manager................................................................................. 14 Figure 8: Module view in Element Manager................................................................................ 15 Figure 9: Cross Connection view in Element Manager ............................................................. 16 Figure 10: Configuration of Timing & Synchronization parameters in element Manager...... 17 Figure 11: Performance management view in Element Manager ............................................. 18 Figure 12: Help view of Element manager .................................................................................. 20
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 3/24
18
18.04.08
1 Introduction
The TNMS CT (TNMS Craft Terminal) is an element management system for Next Generation SDH (SURPASS hiT 70xx series), SURPASS hiT 73xx & 75xx series, DWDM family for backbone networks, feeder and metro networks, Complete range of SDH-Legacy NEs (SMA1/4/16, SL16/64, etc.) . TNMS CT is a common platform solution for different Network Element (NE) types with the benefit modular product concept with homogeneous user interface that will be developed further with the demands of the market. 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. The PC software has two parts : 1. TNMS CT as Common part: for all common functions like fault management, security, administration and Provisoning of NEs. 2. Element Manager: Managed the network element specific functions, the NE application. TNMS CT basically allows local as well as remote operation and control also there is the additional possibility to have a graphical network view, concerning fault detection. It is possible to open more than one NE application at the same time. The number of NEs to be managed in a SDH/WDM network is limited. SIEMENS currently recommends a restriction to approximately 150 NEs, to ensure best performance and a clear representation of the network via the GUI. To manage networks with more than 150 Network Elements Siemens AG recommends to use the TNMS Core. TNMS CT supports a Serial Line Interface for local operation (RS232/V.24, 9.6/19.2 kbit/s) as well as remote operation via an Ethernet Interface. TNMS has been conceived to manage the complete Siemens optical network portfolio.
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 4/24
18
18.04.08
2 TNMS CT
2.1 NCT/LCT mode
TNMS CT supports two different application modes, the NCT and LCT mode. The differences abouts the modes are characterised in the next chapter. 2.1.1 NCT mode The NCT mode supports the daily work of a service technician in a software tool optimized way. Using the NCT mode it is possible to manage small transport networks. NCT-Mode feature can be described as following : Support of up to 150 NEs Max. 50 open element managers at the same time. Based on Client Server architecture, the Client login capability is supported. (local or remote). Network Alarm list or Network Alarm logs are supported.
TNMS CT is able to manage 150 NE at the same time without restriction of the Network topology complexity. 2.1.2 LCT mode The LCT mode provides the service technician with a basic function access to one network element. LCT-Mode feature can be described as following : Elementary requirements in order to commissioning of a NE. One Client and one Server on the same PC.
As comparison with NCT mode , LCT mode has the following restrictions: Only three Element Managers can be opened simultaneously, however it is possible to establish a connection to 50 Network Elements. Network Alarm list or Network Alarm logs are not supported. Remote login is not supported.
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 5/24
18
18.04.08
Title:
page 6/24
18
18.04.08
File: For external communication such as print View: search NE, System message log, . Fault: Display alarm lists, Alarm acknowledge, alarm request Configuration: Creation and activation of all possible configurations in the different functional levels Security Window: Individual monitor configuration Help
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 7/24
18
18.04.08
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 8/24
18
18.04.08
Operation
Configuration Adminsitrator
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 9/24
18
18.04.08
function e.g. SMA, SMA1k, SLR). The port connection discovery of the TNMS CT starts with the activating of the network elements inside the TNMS CT NE connection management (DCN Management). During the initialization process of the network elements the server collects the port connection information and stores the information. The client GUI displays the topology information at the network view. Only one configured network element inside the DCN Management is enough to start the port connection and neighbor NE discovery process.
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 10/24
18
18.04.08
Figure 4: Element Manager GUI Copyright Siemens AG 2003 TNMS CT Technical Description
Issue: Date: Ordering Nr./SNR All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
Title:
page 11/24
18
18.04.08
Displayed menu items supports the following views: File: For external communication such as print and hard copy View: search NE, System message log, . NE-State: for maintenance reasons, set to Idle, Active, maintenance or Operation Fault: Display alarm lists, Alarm acknowledge, alarm request, set/remove alarm inhibition or suppression Performance: to see status of 15 Min or 24 hours performance measurements Security: to get Access right or releasing of access right Option : setting of Alarm severity thresholds, Time display in GMT or Loacal time, Tool bar/Alarm flash. Window: Individual monitor configuration Help
The TNMS CT specific software package allows the creation of a graphical representation of the network such as a geographical arrangement of the NE symbols as an example. Each NE is represented on the GUI by an individual icon. The NE-specific Element Manager will be activated via mouse click on the NE symbol. It is possible to open more than one Element Manager application at the same time. To open a certain function or menu entry in this window, one of the Functional units or one of the equipment units (e.g. optical interface card) have to be selected via mouse click. All the now following actions apply to that selected functionality, e.g. inserted configuration data are for an optical interface card or the complete subrack, depending on the unit, selected before. All menu entries are selectable via pop up menu as well as pull down menu entry Symbol. Additionally, to give an overall view to the status of the NE, each of the NE Applications Main Windows contain a Network-Element-Information-Line, consisting of 6 display fields, indicating the following (left to right):
NE state indicator
data semaphore
Short help: Short help for the actual selected menu item. Alarm summary: Summary of the actual raised alarm severities of the NE.
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
Title:
page 12/24
18
18.04.08
NE report state: Indication, if maintenance mode is selected, which means that all faults will be suppressed for installation purposes. NE state: Indicator, if NE is active or idle. Access mode: Show, if the operator has read only or read/write access to the NE. See Security management. Data semaphore is green if no data transfer between TNMS CT and NE is running
3.1.2 Fault management The TNMS CT receives the messages of the equipment, concerning internal software or hardware problems and external problems. These alarm messages of the different network elements in the manageable network area are reported to the TNMS CT at each screen level. For each view, sub view, selected function or interface all associated faults will be displayed, which are concerned to the currently open view. This allows a very flexible and individual creation of different alarm tables for various functionalities. The functional view gives a quick summary about the actual alarm situation in relation to the traffic of the NE. You can zoom into the symbols to find the individual alarm that is responsible for a problem. Another way to get the actual alarm state is the alarm list. The alarm list shows all of the raised alarms with the related slot and the related traffic functionality. In the current alarm list the actual alarms are shown, in the history list the time of appearance and disappearance.
An alarm filter function provides the possibility to reduce the displayed number of the incoming alarms. An alarm can be suppressed (Menu Alarm Suppression). In case of alarm suppression an alarm will be detected in the NE, but not be sent to the TNMS CT. Each alarm has its own severity class. The alarm severity is show on all of the graphical user interfaces. The sum of alarms shows the colour of the highest severity of all active alarms.
Copyright Siemens AG 2003 TNMS CT Technical Description
Issue: Date: Ordering Nr./SNR All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
Title:
page 13/24
18
18.04.08
The Module View shows the status of interface cards. For selecting the required configuration on every slot position a menu can be opened with the possible card types. The status bar shows a comprehensive alarm overview with one LED symbol for each alarm severity. 3.1.3 Configuration Management 3.1.3.1 General The most configuration of the network element is done via the Modul View Window. By right klicking on one of the symbols, the context menu displays a configuration menu. For each of the symbols an individual configuration window shows all of the parameters of this functionality and the actual state of the related network element.
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 14/24
18
18.04.08
This group provides a set of functions for provisioning and reconfiguring a network element (NE). This process can be done either by a complete manual process or by downloading the contents of a configuration file to the NE. Storing of the NE data in a configuration file on a data medium is also possible. The different configuration data, such as cross connections, alarm filters (e.g. suppression of LOF-, LOS - Alarms), performance thresholds (e.g. threshold for SES) timing, and synchronisation features will be inserted in tables or graphical views, depending on the unit, which shall be configured and the currently open view. 3.1.3.2 Configuration of crossconnection NE cross connections can be configured via the CC-symbol and the contex-sensitive menue (right-mouse button). The dialogue contains of two folders : one folder for the configuration of existing crossconnections and another folder for the creation of a new crossconnection.
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 15/24
18
18.04.08
If the crossconnect configuration window is activated, all related crossconnections will be displayed. With the Filter the list can be reduced to one of the possible directions (unidirectional, bi-directional, loopback, ...).
The configured connections will automatically be written in a table as shown in Figure 9. This table could also be used to manipulate connections by inserting the concerned parameters manually. The list can be stored in an ASCII-textfile. The creation of a cross connection is done in the Action tab. In the TP A, TP B, TP Bfield the sink and source and protection can be selected. The crossconnection list shows all existing crossconnections in dependence to the selected termination points. 3.1.3.3 Configuration of timing and synchronisation parameters Here is an example of the timing configuration with priority options. Furthermore this view gives information about the currently active source for T0 and T4. Corresponding interfaces/slots and switching criteria for the different sources (including minimum allowable SSM quality level) has to be selected before.
Copyright Siemens AG 2003 TNMS CT Technical Description
Issue: Date: Ordering Nr./SNR All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
Title:
page 16/24
18
18.04.08
3.1.4 Performance management The performance functions allow a display of performance data as recorded and stored by the managed NEs, based on ITU-T recommendation G.826. Depending on the currently chosen view, 24 hours performance values, 15 min. performance values and current performance values are shown on the GUI on demand. Any degradation of the signal quality in the network will be identified (depending on the configured thresholds), allowing preventive maintenance. For this purpose the optical components of the line side are also monitored (e.g. output power of the transmitter card, received signal power on the receiver card).
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 17/24
18
18.04.08
3.1.5 Security Management To protect against unauthorised access or incorrect operator inputs, procedures are provided for checking the user's access authorisation. Access checking is performed automatically, when the TNMS CT is started. To protect against unauthorised access or incorrect operator inputs, procedures are provided for checking the user's access authorisation. TNMS CT supports five different user classes. Each user has his own login into the TNMS combined with an user class. The following five user classes are provided by the system: Maintenance Provides acces to Fault Management and allows the starting of an EM in a read only mode. Provides acces to Fault Management Full system acces
Operation Adminsitrator
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 18/24
18
18.04.08
3.2 Maintenance
Suppression of all spontaneous faults, for maintenance and installation purposes, is possible via menu maintenance/operation, included in the popup menu of the Functional Unit. Additionally, there is a set of different functions to support maintenance and test purposes depending on the network element. Some examples are listed below: Laser restart (2s, 90s) Display equipping possibilities per slot Backup of NE software NE Time Software download to each card and NE controller List of HW, FW release of each card and customer specific data - including correlation check between software/firmware and hardware. Interrelation between Functional Units/Group and cards in FV and vice versa in MV Display of connector allocation at the Line Termination Unit of the equipment (fixed) and at the connected Distribution Frame (configurable). Configuration/assignment of monitor points
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 19/24
18
18.04.08
3.3 Help
The 'Help' function offers a comprehensive help text, similar to use as known from the MS Windows Help function. Some examples about the containing information are given below: the structure of the user interface the use and function of a window the menu structure selecting menu titles and menu options all menu items in the form of a brief menu description
The user can browse the help text. The following example shows the help text for the window hierarchy of the SL16 NE application.
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 20/24
18
18.04.08
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 21/24
18
18.04.08
Notebook PC (Recommended HW for LCT Mode) Processor RAM Hard disk Floppy disk drive CD ROM Graphics Pentium 4 1,6 GHz 512 MB
Minitower PC (Recommended HW for NCT Mode) Pentium 4 1,8 GHz 1 GB 20 GB Ultra DMA-100 3.5" / 1.44 MB 48x ATAPI Matrox Millenium G450 16 MB, DH/DVI 19 SCENICVIEW LAN RJ-45 V24/RS232 Microsoft serial mouse or compatible
20 GB E-Serie 3.5" / 1.44 MB - external 24x E-Serie ATI Mobility-Radeon 7500 with 32 MB Video RAM LCD 14.1 TFT XGA Modem /LAN E-Serie V24/RS232 Microsoft serial mouse or compatible
GUI Interfaces card for Remote access Interfaces card for local access Pointer device
A printer can be connected to the PC via the parallel or USB interface for documentation. The TNMS CT software is released only for the official TNMS CT hardware supplied by Siemens. Due to the rapid changes of PC hardware an equal or better follow up model may be delivered.
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 22/24
18
18.04.08
5 Upgrade Startegy
5.1 Upgrade procedure of old Unigate LCT/NCT into TNMS CT
the following possibilities are available : Upgrade Unigate LCT into TNMS CT (LCT Mode) Upgrade Unigate NCT into TNMS CT (NCT Mode) Upgrade TNMS CT (LCT Mode) Upgrade TNMS CT (NCT Mode)
For all above mentioned cases the Logs can be saved and exported in XML Format then via Import function can be used in TNMS CT.
6 Abbreviations
DCC FCAPS FV FW GUI HW ITU-T ISO NE LCT MB MV NCT OSI Data Communication Channel Management Functions acc. to ISO: Performance-, Security Management Functional View Firmware Graphical User Interface Hardware International Telecommunication Union Transmission (former CCITT) International Standard Organisation Network Element Local Craft Terminal Mega Byte Modul View Network Craft Terminal Open System Interconnection
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
Fault-,
Configuration-,
Account-,
Title:
page 23/24
18
18.04.08
Synchronous Line Equipment Synchronous Line Regenerator Synchronous Multiplexer Add Drop Multi Wavelength Line System Termination Point TNMS Craft Terminal Video Graphics Adapter Synchronisation Source Marker Next Generation Network elements
Title:
All Rights Reserved File: TNMS CT_110607.doc Author: Reza Azimi COO_OBS_EO_PMC
page 24/24
18
18.04.08