ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

High collision or drop rate.

Leighton
Visitor

High collision or drop rate.

Hi,

I am currently troublehshooting an issue which cause my core switch 2 down and unresponsive.  The model is ProCurve J8697A Switch 5406zl.  Upon seeing the logs, I notice these errors:

I 02/14/17 12:55:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21707)
I 02/14/17 12:47:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348678)
I 02/14/17 12:38:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21673)
I 02/14/17 12:30:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348644)
I 02/14/17 12:21:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21639)
I 02/14/17 12:13:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348610)
I 02/14/17 12:04:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21605)
W 02/14/17 12:00:20 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:56:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348576)
W 02/14/17 11:54:43 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:47:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21571)
W 02/14/17 11:40:39 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:39:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348542)
I 02/14/17 11:30:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21537)
W 02/14/17 11:29:23 00331 FFI: port C16-High collision or drop rate. See help.
W 02/14/17 11:23:46 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:22:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348508)
W 02/14/17 11:18:08 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:13:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21503)
W 02/14/17 11:12:30 00331 FFI: port C16-High collision or drop rate. See help.
W 02/14/17 11:06:53 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 11:05:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348474)
I 02/14/17 10:56:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21469)
I 02/14/17 10:48:56 00828 lldp: PVID mismatch on port 55(VID 0)with peer device
port 25(VID 1)(348440)
W 02/14/17 10:47:11 00331 FFI: port C16-High collision or drop rate. See help.
I 02/14/17 10:39:32 00828 lldp: PVID mismatch on port 72(VID 0)with peer device
port 71(VID 1)(21435)

I have check the speed duplex setting are correct.  Any idea how can I check on the high colllision and drop rate?

I have also notice that the switch was rebooted by itself and shown the message in the logs:

System went down: 02/14/17 09:41:42
Saved crash information:
Software exception in ISR at btmDmaApi.c:370
-> ASSERT: No resources available!

Any idea what is this?

Appreciate if anyone would help.  Thanks!

Best Regards,
Leighton

7 REPLIES
parnassus
Honored Contributor

Re: High collision or drop rate.

You seem to have 3 different issues:

(1) LLDP PVID mismatch

(2) High Collision or Drop rate

(3) Software exception in ISR at btmDmaApi.c

First, is you Switch equipped with dual Management Modules?

Try to provide show log -s -r -a, show flash and show version commands' outputs.

Regarding (3): are you running an old software version with respect to what is available now? if the answer is a sound Yes, please - do yourself a favour - upgrade!

Regarding (1): the logged "PVID mismatch on port N (VID 0) with peer device port M (VID 1)" warning requires that you examine what is connected (and in which way it is) on stated ports (respectively N = 55 and 72 and M = 25 and 71 in your logs) and which is the PVID configuration on those ports (on both ends).

See here (an explanation of the issue) and here (mismatch fix solution and also a workaround), discussed also in HPE Community here (just for the workaround part): is a port's configuration mismatch, so port's configuration must be corrected.

Regarding (2): a show config (and show interfaces too) would be benefical to diagnose what's happening. A basic network topology diagram (or a clear description of it) would be too...especially because you only know what is connected to Port C16 of your Switch (have you checked for Speed/Duplex mismatches on that port?).

Leighton
Visitor

Re: High collision or drop rate.

Thank for the advice! Will check on those.

One question, for the LLDP PVID mismatch.  Its is showing port 55 mismatch with port 71.  My ports are C1-C24 or E1-E24,  how I do know port 55, 71 are which port?

parnassus
Honored Contributor

Re: High collision or drop rate.

I was wondering that, too: I'm used to Letter (slot) + Module's port numbering (n), especially speaking about ProCurve modular chassis Switch series, so - I guess - if Module in Slot A is equipped with a 24 ports module, I think its absolute chassis ports numbering would be 1-24, then another Module in Slot B is equipped with another 24 ports module its consequent chassis ports numbering would be 25-48...and so on...but, mine, is just an (un)educated guess.

Arimo
Respected Contributor

Re: High collision or drop rate.

This really looks like a stone-age SW version. I'd recommend upgrading to current Maintenance Release K.15.16.0016m before you even try to resolve problems.


HTH,

Arimo
HPE Networking Engineer
parnassus
Honored Contributor

Re: High collision or drop rate.


Arimo wrote: This really looks like a stone-age SW version.

;-)

Probably the OP's Switch is running something like K.15.0x...

Arimo
Respected Contributor

Re: High collision or drop rate.

I snooped around a bit, I think it's K.14...


HTH,

Arimo
HPE Networking Engineer
parnassus
Honored Contributor

Re: High collision or drop rate.

Gosh! if true...it recalls me a consideration I did (some will say: once it runs, don't touch it).