VLAN issue with latest NIC Driver

[Blazhev_1]

Hi,

if the configuration is changed, you will be unable to connect to the VLANS with all tricks you make. I think that the driver changed the config of the NIC, not the VLAN, since it don't have acces to the VLAN(Switch). You can try to downgrade the driver and see if the problem is resolved.
If so , then there is 99% problem with the driver/his relation to the Cicso switch and you can open an elevation at HP suport...

Regards,
Pac

[Massimiliano Fiorazzo]

DL380 G4

Windows 2003 X64 installed with latest SmartStart CD (7.90)

When I add a Vlan to NC7782 with HP Network Utility I get an interface with:

MAC Physical Address: 00-00-00-00-00-00

and the server will comunicate with nobody !

can you tell me how to resolve this ?!?!?

thank you

max

[Technology Helpdesk]

James,

I'm back at the customers site and manually installing the firmware and drivers didn't fix the problem.

Pac,

From the looks of the config on a server still working it doesn't look like the updated driver changed the config. Obviously it changed something though. One thing I did notice is HP has separated the Large Send Offload and IPMI now with the new driver.

I am able to go back on drivers with the latest support pack. But the NCU won't work work and the only way to uninstall it is via the NIC and then it removes the 20 vlans we've got setup. So I'm not a big fan of that.

Also I've contacted HP and they shrug off as to just continue using your previous driver. The only problem is we've updated these servers to SP2 and now I have to get to the latest support pack to prevent random restarts and conflicts with certain drivers.

Thanks guys for all of your help. I honestly just wanted to make sure that we didn't setup our VLANS wrong on our switch, but they worked with the previous driver so in theory they should continue to work.

[Craig A. Liess]

Just wanted to give you the heads up that are you not alone with this issue.. IDENTICAL setup with the 6500 + DL360g4p.

If we disable any of the virtual VLAN NICs and re-enable it, the issue is resolved.

We're going to roll back to the v7.8 driver and see if that solves it.

-Craig

[Technology Helpdesk]

Craig,

Thanks...I was beginning to think I was all alone. So you were able to get it working if you disabled the VLAN and brought it back up? I'm willing to try that and that's not a bad work around if it works.

Thanks,

Travis

[Craig A. Liess]

Hi Travis,

Yes, simply disabling & re-enabling any of the virtual VLAN interfaces seems to resolve the issue... until you reboot the server, that is.

We're going to roll the driver back this weekend (I think..) and see what happens.

-Craig

[Technology Helpdesk]

Craig,

When we've tried the roll back idea we've had to recreate all of our 32 VLANS after we uninstall the NCU. Have you guys found a way to export the VLAN info and then reimport it?

Thanks,

Travis

[Mi6t0]

Hey there ;)

I think the previous idea for stopping TOE is really good and the driver works fine. Just go to network configuration utility - settings - advanced settings and remove the tick from TCP POffload engine.

Also - if you use teaming, make the settings on "transmit load balancing". One more thing - bios version is very important, the old one didn't allocate the ram properly. And sometimes the /PAE switch causes problems.

Greets!

[Carlos Hernandez Barea]

Hello.

Exactly the same issue with ProLiant BL20p G3. The workaround of disable-enable the interface works fine...until you reboot the server :-(

I have tried to disable TOE, but it seems that TOE is only availble if you have Teaming, not only VLAN's. Is it right?

Next I will downgrade the driver.

Regards.

[Carlos Hernandez Barea]

Hello.

The downgrade of the driver didn't fix the issue :-(

Maybe it would be a good idea downgrade also NCU?

Regards.