Table Of Contents

GRP Messages

GRP_C10K_CH_DS3 Messages

GRP_C10K_SRP Messages

GRPSPA Messages

GRP Messages

The following are Gigabit Route Processor (GRP) messages.

Error Message    

%GRP-3-ABANDON_DOWNLOAD : End attempt to start the linecard in slot [dec]

Explanation    The line card has repeatedly failed to initialize (come up). The system will stop the download attempts for a period of at least ten minutes.

Recommended Action    Repeated failures to download may be caused by a board that is seated incorrectly. Try reseating the board. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-ADDRERROR : Bad access to fabric-buffers : invalid address

Explanation    An illegal access was made to fabric buffers. This usually indicates a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-ADJ_UPDATER : [chars] adj([chars])->oi([hex])

Explanation    The adjacency indicated has been delayed because layer 2 information is missing in the egress line card.

Recommended Action    This is a debug message only. No action is required.

Error Message    

%GRP-4-BADCARDTYPEATMSYNC : Failed to get atm property [chars]. Sync failed for slot=[dec], intf=[dec]\n

Explanation    An active-to-standby RP synchronization of an ATM channel or VP tunnel ID, and their respective VC and VP, has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-3-BAD_FSM_LOOKUP : Invalid event [chars] for card [dec] state [chars] phase [chars]

Explanation    The GRP Finite State Machine controlling the line card received an event that was unexpected for the current state. This condition typically indicates a software error. The GRP should put the line card into a known state and then return it to its normal running condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-3-BAD_LC_STATE : Cannot send pkt to slot [int]; state [chars]

Explanation    A message was attempted to be sent to a card that was in an incorrect state. The card and state are shown in the error message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-BADLENGTH : fabric register mismatch, expected [int], received [int]

Explanation    A packet was received from the fabric, but the length received and the length indicated in the buffer header do not match.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message     

%GRP-3-BADSTATE : Reassembly for slot [int], state [int]

Explanation    Software is in an incorrect state for receiving the current packet over the fabric. The message indicates the slot to which the packet was received and the state of the reassembly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-BLOCKTIMEOUT : Fabric send timeout (cback: [hex], slot: [dec])

Explanation    A hardware or software problem has been detected over the fabric between the master RP and the card in the slot specified in the error message. This condition could be created by, most likely, a software problem or, less likely, a hardware problem. The following is a list of possible reasons for this message; however, it is not all-inclusive:

–A software failure has occurred in which a process has disabled interrupts long enough for five consecutive fabric pings to be missed. This condition indicates a problem with the software on the destination card.

–The RP could not send a fabric ping to the specified line card. If a fabric ping cannot be sent for a number of consecutive times, the destination card will be reset.

–The RP could not send data other than a fabric ping to the specified line card. If the data that has failed to be sent is not a fabric ping, the destination card will not be reset, but this condition may affect other functionality of the RP; for example, CEF might be disabled.

–A hardware problem has occurred on the RP or GRP, in the fabric, or on the destination card. If the error was due to a hardware problem with the GRP, other IPC timeout messages would be logged before the fabric ping failure, and entering the show contr fia command on the GRP would show errors, while entering the show contr fia command on the line card would not.

Recommended Action    Consider upgrading the system to the latest Cisco IOS software version in your release train to eliminate all resolved software problems. If this message recurs, copy the error message exactly as it appears on the console or in the system log, enter the show controller fia command and, if the line card was reloaded, the show context slot slot-number command with slot-number being the line card in the specified slot, contact your Cisco technical support representative, and provide the representative with the information you have gathered. More information on Troubleshooting Fabric Ping Timeouts and Failures on the Cisco 12000 Series Internet Router is available at the following URL: http://www.cisco.com/warp/public/63/ping_failure_12421.shtml.

Error Message    

%GRP-5-BOOTVARSYNC : Standby GRP BOOT variable not set, syncing Active GRP BOOT variable to standby GRP

Explanation    The active RP will synchronize its boot variable to standby only if the standby RP boot variable is null. The purpose of this blockage is to protect the user from unexpectedly booting the boot image of the standby RP when a failover occurs in the router, undermining the effectiveness of a dual RP system. This message also serves as a warning in dual RP systems to indicate that the standby RP did not have its boot variable set to handle a potential failover.

Recommended Action    This message informational only. No action is required.

Error Message    

%GRP-4-BWTH_LOW : Insufficient fabric bandwidth for card in slot [dec]

Explanation    The installed fabric configuration does not have the capacity for supporting the line card installed in the mentioned slot. Either one or more fabric cards are not installed properly or a 10 Gigabit line card is attempting to be used in a chassis with a 2.5 Gigabit fabric.

Recommended Action    Enter the show gsr command to examine the installed fabric and ensure that all cards are of the same type, and of the type that is expected. If the configuration appears valid, and 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    

%GRP-4-CAMFULL : couldn't add [enet] to Ethernet

Explanation    Too many MAC addresses were put into an Ethernet cam of the GRP. This situation usually indicates a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-CARVE_FREEQS : Number of free queues to carve ([int]) is greater than max allowed ([int])

Explanation    The number of free queues allowed for the SDRAM buffer carving has been exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-CARVE_INFO : Setting mtu above [int] may reduce available buffers on Slot: [int].

Explanation    The SDRAM page size should be larger than the largest buffer size carved.

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    

%GRP-3-CARVE_VALUE_FAIL : [chars] BMA, slot [int]

Explanation    The carve values from the line card could not be read by the RP. The line card could become disabled at this point.

Recommended Action    Try rebooting the line card. If this fails to fix the problem, consider power cycling the router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    

%GRP-3-CARVE_WATCHBOOL_ERR : Error creating a watched boolean used for buffer carving on slot [dec]

Explanation    The software has attempted to create a watched Boolean during buffer carving to the slot specified in the error message. This condition might occur could happen if the RP is running out of memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-CELLNEG : Detected an internal signal error on the fabric interface

Explanation    An internal signal between the CSAR and the FIA was deasserted too early.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-4-CFGSYNC : Failed to sync [chars] to secondary RP.

Explanation    The primary RP has failed to synchronize the specified configuration data to the secondary RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-COREDUMP : Core dump incident on slot [int], error: [chars]

Explanation    The master GRP has determined that a line card or a secondary route processor has reached such a bad state that a diagnostic core dump might be appropriate. If exception core dumps are configured for that slot, a dump will be taken. The qualifying string gives further details of the error that has caused the dump request.

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    

%GRP-4-CORRUPT : Corrupted packet, start_offset [int], length [int], slot [int]

Explanation    A buffer with a corrupted buffer header was received from the fabric.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-4-CRC32 : CRC32 error detected from slot [int]

Explanation    A crc32 error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-CRYPTOKEY_INCOMPLETE : [chars]\n

Explanation    While the encryption (crypto) keys were being synchronized, and before an entire key had completely and successfully synchronized to the standby RP, a, nonrecoverable problem was encountered. This condition will result in one or more missing crypto keys on the standby RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-DOWNREV_FABLDR : Slot [dec] ROM fabldr too old; downloading from bundle

Explanation    The fabric downloader in the ROM of the slot specified in the error message is not usable given the current hardware configuration of the router. Instead, the version bundled within the Cisco IOS software image will be used to boot the system line cards. This action produces a significant delay when the router is being reloaded.

Recommended Action    Enter the upgrade command to upgrade the fabric downloader in the slot specified in the error message.

Error Message    

%GRP-4-DRVSYNC : [chars] \n

Explanation    An error has occurred while the system was synchronizing driver states from the active RP to the standby RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-EHSASEC : Reverting to EHSA redundancy: [chars]

Explanation    The system software has reverted to EHSA style redundancy.

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    

%GRP-3-ENCAP : Failure to [chars], slot [int] (info [hex])

Explanation    An attempt to allocate or free encapsulation memory has failed. If no other Messages show that there is a hardware error with the GRP or with the specified line card, this condition is most likely due to a software error.

Recommended Action    Consider upgrading your system to the latest Cisco IOS software release in your release train to take advantage of recent fixes. If the problem still occurs after the upgrade, copy the error message text and the output of the diagnostic tests exactly as they appear on the console or in the system log, enter the show tech-support command, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-FABPINGTIMEOUT : Fabric ping timeout, Resetting slot [dec] (sequence number [dec])

Explanation    The line card or standby GRP is not responding to ping messages sent over the fabric. This condition usually indicates a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-6-FAILOVER_PENDING : [chars]\n

Explanation    This message provides information regarding a pending failover to the standby RP.

Recommended Action    No action is required.

Error Message    

%GRP-3-FAILURE_TO_POWER_UP : The linecard in slot [dec] would not power on correctly

Explanation    The line card did not respond to the GRP even after repeated recovery attempts. It will be left permanently powered down. The card may be badly seated, or there may be a more serious hardware fault.

Recommended Action    Try reseating the board. If this condition persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-2-FDNLDAIOFAIL : fab downloader async i/o write to slot [dec] failed [chars]

Explanation    The fabric downloader could not be downloaded over the maintenance bus to the card because the write operation has failed. The download will be automatically retried.

Recommended Action    If this condition persists, copy the error message exactly as it appears on the console or in the system log along with any previous Messages, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-2-FDNLDFAIL : fab downloader download to slot [dec] failed [chars]

Explanation    The fabric downloader could not be downloaded over the maintenance bus to the card. The download will be automatically retried.

Recommended Action    If this condition persists, copy the error message exactly as it appears on the console or in the system log along with any previous Messages, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-2-FDNLDTIMEOUT : fab downloader download to slot [dec] timed out

Explanation    An attempt to download the fabric downloader over the maintenance bus timed out. The download will be automatically retried.

Recommended Action    If this condition persists, copy the error message exactly as it appears on the console or in the system log along with any previous Messages, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-4-FIRSTLAST : First/Last cell error detected from slot [int]

Explanation    A cell was received with an invalid first or last bit set.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-4-FROMFABPAR : Parity error detected in from fabric buffer memory. Slot [int]

Explanation    A parity error was detected from the fabric buffers.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-6-GSRRF : [chars] \n

Explanation    This message provides Redundancy Facility-specific logging information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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    

%GRP-3-IDB : IDBs [chars] in slot [dec] \n

Explanation    IDB processing for the slot specified in the error message has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-3-IDB_COUNT : IDB count check fail [chars] in slot [dec]

Explanation    A sanity check for interface data structure counters did not complete successfully. The system will attempt to contain the fault by limiting processing to the known valid range. The condition indicates a software fault that may have been triggered by a very large configuration or by multiple reloads of the line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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    

%GRP-4-INTFCFG : Possible inconsistency in standby config
if global config contains direct reference to interfaces of slot [dec]

Explanation    After an LC has been removed or is resetting, if a standby RP is reset or an OIR is performed on a standby RP, when the LC is reinserted, the standby RP could be missing some global configuration related to the interfaces on the removed LC.

Recommended Action    If an inconsistency in standby and global configuration is present, reset the standby RP.

Error Message    

%GRP-3-INV_CHAIN : Replaced [chars] with [chars]

Explanation    A hardware or software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. 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    

%GRP-3-INVLDQ : Invalid outputq to [chars], drr queue [dec], type [dec], index [dec]

Explanation    An invalid DRR queue was selected to be sent from the RP to an interface.

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    

%GRP-3-INV_UNCHAIN : [chars] not found

Explanation    A hardware or software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. 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    

%GRP-3-LC_CARD_TYPE_INVALID : Linecard has invalid card type [hex]

Explanation    The line card type is invalid. The line card EEPROM is programmed with an invalid card type.

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    

%GRP-3-LC_FLASH_PROG_FAIL : [chars]

Explanation    The line card Flash memory failed to be programmed. This condition may indicate a problem with the line card Flash memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-5-LC_FLASH_PROG_OK : [chars]

Explanation    Programming of the line card Flash memory has been completed successfully.

Recommended Action    No action is required.

Error Message    

%GRP-3-LC_ROMMON_STARTUP_FAILURE : Slot [dec], output = [chars]

Explanation    The line card did not respond to the GRP even after repeated recovery attempts. The line card ROM monitor software sent some startup messages but did not fully initialize. The condition may be caused by badly-seated memory in a line card or a more serious hardware fault.

Recommended Action    Try removing the board and carefully reseating any memory. If this condition persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-MALLOC_FAIL : [chars]

Explanation    The RP could not allocate memory for its use. This problem can occur if there is not enough memory in the system.

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. data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-3-MEMSIZE : Non oct-byte access to fabric buffers

Explanation    An illegal access was made to fabric buffers. This condition usually indicates a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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. tative, and provide the representative with the information you have gathered.

Error Message    

%GRP-5-NEWPRIMARY : Switchover to new GRP

Explanation    The GRP in which the log is stored has become the primary GRP in a dual GRP system. In other words, there has been a failover. Examine the logs from before the failover to find some indication as to why the failover occurred. The NEWPRIMARY message marks the point of failover.

When the GRP that is currently the primary GRP was the secondary before the failover, it was accumulating log messages from the line cards, as can be seen by issuing the show logging slot slot-number command. The GRP was also accumulating log messages from the GRP that was the primary before the failover, again saving these in a per-slot log. The main log (as viewed with the show logging command) contains only those log messages that were generated locally prior to the failover.

To see what was recorded in the log for the GRP that was previously the primary GRP, enter the show logging slot slot-number command, with slot-number being the slot number of the previous primary processor. Log messages from line cards are recorded once in the per-line card log and then again in the primary GRP log once it has been processed by the primary GRP. If the GRP crashed before it placed the line card message into the system log, the event will still be visible in the per-line card log.

Recommended Action    This message is informational only. No action is required.

Error Message    

%GRP-4-NO_AUTORESET : Auto-reset disabled in config; manual reload of slot [dec] required

Explanation    A line card failure has occurred, but the "no service auto-reset" parameter has been configured, thus keeping the card from being restarted.

Recommended Action    No action is required. In order for the card to become functional again, it must be forcibly reloaded via the CLI.

Error Message     

%GRP-3-NOBUF : Could not malloc line card reset structures on RP (size=[int])

Explanation    The RP could not allocate memory data structures for the line card to reset data structures at startup time. This situation is not in and of itself a serious problem, but the underlying memory shortage at startup time will likely prevent the router from running well, if at all.

Recommended Action    Add more memory and/or debug the memory shortage problem.

Error Message     

%GRP-3-NOBUFLC : Could not malloc line card reset info buffer on RP (LC=[int],bufnum=[int],size=[int])

Explanation    The RP could not allocate memory for one or more buffers to hold line card reset information at startup time. This situation is not in and of itself a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well, if at all.

Recommended Action    Debug the memory shortage problem and determine whether you need to add more memory. Try reducing the size of or the number of reset information buffers allocated per line card to hold crash information.

Error Message    

%GRP-4-NODRVATMBULKSYNC : Failed to sync atm driver [chars] id bulk data (slot=[dec], intf=[dec]) to standby RP\n

Explanation    An active RP to standby RP bulk synchronization of an ATM channel or VP tunnel ID has occurred, and the VC of the ATM channel, or VP of the VP tunnel ID, has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NODRVATMPROPSYNC : Failed to sync driver atm [chars] (slot=[dec], intf=[dec], [chars]=[dec], [chars]=[dec], [chars]=[hex]) to standby RP; HA_SYNC_STATUS = [dec]\n

Explanation    An active-to-standby RP dynamic synchronization of the ATM property has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NODRVATMSYNC : Failed to sync driver atm [chars] id (slot=[dec], intf=[dec], [chars]=[dec], [chars]=[dec]) to standby RP; HA_SYNC_STATUS = [dec]\n

Explanation    An active RP to standby RP dynamic synchronization of an ATM channel or VP tunnel ID has occurred, and the VC of the ATM channel, or VP of the VP tunnel ID, has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NODRVFEBULKSYNC : Failed to sync FE shadow cam bulk data (slot = [dec], intf = [dec]) to standby RP\n

Explanation    The active to standby RP bulk synchronization of the FE shadow cam has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NODRVFESYNC : Failed to sync FE shadow cam entry (slot = [dec], intf = [dec], error code [hex]) to standby RP\n

Explanation    The active to standby RP FE shadow cam entry synchronization has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NODRVFESYNCCMD : Unknown FE shadow cam sync command, slot = [dec], intf = [dec], CMD = [dec]\n

Explanation    The active to standby RP FE shadow cam entry synchronization has failed because of an unknown command.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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     

%GRP-4-NODRVGEBULKSYNC : Failed to sync GE shadow cam bulk data (slot = [dec], intf = [dec]) to standby RP\n

Explanation    The active to standby RP bulk synchronization of the GE shadow cam has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NODRVGESYNC : Failed to sync GE shadow cam entry (slot = [dec], intf = [dec], error code [hex]) to standby RP\n

Explanation    The active to standby RP GE shadow cam entry synchronization has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NODRVGESYNCCMD : Unknown GE shadow cam sync command, slot = [dec], intf = [dec], CMD = [dec]\n

Explanation    The active to standby RP GE shadow cam entry synchronization has failed because of an unknown command.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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    

%GRP-4-NOE3QMFMBULKSYNC : Failed to sync E3 QM/FM bulk data to standby RP\n

Explanation    An active-to-standby-RP bulk synchronization of the E3 QM or FM has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOE3QMFMSYNC : Failed to sync E3 QM/FM dynamic data to standby RP\n

Explanation    An active-to-standby-RP dynamic synchronization of the E3 QM or FM has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOE3QOSMGRBULKSYNC : Failed to sync E3 QoS Mgr bulk data to standby RP\n

Explanation    An active-to-standby-RP bulk synchronization of the E3 QoS Manager has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOE3UIDBBULKSYNC : Failed to sync E3 uidb bulk data to standby RP\n

Explanation    An active-to-standby-RP bulk synchronization of E3 UIDBs has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOE3UIDBSYNC : Failed to sync E3 uidb id dynamic data to standby RP\n

Explanation    An active-to-standby-RP dynamic synchronization of the E3 UIDBs has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NOENCAPBULKSYNC : Failed to sync encap table (slot = [dec]) to standby RP\n

Explanation    The active RP to standby RP encapsulation table bulk synchronization has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOENCAPSYNC : Failed to sync encap table change (slot = [dec]) to standby RP\n

Explanation    The active RP to standby RP encapsulation table change data synchronization has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOGEINSTANCE : Received invalid GE instance (slot=[dec], port=[dec])\n

Explanation    An invalid GE instance was acquired from the HWIDB provided from the active RP to synchronize the GE information to the standby RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOHWIDB : Required hardware IDB is missing (slot = [dec], intf = [dec])\n

Explanation    An invalid hardware IDB was acquired from the slot information that was provided to prepare for synchronizing the driver to change from being the active to the standby RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-4-NOHWIDB : [chars] \n

Explanation    An invalid HWIDB was acquired from the slot information provided to prepare for synchronizing driver information from the active to the standby RP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%GRP-3-NOMEM : Memory allocation failure [chars]

Explanation    A memory allocation operation has failed.

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. data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%GRP-4-NOOIBULKREAD : Failed to read output info bulk sync data (slot = [dec]) on standby RP\n

Explanation    Bulk synchronization of the standby RP read output information table has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%GRP-4-NOOIBULKSYNC : Failed to sync output info table (slot = [dec]) to standby RP\n

Explanation    Bulk synchronization of the active RP to standby RP output information table has failed.

Recom