Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-ENTITY-MIB | 45.56 KB |
ENTITY-MIB
About this MIB
Use this MIB to manage types of physical entities in a device in a tree structure and relationships between these physical entities. Through this MIB, you can obtain the relationship structure between the physical entities on the device and the related data and status of the physical entities.
An entry index in entPhysicalTable is referred to as an entity index, which is assigned by the product. Each entity uniquely identifies a hardware option on the device, such as fans, power supplies, memory modules, CPUs, service modules, and ports.
A network manager obtains the physical entity arrangement and inclusion relationship on the device by calculating the instance values of entPhysicalContainedIn and entPhysicalParentRelPos in the entPhysicalTable. Doing so can avoid assigning physical entity indexes in depth-first or breadth-first order.
RFC 4133 obsoletes RFC 2737, and adds support for the CPU entity type.
This MIB also contains notifications about configuration changes.
MIB file name
rfc4133-entity.mib
Notifications
entConfigChange
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.2.1.47.2.0.1 |
The value of entLastChangeTime changed |
Informational |
Major |
N/A |
ON |
Notification triggers
This notification is generated when a hardware entity on the device, including cards, subcards, power supplies, fans, or storage controllers, is installed, removed, reset, or registered. It can be utilized by an NMS to trigger logical or 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).
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.
An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events.
System impact
Removal of a hardware entity might affect correct operation of the system.
Status control
This notification cannot be disabled.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.145.2.3.1.1 (hh3cLicenseFeatureName) |
Name of a licensed feature. |
hh3cLicensePhysicalIndex hh3cLicenseFeatureName |
SnmpAdminString |
OCTET STRING (SIZE (1..31)) |
|
1.3.6.1.4.1.25506.2.145.2.3.1.2 (hh3cLicenseFeatureState) |
Licensing state of the feature. |
hh3cLicensePhysicalIndex hh3cLicenseFeatureName |
INTEGER |
notLicensed(1), trialLicense(2), formalLicense(3) |
|
1.3.6.1.4.1.25506.2.145.3.1.1 (hh3cLicenseBindValidityPeriodRemaining) |
Remaining days before the license expires. |
N/A |
Unsigned32 |
Standard MIB values. |
Recommended action
To resolve the issue:
1. Verify that the entity is operating correctly.
2. If this alarm is caused by an acknowledged manual operation, no action is required.
