HH3C-NET-MAN-MIB
This MIB file is to provide the object definition of the network
management parameters. These parameters are used to identify devices.
It is useful for devices management in a dynamic address assignment
network.
- Source file
HH3C-NET-MAN-MIB- Last revised
- Identity
hh3cNetMan- Base OID
1.3.6.1.4.1.25506.2.90
Imported Objects
| HH3C-OID-MIB | hh3cCommon |
| INET-ADDRESS-MIB | InetAddress InetAddressType |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
Net-SNMP examples using the hh3c MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'HH3C-NET-MAN-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HH3C-NET-MAN-MIB::hh3cNetMan'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HH3C-NET-MAN-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HH3C-NET-MAN-MIB::hh3cNetMan'
Objects (14)
Showing 14 of 14 objects
Object legend
Table
Row
Column
Scalar
Node
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.25506.2.90 |
||
.1.3.6.1.4.1.25506.2.90.1 |
||
.1.3.6.1.4.1.25506.2.90.2 |
||
.1.3.6.1.4.1.25506.2.90.3 |
||
.1.3.6.1.4.1.25506.2.90.3.1 |
||
.1.3.6.1.4.1.25506.2.90.3.1.1 |
||
.1.3.6.1.4.1.25506.2.90.3.1.2 |
||
|
OctetString
|
.1.3.6.1.4.1.25506.2.90.3.1.3 |
|
|
OctetString
|
.1.3.6.1.4.1.25506.2.90.3.1.4 |
|
.1.3.6.1.4.1.25506.2.90.3.2 |
||
.1.3.6.1.4.1.25506.2.90.3.2.0 |
||
.1.3.6.1.4.1.25506.2.90.4 |
||
.1.3.6.1.4.1.25506.2.90.4.1 |
||
.1.3.6.1.4.1.25506.2.90.4.2 |
Dependencies (6) 4 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- RFC1155-SMIrfc
- HH3C-OID-MIBhh3c
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- INET-ADDRESS-MIBrfc
- SNMPv2-CONFrfc
- HH3C-NET-MAN-MIBhh3cselected
Conformance Groups (2)
|
A collection of objects in net management monitor group.
|
.1.3.6.1.4.1.25506.2.90.4.2.1
|
|
|
A collection of objects in net management notification group.
|
.1.3.6.1.4.1.25506.2.90.4.2.2
|
Compliance Statements (1)
OID
.1.3.6.1.4.1.25506.2.90.4.1.1The statement of compliance for those implementing
the network management MIB.
the network management MIB.
Required groups
| mandatory | hh3cNMMonitorGroup | |
| mandatory | hh3cNMNotificationGroup |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.25506.2.90.3.2.0.1 |
This notification will be generated when the IP address of active
management interface is changed. The change maybe originate from NMS, DHCP server or administrator. The management interfaces are the interfaces that assigned by administrator, which can be used to manage device, but may be inactive for link fault or IP address (IPv4 or IPv6) missing. The active management interface means an active interface, the IP address of which can be used for network management. This notification announces useful management IP address change. So it is triggered by significative IP address change. Suppose that two management interfaces on a device, Interface-A and Interface-B. Initially both interfaces are down and assigned no IP address. Configure Interface-A as the primary monitored interface, Interface-B as the secondary. Significative IP address change in following cases: 1. If Interface-A is assigned an IP address primarily, and it is linking up, then Interface-B will be ignored. A notification will be triggered, appending IP address of Interface-A. 2. If Interface-B is assigned an IP address primarily, and it is linking up, then Interface-A will be ignored. A notification will be triggered, appending IP address of Interface-B. 3. If IP address of that interface, which had its IP address announced to NMS, is changed since last notification triggered, then another notification will be sent to NMS. 4. Suppore that Interface-A was linked up and assigned an IP address primarily. If for some unknown reason, Interface-A is down or loses IP address, and Interface-B is assigned an IP address which is different with that announced to NMS before, then a notification will be triggered, appending the new IP address that Interface-B assigned. 5. A notification appending new IP address that Interface-A assigned will be triggered, if 4 occurs to Interface-B. |