H3C-NET-MAN-MIB
- Registered at
- 1.3.6.1.4.1.2011.10.2.90
- Last updated
- 2008-04-16 17:00
- Organization
- Hangzhou H3C Technologies Co., Ltd.
- Revisions
- 2008-04-16 17:00
- Namespace
- huawei
- Source file
H3C-NET-MAN-MIB- Digest
sha256:6f05696dc0af2b1fb298f3a9588b0898f8330a2c5a5de41f94b958891586ba32
Description
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.
Contact
Platform Team H3C Technologies Co., Ltd. Hai-Dian District Beijing P.R. China Http://www.h3c.com Zip: 100085
Imports
| From | Symbols |
|---|---|
| HUAWEI-3COM-OID-MIB | h3cCommon |
| INET-ADDRESS-MIB | InetAddress, InetAddressType |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
H3C-NET-MAN-MIB HUAWEI-3COM-OID-MIB INET-ADDRESS-MIB SNMPv2-CONF SNMPv2-SMI SNMPv2-TC
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| h3cNMConfigObjects OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.1 | |||
| h3cNMMonitorObjects OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.2 | |||
| h3cNMNotify OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.3 | |||
| h3cNMNotifyScalarObjects OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.3.1 | |||
| h3cNMIpAddressType OBJECT-TYPE The IP address type of specified interface on the device. | 1.3.6.1.4.1.2011.10.2.90.3.1.1 | InetAddressType | accessible-for-notify | current |
| h3cNMIpAddress OBJECT-TYPE The IP address of specified interface on the device. | 1.3.6.1.4.1.2011.10.2.90.3.1.2 | InetAddress | accessible-for-notify | current |
| h3cNMCustomBuildInfo OBJECT-TYPE The customer-required information of devices, for example, OUI (Organizational Unique Identifier). | 1.3.6.1.4.1.2011.10.2.90.3.1.3 | OCTET STRING (SIZE(0..64)) | read-only | current |
| h3cNMSerialNum OBJECT-TYPE The serial number used by NMS (Network Management Station) for mapping IP address and device. | 1.3.6.1.4.1.2011.10.2.90.3.1.4 | OCTET STRING (SIZE(0..64)) | accessible-for-notify | current |
| h3cNMNotifyObjects OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.3.2 | |||
| h3cNMNotifyObjectsPrefix OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.3.2.0 | |||
| h3cNetManConformance OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.4 | |||
| h3cNetManCompliances OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.4.1 | |||
| h3cNetManGroups OBJECT-IDENTITY | 1.3.6.1.4.1.2011.10.2.90.4.2 |
Notifications
| Name | OID | Status |
|---|---|---|
| h3cIpAddrChangeNotify NOTIFICATION-TYPE 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. | 1.3.6.1.4.1.2011.10.2.90.3.2.0.1 | current |
Conformance
| Name | OID | Status |
|---|---|---|
| h3cNetManCompliance MODULE-COMPLIANCE The statement of compliance for those implementing the network management MIB. | 1.3.6.1.4.1.2011.10.2.90.4.1.1 | current |
| h3cNMMonitorGroup OBJECT-GROUP A collection of objects in net management monitor group. | 1.3.6.1.4.1.2011.10.2.90.4.2.1 | current |
| h3cNMNotificationGroup NOTIFICATION-GROUP A collection of objects in net management notification group. | 1.3.6.1.4.1.2011.10.2.90.4.2.2 | current |