HP Version Control 6.
© Copyright 2004-2009 Hewlett-Packard Development Company, L.P. Legal Notices 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.
Table of Contents 1 Product overview........................................................................................9 VCRM...................................................................................................................................................9 VCA......................................................................................................................................................9 HP SIM integration............................................................
Hardware and software ..............................................................................................................28 Installing the VCA for Linux.....................................................................................................................29 Verifying the VCA service is running...................................................................................................30 Installing the VCA for Linux silently......................................................
Glossary....................................................................................................55 Index.........................................................................................................
List of Tables 1 Publishing history................................................................................................................................
1 Product overview Today’s distributed enterprise networks are some of the most complex ever constructed. As companies deploy more business-critical applications, these networks continue to rapidly expand, becoming more sophisticated and requiring servers that support the latest technological innovations. In this fast-changing environment, any loss of availability translates into a loss of time and money, and manageability has become the leading success criterion for today’s highly competitive businesses.
Updates can be scheduled and applied to specific sets of servers based on predetermined criteria, including applying updates only to those systems that require an update.
VCA The VCA is available for Windows and Linux operating systems. The VCA is an integrated part of the SMH that is designed to display the available software inventory of the server on which it is installed. The VCA also enables the installation, comparison, and update of server software from a repository that is managed by the VCRM. Users with administrator or operator privileges can access the VCA to maintain the software inventory of the server manually.
All connections and data are transferred using Secure Sockets Layer (SSL) communications over HTTP. Interactive users connect using a web browser (client) application. The specific security depends on which web application they are browsing. HP SIM uses operating systems authentication, based on the server where it is installed. Single sign-on enables a user that browses to the HP SIM system to follow links from that system to other managed systems without being prompted to login again.
2 Migrating Version Control to the System Management Homepage Migrating Version Control with ProLiant Support Pack 7.1 and earlier Legacy VCA continues to report accurately after upgrading Management HTTP Server to SMH since SMH detects installed Web Agents and migrates the administrator credentials. Legacy VCA uses legacy SMH account names including administrator, operator, and user. Migrating Version Control with ProLiant Support Pack 7.
the VCA, you must use an account name that matches one of the non-administrator accounts the earlier versions of the SMH defined, for example, operator or user. By default, the VCA is unable to login with an account named administrator using operating system authentication, to prevent an accidental lockout of the local administrator account. To add operating system accounts: 1. 2. 3. 4. 5. 6. 7. 8. 9. Select Start→Settings→Control Panel. Double-click Users and Passwords.
7. Change the configuration of the VCAs that are already installed. There are several ways to change the configuration, including: a. HP SIM users should use Replicate Agent Settings to configure one VCA to the account and password previously created in step 3, and then deploy that configuration to all installed VCAs. Note: This is the lowest impact solution, and it does not cause a reboot or restart of the affected systems. b.
3 Obtaining the software This chapter provides information regarding obtaining the VCA, VCRM, and HP SIM. Obtaining VCA, VCRM, and HP SIM VCA The VCA is available from the following sources: • ProLiant Support Pack or Integrity Support Pack. To download the latest version of the ProLiant Support Pack, go to http://www.hp.com/servers/swdrivers or to download the latest Integrity Support Pack, go to http://www.hp.com/support/itaniumservers.
4 Installing the VCA using HP Systems Insight Manager HP SIM is a system management software that is capable of managing a wide variety of systems, including HP systems, clusters, desktops, workstations, and portables. You can use the Initial ProLiant Support Pack Install or the Configure or repair Agents options to deploy VCA and other agents to all the Windows managed systems.
5 Installing the VCA on Windows operating systems VCA for Windows requirements The VCA can be used in conjunction with HP SIM and the VCRM. The options must be configured for full functionality. The installation of the VCA requires that you specify a certified login with a VCRM. When specified, VCAs can determine the versions of HP software and firmware installed on each individual system and compare the version with the latest software or firmware and baseline definitions available in the VCRM.
• • Hardware • ProLiant Server • Windows Integrity Servers Disk space • 11 MB on the Windows SystemDrive Note: The VCA installer can require up to 12 MB of additional free space on your Windows SystemDrive to complete the installation. • • 70 MB for Integrity servers System memory • 256 MB of RAM for Windows Server 2003 • 256 MB of RAM for Windows 2003 Server ES for 64-bit Extended Systems (starting with the ProLiant Support Pack 7.
The VCA installation executable is located in the following locations: • http://www.hp.com/servers/manage • HP SmartStart DVD • HP SmartSetup CD • Software Update CD • A repository managed by the VCRM that contains the latest Windows ProLiant and Integrity Support Pack. Installing the VCA for Windows The VCA installation wizard launches in interactive mode when the installation executable is run from the command line or launched from Windows Explorer.
Installing silently using the CLI To install silently using the CLI: From a command prompt, enter the following command: component name /silent For example, you might enter c:\>cp00xxxx.exe /silent. or c:\>cp00xxxx.exe /s Note: Be sure to configure the VCA component using the HP Smart Update Manager before installing it to remote systems. If the component is not configured, the VCA displays an unknown status.
6 Installing the VCA using the Linux Deployment Utility The Linux Deployment Utility provides an easy and efficient method to upgrade and manage system software. The utility enables you to deploy and maintain ProLiant and Integrity Support Pack software on local servers through use of the terminal window and on remote servers through use of the secure shell (ssh) utility. The Linux Deployment Utility is shipped with the Linux ProLiant and Integrity Support Pack, which is available on the HP SmartStart DVD.
7 Installing the VCA on Linux operating systems VCA for Linux requirements The VCA can be used in conjunction with HP SIM and the VCRM. The options must be configured for full functionality. The following diagram illustrates a logical order to the VCA installation process on a Linux operating system. System requirements To install the VCA on a Linux system, the system must meet the following requirements.
• • • SUSE Linux Enterprise Server 9 for x86, Service Pack 4 • SUSE Linux Enterprise Server 9 with Service Pack 4 for AMD64 and Intel EM64T (starting with the ProLiant Support Pack 7.2 and later) Server software • SMH (hpsmh RPM) installed • HP Server Management Application and Agents (hpasm RPM) 7.
• • • SUSE Linux Enterprise Server 9 for x86, Service Pack 4 • SUSE Linux Enterprise Server 9 with Service Pack 4 for AMD64 and Intel EM64T (starting with the ProLiant Support Pack 7.2 and later) Browsers • Internet Explorer 8.0 • Mozilla 1.7 (local or remote access) or later • Firefox 1.0 or later System memory • 128 MB of RAM Note: You can browse to a Linux server from a Windows system using Internet Explorer 6.0 or higher.
Verifying the VCA service is running To verify the VCA service is running on the system, enter the following: 1. For UnitedLinux and SUSE Linux, execute the following command: /etc/init.d/hpvca status The output that appears is similar to: Checking for process hpvca: running 2.
8 Installing the VCRM on Windows VCRM requirements for Windows The following diagram illustrates a logical order to the VCRM installation process. System requirements To install the VCRM, the computer must meet the minimum requirements listed.
• • • • Server software • TCP/IP installed • SMH installed Hardware • ProLiant Server • HP Business Desktops • Windows Integrity Servers Disk space • 14-15 MB (Installation files only) • 200 MB in the VCRM installation drive for temporary ProLiant or Integrity Support Pack extraction • 2 GB for the repository. This must be on a local, writeable drive.
• Mozilla 1.6 or later • Mozilla 3.0 Note: Uploading software by way of the Mozilla browser interface is not supported. • System memory • 256 MB of RAM for Windows XP or Windows Server 2003 Configuring Internet Explorer settings for SMH pre-configuration Some features of the VCRM's browser interface depend on browser settings at the client system from which the VCRM is being accessed. The security settings in Microsoft Internet Explorer must be set to initialize the VCRM Upload process.
5. The VCRM installation wizard initiates the HP Insight Management Agent configuration settings in interactive mode when the installation executable is run from the command line or launched from Windows Explorer. After the wizard initiates, the HP Setup - VCRM dialog box appears. If you have a previous version of the VCRM installed on a machine, the installation wizard detects it and initiates the upgrade with the current version displayed in the dialog box.
3. Select Perform an initial repository population if you want to have the repository updated with ProLiant and Integrity Support Packs. NOTE: If Perform an initial repository population is deselected, or the option is not displayed, the Select OS for PSP download page appears next. 4. Click Next to accept the selected directory. If you selected Perform an initial repository population on the previous dialog box, the VCRM Setup - Initial Repository Configuration dialog box appears.
6. Click Finish to save the VCRM settings. If Automatic Update is enabled and a proxy server is configured, the connection with the proxy server is verified before continuing. If the proxy server cannot be reached, a message appears indicating there was an error testing the download of the autoupdate catalog. Click Yes to save your settings or click No to re-enter the proxy server information. 7. 8. The HP Setup wizard page appears, and the installation begins.
9 Updating a repository The autoupdate feature of the HP Version Control Repository Manager is the preferred solution for updating repositories automatically. The autoupdate feature of the VCRM keeps servers connected to HP for proactive delivery of the latest ProLiant and Integrity Support Packs and components directly to a specified repository.
4. 5. 6. 7. 8. 9. From within the Contents directory, click supportpack to open the directory. The contents directory contains a supportpack directory that contains all Integrity Support Packs. After you have opened the directory, select all of the Integrity Support Pack files, click Edit from the Windows Explorer toolbar, and select Copy. From Windows Explorer, navigate to the repository directory, for example, c:\repository. Select the repository directory.
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.
NOTE: VCRM is restarted while executing vcrmcli.exe file. NOTE: The displayed XML output may contain Proxy server password. Selecting the operating systems to download ProLiant Support Packs From the command prompt, enter the following command: vcrmcli.exe /os "OS version" The command configures the operating systems listed to download ProLiant Support Packs. Example: vcrmcli.
NOTE: VCRM is restarted while executing vcrmcli.exe file. NOTE: Specify the values for the parameters in double quotation marks (""). Initializing the update from the web From the command prompt, enter the following command: vcrmcli.exe /updatenow NOTE: VCRM is restarted while executing vcrmcli.exe file.
NOTE: If /proxyuser argument has a valid user name and /proxypwd is not used as argument, vcrmcli.exe prompts the user for a password during execution. The command configures the autoupdate schedule settings to update the repository on Sunday 10 PM.
10 Uninstalling the VCA on Windows operating systems To uninstall the VCA: 1. 2. 3. 4. 5. Select Start→Settings→Control Panel. Click Add/Remove Programs. The Add/Remove Programs Properties dialog box appears with a listing of installed software. Select VCA. Click Change/Remove. The Remove dialog box appears asking you to confirm your intention to remove the VCA. Click Yes.
11 Uninstalling the VCA on Linux operating systems To uninstall the VCA for Linux: To uninstall the HP Version Control Agent, log in as root, and execute the following command: # rpm –e For example, # rpm –e hpvca where, hpvca is the version control package name. The VCA is uninstalled. Note: After the VCA has been removed, the configuration options and logs are deleted.
12 Uninstalling the VCRM on Windows operating systems To uninstall VCRM: 1. 2. 3. 4. 5. Select Start→Settings→Control Panel. Click Add/Remove Programs. The Add/Remove Programs dialog box appears with a listing of installed software. Select VCRM. Click Change/Remove. The Remove dialog box appears asking you to confirm your intention to remove the VCRM. Click Yes. If you decide you do not want to uninstall the VCRM, click No to cancel.
Support and other resources New and changed information in this edition The following sections list what is new for the HP Version Control releases. November 2009, Version Control 6.0 release Following are the product enhancements for the HP Version Control 6.0 November 2009 release: HP Version Control Agent (VCA) adds the following enhancements with the current release: • Native x64 (64 bit) support. • Support for Trusted Platform Module (TPM).
in PDF format from http://h18013.www1.hp.com/products/servers/management/agents/ documentation.html. • HP System Management Homepage Installation Guide. The System Management Homepage Installation Guide provides information about installing and getting started using the SMH. This guide includes an introduction to basic concepts, definitions, and functionality associated with the VCA and VCRM. This document is available on the HP Management DVD and at http://h18013.www1.hp.
HP Encourages Your Comments HP encourages your comments concerning this document. HP is committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: feedback@fc.hp.com. Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
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) The 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 data migration VCRM, 38 VCA for Windows, 45 VCA Linux, 47 VCRM, 49 update software, 9 F V features, 9 new, 51 VCA Linux client requirements, 28 Linux install, 27, 29 Linux system requirements, 27 Linux uninstall, 47 obtaining software, 17 overview, 9 requirements for Windows, 21 Windows client requirements, 22 Windows installation, 21 Windows system requirements, 21 Windows uninstall, 45 VCRM client requirements, 32 installation, 31 obtaining software, 17 overview, 9 system requirements, 31 unins
