Thank you for correcting the diagram, now it is applicable. : )
The
as-override
option is my preferred one, since it avoids you accepting looping ASN inbound for all sessions globally, and the as-override is applicable to a single peer, so it scope is not as wide as accepting looping ASN from all peers. The looping option is good when there is a stub connection, usually.
Elvin
Original Message:
Sent: 09-15-2021 23:02
From: Unknown User
Subject: How to deal with AS Loop in my topology ?
If I have the following topology:
bgp.evpn.0: 27 destinations, 43 routes (22 active, 0 holddown, 21 hidden)2:192.168.1.3:3::10::00:05:86:71:dc:03/304 MAC/IP (2 entries, 0 announced) BGP /-101 Route Distinguisher: 192.168.1.3:3 Next hop type: Indirect, Next hop index: 0 Address: 0xc6341b0 Next-hop reference count: 20 Source: 192.168.1.44 Protocol next hop: 192.168.1.3 Indirect next hop: 0x2 no-forward INH Session ID: 0x0 State: <Hidden Int Ext> Local AS: 65535 Peer AS: 64511 Age: 2:40 Metric2: 0 Validation State: unverified Task: BGP_64511_64511.192.168.1.44+179 AS path: 65535 I Communities: target:10:10 encapsulation:vxlan(0x8) Import Route Label: 10 ESI: 00:00:00:00:00:00:00:00:00:00 Localpref: 100 Router ID: 192.168.1.44 Hidden reason: AS path loop Secondary Tables: vpn1.evpn.0 Indirect next hops: 1 Protocol next hop: 192.168.1.3 Metric: 0 Indirect next hop: 0x2 no-forward INH Session ID: 0x0 Indirect path forwarding next hops: 1 Next hop type: Router Next hop: 10.20.1.1 via ge-0/0/5.0 Session Id: 0x140 192.168.1.3/32 Originating RIB: inet.0 Metric: 0 Node path count: 1 Forwarding nexthops: 1 Nexthop: 10.20.1.1 via ge-0/0/5.0 Session Id: 140
How to avoid this AS loop ?
as-override ?
family inet unicast loops 1 ?
Where is the best place to apply this ?
thanks !!