level 7 protocol of Version Control Agent

[Dietmar Hildebrand]

The Version Control User Guide very vagely says "The Version Control Agent determines server software status by comparing each component installed on the local system with the set of individual components or a specified ProLiant Support Pack listed in the Version Control Repository Manager."
Is there any manual or white paper, which is more specific. Does it compare some magic numbers (small packets) or does it everytime request a detailed report from the VCM? a diagram of the handshake would show what kind of traffic this causes.
Any hint appreciated

[David Claypool]

The ProLiant Support Pack is "held together" by an XML formatted file. When the Version Control Agent is started, it requests the XML file from the VCRM for the Reference Support Pack set in the VCA. That happens at agent startup and isn't re-requested unless the agent is restarted or the reference support pack or the VCRM is changed. The VCA is intelligent and creates the status indication on its own. When HP SIM or IM7 do a Software Status Poll, it only requests the single status indicator.

So, infrequently the XML file is pulled down and when the poll takes place a few bytes are exchanged. The bpXXXXXX.xml file is typically around 50K. Assume a little overhead because this is done over Secure HTTP. Not much to worry about in today's modern 100mbit LAN environment. If you have some far-flung sites that you don't want bogging down a slow connection when you reboot by getting their XML file centrally, consider putting a VCRM at the site so the VCAs can get it locally.

[Dietmar Hildebrand]

Where do I find XML tag definitions or a description how the update actually works.
e.g. is it always transfering complete files or is there a mechanism to use deltas (diffs)( to reduce network traffic). Is there a mechanism to remove files, which are no longer needed in a new release (prevent cluttering of systems with leftover old files)?

[David Claypool]

Where do I find XML tag definitions

[not documented; it would be difficult and is not recommended to try and hand-craft XML for a PSP. Use the 'Create Custom Support Pack' in VCRM to personalize for your use.]

or a description how the update actually works.

[When IM7 executes a Software/Firmware Update Task it communicates with all of the VCAs to tell them to initiate an update. The VCA then calls the VCRM and pulls down the entire PSP. Locally the VCA executes the PSP using the setupc.exe command line utility. setupc determines if the component in the PSP is valid for the system or needs updating and will skip as necessary unless the force flag is used.]

e.g. is it always transfering complete files

[yes]

or is there a mechanism to use deltas (diffs)( to reduce network traffic).

[no, this product is not that sophisticated. Schedule your updates in off-hours and consider multiple VCRMs local to each site if you are in a WAN.]

Is there a mechanism to remove files, which are no longer needed in a new release (prevent cluttering of systems with leftover old files)?

[The PSP cleans up its temp files after completion. VCRM, however, does not have a method to age files and delete them automatically from the library.]