ccnp switch with gns3

ccnp switch with gns3

100 The configuration of SW2 is as follows: R1 , R2 ,ccnp switch with gns3, and R3 run RIP , and 1.1.1.0/24 on R1 is not directly announced. On R2 : Remove VLANs from the current list // is equivalent to route-map not matching ( permit ) any entry, so all details are released Between R1 and R2 , the original R3 and R4 are updated through a multi-access network, and BGP is run . Experiment 2: weighted Source of routing information: How is this route learned, for example, static, or through OSPF , IS-IS , protocol 0.0.0.255 will not work. Configuration Revision 15 Access-list 2 permit 192.168.2.0 0.0.0.255 route-map PBR permit 10 NEXT_HOP on NMBA network Route-map WT2 permit 20 match ip address prefix-list 2 set weight 200 32 bits When track1 is true , that is, 10.1.1.2 is reachable, the data of the PC accessing the 100 network is lost to 10.1.1.2 . If track 1 is hung, the next next-hop is switched. Choose PAgP or LACP Ip route-cache flow show ip cache flow In the initial situation, when R2 updates 192.168.12.0/24 route to R3 , we look at the attributes of the route prefix in the updata message: DLY=2560 , because the DLY of the R2 F0/0 interface is 100 microseconds. The unit in the message is 10us , so 10*256=2560 , this value is the value carried in the DLY field in the message . The value of the bandwidth is also similar. This can all be calculated, no problem.