218563595-TNMS-CT-Technical-Description-Apr-08.pdf

Managementfor SDH/WDM Networks TNMS CT Technical Description V1.0/2.0/3.0 TNMS CRAFT TERMINAL This publication provides outline information only which (unless agreed by Company in writing) may not be used, applied or reproduced for any purpose or form part of any order or contract to be regarded as a representation relating to the products or services concerned. The Company reserves the right to alter without notice the specification, design, price or conditions of supply of any product or service. NOTE: This description is related to the presently implemented and planned functionality. Therefore not all features described here are implemented in every version. © Copyright NokiaSiemensNetworks AG 2007 All Rights Reserved TNMS CT Technical Description V1.0/2.0/3.0 Title: File: TNMS-CT_180208.doc Issue: Date: Ordering Nr./SNR Author: Reza Azimi page 1/24 18 18.04.08 COO_OBS_EO_PMC 1 INTRODUCTION 4 2 TNMS CT 5 2.1 NCT/LCT mode 5 2.1.1 NCT mode 5 2.1.2 LCT mode 5 2.2 Graphical User Interface 6 2.3 Fault Management 7 2.4 Security Management 9 2.5 Remote access to Networks via Client/Server architecture 9 2.6 External Application Interfaces 9 2.7 Topology Discovery 9 3 ELEMENT MANAGER OF TNMS CT 11 3.1 Operational concept 11 3.1.1 Graphical user Interface 11 3.1.2 Fault management 13 3.1.3 Configuration Management 14 3.1.3.1 General 14 3.1.3.2 Configuration of crossconnection 15 3.1.3.3 Configuration of timing and synchronisation parameters 16 3.1.4 Performance management 17 3.1.5 Security Management 18 3.2 Maintenance 19 3.3 Help 20 3.4 SURPASS hiT 70xx series 21 3.4.1 Subequipped Cards 21 3.4.2 GFP support 21 3.4.3 Plug & Play 21 4 TNMS CT PLATFORM AND ARCHITECTURE 22 4.1 HW Platform 22 4.2 Operating system 23 5 UPGRADE STARTEGY 23 5.1 Upgrade procedure of old Unigate LCT/NCT into TNMS CT 23 © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.doc Issue: Date: Ordering Nr./SNR Author: Reza Azimi page 2/24 18 18.04.08 COO_OBS_EO_PMC .............. 14 Figure 8: Module view in Element Manager....doc Issue: Date: Ordering Nr.....................................04.................................................................6 ABBREVIATIONS 23 Table of Figures: Figure 1: TNMS CT GUI..................................................................................................................................................................................................................................../SNR Author: Reza Azimi page 3/24 18 18... 8 Figure 3:Alarm statistic in TNMS CT ............ 6 Figure 2: Alarm list in TNMS CT GUI . 15 Figure 9: Cross Connection view in Element Manager ........................................................ 18 Figure 12: Help view of Element manager ............................................................................. 13 Figure 7: Traffic View in Element Manager................................08 COO_OBS_EO_PMC ................................... 16 Figure 10: Configuration of Timing & Synchronization parameters in element Manager........................... 11 Figure 5: NE Info........ Line.................................................................................................................................................................................................................. 17 Figure 11: Performance management view in Element Manager .................................... 8 Figure 4: Element Manager GUI............... 12 Figure 6: Alarm list/attributes view in Element manager .......................... 20 © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607............................................... 24.1 Introduction The TNMS CT (TNMS Craft Terminal) is an element management system for Next Generation SDH (SURPASS hiT 70xx series). 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. Administration and Maintenance (OAM) PC software. It is possible to open more than one NE application at the same time. administration and Provisoning of NEs.6/19. Complete range of SDH-Legacy NEs (SMA1/4/16. the “NE application”. TNMS CT supports a Serial Line Interface for local operation (RS232/V. To manage networks with more than 150 Network Elements Siemens AG recommends to use the TNMS Core. The PC software has two parts : 1. TNMS has been conceived to manage the complete Siemens optical network portfolio.doc Issue: Date: Ordering Nr. The number of NEs to be managed in a SDH/WDM network is limited. DWDM family for backbone networks. Element Manager: Managed the network element specific functions./SNR Author: Reza Azimi page 4/24 18 18.04. feeder and metro networks. TNMS CT as Common part: for all common functions like fault management. This management system basically consists of a PC hardware (standard PC) and an Operation.) . SURPASS hiT 73xx & 75xx series. etc. which provides a high performance supervision and control tool using the internal supervision and control software implemented in the Network Elements. SIEMENS currently recommends a restriction to approximately 150 NEs. TNMS CT basically allows local as well as remote operation and control also there is the additional possibility to have a graphical network view. to ensure best performance and a clear representation of the network via the GUI. 2.08 COO_OBS_EO_PMC . © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. SL16/64.2 kbit/s) as well as remote operation via an Ethernet Interface. security. 9. concerning fault detection. 1./SNR Author: Reza Azimi page 5/24 18 18.08 COO_OBS_EO_PMC . © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. the NCT and LCT mode. (local or remote).2 LCT mode The LCT mode provides the service technician with a basic function access to one network element. 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.doc Issue: Date: Ordering Nr. however it is possible to • establish a connection to 50 Network Elements.1 NCT/LCT mode TNMS CT supports two different application modes.2 TNMS CT 2.1. • Network Alarm list or Network Alarm logs are not supported.1 NCT mode The NCT mode supports the daily work of a service technician in a software tool optimized way. 2. LCT-Mode feature can be described as following : • Elementary requirements in order to commissioning of a NE. The differences abouts the modes are characterised in the next chapter. TNMS CT is able to manage 150 NE at the same time without restriction of the Network topology complexity. the Client login capability is supported. • One Client and one Server on the same PC. LCT mode has the following restrictions: • Only three Element Managers can be opened simultaneously.04. • Remote login is not supported. As comparison with NCT mode . • Based on Client Server architecture. 2. • Network Alarm list or Network Alarm logs are supported. Menu titles and menu options./SNR Author: Reza Azimi page 6/24 18 18. which are frequently used.doc Issue: Date: Ordering Nr. can also be selected via function keys. Figure 1: TNMS CT GUI Displayed menu items supports the following views: © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. It is possible to open more than one Element Manager application at the same time.04. All menus and actions.2. which can be activated via popup menu are also selectable via pull-down menu-titles. The operator is guided through the program by menus.08 COO_OBS_EO_PMC . Operator prompting and the design of the user interface conform to the specifications in the MS Windows Style Guide. Program control and command entry can be performed by means of the mouse and/or keyboard using pull-down menus and the deposition of popup menus. The NE-specific Element Manager will be activated via mouse click on the NE symbol.2 Graphical User Interface 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. activated via right mouse button click. Each NE is represented on the GUI by an individual icon. Furthermore the program offers mechanisms as filtering or sorting of information and offers support through help functions. He has no need to learn complex command syntax. Any fault in each NE of the connected Network will enlighten/flicker the NE-symbol of the TNMS CT GUI . concerning internal software or hardware problems and external problems such as input failures from each NE in the connected network. In all other views the NE- symbol will be enlightened in the same way in each open NE application. ….doc Issue: Date: Ordering Nr.08 COO_OBS_EO_PMC . • Fault: Display alarm lists. in each view. if any NE of the network signalises a failure. In the Network view the icon of the faulty NE or NEs will change its colour. alarm request • Configuration: Creation and activation of all possible configurations in the different functional levels • Security • Window: Individual monitor configuration • Help 2.04. • File: For external communication such as print • View: search NE. depending on their severity and an alarm table can be opened. Fault messages & notification of the Network are received and appears automatically from NEs.3 Fault Management The TNMS CT receives messages of the equipment. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. which will show the number of currently existing faults in the network./SNR Author: Reza Azimi page 7/24 18 18. Alarm reception is also possible in any view. for each NE. Alarm acknowledge. System message log. 08 COO_OBS_EO_PMC ./SNR Author: Reza Azimi page 8/24 18 18.04. Figure 2: Alarm list in TNMS CT GUI Figure 3:Alarm statistic in TNMS CT © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.doc Issue: Date: Ordering Nr. background settings.7 Topology Discovery Using the TNMS CT (NCT mode) it is possible to discover the topology information out of the network elements and display the network topology (Hint: Qd2 NEs do not support this © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. Maintenance Provides acces to Fault Management and allows the starting of an EM in a read only mode. TNMS CT uses the same schema file as TNMS Core. DCN Channels and etc. To protect against unauthorised access or incorrect operator inputs.6 External Application Interfaces The TNMS CT can save the network configuration (network element addresses. Each user has his own login into the TNMS combined with an user class. Configuration like opeartion Broad cast NE User Configuration Adminsitrator Full system access Additional security functions are provided by Windows 2000.08 COO_OBS_EO_PMC . links. 2. In NCT mode the Server can be run on a different computer as the Client (in LCT mode both should be installed in common HW) and is connected over a separate network card to the DCN Network. 2.doc Issue: Date: Ordering Nr. Access checking is performed automatically. The XML interface is equal to the XML Interface of TNMS Core./SNR Author: Reza Azimi page 9/24 18 18.4 Security Management To protect against unauthorised access or incorrect operator inputs. The following five user classes are provided by the system: Supervison Provides only acces to the Fault Managment. procedures are provided for checking the user's access authorisation.) into XML format which can be exported to other devices. TNMS CT supports five different user classes. With this function the upgrade process of TNMS CT to TNMS Core can be realized easily. symbol positions.04.5 Remote access to Networks via Client/Server architecture The TNMS CT supports a remote login from an external computer via TCP/IP using Client/Server architecture. 2. however only a subset of XML data are supported by TNMS CT. Operation Provides acces to Fault Management and allows the starting of an EM. when the TNMS CT is started.2. A second network card. procedures are provided for checking the user's access authorisation. which is connected to an internal company network or the Internet (over a firewall) provides the TCP/IP connection to the Client. /SNR Author: Reza Azimi page 10/24 18 18. Only one configured network element inside the DCN Management is enough to start the port connection and neighbor NE discovery process. The client GUI displays the topology information at the network view. SLR).doc Issue: Date: Ordering Nr.function e.g.04. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. 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. SMA1k. SMA.08 COO_OBS_EO_PMC . 08 COO_OBS_EO_PMC . can also be selected via function keys.1 Operational concept 3. The Module View represents the configuration of the Equipment. The operator is guided through the program by menus. All menus and actions. The entrance point of the Element Manager GUI is the Module View window. Furthermore the program offers mechanisms as filtering or sorting of information and offers support through help functions.04. which can be activated via popup menu are also selectable via pull-down menu-titles. All views will be displayed at the same time on demand. Operator prompting and the design of the user interface conform to the specifications in the MS Windows Style Guide. activated via right mouse button click to a Functional Unit/Group/Subgroup or Hardware Module. He has no need to learn complex command syntax.1. Figure 4: Element Manager GUI © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.1 Graphical user Interface Program control and command entry can be performed by means of the mouse and/or keyboard using pull-down menus and the deposition of popup menus. illustrated below. Menu titles and menu options.3 Element Manager of TNMS CT 3./SNR Author: Reza Azimi page 11/24 18 18. Sub views are selectable via pop up and pull down menus.doc Issue: Date: Ordering Nr. which are frequently used. doc Issue: Date: Ordering Nr. Active.g. inserted configuration data are for an optical interface card or the complete subrack. 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. one of the Functional units or one of the equipment units (e. to give an overall view to the status of the NE. Each NE is represented on the GUI by an individual icon. set to Idle. Alarm acknowledge. Line • Short help: Short help for the actual selected menu item. optical interface card) have to be selected via mouse click. • NE-State: for maintenance reasons. System message log. e.04. each of the NE Applications Main Windows contain a Network-Element-Information-Line. depending on the unit./SNR Author: Reza Azimi page 12/24 18 18. All menu entries are selectable via pop up menu as well as pull down menu entry Symbol.Displayed menu items supports the following views: • File: For external communication such as print and hard copy • View: search NE. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. To open a certain function or menu entry in this window. • Alarm summary: Summary of the actual raised alarm severities of the NE. Additionally. indicating the following (left to right): short help alarm NE NE access data message output summary report state state mode semaphore indicator indicator indicator indicator Figure 5: NE Info. 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. Tool bar/Alarm flash. Time display in GMT or Loacal time.08 COO_OBS_EO_PMC .g. …. consisting of 6 display fields. • 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. All the now following actions apply to that selected functionality. alarm request. maintenance or Operation • Fault: Display alarm lists. selected before. sub view. Each alarm has its own severity class.1. In the current alarm list the actual alarms are shown. • Access mode: Show. • NE report state: Indication. selected function or interface all associated faults will be displayed. which are concerned to the currently open view. if NE is active or idle. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. Another way to get the actual alarm state is the alarm list.08 COO_OBS_EO_PMC . in the history list the time of appearance and disappearance. These alarm messages of the different network elements in the manageable network area are reported to the TNMS CT at each screen level. if the operator has read only or read/write access to the NE. if maintenance mode is selected. Figure 6: Alarm list/attributes view in Element manager An alarm filter function provides the possibility to reduce the displayed number of the incoming alarms. For each view. The sum of alarms shows the colour of the highest severity of all active alarms. In case of alarm suppression an alarm will be detected in the NE.doc Issue: Date: Ordering Nr. An alarm can be suppressed (Menu Alarm Suppression).2 Fault management The TNMS CT receives the messages of the equipment. The alarm severity is show on all of the graphical user interfaces. which means that all faults will be suppressed for installation purposes./SNR Author: Reza Azimi page 13/24 18 18. • NE state: Indicator. • Data semaphore is green if no data transfer between TNMS CT and NE is running 3. The alarm list shows all of the raised alarms with the related slot and the related traffic functionality. but not be sent to the TNMS CT. concerning internal software or hardware problems and external problems. The functional view gives a quick summary about the actual alarm situation in relation to the traffic of the NE. See “Security management”. You can “zoom” into the symbols to find the individual alarm that is responsible for a problem. This allows a very flexible and individual creation of different alarm tables for various functionalities.04. 08 COO_OBS_EO_PMC .04. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.doc Issue: Date: Ordering Nr.1. The status bar shows a comprehensive alarm overview with one LED symbol for each alarm severity. 3. the context menu displays a configuration menu.1 General The most configuration of the network element is done via the Modul View Window.1.3 Configuration Management 3./SNR Author: Reza Azimi page 14/24 18 18. 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. Figure 7: Traffic View in Element Manager The Module View shows the status of interface cards.3. For selecting the required configuration on every slot position a menu can be opened with the possible card types. By right klicking on one of the symbols. This process can be done either by a complete manual process or by downloading the contents of a configuration file to the NE. 3. The different configuration data.g. threshold for SES) timing. and synchronisation features will be inserted in tables or graphical views.doc Issue: Date: Ordering Nr.08 COO_OBS_EO_PMC . Figure 8: Module view in Element Manager This group provides a set of functions for provisioning and reconfiguring a network element (NE).2 Configuration of crossconnection NE cross connections can be configured via the CC-symbol and the contex-sensitive menue (right-mouse button). alarm filters (e. depending on the unit. such as cross connections. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. performance thresholds (e./SNR Author: Reza Azimi page 15/24 18 18.1. The dialogue contains of two folders : one folder for the configuration of existing crossconnections and another folder for the creation of a new crossconnection. suppression of LOF-.04. Storing of the NE data in a configuration file on a data medium is also possible.3. which shall be configured and the currently open view.Alarms). LOS .g. The creation of a cross connection is done in the “Action” tab. all related crossconnections will be displayed. The crossconnection list shows all existing crossconnections in dependence to the selected termination points. This table could also be used to manipulate connections by inserting the concerned parameters manually. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. Figure 9: Cross Connection view in Element Manager The configured connections will automatically be written in a table as shown in Figure 9. Corresponding interfaces/slots and switching criteria for the different sources (including minimum allowable SSM quality level) has to be selected before. With the Filter the list can be reduced to one of the possible directions (unidirectional.3. TP B´field the sink and source and protection can be selected. bi-directional.1.08 COO_OBS_EO_PMC . In the TP A. .If the crossconnect configuration window is activated. 3. The list can be stored in an ASCII-textfile../SNR Author: Reza Azimi page 16/24 18 18.04.).doc Issue: Date: Ordering Nr.3 Configuration of timing and synchronisation parameters Here is an example of the timing configuration with priority options. loopback.. TP B. Furthermore this view gives information about the currently active source for T0 and T4. 826. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. For this purpose the optical components of the line side are also monitored (e.g. allowing preventive maintenance.04. received signal power on the receiver card).4 Performance management The performance functions allow a display of performance data as recorded and stored by the managed NEs.doc Issue: Date: Ordering Nr.1. based on ITU-T recommendation G. Depending on the currently chosen view.08 COO_OBS_EO_PMC . 24 hours performance values. Any degradation of the signal quality in the network will be identified (depending on the configured thresholds). Figure 10: Configuration of Timing & Synchronization parameters in element Manager 3. 15 min./SNR Author: Reza Azimi page 17/24 18 18. performance values and current performance values are shown on the GUI on demand. output power of the transmitter card. 04. procedures are provided for checking the user's access authorisation.1.doc Issue: Date: Ordering Nr. TNMS CT supports five different user classes.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. Operation Provides acces to Fault Management Adminsitrator Full system acces Additional security functions are provided by Windows 2000. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. Each user has his own login into the TNMS combined with an user class./SNR Author: Reza Azimi page 18/24 18 18. To protect against unauthorised access or incorrect operator inputs.08 COO_OBS_EO_PMC . 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. Figure 11: Performance management view in Element Manager 3. when the TNMS CT is started. doc Issue: Date: Ordering Nr. FW release of each card and customer specific data .04./SNR Author: Reza Azimi page 19/24 18 18. included in the popup menu of the Functional Unit.2 Maintenance Suppression of all spontaneous faults. Additionally.including correlation check between software/firmware and hardware. • Configuration/assignment of monitor points © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607. there is a set of different functions to support maintenance and test purposes depending on the network element.08 COO_OBS_EO_PMC . for maintenance and installation purposes. • 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). Some examples are listed below: • Laser restart (2s. is possible via menu maintenance/operation. 90s) • Display equipping possibilities per slot • Backup of NE software • NE Time • Software download to each card and NE controller • List of HW.3. 3./SNR Author: Reza Azimi page 20/24 18 18.08 COO_OBS_EO_PMC . similar to use as known from the MS Windows Help function.doc Issue: Date: Ordering Nr. Figure 12: Help view of Element manager © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.3 Help The 'Help' function offers a comprehensive help text.04. 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. 0 TNMS CT supports SURPASS hiT 7070 DC Rel. SC Rel.2 GFP support Using the Element Manager of the SURPASS hiT 7070 & 7050 the Ethernetports are configureable and GFP assignment (bandwith allocation) in steps of 1MBit/s is supported.4 SURPASS hiT 70xx series From Version 2.3 Plug & Play The target of this feature is to reduce the installation and the commissioning time.4.0. 3.4.0 Including the following highlights : 3.3. The default value of the network elements slots are "auto mode". 3.4./SNR Author: Reza Azimi page 21/24 18 18.0 & SURPASS hiT 7050 FP1 Rel 1. 1. and investment in costly optical interfaces (that will eventually never be used) can be avoided. As soon as a card is configured into the network element. This way the initial costs will be reduced.08 COO_OBS_EO_PMC .1 Subequipped Cards The network elements of the SURPASS hiT 7070 & 7050 product family have interface cards of which the optical interfaces (ports) may not be fully equipped at the time installation.doc Issue: Date: Ordering Nr. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.04. 1. the card is automatically detected and displayed inside the Module View. The following table lists the recommended configuration for that PC.44 MB .8 GHz RAM 512 MB * 1 GB Hard disk 20 GB E-Serie 20 GB Ultra DMA-100 Floppy disk drive 3.doc Issue: Date: Ordering Nr.6 GHz Pentium 4 1. The TNMS CT software is released only for the official TNMS CT hardware supplied by Siemens.4 TNMS CT Platform and Architecture 4.44 MB CD ROM 24x E-Serie 48x ATAPI Graphics ATI Mobility-Radeon 7500 Matrox Millenium G450 with 32 MB Video RAM 16 MB. DH/DVI GUI LCD 14. Of RAM has the following affects: With 256MB: 1 LCT can be managed With 512MB: 4 LCTs and With 1GB: 9 LCTs are possible to be managed.external 3.1 HW Platform The TNMS CT is installed on compatible PC. Due to the rapid changes of PC hardware an equal or better follow up model may be delivered. *) Qnty.1” TFT XGA 19” SCENICVIEW Interfaces card for Modem /LAN E-Serie LAN RJ-45 Remote access Interfaces card for local V24/RS232 V24/RS232 access Pointer device Microsoft serial mouse or Microsoft serial mouse or compatible compatible A printer can be connected to the PC via the parallel or USB interface for documentation.5" / 1. Recommended Configuration: Notebook PC Minitower PC (Recommended HW for (Recommended HW for LCT Mode) NCT Mode) Processor Pentium 4 1./SNR Author: Reza Azimi page 22/24 18 18.5" / 1. © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.04.08 COO_OBS_EO_PMC . /SNR Author: Reza Azimi page 23/24 18 18.doc Issue: Date: Ordering Nr. Configuration-.2 Operating system TNMS CT can be used within two following operation systems: a) MS-Windows 2000 Professional Service Pack 4 (English) and Internet Explorer 6. Security Management FV Functional View FW Firmware GUI Graphical User Interface HW Hardware ITU-T International Telecommunication Union – Transmission (former CCITT) ISO International Standard Organisation NE Network Element LCT Local Craft Terminal MB Mega Byte MV Modul View NCT Network Craft Terminal OSI Open System Interconnection © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.4. 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.08 COO_OBS_EO_PMC . 6 Abbreviations DCC Data Communication Channel FCAPS Management Functions acc. to ISO: Fault-. Account-. Performance-.04. b) MS-Windows XP Professional Service Pack 2 (English). doc Issue: Date: Ordering Nr.SL Synchronous Line Equipment SLR Synchronous Line Regenerator SMA Synchronous Multiplexer Add Drop WL Multi – Wavelength Line System TP Termination Point TNMS CT TNMS Craft Terminal VGA Video Graphics Adapter SSM Synchronisation Source Marker SURPASS hiT Next Generation Network elements © Copyright Siemens AG 2003 All Rights Reserved TNMS CT Technical Description Title: File: TNMS CT_110607.08 COO_OBS_EO_PMC ./SNR Author: Reza Azimi page 24/24 18 18.04.