1.5.1 Packet Tracer – Cabling a Network with Routers, Switches, and Hosts Answers
Topology
| Device | Interface | IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|---|
| R1 | Fa0/0 | 192.168.1.1 | 255.255.255.0 | N/A |
| S0/0/0 | 192.168.2.1 | 255.255.255.0 | ||
| R2 | Fa0/0 | 192.168.3.1 | 255.255.255.0 | N/A |
| S0/0/0 | 192.168.2.2 | 255.255.255.0 | ||
| PC1 | N/A | 192.168.1.10 | 255.255.255.0 | 192.168.1.1 |
| PC2 | N/A | 192.168.3.10 | 255.255.255.0 | 192.168.3.1 |
Learning Objectives
- Review of previously learned skills.
- Basic IOS Command Line Interface operation.
- Basic Router configuration.
- Verification and testing of configurations.
- Management of configuration files.
Scenario
In this lab activity, you will review previously learned skills, including basic IOS command line interface operation and configuration commands. You will also learn to save configuration files to a text file and to a TFTP server. The skills presented in this lab are essential to completing the rest of the labs in this course.
Task 1: Cable the Ethernet Links of the Network.
Connect the Ethernet links for a network similar to the one in the Topology Diagram. The output used in this lab is from Cisco 1841 routers. But you can use any current router in the labs as long as it has the required interfaces as shown in the topology. A simple way to identify the available interfaces on a router is by entering the show ip interface brief command.
Which of the devices in the Topology Diagram require an Ethernet cable between them?
PC1 to S1, S1 to R1 and R2 to PC2
Step 1 Connect the R1 Router to the S1 Switch.
Use a straight through Ethernet cable to connect the FastEthernet 0/0 interface of the R1 router to the FastEthernet 0/1 interface on the R1 switch.
What color is the link status light next to the FastEthernet 0/0 interface on R1?
green
What color is the link status light next to the FastEthernet 0/1 interface on S1?
green
Step 2 Connect PC1 to the S1 Switch.
Use a straight through Ethernet cable to connect the network interface card (NIC) of PC1 to the FastEthernet 0/2 Interface of the S1 switch.
What color is the link status light next to the NIC interface on PC1?
green
What color is the link status light next to the FastEthernet 0/2 interface on S1?
green
If the link status lights are not green, wait a few minutes for the link between the two devices to be established. If after a few minutes the lights are not green, verify that you are using a straight-through Ethernet cable and that switch S1 and PC1 are powered on.
Step 3 Connect PC2 to the R2 Router.
Use a crossover Ethernet cable to connect the FastEthernet 0/0 interface of the R2 router to the NIC of PC2. Since there is no switch between PC2 and the R2 router a crossover cable is required for a direct link between the PC and the router.
What color is the link status light next to the NIC interface on PC2?
green
What color is the link status light next to the FastEthernet 0/0 interface on R2?
green
Task 2: Cable the Serial Link between the R1 and R2 Routers.
In a real WAN connection, the customer local equipment (CPE), often a router, is the data terminal equipment (DTE). This equipment connects to the service provider through a data circuit terminating equipment (DCE) device, which is typically a modem or a channel service unit (CSU)/channel service unit. data (DSU). This device is used to convert DTE data into a form acceptable to the WAN service provider.
Unlike the cables in the lab setup, in the real world the serial cables are not connected consecutively. In a real situation, one router may be in New York while the other may be in Sydney, Australia. An administrator in Sydney would need to connect to the New York router through the cloud WAN in order to diagnose faults on the New York router.
In the academy laboratory, the consecutive connection between DTE-DCE cables simulates the devices that make up the WAN cloud. The connection from the serial interface of one router to the serial interface of another router simulates the entire circuit cloud.
Step 1: Create a null serial cable to connect router R1 to router R2.
In the academy laboratories, the WAN connection between the routers uses a DCE cable and a DTE cable. The DCE-DTE connection between routers is known as null serial cable. In the labs, a DCE V.35 cable and a DTE V.35 cable will be used to simulate the WAN connection. The DCE V.35 connector is generally a V.35 female connector (34 pins). The DTE cable has a V.35 male connector. Cables are also labeled DCE or DTE on the router end of the cable.
DTE and DCE V.35 cables must be joined. With one end of the V.35 in each hand, examine the pins and receptacles as well as the threaded connectors. Note that there is only one correct way to connect the cables together. Align the pins on the male cable with the receptacles on the female cable and carefully attach them. Very little effort should be needed to complete this process. When connected, tighten the screws clockwise to secure the connectors.
Step 2: Connect the DCE end of the serial null cable to serial interface 0/0/0 of router R1 and the DTE end of the serial null cable to serial interface 0/0/0 of router R2.
Please review the information provided below before making these connections.
Before connecting to one of the routers, examine the connector on the router and the cable. Note that the connectors are tapered to prevent poor connection. With the connector in one hand, orient the cable connector and router connector correctly so that the tapers match. Now press the cable connector partially into the router connector. It probably won’t go in all the way, as the threaded connectors must be tightened for the cable to be fully inserted. While holding the cable in one hand and gently pressing the cable toward the router, turn one of the thumbscrews clockwise three or four turns to seat the screw. Now turn the other thumbscrew clockwise three or four turns, to seat it as well. At this point the cable should be secured in such a way that it is possible to release both hands to turn each wing screw at the same speed until the cable is fully inserted. Do not overtighten these connectors.
Task 3 Establish a Console connection to the R1 Router.
Step 1 Connect the console cable to the router and PC.
1. Connect the console cable to the router console port.
2. Connect the console cable to PC1.
Step 2 Create a terminal connection to the R1 router.
1. Use the following parameters when configuring the connection.
- 9600 baud
- 8 data bits
- No parity
- 1 stop bit
- No flow control
2. When the Terminal session window comes up, press the Enter key.
Task 4: Erase and Reload the Routers.
Step 1 Using the HyperTerminal session established in the previous Task, enter privileged EXEC mode on R1.
Router>enable Router#
Step 2 To clear the configuration, issue the erase startup-config command. Confirm the task when prompted, and answer ’no’ if asked to save changes.
Router#erase startup-config Erasing the nvram filesystem will remove all files! Continue? [confirm] [OK] Erase of nvram: complete Router#
Step 3 When the prompt returns, issue the reload command. Confirm the task when prompted. After the router finishes the boot process, choose not to use the Configuration Dialog facility.
Would you like to enter the initial configuration dialog? [yes/no]: no Would you like to terminate autoinstall? [yes]: Press Enter to accept default. Press RETURN to get started!
Step 4 Establish a HyperTerminal Session to R2. Repeat steps 1 through 3 to remove any startup configuration file that may be present.
Task 5: Command Line Basics.
Step 1 Establish a HyperTerminal session to router R1.
Step 2 Enter privileged EXEC mode.
Router>enable Router#
Step 3 Enter an incorrect command and observe the router response.
Router#comfigure terminal
^
% Invalid input detected at '^' marker.
Router#
Command line errors mainly occur due to typing errors. If a keyword in the command is spelled incorrectly, the user interface uses the caret (^) to identify and isolate the error. The ^ symbol appears near or at the point in the command string where the incorrect command, keyword, or argument was entered.
Step 4 Correct the previous command.
1. To correct an incorrectly entered command after the Enter key is pressed, use the Up Arrow key on the keyboard to recall the command. Then use the Right Arrow and Left Arrow keys to move the cursor to the location where the mistake was made and make the correction.
Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
2. If something needs to be deleted, use the Backspace key.
Step 5 Return to Privileged EXEC mode.
Router(config)#exit %SYS-5-CONFIG_I: Configured from console by console Router#
Step 6 Examine the commands that are available for Privileged EXEC mode. A question mark, ?, can be entered at the prompt to display a list of available commands.
Router#? Comandos Exec: <1-99> Número de sesión que debe reanudarse clear Restablece funciones clock Administra el reloj del sistema configure Entra al modo de configuración connect Abre una conexión de terminal copy Copia desde un archivo a otro debug Funciones de depuración (ver también 'undebug') delete Borra un archivo dir Enumera los archivos en un sistema de archivos disable Desactiva los comandos privilegiados disconnect Desconecta una conexión de red existente enable Activa los comandos privilegiados erase Borra un sistema de archivos exit Sale de EXEC logout Sale de EXEC no Inhabilita la información de depuración ping Envía mensajes de eco reload Se detiene y se reinicia desde el hardware resume Reanuda una conexión de red activa setup Ejecuta los comandos dentro del modo SETUP show Muestra la información del sistema en ejecución --More--
Step 7 View the rest of the command output by pressing the Spacebar. The remainder of the output will appear where the –More– prompt appeared previously.
telnet Abre una conexión telnet traceroute Rastrea una ruta hacia el destino undebug Inhabilita las funciones de depuración (ver también 'debug') vlan Configura los parámetros de VLAN write Escribe la configuración actual en la memoria, red o terminal
Step 8 Exit from Privileged EXEC mode with the exit command.
Router#exit
The following information should appear on the screen:
Router con0 is now available Press RETURN to get started.
Step 9 Press the Enter key to enter User EXEC mode. The Router> prompt should be visible.
The Router> indicator should be visible.
Step 10 IOS commands can be abbreviated, as long as enough characters are typed for the IOS to recognize the unique command.
Enter only the character e at the command prompt and observe the results.
Router>e % Ambiguous command: “e” Router>
Enter en the command prompt and observe the results.
Router>en Router#
The en command contains enough characters for the IOS to distinguish between the enable command and the exit command.
Step 11 Typing an abbreviated command, such as conf, followed by the Tab key completes a partial command name. Type the abbreviated command conf, press the Enter key, and observe the results.
Typing a shorthand command, such as conf, followed by the Tab key, completes the partial name of the command. This IOS functionality is called autofill. Type the shortcut command conf, press the Tab key, and see the results.
Router#conf Router#configure
This autocomplete feature can be used as long as you type enough characters for the IOS to recognize a single command.
Step 12 IOS commands must be entered in the correct mode. For example, configuration changes cannot be made while in privileged EXEC mode. Attempt to enter the command hostname R1 at the privileged EXEC prompt and observe the results.
Router#hostname R1
^
% Invalid input detected at '^' marker.
Router#
Task 6: Basic Configuration of Router R1.
Step 1 Establish a Terminal session with the router R1.
Step 2 Enter privileged EXEC mode.
Router>enable Router#
Step 3 Enter global configuration mode.
Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 4 Configure the router name as R1. Enter the command hostname R1 at the prompt.
Router(config)#hostname R1 R1(config)#
Step 5 Disable DNS lookup with the no ip domain-lookup command.
R1(config)#no ip domain-lookup R1(config)#
Why would you want to disable DNS lookup in a lab environment?
So that the router does not try to look up a DNS entry for a name that is actually just a typo.
What would happen if DNS lookup was disabled in a production environment?
A router would not be able to resolve names, which would cause potential problems when the router needs an IP address to send a packet.
Step 6 Configure an EXEC mode password using the enable password password command. Use student for the password.
R1(config)#enable secret class R1(config)#
Step 7 Configure an EXEC mode password using the enable secret password command. Use class for the password.
R1(config)#no enable password R1(config)#
Step 8 Remove the enable password. Since the enable secret is configured, the enable password is no longer necessary. IOS commands can be removed from the configuration using the no form of the command.
Step 9 Configure a message-of-the-day banner using the banner motd command.
R1(config)#banner motd & Enter TEXT message. End with the character '&'. ******************************** !!!AUTHORIZED ACCESS ONLY!!! ******************************** & R1(config)#
When is this title displayed?
When a user connects to the router either through Telnet or the console connection.
Why should all routers have a message of the day title?
To provide a warning to unauthorized access, whether intentional or not.
Step 10 Configure the console password on the router. Use cisco as the password. When you are finished, exit from line configuration mode.
R1(config)#line console 0 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#
Step 11 Configure the password for the virtual terminal lines. Use cisco as the password. When you are finished, exit from line configuration mode.
R1(config)#line vty 0 4 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#
Step 12 Configure the FastEthernet0/0 interface with the IP address 192.168.1.1/24. Activate the interface by using the no shutdown command.
R1(config)#interface fastethernet 0/0 R1(config-if)#ip address 192.168.1.1 255.255.255.0 R1(config-if)#no shutdown %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up R1(config-if)#
Step 13 Use the description command to provide a description for this interface.
R1(config-if)#description R1 LAN R1(config-if)#
Step 14 Configure the Serial 0/0/0 interface.
1. Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24.
2. Activate the interface by using the no shutdown command.
3. Set the clock rate to 64000.
R1(config-if)#interface serial 0/0/0 R1(config-if)#ip address 192.168.2.1 255.255.255.0 R1(config-if)#clock rate 64000 R1(config-if)#no shutdown R1(config-if)#
Step 15 Use the description command to provide a description for this interface.
R1(config-if)#description Link to R2 R1(config-if)#
Step 16 Use the end command to return to privileged EXEC mode.
R1(config-if)#end R1#
Step 17 Save the R1 configuration using the copy running-config startup-config command.
R1#copy running-config startup-config Building configuration... [OK] R1#
Task 7: Basic Configuration of Router R2.
Step 1 For R2, repeat Steps 1 through 11 from Task 3. (Use R2 for the hostname of this router.)
Step 2 Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24. Activate the interface by using the no shutdown command.
R2(config)#interface serial 0/0/0 R2(config-if)#ip address 192.168.2.2 255.255.255.0 R2(config-if)#no shutdown %LINK-5-CHANGED: Interface Serial0/0/0, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up R2(config-if)#
Step 3 Use the description command to provide a description for this interface.
R1(config-if)#description Link to R1 R1(config-if)#
Step 4 Configure the FastEthernet0/0 interface with the IP address 192.168.3.1/24. Activate the interface by using the no shutdown command.
R2(config-if)#interface fastethernet 0/0 R2(config-if)#ip address 192.168.3.1 255.255.255.0 R2(config-if)#no shutdown %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up R2(config-if)#
Step 5 Use the description command to provide a description for this interface.
R1(config-if)#description R2 LAN R1(config-if)#
Step 6 Use the end command to return to privileged EXEC mode.
R2(config-if)#end R2#
Step 7 Save the R2 configuration using the copy running-config startup-config command.
R2#copy running-config startup-config Building configuration... [OK] R2#
Task 8: Configure IP Addressing on the Host PCs.
Step 1 Configure the host PC1 that is attached to R1 with an IP address of 192.168.1.10/24 and a default gateway of 192.168.1.1.
Step 2 Configure the host PC2 that is attached to R2 with an IP address of 192.168.3.10/24 and a default gateway of 192.168.3.1.
Task 9: Router show Commands.
Step 1 Enter the show running-config command to display the contents of the currently running configuration file.
R1#show running-config ! version 12.3 ! hostname R1 ! ! enable secret 5 $1$AFDd$0HCi0iYHkEWR4cegQdTQu/ ! no ip domain-lookup ! interface FastEthernet0/0 description R1 LAN mac-address 0007.eca7.1511 ip address 192.168.1.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 mac-address 0001.42dd.a220 no ip address duplex auto speed auto shutdown ! interface Serial0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000 ! interface Serial0/1 no ip address shutdown ! interface Vlan1 no ip address shutdown ! ip classless ! ! ! ! line con 0 password cisco line vty 0 4 password cisco login ! end
Step 2 Enter the show startup-config command to display the startup configuration.
R1#show startup-config Using 583 bytes ! version 12.3 ! hostname R1 ! ! no ip domain-lookup ! interface FastEthernet0/0 description R1 LAN mac-address 0007.eca7.1511 ip address 192.168.1.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 mac-address 0001.42dd.a220 no ip address duplex auto speed auto shutdown ! interface Serial0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000 ! interface Serial0/1 no ip address shutdown ! interface Vlan1 no ip address shutdown ! ip classless ! ! ! ! line con 0 password cisco line vty 0 4 password cisco login ! end
Step 3 Enter the show interfaces command to display the statistics for all interfaces.
R1# show interfaces fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up (connected)
Hardware is Lance, address is 0007.eca7.1511 (bia 0002.1625.1bea)
Description: R1 LAN
Internet address is 192.168.1.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00,
Last input 00:00:08, output 00:00:05, output hang never
Last clearing of “show interface” counters never
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
R1#
Step 4 Enter the show version command to display the information about the currently loaded software version along with hardware and device information.
R1#show version Cisco IOS Software, 1841 Software (C1841-IPBASE-M), Version 12.3(14)T7, RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Mon 15-May-06 14:54 by pt_team ROM: System Bootstrap, Version 12.3(8r)T8, RELEASE SOFTWARE (fc1) System returned to ROM by power-on System image file is “flash:c1841-ipbase-mz.123-14.T7.bin” This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to [email protected]. Cisco 1841 (revision 5.0) with 114688K/16384K bytes of memory. Processor board ID FTX0947Z18E M860 processor: part number 0, mask 49 2 FastEthernet/IEEE 802.3 interface(s) 2 Low-speed serial(sync/async) network interface(s) 191K bytes of NVRAM. 31360K bytes of ATA CompactFlash (Read/Write) Configuration register is 0x2102 R1#
Step 5 Enter the show ip interface brief command to display a summary of the usability status information for each interface.
R1#show ip interface brief Interface IP-Address OK? Method Status Protocol FastEthernet0/0 192.168.1.1 YES manual up up FastEthernet0/1 unassigned YES manual administratively down down Serial0/0/0 192.168.2.1 YES manual up up Serial0/0/1 unassigned YES manual administratively down down Vlan1 unassigned YES manual administratively down down R1#
Task 10: Using Ping.
Step 1 Use the ping command to test connectivity between the R1 router and PC1.
R1#ping 192.168.1.10 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 72/79/91 ms
Each exclamation point (!) indicates a successful echo. Each dot (.) on the screen indicates that the application timed out while waiting for a packet echo from a target. The first ping packet failed because the router did not have an ARP table entry for the destination address of the IP packet. Since there is no ARP table entry, the packet is discarded. The router then sends an ARP request, receives a response, and adds the MAC address to the ARP table. When the next ping packet arrives, it will be forwarded and will be successful.
Step 2 Repeat the ping from R1 to PC1.
R1#ping 192.168.1.10 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 72/83/93 ms R1#
This time all pings are successful because the router has an entry for the destination IP address in the ARP table.
Step 3 Send an extended ping from R1 to PC1. To accomplish this, type ping at the privileged EXEC prompt and press Enter twice. Enter 192.168.1.10 as the target IP address. Accept the defaults by pressing the Enter key five times.
R1#ping Protocol [ip]: Target IP address: 192.168.1.10 Repeat count [5]: 10 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds: !!!!!!!!!! Success rate is 100 percent (10/10), round-trip min/avg/max = 53/77/94 ms R1#
Step 4 Send a ping from PC1 to R1. From PC1 go to the Desktop tab > Command Prompt. This will open a Command Prompt window. Ping R1.
C:\> ping 192.168.1.1
Step 5 Send an extended ping from PC1 to R1 using the command ping -n 10 192.168.1.1.
C:\>ping 192.168.1.1 –n 10
Task 11: Using Traceroute.
Step 1 Use the traceroute command at the R1 privileged EXEC prompt to discover the path that a packet will take from the R1 router to PC1.
R1#traceroute 192.168.1.10
Type escape sequence to abort.
Tracing the route to 192.168.1.10
1 192.168.1.10 103 msec 81 msec 70 msec
R1#
Step 2 Use the tracert command at the Windows command prompt to discover the path that a packet will take from the R1 router to PC1.
C:\>tracert 192.168.1.1 Tracing route to 192.168.1.1 over a maximum of 30 hops: 1 71 ms 70 ms 73 ms 192.168.1.1 Trace complete. C:\>
Task 12: Create a start.txt File.
The router configurations can be saved to a text (.txt) file for later use. The configuration can be copied back to the router so that the commands do not have to be entered one at a time.
Step 1 View the running configuration of the router using the show running-config command.
R1#show running-config ! version 12.3 ! hostname R1 ! ! enable secret 5 $1$J.hq$Ds72Qz86tvpcuW2X3FqBS. ! no ip domain-lookup ! interface FastEthernet0/0 description R1 LAN mac-address 0007.eca7.1511 ip address 192.168.1.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 mac-address 0001.42dd.a220 no ip address duplex auto speed auto shutdown ! interface Serial0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000 ! interface Serial0/1 no ip address shutdown ! interface Vlan1 no ip address shutdown ! ip classless ! ! ! ! line con 0 password cisco line vty 0 4 password cisco login ! end R1#
Step 2 Select the command output, right-click your mouse over the highlighted text, and select copy to copy the text.
Step 3 Open Notepad. Notepad is typically found on the Start menu under Programs, Accessories. After Notepad opens, select Paste from the Notepad Edit menu.
Step 4 Some commands will have to be edited or added before the startup script can be applied to a router. Some of these changes are:
- Adding a no shutdown command to FastEthernet and serial interfaces that are being used.
- Replacing the encrypted text in the enable secret command with the appropriate password.
- The mac-address command should be removed from the interfaces.
- The ip classless command should be removed.
- Unused interfaces can be removed.
Edit the text in the notepad file.
hostname R1 ! ! enable secret class ! no ip domain-lookup ! interface FastEthernet0/0 description R1 LAN ip address 192.168.1.1 255.255.255.0 no shutdown duplex auto speed auto ! interface Serial0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000 no shutdown ! ! ! ! line con 0 password cisco line vty 0 4 password cisco login ! end
Step 5 Save the open file in Notepad to start.txt.
Task 13: Load the start.txt File onto the R1 Router.
Step 1 Erase the current startup configuration of R1. Confirm the objective when prompted, and answer ’no’ if asked to save changes.
R1#erase startup-config Erasing the nvram filesystem will remove all files! Continue? [confirm] [OK] Erase of
Step 2 When the prompt returns, issue the reload command. Confirm the task when prompted.
Would you like to enter the initial configuration dialog? [yes/no]: no Would you like to terminate autoinstall? [yes]: Press Enter to accept default. Press RETURN to get started!
After the router finishes the boot process, choose not to use the Configuration Dialog facility.
Step 3 Enter global configuration mode.
Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 4 Select all the lines in the start.txt file that was created in Notepad and choose Edit > Copy.
Step 5 From the Terminal window, right-click your mouse in the window and choose Paste.
Step 6 After all of the pasted commands have been applied, use the show running-config command to verify that the running configuration appears as expected.
Step 7 Save the running configuration to NVRAM using the copy running-config startup-config command.
R1#copy running-config startup-config Building configuration... [OK] R1#
