Re: IGP(OSPF) learned route not used for iBGP?

[Nico Schottelius via Bird-users]

Hello Maria,

Maria Matejka via Bird-users <bird-users@network.cz> writes:
> Could you please disclose what "show interfaces" writes out?

Sure:

[18:59] apu-router1.place5:~# birdc
BIRD 2.0.12 ready.
bird> show interfaces
lo up (index=1)
        MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536
        127.0.0.1/8 (Preferred, scope host)
        2a0a:e5c0:1e:a::b/128 (Preferred, scope univ)
        2a0a:e5c0:1e:a::a/128 (scope univ)
        2a0a:e5c0:0:a::b/128 (scope univ)
        2a0a:e5c0:0:a::a/128 (scope univ)
        2a0a:e5c0::4/128 (scope univ)
        2a0a:e5c0::3/128 (scope univ)
        2a0a:e5c0::1/128 (scope univ)
        ::1/128 (scope host)
eth0 down (index=2)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
eth1 up (index=3)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        fe80::20d:b9ff:fe57:2f91/64 (Preferred, scope link)
eth2 up (index=4)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0:0:b::46/64 (Preferred, scope univ)
        fe80::20d:b9ff:fe57:2f92/64 (Preferred, scope link)
eth1.5 up (index=5)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0:0:6::46/64 (Preferred, scope univ)
        fe80::20d:b9ff:fe57:2f91/64 (Preferred, scope link)
eth1.2 up (index=7)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0::46/64 (Preferred, scope univ)
        fe80::20d:b9ff:fe57:2f91/64 (Preferred, scope link)
eth1.7 up (index=8)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0:0:3::46/64 (Preferred, scope univ)
        fe80::20d:b9ff:fe57:2f91/64 (Preferred, scope link)
eth1.41 down (index=9)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
bird>

and server138:

bird> show interfaces
lo up (index=1)
        MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536
        127.0.0.1/8 (Preferred, scope host)
        ::1/128 (Preferred, scope host)
eth0 up (index=2)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0::3eec:efff:fed2:d0c2/64 (Preferred, scope univ)
        fe80::3eec:efff:fed2:d0c2/64 (Preferred, scope link)
eth1 down (index=3)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
eth2 up (index=4)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0:0:b::8a/64 (Preferred, scope univ)
        fe80::3eec:efff:fed2:d0c4/64 (Preferred, scope link)
eth3 down (index=5)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
eth4 down (index=6)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
eth5 up (index=7)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        192.168.1.210/24 (Preferred, scope site)
        fe80::3eec:efff:fed2:d0c7/64 (Preferred, scope link)
eth6 down (index=8)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
eth7 down (index=9)
        MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500
k8sbr0 up (index=10)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        2a0a:e5c0:43:aa::1/64 (Preferred, scope univ)
        fe80::f84f:6ff:fe68:c858/64 (Preferred, scope link)
vethaeaa6a09 up (index=11 master=k8sbr0)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        fe80::d4d3:54ff:fe67:a40b/64 (Preferred, scope link)
veth30d9aa51 up (index=12 master=k8sbr0)
        MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
        fe80::ac8c:8fff:fe7c:4404/64 (Preferred, scope link)
s138s121 up (index=28)
        PtP Multicast AdminUp LinkUp MTU=1420
        2a0a:e5c0:32:2::22/124 (Preferred, scope univ)

Does this explain it?

Best regards,

Nico

--
Sustainable and modern Infrastructures by ungleich.ch