04-21-2010, 11:01 AM
BGP is very picky when it comes to taking network statements and advertising them. The network statement must EXACTLY match the routes as they appear in the routing table propagated by the IGP (unless synchronization is turned off). Perhaps Router B is not advertising a summary route but many different singular routes within the range of 192.168.12.0/22, If this is the case then you would either need network statements for each one or you would need to create a summary on Router A.
We already have a network statement which should inject a route into BGP and advertise it out to the neighbor if it can be found in the routing table propagated by an IGP or a static route. That is why this is the correct answer. Without seeing the routing table I can't tell you why the OSPF routes are not being picked up by BGP but its most likely because Router B is not sending them as a summary but instead individual subnets within that range. If that were true and you didn't want to create the static summary route then you would have to create network statements for each subnet as it appears in the routing table propagated by OSPF.
We already have a network statement which should inject a route into BGP and advertise it out to the neighbor if it can be found in the routing table propagated by an IGP or a static route. That is why this is the correct answer. Without seeing the routing table I can't tell you why the OSPF routes are not being picked up by BGP but its most likely because Router B is not sending them as a summary but instead individual subnets within that range. If that were true and you didn't want to create the static summary route then you would have to create network statements for each subnet as it appears in the routing table propagated by OSPF.