Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Cisco 6509 - I/F Index checksum failed ?

Does anyone know what these messages mean, is there a reference on site that provides info on this error and what actions to take ?

Network Management Processor (ACTIVE NMP) Log:

Reset count: 6

Re-boot History: Feb 25 2002 10:11:40 0, Feb 12 2002 04:13:05 0

Feb 07 2002 06:46:43 0, Feb 07 2002 02:57:20 0

Feb 07 2002 01:27:22 0, Feb 05 2002 02:33:50 0

Bootrom Checksum Failures: 0 UART Failures: 0

Flash Checksum Failures: 0 Flash Program Failures: 0

Power Supply 1 Failures: 0 Power Supply 2 Failures: 1

Swapped to CLKA: 0 Swapped to CLKB: 0

Swapped to Processor 1: 0 Swapped to Processor 2: 0

DRAM Failures: 0

Exceptions: 0

Loaded NMP version: 6.2(3)

Reload same NMP version count: 4

Last software reset by user: 2/7/2002,01:27:02

EOBC Exceptions/Hang: 0

Heap Memory Log:

Corrupted Block = none

NVRAM log:

01. 3/7/2003,09:03:21: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

02. 3/7/2003,09:07:22: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

03. 3/7/2003,09:11:22: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

04. 3/7/2003,09:15:23: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

05. 3/7/2003,09:19:23: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

06. 3/7/2003,09:28:09: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

07. 3/7/2003,09:32:10: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

08. 3/7/2003,09:36:10: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

09. 3/7/2003,09:40:11: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

10. 3/7/2003,09:44:11: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

11. 3/7/2003,09:48:12: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

12. 3/7/2003,09:52:12: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

13. 3/7/2003,09:56:13: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

14. 3/7/2003,10:00:13: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

15. 3/7/2003,10:04:14: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

16. 3/7/2003,10:05:07: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

17. 3/7/2003,10:05:07: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

18. 3/7/2003,10:08:14: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

19. 3/7/2003,10:12:15: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

20. 3/7/2003,10:16:15: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

21. 3/7/2003,10:20:16: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

22. 3/7/2003,10:24:16: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

23. 3/7/2003,10:28:17: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

24. 3/7/2003,10:32:18: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

25. 3/7/2003,10:36:18: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

26. 3/7/2003,10:40:19: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

27. 3/7/2003,10:44:19: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

28. 3/7/2003,10:48:20: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

29. 3/7/2003,10:52:21: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

30. 3/7/2003,10:56:21: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

31. 3/7/2003,11:00:22: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

32. 3/7/2003,11:04:22: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

33. 3/7/2003,11:08:23: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

34. 3/7/2003,11:12:23: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

35. 3/7/2003,11:16:24: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

36. 3/7/2003,11:20:24: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

37. 3/7/2003,11:24:10: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

38. 3/7/2003,11:24:25: new_nvram_checksum:Block 61 checksum failed: 0x4EE0(0x4EA

0)

Module 3 Log:

Reset Count: 6

Reset History: Mon Feb 25 2002, 10:12:44

Tue Feb 12 2002, 04:14:09

Thu Feb 7 2002, 06:47:47

Thu Feb 7 2002, 02:58:25

Module 15 Log:

Reset Count: 8

Reset History: Mon Feb 25 2002, 10:12:51

Tue Feb 12 2002, 04:14:17

Fri Feb 8 2002, 03:18:25

Thu Feb 7 2002, 07:04:03

AO-CW33B-DS-1> sh ver

WS-C6509 Software, Version NmpSW: 6.2(3)

Copyright (c) 1995-2001 by Cisco Systems

NMP S/W compiled on Jul 23 2001, 11:34:30

System Bootstrap Version: 6.1(4)

Hardware Version: 2.0 Model: WS-C6509 Serial #: SCA054401PS

PS1 Module: WS-CAC-1300W Serial #: SNI05160797

PS2 Module: WS-CAC-1300W Serial #: SNI05160532

Mod Port Model Serial # Versions

--- ---- ------------------- ----------- --------------------------------------

1 2 WS-X6K-SUP2-2GE SAD053902KK Hw : 3.2

Fw : 6.1(4)

Fw1: 6.1(3)

Sw : 6.2(3)

Sw1: 6.2(3)

WS-F6K-PFC2 SAD054001WM Hw : 2.0

3 16 WS-X6416-GBIC SAL0542D8CV Hw : 1.0

Fw : 5.4(2)

Sw : 6.2(3)

15 1 WS-F6K-MSFC2 SAD053904T0 Hw : 1.2

Fw : 12.1(3a)E4

Sw : 12.1(3a)E4

DRAM FLASH NVRAM

Module Total Used Free Total Used Free Total Used Free

------ ------- ------- ------- ------- ------- ------- ----- ----- -----

1 130944K 61517K 69427K 32768K 7025K 25743K 512K 254K 258K

I/F Index checksum failed.

Uptime is 375 days, 0 hour, 57 minutes

1 REPLY
Cisco Employee

Re: Cisco 6509 - I/F Index checksum failed ?

You are hitting the following bug

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdx87646

I suggest that you back up your config to device bootflash using "copy config flash" command and resetting the system using "reset system" command. Make sure you back up your config as you will loose part or all of your config due to this bug. Also if you can upgrade to 6.4(2) in 6.x release which has a fix for this bug

189
Views
0
Helpful
1
Replies
CreatePlease login to create content