ccnp route 9tut

ccnp route 9tut

(interface) ip load-sharing per-packet The MAC sublayer is responsible for the following tasks: R3 announces 192.168.1.0 , 2.0 , and sets the community attribute of 1.0 to no-adv. DHCP R 3.0.0.0/8 is possibly down , routing via 9.9.12.2, FastEthernet0/0 Both You must use neighbor in the BGP process to specify the BGP peer . They exchange routing information,ccnp route 9tut, as well as related attributes, not link status. Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to EBGP peer) Flag: 0x820 R4 selects R5 as the next hop to the 100 network segment. This is because the two routes are taken from R5 , the weight weight is 100 , and the weight of R3 is the default 0. Naturally, R5 is preferred, so R4 will The path is switched to R5 . Therefore, we still need to keep the AS_PATH of its details on the summary route. As for the order of the AS number in the AS_PATH of the reserved detailed route , it is not important, because we only need the AS number for the purpose of anti-ring. It is. Therefore , the summary route generated by R3 actually carries two AS_PATH types, one is AS_Seq , the value is 300 , the other type is AS_set , contains two AS numbers of {100,200} , and is unordered. So the AS_PATH received on R4 is 300 (100,200} combined . It is worth noting that the AS number in this bracket is only counted as one hop when performing the AS_PATH calculation. For the verification of this point, please see the section on routing rules.