Page 1 of 1
BGP instance out-filter and BGP peer out-filter
Posted: Wed Aug 19, 2009 11:41 pm
by keefe007
What is the default behavior for handling situations where one is using both a BGP instance out-filter and a BGP peer out-filter. This used to work fine on 3.23 but now that I've upgraded to 3.28 I'm seeing some issues. It appears that the instance filter is not applied and I'm not able to tell if the peer filter was applied because the BGP session won't come up without the instance out-filter.
Keefe
Re: BGP instance out-filter and BGP peer out-filter
Posted: Fri Aug 21, 2009 11:53 am
by mrz
Instance filters are applied first and only then peer filters.
Re: BGP instance out-filter and BGP peer out-filter
Posted: Sun Apr 07, 2019 9:24 pm
by eduardomazolini
I was with the configuration below:
/routing bgp instance
set default as=XXXXXX client-to-client-reflection=no disabled=yes router-id=XXX.XX.68.X
add as=XXXXXX client-to-client-reflection=no name=VIVO out-filter=vivo-out router-id=XXX.XX.69.X routing-table=VIVO
add as=XXXXXX client-to-client-reflection=no name=NTT out-filter=ntt-out router-id=XXX.XX.70.X routing-table=NT
/routing bgp peer
add in-filter=vivo-in instance=VIVO name=vivo remote-address=XXX.XX.X.XXX remote-as=XXXXX1 ttl=default update-source=br-bgp
add in-filter=ntt-in instance=NTT name=ntt out-filter=ntt-out remote-address=XXX.XXX.XX.XX remote-as=XXXXXX2 ttl=default update-source=vlan2000-NTTurbo
The command below did not show:
/routing bgp advertisements> print
PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF
vivo xxx.xx.68.0/23 xxx.xx.x.xxx igp
vivo xxx.xx.68.0/24 xxx.xx.x.xxx igp
vivo xxx.xx.69.0/24 xxx.xx.x.xxx igp
ntt xxx.xx.68.0/22 xxx.xxx.xx.xx igp
ntt xxx.xx.70.0/24 xxx.xxx.xx.xx igp
BUT the output filter has not been applied to VIVO peer.
After confirming with VIVO that it was actually leaking the route I changed it by putting the out-filter in the peer.
/routing bgp instance
set default as=XXXXXX client-to-client-reflection=no disabled=yes router-id=XXX.XX.68.X
add as=XXXXXX client-to-client-reflection=no name=VIVO out-filter=vivo-out router-id=XXX.XX.69.X routing-table=VIVO
add as=XXXXXX client-to-client-reflection=no name=NTT out-filter=ntt-out router-id=XXX.XX.70.X routing-table=NT
/routing bgp peer
add in-filter=vivo-in instance=VIVO name=vivo out-filter=vivo-out remote-address=XXX.XX.X.XXX remote-as=XXXXX1 ttl=default update-source=br-bgp
add in-filter=ntt-in instance=NTT name=ntt out-filter=ntt-out remote-address=XXX.XXX.XX.XX remote-as=XXXXXX2 ttl=default update-source=vlan2000-NTTurbo
the command below did not change the displayed result.
/routing bgp advertisements> print
PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF
vivo xxx.xx.68.0/23 xxx.xx.x.xxx igp
vivo xxx.xx.68.0/24 xxx.xx.x.xxx igp
vivo xxx.xx.69.0/24 xxx.xx.x.xxx igp
ntt xxx.xx.68.0/22 xxx.xxx.xx.xx igp
ntt xxx.xx.70.0/24 xxx.xxx.xx.xx igp
I wonder if this was a bug? which error exactly? /system routerboard print
routerboard: yes
model: CCR1036-12G-4S
serial-number: XXXXXXXXXXXX
firmware-type: tilegx
factory-firmware: 3.27
current-firmware: 6.44.1
upgrade-firmware: 6.44.1