[prev in list] [next in list] [prev in thread] [next in thread]
List: cisco-voip
Subject: Re: [cisco-voip] Duplicate ipaddress space and vlans on separate vSwitches on same ESXi host
From: Lelio Fulgenzi <lelio () uoguelph ! ca>
Date: 2017-12-14 17:32:47
Message-ID: YTXPR01MB064025E5E6CFBEBAE3998264AC0A0 () YTXPR01MB0640 ! CANPRD01 ! PROD ! OUTLOOK ! COM
[Download RAW message or body]
[Attachment #2 (text/plain)]
Thanks for following up!
From: Gentoo [mailto:gentoo@ucpenguin.com]
Sent: Thursday, December 14, 2017 11:56 AM
To: Lelio Fulgenzi <lelio@uoguelph.ca>
Cc: Mike King <me@mpking.com>; 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
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@uoguelph.ca<mailto:lelio@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@gmail.com<mailto:michael.p.king@gmail.com> \
[mailto:michael.p.king@gmail.com] On Behalf Of Mike King
Sent: Wednesday, December 13, 2017 2:27 PM
To: Lelio Fulgenzi <lelio@uoguelph.ca<mailto:lelio@uoguelph.ca>>
Cc: cisco-voip voyp list \
<cisco-voip@puck.nether.net<mailto: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 \
<lelio@uoguelph.ca<mailto:lelio@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<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Thanks for following up! <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gentoo [mailto:gentoo@ucpenguin.com] <br>
<b>Sent:</b> Thursday, December 14, 2017 11:56 AM<br>
<b>To:</b> Lelio Fulgenzi <lelio@uoguelph.ca><br>
<b>Cc:</b> Mike King <me@mpking.com>; cisco-voip voyp list \
<cisco-voip@puck.nether.net><br> <b>Subject:</b> Re: [cisco-voip] Duplicate \
ipaddress space and vlans on separate vSwitches on same ESXi host<o:p></o:p></p> \
</div> </div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">You can have the same VLAN ID on different switches without \
issue.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This works fine:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Switch A has vlan 100 and 200 and NIC A is trunking VLANs 100 \
and 200 to Switch A.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Switch B has vlan 100 and 200 and NIC B is trunking VLANs 100 \
and 200 to Switch B.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Dec 13, 2017, at 15:33, Lelio Fulgenzi <<a \
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Yeah – that was a question I did have. Whether or not it would \
get confused with the same VLAN tagging but to different switches. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">But I would suspect that it would still keep the traffic \
separate since they are separate switches. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p> <p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Other than try. <span style="font-family:"Segoe UI \
Emoji",sans-serif"> 😉</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>From:</b> <a \
href="mailto:michael.p.king@gmail.com">michael.p.king@gmail.com</a> [<a \
href="mailto:michael.p.king@gmail.com">mailto:michael.p.king@gmail.com</a>] <b>On \
Behalf Of </b>Mike King<br> <b>Sent:</b> Wednesday, December 13, 2017 2:27 PM<br>
<b>To:</b> Lelio Fulgenzi <<a \
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br> <b>Cc:</b> cisco-voip \
voyp list <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] Duplicate ipaddress space and vlans on separate \
vSwitches on same ESXi host<o:p></o:p></p> <p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">Lelio, <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Yes with a caveat.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">You have to ensure that you don't cross pollinate (Allow \
both VLANs to see each other). But yes, this is pretty standard \
stuff.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This was via a google search, but it should give you the \
idea....<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><image001.png><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Thu, Dec 7, 2017 at 9:40 PM, Lelio Fulgenzi <<a \
href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>> \
wrote:<o:p></o:p></p> <blockquote style="border:none;border-left:solid #CCCCCC \
1.0pt;padding:0in 0in 0in \
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"> <p \
class="MsoNormal"><br> Just following up on a conversation about online/offline \
networks and making things work on an esxi host.<br> <br>
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.<br> <br>
Guests would be assigned to one vswitch or the other. Not both.<br>
<br>
Have I got it all wrong?<br>
<br>
Sent from my iPad<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" \
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--===============6484404611330154907==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic