I have MPLS running between two sites (testing a VPLS tunnel) and noticed that when checking the ldp neighbor status on router R2 it shows all local addresses that are configured on router R1 (and v.v.):
R2:
Code: Select all
[admin@R2] /mpls ldp neighbor print
Flags: X - disabled, D - dynamic, O - operational, T - sending-targeted-hello, V - vpls
0 DO transport=10.255.255.1 send-targeted=no peer=10.255.255.1:0 local-transport=10.255.255.2
addresses=10.0.0.1,10.0.0.5,10.235.x.x,10.255.255.1,86.x.x.x,192.168.10.1,192.168.60.1,192.168.80.1,192.168.88.1,192.168.130.1,
192.168.140.1,192.168.150.1,192.168.254.2
I have routing filters in place (OSPF) that only advertise certain routes and discard all others.
R1 routing filters:
Code: Select all
[admin@R1] > /routing filter print where chain=r2-out
Flags: X - disabled
0 chain=r2-out prefix=192.168.10.0 prefix-length=24-32 invert-match=no action=accept set-bgp-prepend-path=""
1 chain=r2-out prefix=192.168.130.0 prefix-length=24-32 invert-match=no action=accept set-bgp-prepend-path=""
2 chain=r2-out prefix=10.0.0.4 prefix-length=30-32 invert-match=no action=accept set-bgp-prepend-path=""
3 chain=r2-out prefix=10.255.255.1 prefix-length=32 invert-match=no action=accept set-bgp-prepend-path=""
4 chain=r2-out invert-match=no action=discard set-bgp-prepend-path=""
Is it normal behaviour to always show all local addresses from an ldp neighbour, or can these be filtered out?