Hardware identification and driver problem

[Michael Heims]

Hi together,

Recenty I installed a VCRM for our Servers. Runs fine so far except on two machines. Maybe somebody of you have an idea. I’m a bit lost in the meantime.

The VCA on the ML350 G5, W2k3 SP2 and the ML350 G5, W2k3R2 SP2 with PSP8.11A and 8.15A falsly indentify the NIC as a HP NC-Series Broadcom 1Gb Multifunction Driver for Windows Server 2003 and want to install the approriate driver v4.4.23.0.
Result: The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn't apply to this system.

Removing the discovery folder on the VCRM (Document ID: c01092497) hasn’t helped – on the local machine it doen’t exist. A manual delete of the drivers doesn’t work too – I got the message that they are a part of the PSP.

Any ideas, comments?

Thanks and Regards,

Michael

[Rancher]

Remove the Discovery folder from the two servers that are reporting incorrectly, not from the VCRM server. What version of VCA are you running?

[Michael Heims]

Good Evening,
Thanks for your answer. Well - on all other servers the discovery folder exists but not on this two machines.
The VCA version on both is 2.1.10.801.
Reapplying the PSP 8.11A/8.15A with a reboot hasn't helped too.... Any other things I can do? Google wasn't really friendly to me.
Regards, Michael

[Rancher · Accepted solution]

Here is what I would do now on those two servers. In fact, I have had to do this a few times myself. It almost sounds like the installs somehow got corrupted. When you can, uninstall the VCA on each server through Add/Remove Programs. Then reboot.
Then reinstall the VCA. I would copy the executable to your server desktop and run it that way. Then reboot again. Hopefully that will fix the problems!!!

[Michael Heims]

Thanks a lot for your answer! I'll give it a try this evening and give a feedback. Regards, Michael

[Michael Heims]

Well I'm afraid no success. I deinstalled and reinstalled the VCA with reboots between.
In the next step I de- and reinstalled the whole SMH stuff with drivers, management agents and so on. Again no success. I'm not sure if the NICs shown in the device manager (HP NC110T PCIe Gigabit) and in the SMH (HP NC-Series Broadcom 1Gb Multifunction) do match.
Is there a -of couse not the best- way to simply kick out the NIC from monitoring? Thanks again for your help! Michael

[Rancher]

OH, the NICs! I think you are OK there and maybe your problem is over? HP has gone to more generic NIC drivers. For example, here are 3 NICs we use with their corresponding driver in the VCA:
NC7771 - HP NC-Series Broadcom 1Gb Driver for Windows Server 2003
NC7170 - HP NC-Series Intel Driver for Windows Server 2003
NC373i - HP NC-Series Broadcom 1Gb Multifunction Driver for Windows Server 2003
So it looks like you NICs are reporting properly:)

[Michael Heims]

I'm not sure if I understand you right. Maybe it was a little bit too late yesterday or too early today...
The NIC is physically reported as a HP NC110T by the Windows device manager. The VCA wants to install a HP NC-Series Broadcom 1Gb Multifunction Driver for Windows Server 2003 Version 4.4.24.0. If this doesn't match, how can I "convince" to VCA not to ask me to install the driver 4.4.24.0? I attached a screenshot to show it a bit more specific. Thanks for the time you spend! Michael

[Earl Gable]

I was having this issue on a DL320 G4. I took CP009702 which was listed as the pack for this multifunction and extracted it to see the drivers. I compared that to my C:\windows system32\drivers on the server where it was reporting as needed. Found the sys files and deleted them. Rebooted and the VCA no longer shows this driver as needed on my server. It hasn't given me any issues

[Michael Heims]

This finally help me out! In addition I created a repository for this machine and the problem is completely gone. Thanks a lot.