HW-IMAPV2NORTHBOUND-TRAP-MIB
AI MIB Summary
The HW-IMAPV2NORTHBOUND-TRAP-MIB defines the structure for SNMPv2 trap notifications generated by Huawei hardware devices to report Northbound interface events and state changes to an external management system. It enables the monitoring of interface operational status, error conditions, and link state transitions via asynchronous trap messages rather than active polling.
This MIB defines the managed objects that are used by the function interfaces of the SNMP Northbound Interface.
Main OID:
huawei.1.3.6.1.4.1.2011
68
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
68 total| Object Name |
|---|
huaweiThis MIB defines the managed objects that are used by the function interfaces of the SNMP Northbound Interface. MODULE-IDENTITY .1.3.6.1.4.1.2011 |
products OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2 |
hwNetManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15 |
hwNmAgent OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1 |
hwNmFault OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.3 |
thirdNMSFaultFilterIP: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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.3.5 |
hwNmClearAlarmsThis 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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.3.6 |
hwNmAcknowledgeAlarmsThis 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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.3.7 |
hwNmUnAcknowledgeAlarmsThis 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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.3.8 |
hwNmNorthboundEvent OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7 |
hwNmNorthboundEventInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.1 |
hwNmNorthboundEventTrapEvent Traps OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.1.0 |
hwNmNorthboundEventNotifyNotification for real-time alarm. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.1 |
hwNmNorthboundEventNotifyCriticalNotification for real-time alarm whose level is Critical. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.3 |
hwNmNorthboundEventNotifyMajorNotification for real-time alarm whose level is Major. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.4 |
hwNmNorthboundEventNotifyMinorNotification for real-time alarm whose level is Minor. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.5 |
hwNmNorthboundEventNotifyWarningNotification for real-time alarm whose level is Warning. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.6 |
hwNmNorthboundEventNotifyIndefinitelyNotification for real-time alarm whose level is Indefinitely. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.7 |
hwNmNorthboundEventNotifyUnknownSeverityNotification for real-time alarm whose level is UnknownSeverity. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.1.0.8 |
hwNmNorthboundNENameThe name of network element,string (255)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.1 |
hwNmNorthboundNETypeDevice type of element,string(64)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.2 |
hwNmNorthboundObjectInstanceInstance of element,such as number of Rack, Frame, Slot, Subslot, Port and so on,string(255)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.3 |
hwNmNorthboundEventTypeType of Event,string(64)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.4 |
hwNmNorthboundEventTimeTime 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.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.5 |
hwNmNorthboundProbableCauseProbable cause of the alarm, string(255)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.6 |
hwNmNorthboundSeverityLevel of Alarm., string(64) It can be any of the following: Critical, Major, Minor, Warning, Indeterminate.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.7 |
hwNmNorthboundEventDetailAlarm ID and detail information, string(4096)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.8 |
hwNmNorthboundAdditionalInfoAdditional information of device, such as Country, City and so on, string(255)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.9 |
hwNmNorthboundFaultFlagThe flag which specifies whether the alarm is an Event, Fault, Recovery, Acknowledge Unacknowledge or Change.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.10 |
hwNmNorthboundFaultFunctionThe 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'ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.11 |
hwNmNorthboundDeviceIPIP address of the devicero IpAddress .1.3.6.1.4.1.2011.2.15.1.7.1.12 |
hwNmNorthboundSerialNoThe serial number of alarm.ro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.13 |
hwNmNorthboundProbableRepairAlarm repair recommendations.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.14 |
hwNmNorthboundResourceIDsThe ID of the resource.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.15 |
hwNmNorthboundsAdditionalVB1Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.16 |
hwNmNorthboundsAdditionalVB2Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.17 |
hwNmNorthboundsAdditionalVB3Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.18 |
hwNmNorthboundsAdditionalVB4Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.19 |
hwNmNorthboundsAdditionalVB5Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.20 |
hwNmNorthboundsAdditionalVB6Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.21 |
hwNmNorthboundsAdditionalVB7Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.22 |
hwNmNorthboundsAdditionalVB8Additional information of the alarm. These 8 fields are decided by configuration in snmpsvc.xmlro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.23 |
hwNmNorthboundEventNameThe name of event,string (4096)ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.24 |
hwNmNorthboundReasonIDThe Reason ID of the alarmro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.25 |
hwNmNorthboundFaultIDThe Fault ID of the alarmro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.26 |
hwNmNorthboundDeviceTypeThe Device Type ID of the alarmro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.27 |
hwNmNorthboundTrailNameTrailName effected by alarmro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.1.28 |
hwNmNorthboundRootAlarmSpecifies if the alarm is a root alarm 0 - Non-root alarm 1 - Root alarmro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.29 |
hwNmNorthboundGroupIDThe Group ID of the alarmro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.30 |
hwNmNorthboundMaintainStatusmaintain statusro Integer32 .1.3.6.1.4.1.2011.2.15.1.7.1.31 |
hwNmNorthboundEventKeepAliveInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.2 |
hwNmNorthboundEventKeepAliveInfoTrapKeepAlive Trap OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.2.0 |
hwNmNorthboundEventKeepAliveNotification for keep alive traps. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.2.0.2 |
hwNmNorthboundKeepAliveKeep Alivero OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.2.1 |
hwNmNorthboundEventSynchronization OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7 |
hwNmNorthboundEventSynchronizationStart OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.1 |
hwNmNorthboundEventSynchronizationStartTrapSync Start Trap OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.1.0 |
hwNmNorthboundEventSynchronizationStartNotifyNotification indicates the beginning of alarm synchronization. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.7.1.0.9 |
hwNmNorthboundEventSynchronizationQueryResult OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.2 |
hwNmNorthboundEventSynchronizationQueryResultTrapSync Notification Trap OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.2.0 |
hwNmNorthboundEventSynchronizationQueryResultNotifyNotification carries the query result of alarm synchronization. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.7.2.0.10 |
hwNmNorthboundEventSynchronizationEnd OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.3 |
hwNmNorthboundEventSynchronizationEndTrapSync End Trap OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.15.1.7.7.3.0 |
hwNmNorthboundEventSynchronizationEndNotifyNotification indicates the end of alarm synchronization. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.2.15.1.7.7.3.0.11 |
hwNmNorthboundEventSynchronizationEndStatusIt 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.ro Enumeration .1.3.6.1.4.1.2011.2.15.1.7.7.3.1 |
hwNmNorthboundEventSynchronizationEndStatusDetailThe detail description of the alarm synchronization end status.ro OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.7.3.2 |
hwNmNorthboundEventSynchronizationCommandStartThis 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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.7.4 |
hwNmNorthboundEventSynchronizationCommandStopThis 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.rw OCTET STRING .1.3.6.1.4.1.2011.2.15.1.7.7.5 |