hpsum not picking up installed version correctly even when installed.

[mark q]

Hi,

I am in the process of migrating to support paq 8.0 and I have the process scripted on the server with the use latest and /additional options (sorry don't have the switch handy.

What I'm noticing is that hpsum is not installing all of the updates, specifically the version control agent if the versions are old. then after I do the update even with the force option it does not install them..

I must mention here that I have a mix of servers some are supported and some aren't but the vcagent also once installed is also picking up hardware that's not there on the box.

here are some of the updates that are listed in vcagent but not applied through the support paq..

Intel Chipset Identifier for Windows Server 2003
HP Version Control Agent for Windows
HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2003/2008
HP ProLiant 64-Bit/133-MHz Single/Dual Channel Ultra320 SCSI HBA and SCxxXe series SCSI HBA Driver for Windows Server 2003

these updates are in the support paq from what I can tell but not showing up in hpsum, and even when I run them manually Hpsum isn't picking up that they are installed even though I've checked the versions in the registry.

The odd thing is that I can take multiple servers and do the updates and some work and some don't with the same installation.. and this is on the same ostype and model server.

how can I force the vcagent or specifically hpsum to re-check the versions installed??

[KarloChacon]

hi

I'm not a HPSUM specialist because there is one person (or was) that knows a lot about that

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1198357
Michael Garner
HPSUM Architect

the point is not here to help
but I've seen a lot of issue with HPSUM

so what if you take one of those servers that you're having issues and run proliant support pack(PSP) using a file called *****.cmd
it is silent PSP installation

and let us know

regards

[mark q]

here's the batch file I use for 32 bit

- it backs up the ip config
- it backs up the array config
- it backs up the ilo config
- it backs up the nic teaming config
- it backs up the nic teaming advanced network pack license
- it checks for 1 gig free locally because I run them all locally.
- it centralizes all logs by servername
- it cleans up after itself..

@echo off
Rem check local disk space
Rem if not enough space on the c:\drive it checks d:\drive
SET minimum=1gb
Set drive=c:
freedisk /D %DRIVE% %MINIMUM% > NUL
if errorlevel 1 goto :ddrive
md C:\supportpaq
if errorlevel 0 goto :32bit

:ddrive
Set drive=d:
freedisk /D %DRIVE% %MINIMUM% > NUL
if errorlevel 1 goto :notify
md D:\supportpaq
if errorlevel 0 goto :32bit

:Notify
Rem this section of the batch file notifies by creating a log and putting it on the repository server
Echo Not enough disk space on c: and d: drives to complete the installation >c:\%computername%disk.log
copy c:\%computername%disk.log \\isntenglib01\insightlogs\diskalert
del c:\%computername%disk.log
goto end

:32bit
Rem delete old logs first
if exist c:\CPQSYSTEM\log\nul del c:\cpqsystem\log\*.* /f /q
if exist c:\CPQSYSTEM\hp\log\localhost\nul del c:\CPQSYSTEM\hp\log\localhost\*.* /f /q

Rem get the ip information from the server
ipconfig /all >c:\cpqsystem\ipinfo.txt

Rem delete nic teaming information file if it exists
if exist c:\cpqsystem\nicteam.xml del c:\cpqsystem\nicteam.xml

Rem Backup Nic Teaming Configuration
cqniccmd /s c:\cpqsystem\nicteam.xml

Rem Delete Advanced pack license file if it exists
if exist c:\cpqsystem\%computername%advancedpacklicense.txt del c:\cpqsystem\%computername%advancedpacklicense.txt

Rem Get Advanced Networking Pack license if it exists
nalicense display /l c:\cpqsystem\%computername%advancedpacklicense.txt

Rem delete array configuration file if it exists
if exist c:\cpqsystem\arraycfg.txt del c:\cpqsystem\arraycfg.txt

Rem backup the array configuration to a file
"C:\Program Files\Compaq\Cpqacuxe\bin\cpqacuxe.exe" -c c:\cpqsystem\arraycfg.txt

Rem delete the ilo configuration backup file if it exists
if exist c:\cpqsystem\%computername%ilo.xml del c:\cpqsystem\%computername%ilo.xml

Rem Backup the ilo configuration to an xml file if it needs to be reapplied
c:
cd "\program files\hp\hponcfg"
hponcfg /w %computername%ilo.xml
copy %computername%ilo.xml c:\cpqsystem
del %computername%ilo.xml

Rem stop sms - for ipmi updates to wmi
start /b /w net stop "SMS Agent Host"

Rem Start the install of the support paq and firmware
Echo all prerequisites met copying installation media
COPY \\ISNTENGLIB01\CPQIS\2003 %DRIVE%\SUPPORTPAQ /y /v
start /b /w %DRIVE%\SUPPORTPAQ\hpsum /use_latest /s /current_credential /allow_non_bundle_components

rem remove support paq files after installation
rd %DRIVE%\SUPPORTPAQ /s /q

rem backup logs to central server
c:
cd \cpqsystem\hp\log\localhost
ren hpsum_detail_log.txt %computername%.txt
ren HPSUM_InstallDetails.xml %computername%.xml
ren hpsum_log.txt %computername%_hpsum_log.txt
copy /y *.* \\isntenglib01\insightlogs
shutdown -f -r
goto end

:end
exit

[Michael Garner_1]

Mark,
What you are seeing is a byproduct of our new philosophy for deploying updates. Prior to version PSP 7.90, the Remote Deployment Utility (RDU) allowed you to force install all drivers, utilities, agents, etc. This behavior occurred even if they were not supposed to be deployed because the hardware wasn't there, the update wasn't needed or there were missing dependencies required for the software to work correctly.

Starting with PSP 7.90, we replaced RDU with hpsum. HPSUM does dependency checking and removes any components that are not supported on the server being updated. In your list above, the Intel Chipset Identifier was a NULL driver just to remove a yellow bang in device manager on certain servers. For all other servers that did not have these chipset devices that would cause the yellow bang in Device Manager, it did nothing. For the last two devices in your list, these are for specific hardware which may not be present in your server. Rather than deploy the drivers, they are removed from the installation set.

Because of this new behavior of not listing devices that are not needed, on older versions of the VCA, you will see a version reported as installed that does not match the version in the PSP. I believe the VCA in the PSP 8.00 addresses this problem, but I'll have to contact the engineer responsible for the VCA to determine if this is a true statement.

If you would like to spend the time, I'll take a look at the HPSUM trace files on your server to attempt to determine why the VCA did not update. If you can attach the files from the %TEMP%\hp_sum directory structure, I'll see why the VCA was not installed. It would also be beneficial to see the trace files from a server that is working so I can compare the two.

As Kario states, we provide the BP*.CMD file that can be used in place of HPSUM. The BP*.CMD file is a brute-force script that just calls every component with the silent option. You can pass in the /force switch and it will force all components to install. We normally don't recommend using this CMD file because it does not provide any dependency checking, provides no remote capabilities, doesn't allow any modifications to the installation, doesn't validate the installation order, and has limited testing performed on it among other things. However, in cases where HPSUM doesn't work for some reason, it can be used to deploy a PSP.

Regards,
Michael Garner
HPSUM Architect

[KimO_1]

There is a known problem with the VCA not upgrading from version 7.80 to 8.00. As a workaround, attempt a sequential upgrade of the PSP from version 7.80 to version 7.90 and then to version 8.00, rather than attempting to upgrade directly from version 7.80 to version 8.00.

When components are installed in sequential order, the VCA will be successfully upgraded and the VCA Software Status will be displayed as Green, indicating that the software is at the latest available version.

[KarloChacon]

hi

thanks Michael that is a good information

by the way I need to do some test with HPSUM command line...

regards

[mark q]

as for the chipset identifer it's only happened a few times and I noticed it wasn't part of psp 8.0. I am wondering here do you want people to group support paq's together because there are also things that are installed in older support paq's which aren't in the newer (hp protected your data) for example?

I don't deploy updates through insight manager I do them as you've seen through the commandline becuase I'm cleaning up on allot of lack of updates (firmware etc) so I have to check each on after the update.

I wish that in the readme's for the support paq, you could let people know what's not in them and why.. for example 8.0 had tape drivers 7.91 didn't..

it's just frustrating that I have to circle back now, find the older driver and install it to make sure that the vcagent picks up the right one even though it's not part of the support paq.

[mark q]

thanks