Hello!
DOCSIS 3.0 defines various DOCSIS events, such as authentication failure and CM certificate error events. Configuring DOCSIS event reporting helps you obtain MA5600T/MA5603T/MA5608T and CM running status.
Procedure
1. Run the cable event loghost ip command to set the IP address of a log host to which DOCSIS events are reported.
2. Run the cable event level report { localVolatile | trap | syslog } command to configure the mode and priority of reporting DOCSIS events.
The modes of reporting DOCSIS events include localVolatile, trap, and syslog.
localVolatile: indicates that the DOCSIS events are saved to MA5600T/MA5603T/MA5608T local logs but not to the buffer. The MA5600T/MA5603T/MA5608T does not save the DOCSIS events and clears them after being reset.
Configure the localVolatile mode before setting the mode of reporting DOCSIS events to trap or syslog.
trap: reports DOCSIS events to a log host, which is generally the U2000, as traps. After setting this mode, run the snmp-agent target-host trap-hostname command to configure the log host.
syslog: reports DOCSIS events to a log host as system logs, which are displayed after the log host software parses them.
The mode of reporting DOCSIS events varies depending on the priorities of the DOCSIS events.
Default mode of reporting DOCSIS events with emergency or alert priorities: localVolatile
Default mode of reporting DOCSIS events with critical, error, warning, or notice priorities: trap, syslog, and localVolatile
Default mode of reporting DOCSIS events with information or debugging priorities: not reported
3. (Optional) Run the cable cm-status event command to set parameters for a CM to report events.
I hope it will be helpful for you. Thank you!
