Cisco IOS XR System Error Message Reference Guide, Release 4.2.x
Subscriber Messages
Downloads: This chapterpdf (PDF - 500.0KB) The complete bookPDF (PDF - 68.41MB) | Feedback

Subscriber Messages

Table Of Contents

Subscriber Messages

ACCT_EA Messages

ACCT_MA Messages

COPP Messages

DATABASE Messages

IPSUB_EA Messages

ISLM Messages

PPPOE_EA Messages

PPPOE_GBL_CFG Messages

PPPOE_MA Messages

SUB_UTIL Messages

TMPL Messages

VPDN Messages


Subscriber Messages


This section contains subscriber related System Error Messages.

ACCT_EA Messages

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_EA-3-INIT Failed to initialize [chars], because of [chars]

Explanation    Initialization process such as getting an evm failed.

Recommended Action    sysmgr will retry to start the acct_ea. If not recovered, it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_EA-3-NOMEM ACCT EA failed to program '[chars]' due to low memory

Explanation    The ACCT EA process could not allocate memory needed to program some ACCT feature.

Recommended Action    Check memory status.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_EA-3-PLAT_UPD_FAILED Platform update failed: [chars] - [chars](CH[hex])

Explanation    Platform update failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_EA-3-PLAT_UPD_FAILED_GL Platform update failed for [dec] interface: [chars] - [chars]

Explanation    Platform update failed for all interfaces in a batch.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_EA-4-ERROR [chars]: [chars]

Explanation    There was an error with processing an event in the EA.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ACCT_MA Messages

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-ACCT_NOT_CONFIGURED Policy-map [chars] must have 'accounting aaa list' configured with idle timeout or prepaid commands.

Explanation    A policy-map containing prepaid and/or idle timeout commands must also contain an accounting command.

Recommended Action    Define a policy-map that contains an accounting command in addition to the prepaid or idle timeout command. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-BAD_MATCH_TYPE Policy-map [chars] has an unsupported class-map. Accounting policy-map support is limited to class-maps of type IPv4 ACL.

Explanation    An accounting policy-map must contain a class-map of type IPv4 ACL. This is the only supported match type.

Recommended Action    Define a policy-map that contains an IPv4 ACL class-map. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-CFG_UNDEFINED Prepaid configuration [chars] is not defined.

Explanation    The prepaid configuration name that was specified in the prepaid command has not been defined in the system.

Recommended Action    Define a prepaid configuration with the name used in the prepaid command or change the name in the command to an existing prepaid configuration. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-INIT Failed to initialize [chars], because of [chars]

Explanation    Initialization process such as getting an evm failed.

Recommended Action    sysmgr will retry to start the acct_ma process. If it cannot be restarted it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-MERGE_ERROR Merged and non-merged service-policies cannot be mixed in the same session.

Explanation    The merge keyword must be configured to combine same-direction service-polices from different dynamic-templates.

Recommended Action    Add the merge keyword to all service-policies that are to be combined. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-PLCYMAP_UNDEFINED Policy-map [chars] is not defined.

Explanation    The policy-map name that was configured in the service type dynamic-template has not been defined in the system.

Recommended Action    Define a policy-map with the name used in the service-policy command or change the name in the command to an existing policy-map. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-ACCT_MA-3-PREPAID_REQUEST_ERROR Prepaid session request error: [chars]

Explanation    There was a failure when starting a new prepaid session or requesting a new quota.

Recommended Action    Check all applicable configurations on the router and prepaid server. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

COPP Messages

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-3-BAD_ACTOR_INTF_NOT_CLEARED The platform failed to completely clear the 'penalty box' for interface [chars], [chars].

Explanation    The subscriber control plane policer failed to completely clear the hardware settings for the 'penalty box' for the specified bad actor. Traffic from this source MAC may be affected.

Recommended Action    If traffic from the interface is affected, try flapping the interface or reloading the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-3-BAD_ACTOR_MAC_NOT_CLEARED The platform failed to completely clear the 'penalty box' for source MAC address [chars] on interface [chars], [chars].

Explanation    The subscriber control plane policer failed to completely clear the hardware settings for the 'penalty box' for the specified bad actor. Traffic from this source MAC may be affected.

Recommended Action    If traffic from the source MAC is affected, try flapping the interface or reloading the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-3-DISABLED_DANGLING_BAD_ACTORS Subscriber Control Plane Policing has been disabled, but not all Bad Actors on this node were cleared: [chars]

Explanation    The Subscriber Control Plane Policer feature was disabled by configuration, but not all existing Bad Actors on this node were cleared. This may affect the creation of new subscriber sessions.

Recommended Action    Try clearing the bad actors manually, or reloading the line card. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-3-INIT Failed to initialize [chars], [chars].

Explanation    Initialization of SUBCOPP process failed to complete.

Recommended Action    sysmgr will try to restart the SUBCOPP process. If it cannot be restarted it is a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_INTF_CLEARED Interface [chars] cleared from penalty-policing by timeout.

Explanation    A subscriber interface that was previously flagged by the subscriber control plane policer has been removed from the 'penalty box.'

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_INTF_DELETED Interface [chars] deleted: cleared from penalty-policing.

Explanation    A subscriber interface that was previously flagged by the subscriber control plane policer has been deleted, and so the 'penalty box' for it has been cleared.

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_INTF_DETECTED Excessive [chars] flow detected on interface [chars]. The interface will be penalty-policed at [dec] pps for [dec] minutes.

Explanation    The subscriber control plane flow sampler detected a flow on a subscriber interface that exceeds the control packet policer rate. This could result in a denial of service to other subscribers. The interface will be placed in a 'penalty box' and policed at a much lower rate for a specified time period.

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_INTF_DISABLED Excessive [chars] flow detected on interface [chars]. Penalty-policing is disabled. No action taken.

Explanation    The subscriber control plane flow sampler detected a flow on a subscriber interface that exceeds the control packet policer rate. This could result in a denial of service to other subscribers. Penalty-policing has been disabled by configuration so the interface will not be placed in the 'penalty box.'

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_MAC_CLEARED Source MAC [chars] on interface [chars] cleared from penalty-policing by timeout.

Explanation    A source MAC address that was previously flagged by the subscriber control plane policer has been removed from the 'penalty box.'

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_MAC_DELETED Interface [chars] deleted: source MAC [chars] cleared from penalty-policing.

Explanation    A source MAC address that was previously flagged by the subscriber control plane policer has been removed from the 'penalty box' because the interface on which it was flagged has been deleted.

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_MAC_DETECTED Excessive [chars] flow detected from source MAC address [chars] on interface [chars]. Traffic from this MAC address will be dropped for [dec] minutes.

Explanation    The subscriber control plane flow sampler detected a flow from a source MAC address that exceeds the control packet policer rate. This could result in a denial of service to subscribers. All traffic from this source MAC address will be dropped for a specified time period.

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-COPP-4-BAD_ACTOR_MAC_DISABLED Excessive [chars] flow detected from source MAC address [chars] on interface [chars]. Penalty-policing is disabled. No action taken.

Explanation    The subscriber control plane flow sampler detected a flow from a source MAC address that exceeds the control packet policer rate. This could result in a denial of service to subscribers. Penalty-policing has been disabled by configuration so the interface will not be placed in the 'penalty box.'

Recommended Action    No action necessary. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

DATABASE Messages

Error Message     
 
    
    
   

%SUBSCRIBER-DATABASE-0-INIT_FAILURE Subscriber Database Manager was unable to initialize the [chars] module. Error: '[chars]'. Initialization will be tried again after 60 seconds.

Explanation    An error was encountered while initializing one of the critical modules of the configuration manager server. Without proper initialization of this module, configuration manager can not operate properly. Initialization will be retried every 60 seconds if required.

Recommended Action    Subscriber Database Manager is a critical component and must be operational in order to configure the router. Please note that if the probem is caused by a system resource shortage continued initilization of the module may repair the problem. If this error is seen more than 5 times, contact Cisco TAC support because a reboot of the node may be required.

Error Message     
 
    
    
   

%SUBSCRIBER-DATABASE-0-INIT_RETRY_SUCCEEDED Subscriber Database Manager succeeded in initializing the [chars] module upon retry.

Explanation    An error was previously encountered while initializing one of the critical modules of the configuration manager server. However, the initialization was retried and succeeded.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SUBSCRIBER-DATABASE-4-INIT_ERROR Subscriber Database Manager was unable to initialize the [chars] module. Error: '[chars]'. [chars].

Explanation    An error was encountered while initializing one of the modules of configuration manager server. The failure of this module initialization is not critical to configuration manager to be completely operational.

Recommended Action    Provide the message details to Cisco Support personal.

Error Message     
 
    
    
   

%SUBSCRIBER-DATABASE-4-TRACE [chars] Error:[chars]

Explanation    This is a non-fatal error and can happen when router is low on memory. It should not affect the functioning of the router, but trace messages may not be logged.

Recommended Action    None.

Error Message     
 
    
    
   

%SUBSCRIBER-DATABASE-7-INTERNAL [chars]

Explanation    An unexpected internal error occurred in the configuration subsystem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.

IPSUB_EA Messages

Error Message     
 
    
    
   

%SUBSCRIBER-IPSUB_EA-3-INIT Failed to initialize [chars], because of [chars]

Explanation    Initialization process such as getting an evm failed.

Recommended Action    sysmgr will retry to start the ipsub_ea. If not recovered, it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-IPSUB_EA-3-NOMEM IPSUB EA failed to program '[chars]' due to low memory

Explanation    The IPSUB EA process could not allocate memory needed to program some IPSUB feature.

Recommended Action    Check memory status.

Error Message     
 
    
    
   

%SUBSCRIBER-IPSUB_EA-3-PLAT_UPD_FAILED Platform update failed: [chars] - [chars](CH[hex])

Explanation    Platform update failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-IPSUB_EA-3-PLAT_UPD_FAILED_GL Platform update failed for [dec] interface: [chars] - [chars]

Explanation    Platform update failed for all interfaces in a batch.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-IPSUB_EA-4-ERROR [chars]: [chars]

Explanation    There was an error with processing an event in the EA.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ISLM Messages

Error Message     
 
    
    
   

%SUBSCRIBER-ISLM-4-CONFIGURED_SESSIONS_LIMIT No more sessions can be initiated. The number of configured sessions ([dec]) reached

Explanation    This syslog is printed when the number of sessions have reached the configured session limit. New sessions will not be allowed.

Recommended Action    Change the configuration and install more licenses or move a license from another line card.

Error Message     
 
    
    
   

%SUBSCRIBER-ISLM-4-ENTITLED_SESSIONS_EXCEEDED Reached the number of sessions ([dec]) allowed

Explanation    This syslog is printed when the number of sessions is over the limit of the licenses available.

Recommended Action    Install more licenses or move a license from another line card.

Error Message     
 
    
    
   

%SUBSCRIBER-ISLM-4-ENTITLED_SESSIONS_LIMIT No more sessions can be initiated. The number of entitled sessions ([dec]) has been reached

Explanation    This syslog is printed when the number of sessions has reached the limit of the licenses available. New sessions will not be allowed

Recommended Action    Install more licenses or move a license from another line card.

Error Message     
 
    
    
   

%SUBSCRIBER-ISLM-4-SESSION_THRESHOLD_EXCEEDED Session threshold of [dec] has been exceeded

Explanation    This syslog is printed when the configured session threshold has been exceeded.

Recommended Action    This is warning to alert the user that sessions may be near the limit that is configured or entitled.

PPPOE_EA Messages

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-4-ERR_EVC_ERROR Error resetting IMP connection: [chars]

Explanation    After detecting an error with the IMP connection, PPPoE EA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-4-ERR_EVM_EVENT_BLOCK Error encountered in the event loop: [chars]. The PPPoE EA process will restart

Explanation    An error occured in the event loop. The process will restart which should recover the situation.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-4-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The PPPoE EA process will restart

Explanation    A failure occured during the initialization of the process. The process will restart which should recover the situation.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-4-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes for '[chars]'

Explanation    The process failed to allocate memory for the specified resource.

Recommended Action    *REDUCE*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-4-ERR_RWMGR Unexpected error whilst [chars]: [chars]

Explanation    PPPoE EA encountered an error communicating with Rewrite Manager. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the Rewrite Manager Server process, but the error could also be caused by low memory resource or programming error.

Recommended Action    In many cases, PPPoE EA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_EA-6-ERR_IMP_MULTIPLE_NTFCNS CH[hex]: Multiple [chars] notifications received in a single batch from improxy

Explanation    A batch from IMProxy contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the PPPoE EA. No problems should be seen as a result.

Recommended Action    *NONE*

PPPOE_GBL_CFG Messages

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_GBL_CFG-4-ERR_DBG_TRACE Failed to initialize the PPPoE GBL debug and trace: [chars]

Explanation    PPPoE MA encountered an error initializing its Debug and Trace The error message describes what operation has failed and why it failed. This is a fatal error and the PPPoE GBL process cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_GBL_CFG-4-ERR_EVM_CREATE Error creating the PPPoE GBL Event Manager: [chars]

Explanation    PPPoE GBL failed to create its Event Manager which is a critical resource for the operation of the process. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *SUPPORT*

PPPOE_MA Messages

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-2-ERR_INVALID_CB Invalid [chars] callback: [chars]

Explanation    PPPoE MA received an invalid callback from another process. The error message describes why it is invalid. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-2-ERR_UNEXPECTED_CB Unexpected [chars] callback, when session in [chars] state

Explanation    PPPoE MA received an asynchronous callback from another process when the session was in an incorrect state. The error message describes which callback was received. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-2-ERR_UNEXPECTED_CLEANUP Unexpected [chars], when session in [chars] state

Explanation    PPPoE MA is trying to cleanup a session when it is in an unexpected state. The error message describes which state it was in, and what was triggering the cleanup. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_AAA_ATTR Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using AAA attribute APIs. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_AAA_CONN_DOWN Unexpected [chars] received while AAA connection down

Explanation    PPPoE MA received a notification from AAA while the connection was down. The most likely reason for this a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_AAA_SESSION Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using AAA session APIs. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_AAA_STALE_SESSION Disconnecting subscriber session with sub_label [hex] failed. The session should be cleared manually using the 'clear subscriber' command: [chars]

Explanation    PPPoE MA failed to call AAA to disconnect a session. The session may now need to be cleared manually using the 'clear subscriber' CLI command. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Run 'clear subscriber' for the specified session.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_BBA_CONFIG Unexpected config-value received for the '[chars]' BBA-Group config item

Explanation    PPPoE MA received an unexpected config-value for a piece of BBA-group config through SysDB. The error message describes which config item was invalid. The most likely reason for this a programming error in the verifier for the config item.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_BEFORE_TRACE Error initializing '[chars]': [chars]

Explanation    PPPoE MA encountered an error initializing its Debug and Trace The error message describes what operation has failed and why it failed. This is a fatal error and the PPPoE MA process cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_CDM Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using the CDM Service. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_CHKPT Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using the Checkpoint Service. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_CHKPT_CORRUPT Corrupt [chars] checkpoint record found: [chars]

Explanation    Whilst restoring one of its checkpoint tables PPPoE MA found a corrupt checkpoint entry. The entry will be ignored and so the relevant PPPoE session will be lost.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_CHKPT_DUPLICATE Duplicate [chars] checkpoint record found for CH[hex]

Explanation    Whilst restoring one of its checkpoint tables PPPoE MA found multiple entries for the same interface. PPPoE MA will use the first checkpoint entry it finds for each interface and ignore any subsequent duplicates. This is caused by a programming error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_DEBUG Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using the debug service. The error message describes what operation has failed and why it failed. The error could be caused by low memory resource or programming error.

Recommended Action    In many cases, PPPoE MA will recover by itself. If it does not then restarting the process may help. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_CLOSE Error closing '[chars]' connection: [chars]

Explanation    PPPoE MA failed to close a connection to an essential service. This is an internal error and it requires a restart of the process for recovery.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_CREATE Error creating '[chars]' connection: [chars]

Explanation    PPPoE MA failed to create a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_ERROR Error resetting '[chars]' connection: [chars]

Explanation    After detecting an error with the connection to the specified service, PPPoE MA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_GET_FD Error retrieving the Connection ID from the '[chars]' connection: [chars]

Explanation    PPPoE MA failed to retrieve the file descriptor associated with the specified service. This is an internal error.

Recommended Action    Consider restarting the PPPoE MA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_NOTIFY Error registering for critical events on '[chars]' connection: [chars]

Explanation    During initialization, PPPoE MA failed to register for essential notifications regarding the state of the connection for the specified service. This is an internal error. It requires a restart of the process for recovery.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVC_OPEN Error opening '[chars]' connection: [chars]

Explanation    PPPoE MA failed to open a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVM_ATTACH Failed to register a handler for '[chars]' messages: [chars]

Explanation    PPPoE MA failed to register a handler for the specified class of event. This is an initialization error and implies that PPPoE MA will not be able to operate correctly. The PPPoE MA process will abort and be restarted in an attempt to recover. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the PPPoE MA process. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVM_CREATE Error creating the PPPoE MA Event Manager: [chars]

Explanation    PPPoE MA failed to create its Event Manager which is a critical resource for the operation of the process. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *SUPPORT*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVM_EVENT_BLOCK Error encountered in the event loop: [chars]. The PPPoE MA process will restart

Explanation    An error occured in the event loop. The process will restart which should recover the situation.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVM_SEND Failed to send '[chars]': [chars]

Explanation    PPPoE MA failed to send the specified message. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the affected PPPoE MA process. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVQ_CREATE Error creating event queue for '[chars]': [chars]

Explanation    This is an unexpected error. The PPPoE MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVQ_DEQUEUE Error dequeuing event for '[chars]': [chars]

Explanation    This is an unexpected error. The PPPoE MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_EVQ_ENQUEUE Error queuing event for '[chars]': [chars]

Explanation    This is an unexpected error. The PPPoE MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_IMC Unexpected IfMgr error encountered [chars]: [chars]

Explanation    PPPoE MA encountered an error communicating with Interface Manager. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the Interface Manager Control Server, but the error could also be caused by low memory resource or programming error.

Recommended Action    In many cases, PPPoE MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_INSERT_GLOBAL Interface CH[hex] already in global session tree

Explanation    PPPoE MA tried to insert an interface into the global session tree which was already there. The error is probably caused by a programming error.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_INVALID_CB Invalid [chars] callback: [chars]

Explanation    PPPoE MA received an invalid callback from another process. The error message describes why it is invalid. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_INVALID_MTU Unexpected MTU set for CH[hex]: [unsigned int] bytes. Expected [unsigned int] bytes.

Explanation    An access-interface has been configured with an MTU that is incompatible with a PPPoE sub-interface. The PPP-Max-Payload tag provided by connecting peers is used to places a lower bound on the MTU that can be configured on an access-interface.

Recommended Action    Revert any configuration changes made to the access-interface's MTU or reduce the configured maximum value for ppp-max-payload.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes for '[chars]'

Explanation    The process failed to allocate memory for the specified resource.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_MGD_TIMER Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an unexpected error using the Managed Timer library. This is most likely to be due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the PPPoE MA process. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_PACKET_WITH_INVALID_SESSION_ID_RECEIVED Packet with invalid session ID ([dec]) received on access interface CH[hex].

Explanation    A packet with an invalid session ID has been received. This indicates that a subscriber has started communicating with this AC after initiating this session with another AC.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_PLATFORM_IFNAME_PARSE Unexpected platform error encountered when calling [chars]: [chars]

Explanation    PPPoE MA encountered an error using a platform API to parse the interface name. The error message describes what operation has failed and why it failed. The error is most likely caused by a programming error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_REGCOMP Failed to compile regular expression '[chars]' for [chars]

Explanation    The process failed to compile the given regular expression.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_SUBDB Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using SubDB The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_SYSDB Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an error using SysDB APIs. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_SYSMGR Unexpected Sysmgr error encountered calling [chars]: [chars]

Explanation    PPPoE MA encountered an error communicating with Sysmgr. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary initialization problem, but the error could also be caused by programming error.

Recommended Action    In most cases, PPPoE MA will not be able to recover, so will shutdown. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.. *SUPPORT*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_TEST_ONLY An event was hit that should only occur during testing: [chars]

Explanation    PPPoE MA hit some code that it shouldn't be possible to hit except during testing. This must be related to a programming error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_TIMER_WHEEL Unexpected error encountered whilst [chars]: [chars]

Explanation    PPPoE MA encountered an unexpected error using the Timer Wheel library. This is most likely to be due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the PPPoE MA process. *RECUR*.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_TUPLE Failed to unpack tuple for '[chars]'

Explanation    The process failed to unpack a tuple.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_UNEXPECTED_CB Unexpected [chars] callback, when session in [chars] state

Explanation    PPPoE MA received an asynchronous callback from another process when the session was in an incorrect state. The error message describes which callback was received. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-ERR_UNEXPECTED_CLEANUP Unexpected [chars], when session in [chars] state

Explanation    PPPoE MA is trying to cleanup a session when it is in an unexpected state. The error message describes which state it was in, and what was triggering the cleanup. This is most likely to be a programming error, either in PPPoE or in one of the processes it interacts with.

Recommended Action    PPPoE MA should recover by itself.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_ACCESS_INTERFACE_SESSION_LIMIT_REACHED Access interface CH[hex] session limit maximum ([unsigned int] sessions) reached. Further connection attempts will be rejected.

Explanation    The number of PPPoE sessions on the access interface has reached the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_ACCESS_INTERFACE_SESSION_THRESHOLD_EXCEEDED Access interface CH[hex] session limit threshold ([unsigned int] sessions) reached. Maximum: [unsigned int] sessions.

Explanation    The number of PPPoE sessions on the access interface has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_CARD_SESSION_LIMIT_REACHED Card session limit maximum ([unsigned int] sessions) reached. Further connection attempts will be rejected.

Explanation    The number of PPPoE sessions on the card has reached the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_CARD_SESSION_THRESHOLD_EXCEEDED Card session limit threshold ([unsigned int] sessions) reached. Maximum: [unsigned int] sessions.

Explanation    The number of PPPoE sessions on the card has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_CIRCUIT_ID_SESSION_LIMIT_REACHED Circuit ID [chars] session limit ([unsigned int] sessions) threshold maximum. Further connection attempts will be rejected.

Explanation    The number of PPPoE sessions on a particular Circuit ID has reached the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_CIRCUIT_ID_SESSION_THRESHOLD_EXCEEDED Circuit ID [chars] session limit ([unsigned int] sessions) threshold reached. Maximum: [unsigned int] sessions.

Explanation    The number of PPPoE sessions on a particular Circuit ID has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_MAC_IWF_SESSION_LIMIT_REACHED MAC-IWF address [chars] session limit maximum ([unsigned int] sessions) reached. Further connection attempts will be rejected.

Explanation    The number of IWF PPPoE sessions from a particular MAC address has reached the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_MAC_IWF_SESSION_THRESHOLD_EXCEEDED MAC-IWF address [chars] session limit threshold ([unsigned int] sessions) reached. Maximum: [unsigned int] sessions.

Explanation    The number of IWF PPPoE sessions from a particular MAC address has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_MAC_SESSION_LIMIT_REACHED MAC address [chars] session limit maximum ([unsigned int] sessions) reached. Further connection attempts will be rejected.

Explanation    The number of PPPoE sessions from a particular MAC address has reached the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-4-WARN_MAC_SESSION_THRESHOLD_EXCEEDED MAC address [chars] session limit threshold ([unsigned int] sessions) reached. Maximum: [unsigned int] sessions.

Explanation    The number of PPPoE sessions from a particular MAC address has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-ERR_EVC_DESTROY Error destroying '[chars]' connection: [chars]

Explanation    During process termination PPPoE MA failed to destroy a connection to a service provided by another process. This is an internal error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-ERR_EVQ_DESTROY Error destroying event queue for '[chars]': [chars]

Explanation    During process termination PPPoE MA failed to destroy an event queue. The process will terminate regardless so there should be no lasting problems.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_ACCESS_INTERFACE_SESSION_LIMIT_NOT_REACHED Access interface CH[hex] session limit maximum ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions on the access interface is no longer exceeding the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_ACCESS_INTERFACE_SESSION_THRESHOLD_NOT_EXCEEDED Access interface CH[hex] session limit threshold ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions on the access interface is no longer exceeding the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_CARD_SESSION_LIMIT_NOT_REACHED Card session limit maximum ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions on the card is no longer exceeding the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_CARD_SESSION_THRESHOLD_NOT_EXCEEDED Card session limit threshold ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions on the card is no longer exceeding the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_CIRCUIT_ID_SESSION_LIMIT_NOT_REACHED Circuit ID [chars] session limit ([unsigned int] sessions) maximum no longer reached.

Explanation    The number of PPPoE sessions on a particular Circuit ID is no longer exceeding the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_CIRCUIT_ID_SESSION_THRESHOLD_NOT_EXCEEDED Circuit ID [chars] session limit ([unsigned int] sessions) threshold no longer reached.

Explanation    The number of PPPoE sessions on a particular Circuit ID is no longer exceeding the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_MAC_IWF_SESSION_LIMIT_NOT_REACHED MAC-IWF address [chars] session limit maximum ([unsigned int] sessions) no longer reached.

Explanation    The number of IWF PPPoE sessions from a particular MAC address is no longer exceeding the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_MAC_IWF_SESSION_THRESHOLD_NOT_EXCEEDED MAC-IWF address [chars] session limit threshold ([unsigned int] sessions) no longer reached.

Explanation    The number of IWF PPPoE sessions from a particular MAC address is no longer exceeding the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_MAC_SESSION_LIMIT_NOT_REACHED MAC address [chars] session limit maximum ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions from a particular MAC address is no longer the configured maximum.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-PPPOE_MA-6-INFO_MAC_SESSION_THRESHOLD_NOT_EXCEEDED MAC address [chars] session limit threshold ([unsigned int] sessions) no longer reached.

Explanation    The number of PPPoE sessions from a particular MAC address has exceeded the configured threshold.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

SUB_UTIL Messages

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-0-INIT_RETRY_SUCCEEDED Subscriber Util succeeded in initializing the [chars] module upon retry.

Explanation    An error was previously encountered while initializing one of modules of the sub_util server. However, the initialization was retried and succeeded.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-0-INIT_RETRY_SUCCEEDED Subscriber Util succeeded in initializing the [chars] module upon retry.

Explanation    An error was previously encountered while initializing one of modules of the subscriber util. However, the initialization was retried and succeeded.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-2-INIT_FAILURE Failed to initialze Subscriber util: [chars]

Explanation    This syslog is printed when RwString Manager or its clients fail to initialize necessary data structures and memories. If the error originates from the system call the error message is also printed.

Recommended Action    Based on the system error message the user can tell what went wrong. More likely than not, the user has to restart the system. If the problem persists he or she has to contact Cisco customer support team.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-2-INIT_FAILURE Failed to initialze Subscriber Util: [chars]

Explanation    This syslog is printed when Subscriber Util or its clients fail to initialize necessary data structures and memories. If the error originates from the system call the error message is also printed.

Recommended Action    Based on the system error message the user can tell what went wrong. More likely than not, the user has to restart the system. If the problem persists he or she has to contact Cisco customer support team.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-2-MALLOC_FAILURE Failed to allocate memory: [chars]

Explanation    An explanation is provided in the syslog.

Recommended Action    A user should be able to tell what went wrong and take actions accordingly. For instance, if the system runs out of memory then more memory needs to be installed.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-2-MALLOC_FAILURE Failed to allocate memory: [chars]

Explanation    An explanation is provided in the syslog.

Recommended Action    A user should be able to tell what went wrong and take actions accordingly. For instance, if the system runs out of memory then more memory needs to be installed.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-4-INIT_ERROR Subscriber Util was unable to initialize the [chars] module. Error: '[chars]'. [chars].

Explanation    An error was encountered while initializing one of the modules of configuration manager server. The failure of this module initialization is not critical to configuration manager to be completely operational.

Recommended Action    Provide the message details to Cisco Support personal.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-4-INIT_ERROR Subscriber util was unable to initialize the [chars] module. Error: '[chars]'. [chars].

Explanation    An error was encountered while initializing one of the modules of configuration manager server. The failure of this module initialization is not critical to configuration manager to be completely operational.

Recommended Action    Provide the message details to Cisco Support personal.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-4-TRACE [chars] Error:[chars]

Explanation    This is a non-fatal error and can happen when router is low on memory. It should not affect the functioning of the router, but trace messages may not be logged.

Recommended Action    None.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-4-TRACE [chars] Error:[chars]

Explanation    This is a non-fatal error and can happen when router is low on memory. It should not affect the functioning of the router, but trace messages may not be logged.

Recommended Action    None.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-7-INTERNAL [chars]

Explanation    An unexpected internal error occurred in the sub_util subsystem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SUBSCRIBER-SUB_UTIL-7-INTERNAL [chars]

Explanation    An unexpected internal error occurred in the subscriber util subsystem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.

TMPL Messages

Error Message     
 
    
    
   

%SUBSCRIBER-TMPL-7-INTERNAL [chars]

Explanation    An unexpected internal error occurred in the template manager subsystem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.

VPDN Messages

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-CALL_DLL_ENABLE Failed to initialize '[chars]' when enabling VPDN feature, [hex]:[chars].

Explanation    When 'vpdn' configuration is first added, the VPDN CALL infra initializes in client processes, namely PPP-MA. Something has failed in this process and may prevent VPDN from functioning.

Recommended Action    Remove and re-add 'vpdn' configuration. If the problem repeats, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-CALL_DLL_INIT Failed to initialize '[chars]' when initializing VPDN feature, [hex]:[chars].

Explanation    An essential part of the VPDN CALL infra has failed to initialize in a client process and may prevent VPDN from functioning.

Recommended Action    Restart the client process.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-CALL_IPC_NOTIFY Received IPC error for '[chars]' notificaton, [hex]:[chars].

Explanation    An IPC notification was received that indicates an error. 1 or more sessions may not establish or may be torn down.

Recommended Action    Allow the subscribers to reconnect. If the problem persists, you may need to restart vpdn_mgr and/or this client process.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-CALL_IPC_SEND Failed to send IPC message length [unsigned int], [hex]:[chars].

Explanation    A VPDN CALL message failed to be sent to VPDN MGR. 1 or more sessions may not establish or may be torn down.

Recommended Action    Allow the subscribers to reconnect. If the problem persists, you may need to restart vpdn_mgr and/or this client process.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-CALL_SADB_UPDATE Failed to update SADB attribute '[chars]' for user '[chars]' (sub_label:[hex] sub_ifh:[hex]), [hex]:[chars].

Explanation    A VPDN CALL's Subscriber Attribute Database parameters were not updated. This may affect accounting and show commands.

Recommended Action    Clear the subscriber and allow it to reconnect. If the problem persists, contact technical support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-MGR_ACTIVE Failed to initialize '[chars]' at active, [hex]:[chars].

Explanation    When VPDN Manager (vpdn_mgr) is either the active process or RPFO occurs, the process initializes active-only services. Something has failed in this proceedure and may prevent VPDN from functioning.

Recommended Action    Allow VPDN Manager to restart. You can further remove and re-add 'vpdn' configuration. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-MGR_EVM Failed to receive event from [chars] EVM, [hex]:[chars].

Explanation    The event processing infra has returned a fatal error.

Recommended Action    Allow VPDN Manager to restart. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-MGR_INIT Failed to initialize '[chars]', [hex]:[chars].

Explanation    When 'vpdn' configuration is first added, the VPDN Manager (vpdn_mgr) process starts and initializes. Something has failed in this proceedure and may prevent VPDN from functioning.

Recommended Action    Allow VPDN Manager to restart. You can further remove and re-add 'vpdn' configuration. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-3-MGR_SHUTDOWN Failed at '[chars]' during shutdown, [hex]:[chars].

Explanation    When 'vpdn' configuration is removed, the VPDN Manager (vpdn_mgr) process will shutdown and exit. Something has failed in this proceedure and may prevent VPDN from functioning later or releasing resources.

Recommended Action    Allow VPDN Manager to exit and validate with 'show proc vpdn_mgr'. If it does not exit use 'proc restart vpdn_mgr' to recover. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-CALL_ALLOC Failed to alloc ([unsigned int] hdr) + ([unsigned int] items)*([unsigned int] bytes) equals ([unsigned int] total bytes) for '[chars]', errno [dec]:[chars].

Explanation    The VPDN CALL infra has failed to allocate memory. This may be due to low memory conditions on this particular RP/LC, or this client may be using more memory than it is allowed.

Recommended Action    Reduce system scale.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-CALL_DLL_DISABLE Failed to uninitialize '[chars]' when disabling VPDN feature, [hex]:[chars].

Explanation    When 'vpdn' configuration is removed, the VPDN CALL infra uninitializes in client processes, namely PPP-MA. Something has failed in this process any may contribute to leaked resources. In some cases, this warning message may be harmless.

Recommended Action    None.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-CALL_DLL_UNINIT Failed to uninitialize '[chars]' when uninitializing VPDN feature, [hex]:[chars].

Explanation    Part of the VPDN CALL infra has failed to uninitialize and may contribute to leaked resources. In some cases, this warning message may be harmless.

Recommended Action    None.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-CALL_IPC_DISCONNECT Failed to disconnect IPC, [hex]:[chars].

Explanation    The VPDN CALL IPC failed to disconnect as a result of configuration or an internal error. In some cases, this warning message may be harmless.

Recommended Action    If VPDN problems persist, you may need to restart vpdn_mgr or this client process.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-CALL_TLV Failed to process TLV type [unsigned int] length [unsigned int].

Explanation    Messages are exchanged between the VPDN Manager (vpdn_mgr) process and the client (e.g. ppp_ma). An error has occured here and session state may be out of sync.

Recommended Action    Allow VPDN to recover and the session to re-establish. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-DATAPLANE_ADD Failed to ADD session dataplane programming for CH[hex] on CH[hex] (Tunnel/Session Local: [unsigned int]/[unsigned int] Remote: [unsigned int]/[unsigned int]), [hex]:[chars].

Explanation    Failed to program session dataplane in L2FIB.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact technical support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-DATAPLANE_BATCH Failed to send batch of [unsigned int] bytes containing [unsigned int] sessions, [hex]:[chars].

Explanation    The VPDN MGR failed to program the dataplane for 1 or more sessions. These sessions must be distributed from VPDN MGR to all instances of L2FIB on all nodes. This failure may affect the establishment or tear-down of 1 or more sessions. In the case of tear-down, these resources may be leaked.

Recommended Action    Allow sessions to re-establish. For sessions that fail to tear-down, either restart the vpdn_mgr process or the l2fib_mgr process on all nodes. You may also clear L2FIB tables. This may have significant service disruption. If the problem persists, contact technical support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-DATAPLANE_DELETE Failed to DELETE session dataplane programming for CH[hex] on CH[hex], [hex]:[chars].

Explanation    Failed to DELETE session dataplane from L2FIB. Resources may be leaked for this session.

Recommended Action    You may either restart the vpdn_mgr process or the l2fib_mgr process on all nodes. You may also clear L2FIB tables. This may have significant service disruption. If the problem persists, contact technical support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-FSM_APPDATA Failed to '[chars]' for socket app data for user '[chars]' (sub_label:[hex] sub_ifh:[hex]).

Explanation    VPDN MGR failed process internal messages. This may be due to low memory conditions.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-FSM_CONNECT Failed to connect to protocol for user '[chars]' (sub_label:[hex] sub_ifh:[hex]).

Explanation    VPDN application failed to connect to procotol socket. This may be due to low memory conditions or an invalid argument.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-FSM_NVPAIR Failed to '[chars]' for NVPairs for user '[chars]' (sub_label:[hex] sub_ifh:[hex]), [unsigned int].

Explanation    VPDN MGR failed process internal messages. This may be due to low memory conditions.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-FSM_NVPAIR_ATTR Failed to '[chars]' for NVPair attribute '[unsigned int]' for user '[chars]' (sub_label:[hex] sub_ifh:[hex]).

Explanation    VPDN MGR failed process internal messages. This may be due to low memory conditions.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-FSM_SOCKOPTS Failed to '[chars]' for socket options for user '[chars]' (sub_label:[hex] sub_ifh:[hex]), [unsigned int].

Explanation    VPDN MGR failed process internal messages. This may be due to low memory conditions.

Recommended Action    Allow the subscriber to reconnect. If the problem persists, contact Cisco support.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-MGR_ALLOC Failed to alloc ([unsigned int] hdr) + ([unsigned int] items)*([unsigned int] bytes) equals ([unsigned int] total bytes) for '[chars]', errno [dec]:[chars].

Explanation    The VPDN MGR process has failed to allocate memory. This may be due to low memory conditions on this particular RP, or VPDN Manager may be user more memory than it is allowed.

Recommended Action    Reduce system scale.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-MGR_CHUNK_ALLOC Failed to alloc from chunk '[chars]', [dec]:[chars].

Explanation    The VPDN MGR process has failed to allocate memory. This may be due to low memory conditions on this particular RP, or VPDN Manager may be user more memory than it is allowed.

Recommended Action    Reduce system scale.

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-4-MGR_L2TP_SESSION_ID_SPACE L2TP session id space configuration is incompatible in the system. It is configured hierarchical, while only flat can be supported for the system.

Explanation    L2TP session id space configuration is incompatible in the system. This may prevent new sessions from coming up . Also , existing sessions may be affected.

Recommended Action    Please configure 'no l2tp session id space hierarchical'

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-AUTHEN [chars]

Explanation    A VPDN session has been terminated due to authentication-related error

Recommended Action    Please examine the user credential against AAA authentication database such as RADIUS profile. Also check similar authentication info at peer side such as local authentication info on LNS or RADIUS profile used by LNS

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-AUTHOR [chars]

Explanation    A VPDN session has been terminated due to authorization-related error

Recommended Action    Please examine the user credential against AAA authorization database such as RADIUS profile. Also check similar authorization info at peer side such as local authentication info on LNS or RADIUS profile used by LNS

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-DEADCACHE [chars]

Explanation    An LNS peer is added to or remove from dead cache

Recommended Action    Verify peer's IP reachability or confirm tunnel password configured on both sides match

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-SESSION [chars]

Explanation    A VPDN session has been terminated due to session-specific errors encountered in local or remote VPDN or L2TP protocol processing

Recommended Action    Please examine the human-readable error message that appears in the log and conduct the first level of troubleshooting based on the info in the message. If the root cause is still not clear, collect the required info and forward it to technical support

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-TUNNEL [chars]

Explanation    A VPDN session has been terminated due to errors encountered by the L2TP tunnel that contains the affected session

Recommended Action    The log indicates that a session is terminated or has failed to establish due to teardown of the tunnel that contains it. Please examine the human-readable error message that appears in the log and conduct the first level of troubleshooting based on the info in the message. If the root cause is still not clear, collect the required info and forward it to customer support

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-UNKNOWN [chars]

Explanation    A VPDN session has been terminated. The category of the termination event is unknown

Recommended Action    Please examine the human-readable error message that appears in the log and conduct the first level of troubleshooting based on the info in the message. If the root cause is still not clear, collect the required info and forward it to technical support

Error Message     
 
    
    
   

%SUBSCRIBER-VPDN-6-USER [chars]

Explanation    A VPDN session has been terminated due to user action such as user inactivity has exceeded the configured idle time or user has hung up the call.

Recommended Action    None.