VMware Cloud Community
brettcw23
Contributor
Contributor
Jump to solution

NIC issue after import

I imported an HP DL580 G2 box running win2k3 sp2 box and everything looks good except the NIC. It shows the AMD PCI NIC but says that it cannot start (has the yellow exclamation point next to it). The NIC on the physical box was a Broadcom adapter and we have HP teaming software on the box. What do I need to do in orcer for the adapter to work properly? I attached the message.

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

See http://sanbarrow.com/vmx/vmx-network.html

I'd first set

ethernet0.present = "false"

ethernet1.present = "false"

and clean up phantom nics after boot. Then shutoff VM and then I'd change back to

ethernet0.present = "true"

ethernet1.present = "true"

and add the lines

ethernet0.virtualDev = "e1000"

ethernet1.virtualDev = "e1000"

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

0 Kudos
8 Replies
IamTHEvilONE
Immortal
Immortal
Jump to solution

I thought I had seen something in the forums about this.

If I remember right, the solution was something like ... remove the 2 nics from device manager in the VM. Remove any teaming software in the VM that is left over from the physical server. power off the VM ... remove the nic hardware ... boot vm & power down VM ... add 1 nic back to the VM via edit settings.

I think the root cause was something to do with how the teaming works with the HP software.

However, I may be totally off base.

Maybe this thread might help:

http://communities.vmware.com/message/952973 - where i got my suggestion from.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

I would uninstall both AMD nics - reboot - clean up any phantom nics and reboot another time. Then add one or more e1000 and see if you still have a problem

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
brettcw23
Contributor
Contributor
Jump to solution

How would I go about adding the NIC's back in? I removed it originally via device manager and then the plug and play automatically detected it as an AMD inc. So then I went into VC and added a nic via edit settings thinking that I could use the NIC drivers from the physical box., but the VM recognized that nic as an AMD nic, too.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

See http://sanbarrow.com/vmx/vmx-network.html

I'd first set

ethernet0.present = "false"

ethernet1.present = "false"

and clean up phantom nics after boot. Then shutoff VM and then I'd change back to

ethernet0.present = "true"

ethernet1.present = "true"

and add the lines

ethernet0.virtualDev = "e1000"

ethernet1.virtualDev = "e1000"

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
brettcw23
Contributor
Contributor
Jump to solution

Okay, I think we're moving in the right direction. I did what you stated and now I see an Intel NIC on the box when I go in through the console. Should I just go to edit settings now and add a NIC?

UPDATE: The NIC reappeared as an intel. I simply powered it on. Everything looks good.

Message was edited by: brettcw23

0 Kudos
continuum
Immortal
Immortal
Jump to solution

Do you need a second one ?

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
brettcw23
Contributor
Contributor
Jump to solution

Nope. We are cool with just one.

One other thing though...can I remove the HP management software since

the server is running virtual now? I'd think that I don't care about any

of the array config software and such.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

> can I remove the HP management software

Yes - you may want to uninstall all hardware monitoring software as it makes no sense any more.

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos