CraigV75
Enthusiast
Enthusiast

Management NICs not working after reinstallation

Hi all,

I had issues with drivers and ended up starting to reinstall ESXi 6.5 instead of upgrading from 5.5.

All hosts are HPE ProLiant DL385p Gen8 servers. Started with the 2nd host which installed ESXi 6.5 (maintained VMFS). Got the 1st host done, but while I can configure the Management network within ESXi, I cannot ping the address or run any network checks from within ESXi.

NIC ports and switch ports have not been changed, nor have any changes been made on the switches. Any idea on what I am missing?

Thanks!

7 Replies
IT_pilot
Expert
Expert

Perform

esxcli network nic list

esxcli network nic get -n vmnic #

where # is the network adapter number

http://it-pilot.ru
CraigV75
Enthusiast
Enthusiast

vmnic0 (standb)

vmnic7 (active NIC)

pastedImage_0.png

0 Kudos
IT_pilot
Expert
Expert

1. I see the version of the network adapter, but I do not see the adapter model.

2. Take a screenshot of the adapter settings. They bother me

nic_status_web_client.png

http://it-pilot.ru
0 Kudos
HendersonD
Hot Shot
Hot Shot

Could it be this

VLAN tagging not working properly

Do these servers have nics installed based on the Intel X710 controller?

0 Kudos
CraigV75
Enthusiast
Enthusiast

Here it is. Since the server is down I cannot get to the host for it's screenshot. However, the DL385p Gen8s are all the same config so this is an indication of the NICs installed:

pastedImage_0.png

However, for some or other reason, the host networking is all configured differently, and use different vmnics. Not happy with that myself as it doesn't make any logical sense, or allow any standard to have been followed.

Thanks!

0 Kudos
IT_pilot
Expert
Expert

Let's exclude possible problems with Auto Negotiate.

On the working host, whose screenshot you have attached, Auto Negotiate is everywhere.

And on the bad

Auto_Neg_.png

http://it-pilot.ru
0 Kudos
IT_pilot
Expert
Expert

NetXtreme BCM5719 Gigabit Ethernet and Intel 82580 Gigabit Network Connection driver version 1.4.1 do not even have close.

Therefore, the output of the esxcli network nic list command is still relevant.

http://it-pilot.ru
0 Kudos