cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2811
Views
20
Helpful
11
Replies

VTP pruning

sivam siva
Level 3
Level 3

HI 

What is the difference between  VTP pruning & VLAN pruning in trunk, both are configured by manually and both features prevents the VLAN frame in trunk, then what is the difference ?

Thanks in advance 

1 Accepted Solution

Accepted Solutions

Hello,

 

as Alex explained, VTP pruning is a lot easier to configure, since you only need to enable it on the VTP server. In addition, the 'switchport trunk allowed' command is static, that is, should there be a port connected to a Vlan that you actually want to traverse the trunk, you will have to manually change that, while VTP would adjust dynamically...

View solution in original post

11 Replies 11

Hello,

 

not sure what you mean...VLAN pruning is done through VTP. Or do you mean 'trunk allowed vlan' vs VLAN pruning ?

Yes

Alex explained  the concepts that I can understand, my question is both pruning VLAN through VTP or on the trunk itself ( ex: sw tr allowed vlan x) need to be configured manually , 

So what is the difference ? What VTP simplifies the administrator overhead in this scenario.

Thank you 

Alex Pfeil
Level 7
Level 7
VLAN trunking protocol is a Cisco proprietary way of managing VLANs across a network. VTP pruning is a feature of VTP that will automatically remove VLANs from trunks on switches where the VLAN is not used.
VLAN pruning would be the practice of manually allowing specific VLANs across a trunk with the switchport trunk allowed vlan command.
The best practice is to set all switches to VTP mode transparent and manually add all of the VLANs that are needed on each device. You then trunk each device and allow the necessary VLANs.

Please mark helpful posts.

I feel Alex's post is actually the best complete answer.

Rising Star is a Shining Star

Hello,

 

as Alex explained, VTP pruning is a lot easier to configure, since you only need to enable it on the VTP server. In addition, the 'switchport trunk allowed' command is static, that is, should there be a port connected to a Vlan that you actually want to traverse the trunk, you will have to manually change that, while VTP would adjust dynamically...

Got it ,thank you 

Hello
I personally would NEVER use dynamic vtp pruning, I have seen instances even when a remote switch has had ports related to a specific vlan or even allowed to traverse the trunk vtp pruning has dynamically removed it and caused outage

Manually pruning your vlans is in my opinion the best option - It provides a total controllable approach to vtp pruning on the trunks

Enabling vtp pruning dynamically it is the easiest option to deploy granted but I have found it not deterministic enough to trust which I have found to my cost.

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

I agree.  A year ago we when to 'allowed vlan' per interface.  However, I have an issue that is just creeping up.  I will repost as a new issue, but it would be really cool if you could comment, Paul. Thanks!  The situation is that I have lost the benefit of the 'ip helper-address'. 

 

The name of the new post is 'Allowed VLAN' pruning, 'ip helper-address', and DHCP.

Hello


haggittmark@tm-america.com wrote:
 I have lost the benefit of the 'ip helper-address'. 

Can you elaborate please?

 

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Is the only way to forward DHCP requests to use Cisco's proprietary VTP 'ip helper-address'?

Review Cisco Networking for a $25 gift card