Open elaine-oxide opened 3 months ago
Similar issue for bgp peer set with peer address not already in use but different asn than is already in use. That is, there doesn't already have to be an existing use of the peer address for this issue to appear during bgp peer set, as long as a different asn is used.
I am running a4x2 with:
1059fe109fadbccf559e4adad134eaffcb67b85a
Initial state:
I created a fake peer for address not yet used as a peer address with the ASN already in use by the existing peers.
Resulting state after above command (I see
169.254.60.1
has appeared in the output):Now I try to create/set (another/same) fake peer to use an ASN not already in use by the existing peers.
Resulting state after above command (I see
169.254.60.1
has disappeared from the output of the first command, butas65548
has appeared in the output of the second command):I performed the same set of operations on my real peer
169.254.40.1
, and it had the same behavior.Initial state:
Try to create/set with same address as existing real peer, different ASN.
Resulting state after above command:
Try to create/set with same address as existing real peer, same real ASN that was previously in use.
Resulting state (
169.254.40.1
now using 65547 andas65547
):For reference, here is the ASN information:
Resulting state:
On g3 (switch1):
And for reference, on g0 (switch0):