Extreme Networks Summit WM Technical Reference Manual page 191

Table 44: CDR_COLLECTOR (23) logs and events (Continued)
Log ID Log Message
Fail to receive
cdr_config_notify.
Fail to receive stats bundle
notify.
Fail to receive authenticated
userid from security manager.
Client MAC:%s User-ID:%s:
has invalid IP address
[0.0.0.0]. Failed to create
CDR.
Fail to receive message
get_params_resp:%d
Fail to receive message
mu_deregister_notify:%d
Fail to receive message
smt_shutdown_component_req:
%d
Fail to receive message
es_log_lvl_update_notify:%d
Info
65 New CDR file has been
created.
66 Created a new CDR record with
session id%d.
67 CDR record was written to file
with session id%d.
68 CDR Manager started normally.
Summit WM Technical Reference Guide, Software Version 5.1
Comment
Possible issue with
configuration of CDR/
Accounting sub-system. Can
result in lack of accounting
reporting/CDR for system
users. Doesn't affect users
state, however, it doesn't allow
owner to provide proper billing
for services rendered.
Internal operation error.One
update snapshot is missed.
Possible impact to CDR/
Accounting state. Subsequent
updates should remedy the
situation.
Internal operation error.
Specific CDR record may not
be consistent. Tracking CDR is
harder without username
property.
User records are not tracked
until user obtains proper IP
address. Verify that users are
able to obtain proper addresses
from WM-AD.
Internal operation error.
Specific CDR record may not
be consistent.
Internal operation issue.
Specific CDR may not be
consistent. User termination
time may not be properly
adjusted.
System shutdown operation
under admin control (enable/
disable feature, system
shutdown).
Internal communications issue.
Unable to determine proper
logging level for component.
Accounting state
Accounting state
Accounting state
Accounting sub-system state
Action
Validate configuration of CDR/
Accounting settings for Radius
Server and WM-AD definitions.
If problem persists contact
Technical Support to
investigate.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
If problem persists Contact
Technical Support for
investigation.
191