sjzl20073072-NetNumenN31 Integrated Network Management Troubleshooting - 127424 PDF

NetNumenN31
Integrated Network Management
Troubleshooting
Version 4.1
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Date
Revision No.
Serial No.
Reason for Issue
Oct. 31, 2006
R1.0
sjzl20073072
First edition
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
NetNumenN31 Integrated Network Management Troubleshooting
Product Version
V 4.1
Document Revision
Number
Serial No.
sjzl20073072
Equipment
Installation Date
R1.0
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Your evaluation
of this
documentation
Fair
Average
Poor
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Your
suggestions for
improvement of
this
documentation
Improve the overview/introduction
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Add more examples
Add more/better quick reference aids
Add more detail
Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name
Company
Postcode
Address
Telephone
E-mail
This page is intentionally blank.
Contents
About This Manual ............................................................ i
Purpose ................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge .............................................. i
What Is in This Manual ........................................................... i
Conventions ......................................................................... ii
How to Get in Touch............................................................. iii
Declaration of RoHS Compliance..................................... v

Chapter
1....................................................................... 1
Common Problems and Solutions ................................... 1

Overview ............................................................................. 1
Installation Problems ............................................................. 1
NetNumeN31 Boot Failure Caused By Changed Version Path and
Undeleted Temp Directory ...................................................... 2
NetNumeN31 Platform Crossing the Firewall ............................. 2
Multiple IPs on the NetNumeN31 Platform ................................ 3
Floating IP Problems in Cluster................................................ 4
Strange Problems (For Example, Client Exists Automatically after
Running for a Period) ............................................................ 7
Gray Client Login Window ...................................................... 8
Abbreviations ................................................................... 9
Confidential and Proprietary Information of ZTE CORPORATION
About This Manual

Purpose
This manual describes common problems that might occur in the
NetNumenN31 Integrated Network Management System (NMS)
and provides solutions to the problems.
Intended Audience
This manual is intended for the engineers and technicians who
perform maintenance activities on the NetNumenN31 system.
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general
understanding of the NetNumenN31 system.
What Is in This Manual

This manual contains the following chapters:
TABLE 1 CHAPTER SUMM ARY
Chapter
Summary
Chapter 1,
Common
Problems and
Solutions
This chapter describes the common problems that

might occur in the NetNumenN31 Integrated
Network Management System and provides
solutions to the problems.
Conventions
Typographical
Conventions
ZTE documents employ the following typographical conventions.

TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface
Meaning
Italics
References to other Manuals and documents.
Quotes
Links on screens.
Bold
Menus, menu options, function names, input

fields, radio button names, check boxes, dropdown lists, dialog box names, window names.
CAPS
Keys on the keyboard and buttons on screens

and company name.
Constant width
Text that you type, program code, files and

directory names, and function names.
[]
Optional parameters.
{}
Mandatory parameters.
Select one of the parameters that are delimited

by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Mouse
Operation
Conventions
ii
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually

the left mouse button) once.
Double-click
Refers to quickly clicking the primary mouse button

(usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button

(usually the right mouse button) once.
Drag
Refers to pressing and holding a mouse button and

moving the mouse.
About This Manual
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer
Support
Documentation
Support
If you have problems, questions, comments, or suggestions

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
iii
iv
Declaration of RoHS
Compliance
To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal declaration that NetNumenN31 Integrated Network
Management manufactured by ZTE CORPORATION are in
compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with
respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)
NetNumenN31 Integrated Network Management manufactured

by ZTE CORPORATION meet the requirements of EU
2002/95/EC; however, some assemblies are customized to client
specifications. Addition of specialized, customer-specified
materials or processes which do not meet the requirements of
EU 2002/95/EC may negate RoHS compliance of the assembly.
To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION
in written form.
This declaration is issued based on our current level of
knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and
assumes no liability in connection with the use of this
information.
vi
Chapter
Common Problems and

Solutions
Overview
Introduction
Contents
This chapter describes and analyzes common problems that

might occur in the NetNumenN31 system and provides solutions
to the problems.
This chapter includes the following sections:
Section
Page
Installation Problems
NetNumeN31 Boot Failure Caused By Changed

Version Path and Undeleted Temp Directory
NetNumeN31 Platform Crossing the Firewall
Multiple IPs on the NetNumeN31 Platform
Floating IP Problems in Cluster
Strange Problems (For Example, Client Exists

Automatically after Running for a Period)
Gray Client Login Window
Installation Problems
The version directory on the platform shall not contain the
following symbols. Otherwise the platform cannot operate
normally.
Symbols
including
+
(Chinese
and
(Chinese), !,@,$,^,&,* are not supported.
English),
NetNumeN31 Boot Failure Caused

By Changed Version Path and
Undeleted Temp Directory
Problem
Description
Change version path name and reboot NetNumeN31 client

terminal directly. An error is reported.
Analysis
According to the analysis, it is because the temp directory was

not deleted after the version path name was deleted. Data was
cached on both the client terminal and the server. After the
version path name was changed, the cached data could not be
found when the client terminal was restarted, thus the error was
reported.
Note: Error such as java.lang.ClassNotFoundException
can also be caused by other factors, for example, classes cannot
be found because of incorrect class path setting. What
mentioned in this manual is only one of the possible causes.
Solution
Delete the temp directory after changing the version path name,
and then restart the NetNumeN31.
Note:
If the version you copied to the computer has been running

on another computer, this problem can also occur.
If the change is made on the NetNumeN31 server side, the
following error can be reported. The solution is the same.
NetNumeN31 Platform Crossing the

Firewall
Problem
Description
In enterprise applications, because of the firewall, the platform

cannot cross the firewall to provide services. To random ports
that provide services on the platform, it is not easy to determine
which ports should be opened.
The original solution is: Fix ports providing services on the
server end, and open specified ports to allow them to cross the
firewall.
Many ports are used by the NetNumeN31 platform. And more
ports can be added because of enhanced software functions.
This method is too complex to commissioning, and client may
not agree to open so many ports. And once a certain port is not
opened, errors will occur on the NetNumeN31 platform.
Chapter 1 Common Problems and Solutions
Analysis
The NetNumeN31 platform uses serversocket when creating

services. The default port 0 is used in many places. As the
system automatically assigns random ports and many ports exist,
it brings inconvenience for crossing the firewall.
Solution
Deploy a socks proxy agent on the server, and deploy a tunnel

on the client terminal. All connection establishment operations
are automatically forwarded to the socks proxy agent through
the tunnel and then reach the NetNumeN31 server. By this
means, communications between the client and the server only
use the fixed port, allowing the cross problem to be solved from
the bottom layer.
Multiple IPs on the NetNumeN31

Platform
Problem
Description
Generally, clients and servers in the NetNumeN31 system are

located in different LANs. The LANs are connected with various
IP devices. Data transmitted from one network to another may
be processed by devices such as routers, firewalls, or network
address translations (NAT). The software and hardware
configuration of computers that send or receive the data can be
complex. For example, the computers may have multiple
network adapters, contain many IP addresses, or connect to
different subnetworks.
Analysis
Search the platform and you will find many modules of the
platform use getLocalHost() of InetAddress, around 30 to 40
files. There are more in jboss. The modules involved are:
automatic detection, trap, performance, system management, f
port, security, logs, protocols, debug print, clock, ftp, and
cascade.
Risks exist if we change one by one. Therefore we start from
JDK, or parameters, or the network configuration file of
operating system. Therefore, we solve the problem through the
network configuration file of the operating system. If this
method still does not meet the requirements, we will then
consider modifying the program codes.
Solution
Solve the problem by means of network configurations.

After many experiments with many operating systems, we can
solve the localhost problem by configuring the host files (for
Windows2003, Solaris, or Linux) or by configuring the sequences
of network adapters (Windows2000).
Floating IP Problems in Cluster

Problem
Description
1. In the cluster environment, the server side binds at least

three IP addresses: a real physical address, a database
floating IP address and an application server floating IP
address.
2. In the cluster environment, using system management
functions of NetNumenN31, if the device is set up with the
floating IP address, server information cannot be viewed. If
the device is set up with local address, the server
information can be viewed.
3. Integrated network management system uses the cluster
environment. Platform server end program returns a random
address that can be connected to client, for example, FTP
server end. Only one server end address that can be
connected is exposed to the client. Meanwhile, for
communication from the server to Interface Message
Processor (IMP), only one server end address is allowed to
be exposed to the IMP even if in the cluster switchover
environment due to security limit of the IMP. IP address limit
requirements are transparent to communication protocols.
That is, for communication with IMP using SOCKET, FTP or
CORBA, the address limit requirements function correctly.
Also, if the server is connected to itself, for example, logs
management, server addresses recorded by logs server
during cluster switchover should be the same.
Analysis
1. Create the cluster environment and start the cluster.

Test machine is the cluster consisting of inet1 and inet2.
Locate the problem according to change in inet1 address.
Inet1 address:
hme0
10.197.32.252
Network management floating address: 10.197.33.168

Execute #ifconfig -a to check
hme0:
flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>
mtu 1500 index 2
inet
10.197.32.252
broadcast 10.197.63.255
netmask
ffffe000
ether 0:3:ba:8:b2:c1
hme0:1:
flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>
mtu 1500 index 2
inet
10.197.33.168
broadcast 10.197.63.255
netmask
ffffe000
2. Check if packet loss occurs when sending SNMP traps to the

floating IP address.
The client uses 10.197.33.168 to send 30000 pieces of test

SNMP traps, and the server end receives 30000 pieces.
3. Test system management and set up a management device.
Information is not obtained using floating address
10.197.33.168. But information can be obtained using
10.197.32.252.
Capture packets. For both floating address and real address,
source address contained in the captured packets is
10.197.32.252.
4. Change hme0 10.197.32.252 to 192.168.1.2 netmask
255.255.255.0 another network segment. Then test system
management and capture packets. Information is obtained
using floating IP address 10.197.33.168. Source address
contained in the captured packets is the floating address.
5. Through analysis, it is determined that a fault occurs on
routing.
Use netstat -r to check. The result is:
root@inet1 # netstat -r
Routing Table: IPv4
Destination
Interface
Gateway
Flags
Ref
Use
-------------------- -------------------- ----- ----- ------ -------10.197.32.0
inet1.v0
10.197.32.0
inet1
default
10.197.32.10
localhost
localhost
U
U
1
1
UG
UH
12 hme0
0 hme0:1
1
8
1759 lo0
Analysis: Packets in the same subnet will be sent via the first
route (that is, hme0 interface).
Execute
#ifconfig hme0 down
to make the interface down. Then
#ifconfig hme0 up
Check the route.
root@inet1 # netstat r
Routing Table: IPv4

Destination
Interface
Gateway
Flags
Ref
Use
-------------------- -------------------- ----- ----- ------ -------10.197.32.0
inet1
19 hme0:1
10.197.32.0
inet1.v0
default
10.197.32.10
localhost
localhost
UG
UH
0 hme0
1
8
2744 lo0
From above it can be seen that hme0 interface is behind

hme0:1. Then test system management. Information can be
obtained using floating address hme0:1 10.197.33.168 and
captured packets are normal.
Information is not obtained using hme0 10.197.32.252.
Source address contained in the captured packets is the
floating address.
6. A better solution
In practical applications, do not change IP address mask
range of the machine itself. And make mask range
configured for floating address reduce a bit.
For example: Before modification
hme0
Local
255.255.224.0
address
10.197.32.252
hme0:1
Floating address 10.197.33.168
255.255.224.0
Mask:
Mask:
Now enlarge local mask range consciously:

After modification: Local address 10.197.32.252
255.255.224.0
Floating address 10.197.33.168
Mask:
Mask: 255.255.225.0
In this way ensure that hme0:1 is the first one when

checking routes by netstat -r.
Floating address route is listed in the front of the routing
table because of more mask bits. Thus the problem is solved.
Solution
1. SNMP system management problem is confirmed to be the

same type as integrated network management problem.
Address used by server end. If a getlocalhost sentence is
used to specify source address in the program, it is the first
one in /etc/hosts. Otherwise, the system will use default first
correct route. The first route is the first interface viewed
after netstat -r is executed. IP address of the interface is
source address.
2. In practical applications, do not change IP address mask
range of the machine itself. And make mask range
configured for floating address reduce a bit.
In this way ensure that the floating address route is the first
route.
Execute netstat -r to check order of interfaces.
3. As an alternate solution of 2, local address and floating
address can be configured in different network segments.
In practical situations using floating address, the floating

address is configured in the same network segment as the
machine to be communicated with.
Configure the server address in another network segment.
Use netstat -r to check the order of interfaces.
Use different routes for different network segments. In this
way ensure used IP address is what we need. However, the
configuration does not facilitate remote management server.
4. To ensure the address that can be connected the platform
server end program returns to client is floating address,
configure /etc/hosts file to write floating address as the first
one. Certainly the floating address does not function on the
local computer after the cluster switches to the other
computer.
root@inet1 # more /etc/hosts
#
# Internet host table
#
127.0.0.1
localhost
10.197.33.168
floating IP
inet1
----------Network management
192.168.1.2
inet1.v0 --------Local IP
192.168.1.3
inet1.v1 --------Database Floating IP
10.197.33.165
inet2
If an external machine needs to communicate with database,

it is needed to configure a static route to access database
server 192.168.1.3 on the external machine.
The route can be configured to:
route ADD 192.168.1.3 MASK 255.255.255.0 10.197.33.168
METRIC 3
destination^
metric^
^mask
^gateway
Strange Problems (For Example,

Client Exists Automatically after
Running for a Period)
Problem
Description
Solution
Unknown errors. It is hard to determine the reasons. For

example, the client exits automatically after running for a period
(Solaris commissioning problem).
Download Solaris x Recommended Patch Cluster and install it.
Download and install J2SE Solaris x Recommended Patch Cluster

http://patches.sun.com/clusters/
Execute # showrev -p to check installed patches.
Gray Client Login Window

Problem
Description
After client is started, login window is always gray. It is

unrelated to the server. The simplest java swing program
(showing a frame) cannot be executed. The reason is system
software conflict. PCAnywhere 10.5.1 Build505 is installed on the
computer, which conflicts with Java plotting. Solution is to close
PCAnywhere Agent or use PCAnywhere10.0.0 Build361 when
network management is started.
Other software may also cause conflict, for example OpManager
5.0 of Advenet.
Through analysis, it is found that the following methods can
solve the problem, but the methods are not fully verified.
This fault can be solved by the following startup parameter.
Refer to client startup file.
-Dsun.java2d.noddraw=true
Through tests, it is found that DirectX upgrade can also solve
the problem.
Analysis
According to description on Sun official website:

There are also some DirectDraw-related errors. If you encounter
a DirectDraw problem, close DirectDraw.
-Dsun.java2d.noddraw=true
Some monitor drivers may cause monitor images (including
windows) to resynchronize or skip when DirectDraw is accessed.
If you see the problem, check manufacturer's website to see if a
new version is available to solve the problem.
That is, new Swing uses DirectDraw technology of Microsoft to
improve plotting performance, but the technology is not
supported by all the video cards (especially for some server
video cards). And DirectDraw needs latest DirectX to support it,
so DirectX upgrade can also solve the problem. Besides, closing
DirectDraw can also solve some abnormal display problems.
Abbreviations
Abbreviation
Meaning
DBMS
Database Management System
IP
Internet Protocol
LAN
Local Area Network
NA
Network Administrator (s)
NE
Network Element (s)
NMS
Network Management System
RMI
Remote Method Invocation
RPC
Remote Procedure Call
TCP
Transport Control Protocol
WAN
Wide Area Network

sjzl20073072-NetNumenN31 Integrated Network Management Troubleshooting - 127424 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

sjzl20073072-NetNumenN31 Integrated Network Management Troubleshooting - 127424 PDF

Uploaded by

Copyright:

Available Formats

NetNumenN31

Integrated Network Management

Reason for Issue

Oct. 31, 2006

NetNumenN31 Integrated Network Management Troubleshooting

Improve the overview/introduction

Make it more concise/brief

Improve the Contents

Add more step-by-step procedures/tutorials

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

Add more examples

Add more/better quick reference aids

Add more detail

Improve the index

This page is intentionally blank.

Declaration of RoHS Compliance..................................... v

Common Problems and Solutions ................................... 1

Confidential and Proprietary Information of ZTE CORPORATION

NetNumenN31 Integrated Network Management Troubleshooting

This page is intentionally blank.

About This Manual

Prerequisite Skill and Knowledge

What Is in This Manual

This chapter describes the common problems that

Confidential and Proprietary Information of ZTE CORPORATION

NetNumenN31 Integrated Network Management Troubleshooting

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input

Keys on the keyboard and buttons on screens

Text that you type, program code, files and

Select one of the parameters that are delimited

TABLE 3 MOUSE OPERATION CONVENTIONS

Refers to clicking the primary mouse button (usually

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button

Refers to pressing and holding a mouse button and

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

How to Get in Touch

If you have problems, questions, comments, or suggestions

Confidential and Proprietary Information of ZTE CORPORATION

NetNumenN31 Integrated Network Management Troubleshooting

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

NetNumenN31 Integrated Network Management manufactured

Confidential and Proprietary Information of ZTE CORPORATION

NetNumenN31 Integrated Network Management Troubleshooting

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Common Problems and

This chapter describes and analyzes common problems that

NetNumeN31 Boot Failure Caused By Changed

NetNumeN31 Platform Crossing the Firewall

Multiple IPs on the NetNumeN31 Platform

Floating IP Problems in Cluster

Strange Problems (For Example, Client Exists