entConfigChange — Huawei official enterprise MIB Query and object descriptions
An entity is changed.
{1 3 6 1 2 1 47 2 0 1}
Descriptions may differ between sources. The primary description is shown first.
Source file: Download ENTITY-MIB.mib
Publisher path: Mibs; 60,728 bytes
Source file: Download ENTITY-MIB.txt · Publisher's file
Copy from Netdisco; File: rfc/ENTITY-MIB.txt; 65,951 bytes
Vendor MIB copy from the Netdisco archive.
Related source files and packages:
Source file: Download ENTITY-MIB · Publisher's file
Copy from LibreNMS; 65,951 bytes
Vendor MIB copy from the LibreNMS archive.
Related source files and packages:
Source file: Download ENTITY-MIB.my · Publisher's file
S3200 Series Switches SNMP MIB Files; Models: S3200-8MG4S, S3200-8MG4S-U; Catalog updated: 2025-11-24 18:13:56; File: S3200 Series Switches SNMP MIB Files/ENTITY-MIB.my; Publisher path: mall/resource/s3200-series-switches-snmp-mib-files.zip; 59,499 bytes
Related source files and packages:
Source file: Download rfc4133-entity.mib · Publisher's file
IES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: FS_MIB/rfc4133-entity.mib; Publisher path: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; 59,144 bytes
Related source files and packages:
tsn3220-10s-u-switch-snmp-mib-files.zip
tsn3220-10s-switch-snmp-mib-files.zip
Source file: Download ENTITY-MIB.txt · Publisher's file
IES3110-8TFP-R Switch SNMP MIB Files; Models: IES3110-8TFP-R; Catalog updated: 2026-01-15 17:50:02; File: FSMIB/ENTITY-MIB.txt; Publisher path: mall/resource/ies3110-8tfp-r-switch-snmp-mib-files.zip; 59,262 bytes
Related source files and packages:
Source file: Download ENTITY-MIB-2737.mib · Publisher's file
S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0); Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:39:45; File: S3910-24TS and S3910-48TS Switches SNMP MIB Files/S3910 Series-standard.zip!standard/ENTITY-MIB-2737.mib; Publisher path: mall/doc/2024012909344598z6fl.zip; 52,607 bytes
Related source files and packages:
s3100-16tf-switch-snmp-mib-files.zip
s5860-series-swithes-snmp-mib-files.zip
Source file: Download stdent.mib · Publisher's file
Firmware > Magnum 5RX_10RX > 5RX_10RX MIB 2018-12-31 17:02:37; Publisher path: partner/sfc/servlet.shepherd/document/download/069Qp00000ju6teIAA; 59,144 bytes
Related source files and packages:
Source file: Download ENTITY-MIB.txt · Publisher's file
Hi-SCOM 2023-01-12 01:45:32; File: Hi-SCOM_MIB_BN_V01/public/ENTITY-MIB.txt; Publisher path: partner/sfc/servlet.shepherd/document/download/069Qp00000jtUdAIAU; 59,262 bytes
Related source files and packages:
Source file: Download rfc2737.mib · Publisher's file
File: MS510TX_TXPP MIBS_V6.7.0.43/rfc2737.mib; Publisher path: files/GDC/MS510TX/MS510TX_TXPP_MIBS_V6.7.0.43.zip; 54,464 bytes
Related source files and packages:
Source file: Download RFC2737 - Entity MIB (V2).mib · Publisher's file
File: GS724TPv2 MIB V1.1.1.29/RFC2737 - Entity MIB (V2).mib; Publisher path: files/GDC/GS724TPv2/GS724TPv2 MIB V1.1.1.29.zip; 53,884 bytes
Related source files and packages:
Source file: Download ENTITY-MIB.mib.txt
File: vmware/ENTITY-MIB.mib.txt; 59,268 bytes
Source file: Download rfc2737.mib.txt
File: ruijie/rfc2737.mib.txt; 52,607 bytes
Source file: Download ENTITY-MIB.txt
File: riverstone/ENTITY-MIB.txt; 54,086 bytes
Source file: Download ENTITY-MIB.txt
File: rittal/ENTITY-MIB.txt; 59,229 bytes
Source file: Download rfc2737.mib.txt
File: paradyne/rfc2737.mib.txt; 53,936 bytes
Source file: Download rfc4133-Entity-MIB-Version-3.mib.txt
File: ietf_rfcs/rfc4133-Entity-MIB-Version-3.mib.txt; 60,902 bytes
Source file: Download rfc2737-Entity-Version-2.mib.txt
File: ietf_rfcs/rfc2737-Entity-Version-2.mib.txt; 54,279 bytes
Source file: Download rfc2737-entity.mib.txt
File: huawei/rfc2737-entity.mib.txt; 54,205 bytes
Source file: Download ENTITY-MIB.mib.txt
File: huawei/ENTITY-MIB.mib.txt; 57,235 bytes
Source file: Download rfc2737.mib.txt
File: hp/rfc2737.mib.txt; 53,838 bytes
An entity is changed.
This object indicates that an entity (either a board or a subcard) was inserted, pulled out, reset, or registered, which caused the change of MIB information.
An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events, e.g., due to throttling or transmission loss.
This notification is generated when anentity on the device, including cards, subcards, power supplies, fans, or storagecontrollers, is installed, removed, reset, or registered. It can be utilized byan NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than oneentConfigChange notification event in a given time interval (five seconds isthe suggested default). If additional configuration changes occurwithin the throttling period, then notification-events for these changes shouldbe suppressed by the agent until the current throttling period expires.An NMS should periodically check the valueof entLastChangeTime to detect any missed entConfigChange notification-events.
An entConfigChange trap is sent when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one entConfigChange 'trap-event' in a five second period, where a 'trap-event' is the transmission of a single trap PDU to a list of trap destinations. If additional configuration changes occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange trap-events, e.g. due to throttling or transmission loss.
This object indicates that an entity (either a board or a subcard) was inserted, pulled out, reset, or registered, which caused the change of MIB information.
Implementation notes: This object is implemented as defined in the corresponding MIB file.
A trap is sent by the device when the contents of the Entity-MIB change.
Status in source: unspecified.
Names: entConfigChange
{
"object_class": "notification",
"notification_varbinds": "None."
}Module: ENTITY-MIB
· Download Huawei MIB Query — ENTITY-MIB (derived data index)Related source files and packages:
Derived from the separately linked unchanged publisher JSON exports; this index is not a publisher original.; Publisher path: info-finder/tool/en/enterprise/mib; 2.4 MiB
Downloaded: 2026-10-24T18:37:19.967474+00:00.
Status in source: unspecified.
Names: entConfigChange
{
"syntax": "NA",
"object_class": "notification"
}Module: ENTITY-MIB
Related source files and packages:
Status in source: unspecified.
Names: entConfigChange
{
"smi_kind": "TRAP-TYPE",
"definition": [
"entConfigChange",
"TRAP-TYPE",
"ENTERPRISE",
"entityMIBTraps",
"DESCRIPTION",
"\"An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events, e.g., due to throttling or transmission loss.\"",
"::=",
"1"
],
"syntax_tree": [
[
"objectIdentifier",
[
"entityMIBTraps"
]
],
[],
[
"DESCRIPTION",
"An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events, e.g., due to throttling or transmission loss."
],
null
]
}Module: ENTITY-MIB
entConfigChange TRAP-TYPE
-- Reverse mappable trap
ENTERPRISE entityMIBTraps
-- Status
-- mandatory
DESCRIPTION
"An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling
period is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= 1{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC-v1': ['TDomain', 'TAddress', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI-v1': ['mib-2'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Downloaded: 2026-10-19T00:18:21.156892+00:00.
Module: ENTITY-MIB
entConfigChange TRAP-TYPE
-- Reverse mappable trap
ENTERPRISE entityMIBTraps
-- Status
-- mandatory
DESCRIPTION
"An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling
period is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= 1{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC-v1': ['TDomain', 'TAddress', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI-v1': ['mib-2'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Archived: 2026-10-19T00:22:08.646484+00:00.
Status in source: unspecified.
Names: entConfigChange
{
"object_class": "notification",
"notification_varbinds": "None"
}Module: ENTITY-MIB
Related source files and packages:
Status in source: unspecified.
Names: entConfigChange
{}Related source files and packages:
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 6425 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 2.5 MiB
Downloaded: 2026-10-24T09:35:56.808750+00:00.
Related source files and packages:
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 8522 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 3.4 MiB
Downloaded: 2026-10-24T09:35:59.374656+00:00.
Related source files and packages:
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 7435 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 2.9 MiB
Downloaded: 2026-10-24T09:36:02.325236+00:00.
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 6363 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 2.5 MiB
Downloaded: 2026-10-24T09:36:04.750933+00:00.
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 10000 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 3.9 MiB
Downloaded: 2026-10-24T09:36:07.223160+00:00.
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 4254 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 1.7 MiB
Downloaded: 2026-10-24T09:36:10.046756+00:00.
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 7026 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 2.8 MiB
Downloaded: 2026-10-24T09:36:12.697246+00:00.
Original H3C MIB Lookup object names, numeric OIDs and descriptions. 5526 published rows.; Publisher path: cn/BizPortal/QueryMIB/api.ashx; 2.2 MiB
Downloaded: 2026-10-24T09:36:18.856610+00:00.
Status in source: unspecified.
Names: entConfigChange
{
"smi_kind": "TRAP-TYPE",
"definition": [
"entConfigChange",
"TRAP-TYPE",
"ENTERPRISE",
"entityMIBTraps",
"DESCRIPTION",
"\"An entConfigChange trap is sent when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one entConfigChange 'trap-event' in a five second period, where a 'trap-event' is the transmission of a single trap PDU to a list of trap destinations. If additional configuration changes occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange trap-events, e.g. due to throttling or transmission loss.\"",
"::=",
"1"
],
"syntax_tree": [
[
"objectIdentifier",
[
"entityMIBTraps"
]
],
[],
[
"DESCRIPTION",
"An entConfigChange trap is sent when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one entConfigChange 'trap-event' in a five second period, where a 'trap-event' is the transmission of a single trap PDU to a list of trap destinations. If additional configuration changes occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange trap-events, e.g. due to throttling or transmission loss."
],
null
]
}Module: ENTITY-MIB
entConfigChange TRAP-TYPE
ENTERPRISE entityMIBTraps -- was entityMIBTrapPrefix
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= 1{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['TimeTicks'], 'RFC1213-MIB': ['DisplayString', 'mib-2']}Archived: 2026-10-19T00:22:11.179460+00:00.
Status in source: unspecified.
Names: entConfigChange
{
"syntax": "NA",
"object_class": "notification",
"implementation_notes": "This object is implemented as defined in the corresponding MIB file."
}Module: ENTITY-MIB
Related source files and packages:
Status in source: current.
Names: entConfigChange
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"entConfigChange",
"NOTIFICATION-TYPE",
"STATUS",
"current",
"DESCRIPTION",
"\"An entConfigChange trap is sent when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one entConfigChange 'trap-event' in a five second period, where a 'trap-event' is the transmission of a single trap PDU to a list of trap destinations. If additional configuration changes occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange trap-events, e.g. due to throttling or transmission loss.\"",
"::=",
"{",
"entityMIBTrapPrefix",
"1",
"}"
],
"syntax_tree": [
[],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An entConfigChange trap is sent when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one entConfigChange 'trap-event' in a five second period, where a 'trap-event' is the transmission of a single trap PDU to a list of trap destinations. If additional configuration changes occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange trap-events, e.g. due to throttling or transmission loss."
],
null
]
}Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Downloaded: 2026-10-19T00:18:21.757684+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Archived: 2026-10-19T00:22:07.114586+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Archived: 2026-10-19T00:22:08.911938+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Archived: 2026-10-19T00:22:09.240337+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Archived: 2026-10-19T00:22:09.557877+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE'], 'RFC1213-MIB': ['mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'SNMPv2-PARTY-MIB': ['TAddress']}Archived: 2026-10-19T00:22:09.964267+00:00.
Module: ENTITY-MIB
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
An agent must not generate more than one entConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations. If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of entLastChangeTime to detect
any missed entConfigChange trap-events, e.g. due to
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }{'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Archived: 2026-10-19T00:22:10.116981+00:00.
Status in source: unspecified.
Names: entConfigChange
{
"object_class": "notification",
"notification_varbinds": "None"
}Module: ENTITY-MIB
Related source files and packages:
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling
period is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= { entityMIBTrapPrefix 1 }
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling
period is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= { entityMIBTrapPrefix 1 }
entConfigChange NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling
period is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= { entityMIBTrapPrefix 1 }
Internet Assigned Numbers Authority
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.47.2.0.0 | 0 | 1 | 1 |