OK. I know is not good practice using Vlan1 for regular data traffic, but this is how is been in our network until now (Our LAN includes 2 Cat6500 and 2 Cat3550). We are now deployng several VMware servers with virtual switches. This virtual switches require all Vlans to be tagged (included VLAN1) so we have to change our VLAN1 behaviour. I've seen 2 ways to do so:
1) tag vlan1 (native)
2) changing native vlan1 to another VLAN.
So I have some questions:
- What do you think is the best option in order to minimize configuration changes and impact in the network?
- I'm assuming both options require configuration changes in every switch of our network, is that right? I'm not sure if in case 2) only configuration changes in trunks to vmware switches are needed.
Why would the servers need the tag? Would you be trunking to the servers? If so, I would go with option 1. I would say you need this on the switch which has the VMware server and any directly connected switch to the VMware switch.
VMware switches do need VLAN1 tagged as they trunk to Catalysts. If I choose option 1, isn't needed to add that command "vlan dot1q tag native" in every switch in the network because if one is not configured, i'd break communication over Vlan1 ?
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...