remaining part of this quesiton.

After this configuration, ISP-1 and ISP-2 continue to receive the specific routes and the summary route.
Which configuration resolves the issue?

https://www.examtopics.com/discussions/c...iscussion/

Per the link in the explanation.

"The weight is assigned locally to the router. The value only makes sense to the specific router."



"Unlike the weight attribute, which is only relevant to the local router, local preference is an attribute that routers exchange in the same AS."

Changing the weight on another router will not impact forwarding decisions made by this router.

Exhibit is wrong.

question references AS64501 exhibit uses AS100,AS200, AS300.

https://www.examtopics.com/discussions/c...iscussion/

Missing Diagram Portion of exhibit


https://www.scribd.com/document/65704362...-2023-v1-2

Exhibit is incorrect 

Table shows device id's as ASBR 2,3,4

Diagram shows ASBR 1,2,3

Who is to say the misconfiguration isn't on e0/1 of Cape Town?

CapeTown#sh ip route | inc 192.168.1.0
D    192.168.1.0/24 [90/665600] via 192.168.12.1, 00:00:05, Ethernet0/0
CapeTown#
CapeTown#

CapeTown#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
CapeTown(config)#int e 0/1
CapeTown(config-if)#band 10000
CapeTown(config-if)#end
CapeTown#
CapeTown#
CapeTown#
*Feb 18 04:29:55.827: %SYS-5-CONFIG_I: Configured from console by console
CapeTown#
CapeTown#
CapeTown#sh ip route | inc 192.168.1.0
D    192.168.1.0/24 [90/435200] via 192.168.13.2, 00:00:05, Ethernet0/1
CapeTown#

The Router-ID is the tie breaker in the AS Path Selection. Path 6 wins because of its lowest Router-ID. Path 5 (RID 10.77.255.57) comes in second.

1. Weight - not a factor... no option mentions weight
2. Local Preference - Same value (100) on all paths
3. Origin Code - Same value (learned) on all paths.
4. Path Length - Same on all devices (1) an AS_Set counts as one
5. Origin ID - Same on all Devices (IGP)
6. MED - Same on all devices (0)
7. Prefer eBGP over iBGP - all paths are internal There is no distinction between Conferderation External and Confederation Internal.
8. IGP Metric - Same value (20645) on all paths.
9. Multipath - not used
10. if both paths are external, choose oldest path. not used
11. Lowest Router-ID Path 6 wins,  Path 5 is second.

Changing the Local_Pref could have the desired effect but the wording is incorrect.  Lowering the LOCAL_PREF does not select AS THE BEST PATH, you would need to raise the LOCAL_PREF for this to happen.  

Prepending the AS_PATH for the current best path would move path 6 from first to worst.  Path 5 would become the new best path. 

https://www.cisco.com/c/en/us/support/do...753-25.pdf

Only Allow Networks that Originate from AS 4 to Enter Router 1


Placing 'ip as-path access-list 1 permit ^111$ on ISP-1 only allows ISP-1 to receive routers from AS111.  


See example from 
https://www.cisco.com/c/en/us/support/do...1227473857


If you would like for Router 1 to receive only the routes originated from AS 4 (and no Internet routes), you can apply an inbound access list on Router 1:

Quote:ip as-path access-list 1 permit ^4$
router bgp 1
neighbor 10.4.4.4 remote-as 4
neighbor 10.4.4.4 route-map foo in
route-map foo permit 10
match as-path 1

OSPFv2 supports IPv4, while OSPFv3 supports IPv6.

https://content.cisco.com/chapter.sjs?ur...0.html.xml

The server has a known IP address of 2::2/64

To be able to enable OSPFv3 on an interface, the interface must be enabled for IPv6. This occurs when the interface is configured with a global unicast IPv6 address.

https://www.ciscopress.com/articles/arti...4&seqNum=4


Since there is no mention of IPv6 to IPv4 NAT, we must select the option to use IPv6 to connect to the server at Center (2::2/64).  This assumes that the command "ipv6 ospf 1 area 2" falls under IPv6 configruation but is still the best answer.

BFD Detects path failures between 2 adjacent routers.  A routing protocol failure could be a result of a misconfiguration. 
https://www.cisco.com/c/en/us/td/docs/io...s_bfd.html


BFD is a detection protocol designed to provide fast forwarding path failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding path failure detection, BFD provides a consistent failure detection method for network administrators. Because the network administrator can use BFD to detect forwarding path failures at a uniform rate, rather than the variable rates for different routing protocol hello mechanisms, network profiling and planning will be easier, and reconvergence time will be consistent and predictable.

https:// www. examguides. com / CCNP-ENARSI/ ccnp-enarsi-cramnotes-4.htm



bfd interval milliseconds min_rx milliseconds multiplier interval-multiplier
https://www.cisco.com/c/en/us/td/docs/io...#wp1053749

The Bidirectional Forwarding Detection (BFD) protocol is a simple hello mechanism that detects failures in a network. Hello packets are sent at a specified, regular interval. A neighbor failure is detected when the routing device stops receiving a reply after a specified interval.

https://www.juniper.net/documentation/us...20interval.