MGX and SES Error Messages, Release 4
MGX and SES Error Messages, Release 4 (part C2)
-
MGX and SES Error Messages, Release 4
-
Preface to MGX and SES Error Messages, Release 4
-
MGX and SES Error Messages, Release 4 (part A1)
-
MGX and SES Error Messages, Release 4 (part A2)
-
MGX and SES Error Messages, Release 4 (part A3)
-
MGX and SES Error Messages, Release 4 (part A4)
-
MGX and SES Error Messages, Release 4 (part B1)
-
MGX and SES Error Messages, Release 4 (part B2)
-
MGX and SES Error Messages, Release 4 (part B3)
-
MGX and SES Error Messages, Release 4 (part B4)
-
MGX and SES Error Messages, Release 4 (part C1)
-
MGX and SES Error Messages, Release 4 (part C2)
-
MGX and SES Error Messages, Release 4 (part C3)
-
MGX and SES Error Messages, Release 4 (part C4)
-
MGX and SES Error Messages, Release 4.0.10 (part D)
-
Download this chapter
Download the complete book
Feedback
Table Of Contents
SHMA-7-MSG_NOT_SUPPORT
SEVERITY : InformationFORMAT : "Msg Type %d(%s) is not supported by Active PXM"FLAG : Write BramTHROTTLING : No ThrottlingEXPLANATION : "The specified message type is not supported by the Active PXM and so will be NACKed by the Active PXM. This should happen only after loadrev on the PXM pair. When the Active PXM is running a lower revision."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO : No Required InfoDDTS "csrsmcnf"
SMCS-4-RSRC_ERROR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Insufficient System Resources Available"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore due to insufficient available system resources like memory, ipc messages"RECOMMENDED ACTION: "Check system resources & Try again"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-4-IPCSNDRCV_ERROR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s IPC Message Send Problem"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore due to IPC messaging Problem"RECOMMENDED ACTION: "Check system resources & Try again"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-4-STANDBY_UPDATE_
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s standby PXM update Failed"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore due to failure of PXM standby update for the logged task"RECOMMENDED ACTION: "Check Task & Standby PXM health and try Again"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-4-API_TIMEOUT_ERR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Timed Out"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore due to failure of the task to the operation within the specified timeout period"RECOMMENDED ACTION: "Check Task health and PXM CPU usage and Try Again"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-4-TASK_INTERNAL_E
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Task Error"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore due to internal error in the logged task"RECOMMENDED ACTION: "Check for task related event logs and take suitable action"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-4-AC_DBUPDATE_ERR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Disk Update Failed"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as Disk Modification Request Failed"RECOMMENDED ACTION: "Indicates an internal error, It needs to be analyzed by TAC and possibly by development team."REQUIRED INFO "Collect dsplog, dsperr, dspdbinfo <slot> 3 information"SMCS-4-AC_SHM_ERROR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Request To SHM Failed"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as Request to ShelfMgr Task Failed"RECOMMENDED ACTION: "Indicates an internal error, It needs to be analyzed by TAC and possibly by development team."REQUIRED INFO "Collect dsplog, dsperr, dspcd <slot> information"SMCS-4-PXMCM_FAILURE
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Failed to delete Port/Partition properly"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as PXMCM Failed"RECOMMENDED ACTION: "Indicates an internal error detected by the PXMCM It needs to be analyzed by TAC and possibly by the development team."REQUIRED INFO "Please capture the following information from the and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot having the problem>4) dsperr for the above slots.5) Save the core file if required"SMCS-4-DISK_IPC_FAIL
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s IPC Related Error"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as some IPC related function called by Disk application failed. "RECOMMENDED ACTION: "Check the error log for the specifc IPC related error logged by the dbSvr task. Also look for events that have been logged by the IPC or other tasks to indicate the nature of the IPC problem"REQUIRED INFO "Please capture the following information and call your TAC support1) dspver2) dsplog -sl <slot having the problem> "SMCS-4-DISK_CLNUP_FAIL
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Db cleanup forFLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the cleanup for the slot failed. Most probably a call to dbio_cleanup_slot_info() function returned ERROR"RECOMMENDED ACTION: "Check event logs to find the event logged by disk regarding a failure to clean the slot info. "REQUIRED INFO "Please capture the following information and call your TAC support1) dspver2) dsplog "SMCS-4-DISK_STBY_STATE
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Could not get standby card state."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task could not get the state of the stdby slot. Most probably a call to dbio_standby_card_state_get() function returned ERROR"RECOMMENDED ACTION: "Check event logs to find the event logged by disk regarding a failure to get the standby card state. "REQUIRED INFO "Please capture the following information and call your TAC support1) dspver2) dsplog -sl <standby slot > "SMCS-4-DISK_INVALID_SL
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Was passed invalid slot for clearing "FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task was passed a slot that is not valid for clrsmcnf"RECOMMENDED ACTION: " Try clrsmcnf on valid slot"REQUIRED INFO "Please capture the following information and call your TAC support1) dspcd <slot_number>2) dspcds"SMCS-4-DISK_INVALID_CD
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s clrsmcnf was invoked on standby card."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task detected the command being executed on a card that is not the active card "RECOMMENDED ACTION: "Try clrsmcnf on valid card role"REQUIRED INFO "Please capture the following information and call your TAC support1) dspcd <active_pxm_slot>2) dspcds"SMCS-4-DISK_STBY_SIG_F
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s Could not create a signature file"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task could not create signature file"RECOMMENDED ACTION: "Try clrsmcnf again"REQUIRED INFO "Please capture the following information and call your TAC support1) dspver2) dsplog"SMCS-4-DISK_ERROR
SEVERITY: ErrorFORMAT: "SMCSR Operation Failed Task %s : A general error occurred."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task failed to carry out required function"RECOMMENDED ACTION: "Try clrsmcnf again"REQUIRED INFO "Please capture the following information and call your TAC support1) dspver2) dsplog3) dsperrs"SMCS-4-RMM_CLRSMCNF_ER
SEVERITY: ErrorFORMAT: "Clrsmcnf failed. Task %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error while open/modify an auto_config file."RECOMMENDED ACTION: "Check system resources & Try again"REQUIRED INFO "Please capture the following information1) dspver2) dsplog3) dsperrs"SMCS-4-FATAL_ERR_PNNI
SEVERITY: ErrorFORMAT: "Clrsmcnf failed. %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Pnni module failed Clrsmcnf for un-recoverable error."RECOMMENDED ACTION: "Check for task related event logs"REQUIRED INFO "Collect dsplog, dsperr information"SMCS-7-INFO_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-6-NOTICE_PNNI
SEVERITY: NoticeFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-5-WARNING_PNNI
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "something during CSRSmcnf that may cause potential problem to the system"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO "dsplog -mod CSR; dspconinfo; dsppnports"SMCS-4-ERROR_PNNI
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "internal software error"RECOMMENDED ACTION: "talk to developer engineer to identify problem"REQUIRED INFO "capture logs, especially dsplog -mod CSR; dspconinfo; dsppnports; Go to standby, do the same display"SMCS-7-CONGEST_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-NULL_PTR_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-MALLOC_FAIL_PNN
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-TIMEOUT_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-ABORT_FAIL_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-INTF_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-TREE_NOTEMPTY_P
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-PEP_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-DISK_FAIL_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-START_END_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-BUFFER_UPDT_PNN
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSMCS-7-REDO_UPDT_PNNI
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "control-point"
MIBS-7-INFO
SEVERITY : InformationFORMAT : "%d: %s %d"FLAG : No FlagTHROTTLING : One TickEXPLANATION : "Generic information, see event log"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO : No Required InfoMIBS-7-INFO_RETRY
SEVERITY : InformationFORMAT : "%d: %s %d"FLAG : No FlagTHROTTLING : One TickEXPLANATION : "Subagent retry to register with master agent"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO : No Required InfoEMAN-5-PARMINVALID
SEVERITY: WarningFORMAT: "%d Parm %s value '0x%x'."FLAG: No FlagTHROTTLING One TickEXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoEMAN-5-INVALID_PTR
SEVERITY : WarningFORMAT : "%d: %s %p"FLAG : Stack TraceTHROTTLING : One TickEXPLANATION : "Pointer is not safe to dereference."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO : No Required InfoEMAN-5-INVALID_PTR2
SEVERITY : WarningFORMAT : "%d: %s %p %s %p %d"FLAG : Stack TraceTHROTTLING : One TickEXPLANATION : "Pointer is not safe to dereference."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO : No Required InfoDDTS "control-point"
RTM-5-INVALIDINPUT
SEVERITY: WarningFORMAT: "One of the inputs to the function %s() was invalid."FLAG: No FlagTHROTTLING One TickEXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-PARMINVALID
SEVERITY: WarningFORMAT: "Parm %s value '0x%x' is invalid to %s."FLAG: No FlagTHROTTLING One TickEXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-PARMINVLENGTH
SEVERITY: WarningFORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"FLAG: No FlagTHROTTLING One TickEXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-FUNCFAIL_STKDUM
SEVERITY: WarningFORMAT: "%s() RTM subsystem call to %s() failed. rc=%d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-FUNCFAIL
SEVERITY: WarningFORMAT: "%s() RTM subsystem call to %s() failed. rc=%d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "The specified function call failed. It failed with the specified return code."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-PARMOUTOFRANGE
SEVERITY: WarningFORMAT: "%s() Parm %s '%d' is out of range %d-%d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-MALLOCFAILED
SEVERITY: WarningFORMAT: "%s() Call to ssiMalloc() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to allocate more memory has failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-OPEN_TRANS_FAIL
SEVERITY: WarningFORMAT: "OpenTransport() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "OpenTransport() failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-BIND_TRANS_FAIL
SEVERITY: WarningFORMAT: "BindTransport() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "BindTransport() failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_MSGSEND_FA
SEVERITY: WarningFORMAT: "%s() cntpMsgSend(Queue %s, ptr 0x%x len=%d) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to send a control point message buffer failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_MSGRECV_FA
SEVERITY: WarningFORMAT: "%s() cntpMsgRecv(Queue %s) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to receive a control point message buffer failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-DB_INIT_FAIL
SEVERITY: WarningFORMAT: "Initialization of the RTM Database failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Initialization of the SNMP RTM Database failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-INVALID_SRM_SLO
SEVERITY: WarningFORMAT: "%s() Invalid SRM slot %d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Invocation of a function using an invalid SRM slot."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-UNKNOWN_CARD_TY
SEVERITY: WarningFORMAT: "%s(slot %d, trap %d, seq %d) %s 0x%X."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An attempt to generate a trap resulted in an error. The card type of the originating slot could not be identified."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-INVALID_VARBIND
SEVERITY: WarningFORMAT: "%s() Invalid Varbind type %d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An invalid varbind was detected during processing."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_SEMCREATE_
SEVERITY: WarningFORMAT: "%s() cntpSemBCreate() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to create the control point semaphore failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_SEMTAKE_ER
SEVERITY: WarningFORMAT: "%s() cntpSemBTake(BasisTrapSem 0x%x) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to take the control point semaphore failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_SEMGIVE_ER
SEVERITY: WarningFORMAT: "%s() cntpSemBGive(BasisTrapSem 0x%x) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to give the control point semaphore failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CNTP_MSGBUFTAKE
SEVERITY: WarningFORMAT: "%s() cntpMsgBufTake(dataLn=%d) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to take a control point message buffer failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-7-TRAPS_NOT_ALLOW
SEVERITY: InformationFORMAT: "%s() Trap dropped because they are disallowed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An attempted trap generation was disallowed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-6-TRAPLOG_WRAP
SEVERITY: NoticeFORMAT: "RTM Trap log wrapped around."FLAG: No FlagTHROTTLING One TickEXPLANATION: "The RTM trap log buffer has wrapped around."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-6-RPM_PORT_CLOSED
SEVERITY: NoticeFORMAT: "Port for RPM slot=%d already closed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An attempt to close an RPM port failed because the port was already closed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-RPM_OPEN_PORT_F
SEVERITY: WarningFORMAT: "Opening RPM Port %s for slot=%d failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An attempt to open an RPM port failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-OPEN_PORT_FAILE
SEVERITY: WarningFORMAT: "%s() Opening Port %s failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "An attempt to open an IPC port failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-PROCESS_DEQUEUE
SEVERITY: WarningFORMAT: "%s() Call to process_dequeue(0x%x) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to process_dequeue() failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CREATE_WATCHED_
SEVERITY: WarningFORMAT: "%s() Call to create_watched_queue(%s) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to create_watched_queue() failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-CREATE_NAMED_PO
SEVERITY: WarningFORMAT: "%s() Call to ipc_create_named_port(%s) failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to ipc_create_named_port() failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-IPC_GET_PAK_MSG
SEVERITY: WarningFORMAT: "%s() Call to ipc_get_pak_message() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to ipc_get_pak_message() has failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-IPC_SEND_MSG_FA
SEVERITY: WarningFORMAT: "%s() Call to ipc_send_message() failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A call to ipc_send_message() has failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-MSG_TOO_SMALL
SEVERITY: WarningFORMAT: "%s() Message of len %d was rejected as too small."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A message of a given length was considered too small."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-PXM_SOI_INIT_FA
SEVERITY: WarningFORMAT: "%s() Could not spawn PXM SOI Task."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A message of a given length was considered too small."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-RAM_DB_INIT_FAI
SEVERITY: WarningFORMAT: "%s() Ram DB initialization failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SNMP Ram DB initialization failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-RAMTBL_REGISTRY
SEVERITY: WarningFORMAT: "%s() Ram Table %s registration failed."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SNMP Ram Table registration failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-RAM_TBL_STDBY_U
SEVERITY: WarningFORMAT: "%s() Ram Table 0x%x update failed. Elt = %d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "SNMP Ram Table update to the standby failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-DB_UPDATE_BAD_A
SEVERITY: WarningFORMAT: "%s() Standby update action %d invalid."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Standby Ram update failed. Invalid action requested."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoRTM-5-DB_UPDATE_NUM_E
SEVERITY: WarningFORMAT: "%s() Standby update start elt %d, num elts %d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Standby update needs has the wrong number of elements."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "control-point"
MIBS-5-SEMCREATE_FAILE
SEVERITY: WarningFORMAT: "%s_%d Semaphore Create Failed for %s, return value %x."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can not create semaphore that is required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoMIBS-5-SEMTAKE_FAILED
SEVERITY: WarningFORMAT: "%s_%d Semaphore Take failed for %s, return value %x."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can not take semaphore that is required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoMIBS-5-SEMGIVE_FAILED
SEVERITY: WarningFORMAT: "%s_%d Semaphore Give failed for %s, return value %x."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can not release semaphore which required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoMIBS-5-SEMTAKE_TASK
SEVERITY: WarningFORMAT: "%s_%d Semaphore was taken by Task Id %x, Task Name %s."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can not take semaphore because a timeout has occured and the previous task id that took the semaphore is invalid"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoMIBS-5-SEMTAKE_RECOVER
SEVERITY: WarningFORMAT: "%s_%d Could not recover Semaphore from Task Id %x, Task Name %s."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A time out has occured and the previous task still has the semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "snmp"
SRAT-4-TASKDELAYERROR
SEVERITY: ErrorFORMAT: "%s, %d ssiTaskDelay() error"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Internal error has occured"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SRAT-4-CRD_STATE_EXPIR
SEVERITY: ErrorFORMAT: "%s, %d SNMP_RAT waits for CTC_CD_ACT_PLFM_AVL card state expired, waitcounter = %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Internal error has occured."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SRAT-4-GENERIC_ERROR
SEVERITY: ErrorFORMAT: "%s %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "General Failure."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.DDTS "snmp-sa"
SUBA-4-FAILED_RESOLVE_
SEVERITY: ErrorFORMAT: "%d Could not resolve EPID. Error 0x%x."FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "EPID resolve failed. Subagent will not be registered."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-FAILED_CREATE_E
SEVERITY: ErrorFORMAT: "%dSubagent EPID Creation failed. Error 0x%x."FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "EPID creation failed. Subagent will not be registered."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-FAILED_BIND_EPI
SEVERITY: ErrorFORMAT: "%d Subagent EPID bind failed, Error 0x%x."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to bind EPID. Subagent will not be registered."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-FAILED_MALLOC
SEVERITY: ErrorFORMAT: "%d Failed to allocate memory for %d bytes. Error 0x%x."FLAG: No FlagTHROTTLING One SecondEXPLANATION: "Failed to allocate memory."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-FAILED_IPCMSG_A
SEVERITY: ErrorFORMAT: "%d ssiIpcMessageAllocate failed. Error 0x%x."FLAG: No FlagTHROTTLING One SecondEXPLANATION: "Failed to allocate memory for IPC message."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-FAILED_IPCSEND
SEVERITY: ErrorFORMAT: "%d ssiIpcMessageSend Failed. Error 0x%x."FLAG: No FlagTHROTTLING One SecondEXPLANATION: "Failed to send IPC message. MIB might not be registered/MIB Walk might timeout."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-4-IPCDATAPTR_INVA
SEVERITY: ErrorFORMAT: "%d Invalid IPC Data Pointer."FLAG: No FlagTHROTTLING One SecondEXPLANATION: "The pointer to the IPC data is either empty or invalid"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.SUBA-7-SAREGISTER
SEVERITY: InformationFORMAT: "Subagent is registered."FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "Subagent is registered with master agent."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSUBA-7-SADEREGISTER
SEVERITY: InformationFORMAT: "Subagent is being de-registered %s."FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "Subagent being de-registered due to switchover/reset"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSUBA-7-SASTATECHANGE
SEVERITY: InformationFORMAT: "%d State Change detected for the Subagent."FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "State change detected due to switch over/reset."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSUBA-7-SAREQUEST_FAILE
SEVERITY: InformationFORMAT: "%s Failed due to %s issue."FLAG: No FlagTHROTTLING Five SecondsEXPLANATION: "SNMP Request failed. Get will return NO_SUCH_NAME, Set will return GEN_ERROR."RECOMMENDED ACTION: "Collect information specified in field REQUIRED_INFO and call TAC."REQUIRED INFO "Collect information using following commands. dsplog -mod MIBS dsplog -mod SNMP dsplog -mod SUBAGENT dsplog -sl <slot number specified in the event>."SUBA-5-INVALID_TYPE
SEVERITY : WarningFORMAT : "%d: Invalid message type: expected %d received %d"FLAG : No FlagTHROTTLING : One SecondEXPLANATION : "The message type received is different than what is expected"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO : Collect output from dsplog, dsprev before notifying TAC.DDTS "sntp"
SNTP-4-pSntpInitErr
SEVERITY: ErrorFORMAT: "%s.\n"FLAG: Stack TraceTHROTTLING No ThrottlingEXPLANATION: "Initization Failed."RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."REQUIRED INFO "Issue these command on the prompta) dspverb) dsplogs "SNTP-7-INFO
SEVERITY: InformationFORMAT: "%s.\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "For Information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_D
SEVERITY: InformationFORMAT: "%s. [%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "For Information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_S
SEVERITY: InformationFORMAT: "%s. [%s]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "For Information only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_IP
SEVERITY: InformationFORMAT: "%s. ip %s\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "For Information only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_IPD
SEVERITY: InformationFORMAT: "%s. ip %s [%d]\n"FLAG: No FlagTHROTTLING One HourEXPLANATION: "For Information only. The output will contains IP address and value of index in the server list"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_IPD_RTD
SEVERITY: InformationFORMAT: "%s. ip %s [%d]\n"FLAG: No FlagTHROTTLING One HourEXPLANATION: "For Information only. The output will contains IP address and value of round trip delay"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-INFO_IPD_IPD
SEVERITY: InformationFORMAT: "%s. IP_1 %s[%d], IP_2 %s[%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "For Information only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN
SEVERITY: WarningFORMAT: "%s.\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "It happens when sntp receives unknown message or current server responses with unsync flag on"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN_D
SEVERITY: WarningFORMAT: "%s. [%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN_S
SEVERITY: WarningFORMAT: "%s. [%s]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN_IP
SEVERITY: WarningFORMAT: "%s. ip %s\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN_IPD
SEVERITY: WarningFORMAT: "%s. ip %s [%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-WARN_IPD_IPD
SEVERITY: WarningFORMAT: "%s. ip_1 %s[%d], ip_2 %s[%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR
SEVERITY: WarningFORMAT: "%s.\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_D
SEVERITY: WarningFORMAT: "%s. [%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_S
SEVERITY: WarningFORMAT: "%s. [%s]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_IP
SEVERITY: WarningFORMAT: "%s. ip %s\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_IPD
SEVERITY: WarningFORMAT: "%s. ip %s[%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_IPD_IPD
SEVERITY: WarningFORMAT: "%s. ip_1 %s[%d], ip_2 %s[%d]\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-5-ERROR_UNKNOWN_M
SEVERITY: WarningFORMAT: "receive unknown message %d .\n"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-SNTP_CLIENT_RCV
SEVERITY: InformationFORMAT: "Client receive invalid packet. Err%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSNTP-7-SNTP_SERVER_RCV
SEVERITY: InformationFORMAT: "Server receive invalid packet. Err%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "spvc"
SPFM-3-DRVINIT
SEVERITY: Minor AlertFORMAT: "iosDrvInstall() failed with errno %x, while initing SPFMDRV Driver"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "iosDrvInstall() failed while initing SPFMDRV Driver; FTP access to the SM RAM files may be denied"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM cli take the output of ls C"SPFM-5-SPFM_WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Warning while processing SPVC stats"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "Collect the output of dsplog -mod SPFM"SPFM-7-SPFM_INFORMATIV
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Useful debugging information"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "pxm-connmgm"
SPI-4-SDRV_PATH_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() glcn %d, error-id %d, error-loc %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "This error gets logged to identify a switch Path related problem. It implies an error while programming the conne- ction on the hardware. "RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CD_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() error-id %d, error-loc %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "This error indicates error while initializing card level drivers. The card may not be able to come up under such circumstances."RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_VI_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() vi %d, error-id %d, error-loc %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error activating slot level VIs. This may result in loss of traffic going towards slot # = VI no +1"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_QB_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() qbin %d, error-id %d, error-loc %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error while activating or modifying the Qbins. "RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error error-id %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error while scaling the Qbin or VI rate"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CONNREF_ER
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() conn ref %d line no %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Error trying to reserve an already reserved connref. This implies that connection was incorrectly committed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CONNREF_OU
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Conn Ref out of range error. This will result in the connect- ion not getting programmed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-5-SDRV_PEER_TX_NO
SEVERITY: WarningFORMAT: "Switch Driver Error line no %d connRef=%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "The peer Tx connref wasn't ready when appl (PNNI) bind on an Rx connref. The appl should retry until the Tx conn is setup"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPI-4-SDRV_CONNTYPE_O
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d conn ref=%d conntype=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Conn Type for the connRef is out of range. This would result in connection not getting programmed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_POOL_FULL
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d rsrc=%d, pool=%p"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Pool is full, so resource could not be returned"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_POOL_EMPTY
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d rsrc = %d, pool=%p"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Pool is empty, so unable to get a resource from the pool. This implies that a connection could not get programmed "RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_RSRC_OUTOF
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d rsrc=%x, start=%x, end=%x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Resource return (or set) to pool is out of range (invalid)"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_RSRC_DUP
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d rsrc=%x, pool=%p"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Resource return (or set) to pool duplicated"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CONN_CMT
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Conn Ref has been used. This implies an error while program- ming the connection on the hardware"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CONN_MAP_F
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d conn ref %d conntype %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Error mapping glcns to the connref. This implies that connec- tion could not get programmed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_PATHADD_FA
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d glcn=%d pathType=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Error while programming the connection path on hardware"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_CONN_NOTCM
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Conn Ref has not been committed, so it cannot be modified"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_PATHCFG_FA
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d glcn=%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Path has not been added, so it cannot be modified"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_POOL_CORRU
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d rsrc=%d pool=%p"FLAG: No FlagTHROTTLING One TickEXPLANATION: "The resource pool on Standby PXM is corrupted. This may indi- cate that a connection was not programmed on standby PXM"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_SARLCN_ERR
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d direction=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Unable to get SAR information for a non-SAR conn"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_PATHTYPE_I
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d connType=%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Connref has wrong/invalid pathType. This implies that the connection was not programmed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_POOLGET_ER
SEVERITY: ErrorFORMAT: "Switch Driver Error %s() line no %d connRef=%d connType=%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unable to get resource from the resource pool. This implies that connection was not programmed"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-VISWAPPING
SEVERITY: ErrorFORMAT: "Error VI Swapping may not have happened properly for %d and %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "VI was being serviced while QE0 changed the Utopia address"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-4-SDRV_MEMALLOC_E
SEVERITY: ErrorFORMAT: "Switch Driver Error line no %d."FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error allocating memory during system initialization. Database initialization failed. This may imply that connections did not get added."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredSPI-5-SDRV_OUTOF_CONN
SEVERITY: WarningFORMAT: "Switch Driver Error line no %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can't allocate a connRef. This may be due no resources (connRef, available"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPI-5-SDRV_OUTOF_ROOT
SEVERITY: WarningFORMAT: "Switch Driver Error line no %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can't allocate a Root resource. This may be due no Root resources available"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPI-5-SDRV_OUTOF_LEAF
SEVERITY: WarningFORMAT: "Switch Driver Error line no %d, mce no %d, root no %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Can't allocate a Leaf resource. The maximum leaf per root should be 12"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPI-5-SDRV_INVALID_RO
SEVERITY: WarningFORMAT: "Switch Driver Error line no %d, mce no %d, root no %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Invalid mce or root in R' connref"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "unknown"
SPM-7-SHELFDB_INIT
SEVERITY: InformationFORMAT: "Shelf Archive file header init failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to initialize shelf archive file header."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-7-SPM_SMDB_INIT
SEVERITY: InformationFORMAT: "Slot %u Mib %u Archive Init Failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to initialize slot archive file."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-4-SPM_EPTDB_BAD
SEVERITY: ErrorFORMAT: "SPM database corrupt %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SPM database corruption."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO No Required InfoSPM-7-RM_RAMDB_INIT
SEVERITY: InformationFORMAT: "Resource Mgr Ram DB init failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to initialize Resource Ram Database."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-7-SPM_TIMER_ERROR
SEVERITY: InformationFORMAT: "Timer operation error, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to start the timer."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-7-SPM_MEM_ERROR
SEVERITY: InformationFORMAT: "Memory allocation error, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to allocate memory."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-7-SPM_MSG_ERROR
SEVERITY: InformationFORMAT: "Message send failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to send message."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-7-SPM_ERR_GEN
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "General error."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSPM-4-RM_API_ERROR
SEVERITY: ErrorFORMAT: "%s %d %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "RM Api parameter error."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO No Required InfoSPM-4-RM_NULL_PTR
SEVERITY: ErrorFORMAT: "%s is NULL"FLAG: Stack Trace | Dump TraceTHROTTLING One TickEXPLANATION: "NULL pointer in RM API."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO No Required InfoDDTS "unknown"
SPM-7-SPM_SHELFDB_INI
SEVERITY: InformationFORMAT: "Shelf Archive file header init failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to init shelf archive file header"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_SMDB_INIT
SEVERITY: InformationFORMAT: "Slot %u Mib %u Archive Init Failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to init slot archive file"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-2-SPM_EPTDB_BAD
SEVERITY: Major AlertFORMAT: "SPM database corrupt %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SPM database corruption"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_RM_RAMDB_IN
SEVERITY: InformationFORMAT: "Resource Mgr Ram DB init failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to init Resource Ram Database"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_TIMER_ERROR
SEVERITY: InformationFORMAT: "Timer operation error, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to operate timer"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_MEM_ERROR
SEVERITY: InformationFORMAT: "Memory allocation error, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to allocate memory"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_MSG_ERROR
SEVERITY: InformationFORMAT: "Message send failed, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to send message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPM-7-SPM_TASK
SEVERITY: InformationFORMAT: " %s %d SPM TASK , %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SPM task failure"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "spvc"
SPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC Finite State Machine event handling The meaning of the string is given below x. soft_master_act0102 Fail to allocate leg record(%d,%d,%d) - Failed to allocate one of connection management data structure for SPVC Master endpoint First parameter Logical id of interface Second parameter vpi Third parameter vciRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-4-SWERROR
SEVERITY: ErrorFORMAT: "SOFTWARE ERROR <%d> %d %d %d %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "The meaning for variables in the FORMAT string is given below First parameter can be one of following values:3001 : Connection Management data structure scalling error \3002 : Error n upping and downing connection \3003 : Connetion backward bandwidth error \3004 : Connetion forward bandwidth error \3005 : NSAP Index error \3006 : Resync database error \Second parameter : Logical id of interface \Third parameter : vpi \Fourth parameter: vci \Fifth Parameter : Not used "RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC route optimization - place holder for future use"RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC Redundancy Management - place holder for future use"RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC Configurations - place holder for future use "RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in processing Interfaces/ports failure The meaning for the FORMAT string is given below x. %s() expandSvcRecord Failed pepPtr=%x <%lx %d.%d> - failed to expand SVC records first parameter function name second parameter pointer to SPVC persitent end point data structure Third parameter Interface logical id. Fourth parameter vpi Fifth parameter vciRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC PEP redundancy The meaning for the FORMAT string is given below x. spvcRedmanJrnlItf invalid Event %d - Invalid event detectedRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in handling sig API by SPVCM The meaning of the FORMAT string is given belowRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVM-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVM-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVM-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVM-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in handling SPVC Manager Events The meaning of the FORMAT string is given belowRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVM-7-COMMAND
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Place holder for future use"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in handling SPVC Connection Management Events The meaning of the FORMAT string is given belowRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in SPVC and SVC cross check End-point not found for vpi%d, vci%d on interface0x%x first parameter vpi second Parameter vci third parameter Logical id of interface "RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-7-DINFO
SEVERITY: InformationFORMAT: "DEBUG%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in handling SPVC DCMP messages The meaning for the FORMAT string is given belowRECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Place holder for future use"RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemSPVC-4-ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in Priority Routing This can happen if enqueue/dequeue into priority routing queues fail"RECOMMENDED ACTION: Issue these comamnds on the shell prompta) dspverb) dsplogsc) dsperrsd) dsppnportse) dspconsf) dspconREQUIRED INFO Collect output of these CLIsa) dspver b) dsplogs c) dspvers d) dsppnports e) dspconsf) dspcon for connection in problemDDTS "srm"
SRM-7-SRM_SYNCRAM
SEVERITY: InformationFORMAT: "Event %s received from syncRamManager for DbId %s"FLAG: No FlagTHROTTLING No ThrottlingEXPLANATION: "Information about the Syncram for SRM"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-4-SRM_SYNCRAM_UPD
SEVERITY: ErrorFORMAT: "RAM DB update failed for Standby SRM in bay%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ERROR SRM Application on standby card failed to process the RAM DB update message received from the active card. The function name printed identifies the database on which the update failed."RECOMMENDED ACTION: "This is an application error and might happen due to memory corrpution or a defect. Reset the standby card to see whether the error is transient. If the error is not transient, contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-DBTBLINIT_ERR
SEVERITY: ErrorFORMAT: "Failed to register SRM Database Table %s, NumElm=%d, ElmSize=%d, Upgrd=0x%p, dwngrd=0x%p"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM Application failed to initialize the specified database table. This is a fatal error and might be due to memory corruption or unsupported upgrade or downgrade path. "RECOMMENDED ACTION: "Reset the card to check whether the error is transient if not performing an upgrade or downgrade."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-SRMCT_DBREG_ERR
SEVERITY: ErrorFORMAT: "Failed to register %s database, type = %d, version= %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to register the SRM TASK database. SRMCT task will not spawn properly."RECOMMENDED ACTION: "Contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-DBTBLIDINVLD
SEVERITY: ErrorFORMAT: "%s Table %s is invalid. Table type=%d, idx =%d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unable to read/update database record because of invalid table ID. SRM Application will not operate correctly."RECOMMENDED ACTION: "Contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-HS_INVLD_UPDACT
SEVERITY: ErrorFORMAT: "Invalid Update Action -SRM Bay %d, startElement %d, numElements %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unable to update ram database because of invalid update action."RECOMMENDED ACTION: "Contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-HS_INVLD_UPDATE
SEVERITY: ErrorFORMAT: "Invalid Elements -SRM Bay %d, startElement %d, numElements %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unable to update ram database because of invalid element/range."RECOMMENDED ACTION: "Contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-4-SRMCT_INIT_ERR
SEVERITY: ErrorFORMAT: "Init Error %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRMCT Task initialization error. System will not come up. This is often due to database initialization and registration errors."RECOMMENDED ACTION: "Contact Cisco TAC."REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."SRM-7-SRMCT_CD_INS
SEVERITY: InformationFORMAT: "Got SRM Card Insert Msg. from PMM, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Card insertion notification."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-SRMCT_CD_REM
SEVERITY: InformationFORMAT: "Got SRM Card Remove Msg. from PMM, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Card removal notification."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-SRMCT_BC_INS
SEVERITY: InformationFORMAT: "SRM Back Card inserted or detected, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Successful back card detection."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-BC_MISSING
SEVERITY: InformationFORMAT: "SRM Back Card missing or failed, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unable to detect the back card."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-UNKNOWN_STATE
SEVERITY: InformationFORMAT: "SRMCT entered in unknown state. Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM card in unknown state"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-UNKNOWN_SRM
SEVERITY: InformationFORMAT: "Unknown SRM card detected, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unknown SRM card detected."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-PIO_INIT_FAIL
SEVERITY: InformationFORMAT: "SrmInit Failed to initialise PIOs, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "PIO initialization failure."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-CARD_LOOSE
SEVERITY: InformationFORMAT: "Card Loose;BINS and TINS are High. Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM PIOs indicate that the card is not inserted properly."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-XIL_IMG_ID
SEVERITY: InformationFORMAT: "SRM Xilinx IMG ID. for slot %d, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "XIL image encountered."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-XIL_IMG_ERR
SEVERITY: InformationFORMAT: "SRM Xilinx IMG, Slot %d, %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Function that gets XILimage failed."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-XIL_DNLD_FAIL
SEVERITY: InformationFORMAT: "SRM Xilinx download failed, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM XILINX down failed."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-FPGA_LOAD_FAIL
SEVERITY: InformationFORMAT: "SRM FPGA load failed, Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM FPGA load failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSRM-7-NVRAM_CHECKSUM_
SEVERITY: InformationFORMAT: "SRM NvRam failed. Checksum Error , Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM NvRam failed. Checksum Error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSRM-7-SRMCT_FAIL_MSG
SEVERITY: InformationFORMAT: "Received FAIL msg. from SRBM/SRME Task., Slot %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM card failure message received."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-INVALID_MSG
SEVERITY: InformationFORMAT: "SrmMsgHandler Rcvd. Invalid request"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Invalid SRM message received."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-CLR_SRM_CNF
SEVERITY: InformationFORMAT: "Cleared SRM configuartion for bay %d,"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Successfully cleared SRM configuration."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-CLR_SRM_CNF_ERR
SEVERITY: InformationFORMAT: "Error clearing SRM config for bay %d, error %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Error in clearing SRM configuration."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSRM-4-SRM_HW_UNSUPPOR
SEVERITY: ErrorFORMAT: "SRM CARD FAILED bay = %d, HWREV= %x %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM CARD went in to FAIL state because the hardware revision is not supported."RECOMMENDED ACTION: "Contact Cisco TAC for information about supported SRM hardware revisions."REQUIRED INFO "Note down the HWREV printed in this message."SRM-7-LEGACY_ERR_RPT
SEVERITY: InformationFORMAT: "Srbm Error Rpt %s %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Srbm (SRM-3T3) error has occured."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-7-SRME_ERR_RPT
SEVERITY: InformationFORMAT: "Srme Error Rpt %s %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Srme error has occured."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSRM-7-IPC_ERR
SEVERITY: InformationFORMAT: "Srm IPC Error Rpt %s, errno = 0x%x"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Srm IPC error has occured. Can be ignored during graceful-upgrades or if PXM/SRM is not redundantly configured."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoSRM-7-SRME_UNKNOWN_CL
SEVERITY: InformationFORMAT: "SRME Clock driver Error Rpt %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRME Clock driver Error has occured. Assuming Semtech Clock chip."RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSRM-4-ONLINE_DIAG_ERR
SEVERITY: ErrorFORMAT: "SRM online diagnostic error Error %s, %d, 0x%x, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM/SRME Online diag error has occured."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplogSRM-4-OFFLINE_DIAG_ER
SEVERITY: ErrorFORMAT: "srm offline diag error %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SRM/SRME Offline Diag not supported"RECOMMENDED ACTION: No action requiredREQUIRED INFO "No information required"SRM-7-RAM_SYNC_IOV_FA
SEVERITY: InformationFORMAT: "Call to %s returned error, ramDbId=0x%x"FLAG: No FlagTHROTTLING One TickEXPLANATION: "tRed Ram Sync message create and sending errors"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "atmsig"
SSCO-4-SSCOP_NOMEM_WAR
SEVERITY: ErrorFORMAT: "SSCOP/%s;Out of Mem for%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Required Memory/IPC buffer could not be allocated for the subsystem\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_NOBUF_WAR
SEVERITY: ErrorFORMAT: "SSCOP/%s;Out of IPC Buf for%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Required IPC buffer could not be allocated for the subsystem\n"RECOMMENDED ACTION: This is a temporary condition. If the error message continues to appear, please copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_NOMEM_MAJ
SEVERITY: ErrorFORMAT: "SSCOP/%s;Out of Mem for%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Required Memory could not allocated during system init time\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information:1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_CBPOOL_IN
SEVERITY: ErrorFORMAT: "SSCOP/%s;Cb pool init fail\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Internal memory pool initialization failed during system init time\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_SRCHHELPE
SEVERITY: ErrorFORMAT: "SSCOP/%s;Search helper init fail\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Required Memory could not allocated during system init time\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_EP_CREAT_
SEVERITY: ErrorFORMAT: "SSCOP/%s;EP creat fail for%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Internal IPC endpoints can not be created during system init time\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-2-SSCOP_STG1_INIT
SEVERITY: Major AlertFORMAT: "SSCOP/%s;Stage1 init fail\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Stage1 initialization of internal task structures failed\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-3-SSCOP_INIT_FAIL
SEVERITY: Minor AlertFORMAT: "SSCOP/%s;Init failed\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Task initialization failed\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_CBPOOL_HN
SEVERITY: ErrorFORMAT: "SSCOP/%s;Cb pool handl err;Reason%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Un-initialized or null handle in the internal data structure\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_TMRLIB_ER
SEVERITY: ErrorFORMAT: "SSCOP/%s;Tmr lib err;Reason%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Timer library initialization error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_NULLPTR
SEVERITY: ErrorFORMAT: "SSCOP/%s;Null ptr%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Invalid address error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-7-SSCOP_NULLCTLBL
SEVERITY: InformationFORMAT: "SSCOP/%s;Null Cb;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Control Blk Could not be accessed with the given logical port id\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_NULLIDB
SEVERITY: ErrorFORMAT: "SSCOP/%s;Null idb;Itf Id%d;cb ptr0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Control Block has invalid interface block address\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-6-SSCOP_VCUPMSG
SEVERITY: NoticeFORMAT: "SSCOP/%s;Vc Up Msg Rcvd;Itf Id%d;tx Lcn%d;rx Lcn%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "A VC UP message is received; (Event Not in Use)\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_VCDOWNMSG
SEVERITY: NoticeFORMAT: "SSCOP/%s;Vc Dn Msg Rcvd;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "A VC DOWN message is received; (Event Not in Use)\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-4-SSCOP_VCBINDFAI
SEVERITY: ErrorFORMAT: "SSCOP/%s;LCN bind failed;Itf Id%d;Lcn%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "LCN could not be attached to IPC endpoint\n"RECOMMENDED ACTION: This is a temporary condition. If the error persists and if the error prevented the SSCOP protocol establishment on the corresponding port for which the error is reported and it the port is configured to run SSCOP protocol, copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_CTLBLK_IN
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err in cb insert for itf Id%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Control Block could not be added to internal datastructure\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_CTLBLK_DE
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err in cb del for itf id%d;delr_p%p;dela_ptr%p;Reason%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Control Block could not be deleted from internal datastructure\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_WAVL_DEL_
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err in cb del for cb for itf id%d;Thread%d;Reason%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Control Block could not be deleted from internal datastructure\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_CLR_EPID
SEVERITY: ErrorFORMAT: "SSCOP/%s;Epid(s) clear;Reason%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Delete IPC endpoint(s) due to error in IPC endpoint(s) creation\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-6-SSCOP_INTF_ADD
SEVERITY: NoticeFORMAT: "SSCOP/%s;Cb addition success;itf id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Control Block addtion Successful; (Event not in use) \n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-4-SSCOP_INTF_TXQ_
SEVERITY: ErrorFORMAT: "SSCOP/%s;TxQ Init fail;itf id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Internal Q initialization error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-6-SSCOP_INTF_EXIS
SEVERITY: NoticeFORMAT: "SSCOP/%s;Itf exists;Itf Id%d \n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Duplicate SSCOP add request for an existing interface\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_INTF_NOT_
SEVERITY: NoticeFORMAT: "SSCOP/%s;Itf not exists;Cb not deleted;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Delete SSCOP req received for an non-existing interface\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_INTF_DEL
SEVERITY: NoticeFORMAT: "SSCOP/%s;Cb del success;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP interface deletion successful\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-4-SSCOP_OPENFAIL
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err in prot open;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP protocol open error; (Event not in use)\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_CLOSEFAIL
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err in prot close;Itf Id%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "SSCOP protocol close error;\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-5-SSCOP_VCUNBINDF
SEVERITY: WarningFORMAT: "SSCOP/%s;Lcn unbind Fail;Itf Id%d;Lcn%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "IPC Endpoint LCN unbind error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_FREE_LIST
SEVERITY: ErrorFORMAT: "SSCOP/%s;Cb enq onto free lst fail;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Addition into internal free list failed\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-6-SSCOP_FREE_LIST
SEVERITY: NoticeFORMAT: "SSCOP/%s;Cb 0x%x enq'd to free lst;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Control Block is enqueued to free list (Event not in use)\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-4-SSCOP_CNF_FAIL
SEVERITY: ErrorFORMAT: "SSCOP/%s;Cfg chg incomplete;Cmd%s;Reason%s;Itf id%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Configuration command could not be successfully completed\n"RECOMMENDED ACTION: Retry the configuration request again. If the error persists copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_UNKNOWN_S
SEVERITY: ErrorFORMAT: "SSCOP/%s;Unknown ssi msg;Msg Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unknown IPC message received\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_UNKNOWN_E
SEVERITY: ErrorFORMAT: "SSCOP/%s;Unknown Evt;Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unknown internal event\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_IPC_SEND_
SEVERITY: ErrorFORMAT: "SSCOP/%s;IPC snd fail;From %s tsk to epid 0x%x;Msg Ptr 0x%x;SSI ErrNo0x%x;Msg Type0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "IPC send failure\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_INV_PAK
SEVERITY: ErrorFORMAT: "SSCOP/%s;Inv Pak;Reason%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Internal IPC message conversion failed\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_INV_SSCOP
SEVERITY: ErrorFORMAT: "SSCOP/%s;Inv SSCOP Version 0x%x;Result%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Invalid SSCOP protocol version detected; (Event not in use)\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-6-SSCOP_RESOLV_EP
SEVERITY: NoticeFORMAT: "SSCOP/%s;Resolve incomplete for Ep%s\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Peer tasks IPC endpoint can not be resolved\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_INIT_CB
SEVERITY: ErrorFORMAT: "SSCOP/%s;InitSscopCb;Itf id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP control Block is initialized (Event not in use)\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-6-SSCOP_TMR_EXP
SEVERITY: NoticeFORMAT: "SSCOP/%s;Tmr 0x%x Expiry;Itf Id%d;State0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Timer Expired (Event no in use)\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_TMR_EXP_E
SEVERITY: ErrorFORMAT: "SSCOP/%s;Tmr 0x%x expires wrongly;Itf Id%d;State 0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Timer expiry in wrong state\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-UNEXPECTEDTIMER
SEVERITY: ErrorFORMAT: "SSCOP/%s;Unknown tmr expiry;tmr0x%x;type%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unexpected timer (Event not in use)\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-6-SSCOP_LINK_EST
SEVERITY: NoticeFORMAT: "SSCOP/%s;SSCOP LNK EST;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP Link is established\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_LINK_REL
SEVERITY: NoticeFORMAT: "SSCOP/%s;SSCOP LNK REL;Itf Id%d st%d Rsn%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP Link is released;\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_LINK_RST
SEVERITY: NoticeFORMAT: "SSCOP/%s;SSCOP LNK RST;Itf Id%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP link is reset;\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-4-SSCOP_SEQ_ERR
SEVERITY: ErrorFORMAT: "SSCOP/%s;Err%d;Info%d;port%d;Str%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP protocol sequence error detected \n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-5-SSCOP_PEER_VER_
SEVERITY: WarningFORMAT: "SSCOP/%s;Verify peer UNI ver;Info%s\n"FLAG: No FlagTHROTTLING One MinuteEXPLANATION: "Peer equipment appears to run an old version of ATM UNI\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-5-SSCOP_PEER_VER_
SEVERITY: WarningFORMAT: "SSCOP/%s;Verify Peer UNI ver;Info%s\n"FLAG: No FlagTHROTTLING One MinuteEXPLANATION: "Peer equipment is appears to run an higher version of ATM UNI\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-6-SSCOP_INIT
SEVERITY: NoticeFORMAT: "SSCOP/%s;Prot init;Itf id%d;state %s;Info%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP Control Block is initialized\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-4-SSCOP_PROV_REBU
SEVERITY: ErrorFORMAT: "SSCOP/%s;Rebuild Err;Reason%s;Itf id%d\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Provisioning data rebuild error\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-6-SSCOP_TASK_ST_C
SEVERITY: NoticeFORMAT: "SSCOP/%s;Tsk st chg;Prev st%s;Curr St%s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "SSCOP task changed state\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_TASK_WRON
SEVERITY: NoticeFORMAT: "SSCOP/%s;Tsk rcvd wrong evt0x%x;St0x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Unexpected task change event received\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_TMR_FATAL
SEVERITY: ErrorFORMAT: "SSCOP/%s;Tmr start error;Tmr0x%x\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Timer start error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_TMR_STOP_
SEVERITY: ErrorFORMAT: "SSCOP/%s;Tmr stop error;Tmr0x%x\n"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Timer Stop Error \n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_CONGAPI_E
SEVERITY: ErrorFORMAT: "SSCOP/%s;Cong API Err;ID0x%x;Info10x%x;Info20x%x\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Internal congestion API error\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>SSCO-4-SSCOP_HIRESND_R
SEVERITY: ErrorFORMAT: "SSCOP/%s;Toomany resnd req;port%d;Seqno%d;RsndCnt%d;maxRsndCnt%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Peer is requesting to resend the same PDU too many times\n"RECOMMENDED ACTION:REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problemSSCO-6-SSCOP_DBGLOG
SEVERITY: NoticeFORMAT: "SSCOP/%s;\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Useful debug information\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_DUP_VCUP_
SEVERITY: NoticeFORMAT: "SSCOP/%s;Itf exists;NoLcnChg;Itf Id%d oldRx%d oldTx%d newRx%d newTx%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Received a duplicate VC UP message with No LCN change\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_DUP_VCUP_
SEVERITY: NoticeFORMAT: "SSCOP/%s;Itf exists;LcnChg;Itf Id%d oldRx%d oldTx%d newRx%d newTx%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Received a VC UP message for an already UP port but with different LCNs\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_VC_BIND_M
SEVERITY: NoticeFORMAT: "SSCOP/ VC_BIND_MSGOn port %d rx lcn %d tx lcn %d %s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Received VC BIND message\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_VC_UNBIND
SEVERITY: NoticeFORMAT: "SSCOP/ VC_UNBIND_MSGOn port %d rx lcn %d tx lcn %d %s\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Received VC UNBIND message\n"RECOMMENDED ACTION: No action requiredREQUIRED INFO No Required InfoSSCO-6-SSCOP_INVALID_V
SEVERITY: NoticeFORMAT: "SSCOP Func%s; Var%s;Val%x;Loc%d\n"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Invalid param value in sscop\n"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Please collect the following information1) On the PXM/PXM45 Controller Card CLI execute the following commands andcapture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>DDTS "ssi"
DTAP-4-INVALID_CONID
SEVERITY: ErrorFORMAT: "%s Invalid Connection ID (0x%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Input Connection/Transfer ID is invalid"RECOMMENDED ACTION: "Please capture the following information and call Your Cisco technical support representative "REQUIRED INFO "On PXM451. dspversion2. dsplog - collection the log over a period of two hours to coverwhat has happened before and after this error.3. dsperr for specified slot and the specified error number."DTAP-5-TOOMANYCONS
SEVERITY: WarningFORMAT: "%s The Maximum number of connections are allocated (%d)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error SYNC RAM DB Table is full"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_CONNAME
SEVERITY: WarningFORMAT: "%s The name string (%d) is either 0 or too long (Max %d )"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Connection Name exceeds the maximum allowed or is name length is zero"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_PARM
SEVERITY: WarningFORMAT: "%s Parameter %s has invalid value 0x%x (transferId 0x%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error one of the input parameters has an invalid value assigned to it"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_DATALEN
SEVERITY: WarningFORMAT: "%s Invalid data length %d (Max %d) (transferId 0x%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-4-INVALID_BUFFER
SEVERITY: ErrorFORMAT: "%s Invalid data buffer 0x%x (0x%x) (transferId 0x%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Send/Receive/Alloc message buffer is NULL or has bad magic"RECOMMENDED ACTION: "Please capture the following information and call Your Cisco technical support representative "REQUIRED INFO "On PXM451. dspversion2. dsplog - collection the log over a period of two hours to coverwhat has happened before and after this error.3. dsperr for specified slot and specified error number."DTAP-5-INVALID_RECVAPI
SEVERITY: WarningFORMAT: "%s Invalid API - handler already attached (transferId 0x%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Receive function (EPID handler) has been registered for this connection ID, this makes call to ssiDataTransferReceive() is invalid"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_REREG
SEVERITY: WarningFORMAT: "%s The connection '%s' is already in use"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Input Connection ID has already been registered"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_MSGSIZE
SEVERITY: WarningFORMAT: "%s Invalid size (%d) exceeds the maximum allowed size (%d)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Message size parameter exceeds the maximum allowed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_EPID
SEVERITY: WarningFORMAT: "%s Invalid EPID in DB Table Entry for DBID (%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Failed to get EPID The communication endpoint for this app."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-FAILED_ALLOC
SEVERITY: WarningFORMAT: "%s Data Allocation of size (%d) failed"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Data Transfer API error Failed to allocate buffer "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-FAILED_PROTOEVT
SEVERITY: WarningFORMAT: "%s Protocol Event (%d) failed for conId (%x)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer API error Failed to reset the protocol for a a connection."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDTAP-5-INVALID_FUNC
SEVERITY: WarningFORMAT: "%s Function is not implemented"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Data Transfer API error Function not implemented"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "ssi"
FAS-5-SEMTAKE
SEVERITY: WarningFORMAT: "ssiSemTake failed for %s with errno %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FAS API failed to get fasLfdSem semaphore, hence cannot access file descriptor table"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-2-SEMGIVE
SEVERITY: Major AlertFORMAT: "ssiSemGive failed for %s with errno %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FAS API failed to give fasLfdSem semaphore, hence Remote file access will be frozen"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprevOn slot where it happened1. dspsems2. dspsem <semId of fasLfdSem, 1>3. dsptasks4. dsptask (taskId holding semaphore, level)"FAS-4-FDINVALID
SEVERITY: ErrorFORMAT: "File descriptor (%d) is invalid"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "File descriptor supplied by the application is invalid"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-4-MAXSZTOOSMALL
SEVERITY: ErrorFORMAT: "Max Data Transfer Size (%d) is <= FAS Header size (%d)"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "The Max Data Transfer Size obtained from Data Transfer Module is lesser or equal to the FAS request/response header size. So, no buffer for FAS Data."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-5-NOTREADY
SEVERITY: WarningFORMAT: "File access server is not ready. Semophore %s not initialized"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "File access server is not initialized. Cannot use remote access API yet"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-3-FDFULL
SEVERITY: Minor AlertFORMAT: "Remote file descriptor table is full. Total being used %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Remote file descriptor table is full. Too many remote file transfers happening"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-3-REQUNKNOWN
SEVERITY: Minor AlertFORMAT: "File access server(version %d) received unknown request %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "File access server received unknown request. Protocol error"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-5-DTINUSE
SEVERITY: WarningFORMAT: "This file transfer conection(%x) is already in use"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Present FAS data transfer connection is already doing a file transfer. Another file open request received"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-4-PARAMINVALID
SEVERITY: ErrorFORMAT: "Application supplied an invalid parameter %s"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Application supplied an invalid parameter. Cannot proceed with the API call"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-5-TIDINVALID
SEVERITY: WarningFORMAT: "Data Transfer returned invalid param %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Data Transfer returned invalid param in the callback routine"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-WARNING
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, errMsg %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "General warnings"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-WRVER
SEVERITY: WarningFORMAT: "Protocol version mismatch, expected %d, got %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FAS Protocol version mismatch. Cannot handle received message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-1-CTCDBLD
SEVERITY: FatalFORMAT: "ctcApplGotoDbBuildState() failed with errno%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "ctcApplGotoDbBuildState() failed. Cannot start FAS application"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-1-CTCDBSYNC
SEVERITY: FatalFORMAT: "ctcApplGotoDbSyncState() failed with errno%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "ctcApplGotoDbSyncState() failed. Cannot start FAS application"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-1-CTCGOREADY
SEVERITY: FatalFORMAT: "ctcApplGotoRdyState() failed with errno%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "ctcApplGotoRdyState() failed. Cannot start FAS application"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-5-IPWAIT
SEVERITY: WarningFORMAT: "ssiIpcComEpWait() returned with errno%d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "ssiIpcComEpWait() returned. Going back to ssiIpcComEpWait()"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-1-SEMCREATE
SEVERITY: FatalFORMAT: "ssiSemCreate failed for %s with errno %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FAS API failed to create fasLfdSem semaphone, hence Remote file server will be frozen"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-1-EVTHDLR
SEVERITY: FatalFORMAT: "FAS ctcEventHandler callback returning error %x, for eventtype %x, in routine %s return code %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FAS ctcEventHandler failed to act on the received event"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dsptasks"FAS-2-DRVINIT
SEVERITY: Major AlertFORMAT: "iosDrvInstall() failed with errno %x, while initing FAS Driver"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "iosDrvInstall() failed while initing FAS Driver; FTP access to the SM RAM files may be denied"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "On PXM1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-2-DEVADD
SEVERITY: Major AlertFORMAT: "iosDevAdd() failed with errno %x, for logical partition '%s'"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "iosDevAdd() failed for a logical partition. FTP access to that partition may be denied"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO "Capture the output from1. dspcds2. dsplog3. dsperr4. dsprev5. dspsems6. dsptasks"FAS-5-READOP
SEVERITY: WarningFORMAT: "Read dir op is not supported by this FAS driver"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Read dir op is not supported by this FAS driver"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-LOGPART
SEVERITY: WarningFORMAT: "Logical partition %s not found in the table"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Logical partition not found in the FAS partitions table. The requested partition cannot be accessed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-DEVNM
SEVERITY: WarningFORMAT: "Device Name too long %s "FLAG: No FlagTHROTTLING One TickEXPLANATION: "The request to access a directory found the directory name to exceed valid directory length."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-BDINPUT
SEVERITY: WarningFORMAT: "Failed to process access to STBY %s - %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Access to STBY disk rejected due to invalid parameters."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-BDSTBYSLOT
SEVERITY: WarningFORMAT: "Failed to process access to STBY slot number error from ctc"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Access to STBY disk rejected due to invalid slot number from CTC application"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-DIOFILELOCKTAKE
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, lock type %d, timeout %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ssiDIOFileLockTake() failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-DIOOPEN
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, name %s, flags %d, mode %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ssiDIOOpen() failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-DIOCOPY
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, from %s, to %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ssiDIOCopy() failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-IPCMSGALLOC
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, size %d, priority %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ssiIpcMessageAllocate() returned NULL"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-5-DATAXFERMSGALLO
SEVERITY: WarningFORMAT: "line %d, errno 0x%x, size %d, errMsg %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "ssiDataTransferMsgAlloc returned NULL"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFAS-7-INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "general information"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoDDTS "ssi"
FIPC-1-FATAL_ERROR
SEVERITY: FatalFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FIPC fatal error func()line, Errno, Error Msg"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-2-MAJOR_ERROR
SEVERITY: Major AlertFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FIPC major error func()line, Errno, Error Msg"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-ERROR_STKYES
SEVERITY: ErrorFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "FIPC error with stk trace func()line, Errno, Error Msg"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-ERROR_STKNO
SEVERITY: ErrorFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "FIPC error with stk trace func()line, Errno, Error Msg"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-5-WARNING
SEVERITY: WarningFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "FIPC warning func()line, Errno, Error Msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-7-INFO
SEVERITY: InformationFORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"FLAG: No FlagTHROTTLING One TickEXPLANATION: "FIPC info func()line, Errno, Error Msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-4-COMEPPARAMINVAL
SEVERITY: ErrorFORMAT: "invalid param, %s"FLAG: Stack TraceTHROTTLING No ThrottlingEXPLANATION: "invalid param while modifying EPID info"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-COMEPSEMTAKE
SEVERITY: ErrorFORMAT: "VxWorks error %x taking FIPC semaphore %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Error while acquiring EPID semaphore"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-5-ISRNOTCALLABLE
SEVERITY: WarningFORMAT: "Attempt to take FIPC semaphore %x from interrupt routine"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Attempt to take FIPC semaphore from an interrupt routine"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-MCASTPSLOTINVAL
SEVERITY: WarningFORMAT: "%sInvalid Physical Slot number %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Physical slot number is invalid"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-MCASTPORTINVAL
SEVERITY: WarningFORMAT: "%sMulticast not support on port %d"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Multicast is not supported for this port"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-4-COMEPMALLOCERR
SEVERITY: ErrorFORMAT: "Failed to alloc mem for CommEp array (lstSize %d, arraySize %d)"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to alloc mem for CommEp array"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-NUMCOMEPINVALID
SEVERITY: ErrorFORMAT: "Desired number of Comm Eps %d exceeds the system limit %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Number of EPID's exceeded in the system"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-COMEPMEMAREAERR
SEVERITY: ErrorFORMAT: "Insufficient memory for Comm Ep array Want %d, %d; Got %d, %d"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Insufficient memory for Comm Ep array"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-5-COMEPALLOCFAIL
SEVERITY: WarningFORMAT: "Failed to allocate an FIPC Comm. endpoint at %p"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to allocate an FIPC communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-COMEPFREEFAIL
SEVERITY: WarningFORMAT: "Failed to free an FIPC Comm Endpoint %x"FLAG: No FlagTHROTTLING One TickEXPLANATION: "Failed to free an FIPC communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-COMEPIDINVALID
SEVERITY: WarningFORMAT: "An invalid FIPC_COM_EPID of %p was passed as an argument."FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "An invalid FIPC Communications Endpoint Id was passes"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-5-COMEPDELETED
SEVERITY: WarningFORMAT: "Non-existing CommEp %p has invalid tag %p; Expected tag is %p."FLAG: No FlagTHROTTLING One TickEXPLANATION: "A non-existing communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-COMEPOWNERINVAL
SEVERITY: WarningFORMAT: "Communication Endpoint %x access by non-owner task"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Communication Endpoint being accessed by non-owner task"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-5-COMEPTYPEINVAL
SEVERITY: WarningFORMAT: "Communication Endpoint %x invalid type %x"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Communication Endpoint not IPC plain Async EndPoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO No Required InfoFIPC-4-COMEPSEMINVALID
SEVERITY: ErrorFORMAT: "Invalid semaphore %p in Comm Ep %p"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Invalid semaphore in a Communications Endpoint"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-4-COMEPNAMEINVAL
SEVERITY: ErrorFORMAT: "Communication Endpoint's %x global name %s too long"FLAG: Stack TraceTHROTTLING One TickEXPLANATION: "Communication Endpoint's global name is too long"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.FIPC-5-COMEPNAMESCOINV
SEVERITY: WarningFORMAT: "Name Scope %d is invalid"FLAG: No FlagTHROTTLING One Tick<