08-16-2013 10:48 AM - edited 08-16-2013 10:54 AM
today I realized that our VCRM (220.127.116.11) detects and auto-updates all software components, but doesn't even detect the online firmware packages for our Proliant servers. tried forcing manual sync with HP and it said "no new updates" while on HP download pages I see updated online firmware components (BIOS, Lights-out, SmartArray, etc.)
exact message from VCRM logs returns no error at all:
8/16/2013 12:36:04 PM The automatic repository update process completed successfully. No new, applicable files were found for download.
8/16/2013 12:35:28 PM Automatic update started successfully [ details]
Updated components not detected by VCRM (sync doesn't pull them, but they are not even listed in catalog at all):
Proliant ML350 G6:
14 Aug 2013
Proliant ML350 G8:
- 13 Aug 2013
- 23 Apr 2013
- 8 May 2013
there may be more.
Why is that? are they not available for automatic download (VCRM sync) on HP servers??? that used to work prior to April 2013 ... all other (software updates) are detectd, pulled and listed in VCRM and visible through agents.
anybody else seeing this?
Solved! Go to Solution.
08-20-2013 09:43 AM - edited 08-21-2013 11:42 AM
I tried manually adding the cp***.exe files to repository and found out that packages for Smart Array and Lights out were there, only the online BIOS update packages were missing (not synced).
However, still none of them were listed as available for installation when looking through VC agents on respective servers.
For now, I started the Catalog rescan and rebuild in VCRM, will see if those files get indexed finally.
files were properly indexed and now show up in Catalog (e.g. when checking via VCagent), but how do I know if it really works and pulls new updates to online firmware components in future on its own?
09-17-2013 10:40 AM
I updated everything manually, including VCRM update to 18.104.22.168 and now a new problem, VCRM settings are specifically set for pulling catalog updates on Windows 2008 (x86, x64 and R2) only ... since yesterday the VCRM is downloading Redhat *.rpm packages ... wth ...
09-20-2013 08:12 AM
Here is what I did:
1) uninstalled Repository Manager completely, had to shoot down a process it was using for updating (pulling linux packages), then it completed uninstallation of itself gracefully
2) removed the registry entry for VCRM [HKLM/Software/Hewlett-packard/VersionControl]
3) removed manually all linux packages and corresponding manifest files
4) installed the same latest version again
5) selected same Windows versions in configuration and let it re-scan repository
all works now and VCRM now pulls new support packs and individual components.
Hope it helps others having similar issues.