HW-IMAPV2NORTHBOUND-TRAP-MIB

All MIBs › HW-IMAPV2NORTHBOUND-TRAP-MIB

Organization: HUAWEI

Last Updated: 2010-11-24

Category: Alarm and Event Management, Domain: Network Management, Vendor: Huawei

Description: Huawei MIB defining SNMP trap notifications for the iMAP v2 northbound interface, used for EMS-to-NMS alarm forwarding.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HW-IMAPV2NORTHBOUND-TRAP-MIB?

HW-IMAPV2NORTHBOUND-TRAP-MIB is a Huawei-proprietary SNMP module defining the trap/notification objects used by the iMAP v2 northbound interface, a mechanism for forwarding alarms from an Element Management System (EMS) up to a higher-level Network Management System (NMS). Rather than exposing polled configuration or performance tables, it is entirely dedicated to fault/alarm notification definitions carried northbound as SNMP traps. Operators use it exclusively for fault monitoring - receiving forwarded alarm traps that indicate a hardware or software problem detected at the EMS layer (such as equipment faults, threshold crossings, or state changes) surfaces through this MIB's trap structures for consumption by the NMS. It is inherently dependent on Huawei's iMAP EMS alarm framework and the underlying device MIBs whose native alarms it repackages for northbound delivery. It is typically deployed at the boundary between a Huawei EMS and a carrier's higher-tier NMS, where alarm interoperability across management layers is required, with the HW-IMAPV2NORTHBOUND-TRAP-MIB MIB defining the trap structures that make this interoperability possible.

IPNetwork Monitor allows you to monitor SNMP objects defined in HW-IMAPV2NORTHBOUND-TRAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Huawei EMS-managed network elements (via iMAP northbound interface)

Monitoring Examples

This module is a trap/notification definition MIB rather than a polled data MIB, so there are no data tables to sample; an NMS operator would instead configure the EMS to send these northbound traps and set up trap receivers to log and alert on each forwarded alarm, using the trap's embedded alarm identifiers to correlate back to the originating device fault. No object names were supplied in the sample set to ground a more specific example.

Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
huawei	1.3.6.1.4.1.2011			This MIB defines the managed objects that are used by the function interfaces of the SNMP Northbound Interface.
products	1.3.6.1.4.1.2011.2
hwNetManagement	1.3.6.1.4.1.2011.2.15
hwNmAgent	1.3.6.1.4.1.2011.2.15.1
hwNmFault	1.3.6.1.4.1.2011.2.15.1.3
OCT thirdNMSFaultFilter	1.3.6.1.4.1.2011.2.15.1.3.5	OCTET STRING	read-write	IP:Port:AlarmLevelFilter:AlarmCategoryFilter AlarmLevelFilter = xxxx (Critical, Major, Minor, Warning) (1 - filter, 0 - report) AlarmCategoryFilter = yyyyyy (Event, Fault, Recovery, Acknowledge, UnAcknowledge, Change) (1 - filter, 0 - report) Both AlarmLevelFilter and AlarmCategoryFilter are optional and both or any one can be set E.g.: 10.18.17.28:9999:0110:100000 Only events of major and minor severity will be send to the OSS [10.18.17.28:9999] and rest filtered. The format to specify only AlarmLevelFilter is: 10.18.17.28:9999:0110 The format to specify only AlarmCategoryFilter is: 10.18.17.28:9999::100000 Get attempt on this node will result in error.
OCT hwNmClearAlarms	1.3.6.1.4.1.2011.2.15.1.3.6	OCTET STRING	read-write	This provides the functionality of clearing alarms to third party NMS. The alarms can be cleared based on alarm serial number. Multiple serial numbers are separated by comma(,). Alarms serial number(s)are of type unsigned long and incompatible types are automatically considered as invalid serial number(s). Get attempt on this node will result in error. Output: Serial number(s) of alarms which could not be cleared. This also contains Alarm serial number(s) with incorrect syntax. If all alarms are successfully cleared then output is blank.
OCT hwNmAcknowledgeAlarms	1.3.6.1.4.1.2011.2.15.1.3.7	OCTET STRING	read-write	This provides the functionality of acknowledging alarms to third party NMS. The alarms can be acknowledged based on alarm serial number. Multiple serial numbers are separated by comma(,). Alarms serial number(s) are of type unsigned long and incompatible types are automatically considered as invalid serial number(s). Get attempt on this node will result in error. Output: Serial number(s) of alarms which could not be acknowledged. This also contains Alarm serial number(s) with incorrect syntax. If all alarms are successfully acknowledged then output is blank.
OCT hwNmUnAcknowledgeAlarms	1.3.6.1.4.1.2011.2.15.1.3.8	OCTET STRING	read-write	This provides the functionality of unacknowledging alarms to third party NMS. The alarms can be unacknowledged based on alarm serial number. Multiple serial numbers are separated by comma(,). Alarms serial number(s) are of type unsigned long and incompatible types are automatically considered as invalid serial number(s). Get attempt on this node will result in error. Output: Serial number(s) of alarms which could not be unacknowledged. This also contains Alarm serial number(s) with incorrect syntax. If all alarms are successfully unacknowledged then output is blank.
hwNmNorthboundEvent	1.3.6.1.4.1.2011.2.15.1.7
hwNmNorthboundEventInfo	1.3.6.1.4.1.2011.2.15.1.7.1
hwNmNorthboundEventTrap	1.3.6.1.4.1.2011.2.15.1.7.1.0			Event Traps
NTF hwNmNorthboundEventNotify	1.3.6.1.4.1.2011.2.15.1.7.1.0.1			Notification for real-time alarm.
NTF hwNmNorthboundEventNotifyCritical	1.3.6.1.4.1.2011.2.15.1.7.1.0.3			Notification for real-time alarm whose level is Critical.
NTF hwNmNorthboundEventNotifyMajor	1.3.6.1.4.1.2011.2.15.1.7.1.0.4			Notification for real-time alarm whose level is Major.
NTF hwNmNorthboundEventNotifyMinor	1.3.6.1.4.1.2011.2.15.1.7.1.0.5			Notification for real-time alarm whose level is Minor.
NTF hwNmNorthboundEventNotifyWarning	1.3.6.1.4.1.2011.2.15.1.7.1.0.6			Notification for real-time alarm whose level is Warning.
NTF hwNmNorthboundEventNotifyIndefinitely	1.3.6.1.4.1.2011.2.15.1.7.1.0.7			Notification for real-time alarm whose level is Indefinitely.
NTF hwNmNorthboundEventNotifyUnknownSeverity	1.3.6.1.4.1.2011.2.15.1.7.1.0.8			Notification for real-time alarm whose level is UnknownSeverity.
OCT hwNmNorthboundNEName	1.3.6.1.4.1.2011.2.15.1.7.1.1	OCTET STRING	read-only	The name of network element,string (255)
OCT hwNmNorthboundNEType	1.3.6.1.4.1.2011.2.15.1.7.1.2	OCTET STRING	read-only	Device type of element,string(64)
OCT hwNmNorthboundObjectInstance	1.3.6.1.4.1.2011.2.15.1.7.1.3	OCTET STRING	read-only	Instance of element,such as number of Rack, Frame, Slot, Subslot, Port and so on,string(255)
OCT hwNmNorthboundEventType	1.3.6.1.4.1.2011.2.15.1.7.1.4	OCTET STRING	read-only	Type of Event,string(64)
OCT hwNmNorthboundEventTime	1.3.6.1.4.1.2011.2.15.1.7.1.5	OCTET STRING	read-only	Time at which the alarm was generated,string(64). It can be of any of the following formats: 1. Local Time without timezone information - 'YYYY/MM/DD - hh:mm:ss' 2. UTC Time - 'YYYY/MM/DD - hh:mm:ssZ' 3. Local Time with timezone information - 'YYYY/MM/DD - hh:mm:ss,hh:mmTZ[DST]' where TZ stands for timezone information.
OCT hwNmNorthboundProbableCause	1.3.6.1.4.1.2011.2.15.1.7.1.6	OCTET STRING	read-only	Probable cause of the alarm, string(255)
OCT hwNmNorthboundSeverity	1.3.6.1.4.1.2011.2.15.1.7.1.7	OCTET STRING	read-only	Level of Alarm., string(64) It can be any of the following: Critical, Major, Minor, Warning, Indeterminate.
OCT hwNmNorthboundEventDetail	1.3.6.1.4.1.2011.2.15.1.7.1.8	OCTET STRING	read-only	Alarm ID and detail information, string(4096)
OCT hwNmNorthboundAdditionalInfo	1.3.6.1.4.1.2011.2.15.1.7.1.9	OCTET STRING	read-only	Additional information of device, such as Country, City and so on, string(255)
OCT hwNmNorthboundFaultFlag	1.3.6.1.4.1.2011.2.15.1.7.1.10	OCTET STRING	read-only	The flag which specifies whether the alarm is an Event, Fault, Recovery, Acknowledge Unacknowledge or Change.
OCT hwNmNorthboundFaultFunction	1.3.6.1.4.1.2011.2.15.1.7.1.11	OCTET STRING	read-only	The function type of the alarm.It can be one of these values:'Power','Environment','Signal','Relay','Hardware','Software','Run','Communication','Service','Processerror','UNKNOWN_FUNC_TYPE'
IP hwNmNorthboundDeviceIP	1.3.6.1.4.1.2011.2.15.1.7.1.12	IpAddress	read-only	IP address of the device
I32 hwNmNorthboundSerialNo	1.3.6.1.4.1.2011.2.15.1.7.1.13	Integer32	read-only	The serial number of alarm.
OCT hwNmNorthboundProbableRepair	1.3.6.1.4.1.2011.2.15.1.7.1.14	OCTET STRING	read-only	Alarm repair recommendations.
OCT hwNmNorthboundResourceIDs	1.3.6.1.4.1.2011.2.15.1.7.1.15	OCTET STRING	read-only	The ID of the resource.
OCT hwNmNorthboundsAdditionalVB1	1.3.6.1.4.1.2011.2.15.1.7.1.16	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB2	1.3.6.1.4.1.2011.2.15.1.7.1.17	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB3	1.3.6.1.4.1.2011.2.15.1.7.1.18	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB4	1.3.6.1.4.1.2011.2.15.1.7.1.19	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB5	1.3.6.1.4.1.2011.2.15.1.7.1.20	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB6	1.3.6.1.4.1.2011.2.15.1.7.1.21	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB7	1.3.6.1.4.1.2011.2.15.1.7.1.22	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundsAdditionalVB8	1.3.6.1.4.1.2011.2.15.1.7.1.23	OCTET STRING	read-only	Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xml
OCT hwNmNorthboundEventName	1.3.6.1.4.1.2011.2.15.1.7.1.24	OCTET STRING	read-only	The name of event,string (4096)
I32 hwNmNorthboundReasonID	1.3.6.1.4.1.2011.2.15.1.7.1.25	Integer32	read-only	The Reason ID of the alarm
I32 hwNmNorthboundFaultID	1.3.6.1.4.1.2011.2.15.1.7.1.26	Integer32	read-only	The Fault ID of the alarm
OCT hwNmNorthboundDeviceType	1.3.6.1.4.1.2011.2.15.1.7.1.27	OCTET STRING	read-only	The Device Type ID of the alarm
OCT hwNmNorthboundTrailName	1.3.6.1.4.1.2011.2.15.1.7.1.28	OCTET STRING	read-only	TrailName effected by alarm
I32 hwNmNorthboundRootAlarm	1.3.6.1.4.1.2011.2.15.1.7.1.29	Integer32	read-only	Specifies if the alarm is a root alarm 0 - Non-root alarm 1 - Root alarm
I32 hwNmNorthboundGroupID	1.3.6.1.4.1.2011.2.15.1.7.1.30	Integer32	read-only	The Group ID of the alarm
I32 hwNmNorthboundMaintainStatus	1.3.6.1.4.1.2011.2.15.1.7.1.31	Integer32	read-only	maintain status
hwNmNorthboundEventKeepAliveInfo	1.3.6.1.4.1.2011.2.15.1.7.2
hwNmNorthboundEventKeepAliveInfoTrap	1.3.6.1.4.1.2011.2.15.1.7.2.0			KeepAlive Trap
NTF hwNmNorthboundEventKeepAlive	1.3.6.1.4.1.2011.2.15.1.7.2.0.2			Notification for keep alive traps.
OCT hwNmNorthboundKeepAlive	1.3.6.1.4.1.2011.2.15.1.7.2.1	OCTET STRING	read-only	Keep Alive
hwNmNorthboundEventSynchronization	1.3.6.1.4.1.2011.2.15.1.7.7
hwNmNorthboundEventSynchronizationStart	1.3.6.1.4.1.2011.2.15.1.7.7.1
hwNmNorthboundEventSynchronizationStartTrap	1.3.6.1.4.1.2011.2.15.1.7.7.1.0			Sync Start Trap
NTF hwNmNorthboundEventSynchronizationStartNotify	1.3.6.1.4.1.2011.2.15.1.7.7.1.0.9			Notification indicates the beginning of alarm synchronization.
hwNmNorthboundEventSynchronizationQueryResult	1.3.6.1.4.1.2011.2.15.1.7.7.2
hwNmNorthboundEventSynchronizationQueryResultTrap	1.3.6.1.4.1.2011.2.15.1.7.7.2.0			Sync Notification Trap
NTF hwNmNorthboundEventSynchronizationQueryResultNotify	1.3.6.1.4.1.2011.2.15.1.7.7.2.0.10			Notification carries the query result of alarm synchronization.
hwNmNorthboundEventSynchronizationEnd	1.3.6.1.4.1.2011.2.15.1.7.7.3
hwNmNorthboundEventSynchronizationEndTrap	1.3.6.1.4.1.2011.2.15.1.7.7.3.0			Sync End Trap
NTF hwNmNorthboundEventSynchronizationEndNotify	1.3.6.1.4.1.2011.2.15.1.7.7.3.0.11			Notification indicates the end of alarm synchronization.
INT hwNmNorthboundEventSynchronizationEndStatus	1.3.6.1.4.1.2011.2.15.1.7.7.3.1	INTEGER	read-only	It shows the result of alarm synchronization. 1 means the alarm synchronization successfully ended. 2 means the alarm synchronization is stopped by the NMS's command. 3 means some error occured during the alarm synchronization.
OCT hwNmNorthboundEventSynchronizationEndStatusDetail	1.3.6.1.4.1.2011.2.15.1.7.7.3.2	OCTET STRING	read-only	The detail description of the alarm synchronization end status.
OCT hwNmNorthboundEventSynchronizationCommandStart	1.3.6.1.4.1.2011.2.15.1.7.7.4	OCTET STRING	read-write	This node is to be set to start the alarm synchronization. The format to query alarms is:- IP:port:start time:end time Query time can be UTC time, Local time or Local time with timezone. Syntax for start time and end time is - YYYYMMDDhhmmss. The interpretation of the start time and end time depends on 'AlarmTimeFormat' parameter in $IMAP_ROOT/etc/conf/snmpsvc.xml file. Query can be in any of the following formats: 1. Local time(AlarmTimeFormat = 0): Format:- IP:port:start time:end time Here, the start time and end time will be considered to be in local time format. 2. UTC time(AlarmTimeFormat = 1): Format:- IP:port:start time:end time Here, the start time and end time will be considered to be UTC format. 3. Local time with timezone(AlarmTimeFormat = 2): Format:- IP:port:start time:end time:timezone:dstflag Here, the user can mention the timezone and dst flag. Format to mention timezone is +/-hh.mm if dstflag is 0 - DST disabled, 1- DST enabled. Format to omit dst flag:- IP:port:start time:end time:timezone, will consider the dstflag to be 0. The agent will send alarm synchronization result to the IP and port specified which were raised between start time and end time. If start time and end time are missing all alarms are reported. Start time and end time both are optional. If end time is missing current time of the EMS is taken as end time. If end time is present start time is not optional, it means you cannot provide end time without specifying the start time. If there is already a running alarm synchronization for that IP and port,it will return a commit fail error.
OCT hwNmNorthboundEventSynchronizationCommandStop	1.3.6.1.4.1.2011.2.15.1.7.7.5	OCTET STRING	read-write	This node is to be set to stop the alarm synchronization. It should be set as NMS's IP:port,and the agent will stop alarm synchronization for the IP and port specified. If alarm synchronization is not in progress for the specified IP and port,it will return a commit fail error.

RFC description

Huawei IMAP northbound interface for SNMP fault filtering, alarm level control, and network management integration.

Start monitoring Huawei EMS-managed network element (iMAP v2 northbound alarm forwarding) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HW-IMAPV2NORTHBOUND-TRAP-MIB

What Is HW-IMAPV2NORTHBOUND-TRAP-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description