tag:blogger.com,1999:blog-6230024559279811901.post8029370458703164387..comments2023-08-28T14:37:10.715-07:00Comments on I.T. Proctology: My Windows Network Virtualization demo scriptBrianEhhttp://www.blogger.com/profile/09946552115562772058noreply@blogger.comBlogger37125tag:blogger.com,1999:blog-6230024559279811901.post-73812716410035669522014-06-19T06:25:25.438-07:002014-06-19T06:25:25.438-07:00Take a look at the section here: New-NetVirtualiz...Take a look at the section here: New-NetVirtualizationProviderAddress -InterfaceIndex $swPhysIf.InterfaceIndex -ProviderAddress 172.16.0.1 -PrefixLength 21<br /><br />The PA IP can be thought of as an alternate IP to the external port of the virtual switch (you can do this with physical switches, why not virtual ones).<br /><br />Technically, it is not applied to a vNIC that you can actually 'see', it is applied to a hidden port.<br /><br />Since virtual devices are conceptually similar to physical devices with ports, patch cables (virtual connections between ports), vNICs, etc.<br /><br />A virtual switch has ports. And in reality, a vNIC is a virtual switch port.<br />But I am probably explaining too much in an attempt to help you visualize.<br /><br />There is a blog series here, and PA addresses are a topic of an entire post themselves.<br /><br />http://itproctology.blogspot.com/2012/07/server-2012-windows-network_20.html<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-3029690688950640202014-06-18T22:00:47.500-07:002014-06-18T22:00:47.500-07:00Hi Brian,
Nice and detailed Article !
Actually I...Hi Brian,<br /><br />Nice and detailed Article !<br /><br />Actually I am stuck in Provider Address (PA), where should I punch the PA IP?<br /><br />as you mentioned in your post that this is assigned to the physical NIC of the External Switch - You meant the Virtual adapter? because we can't set IP on P NIC once it is used for vSwitch.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-63726824733181854992014-04-21T11:08:45.705-07:002014-04-21T11:08:45.705-07:00Unfortunately, MSFT did not release the built-in P...Unfortunately, MSFT did not release the built-in PowerShell cmdlets until Server 2012.<br />The best that you can do is invoke vmconnect.exe directly with the connection to option.BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-53277022742480901602014-04-21T07:04:36.032-07:002014-04-21T07:04:36.032-07:00Hi guys,
can any one help me what is cmdlet in W...Hi guys,<br /><br />can any one help me what is cmdlet in Windows 2012 R2 to connect the vm like "New-VMConnectSession" in Windows 2008 R2<br /><br />Thanks to all<br /><br />Regard's<br />MVSsunnyhttps://www.blogger.com/profile/00784260127588178908noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-72515840277981704782013-12-13T20:44:57.103-08:002013-12-13T20:44:57.103-08:00Thanks for the reply! However, there are a few thi...Thanks for the reply! However, there are a few things which are still bothering me..I tried to search everywhere but no luck!<br /><br />My understanding about NVGRE is that when a packet arrives from a NVGRE VM, the packet is received by the PA Switch, the switch uses LookupRecords table to check for the destination. It finds that the packet is destined for a VM which is located on another Hyper-V Host. <br /><br />Ok..so at this point, the packet's destination is known!<br /><br />Now the thing is that:<br /><br /> -In case of non-Gateway VM, the packet is sent to wire via PNIC of NVGRE Switch (PA address is routable). Basically, the packet exists via PNIC bound to NVGRE Switch.<br /><br /> -In case of a VM Gateway (vNIC assigned with NVGRE gateway IP : x.x.50.1), the packet is re-routed to the VM Gateway? Is that the case? <br /><br />Would I be accurate if I describe that the NVGRE traffic will "always" be sent to default gateway (x.x.50.1) whether a Gateway VM is implemented or not? But that depends on the ProviderRoute created as below: <br /><br />New-NetVirtualizationProviderRoute -InterfaceIndex $NIC.InterfaceIndex -DestinationPrefix "0.0.0.0/0" -NextHop "192.168.50.1" <br /><br />----------<br /><br />Another thing bothering me is the IP address configuration:<br /><br />The configuration looks like below in case of non-VM gateway:<br /> All VMs - 192.168.50.x...<br /> PA: public IP Address (which is a routable IP)<br /><br />Very clear on this part if no Gateway VM implemented.<br /><br />but in case of a Gateway VM, the configuration looks like below:<br /><br /> -All VMs - 192.168.50.x<br /> -PA IP - 192.168.50.40 (which is a non-routable IP)<br /> -VM Gateway - vNIC1 - 192.168.50.1 (connected to NVGRE)<br /> -VM Gateway - vNIC2 - this is where the confusion is. Should I assign public IP Address to this vNIC?<br /> if I assign Public IP Address then what IP address should be assigned to the non-NVGRE virtual Switch. Should it be left blank?<br /><br />Thank you for clarifying my doubts!<br />Seth<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-26310704240031616662013-12-13T10:38:53.773-08:002013-12-13T10:38:53.773-08:00The vNIC within the NVGRE network must have an IP ...The vNIC within the NVGRE network must have an IP on that subnet. The vNIC on the LAN needs an IP on that subnet.<br /><br />PA addresses are routable. They exist on the LAN subnet and they are assigned to the virtual switch. No different than a physical router that has multiple IP addresses on one port. PA addresses are the wrapper IP addresses that transport the encapsulated NVGRE packets between the individual hosts that participate in the NVGRE subnet. Networking rules still apply.BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-28064750435501449502013-12-12T02:20:29.640-08:002013-12-12T02:20:29.640-08:00Hi Brian,
I'm missing one part of the Gateway...Hi Brian,<br /><br />I'm missing one part of the Gateway (vvyatta router) configuration. One vNIC is connected to NVGRE network and other vNIC is connected to an external Virtual Switch bound to a physical NIC which in turn is connected to PLAN. <br /><br />My questions are:<br /><br />1. What IP Address I should assign to vNIC (eth0) of Router which is connected to NVGRE network?<br />2. What IP Address should be assigned to vNIC (eth1) of Router which is connected to another External Virtual Switch? Is it going to be a public IP Address <br />3. And what IP address should be assigned to Virtual Switch which connects Router VM?<br /><br />And also in one of your posts you say that NVGRE PA address should be routable. But IMHO, PA address will be a non-routable IP Address if we are going to use VM router?<br /><br />Thank you for your time for looking into this for me!<br /><br />SethAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-5841379252141502552013-07-16T06:31:12.251-07:002013-07-16T06:31:12.251-07:00You have to generate a GUD for the customer, as sh...You have to generate a GUD for the customer, as shown here:<br /># Generate a GUID for each customer<br />$redGUID = [system.guid]::newguid()<br />$blueGUID = [system.guid]::newguid()<br /><br />Beyond that, each VM gets a GUID from the hypervisor at the time the VM is created on the hypervisor (they all do this). You can only query the VM GUID, not create it.<br /><br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-45694517702825207712013-07-16T01:22:14.343-07:002013-07-16T01:22:14.343-07:00Hi, thanks for posting this blog, It really help m...Hi, thanks for posting this blog, It really help me much. <br />And I have a question to ask:<br />Where to generate the guid? On customer's VMs, as in this article, they are four VMs and would generate four different GUIDs. I am a little confuse.<br />Could you please send me an e-mail to "aleanday@163.com" when you see this?<br />Thanks in advanced.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-57901421110963727282013-07-01T06:23:48.787-07:002013-07-01T06:23:48.787-07:00There is no built-in router. so defining a gateway...There is no built-in router. so defining a gateway means that you must have a vm that serves as a gateway at that address.<br /><br />work through my entire blog series. you will see how to define everything.BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-6121217449890244502013-06-30T05:36:54.111-07:002013-06-30T05:36:54.111-07:00Dear , I can n't routing between two VSID .
Ho...Dear , I can n't routing between two VSID .<br />How can i Creat Gateway Records .plz help meAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-62270297665494363852013-03-29T08:05:28.671-07:002013-03-29T08:05:28.671-07:00The feedback that I received from the product team...The feedback that I received from the product team on this is:<br /><br />The KB MUST be installed on all WNV hosts. <br />Otherwise the packet formats will differ between the patched and un-patched hosts.<br /><br />So if you either all hosts patched or all hosts unpatched.<br /><br />I hope that helps.BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-65534041801707649722013-03-28T01:06:30.820-07:002013-03-28T01:06:30.820-07:00We used Wireshark to investigate the problem the a...We used Wireshark to investigate the problem the answer was KB2779768 :) no comment... we spend 2 days on this.<br /><br />the problem is explained on high level from one of my collegues at this blog post http://cloudadministrator.wordpress.com/2013/03/27/network-virtualization-nvgre-in-windows-server-2012-may-not-work-if-you-do-not-have-update-kb2779768-installed/<br /><br />I appreciate your help!<br /><br />Best Regards YordanAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-26583530607006137442013-03-27T10:09:51.310-07:002013-03-27T10:09:51.310-07:00I have not tried using the VLAN ID on the PA.
You...I have not tried using the VLAN ID on the PA.<br /><br />Your InterfaceIndex should be the teamed network adapter where you enabled WNV, which should be the teamed adapter that the virtual switch is attached. <br />InterfaceIndex 12, is generally a physical device, not a teamed adapter.<br /><br />Technically, WNV does all the routing, so it is a filter driver above the network adapter and below the virtual switch. In between, if you will.<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-20948147587745959092013-03-27T01:23:48.963-07:002013-03-27T01:23:48.963-07:00Yes, WNV is enabled on the Teamed adapter. vSwitch...Yes, WNV is enabled on the Teamed adapter. vSwitch is attached on the teamed adapter. NVGRE PA adapter operates between vSwitch and the teamed adapter. So is it possible this PA adapter (NVGRE) to operate as different than VLAN 0 - there is a VlanID switch that could be set:<br /><br />ProviderAddress : 192.168.11.242<br />InterfaceIndex : 12<br />PrefixLength : 0<br />VlanID : 11 <---------------------------------------<br />AddressState : Preferred<br /><br />Or the only way to establish NVGRE between hosts is to use VlanID: 0 ?<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-39711605246572644792013-03-26T10:13:35.970-07:002013-03-26T10:13:35.970-07:00So, lets gather some information.
You have an LBF...So, lets gather some information.<br /><br />You have an LBFO Team. These are trunked ports. (though I believe that NVGRE operates on VLAN 0, it is not VLAN tagged traffic).<br /><br />Where is the WNV filter enabled? (which NIC, the physical or the Team) Since the switch should be attached to the Team the WNV filter needs to be enabled here as well.<br /><br /><br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-44727999806133579762013-03-26T09:56:55.485-07:002013-03-26T09:56:55.485-07:00Im really lost with testing of NVGRE. I was able t...Im really lost with testing of NVGRE. I was able to test it with host (Provider Addresses) connected on access ports on the switch, but when im using teamed adapters connected on 802.1q trunk ports NVGRE seems not working. I really believe that Microsoft does not develop it in the way NVGRE to work only on access ports, but how? What is different in the configuration? What if im using 2 teamed converged adapters for cluster, management and tenant network? Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-38887011701964103742013-02-18T13:58:15.398-08:002013-02-18T13:58:15.398-08:00If you missed this; Here is my setup script.
Note...If you missed this; Here is my setup script.<br />Note I have hardcoded a few things that you might want to use and XML or TXT file to define.<br />http://itproctology.blogspot.com/2012/12/my-windows-network-virtualization-demo.html<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-57490354689605111052013-02-07T06:19:09.093-08:002013-02-07T06:19:09.093-08:00DHCP running in a VM does not work and will not wo...DHCP running in a VM does not work and will not work. I spent a lot of time with that, and have it confirmed from the MSFT folks.<br />In theory it might if you define the broadcast domains, but it doesn't.<br /><br />SCVMM uses a custom switch extension to perform their DHCP magic. They intercept the DHCP request, and respond to it from an IPPool <br /><br />And the reboot / rules wipe. Yes, I have mentioned that pitfall in the blog here.<br /><br />I did create a script that simply queries host a and host b and builds the rules based on the current location of the VMs.<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-27980082108833717842013-02-07T03:21:26.931-08:002013-02-07T03:21:26.931-08:00The hosts are restarted and all the configuration ...The hosts are restarted and all the configuration is gone.It is really cumbersome to have all my configuration back. I have tried it again but i was not successful. will post you know once i get it working.<br /><br />Have you tried having DHCPVM on host1 and able to assign IPAddress to VM1 on another host2 (both DHCPVM and VM1 are in subnet 5001)in nvgre environment without SCVMM? Because unless we create lookup records it does not create DHCPVM and VM1 in the same virtual network which requires customer IPaddress. But if it is DHCP environment you will not have IPaddress. It is like chicken and egg problem. <br /><br />With SCVMM , i see they recommend DHCP extension to be installed on hosts and it manages assigning IP to hosts. But is it possible to manage with DHCPVM on one host without SCVMM in nvgre environment?<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-91544881033858384172013-02-06T05:54:37.859-08:002013-02-06T05:54:37.859-08:00That is the way it is supposed to work. However, I...That is the way it is supposed to work. However, I never had time to try.<br /><br />Can you post your configuration? As examples of defining the gateway?<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-43945800242631244932013-02-06T03:24:00.210-08:002013-02-06T03:24:00.210-08:00Brain, interestingly VMs of different virtual subn...Brain, interestingly VMs of different virtual subnets were able to communicate without having separate router. The configuration i have is<br />Host-1 ---> VM1 ---> vSubnetId:5001 - 10.0.0.0/24<br />Host-2 ---> VM2 ---> vSubnetId:7001 - 10.0.1.0/24<br /><br />By assigning same routing domain id to both vSubnets and creating gateway records for 10.0.0.1 , 10.0.1.1 on both hosts, they were able to communicateAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-78951195478698793642013-02-05T08:20:37.636-08:002013-02-05T08:20:37.636-08:00As long as your gateways are set up properly and y...As long as your gateways are set up properly and you have forwarding enabled it should route.<br /><br />BTW- if you are using Server 2008 or newer, ping won't reply without enabling it.<br /><br />the RRAS router has to have one vNIC associated with each virtual subnet.<br />This is at the VM vNIC configuration level.<br />BrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-43834438053019481482013-02-04T20:07:47.686-08:002013-02-04T20:07:47.686-08:00Brain, i tried to set up rras LAN router with one ...Brain, i tried to set up rras LAN router with one management nic to connect from host, one nic with 10.0.0.1 (which is in 5001 vsubnet) and another nic with 10.0.1.1(which is in 7001 vsubnet) and provided them as gateways for Vms in the corresponding subnets. But i could not ping 10.0.0.0/24 from 10.0.1.0/24 subnet. Am i missing something here? Do i need to configure any static routes<br /><br />In nvgre environment, since the VMs in each subnet are in different virtual subnet ids,how does the rras router know about virtual subnet ids? <br /><br />Let me know your thoughts on this<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6230024559279811901.post-56254170198811114392013-02-01T05:47:28.892-08:002013-02-01T05:47:28.892-08:00absolutely. If you script the RRAS set-up I would ...absolutely. If you script the RRAS set-up I would love to se itBrianEhhttps://www.blogger.com/profile/09946552115562772058noreply@blogger.com