m2000 northbound alarm snmp interface developer guide
TRANSCRIPT
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
1/86
M2000
V200R012C00
Northbound Alarm SNMP Interface
Developer Guide
Issue 01
Date 2012-04-20
HUAWEI TECHNOLOGIES CO., LTD.
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
2/86
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
http://www.huawei.com/ -
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
3/86
About This Document
Purpose
This document provides information about the M2000 northbound alarm SNMP interface. The
document also provides operation guidelines for connecting the network management system
(NMS).
Related Versions
The following table lists product versions related to this document.
Product Name Version
M2000 V200R012C00
Intended Audience
This document is intended for:
Network management engineers
Change History
01 (2012-04-20)
This issue is the first official release. Compared with issue Draft A (2012-02-10), this issue
incorporates the changes listed in the following table.
M2000
Northbound Alarm SNMP Interface Developer Guide About This Document
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
ii
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
4/86
Change Description
l 1.5 Security Mechanism of
Northbound Alarm SNMP
Interface
l 6 Appendix: Scripts of the
Northbound Alarm SNMP
Interface
Added.
1.6 Configuration File of the
Northbound Alarm SNMP
Interface
Modified.
Draft A (2012-02-10)
This issue is a draft.
Organization
1 Introduction to Northbound Alarm SNMP Interface
This chapter describes the position of the northbound SNMP interface, the protocols that the
northbound interface supports, and the interconnection of the northbound alarm SNMP interface.
2 Trap Configuration Information of the Northbound Alarm SNMP Interface (M2000MIB)
This chapter describes configuration information about the alarm traps for the northbound alarm
SNMP interface. It covers the following sections: overview, real-time alarm trap, active alarm
trap, start trap for querying active alarms, end trap for querying active alarms, and heartbeat
notification trap.
3 Trap Configuration Information of the Northbound Alarm SNMP Interface (HW MIB)
The HW-IMAPV1NORTHBOUND-TRAP-MIB (HW MIB for short) is used mainly in the
management of a multi-domain network or upgrades of network management systems (NMSs).
4 Interconnection Commissioning of the Northbound Alarm SNMP Interface
Before interconnecting the NMS with the M2000, you must conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound SNMP
interface meets the conditions for interconnecting with the NMS.
5 Troubleshooting the Northbound Alarm SNMP Interface
If a fault occurs when the NMS interconnects to the M2000 through the northbound SNMP
interface, you need to adopt proper measures to rectify the fault. This chapter describes the
process and methods for handling faults related to the northbound SNMP interface.
6 Appendix: Scripts of the Northbound Alarm SNMP Interface
This section describes the scripts provided by the northbound alarm SNMP interface.
M2000
Northbound Alarm SNMP Interface Developer Guide About This Document
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
iii
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
5/86
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
M2000
Northbound Alarm SNMP Interface Developer Guide About This Document
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
iv
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
6/86
Convention Description
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldfaceand separated by the ">"
signs. For example, choose File> Create> Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enterand press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+Ameans the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, Ameansthe two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
M2000
Northbound Alarm SNMP Interface Developer Guide About This Document
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
v
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
7/86
Action Description
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move thepointer to a certain position.
M2000
Northbound Alarm SNMP Interface Developer Guide About This Document
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
vi
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
8/86
Contents
About This Document.....................................................................................................................ii
1 Introduction to Northbound Alarm SNMP Interface.............................................................1
1.1 Definition of Northbound Interface....................................................................................................................3
1.2 Definitionof Northbound Alarm SNMP Interface.............................................................................................31.3 MIB of the Northbound Alarm SNMP Interface................................................................................................4
1.4 Functions of the Northbound Alarm SNMP Interface........................................................................................5
1.4.1 Functions Supported by M2000 MIB........................................................................................................5
1.4.2 Functions Supported by HW MIB...........................................................................................................11
1.5 Security Mechanism of Northbound Alarm SNMP Interface..........................................................................12
1.6 Configuration File of the Northbound Alarm SNMP Interface........................................................................15
1.7 Mechanism for Forwarding Common Alarms..................................................................................................37
1.8 Technical Specifications of Northbound Alarm SNMP Interface....................................................................39
2 Trap Configuration Information of the Northbound Alarm SNMP Interface (M2000MIB)...................................................................................................................................................40
2.1 Real-Time Alarm Trap.....................................................................................................................................41
2.1.1 Format of the Real-Time Alarm Trap......................................................................................................41
2.1.2 Fields in the Real-Time Alarm Trap........................................................................................................44
2.1.3 Definition of the Real-Time Alarm Trap.................................................................................................48
2.2 Active Alarm Trap............................................................................................................................................48
2.2.1 Format of the Active Alarm Trap............................................................................................................48
2.2.2 Fields of the Active Alarm Trap..............................................................................................................48
2.2.3 Definition of the Active Alarm Trap.......................................................................................................49
2.3 Start Trapfor Querying Active Alarms............................................................................................................49
2.4 End Trap for Querying Active Alarms.............................................................................................................49
2.5 HeartbeatNotification Trap..............................................................................................................................50
3 Trap Configuration Information of the Northbound Alarm SNMP Interface (HW MIB)............................................................................................................................................................51
3.1 Active Alarm Notification Trap.......................................................................................................................52
3.2 Active Alarm Synchronization Start Trap........................................................................................................55
3.3 Active Alarm Report Trap................................................................................................................................56
3.4 Active Alarm Synchronization End Trap.........................................................................................................60
3.5 KeepAlive Info (Heartbeat) Trap......................................................................................................................61
M2000
Northbound Alarm SNMP Interface Developer Guide Contents
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
vii
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
9/86
4 Interconnection Commissioning of the Northbound Alarm SNMP Interface................63
4.1 Negotiating the Interconnection Parameters of the Northbound Alarm SNMP Interface................................64
4.2 Commissioning the Interconnection of the Northbound Alarm SNMP Interface............................................65
4.2.1 Checking License (Alarm SNMP Interface)............................................................................................65
4.2.2 Commissioning the Interconnection of the Northbound Alarm SNMP Interface...................................65
5 Troubleshooting the Northbound Alarm SNMP Interface.................................................69
5.1 Common Troubleshooting and Information Collection (Alarm SNMP Interface)..........................................71
5.2 Troubleshooting Failure to Start the Northbound Alarm SNMP Interface Service After the M2000 Starts
................................................................................................................................................................................72
5.3 Troubleshooting Failure to Make New Settings Take Effect After Modifying the Configuration File...........73
5.4 Troubleshooting Inconsistency Between the Number of Fields Actually Reported and That of Fields in the
Configuration File...................................................................................................................................................73
5.5 Troubleshooting an Issue in Which No SNMP Log Is Recorded in the Specified File...................................74
5.6 Troubleshooting an Issue in Which Users Can Pass SNMPv3 Authentication with Only Part of the CyclicPassword.................................................................................................................................................................74
5.7 How to Set Northbound Interface Compatibility.............................................................................................75
5.8 How to Set Parameters in a Northbound Configuration File............................................................................76
6 Appendix: Scripts of the Northbound Alarm SNMP Interface..........................................77
M2000
Northbound Alarm SNMP Interface Developer Guide Contents
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
viii
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
10/86
1Introduction to Northbound Alarm SNMPInterface
About This Chapter
This chapter describes the position of the northbound SNMP interface, the protocols that the
northbound interface supports, and the interconnection of the northbound alarm SNMP interface.
1.1 Definition of Northbound Interface
The northbound interface links the element management system (EMS) and the NMS.
1.2 Definition of Northbound Alarm SNMP Interface
The M2000 northbound alarm SNMP interface connects the NMSwith the EMS. This interfaceserves as an external interface in the entire M2000 system.
1.3 MIB of the Northbound Alarm SNMP Interface
The Management Information Base (MIB) is a key part of the SNMP network management
framework.
1.4 Functionsof the Northbound Alarm SNMP Interface
The M2000 northbound alarm SNMP interface provides different management information
bases (MIBs) and supports different functions when different MIBs are loaded.
1.5 Security Mechanism of Northbound Alarm SNMP Interface
The security mechanism used by the northbound alarm SNMP interface is also the security
mechanism of the SNMP protocol. Any access to the northbound alarm SNMP interface mustbe authenticated by the security mechanism of the specific SNMP version (SNMPv1, SNMPv2c,
and SNMPv3).
1.6 Configuration File of the Northbound Alarm SNMP Interface
This section describes the configuration file of the northbound alarm SNMP interface.
1.7 Mechanism for Forwarding Common Alarms
If the base stations of a multi-mode base station (MBTS) report common alarms simultaneously
to the M2000, the repeatedly reported alarms that are then forwarded from the M2000 to the
NMS may affect NMS services. The M2000 northbound interface provides policies for
M2000 users to determine whether to forward common alarms that are reported by different BSs
to the NMS.
1.8 Technical Specifications of Northbound Alarm SNMP Interface
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
1
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
11/86
This section describes the technical specifications related to the northbound alarm SNMP
interface.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
2
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
12/86
1.1 Definition of Northbound Interface
The northbound interface links the element management system (EMS) and the NMS.
The NMS obtains information about the network elements (NEs) managed by the EMS and
delivers operation commands through the northbound interface. The NE information includes
the alarm, configuration, performance, and inventory data. Figure 1-1shows the position of the
northbound interface in the network.
Figure 1-1Position of the northbound interface
In the communication network, the M2000 provides the alarm, configuration, performance, and
inventory data of NEs to the NMS through the northbound interface.
1.2 Definition of Northbound Alarm SNMP Interface
The M2000 northbound alarm SNMP interface connects the NMS with the EMS. This interface
serves as an external interface in the entire M2000 system.
The M2000 supports SNMPv1, SNMPv2c, and SNMPv3. The NMS obtains information about
the supported protocol versions from the M2000 administrator.
Figure 1-2shows the position of the northbound alarm SNMP interface in the network.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
3
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
13/86
Figure 1-2Network position of the northbound alarm SNMP interface
The M2000 northbound alarm SNMP interface receives commands issued by the NMS according
to the SNMP protocol. Then, the interface responds to the commands and sends traps to informthe NMS.
The SNMP is an industry standard protocol that is widely used for network management. It
ensures that:
l You can transmit management information between any two nodes.
l The administrator can search for and modify information, and locate faults at any node in
the network.
l The administrator can diagnose the faults, plan the capacity, and generate reports.
The features of the SNMP are as follows:
l Uses the polling mechanism to provide a basic function set. This ensures that the SNMP
fits small-sized, quick, and low-cost network scenarios.
l Requires the User Datagram Protocol (UDP) only.
1.3 MIB of the Northbound Alarm SNMP Interface
The Management Information Base (MIB) is a key part of the SNMP network management
framework.
The MIB is the object set managed by SNMP, including all the variables to be managed. All theSNMP operations such as Get and Set, apply to the managed objects in the MIB.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
4
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
14/86
The MIB defines the managed objects that are used by the function interfaces of the SNMP
northbound interface. The definitions determine the operations that the NMS can do and the
network management information that the NMS can obtain.
The International Organization for Standardization (ISO) assigns MIB node 2011 to Huawei
Technologies Co., Ltd.. Huawei Technologies Co., Ltd. assign MIB node 2011.2.15 to the NMS.The NMS assigns MIB node 2 to the SNMP northbound interface. Therefore, the complete MIB
node information is:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).iMAP(2011).products
(2).iMAPNetManagement(15).iMAPNorthbound(2)
IMAP-NORTHBOUND-MIBdefines the root node information of the SNMP northbound
interface.
The SNMP northbound interface further assigns the MIB node information based on the root
node. The MIB node information is as follows:
--- iMAP(2011)
|--- products (2)
|--- iMAPNetManagement(15)
|--- iMAPNorthbound (2)
|---- iMAPNorthboundCommon(1)
|---- iMAPNorthboundFault(4)
iMAPNorthboundFaultdefines the alarm subinterface of the SNMP northbound interface.
NOTE
In later sections, the following acronyms are used to describe the MIB nodes:
l NA: Not Accessible
l RC: Read and Create
lRW: Read and Write
l RO: Read Only
1.4 Functions of the Northbound Alarm SNMP Interface
The M2000 northbound alarm SNMP interface provides different management information
bases (MIBs) and supports different functions when different MIBs are loaded.
Telecom operators can choose the MIB files to be loaded based on their requirements to facilitate
network maintenance and management.
l M2000 MIB: loaded for managing radio access network (RAN) and core network (CN)
devices.
l HW MIB: loaded for managing microwave and IP networking devices.
1.4.1 Functions Supported by M2000 MIB
This section describes the SNMP versions that the M2000 northbound alarm SNMP interface
complies with. It also describes the functions supported by this interface when M2000 MIB is
loaded.
Compliant SNMP Versions
Currently, the M2000 northbound alarm SNMP interface complies with SNMPv1, SNMPv2c,and SNMPv3. For details, see Table 1-1.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
5
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
15/86
Table 1-1Compliant SNMP versions
SNMP Version Compliance
SNMPv1 l SNMPv1 operations
SNMP Get
SNMP Get Next
SNMP Set
l SNMPv1Trap
l SNMPv1 community-based security model
SNMPv2c l SNMPv2c operations
SNMP Get
SNMP Get Next
SNMP Get Bulk
SNMP Set
l SNMPv2cTrap
l SNMPv2c community-based security model
SNMPv3 l SNMPv3 operations
SNMP Get
SNMP Get Next
SNMP Get Bulk
SNMP Set
l SNMPv3 Trap
l SNMPv3 user-based security model
CAUTION
SNMPv3 and the M2000 support three security levels: NoAuth and NoPriv, Auth and NoPriv,
Auth and Priv. Auth Protocol supports only MD5 and SHA.
Interface Functions
Table 1-2lists the seven basic operations that the M2000 northbound alarm SNMP interface
provides to the NMS.
Table 1-2Overview of the basic operations
Basic Operation Interface Function
Report alarms in real
time
The NMS receives real-time alarm traps through this interface.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
6
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
16/86
Basic Operation Interface Function
Query active alarms The NMS queries active alarms through this interface.
Acknowledge active
alarms
The NMS acknowledges active alarms through this interface.
Unacknowledge
active alarms
The NMS unacknowledges active alarms through this interface.
Clear active alarms The NMS clears active alarms through this interface.
Report heartbeat
traps
The NMS receives heartbeat traps through this interface.
Change the heartbeat
period
The M2000 northbound alarm SNMP interface allows the NMS to
change the heartbeat period in real time. The MIB provides a leaf
node about the heartbeat period to allow the NMS obtains and
changes the value of the heartbeat period in real time.
For details about the basic operations, seeTable 1-3.
Table 1-3Description of the basic operations
Basic Operation Description
Report alarms in real
time
After the real-time alarm report function is enabled in the
configuration file, the M2000 sends real-time alarm traps to the NMS.
This function allows the NMS to learn about alarms generated on NEs
in real time.
The real-time alarms include: fault alarms, cleared alarms, event
alarms, acknowledged alarms, unacknowledged alarms, and changed
alarms.
Do as follows to enable the real-time alarm report function:
1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.
l Set the criteria for filtering alarms by severity.
2. The NMS receives real-time alarms.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
7
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
17/86
Basic Operation Description
Query active alarms The active alarm query function allows the NMS to query active
alarms of NEs at any time.
Do as follows to enable the active alarm query function:1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.
l Set the criteria for filtering alarms by alarm severity.
2. Alarm query is triggered after the NMS sets the MIB node
iMAPNorthboundAlarmQuery to 1.
3. The NMS receives active alarms.
The NMS is not allowed to start a new query before the currentquery is complete. The NMS can set iMAPNorthboundAlarm-
Queryto 0 to stop the current query while receiving active alarms.
Acknowledge active
alarms
The active alarm acknowledgment function allows the NMS to
acknowledge active alarms of NEs at any time.
Do as follows to enable the active alarm acknowledgment function:
1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.l Set the criteria for filtering alarms by alarm severity.
2. Alarm acknowledgment is triggered after the NMS sets the MIB
node iMAPNorthboundAlarmAcknowledge as the alarm serial
number. Multiple alarm serial numbers are separated by commas
(,).
3. The NMS receives and acknowledges alarms.
l If all alarms are acknowledged successfully, a null value is
returned.
l If there are any invalid alarm serial numbers or alarm serial
numbers that are not acknowledged, they are returned to theNMS.
The NMS is not allowed to start a new acknowledgment before the
current acknowledgment is complete.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
8
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
18/86
Basic Operation Description
Unacknowledge
active alarms
The active alarm unacknowledgment function allows the NMS to
unacknowledge active alarms of NEs at any time.
Do as follows to enable the active alarm unacknowledgment function:1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.
l Set the criteria for filtering alarms by alarm severity.
2. Alarm unacknowledgment is triggered after the NMS sets the MIB
node iMAPNorthboundAlarmUnAcknowledge as the alarm
serial number. Multiple alarm serial numbers are separated by
commas (,).
3. The NMS receives and unacknowledges alarms.
l If all alarms are unacknowledged successfully, a null value is
returned.
l If there are any invalid alarm serial numbers or alarm serial
numbers that are not unacknowledged, they are returned to the
NMS.
The NMS is not allowed to start a new unacknowledgment before the
current unacknowledgment is complete.
Clear active alarms The active alarm clearance function allows the NMS to clear active
alarms of NEs at any time.
Do as follows to enable the active alarm clearance function:
1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.
l Set the criteria for filtering alarms by alarm severity.
2. Alarm clearance is triggered after the NMS sets the MIB node
iMAPNorthboundAlarmClearas the alarm serial number.
Multiple alarm serial numbers are separated by commas (,).
3. The NMS receives and clears alarms.
l If all alarms are cleared successfully, a null value is returned.
l If there are any invalid alarm serial numbers or alarm serial
numbers that are not cleared, they are returned to the NMS.
The NMS is not allowed to start a new clearance before the current
clearance is complete.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
9
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
19/86
Basic Operation Description
Report heartbeat
traps
After configuring the IP address and port for receiving traps, the NMS
periodically receives heartbeat traps from the M2000 within the preset
heartbeat period. The heartbeat traps help the NMS learn about its
connection status with the M2000. If the NMS does not receive
heartbeat traps from the M2000 within the preset heartbeat period, its
connection with the M2000 is abnormal. If the NMS receives
heartbeat traps from the M2000 within the preset heartbeat period, its
connection with the M2000 is normal.
Do as follows to enable the heartbeat trap report function:
1. Modify the configuration file as M2000 administrator. For details,
see 1.6 Configuration File of the Northbound Alarm SNMP
Interface.
l Configure the IP address and port from which the NMS
receives traps.l Set the heartbeat period to a value that is greater than 0. In the
configuration file, the default heartbeat period is 60 seconds.
2. The NMS receives heartbeat traps.
Change the heartbeat
period
Do as follows to change the heartbeat period:
l Description
Gain access to and change the leaf node of the heartbeat period.
l OID
OID= 1.3.6.1.4.1.2011.2.15.2.1.3.1.1
l fullpathfullpath= .iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).iMAP(2011).products(2).iMAPNetManagement
(15).iMAPNorthbound(2).iMAPNorthboundCommon
(1).iMAPNorthboundCommuLinkMonitor(3).iMAPNorth-
boundHeartbeatSvc(1).iMAPNorthboundHeartbeatSvcReportIn-
terval(1)
l Field List
For details about the field list, see Table 1-4.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
10
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
20/86
Table 1-4iMAPNorthboundHeartbeatSvcReportInterval field list
MIBVariable
Description
DataType
Index OrNot
AccessMethod
ValueRange
Restriction
iMAPNorthboundHe
artbeatSvc
ReportInte
rval
Gainaccess to
and
change the
leaf node
of the
heartbeat
period.
INTEGER No RW 3 - 3600 current
1.4.2 Functions Supported by HW MIBWhen loaded with the HW MIB, the SNMP NBI supports automatic alarm reporting,
synchronizing, clearing, acknowledging, and unacknowledging. Alarm synchronizing is to
query active alarms.
M2000
At the M2000 side, the primary functions are:
l Reporting alarms
l Reporting heartbeat
NOTE
To enable this function, set third-party NMS parameters only on the M2000 when deploying the SNMP
NBI instead of configuring the NMS. Alarm information will be received at the preset port of the NMS
server.
After receiving alarms from the equipment or the M2000, the SNMP NBI reports these alarms
to the NMS by means of standard SNMP trap messages.
The SNMP NBI periodically reports heartbeat to the NMS. Based on the heartbeat, the NMS
determines whether the connection with the SNMP NBI is proper.
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
Reports alarms from NEs or the M2000.
Reporting
heartbeat
Reports heartbeat and sets the heartbeat period.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
11
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
21/86
NMS
At the NMS side, the primary functions are:
l Synchronizing alarms (querying current alarms)
l Changing filter criteria in real time
l Acknowledging/Unacknowledging alarms
l Clearing alarms
NOTE
Ensure that the NMS is connected to the SNMP NBI properly before the query function is enabled.
Function Description
Synchronizing
alarms (querying
current alarms)
Queries current alarms (uncleared alarms) on the M2000 in the Set
operation.
To query current alarms on the M2000, the NMS issues the query
begin command (value: 1) in the Set operation. After receiving the
command, the SNMP agent queries current alarms from the M2000
and reports the result to the NMS. If there are too many alarms and
the query needs to be stopped, the NMS 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 NMS.
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 HW 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
Acknowledges or unacknowledges current alarms on the M2000
based on alarm serial numbers (SNs).
Clearing alarms Clears alarms on the M2000 based on alarm SNs.
1.5 Security Mechanism of Northbound Alarm SNMPInterface
The security mechanism used by the northbound alarm SNMP interface is also the security
mechanism of the SNMP protocol. Any access to the northbound alarm SNMP interface must
be authenticated by the security mechanism of the specific SNMP version (SNMPv1, SNMPv2c,
and SNMPv3).
Figure 1-3shows that SNMPv1 and SNMPv2c use the community-based security mechanism,
while SNMPv3 uses the user-based security mechanism.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
12
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
22/86
Figure 1-3Security mechanism of northbound alarm SNMP interface
SNMPv1 and SNMPv2
The security mechanism of SNMPv1 and SNMPv2c is community-based: The NMS
authenticates NEs based on the community name list and the agent does not check the validity
of the community name. SNMP packets are transferred without encryption. Therefore,
authentication security and confidentiality are not well guaranteed.
l Before the Get, Get Next, or Set operation, the NMS must know the read and write
community names configured for the agent.
l For trap and inform packets, the community name is the read community name configured
for the agent.
NOTE
SNMPv1 does not support the inform mode.
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 Data integrity check
The data cannot be modified in an unauthorized manner. Any changes in the data sequence
are limited to the allowed extent.
l Data origin authentication
SNMPv3 authenticates users from whom received packets are sent rather than applications
that generate these packets.
l Data confidentiality check
When the NMS or agent receives a packet, it checks when the packet was generated. If theinterval between the creation time and the system time exceeds the preset time range, this
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
13
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
23/86
packet will be discarded. This check prevents packets from being maliciously modified and
malicious packets from being received.
In access control, the NMS performs security checks on managed objects (MOs) based on
SNMPv3.
Security Level
Table 1-5shows security levels supported by the SNMP versions.
Table 1-5
Version Security LevelAuthentication
DataEncryption
Description
v1
Without
authenticationand encryption Community None
Uses only
community
names foraccess
authentication.
v2c
Without
authentication
and encryption
Community None
Uses only
community
names for
access
authentication.
v3
Without
authentication
and encryption
User name None
Uses only user
names for
access
authentication.
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 fordata encryption.
NOTE
The following rules are applicable to SNMPv3:
l You can set a different user name, authentication password, and encryption password from others.
l You can select any of the listed security levels, authentication algorithms, and encryption algorithms.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
24/86
1.6 Configuration File of the Northbound Alarm SNMPInterface
This section describes the configuration file of the northbound alarm SNMP interface.
Overview
To configure the northbound alarm SNMP interface, modify the following items in the
configuration file:
l SNMPv3 protocol
l NMS information
l Heartbeat period
l Reported fields
l Alarm transfer mode
l Report type of the Csn field
l FDN adapter
l Maintenance-mode Alarm Report
NOTE
l The configuration file is stored in /opt/oss/server/nbi/snmp/conf/snmpagent.xml.
l After modifying the configuration file, run the following command to restart the northbound alarm
SNMPinterface service for the configuration to take effect:
svc_adm -cmd restartsvcSnmpAgent
l You can modify the parameters of the northbound configuration file either by running commands or
by using the OSMU. For details about the operations performed on the OSMU, see 5.8 How to Set
Parameters in a Northbound Configuration File.
Table 1-6describes the parameters in the snmpagent.xmlfile.
Table 1-6Parameters in the snmpagent.xmlfile
Parameter
Path ofConfigurationItem
Description DefaultValue
Delimiter snmpagent->MIB1->Delimiter
Delimiter between character elements inthe ObjectInstanceand ResourceIDs
fields.
Space
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
15
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
25/86
Parameter
Path ofConfigurationItem
Description DefaultValue
ResIDFor
mat
snmpagent->MIB1-
>ResIDFormat
Specifies whether to display the resource
information in FDN format.
NOTEThis parameter applies only to HW MIB and
can be set to:
l 0: octet format. The ResourceIDsand
ObjectInstancefields are displayed in
octet format. For example,
[3145731.-1.22.8.912.1.-1.-1].
l 1: FDN format. The ResourceIDsand
ObjectInstancefields are displayed in
FDN format. For example,
[NE=312323,FR=1,S=1,CP=1,PP=4|1|
2|].
If a northbound interface compatibility ID
has been set, the M2000 will adjust the EMS
ID and FDN format based on the setting. For
example, the EMS ID is changed from OSS
to OMC and the FDN is changed from dotted
format to name-value format. For details, see
5.7 How to Set Northbound Interface
Compatibility.
0
SupportX
733Alarm
snmpagent->MIB1-
>SupportX733Alarm
Specifies whether the X733 standard is
supported. This parameter can be set to:
l 0: The X733 standard is supported.
l 1: The X733 standard is not
supported.
0
KeepAliv
eVBOID
snmpagent->MIB1-
>KeepAliveVBOID
Specifies the type of heartbeat VB OIDs.
This parameter is set to
1.3.6.1.4.1.2011.2.15.1by default. It can
also be set to
1.3.6.1.4.1.2011.2.15.1.7.2.1.
1.3.6.1.4.1.
2011.2.15.1
NotifyOI
D
snmpagent->MIB1-
>NotifyOID
Specifies the trap OIDs for alarms. This
parameter can be set to:
l
0: All alarms use the same trap OID.l 1: Alarms of different severities use
different trap OIDs.
0
T2000Sup
port
snmpagent->MIB1-
>T2000Support
Specifies whether to enable T2000 fields
such as ObjectInstance,
ProbableCause, EventDetail,
ProbableRepair, and EventName.
0
CsnType snmpagent->MIB2-
>CsnType
Specifies the format of the AlarmCSN
field. This parameter can be set to:
l 0: character string.
l 1: integer.
0
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
16
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
26/86
Parameter
Path ofConfigurationItem
Description DefaultValue
SupportC
M
snmpagent->MIB2-
>SupportCM
Specifies whether to enable the
configuration of CMC ENUM. This
parameter can be set to:
l 0: disable the configuration of CMC
ENUM.
l 1: enable the configuration of CMC
ENUM.
0
SNMPv3 Protocol
M2000The M2000 supports SNMPv1, SNMPv2c, and SNMPv3. By default, it supports
SNMPv3.
Do as follows to configure the SNMP protocol:
Modify Level, AuthProtocol, and PrivProtocolin snmpagent->v3trap.
NOTE
Leveland AuthProtocolapply only to SNMPv3.
Table 1-7describes the parameters for configuring the SNMPv3 protocol.
Table 1-7Configuring the SNMPv3 protocolParameter Path of
ConfigurationItem
Description Default Value
Level snmpagent-
>v3trap->Level
Sets the security
level:
l 1: unauthorized
and unencrypted
l 2: authorized but
unencrypted
l 3: authorized andencrypted
3
AuthProtocol snmpagent-
>v3trap-
>AuthProtocol
Sets the
authorization
protocol:
l 1: MD5 protocol
l 2: SHA protocol
1
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
17
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
27/86
Parameter Path ofConfigurationItem
Description Default Value
PrivProtocol snmpagent-
>v3trap-
>PrivProtocol
Sets the encryption
protocol of
SNMPv3:
l 1: DES
encryption
protocol
l 2: AES
encryption
protocol
1
NOTE
The M2000 uses 127.0.0.1 as the default IP address for running the SNMP service. If the NMS requires to
use a specific IP address, perform the following operations to configure the SNMP service information.
For example, to avoid possible impact of M2000 active/standby switchovers on northbound
interconnection, use the logical IP address of an M2000 HA system to configure the SNMP service when
interconnecting the NMS with the HA system.
(Optional) Do as follows to configure the SNMP service information:
Modify Agent_IPin snmpagent->common.
Table 1-8describes the parameters for configuring the SNMP service information:
Table 1-8Configuring the SNMP service information
Parameter
Path of Configuration Item Description DefaultValue
Agen
t_IP
snmpagent->common->Agent_IP IP address for running the SNMP
service.
l When the operating system has
only one IP address, the default
value is 127.0.0.1. The SNMPservice runs on the IP address of
the operating system.
l When the operating system has
two IP addresses, set this
parameter to either of the IP
addresses. Otherwise, the NMS
cannot determine the IP address
where the SNMP service runs.
127.0
.0.1
Agen
t_Por
t
snmpagent->common-
>Agent_Port
Port for running the SNMP service.
Generally, this parameter does not
need to be modified.
4700
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
18
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
28/86
NMS Information
The M2000 can concurrently interconnect with four NMSs.
Set the following configuration items related to each NMS:
l Security user name in v3
l Community name in v1 or v2
l Authentication password in v3 (authenticated but unencrypted)
l Encrypted password in v3
l IP address for receiving traps
l Port for receiving traps
l Alarm severity
l Alarm category
Table 1-9describes the parameters for configuring the NMS information and the path of the
parameters in the configuration file.
NOTE
The configuration file displays community names and passwords in ciphertext. Therefore, before setting
a community name or password, run the following commands to enable the GenerateNBPassscript to
encrypt the community name or password and then set the corresponding configuration item to the
encrypted community name or password. Send the plaintext community names and passwords to the NMS
OM personnel and explain them how to use the GenerateNBPassscript.
The community names and passwords must meet the following requirements:
l The character string contains a minimum of 8 characters and a maximum of 30 characters.
l The character string contains at least three of the following four character types:
l Lowercase letters
l Uppercase letters
l Arabic numerals
l Underscores (_)
The default installation directory of the M2000 server is /opt/oss/server.
1. cd/opt/oss/server
2. . ./svc_profile.sh
3. cd/opt/oss/server/nbi/snmp/bin
4. GenerateNBPass -ecommunity name or password to be encrypted
The system displays information similar to the following. In which, information after Encrypt
password result: is the encrypted community name or password:
Encrypt password result: VnYJqua5dagADOng43KJdgy
Table 1-9Configuring the NMS information
Parameter Path of Configuration Item Description
IPAddress snmpagent->nmsinfo->IPAddress
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
IP address or host name for the
NMS to receive traps. You can set
this parameter to an IP address or
a host name.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
19
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
29/86
Parameter Path of Configuration Item Description
Port snmpagent->nmsinfo->Port
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Port for the NMS to receive traps.
The parameters IPAddressand
Portspecify the NMS server that
receives real-time alarm traps,
active alarm query traps, and
heartbeat traps.
Version snmpagent->nmsinfo->Version
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
SNMP version.
l 1: SNMPv1
l 2: SNMPv2
l 3: SNMPv3
Read snmpagent ->nmsinfo-
>community1->Read
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Any readentity specified in the
SAC memory for connecting to
the SNMP agent.
Run the GenerateNBPass -e
command to encrypt the entity
before use.
Write snmpagent ->nmsinfo-
>community1->Write
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Any writeentity specified in the
SAC memory for setting the MIB
field.
Run the GenerateNBPass -e
command to encrypt the entity
before use.
V3User snmpagent->nmsinfo->V3User
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
If the parameter Versionis set to
3, this parameter specifies the
security user name of SNMPv3.
AuthPassword snmpagent->nmsinfo-
>AuthPassword
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Authentication password of an
NMS user. This parameter applies
when SNMPv3 authentication is
enabled.
You need to encrypt the password
and set this parameter to the
encrypted password according to
the note before Table 1-9.
PrivPassword snmpagent->nmsinfo-
>PrivPassword
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
If the version value is set to 3 and
the security level is set to 3, you
must set the encryption policy for
the password.
You need to encrypt the password
and set this parameter to the
encrypted password according to
the note before Table 1-9.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
20
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
30/86
Parameter Path of Configuration Item Description
Critical snmpagent->nmsinfo->alarmlevel-
>Critical
You can set nmsinfoto nmsinfo1,nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out critical
alarms reported to the NMS.
l 0: Critical alarms are filteredout and not reported to the
NMS.
l 1: Critical alarms are not
filtered out and reported to the
NMS.
Major snmpagent->nmsinfo->alarmlevel-
>Major
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out major alarms
reported to the NMS.
l 0: Major alarms are filtered out
and not reported to the NMS.
l1: Major alarms are not filteredout and reported to the NMS.
Minor snmpagent->nmsinfo->alarmlevel-
>Minor
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out minor alarms
reported to the NMS.
l 0: Minor alarms are filtered out
and not reported to the NMS.
l 1: Minor alarms are not filtered
out and reported to the NMS.
Warning snmpagent->nmsinfo->alarmlevel-
>Warning
You can set nmsinfoto nmsinfo1,nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out warning
alarms reported to the NMS.
l 0: Warning alarms are filteredout and not reported to the
NMS.
l 1: Warning alarms are not
filtered out and reported to the
NMS.
Event snmpagent->nmsinfo->category-
>Event
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out events
reported to the NMS.
l 0: Events are filtered out and
not reported to the NMS.
l 1: Events are not filtered outand reported to the NMS.
Fault snmpagent->nmsinfo->category-
>Fault
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out fault alarms
reported to the NMS.
l 0: Fault alarms are filtered out
and not reported to the NMS.
l 1: Fault alarms are not filtered
out and reported to the NMS.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
21
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
31/86
Parameter Path of Configuration Item Description
Recover snmpagent->nmsinfo->category-
>Recover
You can set nmsinfoto nmsinfo1,nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out cleared
alarms reported to the NMS.
l 0: Cleared alarms are filteredout and not reported to the
NMS.
l 1: Cleared alarms are not
filtered out and reported to the
NMS.
Acknowledge snmpagent->nmsinfo->category-
>Acknowledge
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out
acknowledged alarms reported to
the NMS.
l 0: Acknowledged alarms are
filtered out and not reported to
the NMS.
l 1: Acknowledged alarms are
not filtered out and reported to
the NMS.
Unacknowled
ge
snmpagent->nmsinfo->category-
>Unacknowledge
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out
unacknowledged alarms reported
to the NMS.
l 0: Unacknowledged alarms
alarms are filtered out and not
reported to the NMS.
l 1: Unacknowledged alarmsare not filtered out and
reported to the NMS.
Change snmpagent->nmsinfo->category-
>Change
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out changed
alarms reported to the NMS.
l 0: Changed alarms are filtered
out and not reported to the
NMS.
l 1: Changed alarms are not
filtered out and reported to the
NMS.
NeTypeFilter snmpagent->nmsinfo-
>NeTypeFilter
You can set nmsinfoto nmsinfo1,
nmsinfo2, nmsinfo3, or nmsinfo4.
Parameter for filtering out alarms
by device type. By default, this
parameter is not set and therefore
alarms generated on all NEs are
reported. To filter out alarms of
multiple device types, separate the
device types with commas (,)
when setting this parameter.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
22
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
32/86
Parameter Path of Configuration Item Description
MaintenanceA
larmFilter
snmpagent->nmsinfo-
>MaintenanceAlarmFilter
You can set nmsinfoto nmsinfo1,nmsinfo2, nmsinfo3, or nmsinfo4.
Whether to filter out maintenance
alarms reported to the NMS.
l 0: Maintenance alarms arefiltered out and not reported to
the NMS.
l 1: Maintenance alarms are not
filtered out and reported to the
NMS.
To configure the NMS, you need to open the configuration file, delete information similar to
and , and manually configure the related
configuration items.
1
Heartbeat Period
Table 1-10describes the parameters for configuring the heartbeat period and the path of the
parameters in the configuration file.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
23
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
33/86
Table 1-10Configuring the heartbeat period
Parameter Path ofConfigurationItem
Description Default Value
Interval snmpagent-
>heartbeat-
>Interval
Period for reporting
heartbeat traps. The
value range is 3 and
3600 seconds. If this
parameter is set to 0
or to a value that is
not within the
specified range, the
default value 60
seconds is used.
60
Enable snmpagent->heartbeat-
>Enable
Whether to enableheartbeat trap
reporting. When this
parameter is set to 0,
heartbeat trap
reporting is disabled.
When this parameter
is set to a non-0
value, heartbeat trap
reporting is enabled.
1
Lable snmpagent-
>heartbeat->Lable
Identifier of
heartbeat trapreporting.
SNMP Agent
Reported Fields
The M2000 provides the real-time alarm trap service to the NMS. If the NMS subscribes to this
service, the M2000 sends real-time alarms to the NMS in the form of traps. For details about
how to subscribe to this service, see 2.1 Real-Time Alarm Trap.
To configure real-time alarm traps, set parameters under snmpagent->MIB2->Mib in the
configuration file.
l Set VB1to Csn.
l Set VB2to Category.
l Set VB3to OccurTime.
l Set VB4to MOName.
l Set VB5to ProductID.
l Set VB6to NEType.
l Set VB7to NEDevId.
l Set VB8to DevCsn.
l Set VB9to ID.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
24
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
34/86
l Set VB10to Type.
l Set VB11to Level.
l Set VB12to Restore.
l Set VB13to Confirm.
l Set VB14to AckTime.
l Set VB15to RestoreTime.
l Set VB16to Operator.
l Set VB17to ExtendInfo.
l Set VB18to Probablecause.
l Set VB19to Proposedrepairactions.
l Set VB20to SpecificProblems .
l Set VB21to ClearOperator.
l Set VB22to ObjectInstanceType .
l Set VB23to ClearCategory.
l Set VB24to ClearType.
l Set VB25to ServiceAffectFlag.
l Set VB26to AdditionalInfo.
You can set ExtendProductItemXto an integer or a character string, where Xcan be set to 1,
2, 3, ..15. For details, see 2.3 Start Trap for Querying Active Alarms.
Table 1-11lists all the reported alarm fields that can be configured and the path of the related
parameters in the configuration file.
Table 1-11Configurable reported alarm fields
VB Name Path of Configuration Item Description
Csn snmpagent->MIB2->Mib->Csn Network serial number of an
alarm. This field is used as a
keyword to match the fault alarm,
cleared alarm, event alarm,
acknowledged alarm,
unacknowledged alarm, or
changed alarm.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
25
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
35/86
VB Name Path of Configuration Item Description
Category snmpagent->MIB2->Mib-
>Category
Category of an alarm. You to set
filter criteria based on the
following alarm categories:
1. Fault alarm
2. Cleared alarm
3. Event alarm
4. Acknowledged alarm
5. Unacknowledged alarm
6. Unknown alarm
7. Unknown alarm
8. Unknown alarm
9. Changed alarmOccurTime snmpagent->MIB2->Mib-
>OccurTime
Time when an alarm is generated
on a device.
MOName snmpagent->MIB2->Mib-
>MOName
Name of a device.
This field identifies the name of
the device where an alarm is
generated.
ProductID snmpagent->MIB2->Mib-
>ProductID
ID of a product.
This field identifies the product
series of the device where an
alarm is generated.
NEType snmpagent->MIB2->Mib-
>NEType
Type of a device.
This field identifies the type of
the device where an alarm is
generated.
NEDevID snmpagent->MIB2->Mib-
>NEDevID
ID of a device.
In the M2000 system, a device ID
is unique. This field identifies the
ID of the device where an alarm
is generated.
DevCsn snmpagent->MIB2->Mib-
>DevCsn
Unique serial number of a faulty
device.
This field is used for counting
faulty devices.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
26
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
36/86
VB Name Path of Configuration Item Description
ID snmpagent->MIB2->Mib->ID ID of an alarm category.
You can define multiple alarm
categories for a device type.After you define alarm categories
for a device type, a device of the
device type can only report
alarms of the predefined alarm
categories.
Type snmpagent->MIB2->Mib-
>Type
Type of an alarm. The alarm types
are as follows:
1. Power system
2. Environmental system
3. Signaling system
4. Trunk system
5. Hardware system
6. Software system
7. Running system
8. Communication system
9. QoS
10.Processing error
11.Internal
12.Integrity violation
13.Operational violation
14.Physical violation
15.Security service or
mechanism violation
16.Time domain violation
Level snmpagent->MIB2->Mib-
>Level
Severity of an alarm.
This field can be set to:
l 1: Critical
l 2: Major
l 3: Minor
l 4: Warning
l 5: Indeterminate
l 6: Cleared
Restore snmpagent->MIB2->Mib-
>Restore
Clearance identifier.
This field can be set to:
l 1: Cleared
l 2: Uncleared
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
27
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
37/86
VB Name Path of Configuration Item Description
Confirm snmpagent->MIB2->Mib-
>Confirm
Acknowledgment identifier.
This field can be set to:
l 1: Acknowledged
l 2: Unacknowledged
AckTime snmpagent->MIB2->Mib-
>AckTime
Acknowledgment time.
This field identifies the time
when an alarm is acknowledged.
RestoreTime snmpagent->MIB2->Mib-
>RestoreTime
Clearance time.
This field identifies the time
when an alarm is cleared.
Operator snmpagent->MIB2->Mib-
>Operator
Acknowledgment operator.
This field identifies the operator
who acknowledges an alarm.
ExtendInfo snmpagent->MIB2->Mib-
>ExtendInfo
Extended information.
This field contains the location
information about an alarm.
Probablecause snmpagent->MIB2->Mib-
>Probablecause
Alarm cause.
This field identifies the cause of
an alarm.
Proposedrepairac-tions snmpagent->MIB2->Mib->Proposedrepairactions Alarm handling suggestion.This field provides the suggestion
for handling an alarm.
Specificproblems snmpagent->MIB2->Mib-
>Specificproblems
Detailed alarm cause.
ClearOperator snmpagent->MIB2->Mib-
>ClearOperator
Operator who clears an alarm.
ObjectInstance-
Type
snmpagent->MIB2->Mib-
>ObjectInstanceType
Type of an alarm object instance.
ClearCategory snmpagent->MIB2->Mib->ClearCategory
Alarm clearance category.l Automatically Detected
Automatically Cleared
(ADAC)
l Automatically Detected
Manually Cleared (ADMC)
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
28
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
38/86
VB Name Path of Configuration Item Description
ClearType snmpagent->MIB2->Mib-
>ClearType
Alarm clearance type.
l Normal Clear
l Restore Clear
l Manual Clear
l Configure Clear
l Co-relation Clear
ServiceAffectFlag snmpagent->MIB2->Mib-
>ServiceAffectFlag
Identifies whether a service is
affected.
AdditionalInfo snmpagent->MIB2->Mib-
>AdditionalInfo
Additional information about an
alarm.
ExtendProductI-
tem1
snmpagent->MIB2->Mib-
>ExtendProductItem1
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem2
snmpagent->MIB2->Mib-
>ExtendProductItem2
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem3
snmpagent->MIB2->Mib-
>ExtendProductItem3
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem4
snmpagent->MIB2->Mib-
>ExtendProductItem4
Extended product information
based on Huawei alarmspecifications.
ExtendProductI-
tem5
snmpagent->MIB2->Mib-
>ExtendProductItem5
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem6
snmpagent->MIB2->Mib-
>ExtendProductItem6
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem7
snmpagent->MIB2->Mib-
>ExtendProductItem7
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem8
snmpagent->MIB2->Mib-
>ExtendProductItem8
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem9
snmpagent->MIB2->Mib-
>ExtendProductItem9
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem10
snmpagent->MIB2->Mib-
>ExtendProductItem10
Extended product information
based on Huawei alarm
specifications.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
29
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
39/86
VB Name Path of Configuration Item Description
ExtendProductI-
tem11
snmpagent->MIB2->Mib-
>ExtendProductItem11
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem12
snmpagent->MIB2->Mib-
>ExtendProductItem12
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem13
snmpagent->MIB2->Mib-
>ExtendProductItem13
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem14
snmpagent->MIB2->Mib-
>ExtendProductItem14
Extended product information
based on Huawei alarm
specifications.
ExtendProductI-
tem15
snmpagent->MIB2->Mib-
>ExtendProductItem15
Extended product information
based on Huawei alarm
specifications.
Alarm Transfer Mode
Table 1-12describes the parameters for transferring alarms and the path of the parameters in
the configuration file.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
30
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
40/86
Table 1-12Configuring the alarm transfer mode
Parameter Path of Configuration Item Description DefaultValue
SupportedMIB
snmpagent->common->SupportedMIB
Specifies the type of theMIB to be loaded.
l MIB1 indicates
message MIB. OIDs
corresponding to
HW-
IMAPV1NORTHB
OUND-TRAP-
MIB.mibare
supported.
l MIB2 indicates
distributed MIB.OIDs corresponding
to
IMAP_NORTHBO
UND_MIB-V1.mib
and
IMAP_NORTHBO
UND_MIB-V2.mib
are supported.
MIB2
TrapSendI
P
snmpagent->common-
>TrapSendIP
Source IP address from
which traps and informs
are sent. If an invalidvalue is set, the system
IP address is used.
127.0.0.1
TrapSendP
ort
snmpagent->common-
>TrapSendPort
Source port over which
traps and informs are
sent. If an invalid value
is set, the system obtains
a port randomly.
6666
TrapSendIn
terval
snmpagent->common-
>TrapSendInterval
Interval for sending traps
to the NMS. This
parameter is
inapplicable to informs.The value range is 1 to
1000 microseconds.
0
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
31
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
41/86
Parameter Path of Configuration Item Description DefaultValue
TimeForma
t
snmpagent->common-
>TimeFormat
Time format of the VB
field that identifies alarm
time. The time format
can be set to:
l 0: UTC time
l 1: Local time without
time zone
l 2: Local time with
time zone
l 3: UTC time, which
has a different time
format compared
with the UTC timewhen this parameter
is set to 0
l 4: Local time
1
TimeType snmpagent->common-
>TimeType
Type of alarm reporting
time, which can be set to
1 or 2.
l 0: UTC time
l 1: EMS time
l 2: NE time
2
StringSize snmpagent->common-
>StringSize
Maximum length of a
character string that can
be restored in the VB.
4096
ActiveAlar
m
snmpagent->common-
>ActiveAlarm
Specifies to query
current alarms or active
alarms. When it is set to
0, current alarms are
queried. When it is set to
a non-0 value, active
alarms are queried.
1
TrapCodin
g
snmpagent->common-
>TrapCoding
Character set encoding
of alarm traps.
l UTF-8
l ISO-8859-1
l GBK
ISO-8859-1
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
32
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
42/86
Parameter Path of Configuration Item Description DefaultValue
SupportRo
otAlarm
snmpagent->common-
>SupportRootAlarm
Specifies whether to
support root alarms. This
root alarm analysis
function is valid only
after transport or access
E2E function
components are
installed.
l When it is set to 0,
root alarms are not
supported and all
alarms are reported
and queried.
l When it is set to 1,
root alarms are
supported and alarms
except correlative
alarms are reported
and queried.
0
PDUTrace snmpagent->common->
PDUTrace
Specifies whether to
print PDU trace in logs.
l When it is set to 0,
PDU trace is not
printed in logs.l When it is set to 1,
PDU trace is printed
in logs.
0
Table 1-13describes the inform parameters.
Table 1-13Configuring the inform parameters
Parameter Path of Configuration Item Description Default
Value
Enable snmpagent->inform->Enable Specifies whether to report
alarms in the form of
informs. When it is set to 1,
alarms are reported in the
form of informs. When it is
set to a non-1 value, alarms
are not reported in the form
of informs.
0
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
33
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
43/86
Parameter Path of Configuration Item Description DefaultValue
Timeout snmpagent->inform-
>Timeout
Parameter specified by the
SNMP inform protocol,
which specifies the timeout
period for sending an
inform message. The
default value is five
seconds. The minimum
value is one second.
5
Retries snmpagent->inform->Retries Parameter specified by the
SNMP inform protocol,
which specifies the number
of attempts for resending an
inform message. The
minimum value is 0.
3
CacheSize snmpagent->inform-
>CacheSize
Specifies the size of the
cache for real-time alarms.
The maximum value is
50000and the minimum
value is 0. An independent
cache is assigned to each
NMS user.
10000
Report Type of the Csn Field
Table 1-14describes the parameters for configuring the report type of the Csn field and the path
of the parameters in the configuration file.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
34
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
44/86
Table 1-14Configuring the report type of the Csn field
Parameter
Path of Configuration Item Description Default Value
CsnType
snmpagent->MIB2->CsnType Specifies thereport type of
the Csn field that
identifies alarm
serial numbers.
l When it is set
to 1, alarms
are reported
in the form of
integers.
l When it is set
to a non-1value, alarms
are reported
in the form of
character
strings.
0
FDN Adapter
NOTE
You do not need to configure the FDN adapter for the RTN.
In V200R012 and later releases, objects are uniquely identified by distinguished names (DNs)
instead of by full distinguished names (FDNs). DNs are represented in the format of "xxx = yyy"
and FDNs are represented in the format of dot-decimal notation. In scenarios where the
M2000 is upgraded to V200R012 or a later release, you need to enable the FDN adapter to adapt
and switch DNs back to FDNs for reporting the NEDevID field.
Table 1-15describes the path of the parameters for configuring the FDN adapter in the
configuration file.
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
35
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
45/86
Table 1-15Configuring the FDN adapter
Parameter
Path of Configuration Item Description Default Value
FDNAdapter
snmpagent->MIB2->FDNAdapter Specifieswhether to
enable the
adaption from
DNs to FDNs.
This
configuration
item is
inapplicable to
the RTN.
l When it is set
to 0, the FDN
adapter is
disabled.
l When it is set
to a non-0
value, the
FDN adapter
is enabled.
0
Maintenance-mode Alarm Report
To enable the maintenance-mode alarm report function, perform the following steps:
1. Log in to the M2000 server as user ossuser.
2. Run the following command to enable the maintenance-mode alarm report function:
If this function is disabled, the NMS cannot obtain maintenance-mode alarms from any of
the northbound alarm interfaces.
SettingTool -cmd setparam -path/imap/ifms/specialAlarmStatus/enable -value true
3. Run the following commands to enable the maintenance-mode alarm report function over
the SNMP interface:
If this function is disabled, the NMS cannot obtain maintenance-mode alarms from thealarm SNMP interface.
SettingTool -cmd setparam -path/imap/ifms/specialAlarmStatus/nbenable -value true
NOTE
If either /imap/ifms/specialAlarmStatus/enableor /imap/ifms/specialAlarmStatus/nbenableis
set tofalse, the NMS cannot obtain maintenance-mode alarms from the alarm SNMP interface.
4. Run the following command to restart FaultService:
svc_adm -cmd restartsvc FaultService
5. Run the following command to verify that FaultService has been started:
svc_adm -cmd status | grep FaultService
If the system displays the following information, FaultService has been started:
M2000
Northbound Alarm SNMP Interface Developer Guide 1 Introduction to Northbound Alarm SNMP Interface
Issue 01 (2012-04-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
36
-
8/10/2019 M2000 Northbound Alarm SNMP Interface Developer Guide
46/86
FaultService [running ]
1.7 Mechanism for Forwarding Common Alarms
If the base stations of a multi-mode base station (MBTS) report common alarms simultaneouslyto the M2000, the repeatedly reported alarms that are then forwarded from the M2000 to the
NMS may affect NMS services. The M2000 northbound interface provides policies for
M2000 users to determine whether to forward common alarms that are reported by different BSs
to the NMS.
The base stations of an MBTS share some common resources such as power module and FAN
unit. When faults occur on common resources, the BSs report alarms to the M2000
simultaneously.
Common alarms are classified into the following types:
l MBTS-GSM common alarms
l MBTS-UMTS common alarms
l MBTS-LTE common alarms
l MBTS (GU)-GSM common alarms
l MBTS (GU)-UMTS common alarms
l MBTS (GL)-GSM common alarms
l MBTS (GL)-LTE common alarms
l MBTS (UL)-UMTS common alarms
l MBTS (UL)-LTE common alarms
lMBTS (GUL)-GSM common alarms
l MBTS (GUL)-UMTS common alarms
l MBTS (GUL)-LTE common alarms
l MBTS (WL)-LTE common alarms
l MBTS (WL)-WiMax common alarms
Users can modify the configuration items to determine whether to forward the corresponding
common alarms by running the SettingToolcommand. For details about how to set policies for
forwarding common alarms, see Table 1-16.
Following is an example of running the SettingToolcommand to forward MBTS (GU)-GSM
common alarms.
1. Run the following command to forward MBTS (GU)-GSM common alarms:
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ SettingTool -cmd modparam -path/imap/ifms/MBTS_Filter/
GU_GSM -valueyes
NOTE
Users can run the following command for not forwarding MBTS (GU)-GSM