[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 393
  • Last Modified:

2 ends of trunk - allowed vlan 2-4094 - other end allowed all - will vlan1 pass through trunk

Hi - can someone please explain this. - here are 2 settings for either end of trunk
int2.jpg
int1.jpg
0
philb19
Asked:
philb19
1 Solution
 
Don JohnstonInstructorCommented:
What exactly do you want explained?

Looks like VTP is pruning the VLANs on the trunk at one end of the trunk.
0
 
RKnebel512Commented:
No, vlan 1 should not pass through this trunk.  Interface 2 will neither send it out this port nor receive it.  But depending on the way your network is configured, you might want that behavior.

Since the native vlan is vlan 1, the switches put any packets that don't have another place into vlan 1.  

For security purposes, many network administrators run everything on other vlans, then filter out vlan 1.  That way any traffic that they didn't specifically put in one of their own vlans doesn't get sent anywhere.  

But if you aren't using any other vlans, then everything is dumped into vlan 1.  In that case, you definitely want to allow the traffic.

Either way, you should configure the ports so they match, just for simplicity's sake
0
 
Craig BeckCommented:
In addition to what the other experts have said here, it's fine to have different pruning settings at each end of a trunk link from a technical perspective.  You don't need things to match like you do with an EtherChannel.

The beauty of this (depending on how you look at it) is that you can prune VLANs at one end only if you want to, without having to prune at the other end.
0
 
philb19Author Commented:
great explanation - Thanks
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now