I have a customer that we configured over our MPLS backbone. I don't spend enough time in the BGP realm to claim to be an expert. When using EIGRP and static routes, its only necessary under the router eigrp statement to list the directly connected subnets and the redistribute the statics. I found out today with BGP, that you list the subnets under the router bgp statement that you have created static routes for instead of using redistribute static. Why is BGP designed this way? The question might be rhetorical. The remote.txt has the static routes in it.
2) Advertise out the /25 subnets under your BGP config.
3) Advertise the classful 192.168.2.0 network without the mask keyword and then any route for the major network or one of its subnets of 192.168.2.0 that may already exist in the IP routing table would suffice to advertise the class C address. In other words, an exact match is only needed if the mask keyword is used to advertise a classless route.
You don't have to use the network statement to bring those routes into BGP, you still can do a "redistribute static" like other routing protocols.
There are a few differences, though.
First, if you do not filter on the redistribution, it will pull all of your statics into BGP, whereas with network statements, only the ones you specify will be pulled in (as long as those networks listed on the network statements are in the RIB).
Second, routes brought into BGP via the network statement will be listed with an origin of i (IGP) whereas netowrks brought in via redistribution will have an origin of ? (incomplete). In many networks, that difference is not much of a concern.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...