03-12-2010, 12:39 AM
Hello,
For the following question below you stated the correct answer is:
1. Subnets of 172.32.0.0/22 do not exist in the BGP table.
However they would exist in the BGP table because the aggregate-address command works similarly to the network command in BGP. It injects these routes into the BGP table but not the routing table. the problem is that there would not be a ">" mark next to those routes indicating that they are the best routes because BGP cannot find these routes in the routing table propagated by an IGP.
Thus the correct answer is:
5. The BGP command no synchronization is missing.
Please correct thanks!
Question:
59. (QID:NF58) During BGP configuration on a router that has peered with other BGP speakers, the BGP command "aggregate-address 172.32.0.0 255.255.252.0" is issued. However, the peers do not receive this aggregate network in BGP advertisements. Also, the router does not have this aggregate network in its BGP table. Which option indicates a possible reason this command did not cause the router to advertise the aggregate network to its peers?
1. Subnets of 172.32.0.0/22 do not exist in the BGP table.
2. The BGP command no auto-summary is missing.
3. Interface NULL 0 is likely shutdown.
4. The IGP running on this router does not have network 172.32.0.0/22 installed.
5. The BGP command no synchronization is missing.
6. The next hop IP address must be a loopback address.
For the following question below you stated the correct answer is:
1. Subnets of 172.32.0.0/22 do not exist in the BGP table.
However they would exist in the BGP table because the aggregate-address command works similarly to the network command in BGP. It injects these routes into the BGP table but not the routing table. the problem is that there would not be a ">" mark next to those routes indicating that they are the best routes because BGP cannot find these routes in the routing table propagated by an IGP.
Thus the correct answer is:
5. The BGP command no synchronization is missing.
Please correct thanks!
Question:
59. (QID:NF58) During BGP configuration on a router that has peered with other BGP speakers, the BGP command "aggregate-address 172.32.0.0 255.255.252.0" is issued. However, the peers do not receive this aggregate network in BGP advertisements. Also, the router does not have this aggregate network in its BGP table. Which option indicates a possible reason this command did not cause the router to advertise the aggregate network to its peers?
1. Subnets of 172.32.0.0/22 do not exist in the BGP table.
2. The BGP command no auto-summary is missing.
3. Interface NULL 0 is likely shutdown.
4. The IGP running on this router does not have network 172.32.0.0/22 installed.
5. The BGP command no synchronization is missing.
6. The next hop IP address must be a loopback address.