HP NCU - VLAN tagging question

[StevenH]

Hi Guys,

Scenario is I have a switch with multiple VLANs trunked on all ports.

I am attempting to create a VLAN on a non teamed connection using HP NCU (latest release) by going to the NCU utility, selecting the connection, selecting VLAN ID and creating a new VLAN virtual switch. This is on Server 2008 R2 SP1.

I then IP address the newly created interface however it does not seem to work. I cannot ping it, or ping out. 

On the contary, if I start from scratch and select this interface from within network and sharing center, go to properties and configure, and then add a VLAN ID from within here this works fine. I can ping out and in. 

Is there any different in the two?

Reason I ask is the only way I can configure a VLAN on a single interface in server core is using this utility. I can't get access to the adapter properties to add a VLAN tag directly.

If I am going about this the wrong way please let me know :)

Thanks,

[shocko]

Firstly, what hardware are you on? Can you post a screen shot of the VLAN settings you are configuring?

[shocko]

Are you running the NCU in elevated mode i.e. is UAS enabled on the box?

[StevenH]

BL465c in a C7000 chassis :) Using Virtual Connect.

Unsure if the NCU was started in elevated mode actually - will this make a difference? I've not had any issues creating teams, etc if that helps?

I'm not onsite so will have to talk someone through doing it again in an elevated prompt if it is worth it?

If I create a team, add multiple VLANs (which then creates the virtual switches) - and then add these as an external network in Hyper-V, and tag the VLAN on the guest VM this works fine if that provides any further indication!

Appreciate the response :)

[shocko]

Hi Steve,

Lets back track a a little.

So your systems ias a follows:

• bl465c
• Running Hyper-v

What are your virtual connect network settings set up as?

[StevenH]

Hi Shocko,

Correct on the setup - BL465c running Hyper-V with Virtual Connect.

I don't have the Virtual Connect settings to hand at the moment as I am not onsite. Not very familiar with Virtual Connect myself as it is usually pre-configured when I arrive onsite.

What settings are you after so I can clarify with them? Not due on site for another week or so unfortunately.

Kind Regards,

[shocko]

Virtual connect also tags traffic with VLAN ids if configured to do so so we'd need to know that side of the config also.

[StevenH]

I'll find that info out and come back.

I would assume it is not configured to tag any of the traffic in Virtual Connect, as if I attempt to add a VLAN ID in the operating system by performing the following;

- Right Click an Adapter and Select Properties in Network Connections
- Select Configure
- Select Advanced Tab
- Select VLAN ID and tag here

... then this works fine. Which would indicate to me it is more something to do with how NCU is applying the tag?

[shocko]

Hi,

I am suprised that you can set the VLAN tag directly on a network connection. Do you have teams setup?