Catalyst 4006 System Message 1

[frankie2]

We have about 12 Catalyst 4006's connected to redundant 6509's. Here is the output of show logging buffer on a 4006:
%sys-4-p2_warn: 1/invalid crc, dropped packet, count=36664 (and growing). One other switch has the same error but the count is much smaller. Both segments are very sluggish but all the other 4006's are operating normally. Resetting the switches seemed to have cured the issue. I can't find this error on the Cisco website. Any suggestions?

 

[rburke]

Well, it seems as if there were CRC errors so it was dropping the packets. This *usually* has to do with a cabling or physical layer probelm, since what it really means is that there have been some bits in the original message that were changed during transmission. But along the same lines, it could have been a synchronization error and the reset fixed it, or at worst it could be a bad port causing the errors.

I would watch it and see if the errors come back up. If they do then try replacing cabling, and work up from there. Start with the easy stuff and then move up to the harder/expensive stuff.

Hope this helps... Let me know...

Burke

 

[cbeauchamp]

Hi,

I have also run into the same issue and I called Cisco. They are aware of this problem and it is a faulty supervisor module. They are sending me a replacement. The Bug ID is CSCDY46288.

Cheers.

 

[unable24]

My client has many 4006's, and we are seeing the same problem. About once a month, we get reports that users on a switch are seeing slow performance or losing their network connection - in the switch log we are seeing "SYS-4-P2_WARN: 1/Invalid crc, dropped packet" - and the only fix is a hard reboot. We have not seen a repeat of the event on any switch that has been rebooted, but we have seen about 8 4006's hang because of the bug over a period of 6 months. Cisco is siting bug CSCdy46288, but you cannot find this bug on their bug toolkit (hhmmm???). We shipped a Sup module from one of our affected switches to Cisco for evaluation, but the TAC said is was fine. I don't think they have a fix, and I don't think they know if it is hardware or software (we have seen the bug on 5-5-13a and 6-3-5).

CBeauchamp - where are you hearing it is a bad Sup? Cisco is still telling us they don't have a clue....

 

[IPKONFIG]

It's a SUP problem. My company has about 90 or so 4000 series switches. We've had this problem too, and replacing the SUPs fixes all issues. Cisco is aware. Some TAC engineers are not.

 

[cbeauchamp]

Sorry for the delay, I agree I was not able to find the bug online but the engineer did quote that number. Anyway, I replaced the module and all seems well.

I am monitoring the other 4006 that we have that was deployed at the same time but does not have the same amount of traffic, therefore I assume will not show the problem as quickly.

One other symptom I noticed is that the faulty sup module would not reset via command line, the module would not complete all tests and therefore fail. To get it going, I needed to pull all power plugs and the reset them.

Regards,

Chris Regards

 

[Ginjaj]

Hi there, I have the same error message on a 4006 running microcode 6-3-5.
This would not be much of an issue, as I am currently only getting 1 CRC error msg ever 10 mins or so. Thing is, there is only one server on the switch at the moment, and that is turned off at the moment.

The problem I do have though is that when the server was patched, and up they were getting very poor response times, timeouts etc. I went to investigate the problem and found something very peculier. Blade 2 is a 48 port RJ-45, and all ports are configured for VLAN 109, and the default gateway is up.

I could ping the DG from say port 2/14, but when I tried from another port I could not ping the DG. I even had two laptops ping'ing simultaneously each other, and the DG. They would ping each other, and one would be able to ping the DG, and the other not. I know what your thinking now, he must have a mask wrong or something?!?!
But I assure you not.

I tried moving ports and some would ping the DG and others wouldn't.....then all of a sudden they would, and then maybe they wouldn't....all in all a very intermitant.

I was wondering whether or not this was inline with what other people were seeing, or if this is completely unrelated. I have raised a change to reboot the box tomorrow, and so should see whether or not this resolves the issue. Any comments would be very much apprecitated though!!!

Jason

 

[cbeauchamp]

Hi,

The CRC error appears every 10 mins. When I was experiencing the problem, it did seems to be specific to a VLAN but it did start to show up on other VLANs.

Anyway, I would highly recommend that you call Cisco before your switch/servers are in production and highly utilized.

Regards,

Chris

Regards