-
Cisco IOS XR System Error Reference Guide for Platform Independent Messages, Release 3.3
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Default Messages
-
Diagnostic Messages
-
Forwarding Information Base Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 (L1) Messages
-
Layer 2 (L2) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
Security Messages
-
Service Messages
-
Simple Network Management Protocol (SNMP ) Messages
-
System Database Messages
-
Feedback
Table Of Contents
Layer 2 Messages
This section contains all Layer 2 related System Error Messages, including Ethernet drivers, Packet-over-Sonet (PoS), SONET, PLIMS, and so forth. The following facility codes are represented in this module:
BFD Messages
Error Message%L2-BFD-4-RATE_LIMIT_WARNING_HIGH_WATERMARK BFD PPS allocation exceeds 90 percent of maximum.
Explanation BFD has allocated 90 percent of its packet per second allowance on this LC.
Recommended Action No action is required.
Error Message%L2-BFD-4-RATE_LIMIT_WARNING_LOW_WATERMARK BFD PPS allocation now less 85 percent of maximum.
Explanation BFD has released some of the previously allocated packet per second usage and is now at less than 85 percent of its allowance on this LC.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_NO_RESOURCES No resources for session to neighbor [chars] on interface [chars], interval=[unsigned int] ms[chars]
Explanation The BFD session can not be created or modified due to lack of resources.
Recommended Action Remove other BFD sessions to free resources for this session
Error Message%L2-BFD-6-SESSION_NO_RESOURCES_CLR Lack of resources condition has cleared for session to neighbor [chars] on interface [chars]
Explanation Resources are now available for this session.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_REMOVED BFD session to neighbor [chars] on interface [chars] has been removed
Explanation The BFD session has been removed. This is due to the application(s) removing the BFD session. This can happen as a result of BFD being unconfigured under the application(s) or as a result of the application(s) adjacency being removed.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_STATE_DOWN BFD session to neighbor [chars] on interface [chars] has gone down. Reason: [chars]
Explanation The BFD session has gone down. This may be as a result of the forwarding path being down.
Recommended Action Determine if the forwarding path to the neighbor has gone down.
Error Message%L2-BFD-6-SESSION_STATE_UP BFD session to neighbor [chars] on interface [chars] is up
Explanation The BFD session is now up.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_VERSION_CHANGE BFD session to neighbor [chars] on interface [chars] is administratively down due to version change from version [unsigned int] to version [unsigned int]
Explanation The BFD session has been brought administratively down to change protocol version.
Recommended Action No action is required.
BM Messages
Error Message%L2-BM-3-ERR_IIR_MEMBERSHIP Link [chars] in [chars] reported by IIR in bundle [chars].
Explanation When synchronising with IIR during restart the link was reported to be in a different bundle from the checkpoint records of the process. This should never happen and is not recoverable. The information from IIR was discarded and the process is now out of step with IIR, possibly leading to further problems.
Recommended Action Delete the checkpoint data for the Bundle Manager process that reported the error (run rm /tmp/chkpt_bundlemgr_distrib*) and restart the process.
Error Message%L2-BM-3-ERR_MASTER Error reported by Bundle Manager master process: [chars]. The local process will now be out of step with the master.
Explanation A problem occured on the RP which meant that the master process could not update its records to reference the message sent. If the message was sent as a result of a configuration change then the two processes will remain out of sync until one is restarted. If the message was sent due to LACP negotiations then the periodic nature of LACP negotiations should cause the problem to recover automatically.
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%L2-BM-4-ERR_ACTIVATE Failure during activation of [chars]. Error: [chars]
Explanation A failure occurred during the activation of the process. Activation occurs when the card transitions to ACTIVE state. This error resulted in the restart of the process.
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%L2-BM-4-ERR_ADJ_DLL_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the platform independent adjacency completion DLL. This will result in the hosting process being restarted.
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%L2-BM-4-ERR_ADMINSTATE Unable to [chars] administrative state for [chars] on [chars]. Error: [chars]
Explanation The operation attempted failed. For a set this may mean that the link is UP when the bundle is SHUTDOWN. This can be resolved by 'no shut' and then 'shut' of the bundle. For a clear this may mean that the link remains DOWN when it has been removed from the bundle. This can be resolved by re-adding and then removing the link from the bundle again.
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%L2-BM-4-ERR_EVM_EVENT_BLOCK Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process has exited and restarted.
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%L2-BM-4-ERR_GROUP_CREATE Unable to create GSP group. Error: [chars]
Explanation Creation of the group used to communicate between Bundle Manager processes failed. This resulted in the restart of the process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show gsp groups command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsp groups output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_IDENTICAL Attempting to order [chars] and [chars] that have identical port information
Explanation The comparison between an entry in the bundle member list and a new entry to be inserted showed that both had identical port data. Because of this the new link could not be inserted into the list and the operation leading to this failed.
Recommended Action Remove and re-add the configuration for the links named in the message. 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%L2-BM-4-ERR_IIR_BDL_DATA Invalid [chars] specified by IIR for : [unsigned int]
Explanation The data specified in the IIR notification is not one of the recognised values for that type. The information is invalid and the result is that adjacencies for this bundle cannot be programmed in hardware.
Recommended Action Delete and recreate the bundle. 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%L2-BM-4-ERR_IIR_BDL_HANDLE Invalid (NULL) interface handle supplied for a bundle by IIR
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action If this event can be associated with changes to a particular bundle then delete and recreate the bundle. 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%L2-BM-4-ERR_IIR_MBR_DATA Invalid [chars] specified by IIR for member : [unsigned int]
Explanation The data specified in the IIR notification is not one of the recognised values for the type. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. 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%L2-BM-4-ERR_IIR_MBR_HANDLE Invalid (NULL) interface handle supplied by IIR for a member of
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. 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%L2-BM-4-ERR_IIR_OP Unable to report IIR op failure for b_ifh [hex], m_ifh [hex] (op [chars], state [chars]). Error: [chars]
Explanation An error occurred processing the IIR event and the bundle EA process was unable to report this error back to IIR. This may lead to some inconsistency with the bundle membership in the data plane not matching what is intended according to the control plane.
Recommended Action The failure to report the error back to IIR suggests a problem in the connection to IIR. This may have been a transient problem, but restarting ifmgr and/or the bundlemgr_ea process on the location of the error might be necessary. The error that should have been reported also needs to be dealt with. This error may have come from some lower layer platform component, possibly a resource allocation error. If the error code provides some information as to the failure then take action appropriate to the error. If the error code is not specific then take action according to whether the event was a link activation or a link deactivation/deletion. For activation problems unconfigure and reconfigure the member link - if this fails try restarting the bundlemgr_ea process after unconfiguring the member link. For deactivation/deletion failures try restarting the improxy process to trigger a complete resync by the bundlemgr EA.
Error Message%L2-BM-4-ERR_IIR_SUB_HANDLE Invalid (NULL) interface handle supplied by IIR for a sub-interface of
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. 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%L2-BM-4-ERR_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the process. This resulted in the restart of the process.
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%L2-BM-4-ERR_INIT_ENS Failure to initialise ENS - retry scheduled. Error: [chars]
Explanation A failure occurred during the initialization of ENS library in the process. This probably indicates an underlying more severe problem. A retry will be attempted.
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%L2-BM-4-ERR_LINK_ATTACHED Link [chars] is attached to [chars] that is thought to have no attached members.
Explanation This process believes that there are no aggregatable links, but this link is marked as attached. This error is most likely caused by failing to attach or detach a link correctly.
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%L2-BM-4-ERR_MEM_ALLOC Unable to allocate [unsigned int] bytes of memory.
Explanation Memory allocation failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-BM-4-ERR_MIB_CLEANUP Failure during cleanup of [chars] in the dot3ad MIB DLL. Error: [chars]
Explanation A failure occurred during the cleanup of the DLL. This may result in the DLL not being completely cleaned up, possibly causing errors in a subsequent re-initialization of the DLL.
Recommended Action Restart the snmp process reporting the error. 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%L2-BM-4-ERR_MIB_INIT Failure during intialization of [chars] in the dot3ad MIB DLL. Error: [chars]
Explanation A failure occurred during the initialization of the DLL. This resulted in the DLL not being loaded into the SNMP agent, and thus the MIB services will not be available.
Recommended Action Restart the snmp process reporting the error. 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%L2-BM-4-ERR_MTU_IMPOSE Imposition of configured MTU failed for [chars], will continue to use previous value: [unsigned int]
Explanation The MTU imposition was rejected by IM or another client. The bundle will continue to operate with the previously configured MTU.
Recommended Action Check that the configured MTU is within approrpriate ranges for the interface type and network layer protocols on the interface. Remove the configuration and reapply.
Error Message%L2-BM-4-ERR_NETIO_INIT Failure [chars] in the bundle NetIO DLL during [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the bundle NetIO DLL. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user. One possible reason for the error is a low memory condition, particularly if the failure was in allocating trace buffers.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-BM-4-ERR_PAKMAN Unable to handle pakman corruption error: [chars]. Process exiting
Explanation A packet manager corruption has been reported and the Bundle Manager process has failed to cleanup to recover from the problem. The process will exit and be automatically restarted to recover from this situation.
Recommended Action It is expected that restarting the process will fix this problem. This is done automatically so no action should be required. If the problem recurs, then there is a problem in packet manager. A drastic solution would be to reload the linecard.
Error Message%L2-BM-4-ERR_RECREATE_BUNDLE Unable to recreate bundle . Error: [chars]
Explanation When recovering the checkpointed data for a bundle, an error occurred and the data is lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show adjacency detail hardware location command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show adjacency detail hardware location output, call your Cisco technical support representative and provide the representative with the gathered information. If the bundle appears correctly in the output of all three commands then no further action is required, otherwise unconfigure and reconfigure the bundle.
Error Message%L2-BM-4-ERR_RECREATE_LINK Unable to recreate link [chars] in [chars]. Error: [chars]
Explanation When recovering the checkpointed data for a link, an error occurred and the data is lost.
Recommended Action Identify the bundle in which the link was a member. Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle output, call your Cisco technical support representative and provide the representative with the gathered information. If the member appears correctly in the output of both commands then no further action is required, otherwise unconfigure and reconfigure the member.
Error Message%L2-BM-4-ERR_REPAIR_BUNDLE Unable to repair bundle checkpoint structures. Error: [chars]
Explanation When repairing the checkpoint structures for the bundle database an error occurred for named bundle and the bundle was not checkpointed. The next time an attempt is made to checkpoint the bundle it will fail and the checkpoint table will be reconstructed again, perhaps more successfully.
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%L2-BM-4-ERR_REPAIR_DATABASE Unable to repair [chars] database. Failure during checkpoint [chars]. Error: [chars]
Explanation When repairing the checkpoint structures for the named database an error occurred in the database checkpoint registration. As a result the process was intentionally restarted.
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%L2-BM-4-ERR_REPAIR_LINK Unable to repair checkpoint structures for link [chars] in [chars]. Error: [chars]
Explanation When repairing the checkpoint structures for the link database an error occurred for named link and the link was not checkpointed. The next time an attempt is made to checkpoint the link it will fail and the checkpoint table will be reconstructed again, perhaps more successfully.
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%L2-BM-4-ERR_REPLICATE Replication failed for [chars], when adding member [chars]. Error: [chars]
Explanation When attempting to replicate the bundle to the member interface location, the replication operation failed. This probably happened because some hardware resource on the LC where the member is located was exhausted. The record of the member will be removed from the bundle process on the RP but will still be referenced by the bundle process on the LC.
Recommended Action Determine whether the hardware resources for the LC have been oversubscribed, e.g. more VLANs on the LC and on the bundle that the LC can support. If this is the case, reduce the number of allocated VLANs. Then remove the member configuration and reapply.
Error Message%L2-BM-4-ERR_RESTORE_LINK Unable to restore link [chars] in [chars]. [chars]. Error: [chars]
Explanation When restoring the link an error occurred and to maintain consistency the data was removed. It is likely, given the error, that the link had been OIR removed.
Recommended Action Verify that the link has not been OIR removed. If it has not, remove the bundle membership configuration and reapply it. 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%L2-BM-4-ERR_RESYNC_EXCEED_IIR Exceeded the IIR resync limit for [chars]. Process exiting.
Explanation The maximum number of attempts to resync with IIR have been exceeded for this bundle. The safest course of action is to restart the process and this has been done.
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%L2-BM-4-ERR_RESYNC_SCHED_IIR Unable to schedule an IIR resync for [chars]. Process exiting.
Explanation An attempt to schedule a resync with IIR has failed for this bundle. The safest course of action is to restart the process and this has been done.
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%L2-BM-4-ERR_RETRY_EXCEED Exceeded maximum number of retries for [chars]
Explanation After attempting to resend or query information a number of times, the retry limit has been exceeded and no more attempts will be made. The effect of the message will therefore be lost. The impact will depend on the message which was lost. If the message refers to a global error then the process will exit and be restarted.
Recommended Action If the message referred to a global error then check that the process has restarted successfully. If the message referred to a bundle or bundle member then check that the object is still configured and still exists. Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. 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%L2-BM-4-ERR_RETRY_EXCEED_GSP Retry limit for GSP initialization exceeded: [chars]
Explanation After attempting to create the GSP group used for communications with the Bundle Manager process on another node a number of times, the retry limit has been exceeded. The cause of the failure is very likely to be some external communication failure - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.
Recommended Action Check that other processes are not reporting similar communication errors, as this is likely to be a general communication problem. The Bundle Manager process has exited and will be restarted, so no action is needed, though unless the communication problem is resolved the process will still not be able to startup. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_RETRY_EXCEED_IMP Exceeded the retry limit for IMP events.
Explanation The maximum number of attempts to retry an IMP message has been exceeded. An error has occurred in the clean up of a bundle, so there may be residual data for the bundle in the linecard components which could cause subsequent problems. Restart the process that reported the error 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%L2-BM-4-ERR_RETRY_EXCEED_SYSTEM_MAC Retry limit for system MAC address query exceeded: [chars]
Explanation After attempting to query the system MAC address from SDRd a number of times, the retry limit has been exceeded. The cause of the failure is likely to be an issue with SDRd or Shelfmgr - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.
Recommended Action The Bundle Manager process has exited and will be restarted, so no action is needed. Check that the board (EEPROM etc.) is correctly programmed since this is the source of the MAC address information and therefore one possible cause of the problem.
Error Message%L2-BM-4-ERR_RETRY_SCHED Unable to send update for [chars] and unable to schedule retry: [chars]
Explanation A timeout occurred sending an update to a Bundle Manager process on another node. Due to a problem with the retry mechanism, a resend of the message could not be scheduled. The effect of the message will therefore be lost. The impact will depend on the message which was lost.
Recommended Action Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. 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%L2-BM-4-ERR_SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action Check on the status of the sysmgr process on the node from which the error was reported. 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%L2-BM-4-ERR_UNREPLICATE Unreplication failed for [chars], when removing member [chars]. Error: [chars]
Explanation When attempting to unreplicate the bundle from the member interface location, the unreplication operation failed. Some hardware resources may continue to be used for the bundle on the location of the member that was removed. It is also possible that there could be a problem replicating the bundle to that location again if a new member is added.
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%L2-BM-5-CHURN Interface [chars] in [chars] [chars] on actor system
Explanation Churn has either been detected (due to the failure of a link to synchronize soon enough) or the churn state has now cleared.
Recommended Action If churn has been declared, check that the configuration for the link allows it to aggregate, and fix as appropriate. Things to check for are links which are incompatible with each other, or misconfigurations between the two ends of the link which is reporting churn.
Error Message%L2-BM-6-DISTRIBUTING [chars] [chars] in Distributing state as part of [chars]
Explanation This is an informational message reporting that a link has entered or left Distributing state as part of a bundle interface. The link configuration may have just been changed or there may be an operational reason for the event such as a state change or LACP protocol update.
Recommended Action Nothing, this is not an error.
Error Message%L2-BM-6-MIN_MAX [chars] is down because the minimum active link threshold ([unsigned int]) is greater than the maximum permitted links ([unsigned int])
Explanation This is an informational message reporting that a bundle is operationally down because the configuration for minimum active links and maximum active links conflicts. The number of active links required for the bundle to come up is greater than the number of links permitted to be active in the bundle, and there are at least enough links held in standby state for the bundle to come up if the maximum active link criteria were removed.
Recommended Action If this situation is not intended then either reduce the minimum active link threshold or increase the maximum links permitted in the bundle.
CDP Messages
Error Message%L2-CDP-3-ERR_IM_CAPS_ADD Failed to add the CDP capsulation to interface [chars]: [chars]
Explanation CDP could not install the CDP capsulation on the specified interface and hence it is not possible for CDP to send or receive any packets on this interface.
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%L2-CDP-3-ERR_IM_CAPS_REMOVE Failed to remove the CDP capsulation on interface [chars]: [chars]
Explanation CDP could not uninstall the CDP capsulation on the specified interface and hence CDP may be in an inconsistent state.
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%L2-CDP-3-ERR_IM_MTU_REGISTER Failed to register for MTU size changes on interface [chars]: [chars]
Explanation CDP failed to register with the interface manager for MTU size changes on this particular interface. This may cause problems sending CDP packets.
Recommended Action Perform 'cdp disable', 'cdp enable' on the interface to try to recover. 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%L2-CDP-3-ERR_IM_STATE_REGISTER Failed to register for state changes on interface [chars]: [chars]
Explanation CDP failed to register with the interface manager for state changes on this particular interface. This means CDP will be unable to track the state of the interface. CDP functionality may be impaired.
Recommended Action Perform 'cdp disable', 'cdp enable' on the interface to try to recover. 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%L2-CDP-3-ERR_INIT CDP Initialization failed, module: [chars], operation: [chars]: [chars]
Explanation CDP's initialization has failed.
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%L2-CDP-3-ERR_INTF_INIT Initialisation of CDP on interface [chars] failed: [chars].
Explanation CDP is unable to run on the specified interface. It is likely that this is due to a lack of available resources.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Configuring 'cdp disable', 'cdp enable' on the interface, or restarting CDP on the affected node may recover the situation.
Error Message%L2-CDP-3-ERR_IPV4_ADDRESS_SCAN [chars]: Failed to scan the IPv4 addresses for this interface: [chars]. This means that IPv4 information will be missing from outgoing CDP packets
Explanation A scan of the IPv4 addresses on this interface has failed. This means that IPv4 address information for this interface will not be included in outgoing CDP packets. The neighboring device will not see the IPv4 address information for this interface.
Recommended Action Restarting CDP as the address consumer, or the ipv4_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv4_ma location
Error Message%L2-CDP-3-ERR_IPV4_REGISTRATION Unable to register for IPv4 address notifications: [chars]. This means that IPv4 information will be missing from outgoing CDP packets.
Explanation CDP registration with the IP address library has failed. This means that IPv4 address information for interfaces local to this node will not be included in outgoing CDP packets. The neighboring devices will not see the IPv4 address information for this router's interfaces.
Recommended Action Restarting CDP as the address consumer, or the ipv4_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv4_ma location
Error Message%L2-CDP-3-ERR_IPV6_ADDRESS_SCAN [chars]: Failed to scan the IPv6 addresses for this interface: [chars]. This means that IPv6 information will be missing from outgoing CDP packets
Explanation A scan of the IPv6 addresses on this interface has failed. This means that IPv6 address information for this interface will not be included in outgoing CDP packets. The neighboring device will not see the IPv6 address information for this interface.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv6_ma location
Error Message%L2-CDP-3-ERR_IPV6_REGISTRATION Unable to register for IPv6 address notifications: [chars]. This means that IPv6 information will be missing from outgoing CDP packets.
Explanation CDP registration with the IP address library has failed. This means that IPv6 address information for interfaces local to this node will not be included in outgoing CDP packets. The neighboring devices will not see the IPv6 address information for this router's interfaces.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv6_ma location
Error Message%L2-CDP-3-NO_KNOWN_MEDIA CDP did not find any recognized media to run over
Explanation CDP failed to initialize the media module because it could not find any media that it recognizes.
Recommended Action If there are no interfaces on this node with a media type that CDP is expected to run on then this could be a normal condition. If it is expected that CDP should run on the type of interfaces on this node then 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%L2-CDP-3-NO_KNOWN_MEDIA_DRIVERS CDP did not find any recognized media drivers
Explanation CDP failed to initialize the media module because it could not find any media drivers that it recognizes. Without these drivers CDP cannot run over any interfaces.
Recommended Action There are no media drivers for the interfaces on this node. If CDP does not support the interface types on this node then this could be a normal situation Otherwise 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%L2-CDP-4-DUPLEX_MISMATCH Duplex mismatch discovered on [chars] ([chars]), with [chars] [chars] ([chars]).
Explanation CDP discovered mismatching duplex configuration on neighboring interfaces.
Recommended Action Configure the interfaces with the same duplex (full or half).
Error Message%L2-CDP-4-ERR_CONN Connection error on [chars]([pointer]): [chars]
Explanation An error occurred on one of the event connections managed by CDP which CDP could not recover automatically.
Recommended Action Try restarting CDP. 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%L2-CDP-4-ERR_IM_ATTR_REGISTRATION Unable to register for duplex change notifications: [chars]
Explanation CDP registration for duplex change notifications failed. This means that duplex information will be missing from outgoing CDP packets
Recommended Action Try restarting CDP ('proc restart cdp location '). 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%L2-CDP-4-ERR_INTF_STATS No CDP protocol statistics can be collected on [chars]: [chars]
Explanation It was not possible to register for stats collection on the specified interface. The entry in the 'show interface accounting' command is likely to be inaccurate for CDP packets.
Recommended Action Try restarting CDP and the Statistics server process on this node. proc restart cdp location proc restart statsd_server location 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%L2-CDP-4-ERR_MULTICAST_ADDR_SET Error setting up the CDP multicast address on [chars] (media [chars]): [chars]
Explanation The driver returned an error while setting up the CDP multicast address. It is possible that CDP packets will be dropped and not reach the CDP process.
Recommended Action If CDP packet loss is seen then 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%L2-CDP-4-ERR_STATS No per-interface CDP protocol statistics can be collected: [chars]
Explanation It was not possible for CDP to register for per-interface CDP protocol stats collection. The entries in the 'show interface accounting' command are likely to be inaccurate for CDP packets.
Recommended Action Try restarting CDP and the Statistics server process on this node. proc restart cdp location proc restart statsd_server location 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%L2-CDP-4-ERR_TABLE_RESIZE Not enough memory to clear and resize the CDP table
Explanation CDP ran out of memory when trying to resize the CDP hash table.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. CDP will try and continue to use the previous CDP table.
Error Message%L2-CDP-4-NEIGHBOR_LIMIT The CDP cache on this node is full. It contains [dec] neighbor entries
Explanation The limit for neighbors in the CDP cache has been reached. No more neighbors will be added to the neighbor cache until some existing entries have been removed. The number of entries is limited to defend against DoS attacks.
Recommended Action Check the existing CDP neighbors for bogus entries, CDP may be the victim of an attempted DoS attack. The 'clear cdp table' command can be used if CDP neighbor entries need removing.
Error Message%L2-CDP-4-STALE_TLV On [chars] the [chars] TLV is not up to date: [chars]
Explanation CDP received a notification to update a TLV that it sends but failed to do so due to the error given. The information stored by CDP is now out of date.
Recommended Action Perform 'cdp disable', 'cdp enable' on the interface. 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%L2-CDP-4-WARN_INIT Initialization warning, module: [chars], operation: [chars]: [chars]
Explanation A non-fatal error occurred during CDP's initialization.
Recommended Action CDP will try to recover automatically. If this warning persists then check that there are enough resources available to run CDP or contact your technical support representative copying the error message exactly as it appears.
Error Message%L2-CDP-4-WARN_TERM Termination warning, module: [chars], operation: [chars]: [chars]
Explanation A non-fatal error occurred during CDP's termination.
Recommended Action CDP should recover automatically. If this warning persists then check that there are enough resources available to run CDP or contact your technical support representative copying the error message exactly as it appears.
Error Message%L2-CDP-6-DELETED_NEIGHBOR CDP Neighbour [chars] on interface [chars] has been deleted, remote interface [chars]
Explanation An entry has been removed from the CDP neighbors table. Notification of deleted CDP neighbors requested through 'cdp log adjacency changes'.
Recommended Action No action is required.
Error Message%L2-CDP-6-NEW_NEIGHBOR New CDP neighbor [chars] detected on interface [chars], remote interface [chars]
Explanation A new entry has been added to the CDP neighbors table. Notification of new CDP neighbors requested through 'cdp log adjacency changes'.
Recommended Action No action is required.
CDPCP Messages
Error Message%L2-CDPCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-CDPCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-CDPCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
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%L2-CDPCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the function.
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%L2-CDPCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an error condition
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%L2-CDPCP-3-ERR_EVENT_MGR_CREATE CDPCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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%L2-CDPCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation CDPCP was unable to determine the state of the basecaps and has assumed it to be down. CDPCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-CDPCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
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%L2-CDPCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
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%L2-CDPCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
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%L2-CDPCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
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%L2-CDPCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation CDPCP has failed to open a mailbox channel.
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%L2-CDPCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation CDPCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate CDPCP.
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%L2-CDPCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation CDPCP cannot perform some SysDB operation.
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%L2-CDPCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation CDPCP cannot (un)register for SysDB notification.
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%L2-CDPCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
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%L2-CDPCP-3-LTRACE_INIT CDPCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-CDPCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
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%L2-CDPCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
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%L2-CDPCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation CDPCP failed to allocate memory for a structure.
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%L2-CDPCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation CDPCP has failed to receive a message from its mailbox.
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%L2-CDPCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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%L2-CDPCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation CDPCP failed to create an interface structure.
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%L2-CDPCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation CDPCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-CDPCP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation CDPCP has failed an encapsulation operation with the interface manager.
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%L2-CDPCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation CDPCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-CDPCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation CDPCP has failed a protocol operation with the interface manager.
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.
CHDLC_EA Messages
Error Message%L2-CHDLC_EA-3-ERR_EVM_EVENT_BLOCK Unrecoverable error in the event loop. Error: [chars]. The cHDLC EA process will exit
Explanation An error (other than EINTR) occured in the event loop. This is unrecoverable so the process will exit.
Recommended Action *RECUR*
Error Message%L2-CHDLC_EA-3-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The cHDLC EA process will exit
Explanation A failure occured during the initialization of the process. The process will restart.
Recommended Action *RECUR*
Error Message%L2-CHDLC_EA-6-ERR_IMP_MULTIPLE_NTFCNS : 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 cHDLC EA. No problems should be seen as a result.
Recommended Action *NONE*
CHDLC_MA Messages
Error Message%L2-CHDLC_MA-3-ERR_EVM_EVENT_BLOCK Unrecoverable error in the event loop. Error: [chars] The cHDLC MA process will exit
Explanation An error (other than EINTR) occured in the event loop. This is unrecoverable so the process will exit.
Recommended Action *RECUR*
Error Message%L2-CHDLC_MA-3-ERR_IIR_BDL_OP The cHDLC MA failed to process a bundle IIR [chars] message on , error: [chars]
Explanation The chdlc_ma process failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the basecaps is out of step with the bundle configuration.
Recommended Action *SUPPORT*
Error Message%L2-CHDLC_MA-3-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The process will exit
Explanation A failure occured during the initialization of the process. The cHDLC MA process will restart.
Recommended Action *RECUR*
Error Message%L2-CHDLC_MA-3-ERR_INTF_UP_DOWN An error has occured resulting in the interface state being UP, and the line state being DOWN on interface . Because keepalives are disabled the line will never come up. The situation may be resolved by shutting and no shutting the interface, or enabling keepalives.
Explanation If keepalives are disabled and certain errors occur then the interface and line state can end up being out of step. Without keepalives enabled, SLARP has no way to recover by discovering the correct line state, so user intervention is required for a chance of recovery.
Recommended Action shut and then no shut the problematic interface, or enable keepalives on the interface.
Error Message%L2-CHDLC_MA-3-ERR_SYSMGR_SOCK_FEAT_START Startup of the cHDLC Socket feature has unexpectedly failed: [chars]
Explanation The cHDLC socket feature unexpectedly failed to be started by sysmgr. This may mean that processes which use cHDLC sockets to send and receive packets will be unable to do so, and may not be working correctly. Symptoms would include loss of SLARP keepalive packets causing the line state to go down, loss of CDP packets and loss of LACP packets on cHDLC encapsulated interfaces.
Recommended Action The problem can be fixed by manually starting the cHDLC Socket server process on the affected node using the command 'process start chdlc_socket location '. The command 'show process chdlc_socket location ' will indicate the state of the process. Once the socket server process is running, no further action is required.
Error Message%L2-CHDLC_MA-6-ERR_IM_MULTIPLE_NTFCNS : Multiple [chars] notifications received in a single batch from Interface Manager
Explanation A batch from Interface Manager contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the cHDLC MA. No problems should be seen as a result.
Recommended Action *NONE*
CHDLC_SOCK Messages
Error Message%L2-CHDLC_SOCK-3-ERR_EVM_EVENT_BLOCK Unrecoverable failure during receipt of event in the chdlc_socket process. Error: [chars].
Explanation An error (other than EINTR) occured in the event loop. This is unrecoverable so the process will exit.
Recommended Action *RECUR*
Error Message%L2-CHDLC_SOCK-3-ERR_INIT Failure during intialisation of the chdlc_socket process - specifically [chars]. Error: [chars]. The process will exit
Explanation A failure occurred during the initialisation of the cHDLC socket process. The process will exit and restart.
Recommended Action *RECUR*
Error Message%L2-CHDLC_SOCK-3-ERR_PAKMAN_CORRUPTION Unable to handle pakman corruption error: [chars]. chdlc_socket process exiting
Explanation A packet manager corruption has been reported and the cHDLC Socket process has failed to cleanup to recover from the problem. The process will exit and be automatically restarted to recover from this situation.
Recommended Action It is expected that restarting the process will fix this problem. This is done automatically so no action should be required. If the problem recurs, then there is a problem in packet manager. A drastic solution would be to reload the linecard.
CHDLCDLL Messages
Error Message%L2-CHDLCDLL-3-ERR_DEBUG_REGISTER Could not register for debug events : [chars]
Explanation There was an error registering the cHDLC Netio debug with the debug library. No debug will be available for the cHDLC Netio DLLs.
Recommended Action *SUPPORT*
Error Message%L2-CHDLCDLL-3-ERR_PKT_ENCAP Encapsulation of HDLC packet failed. Packet type-code [hex]
Explanation The encapsulation of an HDLC packet failed for the network protocol with the ethernet type code specified. The packet has been dropped.
Recommended Action *SUPPORT*
Error Message%L2-CHDLCDLL-3-ERR_TRACE_REGISTER Could not register with tracing infrastructure: [chars]
Explanation An attempt to register with the tracing infrastructure failed. This will mean that tracing for the cHDLC Netio DLLs will not be available.
Recommended Action *SUPPORT*
d1qnetio Messages
Error Message%L2-d1qnetio-3-CHAIN_BUILDER_FAILED The chain build function failed because '[chars]', err: [chars]
Explanation The 802.1Q NetIO chain builder function 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%L2-d1qnetio-3-CHAIN_UNBUILDER_FAILED The chain unbuild function failed because '[chars]', err: [chars]
Explanation The 802.1Q NetIO chain unbuilder function 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%L2-d1qnetio-3-IDB_NOT_FOUND The Netio IDB associated with handle [hex] could not be found
Explanation The 802.1Q NetIO component could not find the Netio IDB associated with the given handle.
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%L2-d1qnetio-3-REGISTRY_CREATION_FAILED Unable to create the protocol registries during capsulation initialization
Explanation The 802.1Q NetIO component could not create the protocol registries
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%L2-d1qnetio-3-VLAN_ID_SET_FAILED Failed to set the VLAN Id on [chars], err: [chars]
Explanation The 802.1Q NetIO component could not assign a VLAN Id to the given interface
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%L2-d1qnetio-4-DEBUG_INIT_ERROR An error occurred during debug initialization, err: [chars]
Explanation The 802.1Q NetIO component encoutered an error during debug initialization
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%L2-d1qnetio-4-DEVCTL_NOT_SUP Unsupported NetIO devctl code ([dec]) received
Explanation The 802.1Q NetIO component received an unexpected devctl code that has been ignored.
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%L2-d1qnetio-4-DLL_INIT_ERROR Unexpected DLL code ([dec]) during initialization
Explanation The 802.1Q NetIO component encoutered an error during DLL initialization
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%L2-d1qnetio-4-SUBBLOCK_REG_FAILED 802.1Q Netio failed to register the dot1q_ether subblock, err: [chars]
Explanation The 802.1Q NetIO initialization function failed to register the dot1q_ether subblock type.
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%L2-d1qnetio-4-TERM_FAILED 802.1Q NetIO termination failed because '[chars]', err: [chars]
Explanation The 802.1Q NetIO termination function 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%L2-d1qnetio-4-TRACE_INIT_ERROR A error occurred during trace initialization, err: [chars]
Explanation The 802.1Q NetIO component encoutered an error during trace initialization
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.
DI Messages
Error Message%L2-DI-3-CHANNELCREATE unable to create channel [chars] (Error code [int])
Explanation Process failed to create communication channel and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-CHKPT unable to create checkpoint service.
Explanation Process failed to create checkpoint service and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-COMMAND Three command line parameters required: depository_id promid (0/1/2/3)
Explanation Process received wrong third command line parameter and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-COMMAND3 Third command line parameter is [unsigned long int].It must be 0/1/2/3.
Explanation Process received wrong third command line parameter and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-CONNECTION Unable to connect to channel [chars] (Error code [int])
Explanation Process failed to connect to communication channel and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DESTINSANE Data structure destination organizer [chars] is inconsistent for destination [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DESTORG unable to create destination organizer.
Explanation Process failed to create destination organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DIDORG unable to create DID organizer.
Explanation Process failed to create DID organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLABSENT Driver DLL [chars] is absent on the platform.
Explanation A specific driver DLL is required to run certain hardware detected.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLORG unable to create DLL organizer.
Explanation Process failed to create DLL organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLSYMMISSING Driver DLL [chars] has missing symbol [chars].
Explanation A specific driver DLL is not correct.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-ENTRY One of the drivers unable to init.
Explanation Process unable to init one of the drivers and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-ERRORG unable to create error organizer.
Explanation Process failed to create error organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVE Failed to init event manager event.
Explanation Process failed to create event manager event and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVELOOP IM notify event manager loop exited (Error no=[unsigned long int]).
Explanation Process terminated event manager loop and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVEMGR Failed to create event manager.
Explanation Process failed to create event manager and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INCONSISTINSTHASH Data structure Instance Hash is inconsistent for instance id [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INCONSISTRSRCHASH Data structure Resource Hash is inconsistent for resource id [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INSTHASH unable to create instance hash.
Explanation Process failed to create instance hash and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INSTSTORE unable to create instance persistence store.
Explanation Process failed to create instance persistence store and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INTORG unable to create interrupt organizer.
Explanation Process failed to create interrupt organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MAINLINE Unable to create mainline ipc server.
Explanation Process unable to create mainline ipc server and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MUTEXINIT Mutex initialization error [chars] (Error code [int])
Explanation Process failed to initialize a mutex and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MUTEXLOCKFAIL [chars] operation failed in [chars]; reason [chars]
Explanation DI failed to lock the packet mutex.
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%L2-DI-3-NETIOEST NetIO failed to connect to driver_infra_partner and exiting..
Explanation The initial set up between two driver processes failed. NetIO exiting.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-OUTMEM malloc ([unsigned long int] bytes) from::[chars] failed.
Explanation Process failed to allocate run-time memory and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-PEERSTORE unable to create peer persistence store.
Explanation Process failed to create peer persistence store and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOMISSING No installed software to match Hardware in slot [unsigned long int] (PROMID [unsigned long int]).
Explanation Report missing driver registration.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOMISSING1 No installed software to match Hardware in I/O slot in route-processor [unsigned long int] (PROMID [unsigned long int]).
Explanation Report missing driver registration.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOORG unable to create registration organizer.
Explanation Process failed to create registration organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-RESIDORG unable to create RESID organizer.
Explanation Process failed to create RESID organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-RESOURCEHASH unable to create resource hash.
Explanation Process failed to create resource hash and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-SHMWIN failed to reserve the shmwin VM region.
Explanation Process failed to reserve the shmwin VM region and hence exiting.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-STARTCHKPT unable to start checkpoint service.
Explanation Process failed to start checkpoint service and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-STARTDESTORG unable to start destination organizer.
Explanation Process failed to start destination organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-SYNHORG unable to create synchronizer organizer.
Explanation Process failed to create synchronizer organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-THREADCREATE Unable to create thread [chars] (Error code [int])
Explanation Process failed to create thread and hence terminating.
Recommended Action 'No action is required.'
DIV2_DM Messages
Error Message%L2-DIV2_DM-3-INFO driver manager: service degrading error, reason = [chars]
Explanation Driver manager encountered an error that would lead to degraded service.
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%L2-DIV2_DM-3-INIT Driver manager: init. error encountered, reason=[chars]
Explanation Driver manager encountered an error and is not able recover frm it. A reason text will be supplied. Call support with this text.
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%L2-DIV2_DM-3-NO_MEM Driver manager: memory allocation error for bytes
Explanation Driver manager encountered a fatal memory allocation error
Recommended Action Reduce other system activity (e.g. by killing non-essential processes) to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DRIVERS_UTIL Messages
Error Message%L2-DRIVERS_UTIL-3-TUPLE_READ_ERROR [chars]: Tuple read failed with error [hex] [chars]
Explanation An error occured when trying to read the tuple from sysdb.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
DWDM Messages
Error Message%L2-DWDM-3-FATAL dwdm: fatal error encountered, reason=[chars]
Explanation dwdm encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
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%L2-DWDM-3-FATAL_2 dwdm: fatal error encountered, reason=[chars], errno=[dec]
Explanation dwdm code encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
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%L2-DWDM-3-INFO dwdm: service degrading error, reason = [chars]
Explanation The dwdm encountered an error that would lead to degraded service.
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%L2-DWDM-3-NOT_YET_IMPLEMENTED dwdm: this function is not yet implemented
Explanation dwdm, a function was not implemented.
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.
ETHER_NETIO Messages
Error Message%L2-ETHER_NETIO-6-DEBUG_REG Debug registration failed: [chars]
Explanation Debug message registration failed. No debugging of this component will be available, but it should otherwise function properly.
Recommended Action No action is required.
ether_spa_plugin Messages
Error Message%L2-ether_spa_plugin-6-OPTICS_OIR An Optics is [chars] for bay [dec] and port [dec]
Explanation The Optic Interface Module (OIM) for the specified port either has been inserted or removed.
Recommended Action No action is required.
Error Message%L2-ether_spa_plugin-6-UNSUPPORTED_OPTICS [chars] port [dec] security check failed . Disable
Explanation An Unsupported Optic Interface Module (OIM) for the specified port has been inserted .
Recommended Action No action is required.
ETHER Messages
Error Message%L2-ETHER-3-BDL_IIR_OP_FAILED The basecaps failed to process a bundle IIR [chars] message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the Ether basecaps is out of step with the bundle configuration.
Recommended Action Restart the ether_caps_partner process in an attempt to recover, or if this fails, detach and re-attach the physical member interface that the error was reported on by unconfiguring and reconfiguring the bundle member id.
Error Message%L2-ETHER-4-ERR_EVM_EVENT_BLOCK Failure during receipt of message. Error: [chars]
Explanation A failure occurred handling a message arriving at one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.
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%L2-ETHER-4-INIT Failure during intialisation of [chars] in a Ether basecaps process. Error: [chars]
Explanation A failure occurred during the initialisation of one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.
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.
ETHERNET Messages
Error Message%L2-ETHERNET-3-BDL_IIR_OP_FAILED The driver failed to process a bundle IIR [chars] message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the driver is out of step with the bundle configuration.
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%L2-ETHERNET-3-BIA_ERR [chars], for the port [dec], error: [chars]
Explanation A fatal error occurred during Ethernet Driver's initialization.
Recommended Action No action is required.
Error Message%L2-ETHERNET-3-CLIENT_API_REG_FAILURE Failed to create client evm, err: [chars]
Explanation A fatal error occurred during Ethernet Driver's initialization.
Recommended Action No action is required.
Error Message%L2-ETHERNET-3-INT_CREATE_ERROR [chars], after [dec] retries for port [dec], error: [chars]
Explanation A non-fatal error occurred during Ethernet Driver's initialization.
Recommended Action No action is required.
Error Message%L2-ETHERNET-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
Error Message%L2-ETHERNET-3-VLAN_DELETE_ERROR Failure whilst removing VLAN config from H/W (if [hex]), error: [chars]
Explanation An error occurred whilst removing some VLAN config from the H/W.
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%L2-ETHERNET-4-CLNT_DEBUG_INIT Failed to initialize the debugs in the ethernet client library, error: [chars]
Explanation A non-fatal error occurred whilst trying to initialize ethernet client library.
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%L2-ETHERNET-4-DEBUG_INIT_WARNING Initialization warning, operation: [chars], error: [chars]
Explanation A non-fatal error occurred during Ethernet Driver's initialization.
Recommended Action No action is required.
Error Message%L2-ETHERNET-4-REPLAY_WARNING Some hardware replay operations failed for [chars], error: [chars]
Explanation Some operations failed during the hardware replay on this interface. It is possible that the ethernet interface hardware state doesn't match the state configured in software.
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.
G709 Messages
Error Message%L2-G709-4-ALARM [chars]: [chars] [chars]
Explanation The specified G709 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
gulf Messages
Error Message%L2-gulf-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in gulf Driver which involves exiting the process.
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%L2-gulf-4-WARNING warning: [chars]: [chars]: [dec]
Explanation A warning condition is detected in gulf Driver which involves exiting the process.
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%L2-gulf-6-INFO_MSG Info: [chars]: [chars]: [dec]
Explanation This is a Informational message in the gulf driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-gulf-7-DEBUG_MSG Debug: [chars]: [chars]: [dec]
Explanation This is a debug message in the gulf driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
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.
IPCP Messages
Error Message%L2-IPCP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-IPCP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-IPCP-1-ERR_RIB_ROUTE_ADD Failed to add route into RIB; [chars]
Explanation An error was encountered while connecting to the RIB.
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%L2-IPCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-IPCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-IPCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
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%L2-IPCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the function.
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%L2-IPCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an error condition
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%L2-IPCP-3-ERR_EVENT_MGR_CREATE IPCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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%L2-IPCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation IPCP was unable to determine the state of the basecaps and has assumed it to be down. IPCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-IPCP-3-ERR_IPARM Error [chars] IP-ARM; [chars]
Explanation IPCP could not perform the operation with IP-ARM that was desired.
Recommended Action Restart the IPCP and IP-ARM processes. 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%L2-IPCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
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%L2-IPCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
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%L2-IPCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
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%L2-IPCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
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%L2-IPCP-3-ERR_MQ_CREATE Failed to create message queue to AAA; [chars]
Explanation IPCP has failed to open its mailbox channel to AAA.
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%L2-IPCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation IPCP has failed to open a mailbox channel.
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%L2-IPCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation IPCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate IPCP.
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%L2-IPCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation IPCP cannot perform some SysDB operation.
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%L2-IPCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation IPCP cannot (un)register for SysDB notification.
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%L2-IPCP-3-ERR_SYSDB_VERIFICATION Failed to [chars]register for SysDB verification of [chars]; [chars]
Explanation IPCP cannot (un)register for SysDB verification.
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%L2-IPCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
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%L2-IPCP-3-LTRACE_INIT IPCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IPCP-4-ERR_CHKPT Failed checkpoint [chars]
Explanation An error has occurred upon attempting to connect to the checkpointing server. This may cause inconsistent state to be present within IPCP.
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%L2-IPCP-4-ERR_CHKPT_ITERATE Failed iterating checkpoint store: [chars]
Explanation An error has occurred while iterating the checkpoint data store after a process restart. The process will exit and hope for a clear run next time. If failure persists its checkpoint store will be deleted and it will do a cold restart which should resolve the problem.
Recommended Action If multiple restarts does not work then 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%L2-IPCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
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%L2-IPCP-4-ERR_IM_ENCAPS Error checking base encapsulation for [chars]; [chars]
Explanation IPCP was unable to check the base encapsulation of an interface with IM. This may result in IPCP not running on the interface if PPP encapsulation was present.
Recommended Action If the interface that the error is reported for does not have PPP encapsulation then there is no problem. If the interface does have PPP encapsulation then first remove and re-add the IP address or IP unnumbered configuration. If this doesn't get IPCP working then remove and re-add the PPP encapsulation. If IPCP still does not work then 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%L2-IPCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
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%L2-IPCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation IPCP failed to allocate memory for a structure.
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%L2-IPCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation IPCP has failed to receive a message from its mailbox.
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%L2-IPCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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%L2-IPCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation IPCP failed to create an interface structure.
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%L2-IPCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation IPCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation IPCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation IPCP has failed a protocol operation with the interface manager.
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.
IPV6CP Messages
Error Message%L2-IPV6CP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-IPV6CP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-IPV6CP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-IPV6CP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-IPV6CP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
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%L2-IPV6CP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the function.
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%L2-IPV6CP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an error condition
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%L2-IPV6CP-3-ERR_EVENT_MGR_CREATE IPV6CP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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%L2-IPV6CP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation IPV6CP was unable to determine the state of the basecaps and has assumed it to be down. IPV6CP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-IPV6CP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
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%L2-IPV6CP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
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%L2-IPV6CP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
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%L2-IPV6CP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
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%L2-IPV6CP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation IPV6CP has failed to open a mailbox channel.
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%L2-IPV6CP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation IPV6CP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate IPV6CP.
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%L2-IPV6CP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation IPV6CP cannot perform some SysDB operation.
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%L2-IPV6CP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation IPV6CP cannot (un)register for SysDB notification.
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%L2-IPV6CP-3-ERR_SYSDB_VERIFICATION Failed to [chars]register for SysDB verification of [chars]; [chars]
Explanation IPV6CP cannot (un)register for SysDB verification.
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%L2-IPV6CP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
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%L2-IPV6CP-3-LTRACE_INIT IPV6CP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IPV6CP-4-ERR_CHKPT Failed checkpoint [chars]
Explanation An error has occurred upon attempting to connect to the checkpointing server. This may cause inconsistent state to be present within IPV6CP.
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%L2-IPV6CP-4-ERR_CHKPT_ITERATE Failed iterating checkpoint store: [chars]
Explanation An error has occurred while iterating the checkpoint data store after a process restart. The process will exit and hope for a clear run next time. If failure persists its checkpoint store will be deleted and it will do a cold restart which should resolve the problem.
Recommended Action If multiple restarts does not work then 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%L2-IPV6CP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
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%L2-IPV6CP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
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%L2-IPV6CP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation IPV6CP failed to allocate memory for a structure.
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%L2-IPV6CP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation IPV6CP has failed to receive a message from its mailbox.
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%L2-IPV6CP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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%L2-IPV6CP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation IPV6CP failed to create an interface structure.
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%L2-IPV6CP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation IPV6CP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPV6CP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation IPV6CP has failed an encapsulation operation with the interface manager.
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%L2-IPV6CP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation IPV6CP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPV6CP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation IPV6CP has failed a protocol operation with the interface manager.
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.
JDAM Messages
Error Message%L2-JDAM-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in JDAM Driver which involves exiting the PLIM process.
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%L2-JDAM-6-INFO_MSG [chars] [chars] [dec]
Explanation This is a Informational message in the JDAM driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-JDAM-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the JDAM driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
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.
LINK Messages
Error Message%L2-LINK-4-BERTSTATUS [chars] [chars]
Explanation The bert status of the link
Recommended Action None.
MAC_ACCOUNT Messages
Error Message%L2-MAC_ACCOUNT-4-INIT_WARNING Initialization warning, operation: [chars], error: [chars]
Explanation A non-fatal error occurred during the initialization of MAC accounting.
Recommended Action No action is required.
Error Message%L2-MAC_ACCOUNT-4-OOR_WARNING Resource limit hit for MAC accounting entries on this port: [chars]
Explanation The resource limit for MAC accounting entries on this port has been reached, no more MAC accounting entries will be accounted for. This error message is displayed when one or more MAC accounting entries fails to be added as a result of this out of resource condition.
Recommended Action Clear the ARP cache for this interface/node to remove stale entries and repopulate MAC accounting. Use the MAC accounting show command to identify the number of available accounting entries on the port.
MARVEL Messages
Error Message%L2-MARVEL-3-CHAN_CREATE Failed to create channel : [chars]
Explanation Failed to create marvel-test (driver) channel using event_manager_create.
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%L2-MARVEL-3-DEBUG_INIT Debug initialization failed
Explanation Initialization of the debug event 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%L2-MARVEL-3-DEBUG_REG Debug registration failed : [chars]
Explanation debug_register() call 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%L2-MARVEL-3-EVENT_MGR_FAIL [chars] : [chars]
Explanation Generic failure of any event manager API.
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%L2-MARVEL-3-MMAP Failed to map device address : [chars]
Explanation mmap() system call failed to map the device physical address.
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%L2-MARVEL-3-MSG_REPLY Failed to send reply message : [chars]
Explanation This error is reported when msg_reply() (LWM call) fails.
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%L2-MARVEL-3-NOMEM Failed to allocate memory
Explanation This error is reported when malloc()/calloc() type system call fails.
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%L2-MARVEL-3-OPEN Failed to open file [chars] : [chars]
Explanation This error is generated when the open() system call fails.
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%L2-MARVEL-6-RX_ASYNC_MSG Invalid asynchronous message received.
Explanation This error is generated when an invalid asynchronous message is received.
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.
MPLSCP Messages
Error Message%L2-MPLSCP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-MPLSCP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
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%L2-MPLSCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-MPLSCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-MPLSCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
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%L2-MPLSCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the function.
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%L2-MPLSCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an error condition
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%L2-MPLSCP-3-ERR_EVENT_MGR_CREATE MPLSCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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%L2-MPLSCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation MPLSCP was unable to determine the state of the basecaps and has assumed it to be down. MPLSCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-MPLSCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
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%L2-MPLSCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
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%L2-MPLSCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
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%L2-MPLSCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
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%L2-MPLSCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation MPLSCP has failed to open a mailbox channel.
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%L2-MPLSCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation MPLSCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate MPLSCP.
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%L2-MPLSCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation MPLSCP cannot perform some SysDB operation.
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%L2-MPLSCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation MPLSCP cannot (un)register for SysDB notification.
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%L2-MPLSCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
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%L2-MPLSCP-3-LTRACE_INIT MPLSCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-MPLSCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
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%L2-MPLSCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
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%L2-MPLSCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation MPSLCP failed to allocate memory for a structure.
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%L2-MPLSCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation MPLSCP has failed to receive a message from its mailbox.
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%L2-MPLSCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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%L2-MPLSCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation MPLSCP failed to create an interface structure.
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%L2-MPLSCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation MPLSCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-MPLSCP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation MPLSCP has failed an encapsulation operation with the interface manager.
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%L2-MPLSCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation MPLSCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-MPLSCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation MPLSCP has failed a protocol operation with the interface manager.
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.
ND Messages
Error Message%L2-ND-3-INIT Process initialisation failed. [chars]: [chars] ([hex])
Explanation There was a software error during process startup.
Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart, then take the following 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. If the process does not restart automatically, restart it manually. 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.
OSICP Messages
Error Message%L2-OSICP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-OSICP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
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%L2-OSICP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
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%L2-OSICP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the function.
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%L2-OSICP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an error condition
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%L2-OSICP-3-ERR_EVENT_MGR_CREATE OSICP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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%L2-OSICP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation OSICP was unable to determine the state of the basecaps and has assumed it to be down. OSICP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-OSICP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
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%L2-OSICP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
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%L2-OSICP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
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%L2-OSICP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
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%L2-OSICP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation OSICP has failed to open a mailbox channel.
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%L2-OSICP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation OSICP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate OSICP.
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%L2-OSICP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation OSICP cannot perform some SysDB operation.
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%L2-OSICP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation OSICP cannot (un)register for SysDB notification.
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%L2-OSICP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
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%L2-OSICP-3-LTRACE_INIT OSICP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-OSICP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
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%L2-OSICP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
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%L2-OSICP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation OSICP failed to allocate memory for a structure.
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%L2-OSICP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation OSICP has failed to receive a message from its mailbox.
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%L2-OSICP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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%L2-OSICP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation OSICP failed to create an interface structure.
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%L2-OSICP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation OSICP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-OSICP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation OSICP has failed an encapsulation operation with the interface manager.
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%L2-OSICP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation OSICP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-OSICP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation OSICP has failed a protocol operation with the interface manager.
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.
pm5315 Messages
Error Message%L2-pm5315-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in karachi Driver which involves exiting the process.
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%L2-pm5315-6-INFO_MSG Info: [chars]: [chars]
Explanation This is a Informational message in the karachi driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-pm5315-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the karachi driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
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.
pm5316 Messages
Error Message%L2-pm5316-3-FATAL_ERROR [chars](): fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in plim Driver which involves exiting the process.
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%L2-pm5316-4-WARNING [chars](): warning: [chars]: [chars]: [dec]
Explanation A warning condition occurred in plim Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
POS Messages
Error Message%L2-POS-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
PPP_FSM Messages
Error Message%L2-PPP_FSM-3-ERR_SOCKET [chars]: Socket [chars] failed; [chars]
Explanation There is a communication problem with the PPP socket.
Recommended Action Restart the ppp_socket process on the node where the error is reported. 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.
PPP_LCP Messages
Error Message%L2-PPP_LCP-3-MTU_UNUSABLE [chars] has an interface MTU of [unsigned int] which is smaller than the PPP packet header size ([unsigned int]) and so PPP cannot run on the interface
Explanation PPP has been informed that the interface MTU has been set to a value smaller than the PPP header size, which makes it impossible for PPP to operate.
Recommended Action Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required.
Error Message%L2-PPP_LCP-4-MISSING_AUTHENTICATION_LIST AAA authentication list [chars] is not defined for PPP
Explanation One or more PPP interfaces have been configured to authenticate the peer using the authentication list identified in the error message, but this authentication list has not been configured in AAA itself. As a result PPP will be unable to authenticate the peer and the line protocol on the relevant interface or interfaces will not come up.
Recommended Action Configure 'aaa authentication ppp ...'
Error Message%L2-PPP_LCP-4-MTU_WARNING [chars] has a PPP MTU of [unsigned int] which is smaller than the minimum value ([unsigned int]) required for correct operation
Explanation RFC 1661 requires that the media that PPP is running over is always able to receive PPP packets of sizes up to 1500 bytes (where this value excludes the 4 bytes of PPP header). This is to ensure that the peer can always send control protocol packets up to this size if they ever need to renegotiate. IOS-XR routers set their MRU to the same value as the MTU, and this message has been issued because the configured MTU is too small to meet the above condition.
Recommended Action Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required. Note that as most Control Protocol packets are much smaller than 1500 bytes, it is unlikely that MTU values which are smaller than 1500 bytes will actually cause problems, but this cannot be guaranteed.
Error Message%L2-PPP_LCP-4-UNRECOGNIZED_PROTO Unrecognized IfMgr protocol [chars] on [chars] (caps=[chars])
Explanation Interface Manager notified LCP about a protocol that it doesn't recognize, either by sending a request to LCP to adopt this node or by informing LCP that it exists. This is a programming error as LCP needs to recognized all of the protocols which run above it in order to be able to run the relevant CP.
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%L2-PPP_LCP-5-MTU_NEGOTIATED The PPP MTU for [chars] has been negotiated to be [unsigned int]. This is less than the configured PPP MTU of [unsigned int]
Explanation The PPP MTU is reduced when the PPP MRU of the peer is less than the PPP MTU derived from the locally configured interface MTU. The reduced value will be used until LCP is renegotated (such as when the interface goes down and comes back up, or a new MTU is configured), or if the PPP encapsulation is removed from the interface. The MTU then returns to the configured value and another message will indicate if a value less than the configured value is negotiated again. The reduced MTU is a normal part of PPP operation and is not indicative of any problems.
Recommended Action No action is required.
PPP_MA Messages
Error Message%L2-PPP_MA-4-ERR_AAA Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the AAA service. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary problem communicating with the AAA server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP 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%L2-PPP_MA-4-ERR_AIB Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the AIB server. 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 NetIO server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP 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%L2-PPP_MA-4-ERR_BAG Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Bag Client library. 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. The error will affect PPP MA's ability to provide operational management data, but won't otherwise affect PPP MA's operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_CHKPT Unexpected error encountered whilst [chars]: [chars]
Explanation PPP 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%L2-PPP_MA-4-ERR_CHKPT_CORRUPT Corrupt [chars] checkpoint record found: [chars]
Explanation Whilst restoring one of its checkpoint tables PPP MA found a corrupt checkpoint entry. The entry will be ignored and so the relevant interface's PPP session will be renegotiated after the restart and as a result there may be a short period where traffic is 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%L2-PPP_MA-4-ERR_CHKPT_DUPLICATE Duplicate [chars] checkpoint record found for [chars]
Explanation Whilst restoring one of its checkpoint tables PPP MA found multiple entries for the same interface. PPP 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%L2-PPP_MA-4-ERR_CLOCK Unexpected error encountered whilst retrieving the value of the [chars] clock: [chars]
Explanation PPP MA encountered an error whilst retrieving the value of the realtime clock. The error message includes details of the reason for the error. This is a fatal error and the PPP MA process will abort and be restarted to recover.
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%L2-PPP_MA-4-ERR_DEBUG Unexpected error encountered whilst [chars]: [chars]
Explanation PPP 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, PPP 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%L2-PPP_MA-4-ERR_EVC_CLOSE Error closing '[chars]' connection: [chars]
Explanation PPP 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%L2-PPP_MA-4-ERR_EVC_CREATE Error creating '[chars]' connection: [chars]
Explanation PPP 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%L2-PPP_MA-4-ERR_EVC_ERROR Error resetting '[chars]' connection: [chars]
Explanation After detecting an error with the connection to the specified service, PPP 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%L2-PPP_MA-4-ERR_EVC_EVM_HANDLER Error registering for data events on '[chars]' connection: [chars]
Explanation During initialization, PPP MA failed to register for input or output notifications 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%L2-PPP_MA-4-ERR_EVC_GET_FD Error retrieving the Connection ID from the '[chars]' connection: [chars]
Explanation PPP MA failed to retrieve the file descriptor associated with the specified service. This is an internal error.
Recommended Action Consider restarting the PPP 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%L2-PPP_MA-4-ERR_EVC_NOTIFY Error registering for critical events on '[chars]' connection: [chars]
Explanation During initialization, PPP 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%L2-PPP_MA-4-ERR_EVC_OPEN Error opening '[chars]' connection: [chars]
Explanation PPP 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%L2-PPP_MA-4-ERR_EVM_ATTACH Failed to register a handler for '[chars]' messages: [chars]
Explanation PPP MA failed to register a handler for the specified class of event. This is an initialization error and implies that PPP MA will not be able to operate correctly. The PPP 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 PPP MA process. *RECUR*
Error Message%L2-PPP_MA-4-ERR_EVM_CREATE Error creating the PPP MA Event Manager: [chars]
Explanation PPP 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%L2-PPP_MA-4-ERR_EVM_SEND Failed to send '[chars]': [chars]
Explanation PPP 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 PPP MA process. *RECUR*
Error Message%L2-PPP_MA-4-ERR_IMC Unexpected IfMgr error encountered whilst [chars]: [chars]
Explanation PPP 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, PPP 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%L2-PPP_MA-4-ERR_IP_ARM Failed to [chars] [chars]: [chars]
Explanation IPCP encountered an error using the IP-ARM API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv4_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_LAS Failed to [chars] [chars]: [chars]
Explanation IPV6CP encountered an error using the LAS API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv6_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_LTRACE Unexpected error encountered whilst [chars] the [chars] buffer: [chars]
Explanation PPP MA encountered an error using the Lightweight Tracing service. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP 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%L2-PPP_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%L2-PPP_MA-4-ERR_MGD_TIMER Unexpected error encountered whilst [chars]: [chars]
Explanation PPP 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 PPP MA process. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_PAK Error handling pakman corruption problem: [chars]. Process exiting.
Explanation The connection to packet manager was errored and the attempt to recover failed. Restarting the process should resolve the problem.
Recommended Action Restart the ppp_ma process. 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%L2-PPP_MA-4-ERR_SYSDB Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the SysDB service. The error message describes what operation has failed and why it failed. The most likely reason for this is a connection problem with the SysDB server, but the error could also be caused by low memory resources or programming error.
Recommended Action Consider restarting the PPP MA process. 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%L2-PPP_MA-4-ERR_SYSMGR Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error whilst communicating with SysMgr. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP MA process will abort and be restarted 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%L2-PPP_MA-4-ERR_WAVL_INIT Error initializing the WAVL tree used to store PPP MA IDBs: [chars].
Explanation PPP MA encountered an unexpected error which prevents it from functioning. 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.. *RECUR*
Error Message%L2-PPP_MA-6-ERR_EVC_DESTROY Error destroying '[chars]' connection: [chars]
Explanation During process termination PPP 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%L2-PPP_MA-6-ERR_EVM_EVENT_BLOCK Error blocking waiting for an event to process: [chars]
Explanation This is an unexpected error. The PPP MA process may recover by itself, or it may need to be restarted to recover.
Recommended Action Restart the affected PPP MA process. 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.
PPP_NETIO Messages
Error Message%L2-PPP_NETIO-3-ERR_INTF_INIT Failure initializing the PPP NetIO datapath for : [chars]%s
Explanation The PPP NetIO DLL failed to initialize the datapath for processing PPP packets on a particular interface because of an unexpected error. The message includes the exact cause of the failure. As a result, the capsulation will be unloaded from the interface and the interface will not be able to send or receive any PPP packets. One possible reason for the error is a low memory condition, particularly if the failure was in creating the interface descriptor.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration., and then remove and reconfigure the PPP encapsulation on the interface. 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%L2-PPP_NETIO-4-ERR_INIT Failure [chars] in the PPP NetIO DLL: [chars]
Explanation A failure occurred during an initialization operation in the PPP NetIO DLL. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user. One possible reason for the error is a low memory condition, particularly if the failure was in allocating trace buffers.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-PPP_NETIO-4-PAK_DROP Dropping [chars] packet on [chars] ([chars])
Explanation The PPP NetIO DLL has been forced to drop a packet because of an unexpected error. The error message describes the reason for the drop.
Recommended Action The system may recover by itself. If it doesn't then the error message will recur. In this case consider restarting the NetIO process on the affected linecard. If the error messages continue after restarting NetIO then 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%L2-PPP_NETIO-5-SUBBLOCK_VERSION Incompatible subblock version during upgrade. Data has version [unsigned int], but the version supported is [unsigned int]
Explanation When the PPP NetIO DLL was upgraded the existing data version was incompatible with the new software. NetIO will be restarted to recover the appropriate state.
Recommended Action This is not a problem, the message is just to explain why NetIO has restarted.
PPP_SOCK Messages
Error Message%L2-PPP_SOCK-3-ERR_EVM_EVENT_BLOCK Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process must exit.
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%L2-PPP_SOCK-3-ERR_LTRACE_INIT Failed to initialize the ltrace buffer. Error: [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-PPP_SOCK-3-ERR_MEM_ALLOC Unable to allocate [unsigned int] bytes
Explanation Not enough memory was available for the operation to complete.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-PPP_SOCK-3-ERR_PAKMAN Could not clean up and restart pakman connection. Error: [chars]. Control packet I/O will fail so restarting the socket process.
Explanation An unknown error occurred after a pakman disconnect event. Restarting the socket process should have resolved the problem.
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%L2-PPP_SOCK-3-ERR_SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
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%L2-PPP_SOCK-3-INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the process. This resulted in the restart of the process.
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.
Serial Messages
Error Message%L2-Serial-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
Error Message%L2-Serial-4-ALARM [chars]: [chars] [chars]
Explanation The specified Serial Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
SLARP_EA Messages
Error Message%L2-SLARP_EA-2-EVENT_BLOCK Failure during receipt of message. Error: [chars]
Explanation A failure occurred handling a message arriving at the SLARP capsulation EA process
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%L2-SLARP_EA-2-INIT Failure during intialisation of SLARP Caps EA. Error: [chars]
Explanation A failure occurred during the initialisation of the SLARP capsulation EA process
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%L2-SLARP_EA-3-ADJ_UPDATE_FAIL [hex]: unable to update adjacency : [chars]
Explanation Adjacency information was not able to be updated.
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.
SLARP Messages
Error Message%L2-SLARP-1-CAPS_ADD [chars]: Could not add slarp capsulation : [chars]
Explanation Could not add the slarp capsulation in IM
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%L2-SLARP-1-CAPS_REMOVE [chars]: Could not remove slarp capsulation : [chars]
Explanation Could not remove the capsulation in question.
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%L2-SLARP-1-CLOCK_READ_ERROR Unable to read the clock: [chars]
Explanation Unable to read the clock.
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%L2-SLARP-1-CONN_ALLOC Failed to allocate event connection with [chars].
Explanation An attempt to allocate a connection resource 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%L2-SLARP-1-CONN_NOTIFY Failed to attach event connection handler for [chars].
Explanation An attempt to attach a handler for an event connection 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%L2-SLARP-1-DEBUG_REGISTER Could not register for debug events : [chars]
Explanation An attempt ot register with the debug infrastructure failed. The failure cannot be handled, so the process will have exited and will be automatically restarted.
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%L2-SLARP-1-EVENT_CONN Unable to initialize slarp timers
Explanation Can not initialize the even channel used by slarp timers.
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%L2-SLARP-1-EVENTBLOCK event_block returned early : [chars]
Explanation An unexpected or erroneous return while waiting for events.
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%L2-SLARP-1-IM_STATEQUERY Failed to query IM interface state: [chars]
Explanation An attempt to query the interface state from IM 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%L2-SLARP-1-INVTIMER invalid timer [dec]
Explanation An error occurred attempting to transmit a SLARP packet.
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%L2-SLARP-1-NO_INITIAL_CONFIG Failed to get the initial configuration: [chars]
Explanation The initial configuration of the box was unable to be determined.
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%L2-SLARP-1-NOIDB [chars]: Event which we do not have record of
Explanation An internal software error occurred.
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%L2-SLARP-1-NORESOURCE [chars] failed to allocate resource in [chars]
Explanation An attempt to allocate a resource 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%L2-SLARP-1-TIMER_ALLOC [chars]: Could not allocate a timer for SLARP : [chars]
Explanation Could not allocate a timer. SLARP will not run on this interface.
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%L2-SLARP-1-TRACE_REGISTER Failed to register with tracing infrastructure: [chars]
Explanation An attempt to register with the tracing infrastrucure failed. The failure cannot be handled, so the process will have exited and will be automatically restarted. The root cause of the problem is likely to be with the tracing infrastructure, rather than with this process in particular.
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%L2-SLARP-1-TREE_INSERT [chars]: Could not insert interface into storage.
Explanation We could not store information about this interface.
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%L2-SLARP-5-OLDSEQ [chars]: Outdated sequence number [dec], current [dec]
Explanation A keepalive packet was received out of sequence with previous keepalives.
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%L2-SLARP-5-PKTLENGTH Invalid packet length [dec] recv on [chars], should be [dec]
Explanation An invalid SLARP packet was received.
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.
SONET_APS Messages
Error Message%L2-SONET_APS-4-WARNING [chars] - [chars]
Explanation A non-fatal error occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-4-WP_INFO Connection to [chars]%s [chars]
Explanation State change in the APS group internal communication system detected. Expected during transitory conditions at config changes, OIR, etc. The message contains info about the WP communication components affected.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-6-CONTACT [chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message%L2-SONET_APS-6-REQUEST_PREEMPTED APS group [dec] [chars] [dec]: preempted
Explanation The user external request is preempted.
Recommended Action Not Action requirements.
Error Message%L2-SONET_APS-6-UPDOWN [chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message%L2-SONET_APS-7-ERROR [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-7-NOMEM Not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.
SONET_LOCAL Messages
Error Message%L2-SONET_LOCAL-4-ALARM [chars]: [chars] [chars]
Explanation The specified SONET Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
SPA_FPD Messages
Error Message%L2-SPA_FPD-3-FATAL_ERROR [chars]
Explanation An internal system software error has occurred. This type of errors are in general SW bugs that are caused by providing wrong information to SPA FPD API.
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%L2-SPA_FPD-3-GET_IMG_ERROR [chars][[dec]]: [chars]
Explanation An image for an FPD could not be obatined so that it could be updated. The cause of the failure is indicated in the message.
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%L2-SPA_FPD-3-GET_VERSION_ERROR [chars][[dec]]: Failed to get FPD version information.
Explanation The version of the FPD could not be obtained from the specified SPA. The FPD information will not be available for the specified SPA. System processing will continue normally.
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%L2-SPA_FPD-3-SW_ERROR [chars][[dec]]: [chars]
Explanation An internal software error has occurred on the specified SPA.
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%L2-SPA_FPD-3-UPDATE_FAILED [chars][[dec]]: Failed to update FPD '[chars]' image
Explanation The update operation for the specified FPD image has failed.
Recommended Action Retry the operation to update the image. If the retry operation fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2-SPA_FPD-3-WRONG_OIR_STATE [chars][[dec]]: Cannot perform FPD image update on '[chars]' OIR state, it should be in '[chars]' OIR state
Explanation The FPD image update operation could not be performed because the specified SPA is not in the correct state. The correct OIR state for the SPA is specified in the message text.
Recommended Action Do not perform the update operation while the SPA is in the middle of a reload operation or while it is being initialized. Wait until the specified SPA is in the correct OIR state and retry the operation.
Error Message%L2-SPA_FPD-5-OFFLINE_NOTICE [chars][[dec]]: Changing operational status to offline for update of FPD image
Explanation An attempt has been made to temporarily change the operaional status of the SPA from online to offline before the image for the FPD could be updated on the target SPA. For some SPA types, this operation is required.
Recommended Action Ensure that you have redirected the traffic of the target SPA before performing this action, since the target SPA will require a power cycle operation after the image update for the FPD on the target SPA has been performed.
Error Message%L2-SPA_FPD-5-RELOAD_NOTICE [chars][[dec]]: Reloading the SPA for the updated FPD image(s) to take effect
Explanation Indicates the reloading operation of the SPA after the completion of the FPD image update opearation.
Recommended Action No action is required.
Error Message%L2-SPA_FPD-6-UPDATE_PASSED [chars][[dec]]: Successfully updated FPD '[chars]' image
Explanation The FPD image was updated successfully.
Recommended Action No action is required.
Error Message%L2-SPA_FPD-6-UPDATE_START [chars][[dec]]: Starting update of FPD '[chars]' image
Explanation The FPD update update operation has started for the specified image.
Recommended Action No action is required.
SPA_PLIM_SB Messages
Error Message%L2-SPA_PLIM_SB-3-FPD_GETVER_FAIL [chars][[dec]]: Failed to get FPD image version for [chars]
Explanation The FPD image version could not be retrieved from the SPA for the pogrammable device that is specified in the message text. This condition can occur if the system attempts to retrieve the version information while the SPA is not in the correct operational state.
Recommended Action Try to reload the affected SPA or physically remove and then insert the SPA to correct the problem. 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%L2-SPA_PLIM_SB-3-FPD_IMG_UPD_ERROR [chars][[dec]]: [chars] image update error ([chars])
Explanation The FPD image update operation for the indicated device has failed. The cause of the error is also indicated in the message.
Recommended Action Retry the image update operation and if it fails again, 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%L2-SPA_PLIM_SB-3-MSG_REPLY_FAIL [chars][[dec]]: Failed to reply a message ([chars])
Explanation A message to the specified SPA did not receive a reply. The reason for the failure is specified in the message.
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%L2-SPA_PLIM_SB-3-MSG_SEND_FAIL [chars][[dec]]: Failed to send message ([chars])
Explanation A message to the specified SPA could not be sent. The reason for the failure is specified in the message.
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%L2-SPA_PLIM_SB-3-OPEN_CH_FAIL [chars][[dec]]: Open channel for [chars] failed ([chars])
Explanation A communication channel could not be opened with the specified SPA. The reason for the failure is specified in the message.
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%L2-SPA_PLIM_SB-3-SW_ERROR [chars][[dec]]: [chars]
Explanation An internal software error has occurred for the specified SPA.
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.
SPA Messages
Error Message%L2-SPA-3-PLIM_HEARTBEAT_ERR [chars]: bay [dec] heartbeat failed, expected seq# [unsigned int] received seq# [unsigned int], Time since last message [dec]s
Explanation The IPC communication between local CPU and host in the specified slot indicated in the message is not functional. If the problem persists the SPA will be reloaded to recover from the failure.
Recommended Action If the problem persists, try to reseat the SPA. If reseating does not help, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%L2-SPA-3-SYSDB_ERROR [chars]
Explanation SPA Infrastructure SysDb 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%L2-SPA-4-CERR_REGISTRATION_FAILURE Registration of error strings failed with error [hex]
Explanation Error string reistration 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%L2-SPA-5-APPS_IMAGE_DOWNLOADING Downloading SPA Application Image ([chars])...
Explanation Downloading SPA Application image as indicated in the message
Recommended Action none.
Error Message%L2-SPA-5-APPS_IMAGE_ERROR Download SPA Application Image failed.
Explanation Failed to download the SPA Application image.
Recommended Action none.
Error Message%L2-SPA-5-APPS_IMAGE_SIZE_ERR SPA Application image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])
Explanation The size of the SPA Application image is too big.
Recommended Action none.
Error Message%L2-SPA-5-DOWNLOAD_METHOD_ERR SPA Download method [dec] not supported
Explanation The specified download method is not supported
Recommended Action none.
Error Message%L2-SPA-5-FILE_SIZE_ERR SPA File exceeds Rdisk size: File size ([dec]) Rdisk size ([dec])
Explanation The size of the SPA File is too big.
Recommended Action none.
Error Message%L2-SPA-5-OIR_ERROR [chars]
Explanation SPA related error as indicated in the msg
Recommended Action none.
Error Message%L2-SPA-5-OIR_INSERTED SPA discovered in bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message%L2-SPA-5-OIR_REMOVED SPA removed from bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_DOWNLOADING Downloading SPA OS Image ([chars])...
Explanation Downloading SPA OS image as indicated in the message
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_ERROR Download SPA OS Image failed
Explanation Failed to download the SPA OS image.
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_SIZE_ERR SPA OS image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])
Explanation The size of the SPA OS image is too big.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_EVENT_INIT_ERR SPA Init Event Server failed
Explanation Creating SPA event handling server failed.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_KA_INIT_ERR SPA Init SPA Keepavlie Handler failed
Explanation Creating SPA keepalive server failed.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_RELOADING Reloading [chars] in subslot [unsigned int] after heartbeat failure ...
Explanation Reloading SPA because of heartbeat failure.
Recommended Action none.
Error Message%L2-SPA-5-STATE_CHANGE SPA in bay [dec] [chars]
Explanation For displaying state of a SPA
Recommended Action none.
SPAMSG Messages
Error Message%L2-SPAMSG-3-ERR [chars]
Explanation SPA related error msg
Recommended Action none.
Error Message%L2-SPAMSG-6-INFO [chars]
Explanation SPA related info
Recommended Action none.
SRP Messages
Error Message%L2-SRP-3-ERR_DUP_MAC_ADDR [chars]: Duplicate mac addresses in topology
Explanation Another node on the ring is using the same MAC address as this node. This can effect traffic forwarding.
Recommended Action Correct the configuration of each node, where necessary, to ensure that each node uses a unique MAC address. Use the 'show srp topology' CLI to identify any nodes using the same MAC address.
Error Message%L2-SRP-3-ERR_MEDIA_SINGLE_RING [chars] SRR usage changed ([chars])
Explanation SRR ring usage is changed using Inner, Outer or Both rings. There are/were multiple faults (or user requests) on the ring causing potential loss of traffic/bandwidth.
Recommended Action Clear the cause of each fault/wrap on the ring. Use the 'show srp topology' CLI to identify which nodes are wrapped.
Error Message%L2-SRP-3-ERR_MEDIA_WRAP [chars] [chars] on side [char] ([chars])
Explanation The specified side of the interface has wrapped or unwrapped for the given reason. There is/was a fault (or user request) on the ring causing potential loss of traffic/bandwidth.
Recommended Action Clear the cause of the fault/wrap. Use the 'show srp ips' and 'show srp failures' CLI to determine the root cause of the fault (if still present).
Error Message%L2-SRP-3-ERR_SRR_VER_MISMATCH [chars] SRR version mismatch detected.
Explanation SRR has detected incompatible versions with other nodes on the ring and cannot inter-operate.
Recommended Action Update the software image on all nodes of the ring to the same SRR version.
Error Message%L2-SRP-6-INFO_SINGLE_NODE_TOPO [chars]: Single node in topology
Explanation The topology discovery resulted in a single node being found. This is most likely a transient condition during initial ring bring-up.
Recommended Action Verify that the condition is not transient by using 'show srp topology' CLI. Verify the interface is not physically looped back, meaning side A is connected to side B. Verify that the other nodes are not in PassThru mode (ADMIN DOWN). Verify that neither of the adjacent nodes have the same BIA address by using 'show interface srp' CLI. If a duplicate BIA address is found: 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.
STREE Messages
Error Message%L2-STREE-4-CONNECT_FAIL STP Server not available
Explanation stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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%L2-STREE-4-CREATE_FAIL STP Create Failed : [chars]
Explanation stp_process ran into errors while creating the spanning tree instance for control ethernet. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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%L2-STREE-4-MSGSEND_FAIL Message Send Failed : [chars]
Explanation stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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%L2-STREE-4-PORT_CREATE_FAIL Stp port creation fail : [chars]
Explanation Spanning tree port creation failed on the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Spanning tree port creation will be retried automatically. Check if the 'stp_process' is up and running if this error is encountered. 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%L2-STREE-4-SET_MACADDR_FAIL STP Set Mac Addr Failed : [chars]
Explanation MAC address assigned to the spanning tree was either invalid or was not able to be set for the spanning tree instance. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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%L2-STREE-4-START_FAIL Failed to start STP instance : [chars]
Explanation Spanning tree could not be started on the control ethernet for the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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.
T1E1 Messages
Error Message%L2-T1E1-2-NOMEM [chars]([dec]): not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.
Error Message%L2-T1E1-3-ERROR [chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of T1E1.
Error Message%L2-T1E1-4-ALARM [chars]: [chars] [chars]
Explanation The specified T1E1 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-T1E1-4-LOOPSTATUS [chars] [chars]
Explanation A configurable controller loopback status.
Recommended Action None.
Error Message%L2-T1E1-4-UPDOWN [chars]: [chars] [chars]
Explanation The specified T1E1 is operationally down due to alarm. Check alarm status using show controller t1 command on the cli.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-T1E1-4-WARNING [chars]([dec]): [chars] - [chars]
Explanation A non-fatal error occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of T1E1.
T3E3 Messages
Error Message%L2-T3E3-2-NOMEM [chars]([dec]): not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.
Error Message%L2-T3E3-3-ERROR [chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of T3E3.
Error Message%L2-T3E3-4-ALARM [chars]: [chars] [chars]
Explanation The specified T3E3 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-T3E3-4-FEAC [chars] [chars]
Explanation New Far End Alarm Code received.
Recommended Action None.
Error Message%L2-T3E3-4-LOOPSTATUS [chars] [chars]
Explanation A configurable controller loopback status.
Recommended Action None.
Error Message%L2-T3E3-4-UPDOWN [chars]: [chars] [chars]
Explanation The specified T3E3 is operationally down due to alarm. Check alarm status using show controller t3 command on the cli.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-T3E3-4-WARNING [chars]([dec]): [chars] - [chars]
Explanation A non-fatal error occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of T3E3.
vlan_netio Messages
Error Message%L2-vlan_netio-4-DEBUG_INIT_ERROR An error occurred during debug initialization, err: [chars]
Explanation The VLAN NetIO component encoutered an error during debug initialization
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%L2-vlan_netio-4-DLL_INIT_ERROR Unexpected DLL code ([dec]) during initialization
Explanation The VLAN NetIO component encoutered an error during DLL initialization
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.
vlea Messages
Error Message%L2-vlea-3-AIB_INIT_FAILED Failed during AIB initialization, err: [chars]
Explanation The VLAN EA process initialization failed whilst trying to connect to AIB.
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%L2-vlea-3-DEBUG_REG_FAILED Failed to register for debugging services, (err: [chars]).
Explanation It was not possible for the VLAN EA to register for debugging.
Recommended Action Restart the VLAN EA if debug support is required.
Error Message%L2-vlea-3-EVENT_BLOCK An error was received during event_block, err: [chars]
Explanation The VLAN EA restarted due to an error that it received during event block.
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%L2-vlea-3-IMP_INIT_FAILED Failed during IMP initialization, err: [chars]
Explanation The VLAN EA process initialization failed whilst trying to connect to IMP.
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%L2-vlea-3-IMP_REG_FAILED Failed to register for notifications with Imp, err: [chars]
Explanation The VLAN EA process failed to register with IMP for a required service.
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%L2-vlea-3-INIT_FAILED VLAN EA initialization failed, err: [chars]
Explanation The VLAN EA initialization 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%L2-vlea-3-NATIVE_VLAN_NOTIF Failed to generate a notification for the Native VLAN, err: [chars]
Explanation The VLAN EA process failed to generate a Native VLAN change notification due to the specified error. *SUPPORT*
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%L2-vlea-3-NETIO_INIT_FAILED Failed during NETIO initialization, err: [chars]
Explanation The VLAN EA process initialization failed whilst trying to connect to NetIO.
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%L2-vlea-3-NO_STATS VLAN EA failed to register with the stats server, err: [chars]
Explanation Tha VLAN component failed to register for the stats server. No VLAN sub-interface statistics will be gathered on the given linecard.
Recommended Action This error message indicates a likely failure in the stats server on the specified node. 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%L2-vlea-4-ERROR_DLL_REG_FAILED Failed to register the VLAN EA process error DLL, err: [chars]
Explanation The VLAN EA process failed to register its cerrno error DLL.
Recommended Action No action is required.
Error Message%L2-vlea-4-STATS_UPDATE_LOST Stats update failed for [unsigned int] VLAN interfaces. Error: [chars]
Explanation The VLAN component failed to push the final set of interface statistics for a batch of sub-interfaces before those sub-interfaces were removed from the linecard. Up to 30 seconds of statistics may have been lost.
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%L2-vlea-6-NO_MEM Out of memory mallocing [unsigned int] bytes
Explanation The VLAN EA process has run out of memory.
Recommended Action Install more memory
vlma Messages
Error Message%L2-vlma-3-ATTR_INIT_FAILED VLAN MA failed to initialize attribute support for [chars] on [chars], err: [chars]
Explanation The VLAN MA process could not initialize IM attribute support for an attribute on the specified interface.
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%L2-vlma-3-DEBUG_REG_FAILED Failed to register for debugging services, (err: [chars]).
Explanation It was not possible for the VLAN MA to register for debugging.
Recommended Action Restart the VLAN MA if debug support is required.
Error Message%L2-vlma-3-ENCAPS_CHANGE_FAILED Failed to change the basecaps of [chars] to the dot1q_demux caps, err: [chars]
Explanation The VLAN MA process couldn't replace the Ethernet basecaps to the dot1q_demux capsulation.
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%L2-vlma-3-EVENT_BLOCK An error was received during event_block, err: [chars]
Explanation An error was received during event block.
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%L2-vlma-3-IM_CONNECT_FAILED Failed to connect to IM, err: [chars]
Explanation The VLAN MA process failed to connect to the IM server.
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%L2-vlma-3-IM_INIT_FAILED Failed during IM initialization, err: [chars]
Explanation The VLAN MA process initialization failed whilst trying to connect to IM.
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%L2-vlma-3-INIT_FAILED VLAN MA initialization failed, err: [chars]
Explanation The VLAN MA initialization 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%L2-vlma-3-NETIO_CONNECT_FAILED Failed to connect to NetIO, err: [chars]
Explanation The VLAN MA process failed to connect to NetIO.
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%L2-vlma-3-NETIO_INIT_FAILED Failed during NetIO initialization, err: [chars]
Explanation The VLAN MA process initialization failed whilst trying to connect to NetIO.
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%L2-vlma-3-SET_SOURCE_MAC_FAILED Failed to set the source MAC address for [chars] in NetIO, err: [chars]
Explanation The VLAN MA process couldn't set the source MAC address for this interface in Netio. Sub-interface multicast traffic may not work.
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%L2-vlma-3-SUB_IF_CREATE_FAILED Failed to create sub interface [chars], err: [chars]
Explanation The VLAN MA process couldn't create the configured sub interface due to 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%L2-vlma-3-SUB_IF_DELETE_FAILED Failed to delete a batch of [unsigned int] sub-interfaces of [chars]
Explanation The VLAN MA process couldn't delete the configured sub interface due to 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%L2-vlma-3-VLAN_ID_DELETE_FAILED Failed to delete the VLAN Id on sub interface [chars], err: [chars]
Explanation The VLAN MA process couldn't delete the specified VLAN Id on the specified interface due to 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%L2-vlma-3-VLAN_ID_SET_FAILED Failed to set the VLAN Id [dec] on sub interface [chars], err: [chars]
Explanation The VLAN MA process couldn't set the specified VLAN Id on the specified interface due to 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%L2-vlma-4-ASYNC_HANDLER Couldn't install the default handler for async msgs, err: [chars]
Explanation The VLAN MA process couldn't install the default event handler for async msgs.
Recommended Action No action is required.
Error Message%L2-vlma-4-ATTR_NOTIF_LOST The IM attribute notification [dec] was lost, err: [chars]
Explanation The VLAN MA process failed to process the specified attribute notification due to an error.
Recommended Action No action is required.
Error Message%L2-vlma-4-ATTR_NOTIF_UNREG_FAILED VLAN MA failed to unregister for attribute notifications on [chars], err: [chars]
Explanation The VLAN MA process failed to unregister for notification of interface attribute changes on the specified interface.
Recommended Action This error message indicates an internal error, but it is unlikely to adversely affect the operation of the device. 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%L2-vlma-4-ATTR_OWNER_UNREG_FAILED VLAN MA failed to unregister as an attribute owner on [chars] sub-interaces, err: [chars]
Explanation The VLAN MA process failed to unregister for attribute owner support for an attribute on the specified interface.
Recommended Action This error message indicates an internal error, but it is unlikely to adversely affect the operation of the device. 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%L2-vlma-4-BULK_IM_HANDLER_FAILED The handling of a bulk [chars] notification failed on [chars] for [dec] out of a batch of [dec] interfaces
Explanation The bulk operation to process the IM notification for a batch of sub-interfaces failed.
Recommended Action No action is required.
Error Message%L2-vlma-4-BULK_IM_HANDLER_FAILED_ALL The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] interfaces, all err: [chars]
Explanation The bulk operation to process the IM notification for a batch of sub-interfaces failed.
Recommended Action No action is required.
Error Message%L2-vlma-4-BULK_IM_HANDLER_FAILED_BATCH The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] interfaces, err: [chars]
Explanation The bulk operation to process the IM notification for a batch of sub-interfaces failed.
Recommended Action No action is required.
Error Message%L2-vlma-4-DELETE_CONFIRM_FAILED The handling of a bulk [chars] notification failed to confirm the interface deletion for [dec] out of a batch of [dec] interfaces. Batch result: [chars]
Explanation The bulk operation by the VLAN MA process to confirm the deletion of several interfaces failed.
Recommended Action No action is required.
Error Message%L2-vlma-4-ERROR_DLL_REG_FAILED Failed to register the VLAN MA process error DLL, err: [chars]
Explanation The VLAN MA process failed to register its cerrno error DLL.
Recommended Action No action is required.
Error Message%L2-vlma-4-IM_ATTR_MSG_FAILED Failed to generate an IM attribute notification on [chars], err: [chars]
Explanation The VLAN MA process failed to generate an IM attribute notification on the interface specified.
Recommended Action No action is required.
Error Message%L2-vlma-4-IM_HANDLER_FAILED The handling of a [chars] notification failed on [chars] due to error: [chars]
Explanation The attempt to process the given IM notification failed due to the reason specified.
Recommended Action Depending on the specific operation that failed then this error could cause some of the VLAN infrastructure to be out of step. Hence the recommended action is to restart the 'vlan_ma' process at the given location that the error was generated from.
Error Message%L2-vlma-4-IM_RESTART_RESYNC_FAILED Could not syncronize interface data for ([chars]) with IM, err: [chars]
Explanation The VLAN MA process was not able to full resynchronize its owned data with IM. This may cause some lose of VLAN functionality on the VLAN trunk interface on which the error occurred.
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%L2-vlma-4-INIT_WARNING An error occurred during VLAN MA initialization, err: [chars]
Explanation The specified non fatal error occurred during VLAN MA initialization.
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%L2-vlma-4-MAIN_INTF_INIT_FAILED Failed to perform initialization of trunk interface [chars], due to the following error: [chars]
Explanation The VLAN MA process failed to initialize the specified trunk interface. No sub-interfaces of the specified trunk interface can be created.
Recommended Action No action is required.
Error Message%L2-vlma-6-NO_MEM Out of memory mallocing [unsigned int] bytes
Explanation The VLAN MA process has run out of memory.
Recommended Action Install more memory
Error Message%L2-vlma-6-RECOVERY_FAILED Failed to recover from resynchronization with another component for [chars], due to the error: [chars]
Explanation The VLAN MA failed to resynchronize its config with another component in the system after an earlier failure, or component restart.
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%L2-vlma-6-UNKNOWN_NODE_VLAN_LIMIT Failed to determine the maximum number of VLAN sub-interface that are allowed to be configured on the given node, error: [chars]
Explanation A failure occurred whilst trying to determine the maximum number of VLAN sub-interfaces that can be supported on the given node.
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%L2-vlma-6-UNKNOWN_TRUNK_VLAN_LIMIT Failed to determine the maximum number of VLAN sub-interface that are allowed to be configured on [chars], error: [chars]
Explanation A failure occurred whilst trying to determine the maximum number of VLAN sub-interfaces that can be supported on the given trunk interface.
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.
WAN_INARP Messages
Error Message%L2-WAN_INARP-2-INIT failed to initialize: [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
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%L2-WAN_INARP-3-CONFIG config error, [chars][[dec]]: [chars]
Explanation A configuration update has caused a problem inside the InARP code - InARP should continue but may have ignored the latest config change
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%L2-WAN_INARP-3-NOMEM possibly unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory 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%L2-WAN_INARP-3-UNKNOWN_EVENT recieved an unknown event: [dec]
Explanation The system must be sending messages we didn't register for. They will be ignored.
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%L2-WAN_INARP-3-UNKNOWN_FSMSTATE The fsm state ([dec]) is invalid
Explanation The FSM has got into an invalid state
Recommended Action Restart the SFRAR/SAAR processes (contain the InARP DLL) 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%L2-WAN_INARP-3-UNKNOWN_IDB recieved information about an unrecognised interface
Explanation A set of IDBs are kept with information on each interface. Somehow this information has become inconsistent with the system.
Recommended Action Restart the main process (containing the InARP DLL) 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%L2-WAN_INARP-3-UNKNOWN_IDBTYPE The type ([dec]) of this IDB is invalid
Explanation Information about InARP interfaces has become corrupted.
Recommended Action Restart the main processes (containing the InARP DLL) 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%L2-WAN_INARP-3-UNKNOWN_IFSTATE The if state ([dec]) is not handled
Explanation There is no action assigned to the if state change, and so nothing has been done when it was received.
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%L2-WAN_INARP-3-VCCLASS_IDB The IDB is not in synch with the vc-class information
Explanation A set of IDBs are kept with information on each FR interface. A set of VC-CLASSes are also kept and associated with the IDBs. Somehow this information has become inconsistent.
Recommended Action Restart the main process (containing the InARP DLL) 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%L2-WAN_INARP-4-UNKNOWN_INTF failed lookup of interface: [chars]
Explanation The system must be sending messages we didn't register for. They will be ignored.
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.
WAN_LIB_IFDB Messages
Error Message%L2-WAN_LIB_IFDB-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory 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%L2-WAN_LIB_IFDB-3-UNKNOWN_IDBTYPE unknown idb type: [dec]
Explanation The IDB type of this IDB is not recognised.
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.
WAN_LIB_VCC Messages
Error Message%L2-WAN_LIB_VCC-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory 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%L2-WAN_LIB_VCC-3-UNKNOWN_IDBTYPE unknown idb type: [dec]
Explanation The IDB type of this IDB is not recognised.
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.
