Day 1 Demos

Matches no specific book examples.

It pre-configures the PCs into the same subnet just in case.

No pre-config on the switch

Follow these steps:

  1. Login (no password)
  2. Show interfaces
  3. Show interfaces status
  4. Show mac address-table
  5. Show vlan
  6. ?
  7. Show ?
  8. Show mac ?

 

Then show slides about config process, config modes, and then demo some configuration:

  1. Configure terminal
  2. ?
  3. Interface G0/1
  4. ?
  5. Description connected to PC1
  6. Exit
  7. Hostname Fred
  8. Exit

 

Finally, demo seeing the config files:

  1. Show run
  2. Show start – see difference?
  3. Copy run start to save the config.

Part 2 Demo 2:

Put all PCs in the same subnet just in case.

No pre-config.

DO NOT PING FIRST – START W/ EMPTY MAC TABLE

 

Follow these steps:

  1. Show the interfaces using PT UI
  2. USER MODE TO START
  3. Interface status: show interfaces status
  4. MAC table: show mac address-table
  5. Clear MAC table: clear mac address-table
  6. Upgrade to enable mode: enable
  7. Repeat the clear: clear mac address-table

 

Now generate traffic

  1. Connect to PC1 command prompt.
  2. Ping PC2: ping 10.1.1.2
  3. MAC table now has two MACs: show mac address-table
  4. Ping the other two:: ping 10.1.1.3 and 4
  5. MAC table now has four MACs: show mac address-table
  6. Repeat the clear: clear mac address-table
  7. MAC table now has 0 MACs: show mac address-table

Idea: start w/ switch w/ no non-default config. (FYI, pkt is configured w/ vtp mode transparent But it doesn’t matter.) Then show state, config a VLAN, show state, config a 2nd vlan a different way, show state.

 

Show initial status on switch SW1

  1. Use show vlan brief to see only default VLANs.
  2. Use show interfaces status to see all ports assigned to VLAN 1.
  3. Use show vlan brief again to focus on the list of ports.
  4. Use show running-config and look at ports Fa0/11-16. (default)

 

Configure VLAN 2 like Vol 1 Example 8-2:

Vlan 2

Name CCNA0002

Exit

Interface range fa0/13-14

Switchport access vlan 2

Switchport mode access

end

 

Show results, same commands

  1. Use show vlan brief – see now VLAN 2, w 2 ports there.
  2. Use show vlan id 2 – to see detail.
  3. Use show interfaces status to see all ports assigned to VLAN 1 except fa0/13-14.
  4. Use show running-config and look at ports Fa0/11-16.

 

Configure VLAN 3 like Vol 1 Example 8-4, where VLAN is auto-created:

Interface range fa0/15-16

Switchport access vlan 3

Switchport mode access

end

Show results, same commands

  1. Use show vlan brief – see now VLAN 3, w 3 ports there.
  2. Use show interfaces status to see all ports assigned to VLAN 1 except those assigned in lab.
  3. Use show running-config and see the vlan 3 command is there, even though you didn’t type it.

Idea: start w/ VLANs pre-configured per example in the book (8-10) and figure 8-10, and show the simple trunk config. Focus on before and after status, admin and oper.

 

Show initial status on switch SW1

  1. Use show vlan brief to see current VLANs and ports that match the figure.
  2. Use show interfaces g0/1 switchport to see operations trunk state as access, configured as dynamic auto.
  3. Use show interfaces trunk to see no ports listed.
  4. Use show running-config and look at port G0/1. All default.

 

Configure dynamic desirable like Vol 1 Example 8-6:

Int g0/1

Switchport mode dynamic desirable

end

 

Show results, same commands

  1. Use show interfaces g0/1 switchport to see operational trunk state as trunk, configured as dynamic desirable.
  2. Use show interfaces trunk to see G0/1 listed.

Day 2 Demos

PKT file pre-configures IP addresses on routers R2 and R3, but not R1.

 

Demo Part 1: These steps from R1:

  1. From PT UI, hover over each router to show the IP addresses configured on R2, R3, but not R1.
  2. Commands from Chapter 15 on R1:
    1. show interfaces
    2. show interfaces g0/1/0
    3. show ip interface brief.
    4. Discuss status codes, different formats.
  3. Commands about IP:
    1. Show protocols,
    2. show ip protocols,
    3. show run
    4. – see absence of IP addresses.
    5. Show ip route connected – see zero routes.

 

  1. Configure R1 interface IP addresses:
    1. G0/0 w/ 16.1.1/24
    2. S0/0/0 w/ 16.4.1/24
    3. G0/1/0 w/ 172.16.5.1/24
  2. Repeat
    1. show protocols
    2. show ip protocols
    3. show interfaces
    4. show interfaces g0/1/0
    5. show ip interface brief
    6. see IP addresses, no change in interface state.
  3. Run Show ip route connected – take your time here. Discuss routing table features.
  4. Issue ping 172.16.1.9 (R1 to PC1) to add an ARP table entry.
  5. Do a show ip arp on R1.

The entire network is pre-configured for OSPF. Goal: review config and show.

First, review the config on R1.

Then, review the shows on R1 that confirm the config.

Then see the IP routing table and OSPF database on R1.

 

Use this file: (CCC-P3-OSPF-int.pkt)

Derived from Vol 1 Example 20-13

 

 

These steps:

  1. From Router R1, use show running-config and look at all four interfaces.
  2. Then look at router ospf 1.
  3. Then use show protocols (which shows IP addresses) and then show ip protocols (which shows RP details.)
  4. PT quirk – incorrect output for “Routing on Interfaces Configured Explicitly”
  5. Do a show ip ospf to see the process.
  6. Do a show ip ospf interfaces brief to list the enabled interfaces (PT does not support?)
  7. Do a show ip route to see the OSPF routes,
  8. Do a show ip route ospf.
  9. Finally, a show ip ospf database to see the database. Just show the existence of four Type 1 LSAs, one per router.

Day 3 Demos

Demo uses the topology from Volume 1 Examples 25-1, 2, and 3

R2 and R3 have GUA config already

In demo, configure R1 just like in Example 25-1:

 

Demo 1 Part 1: Verify: No IPv6 addresses.

Commands to show:

  1. Show ipv6 route – nothing there.
  2. Show running-config | include ipv6 – nothing there
  3. Show interfaces – no mention of IPv6 addresses
  4. Show ipv6 interface g0/0 – blank line
  5. Show ipv6 interface – all blank lines
  6. Show ipv6 interface brief – all interfaces, but no IPv6 addresses

 

Demo 1 Part 2: Configure IPv6 GUA

Configure just like Example 25-1 (Vol 1) – copy and paste these commands!

 

Ipv6 unicast-routing

Interface gi0/0

Ipv6 address 2001:db8:1111:1::1/64

!

Interface serial0/0/0

Ipv6 address 2001:db8:1111:4::1/64

!

Interface Gi0/1/0

Ipv6 address 2001:db8:1111:5::1/64

 

 

Demo 1 Part 3: Verify the IPv6 addresses

Commands to show:

  1. Show ipv6 route – 3 connected, 3 local
  2. Show running-config | include ipv6 – same commands you just configured
  3. Show interfaces
    1. No mention of IPv6 addresses
    2. Show interfaces | include ipv6 – nothing!
  4. Show ipv6 interface g0/0
    1. Highlight the GUA
    2. Highlight the subnet
    3. Ignore the LLA
  5. Show ipv6 interface – detail, for 3 interfaces only
  6. Show ipv6 interface brief – all interfaces, shows GUA, not prefix length

So, now all three routers have GUAs, but there’s no routing protocol

 

Focus on showing the LLAs!!

 

 

Demo 2 Part 1: LLA on G0/0

Commands to show:

  1. Show interfaces g0/0 – Find and see MAC address
  2. Show ipv6 interface brief – see LLA shown for G0/0 – note IID
  3. Spend time comparing the MAC and the IID
  4. Look at the fe80:: to begin – always.
  5. Show ipv6 route – no routes that begin fe80. No routes for it.

 

Demo 2 Part 1: LLA on G0/1/0

Commands to show – same ones, different interface

  1. Show interfaces g0/1/0 – Find and see MAC address
  2. Show ipv6 interface brief – see LLA shown for G0/1/0 – note IID
  3. Spend time comparing the MAC and the IID
  4. Look at the fe80:: to begin – always.

 

 

Demo 2 Part 3: TIME PERMITTING – ping R3’s WAN LLA

Commands to show – same ones, different interface

  1. On router R3: show ipv6 interface brief – copy the LLA
  2. On router R1: ping <paste> – prompts for interface – type gigabitethernet0/1/0
    1. Works!
  3. On router R1: ping <paste> – prompts for interface – type gigabitethernet0/0
    1. Fails! The LLA does not exist on the LAN.

This one has the ACL PRECONFIGURED, as in Example 2-1, so it’s all show commands.

All action on R2.

 

Demo 3 Part 1: Examine the config

Demo steps on R2:

  1. Do show running-config to display the ACL config
  2. Do show running-config | include access-list to display the ACL config
  3. Do show ip access-lists,
    1. See same config
    2. See line numbers
    3. See matches
  4. Do show access-lists, see it repeated
  5. Do show ip interface S0/0/1, see it enabled

 

 

Demo 3 Part 2: Test the ACL

From PC A and B:

  1. Ping tests
    1. From host A: ping 10.2.2.1 works
    2. From host B: ping 10.2.2.1 fails
  2. Trace tests
    1. From host A: tracert 10.2.2.1 works
    2. From host B: tracert 10.2.2.1 fails, gets to R2 (10.4.4.2).
  3. Do show ip access-lists,
    1. See matches

Demo! Use CGPTL for Vol 2 Example 6-2.

It assumes the config in Vol 2 Example 6-1, which is in the slides. Launch after showing that slide.

 

Demo 4 Part 1: Port Security Config

Look at the config:

  1. From SW1, issue a show running-config to see port security config.
    1. See sticky configured on F0/2
    2. See no specific MAC addresses configured on F0/2
  2. Draw attention to F0/2 – the one with sticky on it.
  3. Connect to Server2 CLI, issue a ping 10.1.1.1 (Server1). See, it fails, FYI because F0/2 is shutdown.
  4. Configure F0/2:
    1. Tell them: shutdown at beginning so it’s easier to demo.
    2. Do a no shut on the interface. So it will sticky learn.
    3. Tell them – I also enabled portfast to speed up the demo.

 

 

 

Demo 4 Part 2: Verify and explore sticky learning

 

Note that the demo begins w/ F0/2 shutdown so we can do a no shut during the demo to demonstrate sticky learning. So the .pkt, vs. the book, is MODIFIED to shutdown F0/2 so the demo flows better.

 

  1. Connect to Server2 CLI, issue a ping 10.1.1.1. See, it works, and keeps working – not filtered.
  2. Back to switch, show run, see the sticky learned MAC on F0/2.
    1. Note the specific MAC address now appears.
  3. Go back to Server2 in PT, and change the MAC to have some 3333s in it. This will cause the switch to learn a 2nd MAC and cause a port sec violation.
  4. From Server 2, try the ping again.
  5. Go back to the Switch and explore why the interface failed.
    1. See the log messages
    2. show interfaces status
    3. show interfaces f0/2.
  6. Aside: Do a show mac address-table dynamic (none) and show mac address-table static (some) to show how on interfaces w/ port-sec, all MACs appear as static.

Day 4 Demos

All is pre-configured. It’s about seeing the output and comparing the output.

Do it all from SW2.

 

  1. Show cdp neighbors and show lldp neighbors.
    1. Compare the output. EG B and S for switches, for example.
  2. Show cdp neighbors detail and Show lldp neighbors detail.
    1. Examine R1’s CDP detail. See platform. Examine LLDP, see platform – tell them that’s an inconsistency, real devices would not show the platform.
    2. See two lists of capabilities w/ LLDP.
  3. Show cdp and show lldp – compare
  4. Show run | include lldp and show run | include cdp
    1. note only one config command on LLDP switch, none on CDP switch.