ccnp route and switch

ccnp route and switch

Configuration example (allocating community for routing ): PC2 is a new host access, arranged 192.168.0.1 address, the address after the completion of the configuration, PC2 transmits to the network a Gratuitous ARP , to prevent someone within the network using the same IP address, the Gratuitous ARP is senderIP and target IP All are themselves, senderMAC is its own MAC . Origin IGP, metric 0, localpref 100,ccnp route and switch, valid, internal, best OK , now go back to the main class network number 172.16.0.0/16 , then we will go out and look at the picture. 172.0.0.0/8 actually shifts the mask of this class B address to the left by 8 bits , so that the network number obtained is actually a large network number including 172.16.0.0/16 . Call it supernet . The static manually configured security address on the interface will not be converted to a sticky mac address. R2 re-advertises the A route, then according to the preemptive rule, R3 will ignore the R1 update about the A route. At the same time, due to the deployment of two-way re-release, R3 will further re-publish the learned A- route back to process 1 . The route to the LOOPBACK interface. Redundant RR environment Fa0/20 Origin AS-Path Next hop Network 192.168.20.0 0.0.0.255 area 1 FastEthernet0/0 BGP table on R7 : As the next hop to 100.0.1.0 and 2.0 . In the R4 on On R2 , in order to reach the network connected by R1 , R2 configures a tool that uses route summarization, referring to a summary route: 192.168.0.0/16 to R1 , although this does serve the purpose of network optimization, but this summary route Too "rough", it even includes the network segment on the R3 side, we call this behavior not accurate enough. Therefore, an ideal way is to use a "just right" summary route that includes these detailed routes, so that you can avoid the problem of insufficient aggregation.