ccna 200 301 syllabus plural or singular phenomena

ccna 200 301 syllabus plural or singular phenomena.. ,,-: :.................................................................. :--- Type escape sequence to abort. sending5, 100-byte ICMPEchos to 12.1.1.2, timeoutis 2,seconds: IIIt! k140 Successrate is 100 percent(5/5), round-trip min/avg/max -12/24/36 ms The result of ping 2.222" on router R1 is as follows: Rltping2.2.2.2Type escape sequence to abort. sending5, 100-byte ICMPEchos to 2.2.2.2, timeoutis 2 seconds:Successrate is 0 percent(0/5)Why does router R1 to 12XP 1.2 arrive, but to 222.2 fails? The reason is that the flow of data in the router is: when a packet is received from the LAN, before entering the RAM, first check its second layer of header information, if it is sent to this router, the second layer of header information is stripped and put into the RAM. In the RAM, the router detects the packet's Layer 3 header information, and the CPU simultaneously searches the routing table and matches the Layer 3 address to determine where the packet should be output and in what manner it should be encapsulated. The router also queries the routing table for packets originated by this router to determine the forwarding interface.When pinging 12.1.1.2 at R1±, R1 queries its own routing table and packets going to 12.1.1.0/24 should be sent out of the Seriall/1 interface, a serial point-to-point line between R1 and R2 with data link layer encapsulation PPP or HDLCo R2 receives the packet from R1, R2 checks the destination IP address in the packet and finds that it is the same as the IP address of this router interface, which is addressed to this router. R2 also learned that the ping packet (Echo request) from the 12 1.1, R2 surveyed their own routing table, the ping packet answer packet (Echoreply) from Serial1/0 interface back, R1 received R2's answer packet, the result is R1 successfully ping through R2oWhen pinging 222.2 on R1, R1 queries its own routing table and finds that there is no route to 222.2 in the routing table, and R1 drops the packet, with the result that R1± fails to ping 2.2.2.2. Similarly, routers Rl, R2, and R3 can ping each other through the IP addresses of directly connected ports, but not through the IP addresses of non-directly connected ports.. 5.3 Static Routing***This section describes the configuration of static routes, and the advantages and disadvantages of static routes.5.3.1 Configuring Static Routes***In Section 5.2, R1 could not ping through 2.222,What is the solution to enable R1 to ping through that IP address? One solution is to configure a static route, which is a route between network segments that requires an administrator to manually join. In Figure 5-2-1, if router R1 knows to send a packet to 2.2.2.2 to R2, R2 checks the source IP address of the ping packet and finds that it is a packet from 12.1.1.1, R2 checks the local routing table and finds that 12.1.1.0/24 is a direct route, R2 sends the ping reply packet out the S1/0 interface, R1 receives the reply packet, and the ping is successful. The ping is successful. The key is how does the administrator notify the router that the packet going to 222.2 from R1 is going to R2? This requires adding a static route, and the command format for adding a static route is as follows.