Exploring Networking with Cisco Packet Tracer

After completing the Cisco Packet Tracer course, I moved on to Exploring Networking with Cisco Packet Tracer.

This course covered the setup, management, and monitoring of small office networks using Packet Tracer. In the first module, it introduced structured cabling, focusing on organizing network infrastructure using tools like wall mounts and color-coded cables. It also covered wireless technologies such as Wi-Fi, Bluetooth, and cellular data. Key device configuration tabs, including the Command Line Interface (CLI), were explained for configuring Cisco devices. The second module explored network monitoring using Packet Tracer’s Simulation mode to check connectivity, security, and service functionality. It highlighted troubleshooting via Protocol Data Units (PDUs) and discussed centralized management through Network Controllers for configuring and monitoring devices.

I have to say, while I wanted to follow the advice and continue using Packet Tracer, it can feel slow and frustrating at times. The course starts with some basic Ethernet connections, which may be helpful if you’ve never dealt with networking in real life. However, having done this in the past, both at home during renovations and at the office, I found the “click adventure” exercises less engaging.

That said, by the end of the first module, things start to get more interesting as you return to working with the CLI (Command Line Interface) instead of relying solely on click-and-drop operations. Although the exercises are basic, they were still valuable for me since I’ve only ever used home networking devices and had limited exposure to Unifi.

I made some notes from the exercises in case I need them for future reference.

Connect to the Device Using a Console Connection

1. Open Terminal Application:

   • Access the switch CLI from the laptop.
   • Accept the defaults in Terminal Configuration, and press ENTER when prompted (“Press RETURN to get started!”).

2. View Available Commands (User EXEC Mode):

   • Use ? to display a list of available commands in User EXEC mode.
     • Switch> ?

3. Access Privileged EXEC Mode:

   • Use enable to switch to Privileged EXEC mode.
     • Switch> enable
     • Switch# (similar to how you would use sudo su in Linux).

4. View Available Commands (Privileged EXEC Mode):

   • Use ? to display the commands available in Privileged EXEC mode.
     • Switch# ?

5. View Running Configuration:

   • Use show running-config to display the current switch configuration.
     • Switch# show running-config

---

Copy Configuration Information to the Device

1. Enter Global Configuration Mode:

   • Use configure terminal to enter global configuration mode.
     • Switch# configure terminal
     • Switch(config)#

2. Update Device Name:

   • Use hostname Office-SW2 to set a new hostname for the switch.
     • Switch(config)# hostname Office-SW2

3. Set Console Password:

   • Use line con 0 to access console line configuration.
   • Set the password with password Cisco123 and enable password protection with login.
     • Office-SW2(config)# line con 0
     • Office-SW2(config-line)# password Cisco123
     • Office-SW2(config-line)# login

4. Exit Configuration Mode:

   • Use end to exit global configuration mode.
     • Office-SW2(config-line)# end
     • Office-SW2#

5. Test Console Password:

   • Use exit to return to the prompt and test the console password by re-entering it (e.g., Cisco123).

---

Save the Updated Configuration

1. Enter Privileged EXEC Mode:

   • Use enable to access Privileged EXEC mode.
     • Office-SW2> enable
     • Office-SW2#

2. Save Running Configuration to Startup Configuration:

   • Use copy running-config startup-config to save the current configuration to the startup configuration.
     • Office-SW2# copy running-config startup-config
     • Confirm with ENTER.

3. Reload the Device:

   • Use reload to reboot the device and test the saved configuration.
     • Office-SW2# reload
     • Confirm with ENTER.

4. Verify Saved Configuration:

   • Ensure you are prompted to enter the console password (e.g., Cisco123) upon restart to confirm the configuration was saved correctly.