Chapter 41: Logging
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1035
Priority-Based Event Routing
Each event is assigned an event priority. The event priority indicates the type and impact of the event on the C4/c CMTS
operations.
Priority values range from 1 to 8. Each priority value is defined in the table below:
Table 122.
Event Priority Value Descriptions
Value
Name
Descriptions and Examples
1
Emergency
Unrecoverable and fatal C4/c CMTS hardware or software fault.
2
Alert
Recoverable and non-fatal hardware or software fault.
3
Critical
Service-affecting problem impacting the whole cable system.
4
Error
Service-degrading condition related to two or more Cable Modems.
5
Warning
Service-degrading condition related to a single subscriber.
6
Notice
Non-failure condition related to the C4/c CMTS itself.
7
Informational
Non-failure condition related to a subscriber.
8
Debug
Non-failure condition related to internal hardware or software state.
Event Routing Sequence
For the SNMP management station and Syslog server, event routing is based first on the priority and then throttle control.
For the history log, system console, and telnet sessions, the routing is based only on the priority associated with the event.
Caution: Logging of debug messages should be enabled only with assistance from ARRIS Technical Support. If enabled and
used improperly, the user could flood the system with event messages. This flood of messages could impair CPU
performance.