cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1358
Views
15
Helpful
12
Replies

Help with VTP Simulation on CCNA Exam

rangelo001
Level 1
Level 1

On the CCNA 840-601 there is a 4 switch simulation to which you can only console to SW3. How do I tell which is the root bridge, when I only have access to SW3? How do I tell where SW3 got it's VTP updates? Thanks!!

1 Accepted Solution

Accepted Solutions

Jon Marshall
Hall of Fame
Hall of Fame

Hi

Execute the following command

sh vtp status

The last line should give you the switch from which the update came. Here's an example from our lab

=============================================

lab_sw1>en

Password:

lab_sw1#sh vtp status

VTP Version : 2

Configuration Revision : 44

Maximum VLANs supported locally : 1005

Number of existing VLANs : 31

VTP Operating Mode : Client

VTP Domain Name : LAB

VTP Pruning Mode : Disabled

VTP V2 Mode : Disabled

VTP Traps Generation : Disabled

MD5 digest : 0xF4 0xBE 0x39 0xC4 0x2F 0x30 0x3D 0x89

Configuration last modified by 10.15.1.3 at 8-28-07 07:43:17

=============================================

As for the root bridge you can tell the bridge ID from a "sh spanning-tree" eg.

=============================================

HQ-FTZ-F00-SW1#sh spanning-tree vlan 10

VLAN0010

Spanning tree enabled protocol ieee

Root ID Priority 32778

Address 000a.b8b3.a980 <-- mac-address of ROOT bridge

Cost 19

Port 24 (FastEthernet0/24)

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32778 (priority 32768 sys-id-ext 10)

Address 000e.84e1.f680

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Aging Time 300

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- ------------------------------

Fa0/1 Desg FWD 19 128.1 Edge P2p

Fa0/2 Desg FWD 19 128.2 Edge P2p

Fa0/24 Root FWD 19 128.24 P2p

=============================================

HTH

Jon

View solution in original post

12 Replies 12

Jon Marshall
Hall of Fame
Hall of Fame

Hi

Execute the following command

sh vtp status

The last line should give you the switch from which the update came. Here's an example from our lab

=============================================

lab_sw1>en

Password:

lab_sw1#sh vtp status

VTP Version : 2

Configuration Revision : 44

Maximum VLANs supported locally : 1005

Number of existing VLANs : 31

VTP Operating Mode : Client

VTP Domain Name : LAB

VTP Pruning Mode : Disabled

VTP V2 Mode : Disabled

VTP Traps Generation : Disabled

MD5 digest : 0xF4 0xBE 0x39 0xC4 0x2F 0x30 0x3D 0x89

Configuration last modified by 10.15.1.3 at 8-28-07 07:43:17

=============================================

As for the root bridge you can tell the bridge ID from a "sh spanning-tree" eg.

=============================================

HQ-FTZ-F00-SW1#sh spanning-tree vlan 10

VLAN0010

Spanning tree enabled protocol ieee

Root ID Priority 32778

Address 000a.b8b3.a980 <-- mac-address of ROOT bridge

Cost 19

Port 24 (FastEthernet0/24)

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32778 (priority 32768 sys-id-ext 10)

Address 000e.84e1.f680

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Aging Time 300

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- ------------------------------

Fa0/1 Desg FWD 19 128.1 Edge P2p

Fa0/2 Desg FWD 19 128.2 Edge P2p

Fa0/24 Root FWD 19 128.24 P2p

=============================================

HTH

Jon

Jon,

Thank you very much for your quick reply! So in order to find the root bridge, would I then do a Show mac-address-table to see where that mac address is coming from? The questions was to indicate which of the four switches was the root. Or is their another way to trace back that mac address to the root bridge/switch.

Ray

The Root bridge is listed as being source from port 24.

Just issue show cdp neighbor and see the device name being announced on port 24.

Excellent, thanks.

rossua994
Level 1
Level 1

Hi, I have encountered a similar problem with a 4 switch simulation, which gives access to only SW3, and asks which switch is the root bridge.

By running show spanning-tree command I can see the MAC address of the root bridge, and the root port of SW3. I can then do show cdp neighbors and see the device directedly connected to this root port.

The problem is that this directly connected device is not necessarily the root bridge. The lowest cost BPDU from the root bridge comes in VIA this device to SW3, but this doesn't necessarily mean the root bridge IS this device.

With the information available it seems to me not possible to deduce for sure which is the root bridge. Or is there something I am missing here ?

You aren't missing anything. You need to treat it as a hop-by-hop discovery.

If you see the root is being sourced via port x, issue a cdp on that port and hop onto that switch.

Repeat the process on that switch (perform the spanning-tree command & cdp combo).

HTH,

Hi, thanks for your reply. In the question it does not allow you to telnet or console onto the next switch. Only one switch out of the four can be connected to. It is this reason I think it is not possible to determine the root switch for sure without further information.

You can provide the MAC address of the switch as displayed on the show spanning-tree command.

The actual switch-name will be unknown, though. That information can only be obtained via CDP.

Thats what I thought. The multiple choice answer will only accept a switch name though. I attach a diagram of the topology. Only SW-AC3 can be connected to, via the console connection shown.

If the MAC address to host cannot be verified, then the fourth switch must be the source.

Yes,

The old if it didn't originate from my neighbors, then it must be from their neighbor. Good thinking, tough to fathom through during a test. I think this resolves the issue.

Thanks.

This resolved my issue. Not sure how to indicate it in this post.

Thanks, again.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco