netnumen t37 transmission network management system northbound interface introduction

NetNumen T37Transmission Network Management SystemNorthbound Interface Introduction

Contents

T37 System Overview T37 Installing T37 Starting Interconnection Between T37 and NMS T37 Uninstalling T37 Upgrading T37 Maintenance Troubleshooting

T37 Background With the rapid development of the telecommunications industry and

communication technologies, today's transmission network is constituted by a variety of techniques, such as SDH, WDM, PTN, and OTN, and the carriers are facing more and more equipment suppliers.

Faced with the ever expanding, increasingly complex transmission network, the carriers have an urgent need for a high performance, low-cost comprehensive network management solution.

How to manage large and complex heterogeneous networks is an urgent issue confronting them.

The emergence of T37 meets the carriers' needs of managing the E

MSs from different manufacturers

T37 interface types

T37 provides following interfaces for the integrated NMS T31 ： SNMP northbound interface, CORBA northbound interface, FILE interface, FTP interface, XML interface,

Specifications and Standards Complied by T37

Interface Standard Description

SNMP

ISO 9595 、 ITU-T X.710 Common Management Information Service (CMIS)

ISO 9596 、 ITU-T X.711 Common Management Information Protocol (CMIP)

ITU-T X.733 Alarm reporting protocol

CORBA

TMF 513 MTNM Business Agreement

TMF 608 MTNM Information Agreement

TMF 814 MTNM Solution Set

Position of T37 in the Network

Located between the T31 EMS and the integrated NMS:

T37 provides the northbound interface for the integrated NMS, as shown below ：

Typical Applications of T37

The T37 northbound interface adopts the distributed installation mode. T37 and T31 are installed on different servers. T37 accesses the T31 server downwards, and provides northbound interfaces for the integrated NMS upwards.

In practice, it is recommended to start the related systems in the following order:1. Start the NetNumen T31 server2. Start the NetNumen T37 northbound interface3. Interconnect the integrated NMS and the NetNumen T37 northbound interface

Contents


Requirements for Operation Environment

The Lowest Configuration Requirements of Hardware Environment

Hardware Requirement

CPU Dual-core 2 G or higher

Memory 2 G or more

Hard disk capacity 80 GB or more

Free space of hard disk 10 GB or more

Monitor 17-inch or more

Resolution 1024×768 or higher

Color Enhanced color (16-bit) or higher

Network adapter Two 10/100 Mbps network adapters

Operating system Windows 2003 server

Requirements for Operation Environment Requirements of CPU and Memory

Number of NEs Managed

Requirements of CPU and Memory on

the T37 Computer

1000

CPU: dual-core 2 G

Memory: 2 G

2000

CPU ： dual-core3G

Memory ： 4G

4000

CPU ： dual-core4G

Memory ： 4G

6000

CPU ： dual-core4G

Memory ： 4G

T37 Installation Mode

T37 supports two installation modes: Centralized installation Distributed installation

T37 Installation Mode Centralized installation

Install T37 and the T31 EMS on the same server. T37 is installed and works as a component of the T31 EMS.

T37 Installation Mode Distributed installation

Install T37 and the T31 EMS on the same server. T37 and the T31 EMS are installed and work as independent

programs respectively,

Installing the T37 Software

Prerequisites The computer used for installing T37 meets the requirements

for operation environment. The computer works properly, and the network

communication is normal. You have completed the planning for the IP address of the

T37 server. You have acquired the T37 installation software package. You have acquired the T31 EMS version managed by T37.


Steps1. In the installation package of T37, double-click to run the

install_Windows.bat file. The setup wizard appears.

2. Click the drop-down list, and then select the language of T37, such as English.

3. Click OK. The Install dialog box appears.


Steps4. Click Next to enter the License Agreement page.


Steps5. Select I accept the terms of License Agreement.

6. Click Next to enter the Please input product license page.


Steps7. Enter the product licenseT37

8. Click Next. The Select T31 Version page appears.


Steps9. Click the drop-down list, and then select the T31 version to

be managed.

10. Click Next. The Select NBI Interface Type page appears.


Steps11. Select the interface types to be installed. In this example,

select all NBI interfaces.

12. Click Next. The Select Deploy Type page appears.

You can select one or all NBI interface types as required.


Steps13. Select a deploy type of T37 according to the installation mode

of T37 and T31. In this example, select Distributed Type.

14. Click NEXT. Choose Installation Directory page appears.

If T37 and T31 are installed on different computers,you must select Distributed Type. If T37 and T31 are installed on a same computer,

select Centralized Type, and T37 will be installed in the same directory of T31.select Distributed Type, and T37 will be installed in a different directory from T31.


Steps15. Choose the installation directory:

16. Click Next. The Configure Parameters page appears.

If Distributed Type is selected in the previous step, the installation directory selected in this step should be different from the directory where T31 is located.If Centralized Type is selected in the previous step, the installation directory selected in this step must be the same as the directory where T31 is installed.


In the Select Deploy Type step, if Centralized Type is selected, the Configure System Parameters tab is not available.

In the Select NBI Interface Type step, if multiple NBI interfaces are selected, the configuration tabs for corresponding interfaces will appear in this step.

Installing the T37 Software Steps

17. Configure the parameters of the system and interfaces ：（ 1 ） . Click the Configure System Parameters tab. Configure the

system parameters

The IP addresses in the Configure Parameters page must be real. The loopback address 127.0.0.1 is not allowed. The port numbers in the Configure Parameters page cannot be the same as those of other applications on the server where T37 is located.To check the port usage on the Windows platform, enter “netstat” in the cmd command line.

Enter the IP address of the T31 server managed by T37.

Enter the CORBA binding port. The default valueis 8005.

Enter a legal T31 username

Enter the IP address of the server where T37 isinstalled.

Enter the password that corresponds to the legalT31 username.


Steps17. Configure the parameters of the system and interfaces ：（ 2 ） Click the Configure CORBA Parameters tab. Configure the parameters

of CORBA interface.

If this option is selected, enter the IP address ofthe T37 server bound with CORBA.

If this option is selected, enter the host name of theT37 server bound with CORBA.

Enter the T37 naming service port. The defaultvalue is 8001.

Enter the T37 notification service port. The defaultvalue is 8003.

Naming service: It registers the object of the system, and gives it a name, so that the corresponding object can be located by this name. Notification service: It allows asynchronous communication among multiple objects, and data transfer between customer and server. At the same time, it can provide specific customers with the data that they are interested in.


Steps17. Configure the parameters of the system and interfaces ：（ 3 ） Click the Configure SNMP Parameters tab. Configure the parameters o

f SNMP interface

Click Add, and you can add the IP address and port numberof an NMS. The default port number is 162.Select the IP address and port number of an NMS. ClickDelete to delete it. Click Modify to modify the IP address orport number.

Enter the T37 server IP and port. The default port number is 1610.


Steps17. Configure the parameters of the system and interfaces ：（ 4 ） Click the Configure File Parameters tab. Configure the parameters of File interfac

e

Managed Element ： collects all the NE information on the EMS.TopoLink ： collects all the topology link information on the EMS. HisPerf ： includes two types ：

24-hour historical performance ： collecting the historical performances within 24 hours .

15-minute historical performance ： collecting the historical performances three hours ago once in two hours. For example, if the first trigger time of the timer is 09:00, the time section of collecting historical performances is 04:00~05:59, and the next time section of collection is 06:00~07:59. HisAlarm ： collects the historical alarms that disappearedon the previous day between 00:00:00 and 23:59:59.

24-hour system, and the default is 22 o'clock.T37 will collect the set data at this time point.

According to the selected resource type for collection, T37 will generate a corresponding csv file after collection, and save it in the corresponding folder of the T37 installation path (that is, the T37 installation path contains four folders:ManagedElement, TopoLink, HisPerf, and HisAlarm, and the generated csv resource file will be placed in the corresponding folder.)” The default path is: "%T37 installation path%\server\plugins\northFileAdapter\local".

Installing the T37 Software Steps

17. Configure the parameters of the system and interfaces ：（ 5 ） Click the Configure FTP Parameters tab. Configure the parameters of FTP interface

The IP address of the remote FTP server. The collected resource file will be automatically uploaded to this FTP server by T37.

The port used by the FTP server, and the default value is 21.

The save path of the remote FTP server. The collected resource file will be saved in this path.

If the set FTP parameter is invalid, that is, the file cannot be transferred to the remote FTP server, the file will be saved in the local default path, which is "%T37 installation path %\server\plugins\northFtpAdapter\local". The save rule is the same as that of the File interface.

The username of the remote FTP server

The password of the remote FTP server


Steps 17. Configure the parameters of the system and interfaces ：

（ 6 ） Click the Configure MTOSI Parameters tab. Configure the parameters of MTOSI interface

Enter the IP address of the T37 server

Enter the port number used by the MTOSI interface. Thedefault value is 8082.


Steps18. Click Next to enter the Installing... page.

19. After installation, click Next to enter the Create Shortcut page.

20. Click Next to enter the Installation Complete page.

21. Click Complete to complete the installation of the T37 software.

Installing the T37 Software Result

Distributed installation The T37 shortcut is created on the Windows desktop. The T37 start menu is created in the Windows start menu.

Centralized installation The related T37 tools are added to the T31 start menu in the

Windows start menu.

Installing the T37 License

Prerequisites You have acquired the authorized T37 License file.

Steps

1. Based on the installation configuration mode of T37, copy the License file to the corresponding folder.

Distributed installation: copy the License file to the %T37 Installation directory%\ server\plugins\northEngine folder.

Centralized installation: copy the License file to the %T31 Installation directory%\server\plugins\northEngine folder.

2. Restart T37.

The T37 License file can only run on the computer provided when the License is applied. If the computer or network adapter is replaced, contact ZTE technical support personnel to re-apply for the License file.

Contents


Starting T37 (for Distributed Installation)

Prerequisites The Distributed Type is selected during the

installation of T37. T37 and T31 have been installed and the

parameters have been correctly configured. The computer where T37 is installed works

properly, and the network communicationis normal.

Starting T37 (for Distributed Installation) Steps

1. On the computer where T37 is installed, double-click the T37 shortcut icon on the desktop. The Console dialog box appears.

The system will start four processes in turn:

T37NAMINGSERVICE process,T37NOTIFYSERVICE process, T37KERNEL process, TARTOOL process.

It takes about one minute in total to start all processes.

Starting T37 (for Distributed Installation)

Steps2. In the Console dialog box, click the icon to enter the Det

ailed specification page.

3. Check the four process operations respectively, to confirm whether their Operation result are Successful.

If one or multiple processes do not start successfully, or they automatically restart, it indicates that the start of T37 fails. Refer to the "Troubleshootings" chapter to handle the problem.

Starting T37 (for Centralized Installation)

Prerequisites The Centralized Type is selected during the

installation of T37. The computer where T37 and T31 are

installed works properly, and the network communication is normal.

Starting T37 (for Centralized Installation) Steps

1. On the Windows server where the T31 EMS is installed, double-click the shortcut icon of T31 server on the desktop. The Console dialog box appears.

2. In the Console dialog box, click the icon to enter the Detailed specification page.

3. Check the Start process of the nine processes respectively, to confirm whether their Operation result are Successful.

4. If any one of the nine processes does not start successfully, it indicates that the start of T37 fails.

Contents


Interconnection Between T37 and Integrated NMS

SNMP CORBA

Interconnection Between SNMP and Integrated NMS （ example ）

Application Scenario T37 and T31 are installed on a same computer A, and the

integrated NMS is installed on computer B.

Computer NMS Version IP Address: Port ID

Computer A T31 T31 V1.20 10.8.60.116

T37 T37 V1.20R1 10.8.60.116:1610

Computer B Integrated NMS - 10.8.20.88.162

Interconnection Between SNMP and Integrated NMS （ example ） Prerequisites

1. Version number of T37 matches with the version number of T31 managed by T37.

2. The integrated NMS of T31 and T37 are installed successfully, and are running normally.

3. You have acquired the corresponding MIB import tool for example, iReasoning MIB Browser).

4. You have acquired the following manuals from ZTE:– MIB Files

– Basic Data Table

– T37 SNMP Interface Standards

– T37 SNMP Interface Development Guide

Interconnection Steps Between SNMP and Integrated NMS （ example ）

Steps Configuring T31 Parameters Configuring T37 Parameters Importing MIB Files Starting the Server Configuring Integrated NMS Parameters Interconnection Result Verification


Configuring T31 Parameters1. Choose Start > Programs > NetNumen T31 > Configure P

arameters ：

2. Select IP Address of Server and IP Address of Database to configured the two IP addresses as the IP addresses of the host where T31 is located. In this topic, the IP context is 10.8.60.116.

3. Click OK.


Configuring T37 Parameters1. Select one of the following paths to run T37 Configure

Tools according to the installation mode of T37.

T37 Installation Mode

Path

Distributed

installation

Choose Start > Programs > NetNumen T37 > T37 Configure

Tools from the menu to display the ZXTIM NBIGuarder for T37

dialog box.

Centralized

Installation

Choose Start > Programs > NetNumen T37 > T37 Configure

Tools from the menu to display the ZXTIM NBIGuarder for T37

dialog box.


Configuring T37 Parameters2. Choose Parameter Config > System Config from the menu

Configure IP Address of T31 Server as the IP address of the host where T31 islocated. In this topic, the IP address is 10.8.60.116.

Configure IP Address of T37 Local as the IP address of the host where T37 is located. In this topic, the IP address is 10.8.60.116.


Configuring T37 Parameters 3. Click SNMP Config

Host IP address where the NMS located, and the port that receives SNMP trap notifications. In this section, the IP address is 10.8.20.88, and the port number is 162 by default.

Use the default value 1610, which should match with the integrated EMS configuration in the subsequent procedures.

Enter a T31 username

Enter a T31 user password


Importing MIB Files1. "MIB.exe" files provided by ZTE include 11 MIB files

and one readme.txt file. Open the readme.txt file.

2. Please strictly follow the importing order in the introduction of the readme.txt file to import the 11 MIB files to the integrated NMS one by one.


Starting the Server1. Start the T31 server.

2. Start the T31 client.

3. Run T37.


Configuring Integrated NMS Parameters Please refer to the corresponding integrated NMS hel

p for detailed configuration methods. Configure the parameters shown below on the integrat

ed EMS ：（ should be consistent with the one in “Configuring T37 Parameters” ）

Integrated NMS IP address Trap port : the port number of the integrated NMS for receivin

g trap information T37 IP address T37 SNMP server port


Interconnection Result Verification Deliver get-bulk criteria query. Make sure the NMS data can be acquired

normally. As successfully ， T37 SNMP interface will save the obtained information to T37 MIB, and we can query needed information from T37 MIB by using the query of get, get-next, and get-bulk.

Enable trap, and then trigger an alarm or performance. Make sure the upper-level EMS can receive the trap information EMS reported. As successfully, all the information will be saved to zteuManagedElementEntry list of T37 MIB.

T37 SNMP spouts the following Trap reports: The notification of creating resource The notification of deleting resource The notification of modifying properties The notification of changing status The notification of alarms ( including TCA) The notification of PSE events The notification of modifying the communication status of NEs The notification of the system

Reference: Ports Needed by T37 SNMP

Port for providing resources and alarms/performance acquisition: 1610

Port for sending Trap to peer end: 162 Ports for communication between T37 and T31:

Naming service: 6001 Notify service: 6003 ORB communication: 6005

UEP distributed port: 32001

Interconnection Between T37 and Integrated NMS

SNMP CORBA

Interconnection Between CORBA and Integrated NMS （ example ）

Application Scenarios The EMS T31 and the T37 are installed on the same computer (A),

and the integrated NMS is installed on computer B.

Computer NMS Version IP Address Port ID

Computer A T31 T31 V1.20 10.8.60.116 -

T37 T37 V1.20R1 10.8.60.116 Local service port ID ： 8005

Naming service port ID:8001

Notification service port ID:8003

Computer B Integrated NMS - 10.8.20.45 -

Interconnection Between CORBA and Integrated NMS （ example ）

Prerequisites1. Make sure the T37 version matches that of the T31 it manages.2. Make sure the T31, the T37 and the integrated NMS are installed succes

sfully, the CORBA interface is selected during the T37 installation, and all the software can start and run normally.

3. The corresponding IDL compiler (for example, JacOrb) is available.4. The following documents have been obtained from ZTE:

IDL file Basic Data Table T37 CORBA Interface Standard T37 CORBA Interface Development Guide The <Difference between the T37 CORBA and the E300 CORBA> file is requ

ired for upgrade interconnection5. Obtain the following basic data for the integrated NMS to use:

Provide the T37 installation directory\server\plugins\northCorbaAdapter\zxonm_corba.ior file to the integrated NMS. This file records details of the naming service.

Provide the naming tree information to the integrated NMS. bindingName[0].id = "ZTE/T3";bindingName[0].kind = "EMSFactory";

Interconnection Steps Between CORBA and Integrated NMS （ example ）

Steps1 、 Configuring T31 Parameters

2 、 Configuring T37 Parameters

3 、 Compiling IDL

4 、 Interconnecting with the Integrated NMS

5 、 Interconnection Result Verification


1 、 Configuring T31 Parameters （ same as SNMP ）2 、 Configuring T37 Parameters

1 ） No.1step same as SNMP

2 ） No.2step same as SNMP

3 ） Configuring CORBA ParametersIP address of the T37 server will be bound if this option is selected. The system will automatically fill in the T37 server IP address, which cannot be modified manually.

Name of the T37 server will be bound if this option is selected. In this case, it is necessary to click Open Hosts and add a redirectionentry to the Hosts file to bind the T37 server name and the IP address. The entry format is “T37 server IP T37 server name”, for example,10.8.20.119 localhost'.

Use the default No. 8001.

Use the default No. 8003.


Compiling IDL Different methods are adopted for different IDL compili

ng tools. Steps as below ：1. Use the IDL compiler to compile the IDL file into correspondi

ng development language codes according to the language selected for the integrated NMS development environment.

2. Interconnect with the CORBA with the compilation language to develop the integrated NMS.


Interconnecting with the Integrated NMS1. Run the T31 server.

2. Run the T37 server.

3. Run the integrated NMS, and enter the information shown below to complete interconnection ：

User name Password T37 IP address （ must be consistent with the value configur

ed in “Configuring T37 Parameters” ） T37 naming service port ID （ must be consistent with the val

ue configured in “Configuring T37 Parameters” ）Because the integrated NMSs developed by different manufacturers provide different functions, the information required for interconnection between the integrated NMS and the T37 CORBA may vary.

Interconnection Steps Between CORBA and Integrated NMS （ example ） Interconnection Result Verification

1. If the interconnection succeeds, the integrated NMS can monitor the NEs managed by the EMS.

2. And configuration operations can be successfully completed through the integrated NMS.

Reference: Ports Needed by T37 CORBA

Ports needed by CORBA interface: Naming service: 8001 Notify service: 8003 ORB communication: 8005

Ports for communication between T37 and T31: Naming service: 6001 Notify service: 6003 ORB communication: 6005

UEP distributed port: 32001

Contents


Uninstalling T37

Prerequisites The computer where T37 is installed works properly,

and the network communication is normal. T37 Uninstalling includes two steps ：

Exiting T37 Uninstalling T37

Generally, the T37 server should not be closed when it is running properly. In some specific cases, such as upgrading the T37 version, you can close the T37 server.After closing the T37 server, all the services provided by T37 will stop.

Exiting T37 Note:

If T37 is installed in centralized mode, you cannot exit it separately. You can only exit it through the T31 console. For the method of exiting the T31 server, refer to the related manuals of T31.

This section only describes the method of exiting T37 when it is installed in distributed mode.

Steps1. In the T37 Console dialog box, stop the TARTOOL process, T37KERNEL

process,T37NOTIFYSERVICE process, and T37NAMINGSERVICE process in turn.

2. Confirm that the four processes in the console have been stopped successfully.

3. Choose System > Exit from the main menu. The Confirm dialog box appears.

4. Click OK to close the console.

The T37 NOTIFYSERVICE process will automatically stop as the T37KERNEL process stops.

Uninstalling T37

Prerequisites The T37 program has been exited.

Steps1. Log in to the Windows system as the administrator role.

2. Based on the T37 installation mode, run the T37 uninstallation tool according to the method described in the following table.

T37 Installation

Mode

Method of Running the T37 Uninstallation Tool

Centralized

installation

Click Start > Programs > NetNumen T31 > Uninstall NetNumen T37.

The Info dialog box appears.

Distributed

installation

Click Start > Programs > NetNumen T37 > Uninstall NetNumen T37.

The Info dialog box appears.

Uninstalling T37

Steps3. Click Yes. The Uninstall dialog box appears.

4. Click Next to enter the Uninstall Data Files page.

Uninstalling T37

Steps 5. After the uninstallation progress bar is displayed as 100%,

you enter the uninstallationcomplete page. Click Complete.

Contents


Upgrading T37

Upgrade Flow

Before upgrade, back up the following files under the T37 installation directory:

1. The license.dat file in the "%T37 installation path%\server\plugins\northEngine" folder.

2. Follow the steps described in the "Modifying Configuration Parameters" section to open the parameter configuration page and copy the configuration parameters into a notepad file.

Upgrading T37

Upgrade Flow

After backing up the related files, you need to uninstall the old-version T37 program, whose method refer to the "Uninstalling T37" chapter.

Upgrading T37

Upgrade Flow

After uninstalling the old-version T37, you can start the installation of the new-version T37, whose method refer to the "Installing T37" chapter.

Upgrading T37

Upgrade Flow

l 、 Go to the parameter configuration page, and then reconfigure the parameters according to the configuration data recorded in the "Backing Up Related Files“ section.

2 、 Copy the backup license.dat file into the following folder of the new-version program:

"%T37 Installation path%\server\plugins\northEngine"

Upgrading T37

Upgrade Flow

l 、 Restart T37 to complete the upgrade. 2 、 Check whether the T37 version is correct. 1 ） Run the T37 Configure Tools. 2 ） In the Junior page, you can check the T37 version

Contents


T37 Maintenance

Maintenance item: Checking the hardware status of T37 server system

Mouse: check whether it can respond correctly to the operations of clicking, dragging, etc.

Keyboard: check whether it can respond correctly to the operation of typing characters.

Monitor: check whether it is under normal display mode and whether it can display normally;

Printer: print a testing paper to check whether it is working properly.

Network Adapter: check whether it is connected to the network correctly.

Router: check whether the indicator is ON and the network routing is normal.

T37 Maintenance

Maintenance item: Checking the space occupancy of the disks The current server uses the WINDOWS operation

system. Click "Control Panel -> Performance and Maintenance

-> Management Tool -> Computer Management"; Open "Storage -> Disk Management" to check the

occupancy of the partitions: If the percentage of free space is lower than 30%, i.e. more

than 70% of the disk space is occupied, you need to clear the hard disk, move the backup files to other storage media or delete the unwanted logs.

T37 Maintenance

Maintenance item: Checking the work efficiency of NMS Check the usage ratios of the CPU and memory of the

NMS. The CPU and memory should be used mainly by the T37 processes. Try to prevent the NMS resources from being used by other system.

Click "Progress" in the "Task Manager" of Windows to check the CPU usage of the process. If the CPU usage ratio of some process is always more than 50%, you need to check it carefully to see whether it is caused by virus.

T37 Maintenance

Maintenance item: Monitoring the running status of the programs (processes)

On the server where T37 is installed, check whether the T37 processes are successfully started.

Method1: Click "Windows -> Start -> Programs -> NetnumenT37 ->T37 Configuration Tool", and click "Advanced -> Interface Monitoring -> Process Monitoring". If the process is running properly, the window will show "Normal"; if the process is not running properly, the window will show "Abnormal"; if the window shows "Not Exist", it means the process is not started successfully.

Method2: Click the T37 icon on the tray at the bottom right of the screen to check whether the process is started normally.

T37 Maintenance Maintenance Items ： Checking the Communicat

ion Status Between T37 and T311. On the server where T37 is located, enter the following comma

nd. If T37 can ping through T31, it indicates that the communication is normal.

“ ping IP address of the server where T31 is located ”

2. After starting T37, run the client of the integrated NMS and check whether you can log in to T37 normally.

T37 Maintenance Maintenance Items ： Checking the Communicat

ion Status Between T37 and the NMS1. On the server where T37 is located, enter the following comma

nd. If T37 can ping through T31, it indicates that the communication is normal.

“Ping IP address of the computer where the NMS is located”

2. Start T37, and confirm that it starts successfully.

3. Start the client of the integrated NMS, and confirm that it can manage the T31 EMS connected by T37 properly.

T37 Maintenance Maintenance item: Checking the security of the computer

Check whether the NMS has installed the patches in time to prevent Windows vulnerabilities; Check the installation of firewall; Check whether the anti-virus software has been updated in time and the virus library is updated.

Maintenance item: Managing the security of passwords and permissions

Check the passwords and permissions of the Windows system on the NMS. Set the passwords in a more complicated manner and change the passwords periodically.

Maintenance item: Backing-up the operation logs of the system The T37 logs are located at: \NetNumen_T37\server\bin\logs Compress the log files under the directory and save a back-up copy to other

storage media. You can also use the T37 configuration tool to collect the log files by just one

click. In the "T37 Configuration Tool" window, click "Basic -> Log Collection -> One-click Collection", then select the directory to save the files. If you click "One-click Log Collection", you will collect all the configuration files and logs related to T37.

Notes for Routine Maintenance

The system time must not be changed when T37 server is running ： This is a limitation of the system. You need to set the

system time correctly when installing the NMS system. If you need to change the system time during the maintenance, you must exit the server correctly. After changing the time, you can restart the T37 server.

T31 must be started successfully before starting T37 ： Before starting T37, you should make sure that T31 h

as already been started successfully and the T31 client can log on the T31 server normally.

Contents


Notify Service and Kernel Process of T37 cannot be Started

Symptoms After the T37 server is started, one or multiple

processes of the T37NOTIFYSERVICE process and T37KERNEL process in the console cannot keep as the state.

Notify Service and Kernel Process of T37 cannot be Started

Fault Analysis and Troubleshooting Check whether T31 has been started successfully. T37 License is not installed or the License file is abnormal:

On the computer where T37 is located, make sure that the license.dat file is added into "%T37 installation path%\server\plugins\northEngine" folder after T37 is installed.

The IP address of the T31 server is wrongly configured: On the computer where T31 is located, select [Start→Programs→NetNumen T31→Con

figure Parameters], check the IP Address of Server, which should be the actual IP address of the computer where T31 is located, instead of the loopback address "127.0.0.1".

The T37 interface parameters are wrongly configured: On the computer where T37 is located, select [Start→Run], imput "cmd" to open the Wi

ndows command dialog box.Input the "netstat" command to check the numbers of the ports used by the Windows programs.

d. On the computer where T37 is located, select [Start→Programs→NetNumen T37→T37Configuration Tool] to check if the configured port numbers of the T37 interfaces are the same as the port numbers of other applications. If so, modify them to unused port numbers.

Before starting T37, check the occupancy of the computer ports and make sure that the ports needed by T37 are not occupied by other programs (8001,8003,8005):

In the Windows CMD dialog box, input “netstat -an >C:\duankou.txt” (">C:\duankou.txt" means the result will be output to "C:\duankou.txt". After the above command is executed, you can check the occupancy of the computer ports in the file. ）

Restart the T37 server to check whether the processes are started successfully.

Naming Service of T37 cannot be Started

Fault Analysis and Troubleshooting In "T37 Configuration Tool", check whether the "IP" or

"Machine Name" in the Corba Parameters is wrongly configured.

Note: The IP here refers to the IP of the network segment where the T37 server and the integrated NMS are located.

Exceptional Network Communication Symptoms

The processes of the T37 server run abnormally. The integrated NMS cannot connect with the T31 EMS through T37.

Fault Causes The communication between T37 and the T31 EMS is abnormal. The communication between T37 and the integrated NMS is abnormal.

Fault Handling1. Check if the network connections among the T31 EMS computer, T37

computer, and integrated NMS are normal. If not, check the network adapters and the communication protocols.

2. Check if the T31 EMS server, T37 server, and NMS server run properly. If not, refer to the corresponding user manual to handle the fault.

3. On the computer where the T37 server is located, ping the computer where the T31 server is located. If the ping operation fails, check the communication line between the two network management systems.

4. On the computer where the T37 server is located, ping the computer where the integrated NMS is located. If the ping operation fails, check the communication line between the two network management systems.

Integrated NMS cannot connect to T37 Fault Description

The integrated NMS cannot get connected to the T37 normally. Fault Analysis

1. On the integrated NMS, ping the IP of T37 server. If the ping cannot get through, it means the network has some problem.

2. If the ping gets through, start the corba client on the integrated NMS server to connect T37. If the corba client can connect to T37 normally, it means the fault is an interconnection problem.

3. If the corba client on the NMS server also cannot connect to T37, start the corba client on the T37 server to connect to T37.If the latter way get through and the former does not, the problem is generally caused by network or firewall problems.

4.If the corba client on the T37 server also cannot connect to T37, check whether the T37 process is started successfully.

5. Besides, you need to check whether the username and passwords used to log on the T37 are correct (this can be checked on T31). If the username or passwords is wrong, get back to the error prompt directly.

6. If you use the machine name to log on T37, you must make sure that the hosts file in the integrated NMS server contains the mapping relation of the IP and machine name of the T37 server.

NE label of T31 is abnormal when T31 and T37 are under centralized deployment Fault Description

When T31 and T37 are under centralized deployment, the NE label of T31 is abnormal.

Fault Analysis This problem may occur on the version of

T37V1.10R2P02B03 or earlier versions.

Troubleshooting When this problem occurs, you need to conduct the

operation of "Sync topology data" on T31.

netnumen t37 transmission network management system northbound interface introduction

Documents

t37 server

t37 startinginterconnection

t37position of t37

language of t37

t37 softwaresteps4

emergence of t37

t37 softwaresteps1

installation package