Hello, in VIRL i have configured a network that pretty much looks identical and acts just like our prod network. The drawing I have attached pretty much encompasses everything that is in prod and in my configs in VIRL.
So I'm having an issue of confusion of where I should place the default-information originate or network 0.0.0.0/0 or redistribution command in my full iBGP mesh. These cores are peer-linked VPC cores that both need to be able to send all traffic bound to the Datacenter(from the branches) to the firewall, then eventually to the internet. The way this is setup in VIRL, when a branch pops up, the route for that branch nativiley falls into the WRs and cores routing table because they learn it via BGP....so if I'm on the core and I want to get to a branch it works because the routes are there. The problem is the branches knowing about routes on the cores. So pretty much all branches must go up to the core to be able to do anything. there is nothing attached to the WR1/2 except the cores...so all traffic must go toward the cores to get anywhere. So I'm thinking that since the cores have a static default route to the firewall because most of all traffic is bound that way anyways, why not just have the cores advertise the "network 0.0.0.0/0" so that they advertise the default to the rest of the BGP domain so all branches must follow that default route that way to the get to the firewall. I was wondering if anyone could think of a reason of this being a problem.
Example: on core 1, there is a “random router” that talks to the core via EIGRP and the other random router off core 2 doesent do EIGRP but just has a static route to point back to the core. I’m wondering if I put the network command 0.0.0.0/0 under both cores for the BGP process, would that cause any routing loop problems?
Please let me know if this is confusing and more clarification is needed. Thank you in advance
