Issue:
customer who is trying to certify VMware ESX4.1U2 on the DL360 Gen8 and DL380 Gen8. They seem to be using the correct driver but the service console command “lspci” is showing the 331FLR is an unknown device. They are able to PXE boot off the NIC and it seems to be working normally, but they wanted some investigating.
They have tested with both VMware’s build and the HP ESX built and received same result in both cases
Reason:
customer who is trying to certify VMware ESX4.1U2 on the DL360 Gen8 and DL380 Gen8. They seem to be using the correct driver but the service console command “lspci” is showing the 331FLR is an unknown device. They are able to PXE boot off the NIC and it seems to be working normally, but they wanted some investigating.
They have tested with both VMware’s build and the HP ESX built and received same result in both cases
Reason:
lscpi compares the pci id’s
against an internal “database” to determine the information to display.
For newer devices, the only way to get an update is for VMware to provide
updated info for the “database”. These updates are provided with ESXi
updates or new releases (e.g. 5.1 U1, 4.1 U3). There is no impact to
functionality, this is purely a reporting issue.
“esxcfg-nics –l”
should report the appropriate model.
Once the hosts are updated with the new databases through vmware patching or updates it should show up properly with the lspci command too.
Once the hosts are updated with the new databases through vmware patching or updates it should show up properly with the lspci command too.
No comments:
Post a Comment