HP Version Control Repository Manager HP Part Number: 367261-008 Published: November 2009 Edition: 15
© Copyright 2005-2009 Hewlett-Packard Development Company, L.P.
Table of Contents 1 Product overview........................................................................................7 Additional resources................................................................................................................................8 Related topics.........................................................................................................................................8 2 Getting started.................................................................
Uploading support packs..................................................................................................................21 Related topics............................................................................................................................22 Creating a custom software baseline..................................................................................................23 Related topics.................................................................................
ProLiant Support Pack problems.........................................................................................................42 Miscellaneous problems.........................................................................................................................43 Service and support..............................................................................................................................43 Windows events..................................................................
1 Product overview The HP Version Control Repository Manager (VCRM) is a repository that stores the software and firmware components used to support ProLiant servers on Windows and Linux platforms. By default, the VCRM is installed on the HP Systems Insight Manager (HP SIM) central management server; however, you can specify a custom directory or a server location.
• “Initializing the update from the web” - Initializing the autoupdate from the web. • “Configuring automatic update for VCRM directory” - Configuring automatic update for VCRM repository directory. Additional resources For additional resources, go to http://www.hp.com/servers/manage.
2 Getting started To start using the HP Version Control Repository Manager (VCRM), use the following steps as a guideline for installing and configuring your machines properly: The recommended installation for the VCRM is on a single system that has a reliable, high-performance network connection between it and all managed systems that have the HP Version Control Agents installed. If the Auto Update feature is being used, that system must have Internet access. 1. 2. 3. 4. 5.
To log in: 1. 2. 3. To access the VCRM with access to all available features, you must log in to the System Management Homepage (SMH) with administrator or operator level access. To log in to the SMH: a. From the system where the VCRM is installed, navigate to https://VCRMSystem:2381. If the SMH is configured to allow anonymous access, click the Login link on the upper right corner of the page, otherwise you are immediately directed to the login page. b.
Related topics • Home • Catalog • Log Updating the repository Configuring the repository using VCRM CLI This section describes procedures that you can use to configure the repository using the VCRM CLI.
• Rhel4 downloads ProLiant Support Packs on Red Hat Enterprise Linux 4 server x86 platform. • Rhel4x64 downloads ProLiant Support Packs on Red Hat Enterprise Linux 4 server AMD64/EM64T platforms. NOTE: Executing the command vcrmcli.exe /os without any value displays all the supported operating system attributes. NOTE: VCRM downloads ProLiant Support Packs for HP Version Control Agent's operating systems. Changing the repository folder From the command prompt, enter the following command: vcrmcli.
vcrmcli.exe /autoupdate /interval “7” /dayofweek “0” /time “22” /proxyname “proxy.domain.com” /proxyport “1234” /proxyuser “” /proxypwd “” NOTE: Specify the values for each of the parameters in double quotation marks (""). where, /interval "7" corresponds to one week (7 days, valid values: 1, 2, 7, 14, 28) /dayofweek "0" corresponds to Sunday (0 is default, and is not used if the interval is less than 7.
Repository Population - Initial Installation 1. 2. Click Add to select a directory that contains a ProLiant and Integrity Support Pack. The Browse for Folder dialog box appears. Navigate to the directory that contains a ProLiant and Integrity Support Pack, and click OK or Cancel to abort the selection. All Support Packs found in the selected directory are added to the list shown in the Initial Repository Configuration dialog box.
Updating the Repository The automatic update feature of the HP Version Control Repository Manager (VCRM) is the preferred solution for updating repositories automatically. The automatic update feature of the VCRM keeps servers connected to HP for proactive delivery of the latest HP ProLiant and Integrity Support Packs and components directly to a specified repository. You can configure the automatic population of the repository during the VCRM installation or after installation.
5. 6. 7. 8. 9. The CSP directory contains a Linux directory for Linux-related Support Packs and a Windows NT® directory that contains all of the components and support packs and an XML file for each supported Microsoft operating system. Click Linux or NT depending on the type of Support Packs with which you want to populate your repository. After you have opened one of the directories, select all of the Support Pack files, click Edit from the Windows Explorer toolbar, and select Copy.
3 Navigating the software You can access the HP Version Control Repository Manager (VCRM) by navigating to https://VCRMSystem:2381/vcrepository, or you can access it from the Version Control status box on the System Management Homepage (SMH).
3. 4. 5. 6. 7. Select the Trusted sites icon. Click Sites.... The Trusted sites dialog box appears. In the Add this Web site to the zone field, enter https://hostname:2381/ and click Add. Click OK to save your changes and close the Trusted sites dialog box. Click OK to close the Internet Options dialog box.
Note: You can access a full listing of all available ProLiant and Integrity Support Packs and components by clicking the Catalog tab. Procedures • Configuring Auto Update • Creating a custom software baseline Related topics • Uploading support packs • Viewing a custom software baseline Viewing a custom software baseline You can view the details regarding a Custom Software Baseline, HP ProLiant and Integrity Support Pack, or component details.
NOTE: 1. 2. 3. You can also configure the Automatic Update Settings using the Command Line Interface (CLI). Click the Home tab. The Home page appears. Click the Configure the Repository and Automatic Update Settings link. The Repository Directory page appears. In the Directory field, enter the location that you want to monitor for components and HP ProLiant and Integrity Support Packs. This must be a local path on the repository system.
c. In the Day of Week and Time of Day fields, select the day of the week that you want to automatically update from the dropdown menu, then in the next field, select the time you want to automatically update from the dropdown menu. Note: If you select one day or two days from the Interval between updates option, the Day of Week option is unavailable because the update happens daily, or every two days, from the day you made the selection.
NOTE: You can install ProLiant Support Packs from the HP SmartStart CD. Refer to “Updating the repository” to learn how to update the repository from the HP SmartStart CD. NOTE: This feature is only supported on the Internet Explorer browser, and you must have configured your security settings to allow downloading and installing the Version Control Upload (ActiveX) Control. NOTE: For information regarding Microsoft Internet Explorer Security Settings, refer to “Configuring Internet Explorer settings”.
Creating a custom software baseline The HP Version Control Repository Manager (VCRM) enables you to create Custom Software Baselines based on the selected software components or HP ProLiant and Integrity Support Packs. NOTE: You can also create a support pack from the Home or Catalog page. To create a Support Pack from the Home page: 1. 2. Click the Home tab. The Home page appears. Click the Create a Custom Software Baseline link. The Create a Custom Software Baseline page appears.
• “Viewing component details” • “Clearing the log” • “Changing log settings” Procedures • Changing log settings • Clearing the log • Viewing component details • Viewing the log • Viewing log entry details • Viewing recently added HP ProLiant and HP Integrity Support Packs Viewing the log To view the log, click the Log tab. The Log page appears. The Log entries are displayed in three columns: • Severity The status icons report the severity of an event.
Icon Status Events of this type indicate an impending failure and are orange in color. Events of this type indicate a warning condition that might escalate into a more serious problem and are yellow in color. Events of this type are operating normally and are green in color. Events of this type require no attention. They are provided as useful information and are blue in color.
Related topics • Clearing the log • Viewing the log Clearing the log If you are logged into the system with Operator or Administrator privileges, you can clear the HP Version Control Repository Manager Log. To clear the log: 1. 2. Click the Log tab. The Log page appears. Click Clear the Log. The Clear the VCRM Log page appears. Optionally, select Save Log Text to save a text only page of the log data before clearing all entries.
Icon Status Configured. The component is configured. By moving your mouse over this icon, the configuration date appears. You can reconfigure the associated component by clicking this icon. Disabled Configuration. Configuration is disabled because you are not logged in as Administrator or Operator. ProLiant and Integrity Support Pack item. Custom Software Baseline item.
Related topics • Viewing the log • Viewing log entry details • Uploading support packs Viewing component details You can access the Component Details page for log entries regarding added components. To access component details: 1. 2. Click the Log tab. The Log page appears. Locate the log entry for the component about which you want to view details. Click the link provided at the end of the log entry. The Component Details page appears.
To copy desired Custom Software Baselines, ProLiant and Integrity Support Packs, or components from the Catalog page: 1. 2. 3. 4. Click the Catalog tab. The Catalog page appears. Click the Copy Items to Another Repository link. The Copy Support Packs and Components page appears. Select the components and Support Packs you want to copy. Click Reset to clear the selected items or Cancel to abort the copy operation. Click Next. The Copy page appears. a.
1. Click the Catalog tab. The Catalog page appears. 2. Click the Copy Items to Another Repository link. The Copy Support Packs and Components page appears. 3. Select the Migrate HP Version Control Repository Manager Settings checkbox. Click Reset to clear the selected checkbox or Cancel to abort the VCRM data migration operation.
4. Click Next. The Destination Version Control Repository Manager page appears. a. b. c. 5. 6. In the Computer Name field, enter the name of the computer to which the VCRM settings and data are to be copied. In the Login field, enter the login name. In the Password field, enter the password for the account you entered. Click Finish. Click Back to return to the previous page, or Cancel to abort the Copy request. Click Close. The Catalog page is refreshed.
1. 2. 3. Click the Catalog tab. The Catalog page appears. Click the Rescan the Repository and Rebuild the Catalog link. The Confirm Rescan dialog box appears. Click Cancel to abort the rescan process. Click Ok to rescan the repository directory and rebuild the catalog. When the process is complete, the refreshed Catalog page appears.
Deleting Items from the repository The HP Version Control Repository Manager (VCRM) enables you to delete selected Custom Software Baselines, HP ProLiant and Integrity Support Packs, and components. CAUTION: Deleting a ProLiant and Integrity Support Pack or component is irreversible. Use this feature with caution. If you delete a file and want to recover it, you must use one of the manual methods to restore the component or ProLiant and Integrity Support Pack to the repository.
4 Troubleshooting HP Version Control Agent Access problems My Install buttons are grayed out in the VCA when I configure the VCA with administrator, operator or even invalid credentials to connect to the VCRM. Solution: The VCRM's SMH has anonymous access enabled. HP recommends that you upgrade the VCRM with the version from the 7.50 HP Management CD.
this specific case, the component setup program detected that the installation succeeded, but will not be complete until the system is rebooted. The VCA does not reboot the system after each component install, but at the end of all installations, to avoid unnecessary restarts. If the installation task was started without the reboot automatically option selected, you must restart the server manually to ensure proper installation of all software.
4. 5. 6. 7. Click Sites.... The Trusted sites dialog box appears. In the Add this Web site to the zone field, enter https://hostname:2381/ and click Add. Click OK to save your changes and close the Trusted sites dialog box. Click OK to close the Internet Options dialog box. Print problems When I try to print from a Mozilla browser, a dialog box displays indicating there is an Unknown Error. Why is this happening? Solution: A default printer has not been configured.
Software inventory problems Why do some of the components display in the inventory for hardware that is not physically located on my server? Solution: This issue is caused by a conflict between SmartStart and the VCA and might display with Yellow status icons in the Latest Version and Support Pack columns.
Add the following exceptions to the firewall protection: Product Port Number HP SMH Insecure Port: 2301 HP SMH Secure Port: 2381 Note: For more information regarding HP SIM secure and insecure ports, refer to the HP SIM User Guide, Troubleshooting, Login Problems section. 5. 6. Click OK to save your settings and close the Add a Port dialog box. Click OK to save your settings and close the Windows Firewall dialog box.
Solution: While the automatic update process was in progress, the VCRM was unable to connect to the website. HP recommends the following actions: • Verify that the hardware connection for the Internet is secure, for example, phone line or cable, to the machine where the VCRM is installed. • Verify the domain name server (DNS) settings are correct. • Verify that the proxy server, port, and proxy user authentication settings are correct.
5. 6. Copy the contents of the directory \compaq\wbem_old to \compaq\wbem. Restart the following services: • All Insight Management Agents • Array Configuration Utility • HP Version Control Repository Manager • HP Version Control Agent • HP Insight Management Agent • Surveyor • HP Insight Control performance management • HP Insight Control performance management Tools The VCRM is accessible from SMH and from https://VCRMSystem:2381.
3. 4. Start preconfiguring the SMH component. When you select the certificate file using Browse, an Internet Explorer warning appears regarding ActiveX Controls. Click Yes to load the certificate file. ProLiant Support Pack problems The ProLiant Support Pack installation terminates due to low disk space. Solution: After setting the repository directory with the encryption attribute and restarting the VCRM service, none of the ProLiant Support Packs are displayed in the VCRM Catalog page.
Miscellaneous problems Should the VCRM be installed before running Discovery in HP SIM, and if so, why? Solution: While it is not essential, it is a good idea to install a VCRM before running Discovery. Be sure that this repository trusts HP SIM. Refer to Setting up Trust Relationships in the HP SIM User Guide for more information on trust relationships. It is a good idea to install a VCRM is so that the Software Version Status Polling task can properly sort the versions of software retrieved from systems.
• Survey Utility output or Inspect printout • System Configuration Utility printout • Description of any non-HP or non-Compaq equipment that is not shown on the Inspect or System Configuration printout. Windows events The following table shows a listing of Windows 2000/Window NT events that are applicable to the HP Version Control Repository Manager. Event ID Facility Severity Text 4098 Application Informational VCRM failed to start.
5 Legal notices Warranty The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental, or consequential damages in connection with the furnishing, performance, or use of this material.
Licensing Software Licensing HP Version Control Repository Manager software includes open source and proprietary software developed or obtained through the third parties listed in the table below. More specifically, the developed or obtained code consists of the licensed Ancillary Software listed below. Installation, copying or otherwise using the Product (as defined in the End-User License Agreement) constitutes acceptance of the Ancillary Software license terms, whether such terms are reviewed.
3. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a. You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b.
5. 6. 7. 8. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The entire risk as to the quality and performance of the program is with you. Should the program prove defective, you assume the cost of all necessary servicing, repair or correction. 13.
invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application.
6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. a.
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all.
Related topics • Licensing • OpenSSL Software Licensing • Zlib Compression Library Zlib Compression Library zlib/libpng license END-USER LICENSE AGREEMENT zlib.h -- interface of the 'zlib' general purpose compression library version 1.1.3, July 9th, 1998 Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION.
Related topics • Licensing • gnu software licensing • Zlib Compression Library Licensing 55
Glossary available software A listing of the software components available in the repository that the VCA has been configured to point to. When browsing directly into a VCA, these additional components can be selected for installation. component A component is a single, self-describing, installable (interactive or silent) binary file containing a single piece of software, such as firmware image, driver, agent, or utility, that is supported by the management and update tools.
Replicate Agent Settings A tool that can be used to copy Web-based agent settings to a group of systems. repository A directory containing ProLiant and Integrity Support Packs and Smart Components. Secure Task Execution (STE) Secure execution of a task from a managed system. This feature of HP SIM ensures that the user requesting the task has the appropriate rights to perform the task, and encrypts the request to protect data from snooping.
Index HP SIM , 35 Log, 35, 41 miscellaneous, 43 print, 37 ProLiant Support Pack, 42 Replicate Agent Settings, 37 software inventory, 38 A about, 10 C catalog page icons, 26 changing, 25 clearing HP Version Control Repository Manager , 26 configuring, 17, 19, 28 copying, 28 copyright notice, 45 creating, 23 D data migration, 29 deleting, 33 G R release history, 45 repository, 11, 28, 29, 31, 32, 33 rescanning, 31 S security, 17 service support, 43 signing out, 10 software repositories, 10 getting star
