cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
827
Views
0
Helpful
2
Replies

VTP Pruning - why does it work this way

SJ K
Level 5
Level 5

Hi all,

 

With regards to the example shown here below

http://packetlife.net/blog/2008/jun/26/when-does-vlan-pruning-occur/

 

Pruning is down on vlan10 in switch 1, when switch 2 no longer have any active ports in vlan 10. (Host b disconnected)

Reason being that there is no need for traffic to travel down the trunk to switch 2 for vlan 10 since there isn't any active connection to vlan 10 in switch 2.

 

However, on switch 2, vlan 10 is not pruned because in switch 1 there are still active ports in vlan 10 hence traffic will need to travel down to the trunk from switch 2 to switch 1.

 

q1) But think about it, if there are no active ports in switch 2 for vlan10, it means that no connections (from switch2) can be established to vlan10 in switch 1 - in that case, why not prune vlan10 from switch 2 as well ?

 

Or is it that switch2 itself can connect to members in vlan10 on switch1 ? hence vlan10 cannot be prune yet even though there are no active ports on switch 2 ?

 

Regards,
Noob

 

 

1 Accepted Solution

Accepted Solutions

Jon Marshall
Hall of Fame
Hall of Fame

q1) VTP pruning is a bit more complicated than that example suggests.

So it talks about active ports but trunks are also active ports not just ports connected to end devices. It's important to understand this because the example you linked to is quite a straightforward one but take this example -

h1 (vlan 10) -> sw1 -> trunk -> sw2 -> trunk -> sw3 -> h2 (vlan 10)

all trunk links are allowing vlan 10 but there are no access ports on sw2 in vlan 10.

For obvious reasons sw2 cannot simply prune vlan 10 off it's trunk links even though it has no active access ports in vlan 10 otherwise h1 cannot send traffic to h2.

The key thing to understand here is that sw2 cannot make a decision as to which vlans to prune based on the state of it's own ports which is the logic of what you are suggesting. It can only make a decision based on information received from neighboring switches.

Going back to the example you linked to if switch 2 pruned vlan 10 off the trunk using the logic you are suggesting it has done that regardless of what ports in vlan 10 are active on switch 1.

Following on with the same logic if a port in vlan 10 now becomes active on switch 2 it will begin to forward traffic for vlan 10 to switch 1 again regardless of whether switch 1 needs it or not.

What if in the meantime the active port on switch 1 in vlan has gone down ?

Because switch 2's decision as to whether to prune or not is based only on it's own port status it has no way of knowing this.

On the other hand if switch 2 does not prune vlan 10 off the trunk link because it knows there are active ports on switch 1 in vlan 10 then if a port becomes active in vlan 10 on switch 2 it can begin forwarding on that trunk link.

And if the port in vlan 10 on switch 1 went down switch 2 could prune that vlan regardless of whether it had active ports in vlan 10 or not.

It should also be noted you gain nothing from pruning on both sides in your example ie. switch 1 has pruned the vlan so it won't be sending any traffic and by definition switch 2 won't either otherwise the vlan would not have been pruned in the first place.

Jon

 

View solution in original post

2 Replies 2

Jon Marshall
Hall of Fame
Hall of Fame

q1) VTP pruning is a bit more complicated than that example suggests.

So it talks about active ports but trunks are also active ports not just ports connected to end devices. It's important to understand this because the example you linked to is quite a straightforward one but take this example -

h1 (vlan 10) -> sw1 -> trunk -> sw2 -> trunk -> sw3 -> h2 (vlan 10)

all trunk links are allowing vlan 10 but there are no access ports on sw2 in vlan 10.

For obvious reasons sw2 cannot simply prune vlan 10 off it's trunk links even though it has no active access ports in vlan 10 otherwise h1 cannot send traffic to h2.

The key thing to understand here is that sw2 cannot make a decision as to which vlans to prune based on the state of it's own ports which is the logic of what you are suggesting. It can only make a decision based on information received from neighboring switches.

Going back to the example you linked to if switch 2 pruned vlan 10 off the trunk using the logic you are suggesting it has done that regardless of what ports in vlan 10 are active on switch 1.

Following on with the same logic if a port in vlan 10 now becomes active on switch 2 it will begin to forward traffic for vlan 10 to switch 1 again regardless of whether switch 1 needs it or not.

What if in the meantime the active port on switch 1 in vlan has gone down ?

Because switch 2's decision as to whether to prune or not is based only on it's own port status it has no way of knowing this.

On the other hand if switch 2 does not prune vlan 10 off the trunk link because it knows there are active ports on switch 1 in vlan 10 then if a port becomes active in vlan 10 on switch 2 it can begin forwarding on that trunk link.

And if the port in vlan 10 on switch 1 went down switch 2 could prune that vlan regardless of whether it had active ports in vlan 10 or not.

It should also be noted you gain nothing from pruning on both sides in your example ie. switch 1 has pruned the vlan so it won't be sending any traffic and by definition switch 2 won't either otherwise the vlan would not have been pruned in the first place.

Jon

 

Hi Jon,

 

You are right. I cant see the bigger picture. Now i understand.

 

Thanks!

 

Regards,
Noob

Review Cisco Networking for a $25 gift card