Hi,

I testing an RB450G interoperability on our cisco based network and i see exactly six times "Invalid MD5 digest" messages on our cisco router log after every RB450G (re)boot and after it successfully authenticated the BGP session:

LC/0/0/CPU0:Jun 30 10:18:30.139 MET_DST: ifmgr[186]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/20, changed state to Up
RP/0/RSP0/CPU0:Jun 30 10:18:30.168 MET_DST: ospf[1011]: %ROUTING-OSPF-5-ADJCHG : Process 100, Nbr a.b.c.d on GigabitEthernet0/0/0/20 in area 0 from LOADING to FULL, Loading Done,vrf default vrfid 0x60000000
RP/0/RSP0/CPU0:Jun 30 10:18:32.168 MET_DST: ospfv3[1030]: %ROUTING-OSPFv3-5-ADJCHG : Process 100, Nbr a.b.c.d on GigabitEthernet0/0/0/20 from LOADING to FULL, Loading Done
RP/0/RSP0/CPU0:Jun 30 10:18:33.763 MET_DST: mpls_ldp[1042]: %ROUTING-LDP-5-ADJ_CHANGE : Adjacency (a.b.x.y) UP with Nbr a.b.c.d:0 on GigabitEthernet0/0/0/20
RP/0/RSP0/CPU0:Jun 30 10:18:40.080 MET_DST: bgp[1047]: %ROUTING-BGP-5-ADJCHANGE : neighbor a.b.c.d Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 10:18:43.405 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122
RP/0/RSP0/CPU0:Jun 30 10:19:21.807 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122
RP/0/RSP0/CPU0:Jun 30 10:20:21.809 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122
RP/0/RSP0/CPU0:Jun 30 10:21:21.810 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122
RP/0/RSP0/CPU0:Jun 30 10:22:21.812 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122
RP/0/RSP0/CPU0:Jun 30 10:23:21.814 MET_DST: tcp[395]: %IP-TCP-3-BADAUTH : Invalid MD5 digest from a.b.c.d:179 to a.b.c.e:64122

Any idea why sends RoS further BGP "Invalid MD5 digest" after (re)boot? If I only shutdown/no shutdown the peering on any side then i can't see these messages.
I use RoS 5.18

Cheers,
oreggin