we're getting a %TCP-6-BADAUTH every minute on 3 routers in our BGP peer group. All the routers are configured with the same peer group settings and for the routers in question the other peers in the same peer group work fine.
%TCP-6-BADAUTH: No MD5 digest from br4.bne:23665 to xr1.bne:179
%TCP-6-BADAUTH: No MD5 digest from br1.wic:41833 to xr1.wic:179
%TCP-6-BADAUTH: No MD5 digest from xr2.bne:18105 to br4.bne:179
I've trimmed down the message and replaced the ip addresses with names.
Each line is from a different router (xr1.bne, xr1.wic, br4.bne).
The xr routers are route-reflector servers and all other routers are route-reflector clients.
I've tried a 'clear ip bgp A.B.C.D' on the affected routers and it doesn't seem to fix the problem.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.