| 1 |
Ben Maddison taught me another aggregation trick: |
| 2 |
|
| 3 |
route-set: AS37271:RS-EXAMPLE |
| 4 |
mp-members: 192.0.2.0/27 |
| 5 |
mp-members: 192.0.2.32/27 |
| 6 |
mp-members: 192.0.2.64/27 |
| 7 |
mp-members: 192.0.2.96/27 |
| 8 |
mp-members: 192.0.2.128/26 |
| 9 |
mp-members: 192.0.2.128/27 |
| 10 |
mp-members: 192.0.2.160/27 |
| 11 |
mp-members: 192.0.2.192/27 |
| 12 |
mp-members: 192.0.2.224/27 |
| 13 |
descr: Example route-set |
| 14 |
mnt-by: MAINT-AS37271 |
| 15 |
changed: [email protected] 20210819 |
| 16 |
source: RADB |
| 17 |
|
| 18 |
BGPQ4 produces the following: |
| 19 |
|
| 20 |
$ bgpq4 -A AS37271:RS-EXAMPLE |
| 21 |
no ip prefix-list NN |
| 22 |
ip prefix-list NN permit 192.0.2.0/25 ge 27 le 27 |
| 23 |
ip prefix-list NN permit 192.0.2.128/26 le 27 |
| 24 |
ip prefix-list NN permit 192.0.2.192/26 ge 27 le 27 |
| 25 |
|
| 26 |
But the following aggregation also is valid, and shorter: |
| 27 |
|
| 28 |
ip prefix-list NN permit 192.0.2.0/24 ge 27 le 27 |
| 29 |
ip prefix-list NN permit 192.0.2.128/26 |