Each connectivity unit has its own event buffer.
As it wraps, it may write over previous events.
This object is an index into the buffer.
It is recommended that this table be read using
'getNext's to retrieve the initial table.
The management application should read the event
table at periodic intervals and then determine if
any new entries were added by comparing the last
known index value with the current highest index
value. The management application should then update
its copy of the event table. If the read interval is
too long, it is possible that there may be events
that may not be contained in the agent's internal
event buffer. For example, an agent may read events
50-75. At the next read interval, fcConnUnitEventCurrID
is 189. If the management app tries to read event index
76, and the agent's internal buffer is 100 entries max,
event index 76 will no longer be available.
The index value is an incrementing integer starting
from one every time there is a table reset. On table
reset, all contents are emptied and all indeces are set
to zero. When an event is added to the table, the event
is assigned the next higher integer value than the last
item entered into the table. If the index value reaches
its maximum value, the next item entered will cause the
index value to roll over and start at one again.
Parsed from file fcmgmt_efcm.mib.txt
Company: emc
Module: mcdata_31
fcConnUnitEventIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Each connectivity unit has its own event buffer. As it wraps, it may write over previous events. This object is an index into the buffer. It is recommended that this table be read using 'getNext's to retrieve the initial table. The management application should read the event table at periodic intervals and then determine if any new entries were added by comparing the last known index value with the current highest index value. The management application should then update its copy of the event table. If the read interval is too long, it is possible that there may be events that may not be contained in the agent's internal event buffer. For example, an agent may read events 50-75. At the next read interval, fcConnUnitEventCurrID is 189. If the management app tries to read event index 76, and the agent's internal buffer is 100 entries max, event index 76 will no longer be available. The index value is an incrementing integer starting from one every time there is a table reset. On table reset, all contents are emptied and all indeces are set to zero. When an event is added to the table, the event is assigned the next higher integer value than the last item entered into the table. If the index value reaches its maximum value, the next item entered will cause the index value to roll over and start at one again." ::= { fcConnUnitEventEntry 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.8888.1.1.7.1.2 | fcConnUnitREventTime | 0 | 0 | This is the real time when the event occurred. It has the following format. DDMMYYYY HHMMSS DD=day number MM=month number YYYY=year … |
| 1.3.6.1.2.1.8888.1.1.7.1.3 | fcConnUnitSEventTime | 0 | 0 | This is the sysuptime timestamp when the event occurred. |
| 1.3.6.1.2.1.8888.1.1.7.1.4 | fcConnUnitEventSeverity | 0 | 0 | The event severity level. |
| 1.3.6.1.2.1.8888.1.1.7.1.5 | fcConnUnitEventType | 0 | 0 | The type of this event. |
| 1.3.6.1.2.1.8888.1.1.7.1.6 | fcConnUnitEventObject | 0 | 0 | This is used with the fcConnUnitEventType to identify which object the event refers to. It can be the OID of a connectivity unit… |
| 1.3.6.1.2.1.8888.1.1.7.1.7 | fcConnUnitEventDescr | 0 | 0 | The description of the event. |