GCSR4.2 User Manual

General Communication ServiceGCS R4.2User ManualC33596.23DN011794 Nokia Networks Oy 1 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the

use of Nokia Networks' customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia Networks. The document has beenprepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia Networks welcomes customer comments aspart of the process of continuous development and improvement of the documentation.The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia Networks and the customer.However, Nokia Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaNetworks will, if necessary, explain issues which may not be covered by the document.Nokia Networks' liability for any errors in the document is limited to the documentary correctionof errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS INTHIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this document or theinformation in it.This document and the product it describes are considered protected by copyright according tothe applicable laws.NOKIA logo is a registered trademark of Nokia Corporation.Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Networks Oy 2001. All rights reserved.2 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

ContentsContents 3

List of tables 6

List of figures 7

1 About this manual 111.1 Typographic conventions 11

2 Introduction to General Communication Service GCS R4.2 132.1 Features 132.2 Architecture 152.3 Compatibility with earlier versions 17

3 Installing GCS 193.1 Prerequisites for installing GCS 193.2 Installing GCS 203.3 Prerequisites for uninstalling GCS 233.4 Uninstalling GCS 23

4 Defining connections to nodes 254.1 Introduction to Nokia Connection Tool 254.2 Security 264.3 Starting Nokia Connection Tool 274.4 Connecting to nodes with Nokia Connection Tool 304.5 Main functions of Nokia Connection Tool 314.5.1 Defining connections 314.5.2 Defining nodes 364.5.3 Viewing connections and nodes 394.5.4 Scanning for network equipment (nodes) 414.6 Connection types 494.6.1 Serial Port Connection 504.6.2 Modem Connection 514.6.3 Network Connection 514.6.4 Telnet Connection 524.6.5 Nokia Q1 Pipe Connection 524.6.6 BSC Connection 534.6.7 BTS Connection 544.6.8 Nokia MF C1.0 Connection 544.6.9 TMS4 Serial Connection 554.6.10 TMS4 Modem Connection 554.6.11 TMS4 Telnet Connection 564.6.12 RCM Macro TMS4 Serial Port Connection 574.6.13 RCM Macro TMS4 Modem Connection 574.6.14 RCM Macro TMS4 Telnet Connection 584.6.15 RCM Macro Nokia MF C1.0 Network Connection 584.6.16 SNMP Connection 594.7 Node properties 59DN011794 Nokia Networks Oy 3 (112)Issue 1-0 en Nokia Proprietary and Confidential


4.7.1 Q1 Node 594.7.2 MML node 60

4.7.3 SNMP node 604.8 Configuring modems 614.8.1 Prerequisites for the computer containing GCS 614.8.2 Physical configuration 614.8.3 Modem B sample settings 62

5 GCS Database 655.1 Introduction to the GCS database 655.2 Maintenance 665.2.1 Compacting the GCS Database 66

6 GCS Remote Database Update 696.1 Introduction to GCS Remote Database Update 696.2 Installing GCS Remote Database Update 696.3 Configuring GCS Remote Database Update 70

7 GCS troubleshooting 757.1 Operating GCS 757.2 Known problems 76

Appendix A. Connection parameters 79A.1 Common connection parameters 79A.2 Serial Port Connection 80A.3 Modem Connection 81A.4 Network Connection 81A.5 Telnet Connection 82A.6 Nokia Q1 Pipe Connection 83A.7 BSC Connection 84A.8 BTS Connection 86A.9 Nokia MF C1.0 Connection 89A.10 TMS4 Serial Connection 91A.11 TMS4 Modem Connection 92A.12 TMS4 Telnet Connection 93A.13 RCM Macro TMS4 Serial Port Connection 95A.14 RCM Macro TMS4 Modem Connection 96A.15 RCM Macro TMS4 Telnet Connection 97A.16 RCM Macro Nokia MF C1.0 Network Connection 99A.17 SNMP Connection 100

Appendix B. Node parameters 101B.1 Q1 Node 101B.2 FE Parameters 102B.3 MML node 103B.4 SNMP node 103

Appendix C. Keyboard support for Nokia Connection Tool 104C.1 Connection tree 104C.2 Connection Properties dialog box 105C.3 Node tree 1064 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

C.4 Node Properties dialog box 107Glossary 111DN011794 Nokia Networks Oy 5 (112)Issue 1-0 en Nokia Proprietary and Confidential


List of tablesTable 1. Typographic conventions 12Table 2. Earlier GCS versions 17Table 3. Actions permitted for the NMS/10 user groups 26Table 4. Old and new connection names 50Table 5. Functionality of the Q1 Node 60Table 6. Modem B: DTE settings 62Table 7. Modem B: auxiliary settings 63Table 8. Modem B: other settings 636 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

List of figuresFigure 1. Example of connections provided by GCS 14Figure 2. Functional components of GCS 15Figure 3. Local management with GCS R4.2 16Figure 4. Remote management with GCS R4.2 16Figure 5. Nokia Connection Tool started from Windows Start menu 28Figure 6. Nokia Connection Tool started from a node manager application 29Figure 7. Connection Properties for a new connection 33Figure 8. Connection Properties with all parameters visible 34Figure 9. Properties dialog box for Network Connection Parameters 35Figure 10. Node Properties dialog box 38Figure 11. Manager Info dialog box 38Figure 12. Nokia Connection Tool, Database tab 40Figure 13. Scan dialog box 43Figure 14. Scan dialog box with Show List button enabled 44Figure 15. Scan: Found Buses dialogd box 45Figure 16. Save Node dialog box 46Figure 17. Scan Results: Save All dialog box 47Figure 18. Scan Results Selection for Database Saving dialog box 48Figure 19. Rename Node dialog box 48Figure 20. Serial Port Connection 51Figure 21. Modem Connection 51Figure 22. Network Connection 51Figure 23. Telnet Connection 52Figure 24. Nokia Q1 Pipe Connection 53Figure 25. BSC Connection via NMS/2000 53Figure 26. BTS Connection 54Figure 27. Nokia MF C1.0 Connection 55Figure 28. TMS4 Serial Connection 55Figure 29. TMS4 Modem Connection 56DN011794 Nokia Networks Oy 7 (112)Issue 1-0 en Nokia Proprietary and Confidential


Figure 30. TMS4 Telnet Connection 56

Figure 31. RCM Macro TMS4 Serial Port Connection 57Figure 32. RCM Macro TMS4 Modem Connection 57Figure 33. RCM Macro TMS4 Telnet Connection 58Figure 34. RCM Macro Nokia MF C1.0 Network Connection 58Figure 35. SNMP Connection 59Figure 36. Physical connection of modems 61Figure 37. Example of GCS Remote Database Update Allowed Clients key 71Figure 38. Modifying GCS Remote Database Update settings 728 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Summary of changesIn this release

This section lists the changes between GCS R4.1 and GCS R4.2 User Manual:

GCS R4.2 supports Windows 2000 operating system.

A new document numbering scheme has been adopted: C33596002SE_00/09 Mar 2000 has been replaced with DN011794 Issue 1-0 en

Partly new typographic conventions have been adopted in this document(Section 1.1).

A new chapter 2, Introduction to General Communication Service GCSR4.2 has been added. It gives general information about GCS R4.2.

Installing instructions are in chapter 3 and they have been completelyupdated.

The old chapter 3, Defining connections to nodes is now chapter 4 and ithas been corrected and restructured. Some connection names have beenchanged. A table of the old and new connection names is included insection 4.5, Connection types.

Section 3.4 Keyboard support has been moved to a new Appendix C,Keyboard support for Nokia Connection Tool.

From the old section 3.6 Connection types, the parameter tables have beencorrected and moved to a new Appendix A, Connection parameters.

The tables from section 3.7 have been corrected and moved to a newAppendix B, Node parameters.

The old section 3.9 Troubleshooting has been moved to new chapter 7.Chapter 7, GCS troubleshooting contains also completely newinformation.

A new chapter 5, GCS Database has been added.

Interface Synchronization has been renamed GCS Remote DatabaseUpdate. Therefore the old chapter 4, GCS Interface Syncronization Servicehas been replaced with chapter 6, GCS Remote Database Update

A short glossary has been included in the document.

O&M node has been replaced with the name MML node which betterdecribes the domain where this name is applicable.DN011794 Nokia Networks Oy 9 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.210 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

About this manual1 About this manualThis manual is intended for users of Nokia agents, alarm managers, and nodemanagers that use connectivity and database services of General CommunicationService GCS R4.2. GCS R4.2 provides these services to those applications thatuse Nokia Q1 and MML protocols. The manual covers all information needed toinstall and use GCS R4.2 with Nokia network elements.

This User Manual covers the following topics:

Chapter 2, Introduction to General Communication Service GCS R4.2

Chapter 3, Installing GCS

Chapter 4, Defining connections to nodes

Chapter 5, GCS Database

Chapter 6, GCS Remote Database Update

Chapter 7, GCS troubleshooting

Appendix A, Connection parameters

Appendix B, Node parameters

Appendix C, Keyboard support for Nokia Connection Tool

1.1 Typographic conventions

The table below presents the conventions that are used in this User Manual:DN011794 Nokia Networks Oy 11 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Table 1. Typographic conventions

Convention Explanation

Initial Upper Case Names of applications, windows and dialogs.

Italic Emphasis or referenced document titles.

Courier System output, user input, user names, file anddirectory names, database table names and counters

UPPER CASE Keys on the keyboard

Click File Exit Select Exit from the File menu

Variable user input

[text in brackets] Optional information in a command12 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Introduction to General Communication Service GCS R4.22 Introduction to General CommunicationService GCS R4.2

This chapter contains the following sections, which provide an overview ofGeneral Communication Service GCS R4.2 :

Section 2.1, Features

Section 2.2, Architecture

Section 2.3, Compatibility with earlier versions

2.1 Features

General Communication Service GCS R4.2 is a communication stack that is usedby Nokia agents, alarm managers, node managers and NMS/10 CommandScripting (RCM) to communicate with Nokia's PDH/Primary Rate networkelements. GCS R4.2 is also used by MML Alarm Manager to communicate withMML network elements.

GCS provides, for example, the following types of connections. For more aboutthe connections, see Section 4.6, Connection types.DN011794 Nokia Networks Oy 13 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 1. Example of connections provided by GCS

GCS R4.2 provides a uniform communication interface for all applications byhiding protocol differences and complexity of network topology. GCS uses theGCS Database and Nokia Connection Tool for node name and addressmanagement.

GCS R4.2 supports multi-user functionality in Windows NT Server, TerminalServer Edition (Node Manager Server).

Network Management Systems use GCS Remote Database Update to update theGCS Database. Node manager applications use this information when they makeconnection to the node.

NMS/2000 BTS

Modem

Telnetserver

TCP/IP

GSC Service

Modem

NE

TMS4

NE

NE

MF C1.0

NE

MF C2.0

NE

NE NE

NE

TP4

BSC

POTS14 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Introduction to General Communication Service GCS R4.2Figure 2. Functional components of GCS

2.2 Architecture

GCS R4.2 can be used in several different configurations:

Part of NMS/2000 (management of cellular networks) Part of NMS/100(0) (management of fixed transmission networks and

exchanges) Part of NMS/10 C4.x (small network management system) Part of NMS/10 C5.x (small network management system) Stand alone with node manager(s) (local management and commissioning)

GCSCommunication

Stack

to management network

NokiaConnection

ToolNode manager

NetworkManagement

System

Data storeGCS Database

GCS RemoteDatabase UpdateDN011794 Nokia Networks Oy 15 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 3. Local management with GCS R4.2

When GCS R4.2 is used as a stand-alone application, it is installed in a PC withthe required node manager software. Typically this kind of solution is used duringnetwork commissioning when new equipment is configured locally beforeconnecting it to transmission and management networks. Local management maybe needed also for diagnostics and troubleshooting purposes (see Figure 3).

Figure 4. Remote management with GCS R4.2

In remote management the architecture is more complicated: It consists of amanagement centre that contains GCS R4.2, some Node Management System,and mediator devices for providing access to management buses via LAN. Whenusing NMS/10, all these can be in the same PC or they can be distributed indifferent PCs which have distinct roles. When using NMS/2000/100(0) in a

Personal Computer (with GCS)

Q1 Network Element Laptop(with GCS)

Q1 Network Element

... OR ...

Workstation

Q1 Network Element

NMS/2000 NMS/10

Node Manager Server (with GCS)

Q1 MediatorBSC/BTS/TMS4/MF C1.0, MF C2.0 etc.

Local Area Network

Q1 Management bus16 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Introduction to General Communication Service GCS R4.2

UNIX server, there is always one PC (Node Manager Server on Windows NT 4.0Server, Terminal Server Edition) that contains GCS R4.2 and the required node

managers. Access to UNIX workstations is provided using Citrix Metaframewhich allows UNIX workstations to run an application that is located in a remoteNode Manager Server (see Figure 4).

2.3 Compatibility with earlier versions

GCS R4.2 is fully backwards compatible with the earlier versions of GCS andQ1CS. When an older GCS or Q1CS version is upgraded to GCS R4.2, all settingsand contents of the GCS Database are preserved. All node managers and otherapplications using GCS or Q1CS will work as they did with the earlier GCS orQ1CS version. The earlier versions are listed in the following table:

Table 2. Earlier GCS versions

Version Explanation

Q1CS V2 Q1 Communication Stack V2, a communicationstack for Q1 managed equipment. Used by 16-bit Windows 3.1 applications.

Q1CS R3.0 Q1 Communication Stack R3.0, successor toQ1CS V2. Communication stack for Q1managed equipment used with Windows NT 4.0and Windows 95 operating systems.

Q1CS R3.1 Q1 Communication Stack R3.1

GCS R4.0 General Communication Service R4.0,successor to Q1CS R3.1. A communicationstack for Q1 and MML managed equipment.

GCS R4.1 General Communication Service R4.1

GCS R4.2 The latest version of General CommunicationServiceDN011794 Nokia Networks Oy 17 (112)Issue 1-0 en Nokia Proprietary and Confidential

Installing GCS3 Installing GCSThis chapter describes how to install GCS on the hard disk of your computer. Itcovers the following topics:

Section 3.1, Prerequisites for installing GCS

Section 3.2, Installing GCS

Section 3.3, Prerequisites for uninstalling GCS

Section 3.4, Uninstalling GCS

3.1 Prerequisites for installing GCS

Prerequisites for installing GCS are:

You have the GCS R4.2 installation files available.

You have one of the following operating systems installed on the hard diskof your computer and you know how to use it.

GCS R4.2 is compatible with the following operating systems:

Windows 95 (OEM SR2 optional) Windows 98

Windows 98 Second Edition (SE) Windows Millenium Edition (ME) Windows NT Workstation 4.0 (with SP3 or newer)DN011794 Nokia Networks Oy 19 (112)Issue 1-0 en Nokia Proprietary and Confidential


Windows NT Server 4.0, Terminal Server Edition (with SP3 or newer)Note

Note

Windows 2000 Professional (SP1 is optional)

Windows 2000 Terminal Services are not supported by the first release of GCSR4.2.

Do not install GCS in a computer with dual-boot operating systems if they sharethe same disk where GCS is installed.

Microsoft Internet Explorer 3.02 or a later version is needed for viewing the Help.However, version 4.0 or later is recommended.

3.2 Installing GCS

The GCS software is supplied in several different ways. Depending on deliverymedia, the instructions and installation procedure of GCS can be slightlydifferent.

GCS supplied on NMS/10 SR CD-R

The GCS software is included in NMS/10 SR CD-R. See the instructions belowhow to install GCS from NMS/10 SR CD-R.

To install GCS from NMS/10 CD-R

1. Insert NMS/10 CD-R and wait for Autoplay to start the installation.

If Autorun is enabled, the NMS/10 Start page is shown.

2. Navigate to the Software section and select GCS under the Others section.

GCS supplied with node managers

Refer to the related node manager documentation for starting GCS installation.

Usually GCS installation is integrated within node manager installation andstarted automatically if required.20 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Installing GCS

GCS (Service Pack) downloaded from Nokia Intranet

GCS software can be downloaded from Nokia Intranet.

To install GCS from Nokia Intranet

1. Open GCS home page in the following URL:

http://apdweb.trs.ntc.nokia.com/tmn/development/platform/gcs/

2. Click the Download link in the navigation pane on the left.

The GCS R4.2 Download page opens.

3. Download the desired GCS release by clicking the related link to the .zipfile. The zip files are named GCSR42_NNN, where NNN is the GCS buildnumber.

The zip file is downloaded.

4. Save the downloaded file on your hard disk and unzip the file.

5. Double-click the setup.exe file to start GCS installation

6. Follow the on-screen instructions to continue.

Location of GCS

The default location for installing GCS is C:\Program Files\Nokia inWindows 2000 and C:\NokiaMgr in other operating systems.

If GCS is installed for the first time and there are no other GCS compatibleapplications installed, the default installation location can be changed duringinstallation. If GCS is already installed and/or there are other GCS compatibleapplications installed, GCS will be installed in the same location with theseapplications. In this case it is not possible to change the location.

When GCS is installed from a network drive, make sure that the drive is availableafter possible reboot. Otherwise setup cannot continue and it must be restartedmanually after reconnecting the network drive.

Sometimes installation order of network management products is significant. Toensure the correct order, install the latest GCS version once more after you haveinstalled all other products.

Read all documentation to find out possible installation or coexistence issues.DN011794 Nokia Networks Oy 21 (112)Issue 1-0 en Nokia Proprietary and Confidential


Upgrading GCSNoteRead the following before upgrading GCS:

You should take a backup copy of the GCS Database before upgrading. Forthe database location, see section 5.1, Introduction to the GCS database.

If you have upgraded GCS to a newer version, it is not possible to return tothe previous version without first uninstalling GCS. This means that thecurrent GCS Database contents are lost in downgrade. After downgradeyou can restore the GCS Database from a backup copy if it is available forthat GCS version.

When you upgrade GCS in Windows NT Server 4.0, Terminal ServerEdition, make sure that there are no active user sessions on. They mayprevent closing the GCS services and continuing the installation.

When GCS is upgraded, database conversion from an earlier version to theGCS Database R4.2 format may be needed. This is carried outautomatically during the GCS installation.

Database conversion from Q1CS V2 to GCS R4.2 is not performed inWindows 95/98 operating systems because of 16- and 32-bit ODBC (OpenDataBase Connectivity) problems. If you make an upgrade from Q1CS V2to GCS R4.2, the database will be empty.

Microsoft Data Access Components 2.1 SP2 (MDAC)GCS uses Microsoft Data Access Components for its ODBC connectivity. IfMDAC has to be installed or updated, the computer has to be restarted tocomplete the installation process. The GCS setup will continue automaticallyafter restart.

Additional support files for Windows 95

Winsock Version 2 run-time components for Windows 95 are needed for networkconnections to work. If only serial port connections are used, they can be installedlater when required. NMS/10 System Release CD-R on which GCS is suppliedcontains the \Accessories directory for all additional Windows 95 supportfiles.22 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Installing GCS

TP4 supportNote

GCS R4.2 is able to connect to BSC/BTS directly using OSI transport layerprotocol Transport Class 4/Connectionless Network Protocol (TP4/CLNP). Itprovides an OSI interface over a local area network (LAN). To install files forTP4 support, refer to TP4SETUP.HLP file in \Nokiamgr\SYSTEM32 for moreinformation.

TP4 support is not available for Windows 2000.

3.3 Prerequisites for uninstalling GCS

Prerequisites for uninstalling GCS R4.2 are:

The applications that use GCS have to be uninstalled first because theycannot work without GCS.

3.4 Uninstalling GCS

Use the Control Panels Add/Remove programs for uninstalling GCS. Follow theinstructions on the screen or the operating systems manuals. For example:

To uninstall GCS from Windows:

1. Open the Start menu and select SettingsControl Panel. Open Add/Remove Programs.

2. Select Nokia GCS R4 Communication Service (in Windows 2000 NokiaGCS General Communication Service R4.2) from the program list andclick Add/Remove....

3. To continue, follow the instructions on the screen.DN011794 Nokia Networks Oy 23 (112)Issue 1-0 en Nokia Proprietary and Confidential

Defining connections to nodes4 Defining connections to nodesThis chapter explains how to define connections to nodes with Nokia ConnectionTool.

This chapter covers the following topics:

Section 4.1, Introduction to Nokia Connection Tool

Section 4.2, Security

Section 4.3, Starting Nokia Connection Tool

Section 4.4, Connecting to nodes with Nokia Connection Tool

Section 4.5, Main functions of Nokia Connection Tool

Section 4.6, Connection types

Section 4.7, Node properties

Section 4.8, Configuring modems

4.1 Introduction to Nokia Connection Tool

Nokia Connection Tool allows you to make connection and node definitions foridentifying objects on a network, and save them permanently to the database.The information in the database is organised by connections and nodes. Theconnections must be defined first before any nodes can be saved within them.Each node in the database must have a designated connection type.

In addition to adding, modifying and deleting connection and node definitions,you can also scan network elements (nodes) with Nokia Connection Tool.Scanning network elements is available only for some connection typessupporting Nokia Q1 protocol.

You can use Nokia Connection Tool in standalone mode for databasemaintenance or open it from a node manager. When you start it from the nodemanager, you can select a node and establish a connection to it, for example, forcommissioning purposes.DN011794 Nokia Networks Oy 25 (112)Issue 1-0 en Nokia Proprietary and Confidential


The buttons displayed on the screen and their mode (enabled/disabled) dependson the Connection Tool mode. You can find examples of the displayed buttons inNote

Section 4.3, Starting Nokia Connection Tool. The keyboard shortcuts aredescribed in Appendix C, Keyboard support for Nokia Connection Tool.

4.2 Security

NMS/10 security features are supported when Nokia Connection Tool is run on acomputer which has the NMS/10 System Frame installed.

Nokia Connection Tool disables and enables save and search functions accordingto the custom user groups of NMS/10. The NMS/10 Operator user can onlyview saved connections and nodes, and the NMS/10 Basic user can search forthe network elements but is not allowed to save, whereas other types of users cancarry out all actions. See Table 3 for details.

Table 3. Actions permitted for the NMS/10 user groups

NMS/10 custom groups Standard NTgroups

Allowed actions NMS10Operator

NMS10Basic

NMS10Experienced

NMS10NetworkAdmin

Domain Admins,SystemAdministrators

Add and removeconnections andnodes

No No Yes Yes Yes

View propertiesof connectionsand nodes

Yes Yes Yes Yes Yes

Saveconnectionsand nodes

No No Yes Yes Yes

Search fornetwork elements

No Yes Yes Yes Yes26 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodes

4.3 Starting Nokia Connection ToolYou can start Nokia Connection Tool in two ways:

In standalone mode from Windows Start menu

In Connect to Node mode from a node manager application

To start Nokia Connection Tool in standalone mode:

Open the Start menu and select Programs Nokia Applications. OpenNokia Connection Tool.

In Windows 2000, select ProgramsNokia. Select GCS and open NokiaConnection Tool.

Nokia Connection Tool is displayed.DN011794 Nokia Networks Oy 27 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 5. Nokia Connection Tool started from Windows Start menu

To start Nokia Connection Tool from a node manager application:

Select Manage Connect... from the menu.

Nokia Connection Tool is displayed.28 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesNote

Note

Figure 6. Nokia Connection Tool started from a node managerapplication

If the GCS Database contains thousands of nodes, it may take a while beforeNokia Connection Tool is displayed when starting it.

You can see the version information of Nokia Connection Tool by clicking theAbout button.DN011794 Nokia Networks Oy 29 (112)Issue 1-0 en Nokia Proprietary and Confidential


NoteNote

There are different buttons on the right of the window depending on from whereNokia Connection Tool was started (from a node manager application orWindows).

You can close Nokia Connection Tool by clicking Exit.

4.4 Connecting to nodes with Nokia Connection Tool

You can start Nokia Connection Tool from a node manager application if youwish to make a connection to a node. For starting, see section 4.3, Starting NokiaConnection Tool.

After Nokia Connection Tool is displayed, there are two ways to connect to anode:

From the Direct tab that is displayed by default when Nokia ConnectionTool is started. The Direct tab enables to connect to a node that is not savedin the database.

From the Database tab. The Database tab enables you to connect to a nodethat is already in the database.

To connect to a node via the Direct tab:

When Nokia Connection Tool is displayed, it shows the Direct tab by default.

1. If the Direct tab is not selected, select it first.

2. Select the connection you wish to use in the Name combo box. Note thatthe connection type is shown below in the Type field.

3. In Node Parameters, select Q1 Node or MML Node depending on the nodetype you wish to make a connection to.

Node manager applications support usually only one node type. Find out the nodetype in advance before connecting to the node.30 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


4. In Node Parameters, fill in the appropriate parameters, for example, Q1Address for Q1 Node.5. Click Connect to open the connection.

Nokia Connection Tool is closed and the node manager application startsits own connection establishment phase. Usually it contains a progress baror similar indicator that shows how connection establishment advances.

To connect to a node via the Database tab:

1. If the Database tab is not selected, select it first.

2. Select the node you wish to connect to in the Nodes list.

3. Click Connect to open the connection.

Nokia Connection Tool is closed and the node manager application startsits own connection establishment phase. Usually it contains a progress baror similar indicator that shows how connection establishment advances.

Refer to the corresponding alarm or node managers user documentation fordetails on making connections.

4.5 Main functions of Nokia Connection Tool

This section covers the following topics:

Section 4.5.1, Defining connections

Section 4.5.2, Defining nodes

Section 4.5.3, Viewing connections and nodes

Section 4.5.4, Scanning for network equipment (nodes)

For details on the connection types and node properties, refer to sections 4.6,Connection types; 4.7, Node properties; Appendix A, Connection parameters andAppendix B, Node parameters.

4.5.1 Defining connections

With Nokia Connection Tool, you can define the following connections betweenthe management workstation and nodes:DN011794 Nokia Networks Oy 31 (112)Issue 1-0 en Nokia Proprietary and Confidential


Q1 connections (always to a Q1 bus containing zero, one or more networkelements) MML connections (to one network element) SNMP connections (currently not used by GCS)

To define a connection:

1. Select the Connections option button in the Database tab.

2. If you want to create a new connection, select the Connections line in theconnection list. If you want to copy an existing connection as a basis for thenew connection, select it in the list box.

3. Click Add....

4. The Connection Properties dialog box is displayed with the text NewConnection in the Name field (see Figure 7). If you selected an existingconnection, its properties are copied to this new connection.

5. Give a name to the connection in the Name field. The maximum length ofthe name is 32 characters. Single quotation marks are not allowed in thename.

6. If you are creating a new connection, select a proper connection type in theType combo box.

Each connection type has different parameters that are shown in theConnection Definition list box. Each line in the Connection Definition boxrepresents an interrelated set of parameters for the selected connectiontype. For details, refer to section 4.6, Connection types and Appendix A,Connection parameters.32 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesFigure 7. Connection Properties for a new connection

7. If you want to see a full list of parameters, click Show Parameters.

All parameters for the selected connection type are displayed in theConnection Definition list box.

Definitions that require a value are marked with an M (mandatory) in the M/D column in the Connection Definition list box.

Definitions with default parameter values are marked with a D (default) inthe M/D column in the Connection Definition list box. You do not need togive values to any of these parameters if the default values are suitable.DN011794 Nokia Networks Oy 33 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 8. Connection Properties with all parameters visible

8. Select each line in the Connection Definition list box and click theProperties button to modify it. The Properties dialog box is displayed (seeFigure 9).34 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesNote

Figure 9. Properties dialog box for Network Connection Parameters

9. Once you have selected an edit field, you can type in a value, scroll theparameter value with the keyboard up and down arrow keys, or select avalue in a list box. Use the SHIFT and UP/DOWN ARROW keys tonavigate between edit fields.

It is not possible to type in or select too small or large values.

Parameters marked with bold italic font (PORT and TSELECTION in Figure 9)are mutually exclusive, that is, you can only give value to one of them at the sametime.

10. If the connection requires a username and a password, give them accordingto the following rules:DN011794 Nokia Networks Oy 35 (112)Issue 1-0 en Nokia Proprietary and Confidential


The length of Username and Password can be up to 32 characters. Thestring ****** (6 *'s) is always shown in the Password field regardless ofNote

Note

the actual length of the password.

Only 7-bit US ASCII characters are recommended to be used in the username andpassword.

11. Click OK after you have entered the correct data.

12. Click Save to save the definitions to the database (disk).

4.5.2 Defining nodes

You can add new nodes to the database and modify existing nodes.

To add a node:

1. Select the Nodes option button in the Database tab to view the nodesdefined in the database.

2. Click Add to display the Node Properties dialog box (see Figure 10). If youwish to copy values from an existing node, select the node first in the listbox and then click Add.

3. Select a connection for the node in the Connection Name field.

4. Name the node in the Node Name field. The maximum length of the nodename is 32 characters. Single quotation marks are not allowed in the name.

5. Select a node class in the Node Class list box. Q1 Node denotes Nokia'sQ1-managed nodes, and MML Node Nokia's MML nodes.

SNMP nodes an be saved in the database and edited, but GCS does not support aconnection with them.36 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


6. The selected nodes are displayed in the Parameters list box. The parametersshown in bold typeface are mandatory (such as Q1 ADDRESS in FigureNote

Note

10).

You do not need to give values to any parameters with a default value if thedefault values are suitable.

7. Click Manager Info to select a node manager for the node. The ManagerInfo dialog box is displayed (see Figure 11).

With NMS/10 SR C5.0 and later releases Manager Info is not used. When usingNMS/10 SR C4.1 or an earlier release, select MMLMGR, PAMMGR orTAMMGR (depending on the Alarm Manager you are using) and click OK.When the node is connected through NMS/2000, select NMSSPAWN. Otherwiseit is not possible to poll alarms.DN011794 Nokia Networks Oy 37 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 10. Node Properties dialog box

Figure 11. Manager Info dialog box38 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


8. Click Save to save the defined node to the database.To modify a node:

1. Select the Nodes option button in the Database tab to view the nodesdefined in the database.

2. Select a node in the Nodes list and click Properties to display the NodeProperties dialog box (Figure 10).

3. Modify the parameters as explained above.

4. Click Save to save the defined node to the database.

4.5.3 Viewing connections and nodes

You can view the connections and nodes stored in the database in the Databasetab (Figure 12). There are three different views available in the list box:connections only, connections and nodes, and nodes only.DN011794 Nokia Networks Oy 39 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 12. Nokia Connection Tool, Database tab

Command buttons

Add... displays a Connection Properties or Node Properties dialog box, dependingon what is selected in the list box. If a connection or node is selected, its parametervalues are copied as a basis for the new connection or node. If no connection ornode is selected, the dialog box contains default values.

Remove deletes a selected connection or node.

Properties... displays the Connection Properties or Node Properties dialog boxand allows you to modify the selected connection or node information.

Scan... displays the Scan dialog box for searching for nodes on the selectedconnection. This button is enabled when a connection that supports scanning fornodes is selected.

Manage is enabled if the Manager Info properties have been set for thehighlighted node. For more, see Section 4.5.2, Defining nodes.40 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


The Load More button retrieves missing nodes to work memory. The progress barshows an up-to-date status of the percentage of loaded nodes. If Connections and

View Nodes are selected, only the nodes on the selected connection are retrieved.

Help displays the context-sensitive Help.

To view connections and nodes in the database:

1. Click the Database tab and select the Connections option button. TheConnections list box is displayed with all connections defined in thedatabase (Figure 12).

2. Check View Nodes if you want to see both connections and nodes at thesame time in the Connections list box.

3. You can expand a connection view by double-clicking the connectionname. All definitions that contain any values are shown.

4. If there are more nodes in the database that can be loaded at once, the LoadMore button is enabled. Clicking this button retrieves the missing nodesand brings them to be seen on the screen.

5. Select a connection, and click Properties... to display the ConnectionProperties dialog box (Figures 7, 8).

6. Select the Nodes option button to view only the nodes in the database.

For details on adding and modifying nodes, refer to Section 4.5.2, Definingnodes.

4.5.4 Scanning for network equipment (nodes)Scanning for new nodes is a useful function when you wish to save a node to thedatabase (Database tab), or establish a connection between a node manager and anode (Direct tab).Scanning for nodes

To scan for nodes:

1. Select a connection in the Database or Direct tab.

2. Click Scan.... The Scan dialog box is displayed. See Figure 13.DN011794 Nokia Networks Oy 41 (112)Issue 1-0 en Nokia Proprietary and Confidential


3. Select the address range to be searched for. The accepted values are0...4094 and End must be equal or greater than Begin.NoteSearching through an address range with lots of empty addresses (without nodes)can take a long time. It can be calculated using the following formula.

(number of empty addresses) * (retries + 1) * (time-out)

The default value for retries is 3 and for time-out 2000 milliseconds (2seconds).

4. Give values for Retries and Time-out (optional).

5. Click Start to search for the nodes. The Start button is replaced with theStop button during scanning. You can stop scanning at any time by clickingStop.

There can be a delay of up to 2 minutes before searching stops.

If you wish to continue searching after the first round, check the Repeatcheck box and click the Start button. When you want to stop scanning, clickStop.

If new nodes are found after the previous round, they are added to the listaccording to their address. If nodes that are already in the list do notrespond to the scan command, their rows are shown in italics. If thesenodes start to respond again to the scan command, they are shown innormal font.

Thus a node list row in italics means that there is some trouble either withthe connection or with the node itself.

6. After the searching is finished, all the found nodes are shown on the list(Figure 13).42 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesFigure 13. Scan dialog box

Listing for buses on NMF

Show List button is enabled if the connection supports the bus list function.

To list buses on NMF:

1. Select a connection in the Database or Direct tab.

2. Click Scan... The Scan dialog box is displayed.DN011794 Nokia Networks Oy 43 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Note

Figure 14. Scan dialog box with Show List button enabled

3. Click Show List. The list of buses is shown in a dialog box. See Figure 15.

The following Q1 mediator equipment and respective connection types supportbus list query:

TMS4 with Serial, Modem or Telnet Connection

Nokia MF C1.0 Connection

Nokia Q1 Pipe Connection44 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesFigure 15. Scan: Found Buses dialogd box

4. Select a bus, and click OK.

5. You can continue scanning for nodes on the given address range.

If the bus number has been changed

Nokia Connection Tool requires you to create a new connection and save it beforeany found nodes can be saved if you have changed the Selected Bus number.

To save the changed connection to the database

1. In the following box, click OK to confirm that you want to save a newconnection.

The Connection Properties dialog is shown. All connection parameters arepreset and there is no need to change them.DN011794 Nokia Networks Oy 45 (112)Issue 1-0 en Nokia Proprietary and Confidential


2. Give a name for the connection and click Save to proceed with saving anode.Saving a node

To save a node to the database:

1. Select a node in the search list.

2. Click Save. The Save Node dialog box is displayed with the nodeinformation (Figure 16).

Figure 16. Save Node dialog box

3. You can change the name of the node in the Node Name field.

4. Click Manager Info to select a node manager for the node. The ManagerInfo dialog box is displayed.46 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


With NMS/10 SR C5.0 and later releases Manager Info is not used. Whenusing NMS/10 SR C4.1 or an earlier release, the node managers are

MMLMGR, PAMMGR, TAMMGR, and when using NMS/2000,NMSSPAWN.

5. Click Save. The node is saved to the database.

Saving all nodes

To save all nodes to the database after scanning for nodes:

1. Click Save All... in the Scan dialog box (See Figure 13). The Scan Results:Save All dialog box is displayed (Figure 17).

Figure 17. Scan Results: Save All dialog box

2. Depending on how you wish the found nodes to be named in the database,select either Use node identification as node name, or Generate node namefrom prefix and the checked items.

You can enter a prefix in the Prefix field. Any checked items (Nodeaddress, Node identification, Node type) are added to the node name,following the prefix. The maximum length of the prefix (and the wholename) is 32 characters.

3. Click OK. The Scan Results Selection for Database Saving dialog box isdisplayed, containing a list of nodes found in the search (Figure 18).DN011794 Nokia Networks Oy 47 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Figure 18. Scan Results Selection for Database Saving dialog box

If Yes is displayed in the field Name length too long, click Rename...to shorten the name. The Rename Node dialog box is displayed (Figure19). The maximum length of the node name is 32 characters. Singlequotation marks are not allowed in the name.

Figure 19. Rename Node dialog box

If Yes is displayed in the field Name exists in database, clickReplace/Save to replace and save the selected nodes to the database. Thenode that already is in the database will be overwritten. Rename the nodeif you do not want the old definition to be overwritten.

4. For selecting a node manager for the node, see the procedure To save anode to the database in this section, step 4.48 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


5. Click Select All and then Save to save all the nodes in the list to thedatabase. Once a node has been saved to the database, it is not shown in theNote

list.

4.6 Connection types

This chapter describes all connection types that Nokia Connection Tool supports.Each connection type contains parameters that can be modified. The acceptedvalues and default values are listed in tables in Appendix A.

The connection types listed in this section are:

Section 4.6.1, Serial Port Connection

Section 4.6.2, Modem Connection

Section 4.6.3, Network Connection

Section 4.6.4, Telnet Connection

Section 4.6.5, Nokia Q1 Pipe Connection Section 4.6.6, BSC Connection

Section 4.6.7, BTS Connection

Section 4.6.8, Nokia MF C1.0 Connection

Section 4.6.9, TMS4 Serial Connection

Section 4.6.10, TMS4 Modem Connection

Section 4.6.11, TMS4 Telnet Connection

Section 4.6.12, RCM Macro TMS4 Serial Port Connection

Section 4.6.13, RCM Macro TMS4 Modem Connection

Section 4.6.14, RCM Macro TMS4 Telnet Connection

Section 4.6.15, RCM Macro Nokia MF C1.0 Network Connection

Section 4.6.16, SNMP Connection

Some connection names have been changed. The new and old names of theconnections are listed in the table below:DN011794 Nokia Networks Oy 49 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2Node properties are described in section 4.7, Node properties.

Node parameters are listed in Appendix B, Node parameters.

4.6.1 Serial Port Connection

Serial Port Connection is a direct connection to one or more Q1 or MML nodesusing a serial port of a PC and a cable. When connecting to Nokia Q1 node(s), aV.11/V.28 (RS-232/RS-422) converter and/or a special cable may be needed. Formore about detailed cabling instructions, see the related node documentation.

Table 4. Old and new connection names

New name Old name

Serial Port Connection Serial Port Connection

Modem Connection Modem Connection

Network Connection Network Connection

Telnet Connection Network Connection to Node

Nokia Q1 Pipe Connection Nokia Mediation Function with MF C2.0

BSC Connection BSC Connection

BTS Connection BTS Connection

Nokia MF C1.0 Connection Nokia Mediation Function

TMS4 Serial Connection Serial Connection to TMC

TMS4 Modem Connection Modem Connection to TMC

TMS4 Telnet Connection Network Connection to TMC

RCM Macro TMS4 Serial PortConnection

RCM Macro Serial Port Connection

RCM Macro TMS4 Modem Connection RCM Macro Modem Connection

RCM Macro TMS4 Telnet Connection RCM Macro Network TMC Connection

RCM Macro Nokia MF C1.0 NetworkConnection

RCM Macro Nokia Mediation Function

SNMP Connection Simple Network Management Protocol50 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesFigure 20. Serial Port Connection

4.6.2 Modem Connection

Modem Connection is a connection via a modem to one or more nodes. SeeSection 4.8, Configuring modems for instructions on setting up modemconnections.

Figure 21. Modem Connection

4.6.3 Network Connection

Network Connection is a LAN connection to one or more nodes that have NIC(Network Interface Card) with the TCP/IP protocol stack.

Figure 22. Network ConnectionDN011794 Nokia Networks Oy 51 (112)Issue 1-0 en Nokia Proprietary and Confidential


4.6.4 Telnet ConnectionNote

Note

Telnet Connection is a LAN connection to one or more Q1 or MML nodes thatare located behind a Telnet Terminal Server.

In GCS connections, Telnet Terminal Server means a multiprotocolcommunications server for Ethernet (LAN). It is used to connect GCS to networkequipment with serial interface (RS-232 or similar) attached to Telnet TerminalServer.

Telnet Connection uses always Binary Telnet protocol between GCS and TelnetTerminal Server to ensure free of losses data communication.

In Telnet Connection, GCS supports Shiva Port and Shiva Port Atom devices.

Figure 23. Telnet Connection

4.6.5 Nokia Q1 Pipe Connection

A node manager may lose the connection to a network element made via an NMS/10 MF C2.0. The loss of connection occurs if no data is sent between the nodemanager and the network element for a period of time. The default value is 24 h.If NMS/10 MF C2.0 has been upgraded from MF C1.0, the default value is 60seconds! You must manually replace it with 24 h to ensure that connections arenot lost because of too short timeout.

Nokia Q1 Pipe Connection is a LAN connection to one or more Q1 nodes that arelocated behind NMF using Nokia Q1 Pipe Protocol. NMF can be:52 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


Nokia MF C2.0Note

AXC ATM Cross-connect

DCN Adapter C2.0

Figure 24. Nokia Q1 Pipe Connection

4.6.6 BSC Connection

A node manager may lose the connection to a network element made via a BSC(Base Station Controller). The loss of connection occurs if no data is sent betweenthe node manager and the network element for a period of time. The default valueis 5 minutes. The connection must be re-established for further operationsbetween the node manager and the network element.

BSC Connection via NMS/2000

This kind of BSC Connection is to nodes that are located behind the NMS/2000management system and a Base Station Controller. NMS/2000 works as aprotocol converter between LAN and OSI X.25 TP protocol.

Figure 25. BSC Connection via NMS/2000DN011794 Nokia Networks Oy 53 (112)Issue 1-0 en Nokia Proprietary and Confidential


BSC connection without NMS/2000Note

This kind of BSC Connection is to nodes that are located behind a Base StationController without NMS/2000 in between. This connection requires the OSI X.25TP4 protocol installed.

4.6.7 BTS Connection

A node manager may lose the connection to a network element made via a BTS.The loss of connection occurs if no data is sent between the node manager and thenetwork element for a period of time (5 minutes as a default). The connectionmust be re-established for further operations between the node manager and thenetwork element.

BTS Connection via NMS/2000

BTS Connection is a connection to nodes that are located in a Base Station.

Figure 26. BTS Connection

BTS Connection without NMS/2000

BTS Connection without NMS/2000 is a connection to a base station that islocated behind a Base Station Controller without NMS/2000 in between. Thisconnection requires the OSI X.25 TP4 protocol installed.

4.6.8 Nokia MF C1.0 Connection

Nokia MF C1.0 Connection is a connection to:54 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


NMS/10 MF C1.0 PDH Polling

TMS4 via a customer-specific front end

Figure 27. Nokia MF C1.0 Connection

4.6.9 TMS4 Serial Connection

TMS4 Serial Connection is a local serial cable connection to Q1 nodes that arelocated behind TMS4. This connection requires a V.11/V.28 converter.

Figure 28. TMS4 Serial Connection

4.6.10 TMS4 Modem Connection

TMS4 Modem Connection is a connection via a modem to Q1 nodes that arelocated behind TMS4.DN011794 Nokia Networks Oy 55 (112)Issue 1-0 en Nokia Proprietary and Confidential


Figure 29. TMS4 Modem Connection

4.6.11 TMS4 Telnet Connection

TMS4 Telnet Connection is a LAN connection to Q1 nodes that are locatedbehind TMS4. TMS4 is connected to LAN using Telnet Terminal Server.

In GCS connections, Telnet Terminal Server means a multiprotocolcommunications server for Ethernet (LAN). It is used to connect GCS to networkequipment with serial interface (RS-232 or similar) attached to Telnet TerminalServer.

Telnet Connection uses always Binary Telnet protocol between GCS and TelnetTerminal Server to ensure free of losses data communication.

In Telnet Connection, GCS supports Shiva Port and Shiva Port Atom devices.

Figure 30. TMS4 Telnet Connection56 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


4.6.12 RCM Macro TMS4 Serial Port ConnectionNote

Note

RCM Macro TMS4 Serial Port Connection is a Remote Control andMeasurement Macro connection via a serial port to TMS4.

RCM Macro TMS4 Serial Port Connection is used by some older NMS systems.It is preferable to use TMS4 Serial Connection instead.

Figure 31. RCM Macro TMS4 Serial Port Connection

4.6.13 RCM Macro TMS4 Modem Connection

RCM Macro TMS4 Modem Connection is a Remote Control and MeasurementMacro connection via a modem to TMS4.

RCM Macro TMS4 Modem Connection is used by some older NMS systems. Itis preferable to use TMS4 Modem Connection instead.

Figure 32. RCM Macro TMS4 Modem ConnectionDN011794 Nokia Networks Oy 57 (112)Issue 1-0 en Nokia Proprietary and Confidential


4.6.14 RCM Macro TMS4 Telnet ConnectionNote

Note

RCM Macro TMS4 Telnet Connection is a Remote Control and MeasurementMacro connection via a TCP/IP network and Terminal Server to TMS4.

RCM Macro TMS4 Telnet Connection is used by some older NMS systems. It ispreferable to use TMS4 Telnet Connection instead.

Figure 33. RCM Macro TMS4 Telnet Connection

4.6.15 RCM Macro Nokia MF C1.0 Network Connection

RCM Macro Nokia MF C1.0 Network Connection is a Remote Control andMeasurement Macro connection to NMS/10 MF.

RCM Macro Nokia MF C1.0 Network Connection is used by some older NMSsystems. It is preferable to use Nokia MF C1.0 Connection instead.

Figure 34. RCM Macro Nokia MF C1.0 Network Connection58 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


4.6.16 SNMP ConnectionNote

SNMP Connection needs to be created even though it contains no parameters.The required parameters are given when defining the node. See Appendix B,Section B.4, SNMP node.

The GCS Database supports saving/retrieving SNMP connections and addresses,but there are no applications using this functionality. SNMP is not supported inother parts of GCS.

Figure 35. SNMP Connection

4.7 Node properties

This section describes network elements (nodes) that can be accessed andmanaged using GCS. It contains the following subsections:

Section 4.7.1, Q1 Node Section 4.7.2, MML node

Section 4.7.3, SNMP node

Node parameters are listed in Appendix B, Node parameters.

4.7.1 Q1 Node

Q1 Node is a network element that is managed using Nokia proprietary Q1network management protocol. Functionality of the Q1 Node is hierarchicallydivided into the following groups:DN011794 Nokia Networks Oy 59 (112)Issue 1-0 en Nokia Proprietary and Confidential


The GCS Database has separate settings for the Q1 Node itself and an option tospecify the FE parameters. The FE parameters are, however, usually not specifiedin the GCS Database, but the node manager application supplies the parameterswhen required. Note that some node managers may ignore the FE parameters andspecify their own. They may even refuse to connect to a node if any of the FEparameters have been specified.

4.7.2 MML node

MML Node is a network element that is managed using Nokia proprietary MMLnetwork management protocol. A large cross-connection device, SXC-T nodeuses MML as its management protocol. SXC-T Node Manager uses the GCSDatabase for saving and retrieving the MML Node addresses.

MML connections cannot be shared between several applications or usersbecause the MML protocol itself does not support it.

4.7.3 SNMP node

SNMP Node is a network element that is managed using SNMP, Simple NetworkManagement Protocol. SNMP Nodes can be saved in the GCS Database but theirusage is not otherwise supported in GCS.

Table 5. Functionality of the Q1 Node

Group Explanation

Q1 Node Represents the node itself.The Functional Entity number zero (0)

Functional Entity (FE) Main functionality of the node is mapped intoFunctional Entities.Older Nokia Q1 Nodes consist usually of onlyone FE, the Q1 Node itself.Newer Nokia Q1 Nodes may have several FEs.In some cases their number varies dependingon the node configuration.

Supervision Block (SB) Not visible to GCS.Used to locate the origin of alarms raised in FEs60 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en


4.8 Configuring modemsNote

This section describes the settings that are needed to make the GCS computer anda Nokia modem to serve as a front end for dial-up connections from computersrunning GCS R4.2. It contains the following sections:

Section 4.8.1, Prerequisites for the computer containing GCS

Section 4.8.2, Physical configuration

Section 4.8.3, Modem B sample settings

4.8.1 Prerequisites for the computer containing GCS

The prerequisites for the computer containing GCS are:

A modem is installed in the PC with a maximum speed of 9600 bit/s orslower, depending on the Q1 bus speed

The modem is properly configured

TAPI and support for the modem are available on the PC.

GSC uses TAPI (telephony API; a Windows component) to access the modem.Hence, if there are more than one modem installed in the PC, GCS selects the firstavailable modem that supports data calls.

4.8.2 Physical configuration

The following figure illustrates the physical connection of modems whenconnecting a GCS computer with a TMC.

Figure 36. Physical connection of modemsDN011794 Nokia Networks Oy 61 (112)Issue 1-0 en Nokia Proprietary and Confidential


4.8.3 Modem B sample settingsNote

The settings shown in the following tables are done to the modem B. In thisexample it is a Nokia modem. You can use the matching settings in modem A aswell.

The settings shown in this example are valid for Nokia modems only. You mayhave to use different settings if you are using other than Nokia modems.

Table 6. Modem B: DTE settings

DTE settings Value Note

AT Selected

108.2 Ignored

DSR Always ON

DCD Carrier

Delay (ms) 10DTE speed (bit/s) 9600 Must match with the used TMC

terminal port setting.

Deviation (%) 2.3 The default is 1%.Flow control None Q1 has its own flow control.

Data bits + Parity 8 + Even Must match with the used TMCterminal port setting.

Dir Asy 9 Data

AT set Whole

Break Ingnored Q1 has its own flow control.62 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Defining connections to nodesTable 7. Modem B: auxiliary settings

Auxiliary settings Value Note

Character echo OFF TMC must not get characters echoedback.

Result codes NO TMC must not get characters echoedback.

Connection msg Disabled TMC must not get extra messagesadded back.

Table 8. Modem B: other settings

Other settings Value Note

Compression Auto V-42 sc

Automatic speednegotiation

300-19200 Modem B adjusts automatically to thespeed of modem A.

Auto answer After 1 ring Modem B connects automatically afterone ring.DN011794 Nokia Networks Oy 63 (112)Issue 1-0 en Nokia Proprietary and Confidential

GCS DatabaseCaution

Caution

5 GCS DatabaseThis chapter contains the following sections:

Section 5.1, Introduction to the GCS database

Section 5.2, Maintenance

5.1 Introduction to the GCS database

The GCS Database is a central location for saving connection and nodeinformation used by other applications such as node and alarm managers andsome agents. The database name is dbs.mdb.

The database is by default located in the following directory:

C:\NokiaMgr\System\Database

or

C:\Documents And Settings\All Users\ApplicationData\Nokia\GCS

(Windows 2000).

If the GCS database contains several thousand network elements, its performancemay slow down considerably.

Frequent updates of the GCS Database will degrade its performance over a periodof time. To keep the performance optimal, refer to section 5.2.1, Compacting theGCS Database.DN011794 Nokia Networks Oy 65 (112)Issue 1-0 en Nokia Proprietary and Confidential


5.2 MaintenanceNote

The GCS Database uses Microsoft Access as underlying database technology.Microsoft Access does not manage unused space in its databases. Thereforeregular database maintenance is required to keep the GCS Database size andperformance on the best possible level.

5.2.1 Compacting the GCS Database

The GCS Database must not be in use when compaction is done.

If the GCS Database is updated daily, it should be compacted regularly. Forexample, NMS/2000 and NMS/10 can cause heavy database load. When they areused, the database should be compacted regularly.

You can compact the GCS Database either automatically or manually. Automaticcompaction works only in Windows NT 4 or a later version.

Compacting the GCS Database automatically in Windows NT 4.0

The scheduling.bat file is delivered together with GCS. It containsinstructions on automatic compaction of the GCS Database.

The GCSCompactDb.exe application is installed by default so that it is executedat scheduled intervals (by default at 3:00 a.m.). To change the default settings, seethe help for the AT command. To remove the scheduled job, use the AT /DELETE/YES command, where is the job identificator assigned toGCSCompactDb.exe.

Compacting the GCS Database automatically in Windows 2000

In Windows 2000, set GCSCompactDb.exe in the GCS installation directory torun at regular intervals: Control PanelScheduled Tasks.

Compacting the GCS Database manually (normal case)

To compact the GCS Database manually:

1. Stop all running applications that use GCS

2. Open the Start menu and select SettingsControl Panel. Open DataSources (ODBC).66 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

GCS Database

In Windows 2000 the location is under Control Panel and then underAdministrative Tools.3. From System DSN tab, select DBS32.

4. Click the Configure button to configure DBS32.

5. In Microsoft Access Setup dialog box, click Compact... to compact thedatabase.

6. Use the same database file name for the compacted database and confirmthe replacement of the database.

Compacting the GCS Database manually (the GCS Remote DatabaseUpdate denied)Steps 2 - 4 and 10 - 12 are required only if some NMS system tries to update theGCS Database while it is being compacted and it must be prevented.

To compact the GCS Database manually:

1. Stop all running applications that use GCS

2. Open the Start menu and select SettingsControl Panel. Open Services.

3. Select Nokia GCS Sync from the Service list.

4. Click Stop to stop the service, and confirm it by clicking Yes.

5. Open the Start menu and select SettingsControl Panel. Open DataSources (ODBC).

In Windows 2000 the location is under Control Panel and then underAdministrative Tools.

6. From System DSN tab, select DBS32.

7. Click the Configure button to configure DBS32.

8. In Microsoft Access Setup dialog box, click Compact... to compact thedatabase.

9. Use the same database file name for the compacted database and confirmthe replacement of the database.

10. Restart Nokia GCS Sync by opening the Start menu and selecting SettingsControl Panel. Open Services.DN011794 Nokia Networks Oy 67 (112)Issue 1-0 en Nokia Proprietary and Confidential


11. Select Nokia GCS Sync from the Service list.12. Click Start to restart the service.68 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

GCS Remote Database UpdateNote

Note

6 GCS Remote Database UpdateThis chapter contains the following sections:

Section 6.1, Introduction to GCS Remote Database Update

Section 6.2, Installing GCS Remote Database Update

Section 6.3, Configuring GCS Remote Database Update

6.1 Introduction to GCS Remote Database Update

GCS Remote Database Update was previously called Interface Synchronization.

GCS Remote Database Update allows the other Nokia NMSs to add networkelement information into the GCS Database via a socket connection. This isneeded because node managers launched by NMS must have node andconnection information in the GCS Database before they can open a connectionto the requested node.

6.2 Installing GCS Remote Database Update

GCS Remote Database Update is installed by GCS Setup. After the installation,GCS Remote Database Update starts automatically.

This is available only for Windows NT 4 and Windows 2000 operating systems.DN011794 Nokia Networks Oy 69 (112)Issue 1-0 en Nokia Proprietary and Confidential


6.3 Configuring GCS Remote Database UpdateNote

GCS Remote Database Update allows other Network Management Systems(from now on called clients) to add network element information (name andaddress) into the GCS Database using a socket connection.Configuration

The client must know the host name or IP address of the workstation where GCSRemote Database Update is running and the socket port number where to connect.The port number can be configured using Windows Registry Editor as explainedlater in this chapter. The TimeOut parameter is currently not used.

Restricting use of GCS Remote Database Update

By default all clients can use GCS Remote Database Update for updating the GCSDatabase. If desired, GCS Remote Database Update can be configured so thatonly clients from a specific IP address are allowed to use GCS Remote DatabaseUpdate.

To restrict use of GCS Remote Database Update so that only certain computersare allowed to use it, follow the instructions later in this chapter.

Modifying the Windows registry database with the Registry Editor(REGEDIT.EXE) may damage your system. You must possess proper skills andthe Administrator rights to use the Registry Editor.

To set up a list of allowed clients:

1. Open the Start menu and select Run....

2. Type Regedit in the Open field and click the OK button.

3. Navigate in Registry Editor to the following location (see Figure 37):

My Computer

HKEY_LOCAL_MACHINE

SOFTWARE

Nokia

GCS Communication Service70 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

GCS Remote Database Update

GCSServicesNote

GCSSYNC

4. Add a new key under GCSSYNC and name it Allowed Clients.

5. For each allowed client, add a new key under Allowed Clients and give ita name that is the IP address of the computer which is allowed to use GCSRemote Database Update. Only IP addresses in numeric format areallowed, for example, 172.21.172.174.

6. After all clients have been added, close Registry Editor selecting Registry Exit in the menu.

Figure 37. Example of GCS Remote Database Update Allowed Clientskey

GCS Remote Database Update must be restarted for the changes to take effect.

If you want to allow the same computer where GCS Remote Database Update isinstalled to use GCS Remote Database Update, add IP address 127.0.0.1 underAllowed Clients. You cannot use the computers real IP address but this addressrepresenting the local host computer.DN011794 Nokia Networks Oy 71 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2To modify GCS Remote Database Update settings:

1. Open the Start menu and select Run....

2. Type Regedit in the Open field and click the OK button.

3. Navigate in Registry Editor to the following location (see Figure 38):

My Computer

HKEY_LOCAL_MACHINE

SOFTWARE

Nokia

GCS Communication Service

GCSServices

GCSSYNC

4. You can modify the values of Port No and TimeOut.

5. Close Registry Editor selecting Registry Exit in the menu.

Figure 38. Modifying GCS Remote Database Update settings

GCS Remote Database Update must be restarted for the changes to take effect.72 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

GCS Remote Database UpdateTo manually restart GCS Remote Database Update:

1. Open the Start menu and select SettingsControl Panel.

2. Double-click the Services icon to open it.

3. Select Nokia GCS Sync from the Service list.

4. Click Stop to stop the service, and confirm it by clicking Yes.

5. Click Start to restart the service.DN011794 Nokia Networks Oy 73 (112)Issue 1-0 en Nokia Proprietary and Confidential

GCS troubleshooting7 GCS troubleshootingThis chapter contains the following sections, which describe the known problemsand give instructions on solving them:

Section 7.1, Operating GCS

Section 7.2, Known problems

7.1 Operating GCSStopping and restarting the Nokia GCS service

If you have problems in connecting to nodes, you may need to stop and restart theNokia GCS service.

To stop and restart the service:

1. Double-click the Services icon in the Control Panel.

2. Select the Nokia GCS service in the Service list in the Services dialog box.

3. Click Stop, and click Yes to the confirmation message.

4. The Status column of Nokia GCS becomes empty.

5. Select the Nokia GCS service in the Service list in the Services dialog box.

6. Click Start, and click Yes to the confirmation message.DN011794 Nokia Networks Oy 75 (112)Issue 1-0 en Nokia Proprietary and Confidential


7. In the Status column of Nokia GCS appears the text Started.Note

Note

If you stop the GCS service when you have open connections, an error messagemay be issued. You can ignore this message.

If stopping and restarting the Nokia GCS service does not help, restart thecomputer.

7.2 Known problemsTemporary lock situations with older 16-bit node manager applications

When you use older 16-bit node manager applications, there may be temporarylock situations. This may happen if you are making a connection with theConnection to Node dialog open and you change to another application. You canavoid this problem by completing the connection before using other applications.

Never leave the Connection to Node dialog open in the background.

Incompatiblity of GCS with some 16-bit applications

GCS is incompatible with:

16-bit alarm managers, for example, TAM C1.5 and PAM C1.0

TruMan C4.0 Node Manager

If GCS is installed in a system with TruMan C4.0, the local connection does notwork. You must upgrade TruMan to a newer version to avoid this.

Upgrading from Q1CS R3.0

If you are upgrading from Q1CS R3.0 and have made changes to settings under

HKEY_CURRENT_USER\Software\Nokia Telecommunications Oy\Q1CSR3 Stack\Setting

you have to copy them manually to

HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\GCS CommunicationService\GCSServices\GCSR4\Setting.76 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

GCS troubleshooting

Using modemsOnly one modem can be used at the same time. GCS modem connections havebeen tested with Windows NT 4 and Windows 2000 operating systems. GCS usesthe first available modem that supports data calls if more than one modem isinstalled.

Lost TCP/IP connection

If the TCP/IP connection is lost, most applications (node managers) cannotrecover from it. You must close the connection (for example,ManageDisconnect) and open it again to recover it (ManageConnect).Problems with Macro STE C4.0

Macro STE C4.0, versions A and B cause long communication delays if the FlashLed menu option is on. You must change Green LedLed Off in the menu bar tobe able to communicate normally with Macro STE C4.0.

BSC connection with TP4 protocol

BSC connection with TP4 protocol does not work with default values. When youdefine a BSC connection that uses TP4 protocol, set the PROTOCOL parameter inthe BSC parameters to 0 (zero) manually.ODBC problems in the GCS Database

Most GCS Database problems are related to ODBC settings or Windows NT 4security settings. If the System Data Source, DBS32 is not properly defined, youcan set it up manually.

To manually setup the ODBC settings of the GCS Database

1. Check first that Windows Security permissions allow change access to theC:\NokiaMgr\System\Database directory and all files under it. Ifthere are access problems, fix them manually or reinstall GCS to fix them.

2. Open the Start menu and select Settings. Open Control Panel and selectData Sources (ODBC).

3. Click the Add... button to add a new system data source in the System DSNtab.

The Create New Data Source dialog box is displayed with a list of drivers.

4. Choose the driver of MS Access Driver (*.mdb) and click Finish.

A driver-specific setup dialog box is displayed.DN011794 Nokia Networks Oy 77 (112)Issue 1-0 en Nokia Proprietary and Confidential


5. Type DBS32 into the Name field.Note

6. Click Select to select a database file (for example,

C:\NokiaMgr\System\Database\dbs.mdb)

and click OK.

The System Data Source, DBS32 is defined.

If the problems persist, remove the GCS Database ODBC settings and reinstallGCS.78 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Connection parameters

Appendix A. Connection parametersThe accepted values and default values for the supported connection types arelisted in tables below.

The connection types listed in this section are:

Section A.1, Common connection parameters

Section A.2, Serial Port Connection

Section A.3, Modem Connection

Section A.4, Network Connection

Section A.5, Telnet Connection

Section A.6, Nokia Q1 Pipe Connection Section A.7, BSC Connection

Section A.8, BTS Connection

Section A.9, Nokia MF C1.0 Connection

Section A.10, TMS4 Serial Connection

Section A.11, TMS4 Modem Connection

Section A.12, TMS4 Telnet Connection

Section A.13, RMC Macro TMS4 Serial Port Connection

Section A.14, RMC Macro TMS4 Modem Connection

Section A.15, RMC Macro TMS4 Telnet Connection

Section A.16, RMC Macro Nokia MF C1.0 Network Connection

Section A.17, SNMP Connection

A.1 Common connection parameters

The following optional parameters are common to all connections:DN011794 Nokia Networks Oy 79 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2A.2 Serial Port Connection

Name Values Default Description

Data Protocol Q1DTQ1DLQ1ADQ1UD

Q1DT Q1 data transfer or Q1 data link protocol. Q1specific "sub-protocol" (Data Transfer, Data Link,App Data or User-Defined) can be selected.

Character Coding ASISUNICODEUNIHEX

ASIS -no conversion-UNICODE to ASCII conversion-UNICODE hex to ASCII binary

Verify Connection YESNO

NO Determines if the existence of the Q1 networkelement is verified

Serial Port Connection


Serial Port 1...65535 no default Mandatory parameterSerial communication port number in the PC

Baud Rate 11030060012002400480096001440019200384005600057600115200128000256000

9600 Serial communication port speed

Data Bits 7, 8 8 Number of data bits80 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Connection parameters

Serial Port ConnectionA.3 Modem Connection

A.4 Network Connection

Parity EVENODDNONE

EVEN Parity

Stop Bits 1, 1.5, 2 1 Stop bits for port driver

Flow Control DTR/DSRXON/XOFFNONE

NONE Flow control

Time out 0...300000 2000 Timeout for communication (ms)Retry count 0...1000 3 Communication retry counter


Modem Connection


Phone Number Max. 32characters

no default Mandatory parameterPhone number


Network Connection


Host Name Max. 40characters

no default Mandatory parameterTCP/IP address; either numerical or host name

Port 1...65535 no default Mandatory parameterPort number for TCP/IP node

Data Protocol TCPTP4

TCP The data protocol of the connection.DN011794 Nokia Networks Oy 81 (112)Issue 1-0 en Nokia Proprietary and Confidential


Network ConnectionA.5 Telnet Connection

Connection Reuse YESNO

YES Other clients/users can share the connection, or anew connection is created for them to the samedestination.

TSELECTOR Max. 12characters

no default Mandatory in OSI addresses, not used in IPaddresses



Network Connection






TCP The data protocol of the connection.


YES Other clients/users can share the connection, ora new connection is created for them to the samedestination.



Time out 0...300000 10000 Timeout for communication (ms)Retry count 0...1000 0 Communication retry counter82 (112) Nokia Networks Oy DN011794Nokia Proprietary and Confidential Issue 1-0en

Connection parametersA.6 Nokia Q1 Pipe Connection

Terminal Password


Port Password Max. 32characters

no default Password for RS-232 line access


Network Connection












User Identification


Username Max. 32characters

no default Mandatory parameterUsername for NMS/10 MF C2.0

Password Max. 32characters

no default Mandatory parameterPassword for NMS/10 MF C2.0DN011794 Nokia Networks Oy 83 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2A.7 BSC Connection

BSC Connection via NMS/2000

MF C2.0 Parameters


Equipment ID 0...255 0 ID number defined in NMS/10 MF C2.0

Bus Number


Bus Number 0...255 no default Mandatory parameterBus number in NMF


Network Connection










Connection parametersBSC Connection without NMS/2000

BSC Parameters



no default Mandatory parameterUsername for NMS/2000 connection


no default Mandatory parameterPassword for NMS/2000 connection

Protocol Number 0...255 1 Protocol number for NMS/2000 communication

BSC ID 0...999999 no default Mandatory parameterID of the BSC

Bus ID(mandatory)

0...255 0 Number of the Q1 bus for the managed node


Network Connection



no default Mandatory parameterOSI address (NSAP in hexadecimal format)


TCP The data protocol of the connection.In BSC connection without NMS/2000 the dataprotocol must be TP4





Time out 0...300000 10000 Timeout for communication (ms)Retry count 0...1000 0 Communication retry counterDN011794 Nokia Networks Oy 85 (112)Issue 1-0 en Nokia Proprietary and Confidential

General Communication Service GCS R4.2A.8 BTS Connection

BTS Connection via NMS/2000

BSC Parameters



no default Mandatory parameterUsername for NMS/2000


no default Mandatory parameterPassword for NMS/2000



Bus ID 0...255 0 Number of the Q1 bus for the managed node


Network Connection








YES Other clients/users can share the connection, ora new connection is created for them to the samedestination.


Connection parametersBSC Parameters



no default Mandatory parameterUsername for NMS/2000 connection


no default Mandatory parameterPassword for NMS/2000 connection



Bus ID(optional)

0...255 0 Number of the Q1 bus for the managed node


BTS Parameters


BCF ID 0...255 no default Mandatory parameterID of the BCF

TRX ID 0...255 1 TRX ID

Time out 0...300000 30000 Timeout for communication (ms)Retry count 0...1000 0 Communication retry counterDN011794 Nokia Networks Oy 87 (112)Issue 1-0 en Nokia Proprietary and Confidential


BTS Connection without NMS/2000Network Connection



no default

Date post:	07-Nov-2015
Category:	Documents
Upload:	jovares2099
View:	216 times
Download:	3 times