ccna question paper

ccna question paper

Default Gateway . . . . . . . . . . . . . : fe80::5efe:2.2. 2.2%40 Match metric matches the route with the specified metric. match route-type matches the specified type of route match community matches the BGP community. 1111 0xxx xxxx xxxx ! Protocol ID: 0x86DD Address classification Dns-server 2000::8 domain-name HelloWord length In order to allow R1 to access the rest of the network, once and for all, send a RIPng default route to R1 : Then do a simple test: Image IPv4-Mapped NAT-PT R2 , R3 , aiming RIP create static routing domain summary route, point null0 , while only these static routes redistributed into OSPF , and indeed can play a sub-optimal paths to avoid the question, but: Ipv6 unicast-routing interface Loopback0 After completion, both OR1 and OR2 can learn the loopback interface route of the other party , but they cannot ping . View the routing table of OR1 : Neighbor discovery and adjacency formation mechanisms are the same 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 . 16 bits Ipv6 route ::/0 tunnel 0 Default route !! Core in OSPF R1 RIPv1 ! MTU Field name If the above is replaced by EIGRP , the phenomenon is the same as RIP , R1 will declare 1.1.1.0 into EIGRP. 729 compatibility Interface Serial0/0 ipv6 enable Difficult case 2002::2 The BGP4+ configuration of R3 is as follows: RS requires the router to generate RA immediately The configuration of R2 is as follows: Image Ip sla monitor 2 Interface fast0/0 ipv6 enable 90 Router ospf 100 supplement: S ...... ! RIP redistribute directly connected If you do not set Metric ,ccna question paper, the default 1 -hop neighbor passed (the neighbors directly using this 1 jump as Metric ); redistributed static route default Metric = 1 , use the default-metric can modify this default value, this command No effect on the metric that re-releases the direct connector . Image ............ PC1#sh ipv int PE1#sh mpls for :: ISATAP is an IPv6 transition mechanism that is very easy to deploy and use . In an IPv4 network, we can do it very easily !! Match, go this one Not used (set to all 0s ) ! Configure all interfaces as passive and manually activate specific interfaces: Ipv6 enable Network consolidation (same protocol or different protocols) Ipv6 route 2002::/16 Tunnel0 The prefix list contains the serial number, matching from the smallest The configuration of PE2 is as follows: Image A small experiment about DR understanding Switchport access vlan 20 interface vlan 10 When R2 is configured with no validate-update-source , R2 will not verify the RIP update message source, so R2 will accept R1. RIPv2 Image The session between Source and Destination is established. Offset-list offset list Image The configuration of R2 is as follows: Image The 64bits interface ID , and FE80 :: / 10 constitute a PC 's Linklocal address: fe80 :: 200: 5EFE: 1.1.1.1 At the same time, PC will ISATAP router Linklocal address fe80 :: 5efe: 2.2.2.2 set as the default gateway Holddown timer Per packet load-sharing is disabled IP unicast RPF check is disabled Inbound access list is not set Outbound access list is not set For link state routing protocols such as OSPF F000 – F7FF B removes the IPv4 header of the packet , obtains the original IPv6 data, and forwards it to PC2 . 1 : RIP-1 ; Neighbor FE80::CE02:8FF:FED8:0 activate No frame-relay inverse-arp ipv6 enable If no conflict is detected after 1S , A will send a non-solicited advertisement (an NA message), announcing that I will officially use this IPv6 address. There is an address pool on R1 . If R2 wants to use the address pool of R1 ( IPv6 DHCPserver ) to allocate it to users on its intranet, then you can make The PMTU here refers to the one-way, the smallest of the data outbound MTU along the way . Interface Serial0/0 ipv6 enable R2(config)# access-list 1 deny 192.168.3.0 R2(config)# access-list 1 permit any R2(config)# router ospf 1 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: Ip address 132.214.1.10 255.255.255.0 Interface FastEthernet0/0 ipv6 ospf 1 area 0 If an external route carrying a tag is advertised on R1 and OSPF is redeployed to EIGRP on R2 , then the route is advertised. The allocated portion of the entire IPv6 space: 192.168.1.0 the OSPF routing but will be re-injected into the RIP (because we deploy a two-way re-release), this is the route Feedback , the route was filling back. The Response packet contains a maximum of 25 routing entries. Image Exit Ipv6 nd prefix 2012::/64 890000 720000 off-link System Id Type Interface IP Address State Holdtime Circuit Id ! Port-channel Ethernet Channel of interfaces Router responds to this RA where there is a ICMPv6 of the Option , which contains the ISATAP router IPv6 prefix. and Image Path control Wherein R3 is as follows: Mechanism supplement 2023::3 ! Ipv6 ospf 100 area 1 301 There is an address pool on R1 . If R2 wants to use the address pool of R1 ( IPv6 DHCPserver ) to allocate it to users on its intranet, then you can make For a comprehensive explanation of IPv6 multicast , please see the "Black Tea Three Cup Multicast Technical Notes" Ip prefix-list ABC seq 5 permit 172.0.0.0/8 The configuration of R3 is as follows: Access-list 1 permit 192.168.2.0 Ipv6 address 2001::1/64 Each routing table entry must include at least the following three items: VLSM support Neighbor 2.2.2.2 update-source Loopback0 !! Reveal the IPv6 route prefix learned from CE1 into BGP. --- Access-list 1 permit 1.1.1.0 Mechanism introduction The AD value of 11.11.11.0/24 is adjusted to be larger than OSPF , for example 130 . So the configuration is as follows: Ipv6 address 2001:1:1::1/64 ipv6 address 2001:1:2::1/64 exit Whether the hop limit of the IPv6 header of the RA packet is 255 . Because only 255 means that it is generated by the router in the local network. IPv4 source IPv4 destination Configuration command At this point, the initial configuration has been completed. Origin codes: i - IGP, e - EGP, ? - incomplete ! Next hop Network 4.4.4.4 0.0.0.0 area 0 Note that, in the IPv6 environment is not recommended as IPv4 treat NAT attitude Which, to use NAT . Only in V4 single protocol with V6 There are two general ways to automatically configure an IPv6 address: External route tag Ipv6 address autoconfig [default] ! Metric: 0 Show ip cef Next on R4 , summarize the external routes that are re-released by itself: Interface FastEthernet0/0 ipv6 enable On this topic, the individual feels that there is no need to study it. It does not make much sense for the research of class-based routing protocols. No matter the actual application or the LAB exam, it is no longer involved, and you are interested in making it yourself. R1 and R2 are dual-stack routers that connect to both IPv6 and IPv4 networks. Use UDP521 (both source UDP port and destination UDP port are 521 ) Routing? The key point is that R2 , through the R2 deployment redistributed routing , routing information may be selected in different transmission routes between the domains. In the Stale state, if A wants to send data to B , it can be sent directly, and the entry about B from A is from Stale->Delay , and will wait for the prompt information of the application layer to indicate whether the neighbor is reachable. Complete PE1 and PE2 , PE-CE routing protocol configuration, and MP-BGP configuration. Mpls label range 200 299 mpls ldp router-id loopback0 Mpls label range 400 499 mpls ldp router-id Loopback0 Therefore, when the route lookup mode of the router is classless or the classless route lookup mode, the default lookup action of the router is the longest match criterion. For example, in the above figure, when R3 receives a packet and goes to 172.16.1.1 , then in fact, 172.16.1.1 is "dropped" in the network of 172.16.1.0/24 and 172.16.0.0/16 , both seemingly Yes , but 172.16.1.0/24 obviously has a longer match, so the packet is eventually dropped to R1 . Similarly, if there is a data packet going to 172.16.2.1 ? Since the entry of 172.16.2.0/24 is the highest according to the longest match principle, the data is thrown to R2 .