System
V100R006C02
05
Date
2013-05-17
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 05 (2013-05-17)
Version
iManager U2000
V100R006C02
Intended Audience
This document describes the basic concept and principles of the SNMP NBI (northbound
interface). And it is also describes how to deploying and maintaining the SNMP NBI. This
document also provides the relationship between the SNMP NBI and license, description of
alarms reported by the SNMP NBI, the glossary, and the acronyms and abbreviations.
This document guides the user to understand basic operations of the SNMP NBI.
This document is intended for:
l
Application Developer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
Issue 05 (2013-05-17)
ii
Symbol
Description
WARNING
CAUTION
TIP
NOTE
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... }*
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Issue 05 (2013-05-17)
Convention
Description
Boldface
iii
Convention
Description
>
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Change the ID of the port for sending traps from the default value 982 to 6666.
Change the read community from the default value public to Changeme_123.
Change the write community from the default value private to Changeme_123.
Issue 05 (2013-05-17)
iv
Contents
Contents
About This Document.....................................................................................................................ii
1 Preview............................................................................................................................................1
1.1 Overview........................................................................................................................................................................2
1.2 Reading Guide................................................................................................................................................................2
2 Overview.........................................................................................................................................4
2.1 Introduction....................................................................................................................................................................5
2.2 Network Position............................................................................................................................................................5
2.3 Function..........................................................................................................................................................................6
2.3.1 U2000 MIB..................................................................................................................................................................6
2.3.2 U2000-T MIB..............................................................................................................................................................8
2.4 Security Mechanism.......................................................................................................................................................9
2.5 Standard Compliance....................................................................................................................................................11
2.6 Performance Indicators.................................................................................................................................................12
Contents
vi
Contents
C U2000 MIB..................................................................................................................................118
C.1 MIB Description........................................................................................................................................................119
C.2 Reported Alarm Field by U2000 MIB.......................................................................................................................119
C.3 U2000 MIB Trap........................................................................................................................................................124
C.3.1 Active Alarm Notification Trap..............................................................................................................................124
C.3.2 Active Alarm Synchronization Start Trap..............................................................................................................128
C.3.3 Active Alarm Report Trap......................................................................................................................................129
C.3.4 Active Alarm Synchronization End Trap...............................................................................................................133
C.3.5 KeepAlive Info (Heartbeat) Trap............................................................................................................................134
C.4 U2000 MIB Trap Sample...........................................................................................................................................136
C.4.1 Active Alarm Trap..................................................................................................................................................136
C.4.2 Active Alarm Synchronization Start Trap..............................................................................................................138
C.4.3 Active Alarm Synchronization Result Trap............................................................................................................139
C.4.4 Active Alarm Synchronization End Trap...............................................................................................................140
C.4.5 Heartbeat.................................................................................................................................................................141
D U2000-T MIB.............................................................................................................................143
D.1 MIB Description........................................................................................................................................................144
D.2 Reported Alarm Field by U2000-T MIB...................................................................................................................144
D.3 U2000-T MIB Trap....................................................................................................................................................147
D.3.1 Active Alarm Notification Trap..............................................................................................................................148
D.3.2 Active Alarm Synchronization Start Trap..............................................................................................................151
D.3.3 Active Alarm Report Trap......................................................................................................................................152
D.3.4 Active Alarm Synchronization End Trap...............................................................................................................155
D.4 U2000-T MIB Trap Sample.......................................................................................................................................156
D.4.1 Active Alarm Trap..................................................................................................................................................156
D.4.2 Active Alarm Synchronization Start Trap..............................................................................................................158
Issue 05 (2013-05-17)
vii
Contents
F Equipment Supported..............................................................................................................163
G Acronyms and Abbreviations................................................................................................165
Issue 05 (2013-05-17)
viii
1 Preview
Preview
Issue 05 (2013-05-17)
1 Preview
1.1 Overview
The overview describes main contents of each chapter.
Chapter
Description
2 Overview
B Configuration Parameters
C U2000 MIB
G Acronyms and
Abbreviations
Issue 05 (2013-05-17)
1 Preview
NOTE
The SNMP NBI supports two formats of management information bases (MIBs): U2000 MIB and U2000-T
MIB.
l Both HW-IMAPV1NORTHBOUND-TRAP-MIB.mib and HW-IMAPV2NORTHBOUND-TRAPMIB.mib refer to the U2000 MIB, which is used to manage transport, access, and datacom devices, or crossdomain devices. V1 and V2 indicate the SMI (Structure of Management Information) versions of the HWIMAPV1NORTHBOUND-TRAP-MIB.mib and HW-IMAPV2NORTHBOUND-TRAP-MIB.mib
respectively. The OSS selects a version based on its supported SMI version. SMI versions differ in syntax.
For details, see RFC 1155 and RFC 1902.
l T2000-NETMANAGEMENT-MIB.mib refers to the U2000-T MIB, which supports upgrades of original
transport NMSs and can manage only transport devices.
Intended
Audience
Purpose
Recommended Chapter
Network
Planning
Engineer
Application
Developer
Installation
and
Commissioni
ng Engineer
Data
Configuratio
n Engineer
System
Maintenance
Engineer
Issue 05 (2013-05-17)
2 Overview
Overview
Issue 05 (2013-05-17)
2 Overview
2.1 Introduction
The Simple Network Management Protocol (SNMP) northbound interface (NBI) is one of the
NBIs provided by the U2000. The operational support systems (OSSs) can access U2000 by the
SNMP NBI to monitor and manage alarms in Huawei equipment networks.
The SNMP protocol consists of a set of standards for network management and is the most
widely used protocol in TCP/IP networks. TCP is short for Transmission Control Protocol and
IP is short for Internet Protocol.
Huawei developed the SNMP NBI for the U2000 in compliance with industry standards. With
this NBI, OSSs can interconnect with the U2000 quickly and manage alarms on the network.
NOTE
OSSs are computer systems used by telecommunications carriers to manage performance, inventories,
services, and faults of network equipment efficiently. By function, OSSs can be classified into the service
assurance OSS, the service provisioning OSS, and the inventory management OSS.
In this document, OSSs cover upper-layer NMSs and third-party NMSs (NMS is short for network
management system). Currently, the SNMP NBI supports alarm management only and the OSS is usually
a service assurance OSS.
Issue 05 (2013-05-17)
2 Overview
Get/Set
SNMP Trap
Northbound SNMP
Interface
U2000
Device Network
NEn
NE1
NE2
OSS:
The SNMP NBI can support alarm management only. Generally, the OSS
indicates the service assurance OSS.
U2000:
NE:
Network Element
2.3 Function
The SNMP NBI supports two types of management information bases (MIBs) for different
functions. Telecommunication carriers can select an appropriate MIB to interconnect managed
devices with the OSS for network operation and maintenance (O&M) based on the following
principles.
2 Overview
U2000
At the U2000 side, the primary functions are:
l
Reporting alarms
Reporting heartbeat
NOTE
To enable this function, set third-party NMS parameters only on the U2000 when deploying the SNMP
NBI instead of configuring the OSS. Alarm information will be received at the preset port of the OSS
server.
After receiving alarms from the equipment or the U2000, the SNMP NBI reports these alarms
to the OSS by means of standard SNMP trap messages.
The SNMP NBI periodically reports heartbeat to the OSS. Based on the heartbeat, the OSS
determines whether the connection with the SNMP NBI is proper.
For details on trap messages, see C.3 U2000 MIB Trap.
Function
Description
Subscribi
ng alarms
Subscribes alarms by alarm severity and alarm category. You can set the severity
and category when deploying the SNMP NBI.
Sets the alarm field or variable binding (VB).
Reporting
alarms
Reporting
heartbeat
OSS
At the OSS side, the primary functions are:
l
Acknowledging/Unacknowledging alarms
Clearing alarms
NOTE
Ensure that the OSS is connected to the SNMP NBI properly before the query function is enabled.
Issue 05 (2013-05-17)
2 Overview
Function
Description
Synchronizing
alarms (querying
current alarms)
Querying alarms by
criteria
Reports alarms by alarm severity and category. The filter criteria are
specified during alarm subscription.
You can change filter criteria in real time when loading the U2000
MIB.
Changing filter
criteria in real time
Changes filter criteria using the Set operation when the SNMP NBI
is running.
The change will take effect without restarting the SNMP NBI.
Acknowledging/
Unacknowledging
alarms
Clearing alarms
U2000
At the U2000 side, the primary function is automatic alarm reporting.
NOTE
To enable this function, set third-party NMS parameters only on the U2000 when deploying the SNMP
NBI instead of configuring the OSS. Alarm information will be received at the preset port of the OSS
server.
After receiving alarms from the equipment or the U2000, the SNMP NBI reports these alarms
to the OSS using standard SNMP traps. For details, see D.3 U2000-T MIB Trap.
Issue 05 (2013-05-17)
2 Overview
Function
Description
Subscribi
ng alarms
Subscribes alarms by alarm severity and alarm category. You can set the severity
and category when deploying the SNMP NBI.
Reporting
alarms
OSS
At the OSS side, the primary function is querying current alarms on the U2000 (current alarms
are uncleared alarms). The OSS uses the Set operation to query these alarms.
NOTE
Ensure that the OSS is connected to the SNMP NBI properly before the query function is enabled.
To query current alarms on the U2000, the OSS issues the query begin command (value: 1) in
the Set operation. After receiving the command, the SNMP agent queries current alarms from
the U2000 and reports the result to the OSS. If there are too many alarms and the query needs
to be stopped, the OSS issues the query end command (value: 0) in the Set operation. After
receiving the command, the SNMP agent stops querying and does not report the result to the
OSS.
For details on alarm synchronization, see 6.2.2 Synchronizing Alarms.
For details on traps, see D.3 U2000-T MIB Trap.
Function
Description
Querying
all current
alarms
Reports all alarms by default. You can stop alarm synchronization using the Set
operation.
Querying
alarms by
criteria
Reports alarms by alarm severity and category. The filter criteria are specified
during alarm subscription.
Issue 05 (2013-05-17)
2 Overview
v1/v2c use
community name
based security
mechanism
v3 uses user
based security
mechanism
Before the Get, Get Next, or Set operation, the NMS must know the read and write
community names configured for the agent.
For trap and inform packets, the community name is the read community name configured
for the agent.
NOTE
SNMPv3
The security mechanism of SNMPv3 is user-based. In terms of security, SNMPv3 emphasizes
data security and access control and therefore offers a higher level of security than SNMPv1 and
SNMPv2c.
In data security, SNMPv3 provides protection for SNMP packets in the following ways:
l
In access control, the NMS performs security checks on managed objects (MOs) based on
SNMPv3.
Issue 05 (2013-05-17)
10
2 Overview
Security Level
Table 2-1 shows security levels supported by the SNMP versions.
Table 2-1 Security Level
Version
Security Level
Authenticatio
n
Data
Encryption
Description
v1
Without
authentication
and encryption
Community
None
Uses only
community
names for
access
authentication.
v2c
Without
authentication
and encryption
Community
None
Uses only
community
names for
access
authentication.
v3
Without
authentication
and encryption
User name
None
v3
With
authentication
and without
encryption
MD5 or SHA
None
Uses MD5 or
SHA algorithms
for
authentication.
v3
With
authentication
and encryption
MD5 or SHA
AES or DES
Uses MD5 or
SHA algorithms
for
authentication;
AES or DES
algorithms for
data encryption.
NOTE
11
2 Overview
SNMPv2c: the second release version. Some data types and protocol applications are added.
For details, see RFC1902.
SNMPv3: the latest release version. The security mechanism is reinforced. For details, see
RFC2571, RFC2572, RFC2573, RFC2574, and RFC2575.
Issue 05 (2013-05-17)
Indicator
Description
10
12
Issue 05 (2013-05-17)
13
3.1 Overview
SNMP is one of the widely applied NMS protocols in the TCP/IP network.
As a widely applied industry standard for the NMS protocols, the SNMP aims:
l
To help the manager to search and modify the information, and locate faults at any node
in the network.
To help the manager to diagnose the faults, configure the capacity, and generate reports.
In SNMPv3, both the NMS and the agent are called an entity.
MIB
SNMP
NMS
Agent
Module1
Module2
Module3
NMS
An independent system that runs network management applications.
The NMS performs the following operations:
Send query packets to NEs.
Receive responses or traps from NEs.
l
Issue 05 (2013-05-17)
SNMP agent
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
MIB
A collection of equipment that the agent can query or set.
The agent queries the MIB for required operations.
SNMP
An application-layer protocol carried over UDP in the TCP/IP structure.
Exchanges management information between the NMS and agents.
Figure 3-2 shows the position of SNMP in the TCP/IP family.
Figure 3-2 Position of SNMP
SNMP
UDP
IP
Link Layer
Physical Layer
NOTE
For the SNMP NBI, the agent is running on the U2000 and the NMS refers to the OSS. Currently two MIBs
are supported: U2000-T MIB andU2000 MIB. For details, see C U2000 MIB and D U2000-T MIB.
GetNextRequest
GetRequest
NMS
SetRequest
Agent
GetResponse
Trap
Issue 05 (2013-05-17)
15
GetRequest: The PDU that the NMS uses to visit the agent and obtains one or several
parameter values.
GetNextRequest: The PDU that the NMS uses to visit the agent and obtains the next
parameter value.
SetRequest: The PDU that the NMS uses to visit the agent and sets one or more parameter
values.
GetResponse: The PDU that the agent uses to return one or more parameter values to the
NMS as responses to GetRequest, GetNextRequest, and SetRequest packets.
Trap: The PDU that the agent uses to send traps to inform the NMS of important events or
state changes that occurred in NEs.
GetRequest, GetNextRequest, and SetRequest packets are sent from the NMS to agents while
GetResponse and trap packets are sent from agents to the NMS.
3.4 MIB
MIB is a key part of the SNMP network management framework.
NOTE
For U2000, the MIB defines managed objects that are used by the function interfaces of the SNMP NBI. These
definitions are extremely important for the U2000 in that they determine what operations the OSS can perform
and what network management information the OSS can obtain.
The MIB covers all managed objects (MOs) and refers to a group of SNMP-based entities. The
MIB structure resembles a tree, so it is also called a MIB tree. Each MO is mapped to a leaf
node, also called an object or object identifier (OID). The MIB tree is static in that after the agent
is started and the MIB is initialized, the NMS queries or modifies MOs based on the current
MIB. The NMS manages the MIB in read and write mode.
All MOs in a network are displayed as a leaf node in the MIB tree. An MO is identified by OID,
a unique path that originates from the root node to the leaf node.
An OID consists of a set of integers greater than or equal to 0 and is used to identify an MO in
the MIB tree. The structure of management information (SMI) ensures that an MO is mapped
to a unique OID.
Once the MIB file is released, OIDs are bound to related MOs and this binding cannot be
modified. A MO in the MIB cannot be deleted, but can be set to obsolete indicating that this
MO is not no longer used.
Issue 05 (2013-05-17)
16
Figure 3-4 gives an OID example: In the MIB tree, the MO mgmt is marked { iso(1) org
(3) dod(6) internet(1) mgmt(2) } or simply 1.3.6.1.2.
Decoding the packet based on basic encoding rules of ASN.1 and representing it in an
internal data structure
The agent discards the packet if some errors cause the decoding failure.
2.
3.
Issue 05 (2013-05-17)
17
4.
5.
6.
The NMS performs the same operations as the agent, and displays the final result.
SNMPv1
l
Mutual access to management information between the NMS (also called SNMP manager)
and SNMP agent.
Operations include:
Get
Set
Trap
The OSS must get the community information from the U2000 administrator.
SNMPv2c
SNMPv2 inherits all functions in SNMPv1 and provides the following new features:
l
Operations include:
GetBulk
Inform
Report
The format of traps is modified to the same as that of the Get and Set packets.
The OSS must get the community information from the U2000 administrator.
Issue 05 (2013-05-17)
18
SNMPv3
SNMPv3 inherits all functions in SNMPv2 and provides the following new features:
l
The OSS must get the SNMPv3 information from the U2000 administrator, including security levels, user
names, authentication passwords, and encryption passwords.
Issue 05 (2013-05-17)
19
20
Issue 05 (2013-05-17)
21
4.1 Overview
This topic describes the background information and the terms involved in the process of
deploying and configuring the northbound interface.
Attention Item
l
If you do not install the northbound interface component during the installation of the
U2000, you need to add it manually.
CAUTION
l After the northbound interface component is installed or added, you need to add a
corresponding instance and configure parameters. Then, the U2000 can start the NBI-related
process.
l After initializing the database of the U2000, you need to configure the northbound interface
instance again.
l After the northbound interface instance is configured, you need to restart all the NMS
services.
l You can configure only one IP address for one network interface. It is not allowed to set
multiple IP addresses for the same network interface. It is suggested that configure multiple
network interface for multiple IP address.
l If the NAT is used to transform addresses between the Msuite server and clients, deploy the
NBI on the Msuite client that installed on the U2000 server. Otherwise, the NBI may be
failure to deploy.
l The U2000 server and the OSS must can communicate with each other. Otherwise, the OSS
cannot interconnect with the NBI of the U2000. Therefore, if the U2000 server is configured
with multiple network interface cards (NICs) and the NICs are in different network segments,
set the IP address for connecting to the OSS as the IP address of the U2000 server.
l You must configure the northbound interface again after the IP of NMS changed.
Terms
The following explains certain confusable terms:
l
Component: It is the software functional unit that you can choose to install. Each component
can include multiple deployment packages.
Issue 05 (2013-05-17)
22
Instance: It is a physical process that appears after the deployment package is deployed.
You can add the instance during the installation of the U2000, or add the instance through
the Msuite after the U2000 is installed.
NOTE
l Instance names are irrelevant with process names queried on the System Monitor. You can change
instance names by using the Msuite.
l The type of northbound interface deployment package is System single-instance.
Msuite
Through the GUI of the Msuite, you can conveniently deploy the northbound interface.
The Msuite is a graphical maintenance tool developed for the Huawei iManager U2000, a type
of Huawei network product. The Msuite is used to debug, maintain, and redeploy the U2000.
Refer to the Msuite part of the iManager U2000 Administrator Guide for the details about the
Msuite.
For different operating system, the configuration requirements of U2000 is different, refer to the
corresponding Software Installation Guide for more information.
Hardware Configuration
In practice, the U2000 SNMP interface and the U2000 server run on the same PC or SUN
workstation. The hardware should be well configured enough to ensure the proper installation
and running of the U2000 server. Any additional hardware configuration is not required the
U2000 SNMP interface.
For details of hardware requirements of U2000 Server, refer to section Configuration
Requirements in the iManager U2000 Software Installation Guide.
Software Configuration
The function of U2000 SNMP interface is implemented based on the ORB technology of the
SNMP. Since the the SNMP is integrated into the U2000 installation software, no additional
software configuration is required for the installation of the U2000SNMP interface.
For details of software requirements U2000 Server, refer to section Configuration
Requirements in the iManager U2000 Software Installation Guide.
Issue 05 (2013-05-17)
23
License
The U2000 controls the functions and available resources of the SNMP NBI through a license.
If you want to enable the SNMP interface, you need to purchase the U2000 license. Ensure the
license support SNMP interface function before deploying the SNMP NBI.
For details, see A Relations Between License and SNMP Interface. If the license does not
support the functions or resources needed, contact Huawei engineers to apply for the license.
For the license introduction and information on how to apply for a license, see section Applying
for and Updating the U2000 License in the iManager U2000 Administrator Guide.
Context
l
Through the GUI of the Msuite, you can conveniently deploy SNMP NBIs.
SNMP NBI is an optional component of the U2000. A license is required for using this
function.
If you do not install the SNMP interface component during the installation of the U2000,
you need to manually add it.
The SNMP interface component is a single-instance system. Therefore, only one instance
can be deployed.
After the northbound interface (SNMP) server component is installed or added, you need
to add a corresponding instance and configure parameters. Then, the U2000 can start the
SNMP-related process.
After initializing the database of the U2000, you need to configure the SNMP NBI instance
again.
Issue 05 (2013-05-17)
24
No
Yes
Deploy for
the first time?
No
Yes
Add the Northbound
Interface Component
Configure the Northbound
Interface
Test the
Norhtbound Interface
End
CAUTION
l Collect general parameters only and use default values for advanced parameters.
l For U2000 upgrades, select the MIB structure carefully by referring to B.2.9 MIB Frame.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.
Issue 05 (2013-05-17)
25
Sample
Description
IP address
10.71.227.2
03
6666
Up-layer
NMS server
port to receive
the request
9812
IP address
10.70.71.97
SNMPv1/v2c
SNMPv3
Alarm Filter
Port to receive
trap
6666
Read
Community
Changeme_
123
Write
Community
Changeme_
123
user name
admin
Password
Authentication
U2k_snmpv
3
Password for
Privacy
u2000_SN
MP
Alarm Level
Critical
Major
Alarm Category
Fault Alarm
Sample
Description
Heartbeat
Need heartbeat
Heartbeat Period:
60 s
Issue 05 (2013-05-17)
26
Item
Sample
Description
N/A
Reported
Notificatio
n
Reporting
Mode
Trap
Trap Transmit
Interval
40ms
Inform Delay
5s
Inform Failure
Retry
UTC
UTF-8
Record Log
No
10000
MIB Frame
U2000 MIB
Issue 05 (2013-05-17)
27
Prerequisites
l
Context
NOTE
Procedure
Step 1 Log in U2000 server.
l
On the Windows OS, log in the U2000 server as the Administrator user.
On the Solaris or Linux OS, log in U2000 server as the nmsuser user.
Step 2 Open the directory that contain License. Use the text viewer to view the contents of the License
file. For the relations between the control items in the U2000 license file and the SNMP NBI
functional items, see Table 4-3.
NOTE
Issue 05 (2013-05-17)
Abbreviation
Value
LNSDPENES01
0-100000
LNSDPENES02
0-100000
LNSDPENEC21
0~8000000
LNSDPENEC25
0~8000000
LNSDNELCR84
0~8000000
LNSDNELCR75
0~8000000
28
Step 3 If the license does not support the function needed, contact Huawei engineers to apply for the
license. For the license introduction and information on how to apply for a license, see section
Applying for and Updating the License in the iManager U2000 Administrator Guide.
----End
Context
Generally, the process of the MSuite server server is started with the OS startup. If the process
is not started, perform the following operations to start it.
NOTE
If the server is a Netra 240, V240, or V440 workstation, the process of the MSuite server is not started with
the OS startup.
Procedure
l
In Windows OS, check whether the msdaemon.exe and msserver.exe processes are started
in the Task Manager window. If you can find the two processes in the process list, the
MSuite server is running. If the two processes do not exist in the process list, the MSuite
server is not running. In this case, perform the following operations to start the MSuite
server:
Go to the C:\HWENGR\engineering path, and double-click the startserver.bat file.
In Solaris or SUSE Linux OS, run the following command as user root to verify that the
MSuite server is running:
# ps -ef | grep java
----End
Prerequisites
The MSuite server must be started.
Issue 05 (2013-05-17)
29
Context
If you consecutively enters incorrect passwords three times, the IP address of the PC on which
the MSuite client is installed will be locked by the U2000. The U2000 will unlock this IP address
5 minutes later.
Procedure
Step 1 On a computer where the MSuite client is installed, double-click the U2000 NMS Maintenance
Suite shortcut icon on the desktop and then wait about one minute. The Login dialog box is
displayed.
NOTE
l In Solaris/SUSE Linux OS, log in to the Java desktop system as user nmsuser. Otherwise, the U2000
NMS Maintenance Suite shortcut icon is not displayed on the desktop. To start the MSuite client by
running commands, run the following commands as user nmsuser. If you have logged in as the root
user, you cannot run the su - nmsuser command to switch to the nmsuser user to run the following
command:
$ cd /opt/U2000/engineering
$ ./startclient.sh
l If a dialog box showing The client and server versions are different. Upgrade the client using the
CAU. is displayed, the method of upgrading the U2000 client by using the CAU is as follow:
1. Install the U2000 client software in network mode: Enter https://server_IP_address:10443/cau
(more secure) or http://server_IP_address:8080/cau in the address box of the Internet Explorer,
and press Enter to access the Web installation page. For details, see Installing the U2000 Client
in Network Mode in the U2000 Client Software Installation Guide.
2. If you upgrade the U2000 client software using the CAU, the MSuite client is also upgraded. For
details, see Upgrading a Standalone U2000 Client in In-Service CAU Mode in the U2000 Client
Upgrade Guide.
The Login dialog box of the MSuite client has the function to keep the login list. Selecting an IP address
from the IP Address drop-down list is recommended. If the desired IP address is not displayed in the
drop-down list, enter an IP address.
l Port No.: The default port ID is 12212. There is no need to change the default value during
login but ensure that the port is not occupied.
l User Name: The default user name is admin.
l Password: The default password is Changeme_123. If the password has been changed, enter
the new password.
Step 3 Click Login.
Issue 05 (2013-05-17)
30
NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of querying
components and instances. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the MSuite at one
time.
l Change the initial password upon your first login to ensure U2000 system security and remember the new
password. For details, see 4.6.3 Changing the Password of the MSuite.
----End
Exception Handling
If a dialog box is displayed during the login, indicating that network configuration information
is inconsistent and re-synchronization is required after login, read through the message to learn
the server that needs to be synchronized. Then, update the network configuration, for details,
see iManager U2000 Administrator Guide.
Context
In the high availability system, you only need to log in to the MSuite server on the primary site
and change the password of the MSuite. The password of the MSuite on the secondary site is
then automatically changed.
Procedure
Step 1 Log in to the MSuite client. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the MSuite client, choose System > Change Password from the main menu. The Change
Password dialog box is displayed.
Step 3 Click OK. The Change Password dialog box is displayed.
Step 4 Enter the old password and new password.
NOTE
Issue 05 (2013-05-17)
31
Prerequisites
l
The Msuite client communicates with the Msuite server in the normal state.
Deploy Environment
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Context
The SNMP NBI is one of the components of U2000. The installation of the SNMP NBI is
integrated in the process of installing the U2000 server. There are two cases of the installation.
l
If the SNMP NBI is not installed during the installation of the U2000 server, to enable the
interface, you need to add the component first and then add the instance. For details, see
4.8 Adding SNMP NBI Component.
If the SNMP NBI is installed during the installation of the U2000 server, to enable the
interface, you need to configure the instance. For details, see 4.9 Configuring the SNMP
NBI.
The details for how to install the U2000 Server, refer to iManager U2000 Software Installation
Guide. If you want to install SNMP NBI, ensure you have select Northbound SNMP Interface
component during the installation of the U2000 server.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 Click Instance tab, check whether the AgentSNMP exist in the instance list.
l
If the AgentSNMP instance exist, refer the steps in 4.9 Configuring the SNMP NBI to
enable the SNMP NBI.
If the AgentSNMP instance not exist, you need to check whether the SNMP NBI
deployment package exist according to the Step 3.
Step 3 Click Deployment Package tabs, check whether the SNMP NBI exist in the deployment
package list.
Issue 05 (2013-05-17)
32
If the SNMP NBI deployment package exist, refer the steps in 4.9 Configuring the SNMP
NBI to enable the SNMP NBI.
If the SNMP NBI deployment package not exist, refer the steps in 4.8 Adding SNMP NBI
Component to enable the SNMP NBI.
----End
Prerequisites
l
The Msuite client communicates with the Msuite server in the normal state.
Ensure the installation directory has enough available space. In the Solaris or Linux OS,
you can run the df -hk /opt command to view the remaining space of the /opt directory.
Deploy Environment
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the Msuite client, choose Deploy > Add Component. The Add Component dialog box is
displayed.
CAUTION
l In the distributed system, the SNMP NBI could be deployed in master server only.
l You can add one SNMP NBI component only.
Step 3 Choose the North-Bound SNMP Interface component and click OK, the progress bar is
displayed.
Step 4 Wait until the message the component is successfully added is displayed. Click OK, completed
the operation
Issue 05 (2013-05-17)
33
Step 5 View the deployment package list in the Deployment Package tab, the North-Bound SNMP
Interface deployment package exist indicate that the operation is successful.
----End
Follow-up Procedure
After the component is added, you need to configure the SNMP NBI instance, then you can
enable the SNMP interface.
Prerequisites
l
The Msuite client communicates with the Msuite server in the normal state.
Ensure the installation directory has enough available space. In the Solaris or Linux OS,
you can run the df -hk /opt command to view the remaining space of the /opt directory.
Ensure that the component for the instance to be added is installed. If the component is not
installed, install it first. For details, see adding SNMP NBI component.
CAUTION
l Set the MIB to U2000 MIB when loading the U2000 MIB.
l Set the MIB to U2000-T MIB when loading the U2000-T MIB.
When the U2000-T MIB is loaded, the following advanced parameters are not supported:
l Heartbeat Settings
l Alarm Field Settings
l Report Date Format Settings
Deploy Environment
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Issue 05 (2013-05-17)
34
Start
Whether
SNMPv3 is used?
Yes
Add NMS/OSS
No
Set v3 user name,
password for authentication
and encryption
Set read/write
community
Yes
Multiple NMS?
No
Set Advanced
parameters
End
Issue 05 (2013-05-17)
35
CAUTION
l After filter criteria for correlative alarms and engineering alarms are set, restart the U2000
for these settings to take effect.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Click SNMP Agent on the General tab.
Issue 05 (2013-05-17)
36
CAUTION
The trap-transmitting IP address and request-receiving IP address are both the U2000 server
IP address. Ensure that this IP address can be used for successful communication between
the U2000 and the OSS.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI. Before
configuring these ports, ensure that the specified ports are idle.
Do not use the default ports of the SNMP protocol (port 161 and port 162) to deploy the
SNMP NBI, because they are occupied by other processes.
2.
Select the SNMP version. You also need to set the security level, authentication protocol,
and data encryption protocol if the version is set to v3.
By default, the SNMP version is v1.
Step 4 Click Third-Party NMS and set parameters for the OSS.
Issue 05 (2013-05-17)
Set the trap receive IP address/port. The trap receive IP address is the IP address of the OSS
server. The port is 6666 by default.
37
NOTE
The Receive Trap Address is not the IP address of the U2000 server.
Currently a maximum of 10 third-party NMSs are supported.
The same SNMPv3 user configured for different third-party NMSs, for example, NMS 1 and NMS
2, must use the same authentication and encryption passwords
When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.
l If multiple OSSs use the same read or write community, only the first OSS gets the synchronized
results when any of the OSSs tries to synchronize data.
l It is recommended that each OSS uses a unique read or write community so that the OSS can get
correct synchronized results.
CAUTION
In a Linux-based HA system, if the floating IP address function is enabled during NMS
installation, set Send Trap address and Receive Request from NMS address to floating
IP addresses.
2.
Set SNMP security parameters. For security concern, input parameters are encrypted. For
example, to set Read Community, click
in the Set Password dialog box.
The following are the default security parameters. Modifying these parameters is
recommended for security concern.
l If the SNMP version is set to v1 or v2c, configure the read and write communities. By
default, the read community is Changeme_123 and the write community is
Changeme_123.
l If the SNMP version is set to v3, configure the V3 User Name, V3 Authentication
Password, and V3 Privacy Password for SNMPv3 users.
l By default, the user name is admin and the two passwords are blank.
Issue 05 (2013-05-17)
38
CAUTION
In the case of SNMPv3, the V3 User Name is required. If no user name is entered, the
SNMP service process cannot start after deployment.
To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly.
The password must meet the following requirements to safeguard your user account.
l Consists more than 8 characters.
l The password cannot be the user name or its reverse spelling.
l The password must consist of three of the following types of characters at least:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ?
and space
3.
Set the alarm filter criteria, including Alarm Level and Alarm Category.
NOTE
Alarms are reported to the OSS based on the defined alarm severity and category.
The OSS can change the filter criteria in real time. For details, see 6.1.2 Changing Filter Criteria.
Fault: Indicates that the SNMP NBI will report alarm generation and alarm clearance. That is, the second
and third places of the value of AlarmCategoryFilter in binary mode are set to 0 when the
thirdNMSFaultFilter subinterface is invoked.
Event alarm reporting is disabled by default and cannot be configured by using the Msuite. But you can
enable this function by following methods.
l You can enable event alarm function manually. For details, see 7.3.10 How to report the event
alarm.
l To configure event alarm reporting, you can invoke the thirdNMSFaultFilter subinterface and set
the first place of the value of AlarmCategoryFilter in binary mode to 0.
4.
Optional: Click New Tab Item. To add more third-party NMSs, repeat the preceding
substeps.
Click Heartbeat, specify whether to set the heartbeat, and set the heartbeat period.
NOTE
Parameters
Value
Description
Heartbeat Period
Default: 60s
3s~300s
Report Heartbeat
Info
Issue 05 (2013-05-17)
Default: Yes
Yes, No
39
2.
Click Alarm Field and set the alarm information to be reported. For details, see B.2.2
Alarm Field.
3.
Click notification and set the reporting mode and other relevant parameters.
Parameter
Description
Value
Reporting
Mode
Support X733
Alarm
Default: No
Yes, No
Trap Transmit
Interval
Default: 0
Inform Delay
Default: 5
0 ms-1000 ms
5 s - 120 s
Inform Failure
Retry
4.
Issue 05 (2013-05-17)
Default: 3
2 times-6 times
Click Time Format and set the date format for reported alarms.
40
Paramete
rs
Value
Description
Alarm
Time
Format
Default: UTC
Time
UTC Time,
Local Time
(without Time
Zone), Local
Time (with
Time Zone)
UTC Time
Example: 2009/12/23 - 11:30:30Z
Local Time (without Time Zone)
The format is as YYYY/MM/DD - hh:mm:ss.
Example: 2009/12/23 - 19:30:30
Local Time (with Time Zone)
The format is as YYYY/MM/DD hh:mm:ss,hh:mmTZ[DST], where TZ stands for
timezone information.
Example:
l 2009/12/23 - 19:30:30,+08:00[0] (if the date is not
in DST).
l 2009/12/23 - 19:30:30 +08:00[3600] (if the date is
in DST of 1 hr). The DST value is in seconds.
5.
6.
7.
8.
Issue 05 (2013-05-17)
Click Encoding Format and set the code format for traps.
Parameters
Value
Description
Alarm
Character
Default: UTF-8
UTF-8, GBK
Click Alarm Relativity Config and specify whether to report the correlative alarms.
Parameter
s
Value
Description
Alarm
Relativity
Config
Default: All
alarms
All alarms,
Root Alarm
Root Alarm: Queries and reports only the root alarm and
common alarms.
Click Engineering Alarm and specify whether to report the engineering alarms.
Parameters
Value
Description
Engineering
Alarm
Click Other Settings, specify whether to log alarms, and set the cache size for alarms.
41
Parameters
Value
Description
Record Log
Default: No
Yes, No
Real-time Alarm
Cache Size
Default:
10000
0-50000
9.
Click MIB Frame and set the MIB structure and resource information for alarms.
CAUTION
Select an appropriate MIB structure based on integration scenarios. For details, see B.2.9
MIB Frame.
Step 6 Click OK to complete the settings.
NOTE
In a Linux-based HA system, floating IP addresses can be used to deploy SNMP NBIs. Specifically, the
active and standby servers use the same floating IP address. In a non-Linux-based HA system, perform the
following operations to complete the configuration.
Step 7 Optional: For an HA system with multiple network interface cards (NICs), if you use the IP
address of the primary site to deploy the SNMP NBI and this IP address is not displayed in the
required drop-down list, the Address for Standby Server dialog box will be displayed.
1.
Issue 05 (2013-05-17)
Set the IP address of the secondary site for the SNMP NBI.
42
CAUTION
l The SNMP NBI can be deployed on the primary site only.
l You can set any of the IP addresses of the secondary site (except for 127.0.0.1). Ensure
that the secondary site can communicate with the OSS properly using this IP address.
l The SNMP NBI searches the IP configuration list (or host files) automatically and binds
the first IP address to the primary site. If necessary, manually bind an appropriate IP
address that can be used for communication.
l Receive Request from NMS address is mandatory, while Send Trap address is
optional. These two IP addresses can be different.
2.
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
WARNING
After the following operations, you must restart U2000.
l Deploy the SNMP NBI for the first time.
l Modify the Alarm Relativity Config or Engineering Alarm item.
Step 9 Optional: Click OK to close the dialog box.
Step 10 Optional: Log in to the System Monitor. Restart all processes of the U2000.
Step 11 Check the status of the SNMP Service process. If the process is running, the SNMP NBI has
been enabled successfully.
----End
Issue 05 (2013-05-17)
43
Prerequisites
l
Procedure
Step 1 On the System Monitor client, check the status of the SNMP service. If Status is Running, the
SNMP NBI is enabled.
l If no SNMP NBI process is found, see the 7.3.1 SNMP Service Process Is Not Displayed
for troubleshooting.
l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to
Be Started for troubleshooting.
Step 2 Check whether heartbeat messages are received on the related OSS port. If no heartbeat message
is received, see the 7.3.4 The OSS Cannot Receive Heartbeat Information for
troubleshooting.
----End
Prerequisites
The SNMP NBI is correctly deployed and configured.
Procedure
Step 1 On the System Monitor client, check the status of the SNMP service. If Status is Running, the
SNMP NBI is enabled.
l If no SNMP NBI process is found, see the 7.3.1 SNMP Service Process Is Not Displayed
for troubleshooting.
Issue 05 (2013-05-17)
44
l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to
Be Started for troubleshooting.
----End
Prerequisites
l
Network Planning
The MIB file HW-IMAPV1NORTHBOUND-TRAP-MIB.mib is loaded to the OSS, as shown
in Figure 4-3. The OSS manages and monitors alarms from Huawei network equipment using
the SNMPv1 NBI. Table 4-4 and Table 4-5 list detailed parameters.
You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.
Table 4-4 Server parameters for the SNMPv1 NBI
Server
Parameters
Value
Upper-layer
NMS
IP address
10.70.71.97
6666
MIB
HW-IMAPV1NORTHBOUNDTRAP-MIB.mib
IP address
10.71.226.158
6666
9812
U2000
Issue 05 (2013-05-17)
Parameters
Value
SNMP Version
SNMPv1
Read Community
Changeme_123
45
Parameters
Value
Write Community
Changeme_123
OSS
set/get
U2000
Device Network
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for
the SNMP agent.
SNMP agent parameters are U2000 server parameters.
l Send Trap address: 10.71.226.158 Port: 6666
l Receive Request from NMS address: 10.71.226.158 Port: 9812
Issue 05 (2013-05-17)
46
Step 4 In the right pane, set the SNMP version (in this example, v1 is selected).
NOTE
Step 5 Choose Third-Party NMS from the navigation tree to set parameters for third-party NMSs in
the right pane.
Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.
l NMS Receive Trap Address: 10.70.70.97
l Port: 6666
l Read Community: Changeme_123
l Write Community: Changeme_123
NOTE
Parameter for SNMPv3 (such as user name/password, authentication password, and encryption password)
are invalid if v3 is not selected.
Issue 05 (2013-05-17)
47
Step 6 Click the Advanced tab and choose MIB Frame from the navigation tree. In the right pane,
select U2000 MIB from the MIB drop-down list.
Step 7 Click OK. The U2000 starts to redeploy the SNMP NBI.
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
Issue 05 (2013-05-17)
48
WARNING
After the following operations, you must restart U2000.
l Deploy the SNMP NBI for the first time.
l Modify the Alarm Relativity Config or Engineering Alarm item.
Step 9 Optional: Click OK to close the dialog box.
----End
Prerequisites
l
Network Planning
The MIB file T2000-NETMANAGEMENT-MIB.mib is loaded to the OSS, as shown in
Figure 4-4. The OSS manages and monitors alarms from Huawei network equipment using the
SNMPv1 NBI. Table 4-6 and Table 4-7 list detailed parameters.
You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.
Table 4-6 Server parameters for the SNMPv3 NBI
Server
Parameters
Value
Upper-layer
NMS
IP address
10.70.71.97
9833
MIB
T2000-NETMANAGEMENTMIB.mib
IP address
10.71.226.158
9831
9832
U2000
Issue 05 (2013-05-17)
Parameters
Value
SNMP Version
SNMPv3
49
Parameters
Value
Security Level
V3 User Name
admin
V3 Password Authentication
U2ksnmp_v3
u2000_SNMP
OSS
set/get
SNMPv3
User: admin
Inform Authentication password: U2ksnmp_v3
Encryption password: u2000_SNMP
IP: 10.71.226.158
Received Port: 9832
Send Port: 9831
U2000
Device Network
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for
the SNMP agent.
SNMP agent parameters are U2000 server parameters.
l Send Trap address: 10.71.226.158 Port: 9831
l Receive Request from NMS address: 10.71.226.158 Port: 9832
Issue 05 (2013-05-17)
50
Step 4 In the right pane, set the SNMP version (in this example, v3 is selected).
l Security Model: USM
l Security Level: With authentication and encryption
l Authentication: HMACMD5
l Data Encryption: DES
Step 5 Click the General tab and choose Third-Party NMS from the navigation tree to set parameters
for third-party NMSs.
Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.
l NMS Receive Trap Address: 10.70.71.97
l Port: 9833
l V3 User Name: admin
l V3 Password Authentication: U2ksnmp_v3
l V3 Password for Privacy: u2000_SNMP
Issue 05 (2013-05-17)
51
Step 6 Click the Advanced tab and choose MIB Frame Setting from the navigation tree. In the right
pane, select T2000-MIB from the MIB drop-down list.
Step 7 Click OK. The U2000 starts to redeploy the SNMP NBI.
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
Issue 05 (2013-05-17)
52
WARNING
After the following operations, you must restart U2000.
l Deploy the SNMP NBI for the first time.
l Modify the Alarm Relativity Config or Engineering Alarm item.
Step 9 Optional: Click OK to close the dialog box.
----End
Issue 05 (2013-05-17)
53
Issue 05 (2013-05-17)
54
Prerequisites
l
For SNMP NBI deployment, the SNMP version has been set to SNMPv1 or SNMPv2c,
and write and read communities have been configured.
For SNMP NBI deployment, third-party NMS parameters have been set properly and the
OSS can receive real-time alarms or heartbeat from the U2000.
Procedure
Step 1 Confirm SNMP NBI parameters with the U2000 administrator.
1.
2.
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the
main menu. View parameters as follows.
Para
meter
s
Description
Default Value
Navigation Path
IP
addres
s and
port of
U2000
Indicates the
request receive IP
address/port on the
U2000.
9812
SNMP
Versio
n
v1
Read/
Write
Comm
unity
Read
Community:
Changeme_123
Write
Community:
Changeme_123
Step 2 Configure the OSS based on the previous parameters set on the U2000.
Issue 05 (2013-05-17)
55
CAUTION
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
connection may fail.
----End
Prerequisites
l
For SNMP NBI deployment, the SNMP version has been set to SNMPv3, and related
security parameters have been set.
For SNMP NBI deployment, third-party NMS parameters have been set properly and the
OSS can receive real-time alarms or heartbeat from the U2000.
Procedure
Step 1 Confirm SNMP NBI parameters with the U2000 administrator.
1.
2.
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the
main menu. View parameters as follows.
Parameters
Description
Default
Value
Navigation Path
IP address
and port of
U2000
Indicates the
request receive IP
address/port on
the U2000.
9812
SNMP
Version
Indicates the
SNMP version for
the SNMP NBI.
v1
Security
Model
USM model
USM model
Change the
value to v3 if
SNMPv3 is
used.
Issue 05 (2013-05-17)
56
Parameters
Description
Default
Value
Navigation Path
Security
Level
Indicates the
security level,
including without
authentication
and encryption,
with
authentication
and without
encryption, and
with
authentication
and encryption.
Without
authentication
and encryption
Authenticati
on Protocol
Indicates the
authentication
algorithm,
including NONE,
HMACMD5, and
HMACSHA.
NONE
Data
Encryption
Protocol
Including the
encryption
algorithm,
including NONE,
DES, and AES.
NONE
User Name
admin
Authenticati
on Password
Indicates the
authentication
password.
The default
value is left
blank.
Data
Encryption
Password
The default
value is left
blank.
Step 2 Configure the OSS based on the previous parameters set on the U2000.
Issue 05 (2013-05-17)
57
CAUTION
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
connection may fail.
----End
Issue 05 (2013-05-17)
58
Ensure that the OSS has connected to the U2000 through the SNMP NBI and the desired operations have
been licensed for use.
Issue 05 (2013-05-17)
59
CAUTION
Ensure that the U2000 MIB has been loaded to the OSS. To load the U2000 MIB, set the MIB
type to U2000 MIB when deploying the SNMP NBI.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured
on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the
U2000, the OSS can receive real-time alarms.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected
to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring
SNMP.
Function
The OSS can call the alarm filter interface to change alarm filter criteria dynamically when the
SNMP NBI is working.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.5.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).thirdNMSFaultFilter(5)
Issue 05 (2013-05-17)
60
Object
Type
Max Access
Description
thirdNMSFaultFilter
Octet string
read-write
Setting Method
The OSS can set the value of the MIB node to change the alarm filter criteria. The format is as
follows:
IPAddress:Port:AlarmFilterLevel:AlarmCategoryFilter
Table 6-1 Format description - changing filter criteria
Field
Description
IPAddress
Indicates the IP address used by the OSS. This IP address is the trapreceiving IP address preset for third-party NMSs when the SNMP NBI is
deployed.
Port
Indicates the port used by the OSS. This port is the trap-receiving port preset
for third-party NMSs when the SNMP NBI is deployed.
AlarmFilterLe
vel
AlarmCategor
yFilter
Sample
Prerequisite
l
The IP address of the OSS is set to 10.70.73.97 and the port for receiving alarms 6666.
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
Issue 05 (2013-05-17)
61
To change the filter criteria as follows: alarm severity (critical or major) and alarm category
(fault or clear).
Table 6-2 shows the parameters of this sample.
Table 6-2 Sample parameters - changing filter criteria
Parameter
Value
MIB Object
10.70.73.97
10.70.73.97
6666
6666
Alarm Severity to be
Reported
Critical, Major
0011
Alarm Category to be
Reported
100111
Procedure
The OSS sets thirdNMSFaultFilter to 10.70.73.97:6666:0011:100111.
The OSS receives responses from the U2000, indicating that the filter criteria are changed
successfully. The OSS will then receive the required alarms only.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and
some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data
consistency and can also stop synchronization.
After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform the
OSS that the alarm synchronization is started.
When the synchronization is complete or stopped, the U2000 will send traps through the SNMP
NBI to inform the OSS that the alarm synchronization is ended.
Figure 6-1 shows the alarm synchronization process.
Issue 05 (2013-05-17)
62
.
.
.
.
SNMP NBI
Set alarm
synchronization start node
Report alarm
synchronization start trap
Report alarm
.
All
synchronization result trap
. Alarms
. are
. reported
Report the alarm
synchronization stop trap
Set alarm
synchronization start node
Report alarm
synchronization stop trap
Operation
Description
Synchronize alarms
NOTE
For details of the alarm synchronization start trap, see C.3.2 Active Alarm Synchronization Start
Trap.
For details of the alarm synchronization result trap, see C.3.3 Active Alarm Report Trap.
For details of the alarm synchronization stop trap, see C.3.4 Active Alarm Synchronization End Trap.
MIB Definition
There are two MIB nodes for alarm synchronization:
hwNmNorthboundEventSynchronizationCommandStart and
hwNmNorthboundEventSynchronizationCommandStop. The former indicates start alarm
synchronization, while the latter indicates stop alarm synchronization.
The OIDs are 1.3.6.1.4.1.2011.2.15.1.7.7.4 and
1.3.6.1.4.1.2011.2.15.1.7.7.5.
The full paths are
Issue 05 (2013-05-17)
63
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization
(7).hwNmNorthboundEventSynchronizationCommandStart(4)
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization
(7).hwNmNorthboundEventSynchronizationCommandStop(5)
Object
Syntax
Max Access
Description
hwNmNorthboundE
ventSynchronizationCommandStart
Octet string
read-write
hwNmNorthboundE
ventSynchronizationCommandStop
Octet string
read-write
Setting Method
Start alarm synchronization.
The OSS can set the value of the MIB node to start alarm synchronization within a specified
time. The format is as follows:
IP:port:start time:end time
Stop alarm synchronization.
The OSS can set the value of the MIB node to stop alarm synchronization. The format is as
follows:
IP:port
NOTE
You do not need to set the start and end time to stop the alarm synchronization.
Issue 05 (2013-05-17)
Parameter
Description
IP
Indicates the IP address used by the OSS. This IP address is the trapreceiving IP address set for third-party NMSs when the SNMP NBI is
deployed.
port
Indicates the port used by the OSS. This port is the trap-receiving port set
for third-party NMSs when the SNMP NBI is deployed.
64
Parameter
Description
start
time:endtime
Sample
Prerequisite
l
The IP address of the upper-layer OSS is set to 10.70.73.97 and the port for receiving alarms
is set to 6666.
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To synchronize alarms that are generated between 2011-03-01 00:00:00 and 2011-03-15
00:00:00.
Table 6-4 shows the parameters of this sample.
Table 6-4 Sample parameters - synchronizing alarms
Issue 05 (2013-05-17)
Parameter
Value
MIB Object
10.70.73.97
10.70.73.97
6666
6666
Start time
2011-03-01 00:00:00
20110301000000
End Time
2011-03-15 00:00:00
20110315000000
65
Procedure
1.
2.
Optional:
To stop the synchronization, the OSS sets
hwNmNorthboundEventSynchronizationCommandStop to 10.70.73.97:6666.
3.
After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.
Function
The OSS can acknowledge U2000 alarms based on the alarm serial numbers.
The alarm status will change after the alarm is acknowledged. If acknowledged alarms are
specified as the filter criteria, the OSS will receive the information about state changes along
with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an
alarm is acknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be acknowledged
and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.7.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).hwNmAcknowledgeAlarms(7)
Issue 05 (2013-05-17)
Object
Type
Max Access
Description
hwNmAcknowledgeAlarms
Octet string
read-write
66
NOTE
Setting Method
The OSS can set the value of the MIB node to acknowledge the active alarm on U2000. The
format is as follows:
Serial Number,Serial Number,...
Table 6-5 Format description - acknowledging alarms
Parameter
Description
Serial
Number,Se
rial
Number,..
.
Table 6-6 shows the status changes when alarms are acknowledged.
Table 6-6 Alarm states - acknowledging alarms
Sl.No
Alarm Status
Status Change
SET Response
Failed List
Unacknowledge
and Unclear
Acknowledge
and Unclear
Success
Empty
Unacknowledge
and Clear
Acknowledge
and Clear
Success
Empty
Acknowledge
and Unclear
Acknowledge
and Unclear
Success
Empty
Acknowledge
and Clear
NA
Success
serial number
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you acknowledge these alarms. The life cycle specifies the period in
which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To acknowledge the alarm with the serial number 20,30,10005,18000.
Issue 05 (2013-05-17)
67
Value
MIB Object
20,30,10005,18000
20,30,10005,18000
Procedure
The OSS sets hwNmAcknowledgeAlarms to 20,30,10005,18000.
Query the alarm status on the OSS or U2000. The state for the alarm
20,30,10005,18000 is Acknowledge, indicating the alarm is acknowledged successfully.
The Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If acknowledged alarms are specified as the filter criteria, the OSS will receive the information about state
changes along with the alarms. The alarm time is when the alarm is acknowledged.
Function
The OSS can unacknowledge alarms based on alarm serial numbers.
The alarm status will change after the alarm is unacknowledged. If unacknowledged alarms are
specified as the filter criteria, the OSS will receive the information about state changes along
with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an
alarm is unacknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be
unacknowledged and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.8.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).hwNmUnAcknowledgeAlarms(8)
Issue 05 (2013-05-17)
68
Object
Type
Max Access
Description
hwNmUnAcknowledgeAlarms
Octet string
read-write
NOTE
Setting Method
The OSS can set the value of the MIB node to unacknowledge the active alarm on U2000. The
format is as follows:
Serial Number,Serial Number,...
Table 6-8 Format description - unacknowledging alarms
Parameter
Description
Serial
Number,Se
rial
Number,..
.
Table 6-9 shows the state change when alarms are unacknowledged.
Table 6-9 Alarm states - unacknowledging alarms
Issue 05 (2013-05-17)
Sl.No
Alarm Status
Status Change
SET Response
Failed List
Unacknowledge
and Unclear
Unacknowledge
and Unclear
Success
Empty
Unacknowledge
and Clear
Unacknowledge
and Clear
Success
Empty
Acknowledge
and Unclear
Unacknowledge
and Unclear
Success
Empty
Acknowledge
and Clear
NA
Success
serial number
69
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you unacknowledge these alarms. The life cycle specifies the period
in which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To unacknowledge the alarm with the serial number 20,30,10005,18000.
Table 6-10 shows the parameters of this sample.
Table 6-10 Sample parameters - unacknowledging alarms
Parameter
Value
MIB Object
20,30,10005,18000
20,30,10005,18000
Step
The OSS sets hwNmUnAcknowledgeAlarms to 20,30,10005,18000.
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000
is Unacknowledge, indicating the alarm is unacknowledged successfully. The
Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If unacknowledged alarms are specified as the filter criteria, the OSS will receive the information about
status changes along with the alarms. The alarm time is when the alarm is generated.
Function
The OSS can clear alarms based on the alarm serial numbers.
The alarm status will change after the alarm is cleared. If cleared alarms are specified as the
filter criteria, the OSS will receive the information about status changes along with the alarms.
Issue 05 (2013-05-17)
70
CAUTION
The Clearance User parameter is SNMP Agent User on the U2000 client after an alarm is
cleared by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be cleared and
the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.6.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).hwNmClearAlarms(6)
Object
Type
Max Access
Description
hwNmClearAlarms
Octet string
read-write
NOTE
Setting Method
The OSS can set the value of the MIB node to clear the active alarm on U2000. The format is
as follows:
Serial Number,Serial Number,...
Table 6-11 Format description - clearing alarms
Parameter
Description
Serial
Number,Se
rial
Number,..
.
Table 6-12 shows the change in state when alarms are cleared.
Issue 05 (2013-05-17)
71
Alarm Status
Status Change
SET Response
Failed List
Unacknowledge
and Unclear
Unacknowledge
and Clear
Success
Empty
Unacknowledge
and Clear
Unacknowledge
and Clear
Success
Empty
Acknowledge
and Unclear
Acknowledge
and Clear
Success
Empty
Acknowledge
and Clear
NA
Success
serial number
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you clear these alarms. The life cycle specifies the period in which
these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To clear the alarm with the serial number 20,30,10005,18000.
Table 6-13 shows the parameters of this sample.
Table 6-13 Sample parameters - clearing alarms
Parameter
Value
MIB Object
20,30,10005,18000
20,30,10005,18000
Procedure
The OSS sets hwNmClearAlarms to:
20,30,10005,18000
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000
is Clear, indicating the alarm is cleared successfully. The Clearance User parameter is SNMP
Agent User on the U2000 client.
NOTE
Issue 05 (2013-05-17)
72
CAUTION
Ensure that the U2000-T MIB has been loaded to the OSS. To load the U2000-T MIB, set the
MIB type to U2000-T MIB when deploying the SNMP NBI.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured
on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the
U2000, the OSS can receive alarms in real time.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected
to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring
SNMP.
CAUTION
The reported alarm field for the U2000-T MIB consists of 36 bound variables (VBs). For details,
see D.2 Reported Alarm Field by U2000-T MIB.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and
some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data
consistency and can also stop the synchronization.
After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform the
OSS that the alarm synchronization is started.
Issue 05 (2013-05-17)
73
When the synchronization is complete or stopped, the U2000 will send traps through the SNMP
NBI to inform the OSS that the alarm synchronization is ended.
Figure 6-2 shows the alarm synchronization process.
Figure 6-2 Alarm synchronization process
NMS/OSS
.
.
.
.
SNMP NBI
Set alarm
synchronization start node
Report alarm
synchronization start trap
Report alarm
.
All
synchronization result trap
. Alarms
. are
. reported
Report the alarm
synchronization stop trap
Set alarm
synchronization start node
Report alarm
synchronization stop trap
Operation
Description
Synchronize alarms
Stop alarm
synchronization
NOTE
For details of the alarm synchronization start trap, see D.3.2 Active Alarm Synchronization Start
Trap.
For details of the alarm synchronization result trap, see D.3.3 Active Alarm Report Trap.
For details of the alarm synchronization stop trap, see D.3.4 Active Alarm Synchronization End Trap.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.7.4.1.
The full path is
Issue 05 (2013-05-17)
74
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).netManagement(15).nmAgent
(1).nmNorthboundEvent(7).northboundSynchAlarm
(4).northBoundSynchAlarmCommand(1)
Object
Type
Max Access
Description
northBoundSynchAlarmCommand
Integer
read-write
Setting Method
The OSS can set the value of the MIB node to start or stop the synchronization. The format is
as follows:
number
Table 6-14 Format description - synchronizing alarms
Parameter
Description
number
0, 1
l 0: indicates the stop of alarm synchronization.
l 1: indicates the start of alarm synchronization.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To start or end the alarm synchronization.
Step
1.
2.
Optional:
To stop the synchronization, set the northBoundSynchAlarmCommand node to 0.
3.
Issue 05 (2013-05-17)
After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.
75
Issue 05 (2013-05-17)
76
2.
3.
4.
The parameter is correct when you deploy the SNMP NBI by Msuite.
Prerequisites
Before login, ensure that the U2000 client and server are connected properly and that the server
works correctly.
Context
l
The default port number of the server is 31030. Do not change it in normal conditions.
Otherwise, you cannot log in to the U2000 server.
The login modes include the SSL mode and common mode. In SSL mode, the data is
encrypted when being transmitted between the client and the server. In common mode, the
data is not encrypted during transmission. To ensure the security of data transmission, you
are recommended to use the Security (SSL) mode.
The port used for login in common mode is different from that in SSL mode. The port
number is 31030 in common mode, and 31080 in security (SSL) mode.
After last login, if you do not log in again during the preset period, your account hibernates
or the U2000 deletes the account.
If you never use a new user account for login, the U2000 does not invalidate or delete the
account.
Procedure
Step 1 Double-click the shortcut icon on the desktop to start the system monitor client.
Issue 05 (2013-05-17)
77
NOTE
In the Solaris and Linux OS , login to the OS of the server as the nmsuser user. Run the following command
to start the system monitor client.
$ cd /opt/U2000/client
$ ./startup_sysmonitor_global.sh
/opt/U2000 is the default installation path for the U2000. You can change it as required.
Step 2 In the Login dialog box, select a server by selecting an IP address or host name from the
Server drop-down list.
NOTE
Step 3 In the Login dialog box, enter the user name and password.
The user name and password are the same as those used on the U2000 client.
Step 4 Click Login.
NOTE
l If the user name and the password are correct, the Loading dialog box is displayed, showing the loading
progress.
l If the user name or password is incorrect, the Information dialog box is displayed, prompting that you
cannot log in.
l If the password will expire in the specified days, a dialog box is displayed, prompting you to change
the password before the expiration date.
----End
Prerequisites
l
Context
NOTE
After the SNMP interface instance is added through the Msuite, the default start mode is Automatic. The
SNMP interface process is started with the U2000.
Issue 05 (2013-05-17)
78
Procedure
Step 1 Log in to the System Monitor.
Step 2 On the System Monitor, enter the Process Monitor tab.
Step 3 Select SNMP Service process, right-click and choose Stop the Process.
Step 4 The prompt dialog box displayed, click Yes.
Step 5 On the System Monitor client, if Status of the related processes of the SNMP NBI is
Stopped, it indicates that the operation is successful.
----End
Issue 05 (2013-05-17)
79
Prerequisites
l
Procedure
Step 1 Log in to the System Monitor.
Step 2 On the System Monitor, enter the Process Monitor tab.
Step 3 Select the SNMP Service process, right-click, and choose Startup Mode > Disable to disable
the process.
Step 4 On the System Monitor client, if Startup Mode of the related processes of the SNMP NBI is
Disabled, it indicates that the operation is successful.
Issue 05 (2013-05-17)
80
----End
Prerequisites
l
Procedure
Step 1 Log in to the System Monitor.
Step 2 On the System Monitor, enter the Process Monitor tab.
Issue 05 (2013-05-17)
81
Step 3 Select the SNMP Service process, right-click, and then choose Start the Process from the
shortcut menu.
Step 4 In the System Monitor client, when Status of the relevant SNMP processes, namely SNMP
Service are Running, the operation is successful.
----End
Issue 05 (2013-05-17)
82
Prerequisites
l
The Msuite client communicates with the Msuite server in the normal state.
It is recommended that you stop the SNMP NBI before delete the instance.
Deploy Environment
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 Click the Instance tab. Select the AgentSNMP instance from the instance list, right-click, and
choose Delete Instance
Step 3 Click OK. After the confirmation, the Msuite begins deleting the AgentSNMP instance.
Step 4 Click the Deployment Package tab, if the Instance Count of the SNMP NBI deployment
package is zero, that means the deletion success.
Step 5 Required: Log in to the System Monitor. Restart all processes of the U2000.
----End
Result
NOTE
After the AgentSNMP instance is deleted, the Sysmonitor does not display the information about the
AgentSNMP process. If you need to re-enable the SNMP interface, refer to 4.9 Configuring the SNMP
NBI.
83
Prerequisites
l
The Msuite client communicates with the Msuite server in the normal state.
Deploy Environment
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the Msuite client, click Deployment Package tab, check whether the instance count of SNMP
NBI deployment package is zero.
l
If Instance Count is not zero, you need to deleted the SNMP NBI instance first.
If Instance Count is zero, choose Deploy > Remove Component from the Main Menu.
The dialog box is displayed.
You cannot delete the components which are basic or have not installed. You cannot select them in the left
window.
Step 4 Click OK in the displayed dialog. The deleting of the component is started.
Step 5 Wait until the message the component is successfully removed is displayed. Click OK.
Step 6 View the deployment package list in the Deployment Package tab, the North-Bound SNMP
Interface deployment package not exist indicate that the operation is successful.
----End
84
Possible Causes
The SNMP NBI is not licensed.
Procedure
Step 1 Check whether the license for the SNMP NBI has been obtained. If not, the SNMP service
process is not displayed on the System Monitor client. For details, see 4.5 Checking the
License.
Step 2 If there is a license for the SNMP NBI, redeploy the NBI or restart the U2000. Then check for
the SNMP Service process.
Step 3 If the SNMP Service process is not running, contact your Huawei engineers.
----End
Possible Causes
Port 9812 for configuring the SNMP NBI is occupied by other processes.
The V3 User is blank when use the SNMP v3.
CAUTION
Do not use the default ports of the SNMP protocol (port 161 and port 162) to configure the
SNMP NBI, because these they are occupied by other processes.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI.
Procedure
Step 1 Check whether other processes are using the port of the SNMP service.
Run the netstat -an command to view the service ports opened by the system.
l On the Solaris or Linux OS, run the netstat -an | grep port_number command to view the
status of a specified port.
For example, run the netstat -an | grep 6666 command to view the status of port 6666.
l In the Windows OS, run the netstat -an | find "port_number" command to view the status
of a specified port.
For example, run the netstat -an | find "6666" command to view the status of port 6666.
NOTE
If any router or firewall is located on the network between the U2000 and the OSS, you must check the
ports used by the U2000 and the OSS and ensure that these ports can be opened for normal communication.
Issue 05 (2013-05-17)
85
Serving Port/
Protocol Type
Direction (with
the Server as the
Reference Object)
Description
SnmpAgent
6666/UDP
OUT
SnmpAgent
9812/UDP
IN
Step 2 If the port is occupied by other processes, negotiate with OSS engineers to modify the port for
the SNMP NBI, or end the processes if they are not needed.
Step 3 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 4 Select Third-party NMS in the General tab. Check whether the V3 user is blank. If it is blank,
input the correct value, then deploy the SNMP NBI.
----End
Possible Causes
l
As the following tables shows, the communication parameters of the OSS do not match
with those of the U2000.
Version
Communication Parameters
SNMPv1 and
SNMPv2
SNMPv3
Issue 05 (2013-05-17)
The firewall blocks the communication between the request transmit port on the OSS and
the request receive port on the U2000.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
86
Procedure
Step 1 Log in the client of U2000 System Monitor and check whether the SNMP Service process is
started.
l
If the SNMP Service process cannot be started, see 7.3.2 SNMP Service Process Fails to
Be Started.
Step 2 If the SNMP Service process has been started, determine the communication parameters with
OSS engineers and redeploy the SNMP NBI.
Step 3 Ensure the communication between the request transmit port on the OSS and the request receive
port on the U2000 is not blocked by the firewall; otherwise they cannot communicate with each
other.
----End
Possible Causes
l
The OSS is loaded with the U2000-T MIB that does not support heartbeat transmission.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Check whether the loaded MIB meets the requirements:
Click the Advanced tab and choose MIB Frame from the navigation tree. In the right pane,
check whether MIB is set to U2000 MIB. If no, change it to U2000 MIB and then reconfigure
the SNMP NBI.
Step 4 Check whether the heartbeat function is disabled:
Click the Advanced tab and choose Heartbeat from the navigation tree. In the right pane, check
whether Report Heartbeat Info is set to Yes. If no, change it to Yes and then reconfigure the
SNMP NBI.
----End
87
Possible Causes
l
The following parameters are incorrect when the SNMP NBI is deployed.
Send Trap address/port in SNMP Agent
NMS receive Trap address/port in Third-part NMS
The request transmit port on the OSS and the request receive port on the U2000 are disabled
on the firewall, so they cannot communicate with other.
The request transmit port on the OSS is 6666 by default.
The request receive port on the U2000 is 6666 by default.
Procedure
Step 1 After confirming the previous parameters with OSS engineers, log in to the Msuite MSuite client
and reconfigure the SNMP NBI based on the confirmation.
Step 2 Check whether the request transmit port on the OSS and the request receive port on the
U2000 are enabled on the firewall; otherwise they cannot communicate with each other.
----End
Possible Causes
l
The dependent services are down, such as log service and fault service.
Procedure
Step 1 Log in the client of U2000, browse the history alarms. View the serial number is exist. If the
serial number is exist, the alarm is converted to history alarm, then you cannot acknowledge,
unacknowledge and clear history alarms.
Step 2 Log in the client of U2000 System Monitor, view whether the log service and fault service are
running normally. If not started, please restart the processes.
Step 3 View whether the MIB file the U2000 loaded is correct.
1.
2.
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the
main menu.
Issue 05 (2013-05-17)
88
3.
Click Advanced, select MIB Frame. View whether the MIB is set to U2000 MIB. If the
MIB is set to U2000-T MIB, please modify to U2000 MIB. Then deploy the SNMP NBI
again.
Step 4 View whether the MIB file the NMS/OSS loaded is correct.
l
If the MIB file is HW-IMAPV1NORTHBOUND-TRAP-MIB.mib or HWIMAPV2NORTHBOUND-TRAP-MIB.mib, please get the U2000 version
documentation iManager U2000 Northbound SNMP Interface MIB file from Huawei
technology engineer. This documentation is published in Huawei support website.
----End
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
l U2000 is running normally.
l The environment variables are correct. For details, refer to iManager U2000 Software
Installation Guide.
l The SNMP NBI instance is deployed and configured.
l In a high availability system, you only need to log in to the primary site to perform this
operation. But you need to modify the configuration files in primary site and secondary site.
Step 1 Log in to the OS of the U2000 server.
l
For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.
For windows, log in to the OS of the U2000 server as the Administrator user.
Issue 05 (2013-05-17)
89
NOTE
Step 7 Optional: Perform the following operations for the heartbeat notification trap to report
hwNmAgent instead of hwNmNorthboundKeepAlive:
1.
2.
3.
----End
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
l U2000 is running normally.
l The environment variables are correct. For details, refer to iManager U2000 Software
Installation Guide.
l The SNMP NBI instance is deployed and configured.
l In a high availability system, you only need to log in to the primary site to perform this
operation. But you need to modify the configuration files in primary site and secondary site.
Step 1 Log in to the OS of the U2000 server.
Issue 05 (2013-05-17)
90
For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.
For windows, log in to the OS of the U2000 server as the Administrator user.
name="VB22">GroupID</param>
name="VB23">MaintainAlmStatus</param>
name="AdditionalVB1">0</param>
name="AdditionalVB2">1</param>
name="AdditionalVB3">2</param>
name="AdditionalVB4">3</param>
name="AdditionalVB5">4</param>
name="AdditionalVB6">5</param>
name="AdditionalVB7">6</param>
name="AdditionalVB8">7</param>
Step 7 Optional: Perform the following operations if the additional VBs are not needed.
1.
2.
3.
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
-path /imap/snmpagent/notify/transVB/Mib1/
----End
Issue 05 (2013-05-17)
91
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
l U2000 is running normally.
l The environment variables are correct. For details, refer to iManager U2000 Software
Installation Guide.
l The SNMP NBI instance is deployed and configured.
l In a high availability system, you only need to log in to the primary site to perform this
operation. But you need to modify the configuration files in primary site and secondary site.
Step 1 Log in to the OS of the U2000 server.
l
For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.
For windows, log in to the OS of the U2000 server as the Administrator user.
----End
Issue 05 (2013-05-17)
92
Answer
The OSS can change the filter criteria in real time. For details, see 6.1.2 Changing Filter
Criteria.
Step 1 Log in to the OS of the U2000 server.
l
For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.
For windows, log in to the OS of the U2000 server as the Administrator user.
Issue 05 (2013-05-17)
93
This part introduces the relations between license and SNMP interface.
The U2000 license controls the software of SNMP interface in the following three dimensions:
l
Interface function
Technical domain
Management capacity
The three dimensions depend on each other. The U2000 divides the license according to the
dimensions to dynamically control the SNMP software.
For details of Dimension, refer to Figure A-1 and Table A-1.
Figure A-1 Main dimensions
technical domain
m
ge
na
a
M
t
en
y
cit
pa
a
C
Interface Function
Issue 05 (2013-05-17)
94
Meaning
Interface function
Alarm
Technical domain
l Transmission Network
l IP
l Access Network
Management capacity
On Solaris or Linux, view the license as user root. Use the text viewer to view the contents of
the $IMAP_ROOT/etc/conf/license/LIC_ONxxxxxxx.dat file.
On Windows, view the license as user administrator. Use the text viewer to view the contents
of the %IMAP_ROOT%\etc\conf\license\LIC_ONxxxxxxx.dat file.
Here each "X" represents an integer ranging from 0 to 9. Refer to Table A-2 for the details of
license control items.
Table A-2 Description for License Item
Issue 05 (2013-05-17)
Abbreviation
Value
LNSDPENES01
0-100000
LNSDPENES02
0-100000
LNSDPENEC21
0~8000000
LNSDPENEC25
0~8000000
LNSDNELCR84
0~8000000
LNSDNELCR75
0~8000000
95
B Configuration Parameters
Configuration Parameters
The U2000 can connect to the NMS/OSS after you correctly set general parameters by using the
Msuite. You can also set advanced parameters to customize the messages queried or reported
through the SNMP NBI.
B.1 General Configuration
The SNMP NBI is used to exchange management information between the OSS and the
U2000. This NBI with the standard network management frame is provided by the U2000.
B.2 Advanced Configuration
You can set the advanced parameters for the SNMP NBI throughMsuite.
Issue 05 (2013-05-17)
96
B Configuration Parameters
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. In the dialog box that is displayed, click SNMP Agent on the General tab.
Issue 05 (2013-05-17)
97
B Configuration Parameters
Parameters
CAUTION
The trap-transmitting IP address and request-receiving IP address are both the U2000 server IP
address. Ensure that this IP address can be used for successful communication between the
U2000 and the OSS.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI. Before
configuring these ports, ensure that the specified ports are idle.
Do not use the default ports of the SNMP protocol (port 161 and port 162) to deploy the SNMP
NBI, because they are occupied by other processes.
Parameter
Value
Description
Port
Default: 6666
1025~32767
Port
Default: 9812
Recommended value:
1025~32767
SNMP version
v1, v2c, v3
Default: v1
98
B Configuration Parameters
Parameter
Value
Description
Security Model
USM model
Security Level
NONE, HMACMD5,
HMACSHA
Default: NONE
Data Encryption
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Third-Party NMS in General tab.
Issue 05 (2013-05-17)
99
B Configuration Parameters
Parameters
NOTE
The Receive Trap Address is not the IP address of the U2000 server.
Currently a maximum of 10 third-party NMSs are supported.
The same SNMPv3 user configured for different third-party NMSs, for example, NMS 1 and NMS 2, must
use the same authentication and encryption passwords
When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.
Issue 05 (2013-05-17)
If multiple OSSs use the same read or write community, only the first OSS gets the synchronized
results when any of the OSSs tries to synchronize data.
It is recommended that each OSS uses a unique read or write community so that the OSS can get
correct synchronized results.
100
B Configuration Parameters
CAUTION
To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are digits,
letters, and special characters. Remember to change passwords regularly.
The password must meet the following requirements to safeguard your user account.
l
The password must consist of three of the following types of characters at least:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and
space
Parameters
Value
Description
Receive Trap
Address
IP address
Port
Default: 6666
1025~32767
NOTE
l When the U2000 is interconnected with the OSS,
enter the port ID that is provided by the OSS.
l When the U2000 is not interconnected with the
OSS, the port ID cannot be left blank. In this case,
use the default port ID 6666.
Default
Read/Write
Community
l Read Community:
Changeme_123
l Write Community:
Changeme_123
You can also enter any
character string
consisting of 255
characters at most.
V3 User Name
Default: admin
Character string (20)
Issue 05 (2013-05-17)
101
B Configuration Parameters
Parameters
Value
Description
V3
Authentication
Password
V3 Privacy
Password
Alarm Level
Default: All
Default: Fault
Fault, Acknowledge,
Unacknowledged,
Changed
Issue 05 (2013-05-17)
102
B Configuration Parameters
B.2.1 Heartbeat
The U2000 can periodically send heartbeat information to the OSS through the SNMP NBI.
Based on the heartbeat information, the OSS determines whether the communication is
successful. The heartbeat settings are applicable to the U2000 MIB only.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Heartbeat on the Advanced tab.
Parameters
NOTE
Parameters
Value
Description
Heartbeat Period
Default: 60s
3s~300s
Report Heartbeat
Info
Default: Yes
Yes, No
103
B Configuration Parameters
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Alarm Field on the Advanced tab.
Parameters
CAUTION
This parameter is applicable to the U2000 MIB only.
This parameter is applicable to all third-party NMSs connected to the SNMP NBI.
The U2000 automatically fills the alarm field and the alarm field is not support manual setting.
Issue 05 (2013-05-17)
Name
Name in the
MIB
Description
Value
NE Name
hwNmNorthbou
ndNEName
Octet string
NE Type
hwNmNorthbou
ndNEType
Octet string
Object
instance
hwNmNorthbou
ndObjectInstanc
e
Octet string
104
B Configuration Parameters
Name
Name in the
MIB
Description
Value
Event Type
hwNmNorthbou
ndEventType
Octet string
l Communication
l Environment
l Equipment
l Service
l Processing
l Unknown
For X.733-compliant alarms, options are as
follows:
l communicationsAlarm
l environmentalAlarm
l equipmentAlarm
l qualityofServiceAlarm
l processingErrorAlarm
l Unknown_EventType
Issue 05 (2013-05-17)
105
B Configuration Parameters
Name
Name in the
MIB
Description
Value
Alarm time
hwNmNorthbou
ndEventTime
Octet string
Issue 05 (2013-05-17)
hwNmNorthbou
ndProbableCaus
e
Octet string
106
B Configuration Parameters
Name
Name in the
MIB
Description
Value
Alarm
Severity
hwNmNorthbou
ndSeverity
Octet string
Alarm
Details
hwNmNorthbou
ndEventDetail
Octet string
Alarm
Location
hwNmNorthbou
ndAdditionalInf
o
Octet string
Type Flag
hwNmNorthbou
ndFaultFlag
Octet string
Issue 05 (2013-05-17)
107
B Configuration Parameters
Name
Name in the
MIB
Description
Value
Alarm
Function
Category
hwNmNorthbou
ndFaultFunction
Octet string
l Power alarms
l Environment alarms
l Signaling alarms
l Relay alarms
l Hardware alarms
l Software alarms
l Running alarms
l Communication faults
l Service quality alarms
l Processing error alarms
l Unknown type alarms
Managed
Equipment
Address
hwNmNorthbou
ndDeviceIP
IP address
Alarm
Serial
Number
hwNmNorthbou
ndSerialNo
Integer
Alarm
Recovery
Advice
hwNmNorthbou
ndProbableRepa
ir
Octet string
Resource
ID
hwNmNorthbou
ndResourceIDs
Octet string
Event
Name
hwNmNorthbou
ndEventName
Octet string
Alarm ID
hwNmNorthbou
ndReasonID
Integer
Fault ID
hwNmNorthbou
ndFaultID
Integer
Managed
Equipment
Type
hwNmNorthbou
ndDeviceType
Octet string
Trail Name
hwNmNorthbou
ndTrailName
Octet string
Root
Alarm
hwNmNorthbou
ndRootAlarm
Integer
l 0: Non-root alarm
l 1: Root alarm
Issue 05 (2013-05-17)
108
B Configuration Parameters
Name
Name in the
MIB
Description
Value
Group ID
hwNmNorthbou
ndGroupID
Integer
Engineerin
g Alarm
Status
hwNmNorthbou
ndMaintainStatu
s
Integer
l 0: Non-engineering alarms
l 1: Engineering alarms
NOTE
NEs during engineering commissioning or
service cutover generate a large number of
alarms and you can set the NEs in engineer
maintenance state, therefore, the alarms
generated by this kind of NEs are engineering
alarms.
B.2.3 Notification
You can set the reported mode and the relevant parameters.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Notification in Advanced tab.
Issue 05 (2013-05-17)
109
B Configuration Parameters
Parameters
WARNING
l Trap mode: A received alarm is reported immediately regardless of whether the OSS returns
a response to the previous alarm reporting.
l Inform mode: A received alarm is reported immediately after the OSS returns a response to
the previous alarm reporting or the retried times is excessed. In this mode, if the parameters
configured for the OSS are incorrect, the SNMP agent tries connecting to the OSS for many
times. This will occupy a large number of resources. As a result, the efficiency of the SNMP
agent is reduced. Therefore, exercise caution when you set this parameter to Inform.
l The SNMPv1 supports the Trap mode only.
Parameter
Description
Value
Reporting Mode
Default: No
Yes, No
Trap Transmit
Interval
Default: 0
Inform Delay
Default: 5
0 ms-1000 ms
5 s - 120 s
Inform Failure
Retry
Default: 3
2 times-6 times
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Time Format on the Advanced tab.
Issue 05 (2013-05-17)
110
B Configuration Parameters
Parameters
Parameter
s
Value
Description
Alarm
Time
Format
Default: UTC
Time
UTC Time
Example: 2009/12/23 - 11:30:30Z
Local Time (without Time Zone)
The format is as YYYY/MM/DD - hh:mm:ss.
Example: 2009/12/23 - 19:30:30
Local Time (with Time Zone)
The format is as YYYY/MM/DD - hh:mm:ss,hh:mmTZ
[DST], where TZ stands for timezone information.
Example:
l 2009/12/23 - 19:30:30,+08:00[0] (if the date is not in
DST).
l 2009/12/23 - 19:30:30 +08:00[3600] (if the date is in
DST of 1 hr). The DST value is in seconds.
111
B Configuration Parameters
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Encoding Format in Advanced tab.
Parameters
Parameters
Value
Description
Alarm
Character
Default: UTF-8
UTF-8, GBK
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.On the Advanced tab, click Alarm Relativity Config.
Issue 05 (2013-05-17)
112
B Configuration Parameters
Parameters
Parameter
s
Value
Description
Alarm
Relativity
Config
Default: All
alarms
All alarms: Queries and reports all alarms including the root
alarm and correlative alarms.
All alarms,
Root Alarm
Root Alarm: Queries and reports only the root alarm and
common alarms.
NOTE
The following two correlative alarms are involved by the location relationships between correlative alarms
and root alarms:
l NE-level correlative alarms: Correlative alarms and root alarms are generated on the same NE.
l Trail-based correlative alarms: Correlative alarms and root alarms are generated on different upstream
and downstream NEs connected by services.
After alarm correlation rules are enabled on the U2000, the NBIs report correlative alarms based on the
alarm correlation analysis results on the U2000 and different NBIs have different rules for reporting
correlative alarms. The SNMP NBI supports only trail-based correlative alarms.
Issue 05 (2013-05-17)
113
B Configuration Parameters
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.On the Advanced tab, click Engineering Alarm.
Parameters
Parameters
Value
Description
Engineering
Alarm
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Other Settings in Advanced tab.
Issue 05 (2013-05-17)
114
B Configuration Parameters
Parameters
Parameters
Value
Description
Record Log
Default: No
Yes, No
Real-time Alarm
Cache Size
Default:
10000
0-50000
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose MIB Frame on the Advanced tab.
Issue 05 (2013-05-17)
115
B Configuration Parameters
Parameters
CAUTION
This setting has a direct impact on the successful communication between the U2000 and the
OSS for alarm management. Confirm the MIB frame with the MIB frame on the OSS.
Three MIB files are supported:
l
Issue 05 (2013-05-17)
116
B Configuration Parameters
Parameter
s
Value
Description
MIB
U2000 MIB,
U2000-T
MIB
Issue 05 (2013-05-17)
117
C U2000 MIB
U2000 MIB
The U2000 MIB is used mainly in the management of a multi-domain network or upgrades of
network management systems (NMSs) such as the N2000 DMS and N2000 BMS.
Both HW-IMAPV1NORTHBOUND-TRAP-MIB.mib and HWIMAPV2NORTHBOUND-TRAP-MIB.mib refer to the U2000 MIB, which is used to manage
transport, access, and datacom devices, or cross-domain devices. V1 and V2 indicate the SMI
(Structure of Management Information) versions of the HW-IMAPV1NORTHBOUNDTRAP-MIB.mib and HW-IMAPV2NORTHBOUND-TRAP-MIB.mib respectively. The
OSS selects a version based on its supported SMI version. SMI versions differ in syntax. For
details, see RFC 1155 and RFC 1902.
This document uses HW-IMAPV1NORTHBOUND-TRAP-MIB as an example.
MIB
SMI Version
HW-IMAPV1NORTHBOUND-TRAP-MIB.mib
SMI-V1
HW-IMAPV2NORTHBOUND-TRAP-MIB.mib
SMI-V2
Issue 05 (2013-05-17)
118
C U2000 MIB
The iManager U2000 SNMP NBI MIB File is available on the Huawei technical support website. To obtain
this document, contact the local technical support engineers.
Issue 05 (2013-05-17)
Name
Name in the
MIB
Description
Value
NE Name
hwNmNorthbou
ndNEName
Octet string
NE Type
hwNmNorthbou
ndNEType
Octet string
Object
instance
hwNmNorthbou
ndObjectInstanc
e
Octet string
119
C U2000 MIB
Name
Name in the
MIB
Description
Value
Event Type
hwNmNorthbou
ndEventType
Octet string
l Communication
l Environment
l Equipment
l Service
l Processing
l Unknown
For X.733-compliant alarms, options are as
follows:
l communicationsAlarm
l environmentalAlarm
l equipmentAlarm
l qualityofServiceAlarm
l processingErrorAlarm
l Unknown_EventType
Issue 05 (2013-05-17)
120
C U2000 MIB
Name
Name in the
MIB
Description
Value
Alarm time
hwNmNorthbou
ndEventTime
Octet string
Issue 05 (2013-05-17)
hwNmNorthbou
ndProbableCaus
e
Octet string
121
C U2000 MIB
Name
Name in the
MIB
Description
Value
Alarm
Severity
hwNmNorthbou
ndSeverity
Octet string
Alarm
Details
hwNmNorthbou
ndEventDetail
Octet string
Alarm
Location
hwNmNorthbou
ndAdditionalInf
o
Octet string
Type Flag
hwNmNorthbou
ndFaultFlag
Octet string
Issue 05 (2013-05-17)
122
C U2000 MIB
Name
Name in the
MIB
Description
Value
Alarm
Function
Category
hwNmNorthbou
ndFaultFunction
Octet string
l Power alarms
l Environment alarms
l Signaling alarms
l Relay alarms
l Hardware alarms
l Software alarms
l Running alarms
l Communication faults
l Service quality alarms
l Processing error alarms
l Unknown type alarms
Managed
Equipment
Address
hwNmNorthbou
ndDeviceIP
IP address
Alarm
Serial
Number
hwNmNorthbou
ndSerialNo
Integer
Alarm
Recovery
Advice
hwNmNorthbou
ndProbableRepa
ir
Octet string
Resource
ID
hwNmNorthbou
ndResourceIDs
Octet string
Event
Name
hwNmNorthbou
ndEventName
Octet string
Alarm ID
hwNmNorthbou
ndReasonID
Integer
Fault ID
hwNmNorthbou
ndFaultID
Integer
Managed
Equipment
Type
hwNmNorthbou
ndDeviceType
Octet string
Trail Name
hwNmNorthbou
ndTrailName
Octet string
Root
Alarm
hwNmNorthbou
ndRootAlarm
Integer
l 0: Non-root alarm
l 1: Root alarm
Issue 05 (2013-05-17)
123
C U2000 MIB
Name
Name in the
MIB
Description
Value
Group ID
hwNmNorthbou
ndGroupID
Integer
Engineerin
g Alarm
Status
hwNmNorthbou
ndMaintainStatu
s
Integer
l 0: Non-engineering alarms
l 1: Engineering alarms
NOTE
NEs during engineering commissioning or
service cutover generate a large number of
alarms and you can set the NEs in engineer
maintenance state, therefore, the alarms
generated by this kind of NEs are engineering
alarms.
Function
When alarms are generated on NEs or the U2000, the U2000 automatically sends this type of
traps to notify the OSS of real-time alarms through the SNMP NBI.
Trigger Condition
Alarms generated on NEs or the U2000 trigger the sending of active alarm notification traps
through the SNMP NBI.
Definition
Issue 05 (2013-05-17)
Name
Enterprise
Type
Description
hwNmNorthboundE
ventNotify
hwNmNorthboundE
ventInfo
Trap/Inform
124
C U2000 MIB
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm
notification traps are automatically sent by the U2000 while active alarm report traps are responses to
the query of active alarms from the OSS.
l Additional VBs range from hwNmNorthboundsAdditionalVB1 to
hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not
use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report
additional VBs alarm trap.
VB
OID
Data
Type
Description
hwNmNorthboundNEName
1.3.6.1.4.1.2011.2.
15.1.7.1.1
Octet
string
hwNmNorthboundNEType
1.3.6.1.4.1.2011.2.
15.1.7.1.2
Octet
string
hwNmNorthboundObjectInstance
1.3.6.1.4.1.2011.2.
15.1.7.1.3
Octet
string
hwNmNorthbound
EventType
1.3.6.1.4.1.2011.2.
15.1.7.1.4
Octet
string
Issue 05 (2013-05-17)
125
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthbound
EventTime
1.3.6.1.4.1.2011.2.
15.1.7.1.5
Octet
string
hwNmNorthboundProbableCause
1.3.6.1.4.1.2011.2.
15.1.7.1.6
Octet
string
hwNmNorthboundSeverity
1.3.6.1.4.1.2011.2.
15.1.7.1.7
Octet
string
hwNmNorthbound
EventDetail
1.3.6.1.4.1.2011.2.
15.1.7.1.8
Octet
string
hwNmNorthboundAdditionalInfo
1.3.6.1.4.1.2011.2.
15.1.7.1.9
Octet
string
hwNmNorthboundFaultFlag
1.3.6.1.4.1.2011.2.
15.1.7.1.10
Octet
string
Issue 05 (2013-05-17)
126
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthboundFaultFunction
1.3.6.1.4.1.2011.2.
15.1.7.1.11
Octet
string
Issue 05 (2013-05-17)
hwNmNorthboundDeviceIP
1.3.6.1.4.1.2011.2.
15.1.7.1.12
IP address
hwNmNorthboundSerialNo
1.3.6.1.4.1.2011.2.
15.1.7.1.13
Integer
hwNmNorthboundProbableRepair
1.3.6.1.4.1.2011.2.
15.1.7.1.14
Octet
string
hwNmNorthboundResourceIDs
1.3.6.1.4.1.2011.2.
15.1.7.1.15
Octet
string
hwNmNorthboundsAdditionalVB1
1.3.6.1.4.1.2011.2.
15.1.7.1.16
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB2
1.3.6.1.4.1.2011.2.
15.1.7.1.17
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB3
1.3.6.1.4.1.2011.2.
15.1.7.1.18
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB4
1.3.6.1.4.1.2011.2.
15.1.7.1.19
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB5
1.3.6.1.4.1.2011.2.
15.1.7.1.20
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB6
1.3.6.1.4.1.2011.2.
15.1.7.1.21
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB7
1.3.6.1.4.1.2011.2.
15.1.7.1.22
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB8
1.3.6.1.4.1.2011.2.
15.1.7.1.23
Octet
string
Reserved field.
127
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthbound
EventName
1.3.6.1.4.1.2011.2.
15.1.7.1.24
Octet
string
hwNmNorthboundReasonID
1.3.6.1.4.1.2011.2.
15.1.7.1.25
Integer
hwNmNorthboundFaultID
1.3.6.1.4.1.2011.2.
15.1.7.1.26
Integer
hwNmNorthboundDeviceType
1.3.6.1.4.1.2011.2.
15.1.7.1.27
Octet
string
hwNmNorthboundTrailName
1.3.6.1.4.1.2011.2.
15.1.7.1.28
Octet
string
hwNmNorthboundRootAlarm
1.3.6.1.4.1.2011.2.
15.1.7.1.29
Integer
hwNmNorthboundGroupID
1.3.6.1.4.1.2011.2.
15.1.7.1.30
Integer
hwNmNorthboundMaintainStatus
1.3.6.1.4.1.2011.2.
15.1.7.1.31
Integer
Function
After the OSS sends alarm query requests, the U2000 sends this type of traps to inform the OSS
that the synchronization starts.
Trigger Condition
The OSS triggers the alarm synchronization. For details, see 6.1.3 Synchronizing Alarms.
The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStart
in the following format:
NMS IP:port:start time:end time
Issue 05 (2013-05-17)
128
C U2000 MIB
NOTE
Definition
Name
Enterprise
Type
Description
hwNmNorthboundE
ventSynchronizationStartNotify
hwNmNorthboundE
ventSynchronizationStart
Trap/Inform
VB List
N/A
Function
After the OSS initiates the alarm synchronization, the U2000 sends this type of traps to report
required alarms on the U2000 to the OSS.
Trigger Condition
The OSS triggers the synchronization. For details, see 6.1.3 Synchronizing Alarms.
The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStart
in the following format:
NMS IP:port:start time:end time
NOTE
Definition
Issue 05 (2013-05-17)
Name
Enterprise
Type
Description
hwNmNorthboundE
ventSynchronizationQueryResultNotify
hwNmNorthboundE
ventSynchronizationQueryResult
Trap/Inform
Indicates the
synchronization
result or required
alarms.
129
C U2000 MIB
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm
notification traps are automatically sent by the U2000 while active alarm report traps are responses to
the query of active alarms from the OSS.
l Additional VBs range from hwNmNorthboundsAdditionalVB1 to
hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not
use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report
additional VBs alarm trap.
VB
OID
Data
Type
Description
hwNmNorthboundNEName
1.3.6.1.4.1.2011.2.
15.1.7.1.1
Octet
string
hwNmNorthboundNEType
1.3.6.1.4.1.2011.2.
15.1.7.1.2
Octet
string
hwNmNorthboundObjectInstance
1.3.6.1.4.1.2011.2.
15.1.7.1.3
Octet
string
hwNmNorthbound
EventType
1.3.6.1.4.1.2011.2.
15.1.7.1.4
Octet
string
Issue 05 (2013-05-17)
130
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthbound
EventTime
1.3.6.1.4.1.2011.2.
15.1.7.1.5
Octet
string
hwNmNorthboundProbableCause
1.3.6.1.4.1.2011.2.
15.1.7.1.6
Octet
string
hwNmNorthboundSeverity
1.3.6.1.4.1.2011.2.
15.1.7.1.7
Octet
string
hwNmNorthbound
EventDetail
1.3.6.1.4.1.2011.2.
15.1.7.1.8
Octet
string
hwNmNorthboundAdditionalInfo
1.3.6.1.4.1.2011.2.
15.1.7.1.9
Octet
string
hwNmNorthboundFaultFlag
1.3.6.1.4.1.2011.2.
15.1.7.1.10
Octet
string
Issue 05 (2013-05-17)
131
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthboundFaultFunction
1.3.6.1.4.1.2011.2.
15.1.7.1.11
Octet
string
Issue 05 (2013-05-17)
hwNmNorthboundDeviceIP
1.3.6.1.4.1.2011.2.
15.1.7.1.12
IP address
hwNmNorthboundSerialNo
1.3.6.1.4.1.2011.2.
15.1.7.1.13
Integer
hwNmNorthboundProbableRepair
1.3.6.1.4.1.2011.2.
15.1.7.1.14
Octet
string
hwNmNorthboundResourceIDs
1.3.6.1.4.1.2011.2.
15.1.7.1.15
Octet
string
hwNmNorthboundsAdditionalVB1
1.3.6.1.4.1.2011.2.
15.1.7.1.16
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB2
1.3.6.1.4.1.2011.2.
15.1.7.1.17
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB3
1.3.6.1.4.1.2011.2.
15.1.7.1.18
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB4
1.3.6.1.4.1.2011.2.
15.1.7.1.19
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB5
1.3.6.1.4.1.2011.2.
15.1.7.1.20
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB6
1.3.6.1.4.1.2011.2.
15.1.7.1.21
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB7
1.3.6.1.4.1.2011.2.
15.1.7.1.22
Octet
string
Reserved field.
hwNmNorthboundsAdditionalVB8
1.3.6.1.4.1.2011.2.
15.1.7.1.23
Octet
string
Reserved field.
132
C U2000 MIB
VB
OID
Data
Type
Description
hwNmNorthbound
EventName
1.3.6.1.4.1.2011.2.
15.1.7.1.24
Octet
string
hwNmNorthboundReasonID
1.3.6.1.4.1.2011.2.
15.1.7.1.25
Integer
hwNmNorthboundFaultID
1.3.6.1.4.1.2011.2.
15.1.7.1.26
Integer
hwNmNorthboundDeviceType
1.3.6.1.4.1.2011.2.
15.1.7.1.27
Octet
string
hwNmNorthboundTrailName
1.3.6.1.4.1.2011.2.
15.1.7.1.28
Octet
string
hwNmNorthboundRootAlarm
1.3.6.1.4.1.2011.2.
15.1.7.1.29
Integer
hwNmNorthboundGroupID
1.3.6.1.4.1.2011.2.
15.1.7.1.30
Integer
hwNmNorthboundMaintainStatus
1.3.6.1.4.1.2011.2.
15.1.7.1.31
Integer
Function
The U2000 sends this type of traps to inform the OSS that the alarm synchronization completes.
Trigger Condition
Active alarm synchronization end traps are triggered when:
l
All required alarms have been reported to the OSS in trap packets.
The OSS triggers the termination of synchronization. For details, see 6.1.3 Synchronizing
Alarms.
The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStop
on the designated U2000 in the following format:
Issue 05 (2013-05-17)
133
C U2000 MIB
NMS IP:port
NOTE
NMS IP:port refers to the IP address and port of the OSS server.
Definition
Name
Enterprise
Type
Description
hwNmNorthboundE
ventSynchronizationEndNotify
hwNmNorthboundE
ventSynchronizationEnd
Trap/Inform
VB List
In the following table, listed data types for interconnection using the SNMPv1 protocol. Most
of these data types are applicable to the SNMPv2c and SNMPv3 protocols. For any differences,
details will be described in brackets.
VB
OID
Data
Type
Description
hwNmNorthbound
EventSynchronizationEndStatus
1.3.6.1.4.1.2011.2.
15.1.7.7.3.1
Integer
hwNmNorthbound
EventSynchronizationEndStatusDetail
1.3.6.1.4.1.2011.2.
15.1.7.7.3.2
Octet
string
Description
U2000 sends the KeepAlive info (heartbeat) to the NMS/OSS regularly each period. If the NMS
receives the trap, the connection between the NMS/OSS and the U2000 works. If the NMS/OSS
Issue 05 (2013-05-17)
134
C U2000 MIB
does not receive the trap in this period and the heartbeat is enabled, it indicates that the NMS/
OSS disconnects with the U2000.
NOTE
You can configure the heartbeat, for details, see B.2.1 Heartbeat.
Condition
The U2000 sends the keepAlive info (heartbeat) trap to the NMS/OSS regularly in the preset
period.
Trap Definition
Name
ENTERPRISE
Type
Description
hwNmNorthboundE
ventKeepAlive
hwNmNorthboundE
ventKeepAliveInfo
Trap/Inform
Field List
In the following table, by default, the field types are those used for the connection with SNMPv1.
For SNMPv2c or SNMPv3, the same data types will not be introduced again. Different data
types are remarked in brackets.
Name
OID
Data Type
Descriptio
n
hwNmAgent
1.3.6.1.4.1.2011.2.15.1
OCTET STRING
By default,
this field is
reported.
hwNmNorthboundKeepAlive
1.3.6.1.4.1.2011.2.15.1.7.2.1
OCTET STRING
You can
make
configuratio
ns for the
heartbeat
notification
trap to report
this field.
CAUTION
By default, the heartbeat notification trap reports the hwNMAgent field. You can make
modifications for the trap to report the hwNmNorthboundKeepAlive field. For details, see 7.3.7
How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive.
Issue 05 (2013-05-17)
135
C U2000 MIB
File Path
server/conf/snmpagent.cfg
server/etc/conf/snmp_agent_svc.xml
T2000supp
ort
Configurat
ion Item
Example Value of
hwNmNorthboundObjectInstance
Description
Managing
multipledomain NEs
<param
name="T20
00Support"
>0</param>
hwNmNorthboundObjectInstance.0 ***
(octets) Slot=4 Port=1
TTP_TYPE=1 4N1SL16-1(SDH-1)-SPI:
1
Issue 05 (2013-05-17)
136
C U2000 MIB
Scenario
T2000supp
ort
Configurat
ion Item
Example Value of
hwNmNorthboundObjectInstance
Description
Managing
optical NEs
of the
transport
domain
<param
name="T20
00Support"
>1</param>
hwNmNorthboundObjectInstance.0 ***
(octets) source=NE
(9-3500) location=4N1SL16-1(SDH-1)-SPI:
1
<param name="T2000Support">0</param>
13: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1
trap(v1) received from: 10.71.224.13 at 2011-12-27 16:19:58
Time stamp: 0 days 00h:05m:29s.09th
Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.224.13
Enterprise: hwNmNorthboundEventInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAPMIB, Enterprise: hwNmNorthboundEventInfo
Bindings (19)
Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)
Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500
Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) Slot=4 Port=1
TTP_TYPE=1 4-N1SL16-1(SDH-1)-SPI:1
Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication
Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 16:11:30
Binding #6: hwNmNorthboundProbableCause.0 *** (octets) ID:
1,DeviceType:0,\(1)The fiber jumper is not connected at the optical
interface of the board;\(2)The laser of the board on the opposite station
is shutdown;\(3)A fiber break occurs in the transm ...
Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical
Binding #8: hwNmNorthboundEventDetail.0 *** (octets) ID:1,DeviceType:
0,Loss of signal
Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)
Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01
Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault
Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication
Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97
Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85415
Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) ID:
1,DeviceType:0,
Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)
3145893.-1.4.1.1.1.-1.-1
Binding #16: hwNmNorthboundEventName.0 *** (octets) ID:1,DeviceType:
0,R_LOS
Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1
Binding #18: hwNmNorthboundFaultID.0 *** (int32) 1
Issue 05 (2013-05-17)
137
#19:
#20:
#21:
#22:
#23:
C U2000 MIB
<param name="T2000Support">1</param>
21: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1
trap(v1) received from: 10.71.224.13 at 2011-4-27 16:25:24
Time stamp: 0 days 00h:02m:02s.27th
Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.224.13
Enterprise: hwNmNorthboundEventInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAPMIB, Enterprise: hwNmNorthboundEventInfo
Bindings (19)
Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)
Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500
Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) source=NE
(9-3500) location=4-N1SL16-1(SDH-1)-SPI:1
Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication
Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 16:11:30
Binding #6: hwNmNorthboundProbableCause.0 *** (octets) \(1)The fiber
jumper is not connected at the optical interface of the board;\(2)The
laser of the board on the opposite station is shutdown;\(3)A fiber break
occurs in the transmission line;\(4) T ...
Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical
Binding #8: hwNmNorthboundEventDetail.0 *** (octets) Loss of signal
Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)
Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01
Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault
Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication
Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97
Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85417
Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) (zerolength)
Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)
3145893.-1.4.1.1.1.-1.-1
Binding #16: hwNmNorthboundEventName.0 *** (octets) R_LOS
Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1
Binding #18: hwNmNorthboundFaultID.0 *** (int32) 1
Binding #19: hwNmNorthboundDeviceType.0 *** (octets) 0
Binding #20: hwNmNorthboundTrailName.0 *** (octets) PWE3:2
Binding #21: hwNmNorthboundRootAlarm.0 *** (int32) 0
Binding #22: hwNmNorthboundGroupID.0 *** (int32) 268374017
Binding #23: hwNmNorthboundMaintainStatus.0 *** (int32) 0
Issue 05 (2013-05-17)
138
C U2000 MIB
15:56:45
Time stamp: 0 days 00h:06m:24s.69th
Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.88.151
Enterprise: hwNmNorthboundEventSynchronizationStart
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventSynchronizationStartNotify, Module: HWIMAPV1NORTHBOUND-TRAP-MIB, Enterprise:
hwNmNorthboundEventSynchronizationStart
Bindings (0)
None.
Issue 05 (2013-05-17)
139
#18:
#19:
#20:
#21:
#22:
#23:
C U2000 MIB
Issue 05 (2013-05-17)
140
C U2000 MIB
C.4.5 Heartbeat
The SNMP NBI sends the heartbeat trap to the NMS/OSS periodically. The NMS/OSS can check
the connection status by the heartbeat.
NOTE
Two OIDs are supported. For their configurations, see 7.3.7 How to configure the heartbeat notification trap
to hwNmNorthboundKeepAlive.
hwNmAgent (default)
795: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.71.88.151 at 2010-11-24 15:57:20
Time stamp: 0 days 00h:07m:00s.12th
Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.88.151
Enterprise: hwNmNorthboundEventKeepAliveInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAPMIB, Enterprise: hwNmNorthboundEventKeepAliveInfo
Bindings (1)
Binding #1: hwNmAgent *** (octets) SNMP Agent
hwNmNorthboundKeepAlive (configurable-1.3.6.1.4.1.2011.2.15.1.7.2.1)
8: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.67.192.220 at 2012/6/26 11:19:13
Time stamp: 0 days 00h:00m:15s.04th
Agent address: 10.67.192.220 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.66.102.169 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.67.192.220
Enterprise: hwNmNorthboundEventKeepAliveInfo
Issue 05 (2013-05-17)
141
C U2000 MIB
hwNmNorthboundKeepAlive (configurable-1.3.6.1.4.1.2011.2.15.1.7.2.1.0)
3: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.78.219.70 at 2012/7/26 19:11:29
Time stamp: 0 days 00h:01m:45s.11th
Agent address: 10.78.219.70 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.66.103.78 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.78.219.70
Enterprise: hwNmNorthboundEventKeepAliveInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAPMIB, Enterprise: hwNmNorthboundEventKeepAliveInfo
Bindings (1)
Binding #1: hwNmNorthboundKeepAlive.0 *** (octets) SNMP Agent
Issue 05 (2013-05-17)
142
D U2000-T MIB
U2000-T MIB
Issue 05 (2013-05-17)
143
D U2000-T MIB
The iManager U2000 SNMP NBI MIB File is available on the Huawei technical support website. To obtain
this document, contact the local technical support engineers.
Description
Value
EMS Name
northboundReportAlarmEmsName
EMS name.
Octet string
northboundReportAlarmManagedObjectClass
northboundReportAlarmManagedObjectInstance
northboundReportAlarmNEName
Equipment
Type
Equipment
Name
NE Name
Issue 05 (2013-05-17)
144
D U2000-T MIB
Name
Description
Value
Rack Name
northboundReportAlarmRackName
Octet string
northboundReportAlarmShelfName
Octet string
northboundReportAlarmDevLocation
Octet string
northboundReportAlarmBoardName
Octet string
Port Number
Location of
an Alarm
Object
northboundReportAlarmPortType
Port type.
northboundReportAlarmPortNumber
Port number.
northboundReportAlarmLocation
Octet string
For example, 1.
Octet string
Issue 05 (2013-05-17)
145
D U2000-T MIB
Name
Description
Value
Alarm Type
northboundReportAlarmEventType
Alarm type.
Octet string
Alarm Rising
Time
northboundReportAlarmEventTime
Octet string
For example,
2005-10-14,17:41:04.0.
Alarm
Severity
northboundReportAlarmPerceivedSeverity
Alarm severity.
Octet string
Possible
Alarm Cause
northboundReportAlarmProbableCause
Alarm Cause
northboundReportAlarmSpecificProblems
Alarm cause.
northboundReportAlarmOperationAffected
Affect
Service
Octet string
For example, NE
communication was lost
Integer
Alarm ID
Alarm Name
Issue 05 (2013-05-17)
northboundReportAlarmID
Alarm ID.
northboundReportAlarmName
Alarm name.
Integer
146
D U2000-T MIB
Name
Description
Value
Advice on
Fixing an
Alarm
northboundReportAlarmProposedRepairActions
Octet string
Serial
Number of an
Alarm
northboundReportAlarmNotificationIdentifier
ID of the
Resource for
Alarm Rising
northboundReportAlarmResourceID
Additional
Information
northboundReportAlarmAdditionalText
Additional information.
Clear Alarm
northboundReportAlarmCleared
IP address
Serial
Number of
the Alarm to
Be Cleared
northboundReportAlarmCorrelatedNotifications
Additional
Alarm
Information
(10 Fields)
northboundReportAlarmAdditionalVB
Additional information of an
alarm.
Integer
Issue 05 (2013-05-17)
147
D U2000-T MIB
Trigger Condition
When alarms are generated on NEs or the U2000, active alarm report traps are triggered.
Definition
Name
Enterprise
Type
Description
northBoundReportAlarm
northboundNotificationType
Trap
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm notification
traps are automatically sent by the U2000 while active alarm report traps are used as responses to OSS
queries.
VB
OID
Type
Description
northboundReportAlarmManagedObjectClass
1.3.6.1.4.1.
2011.2.15.
1.7.3.1
Octet string
northboundReportAlarmManagedObjectInstance
1.3.6.1.4.1.
2011.2.15.
1.7.3.2
Octet string
northboundReportAlarmEventType
1.3.6.1.4.1.
2011.2.15.
1.7.3.3
Octet string
Issue 05 (2013-05-17)
148
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmEventTime
1.3.6.1.4.1.
2011.2.15.
1.7.3.4
Octet string
northboundReportAlarmProbableCause
1.3.6.1.4.1.
2011.2.15.
1.7.3.5
Octet string
northboundReportAlarmSpecificProblems
1.3.6.1.4.1.
2011.2.15.
1.7.3.6
Octet string
northboundReportAlarmPerceivedSeverity
1.3.6.1.4.1.
2011.2.15.
1.7.3.7
Octet string
northboundReportAlarmNotificationIdentifier
1.3.6.1.4.1.
2011.2.15.
1.7.3.8
Integer
northboundReportAlarmCorrelatedNotifications
1.3.6.1.4.1.
2011.2.15.
1.7.3.9
Integer
northboundReportAlarmProposedRepairActions
1.3.6.1.4.1.
2011.2.15.
1.7.3.10
Octet string
northboundReportAlarmAdditionalText
1.3.6.1.4.1.
2011.2.15.
1.7.3.11
Octet string
northboundReportAlarmEmsName
1.3.6.1.4.1.
2011.2.15.
1.7.3.12
Octet string
northboundReportAlarmNEName
1.3.6.1.4.1.
2011.2.15.
1.7.3.13
Octet string
Issue 05 (2013-05-17)
149
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmDevLocation
1.3.6.1.4.1.
2011.2.15.
1.7.3.14
Octet string
1.3.6.1.4.1.
2011.2.15.
1.7.3.15
Octet string
1.3.6.1.4.1.
2011.2.15.
1.7.3.16
Octet string
northboundReportAlarmRackName
northboundReportAlarmShelfName
northboundReportAlarmBoardName
1.3.6.1.4.1.
2011.2.15.
1.7.3.17
Octet string
northboundReportAlarmPortType
1.3.6.1.4.1.
2011.2.15.
1.7.3.18
Octet string
northboundReportAlarmPortNumber
1.3.6.1.4.1.
2011.2.15.
1.7.3.19
Integer
northboundReportAlarmLocation
1.3.6.1.4.1.
2011.2.15.
1.7.3.20
Octet string
northboundReportAlarmOperationAffected
1.3.6.1.4.1.
2011.2.15.
1.7.3.21
Octet string
northboundReportAlarmID
Issue 05 (2013-05-17)
1.3.6.1.4.1.
2011.2.15.
1.7.3.22
Integer
150
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmName
1.3.6.1.4.1.
2011.2.15.
1.7.3.23
Octet string
northboundReportAlarmIPAddress
1.3.6.1.4.1.
2011.2.15.
1.7.3.24
IP address
1.3.6.1.4.1.
2011.2.15.
1.7.3.25
Integer
1.3.6.1.4.1.
2011.2.15.
1.7.3.26
Integer
northboundReportAlarmResourceID
northboundReportAlarmCleared
northboundReportAlarmAdditionalVB1VB10
1.3.6.1.4.1.
2011.2.15.
1.7.3.27
Octet string
Trigger Condition
The OSS triggers the synchronization. For details, see 6.2.2 Synchronizing Alarms.
The OSS sets northBoundSynchAlarmCommand to 1.
NOTE
Definition
Issue 05 (2013-05-17)
Name
Enterprise
Type
Description
northBoundSynchAlarmStart
northboundNotificationType
Trap
151
D U2000-T MIB
VB List
N/A
Trigger Condition
The OSS triggers the synchronization. For details, see 6.2.2 Synchronizing Alarms.
The OSS sets northBoundSynchAlarmCommand to 1.
NOTE
Definition
Name
Enterprise
Type
Description
northBoundSynchAlarm
northboundNotificationType
Trap/Inform
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm notification
traps are automatically sent by the U2000 while active alarm report traps are used as responses to OSS
queries.
Issue 05 (2013-05-17)
VB
OID
Type
Description
northboundReportAlarmManagedObjectClass
1.3.6.1.4.1.
2011.2.15.
1.7.3.1
Octet string
northboundReportAlarmManagedObjectInstance
1.3.6.1.4.1.
2011.2.15.
1.7.3.2
Octet string
152
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmEventType
1.3.6.1.4.1.
2011.2.15.
1.7.3.3
Octet string
northboundReportAlarmEventTime
1.3.6.1.4.1.
2011.2.15.
1.7.3.4
Octet string
northboundReportAlarmProbableCause
1.3.6.1.4.1.
2011.2.15.
1.7.3.5
Octet string
northboundReportAlarmSpecificProblems
1.3.6.1.4.1.
2011.2.15.
1.7.3.6
Octet string
northboundReportAlarmPerceivedSeverity
1.3.6.1.4.1.
2011.2.15.
1.7.3.7
Octet string
Issue 05 (2013-05-17)
northboundReportAlarmNotificationIdentifier
1.3.6.1.4.1.
2011.2.15.
1.7.3.8
Integer
northboundReportAlarmCorrelatedNotifications
1.3.6.1.4.1.
2011.2.15.
1.7.3.9
Integer
northboundReportAlarmProposedRepairActions
1.3.6.1.4.1.
2011.2.15.
1.7.3.10
Octet string
northboundReportAlarmAdditionalText
1.3.6.1.4.1.
2011.2.15.
1.7.3.11
Octet string
153
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmEmsName
1.3.6.1.4.1.
2011.2.15.
1.7.3.12
Octet string
northboundReportAlarmNEName
1.3.6.1.4.1.
2011.2.15.
1.7.3.13
Octet string
northboundReportAlarmDevLocation
northboundReportAlarmRackName
northboundReportAlarmShelfName
1.3.6.1.4.1.
2011.2.15.
1.7.3.14
Octet string
1.3.6.1.4.1.
2011.2.15.
1.7.3.15
Octet string
1.3.6.1.4.1.
2011.2.15.
1.7.3.16
Octet string
northboundReportAlarmBoardName
1.3.6.1.4.1.
2011.2.15.
1.7.3.17
Octet string
northboundReportAlarmPortType
1.3.6.1.4.1.
2011.2.15.
1.7.3.18
Octet string
northboundReportAlarmPortNumber
1.3.6.1.4.1.
2011.2.15.
1.7.3.19
Integer
northboundReportAlarmLocation
1.3.6.1.4.1.
2011.2.15.
1.7.3.20
Octet string
Issue 05 (2013-05-17)
154
D U2000-T MIB
VB
OID
Type
Description
northboundReportAlarmOperationAffected
1.3.6.1.4.1.
2011.2.15.
1.7.3.21
Octet string
northboundReportAlarmID
1.3.6.1.4.1.
2011.2.15.
1.7.3.22
Integer
northboundReportAlarmName
1.3.6.1.4.1.
2011.2.15.
1.7.3.23
Octet string
northboundReportAlarmIPAddress
1.3.6.1.4.1.
2011.2.15.
1.7.3.24
IP address
1.3.6.1.4.1.
2011.2.15.
1.7.3.25
Integer
1.3.6.1.4.1.
2011.2.15.
1.7.3.26
Integer
northboundReportAlarmResourceID
northboundReportAlarmCleared
northboundReportAlarmAdditionalVB1VB10
1.3.6.1.4.1.
2011.2.15.
1.7.3.27
Octet string
Trigger Condition
Active alarm synchronization end traps are triggered when:
l
All required alarms have been reported to the OSS in trap mode.
The OSS triggers the termination of synchronization. For details, see 6.2.2 Synchronizing
Alarms.
Issue 05 (2013-05-17)
155
D U2000-T MIB
Definition
Name
Enterprise
Type
Description
northBoundSynchAlarmEnd
northboundNotificationType
Trap/Inform
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
VB
OID
Data
Type
Description
northBoundSynchAlarmEndStatus
1.3.6.1.4.1.2011.2.
15.1.7.4.3
Integer
Issue 05 (2013-05-17)
156
D U2000-T MIB
Issue 05 (2013-05-17)
157
D U2000-T MIB
Issue 05 (2013-05-17)
158
D U2000-T MIB
159
D U2000-T MIB
Issue 05 (2013-05-17)
160
This appendix describes service ports of the Northbound Interface and how to query the service
ports.
E.1 Notes and Precautions
E.2 Port Used Between the U2000 Server and the OSS
This topic describes the port used between the U2000 server and the OSS.
Issue 05 (2013-05-17)
161
The service ports used by the NMS should not be closed. Run the following command to
view the system service ports:
netstat -an
If there are routers or firewalls between the source and the sink, check all ports used by the
source and the sink. Make sure that these ports can be normally turned up to support the
communication between the source and sink.
E.2 Port Used Between the U2000 Server and the OSS
This topic describes the port used between the U2000 server and the OSS.
If a firewall is deployed between the U2000 server and the OSS, ensure that any port on the OSS
can set up connections with ports on the U2000 through the firewall. For ports used by the U2000,
see U2000 Communication Port Matrix.
Issue 05 (2013-05-17)
162
F Equipment Supported
Equipment Supported
Transport Equipment
Table F-1 Transport equipment supported by the SNMP NBI
Featu
re
MST
P
Hybri
d
MST
P
WD
M
OTN
Hybri
d
RTN
(TD
M
Featu
re)
TDM
RTN
Packe
t RTN
PTN
Mari
ne
Alarm
NOTE
Router Equipment
Table F-2 Router equipment supported by the SNMP NBI
Issue 05 (2013-05-17)
Feature
NE Series
CX Series
Huawei
Switch
BRAS
ATN
Security
Alarm
163
F Equipment Supported
NOTE
Access Equipment
Table F-3 Access equipment supported by the SNMP NBI
Feature
Alarm
Issue 05 (2013-05-17)
MSAN/DSLAM
FTTx
Narrowband
Port
Broadband
Port
FTTH
FTTB/FTTC
164
I
IP
Internet Protocol
M
MC
Monitor Center
MIB
N
NBI
Northbound Interface
NE
Network Element
NMC
NMS
P
PDU
S
SMI
SNMP
T
TCP
TMN
V
Issue 05 (2013-05-17)
165
VB
Issue 05 (2013-05-17)
166