Skip to main content
edited tags
Link
Ron Maupin
  • 101.1k
  • 26
  • 123
  • 199
Tweeted twitter.com/StackNetworkEng/status/1148562596586512384
deleted 7 characters in body
Source Link
Teun Vink
  • 17.4k
  • 6
  • 45
  • 70

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device
router bgp 65001
bgp log-neighbor-changes
network 8.1.5.0 mask 255.255.255.252
network 8.1.7.0 mask 255.255.255.252
network 8.8.8.2 mask 255.255.255.255
network 17.1.2.0 mask 255.255.255.252
neighbor 8.1.7.2 remote-as 65002
neighbor 8.8.8.3 remote-as 65001
neighbor 8.8.8.3 update-source Loopback0

router bgp 65001
 bgp log-neighbor-changes
 network 8.1.5.0 mask 255.255.255.252
 network 8.1.7.0 mask 255.255.255.252
 network 8.8.8.2 mask 255.255.255.255
 network 17.1.2.0 mask 255.255.255.252
 neighbor 8.1.7.2 remote-as 65002
 neighbor 8.8.8.3 remote-as 65001
 neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

Lab setup

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device
router bgp 65001
bgp log-neighbor-changes
network 8.1.5.0 mask 255.255.255.252
network 8.1.7.0 mask 255.255.255.252
network 8.8.8.2 mask 255.255.255.255
network 17.1.2.0 mask 255.255.255.252
neighbor 8.1.7.2 remote-as 65002
neighbor 8.8.8.3 remote-as 65001
neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

Lab setup

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device

router bgp 65001
 bgp log-neighbor-changes
 network 8.1.5.0 mask 255.255.255.252
 network 8.1.7.0 mask 255.255.255.252
 network 8.8.8.2 mask 255.255.255.255
 network 17.1.2.0 mask 255.255.255.252
 neighbor 8.1.7.2 remote-as 65002
 neighbor 8.8.8.3 remote-as 65001
 neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

Lab setup

Adding the lab setup, need to add the configs when I'm back at my desk
Source Link

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device
router bgp 65001
bgp log-neighbor-changes
network 8.1.5.0 mask 255.255.255.252
network 8.1.7.0 mask 255.255.255.252
network 8.8.8.2 mask 255.255.255.255
network 17.1.2.0 mask 255.255.255.252
neighbor 8.1.7.2 remote-as 65002
neighbor 8.8.8.3 remote-as 65001
neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

Lab setup

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device
router bgp 65001
bgp log-neighbor-changes
network 8.1.5.0 mask 255.255.255.252
network 8.1.7.0 mask 255.255.255.252
network 8.8.8.2 mask 255.255.255.255
network 17.1.2.0 mask 255.255.255.252
neighbor 8.1.7.2 remote-as 65002
neighbor 8.8.8.3 remote-as 65001
neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

I don't know what I should be using for this or how I should go about it.

In my lab where I am testing out the BGP configs that I've learned I want my ISP topology to have a summary prefix for the Customer to see. I am peering with eBGP to the customer with 3 links. 8.1.7.0 /30 1 - 20 are allocated to this Customer for their WAN links.

ISP has BGP built over an OSPF underlay and is peering with loopbacks

Customer is using EIGRP for IGP
On the Customer's ASBRs the only advertised address is 17.1.2.0 /24
The addresses is aggregated after being redistributed into BGP

These are my configs for BGP on the ISP CE device
router bgp 65001
bgp log-neighbor-changes
network 8.1.5.0 mask 255.255.255.252
network 8.1.7.0 mask 255.255.255.252
network 8.8.8.2 mask 255.255.255.255
network 17.1.2.0 mask 255.255.255.252
neighbor 8.1.7.2 remote-as 65002
neighbor 8.8.8.3 remote-as 65001
neighbor 8.8.8.3 update-source Loopback0

I think I can remove the #network 17.1.2.0 command since I aggregated the route on another BGP device

When it comes to summarizing all my 8.0.0.0 /8 prefixes to AS65002 I can't figure out how. I'm pretty new to using route-maps and prefix lists and that's what I was trying to use for this project.

Lab setup

edited tags
Link
Ron Maupin
  • 101.1k
  • 26
  • 123
  • 199
Loading
Source Link
Loading