ccnp switch podcast

ccnp switch podcast

R2#sh ip b 100.100.100.0 Class and classless route lookup mode 9 R3 summarizes the details of R1 and R2 (summary command plus AS_SET keyword), so that the BGP summary route generated by R3 inherits the detailed AS_PATH attribute, and the packet capture on R4 will find the summary route. = 300 {100,200} AS_PATH : look at the results of the capture, found article summary route AS_PATH attribute consists of two parts ( segment ), the value 300 that the segment is ? Access-list 1 permit 1.1.1.0 The PVID is the "port default VLAN ID ", which means that a port belongs to the VLAN by default . 2 : Reponse message, send all or part of its routing information, one r >i1.1.1.0/24 Local network and re-routed routes, LP defaults to 100 , and can be transmitted to other IBGP neighbors within the AS . The LP is unchanged unless the policy is deployed during transmission. The election of the Root Bridge will not be said. Router bgp x Weight The Native VLAN must match at both ends of the trunk . Otherwise, VLAN traffic will appear. O IA C The default COST value of all ports on the switch will increase by 3000 ,ccnp switch podcast, so that the port of the switch is not elected as the designated port. LocPrf 1 Experimental phenomena: If you configure the following, then the COST comparison will exceed the weight and become the most preferred comparison rule. 3.3.3.3 Of course, you can also associate the route-map after re-issuing the command and set the tag in the route-map . Establish BGP neighbor relations 4 R3 , R4 , and R5 each create a LOOPBACK interface with an IP address of xxxx and x is the number of the router. If you don't feel it (such as the middle switch ), you can't switch automatically. The router will still throw data to this next-hop . Here we are talking about is the switcher, as we all know, is not recognized by the switcher Layer 3 packet, which they will not see a three-tier I head, but this does not affect a switcher own IP address. On the router, we configure the IP address of the physical interface of the router , and the second layer Show ip bgp 11 Protocol Interface The KEEPALIVE message actually compensates for the defect that TCP cannot confirm the peer's survival. Tunnel Tunnel interface No synchronization Access-list 1 permit any route-map PBR permit 10 match ip address 1 None The configuration of SW2 is as follows: Next Hop Prefix list is much more controllable than access list, supports incremental modification, and is more flexible These two attributes are used to prevent ringing within the federation and member AS . Distance 100 192.168.12.1 0.0.0.0 1 Hello time root bridge sends configuration BPDU default interval 2 is S Ip flow-export forwards the NETFLOW audited packet to the specified device . Bgp bestpath as−path ignore This command, if configured, skips this rule Used to increase the route metrics learned through EIGRP or RIP when inbound or outbound . Set interface Redistribute external routes into the IGP to ensure IGP synchronization with BGP . However, the drawback of this method is that if a large number of routes are obtained from BGP , it is a considerable burden for the IGP . Destination Address (Route Prefix): This is the destination network number associated with the route entry. A complete route prefix consists of: network number + prefix length In the figure above, we started the re-release action on R2 . We "inject" the OSPF route into the RIP process, so that Configuration example 1 : as-path access-list with filter-list If R1 turns on auto-summary and network 1.1.1.0 mask 255.255.255.0 , it is still updated to R2 with details. Run the switchport port-security mac-address command to configure a static security address entry. The configuration of R4 is as follows: 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 Sh ip bgp neighbors {address} received-routes The protocol for RSTP BPDU is 2 and the version is 2 . Wherein SW1 is as follows: 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. RIP defines two types of request messages and response messages. * i100.0.1.0/24 In VTP server mode of SW3 is turned on VTP pruning after, Client of SW1 and SW2 are learning and also to open their VTP pruning . Exit Of course, on R3 , the same effect can be achieved with the distribution list in the in direction. Fa0/20 Ip detects whether the IP address in the ARP body is invalid or unexpected, such as 0.0.0.0 , 255.255.255.255 , and multicast IP address, which are considered invalid IP . SenderIP verifies whether the message is an ARP request or response . And targetIP only if the message is the ARP response will be verified when The configuration of R1 is as follows: 10.1.12.1 from 10.1.12.1 (1.1.1.1) DMZ-Link Bw 12500 kbytes Port Weight Note the tool. Here is actually a summary of the deployment of static routes, of course, in addition to we can also route summary in the dynamic routing protocol, almost all dynamic routing protocols support route summarization. Switch(config)# interface fast0/15 CISCO Private Agreement 10.1.12.2 Ip route 172.16.1.0 255.255.255.224 192.168.12.1 basic concept After SW3 receives this message, it knows that SW2 no longer has vlan10 users, and no longer needs vlan10 traffic, so it will trim vlan10 on its own FA0/22 port : 3.3.3.3 Hello time 3 sec, hold time 10 sec Next hello sent in 1.280 secs Summary 1) 2) two points is MED in IBGP passed without problems (not lost) between, but EBGP between transfer depends on whether the route originated in themselves. Rl , R2 , R3 running the OSPF , R3 routing table is as follows: 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 . Of course, this time 1.1.1.0 is unable to access 3.3.3.0 , because R3 does not have a route in the RIP routing domain (that is, there is a problem with the backhaul routing, data communication must always consider the round-trip path, remember), so if To achieve network-wide interworking, you need to be on R2 : AS_SEQUENCE exactly the same, except that the list of AS numbers belong to the local Federation AS Switch(config-if)# ip address 192.168.10.254 255.255.255.0 Document number trunk permanent link aggregation mode, forced trunk , send DTP frames Route . 3 : the AS_PATH : 500 the MED : 150 External RouterID : 172.16.13.1 MD5 digest : 0x73 0x52 0x60 0xE7 0x4D 0xA5 0xC7 0x4F 0xCA 0x3D 0x6F 0x1D 0x3F 0x23 0x03 0xBB Switch(config)# interface fast0/15 Detailed rules Modify the default value of the MED value R1 and R3 , R2, and R5 establish an EBGP neighbor relationship. A sends the BPDU out of its designated port, and the BPDU is flooded to the network. Difficult to resolve Create secure addresses through dynamic learning, manual configuration, and stciky In R6 connecting the R4 interface to capture found update package 11.11.11.0 prefix attribute carried AS_PATH contains 2 th content: After the basic configuration is complete, take a look: 100 When the route-map is executed, the match statement contained in the policy-list called by it will be traversed and the match action will be executed . ? ... Route filtering or execution strategy during redistribution Run RIP between R1 and R2 (declare direct connection and their respective LOOPBACK ). At this time , the update package sent by R1 has the source address of 192.168.12.1 . The configuration of R2 is as follows: Ip sla monitor responder SW2 and SW3 are similar situations; note that at this point we are not allowed to do any static configuration of the allowed vlan configuration on the trunk port. Neighbor 10.1.23.2 remote-as 200 Trunking Bgp default local-preference 500 // Modify the default LP value Network 100.0.2.0 mask 255.255.255.0 Frames with a type field of 8137 represent IPX and SPX transport protocol frames. Switch(config)# interface fast0/15 Ip route 100.0.0.0 255.0.0.0 null0 BGP routing table entry for 100.0.1.0/24, version 3 Implementation points ? 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 About sticky secure address BGP does not update the route periodically. It is updated only when needed. Because the route of the public network may be turbulent, there will be a certain waiting time for triggering the update. The IBGP peer is 5S . The EBGP peer is 30S . During the time, BGP can still collect routing information, so BGP convergence will be slower. 5.5.5.5 Then R2 introduced locally 1.1.1.0 of BGP routes, and inherits from OSPF learned 1.1.1.0 of Metric 2 , then R3 on CISCO Note: The DHCP option-82 feature is supported only when DHCP snooping is globally enabled and on the VLANs to which subscriber devices using this feature are assigned. Switch(config)# interface fast0/15 AS_CONFED_SEQUENCE A list of ordered AS numbers on a path to a particular destination. The configuration of R3 is as follows: The Response packet contains a maximum of 25 routing entries. The EBGP route is set to a small AD value of 20 . In addition: when the spanning tree reconfigures the new root port, other interfaces flood the network with Establish IBGP full interconnection and close the synchronization mechanism. This method is basically used at present. But this method has a flaw, that is, if IBGP By modifying the weight to influence the routing decision One solution is that SW1 does not insert opiton82 , another method is to use the configuration on the DHCPserver : You can learn these two external routes. When a route oscillates (continuously fails, recovers), it is assigned a penalty value. The more the swing, the larger the penalty value and the constant accumulation. 5.5.5.5 Weight Set ip default next-hop 10.1.12.1 If you do the following configuration on R2 : In the transport AS , establish IBGP full interconnection, that is, R3 and R4 , R4 and R5 , R3 and R5 are established. Match community 1 Network 192.168.24.2 0.0.0.0 area 0 We see that on R4 , there are redundant paths for the two networks of 100.0 , but they are not best . Naturally, R4 cannot use these routes. Why is it not best ? The reason is that the next hop, nexthop is unreachable. Further, the summary is transmitted to the route D after, D will continue to B to pass, and as summarized route from C , thus reaching D of AS400 BVI Bridge-Group Virtual Interface If an error occurs after receiving the open message, a Notification message is sent . If not Mechanism overview EBGP non-equivalent load balancing Port 100 When there are multiple paths, the BGP Router only selects the optimal route ( BEST ) to use (without load balancing) LocPrf Sw(config)#interface range fa 0/3-4 Convergence comparison between 802.1D and RSTP Manual summary Router bgp 200 basic concept Network Static Routing Use the show spanning-tree inconsistentports command to view related entries. Sw1(config-if)#ip address 172.16.10.1 255.255.255.0 Sw1(config-if)#no shu (global configuration command) activates portfast features on all non- trunk interfaces Configuration command Manual network through BGP , which originated from IGP , because BGP network must guarantee the network ip route 172.16.1.0 255.255.255.0 192.168.12.1 !! go subnet route If the number exceeds xx , disconnect the BGP connection with the neighbor and reconnect after 2 minutes. Ip community-list 11 permit 100:11 no-export 100 AS100 sends 10000 routes to R2 . If R2 only wants to collect 100 routes and the rest is filtered, then the general practice is to execute the in- direction filter on R2 , because AS100 is uncontrollable for AS200 . However, this method is actually a waste of link bandwidth and network resources. Next-hop , the next-hop is changed to the update source IP of R3 , which is the loopback interface IP. Database , this database is DHCP Snooping listens for DHCP information recorded after the interaction, inside contains the client's IP , the MAC , belongs to VLAN -related information, etc., and this information, just as ARP 's legality verification. Switch(config-if)# ip address 192.168.255.254 255.255.255.0 Version Used in route-map , when some of the matching entry, and using the set command, the route-map used in a neighbor (e.g., out time direction), then to update the route to a neighbor, the BGP of MED properties will Inherit the metric value of these routes in the local IGP To other neighbors the Next-Hop recursive This (recursive next hop ) broke the characteristics of the traditional hop-hop interface must be directly connected under the router IP restrictions. Recursive next-hop may not be directly connected to the network, as long as the relevant routes in the routing table are reachable. Generally, the recursive next-hop is unreachable, and the data will be handled by the route (generally the default route is matched).