M2000-V2

All MIBs › M2000-V2

Organization: iMAP

Last Updated: 2006-10-05

Description: M2000-V2 module

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 M2000-V2?

M2000-V2 is a Huawei M2000-family Element Management System MIB that defines managed objects used by the SNMP Northbound Interface, i.e., the objects an upstream OSS/NMS polls or receives notifications for when integrating with Huawei's M2000 management platform rather than objects on a single network element itself. No sample objects were provided in the source, limiting concrete specificity, but as a northbound integration MIB it would typically expose alarm/fault summary objects, managed-element status, and system-level notifications representing the aggregated state of the devices under M2000 management. Administrators use it to monitor the software-level health and alarm status of the managed network as surfaced through the M2000 EMS northbound interface, rather than hardware sensors on a single box. It is inherently dependent on the broader Huawei M2000 EMS architecture and the network elements it manages, acting as an aggregation/proxy layer rather than a standalone device MIB. It is deployed at the OSS/NMS integration layer where a higher-level management system polls or receives traps from Huawei's M2000 EMS for telecom network monitoring. Engineers can download the M2000-V2 file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in M2000-V2. 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 M2000 Element Management System (EMS) northbound interface

Monitoring Examples

Without concrete sample object names, a specific grounded monitoring example cannot be constructed for this module; in general, an integrating OSS would use this MIB's northbound objects to receive alarm notifications and query aggregated managed-element status forwarded by the M2000 EMS rather than polling hardware sensors directly.

What Can Be Monitored

aggregated alarm/fault status
managed network element status
EMS northbound notifications

Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

OIDs

OID symbolic	OID numeric	Type	Access	Description
iMAP	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
iMAPNetManagement	1.3.6.1.4.1.2011.2.15
iMAPNorthbound	1.3.6.1.4.1.2011.2.15.2
iMAPNorthboundCommon	1.3.6.1.4.1.2011.2.15.2.1
iMAPNorthboundEventMgmt	1.3.6.1.4.1.2011.2.15.2.1.2
iMAPNorthboundNotificationReport	1.3.6.1.4.1.2011.2.15.2.1.2.1
iMAPNorthboundNotificationCommon	1.3.6.1.4.1.2011.2.15.2.1.2.1.1
iMAPNorthboundHeartbeatNotification	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1
iMAPNorthboundHeartbeatNotificationV2	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.0			Root node for the converted TRAP-TYPEs.
NTF iMAPNorthboundHeartbeatNotificationType	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.0.5			The M2000 sends the heartbeat notification trap to the NMS regularly each period. If the NMS receives the trap, the connection between the NMS and the M2000 works. If not, the connection fails.
OCT iMAPNorthboundHeartbeatSystemLabel	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.1	OCTET STRING	read-only	Managed system ID: indicates the managed system from which the heartbeat notification is reported. It uniquely identifies one EMS.
I32 iMAPNorthboundHeartbeatPeriod	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.2	Integer32	read-only	Heartbeat period
OCT iMAPNorthboundHeartbeatTimeStamp	1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.3	OCTET STRING	read-only	Time stamp: the time when the notification is generated
iMAPNorthboundCommuLinkMonitor	1.3.6.1.4.1.2011.2.15.2.1.3
iMAPNorthboundHeartbeatSvc	1.3.6.1.4.1.2011.2.15.2.1.3.1
I32 iMAPNorthboundHeartbeatSvcReportInterval	1.3.6.1.4.1.2011.2.15.2.1.3.1.1	Integer32	read-write	Accepts integral values in the range 3-300 (both end inclusive) Sets heartbeat interval to the value supplied. A heart beat is sent immediately consisting of changed interval. Attempt to set with invalid value results in error.
iMAPNorthboundFault	1.3.6.1.4.1.2011.2.15.2.4
iMAPNorthboundFaultQuery	1.3.6.1.4.1.2011.2.15.2.4.1
OCT iMAPNorthboundAlarmQuery	1.3.6.1.4.1.2011.2.15.2.4.1.5	OCTET STRING	read-write	Accepts only values 0 and 1 (single character) Attempt to set any other value returns error 1-> starts query active alarm process (if previous query alarm process is in progress then error is returned) 0-> stops the previous query active alarm process in progress (if any)
iMAPNorthboundFaultNotification	1.3.6.1.4.1.2011.2.15.2.4.3
iMAPNorthboundFaultAlarmNotification	1.3.6.1.4.1.2011.2.15.2.4.3.3
iMAPNorthboundFaultAlarmNotificationV2	1.3.6.1.4.1.2011.2.15.2.4.3.3.0			Root node for the converted TRAP-TYPEs.
NTF iMAPNorthboundFaultAlarmReportNotificationType	1.3.6.1.4.1.2011.2.15.2.4.3.3.0.1			The M2000 system sends real-time alarms to the NMS using this trap. If an alarm occurs to an NE or the M2000, the M2000 sends the alarm trap to the NMS.
NTF iMAPNorthboundFaultAlarmQueryBeginNotificationType	1.3.6.1.4.1.2011.2.15.2.4.3.3.0.2			The M2000 notifies the NMS of the start of the query. After the NMS receives the active alarm query start trap, the query starts. The trap is triggered by NMS for alarm query.
NTF iMAPNorthboundFaultAlarmQueryNotificationType	1.3.6.1.4.1.2011.2.15.2.4.3.3.0.3			The M2000 system sends queried alarms to the NMS using this trap.
NTF iMAPNorthboundFaultAlarmQueryEndNotificationType	1.3.6.1.4.1.2011.2.15.2.4.3.3.0.4			The M2000 notifies the NMS of the stop of the query. After the NMS receives the active alarm query stop trap, it indicates that the query ends. The NMS triggers the stop of the query, or the query ends after the NMS receives the active alarms.
OCT iMAPNorthboundAlarmCSN	1.3.6.1.4.1.2011.2.15.2.4.3.3.1	OCTET STRING	read-only	Alarm network number > 0
OCT iMAPNorthboundAlarmCategory	1.3.6.1.4.1.2011.2.15.2.4.3.3.2	OCTET STRING	read-only	Category can be one of the following: 1. Fault 2. Clear 3. Event 4. Acknowledge 5. Unacknowledge 9. Change
OCT iMAPNorthboundAlarmOccurTime	1.3.6.1.4.1.2011.2.15.2.4.3.3.3	OCTET STRING	read-only	Occurrence time
OCT iMAPNorthboundAlarmMOName	1.3.6.1.4.1.2011.2.15.2.4.3.3.4	OCTET STRING	read-only	Managed object name
INT iMAPNorthboundAlarmProductID	1.3.6.1.4.1.2011.2.15.2.4.3.3.5	INTEGER	read-only	Product type ID: 1:transmission 2:mobile 3:fixed network narrowband 4:fixed network broadband 5:intelligent network 6:omc
OCT iMAPNorthboundAlarmNEType	1.3.6.1.4.1.2011.2.15.2.4.3.3.6	OCTET STRING	read-only	NE type > 0
OCT iMAPNorthboundAlarmNEDevID	1.3.6.1.4.1.2011.2.15.2.4.3.3.7	OCTET STRING	read-only	NE ID
OCT iMAPNorthboundAlarmDevCsn	1.3.6.1.4.1.2011.2.15.2.4.3.3.8	OCTET STRING	read-only	Device serial number
I32 iMAPNorthboundAlarmID	1.3.6.1.4.1.2011.2.15.2.4.3.3.9	Integer32	read-only	Alarm ID
I32 iMAPNorthboundAlarmType	1.3.6.1.4.1.2011.2.15.2.4.3.3.10	Integer32	read-only	Alarm type.
INT iMAPNorthboundAlarmLevel	1.3.6.1.4.1.2011.2.15.2.4.3.3.11	INTEGER	read-only	Level is the alarm severity. It can be one of the following: 1. Critical 2. Major 3. Minor 4. Warning 6. Cleared
INT iMAPNorthboundAlarmRestore	1.3.6.1.4.1.2011.2.15.2.4.3.3.12	INTEGER	read-only	Alarm clear status 1:Cleared 2:Uncleared
INT iMAPNorthboundAlarmConfirm	1.3.6.1.4.1.2011.2.15.2.4.3.3.13	INTEGER	read-only	Alarm acknowledgement status 1:Acknowledged 2:Unacknowledged
OCT iMAPNorthboundAlarmAckTime	1.3.6.1.4.1.2011.2.15.2.4.3.3.14	OCTET STRING	read-only	Acknowledged time
OCT iMAPNorthboundAlarmRestoreTime	1.3.6.1.4.1.2011.2.15.2.4.3.3.15	OCTET STRING	read-only	Cleared time
OCT iMAPNorthboundAlarmOperator	1.3.6.1.4.1.2011.2.15.2.4.3.3.16	OCTET STRING	read-only	It identifies the last user who has changed the Acknowledged State.
I32 iMAPNorthboundAlarmParas1	1.3.6.1.4.1.2011.2.15.2.4.3.3.17	Integer32	read-only	Reserved field 1
I32 iMAPNorthboundAlarmParas2	1.3.6.1.4.1.2011.2.15.2.4.3.3.18	Integer32	read-only	Reserved field 2
I32 iMAPNorthboundAlarmParas3	1.3.6.1.4.1.2011.2.15.2.4.3.3.19	Integer32	read-only	Reserved field 3
I32 iMAPNorthboundAlarmParas4	1.3.6.1.4.1.2011.2.15.2.4.3.3.20	Integer32	read-only	Reserved field 4
I32 iMAPNorthboundAlarmParas5	1.3.6.1.4.1.2011.2.15.2.4.3.3.21	Integer32	read-only	Reserved field 5
I32 iMAPNorthboundAlarmParas6	1.3.6.1.4.1.2011.2.15.2.4.3.3.22	Integer32	read-only	Reserved field 6
I32 iMAPNorthboundAlarmParas7	1.3.6.1.4.1.2011.2.15.2.4.3.3.23	Integer32	read-only	Reserved field 7
I32 iMAPNorthboundAlarmParas8	1.3.6.1.4.1.2011.2.15.2.4.3.3.24	Integer32	read-only	Reserved field 8
I32 iMAPNorthboundAlarmParas9	1.3.6.1.4.1.2011.2.15.2.4.3.3.25	Integer32	read-only	Reserved field 9
I32 iMAPNorthboundAlarmParas10	1.3.6.1.4.1.2011.2.15.2.4.3.3.26	Integer32	read-only	Original alarm level, defined by the device when the alarm is generated. 1 Critical 2 Major 3 Minor 4 Warning
OCT iMAPNorthboundAlarmExtendInfo	1.3.6.1.4.1.2011.2.15.2.4.3.3.27	OCTET STRING	read-only	Extended information (max: 250 characters)
OCT iMAPNorthboundAlarmProbablecause	1.3.6.1.4.1.2011.2.15.2.4.3.3.28	OCTET STRING	read-only	Alarm Probablecause (max: 250 characters)
OCT iMAPNorthboundAlarmProposedrepairactions	1.3.6.1.4.1.2011.2.15.2.4.3.3.29	OCTET STRING	read-only	Alarm Proposed Repairactions (max: 250 characters)
OCT iMAPNorthboundAlarmSpecificproblems	1.3.6.1.4.1.2011.2.15.2.4.3.3.30	OCTET STRING	read-only	Alarm Specific Problems (max: 250 characters)
OCT iMAPNorthboundAlarmClearOperator	1.3.6.1.4.1.2011.2.15.2.4.3.3.46	OCTET STRING	accessible-for-notify	The operator who cleared this alarm.
OCT iMAPNorthboundAlarmObjectInstanceType	1.3.6.1.4.1.2011.2.15.2.4.3.3.47	OCTET STRING	accessible-for-notify	Object instance type
OCT iMAPNorthboundAlarmClearCategory	1.3.6.1.4.1.2011.2.15.2.4.3.3.48	OCTET STRING	accessible-for-notify	Clear Category of Alarms
OCT iMAPNorthboundAlarmClearType	1.3.6.1.4.1.2011.2.15.2.4.3.3.49	OCTET STRING	accessible-for-notify	Clear type of alarms
OCT iMAPNorthboundAlarmServiceAffectFlag	1.3.6.1.4.1.2011.2.15.2.4.3.3.50	OCTET STRING	accessible-for-notify	Affecting service flag for the alarm
OCT iMAPNorthboundAlarmAdditionalInfo	1.3.6.1.4.1.2011.2.15.2.4.3.3.51	OCTET STRING	accessible-for-notify	Additional Information regarding the alarm
iMAPNorthboundFaultAcknowledge	1.3.6.1.4.1.2011.2.15.2.4.4
OCT iMAPNorthboundAlarmAcknowledge	1.3.6.1.4.1.2011.2.15.2.4.4.1	OCTET STRING	read-write	Give serial number(s) of alarms to be acknowledged. 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 invalid Alarm serial number(s). If all alarms are successfully acknowledged then output is blank.
iMAPNorthboundFaultUnAcknowledge	1.3.6.1.4.1.2011.2.15.2.4.5
OCT iMAPNorthboundAlarmUnAcknowledge	1.3.6.1.4.1.2011.2.15.2.4.5.1	OCTET STRING	read-write	Give serial number(s) of alarms to be unacknowledged. 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 invalid Alarm serial number(s). If all alarms are successfully unacknowledged then output is blank.
iMAPNorthboundFaultClear	1.3.6.1.4.1.2011.2.15.2.4.6
OCT iMAPNorthboundAlarmClear	1.3.6.1.4.1.2011.2.15.2.4.6.1	OCTET STRING	read-write	Give serial number(s) of alarms to be cleared. 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 invalid Alarm serial number(s). If all alarms are successfully cleared then output is blank.
iMAPConformance	1.3.6.1.4.1.2011.3
iMAPGroups	1.3.6.1.4.1.2011.3.1
currentObjectGroup	1.3.6.1.4.1.2011.3.1.1			The OBJECT-GROUP for SNMP Northbound Interface
currentNotificationGroup	1.3.6.1.4.1.2011.3.1.2			The NOTIFICATION-GROUP for SNMP Northbound Interface.
iMAPCompliances	1.3.6.1.4.1.2011.3.2
basicCompliance	1.3.6.1.4.1.2011.3.2.1			MODULE-COMPLIANCE for SNMP Northbound Interface

RFC description

SNMP northbound interface management information for iMAP network management systems.

Start monitoring Huawei M2000 Element Management System (EMS) northbound interface 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 M2000-V2

What Is M2000-V2?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description