PVSTP – Per VLAN Spanning Tree Protocol

October 19, 2013

The second item under the topics in the new ICND2 200-101 exam, requires that you can identify PVSTP.

PVSTP or Per VLAN Spanning Tree Protocol  does just that, each VLAN will have a different STP setup or topology, as it is done on per VLAN basis.

As the engineer this provides you with a great tool to load balance traffic over the network, using some configuration options you can decide what switches will become root.

Note: All of the interfaces on the Root switch will be DP’s

PVSTP

 

 

 

 

 

 

The above example show you how the two VLANs have a different topology.


VLAN & VTP Switch Defaults (CISCO)

August 26, 2013
  • VTP server mode
  • No VTP domain name
  • VLAN 1 and VLAN’s 1002-1005 are automatically configured (cannot be deleted)
  • All access interfaces are assigned to VLAN 1 (an implied switchport access vlan 1 command)

Creating A VLAN Step By Step

August 26, 2013

Step 1 

 a. From configuration mode, use the vlan vlan-id global configuration

command to create the VLAN and to move the user into VLAN

configuration mode.

 

b. (Optional) Use the name name VLAN subcommand to list a name

for the VLAN. If not configured, the VLAN name is VLANZZZZ,

where ZZZZ is the 4-digit decimal VLAN ID.

 

Step 2  To configure a VLAN for each access interface, follow these steps:

 a. Use the interface command to move into interface configuration

mode for each desired interface.

 

b. Use the switchport access vlan id-number interface subcommand to

specify the VLAN number associated with that interface.

 

c. (Optional) To disable trunking on that same interface, ensuring that

the interface is an access interface, use the switchport mode access

interface subcommand.


VTP Pruning

August 25, 2013

By default a cisco switch flood broadcasts (and unknown destination unicast frames) in each active VLAN out all trunks, as long as the current STP topology does not block the trunk. In most campus networks, many VLANS exist only on a few switches. Therefore it’s wasteful to forward broadcasts over all trunks, causing frames to arrive at switches that do not have any ports in that VLAN.

 

Switches support two methods by which an engineer can limit which VLAN’s traffic flows over a trunk.

 

  • Manual method using the allowed VLAN list
  • VTP Pruning

 

VTP pruning allows VTP to dynamically determine which switches do not need frames from certain VLANS and then VTP Prunes those VLANs.

 

Pruning Simply means that the appropriate switch trunk interfaces do not flood frames in that VLAN.


VLAN Database

August 25, 2013

To forward traffic for a VLAN, a switch needs to know the VLAN’s ID and it’s name and that’s the job of VTP.

The VLAN database itself is actually stored in flash as VLAN.dat 


VLAN Trunking Protocol (VTP) – Synchronisation

August 24, 2013

Synchronisation occurs when all switches learn of a new VLAN configuration and they all learn the same VLAN ID and name.


Reasons For Using VLANs

August 15, 2013
  • Create designs that allow you to group users more easily by either those working together or department
  • Allows you to segment the LAN which has the positive affect of reducing the overhead on each LAN segment
  • Provide Spanning Tree Protocol (STP) with less work to do by limiting a VLAN to an access switch
  • By keeping hosts that work together on a single VLAN, you are able to enforce stronger security by keeping the data on a individual VLAN
  • Seperate CISCO IP Phone traffic from the PC traffic

You could simplify this further:

  • Security
  • Performance
  • Design