All MIBs › HH3C-NET-MAN-MIB › hh3cIpAddrChangeNotify
hh3cIpAddrChangeNotify
Module: HH3C-NET-MAN-MIB
OID (symbolic): HH3C-NET-MAN-MIB::hh3cIpAddrChangeNotify
OID (numeric): 1.3.6.1.4.1.25506.2.90.3.2.0.1
Node type: NOTIFICATION-TYPE
Description: 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.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' HH3C-NET-MAN-MIB::hh3cIpAddrChangeNotify snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.25506.2.90.3.2.0.1
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:52291->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (132246595) 15 days, 7:21:05.95 SNMPv2-MIB::snmpTrapOID.0 = OID: HH3C-NET-MAN-MIB::hh3cIpAddrChangeNotify
Start monitoring H3C routers and switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-NET-MAN-MIB::hh3cIpAddrChangeNotify OID value, configure state conditions and alerts, and monitor any H3C routers and switches from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.25506 | hh3c | HH3C-OID-MIB |
| 1.3.6.1.4.1.25506.2 | hh3cCommon | HH3C-OID-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.25506.2.90 | hh3cNetMan | HH3C-NET-MAN-MIB |
| 1.3.6.1.4.1.25506.2.90.3 | hh3cNMNotify | HH3C-NET-MAN-MIB |
| 1.3.6.1.4.1.25506.2.90.3.2 | hh3cNMNotifyObjects | HH3C-NET-MAN-MIB |
| 1.3.6.1.4.1.25506.2.90.3.2.0 | hh3cNMNotifyObjectsPrefix | HH3C-NET-MAN-MIB |
| 1.3.6.1.4.1.25506.2.90.3.2.0.1 | hh3cIpAddrChangeNotify | HH3C-NET-MAN-MIB |