You can have the same VLAN ID on different switches without issue. This works fine:
Switch A has vlan 100 and 200 and NIC A is trunking VLANs 100 and 200 to Switch A. Switch B has vlan 100 and 200 and NIC B is trunking VLANs 100 and 200 to Switch B. As long as those are truly different/isolated Vlans outside of vmware you wont have an issue. Just make sure you name them well, so you know which vlan 100 is A/B or even C. > On Dec 13, 2017, at 15:33, Lelio Fulgenzi <le...@uoguelph.ca> wrote: > > Yeah โ that was a question I did have. Whether or not it would get confused > with the same VLAN tagging but to different switches. > > But I would suspect that it would still keep the traffic separate since they > are separate switches. > > I might open a TAC case for this one. I donโt like doing that for technical > design issues, but I might not have any other avenue to confirm. > > Other than try. ๐ > > From: michael.p.k...@gmail.com [mailto:michael.p.k...@gmail.com] On Behalf Of > Mike King > Sent: Wednesday, December 13, 2017 2:27 PM > To: Lelio Fulgenzi <le...@uoguelph.ca> > Cc: cisco-voip voyp list <cisco-voip@puck.nether.net> > Subject: Re: [cisco-voip] Duplicate ipaddress space and vlans on separate > vSwitches on same ESXi host > > Lelio, > > Yes with a caveat. > > You have to ensure that you don't cross pollinate (Allow both VLANs to see > each other). But yes, this is pretty standard stuff. > > I don't think you can do Trunking on in VMware if your trying to do this. > (Carry multiple VLANs) since I think VMware will get confused which NIC has > which VLAN. > > This was via a google search, but it should give you the idea.... > > <image001.png> > > On Thu, Dec 7, 2017 at 9:40 PM, Lelio Fulgenzi <le...@uoguelph.ca> wrote: > > Just following up on a conversation about online/offline networks and making > things work on an esxi host. > > I've now had a bit more experience with virtual environments, and as far as I > can tell, there should be no issue creating a second (or third) vSwitch, > assigning it vmnics connected to the offline network and building networks > with the same VLAN information carried over the offline trunk that is carried > over the production trunk. > > Guests would be assigned to one vswitch or the other. Not both. > > Have I got it all wrong? > > Sent from my iPad > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
