SPECTRUM In-Place Upgrades

Transcription

1

2 Notice Copyright Notice Copyright present by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ( Aprisma ) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to: All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III(g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virus-free. Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100-percent effective, we strongly recommend that you write protect the licensed software and verify (with an antivirus system with which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc., 273 Corporate Drive, Portsmouth, NH USA Phone: U.S. toll-free: Web site: Page 2

3 Contents Notice... 2 Preface... 4 Intended Audience... 4 Text Conventions... 4 Document Feedback... 5 Online Documents... 5 Introduction... 6 The Upgrade Process... 7 Prerequisites... 7 Preparation... 8 SpectroWATCH... 8 Web Operator Suite... 9 In-Place Upgrade with a Distributed SpectroSERVER Deployment (No Fault Tolerance)... 9 In-Place Upgrade with a Distributed SpectroSERVER Environment and Fault Tolerance Deployment...12 Using SPECTRUM Version 6.6 Distributed Install (SDI) Functionality Index Page 3

4 Preface In This Section Intended Audience [page 4] Text Conventions [page 4] Document Feedback [page 5] Online Documents [page 5] Intended Audience This guide is intended for system administrators who are installing and upgrade of SPECTRUM on a Windows or Solaris platform. Text Conventions The following text conventions are used in this document: Element Convention Used Example Variables (The user supplies a value for the variable.) The directory where you installed SPECTRUM (The user supplies a value for the variable.) Courier and Italic in angle brackets (<>) <$SPECROOT> Type the following: DISPLAY=<workstation name>:0.0 export display Navigate to: <$SPECROOT>/app-defaults Solaris and Windows directory paths Unless otherwise noted, directory paths are common to both operating systems, with the exception that slashes (/) should be used in Solaris paths, and backslashes (\) should be used in Windows paths. <$SPECROOT>/app-defaults on Solaris is equivalent to <$SPECROOT>\app-defaults on Windows. On-screen text Courier The following line displays: path= /audit User-typed text Courier Type the following path name: C:\ABC\lib\db Page 4

5 Element Convention Used Example Cross-references References to SPECTRUM documents (title and number) Underlined and hypertextblue Italic See Document Feedback [page 5]. SPECTRUM Installation Guide (0675) Document Feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Page 5

6 Introduction In a large distributed and fault tolerant SPECTRUM environment, the task of upgrading to a new version of SPECTRUM can seem overwhelming. Often times, upgrades must be scheduled, resources located, and network management downtime factored in. However, with a little planning and minimal additional resources, this task can be conducted with minimum loss of network management visibility throughout the upgrade process. The purpose of this guide is to assist the SPECTRUM Administrator with proper planning, required resources, and upgrade techniques before the actual upgrade is performed. Different methods of upgrading SPECTRUM exist, some of which can require many additional machines and/or loss of network management during the upgrade. However, the recommended method for an in-place upgrade without sacrificing network management is conducted using a swing machine. The swing machine is configured as a secondary (fault tolerant) SpectroSERVER and is used to retain network management while SPECTRUM is being upgraded. This eliminates the need to setup, install, and configure many SPECTRUM machines prior to the production environment being upgraded. In addition, since only one SpectroSERVER is upgraded at a time, problems or issues can be resolved before moving on to the next SpectroSERVER. Full details for completing this process are described in this guide. Page 6

7 The Upgrade Process In This Section Prerequisites [page 7] Preparation [page 8] In-Place Upgrade with a Distributed SpectroSERVER Deployment (No Fault Tolerance) [page 9] In-Place Upgrade with a Distributed SpectroSERVER Environment and Fault Tolerance Deployment [page 12] Prerequisites To conduct a SPECTRUM in-place upgrade in a distributed, non-fault tolerant environment without losing network management during the process, a few additional resources are required: 1. If you have a Windows SpectroSERVER install base, you will need one extra Windows workstation configured similarly to one of your production SpectroSERVER machines. If you have a Solaris SpectroSERVER install base, you will need one extra Solaris workstation configured similarly to one of your production SPECTRUM machines. If your install base is mixed with Windows and Solaris SpectroSERVER's, you will need one extra of each, both configured similarly to your production SpectroSERVER machines. Aprisma recommends that any secondary, fault tolerant SpectroSERVER machine must match the operating system of the primary. 2. The swing machine(s) must meet all prerequisites outlined in the Spectrum Installation Guide (0675). See Solaris Prerequisites and Windows Prerequisites in the Spectrum Installation Guide (0675) for more information. 3. Additional SPECTRUM license(s) are needed for the swing machine(s). If your install base is all Windows or all Solaris, you will only need one extra license. If your SPECTRUM environment consists of mixed SpectroSERVER's (Windows & Solaris), you will need two extra licenses; one for each operating system. A lab license could be used in these cases. For futher information on pricing and availablity for lab licenses, contact your Aprisma sales representative. Any machine Page 7

8 configured as a swing machine must be the same platform (Solaris or Windows) as the primary. 4. Before conducting any upgrades, ensure all SPECTRUM installations are up-to-date with current patch requirements. For example: a. Upgrading from requires patch b. Upgrading from 6.5 requires patches and c. Upgrading from requires patch or Note: Go to for the latest patch information. To conduct a SPECTRUM in-place upgrade in a distributed and fault tolerant environment without losing network management during the process, the additional swing machine will not be required. However, fault tolerance will be temporarily disabled during the upgrade process, as a secondary SpectroSERVER will substitute as the swing machine. Ensure the required patches are installed prior to beginning the in-place upgrade(s) [see step 4]. Preparation You will need to take additional measures to prepare for the upgrade if you are using SpectroWATCH or the Web Operator Suite. SpectroWATCH Create a SpectroWATCH report on each SpectroSERVER to be upgraded. This will generate a record of all SpectroWATCHES configured on each SpectroSERVER. When upgrading SPECTRUM and SpectroWATCHES, be aware of the following: 1. Default SpectroWATCHES that have been edited will not survive an upgrade; only new (custom) SpectroWATCHES will be migrated. If your SpectroSERVER contains default SpectroWATCHES that have been edited, create new SpectroWATCHES based on the edited default SpectroWATCHES before upgrading. 2. Any default SpectroWATCH that was turned off will be turned back on after the upgrade. After completing the upgrade, be sure to go back and ensure that only SpectroWATCHES you care about are turned on. The less SpectroWATCHES you have running, the better performing SpectroSERVER you will have. Page 8

9 Web Operator Suite If Web Operator Suite is deployed in your environment, be sure to edit the.localregfile in the WOS install area and add the secondary Location Server host name. This host name will be the name of the secondary (fault tolerant) SpectroSERVER machine; perhaps the swing machine. Restart the Spectrum Tomcat service to update these changes. This will allow WOS to preserve contact with SPECTRUM when the primary SpectroSERVER is disabled during the upgrade. In-Place Upgrade with a Distributed SpectroSERVER Deployment (No Fault Tolerance) With no fault tolerant SpectroSERVER's configured in your deployment, a temporary fault tolerant system will be used as a swing machine during the upgrade process. Once configured, the primary SpectroSERVER will be disabled for the in-place upgrade and the secondary swing SpectroSERVER will resume core network management duties. Some SPECTRUM applications may or may not support automatic failover and could be disabled during the upgrade. These applications may include: Remedy, TL1, Southbound Gateway, Modeling Gateway, Alarm Notifier, and Event Notifier. All SpectroGRAPH clients will automatically switch over to the secondary and basic network management visibility will be retained during the upgrade. Figure 1 is a typical distributed SPECTRUM deployment: Page 9

10 Figure 1: Distributed SPECTRUM Deployment MoM Secondary swing SpectroSERVER SpectroSERVER 1 SpectroSERVER 2 SpectroSERVER 3 In the illustration above, the swing machine has been added. This machine will be systematically configured as the secondary, fault tolerant server for each SpectroSERVER that is upgraded, beginning with the MoM (Mother of Managers) server. The MoM SpectroSERVER is also the Main Location Server for all SpectroSERVER's. The procedure to perform an in-place upgrade with no network management loss is described below. These steps are for general guidance. For detailed information, refer to the SPECTRUM Installation Guide (0675) and the Distributed SpectroSERVER (2770) guide. Begin the upgrade process by upgrading the MoM first. 1. Install the current (pre-upgrade) version of SPECTRUM on the swing machine. That is, if you have currently deployed, install (w/required patches) on the swing machine. Ensure the Main Location Server for the swing machine is MoM server. Once installed, do not start the SpectroSERVER. 2. Edit the Host Security of the swing machine. The list of host names should be identical to the MoM. 3. Perform an on-line backup of the SpectroSERVER database on the MoM machine. Be sure to disable file compression and auto backup features until the entire upgrade process is complete. Copy this database to the <$SPECROOT>/SS directory on the swing machine. See SPECTRUM Installation Guide (0675) for more details. Page 10

11 4. On the swing machine, with the SpectroSERVER shutdown, navigate to the SS directory. Load the database file using the following command:../ss-tools/ssdbload -il -add <precedence> <savefile> where <precedence> is a numeric value greater than the primary's [MoM] default value of 10 (20 is recommended), and <savefile> is the name of the save file created in step Start the SpectroSERVER on the secondary swing machine. The swing machine is now the secondary fault tolerant SpectroSERVER to the MoM. Stop the Archive Manager on the secondary to avoid losing event and statistical data. All data will be cached and returned to the primary once the upgrade is complete and the primary is restarted. After shutting down Archive Manager, an orange alarm will be generated on the VNM-this is normal. Simply clear the alarm or ignore it. To help insure no events are lost during the upgrade, increase the maximum locally stored event record size. The default maximum locally stored log sizes for events and statistics are 20,000 and 5,000, respectively. However, in most cases, these default settings are sufficient. 6. To verify proper setup of the secondary fault tolerant SpectroSERVER, check the Landscape Configuration view on the MoM server. To do this, double-click on the arrow on the VNM icon in the Universe view of the SpectroGRAPH. The landscape container will now be displayed. Right-click on the landscape container and select Configuration from the sub-menu. The Landscape Configuration view should display both the primary and newly configured secondary SpectroSERVER's. This view may take a couple of minutes to update so the view may have to be re-opened a couple of times. If the landscape container is flashing an alarm condition, it usually means the secondary SpectroSERVER is not correctly configured. Model the alarm and follow the recommended actions listed in Alarm Manager. 7. Once the secondary SpectroSERVER is verified (as described above), shutdown the primary (MoM) SpectroSERVER. The secondary SpectroSERVER will resume management while the MoM is being upgraded. Secondary failover can be verified by viewing the SpectroGRAPH connection status and/or depending on your version, a yellow border may appear around the SpectroGRAPH window. Follow the in-place upgrade steps described in the Spectrum Installation Guide (0675). Page 11

12 8. Once the MoM has been successfully upgraded, start the SpectroSERVER. Be sure to run all deprecation scripts and review the post install steps as outlined in the Spectrum Installation Guide (0675). Primary management function will switch back over to the MoM SpectroSERVER. 9. Upgrade of the MoM SpectroSERVER is now complete. The swing machine must now be configured as the secondary to SpectroSERVER 1 (see Figure 1). Repeat steps 3 through 8 for SpectroSERVER 1 and the remaining SpectroSERVERs. Once all SpectroSERVERs are upgraded, upgrade any SpectroGRAPH-only machines. Finally, upgrade the Web Operator Suite. In-Place Upgrade with a Distributed SpectroSERVER Environment and Fault Tolerance Deployment The following section describes the upgrade process over an existing fault tolerant deployment. This process temporarily eliminates fault tolerance during the upgrade. If you must maintain fault tolerance during the upgrade process, a swing machine configured as a tertiary fault tolerant system must be configured. However, this adds complexity and will significantly lengthen the entire upgrade process. Temporarily eliminating fault tolerance is the easiest and fastest method for conducting an upgrade (described below). With a pre-existing distributed and fault tolerant SPECTRUM deployment, the process for conducting in-place upgrades is easier, especially if every SpectroSERVER in your environment is configured with a secondary backup, as illustrated in Figure 2: Page 12

13 Figure 2: Fault Tolerant SPECTRUM Deployment MoM Secondary MoM Fault Tolerant SpectroSERVER SpectroSERVER 1 SpectroSERVER 2 SpectroSERVER 3 Secondary Fault Tolerant SpectroSERVER 1 Secondary Fault Tolerant SpectroSERVER 2 Secondary Fault Tolerant SpectroSERVER 3 Even if only one SpectroSERVER is configured with a secondary server, time is saved as the swing machine is already setup. The steps to complete the upgrade without losing network management are similar to those in the previous section. Begin the upgrade process by upgrading the MoM first. 1. If the MoM server is already configured with a fault tolerant system, skip to step 7. Otherwise, setup a secondary system for the MoM SpectroSERVER as described below. You can either setup a new swing machine or temporarily disable fault tolerance on another SpectroSERVER and use this as the swing box. 2. Edit the Host Security of the secondary swing machine. The list of host names should be identical to the MoM. 3. Perform an on-line backup of the SpectroSERVER database on the MoM machine. Be sure to disable file compression and auto backup Page 13

14 features until the entire upgrade process is complete. Copy this database to the <$SPECROOT>/SS directory on the swing machine. See SPECTRUM Installation Guide (0675) for more details. 4. On the swing machine, with the SpectroSERVER shutdown, navigate to the SS directory. Load the database file using the following command:../ss-tools/ssdbload -il -add <precedence> <savefile> where <precedence> is a numeric value greater than the primary's [MoM] default value of 10 (20 is recommended), and <savefile> is the name of the save file created in step Start the SpectroSERVER on the secondary swing machine. The swing machine is now the secondary fault tolerant SpectroSERVER to the MoM. Stop the Archive Manager on the secondary to avoid losing event and statistical data. All data will be cached and returned to the primary once the upgrade is complete and the primary is restarted. After shutting down Archive Manager, an orange alarm will be generated on the VNM. This is normal. Simply clear the alarm or ignore it. To help insure no events are lost during the upgrade, increase the maximum locally stored event record size. The default maximum locally stored log sizes for events and statistics are 20,000 and 5,000, respectively. However, in most cases, these default settings are sufficient. 6. To verify proper setup of the secondary fault tolerant SpectroSERVER, check the Landscape Configuration view on the MoM server. To do this, double-click on the arrow on the VNM icon in the Universe view of the SpectroGRAPH. The landscape container will now be displayed. Right-click on the landscape container and select Configuration from the sub-menu. The Landscape Configuration view should display both the primary and newly configured secondary SpectroSERVERs. This view can take several minutes to update and may have to be reopened a number of times to be refreshed. If the landscape container is flashing an alarm condition, it usually means the secondary SpectroSERVER is not correctly configured. Model the alarm and follow the recommended actions listed in Alarm Manager. 7. Once the secondary SpectroSERVER is verified, shutdown the primary (MoM) SpectroSERVER. The secondary SpectroSERVER will resume management while the MoM is being upgraded. Secondary failover can be verified by viewing the SpectroGRAPH connection status and/ or depending on your version, a yellow border may appear around the Page 14

15 SpectroGRAPH window. Follow the in-place upgrade steps described in the SPECTRUM Installation Guide (0675). 8. Once the MoM has been successfully upgraded, start the SpectroSERVER. Be sure to run all deprecation scripts and review the post install steps as outlined in the SPECTRUM Installation Guide (0675). Primary management function will switch back over to the MoM SpectroSERVER. 9. Upgrade of the MoM SpectroSERVER is now complete. The swing machine must now be configured as the secondary to any other SpectroSERVER not already running a fault tolerant server. If all other SpectroSERVER's are already configured with fault tolerant servers, simply shut down the primary servers and follow the upgrade procedures (one at a time). Repeat the necessary steps to complete the upgrade process. Once all primary SpectroSERVERs are upgraded, upgrade the secondary SpectroSERVERs followed by any SpectroGRAPH only machines. Finally, upgrade the Web Operator Suite. When upgrading the secondary SpectroSERVER's, fault tolerance will be temporarily disabled during the upgrade. Page 15

16 Using SPECTRUM Version 6.6 Distributed Install (SDI) Functionality For SPECTRUM v6.6, new functionality was added to enable administrators to install SPECTRUM (new versions, upgrades, and patches) from a remote location. While SDI makes new installations extremely fast and easy, conducting multiple, simultaneous in-place upgrades may be work intensive due to SDI s current setup procedures. For example, the v6.6 sradmin service must be installed on all target install machines prior to running SDI. In some cases, this cannot be completed remotely. Therefore, since the administrator must be located at the target machine to update this service, it may be easier to conduct the full SPECTRUM upgrade locally at that point rather than conducting it remotely. SPECTRUM Service Pack 01 includes functionality that automatically updates the sradmin service on all target machines, using this service pack makes conducting in-place upgrades with SDI much easier. Page 16

17 Index A Alarm Notifier [9] D Distributed SpectroSERVER [9], [12] E Event Notifier [9] F Fault Tolerance [9], [12] L lab license [7] M Modeling Gateway [9] P patches [8], [16] R Remedy [9] S SDI [16] Southbound Gateway [9] SpectroWATCH [8] SPECTRUM Service Pack 01 [16] Page 17

18 SPECTRUM license(s) [7] SPECTRUM patches [16] SPECTRUM Version 6.6 Distributed Install [16] swing machine [6], [7] T TL1 [9] W Web Operator Suite [8], [9], [12], [15] Page 18