cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
298
Views
0
Helpful
3
Replies

Catalyst 2948G Gives Multiple Errors...

klivesey
Level 1
Level 1

Greetings,

I have an issue with a 2948G switch. The unit generates the following errors (sample given bellow) and stops switching on all ports. A reset of the switch resolves the issue for a period a day or so, after which, then produces the given errors and the halt of all switching functions.

The unit is running the latest RMON and CAT/IOS.

I have searched Cisco’s TAC and Forums but noting the mirrors this. This baby FUBAR?

Errors:

Console> (enable) 2003 Oct 24 17:02:14 %SYS-4-P2_WARN: 1/Protocol Packet

DA=01:00:5e:7f:ff:fa SA=00:0c:41:4e:c2:04 arrived on unexpected port 2/13 cnt 166674

Console> (enable) 2003 Oct 24 17:49:43 %SYS-4-P2_WARN: 1/Protocol Packet

DA=00:0c:41:4e:c2:04 SA=00:03:47:8f:c1:55 arrived on unexpected port 2/13 cnt 168946

2003 Oct 24 17:50:28 %SYS-4-P2_WARN: 1/Astro 2-2(2/9-16) - management request timed out.

2003 Oct 25 01:39:31 %SYS-4-P2_WARN: 1/Invalid crc on K1, dropped packet at buffer 487, count = 1

2003 Oct 25 01:39:58 %SYS-4-P2_WARN: 1/Astro 2-2(2/9-16) - management request timed out.

2003 Oct 25 01:40:12 %SYS-4-P2_WARN: 1/Blocked queue on gigaport 1, ( 0 : 1 )

2003 Oct 25 01:40:12 %SYS-4-P2_WARN: 1/Blocked queue (rx) on ports 2/9 2/10 2/11

2/12 2/14 2/13 2/15 2/16

2003 Oct 25 01:40:13 %SYS-4-P2_WARN: 1/Protocol Packet DA=01:00:5e:7f:ff:fa

SA=00:0c:41:4e:c2:04 arrived on unexpected port 2/13 cnt 1

2003 Oct 25 01:40:43 %SYS-4-P2_WARN: 1/Protocol Packet DA=01:00:5e:7f:ff:fa

SA=00:0c:41:4e:c2:04 arrived on unexpected port 2/13 cnt 129

2003 Oct 25 01:41:11 %SYS-4-P2_WARN: 1/Host 00:0c:41:4e:c2:04 is flapping between port 2/11 and port 2/13

2003 Oct 25 01:41:14 %SYS-4-P2_WARN: 1/Protocol Packet DA=01:00:5e:7f:ff:fa SA=00:0c:41:4e:c2:04 arrived on unexpected port 2/13 cnt 224

Help!

3 Replies 3

Prashanth Krishnappa
Cisco Employee
Cisco Employee

From the looks of it, it appears you are running into the following bug

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

Follow the steps listed in the bug and if it matches, you'll need to open a TAC case and RMA a switch.

Is there a code fix for this because we ran into this not too long ago on a 2948 and we have seen this on Cat4000's also . Is this strictly a hardware issue ?

6.4(7) has enhancements to flag switches exhibiting this symptom

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

Fix would be to replace hardware