This profile displays the event Log status of the items related to each Event Log type.
On SBC main screen, go to Administration > Accounting and Logs > Event Log > Type Status. The Type Status window is displayed.
By default only ten entries are displayed in a view. You can choose the number of entries to be displayed under the Show entries drop down box.
The following fields are displayed:
Parameter | Description |
---|---|
| Specifies the type of the event log. Each type has separate configuration parameters and logs to a separate file. |
| Specifies the filename that is currently being used for logging. No name is displayed when disk logging is disabled. The name RECOVERING is displayed when an attempt to automatically restart disk logging is in progress. |
| Specifies the count of the number of event records written to the current event log file. |
| Specifies the count of the number of bytes written to the current event log file. |
| Specifies the count of the number of log files of this event type. |
| Specifies the count of the number of bytes written to the log files of this event type. |
| Specifies the count of the number of event records dropped when writing to an Event Log file. |
| Specifies the time in minutes left before next rollover. |
| Identifies the location where this Event Log type writes to. |
| Specifies the time of the last event record dropped when writing to an Event Log file. The value will be zero length if no records have been dropped since last reboot. |
Info Level Logging Disabled | If set to True, the info level messages gets dropped as the system was once congested. The active and standby SBC are designed to turn off info level logging if the system becomes congested. The Execute this command only when system congestion dissipates. The system may become further congested if this command is executed while the system is still congested. |
When NP 0 error counter messages are received in the DBG logs, the Ethernet Switch configuration (Datalink Device L2) is checked. If the Switch is overloaded with traffic,
Every Switch vendor has their own command to display the drop counts. Therefore, the respective document must be checked to check the drop counts.