VITALQIP APPLIANCE MANAGER (AM) 1.

7 RELEASE NOTES

190-409-110R1.7 Issue 8 November 2011

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

TABLE OF CONTENTS 1. INTRODUCTION ................................................................................................................................ 3 1.1. RELEASE INFORMATION ............................................................................................................... 3 1.1.1. Reason for Reissue ................................................................................................................. 3 1.1.2. Electronic Availability............................................................................................................ 4 1.1.3. Ordering Documentation Online ............................................................................................ 4 2. INSTALLATION REQUIREMENTS FOR AM RELEASE 1.7 ..................................................... 5 2.1. 2.2. 2.2.1. 2.3. 2.4. 2.5. 3. SUPPORTED PLATFORMS .............................................................................................................. 5 THIRD-PARTY OR OTHER HARDWARE/SOFTWARE REQUIREMENTS................................................ 5 DNS High Availability ........................................................................................................... 5 SOFTWARE REQUIREMENTS ......................................................................................................... 6 SYSTEM REQUIREMENTS .............................................................................................................. 6 PRE-INSTALLATION REQUIREMENTS ............................................................................................ 6

RELEASE DESCRIPTION................................................................................................................. 7 3.1. 3.2. 3.2.1. 3.2.2. 3.3. 3.4. 3.4.1. FEATURES IN VITALQIP APPLIANCE MANAGER RELEASE 1.7 ..................................................... 7 PACKAGES INCLUDED IN APPLIANCE MANAGER 1.7 .................................................................... 8 The Supported Platform for Packages .................................................................................. 10 Enterprise Package Frequently Asked Question................................................................... 11 RESOLVED ISSUES ...................................................................................................................... 12 KNOWN ISSUES .......................................................................................................................... 14 SSL Configuration Limitation for Enterprise Appliance...................................................... 15

4.

SOFTWARE APPLIANCE MANAGER RELEASE 1.7............................................................... 16 4.1. 4.2. 4.3. 4.4. SOFTWARE APPLIANCE MANAGER ............................................................................................. 16 LICENSING FOR SAM ................................................................................................................. 16 SUPPORTED PLATFORMS ............................................................................................................ 17 HARDWARE SUPPORT POLICY .................................................................................................... 18

5. 6.

DOCUMENTATION ......................................................................................................................... 19 INSTALLING VITALQIP APPLIANCE MANAGER .................................................................. 20 6.1. OBTAINING INSTALLATION FILES ............................................................................................... 20 6.1.1. Installation Files by ALED................................................................................................... 20 6.1.1.1. For Appliance Manager............................................................................................... 20 6.1.1.2. For Software Appliance Manager ............................................................................... 20 6.2. UPGRADING AMS ON RHEL4 TO AMS 1.6 ............................................................................... 21 6.3. UPGRADING AN APPLIANCE ....................................................................................................... 21 6.3.1. Download AM 1.7 Content from ALED .............................................................................. 21 6.3.2. Upgrade AMS....................................................................................................................... 22 6.3.3. Enable AutoConfig ............................................................................................................... 22 6.3.3.1. Method 1: Enable AutoConfig on appliance............................................................... 23 6.3.3.2. Method 2: Remove console account in AMS.............................................................. 23 6.3.4. Upgrade the ESM Appliance ................................................................................................ 23 6.3.5. Upgrade AMM Appliances................................................................................................... 24 6.4. SERVICE PACKAGES DIRECTORY STRUCTURE ............................................................................. 26

7.

SUPPORTING INFORMATION ..................................................................................................... 29 7.1. GLOSSARY- ACRONYMS AND DEFINITIONS ................................................................................ 29

Page 2 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

1. INTRODUCTION
1.1. Release Information

VitalQIP Appliance Manager (AM), Release 1.7 is released in November, 2011.

1.1.1.

REASON FOR REISSUE

The Appliance Manager 1.7 Release Notes has been reissued. Refer to the following table to review the revision history of this document.
Issue number Date of issue Description of changes Availability of packages to support DNS 4.2.19, DNS 5.0.14 and DNS SNMP 5.0.14 that contains the fix for ISC BIND CERT Advisory CVE-2011-4313. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of packages to support DNS 5.1.15 and DNS SNMP 5.1.15 that contains the fix for ISC BIND CERT Advisory CVE-2011-4313. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of VitalQIP 7.2PR4 packages 7.2.1708-1. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of DNS package 4.2.18-2 to fix the CR HELIO00005917. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of packages to support DNS 5.1.12, DNS SNMP 5.1.12, DHCP 6.0.11 and DHCP SNMP 6.0.11. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of packages to support DHCP 5.6.18. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Availability of packages to support DNS 5.1.9, DNS SNMP 5.1.9, DHCP 6.0.10 and DHCP SNMP 6.0.10. Refer to Table 6 Appliance packages, Table 7 Platform for Packages and Service Packages directory structure. Original release of AMS 1.7

November 2011

November 2011

October 2011

August 2011

July 2011

June 2011

June 2011

May 2011

Page 3 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

1.1.2. ELECTRONIC AVAILABILITY

VitalQIP Appliance Manager, 1.7 installation files are available for download via ALED (Alcatel-Lucent Electronic Delivery) services. ALED uses secure HTTP and FTP to download files and documentation. In order to use ALED, you must be registered with Alcatel-Lucent Global Support. If you are not registered with Alcatel-Lucent Global Support, visit https://market.alcatellucent.com/release/SPRegistrantTypeSvlt. If you need assistance in registering, contact the Alcatel-Lucent Customer Support Services at: Inside the United States: 1 (866) 582-3688, prompt 7 Outside the United States: 1 (630) 218-7688 You must have SSH installed and configured before downloading installation files. For more information about setting up secure FTP, visit https://download.support.alcatel-lucent.com/cgi-bin/ssh_ftp.cgi. After you have set up secure FTP, you can connect via secure FTP and access the Product|Version|Platform directory to download the products files. To download the product via secure HTTP, follow these steps: 1. If you have not registered, register at https://market.alcatellucent.com/release/SPRegistrantTypeSvlt. Open a browser and go to https://support.alcatel-lucent.com/portal/olcsHome.do. Log in with your user name and password. Click the Customer Center. Under Customer Support, click Documentation and downloads. On the Documentation and downloads page, click Product index. In the Alphabetical listing Products 1-999 page, click V. In the Alphabetical listing Product V page, click VitalQIP Appliance Manager (AM) for AM and click VitalQIP Software Appliance Manager for SAM.
P

2. 3. 4. 5. 6. 7. 8.

9.

Under Documentation and downloads, click Downloads: Electronic Delivery.

10. Select AM-<release number> for AM or SAM-<release number> for SAM. 11. Click Next. 12. Select the file to download and click Next. 13. Enter the download directory on your local machine and click Download.

1.1.3.

ORDERING DOCUMENTATION ONLINE

VitalQIP Appliance Manager Product documentation is available on the Alcatel-Lucent FTP Site. You can also order additional documentation online at https://support.alcatel-lucent.com/portal/olcsHome.do.
Page 4 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES 2. INSTALLATION REQUIREMENTS FOR AM RELEASE 1.7
Important! This section is not applicable to customers who have purchased the AMS 500, AMS 1000, or AMS 1200 Appliance since the Appliance Management Software has already been preloaded by the vendor.

2.1.

Supported Platforms

Table 1 VitalQIP Appliance Manager 1.7 Supported platforms

Platform Appliance Management Software Server Web Browser Web Server

Description/Comments Red Hat Enterprise Linux ES 5.x x86 platform Mozilla Firefox 3.x or higher Microsoft Internet Explorer 8.x Apache Tomcat 5.5.27. Apache Tomcat is included with AM.

Table 2 VitalQIP Appliance Manager 1.7 Hardware models

Model 500 Appliance type AMM 500 Remote Server VitalQIP Enterprise Server Management Station AMS 500 AMM 1000

Model 1000 ESM 1000 AMS 1000 AMM 1200

Model 1200 ESM 1200 AMS 1200

Model 5000 AMM 5000 ESM 5000

2.2. 2.2.1.

Third-party or other hardware/software requirements DNS HIGH AVAILABILITY

Alcatel-Lucent recommends running the DNS HA heartbeat over a crossover cable connecting the appliance pair. Customers who wish to run the DNS HA heartbeat between appliances located in different physical locations over a high-speed network connection will be supported as follows: If an AR (Assistance Request) is opened with Alcatel-Lucent Support, customers must clearly state whether they are running the DNS HA feature between locations. Support will make every effort to resolve the problem, however, issues related to the network latency will be attempted to be resolved on a best effort basis. If the problem persists, customers may also be asked to reproduce the problem on a co-located pair of appliances using a crossover cable.

Page 5 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

2.3. Software Requirements

The section lists the software requirements for VitalQIP Appliance Manager, Release 1.7. Please note if you are not currently running on the supported platform version, you are strongly encouraged to upgrade to the supported version.
Table 3 Software requirements

Platform Red Hat Enterprise Linux ES 5.x

Software Package MySQL

Version

Description/Comments

5.0.x

MySQL is included with RHEL 5.x.

2.4.

System Requirements

Table 4 System requirements

Component

Linux 1 GHz processor

VitalQIP Appliance Management Software Server

1 GB memory (minimum) 80 GB disk space (minimum)

2.5.

Pre-Installation Requirements

This section contains pre-installation requirements for VitalQIP Appliance Manager, Release 1.7. Refer to Chapter 1 of the VitalQIP Appliance Management Software Installation and Configuration Guide for information on system or database requirements and any preliminary steps that need to be taken before installing VitalQIP Appliance Management Software.

Page 6 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES 3. RELEASE DESCRIPTION

3.1. Features in VitalQIP Appliance Manager Release 1.7

The following table identifies the features and/or capabilities contained in this release.
Table 5 New features in Appliance Manager 1.7

Feature ID APP1.70100

Feature name QIP 7.3 package

Description This feature creates the appropriate appliance packages for all VitalQIP7.3 release modules. There is an upgrade facility available to upgrade from VitalQIP7.2PR3 Enterprise to VitalQIP7.3 Enterprise package. Existing data in the VitalQIP7.2 database is preserved for current appliance installations running in VitalQIP7.2PR3 Enterprise server. ENUM is now integrated with VitalQIP 7.3.

APP1.70200

Package Deployment Scheduling

This feature enables the user to schedule the package deployment either directly on the appliance or through appliance group from the AMS GUI. This helps the AMS GUI administrator to plan in advance and schedule the package deployment during off peak hours.

APP1.70400

AMS Controlled QIP export/import

The feature will allow authorized users to perform VitalQIP database export/import operations from the AMS web interface. This feature makes SNMP available on AMS

APP1.70500 APP1.70600

SNMP on AMS

Configuration of multiple syslog servers via AMS GUI (AR 12473083) Address AR related defects listed in the AMS defects tab File Transfer Capabilities

This enhancement will enable AMS GUI users to define up to a maximum of 10 remote logging servers for each individual appliance.

APP1.70700

AR related defects are resolved and updates are made available to customers.

APP1.7800

This feature allows files or directories to be transferred to/from appliances via the AMS. If it is a directory, then the content will be compressed into one file to optimize the data transfer.

Page 7 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Feature ID Feature name Description

APP1.70900

Console Package Import Utility

This console utility tool provides the capability to import the packages from the AMS console. User can use this utility if they have the package files in AMS machine and want to import the packages through the console instead of using the AMS GUI.

3.2.

Packages Included in Appliance Manager 1.7

The packages listed in the following table are included in Appliance Manager 1.7. Important! The system package removal does not undo the software changes.
Table 6 Appliance packages

Package amm-patch LDRM Server

Filename amm-patch2-2.1.5-2.x86_64.lpf ldrm-server-2.1.3-9.i386.lpf Note: This package is only compatible with vitalqip7.3-enterprise. ldrm-remote-2.1.3-9.i386.lpf

LDRM remote Note: This package is only compatible with vitalqip7.3-remote. amm-base-20090715-1.tar.bz2 Bootstrap bootstrap-20090603-6.x86_64.lpf jre-1.4.2-sun-1.4.2.16-1.i386.lpf JRE jre-1.5.0-sun-1.5.0.22-1.i386.lpf jre-1.6.0-sun-1.6.0.24-1.i386.lpf qddns-4.0.30-1.i386.lpf qddns-4.1.14-1.i386.lpf VitalQIP DNS qddns-4.2.19-1.i386.lpf qddns-5.0.14-1.i386.lpf qddns-5.1.15-1.x86_64.lpf DNS SNMP Anycast DNS VitalQIP DNS High Availability (on AMM appliances only) VitalQIP DNS user exits qddns-snmp-5.0.14-1.i386.lpf qddns-snmp-5.1.15-1.x86_64.lpf qddns-anycast-1.0.3-1.x86_64.lpf qddns-ha-1.0.5-1.x86_64.lpf Note: Get active Node and Force Switchover buttons on the Appliance Pair page are disabled for AMM1. They are enabled for AMM2 when HA is deployed. qddns-ha-2.0.7-1.x86_64.lpf qddns-userexits-1.0-3.i386.lpf
Page 8 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Package Filename qdhcp-5.4.45-1.i386.lpf qdhcp-5.5.9-1.i386.lpf VitalQIP DHCP qdhcp-5.6.18-1.i386.lpf Note: Lucent DHCP 5.6 is not supported on VitalQIP remote versions prior to VitalQIP 7.2 PR1, nor can it be deployed on AMM1 machines. qdhcp-6.0.11-1.i386.lpf DHCP SNMP VitalQIP DHCP user exits qdhcp-snmp-6.0.11-1.i386.lpf qdhcp-userexits-1.0-1.i386.lpf qip-snmp-2.2.1-9.i386.lpf VitalQIP SNMP qip-snmp-2.3.4-6.i386.lpf qip-snmp-2.3.5-2.i386.lpf Note: This package is only compatible with Lucent DHCP 5.6. snmp-server-1.0.1-1.x86_64.lpf SNMP Server snmp-server-2.0.2-1.x86_64.lpf Sybase Sybase 64 sybase64-15.5.0.2-5.x86_64.lpf System Patch System Patch2 Note: Refer to Appliance Packages Configuration Guide 1.7 for package rpms. ntp-server-1.0-5.x86_64.lpf NTP Server ntp-server-2.0-4.x86_64.lpf tftp-server-1.0-2.x86_64.lpf TFTP Server tftp-server-2.0-2.x86_64.lpf vitalqip7.1-enterprise-7.1.173-3.i386.lpf Note: This package is only compatible with an AMM1 appliance. VitalQIP Enterprise vitalqip7.2-enterprise-7.2.1708-1.i386.lpf vitalqip7.2-enterprise-7.2.592-4.i386.lpf vitalqip7.3-enterprise-7.3.147-1.i386.lpf vitalqip6-remote-6.2.53-1.i386.lpf vitalqip7-remote-7.0.520-4.i386.lpf vitalqip7.1-remote-7.1.173-1.i386.lpf VitalQIP Remote vitalqip7.2-remote-7.2.592-2.i386.lpf vitalqip7.2-remote-7.2.1708-1.i386.lpf vitalqip7.3-remote-7.3.147-1.i386.lpf AutoDiscovery ad-remote-2.3.5-4.i386.lpf system-patch-20090421-2.x86_64.lpf system-patch2-20110524-1.x86_64.lpf sybase-15.0.2.6-2.i386.lpf sybase64-15.0.2.6-6.x86_64.lpf

Page 9 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Package Filename ad-server-2.3.5-4.i386.lpf Note: This package is only compatible with vitalqip7.3-enterprise DHCP Configuration Manager VitalQIP DNS and DHCP Probe Dashboard qdhcp-manager-1.0.10-1.x86_64.lpf probe-server-1.0.2-1.i386.lpf probe-dns-1.0.3-1.noarch.lpf probe-dhcp-1.0.2-1.noarch.lpf dashboard-1.7.0-1.noarch.rpm

3.2.1.

THE SUPPORTED PLATFORM FOR PACKAGES

The supported platforms for the packages are listed in the following table.
Table 7 Platform for Packages

Package

AMM2 Platform (RHEL5.x) ad-remote-2.3.5-4.i386.lpf

AMM1 platform (RHEL4.x) ad-remote-2.3.5-4.i386.lpf Note: This package is only compatible with vitalqip7.3-enterprise ad-server-2.3.5-4.i386.lpf NA bootstrap-20090603-6.x86_64.lpf amm-base-20090715-1.tar.bz2.lpf jre-1.6.0-sun-1.6.0.04-1 jre-1.5.0-sun-1.5.0.14-1 jre-1.4.2-sun-1.4.2.16-1 NA

ad-remote ad-server amm-patch BOOT STRAP AMM BASE

Note: This package is only compatible with vitalqip7.3-enterprise ad-server-2.3.5-4.i386.lpf amm-patch2-2.1.5-2.x86_64.lpf NA NA jre-1.6.0-sun-1.6.0.24-1.i386.lpf

JRE

jre-1.5.0-sun-1.5.0.22-1.i386.lpf jre-1.4.2-sun-1.4.2.16-1.i386.lpf ldrm-server-2.1.3-9.i386.lpf

LDRM Server

Note: This package is only compatible with vitalqip7.3-enterprise. ldrm-remote-2.1.3-9.i386.lpf NA

LDRM remote NTP Server

Note: This package is only compatible with vitalqip7.3-remote. ntp-server-2.0-4.x86_64.lpf probe-dhcp-1.0.2-1.noarch.lpf ntp-server-1.0-5.x86_64.lpf NA

PROBE

probe-dns-1.0.3-1.noarch.lpf probe-server-1.0.2-1.i386.lpf qddns-5.1.15-1.x86_64.lpf qddns-5.0.14-1.i386.lpf qddns-4.1.14-1.i386.lpf qddns-4.2.19-1.i386.lpf qddns-anycast-1.0.3-1.x86_64.lpf

Page 10 of 29 ISSUE 8 November 2011 190-409-110R1.7

QDDNS

qddns-4.2.19-1.i386.lpf qddns-4.1.14-1.i386.lpf qddns-4.0.30-1.i386.lpf NA

QDDNS ANYCAST

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Package QDDNS HA QDDNS SNMP QDDNS User exits AMM2 Platform (RHEL5.x) qddns-ha-2.0.7-1.x86_64.lpf qddns-snmp-5.0.14-1.i386.lpf qddns-snmp-5.1.15-1.x86_64.lpf qddns-userexits-1.0-3.i386.lpf qdhcp-6.0.11-1.i386.lpf QDHCP qdhcp-5.6.18-1.i386.lpf qdhcp-5.5.9-1.i386.lpf qdhcp-5.4.45-1.i386.lpf QDHCP Manager QDHCP SNMP QDHCP User exits QIP-SNMP SNMP-Server Sybase Sybase64 System Patch System Patch2 TFTP qdhcp-manager-1.0.10-1.x86_64.lpf qdhcp-snmp-6.0.11-1.i386.lpf qdhcp-userexits-1.0-1.i386.lpf qip-snmp-2.3.5-2.i386.lpf qip-snmp-2.2.1-9.i386.lpf snmp-server-2.0.2-1.x86_64.lpf sybase-15.0.2.6-2.i386.lpf sybase64-15.5.0.2-5.x86_64.lpf sybase64-15.0.2.6-6.x86_64.lpf NA system-patch2-20110524-1.x86_64.lpf tftp-server-2.0-2.x86_64.lpf vitalqip7.2-remote-7.2.1708-1.i386.lpf vitalqip7.1-remote-7.1.173-1.i386.lpf Vital QIP remote vitalqip7-remote-7.0.520-4.i386.lpf vitalqip6-remote-6.2.53-1.i386.lpf vitalqip7.3-remote-7.3.147-1.i386.lpf vitalqip7.2-enterprise-7.2.17081.i386.lpf Vital QIP Enterprise vitalqip7.1-enterprise-7.1.173-3.i386.lpf vitalqip7.3-enterprise-7.3.147-1.i386.lpf vitalqip7.2-enterprise-7.2.592-4.i386.lpf vitalqip7.1-enterprise-7.1.173-3.i386.lpf system-patch-20090421-2.x86_64.lpf NA tftp-server-1.0-2.x86_64.lpf vitalqip7.2-remote-7.2.592-2.i386.lpf vitalqip7.1-remote-7.1.173-1.i386.lpf vitalqip7-remote-7.0.520-4.i386.lpf vitalqip6-remote-6.2.53-1.i386.lpf qdhcp-manager-1.0.10-1.x86_64.lpf NA qdhcp-userexits-1.0-1.i386.lpf qip-snmp-2.3.4-6.i386.lpf qip-snmp-2.2.1-9.i386.lpf snmp-server-1.0.1-1.x86_64.lpf sybase-15.0.2.6-2.i386.lpf sybase64-15.0.2.6-2.x86_64.lpf qdhcp-5.4.45-1.i386.lpf qddns-userexits-1.0-3.i386.lpf qdhcp-5.5.9-1.i386.lpf AMM1 platform (RHEL4.x) qddns-ha-1.0.5-1.x86_64.lpf NA

3.2.2.

ENTERPRISE PACKAGE FREQUENTLY ASKED QUESTION

Q: After I deployed VitalQIP Enterprise Package, qipd refuses to come up. A: The default .Lic file that is part of the Enterprise Package is empty. This is deployed on a new Enterprise Server install or with an ESM appliance. The file should be updated as a custom configuration file, as described in Activate license key on an ESM appliance, in the AMS Packages Configuration Guide. Note: In Appliance Manager 1.7, the existing .Lic file should be preserved after an upgrade if the Enterprise Package has already been deployed and is working.

Page 11 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

3.3. Resolved Issues

The following table identifies the customer reported issues that were resolved in Appliance Manager 1.7.
Table 8 Resolved issues in Appliance Manager 1.7

Fault ID HELIO00005917

AR ID 1-2455615

Severity 3: Medium

Description of issue Defect: Prerequisite needed for LDNS 4.2 and LDHCP 5.6 for SNMP 2.3 in AMS. Currently LDHCP 5.6 and LDNS 4.2 can be deployed with SNMP 2.2, but those versions are not compatible. Package Config Guide - The qddns section should include the session-key directive in step 7 for LDNS 5.1 There is " missing in the qddns package description section of the Appliance Packages Configuration Guide for AM1.7 AMM500 appliance stopped responding, had to reboot Vulnerability in AMS increase QIP user no files to 4096 at default or allow this to be configured via the AMS Cache issue in AMS GUI with mozilla browser Error received when stopping qip-tomcat from command line AMS: Appliance Add Error, when selecting a group on initial create Doc Defect - AMS Backup/restore procedure needs improvement named is not starting once the snmp status changes. Help configuraing AMS HTTPS User Synchronization does not work automatically with AMS Installer configuration. There is no documented way change the timezone on the AMM/ESM Step 3 in the AMS 1000 quick start guide to mention about connecting Mouse RFE: Establish Support Policy - Custom Appliance Packages Section Recover AMS database tells users to remove the AMS software, but doesn't tell them to install it again!

HELIO00018129

1-3242620

3: Medium

HELIO00018410

1-3336924

4: Low

HELIO00006122 HELIO00006053 HELIO00005995

1-2741545 1-2676282 1-2531190

2: High 3: Medium 3: Medium

HELIO00000512 HELIO00005853 HELIO00006063 1-2387947 1-2639407

3: Medium 3: Medium 3: Medium

HELIO00006025

1-2620024

3: Medium

HELIO00005952 HELIO00005888 HELIO00006132

1-2477256 1-2427945

3: Medium 3: Medium 3: Medium

HELIO00003423

3: Medium

HELIO00005999

1-2567663

3: Medium

HELIO00006284 HELIO00010056

3: Medium 1: Critical

HELIO00018018

1-3161177

3: Medium

Package Config Guide needs to be updated for qddns-ha 2.0.7 troubleshooting.

Page 12 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Fault ID HELIO00018029 AR ID 1-3194925 Severity 3: Medium Description of issue The Package Config Guide needs to be updated to reflect new procedures for SSL Configuration By default SSH V1 should be disabled by default. AMS Install guide is missing a few steps for first time backups of the ESM snmp-server-1.0-2 service does not start. Bug with IE 8 and AMS 1.5. AM 1.5 Upgrade failure. Authentication Callout: scheduleservice login failure. Any castd, ospfd restarted every week causes unavailability of DNS for about 5 minutes. Restore Package is not working in some cases. It is not validating the packages based on AMM Appliance version. File retrieval: Follow file functionality not working. Full install from AMS1.4 to AMS1.5 is not working. QIP License Extender: .Lic file goes out of sync with the AMS when the license extender feature is used to extend the license. Packages import fails if the user go back to other screen while the import is in progress Package Association: Unselect and select inside a modify session fails Slow unselection of checkbox when last ES service stops. Resizing the left pane hangs the AMS GUI only for IE. Anycastd, ospfd restarted every week Occasionally, could not stop HA heartbeat process from AMS GUI. Upgrade DNS HA package to the latest Linux-HA software (PaceMaker) ip_conntrack: table full, dropping packet messages and server unreachable messages logged

HELIO00000924 HELIO00001087

1-1934782 1-2113435

4: Low 3: Medium

HELIO00004930 HELIO00005862 HELIO00005882 HELIO00005886 HELIO00006006

1-2292723 1-2407921 1-2421073 1-2424984 1-2588040

2: High 4: Low 3: Medium 3: Medium 3: Medium

HELIO00005831

3: Medium

HELIO00005835 HELIO00005777 HELIO00000827

3: Medium 3: Medium 3: Medium

HELIO00000848

3: Medium

HELIO00001007

3: Medium

HELIO00001008 HELIO00001009 HELIO00006006 HELIO00002677 1-2588040

3: Medium 3: Medium 3: Medium 3: Medium

HELIO00005929

3: Medium

HELIO00001112/ HELIO00006142

1-2802421

3: Medium

Page 13 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

3.4. Known Issues

The following table includes a list of known issues that have been identified as customer impacting and/or outstanding customer problems that are not yet resolved.
Table 9 Known issues in AM 1.7

Defect Number HELIO00018088

AR Number

Abstract AMS file transfer: Alert should be displayed immediately if the file size exceeds max limit Export/Import: Schedule time and Schedule Export message displayed should be in same

Release Identified 1.7

Workaround (if applicable)

HELIO00018065

1.7

HELIO00018403

1-3318008

Unable to execute the CLI on the ESM box if we have a character next to any special character in the password field. AMS doens't accept appliances' names starting with digits AMS does not clean up incomplete status checks against named. Bootstrap process disables console account. ktutil command missing in the VitalQIP AMM2.0 OS.

1.6

use single quotes. Example: 'C0pperc0!n'

HELIO00006136

1-2767854

1.5

HELIO00006007

1-2593092

1.5

HELIO00006015 HELIO00006016

1-2541345 1-2600252

1.5 1.5 Windows export via ktpass.exe can be done in a way to include all necessary keys in one keytab. Just upload the keytab to AMS and deploy that (rather than merging keys in new and existing keytab files with ktutil) or use ktutil on the AMS or other machine.

HELIO00006075

1-2710733

AMM1000 does not AUTO authenticate after upgrade to RHEL5 (AMM2). Appliance group: Packages not displayed in red when undeploy failed. qip-cached process of 7.2 PR1 remote package not getting killed on downgrade.

1.5

HELIO00005803

1.5

HELIO00005815

1.5

Follow these steps: 1. Stop the cached service from the AMS GUI before downgrading. 2. Log in to the console as root or qip user and kill the process.

Page 14 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Defect Number HELIO0005839 AR Number Abstract A configured syslog host may cause an error during the upgrade process. This appears to be dependent on hardware with NIC reordering during an upgrade. The error happens late during the upgrade process. Despite this error, the upgrade completes successfully. HELIO00000978 Appliance lost gateway with Secondary Interface configuration. 1-2019869 Upgrading to AMS 1.3 B10 did not create new ams.properties file Package color incorrect after group deployment. Tomcat process cannot be killed from GUI. send mail utility not available on appliance (VitalQIP thick client will not be able to send email. Currently works only with web client.) Config file changes to HA from AMS fails to start HA Service after file push. 1.4 Reconfigure gateway on appliance. Release Identified 1.5 Workaround (if applicable) Unconfigure the syslog host before installing the bootstrap package.

HELIO00000950

1.3

HELIO00000986 HELIO00000858 HELIO00000807

1-2032809

1.3 1.3 1.3

HELIO00000729

1.3

User needs to pick up Config files to edit from earlier deployed history. Do not use Config files for editing from Appliance>Packages> Configure packages>next deployment.

HELIO00000630 VQIP00022431

SNMP daemon restarted during deployment. DHCP push fails in PR5 with PR4 scopes ( created via web with DHCP server Same as subnet profile). Cannot add maintainers in 7.1PR5.

1.1 7.1 PR5

Deploy a configuration file in another package. Refer to the Post-installation tasks section in the VitalQIP 7.1 PR5 Release Notes. Refer to the Post-installation tasks section in the VitalQIP 7.1 PR5 Release Notes.

VQIP00022455

7.1 PR5

3.4.1.

SSL CONFIGURATION LIMITATION FOR ENTERPRISE APPLIANCE

If you configure the qip.pcy file to use SSL, there can be only one key in qipkeystore. Use the keytool command to see the number of keys in qipkeystore. For example:
$/opt/jre-1.6.0-sun/bin/keytool list keystore /opt/qip/qipkeystore
Page 15 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

4. SOFTWARE APPLIANCE MANAGER RELEASE 1.7

4.1. Software Appliance Manager

The VitalQIP Software Appliance Manager (SAM) comprises a set of software images that replicate the software functionality that is included in the VitalQIP Appliance Manager (AM) Release 1.7 product line and makes the functionality available on hardware platforms other than the existing VitalQIP appliance platforms. This allows customers to install and utilize the market leading VitalQIP Appliance Manager (AM) software and services on their own preferred hardware. The hardware platforms that are supported by VitalQIP Software Appliance Manager (SAM), in general, must be compatible with the hardware and device drivers used in the VitalQIP Appliance Manager (AM) hardware appliances. This encompasses a wide-variety of platforms certified with Red Hat Enterprise Linux Release 5 (RHEL5). Please see the section below on Supported Platforms for additional details. There are many advantages to the VitalQIP Software Appliance Manager (SAM) approach, including the ability to run the complete set of VitalQIP IP Address Management (IPAM), DNS/DHCP and Appliance Management Software (AMS) on a customer-preferred set of hardware platforms. This can significantly reduce overall hardware, maintenance and support costs, while improving the reliability of network operations. The VitalQIP Software Appliance Manager (SAM) product line is comprised of the following software image components: VitalQIP Appliance Manager Software (AMS) 1.7 ISO image. This is a disk image of the AMS software that is used to manage VitalQIP appliances. VitalQIP Appliance Manager Module (AMM) 1.7 ISO image. This is a disk image of the base software used in the VitalQIP Appliance Manager Module (AMM) appliances. VitalQIP Appliance Manager Module (ESM) 1.7 ISO image. This is a disk image of the base software used in the VitalQIP Enterprise Server Module (ESM) appliances. Note: ISO is a disk image standard developed by the International Organization for

Standardization.
The ISO images can be burned onto CD/DVD and used at boot time to initialize the hardware platforms, used during a network boot of the machines, etc. Once the platforms are successfully booted from the ISO image, the complete set of VitalQIP Appliance Manager (AM) software packages and services are available on the customer-preferred hardware.

4.2.

Licensing for SAM

VitalQIP Software Appliance Manager (SAM) utilizes the standard VitalQIP licensing mechanism. The VitalQIP Enterprise Server requires a license that specifies how many IP objects can be managed. In addition, the VitalQIP Appliance Management Software (AMS) requires a license that specifies how many appliances can be supported. VitalQIP Support provides both licenses.
Page 16 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

4.3. Supported Platforms

VitalQIP Software Appliance Manager (SAM) software runs on a security-hardened version of the Red Hat Enterprise Linux Release 5 (RHEL5) 64-bit (x86_64) operating system. A wide variety of device drivers are supported in the disk image. However, a large number of drivers have been eliminated due to security concerns. The device drivers will largely dictate which hardware platforms can support the VitalQIP Software Appliance Manager (SAM) images. Besides device drivers, there are other hardware considerations the dictate whether or not the ISO disk images will run on the hardware: CPU, Motherboard, Disk, Memory, Video, etc. Due to the magnitude of all possible combinations, versions, and manufacturers of these devices, it is impossible to provide a list in these notes. The best place to start to determine whether a particular hardware platform is supported is to examine the Red Hat Certified Hardware list (https://hardware.redhat.com/). Search for the hardware in question and see if it is certified for RHEL 5.3 x86_64 or greater. If the hardware is not in the list, this does not necessarily preclude the hardware from being a supported hardware platform. Consult with Alcatel-Lucent and arrange for a test of the ISO disk images on the particular hardware. When a hardware platform is first being evaluated and tested to determine whether it supports the VitalQIP Software Appliance Manager (SAM) ISO images, Alcatel-Lucent will work with the customer to ensure that the basic operations of the appliances and VitalQIP are supported properly. It is recommended that the hardware is either shipped to Alcatel-Lucent to be evaluated and certified, or a connection established to the customer location so that Alcatel-Lucent personnel can log into the systems and evaluate the configuration. The table below contains the current list of certified hardware:
Table 10 VitalQIP Software Appliance Manager (SAM) 1.7 Supported platforms

Platform Intel TIGW1U Intel S3200SH Intel 945 HP DL180 G6 HP BL460c G6 HP DL3x0 G6 HP ProLiant ML110 G6 Dell SC1435 Dell PowerEdge R210 IBM System x3650 HP Compaq DC7800

Description/Comments Intel Carrier-Grade, NEBS-Compliant server (utilized by the VitalQIP Model 5000 Appliance) Intel Enterprise-Grade server (utilized by the VitalQIP Model 1000 Appliance) Intel Small-Office/Retail server (utilized by the VitalQIP Model 500 Appliance) HP ProLiant Enterprise-Grade server HP Blade Server. HP 1U Enterprise Business Server HP Small Business Server Dell Low-end Rack Server for small businesses Dell 1U Rack Server IBM 2U Virtualization Server HP Small Form Factor PC

Page 17 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

4.4. Hardware Support Policy

If the VitalQIP Software Appliance Manager (SAM) images load successfully on hardware without any device driver or other conflicts and the VitalQIP Appliance Manager (AM) functionality performs without problems, Alcatel-Lucent will consider the hardware for certification of the VitalQIP Appliance Manager (AM) software. This means that the VitalQIP Appliance Manager (AM) software is supported once the hardware platform is certified. If a problem occurs and there is a question as to whether the problem is hardware or software-related, Alcatel-Lucent reserves the right to request that the software be loaded and the problem reproduced on a standard Alcatel-Lucent VitalQIP appliance to isolate the problem. VitalQIP Support will make every effort to resolve the problem. However, respond-only objectives will apply if the issue is determined to be hardware-related.

Page 18 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES 5. DOCUMENTATION

The following table lists the manuals that comprise the documentation set for VitalQIP Appliance Manager, 1.7.
Table 11 AM1.7 Documentation deliverables

Guide VitalQIP AMM 500 Quick Start Guide

Part Number 190-409-120

Description This guide describes how to set up the AMM 500 appliance. This guide describes how to set up the AMM 1000 appliance. This guide describes how to set up the AMM 1200 appliance. This guide describes how to set up the AMM 5000 appliance. This guide describes how to set up the ESM 1000 appliance. This guide describes how to set up the ESM 1200 appliance. This guide describes how to set up the ESM 5000 appliance. This guide describes how to set up the AMS 500 appliance. This guide describes how to set up the AMS 1000 appliance This guide describes how to set up the AMS 1200 appliance. This guide describes how to use the VitalQIP Appliance Management Software (AMS). This guide describes how to install and configure the VitalQIP Appliance Management Software (AMS). This guide describes the appliance packages and how to configure them. These release notes describe the new features, resolved issues, known issues, and upgrade instructions for VitalQIP Appliance Manager.

VitalQIP AMM 1000 Quick Start 190-409-088 Guide VitalQIP AMM 1200 Quick Start 190-409-131 Guide VitalQIP AMM 5000 Quick Start 190-409-117 Guide VitalQIP ESM 1000 Quick Start Guide VitalQIP ESM 1200 Quick Start Guide VitalQIP ESM 5000 Quick Start Guide VitalQIP AMS 500 Quick Start Guide VitalQIP AMS 1000 Quick Start Guide VitalQIP AMS 1200 Quick Start Guide 190-409-118 190-409-133 190-409-119 190-409-121 190-409-093 190-409-132

VitalQIP Appliance Management 190-409-089 Software Users Guide VitalQIP Appliance Management 190-409-094 Software Installation and Configuration Guide VitalQIP Appliance Management 190-409-116 Software Appliance Packages Configuration Guide VitalQIP Appliance Manager Release Notes 190-409-110

Page 19 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

6. INSTALLING VITALQIP APPLIANCE MANAGER

The following sections include information on installing VitalQIP Appliance Manager.

6.1.

Obtaining Installation Files

Installation files are available by ALED. Before installing any additional products, contact your sales representative to obtain a license key AMS and ESM products. If you encounter problems during the installation, contact technical support for assistance: For North America customers: 1-866-LUCENT8 (582-3688), Option 1, then Option 2 For Europe, Middle East and Africa: 00 800 00 LUCENT or +353 1 692 4579 For Central and South America support: o Brazil: 0800 89 19325 or +55 11 3205 7626

Important! For other local CALA numbers, consult the web site http://www.alcatellucent.com/support or contact your local sales representative. For Asia Pacific technical support: o o o 1800-458-236 (toll free from within Australia) (IDD) 800-5823-6888 (toll free from Asia Pacific China, Hong Kong, Indonesia, South Korea, Malaysia, New Zealand, Philippines, Singapore, Taiwan, and Thailand) (613) 9614-8530 (toll call from any country)

6.1.1.

INSTALLATION FILES BY ALED

6.1.1.1. For Appliance Manager

VitalQIP Appliance Manager 1.7 installation files are available on the ALED site. Please contact technical support for more information on obtaining the installation files. If you obtain your installation files from the ALED site, follow these steps to begin the installation: 1. Access the installation directory and run the following Linux command: ./amsSetupLinux-1.7B15.bin 2. Follow the installation directions provided in the VitalQIP Appliance Management Software Installation & Configuration Guide. 6.1.1.2. For Software Appliance Manager

VitalQIP Software Appliance Manager (SAM) 1.7 disk image files are available on the ALED site. Contact Technical Support for more information on obtaining the installation files.

Page 20 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

6.2.

Upgrading AMS on RHEL4 to AMS 1.6

AMS 1.6 is not supported on RHEL4. All RHEL4 based AMS must be upgraded to RHEL5. For upgrade procedure, refer to the section "Upgrading from AMS 1.4 or 1.5 on RHEL 4.0 to AMS 1.6" of VitalQIP Appliance Manager Installation & Configuration Guide. Alcatel-Lucent provides all customers who have purchased RHEL4-based AMS appliances with a USB stick with a RHEL5-based AMS 1.6 upgrade. Please contact VitalQIP Support for instructions. Data from the previous AMS releases can be imported into AMS 1.6. For more information, refer to the section "AMS database migration" of VitalQIP Appliance Manager Installation & Configuration Guide.

6.3.

Upgrading an Appliance

This section describes the recommended steps to upgrade an AMM1-based appliance that runs on Red Hat Linux 4 (VitalQIP AM Release 1.4 and earlier) to an AMM2-based appliance that runs on Red Hat Linux 5 (VitalQIP AM Release 1.7 and above). The process is as follows. 1. 2. 3. 4. 5. Download AM 1.7 content from the Alcatel-Lucent Electronic Distribution site (ALED). Upgrade AMS to AM 1.7 Enable Autoconfig Upgrade ESM to AM 1.7 Upgrade AMMs to AM 1.7

Before beginning the upgrade, thoroughly review the following documents: AM 1.7 Release Notes (this document) Appliance Manager Installation and Configuration Guide Appliance Packages Configuration Guide (in particular, the Bootstrap section)

Contact VitalQIP Technical Support for upgrade assistance, or if you have any questions.

6.3.1.

DOWNLOAD AM 1.7 CONTENT FROM ALED

To download Appliance Manager 1.7 content, follow these steps. 1. 2. 3. Log into http://support.alcatel-lucent.com. Go to the VitalQIP Appliance Manager product area and select AM1.7. Download AMM1.7, AMS1.7 and Docs:
Page 21 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

Under AMM1.7, the EnterprisePackages and RemotePackages are complete zip files of all necessary Enterprise and Remote packages respectively. (EnterprisePackages are only needed if ESM appliances are deployed; RemotePackages are only needed if AMM appliances are deployed.) The Packages area allows individual packages to be selected. Under AMS1.7, select amsSetupLinux-1.7B15.bin if you plan to upgrade your existing AMS environment. Under Docs, download the AMR1.7Docs zip file and the AMR1.7ReleaseNotes.

6.3.2.

UPGRADE AMS

AMS 1.7 can run only on RHEL5-based AMS appliances and servers. To upgrade an AMS machine, follow these steps. 1. Follow the instructions in the Appliance Manager Installation and Configuration Guide for upgrading the AMS machine. (Ensure you back up the MySQL database and repo package directory.) To upgrade AMS, execute the latest AMS 1.7 installation file (amsSetupLinux-1.7B15..bin). This can be done on an AMS Appliance, or AMS Server. Install the bootstrap base image on the AMS machine (per the instructions in the Appliance Packages Configuration Guide): 4. Create the $AMSHOME/download directory if it does not exist Copy amm-base-yyyymmdd-X.tar.bz2 to $AMSHOME/download/amm-base.tar.bz2 Rename the file (or link it) to amm-base.tar.bz2

2.

3.

Make sure you clear your browser cache when you access the AMS 1.7 GUI (to ensure you are accessing the latest AMS functionality). Once installation is complete, follow these steps: Import new AM 1.7 packages into AMS (using the Import Package action on the Packages screen). Exercise AMS operations to ensure your appliance environment is operating correctly.

5.

Note: AMS 1.7 supports ESM/AMM 1.3, 1.4, 1.5, 1.6 and 1.7 appliances. Data from the previous AMS releases can be imported into AMS 1.7. For more information, refer to the section "AMS database migration" of VitalQIP Appliance Manager Installation &

Configuration Guide.
You can also install AMS 1.7 on a RHEL5 Server and then import the MySQL database and packages in the repo directory from the AMS 1.4 and 1.5 environment.

6.3.3.

ENABLE AUTOCONFIG

Before an ESM or AMM appliance is upgraded, the AutoConfig option must be enabled on the appliance. You can either enable autoconfiguration directly on the appliance or remove the console account.
Page 22 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

For more information on appliance configuration, refer to Part II of the Appliance Manager Installation & Configuration Guide. 6.3.3.1. Method 1: Enable AutoConfig on appliance To enable AutoConfig directly on an appliance that is being upgraded, follow these steps: 1. 2. 3. 4. 5. Access the Console Menu, and type enable to enter privileged mode. In privileged mode, type config. In configuration mode, type autoconfig. At the Enable autoconfig prompt, type yes. Type show to check that autoconfigure is set. The following response is displayed: autoconfig: enabled 6.3.3.2. Method 2: Remove console account in AMS To ensure AutoConfig is enabled, set a console password and then remove it. Follow these steps: 1. 2. 3. Select the appliance in AMS. Click Console Account. Click Modify, set a password and click Submit.

Note: This step is mandatory, regardless of whether the password was set previously. 4. 5. Click Console Account again. Click Remove Password.

6.3.4.

UPGRADE THE ESM APPLIANCE

To upgrade the ESM appliance, follow these steps: 1. Export the VitalQIP database from the ESM appliance: Log onto the ESM appliance and use the exportdb.sh CLI command to export the existing database. Copy the resulting qef files to another machine (for example, AMS).

2.

Although ESM configuration files are preserved in AMS configuration history, Alcatel-Lucent recommends that you make an extra backup on the AMS machine of important ESM configuration files (such as .Lic and qip.pcy), and any custom files. These configuration files are deleted on the ESM appliance after it is upgraded and a Query (see step 8 below) is executed. Also make a note of the current packages deployed on the ESM appliance. Enable the ammuser user account on the ESM appliance in case you need to log in.
Page 23 of 29 ISSUE 8 November 2011 190-409-110R1.7

3.

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

4. Associate the bootstrap package with the ESM appliance. The bootstrap package should be deployed without any other packages, or with only a minimal set of packages, such as a system-patch package. After creating the association, click Deploy. The deployment of the bootstrap package is quick. Once deployed, the bootstrap is executed the next time the ESM appliance is rebooted. 5. Reboot the ESM appliance (click Reboot on the ESM appliance Properties page). Note: The reboot takes approximately half an hour. When the ESM appliance is rebooted, the bootstrap base image is copied from AMS and is used to boot the appliance. The base image reformats the disk and lays down a new security-hardened RHEL5 image on the appliance, along with base AM 1.7 software. (Note that previous versions used RHEL4.) The ESM appliance retains its network configuration so that it can communicate with AMS. 6. Wait for the ESM appliance to reboot. You can periodically click Verify Communication on the Properties page to determine when it is up. After the reboot, the Appliance Version field on the Properties page should display 2.0. Note: If the version has not updated, click Get Version. 7. Once the ESM appliance has re-established communication with AMS, disassociate the bootstrap package from the ESM appliance. In AMS, select the ESM appliance Configuration History tab and click Query. AMS resets the package associations with the ESM appliance. Note: If communication is not re-established or you receive an error while querying the ESM appliance, try to ssh into the appliance and reboot the machine (log in as ammuser, su to root and enter reboot). If this does not work, contact VitalQIP Support. 9. If the reboot is successful, click on the Packages tab and select the desired packages (for example, Sybase64, VitalQIP 7.2 Enterprise, and so on). Click Deploy.

8.

10. Once the ESM packages have been deployed, configure the ESM appliance .Lic, qip.pcy and other configuration files (using the files backed up in step 2 above or the AMS configuration history roll back feature) and deploy. 11. Secure copy the export (qef) files to the ESM appliance and import them using the importdb.sh CLI command. 12. Verify that the ESM appliance can push to the remote DNS/DHCP servers/appliances. 13. Test the environment until you are confident that the upgrade was successful.

6.3.5.

UPGRADE AMM APPLIANCES

To upgrade your AMM remote appliances (running DNS, DHCP, and so on) to AM 1.7, follow these steps.

Page 24 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

1. Although AMM configuration files are preserved in AMS configuration history, Alcatel-Lucent recommends that you make an extra backup on the AMS machine of important AMM configuration files (such as qip.pcy), and any custom files. These configuration files are deleted on the AMM appliance after it is upgraded and a Query (see step 8 below) is executed. Also make a note of the current packages deployed on the AMM appliance. Enable the ammuser user account on the AMM appliance in case you need to log in. Associate the bootstrap package with the AMM appliance. The bootstrap package should be deployed without any other packages, or with only a minimal set of packages, such as a system-patch package. After creating the association, click Deploy. The deployment of the bootstrap package is quick. Once deployed, the bootstrap is executed the next time the AMM appliance is rebooted. 4. Reboot the AMM appliance (click Reboot on the AMM appliance Properties page): Note: The reboot takes approximately half an hour. 5. When the AMM appliance is rebooted, the bootstrap base image is copied from AMS and is used to boot the appliance. The base image reformats the disk and lays down a new security-hardened RHEL5 image on the appliance, along with base AM 1.7 software. (Note that previous versions used RHEL4.) The AMM appliance retains its network configuration so it can communicate with AMS. Wait for the AMM appliance to reboot. You can periodically click Verify Communication on the Properties page to determine when it is up. After the reboot, the Appliance Version field on the Properties page should display 2.0. Note: If the version has not updated, click Get Version. 7. Once the AMM appliance has re-established communication with AMS, disassociate the bootstrap package from the AMM appliance. In AMS, select the AMM appliance Configuration History tab and click Query. AMS resets the package associations with the AMM appliance. Note: If communication is not re-established or you receive an error while querying the AMM appliance, try to ssh into the appliance and reboot the machine (log in as ammuser, su to root and enter reboot). If this does not work, contact VitalQIP Support. 9. If the reboot is successful, click on the Packages tab and select the desired packages (for example, JRE, VitalQIP 7.2 Remote, DNS/DHCP, and so on). Click Deploy.

2. 3.

6.

8.

10. Once the AMM packages have been deployed, configure the AMM qip.pcy and other configuration files (using the files backed up in step 1 above or the AMS configuration history roll back feature) and deploy. 11. Verify that the Enterprise Server (for example, ESM) can push the DNS/DHCP configuration files to the AMM appliance. 12. Test the environment until you are confident that the upgrade was successful.
Page 25 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

6.4. Service Packages directory structure

Packaged LPF files are posted in a directory structure in which each major revision of AMS has a top-level directory that contains both a server directory and a packages directory. The server directory contains InstallShield executables, whereas the packages directory contains LPF packages that are placed in directories based upon the package name. This directory may contain multiple versions of a package. For example:

AM1.7 AMM1.7
Packages AD ad-remote ad-remote-2.3.5-4.i386 ad-server ad-server-2.3.5-4.i386 amm-patch amm-patch2-2.1.5-2.x86_64

BOOTSTRAP bootstrap-20090603-6.x86_64 amm-base-20090715-1.tar.bz2 LDRM Server ldrm-server-2.1.3-9.i386 LDRM remote ldrm-remote-2.1.3-9.i386 JRE jre-1.4.2-sun-1.4.2.16-1.i386 jre-1.5.0-sun-1.5.0.22-1.i386 jre-1.6.0-sun-1.6.0.24-1.i386 QDDNS qddns qddns-4.0.30-1.i386 qddns-4.1.14-1.i386 qddns-4.2.19-1.i386 qddns-5.0.14-1.i386 qddns-5.1.15-1.x86_64 qddns-snmp qddns-snmp-5.0.14-1.i386 qddns-snmp-5.1.15-1.x86_64 qddns-ha AMM1 qddns-ha-1.0.5-1.x86_64 AMM2 qddns-ha-2.0.7-1.x86_64 qddns-userexits
Page 26 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

qddns-userexits-1.0-3.i386 qddns-anycast qddns-anycast-1.0.3-1.x86_64 QDHCP qdhcp qdhcp-5.4.45-1.i386 qdhcp-5.5.9-1.i386 qdhcp-5.6.18-1.i386 qdhcp-6.0.11-1.i386 qdhcp-snmp qdhcp-snmp-6.0.11-1.i386 qdhcp-userexits qdhcp-userexits-1.0-1.i386 snmp-server AMM1 snmp-server-1.0.1-1.x86_64 AMM2 snmp-server-2.0.2-1.x86_64 qip-snmp qip-snmp-2.2.1-9.i386 qip-snmp-2.3.4-6.i386 qip-snmp-2.3.5-2.i386 Sybase sybase-15.0.2.6-2.i386 Sybase64 sybase64-15.5.0.2-5.x86_64 sybase64-15.0.2.6-6.x86_64 System Patch system-patch-20090421-2.x86_64 system-patch2 system-patch2-20110524-1.x86_64 NTP ntp-server AMM2 ntp-server-2.0-4.x86_64 AMM1 ntp-server-1.0-5.x86_64 TFTP tftp-server AMM2 tftp-server-2.0-2.x86_64 AMM1 tftp-server-1.0-2.x86_64
Page 27 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES

vitalqip6.2-remote vitalqip6-remote-6.2.53-1.i386 vitalqip7-remote vitalqip7-remote-7.0.520-4.i386 vitalqip7.1-enterprise vitalqip7.1-enterprise-7.1.173-3.i386 vitalqip7.1-remote vitalqip7.1-remote-7.1.173-1.i386 vitalqip7.2-remote vitalqip7.2-remote-7.2.1708-1.i386 vitalqip7.2-remote-7.2.592-2.i386 vitalqip7.2-enterprise vitalqip7.2-enterprise-7.2.592-4.i386 vitalqip7.2-enterprise-7.2.1708-1.i386 vitalqip7.3-remote vitalqip7.3-remote-7.3.147-1.i386 vitalqip7.3-enterprise vitalqip7.3-enterprise-7.3.147-1.i386 QDHCP-Manager qdhcp-manager-1.0.10-1.x86_64 DNS-DHCP Probe probe-server-1.0.2-1.i386 probe-dns-1.0.3-1.noarch probe-dhcp-1.0.2-1.noarch EnterprisePackages enterprisepackages.zip RemotePackages remotepackages.zip

AMS1.7
amsSetupLinux-1.7B15.bin Dashboard dashboard-1.7.0-1.noarch.rpm ISOs ams-20110511.iso amm2-20110524.iso esm-20110526.iso Docs AM1.7Docs

Page 28 of 29 ISSUE 8 November 2011 190-409-110R1.7

VITALQIP APPLIANCE MANAGER 1.7 RELEASE NOTES 7. SUPPORTING INFORMATION

7.1.
ACL AD ALED AM AMM AMM1 AMM2 AMS AR DNS DHCP ESM HA iBGP IPMI ISO OSPF RFC SNMP SP SSH TFTP

Glossary- Acronyms and Definitions

Acronym for Access Control List Acronym for AutoDiscovery Acronym for Alcatel-Lucent Electronic Delivery Acronym for Appliance Manager Acronym for Appliance Management Module Acronym for Appliance Management Module running on Red Hat Linux 4 Acronym for Appliance Management Module running on Red Hat Linux 5 Acronym for Appliance Management Software Acronym for Assistance Request Acronym for Domain Name Service Acronym for Dynamic Host Configuration Protocol Acronym for Enterprise Server Module Acronym for High Availability Acronym for internal Border Gateway Protocol Acronym for Intelligent Platform Management Interface International Organization for Standardization Acronym for Open Shortest Path First Acronym for Request for Comment Acronym for Simple Network Management Protocol Acronym for Service Pack Acronym for Secure Shell Protocol Acronym for Trivial File Transfer Protocol

Page 29 of 29 ISSUE 8 November 2011 190-409-110R1.7