Reference record for OID 1.3.6.1.4.1.11.2.14.11.15.2.90.3.2.0.1

Parent
1.3.6.1.4.1.11.2.14.11.15.2.90.3.2.0 (hpnicfNMNotifyObjectsPrefix)
Node code
1
Node name
hpnicfIpAddrChangeNotify
Numeric OID
1.3.6.1.4.1.11.2.14.11.15.2.90.3.2.0.1
URN notation
urn:oid:1.3.6.1.4.1.11.2.14.11.15.2.90.3.2.0.1
ASN.1 notation

{1 3 6 1 4 1 11 2 14 11 15 2 90 3 2 0 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfNetMan(90) hpnicfNMNotify(3) hpnicfNMNotifyObjects(2) hpnicfNMNotifyObjectsPrefix(0) hpnicfIpAddrChangeNotify(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/11/2/14/11/15/2/90/3/2/0/1
  • /ISO/Identified-Organization/6/1/4/1/11/2/14/11/15/2/90/3/2/0/1
  • /ISO/3/6/1/4/1/11/2/14/11/15/2/90/3/2/0/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfNetMan/hpnicfNMNotify/hpnicfNMNotifyObjects/hpnicfNMNotifyObjectsPrefix/hpnicfIpAddrChangeNotify
  • Additional combinations skipped.

Descriptions

hpnicfIpAddrChangeNotify — HPE networking MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies

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.

Source records

hpnicfIpAddrChangeNotify

Status in source: current.

Names: hpnicfIpAddrChangeNotify

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "hpnicfIpAddrChangeNotify",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "hpnicfNMIpAddressType",
    ",",
    "hpnicfNMIpAddress",
    ",",
    "hpnicfNMCustomBuildInfo",
    ",",
    "hpnicfNMSerialNum",
    "}",
    "STATUS",
    "current",
    "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.\"",
    "::=",
    "{",
    "hpnicfNMNotifyObjectsPrefix",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "hpnicfNMIpAddressType",
        "hpnicfNMIpAddress",
        "hpnicfNMCustomBuildInfo",
        "hpnicfNMSerialNum"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "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."
    ],
    null
  ]
}
  • HPE networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. HPE networking support.

    Module: HPN-ICF-NET-MAN-MIB

    Published definition
    hpnicfIpAddrChangeNotify NOTIFICATION-TYPE
        OBJECTS
            {
                hpnicfNMIpAddressType,
                hpnicfNMIpAddress,
                hpnicfNMCustomBuildInfo,
                hpnicfNMSerialNum
            }
        STATUS      current
        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."
    
        ::= { hpnicfNMNotifyObjectsPrefix 1 }
    Module imports
    {'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'HPN-ICF-OID-MIB': ['hpnicfCommon'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}

    Related source files and packages:


    Source location: HPN-ICF-NET-MAN-MIB::hpnicfIpAddrChangeNotify.
    Source version and references

    Downloaded: 2026-10-23T19:25:41.317274+00:00.

  • Netdisco MIB archive copies · Publisher's source file: hpnicfNetMan.mib

    Vendor MIB copy from the Netdisco archive.

    Module: HPN-ICF-NET-MAN-MIB

    Published definition
    hpnicfIpAddrChangeNotify NOTIFICATION-TYPE
        OBJECTS
            {
                hpnicfNMIpAddressType,
                hpnicfNMIpAddress,
                hpnicfNMCustomBuildInfo,
                hpnicfNMSerialNum
            }
        STATUS      current
        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."
    
        ::= { hpnicfNMNotifyObjectsPrefix 1 }
    Module imports
    {'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'HPN-ICF-OID-MIB': ['hpnicfCommon'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}
    · Archived source file

    Related source files and packages:


    Source location: HPN-ICF-NET-MAN-MIB::hpnicfIpAddrChangeNotify.
    Source version and references

    Downloaded: 2026-10-24T15:28:10.553993+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.11)

Peterson Tyler