Available Languages

Download Options

PDF (1.9 MB)
View with Adobe Reader on a variety of devices

Updated:June 5, 2017

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Cisco cBR Series Converged Broadband Routers System Messages

Revised: August 29, 2019

Overview of System Messages

Use this document together with the tools and utilities that are available on Cisco.com on this page:

http://www.cisco.com/c/en/us/support/index.html

■ Cisco Technical Assistance Center (TAC): https://mycase.cloudapps.cisco.com/case

■ Bug Search Tool link: https://bst.cloudapps.cisco.com/bugsearch/

Note: When contacting TAC, please have available the nonzipped, plain-text (.txt) output of the show logging and show tech-support commands, as well as any pertinent troubleshooting logs.

System messages can be grouped into these categories:

■ System Event Messages—Describe the system and error messages that are generated for events related to the Cisco platform, and its hardware and software components.

■ DOCSIS Event Messages—Describe the error messages for events as required by the DOCSIS specifications.

■ Video/QAM Event Messages—Describe the error messages for events as required by the Video specifications.

System error messages begin with a percent sign (%) and are structured as follows:

%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text

System error messages contain the following components:

■ FACILITY is a code indicating the platform or other component that is generating the message.

■ SEVERITY is a number that reflects the significance of the error message. All error messages have a Cisco severity number that ranges from 0 to 7. DOCSIS-related events also contain a DOCSIS severity level that ranges from 129 to 136. The lower the number, the more serious the situation. This table describes the possible severity levels and their meanings.

Cisco Level	DOCSIS	Class	Description
0	129	Emergency	The system has become unusable and requires immediate attention. This problem might also be affecting other parts of the network.
1	130	Alert	Some type of system or connection failure has occurred and requires immediate attention.
2	131	Critical	An error occurred that requires immediate attention to avoid system or connection failure.
3	132	Error	An error condition occurred that requires attention to resolve. Failure to address this problem will result in some type of system or connection failure in the near future.
4	133	Warning	A condition occurred that indicates attention is needed in near future to avoid potential problems. Failure to address this problem could result in some type of system or connection failure later on.
5	134	Notice	A situation occurred that is normal but is significant enough that system administrators might want to notice.
6	135	Informational	An information message that might or might not be significant to the system administrators.
7	136	Debug	Messages that appear only while debugging is turned on.

■ MNEMONIC is a string that uniquely identifies the error message. Error messages are usually organized and referred to by their mnemonic value.

■ The Message-text is a string that provides details about the particular error. This string can include specifics about cable interface, IP or MAC addresses, and other information. In this document, the specific information is presented by variable fields that are indicated by square brackets ([ ]). A decimal number, for example, is represented as [dec].

System Messages Description

B

BIPC

%BIPC-3-SESSION_INVALID : Invalid Session Slot=[dec] Session=[hex]

Explanation An internal software error has occured. The IPC session was incorrectly not deleted when the slot went down.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%BIPC-6-SESSION_DOWN : IPCCL Session to [chars][dec] is DOWN

Explanation An internal software debug info to notify IPCCL session to specific slot went down.

Recommended Action No action is required.

%BIPC-6-SESSION_UP : IPCCL Session to [chars][dec] is UP

Explanation An internal software debug info to notify IPCCL session to specific slot went up.

Recommended Action No action is required.

C

CABLE_CLC

%CABLE_CLC-3-CONFIG_MISMATCH : Card type mismatch. config: [chars] is not consistent with the working mode in slot [dec]

Explanation There are several scenarios that the error message will be reported. Some cases can be recovered by CLC auto reloading. Eg. Kobal-R can work as 10GE or 100GE ifmod for DPIC-G2. If system reload with card pre-configured as DPIC-G2-10GE 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE', while .board.conf was saved as DPIC-G2 100GE mode and Kobal boot up before card precfg parsing. Some cases need to shut down the lc first then change the configuration or change the pic card Eg. if the card is pre-configured as RPHY with the command 'card <slot_num>/0 cBR-CCAP-LC-40G r-phy', but a rf-pic card was inserted to the same slot. Or the card is pre-configured as ICMTS with the command 'card <slot_num>/0 cBR-CCAP-LC-40G', but a dpic card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G2 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE', but a DPIC-G1 card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G1 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy', but a DPIC-G2 card was inserted to the same slot.

%CABLE_CLC-3-UNSUPPORTED_DATA : Data conversion error ([chars], [hex])

Explanation An internal software error has occured when converting the data specified in the message from one representation to another.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CABLE_CLC-4-LCLOG_PARSE_ERR : Error parsing logger message: [chars] from subslot [int]/[int]

Explanation The carrier card passed down a logger message that could not be parsed.

%CABLE_CLC-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes

Explanation The carrier card passed down a logger message that is too long for the RP to handle.

%CABLE_CLC-4-LOGGERMSGTOOBIG : Logger message length ([int] bytes) exceeds the maximum allowed size

Explanation The carrier card attempted to send a large message to the Route Processor

%CABLE_CLC-5-LOGGER_LC_REMOVED : Carrier Card [dec] removed

Explanation The carrier card was removed

Recommended Action No action is required.

CABLE_IPCCL_LIB

%CABLE_IPCCL_LIB-4-EAGAIN : ipccl port [chars] throttling on, port curr_pending msg ([dec])[conf_high_watermark ([dec])-conf_low_watermark ([dec])]. current oustanding msg waiting for ack ([dec]). client_id [chars] svc_id [chars] msg_type [dec] d_slot [dec]

Explanation IPCCL port throttling on

Recommended Action Application should check whether they send too much msg, and better to slow down

%CABLE_IPCCL_LIB-4-SVC_EAGAIN : ipccl svc_id [chars] throttling on, svc current q_size ([dec])[high_watermark ([dec])-low_watermark ([dec])]. port_id [chars] client_id [chars] msg_type [dec] d_slot [dec] session_id [int]

Explanation IPCCL service throttling on

Recommended Action Application should check whether they send too much msg, and better to slow down

%CABLE_IPCCL_LIB-5-LOW_WATERMARK : ipccl port [chars] hit low watermark, port current pending msg ([dec])[conf_high_watermark ([dec])-conf_low_watermark ([dec])]. current oustanding msg waiting for ack ([dec]). client_id [chars] svc_id [chars] msg_type [dec] d_slot [dec]

Explanation IPCCL port watermark hit

Recommended Action Application should check whether they send too much msg, and better to slow down

%CABLE_IPCCL_LIB-5-SVC_LOW_WATERMARK : ipccl svc_id [chars] hit low watermark, svc current q_size ([dec])[high_watermark ([dec])-low_watermark ([dec])]. port_id [chars] client_id [chars] msg_type [dec] d_slot [dec] session_id [int]

Explanation IPCCL service watermark hit

Recommended Action Application should check whether they send too much msg, and better to slow down

CABLE_UTIL

%CABLE_UTIL-3-CARD_MISMATCH_ERR : Configure Mismatch: Config:[chars]; Card:[chars]

Explanation There are several scenarios that the error message will be reported. One case is line card boot up mode for different PIC type does not match to pre-configured PIC type. There two modes of the line card : ICMTS&RPHY and Kobal-R can work with DPIC-G1 or DPIC-G2 with different FW. Eg. if the card is pre-configured as RPHY with the command 'card <slot_num>/0 cBR-CCAP-LC-40G r-phy', but a rf-pic card was inserted to the same slot. Or the card is pre-configured as ICMTS with the command 'card <slot_num>/0 cBR-CCAP-LC-40G', but a dpic card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G2 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-<ifmod>', but a DPIC-G1 card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G1 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy', but a DPIC-G2 card was inserted to the same slot. Another case is Kobal-R working ifmod mismatch to precfg. Eg. if system reload with card pre-configured as DPIC-G2-10GE 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE', while .board.conf was saved as DPIC-G2 100GE mode and Kobal boot up before card precfg parsing, then this error message will be reported, however, it can be recovered by CLC auto reloading.

Recommended Action change the pre-config to another mode or replace the pic card

%CABLE_UTIL-4-DC_INVOKE_ERR : Dynamic Command [chars] invoke failure

Explanation The dynamic Command parse failed.

CARD_STATE

%CARD_STATE-3-CARD_UNSUPPORT : Card in slot [int] with type ([chars]) is not supported in version [int].[int], Upgrade right software version to support card.

Explanation The linecard inserted does not supported in currently running software.

Recommended Action Replace the unsupported card or upgrade to right software.

%CARD_STATE-3-TYPE_MISMATCH : Mismatched card type ([chars]) in slot [dec]. Expected type [chars]. Use 'no card' command to override preprovisioning and update card type.

Explanation The linecard inserted does not match the currently provisioned card type.

Recommended Action Replace wrong board type with currently provisioned board type, or type 'no card' to allow new card type to be discovered.

%CARD_STATE-3-UNEXPECTED : Unexpected error on slot [dec]: [chars]

Explanation An unexpected error has occured while performing a linecard OIR action

%CARD_STATE-4-FORCE_RESET : Reset slot [int] for reason: [chars]

Explanation The SUP forced a linecard to reload for the reason.

%CARD_STATE-4-INCONSISTANT : Gemini version inconsistant: slot [dec] daughter board [dec], version [chars] slot [dec] daughter board [dec], version [chars]

Explanation Different Gemini in chassis, CBR only supports the same hardware version US modules.

Recommended Action Replace the Gemini to let the version of the Gemini in two slots be the same.

%CARD_STATE-4-LEOBEN_MISMATCH : Leoben version mismatch: slot [dec], version [chars] slot [dec], version [chars]

Explanation Different Leoben in chassis, CBR only supports the same hardware version US modules.

Recommended Action Replace the Leoben to let the version of the Leoben in two slots be the same.

CBR

%CBR-0-CPUCARD : CMTS([dec]/[dec]), Init failed, CSR[dec]=[hex].

Explanation Most likely Hardware failure

Recommended Action Replace defective Line Card

%CBR-0-TEMPHIGH : [chars] measured at [chars] is too high: shutdown temperature [chars]

Explanation Current temperature exceeds the max shutdown temperature

Recommended Action Determine cause of the high temperature and correct if possible.

%CBR-0-VOLTHIGH : [chars] measured at [chars] is too high: shutdown voltage [chars]

Explanation Current voltage exceeds the max shutdown voltage

Recommended Action Determine cause of the high voltage and correct if possible.

%CBR-0-VOLTLOW : [chars] measured at [chars] is too low: shutdown voltage [chars]

Explanation Current voltage exceeds the min shutdown voltage

Recommended Action Determine cause of the low voltage and correct if possible.

%CBR-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay

Explanation Most likely system or hardware failure

Recommended Action Replace Line Card

%CBR-2-CPE_MGMT_IDX_ERR : Index out of range during CPE MGMT data decoding

Explanation The index is out of range during CPE MGMT HCCP data decoding.

Recommended Action Contact Cisco with this log message

%CBR-2-LOG_CON_SYS_CRIT : [chars] logging console level to [dec] from [dec], Rate-limit level [dec], [chars].

Explanation Logging console restricted during critical situations

Recommended Action Please run 'show logging' to view all sys-logged messages

%CBR-2-NOMEMORY : Failure to create new IPv6 entry [IPV6 address]

Explanation Unable to malloc a buffer to create a new entry to add Ipv6 addr

Recommended Action Enter a show chunks command and report the output, along with this error message, to your technical support representative.

%CBR-3-ACFE_FAILURE : [chars]

Explanation A failure occurred in ACFE algoirhtm module

%CBR-3-ALARM_ERROR : [chars]

Explanation General error information.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

%CBR-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER : <132>CMTS[DOCSIS]:<66030206> Auth Invalid -Invalid Key Sequence Number. CM Mac Addr <[enet]>

Explanation Auth Invalid-Invalid Key Sequence Number

Recommended Action No action is required.

%CBR-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE : <132>CMTS[DOCSIS]:<66030207> Auth Invalid -Message(Key Request) Authentication Failure . CM Mac Addr <[enet]>

Explanation Auth Invalid Message Authentication Failure

Recommended Action No action is required.

%CBR-3-AUTH_INVALID_NO_INFORMATION : <132>CMTS[DOCSIS]:<66030202> Auth Invalid -No Information. CM Mac Addr <[enet]>

Explanation Auth Invalid No Information

Recommended Action No action is required.

%CBR-3-AUTH_INVALID_UNAUTHORIZED_CM : <132>CMTS[DOCSIS]:<66030203> Auth Invalid -Unauthorized CM. CM Mac Addr <[enet]>

Explanation Auth Invalid Unauthorized CM

Recommended Action No action is required.

%CBR-3-AUTH_INVALID_UNSOLICITED : <132>CMTS[DOCSIS]:<66030205> Auth Invalid -Unsolicited. CM Mac Addr <[enet]>

Explanation Auth Invalid Unsolicited

Recommended Action No action is required.

%CBR-3-AUTH_REJECT_NO_INFORMATION : <132>CMTS[DOCSIS]:<66030102> Auth Reject -No Information . CM Mac Addr <[enet]>

Explanation Auth Reject No Information

Recommended Action No action is required.

%CBR-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE : <132>CMTS[DOCSIS]:<66030108> Auth Reject -Permanent Authorization Failure . CM Mac Addr <[enet]>

Explanation Auth Reject Permanent Authorization Failure

Recommended Action No action is required.

%CBR-3-AUTH_REJECT_TOD_NOT_ACQUIRED : <132>CMTS[DOCSIS]:<66030109> Auth Reject -Time of Day not acquired . CM Mac Addr <[enet]>

Explanation CM Auth Rejected. TOD not acquired.

Recommended Action No action is required.

%CBR-3-AUTH_REJECT_UNAUTHORIZED_CM : <132>CMTS[DOCSIS]:<66030103> Auth Reject -Unauthorized CM . CM Mac Addr <[enet]>

Explanation Auth Reject Unauthorized CM

Recommended Action No action is required.

%CBR-3-AUTH_REJECT_UNAUTHORIZED_SAID : <132>CMTS[DOCSIS]:<66030104> Auth Reject -Unauthorized SAID. CM Mac Addr <[enet]>

Explanation Auth Reject Unauthorized SAID

Recommended Action No action is required.

%CBR-3-BADARPDELETE : Tried to remove arp entry for [IP_address] that is not dynamic

Explanation Tried to delete non-dynamic arp entry - possible spoof attempt

Recommended Action Look for possible CMTS IP address spoofing attempt

%CBR-3-BADFFTINTERRUPT : BCM3138 chip [dec] dma interrupt error.

Explanation FFT dma interrupt error occured.

Recommended Action No action is required.

%CBR-3-BADFFTSTATE : BCM3138 chip [dec] is in wrong state [dec], expected state [dec]

Explanation Impossible state has been reached.

Recommended Action No action is required.

%CBR-3-BADUSPORT : Interface [chars] U[dec] invalid, highest port number is U[dec]

Explanation Upstream port number must be valid.

Recommended Action Redo command with valid upstream port number.

%CBR-3-BPI_ENFORCE : Blocking CPE=[enet] CM=[enet] sid [dec] interface [chars]: CPE blocked

Explanation CMTS glean function received blocked cpe mac addr

Recommended Action Check for bpi-plus-policy: CPE blocked mac addr

%CBR-3-BPI_ERR : [chars] [dec] [dec] [dec]

Explanation BPI Error

Recommended Action No action is required.

%CBR-3-BPI_ERR_DOCSIS : [chars] [enet] [dec] [dec]

Explanation BPI DMP Error

Recommended Action Check BPI DMP Module

%CBR-3-BPI_ERR_UMP : [chars] [enet] [dec] [dec]

Explanation BPI UMP Error

Recommended Action Check BPI UMP Module

%CBR-3-BUN_MCAST_INIT : Unable to allocate memory for bundle multicast initialization.

Explanation An internal software error occured

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-BUN_MCAST_NOFREE_MAC : Fail to allocate free Bundle Multicast Map Entry for Bundle:[dec] Group:[IP_address] Source:[IP_address] IDB:[chars]

Explanation An internal software error occured

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-BUN_MCAST_REV_MAP_ERR : Unable to find the Multicast Mapped Entry from reverse-mapping table for Bundle: [dec] MAC:[enet]

Explanation An internal software error occured

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-CHASSIS : Unknown chassis model.

Explanation Data stored in midplane is bad or incomplete.

Recommended Action Contact technical support to update your system.

%CBR-3-CM_CERTIFICATE_ERROR : <132>CMTS[DOCSIS]:<66030111> CM Certificate Error. CM Mac Addr <[enet]>

Explanation CM Certificate error.

Recommended Action No action is required.

%CBR-3-CM_CERTIFICATE_FORMAT_ERROR : <133>CMTS[DOCSIS]: CM Certificate Format Error

Explanation CM Certificate Format Error

Recommended Action No action is required.

%CBR-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR : <133>CMTS[DOCSIS]:<0> CM Certificate Self-Verfication Error

Explanation CM Certificate Self-Verfication Error

Recommended Action No action is required.

%CBR-3-CMTS_QUACK_FAIL_ERR : [chars]

Explanation This LC requires programmed Quack IDPROM.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-CMTS_RCC_CREATION_FAILURE : RCC creation failure -ID [dec], host [chars]

Explanation RCC creation failed due to list insert failure.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-CMTS_TCC_RNG_INVALID_SB : TCC RNG on Interface [chars] with invalid SB for CM [enet]

Explanation TCC RNG could not get a valid subblock for the interface that the CM is ranged on. SW Bug.

Recommended Action No action is required.

%CBR-3-CONFIG : Exceeds [dec] [chars]

Explanation The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.

Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.

%CBR-3-DBDSPDEAD : AWACS Slot [dec] is dead

Explanation Daughter board DSP hungs

Recommended Action Reload image, if still fail, replace defective daughter board

%CBR-3-DBDSPDOWNLOADERR1 : DSP FAILED TO RESPOND TO INIT_DOWNLOAD CMD.

Explanation Failed initiating DSP downloading

Recommended Action Reload image, if still fail replace defective daughter board

%CBR-3-DBDSPDOWNLOADERR2 : Failed downloading.

Explanation Failed DSP downloading

Recommended Action Reload image, if still fail replace defective daughter board

%CBR-3-DBDSPDOWNLOADERR3 : FAILED DOWNLOADING OF DSP FW DUE TO CHECKSUM FAILURE.

Explanation Failed last step of DSP downloading

Recommended Action Reload image, if still fail replace defective daughter board

%CBR-3-DBDSPDOWNLOADPASS1 : INIT DOWNLOAD OF DSP F/W PASS.

Explanation The DSP firmware download initiation was successful

Recommended Action No action is required.

%CBR-3-DBDSPDOWNLOADPASS2 : DOWNLOAD OF DSP F/W SUCCESS.

Explanation The DSP firmware download was successful

Recommended Action No action is required.

%CBR-3-DBDSPDOWNLOADPASS3 : END DOWNLOAD OF DSP F/W SUCCESS.

Explanation The DSP firmware end download was successful

Recommended Action No action is required.

%CBR-3-DBDSPERR1 : DSP SRAM failed

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR2 : DSP SRAM semaphore failed

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR3 : DSP side dual-port SRAM failed

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR4 : DSP FLASH memory failed

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR5 : DSP failed to respond to Host Handshake

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR6 : Switching to backup dsp image failed

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBDSPERR7 : Switching again to regular dsp image failed

Explanation Daughter board regular image corruption failure

Recommended Action Replace with BACKUP image

%CBR-3-DBDSPIDERR : DSP id read [hex],expect [hex]

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBFPGADLERR : [chars]

Explanation XILINX FPGA download failure

Recommended Action Reload image, if still fail replace defective line card

%CBR-3-DBFPGAERR : XILINX not up, reset reg is [hex]

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBPLX9050ERR : Plx9050 id read [hex],expect [hex]

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DBPLX9080ERR : Plx9080 id read [hex],expect [hex]

Explanation Daughter board hardware failure

Recommended Action Replace defective daughter board

%CBR-3-DDC_INVALID_HASHTYPE : The hash type [dec] for hash id [dec] is invalid

Explanation Software does not recognize the configured hash type

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-3-DDC_INVALID_STATICMAP : The node [dec] for mac-address [enet] exceeds maximum configured nodes

Explanation A mapping specified by the oui-map or mac-map commands exceeds the configured number of participant nodes

Recommended Action Fix configuration

%CBR-3-DDC_UNEXPECTED_NODES : The number of nodes [dec] is invalid

Explanation The number of nodes is either smaller or greater than the limits supported by the platform

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-3-DISCOVER_FAIL : [chars]

Explanation Unable to discover physical entity

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-DIV_BY_ZERO_ERROR : Divide by zero attempted error [chars]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-DOCSIS_SYNC_SF : cminstp is NULL: [chars].

Explanation No valid cminstp is found for sid referenced in this checkpoint msg, message will be dropped

Recommended Action No action is required.

%CBR-3-DS_FLOW_INCONSIST_WB_INFO : DS Flow Error: [chars] [enet] prim_rfid [dec] sfid [dec] wb_mode [dec] forw_chid [dec] [chars]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-DSX_DUP_TRANSC_SAME_ID : [chars] Err: [enet] [dec] ([chars]/[chars]) ([dec]/[dec]) ([dec]/[dec])

Explanation Duplicated DSX transaction with the same ID.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-ENVM_FAN_OVERLOAD : Fan Tray overloaded, fail to support the linecard at slot [dec]

Explanation The cooling power provided by the routers's fans is lower than some LCs in chassis required.

Recommended Action Replace the fan as soon as possible or the system may shut itself down or fail to operate properly.

%CBR-3-FLOW_ERR : Flow error sfid [dec] sid [dec] CM Mac address <[enet]>

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-FPSUBINIT : Unable to create subinterface [chars] for hw interface [chars]

Explanation The system was unable to create the cable subinterface data structures

Recommended Action Gather information about running configuration and amount of memory in the system and file a bug

%CBR-3-GRD_HCCP_RECOVER : Wideband-Cable[int]/[int]/[int]:[int] not recovered after switchover

Explanation After a switchover or revert where the modular-host for a SPA becomes active on the standby, a wideband interface on that SPA is not recovered. This is most likely due to a software problem.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-GRD_HCCP_REMOVE : Wideband-Cable[int]/[int]/[int]:[int] not removed

Explanation When the modular-host configuration for a SPA is removed, a wideband interface on that SPA is not removed. This is most likely due to a software problem.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-HUNGFFTSTATE : BCM3138 chip [dec] is not idle for [dec] retries

Explanation BCM3138 FFT processor stuck

Recommended Action No action is required.

%CBR-3-I2CERR : [chars]

Explanation ERROR while accessing the i2c bus

Recommended Action Error has occured while accessing the internal bus.

%CBR-3-I2CUPXERR : [chars]

Explanation ERROR while accessing the Upconverter

Recommended Action Error occured while accesing the upconverter.

%CBR-3-INTERCEPT : Interface [chars], Failed to send intercept packet to server [IP_address]:[dec]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-INVALID_BP_CONFIGURATION_SETTING_VALUE : <132>CMTS[DOCSIS]:<66010200> Invalid BP Configuration Setting Value for TLV type [dec]. CM MAC Addr <[enet]>

Explanation Invalid BP Configuration Setting Value

Recommended Action No action is required.

%CBR-3-INVALID_INVOKE_FROM_ISR : Invalid [chars] from interrupt level [dec]

Explanation Invalid operation from ISR context. Possible recurrence of CSCek63728

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-INVALID_US_CHID : Invalid Upstream Channel ID

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-IPCRECVERR : Internal RP-CLC/CLC-CLC IPC receive error from [dec]/[dec]

Explanation Internal IPC receive error

Recommended Action No action is required.

%CBR-3-IPDR_BUFFER_ERR : unable to alloc buffer because percent of free memory is [dec] (which is below [dec])

Explanation The IPDR feature requires memory to hold record. Since insufficient memory it might result in lost IPDR data

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-IPDR_FILESYS_FULL : File [chars] cannot be created/written since filesystem is full.

Explanation The IPDR feature requires a file to be written to filesystem. Since filesystem is full it might result in lost IPDR data.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-IPDR_GET_MACDOMAIN_ERR : The IPDR CM-US failed to get MAC domain with slot[[dec]], subslot[[dec]], slotunit[[dec]].

Explanation The IPDR CM-US failed to get MAC domain by docsIf3CmtsCmRegStatusId.

Recommended Action Ignore this IPDR record, collecting records at next interval.

%CBR-3-IPDR_SFLOG_FILE_ERR : The IPDR failed to handle file: [chars]

Explanation The IPDR failed to handle file

Recommended Action Check the file system

%CBR-3-IPV4ADDRERR : Host with invalid IPv4 address. Master Interface [chars] Input Interface [chars] MAC = [enet] IP = [IP_address]

Explanation Most likely a sw error of the packet sender

Recommended Action Check the modem and subscriber

%CBR-3-IPV6ADDRERR : Host with invalid IPv6 address. Master Interface [chars] Input Interface [chars] MAC = [enet] IP = [IPV6 address]

Explanation Most likely a sw error of the packet sender

Recommended Action Check the modem and subscriber

%CBR-3-IPV6SOCKETFAIL : IPv6 TFTP server socket

Explanation Could not open the IPv6 TFTP server socket

Recommended Action Make sure the /ip tftp-server / CLI is not configured

%CBR-3-JIB_Q_LENGTH_PHS_ERR_DETECTED : JIB Upstream Queue Length or PHS Rule Failure Detected.

Explanation JIB Upstream internal queue length error; or Bad PHS Rule Entry

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-KEY_REJECT_NO_INFORMATION : <132>CMTS[DOCSIS]:<66050102> Key Reject -No Information. CM Mac Addr <[enet]>

Explanation Key Reject, No Information

Recommended Action No action is required.

%CBR-3-KEY_REJECT_UNAUTHORIZED_SAID : <132>CMTS[DOCSIS]:<66050103> Key Reject -Unauthorized SAID. CM Mac Addr <[enet]>

Explanation Key Reject, Unauthorized SAID

Recommended Action No action is required.

%CBR-3-L2VPNMAXLIMIT : L2VPN XCONNECT PW max limit of [int] pseudo-wires reached.

Explanation L2VPN XCONNECT PW max limit of pseudo-wires reached.

Recommended Action Cannot configure anymore pseudo-wires

%CBR-3-LB_IF_DISABLED : Disabled interface [chars]

Explanation Load balance disabled the interface because this could not move any modem in and out of it.

Recommended Action Check if any modem can be online with this interface, then check the path of RF channel, and check if upstream and downstream channels are associated as expected in topology

%CBR-3-LB_MODEM_FAILED : Failed to move modem [enet] from [chars] to [chars].

Explanation Load balance failed to move the modem from one interface to another.

Recommended Action Check if any other modem can be online with this interface, then check the path of RF channel, and check if upstream and downstream channels are associated as expected in topology

%CBR-3-LB_STALE_PENDING_CM : This is a pre-exist pending entry, detailed information as: [enet] action [hex]:[hex] client [dec]:[dec] count update flag [dec]

Explanation Stale pending CM exist

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-MACADDRERR : Upstream packet from host with non unicast MAC address. Master Interface [chars] Input Interface [chars] SID = [dec] MAC = [enet]

Explanation Most likely a sw error of the packet sender

Recommended Action Check the modem and subscriber

%CBR-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR : <133>CMTS[DOCSIS]: CM MAC Addr <[enet]> on Interface [chars] U[dec] : [chars]

Explanation Manufacture CA Certificate Format Error

Recommended Action No action is required.

%CBR-3-MAPPED_TO_EXISTING_SAID : <132>CMTS[DOCSIS]:<66060600> Mapped to existing SAID. CM Mac Addr <[enet]>

Explanation Mapped to existing SAID

Recommended Action No action is required.

%CBR-3-MAPPED_TO_NEW_SAID : <132>CMTS[DOCSIS]:<66060700> Mapped to new SAID. CM Mac Addr <[enet]>

Explanation Mapped to new SAID

Recommended Action No action is required.

%CBR-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC : <132>CMTS[DOCSIS]:<66060509> Map Reject -Not Authorized for requested downstream traffic flow. CM Mac Addr <[enet]>

Explanation Map Reject - Not Authorized for requested downstream traffic flow

Recommended Action No action is required.

%CBR-3-MAX_DS_SF_ERROR : Maximum limit for downstream service-flows reached

Explanation The number of DS service-flows cannot exceed 50

Recommended Action No action is required.

%CBR-3-MAX_DYN_DS_SF_ERROR : Maximum limit for dynamic downstream service-flows reached

Explanation The number of dynamic DS service-flows cannot exceed 31

Recommended Action No action is required.

%CBR-3-MONITOR : Interface [chars], Failed to send monitored packets

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-MONITOR_ACCESS_FILTER : Null access list

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-MONITOR_EMPTY : Unable to allocate packet with rx_type = [dec]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-NEG_PENDING : Negative decrement of pending stats on [chars] for [enet]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-NOFORK : Could not start Spectrum Management process

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-NOMAC : Can't allocate MAC address for interface [int]/[int]

Explanation Your system is out of available MAC addresses.

Recommended Action Contact technical support.

%CBR-3-NOMEM : [chars]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-NOMORESIDS : Maximum number of SIDS have been allocated for interface [chars]: CM [enet]: SID container info: start [dec] end [dec]

Explanation The Maxmium number of SIDS has reached

Recommended Action Assign Cable Modem to another Line Card

%CBR-3-NOTCMTS : Device reported [hex]

Explanation Most likely hardware failure

Recommended Action Replace defective hardware

%CBR-3-NULLHWIDB : A Null hwidb prevents the acl update for a modem's associated hosts , MAC [enet] SID [dec]

Explanation A failure occurred in trying to update acl for a modem's associated host

Recommended Action No action is required.

%CBR-3-NULLIDBTTSVTBL : A Null sw idb prevents pxf src-vfy tables from being updated, MAC [enet] SID [dec]

Explanation A failure occurred in trying to update pxf src-vfy tables

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

%CBR-3-NULLMAPPTR : Cannot send maps as current_map ptr is NULL, ds->[hex],current_map->[hex]: [chars]

Explanation This is an internal error, or may indicate a memory problem.

Recommended Action Check your available memory. If necessary, add more memory to the system.

%CBR-3-OFDMA_IUC_CHANGE_ERR : OFDMA IUC change error: cm [enet] [chars]

Explanation Changing OFDMA service flow IUC failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-OWNERR : CMTS([dec]/[dec]), Buffer ownership error, pak=[hex].

Explanation Most likely hardware failure

Recommended Action Replace defective board

%CBR-3-PA_REM_ENQFAIL : Enqueue of message failed slot ([dec])

Explanation Enqueue of a PA removal message to an event queue failed

%CBR-3-PA_REM_GENERAL : [chars]

Explanation A general failure occured in the operation of the PA removal event state machine as defined by the failure string

%CBR-3-PA_REM_PCI_ERROR : PCI error address = [hex]

Explanation An unexpected PCI error happened

%CBR-3-PKTCBL_INVALID_GATE_ID : if_index_db is null, index = [dec], gid = [dec]

Explanation PacketCable encounters invalid gate id to look up from its DB

Recommended Action SW code path errors

%CBR-3-RP_INVALIDSID_ASSIGN : Invalid SID assignment for interface: [chars], CM: [enet]

Explanation Invalid SID assignment by RP

Recommended Action Contact Cisco TAC

%CBR-3-SA_MAP_UNSUPPORTED_CRYPTO_SUITE : <132>CMTS[DOCSIS]:<66060200> Unsupported Crypto Suite. CM Mac Addr <[enet]>

Explanation Unsupported Crypto Suite

Recommended Action No action is required.

%CBR-3-SEMCREATEFAIL : Unable to create the semaphore

Explanation Unable to create the semaphore for non-blocking UPX access

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-SEMLOCKFAIL : Unable to lock the semaphore

Explanation Unable to lock the semaphore for non-blocking UPX access

Recommended Action Unable to read the Upconverter status Try again

%CBR-3-SIDERRORHCCP : Tried to allocate New SID during Failover for interface [chars]: CM [enet]: SID container info: start [dec] end [dec]

Explanation Allocate SID during Failover

Recommended Action Assign Cable Modem to another Line Card

%CBR-3-SLOTS : Number of slots in chassis is undefined.

Explanation Data stored in midplane is bad or incomplete.

Recommended Action Contact technical support to update your system.

%CBR-3-SNMPMALLOC : no sufficient memory for sorted table, index [dec], allocated [int], unallocated [int]

Explanation There is no enough memory to allocate for AVL tree

Recommended Action No action needed.

%CBR-3-SPIERRNRD : SPI PENDING NO READ DATA([chars]): spistat=[hex], chid=[hex], cmd=[hex], regaddr=[hex]

Explanation Read error on PHY chip serial communications bus.

Recommended Action Line card is defective, replace it.

%CBR-3-SPIERRR : SPI PENDING READ ERROR([chars]): spistat=[hex], chid=[hex], cmd=[hex], regaddr=[hex]

Explanation Read error on PHY chip serial communications bus.

Recommended Action Line card is defective, replace it.

%CBR-3-SPIERRRBS : SPI BUS READ [hex] BYTES SHORT([chars]): spistat=[hex], chid=[hex], cmd=[hex], regaddr=[hex]

Explanation Read error on PHY chip serial communications bus.

Recommended Action Line card is defective, replace it.

%CBR-3-SPIERRW : SPI PENDING WRITE ERROR([chars]): spistat=[hex], chid=[hex], cmd=[hex], regaddr=[hex]

Explanation Write error on PHY chip serial communications bus.

Recommended Action Line card is defective, replace it.

%CBR-3-SPIERRW_CHID : Invalid Channel ID([chars]): chid=[hex], cmd=[hex], regaddr=[hex]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-3-SPOOFEDIP : Rejecting IP=[IP_address] [chars] sid [dec]: Address configured on [chars]

Explanation CMTS glean function received overlapping ip address info

Recommended Action Check for spoofing: CPE may be using CMTS IP addr

%CBR-3-SPOOFEDMAC : Investigating MAC=[enet] [chars] sid [dec]: Original MAC on sid [dec] [chars]

Explanation CMTS glean function received overlapping mac address info

Recommended Action Check for spoofing: CPE may be reusing mac addr

%CBR-3-SUBDB_CPE_NO_CM : CM doesn't exist when CPE is online on corresponding SID, [chars], mac [enet], sid [dec] hwidb [chars]

Explanation CM doesn't exist when CPE is online on corresponding SID

Recommended Action Contact TAC support, and report the error message.

%CBR-3-SUBDB_FREE_IN_ISR : Unexpected freeing Subscriber Data in interrupt context, host_mac [enet] hwidb [chars]

Explanation Unexpected freeing CMTS Subscriber DB data in interrupt context

Recommended Action Contact TAC support, and report the error message.

%CBR-3-SUBDB_INIT_FAILURE : CMTS Subscriber DB initialization failed [chars] [chars] [chars]

Explanation CMTS Subscriber DB initialization failed

Recommended Action Contact TAC support, and report the error message.

%CBR-3-TEK_INVALID_INVALID_KEY_SEQUENCE_NUMBER : <132>CMTS[DOCSIS]:<66050206> TEK Invalid -Invalid Key Sequence Number . CM Mac Addr <[enet]>

Explanation TEK Invalid - Invalid Key Sequence Number

Recommended Action No action is required.

%CBR-3-TEK_INVALID_NO_INFORMATION : <132>CMTS[DOCSIS]:<66050203> TEK Invalid -No Information. CM Mac Addr <[enet]>

Explanation TEK Invalid, No Information

Recommended Action No action is required.

%CBR-3-TOOMANY_RANGEDSIDS : CMTS-HCCP [chars]: Actual Rcvd ranged list sync sids [dec], # of sids saved [dec]

Explanation Size of Ranged List Sync Message received.

Recommended Action Reduce the Number of Cable Modem Sids pre i/f

%CBR-3-UCDPROCERR : CMTS UCD processing failed on [chars] U[dec], lch_state [dec], err [dec], retry [dec]

Explanation UCD update error

Recommended Action Check the system CPU load and reset the upstream

%CBR-3-UNEXPECTED : [chars]

Explanation The specified operation failed.

Recommended Action No action is required.

%CBR-3-UNSUPPORTED_CRYPTO_SUITE : <132>CMTS[DOCSIS]:<66030300> Unsupported Crypto Suite. CM Mac Addr <[enet]>

Explanation Unsupported Crypto Suite

Recommended Action No action is required.

%CBR-3-WRONG3138CHIP : BCM3138 current chip [dec], desired chip [dec]

Explanation Wrong BCM3138 chip has been selected.

Recommended Action No action is required.

%CBR-3-ZOMBIESID : SID [dec], macaddr [enet], us_channel_id [int], rng_list_id [int], ds_time_stamp [int], rngpoll_timeout [int], now [int], last_ranging [int], stn_mtn=[int], cont_mtn=[int], pending=[int].

Explanation SID instance didn't get cleanup after modem is gone.

Recommended Action Call TAC and show him/her the log.

%CBR-4-BADCFGFILE : Modem config file [chars] at [IP_address]: [chars]

Explanation Configuration file for the cable modem has problems

Recommended Action Make sure the config file is proper

%CBR-4-BADCFGFILE_V6 : Modem config file [chars] at [IPV6 address]: [chars]

Explanation Configuration file for the cable modem has problems

Recommended Action Make sure the config file is proper

%CBR-4-BAD_MAX_DOWNSTREAM_BITRATE_UNSUPPORTED_SETTING : <133>CMTS[DOCSIS]:<73011201> Bad Max DS Bit Rate Unsupported Setting. CM Mac Addr <[enet]>

Explanation REG REQ : Bad Max DS Bit Rate Unsupported Setting.

Recommended Action Check the Config File Parameters

%CBR-4-BAD_MAX_UPSTREAM_BITRATE_UNSUPPORTED_SETTING : <133>CMTS[DOCSIS]:<73011301> Bad Max US Bit Rate -Unsupported Setting. CM Mac Addr <[enet]>

Explanation REG REQ : Bad Max US Bit Rate - Unsupported Setting.

Recommended Action Check the Config File Parameters

%CBR-4-BAD_NETWORK_ACCESS_CONFIGURATION : <133>CMTS[DOCSIS]:<73010800> Network Access has Invalid Parameter. CM Mac Addr <[enet]>

Explanation REG REQ : Network Access has Invalid Parameter.

Recommended Action Check the Config File Parameters

%CBR-4-BAD_REGISTRATION : Cable modem [enet] on interface [chars] when [chars] attempted re-registration with different QoS

Explanation Modem sent a registration request when already registered with a different QoS

Recommended Action Modem could be attempting theft of service

%CBR-4-BADTXOFFSET : Bad timing offset %ld detected for cable modem [enet] sid [hex] cm status [hex] dcc [chars] skip_reg [chars].

Explanation The cable modem is not using the correct starting offset during initial ranging. This causes a zero, negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithm(s) that rely on the timing offset parameter, will exclude such modems from any analysis. Such bad modems may or may-not be able to function depending on their physical location on the cable plant

Recommended Action Locate the cable modem based on MAC address and report initial timing offset problem to the CM vendor

%CBR-4-BAD_UPSTREAM_CHANNEL_OVERLOAD : <133>CMTS[DOCSIS]:<73010700> Bad US CH -Overload. CM Mac Addr <[enet]>

Explanation REG REQ : Bad US CH -Overload.

Recommended Action Check the Upstream Frequency

%CBR-4-BLZE_HM_TEST : Blaze HM testcase failed. Blaze indices allocated for MD host [dec]/[dec] on the Guardian [dec]/[dec] : [dec] Blaze indices in use on the MD Host: [dec]

Explanation The blaze indices have not been deallocated on the Guardian

Recommended Action No action is required.

%CBR-4-BPI_WARNING : [chars]: SID=[dec], KeySeq=[hex], Cable Interface <[chars]>

Explanation BPI Warning

Recommended Action No action is required.

%CBR-4-CACHE_ENGINE_WARNING : Warning: [chars] -[dec]

Explanation Cache engine warning message.

Recommended Action .

%CBR-4-CLASSIFIER_ERROR : CM MAC: [chars] Classifier direction: [chars], Param code: [dec], Confirm code: [dec]

Explanation Looks like issue while admitting/activating Classifier

Recommended Action Please look for DOCSIS message logs followed for more details

%CBR-4-CLK_HWFAULT : Hardware Fault in Clockcard

Explanation Hardware fault in Clockcard

Recommended Action Replace clock card

%CBR-4-CMLOCKED : Cable Modem [enet] in [chars] locked due to [chars] theft of service

Explanation Configuration file for the cable modem has problems

Recommended Action Cable modem attempted to steal service

%CBR-4-CMMARKED : Cable Modem [enet] in [chars] attempted theft of service

Explanation Configuration file for the cable modem has problems

Recommended Action Cable modem attempted to steal service

%CBR-4-CMNOPRIMSF : CM [enet] does not have any primary service flows

Explanation This CM has no primary service flows

Recommended Action NO action is required

%CBR-4-CM_NP_RF_FAILURE : CM <[enet]> on host interface <[chars]> reported NP RF <[dec]> failure, modular-cable <[chars]>, CM's NP RFs <[chars]>

Explanation CMTS is configured to run script via Embedded Event Manager to handle the Cable Modem NP RF failure.

Recommended Action Verify that Cable Modem is not experienceing wideband connectivity.

%CBR-4-CM_SF_DSID_INCONSISTENT : DSID [dec] (BG: [dec]) assigned to SF:[dec] already. DSID invalid on CM-[enet]

Explanation DSID assigned to SF not valid any longer. SW Bug

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-CMTS_IPV6_LLA_FAILED_DAD : <133>CMTS[DOCSIS]:<68001301> IPv6 Link-local address has failed DAD. Addr <[enet]>

Explanation IPv6 Link-Local has failed DAD.

Recommended Action Check the modem and subscriber

%CBR-4-CMTS_IPV6_RX_DHCPV6_WITH_BADADDR : DHCPv6 request received with a bad src IPv6 addr. IP <[IPV6 address]> msg <[chars]>

Explanation DHCPv6 request received with a bad src IPv6 addr, dropping the req

Recommended Action Check the modem and subscriber

%CBR-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED : Card on [dec]/[dec] with l2vpn [chars] command should be taken care of before plugging different type of card or executing no card command.

Explanation Card is configured with cable l2vpn commands, please take care of these configurations before plugging different type of card or executing no card command.

Recommended Action .

%CBR-4-CMTS_RF_POWER_ADJUST : rf-power adjusted to [dec] dBmV to meet upconvertor requirement.

Explanation This card has an upconvertor that has different limits on rf-power. rf-power has been adjusted to meet these limits.

Recommended Action No action is required.

%CBR-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]

Explanation Data stored in midplane is bad.

Recommended Action Contact technical support to update your system.

%CBR-4-COS_INVALID_ID_OUT_OF_RANGE : <133>CMTS[DOCSIS]:<73011100> Bad Class of Service. Invalid Class ID or out of range. CM Mac Addr <[enet]>

Explanation Bad Class of Service. Invalid Class ID or out of range.

Recommended Action No action is required.

%CBR-4-COS_UNSUPPORTED_CLASS : <133>CMTS[DOCSIS]:<73011000> Bad Class of Service-Unsupported class. CM Mac Addr <[enet]>

Explanation Registration Failed, Bad Class of Service-Unsupported class

Recommended Action No action is required.

%CBR-4-CRL_NOT_RESPONDING : <132>CMTS[DOCSIS]:<66030400> Failed to retrieve CRL from [chars]

Explanation CRL not available

Recommended Action No action is required.

%CBR-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID : <133>CMTS[DOCSIS]:<67040300> DCC-ACK is rejected -Unknown transaction ID. CM MAC addr <[enet]>

Explanation DCC-ACK is rejected because of unknown transaction ID

Recommended Action No action is required.

%CBR-4-DCC_NO_RESOURCE_ON_TARGET : DCC [enet] is aborted -No resource available on target [chars] U[dec]

Explanation No resource available on target channel for the DCC transaction

Recommended Action Check target channel utilization

%CBR-4-DCC_REJ_20_DISABLE : <133>CMTS[DOCSIS]:<67021900> DCC is rejected -DOCSIS 2.0 mode is disabled. CM MAC addr <[enet]>

Explanation DCC is rejected because DOCSIS 2.0 mode is disabled

Recommended Action No action is required.

%CBR-4-DCC_REJ_AUTHENTICATION_FAILURE : <133>CMTS[DOCSIS]:<67021100> DCC is rejected -Authentication failure. CM MAC addr <[enet]>

Explanation DCC is rejected because of authentication failure

Recommended Action No action is required.

%CBR-4-DCC_REJ_DUPLICATE_REF_ID_INDEX : <133>CMTS[DOCSIS]:<67021500> DCC is rejected -Duplicated service flow reference-ID or index in message. CM MAC addr <[enet]>

Explanation DCC is rejected because duplicated service flow reference-ID or index exists in message

Recommended Action No action is required.

%CBR-4-DCC_REJ_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<67021700> DCC is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation DCC is rejected because of message syntax error

Recommended Action Check the TLV and parameters setting while sending the DCC request message

%CBR-4-DCC_REJ_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<67021800> DCC is rejected -Message length too big. CM MAC addr <[enet]>

Explanation DCC is rejected because message length is too big

Recommended Action Mimimize the message length to be less than 1536

%CBR-4-DCC_REJ_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<67021200> DCC is rejected -Multiple errors. CM MAC addr <[enet]>

Explanation DCC is rejected because of multiple errors

Recommended Action No action is required.

%CBR-4-DCC_REJ_PARAMETER_INVALID_CONTEXT : <133>CMTS[DOCSIS]:<67021600> DCC is rejected -Invalid parameter for context. CM MAC addr <[enet]>

Explanation DCC is rejected because of invalid parameter for contex

Recommended Action No action is required.

%CBR-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED : <133>CMTS[DOCSIS]:<67020800> DCC is rejected permanently -DCC not supported. CM MAC addr <[enet]>

Explanation DCC is rejected permanently because DCC is not supported

Recommended Action No action is required.

%CBR-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT : <133>CMTS[DOCSIS]:<67021000> DCC is rejected -Required parameter not present. CM MAC addr <[enet]>

Explanation DCC is rejected because required parameter is not present

Recommended Action Double check the parameters while sending the DCC request message

%CBR-4-DCC_REJ_SRV_FLOW_NOT_FOUND : <133>CMTS[DOCSIS]:<67020900> DCC is rejected -Service flow not found. CM MAC addr <[enet]>

Explanation DCC is rejected because service flow was not found

Recommended Action No action is required.

%CBR-4-DCC_REJ_UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<67020700> DCC is rejected -Unspecified reason. CM MAC addr <[enet]>

Explanation DCC is rejected because of unspecified reason

Recommended Action No action is required.

%CBR-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL : <133>CMTS[DOCSIS]:<67020600> DCC is aborted -Unable to communicate on new upstream channel. CM MAC addr <[enet]>

Explanation DCC is aborted unable to communicate on new upstream channel

Recommended Action No action is required.

%CBR-4-DCC_REQ_ARRIVE_NEW : <133>CMTS[DOCSIS]:<67020300> DCC arrives new channel. CM MAC addr <[enet]>

Explanation DCC arrives new channel

Recommended Action No action is required.

%CBR-4-DCC_REQ_DEPART_OLD : <133>CMTS[DOCSIS]:<67020200> DCC departs old channel. CM MAC addr <[enet]>

Explanation DCC departs old channel

Recommended Action No action is required.

%CBR-4-DCC_REQ_REJ_ALREADY : <133>CMTS[DOCSIS]:<67020100> DCC is rejected -CM MAC address <[enet]> already on destination.

Explanation DCC is rejected because CM MAC address is already on destination

Recommended Action Wait until the transaction ends. Otherwise try to move the modem on another channel.

%CBR-4-DCC_RSP_NOT_RCV_NEW_CHANNEL : <133>CMTS[DOCSIS]:<67030200> DCC response was unreceived on new channel. CM MAC addr <[enet]>

Explanation DCC response was unreceived on new channel

Recommended Action No action is required.

%CBR-4-DCC_RSP_NOT_RCV_OLD_CHANNEL : <133>CMTS[DOCSIS]:<67030100> DCC response was unreceived on old channel. CM MAC addr <[enet]>

Explanation DCC response was unreceived on old channel

Recommended Action No action is required.

%CBR-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE : <133>CMTS[DOCSIS]:<67030500> DCC Response is rejected -Authentication failure. CM MAC addr <[enet]>

Explanation DCC response is rejected because of authentication failure

Recommended Action No action is required.

%CBR-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<67030600> DCC Response is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation DCC response is rejected because of message syntax error

Recommended Action No action is required.

%CBR-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID : <133>CMTS[DOCSIS]:<67030400> DCC Response is rejected -Unknown transaction ID. CM MAC addr <[enet]>

Explanation DCC response is rejected because of unknown transaction ID

Recommended Action No action is required.

%CBR-4-DCC_RSP_REJ_UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<67030300> DCC Response is rejected -Unspecified reason. CM MAC addr <[enet]>

Explanation DCC response is rejected because of unspecified reason

Recommended Action No action is required.

%CBR-4-DDC_CFG_HASHID : Hash id [dec] does not exist in global configuration

Explanation A hash id is configured for a cable interface, but is not defined globally

Recommended Action Fix configuration

%CBR-4-DDC_GENERAL_ERROR : Error: [chars]

Explanation Catchall error message for DDC

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_LIST_ERROR : DDC list error

Explanation DDC failed to create or add element to list

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_MESSAGE_ERROR : DDC message error. type [dec]

Explanation DDC failed to send interprocess or IPC message

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_NODE_ID_ERROR : Node id mismatch NPE: [dec] linecard: [dec]

Explanation Node id's on NPE subinterface is different than on linecard

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_PROT_FREQ_ERROR : DS frequency not configured for the protect target node [dec]

Explanation DS frequencies are not configured for all protect targets

Recommended Action Fix configuration

%CBR-4-DDC_SEMAPHORE_ERROR : DDC semaphore released when it was not taken

Explanation DDC semaphore was not take when release was requested

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_UNEXPECTED_EVENT_ERROR : DDC unexpected event error [dec]

Explanation DDC received an unexpected or unsupported event

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DDC_UNEXPECTED_MESSAGE_ERROR : DDC unexpected message error [dec]

Explanation DDC received an unexpected or unsupported message

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DHCP_ACK_MISMATCH_CM : Not update cm state for DHCP ACK, Expected CM [enet] ip [IP_address] found CM [enet] ip [IP_address] new ip [IP_address]

Explanation Found a wrong CM during update DHCP ACK

Recommended Action No action is required.

%CBR-4-DIAG_LOG_HIGH_THRSHLD_REACHED : [DOCSIS]:<86000100>Docs Diag Log exceeds high threshold

Explanation Docs Diag Log Notification :log size exceeds high threshold

Recommended Action No action is required.

%CBR-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID : <133>CMTS[DOCSIS]:<73010500> Bad DS FREQ -Format Invalid. CM Mac Addr <[enet]>

Explanation REG REQ : Bad DS FREQ - Format Invalid .

Recommended Action No action is required.

%CBR-4-DOWNSTREAM_FREQUENCY_NOT_IN_USE : <133>CMTS[DOCSIS]:<73010501> Bad DS FREQ -Not in use. CM Mac Addr <[enet]>

Explanation REG REQ : Bad DS FREQ - Not in use.

Recommended Action Please Check the Config File Frequency

%CBR-4-DOWNSTREAM_FREQUENCY_NOT_MULTIPLE_OF_62500 : <133>CMTS[DOCSIS]:<73010502> Bad DS FREQ -Not multiple of 62500. CM Mac Addr <[enet]>

Explanation REG REQ : Bad DS FREQ - Not multiple of 62500.

Recommended Action Please Check the Config File Frequency

%CBR-4-DSA_ABORTED_NO_ACK : <133>CMTS[DOCSIS]:<83020101> Service Add is aborted -No ACK. CM MAC addr <[enet]>

Explanation DSX is aborted because no ACK

Recommended Action No action is required.

%CBR-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID : <133>CMTS[DOCSIS]:<83020100> Service Add Response is rejected -Invalid transaction ID. CM MAC addr <[enet]>

Explanation ACK is rejected because of invalid transaction ID

Recommended Action No action is required.

%CBR-4-DSA_ADD_ABORTED : <133>CMTS[DOCSIS]:<83000108> Service Add is rejected -Add aborted. CM MAC addr <[enet]>

Explanation CM DSA message is rejected.

Recommended Action No action is required.

%CBR-4-DSA_AUTH_FAILURE : <133>CMTS[DOCSIS]:<83000120> Service Add is rejected -Authorization failure. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of an authorization failure.

Recommended Action No action is required.

%CBR-4-DSA_CLASSIFIER_ANOTHER_FLOW : <133>CMTS[DOCSIS]:<83000117> Service Add is rejected -Classifier for another flow. CM MAC addr <[enet]>

Explanation CM DSA is rejected because classifier is for another flow.

Recommended Action No action is required.

%CBR-4-DSA_CLASSIFIER_EXISTS : <133>CMTS[DOCSIS]:<83000111> Service Add is rejected -Classifier exists. CM MAC addr <[enet]>

Explanation CM DSA is rejected because classifier already exists.

Recommended Action No action is required.

%CBR-4-DSA_CLASSIFIER_NOT_FOUND : <133>CMTS[DOCSIS]:<83000110> Service Add is rejected -Classifier not found. CM MAC addr <[enet]>

Explanation CM DSA is rejected because classifier was not found.

Recommended Action No action is required.

%CBR-4-DSA_DUPLICATE_REF_ID_INDEX : <133>CMTS[DOCSIS]:<83000114> Service Add is rejected -Duplicated reference-ID or index in message. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of duplicated reference ID or index.

Recommended Action No action is required.

%CBR-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED : <133>CMTS[DOCSIS]:<83000105> Service Add is rejected -Header suppression setting not supported. CM MAC addr <[enet]>

Explanation Header suppression setting is not supported

Recommended Action No action is required.

%CBR-4-DSA_HMAC_AUTHENTICATION_FAILURE : <133>CMTS[DOCSIS]:<83000101> Service Add is rejected -HMAC authentication failure. CM MAC addr <[enet]>

Explanation HMAC Authentication Failure

Recommended Action No action is required.

%CBR-4-DSA_MAJOR_CLASSIFIER_ERROR : <133>CMTS[DOCSIS]:<83000122> Service Add is rejected -Major classifier error. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of a major classifier error.

Recommended Action No action is required.

%CBR-4-DSA_MAJOR_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<83000124> Service Add is rejected -Multiple major errors. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of multiple major errors.

Recommended Action No action is required.

%CBR-4-DSA_MAJOR_PHS_RULE_ERROR : <133>CMTS[DOCSIS]:<83000123> Service Add rejected -Major PHS rule error. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of a major PHS rule error.

Recommended Action No action is required.

%CBR-4-DSA_MAJOR_SRV_FLOW_ERROR : <133>CMTS[DOCSIS]:<83000121> Service Add is rejected -Major service flow error. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of a major service flow error.

Recommended Action No action is required.

%CBR-4-DSA_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<83000125> Service Add is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of message syntax error.

Recommended Action No action is required.

%CBR-4-DSA_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<83000126> Service Add is rejected -Message too big. CM MAC addr <[enet]>

Explanation CM DSA is rejected because message length was too big.

Recommended Action No action is required.

%CBR-4-DSA_MULTIPLE_DOWNSTREAM_FLOW : <133>CMTS[DOCSIS]:<83000116> Service Add is rejected -Multiple downstream flow. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of mulitple DS flows.

Recommended Action No action is required.

%CBR-4-DSA_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<83000109> Service Add is rejected -Multiple errors. CM MAC addr <[enet]>

Explanation CM DSA is rejected due to multilpe errors.

Recommended Action No action is required.

%CBR-4-DSA_MULTIPLE_UPSTREAM_FLOW : <133>CMTS[DOCSIS]:<83000115> Service Add is rejected -Multiple upstream flow. CM MAC addr <[enet]>

Explanation CM DSA is rejected because of muliptle US flows.

Recommended Action No action is required.

%CBR-4-DSA_PARAMETER_INVALID_CONTEXT : <133>CMTS[DOCSIS]:<83000119> Service Add is rejected -Parameter invalid for context. CM MAC addr <[enet]>

Explanation CM DSA is rejected because parameter is invalid for the context.

Recommended Action No action is required.

%CBR-4-DSA_PERMANENT_ADMINISTRATIVE : <133>CMTS[DOCSIS]:<83000103> Service Add is rejected -Permanent administrative.CM MAC addr <[enet]> [chars]

Explanation Permanent administrative

Recommended Action No action is required.

%CBR-4-DSA_PHS_RULE_ANOTHER_FLOW : <133>CMTS[DOCSIS]:<83000118> Service Add is rejected -PHS rule for another flow. CM MAC addr <[enet]>

Explanation CM DSA is rejected because PHS rule is for another flow.

Recommended Action No action is required.

%CBR-4-DSA_PHS_RULE_EXISTS : <133>CMTS[DOCSIS]:<83000113> Service Add is rejected -PHS rule exists. CM MAC addr <[enet]>

Explanation CM DSA is rejected because the PHS rule already exists.

Recommended Action No action is required.

%CBR-4-DSA_PHS_RULE_NOT_FOUND : <133>CMTS[DOCSIS]:<83000112> Service Add is rejected -PHS rule not found. CM MAC addr <[enet]>

Explanation CM DSA is rejected because the PHS rule was not found.

Recommended Action No action is required.

%CBR-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT : <133>CMTS[DOCSIS]:<83000104> Service Add is rejected -Required parameter not present. CM MAC addr <[enet]>

Explanation Required parameter is not present

Recommended Action No action is required.

%CBR-4-DSA_RSP_ABORTED_NO_RSP : <133>CMTS[DOCSIS]:<83010101> Service Add is aborted -No response. CM MAC addr <[enet]>

Explanation CM DSA is aborted because no response.

Recommended Action No action is required.

%CBR-4-DSA_RSP_INVALID_TRANSACTION_ID : <133>CMTS[DOCSIS]:<83010100> Service Add Response is rejected -Invalid transaction ID. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of invalid transation ID.

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_MAJOR_CFR_ERROR : <133>CMTS[DOCSIS]:<83010115> Service Add Response is rejected -Major classifier error. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of a major classifier error.

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_MAJOR_PHS_RULE_ERROR : <133>CMTS[DOCSIS]:<83010116> Service Add Response is rejected -Major PHS rule error. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of a major PHS rule error.

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<83010118> Service Add Response is rejected -Message length too big. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because message length was too big.

Recommended Action No action is required.No action is required.

%CBR-4-DSA_RSP_REJECT_PARAM_INVALID_FOR_CONTEXT : <133>CMTS[DOCSIS]:<83010113> Service Add Response is rejected -Invalid parameter for context. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of invalid parameter for context

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_PHS_RULE_EXISTS : <133>CMTS[DOCSIS]:<83010110> Service Add Response is rejected -PHS rule exists. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because the PHS rule already exist.

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_REQD_PARAM_NOT_PRESENT : <133>CMTS[DOCSIS]:<83010106> Service Add Response is rejected -Required parameter not present. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because the required parameter is not present.

Recommended Action No action is required.

%CBR-4-DSA_RSP_REJECT_UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<83010105> Service Add Response is rejected -Unrecognized configuration setting. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of unrecognized configuration setting.

Recommended Action No action is required.

%CBR-4-DSA_SERVICE_FLOW_EXISTS : <133>CMTS[DOCSIS]:<83000106> Service Add rejected -Service flow exists. CM MAC addr <[enet]>

Explanation CM DSA is rejected because service flow exists.

Recommended Action No action is required.

%CBR-4-DSA_TEMP_NO_RESOURCE : <133>CMTS[DOCSIS]:<83000102> Service Add is rejected -Temporary no resource.CM MAC addr <[enet]> [chars]

Explanation CM DSA message is rejected due to no resources.

Recommended Action No action is required.

%CBR-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<83000101> Service Add is rejected -Unrecognized configuration setting. CM MAC addr <[enet]>

Explanation Unrecognized configuration setting

Recommended Action No action is required.

%CBR-4-DSA_UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<83000100> Service Add is rejected -Unspecified reason. CM MAC addr <[enet]>

Explanation Unspecified reason

Recommended Action No action is required.

%CBR-4-DSC_ABORTED_NO_ACK : <133>CMTS[DOCSIS]:<83020201> Service Change is aborted -No ACK. CM MAC addr <[enet]>

Explanation DSX is aborted because no ACK

Recommended Action No action is required.

%CBR-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID : <133>CMTS[DOCSIS]:<83020200> Service Change ACK is rejected -Invalid transaction ID. CM MAC addr <[enet]>

Explanation ACK is rejected because of invalid transaction ID

Recommended Action No action is required.

%CBR-4-DSC_AUTH_FAILURE : <133>CMTS[DOCSIS]:<83000220> Service Change is rejected -Authorization failure. CM MAC addr <[enet]>

Explanation CM DSC is rejected because authorization failed.

Recommended Action No action is required.

%CBR-4-DSC_CLASSIFIER_ANOTHER_FLOW : <133>CMTS[DOCSIS]:<83000217> Service Change rejected -Classifier for another flow. CM MAC addr <[enet]>

Explanation CM DSC is rejected because classifier is for another flow.

Recommended Action No action is required.

%CBR-4-DSC_CLASSIFIER_EXISTS : <133>CMTS[DOCSIS]:<83000211> Service Change is rejected -Classifier exists. CM MAC addr <[enet]>

Explanation CM DSC is rejected because classifier has been exist.

Recommended Action No action is required.

%CBR-4-DSC_CLASSIFIER_NOT_FOUND : <133>CMTS[DOCSIS]:<83000210> Service Change is rejected -Classifier not found. CM MAC addr <[enet]>

Explanation CM DSC is rejected because classifier is not found.

Recommended Action No action is required.

%CBR-4-DSC_DUPLICATE_REF_ID_INDEX : <133>CMTS[DOCSIS]:<83000214> Service Change is rejected -Duplicated reference-ID or index in message. CM MAC addr <[enet]>

Explanation CM DSC is rejected because of duplicated reference ID or index.

Recommended Action No action is required.

%CBR-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED : <133>CMTS[DOCSIS]:<83000207> Service Change is rejected -Header suppression setting not supported. CM MAC addr <[enet]>

Explanation Header suppression setting is not supported

Recommended Action No action is required.

%CBR-4-DSC_HMAC_AUTHENTICATION_FAILURE : <133>CMTS[DOCSIS]:<83000208> Service Change is rejected -HMAC authorization failure. CM MAC addr <[enet]>

Explanation HMAC Authentication Failure

Recommended Action No action is required.

%CBR-4-DSC_MAJOR_CLASSIFIER_ERROR : <133>CMTS[DOCSIS]:<83000222> Service Change is rejected -Major classifier error. CM MAC addr <[enet]>

Explanation CM DSC is rejected because major classifier error.

Recommended Action No action is required.

%CBR-4-DSC_MAJOR_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<83000224> Service Change is rejected -Multiple major errors. CM MAC addr <[enet]>

Explanation CM DSC is rejected because of mulitple major errors.

Recommended Action No action is required.

%CBR-4-DSC_MAJOR_PHS_RULE_ERROR : <133>CMTS[DOCSIS]:<83000223> Service Change is rejected -Major PHS rule error. CM MAC addr <[enet]>

Explanation CM DSC is rejected because major PHS rule error.

Recommended Action No action is required.

%CBR-4-DSC_MAJOR_SRV_FLOW_ERROR : <133>CMTS[DOCSIS]:<83000221> Service Change is rejected -Major service flow error. CM MAC addr <[enet]>

Explanation CM DSC is rejected because service flow error.

Recommended Action No action is required.

%CBR-4-DSC_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<83000225> Service Change is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation CM DSC is rejected because message syntax error.

Recommended Action No action is required.

%CBR-4-DSC_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<83000226> Service Change is rejected -Message too big. CM MAC addr <[enet]>

Explanation CM DSC is rejected because message length is too big.

Recommended Action No action is required.

%CBR-4-DSC_MULTIPLE_DOWNSTREAM_FLOW : <133>CMTS[DOCSIS]:<83000216> Service Change is rejected -Multiple downstream flow. CM MAC addr <[enet]>

Explanation CM DSC is rejected because of mulitple DS flows.

Recommended Action No action is required.

%CBR-4-DSC_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<83000209> Service Change is rejected -Multiple errors. CM MAC addr <[enet]>

Explanation CM DSC is rejected because mulitple errors have already occurred.

Recommended Action No action is required.

%CBR-4-DSC_MULTIPLE_UPSTREAM_FLOW : <133>CMTS[DOCSIS]:<83000215> Service Change is rejected -Multiple upstream flow. CM MAC addr <[enet]>

Explanation CM DSC is rejected because of multiple US flows.

Recommended Action No action is required.

%CBR-4-DSC_PARAMETER_INVALID_CONTEXT : <133>CMTS[DOCSIS]:<83000219> Service Change rejected -Invalid parameter for context. CM MAC addr <[enet]>

Explanation CM DSC rejected because of invalid parameter for context.

Recommended Action No action is required.

%CBR-4-DSC_PERMANENT_ADMINISTRATIVE : <133>CMTS[DOCSIS]:<83000203> Service Change is rejected -Permanent administrative. CM MAC addr <[enet]> [chars]

Explanation Permanent administrative

Recommended Action No action is required.

%CBR-4-DSC_PHS_RULE_ANOTHER_FLOW : <133>CMTS[DOCSIS]:<83000218> Service Change is rejected -PHS rule for another flow. CM MAC addr <[enet]>

Explanation CM DSC is rejected because PHS rule is for another flow.

Recommended Action No action is required.

%CBR-4-DSC_PHS_RULE_EXISTS : <133>CMTS[DOCSIS]:<83000213> Service Change is rejected -PHS rule exists. CM MAC addr <[enet]>

Explanation CM DSC is rejected because PHS rule exists.

Recommended Action No action is required.

%CBR-4-DSC_PHS_RULE_NOT_FOUND : <133>CMTS[DOCSIS]:<83000212> Service Change is rejected -PHS rule not found. CM MAC addr <[enet]>

Explanation CM DSC is rejected because PHS rule can't be found.

Recommended Action No action is required.

%CBR-4-DSC_REQUESTOR_NOT_OWNER : <133>CMTS[DOCSIS]:<83000204> Service Change is rejected -Requestor not the owner of service flow. CM MAC addr <[enet]>

Explanation Requestor is not the owner of service flow

Recommended Action No action is required.

%CBR-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT : <133>CMTS[DOCSIS]:<83000206> Service Change is rejected -Required parameter not present. CM MAC addr <[enet]>

Explanation Required parameter is not present

Recommended Action No action is required.

%CBR-4-DSC_RSP_ABORTED_NO_RSP : <133>CMTS[DOCSIS]:<83010201> Service Change is aborted -No response. CM MAC addr <[enet]>

Explanation CM DSC is aborted because no response.

Recommended Action No action is required.

%CBR-4-DSC_RSP_INVALID_TRANSACTION_ID : <133>CMTS[DOCSIS]:<83010200> Service Change Response is rejected -Invalid transaction ID. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of an invalid transation ID.

Recommended Action No action is required.

%CBR-4-DSC_RSP_PARAMETER_INVALID_CONTEXT : <133>CMTS[DOCSIS]:<83010211> Service Change Response is rejected -Invalid parameter for context. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of invalid parameter for context.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_AUTHORIZATION_FAILURE : <133>CMTS[DOCSIS]:<83010202> Service Change Response is rejected -HMAC authorization failure. CM MAC addr <[enet]>

Explanation CM DSA response is rejected because of authorization failure.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_DUPLC_REF_ID_OR_INDEX : <133>CMTS[DOCSIS]:<83010210>Service Change Response is rejected -Duplicated reference-ID or index in message. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of duplicated refrence ID or index.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_MAJOR_CFR_ERROR : <133>CMTS[DOCSIS]:<83010212> Service Change Response is rejected -Major classifier error. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of a major classifier error.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_MAJOR_PHS_RULE_ERROR : <133>CMTS[DOCSIS]:<83010213> Service Change Response is rejected -Major PHS rule error. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of a major PHS error.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<83010203> Service Change Response is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of a message syntax error.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<83010215> Service Change Response is rejected -Message too big. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because message length was too big.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_PHS_RULE_EXISTS : <133>CMTS[DOCSIS]:<83010209> Service Change Response is rejected -PHS rule exists. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of a major PHS rule error.

Recommended Action No action is required.

%CBR-4-DSC_RSP_REJECT_REQD_PARAM_NOT_PRESENT : <133>CMTS[DOCSIS]:<83010206> Service Change Response is rejected -Required parameter not present. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because the required parameter not present.

Recommended Action No action is required.

%CBR-4-DSC_RSP_UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<83010205> Service Change response is rejected -Unrecognized configuration setting. CM MAC addr <[enet]>

Explanation CM DSC response is rejected because of unrecognized configuration setting.

Recommended Action No action is required.

%CBR-4-DSC_SERVICE_FLOW_NOT_FOUND : <133>CMTS[DOCSIS]:<83000205> Service Change is rejected -Service flow not found. CM MAC addr <[enet]>

Explanation Service flow is not found

Recommended Action No action is required.

%CBR-4-DSC_TEMP_NO_RESOURCE : <133>CMTS[DOCSIS]:<83000202> Service Change is rejected -Temporary no resource. CM MAC addr <[enet]> [chars]

Explanation CM DSC is rejected because of no resource.

Recommended Action No action is required.

%CBR-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<83000201> Service Change is rejected -Unrecognized configuration setting. CM MAC addr <[enet]>

Explanation Unrecognized configuration setting

Recommended Action No action is required.

%CBR-4-DSC_UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<83000200> Service Change is rejected -Unspecified reason. CM MAC addr <[enet]>

Explanation Unspecified reason

Recommended Action No action is required.

%CBR-4-DSD_HMAC_AUTHENTICATION_FAILURE : <133>CMTS[DOCSIS]:<83000303> Service Delete is rejected -HMAC authorization failure. CM MAC addr <[enet]>

Explanation HMAC authentication failure

Recommended Action No action is required.

%CBR-4-DSD_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<83000304> Service Delete is rejected -Message syntax error. CM MAC addr <[enet]>

Explanation CM DSD is rejected because of message syntax error.

Recommended Action No action is required.

%CBR-4-DSD_REQUESTOR_NOT_OWNER : <133>CMTS[DOCSIS]:<83000301> Service Delete is rejected -Requestor not the owner of service flow. CM MAC addr <[enet]>

Explanation Requestor is not the owner of service flow

Recommended Action No action is required.

%CBR-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID : <133>CMTS[DOCSIS]:<83010300> Service Delete Response is rejected -Invalid transaction ID. CM MAC addr <[enet]>

Explanation DSD response is rejected because of invalid transaction ID

Recommended Action No action is required.

%CBR-4-DSD_SERVICE_FLOW_NOT_FOUND : <133>CMTS[DOCSIS]:<83000302> Service Delete is rejected -Service flow not found. CM MAC addr <[enet]>

Explanation Service flow was not found

Recommended Action No action is required.

%CBR-4-DSD_UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<83000300> Service Delete is rejected -Unspecified reason. CM MAC addr <[enet]>

Explanation Unspecified reason

Recommended Action No action is required.

%CBR-4-DSID_DUPLICATE : Duplicate DSID [dec]/[dec]/[dec]: [dec] detected

Explanation Detected an attempt to enqueue a duplicate DSID. SW Bug

Recommended Action Copy the error message exactly as it appears and report it to your technical services representative

%CBR-4-DSX_MSG_ERROR : CM MAC: [chars] MSG type: [chars], Error code: [dec], MSG: [chars].

Explanation Received invalid DSX message.

Recommended Action Please turn on debug to see more detailed DSX messages.

%CBR-4-DSX_RESTORE_CFR_STATE_FAILED : DSX restore classifier state fail when try to restore state. CM MAC addr <[enet]>

Explanation DSX restore classifier state fail.

Recommended Action No action is required.

%CBR-4-DSX_RESTORE_INVALID_CFRID : Invalid classifier ID was found when DSX restore classifier state. CM MAC addr <[enet]>

Explanation DSX restore classifier state because invalid classifier ID was found.

Recommended Action No action is required.

%CBR-4-DUPIPV6_SIDMISMATCH : Duplicate IPv6 Address [IPV6 address] in [chars] Sid [dec], MAC:[enet]. Dup, Original Sid [dec]

Explanation Duplicate IPv6 Address found with different sid.

Recommended Action No action is required.

%CBR-4-DUPLICATEMAC : Cable modem [enet] is online on both interface [chars] and interface [chars].

Explanation The cable modem has been detected on two interfaces.

Recommended Action Check for cable modems with duplicate MAC addresses.

%CBR-4-ENVM_PS_OVERLOAD : Power supply may be overloaded to support the line card installed in slot [dec]

Explanation The power supply may be insufficient to support the number of line cards installed in the system under certain operation conditions like high temperature and high voltage margining.

Recommended Action Upgrade the power supply as soon as possible or the system may fail to operation properly under some certain operation conditions.

%CBR-4-GRD_UNAVAIL : Unable to reach Card [dec]/[dec] for Modular-host services

Explanation The Guardian card is down or the IPC to the Guardian card is down

Recommended Action Make sure the card selected to be Modular-host is operational or change the relevant Modular-host config to use an operational card.

%CBR-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED : <133>CMTS[DOCSIS]:<73020105> REG REQ rejected , Header suppression setting not supported. CM Mac Addr <[enet]>

Explanation Header suppression setting not supported

Recommended Action No action is required.

%CBR-4-INVALID_COS_CONFIGURATION : <133>CMTS[DOCSIS]:<73010900> Bad Class of Service-Invalid Configuration. CM Mac Addr <[enet]>

Explanation Registration Failed, Bad Class of Service

Recommended Action No action is required.

%CBR-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT : <133>CMTS[DOCSIS]:<73011200> Bad Max DS bit -Invalid format. CM Mac Addr <[enet]>

Explanation Registration Failed, Bad Max Downstream bit has invalid format.

Recommended Action No action is required.

%CBR-4-INVALID_MAX_UPSTREAM_BIT_FORMAT : <133>CMTS[DOCSIS]:<73011300> Bad Max US Bit -Invalid format. CM Mac Addr <[enet]>

Explanation Registration Failed, Bad Max Upstream bit Rate has invalid format.

Recommended Action No action is required.

%CBR-4-INVALID_MAX_UPSTREAM_BURST_FORMAT : <133>CMTS[DOCSIS]:<73011600> Bad Max US CH Transmit Burst Configuration setting -Invalid format. CM Mac Addr <[enet]>

Explanation CM Max US channel transmit burst type invalid format.

Recommended Action No action is required.

%CBR-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT : <133>CMTS[DOCSIS]:<73011500> Bad Guaranteed MIN US Channel bit Rate Configuration setting -Invalid format. CM Mac Addr <[enet]>

Explanation Guaranteed Minimum Upstream Rate format invalid.

Recommended Action No action is required.

%CBR-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT : <133>CMTS[DOCSIS]:<73011700> Invalid Modem Capabilities configuration setting . CM Mac Addr <[enet]>

Explanation CM Capabilities config value contains an invalid format.

Recommended Action No action is required.

%CBR-4-INVALID_SID : <133>CMTS[DOCSIS]:<73010200> REG REQ has Invalid SID or not in use. CM Mac Addr <[enet]>

Explanation REG REQ has Invalid SID or not in use

Recommended Action No action is required.

%CBR-4-INVALID_UNASSIGNED_UPSTREAM_CHANNEL : <133>CMTS[DOCSIS]:<73010600> Bad US CH -Invalid or Unassigned. CM Mac Addr <[enet]>

Explanation REG REQ : Bad US CH - Invalid or Unassigned.

Recommended Action Please Check the upstream Channel Frequency

%CBR-4-INVALID_UPSTREAM_PRIORITY_FORMAT : <133>CMTS[DOCSIS]:<73011400> Bad US Priority Configuration -Invalid format. CM Mac Addr <[enet]>

Explanation Registration Failed, Upstream Priority Format has invalid format.

Recommended Action No action is required.

%CBR-4-IPDR_CPETYPE_ENQ_ERR : Enqueue error for CPETYPE event. [chars] Q size [dec]

Explanation Too many IPDR CPETYPE events generated in a moment

Recommended Action If there are a lot of memory leaks, do PRE switchover.

%CBR-4-L2VPN_CMIM_ERROR : ERROR: CM [enet] [chars] Top Level CMIM TLV does not exclude eCM

Explanation Top Level CMIM TLV does not exclude eCM

Recommended Action Check CM config file

%CBR-4-L2VPN_DS_CFR_VPNID_ERROR : ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for DS-CFR

Explanation Matching TopLevel L2VPNID not found for DS-CFR

Recommended Action Check CM config file

%CBR-4-L2VPN_DUPLICATE_VLANID_ERROR : ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vlanid at top level

Explanation Multiple L2VPN TLV with same vlanid at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_ERROR_BPI_NOT_ENABLED : L2VPN enabled without enabling BPI+ or 1.0 CM [enet] [chars]

Explanation Encryption not enabled for L2VPN CM

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLS_BKUP_DISABLE_CFG_ERR : ERROR: CM [enet] [chars] Bkup disable delay and never disable bkup, both configured

Explanation Both TLVs cannot be configured

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLS_BKUP_EXCEEDED : ERROR: CM [enet] [chars] Too many backup peers

Explanation Too many backup peers

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLS_BKUP_PRIO_ERR : ERROR: CM [enet] [chars] Incorect or missing priority for backup peer

Explanation Priority incorrect or missing for backup peer

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLSPEER_ERROR : ERROR: CM [enet] [chars] MPLS PEER IPADDR TLV invalid at top level

Explanation MPLS PEER IPADDR TLV invalid at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLSPEERNAME_LEN_ERROR : ERROR: CM [enet] [chars] MPLSPEERNAME TLV length invalid

Explanation MPLSPEERNAME TLV length invalid

Recommended Action Check CM config file

%CBR-4-L2VPN_MPLS_PWTYPE_ERROR : ERROR: CM [enet] [chars] MPLS PW TYPE TLV invalid at top level

Explanation MPLS PW TYPE TLV invalid at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_MULTIPLE_VPNID_ERROR : ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vpnid at top level

Explanation Multiple L2VPN TLV with same vpnid at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_NSI_DUPLICATE_ERROR : ERROR: CM [enet] [chars] VLANID and MPLSPEER TLV both present at top level

Explanation VLANID and MPLSPEER TLV both present at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_NSI_MISSING_ERROR : ERROR: CM [enet] [chars] VLANID or MPLSPEER TLV missing at top level

Explanation VLANID or MPLSPEER TLV missing at top level

Recommended Action Check CM config file

%CBR-4-L2VPN_TLVERR : L2VPN XCONNECT PW Cable Modem CM config file TLV Error.

Explanation L2VPN XCONNECT PW TLV Error VCID or SAII or TAII not valid

Recommended Action Check CM config file

%CBR-4-L2VPN_US_SFLOW_VPNID_ERROR : ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for US-SF

Explanation Matching TopLevel L2VPNID not found for US-SF

Recommended Action Check CM config file

%CBR-4-L2VPN_VCID_OR_TAII_SAII_MISSING_ERROR : ERROR: CM [enet] [chars] VCID or TAII & SAII TLV missing or out-of-range

Explanation VCID or TAII & SAII TLV missing or out-of-range

Recommended Action Check CM config file

%CBR-4-L2VPN_VPNID_MISSING_ERROR : ERROR: CM [enet] [chars] VPNID TLV missing at top level

Explanation VPNID TLV missing at top level

Recommended Action Check CM config file

%CBR-4-LB_CM_LIST_DUP_ENTRY : Duplicated CM [enet] in CM List ([hex]), group [dec], expected RFID [int] MD [chars] US [int], found RFID [int] US [int], CM state [int] LB(Load Balance) state [int] last skip [int]

Explanation Duplicated entries in CM lists. No operational impact.

Recommended Action No action is required.

%CBR-4-LB_CM_LIST_MISMATCH_ENTRY : CM [enet] on CM List ([hex]), group [int], action [int], not matched the expected RFID [int] MD [chars] US [int], found RFID [int] US [int], CM state [int] LB(Load Balance) state [int], last skip [int]

Explanation Entry in CM list seen at different position than expected . There is no operational impact

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-4-LB_CM_WITH_INVALID_GROUP_ID : The CM [enet] MD [chars] LB(Load Balance) group [dec] is not found in load balance database

Explanation The CM is assigned to an invalid load-balance group. No operational impact.

Recommended Action No action is required.

%CBR-4-LB_COUNT_OUT_OF_RANGE : LB(Load Balance) Counter out of range: group [int] MD [chars] [chars] chan [int] CM [enet] [chars], current value [int] new state [chars] old [int] skip reason [chars]

Explanation LB modem counter is out of decrements range.

Recommended Action No action is required.

%CBR-4-MACBLKSIZE : Unknown MAC address block size.

Explanation Data stored in midplane is bad or incomplete.

Recommended Action Contact technical support to update your system.

%CBR-4-MCAST_ADMISSION_CONTROL_FAILURE : Multicast Service flow creation failed -group [chars], source [chars], host Interface [chars]

Explanation service flow creation failure due to admission control check.

Recommended Action Adjust the min-rate parameter mentioned as part of the service class

%CBR-4-MCAST_DB_MAX_LIMIT_REACHED : Multicast DB full, new entry not created -max [int] group [chars], source [chars], fwd Interface [chars], bundle [chars]

Explanation Multicast explicit tracking DB entry creation failed due to max limit reached

Recommended Action Reduce Static IGMP multicast config or wait for Dynamic IGMP OR PCMM multicast clients to leave

%CBR-4-MCAST_SID_MAX_LIMIT_REACHED : Multicast SID full, new entry not created -max [int], Bundle Interface [chars]

Explanation Multicast sid allocation failed due to max mcast sid limit reached

Recommended Action Remove multicast qos or change single mqos to aggregate mqos

%CBR-4-METERING_NOFILESYS_SFLOG : No file system [chars] can be used for sflog file.

Explanation Cannot find a suitable file system to store sflog file.

Recommended Action Please check whether tmp disk is ready or full.

%CBR-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX : <133>CMTS[DOCSIS]:<73011501> Bad Guaranteed Min US Channel Bit Rate Configuration setting -Exceed Max US Bit Rate. CM Mac Addr <[enet]>

Explanation CM MIN Upstream Channel Bit Rate exceeds maximum value.

Recommended Action No action is required.

%CBR-4-MIN_UPSTREAM_CHANNEL_BITRATE_OUT_OF_RANGE : <133>CMTS[DOCSIS]:<73011502> Bad Guaranteed Min US CH Bit rate Configuration setting -Out of Range. CM Mac Addr <[enet]>

Explanation REG REQ : Bad Guaranteed Min US CH Bit rate Configuration setting - Out of Range.

Recommended Action Check the Config File Parameters

%CBR-4-MISMATCH_BP_CONFIGURATION_SETTING_VALUE : <132>CMTS[DOCSIS]: Misconfigured BPI Setting: gracetime (Type [dec]) is longer than 50%%of lifetime. CM MAC Addr <[enet]>

Explanation Misconfigured BPI Configuration Setting Value

Recommended Action Please inspect the configuration file

%CBR-4-MISMATCH_BP_REVOCATION_TIMEOUT_VALUE : <132>CMTS[DOCSIS]: Misconfigured BPI Setting: [chars] (Type [dec]) is longer than revocation timeout value. CM MAC Addr <[enet]>

Explanation Misconfigured BPI Configuration Setting Value

Recommended Action Please inspect the configuration file

%CBR-4-MTA_REQ_ON_NON_HA_DS : MTA Modem [enet] in [chars] to come online on a non-HA capable DS

Explanation CMTS can not move the MTA to a DS that is HA capable after 3 trials

Recommended Action No action is required.

%CBR-4-NOCFGFILE : Cannot read modem config file [chars] from [IP_address]: [chars]

Explanation Configuration file for the cable modem cannot be read

Recommended Action Make sure the config file is accesable to the CMTS

%CBR-4-NOCFGFILE_V6 : Cannot read modem config file [chars] from [IPV6 address]: [chars]

Explanation Configuration file for the cable modem cannot be read

Recommended Action Make sure the config file is accesable to the CMTS

%CBR-4-NOCPUVER : Invalid CPU ID, assuming revision 1

Explanation CPU Revision ID is unreadable.

Recommended Action Update CPU board.

%CBR-4-NO_RANGING_REQUESTS : <133>CMTS[DOCSIS]:<82010100> No Ranging Requests received from POLLED CM Mac Addr <[enet]> (CMTS generated polls)

Explanation No Ranging Requests received from POLLED CM (CMTS generated polls)

Recommended Action Please look for possible noise or other RF plant problems on the upstream channel

%CBR-4-NO_RNG_REQ_TIMEOUT_SID : <133>CMTS[DOCSIS]:<82010400> Failed to receive Periodic RNG-REQ from modem [chars], timing-out SID

Explanation Failed to receive Periodic RNG-REQ from modem (SID X), timing-out SID

Recommended Action No action is required.

%CBR-4-NOTLEARNABLE : New address of CPE [enet] behind modem [enet] on interface [chars] is ignored: [chars]. Count [dec]

Explanation The CPE is not learnable due to provisioning.

Recommended Action Provisioning failure. Please check configuration

%CBR-4-OACKERROR : TFTP Option Negotiation Error for [chars] file at [IP_address]: [chars]

Explanation TFTP OACK packet is malformed or wrong options appended

Recommended Action Make sure TFTP Server supports TFTP Options

%CBR-4-OACKERROR_V6 : TFTP Option Negotiation Error for [chars] file at [IPV6 address]: [chars]

Explanation TFTP OACK packet is malformed or wrong options appended

Recommended Action Make sure TFTP Server supports TFTP Options

%CBR-4-OCSP_NOT_RESPONDING : <132>CMTS[DOCSIS]:<66030401> Failed to retrieve OCSP status

Explanation OCSP not available

Recommended Action No action is required.

%CBR-4-OUT_OF_RANGE_CONFIG_FILE_PARAMETERS : <133>CMTS[DOCSIS]:<73011800> Configuration file contains parameter with the value outside of the range. CM Mac Addr <[enet]>

Explanation CM config file parameter contains an out of range parameter.

Recommended Action No action is required.

%CBR-4-OUT_OF_RANGE_MAX_UPSTREAM_BURST : <133>CMTS[DOCSIS]:<73011601> Bad Max US CH Transmit Burst Configuration setting -Out of Range. CM Mac Addr <[enet]>

Explanation CM Max US channel transmit burst setting out of range.

Recommended Action No action is required.

%CBR-4-OUT_OF_RANGE_US_PRIORITY_CONFIGURATION : <133>CMTS[DOCSIS]:<73011401> Bad US Priority Configuration -Setting out of Range. CM Mac Addr <[enet]>

Explanation Out of Range US Traffic Priority Value.

Recommended Action No action is required.

%CBR-4-OVERLAP_IPV4 : MAC [enet] on interface [chars] SID [dec] attempting to use [IP_address]. This address is already in use by MAC [enet] on interface [chars] SID [dec]

Explanation There might be an IPv4 spoofing attempt going on.

Recommended Action Look for possible spoofing attempt

%CBR-4-OVERLAP_IPV6 : MAC [enet] on interface [chars] SID [dec] attempting to use [IPV6 address]. This address is already in use by MAC [enet] on interface [chars] SID [dec]

Explanation There might be an IPv6 spoofing attempt going on.

Recommended Action Look for possible spoofing attempt

%CBR-4-PHS_ERROR : CM MAC: [chars] PHS_ERROR, Param code: [dec], Confirm code: [dec]

Explanation Looks like issue with PHS header

Recommended Action Please look for DOCSIS message logs followed for more details

%CBR-4-RECALLED_NPE : Old version NPE-175/225 with Rev = [hex] system controller. Contact upgrades-info@cisco.com for replacement

Explanation NPE board has been recalled due to an errata in the system controller chip.

Recommended Action Replace NPE-175/225 Board

%CBR-4-REG_ACK_REJ_BAD_RCC : <133>CMTS[DOCSIS]:<73030208> REG ACK rejected bad rcc. CM Mac Addr <[enet]>

Explanation CM Reg Ack message bad rcc.

Recommended Action No action is required.

%CBR-4-REG_ACK_REJ_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<73030300> REG ACK rejected message syntax error. CM Mac Addr <[enet]>

Explanation CM Reg Ack message syntax error.

Recommended Action No action is required.

%CBR-4-REG_ACK_REJ_UNSPECIFIED : <133>CMTS[DOCSIS]:<73030200> REG ACK rejected unspecified reason. CM Mac Addr <[enet]>

Explanation CM Reg Ack message rejected.

Recommended Action No action is required.

%CBR-4-REGISTRATION_ABORT_NO_REG_ACK : <133>CMTS[DOCSIS]:<73030100> REG aborted ,no REG-ACK. CM Mac Addr <[enet]>

Explanation CM Reg aborted. No CM REG_ACK message.

Recommended Action No action is required.

%CBR-4-REGISTRATION_BEFORE_TFTP : Registration request unexpected: Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <[enet]>

Explanation Registration request unexpected: Cable Modem did not attempt TFTP

Recommended Action No action is required.

%CBR-4-REGISTRATION_BEFORE_TFTP_MARK : Registration request unexpected: Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <[enet]>

Explanation Registration request unexpected: Cable Modem did not attempt TFTP

Recommended Action No action is required.

%CBR-4-REG_REJ_AUTH_FAIL_CMTS_MIC_INVALID : <133>CMTS[DOCSIS]:<73000500> Registration rejected authentication failure: CMTS MIC invalid. CM Mac Addr <[enet]>

Explanation Registration rejected authentication failure: CMTS MIC invalid

Recommended Action No action is required.

%CBR-4-REG_REJ_AUTH_FAIL_TLV_PARAMS_MISMATCH : <133>CMTS[DOCSIS]:<73000501>Registration authentication failure: REG REQ rejected TLV parameters do not match learned config file TLV parameters. CM Mac Addr <[enet]>

Explanation REG REQ TLV parameters do not match learned config fileTLV parameters

Recommended Action No action is required.

%CBR-4-REG_REQ_AUTH_FAILURE : <133>CMTS[DOCSIS]:<73020109> REG REQ rejected -Authorization failure . CM Mac Addr <[enet]>

Explanation CM Registration Request Authorization failure.

Recommended Action No action is required.

%CBR-4-REG_REQ_DS_SELECTION_FAIL : DS Selection failed for Cable Modem [enet] in [chars]

Explanation CMTS cannot proceed with handling modem's Registration Request

Recommended Action No action is required.

%CBR-4-REG_REQ_DUPLICATE_REF_ID_INDEX : <133>CMTS[DOCSIS]:<73020107> REG REQ rejected duplicate reference-ID or index in message . CM Mac Addr <[enet]>

Explanation CM Registration Request message contains a duplicate ID or index.

Recommended Action No action is required.

%CBR-4-REG_REQ_INVALID_MAC_HEADER : <133>CMTS[DOCSIS]:<73010100> REG REQ has Invalid MAC header. CM Mac Addr <[enet]>

Explanation REG REQ has Invalid MAC header

Recommended Action No action is required.

%CBR-4-REG_REQ_MAJOR_CLASSIFIER_ERROR : <133>CMTS[DOCSIS]:<73020111> REG REQ rejected -Major classifier error . CM Mac Addr <[enet]>

Explanation CM Registration Request classifier error.

Recommended Action No action is required.

%CBR-4-REG_REQ_MAJOR_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<73020113> REG REQ rejected -Multiple major errors. CM Mac Addr <[enet]>

Explanation CM Registration Request mulitiple errors.

Recommended Action No action is required.

%CBR-4-REG_REQ_MAJOR_PHS_RULE_ERROR : <133>CMTS[DOCSIS]:<73020112> REG REQ rejected -Major PHS rule error . CM Mac Addr <[enet]>

Explanation CM Registration Request PHS rule error.

Recommended Action No action is required.

%CBR-4-REG_REQ_MAJOR_SRV_FLOW_ERROR : <133>CMTS[DOCSIS]:<73020110> REG REQ rejected -Major service flow error . CM Mac Addr <[enet]>

Explanation CM Registration Request service flow error.

Recommended Action No action is required.

%CBR-4-REG_REQ_MSG_SYNTAX_ERROR : <133>CMTS[DOCSIS]:<73020114> REG REQ rejected -Message syntax error . CM Mac Addr <[enet]>

Explanation CM Registration Request syntax error.

Recommended Action No action is required.

%CBR-4-REG_REQ_MSG_TOO_BIG : <133>CMTS[DOCSIS]:<73020116> REG REQ rejected -Message too big. CM Mac Addr <[enet]>

Explanation CM Registration Request message to large.

Recommended Action No action is required.

%CBR-4-REG_REQ_MULTIPLE_ERRORS : <133>CMTS[DOCSIS]:<73020106> REG REQ rejected -Multiple errors. CM Mac Addr <[enet]>

Explanation CM Registration Request msg contains multile errors.

Recommended Action No action is required.

%CBR-4-REG_REQ_PARAM_INVALID : <133>CMTS[DOCSIS]:<73020108> REG REQ rejected parameter invalid for context. CM Mac Addr <[enet]>

Explanation CM Registration Request conatins a invalide parameter for context.

Recommended Action No action is required.

%CBR-4-REG_REQ_PERMANENT_ADMINISTRATIVE : <133>CMTS[DOCSIS]:<73020103> REG REQ rejected -Permanent administrative . CM Mac Addr <[enet]>

Explanation REG REQ rejected - Permanent administrative.

Recommended Action No action is required.

%CBR-4-REG_REQ_PRIM_SRV_FLOW_ERROR : <133>CMTS[DOCSIS]:<73020115> REG REQ rejected -Primary service flow error. CM Mac Addr <[enet]>

Explanation CM Registration Request primary service flow error.

Recommended Action No action is required.

%CBR-4-REG_REQ_TEMPORARY_NO_RESOURCE : <133>CMTS[DOCSIS]:<73020102> REG REQ rejected -temporary no resource . CM Mac Addr <[enet]>

Explanation REG REQ rejected - temporary no resource .

Recommended Action No action is required.

%CBR-4-REG_REQ_UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<73020101> REG REQ rejected -Unrecognized configuration setting. CM Mac Addr <[enet]>

Explanation REG REQ rejected - Unrecognized configuration setting .

Recommended Action No action is required.

%CBR-4-REQUIRED_PARAMETER_NOT_PRESENT : <133>CMTS[DOCSIS]:<73020104> REG REQ rejected , Required parameter not present. CM Mac Addr <[enet]>

Explanation Required parameter not present

Recommended Action No action is required.

%CBR-4-REQUIRED_TLV_ABSENT : <133>CMTS[DOCSIS]:<73010400> REG REQ missed Required TLV's. CM Mac Addr <[enet]>

Explanation REG REQ missed Required TLV's

Recommended Action No action is required.

%CBR-4-RETRIES_EXHAUSTED_POLL_CM : <133>CMTS[DOCSIS]:<82010200> Retries exhausted for polled CM Mac Addr <[enet]>. After 16 R101.0 errors.

Explanation Retries exhausted for polled CM . After 16 R101.0 errors.Note: this is different from R102.0 in that it was able to try, i.e. got REQ's but failed to Range properly.

Recommended Action Please look for possible noise or other RF plant problems on the upstream channel

%CBR-4-SERVICE_FLOW_ERROR : CM MAC: [chars] Service flow direction: [chars], Param code: [dec], Confirm code: [dec]

Explanation Looks like issue while admitting/activating Service flow

Recommended Action Please look for DOCSIS message logs followed for more details

%CBR-4-SERVICE_FLOW_INDEX_ERROR : [chars] [dec]/[dec], nb_unique_index: [dec], SFID: [dec], index: [dec] flow-chid: [dec] wb-mode: [dec] dsid: [dec] cm [enet]

Explanation Looks like issue while allocating remote downstream index

Recommended Action Please see show cable modem pri and show int cx/y/z service-flow for more details

%CBR-4-SERVICE_FLOW_ZERO_BLAZE_INDEX_ERROR : spa_num: [dec], spa_if_num: [dec], nb_unique_index: [dec], lc_slot: [dec], lc_subslot: [dec], SFID: [dec], Blaze index: [dec]

Explanation Looks like issue while allocating remote downstream blaze index

Recommended Action Please see show cable modem and show int cx/y/z service-flow for more details

%CBR-4-SERVICE_PERMANENTLY_UNAVAILABLE : <133>CMTS[DOCSIS]:<73000403> Service unavailable -Permanent. CM Mac Addr <[enet]>

Explanation Service Permanently unavailable

Recommended Action No action is required.

%CBR-4-SERVICE_TEMPORARILY_UNAVAILABLE : <133>CMTS[DOCSIS]:<73000402> Service unavailable -Temporarily unavailable. CM Mac Addr <[enet]>

Explanation Registration Failed, Service temporarily not available

Recommended Action No action is required.

%CBR-4-SERVICE_UNAVAIL_OTHER : <133>CMTS[DOCSIS]:<73000400> Service unavailable -Other. CM Mac Addr <[enet]>

Explanation Registration Failed :Service Unavailable

Recommended Action No action is required.

%CBR-4-SIDERRORDCC : Tried to allocate new SID [dec] during DCC CM rebuild for interface [chars]: CM [enet]: SID container info: start [dec] end [dec]

Explanation Allocate SID during DCC CM rebuild

Recommended Action Assign Cable Modem to another interface

%CBR-4-SIDWITHOUTCM : SID [dec] not bound to any CM.

Explanation This SID does not have a valid CM database pointer

Recommended Action NO action is required

%CBR-4-SPECMGMTGRP : Spectrum group [dec] with discrete frequency is not fully supported on interface [chars]

Explanation The spectrum management group is not fully supported

Recommended Action Suggest convert discrete frequency to frequency band in the group

%CBR-4-STALE_IPV4_DB_FOUND : When update IPv4 DB entry for [enet] to ip [IP_address] tableid [dec] Found stale entry for [IP_address] tableid [dec] is cm [dec] mac [enet]

Explanation Subscriber IPv4 DB entry for CM have not been cleaned

Recommended Action No action is required.

%CBR-4-SUBDB_CLEANUP_CM : Free all Subscriber DB entries for CM [enet] hwidb [chars] ip [IP_address] tableid [dec] prim sid [dec] sidp [IPV6 address]

Explanation Subscriber DB entries for CM have not been cleaned previously, clean them now.

Recommended Action No action is required.

%CBR-4-TEMPLATE_LKUP_ERROR : CM MAC: [enet] Sid: [dec], Act_Qos: [dec]

Explanation Problem while looking up qos template

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-4-TFTP_DATA_LEN_ERROR : The length of TFTP DATA packet exceeded negotiated/default block size of [dec] while downloading [chars] from [IP_address]

Explanation TFTP DATA packet received exceeded its negotiated/default block size

Recommended Action Make sure that the block size of the TFTP DATA packets does not exceed the negotiated/default block size

%CBR-4-TLV56_CONFLICT_CHANNEL_SET : Confilct with TLV56 and channel set. Either remove TLV56 from the CM config file or adjust the power plant. CM Mac Addr <[enet]> may go offline due to high power.

Explanation Registration Failed, Check TLV56 Configuration Setting

Recommended Action No action is required.

%CBR-4-UCC_RSP_NOT_RCV_ON_CHANNEL_ID : <133>CMTS[DOCSIS]:<67010100> UCC-RSP was not received on previous channel ID. CM MAC addr <[enet]>

Explanation The Upstream Channel Change Response (UCC-RSP) at the CMTS was not received through the previous channel. This could be happened in case the UCC-RSP message is lost or the cable modem is incompatibled with DOCSIS. If it appears several times, Please contact the technical services

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-4-UCC_RSP_RCV_INVALID_CHANNEL_ID : <133>CMTS[DOCSIS]:<67010200> UCC-RSP was received with invalid channel ID. CM MAC addr <[enet]>

Explanation The Upstream Channel Change Response (UCC-RSP) was received by CMTS with an invalid channel ID, This could be happened in case CMTS did not send correct channel ID as part of Upstream Channel Request (UCC-REQ) message or cable modem is incompatibled with DOCSIS

Recommended Action Enable debug cable ucc at CMTS and make sure that CMTS sends UCC-REQ with correct channel ID. If CMTS is not sending the correct channel ID, report the problem

%CBR-4-UCC_RSP_RCV_INVALID_CHANNEL_ID_NEW : <133>CMTS[DOCSIS]:<67010300> UCC-RSP was received with invalid channel ID on new channel. CM MAC addr <[enet]>

Explanation The Upstream Channel Change Response (UCC-RSP) was received by CMTS through the new channel with an invalid channel ID. This could be happened in case cable modem is incompatibled with DOCSIS. If it appears several times, Please contact the technical services

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-4-UNABLE_TO_RANGE_CM : <133>CMTS[DOCSIS]:<82010300> Unable to Successfully Range CM Mac Addr <[enet]>. Retries Exhausted.

Explanation Unable to Successfully Range CM Retries Exhausted.

Recommended Action CM reinitialize its MAC interface and attempt to reregister. check the cable plant for potential,noise or other RF problems Check the configuration of the cable interface on the CMTS that is servicing this cable modem, to ensure that the interface is enabled and properly configured

%CBR-4-UNRECOGNIZED_CONFIGURATION_SETTING : <133>CMTS[DOCSIS]:<73000401> Service unavailable -Unrecognized configuration setting. CM Mac Addr <[enet]>

Explanation Registration Failed, Unrecognized Configuration Setting

Recommended Action No action is required.

%CBR-4-UNSPECIFIED_REASON : <133>CMTS[DOCSIS]:<73020100> REG REQ rejected , Unspecified Reason . CM Mac Addr <[enet]>

Explanation Unspecified Reason

Recommended Action No action is required.

%CBR-4-UPSTREAM_CHANNEL_CHANGE_WITH_REG_REQ : <133>CMTS[DOCSIS]:<73010601> Bad US CH -Change followed with (RE-) Registration REQ. CM Mac Addr <[enet]>

Explanation REG REQ : Bad US CH -Change followed with (RE-) Registration REQ .

Recommended Action No action is required.

%CBR-4-VERSION_MISMATCH : Midplane data version mismatch.

Explanation Data stored in midplane is out of date and needs update.

Recommended Action Contact technical support to update your system.

%CBR-5-ATTRIBUTE_CHANGE_CONFLICT : <133>CMTS[DOCSIS]:<75010100> Attribute Masks for SF (SFID [int]) do not satisfy the provisioned Attribute Masks

Explanation Change in provisioned attribute mask causes mismatch

Recommended Action Modify provisioned attributes such that it meets requirements

%CBR-5-BADMNCSMSG : Invalid DOCSIS Message (Type [dec]) received from the CM [enet] for interface [chars]

Explanation This is a DOCSIS Message, but not an appropriate message for the cBR.

Recommended Action Locate Cable Modem sending this message and replace with DOCSIS compliant modem.

%CBR-5-BPKMDROPEXCESS : CMTS deleted excessive [chars] Requests Cable Modem [enet] with Sid [dec]

Explanation Cable Modem did excessive BPKM requests.

Recommended Action Check modem interface configuration for privacy mandatory, or noise on the plant.

%CBR-5-CLASSFAIL : Registration failed for Cable Modem [enet] on interface [chars][chars]: [chars]

Explanation The registration of this modem failed due to an invalid or unsupported Class of Service setting.

Recommended Action Make sure the Class of Service fields in the configuration file are set correctly.

%CBR-5-CLEAR_ARP_INTERFACE : Clearing all ARP entries for interface [chars]

Explanation All the entries have been cleared

Recommended Action No action is required.

%CBR-5-CLEAR_ARP_TABLE : Clearing all ARP entries

Explanation All the entries have been cleared

Recommended Action No action is required.

%CBR-5-CLONED_CM_DETECTED : Cloned CM with MAC address [enet] connection attempt rejected on [chars] U[dec]

Explanation There might be a hacking attempt going on.

Recommended Action Look for possible hacking attempt

%CBR-5-DBDSPRECOVER1 : Trying to switch to backup dsp image

Explanation Trying to recover DSP using backup image

Recommended Action No action is required.

%CBR-5-DBDSPRECOVER2 : Switching to backup dsp image succeeded

Explanation Switching to backup dsp image succeeded

Recommended Action No action is required.

%CBR-5-DBDSPRECOVER3 : Recovering and switching back to regular dsp image succeeded

Explanation DSP recover operation using backup image succeeded

Recommended Action No action is required.

%CBR-5-DBDSPUP : Handshake DSP is successful after [dec] ms delay

Explanation DSP is up and running

Recommended Action No action is required.

%CBR-5-DIAG_LOG_LOW_THRSHLD_REACHED : [DOCSIS]:<86000200>Docs Diag Log reaches low threshold

Explanation Docs Diag Log Notification :log size reaches low threshold

Recommended Action No action is required.

%CBR-5-EAEREJECT : EAE registration rejected CM [enet] on Interface [chars]

Explanation CM registration rejected to force EAE policy.

Recommended Action No action is required.

%CBR-5-EXCESSIVE_SAV_GROUP_IDS : More than 1 SAV Group ID in registration request for CM MAC <[enet]>. Ignoring the excessive group ids

Explanation There may be more than 1 SAV Group IDs specified in the in the configuration file

Recommended Action Please inspect the configuration file

%CBR-5-EXCESSIVE_SAV_PREFIXES : More than [dec] SAV prefixes in the registration request for CM MAC <[enet]>. Ignoring the excessive prefixes

Explanation There are excessive number of SAV prefixes in the configuration file

Recommended Action Please inspect the configuration file

%CBR-5-EXPIREDBPITIMEOUT : CMTS deleted BPI [chars] expired Cable Modem [enet] with Sid [dec]

Explanation Expired cable modem deleted to enforce CM go through BPI authorization.

Recommended Action Check modem interface configuration for privacy mandatory, or noise on the plant.

%CBR-5-KEEPALIVE : Keepalive shutting down interface [chars].

Explanation No activity detected within the Keepalive timeout period on the interface.

Recommended Action Check RF path for failure.

%CBR-5-MACTSSLDERR : CMTS MAC TGC load pulse error, sync-pulse interval [dec]

Explanation MAC FPGA TGC load pulse generation error

Recommended Action Replace defective Line Card

%CBR-5-MALFORMED_MODEM_TLV : PARSER-ERR: Next TLV (type=[int]), steps beyond end of TLV block.t TLV-addr:[hex]. TLV-blk-limits:{[hex],[hex],[hex]} for modem [enet] sid:[int] in [chars].

Explanation Malformed TLV found in parsing

Recommended Action Please check if the modem's behavior is correct

%CBR-5-MAXHOST : Interface [chars], New host with MAC [enet] on SID [dec] (CM [enet]) is ignored: [chars]. Count [dec]

Explanation Number of hosts on the SID has been exceeded.

Recommended Action Locate the Cable Modem in question

%CBR-5-NOMULTIPLEUPSTREAMS : Upstream Channel Change not valid for interface [chars]

Explanation The software does not support this command for this interface

Recommended Action Please use this command on a multiple upstream Line card

%CBR-5-OVERLIMIT : Interface [chars] Current total reservation of [dec] bps on Port U[dec], exceeds its maximum configured reservation limit of [dec] bps.

Explanation The currently reserved capacity on the upstream channel already exceeds the virtual reservation capacity of that upstream channel (based on configured subscription level limit).

Recommended Action Need to load balance modems requesting reserved upstream rate on some other upstream channel, or increase the subscription level limit on current upstream channel at increasing risk of not being able to guarantee the individual reserved rates for modems if this upstream channel is already oversubscribed beyond raw capacity

%CBR-5-TEKREQTIMEOUT : CMTS deleted BPI Cable Modem [enet] because traffic not encrypted

Explanation Cable modem deleted to force modem to request TEK.

Recommended Action Check upsteam utilization to ensure bandwidth available for TEK request. Noise on the plant can cause this also.

%CBR-5-TIMESCH : Time scheduled event, spectrum group [int], [chars]

Explanation A time scheduled reconfiguration event occurred on an interface.

Recommended Action No action is required.

%CBR-5-TRAFSHAPBADTIMER : Bad timer expiry in downstream traffic shaper process, Timer [hex]

Explanation An unknown downstream traffic shaper timer has expired.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

%CBR-5-TRAFSHAPNOCREAT : Unable to create downstream traffic shaping queues

Explanation A possible memory error has occurred which is preventing the software from creating downstream traffic shapping queues.

Recommended Action Gather information about running configuration and amount of memory in the system and report it to your technical support representative.

%CBR-5-TRAFSHAPPROCFAIL : Unable to fork downstream shaper process

Explanation A possible memory error has occurred which is preventing the software from creating the downstream shaper process.

Recommended Action Gather information about running configuration and amount of memory in the system and report it to your technical support representative.

%CBR-5-UCDCCCERR : CMTS UCD failed to update CCC on [chars] U[dec], lch_state [dec]

Explanation UCD update CCC error

Recommended Action Check the lch_state, reset the upstream if necessary

%CBR-5-UNAUTHSIDTIMEOUT : CMTS deleted BPI unauthorized Cable Modem [enet]

Explanation Unauthorized cable modem deleted to enforce CM go through BPI authorization.

Recommended Action Check modem interface configuration for privacy mandatory, or errors in tftp configuration file.

%CBR-5-UNREGSIDTIMEOUT : CMTS deleted unregistered Cable Modem [enet]

Explanation Unregistered cable modem deleted to avoid unaccounted bandwidth usage.

Recommended Action Check modem i/f config for registration bypass, or errors in tftp config file.

%CBR-5-UPDOWN : Interface [chars] U[chars], changed state to [chars]

Explanation The upstream port was brought up or down.

Recommended Action No action is required.

%CBR-5-USCONTEND : Interface [chars] U[dec], frequency hop ended at [int].[int] MHz

Explanation At least one modem came back online. This message logs the abort of frequency hop.

Recommended Action No action is required.

%CBR-5-USCONTHOP : Interface [chars] U[dec], frequency hop started

Explanation All modems just went offline. This message logs the start of frequency hop.

Recommended Action No action is required.

%CBR-5-USCWCHG : [chars], channel width changed to [int] kHz

Explanation The upstream channel width was changed.

Recommended Action No action is required.

%CBR-5-USFREQCHG : Interface [chars] U[chars], changed to Freq [int].[int] MHz

Explanation The upstream channel frequency was changed.

Recommended Action No action is required.

%CBR-5-USIPLCHG : [chars], input power level changed to [dec] dBmV

Explanation The upstream channel input power level was changed.

Recommended Action No action is required.

%CBR-5-USIPLFIX : Interface [chars] U[dec], input power level fixed at [dec] dBmV

Explanation Setting the upstream frequency to a fixed value caused the upstream input power level to assume a fixed value.

Recommended Action No action is required.

%CBR-5-USIPLINVALID : Interface [chars] U[dec], input power level is outside of valid range due to channel width change

Explanation The upstream channel input power level is invalid.

Recommended Action No action is required.

%CBR-5-USJIB3NBC : Interface [chars] U[dec], INFO: receives collision no burst

Explanation A collision happens on an upstream channel

Recommended Action If consistently, offending modems/channel can be found by test cable jib3us show intr-logs 1 on LC console and show cable modem on the interface

%CBR-5-USMODCHANGE : [chars] , dynamic modulation changed to [chars]

Explanation Dynamic modulation change from QAM to QPSK and vice-versa.

Recommended Action No action is required.

%CBR-5-USMODCHANGE_WARN : Interface [chars] U[dec], new profile [dec] is [chars] than old profile [dec]

Explanation Print warning message about the increase or decrease in through-put

Recommended Action No action is required.

%CBR-5-USPHY_BAD_INTR : USPHY with physical channel [dec] gets too many error interrupts

Explanation US PHY or MAC chips on the LC get into a bad state and SW can not recover it

Recommended Action Collect show tech, and then power cycle the Line card. If problem does not recover, contact Cisco for support

%CBR-5-USPHYTSSDISC : PHY TSS discontinuous on [chars] U[dec] old<T [hex], M [hex], F [hex]> new<T [hex], M [hex], F [hex]>, start<T [hex], M [hex], F [hex]> mac<T [hex], M [hex], F [hex]>, tgc/frame [hex], mslot/frame [hex]

Explanation PHY TSS error

Recommended Action If the problem is persistent, modify minislot size and reset the upstream

%CBR-5-USPHYTSSLATE : PHY late TSS on [chars] U[dec] MAC [hex], phy <last [hex] curr [hex]> tgc/frame [hex]

Explanation late PHY TSS SNAPSHOT messages are received

Recommended Action This is an internal failure and not necessarily problematic

%CBR-5-USTSSMISMATCH : MAC-PHY TSS mismatch [chars] U[dec]: MAC<T [hex], M [hex], F [hex]> PHY<T [hex], M [hex], F [hex]> Old-PHY<T [hex], M [hex], F [hex]> start<T [hex], M [hex], F [hex]>, curr [hex], tgc/fame [hex], mslots/fame [hex]

Explanation Mis-matched MAC-PHY TSS is detected

Recommended Action This is an internal failure and not necessarily problematic

%CBR-5-USTSSNOTALIGNED : MAC-PHY TSS on [chars] U[dec] not at frame boundary, MAC<T [hex], M [hex], F [hex]> start <T [hex], M [hex], F [chars]> current<T [hex]>, tgc/frame [hex], mslot/frame [hex]

Explanation PHY TSS is not sampled at frame boundary

Recommended Action This is an internal failure and not necessarily problematic

%CBR-5-WIDEBAND_AUTORESET : Reset total [dec] wideband capable cable modem(s) which registered in narrow band mode for MAC Domain [chars].

Explanation wideband autoreset feature reset wideband capable cable modem(s) which registered in narrow band mode.

Recommended Action No action is required.

%CBR-6-ACFE_NOTIFICATION : [chars]

Explanation A special event happened in ACFE algorithm module

Recommended Action No action is required.

%CBR-6-ACTIVE : Cable clock [chars] reference active

Explanation The clock reference became active

Recommended Action Informational only

%CBR-6-ALARM_INFO : [chars] [chars] [chars] [chars] [chars]

Explanation Alarm assertion or deassertion information.

Recommended Action No action is required.

%CBR-6-BADIPSOURCE : Interface [chars], IP packet from invalid source. IP=[IP_address], MAC=[enet], Expected SID=[dec], Actual SID=[dec]

Explanation There might be a spoofing attempt going on.

Recommended Action Look for possible spoofing attempt

%CBR-6-CACHE_ENGINE_BUF_FULL : Max. cache buffer has been reached!

Explanation Max. cache buffer has been reached. cache engine service for current request is denied.

Recommended Action .

%CBR-6-CGD_AUTO_DCID_PARSE_ERROR : Parse error during sync newly assigned automatic DCID while running CGD command.

Explanation A parse error has occured while trying to sync the newly assigned DCID to standby PRE.

Recommended Action Remove and attempt to add the channel set again.

%CBR-6-CGD_AUTO_DCID_UNAVAILABLE : Unable to assign an automatic channel ID for channel in the FN and MD for downstream [dec]/[dec]/[dec]:[dec] in FN [dec]

Explanation Unable to assign an automatic Channel ID for the newly added channel in the MAC Domain. See show cable fiber-node to see channel ID assignments in the Fiber-Node.

Recommended Action Attempt to manually resolve channel ID conflict by disabling automatic DCID assignment.

%CBR-6-CMMOVED : Cable modem [enet] has been moved from interface [chars] to interface [chars].

Explanation The cable modem has been detected ranging on a new interface.

Recommended Action Informational only

%CBR-6-CM_OFFLINE_WITH_DUP_MPLSPEER_VCID : MPLS PEER [IP_address] VCID [int] in use, sending CM [enet] offline

Explanation MPLS PEER & VCID is in use. Send offline message to CM.

Recommended Action Check L2VPN MPLS PEER & VCID specified in CM configuration file

%CBR-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE : DOCSIS L2VPN not enabled, sending CM [enet] offline

Explanation Cable Modem is configured with L2VPN, but CMTS L2VPN isn't enabled. Send offline message to CM.

Recommended Action Configure cable l2-vpn-service xconnect nsi dot1q interface . and cable l2-vpn-service nsi dot1q commands.

%CBR-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED : Already configured for legacy TLS, sending CM [enet] offline

Explanation Legacy TLS is already configured. Send offline message to CM.

Recommended Action Check CMTS configuration for legacy TLS with this CM

%CBR-6-CM_OFFLINE_WITH_MPLS_L2VPN_NOT_ENABLE : DOCSIS MPLS L2VPN not enabled, sending CM [enet] offline

Explanation Cable Modem is configured with L2VPN, but CMTS MPLS L2VPN isn't enabled. Send offline message to CM.

Recommended Action Configure cable l2-vpn-service xconnect nsi mpls command.

%CBR-6-CM_OFFLINE_WITH_NO_FREE_VPNID : No free VPNIDs remaining, sending CM [enet] offline

Explanation There aren't any free VPNIDs. Send offline message to CM.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-6-CM_OFFLINE_WITH_UNRESOLVED_MPLSPEER_NAME : Unable to resolve MPLS NAME [chars] VCID [int], sending CM [enet] offline

Explanation Unable to resolve MPLS NAME via DNS. Send offline message to CM.

Recommended Action Check L2VPN MPLS PEERNAME specified in CM configuration file Or DNS configuration and setup

%CBR-6-CM_OFFLINE_WITH_VLANID_USED : VLANID [int] on [chars] in use, sending CM [enet] offline

Explanation VLANID is in use. Send offline message to CM.

Recommended Action Check L2VPN VLANID specified in CM configuration file

%CBR-6-CM_RNG_CLASS_ID_UNMATCH : US that CM [enet] send Initial Rng Req has unmatched Channel Class ID([hex]) with CM's Ranging Class ID([hex])

Explanation CM's Ranging Class ID doesn't match the the Channel Class ID of its upstream, but it may be expected due to CM received a DCC/DBC..., or CM config file included extended Ranging Class ID

Recommended Action No action is required.

%CBR-6-CMTS_MD_IDX_OUT_OF_RANGE_ERROR : Mac Domain Index [dec] is out of range.

Explanation Mac Domain Index is out of range.

Recommended Action No action is required.

%CBR-6-CMTS_SLOT_OUT_OF_RANGE_ERROR : Slot [dec]/Subslot [dec]/MD [dec] is out of range.

Explanation Slot/subslot is out of range.

Recommended Action No action is required.

%CBR-6-COMPAT_NEW_CARD : The old card <[chars]> is replaced by new card <[chars]> in slot [dec].

Explanation OIR: card replacement

Recommended Action No action is required.

%CBR-6-COMPAT_SHUTDOWN_CARD : Failed to restore the configuration for [chars].

Explanation OIR-compatiblity configuration restore failed

Recommended Action Configure the interface manually

%CBR-6-CONFIG_EXIT : Exiting config mode by [chars] since Port Adapter in slot [dec] removed

Explanation The user was configuring a port adapter which was either removed from the system or if an mc28u card was reset. Therefore, the configuration mode is invalid, and terminated by IOS

Recommended Action No action is required.

%CBR-6-CPE_MOVED_FROM_WRONG_SID_CHAIN : CPE [enet] was moved from SID Chain [dec] to [dec] from [chars] of the chain

Explanation The CMTS automatically corrected a condition where the CPE was in the wrong SID chain.

Recommended Action No action is required.

%CBR-6-CREATE_MAUTH_PROF : <132>CMTS[DOCSIS]:<89010300> Multicast Profile [chars] created for CM Mac [enet].

Explanation CMTS automatically creates an IP Multicast Profile

Recommended Action No action is required.

%CBR-6-DBDSPDOWNLOADDONE : Downloading dsp code completed

Explanation Downloading dsp code completed

Recommended Action No action is required.

%CBR-6-DBDSPDOWNLOADSTART : Downloading dsp code initiated

Explanation Downloading dsp code started

Recommended Action No action is required.

%CBR-6-DBDSPVERSION : Current DSP version : [dec], DSP flash version : [dec]

Explanation The current code version and the version DSP booted up with

Recommended Action No action is required.

%CBR-6-DDC_CFG_HASHFILTER_REMOVED : Hash-filter [dec] not present in global config -Filter removed from [chars]

Explanation The hash-filter was removed from the global config while the card was not present in the chassis, therefore the corresponding interface hash filter is removed from the config

Recommended Action No action is required.

%CBR-6-DDC_CFG_TARGET_REMOVED : Redundancy target invalid -removed from [chars]

Explanation The router's my_id was config removed while the card was not present in the chassis, therefore the redundancy target cli is removed from the interface

Recommended Action No action is required.

%CBR-6-DIFFENCADJUST : Differential-encoding is disabled on interface [chars] upstream [chars], it is only supported for QPSK or QAM16.

Explanation Differential-encoding is only supported for QPSK or QAM16.

Recommended Action Informational only

%CBR-6-DRVMP : Midplane TDM clock reference defaults to Clockcard

Explanation Clockcard primary reference is from midplane TDM clock

Recommended Action Informational only

%CBR-6-DSPRIMARYSFIDCONFLICT : Assigned ds primary sfid [dec] conflicts with existing ds primary sfid [dec] for Cable modem [enet] on interface [chars]

Explanation The assigned downstream primary SFID conflicts with the existing downstream primary SFID for the cable modem.

Recommended Action Informational only

%CBR-6-DUAL_CLEANUP_ATTEMPT : Second cleanup for modem

Explanation A modem entry was attempted to be cleaned up twice

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR-6-FECKBYTEADJUST : [chars] burst's FEC K BYTE in mod profile [dec] is adjusted to [dec] bytes.

Explanation The FEC K bytes in the burst profile adjusted to a valid value.

Recommended Action Informational only

%CBR-6-FREERUN : Cable clock in Freerun mode

Explanation Clockcard is in free run mode

Recommended Action Informational only

%CBR-6-GRDIDX_LOG : DS [int]/[int]/[int] Index [int] DSID [hex] SID [int] SF_BU [int] FW [chars] [int]/[int]/[int]:[int] MD Ca[int]/[int]/[int] [chars] [chars]

Explanation Debug message for Guardian index operations

Recommended Action No action is required.

%CBR-6-GUARDSYMLENADJUST : [chars] burst's guard symbol length in mod profile [dec] is adjusted to [dec] symbols.

Explanation The guard symbol length in the burst profile adjusted to a valid value.

Recommended Action Informational only

%CBR-6-HOLDOVER : Cable clock in Holdover mode

Explanation Clockcard switched to holdover mode

Recommended Action Check reference source

%CBR-6-HOTLISTMAC : Investigating MAC=[enet] sid [dec] interface [chars]: MAC blocked

Explanation CMTS glean function received blocked mac addr

Recommended Action Check for spoofing: CPE using blocked mac addr

%CBR-6-INTERNAL_XCONNECT_INTERFACE_ERROR : Unable to create internal xconnect bundle interface

Explanation Unable to find free bundle interface for l2vpn xconnect function

Recommended Action Free one bundle interface for internal l2vpn xconnect function

%CBR-6-LCHDIFFENCADJUST : Differential-encoding is disabled on interface [chars] upstream [chars], it should be supported by all active logical channels.

Explanation Differential-encoding should be supported on all logical channels.

Recommended Action Informational only

%CBR-6-LOS : Cable clock [chars] reference Loss of Signal

Explanation The clock reference was lost

Recommended Action Check reference source

%CBR-6-MACCLTCLR : Enable mac mgmt msg processing on [chars].

Explanation The RP has reenabled the sending of DOCSIS MAC-layer messages on the cable interfaces after an N+1 switchover.

Recommended Action No action needed.

%CBR-6-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED : <132>CMTS[DOCSIS]:<66060510> Map Reject -Downstream traffic flow not mapped to BPI+SAID. CM Mac Addr <[enet]>

Explanation Map Reject - Downstream traffic flow not mapped to BPI+SAID

Recommended Action No action is required.

%CBR-6-MAP_UPSTREAM_BW_ALLOCATION : <135>CMTS[DOCSIS]:<77000100> A transmit opportunity was missed because MAP arrived too late

Explanation A transmit opportunity was missed because MAP arrived too late

Recommended Action If the problem persists with a particular cable modem reboot the cable modem, and check for possible hardware or software problems with that cable modem, If this problem occurs with many cable modems,check the cable plant for RF transmission and noise ingress problems.

%CBR-6-MCAST_IPC_HEADER_ADD_FAILURE : Multicast IPC header could not be added for source [chars], group [chars], fwd interface [chars]

Explanation Multicast IPC header could not be added

%CBR-6-MCAST_SESS_NOT_AUTH : <132>CMTS[DOCSIS]:<89010200> Multicast session [chars] is not authorized for CM [enet]

Explanation Default configured action for IGMP Join is denied or the matching session rule's action is denied or the maximium session limit for the modem has been reached.

Recommended Action No action is required.

%CBR-6-MD_DS_SG_DCID_CONFLICT : Downstream channel IDs conflict in mac-domain of [chars]

Explanation At least two channels in the mac-domain have the same downstream channel ID. See show cable fiber-node to see channel ID assignments

Recommended Action Change the downstream channel ID.

%CBR-6-MDIDX_LOG : GRD [int]/[int] Index [int] SID [int] SF [int] FW [chars] [int]/[int]/[int]:[int] MD [chars] [chars] [chars]

Explanation Debug message for MAC Domain index operations

Recommended Action No action is required.

%CBR-6-MQOS : Power supply may be overloaded to support the line card installed in slot [dec]

Explanation The power supply may be insufficient to support the number of line cards installed in the system under certain operation conditions like high temperature and high voltage margining.

Recommended Action Upgrade the power supply as soon as possible or the system may fail to operation properly under some certain operation conditions.

%CBR-6-PKTCBL_COPS_CONNECTION_DOWN : Cops connection: IP addr: [IP_address] Handle: [hex] went down, Error code: [dec]

Explanation Cops connection went down

Recommended Action Check cops connection

%CBR-6-PKTCBL_COPS_CONNECTION_UP : Cops connection: IP addr: [IP_address] Handle: [hex] is up

Explanation Cops connection is up

Recommended Action No action is required.

%CBR-6-PREAMLENADJUST : [chars] burst's preamble length in mod profile [dec] is adjusted to [dec] bits.

Explanation The preamble length in the burst profile adjusted to a valid value.

Recommended Action Informational only

%CBR-6-PREAMLENCHECK : preamble length exceeds total of 128 byte.

Explanation The preamble length exceeds total of 128 byte.

Recommended Action Informational only

%CBR-6-REFLOCK : Cable clock locked to [chars] reference

Explanation Clockcard locked onto clock source

Recommended Action Informational only

%CBR-6-RF_CHAN_DCID_CONFLICT : The downstream channel id's conflict for [chars] rf-channel [dec] could not be resolved by automatic DCID assignment.

Explanation Auto DCID assignment fails to assign valid DCID for a specific channel See show cable fiber-node for detail channel ID assignments

Recommended Action Check fiber node and downstream channel configuration.

%CBR-6-RSINTRLVBLKSIZEADJUST : [chars] burst's RS interleave block size in mod profile [dec] is adjusted to [dec] bytes.

Explanation The RS interleave block size in the burst profile adjusted to a valid value.

Recommended Action Informational only

%CBR-6-RSINTRLVDEPTHADJUST : [chars] burst's RS interleave depth in mod profile [dec] is adjusted to [dec].

Explanation The RS interleave depth in the burst profile adjusted to a valid value.

Recommended Action Informational only

%CBR-6-RSINTRLVDISABLED : [chars] burst's RS interleaver in mod profile [dec] is auto disabled.

Explanation The RS interleaver in the burst profile is auto disabled.

Recommended Action Informational only

%CBR-6-SRCMP : Cable Clock primary reference is midplane TDM clock

Explanation Clockcard primary reference is from midplane TDM clock

Recommended Action Informational only

%CBR-6-USPRIMARYSFIDCONFLICT : Assigned us primary sfid [dec] conflicts with existing us primary sfid [dec] for Cable modem [enet] on interface [chars]

Explanation The assigned upstream primary SFID conflicts with the existing upstream primary SFID for the cable modem.

Recommended Action Informational only

%CBR-7-PHY_CLK_MIS_DET_MSG : Clock misalignment detected on phy [dec]:IOS det count=[dec], bad DV count=[dec], total DV count=[dec], old cal data=[hex], new cal data=[hex][chars]

Explanation A phy clock misalignment has been detected and corrected.

Recommended Action No action is required.

CBRCCE

%CBRCCE-3-CBR_DP_CFR_ADD_ERR : Failed to add cfr for CM [enet], cfr id [int], sfref [int], sfid [int], rc [int]

Explanation Mostly caused by cfr chunk exhausted or cm_qos not found

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_DYN_QOS_ERR : Failed to commit dynamic qos for CM [enet], sfid [int], rc [int]

Explanation Mostly caused by dynamic qos bind failure

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_FLOW_ADD_ERR : Failed to add flow for CM [enet], sfid [int], rc [int]

Explanation Mostly caused by flow or cm_qos chunk exhausted

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_FORW_INTF_SET_ERR : Failed to set forwarding interface for CM [enet], sfid [int], rc [int]

Explanation Mostly caused by invalid service flow ID

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_JIB_HDR_SET_ERR : Failed to set JIB header for CM [enet], sfid [int], rc [int]

Explanation Mostly caused by invalid service flow ID

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_LOCK_ERR : Failed to lock semaphore, pid [dec]

Explanation Mostly caused by a process hogging CPU

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_QOS_PARAMS_SET_ERR : Failed to set qos parameters for CM [chars], sfid [int], rc [int]

Explanation Mostly caused by invalid service flow ID

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_STA_QOS_ERR : Failed to commit static qos for CM [enet], rc [int]

Explanation Mostly caused by qos bind failure

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-3-CBR_DP_TMP_DEL_ERR : Failed to remove template from template_list for CM [enet]

Explanation Mostly caused by template remove failure

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBRCCE-4-CBR_DP_CFR_PARAM_CONFLICT : Classifier's parameters conflict: [chars]

Explanation Mostly caused by unsupported classifier's parameters combination

Recommended Action Please do not configure unsupported classifier's parameters or unsupported classifier's parameters combination as the error message indicated.

CBRDTI

%CBRDTI-5-DTISLOT : DTI slot [dec]/[dec]: card role changed to [chars]

Explanation Change in role of DTI slot

Recommended Action Check DTI link/cable

%CBRDTI-6-CHG_CLK_REF : Clock reference source set to [chars]

Explanation The reasons for the change in clock reference. (1)Manual mode configuration command for DTI mode (2)Loss of previous source reference (3)Network-Clock Synchronization

Recommended Action Check reference source of DTI

CBR_LIC

%CBR_LIC-3-APPLY_DS_FAILED : Applying downstream license failed

Explanation Unable to apply the downstream license

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-3-APPLY_LCHA_FAILED : Enforcement failed

Explanation Unable to enforce

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-3-APPLY_US_FAILED : Applying upstream license failed

Explanation Unable to apply the upstream license

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-3-APPLY_WAN_FAILED : Applying upstream license failed

Explanation Unable to apply the upstream license

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-3-CPB_OPEN_FAILED

Explanation Unable to open CPB data file. File IO error.

Recommended Action Please report to TAC

%CBR_LIC-3-CPB_READ_FAILED

Explanation Unable to read CPB data from file. File IO error.

Recommended Action Please report to TAC

%CBR_LIC-3-CPB_WRITE_FAILED

Explanation Unable to write CPB data to file. File IO error.

Recommended Action Please report to TAC

%CBR_LIC-4-CPB_SEEK_FAILED

Explanation Unable to set file position for reading and/or writing. File IO error.

Recommended Action Please report to TAC

%CBR_LIC-3-CSB_FAIL : [chars] Failed for [chars]

Explanation An attempt to parse a license related CLI failed

Recommended Action Check the linecard license details and call TAC

%CBR_LIC-3-LIC_SA_MALLOC_FAILED : [chars]

Explanation Platform malloc for Smart License Agent failed

Recommended Action Check the mem usage and report to TAC

%CBR_LIC-3-LIC_SA_NULL_FUN_PTR : [chars]

Explanation Platform getting a null function pointer from Smart License Agent

Recommended Action Report to TAC

%CBR_LIC-3-LIC_SA_REGISTER_FAILED : [chars]

Explanation Smart License Agent registr failed

Recommended Action Check call-home, pki, vrf config and the IdToken

%CBR_LIC-3-NULL_LICENSE_ENTITLEMENT : License entitlement DB is NULL!

Explanation The DS license DB is NULL

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-3-NULL_LICENSE_INFO : License DB is NULL!

Explanation The license DB is NULL

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-4-CPB_LESS_RECORD

Explanation When calculate CPB value at the beginning of natural quarter, it will check the count of CPB samples for each month in last natural quarter.

If the count is less than expected, will see this error message.

Recommended Action If it is the first month apply CPB feature, or downtime is more than 5 hours in that month, it is expected and it has no impact on service and performance of cBR. Otherwise report to TAC.

%CBR_LIC-4-CPB_SN_MISMATCH

Explanation CPB records were saved in other Chassis. If SUP is moved to other Chassis, this is expected message.

Recommended Action This is informational message, it has no impact on the service and performance of cBR, ignore the message.

%CBR_LIC-6-APPLY_BC_FAILED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License BC video Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-APPLY_NC_FAILED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License NC video Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-BC_LIC_CAPPED_RESTRICTED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License BC video Capped Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-BC_LIC_RESTRICTED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License BC video Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-CHANNEL_NO_SHUTDOWN : [chars]:[int] has been restored to no shut

Explanation Restored previously shutdown channels to no shut state

Recommended Action None

%CBR_LIC-6-CHANNEL_SHUTDOWN : [chars]:[int] has been shutdown due to deactivated enforcement

Explanation Channel shut due to enforcement

Recommended Action Buy additional licenses. Please report to TAC

%CBR_LIC-6-CHAN_NOSHUTFAIL : [chars] channel [int] no shut is not allowed due to insufficient licenses

Explanation Unable to no shut the channel due to insufficient licenses

Recommended Action Procure more licenses, report to TAC

%CBR_LIC-6-DS_LIC_ENFORCED : enforce_en:[int], [chars] is [int]

Explanation License contract violation! Enforced

Recommended Action Buy consumed additional licenses and report to TAC

%CBR_LIC-6-DS_LIC_RESTRICTED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-LCHA_CHANNEL_NO_SHUTDOWN : [chars] has been restored to no shut

Explanation Restored previously shutdown channels to no shut state

Recommended Action None

%CBR_LIC-6-LCHA_CHANNEL_SHUTDOWN : [chars]

Explanation Channel shut due to enforcement

Recommended Action Buy additional licenses. Please report to TAC

%CBR_LIC-6-LCHA_LIC_ENFORCED : enforce_en:[int], [chars] is [int]

Explanation License contract violation! Enforced

Recommended Action Buy consumed additional licenses and report to TAC

%CBR_LIC-6-LCHA_LIC_RESTRICTED : [chars] [chars]

Explanation License contract violation! License Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-LIC_CAP_LIMIT_BELOW_CONSUMED : [chars]

Explanation Capped count cannot be set! Consumed count is higher

Recommended Action Capped count cannot be set! Consumed count is higher

%CBR_LIC-6-LIC_CAPPED_DURATION_EXPIRED : Capped Enforcement duration expired. Deactivated Enforced

Explanation Capped Enforcement duration expired after an Eval or Grace expired

Recommended Action Restore communication with cisco and add entitlements if required

%CBR_LIC-6-LIC_CAPPED_DURATION_TIMER_STARTED : License [chars] period has expired. Capped enforcement is active. The router will be deactivated in 90 days

Explanation Eval or Grace Period has expired. Capped enforced - Will be deactivated in 90 days

Recommended Action Restore communication with cisco and add entitlements if out of compliance

%CBR_LIC-6-LIC_CONFIG_LOCKED : [chars]

Explanation Configuration lock in effect! Please register the cBR and try

Recommended Action Configuration lock in effect! Register the cBR and try

%CBR_LIC-6-LICENSE_ENFORCE : Enforcement mode set to [chars]

Explanation License Information has been applied

Recommended Action No action required

%CBR_LIC-6-LIC_LIMIT_NOT_SUPPORT : [chars]

Explanation Don't support Capped Enforcement for this license tag

Recommended Action License limits cannot be changed for this feature

%CBR_LIC-6-LIC_LIMIT_SET_ALREADY : [chars]

Explanation To change license limits disable license limits first

Recommended Action License limits cannot be changed without disbling license limits first

%CBR_LIC-6-LIC_OOC_DURATION_EXPIRED : OOC duration expired -Capped Enforced

Explanation OOC duration has expired and hence capped enforced

Recommended Action Add entitlements to stay in compliance

%CBR_LIC-6-LIC_OOC_DURATION_TIMER_STARTED : License OOC timer has started. All entitlements will be Capped Enforced in 270 days. Please add necessary entitlements

Explanation OOC duration timer has started. All entitlements will be Capped Enforced in 270 days.

Recommended Action Add necessary entitlements to stay in compliance

%CBR_LIC-6-LIC_SA_DISABLED : [chars]

Explanation License contract is violated. The device is disabled

Recommended Action Report to TAC and add sufficient licenses

%CBR_LIC-6-LIC_SA_EVAL_EXPIRED : [chars]

Explanation Eval Period has expired. License agent moving to eval-expired state

Recommended Action Restore communication with cisco and register the device

%CBR_LIC-6-LIC_SA_GLOBAL_NOTIFICATION : [chars]

Explanation A global notification about an event change in the Smart License Agent was received

Recommended Action None

%CBR_LIC-6-LIC_SA_GRACE_EXPIRED : [chars]

Explanation Grace Period has expired. License agent moving to garce-expired state

Recommended Action Restore communication with cisco

%CBR_LIC-6-LIC_SA_IN_COMPLIANCE : [chars]

Explanation Smart License Agent enforcement mode changed to Incompliance

Recommended Action None

%CBR_LIC-6-LIC_SA_OUT_OF_COMPLIANCE : [chars]

Explanation Smart License Agent enforcement mode changed to out of compliance

Recommended Action Report to TAC and add sufficient licenses. If CPB (Core Peak Bandwidth) feature is enabled, this is a normally expected message currently and it has no impact on service and performance of cBR. Do not need report.

%CBR_LIC-6-LIC_SA_OVERAGE : [chars]

Explanation Smart License Agent enforcement mode changed to overage

Recommended Action Report to TAC and add sufficient licenses

%CBR_LIC-6-NC_LIC_CAPPED_RESTRICTED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License NC video Capped Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-NC_LIC_RESTRICTED : [chars] [chars]:[int] [chars]

Explanation License contract violation! License NC video Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-OUT_OF_RANGE : [chars] is out of range:[int]

Explanation License counters have reached boundary condition

Recommended Action Please copy traceback infomation and report to TAC

%CBR_LIC-6-SUBS_LIC_ENFORCED : License enforced. All CM dropped.

Explanation License contract violation! License restricted/enforced and all CMs have been dropped offline.

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-SUBS_LIC_RESTRICTED : License enforced. CM [enet] denied access

Explanation License contract violation! License restricted/enforced and a CM has been denied network access.

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-US_CHANNEL_NO_SHUTDOWN : [chars] has been restored to no shut

Explanation Restored previously shutdown channels to no shut state

Recommended Action None

%CBR_LIC-6-US_CHANNEL_SHUTDOWN : [chars] has been shutdown due to deactivated enforcement

Explanation Channel shut due to enforcement

Recommended Action Buy additional licenses. Please report to TAC

%CBR_LIC-6-US_LIC_ENFORCED : enforce_en:[int], [chars] is [int]

Explanation License contract violation! Enforced

Recommended Action Buy consumed additional licenses and report to TAC

%CBR_LIC-6-US_LIC_RESTRICTED : [chars] [chars] [chars]

Explanation License contract violation! License Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

%CBR_LIC-6-WAN_CHANNEL_NO_SHUTDOWN : [chars] has been restored to no shut

Explanation Restored previously shutdown channels to no shut state

Recommended Action None

%CBR_LIC-6-WAN_CHANNEL_SHUTDOWN : [chars] has been shutdown due to deactivated enforcement

Explanation Channel shut due to enforcement

Recommended Action Buy additional licenses. Please report to TAC

%CBR_LIC-6-WAN_LIC_ENFORCED : enforce_en:[int], [chars] is [int]

Explanation License contract violation! Enforced

Recommended Action Buy consumed additional licenses and report to TAC

%CBR_LIC-6-WAN_LIC_RESTRICTED : [chars] [chars] [chars]

Explanation License contract violation! License Restricted/Enforced

Recommended Action Buy additional licenses and report to TAC

CBR_MCAST

%CBR_MCAST-3-SF_RECOVER : Sfid [dec] Recover failed on [chars].

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

CBR_PLFM_HA

%CBR_PLFM_HA-3-CHKPTADDCLIENT : Check Point Client [dec] Add Failed -[dec]

Explanation Failed to add checkpoint client

%CBR_PLFM_HA-3-GET_DATA_PTR : [chars]: checkpoint get data pointer error

Explanation Checkpoint infra get message data pointer failed

%CBR_PLFM_HA-3-REPL : Failed to setup [chars] chasfs, reason: [chars]

Explanation Failed to create replication manager related chasfs entry which is used to trigger database sync

%CBR_PLFM_HA-3-STATESYNC : Redundancy state synchronization failure [dec]/[dec] -([chars])

Explanation A failure occurred in trying to synchronize CBR platform information

%CBR_PLFM_HA-3-STBY_FP_ERR : Standby FP failed to reach sso-ready within tolerated wait time

Explanation Standby FP failed to reach sso-ready within tolerated wait time

%CBR_PLFM_HA-3-STBY_PLL_NOT_LOCK : Standby PLL failed to lock active within tolerated wait time

Explanation Standby PLL failed to lock active within tolerated wait time

%CBR_PLFM_HA-6-STATE_CC : Lincard [dec] will be reloaded -([chars])

Explanation Lincard is not ready for sup-ha

Recommended Action No action is required.

CBR_PTP

%CBR_PTP-3-DISPATCH : Unable to dispatch received TDL message from PTP daemon

Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from PTP daemon.

%CBR_PTP-3-INITFAIL : Failed to initalize required PTP resource: [chars]

Explanation During the initialization of the resources required by PTP, a failure occured. This has prevented PTP from being activated.

%CBR_PTP-3-NITFAIL : Failed to initalize required PTP resource: [chars]

Explanation During the initialization of the resources required by PTP, a failure occured. This has prevented PTP from being activated.

%CBR_PTP-5-TOD_CHG : The TOD source changed: [chars]

Explanation The source of time of day changed: 1. from GPS of SUP-PIC 0/1 2. from DTI of SUP-PIC 0/1 3. free run mode

Recommended Action No action is required.

CBR_SPA

%CBR_SPA-0-DPIC_EMERG : [chars]-[chars]

Explanation Receive some EMERG message from DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-1-DPIC_ALERT : [chars]-[chars]

Explanation Receive some ALERT message from DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-2-DPIC_CRIT : [chars]-[chars]

Explanation Receive some CRITICAL message from DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-CORTINA_PHY_DEV_ATTACH_ERROR : [chars] Cortina PHY device attach error port [dec]/[dec]/[dec]

Explanation Unable to attach Cortina PHY device object

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-CORTINA_PHY_DEV_CREATE_ERROR : [chars] Cortina PHY device create error port [dec]/[dec]/[dec]

Explanation Unable to create Cortina PHY device object

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-CORTINA_PHY_DEV_INIT_ERROR : [chars] Cortina PHY device init error port [dec]/[dec]/[dec]

Explanation Unable to downaload firmware to Cortina PHY device

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-DPIC_BOOT_REASON : DPIC [dec]/[dec]: [chars]

Explanation DPIC Boot Error Reason

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-DPIC_ERR : [chars]-[chars]

Explanation Receive some ERR message from DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-DPIC_NGIO_ERROR : NGIO connection between IOMd and DPIC [dec]/[dec] is down!

Explanation NGIO is down between IOMd and DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-DPIC_NGIO_KEEPALIVE : NGIO keepalive between IOMd and DPIC [dec]/[dec] timeout! ([int] NGIO rx, [int] ping successes, [int] ping failures)

Explanation NGIO keepalive is timeout.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-DTI_CLIENT_DNLD_ERROR : [chars] DTI Client error

Explanation Unable to download DTI client firmware

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_CLK_NOT_RDY_ERR : [chars] Falcon ESI Clocks reg:[hex]

Explanation Falcon-ESI clocks are NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_CLOCK_NOT_READY_ERROR : [chars] Raptor ESI Clocks reg:[hex]

Explanation Raptor-ESI clocks are NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_NOT_READY_ERROR : [chars] Raptor ESI Global Ready reg:[hex]

Explanation Raptor-ESI NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PIC_PWR_NOT_GOOD_ERR : [chars] Falcon SUP PIC Power not good

Explanation Falcon-ESI PLL not locked

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PIC_PWR_NOT_GOOD_ERROR : [chars] Raptor SUP PIC Power not good

Explanation Raptor-ESI PLL not locked

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PIC_STATUS_REG_READ_ERR : [chars] unable to read from Falcon ESI PIC STATUS REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PIC_STATUS_REG_READ_ERROR : [chars] unable to read from Raptor ESI PIC STATUS REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_LOCK_ERR : [chars] unable to lock Falcon ESI PLL

Explanation Falcon-ESI PLL not locked

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_LOCK_ERROR : [chars] unable to lock Raptor ESI PLL

Explanation Raptor-ESI PLL not locked

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_REG_READ_ERR : [chars] unable to read from Falcon ESI PLL CONTROL REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_REG_READ_ERROR : [chars] unable to read from Raptor ESI PLL CONTROL REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_REG_WR_ERR : [chars] unable to write to Falcon ESI PLL CONTROL REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_PLL_CTRL_REG_WRITE_ERROR : [chars] unable to write to Raptor ESI PLL CONTROL REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_RDY_REG_READ_ERR : [chars] unable to read Falcon ESI READY REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_READY_REG_READ_ERROR : [chars] unable to read Raptor ESI READY REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_SUP_CHASSIS_SLOT_REG_WR_ERR : [chars] unable to write to Falcon ESI CHASSIS SLOT ID REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_SUP_CHASSIS_SLOT_REG_WRITE_ERROR : [chars] unable to write to Raptor ESI CHASSIS SLOT ID REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_SUP_CTRL_REG_WR_ERR : [chars] unable to write to Falcon ESI CONTROL REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-ESI_SUP_CTRL_REG_WRITE_ERROR : [chars] unable to write to Raptor ESI CONTROL REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_EGR_BUF_LOCAL_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from EGRESS LOCAL BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_EGR_BUF_PEER_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from EGRESS REMOTE BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_EGR_DISPATCH_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from EGRESS DISPATCH Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_ESI_CLOCK_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from CLOCK Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_ESI_PCIE_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from PCIE Wrapper Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_FP_EGR_SCH_TOP_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from FP EGRESS SCHDULER TOP Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_FP_INGR_PAR_TOP_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from FP INGRESS PARSER TOP Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_INGR_BUF_LOCAL_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from INGRESS LOCAL BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_INGR_BUF_PEER_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from INGRESS REMOTE BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_INGR_PARSER_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from INGRESS PARSER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_INGR_SCH_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from INGRESS SCHDULER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_INIT_ERROR : [chars] Falcon err [dec]

Explanation Falcon driver initialization error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_MAC_ENTRY_FULL : [chars] Falcon [chars] mac-filter entry full, drop addr [hex].[hex].[hex].[hex].[hex].[hex]

Explanation Falcon mac filter entry full

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_MAC_LOCAL_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from LCOAL MAC Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_MAC_PEER_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from PEER MAC Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_MODE_XCVR_MATCH_ERR : SUP-PIC [dec]/1 port [dec] interface mode mismatched: QSFP type is [chars], interface mode is [chars]

Explanation SUP250 backhaul interface support two kinds of transceiver: QSFP28 and QSFP+. If the backhaul mode is configured as 100GE mode with commad 'cable sup250-ifmod 100GE', but insert a QSFP+ transceiver. Or the backhaul mode is configured as 10GE mode with comand 'cable sup250-ifmod 10GE', but insert a QSFP28 transceiver. This error message will be reported.

Recommended Action Change configration to another backhaul mode or replace other type of transceiver.

%CBR_SPA-3-FALCON_PAR_RST_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from PAR RST Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_PLL_LOS : [chars]

Explanation Falcon PLL LOS

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_PMBIST_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from PM BIST Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-FALCON_SEM_HI_INTERRUPT : [chars], [chars], err_report_reg [hex], stat_reg [hex]

Explanation HIGH Priority Interrupt received from SEM Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_CFG_REG_WRITE_ERROR : [chars] unable to write to Raptor MAC RX/TX CFG REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_CLK_NOT_RDY_ERR : [chars] Falcon MAC Clocks reg:[hex]

Explanation Falcon-MAC clocks are NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_CLOCK_NOT_READY_ERROR : [chars] Raptor MAC Clocks reg:[hex]

Explanation Raptor-MAC clocks are NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_NOT_RDY_ERR : [chars] Falcon MAC Global reg:[hex]

Explanation Falcon-MAC Contrpl Plane NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_NOT_READY_ERROR : [chars] Raptor MAC Global reg:[hex]

Explanation Raptor-MAC Contrpl Plane NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_PIC_CPLD_NOT_RDY_ERR : [chars] Falcon MAC PIC CPLD error

Explanation Falcon-MAC PIC CPLD NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_PIC_CPLD_NOT_READY_ERROR : [chars] Raptor MAC PIC CPLD error

Explanation Raptor-MAC PIC CPLD NOT Ready

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_PIC_CTRL_REG_WR_ERR : [chars] unable to write to Falcon MAC PIC CONTROL REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_PIC_CTRL_REG_WRITE_ERROR : [chars] unable to write to Raptor MAC PIC CONTROL REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_READY_REG_READ_ERR : [chars] unable to read Falcon MAC READY REG err [dec]

Explanation Unable to communicate with Falcon Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-MAC_READY_REG_READ_ERROR : [chars] unable to read Raptor MAC READY REG err [dec]

Explanation Unable to communicate with Raptor Device driver

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-NULL_SPA_PTR :

Explanation Pointer to a SPA object is NULL.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_CLOCK_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from Clock Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_INGRESS_SCH_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from Ingress Scheduler Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_PCIE_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from PCIE Wrapper Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_PROCBUS_MASTER_HI_INTERRUPT : [chars], [chars]

Explanation HIGH Priority Interrupt received from ProcBus Master Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_PRST_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received Partial reset Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_ESI_SERDES_PKTBUS_HI_INTERRUPT : [chars], [chars]

Explanation Hign Priority Interrupt received from Serdes PktBus Module in Raptor-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_INIT_ERROR : [chars] Raptor err [dec]

Explanation Raptor driver initialization error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_LED_ERROR : SUP-PIC [dec]/[dec] LED err

Explanation SUP-PIC LED initialization error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_CLOCK_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from Clock Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_DNLD_FAILED : [chars] Raptor-MAC error

Explanation Unable to download Raptor-MAC firmware

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_ENTRY_FULL : [chars] Raptor [chars] mac-filter entry full, drop addr [hex].[hex].[hex].[hex].[hex].[hex]

Explanation Raptor mac filter entry full

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_FIFO_CTL_HI_INTERRUPT : [chars], [chars]

Explanation HIGH Priority Interrupt received from FIFO Control Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_MDIO_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from MDIO Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_PROCBUS_SLAVE_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from ProcBus Slave Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_PRST_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received Partial reset Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_RLDRAM_HI_INTERRUPT : [chars], [chars]

Explanation HIGH Priority Interrupt received from RLDRAM Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_SERDES_PKTBUS_HI_INTERRUPT : [chars], [chars]

Explanation HIGH Priority Interrupt received from Serdes PktBus Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_MAC_XFI_IF_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from XFI Module in Raptor-MAC FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_PLL_LOS : [chars]

Explanation Raptor PLL LOS

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RAPTOR_SEM_HI_INTERRUPT : [chars], [chars], err_report_reg [hex], stat_reg [hex]

Explanation HIGH Priority Interrupt received from SEM

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RETIMER_PHY_DEV_ATTACH_ERROR : [chars] Retimer PHY device attach error quad [dec]/[dec]/[dec]

Explanation Unable to attach Retimer PHY device object

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RETIMER_PHY_DEV_CREATE_ERROR : [chars] Retimer PHY device create error quad [dec]/[dec]/[dec]

Explanation Unable to create Retimer PHY device object

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-RETIMER_PHY_DEV_INIT_ERROR : [chars] Retimer PHY device init error quad [dec]/[dec]/[dec]

Explanation Unable to init Retimer PHY device

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SFP_SUB_INIT_ERROR : [chars] SFP Subblock create error

Explanation Unable to create SFP sub-block

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_DPIC_UPGRADE_NOSPACE : no enough space in harddisk to store digital pic image ([dec]MB free, [dec]MB needed)

Explanation DIGI PIC firmware can not be upgraded due to harddisk is full

Recommended Action Free up some space in harddisk to store digital pic image.

%CBR_SPA-3-SPA_PLUGIN_INIT_ABORT_ERROR : [chars] SPA Plugin Init Abort error

Explanation Unknown SPA Init phase

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_RFSW_I2C_FAILURE : I2C failure on [dec]/[dec], I2C status:[chars]

Explanation An I2C failure error received from RFSW PIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_RFSW_POWER_ERROR : Power circuit error on [dec]/[dec], voltages:[chars]

Explanation A power circuit error received from RFSW PIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_RFSW_RELAY_FAILURE : Relay failure on [dec]/[dec], relay status:[chars]

Explanation A Relay failure error received from RFSW PIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_RFSW_TEMPERATURE_ERROR : Temperature Error on [dec]/[dec], temperature:[chars]

Explanation A Temperature error received from RFSW PIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_RFSW_UPGRADE_UNSUPPORTED : unsupported firmware upgrade on [dec]/[dec], firmware version :[hex]

Explanation RFSW PIC firmware can not be upgraded

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-SPA_UNKN_INIT_ERROR : [chars] Unknown SPA Init phase error

Explanation Unknown SPA Init phase

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-XCVR_MISSING_HWIDB_ERROR : [chars] XCVR Missing interface object port [dec]/[dec]/[dec]

Explanation Unable to downaload firmware to Cortina PHY device

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-XCVR_POP_DEF_PARAMS_ERROR : [chars] XCVR Unable to poulate default parameters port [dec]/[dec]/[dec]

Explanation Unable to poulate default XCVR SM parameters

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-3-XCVR_SM_LAUNCH_ERROR : [chars] XCVR Unable to launch SM port [dec]/[dec]/[dec]

Explanation Unable to launch XCVR SM

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-4-DPIC_WARNING : [chars]-[chars]

Explanation Receive some WARNING message from DPIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-4-FALCON_PLL_MIS : [chars]

Explanation Falcon PLL clock soure not come from active RP

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-4-RAPTOR_PLL_MIS : [chars]

Explanation Raptor PLL clock soure not come from active RP

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-4-SPA_RFSW_WATCH_DOG_TIMEOUT : Watch Dog Timeout on [dec]/[dec]

Explanation A Watch Dog Timeout error received from RFSW PIC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-5-DPIC_NOTICE : [chars]-[chars]

Explanation Receive some NOTICE message from DPIC

Recommended Action No action is required.

%CBR_SPA-5-DPIC_RESET : DPIC [dec]/[dec] will be recovered from unexpected state

Explanation DPIC can not be online in 5 min

Recommended Action No action is required.

%CBR_SPA-6-DPIC_INFO : [chars]-[chars]

Explanation Receive some INFO message from DPIC

Recommended Action No action is required.

%CBR_SPA-6-SPA_DPIC_UPGRADE_UNSUPPORTED : unsupported firmware upgrade on [dec]/[dec]

Explanation DIGI PIC firmware can not be upgraded

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-DPIC_DEBUG : [chars]-[chars]

Explanation Receive some DEBUG message from DPIC

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-FALCON_EGR_BUF_LOCAL_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from EGRESS LOCAL BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_EGR_BUF_PEER_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from EGRESS REMOTE BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_EGR_DISPATCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from EGRESS DISPATCHER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_ESI_FC_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from ESI FC Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_ESI_PCIE_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from PCIE Wrapper Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_ESI_QPLL_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from PCIE Wrapper Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_FP_10G_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from FP 10G Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_FP_EGR_SCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from FP EGRESS SCHEDULER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_FP_INGR_PAR_TOP_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from FP INGRESS PARSER TOP Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_GB_MDIO_IF_HI_INTERRUPT : [chars], [chars]

Explanation High Priority Interrupt received from GB MDIO Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_INGR_BUF_LOCAL_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from INGRESS LOCAL BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_INGR_BUF_PEER_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from INGRESS REMOTE BUF Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_INGR_PARSER_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from INGRESS PARSER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_INGR_SCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from INGRESS SCHEDULER Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_INTERRUPT_DISABLE : Interrupt throttled for: [chars], [chars]

Explanation Interrupt throttled

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-FALCON_INTERRUPT_ENABLE : Interrupt enabled for: [chars], [chars]

Explanation Interrupt unthrottled

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-FALCON_MAC_LOCAL_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from LOCAL MAC Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_MAC_PEER_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from REMOTE MAC Module in Falcon FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_PAR_RST_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from PAR RST Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_PWM_DIST_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from PWM DIST Module in Falcon-ESI FPGA

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-FALCON_SEM_LO_INTERRUPT : [chars], [chars], err_report_reg [hex], stat_reg [hex]

Explanation Low Priority Interrupt received from SEM

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CBR_SPA-7-RAPTOR_ESI_EGRESS_HDR_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Egress Header Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_EGRESS_SCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Egress Scheduler Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_FC_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Flow Control Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_INGRESS_SCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Ingress Scheduler Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_PCIE_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from PCIE Wrapper Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_PROCBUS_MASTER_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from ProcBus Master Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_PRST_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received Partial reset Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_ESI_SERDES_PKTBUS_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Serdes PacketBus Module in Raptor-ESI FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_INTERRUPT_DISABLE : Interrupt throttled for: [chars], [chars]

Explanation Interrupt throttled

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_INTERRUPT_ENABLE : Interrupt enabled for: [chars], [chars]

Explanation Interrupt unthrottled

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_10G_MAC_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from 10GE MAC Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_FIFO_CTL_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from FIFO Control Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_FIFO_CTRL_MUX_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from FIFO Control MUX Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_INGRESS_QOS_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Ingress QoS Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_MAC_SCH_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from MAC Scheduler Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_PROCBUS_SLAVE_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Proc Bus Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_PRST_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received Partial reset Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_RLDRAM_IF_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from RLDRAM Interface Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_MAC_SERDES_PKTBUS_LO_INTERRUPT : [chars], [chars]

Explanation Low Priority Interrupt received from Serdes Packet Bus Module in Raptor-MAC FPGA

Recommended Action This is a debug message only. No action is required.

%CBR_SPA-7-RAPTOR_SEM_LO_INTERRUPT : [chars], [chars], err_report_reg [hex], stat_reg [hex]

Explanation Low Priority Interrupt received from SEM

Recommended Action This is a debug message only. No action is required.

CDMAN

%CDMAN-0-LOW_FPA_FATAL : Free buffer pool [dec] is at shutdown [dec] percent low level, top 3 features: ([dec], [dec]), ([dec], [dec]), ([dec], [dec])

Explanation The FPA buffer is too low level in this pool to function

Recommended Action Log a ddts

%CDMAN-2-INITIALIZATION_FAILED : Cable Device Manager initialization failed.

Explanation Initialization of the Cable Device Manager failed.

Recommended Action Review Cable Device Manager logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%CDMAN-3-CLC_FPGA_SEM_HALTED : CLC_FPGA SEM controller [dec] detected an uncorrectable error

Explanation CLC FPGA SEM module detected an uncorrectable error

Recommended Action Save Cable Device Manager logs and review with SW/HW team

%CDMAN-3-CLC_FPGA_SEM_HRT : CLC_FPGA SEM controller [dec] heartbeat has stopped

Explanation CLC FPGA SEM controller heartbeat has stopped

Recommended Action Save Cable Device Manager logs and review with SW/HW team

%CDMAN-3-CLC_FPGA_WDOG_ERR : CLC FPGA level 1 watchdog timeout [dec] sec

Explanation CLC FPGA hardware driver/ cpu hardware problem

Recommended Action Save kernel dmesg log

%CDMAN-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars]

Explanation Setup of a console service failed.

Recommended Action Check the host manager launch parameters and correct as required.

%CDMAN-3-DUPLICATE_DCD : Duplicated DCD packet received: MD [dec] received [dec] last received [dec]

Explanation Duplicated DCD packet received from the iosd

Recommended Action Check the problem in the iosd-clc

%CDMAN-3-LOW_FPA_ERROR : Free buffer pool [dec] is at [dec] percent low level, top 3 features: ([dec], [dec]), ([dec], [dec]), ([dec], [dec])

Explanation The FPA buffer is low in this pool

Recommended Action Check the FPA buffer usage. It could be permanent leak or temporary low

%CDMAN-5-CLC_FPGA_SEM_CORR : CLC_FPGA SEM controller [dec] detected a problem and performed a correction

Explanation CLC FPGA SEM module detected a problem and performed a correction

Recommended Action No user action is required.

CMCC

%CMCC-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.

Explanation Hardware in the specified location could not be identified as a genuine Cisco product

Recommended Action Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information

%CMCC-2-BAD_ID_HW_SLOT_STR : Failed Identification Test in [chars]. The module [chars] on the [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.

Explanation Hardware in the specified location could not be identified as a genuine Cisco product

CMCC_CBR

%CMCC_CBR-4-PROC_DOWN : Process [chars] is down

Explanation A process on the given FRU went down

Recommended Action Check the logs on the FRU for exact cause. If cause is not known please contact TAC

%CMCC_CBR-4-PROC_RESTART : Process [chars] restarted. Please undo and redo any config changes made during process restart

Explanation A process on the given FRU was restarted

Recommended Action Check the logs on the FRU for exact cause. If cause is not known please contact TAC

CMFP

%CMFP-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.

Explanation Hardware in the specified location could not be identified as a genuine Cisco product

CM_REDUC_MODE

%CM_REDUC_MODE-4-BM_ATTR_NOT_MAINTAIN : Attribute masks are not maintained when entering battery mode. CM MAC addr <[enet]>

Explanation Attribute masks are not maintained when entering battery mode

Recommended Action No action is required.

%CM_REDUC_MODE-4-BM_NO_AVAILABLE_DBG : Entering battery mode failed since no available RBG. CM MAC addr <[enet]>

Explanation Entering battery mode failed since no available RBG

Recommended Action Please inspect the configuration file and configured available RBG

%CM_REDUC_MODE-4-BM_OPERATION_EXCEED_MAX_COUNT : Enter into/exit BM mode failed for CM MAC addr <[enet]>

Explanation There maybe resource limitation which induce BM operation failure.

Recommended Action No action is required.

%CM_REDUC_MODE-4-BM_ORG_RCC_INAVAILABLE : Exiting battery mode failed since original rcc unavailable. CM MAC addr <[enet]>

Explanation Exiting battery mode failed since original rcc unavailable

Recommended Action No action is required.

%CM_REDUC_MODE-4-DBC_REJECT_CAUSE_CM_OFFLINE : CM [enet] forcely offline, because the operation failed as DBC rejected the invalid request, DBC client [dec]

Explanation DBC failed to change CM BG, because the operation was rejected as one invalid request. That cause the CM was not permitted to register again to the original BG. Mark CM offline to avoid CM stuck in reduce mode

Recommended Action No action is required.

%CM_REDUC_MODE-4-EM_ATTR_NOT_MAINTAIN : Attribute masks are not maintained when entering EM mode. CM MAC addr <[enet]>

Explanation Attribute masks are not maintained when entering EM mode

Recommended Action No action is required.

%CM_REDUC_MODE-4-EM_INVALID_EM_REQ : Receive an invalid EM request message from CM MAC addr <[enet]>, request power mode [dec].

Explanation Receive invalid requested power mode from CM

Recommended Action No action is required.

%CM_REDUC_MODE-4-EM_NO_AVAILABLE_DBG : Entering EM mode failed since no available RBG. CM MAC addr <[enet]>

Explanation Entering EM mode failed since no available RBG

Recommended Action Please inspect the configuration file

CMRP

%CMRP-2-ACT2_UDI_DATA_INVALID : The act2 udi secure area format mismatch with unsecure area

Explanation This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.

Recommended Action Replace the current product with a Cisco authorised product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information.

%CMRP-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.

Explanation Hardware in the specified location could not be identified as a genuine Cisco product

%CMRP-3-POWERBUDGET : not enough power budget left for : [chars]:[dec]

Explanation The system do not have enough power budget for the new card.

Recommended Action the message will be displayed when not enough power budget left for the new card inserted.

%CMRP-5-PEM_OUTPUT_DETECT : Output of PEM [dec] is [dec] V

Explanation Value of Output of PEM.

Recommended Action If PEM Output is 0, check Power Cable.

CMRP_PFU

%CMRP_PFU-1-PFU_FAN_FAILED : System detected fan tray removal or fan failure, reinsert or service the faulty fan tray to avoid system shutdown due to high temperature.

Explanation Fan tray has been removed or one of the fan failed and the router will shutdown when the temp reaches Critical temperature to protect itself from overheating.

Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.

%CMRP_PFU-3-DCPOWERREDUNDANCY : dc input [chars] failed for pem: [dec]

Explanation The DC input failed for pem module.

Recommended Action the message will be displayed when DC input failed.

%CMRP_PFU-3-FANASSY_REMOVED : Fan Assembly is removed. Please insert to avoid system from heating.

Explanation Fan Assembly has been removed from the system. It needs to be inserted back to prevent system from heating. If the system over heats, parts of the system will not function normally and system may shut itself down.

Recommended Action Insert the fan assembly in the system to prevent system from over heating.

%CMRP_PFU-3-PEM_STATUS : WARNING: The power supply module on slot [dec] hits [chars],

Explanation The power supply module are not functioning properly.

Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMRP_PFU-3-PEM_VOLTAGENOTSUPPORTED : WARNING: Input voltage of power supply module on PS[dec] is not supported. Please use the supported range of either [dec]-[dec] volts for [dec]W or [dec]-[dec] volts for [dec]W

Explanation The input voltage of the power supply module is out of range

%CMRP_PFU-3-PFU_FAN_DEAD : WARNING: Fan [dec] in the [chars] in slot [dec] has failed.

Explanation A fan is not functioning properly.

%CMRP_PFU-3-PFU_FAN_ERR : WARNING: Fan [dec] in slot [dec] has the error: [chars], Please replace it with a new fan.

Explanation A fan is not functioning properly.

%CMRP_PFU-3-PFU_FANS_DEAD : The fans in the [chars] in slot [dec] have all failed.

Explanation The system is in danger of overheating because none of the fans in one of the PEMs are working properly.

%CMRP_PFU-3-PFU_FANS_DEAD_SHUTDOWN : Shutting down system now because the fans in slot [dec] have all failed.

Explanation When the fans fail then system does not have sufficient cooling capacity. To prevent damage, the system will automatically shut down.

%CMRP_PFU-3-PFU_IDPROM_CORRUPT : The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component

Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.

%CMRP_PFU-3-PFU_IDPROM_READ_ERR : Could not read the PEM/FM idprom in slot P[dec]. The system will run without environmental monitoring for this component

Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.

%CMRP_PFU-3-PFU_SHUTDOWN : Shutting down system now because the PEM in slot [dec] was removed or not seated correctly.

Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.

%CMRP_PFU-3-PFU_SLOT_VACANT : The platform does not detect a power supply in slot [dec]

Explanation There is no power supply in one of the power supply slots.

Recommended Action Insert a power supply into the empty slot.

%CMRP_PFU-3-PWR_MGMT_ALARM : WARNING: System does not have sufficient input power for minimum reliable operation requiring [dec] watts. The system needs [dec] watts of additional power.

Explanation System power does not meet minimum requirements. Insert additional power supplies or provide current power supplies with a greater input voltage source if applicable.

%CMRP_PFU-3-PWR_MGMT_LC_SHUTDOWN : WARNING: Linecard in slot [dec] with priority [dec] and a power requirement of [dec] watts has shutdown.

Explanation A LC was shutdown due to a power loss.

%CMRP_PFU-3-PWR_MGMT_SINGLE_SUP_ERROR : ERROR: Remote supervisor has been detected in slot [dec]. System is configured to SINGLE-SUP power mode. Remove remote supervisor IMMEDIATELY.

Explanation User inserted a second supervisor in a single-sup power mode.

%CMRP_PFU-3-PWR_PROTECTION_ACTION : Shutdown the card [chars] due to insufficient power budget.

Explanation The total power is not enough, shutdown FRUs for power protection.

%CMRP_PFU-3-PWR_PROTECTION_MODE : WARNING: Detected low input voltage ([dec]V) on the power supply in slot P[dec], the power budget may not be enough, some cards may be shutdown due to the power budget reduction. Please check the power input.

Explanation Input voltage of power supply is too low.

%CMRP_PFU-3-PWR_REDUN_ALARM_STATE : WARNING: An active power supply has failed and the system has entered alarm state. The system is operating without power redundancy and has [dec] watts of power remaining

Explanation An active power supplied failed while in redundant power mode.

%CMRP_PFU-3-SHUTDOWN_FAILURE : The system attempted to shut itself down, but failed because [chars]

Explanation The system reached a condition where it should be shut down, but the shutdown call failed. The system should be manually rebooted.

%CMRP_PFU-3-TEMP_FRU_SHUTDOWN : [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes.

Explanation The FRU is overheating and will be shut down in order to protect the components.

%CMRP_PFU-3-TEMP_SYSTEM_SHUTDOWN : [chars] temperature sensor is in a shutdown system state. System shutdown will occur in [dec] minutes.

Explanation The system is overheating and will be shut down in order to protect the components.

%CMRP_PFU-4-PFU_FAN_INSUFFICIENT : WARNING: Insufficient number of fan modules installed. There are only [dec] fan modules, expecting [dec]

Explanation Insufficient number of fan modules installed, should insert new fans as soon as possible to avoid system from over heating.

%CMRP_PFU-4-PFU_FAN_WARN : WARNING: Fan [dec] in slot [dec] has the error: [chars].

Explanation A fan is not functioning properly.

%CMRP_PFU-4-PWR_MGMT_CAPACITY_MIXED : System contains power supplies of mixed power capacity. Redundancy operating mode Full protected is not supported with this configuration. System will run in Normal protected state.

Explanation HW does not support Full protected mode with mixed capacity power supplies. This is due to current sharing specifically

%CMRP_PFU-4-PWR_MGMT_WARN : WARNING: Insufficient number of power supplies ([dec]) are installed for power redundancy mode [chars]. The system needs [dec] watts additional power.

Explanation Insufficient number of power supplies are installed. Should insert new power supplies as soon as possible

%CMRP_PFU-5-DCPOWERINPUT : dc input [chars] recovered for pem: [dec]

Explanation The DC input recovered for pem module.

Recommended Action the message will be displayed when DC input recovered.

%CMRP_PFU-6-FANASSY_INSERTED : Fan Assembly is inserted.

Explanation Fan Assembly that was previously removed has been inserted in the system. Preventing the system from over heating is important. So fan assembly should not be removed for extended period of time during normal operation.

Recommended Action No further action is necessary.

%CMRP_PFU-6-PEM_INSERTED : PEM in slot [dec] not operational.

Explanation A PEM seems to be inserted without the power cable connected. This message is a notice that the power supply is not operational, will not provide power to the system, and may not be completely detected by the software until the power cable is connected and the PEM is supplied with the power.

Recommended Action Insert the power supply cable in the PEM and provide power.

%CMRP_PFU-6-PFU_BEACON_LED_ON_OFF : [chars] beacon LED for PFU[dec] is TURNED [chars].

Explanation Power Supply or Fan-tray, Beacon LED turned ON/OFF. This is a notification message only.No action is required.

Recommended Action This is a notification message only. No action is required.

%CMRP_PFU-6-PFU_FAN_RECOVERED : Fan in slot [dec] has been recovered from error conditions, Now it's working normally.

Explanation Fans are just recovered from an error condition,

%CMRP_PFU-6-PFU_FAN_RECOVERED_I2C : Successfully restored I2C communication to PSoC [dec] on fan module in slot [dec].

Explanation Fans are just recovered from an I2C communcation.

%CMRP_PFU-6-PFU_INSERTED : [chars] inserted. System shutdown aborted.

Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.This message serves as notice that the module has been replaced within the required time

%CMRP_PFU-6-PWR_MGMT_LC_RECOVERED : Linecard in slot [dec] with priority [dec] has been recovered from shutdown

Explanation A LC was recovered from a shutdown

%CMRP_PFU-6-PWR_MGMT_OK : Sufficient number of power supplies ([dec]) are installed for power redundancy mode [chars] (excess power [dec] watts).

Explanation Sufficient number of power supplies are installed.

%CMRP_PFU-6-PWR_MGMT_SINGLE_SUP_NOTICE : NOTICE([dec] of [dec]): System is now running in SINGLE-SUP power budget mode. Insertion of the remote supervisor is not supported in this power mode. System may shutdown if second supervisor is inserted.

Explanation User needs to be notified that single-sup mode is enabled

%CMRP_PFU-6-PWR_PROTECTION_RECOVERED : The power supply in slot P[dec] has been recovered from the power protection mode.

Explanation Power supply input are just recovered from an error condition,

%CMRP_PFU-6-PWR_REDUN_RECOVERED : System has recovered from the alarm state and has [dec] watts of power remaining

Explanation User has recovered the system from the alarm state triggered by a power failure

%CMRP_PFU-6-PWR_UP_FRU : Power up the card [chars] due to power budget change.

Explanation The total power become enough, power FRUs.

CMTS

%CMTS-3-CABLE_IPC_SEND_FAILURE : cable nonblocked ipc send failed, msg_type[[dec]], dst_slot[[dec]]

Explanation Cable send nonblocked ipc failed

Recommended Action No action is required.

%CMTS-3-DYN_SRV_IPC_SEND_FAILURE : [chars]_Tx: nonblocked send failed, dst_slot [dec]

Explanation Dynamic service failed to send nonblock IPC message

Recommended Action No action is required.

%CMTS-3-INVALID_BW : Invalid bandwidth configuration: cir_pct [dec], cir_sum [dec], eir_sum [dec]

Explanation Bandwidth configuration is invalid

%CMTS-3-LIST_CREATE : list create failed for list [chars]

Explanation The Cisco CMTS router is unable to create list due to insufficient system memory

Recommended Action Run the show memory command to verify available system memory. If memory is full, contact your Cisco technical support representative and provide the representative with the gathered information

%CMTS-3-LIST_ENQUEUE : list enqueue failed for list [chars]

Explanation Unable to enqueue an entry to list

%CMTS-3-LIST_INSERT : list insert failed for list [chars]

Explanation The Cisco CMTS router is unable to insert an entry into list due to insufficient system memory or insert an exist entry

Recommended Action Run the show memory command to verify available system memory. Then, run the show logging command to view all system-logged messages. If memory is full, contact your Cisco technical support representative and provide the representative with the gathered information

%CMTS-3-MCAST_SES_MISMATCH : Session Request Response Mismatch for transaction ID [dec] session ([chars],[chars]) CM [enet]

Explanation Response from the LC does not match the session requested for.

%CMTS-3-PKTCBL_GATE_RECON_START : Pktcbl reconciliation ([chars]) in progress: rejecting gate message [dec] with tid [hex]

Explanation Pktcbl Reconciliation started.

%CMTS-4-CM_GET_RCC_FAILED_AFTER_LCHA : failed to get rcc after LCSO Attempting to get rcc[[dec]] cm[[enet]]

Explanation Find invalid rcc while cm recover

%CMTS-4-DELETE_BONDING_MISMATCH : Error deleting upstream sid clusters, CM[[enet]] docsis_prim_sid[[dec]] matches csc_sid[[dec]]

Explanation The secondary sid should never match the primary.

%CMTS-4-DS_RESIL_FAILURE : [chars]: [chars] failed

Explanation DS Resiliency ipc message processing failure.

Recommended Action .

%CMTS-4-ENQUEUE_SID_DUPLICATE : Error enqueing sid element, Attempting to enqueue sid[[dec]] onto sid_reuse_queue that already exists

Explanation A duplicate sid should never exist in the free pool.

%CMTS-4-ENQUEUE_SID_INVALID : Error enqueing sid element, Attempting to enqueue invalid sid[[dec]] onto sid_reuse_queue

Explanation An invalid sid cannot be added to the free pool.

%CMTS-4-PKTCBL_DB_ERROR : Pktcbl failure op. ([int]), type: [[int]], gate id: [[int]], sub_id: [[chars]], rc: [[int]]

Explanation PacketCable database encounters an error Details embedded in message ..

Recommended Action No action is required.

%CMTS-4-PKTCBL_GATE_RECON_DONE : Reconciliation ([chars]) for slot [int] finished: total [int], success [int], multicast [int], failed [int], clc-only [int], sup-only [int], mismatch [int]

Explanation Reconciliation completed, print counters.

%CMTS-4-PKTCBL_GATE_RECON_MISMATCHED : Pktcbl reconciliation ([chars]) gate IE mismatched: gate id [int] type [chars] subs id [chars] slot [int]

Explanation Pktcbl reconciliation gate IE mismatched.

%CMTS-4-PKTCBL_GATE_RECON_TIMEOUT : Pktcbl reconciliation for slot [dec] timeout

Explanation Usually the reconciliation will end after all gates' info being synced between SUP and LC. If we didn't get the end normally, timer mechanism will take job, and clean up left gates' info

%CMTS-4-RECONCL_CM_FINISH_CLC : Reconciliation ([chars]) for slot [dec] finished: total [dec], success [dec], failed [dec], [chars]-only [dec], [chars]-only [dec], mismatch [dec], offline [dec], in-transaction-reconl [dec], in-transaction-recover [dec].

Explanation Reconciliation finished, print counters.

%CMTS-4-RECONCL_CM_FINISH_SUP : Reconciliation ([chars]) for slot [dec] finished: total [dec], success [dec], failed [dec], [chars]-only [dec], [chars]-only [dec], mismatch [dec], offline [dec].

Explanation Reconciliation finished, print counters.

%CMTS-4-RECONCL_CM_MISMATCH : Modem [enet] on Ca[dec]/0/[dec] mismatch during reconciliation, delete reason: [chars]

Explanation After the LC switchover, modem info will be synced to SUP to compare, if there is any info mismatch(eg: modem state, service flow info etc.), the modem will be deleted fully.

%CMTS-4-RECONCL_CM_TIMEOUT : Reconciliation for slot [dec] timeout

Explanation Usually the reconciliation will end after all modem info being synced between SUP and LC. If we didn't get the end normally, timer mechanism will take job, and clean up left modem info

%CMTS-4-RECONCL_RESET_D31_CM_FINISH : Reconciliation reset partial D31 CM for slot [dec] finished: D3.1 Online [dec], D3.1 DS partial [dec], D3.1 US partial [dec], D3.1 both partial [dec]. D3.0 DS partial [dec], D3.0 US partial [dec], D3.0 both partial [dec].

Explanation Reconciliation reset partial D31 CM finished, print counters.

%CMTS-4-UPSTREAM_SID_MISMATCH : Error populating upstream sid clusters, CM[[enet]] docsis_prim_sid[[dec]] matches csc_sid[[dec]]

Explanation The secondary sid should never match the primary.

%CMTS-6-PKTCBL_GATE_ERROR : Pktcbl failure op. ([int]), type: [[int]], gate id: [[int]], sub_id: [[chars]]

Explanation PacketCable encounters an error Details embedded in message ..

Recommended Action No action is required.

CMTS_INFRA

%CMTS_INFRA-3-DBG_BG_INTF_PER_CTRL_EXCD : WB interface resource on [dec]/[dec]/[dec] Exhausted

Explanation Unable to allocate additional WB Interface.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-FPM_ERR : [chars]: CM [enet], profile [dec]

Explanation A service flow for the modem has been mapped to a profile that is not configured for the ofdm channel.

Recommended Action Remove or correct the ofdm-flow-to-profile configuration for the modem.

%CMTS_INFRA-3-INVALID_OFDMA_MSLOT : Controller [dec]/[dec]/[dec] upstream [chars] is OP down; channel bw is too small or can't schedule IR/FR

Explanation OFDMA channel bandwidth is too small to support the minimum number of mini-slots or no minislot to schedule IR/FR

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NOENTROPY_PROC : Failed to create process to create entropy

Explanation Failure to create process to collect entropy.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NOHWENTROPY : Failed to receive HW entropy from RP; System fell back to SW entropy.

Explanation CLC doesn't receive HW entropy from RP for the last 10 minutes.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NORAND64 : Failed to read entropy from CPU

Explanation Failure to retrieve entropy for random number generator.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NORAND64_CPU : This is a pre-production SUP that's strictly for lab use; contact your sales rep to purchase a newer version if found in production.

Explanation CPU doesn't support RDRAND for crypto entropy.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NORANDNIST : Failed to generate random number

Explanation Failure to generate random number.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NORES : [chars] [dec] [dec]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NORES_BG_EXCD : [chars] [dec] [dec]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-NOTAMC : Failed to read entropy from ACT2 for [chars], err: [hex]

Explanation Failure to retrieve entropy for random number generator.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-PNM_INVALID_FREQ_SPAN_CFG : PNM: Capture tests cannot be started on port [dec]/[dec]/[dec] dev [dec] -Current capcfg freq: [dec]Hz, span: [dec]Hz. For this user configured center freq [dec]Hz, expected span value should not be more than [dec]Hz.

Explanation PNM capture configuration has invalid values, capture start rejected

Recommended Action Set the capture configuration center frequency and/or span to valid range as per suggested recommendations in msg to run captures.

%CMTS_INFRA-3-PNM_ZERO_FREQ_SPAN_CFG : PNM: Capture tests cannot be started on port [dec]/[dec]/[dec] dev [dec] -both capture config center frequency: [dec]Hz and span: [dec]Hz should be non zero or no meaningful data can be captured by CLC.

Explanation PNM Capture center frequency and span cannot be zero to run captures

Recommended Action Set non zero valid values for capture configuration center frequency and span paramters to run captures.

%CMTS_INFRA-3-REALLOC_VALID_FLOW : Attempt to realloc valid flow: [dec], [enet] md([dec]) sid([dec]) sfid([dec]) dsid([dec]). req: [enet]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-3-RELOAD : Configuration changed for Gemini 1 ports on card in slot [dec]. Please reload the card for the changes to take effect, and save the configuration.

Explanation After booting card with Gemini version 1, and removing configuration for Gemini version 2, the card needs to be reloaded for the changes to take effect. The configuration should be saved to avoid the issue on next reboot.

Recommended Action Reload the card and save the configuration.

%CMTS_INFRA-5-DMP_INVAL_IDX : Invalid Index: [dec] >= [dec]

Explanation An internal software error occurred and an Invalid Index value was used. Such errors typically happen due to timing issues and can be ignored if only seen infrequently. Report the error to Tech Support if seen repeatedly.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA-6-CTRLR_CHAN_CONFIG_CONTINUOUS_CHANGE : [chars] channel [dec]/0/[dec]:[dec] configuration is being continuously changed or it's admin state is being continuously toggled causing the system to enter an indeterminate state, recommend pacing controller/channel config changes.

Explanation Controller/channel config is being continuously changed or it's admin state is being toggled, this can put the system in an indeterminate state causing the modems to fall offline online or not come online.

Recommended Action Pace controller/channel configuration changes giving the system enough time to react to these events, recommeded wait time is 30 seconds between config operations on controllers/channels, use the recommendation to toggle channel admin state if modems don't come online or are partially online.

%CMTS_INFRA-6-CTRLR_PORT_ADMIN_STATE_LOCKED : User attempted to perform a no shut on Integrated-Cable [dec]/0/[dec] [dec] seconds after a shut event. This does not allow resources sufficient time to clean up. Calculated wait time was [dec] seconds between shut/no shut config operations on this controller.

Explanation Controller is attempting to be no shut too soon after a shut event. This oepration was blocked to prevent resources from being reused before they have been cleaned up.

Recommended Action None

%CMTS_INFRA-6-DELETE_HW_FLOW_MAC_MISMATCH : [chars] [int] [enet]:[enet]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

CMTS_INFRA_LCHA

%CMTS_INFRA_LCHA-3-DMP_MCAST_STATUS_TBL_NULL : Error:mcast_flow_status_tbl is NULL!

Explanation mcast_flow_status_tbl not initialized

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA_LCHA-3-SYNC_CONFIG_LIST_CREATION_FAILURE : DOCSIS SYNC configuration list creation failure, current slot [dec]

Explanation Failed to create the list of LCHA DOCSIS SYNC configuration

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA_LCHA-3-SYNC_CONFIG_LIST_INVALID : DOCSIS SYNC configuration list is invalid, current slot [dec], virtual slot [dec]

Explanation The list of LCHA DOCSIS SYNC configuration is invalid

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA_LCHA-4-RECONCIL_CM_CDM_MISMATCH : LCHA CDMAN to LC CM Reconciliation: Mac: [enet], Reason: [chars]

Explanation Mis-match between CDMAN and LC CM data

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA_LCHA-4-RECONCIL_DMP_MISMATCH : LCHA CDMAN to LC DMP Reconciliation: HW-Flow: [dec], Reason: [chars]

Explanation Mis-match between CDMAN and LC DMP data

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_INFRA_LCHA-4-RECONCIL_UMP_MISMATCH : LCHA CDMAN to LC UMP Reconciliation: Service-Flow: [dec], Reason: [chars]

Explanation Mis-match between CDMAN and LC UMP data

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

CSMPI

%CSMPI-3-ADDR_MISMATCH : Region address error: start @ [IPV6 address], end @ [IPV6 address], part addr @ [IPV6 address]

Explanation CSMPI encountered a bnad buffer address, possible corruption.

%CSMPI-3-BAD_INDEX : bad particle index [int], max [int], addr [IPV6 address]

Explanation CSMPI encountered a bnad buffer address, possible corruption.

%CSMPI-3-IF_INIT_FAILED : CSMPI interface initialization failed.

Explanation Essential CSMPI initialization has failed.

%CSMPI-3-PLATFORM_INIT_FAILED : CSMPI platform initialization failed.

Explanation Essential CSMPI initialization has failed.

D

DBMS

%DBMS-2-INITIALIZATION_FAILED : DBLIB initialization failed for [chars]

Explanation Initialization of the database library failed.

%DBMS-2-INITIALIZATION_FAILED (DUPLICATE) : DBLIB initialization failed for [chars]

Explanation Initialization of the database library failed.

%DBMS-3-IPC_ERROR : DBLIB ipc failure : [chars]

Explanation An internal inter-process communication error has occurred.

Recommended Action The ipc failure is reported by the operating system. Check the system resources and state to determine the source of the ipc failure. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%DBMS-3-IPC_ERROR (DUPLICATE) : DBLIB ipc failure : [chars]

Explanation An internal inter-process communication error has occurred.

%DBMS-3-MALLOC_FAILED : DBLIB malloc failed for [chars] size [int]

Explanation An internal memory allocation has failed.

Recommended Action Determine the cause of low system memory. Start by examining the system for memory leaks using the command 'show memory debug leaks'. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%DBMS-3-MALLOC_FAILED (DUPLICATE) : DBLIB malloc failed for [chars] size [int]

Explanation An internal memory allocation has failed.

%DBMS-3-TDL_ERROR : DBLIB TDL error : [chars]

Explanation A TDL messaging error has been detected.

Recommended Action Verify the route processors and cable linecard software versions are compatible. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%DBMS-3-TDL_ERROR (DUPLICATE) : DBLIB TDL error : [chars]

Explanation A TDL messaging error has been detected.

%DBMS-5-CONNECTION_DROP : DBLIB RIPC connection from [chars] to [chars] dropped

Explanation An internal socket connection has been dropped.

Recommended Action Determine the cause of the connection drop. Examine the system logs for peer cards or processes that may have failed. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%DBMS-5-CONNECTION_DROP (DUPLICATE) : DBLIB connection from [chars] to [chars] dropped

Explanation An internal socket connection has been dropped.

DSG

%DSG-3-DSG_DA_TO_DSID_DUPLICATED : DA [enet] to DSID table duplicated when operation [chars] DSID ([hex]) on interface ([chars]/[dec]).

Explanation DSG DA_TO_DSID table in LC should be unique for DA on a interface.

Recommended Action Issue the show tech-support command to gather data that may help identify the nature of the error. Then reconfigure DSG in the mac domain to refresh all DSG configurations in the interface.

%DSG-3-DSG_DCD_UPDATE_FAILURE : Faild to DCD message on [chars]

Explanation DSG DCD update failure

Recommended Action Check if DSG traffic is blocked on the influenced mac domain. If so, contact your Cisco technical support representative for help.

%DSG-3-DSG_DEL_DSID_FAILURE : dsg delete dsid failure [[chars]: [chars], [chars], [enet]]

Explanation dsg delete dsid failure

Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.

%DSG-3-DSG_DIFFERENT_DSG_DSID : different dsid [dec] assign to dsg da2dsid entry [dec]

Explanation DSG DSID Allocate Err

Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.

%DSG-3-DSG_ZERO_DSG_DSID : zero dsid found in dsg da2dsid entry for [[chars], [chars], [enet]]

Explanation Zero DSG DSID Found

Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.

%DSG-5-CFR_CONFLICT : classifier <[chars]> is put into conflict state because of errors

Explanation classifier is already applied, but we cannot update the classifier with changed destination IP address or source IP address because of errors. So we put the classifier into conflict state.

Recommended Action No action is required.

%DSG-5-CFR_NOT_APPLIED : classifier <[chars]> cannot be applied because of errors

Explanation classifier cannot be applied because of errors.

Recommended Action No action is required.

%DSG-5-CFRRMTUNNEL : cfr [dec] becomes unresolved, it will be removed from the tunnel it belongs to

Explanation cfr becomes unresolved, it will be removed from the tunnel it belongs to

Recommended Action No action is required.

%DSG-5-DSG_INFO_DB_LOOKUP_FAILURE : Faild to find the entry from the DSG Info DB for ([chars], [chars], [chars])

Explanation DSG Info DB lookup failure

Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.

%DSG-5-IDENTICAL_CFR : cfr [dec] and [dec] are identical

Explanation two cfrs are identical

Recommended Action No action is required.

%DSG-5-ILLEGAL_MCASTADDR : IP address <[IP_address]> is not a multicast address or is a reserved multicast address

Explanation IP address is not an multicast address or is a reserved multicast address

Recommended Action No action is required.

%DSG-5-ILLEGAL_SOURCEADDR : IP address <[IP_address]> is an illegal source address

Explanation IP address is an illegal source address

Recommended Action No action is required.

%DSG-5-MAC_ADDR : cfr [dec] and cfr [dec] have the same destination IP address [IP_address], but different MAC addresses [enet] and [enet]

Explanation two cfrs have the same destination IP address but different MAC addresses

Recommended Action No action is required.

%DSG-5-NAME_CHANGED : hostname <[chars]> is changed from <[IP_address]> to <[IP_address]>

Explanation IP address of a hostname is changed.

Recommended Action No action is required.

%DSG-5-NAME_UNRESOLVED : hostname <[chars]> cannot be resolved

Explanation DNS query for a hostname is not successful.

Recommended Action No action is required.

%DSG-5-SEMAPHORE_ERROR : failed to obtain the DSG semaphore

Explanation failed to get the semaphore

Recommended Action No action is required.

%DSG-5-SOURCE_LEN : cfr [dec]: source IP address [IP_address] and source prefix length [dec] don't match

Explanation source IP address and source prefix length of the cfr don't match

Recommended Action No action is required.

%DSG-5-SSM_SOURCE_PREFIX : destination IP address is <[IP_address]> in SSM range, source IP address prefix length must be [dec]

Explanation dest-ip is in SSM range, src-ip prefix length should match

Recommended Action No action is required.

%DSG-5-SSM_SOURCE_ZERO : destination IP address is <[IP_address]> in SSM range, source IP address cannot be zero

Explanation dest-ip is in SSM range, src-ip cannot be zero

Recommended Action No action is required.

%DSG-5-STATICJOINERR : cfr [dec] cannot be enabled, because there already has been a non-DSG static join for (S, [IP_address]) or (*, [IP_address]) in interface [chars]

Explanation cfr cannot be enabled because there already exists a non-DSG static join for the multicast group

Recommended Action No action is required.

%DSG-6-CFR_APPLIED : classifier <[chars]> is applied successfully

Explanation classifier is applied successfully.

Recommended Action No action is required.

%DSG-6-CFR_UPDATED : classifier <[chars]> is updated

Explanation classifier is updated

Recommended Action No action is required.

%DSG-6-LIST_ERR : [chars] [dec]

Explanation Infomational only

Recommended Action No action is required.

%DSG-6-NAME_RESOLVED : hostname <[chars]> is resolved as <[IP_address]>

Explanation DNS query for a hostname is successful.

Recommended Action No action is required.

%DSG-6-NO_TG : tg <[dec]> removal will remove all tg conf on bundle and mac-domain.

Explanation remove global tg is successful.

Recommended Action No action is required.

G

GCP

%GCP-3-THROTTLE : [chars] message queue for GCP session([dec]) of RPD([chars]) hits the HIGH WATERMARK([dec])

Explanation Message queue is throttled

Recommended Action check the GCP response message

I

INFRA_STATS

%INFRA_STATS-3-OUT_OF_RANGE : [chars] [dec] out of max size [dec] STATS work improperly

Explanation Data invalid from DMA

%INFRA_STATS-3-OUT_OF_SHMEM : out of max size [dec], start [IPV6 address], curloc [IPV6 address], type [dec], len [dec], next %lld

Explanation Data invalid from NONDMA

%INFRA_STATS-4-PROCESS_OVERTIME : NON_DMA has been processing for [dec]ms, check if CPU high

Explanation Process NONDMA Stats overtime, it is probably related to CPU high utilization. It is normal to see a small amount of it right after LCHA with scale modems due to low priority of this process and high CPU

IOSXE_VMAN

%IOSXE_VMAN-3-MSGDISPATCH : Unable to dispatch received TDL message from Virt-manager

Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-manager.

%IOSXE_VMAN-3-MSGINITFAIL : Failed to initialize required Virt-manager resource: [chars]

Explanation During the initialization of the resources required by Virt-manager, a failure occurred. This has prevented virtual services from being activated.

%IOSXE_VMAN-3-RSPMSGHDLR : Failed to deliver response message: [chars]

Explanation An unexpected condition has occurred while IOS was trying to deliver a response message to a virtual service received from Virt-manager.

L

LCHA

%LCHA-3-ASYNC_RSP_DROP : lcha async response event ignored from peer [dec]: invalid tag [dec]

Explanation LCHA client async response is not found in LCHA manager's pend event list, ignore this response.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-3-CFR_LIST : Remove an element before destroy [chars]: cfrid=[int], direction=[int], state=[dec], ip_sadd=[IP_address], ip_daddr=[IP_address], dest_macaddr=[enet], src_macaddr=[enet], ip_prot=[int], eport=[int]

Explanation Remove an element from interdb cfr_list before destroy the list.

Recommended Action Reset the system

%LCHA-3-DISTPEER_CREATION : lcha distpeer [dec] creation failed: [chars]

Explanation LCHA distpeer domain creation failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log, and check the core files.

%LCHA-3-DOMAIN_CREATION : lcha lcpeer domain [dec] creation failed: [chars]

Explanation LCHA lcpeer domain creation failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-3-EVENT_FAIL : LCHA event failed: [chars]

Explanation LCHA event failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-3-MSG_DISPATCH_ERR : lcha Message dispatch failed ([chars]): [hex]

Explanation LCHA message dispatch failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-3-MSG_RX_ERR : lcha mgr Rx of [chars] message failed reason [chars]

Explanation LCHA Manager failed to process the received message.

Recommended Action Check platform and process memory status. Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-3-MSG_RX_INPROG : lcha mgr Rx of [chars] message is in progress reason [chars]

Explanation LCHA Manager Rx of message is in progress.

%LCHA-3-MSG_TX_ERR : lcha mgr Tx of [chars] Message failed reason [chars]

Explanation LCHA Manager Tx of message failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

%LCHA-3-PEND_EV_CREATION : lcha pend event [dec] creation failed: [chars]

Explanation LCHA pend event creation failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman btrace log.

%LCHA-4-DYN_SRV : CM [enet], [chars] transcation id [dec] is not end before lc switch

Explanation Dynamic service not finished

Recommended Action No action is required.

%LCHA-4-RF_RESIL_IDX_OUT_OF_RANGE : CM [enet], RF channel id [dec] is out of range [dec]

Explanation RF channel index out of range

Recommended Action No action is required.

LCHA_CLIENT

%LCHA_CLIENT-3-CLIENT_CREATION : lcha client [dec]/[dec] ([chars]) creation failed: [chars]

Explanation LCHA client creation failed.

Recommended Action Check platform and process memory status. Check core files and crashinfo files.

%LCHA_CLIENT-3-CLIENT_DESTROY : lcha client [dec]/[dec] ([chars]) remove failed: [chars]

Explanation LCHA client remove failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

%LCHA_CLIENT-3-DOMAIN_CREATION : lcha domain [dec] creation failed: [chars]

Explanation LCHA domain creation failed.

Recommended Action Check platform and process memory status. Check core files and crashinfo files.

%LCHA_CLIENT-3-EXTEND_TIMER : lcha client [dec]/[dec] event [dec] timer extension failed: [chars]

Explanation LCHA client timer extension failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

%LCHA_CLIENT-3-MSG_DISPATCH_ERR : lcha client connection with [chars] message dispatch failed: [chars]

Explanation LCHA client message dispatch failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

%LCHA_CLIENT-3-MSG_HANDLER_ERR : lcha client [chars] message failed: [chars]

Explanation LCHA client message handling failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

%LCHA_CLIENT-3-MSG_TX_ERR : lcha client [chars] message not sent to [chars] reason [chars]

Explanation LCHA client message sending failed.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc, cdman, vidman btrace logs.

LCHA_INFRA

%LCHA_INFRA-3-UNEXPECTED : [chars]

Explanation An unexpected error has occured while performing a linecard HA action

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'.

%LCHA_INFRA-4-CUTOVER : Cutover request received from slot [int]

Explanation A cutover interrupt received from a failing linecard

Recommended Action Check core files and crashinfo files. Collect tech-support logs. Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'.

%LCHA_INFRA-4-FORCE_RESET : Reset slot [int] for reason: [chars]

Explanation The SUP forced a linecard to reload for the given reason.

Recommended Action Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'.

%LCHA_INFRA-5-SW_RESET : Soft-reset slot [int] [chars]

Explanation The SUP software reset linecard's processes without HW reset it.

Recommended Action No action is required.

%LCHA_INFRA-6-LCHA_INFO : [chars]

Explanation lcha information for better monitor chassis lcha relates status

Recommended Action No action is required.

LCPR_INFRA

%LCPR_INFRA-3-UNEXPECTED : [chars]

Explanation An unexpected error has occured while performing linecard IOSD or CDMAN process restart.

Recommended Action Check the IPC status of the platform. Collect the system log using CLI 'show logging', and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman, iosd-clc and cdman btrace logs.

%LCPR_INFRA-5-PROGRESSION : [chars]

Explanation LCPR generic progression information.

Recommended Action No action is required.

LED

%LED-2-DB_HA_ERROR : Database HA Error, Led id [int]

Explanation This is an internal software error.

Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%LED-2-GQILIB_INIT_FAILED : Failed to init GQI Lib, Led id [int]

Explanation This is an internal software error.

%LED-2-ID_MISMATCH : LED ID mismatch Led id -[int], Instance -[int]

Explanation This is an internal software error.

%LED-2-INIT_FAILED : Video LED process initialization failed id [int]

Explanation Initialization of the Video LED process failed. This is an internal software error.

%LED-2-INVALID_PSI_TYPE : Invalid PSI type, Led id [int]

Explanation This is an internal software error.

%LED-2-OUT_OF_CONTEXT_ERROR : LED Fell out of context loop, Led id [int]

Explanation This is an internal software error.

%LED-2-RESOURCE_ALLOCATION : Failed to Allocate memory, Led id [int]

Explanation This is an internal software error.

%LED-2-TBLLIB_INIT_FAILED : Failed to init Table-based Lib, Led id [int]

Explanation This is an internal software error.

%LED-2-VDMAN_IPC_INIT_FAILED : Vidman IPC initialization failed id [int]

Explanation Initialization of the Video LED process failed. This is an internal software error.

%LED-2-VIPC_INIT_FAILED : VIPC initialization failed id [int]

Explanation Initialization of the Video LED process failed. This is an internal software error.

%LED-2-VIPC_SEND_FAILURE : VIPC send failed, Led id [int]

Explanation This is an internal software error.

%LED-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars]

Explanation Setup of a console service failed. This is a possible cBR8 provisioning error.

Recommended Action Check the host manager launch parameters and correct as required.

%LED-3-LED_IPC_FLOW_CONTROL : Flow control turned [chars] for VIPC port [int], remote port [int], remote slot [int]

Explanation Flow control triggered on IPC link between LED and VDMAN.

Recommended Action Check the LED btrace logs

%LED-3-VIDEO_SOURCE_CHANGE_FAILED : Video Multicast Source Switch Failed. Error [dec], Source ([hex], [hex]), LED [dec]

Explanation Video Input Source failed to switch to the next sourcee.

Recommended Action Check the failed input source, and check for service impact

M

MEM_DIAGNOSE

%MEM_DIAGNOSE-3-OVERFLOW : Memory is overflowed -fence(hdr:[IPV6 address], foot:[IPV6 address]), dump memory: [chars]

Explanation Current memory is overflowed

Recommended Action check the memory structure and operation

R

RMFD

%RMFD-3-ERR_LOG : [chars]

Explanation RMFD Error has occured

Recommended Action No action is required.

%RMFD-4-WARN_LOG : [chars]

Explanation Relay warning message

Recommended Action No action is required.

%RMFD-5-NOTICE_LOG : [chars]

Explanation Relay notice message

Recommended Action No action is required.

RPHY_DB

%RPHY_DB-3-DB_HOG : Holding [chars] lock of <[chars]> for [int] ms

Explanation The IOSd process was holding the DB lock for too long, which may block other processes.

Recommended Action Collect the system log using CLI 'show logging'.

%RPHY_DB-3-NEST_LOCK : Nested lock: try to lock <[chars]> while holding lock <[chars]>

Explanation Nested lock detected

Recommended Action Collect the system log using CLI 'show logging'.

%RPHY_DB-3-UNEXPECTED : Error on lock <[chars]>: [chars]

Explanation Unexpected error when manipulating DB lock

Recommended Action Collect the system log using CLI 'show logging'.

%RPHY_DB-4-DB_STARVE : Waiting [chars] lock of <[chars]> for [int] ms

Explanation The IOSd process was waiting for the DB lock for too long

Recommended Action Collect the system log using CLI 'show logging'.

RPHYMAN

%RPHYMAN-0-RPD_EVENT_EMERGENCY : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-1-RPD_EVENT_ALERT : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-2-RPD_EVENT_CRITICAL : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-3-CCAP_CORE_EVENT_ERROR : [chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec]

Explanation CCAP CORE error event report

Recommended Action No action needed

%RPHYMAN-3-GCP_TX_FAIL : RPD [chars] send [chars] failed with error ([chars])

Explanation RPHYMAN send GCP msg failed

Recommended Action check GCP connection to see whether it's closed or throttled

%RPHYMAN-3-MISMATCH_XGE_IP : RPD [chars] configured xGE interface [dec].[dec].[dec].[dec] is mismatch with connectting xGE interface [dec].[dec].[dec].[dec]

Explanation RPD connect to a wrong DPIC xGE

Recommended Action check the rpd configuration and topo

%RPHYMAN-3-RPD_EVENT_ERROR : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-4-LCHA_STATUS_SUMMARY_WARNING : switchover from slot [dec] to slot [dec]: become active [dec], delete standby [dec], mis-protected [dec].

Explanation RPD status after linecard switchover

Recommended Action Please check the mis-protected rpds

%RPHYMAN-4-RPD_CAPA_PARAM_MISMATCH_WARNING : rpd_capa check, rpd_id: [chars], config_value [dec] rpdCapa_value [dec], event: [chars].

Explanation RPD DS/US configuration mismatch with RPD capability

Recommended Action Please pay attention to the RPD DS/US configuration

%RPHYMAN-4-RPD_EVENT_WARNING : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-4-RPD_US_BURST_VENDOR_EVENT_WARNING : us_share mode, rpd_id: [chars], Mapping to Upstream-Controller [dec]/0/[dec], event:[chars].

Explanation RPD us burst vendor is incosistent

Recommended Action Please do not combine RPDs with different vendors

%RPHYMAN-5-LCHA_STATUS_SUMMARY_NOTICE : switchover from slot [dec] to slot [dec]: become active [dec], delete standby [dec], mis-protected [dec].

Explanation RPD status after linecard switchover

Recommended Action No action needed

%RPHYMAN-5-MASTER_FSM_NOTICE : RPD [chars] Core [chars] [dec]/1/[dec] change MASTER STATE from [chars] to [chars]

Explanation The MASTER state machine has entered to a new state

Recommended Action No action needed

%RPHYMAN-5-MASTER_FSM_NOTICE_REASON : RPD [chars] Core [chars] [dec]/1/[dec] change MASTER STATE from [chars] to [chars] due to [chars]

Explanation The MASTER state machine has entered to a new state

Recommended Action No action needed

%RPHYMAN-5-RPD_EVENT_NOTICE : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-5-RPD_LCHA_EVENT_NOTICE : rpd_id: [chars], local_port_id: [dec], event: [chars].

Explanation RPD instance became active or was deleted due to LCHA

Recommended Action No action needed

%RPHYMAN-6-LCHA_INFO : rphyman_lcha_info: [chars]

Explanation this is information to better know the status of chassis

Recommended Action Please save the information if there's issue in your chassis

%RPHYMAN-6-RPD_EVENT_INFORMATIONAL : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

%RPHYMAN-7-RPD_EVENT_DEBUG : [chars]RPD-ID=[chars]EVENT-ID=[int]FirstTime=[chars]LastTime=[chars]Count=[dec][chars]

Explanation CCAP received a RPD event report

Recommended Action No action needed

RPHYMAN_DB

%RPHYMAN_DB-3-DB_HOG : Holding [chars] lock of <[chars]> for [int] ms

Explanation The rphyman process was holding the DB lock for too long, which may block other processes.

Recommended Action Collect the system log using CLI 'show logging'.

%RPHYMAN_DB-3-NEST_LOCK : Nested lock: try to lock <[chars]> while holding lock <[chars]>

Explanation Nested lock detected.

Recommended Action Collect the system log using CLI 'show logging'.

%RPHYMAN_DB-3-UNEXPECTED : Error on lock <[chars]>: [chars]

Explanation Unexpected error when manipulating DB lock.

Recommended Action Collect the system log using CLI 'show logging'.

%RPHYMAN_DB-4-DB_STARVE : Waiting [chars] lock of <[chars]> for [int] ms

Explanation Current process was waiting for the DB lock for too long

Recommended Action Collect the system log using CLI 'show logging'.

S

SMART_LIC

%SMART_LIC-3-OUT_OF_COMPLIANCE : [chars]

Explanation Smart License Agent enforcement mode changed to out of compliance

U

UBRCCE

%UBRCCE-0-CLI_CONFIG : CMTS([dec]/[dec]/[dec]), schrp_cli_cmd failed in [chars]

Explanation Most likely S/W failure

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

%UBRCCE-6-CM_INCONSISTENCY : CM state inconsistency [enet](msgp [enet]), sid [dec] ([dec]), mac state [dec], hwidb [chars]

Explanation Received INIT_CM for an online CM, Copy the message and report to your technical support representative

%UBRCCE-6-DSD_SRV_FLOW_ERROR : SFID found: SFID [dec], type [dec], MAC [enet]([enet]), prim_sid [dec]([dec])

Explanation The RP and LC have different service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative

%UBRCCE-6-DS_SFID_INCONSISTENCY : DS-SF found: SFID [dec], type [dec], MAC [enet]([enet]), prim_sid [dec]([dec])

Explanation The RP and LC have different downstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative

%UBRCCE-6-HA_CM_INCONSISTENCY : CM sync received [enet](msgp [enet]), sid [dec] ([dec]), mac state [dec], hwidb [chars]

Explanation Received sync message on secondary SUP for mismatched entry This problem should resolve by itself. If it persists, report to your technical support representative

%UBRCCE-6-RCC_WB_INCONSISTENCY : [chars] RCC-[dec] [chars] mismatch with DSBG-[dec] [chars]

Explanation Receive chanel set in RCC is mismatch with the Wideband.

%UBRCCE-6-STDBY_CM_INCONSISTENCY : CM sync received [enet](msgp [enet]), sid [dec] ([dec]), mac state [dec], hwidb [chars]

Explanation Received sync message on secondary SUP for mismatched entry This problem should resolve by itself. If it persists, report to your technical support representative

%UBRCCE-6-US_SFID_INCONSISTENCY : US-SF found: SFID [dec], type [dec], sid [dec]([dec]), MAC [enet]([enet]), prim_sid [dec]([dec])

Explanation The RP and LC have different upstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative

V

VCFG

%VCFG-2-INVALID_DB_HANDLE : VCFG invalid Database handle, Led id [int]

Explanation This is an internal software error

%VCFG-2-RESOURCE_ALLOCATION_ERROR : VCFG Failed to Allocate memory, Led id [int]

Explanation This is an internal software error

VD6

%VD6-2-CONNECT_FAILED_AFTER_SSO : [dec]:[chars] => Server connection failed after SSO, Reason:[chars]

Explanation Failed to connect to D6 server after Supervisor Switch over. This error most likely occured due to routing issue or server did not handle the second connection request

Recommended Action Verify ping works both ways. Check the arp entries. Try changing the mgmt-ip assigned to D6.

%VD6-2-INIT_FAILED : [dec]: => Failed to initialize D6, Reason = [chars]

Explanation Failed to initialize D6 discovery on the LED

Recommended Action Review the D6 configuration parameters and Memory availability. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VD6-3-CONNECTION_CLOSED_BY_LED : [dec]:[chars] => D6 terminated server connection, reason:[chars]

Explanation Server connection terminated. Look for the reason in the message. This error most likely occured due to configuration change, D6 server issue or network issue.

Recommended Action The reason shall indicate the root cause. The action shall be based on that.

%VD6-3-CONNECTION_CLOSED_BY_SERVER : [dec]:[chars] => Connection closed by D6 Server:[chars]

Explanation Connection closed at the Server side. The D6 Client will retry the connection. This error most likely occured due to configuration change, D6 server issue or network issue.

Recommended Action Check the D6 server connection and its status.

%VD6-3-ERROR_NOTIFICATION_FROM_SERVER : [dec]:[chars] => Received Error notification from Server when expecting [chars] message.

Explanation Received error notification from Server. Connection will be closed and re-tried. This error most likely occured due to D6 server issue or network issue.

Recommended Action Check the connection, show interface cmd for errors and the D6 server status.

%VD6-3-HOLD_TIME_EXPIRED : [dec]:[chars] => Hold time expired as no keepalive from D6 server:[chars]

Explanation No keepalive messages received from server for a duration that is 3 times that of the negotiated hold time. The connection will be closed and retried. This error most likely occured due to D6 server issue or network issue.

Recommended Action Check the connection and show interface cmd for errors.

%VD6-3-INVALID_MSG_FROM_SERVER : [dec]:[chars] => Invalid [chars] message received from server:[chars]

Explanation Received message is either incomplete or contains invalid data. The connection will be closed and retried. This error most likely occured due to D6 server issue or network isssue.

Recommended Action Check the connection and show interface cmd for errors. Verify QAM hostname matches in CEM.

%VD6-3-SEND_MESSAGE_FAILED : [dec]:[chars] => Failed to send [chars] message to server:[chars]

Explanation Failed to send D6 message to server. The Connection will be closed and retried. This error most likely occured due to config change or network issue.

Recommended Action Check the connection and show interface cmd for errors.

%VD6-4-UNKNOWN_MSG_FROM_SERVER : [dec]:[chars] => Unknown Message from D6 Server,Message Type = [dec]

Explanation Unknown message received from the D6 server. This error most likely occured due to D6 server issue or network issue.

Recommended Action Check the connection and show interface cmd for errors

VEMAN

%VEMAN-3-BIND_FAILED : Alarm [chars]: [chars]: [chars]

Explanation Unable to bind a socket to the EIS port. Failed to create a socket to listen for an EIS connection. Could not bind to the UDP port.

Recommended Action Set or ClearCheck the configuration of the EIS proxy.

%VEMAN-3-CEM_CONNECTION_LOST : Alarm [chars]: [chars]: [chars]-[chars]:[dec]

Explanation CEM connectivity Lost. An active CEM connection to CBR8 CEM Mangement IP was lost.

Recommended Action Set or ClearCheck QAM IP and hostname in CEM server GUI. Check connectivity between PME Management IP and CEM IP address. Verify QAM Management IP configuration in CEM. Verify QAM hostname matches in CEM

%VEMAN-3-CHANNEL_CLOSE_PEER : Alarm [chars]: [chars]: [chars]

Explanation The peer EIS has closed the communication channel. VEMAN has received a channel close message from the EIS

Recommended Action Set or ClearCheck the status of the external EIS.

%VEMAN-3-CHANNEL_ERROR : Alarm [chars]: [chars]: [chars]

Explanation Connection to ECMG has an error, so services cannot be scrambled. An external (DVB) ECMG or internal (PME or PK) ECMG error has occurred

Recommended Action Set or ClearFor external (DVB) ECMG, review the configuration parameters. For internal (PME or PK) ECMG, a software error has occurred. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VEMAN-3-CLEAR_EXTENSION : Alarm [chars]: [chars]: [chars]

Explanation Either service is not present, so there are no components to scramble, or there is a problem with ECM retrieval from ECMG or with CW retrieval. This is likely an input stream issue.

Recommended Action Set or ClearConfirm that the service is present on the input and ECMG is properly connected.

%VEMAN-3-CONNECTION_LOST : Alarm [chars]: [chars]: [chars]

Explanation Unable to connect to the peer EIS. Connection to the EIS has timed out or can not be established.

Recommended Action Set or ClearCheck the configuration and status of the external EIS.

%VEMAN-3-CP_EXTENSION_NO_COMP : Alarm [chars]: [chars]: [chars]

Explanation The Service or PIDs are not present, so there are no components to scramble. This error most likely occured due to an input service not arriving properly which is likely either a problem in the input path or in the session create parameters.

Recommended Action Set or ClearConfirm that the service is present on the input.

%VEMAN-3-CP_EXTENSION_NO_ECMS : Alarm [chars]: [chars]: [chars]

Explanation The ECMG has not returned the requested ECMs, so the components can not be scrambled. An external (DVB) ECMG or internal (PME or PK) ECMG error has occurred.

Recommended Action Set or ClearConfirm that the external (DVB) ECMG is connected and operating correctly, and that it is not overwhelmed with ECM requests. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VEMAN-3-ECMG_NO_CHANNEL_AVAILABLE : Alarm [chars]: [chars]: [chars]

Explanation Cannot connect to ECMG, so services cannot be scrambled. An external (DVB) ECMG or internal (PME or PK) ECMG error has occurred

Recommended Action Set or ClearFor external (DVB) ECMG, review the configuration parameters. For internal (PME and PK) ECMG, a software error has occurred. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VEMAN-3-ECMG_REMOVE : Alarm [chars]: [chars]: [chars]

Explanation Operator has removed and ECMG Proxy configuration with actively scrambled services. An external (DVB) ECMG or internal (PME or PK) ECMG error has occurred.

Recommended Action Set or ClearRe-add the ECMG Proxy configuration, so services can continue to be scrambled. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VEMAN-3-EIS_REMOVE : Alarm [chars]: [chars]: [chars]

Explanation An active EIS proxy has been removed. This error most likely occured due to a configuration change of the EIS Proxy.

Recommended Action Set or ClearAn EIS Proxy with an active channel to an EIS has been removed and is no longer connected to the EIS.

%VEMAN-3-FPGA_ALGO_MISMATCH : Alarm [chars]: [chars]: [chars]

Explanation Raider FPGA scrambling algorithm mismatch detected

Recommended Action Set or ClearConfirm that the FPGA scrambling algorihm loaded in the linecard is aligned with configuration.

%VEMAN-3-LED_REMOVE : Alarm [chars]: [chars]: [chars]

Explanation The active LED EIS has been removed. This error most likely occured due to a configuration change of the LED.

Recommended Action Set or ClearAn LED with active sessions has been removed and is no longer connected to VEMAN.

%VEMAN-3-PID_COULD_NOT_BE_ALLOCATED : Alarm [chars]: [chars]: [chars]

Explanation Encryption requested an ECM PID from the Video process and did not receive one

Recommended Action Set or ClearConfirm the service is present on input and does not exceed the maximum allowed input PIDs.

%VEMAN-3-PME_CWIDX_MISMATCH : Alarm [chars]: [chars]: [chars]

Explanation PME CWIndex mismatch detected because of Internal error.PME session may affected

Recommended Action Set or ClearRestart the veman process of linecard, if process restart in configured

VGQI

%VGQI-2-RESOURCE_ALLOCATION_ERROR : VGQI Failed to allocate memory for [chars]. LED ID [int]

Explanation LED process ran out of memory error. This is an internal software error

%VGQI-3-ANNOUNCE_EVENT_QUEUE_FULL : Announce event queue is full. All previously existing events in the queue for server [chars] on LED [dec] were deleted.

Explanation Previously existing events in the queue were deleted due to the queue being full.

%VGQI-3-BW_EXCEED_LIMIT : LED ID [int], Bitrate [int] for input source [chars] on slot [dec] exceeds the configured bitrate

Explanation Session bitrate exceeds the configured bitrate. This is a possible cBR8 provisioning error.

Recommended Action Review the source and configured session bitrate and compare.

%VGQI-3-SESSION_ID_MAPPING_ERROR : VGQI Failed to map the internal session ID [dec] to a GQI session ID, LED ID [int]

Explanation This is an internal software error

VIDEO

%VIDEO-3-RF_POSTCONFIG_TIMEOUT : missing one or more client's RF_POSTCONFIG

Explanation Missing RF_POSTCONFIG done from at least one client

Recommended Action Check if any client has crashed

%VIDEO-3-RF_STBY_BULK_SYNC_TIMEOUT : Video standby-bulk-sync timed out

Explanation Missing RF_BULK_SYNC done from at least one client

Recommended Action Check if any client is hang or crashed

VIDMAN

%VIDMAN-2-VIDEO_ILK_PKO_ERROR : Video output exceeds system capacity. All video output STOPPED

Explanation Software detects packet output (PKO) error, indicating one of two Interlaken (ILK) buses between line card CPU and Raider FPGA is overloaded.

Recommended Action Reduce number of video QAMs and reset line card

%VIDMAN-2-VIDEO_SEND_OUTPUT_ERROR : Video send API call failed

Explanation Video send API call failed

Recommended Action Contact Richard Lindquist

%VIDMAN-3-IPC_MALLOC_BUFFER_FAILED : [chars]: Run out of IPC buffer for [chars] message

Explanation Video software fails to allocate an IPC buffer. This is a software error due to insufficient IPC buffer.

%VIDMAN-3-IPC_SEND_FAILED : Failed to send IPC message to [chars]. '[chars]' rc=[chars]

Explanation Video software failed to send message to the peer. This is an internal software error.

%VIDMAN-3-LCRED_BAD_MODE_ROLE_TRANSITION : Invalid linecard redundancy role/mode transition from [chars]/[chars] to [chars]/[chars]

Explanation Bad LCHA mode-role transition is received. This is an internal software error.

%VIDMAN-3-LCRED_UNEXPECTED_GO_HOT : Unexpected linecard redundancy in [chars]/[chars]

Explanation Unexpected LCHA go-hot message received. This is an internal software error.

%VIDMAN-3-LCRED_UNEXPECTED_JOINED_GROUP : Invalid linecard redundancy configuration when the card is in [chars]/[chars]

Explanation Unexpected LC redundancy group join message received. This error most likely occured due to an invalid configuration.

Recommended Action Check the configuration and if the problem persists continue with the next step. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VIDMAN-3-LCRED_UNEXPECTED_LEFT_GROUP : Invalid linecard redundancy configuration when the card is in [chars]/[chars]

Explanation Video Manager redundancy configuration error. This error most likely occured due to an invalid configuration.

%VIDMAN-3-LOGGER_OPEN_FAILED : Failed to create video internal log file.

Explanation Video Manager logger initialization failed. This is an internal error.

Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/.If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VIDMAN-3-VDMAN_IPC_FLOW_CONTROL : Flow control turned [chars] for VIPC port [int], remote port [int], remote slot [int]

Explanation Flow control triggered on IPC link between VDMAN and LED.

Recommended Action Check the VDMAN btrace logs

%VIDMAN-3-VIDEO_BAD_BITRATE_ALLOC : [chars]: Out of range bitrate allocation for bitrate [dec]

Explanation Video session configuration with bad allocated bitrate received. This is a software error due to invalid configuration

Recommended Action Check the LED configuration on the RP and if the problem persists continue to the next step. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VIDMAN-3-VIDEO_BAD_CR_MODE : [chars]: Invalid Clock Recovery Mode [dec]

Explanation Video session configuration with bad clock recovery mode received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_DELAY : [chars]: Bad target delay value [dec]

Explanation Video session configuration with bad delay parameter received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_DST_UDP_PORT : [chars]: Invalid or out of range UDP port number [dec]

Explanation Video session configuration with bad destination UDP port received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_FILTERED_PID : [chars]: Invalid filtered PID [dec] for output session [dec], IOS session ID [dec]

Explanation Config message with bad filtered pid value is received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_FILTERED_PROG : [chars]: Invalid filtered program [dec] for output session [dec], IOS session ID [dec]

Explanation Config message with bad filtered program number is received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_INPUT_PORT : [chars]: Invalid input port [dec]

Explanation Video session configuration with bad input port number received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_INPUT_TYPE : [chars]: Invalid transport type [dec] for a input session

Explanation Video session configuration with bad input cast type received. This is a software error due to invalid configuration.

%VIDMAN-3-VIDEO_BAD_IN_SESSION_ID : [chars]: Invalid input session [dec], IOS session ID [dec]

Explanation Input session id is outside the valid range. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_IP_ADDR_LEN : [chars]: Invalid input IP address length [dec]

Explanation Video session configuration with bad IP address length received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_JITTER : [chars]: Invalid or out of range jitter value [dec]

Explanation Video session configuration with bad jitter value received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_OUT_SESSION_ID : [chars]: Invalid output session id [dec]. IOS session ID [dec]

Explanation Bad output session ID (out of range) received. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_PID_RANGE : [chars]: Invalid PID range [dec]-[dec]

Explanation Video session configuration with bad output PID range received. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_PRIMARY_ID : [chars]: Invalid linecard for config context id [dec]

Explanation Video command with bad primary ID received. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_PROG_NUM : [chars]: Out of range program number [dec]

Explanation Video session configuration with bad output program number received. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_PSIP_EAS_TYPE : [chars]: Invalid PSIP/EAS session type [dec]

Explanation Video session configuration with bad session type received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_BAD_QAM_ID : [chars]: Invalid physical QAM id [dec]

Explanation Bad QAM channel ID (out of range) received. This is an internal software error.

%VIDMAN-3-VIDEO_BAD_REMAPPED_PID : [chars]: Invalid remap PID [dec] for output session [dec], IOS session ID [dec]

Explanation Config message with bad remapped pid value is received. This is an internal software error.

%VIDMAN-3-VIDEO_CAROUSEL_ALLOC_FAILED : [chars]: Run out of carousel insert for id [dec].

Explanation Video software fails to allocate a carousel. This is an internal software error.

%VIDMAN-3-VIDEO_CAROUSEL_IN_USE : [chars]: Carousel [dec] already in use

Explanation The video carousel being created is already in use. This is an internal software error.

%VIDMAN-3-VIDEO_CAROUSEL_NOT_FOUND : [chars]: Carousel insert [dec] doesn't exist.

Explanation Video software fails to locate a carousel referenced in a command. This is an internal software error.

%VIDMAN-3-VIDEO_COMMAND_FAILED : Invalid video operation [chars] resource id [dec], rc [dec].

Explanation Video software fails to handle a video configure message. This is a possible cBR8 provisioning error.

Recommended Action Check the LED configuration on the RP to see if the operation is supported.

%VIDMAN-3-VIDEO_CONTEXT_INIT_FAILED : [chars]: Failed to initialize video context with id [dec]

Explanation Failed to initialize the video context. This is an internal software error.

%VIDMAN-3-VIDEO_CONTEXT_RESET_FAILED : Failed to remove all configuration for primary [dec] due to [chars]

Explanation Failed to reset a video context. This is an internal software error.

%VIDMAN-3-VIDEO_FEATURE_NOT_AVAIL : [chars]: Invalid configuration for output session [dec], IOS session ID [dec]

Explanation A config message request for a video feature not supported is received. This is a software error due to invalid configuration

%VIDMAN-3-VIDEO_FLOW_ALLOC_FAILED : [chars]: Run out number of video flow for output session [dec], physical QAM [dec]. IOS session ID [dec].

Explanation Video software fails to allocate an output video flow. This is an internal software error.

%VIDMAN-3-VIDEO_HIGH_LOAD : [chars]: video load too high: demux [dec], input [dec], output [dec]

Explanation Video load exceeds design limit

Recommended Action Check configuration. Make sure the loading is within design spec.

%VIDMAN-3-VIDEO_INCOMPLETE_MSG : Missing parameters in the request [chars].

Explanation A partial video config message is received. This is an internal software error.

%VIDMAN-3-VIDEO_IN_SESSION_ALLOC_FAILED : [chars]: Run out of buffer pool for input session [dec], IOS session ID [dec]

Explanation Failed to allocate input session. This is an internal software error.

%VIDMAN-3-VIDEO_IN_SESSION_INIT_FAILED : [chars]: Input session initialization failed, input session id [dec], rc = [chars], [chars]

Explanation Video input session initialization failed. This is a possible cBR8 provisioning error.

%VIDMAN-3-VIDEO_MISSING_PROG_NUM : [chars]: Missing program number on output session [dec], IOS session ID [dec].

Explanation A remap session with missing output program number. This is an internal software error.

%VIDMAN-3-VIDEO_OUT_PROG_ALLOC_FAILED : [chars]: Run out of output program buffer pool for program [dec]

Explanation Video software fails to allocate an output program. This is a software error due to insufficient buffer pool.

%VIDMAN-3-VIDEO_OUT_SESSION_INIT_FAILED : output session iniialization failed on operation [chars], output session id [dec], rc = [chars], IOS session ID [dec].

Explanation Video output session initialization failed. This is a possible cBR8 provisioning error.

%VIDMAN-3-VIDEO_OUT_SESSION_NOT_USED : [chars]: Output session [dec] doesn't exist. IOS session ID [dec]

Explanation Video output session being referenced is not configured. This is an internal software error.

%VIDMAN-3-VIDEO_PACKET_ALLOC_FAILED : [chars]: Run of buffer pool

Explanation Video Manager failed to packetize PSI section into MPEG packet. This is an internal software error.

%VIDMAN-3-VIDEO_PACKET_INSERT_ALLOC_FAILED : [chars]: Run of memory pool for carousel [dec]

Explanation Video software fails to allocate packet insert buffer. This is an internal software error due to insufficient resources.

%VIDMAN-3-VIDEO_PAT_BUILD_FAILED : Failure in regenerate PMT for QAM [dec]

Explanation Failed to build output PAT. This is an internal software error.

%VIDMAN-3-VIDEO_PMT_NOT_FOUND : [chars]: PMT doesn't exist in TP id [dec] input session [dec], [chars]

Explanation Video program not found on the PMT pid. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_PROG_CA_BLOCKED : [chars]: CA descriptor for program [dec], qam [dec]

Explanation A program to be encrypted is blocked because the input program contains CA descriptor. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration. Make sure programs to be edge-encrypted are not already encrypted.

%VIDMAN-3-VIDEO_PROG_NUM_IN_USE : [chars]: Program number [dec] failed to be used for output session [dec], due to it already used in the physical QAM [dec]. IOS session ID [dec].

Explanation Program number being configured for a new session is already in use. This is a possible cBR8 provisioning error.

Recommended Action Check cBR8 provisioning to see if the same output program number has been used more than once in the same qam channel.

%VIDMAN-3-VIDEO_PSI_BLOCKED : [chars]: PSI is being blocked for input session [dec]. error = [chars]. [chars]

Explanation Input program is blocked due to any error in PAT or PMT. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_PSI_SECTION_ALLOC_FAILED : [chars]: Run out of PSI section buffer pool for id [dec]

Explanation Video software fails to allocate a PSI section. This is a software error due to insufficient buffer pool.

%VIDMAN-3-VIDEO_SESSION_NOT_USED : [chars]: video session [dec] doesn't exist.

Explanation Video session being referenced is not configured. This is a possible cBR8 provisioning error.

%VIDMAN-3-VIDEO_TOO_MANY_CA_DESC : [chars]: Too many CA descriptors [dec] in PMT. Max CA descriptors allowed per program is [dec]

Explanation A program with more than 32 CA-descriptors is found in PMT. This is likely an input stream issue, or the input stream exceeds the limits the cBR8 software can handle.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_TOO_MANY_ES : [chars]: Too many ES per program in PMT. ES count = [dec], max ES per program = [dec]

Explanation Program with more than 31 ES pids is found in PMT. This is likely an input stream issue, or the input stream exceeds the limits the cBR8 software can handle.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_TOO_MANY_PROG_IN_PAT : [chars]: Number of programs has oversubscribed in PAT. Total program count = [dec]

Explanation PAT containing more than 64 programs is found. This is likely an input stream issue, or the input stream exceeds the limits the cBR8 software can handle.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_TOO_MANY_PROG_IN_QAM : Number of programs per MPTS has exceeded the limit in QAM [dec]

Explanation More than 64 programs in a QAM channel. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-3-VIDEO_UNEXPECTED_PROG_NUM : [chars]: Unexpected program number [dec] for a non remap output session [dec], IOS session ID [dec].

Explanation Passthru or Data piping session configuration does not require program number. This is a software error

%VIDMAN-3-VIDEO_UNKNOWN_MSG : [chars]: Failed to handle request message type [dec].

Explanation A video config message of unknown type is received. This is an internal software error.

%VIDMAN-3-VIPC_BUFFER_FULL : Unable to send IPC msg from line card [dec] to led [dec]. IPC buffer full.

Explanation Detect IPC buffer full. Application may send too many IPC messages, or vidman encounters too many errors.

Recommended Action Reduce messages such as reduce SNMP queries, or number of sessions.

%VIDMAN-4-VIDEO_BAD_ES_DESC : [chars]: Invalid ES in PMT.

Explanation Error found in parsing PMT ES-level descriptors. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_BAD_PROG_DESC : [chars]: Invalid program descriptor in PMT.

Explanation Error found in parsing PMT program-level descriptors. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_BAD_PSI_SECTION_NUM : Invalid PSI section number [dec] detected in input session [dec]. Last section number [dec]. [chars]

Explanation Bad section number found in PAT. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_BAD_TABLE_IN_PAT : Invalid PAT table id [dec] detected in input session [dec], [chars]

Explanation Table other than PAT is found on pid 0. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_INVALID_CDM_PAK : Received invalid cmd_pak with null bufer pointer (occurred [dec] times)

Explanation Video software received invalid cmd_pak with NULL buffer pointer

Recommended Action If the symptom persists for minutes, please reload the LC

%VIDMAN-4-VIDEO_PSI_CRC_ERROR : [chars]: CRC error for input session [dec], [chars]

Explanation PAT or PMT with CRC error is found. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_SESSION_EXISTS : Invalid video operation [chars] Session [dec] already exists, rc [dec].

Explanation Video software failed to process a create_session request due to the session ID already exists

Recommended Action Check if the session is running and the service is active.

%VIDMAN-4-VIDEO_TOO_MANY_NIT_IN_PAT : Invalid NIT PID detected in PAT

Explanation PAT containing more than one NIT entry is found. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_TOO_MANY_PMT_SECTIONS : [chars]: Too many PMT sections in input session [dec]. Last section number [dec]. [chars]

Explanation PMT with more than 1 section is found. This is likely an input stream issue.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_TOO_MANY_SECTION_IN_PAT : Too many PAT section in input session [dec]. Last section num [dec]. [chars]

Explanation PAT of more than 4 sections is found. This is likely an input stream issue, or the input stream exceeds the limits the cBR8 software can handle.

Recommended Action Inspect video input streams and/or source configuration.

%VIDMAN-4-VIDEO_UNKNOWN_PROG_NUM : [chars]: Unrecognized program number [dec] found in PMT section input session [dec], [chars]

Explanation A PMT with program number not included in PAT is found. This is likely an input stream issue. Customer is advised to capture and analyze the input stream if 10 or more such messages are seen in 10 hours

Recommended Action Inspect video input streams and/or source configuration.

VRSA

%VRSA-3-RSA_KEY_ERROR : Failed to retreive keypair [int]

Explanation Failed to retrieve keypair. This is an internal software error.

VSESS

%VSESS-2-RESOURCE_ALLOCATION_ERROR : VSESS Failed to Allocate memory, Led id [int]

Explanation This is an internal software error

%VSESS-3-INPUT_STREAM_FAILURE : Input Stream Failure for Source [chars], LED [dec], Slot: [dec]

Explanation Input stream failure has been detected. This is possibly due to input interface down or network issue

Recommended Action Check the input source, or initiate a SSO

%VSESS-3-PMT_MISSING_ERROR : PMT is missing for program [dec], session ID [dec], LED [dec], Slot [dec]

Explanation PMT is missing from input stream.

Recommended Action Check the input source for missing PMT, and check for service impact

%VSESS-3-PMT_MISSING_EVENT_INVALID_PROGRAM_NUM : PMT missing event from vidman, invalid program number [dec], session ID [dec], LED [dec], Slot [dec]

Explanation PMT missing is detected.

Recommended Action Check input stream for missing PMT

%VSESS-3-PROG_NUM_CONFLICT : Program number [int] is already used by session [int] on line card slot [int]. Session creation failed for session ID [int]

Explanation Linecard detected a program number conflict on session creation.

Recommended Action Check for service impact. Delete the old session and recreate the new session.

%VSESS-3-STREAM_ERROR : [dec] Slot: [dec] [chars]

Explanation Stream error set or clear has been detected. This is possible due to faulty stream or due to packet loss in Network.

Recommended Action Review the source and do the source switchover (in case of Multicast) if there is any video impact seen.

%VSESS-3-VIPC_BUFFER_FULL : Unable to send IPC msg from led [dec] to line card [dec]. IPC buffer full.

Explanation Detect IPC buffer full. Application may send too many IPC messages.

Recommended Action Reduce messages such as reduce SNMP queries, or number of sessions.

%VSESS-4-QAM_ERROR : Physical QAM number [int] or QAM channel [chars] is oversubscribed

Explanation Possible QAM oversubscription. Possible cBR8 provisioning eror. Check QAM/session configuration. Check: show controllers integrated-cable x/y/z all.

%VSESS-5-PROGRAM_CONFLICT_RECOVERED : A program number conflict was resolved by LED [int]. Old session [int] was deleted, new session [int] has been created on line card slot [int] for program number [int]

Explanation Linecard detected a program number conflict on session creation.

Recommended Action Software auto recovered from the error by deleting the old session and recreated the new session.

%VSESS-5-VIDEO_SOURCE_CHANGED : Video Multicast Input Source has switched to [chars], led: [dec], slot [dec]

Explanation Video Input Source has switched to the next source due to input stream failure.

Recommended Action Check service impact, and check the failed input source

%VSESS-6-INPUT_STREAM_ACTIVE : Input Stream has become active for Source [chars], LED [dec], Slot: [dec]

Explanation Input stream has become active again

Recommended Action Informational message, no action needed

%VSESS-6-PMT_RESUMED : PMT is resumed on input stream for program [dec], session ID [dec], LED [dec], Slot [dec]

Explanation PMT is resumed on input stream.

Recommended Action Informational message, no action needed

VTBL

%VTBL-2-RESOURCE_ALLOCATION_ERROR : VTBL Failed to Allocate memory, Led id [int]

Explanation This is an internal software error

%VTBL-3-BW_EXCEED_LIMIT : LED ID [int], Bitrate [int] for input source [chars] on slot [dec] exceeds the configured bitrate

Explanation Session bitrate exceeds the configured bitrate. This is a possible cBR8 provisioning error.

Recommended Action Review the source and configured session bitrate and compare.

%VTBL-3-CA_BLOB_DECODE_ERROR : Encryption error reported for session [int]

Explanation Encryption error reported for video session. This is a possible cBR8 provisioning error.

Recommended Action Review the encrypted video session configuration parameters. Check the CA data in the stream.

%VTBL-3-IGMP_JOIN_FAILURE : Video sessions for LED [dec] has failed to join multicast source [chars] on linecard [dec]

Explanation IGMP Join failure for LED.

Recommended Action Review the input source configuration. This error most likely occured due to no input traffic or network issue

%VTBL-3-MCAST_JOIN_ATTEMPTED : All backup multicast sources [chars] for LED [dec] on linecard [dec] have been attempted.

Explanation IGMP Join failure for all backup sources on LED.

Recommended Action Review the input source configuration. This error most likely occured due to no input traffic or network issue

%VTBL-3-PID_CONFLICT : Conflicting PID [int] reported for session [int]. qam = [int]

Explanation PID conflict reported for video session. This is a possible cBR8 provisioning error.

Recommended Action Review the table based video session configuration parameters. Check for duplicated PID.

%VTBL-3-PROG_NUMBER_CONFLICT : Conflicting program number [int] reported for session [int]. qam = [int]

Explanation Program number conflict reported for video session. This is a possible cBR8 provisioning error.

Recommended Action Review the table based video session configuration parameters. Check for duplicated program number.

%VTBL-3-SESSION_CREATE_FAILED : Failed to create video session [int] on the line card. error = [int]

Explanation Failed to create video session on the line card. This is a possible cBR8 provisioning error.

Recommended Action Review the table based video session configuration parameters

%VTBL-3-SESSION_DELETE_FAILED : Failed to delete video session [int] on the line card. error = [int]

Explanation Failed to delete video session on the line card. This is a possible cBR8 provisioning error.

Recommended Action Review the table based video session configuration parameters

%VTBL-3-SESSION_UPDATE_FAILED : Failed to update video session [int] on the line card. error = [int], oper = [int]

Explanation Failed to update video session on the line card. This is a possible cBR8 provisioning error.

Recommended Action Review the table based video session configuration parameters

%VTBL-3-VIDEO_IN_INIT_FAILURE : Input source initialization failed on slot [dec]. Source [chars], rc = [chars]

Explanation Video input session initialization failed. This is a possible cBR8 provisioning error.

Recommended Action Check the LED configuration on the RP and if the problem persists continue to the next step. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/.If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VTBL-3-VIDEO_OUT_INIT_FAILURE : output session iniialization failed on LC. Output session id [dec], rc = [chars]

Explanation Video output session initialization failed. This is a possible cBR8 provisioning error.

Recommended Action Check the LED configuration on the RP and if the problem persists continue to the next step. Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/.If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.

%VTBL-3-VIDEO_TS_INVALID : PSI error found in input source [chars] on slot [dec]

Explanation PAT/PMT built failure due to invalid input stream

Recommended Action Review the input source configuration and video resources.

%VTBL-6-SOURCE_SWITCHOVER : Multicast redundancy is in use. Video sessions on LED [dec] is switching to a backup source [chars] on linecard [dec]

Explanation Source switchover is detected for LED %d.

Recommended Action Review the input source configuration. This error most likely occured due to no input traffic or network issue.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Cisco cBR Converged Broadband Router Series System Messages

Available Languages

Download Options

Bias-Free Language

Cisco cBR Series Converged Broadband Routers System Messages

Overview of System Messages

System Messages Description

B

C

D

G

I

L

M

R

S

U

V

Obtaining Documentation and Submitting a Service Request

Was this Document Helpful?

Contact Cisco

This Document Applies to These Products