ccnp tshoot ticket 7

ccnp tshoot ticket 7

Community R1 and R2 establish EBGP . On R1 , the network announces 11 and 12 network segments. To filter out 12 network segments, do not let them pass to R2 . Let's take a look at R4 : Local origin Set the interface to DTP dynamic negotiation, optional auto or desirable Switch(config-if)# switchport mode host If a DHCP relay is also deployed on the switch, the switch adds the relay address to the DHCP packet. 200 i R1 uses 1.1.1.1 as the update source, trying to establish a BGP connection with 2.2.2.2 , and the local IP address of R2 is 1.1.1.1 , and The version of the last bgp table sent by TblVer to the neighbor * i 8 bits Synthesis example 2 : The configuration of SW2 is as follows: PS : At present, the Ethernet frames we use are basically Ethernet II frames. In the above figure, the configuration revision number of server and client is the same, but the vlan information is different. At this time, an error will be reported, prompting md5 digest checksum mismatch Vlan 101 So first on R1 and R2 , in order to allow them to reach the server 10.1.1.0 and 2.0 network segments, you need to configure two static routes: CCNP ROUTE contains all the contents of the book Interface fa1/0 Border Gateway Protocol (BGP) Connected Data forwarding mode 13 Invalid timer * 172.16.0.0/16 is variably subnetted, 4 subnets, 2 masks S* 172.16.0.0/16 [1/0] via 172.16.3.0 Instead of tearing down and rebuilding TCP or BGP connections, only the update operation is triggered to make the new routing policy take effect. Soft reset can be used for both inbound and outbound policies only due to outbound or inbound policies. R2#sh ip b 100.100.100.0 Remarks The out- direction policy cannot be used separately for the member of the peer-group . It can only be used for the entire group . The in direction does not have this restriction. All neighbors in the same peer group must be all iBGP neighbors or all eBGP neighbors. Sw(config-if)#switchport mode private-vlan host Bridge ID in the MAC , is the backplane of the switch MAC , the port ID in the MAC switch port MAC , all the view switch mac available Interface vlan 100 Network Interface loopback1 Port The Layer 2 switch searches for VLAN configuration information based on the destination MAC address and VLAN ID of the frame, and determines from which port the frame is sent out. Avoid routing loops with triggered updates Therefore, you need to use the MAC address reduction scheme. As-path: all specific routes received as numbers are placed in {} , the calculation AS_Path the length of the AS is only counted as . 1 th AS R3 and R4 , R4 and R5 establish IBGP neighbor relationships, and R3 R4 R5 uses LOOPBACK as the update source and refers to the neighbor . A static route to the host Milne is added to the ROO . The next hop is the E1 port of Kanga . The purpose is to pass the bridge that is often congested. But found that Kanga will be sent to the host Based on UDP protocol ports 67 and 68 BGP path attribute STP uses four parts to solve the Layer 2 loop: Set ip next-hop ip1 Set ip next-hop ip2 128 Paths: (1 available, best #1, table Default-IP-Routing-Table) Flag: 0x820 Basic VLAN concept Limit the number of access hosts per port (number of MAC addresses) Message age If R1 turns off auto-summary and network 1.1.1.0 , the declaration is unsuccessful because there is no mask for class declaration. The configuration of R2 is as follows: Modify the default value of the MED value *>i Paths: (2 available, best # 2, table Default-IP-Routing-Table) Flag: 0x820 neighbor to mean), BGP The network command, only the local routing loaded into BGP one way process. RIP-1 Only What is the routing table for R3 ? In fact, without any impact, R3 can learn the routing of the entire network. As for why, I believe that it has been explained very clearly. MAC address allocation and reduction Basic experiment Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale neighbor to mean), BGP The network command, only the local routing loaded into BGP one way process. Set ip address prefix-list Solution: The way to redistribute static summary route to avoid the sub-optimal routing and other issues Standard ACL Atomic character Ip address 10.1.45.4 255.255.255.0 Associate the static route of the next hop 100 100 i BVI Bridge-Group Virtual Interface : Disabled Interface vlan 100 Basic 32 bits Route-map test permit 10 Set origin incom Protocol basis If multiple path originating router IDs or router IDs are the same, then the shortest path of the Cluster-List is preferred . The range of prefixes to match, ranging from length to le-value Neighbor 1.1.23.2 route-map test out BGP is designed to AS transfer routes between, so it is actually a hop AS . s> 172.16.2.0/24 Network 200 When the switch receives suboptimal BPDUs from other designated switches or root bridges , 802.1D encounters this situation by first ignoring these suboptimal BPDUs . LocPrf When ISP1 is down, the interface of GW connected to ISP1 is DOWN , and the traffic of PC access 100 is automatically switched to ISP2. LocPrf 200 i learner Next we SW1 of the Fa0 / 20 interface, do switchport allowed vlan the Remove Trunk 10 , the vlan10 traffic pruned,ccnp tshoot ticket 7, this time the PC between can not ping pass, go R1 speaking about: + Public Origin IGP, metric 0, localpref 100, valid, internal, best IP Routing Overview 5 Learn R3 and R5 both advertise the routes of the same network segment to R4 . If the first eight rules cannot be determined, if R4 is configured: Therefore, from here we can see that the route summary is a risk of looping. One way to solve the above problem is to add a static route on the Layer 3 switch: ip route 192.168.0.0 255.255.0.0 null 0 , this way, when it receives access Route-map WT2 permit 20 match ip address prefix-list 2 set weight 200 In the R3 , the route AS_PATH learned from R2 about 1.1.1.0 will become " 6666 200 i ", because R3 receives 1.1.1.0 Activates self-recovery of the err-disable interface due to arp-inspection violations . Assuming the environment is like this, R1 re-releases A route into OSPF , then R2 will learn this OE2 in its own OSPF process 1 . ? For the next hop and route tag, see Volume I, page 189 . * i For example , the configuration of R3 is as follows: Interface vlan 10 Feature VLAN: Network 100.0.1.0 mask 255.255.255.0 Set excommunity cost pre-bestpath 1 20 , the cost value will greatly affect the routing principle, will become the first rule beyond the weight value The default load balancing method is round-robin ? R1 uses 1.1.1.1 as the update source, trying to establish a BGP connection with 2.2.2.2 , and the local IP address of R2 is 1.1.1.1 , and s> 172.16.10.0/24 Default seed metric When the previous eight routing principles fail to optimize the optimal route, and the maximum-paths [ibgp] n is configured under the BGP process , and the value of n is 2-6, the equivalent load balancing will be performed. All dynamically learned MACs on this interface will be converted to a sticky mac address to form a secure address. 300 {100,200}, (aggregated by 300 3.3.3.3) If multiple path originating router IDs or router IDs are the same, then the shortest path of the Cluster-List is preferred . In 802.1q the native vlan is untagged, using Dot1q switches all unmarked frame is forwarded to the native vlan in the ISL on all data frames, including native vlan encapsulation, so if the package is not received The data frame will be discarded (the ISL does not have the concept of a native VLAN ). Holddown timer We mainly analyze: Host 192.168.1.111 255.255.255.0 Ip dhcp snooping Load balancing can be modified on AVG , but it is recommended to configure on all routers. Display BGP tables, for example: Network Next Hop Document number So first on R1 and R2 , in order to allow them to reach the server 10.1.1.0 and 2.0 network segments, you need to configure two static routes: 0.0.0.255 will not work. 100 i 16 Vlan range MST ! As a result, R3 updates the BGP route to R4 , and next-hop will be replaced with R3 's loopback interface IP . Ip dhcp relay information trusted Switch(config)# spanning-tree portfast default Note that this modification will take effect on all routes sent by R5 (the weight of all routes will become 100 ), and Neighbor 10.1.25.5 remote-as 345 Then the test lines will be powered up for detection. It is found that the 2nd and 3rd lines match, but the matching length of the 2nd line is the longest, so the final result: 0 7 15 31 The configuration of R2 is added as follows: ? 3 Sender ( R2 ) saves basic configuration, such as BGP neighbor relationships Establish BGP neighbors 2 : RIP-2 ; 2.2.2.2 3 Root ID At another point, R2 will take 10.0.0.0 , 11.0.0.0 (the network segment where the secondary address is located), and 1.0.0.0 and 3.3.3.0 from their own loopback. Network 4.4.4.4 0.0.0.0 area 0 Suppose we have several subnets: 2 : RIP-2 . Redistribute ospf 1 match nssa-external 1 nssa-external 2 Neighbor xxxx advertise-map xx exist-map xx Then all the 172 network segments on R1 and R2 are suppressed. At the same time, since the route-map test only matches the 1.0 and 2.0 network segments (in AS100 ), this summary route, AS_PATH only inherits AS100 , which is 300 100 ; When the GW loses the route to 10.1.12.2 and the connection to ISP2 is also lost, then the default route is taken. BGP introducing and transmission routes Experimental topology and description 1 Bindings are just special address pools. There is no limit on the number of manual bindings, but you can only configure one manual binding per host pool. 192.168.1.0/24 Vlan 101 Add the following configuration on R5 : Each update message describes only a single BGP route. This is because the BGP path attribute can only describe a single route. If both commands are closed: 0 ? Neighbor 10.1.13.3 route-map test out Switch(config)# vtp password x LocPrf Blocking to forwarding state usually takes 30-50s (default 50S , ie 20+15+15 ), this time can also be adjusted by configuring the spanning tree timer. NAT (Network Address Translation) Bgp default local-preference 500 // Modify the default LP value Let's analyze that SW1 inserts the DHCP request message from the PC into option82 and then sends it to SW2 . Via SW2 Experimental topology and description 1 R3 associates the route-map with the redistribution of the direct route 3.3.3.3/32 , tag#11 , and the route is passed to R2 . On R2 , the redistribution of RIP to OSPF is deployed. After the external route of 3.3.3.3 is injected into OSPF , the tag value is carried by default. Router ospf 100 Bgp cluster-id 222.222.222.222 5.5.5.5 Receiving behavior RIPV1 operating behavior Vlan 10 Neighbor 10.1.13.1 remote-as 100 MTU problem Ip community-list 11 permit 100:11 no-advertise The default load balancing method is destination-based load balancing. CEF 's destination-based load balancing is actually implemented by HASHing the destination and source IP addresses . In contrast, in fast forwarding, load balancing based on destination address is performed strictly according to the destination IP address.