%GRP Errors on Cisco 12000

davidhvoss · ‎04-29-2005

Seeing the following errors on our system. Do you know what these may be? I can find nothing on Cisco's site:

Cisco Internetwork Operating System Software

IOS (tm) GS Software (GSR-P-M), Version 12.0(23)S3, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

TAC Support: http://www.cisco.com/tac

Compiled Fri 23-May-03 12:23 by nmasa

Image text-base: 0x50010CD8, data-base: 0x52324000

ROM: System Bootstrap, Version 11.2(20030116:225008) [rarcher-pre_lci_throttle 184], DEVELOPMENT SOFTWARE

BOOTLDR: GS Software (GSR-P-M), Version 12.0(23)S3, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

xx-xxxxx-xx uptime is 52 minutes

System returned to ROM by RPR Switchover

System restarted at 15:06:47 EDT Fri Apr 29 2005

System image file is "slot0:gsr-p-mz.120-23.S3.bin"

cisco 12012/GRP (R5000) processor (revision 0x05) with 262144K bytes of memory.

R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache

Last reset from power-on

LOGFILE

.Apr 26 12:16:07.913 EDT: %GRP-4-SEQUENCE: Sequence error detected from slot 1. Expected 0

.Apr 26 12:16:07.913 EDT: %GRP-4-FIRSTLAST: First/Last cell error detected from slot 1

.Apr 26 14:24:30.937 EDT: %GRP-4-SEQUENCE: Sequence error detected from slot 1. Expected 2

.Apr 26 14:24:30.937 EDT: %GRP-4-CORRUPT: Corrupted packet, start_offset 65535, length 0, slot 15

.Apr 26 17:38:21.070 EDT: %GRP-4-SEQUENCE: Sequence error detected from slot 1. Expected 7

.Apr 26 17:38:21.070 EDT: %GRP-4-CORRUPT: Corrupted packet, start_offset 59647, length 0, slot 15

spremkumar · ‎04-30-2005

hi

hope this helps..

1. %GRP-4-SEQUENCE: Sequence error detected from slot [int]. Expected [int]

A cell was received with an incorrect sequence number.

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

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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.

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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.

regds