DL380G5 Network teaming problem after imaging

[Sandor Bardi]

We install a w2003 R2 std to DL380G5 server with Smart start.
After that we created a image with acronis true image echo server.
We restored the image to the another DL380G5 srv with the same configuration.
After the start we couldn't create the network team on the new hardware.

Do You have any idea? Is it possible another problem with this method?

[juan quesada]

Hi,

h20000.www2.hp.com/bc/docs/support/SupportManual/c00288924/c00288924.pdf
NIC's tested (from a HW point of view)?
Can you ping them?
Any error code or so?
NCU version latest or previous one?
Drivers ok? http://broadcom.com/support/ethernet_nic/netxtremeii.php
Have you checked this?
http://support.microsoft.com/kb/948496

Regards,

[KarloChacon]

hi

did you have a NIC teaming created when you created the image in the original DL380 G5?
if that is your case what I think is when you create a NIC teaming that NIC teaming creates new values for that server(virtual MAC address for instance) and those values are going to reflect in the other server...
so recommendation is disolve any teaming before create an image

------------------------

if not what is the error?
something in event viewer?

uninstall Network configuration utility (NCU)
unistall TCP/IP protocol from NICs
reboot server
reinstall TCP/protocol
reinstall NCU and try again

regards

[Sandor Bardi]

Hi

We didn't created a team, before the making image.
This is a basic install whitout any settings.
When we restored this image to the another server and try set the team, the team connection will be unpluged (the phisical connections are existing).

thx

[KarloChacon]

hi

which driver version for NIC cards?
which Network configuration utility version?

if you configure them individually can they work?

did you try this?
uninstall Network configuration utility (NCU)
uninstall TCP/IP protocol from NICs
reboot server
reinstall TCP/protocol
reinstall NCU and try again

regards

[Joshua Small_2]

The registry will refer to the NICs in the old server. Ghosting on servers never tends to be trouble free.

First uninstall the network configuration utility.
Then remove the existing NICs using this guide:
http://support.microsoft.com/kb/241257

Then reboot, reinstall the NIC driver, and teaming utility, and you'll probably be away.

[Kenneth Pinson]

I had a problem with the version of the Network Configuration Utility. I had installed Support Pack 7.91 on my image which is using version 8.80 of the Network Configuration Utility. I was unable to create a team on any of the servers that I created from the image. I am testing various combinations to see which work. So far, downgrading the NCU to version 8.7 worked. When I upgraded the NCU to 9.1, that also required me to upgrade the NIC drivers. I am in the process of testing Support Pack 8.0A. So far that seems to have fixed my problem.