Overview

This guide teaches how to quickly initialize Cisco routers and switches in a virtual or isolated lab while clearly separating insecure lab conveniences from proper real-world configurations. Know whether you are configuring a router, a Layer 2 switch, or a multilayer switch before you paste any block.

1. Lab Setup Versus Production Setup

Telnet sends credentials and traffic in cleartext. SSH should be used in real environments.

Sample passwords such as cisco and class must never be used in production.

2. Correct Common Configuration Mistakes

3. Fast Isolated-Lab Router Configuration

enable
configure terminal
hostname R1
no ip domain-lookup
enable secret class
service password-encryption
line console 0
logging synchronous
exec-timeout 0 0
password cisco
login
exit
line vty 0 4
logging synchronous
exec-timeout 0 0
password cisco
login
transport input telnet
exit
end
copy running-config startup-config

You may paste the whole block, including exit and end, to move cleanly between configuration modes.

4. Devices With Additional VTY Lines

Not every device has the same number of VTY lines. Some platforms use 0–4; others support 0–15.

configure terminal
line vty 5 15
logging synchronous
exec-timeout 0 0
password cisco
login
transport input telnet
exit
end
copy running-config startup-config

show running-config | section line vty
show line

5. Optional Clean Lab Output

This subsection is optional and lab-only. Do not use it in the production baseline.

configure terminal
no service timestamps debug datetime msec
no service timestamps log datetime msec
end

Disabling millisecond timestamps may make disposable lab output shorter, but it removes useful timing information for troubleshooting and syslog correlation.

6. Secure Real-World SSH Baseline

enable
configure terminal
hostname R1
no ip domain-lookup
enable secret <STRONG-ENABLE-SECRET>
username netadmin privilege 15 secret <STRONG-USER-SECRET>
ip domain-name lab.example
crypto key generate rsa modulus 2048
ip ssh version 2
service password-encryption
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
banner motd #
AUTHORIZED ACCESS ONLY
line console 0
logging synchronous
exec-timeout 10 0
login local
exit
line vty 0 4
logging synchronous
exec-timeout 10 0
login local
transport input ssh
exit
no ip http server
no ip http secure-server
end
copy running-config startup-config

Key points:

• The device needs a hostname and domain name before RSA key generation.
• SSH support depends on the IOS image and platform. Image names containing k9 generally indicate cryptographic functionality — k9 is not "IP KVM."
• RSA key-size syntax varies on some releases; verify with crypto key generate rsa ?.
• Some modern platforms support stronger SSH algorithms; older lab hardware may have limitations.

show ip ssh
show ssh
show crypto key mypubkey rsa
show running-config | section line vty

7. Layer 2 Switch Management Setup

A Layer 2 switch uses a management SVI. The management VLAN must exist, and the SVI may stay down until the VLAN has an active access port or trunk.

vlan 99
name MANAGEMENT
exit

enable
configure terminal
hostname SW1
no ip domain-lookup
interface vlan 99
ip address 192.0.2.2 255.255.255.0
no shutdown
exit
ip default-gateway 192.0.2.1
end
copy running-config startup-config

Example to make VLAN 99 active — assign at least one access port or carry the VLAN on a trunk:

interface FastEthernet0/1
switchport mode access
switchport access vlan 99
no shutdown

ip default-gateway is used because the switch is not routing IP packets between subnets.

8. Multilayer Switch Setup

After ip routing is enabled, a multilayer switch behaves like a router for inter-VLAN traffic and uses a default route, not ip default-gateway.

enable
configure terminal
ip routing
interface vlan 99
ip address 192.0.2.2 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.0.2.1
end
copy running-config startup-config

9. Quick Telnet Switching Between Lab Devices

Configure host aliases for faster lab navigation:

configure terminal
ip host R1 10.0.0.1
ip host R2 10.0.0.2
ip host R3 10.0.0.3
ip host R4 10.0.0.4
end

telnet R1

To suspend a Telnet session: press Ctrl-Shift-6, release, then press x.

telnet R2
show sessions

Typing 1, 2, 3, or 4 resumes active sessions by their dynamically assigned session numbers — the numbers are not permanently tied to specific routers.

disconnect 1

Use show sessions to inspect open sessions and disconnect or clear line as appropriate to close them.

10. Essential Verification Commands

11. Saving and Erasing Configurations

12. Copy-and-Paste Configuration Tips

• Include exit commands between sections so mode changes are explicit.
• Use end before verification or save commands.
• Paste in smaller blocks on real serial connections.
• Watch for IOS error markers beginning with %.
• Confirm every interface name before pasting — Packet Tracer names may not match physical equipment.
• Run show running-config afterward to confirm the result.
• Do not paste production secrets into screenshots, public repositories, or shared lab files.

Router setup checklist

• Hostname and no ip domain-lookup (lab) or domain name (production SSH)
• enable secret with a strong password in production
• Console and VTY lines configured with appropriate timeout and login method
• VTY transport input ssh in production; Telnet lab only
• Interfaces addressed and no shutdown where needed
• Default route or static routes configured
• Configuration saved with copy running-config startup-config

Switch setup checklist

• Identify Layer 2 vs multilayer switch role
• Management VLAN and SVI configured
• ip default-gateway (L2) or ip routing + default route (L3)
• At least one port or trunk to bring the management VLAN up
• Access/trunk ports verified with show vlan brief / show interfaces status
• Configuration saved