top of page

Grupo

Público·95 miembros
Volver
Adrian Scott
Adrian Scott
30 de mayo de 2023

Ejercicios de packet tracer resueltos ccna 2: Desafío de integración de habilidades



Introduction




Packet Tracer is a network simulation tool that allows you to create, configure, and troubleshoot network scenarios in a virtual environment. It is designed by Cisco Systems as a learning tool for CCNA (Cisco Certified Network Associate) students and instructors.




Ejercicios De Packet Tracer Resueltos Ccna 2



CCNA 2 is one of the four courses that prepare you for the CCNA certification exam. It covers topics such as switching, routing, VLANs, DHCP, NAT, ACLs, OSPF, EIGRP, and more.


In this article, we will show you some examples of ejercicios de packet tracer resueltos ccna 2 (solved packet tracer exercises ccna 2) that you can use to practice your skills and test your knowledge.


Ejercicios resueltos Paket Tracer




There are many sources of ejercicios resueltos paket tracer online that you can download and use for free. One of them is packettracer.network, which offers exercises in pdf and video formats.


These exercises are designed to help you master various concepts and protocols of CCNA 2 in a hands-on way. They cover topics such as RIPv2, DHCP, NAT, OSPF, EIGRP, STP, EtherChannel, VTP, DTP, etc.


Ejercicios en pdf




Here are some of the ejercicios en pdf (exercises in pdf) that you can find on packettracer.network:


  • Ejercicios resueltos paket tracer 1: This exercise consists of four parts that involve configuring RIPv2 on four routers and verifying connectivity.



  • Ejercicios resueltos paket tracer 2: This exercise consists of three parts that involve configuring DHCP on two routers and verifying connectivity.



  • Práctica de laboratorio 7.5.2 del desafío de RIPv2 (Lab Practice 7.5.2 RIPv2 Challenge): This exercise consists of five parts that involve configuring RIPv2 with passive interfaces, default routes, static routes, route summarization, and floating static routes.



  • Ejercicios resueltos paket tracer 3: This exercise consists of four parts that involve configuring NAT on two routers and verifying connectivity.



Ejercicios en video




Here are some of the ejercicios en video (exercises in video) that you can find on packettracer.network:


  • Configuración básica de DHCP y NAT (Basic configuration of DHCP and NAT): This video shows how to configure DHCP on a router and NAT on another router using Packet Tracer.



  • Exámenes Parciales CCNA 2 (Partial Exams CCNA 2): This video shows how to solve some questions from partial exams of CCNA 2 using Packet Tracer.



  • Biblioteca CCNA (CCNA Library): This video shows how to access a library of Packet Tracer files that cover various topics of CCNA 2.



Configuring Initial Switch Settings




This exercise is based on this source. It aims to teach you how to configure initial switch settings such as hostname, password, banner, interface description, etc.


The topology consists of two switches (S1 and S2) connected by a crossover cable and two PCs (PC1 and PC2) connected to each switch by straight-through cables.


Part 1: Verify the Default Switch Configuration




In this part, you will use show commands to verify the default switch configuration such as hostname, interface status, VLANs, etc.


  • On S1, enter privileged EXEC mode by typing enable.



  • Type show running-config to view the current configuration. Note the default hostname (Switch), password (none), banner (none), interface status (up or down), VLANs (default VLAN 1), etc.



  • Type show vlan brief to view the VLAN information. Note that all interfaces are assigned to VLAN 1 by default.



  • Type show ip interface brief to view the IP address information. Note that no IP address is assigned to any interface by default.



  • Type show mac address-table to view the MAC address table. Note that no MAC address is learned by any interface by default.



  • Repeat steps 1-5 on S2.



Part 2: Configure Basic Settings for Each Switch




In this part, you will configure basic settings for each switch such as hostname, password, banner, interface description, etc.



  • On S1, enter global configuration mode by typing configure terminal.



  • Type hostname S1 to change the hostname from Switch to S1.



  • Type enable secret class to set the encrypted privileged EXEC mode password to class.



  • Type line console 0 to enter console line configuration mode.



  • Type password cisco to set the console password to cisco.



  • Type login to enable password checking at login.



  • Type exit to return to global configuration mode.



  • Type line vty 0 15 to enter vty line configuration mode.



```html welcome\nto\nS1! to create a MOTD banner that displays welcome, to, and S1! on separate lines.


  • Repeat steps 1-16 on S2, but use the following values: enable secret class, console password cisco, vty password cisco, banner motd #Welcome to S2!#.



Part 4: Save Configuration Files to NVRAM




In this part, you will save the configuration files to NVRAM for each switch so that they are retained after a reboot.



  • You have already saved the configuration files to NVRAM in Part 2. To verify it, enter privileged EXEC mode by typing enable and entering the password class.



  • Type show startup-config to view the configuration file stored in NVRAM. You should see the same configuration as in the running-config file.



  • Type show version to view the system information. Note the value of the Configuration register, which should be 0x2102 by default. This means that the switch will load the startup-config file from NVRAM when it boots up.



  • To change the Configuration register value, enter global configuration mode by typing configure terminal.



  • Type config-register 0x2142 to change the Configuration register value to 0x2142. This means that the switch will bypass the startup-config file and load the default configuration when it boots up.



  • Type end to return to privileged EXEC mode.



  • Type reload to reboot the switch. Press Enter to confirm.



  • You should see a message that says System configuration has been modified. Save? [yes/no]:. Type no and press Enter. You should not save the configuration file because you want to test the Configuration register value.



  • You should see a message that says Proceed with reload? [confirm]. Press Enter to confirm.



  • The switch should reboot and display a message that says Would you like to enter the initial configuration dialog? [yes/no]:. Type no and press Enter. You should not enter the initial configuration dialog because you want to test the Configuration register value.



  • You should see a message that says Press RETURN to get started!. Press Enter to get started.



  • You should enter user EXEC mode with the default hostname Switch>. Type enable and press Enter. You should enter privileged EXEC mode with no password required.



  • Type show running-config. You should see the default configuration with no hostname, password, banner, interface description, etc.



  • Type show startup-config. You should see the configuration file stored in NVRAM with hostname S1, password class, banner Welcome to S1!, interface description Link to PC1 and Link to S2, etc.



  • Type show version. You should see the system information with the Configuration register value 0x2142.



  • To restore the Configuration register value to 0x2102, enter global configuration mode by typing configure terminal.



  • Type config-register 0x2102 to change the Configuration register value back to 0x2102.



  • Type end to return to privileged EXEC mode.



  • Type copy startup-config running-config to copy the configuration file from NVRAM to RAM. Press Enter to confirm.



  • You should see a message that says Destination filename [running-config]?. Press Enter to accept the default filename.



  • You should see a message that says [OK]. This means that the copy operation was successful.



  • Type show running-config. You should see the same configuration as in the startup-config file with hostname S1, password class, banner Welcome to S1!, interface description Link to PC1 and Link to S2, etc.



  • Type reload to reboot the switch. Press Enter twice to confirm and not save the configuration file.



  • The switch should reboot and display a message that says Would you like to enter the initial configuration dialog? [yes/no]:. Type no and press Enter.



  • You should see a message that says Press RETURN to get started!. Press Enter to get started.



```html show ip interface brief to view the IP address information. You should see that S1 has an IP address of 192.168.1.11 and a subnet mask of 255.255.255.0 on VLAN 1.


  • Type ping 192.168.1.1 to ping PC1. You should see five exclamation marks (!) indicating successful pings.



  • Type ping 192.168.1.2 to ping PC2. You should see five exclamation marks (!) indicating successful pings.



  • Type ping 192.168.1.12 to ping S2. You should see five exclamation marks (!) indicating successful pings.



  • On S2, enter privileged EXEC mode by typing enable and entering the password class.



  • Type show ip interface brief to view the IP address information. You should see that S2 has an IP address of 192.168.1.12 and a subnet mask of 255.255.255.0 on VLAN 1.



  • Type ping 192.168.1.1 to ping PC1. You should see five exclamation marks (!) indicating successful pings.



  • Type ping 192.168.1.2 to ping PC2. You should see five exclamation marks (!) indicating successful pings.



  • Type ping 192.168.1.11 to ping S1. You should see five exclamation marks (!) indicating successful pings.



Using a TFTP Server to Upgrade a Cisco IOS Image




This exercise is based on this source. It aims to teach you how to use a TFTP server to upgrade and backup a Cisco IOS image on a Cisco device.


The topology consists of a router (R1) connected to a TFTP server (TFTP Server) and a PC (PC-A) by straight-through cables.


Part 1: Upgrade an IOS Image on a Cisco Device




In this part, you will upgrade an IOS image on R1 using a TFTP server.



  • On R1, enter privileged EXEC mode by typing enable.



  • Type show flash to view the current IOS image stored in flash memory. You should see that R1 has an IOS image named c1900-universalk9-mz.SPA.152-4.M3.bin with a size of 101171712 bytes.



  • Type show version to view the system information and the current IOS version running on R1. You should see that R1 is running IOS version 15.2(4)M3.



  • Type copy tftp flash to copy an IOS image from the TFTP server to flash memory.



  • You should be prompted for the IP address of the TFTP server. Type 10.0.0.254 and press Enter.



  • You should be prompted for the source filename of the IOS image on the TFTP server. Type c1900-universalk9-mz.SPA.156-3.M6.bin and press Enter.



  • You should be prompted for the destination filename of the IOS image on flash memory. Press Enter to accept the default filename, which is the same as the source filename.



  • You should see a message that says Accessing tftp://10.0.0.254/c1900-universalk9-mz.SPA. 156-3.M6.bin.... followed by some exclamation marks (!) indicating successful transfers.



  • You should see a message that says [101171712 bytes copied in 25 secs (4046868 bytes/sec)]. This means that the copy operation was successful and the new IOS image has been copied to flash memory with a size of 101171712 bytes.



  • Type show flash to verify that the new IOS image is stored in flash memory along with the old one.



  • To make R1 boot from the new IOS image, enter global configuration mode by typing configure terminal.



```html boot system flash c1900-universalk9-mz.SPA.156-3.M6.bin to specify the new IOS image as the first boot option.


  • Type exit to return to privileged EXEC mode.



  • Type show running-config include boot to verify that the boot system command has been added to the running configuration.



  • Type copy running-config startup-config to save the configuration to NVRAM. Press Enter twice to confirm.



  • Type reload to reboot R1. Press Enter twice to confirm and not save the configuration file.



  • R1 should reboot and load the new IOS image. You should see a message that says System Bootstrap, Version 15.0(1r)M16, followed by some system information and the IOS version 15.6(3)M6.



  • You should enter user EXEC mode with hostname Router>. Type enable and press Enter. You should enter privileged EXEC mode with no password required.



  • Type show version to verify that R1 is running the new IOS version 15.6(3)M6.



Part 2: Backup an IOS Image on a TFTP Server




In this part, you will backup an IOS image on R1 to a TFTP server.



  • On R1, enter privileged EXEC mode by typing enable.



  • Type show flash to view the IOS images stored in flash memory. You should see two IOS images: c1900-universalk9-mz.SPA.152-4.M3.bin and c1900-universalk9-mz.SPA.156-3.M6.bin.



  • Type copy flash tftp to copy an IOS image from flash memory to the TFTP server.



  • You should be prompted for the source filename of the IOS image on flash memory. Type c1900-universalk9-mz.SPA.152-4.M3.bin and press Enter.



  • You should be prompted for the IP address of the TFTP server. Type 10.0.0.254 and press Enter.



  • You should be prompted for the destination filename of the IOS image on the TFTP server. Press Enter to accept the default filename, which is the same as the source filename.



  • You should see a message that says Accessing flash:c1900-universalk9-mz.SPA. 152-4.M3.bin... followed by some exclamation marks (!) indicating successful transfers.



  • You should see a message that says [101171712 bytes copied in 25 secs (4046868 bytes/sec)]. This means that the copy operation was successful and the old IOS image has been copied to the TFTP server with a size of 101171712 bytes.



  • To verify that the IOS image is stored on the TFTP server, click TFTP Server and then Services.



  • You should see a list of files stored on the TFTP server. You should see c1900-universalk9-mz.SPA.152-4.M3.bin with a size of 101171712 bytes and c1900-universalk9-mz.SPA.156-3.M6.bin with a size of 101171712 bytes.



  • To delete an IOS image from flash memory, enter privileged EXEC mode on R1 by typing enable.



  • Type delete flash:c1900-universalk9-mz.SPA.152-4.M3.bin to delete the old IOS image from flash memory.



  • You should be prompted for confirmation. Type y and press Enter.



  • You should see a message that says Delete filename [c1900-universalk9-mz.SPA. 152-4.M3.bin]?. Press Enter to confirm.



  • You should see a message that says Delete flash:c1900-universalk9-mz.SPA. 152-4.M3.bin? [confirm]. Press Enter to confirm.



  • You should see a message that says Erasing device... followed by some dots (.) indicating progress.



```html the old IOS image has been deleted from flash memory.


  • Type show flash to verify that only the new IOS image is stored in flash memory.



Verifying and Troubleshooting NAT Configurations




This exercise is based on this source. It aims to teach you how to verify and troubleshoot NAT configurations using show commands and debug commands.


The topology consists of a router (R1) connected to two switches (S1 and S2) and a PC (PC-A) by straight-through cables. R1 has two interfaces: G0/0 connected to S1 and G0/1 connected to S2. S1 has two PCs (PC-B and PC-C) connected to it by straight-through cables. S2 has a server (Server-PT) connected to it by a straight-through cable. R1 is configured with NAT to allow the PCs to access the server using private IP addresses.


Part 1: Isolate Problems




In this part, you will use show commands and ping commands to isolate problems in the NAT configuration.



  • On PC-A, click Desktop and then Command Prompt.



  • Type ipconfig /all to view the IP address information. You should see that PC-A has an IP address of 192.168.10.10 and a subnet mask of 255.255.255.0.



  • Type ping 192.168.10.11 to ping PC-B. You should see four replies from PC-B.



  • Type ping 192.168.10.12 to ping PC-C. You should see four replies from PC-C.



  • Type ping 209.165.200.225 to ping Server-PT. You should see four replies from Server-PT.



  • On PC-B, click Desktop and then Command Prompt.



  • Type ipconfig /all to view the IP address information. You should see that PC-B has an IP address of 192.168.10.11 and a subnet mask of 255.255.255.0.



  • Type ping 192.168.10.10 to ping PC-A. You should see four replies from PC-A.



  • Type ping 192.168.10.12 to ping PC-C. You should see four replies from PC-C.



  • Type ping 209.165.200.225 to ping Server-PT. You should see four replies from Server-PT.



  • On PC-C, click Desktop and then Command Prompt.



```html to view the IP address information. You should see that PC-C has an IP address of 192.168.10.12 and a subnet mask of 255.255.255.0.


  • Type ping 192.168.10.10 to ping PC-A. You should see four replies from PC-A.



  • Type ping 192.168.10.11 to ping PC-B. You should see four replies from PC-B.



  • Type ping 209.165.200.225 to ping Server-PT. You should see four replies from Server-PT.



  • On Server-PT, click Desktop and then Command Prompt.



  • Type ipconfig /all to view the IP address information. You should see that Server-PT has an IP address of 209.165.200.225 and a subnet mask of 255.255.255.224.



  • Type ping 192.168.10.10 to ping PC-A. You should see four replies from PC-A.



  • Type ping 192.168.10.11 to ping PC-B. You should see four replies from PC-B.



  • Type ping 192.168.10.12 to ping PC-C. You should see four replies from PC-C.



  • On R1, enter privileged EXEC mode by typing enable.



  • Type show ip interface brief to view the IP address information for the interfaces on R1. You should see that R1 has an IP address of 209.165.200.226 and a subnet mask of 255.255.255.224 on G0/1, and an IP address of 192.168.10.1 and a subnet mask of 255.255.255.0 on G0/0.



Type show ip


Acerca de

¡Bienvenido al grupo! Puedes conectarte con otros miembros, ...
Leer más

Miembros

Ver todos los miembros (95)
bottom of page