Installing and Upgrading Avaya Auraâ„¢ System Manager

Installing and Upgrading Avaya Aura™System Manager

Release 5.2January 2010

© 2010 Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts were made to ensure that the information inthis document was complete and accurate at the time of printing, AvayaInc. can assume no liability for any errors. Changes and corrections tothe information in this document might be incorporated in futurereleases.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, additions, ordeletions to the original published version of this documentation unlesssuch modifications, additions, or deletions were performed by Avaya.Customer and/or End User agree to indemnify and hold harmlessAvaya, Avaya's agents, servants and employees against all claims,lawsuits, demands and judgments arising out of, or in connection with,subsequent modifications, additions or deletions to this documentationto the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linkedWeb sites referenced elsewhere within this documentation, and Avayadoes not necessarily endorse the products, services, or informationdescribed or offered within them. We cannot guarantee that these linkswill work all the time and we have no control over the availability of thelinked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to yoursales agreement to establish the terms of the limited warranty. Inaddition, Avaya’s standard warranty language, as well as informationregarding support for this product, while under warranty, is availablethrough the Avaya Support Web site: http://www.avaya.com/support

Licenses

USE OR INSTALLATION OF THE PRODUCT INDICATES THE ENDUSER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN ANDTHE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE http://www.avaya.com/support/LicenseInfo/ ("GENERALLICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BYTHESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THEPOINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FORA REFUND OR CREDIT.

Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units ofcapacity for which the license is granted will be one (1), unless adifferent number of licenses or units of capacity is specified in theDocumentation or other materials available to End User. "DesignatedProcessor" means a single stand-alone computing device. "Server"means a Designated Processor that hosts a software application to beaccessed by multiple users. "Software" means the computer programsin object code, originally licensed by Avaya and ultimately utilized byEnd User, whether as stand-alone Products or pre-installed onHardware. "Hardware" means the standard hardware Products,originally sold by Avaya and ultimately utilized by End User.

Copyright

Except where expressly stated otherwise, the Product is protected bycopyright and other laws respecting proprietary rights. Unauthorizedreproduction, transfer, and or use can be a criminal, as well as a civil,offense under the applicable law.

Third-party components

Certain software programs or portions thereof included in the Productmay contain software distributed under third party agreements ("ThirdParty Components"), which may contain terms that expand or limitrights to use certain portions of the Product ("Third Party Terms").Information identifying Third Party Components and the Third PartyTerms that apply to them is available on the Avaya Support Web site: http://www.avaya.com/support/ThirdPartyLicense/

Preventing toll fraud

"Toll fraud" is the unauthorized use of your telecommunications systemby an unauthorized party (for example, a person who is not a corporateemployee, agent, subcontractor, or is not working on your company'sbehalf). Be aware that there can be a risk of toll fraud associated withyour system and that, if toll fraud occurs, it can result in substantialadditional charges for your telecommunications services.

Avaya fraud intervention

If you suspect that you are being victimized by toll fraud and you needtechnical assistance or support, call Technical Service Center TollFraud Intervention Hotline at +1-800-643-2353 for the United Statesand Canada. For additional support telephone numbers, see the AvayaSupport Web site: http://www.avaya.com/support/

Suspected security vulnerabilities with Avaya Products should bereported to Avaya by sending mail to: [email protected].

Trademarks

Avaya, the Avaya logo, Avaya Aura™ System Manager are eitherregistered trademarks or trademarks of Avaya Inc. in the United Statesof America and/or other jurisdictions.

All other trademarks are the property of their respective owners.

Downloading documents

For the most current versions of documentation, see the Avaya SupportWeb site: http://www.avaya.com/support

Contact Avaya Support

Avaya Inc. provides a telephone number for you to use to reportproblems or to ask questions about your product. The supporttelephone number is 1-800-242-2121 in the United States. Foradditional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support

Contact Avaya Support

Avaya Inc. provides a telephone number for you to use to reportproblems or to ask questions about your product. The supporttelephone number is 1-800-242-2121 in the United States. Foradditional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support

2 Installing and Upgrading Avaya Aura™ System Manager January 2010

http://www.avaya.com/support

http://www.avaya.com/support/LicenseInfo

http://www.avaya.com/support/ThirdPartyLicense/

http://www.avaya.com/support/






Contents

Chapter 1: System Manager - installation requirements......................................................5Introduction......................................................................................................................................................5Hardware requirements....................................................................................................................................5

Chapter 2: Checklists and worksheets....................................................................................7System Manager installation checklist..............................................................................................................7System Manager information worksheet..........................................................................................................7

Chapter 3: Installing System Manager Template....................................................................9Downloading System Manager from PLDS......................................................................................................9Installing the System Manager template........................................................................................................10

Default Credentials................................................................................................................................12

Chapter 4: System Manager Upgrades..................................................................................13Upgrade the System Manager Template........................................................................................................13

Performing load to load upgrade............................................................................................................13Performing release to release upgrade..................................................................................................16Default Credentials................................................................................................................................18

Chapter 5: Modify Alarm ID and Managed element ID........................................................19Modifying an Alarm ID....................................................................................................................................19Modifying managed Element ID......................................................................................................................20

Chapter 5: Switching to Cold Standby Server......................................................................21Cold Standby server as the failover server for System Manager....................................................................21Setting up a Cold Standby server..................................................................................................................21

Creating backup of application data......................................................................................................22Scheduling a data backup......................................................................................................................23Restoring a backup................................................................................................................................23

Chapter 7: Removing the System Manager template..........................................................25

Index.........................................................................................................................................27

Installing and Upgrading Avaya Aura™ System Manager January 2010 3

Contents


Chapter 1: System Manager - installationrequirements

IntroductionThe Avaya Aura™ System Manager delivers a set of shared management services which youcan access using the System Manager common console.

The System Manager Template is packaged and delivered in an ISO file. This templatecontains Red Hat Enterprise Linux 5.3 and System Manager installed on RHEL 5.3. Installingthe System Manager virtual appliance requires you to perform the following steps:

1. Install System Platform.

2. Install the System Manager virtual appliance on System Platform.

Hardware requirementsSystem Manager is to be installed on either an Avaya S8510 server or an Avaya S8800 server,depending on what was ordered. These servers arrive at the customer’s site with all therequired components and memory. Prior to installing System Manager on the server you haveto install System Platform product on the hardware.


System Manager - installation requirements


Chapter 2: Checklists and worksheets

System Manager installation checklist

# Action Notes

1 Download the System Platform1.1 SP1 build 2 ISOinstaller ISO image & applicablepatch from the Avaya PLDS Website.

Verify that the md5sum forthe downloaded ISOmatches the numbermentioned on the PLDS site.

2 Download the System Managertemplate present in theSystem_Manager_05_02_GA_02.iso file from the Avaya PLDS Website.

Verify that the md5sum forthe downloaded templatematches the numbermentioned on the PLDS site.

3 Set up a DVD or USB flash drive toperform the System Platforminstallation from a DVD or USB flashdrive.

See Installing SystemPlatform guide on the AvayaSupport Web site to deploythe System Platform producton the hardware.

4 Deploy the System Managertemplate on System Platform byfollowing the installation procedurementioned in this guide.

System Manager information worksheetThe System Manager template deployment using the System Platform Console requires youto fill in several fields. Having the information available at the time of installation expedite theSystem Manager deployment and ensures accuracy. Print out the following tables and workwith your network administrator to fill in the appropriate value for each field displayed in thetables.


For the System Manager Virtual Appliance

Field Value Notes

IP address Enter the IP address that is to be assigned tothe System Manager virtual appliance onSystem Platform.

ShortHostname

Enter the short host name for the SystemManager.

Non-rootUser

This is an optional field. A non-root user ID tobe entered if you want to do the install using anon-root ID.

LoginDomain

Enter the domain name. This domain namegets appended to all users that do not have adomain name associated with it.

DomainName

Enter the domain name for your setup. Forexample: production.mydomain.com

For the Network Configurations

Field Value Notes

GatewayAddress

Enter the IP address of the server that hasbeen set up as the gateway in your enterpriseenvironment.

NetworkMask

Enter the network mask value.

DNS Enter the IP address of the Domain NameServer.

SearchString

Enter the search string. The system uses thissearch string to resolve the domain names.

Checklists and worksheets


Chapter 3: Installing System ManagerTemplate

Downloading System Manager from PLDS

1. Type http://plds.avaya.com in your web browser to open the ProductLicensing and Delivery System Web site.

2. Click Log in with my password.

3. Enter your login and password detailsYour login id is your e-mail address.

4. Click Log In.

5. On the Home page, expand Asset Mgmt and click View Downloads.

6. On the Downloads page, enter your company's name in the %Company field.

7. In the Application drop down menu, choose “System Manager”.

8. Click Search Downloads.

9. From the Software Downloads list, locate theSystem_Manager_05_02_GA_02.iso file and download them.System_Manager_05_02_GA_02.iso contains the following files:

a. System Manager 5.2 template (gzip file)

b. System Manager 5.2 backup plugin script file (sh file)

c. System Manager 5.2 template descriptor (ovf file)

You can also download the System Manager 5.2 template (gzip file),System Manager 5.2 backup plugin script file (sh file), andSystem Manager 5.2 template descriptor (ovf file) that are presentin the ISO file individually from the same location.

10. On the About the Download Manager page, click Click to download your file now.

11. If you receive an error message, click on the message, install Active X, and continuewith the download.

12. When the security warning displays, click Install.


When the install is complete, Product Licensing and Delivery System (PLDS)displays the downloads again with a checkmark next to the download which issuccessfully completed.

Installing the System Manager templateWhen you install System Manager on a virtual machine using the System Manager Template,the System Manager Template installs Linux Operating System and System Manager.

PrerequisitesUse System Platform 1.1 SP1 build 2 ISO installer to install System Platform.

Note:See the Installing System Platform guide on the Avaya Support Web site for information onthe installation of System Platform.

1. Perform the following sub steps in this step if you downloaded theSystem_Manager_05_02_GA_02.iso file containing the installer files:

a. Log in to the System Platform on C-dom with root privileges using ssh .

b. Type mkdir /iso at the command prompt.

c. Copy the System_Manager_05_02_GA_02.iso file in the /tmp folder.

d. Type mount -o ro,loop /tmp/System_Manager_05_02_GA_02.iso /iso at the command prompt.

e. Type cd /iso at the command prompt and verify if all the files are present inthe iso folder.

The ISO folder must contain the following files:

a. System Manager 5.2 template (gzip file)

b. System Manager 5.2 backup plugin script file (sh file)

c. System Manager 5.2 template descriptor (ovf file)

2. Enter the https://<IPAddress>/webconsole URL in the web browser to login to the C-dom web console, where <IPAddress> is the IP address of C-dom.

3. Log in to the C-dom web console with the administrator credentials made availableat the time of the System Platform installation.

4. On the System Platform console, click Virtual Machine Management > SolutionTemplate in the left navigation pane.

Installing System Manager Template


5. On the Search Local and Remote Template page, select an appropriate installationmode.

Note:The files downloaded from the PLDS Web site or extracted from the ISO imageof the installer in step 1 can be stored on different locations. The selection of alocation depends on the mode using which you want to deploy the SystemManager template. See the Selecting a template to install section in Chapter 8of the Installing System Platform guide.

6. Click Search to find the installation OVF file.

7. From the Select Template drop-down field, click the SystemManagerGA.ovf fileand click Select.

8. On the Templates Details page, click Install.

9. Click Save.

10. On the Templates Details page, in the IP address of the SMGR field enter the IPaddress of the virtual machine on which you are installing System Manager.This IP address should be different from the IP address of the C-dom and Dom–0virtual machines.

11. In the SMGR short hostname field, enter the short host name of the virtualmachine.

12. In the SMGR domain field, enter an appropriate domain name based on yourenterprise environment.For example you can enter a domain name in the form of mydomain.com.

13. In the Gateway address field, enter the IP address of the computer configured asgateway in your enterprise environment.

14. In the Network mask field, enter the network mask value.

15. Enter the login domain for users in the Login Domain field.Following are the rules for setting a domain name:

• The domain name part before the DOT can only contain digits (0–9), letters(a-z), and hyphen (-). It must not begin or end with a hyphen (-). Forexample, [email protected] and [email protected] areinvalid domain names. [email protected] is a valid domain name.

• The domain name must not start or end with a DOT and must not containconsecutive DOT's. For example [email protected],[email protected], [email protected]. are invalid domainnames.

• The domain name part after DOT must contain country code. For example,com, co.in, gov and so on. [email protected] is an not a valid domainname as the name does not have a country code.

• Each country code can contain only letters. For example,[email protected] is an invalid domain name as the country codecontains digits .

Installing the System Manager template


• Each country code must have at least two letters, for [email protected] is invalid [email protected] is valid domainname.

• The domain name must not contain any upper case letters.

16. In the SearchString field, enter a search string.

17. In the DNS field, enter an the IP address of the domain name server.

18. In the Non-root User field, enter the non root user name. This is an optional field.

19. Click Install.After the completion of System Manager installation, enter the https://<IPAddress>/SMGR URL in the web browser to access System Manager,where<IPAddress> is the IP address of the System Manager virtual appliance.

Related topics:Default Credentials on page 12

Default CredentialsAccessing System Manager Virtual ApplianceTo log in on the command prompt of the System Manager virtual appliance, you need to sshto the IP address of the virtual appliance. Use root as the login ID and root01 as password.You must change the default password on the initial login.

Accessing System Manager Common ConsoleTo access System Manager Common Console, enter the https://<IPAddress>/SMGRURL in the web browser where <IPAddress> is the IP address of the System Manager virtualappliance. The default user name and password for accessing the System Manager commonconsole is admin and admin123. You must change the default password on the initial login.

Installing System Manager Template


Chapter 4: System Manager Upgrades

Upgrade the System Manager Template

The upgrade for System Manager is available from previous load to the current load of SystemManager Release 5.2 and as release to release upgrade from System Manager Release 1.0to System Manger Release 5.2.

Related topics:Performing load to load upgrade on page 13Performing release to release upgrade on page 16Default Credentials on page 18

Performing load to load upgradePrerequisites

Before you perform the upgrade procedure, you must take a backup of the installedSystem Manager Template. See the Creating backup of application data section underSetting up a Cold Standby server in Chapter 6 for creating a backup of the installedSystem Manager data.

Ensure that System Platform 1.1 SP1 build 2 installed on your computer. See UpgradingAvaya Aura™ System Platform guide on the Avaya Support Web site for steps onupgrading System Platform.

1. Log in to the computer on which you installed System Manager and follow the stepsto note the alarmID:

a. At the command prompt, type cd $SPIRIT_HOME/scripts/ and pressEnter .The $SPIRIT_HOME/scripts/ directory has SAL Agent command lineutilities.

b. Type sh spiritAgentCLI and press Enter to execute the SAL Agentcommand line utility.This displays the command line options. Each option is assigned a number.

c. Take a note of the current alarm ID that is displayed along with option 1.


The option (1) updates the alarming module for the specified alarm ID.

d. Type 0 to quit the SAL Agent command line utility without saving the changes.

2. Download the latest System Manager Template files from the PLDS Web site.

3. Replace BackupSMGR.sh and vspUtil.jar present in/opt/vsp with theBackupSMGR.sh and vspUtil.jar files downloaded from the PLDS.

4. Type dos2unix BackupSMGR.sh at the command prompt to convert the file toUNIX text file format.

5. Type chmod +x BackupSMGR.sh to give the execute permission on the script file.




9. On the Search Local and Remote Template page, select an appropriate installationmode.

Note:The files downloaded from the PLDS Web site or extracted from the ISO imageof the installer in step 1 can be stored on different locations. The selection of alocation depends on the mode using which you want to deploy the SystemManager template. See the Selecting a template to install section in Chapter 8of the Installing System Platform guide.

10. Click Upgrade.

11. On the Select Template page, click theSystemManager_Beta_GA_upgrade.ovf file and click Select.

12. Click Upgrade.

13. Click Save.

14. On the Templates Details page, in the IP address of the SMGR field enter the IPaddress of the virtual machine on which you are installing System Manager.This IP address should be different from the IP address of the C-dom and Dom–0virtual machines.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

15. In the SMGR short hostname field, enter the short host name of the virtualmachine.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

16. In the SMGR domain field, enter an appropriate domain name based on yourenterprise environment.

System Manager Upgrades


Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

17. In the Gateway address field, enter the IP address of the computer configured asgateway in your enterprise environment.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

18. In the Network mask field, enter the network mask value.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

19. In the SearchString field, enter a search string.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

20. In the login domain field, enter the domain name of the user logging into SystemManager.Following are the rules for setting a domain name:

• The domain name part before the DOT can only contain digits (0–9), letters(a-z), and hyphen (-). It must not begin or end with a hyphen (-). Forexample, [email protected] and [email protected] areinvalid domain names. [email protected] is a valid domain name.

• The domain name must not start or end with a DOT and must not containconsecutive DOT's. For example [email protected],[email protected], [email protected]. are invalid domainnames.

• The domain name part after DOT must contain country code. For example,com, co.in, gov and so on. [email protected] is an not a valid domainname as the name does not have a country code.

• Each country code can contain only letters. For example,[email protected] is an invalid domain name as the country codecontains digits .

• Each country code must have at least two letters, for [email protected] is invalid [email protected] is valid domainname.

• The domain name must not contain any upper case letters.

21. In the DNS field, enter an the IP address of the domain name server.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

22. In the Non-root User field, enter the non root user name. This is an optional field.Ensure that you provide the same information as was provided in the previousSystem Manager template installation.

23. Click Upgrade.



24. After the upgrade is complete, open a new browser and enter the https://<IPAddress>/SMGR URL to access the System Manager, where <IPAddress> isthe IP address of the System Manager virtual appliance.

25. Log in to the System Manager common console and perform a quick test byperforming some basic operations on System Manager. The test verifies if SystemManager is functioning properly. System Manager.

26. Click Commit Installation if you are able to log in to System Manager.If the quick test as specified in step 24 and 25 failed, click Rollback Installation.

Next stepsAfter the successful upgrade of System Manager you need to substitute the new alarm ID ofSystem Manager with the alarm ID that you took a note in Step 1. See the Modifying an Alarm IDsection in Chapter 5 for information on replacing the alarm ID.

Related topics:Modifying an Alarm ID on page 19Modifying managed Element ID on page 20

Performing release to release upgradePrerequisitesBefore you perform the upgrade procedure, you must take a backup of the installed SystemManager Template. See the Creating backup of application data section under the Setting up aCold Standby server in Chapter 6 for creating a backup of the installed System Manager data.

1. Log in to the computer on which you installed System Manager and follow thesubsteps in this step to note the alarmID:

a. At the command prompt, type cd $SPIRIT_HOME/scripts/ and pressEnter .The $SPIRIT_HOME/scripts/ directory has SAL Agent command lineutilities.

b. Type sh spiritAgentCLI and press Enter to run the SAL Agent commandline utility.Running this utility displays the command line menu options. Each menu optionis assigned to a number.

c. Take a note of the current alarm ID that is displayed along with option 1.

d. Type 0 to quit the SAL Agent command line utility.

2. Download the latest System Manager Template files from the PLDS Web site.



3. Type mkdir -p /opt/vsp to create a directory /opt/vsp on the computer onwhich System Manager R1.0 SP3 is installed.

4. Copy BackupSMGR-R1xSP3.sh and vspUtil.jar downloaded in Step 2 to the /opt/vsp directory.

5. Type dos2unix BackupSMGR-R1xSP3.sh at the command prompt to convertthe file to UNIX text file format.

6. Type chmod +x BackupSMGR-R1xSP3.sh to give the execute permission on thescript file.

7. Type sh BackupSMGR-R1xSP3.sh at the command prompt to run theBackupSMGR-R1xSP3.sh script file.

8. Copy the /tmp/MgmtBackup_1.0.*.zip file created in step 7 to a differentcomputer on the network if upgrading on the same machine.

9. Install System Platform.See the installing System Platform guide on the Avaya Support Web site forinformation on the installation of System Platform 1.1 SP1 build 2.

10. Install System Manager Template.See the Installing System Manager section in this guide for more information on theinstallation of System Manager Template.

Note:Since this is an upgrade, you are required to use same Hostname and IPAddress,Domain Name, Gateway Address, Network Mask, DNS for System ManagerTemplate machine. If you are using different machine for SP installation, switchoff the computer on which System Manager R1.0 SP3 is installed.

11. Copy the MgmtBackup_1.0.*.zip file that you took a backup in step 8 to the /tmp/ directory in the 5.2 GA template.

12. Go to the /opt/vsp directory.

13. Type sh RestoreSMGR.sh to run the RestoreSMGR.sh script file.This upgrades System Manager from 1.0 to 5.2.

Next stepsAfter successful upgrade of System Manager you need to substitute the new alarm ID ofSystem Manager with the alarm ID that you took a note in Step 1. See the Modifying an Alarm IDsection in Chapter 5 for information on replacing the alarm ID.

Related topics:Modifying managed Element ID on page 20Modifying an Alarm ID on page 19



Default CredentialsAccessing System Manager Virtual ApplianceTo log in on the command prompt of the System Manager virtual appliance, you need to sshto the IP address of the virtual appliance. Use root as the login ID and root01 as password.You must change the default password on the initial login.

Note:An upgrade resets the password to root 01.



Chapter 5: Modify Alarm ID and Managedelement ID

After the new installation, the system needs to be registered using the Functional Location (FL)and product type. At that time, a Product ID will be provided for each managed element foralarm reporting.

Related topics:Modifying an Alarm ID on page 19Modifying managed Element ID on page 20

Modifying an Alarm ID

1. Log in to the computer on which you installed System Manager.

2. At the command prompt, type cd $SPIRIT_HOME/scripts/ and press Enter .The $SPIRIT_HOME/scripts/ directory has SAL Agent command line utilities.

3. Type sh spiritAgentCLI and press Enter to execute the SAL Agent commandline utility.This displays the command line options. Each option is assigned a number.

4. Type 1 .

5. Type the new alarm ID when the prompt asks you to enter the new SPIRIT alarmingID and press Enter.

6. On the main menu, type 99 to save the changes and quit the SAL Agent commandline utility.The alarm id is modified to the required value.


Modifying managed Element ID

1. Log in to the computer on which you installed System Manager.

2. At the command prompt, type cd $SPIRIT_HOME/scripts/utils and pressEnter .The $SPIRIT_HOME/scripts/ directory has SAL Agent command line utilities.

3. Type sh setProductID.sh ProductType Element_ID and press Enter.where:

• sh setProductID.sh is the command name for setting the managedelement ID.

• ProductType is the name of the product for which you want to modify themanaged element ID. Currently, SAL Agent is configured with the followingProductType: SM, IPTCM, and SMELEM.

• Element_ID is the new managed element id for the specified product.

For example: sh setProductID.sh SM 70000002, where SM is the name of theproduct and 70000002 is the new element ID that you want to assign to the product.

Modify Alarm ID and Managed element ID


Chapter 5: Switching to Cold StandbyServer

Cold Standby server as the failover server for SystemManager

A cold standby System Manager server acts as a failover server when the main server runningSystem Manager fails. This section covers the Cold Standby failover process for the SystemManager application deployed on System Platform. This section explains the process with anexample of having 2 nodes, one being active and the other being the cold standby node. Thesection refers to Node A as the primary server that is active. Node B is the cold standby server.The cold standby procedure is to be executed in the scenario of Node A going down and theapplication is to be switched to Node B.

Setting up a Cold Standby serverPrerequisites

1. Primary (Node A) and Cold Standby (Node B) servers must have the same IPaddress and hostname. It is assumed that when the primary server is running, theStandby server is turned off.

2. The System Manager 5.2 template is deployed on the Primary and Standby serverusing the install procedure mentioned in the System Manager Installation Guide.

3. The system date must be identical on both the servers.

4. Using the Remote backup facility of System Manager Element Manager you musttake a regular backup of System Manager database of the Primary Server. Takingregular backups of System Manager database ensures the availability of the latestdata that you need for a cold standby procedure in case the Primary sever fails.Create the backup of the database on a remote computer or on an external storagedevice (for example, Tape drive, DVD, and so on). When the Primary server fails,use the backup to restore the database on the Standby server. See sectionScheduling a Data Backup in this chapter for information on scheduling a backupon the System Manager node.


1. Confirm that the Primary server (Node A) is turned off.

2. Turn on the Standby server (Node B).

3. Restore the last database backup that you took from the Primary sever on theStandby server using the backup & restore utility of System Manager ElementManager provided with System Manager. The section on Restoring a Backup in thischapter provides the information on restoring the backup on the System Managernode.After data restoration, System Manager on the Standby server (Node B) becomesavailable for operations.

Related topics:Creating backup of application data on page 22Scheduling a data backup on page 23Restoring a backup on page 23

Creating backup of application data

1. Log in to the Avaya Aura™ System Manager web interface as an administrator.

2. Click Settings > Backup and Restore .

3. Click Backup.

4. On the Backup page, perform one of the following steps:

• To back up data to a local drive, do the following:

i. Click Local option.

ii. In the File name field, enter the name of the backup file fieldthat you want to create.

• To back up data to a remote location, do the following:

i. Click Remote option.

ii. Specify the SCP server IP, SCP server port, user name,password, and file name in the respective fields.

5. Click Now.

If the backup is successful, the Backup and Restore page displays a message Backup createdsuccessfully!!.

Switching to Cold Standby Server


Scheduling a data backup



3. Click Backup.

4. On the Backup page, perform one of the following steps:

• To schedule a local backup, perform the following steps:


ii. In the File name field, enter the name of the backup file that youwant to create.

• To schedule a remote backup, perform the following steps:



5. Click Schedule.

6. On the Schedule Backup page, specify the following: Job Name, Task Time,Recurrence and Range in the respective fields.

7. Click Commit.

Restoring a backup



3. Click Restore.

4. On the Restore page, perform one of the following steps:

• To restore data from a local backup


ii. Enter the back up file name in the File name field.

• To restore data from a remote backup

Setting up a Cold Standby server




5. Click Restore.

After the successful restore operation, the user who initiated the restore is logged out of theSystem Manager console.

Switching to Cold Standby Server


Chapter 7: Removing the System Managertemplate




4. Click Delete Installed Template to delete the System Manager Template.


Removing the System Manager template


Index

Cchecklist, installation, ...................................................7cold standby as failover for System Manager ............21creating backup of application data ............................22

Ddefault Credentials ................................................12, 18downloading System Manager from PLDS ..................9

Hhardware requirements ................................................5

Iinstallation checklist .....................................................7installing System Manager Template ..........................10introduction ...................................................................5

Llegal notice ...................................................................2

Mmodify Alarm ID ..........................................................19modify managed element ID ......................................19modifying an Alarm ID ................................................19ModifyingManagedElementID ....................................20

Pperforming load to load upgrade ................................13performing release to release upgrade ......................16

Rremoving the System Manager Template ...................25restoring a backup ......................................................23

Sscheduling a data backup ...........................................23setting up a Cold Standby server ...............................21System Manager information worksheet ......................7

Uupgrade System Manager Template ..........................13

Wworksheet, System Manager information .....................7


Index


Documents

Installing and Upgrading Avaya Auraâ„¢ System Manager