OID reference

h3cIpAddrChangeNotify

1.3.6.1.4.1.43.45.1.10.2.90.3.2.0.1

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…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.90.3.2.0 (h3cNMNotifyObjectsPrefix)
Node code
1
Node name
h3cIpAddrChangeNotify
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.90.3.2.0.1
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.90.3.2.0.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 90 3 2 0 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cNetMan(90) h3cNMNotify(3) h3cNMNotifyObjects(2) h3cNMNotifyObjectsPrefix(0) h3cIpAddrChangeNotify(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/90/3/2/0/1
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/90/3/2/0/1
  • /ISO/3/6/1/4/1/43/45/1/10/2/90/3/2/0/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cNetMan/h3cNMNotify/h3cNMNotifyObjects/h3cNMNotifyObjectsPrefix/h3cIpAddrChangeNotify
  • Additional combinations skipped.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cIpAddrChangeNotify · current

h3cIpAddrChangeNotify NOTIFICATION-TYPE
    OBJECTS
        {
            h3cNMIpAddressType,
            h3cNMIpAddress,
            h3cNMCustomBuildInfo,
            h3cNMSerialNum
        }
    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."

    ::= { h3cNMNotifyObjectsPrefix 1 }

h3cIpAddrChangeNotify · current

h3cIpAddrChangeNotify NOTIFICATION-TYPE
    OBJECTS
        {
            h3cNMIpAddressType,
            h3cNMIpAddress,
            h3cNMCustomBuildInfo,
            h3cNMSerialNum
        }
    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."

    ::= { h3cNMNotifyObjectsPrefix 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cIpAddrChangeNotify · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cIpAddrChangeNotify

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "h3cIpAddrChangeNotify",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "h3cNMIpAddressType",
    ",",
    "h3cNMIpAddress",
    ",",
    "h3cNMCustomBuildInfo",
    ",",
    "h3cNMSerialNum",
    "}",
    "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.\"",
    "::=",
    "{",
    "h3cNMNotifyObjectsPrefix",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "h3cNMIpAddressType",
        "h3cNMIpAddress",
        "h3cNMCustomBuildInfo",
        "h3cNMSerialNum"
      ]
    ],
    [
      "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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel