Professional Documents
Culture Documents
Imanager U2000 Administration Training PDF
Imanager U2000 Administration Training PDF
Trademarks
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice, every effort
has been made in the preparation of this manual to ensure accuracy of the
contents, but all statements, information, and recommendations in this manual do
not constitute a warranty of any kind, express or implied.
Huawei Technologies
TABLE OF CONTENT
CONTENT
As a model and standard of software development, the Common Object Request Broker
Architecture (CORBA) provides necessary services and toolkit to develop software.
The CORBA northbound interface (NBI) functions to integrate the distributed software at the
element management layer with that at the network management layer.
The CORBA NBI has the following features:
Complying with the CORBA 2.3 specification of the Object Management Group (OMG) and
supporting the IIOP 1.1 and IIOP 1.2.
Adopting the standard CORBA Naming Service 1.1 and Notification Service 1.0.
The current version that uses The ACE ORB (TAO) 1.3 is highly efficient. Capable of being
smoothly transplanted to other ORB platforms.
It supports the interconnection between different ORB platforms, including:
– IONA Orbix2000
– IONA Orbix 6.1
– InterBus
– JacORB
– Borland VisiBroker
– Borland BES
Supporting cross-platform operation
– Windows 2000, Windows 2003, Solaris 8, Solaris 10
The CORBA NBI complies with the following standards recommended by the Tele
Management Forum (TMF):
TMF 513 V2.1
TMF 608 V2.1
TMF 814 V2.0 (IDL V2.1)
Network element (NE): It refers to the device in the network. The NE reports alarms to
the element management system (EMS) .
EMS: The network devices provided by Huawei can be managed by the iManager
U2000. The iManager U2000 is at the EMS layer and interconnects with the third-
party NMS through the NBI.
NMS: It refers to the NMS of a carrier.
CORBA NBI: It provides an interface for the superior NMS to access the EMS.
Querying the Current Alarms of the EMS and All NEs in Real-Time
This function allows the superior NMS to query the current alarms of the EMS and all
NEs and set alarm severity levels to filter the alarms. The filter for the notification
service does not affect the query result. The current alarm refers to a fault alarm that is
uncleared and unacknowledged, uncleared but acknowledged, or cleared but
unacknowledged. NMS can obtain the real-time alarms of the EMS and NEs. The EMS
detects the alarms returned to the caller. The NMS needs to perform this task
periodically to obtain the real-time alarms.
Filtering Alarms
This function allows the superior NMS to set the filtering rules for the EMS or NE
alarms and set the alarm severity levels, event type, and device type to filter the
alarms.
Alarm Synchronization
This function allows the superior NMS to synchronize alarm information with the EMS.
Resource changing report
This function allows the EMS to report the resource changing information to the
superior NMS .
Resource querying
This function allows the superior NMS to query the resource information such as the
main type of EMS resource, topology information of EMS, etc.
Service deployment
This function allows the superior NMS to deploy services such as SDH, WDM path
creation, active, deactive, delete, etc.
Current performance querying
This function allows the superior NMS to query the current performance data.
History performance querying
This function allows the superior NMS to query the historical performance data.
There are three parts of the CORBA interface: standard naming service, notifying
service and CORBA agent.
Naming service: provides the interface for the OSS to access the U2000 CORBA. The
uniqueness of the name of the EMS must be guaranteed in the NMS management
domain.
Notifying service: is responsible for the adding/deleting events monitoring, receiving
alarm/performance/report.
CORBA agent: transform the internal data of U2000 to the CORBA data complying
with the international standard and transform the request from OSS to the internal
data of U2000 to guarantee the integration of OSS and U2000.
IDL: Interface Definition Language. IDL is not a programming language and its only
purpose is to allow the CORBA interface being defined as a programming language
independent mode, and allow the inter-operation of applications programmed with
different languages. IDL can not be programmed and compiled, and is only applicable
to describe the CORBA interface and define the data type of the objects.
Language mapping defines how to translate the IDL file into different programming
languages. The third party software can be used such as TAO, JacORB. Huawei
uses TAO to translate CORBA language into C++.
NMS and EMS invoke functions such as getNEName{} to query and report alarm,
resource, and performance information.
When OSS connects to U2000, U2000 establishes a session between them. U2000
performs the “ping” every 30 seconds and if there is no reply to the “ping” for 4 times,
U2000 will abort the session; meanwhile, U2000 sends a heartbeat notifying message
to OSS every 30 seconds.
getAllManagedElements: Query the NE resource information of the EMS and all NEs
getAllActiveAlarms: Query the current alarms of the EMS and all NEs
getAllCurrentPMData: Query the current performance data of the EMS and all NEs
NT_ALARM: Alarm notifying
The interface connection type problem need to analyze the log file. It is complex. If
there is this type problems, please contact Huawei company.
At the beginning, the network and service are simple. We can use ICMP and Ping
command to manage and monitor the network. As time went by, the Ping command
cannot manage the network. How to develop the new NMS protocol which is easy to
the maintenance engineer is the next step for R&D. In this background SNMP (Simple
Network Management Protocol) is developed.
Many telecom level equipment support SNMP, such as Huawei Access and IP
equipment. If we enable the SNMP function, and then the U2000 is server for the
equipment. In this case, SNMP is a southbound interface for U2000.
Actually, SNMP is a type of NBI of U2000, which will transfer data to higher layer
OSS.
The relationship between SNMP and COBRA:
The basic function of SNMP and COBRA is to report the information to upper
level NMS;
SNMP is protocol which is applied between NMS and EMS or EMS and NEs;
but COBRA is only applied between NMS and EMS;
COBRA is more security than SNMP in data transfer.
SNMP is divided into NMS U2000 and AGENT. U2000, the NMS sends request to
Agent. Agent is a process or task residing in managed equipment. When Agent
receives the enquiry packet from the NMS, it performs decoding analysis and gets
value of management variable from relevant modules. Then it generates Response
message, sends the packet back to the NMS after it is encoded.
SNMP is the application layer protocol that defines the transfer of management
information between NMS and Agent.
To simplify the development of the Agent side, SNMP only defines two kinds of
operations --- Get and Set. Get is used to obtain management information from
managed equipment. And Set is used to configure managed equipment via setting
the value of variable.
NMS and Agent transfer management information to each other via packet. And
SNMP V1 only defines five kinds of packets:
Get Request packet: Used to get the value of specified management variable.
GetNext Request packet: Used to continuously get the values of a group of
variables.
GetResponse packet: Used to respond request, return value for request or
error type, etc.
Set Request packet: Used to set the specified management variable.
Trap packet: Used for managed equipment to send information to NMS
initiatively in urgent cases.
GetRequest and GetNextRequest are used to obtain information of the managed
object in NM. SetRequest is used to configure the managed object. These three kinds
of requests correspond with three kinds of SNMP messages. Agent responds them
via sending GetResponse message.
Trap is generated by Agent. It is used to report abnormal event of the managed
equipment to the NM. Agent will send Trap to notify NM when equipment gives alarm
or important data is changed by user/console/other NMs. When SNMP Manager
receives the Trap, relevant actions will be initiated, such as diagnosing fault via
polling, adopting recovery measures, modifying relevant database of the NM.
SNMP is base on TCP/IP, and it is in the application layer of TCP/IP. SNMP provides
one simple command set for communication, and it use UDP to send and receive
massage between NMS and Agent.
Version: version of SNMP;
Community: user name of NMS to login Agent.
SNMP PDU:SNMP PDU(Protocol Data Unit), SNMP protocol message
payload, querying and acknowledge command and so on.
Normally:
The OSS will send message to Agent, such as request operations, after the
Agent receive the message, at first, it will check the version, community and
operation objective of SNMP message. If they are matched, the Agent will give
the feedback message and report what the OSS want to know.
In emergency:
Such as the NIC port is down and repaired, and then the Agent will send
TRAP message to OSS to establish the link again.
1. The agent receives an SNMP request packet from the NM station through UDP
port 161.
2. The agent decodes the packet based on ASN.1 basic coding rules and represents
it in an internal data structure. The agent discards the packet if there is a decoding
failure.
3. The agent gets the version number from the packet. The agent discards the packet
if the version is inconsistent with the SNMP version it supports.
4. The agent gets the community name from the packet. The community name is filled
by the NM station that sends the request. If the community name is inconsistent with
that of the agent, the packet is discarded. A trap message or an Inform packet is
generated simultaneously.
5. The agent gets PDUs from the authenticated ASN.1 object. If the agent fails to get
the PDUs, the agent discards the packet; otherwise, the agent processes the PDUs.
6. The agent processes PDUs differently and gets the management variables of the
corresponding protocol modules by searching nodes that correspond to management
variables in the MIB.
7. The agent encapsulates the values of management variables in a PDU, uses the
source IP address and port of the request packet as the destination IP address and
port, and adds the SNMP version number. A response packet is then generated. After
being coded, the response packet is sent to the NM station.
After we add the SNMP Agent instant, we can start and stop the process by right
click on the process.
Entrance
Choose Administration > NE Communicate Parameter > Default Access
Protocol Parameters from the main menu.
In the Default Access Protocol Parameters tab, click the SNMP version tab to
switch to the page for configuring protocol parameters.
Configure the NE SNMP parameter template as follows:
Add a parameter template.
Click Add. After setting all the parameters in the parameter setting
area at the bottom of the window, click OK.
Modify a parameter template.
For U2000 SBI, we need to configure on U2000 and configure SNMP parameters in
the managed equipment, such as DSLAM and Router.
If the parameters are the same. The SNMP interface will work normal.
Pre-configuration Tasks
Before Configuring, complete the following tasks:
For more detailed steps, please refer 《 Northbound SNMP Interface User Guide
(U2000 V100R002C01) 》
Item Index
Maximum concurrent
10
NMS connections
Alarm Forwarding Not less than 60 alarms per second (three
capacity NMSs connected)
security management strategy: The security management function provides the role-
based and domain-based management for the U2000 and NEs. With this function, the
U2000 can also monitor in real time the users that already log in to the U2000 and
NEs. In this way, the network and data security ensures that login failures or illegal
operations are captured.
After installing U2000 on Solaris platform, there will be three system users: root,
sybase, nmsuser. Usually we use nmsuser to log in the JDE and start U2000 server.
root: this user is the super user of the OS and it has the highest authority in the
system. The root user is used to create other users with relevant authorities.
The default password of root is rootkit.
sybase: this user is the database operation user. It is responsible for setting
Sybase environment variables, installing, maintaining and managing the
Sybase database, As the owner of the directory /opt/sybase, the sybase user
can manage the Sybase database, for example, configuring Sybase
environment variables and starting/stopping the Sybase service.
nmsuser: During the U2000 installation, the software creates a nmsuser user
of the operating system automatically. The nmsuser user is responsible for
setting environment variables of the U2000 server and starting the U2000
server. The nmsuser user has all the rights of its home directory. The
file .profile in this directory records environment variables for the U2000
running.
After database initialization, there are two default users: sa and NMSuser.
sa is the super user of the database. The default password is ‘changeme’.
NMSuser is the database user which is used for U2000 to login database. The
default password is NMSuser
NM User: The one to login U2000 Server.
NE User: The one to login NEs by U2000 or other software.
Confidential Information of Huawei. No Spreading Without Permission
iManager U2000 Security and Data Management P-6
The logs include the U2000 security log, the U2000 operation log, the system logs
and the NE log. The logs record operations performed by operators to the U2000 or
an NE.
Security logs record the security operations that the user performs in the
U2000, for example, login, logout, locking, and unlocking. By viewing the logs,
an administrator can track and check the security operations of the users.
Operation logs record the information about the non-security operations that
the user performs in the U2000, for example, creating subnets, and muting
and unmuting the alarm sound. By viewing the logs, an administrator can track
and check the user operations.
System logs record the operations or tasks that the U2000 performs
automatically, for example, scheduled tasks and system tasks.
The NE syslog running logs record the running information of U2000 NEs. By
obtaining all NE syslog running logs from NEs through the U2000, you can
view the NE syslog running logs managed by the U2000 through the U2000,
instead of viewing the NE syslog running logs on each NE.
Procedure:
Choose Administration > Log Management > Query Operation Logs. You can also
select Query System Logs or Query Security Logs to browse system or security logs.
In the Filter window as follows, set the filtering conditions, and then click OK.
Right-click in the query window and perform the operations listed in the picture.
Procedure:
Choose Administration > Log Management > Operation Log Statistics
from the main menu. You can also select System Log Statistics or Security
Log Statistics items.
In the Statistic Filter window, set the statistical items and statistical conditions,
and then click OK.
Dump log can avoid that the logs reach the maximum storage capacity of the
database and that the system performance is degraded.
There are three types of dump: scheduled dump, manual dump and overflow dump.
Setting the log timing dump:
Choose Administration > Task Schedule > Task Management from the
main menu.
In the Task Management window, select Database Capacity Management
in the navigation tree.
Double-click the Operation Log Dump task in the task list. You can configure
the timing dump parameters as follows and the presentation. The file type
support CSV and XML.
In the network planning, you can configure and plan the data transmission according
to certain network security isolation policy. In this way, you can ensure the security
and reliability of the network and data of the U2000 system, and avoid illegal login
and data loss or theft.
The ACL (Access Control List) is a secure access control mechanism. It restricts a
user to log in to the server through only the clients with the specified IP addresses.
Procedure:
Choose Administration > NMS Security > ACL from the Main Menu. The ACL
dialog box is displayed
Click Add and the New System Access Control Item box is displayed
Set parameters of the IP address or network segment, and click OK
Click Close to close the System ACL dialog box
Procedure:
Choose Administration > NMS Security > NMS User Management from the
Main Menu.
In the NMS User Management area, double-click Users and select a desired
user.
In the right-hand pane, click the ACL Settings tab.
Select Use all the ACLs in the system or Use the specified ACLs according to
requirements.
Click Set ACL and the ACL dialog box is displayed.
NOTES:
If you select Use System ACL, the U2000 user can log in to the clients
corresponding to all IP addresses or network segments in the list by default.
If you select Use User ACL, you need to select an IP address or network
segment of the client that the U2000 user can log in.
Procedure:
Click Add and the New System Access Control Item dialog box is displayed.
Set parameters of the IP address or network segment, and click OK.
Click Close to close the Set ACL dialog box.
Procedure:
Optional: If Use the specified ACLs is selected, you need to check the Access
Permitted check box corresponding to the IP address or network segment.
Click Apply.
Procedure:
Choose Administration > NMS Security > Security Policies… from the Main
Menu. The Security Policy dialog box is displayed
In the Security Policy dialog box, click the Password Policy tab.
Set the basic and advanced parameters of the password policy as required.
Click OK.
In the Security Policy dialog box, click the Account Policy tab.
Set the account policy as required.
Click OK.
Procedure:
Log in the Msuite system.
In the main menu ,select ” System > Change Password”.
The U2000 remote maintenance function allows login to the U2000 server from a
remote client. Strict management for the remote maintenance user not only ensures
U2000 system security, but also makes maintenance operations easier.
Procedure:
Choose Administration > NMS Security > Remote Maintenance User
Management from the Main Menu. The Remote Maintenance User
Management dialog box is displayed. Enable the remote maintenance user
and set its other parameters
Set the Operation Authority. You can select Query or Configuration as needed
Set Valid Forever or Not to No
Set Validity Period
Click OK
By DCN or other types, you can access the U2000 server by remote maintenance
user. Then maintenance command can be done by this function.
Remote maintenance client login procedure.
On the Windows platform, click startup_cmdclient_global.bat under the
\U2000\client directory;
Input the user and password, then the windows display as the slide;
Double click the NE, and input the command.
User: The user name and password of a U2000 user identifies the U2000
management rights entitled to the user. When a user is added to a user group, the
user has all the operation rights of this user group. The U2000 provides a default user:
admin. It is the super user of the system and has a higher authority than the system
administrator group. You can neither modify the rights of the user admin, nor add user
admin to other user groups.
Procedure:
Choose Administration > NMS Security > NMS User Management from the
Main Menu
In the NMS User Management area, double-click Users, right-click and choose
New User from the shortcut menu
Complete the information in the New User dialog box
For network maintenance purposes, you can create U2000 users and assign different
authorities to them. Apart from user admin, all the users to operate the U2000 need to
create corresponding accounts, that is, the U2000 user accounts.
You can specify the user group of a U2000 user so that the user can have the
management rights and operation rights of the user group.
Usually, we assign the user with certain user authorities by adding the user to a user
group rather than assigning specific authorities for the user.
Procedure:
Choose Administration > NMS Security > NMS User Management from the
Main Menu
In the NMS User Management area, double-click Users and select a desired
user
In the right-hand pane, click the Groups tab
Optional: Select a desired user group and click Delete
Click Add and the Add User Groups dialog box is displayed
Select a user group that you want to add, and click OK
In the right-hand pane, click the Operation Rights tab
Optional: Select a desired user operation rights and click Delete
Click Add and the Add Rights dialog box is displayed
Select a user group that you want to add, and click OK
User Group: This is a collection of the U2000 users that have the same management
rights. The default user groups are maintainer group, manager group, monitor group,
operator group and security manager. The attributes of the user groups include name,
description, member and authority.
Procedure:
Choose Administration > NMS Security > NMS User Management from the
Main Menu.
In the NMS User Management area, double-click User Group, right-click and
choose New User Group from the shortcut menu. In the New User Group
dialog box that is displayed, input the information of a new user group.
Click OK.
If you want to add one or more authorities to a user, you can select the
user that you want to set the authority directly. Select the Operation
Rights tab, and click ‘select’ to add the corresponding operation
authorities to the user.
Procedure:
Choose Administration > NMS Security > NMS User Management from the
Main Menu
In the NMS User Management area, double-click User Groups, and select a
U2000 user group
In the right-hand pane, click the Operation Rights tab
Optional: Select one or more desired operation authorities and click Delete
Click Select and the Select Operation Rights dialog box is displayed
Select the operation and operation set
Click OK
Procedure:
Choose Administration > NMS Security > NMS User Management from the
main menu
In the NMS User Management navigation tree, expand the User Groups node,
and then select a user group
Click the Domain tab to view the managed domain of the user group
Click Select button. In the Select Domain dialog box, select the devices and
object sets.
Click OK
You can back up and restore the U2000 data in two ways: Back up and restore all
data in U2000 databases, and back up and restore the U2000 network configuration
data by using scripts.
The following data is not backed up when you back up the U2000 database:
The data save at the NE side that cannot be uploaded.
The custom options of the system.
Comparison of Two Data Maintenance Methods
Backing up and 1. Backs up the structure and contents of The backed up data for a
restoring all data the U2000 database. The data is in the certain type of database
in the U2000 binary mode. cannot be restored to the
databases 2. Backs up all data. data for a different type of
3. The processing speed is fast, and the database.
backup file is big.
Backing up and 1. Exports the configuration data in the This method is usually
restoring the U2000 to a txt file that is similar to the used to upgrade the
U2000 network MML format. This is done to save data. U2000.
configuration data You can directly understand the
by using the script configuration contents of the txt file.
files 2. Backs up only some of the data,
including the basic configuration data, port
naming data and user-defined data.
3. The processing speed is slow and the
backup file is very small.
Back up is a method used to store important data to prevent the damage of the
original data. You can back up network configuration data, alarm data and
performance data.
Dump is a method used to store the log information in databases as operating system
files in text format, to clear database space. The dumped objects are various types of
logs, including alarm events, abnormal events, operation logs and different types of
performance events.
Procedure :
Choose Administration > Back Up/Restore NMS Data > Database Backup
from the Main Menu
Set a backup directory for the server, and click Backup. The U2000 starts to
back up the database. A progress bar is displayed showing the status of the
operation.
Notes: The default directory for database backup is as below:
On the UNIX platform, /U2000/server/var/backup
On the Windows platform, d:\U2000\server\var\backup
Procedure:
1. Login to the U2000 client.
2. Choose Administration > Task Schedule > Task Management from the main
menu.
3. Click New. The New Task dialog box is displayed.
4. Select DB Backup as the task type and enter a name for the scheduled task.
Select Period as the run type. Then click Next.
5. In Time Setting, set the planed start time of the task. In Period Setting, set
the planed period and execution times of the task. Then, click Next.
6. Select Back up the data to the local server and enter a backup path on the
local server. Then click Finish. The created scheduled task is displayed in the
Task Management window.
This method is usually used to upgrade the U2000 and to back up and restore the
basic configuration data for a single NE. This method also restores the user-defined
data. The new U2000 version is compatible with the scripts of the old version.
Procedure:
Choose Administration > Back Up/ Restore NMS Data > Import/Export Script
File from the Main Menu
Select a file format. Then select a script file type from the Script File Type field
Select the NE for which you want to export script files from the Export NE List
Click Create File Directory to create a directory where the exported script files
are to be saved
Enter the directory name and click OK
Select a directory and click Apply
In the Confirm dialog box, click OK. A progress bar appears showing the
status of the export
NOTES:
The script file is saved on the U2000 server. On Windows, the backup
directory is \U2000\server\script; on UNIX, the backup directory is
/opt/U2000/server/script. You can create a new directory under it.
Procedure:
Choose Administration > Back Up/ Restore NMS Data > Import/Export Script
File from the Main Menu.
Click the Import option button.
Select the file format and select the script file type from the Script File Type
field.
In the Operation Directory List, select the directory where the script file is to be
imported is located.
Select the script file to import from the Import File List.
Click Apply. The system prompts you twice that the import of the configuration
script will result in data inconsistency between the U2000 and the NE.
Click OK. A progress bar appears showing the status of the import.
NOTES:
Before importing the script file, it is better to back up the U2000 database.
Procedure:
Choose Administration > Task Schedule > Task Management from the main
menu.
In the Task Management window, select Database Capacity Management,
Manual Dump or Overflow Dump in the navigation tree.
Double-click the task in the task list. You can configure the dump parameters
as the presentation. The file type support CSV and XML.
overflow dump :It is performed when the logs in the databases reach the maximum
storage capacity. You can specify the number of logs to dump.
Maximum Capacity : The maximum piece of data that can be saved when the
U2000 server works normally. If exceeded, the overflow occurs
scheduled dump : It is the alternative method of overflow dump, is optional. You can
set whether to create a scheduled task, and if you create a scheduled task you can
specify the schedule time and duration.
Overflow dump and periodic dump can work together. In this case, the U2000 dumps
the data or log according to the settings of overflow dump and periodic dump.
During the routine maintenance of the U2000, you can clear the unwanted log data to
save spaces for the computer.
Notes: Clearing the U2000 log data will directly delete the log data from the
database. This affects the fault location in future. You are recommended to
clear the database space by dumping.
Confidential Information of Huawei. No Spreading Without Permission
iManager U2000 Security and Data Management P-41
ISSUE 1.00
iManager U2000 Security and Data
Management Practice Guide
Table of Contents
Task 2 Starting and Shutting Down U2000 (Solaris HA System) (Optional) .................................... 5
1.2 Setting SSL Protocol Communication between Server and Client ................................... 9
1.7 Testing the Communication between the U2000 and the GNE ....................................... 18
1.8.1 Check the communication status between the U2000 and a non-gateway NE........ 18
1.8.2 Check the communication status between the U2000 and the GNE. ...................... 19
U2000 can be installed on the UNIX/Linux and Windows platforms, and it provides the same functions
The database always starts with the Operating System (OS), and you can check in by inputting the
$cd /opt/sybase/ASE-15_0/install
$ ./showserver
If it replies at least two processes as below, it means sybase has started correctly.
And then start the U2000 Server and the U2000 Client as follows:
Step Action
$cd /opt/U2000/server/bin
Step Action
$ ./startnms.sh
Method 1: Double-click the "U2000 System Monitor " icon on the desktop;
$cd /opt/U2000/client
$ ./startup_sysmonitor_global.sh
Enter the user, password and server. For example,
User: admin
3 Password: XXXXX (The initial password of the admin user is null. When you log in
to the system for the first time, the system requires you to change the password.)
Server: Local
Click <Login>
Notes:
4 Wait a few minutes until the NE Manager, Security Process, Topology Processr, etc.
processes of Automatic start mode are all in "Running" status. Then the U2000
server starts successfully.
Starting the U2000 Client
Method 1: Double-click the "U2000Client" icon on the desktop.
$cd /opt/U2000/client
$./startup_all_global.sh
Enter the user name, password and server. For example:
User: admin
Password: XXXXX (The same password as you login system monitor)
6 Server: <Local>
Notes:
If the UU2000 Server and the U2000 Client are on different computers, click
icon to edit the IP Address and port where the U2000 Server is installed.
7 Click <Login> to display the U2000 workbench.
In the Notification Area (window bottom right) there is the icon for MS SQL Server Service Manager.
Double-click the icon to see the status. If it is not in running status, then click Start.
And then start the U2000 Server and U2000 Client as follow:
Step Action
Method 1: Double-click the "U2000 System Monitor " icon on the desktop;
2
Method 2: In the directory C:\U2000\client, double-click
“startup_sysmonitor_global.bat”.
Enter the user, password and server. For example,
User: admin
3 Password: XXXXX (The initial password of the admin user is null. When you log in
to the system for the first time, the system requires you to change the password.)
Server: Local
Click <Login>
Notes:
4 Wait a few minutes until the NE Manager, Security Process, Topology Processr, etc.
processes of Automatic start mode are all in "Running" status. Then the U2000
server starts successfully.
Start the U2000 Client
Method 1: On the computer of the U2000 client, double-click the "U2000 Client"
“startup_all_global.bat”.
Enter the user name, password and server. For example:
User: admin
Password: XXXXX(The same password as you login system monitor)
6 Server: <Local>
Notes:
If the U2000 Server and the U2000 Client are on different computers, click icon
to edit the IP Address and port where the U2000 Server is installed.
7 Click <Login> to display the U2000 workbench.
Step Action
$cd /opt/U2000/server/bin
4 $ ./stopnms.sh
Step Action
You should start the OS of both the active and standby servers and the software such as
VxVM, VVR and VCS. Normally, the U2000 is not started automatically with the VCS. You
Step Action
Turn on the power supply of the active server. Login the Solaris as root user and the default
password for root user is rootkit.
1
The OS is automatically started and at the same time, VxVM, VVR and VCS are all started
automatically along with the OS.
Turn on the power supply of the standby server. Login the Solaris as root user and the default
password for root user is rootkit.
2
The OS is automatically started and at the same time, VxVM, VVR and VCS are all started
automatically along with the OS.
Run the following command to log in to the VCS interface on primary node.
3
# hagui &
Step Action
Select [File/New Cluster...], and input [Primary] in the “Host name” column, then click <OK>;
Here Primary is the hostname of the primary workstation. You can also enter the IP address of
the Heartbeat network service of the primary site
Input user name [admin] and password [password], then click <OK>;
Right-click AppService in the Object Tree and choose Online > Primary to start the U2000 on
6
the primary node.
Step Action
If the status of all resources in the AppService group is Online on Primary, the AppService is
7
normally started.
8 On the U2000 client computer, double-click the U2000 Client icon on the desktop.
Enter the User Name and Password of the U2000 client.
9
For example, the default super user name: admin; password: admin.
Step Action
Choose File > Exit from the Main Menu of U2000 client.
1
In the Confirm dialog box displayed, click OK to log out of the client.
2 Right-click AppService in the Object Tree and choose Offline > Primary to shut
Log in to the active server as the root user and run the following commands to
To check whether the VCS service is disabled normally, run the following
command:
If information about "had" and "hadshadow" is not detected, it indicates that the
Log in to the server of the standby site as the root user and perform the
5
preceding two steps to stop the VCS service on the server of the standby site.
Run the following command on both the primary and secondary nodes to keep
6 the data in the disk synchronous with the data stored in the memory:
Run the following command at both the primary and secondary nodes to shut
Step Action
On the NMS Maintenance Suite client, choose Deploy > Change Database
displayed.
# ./stopserver.sh
# ./startserver.sh
Step Action
Step Action
Run the ssl_adm -cmd setmode both command to change the SSL mode between
U2000 server and client.
The new communication mode takes effect after you restart the U2000.
Note:
Value Description
Step Action
Choose Administration > NMS Security > NMS User Management from the
1
main menu.
In the NMS User Management navigation tree, expand the User node, and then
2
select a user.
3 Click the ACL tab.
Click Set ACL, then click Add and the Add dialog box is displayed.
Step Action
5 Set parameters of the IP address or network segment, and click OK.
Click Close to close the ACL dialog box.
NOTE:
6 If you select Use all the ACLs in the system, you can not specify the ACLs for
the user.
If you select Use the specified ACLs, you can select some permitted access IP
address for the user.
Step Action
Choose Administration > NMS Security > NMS User Management from the main
1
menu.
In the NMS User Management navigation tree, expand the User node, and then
2
select a user.
3 Click the Details tab.
Modify the following user validity parameters: User account is disabled and
Password validity period(days).
5 Click Apply.
Step Action
1 Choose Administration > NMS Security > NMS User Management from the main menu.
Create the U2000 user NM_user1.
1. In the NMS User Management area, double-click User, right-click and choose New User
from the shortcut menu.
2. In the New User dialog box, complete the following information:
Name: NM_user1
Password: User1368
Confirm Password: User1368
3. Click OK.
Assign management domain to the user NM_user1.
4 1. Click Domain tab. Then click Select.
2. Select the devices and object sets as the following window.
3. Click OK.
Assign operation rights to the user NM_user1.
1. Click the Operation Rights tab and click Select.
2. In the Select Operation Rights dialog box, select the additional operation rights for the user
as following.
3. Click OK.
The added authorities are displayed in the Operation Rights list.
6 Set the IP address range of clients from which NM_user1 is allowed to log in.
Step Action
Choose Administration > DCN Management from the Main Menu.
Click OK in the Filter NE window. Then click Close in the Operation Result
1
dialog box.
Click the GNE tab.
Select the GNE to be modified, right-click and choose Modify GNE from the
2
shortcut menu.
In the Modify GNE dialog box displayed, set Gateway Type.
4 Click OK. In the Warning dialog box that is displayed, click Close.
Step Action
Choose Administration > DCN Management from the Main Menu.
1 Click OK in the Filter NE window. Then click Close in the Operation Result
dialog box.
2 Click the NE tab.
Select an NE. Double-click the Primary GNE1 field and select a GNE from the
3
drop-down list.
4 Click Apply. Click Close in the Operation Result dialog box.
5 Click Refresh.
Step Action
1 Choose Administration > DCN Management from the Main Menu. Click the NE tab.
Select an NE. Double-click GNE2 and select a GNE from the drop-down list.
Step Action
Choose Administration > DCN Management from the Main Menu. Click the
1
GNE tab.
Right-click the GNE that you want to change and choose Delete GNE from the
shortcut menu.
2
Click OK in the Confirm and Reconfirm dialog box. Click Close in the Operation
Result dialog box.
Step Action
Choose Administration > DCN Management from the Main Menu. Click the NE
1
tab.
2 Right-click a normal NE and choose Change to GNE from the shortcut menu.
In the Change to GNE dialog box, select the Gateway Type, and enter the IP
Address.
Step Action
1 Choose Administration > DCN Management from the Main Menu.
2 Click the NE tab.
3 Click Refresh to query the GNE switching status.
1.7 Testing the Communication between the U2000 and the GNE
Step Action
1 Choose Administration > DCN Management from the Main Menu. Click the
GNE tab.
2 Right-click the GNE to be tested and choose Test GNE from the shortcut menu.
3 Click Close in the Operation Result dialog box.
1.8.1 Check the communication status between the U2000 and a non-gateway NE.
Step Action
1 Choose Administration > DCN Management from the Main Menu.
2 Click the NE tab. Click Refresh to view the communication status of all NEs.
3 Select an NE. Right-click in the Communication Status column and choose Test
1.8.2 Check the communication status between the U2000 and the GNE.
Step Action
1 Choose Administration > DCN Management from the Main Menu.
2 Click the GNE tab. Click Refresh to view the communication status of the GNE.
3 Right-click an NE and choose Test GNE from the shortcut menu.
The Operation Result dialog box is displayed indicating the test result of the
4
GNE.
Step Action
Choose Administration >Back Up/Restore NMS Data > Database Backup
1
from the Main Menu.
Set a backup directory for the server, and click Backup. The U2000 starts to back
2
up the database. A progress bar is displayed showing the status of the operation.
Method 2: By Maintenance SUITE
Step Action
Log in to the U2000 MSuite.
# su - nmsuser
$ cd /opt/HWENGR/engineering
$ ./startclient.sh
The default user name and password are both admin. If the password has been
changed, enter the changed password.
2 Click Back Up and Restore > Back Up System Data.
3 Select Data Backup – Binary Mode (Recommended). Then click Next.
4 Select Backup the data to the local server.
5 Set the backup path on the local server. Then click Next.
The system starts the backup preprocessing and data backup process. A progress
6
bar is displayed to show the backup progress. Wait patiently.
Step Action
1 Log in to the U2000 client.
2 Choose Administration > Task Schedule > Task Management from the Main Menu.
On the Task Management page, Select DB Backup then click New.
4 Input DB Backup as the task name. Select Run Type as Period. Then click Next.
5 Configure the running time and period. Then click Next.
Select Back up the data to the local server and enter Backup Path on the Local Server. Then
6
click Finish.
Step Action
Choose Administration > Back Up/Restore NMS Data > Import/Export Script
2
File from the Main Menu.
Select TXT file format. Then select a script file type from the Script File Type
field.
3 NOTE:
To export the networkwide script file, select Networkwide Configuration File. Export the
following files to a specified directory: NE Port Naming File, NE Configuration File, NE List File,
NM Computer Information File, Service Actualization Script, Network Layer Information File,
Network Modeling and Design Information File, CEAS.
Select the NE for which you want to export script files from the Export NE List.
NOTE:
4
Specify the NE only when you export the NE Configuration File, NE List File, NE Port
Naming File and Networkwide Configuration File.
Click Create File Directory to create a directory where the exported script files are to
5
be saved.
6 Enter the directory name and click OK.
7 Select a directory and click Apply.
8 In the Confirm dialog box, click OK.
Step Action
Stop U2000 on the active server.
1
The current user is root user, and the Sybase database is started
2 Log in to the U2000 MSuite on the active server.
3 Select System > Initialize NMS from the main menu.
4 Click Next.
The system starts initializing the database and displays the initialization progress in a
5
progress bar. Wait patiently.
6 After the initialization is complete, click Finish.
Step Action
Stop U2000 server.
1
The Sybase or SQL server is started
2 Log in to the U2000 MSuite.
3 Select System > Initialize NMS from the main menu.
4 Click Next.
The system starts initializing the database and displays the initialization progress in a
5
progress bar. Wait patiently.
6 After the initialization is complete, click Finish.
Step Action
Stop U2000 on the active server.
1
The current user is root user, and the Sybase database is started
2 Log in to the U2000 MSuite on the active server.
3 Select Back Up and Restore > Restore System Data from the main menu.
4 Select Data Restore – Binary Mode(Recommended) and click Next.
5 Select Path to the file on the local server.
6 Enter the restoration path on the local server and click Next.
The system starts the restoration preprocessing and data restoration, and displays
7
the restoration progress in a progress bar. Wait patiently.
8 After the restore is complete, click Finish.
Step Action
Stop U2000 server.
1
The current user is root user, and the Sybase database is started
2 Log in to the U2000 MSuite on the active server.
3 Select Back Up and Restore > Restore System Data from the main menu.
4 Select Data Restore – Binary Mode(Recommended) and click Next.
5 Select Path to the file on the local server.
6 Enter the restoration path on the local server and click Next.
The system starts the restoration preprocessing and data restoration, and displays
7
the restoration progress in a progress bar. Wait patiently.
Step Action
Choose Administration > Back Up/Restore NMS Data > Import/Export Script
2
File from the Main Menu.
3 Click the Import option button.
Select the TXT file format and select Networkwide Configuration File from the
Script File Type field.
4 NOTE:
Service Actualization Script and NM Computer Information File are not
supported.
In the Operation Directory List, select the directory where the script file is to be
5
imported is located.
6 Select the script file to import from the Import File List.
7 Click OK. A progress bar appears showing the status of the import.
8 In the Import Subnet List, select the subnets to be imported. All subnets are
required to be selected.
Click Apply. The system prompts you twice that the import of the configuration
9
script will result in data inconsistency between the U2000 and the NE.
10 Click OK. A progress bar appears showing the status of the import.
Step Action
1 Open a terminal window in the server.
Run the following command as user sybase: (The default password of sybase user is sybase.)
$ /opt/sybase/ASE-15_0/install/showserver
2
if the server DBSVR and the backup server DBSVR_back are running, the status of databases
is normal.
Step Action
1 Choose Administration > Log Management > Query Security Logs from the main menu.
Step Action
1 Choose Administration > Task Schedule > Task Management from the main menu.
In the Task Type navigation tree, select Database Capacity Management > Security Log
2
Dump.
Step Action
Select Security Log Dump, then click Attribute to set period dump.
Step Action
1 Choose Administration > Task Schedule > Task Management from the main menu.
In the Task Type navigation tree, select Overflow Dump > Security Log Overflow Dump.
3 Select Security Log Overflow Dump, then click Attribute to set overflow dump.
Step Action
Step Action
1 Choose Administration > Task Schedule > Task Management from the main menu.
2 In the Task Type navigation tree, select Manual Dump > Security Log Manual Dump.
Step Action
Select Security Log Manual Dump, then click Attribute to browse manual dump settings.
Step Action
1 Choose Administration > Log Management > Query Operation Logs from the main menu.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Database Capacity Management >
2
Operation Log Dump.
3 Select Operation Log Dump, then click Attribute to set period dump.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Overflow Dump > Operation Log
2
Overflow Dump.
3 Select Operation Log Overflow Dump, then click Attribute to set overflow dump.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Manual Dump > Operation Log
2
Manual Dump.
Select Operation Log Manual Dump, then click Attribute to browse manual dump
3
settings.
Step Action
1 Choose Administration > Log Management > Query System Logs from the main menu.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Database Capacity Management >
2
System Log Dump.
3 Select System Log Dump, then click Attribute to set period dump.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Overflow Dump > System Log Overflow
2
Dump.
3 Select System Log Overflow Dump, then click Attribute to set overflow dump.
Step Action
Choose Administration > Task Schedule > Task Management from the main
1
menu.
In the Task Type navigation tree, select Manual Dump > System Log Manual
2
Dump.
Select System Log Manual Dump, then click Attribute to browse manual dump
3
settings.
Step Action
1 Log in to the Solaris operating system as user nmsuser.
Open a terminal window, and run the following commands to switch to user root:
2 % su - root
Password:password_of_user_root
Run the following commands to view the physical status of the disk on the current server:
3
# iostat -E
Run the following commands to switch to non-root user:
4
# exit
Step Action
In the My Computer window, select a disk, right-click, and choose Attribute from the shortcut
1
menu.
2 In the dialog box displayed, click the Tools tab.
3 In the Check Error area, click Start Check. Follow the prompts to check the disk status.
You can view the disk space of the server through sysmonitor or command lines. The following
Step Action
1 Log in to the Solaris operating system as user nmsuser.
Open a terminal window, and run the following commands to switch to user root:
2 % su - root
Password:password_of_user_root
Run the following command to view the disk space usage on the server:
3
# df -k
Step Action
4 In the screen output, view the space usage of the / and /opt directories.
Run the following commands to switch to non-root user:
5
# exit
Step Action
View the disk space of the server through sysmonitor or in the My Computer window.
1 You need to view the disk space usage of the operating system, SQL server, and U2000
mainly.
Step Action
1 Log in to the system as user root.
Delete the core files created by the system. These files are usually located in the
2 directories of /, /opt/U2000/server/conf and /opt/U2000/server/bin. The file names start
with core.
Delete the outdated and useless alarm dump files. The default path is
3
/opt/U2000/server/dump.
Delete the outdated and useless log dump files. The default path is
4
/opt/U2000/server/dump.
Delete the outdated and useless database backup files. The default path is
5
/opt/U2000/server/var/backup.
Delete the outdated and useless U2000 running logs. The default path is
6
/opt/U2000/server/log.
Delete other outdated and useless files, such as installation files and patch files of earlier
7
versions.
Step Action
1 Log in to Windows as the administrator user.
Delete the outdated and useless alarm dump files. The default path
2
is %IMAPROOT%\server\dump.
Delete the outdated and useless log dump files. The default path
3
is %IMAPROOT%\server\dump.
Step Action
Delete the outdated and useless database backup files. The default path
4
is %IMAPROOT%\server\var\backup.
Delete the outdated and useless U2000 running logs. The default path
5
is %IMAPROOT%\serve\log.
Delete other outdated and useless files, such as installation files and patch files of earlier
6
versions.
Step Action
1 Empty the Recycle Bin.
2 Delete the files in D:\U2000\client\log.
3 Delete other useless files.
Step Action
On the desktop of the computer that the network management system maintenance suite
locates in, double-click the U2000 NMS Maintenance Suite icon, the Login dialog box is
displayed.
Step Action
Step Action
1 In the network management system maintenance suite client, select the Instance tab.
Click the shortcut icon to refresh the information of the network management
system.
Step Action
On the network management system maintenance suite client, choose System >
1
Synchronizing the NMS Information. The Synchronize Data dialog box is displayed.
Step Action
Click OK. The progress bar of data synchronization is displayed. Wait until a message is
2
displayed indicating that data synchronization is complete.
3 Click OK. The deployment is successfully synchronized.
Step Action
Step Action
Step Action
On the client of the NMS Maintenance Suite, choose Deploy > Remove Component
1
from the main menu. The Remove Component dialog box is displayed.
2 Select the components to be removed and click OK.
3 Click OK. The deleting of the components is started.
Wait until the message Succeeded in removing the following components is
4
displayed. This indicates that deleting the components is complete. Click OK.
Step Action
1 Log in to the MSUITE client.
In the U2000 NMS maintenance suite, select Deployment Package tab, then click the
2 package you want to adds. Choose Deploy > Add Instance from the Main Menu or right
click to select Add Instance. The Add Instance dialog box is displayed.
Step Action
Step Action
1 Log in to the MSUITE client.
On the network management system maintenance suite client, select the instance whose
2
information you want to modify.
Choose Deploy > Modify the instance name and description from the Main Menu, and
3
the Modify the instance name and description dialog box is displayed.
4 Enter the new name and memo of the instance.
Click OK and wait until the prompt is displayed indicating that the instance information is
5
successfully modified.
6 Click OK.
Step Action
Step Action
you want to delete and choose Delete Instance from the shortcut menu.
4 A reconfirmation dialog box of Delete local Instance is displayed.
5 Click OK to start deleting the instance.
Wait. The The instance is successfully deleted dialog box is displayed indicating that
6
the instance is successfully deleted. Click OK.
Step Action
1 Log in to the MSUITE client.
On the network management system maintenance suite client, choose NBI > Configure
the CORBA interface instance. The NBI Config dialog box is displayed.
3 Click the General tab to perform the basic configuration of CORBA instance.
4 Click the Advanced tab to perform the advanced configuration of CORBA instance.
5 Click OK.
Step Action
In the network management system maintenance suite client, choose System > Exit.
1
The Exit dialog box is displayed.
2 Click OK to exit the network management system maintenance suite client.
www.huawei.com
Objectives
Upon completion of this course, you will be able to:
List the common analysis methods of fault localization
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 1
1
Contents
1. General Thoughts About U2000 Troubleshooting
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Others
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 3
2
General Thoughts About
Troubleshooting
Localization Client
sequence
1. operating system Server
2. database
3. server Database
4. client
OS
U2000 software
architecture Page 4
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.
Virus infection
Man-made mistake
Reinstall OS
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 5
3
General Thoughts About
Troubleshooting
Database Faults
Fail to Cause The database has been installed ever and there are some
install leftover information in OS.
The free space of the disk is not enough.
Method Delete the leftover information.
Check the space of the disk.
Fail to Cause The host name is changed.
start
The host IP is changed, also can lead to start database failure on
Solaris.
Method Change back to the old name
Reinstall the database , and select “upgrade” option on Window
OS
Comply the operation guide strictly to modify host IP and name on
Solaris OS.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 6
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 7
4
General Thoughts About
Troubleshooting
U2000 Software Faults
Fail to Cause The problem of client software.
start client
Fail to communicate with server.
Method Copy the files of the same version client from other
computer and cover the problem client.
Or reinstall the client.
Check the physical connection.
Check the software configuration.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 8
License fault Check whether the ESN information of U2000 server and the
license file are the same
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 9
5
General Thoughts About
Troubleshooting
U2000 Software Faults
Fail to backup the Check the running status of database
database Ensure that the firewall is closed
Ensure the authority of directory “dump” is writable for the
current user
Fail to restore the Check the running status of database
database
Ensure that all the processes of U2000 server are closed
The data can be restored only during the same version servers
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 10
Contents
1. General Thoughts About U2000 Troubleshooting
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 11
6
Case 1
Phenomenon Description
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 12
Case 1
Can not
be local
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 13
7
Case 2
Phenomenon Description
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 14
Case 2
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 15
8
Case 2
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 16
Case 2
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 17
9
Case 2
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 18
Case 3
Phenomenon Description
When the operator renames the computer, and restart the
computer, then the OS prompts as follows :
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 19
10
Case 3
Handling Process
1、 Rerun the setup program ,and select the “upgrade”, then SQL
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 20
Case 4
Phenomenon Description
The following IP address error occurs during the U2000 LCT installation.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 21
11
Case 5
Phenomenon Description
Network element (NE) managers of some devices at the U2000 NM
client are opened, appear in gray screen or abnormal display.
Cause Analysis
For the NE managers of some devices (such as PTN series, RTN
series, NG WDM series, and SLM 3160) incorrect browser settings
may cause abnormal display.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 22
Case 6
Phenomenon Description
On the U2000 NM, certain NEs are logged in and out frequently.
Cause Analysis
1. The number of NEs exceeds the NM management capability.
Handling Process
1. Check whether the number of NEs is within the NMS management capability.
Refer to the performance indexes indicated in iManager U2000 Description.
2. Check whether the disk space usage on the server exceeds 80%. If yes,
free up the disk. Backup and delete related files to free up disk space.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 23
12
Case 7
Phenomenon Description
An NM fails to communicate with a NE. The NE icon on the NM is
grayed out. In this case, an NE_COMMU_BREAK alarm is usually
sent.
Cause Analysis
1. Incorrect communication parameters on the NMS or NEs.
2. Data Communication Network (DCN) failure between the NMS and NEs.
3. Mutual interference between embedded Control Channel (ECC) of
subnetworks.
5. Too many non-gateway NEs carried by the gateway NEs.
6. ECC error codes.
7. Conflicts between NE users.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 24
Contents
1. General Thoughts About U2000 Troubleshooting
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 25
13
Case 1
Phenomenon Description
A U2000 NMS is running on a workstation, status is normal, one day,
the workstation is powered off abnormally, restart it, and input ”fsck -
y” , but the OS can’t be booted from hard disk.
Cause Analysis
The system is shut down abnormally, may be damaged the system
files, in rebooting procedure, the OS can’t switch to the CDE interface,
generally speaking, ”fsck -y” can repair the common errors, but if the
kernel is damaged or OS boot parameters are error, ”fsck -y” can’t
repair them.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 26
Case 1
Handling Process
4. Run “fsck –y ” and restart workstation again, but the fault still exists.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 27
14
Case 1
Handling Process
6、Execute format command to repair the slices table, as follows:
# format
Searching for disks...done
……
Specify disk (enter its number): 0
selecting c0t0d0
……
7、(Restore slice information)
format> label
Ready to label disk, continue? y(confirm)
format> quit
Restart the workstation, ensure whether the fault is solved .
8、If the fault still exits, and the hard disk has the abnormal sound, try to
replace the hard disk.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 28
Case 2
Phenomenon Description
When U2000 is upgraded, finish all the operation, then restart
the OS, the operator can’t login JDE desktop with user
nmsuser, only can use user name: root, password: rootkit to
login.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 29
15
Case 3
Phenomenon Description
One day, a workstation with U2000 is restarted, re-login again,
but fail to start server.
Cause Analysis
About the problem of starting server , the reader can consider it
in three aspect---database is running or not, database number
of user connections, environment variable.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 30
Case 3
Handling Process
1. Judge whether database is running;
2. Check the number of devices;
3. Check the environment variable, ensure the value of IMAP is
the path of installation.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 31
16
Case 4
Phenomenon Description
Because of requirement , the operator modify the IP of
workstation manually, then start U2000, but he can’t start
U2000, query the Sybase running status ,the database can not
be started(U2000 software and Sybase are installed on the
same workstation).
Cause Analysis
When modify the IP of workstation, not only modify host IP, but
also need to modify database IP, otherwise database can not
run.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 32
Contents
1. General Thoughts About U2000 Troubleshooting
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 33
17
Common Troubleshooting List
AppService abnormality
Data replication abnormality
Recovery from dual-active status
The primary node failure recovery
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 34
Case 1
AppService abnormality
If AppService stopped abnormally, the VCS will try to restart them. If
restarting fails, under the rules the system will switch to the secondary
node. The recovery strategies are as follows:
Clear fault of AppService on the primary and secondary nodes.
Temporarily freeze AppService on the primary and secondary nodes.
Troubleshoot the system as single node until the failure is removed.
Unfreeze AppService on the primary and secondary nodes.
Make AppService online on the primary node.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 35
18
Case 2
# vxprint –v
And the status of the data volume is not ACTIVE or ENABLED, the
status of datarvg and datarlk is RECOVER, That means data replication
is abnormal.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 36
Case 3
Dual-Active Recovery
When the network between the primary and secondary nodes is interrupted more
than 10 minutes, the secondary node will take over the server. Then the HA system
is running in a dual-active status that the primary and secondary nodes are both
active servers.
In the case of dual-active, the U2000 server processes are all running on both
primary and secondary nodes.
After the connection recovered from the fault, the system is running in a healing
status.
Healing status checking:
#vradmin -g datadg repstatus datarvg
Config Errors:
129.9.1.1: Primary-Primary
configuration
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 37
19
Case 4
Run the following command to forcibly disable the VCS on the primary and
secondary nodes.
Restart the primary and secondary nodes after the data replication is
complete.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 38
Summary
Basic Ideas and Methods for U2000 Troubleshooting
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 39
20
Thank you
www.huawei.com
21