Installing, Upgrading, and Patching Avaya Media Server 7

Installing, Upgrading, and Patching AvayaMedia Server 7.5

Release 7.5June 2013

© 2012 Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reserves theright to make changes and corrections to the information in thisdocument without the obligation to notify any person or organization ofsuch changes.

Documentation disclaimer

“Documentation” means information published by Avaya in varyingmediums which may include product information, operating instructionsand performance specifications that Avaya generally makes availableto users of its products. Documentation does not include marketingmaterials. Avaya shall not be responsible for any modifications,additions, or deletions to the original published version ofdocumentation unless such modifications, additions, or deletions wereperformed by Avaya. End User agrees 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 documentation,to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation provided by Avaya.Avaya is not responsible for the accuracy of any information, statementor content provided on these sites and does not necessarily endorsethe products, services, or information described or offered within them.Avaya does not guarantee that these links will work all the time and hasno control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on its Hardware and Software(“Product(s)”). Refer to your sales agreement to establish the terms ofthe limited warranty. In addition, Avaya’s standard warranty language,as well as information regarding support for this Product while underwarranty is available to Avaya customers and other parties through theAvaya Support Web site: http://support.avaya.com. Please note that ifyou acquired the Product(s) from an authorized Avaya reseller outsideof the United States and Canada, the warranty is provided to you bysaid Avaya reseller and not by Avaya.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ AREAPPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITHAVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINEDFROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE ORAN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THERIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONEELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, ORAUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OFYOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,DOWNLOADING OR USING THE SOFTWARE (HEREINAFTERREFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),AGREE TO THESE TERMS AND CONDITIONS AND CREATE ABINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (“AVAYA”).

Copyright

Except where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, or Hardwareprovided by Avaya. All content on this site, the documentation and theProduct provided by Avaya including the selection, arrangement anddesign of the content is owned either by Avaya or its licensors and isprotected by copyright and other intellectual property laws including thesui generis rights relating to the protection of databases. You may notmodify, copy, reproduce, republish, upload, post, transmit or distributein any way any content, in whole or in part, including any code andsoftware unless expressly authorized by Avaya. Unauthorizedreproduction, transmission, dissemination, storage, and or use withoutthe express written consent of Avaya can be a criminal, as well as acivil 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 regarding distributed Linux OS source code (for thoseProducts that have distributed the Linux OS source code), andidentifying the copyright holders of the Third Party Components and theThird Party Terms that apply to them is available on the Avaya SupportWeb site: http://support.avaya.com/Copyright.

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation and Product(s) provided by Avaya are theregistered or unregistered Marks of Avaya, its affiliates, or other thirdparties. Users are not permitted to use such Marks without prior writtenconsent from Avaya or such third party which may own the Mark.Nothing contained in this site, the Documentation and Product(s)should be construed as granting, by implication, estoppel, or otherwise,any license or right in and to the Marks without the express writtenpermission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners,and “Linux” is a registered trademark of Linus Torvalds.

Downloading Documentation

For the most current versions of Documentation, see the AvayaSupport Web site: http://support.avaya.com.

Contact Avaya Support

See the Avaya Support Web site: http://support.avaya.com for productnotices and articles, or to report a problem with your Avaya product.For a list of support telephone numbers and contact addresses, go tothe Avaya Support Web site: http://support.avaya.com, scroll to thebottom of the page, and select Contact Avaya Support.

2 Installing, Upgrading, and Patching Avaya Media Server 7.5 June 2013Comments? [email protected]

http://support.avaya.com

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

http://support.avaya.com/Copyright




mailto:[email protected]?subject=Installing, Upgrading, and Patching Avaya Media Server 7.5

Contents

Chapter 1: System requirements and preparation........................................................... 5System requirements................................................................................................................................ 5Hardware requirements and setup............................................................................................................ 5

Hardware requirements.................................................................................................................... 5Installing the server hardware.......................................................................................................... 6Connecting Avaya MS to the network.............................................................................................. 6

Software requirements.............................................................................................................................. 7Supported operating systems........................................................................................................... 7Linux kernel requirements................................................................................................................ 7MySQL server.................................................................................................................................. 8Linux package requirements............................................................................................................ 8Network port requirements............................................................................................................... 9

Red Hat Enterprise Linux installation........................................................................................................ 11Installing RHEL................................................................................................................................. 11Installing required packages using YUM.......................................................................................... 11Installing required packages using RPM.......................................................................................... 12Configuring hostname...................................................................................................................... 13Configuring SE Linux........................................................................................................................ 13Configuring the Linux firewall........................................................................................................... 14

Windows Server installation...................................................................................................................... 15Installing Windows Server 2008 R2................................................................................................. 15Changing the computer name.......................................................................................................... 16Disabling Admin Approval Mode for Windows 2008 administrators................................................. 16Avaya MS restart.............................................................................................................................. 17

Network and security configuration........................................................................................................... 17Securing Avaya MS installations...................................................................................................... 17Virtual Teaming Adapter configuration............................................................................................. 18NIC and switch configuration............................................................................................................ 18

PVI Checker.............................................................................................................................................. 19Obtaining the PVI Checker software................................................................................................ 19Verifying specifications using PVI Checker...................................................................................... 19Reviewing PVI Checker reports after installation............................................................................. 21

Chapter 2: Installation........................................................................................................ 23Installing Avaya MS on Linux.................................................................................................................... 23

Installing Avaya MS on Linux using the interactive command-line mode......................................... 23Installing Avaya MS on Linux using the silent mode........................................................................ 24

Uninstalling Avaya MS from Linux............................................................................................................ 26Uninstalling Avaya MS from Linux using the interactive command-line mode................................. 26Uninstalling Avaya MS from Linux using the silent mode................................................................. 27

Installing Avaya MS on Windows.............................................................................................................. 28Installing Avaya MS on Windows using the GUI mode.................................................................... 29Installing Avaya MS on Windows using the interactive command-line mode................................... 30Installing Avaya MS on Windows using the silent mode.................................................................. 31

Uninstalling Avaya MS from Windows...................................................................................................... 32

Installing, Upgrading, and Patching Avaya Media Server 7.5 June 2013 3

Uninstalling Avaya MS on Windows using the GUI mode................................................................ 33Uninstalling Avaya MS from Windows using the interactive command-line mode........................... 34Uninstalling Avaya MS from Windows in the silent mode................................................................ 35

Chapter 3: Patches.............................................................................................................. 37Quick Fix Engineering overview................................................................................................................ 37Obtaining QFE.......................................................................................................................................... 37Description of the patch tool..................................................................................................................... 37Installing a QFE patch............................................................................................................................... 38Removing a QFE patch............................................................................................................................. 40Managing QFEs on High Availability servers............................................................................................ 42Managing QFEs in a cluster...................................................................................................................... 42

Chapter 4: Service Packs................................................................................................... 43Installing a service pack............................................................................................................................ 43Removing a service pack.......................................................................................................................... 45Managing service packs on High Availability servers............................................................................... 48Managing service packs in a cluster......................................................................................................... 48

Chapter 5: Upgrade to Avaya MS 7.5................................................................................ 49Upgrade introduction................................................................................................................................. 49Prerequisites for Avaya MS 7.5 upgrade.................................................................................................. 50Avaya MS upgrade overview.................................................................................................................... 51

High-level task for upgrading a multi-server Avaya MS cluster........................................................ 51High-level task for upgrading a single-server Avaya MS server....................................................... 51

Performing a backup................................................................................................................................. 52Upgrade a multi-server Avaya MS cluster................................................................................................. 53

Separation of a multi-server Avaya MS cluster................................................................................ 53Upgrading a multi-server Avaya MS cluster..................................................................................... 54

Upgrading a single Avaya MS................................................................................................................... 57Rollback of Avaya MS 7.5 upgrade........................................................................................................... 61

Performing a cluster rollback............................................................................................................ 61Performing a single server rollback.................................................................................................. 64

Index..................................................................................................................................... 69

4 Installing, Upgrading, and Patching Avaya Media Server 7.5 June 2013

Chapter 1: System requirements andpreparation

System requirementsYou can install Avaya Media Server (MS) 7.5 on commercially available off-the-shelf (COTS)hardware using standard server operating systems. The hardware and operating systemconfiguration must meet the minimum system requirements to support the functionality ofAvaya MS. Avaya provides the Platform Vendor Independent (PVI) Checker software to verifythat the server you have installed meets the system requirements required to support AvayaMS 7.5.

Review the system requirements in this chapter and perform the procedures to configure yoursystem. Run PVI Checker after you complete the hardware and operating system configurationto verify that the system meets the minimum requirements.

Hardware requirements and setup

Hardware requirementsThe server must meet the following hardware requirements to support Avaya MS functionality:

Hardware requirementsHardware

ComponentMinimum

(audio/video)Typical

(audio/video)High Capacity(audio/video)

Number of Processorcores

2 4 8 or greater

Processor Speed 1.2 GHz 2.2 GHz or greater 2.5 GHz or greater

Memory 2 GB 4 GB 8 GB

Network Interfaces 1 at 100 Mbps orgreater

2 at 1000 Mbpsteamed

2 at 1000 Mbpsteamed


Hardware requirementsHardware

ComponentMinimum

(audio/video)Typical

(audio/video)High Capacity(audio/video)

Free Disk Space 3 GB 3 GB 3 GB

Disk Drive Speed 5000 RPM 10,000 RPM 10,000 RPM

Installing the server hardwareAbout this taskInstall the server hardware, especially rack mounted servers, in compliance with theinstructions of the manufacturer. Use approved mounting hardware and follow guidelines forproper ventilation and cooling.

Procedure

1. Install hardware by following the instructions of the hardware manufacture.

2. Connect applicable peripheral devices, for example, a monitor, a keyboard, and amouse.

3. Connect the power cables to the server and to a properly grounded powersource.

Important:If your server has redundant power supplies, ensure you connect the powercables to both power supplies.

4. Turn the server ON using the power button.

Connecting Avaya MS to the networkAbout this taskConnect Avaya MS to the required network using cables that meet 100 Mbps or 1000 Mbpsspecifications as applicable. For more information about connecting the server Ethernetcables, see the documentation of the server manufacturer.

Procedure

1. Connect the network cables between the network ports on the back of the serverand the required Ethernet switch.

System requirements and preparation



Important:When using multiple network connections, install and connect each connectionto the proper Ethernet switch for network redundancy.

2. Ensure the Ethernet activity lights are ON at each end of each Ethernetconnection.

Software requirements

Supported operating systemsInstall Avaya MS only on the following operating systems:

• Microsoft Windows Server 2008 R2

• Red Hat Enterprise Linux Advanced Platform 5.x

• Red Hat Enterprise Linux Server 5.x

• Red Hat Enterprise Linux Server 6.x

Important:Avaya MS does not support operating systems other than those listed.

The adopting product specifies whether you must use the 32-bit or 64-bit Red Hat EnterpriseLinux (RHEL) operating system.

Linux kernel requirementsAvaya MS requires Symmetric Multiprocessing (SMP). SMP is included in all i686 and x86_64kernel variants of RHEL 5 and RHEL 6.

Physical Address Extension (PAE) is required if you install an i686, 32-bit, variant of RHEL.PAE enables 32-bit architecture to address more than 4 GB of memory. PAE is enabled bydefault for the RHEL 5 Advanced Platform and RHEL 5 or RHEL 6 Server 32-bit variants.



MySQL serverAvaya MS installations include a MySQL server. There must be no other MySQL serverinstance on the system, even if the other MySQL server instance opens different serverports.

Linux package requirementsAvaya MS requires 32-bit versions of the following RHEL 5 or RHEL 6 packages:

cyrus-sasl-libe2fsprogs-libsglibckeyutils-libskrb5-libslibICElibSMlibX11libXaulibXdmcplibXextlibXtlibgcclibidnlibselinuxlibsepollibstdc++openldapzlibiproutelibaio




You must not install the mysql-server package. If the mysql-server package is alreadyinstalled, remove the package.

Network port requirementsAvaya MS requires network ports for management of the server, for communicating with clientsand other servers in your network, and for media transmission. The following tables list theports that Avaya MS requires to be available on the server and permitted through firewalls:

External protocol ports requiredPort Type Description Direction required3306 TCP MySQL Inbound and Outbound

3389 TCP Microsoft Remote Desktop(Windows)

Inbound

3998 UDP License Server Inbound and Outbound

4005 TCP Resource Manager ExternalSession

Inbound

4020 TCP High Availability MSLink Inbound and Outbound

4020 UDP High Availability MSLink Inbound and Outbound

5060 TCP SIP over TCP Inbound and Outbound

5060 UDP SIP over UDP Inbound and Outbound

5061 TCP SIP over TLS Inbound and Outbound

7410 TCP SOAP Server Inbound

7411 TCP SOAP Server TLS Inbound

8080 TCP EM HTTP Inbound

8443 TCP EM HTTPS Inbound

19999 TCP IvrMP SSData Inbound and Outbound

52005 TCP Content Store MSLink Inbound and Outbound

52007 TCP Content Store RTFT Inbound and Outbound

52009 TCP IvrMP RTFT Inbound and Outbound

External UDP port ranges required for media to clientsMedia service Linux port range Windows port range Direction required

IVR andConferencing

6000-32598 20000-45498 Inbound andOutbound



External UDP port ranges required for media to clientsMedia service Linux port range Windows port range Direction required

(Optional) MRCP 1030-4998 16000-19998 Inbound andOutbound

(Optional) Video 32600-42599 Not supported Inbound andOutbound

Avaya MS requires several ports for communication between components on the local host.The following table lists the local host ports that Avaya MS requires. These ports do not needto pass through firewalls.

Internal protocol ports requiredPort Type Description4001 TCP IvrMP MSLink

4004 TCP SIP UA MSLink

4014 TCP SIP UA Command Interface

4015 TCP Resource Manager Command Interface

7080 TCP ConfMP MSLink

8009 TCP Tomcat AJP connector

51000 TCP Resource Manager Inter ProcessCommunication

51002 TCP Voice XML Interpreter Inter ProcessCommunication

After Avaya MS is installed, you can use Avaya MS EM to reassign many of the ports AvayaMS uses. To change the default ports for Avaya MS, navigate to EM > SystemConfiguration > Network Settings > Advanced Settings.

You can also change the ports that EM uses. Edit the following files to change the ports AvayaMS EM uses:

• Linux:

install path/ma/apache-tomcat/conf/server.xml• Windows:

install path\multimedia_applications\apache-tomcat\conf\server.xmlRestart the server after changing the ports.




Red Hat Enterprise Linux installation

Installing RHELAbout this taskPerform the following procedure to install the RHEL operating system and configure theoperating system to meet Avaya MS system requirements:

Procedure

1. Install the RHEL operating system by following the Red Hat installationprocedures.You do not need to customize the software installation or include optional packagesduring the initial installation. Use the default server installation options.

2. Install all the latest, critical security updates.For update procedures, see Red Hat documentation. You can install securityupdates by using the Yellowdog Updater, Modified (YUM) package manager if youhave an internet connection.

3. Add the required user and administrator accounts, using defined procedures foryour site.

4. Restart the server.

Installing required packages using YUMAbout this taskPerform the following procedure for each of the required packages listed in the Required Linuxpackages section. The procedure is based on using the YUM package manager and theinstallation disc. Ensure that all the required packages are added to the system and the mysql-server package is not installed on the system. For more information about how to use YUM,see the Red Hat YUM manual.

Procedure

1. Insert RHEL DVD into the server and close the tray.

2. From a Linux shell, set up the YUM repository by copying the .repo description onthe DVD to the yum.repos.d location:



cp /mnt/cdrom/media.repo /etc/yum.repos.d/3. Edit the /etc/yum.repos.d/media.repo file, and add the following two lines:

baseurl=file:///mnt/cdromenabled=1

Tip:If the DVD was mounted at a location other than /mnt/cdrom, then change thepath accordingly.

4. Use YUM to install each required 32-bit package. 32-bit package are indicated byi686 in the file name. Do not install developer or x86_64 versions of thepackages.The following is an example of a YUM install command for the libX11 package:yum install libX11.i686

5. (Optional) Install the Simple Network Management Protocol (SNMP) softwareusing YUM in a Linux shell:yum install net-snmp-utils

6. Use YUM to remove the mysql-server package from the system:yum remove mysql-server

Related topics:Linux package requirements on page 8

Installing required packages using RPMAbout this taskPerform the following procedure for each of the required packages. For the list of requiredpackages, see Required Linux Packages. The procedure is based on using Red Hat PackageManager (RPM) and the installation disc. Ensure that all the required packages are added tothe system and the mysql-server package is not installed on the system. For moreinformation about how to use RPM, see the Linux RPM manual.

Procedure

1. Insert RHEL DVD into the server and close the tray.

2. From a Linux shell, create the cdrom directory:mkdir /mnt/cdrom

3. Mount the DVD to gain access to the content:mount -t iso9660 /dev/cdrom /mnt/cdrom




4. Go to the directory containing the RPM packages:cd /mnt/cdrom/Packages

5. Use RPM to install each required 32-bit package. 32-bit packages are indicated byi686 in the file name. Do not install developer or x86_64 versions of thepackages.The following is an example of an RPM install command for the libX11 package:rpm -ivh libX11-1.3-2.el6.i686.rpm

6. (Optional) Use RPM to install net-snmp-utils for the Simple NetworkManagement Protocol (SNMP) software.

7. Use RPM to remove the mysql-server package from the system:rpm -e mysql-server

Related topics:Linux package requirements on page 8

Configuring hostnameAbout this taskPerform the following procedure to associate the IP address of the server with the host nameand domain name when DNS is not available:

Procedure

Edit the file /etc/hosts and ensure that the IP address mapping to the host nameis configured as shown in the first line of the following example:135.45.72.153 Server4885.lab.avaya.com Server4885127.0.0.1 localhost.localdomain localhost::1 localhost6.localdomain6 localhost6

Important:The host name must not appear in the other lines which associate localhost.

Configuring SE LinuxAbout this taskBy default, RHEL sets the Security-Enhanced Linux (SE Linux) feature to enforcing. You mustensure SE Linux is set to disabled for Avaya MS.



Note:Disable SE Linux if the system displays the following error message:

Cannot restore segment prot after reloc: Permission denied.Procedure

To disable SE Linux, ensure SELINUX=disabled is set in the /etc/selinux/config file and then restart the server.

Configuring the Linux firewallAbout this taskFollow your adopting product documentation and installation procedures for proper firewallconfiguration. If adopting product firewall procedures are not available, perform the followingprocedure to modify RHEL default firewall rules so that the external ports listed in tables ofNetwork port requirements are permitted through the firewall. If you are not using the defaultRHEL firewall, see your firewall documentation.

Tip:If you want to turn the default firewall off to enable all ports and your site security policypermits this, do not use this procedure. Instead, use a Linux shell on Avaya MS and turn offthe firewall as follows:

service iptables stopchkconfig iptables off

Procedure

1. To allow the required ports through the firewall, edit the file:/etc/sysconfig/iptables

2. Add rules to iptables similar to the following one for port 8080 to open eachrequired port in the firewall:-A INPUT -m state --state NEW -m tcp -p tcp --dport 8080 –jACCEPT

3. Save and close the iptables file.

4. Restart the firewall:service iptables restart

5. Ensure the firewall is set to accept connections on the ports you added to theiptables file by looking for an ACCEPT row relating to your ports in the output ofthis command:




iptables -L –n

Related topics:Network port requirements on page 9

Windows Server installation

Installing Windows Server 2008 R2About this taskPerform the following procedure to install the Windows Server 2008 R2 operating system andconfigure the operating system to meet Avaya MS system requirements:

Procedure

1. Install the Windows Server 2008 R2 operating system by following the Microsoftinstallation procedures. Ensure you configure the following options during theinstallation:

• Configure the operating system as a standalone server.

• Do not install Internet Information Services (IIS).

2. Install the SNMP service:

a. Go to Start > Administrative Tools > Server Manager.b. Click Features in the left panel.c. Click Add Features on the right.d. Scroll down to locate SNMP services in the Features list and click plus sign

(+) to open the menu.e. Check the SNMP service.f. Click Next.g. Click Install.

3. Install all the latest, critical security updates, and service packs:

a. Go to Start > Control Panel > System and Security > Windows Update.b. Click Check for updates.

4. Add the required user and administrator accounts, using defined procedures foryour site.

Windows Server installation


5. Configure the operating system and firewall to ensure that the ports listed in Networkport requirements are properly configured.

Related topics:Network port requirements on page 9

Changing the computer nameAbout this taskPerform the following procedure to change the computer name of your Windows server beforeyou install the Avaya MS software. This is optional.

Procedure

1. Click Start, right-click Computer, and then click Properties.The system displays the System dialog box.

2. In Computer name, domain, and workgroup settings, click Change settings.The system displays the System Properties window.

3. Click Change.The system displays the Computer Name/Domain Changes window.

4. In the Computer Name field, type the new name for your computer.

5. Click OK in the Computer Name/Domain Changes window.

6. Click OK in the System Properties window.

Note:Restart the server for the changes to take effect. To avoid restarting the serverafter every preinstallation change, select No at the prompt, and then restart theserver later.

Disabling Admin Approval Mode for Windows 2008 administratorsAbout this taskWindows 2008 implements a security feature known as User Account Control (UAC). Bydefault, UAC causes applications run by local, non built-in administrators to function as if theapplications had been run by standard users. Running applications as a standard user canlead to problems when you install Avaya MS or when you configure the Avaya MS securityframework. With the following procedure, the local administrators receive full privilege forrunning applications.




Procedure

1. Navigate to Start > Administrative Tools.

2. Double-click Local Security Policy.The system displays the Local Security Policy window.

3. Select Security Settings.

4. Expand Local Policies by clicking on the plus sign (+).

5. Select Security Options.

6. In the policy pane on the right, scroll down and double-click the policy User AccountControl: Run all administrators in Admin Approval Mode.The system displays a new window.

7. On the Local Security Setting tab, select the Disabled option.

8. Click OK.

Note:Restart the server for the changes to take effect. To avoid restarting the serverafter every preinstallation change, select No at the prompt, and then restart theserver later.

Avaya MS restartIf the system prompted you to restart the server in any of the preceding procedures, ensurethat you restart the Windows server for the changes to take effect before you install AvayaMS.

Network and security configuration

Securing Avaya MS installationsAbout this taskPerform the following procedure to apply the following optional security measures to theoperating system you installed:

Network and security configuration


Procedure

1. (Optional) Configure the operating system using defined site securityprocedures.

2. (Optional) Install antivirus software and ensure that you exclude the followingdirectories and the subdirectories from the scans:

• Linux:

install path/ma/MAS/common/loginstall path/ma/MAS/platdata

• Windows:

install path\multimedia_applications\MAS\common\loginstall path\multimedia_applications\MAS\platdata

Important:

Scanning software can degrade the performance and decrease the reliability of thesystem. Install virus scanning software only if you connect the system to a networkexposed to the Internet.To maintain the performance of the server, you must schedule virus scans onlyduring maintenance periods or low usage hours.

Virtual Teaming Adapter configurationTeaming, also called bonding, of the network interfaces on your server into a single logicalnetwork interface provides increased throughput and redundancy in case one of the networkinterfaces fails. Teaming configuration is hardware specific. Follow the procedures providedby your server hardware manufacturer.

Avaya recommends using the active-backup bonding mode to provide fault tolerance for thesystem.

NIC and switch configurationAuto negotiation of transmission speed and duplex mode is mandatory for 1000 BASE-Tgigabit Ethernet over copper. To avoid duplex mode mismatches and other interoperabilityproblems, ensure that auto-negotiation is configured on the Network Interface Cards (NICs)and the switch. Configure the NICs and the switch with matching modes. If you disable auto-negotiation and configure the NICs to full-duplex mode or half-duplex mode then the switchmust also have auto-negotiation disabled and be set to the matching full-duplex mode or half-




duplex mode. For more information, see the configuration procedures your server and switchmanufacturer provide.

PVI CheckerPVI Checker is software that you run to verify that a server and the configured operating systemmeet the Avaya MS hardware and software requirements. PVI Checker is available asstandalone software that you can run on a server prior to installation and is automatically runby the Avaya MS installer. The installer blocks the installation on detecting anynoncompliance.

Obtaining the PVI Checker softwareAbout this taskFollow the recommendations in the documentation of the adopting product on how to obtainand run the PVI Checker utility. Typically, you can obtain the software from the productinstallation DVD.

From the PVI Checker installer DVD, run one of the following executable files:• Linux: mapvicheck• Windows: mapvicheck.exe

Verifying specifications using PVI CheckerPVI Checker provides three different user interface modes:

• The Graphical User Interface (GUI) mode for Windows installations.

• The Command-line mode for Windows or Linux operating systems.

• The Integrated installer mode, whenever the media server installer is run.

Using PVI Checker in the GUI mode

About this taskThe GUI mode is the default mode for Windows systems when you double-click the PVIChecker executable file. The GUI mode of the Avaya MS installer also displays the GUI modeof the PVI Checker to display information on noncompliance issues.

During the execution of the PVI Checker, the system displays a progress bar. After the systemcheck is completed, you can use the Summary, Software, Hardware, and Drives tabs toselect a particular category of results for review. See Figure 1: PVI Checker GUI.

PVI Checker


Figure 1: PVI Checker GUI

You can use the Save Log option in the File menu to save PVI Checker results. While the toolwindow is open, you can rectify non-compliances on the system and then rerun PVI Checkerby clicking Check System.

Procedure

1. Using Windows Explorer, navigate to the folder where mapvicheck.exe islocated.

2. Double-click mapvicheck.exe.

3. After the tool completes the scan, review the results under the Summary, Software,Hardware, and Drives tabs.

4. To save the results, select File > Save Log... from the menu.

5. Make any required changes to the system, and repeat system checks by clickingCheck System.

6. Address the problems, if any, and repeat system checks as needed.

7. Click Exit to close the tool.

Using PVI Checker in the command-line mode

About this taskYou can run PVI Checker software in command-line mode on Windows or Linux. Thecommand-line mode of the tool displays the results to the console or generates a results textfile.




Procedure

1. Open a Linux shell or Windows Command Prompt.

2. From the command-line, go to the directory where you saved the mapvicheckfile.

3. Run the system check by using one of the following commands:mapvicheck -m consolemapvicheck -m log -f results.txt

4. Review the results in the console window or in the results.txt file.

PVI Checker in the installer mode

When you run the Avaya MS installer, the installer automatically runs PVI Checker. PVIChecker runs silently during all installations. PVI Checker does not display any output unlessPVI Checker detects a warning or a failure. In case of a warning or failure system message,follow the on-screen instructions and see the GUI mode or the command-line mode PVIChecker instructions discussed earlier in this section.

Reviewing PVI Checker reports after installationAbout this taskAfter the installation is completed, you can review the results of the PVI Checker inspection inthe following ways:

Procedure

1. In the home directory of the user, check the maspviresult.xml file located in /root on Linux systems or in C:\Users\Administrator on Windows systems.

2. Use the log capture utility. Go to EM > Tools > Logcapture, and click download.The generated log archive contains the results in the PVI Check Results.htmfile.

3. View the results directly in EM. Go to EM > Tools > PVI Results.The results of the PVI Checker inspection run during the installation are shown onthis EM page.

PVI Checker


Note:You can only use Avaya MS EM after the installation of your system is complete.Avaya MS EM is an optional component which may not be installed on yoursystem.




Chapter 2: Installation

Installing Avaya MS on LinuxYou can install Avaya MS on servers that run the Linux operating system using one of thefollowing modes:

• The interactive command-line mode

• The silent install mode

Adopting products can automatically install Avaya MS as a component of the product solution.Additionally, the adopting products usually use the silent mode of Avaya MS installation. Thefollowing installation procedures are not necessary if the adopting product installs AvayaMS.

Installing Avaya MS on Linux using the interactive command-linemode

Before you beginComplete the procedures in System requirements and any restarts that the system preparationprocedures require before installing the software.

About this taskPerform the following procedure to interactively install Avaya MS in a Linux shell:

Procedure

1. Using a Linux shell on Avaya MS, change to root user by running the followingcommand:su -

2. Download the installer file to the server, or insert the Avaya MS installation DVDinto the DVD drive of the server.

3. Change the current directory to the location of the downloaded installer or the drivewhere Avaya MS installation DVD resides.The name of the installation file is in the following format:MediaServer_x.y.z.bbb_yyyy.mm.dd.bin


For example, MediaServer_7.5.0.231_2011.11.06.bin4. Apply executable permissions to the installer file:

chmod 755 filename5. Enter the following command to run the installer:

./filenamewhere filename is the Avaya MS installer.

6. Read the Introduction and press Enter.

7. Press Enter to read through the pages of the license agreement.To accept the terms of the license agreement, enter Y and press Enter.

8. To install Element Manager (EM) on Avaya MS, enter Y and press Enter.The EM option provides a Web-based management system for Avaya MS whenyou do not use another management system.The system prompts you for a Linux group name to use for EM login. Press Enterto accept the default name, or type another defined Linux group and pressEnter.

Important:The Linux group that you specify must contain users who can successfullyauthenticate against Secure Shell (SSH).

9. To begin the installation, choose the installation destination by specifying a locationor accepting the default location by pressing Enter.

Related topics:System requirements on page 5

Installing Avaya MS on Linux using the silent modeBefore you beginComplete the procedures in System requirements and any restarts that the system preparationprocedures require before installing the software.

About this taskThe silent mode of installing Avaya MS is typically used by adopting product installers thatinstall Avaya MS as a component of the product solution.

You can control the options for the silent installation by creating thesilent_install.properties file and then specifying this file in the command forexecuting the installer.

Installation



Perform the following procedure to install Avaya MS silently, with no user interaction:

Procedure

1. Download the installer file to the server or insert the Avaya MS installation DVD intothe DVD drive of the server.

2. Using a Linux shell, change the directory to the location of the downloaded installeror the drive where the Avaya MS installation DVD is located.The name of the installation file is in the following format:MediaServer_x.y.z.bbb_yyyy.mm.dd.binFor example, MediaServer_7.5.0.231_2011.11.06.bin.

3. Apply executable permissions to the installer file:chmod 755 filename

4. To modify the default Linux installation directory and restart options, use a text editorto create the file silent_install.properties with the following content:#Choose Options#--------------INSTALL_EMLITE_SILENT=nLINUX_GROUP=root

#Choose Install Folder#---------------------USER_INSTALL_DIR=/opt/avaya

5. In the Choose Options section, you can install the Avaya MS EM by settingINSTALL_EMLITE_SILENT=Y or bypass installation of EM by settingINSTALL_EMLITE_SILENT=N.Setting INSTALL_EMLITE_SILENT to Y provides a Web-based managementsystem for Avaya MS when another management system is not being used.Set the LINUX_GROUP to use for EM login.

Important:The Linux group that you specify must contain users who can successfullyauthenticate against Secure Shell (SSH).

6. In the Choose Install Folder section of the file, type a directory name to specifythe location to install Avaya MS.

7. Save your changes and exit the text editor.

8. Run the silent installation from a Linux shell by entering the following command:./filename -i silent -f location/silent_install.propertiesWhere filename is the Avaya MS installation file with a name similar toMediaServer_7.5.0.231_2010.11.06.bin and location is the directorywhere the silent_install.properties file that you want to use is located.

Installing Avaya MS on Linux


Tip:The installation is complete when the system CPU is idle. You can monitor thesystem CPU activity using a command like top in a Linux shell.

Note:If any errors occur during the silent mode installation, the system stops theinstallation and saves the errors to log files in the /var/log/mas/installdirectory.


Uninstalling Avaya MS from LinuxYou can use the following modes to remove Avaya MS from servers that run the Linuxoperating system:



When you uninstall the media server software, you can retain the system configuration andapplication data on the media server This data includes all configuration settings of themanagement system and any application-related data stored in the media server ContentStore, such as audio prompts or user data files. If you select the preserve data option duringthe uninstallation process, the data remains on the system. Any subsequent reinstallation ofthe media server software automatically uses your preserved settings and application data.

Adopting products can automatically uninstall Avaya MS. The adopting products usually usethe silent mode for uninstalling Avaya MS. The following uninstallation procedures are notnecessary if the adopting product uninstalls Avaya MS.

Uninstalling Avaya MS from Linux using the interactive command-line mode

Before you beginUninstall any Avaya MS packaged applications listed on the EM > Applications > PackageApplications page before you uninstall Avaya MS.

See the application documentation for the detailed uninstallation procedures. Ensure that youselect the preserve application data option, if applicable to your applications.

Installation



About this task

Important:You lose all your data if you do not accept the default action to preserve application data.

Perform the following procedure to interactively uninstall Avaya MS in a Linux shell:

Procedure

1. Locate the uninstaller. From a Linux shell, type:cd installpath/UninstallMediaServer

2. To run the uninstaller, type:./UninstallMediaServer

3. Press Enter to proceed with the uninstallation process.

4. Type Yes to preserve system configuration and application content data, or typeNo if you do not want to preserve system configuration and application content.

Important:You lose all your data if you do not accept the default action to Preserve SystemConfiguration and Application Content data.

5. To remove all your data type Yes and press Enter when the system displays thefollowing warning:WARNING: This will remove ALL System Configuration andprovisioned Service Data. Are you sure you want to continue?

6. If prompted, restart the system after the uninstallation process is complete.

Uninstalling Avaya MS from Linux using the silent modeBefore you beginYou must uninstall any Avaya MS packaged applications listed under EM > Applications >Package Applications before uninstalling Avaya MS.


About this task

Important:You lose all your data if you do not accept the action to preserve application data.

Adopting products use the silent mode to uninstall the Avaya MS component of the productsolution.

Uninstalling Avaya MS from Linux


Perform the following procedure to uninstall Avaya MS silently, with no user interaction:

Procedure

1. Locate the uninstaller. From a Linux shell, type:cd install path \UninstallMediaServer

2. To run the silent uninstaller, type one of the following commands.

Important:You lose all your data if you add the option -DREMOVE_USER_DATA=1 and donot use the default action to preserve system configuration and applicationcontent data.

To preserve data, type the following command:./UninstallMediaServer –i silentTo remove data, type the following command:./UninstallMediaServer -i silent -DREMOVE_USER_DATA=1As the uninstallation process is in the silent mode, you do not see anything on thescreen after this point.Wait for the uninstallation process to complete.

Tip:The uninstallation is complete when the system CPU is idle. You can monitor thesystem CPU activity using a command like top in a Linux shell.

Installing Avaya MS on WindowsThe installer provides the following installation modes for servers using the Microsoft Windowsoperating system:

• The Graphical User Interface (GUI) mode



Adopting products can automatically install Avaya MS. The adopting product uses the silentmode of Avaya MS installation. The following installation procedures are not necessary if theadopting product installs Avaya MS.

Installation



Installing Avaya MS on Windows using the GUI modeBefore you beginComplete the procedures in System requirements and any restarts that the system preparationprocedures require before installing the software.

About this taskPerform the following procedure to install Avaya MS using the Windows GUI:

Procedure

1. Download the installer software to the server, or insert the Avaya MS installationDVD into the DVD drive of the server.

2. Using Windows Explorer, locate the downloaded installer or the drive where theAvaya MS installation DVD resides.The name of the installation file is in the following format:MediaServer_x.y.z.bbb_yyyy.mm.dd.exeFor example, MediaServer_7.5.0.231_2011.11.06.exe.

3. Double-click the installation file.

4. In the Overview window, click Next.The system displays the License Agreement window.

5. Read the license agreement.

6. Select I accept the terms of the License Agreement.

7. Click Next.

8. (Optional) Select Install Element Manager.This option provides a Web-based management system for Avaya MS when youdo not use another management system.

9. Click Next.

10. In the Choose Install Folder window, click Install to install the software to the defaultfolder or a folder you specify.

11. Select the Restart option.

12. Click Done to restart the system.


Installing Avaya MS on Windows


Installing Avaya MS on Windows using the interactive command-line mode

Before you beginComplete the system preparation procedures and any restarts that the system preparationprocedures require before installing the software.

About this taskPerform the following procedure to interactively install Avaya MS using Windows CommandPrompt.

Procedure

1. Download the installer file to the server or insert the Avaya MS installation DVD intothe DVD drive of the server.

2. Using the Command Prompt window, locate the downloaded installer or the drivewhere the Avaya MS installation DVD resides.The name of the installation file is in the following format:MediaServer_x.y.z.bbb_yyyy.mm.dd.exeFor example, MediaServer_7.5.0.231_2011.11.06.exe.

3. Enter the following command:filename -i consolewhere filename is the Avaya MS installer.

Important:The system displays a new window during the installation. The installation takesa couple of minutes to return your command-line prompt. Do not close the windowthat the system displays.

4. Read the Introduction details and press Enter.

5. Press Enter to read through the pages of the license agreement.

6. To accept the terms of the license agreement, enter Y and press Enter.

7. (Optional) To install EM on Avaya MS, type Y and press Enter.The EM option provides a Web-based management system for Avaya MS whenyou do not use another management system.

8. To begin the installation, choose the installation destination by specifying a locationor accepting the default location by pressing Enter.

9. Restart the server after the installation process is complete.

Installation



Installing Avaya MS on Windows using the silent modeBefore you beginComplete the system preparation procedures and any restarts that the system preparationprocedures require before installing the software.

About this taskThe silent mode of installing Avaya MS is typically used by adopting product installers thatinstall Avaya MS as a component of the product solution.

You can control the options for the silent installation by creating thesilent_install.properties file and then specifying this file in the command forexecuting the installer.

Perform the following procedure to install Avaya MS silently, with no user interaction:

Procedure

1. Download the installer file to the server, or insert the Avaya MS installation DVDinto the DVD drive of the server.

2. Using the Windows Command Prompt , locate the downloaded installer or the drivewhere the Avaya MS installation DVD resides.The installation file has a name in the following format:MediaServer_x.y.z.bbb_yyyy.mm.dd.exeFor example, MediaServer_7.5.0.231_2011.11.06.exe.

3. To modify the default Windows installation directory and restart options, create thefile silent_install.properties with the following content, using a text editor:#Choose Options#--------------INSTALL_EMLITE_SILENT=n

#Choose Install Folder#---------------------USER_INSTALL_DIR=C:\\Program Files (x86)\\Avaya

#Restart System#--------------RESTART_NOW=1RESTART_LATER=0

4. In the Choose Options section of the file, you can install the Avaya MS EM bysetting INSTALL_EMLITE_SILENT=Y or bypass installation of EM by settingINSTALL_EMLITE_SILENT=N.Setting INSTALL_EMLITE_SILENT to Y provides a Web-based managementsystem for Avaya MS when another management system is not being used.

5. In the Choose Install Folder section of the file, type a directory name to specifythe location where you want to install Avaya MS.

Installing Avaya MS on Windows


Use double backslashes (\\) in the pathname because a single backslash needs tobe escaped with another backslash.

6. In the Restart Windows section of the file, select either RESTART_NOW orRESTART_LATER. Assign the selected option to 1 and the other to 0.

7. Save your changes and exit the text editor.

8. Using the Windows Command Prompt , type the following command to run theinstaller:

filename -i silent -f location\silent_install.propertieswhere filename is the Avaya MS installation file with a name similar toMediaServer_7.5.0.231_2010.11.06.exe and location is the directorywhere the silent_install.properties file is located.

Tip:

The installation is complete when the process with the same name as the installerexecutable, for example, MediaServer_7.5.0.231_2011.12.06.exe is nolonger listed as a process on the Windows Task Manager.

Important:If any errors occur during the silent mode installation, the system stops theinstallation and saves the errors to log files in the C:\MA_Logs directory.

Uninstalling Avaya MS from WindowsYou can use the following modes to uninstall Avaya MS from servers that run the Linuxoperating system:

• The Graphical User Interface (GUI) mode



When you uninstall the media server software, you can retain the system configuration andapplication data on the media server This data includes all configuration settings of themanagement system and any application-related data stored in the media server ContentStore, such as audio prompts or user data files. If you select the preserve data option duringthe uninstallation process, the data remains on the system. Any subsequent reinstallation ofthe media server software automatically uses your preserved settings and application data.

Installation



Adopting products can automatically uninstall Avaya MS. The adopting products usually usethe silent mode for uninstalling Avaya MS. The following uninstallation procedures are notnecessary if the adopting product uninstalls Avaya MS.

Uninstalling Avaya MS on Windows using the GUI modeBefore you beginYou must uninstall any Avaya MS packaged applications listed under EM > Applications >Package Applications before uninstalling Avaya MS.


About this task

Important:

You lose all your data if you do not accept the action to preserve application data.

Perform the following procedure to uninstall Avaya MS using the Windows GUI:

Procedure

1. To uninstall the Avaya MS installation, navigate to Start > Control Panel >Programs and Features, and then double-click Avaya Media Server from the listof programs.

2. Click Next to proceed with the uninstallation.

3. Select Remove to delete the system configuration and application content data orselect Preserve to retain the system configuration and application content data.

Important:You lose all your data if you do not accept the default action to preserve systemconfiguration and application content data.

4. Click Uninstall to proceed.

5. To remove all your data, click Uninstall when the system displays the followingwarning:WARNING: This will remove ALL System Configuration andprovisioned Service Data. Are you sure you want to continue?

6. If prompted by the system, restart the system after the uninstallation process iscomplete.

Uninstalling Avaya MS from Windows


Uninstalling Avaya MS from Windows using the interactivecommand-line mode

Before you beginYou must uninstall any Avaya MS packaged applications listed under EM > Applications >Package Applications before uninstalling Avaya MS. See the application documentation forthe detailed uninstallation procedures. Ensure that you select to preserve application data, ifapplicable to your applications.

About this task


Perform the following procedure to interactively uninstall Avaya MS in a Windows CommandPrompt:

Procedure

1. Locate the uninstaller. Using a Windows Command Prompt, type:cd install path\UninstallMediaServer

2. To run the uninstaller, type:UninstallMediaServer.exe –i console

3. Press Enter to proceed with the uninstallation process.

4. Enter Yes to preserve system configuration and application content data. Enter Noif you do not want to preserve system configuration and application content


5. To remove all your data type Yes and press Enter when the following warningappears:WARNING: This will remove ALL System Configuration andprovisioned Service Data. Are you sure you want to continue?

6. If prompted by the system, restart the system after the uninstallation process iscomplete.

Installation



Uninstalling Avaya MS from Windows in the silent modeBefore you beginYou must uninstall any Avaya MS packaged applications listed under EM > Applications >Package Applications before uninstalling Avaya MS.

See the application documentation for the detailed uninstallation procedures. Ensure that youselect to preserve application data, if applicable to your applications.

About this task


Adopting products use the silent mode to uninstall the Avaya MS component of the productsolution.

Perform the following procedure to uninstall Avaya MS silently, with no user interaction:

Procedure

1. Locate the uninstaller. From a Windows Command Prompt type:cd install path\UninstallMediaServer

2. To run the silent uninstaller, type one of the following commands:

Important:You lose all your data if you add the option -DREMOVE_USER_DATA=1 and donot use the default action to preserve system configuration and applicationcontent data.

To preserve data, type the following command:_UninstallMediaServer.exe –i silentTo remove data, type the following command:_UninstallMediaServer.exe -i silent -DREMOVE_USER_DATA=1As the uninstallation process is in the silent mode, you do not see anything on thescreen after this point.Wait for the uninstallation process to complete.

Tip:Avaya MS has finished uninstalling when UninstallMediaServer.exe is nolonger listed as a process on the Windows Task Manager.

3. Restart the system after the uninstallation completes.

Uninstalling Avaya MS from Windows


Installation



Chapter 3: Patches

Quick Fix Engineering overviewYou can use Quick Fix Engineering (QFE), also referred to as a Hot Fix, to apply an urgentpatch to Avaya MS systems that need an immediate fix before the next official service pack orrelease. QFE patches do not typically go through a formal product verification cycle.

Important:Apply a QFE patch only if Avaya recommends the patch for your installation.

Obtaining QFEAbout this taskDownload the required QFE patch to apply to the system.

Follow the download instructions that the Avaya technical support engineer provides.

Description of the patch toolUse the maspatch command-line tool to apply the QFE patches to the system.

You can use the tool to perform the following actions:

maspatch [apply | remove | info | list | fullinfo] [options]The following table lists the typical usage of the tool:

Command Descriptionmaspatch list [applied |available | all]

Lists the patches on the system.The available patches are present in theQFE directory. You can apply these patchesto the installed software when required.


Command Descriptionmaspatch info [patchname |applied | available | all] [-h]

Provides detailed information about a patchor list of patches.The -h option includes the detailed historyof the patch on the current system.

maspatch apply patchname [-v] Applies the specified patch to the system.Apply patches in numerical order.You can specify all as the patch name toapply all available patches.The -v option specifies verbose output.The verbose output is always recorded inthe history log.

maspatch remove patchname [-v] Removes the specified patch from thesystem.Remove patches in reverse numericalorder.The -v option specifies verbose output.The verbose output is always recorded tothe history log.

Installing a QFE patchBefore you beginBefore proceeding with the QFE installation, ensure that you:

• Back up your system.

In case of unforeseen problems, you can use the backup to restore your system to theprevious configuration.

• Install the latest software version of Avaya MS.• Install any previous QFE patches for the latest software version.• Apply a patch to one node at a time while other nodes handle service requests in a cluster

configuration.• When patching High Availability server pairs, apply the QFE to the Backup server first

and then apply the QFE to the Active server.

About this taskPerform the following procedures to install a QFE patch to the system. When possible, applypatches during a maintenance window:

You must apply QFE patches in sequential, numerical order because new patches depend onpreviously installed QFE patches. For example, you must install QFE-platform-7.5.0.230-0001before you install QFE-platform-7.5.0.230-0002.

Patches



Note:Some steps in the following procedure are specific to the Avaya MS Element Manager (EM)management system. If you are using a different management system, the procedure isdifferent.

Procedure

1. Transfer the required QFE to the target server, and place the QFE patch in the QFEdirectory for the installation:

• Linux: install path/ma/MAS/QFE• Windows: install path/multimedia-applications/MAS/QFE

2. Open EM for the target server.

3. To check for active sessions on the server, navigate to EM > System Status >Monitoring > Active Sessions.

4. If the server does not have active sessions, go to Step 5. If the server has activesessions, proceed with the following steps:

a. Navigate to EM > System Status > Element Status > More Actions >Pending Lock.

b. Click Confirm.c. Wait for the active sessions to end. If you continue before all active sessions

end, then the system ends the remaining active sessions.

5. Select EM > System Status > Element Status > More Actions > Lock.

6. Click Confirm.

7. (Optional) To reduce the time required to apply multiple QFEs, stop the mediaserver prior to applying the patches. When the media server is stopped first, thesystem is not stopped and restarted by the maspatch tool in-between each QFEapplication.

a. Select EM > System Status > Element Status > More Actions > Stop.b. Click Confirm.


9. On Linux, change to root user by running the following command:su —

10. Enter the following command to get the actual name of the patch to be applied:maspatch list allRemember the name of the patch listed under the QFE column for use in the nextstep. This name can be different from the file name.

11. Enter the following command to apply a single patch:maspatch apply patchname

Installing a QFE patch


To apply all available patches enter the following command:maspatch apply all

12. Press y to continue.

13. After the patch application is complete, open EM and navigate to EM > SystemConfiguration > Software Inventory.

14. Verify whether the patch version listed in the Patch Level column is correct.

15. (Optional) If you stopped the media server in Step 6, then start Avaya MS with thefollowing steps:

a. Navigate to EM > System Status > Element Status > More Actions >Start.

b. Click Confirm.

16. Select EM > System Status > Element Status > More Actions > Unlock.

17. Click Confirm.

18. Check for any service-impacting alarms and perform an appropriate test of thesystem, for example, place a call to the application.

Removing a QFE patchBefore you beginRemove a QFE from clusters one node at a time so that other nodes in the cluster can provideservice during the procedure.

For High Availability server pairs remove the QFE from the Backup server first and then removethe QFE from the Active server.

About this taskRemove a QFE patch to revert the system to the state before you installed the patch. Removepatches during a maintenance window when possible.

Perform the following procedures to remove a QFE patch from the system:

Important:You must remove QFE patches in reverse, numerical order. For example, if QFE-platform-7.5.0.230-0001 and QFE-platform-7.5.0.230-0002 are both installed on yoursystem, you must remove QFE-platform-7.5.0.230-0002 before you remove QFE-platform-7.5.0.230-0001.

Patches



Note:Some steps in the following procedure are specific to the Avaya MS EM managementsystem. If you are using a different management system, the procedure is different.

Procedure

1. Open EM that manages the server to be patched.

2. Navigate to EM > System Status > Monitoring > Active Sessions to check foractive sessions on the server.

3. If there are no active sessions go to Step 4. If there are active sessions, proceedwith the following steps:





5. Click Confirm.

6. Select EM > System Status > Element Status > More Actions > Stop.

7. Click Confirm.


9. On Linux, change to root user by running the following command:su —

10. Enter the following command to get the actual name of the patch to remove:maspatch list allRemember the name of the patch listed under the QFE column for use in the nextstep. This name can be different from the file name.

11. Enter the following command:maspatch remove patchname

12. After the patch removal is complete, open the EM and navigate to EM > SystemConfiguration > Software Inventory.

13. Verify whether the patch version listed in the Patch Level column is correct.

14. Select EM > System Status > Element Status > More Actions > Start.

15. Click Confirm.


17. Click Confirm.

Removing a QFE patch



Managing QFEs on High Availability serversWhen patching High Availability server pairs, first apply or remove QFEs for the backup serverand then apply or remove QFEs for the active server.

Managing QFEs in a clusterTo offer continuous service during the QFE maintenance, you must patch each server that ispart of a cluster one at a time.

Patches



Chapter 4: Service Packs

Installing a service packBefore you beginBefore proceeding with the software upgrade, ensure that you:

• Obtain the service pack installer.

Avaya delivers the latest software release on DVD to customers.• Back up your system.

In case of unforeseen problems during the installation, you can use the backup to restoreyour system to the previous configuration.

• Apply the service pack to one node at a time in a cluster configuration while the othernodes in the cluster maintain service.

• Apply the service pack for the standby server first and then apply the service pack for theactive server when upgrading High Availability server pairs.

About this taskService pack upgrades are fully automated and preserve all your system configuration andapplication data. If errors occur during the upgrade, the software is rolled back to the previouslyinstalled version.

Perform service pack installations during scheduled maintenance times.

Perform the following procedure to upgrade your system to the latest 7.5 software release:

Note:Some steps in the following procedure are specific to the Avaya MS Element Manager (EM).If you are using a different management system, your actions will be different for thosesteps.

Procedure

1. Open EM that manages the server to be upgraded.




a. Navigate to System Status > Element Status > More Actions > PendingLock.




5. Click Confirm.


7. Click Confirm.

8. Insert the maintenance release DVD into the DVD drive.

9. Navigate the file system to locate the drive where the service pack installerresides.

10. Run the installer:

• Linux: ./MediaServer_7.5.0.99_2011.11.06.bin• Windows: Double-click MediaServer_7.5.0.99_2011.11.06.exe

Tip:You can use either the GUI, command-line, or silent installer modes that AvayaMS provides for the upgrade.

For more details, see Installation.

11. When the system displays the Upgrade Introduction window, select the option toinstall the upgrade.

12. After the system completes the software upgrade, the installer prompts you torestart the system. If you are also upgrading applications at the same time, selectNo to restart later. Otherwise, select Yes to restart now.

13. Follow the prompts to exit the upgrade installer. Wait for the restart to complete.

14. Log in to Avaya MS EM.

15. Update each application by running the installation for each application.For application upgrade procedures, see application documentation.

16. Open EM, and navigate to EM > Tools > Software Inventory.

17. Verify the software versions listed are correct.

18. If at any time the system prompted you for a restart but you deferred the restart,restart your system now.

19. After the system restarts, open EM.

20. Select EM > System Status > Element Status > More Actions > Start.

21. Click Confirm.

Service Packs




23. Click Confirm.


Related topics:Installation on page 23

Removing a service packBefore you beginBefore proceeding with the software removal, ensure that you:

• Obtain the installer for the earlier software release.

You must reinstall the earlier software.• Back up your system.

In case of unforeseen problems during the downgrade, you can use the backup to restoreyour system to the previous configuration.

• Remove service packs one node at a time in a cluster configuration. The other nodes inthe cluster maintain service.

• Remove the service pack from the standby server first and then remove the service packfrom the active server when upgrading High Availability server pairs.

About this taskThe service pack removal procedure downgrades your software to the previous softwareversion.

If you follow this procedure, you do not have to reconfigure or reprovision the system. Allsystem configuration and application data is preserved.

Remove service packs during scheduled maintenance times.

Perform the following procedure to remove an installed service pack from your system:

Important:If you have installed service pack version 7.5.0.1140 or higher, you cannot downgrade thesystem to a build version lower than 7.5.0.1140. You can still revert to an older version byuninstalling the current version without preserving data, installing the version lower than7.5.0.1140, and restoring the saved backed-up data from the older version.

Removing a service pack


Note:Some of the steps in this procedure are specific to the Avaya MS EM. If you are using adifferent management system, your actions will be different for those steps.

Procedure

1. Open EM that manages the server to be downgraded.







5. Click Confirm.


7. Click Confirm.

8. You must uninstall any Avaya MS packaged applications listed under EM >Applications > Package Applications before uninstalling Avaya MS.See the application documentation for the detailed uninstallation procedures.Ensure that you select the option to preserve system configuration and applicationcontent data.

Important:You lose all your data if you do not accept the default action to preserveapplication data.

9. Uninstall the current Avaya MS installation, but ensure that you select the option topreserve system configuration and application content data.


10. Uninstall your media server software:

• Linux: In a Linux shell type: install path/UninstallMediaServer/UninstallMediaServer

Service Packs



• Windows: Go to Start > Control Panel > Programs > Programs andFeatures, and double-click Avaya Media Server in the list of programs to startthe uninstaller.

11. If prompted, restart the system after the uninstallation process is complete.

12. Navigate the file system to locate where the installer for the earlier version of AvayaMS resides.

13. Run the installer. For example:

• Linux: ./MediaServer_7.5.0.88_2011.11.06.bin• Windows: Double-click MediaServer_7.5.0.88_2011.11.06.exe

Tip:You can use any of the Installer modes that Avaya MS provides for the upgrade:GUI, command-line, or silent. For details, see Installation.

14. Read the introduction and press Enter.

15. Press Enter to read through the pages of the license agreement.To accept the terms of the license agreement, enter Y and press Enter.

The installer automatically detects the preserved configuration and applicationcontent data. As a result, the system does not prompt you to choose an installationlocation or to reselect any other options. The installer uses the original location andselections.

16. After the software installation completes, the system prompts you to restart yoursystem. If you are installing other applications at the same time, select No to restartlater. Otherwise, select Yes to restart now.

17. Follow the prompts to exit the installer. Wait for the restart to complete.

18. Install each application by running the installation for each application.For application installation procedures, see application documentation.

19. Open EM and navigate to EM > Tools > Software Inventory.

20. Verify whether the software versions listed are correct.

21. If at any time the system prompted you for a restart but you deferred the restart,restart your system now.




Removing a service pack


Managing service packs on High Availability serversWhen patching High Availability server pairs, follow the Service Pack installation or removalprocedures in the following order: Apply or remove the Service Pack for the Standby serverfirst and then apply or remove the Service Pack for the Active server.

Managing service packs in a clusterYou do not need to break up a cluster to install or remove a service pack. Work on one clusternode at a time to avoid service interruption. If the procedure fails on one server in a cluster, allservers in this cluster must revert to the same release version. However, other Avaya MSclusters do not need to be on the same software release version.

Service Packs



Chapter 5: Upgrade to Avaya MS 7.5

Upgrade introductionYou can upgrade a media server to Release 7.5 provided your current system is listed as asupported upgrade scenario in the following table:

Table 1: Supported upgrades to Avaya MS 7.5

Current software Upgrades supported from these versionsAvaya Media Server 7.0 AMS 7.0.0.249 (MR1)

AMS 7.0.0.363 (FP1 Beta)AMS 7.0.0.389 (FP1 GA)AMS 7.0.0.466 (FP1 SP1)AMS 7.0.0.623 (FP1 SP2)

Avaya Media Server Application Platform7.0

AMS 7.0.0.249 (MR1)AMS 7.0.0.363 (FP1 Beta)AMS 7.0.0.389 (FP1 GA)AMS 7.0.0.466 (FP1 SP1)AMS 7.0.0.623 (FP1 SP2)

Upgrades are only supported in cases where the source and target operating systems are thesame.

In multi-server (cluster) Avaya MS deployments, you can maintain continuous access to AvayaMS services during upgrades by dividing the cluster and upgrading the cluster in parts. Forstandalone installations, service is unavailable during the upgrade.

Prior to upgrading an Avaya MS, set the operational state to Pending Lock using EM. Thepurpose of placing Avaya MS in the Pending Lock state is to ensure the system rejects all newservice requests by this Avaya MS and routes the requests to another Avaya MS in the clusteras defined by the routing selections in the network. On Avaya MS that you are upgrading, youcan allow the existing traffic to clear on its own. Use the EM Active Sessions page to monitorthe active traffic.

When the Avaya MS that you have upgraded has no active sessions, set the operational stateto Locked. When the upgrade is complete, Avaya MS is restarted and Unlocked so that is ableto process incoming service requests.

Perform upgrades only during the maintenance window or at some other off peak-usage time.Placing Avaya MS in the Pending Lock state, an hour prior to the actual upgrade maintenance


window, ensures that a minimum number of user sessions, if any, are present on the upgradetarget when the server is actually upgraded during the maintenance window.

The masupgrade tool converts and carries forward the configuration and application data. Thetool converts backup files from current installation and restores the files to the newinstallation.

Note:You cannot perform a direct restore of the earlier backup files to a newer system using thenormal backup and restore procedures.

If errors occur during the upgrade, rollback to the previously installed version. For details, seeRollback of Avaya MS 7.5 upgrade.

Important:

• If the upgrade fails on a server in a cluster, all servers in that cluster must be rolled backto the same release version. However, other Avaya MS clusters do not need to be on thesame software release version because clusters can be upgraded independently of eachother.

Tip:When clearing a configuration parameter, if the management system requires a value, entera space character for the parameter.

Related topics:Rollback of Avaya MS 7.5 upgrade on page 61

Prerequisites for Avaya MS 7.5 upgrade• Prior to attempting the upgrade to Avaya MS 7.5, ensure that the current Avaya MS

servers are on release 7.0. You can check the installed version using EM from eitherTools > Software Inventory or System Configuration > Software Inventory,depending on the release you have installed.

• Ensure the minimum hardware requirements are met. For details, see Systemrequirements.

• Ensure the minimum software requirements, including Windows Server 2008 R2 or RedHat Enterprise Linux 5.x operating system. For details, see System requirements.

• Ensure you have the new Avaya MS 7.5 license key to enable all the desired applications.The previous license is not valid on the upgraded server.

• Ensure the source and the target operating systems are the same. The system onlysupports upgrades in cases where the source and target operating systems are thesame.

Upgrade to Avaya MS 7.5




Avaya MS upgrade overviewThe steps you perform to upgrade depend on whether you have a cluster of media servers ora stand-alone media server. The following section outlines the upgrade steps in eachscenario.

High-level task for upgrading a multi-server Avaya MS clusterAbout this taskThe following steps describe how to upgrade service clusters with two or more Avaya MSnodes.

• Create backups of each node.• Set the servers through a progression of Pending Lock, Lock, and Stopped states.• Separate a multi-server cluster into two parts if you want continuous service, and divert

traffic to the part of the cluster that remains active, while upgrading the other part.• Upgrade one server at a time in the inactive part following the single server upgrade

procedure.• Swap traffic from the active servers to the newly upgraded part of the cluster.• Upgrade one server at a time in the inactive part following the single server upgrade

procedure.• Reform the fully upgraded cluster.• Back up the new system.

High-level task for upgrading a single-server Avaya MS serverAbout this taskThe following steps describe how to upgrade a single Avaya MS server to Avaya MS 7.5.

• Back up the server data.• Set the server through a progression of Pending Lock, Lock, and Stopped states.• Uninstall media server and any applications.• Install the new software.

Avaya MS upgrade overview


• Use the backup files with the masupgrade tool to convert and restore your data for thenew installation.

• Apply the new license key.• Verify the system is functional with no unexpected alarms.• Back up the new system.

Performing a backupAbout this taskCreate a backup of the System Configuration, Network Data, and Application data for eachAvaya MS. The following is a quick reference to the backup procedure that you can use duringthe upgrade procedures. For more information on backup and restore, see ImplementingAvaya Media Server 7.5.

Important:To perform a rollback, you must back up the Network Data type.

Procedure

1. Log in to Avaya MS to upgrade, using the administrator account.

2. Log in to EM.

3. Navigate to EM > Tools > Backup and Restore > Backup Tasks.

4. Create or select an existing backup task which includes System Configuration,Application Content, and Network Data backup types.

5. Click Run Now.

6. Monitor the Backup and Restore History Log at EM > Tools > Backup andRestore > History Log.Once complete, the log shows a completed backup task entry.

7. Confirm the backup files were saved to their desired FTP location or local defaultdestination.There is one file for each backup type for a total of two backup files. If you are usingan FTP location, skip Step 8.

8. If you are using a local destination and want to re-image the operating system, youmust move the backup files to a new folder, for example, D:\MSbackup or ~/MSBackups. You can find the local backups in:

• Linux: install path/ma/MAS/platdata/EAM/Backups• Windows: install path\Multimedia_Applications\MAS\platdata\EAM\Backups




Important:If you choose to re-image the operating system, ensure you transfer the backupfiles off the server for safe keeping.

Upgrade a multi-server Avaya MS clusterThis section only applies to service clusters with two or more Avaya MS nodes.

Separation of a multi-server Avaya MS clusterYou must divide Avaya MS clusters into two parts in order to proceed with the upgrade andsimultaneously maintain service. This section describes the steps to divide the cluster, thesequence for upgrading each node, and the steps for reforming the cluster after theupgrades.

The Primary and Secondary nodes in a cluster require special consideration during theupgrade, since these nodes have master Content Store components on them serving the entirecluster’s data needs.

The Primary and Secondary node Content Stores are synchronized, equal peers containingthe user application data. The other nodes reference the masters for application data whenneeded. During the upgrade, the two Content Stores are separated from each other andindependently upgraded in a way that provides continuous access to the data during theupgrade. This separation allows service to continue uninterrupted.

Figure 1 shows a cluster with Avaya MS nodes A, B, C, and D, where the Master ContentStores are on Avaya MS A and Avaya MS B. Avaya MS C and Avaya MS D do not have activeContent Stores. Figure 1 illustrates how the cluster is divided for the upgrade. The proceduremaintains service during the upgrade maintenance window using separate parts of the cluster.As you upgrade one part of the cluster, the other part remains in service.

Upgrade a multi-server Avaya MS cluster


Figure 2: The cluster separation sequence for upgrades

Upgrading a multi-server Avaya MS clusterAbout this taskThe following procedure describes how to upgrade service clusters with two or more AvayaMS nodes while maintaining service.

Important:You must not make any provisioning changes during the upgrade process. You must planthe upgrade during scheduled maintenance windows.

See Figure 1 to understand the definitions of Avaya MS A, B, C, and D.

Note:Some steps in the following procedure are specific to EM management system. If you areusing a different management system, your actions will be different for those steps.

Procedure

1. Divert all traffic to Avaya MS B.




Avaya MS B continues to provide service while you upgrade the other servers.

2. Set each Avaya MS server to the Pending Lock state, except Avaya MS B, byperforming the following step:


b. Click Confirm.

3. To monitor active sessions, click System Status > Monitoring > ActiveSessions on each pending lock server.

4. When existing sessions end, lock Avaya MS by performing the following steps:

a. Navigate to EM > System Status > Element Status > More Actions >Lock.

b. Click Confirm.

5. Remove the Secondary Avaya MS B from the cluster, making the Secondary AvayaMS B a Primary standalone node, by performing the following steps on Avaya MSB:

a. Navigate to EM > Cluster Configuration > Server Designation > LocalServer > Role.

b. Select Primary as the role.c. Scroll down to Server Designation, select each of the nodes in the list, and

click Remove.d. Scroll down to Replication Account and clear Enable Replication

Account.e. Click Save.f. Click Confirm.

6. Stop all Avaya MS nodes, except Avaya MS B, by performing the following steps:

a. Navigate to EM > System Status > Element Status > Stop.b. Click Confirm.

7. Perform the steps of Upgrading a single Avaya MS server for all the stopped serversexcept Avaya MS B.After you complete that procedure, continue with Step 8.

8. After each node (except Avaya MS B) is upgraded, join Avaya MS A and the othernodes back together in a cluster, setting Avaya MS A as the Primary node and allthe other nodes as Standard nodes .On Avaya MS A, navigate to EM > ClusterConfiguration > Server Designation.

9. On Avaya MS A, set the Local Server > Role to Primary.

10. Repeat the following steps to add each server, except Avaya MS A and Avaya MSB, to the servers list on Avaya MS A:

a. In Server Designation on Avaya MS A, click Add to add one of the otherservers.

Upgrade a multi-server Avaya MS cluster


b. Enter values in Server Address and Server UUID of one of the otherservers.Copy and paste the address and UUID from the Server Designation screen ofeach server.

11. Repeat the following steps for each of the other servers, except Avaya MS A andAvaya MS B.

a. Navigate to EM > Cluster Configuration > Server Designation.b. Set the Local Server > Role to Standard.c. In Server Designation, enter values in Primary Server UUID and Primary

Server IP Address.d. Select Enable Replication Account.e. Enter the same username and password as entered on the Primary Server.f. Click Save.g. Click Confirm.

This part of the cluster, which includes Avaya MS A, is now upgraded and ready toreceive traffic.

12. Divert traffic from Avaya MS B to this new cluster to maintain continuous serviceduring the upgrade.

13. Set Avaya MS B to Pending Lock by performing the following steps:


b. Click Confirm.

14. To monitor active sessions, click System Status > Monitoring > ActiveSessions on each pending lock server.

15. When existing sessions end, lock Avaya MS by performing the following steps:


b. Click Confirm.

16. Perform the steps of Upgrading a single Avaya MS server for only Avaya MS B.After you complete that procedure, continue with Step 17.

17. Add Avaya MS B back into the cluster of upgraded servers by performing thefollowing steps:

a. Navigate to EM > Cluster Configuration > Server Designation on Avaya MSB.

b. Set the Local Server > Role to Secondary.c. In Server Designation, enter values in Primary Server UUID and Primary

Server IP Address.d. Select Enable Replication Account and enter the same username and

password as entered on the Primary server.




e. Click Save.f. Click Confirm.

18. On Primary Avaya MS A, navigate to EM > System Status > Cluster Status, andverify all the nodes of the cluster are listed and have the correct role.Synchronization alarms appear on the Primary and Secondary servers while theContent Stores synchronize your application data.

19. If you routed any traffic away from Avaya MS B, restore that routing.All Avaya MS nodes in the cluster are ready to receive traffic and you can restoreany external routing to the same state as before the upgrade.

20. Verify the success of the installation. Check for any service-impacting alarms andperform a test of the system. For example, place a call to an application, and verifyall the nodes in the cluster receive calls.Your cluster upgrade is complete.

21. To save your newly configured and tested installation, you must now back up yourAvaya MS 7.5 cluster by performing the following steps:

a. Log in to EM.b. Navigate to EM > Tools > Backup and Restore > Backup Tasks.c. Create or select a backup task for all the data types.d. Click Run Now.e. Click Confirm.f. Repeat the backup procedure for each Avaya MS server in the cluster.

Related topics:Upgrading a single Avaya MS on page 57

Upgrading a single Avaya MS About this taskThe following procedure describes how to upgrade a single Avaya MS to Avaya MS 7.5.

Important:

• Ensure you back up the existing server before proceeding with the upgrade.• Do not make any provisioning changes on the provisioning client during the rollback

process.

You must plan your upgrade during scheduled maintenance windows.

Upgrading a single Avaya MS



Procedure

1. Skip to Step 2 if you are executing this procedure as part of a multi-server clusterupgrade. For stand-alone server upgrades, perform the following steps:

a. To set Avaya MS to Pending Lock in EM, navigate to EM > System Status >Element Status > More Actions > Pending Lock.

b. Click Confirm.c. To monitor active sessions, click System Status > Monitoring > Active

Sessions.Moving to the Lock state ends any active sessions.

d. To lock Avaya MS, when existing sessions have ended, click System Status> Element Status > More Actions > Lock.

e. Click Confirm.f. To stop Avaya MS, click System Status > Element Status > Stop.g. Click Confirm.

2. (Optional) Re-image to a new OS.All data on a re-imaged server is lost during the new OS install. If you re-image theOS, skip Step 3 and proceed to Step 4 to install the new Avaya MS.

3. Uninstall the current Avaya MS installation but DO NOT preserve data. SelectRemove.To select an appropriate uninstallation method, see uninstallation methods inInstallation and proceed to Step 4.

4. You are now ready to install the new Avaya MS.To select an appropriate installation method, see Installation and proceed to Step5.

5. After the installation is complete, log in to the new Avaya MS EM.

Note:If Security Alert dialog boxes appear in your browser, click Accept to proceed.

6. Verify System Configuration and Application Content backup files saved earlier areavailable on the server.If not, transfer the backups created earlier to this server.

7. To stop Avaya MS from the Avaya MS EM, click System Status > ElementStatus > Stop.

8. Click Confirm.




9. From the command-line, change to the directory where you have saved the backupfiles.You can identify the System Configuration backup file by Task0_ in the filename,for example, backupTask0_MyHostname_2010_06_30_0_9_17.zip

10. Perform System Configuration Data upgrade from the command-line by entering:masupgrade <backuptask>0_<host_date>.zip

Important:Backup data is not portable from one server to another. If you need to replace aserver, you must configure the server with the same installation path, IP address,and hostname so that the data is compatible.

11. Enter Y to stop all the Avaya MS services at the prompt.

12. In the same directory, you can identify the Application Content backup file by Task1_in the filename, for example, backupTask1_MyHostname2010_06_30_0_9_17.zip

13. Perform Application Content upgrade from the command-line by entering:masupgrade <backuptask>1_<host__date>.zip

14. Enter Y to stop all the Avaya MS services when prompted.

Note:The time to complete the application content upgrade depends on the amount ofapplication data in the backup file.

15. After the upgrade is complete, close the Windows Command Prompt or Linuxshell.

16. In Avaya MS EM, navigate to Licensing > General Settings.

17. Select the appropriate Licensing type for your installation and then copy and pastethe new Avaya MS 7.5 License key for the Avaya MS platform and applicationservices into the Keys field.

Important:You cannot use the earlier license key.

18. Click Save.

19. Click Confirm.

20. In Avaya MS EM, navigate to System Configuration > Signaling Protocols > SIP> Nodes and Routes.

21. If the Routes list is empty, then add an appropriate Trusted Nodes if no trusted nodeis present, and then click Add… followed by Save to add a route.

Upgrading a single Avaya MS


If the nodes are clustered with replication enabled, then you must perform this steponly on the Primary server because the configuration will be replicated to all othernodes connected to the Primary node.

Note:The system raises an alarm if you do not configure a SIP Proxy Route.

22. On Avaya MS, CCXML and VoiceXML applications are disabled by default. If youare upgrading from Avaya Media Server Application Platform 7.0 and if you areusing VXML or CXML applications, then you must perform the following steps toactivate VXML and CCXML functionality.

a. Navigate to EM > System Configuration > Server Profile.b. Select the additional application interpreters required.c. Click Save.

23. To start Avaya MS, use the following steps:

a. Navigate to EM > System Status > Element Status > Start.b. Click Confirm.

Skip the remaining steps if you are working on a cluster upgrade.

24. Re-enable traffic to this Avaya MS server if this is a standalone Avaya MS serverupgrade.

25. Verify the success of the installation. Check for any service-impacting alarms andperform an appropriate test of the system, for example, place a call to anapplication.The upgrade procedure is for a single Avaya MS server. To upgrade an Avaya MScluster, return to the cluster upgrade procedure where you left off.

26. Back up your new Avaya MS 7.5 server to save the new configured and testedinstallation by performing the following steps:

a. Log in to EM.b. Navigate to EM > Tools > Backup and Restore > Backup Tasks.c. Create or select a backup task for all the data types.d. Click Run Now.e. Click Confirm.

Note:Running masupgrade tool with a backup file from an earlier release as input,upgrades all the application data so the data is ready to use. There are new andupdated configuration options in this release. To ensure all new options are filledin, see Implementing and Administering Avaya Media Server 7.5. Configure theareas that the system does not upgrade automatically and which apply to yourinstallation. Many systems might not need this additional configuration.





Rollback of Avaya MS 7.5 upgradeIf the process of upgrading a server from Avaya MS 7.0 to Avaya MS 7.5 fails, use the followingprocedure to rollback the server to the previous Avaya MS 7.0 release.

Important:Rollback all the servers in the same cluster to the previous release. Independent clustersare not required to be on the same release version.

The procedure requires a complete uninstallation of Avaya MS 7.5 and reinstallation of theWindows or Linux OS and Avaya MS 7.0. After the reinstallation, use the saved Avaya MS 7.0backups to restore the system configuration and data.

Performing a cluster rollbackThe following procedure describes how to roll back a cluster of two or more Avaya MS nodesto release 7.0.

Before you beginYou need Avaya MS 7.0 license keys and the earlier backup files from Avaya MS 7.0 for SystemConfiguration, Network Data, and Application Content data for each rolled back server.

About this task

Important:Skip this section if you are upgrading a standalone/simplex Avaya MS server.

If you have a cluster, follow the same upgrade procedure to break up the cluster for continuedservice as with the upgrade. Avaya MS clusters are divided into two parts in order to proceedwith the rollback. This section provides the steps to divide the cluster, the sequence for rollingback each node, and the steps to reform the cluster after the rollback.

Important:

• The system reverts any data that you provision or alter after the upgrade, to Avaya MS7.0 backup file state.

• Do not make any provisioning changes on the provisioning client during the rollbackprocess.

Rollback of Avaya MS 7.5 upgrade


See Figure 1 to understand the definitions of Avaya MS A, Avaya MS B, Avaya MS C, andAvaya MS D.

Note:Some steps in the following procedure are specific to Avaya MS EM. If you are using adifferent management system, your actions will be different for those steps.

Procedure

1. Divert all traffic to Avaya MS B. Avaya MS B continues to provide service while theother servers roll back to the previous release.

2. Set each Avaya MS server to the Pending Lock state, except Avaya MS B, byperforming the following steps:


b. Click Confirm3. To monitor active sessions, click System Status > Monitoring > Active

Sessions on each pending lock server.

4. When existing sessions have ended, lock the MS by performing the following steps:


b. Click Confirm.

5. Remove the Secondary Avaya MS B from the cluster, making Secondary AvayaMS B a Primary standalone node, by performing the following steps on Avaya MSB:

a. Navigate to EM > Cluster Configuration > Server Designation > LocalServer > Role.

b. Select Primary as the role.c. Scroll down to Server Designation, select each node in the list, and click

Remove.d. Scroll down to Replication Account and clear Enable Replication

Account.e. Click Save.f. click Confirm.

6. Stop all Avaya MS nodes, except Avaya MS B, by performing the following steps:

a. Navigate to EM > System Status > Element Status > Stop.b. Click Confirm.

7. Perform the steps in performing a single server rollback for all stopped serversexcept Avaya MS B.After completing that procedure, continue with Step 8.

8. After each node (except Avaya MS B) is rolled back, join Avaya MS A and the othernodes back together in a cluster, setting Avaya MS A as the Primary node and all




the other nodes as Standard nodes. On Avaya MS A, navigate to EM > ClusterConfiguration > Server Designation.

9. On Avaya MS A, set the Local Server > Role to Primary.

10. Repeat the following steps to add each server, except Avaya MS A and Avaya MSB, to the servers list on Avaya MS A:

a. In Server Designation on Avaya MS A, click Add to add one of the otherservers.

b. Enter values in Server Address and Server UUID of one of the otherservers.Copy paste the address and UUID from the Server Designation screen of eachserver.

11. Repeat the following steps for each of the other servers except Avaya MS A andAvaya MS B.

a. Navigate to EM > Cluster Configuration > Server Designation.b. Set the Local Server > Role to Standard.c. In Server Designation, enter values in Primary Server UUID and Primary

Server IP Address.d. Select Enable Replication Account.e. Enter the same username and password as entered on the Primary Server.f. Click Save.g. Click Confirm

This part of the cluster, which includes Avaya MS A, is now rolled back and readyto receive traffic.

12. Divert traffic from Avaya MS B to this new cluster to maintain continuous serviceduring the rollback.

13. After the traffic is diverted, set Avaya MS B to Pending Lock by performing thefollowing steps:


b. Click Confirm.

14. To monitor active sessions, click System Status > Monitoring > ActiveSessions on each pending locked server.

15. When existing sessions have ended, lock Avaya MS B by performing the followingsteps:


b. Click Confirm.

16. Perform the steps in Performing a single server rollback for only Avaya MS B.After completing that procedure, continue with Step 17.



17. Add Avaya MS B back into the cluster of rolled back servers by performing thefollowing steps:

a. Navigate to EM > Cluster Configuration > Server Designation.b. Set the Local Server > Role to Secondary.c. In Server Designation, enter values in Primary Server UUID and Primary

Server IP Address.d. Select Enable Replication Account and enter the same username and

password as entered on the Primary server.e. Click Save.f. Click Confirm.

18. On Primary Avaya MS A, navigate to EM > System Status > Cluster Status andverify all the nodes of the cluster are listed and have the proper role.Synchronization alarms appear on the Primary and Secondary servers while theContent Stores synchronize your application data.

19. If traffic is routed away from Avaya MS B, restore that traffic routing to Avaya MSB.All Avaya MS nodes in the cluster are ready to receive traffic and any externalrouting can be restored to the original state.

20. Verify the success of the installation. Check for any service-impacting alarms andperform an appropriate test of the system, for example, place a call to an application,and verify all the nodes in the cluster receive calls.Your cluster rollback is complete.

Related topics:Performing a single server rollback on page 64

Performing a single server rollbackBefore you beginYou need Avaya MS 7.0 license keys and the earlier backup files from Avaya MS 7.0 for SystemConfiguration, Network Data, and Application Content data for each server being rolledback.

About this taskThe following procedure describes how to roll back a single Avaya MS 7.5 node to release7.0.

Important:The system reverts any data that you provision or alter after the upgrade, to Avaya MS 7.0backup file state.




Do not make any provisioning changes on the provisioning client during the rollbackprocess.


Procedure

1. Skip to Step 2 if you are executing this procedure as part of a multi-server clusterrollback.For stand-alone server rollbacks, perform the following steps:

a. To set Avaya MS to Pending Lock in EM, navigate to System Status > ElementStatus > More Actions > Pending Lock.Click Confirm.

b. Moving to the Lock state ends any active sessions.c. To monitor active sessions, click System Status > Monitoring > Active

Sessions. To lock Avaya MS when existing sessions have ended, navigate toSystem Status > Element Status > More Actions > Lock.

d. Click Confirm.e. To stop Avaya MS, navigate to System Status > Element Status > Stop.f. Click Confirm.

2. Uninstall the current Avaya MS installation but DO NOT preserve data. Select theRemove option.To select an appropriate uninstallation method, see Installation and then proceedwith Step 3.

3. Remove the installation directory and all the directory contents:

• Linux: install path/ma• Windows: install path\Multimedia_Applications\

You are now ready to re-install the previous Avaya MS.

4. Using the earlier installer, to select an appropriate install method, see Installationand then proceed with Step 5.

5. After the installation is complete, log in to Avaya MS EM.

6. Install each application by running each of the desired installers one at a time.See documentation and procedures for your applications.

7. Navigate to EM > Tools > Software Inventory.

8. Verify that the software versions that are listed are correct.If at any time the system prompted you for a restart but you deferred the prompt,restart your system now.




10. To stop Avaya MS node, navigate to System Status > Element Status > Stop.

11. Click Confirm.

12. Move the old backup files to the EM backup folder so that EM can find the files forthe restore operation. Copy the backup files saved before the upgrade to the MSbackup folder at:

• Linux: install path/ma/MAS/platdata/EAM/Backups• Windows: install path\Multimedia_Applications\MAS\platdata\EAM\Backups

13. To restore configuration data, click EM > Tools > Backup and Restore >Restore.

14. Select the listed System Configuration backup file.

15. Click Restore Now.

16. Click Confirm.

17. Monitor the Backup and Restore History Log at EM > Tools > Backup andRestore > History Log.When the backup task completes, the system displays a completed restore taskentry in the History Log.

18. To restore Application Content data, click EM > Tools > Backup and Restore >Restore.

19. Select the listed Application Content backup file.


21. Click Confirm.


23. To restore Network data, click EM > Tools > Backup and Restore > Restore.

24. Select the Network Content backup file listed.


26. Click Confirm.


28. Restart Avaya MS using EM by performing the following steps:




a. Navigate to System Status > Element Status > Start.b. Click Confirm.

29. Verify the success of the installation. Check for any service-impacting alarms andperform an appropriate test of the system, for example, place a call to an application,and verify all the nodes in the cluster receive calls.The rollback is complete for a single Avaya MS.If you are rolling back an Avaya MS cluster, return to the cluster rollback procedurewhere you left off.







Index

A

Avaya MS .....................................................................5PVI Checker ...........................................................5

C

change computer name ..............................................16configure ......................................................... 13, 14, 18

hostname ............................................................. 13Linux firewall ........................................................ 14NIC .......................................................................18SE LINUX .............................................................13

connect .........................................................................6Avaya MS to network .............................................6

D

disable ........................................................................ 16admin approval mode .......................................... 16

H

hardware ...................................................................... 6install ......................................................................6

high-level task ............................................................ 51upgrade multi-server Avaya MS cluster ...............51upgrade single-server Avaya MS server ..............51

I

install .........................................11, 12, 15, 23, 24, 28–31Avaya MS .............................................................23Avaya MS on Linux ..............................................23Avaya MS on Windows ........................................28command-line mode on Linux ..............................23command-line mode on Windows ........................30GUI mode on Windows ........................................29silent mode on Linux ............................................24silent mode on Windows ......................................31use RPM .............................................................. 12use YUM .............................................................. 11Windows Server 2008 R2 .................................... 15

Install .......................................................................... 11RHEL ................................................................... 11

L

Linux .............................................................................7kernel .....................................................................7

M

multi-server cluster ............................................... 53, 61rollback .................................................................61separation ............................................................ 53

MySQL server .............................................................. 8

O

operating systems ........................................................ 7

P

PVI Checker ..........................................................19–21command-line mode ............................................ 20GUI mode .............................................................19installer mode .......................................................21reports ..................................................................21verify specifications ..............................................19

Q

QFE ........................................................... 37, 38, 40, 42cluster .................................................................. 42HA servers ........................................................... 42install ....................................................................38obtain QFE ...........................................................37overview ...............................................................37patch tool ............................................................. 37remove .................................................................40

R

requirements .........................................................5, 8, 9hardware ................................................................5Linux packages ......................................................8network port ...........................................................9

restart ......................................................................... 17rollback ................................................................. 61, 64


Avaya MS 7.5 upgrade ........................................ 61single-server ........................................................ 64

S

secure .........................................................................17Avaya MS .............................................................17

service pack ..........................................................43, 45install ....................................................................43removal ................................................................ 45

service packs ..............................................................48HA ........................................................................48

U

uninstall ..................................................... 26, 27, 32–35

Avaya MS from Linux ...........................................26Avaya MS from Windows .....................................32Avaya MS in silent mode from Windows ..............35command-line mode from Linux ...........................26command-line mode from Windows .....................34GUI mode from Windows .....................................33silent mode from Linux .........................................27

upgrade ..................................................... 49–52, 54, 57Avaya MS upgrade overview ............................... 51backup ................................................................. 52introduction .......................................................... 49multi-server Avaya MS cluster ............................. 54prerequisites for Avaya MS 7.5 upgrade ..............50single Avaya MS .................................................. 57

70 Installing, Upgrading, and Patching Avaya Media Server 7.5 June 2013

Installing, Upgrading, and Patching Avaya Media Server 7

Documents