3/21/2024 0 Comments Cisco ping source loopback![]() ![]() Set protocols bgp 65018 address-family ipv4-unicast redistribute connected Set interfaces loopback lo address 10.254.18.1/32 R18 config: set interfaces ethernet eth0 address 10.10.18.1/30 Set protocols bgp 65001 address-family ipv4-unicast redistribute connected Set interfaces loopback lo address 10.254.1.1/32 R1 config: set interfaces ethernet eth0 address 10.10.18.2/30 ![]() R1 and r18 ethernet connected between eth0 and eth0 Here are pictures for version 2 of the same lab. (so 217 is the RR for iBGP, and all other router just have it as a neighbor). Just take the same scheme of «version 1», remove RFI1, and take 217 as its replacement )Įven more, just because RFI1 is a REAL production router, for a while I used a smaller set of devices. Moreover: IF the chain is ONLY of extreme switches, everything works perfectly (still using RFI1, a cisco device, as RR. Loopback interface of each other switch/router as the destination, we have: To be more specific, if we look at «version 1» of the test, if we try to ping from RFI1 using the iBGP loopback interface as source, and the iBGP ![]() (we tried to «switch» between cisco models, but nothing changed). The «guilty device» is the FIRST cisco switch/router, no matter which model it is (and from that one, nothing works, like in a chain) The cause seems to be the fact that as soon as I enable the MPLS routing, I loose the reachability of the iBGP loopback interface, and from there I loose the iBPG neighborship.Īnd here is the MOST interesting part: the ISSUE is NOT everywhere, but just from a device
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |