P2IPC through RADIX
Available Languages
Table Of Contents
PLATFORM_CATALYST2940 Messages
PLATFORM_CATALYST2950 Messages
PLUGGABLE_TRANSCEIVER Messages
P2IPC Messages
Error Message%P2IPC-3-BUFSZERR : [chars](): Failed to get padding size for chunk data size [dec] errno [dec], [chars], line [dec]
Explanation An internal error has occurred. The padding size could not be determined for the specified chunk data size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPDETACHERR : Failed to detach Endpoint from Endpoint chain, [chars], line [dec]
Explanation An endpoint could not be detached from the endpoint chain.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPIDINVALID : [chars]() An invalid P2IPC_COM_EPID of [hex] was passed as an argument.
Explanation An invalid FIPC communications endpoint ID has been passed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMALLOCERR : [chars]() Failed to alloc mem for CommEp array (lstSize [dec], arraySize [dec]), errno [dec]
Explanation Memory for a communications endpoint array could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMEMAREAERR : [chars]() Insufficient memory for Comm Ep array: Want [dec], [dec] ; Got [dec], [dec]
Explanation Insufficient memory was available for a communications endpoint array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMGRSEMGIVE : [chars], [dec]
Explanation An error occurred while the communications endpoint manager semaphore was being released.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMGRSEMTAKE : [chars], [dec]
Explanation An error occurred while the communications endpoint manager semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPNAMEINVAL : Communication Endpoint's [hex] global name [chars] too long, [chars], line [dec]
Explanation The global name for the communication endpoint is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPRPLYEPDINV : [chars]() Couldn't get task's Sync Rply Epid, errno [dec]
Explanation The task synchronization reply endpoint ID could be not obtained.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMCREATE : Error [hex] creating EPID semaphore for task [dec]
Explanation An error occurred while the endpoint ID semaphore was being created for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMDEL : Error [hex] deleting P2IPC semaphore [hex] for task [dec]
Explanation An error occurred while the MGX-8850 semaphore was being deleted for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMGIVE : Error [hex] giving EPID semaphore [hex] for task [dec]
Explanation An error occurred while the endpoint ID semaphore was being given for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMINVALID : Invalid EndPoint semaphore in function [chars]
Explanation An invalid semaphore was detected in a communications endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMTAKE : [chars] Error [hex] taking EPID semaphore [hex] for task [dec]
Explanation An error occurred while an endpoint ID semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CONNADD_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], connType=[dec]
Explanation An spiConnAdd action has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CONNDEL_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec]
Explanation An spiConnDel action has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTCEVTREGFAIL : [chars] - CTC Event Registration failed, event [hex], rc [hex], errno [dec]
Explanation CTC event registration failed for the event specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTCSTATETRAFAIL : [chars] - CTC state transition failed, event [hex], rc [hex], errno [dec]
Explanation CTC state transition failed for the event specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTATESETERROR : Epid [hex]
Explanation A Bind request is in an invalid state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL1 : [chars](): Epid [hex]: Bind state failed, error [hex] sending to Name Svr
Explanation A Bind request failed because an error occurred while the request was being sent to the name server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL2 : [chars](): Epid [hex]: Bind state failed, error [hex] - out of mblks
Explanation The state of a Bind request has failed because of an outage of memory blocks.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL3 : [chars](): Epid [hex]: error [hex] binding global name
Explanation A Bind request failed because the request was invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLCOMEPERR : [chars]() Error [hex] instantiating P2IPC Control Port
Explanation An error occurred while the FIPC control port was being instantiated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLEPWAITERR : [chars](): Error [hex] exiting from EP Wait handler
Explanation An error occurred while the FIPC was exiting from the EP wait handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLHDLRATTCHERR : [chars]():Error [hex] attaching EP Wait handler to IPC Ctl queue
Explanation An error occurred while the FIPC was attaching an EP wait handler to an IPC control queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLINVIPCVER : [chars](): Ipc Version of Remote Card [dec] is different
Explanation A message could not be sent to a remote card because the IPC version of the remote card is different from the IPC version for this card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLINVRMTCTLMSGVER : [chars](): Remote Card IPC CtlMsg Version Invalid
Explanation A message could not be sent to a remote card because the IPC control version of the remote card is different fromthe IPC control version for this card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLMAXBUFRPLYERR : [chars](): Error in Replying to Query for MaxBufSize, error [dec]
Explanation An attempt to reply to a remote card query for the buffer size has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLRCVEPIDERR : [chars]() Error getting caller task's Receive Sync Epid
Explanation An error occurred while the system was attempting to obtain the synchronization endpoint ID for the caller task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLRETXQERR : [chars](): Error [hex] initializing P2IPC Retransmission Queue
Explanation An error occurred while the FIPC retransmission queue was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLSYNCTMRERR : [chars](): Error [hex] initializing P2IPC Sync Timer
Explanation An error occurred while an FIPC synchronization timer was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLUNBINDSTFAIL1 : [chars](): Epid [hex]: UnBind state failed, error [hex] sending to Name Svr
Explanation A send request to the name server has failed . This condition caused an Unbind request to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILECLOSEFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation An error occurred while the FIPC was attempting to close a file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEINVALID : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation The specified file is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEOPENFAIL : [chars], errno is [dec], fileName is [chars], [chars], line [dec]
Explanation The specified file could not be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEREADFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation The specified file could not be read.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILESEEKFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation An error occurred while the FIPC was attempting to find the specified file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEWRITEFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation A write operation failed for the file specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-HIGHMSGQDEAD : P2IPC message High queue, queue [hex] is dead, [chars], line [dec]
Explanation The FIPC message High queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-INVHWIDB : Invalid HWIDB Value: [hex] , [chars], line [dec]
Explanation An invalid hardware IDB was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-INVNUM : [chars], line [dec]
Explanation An invalid number was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNALREADYBOUND : Bind failed: LCN [dec] already bound by [hex], [chars], line [dec]
Explanation A Bind attempt failed because the LCN is already bound by the task ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNBIND_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], lcn=[dec], epid=[hex], hanle=[hex], offset=[hex], option=[hex]
Explanation A ssiIpclcnBind attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNUNBIND_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], lcn=[dec]
Explanation An ssiIpclcnUnbind attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LINKMEMALLOCERR : Failed to allocate memory for link cfg table (num links [dec]), [chars](), line [dec]
Explanation Memory could not be allocated for the link configuration table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LOWMSGQDEAD : P2IPC message Low queue, queue [hex] is dead, [chars], line [dec]
Explanation The FIPC message Low queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKALLOCFTLERR : [chars]() Fatal error [dec] allocating floating mblk, mblk control corrupted ,
Explanation A fatal error occurred while a floating memory block was being allocated. This condition indicates that the memory block control was corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKASSIGNFAIL : Message assignment failed: [chars]() [hex], [chars], line [dec]
Explanation A message assignment has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBPOOLCRTERR : Failed to create P2IPC buffer pool(buf size [dec], num bufs [dec]), [chars](), line [dec]
Explanation An FIPC buffer pool could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBUFDESCERR : [chars]() Failed to alloc P2IPC buffer descriptor memory (num buf desc [dec]),
Explanation An FIPC buffer could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBUFFREEFAIL : [chars]() Failed to free data buffer [hex], errno [dec]
Explanation The FIPC could not free a data buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKFREEFAIL : [chars]() Failed to free mblk [hex], errno [dec]
Explanation A memory block could not be freed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKINVALID : [chars]() Invalid message descriptor
Explanation FIPC has detected an invalid message descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKMPOOLCRTERR : [chars]() Failed to create P2IPC mblk pool (tot. mblks [dec], fltg. mblks [dec])
Explanation An FIPC memory block pool could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKNOHDRSPACE : [chars] No space for header, errno [dec], Wanted [dec], Got [dec]
Explanation There is no space for a header.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQCREATEFAIL : [chars]() Failed to create P2IPC message queue, error [dec]
Explanation An FIPC message queue could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQDEAD : [chars]() P2IPC message queue, line [dec]
Explanation The FIPC message High queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQDELETEFAIL : [chars] Failed to delete P2IPC message queue, queue [hex], errno [dec]
Explanation The FIPC message queue could not be deleted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQEVENT : P2IPC MsgQ Event: [chars], queue [hex], parameters [hex], [hex], [hex], [hex], [chars], line [dec]
Explanation A message queue event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQFULL : [chars], line [dec], [chars], line [dec]
Explanation The message queue is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEARRAYFULL : P2IPC Name Server name array is full, [chars], line [dec]
Explanation The FIPC name server name array is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMECOMEPCREATE : Failed to instantiate name Server Comm endpoint, errno [dec], [chars], line [dec]
Explanation The name server communications endpoint could not be instantiated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEENTRYINIT : Failed to initialize Name Server name entry, [chars], line [dec]
Explanation A Name Server name entry could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEINVMSGVER : Invalid message version [hex], arg [hex], [chars], line [dec]
Explanation An invalid IPC message version has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEMEMALLOC : Failed allocate memory forUnrecognized format ` %,' maxNumNames [dec], [chars], line [dec]
Explanation FIPC failed to allocate memory for a global name array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEMSGALLCFAIL : Failed to allocate BIND/RESOLVE ACK message, [chars], line [dec]
Explanation A Bind or Resolve acknowledgment message could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMESRCSLOTINV : Name Server BIND Rqst from slot [dec]: Epid's srcPhySlotId [dec], [chars], line [dec]
Explanation A Bind request is invalid because of a slot mismatch.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMETASKCREATE : Failed to create Name Server task, errno [dec], [chars], line [dec]
Explanation A name server task could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NUMCOMEPINVALID : [chars]() Desired number of Comm Eps [dec] exceeds the system limit [dec], errno [dec]
Explanation The number of available endpoint IDs in the system has been exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCBASEINITFAIL : Failed to initialize P2IPC Buffers , [chars], line [dec]
Explanation FIPC buffers could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCINITFAIL : Failed to initialize P2IPC , [chars], line [dec]
Explanation FIPC could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCLINKINITFAIL : Failed to initialize Link Parameters , [chars], line [dec]
Explanation Link parameters cannot be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PAKINVALID : Invalid PakType, [chars](), line [dec]
Explanation The specified packet is of an invalid type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PARMINVALID : [chars], at address [hex], [chars], line [dec]
Explanation An invalid parameter has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PARMOUTOFRANGE : Invalid parameter [chars], value is [dec], [chars], line [dec]
Explanation The value of the specified parameter is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-REBINDERROR : [chars](): Event Type is [dec]
Explanation The specified event type is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-RETXQSGUNLKFAIL : Failed to unlock timer signal, errno [dec], [chars], line [dec]
Explanation The timer signal could not be unlocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-RETXQSIGLCKFAIL : Failed to lock timer signal, errno [dec], [chars], line [dec]
Explanation The timer signal could not be locked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-SYNCCTXTCLNERR : [chars]() Failed to cleanup sync context for epid [dec], errno [dec]
Explanation The synchronization context for the endpoint ID could not be cleaned up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKENTRYGETFAIL : Error getting task entry for task [dec], [chars], line [dec]
Explanation An error occurred while a task entry was being obtained.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKINITFAIL : Error initializing task entry for task [dec], [chars], line [dec]
Explanation An error occurred while a task entry was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMCREATE : Error [hex] creating Task semaphore for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMDEL : Error [hex] deleting P2IPC semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being deleted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMGIVE : Error [hex] giving Task semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMINVL : Invalid Task semaphore [dec], [chars], line [dec]
Explanation An invalid task semaphore has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMTAKE : Error [hex] taking Task semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TIMERERROR : Error processing Timer, [chars], line [dec]
Explanation An error has occurred in processing the timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-UNEXPECTEDEVENT : [chars], [dec], [chars], line [dec]
Explanation A major software process event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPALLOCFAIL : [chars]() Failed to allocate a P2IPC Comm. endpoint [hex]
Explanation A FIPC communications endpoint failed to be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPDELETED : [chars]() Non-existing CommEp [hex] has invalid tag [dec]; Expected tag is [dec]
Explanation A communications endpoint does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPFREEFAIL : [chars]() Failed to free an P2IPC Comm Endpoint [hex]
Explanation An FIPC communications endpoint could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPNAMESCOINV : [chars]() Name Scope [dec] is invalid
Explanation The name scope of the communication endpoint is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPOWNERINVAL : [chars]() Communication Endpoint [hex]: access by non-owner task
Explanation The communication endpoint is being accessed by a non-owner task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPTYPEINVAL : [chars]() Communication Endpoint [hex]: invalid type [hex]
Explanation The specified communication endpoint is not an IPC plain asynchronous endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CONNREF_INVALID : ssi ipc connRef: [chars]() line no [dec] connRef=[dec]
Explanation An invalid connection reference has been received by the SSI IPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLALLOCMSGFAIL : [chars]() Error [hex] allocating message
Explanation An error occurred while a message was being allocated.
Recommended Action No action is required.
Error Message%P2IPC-4-CTLBINDSTUNKN1 : [chars](): Epid [hex]: Bind st. unknown, error [hex] sending duped BIND Rqst
Explanation An unknown error was encountered while a duplicate Bind request was being sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN2 : [chars](): Epid [hex]: Bind state unknown, error [hex] receiving BIND Ack
Explanation The system was in an unknown Bind state while a Bind acknowledgment message was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN3 : [chars](): Epid [hex]: Bind state unknown, error [hex] putting BIND Rqst on RetxQ
Explanation The system was in an unknown Bind state while a Bind request was being placed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN4 : [chars](): Epid [hex]: Bind st unknown, unknown sts [hex] in BIND Ack, errno [dec]
Explanation A Bind acknowledgment message is in an unknown Bind state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN5 : [chars](): Epid [hex]: Bind state unknown, error [hex] retransmitting BIND Rqst
Explanation The system was in an unknown Bind state while a Bind request was being retransmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLDUPMSGFAIL : [chars]() Error [hex] duplicating message
Explanation An error occurred while a message was being duplicated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLINVMSGTYPE : [chars](): Invalid P2IPC Ctl msg type [hex], arg [hex]
Explanation The message is an invalid FIPC control message type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLINVMSGVER : [chars](): Invalid P2IPC Control msg version [hex], arg [hex]
Explanation The message contains an invalid FIPC control message version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLOUTOFMBLKS : [chars](): P2IPC Control could not allocate mblk
Explanation The FIPC control could not allocate a memory block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLRCVMSGERR : [chars](): Error [hex] receiving P2IPC Ctl message
Explanation An error occurred while an FIPC control message was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLTSKCREATEERR : [chars](): Error [hex] creating P2IPC Control Task
Explanation An error occurred while an FIPC control task was being created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLUNBINDSTUNKN1 : [chars](): Epid [hex]: UnBind st. unknown, error [hex] sending duped UNBIND Rqst
Explanation A duplicate Unbind request was sent while the system was in an unknown unbind state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-DBUFSIZEINVALID : Requested data buffer size [dec] exceeds system max buffer size, [chars](), line [dec]
Explanation The requested data buffer size exceeds the maximum buffer size of the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPHNDLRATTACHED : [chars]() Com Ep [hex] already has EP Handler attached
Explanation The communication endpoint already has an EP handler attached.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPHNDLRFAIL : [chars]() P2IPC EPHandler [hex] on Ep [hex] returning sts [hex], errno [dec]
Explanation An error was returned by the FIPC endpoint handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPWAITEXTINVPRM : Status parameter [hex] to ssiIpcComEpWaitExit is invalid, [chars](), line [dec]
Explanation The ssiIpcComEpWaitExit function has received an invalid status parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-ISRNOTCALLABLE : Attempt to take P2IPC semaphore [hex] from interrupt routine
Explanation An attempt was made to remove an FIPC semaphore from an interrupt routine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNEPIDINVALID : Bind failed: LCN [dec], epid [hex] invalid, [chars], line [dec]
Explanation A Bind attempt has failed because the LCN endpoint ID is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNMSGSENDERROR : Failed to send msg on LCN [dec] to epid [hex], errno [dec]
Explanation A message could not be sent on the LCN to the endpoint ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNNOTBOUND : LCN [dec] is not bound
Explanation The LCN is not bound.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNOUTOFRANGE : LCN [dec] out of range , [chars], line [dec]
Explanation The LCN is outside of the normal range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNOWNERINVALID : LCN [dec] owned by [hex]: access by non-owner task [hex]
Explanation The LCN is being accessed by a non-owner task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNSARREGFAILED : Bind Failed: LCN [dec] failed SAR registration, errno [dec], [chars], line [dec]
Explanation The LCN failed while SAR registration was occurring. This condition caused a Bind operation to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNSARUNREGFAIL : Unbind Failed: LCN [dec] failed SAR unregistration, errno [dec], [chars], line [dec]
Explanation An Unbind attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKINERROR : [chars]() Link rcv error [hex], link [hex]; Got [hex], Expected [hex]
Explanation An FIPC link receive error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKOUTERROR : [chars](), line [dec], FIPC Link snd error: Expected [hex], Got [hex]
Explanation An FIPC link send error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKPLFMSLOT2RX : Platform cannot translate RxLcn for slot [dec], [chars], line [dec]
Explanation The platform cannot translate the Rx LCN.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKSARREGERROR : Error [hex] registering link [dec] SAR (slot [dec]), [chars], line [dec]
Explanation An error occurred while a link was being registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-MBLKENQUEUED : [chars]() Epid [dec]; mbPtr [hex] already freed, mbPtr-next is [hex], mbPtr-datap is [hex], ownerTask is [dec]
Explanation The specified memory block is already enqueued and in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-MBLKUNAVAILABLE : [chars] No mblk available for a buffer - mblk pool corrupted
Explanation No memory block is available for a buffer because the memory block pool is corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEENTRYBNDINV : Returned name entry [hex] out of name array bounds [hex]-[hex], [chars], line [dec]
Explanation The FIPC has returned a name entry out of a name array boundary.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEENTRYOVRRID : Name entry [chars] epid [hex] overriden with epid [hex], [chars], line [dec]
Explanation The name entry of an endpoint ID has been overridden by another endpoint ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEINVMSGTYPE : Invalid message type [hex], arg [hex], [chars], line [dec]
Explanation An invalid IPC control message type has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMENOENTRYOUT : No outstanding name entry [hex] in name array, [chars], line [dec]
Explanation No outstanding name entry exists in the name array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQMQCHAINERR : [chars]() [chars] [chars]: Retxq [hex] Got [hex], Expected [hex]
Explanation The message is not the first message in the chain.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQTIMERSET : [chars]() [chars]: RetxQ [hex]: timer set error [hex]
Explanation An error occurred while the time was being set for the queue during message retransmission.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQTIMRCANCEL : [chars]() [chars]: RetxQ [hex]: timer cancel error [hex]
Explanation An error occurred because the queue timer was being canceled while a message was being retransmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RSLVACKERR : [chars](): Received msg [hex] instead of RESOLVE ACK, arg [hex]
Explanation A Resolve acknowledgment should have been received; instead, the message itself was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RSLVNAMELENERR : [chars](): Requested P2IPC Global Name '[chars]' too long (max name len [dec] )
Explanation The name that is to be resolved is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SENDERROR : P2IPC Message Send error to Epid [hex], Message pointer is [hex], [chars](), line [dec]
Explanation An FIPC error occurred while a message was being sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SMSLOTERROR : Error [hex] and SM slot no passed is [dec], [chars], line [dec]
Explanation An error occurred in the specified SM slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCCTXTINUSE : [chars]() Sync context in use in Comm Epid [dec]
Explanation The synchronization context for the specified endpoint ID is already in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCINVALIDRPLY : [chars]() Invalid sync reply on epid [chars], Epid [hex] ([hex]), SeqNum [dec] ([dec])
Explanation An invalid synchronization reply was received on an endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCNOTSYNCRPLY : [chars]() Received msg not Sync Reply on epid [chars]
Explanation A synchronization message was expected to be received on the endpoint, but another message was received instead.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-TIMEREVENT : Timer Event, [chars], line [dec], task [dec], timeout [dec]
Explanation The process timed out while it was waiting for a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC_TRACE-0-0 : Fast IPC Trace Messages
Explanation This messages provides trace messages for FIPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PA Messages
The following are port adapter (PA) messages.
Error Message%PA-0-RUPTCONFLICT : Conflict detected when trying to install %s interrupt handler, bay %d.
Explanation An attempt was made to register an interrupt handler for either a non existent port adaptor or the wrong interrupt prority level.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADDAT : PA interface data incorrect, %#x
Explanation Incorrect PA interface data found
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADIDB : PA interface idb incorrect, %#x
Explanation The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADINTERFACE : Out of range PCI Port Adaptor interface, %d on bay %d
Explanation The software specified an out-of-range port adapter interface.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADPA : PA interface pa incorrect, %#x
Explanation Incorrect PA interface specified
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADPA2 : PA null adapter, %#x
Explanation Null PA interface specified
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADPABAY : Out of range PCI Port Adaptor bay %d
Explanation The software specified an out-of-range port adapter bay.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADPASCB : PA interface pascb incorrect, %#x
Explanation The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADPINST : PA interface port_inst incorrect, %#x
Explanation Failure to access port instance internal data.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-BADVCONT : PA interface vcont incorrect, %#x
Explanation Incorrect VC interface specified.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-ILLEGALPA : Illegal Port Adaptor type %d in bay %d of %s.
Explanation The port adapter is not supported by the controller to which it is plugged into.
Recommended Action Remove the port adapter and return the controller to its original configuration.
Error Message%PA-2-INCORRECTBRIDGEREG : Bad default register(%x) setting(%x) in PA bridge
Explanation The software is unable to configure certain settings for the port adapter protocol control information bridge in the specified bay.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-PABRIDGE : Failed to config bridge for PA %d
Explanation The system side PCI bridge for this PA failed initialization. The PA will not be operational because of this.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-PARECUR : Recursive loop while getting the daughtercard info for PA type %d
Explanation While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-PCIPARITY : Port Adaptor Detected Parity Error in slot [dec]
Explanation PCI integrity issue - Network Module will not work properly on this slot
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-QOVERFLOW : PA queue overflow, cmd %#x
Explanation PA queue has overflowed; programming lost
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-UNDEFIO : Unsupported I/O Controller (type %d) in I/O Bay. The I/O Controller network interfaces will be unavailable.
Explanation The software does not have a driver for the port adapter type in the specified bay.
Recommended Action Make sure the image you are running is supposed to support this card. Newer I/O Controllers will only work with the -kboot- image. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-UNDEFPA : Undefined Port Adaptor type %d in bay %d
Explanation The software does not have a driver for the port adapter type in the specified bay.
Recommended Action Make sure the image you are running is supposed to support this card. Check that the card is properly seated. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-UNDEFPABRIDGE : Unsupported Port Adaptor Bridge [hex] in bay [dec]
Explanation The software does not have a driver for the port adapter protocol control information bridge in the specified bay.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PA-2-UNDEFWIC : Undefined WIC Adaptor type [dec] in bay [dec]
Explanation The software does not have a driver for the type of WIC adapter that is in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-BRINGUPFAIL : port adapter in bay [%d] failed to reset.
Explanation An attempt to reset and initialize the port adapter timed out.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PA-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
Error Message%PA-3-DEACTIVATED : port adapter in bay [%d] powered off.
Explanation The port adapter is being powered off.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PA-3-IMPROPER_INSERT : Improper insertion for slot [dec]. Remove and then re-insert the PA
Explanation The PCI activation of the PA has failed. The PA has been deactivated.
Recommended Action Remove the PA and then reinsert it firmly into the slot.
Error Message%PA-3-MODULE_COUNT : The number of PA([hex]) in the system exceeds the supported configuration. The system supports a maximum of [dec] PA.
Explanation The number of port adapters currently in the systemare more than that allowed.
Recommended Action Remove the extra port adapters and reload the router.
Error Message%PA-3-NOTSUPPORTED : PA in slot%d (%s) is not supported on this %s
Explanation This port adaptor is not supported on this chassis/cpucard.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-3-PACREATE : Unable to create driver for Port Adaptor type %d in bay %d
Explanation Possible memory shortage or adaptor hardware error
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-3-REVNOTSUPPORTED : PA in slot%d (%s) requires base h/w revision of (%d.%d) for this %s
Explanation A newer hardware revision of the port adaptor is required for functional operation on this chassis.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-3-SLOTNOTSUPPORTED : This PA type ([chars]) is not supported in slot[dec] of this [chars]
Explanation This port adapter is not supported on the specified slot of this chassis or CPU card.
Error Message%PA-4-IMPROPER_REMOVAL : Improper removal for slot %d.
Explanation PA was inserted and then removed while being initialised.
Recommended Action After an insertion, the PA should be pulled out only after the initialisation is complete. If there is any traffic running through the router, the initialisation can take up to 30 seconds.
Error Message%PA-4-MPFBIND : PA failed to register [chars] with MPF
Explanation The PA has failed during initialization to register the interface which is being created with the MPF subsystem. This is due to an error within the MPF subsystem and it will result on no MPF forwarding for this interface, all traffic will proceed via the next level of switching.
Recommended Action Enter the show version command to obtain the software version. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-4-PCIVALID : PCI activation failed, bay %d, 0x%x
Explanation The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-0-DLL_OUTOFLOCK : [chars] HW DLLs failed to lock in linecard at slot [dec]
Explanation The port adapter carrier card has failed to initialize. This error indicates a hardware failure.
Recommended Action Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message recurs, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-0-INITFAIL : [chars] initialization failure for slot [dec], [chars]
Explanation The initialization of a device on the port adapter carrier card has failed. The error message specifies the device whose initialization has failed. The message also displays the slot number and either the interface name or more details about the error. This error indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory summary command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show memory summary output, 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://tools.cisco.com/ServiceRequestTool/create/, 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 memory summary, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-1-ALLOCFAIL : [chars] (slot [dec]) [chars] allocation failure
Explanation The router has failed to allocate sufficient memory for a component of the port adapter carrier card. This component is displayed after the slot number in the message text.
Recommended Action Issue the show memory summary command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 memory summary, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-2-IOMEMCORRUPT : PA-CC I/O memory corruption in slot [dec]
Explanation The PA carrier card experienced a memory corruption possibly caused by a software problem. The PA carrier card will be reset to recover from the problem.
Recommended Action If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-2-IOMEMLOW : PA-CC I/O memory too low in slot [dec]: free: [int], used: [int], largest free: [int]
Explanation The PA carrier card experienced a memory leak caused by a software problem. The remaining amount of I/O memory on the card is too little to continue operation. The PA carrier card will be reset to recover from the problem.
Recommended Action If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-2-PROCMEMCORRUPT : PA-CC processor memory corruption in slot [dec]:
Explanation The PA carrier card experienced a memory corruption possibly caused by a software problem. The PA carrier card will be reset to recover from the problem.
Recommended Action If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-2-PROCMEMLOW : PA-CC processor memory too low in slot [dec]: free: [int], used: [int], largest free: [int]
Explanation The PA carrier card experienced a memory leak caused by a software problem. The remaining amount of processor memory on the card is too small to continue operation. The PA carrier card will be reset to recover from the problem.
Recommended Action If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-3-FLOWCTRL : PA-CC FPGA flow control failure from slot [dec]
Explanation The FPGA on the port adapter carrier card cannot generate a flow-control frame. This problem could be caused by faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this message occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-GM_IPC_MESSAGE_HANDLER_FAIL : Can not create IPC message handler for PA-CC on RP.
Explanation The IPC handling process could not be created on RP. The condition indicates resource allocation issue for RP. The PA-CC(s) on this router will not work properly.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-3-GM_IPC_QUEUE_FAIL : Can not create watched queue for the PA-CC on router.
Explanation The condition indicates resource allocation issue on RP. The PA-CC(s) onthis router will not work properly.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-3-HEARTBEAT_LOSS : [chars] Loss of heartbeat from linecard in slot [dec]
Explanation The port adapter carrier card has failed to send keepalives (heartbeats) to the RP. The slot number is specified in the error message. This error usually indicates a software error.
Recommended Action Copy the error message, and any messages preceding this message that might be related to this message, exactly as they appear 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC-3-NOPA : No port adapter detected in slot [dec]
Explanation The port adapter carrier card ROMmon cannot detect a port adapter being plugged into the port adapter carrier card.
Recommended Action Ensure that the port adapter is plugged correctly into the port adapter carrier card.
Error Message%PACC-3-NOPATYPE : No port adapter type obtained for slot [dec]
Explanation The port adapter carrier card ROMmon has not reported any information about the port adapter that is plugged into the port adapter carrier card. This condition could be caused by either a hardware or a software problem and indicates a communication problem between the ROMmon for the carrier card and the Cisco 7300.
Recommended Action Remove and reinsert the port adapter carrier card. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-REVNOTSUPPORTED : The PA-CC in slot [dec] contains a PA with a H/W revision of ([dec].[dec]). The required minimum H/W revision for this PA is ([dec].[dec]).
Explanation The port adapter in the slot specified in the error message has an old hardware revision level. A newer hardware revision level of the port adapter is required for the port adapter carrier card to function on the chassis.
Recommended Action Replace the older port adapter with a port adapter that has a newer hardware revision level. The minimum hardware revision level is shown in the error message.
Error Message%PACC-3-RXOFLOW : PA-CC FPGA ingress buffer overflow on slot [dec]
Explanation The FPGA on the port adapter carrier card has detected a failure of hardware flow control for ingress frames. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-RXPAKLEN : PA-CC FPGA detected an ingress packet length error on slot [dec]
Explanation The PA carrier card has detected a packet length error while an ingress packet was being received. This condition could be caused by one of the following: –Faulty hardware involving either the Cisco 7300 or the PA carrier card,
Explanation –A corrupted FPGA image,
Explanation –By software problems (very unlikely).
Recommended Action If this message occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC-3-RXPARITY : Ingress packet parity error on slot [dec]
Explanation The FPGA on the port adapter carrier card has detected a parity error on an ingress frame. This problem could be caused by one of the following: –Faulty hardware (either the Cisco 7300 or the port adapter carrier card),
Explanation –A corrupted FPGA image, or
Explanation –A software error (least likely).
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-RXSMALLPAK : PA-CC FPGA ingress packet too small error on slot [dec]
Explanation The FPGA on the port adapter carrier card has detected a packet that is too small for an ingress frame from the port adapter carrier card CPU interface.
Recommended Action Issue the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-SYSRET : PA-CC in slot [dec] has returned to ROM Monitor:
[chars]Explanation The port adapter carrier card in the slot specified in the error message has experienced a system failure and has returned to ROMmon mode. Additional information in the error message shows the stack trace from the port adapter carrier card failure.
Recommended Action Issue the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-TXERROR : PA-CC FPGA Common Logic egress packet error on slot [dec]
Explanation The backplane side of the common logic in the FPGA on the port adapter carrier card has experienced an error on an egress packet. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-TXOFLOW : PA-CC FPGA Common Logic egress buffer overflow on slot [dec]
Explanation The backplane side of the common logic in the FPGA on the port adapter carrier card has experienced a buffer overflow for egress packets. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-TXPAKLEN : PA-CC FPGA detected an egress packet length error on slot [dec]
Explanation The PA carrier card has detected a packet length error while an egress packet was being transmitted. This condition could be caused by either faulty hardware involving either the Cisco 7300 or the PA carrier card, by a corrupted FPGA image, or, with a very low likelihood, by software problems.
Recommended Action If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC-3-TXPARITY : Egress packet parity error on slot [dec]
Explanation The FPGA on the port adapter carrier card detected a parity error on an egress frame. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-TXSLOTID : Egress packet slot ID mismatch on slot [dec]
Explanation The FPGA on the port adapter carrier card detected a slot ID mismatch on an egress packet. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.
Recommended Action If this error occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS image might have an updated FPGA bundle that could potentially solve the problem. If this message persists, enter the show diag slot-number command to gather data that might help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, 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 diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PACC-3-UNKNPA : Unrecognized port adapter in slot [dec]
Explanation The port adapter carrier card ROMmon has detected a port adapter but has not been able to determine the port adapter type from the port adapter IDPROM.
Recommended Action Remove the port adapter carrier card, and then remove the port adapter from the line card. Reinsert the port adapter into the line card and ensure that the port adapter is fully inserted. Close the latch on the port adapter carrier card and reinsert the port adapter carrier card into the router. If the problem persists, insert the port adapter into another Cisco router (for example, a Cisco 7200, Cisco 7400, Cisco 7301, or Cisco 7500). If the port adapter is not functional in another router, the port adapter has to be replaced.
Error Message%PACC-3-UNSUPPORTED_PA : Unsupported port adapter (type [dec]) in slot [dec]
Explanation An unsupported port adapter of the indicated type has been inserted into the port adapter carrier card in the slot indicated in the error message.
Recommended Action Replace the port adapter.
Error Message%PACC-3-UPGRADEFAILED : Upgrade of ROM Monitor on PA-CC in slot [dec] failed.
Explanation The upgrade of the ROM Monitor on the PA-CC in the specified slot failed due to an error. Upgrade of the ROM Monitor will be aborted.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PACC-3-UPGRADEREFUSED : Upgrade of ROM Monitor on PACC in slot [dec] refused
Explanation The user aborted the upgrade of the PACC ROM Monitor.
Recommended Action Restart the automatic ROM Monitor version. Check and upgrade via router reload, OIR or CLI by entering the upgrade rom-monitor linecard all command.
Error Message%PACC-6-NOFLASHREAD : Could not read boot flash on the PA-CC in slot [dec]
Explanation The router tried to read from the boot flash device on the PA carrier card in the specified slot. Due to software or hardware problems this was not possible. There is no impact on the operation of the PA carrier card. This failure only prevents some minor diagnostic features being available.
Recommended Action If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, but the card operates normal otherwise, no action is required.This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), or, with a very low likelihood, by software problems.
Error Message%PACC-6-NOFLASHSIZE : No boot flash size obtained for the PA-CC in slot [dec]
Explanation The router tried to determine the size of the boot flash device on the PA carrier card in the specified slot. Due to software or hardware problems this was not possible. There is no impact on the operation of the PA carrier card. This failure only prevents some minor diagnostic features being available.
Recommended Action If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, but the card operates normal otherwise, no action is required.This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), or, with a very low likelihood, by software problems.
Error Message%PACC-6-ROMINVFIELD : Invalid boot flash field found on the PA-CC in slot [dec]
Explanation The router tried to find information in the boot flash device on the PA carrier card in the specified slot. The router found an invalid field in the boot flash device on the PA carrier card. There is no impact on the operation of the PA carrier card. This failure only prevents some minor diagnostic features being available.
Recommended Action If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, but the card operates normal otherwise, no action is required.This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), or, with a very low likelihood, by software problems.
Error Message%PACC-6-ROMNOSIGN : Boot flash signature not found on the PA-CC in slot [dec]
Explanation The router tried to find a signature in the boot flash device on the PA carrier card in the specified slot. Due to software or hardware problems, this was not possible. There is no impact on the operation of the PA carrier card. This failure only prevents some minor diagnostic features being available.
Recommended Action If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, but the card operates normal otherwise, no action is required.This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), or, with a very low likelihood, by software problems.
Error Message%PACC2-0-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 2.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 2.
Error Message%PACC2-1-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 2.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 2.
Error Message%PACC2-2-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 2.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 2.
Error Message%PACC3-0-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 3.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 3.
Error Message%PACC3-1-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 3.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 3.
Error Message%PACC3-2-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 3.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 3.
Error Message%PACC4-0-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 4.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 4.
Error Message%PACC4-1-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 4.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 4.
Error Message%PACC4-2-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 4.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 4.
Error Message%PACC5-0-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 5.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 5.
Error Message%PACC5-1-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 5.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 5.
Error Message%PACC5-2-MSG : [chars]
Explanation The message immediately following this message originated from the PACC in slot 5.
Recommended Action Refer to the message immediately following this message for the actual error message that was received from slot 5.
Error Message%PACC_IPC-0-DOORBELL : Doorbell register information incorrect
Explanation A number of parameters are passed to the initialization code through registers known as doorbells. The parameters supplied by the RP are an incorrect type.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-0-DOORBELL_NOINT : Nothing written to doorbells yet
Explanation The RP software has not written the information required by the port adapter carrier card startup code. Because the startup code does not wait for the data, the port adapter carrier card could not be initialized.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-0-IPC_MASTER : Cannot create the master seat
Explanation The master IPC seat could not be created. The master seat resides on the RP and the port adapter carrier card was not able to create an entry to the RP seat. This error indicates a communication problem with the RP.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-1-DECODE : Unrecognised message: [dec]
Explanation The port adapter carrier card received an unrecognized IPC message. The error message shows the unrecognized command. This condition indicates a software problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-1-EVENT : Unexpected wakeup event [dec]. Process: [chars]
Explanation An unexpected event was received in a process, waiting for timer events. This condition indicates a software problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-1-EVENT_PORT : Cannot open event port. IPC error [chars]
Explanation The IPC port that receives events from the RP could not be opened. The IPC error code is specified at the end of the error message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-1-LOCAL_CMD : Cannot register local command port. IPC error [chars]
Explanation The IPC local command port could not be registered with the RP. The IPC error code is specified at the end of the error message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-1-PORT_CREATE : Cannot create IPC port. IPC error [chars]
Explanation The IPC command port could not be created on the port adapter carrier card. This condition indicates a resource allocation problem in the IPC code.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-3-EGRESS : IPC received too many particles ([dec])
Explanation The IPC code on the port adapter carrier card received a packet that had too many particles. This condition indicates a software problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-3-REPLY_MSG : Cannot obtain an IPC reply buffer
Explanation The port adapter carrier card could not obtain an IPC message buffer to send a reply back to the RP. This condition indicates a resource allocation problem in the IPC code.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACC_IPC-3-SEND_FAILED : Failed to send IPC message. IPC error [chars]
Explanation An IPC message could not be sent. This condition indicates a resource allocation problem in the IPC code.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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. PACKET Messages
Recommended Action The following are Packet Manager messages.
Error Message%PACK-0-BADSIZE : Invalid size in connnection request- [dec] R, [dec] W; defined - [dec] R [dec] W
Explanation In a packed connection request, either a read size requested was smaller than the packed type defined or a write size requested was larger than the packed type defined.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADSIZE2 : Packed type names:'[chars]' - '[chars]'
Explanation The specified packed type names have experienced a BADSIZE-PACK error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADTYPE : Host Packed names '[chars]' - '[chars]' do not match any configured names.
Explanation An attempt was made to establish a packed connection, but the packed type names specified on the host do not match any of the packed names specified in the CMCC.
Recommended Action Correct the host configuration or upgrade the CMCC microcode to a version that supports the packed type specified by the host.
Error Message%PACK-0-BADTYPE2 : Supported packed type names: '[chars]' - '[chars]'
Explanation An attempt was made to establish a packed connection, but the packed type names specified on the host do not match any of the packed names specified in the CMCC.
Recommended Action Correct the host or router configuration.
Error Message%PACK-0-BADVERSION : Host CLAW Packing version [dec] does not equal CMCC version [dec].
Explanation The version specified in a packed CLAW message from the host is not the same as the version specified in the CMCC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-NOLINKID : Unable to allocate sublink id for CLAW packing sublink.
Explanation An attempt was made to allocate a sublink ID to assign to a connection request, but all sublink IDs were in use. This error should not occur.
Recommended Action The CMCC has recovered by generating a bad return code to the requestor. Report this error to your Cisco technical support representative.
Error Message%PACK-0-SYSMGT_ERROR1 : CLAW detected error in sysmgt call: invalid CLAWPACK CONTROL length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-SYSMGT_ERROR2 : CLAW detected error in sysmgt call: invalid CLAWPACK SUBLINK length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-BADLEN : Invalid length in CLAW packed control message - act [dec], exp [dec]
Explanation A control message was received under the packed CLAW link, and the length did not match that of a known packed control message.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-3-BADSCBQ : Found data queued with channel queue partially empty.
Explanation After a packet was received, the packed driver detected that packed data was waiting to be queued even though the channel queue was partially emptied.
Recommended Action This is an internal logic error. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-BADSTATE : Claw packed sublink [dec] is in an unknown state [dec]. Path=[hex][hex][hex] device=[hex] link=[hex]
Explanation A packet was received from the host on a packed sublink for which the state was unknown. This is a logic error.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message%PACK-3-ILLEN : Not enough data left in buffer for packed message - remaining [dec], length [dec]
Explanation The host has written a block of packed messages, and the length of the block was inconsistent with the size of the packed messages.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed messages.
Error Message%PACK-3-ILLEN2 : Received zero length packed message.
Explanation The host has written a block of packed messages, and the length of a packed message was zero. This is an invalid size.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-3-NOMBUF : Couldn't allocate a new MBUF from the CLAW Packing pool.
Explanation An attempt to allocate a new memory buffer from the CLAW packing pool has failed. This is a design error. There should always be enough memory buffers for packed CLAW data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-NOMORE : Packed sublink [dec] doesn't support the more bit
Explanation The host sent a packet message with the More bit on, and the sublink to which the message was sent does not support the More bit.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-3-TOOBIG : Received packet [dec], packed header [dec], negotiated frame [dec], dropped the packet
Explanation The received packet together with the packed header is larger than negotiated CLAW read frame size, and the packet has been dropped.
Recommended Action Set the IP MTU to the negotiated CLAW frame size that is specified in the error message text, less 4 (for the CLAW packed header).
Error Message%PACK-3-TOOLARGE : Received [dec] byte message on packed sublink [dec] - max is [dec].
Explanation The host has sent a packed message on a sublink that was larger than the write size negotiated during the Packed Connection Request sequence.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-6-COMMAND : Unrecognized CLAW packing control command code [dec].
Explanation The host has sent a CLAW packing control command with an invalid command code.
Recommended Action The CMCC has ignored the request. Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-6-CTLERROR : Packed control error message received with return code of [dec].
Explanation The host rejected a previously received CLAW packed control message sent by the CMCC.
Recommended Action Check the return code and correct IT as appropriate.
Error Message%PACK-6-NOCONN : Channel wrote data on sublink [dec] without a valid connection. Path=[hex][hex][hex] device=[hex] link=[hex]
Explanation A packet has been received from the host, but the packed sublink specified with the data does not represent a valid connection.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message%PACK-6-NOTPRESENT : CLAW Packing sublink [dec] being freed was not present.
Explanation The host software has attempted to disconnect a CLAW packing sublink that was not established.
Recommended Action The CMCC has ignored the request. Report this error to your Cisco technical support representative.
Error Message%PACK-6-RANGE : CLAW packing sublink [dec] being freed is out of range.
Explanation An attempt to disconnect a CLAW packing sublink has failed because the CLAW packing sublink ID is not in the valid range for all CLAW packed sublinks.
Recommended Action The CMCC has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message%PACK-6-RANGE2 : Out of range sublink ([dec]) received in packed claw message.
Explanation The CLAW packing sublink ID in a packed message is not in the valid range for all CLAW packed sublinks.
Recommended Action The CMCC has recovered by ignoring this request. Report this error to your Cisco technical support representative.
PACKET Messages
Error Message%PACKET-2-ACCESSERROR : Client process [dec] attempted to access packet [hex] owned by process [dec]
Explanation A client process attempted to access a packet owned by another process. A packet manager client can only access and modify packets that have been assigned to its process.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-BLOCKERROR : Client process [dec] has packet [hex] , the buffer [hex] has been corrupted.
Explanation Data has been written past the end of the previous buffer, causing memory to be corrupted.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-CHANCREATEFAIL : Packet server fails to create a channel and event manager error: [chars]
Explanation The packet server has failed to create an event manager and channel. Clients are unable to connect to the packet server. The packet server is unable to send or receive messages.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-CHUNKCREATEFAIL : chunk_create for [chars] pool failed
Explanation The packet manager encountered a failure while it was creating the packet header chunk.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-CONNECTFAIL : Client process [dec] failed to connect to Packet Manager (reason [chars])
Explanation A packet manager client has failed to connect to the packet manager.
Recommended Action Restart the process that could not connect to the packet manager. 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-CTXERROR : The context information [hex] is not valid.
Explanation An application to the memory block manager has passed a context pointer that is not valid.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-DEQUEUEFAIL : Fail to remove client [dec] from pak_client_list at [chars]
Explanation The system cannot remove the client from the client list queue. This error can cause the client to fail to reconnect to the packet server.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-ENQUEUEFAIL : Fail to insert client [dec] into pak_client_list at [chars]
Explanation The system cannot insert the client into the client list queue. This error keeps the client from connecting to packet server.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-EVENTATTACHFAIL : event attach failure
Explanation The packet subsystem has encountered an error when registering for synchronous or asynchronous events.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-EVENTBLOCKFAIL : event_block failure
Explanation An event block error has been encountered when blocking for external events.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-EVENTCONTEXTALLOCFAIL : event_context_alloc failure
Explanation A failure occurred while allocating the event context.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-GETNODENAMEFAIL : failed to get node name in pakman server init
Explanation The packet manager server cannot retrieve the host name for a node or line card.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-HDRPOOLINITFAIL : Packet header pool init failed
Explanation The system has failed to initialize the packet pool headers.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-MEMBLKERROR : Memory block [hex] is not valid.
Explanation An application to the memory block manager has passed a memory block that is not valid.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-MEMFREEERROR : Memory block [hex] has already been freed.
Explanation An application to the memory block manager has attempted to free or lock a memory block that is not allocated.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-MEMORDINALERROR : The memory block manager has detected an ordinal error. Memory block [hex] has an ordinal of [hex] and a size of [hex].
Its corresponding lower sibling memory block [hex] has
an ordinal of [hex] and a size of [hex].Explanation The memory block manager has detected an ordinal error. The lower sibling ordinal should be equal to the difference between the higher sibling's ordinal and size.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-MEMTWINBLKERROR : An attempt to coalesce memory block [hex] with its
sibling memory block [hex] has failed because the sibling
block is not valid.Explanation An attempt to coalesce two memory blocks has failed because a memory block is not valid.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-MUTEXFAIL : mutex [chars] operation on [chars] in [chars] failed; reason [chars]
Explanation A MUTEX operation has failed in the packet server.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-NEXTBLOCKERROR : The next block after buffer [hex] (packet [hex]) has been corrupted.
Explanation Data has been written past the end of the current buffer. This action caused memory to become corrupted.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-PTHREADCREATEFAIL : pthread create fail in pakman while creating the [chars] thread
Explanation The packet manager server cannot create a new thread.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-PTHREADMUTEXFAIL : pthread_mutex_init failed on packet mutex. Reason : [chars]
Explanation The packet manager has failed to initialize the global MUTEX.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-REDZONEERROR : Client process [dec] has packet [hex] , the buffer [hex] has been overrun.
Explanation Data has been written past the end of the previous buffer, causing the memory to be corrupted.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-SHMCREATEFAIL : Error in creating the shared buffer mem: [chars]
Explanation The system encountered a fatal error while creating shared packet buffers.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-2-SHMCTLFAIL : Error in shm_ctl: [chars]
Explanation The system has encountered a fatal error while performing the shm_ctl operations on the shared packet memory.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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. PARSE_RC Messages
Recommended Action The following are PARSE_RC-related messages.
Error Message%PACKET-3-BLKDUMP : %s
Explanation This is just to report general messages in the memory management code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-CLNTDISCONN : Handling disconnect for client %d (%s)
Explanation The client id is not found in the previous client list. Remove the client's information from the list of all connected clients.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-CORRUPTPAKHDR : Corruption in packet header %x, pid %d, magic %x, buffer %x caller_pc %x
Explanation The packet header has become corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-CORRUPTPAKPOOL : %s Pool %x corrupted, magic %x
Explanation The packet pool has failed a consistency check as it has got corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-ERRPAKHDR : Not able to fix corruption in packet header %x, pid = %d
Explanation There has been a corruption in the packet header memory and it cannot be fixed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-IFINPUTCOUNTERROR : Packet:[p] being punted from process: [dec] to process: [dec] with out decrementing the input_qcount
Explanation An attempt was made to punt a packet from one process to another with the PAK_INPUTQ flag set. The input queue count was not decremented for the IDB from which the packet came. This condition will lead to input queue throttling on the affected interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-3-INITFAIL : Packet server initialization failed. Reason : [chars]
Explanation The packet subsystem could not be initialized properly.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-3-INITWARNING : Warning([chars]) while initializing the packet process
Explanation The packet subsystem detected errors while initializing.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-3-PACKETHDRDUMP : %s
Explanation This is just to report general packet header messages.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-PAK_INPUTQ_ERROR : Packet:[p] in process: [dec] has PAK_INPUTQ set incorrectly
Recommended Action A packet that has the PAK_INPUTQ flag set was received outside of a blob. This condition indicates that the packet was punted from a blob to another ION process without causing the input queue count to be decremented. This packet most likely came from a registry that does not use the PACKET or MTPACKET attribute.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-3-RECOVERBLK : BLOCK 0x%x IS SUCESSFULLY RECOVERED AFTER CORRUPTION
Explanation Corruption was detected in a memory block, and it was posible to recover the block successfully.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-REFCOUNTERROR : Bad reference count in packet:Unrecognized format ` %p' refcount: [dec].
Explanation The system made an attempt to free a packet that has already been freed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PACKET-3-REINITSHMEM : Restarting %s to reinitialize shared memory because of memory corruption
Explanation There has been a memory corruption. Restart the client to reinitialise shared memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PACKET-3-RESTARTFAIL : Packet server restart failed. Reason : [chars]
Explanation The packet subsystem did not restart properly.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PAD Messages
Error Message%PAD-2-INTR : %s called at interrupt level %x
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%PAD-2-PUTSETUP : Tty%t, buffer already setup
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%PAD-3-GETLINE : Tty%t, bad return code %d from x3_getline()
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
PAGP Messages
Error Message%PAGP_DUAL_ACTIVE-1-RECOVERY : PAgP running on %s triggered dual-active recovery: active id %e received, expected %e
Explanation Pagp detected dual-active scenario on specified interface and caused switch to go into recovery mode.
Recommended Action No action is required.
Error Message%PAGP_DUAL_ACTIVE-3-ADD_TLV_FAIL : Too few bytes for %s TLV in PAgP (reqd. %d, got %d) on port %s
Explanation The dual-active tlv could not be added to the PAgP packet due to too few bytes in the packet. PAgP dual-active detection may be disabled as a result.
Recommended Action Enter the commands: show switch virtual dual-active summary show switch virtual dual-active pagp Retrieve the PAgP packet contents by entering the commands: debug condition interface debug pagp packet and 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED : Unable to create %s
Explanation Unable to create the specified managed object
Recommended Action No action is required.
Error Message%PAGP_DUAL_ACTIVE-3-PROC_CREATE_FAILED : Unable to create process %s
Explanation Unable to create the specified process
Recommended Action No action is required.
Error Message%PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER : PAgP running on %s has detected a switchover or possible dual-active situation on the neighbor virtual switch. Informing virtual switches of active id change: new id %e, old id %e
Explanation Pagp received new active id on specified interface, indicating virtual switches are in a dual-active scenario. Interface is informing virtual switches of this, which will cause one switch to go into recovery mode.
Recommended Action No action is required.
Error Message%PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR : Failure in adding to %s registry
Explanation Could not add a function to the registry
Recommended Action No action is required.
Error Message%PAGP_DUAL_ACTIVE-4-NO_CHNL_GROUP : Port %s channel group not present while %s
Explanation Extraction of the channel group from a link has failed, but is expected to be present. This should not occur, and may affect functionality, depending on where it occurred.
Recommended Action This message should not be seen under normal operation. If it is appearing, it is an indication of a software bug. Enter the commands: show switch virtual dual-active summary show switch virtual dual-active pagp Retrieve the PAgP packet contents by entering the commands: debug condition interface debug pagp packet and 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PAGP_SWITCH_ISSU-2-GET_BUFFER : PAGP SWITCH ISSU client failed to get buffer for message. Error: %d (%s)
Explanation PAGP SWITCH ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show logging and show checkpoint client)
Error Message%PAGP_SWITCH_ISSU-2-INIT : PAGP SWITCH ISSU client initialization failed to %s. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-2-SEND_NEGO_FAILED : PAGP SWITCH ISSU client failed to send negotiation message. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs.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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show logging and show checkpoint client)
Error Message%PAGP_SWITCH_ISSU-2-SESSION_ARBITRATE : PAGP SWITCH ISSU client failed to register arbitrate callback. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client failed to register arbitrate callback. If a problem occurs with the callback registration, the standby device cannot be brought up properly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-2-SESSION_NEGO : PAGP SWITCH ISSU client encountered unexpected client nego_done. Error: %d (%s)
Explanation An ISSU-compliant client transitions through a series of internal states. The PAGP SWITCH ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-2-SESSION_REGISTRY : PAGP SWITCH ISSU client failed to register session information. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-3-BUFFER : PAGP SWITCH ISSU client failed to get buffer for message, error [dec]
Explanation PAGP SWITCH ISSU client failed to get buffer for building a negotiation message. Thus, it can send the negotiation message to the standby unit. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-CAPABILITY : PAGP SWITCH ISSU client [chars]
Explanation PAGP SWITCH ISSU client observed an error during capability negotiaiton. When this error happens, there is a mismatch between the client capability and between the active and standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries , show issu session and show issu negotiated capability commands to gather data that might help identify the nature of the message.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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-INIT : PAGP SWITCH ISSU client initialization failed at [chars], error [chars]
Explanation PAGP SWITCH ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-INVALID_CAPABILITY : PAGP SWITCH ISSU client: invalid capability list
Explanation PAGP SWITCH ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-3-INVALID_SESSION : PAGP SWITCH ISSU client does not have a valid registered session.
Explanation The PAGP SWITCH ISSU client does not have a valid registered session.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-3-MSG_NOT_OK : PAGP SWITCH ISSU client 'Message Type %d' is not compatible
Explanation The PAGP SWITCH ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu message group and show issu session and show issu negotiated version )
Error Message%PAGP_SWITCH_ISSU-3-MSG_SIZE : PAGP SWITCH ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)
Explanation The PAGP SWITCH ISSU client failed to calculate the MTU for the specified message. The PAGP SWITCH ISSU client is not able to send the message to the standby device.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu message group and show issu session and show issu negotiated version )
Error Message%PAGP_SWITCH_ISSU-3-POLICY : PAGP SWITCH ISSU client message type [dec] is [chars]
Explanation PAGP SWITCH ISSU client received an message type which it does not support. The policy is applied to make the session compatible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-POLICY_NOT_SUPPORTED : PAGP SWITCH ISSU client does not support Message Type %d
Explanation PAGP SWITCH ISSU client received an message type which it does not support. The policy is applied to make the session incompatible.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu session )
Error Message%PAGP_SWITCH_ISSU-3-REJECTED_CAPABILITY : PAGP SWITCH ISSU client rejected capability '%s'
Explanation PAGP SWITCH ISSU client rejected a capability duringnegotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu capability entries and show issu session and show issu negotiated capability)
Error Message%PAGP_SWITCH_ISSU-3-REJECTING_CAPABILITY : PAGP SWITCH ISSU client rejecting capability '%s'
Explanation PAGP SWITCH ISSU client is rejecting a capability duringnegotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-3-SEND_FAILED : PAGP SWITCH ISSU client failed to send a negotiation message, error [dec]
Explanation PAGP SWITCH ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-SESSION : PAGP_SWITCH ISSU client [chars]
Explanation PAGP SWITCH ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries , show issu session and show issu negotiated capability commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PAGP_SWITCH_ISSU-3-SESSION_UNREGISTRY : PAGP SWITCH ISSU client failed to unregister session information. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client failed to unregister session information.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu session and show issu negotiated capability )
Error Message%PAGP_SWITCH_ISSU-3-TRANSFORM : PAGP SWITCH ISSU client [chars] transform failed, error [chars]
Explanation PAGP SWITCH ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases the PAGP_SWITCH state will not be indentical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session and show issu negotiated version commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. PAR Messages
Recommended Action The following are Parity messages.
Error Message%PAGP_SWITCH_ISSU-3-TRANSFORM_FAIL : PAGP SWITCH ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)
Explanation The PAGP SWITCH ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the PAGP SWITCH state between the active device and the standby device is not identical.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu session and show issu negotiated version )
PAMMBOX Messages
Error Message%PAMMBOX-3-BADCONFIG : Bad mailbox config data 0x%x, 0x%x
Explanation An error was found in the mailbox config data
Error Message%PAMMBOX-3-BADRXFRMHDR : %d %d %d %d 0x%x 0x%x 0x%x
Explanation A received PAM mailbox message frame has a bad header
Error Message%PAMMBOX-3-BADSTATUS : Bad mailbox status data 0x%x, 0x%x
Explanation An error was found in the mailbox status data
Error Message%PAMMBOX-3-INITERROR : Initialization Error: %s
Explanation An error occured during the subsystem initialization
Error Message%PAMMBOX-3-PLATADDSLOT : Platform add slot error %d, %d
Explanation The platform-dependant add slot routine failed
Error Message%PAMMBOX-3-PLATDELETESLOT : Platform delete slot error %d, %d
Explanation The platform-dependant delete slot routine failed
Error Message%PAMMBOX-3-RXBADSTATE : RX mailbox in illegal state %d %d
Error Message%PAMMBOX-3-RXNOIDB : RX a message but no NRP IDB for slot [dec] subslot[dec]
Explanation A message has been received, but no IDB exists for the specified slot and subslot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error MessageExplanation The RX mailbox has interrupted as owned but state is not owned %PAMMBOX-3-RXNOIDB : RX a message but no NRP IDB for slot %d subslot%d
Error Message%PAMMBOX-3-RXQWAKEUPREASON : Unknown wakeup reasons: [dec] [dec]
Explanation The Rx packet queue process has woken up for an unknown reason.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error MessageExplanation A message has been recieved but no IDB exists for the given slot/subslot. %PAMMBOX-3-RXQWAKEUPREASON : Unknown wakeup reasons: %d %d
Recommended Action The RX packet Q process wokeup for unknown reason.
Error Message%PAMMBOX-3-TXBADSTATE : TX mailbox in illegal state %d %d %d
Recommended Action The TX mailbox is owned and empty, but output Q is not empty.
Error Message%PAMMBOX-3-TXOUTERR : Transmit Message Output Error: %d %d %d %d
Recommended Action Sanity checks on a transmit message failed.
Error Message%PAMMBOX-3-TXPAKERR : Transmit Message No Packet
Explanation TX message cannot get a packet.
Error Message%PAMMBOX-3-TXRXBADINITSTATE : TX/RX mailbox owned in illegal initial state %d %d
Explanation The TX/RX mailbox is in an illegal initial ownership state.
Error Message%PAMMBOX-3-UNEXPECTEDINT : Unexpected PAM Mailbox Interrupt: %s
Explanation Sanity checks on a transmit message failed.
Error Message%PAR-1-FATAL : [chars]
Explanation A parity error has occurred. This problem might be caused either by a motherboard that has failed or motherboard jumper settings that are incorrectly set.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, 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.
PARSER Messages
Error Message%PARSER-2-INTDISABLE : Interrupts disabled in mode [chars] by command '[chars]'
Explanation A hardware or software error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-3-BADLINK : bad link point [int]
Explanation The software has attempted to perform an invalid parser operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-BADSUBCMD : Unrecognized subcommand [dec] in [chars] command '[chars]'
Explanation The parser has failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-3-BADUNLOCKREQ : Unlock requested by process '[dec]'. You are not the lock owner
Explanation A request to unlock the configuration has been requested by a process that does not own the lock.
Recommended Action Check the code flow for a configuration unlock request that is not required.
Error Message%PARSER-3-CFGLOG_CLI_INITFAILED : Initialization of the Config Log CLI failed.
Explanation Configuration log CLI commands may not be accessible. The configuration logger may not be accessible by the IOS CLI.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_EMPTYCMD : User:[chars]
Explanation The user specified entered an empty command for which a log attempt was made. Normally, empty commands will not be logged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version, show tech-support and show cfglog user username xml detailed commands, with username being the name of the user specified in the error message, and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_INCONSISTENT : User:[chars] command:[chars]
Explanation The configuration logger detected an inconsistency in the log while a CLI command was being entered. This inconsistency may result in a failure to log the command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. If possible, determine which users are presently logged in to the router, and who was copying configuration files or executing commands in global configuration mode, SNMP or HTTP. Contact your technical support representative. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_INITFAILED : Initialization of the Config Log subsystem failed.
Explanation During system initialization, one or more queues or data structures that are essential to the configuration logger could not be set up. As a result, the configuration logger is not available for use.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_NOMEM : User:[chars] [chars]
Explanation The command that was entered could not be logged because of a lack of memory. The configuration logger will free old entries one by one until the system logger (syslog) has enough memory to log the command so that an NMS can receive notification of it.
Recommended Action Attempt to free up memory on the router by stopping nonessential processes or unused features that may be running. Once sufficient memory is available, this message no longer appears.
Error Message%PARSER-3-CFGLOG_NOUSER : Command:[chars]
Explanation The user could not be determined when the specified command was being logged. The command could not be saved in the configuration log.
Recommended Action Copy the message exactly as it appears on the console or in the system log. If possible, determine which users are presently logged in to the router, and who was copying configuration files or executing commands in global configuration mode, SNMP or HTTP. Contact your technical support representative. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_PERSIST_APPLY_CMD_FAILED : Configuration logger persistency: Applying config command '[chars]' failed. result '[dec]'.
Explanation When applying the command to the running configuration the parser returned an error.
Recommended Action Parser encountered an error when the command is applied to the running configuration during reload. Verify no other process locks the configuration mode during this time. The parser could be locked by the HA or SNMP or by some other process.
Error Message%PARSER-3-CFGLOG_PERSIST_DB_OPEN_FAILED : Configuration logger persistency: opening persist db failed. File '[chars]'.
Explanation The file open for writing or reading persisted commands failed.
Recommended Action Check for the file system availablity. The file system might have got corrupted. Try formatting the file system.
Error Message%PARSER-3-CFGLOG_PERSIST_FILESYS_FULL : Configuration logger persistency: Add command to persistent db failed. File system '[chars]' full.
Explanation When logging a command entered on the CLI, in to the configuration logger persistent database the configurationLogger persistency detected zero bytes free in the file system.
Recommended Action Check the space available in the filesystem displayed reported. Enter dir to determine the bytes free. Clear out some space for the configuration logger persistency feature to continue to store the configurationcommands logged in to the persistent database.
Error Message%PARSER-3-CFGLOG_PURGEFAILED : Purge config log failed.
Explanation Failed to purge some of the configurationlog entries.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSER-3-CFGLOG_RESIZE_FAILED : Could not resize the configuration logger to new size:[dec]
Explanation Due to an internal error, a request to resize the configuration log was not carried out. Apart from a failure to resize, there should be no change in the behavior of the configuration logger.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CFGLOG_SESSIONERR : Could not delete config log session:[dec] for user:[chars].
Explanation When a user logged out, the configuration logger was unable to clean up information about the login session of the user. The cause of this condition might be a memory leak or an inability to add new commands to the configuration log.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-3-CONFIGNOTLOCKED : Configuration unlock requested by the process '[dec]' on a free lock.
Explanation A request to unlock a configuration was requested on a free lock.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-3-CREATEINT : Can't create any more subinterfaces
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-3-NOLINK : no link_point([dec]) in the [chars] [chars] command chain
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-3-URLOPENFAIL : cannot open file for redirection '[chars]'
Explanation The destination URL for the redirection operation could not be opened for writing.
Recommended Action Check that proper Uniform Resource Locator syntax was used, and that write permission has been granted. Check for available space and retry the operation.
Error Message%PARSER-4-BADCFG : Unexpected end of configuration file.
Explanation A configuration file has been read from TFTP or NVRAM, and the end of the file has been encountered before the end statement. This message indicates that the configuration may be corrupted or incomplete. Whatever has been read will be applied to the configuration.
Recommended Action Ensure that the configuration is valid, then enter either the copy running-config startup-config command to write the good configuration to NVRAM or the copy running-config tftp command to write the valid configuration to a network TFTP server.
Error Message%PARSER-4-BADRANGE : Bad range for command '[chars]'
Explanation A software or hardware error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-BADRANGELONGLONG : Bad range for command '%s'
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PARSER-4-INVLDLINE : Invalid line in NV generation: [t-line]
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-INVLDNVGEN : Invalid function called in NVGEN of '[chars]'
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, 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, show version and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PARSER-4-INVLDSYNTX : Syntax clean up called while not syntax checking. FuncPtr / Context [chars]
Explanation Functions were mistakenly called, there might be more than listed
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSER-4-LINKPOINT : Parser reached link_point
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-MULFUNCS : unknown test in test_multiple_funcs '[char]'
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-MULTIPLEIFS : interface_action: multiple ifs present when unit_only set
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-NUMHELP : general_number_short_help: Invalid [chars] number flag
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-NVGEN : nvgen_token called but csb-nvgen not set
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-4-PROTOADDR : protoaddr_action: Unknown link_type [dec]
Explanation The parser failed an internal software check.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSER-5-CFGLOG_LOGGEDCMD : User:[chars] logged command:[chars]
Explanation The configuration logger, which logs every CLI command, has an option to log messages to syslog. Whenever a CLI command is executed, this message is displayed.
Recommended Action This message does not denote any error condition and is a part of the normal operation of the parser and configuration logger. To disable displaying of this syslog message, enter the no cfglog send to syslog command.
Error Message%PARSER-5-CFGLOG_PERSIST_APPLY_ON_RELOAD : Apply persisted config cmds on reload switched off
Explanation The switch that controls the persisted commands applied during reload is set to OFF.
Recommended Action Verify the rommon variable 'logpersistreload' value from rommon prompt. This variable might have been intentionally set to OFF.
Error Message%PARSER-6-CONFIGLOCKCLEARED : Configuration lock cleared by user '[chars]' process '[dec]' from terminal '[dec]'
Explanation Configuration lock cleared using clear configuration lock command.
Recommended Action This is a n informational message only. No action is required.
Error Message%PARSER-6-CONFIGLOCKNOTSUPPORTED : Configuration lock not supported for this transport '[chars]'
Explanation Configuration lock enabled from a transport other than telnet/SSH.
Recommended Action This is an informational message only. No action is required.
Error Message%PARSER-6-EXPOSEDLOCKACQUIRED : Exclusive configuration lock acquired by user '[chars]' from terminal '[dec]'
Explanation Exclusive configuration lock acquired by the user.
Recommended Action This is an informational message only. No action is required.
Error Message%PARSER-6-EXPOSEDLOCKRELEASED : Exclusive configuration lock released from terminal '[dec]'
Explanation Exclusive configuration lock released by the user.
Recommended Action This is an informational message only. No action is required.
Error Message%PARSER-6-LI_VIEW_INIT : LI-View initialised.
Explanation You have successfully initialised LI-View.
Error Message%PARSER-6-SUPER_VIEW_CREATED : super view '%s' successfully created.
Explanation Super View is successfully created and the system enters into the view configuraation mode
Recommended Action This is informational only, not a error.
Error Message%PARSER-6-SUPER_VIEW_DELETED : super view '%s' successfully deleted.
Explanation Super View is successfully deleted.
Recommended Action This is informational only, not a error.
Error Message%PARSER-6-SUPER_VIEW_EDIT_ADD : view %s added to superview %s.
Explanation Views is successfully added to the SuperView, now all view related configurations can be accessed from SuperView.
Recommended Action This is informational only, not a error.
Error Message%PARSER-6-SUPER_VIEW_EDIT_REMOVE : view %s removed from superview %s.
Explanation Views is successfully removed from the SuperView.
Recommended Action This is informational only, not a error.
Error Message%PARSER-6-VIEW_CREATED : view '%s' successfully created.
Explanation You have successfully created the view and entered into the view configureation mode of that view.
Error Message%PARSER-6-VIEW_DELETED : view '%s' successfully deleted.
Explanation You have successfully deleted the required view.
Error Message%PARSER-6-VIEW_SWITCH : successfully set to view '%s'.
Explanation You have successfully switched the view.
Error Message%PARSE_RC-3-PRC_INTERRUPT : [chars]
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_INVALID_BLOCK_PTR :
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_INVALID_CSB :
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_LEV_RANGE : Parser Return Code level range error [dec]
Explanation An internal software error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSE_RC-3-PRC_NO_CSB : Parser Return Code csb error [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_OUT_OF_RANGE_ENUM : [chars] had value [int]
Explanation An out-of-range parameter was passed to an internal API.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_STATE_RANGE : Parser Return Code state range error [dec]
Explanation An internal software error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSE_RC-3-PRC_SUBRCODE_RANGE : Parser Return Code state range error [dec]
Explanation An internal software error has occurred.
Recommended Action Copy down the system configuration. Also 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://tools.cisco.com/ServiceRequestTool/create/, 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%PARSE_RC-3-PRC_UNRECOGNIZED_ERROR : error value `[dec]' is not currently mapped
Explanation An unrecognized error was caught and remapped.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. PARSER Messages
Recommended Action The following are parser messages.
Error Message%PARSE_RC-4-PRC_NON_COMPLIANCE : `[chars]'
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-6-PRC_DISABLE : Parser PRC Feature Disabled
Explanation Parser PRC Feature Disabled
Recommended Action No action is required.
Error Message%PARSE_RC-6-PRC_ENABLE : Parser PRC Feature Enabled.PRC logs are displayed for configration commands alone
Explanation Parser PRC Feature Enabled.PRC logs are displayed for configration commands alone
Recommended Action No action is required.
Error Message%PATCH-3-CHANNEL_MISMATCH : Channel mismatch between [chars] and [chars]
Explanation A channel mismatch occurred when creating a patch.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PBI_OPEN-4-ERROR_ALLOC : %%Error: Can't allocate %d bytes for pbi data
Explanation The system is unable to allocate required memory to access the file.
Recommended Action Check the memory usage of the system and retry the operation.
Error Message%PBI_OPEN-4-ERROR_OPEN : %%Error: Can't open %s
Explanation The system is unable to open the file specified.
Recommended Action Ensure that the file name is correct. Enter the dir command to check the file name.
Error Message%PBI_OPEN-4-ERROR_READ : %%Error: pbi file %s read failed
Explanation An unknown error has occurred while the system was copying the PBI program file to a local buffer.
Recommended Action Enter the del %s command to remove the file.Use the copy command to recopy the file from a known good source to its desired destination %s.If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PBI_OPEN-4-ERROR_SIZE : %%Error: Bad file size %s
Explanation The file is too small or too large for a PBI program file.
Recommended Action Enter the dir command and check the size of the file. Retry the operation.
PBR Messages
The following are Policy-Based Routing (PBR) messages.
Error Message%PBR-2-NO_RMAP : Cannot create PBR data structures for route-map [chars]
Explanation The PBR manager could not allocate the data structures that are required to describe a route map that is being used for policy routing. This condition is probably caused by a lack of available memory.
Recommended Action Use a less-complicated configuration that requires less memory.
Error Message%PBR-3-INSTALL_FAIL : Policy route-map [chars] not installed in hardware
Explanation The PBR manager was unable to install the complete route map in the hardware, so the route map will have to be applied in the Cisco IOS software. This situation requires that the packets be forwarded by the CPU.
Recommended Action Reconfigure the route map to use a simpler configuration. Use the same route map on multiple interfaces if possible.
Error Message%PBR-3-MERGE_FAIL : [chars] ACL merge error [dec] on route-map [chars]
Explanation The PBR manager could not merge the configured route map into a form that was suitable to be loaded into the hardware. The most likely cause of this condition is an ACL that was too large or too complex for the system to process.
Recommended Action Attempt to specify a smaller and less-complicated configuration.
Error Message%PBR-3-NO_LABEL : Cannot allocate label for route-map [chars]
Explanation The PBR manager could not allocate a label for this route map. The hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy-based routing.
Recommended Action Use a less-complicated configuration that allows label sharing. Use the same route maps on multiple interfaces, if possible.
Error Message%PBR-3-UNSUPPORTED_RMAP : Route-map [chars] not supported for Policy-Based Routing
Explanation The route map that is attached to an interface for policy routing contains an action that is not supported on this platform. This condition indicates a hardware limitation.
Recommended Action Reconfigure the route map. Use only entries that are specified by the permit command, and actions that are supported by the set ip next-hop command, in the route map.
Error Message%PBR-4-CPU_SUPPORTED_ACTION : Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU
Explanation The route map that is attached to an interface for policy routing contains an action that is not supported in hardware, since it contains actions related to the set interface, set ip default next-hop, set default interface or set ip df commands. Packets will now be forwarded by the CPU in order to support the route map.
Recommended Action Reconfigure the route map. Apply conditions related to the set ip next-hop command in the route map if possible.
Error Message%PBR-4-RETRY_INSTALL : Route-map [chars] installed in hardware upon retry
Explanation The PBR manager was able to fit the complete configuration into the hardware. One or more route maps had previously not been loaded because of a lack of space.
Recommended Action No action is required.
PCI Messages
Error Message%PCI_FE-3-ID_INVALID : PCI FE MAC id [hex] is different from expected id [hex]
Explanation The PCI FE MAC vendor and device identification number are invalid. The PCI FE MAC hardware used for the RSC BIC may be faulty or may have the wrong version. The RSC BIC may not operate as expected.
Recommended Action During the nearest convenient maintenance window, reload the RSC reporting the error. If the condition persists, replace the RSC with a spare. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
PCM_TRACER Messages
Error Message%PCM_TRACER-3-PCMT_CHANNEL_TYPE_NOT_SUPPORTED : The channel/group type of ds0 [int] is not supported by PCM Tracer.
Explanation An attempt to execute the command on the specified DS0 slot failed.
Recommended Action Unavailable
Error Message%PCM_TRACER-3-PCMT_NO_CAPTURE_DURATION : No capture duration configured.
Explanation The capture duration value was not configured before starting the PCM tracer.
Recommended Action Configure the capture duration value before starting the PCM tracer.
Error Message%PCM_TRACER-3-PCMT_NO_CAPTURE_TDM : No capture-tdm configured under profile [int].
Explanation The capture-tdm variable was not configured before starting the PCM tracer.
Recommended Action Configure the capture-tdm variable before starting the PCM tracer.
Error Message%PCM_TRACER-3-PCMT_NOT_SUPPORTED : PCM Tracer is not supported on slot [int].
Explanation An attempt to execute the command on the specified slot has failed.
Recommended Action Unavailable
PCMCIAFS Messages
The following are PCMCIA disk messages.
Error Message%PCMCIAFS-3-RESETERR : PCMCIA disk [dec] [chars]
Explanation A PCMCIA disk could not be reset while the system is was being initialized or reloaded. This condition will cause a transient disk error or disk timeout error, when the ROMMON initialization code attempts to read the DIB. This is a transient error. The system will be able to access the disk and continue normal system operation.
Recommended Action No action is required.
Error Message%PCMCIAFS-4-DFS_FSCK_ERR : Error while running fsck on the file %s.
Explanation Fsck is running in a loop while walking through the cluster chain of a file and has aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PCMCIAFS-5-DFS_CLOSE_ERR : Error during close of the file [chars]. [chars]
Explanation An error occurred while a file was being closed.
Recommended Action Enter the fsck filesystem: command, with filesystem: being the file system prefix indicating the disk to be checked, to check and attempt to repair the disk. If this operation does not fix the problem, format the disk.
Error Message%PCMCIAFS-5-DIBERR : PCMCIA disk [dec] [chars]
Explanation The system cannot boot an image from the PCMCIA Flash memory disk because the Device Information Block is different. The Flash memory disk can be read by the router, but it requires formatting by the router before an image can be booted from it.
Recommended Action Follow any instructions provided in the error message. Before storing an image in the Flash memory disk and trying to boot from this device, enter the format command to format theFlash disk from the router. Copy the desired image to the Flash memory disk, and then boot from this device.
PC_QOS Messages
Error Message%PC_QOS-3-POLICE_MARKING_NOT_SUPPORTED_WITH_1R2C : Police marking is not supported with 1R2C police configuration
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_DFT_NOQ : Queueing must be defined in class-default in a flat policy on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_POLICE : Ingress policer not supported for this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_SET_L2L3 : Combined L2 and L3 set operations can not be supported in the same class-map on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_SET_L2_OVER : More then two types of set operations in the same class-map can not be supported on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_SHAPE : 'Shape' action is required in parent classes for this interface.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-ACTION_SHAPE_BRR : Only 'shape' and 'bandwidth remaining ratio' actions are supported in parent classes for this interface.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-BW_% : Bandwidth percent not supported for this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_COS : 'match cos [inner]' can only be combined with match vlan [inner] in a service instance
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_DUPED : Only 'match-any' class-map supports match statements with same type.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_IP : 'match ip prec' or 'match ip dscp' is not supported for this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_VLAN : Only 'match vlan', 'match vlan inner' or class-default are supported in a parent policy-map for this interface.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_VLAN_CHILD : Service policy with 'match vlan' in both parent and child is not supported on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-FILTER_VLAN_INNER : Service policy with 'match vlan inner' in both parent and child is not supported on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-HQOS_POLICE : Hierarchical policy with police operations in child can not be supported on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-PC_PMAP_INCOMPATIBLE : Warning - Policymap attached to port-channel EVC is incompatible with ESM20 member link.
Explanation Policymap attached to port-channel EVC is with ESM20 member link.
Recommended Action Remove policymap attached to port-channel EVC before adding a ESM20 member link to port-channel.
Error Message%PC_QOS-4-POLICE_1R2C : Ingress policy with 1R2C police is only supported in class-default on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-POLICE_1R2C_2R3C : 1R2C and 2R3C police can not be supported in the same ingress policy on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-POLICE_1R2C_USER_CLASS : User-defined classes are not allowed in a flat-policy or parent-policy with 1r2c police configured in class-default
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PC_QOS-4-PRIORITY_LEVEL : Priority Level is not supported on this interface
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PDSD-3-INTERNAL_ERROR : %s(%d)
Explanation A PDS daemon internal error has occurred.
Recommended Action Restart the process. If the problem persists, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PDSD-3-NO_DEBUG : PDS Daemon debug %s failed(%d)
Explanation The PDS daemon process failed to initialize the debugging facility
Recommended Action Restart the process. If the problem persists, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PDSD-3-NO_TRACE : PDS Daemon trace initialization failed(%d)
Explanation The PDS Daemon process failed to initialize trace buffer. The operational log will not be available.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PERSEUS-4-INTR_THROTTLE : Throttling '[chars]' interrupt exceeded permitted [int]/[dec] interrupts/msec
Explanation Excessive interrupts have been generated by the EARL ASIC. The system is enforcing an interrupt throttle to keep the SP safe.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PERUSER-3-ISDNINTF : %s %s: Can not apply configuration to ISDN channel: %s
Explanation Configuration can not be applied to individual ISDN channels.
Recommended Action You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. See the section on virtual-profiles in your manual.
Error Message%PF-4-MEM_UNAVAIL : Memory was not available to perform the protocol filtering action
Explanation Protocol filtering is unable to operate because of a lack of memory
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PF-4-PROC_START_ERR : Protocol filtering unable to start
Explanation The protocol filtering process was unable to be created for unknown reasons.
Recommended Action Start protocol filtering again in case the condition was transient. If this still fails, reload the device.
Error Message%PF-4-UNKN_ERR : An unknown operational error occurred
Explanation Protocol filtering is unable to operate because an internal operation generated an error which was not expected to ever happen.
Recommended Action Because of the unexpected nature of the problem, the only recommended action is to reload the device.
Error Message%PF-5-SPANDSTOFF : Protocol filtering disabled on interface [chars] because it is a span destination
Explanation Protocol filtering does not operate on a span destination. The protocol filtering configuration stays with the span destination port, but it has no effect and does not appear when you show all non-default protocol filters.
Recommended Action Unavailable.
Error Message%PF-5-TRUNKPFOFF : Protocol filtering disabled on interface %s because it is a trunk
Explanation Protocol filtering does not operate on trunks. The protocol filtering configuration stays with the trunk port, but it has no effect and does not appear when you show all non-default protocol filters.
Error Message%PFINIT-1-CONFIG_SYNC_FAIL : Sync'ing the %s configuration to the standby Router FAILED, the file may be already locked by a command like: show config.
Explanation CONFIG_SYNC_FAIL_EXPLANATION
Recommended Action CONFIG_SYNC_FAIL_ACTION
Error Message%PFINIT-1-CONFIG_SYNC_FAIL_RETRY : Sync'ing the %s configuration to the standby Router FAILED, the file may be already locked by a command like: show config. Will attempt to sync %d more time%s
Explanation CONFIG_SYNC_FAIL_EXPLANATION
Recommended Action CONFIG_SYNC_FAIL_ACTION
Error Message%PFINIT-2-EOBC : [chars]
Explanation The PF subsystem could not send IPC bootstrap messages to the RP.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PFINIT-2-IPCREINIT : Unable to reinitialzie IPC
Explanation The PF subsystem could not reinitialize the IPC.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PFINIT-2-IPCSEAT : Unable to add/remove IPC seats for [chars]
Explanation The PF subsystem could not add or remove IPC seats.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFINIT-2-NOMEM : No memory available for [chars]
Explanation The PF subsystem could not obtain the memory it needed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PFINIT-5-CONFIG_SYNC : Sync'ing the [chars] configuration to the standby Router
Explanation The configuration has been successfully synchronized to the standby router.
Recommended Action This is an informational message. No action is required.
Error Message%PFINIT-5-CONFIG_SYNC_NOT_SUPPORTED : Sync'ing the [chars] configuration to the standby Router is not supported.
Explanation The configuration has not been successfully synchronized to the standby router.
Recommended Action This is an informational message. No action is required.
Error Message%PFINIT-6-PROC_MAX : Process-max-value changed from [dec] to [dec] millisecs
Explanation Informational messages regarding change in Process-max-value.
Recommended Action No action is required. PF_OBFL Messages
Recommended Action The following are 7600 SIP Platform OBFL messages.
Error Message%PFINIT-SP-5-CONFIG_SYNC : Sync'ing the [chars] configuration to the standby Router.
Explanation The configuration has been successfully synchronized to the standby router.
Recommended Action Informational message only. No action is required.
Error Message%PFREDUN-1-VTP_CONFIG_DISLOCATE : VTP config file must be in default location for standby supervisor to come online
Explanation The standby supervisor engine failed to come online because the VTP configuration file is not in the default location.
Recommended Action Reset the standby supervisor engine and then configure the VTP configuration file so that it is in the default location.
Error Message%PFREDUN-3-ACTIVE_FORCED_TO_RELOAD : Active not able to operate properly. Standby is ready to take over and forced active to reload.
Explanation Active is not operating properly since it fails to respond. The standby is ready to take over and forces the active to reload.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-3-CCMODE_MISMATCH : Standby Supervisor cannot support Configured Card Mode %s(0x%x) due to %s(enf mask 0x%x, cap mask 0x%x, msg ver 0x%x)!
Explanation The active supervisor engine is in user-configured mode (for example, DFC-only mode). The active supervisor engine attempts to bring the standby supervisor engine on line, but incompatible software on the standby cannot support this mode The active keeps the standby in ROMMON mode.
Recommended Action Remove the user-configured mode on the active supervisor engine so that the active can bring the standby on line.
Error Message%PFREDUN-3-STANDBY_OUT_OF_SYNC : Active and Standby are out of sync.
Explanation Active and Standby are out of synchronization either due to communication failure, configuration synchronization failure, etc.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-3-SUP : [chars]
Explanation This supervisor card has failed to boot because it detects that the system might contain an invalid combination of supervisor cards.
Recommended Action Check all the line cards in the system and look for invalid combination of supervisor cards.
Error Message%PFREDUN-4-AUTOBOOT : %s
Explanation The RP has experienced a hardware or other failure. When the redundant system initializes, the redundant supervisor will wait for the RP to initialize. Since the RP cannot initialize due to the hardware or other failure, it is possible that the supervisor can never initialize. The default wait time for the RP to initialize is three minutes. The wait time has now expired, and the autoboot feature for supervisor has been disabled.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-4-BOOTSTRING_INVALID : The bootfile [chars] is present on the [chars] supervisor but not on the [chars]
Explanation The bootfile that is configured is present on one supervisor but not the other. This means that if the systems is reloaded, one of the supervisors will not come up because it will not find the image specified in the boot string.
Recommended Action No action is required.
Error Message%PFREDUN-4-INCOMPATIBLE : Defaulting to RPR mode ([chars])
Explanation A warning message to indicate that there is a runtime incompatibility of image versions running on active and standby supervisors.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-4-INCOMPATIBLE_ISSU_MATRIX : Compatibility Matrix check failed. reason [dec]
Explanation A warning message to indicate that there is a mismatch of compatibility matrix between the images running on active and standby supervisors.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-4-PFC_MISMATCH : My PFC %s and Other's PFC %s mismatch
Explanation This message indicate that the active and the standby supervisor has different version of the PFC daughter card.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-4-PHYSMEM_MISMATCH : Asymmetrical redundant configuration: Active %s has (%u/%uK) memory, Standby has (%u/%uK).
Explanation To support the High Availability feature it is recommended to have redundant supervisors with symmetrical memory configurations.
Recommended Action Upgrade the memory on the supervisor with less memory to match the amount of memory on the other supervisor.
Error Message%PFREDUN-4-SUP_FORCE_TO_ROMMON : Supervisor forced to rommon with reason: [chars]
Explanation An application forced the supervisor to stay in rommon with the reason given.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-4-VERSION_MISMATCH : Defaulting to RPR mode (%s)
Explanation A warning message to indicate that there is a mismatch of image versions running on active and standby supervisors.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PFREDUN-6-ACTIVE : [chars]
Explanation This is an informational message regarding the state of the active supervisor.
Recommended Action No action is required.
Error Message%PFREDUN-6-STANDBY : [chars]
Explanation This is an informational message regarding the state of the active supervisor.
Recommended Action No action is required.
Error Message%PFREDUN-7-KPA_WARN : RF KPA messages have not been heard for %d seconds
Explanation RF Keepalive messages have not been sent from the peer is printed after every third KPA timer expiry.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PF_ASIC-3-ASIC_DUMP : [[dec]:[hex]] [chars] = [hex]
Explanation This message includes relevant ASIC counters that might help to diagnose the problem with the switching bus.
Recommended Action Copy this message and the SWITCHING_BUS_IDLE message exactly as they appear 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PF_OBFL-5-FEATURE : Platform OBFL [chars] feature initialization fails in slot [dec].
Explanation The PF subsystem could not initialize OBFL [chars] feature.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PF_OBFL-5-STORAGE : Platform OBFL storage ([chars]) initialization fails in slot [dec].
Explanation The PF subsystem could not initialize OBFL storage flash.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PF_PRST_VBL-3-MEDIA : PF persistent variable media error: [chars]
Explanation Media error with the persistent variable PF interface.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PF_SP-2-6 : Recovered from RPC send failure for request [chars]. Resending request.
Explanation The communication error occurred during an RPC request. RPC will retry
Recommended Action No action is required.
Error Message%PF_SP-2-FAILED : Failed to send RPC request [chars] (fatal)
Explanation A fatal communication error occurred during an RPC request.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PF_SP-2-RETRY : Recovered from RPC send failure for request [chars]. Resending request.
Explanation The communication error has occurred during an RPC request. RPC will retry
Recommended Action No action is required.
Error Message%PGM-3-EXP_TSI_SQN_ERR : Expiring TSI %s has retransmit state
Explanation An expiring PGM TSI has unexpired retransmit state. This can only occur due to an internal error or due to unfreeable memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PGM-3-PAK_ALLOC_ERR : Failed to allocate buffer for %s
Explanation Resources (memory) for allocating packet buffers are not serviceable.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PGM-3-RTX_STATE_ALLOC_ERR : Failed to allocate [chars] state
Explanation Memory is exhausted for the retransmit state, or the memory is not serviceable.
Recommended Action Manually clear all retransmit states by entering the clear ip pgm router command, or deconfigure and reconfigure the PGM.
Error Message%PGM-3-RTX_STATE_FREE_ERR : Failed to free [chars] state
Explanation Memory for the retransmit state is not serviceable.
Recommended Action Manually clear all retransmit states by entering the clear ip pgm router command, or deconfigure and reconfigure the PGM.
Error Message%PGM-6-ADDR_ERR : Invalid %s address %i in %s
Explanation Received the packet with invalid address.
Recommended Action No action is required.
Error Message%PGM-6-PAK_IIF_FIXUP : Pak for %i received on %i, fixed input interface
Explanation A PGM packet was recieved on an interface other than the one it was addressed to.
Recommended Action No action is required.
Error Message%PGM-6-PAK_MALFORMED_ERR : Malformed packet: %s
Explanation A PGM packet did not pass the internal sanity check.
Recommended Action No action is required.
Error Message%PGM-6-QUEUE_FULL : Serviced full queue of PGM packets.
Explanation The PGM process is busy, either because of excessive retransmit state or because of excessive traffic.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PGM-6-TSI_GROUP_CHANGE : TSI group changed from [IP_address] to [IP_address]
Explanation The system has processed a PGM SPM advertising a new group for the TSI.
Recommended Action No action is required.
Error Message%PGM-6-TSI_SOURCE_CHANGE : TSI source changed from [IP_address] to [IP_address]
Explanation The system has processed a PGM SPM advertising a new group for the TSI.
Recommended Action No action is required.
Error Message%PGMHOST-6-INPUT_PACKET_ERR : Matched TSI but failed to match dport; expected %d actual %d
Explanation An incorrectly structured packet has been received from the netwrok.
Recommended Action Investigate and fix the other implementation of PGM.
Error Message%PGTT_IPC_MSG-2-ALLOC_ERR : Unable to allocate message packet to SECONDARY %u.
Error Message%PGTT_IPC_MSG-2-IPC_MSG_HANDLER_ERR : Error handling IPC message from SECONDARY processor.
Error Message%PGTT_IPC_MSG-2-IPC_PORT_TO_SECONDARY_ERR : Unable to open IPC port to SECONDARY slot %ld: %s.
Error Message%PGTT_IPC_MSG-2-PGTT_MSG_DEBUG : %s
Error Message%PGTT_IPC_MSG-2-PKTS_ALLOC_ERR : PKTS could not allocate message packet to SECONDARY %u.
Error Message%PGTT_IPC_MSG-2-PKTS_COUNT_REPLY_ALLOC_ERR : PKTS could not allocate count reply message.
Error Message%PGTT_IPC_MSG-2-RVT_PRIMARY_CREATE_ERR : Unable to create RVT-PRIMARY port. %PG_TCP-3-MSG_ERR : %s
Error Message%PG_TCP-6-MSG_INF : %s
Explanation Program information.
Error Message%PG_TCP-7-MSG_DBG : %s
Explanation Debug Messages.
Error MessageError Message%PHY-4-BADTRANSCEIVER : An inappropriate transceiver has been inserted in interface [chars].
Explanation An inappropriate transceiver was inserted at the interface specified in the error message. This transceiver should not be used in this system.
Recommended Action Remove the specified transceiver. If this transceiver was purchased from Cisco, 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PHY-4-CHECK_SUM_FAILED : SFP EEPROM data check sum failed for SFP interface [chars]
Explanation The SFP has been identified as a Cisco SFP, but the system was unable to read the vendor data information to verify its correctness.
Recommended Action Remove and reinsert the SFP. If the read operation fails again, the SFP may be defective.
Error Message%PHY-4-EXCESSIVE_ERRORS : Excessive FCS, data, or idle word errors found on interface [chars]
Explanation The system has detected excessive FCS, data word, or idle word errors on the specified interface.
Recommended Action Enter the show interface command on the specified interface and check for CRC and other input errors. If errors are excessive, enter the shutdown command followed by the no shutdown command to shut down and restart the interface.
Error Message%PHY-4-MODULE_DUP : SFPs in [chars] and in [chars] have duplicate vendor-id and serial numbers
Explanation The Small Form-factor Pluggable (SFP) module was identified as a Cisco SFP, but its vendor ID and serial number match that of another SFP in the system. The first [chars] represents the interface where the SFP is installed, and the second [chars] represents the interface where the duplicate SFP is installed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PHY-4-SFP_NOT_SUPPORTED : The SFP in [chars] is not supported
Explanation This Small Form-factor Pluggable Plus (SFP) type is not supported on this switch.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PHY-4-SFP_PLUS_NOT_SUPPORTED : The SFP PLUS in %s is not supported
Explanation The Small Form-factor Pluggable (SFP) PLUS type is not supported on this switch.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PHY-4-UNSUPPORTED_SFP_CARRIER : Unsupported SFP carrier module found in %s
Explanation The SFP carrier module was identified as an unsupported non-Cisco SFP carrier module.
Recommended Action Remove the unsupported SFP and procure a supported module.
Error Message%PHY-4-UNSUPPORTED_TRANSCEIVER : Unsupported transceiver found in %s
Explanation The specified module was identified as an unsupported non-Cisco transceiver.
Error Message 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PHY-4-XFP_NOT_SUPPORTED : The XFP in [chars] is not supported
Explanation 10-Gigabit Small Form Factor Pluggable (XFP) type is not supported on this switch.
Explanation 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PIF-3-DOWNLOAD_ERROR : [chars], [chars]
Explanation The image for the port interface could not be downloaded because the image is either corrupt, is invalid, or is not available. The interface could not be initialized.
Recommended Action Check the port interface status by entering the show pif command and repeat the operation with the port interface debug logs enabled. Enter the debug pif download command to enable the debug log. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-DOWNLOAD_SUBSYS_ERROR : [chars]
Explanation The download subsystem could not be created. The download procedure could not be started. It is possible that the download attempt might not succeed.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-DYN_DOWNLOAD_ERROR : [chars], [chars]
Explanation The image for the port interface could not be downloaded because the image is either corrupt, is invalid, or is not available. The interface could not be initialized.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-EPIF_MIPC_ERROR : [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-GIGE_AUTO_NEG_INIT_ERROR : [chars]
Explanation The gigabit Ethernet auto-negotiation operation has failed while the gigabit Ethernet interface was being configured.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-GIGE_DISABLE_GMAC_ERROR : [chars]
Explanation While the gigabit Ethernet interface was being disabled, the gigabit MAC could not be disabled.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-GIGE_ENABLE_GGI_ERROR : [chars]
Explanation During the initialization of the gigabit Ethernet interface, the generic gigabit Ethernet interface could not be enabled.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-GIGE_INIT_GMAC_ERROR : [chars]
Explanation While the gigabit Ethernet interface was being configured, the gigabit MAC could not be initialized.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-GIGE_LINKUP_INIT_ERROR : [chars]
Explanation The gigabit Ethernet linkup initialization operation has failed while gigabit Ethernet was being configured
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-IDB_CONFIG_PUNT_ERROR : Error configuring [char]PIF on RSC [dec] for packet punting
Explanation The system could not configure the specified hardware to redirect packets to the specified RSC. The most likely cause of this condition is the absence or failure of the peer RSC.
Recommended Action Replace or insert the peer RSC. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-PIF_INTERNAL : Internal PIF error [[chars]]
Explanation An internal error occurred within the PIF driver software.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-PIF_MAC_ERROR : [chars], [chars]
Explanation An internal software error has occurred. An internal module failed to allocate a MAC address to a port. This condition may lead to a communication failure between the RSC and the feature board.
Recommended Action Reload the gateway to attempt to fix the problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show pif and show tech-support commands. 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-PIF_RESET_INT : Function [chars] called from interrupt context
Explanation An internal software error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-READ_IMEM_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-READ_PHY_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-SLICER_ENABLE_ERROR : Enabling Tx/Rx on SMDR for [chars] port[dec] failed
Explanation An error relating to the port interface has occurred. The enabling of the transceiver on the station message detail recording port has encountered an error.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-UNKNOWN_EGRESS_CARD_TYPE_ERROR : Unknown Egress Card type [hex] for RSC [dec].
Explanation The system could not configure the specified hardware. The most likely cause is that the egress card is either unsupported or has experienced a hardware failure.
Recommended Action Replace the RSC or the egress card of the RSC. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-WRITE_IMEM_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-WRITE_PHY_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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%PIF-3-XPIF_MIPC_ERROR : [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, 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 MessageExplanation A PIM router received a register message from another PIM router that thinks it is the rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message.
Recommended Action Configure all the leaf routers (first-hop routers to multicast sources) with the IP address of the valid rendezvous point.
Error Message%PIM-1-INVALID_RP_REG : Received Register from router %i for group %i, %i not willing to be RP
Explanation A PIM router received a register message from another PIM router that thinks it is the rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message.
Recommended Action Configure all leaf routers (first-hop routers to multicast sources) with the IP address of the valid rendezvous point.
Error MessageExplanation A State-Refresh capable PIM neighbor on this interface has a different setting for the State-Refresh origination interval.
Recommended Action Configure all the PIM routers connected to this LAN to use the same State-Refresh origination interval for their interfaces on the LAN.
Error Message%PIM-1-SR_INTERVAL_SETTING_ERR : Incompatible SR interval from %i on %s (%d != %d)
Explanation A State-Refresh capable PIM neighbor on this interface has a different setting for the State-Refresh origination interval.
Recommended Action Configure all PIM routers connected to this LAN to use the same State-Refresh origination interval for their interfaces on the LAN.
Error Message%PIM-3-TWHEEL_INIT_ERR : Unable to create PIM timer wheel
Explanation An error occured intializing the PIM timer twheel.
Recommended Action An error in maintaining the PIM timer wheel occurred. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error MessageExplanation A PIM neighbor is running an old software that uses deprecated Hello Option TLVs. Unless the router is upgraded, DR priority and bidirectional groups may not function properly.
Recommended Action Upgrade all the routers.
Error Message%PIM-4-DEPRECATED_HELLO_TLV : Deprecated PIM Hello Option TLV [dec] ([chars]) from [IP_address] ([chars])
Explanation A PIM neighbor is running old software that uses deprecated Hello Option TLVs. Unless the router is upgraded, DR priority and bidirectional groups may not function properly.
Recommended Action Upgrade all the routers to a later version of Cisco IOS Software.
Error MessageExplanation A PIM router configured as a rendezvous point and received a register message from another PIM router but the source of the multicast data is not allowed in this RP.
Recommended Action This is an informational message only. No action is required.
Error Message%PIM-4-INVALID_SRC_REG : Received Register from [IP_address] for ([IP_address], [IP_address]), not willing to be RP
Explanation A PIM router configured as a rendezvous point has received a register message from another PIM router, but the source of the multicast data is disallowed in this RP.
Recommended Action No action is required.
Error Message%PIM-5-DRCHG : DR change from neighbor %i to %i on interface %s
Explanation A PIM neighbor is the new DR on an interface.
Recommended Action No action is required.
Error Message%PIM-5-NBRCHG : neighbor %i %s on interface %s %s
Explanation A PIM neighbor has gone UP or DOWN on an interface.
Recommended Action No action is required.
Error Message%PIM-5-PROXY : Deny proxy for ([IP_address], [IP_address]) from neighbor [IP_address] (vrf [chars])
Explanation Deny PIM Proxy from neighbor.
Recommended Action No action is required.
Error MessageExplanation A downstream PIM router sent a join message for the shared tree, which this router does not want to accept. This behavior indicates that this router will let only downstream routers join to a specific rendezvous point.
Recommended Action Configure all downstream leaf routers to join to the RP that is allowed by upstream routers toward the validated rendezvous point.
Error Message%PIM-6-INVALID_RP_JOIN : Received (*, %i) Join from %i for invalid RP %i
Explanation A downstream PIM router sent a join message for the shared tree, which this router does not want to accept. This behavior indicates that this router will let only downstream routers join to a specific rendezvous point.
Recommended Action Configure all downstream leaf routers to join to the RP that is allowed by upstream routers toward the validated rendezvous point.
Error MessageExplanation A PIM router configured as a rendezvous point or with network address translation (NAT) received a PIM Register packet from another PIM router. The data encapsulated in this packet is invalid.
Recommended Action This is an informational message only. No action is required.
Error Message%PIM-6-REG_ENCAP_INVALID : Bad register from %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x
Explanation A PIM router configured as a rendezvous point or with network address translation (NAT) received a PIM Register packet from another PIM router. The data encapsulated in this packet is invalid.
Recommended Action No action is required.
Error MessageExplanation PIM router configured as MSDP peer received a SA with encapsulated data. The data encapsulated in this packet is invalid.
Recommended Action This is an informational message only. No action is required.
Error Message%PIM-6-SA_ENCAP_INVALID : Bad SA from RP %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x
Explanation A PIM router configured as MSDP peer received a SA with encapsulated data. The data encapsulated in this packet is invalid.
Recommended Action No action is required.
Error Message%PIMP-2-NOMEM : No memory available for [chars]
Explanation Process interrupt mask profiler subsystem could not obtain the memory it needed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PIMSN-6-IGMPSN_GLOBAL : PIM Snooping global runtime mode %s due to IGMP Snooping %s
Explanation PIM snooping requires IGMP snooping to be enabled. When IGMP snooping is disabled, PIM snooping gets disabled too. It gets re-enabled when IGMP snooping is enabled
Recommended Action Nothing. The system is working properly. It is advisable to have IGMP Snooping always enabled.
Error Message%PIMSN-6-IGMPSN_VLAN : PIM Snooping runtime mode on vlan %d %s due to IGMP Snooping %s
Explanation PIM snooping requires IGMP snooping to be enabled. When IGMP snooping is disabled, PIM snooping gets disabled too. It gets re-enabled when IGMP snooping is enabled.
Recommended Action Nothing. The system is working properly. It is advisable to have IGMP Snooping always enabled.
Error Message%PIM_PROT-3-IDB_INIT : [chars] in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-IM_ERR : Interface Manager error - [chars] in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-LIST_ERR : List error in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-MSG_SEND_ERR : [chars]
Explanation An internal error has occurred while a message was being sent. Events that are scheduled to occur when this message is received, such as deletion of the PIM tunnel IDB, may not occur.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-PAK_ERR : An internal error occured while processing a packet queue
Explanation A managed queue event has been received without a packet.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-PROTOCOL_ERR : [chars] - [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-RP_INIT : [chars] in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-SHUTDOWN_ERR : Error in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-3-SRC_UPDATE_ERR : Error in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_PROT-6-IDB_ENABLE : Interface [chars] does not support multicast, not enabled
Explanation The PIM feature has not been enabled on an interface that does not support multicasting.
Recommended Action No action is required.
Error Message%PIM_PROT-7-INTERNAL_ERR : [chars]
Explanation An internal error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PIM_REG_TUN-3-SET_SRC_ERR : Failed to set PIM register tunnel source for [chars] to [chars]
Explanation The PIM tunnel is not usable without a source address. This can happen because of an internal error.
Recommended Action Manually unconfigure the PIM-SM RP and re-configure it.If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PIM_REG_TUN-3-UNNUM_ERR : Failed to update source on Encaps idb, [chars]
Explanation Memory resources required for the retransmit state are exhausted or otherwise not serviceable.
Recommended Action Manually unconfigure and re-configure the PIM-SM RP. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PKI-3-AUTOCERTERR : Auto Certificate (re)enrollment failed. Cannot retry
Explanation Automatic certificate re-enrollment failed.The router clock my not be set correctly. If the router has a certificate it might be expired.
Recommended Action Check router clock is set correctly. Ensure the router's certificate has not expired.
Error Message%PKI-3-CERTIFICATE_INVALID : Certificate chain validation has failed.
Explanation The certificate is not valid.
Recommended Action Check the system clock to determine if it is set correctly.
Error Message%PKI-3-CERTIFICATE_INVALID_EXPIRED : Certificate chain validation has failed. The certificate (SN : [chars]) has expired. Validity period ended on [chars]
Explanation The certificate validity period indicates that this certificate has expired.
Recommended Action Check the system clock to determine if it is set correctly.
Error Message%PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID : Certificate chain validation has failed. The certificate (SN : [chars]) is not yet valid Validity period starts on [chars]
Explanation The certificate validity period indicates that this certificate is not yet valid.
Recommended Action Check the system clock to determine if it is set correctly.
Error Message%PKI-3-CERTIFICATE_INVALID_UNAUTHORIZED : Certificate chain validation has failed. Unauthorized
Explanation The certificate is valid but not authorized.
Recommended Action Check the system clock to determine if it is set correctly.
Error Message%PKI-3-CERTIFICATE_REVOKED : Certificate chain validation has failed. The certificate (SN : [chars]) is revoked
Explanation The certificate has been revoked by the CA administrator.
Recommended Action Check the status, contact the CA administrator.
Error Message%PKI-3-CERTPENDERR : Failed to receive pending certificate during enrollment
Explanation The router's certificate remains in a pending state after the maximum number of retries to enroll.
Recommended Action Retry the enrollment. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. .
Error Message%PKI-3-CERTRETFAIL : Certificate enrollment failed.
Explanation Certificate enrollment transaction failed due to internal error.
Recommended Action Contact CE.
Error Message%PKI-3-CS_CRIT_STORAGE : Critical certificate storage, [chars], is inaccessible, server disabled.
Explanation Critical certificate storage is inaccessible, server disabled.
Recommended Action Make storage accessible, or re-configure the storage location.
Error Message%PKI-3-GETCARACERT : Failed to receive RA/CA certificates.
Explanation Encountered failure when parsing and processing CA/RA certificates
Recommended Action Check the status, contact the CA administrator.
Error Message%PKI-3-INVALIDCACERT : Failed to process CA certificate.
Explanation Failed to process the ca certificate received from ca server.
Recommended Action Use parser command cr ca auth and try again.
Error Message%PKI-3-INVALID_INPUT : The input to the parser command is not correct
Explanation The input to the parser command is not correct.
Recommended Action Repeat the command.
Error Message%PKI-3-POLLCACERT : Polling CA certificate .....
Explanation Polling ca certificate.
Recommended Action Check if CA or ldap server is online.
Error Message%PKI-3-POLLRACERT : Polling RA certificate .....
Explanation Polling ra certificate.
Recommended Action Check if CA or ldap server is online.
Error Message%PKI-3-POLLROUTERCERT : Polling Router certificate .....
Explanation Polling router certificate.
Recommended Action Check if CA or ldap server is online.
Error Message%PKI-3-QUERYCACERT : Failed to query CA certificate.
Explanation Failed to query ca certificate from ca server.
Recommended Action Use parser command cr ca auth and try again.
Error Message%PKI-3-QUERY_KEY : Querying key pair failed.
Explanation Querying public key/private key using subject name failed
Recommended Action Resubmit enrollment request. Check the subject name.
Error Message%PKI-3-SOCKETSELECT : Failed to select the socket.
Explanation The failure is caused by socket selection.
Recommended Action Check tcp/socket debugging message.
Error Message%PKI-3-SOCKETSEND : Failed to send out message to CA server.
Explanation The failure is caused by http transaction.
Recommended Action Check http connection to the CA server.
Error Message%PKI-3-UNUSABLE_KEY_USAGE : Key-usage type '[chars]' for cert with serial number [chars] is not usable.
Explanation The given key-usage type is not usable by IOS. If seen during an import operation, this will likely cause the import to fail. Acceptable key-usage types should include Key-encipherment and/or digital-signature. Other key-usage types may be present, but will be ignored.
Recommended Action Recreate the certificate with key-encipherment, digital-signature, or both.
Error Message%PKI-4-AUTOCERTFAILWARN : Certificate (re)enrollment failed. Delaying before retry
Explanation Automatic certificate re-enrollment failed. The router will retry in six hours or less dependingon the expiration time of the router's certificate. Caution - Router's Certificate might expire soon.
Recommended Action The router will retry. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error MessageExplanation The CRL location is not reachable. Make sure the server is online.
Recommended Action Verify that the CRL is at the location specified in the certificate, and that the server is operational. To see the interaction between Cisco IOS software and the CRL server, use the debug crypto pki transactions command.
Error MessageExplanation Inserting or verifying the CRL failed. If the trustpoint revocation check includes the keyword none, then the transaction succeeds. If the revocation checking is not optional, then the transaction fails.
Recommended Action Check the CRL manually to verify if it is correct. To see the interaction between Cisco IOS software and the CRL server, use the debug crypto pki transactions command.
Error Message%PKI-4-CRL_LDAP_QUERY : The CRL could not be retrieved from the specified LDAP server
Explanation The certificate revoocation list is located on an LDAP server, but the LDAP query failed.
Recommended Action Check that the LDAP server is reachable and online. Verify that the CRL is at the specified location.
Error Message%PKI-4-CS_PUBLISH_STORAGE : Publish certificate storage, [chars], is inaccessible.
Explanation Publish certificate storage is inaccessible.
Recommended Action Make storage accessible, or re-configure the storage location.
Error MessageExplanation Too many redirections occurred while fetching a CRL through the HTTP; hence, the operation has aborted. If the trustpoint revocation check includes the keyword none, then the transaction succeeds. If the revocation checking is not optional, then the transaction fails.
Recommended Action Verify that the CRL is at the location specified in the certificate, and that the server is operational. To see the interaction between Cisco IOS software and the CRL server, use the debug crypto pki transactions command.
Error Message%PKI-4-NOAUTOSAVE : Configuration was modified. Issue write memory to save new certificate
Explanation Auto-Enroll has obtained a new router key pair and certificate.However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new certificate(s) and key(s).
Error Message%PKI-4-NOCONFIGAUTOSAVE : Configuration was modified. Issue write memory to save new IOS PKI configuration
Explanation IOS PKI APIs have generated new PKI configuration.However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new PKI configuration.
Error Message%PKI-4-NOSHADOWAUTOSAVE : Configuration was modified. Issue 'write memory' to save new IOS CA certificate
Explanation IOS CA Rollover has generated a shadow CA key pair and certificate. However, the running configuration was previously modified.
Recommended Action Enter the write memory command to save the new certificate(s) and key(s).
Error Message%PKI-6-AUTOCERTFAIL : Certificate (re)enrollment failed. Delaying before retry
Explanation Automatic certificate enrollment or re-enrollment failed. The router will retry in six hours or less depending on the expiration time of the router's certificate.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKI-6-AUTOENROLL_KEY_LOCKED : Auto-enroll failed - RSA keypair is locked
Explanation Auto-enroll attempted to generate a new RSA keypair.However the existing RSA keypair is locked so auto-enroll cannot proceed
Recommended Action Auto-enroll will retry the enrollment request. Ensure the existing RSA keypair is unlocked before the next retry.
Error Message%PKI-6-AUTOSAVE : Running configuration saved to NVRAM
Explanation Auto-Enroll has obtained a new router key pair and certificate, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CERTFAIL : Certificate enrollment failed.
Explanation Certificate enroll encounter fatal error.
Recommended Action Contact the CA administrator.
Error Message%PKI-6-CERTIFSRECV : Could not receive router's Certificate from file system.
Explanation The router's certificate could not be received from file system.
Recommended Action Verify the enrollment URL and that the router is able toread from the file system.
Error Message%PKI-6-CERTIFSSEND : Could not send Certificate enrollment request to file system.
Explanation The certificate enrollment request could not be sent to file system.
Recommended Action Verify the enrollment URL and that the router is able towrite to the file system.
Error Message%PKI-6-CERTPENDING : Enter manual authentication ...
Explanation CA server want to manually authenticate the router.
Recommended Action Follow a manual authentication procedure.
Error Message%PKI-6-CERTREJECT : Certificate enrollment request was rejected by Certificate Authority
Explanation A previous certificate enrollment request was received by the Certificate Authority. It has rejected the enrollment request.
Recommended Action Contact the Certificate Authority administrator.
Error Message%PKI-6-CERTRET : Certificate received from Certificate Authority
Explanation A previous certificate enrollment request was received by the Certificate Authority. It has issued the certificate, and sent back a copy
Recommended Action Informational message only. No action required.
Error Message%PKI-6-CERT_FATAL_ERR : %s
Explanation Certificate enroll encounter fatal error. Abort.
Recommended Action Contact the CA administrator.
Error Message%PKI-6-CONFIGAUTOSAVE : Running configuration saved to NVRAM
Explanation IOS PKI APIs have generated new PKI configuration, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message.
Error MessageExplanation The CRL fetch has returned a redirect directive. This is not an error if the file exists at the redirected location.
Recommended Action If there are no other errors, this message implies that the CRL has been fetched from the new location. No action is required. To see the interaction between Cisco IOS software and the CRL server, use the debug crypto pki transactions command.
Error Message%PKI-6-CS_DELETE : Certificate Server is deleted.
Explanation Certificate Server is deleted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_DELETE_TP_KEY : Trustpoint and key deleted.
Explanation Trustpoint and key used by the Certificate Server are deleted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_DISABLED : Certificate server now disabled.
Explanation Certificate server now disabled.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_ENABLED : Certificate server now enabled.
Explanation Certificate server now enabled.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_GRANT_AUTO : All enrollment requests will be automatically granted.
Explanation All enrollment requests will be automatically granted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_GRANT_AUTO_CACERT : All rollover subordinate CA cert requests will be automatically granted.
Explanation All rollover subordinate CA cert requests will be automatically granted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_GRANT_AUTO_RA : Enrollment requests coming from known RAs will be automatically granted.
Explanation Enrollment requests coming from known RAs will be automatically granted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_GRANT_AUTO_RACERT : All rollover RA cert requests will be automatically granted.
Explanation All rollover RA cert requests will be automatically granted.
Recommended Action No action required. Informational message.
Error Message%PKI-6-CS_REJECT_AUTO : All enrollment requests will be automatically rejected.
Explanation All enrollment requests will be automatically rejected.
Recommended Action No action required. Informational message.
Error Message%PKI-6-PKCS12EXPORT_FAIL : PKCS #12 Export Failed.
Explanation An attempt to generate and export a PKCS #12 has failed.
Recommended Action No action required. Informational message.
Error Message%PKI-6-PKCS12EXPORT_SUCCESS : PKCS #12 Successfully Exported.
Explanation A PKCS #12 has been generated and successfully exported.
Recommended Action No action required. Informational message.
Error Message%PKI-6-PKCS12IMPORT_FAIL : PKCS #12 Import Failed.
Explanation An attempt to import a PKCS #12 has failed.
Recommended Action No action required. Informational message.
Error Message%PKI-6-PKCS12IMPORT_SUCCESS : PKCS #12 Successfully Imported.
Explanation A PKCS #12 has been successfully imported.
Recommended Action No action required. Informational message.
Error Message%PKI-6-SHADOWAUTOSAVE : Running configuration saved to NVRAM
Explanation IOS CA Rollover has generated a shadow CA key pair and certificate, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message.
Error Message%PKTS-3-BUFLEN : Zero length buffer detected in [chars] for [chars]([hex])
Explanation An application buffer error has been detected in the channel adapter packet-switching API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-CONSISTENCY : [chars] : [chars] [hex] [dec]
Explanation A consistency error has been detected in the channel adapter packet-switching API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-INIT : [chars] ([dec])
Explanation The CMCC packet switching initialization has failed because of a lack of memory on the card. Packets will not be switched between the CMCC card and the Route Processor.
Recommended Action Verify that the amount of memory installed an the CMCC card is capable of supporting the configured CMCC microcode.
Error Message%PKTS-3-NOSUPP : [chars] ([hex],[hex])
Explanation An attempt was made to call a function in a packet-switching API control block that was not implemented or supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-NOTREADY : packet switching API not initialized - [chars]
Explanation An attempt was made to call a function in a packet-switching API before the initialization of the API was complete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-SEGMENT : [chars] : [chars] [hex] [dec]
Explanation A data buffer containing too many segments or particles to transmit to the platform Route Processor was detected. The packet is being dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS_INFO-6-MSG : %s
Error Message%PLATFORM--ELEMENT_CRITICAL : %s/%d: %s value %s %s critical level %s
Explanation The shell-manager monitors the health of each boardand will emit an error message when a value has passeda critical level
Recommended Action UNAVAILABLE
Error Message%PLATFORM--ELEMENT_WARNING : %s/%d: %s value %s %s warning level %s
Explanation The shell-manager monitors the health of each boardand will emit a warning message when a value has passeda critical level
Recommended Action UNAVAILABLE
Error Message%PLATFORM-0-ARP : ARP error: [chars]
Explanation An unexpected error occurred while performing ARP operation .
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-5-CONFIG_RECOVERY: IOS Configuration recovery is in progess.
Explanation The reset button was pushed at boot time and the golden configuration is being recovered.
Recommended Action No action is required.
Error Message%PLATFORM-4-I2C_NOTAVAIL: Device [dec] on I2C bus [dec] is not available for [chars]
Explanation The device is not available on the Inter-Integrated Circuit (I2C) bus for this platform. The router might not operate normally.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-4-QUEUE_FULL: Ethernet Switch Module transmit queue is full
Explanation The transmit queue of the switch module was full and packets are being dropped.
Recommended Action Reduce the rate of packet transmission to the Switched Virtual Interfaces (SVI) to be less than 9 Mbps.
Error Message%PLATFORM-5-RESET_BUTTON: Reset Button pressed during boot up.
Explanation The reset button has been pushed at the boot up time and the system has been directed to take necessary action.
Recommended Action No action is required.
Error Message%PLATFORM-0-NM_REMOVED_SM2NM : Network module was removed from the SM2NM adapter in slot [dec]
Explanation The network module was removed while online from the SM2NM adapter. For online insertion and removal, the network module must be removed with the SM2NM adapter.
Recommended Action Enter the managed OIR command for the online removal of the network module and the SM2NM adapter. Enter hw-module slot command prior to online removal of the service module and remove the SM2NM adapter with the network module installed.
Error Message%PLATFORM-0-PCIE_ERR : [chars] Detect PCIe [dec] error, [hex], [hex], [hex], [hex], [hex]
Explanation The system has detected a severe PCIe error, such as the PCIe fatal error messages received by root complex. The system cannot recover from this fatal error on by its own and a system reset is required.
Recommended Action The system will restart automatically. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-0-SAMI_INVALID_SLOT_ID : Invalid slot id [dec] in ROMMON cookie at [hex]
Explanation Unable to determine the slot number of the 7600/6500 chassis containing this SAMI card. Since the card cannot continue to operate without this information, it was reloaded.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-0-SURPRISE_OIR : Non-managed Online removal of card in slot [dec]
Explanation The service module was unexpectedly removed while online. Unmanaged online removal is not supported. The managed OIR CLI must be used for online removal of service modules.
Recommended Action Enter the hw-module slot stop command prior to the online removal of the service module.
Error Message%PLATFORM-1-CRASHED : [chars]
Explanation The system is attempting to display further information regarding the crash that just occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-1-DP_HM_FAIL : Failed to receive response from [chars]. Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more info
Explanation Data path monitoring has missed configured number of responses and indicating failure. This can be caused if there is an issue in the hardware path between backplane and NP (IXP) or a software issue or a configuration issue.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-1-HMPROBE_IPFAIL : [chars] while sending probe to [IP_address]. Effectively, probe monitoring will be ignored. Please make necessary modifications to sami health-monitoring probe CLI
Explanation The CLI sami health-monitoring probe will not be effective because either there is no suitable local source ip that can be used to send ping packets to the configured address, or the peer address is not responding, or there is some other data path issue.
Recommended Action Correct configuration such that pings can be sent and responses received by using ping ip. If you do not need the probe monitoring, you can unconfigure it using the CLI no sami health-monitoring probe. If pings are working fine without giving any explicit source ip address but this message is still seen, then cCopy 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-1-SPUR_INT : Detected spurious timer interrupt
Explanation The CPU detected an unexpected interrupt event. There is no interrupt service routine assigned to this interrupt.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-1-UNRECOGNIZED_BOARD_TYPE : Unrecognized main board type: [hex].
Explanation The mainboard type, read from on-board registers, has an unexpected value. This can have two typical causes. If the version of Cisco IOS software does not support this version of hardware, then this error could be a software problem. If the on-baord registers are not working properly to identify the type of hardware, then this error could be a hardware problem. In either case, the router will not operate properly.
Recommended Action Ensure that the lastest version of Cisco IOS software is installed and supported by this hardware. Otherwise, you can try a different hardware of the same model to check if the problem is resolved. In this case, the hardware must be repaired. Before returning any hardware, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-BOOT_BUS_ERR : MIO Boot bus error [hex]
Explanation The boot bus, which is a hardware unit inside the processor, connects to the flash memory and the compact flash for initial booting. When the boot bus hardware unit encounters either an address-decode or a wait-mode error, the boot bus notifies the CPU through an interrupt.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show run and show version commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-CIU_ALLOC_ERR : Cannot allocate the CIU interrupt type [dec]
Explanation The CIU, which is a hardware unit inside the processor, aggregates the module and the IO-controller's interrupts and reports them to the CPU. There are many CIU interrupt resources in the chip, but an interrupt resource can be allocated only by an application. This error message indicates that an application is attempting to allocate an interrupt resource that has been allocated by other applications. The application may not function properly because of this software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-CIU_DEALLOC_ERR : Cannot deallocate the CIU interrupt - [chars] type [dec]
Explanation The CIU, which is a hardware unit inside the processor, can release its interrupt resource when the it does not need it. This interrupt resource becomes unusable after this software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-CIU_DIS_ERR : Cannot disable the CIU interrupt - [chars] type [dec]
Explanation The CIU, which is a hardware unit inside the processor, can disable an interrupt resource when the it does not need it. This interrupt resource may still be in the enabled state after this software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-CIU_ENA_ERR : Cannot enable the CIU interrupt type [dec]
Explanation The CIU is a hardware unit inside the processor. The application might have attempted to enable the interrupt before allocating it or to pass incorrect parameter to platform interrupt API. The application may not function correctly, because of this software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-CIU_INV_TYPE : Invalid CIU interrupt type [dec].
Explanation The CIU is a hardware unit inside the processor. The allocate or deallocate CIU interrupt resource failed because of the invalid interrupt type requested from the CIU. The CIU may not function correctly, because of this software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-FPA_MEM_ERR : FPA memory error - [hex]
Explanation The router will be automatically reload and recover this memory multi bit error detected in the FPA.
Recommended Action The system will be automatically restarted. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-2-INITFAIL : [chars] [dec] failed
Explanation A hardware or software error has occurred.
Recommended Action Reload the router to recover. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-2-ISR_ERR_MSG : [chars], [hex] [hex]
Explanation The platform interrupt service routine detects abnormal events. This could be a software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-2-NO_POLL_TIMER : Cannot allocate a polling timer
Explanation A software error has occurred. The Voice DSP driver requested a hardware poll timer, but system does not have the resource available at the moment. As a result, the voice application will not function correctly.
Recommended Action Reload the router. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-2-PHY_CONFIG : [chars], Onboard GE PHY configuration failed
Explanation The Onboard GE Ethernet device driver attempted to configure the Ethernet PHY device, but the PHY configuration failed. This may be a transient error. Reload the system.
Recommended Action If the problem recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the debug ethernet-interface command and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-CLK_SET_FAILED : Failed to set clock received from proc0
Explanation System clock is not updated with the proc0 clock during bootup.
Recommended Action Set the clock manually, or configure ntp.
Error Message%PLATFORM-3-CLK_SYNC_FAILED : Failed to receive clock update from proc0
Explanation System clock is not updated with the proc0 clock during bootup.
Recommended Action Set the clock manually, or configure ntp.
Error Message%PLATFORM-3-ENERGYWISE_REG : Could not register type [dec], slot [chars], mask [hex], due to [chars]
Explanation The slot of indicated type failed to register with the energy-wise subsystem due to the reason specified in the message. This results in no energy-wise functionality for the indicated slot.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform hw-module-power and show diag commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-FATALCINNAMON : The FPGA controller has received a fatal interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]
Explanation The FPGA controller has received a fatal interrupt. This error could be either a hardware or a software problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FATALPXF : Fatal PXF interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]
Explanation The PXF has issued a fatal interrupt. This condition can be caused by a hardware or a software problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPA_ERR : FPA Pool [dec] error, int_sum [hex], expect [hex], actual [hex], avail [hex]
Explanation The Free Pool Allocator (FPA) unit, which is a hardware unit within the processor, has detected its internal queue error and reports to the CPU. This could be because of a hardware error or a software that incorrectly programs the FPA that causes the FPA to report this error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-FPGAUPDBRDNOACCESS : Cannot access Slot [dec], FPGA version check and update skipped.
Explanation The system cannot access the line card or the NSE to perform the FPGA version check and update.
Recommended Action Do not remove either any line cards or the NSE during the FPGA version check and update process. 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDFAIL : Slot [dec] [chars] update from version [dec].[dec] to version [dec].[dec] failed. System may not function properly.
Explanation An FPGA update has failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDLCNOACTIVE : Slot [dec] linecard activation failed after FPGA update, error code = [dec]
Explanation The system cannot activate the line card after the FPGA update.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDLCNODEACTIVE : Slot [dec] linecard deactivation failed after FPGA update, error code = [dec]
Explanation The system cannot deactivate the line card after the FPGA update.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDLCNORESET : Slot [dec] linecard reset failed after FPGA update
Explanation The system cannot reset the line card after the FPGA update.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDNOACCESS : Cannot access Slot [dec] [chars], FPGA version check and update skipped.
Explanation The system cannot access the FPGA flash.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDNORELOAD : After FPGA update, Primary NSE reload was aborted. Need to reload in order for the new FPGA image(s) to take effect
Explanation The FPGA of the primary NSE has been updated. However, the system did not reload.
Recommended Action Reload the primary NSE. If the reload 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-FPGAUPDUITIMEOUT : System FPGA update skipped for slot [dec] and up due to no user response.
Explanation The system FPGA update has been skipped because there is no user response.
Recommended Action Enter the upgrade fpga all command in EXEC mode to manually start the whole-system FPGA version check and update process. This process ensures that all the FPGAs in the system are compatible.
Error Message%PLATFORM-3-GEC_NOMAC : Can't allocate MAC address for port-channel interface %u
Explanation MAC address allocation failed for the port-channel interface specified in the message. This may happen if the port-channel interface exceeds the maximum number of supported port-channel interfaces.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-HASTATUS_FAIL : RP switchover, %s (count %u)
Explanation RP switchover failed to reach active state. The RP will be reset. This is indicative of a IPC problem between IOSd and CMRP
Recommended Action Make sure system achieves full redundant state after the RP reset. If not, reload entire system.
Error Message%PLATFORM-3-INTERNAL_INTERRUPT : [chars] [chars]
Explanation An internal error has occurred in the platform interrupt routine. This is a general software issue.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-IOMEM_INVALID : Current I/O memory setting [dec] MB invalid. Using default value [dec] MB
Explanation There are only certain values allowed for IO memoryconfiguration based on the total memory available. Currently configured value is not allowed. Default value will be used
Recommended Action Choose a valid I/O memory setting using the CLI memory-size iomem.
Error Message%PLATFORM-3-IOMEM_MISMATCH : I/O memory size mismatch. Allocated size [dec] MB, Configured size [dec] MB. Updated nvvar per configuration. Reload again for this to be effective.
Explanation The configured I/O memory size does not agree with the size setting stored in the non-volatile variable. This could happen in case the config was not saved after size setting modified last time. Other possibility could be nonvolatile variable write failed last time but config was saved.
Recommended Action Remove memory-size iomem CLI and add it again. Save configuration and verify both startup and running configurations agree each other with respect to this CLI. Reload the router for this to come into effect.
Error Message%PLATFORM-3-IPD_ERR : IPD error [hex]
Explanation The Input Packet Data Unit (IPD) is a hardware unit within processor. When the IPD internal module detects either memory parity error or interface error, it notifies the CPU through interrupt.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-LCCONFIG : Exceeds [dec] [chars]
Explanation The aggregate throughput of line cards exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed aggregate throughput of line cards for the system.
Error Message%PLATFORM-3-MINIMALBOOT : System in minimal boot mode.
Explanation The system came up in minimal boot mode. This condition can be because of an incompatible FPGA or hardware version, or the FPGA might not be properly loaded.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation The MAC address allocation has failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-NO_BASEMAC : Can't retrieve base MAC address
Explanation Base MAC address determination failed at system start.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NO_HARDWARE_RESOURCES : Not enough hardware resources. Shutting down [chars]
Explanation There are too many VLANs and routed ports on the system.
Recommended Action Reduce the total number of vlans and routed ports to be fewer than 1,023. If this configuration and connectivity requires to be maintained across system reboots, save the configuration to NVRAM.
Error Message%PLATFORM-3-NVRAM_OPEN_FAIL : Failed to open nvram - %s.
Explanation The nvram device could not be opened.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NVRAM_READ_FAIL : Failed to read nvram - %s.
Explanation The nvram contents could not be read.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NVRAM_WRITE_FAIL : Failed to write nvram - %s.
Explanation Couldn't write into the nvram device.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-PACONFIG : Exceeds [dec] [chars]
Explanation The total bandwidth of high and medium bandwidth port adapters exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
Error Message%PLATFORM-3-PCIE_ERRMSG : [chars] [hex]
Explanation The router's PCIe root complex received an unsupported message from a downstream PCIe node or a memory access timeout has occurred across the PCIe. The network device driver may not function correctly after this event. If the problem recurs, reload the system to recover.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-PIP_ERR : PIP error reg [hex]
Explanation The Packet Input Processing Unit (PIP), which is a hardware unit within the processor detected a memory parity error and notifies CPU through an interrupt. This could be a hardware error.
Recommended Action If this problem is recurs, replace the hardware. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-PKO_ERR : PKO error reg [hex]
Explanation The Packet Output Unit (PKO) is a hardware unit within the processor. A read-parity error has occurred in the port data buffer of the PKO. If this error is recurs, replace the hardware.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-PORT_NOT_OPERATING : %s %s %s %s
Explanation The port is not operating, the startup selftest has failed
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-POW_ERR : POW error reg [hex] - [hex]
Explanation The Packet Order Work (POW) unit is a hardware within the processor. When the POW detects a memory or internal operation error, it interrupts the CPU. The memory error can be either single-bit or multi-bit error. If it is a multi-bit memory error, the router will be reloaded automatically and hardware replacement is required. If it is a single-bit memory error, the POW will correct it by itself. Other errors like POW illegal operation and POW remote pointer errors could be reported as well. If the router reloads because of the multi-bit memory error, then the router hardware replacement is required.
Recommended Action If system is automatically restarted, capture the crash dump from flash. Otherwise, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-3-PW_REC_HRPC_BAD_LENGTH : Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec].
Explanation The system has received an incompatible length parameter in a set-password-recovery HRPC message. This condition could be caused by a stack that is operating with incompatible software versions on different stack members.
Recommended Action Ensure that all stack members are running compatible software images. If the problem persists, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-PW_REC_HRPC_NOT_ON_MASTER : Set-password-recovery HRPC msg from box [dec] received on master.
Explanation The active stack has received a set-password-recovery HRPC message. These types of messages should only be received on standby systems.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-PW_REC_HRPC_ONLY_ON_MASTER : Get-password-recovery HRPC msg from box [dec] received on slave.
Explanation A standby switch has received a get-password-recovery HRPC message. These types of messages should only be received by the active stack.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-3-RF_PROG_FAIL : Progression completion notification to chassis management failed, %s
Explanation Could not notify the completion of the RF progression to the chassis management process. The system will potentially not be in a fully redundant state.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-RF_RELOAD_PEER : Reload peer notification to chassis management failed, %s
Explanation Could not notify Reload Peer to the chassis management process. The Standby peer could not be reloaded by the Active. The system will potentially not be in a fully redundant state.
Recommended Action Reload peer instance using the available CLI commands. If system does not achieve full Standby status after that, the system must be reloaded.
Error Message%PLATFORM-3-SAMI_HM_FAIL : [chars]
Explanation Platform error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-3-SAMI_IPC_FAIL : [chars]
Explanation Platform error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-3-SAMI_IPC_IXP_FAIL : [chars]
Explanation Error in PowerPC - IXP Communication. Further configuration may not be effective.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-3-SAMI_SVC_FAIL : [chars]
Explanation Platform error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-3-SM2NM_OIR : SM2NM adapter inserted without network module in slot [dec]
Explanation The SM2NM adapter card was inserted without network module installed. For online insertion, the SM2NM adapter must be inserted with the network module in the slot.
Recommended Action The SM2NM adapter card must be inserted with the network module in the slot.
Error Message%PLATFORM-3-SPEED_DUPLEX_MISMATCH : [chars] does not support mixed auto and non-auto speed and duplex settings. Default both speed and duplex to auto.
Explanation The hardware does not support mixed auto and non-auto speed and duplex settings. The speed and the duplex settings should be both be set to auto or non-auto. Any mismatch results in both settings default to auto-negotiated.
Recommended Action Set the speed and the duplex settings of the port to both be auto or both be non-auto.
Error Message%PLATFORM-3-UNEXPECTED : [chars]
Explanation Platform error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]
Explanation The contents of the MAC address in the EEPROM is invalid. The system is providing a random MAC address.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PLATFORM-4-DEVICE : Device [chars] (Slot [dec], Device Instance [dec]) - [chars]
Explanation The system software encountered an error while the indicated device was being accessed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-2-DP_IXP_HM_WARN: Failed to receive response from IXP1 in 16 retries, system will reboot if it continues to fail receiving response in another 16 retries (i.e. in the next 256 milliseconds.)
Explanation This message indicates the possibility of system reload in future due to the chances of data path monitoring missing configured number of responses. This can be caused if there is an issue in the hardware path between backplane and NP (IXP) or a software issue or a configuration issue.
Recommended Action 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-4-FPGAUPDNOBNDLIMG : System cannot retrieve a compatible bundled FPGA image for slot [dec] [chars] (hardware version [dec].[dec]), FPGA version check and update skipped
Explanation The Cisco IOS software does not have a compatible FPGA image bundled.
Recommended Action Check the field alerts and other related documents to ensure that this particular line card or NSE is supported. Upgrade the hardware or the Cisco IOS release, if needed.
Error Message%PLATFORM-4-FPGAUPD_RELOAD_SKIP : After the FPGA update, the card in slot [dec] was not reloaded. The card should be reloaded for the new FPGA image to take effect.
Explanation The FPGA image on the specified card is updated. The new FPGA image will not be operational until the card is reloaded. The FPGA image upgrade will take effect after the next reload of the card. The card was not reloaded due to negative user response to the reload prompt.
Recommended Action Reload the card in the specified slot. If the card is a processor, reload the router.
Error Message%PLATFORM-4-FPGA_MISMATCH : FPGA image in slot [dec] (name = [chars], hardware version = [dec].[dec], current fpga version = [chars]) does not match the FPGA image in Cisco IOS software (version [dec].[dec]). Approximate time to update the FPGA image is [dec] minutes.
Explanation The version of the FPGA image on the specified card differs from the Cisco IOS software bundled FPGA image version.
Recommended Action Update the FPGA image by entering the upgrade fpga all command.
Error Message%PLATFORM-4-FPGA_VER_INVALID : FPGA version information for the hardware in slot [dec] (fpga [dec]) has not been cached.
Explanation An attempt to read the current FPGA version from the cache was unsuccessful. Normally, the FPGA version on the RP and line cards is read from the flash memory device and is cached during the initialization of the card. However, the FPGA image version information for the card in the specified slot has not been cached. This problem is caused by a software message.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-4-HWTIMERALLOCFAIL : Failed to allocate hardware timer for [chars]
Explanation The system software could not allocate a hardware timer from the system hardware timer pool. The feature indicated in the error message is not functional because of this error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-4-IOMEM_MISMATCH : I/O memory size mismatch. Configured size is [dec], allocated size is [dec]
Explanation The allocated I/O memory size does not agree with the configured size.
Recommended Action Reboot the router to reallocate I/O memory.
Error Message%PLATFORM-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from the EEPROM. This problem is probably due to a hardware failure.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM-4-RECALLED_NPE : Old version NPE-175/225 with Rev = [hex] system controller. Contact
upgrades-info@cisco.com for replacementExplanation The NPE board has been recalled because of errors in the system controller chip.
Recommended Action Replace the NPE-175/225 board.
Error Message%PLATFORM-4-SAMI_HM_UNKNOWN : Unknown/Unexpected message rcvd with opcode = [int], received from [chars]
Explanation Unknown/unexpected message received.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-4-SAMI_PKT : [chars]: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation Unknown/unexpected message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM-4-WARN_EXT_INT : Potential loss of external error interrupt, intreg = [hex]: [chars]
Explanation The FPGA initialization has masked external error interrupts.
Recommended Action Verify that the OIR for the card still functions.
Error Message%PLATFORM-5-ECC_MSG : A corrected single bit error has occurred in [chars] at location [hex].
Explanation A single bit error has occurred in memory and is corrected. The system will operate normally, and the operation can continue without interruption. However, if the error happens very frequently at the same location, it may be a hardware defect.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show platform interrupt, show version and show run output commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-6-ENERGYWISE : Power level transition from [chars] to [chars] on [chars] slot [chars] [chars]
Explanation This message indicates the result of power level transition attempted on the given card. The transition is either successful or unsuccessful
Recommended Action This is an informational message only. Enter show platform hw-module-power command to display additional information.
Error Message%PLATFORM-6-FPGAUPDSKIP : Slot [dec] [chars] update skipped.
Explanation The system skipped the FPGA update even though the current FPGA version is potentially incompatible.
Recommended Action Check the field alerts and other related documents for similar problems. Update the FPGA, if needed.
Error Message%PLATFORM-6-FPGAUPDSUCCESS : Slot [dec] [chars] successfully updated from version [dec].[dec] to [dec].[dec].
Explanation The FPGA update is successful.
Recommended Action No action is required.
Error Message%PLATFORM-6-HASTATUS : RP switchover, %s
Explanation RP switchover events received by platform code.
Recommended Action No action is required.
Error Message%PLATFORM-6-HASTATUS_DETAIL : RP switchover, %s (count %u)
Explanation RP switchover events received by platform code.
Recommended Action No action is required.
Error Message%PLATFORM-6-MODULE_INSERTED : %s module inserted in slot %d %s
Explanation The system supports two types of modules a 10GE X2 and a TwinGig Converter Module in slot 1/2. The module is inserted
Recommended Action No action is required.
Error Message%PLATFORM-6-MODULE_REMOVED : %s module removed in slot %d %s
Explanation The system supports two types of modules a 10GE X2 and a TwinGig Converter Module in slot 1/2. The module is removed
Recommended Action No action is required.
Error Message%PLATFORM-6-NONESSINITFAIL : Initialization failed for [chars]
Explanation The router tried to initialize the indicated component of the software; however this failed. The component that was to be initialized is non-essential and therefore the router can continue.
Recommended Action No action is required. The router will function normally. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-6-RF_PROG_SUCCESS : RF state %s
Explanation A marker to illuminate when the standby reaches a terminal state.
Recommended Action No action is required.
Error Message%PLATFORM-6-USB_CLOSE : [chars] USB Port [dec], pipe [dec]
Explanation The USB hardware could not be closed properly during the shutdown process.
Recommended Action Ensure that the USB drive is firmly inserted in the USB port indicated in the message.
Error Message%PLATFORM-6-USB_SHUTDOWN : [chars] USB Port [dec], status is [dec]
Explanation The USB hardware could not be shutdown properly during the shutdown process.
Recommended Action Ensure that the USB drive is firmly inserted in the USB port indicated in the message.
Error Message%PLATFORM_CAPABILITY-4-CALL : Fatal Initialization Error - [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAPABILITY-4-INIT : Fatal Initialization Error - [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-ASIC_BIST_FAILURE :
C2950 BIST failed for memory [chars] count [dec]
Explanation The built-in memory test on the internal chip memories failed during the Power-On Self Test. This error could be because of an ASIC defect.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-ASIC_INIT_FAILURE :
Asic driver initialization has failed
Explanation One of the ASIC initialization steps has failed. This error could be a failure in the PCI configuration setup, I2C initialization, built-in self-test on the internal chip memories, or other miscellaneous initialization steps caused by a hardware defect.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-GBP_FAILURE :
Unable to initialize the external packet memory
Explanation An error occurred in the external packet memory initialization during the switch driver initialization. This error could be a defect in the ASIC or in the external SDRAM.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-GBP_INIT_FAILURE :
GBP currently FULL or UNAVAILABLE.Explanation During the switch driver initialization, an error was detected in the external packet memory. This error could be a defect in the ASIC or in the external SDRAM.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MEM_COPY_FAILURE :
Invalid copy [dec] for table [chars]
Explanation There was an attempt to read or write an invalid copy of the switch internal memory. This error is recoverable, but should not occur.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MEM_INDEX_FAILURE :
Invalid index [dec] for table [chars]
Explanation There was an attempt to access an invalid index of the switch internal memory. This error is recoverable, but should not occur.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MEM_INIT_FAILURE :
The switch memory resources could not be allocated for [chars], initialization failedExplanation Driver-related memory resources could not be allocated during the switch driver initialization. This error could be caused by a hardware defect.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MEM_READ_FAILURE :
Read memory failed for memory [chars] at index [dec]
Explanation An attempt to read a valid location in the internal chip memory has failed. This error could be caused by a hardware defect.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MEM_WRITE_FAILURE :
Write memory failed for memory [chars] at index [dec]
Explanation An attempt to write to a location in the internal chip memory has failed. This error might be caused by writing to an invalid memory location or by a defect in the hardware.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-MIIM_OP_FAILURE :
Unable to read PHY register at addr [hex] for phy id [hex]
Explanation There was a failure to read from or write to a PHY register on the switch. This error could be caused by a defect in the MII/GMII interface of the switch.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-PCI_FIND_FAILURE :
The number of asics expected were [dec], PCI bus scan found [dec]
Explanation During the switch driver initialization, an incorrect number of ASICs was found on the PCI bus or no ASIC with a correct PCI value was found. This error could be caused by a system PCI bus defect or by an incompatible software version running on the switch.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-PCI_INIT_FAILURE :
The PCI address space initialization failedExplanation During the switch driver initialization, the PCI address space for the ASIC could not be initialized. This error could be a system PCI-bus-related issue.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-PCI_TEST_FAILURE :
PCI address space test failed,Wrote [hex], read [hex], re-read [hex]
Explanation During the power-on self test, it was found that the PCI address space for the ASIC had not been mapped correctly. This error could be a system PCI-bus-related issue.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-REG_READ_FAILURE : Register read failed for register [chars] in [chars]
Explanation An attempt to read a valid location in the internal chip register has failed. This condition could be caused by a hardware defect.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-REG_WRITE_FAILURE : Register write failed for register [chars] in [chars]
Explanation An attempt to write to a location in the internal chip register has failed. This condition might be caused by a write operation that was made to an invalid register location or a defect in the hardware.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-SCHAN_OP_FAILURE :
S-channel operation timeout for opcode [chars]
Explanation There has been a failure to read or write to an ASIC register or to a memory location because of an ASIC internal bus failure.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-SCHAN_READ_REG_FAILURE :
S-channel operation read register failure at addr [hex]
Explanation There has been a failure to read an ASIC register. The error might be caused by an invalid register address or by an internal bus failure.
Recommended Action If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CAT2950-3-SYSTEM_INFO_FAILURE :
The board information could not be read correctly,initialization failedExplanation During switch driver initialization, there was a failure to read the system board information. This error could be caused by a hardware problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PLATFORM_CAT3550 Messages
The following are low-level platform messages.
Error Message%PLATFORM_CAT3550-1-CRASHED : [chars]
Explanation The system is attempting to display the previous crash message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PLATFORM_CATALYST2940 Messages
The following are Calhoun uplink-related messages.
Error Message%PLATFORM_CATALYST2940-3-C2940_UPLINK_SELECT : [chars] is selected as uplink port
Explanation A single uplink has been selected at system startup. Other uplink ports remain inactive (shutdown).
Recommended Action No action is required.
PLATFORM_CATALYST2950 Messages
The following are low-level platform messages.
Error Message%PLATFORM_CATALYST2950-1-CRASHED : [chars]
Explanation The system is attempting to display further information regarding the crash that just occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CATALYST2955-3-PORT_NOT_OPERATING : [chars] [chars] [chars] [chars]
Explanation The port is not operating. The self-test that is performed at system startup has failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_CIGESM-2-OVER_THERMAL_THRESH2 : The Switch Module has exceeded its second thermal threshold
Explanation When the temperature of the second thermal threshold (85C) is exceeded, the switch module is operating in an environment that can cause damage to the hardware. The chassis will shutdown the switch module shortly after this condition is detected.
Error Message%PLATFORM_CIGESM-3-IMAGEUPGRADEFAIL : PIC microcontroller image upgrade failed.
Explanation Error msg. Problem with PIC microcontroller image upgrade. After upgrade, new PIC microcontroller image failed the sanity check or the readback verification. Restart the PIC microcontroller image upgrade again.
Error Message%PLATFORM_CIGESM-4-LOCKOUT_ILLEGALREQUEST : Illegal Request from Management Module in Protected Mode: %s. Request turned down.
Explanation This message means that the chassis management module has requested a configuration change on the switch, when the switch is operating in protected mode. The request will not be granted. The request was either an IP Address change, an admin state control on external Ethernet ports, a revert to manufacturing defaults, or external management of the switch.
Recommended Action No action is required.
Error Message%PLATFORM_CIGESM-4-MM_NOLOCKOUT : Switch is no longer running in Protected Mode
Explanation This message means that the switch is not configured for protected mode and that the chassis management module has control over the switch.
Recommended Action No action is required.
Error Message%PLATFORM_CIGESM-4-MM_NOLOCKOUTSUPPORT : Management Module no longer supports Protected Mode : Management Module still remains in Protected Mode
Explanation This message means that when the chassis management module changes to a new primary management module, the new primary management module does not detect support for protected mode on the switch.
Recommended Action No action is required.
Error Message%PLATFORM_CIGESM-4-OVER_THERMAL_THRESH1 : The Switch Module has exceeded its first thermal threshold
Explanation When the temperature of the first thermal threshold is exceeded, the switch module will still operate normally. Temperature inside the chassis should be monitored. The first thermal threshold is 75C.
Error Message%PLATFORM_CIGESM-4-SWITCHRESETPIC : Keepalive ECHO failed, PIC has been reset.
Explanation Warning msg. Three consecutive keep alive msgs were not responded to by PIC microcontroller. PIC was reset to re-establish communication.
Error Message%PLATFORM_CIGESM-4-UNDR_THERMAL_THRESH2 : The Switch Module has recovered from second thermal threshold
Explanation The switch module has detected that it no longer exceeds the second thermal threshold of 85C. It may still be over first thermal threshold of 75C, so monitoring of chassis temperature is still recommended.
Error Message%PLATFORM_CIGESM-5-DISABLE_EXTERN : Request from Management Module: disable all external ethernet portsgi0/17 - 20.
Explanation Information msg only. Switch received a request from the management module to shut down the external ports gi0/17 - 20.
Error Message%PLATFORM_CIGESM-5-DISABLE_EXTERNMGMT : Request from Management Module: Switch can be managed from mgmt module portsonly gi0/15 - 16.
Explanation Information msg only. Switch received a request from the management module that cannot receive management traffic from the external ports gi0-17 - 20. This includes HTTP and IP.
Error Message%PLATFORM_CIGESM-5-ENABLE_EXTERN : Request from Management Module: enable external ethernet ports gi0/17 - 20.
Explanation Switch received a request from the management module to re-enable (or admin up) the external ports gi0/17 - 20
Error Message%PLATFORM_CIGESM-5-ENABLE_EXTERNMGMT : Request from Management Module: Switch can be managed from all ports.
Explanation Information msg only. Switch received a request from the management module that it can receive management traffic from the external ports gi0-17 - 20. This includes HTTP and IP.
Error Message%PLATFORM_CIGESM-5-MM_NEITHER : The Switch Module cannot detect either Managment Module as active
Explanation Readings from the MidPlane cannot detect either management module to be active primary. This will not impact the switches to operate as expected.
Error Message%PLATFORM_CIGESM-5-MM_SWITCHOVER : The active Managment Module is now in slot %d
Explanation Information msg only. The active Management Module has switched over.
Error Message%PLATFORM_CIGESM-5-UNDR_THERMAL_THRESH1 : The Switch Module has recovered from first thermal threshold
Explanation The switch module has detected that it no longer exceeds the first thermal threshold of 75C.
Error Message%PLATFORM_CIGESM-6-ACQUIRE_IP : Request from Management Module: acquire IP Address from EEPROM
Explanation Information msg only. Switch received a request from the management module to read the IP Address, Netmask, and default IP gateway from the EEPROM. These are values set by user on IBM web browser.
Error Message%PLATFORM_CIGESM-6-PICREADFAIL : Read request to PIC microcontroller failed.
Explanation Informational msg only. Read failure could be caused by PIC to busy to respond and the read request timed out, or a checksum error in the communication.
Error Message%PLATFORM_CIGESM-6-PICWRITEFAIL : Write request to PIC microcontroller failed.
Explanation Informational msg only. Write failure could be caused by PIC too busy to respond and the write request timed out, or a checksum error in the communcation.
Error Message%PLATFORM_CIGESM-6-RESETMGMT1 : Request from Management Module received: reset ethernet port Gi0/15.
Explanation Information msg only. Switch received a request from the management module to reset the ethernet port to connected to management module in mgmt slot1 (Gi0/15).
Error Message%PLATFORM_CIGESM-6-RESETMGMT2 : Request from Management Module received: reset ethernet port Gi0/16.
Explanation Information msg only. Switch received a request from the management module to reset the ethernet port to connected to management module in mgmt slot2 (Gi0/16).
Error Message%PLATFORM_DIAG-3-FLASH_FULL : %s %d: Unable to perform diagnostic testing because there is insufficient free space in the file system to store test results. Need a minimum of %d bytes.
Explanation Diagnostic tests that reload the switch upon test completion store test results in the file system.
Recommended Action Free up space in the file system.
Error Message%PLATFORM_DIAG-3-MONITOR_ERROR : %s %d: Health monitor threshold of %d consecutive failures for %s has been reached.
Explanation The switch is not operating properly because an online diagnostic health monitor test has reached the failure threshold.
Recommended Action Reset the switch. If this does not resolve the problem, then 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PLATFORM_DIAG-6-TEST : %s %d: Stored test results from before reload:
Explanation This is an informational message stating that the following online diagnostic results are from before the switch was reloaded. This type of testing requires that the switch be reloaded after the tests complete. The test results are reported after the switch reloads.
Recommended Action No action is required. This is an informational message and the system is working properly.
Error Message%PLATFORM_EEM-3-POLICY_ACCESS_FAILED : Failed to access %s: %s
Explanation There was a problem accessing the event manager policy file.
Recommended Action Check the permissions of the file. Manually copy the file to the member switches using copy command.
Error Message%PLATFORM_EEM-3-POLICY_SYNC_FAILED : Failed to sync policy file %s with member switch %d
Explanation There was a problem sending the event manager policy file to the specified switch.
Recommended Action Manually copy the file to the member switch using copy command.
Error Message%PLATFORM_EEM-3-POLICY_TOO_BIG : Size of policy file %s (%d bytes) exceeds supported size %d bytes
Explanation The policy file size exceeds the supported size and will not be available on the member switches
Recommended Action Manually copy the file to the member switches using copy command.
Error Message%PLATFORM_ENV-1-DUAL_PWR : Faulty internal power supply %s detected
Explanation Faulty internal power supply detected in two power supplies supported platforms
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT : Alarm asserted: %s
Explanation Error condition detected on external alarm contact
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR : Alarm cleared: %s
Explanation Error condition cleared on external alarm contact.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-FAN : Faulty fan%s detected
Explanation Faulty fan detected.
Recommended Action If the fault persists, replace the fan.
Error Message%PLATFORM_ENV-1-FAN_NOT_PRESENT : Fan is not present
Explanation Fan is not present.
Recommended Action If it is a removable fan, insert it back into the switch. If fault persists after insertion, replace the fan.
Error Message%PLATFORM_ENV-1-FRU_PS_ACCESS : %s
Explanation Switch failed to access power supply due to communication problem.
Recommended Action This problem could be transient. If fault persists, replace the power supply.
Error Message%PLATFORM_ENV-1-FRU_PS_FAN_FAILED : Faulty PS%s fan detected
Explanation Power supply fan failure detected.
Recommended Action Replace the faulty fan.
Error Message%PLATFORM_ENV-1-FRU_PS_FAN_OK : PS%s fan ok
Explanation Power supply fan working ok.
Recommended Action No action is required..
Error Message%PLATFORM_ENV-1-FRU_PS_SIGNAL_FAULTY : %s signal on power supply %d is faulty
Explanation The specified signal of power supply is faulty.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information..
Error Message%PLATFORM_ENV-1-FRU_PS_SIGNAL_OK : %s signal on power supply %d is restored
Explanation The specified signal of power supply has been restored.
Recommended Action No action is required..
Error Message%PLATFORM_ENV-1-PLATFORM_FAN_CRITICAL : %s
Explanation Faulty fans(FRU fan or PS fan) detected.
Recommended Action Replace the faulty fan(s) and then turn on the system.
Error Message%PLATFORM_ENV-1-PS_NONPOE : Internal Power supply not adequate for inline power
Explanation Internal Power supply not adequate for inline power.
Recommended Action Procure a power supply that can provide adequateinline power.
Error Message%PLATFORM_ENV-1-PWR : Faulty %s power supply detected
Explanation Faulty internal or redundant power supply detected.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-PWR_RPS : Redundant power supply faulty or in standby mode
Explanation Redundant power supply is either faulty or it is in standby mode
Recommended Action Move the redundant power supply out of standby mode and check the cables. Refer to the RPS User's Guide for the steps. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_ACCESS : %s
Explanation RPS communication error detected
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_FAN_FAILED : %s
Explanation RPS fan failure detected
Recommended Action Disconnect any switches connected to the RPS and replace the fan immediately
Error Message%PLATFORM_ENV-1-RPS_OVER_CURRENT : %s
Explanation RPS overcurrent condition detected
Recommended Action Unplug the switches that are being backed off
Error Message%PLATFORM_ENV-1-RPS_PS_FAN_FAILED : RPS power supply %s fan failure detected
Explanation RPS power supply fan failure has been detected
Recommended Action Disconnect any switches connected to the RPS and replace the power supply immediately
Error Message%PLATFORM_ENV-1-RPS_PS_MISMATCH : %s
Explanation Power supplies inserted in RPS are incompatible
Recommended Action Remove either one of the power supplies or insert compatible power supplies.
Error Message%PLATFORM_ENV-1-RPS_PS_SIGNAL_FAULTY : %s signal on RPS power supply %s is faulty
Explanation The specified power supply of RPS has faulty signal
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL : RPS power supply %s temperature has reached critical threshold
Explanation The power supply inside RPS has reached the critical threshold. RPS cannot function normally
Recommended Action The external temperature is very high. Reduce the temperature in the room immediately
Error Message%PLATFORM_ENV-1-RPS_STANDBY : %s
Explanation Faulty RPS detected
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_SYS_POWER_BAD : %s
Explanation RPS system power changed state to bad. It may not provide backup
Recommended Action Check the power supplies in RPS. If fault persists, replace the power supply
Error Message%PLATFORM_ENV-1-RPS_SYS_POWER_GOOD : %s
Explanation RPS system power changed state to good
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-RPS_THERMAL_CRITICAL : RPS temperature has reached critical threshold
Explanation The temperature sensor value inside RPS has reached the critical threshold. RPS cannot function normally
Recommended Action The external temperature is very high. Reduce the temperature in the room immediately
Error Message%PLATFORM_ENV-1-TEMP : Abnormal temperature detected
Explanation Abnormal temperature detected
Recommended Action Ensure that ambient temperature is not too high in the area. If fault persists, replace the component
Error Message%PLATFORM_ENV-2-RPS_THERMAL_WARNING : RPS temperature has reached warning threshold
Explanation The temperature sensor value inside RPS has reached the warning threshold. RPS can function normally until the temperature reaches the critical threshold
Recommended Action The external temperature is high. Reduce the temperature in the room
Error Message%PLATFORM_ENV-3-ILP_PORT_POST_ERR : %s can't be brought up because it failed POST in Inline Power test.
Explanation An error reported by the Power over Ethernet (PoE) controllerduring POST.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PLATFORM_ENV-3-LOOPBACK_PORT_POST_ERR : %s can't be brought up because it failed POST in Loopback test.
Explanation A loopback error detected during POST.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PLATFORM_ENV-3-RPS_BACKOFF_FAILED : %s
Explanation RPS is continuing to backup switch even though switch issued a command to backoff
Recommended Action No action is required.
Error Message%PLATFORM_ENV-3-RPS_CHANGE_TO_STANDBY : %s
Explanation RPS has changed state to standby. It will no longer backup the switch
Recommended Action No action is required.
Error Message%PLATFORM_ENV-3-RPS_FAULTY_BACKUP : %s
Explanation RPS error condition detected
Recommended Action This problem could be transient. If fault persists, remove and reconnect the switch
Error Message%PLATFORM_ENV-3-RPS_POST_FAILED : %s
Explanation RPS POST failure detected
Recommended Action No action is required.
Error Message%PLATFORM_ENV-3-SMB_HW_FAULT : %s 0x%2x
Explanation Faulty Bus State detected
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-3-SMB_RESET_EXCEEDED : %s 0x%02x
Explanation Faulty device detected
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-5-RPS_THERMAL_NORMAL : RPS temperature is within the acceptable limit
Explanation The temperature sensor value inside RPS is within the normal limit
Recommended Action No action is required.
Error Message%PLATFORM_ENV-6-FRU_PS_OIR : FRU Power Supply %s
Explanation Power Supply inserted or removed
Recommended Action No action is required.
Error Message%PLATFORM_ENV-6-RPS : Redundant Power Supply(RPS) %s
Explanation Redundant Power Supply (RPS) changed state
Recommended Action No action is required.
Error Message%PLATFORM_ENV-6-RPS_INFO : Redundant Power Supply %s
Explanation Related info about RPS
Recommended Action No action is required.
Error Message%PLATFORM_ENV-6-RPS_PS_INSERTED : %s
Explanation Power supply inserted in RPS
Recommended Action No action is required.
Error Message%PLATFORM_ENV-6-RPS_PS_REMOVED : %s
Explanation Power supply removed from RPS
Recommended Action No action is required.
Error Message%PLATFORM_FBM-4-RECOVERED : Fallback bridging recovered from resource crunch.
Explanation Fallback bridging has recovered from an earlier resource allocation failure.
Recommended Action No action is required.
Error Message%PLATFORM_FBM-4-RESOURCE_CRUNCH : Fallback bridging on bridge-group [dec] is experiencing a resource crunch. One or more bridge-groups may not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover.
Explanation Fallback bridging could not be properly configured. The most likely cause of this condition is that the TCAM is full on at least one stack member.
Recommended Action Stop all traffic, enter the clear mac-address-table dynamic command and restore the switch to normal operation.
Error Message%PLATFORM_GE_PHY-2-PAGE_RESET : Platform Phy PAGE Reset Failed
Explanation An attempt to reset the Platform Phy Page to page 0 failed. The PHY behavior is not guaranteed to work properly. Subsequent operations will be setting on wrong pages and can lead to unexpected behavior.
Recommended Action Enter shut and no shut commands to shutdown and restart the interface for which the mode selection is failing. If the problem recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_GE_PHY-2-READ : Read attempt from Platform Phy over SMI Bus failed
Explanation An attempt to read the contents of a register associate with the Gigabit-Ethernet hardware failed. This may result in failure to setup the Gigabit-Ethernet correctly, and may cause a network outage. There may be hardware problem.
Recommended Action Reload the router. If the problem recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_GE_PHY-2-WRITE : Write attempt to Platform Phy over SMI Bus failed
Explanation An attempt to write to the register associate with the Gigabit-Ethernet hardware failed. This may result in failure to setup the Gigabit-Ethernet correctly, and may cause a network outage. There may be hardware problem.
Recommended Action Reload the router. If the problem recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_GE_PHY-3-DUPLEX : Platform Phy Unsupported Duplex settings
Explanation Platform Phy Half Duplex is not supported at 1 Gig Speed, the link is not expected to come up. The Duplex Set fails.
Recommended Action Enter shut and no shut commands on the interface for which the duplex setting are failing. If the problem recurs, attempt to reload the system if there is no traffic on other interfaces.
Error Message%PLATFORM_GE_PHY-3-MODE_SELECT : Mode Select Operation failed on Platform Phy
Explanation The intended mode is not set for the platform phy, the link would not operate in the way intended.
Recommended Action Enter shut and no shut commands on the interface for which the mode selection is failing. If the problem recurs, 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-ADJ : %s
Explanation Platform hulc cef adj related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-ADJ_BACKWALK : %s
Explanation Platform hulc cef Adj Backwalk related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-ERROR : %s
Explanation Platform hulc cef module encountered an error
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-FIB : %s
Explanation Platform hulc cef prefix related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-INTERFACE : %s
Explanation Platform hulc cef interface related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-LB : %s
Explanation Platform hulc cef load balance related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-LB_BACKWALK : %s
Explanation Platform hulc cef LB Backwalk related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-NULL_HANDLE : %s
Explanation Platform hulc cef null handle error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HCEF-3-TABLE : %s
Explanation Platform hulc cef table related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HPLM-3-ERROR : %s
Explanation An internal resource allocation error occurred during label compaction
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_HPLM-6-LABEL_COMPLETE : %s
Explanation VRF label compaction completed successfully
Recommended Action No action is required.
Error Message%PLATFORM_HPLM-6-LABEL_FAILED : %s
Explanation VRF label compaction failed
Recommended Action No action is required.
Error Message%PLATFORM_HPLM-6-LABEL_START : %s
Explanation VRF label compaction started
Recommended Action No action is required.
Error Message%PLATFORM_IPC-3-COMMON : [chars]
Explanation An IPC failure has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_IPC-3-MASTER : [chars]
Explanation A failure has occurred on the active system.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_IPC-3-MAX_LENGTH_EXCEEDED : Len:%d,Max:%d,IPCTotal:%d,TPFFD :%d,CRC :%d,IPCHDR :%d
Explanation IPC application internal error, an attempt to send an IPC message with length exceeding the max limit
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPC-3-SLAVE : [chars]
Explanation A failure has occurred on the backup system.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_IPC-3-STACK_EVENT : [chars]
Explanation An IPC failure has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_IPE-4-SDM_MISMATCH : Template chosen is not suitable for IPe
Explanation The template selected is not optimized for IPe. Choose the appropriate template using the sdm prefer config command
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPV6HOST-2-CANNOT_INIT : Insufficient resources to initialize platform-specific IPv6 host functionality
Explanation The platform-specific part of the IPv6 host support failed to initialize at boot time.
Recommended Action IPv6 cannot be used on this system
Error Message%PLATFORM_IPv6_UCAST-3-ADJ : %s
Explanation Platform ipv6 unicast routing adj related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-ADJ_BACKWALK : %s
Explanation Platform ipv6 unicast routing Adj Backwalk related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-ERROR : %s
Explanation Platform ipv6 unicast routing module encountered an error
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-FIB : %s
Explanation Platform ipv6 unicast routing prefix related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-INTERFACE : %s
Explanation Platform ipv6 unicast routing interface related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-LB : %s
Explanation Platform ipv6 unicast routing load balance related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-LB_BACKWALK : %s
Explanation Platform ipv6 unicast routing LB Backwalk related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-ND : %s
Explanation Platform ipv6 unicast routing neighbor discovery related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-PROXY : %s
Explanation Platform ipv6 unicast routing ND-Proxy related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-RPC : %s
Explanation Platform ipv6 unicast routing RPC related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-TABLE : %s
Explanation Platform ipv6 unicast routing table related error occured
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-6-PREFIX : %s
Explanation A more specific prefix could not be programmed into TCAM and is covered by a less specific prefix. This could be a temporary condition. The show platform ipv6 unicast retry route command lists failed prefixes at a given time.
Recommended Action No action is required.
Error Message%PLATFORM_LICENSING-3-EULA_NOT_ACCEPTED : ********************************************************* WARNING : License is not yet activated. Please configure appropriate 'license feature ' command and accept the EULA to activate the license. *********************************************************
Explanation EULA is not accepted.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_N2 Messages
The following are SAMI Platform crypto messages.
Error Message%PLATFORM_N2-3-INIT_FAIL : [chars]
Explanation Platform error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PLATFORM_N2-3-NOMEMORY : Could not allocate memory for [chars] [int]
Explanation Unknown or unexpected message received.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
PLATFORM_PBR Messages
The following are policy-based routing messages.
Error Message%PLATFORM_PBR-2-NO_RMAP : Cannot create PBR data structures for route-map [chars]
Explanation The PBR manager could not allocate the data structures that are required to describe a route map that is being used for policy routing. This condition is probably caused by a lack of available memory.
Recommended Action Use a less-complicated configuration that requires less memory.
Error Message%PLATFORM_PBR-3-INSTALL_FAIL : Policy route-map [chars] not installed in hardware
Explanation The PBR manager was unable to install the complete route map in the hardware. The route map will be applied in the Cisco IOS software. The packets will now be forwarded by the CPU.
Recommended Action Reconfigure the route map to use a simpler configuration. Use the same route map on multiple interfaces, if possible.
Error Message%PLATFORM_PBR-3-MERGE_FAIL : [chars] ACL merge error [dec] on route-map [chars]
Explanation The PBR manager could not merge the configured route map into a form that was suitable to be loaded into the hardware. The most likely cause of this condition is an ACL that was too large or too complex for the system to process.
Recommended Action Attempt to specify a smaller and less-complicated configuration.
Error Message%PLATFORM_PBR-3-NO_LABEL : Cannot allocate label for route-map [chars]
Explanation The PBR manager could not allocate a label for this route map. The hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy-based routing.
Recommended Action Use a less-complicated configuration that allows label sharing. Use the same route maps on multiple interfaces, if possible.
Error Message%PLATFORM_PBR-3-NO_LABEL_DETERMINATION : Cannot determine current label usage
Explanation The policy manager could not create a list of current policy usage. A policy usage list determines how many more policies the interfaces can support. If current policy usage is unknown, the platform will not allow any more policies.
Recommended Action The platform might not be able to create a policy usage list because system memory is low. Free up resources so that the policy manager can determine current policy usage.
Error Message%PLATFORM_PBR-3-UNSUPPORTED_RMAP : Route-map [chars] not supported for Policy-Based Routing
Explanation The route map that is attached to an interface for policy routing contains an action that is not supported on this platform. This condition indicates a hardware limitation.
Recommended Action Reconfigure the route map. Use only entries that are specified by the permit command, and actions that are supported by the set ip next-hop command, in the route map.
PLATFORM_PM Messages
The following are platform-specific Port Manager messages.
Error Message%PLATFORM_PBR-4-CPU_SUPPORTED_ACTION : Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU
Explanation The route map that is attached to an interface for policy routing contains an action that is not supported in hardware, since it contains actions related to the set interface, set ip default next-hop, set default interface or set ip df commands. Packets will now be forwarded by the CPU in order to support the route map.
Recommended Action Reconfigure the route map. Apply conditions related to the set ip next-hop command in the route map if possible.
Error Message%PLATFORM_PBR-4-RETRY_INSTALL : Route-map [chars] installed in hardware upon retry
Explanation The PBR manager was able to fit the complete configuration into the hardware. One or more route maps had previously not been loaded because of a lack of space.
Recommended Action No action is required.
Error Message%PLATFORM_PBR-4-SDM_MISMATCH : [chars] requires sdm template routing
Explanation In order to support the specified feature, SDM template routing must be.
Recommended Action Modify the Switch Database Management template to enable the switch to support the routing template. Enter the sdm prefer routing command in user configuration mode, then reload the switch by entering the reload command in privileged EXEC mode.
Error Message%PLATFORM_PM-3-HOSTACCESSFAIL : Unable to configure hardware to %s host access on %s. Port may not behave as expected.
Explanation The system was unable to configure the hardware to set the requested host access policy. There may be insufficient TCAM resources available.
Recommended Action Stop all traffic, issue clear mac-address-table dynamic and remove and re-issue the command that failed.
Error Message%PLATFORM_PM-3-IFCOUNTERROR : Unit number [dec] of interface [chars] is more than max allowed value of [dec]
Explanation The system supports a limited number of interfaces for each interface type. The user has created more interfaces than can be supported.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_PM-3-INTVLANINUSE : internal vlan-id [dec] allocated for interface [chars] is still in use
Explanation An internal VLAN ID that was allocated for an interface is still in use.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_PM-3-NOINTVLAN : internal vlan of interface [chars] is not active for vlan-id [dec]
Explanation Internal VLAN data is not active for the specified VLAN ID.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PLATFORM_RPC Messages
The following are platform RPC messages.
Error Message%PLATFORM_RPC-0-RESOURCE_CRASH : [chars]
Explanation The system is unable to allocate memory for the RPC.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-BAD_CLASS : Bad Class in RPC message: [int]
Explanation A class table is missing an entry for the message class.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-MSG_THROTTLED : RPC Msg Dropped by throttle mechanism: type [int], class [int], max_msg [int], total throttled [int]
Explanation Too large a number of outgoing messages are queued for the message class.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-PERSISTENT_UNABLE_TO_SEND : System is consistently unable to send RPC message: [chars], paks_outstanding: [int]
Explanation A persistent low-level transport failure has occurred while an RPC message was being sent.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-RESP_FAIL : Unexpected response or failure, class [dec], req [dec], switch [dec], error [dec], [chars]
Explanation An unexpected response was received.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-SEND_FAIL : Failed to send RPC message in class [dec], req [dec], [chars]
Explanation Either a local resource error has occurred, or too large a number of outgoing messages are queued for the message class.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_RPC-3-UNABLE_TO_SEND : System is unable to send RPC message: [chars], paks_outstanding: [int]
Explanation An low-level transport failure occurred while an RPC message was being sent.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PLATFORM_SPAN Messages
The following are SPAN platform messages.
Error Message%PLATFORM_SNMP-3-COMMAND_WARNING : The command [%s] should not be configured on a stack of switches
Explanation A command that is supported for standalone switches only was entered on a stack of switches.
Recommended Action Either remove this command from the configuration, save startup configuration and reload the stack, OR, remove all other stack members from the stack.
Error Message%PLATFORM_SPAN-3-FEATUREMISMATCH : %s cannot be supported with the image running on switch-%d
Explanation A feature that was configured on the stack can not be supported on one or more switches in the stack. The feature will work on the switches that support it, but it can not be applied to switches that do not support the feature, and traffic will no longer be monitored in the affected SPAN session on those switches. However, the SPAN destinations ports on affected switches will continue to send out traffic monitored by other switches in the stack.
Recommended Action Upgrade the software running on switches that can not support the feature to a software version that supports the feature.
Error Message%PLATFORM_SPAN-3-PACKET_DROP : Decreased egress SPAN rate.
Explanation When SPAN is enabled with multicast routing or bridge groups, the egress span rates will decrease. All packets going out may not be monitored.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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.
PLATFORM_UCAST Messages
The following are platform Unicast Routing messages.
Error Message%PLATFORM_UCAST-3-ADJ : [chars]
Explanation The platform unicast routing adjacency module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-ARP : [chars]
Explanation The platform unicast routing ARP module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-CEF : [chars]
Explanation The platform unicast routing CEF module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-DYNAMIC : [chars]
Explanation The dynamic address tracking mechanism for the platform has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-ERROR : [chars]
Explanation An internal platform unicast routing error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-FHRP : %s
Explanation Platform unicast routing fhrp module encountered an error
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_UCAST-3-HSRP : [chars]
Explanation The platform unicast routing HSRP module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-INTERFACE : [chars]
Explanation A platform unicast routing interface-related error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-INV_SDM : IP routing configured with invalid SDM template.
Explanation The configured SDM template doesn't support ip routing and may severely degrade the routing performance
Recommended Action Change to an SDM template that supports IP routing.
Error Message%PLATFORM_UCAST-3-LB : [chars]
Explanation The platform unicast routing load-balancing module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-LB_BACKWALK : [chars]
Explanation The platform unicast routing backwalk load-balancing module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-NULL_HANDLE : [chars]
Explanation The platform unicast routing module has received a software object handle with a null value.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-3-RPC : [chars]
Explanation The platform unicast routing RPC module has encountered an error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_UCAST-6-PREFIX : %s
Explanation A more specific prefix could not be programmed into TCAM and is covered by a less specific prefix. This could be a temporary condition. The show platform ip unicast failed route command lists failed prefixes at a given time.
Recommended Action No action is required.
Error Message%PLATFORM_VLAN-3-LOCK_FAIL : Failed to lock vlan-id [dec], associated mapped vlan id value [dec]
Explanation A VLAN lock operation has failed. The most likely cause might be either that the VLAN is already active in the system, or that the VLAN ID is not active.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_VLAN-3-MVID_ERROR : Mapped Vlan ID value [dec] associated with vlan-id [dec] is invalid
Explanation Each active VLAN in the system is associated with a mapped VLAN ID. The specified MVID is not correct or is invalid.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_VLAN-3-UNLOCK_FAIL : Failed to unlock vlan-id [dec], associated mapped vlan id value [dec]
Explanation A VLAN ID could not be unlocked. The most likely cause of this condition is that the VLAN has already been freed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PLATFORM_WCCP-3-NO_LABEL : Cannot allocate WCCP Label
Explanation The WCCP label could not be allocatedThis means that the hardware cannot be programmed to implement WCCP Redirection.
Recommended Action Reduce the number of interfaces configured for WCCP redirection or policy based routing.
Error Message%PLATFORM_WCCP-4-SDM_MISMATCH : WCCP requires sdm template routing
Explanation To support this feature, enable the sdm routing template.
Recommended Action Modify the Switch Database Management (SDM) template to enable the routing template. Use the sdm prefer routing configuration command, and then reload the switch by using the reload privileged EXEC command.
Error Message%PLATFORM-1-CRASH_PCIE : ERROR PCIE-[dec]: Fatal error. ERR_DR=[hex], ERR_CAPT=[hex], ERR_CAPT_R0=[hex], ERR_CAPT_R1=[hex], ERR_CAPT_R2=[hex] ERR_CAPT_R3=[hex]
Explanation The system is crashing because of a hardware error.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-6-EVENT_LOG : [chars]
Explanation The message indi cates the entry from the internal event log at reload on the standby route processor (RP).
Recommended Action No action is required.
Error Message%PLATFORM-3-GEC_NOMAC : Can't allocate MAC address for port-channel interface [int]
Explanation MAC address allocation for the port-channel interface specified in the message failed because the number of supported port-channel interfaces exceeded the maximum limit.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-6-HASTATUS : RP switchover, [chars]
Explanation The platform code received the route processor (RP) switchover events.
Recommended Action No action is required.
Error Message%PLATFORM-6-HASTATUS_DETAIL : RP switchover, [chars] (count [int])
Explanation The platform code received the route processor (RP) switchover events.
Recommended Action No action is required.
Error Message%PLATFORM-4-HASTATUS_WARN : RP HA status warning, [chars])
Explanation The standby route processor (RP) reports a peer not present event.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-6-MODULE_INSERTED : [chars] module inserted in slot [dec] [chars]
Explanation The system supports two types of modules, a 10-Giga Ethernet X2 and a 2 1-GE SFP module in slot 1/2. One of the two modules was inserted.
Recommended Action No action is required.
Error Message%PLATFORM-6-MODULE_REMOVED : [chars] module removed in slot [dec] [chars]
Explanation The module indiacted in the message was removed from the slot specified in the message.
Recommended Action No action is required.
Error Message%PLATFORM-3-NO_BASEMAC : Can't retrieve base MAC address
Explanation The base MAC address determination failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NOMAC_INTF : Failed to allocate MAC address for interface [chars]
Explanation MAC address allocation for the logical interface specified in the message failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NVRAM_OPEN_FAIL : Failed to open nvram - [chars].
Explanation The system could not open the NVRAM device.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NVRAM_READ_FAIL : Failed to read nvram - [chars].
Explanation The system could not read the NVRAM contents.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-3-NVRAM_WRITE_FAIL : Failed to write nvram - [chars].
Explanation The system could not write into the NVRAM device.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-4-RELOAD_STANDBY : [chars] reload requested by [chars]. Reason [chars]
Explanation An unexpected configuration or mismatch of states between the active and standby route processors (RPs) occurred.
Recommended Action Reload the standby RP to synchronize the configuration or states.
Error Message%PLATFORM-6-RF_PROG_SUCCESS : RF state [chars]
Explanation A marker that indicates the status of the standby route processor (RP) indicates the RP has reached the terminal state.
Recommended Action No action is required.
Error Message%PLATFORM-6-SB_INIT_DELAY : RF progression will be suspended due to standby initialization delay configuration setting. Standby initialization will resume after [int] seconds
Explanation The redundancy facility (RF) progression is delayed. Bulk synchronization and other progression events will occur only when the system reaches the configured delay value.
Recommended Action No action is required.
Error Message%PLATFORM-6-SB_INIT_DELAY_END : RF progression delay timer expired. Standby initialization will now continue
Explanation The redundancy facility (RF) progression is continuing because the configured delay has expired.
Recommended Action No action is required.
Error Message%PLATFORM-4-STATS_COLLECTION : Reducing statistics collection interval for SPA ([chars]) will impact the RP control plane activity
Explanation By default, the MIB statistics for the hardware counters are sent to the route processor (RP) every ten seconds. Changing the timer by using the command line interface (CLI) to send the statistics more often will increase the RP CPU utilization and result in sending more inter process communication (IPC) messages.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-DUAL_PWR : Faulty internal power supply [chars] detected
Explanation A faulty internal power supply was detected in one of the two power supplies on the switch.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-3-ENV_INIT_FAIL : Environmental Driver Initialization Error
Explanation The environmental driver did not initialize. The switch cannot determine the system, voltage rail, thermal, and fan status.
Recommended Action If the message appears again, upgrade the firmware or replace the driver.
Error Message%PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT : Alarm asserted: [chars]
Explanation The error condition was detected on the external alarm contact.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR : Alarm cleared: [chars]
Explanation An error condition was rectified on the external alarm contact.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-FAN : Faulty fan[chars] detected
Explanation A faulty fan was detected.
Recommended Action If the message appears again, replace the fan immediately.
Error Message%PLATFORM_ENV-1-FAN_NOT_PRESENT : Fan is not present
Explanation The fan is not in the switch.
Recommended Action If the fan is removable, remove and replace it into the switch. If the problem persists after insertion, replace the fan.
Error Message%PLATFORM_ENV-1-FRU_PS_ACCESS : [chars]
Explanation The switch failed to access the power supply due to a communication problem.
Recommended Action This problem could be transient. If the fault persists, replace the power supply.
Error Message%PLATFORM_ENV-1-FRU_PS_FAN_FAILED : Faulty PS[chars] fan detected
Explanation The specified power supply fan failed.
Recommended Action Replace the faulty fan.
Error Message%PLATFORM_ENV-6-FRU_PS_OIR : FRU Power Supply [chars]
Explanation The power supply cable was inserted or removed.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-FRU_PS_SIGNAL_FAULTY : [chars] signal on power supply [dec] is faulty
Explanation The specified power supply signal is faulty.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-FRU_PS_SIGNAL_OK : [chars] signal on power supply [dec] is restored
Explanation The specified power supply signal has been restored.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-3-GLUE_INIT_FAIL : Hardware Tracking Driver Initialization Error
Explanation The hardware tracking (control FPGA) driver failed to initialize. The switch cannot determine the field-replaceable units (FRUs) power supply, small form-factor pluggable (SFP) module, field-programmable gate array (FPGA), stateful packet inspection (SPI), Joint Test Action Group (JTAG), and alarm state changes.
Recommended Action If the error persists, replace the component and upgrade the control FPGA.
Error Message%PLATFORM_ENV-3-GLUE_INTR_NOT_FUNCTIONING : Hardware Tracking Driver: State Change Detection not functioning
Explanation The hardware tracking (control FPGA) driver no longer detects state changes. The switch cannot determine the field-replaceable units (FRU) power supply, small form-factor pluggable (SFP) module, field-programmable gate array (FPGA), stateful packet inspection (SPI), Joint Test Action Group (JTAG), and alarm state changes.
Recommended Action If the message appears again, upgrade the control FPGA. If the message appears even after upgrading the control FPGA, 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-3-MCU_I2C_READ_ERROR: I2C read failed in MCU and attached devices (e.g. Temperature Sensor) can't be read.
Explanation The system could not read the Multipoint Control Unit (MCU) Inter-Integrated Circuit (I2C) and the temperature sensor.
Recommended Action Ensure that the ambient temperature is not too high in the area. If the error persists, replace the component.
Error Message%PLATFORM_ENV-1-PWR : Internal power supply not supplying power
Explanation There is no power supply from the internal power supply because either the cable is removed, or the power supply is faulty.
Recommended Action Check the power supply cables and power source. 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-PWR_RPS : Redundant power supply faulty or in standby mode
Explanation The redundant power supply (RPS) is either faulty, or is in standby mode.
Recommended Action Move the redundant power supply out of standby mode, and check the cables.
Error Message%PLATFORM_ENV-6-RPS : Redundant Power Supply(RPS) [chars]
Explanation The redundant power supply (RPS) changed state.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-RPS_ACCESS : [chars]
Explanation A redundant power supply (RPS) communication error was detected.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_FAN_FAILED : [chars]
Explanation Redundant power system (RPS) fan failure was detected.
Recommended Action Disconnect any switches connected to the RPS, and replace the fan immediately
Error Message%PLATFORM_ENV-1-RPS_OVER_CURRENT : [chars]
Explanation Redundant power supply (RPS) excessive power condition was detected.
Recommended Action Unplug the switches that are being backed off.
Error Message%PLATFORM_ENV-3-RPS_POST_FAILED : [chars]
Explanation The redundant power supply (RPS) power-on self-test (POST) failure was detected.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-RPS_PS_FAN_FAILED : RPS power supply [chars] fan failure detected
Explanation The redundant power supply (RPS) power supply fan failed.
Recommended Action Disconnect any switch that is connected to the RPS, and replace the power supply immediately.
Error Message%PLATFORM_ENV-6-RPS_PS_INSERTED : [chars]
Explanation A power supply cable was inserted in the redundant power supply (RPS).
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_PS_MISMATCH : [chars]
Explanation The power supplies inserted in the redundant power supply (RPS) are incompatible.
Recommended Action Remove either of the power supplies, or insert a compatible power supply.
Error Message%PLATFORM_ENV-6-RPS_PS_REMOVED : [chars]
Explanation The power supply was removed from the redundant power supply (RPS).
Recommended Action No action is required.
Error Message%PLATFORM_ENV-1-RPS_PS_SIGNAL_FAULTY : [chars] signal on RPS power supply [chars] is faulty
Explanation The specified power supply of redundant power supply (RPS) has a faulty signal.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL : RPS power supply [chars] temperature has reached critical threshold
Explanation The temperature of the power supply inside the redundant power supply (RPS) has reached the critical threshold. The RPS cannot function normally
Recommended Action Reduce the temperature in the room immediately.
Error Message%PLATFORM_ENV-1-RPS_STANDBY : [chars]
Explanation A faulty redundant power supply (RPS) was detected.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_SYS_POWER_BAD : [chars]
Explanation The state of the redundant power supply (RPS) system power has changed to bad. A backup may not be available.
Recommended Action Check the power supplies in the RPS. If the error persists, replace the power supply.
Error Message%PLATFORM_ENV-1-RPS_SYS_POWER_GOOD : [chars]
Explanation The state of the redundant power supply (RPS) system power has changed to good.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-RPS_THERMAL_CRITICAL : RPS temperature has reached critical threshold
Explanation The temperature sensor value inside the redundant power supply (RPS) has reached the critical threshold. The RPS cannot function normally.
Recommended Action Reduce the temperature in the room immediately.
Error Message%PLATFORM_ENV-5-RPS_THERMAL_NORMAL : RPS temperature is within the acceptable limit
Explanation The temperature sensor value inside the redundant power supply (RPS) is within the acceptable limit.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-2-RPS_THERMAL_WARNING : RPS temperature has reached warning threshold
Explanation The temperature sensor value inside the redundant power supply (RPS) has reached the warning threshold. The RPS can function normally until the temperature reaches the critical threshold.
Recommended Action Reduce the temperature in the room.
Error Message%PLATFORM_ENV-3-SMB_HW_FAULT : [chars] [hex]
Explanation A faulty bus state was detected.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-3-SMB_RESET_EXCEEDED : [chars] [hex]
Explanation A faulty device was detected.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_ENV-1-TEMP : Abnormal temperature detected
Explanation The temperature is abnormally high.
Recommended Action Ensure that the ambient temperature is not too high in the area. If the fault persists, replace the component.
Error Message%PLATFORM_ENV-1-THERMAL_CRITICAL : Temperature has reached critical threshold
Explanation The temperature sensor value inside the switch has reached the critical threshold. The switch cannot function normally.
Recommended Action Reduce the temperature in the room immediately.
Error Message%PLATFORM_ENV-5-THERMAL_NORMAL : Temperature is within the acceptable limit
Explanation The temperature sensor value inside the switch is within the acceptable limit.
Recommended Action No action is required.
Error Message%PLATFORM_ENV-3-THERMAL_NOT_FUNCTIONING : Temperature Sensor is not functioning
Explanation An error occurred because the temperature sensor is not functioning.
Recommended Action Ensure that the ambient temperature is not too high in the area. If the error persists, replace the component and update the driver.
Error Message%PLATFORM_ENV-2-THERMAL_WARNING : Temperature has reached warning threshold
Explanation The temperature sensor value inside the switch reached the warning threshold. The switch can function normally until the temperature reaches the critical threshold.
Recommended Action Reduce the temperature in the room.
Error Message%PLATFORM_ENV-3-VOLTAGE_NOT_FUNCTIONING : Voltage Rail Sensors are not functioning
Explanation The voltage rail sensors are not working properly. The switch could not determine the voltage rail behavior.
Recommended Action Ensure that the ambient temperature is not too high in the area surrounding the system. If the fault persists, replace the component and/or update the driver.
Error Message%PLATFORM_IPv6_UCAST-3-LB : [chars]
Explanation An error occurred in the IPv6 unicast routing load balance (LB).
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-LB_BACKWALK : [chars]
Explanation An error occurred in the IPv6 unicast routing load balance (LB) backwalk.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_IPv6_UCAST-3-ND : [chars]
Explanation An error occurred in the IPv6 unicast routing Neighbor Discovery Protocol (NDP).
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-ADJ : [chars]
Explanation An error occurred in the Cisco Express Forwarding adjacency.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-ADJ_BACKWALK : [chars]
Explanation An error occurred in the Cisco Express Forwarding adjacency backwalk.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-ERROR : [chars]
Explanation An error occurred in the Cisco Express Forwarding module.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-FIB : [chars]
Explanation An error occurred in the Cisco Express Forwarding prefix.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-INTERFACE : [chars]
Explanation An error occur in the Cisco Express Forwarerding interface.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-LB : [chars]
Explanation An error occurred in the Cisco Express Forwarding load balancer (LB).
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-LB_BACKWALK : [chars]
Explanation An error occurred in the Cisco Express Forwarding load balancer (LB) backwalk.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-NULL_HANDLE : [chars]
Explanation The Cisco Express Forwarding NULL handle error has occurred.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NCEF-3-TABLE : [chars]
Explanation An error occurred in the Cisco Express Forwarding table.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_NETWORK_CLOCK-4-ERROR : [chars]
Explanation An internal error has occurred.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM_PM-3-HOSTACCESSFAIL : Unable to configure hardware to [chars] host access on [chars]. Port may not behave as expected.
Explanation The system could not configure the hardware to set the requested host access policy. There may be insufficient ternary content addressable memory (TCAM) resources available.
Recommended Action Stop all the traffic, enter the clear mac-address-table dynamic command, and remove and reenter the command that failed.
Error Message%PLATFORM_SCC-1-AUTHENTICATION_FAIL : Chassis authentication failed
Explanation This router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLAT_MP-3-QSTUCK : Inter-CPU handoff ring at [hex] (dest cpu [dec]) stuck.
Explanation The indicated inter-CPU handoff ring is not processing ring entries.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLAT_MP-5-QSTUCK1 : mp=[hex], free=[dec], msg=[dec], ver=[dec], source_cpu=[dec]
Explanation The indicated inter-CPU handoff ring is not processing ring entries.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLAT_MP-5-QSTUCK2 : data[0..2] = [hex]([dec]), [hex]([dec]), [hex]([dec])
Explanation The indicated inter-CPU handoff ring is not processing ring entries.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLIM_QOS-3-IOSXE_RP_PLIM_QOS_FAIL : A software error while configuring the [chars] on slot [dec]
Explanation The system failed to send messages while configuring the per slot quality of software (QoS) parameters in the forwarding plane.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLOGDRP-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLOGDRP-3-MSGDISPATCHERR : Error when receiving TDL error message: %s
Explanation An unexpected condition in which IOS has received an error during TDL message processing from the Proxy Logger.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLOGDRP-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message for the Proxy Logger.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLOGDRP-3-MSGINVALIDFIELD : Invalid errmsg field '%s' received from the Proxy Logger, error %d
Explanation An error message received from the Proxy Logger is missing a required field.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLUGGABLE_TRANSCEIVER Messages
The following are pluggable transceiver module Online Insertion and Removal (OIR) messages.
Error Message%PLUGGABLE_TRANSCEIVER-6-INSERTED : Pluggable transceiver module inserted in [chars]
Explanation The OIR facility has detected a newly-inserted pluggable transceiver module for the interface that is specified in the error message.
Recommended Action No action is required.
Error Message%PLUGGABLE_TRANSCEIVER-6-REMOVED : Pluggable transceiver module removed from [chars]
Explanation The OIR facility has detected the removal of a pluggable transceiver module from the interface that is specified in the error message.
Recommended Action No action is required.
PM Messages
The following are Port Manager messages.
Error Message%PM-1-INCONSISTENT_PORT_STATE : Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface
Explanation The hardware and software port state has become inconsistent.
Recommended Action Enter a shutdown then a no shutdown command for the specified port.
Error Message%PM-2-LOW_SP_MEM : Switch process available memory is less than [dec] bytes
Explanation Available memory for the switch processor has dropped to a low level. A possible cause of this condition is that too many Layer 2 VLANs are configured in the system.
Recommended Action Removed features from the system to reduce memory usage.
Error Message%PM-2-NOMEM : Not enough memory available for %s
Explanation The Port Manager subsystem could not obtain the memory it needed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-2-VLAN_ADD : Failed to add VLAN [dec] - [chars].
Explanation The system has failed to add a VLAN via VTP. The message contains text that can help identify the nature of the problem.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-3-ERR_INCOMP_PORT : [dec]/[dec] is set to inactive because [dec]/[dec] is a [chars] port
Explanation A private host port cannot be configured with a trunk, private promiscuous, and span destination port on the same coil.
Recommended Action Configure the incompatible ports on different coils.
Error Message%PM-3-INTERNALERROR : Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars])
Explanation An internal software error occurred in the Cisco IOS port manager.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-3-INVALID_BRIDGE_PORT : Bridge Port number [dec] is out of range
Explanation The value of bridge portnumber that is passedto an internal Port Manager function is invalid. This indicates an internal software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PM-3-INVALID_SLOT_PORT : Slot/Port [dec]/[dec] is out of range
Explanation The values of slot and/or port that are passedto an internal Port Manager function are invalid. This indicates an internal software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PM-3-NON_SWITCHABLE_PORT : Non-switchable port: [chars].
Explanation The command cannot be performed on the specified port. A switch port configuration command is valid only on ports that support hardware packet switching.
Recommended Action Do not attempt to use switch port commands on standard routed ports. Check the name of the interface you are configuring against the actual hardware.
Error Message%PM-3-PORT_NOT_SHUTDOWN : [chars].
Explanation The command cannot be performed on the specified port. A switch port configuration command is valid only on ports that are shut down.
Recommended Action Do not attempt to use switch port commands until the port has been shut down.
Error Message%PM-4-BAD_APP_ID : an invalid application id (%d) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_APP_REQ : an invalid %s request by the '%s' application was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_CARD_COOKIE : an invalid card cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_CARD_SLOT : an invalid card slot (%d) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_COOKIE : %s was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_HA_ENTRY_EVENT : Invalid Host access entry event ([dec]) is received
Explanation The host access table received an entry event that is not an add, delete, or update event.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-BAD_PORT_COOKIE : an invalid port cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_PORT_NUMBER : an invalid port number (%d) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_VLAN_COOKIE : an invalid vlan cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BAD_VLAN_ID : an invalid vlan id (%d) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-BIT_OUTOFRANGE : bit [dec] is not in the expected range of [dec] to [dec]
Explanation An invalid request has been detected by the Port Manager.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-ERR_DISABLE : %s error detected on %s, putting %s in err-disable state
Explanation This is a defensive measure that will put the interface in err-disable state when it detects a mis-configuration or mis-behavior . A recovery will be attempted after the configured retry time (default 5 minutes).
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-ERR_DISABLE_VP : %s error detected on %s, vlan %d. Putting in err-disable state.
Explanation This is a defensive measure that will put the virtual port (i.e., the port-vlan pair) in err-disable state when it detects a mis-configuration or mis-behavior. If so configured, a recovery will be attempted after the configured retry time (default 5 minutes).
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-ERR_RECOVER : Attempting to recover from %s err-disable state on %s
Explanation This is an attempt to bring the interface back after taking it down to err-disable state
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-ERR_RECOVER_VP : Attempting to recover from %s err-disable state on %s, vlan %d.
Explanation This is an attempt to bring the virtual port back after taking it down toerr-disable state
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-EXT_VLAN_INUSE : VLAN [dec] currently in use by [chars]
Explanation The Port Manager has failed to allocate the VLAN for external use because the VLAN is currently occupied by another feature.
Recommended Action Reconfigure the feature (for example, the routed port) to use another internal VLAN, or request another available VLAN.
Error Message%PM-4-EXT_VLAN_NOTAVAIL : VLAN [dec] not available in Port Manager
Explanation The Port Manager has failed to allocate the requested VLAN. The VLAN is most likely being used as an internal VLAN by other features.
Recommended Action Try a different VLAN on the device.
Error Message%PM-4-INACTIVE : putting [chars] in inactive state because [chars]
Explanation The port manager has been blocked from creating a virtual port for the switch port and VLAN, causing the port to be in an inactive state. The reason for this condition is specified in the error message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-INT_FAILUP : [chars] failed to come up. No internal VLAN available
Explanation The Port Manager has failed to allocate an internal VLAN, consequently, the interface cannot become active (come up).
Recommended Action Remove any extended-range VLANs to free up resources.
Error Message%PM-4-INT_VLAN_NOTAVAIL : Failed to allocate internal VLAN in Port Manager
Explanation The Port Manager has failed to find any available internal VLANs.
Recommended Action Remove some extended range VLANs created by users, or remove some features that require internal VLAN allocation; for example, a routed port.
Error Message%PM-4-INVALID_HOST_ACCESS_ENTRY : Invalid Host access entry type ([dec]) is received
Explanation The host access entry should be one of the configured or dynamic types.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-LIMITS : Virtual port count for [chars] exceeded the recommended limit of [dec]
Explanation The slot exceeds the limit for virtual ports on the switch.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-MPLS_MTU_EC_CFG : MPLS MTU size %d is not supported by one or more ports in channel %s.
Explanation The MPLS MTU size configured on the ethernet channel is larger than the maximum MTU size that can be supported by one or more ports in this channel. As a result, large packets can be dropped.
Recommended Action Reduce the MPLS MTU size, or remove these ports from the channel before increasing the MPLS MTU size.
Error Message%PM-4-MPLS_MTU_PORT_CFG : MPLS MTU size %d is not supported by port %s.
Explanation The MPLS MTU size configured on the port is larger than the maximum MTU size that can be supported by this port. As a result, large packets can be dropped.
Recommended Action Reduce the MPLS MTU size.
Error Message%PM-4-NOSB : No PM subblock found for interface [chars]
Explanation This syslog, along with T/B, is logged for all type of interfaces where PM subblock is absent.The interface types include WAN, loopback and tunnel, which do not have associated PM subblock as per the design.This message helps the PM group to identify the offending application.This message indicates that PM module encounters unusual conditions for diagnose purpose.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-NO_SUBBLOCK : No PM subblock found for [chars]
Explanation The system has failed to find a PM subblock for this interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-PORT_BOUNCED : Port %s was bounced by %s.
Explanation The Port Manager needed to perform a reactivation of a port in the link down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisors. Active ports in the link down state were returned to the link up state by the reactivation event.
Recommended Action No action is required.
Error Message%PM-4-PORT_CONSISTENT : Port %s consistency has been restored, IDB state: %s.
Explanation Port Manager on Standby discovered that port state became consistent again.
Recommended Action No action is required.
Error Message%PM-4-PORT_INCONSISTENT : Port %s is inconsistent: IDB state %s (set %TE ago), link: %s (%TE ago), admin: %s (%TE ago).
Explanation Port Manager on Standby discovered that the port state has been inconsistent for more that 1 second. Inconsistent ports are reactivated on switchover (you will see PORT_BOUNCED message).
Recommended Action No action is required.
Error Message%PM-4-PVLAN_TYPE_CFG_ERR : Failed to set VLAN [dec] to a [chars] VLAN
Explanation The platform failed to set the type for the private VLAN.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-TOO_MANY_APP : application '%s' exceeded registration limit
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM-4-UNKNOWN_HOST_ACCESS : Invalid Host access value ([dec]) is received
Explanation The host access table is being accessed with an invalid host access value.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM-4-VMPS_CFG : Dynamic access VLAN [dec] same as voice vlan on [chars].
Explanation The access VLAN on the VMPS server is set to the same VLAN as the voice VLAN on the port. The access VLAN assignment on the VMPS server should be different from the voice VLAN.
Recommended Action Change the access VLAN assignment on the VMPS server to be different from the voice VLAN. PM_MODEM_HIST Messages
Recommended Action The following are modem history and tracing messages.
Error Message%PM-6-EXT_VLAN_ADDITION : Extended VLAN is not allowed to be configured in VTP CLIENT mode.
Explanation This message will only be seen if you try to configure an extended VLAN while the switch is in VTP client mode. The configuration will fail and will not be written to the runnning configuration file, but otherwise switch performance and features will be unaffected.
Recommended Action This is an informational message only, no further action is required. If you need to configure an extended VLAN, you must configure the switch to leave VTP client mode.
Error Message%PM-SP-4-ERR_DISABLE : [chars] error detected on [chars] putting [chars] in err-disable state,
Explanation The port manager detected a misconfiguration or misbehavior and placed the interface in an error-disabled state. A recovery is attempted after the configured retry time (the default is 5 minites). On PoE switches, this message might appear when a devcie that can be powered by either a PoE switch or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. The first [chars] is the error and the second and third [chars] are the affected interfaces.
Recommended Action On non-PoE switches, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEX command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-SP-4-ERR_RECOVER : Attempting to recover from [chars] err-disable state on [chars].
Explanation The port manager is attempting to bring the interface up after taking it down to the error-disabled state. The first [chars] is the error and the second [chars] is the affected interface.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM3387-3-BAD_CLOCK : Clock is missing at DLL0_RUN
Explanation MAC cannot aquire clocks on the system bus .
Recommended Action Hardware problem. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM3387-3-MISSING_RES : Missing resistors on TDI and TMS
Explanation MAC hardware assembly problem.
Recommended Action Hardware problem. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMB-4-CANTPWROFF : Attempts to power down slot %d failed, card will be disabled.
Explanation A linecard in the system could not be powered down to read the seprom.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMB-4-NOTSUPPORTED : Unsupported/old card at slot %d
Explanation A linecard in the system is either unsupported or an old one.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMIP-3-AAP_UNAVAIL : Authoritative Access Point is unavailable
Explanation The Authoritative Access Point cannot be reached to obtain the subnet map table .
Recommended Action Ensure all the APs have the same information regarding which is an authoritative or regular AP.
Error Message%PMIP-3-AUTH_UNAVAIL : Authentication for [IP_address] unavailable
Explanation Proxy mobile IP failed to obtain the mobile node's authentication information either locally or from a AAA server.
Recommended Action Enure that the correct mobile node information is configured locally or on the AAA server.
Error Message%PMIP-3-HAFA_UNAVAIL : No response from the Mobile IP Agent to our registration requests
Explanation Proxy Mobile IP failed to access the home or foreign agent while trying to register the mobile node.
Recommended Action Enure that the HA or FA is not down or is network inaccessible. Also check that the home agent subnet map information is correct.
Error Message%PMIP-3-REG_AUTH_FAIL : Mobile Node [IP_address] registration failed due to authentication failure
Explanation When a mobile node (MN) moves to a foreign network, the AP will register the MN to its home agent. This message indicates that the registration has failed because the HA or FA failed to authenticate each other or the MN.
Recommended Action Ensure that the correct authentication information is configured on the home agent, the foreign agent, and the access point.
Error Message%PMIP-3-REG_FAIL : Mobile Node [IP_address] mobile ip registration failed
Explanation When a Mobile node (MN) moves to a foreign network, the AP will register the MN to its home agent. This message indicates that the registration has failed.
Recommended Action Ensure that the Mobile IP agents and the Access Point are configured correctly.
Error Message%PMIP-3-REG_FA_FAIL : Mobile Node [IP_address] registration failed due to Foreign Agent denial
Explanation When a mobile node (MN) moves to a foreign network, the AP will register the MN to its home agent. This message indicates that the registration was denied by the foreign agent.
Recommended Action Ensure the correct authentication information is configured on the home agent, the foreign agent, and the access point.
Error Message%PMIP-3-REG_HA_FAIL : Mobile Node [IP_address] registration failed due to Home Agent denial
Explanation When a Mobile node (MN) moves to a foreign network, the AP will register the MN to its home agent. This message indicates that the registration was denied by the home agent.
Recommended Action Ensure that the correct authentication information is configured on the home agent, the foreign agent, and the access point.
Error Message%PMIP-6-HAFA_DOWN : Mobile IP Agent [IP_address] is down or unavailable
Explanation Mobile IP Home or Foreign agent has gone down or is unaccessible to the access point.
Recommended Action Ensure there is at least one home and foreign agent is configured on that subnet and that it is accessible to the Access Point.
Error Message%PMIP-6-REPEATER_STOP : AP is now operating as a repeater, disabling Proxy Mobile IP services
Explanation Proxy Mobile IP does not run on repeaters or workgroup bridges.
Recommended Action No action is required.
Error Message%PMIP-6-START : Proxy Mobile IP services has started
Explanation Proxy Mobile IP service has started.
Recommended Action No action is required.
Error Message%PMIP-6-STOP : Proxy Mobile IP services has stopped
Explanation Proxy Mobile IP service has started.
Recommended Action No action is required.
Error Message%PMOD-3-MSG_ERR : %s
Error Message%PMOD-6-MSG_INF : %s
Explanation Program information
Error Message%PMOD-7-MSG_DBG : %s
Explanation Debug Messages
Error Message%PMSM-4-BADEVENT : Event '[chars]' is invalid for the current state '[chars]': [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that is invalid for the current state.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-INIT : Internal error while initializing state machine '[chars]', state '[chars]': [chars]
Explanation An invalid request was detected by the Port Manager.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-NOTIDLE : Attempted to stop state machine [chars] [chars] but it is not idle
Explanation The Port Manager subsystem attempted to stop a state machine that has pending events.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-STOPPED : Event '[chars]' ignored because the state machine is stopped: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that has already been stopped.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-TOOMANY : Event '[chars]' ignored because there are too many pending events: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that already has the maximum number of events pending.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-UNKNOWN : Event ([dec]) is unknown for the state machine: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an unknown event to a state machine.
Recommended Action 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 might help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_DB_HA-3-CHKPT_INTERNAL : Internal PM DB checkpointing error [[chars]]
Explanation An internal error occurred within the PM DB checkpointing code.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_DB_HA-3-OBJ_MISSING : Missing entry for [chars] [[dec]] for slot [dec] to populate [chars]
Explanation Cannot get the object to be populated with the checkpointed data.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_DB_HA-3-SPE_SM_FAIL : Fail to simulate the [chars] event during the switchover
Explanation Cannot replay the event on the new Active RSC during the switchover.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_ISSU-3-BUFFER : Port Manager ISSU client failed to get buffer for message, error %d
Explanation Port Manager ISSU client failed to get buffer for building a negotiation message. Hence, it can send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up.
Recommended Action i 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show logging and show checkpoint client)
Error Message%PM_ISSU-3-CAPABILITY : Port Manager ISSU client %s
Explanation Port Manager ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch between the client capability between the active and standby unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PM_ISSU-3-CAP_INVALID_SIZE : Port Manager ISSU client capability list is empty.
Explanation The Port Manager ISSU client capability exchange list size is invalid.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu capability entries )
Error Message%PM_ISSU-3-CAP_NOT_COMPATIBLE : Port Manager ISSU client capability exchange result incompatible.
Explanation The Port Manager ISSU client capability exchange has negotiated as incompatible with the peer.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu negotiated capability )
Error Message%PM_ISSU-3-INIT : Port Manager ISSU client initialization failed at %s, error %s
Explanation Port Manager ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PM_ISSU-3-MSG_NOT_OK : Port Manager ISSU client message %d is not compatible
Explanation Port Manager ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu message group and show issu session and show issu negotiated version )
Error Message%PM_ISSU-3-MSG_SIZE : Port Manager ISSU client failed to get the message size for message %d
Explanation Port Manager ISSU client failed to calculate message size for the message specified. The PM ISSU client will not be able to send message to the standby unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu message group and show issu session and show issu negotiated version )
Error Message%PM_ISSU-3-POLICY : Port Manager ISSU client message type %d is %s
Explanation Port Manager ISSU client received an message type which it does not support. The policy is applied to make the session compatible.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu session )
Error Message%PM_ISSU-3-SEND_FAILED : Port Manager ISSU client failed to send a negotiation message, error %d
Explanation Port Manager ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show logging and show checkpoint client)
Error Message%PM_ISSU-3-SESSION : Port Manager ISSU client %s
Explanation Port Manager ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu capability entries and show issu session and show issu negotiated capability )
Error Message%PM_ISSU-3-SESSION_UNREGISTRY : Port Manager ISSU client failed to unregister session information. Error: %d (%s)
Explanation The Port Manager ISSU client failed to unregister session information.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ( show issu session and show issu negotiated capability )
Error Message%PM_ISSU-3-TRANSFORM : Port Manager ISSU client %s transform failed, error %s
Explanation Port Manager ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message can not be applied on the standby unit. In both cases the Port Manager state will not be indentical with the active unit.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show issu session and show issu negotiated version )
Error Message%PM_MODEM_HIST-7-CSM_IC_CALLED_NUM : %s: ISDN incoming called number: %s
Explanation This is a tracing message indicating the number of the ISDN line recieving a call.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-CSM_IC_CALLING_NUM : %s: ISDN incoming caller number: %s
Explanation This is a tracing message indicating the number of an incoming ISDN caller.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-CSM_OC_CALLED_NUM : %s: ISDN outgoing called number: %s
Explanation This is a tracing message indicating a dialed ISDN number.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_DYNAMIC_EVT :
[chars]: [chars]
[chars]Explanation This tracing message indicates a dynamic event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_END_CONN_EVT :
[chars]: [chars]
[chars]Explanation This tracing message indicates an end-of-connection event from the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_ROS_EVT :
[chars]: [chars]
[chars]Explanation This tracing message indicates a link rate event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_STATE_EVT :
[chars]: [chars]
[chars] State: [chars]Explanation This tracing message indicates a state event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_STATIC_EVT :
[chars]: [chars]
[chars]Explanation This tracing message indicates a static event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-PORT_STATE_REACHED_NTF_EVT :
[chars]: [chars] [chars]Explanation This tracing message indicates a link rate event reported by the specified modem.
Recommended Action his is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-TRACE_HDR :
Modem [chars] Events Log:Explanation This is the initial message for the trace of the specified modem. The stored trace messages of the modem will follow.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-UNKNOWN_EVENT :
[chars]: Error in events logExplanation This tracing message indicates a formatting error in the modem event history. One or more events may be missing from the trace.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-UNKNOWN_FRAME :
[chars]: Error in events logExplanation This tracing message indicates a formatting error in the modem event history. One or more events may be missing from the trace.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_MAINT-1-BADEVENT : Invalid modem management %s event 0x%02x for modem(%s)
Explanation The modem management facility received an unrecognize event.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-1-BADMODEM : Modem (%s) failed %s
Explanation A software or hardware problem has been detected on a modem. The specific modem and reason are listed in the message.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-1-INITFAIL : Initialization failed.
Explanation Modem maintenance facility initialization failed.
Recommended Action Disable Autotest, Poweron test and avoid manual back-2-back test. 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-4-B2BABORT : Modems (%s) and (%s) back-to-back test: aborted
Explanation This is a tracing message indicating a back-to-back test failed between the two specified MICA modems.
Recommended Action Perform more back to back tests by pairing the failed modems with other modems to determine which modem is bad. Check the failed modems again after performing a power cycle. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-4-BADMODEMS : Modems (%s) and (%s) failed back-to-back test: %s
Explanation The two modems reported in the message failed a back-to-back test. At least one of them has failed.
Recommended Action Perform more back to back tests by pairing the failed modems with other modems to determine which modem is bad. Check the failed modems again after performing a power cycle. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-5-B2BCONNECT : Modems (%s) and (%s) connected in back-to-back test: %s
Explanation A back to back test connection has been made between the selected modems. The test is still in progress.
Recommended Action No action is required.
Error Message%PM_MODEM_MAINT-5-B2BINIT : Auto Back-to-Back test initiated by %s
Explanation This is a tracing message indicating an automatic back-to-back test was initiated by the specified MICA modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_MAINT-5-B2BMODEMS : Modems (%s) and (%s) completed back-to-back test: success/packets = %d/%d
Explanation The reported modems have passed the back to back test without any errors.
Recommended Action No action is required.
Error Message%PM_MODEM_MAINT-5-MODEM_OK : Modem (%s) passed the test
Explanation Tests on the specified modem were successful.
Recommended Action No action is required.
Error Message%PM_PVLAN_ISSU-3-BUFFER : Private Vlan ISSU client failed to get buffer for message, error [dec]
Explanation Private Vlan ISSU client failed to get buffer for building a negotiation message. Thus, it cannot send the negotiation message to the standby unit. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-CAPABILITY : Private Vlan ISSU client [chars]
Explanation Private Vlan ISSU client observed an error during capability negotiation. When this error happens there is a mismatch in the client capability between the active and standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries , show issu session and show issu negotiated capability commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-INIT : pm_pvlan Client Name ISSU client initialization failed at [chars], error [chars]
Explanation pm_pvlan Client Name ISSU client could not be initialized, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-MSG_NOT_OK : Private Vlan ISSU client message [dec] is not compatible
Explanation Private Vlan ISSU client received an incompatible message from the peer unit. As the message is not compatible it cannot be processed by this unit
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group , show issu session and show issu negotiated version commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-MSG_SIZE : Private Vlan ISSU client failed to get the message size for message [dec]
Explanation Private Vlan ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able to send message to the standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group , show issu session and show issu negotiated version commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-POLICY : Private Vlan ISSU client message type [dec] is [chars]
Explanation Private Vlan ISSU client received a message type which it does not support. The policy is applied to make the session compatible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-SEND_FAILED : Private Vlan ISSU client failed to send a negotiation message, error [dec]
Explanation Private Vlan ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-SESSION : Private Vlan ISSU client [chars]
Explanation Private Vlan ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries , show issu session and show issu negotiated capability commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_PVLAN_ISSU-3-TRANSFORM : Private Vlan ISSU client [chars] transform failed, error [chars]
Explanation Private Vlan ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases the pm_pvlan Client Name state will not be indentical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session and show issu negotiated version commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
PM_SCP Messages
The following are Port Manager SCP messages.
Error Message%PM_SCP-1-LCP_FW_ERR : System resetting module [dec] to recover from error: [chars]
Explanation A nonrecoverable error was detected by the line card firmware. The system is automatically resetting the module to recover from this error.
Recommended Action No action is required.
Error Message%PM_SCP-1-TASK_CREATE_FAIL : Failed to create SCP message handler task
Explanation Task creation has failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-2-LCP_FW_ERR_INFORM : Module %d is experiencing the following error: %s
Explanation An error condition was detected by the linecard firmware and the supervisor is being informed about it.
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-RESET : Module %d is resetting - Due to Packet Buffer Error.
Explanation An error condition was detected by the linecard firmware and the supervisor has initiated reset procedure for the linecard.
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-SHUTDOWN : Module %d is shutting down - Due to Packet Buffer Error.
Explanation An error condition was detected by the linecard firmware and the supervisor has initiated shutdown procedure for the linecard.
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-STDBY_NOT_SWTCH_OVER : Standby is not ready for switchover for Packet Buffer Error. Active-Sup (Module %d) is going down...
Explanation An error condition was detected by the supervisor firmware and standby is not ready for switch-over, active-Sup is going down
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-STDBY_RELOAD : Standby (Module %d) is reloading due to Packet Buffer Error...
Explanation An error condition was detected by the supervisor firmware and standby is reloading now.
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-STDBY_SWTCH_OVER : Supervisor (Module %d) is preparing for switch-over - Due to Packet Buffer Error.
Explanation An error condition was detected by the supervisor firmware and now its initiated the switch-over action.
Recommended Action Please report this to the Cisco tech support.
Error Message%PM_SCP-2-TRANSCEIVER_BAD_HW : Module %d will be power disabled for safety reasons because a defective transceiver is inserted at %s.
Explanation An inappropriate transceiver is inserted at the interface specified in the error message. This transceiver should not be used in this system.
Recommended Action Remove the specified transceiver and enablepower to the module. If this transceiver was purchased from Cisco, pleasecontact Cisco TAC to get the transceiver replaced.
Error Message%PM_SCP-2-TRANSCEIVER_INCOMPATIBLE : Transceiver inserted in %s port %d/%d is not compatible with its interface (transceiver speed is %s, interface speed is %s)
Explanation An incompatible transceiver is inserted in the module specified in the error message. This transceiver should not be used with this module.
Recommended Action Replace the specified transceiver with anothertransceiver that is compatible with this module.
Error Message%PM_SCP-3-GBIC_BAD : GBIC integrity check on port [dec]/[dec] failed: bad key
Explanation The GBIC has an incorrectly programmed EEPROM.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-3-GBIC_DUP : GBICs in ports [dec]/[dec] and [dec]/[dec] have duplicate serial numbers
Explanation The GBIC was identified as a Cisco GBIC, but its vendor ID and serial number match those of another GBIC on the system.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-3-LCP_FW_ABLC : Late collision message from module %d, port:0%d
Explanation Linecard firmware detected abnormal collisions in port traffic.
Recommended Action Usually a temporary situation. If the situation is recurrent, please report this to the Cisco tech support
Error Message%PM_SCP-3-TRANSCEIVER_BAD_EEPROM : Integrity check on transceiver in %s port %d/%d failed: bad key
Explanation The transceiver has an incorrectly programmed EEPROM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_SCP-3-TRANSCEIVER_DUPLICATE : Transceiver in %s port %d/%d and in %s port %d/%d have duplicate serial numbers
Explanation The transceiver was identified as a Cisco transceiver, but its vendor ID and serial number match that of another transceiver on the system.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_SCP-3-TRANSCEIVER_UNSUPPORTED : Unsupported transceiver in [chars] port [dec]/[dec]
Explanation The module was identified as an unsupported non-Cisco transceiver.
Recommended Action If this transceiver was purchased from Cisco, contact Cisco TAC to get the transceiver replaced.
Error Message%PM_SCP-4-FPOE_INFO : An unsupported distributed fabric card has been detected
Explanation Fabric capable line cards are not supported in this system.
Recommended Action Please report this to the Cisco tech support
Error Message%PM_SCP-4-LCP_FW_ABLC : Late collision message from module [dec], port:0[dec]
Explanation The line card firmware has detected abnormal collisions in port traffic.
Recommended Action Usually, this is a temporary situation. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-4-LCP_FW_INFORM : Linecard firmware Inform message from module [dec], sub-command:[hex]
Explanation An Inform message has been sent to the supervisor by the line card firmware.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-4-LCP_TEMP_ALARM : Received temperature alarm message from module [dec], alarm:[hex]
Explanation A message has been sent to the supervisor by the line card firmware.
Recommended Action This message is usually not critical. In some situations, the affected line card module will be automatically reset.
Error Message%PM_SCP-4-TRANSCEIVER_UNSUPP_MODULE : Interface %s does not support receive-only transceivers
Explanation A receive-only transceiver has been inserted into a module which does not support it.
Recommended Action Use the receive-only transceiver with a supported module. Refer to documentation for modules which support receive-only transceivers
Error Message%PM_SCP-4-UNK_OPCODE : Received unknown unsolicited message from module [dec], opcode [hex]
Explanation A message has been sent to the supervisor by the line card firmware.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-6-LCP_FW_ERR_INFORM : Module [dec] is experiencing the following error: [chars]
Explanation An error condition was detected by the line card firmware, and the supervisor is being informed of the condition.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PM_SCP-SP-1-LCP_FW_ERR : System resetting module [dec] to recover from error: [chars]
Explanation This message indicates that the firmware of the specified module detected an error. [dec] is the module number and [chars] is the error.
Recommended Action The system is automatically resetting the module to recover from the error.
Error Message%PM_SCP-SP-3-GBIC_BAD : GBIC integrity check on port [dec]/[dec] failed: bad key
Explanation This message indicates that the GBIC has an incorrectly programmed EEPROM. [dec]/[dec] is the module and port.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM_SCP-SP-4-LCP_FW_ABLC : Late collision message from module [dec], port:0 [dec]
Explanation The line card firmware has detected abnormal collisions in port traffic.
Recommended Action This is usually a temporary condition. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. %PNNI-2-NO_INTERNAL_NUMBER : Empty Internal Number Stack: [chars]
Explanation An internal software error has occurred.
Recommended Action 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 help identify 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 command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-2-FLOOD_ERROR : %s %PNNI-2-NO_INTERNAL_NUMBER : Empty Internal Number Stack: %s
Explanation An internal software error has occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%PNNI-2-NO_INTERNAL_NUMBER : Empty Internal Number Stack: [chars]
Explanation An internal software error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-2-SPF_ERROR : Tent List Overflow in %s
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-3-INTERNAL_ERROR : %s%s %x
Explanation An internal software error occurred. The message contains more information that can be used to identify the problem.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-3-INVALID_MEM : Bad address of %s %#x, please collect show atm pnni trace error
Explanation An internal software error occurred.
Recommended Action Use show atm pnni trace error to collect more information. If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-4-ADDRESS_EXIST : Address derived from the switch's prefix by soft PVC manager %s clashes with existing address in prefix table
Explanation An PVC port address assignment has collided with an existing address. An address that would have been assigned by this switch has already been assigned by another.
Recommended Action If possible, assign a new MAC address to the peer system that caused the assignment collision.
Error Message%PNNI-4-ATM_SYS_ERROR : Error: %s
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-4-BADPACKET : Invalid %s pkt: %s %d %d
Explanation An invalid packet was received from a network peer.
Recommended Action Check the originating device for a cause of the corrupted packets.
Error Message%PNNI-4-BADROUTEREQ : Bad Request from Signaling %x
Explanation A source routing request by another network host was corrupted.
Recommended Action Check the originating system for a cause of the problem.
Error Message%PNNI-4-CONFIG_ERROR : Configuration Error: %s
Explanation This message indicates a configuration error in the PNNI subsystem. The message will display more specific information about the cause of problem.
Recommended Action Change the confguration to correct the error.
Error Message%PNNI-4-DUPLICATE_NODE_ID : %s %s for node %d %s
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-6-INFO : %s
Explanation This is an informational message only.
Recommended Action Informational messages can be disabled by changing logging level.
Error Message%PNNI-7-DEBUG : %s
Explanation This is an informational message only. It is used by Cisco for testing.
Recommended Action Informational messages can be disabled by changing logging level.
Error Message%PM_SCP-1-LCP_FW_ERR_POWERDOWN : Module [dec] will be powered down due to firmware error: [chars]
Explanation An unrecoverable error was detected by the line card firmware causing powering down of the line card.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-3-CHUNK_CREATE : chunk create failed
Explanation The chunk creation failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-3-CREATE_FAIL : creation failed : [chars]
Explanation The creation of the element indicated in the message failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-4-FSM_FIND_INFO_FAIL : Could not find element (if_number [dec]) in FSM list
Explanation The system could not find the element specified in the message in the finite state machine (FSM) list.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-3-MALLOC_FAIL : malloc failed : [chars]
Explanation The memory allocation failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-3-PROC_ALL_TRANSIT_EVENT : All events could not be processed in transit queue
Explanation All events in the transit queue could not be processed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_FSM-3-TRANSIT_EVENT : Invalid event [dec] while processing transit event queue
Explanation An error occurred because the system encountered an invalid event while processing the transit event queue.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_L3_TRIG-3-CHUNK_CREATE : chunk create failed
Explanation An error occurred because a chunk failed to create.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_L3_TRIG-3-INVALID_CLIENT_TYPE : Invalid client type ([dec]) from xdr
Explanation An error occurred because the system encountered an invalid client type in the External Data Representation (XDR) message.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_L3_TRIG-3-ISSU_COMP_FAIL : L3 trigger xdr priority msg not issu compatible
Explanation An error occurred because the Layer 3 trigger External Data Representation (XDR) priority message is not In-Service Software Upgrade (ISSU) compatible.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PPROT_L3_TRIG-3-MALLOC_FAIL : malloc failed: [chars]
Explanation The memory allocation failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_API-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action Unavailable.
Error Message%POLICY_API-4-POLICYDYNCLR : Dynamic policy on intf:[chars] cleared. Static policy in use.
Explanation A dynamic policy was overriding the static policy. The dynamic policy has been cleared, the static policy is now in effect.
Recommended Action No action is required.
Error Message%POLICY_API-4-POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action Remove the static policy configuration, if desired.
Error Message%POLICY_API-4-POLICYSTATICCLR : Static policy on intf:[chars] cleared. Dynamic policy in use.
Explanation A dynamic policy was overriding the static policy. Static policy has been cleared.
Recommended Action No action is required.
Error Message%POLICY_MANAGER-2-INIT_FAILURE : Init failure: [chars]
Explanation A problem occurred in the Policy Manager during initialization.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation The event pool has been depleted. There are no free buffers to process event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-INVALID_ACTION : Invalid action
Explanation An invalid Policy Manager action was detected.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-INVALID_PARAMETERS : A call to Policy Manager is made with invalid parameters
Explanation A call to Policy Manager was made with one or more invalid parameters.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation The event that was received by the Policy Manager contained an invalid severity and was therefore not processed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-NO_FREE_POLICY_IDS : No more Policy IDs available
Explanation There are no more Policy IDs that can be allocated. The effect of this condition is that Policy Manager policies can no longer be created.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation The Policy Manager attempted to invoke an action which was NULL.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%POLICY_MANAGER-3-PRE_INIT_CALL : Policy Manager routine called prior to initialization
Explanation The Policy Manager component was called prior to initialization.This could result in vital information being lost.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORT-4-MACADDRERR : Failed to get Mac Base Address
Explanation The four-port Gigabit interface could not obtain a MAC base address.
Recommended Action System operation continues normally. No action is required.
Error Message%PORT-4-OUTOFSYNC : GMAC is not in SYNC: port [dec]
Explanation The four-port Gigabit interface is not in synchronization with the rest of the system.
Recommended Action System operation continues normally. No action is required.
Error Message%PORT-6-NULL_OBJ : Port object %s is unavailable.
Explanation Information about this port could not be retrieved. The port may not exist.
Recommended Action No action is required.
Error Message%PORT-6-PORT_RECOVERY : %s %s
Explanation Recovery has been triggered. Configured action will take place on the port
Recommended Action No action is required.
Error Message%PORT-6-SESSION_RECOVERY : %s %s %d
Explanation Session recovery has an invalid cause code
Recommended Action No action is required.
Error Message%PORT-6-SM_PORT_CLEARED : %s
Explanation The ports will be reset, and any active calls on these ports will be terminated
Recommended Action No action is required.
Error Message%PORTCHAN-2-CRITEVENT : Unable to create Toaster Instance for interface [chars]
Explanation Notification of Failure in creating EtherChannel interface for PXF.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORTCHAN-3-EREVENT : [chars] [chars]
Explanation General EtherChannel error to be used for sanity tests .
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORTCHAN-3-IDB_MISMATCH : Mismatch in IDB for interface [chars] at index [dec]
Explanation Notification of Mismatch in IDB for EtherChannel member-link.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORTCHAN-3-INVALID_INDEX : [chars] [chars] [dec]
Explanation Notification of Invalid index for EtherChannel member-link.
Recommended Action 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. . Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORTCHAN-6-LINKMTU : [chars]
Explanation Notification of etherchannel link MTU changes.
Recommended Action No action is required. P
Error Message%PORTCHAN-6-UNSUPPORTED_POLICY : [chars]
Explanation Notification of unsupported service-policy for EtherChannel Bundle or member-link.
Recommended Action No action is required.
Error Message%PORT_SECURITY-2-INELIGIBLE : Port security configuration on [chars] is being made inactive since the port is now not eligible for port security as [chars].
Explanation A port had port security configuration on it, but the port now has a configuration not supported with port security. Since the port is now not eligible for port security, the port security configuration on it is being made inactive.
Recommended Action Check the port's configuration and remove the offending configuration that is not compatible with port security.
Error Message%PORT_SECURITY-2-PSECURE_VIOLATION : Security violation occurred, caused by MAC address [enet] on port [chars].
Explanation An unauthorized device attempted to connect on a secure port. The MAC address of the unauthorized device and the secure port are specified in the message text. The two causes of the error message are as follows:
–
The number of MAC addresses learned is more than the value configured by the switchport port-security maximum command.
–
Recommended Action Determine the device that attempted to connect on the secure port. Notify your network system administrator of this condition. Determine whether the values set by the two commands mentioned above need to be adjusted. If not, remove the offending device. If the problem persists, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PORT_SECURITY-2-PSECURE_VIOLATION_VLAN : Security violation on port %s due to MAC address %e on VLAN %d
Explanation An unauthorized device attempted to connect on a secure trunk port. The MAC address of the unauthorized device and the secure trunk and VLAN are specified in the error message.
Recommended Action Determine the device that attempted to connect via the secure trunk port. Notify your network system administrator of this condition.
Error Message%PORT_SECURITY-4-PORTSEC_RATELIMIT_DISABLED : Layer 2 port security rate limiter disabled while port security enabled.
Explanation Layer 2 port security rate limiter disabled by user while port security is enabled.
Explanation Configure: mls rate-limit layer2 port-security 6000 10.
Error Message%PORT_SECURITY-4-PORTSEC_RATELIMIT_FAIL : Fail to set port security rate limiter when enabling port security.
Explanation This failure happens when enabling port security.
Recommended Action Configure: mls rate-limit layer2 port-security 6000 10. It may be necessary to remove an existing layer 2 rate limiter.
Error Message%PORT_SECURITY-6-ADDRESSES_REMOVED : Maximum system secure address count reached. Some secure addresses configured on port %s removed.
Explanation Some configured and sticky MAC addresses on the specified port were removed from the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes (for example, when the port is converted from a L3 to a L2 port).
Recommended Action No action is required.
Error Message%PORT_SECURITY-6-ADDR_REMOVED : 'Address [IP_address]/[IP_address]
Explanation There is not enough memory to allocate a PXF NAT static entry. PXF switched traffic for this entry will fail.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PT-3-PT_HW_UNAVAIL : Protocol Tunneling hardware resource not available. [chars]
Explanation Protocol tunneling could not be enabled because no redirect registersare available. Protocol Tunneling requires redirect registers
Recommended Action Disable any applications that uses redirect registers and tryconfiguring the Protocol Tunneling again
Error Message%PT-3-PT_NO_SWSB : Protocol Tunneling software subblock not found. [chars]
Explanation The software subblock that is used for protocol tunnelling could not be found for the port specified in the message text. Protocol tunnelling has been disabled on this port.
Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%PVDM-6-UNSUPPORTED: Codec G.723 is not supported on PVDM3.
Explanation G.723 calls are not supported on PVDM3 digital signal processing (DSP).
Recommended Action Change the configuration to use C5510 DSP to enable G.723 calls.
Error Message%PXF_NICKEL-2-BOUND_MODE_OTHER_SSLT_IB_ERR : Card for which Ironbus interface restart is being initiated is running in Bound mode. Opposing subslot is slot [dec], subslot [dec] Opposing subslot's IB error statistics counts are as follows: multisop_1frm = [int], bad9th_bit_frm = [int], allzeros = [int], unexp_fsync = [int], missing_fsync = [int], len_hi_nonzero = [int], giant = [int], runt = [int]
Explanation In bound mode, opposing subslot IB errors.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-BOUND_MODE_OTHER_SSLT_IMCMP_ERR : Card for which Ironbus interface restart is being initiated is running in Bound mode and opposing subslot's Ironbus interface is not in a compatible state. (i.e. - Opposing subslot is either in reset, not ready, or does not have Cobalt event processing enabled for it.) Opposing subslot is slot [dec], subslot [dec] Opposing subslot's reset bit = [hex] (1 = subslot in reset) Opposing subslot's ready bit = [hex] (0 = subslot not in ready state) Opposing subslot's event mask bit = [hex] (1 = event processing for subslot is not enabled)
Explanation In bound mode, opposing subslot not compatible.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_FBB_EVT : Nickel FBB Error: nickel[dec] fbb_event_reg @ [hex] = [hex]
Explanation Nickel FBB Event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_FTS_EVT : Nickel FTS Error: nickel[dec] fts_event_reg @ [hex] = [hex]
Explanation Nickel FTS Event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_IB_EVT : Nickel Ironbus Error: ib_event @ [hex] = [hex]
Explanation Nickel IB Event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_IB_SEC_READ_ERR : Nickel Ironbus Err Second Read Non-Zero: stat1=[hex], stat2=[hex], stat3=[hex]
Explanation Nickel IB Error Not Clear on Read.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_IB_SLT : Nickel Ironbus Error: nickel[dec] IB slot[dec]/subslot[dec] event
Explanation Nickel IB Event In Slot.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_IB_STAT : Nickel Ironbus Stat[dec]: @ [hex] = [hex]
Explanation Nickel IB Statistic.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_REG : Nickel Global Event Reg: nickel[dec]: Addr = [hex], Value = [hex]
Explanation Nickel Global Event Register.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_STT_EVT : Nickel STT Error: nickel[dec] stt_event_reg @ [hex] = [hex]
Explanation Nickel STT Event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-GLOB_EVT_TBB_EVT : Nickel TBB Error: nickel[dec] tbb_event_reg @ [hex] = [hex]
Explanation Nickel TBB Event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-IB_ENABLE_FAILED : Ironbus enable failed
Explanation Ironbus enable failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-IB_ERR_OVER_THRSHLD : IB error statistics exceeded threshold for slot [dec], subslot [dec] IB restart initiated. Subslot error statistics counts are as follows: multisop_1frm = [int], bad9th_bit_frm = [int], allzeros = [int], unexp_fsync = [int], missing_fsync = [int], len_hi_nonzero = [int], giant = [int], runt = [int]
Explanation Too many ironbus errors .
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-IB_ERR_SPR : IB Stuck Pause Request Error in slot[dec]/subslot[dec]: status reg @ [hex] = [hex]
Explanation Ironbus Stuck Pause Request Error.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-IB_STATUS_FAILED : [chars] received failure status
Explanation Ironbus status failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-INVALID_EVNT_ID : [chars]: invalid event id ([dec])
Explanation Invalid event ID.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-INVALID_SLOT0_CFG : Current HW level not allow to configure subslot 0.
Explanation Incorrect configuration to slot 0.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-INVALID_SLOT_PTR : get_vanadium_revision(): Error - Invalid slot pointer
Explanation Invalid slot pointer.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-LC_ASIC_VER_ERR : Error:get_lc_asic_ver() failed. Slot[dec]
Explanation Incorrect LC ASIC version.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-LC_NOT_IN_SLOT : LC in slot [dec] doesn't exist
Explanation No LC in the slot.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-NOT_HANDLED_EVNT : Event [chars] not handled
Explanation Not handled event.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-PLL_NOT_LOCK : PLLs did not lock: glob_status @[hex] = [hex]
Explanation PLL not lock.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-SLOT_OUT_OF_RANGE : is_slot_bound(): Received out-of-range slot value. Slot passed in = [dec].
Explanation Slot number passed into is_slot_bound() is out of range.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-TBB_SYNC_FAILED : TBB sync of the RP failed. No traffic is being sent to the RP!
Explanation TBB synchronization of RP failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-TBB_SYNC_LC_FAILED : TBB sync of the line card failed (slot [int]/[int]). No traffic is being through the line card. Need to reset the line card.
Explanation TBB synchronization of RP failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-TIB_IB_RESET_FAILED : TIB IRONBUS_RESET command failed
Explanation Reset TIB failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-2-UNKNOWN_EVNT_REG : [chars]: unknown event register ([dec])
Explanation Unknown event register.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-FBB_LINE_CARD : A Nickel FBB Line Card Error has occurred.
Explanation A Nickel FBB Line Card Error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-FTBB_ERROR : FTBB is set to disable for slot [int]/[int]!
Explanation FTBB is disabled.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-FTS_ERROR : FTS [chars] Error: [dec] in nicket[dec]/port[dec]
Explanation Ingress Nickel—Cobalt3 ASIC communication Error.
Recommended Action Monitor system to determine if this error message is persistent. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-INIT_ERR : Nickel Initialization failed!
Explanation Nickel ASIC initialization failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware nickel command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-IRONBUS_NOTRUNNING : Data path to slot [int]/[int] failed to synchronize ([chars])
Explanation NICKEL data path could not be initialized.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-MALLOCFAIL : Nickel driver malloc failed!
Explanation Not enough free memory for the NICKEL driver to operate.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-NOT_INIT : Either no Nickel on the board or Nickel init failed.
Explanation Either no Nickel on the board or Nickel initialization failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-REG_ADDR_ERR : Nickel Address Error [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid Nickel register address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware nickel command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-SPI_SYNC_FAIL : Nickel[int] SPI RX/TX Sync Failure: spi4_status=[hex]
Explanation NICKEL SPI RX/TX sync failure.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-STT_ERROR : STT [chars] [chars] Error: [dec] in nickel[dec]
Explanation Egress Cobalt3—Nickel ASIC communication Error.
Recommended Action Monitor system to determine if this error does not appear together with a PXF restart. If this error is presistent (for example it appears more than once or twice in a day AND it does not appear together with a PXF restart then there might be a hardware issue which warrants further investigation by Cisco Technical Support
Error Message%PXF_NICKEL-3-STT_PORT_ERROR : STT [chars] Error: [dec] in nickel[dec]/port[dec]
Explanation Egress Cobalt3—Nickel ASIC communication Error.
Recommended Action Monitor system to determine if this error does not appear together with a PXF restart. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-TBB_ERROR : TBB [chars] Error: [dec] in slot [dec]/subslot[dec]
Explanation Egress Cobalt3—Nickel ASIC communication Error.
Recommended Action Monitor system to determine if this error message is persistent.If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_NICKEL-3-VAN_V1_NOT_SUPPORT : slot [int] contains a Vanadium version 1 LC which is no longer supported by C10K3.
Explanation This slot contains a Vanadium1 LC not supported by C10K3.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
PXF_QOS Messages
The following are Parallel eXpress Forwarding (PXF) Quality of Service (QoS)-related messages.
Error Message%PXF_QOS-3-LINK_BANDWIDTH : VTMS will not work correctly. Use hierarchical policy-map for this interface.
Explanation This interface does not have a configured link bandwidth. A link bandwidth is required for VTMS to operate correctly.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_ATTACH_POLICY : PXF MEM ERROR when attaching service policy in PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. The service policy-map could not be properly attached to the PXF interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_DETACH : PXF MEM ERROR when detaching CBWFQ from an interface in PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. CBWFQ could not be properly detached from the PXF interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_PARAM : PXF MEM ERROR when downloading CBWFQ parameters to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. CBWFQ parameters could not be properly downloaded to the PXF chip.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_SETUP : PXF MEM ERROR when setting CBWFQ up in an interface in PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. CBWFQ could not be properly set up in the PXF interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_CLASS_ENTRY : PXF MEM ERROR when downloading QoS classificaton entry to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. A QoS classification entry could not be properly downloaded to the PXF memory.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_CLR_WRED_CNT : PXF MEM ERROR when clearing a WRED counter in PXF (Addr=[hex])
Explanation An error occurred during writing to the PXF memory. The PXF WRED counter could not be properly cleared.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_DETACH_POLICY : PXF MEM ERROR when detaching service policy in PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. The service policy map could not be properly detached from the PXF interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_POL_PARAM : PXF MEM ERROR when downloading policing parameters to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. Police parameters could not be properly downloaded to the PXF interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_PRI_PARAM : PXF MEM ERROR when downloading priority parameters to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. Parameters for the priority command could not be properly downloaded to the PXF memory.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_SET_PARAM : PXF MEM ERROR when downloading marking parameters to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. Parameters for the set command could not be properly downloaded to the PXF memory.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_WRED_CNT : PXF MEM ERROR when reading a WRED counter from PXF (Addr=[hex])
Explanation An error occurred during reading from the PXF memory. The specified PXF WRED counter could not be properly read (a 0 value is assumed).
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_MEM_ERR_WRED_PARAM : PXF MEM ERROR when downloading WRED parameters to PXF (Addr=[hex])
Explanation An error occurred during reading from or writing to the PXF memory. WRED parameters could not be properly downloaded to the PXF memory.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-PXF_QOS_L2_MEMORY_EXCEEDED : Maximum possible outcomes exceeded for L2 classification tables. Only [int] bytes free.
Explanation QoS PXF L2 Classification Engine (based on turbo acl): Memory limit has been exceeded.
Recommended Action Modifying the L2 ACLs to trigger recompilation might free some memory.
Error Message%PXF_QOS-3-QOS_RP_GEN_XOFF : XOFF with tif number 0 is generated
Explanation PXF received unexpected XOFF from RP; overridden.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_QOS-3-QOS_STAT_GENERATION_FAIL : Cannot [chars] actual QoS statistics generation in PXF
Explanation An error occurred when enabling or disabling QoS Statistic Generation.
Recommended Action Disable and re-enable PXF qos-statistics. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PXF_QOS-3-SUB_INTF_SRVPOL_FAIL : Error attaching [chars] service-policy PXF data to [chars]: [chars]
Explanation The assignment of the PXF portion of the service-policy data to a sub-interface has failed. This means that, even though the configuration shows that the service-policy is attached to the sub-interface, the download of the necessary PXF data has not occurred. Because of that, the service-policy will not be effective on the sub-interface.
Recommended Action Detach and reattach the service-policy to the sub-interface. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PXF_QOS-3-TOO_MANY_POSSIBLE_OUTCOMES : Too many possible turbo acl outcomes: [dec] (max policies: [dec]).
Explanation The QoS PXF classification engine (based upon turbo ACL) has determined that there is not enough memory to hold all possible outcomes of the turbo ACL compilation.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-TOO_MANY_POSSIBLE_OUTCOMES_FOR_POLICIES : Too many possible turbo acl outcomes ([dec]) for current number ofconfigured policy-maps ([dec]).
Explanation The QoS PXF classification engine (based upon turbo ACL) has determined that because of the current number of policy maps, there is not enough memory to hold all possible outcomes of the turbo ACL compilation.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-TOO_MANY_POSSIBLE_POLICIES_FOR_OUTCOMES : Too many configured policy-maps ([dec]) for current number ofTurboACL classification outcomes ([dec]).
Explanation The QoS PXF classification engine (based upon turbo ACL) ha s determined that because of the current number of possible outcomes of the turbo ACL compilation, there is not enough memory to hold new policy maps.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_QOS-3-UNKNOWN_QOS_ACTION : Unknown QoS action type: [hex].
Explanation A QoS feature, unrecognized by PXF, has been configured with the modular QoS CLI. The feature will work, but excessive punting can occur if the feature is on an output interface.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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. PXF_VRFS Messages
Recommended Action The following are Parallel eXpress Forwarding (PXF) VRF Select (VRFS) messages.
Error Message%PXF_QOS-3-WS_QOS_L2C_CLASS_NODE_TOO_LARGE : Classification node [dec]'s table size of [int] is too large for PXF. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: the size of classification table for the specified node is larger than the amount of PXF memory set aside for that node.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_QOS-3-WS_QOS_L2C_EGRESS_CLASS_ENTRY_PXF_MEM_ERR : PXF MEM ERROR when downloading classification entry of egress traffic to PXF (Addr=[hex]). PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: an error occurred when writing to PXF memory. The classification entry could not be properly downloaded.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_QOS-3-WS_QOS_L2C_MALLOC_FAILED_PLATFORM_INIT : The system failed to allocate a PXF data structure for layer 2 classification engine. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: there is not enough memory to setup layer 2 classification engine.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_QOS-3-WS_QOS_L2C_TOO_MANY_L2_LKP_TBLS : Too many possible PXF QoS layer 2 lookup tables: [int]. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: the resulted PXF QoS layer 2 lookup tables exceeds system limitation.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
PXF_VRFS Messages
The following are Parallel eXpress Forwarding (PXF) VRFS selection-specific messages.
Error Message%PXF_VRFS-3-CHUNKFREE : Node resource could not be freed
Explanation The router tried to free a node resource for an IP address range but failed to do so. The router might still continue to function correctly, however, if this re-occurs often, the router might run out of memory and reload.
Recommended Action This is a software problem. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_VRFS-3-NOADD : IP address range [IP_address]/[IP_address] not added to the VRF selection table: [chars]
Explanation When the router processed a configuration command to add an IP address range to a VRF selection table the router could not complete the command. The error message shows the reason why.
Recommended Action Reasons for this to happen could be software errors and resource problems. Should the error message indicate that memory allocation failed, then try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem then you might need to install more memory in the router.
Error Message%PXF_VRFS-3-NOTABLE : Initialization for PXF VFR-Select failed: [chars]
Explanation The router failed to initialize the internal database to keep the VRF selection table. The reason is shown in the error message.
Recommended Action The reason for this can be a software problem or router memory exhaustion. Verify that the router has enough memory using the show memory summary command. If the router does have enough memory then 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_VRFS-3-NOTFOUND : Node for IP address range [IP_address]/[IP_address] was not found
Explanation When the router processed a configuration command to remove an IP address range from a VRF selection table the router could not find the entry in its internal database.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PXF_VRFS-3-WS_VRFS_EVENT : [chars]
Explanation This message is for generic PXF VRFS errors.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%PXF_VRFS-6-NOHWNODE : No PXF node resource available to add IP address range
Explanation When adding an IP address range to a VRF selection table PXF could not allocate a node structure for the IP address range shown in the message. The reason for this is that too many addresses have been added already and PXF has run out of resources for VRF-Select to maintain a larger number of addresses.
Recommended Action Try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem then you might need to turn PXF off or use a non-PXF routing engine.
Error Message%PXF_VRFS-6-NONODE : No node resource available for [IP_address]/[IP_address]
Explanation When adding an IP address range to a VRF selection table the router could not allocate a node structure for the IP address range shown in the message. The reason for this is that too many addresses have been added already and the router has run out of resources for VRF-Select to maintain a larger number of addresses.
Recommended Action Try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem then you might need to install more memory in the router.
Error Message%QA-3-ALLOC : %s
Explanation This is a software error.
Recommended Action Copy the error message exactly as it appears. Also copy the output of show version and show cont cbus. Contact your technical support representative.
Error Message%QA-3-DIAG : [chars]
Explanation This is a diagnostic message.
Recommended Action This message appears after a QA error, and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Also copy the output of show version and show cont cbus. Contact your technical support representative.
Error Message%QATM-2-ASDATA_READ : Cannot read TCAM associated data
Explanation The hardware might have failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QATM-2-ASDATA_WRITE : Cannot write TCAM associated data
Explanation The hardware might have failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QATM-2-TCAM_READ : Cannot read TCAM
Explanation The hardware might have failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QATM-2-TCAM_WRITE : Cannot write the TCAM
Explanation The hardware might have failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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. QM Messages
Recommended Action The following are Quality of Service (QoS) Manager messages.
Error Message%QATM-4-TCAM_LOW : TCAM resource running low for table %s, resource type %s, on TCAM number %d.
Explanation Specific hardware TCAM resource running low, system may become unstable if resource gets even lower.
Recommended Action Careful with further actions requiring more TCAM resource. Use command, show tcam ..., to monitor. If possible, change to a different TCAM allocation profile using the command, sdm prefer ...
Error Message%QBM-3-QBM_CONSISTENCY : QBM internal error: [chars]
Explanation An action attempted by the QoS Bandwidth Manager implementation encountered an unexpected software condition
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show qbm client, show qbm pool, show running, and show version commands to gather data which might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QEM-3-DISCOVER : Found %s switch processors
Explanation The QEM driver found either no switch processors or more than one. Exactly one is the only supported configuration.
Recommended Action Make sure there is only one switch processor.
Error Message%QLLC-3-BADOPCODE : Opcode %s is invalid
Explanation Either remote source-route bridging or local acknowledgment is configured incorrectly.
Recommended Action Verify that remote source-route bridging and local acknowledgment are configured correctly.
Error Message%QLLC-3-BADQLLCSTATE : Bad qllc state - %s
Explanation An invalid QLLC primitive was detected.
Recommended Action Verify that the partner QLLC device is configured correctly.
Error Message%QLLC-3-BADRSRBOPCODE : Bad opcode %04x from %e to %e
Explanation Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.
Recommended Action Verify that remote source-route bridging is configured correctly with the right version of the IOS software.
Error Message%QLLC-3-BADSTATE : Bad qllc state - %s - %e
Explanation An invalid LLC primitive was detected.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message%QLLC-3-BADSTATEEVENT : Bad qllc state - %s event - %s macaddr - %e
Explanation The LLC primitive specified placed the router in an invalid state.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message%QLLC-3-BAD_XID : Sna configuration error for %e: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)
Explanation The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3 which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation - for example, Revision A5.6 on, and C5.1 on the 3172. A likely cause is that the revision levels on the IBM equipment are incompatible.
Recommended Action Check the revision levels on the external equipment, and upgrade them if necessary.
Error Message%QLLC-3-DIFFPRTR : %e - Different partner - originally %e - now %e
Explanation The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action Verify that the qllc partner statement in the configuration file is correct.
Error Message%QLLC-3-GENERRMSG : %s
Explanation The text string provided with this error message describes the specific QLLC problem.
Recommended Action Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QLLC-3-IFRAME : %s
Explanation An I-Frame was discarded due to network congestion.
Recommended Action Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QLLC-3-INCALL_CFG : Incoming call: No QLLC Service Access Point Configured for x.25 subaddress %s
Explanation A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.
Error Message%QLLC-3-INCALL_NO_PARTNER : Incoming call: No partner Mac Address configured - X.25 subaddress %s
Explanation There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (for QLLC/DLSw+ only).
Recommended Action Configure a partner for the incoming calling (such as using the qllc dlsw partner command).
Error Message%QLLC-3-LNXNOTFOUND : lnx_remove_macaddr_hash did not find target lnx
Explanation The qllc srb command was not defined for this interface.
Recommended Action Add a valid qllc srb statement for this serial interface.
Error Message%QLLC-3-NOLLC2 : Unable to open an llc2 session
Explanation An LLC2 session could not be established with the destination MAC address.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message%QLLC-3-NOMACADDR : No lnx entry for macaddr %e
Explanation No virtual MAC address was defined for this interface.
Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.
Error Message%QLLC-3-NOMEM : Not enough memory available
Explanation There is not enough memory in the system to complete this request.
Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.
Error Message%QLLC-3-NONULLXID : Couldn't make null xid - %e -%e
Explanation An attempt to create an IEEE XID failed.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message%QLLC-3-NOPAKENQ : Pak enqueue failed
Explanation A packet was not sent to the LAN.
Recommended Action Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.
Error Message%QLLC-3-NOXID2 : Couldn't make xid - %e -%e
Explanation The QLLC XID could not be forwarded to the LAN.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Error Message%QLLC-3-NO_QLLCBUFFER : M bit Reassembly failed - couldn't allocate a packet
Explanation The router ran out of memory to allocate buffers.
Recommended Action Make sure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will need more memory.
Error Message%QLLC-3-NO_QSR : No QLLC Service Access Points defined
Explanation No QLLC services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action Configure the QLLC service required.
Error Message%QLLC-3-NO_RESOURCE : Incoming Call: Insufficient resources available
Explanation This message is reporting insufficient system memory.
Recommended Action Upgrade the memory.
Error Message%QLLC-3-NULLPTR : %s ptr is null
Explanation The specified structure was not configured.
Recommended Action Confirm the configuration commands for the structure.
Error Message%QLLC-3-PARTNER_MISMATCH : Outgoing call: Partner Mac Address %e doesn't match configured partner %e
Explanation A device tried to connect to a QLLC VMAC (from Token Ring, for instance), but the MAC address of that device does not match the partner in the qllc dlsw command.
Recommended Action Correct the QLLC configuration to match the right partner.
Error Message%QLLC-3-QLLCMAP_ERR : Incoming call: QLLC map entry not found
Explanation A software error in the router code occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QLLC-4-NOQLLC : Unable to open qllc session, current state is %s
Explanation A QLLC session could not be established.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Error Message%QM-2-ACL_FAILURE : Interface %s traffic will not comply with ACLs in %s direction(s)
Explanation ACLs will not be applied to traffic for this interface due to TCAM resource contention.
Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%QM-2-ACL_MERGE_NO_MEM : Memory low: ACL merge failed for interface [chars] in [chars] direction
Explanation Insufficient system memory was available for merging ACLs.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-AGGREG_FAILURE : Interface %s aggregate QoS will not comply with policymap in %s direction(s)
Explanation QoS will not be applied to traffic for this interface due to aggregate policer resource contention.
Recommended Action There are too many configured aggregate policers fit in the hardware Aggregate RAM. Try to share the same aggregate policer(s) across multiple classes or/and interfaces in order to reduce policer resource contention. Use named QoS aggregates as a mechanism for sharing policers.
Error Message%QM-2-BAD_MESSAGE : Error in internal messaging - bad result %d
Explanation Software error may have effected programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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.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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-2-BAD_TLV : Error in internal messaging - bad tlv %d
Explanation Software error may have effected programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-2-CONFORM_ACTION_NE : Different aggregate and microflow conform-action in class %s[policy %s]
Explanation Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.
Recommended Action Change the conform-action in 'police' or 'police flow' command to make both actions the same, or remove one of two commands.
Error Message%QM-2-DSCP_NE : Different aggregate and microflow DSCP in class %s[policy %s]
Explanation Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.
Recommended Action Change the conform-action in 'police' or 'police flow' command to make both actions the same, or remove one of two commands.
Error Message%QM-2-ERROR : [chars] [chars]:[dec]
Explanation A software error has occurred.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-MAX_ACLS_EXCEED : The number of [chars] ACLs in a service-policy for [chars] exceeds 255
Explanation This interface does not support more than 255 ACLs per service policy, per protocol.
Recommended Action Reduce the total number of classes (per protocol) in the service policy.
Error Message%QM-2-MERGE_ERROR : ACL merge error for Interface [chars] in [chars] direction status [dec]
Explanation The ACL merge failed before programming ACLs into the TCAM.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-MICROFLOW_FAILURE : Interface %s microflow QoS will not comply with policymap in %s direction(s)
Explanation QoS will not be applied to traffic for this interface due to microflow policer resource contention.
Recommended Action There are too many configured microflow policers fit in the hardware Threshold RAM. Try to specify the same microlow policing parameters (rate+burst) across multiple classes/interfaces in order to reduce the policer resource contention.
Error Message%QM-2-NO_AGGREG_PLC : Hardware aggregate policer resources exceeded
Explanation The hardware doesn't have the capacity to handle aggregate policers required by configuration.
Recommended Action Reduce the total number of aggregate policers required by all service-policies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers
Error Message%QM-2-NO_AGGREG_PLC_IF : Out of hardware aggregate policers (policy %s, class %s, interface %s
Explanation The hardware doesn't have the capacity to handle aggregate policers required by the service-policy class for the indicated interface.
Recommended Action Reduce the total number of aggregate policers required by all service-policies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers
Error Message%QM-2-NO_FLOW_PLC : Hardware microflow policer resources exceeded
Explanation The hardware doesn't have the capacity to handle microflow policers required by the policy-map.
Recommended Action Adjust microflow policing rate/burst parameters so that the total number of different rate/burst combinations in the device is reduced.
Error Message%QM-2-PLC_ATTACH_REJECT : Command rejected: (policy [chars] interface [chars] dir [chars]) police/trust and set commands present in same traffic class
Explanation One of two conditions cause this error: –A policy map containing a traffic class with both the set and police command, or both the set and trust commands, is attached to an unsupported interface,
Explanation –A policy that is attached to an interface is being modified in an unsupported manner.
Recommended Action Remove either the set and police or set and trust commands from the same traffic class. If a policy that was attached an unsupported interface was modified, no action is required because the command is rejected.
Error Message%QM-2-PLC_ATTACH_REJECT_ARP_UFLOW : Command rejected: (policy-map %s class %s interface %s dir %s) flow policer is not supported for traffic classes matching ARP ACL.
Explanation In a policymap, flow policer is not supported if the traffic class is matching ARP ACL.
Recommended Action Remove the flow policer from traffic class matching ARP ACL and re-attch the policy (or) Change the traffic class to match non-ARP ACL and configure flow policer.
Error Message%QM-2-POLARIS_POLICY_REINSTALL : Policy [chars] on [chars] is reinstalled.
Explanation The Polaris Version 1 card does not support egress QoS for multicast traffic.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-POLARIS_POLICY_REMOVE : Policy [chars] on [chars] is removed.
Explanation The Polaris Version 1 card does not support egress QoS for multicast traffic.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-QM_MODE_1 : QoS on vlan/etherchannel interfaces or egress side is removed.
Explanation The Polaris Version 1 card does not support egress QoS for multicast traffic.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-QM_MODE_2 : QoS on vlan/etherchannel interfaces or egress side is reinstalled.
Explanation The Polaris Version 2 mode has full QoS support.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-SEQUENCE : Error in internal messaging - lost message (i/f %s, dir %s, type %d)
Explanation Software error may have effected programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-2-SET_IP_AND_MPLS : Hardware does not support 'set mpls exp' and 'set precedence | dscp' together
Explanation Hardware does not support 'set mpls exp' and 'set precedence | dscp' together
Recommended Action Chose between 'set mpls exp' and 'set precedence | dscp'
Error Message%QM-2-TCAM_BAD_LOU : Bad TCAM LOU operation in ACL
Explanation Software error caused failure in programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-2-TCAM_ENTRIES_EXCEEDED : ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, [dec] ACEs for interface [chars] in [chars] direction
Explanation The ACL merge was halted. The results of the ACL merge has caused the number of ACEs to exceed the TCAM capacity, or zero ACEs were present.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-2-TCAM_ERROR : TCAM programming error %d
Explanation Software error caused failure in programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-2-TCAM_MEMORY : NMP processor memory low
Explanation Inadequate memory caused failure in programming ACLs into the TCAM.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%QM-3-ERROR : [chars] [chars]:[dec]
Explanation A software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%QM-3-ERROR_STAT : %s stat:%d in %s:%d
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QM-4-ACTION_NOT_SUPPORTED : Action is not supported in policymap [chars]
Explanation An action other than entering the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation.
Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.
Error Message%QM-4-AGGREG_PLC_IGNORED : 'police' command ignored in presence of 'police aggregate %s'
Explanation If both 'police' and 'police aggregate' are specified as policy actions for the same class, 'police' is ignored as long as aggregate has been defined via 'mls qos aggregate'.
Recommended Action Do not specify both 'police' and 'police aggregate' in same class.
Error Message%QM-4-AGG_POL_EXCEEDED : QoS Hardware Resources Exceeded : Out of Aggregate policers
Explanation Only a limited number of aggregate policers can be supported. On Earl7 based switches, this limit is 1023.
Recommended Action Try to aggregate policers if possible.
Error Message%QM-4-CLASS_NOT_SUPPORTED : Classification is not supported in classmap [chars]
Explanation Either an unsupported match class-map configuration command was configured in a policy map and attached to an egress interface or more than one match command was configured. This is caused by a hardware limitation.
Recommended Action Reconfigure the class map or the policy map. Use the match ip dscp class-map configuration command only in a policy map that is attached to an egress interface. Only one match per class map is supported.
Error Message%QM-4-HARDWARE_NOT_SUPPORTED : Hardware limitation has reached for policymap [chars]
Explanation The policy-map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management (sdm) template.
Recommended Action Reconfigure the class map or the policy map and reduce the number of QoS ACLs.
Error Message%QM-4-IDB_MODE_CHANGE_SERV_POLICY : Interface %s service-policy is not preserved on transition to/from switchport
Explanation The service-policy applied to the interface before transition includes features which cannot be applied to the interface after the transition. Since a service-policy is applied atomically, none of the features in its policy-map are applied after the transition.
Recommended Action After the transition, install a different service-policy on the interface, which only includes applicable features.
Error Message%QM-4-MATCH_NOT_SUPPORTED : Match type is not supported in classmap [chars]
Explanation An invalid match type was specified. The match types that are supported are "match ACL", "match ip dscp" and "match ip precedence".
Recommended Action Reconfigure the class map and use only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map.
Error Message%QM-4-MFLOW_POL_EXCEEDED : QoS Hardware Resources Exceeded : Out of Micro flow policers
Explanation Only a limited number of micro-flow policers can be supported. On Earl7 based switches, this limit is 63.
Recommended Action No Action.
Error Message%QM-4-NOT_SUPPORTED : Action '[chars]' is not supported for a policymap attached to output side.
Explanation A set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take affect. This is a hardware limitation.
Recommended Action Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy map actions are supported only on ingress interfaces.
Error Message%QM-4-NO_IP_DSCP_RW_SLOT_IGNORED : 'no mls qos rewrite ip dscp slot [dec]' will not be effective. Disable the ip-dscp-rewrite on Supervisor (slot [chars]) to avoid ip-dscp-rewrite of packets coming in on non-DFC linecards.
Explanation If a non-PFC or non-DFC slot is provided in the no mls qos rewrite ip dscp command, the command will not be effective for the slot. If ip-dscp-rewrite must be disabled for packets coming in on a non-DFC line card, the Active Supervisor slot must be provided in the command.
Recommended Action To disable dscp-rewrite of packets coming in on a non-DFC line card, disable the dscp-rewrite on the Active Supervisor slot.
Error Message%QM-4-POLICER_NOT_SUPPORTED : Number of policers has exceeded hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than are supported.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of policers.
Error Message%QM-4-POLICING_RATE_NOT_SUPPORTED : Policer configuration has exceeded hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured a larger policing rate or burst size in a policy map (by using the police or police aggregate policy-map class configuration command) than are supported.
Recommended Action Reconfigure the class map or the policy map, and reduce the policing rate or burst size.
Error Message%QM-4-TCAM_CAPMAP : Interface %s hardware TCAM LOU usage capability exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface.
Recommended Action The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs.
Error Message%QM-4-TCAM_ENTRY : Hardware TCAM entry capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle all of the configured ACLs.
Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%QM-4-TCAM_LABEL : Hardware TCAM label capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of interfaces configured with ACLs.
Recommended Action The hardware TCAM can only handle 500 interfaces configured with ACLs. Deconfigure ACLs from some of the interfaces.
Error Message%QM-4-TCAM_LOU : Hardware TCAM LOU capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs.
Recommended Action The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs.
Error Message%QM-4-UNEXPECTED_INTERNAL_QOS_CONDITION : Unexpected internal QoS condition.
Explanation This message means that an unexpected internal QoS condition has occurred. QoS debug might be enabled to obtain more information in case the condition recurs.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QM-4-WARNING : [chars] [chars]:[dec]
Explanation This message provides information about a software warning.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, 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%QM-6-EOM_FORCE_TRUSTED : EoMPLS on %s caused install of 'trust cos' state
Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the 'no trust' state is auto-replaced by 'trust cos'.
Recommended Action Remove all EoMPLS configuration from the interface to restore 'no trust'
Error Message%QM-6-EOM_RESTORE_UNTRUSTED : The 'no trust' state is restored on EoMPLS removal from %s
Explanation If EoMPLS is de-configured on the interface and all its subinterfaces, the configured 'no trust' state is restored'.
Recommended Action No action needed
Error Message%QM-6-EOM_TRUST_NOT_INSTALLED : 'no trust' command is not installed on %s in presence of EoMPLS
Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the 'no trust' command is not installed.
Recommended Action Remove all EoMPLS configuration from the interface
Error Message%QM-6-IOS_AND_PS_FEATURE : %s action cannot be present in classmap %s of policymap %s because this service-policy cannot be executed in Cat6K HW due to the presence of filters which require packets to be processed in IOS SW
Explanation NBAR is required for the match protocol commands used. NBAR exists only in SW. Therefore HW specific actions cannot be supported
Recommended Action Remove either the HW specific command(s) or the match protocol criteria in classmap
Error Message%QM-6-NBAR_DISABLED : Packets will not be software switched.
Explanation NBAR is disabled, now traffic will not be punted to RP.
Recommended Action No action needed
Error Message%QM-6-NBAR_ENABLED : Packets will be software switched.
Explanation NBAR is enabled, now all the traffic will be punted to the RP.
Recommended Action No action needed
Error Message%QM-6-SET_AND_POLICE : 'set' and 'police' commands cannot co-exist in classmap %s of policymap %s
Explanation set' and 'police' commands cannot co-exist in a classmap for a QM supported interface
Recommended Action Chose between one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command
Error Message%QM-6-SET_AND_TRUST : 'set' and 'trust' commands cannot co-exist in classmap %s of policymap %s
Explanation set' and 'trust' commands cannot co-exist in a classmap for a QM supported interface
Recommended Action Chose between one of the commands
Error Message%QM-6-SHAREDAG_AND_POLICE : 'police aggregate' and regular 'police' commands cannot co-exist in classmap %s of policymap %s
Explanation set' and 'police' commands cannot co-exist in a classmap for a QM supported interface
Recommended Action Chose between one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command
Error Message%QM-6-UNDEF_SHR_AG : shared aggregate policer %s used in classmap %s of policymap %s is not defined
Explanation Shared aggregate policers have to be created first using the mls qos aggregate command before being used in a policymaps
Recommended Action Either define the shaed aggregate policer or dont use it in the policymap
Error Message%QNQ-6-NATIVE_VLAN_TAGGING : Please enable the native VLAN tagging feature for proper functioning of the Q-in-Q service.
Explanation QnQ may not function properly for packets in the native vlan if native-vlan-tagging is not enabled.
Recommended Action Enable native VLAN tagging by entering the vlan dot1q tag native command.
QOS Messages
Error Message%QOS-3-ATLEAST_ONE_FAILOVER_ERR : Fail-over of dynamic interface [chars] failed
Explanation Dynamic interface has changed its route out of different physical interface and queueing cannot set-up data-sructures for that new physical interface.
Recommended Action One possibility is that new physical interface already has service-policy or some other dynamic interface already has queueing data-structures associated with that physical interface and conjuction of such service-policies are not allowed. Remove one or the other service-policy in that case. If that is not the case, then 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-BADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-BLT_INDEX : Failed to assign index for target/policy/class/action %u/%u/%u/%s
Explanation The configuration of queuing has resulted in the failure to generate an internal unique identifier which represents the queue. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-BURST_BC_ERR : Burst Bc increased to [dec] bytes
Explanation If Burst BC is less than the default burst size then Burst Bc is increased to AF_DEAFULT_BURST.
Recommended Action This is informational message. No action is required.
Error Message%QOS-3-CFGERR : interface [chars]: configuration failed
Explanation Available memory is insufficient for configuring the feature. It is not possible to configure the issued command (feature) unless the required amount of memory is available.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%QOS-3-COEX_NOT_ALLWD : queueing policy at session cannot co-exist with servicepolicy at sub-interface/pvc
Explanation There already might be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session.
Recommended Action Remove the policy attached to the sub-interface or pvc before attaching a new policy to a session.
Error Message%QOS-3-COLLISION_COUNT : %s mismatch, count %u
Explanation The specified type of collision has detected that although there are no collisions present the count of such indicates otherwise. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-COLLISION_DELETE : %s unable to remove index %08X
Explanation The specified type of collision is unable to removed the specified index. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-COLLISION_TYPE : Type %u is invalid for collision %s
Explanation The specified type of collision is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-DETACH : Failed to detach %s %s service policy
Explanation The specified type of service policy has failed to detach itself from the attachment point indicated. The service policy will remain attached although repeated attempts to remove such should fail in a similar manner.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show policy-map [type] )
Error Message%QOS-3-HA_BULK_SYNC : %s Failure in completing bulk sync
Explanation QoS configuration can't be synced to the standby
Recommended Action Contact your Cisco technical support representative.
Error Message%QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT : [chars] Failure in completing bulk sync before timeout
Explanation QoS configuration canot be synchronized to the standby.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HA_COLLISION_INVALID : Received collision table of type %u
Explanation The specified type of collision is an invalid value which indicates that the message received on the standby RP contains erroneous data. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HA_COLLISION_SIZE : Received %s message, total/unit %u/%u %s
Explanation The specified type of collision table has been determined to contain a discrepancy between the total message size and the individual table unit that is being decoded on the standby RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HA_COLLISION_STRING : Received %s message, length %u for string %s
Explanation The specified type of collision table contains an individual unit within the message which has an incorrectly encoded string which is used to represent the collision which is being synced from the active RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HA_GET_ARG_NUM : %s Failure in getting event identification
Explanation QoS configuration can't be synced to the standby
Recommended Action Contact your Cisco technical support representative.
Error Message%QOS-3-HA_MISMATCH : Bulk sync failed for %s collisions, space available %u, buffer %u
Explanation A synchronization attempt between the active and standby RP peers has failed due to the detection of a mismatch in the source and destination sizes of a buffer used in the transport of the collision information to the standby RP. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HQFNOPAK : interface [chars]: pak_reparent failed
Explanation Pak_reparent has been invoked and failed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HQFPAKREQUEUE : interface [chars]: pak_requeue_head has been invoked
Explanation pak_requeue_head() function has been invoked on a packet. One or more packets have been dropped. This is not the normal mode of operation.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HQFPOOLERR : interface %s: failed to allocate hqf particle
Explanation The HQF particle pool is empty. It cannot process a router generated packet
Recommended Action Collect show buffer and show policy interface output and send to technical support
Error Message%QOS-3-HQF_FEA_API_FAIL : Feature processing API returned NULL pak with INCOMPLETE flag
Explanation The HQF calls the API that processes the feature to get the next packet from the feature, for example, the Frame-relay fragmentation. The API returns conflicting flags with NULL packet.
Recommended Action Check if the system resources, for example the packet buffers, are exhausted. 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-HQF_QID_ERR : Maximum number of QoS queues ([dec]) reached.
Explanation The system has run out of QoS queue identifiers and cannot allocate any more until existing queues are freed.
Recommended Action Remove the existing QoS configurations to free up more queue identifiers. For example, remove the existing QoS service-policy configurations or modify policy-map templates to have fewer queueing actions.
Error Message%QOS-3-INDEX_DELETE : %s unable to remove index %08X
Explanation The specified entity is unable to removed the specified index. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-INDEX_EXISTS : %s attempt to add index %08X %s
Explanation The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show cce cp id [collisions])
Error Message%QOS-3-INVALID_POLICY : queueing policy at session can co-exist only with class-default shaping policy at sub-interface/pvc
Explanation There already might be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session.
Recommended Action Make sub-interface/pvc based policy just one level policy with only class-default.
Error Message%QOS-3-ISSU_COMP : Failed to exchange capability with peer
Explanation The attempt to negotiate version capabilities and the exhange of the peer support has failed. This indicates that QoS is unable to support a redundant operation with the standby RP peer.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-MAIN_SUB_POLICY : FR fragmentation is not supported with interface or sub-interface based policies
Explanation On Cisco 7500 series routers, Frame Relay fragmentation is not supported when service policies are configured on the interface or subinterfaces.
Recommended Action Remove the service policy configuration under the interface or subinterfaces and reissue either the class command in Frame Relay DLCI interface configuration mode or the frame-relay fragment command in map-class configuration mode.
Error Message%QOS-3-NOCAPID : Failed to allocate QoS capability ID.
Explanation No more QoS capability IDs are available.
Recommended Action Contact your Cisco technical support representative. The Cisco IOS software image has to be changed so that it can support more QoS capability IDs.
Error Message%QOS-3-SA_SESSION_FAILOVER_ERR : Fail-over of dynamic SA session to interface [chars] failed
Explanation Dynamic SA session has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface.
Recommended Action One possibility is that new physical interface already has service-policy with queueing configured. Remove the other service-policy in that case. If that is not the case then contact technical support.
Error Message%QOS-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure failed.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-TARGET_INDEX : %s %s service policy attachment failed to assign index
Explanation The configuration of a service policy has resulted in the failure to generate an internal unique identifier which represents the attachment point (target) of the associated policy map. This is an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-UNASSIGNED : A %s event resulted in an (un)assigned index for %s %s
Explanation The configuration of either the addition or removal of the specified entity has resulted in the failure to either assign or remove a previously assigned index from such. This is an internal software error and indicates an out of sync condition if operating in a redundant manner
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-3-VTEMP_MAIN_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the main interface before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-VTEMP_MLP_ERR : A service policy cannot be attached to a PPP virtual-access interface when ppp multilink is enabled. A service policy can be attached to a ppp multilink bundle interface only.
Explanation A service policy attached to a virtual-template is usually copied to associated virtual-access interfaces. However, if such a virtual-access interface joins a multilink ppp bundle, the policy is not attached to the virtual-access interface.
Recommended Action This is an informational message. No action is required.
Error Message%QOS-3-VTEMP_SUB_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the subinterface before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-VTEMP_VC_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the vc or pvc before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-XDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec]
Explanation An internal software error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-4-FO_IN_USE : Releasing feature object with reference count [dec]
Explanation This is an internal software error. A QoS policy feature object has a stale reference.
Recommended Action If the message recurs, isolate the traffic conditions which trigger the message and contact technical support. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show tech-support and show policy-map interface command and your pertinent troubleshooting logs.
Error Message%QOS-4-INVALIDBW : interface %s: Not enough bandwidth to configure service-policy
Explanation The issued interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action Reconfigure the service policy for the new issued bandwidth on the interface, or increase the issued interface bandwidth to the required value.
Error Message%QOS-4-LC_STATS_MSG_DROPPED : QoS statistics update message dropped due to [chars]
Explanation Changes to QoS counters are sent periodically from line cards to the route processor. One of these statistics updatemessages was discarded because it was inconsistent or because the route processor ran out of message buffers.The packet and bytes counters for a single service-policy might be underreported by show commands and SNMP queries.
Recommended Action This is an informational message only. No action is required.
Error Message%QOS-4-TUN_MOV_FAIL : Queueing hierarchy move failed on [chars], suspending policy.
Explanation An attempt to move a QoS queueing hierarchy on a tunnel failed. The move might have been caused by a change in the forwarding path.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-5-POLICY_DETACHED : service policy %s detached: as it cannot be supported.
Explanation Platform validation of modification to service policy failed due to one or more of the following reasons: modified classification filters are not supported, or modified actions not supported, or with modified target attributes (such as interface bandwidth) some of the action(s) cannot be supported.
Recommended Action Review the modifications to: service policy and target attributes. Try to remove unsupported classification filters, or remove unsupported actions, or restore target attributes, then try to re-attach the service policy.
Error Message%QOS-6-ACTIVATE : Activating service policy [chars] on [chars] in [chars] direction
Explanation The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action No action is required.
Error Message%QOS-6-ACTIVATE_NOHW : Activating service policy [chars] in [chars] direction
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%QOS-6-COLLISION_MAX : Maximum number of collision entries, %u, reached
Explanation The system limit on the number of collision entries used in assigning unique identifiers for policy and class maps et al. has been reached. This indicates that no further configuration of entities which require additional generation of a unique identifier will be possible.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-6-EXTENDED_BURST_CHANGED_WARN : Illegal extended burst size; it is increased to [int]
Explanation The configured extended burst size is illegal because it is less than the burst rate. It has been increased to an amount equal to the rate, depending on the MTU of the interface.
Recommended Action Informational message only. No action is required.
Error Message%QOS-6-INACTIVETUNNEL_INACTIVEQUEUING : Queuing stats on tunnel is shown only when tunnel is active
Explanation For policy enabled on a tunnel, queuing features specific statistics are shown only when tunnel is active.
Recommended Action If queuing features infomation is not shown, tunnel must be down. Bring up tunnel.
Error Message%QOS-6-NORMAL_BURST_CHANGED_WARN : Illegal normal burst size; it is increased to [int]
Explanation The configured extended burst size is illegal because it is less than the burst rate. It has been increased to an amount equal to the rate, depending on the MTU of the interface.
Recommended Action Informational message only. No action is required.
Error Message%QOS-6-POLICY_INST_FAILED : Service policy installation failed
Explanation The service policy could not be installed.
Recommended Action This is an informational message only. No action is required.
Error Message%QOS-6-RELOAD : %s, reloading %s
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-6-SUSPEND : Suspending service policy [chars] on [chars] in [chars] direction
Explanation The interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action No action is required.
Error Message%QOS-6-TUN_INSTALL : Installing suspended policy on [chars].
Explanation The system is attempting to install a service policy on a tunnel that is in a suspended state. This is caused either by tunnel address change or forwarding path change.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOS-6-WAVL : [chars] is not successful
Explanation The specified classmap or policymap insertion or removal was notsucccessful. This is an internal software error.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
QOS_CLI_DEPRECATE Messages
Error Message%QOS_CLI_DEPRECATE-4-CUSTOM_QUEUE : Custom Queue list on interface has been deprecated. Use equivalent MQC bandwidth command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface custom queue list command has been deprecated as per the Modular QoS CLI (MQC) convention.
Recommended Action Configure a policy with the bandwidth command and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FAIR_QUEUE : Fair Queue on interface has been deprecated. Use equivalent MQC fair-queue command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface custom fair-queue command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the fair-queue command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_ADAPTIVE_SHAPE : frame relay adaptive-shaping has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface shape command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the shape command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_CBS : Frame relay bc command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay bc command has been deprecated as per the MQC convention.
Recommended Action Unavailable
Error Message%QOS_CLI_DEPRECATE-4-FR_CIR : Frame relay cir command has been deprecated. Use equivalent MQC priority command
Explanation The frame-relay cir command has been deprecated as per the MQC convention.
Recommended Action Unavailable
Error Message%QOS_CLI_DEPRECATE-4-FR_EBS : Frame relay be command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay be command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the MQC-equivalent of the frame-relay be command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FRFECN_ADAPT : frame relay fecn-adapt command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay fecn-adapt command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the MQC-equivalent of the frame-relay fecn-adapt command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_ADAPTIVE_SHAPE_BECN : frame relay adaptive-shaping becn has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface shape command has been deprecated by the Modular QoS CLI (MQC) commands.
Recommended Action Configure a policy with the shape command and attach the policy to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_ADAPTIVE_SHAPE_FORESIGHT : frame relay adaptive-shaping foresight has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface shape command has been deprecated by the Modular QoS CLI (MQC) commands.
Recommended Action Configure a policy with the shape command and attach the policy to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_ADAPTIVE_SHAPE_INTERFACE_CONGESTION : frame relay adaptive-shaping interface congestion has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface shape command has been deprecated by the Modular QoS CLI (MQC) commands.
Recommended Action Configure a policy with the shape command and attach the policy to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_IF_QUEUE : Frame Relay interface-queue has been deprecated. Use equivalent MQC queueing command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface queue command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the queueing command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_IP_RTP_PRIO : frame relay ip rtp priority has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay interface ip rtp priority command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the priority command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_QOS_AUTOSENSE : Frame Relay qos-autosense has been deprecated. Since it requires FRTS to be configured, there is no equivalent for this command in MQC. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface traffic shape command has been deprecated as per the MQC convention.
Recommended Action Unavailable
Error Message%QOS_CLI_DEPRECATE-4-FR_THRESH_DE : frame relay congestion threshold de command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay congestion threshold de command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the MQC-equivalent of the frame-relay congestion threshold de command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_THRESH_ECN : frame relay congestion threshold ecn command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay congestion threshold ecn command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the MQC-equivalent of the frame-relay congestion threshold ecn command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_TRAFFIC_RATE : Frame Relay traffic-rate has been deprecated. Use equivalent MQC shape command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface traffic shape command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the traffic-shape command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FR_TRAFFIC_SHAPE : Frame Relay traffic-shaping has been deprecated. Use equivalent MQC traffic-shape command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface traffic shaping command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the traffic-shape command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FRVCQ_CUSTOM : frame relay custom-queue-list command has been deprecated. Use equivalent MQC bandwidth command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay custom-queue command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the bandwidth command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FRVCQ_FAIR : frame relay fair-queue command has been deprecated. Use equivalent MQC fair-queue command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay fair-queue command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the fair-queue command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-FRVCQ_PRIORITY : frame relay priority-group command has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The frame-relay priority-group command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the priority command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-IP_RTP_PRIO : ip rtp priority command on interface has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface ip rtp priority command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the priority command, and attach it to the interface.
Error Message
%QOS_CLI_DEPRECATE-4-MAX_RESERVED_BW: max-reserved-bandwidth on interface has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands DeprecationExplanation The max-reserved-bandwidth command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the bandwidth command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-PRIORITY_LIST: priority-list global config mode CLI has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The priority-list command used in global configuration mode has been deprecated as per the Modular QoS CLI (MQC) convention.
Recommended Action Configure a policy with an equivalent MQC command and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-PRIORITY_QUEUE : Priority Queue on interface has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface priority-group command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the priority command, and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-QUEUE_LIST: queue-list global config mode CLI has been deprecated. Use equivalent MQC priority command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The queue-list command used in global configuration mode has been deprecated as per the Modular QoS CLI (MQC) convention.
Recommended Action Configure a policy with an equivalent MQC command and attach it to the interface.
Error Message%QOS_CLI_DEPRECATE-4-RANDOM_DETECT : Random detect on interface has been deprecated. Use equivalent MQC random-detect command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface random detect command has been deprecated as per the MQC convention.
Recommended Action Unavailable
Error Message%QOS_CLI_DEPRECATE-4-RANDOM_DETECT_GROUP : Random detect group command has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The random detect group command has been deprecated as per the MQC convention.
Recommended Action Unavailable
Error Message%QOS_CLI_DEPRECATE-4-TRAFFIC_SHAPE : Traffic shape on interface has been deprecated. Use equivalent MQC traffic-shape command. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
Explanation The interface traffic shape command has been deprecated as per the MQC convention.
Recommended Action Configure a policy with the traffic-shape command, and attach it to the interface.
QOSMGR Messages
Error Message%QOSMGR-3-ACL_CLASS_NOT_ALLOWED_FOR_OUTPUT_POLICY : Configuration Failed. Can not have ACL based classification in a class-map within an output policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ACTION_NOT_SUPPORTED_FOR_INPUT_POLICY : Configuration failed. The configured action is not supported in an input policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-AGG_POLICER_IN_USE_BY_POLICYMAP : Configuration failed. Cannot allocate aggregate policer '%s' used by another policy-map '%s'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-AGG_POLICE_NOT_EXIST : Configuration failed. Aggregate policer '%s' does not exist
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-BW_REMAINING_NOT_ALLOWED : Configuration failed. 'bandwidth remaining percent' can be configured only with strict priority in another class
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-BW_REMAINING_NOT_ALLOWED_WITH_BW : Configuration failed. 'bandwidth remaining percent' and 'bandwidth' can not be configured together
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CANNOT_ALLOC_POL_FOR_PLCMAP : Failed to allocate policer for policy-map %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CANNOT_ERR_DISABLE_DUE_TO_INTERNAL_ERR : Can not put port in err-disable due to an internal error
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CANNOT_HAVE_DIFFERENT_EXCEED_ACTION_FOR_SAME_CLASS : Configuration failed. Can not have different exceed-action actions for the same class
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CANNOT_HAVE_MARKING_FOR_BOTH_CONFORM_AND_EXCEED : Configuration failed. Can not have marking actions as both police conform AND exceed actions
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CLSMAP_IN_OUTPUT_PLCMAP_NOT_SAME : Configuration failed. Class-maps in policy-map %s are not the same as other attached output policies.All output policies must have the same class-maps.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_BW_EXCEED_AVAIL_BW : Configuration failed. The configured bandwidth %d in class %s is greater than available bandwidth %d
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_BW_EXCEED_AVAIL_BW_2_PARAM : Configuration failed. Configured bandwidth %d is greater than available bandwidth %d
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_POLICE_CLASS_RATE_EXCEED_AVAIL_BW : Configuration failed. The configured police class rate %d of class %s, policy-map %s exceeds available bandwidth %d.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_RATE_NOT_ACHIEVABLE_1_PARAM : Configuration failed. The configured rate is not achievable in hw within 1%% of configuration. Closest value is: %d bps
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_RATE_NOT_ACHIEVABLE_2_PARAM_ABS_ABS : Configuration failed. The configured rate is not achievable in hw within 1%% of configuration. Closest value(s) are: %d, %d bps
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_RATE_NOT_ACHIEVABLE_2_PARAM_PCT_ABS : Configuration failed. The configured rate is not achievable in hw within 1%% of configuration. Closest value is: %d %% (%d bps)
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_RATE_NOT_ACHIEVABLE_4_PARAM : Configuration failed. The configured rate is not achievable in hw within 1%% of configuration. Closest value(s) are: %d %% (%d bps), %d %% (%d bps)
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFIG_SHAPE_CLASS_RATE_EXCEED_AVAIL_BW : Configuration failed. The configured shape class rate %d of class %s, policy-map %s exceeds available bandwidth %d.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFLICTING_CONFORM_ACTION : Configuration failed. Conflicting conform-actions
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-CONFLICTING_EXCEED_ACTION : Configuration failed. Conflicting exceed-actions
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACHED_OUTPUT_POL_PRIOR_ADDING_CLASS : Configuration failed. Please detach the output policy %s prior to adding the class
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACH_OUTPUT_POLICYMAP_BEFORE_ADDING_ACTION : Configuration failed. Please detach policy %s prior to adding any action.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACH_OUTPUT_POLICYMAP_BEFORE_ADDING_CHILDPOLICY : Configuration failed. Please detach output policy %s prior to adding a child policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACH_OUTPUT_POLICYMAP_BEFORE_REMOVING_ACTION : Please detach output policy %s from the interface prior to removing this action.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACH_POL_BEFORE_REMOVING_CHILDPLC : Configuration failed. Please detach output policy %s prior to removing a child policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-DETACH_POL_BEFORE_REMOVING_CLASS : Please detach output policy %s from the interface prior to removing the class.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-FAIL_GET_AGG_POLICER : Failed to get agg policer %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-FAIL_TO_MATCH_QOS_LABEL : Failed to match to QoS labels
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-FAIL_TO_UPDATE_TX_QOS_LABEL : Failed to update TX QoS label to queue mapping
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-FAIL_UPDATE_HARDWARE_FOR_TBLMAP : Failed to update hardware for Table-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-FEATURE_NOT_FOUND : Cannot find feature for [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-FILTERTYPE_INVALID : Internal Error Invalid Policy filtertype [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-HW_PROGRAM_POL_RATE_FAIL : Error in programming the configured police rate in policy %s, class %s.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-HW_PROGRAM_PORT_SHAPE_FAIL : Error in programming HW for port shape for interface %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-HW_PROGRAM_Q_SHAPE_FAIL : Error in programming HW for queue shape in policy %s, class %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-HW_PROGRAM_SHAPE_CLASS_FAIL : Error in programming HW for shape class for policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-HW_PROGRAM_WRITE_PORT_POLICER_FAIL : Failed to program port policer
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INCOMPATIBLE_ACTION_WITH_BANDWIDTH : Configuration failed. 'bandwidth' can be configured in the same class only with 'queue-limit'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INCOMPATIBLE_ACTION_WITH_PRIORITY : Configuration failed. 'priority' can be configured in the same class only with 'queue-limit' and/or 'police'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INCOMPATIBLE_ACTION_WITH_SHAPE : Configuration failed. 'shape' can be configured in the same class only with 'queue-limit'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INITIALIZING_INTERNAL_LINK_FAIL : Failed to initialize internal link
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ()
Error Message%QOSMGR-3-INPUT_POL_CANNOT_BE_HIERARCHICAL : Configuration failed. Input policy cannot be hierarchical.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INTERNAL_TABLEMAP_NOT_ALLOWED : Processing failed. Please use another table-map name. This table-map is being used for internal processing
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INVALID_CLASSIFICATION_CRITERIA_FOR_WTD : Configuration failed. All queue-limit qualifier criteria must be represented within the associated class-map classification criteria
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INVALID_MATCH_IP_TYPE : Invalid match_ip_type
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-INVALID_POL_DIR : Invalid Policy direction
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-MATCH_ACL_AND_NONACL_NOT_ALLOWED : Configuration Failed. Can not have ACL and non-ACL classification in the same class-map within an input policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-MATCH_DSCP_AND_PRED_NOT_ALLOWED : Configuration Failed. Can not have Precedence AND DSCP IP classification in the same class-map within a policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-MAX_UNIQUE_OUTPUT_POLICYMAP_EXCEEDED : Configuration failed. Maximum number of allowable unique output policy-maps exceeded.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-MERGE_RES_COUNT : Internal Error Invalid count
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-MULTIPLE_MATCH_STATEMENT_FOR_MATCH_ALL : Configuration failed. 'match-all' classification with multiple match statements is not allowed in policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-NEW_Q_LIMIT_NOT_MATCH_POLICY : Configuration failed. The new configured queue-limit in policy %s is not consistent with the attached policy
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-NO_ACTION_ALLOWED_FOR_CLSDFT_FOR_OUT_POLICY : Configuration failed. No action is allowed in class-default for output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-NO_CLASS_IN_POLICY : Configuration failed. There's no class in the policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-NO_POLICER_QOSLABEL : Creating port Class Label Failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-NO_VMR_QOSLABEL : qm_generate_vmrs have no qos label
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-NULL_POLICER : Internal Error Invalid Policer
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-NUM_Q_LIMIT_EXCEED_MAX : Configuration failed. The number of unique queue-limit thresholds including default %d exceeds maximum of 3.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONE_UNIQUE_POL_COS_MARKDOWN_ALLOWED : Configuration failed. Only 1 unique policed-cos mark-down table-map allowed onthe switch. Another policed-cos mark-down table-map is attached to a port.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONE_UNIQUE_POL_DSCP_PRED_MARKDOWN_ALLOWED : Configuration failed. Only 1 unique policed-dscp/prec mark-down table-map allowed onthe switch. Another policed-dscp/prec mark-down table-map is attached to a port.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_16_QOS_GROUP_VALUES_ARE_SUPPORTED : Configuration failed. Only 16 levels of qos-groups are supported.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_BW_REMAINING_ALLOWED : Configuration failed. Strict priority can co-exist only with 'bandwidth remaining percent' in any other class
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_CLASS_DEFAULT_ALLOWED_FOR_TOP_OUTPUT : Configuration failed. Only class-default is allowed in top level of an output policy
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_CONFORM_ACTION_TRANSMIT_ALLOWED_FOR_CONTROL_PLANE : Configuration failed. Only 'conform-action transmit' allowed in policy-map attached to 'control-plane'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_EXCEED_ACTION_DROP_ALLOWED_FOR_CONTROL_PLANE : Configuration failed. Only 'exceed-action drop' allowed in policy-map attached to 'control-plane'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-ONLY_SHAPE_ACTION_ALLOWED_FOR_TOP_OUTPUT : Configuration failed. Only shaping action is allowed in top level of output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-OUTPUT_PLCMAP_CAN_HAVE_MAX_THREE_CLSMAPS : Configuration failed. Only 3 unique class-maps excluding class-default can be configured for all output policy-maps.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-OUTPUT_PLCMAP_HAS_INVALID_NUM_CLASS_MAP : Configuration failed. policy-map %s has an invalid number of class-maps. All output policies must have same number of class-maps.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICER_NOT_ALLOWED_WITHOUT_PRIORITY : Configuration failed. 'police' can not be configured without 'priority' in the same class, for output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICER_PER_PORT_EXCEEDED : Policers per port %s limit exceeded in hardware
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICER_RES_COUNT : Internal Error Invalid Policer count
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-POLICE_ACTION_MISMATCH : Configuration failed. Police action cannot be configured along with the other configured action
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICE_ACTION_NOT_ALLOWED_FOR_CLASS_DEFAULT : Configuration failed. 'police' action cannot be configured for class-default
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICE_AGG_ACTION_MISMATCH : Configuration failed. 'police aggregate' action cannot be configured along with any other action
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICE_AGG_NOT_ALLOWED_FOR_CLASS_DEFAULT : Configuration failed. 'police aggregate' action cannot be configured for class-default
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICYMAP_NOT_ALLOWED_FOR_ETHERCHANNEL_INT : Configuration failed. Policymap not supported on ether-channel interface
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICYMAP_NOT_ALLOWED_FOR_VIRTUAL_INT : Configuration failed. Policymap is not supported on virtual interfaces
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICYMAP_NOT_ALLOWED_FOR_VLAN_INT : Configuration failed. Policymap not supported on vlan-interface
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICYMAP_NOT_FOUND : Cannot find policymap for [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-POLICYMAP_NOT_SUPPORTED_ON_CONTROL_PLANE : Configuration failed. Output policy-map is not supported on 'control-plane'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-POLICY_MAP_ALREADY_ATTACHED : Configuration failed. Policy map %s is already attached
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-PORT_SHAPE_RATE_EXCEED_AVAIL_BW : Configuration failed. The configured port shape rate exceeds available bandwidth %d
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-PRI_SHOULD_BE_IN_SAME_CLASS : Configuration failed. Priority is required to be associated with the same class %s, as in an existing policy.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-QOS_GROUP_NOT_ALLOWED_FOR_INPUT : Configuration Failed. 'match qos-group' not allowed in input policy-map
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-QUEUELIMIT_NOT_ALLOWED_WITHOUT_SCHEDULING_ACTION : Configuration failed. 'queue-limit' can not be configured without 'bandwidth', 'shape' or 'priority' in the same class
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-QUEUE_PTR_ERROR : queue pointers out of order [hex] [hex] [hex] [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-Q_LIMIT_NOT_THE_SAME_TYPE : Configuration failed. Queue-limit for policymap %s is not of the same type as the new queue-limit of new policy
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-Q_LIMIT_THRESHOLD_EXCEED_DEFAULT_MAX : Configuration failed. The configured queue-limit threshold %d exceeds the default max threshold value %d
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-Q_LIMIT_THRESHOLD_EXCEED_MAX : Configuration failed. The configured queue-limit threshold %d exceeds the max threshold value %d
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-RESERVE_COUNT_ERROR : Reserved Count Exceeding total [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-RESOURCE_INTERNAL : Internal Error in resource allocation
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-SAME_CLASSIFICATION_CRITERIA_NOT_ALLOWED : Configuration failed. Class-map %s can not have the same classification criteria as class-map %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-SHAPE_BURST_NOT_SUPPORTED : Configuration failed. Shape burst parameter is not supported for output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-SHAPE_NOT_ALLOWED_FOR_CLSDEFAULT_CHILDPLC : Configuration failed. Shape is not allowed in class-default of a child policy of the output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-TBLMAP_IN_USE_BY_AGG_POLICER : Configuration failed. Table-map cannot be deleted. Tablemap being used by one or more aggregate policers
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-TOP_HIERARCHICAL_OUTPUT_REQUIRE_SHAPING_ACTION : Configuration failed. Top level of hierarchical output policy %s requires a shaping action.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-TOTAL_BW_EXCEED_AVAIL_BW : Configuration failed. Total of rates %d in the policy exceeds available bandwidth %d of output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-TOTAL_POLICE_CLASS_RATE_EXCEED_AVAIL_BW : Configuration failed. Total of rates %d in the policy exceeds available bandwidth %d of output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-TOTAL_SHAPE_CLASS_RATE_EXCEED_AVAIL_BW : Configuration failed. Total of rates %d in the policy exceeds available bandwidth %d of output policy %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-UPDATE_QUEUE_THSHLD_FAIL : Failed to update queue threshold
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-3-VMRSEQ_INVALID : Internal Error Invalid VMR sequence
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-4-ACTION_NOT_SUPPORTED : Action is not supported in policymap [chars]
Explanation An action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation.
Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.
Error Message%QOSMGR-4-ACTION_NOT_SUPPORTED_PPVLAN : Action '%s' is not supported for a per port QoS child policy-map.
Explanation This message means that an action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation.
Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.
Error Message%QOSMGR-4-ADD_RMV_CHILD_POLICYMAP_NOT_ALLOWED : Not allow to add/remove attached child policymap of %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. ()
Error Message%QOSMGR-4-CLASS_NOT_SUPPORTED : Classification is not supported in classmap [chars]
Explanation This message means the an unsupported match class-map configuration command was configured in a policy map and attached to an egress interface, or that more than one match command was configured. This is a hardware limitation.
Recommended Action Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported.
Error Message%QOSMGR-4-CLSMAP_PROT_AND_TBLMAP_FROMTYPE_MUST_BE_SAME : Configuration failed. class-map protocol and table-map from-type protocol must be the same.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-CLSMAP_PROT_AND_TBLMAP_FROMTYPE_MUST_BE_SAME_ACL : Invalid configuration. class-map protocol and table-map from-type protocol must be the same. Classification for policy-map '%s' and class-map '%s' will not take place
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-CLSMAP_PROT_AND_TBLMAP_FROMTYPE_MUST_BE_SAME_IN_AGG_POLICER : Configuration failed. class-map protocol and table-map from-type protocol (within the configured aggregate-policer) must be the same.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-COMMAND_FAILURE : Execution of [chars] command failed on [chars]
Explanation The command to configure a QoS setting failed. This is possible due to lack of hardware resources. Check if any other messages along with this message indicate resource failure.
Recommended Action If other messages indicate that the hardware resources exceeded, retry the command with a smaller configuration. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-4-CONTROL_PLANE_CAN_HAVE_ONLY_CLASS_DEFAULT : Configuration failed. A Policy-map containing only 'class-default' can be attached to the 'control-plane'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-CONTROL_PLANE_CAN_HAVE_ONLY_POLICE_ACTION : Configuration failed. Only 'police' action allowed for a policy-map attached to the 'control-plane'
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-HARDWARE_NOT_SUPPORTED : Hardware limitation has reached for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management (sdm) template.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS ACLs.
Error Message%QOSMGR-4-HARDWARE_PROGRAMMING_ERROR : Hardware programming error encountered for policymap %s
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-INVALID_TABLE_MAP_FROM_TYPE : Configuration failed. Invalid table-map from-type
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-MATCH_NOT_SUPPORTED : Match type is not supported in classmap [chars]
Explanation Match ACL, match ip dscp and match ip precedence are the match types that are supported.
Recommended Action Reconfigure the class map; use only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map.
Error Message%QOSMGR-4-NOT_SUPPORTED : Action '[chars]' is not supported for a policymap attached to output side.
Explanation This message means that a set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take affect. This is a hardware limitation.
Recommended Action Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces.
Error Message%QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED : Policer configuration has exceeded hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more policers together in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by hardware.
Recommended Action Reconfigure the class map or the policy map or delete policy from some interfaces.
Error Message%QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED : Number of policers has exceeded per policy hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of policers.
Error Message%QOSMGR-4-POLICER_RATE_OUT_OF_RANGE : Configuration failed. Policer rate out of range. Maximum policing rate is %d bits per second
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-POLICE_QOS_GROUP_ACTION_MISMATCH : Configuration failed. Can not have set-qos-transmit conform-action with other conform-actions
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-POLICY_MAP_MIXED_IP_AND_NONIP_ACROSS_CMAPS : Configuration failed. Can not have IP and Non-IP classification across class-maps in the same input policy-map.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-POLICY_MAP_MIXED_IP_AND_NONIP_ACROSS_CMAPS_ACL : Invalid configuration. Can not have IP and Non-IP classification across class-maps in the same input policy-map. Classification for policy-map '%s' and class-map '%s' will not take place
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-POLICY_MAP_MIXED_IP_AND_NONIP_WITHIN_CMAP : Configuration failed. Can not have IP and Non-IP classification in the same class-map within an input policy-map.
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-QOSLABEL_EXCEED_MAX : Hardware limitation has reached for policymap %s
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more QoS Label entries than the number specified in the Switch Database Management (sdm) template.
Recommended Action Reconfigure the class map or reduce number of classes in the policy map to reduce the number of QoS Labels.
Error Message%QOSMGR-4-QOS_64_NO_CHILD_CLASS : Policymap %s does not have child class defined in 64 policers policymap
Explanation This policymap with 63/64 classes does not have a child class configured for all child policymaps
Recommended Action Reconfigure the policymap to have a class-default only child policy attached with all the parent classes
Error Message%QOSMGR-4-QOS_64_NO_CHILD_POLICY : Policymap %s does not have child policy to support 64 policers policymap
Explanation This policymap with 63/64 classes does not have a proper child policy configured for all parent vlan classes
Recommended Action Reconfigure the policymap to have a class-default only child policy attached with all the parent classes
Error Message%QOSMGR-4-QOS_64_NO_POLICER : Policymap %s has no policer defined in the child policy
Explanation This policymap does not have a policer in the child policy to qualify as a 64 policers ingress policymap
Recommended Action Reconfigure the policymap to have a class-default only child policy with policing action.
Error Message%QOSMGR-4-QOS_NOT_64_PLCR_CHILD : Policymap %s is not a valid 64 policer child policy
Explanation This policymap violates the conditions of 64 policer PPPV child policymap.
Recommended Action Reconfigure the policymap to meet the below criteria 64 Policers ingress policymap should have only 63 or 64 parent vlan classes It should satisfy all the Per-Port-Per-VLAN policymap conditions and have child policies attached with all the parent classes The child policies must have policing action defined for all the classes
Error Message%QOSMGR-4-QOS_NOT_64_PLCR_POLICY : Policymap %s is not a valid 64 policer ingress policy. %s
Explanation This policymap violates the conditions of 64 policer ingress policymap.
Recommended Action Reconfigure the policymap to meet the below criteria 64 Policers ingress policymap should have only 63 or 64 parent vlan classes It should satisfy all the Per-Port-Per-VLAN policymap conditions and have child policies attached with all the parent classes The child policies must have only class-default and policing action defined
Error Message%QOSMGR-4-QOS_TCAM_RESOURCE_EXCEED_MAX : Exceeded a maximum of QoS TCAM resources
Explanation The number of QoS TCAM entries required for all attached QoS policies exceeds the maximum number of QoS TCAM entries
Recommended Action Reconfigure the attached QoS policies the number of classmaps for per-port QoS polices, or classmap, vlans and attached interfaces for per-port, per-vlan QoS policies.
Error Message%QOSMGR-4-SET_ACTION_MISMATCH : Configuration failed. Set action cannot be configured along with any other kind of action
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-SET_POLICE_ACTION_MISMATCH : Configuration failed. For configuring marking with policing, use the 'police' extended CLI format to specify marking actions
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-SET_QOS_GROUP_ACTION_MISMATCH : Configuration failed. 'set qos-group' can not be configured along with any other set action
Explanation An internal software error has occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.()
Error Message%QOSMGR-4-TABLE_MAP_ACTION_MISMATCH : Configuration failed. Table-map set action can not be configured with other actions
Explanation An internal software error has occurred
Error Message 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.%QOSMGR-3-ASIC_PROGRAMMING_FAIL : Fails to program the ASIC for policymap [chars]
Explanation The system failed to access the hardware.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-BANDWIDTH_CHILD_ERROR : Bandwidth in one of the children class is greater than input bandwidth
Explanation An error occurred because the bandwidth value in one of the child classes is greater than the configured bandwidth value.
Recommended Action Either configure a higher bandwidth value, or decrease the bandwidth value of the child class.
Error Message%QOSMGR-3-BANDWIDTH_LEVEL_ERROR : Bandwidth command not acceptable at interface level
Explanation An error occurred because the hardware does not support the configured bandwidth value at the physical level.
Recommended Action Do not enter the bandwidth command at the interface level policy.
Error Message%QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED : Bandwidth oversubscribed in the interface
Explanation An error occurred because the total sum of the committed bandwidths at a particular level exceeds the maximum bandwidth of the interface.
Recommended Action Reduce the total committed bandwidth value to a value that is smaller than the maximum bandwidth of the interface.
Error Message%QOSMGR-3-BANDWIDTH_PARENT_ERROR : Sum of bandwidths is greater than parent class's bandwidth
Explanation An error occurred because the total sum of bandwidths of all the classes at the same level exceeds the bandwidth of the parent class.
Recommended Action Reduce the bandwidth value of the parent class.
Error Message%QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR : Sum of bandwidths is greater than parent class's shape(PIR)
Explanation An error occurred because the total sum of bandwidths of all the classes at the same level exceeds the shape value of the parent class.
Recommended Action Reduce the bandwidth value.
Error Message%QOSMGR-3-BANDWIDTH_SHAPE_ERROR : Bandwidth configured is greater than shape(PIR) of the class
Explanation An error occurred because the configured bandwidth is greater than the shape value.
Recommended Action Reduce the bandwidth value to a value smaller than the shape value of the class.
Error Message%QOSMGR-3-EFP_SHAPE_RESTRICTION : EFP policies cannot have shape command at physical level and more than one logical level classes
Explanation An error occurred because the hardware does not support four- level hierarchy, and the Ethernet Flow Point (EFP) policies resides in the pseudo-level between physical and logical levels.
Recommended Action Either remove the VLAN hierarchy from the EFP policy, or do not configure the shape command the physical level.
Error Message%QOSMGR-3-EQOS_CXT_EXCEEDED : Maximum Egress QosContexts consumed in the Bridge-Domain
Explanation An error occurred because the number of egress Quality of Service (QoS) VLAN matches or exceeds the maximum limit in the bridge-domain command.
Recommended Action Reduce the number of Egress Quality of Service (QoS) VLAN matches in the bridge domain command.
Error Message%QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED : Internal Error in resource allocation
Explanation An error occurred because the system is being depeleted of qos-handle profiles that are required to support the policy map.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED : Internal Error in resource allocation
Explanation An error occurred because the system is being depeleted of qos-profiled profiles that are required to support the policy-map.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT : The policy-map [chars] is detached due to the event [chars].
Explanation The attached policy map has become invalid because of the change in the port speed.
Recommended Action Change the value of the shaping or bandwidth entry in the output policy map and reattach the policy map to the interface.
Error Message%QOSMGR-3-LABEL_EXHAUST : Internal Error in resource allocation
Explanation An error occurred because the system is being depleted of Quality of Service (QoS) labels required to support all traffic classes in all the attached policy maps.
Recommended Action Reduce the number of distinctive class-map matches or set actions in the attached policy maps.
Error Message%QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED : Logical level queuing resource exhausted [chars]
Explanation An error occurred because the logical level queueing resources have been exhausted.
Recommended Action Release the unused logical level classes.
Error Message%QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED : Invalid policy-map detected during interface speed change
Explanation An error occurred because the value of the shape parameter in the policy exceeds the port speed.
Recommended Action Configure a lesser shape parameter value that will not exceed the interface speed parameter value.
Error Message%QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED : Exceeding the maximum queue-limit commands per class
Explanation An error has occurred because you attempted to exceed the maximum number of maximum queue-limit commands allowed per class.
Recommended Action Reduce the number of maximum queue-limit commands in each class.
Error Message%QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED : Exceeding the maximum qualified queue-limit commands per class
Explanation An error occurred because you attempted to exceed the maximum number of qualified queue-limit commands allowed per class.
Recommended Action Reduce the number of qualified queue-limit commands in each class.
Error Message%QOSMGR-3-MAX_WRED_THRESHOLDS_EXCEEDED : Exceeding the maximum number of wred thresholds per class
Explanation An error occurred because the system has exceeded the maximum weighted random early detection (WRED) thresholds allowed per class.
Recommended Action Do not use more than two threhshold combinations under a class.
Error Message%QOSMGR-3-OUT_OF_TCAM_RESOURCES : Out of tcam resources to execute command
Explanation An error occurred because of the nonavailability of ternary content addressable memory (TCAM) resources.
Recommended Action Change the configuration to reduce the TCAM entry usage.
Error Message%QOSMGR-4-POLICER_EXCEEDING_HW : Policer configuration has exceeded hardware limitation for policymap [chars]
Explanation An error occurred because the system has been exhausted of policers that support the specified policy maps.
Recommended Action Reduce the number of policer usage in the attached input policy maps.
Error Message%QOSMGR-3-POLICER_PROGRAMMING_FAIL : Fails to program HW policer
Explanation An attempt to access the hardware failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-PRIORITY_LEVEL_ERROR : Priority command not acceptable at interface level
Explanation An error occurred because the priority command is not supported in the hardware at the physical level.
Recommended Action Do not apply the priority command at the interface level policy.
Error Message%QOSMGR-3-PROFILE_EXHAUST : No free scheduler profiles available in hardware
Explanation An error occurred because there is no free scheduler profile in the hardware. This error may have occurred because of dissimilar profiles configured at the same hierarchy level.
Recommended Action Change the configuration value to the closest existing configuration.
Error Message%QOSMGR-3-PROFILES_EXHAUSTED : Out of rm profiles to execute command
Explanation An error occurred because there is no record manager (RM) profile to execute the command.
Recommended Action Change the configuration so you can reduce or reuse the RM profiles.
Error Message%QOSMGR-3-QLIMIT_LEVEL_ERROR : Qlimit command not supported in non-leaf classes
Explanation You attempted to configure a qlimit value in a nonleaf class.
Recommended Action Configure the qlimit value in leaf classes only.
Error Message%QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE : Qlimit value is out of range
Explanation You attempted to configure a qlimit value that are not within the supported range of values.
Recommended Action Configure the qlimit value within the supported range.
Error Message%QOSMGR-4-QUEUE_EXCEEDING_HW : Queue configuration has exceeded hardware limitation for policymap [chars]
Explanation The system has exhausted output queues that is required to support the policy map indicated in the message.
Recommended Action Reduce the number of traffic classes in the output policy maps.
Error Message%QOSMGR-3-QUEUE_EXHAUSTED : Class level queuing resource exhausted [chars]
Explanation The class-level queuing resources indicated in the message have been exhausted.
Recommended Action Release the unused class-level resources.
Error Message%QOSMGR-3-QUEUE_FLUSH_FAILED : Queue-Flush not successful
Explanation The scheduler failed to flush the queue.
Recommended Action Remove the shape configuration for the queue. If the error recurs, 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL : Fails to program HW scheduler
Explanation An attempt to access the hardware failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-SHAPE_BANDWIDTH_%_ERROR : Shape - Bandwidth-percent values inconsistent in the hierarchy, calculated bandwidth will exceed shape
Explanation An error occurred because you used the shape command to configure a bandwidth percent greater than the manually configured value in one of the child classes.
Recommended Action Configure a shape value greater than the current shape value, or a bandwidth percent value lesser than the current bandwidth percent value.
Error Message%QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR : Bandwidth in one of the children class is greater than input shape value
Explanation An error occurred because the value of the input bandwidth is less than the child class bandwidth.
Recommended Action Either increase the input bandwidth value, or decrease the bandwidth of the child class.
Error Message%QOSMGR-3-SHAPE_CHILD_ERROR : One of children class's shape config is higher
Explanation An error occurred because the shape value configured in the child class is greater than the shape value configured in the parent class.
Recommended Action Increase shape value in the parent class, or decrease the shape value in the child class.
Error Message%QOSMGR-3-SHAPE_PARENT_ERROR : Shape value is greater than parent class's shape or interface's speed
Explanation An error occurred because the shape value configured in the child class is greater than the shape value in the parent class.
Recommended Action In the child class, configure a shape value on the child class that is less than the shape value in the parent class or the speed value of the interface.
Error Message%QOSMGR-3-SHAPE_UNDERFLOW : New shape/speed value is less than the total bandwidth configured in the interface
Explanation An error occurred because the shape or speed value configured is less than the total bandwidth configured in the interface.
Recommended Action Either increase the shape or speed value, or reduce the bandwidth configured in the child classes.
Error Message%QOSMGR-4-STATISTICS_FAIL : Internal Error in reading statistics
Explanation The system failed to access the hardware to read the statistics.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-TCAM_EXHAUSTION : Internal Error in resource allocation
Explanation Ternary content addressable memory (TCAM) entries required to support the number of traffic classes defined in the policy map have been exhausted. The maximum number of allowed TCAM entries varies from one platform to another.
Recommended Action Reduce the number of traffic classes in the attached policy maps.
Error Message%QOSMGR-3-TCAM_PROGRAMMING_FAIL : Fails to program TCAM for policymap [chars]
Explanation An attempt to access the hardware failed.
Recommended Action 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/cisco/web/support/index.html. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS : Qlimit unit other than usec & byte is not supported
Explanation An error occurred because have you attempted to configure a qlimit unit that is not bytes or microseconds.
Recommended Action Configure the qlimit in units of bytes or microseconds.
Error Message%QOSMGR-3-UNSUPPORTED_WRED_UNITS : WRED threshold unit other than usec & byte is not supported
Explanation An error occurred because you attempted to configure a weighted random early detection (WRED) threshold unit that is not bytes or microseconds.
Recommended Action Configure the WRED threshold in units of bytes or microseconds.
Error Message%QOSMGR-3-WRED_LEVEL_ERROR : random-deteact command not supported in non-leaf classes
Explanation An error occurred beacuse you attempted to configure the random-detect command in a non leaf class.
Recommended Action Configure the random-detect command in leaf classes only.
Error Message%QOSMGR-3-WRED_VALUE_OUT_OF_RANGE : random-detect value is out of range
Explanation An error occurred because you attempted to configure a random-detect value outside the supported range.
Recommended Action Configure the random-detect value from within the supported range.
Error Message%QUICC-1-BADHDXFSM : Quicc(%d/%d), Unexpected HDX state %d, event %d
Explanation A bad event was detected in the state machine for half duplex transmission/reception.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC-1-CTSLOST : QUICC(%d/%d), Clear to Send Lost
Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Error Message%QUICC-1-INITFAIL : QUICC([dec]/[dec]), SCC[hex] init failed
Explanation The software has failed to initialize or restart a 1T serial card.
Recommended Action Clear the serial interface. If this message recurs, 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://tools.cisco.com/ServiceRequestTool/create/, 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%QUICC-1-LINEFLAP : Quicc(%d/%d), Excessive modem control changes
Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Error Message%QUICC-1-NOMEMORY : msgtxt_nomemory
Explanation The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large, requiring a lot of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.
Error Message%QUICC-1-TOOBIG : Quicc([dec]/[dec]), packet too big, packet size was [dec] bytes
Explanation A packet larger than the assigned MTU of this serial interface has been queued for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. 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://tools.cisco.com/ServiceRequestTool/create/, 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%QUICC-1-TOOSMALL : Quicc([dec]/[dec]), packet was less than 2 bytes, packet size was [dec] bytes
Explanation A small packet (less than 2 bytes) has been queued for transmission. The interface cannot handle such small packets for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. 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://tools.cisco.com/ServiceRequestTool/create/, 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%QUICC-1-UNDERFLO : QUICC(%d/%d), Transmit underflow
Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%QUICC-1-UNEXPECTED_INTERRUPT : Quicc(%d), Unexpected modem-signal interrupt
Explanation The software did not expect to see a modem control signal change on this type of WIC card interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC-1-UNKNOWN_WIC : Quicc(%d), wic card has an unknown id of %x
Explanation The software does not recognize the type of WIC card plugged into the port module.
Recommended Action Check the part number on the WIC card to verify that it is supported in the IOS release operational on the router or contact your technical support representative.
Error Message%QUICC-1-UNSUPPORTED_CONFIG : Slot %d has an unsupported combination of ISDN WAN interface cards
Explanation It is not possible to support this type of BRI card in slot 1 along with another BRI card in slot 0.
Recommended Action Remove one of the BRI cards from either slot.
Error Message%QUICC-1-WRONG_SLOT : Quicc(%d), BRI card in wrong slot(1)
Explanation The BRI card is not supported in WIC slot 0.
Recommended Action Power down, move the BRI card to the other WIC slot on the port module and reboot.
Error Message%QUICC-3-OWNERR : QUICC(%d/%d), Buffer ownership error, pak=0x%x
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Error Message%QUICC-3-UCODE_REV_UNKN : Unknown microcode revision number: %d
Explanation The MC68360/QUICC CPU was running an unexpected version of microcode. This could be possible if a new version of the QUICC chip was released or if a very old version was used in the manufacturing process. This could also occur if a new version of microcode was released to fix any bugs
Recommended Action A decrease in performance might occur for any async interfaces running PPP. Call your technical support representative if this is an issue.
Error Message%QUICC-3-UNKNOWN_SCCS : Quicc, Incorrect SCC number
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Error Message%QUICC3-1-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the Ethernet 10BASE-T cable.
Error Message%QUICC_ASYNC-1-INITFAIL : msgtxt_initfail
Error Message%QUICC_ASYNC-3-CTSLOST : Unit %d, Clear to Send Lost
Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection
Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Error Message%QUICC_ASYNC-3-UNDERFLO : Unit %d, underflow error
Error Message%QUICC_ETHER-1-INITFAIL : msgtxt_initfail
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC_ETHER-1-LOSTCARR : Unit %d, lost carrier. Transceiver problem?
Explanation The Ethernet 10BaseT cable is unplugged.
Recommended Action Connect the 10BaseT Ethernet cable.
Error Message%QUICC_ETHER-3-UNDERFLO : Unit %d, underflow error
Explanation While transmitting a frame, the Ethernet controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem reccurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC_ETHER-5-COLL : Unit %d, excessive collisions. Retry limit %d exceeded
Explanation An Ethernet cable is broken or unterminated.
Recommended Action Check cables for proper connections, termination, and so on.
Error Message%QUICC_ETHER-5-HBEAT : Unit %d, heartbeat check failure
Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message%QUICC_ETHER-5-LATECOLL : Unit %d, late collision error
Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message%QUICC_SERIAL-1-INITFAIL : msgtxt_initfail
Explanation The serial interface controller of the QUICC chip could not be initialized or started for operation. There is probably a hardware problem.
Recommended Action Power cycle the system. If the error reoccurs, replace the unit.
Error Message%QUICC_SERIAL-3-CTSLOST : Unit %d, Clear to Send Lost
Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem stems from a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and or communication equipment such as the channel service unit/data service unit (CSU/DSU).
Error Message%QUICC_SERIAL-3-UNDERFLO : Unit %d, underflow error
Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem reccurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC_SERIAL-5-LINEFLAP : Unit %d, excessive modem control changes
Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Error Message%QUICC_SERIAL-5-LOSTCARR : Unit %d, carrier detect signal lost during message reception
Explanation The RS-232C Carrier Detect (DCD) signal was de-asserted during message reception. The DCE equipment is responsible for asserting this signal.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected.
Error Message%R4K_MP-3-CPUMON_QFULL : CPU Monitor queue full
Explanation A process-level RPC call fails due to lack of resources.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%R4K_MP-3-CPUMON_QKEEPALIVE_EXCEEDED : CPU Monitor queue keepalive exceeded
Explanation A process-level RPC call exceeded allowed keepalive limit
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%R4K_MP-3-CPUMON_RECURSION : handle_cpumon_queue recursion, continuing...
Explanation MP queue handler recursion, should never occur.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%R4K_MP-3-CRASHED : CPU %d has now crashed a total of %d times.
Explanation The indicated CPU crashed, and has been restarted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%R4K_MP-5-DELEGATE_GETBUF : Delegated call to 0x%x failed, out of buffers
Explanation An RPC call to the indicated function failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%R4K_MP-5-NOMSGDECODE : cpu[dec]: no message decoder for msgid [dec]
Explanation No decoder table entry exists for the indicated message.
Recommended Action 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://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RAC-3-RACIPL : DHCP is already running on interface [chars]
Explanation The interface already has a DHCP-originated address through some other system mechanism.
Recommended Action Verify the system configuration.
Error MessageError Message%RAC-3-RACNOIPL : Can not find lease information for interface %s
Explanation Internal error - DHCP lease information is missing for the interface
Recommended Action Report the problem and how it can be reproduced to Cisco TAC
Error Message%RAC-3-RACNOQ : Can't create RAC work queue
Explanation Internal error - probable cause is insufficient memory resources
Recommended Action Check available memory.
Error Message%RADIO-2-RF_OVERTEMP : Radio%d/0, ODU %d: over temperature %s
Explanation Most likely cause is hardware failure or solar heating
Recommended Action Keep the RF ODU cool
Error Message%RADIO-3-SELF_TEST_FAILED : Radio%d/0, failed self-test
Explanation Most likely a hardware failure
Recommended Action Call tech support
Error Message%RADIO-4-BAD_IF_PIC : Radio%d/0, bad IF PIC version (%d) on IDU
Explanation Most likely a hardware configuration oversite
Recommended Action Call tech support
Error Message%RADIO-4-BAD_RF_PIC : Radio%d/0, bad RF PIC version (%d) on ODU %d
Explanation Most likely a hardware configuration oversite
Recommended Action Call tech support
Error Message%RADIO-4-CHECKSUM_ERR : Radio%d/0, radio phy eeprom %s checksum (stored:0x%02x, calculated:0x%02x)
Explanation Most likely cause is Shut or No Shut command
Recommended Action Enter the No Shut command
Error Message%RADIO-4-DSPHPITIMEOUT : Radio%d/0, HPI timeout while attempting to access DSP %s
Explanation A DSP on the RADIO line card was not granting access to its memory. Most likely cause is a DSP firmware internal error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-DSPINDERR : Radio%d/0, Error processing indication from DSP %s (%s:%d)
Explanation A DSP on the RADIO line card generated an indication message that could not be processed. This can happen when the router is operating under severe traffic load.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-DSPSPURRESP : Radio%d/0, spurious DSP response from %s: %08x %08x %08x %08x %08x %08x %08x %08x
Explanation A DSP on the RADIO line card generated a response message unexpectedly. This can happen when the router is operating under severe traffic load.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-DSPULOFLOW : Radio%d/0, uplink message queue overflow reported by DSP %s
Explanation At least one DSP-to-router message was lost due to that DSP's uplink queue being full. This can happen when many thresholds/histograms/timelines are being triggered or expiring at the same time.
Recommended Action Change thresholds and/or reduce histogram/timeline usage to lower the load on the system
Error Message%RADIO-4-FPGADONEPINLOW : Radio%d/0, DONE pin on FPGA %s did not assert after downloading
Explanation The DONE pin of a FPGA device on the RADIO line card did not assert after the downloading of the device. This probably indicates an existing or developing hardware failure.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-FPGAINITPINHIGH : Radio%d/0, INIT pin on FPGA %s asserted during downloading
Explanation The INIT pin of a FPGA device on the RADIO line card asserted midway through the downloading of the device. Most likely cause is corrupted FPGA image.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-FPGAINITPINLOW : Radio%d/0, INIT pin on FPGA %s not asserted when PROG pin asserted
Explanation The INIT pin of a FPGA device on the RADIO line card did not assert when the PROG pin was asserted. This indicates either a faulty FPGA device or software problem resetting it.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-IF_COMM : Radio%d/0, IDU IF internal serial communication error - %s
Explanation Most likely cause is a loose IF baby board
Recommended Action Replace hardware
Error Message%RADIO-4-IF_OSC : Radio%d/0, Internal %s Oscillator out of Lock %s
Explanation Most likely cause is vibration or hardware failure
Recommended Action Replace internal card
Error Message%RADIO-4-NEWER_IF_EEPROM : Radio%d/0, Unsupported IF PIC major eeprom version (%u) on IDU
Explanation IOS should be upgraded to support the new eeprom
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO-4-NEWER_RF_EEPROM : Radio[dec]/0, Unsupported RF PIC major eeprom version ([int]) on ODU [dec]
Explanation The system has detected an unsupported RF PIC major EEPROM version on the ODU specified in the error message.
Recommended Action Contact your Cisco technical support representative to upgrade the Cisco IOS Software for the system.
Error Message%RADIO-4-NO_HWCAP_FIELD : Radio%d/0, could not find HW Capabilities field in IDPROM
Explanation Most likely cause is an improperly-programmed IDPROM
Recommended Action Have the IDPROM on the linecard reprogrammed
Error Message%RADIO-4-NO_IMAGE : %s%d/%d, Chip %s: failed to find image given current configuration
Explanation Most likely configured to use external files
Recommended Action Change configuration to use internal files
Error Message%RADIO-4-PHY_REQ : Radio%d/0, link synchronization %s.
Explanation Most likely cause loose ODU cable
Recommended Action Check all cables
Error Message%RADIO-4-PHY_SYNC_FAIL : Radio%d/0, link synchronization %s.
Explanation Most likely cause loose ODU cable
Recommended Action Check all cables
Error Message%RADIO-4-PHY_SYNC_OK : Radio%d/0, link synchronization acquired.
Explanation Most likely cause is No Shut command
Recommended Action None
Error Message%RADIO-4-PHY_SYNC_REOK : Radio%d/0, link synchronization re-acquired.
Explanation Most likely cause is No Shut command on remote end
Recommended Action None
Error Message%RADIO-4-RF_AGC : Radio%d/0, ODU %d max transmitter power exceeded %s
Explanation Most likely cause is hardware failure
Recommended Action Replace RF ODU
Error Message%RADIO-4-RF_ANTENNA : Radio%d/0, ODU %d is %s
Explanation Most likely cause is a disconnected cable
Recommended Action Check or replace cable from UBR to the Out Door Unit
Error Message%RADIO-4-RF_COMM : Radio%d/0, ODU %d serial communication error - %s
Explanation Most likely cause is a disconnected cable
Recommended Action Check or replace cable from UBR to the Out Door Unit
Error Message%RADIO-4-RF_OSC : Radio%d/0, ODU %d %s Oscillator out of Lock %s
Explanation Most likely cause is vibration or hardware failure
Recommended Action Replace electronics on Out Door Unit
Error Message%RADIO-4-RF_TEMP : Radio%d/0, ODU %d: temperature is %d degrees C, threshold is %d degrees C
Explanation Most likely cause is hardware failure or solar heating
Recommended Action Keep the RF ODU cool
Error Message%RADIO-4-RF_VOLT : Radio%d/0, ODU %d: supply voltage out of range %s
Explanation Most likely cause is hardware failure
Recommended Action Replace RF ODU
Error Message%RADIO-5-CLEAR_METRICS : Radio%d/0, link metrics cleared
Explanation User requested the link metrics be cleared
Recommended Action none
Error Message%RADIO-5-CONFIG_HW : Radio%d/0, hardware does not support requested configuration: %s
Explanation Most likely cause is incorrect configuration
Recommended Action Change the configuration to match the hardware
Error Message%RADIO-5-CONFIG_MISMAT : Radio%d/0, invalid or inconsistent configuration requested %s
Explanation Most likely cause is the ARQ settings are not supported by the current radio channel parameters
Recommended Action Change ARQ settings to allowed values given the current radio channel parameters. You can use the radio arq reset command to do this.
Error Message%RADIO-5-IMAGE_BAD_CRC : %s%d/%d, detected a bad CRC while downloading image %s to chip %s
Explanation Most likely a protocol error while downloading
Recommended Action If it's a TFTP download, try again; otherwise call tech support
Error Message%RADIO-5-IMAGE_TIMEOUT : %s%d/%d, timeout trying to open image %s for chip %s
Explanation Most likely a protocol error while opening
Recommended Action If it's a TFTP download, try again; otherwise call tech support
Error Message%RADIO-5-LOCAL_IN_SYNC : Radio%d/0, Link synchronization acquired.
Explanation Phy layer successfully acquired link.
Recommended Action None
Error Message%RADIO-5-LOCAL_NO_CW : Radio%d/0, Still trying to establish link (validate codeword).
Explanation Most likely cause remote system is not transmitting on correct frequency
Recommended Action No Shut remote system
Error Message%RADIO-5-LOCAL_NO_FREQ : Radio%d/0, Still trying to establish link (frequency sync).
Explanation Most likely cause remote system is not transmitting on correct frequency
Recommended Action No Shut remote system
Error Message%RADIO-5-LOCAL_NO_SYNC : Radio%d/0, Still trying to establish link (timing sync).
Explanation Most likely cause remote system is not transmitting.
Recommended Action No Shut remote system
Error Message%RADIO-5-LOCAL_NO_TRANSMIT : Radio%d/0, ODU saftey interlock is preventing transmission. Check ODU and cables. %s
Explanation Most likely cause cable not attached, ODU overheated
Recommended Action Check ODU cable
Error Message%RADIO-5-LOCAL_NO_VITERBI : Radio%d/0, Still trying to establish link (viterbi sync).
Explanation Most likely cause remote system is not transmitting on correct frequency
Recommended Action No Shut remote system
Error Message%RADIO-5-METRICS_THRESH : Radio%d/0, %s per %s threshold met(%d=%d)
Explanation Most likely cause is a mis-aligned antenna
Recommended Action Re-align the antenna(s)
Error Message%RADIO-5-PHY_RETRY : Radio%d/0, event %23s in state %15s
Explanation Most likely cause incorrect configuration
Recommended Action Review configuration and hardware capabilities
Error Message%RADIO-5-PHY_SYNC_LOST : Radio%d/0, Lost link. Check remote transmitter.
Explanation Most likely cause remote system is not transmitting.
Recommended Action No Shut remote system
Error Message%RADIO-5-REMOTE_LOST_SYNC : Radio%d/0, Remote end reports: %s
Explanation Most likely cause cable not attached, ODU overheated
Recommended Action Check ODU cables
Error Message%RADIO-5-REMOTE_NO_SYNC : Radio%d/0, Remote end reports: Unable to acquire link synchronization.
Explanation Most likely cause cable not attached, ODU overheated
Recommended Action Check ODU cables
Error Message%RADIO-5-THRESHOLD : Radio%d/0, %s %s threshold crossed ODU %d
Explanation Most likely cause is a user defined threshold
Recommended Action none
Error Message%RADIO-6-IMAGE_NOT_FOUND : %s%d/%d, could not find image %s for chip %s
Explanation Most likely a typo when set the url of the image
Recommended Action Try again
Error Message%RADIO-6-SELF_TEST_SUCCESS : Radio%d/0, self-test successful
Explanation Passed a self-diagnostic
Recommended Action This is a good thing
Error Message%RADIO_DRIVER-1-DISCOVER : Only found %d interfaces on bay %d, shutting down bay
Explanation Most likely system or hardware failure
Recommended Action Replace Line Card
Error Message%RADIO_DRIVER-3-DMADESCSEQERR : DMAC detected a descriptor sequence error (DMAC Status Register is 0x%08x).
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO_DRIVER-3-LOCALBUSERR : A line card local bus error, error status 0x%08x, error address 0x%08x
Explanation A device on the RADIO line card local bus either didn't respond to a select, timed out once selected or issued an error while selected. This probably indicates an existing or developing hardware failure.
Error Message%RADIO_DRIVER-3-NOTRADIO : Device reported %#x
Explanation Most likely hardware failure
Recommended Action Replace defective hardware
Error Message%RADIO_DRIVER-3-PCIPERROR : DMAC reported PCI parity error (DMAC Status Reg: 0x%08x)
Explanation A parity error occured on the PCI bus while the RADIO DMA controller was performing a read/write. This probably indicates an existing or developing hardware failure.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIO_DRIVER-3-PCITARGETABORT : Device received a PCI Target Abort (DMAC Status Register is 0x%08x)
Explanation When attempting a PCI master read/write, the target issued an abort to the DMA controller. This usually indicates that an incorrect target was selected, and in this case means that shared packet memory was not the target. This is likely a software error causing the RADIO DMAC to access an invalid target.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
RADIUS Messages
Error Message%RADIUS-3-ALLDEADSERVER : Group [chars]: No active radius servers found. Id [dec].
Explanation This error message occurs when all the servers configured in a server group are found to be unresponsive.
Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running.
Error Message%RADIUS-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.
Recommended Action This is an internal software error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-CANNOT_OPEN_SOCKET : Cannot open UDP socket for service [chars]
Explanation The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port.
Recommended Action Check your configuration to make sure that no other services are using the same port. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-CORRUPTCONTEXT : Bad Magic pattern in [chars]:[hex], magic:[hex]!
Explanation The magic pattern imprinted on the internal hash table data structures in RADIUS subsystem is missing and indicates memory corruption. The memory is getting overwritten by a misbehaving process. The traceback and the process information is generated to the result of the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-DATAERROR : Warning: %s
Explanation The given data passed into the Radius subsystem is considered invalid and may result in loss of attributes.
Recommended Action Please collect traceback and contact your technical support representative.
Error Message%RADIUS-3-FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-FORMATLONG : Format string too long.Maximum allowed length is [dec].
Explanation The user is attempting to configure a format string with a prefix that is too long.
Recommended Action Enter a shorter string to configure.
Error Message%RADIUS-3-IDENTFAIL : Saving of unique accounting ident aborted. Configuration has been modified.
Explanation The configuration has been modified. It cannot save the unique accounting IDENT to nvram. The message is to inform the user that the saving of unique accountingident is aborted due to the change in configuration.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-INVALIDFORMAT : Invalid Nas Port Format: [chars] [char]
Explanation The user is attempting to configure an incorrect format string.
Recommended Action Enter a 32-character string using supported characters only.
Error Message%RADIUS-3-NOACCOUNTINGRESPONSE : Accounting message [chars] for session [chars] failed to receive Accounting Response.
Explanation Maximum number of retransmissions is exceeded. Thenetwork is not accessible or the RADIUS server is down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-NOATTRLIST : No attribute-list passed through parser.
Explanation An internal error has occurred. The reason could be hardware or software. The error appears when no attribute list is passed through the parser.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-NOHOSTNAME : Failed to retrieve my hostname.
Explanation Could not find the router's hostname. A hostname needs to be defined, since it determines the RADIUS profile we will retrieve.
Recommended Action Define a hostname on the router's config. Refer to the hostname configuration section of IOS documentation.
Error Message%RADIUS-3-NOSERVERS : No Radius hosts configured or no valid server present in the server group [chars]
Explanation RADIUS is attempting to send a request, but there are no hosts configured to which the request is sent.
Recommended Action Configure a host with the radius-server command providing the IP address of the server. Refer to the radius-server host configuration section of IOS documentation.
Error Message%RADIUS-3-OVERRUN : Insufficient buffer space [dec] for string value.
Explanation This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software, less likely by a hardware. The traceback and process information is generated due to this condition.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter show tech-support command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-PICKERR : Internal pick-server error: %s
Explanation Radius encountered an internal consistency error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action Configure a proper secret. Refer to the shared secret configuration section for RADIUS servers in IOS documentation.
Error Message%RADIUS-3-SERVERTYPEMISMATCH : Servers [IP_address] and [IP_address] in server group '[chars]' are of different types.
Explanation All the servers in a server group should either be of type standard or non-standard.
Recommended Action Enter show running-config command and enure all the RADIUS servers in the server group printed above are of the same type — either standard or non-standard.
Error Message%RADIUS-3-SOURCEPORTALLOCERROR : Warning: Unable to allocate port %d
Explanation Unable to allocate a certain port, will not have the full range of source ports. This is not supposed to happen, contact support.
Recommended Action Contact support
Error Message%RADIUS-3-UNKNOWNAPI : Unknown API type [dec]
Explanation RADIUS code has been invoked using an unknown API type. This is the result of a bug in the RADIUS subsystem.
Recommended Action Check bug toolkit on Cisco web-site to look for a bug which has symptoms similar to the one occured. If there is no entry for the problem you faced, collect traceback and 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-3-ZEROATTRLEN : Radius attr [dec] len 0
Explanation An internal error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-4-BADATTRLIST : Unable to process attribute list.
Explanation The attribute list is syntactically incorrect.
Recommended Action Please specify the attribute list as a comma-delimited string of integers between 1 and 255.
Error Message%RADIUS-4-NOATTRLISTDEF : Warning: Attribute list %s is not defined.
Explanation The given attribute list is not defined.
Recommended Action Please define the attribute list as soon as possible.
Error Message%RADIUS-4-NOPUBLICSERV : Warning: No servers werefound in the public server list.
Explanation The given server is not on the global public servers list. This is an internal consistency error.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-4-NOSERV : Warning: Server [IP_address]:[dec],[dec] is not defined.
Explanation The given server is not globally defined.
Recommended Action Define the server. Refer to the server configuration section of IOS documentation.
Error Message%RADIUS-4-RADIUS_ALIVE : RADIUS server [IP_address]:[int],[int] is being marked alive.
Explanation A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired.
Recommended Action No action is required.
Error Message%RADIUS-4-RADIUS_DEAD : RADIUS server [IP_address]:[int],[int] is not responding.
Explanation The server might not be available to serve request. server has not responded to repeated requests.
Recommended Action Check for the connectivity to server. Check if the RADIUS server is still active. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter show running-config command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RADIUS-4-SERVREF : Warning: Server [IP_address]:[dec],[dec] is still referenced by server group.
Explanation The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action De-reference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.
Error Message%RADIUS-6-GETPOOLS : Retrieving IP-Pools via user [chars]
Explanation Getting initial IP-Pool definitions from RADIUS, using the given user's profile.
Recommended Action No action is required.
Error Message%RADIUS-6-GETROUTES : Retrieving static routes in user [chars]
Explanation Getting initial static routes from RADIUS, using the given user's profile.
Recommended Action No action is required. The message is informatory in nature indicating that it is getting the static routes based on user's profile.
Error Message%RADIUS-6-IDENTSAVE : Saving config with new acct ident in nvram.
Explanation Saving an accounting ident in nvram.
Recommended Action Informational message only. No action is required.
Error Message%RADIUS-6-RESETDEADSERVER : Group [chars]: Marked alive as Radius server [IP_address]:[dec],[dec] configured.
Explanation RADIUS server is now configured in the server group which was previously marked dead.
Recommended Action Informational message only. No action is required.
Error Message%RADIUS-6-SERVERALIVE : Group [chars]: Radius server [IP_address]:[dec],[dec] is responding again (previously dead).
Explanation A RADIUS server, which previously was dead, has started responding again.
Recommended Action Informational message only. No action is required.
RADIX Messages
Error Message%RADIX-2-INIT : No memory for radix initialization: %s
Explanation The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
Error Message%RADIX-3-ADDMASK : Error adding mask entry, %s
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-3-BADTREE : Invalid pointer to head of tree, 0x%x
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-3-DELETE : Error deleting trie entry, %s
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-3-NOMEMORY : No memory available %s
Explanation The system is out of memory.
Recommended Action Try one of these actions to correct the problem: Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms.
Error Message%RADIX-4-ORPHAN : Orphaned mask %#x, refcount=%d at %#x, next=%#x
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)