2.1.f Implement and troubleshoot spanning-tree

Screenshot from 2013-04-06 09:01:27

the first step was to establish point to point connectivity… i achieved that to connected devices only as i did not want to assume any configuration… it is time consuming in the initial set up with gns3 and the switched network… the frame-relay perspective from r2..

R2(tcl)#foreach address {
+>(tcl)#120.100.123.1
+>(tcl)#120.100.123.3
+>(tcl)#120.100.25.5
+>(tcl)#} { ping $address }

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 120.100.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/36/48 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 120.100.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/22/32 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 120.100.25.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/24 ms

i threw in some vty stuff just to get around, domain names and ntp, but little else…

R6#sh cdp neigh
Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge
S – Switch, H – Host, I – IGMP, r – Repeater

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
SW1              Fas 0/0            134        R S I      WS-C3560- Fas 0/6
SW2              Fas 0/0            138        R S I      WS-C3560- Fas 0/4
R5.lab.local     Fas 1/0            173        R S I      3640      Fas 1/0

i didn’t care too much about his interface assignments for the routers although the vlans and ip addresses are exact…

l2 begins…

Configure your switches as a collapsed backbone network with Switches 1 and 2 performing core and distribution functionality and Switches 3 and 4 as access switches in your topology. Switches 3 and 4 should connect only to the core switches. (2 points)

i can only guess at how i would receive the topology in a real setting, and i built trunks and configured native vlans right away because native vlan mismatches drive me wild… so for this first task, i simply shut down one side of the sw3-4 connections… i turned on ip routing for sw1-2 early on for accessibilty…

ccie_lab_l2bb

Switch 1 and 2 should run spanning tree in 802.1w mode; Switches 3 and 4 should operate in their default spanning-tree mode. (2 points)

SW3#sh spann summ
Switch is in pvst mode

SW1(config)#do sh spann summ
Switch is in rapid-pvst mode

SW2(config)#spann mode rapid
SW2(config)#do sh spann summ
Switch is in rapid-pvst mode

Configure Switch 1 to be the root bridge and Switch 2 the secondary root bridge for VLANs 1 and 300. Ensure that Switches 3 and 4 can never become root bridges for any VLANs for which Switch 1 and Switch 2 are root bridges by configuring only Switches 1 and 2. (2 points)

SW1(config)#spann vlan 1,300 root prim

SW2(config)#do sh spann vlan 1

VLAN0001
Spanning tree enabled protocol rstp
Root ID    Priority    24577
Address     0016.c706.9680
Cost        19
Port        6 (FastEthernet0/4)
Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

Bridge ID  Priority    28673  (priority 28672 sys-id-ext 1)
Address     0016.479e.5f80
Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
Aging Time  300 sec