Table of Contents
Advertisement
cable logging badipsource
To create a separate log for these error messages, use the cable logging badipsource command. You can
also specify the size of the buffer that will contain these error messages. When the buffer becomes full,
the oldest messages are deleted to make room for newer messages, so choose a buffer size that will allow
you to retain all messages until you can examine them.
On the Cisco uBR10012 router, this command includes only the BADIPSOURCE error messages
generated by the PRE module. The cable interface line cards also generate their own error messages, but
because these error messages are typically duplicates of the ones generated by the PRE module, they are
not included in the separate log.
If you find that the current buffer is too small to contain the current volume of error log messages, you
Tip
can issue this command again with a larger buffer size. However, doing so will automatically clear out
all messages currently in the buffer, so be certain that you have viewed all of the current messages before
giving a second cable logging badipsource command.
Be cautious when specifying the buffer size, because the Cisco CMTS could run out of memory for other
Note
tasks. Use the show memory EXEC command to display the maximum available processor memory,
and set the buffer size for this command to a value well within that maximum value.
To display the contents of this error log, use the
you have viewed the error messages, use the
timestamps log command to add a timestamp to the messages in the log.
To print the BADIPSOURCE messages to the console or syslog server, use the no cable logging
badipsource command (which is the default configuration). Note that this configuration does not turn
off the generation of BADIPSOURCE messages, but only configures the system for the default log
message behavior.
If you do not want to see any BADIPSOURCE messages at all, use the cable logging badipsource 4096
Tip
command so that these messages go to a separate buffer with the smallest possible size. You will then
not see these error messages unless you explicitly use the
Examples
The following example shows how to enable the logging of bad IP source address error messages, using
a buffer size of 524,288 bytes (512 KB):
Router# configure terminal
Router(config)# cable logging badipsource 524288
Router(config)#
You must also use the
Tip
the buffer will contain any error messages about bad IP source addresses. If you do not use the
source-verify
but the buffer will always remain empty.
The following example shows how to enlarge the current buffer for bad IP source address error messages
by giving the cable logging badipsource command a second time. Because this will empty out the buffer
of all current messages, be sure to display the current buffer contents before giving the command a
second time.
Router# configure terminal
Cisco Broadband Cable Command Reference Guide
2-144
cable source-verify
command, you can still use the cable logging badipsource command to create a buffer,
Chapter 2
show cable logging
clear cable logging
command. You can also use the service
show cable logging
command to enable verification of source IP addresses before
Cisco CMTS Configuration Commands
command. To clear the buffer after
command to display them.
OL-1581-08
cable
Advertisement
Table of Contents
