 |
 |
On Fri, Dec 08, 2017 at 10:10:00PM +0000, Frank Bulk wrote: >Anyone else see this today with both MICE route reflectors? > >Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) >Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) >Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:44:36 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:45:23 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Which AS are you? No, but at the same time on the BIRD side we saw 2017-12-08 13:39:55NASN_26794: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 NASN_54578: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 NASN_32609: Received: Malformed AS_PATH: 400200 2017-12-08 13:39:55 NASN_22402: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 NASN_16842: Received: Malformed AS_PATH: 400200 2017-12-08 13:39:55 NASN_10242: Received: Malformed AS_PATH: 400200 Which in the past meant somebody had a cisco, and wasn't doing no bgp enforce-first-as as BIRD doesn't insert the MICE AS into the AS path, and that confuses Cisco devices. -- Doug McIntyre <[log in to unmask]> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades