Valid 400-101 Dumps shared by ExamDiscuss.com for Helping Passing 400-101 Exam! ExamDiscuss.com now offer the newest 400-101 exam dumps, the ExamDiscuss.com 400-101 exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com 400-101 dumps with Test Engine here:
Which two loop-prevention mechanisms are implemented in BGP? (Choose two.)
Correct Answer: A,B
Explanation/Reference: Explanation: When dealing with the possibility of routing updates making their way back into an AS, BGP relies on the information in the AS_path for loop detection. An update that tries to make its way back into the AS it was originated from will be dropped by the border router. With the introduction of route reflectors, there is a potential for having routing loops within an AS. A routing update that leaves a cluster might find its way back inside the cluster. Loops inside the AS cannot be detected by the traditional AS_path approach because the routing updates have not left the AS yet. BGP offers two extra measures for loop avoidance inside an AS when route reflectors are configured. Using an Originator ID The originator ID is a 4-byte, optional, nontransitive BGP attribute (type code 9) that is created by the route reflector. This attribute carries the router ID of the originator of the route in the local AS. If, because of poor configuration, the update comes back to the originator, the originator ignores it. Using a Cluster List The cluster list is an optional, nontransitive BGP attribute (type code 10). Each cluster is represented with a cluster ID. A cluster list is a sequence of cluster IDs that an update has traversed. When a route reflector sends a route from its clients to nonclients outside the cluster, it appends the local cluster ID to the cluster list. If the route reflector receives an update whose cluster list contains the local cluster ID, the update is ignored. This is basically the same concept as the AS_path list applied between the clusters inside the AS. Reference: http://borg.uu3.net/cisco/inter_arch/page11.html