ccnp tshoot 300-135 pdf

ccnp tshoot 300-135 pdf

B is RR , C and D are clients , BCD constitutes a route reflection cluster; a BGP route is advertised from C. The so-called seed metric refers to when I use a route to re-publish from an external routing protocol to this routing protocol, if the metric of the route is not manually specified , the default metric is used . Look at the following table (the following table is a recognized default value that can be modified using the default-metric in the routing process ): ? In the ORIGINATOR_ID , then it is known that a routing loop has occurred , so the route is ignored. Neighbor 3.3.3.3 remote-as 345 Interface vlan 100 After receiving this poisoning message, B erases 10.4.0.0 from the routing table, but it still exists in the rip database , the status is possible down , the garbage collection time ( Garbage colletion CISCO default 60S ), the route is from B. The database is erased. The configuration of R2 is similar. After the configuration is complete, the RIP messages are exchanged between R1 and R2 , and the unicast is performed, so that the PC will not be affected. The other values ​​of DSAP and SSAP are pure IEEE802.3 frames. R5 release B segment RIP routing, R2 and R3 can learn, at the moment we are in R2 and R3 are on to OSPF to inject RIP routing, assuming that R2 injected first, then the B route will be R1 update to R3 , R3 this When you learn B routing from both RIP and OSPF , then it will: Aggregate-address 172.16.0.0 255.255.0.0 as-set summary-only When a secure address is configured on a Port-Security interface, and the MAC address of the secure address attempts to access another Port-Security interface in the same VLAN , the penalty is initiated. SA sends the original switch MAC of the frame Two-point two-way route is re-released CASE4 : Origin IGP, metric 0, localpref 100, valid, internal Message type Version Atomic_Aggregate is a recognized self-determination attribute; Aggregator is optional. 10.1.23.2 from 10.1.23.2 (10.1.23.2) : ccnp [Synchronization concept] After a BGP router learns a route from an IBGP neighbor, it is not enabled (not optimized) unless it learns the same route from the IGP again . This is to prevent the routing black hole problem described above. ? Strange phenomenon: In the BGP table of R5 , there are only two routes advertised by R2 , and the 100.0 route from R3 is not passed to R5 via R4 . In other words, we expect that AS345 will have redundancy to 100.0 network. Remaining path (through R1 , DHCP server messages (such as DHCPOFFER, DHCPACK, DHCPNAK , or DHCPLEASEQUERY ) will be released. On the contrary, packets received from the DHCP server on the untrust interface will be filtered out, thus preventing illegal DHCPserver access. . While the deployment of DHCP Snooping the switch locally, but also to maintain a DHCPsnooping binding database ( the Binding Database ),ccnp tshoot 300-135 pdf, save for listening to the DHCP entries interaction, information includes (for untrust interface): the MAC address, IP address ( assigned by DHCP ), lease, binding type, VLAN number, and interface number (the DHCP client is the untrust interface connected to the client PC ) . This oneIn addition to doing some basic security access control, DHCP snooping banding databse can also be used for anti- ARP spoofing solutions such as DAI .