VSLP-SW1-4-LMP_PAK_LOSS

[abhisar patil]

Dear Team,

I am getting following error on one of the port of VSL, the link is up. What may be the reason?

Nov 27 23:33:16.829: %VSLP-SW1-4-LMP_PAK_LOSS: 13 VSLP Hello Packets dropped on interface Te1/3/5 in 180 seconds
Nov 28 11:24:34.465: %VSLP-SW1-4-LMP_PAK_LOSS: 13 VSLP Hello Packets dropped on interface Te1/3/5 in 180 seconds

Thank You,

Abhisar

[InayathUlla Sharieff · Accepted solution]

Abhisar,

%VSLP-SW1-4-LMP_PAK_LOSS: 13 VSLP Hello Packets dropped on interface

Explanation:
============
LMP_PAK_LOSS, VSLP, LOG_WARNING, 0, "VSLP Hello Packets dropped on interface
%s in %d seconds"

Explanation - VSLP Hello packets are getting dropped. This does not
necessarily mean VSL link will go down. This could be due to bad
transceiver/cable. Please check the interface status (show interface) of the
VSL link and look for CRC errors to confirm this.

Recommended action is to check and replace the bad transceiver/cable

++LMP is the protocol that maintains the keepalives on the VSL and ensures
that it is up and running and exchanges periodic hellos between the chassis.
Occasional occurrence of these logs do not imply data loss/ impact on the
VSS operation. 

HTH

Regards

Inayath

[abhisar patil]

Dear Suresh/Inayath,

Thank you for your comments. I can see some errors on both the ports in VSL. I have opened the TAC case as well and will change the cables as well.

Switch#show interfaces te1/3/4
TenGigabitEthernet1/3/4 is up, line protocol is up (connected)
  Hardware is C6k 10000Mb 802.3, address is 3c08.f622.2540 (bia 3c08.f622.2540)
  Description: ****MEMBER OF PORTCHANNEL 1 - NEVER SHUTDOWN THIS PORT****
  MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 10Gb/s, media type is 10Gbase-SR
  input flow-control is on, output flow-control is off
  Clock mode is auto
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 405000 bits/sec, 141 packets/sec
  5 minute output rate 92000 bits/sec, 70 packets/sec
  L2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
  L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
  L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
     48470447 packets input, 17678109375 bytes, 0 no buffer
     Received 42264396 broadcasts (34814089 multicasts)
     0 runts, 6733720 giants, 0 throttles
     200899 input errors, 200899 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     46212090 packets output, 11815665795 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Switch#show interfaces te1/3/5
TenGigabitEthernet1/3/5 is up, line protocol is up (connected)
  Hardware is C6k 10000Mb 802.3, address is 3c08.f622.2540 (bia 3c08.f622.2540)
  Description: ****MEMBER OF PORTCHANNEL 1 - NEVER SHUTDOWN THIS PORT****
  MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 249/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 10Gb/s, media type is 10Gbase-SR
  input flow-control is on, output flow-control is off
  Clock mode is auto
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 386000 bits/sec, 109 packets/sec
  5 minute output rate 3000 bits/sec, 2 packets/sec
  L2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
  L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
  L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
     35148288 packets input, 10371022385 bytes, 0 no buffer
     Received 29397725 broadcasts (22747307 multicasts)
     1 runts, 2489499 giants, 0 throttles
     769641 input errors, 769641 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     22401151 packets output, 5913336762 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

[InayathUlla Sharieff]

Abhisar,

Thanks for the update. Yes it would be worth changing the cable. AS I see many input errors and CRC which is usually Layer 1 issue.

- Change the cable first and have the counter checked. 

- In case after changing the cable still you see these counters(input/crc) increasing try changing the port at both the ends.

HTH

[abhisar patil]

Dear Inayat,

Thank you.

I have changed the cable and seems it is fine.

Thank You,

Abhisar.

[smanne]

I'm getting the same error periodically, But i'm not seeing any errors and its showing that CRC count is zero. Is it still with the Physical layer, Do i need to care about the similar log message if i don't see any errors in the show interface output.

[Suresh Vinayagam Subramanian · Accepted solution]

Dear Abhisar,

Can you check the interface 1/3/5 status . I guess, you would see some errors on that interface. If you see errors then you need to check the physical layer to clear the issue.

HTH

Regards,

VS.Suresh.

*Plz rate the usefull posts *