CNR Log Messages

Table Of Contents

CNR Log Messages

Log Messages

CNR Log Messages

This module describes the log messages written to the CNR Log.

Log Messages

The following messages are displayed during the LEG startup procedure. (This message is logged every time the DHCP server is restarted):

•"CNR LEG: init entry called - starting initialization" - CNR LEG initialization was called

•"CNR LEG: finished initialization successfully"

The following messages are displayed - containing the configuration or default parameters - at initialization:

•"CNR LEG: thread priority =<integer value>"

•"CNR LEG: buffer size =<integer value>"

•"CNR LEG: reconnect timeout =<integer value>"

•"CNR LEG: encoding =<encoding>"

•"CNR LEG: KA duration =<integer value>"

•"CNR LEG: session timeout =<integer value>"

•"CNR LEG: debug mode on =<integer value>"

•"CNR LEG: trace level =<integer value>"

•"CNR LEG: lease time option =<integer value>"

•"CNR LEG: SM port =<integer value>"

•"CNR LEG: SM IP =<IP address>"

•"CNR LEG: report errors on =<integer value>"

•"CNR LEG: CM as Subscriber =<integer value>"

•"CNR LEG: Attack-Filter on =<integer value>"

•"CNR LEG: Attack threshold <integer value>sec"

•"CNR LEG: Filter entries =<integer value>"

•"CNR LEG: Log filter every <integer value>attacks"

•"CNR LEG: DEBUG MODE ON - enabling trace level <trace level>"

The following messages are displayed if there is a configuration error:

•"CNR LEG: the file <filename>was not found" - configuration file was not found, you must fix the configuration or move the file to the correct location.

•"CNR LEG: no SM IP address in the configuration file - aborting" - the SM IP address is the only parameter that is required in the configurtion file.

•"CNR LEG: invalid Attack Filter configuration parameters must be positive"

•"CNR LEG: unable to initialize the PRPC client - aborting"

The following messages are displayed every time the DHCP server is stopped:

•"CNR LEG: init entry called - starting un-initialization"

•"CNR LEG: finished uninitialization successfully"

The following messages are displayed when triggered by the attack filter:

•"CNR LEG: Identified attack start of CM <name>, IP <IP address>- filtering (total attacks - <number of attacks>)" - logged at detection of the attack. 'total attacks' refers to the total number of attacks detected from all devices by this LEG.

•"CNR LEG: Identified attack number <attack number>of CM <name>, IP <IP address>- filtering (total attacks - <number of attacks>)" - logged every 100 sequential attack-packets of a certain device.

The following messages are displayed in response to a device login or a renewal failure:

•"CNR LEG: failed to extend lease IP <IP address>- probably buffer overflow" - logged in CM as subscriber mode when the request does not contain option 82

•"CNR LEG: CPE Login - failed to login CM <name>, IP <IP address>- probably buffer overflow" - logged in CM as subscriber mode when the request contains option 82

•"CNR LEG: CM Login - failed to login CM <name>, IP <IP address>- probably buffer overflow" - logged in CPE as subscriber mode

•"CNR LEG: CPE Login - failed to login CPE <name>, IP <IP address>- probably buffer overflow" - logged in CPE as subscriber mode

The following messages are displayed in response to device logout failures:

•"CNR LEG: CPE Logout - failed to logout IP <IP address>- probably buffer overflow" - logged in CM as subscriber mode when the request does not contain option 82

•"CNR LEG: CPE Logout - failed to logout CM <name>, IP <IP address>- probably buffer overflow" - logged in CM as subscriber mode when the request contains option 82

•"CNR LEG: CM Logout - failed to logout CM <name>, IP <IP address>- probably buffer overflow" - logged in CPE as subscriber mode

•"CNR LEG: CPE Logout - failed to logout CPE <name>, IP <IP address>- probably buffer overflow" - logged in CPE as subscriber mode