Introduction
This lab is designed to help you gain the skills required for the practical portion of the CCENT certification. The tasks involve configuring a Cisco switch from startup, including setting up initial configurations and securing the device.
Assignment
Your task is to perform a switch startup and initial configuration using a real Cisco device. You will console into the switch, erase any existing configurations, and set up the device with a basic configuration, including setting passwords and enabling IP services.
Conditions
- Devices: The devices in the diagram below include the routers and switches that you will control. In some labs, additional devices simulate service provider infrastructure, which will be specified if applicable. All devices you access in these labs are real Cisco routers and switches, with no simulations involved.
Note: To access the console of the routers and switches, click on the device tab on the left side of the webpage. If you encounter a blank screen, click inside the window and press the return/enter key to activate the console port.
Task Index
- Performing Switch Startup and Initial Configuration
Step 1: Console into NYCORE1. Enter the enable command to access privileged exec mode.
- Action:shellCopy codeNYCORE1>enable NYCORE1#
- Explanation: You should see the prompt change from NYCORE1> (user mode) to NYCORE1# to indicate that you are in privileged exec mode. From privileged exec mode, you can enter any available show or debug commands and access global configuration mode.
Step 2: Erase the startup configuration on NYCORE1 and reload the device.
- Action:vbnetCopy codeNYCORE1#erase startup-config
(PRESS ENTER to confirm)
NYCORE1#reload
(TYPE no when asked to save configuration)
(PRESS ENTER to confirm reload)
- Result: The startup configuration is erased, and the switch is reloaded, allowing you to configure the switch from scratch.
- Explanation: RAM stores the running configuration, which is volatile and flushed when the device is rebooted. NVRAM, which is non-volatile, stores the startup configuration. Erasing the startup configuration allows you to start fresh.
Step 3: After NYCORE1 reloads, press Enter. When prompted to enter the configuration dialog, answer yes.
- Action:bashCopy codeWould you like to enter the initial configuration dialog? [yes/no]: yes
- Explanation: The initial configuration dialog guides you through basic setup questions. Cisco engineers typically do not use this dialog, but it can be helpful for creating a basic configuration, especially for those unfamiliar with Cisco switches.
Step 4: On NYCORE1, answer yes to entering basic management setup.
- Action:bashCopy codeWould you like to enter basic management setup? [yes/no]: yes
- Explanation: Basic setup configures only one interface, making it the preferred option for this lab.
Step 5: Change the hostname to NYCORE1.
- Action:mathematicaCopy codeEnter host name [Switch]: NYCORE1
- Explanation: By default, the hostname on a Cisco switch is “Switch.” You will change it to “NYCORE1.”
Step 6: On NYCORE1, enter “cisco” as the enable secret password.
- Action:bashCopy codeEnter enable secret: cisco
- Result: Be careful not to mistype or add an extra space. This password provides security for privileged exec mode.
- Explanation: The enable secret password secures privileged exec mode, requiring users to enter the password to gain access.
Step 7: On NYCORE1, enter “cisco1” as the enable password.
- Action:bashCopy codeEnter enable password: cisco1
- Explanation: The enable password also secures privileged exec mode, but if both enable secret and enable passwords are configured, only the enable secret is used.
Step 8: Enter “cisco” as the virtual terminal password for NYCORE1.
- Action:arduinoCopy codeEnter virtual terminal password: cisco
- Explanation: The virtual terminal (VTY) password is used to authenticate users attempting to telnet into the switch.
Step 9: Answer no when asked to configure SNMP Network Management.
- Action:perlCopy codeConfigure SNMP Network Management? [no]: no
- Explanation: The default answer is “no,” which is indicated by the brackets. Pressing Enter will confirm this.
Step 10: Review the interface summary. Press the space bar to page down through the interfaces until you reach the end of the list.
- Action:vbnetCopy code(PRESS SPACEBAR UNTIL YOU SEE THE MANAGEMENT INTERFACE)
- Explanation: Interfaces will show as up/up, down/down, or administratively down/down. The VLAN 1 interface, which is a logical management interface, is typically disabled by default.
Step 11: Enter “VLAN1” when asked for an interface name for connecting to the management network.
- Action:vbnetCopy codeEnter interface name used to connect to the management network from the above interface summary: vlan1
- Explanation: VLAN 1 is the default management interface on a Cisco switch.
Step 12: Answer yes when asked to configure IP on this interface.
- Action:csharpCopy codeConfigure IP on this interface? [no]: yes
Step 13: Enter the IP address 10.1.1.2 when prompted.
- Action:kotlinCopy codeIP address for this interface: 10.1.1.2
Step 14: Enter 255.255.255.0 as the subnet mask.
- Action:kotlinCopy codeSubnet mask for this interface [255.0.0.0]: 255.255.255.0
Step 15: Answer no to enabling as a cluster command switch.
- Action:bashCopy codeWould you like to enable as a cluster command switch? [yes/no]: no
Step 16: Review the configuration that was created based on your inputs. Page down using the space bar.
- Action:cssCopy code(PRESS SPACEBAR UNTIL YOU RECEIVE THE MENU)
- Explanation: The configuration script displays the commands generated based on the information provided.
Step 17: Save the configuration to NVRAM and exit.
- Action:cssCopy codeEnter your selection [2]: 2NYCORE1>
- Explanation: Selecting 2 saves the configuration to NVRAM, ensuring it remains after a reload.
Step 18: Enter global configuration mode on NYCORE1.
- Action:shellCopy codeNYCORE1>enablePassword: ciscoNYCORE1#config tNYCORE1(config)#
- Explanation: Global configuration mode allows you to make changes affecting the entire device.
Step 19: Configure the default gateway: 10.1.1.1.
- Action:scssCopy codeNYCORE1(config)#ip default-gateway 10.1.1.1
Step 20: Configure the console port password as “cisco” and enable security.
- Action:arduinoCopy codeNYCORE1(config)#line con 0NYCORE1(config-line)#password ciscoNYCORE1(config-line)#login
Step 21: View your running configuration. Note which passwords are readable.
- Action:arduinoCopy codeNYCORE1(config-line)#endNYCORE1#show run
- Result: The enable secret password is encrypted, but other passwords may be in clear text.
Step 22: Verify that your user mode and privileged mode passwords are working. Exit out of NYCORE1, log back in, and enter privileged exec mode.
- Action:shellCopy codeNYCORE1#exit(PRESS ENTER TWICE)
User Access Verification
Password: ciscoNYCORE1>enablePassword: ciscoNYCORE1#
Step 23: Configure password encryption service to secure all clear text passwords.
- Action:arduinoCopy codeNYCORE1#config tNYCORE1(config)#service password-encryption
Step 24: View the running configuration again. Verify that passwords are now encrypted.
- Action:arduinoCopy codeNYCORE1(config)#endNYCORE1#show run
Step 25: Configure a message of the day (MOTD) banner warning unauthorized users not to log in.
- Action:arduinoCopy codeNYCORE1#config tNYCORE1(config)#banner motd $UNAUTHORIZED ACCESS PROHIBITED.
$
Step 26: Exit out of NYCORE1 to verify that your banner is configured correctly.
- Action:shellCopy codeNYCORE1(config)#exitNYCORE1#exit(PRESS ENTER TWICE)
Step 27: Remove the enable secret, enable password, and console password. Also, remove the login command from the console.
- Action:arduinoCopy codeNYCORE1>enable
Password: cisco
NYCORE1#config tNYCORE1(config)#no enable secretNYCORE1(config)#no enable passwordNYCORE1(config)#line con 0NYCORE1(config-line)#no passwordNYCORE1(config-line)#no login
Step 28: Compare your running configuration with your startup configuration.
- Action:arduinoCopy codeNYCORE1(config-line)#endNYCORE1#show runNYCORE1#show start
Step 29: Copy the running configuration to the startup configuration.
- Action:arduinoCopy codeNYCORE1#copy run startDestination filename [startup-config]? (Press Enter)
Step 30: Verify that the configuration is saved in NVRAM.
- Action:sqlCopy codeNYCORE1#show start
Step 31: Erase the startup configuration.
- Action:vbnetCopy codeNYCORE1#erase startup-config
(PRESS ENTER to confirm)
Result: The startup configuration is erased, marking the completion of the lab.
Summary
In this lab, you completed the following tasks:
- Task 1 - Performing Switch Startup and Initial Configuration
This lab provided hands-on experience in configuring a Cisco switch from startup, erasing existing configurations, setting up new configurations, and securing the device.