[cisco-voip] Duplicate ipaddress space and vlans on separate vSwitches on same ESXi host

[Lelio Fulgenzi]

Thanks for following up!
From: Gentoo [mailto:gentoo at ucpenguin.com]
Sent: Thursday, December 14, 2017 11:56 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: Mike King <me at mpking.com>; cisco-voip voyp list <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Duplicate ipaddress space and vlans on separate vSwitches on same ESXi host

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 <lelio at uoguelph.ca<mailto:lelio at 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.king at gmail.com<mailto:michael.p.king at gmail.com> [mailto:michael.p.king at gmail.com] On Behalf Of Mike King
Sent: Wednesday, December 13, 2017 2:27 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip voyp list <cisco-voip at puck.nether.net<mailto:cisco-voip at 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 <lelio at uoguelph.ca<mailto:lelio at 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 at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171214/b2a7a554/attachment.html>