History Control Entry
RMON can be used to create a record of network utilization, packet types, errors and collisions. You need a historical record of activity to track down intermittent problems. Historical data can also be used to establish normal baseline activity, which may reveal problems associated with high traffic levels, broadcast storms, or other unusual events. Historical information can also be used to predict network growth and plan for expansion before your network becomes too overloaded. Select “History” then “History Control Entry” to display the collection items defined in the history control table.
Item | Description |
History Index | An index that uniquely identifies an entry in the History Control |
| table. Each such entry defines a set of samples at a particular |
| interval for an interface on the device. |
Data Source | MIB variable that is being monitored: |
| 1.3.6.1.2.1.2.2.1.1.1 - Agent board 100 Mbps interface |
| 1.3.6.1.2.1.2.2.1.1.2 - Agent board 10 Mbps interface |
| 1.3.6.1.2.1.2.2.1.1.3 - Serial port for |
| 1.3.6.1.2.1.2.2.1.1.4 - 100 Mbps stack backplane |
| 1.3.6.1.2.1.2.2.1.1.5 - 10 Mbps stack backplane |
| 1.3.6.1.2.1.2.2.1.1.6 - Stack Unit 1 100 Mbps segment |
| 1.3.6.1.2.1.2.2.1.1.7 - Stack Unit 1 10 Mbps segment |
| ... |
| 1.3.6.1.2.1.2.2.1.1.16 - Stack Unit 6 100 Mbps segment |
| 1.3.6.1.2.1.2.2.1.1.17 - Stack Unit 6 10 Mbps segment |
Buckets Requested | Requested number of discrete time intervals over which data is |
| to be saved in the part of the |
| with this entry. |
Buckets Granted | Number of discrete sampling intervals over which data shall |
| actually be saved in the part of the |
| associated with this entry. |
Interval | Interval in seconds over which the data is sampled for each |
| bucket in the part of the |
| this entry. |
Owner | Person who added this entry to the control table. |
Status | Indicates if this control entry has been set to valid or invalid. |
|
|
78 |
