correction: "are working fine _without_ VLAN tagging" (untagged)
I tried creating a VLAN using prosetcl.exe and see the same failure. I have submitted a bug report. If I come up with a workaround, I will let you know.
I figured out why VLAN creation was failing for me. I was not running the commands with administrator privileges. Once I had the proper permissions, I was able to successfully create a VLAN. Could that be why VLAN creation is failing for you?
Thanks for your help, but I'm still getting the same error after starting a command shell runas local administrator on the Hyper-V node:
C:\Program Files\Intel\DMIX\CL>PROSetCL.exe Adapter_CreateVlan 1 100 SAN
1) Intel(R) PRO/1000 EB Network Connection with I/O Acceleration #2
Attempting to create VLAN 'SAN' ...
Failed to create VLAN
I guess a weekend can clear the cobwebs. I was so focused on the PROSet command line utility that I did not pay close attention that you need to use VLANs under Hyper-V. For Hyper-V you should create the VLANs in the virtual interface instead of on the physical port.
FAQ: VLANs and VMDq on Intel® Ethernet Adapters in Hyper-V covers this subject.
The way the protocol bindings work will also complicate things if you create the VLAN on the physical port. Take a look at Hyper-V* virtual NIC will not communicate for more information.
I am not sure why you cannot create the VLAN wit the utility. Maybe only configuring the VLANs on the virtual NICs will work for you.
I saw your name on one of the posts on the Intel website. We are deploying several thousand Dell Optiplex 980 desktops for a Federal Gov't customer. We tryed using vPro about 18 months ago for remote desktop management (same customer) and had a lot of trouble with it. Can you tell me if the technology has improved/matured and are there any centralized management tools available to push the certificates out over the air vs manually loading them from USB stick?
Thanks in advance,
Northrop Grumman IS
Thanks for your question. Unfortunately this question is outside my area of expertise. You should probably repost the question in a new thread. I do know that VPro has evolved from earlier versions, so someone else in this community can probably answer your question.
Mark, thanks for the follow up. The purpose for creating the VLAN in Hyper-V was to segregate VLAN traffic at the Hyper-V host level. Since the Microsoft iSCSI initiator is managed exclusively from the Hyper-V host, it is necessary to bind a VLAN to the physical interface. That said, the FAQ does indeed describe the required steps. Unfortunately, it is only possible to bind one VLAN per physical adapter at the host level using this approach, which means that the physical adapter cannot be shared for multiple purposes -- for example, as the iSCSI SAN LAN and also for general Hyper-V management, live migration, or heartbeat (even though this is clearly not best practices).