STEP 11 β€” Interface Awareness (KNOW WHAT EACH PORT IS FOR)

Why this step matters

Before configuring anything, you must know:

  • which interface is LAN
  • which is WAN
  • which goes upstream / downstream

This prevents 90% of CCNA mistakes.


πŸ”Ή 11.1 Head Office Router β€” HO-R1

Open HO-R1 β†’ CLI and just look, don’t configure:

show ip interface brief

Conceptual role of interfaces:

  • GigabitEthernet0/0 β†’ LAN side (to DIST-SW1)
  • Serial0/x/x β†’ WAN side (to BR-R2)
  • GigabitEthernet0/1 (if connected to ISP) β†’ Internet-facing

πŸ‘‰ HO-R1 = LAN ↔ WAN boundary


πŸ”Ή 11.2 Branch Router β€” BR-R2

On BR-R2 β†’ CLI:

show ip interface brief

Roles:

  • Serial0/x/x β†’ WAN (to HO-R1)
  • GigabitEthernet0/1 β†’ Branch LAN (to BR-SW4)

πŸ‘‰ BR-R2 = branch gateway


πŸ”Ή 11.3 ISP Router β€” ISP-R0

On ISP-R0:

show ip interface brief

Role:

  • Interfaces here represent public / ISP-side
  • We won’t do much config on this device

πŸ‘‰ ISP-R0 = outside world


πŸ”Ή 11.4 Distribution Switch β€” DIST-SW1

On DIST-SW1 β†’ CLI:

show interfaces status

What to identify:

  • Port to HO-R1 β†’ uplink
  • Port to BR-R2 β†’ routed/uplink
  • Ports to HQ-SW2 / HQ-SW3 β†’ access-switch uplinks

πŸ‘‰ DIST-SW1 = traffic aggregator


πŸ”Ή 11.5 Access Switches

HQ-SW2

  • Ports β†’ PCs (users)

HQ-SW3

  • Ports β†’ Server
  • Ports β†’ Wireless router

BR-SW4

  • Ports β†’ Branch PCs
  • One uplink β†’ BR-R2

πŸ‘‰ Access switches = end devices only


🧠 One-sentence summary (lock this in)

Routers connect networks; switches connect devices; serial = WAN; Ethernet = LAN.


🚫 Still NOT doing

❌ No IP addresses
❌ No VLANs
❌ No routing
❌ No DHCP

Leave a Reply

Your email address will not be published. Required fields are marked *

Buy Me a Coffee