Bug #11847
closedFilters not applied to PEER Groups
100%
Description
When creating a Peer group and adding an AS/Prefix filter or route map to the peer group, the generated configuration does not apply the filters to the peer group. Applying them directly to a peer does.
Expected Output
neighbor DEFAULT_PEERS peer-group
neighbor DEFAULT_PEERS description Default Peer Group
neighbor DEFAULT_PEERS prefix-list default-routes out
neighbor DEFAULT_PEERS filter-list default-as-filter out
neighbor DEFAULT_PEERS route-map set-local-pref in
Actual Output
neighbor DEFAULT_PEERS peer-group
neighbor DEFAULT_PEERS description Default Peer Group
Updated by Viktor Gurov about 4 years ago
Updated by Jim Pingle about 4 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho almost 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Updated by Alhusein Zawi almost 4 years ago
Prefix filter is not showing up in configuration file if there is no added neighbor
router bgp 61000
no bgp network import-check
neighbor peergrouptest peer-group
neighbor peergrouptest remote-as 61000
after adding neighbor:
router bgp 61000
no bgp network import-check
neighbor peergrouptest peer-group
neighbor peergrouptest remote-as 61000
neighbor 172.17.99.211 remote-as 61000
!
address-family ipv4 unicast
neighbor 172.17.99.211 activate
no neighbor peergrouptest send-community
neighbor peergrouptest prefix-list prefixtest in
neighbor peergrouptest prefix-list prefixtest out
no neighbor 172.17.99.211 send-community
exit-address-family
Updated by Azamat Khakimyanov over 2 years ago
- Status changed from Feedback to Assigned
- Assignee changed from Viktor Gurov to Jim Pingle
Tested on 22.05
I still see that filters are not applied to Peer group. But I don't think it's a Bug because:
1. I don't see any sense for having peer group without any members in it
2. when I added one member (BGP neighbor) to peer group I've created, filters immediately occurred in 'address-family ipv4 unicast' section. So having at least one member in peer group fixes this issue.
So as I understand, the reason for this behavior is that adding peer group into BGP config doesn't create 'address-family ipv4 unicast' section in Zebra/FRR configuration.
I would say we can close this Bug report.
Updated by Jim Pingle over 2 years ago
- Status changed from Assigned to Resolved
- Start date deleted (
04/23/2021) - % Done changed from 0 to 100