Vtp status not updating 100 percent free dirty chat sites

I’ll use the following topology: All interfaces between the switches are configured as trunks.

First we will try to enable VTP version 1 on one of our switches: SW1#show vtp devices Retrieving information from the VTP domain. VTP Feature Conf Revision Primary Server Device ID Device Description ------------ ---- -------- -------------- -------------- ---------------------- VLAN No 6 0019.569d.5700 0011.214e.d180 SW3 VLAN No 6 0019.569d.5700 0011.bb0b.3600 SW2 You can run this command on any of your switches, it will show all VTP members (not just the directly connected ones like CDP does).

Let’s see if we are able to synchronize some VLANs.

We’ll start with something simple: No problem at all! VTP version 3 is able to synchronize private VLAN information.

To synchronize MST information we have to use the “MST” feature.

As you can see the VTP mode for this feature is currently transparent.

Each VLAN is created in the local switch's database for use.

If a VLAN is not known to a switch, that switch cannot transfer traffic across any of its ports for that VLAN.

VLANs are created by number, and there are two ranges of usable VLAN numbers (normal range 1–1000 and extended range 1025–4096).

Because these are not widely used topologies, the options and descriptions of Token Ring and FDDI VLAN configuration and parameters have not been included in this book.

For information on Token Ring or FDDI VLANs, refer to lan/cat5000/rel_6_3/config/

A server is configured on VLAN 2 on the Cisco Meraki Switch.

You must have an account to comment. Please register or login here!