Table Of Contents

MCC192 Messages

MDS Messages

MDT Messages

MDX Messages

MEM_ECC Messages

MEMPOOL Messages

MEMSCAN Messages

MFIB Messages

MFIB_STATS Messages

MICA Messages

MISTRAL Messages

MLD_PROT Messages

MODEM Messages

MODEM_HIST Messages

MPA68360 Messages

MPLS_ATM_TRANS Messages

MPLS_TE Messages

MPLS_TE_LM Messages

MCC192 Messages

The following are MCC192 messages.

Error Message     

%MCC192-3-CPUIF : Error=[hex]\n rd [hex] base [hex] hdr [hex] last [hex] wr [hex] insert [hex] back [hex] len [hex] cnt [hex]\n

Explanation    A software error has been detected by the CPUIF module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-CPUIF_ERR : [chars].

Explanation    A hardware error has been detected by the CPUIF module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-CPUIF_FIFO_DUMP : [hex]: [hex] [hex] [hex] [hex]

Explanation    A hardware error has been detected by the CPUIF module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-CPU_PIF : Error=[hex]
rd [hex] wr [hex] pkt_ins_cmd [hex] pkt_len [dec] pkt_count [dec]\n

Explanation    A software error has been detected by the CPU PIF module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-CPUPI_RAM_MBE : [chars] Syndrome [hex], Address [hex], samebit [chars], diffbit [chars]\n

Explanation    A multiple-bit error has been detected by the CPUIF module in packet insertion RAM. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-CPUPI_RAM_SBE : [chars] - Single Bit Error detected and corrected
Syndrome [hex], Address [hex], samebit [chars], diffbit [chars]\n

Explanation    An SBE error has been detected by the CPUIF module in Packet Insertion RAM. The SBE error has already been corrected and the device will not be reset. If the problem persists, the card will be automatically reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-ECC : [chars]:[chars],Syndrome=[hex] Addr=[hex], samebit [chars], diffbit [chars]

Explanation    An hardware ECC error has been detected in the MCC module on the Internet Router engine 6 line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-MDRR : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the MDRR module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-PKTMEM_MBE : Error=[hex] - Syndrome=[hex] Addr=[hex]
Data=[hex][hex] [hex][hex]\n [hex][hex] [hex][hex]\n [hex][hex] [hex][hex]
[hex][hex] [hex][hex]

Explanation    A hardware error has been detected by the RLDRAM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-PKTMEM_SBE : Single bit error detected and corrected
Error=[hex] - Syndrome=[hex] Addr=[hex] [chars]

Explanation    A hardware error has been detected by the RLDRAM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-QM : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the QM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-QM_FBF_MBE : [chars] MBE Syndrom = [hex], Addr = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error occurred in the QM free block FIFO component. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-QM_FBF_SBE : [chars] - Single Bit Error detected and corrected
Syndrom = [hex], Addr = [hex], samebit [chars], diffbit [chars]

Explanation    An SBE error has occurred in the QM free block FIFO queue. The SBE error has been corrected, and the Ares ASIC will not be reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-QSTAT : [chars] [hex].

Explanation    A hardware error has been detected by the QSTAT module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-RED : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the RED module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-RED_AQD_SBE : [chars] - Single Bit Error detected and corrected
Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    An SBE error has been detected by the RED module in AQD RAM. The SBE error has already been corrected and the device will not be reset. If the problem persists, the card will be automatically reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-RED_PARAM1_SBE : [chars] - Single Bit Error detected and corrected
Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    An SBE error has been detected by the RED module in PARAM1 RAM. The SBE error has already been corrected and the device will not be reset. If the problem persists, the card will be automatically reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-RED_PARAM2_SBE : [chars] - Single Bit Error detected and corrected
Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    An SBE error has been detected by the RED module in PARAM2 RAM. The SBE error has already been corrected and the device will not be reset. If the problem persists, the card will be automatically reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-RED_STAT_SBE : [chars] - Single Bit Error detected and corrected
Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A SBE error has been detected by the RED module in the part of RAM that performs statistical processing (Stat RAM). The SBE error has already been corrected and the device will not be reset. If the problem persists, the card will be automatically reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-RIM : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the RIM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-RS : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the RS module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-QM_FBF_MBE : [chars] MBE Syndrom = [hex], Addr = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error has occurred in the QM free block FIFO component. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-6-QM_FBF_SBE : [chars] SBE Syndrom = [hex], Addr = [hex], samebit [chars], diffbit [chars]

Explanation    A single-bit error occurred in the QM free block FIFO component. The SBE error has been corrected, and the card or Ares ASIC will not be reset.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-RED_AQD_MBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error has been detected in AQD RAM by the RED module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-6-RED_AQD_SBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A single-bit error has been detected in AQD RAM by the RED module. If the SBE error has been corrected, the device will not be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-RED_PARAM1_MBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error has been detected in PARAM1 RAM by the RED module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-6-RED_PARAM1_SBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A single-bit error has been detected in PARAM1 RAM by the RED module. If the SBE error has been corrected, the device will not be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-RED_PARAM2_MBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error has been detected in PARAM2 RAM by the RED module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-6-RED_PARAM2_SBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A single-bit error has been detected in PARAM2 RAM by the RED module. If the SBE error has been corrected, the device will not be reset. If the problem persists, the card will be reset automatically.

Explanation    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-RED_STAT_MBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A multiple-bit error has been detected in statistical (Stat) RAM by the RED module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-6-RED_STAT_SBE : [chars]. Syndrome = [hex], Address = [hex], samebit [chars], diffbit [chars]

Explanation    A single-bit error has been detected in statistical (Stat) RAM by the RED module. If the SBE error has been corrected, the device will not be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-SDRAM_MBE : Error=[hex] - DIMM[dec] Syndrome=[hex] Addr=[hex]

Explanation    A multiple-bit error has been detected by the SDRAM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-SDRAM_SBE : Single bit error detected and corrected
Error=[hex] - DIMM[dec] Syndrome=[hex] Addr=[hex] [chars]

Explanation    A hardware error has been detected by the SDRAM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MCC192-3-SDRAM_SPD : EPROM contents for DIMM[dec]:
[chars]

Explanation    A hardware error has been detected by the SDRAM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%MCC192-3-SIM : Error=[hex] - [chars].

Explanation    A hardware error has been detected by the SIM module. The device will be reset. If the problem persists, the card will be reset automatically.

Recommended Action    If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MDS Messages

The following are multicast distributed switching messages. Explanations and recommended actions for these error messages are not currently available.

Error Message    

%MDS-2-INIT : Error initializing MDS structures

Explanation    An error occurred when the system attempted to initialize MDS structures.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_FAILED_IPC_ACK : RP failed in getting Ack for IPC message of size [dec] to LC in slot [dec] with sequence [dec], error = [chars]

Explanation    The Route Processor has failed to obtain IPC acknowledgment

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-LC_FAILED_IPC_OPEN : LC in slot [dec] failed to open IPC port to RP, error = [chars]

Explanation    The line card has failed to open an IPC port to the Route Processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_FAILED_SEND_LC_READY : LC in slot [dec] failed to send LC ready to RP, error = [chars]

Explanation    The line card has failed to send a Ready message to the Route Processor

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_INIT : Error initializing linecard

Explanation    System resources could not be allocated on the line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_INVALID_HWIDB_INDEX : Invalid if_index for HWIDB [chars]

Explanation    The hardware IDB interface index is invalid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-LC_INVALID_HWIDBQ_SIZE : Invalid Q count value

Explanation    The hardware IDB queue count has an invalid value.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_INVALID_MROUTE_MSG : Unknown message received from RP

Explanation    An unrecognized route event has been sent from the Route Processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-LC_INVALID_MSG : Unknown IPC received from RP

Explanation    An unrecognized message type has been sent from the Route Processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_INVALID_SIZE : Unknown IPC size received from RP

Explanation    An unrecognized IPC size has been sent from the Route Processor

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-LC_INVALID_SWIDB_IFNUM : Invalid if_num for SWIDB [chars]

Explanation    The software IDB interface number is invalid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_INVALID_SWIDBQ_SIZE : Invalid Q count value

Explanation    The software IDB queue count has an invalid value.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_NOIPCBUFFR : No IPC buffers available for messages to be sent to the RP

Explanation    The system has run out of buffers for IPC.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_PLATFORM : [chars] ([dec])

Explanation    Unavailable.

Recommended Action    Unavailable.

Error Message    

%MDS-2-LC_SPDLISTCORR : SPD list corrupted

Explanation    The list of Selective Packet Discard has become corrupted.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-LC_SWIDB_UPDATE_NULL_MVRF : LC received swidb update for if_number [hex] ([chars]) tableid [hex].mvrf pointer for this tableid is NULL.

Explanation    The line card has received a software IDB update from the Route Processor specifying a multicast VRF table ID for which no multicast VRF exists in the line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%MDS-2-RADIXINSERT : Error trying to add mdfs entry for group=[IP_address], source=[IP_address]

Explanation    An error in adding an MDFS Mtrie entry has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-RADIXMATCH : Error trying to match mdfs entry for group=[IP_address], source=[IP_address]

Explanation    An error in matching an MDFS Mtrie entry has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-3-ROUTECOUNT_ZERO : Multicast route count reached zero

Explanation    The multicast route count has unexpectedly reached zero.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-4-ROUTELIMIT : [int] routes exceeded multicast route-limit of [dec]

Explanation    The number of multicast routes exceeds the configured maximum allowed. New routes cannot be added unless the configuration is changed.

Recommended Action    If multicast traffic is of any priority among the traffic carried by this router, enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

Error Message    

%MDS-2-RP : [chars]

Explanation    The Route Processor either cannot allocate memory or has missing data.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     

%MDS-2-RP_FAILED_IPC_CREATE : RP failed in creating IPC port, error = [chars]

Explanation    The Route Processor failed to create an MDS Interprocess Communications port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-2-RP_RCV_IPC_ERR_SIZE : RP received oversized IPC, size = [dec], type = [dec]

Explanation    The Route Processor has received oversized IPC message from the line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.rom the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%MDS-3-UNMAPPED_MDFS_IF_INDEX : \n NULL/Invalid ifindex [hex] received for target interface.

Explanation    The interface identifier specified for the input MDFS HWIDB does not correspond to a known interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MDT Messages

The following are PIM MDT messages.

Error Message    

%MDT-5-DATA_MDT_REUSED : Data MDT [IP_address] is reused in VRF [chars]

Explanation    A data MDT group has been reused by a VRF. A data MDT group can be reused by a particular host that sources user traffic in a VPN if all pre-defined data MDT groups are used.

Recommended Action    No action is required.

Error Message    

%MDT-4-LBSRC : MDT [chars] uses source address [IP_address] from a non-loopback interface

Explanation    The local peering interface used to set up the MDT tunnel is not a loopback interface. This condition may cause black holes if the interface is in the outgoing list of the MDT group.

Recommended Action    Change the configuration of the BGP update source and use a loopback interface as the local peering interface.

Error Message    

%MDT-4-TUNSYNCRCV : [chars] failure in reception of MDT tunnel sync information

Explanation    Confirmation has failed for standby RP reception of an MDT tunnel message. This message is needed to provide the standby RP with MDT information required for creation of the MDT tunnel.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message    

%MDT-4-VRFSRC : The source interface of the MDT tunnels, [chars], is not in the global table

Explanation    The local peering interface must not be an interface in a VRF.

Recommended Action    Change the configuration of "BGP update source" and use a loopback interface in the global table.

MDX Messages

The following are MDX error messages for the Cisco Internet Router se