MSDP perring flaps

Alexander Istomin · ‎12-11-2017

Hello,

I have a strange problem with MSDP perring on my 3560 box, in logs i see:

059846: Dec 11 14:27:10.156 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going down
059847: Dec 11 14:27:23.091 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going up
059848: Dec 11 14:27:24.308 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going down
059849: Dec 11 14:27:37.419 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going up
059850: Dec 11 14:27:39.407 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going down
059851: Dec 11 14:27:51.957 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going up
059852: Dec 11 14:27:53.509 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going down
059853: Dec 11 14:28:06.352 MSK/MSD: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.1.1 going up

My MSDP peer is ASR9k, logs from there:

%ROUTING-MSDP-5-INIT_PEER_UP_DOWN : MSDP peer down: 192.168.1.2 bad TLV len %ROUTING-MSDP-3-IO_FAILED : I/O failure: bad len 8, Error code 3

What could be the cause of such messages "...bad TLV len..."?

vamikhai · ‎12-14-2017

Hello.

I would suggest to capture packets (on any device in the middle, but NO on any of the end-devices) for the MSDP session and check what is happening inside.