HUAWEI-ISIS-MIB

All MIBs › HUAWEI-ISIS-MIB

Organization: Huawei Technologies co.,Ltd.

Last Updated: 2003-06-11

Category: Routing Protocols, Vendor: Huawei

Description: Huawei IS-IS MIB for managing IS-IS routing protocol instances, adjacencies, level-1/2 topology, and routing database on Huawei routers.

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 HUAWEI-ISIS-MIB?

HUAWEI-ISIS-MIB is a Huawei-proprietary MIB implemented on Huawei routers to manage the IS-IS (Intermediate System to Intermediate System) interior gateway routing protocol in a pure IP environment, covering Huawei-specific private extensions beyond the standard protocol objects. Its data spans configuration of IS-IS protocol instances and interfaces, and operational state including neighbor adjacency status, Level-1/Level-2 topology information, and the link-state routing database. As a core routing-protocol MIB it is essential for monitoring the software health of the routing control plane: whether IS-IS adjacencies with neighboring routers are up or flapping, whether the link-state database is synchronized, and whether routes are being computed and installed correctly, all of which directly affect network reachability. It is explicitly a private/vendor extension layered on the standard IS-IS protocol and complements (rather than replaces) any standard ISIS-MIB objects a device may also support. It is typically deployed on Huawei NE/CE/AR-series routers in service-provider or enterprise core and backbone networks running IS-IS as their IGP. Network engineers evaluating or troubleshooting this functionality can download the HUAWEI-ISIS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-ISIS-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 routers (NE/CE/AR-series) running IS-IS

Monitoring Examples

An administrator would poll IS-IS adjacency-state objects to confirm neighbor relationships on a given interface are in the "up" state, and would check Level-1/Level-2 database synchronization objects to verify the router has a consistent view of network topology. No sample object names were provided for this module, so specific table names cannot be cited, but the module description confirms adjacency and topology/database monitoring as the scope. A neighbor adjacency repeatedly transitioning down and back up (flapping) would indicate a link-quality or timer-mismatch problem needing investigation.

What Can Be Monitored

IS-IS neighbor adjacency status
Level-1/Level-2 topology database state
routing instance configuration
link-state database synchronization

Imported Objects

From HUAWEI-3COM-OID-MIB

huaweiMgmt

OBJECT-IDENTITY

From ISIS-MIB

isisCircAdjChanges	OBJECT-TYPE
isisCircEntry	OBJECT-TYPE
isisCircInitFails	OBJECT-TYPE
isisCircLANL1DesISChanges
isisCircLANL2DesISChanges
isisCircRejAdjs	OBJECT-TYPE
isisIPRAEntry	OBJECT-TYPE
isisISAdjNeighSysID	OBJECT-TYPE
isisISAdjState	OBJECT-TYPE
isisSysAttmptToExMaxSeqNums
isisSysAuthFails
isisSysCorrLSPs
isisSysEntry
isisSysID	OBJECT-TYPE
isisSysIDFieldLenMismatches
isisSysL1State
isisSysL2State
isisSysLSPL1DbaseOloads
isisSysLSPL2DbaseOloads
isisSysManAddrDropFromAreas
isisSysMaxAreaAddrMismatches
isisSysMaxAreaAddresses
isisSysOwnLSPPurges
isisSysSeqNumSkips
isisSysType
isisSysVersion	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using hwIsisSysWrongSysTypes OID:

Select a Huawei router (NE/CE/AR-series) running IS-I as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type hwIsisSysWrongSysTypes into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the number of Times Wrong System Types requested for Adjacencies. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
huaweiDatacomm	1.3.6.1.4.1.2011.5.25
hwISIS	1.3.6.1.4.1.2011.5.25.24			The private ISIS MIB contains objects to manage the ISIS routing protocol private objects in pure IP environment.
hwIsisSystem	1.3.6.1.4.1.2011.5.25.24.1			ISIS global system information.
hwIsisSysTable	1.3.6.1.4.1.2011.5.25.24.1.1		not-accessible	The set of instances of the Integrated IS-IS protocol existing on the system.
hwIsisSysEntry	1.3.6.1.4.1.2011.5.25.24.1.1.1		not-accessible	Each row defines Huawei priviate information specific to a single instance of the protocol existing on the system.
C32 hwIsisSysWrongSysTypesEx	1.3.6.1.4.1.2011.5.25.24.1.1.1.1	Counter32	read-only	Number of Times Wrong System Types requested for Adjacencies.
OCT hwIsisSysAuthAreaRecvPwd1	1.3.6.1.4.1.2011.5.25.24.1.1.1.2	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysAuthAreaType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthAreaType does not modify the hwIsisSysAuthAreaRecvPwd1 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisSysAuthAreaRecvPwd2	1.3.6.1.4.1.2011.5.25.24.1.1.1.3	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysAuthAreaType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthAreaType does not modify the hwIsisSysAuthAreaRecvPwd2 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisSysAuthAreaRecvPwd3	1.3.6.1.4.1.2011.5.25.24.1.1.1.4	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysAuthAreaType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthAreaType does not modify the hwIsisSysAuthAreaRecvPwd3 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisSysAuthDomainRecvPwd1	1.3.6.1.4.1.2011.5.25.24.1.1.1.5	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 2 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysDomainAreaType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthDomainType does not modify the hwIsisSysAuthDomainRecvPwd1 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisSysAuthDomainRecvPwd2	1.3.6.1.4.1.2011.5.25.24.1.1.1.6	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 2 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysAuthDomainType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthDomainType does not modify the hwIsisSysAuthDomainRecvPwd2 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisSysAuthDomainRecvPwd3	1.3.6.1.4.1.2011.5.25.24.1.1.1.7	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 2 Link State Packets receivied from the neighbouring systems, whenever the value of isisSysDomainAreaType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of isisSysAuthDomainType does not modify the hwIsisSysAuthDomainRecvPwd3 value. Reading this object always results in an of length zero; authentication may not be bypassed by reading the MIB object.
T/F hwIsisSysSetLSDBOload	1.3.6.1.4.1.2011.5.25.24.1.1.1.8	TruthValue	read-write	Setting this object to 'true' forces the system to set the overload bit in its non-pseudonode LSPs. The result will be that no paths through this system are seen by other systems in the IS-IS area.
hwIsisCirc	1.3.6.1.4.1.2011.5.25.24.2			ISIS local circuits information.
hwIsisCircTable	1.3.6.1.4.1.2011.5.25.24.2.1		not-accessible	The table of circuits used by each instance of Integrated IS-IS on this system.
hwIsisCircEntry	1.3.6.1.4.1.2011.5.25.24.2.1.1		not-accessible	An isisCircEntry exists for each circuit used by Integrated IS-IS on this system.
OPE hwIsisCircFuncState	1.3.6.1.4.1.2011.5.25.24.2.1.1.1	OperState	read-only	The functional state of the circuit. This specifies whether the circuit is currently active or not.
INT hwIsisCircLevel	1.3.6.1.4.1.2011.5.25.24.2.1.1.2	INTEGER	read-write	The level of the circuit. This object follows the replaceOnlyWhileDisabled behaviour.
OCT hwIsisCircL1TransPassword	1.3.6.1.4.1.2011.5.25.24.2.1.1.3	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets while transmitting, whenever the corresponding instance of isisCircL1AuthType has a value of plaintext or md5. A modification of the corresponding instance of isisCircL1AuthType does not modify the hwIsisCircL1TransPassword value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL1RecvPassword1	1.3.6.1.4.1.2011.5.25.24.2.1.1.4	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL1AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL1AuthType does not modify the hwIsisCircL1RecvPassword1 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL1RecvPassword2	1.3.6.1.4.1.2011.5.25.24.2.1.1.5	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL1AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL1AuthType does not modify the hwIsisCircL1RecvPassword2 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL1RecvPassword3	1.3.6.1.4.1.2011.5.25.24.2.1.1.6	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL1AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL1AuthType does not modify the hwIsisCircL1RecvPassword3 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL2TransPassword	1.3.6.1.4.1.2011.5.25.24.2.1.1.7	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 2 and Point-to-Point hello packets while transmitting, whenever the corresponding instance of isisCircL2AuthType has a value of plaintext or md5. A modification of the corresponding instance of isisCircL2AuthType does not modify the hwIsisCircL2TransPassword value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL2RecvPassword1	1.3.6.1.4.1.2011.5.25.24.2.1.1.8	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL2AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL2AuthType does not modify the hwIsisCircL2RecvPassword1 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL2RecvPassword2	1.3.6.1.4.1.2011.5.25.24.2.1.1.9	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL2AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL2AuthType does not modify the hwIsisCircL2RecvPassword2 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
OCT hwIsisCircL2RecvPassword3	1.3.6.1.4.1.2011.5.25.24.2.1.1.10	OCTET STRING	read-write	The value to be used as the Authentication Key in Level 1 and Point-to-Point hello packets that are receivied from the neighboring Systems, whenever the corresponding instance of isisCircL2AuthType has a value of plaintext or md5. Authentication of the received LSP is successful, when authentication is successful on using any one of the RecvPwd?. A modification of the corresponding instance of isisCircL2AuthType does not modify the hwIsisCircL2RecvPassword3 value. Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
C32 hwIsisCircVersionSkews	1.3.6.1.4.1.2011.5.25.24.2.1.1.11	Counter32	read-only	The number of PDUs of different version was received
C32 hwIsisCircStateChanges	1.3.6.1.4.1.2011.5.25.24.2.1.1.12	Counter32	read-only	The number of times the circuit has changed the state.
C32 hwIsisCircAreaMismatches	1.3.6.1.4.1.2011.5.25.24.2.1.1.13	Counter32	read-only	The number PDUs from an unrecognised area was received
hwIsisIPReachAddr	1.3.6.1.4.1.2011.5.25.24.3			ISIS local interface IP address information.
hwIsisIPRATable	1.3.6.1.4.1.2011.5.25.24.3.1		not-accessible	The table of IP Reachable Addresses to networks, subnetworks or hosts either manually configured or learned from another protocol.
hwIsisIPRAEntry	1.3.6.1.4.1.2011.5.25.24.3.1.1		not-accessible	Each entry defines an IP Reachable Address to a network, subnetwork or host.
OPE hwIsisIPRAFuncState	1.3.6.1.4.1.2011.5.25.24.3.1.1.1	OperState	read-only	The functional state of the IP reachable address. This specifies whether this RA is active or not.
IP hwIsisIPRANextHopAddress	1.3.6.1.4.1.2011.5.25.24.3.1.1.3	IpAddress	read-write	The Next Hop IP Address to which a PDU may be forwarded in order to reach a destination which matches this IP Reachable Address. This object follows the manualOrAutomatic behaviour.
hwIsisNotifications	1.3.6.1.4.1.2011.5.25.24.4			ISIS trap information.
NTF hwIsisCorruptedLSPDetected	1.3.6.1.4.1.2011.5.25.24.4.1			The Corrupted LSP Detected Notification is generated when a corrupted Link State PDU is detected in memory.
NTF hwIsisCorruptedLSPReceived	1.3.6.1.4.1.2011.5.25.24.4.2			The Corrupted LSP Received Notification is generated when a corrupted Link State PDU is Received. The occurance of this event is counted by the isisSysCorrLSPscounter.
NTF hwIsisLSPL1DatabaseOverload	1.3.6.1.4.1.2011.5.25.24.4.3			The LSP L1 Database Overload Notification is generated when the l1State of the system changes between On and Waiting or Waiting and On. The isisSysL1State argument is set to indicate the resulting state, and in the case of Waiting the isisSysID is set to indicate the source of the LSP which precipitated the overload. The occurance of this event is counted by the isisSysLSPL1DbaseOloads counter.
NTF hwIsisLSPL2DatabaseOverload	1.3.6.1.4.1.2011.5.25.24.4.4			The LSP L2 Database Overload Notification is generated when the l2State of the system changes between On and Waiting or Waiting and On. The isisSysL2State argument is set to indicate the resulting state, and in the case of Waiting the isisSysID is set to indicate the source of the LSP which precipitated the overload. The occurance of this event is counted by the isisSysLSPL2DbaseOloads counter.
NTF hwIsisAuthenticationFailure	1.3.6.1.4.1.2011.5.25.24.4.5			Generated when a PDU is received with an incorrect Authentication information field
NTF hwIsisWrongSysType	1.3.6.1.4.1.2011.5.25.24.4.6			Generated when a Adjacency Request for Wrong/unsupported adjacency type is made.
NTF hwIsisVersionSkew	1.3.6.1.4.1.2011.5.25.24.4.7			Generated when a PDU of Wrong/different version is received
NTF hwIsisIDFieldLengthMismatch	1.3.6.1.4.1.2011.5.25.24.4.8			The hwIsisIDFieldLengthMismatch Notification is generated when a PDU is received with a different value for ID field length to that of the receiving Intermediate system. The occurance of this event is counted by the isisSysIDFieldLenMismatches.
NTF hwIsisAreaMismatch	1.3.6.1.4.1.2011.5.25.24.4.9			Generated when a PDU is received from Wrong/different area not recognised by this system
NTF hwIsisMaxAreaAddrMismatch	1.3.6.1.4.1.2011.5.25.24.4.10			Generated when a PDU is received from Wrong/different area not recognised by this system
NTF hwIsisManualAddressDroppedFromArea	1.3.6.1.4.1.2011.5.25.24.4.11			The Manual Address Dropped From Area Notification is generated when one of the manualAreaAddresses (specified on this system) is ignored when computing partitionAreaAddresses or areaAddresses because there are more than MaximumAreaAddresses distinct Area Addresses. The hwIsisTrapDroppedAreaAddr argument is set to the ignored Area Address. It is generated once for each Area Address in manualAreaAddresses which is dropped. The occurance of this event is counted by the isisSysManAddrDropFromAreas counter.
NTF hwIsisAttemptToExceedMaximumSequenceNumber	1.3.6.1.4.1.2011.5.25.24.4.12			The Attempt To Exceed Maximum Sequence Number Notification is generated when an attempt is made to increment the sequence number of an LSP beyond the maximum sequence number. Following the generation of this event the operation of the Routeing state machine shall be disabled for atleast (MaxAge + ZeroAgeLifetime) seconds. The occurance of this event is counted by the isisSysAttmptToExMaxSeqNums counter.
NTF hwIsisSequenceNumberSkip	1.3.6.1.4.1.2011.5.25.24.4.13			The Sequence Number Skipped Notification is generated when the sequence number of an LSP is incremented by more than one. The occurance of this event is counted by the isisSysSeqNumSkips counter.
NTF hwIsisOwnLSPPurge	1.3.6.1.4.1.2011.5.25.24.4.14			The Own LSP Purged Notification is generated when a zero aged copy of a system's own LSP is received from some other system. This represents an erroneous attempt to purge the local system's LSP. The occurance of this event is counted by the isisSysOwnLSPPurges counter.
NTF hwIsisCircuitChange	1.3.6.1.4.1.2011.5.25.24.4.15			The Circuit Change Notification is generated when the state of the Circuit changes from On to Off or from Off to On. The relative order of events relating to the same Circuit must be preserved.
NTF hwIsisAdjacencyStateChange	1.3.6.1.4.1.2011.5.25.24.4.16			The Adjacency State Change Notification is generated when the state of an Adjacency on the Circuit changes from Up to Down or Down to Up. For these purposes the states Up and Up/dormant are considered to be Up, and any other state is considered to be Down. The occurance of this event is counted by the isisCircAdjChanges counter.
NTF hwIsisInitializationFailure	1.3.6.1.4.1.2011.5.25.24.4.17			The Initialisation Failure Notification is generated when an attempt to initialise with an adjacent system fails as a result of either Version Skew or Area Mismatch. In the case of Version Skew, the Adjacent system argument is not present. The occurance of this event is counted by the isisCircInitFails counter.
NTF hwIsisRejectedAdjacency	1.3.6.1.4.1.2011.5.25.24.4.18			The Rejected Adjacency Notification is generated when an attempt to create a new adjacency is rejected, because of a lack of resources. The occurance of this event is counted by the isisCircRejAdjs counter.
NTF hwIsisLanL1DesignatedIntermediateSystemChange	1.3.6.1.4.1.2011.5.25.24.4.19			The LAN L1 Designated Intermediate System Change Notification is generated when the local system either elects itself or resigns as being the LAN L1 Designated Intermediate System on this circuit. The relative order of these events must be preserved. The occurance of this event is counted by the isisCircLANL1DesISChanges counter.
NTF hwIsisLanL2DesignatedIntermediateSystemChange	1.3.6.1.4.1.2011.5.25.24.4.20			The LAN L2 Designated Intermediate System Change Notification is generated when the local system either elects itself or resigns as being the LAN L2 Designated Intermediate System on this circuit. The relative order of these events must be preserved. The occurance of this event is counted by the isisCircLANL2DesISChanges counter.
hwIsisTrapTable	1.3.6.1.4.1.2011.5.25.24.5		not-accessible	The set of Values needed for trap support.
hwIsisTrapEntry	1.3.6.1.4.1.2011.5.25.24.5.1		not-accessible	Each row defines information specific to a Trap information
I32 hwIsisTrapSysInstance	1.3.6.1.4.1.2011.5.25.24.5.1.1	Integer32	not-accessible	The unique identifier of the Integrated IS-IS instance to which this row corresponds. This object follows the index behaviour.
ADR hwIsisTrapDroppedAreaAddr	1.3.6.1.4.1.2011.5.25.24.5.1.2	OSINSAddress	read-only	The Area Address that was dropped by the system when the count of area addresses exceeded the Maximum .
LSP hwIsisTrapCorruptedLSPID	1.3.6.1.4.1.2011.5.25.24.5.1.3	LSPID	read-only	The ID of the LSP that was found to be Corrupted.
I32 hwIsisTrapSysIDLength	1.3.6.1.4.1.2011.5.25.24.5.1.4	Integer32	read-only	The Length of the SystemID of current system.
I32 hwIsisTrapRecdSysIDLength	1.3.6.1.4.1.2011.5.25.24.5.1.5	Integer32	read-only	The Receined systemID Length
ADR hwIsisTrapRecdAreaAddr	1.3.6.1.4.1.2011.5.25.24.5.1.6	OSINSAddress	read-only	The Received Area Address
I32 hwIsisTrapAuthErrorType	1.3.6.1.4.1.2011.5.25.24.5.1.7	Integer32	read-only	The type of Authentication Error.
OCT hwIsisTrapAuthErrorInfo	1.3.6.1.4.1.2011.5.25.24.5.1.8	OCTET STRING	read-only	The Information Pertaining to the Authentication error.
I32 hwIsisTrapRecdSysType	1.3.6.1.4.1.2011.5.25.24.5.1.9	Integer32	read-only	The Received system Type.
STR hwIsisTrapRecdVersion	1.3.6.1.4.1.2011.5.25.24.5.1.10	DisplayString	read-only	The version number of the IS-IS protocol that was received.
I32 hwIsisTrapRecdMaxAreaAddr	1.3.6.1.4.1.2011.5.25.24.5.1.11	Integer32	read-only	The Max Area Address Count in a received PDU.
hwIsisConformance	1.3.6.1.4.1.2011.5.25.24.6
hwIsisCompliances	1.3.6.1.4.1.2011.5.25.24.6.1
hwIsisCompliance	1.3.6.1.4.1.2011.5.25.24.6.1.1			The compliance statement for entities implementing the Huawei ISIS MIB
hwIsisGroups	1.3.6.1.4.1.2011.5.25.24.6.2
hwIsisGroup	1.3.6.1.4.1.2011.5.25.24.6.2.1			A collection of objects.
hwIsisNotificationGroup	1.3.6.1.4.1.2011.5.25.24.6.2.2			A collection of isis notification objects.
hwIsisTrapInfoGroup	1.3.6.1.4.1.2011.5.25.24.6.2.3			A collection of objects providing trap records.

RFC description

Manages Huawei IS-IS routing protocol status, adjacencies, and Link State Protocol database information.

Start monitoring Huawei router (NE/CE/AR-series) running IS-IS 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 HUAWEI-ISIS-MIB