Intelligent Presence Server (IPS) Installation and ...€¦ · Intelligent Presence Server (IPS)...

Intelligent Presence Server (IPS)Installation and Configuration GuideVersion 1.0 SP1

02-602753Release 1.0

Issue 1March 2009

Copyright 2008, Avaya Inc. All Rights ReservedThis document contains information related to Intelligent Presence Server (IPS) software (as defined below) and Documentation (“Product”). “Documentation” means this document and Avaya’s information manuals in printed or electronic form containing operating instructions and performance specifications that Avaya or its suppliers generally make available to users of its products, and which Avaya delivers to End User with the Products. “End User” means any customer of Avaya or its authorized resellers, or any end user of the Product. See the Software and Documentation DVD/CD inserts for additional legal and licensing information.

NoticeChanges and corrections to the information in this document may be incorporated in future releases.

DisclaimerAvaya, its affiliates or subsidiaries (“Avaya”) are not responsible for any modifications, additions or deletions to the original published version of the Documentation unless such modifications, additions or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants, directors, officers, and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to the Documentation to the extent made by the End User.

WarrantyAvaya provides a limited warranty on the Product. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support.

LicenseUSE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT: http://www.avaya.com/support (“GENERAL LICENSE TERMS”). DO NOT USE THE PRODUCT IF YOU DO NOT WISH TO BE BOUND BY THE GENERAL LICENSE TERMS. IN ADDITION TO THE GENERAL LICENSE TERMS, THE FOLLOWING LICENSE TERMS AND RESTRICTIONS WILL APPLY TO THE PRODUCT.Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. “Designated Processor” means a single stand-alone computing device. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users. “Software” means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. “Hardware” means the standard hardware products, originally sold by Avaya and ultimately utilized by End User.If your system is running in a TDM environment, the following license restriction applies:Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.If your system is running in an IP environment, the following license restriction applies:Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.

For all systems, the following license restriction applies:Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the “shrinkwrap” or “clickwrap” license accompanying the Software (“Shrinkwrap License”). The text of the Shrinkwrap License will be available from Avaya upon End User’s request (see “Copyright” below for more information).

CopyrightExcept where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.Certain Software programs or portions thereof included in the Product may contain software distributed under third party agreements (“Third Party Components”), which may contain terms that expand or limit rights to use certain portions of the Product (“Third Party Terms”). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya’s web site at http://support.avaya.com/ThirdPartyLicense/.The disclaimers of warranties and limitations of liability set forth in the Third Party Terms do not affect any express warranty or limitation of liability that may be provided to you by Avaya pursuant to the license terms covering the Product contained in a separate written agreement between you and Avaya. To the extent there is a conflict between the General License Terms or your customer sales agreement and any Third Party Terms, the Third Party Terms shall prevail solely for such Third Party Components.

Security and virus disclaimerEnd User's decision to acquire products from third parties is End User's sole responsibility, even if Avaya helps End User identify, evaluate or select them. Avaya is not responsible for, and will not be liable for, the quality or performance of such third party products or their suppliers.ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO END USER’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.Avaya does not warrant that this Product is immune from or will prevent unauthorized use of telecommunication services or facilities accessed through or connected to it. Avaya is not responsible for any damages or charges that result from either unauthorized uses or from incorrect installations of the security patches that are made available from time to time.Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to [email protected].

TrademarksAll trademarks identified by ® and TM are registered trademarks or trademarks of Avaya Inc. All other trademarks are the property of their respective owners.

http://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/supporthttp://support.avaya.com/ThirdPartyLicense/http://support.avaya.com/ThirdPartyLicense/mailto:[email protected]

Series 2_March 2009_SP1_IPS 1.0: Installation and Configuration Guide March 2009 3

Contents

Chapter 1: Avaya IPS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Avaya IPS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Additional requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16swversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Documentation on the Avaya Support Web site . . . . . . . . . . . . . . . . . . . . . . 18Typographic Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing the RHEL software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22RHEL Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Configuring the NTP daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing the IPS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Uninstalling the IPS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Starting and stopping services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Changing IP address of IPS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3: Upgrading IPS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Upgrading the IPS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4: Configuring Intelligent Presence Server . . . . . . . . . . . . . . . . . . . . . 37In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Server Maintenance Configuration (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . 38

Maintenance Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Presence Component Configuration (XCP) . . . . . . . . . . . . . . . . . . . . . . . . 40

Detailed Description of Configuration Pages . . . . . . . . . . . . . . . . . . . . . 41SIP Bulk Subscription Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Adding/Deleting Trusted hosts for IPS . . . . . . . . . . . . . . . . . . . . . . . 60


RTC Collector Related Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 61RTC Collector Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Pre-Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Open Certificates Snap-in for Edge Server in MMC . . . . . . . . . . . . . . . . 62Checking the certificate used by External Interface on MS Edge Server . . . . 66Generate a Certificate with Server and Client Authentication . . . . . . . . . . 66Download the CA which signed the certificate for the External Interface . . . . 67Add CA for MS Edge server to IPS trusted list. . . . . . . . . . . . . . . . . . . 68Generate a self signed certificate for RTC collector to communicate with MS Edge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Add IPS RTC certificate to MS Edge Server Trusted Root Certificates . . . . . 68RTC Collector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Add RTC collector as an IM service provider . . . . . . . . . . . . . . . . . . . . . 71Add a DNS SRV record for the RTC Collector . . . . . . . . . . . . . . . . . . . . . 74

Example DNS SRV settings with Windows. . . . . . . . . . . . . . . . . . . . . 75Testing DNS records from Microsoft Edge Server . . . . . . . . . . . . . . . . 76Restart the MS Edge Server service after completing changes to DNS . . . . . 77Restart IPS Presence Server Component . . . . . . . . . . . . . . . . . . . . . 77

MOC client notification of RTC collector subscription . . . . . . . . . . . . . . . . 77Debug Logs and Tools for RTC collector integration . . . . . . . . . . . . . . . . . 78

Launch a New Debug Session on OCS Server. . . . . . . . . . . . . . . . . . . 81

Chapter 5: Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Installation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Backup and Restore Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Database Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Memory Usage Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Presence Server Components Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82IPS Collector Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83IPS Core Start Stop log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Core Services logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Core Services Tomcat logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Core Services Debug log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Core Services Syslogreader log . . . . . . . . . . . . . . . . . . . . . . . . . . 84Core Services Life Cycle Manager CLI log . . . . . . . . . . . . . . . . . . . . . 84Core Services Life Cycle Manager log . . . . . . . . . . . . . . . . . . . . . . . 84Core Service SNMP log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Core Services Watchdog logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 84


Changing Logging level in IPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Collecting IPS logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Viewing Logs on OAM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 6: Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89AES Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89RTC Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Purging Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Tripwire Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 7: Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Trap Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91AES Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91RTC Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91SNMP Trap Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Appendix A: Known Installation Issues and Resolutions. . . . . . . . . . . . . . . . . . . 93Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix B: Backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Data included in the backup file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Appendix C Windows Service Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

When to Restart the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Windows Service Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Appendix D IPS Security information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Security Architecture in Intelligent Presence Server 1.0 . . . . . . . . . . . . . . . . . 108 Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Controlling the Firewall on Intelligent Presence Server Solution . . . . . . . . . . 110 Monitoring Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Logins and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

XCP Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Server Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111


Internal Unprivileged Linux Accounts . . . . . . . . . . . . . . . . . . . . . . . . . 112 Session Inactivity, Audit Trails and Account Lockouts. . . . . . . . . . . . . . . . . . 112SIP Stack Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Vulnerability Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Linux PAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Inactivity time-outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Firewall Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Modifying the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Listing the rules of the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Starting the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Stopping the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Restarting the Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Allowing access to a port on the IPS server . . . . . . . . . . . . . . . . . . . . 117Disabling access to a port on the IPS server . . . . . . . . . . . . . . . . . . . 117

Warning banners / Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Appendix E: Configuring Intelligent Presence Server for one-X Portal . . . . . . . . . . . 119In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Configure one-X Portal Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Export Websphere Certificates to IPS . . . . . . . . . . . . . . . . . . . . . . . . . 121Activate Security Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Configure IPS Server for one-X Portal Server(s) . . . . . . . . . . . . . . . . . . . . . 122Configure one-X Portal for IPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Add Domain Substitution Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Configuration Required to Support Multiple one-X Portals. . . . . . . . . . . . . . . . 125

Server 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Configure Certificates Across Sites . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Change Security Settings for the Other Buses . . . . . . . . . . . . . . . . . . 130 Verify Link Status Is Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Restarting one-X Portal/IPS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Appendix F: Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Troubleshooting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133IPS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Receiving SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133


Viewing Alarm events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Viewing Log events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134avApasAesConnectionFailureNotification . . . . . . . . . . . . . . . . . . . . . . . 134avApasCmConnectionFailureNotification . . . . . . . . . . . . . . . . . . . . . . . 134avApasRtcSipDomainDownNotification . . . . . . . . . . . . . . . . . . . . . . . . 134avIpsCoreDatabaseConnectionFailureNotification . . . . . . . . . . . . . . . . . . 134avApasIpsCoreXcpComponentConnectionFailureNotification. . . . . . . . . . . . 135avApasGuiceContainerFailureNotification. . . . . . . . . . . . . . . . . . . . . . . 135avApasConfigurationErrorNotification . . . . . . . . . . . . . . . . . . . . . . . . . 135avApasXcpComponentSessionFailureNotification . . . . . . . . . . . . . . . . . . 135avApasXcpComponentInvalidResponseFailureNotification . . . . . . . . . . . . . 136

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136APRES02200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136APRES02201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136APRES02202 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137APRES03001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137APRES08001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137APRES08002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138APRES08100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138APRES08101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138APRES08102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138APRES08103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138APRES08104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139APRES08106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139APRES08107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139APRES08108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139APRES08109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140APRES08200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140APRES08201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140APRES08300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140APRES08301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140APRES08302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141APRES08303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141LPRES02000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141LPRES02001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142LPRES02002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142LPRES02003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142LPRES02004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8 Series 2_March 2009_SP1_IPS 1.0: Installation and Configuration Guide March 2009

LPRES02005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143LPRES02006, LPRES02007, LPRES02008 . . . . . . . . . . . . . . . . . . . . . . . 143LPRES02009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143LPRES02010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143LPRES02011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144LPRES02012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144LPRES02013, LPRES02014, LPRES02015 . . . . . . . . . . . . . . . . . . . . . . . 144LPRES02016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144LPRES02017 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145LPRES02018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145LPRES02019 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145LPRES02020 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145LPRES02021 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146LPRES02022 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146LPRES02023 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146LPRES02024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146LPRES02025 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147LPRES02026 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147LPRES02027 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147LPRES02028 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148LPRES02029 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148LPRES02200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148LPRES02201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148LPRES02202 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149LPRES02300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149LPRES03000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149LPRES03001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150LPRES03100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150LPRES03101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150LPRES03102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150LPRES03103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151LPRES03104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151LPRES03200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151LPRES03300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151LPRES03400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LPRES03401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LPRES03402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LPRES03600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LPRES06000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LPRES07002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153LPRES07003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153


LPRES07004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153LPRES07006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153LPRES08001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154LPRES08002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154GSYSL00008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154GSYSL00009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155GSYSL00052 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155GSYSL00053 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155GSYSL00054 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155GSYSL00103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156GSYSL00105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156GSYSL00106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156GSYSL00107, GSYSL00108, GSYSL00109, GSYSL00110 . . . . . . . . . . . . . . . 156GSYSL00111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156GSYSL00112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157GSYSL00113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157GSYSL00114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157GSYSL00115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157GSYSL00116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157GSYSL00117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158GSYSL00118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158GSYSL00119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158GSYSL00123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158GSYSL00124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158GSYSL00125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159GSYSL00126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159GSYSL00129 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159GSYSL00130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159GSYSL00131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159GSYSL00132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Troubleshooting for Technical Experts. . . . . . . . . . . . . . . . . . . . . . . . . . . 160Symptom: one-X Portal user does not receive Presence changes for a particular contact from IPS or All one-X Portal users do not receive Telephony presence . . . . . . 160

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Problem 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Diagnosis 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Possible Resolution for Problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . 160Problem 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Diagnosis 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Possible Resolution for Problem 2 . . . . . . . . . . . . . . . . . . . . . . . . . 162

Symptom: All one-X Portal users do not receive presence information for any contacts

10 Series 2_March 2009_SP1_IPS 1.0: Installation and Configuration Guide March 2009

from IPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Problem 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Diagnosis 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Possible Resolution for problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . 162Problem 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Diagnosis 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Possible Resolution for problem 2 . . . . . . . . . . . . . . . . . . . . . . . . . 163Problem 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Diagnosis 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Symptom: All one-X Portal users do not receive presence information related to OCS for their contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Symptom : All one-X Portal users do not receive presence information for their contacts from IPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Problem 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Diagnosis 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Possible Resolution for Problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . 164

Symptom: Presence Adapter in one-X Portal fails to start-up . . . . . . . . . . . . 165Problem 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Diagnosis 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Possible Resolution for Problem 1 . . . . . . . . . . . . . . . . . . . . . . . . . 165

Symptom: All one-X Portal users do not receive presence information for any contacts from IPS after reinstalling one-X Portal and reconfiguring certificates. . . . . . . 165

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Problem 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Diagnosis 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Possible Resolution for Problem . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Appendix G: Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Series 2_March 2009_SP1_IPS Installation and Configuration Guide 11

Chapter 1: Avaya IPS Overview

In this chapter● Avaya IPS overview

● Intended audience

● Hardware requirements

● Software requirements

● Additional requirements

● Documentation on the Avaya Support Web site

● Typographic Conventions

Avaya IPS overviewThe Avaya Intelligent Presence Server (IPS) is a single point of presence collection. It provides facilities for gathering presence information from a diverse range of sources, aggregating this information on a per user basis, and then making it available to consuming or subscribing applications. The IPS also provides facilities which Avaya enterprise application solutions can use to publish their own users’ presence.

Presence aware applications (e.g. one-X Portal, etc.) may use the Local Presence Service (LPS), which runs co-resident on the application server (e.g. one-X Portal Server), to subscribe to IPS to receive presence change notifications containing aggregated presence information for a user and the communication resources that user has available to them. This information can be used to provide visual indications about a user’s availability to an end user client GUI (e.g. one-X Portal).

The LPS is used to efficiently transfer presence information between the IPS server and the application server. The LPS combines all presentities across all watchers into a single resource list which is subscribed to on the IPS server. Consumers of presence information may be internal or external to the home network. When presence changes occur, batched notifications are sent from the IPS server to the LPS. The LPS then performs the necessary fan-out to the active watchers for their subscribed presentities (which it determines based on the active watcher lists it maintains for each presentity). The definition for presentity is that it is an entity that provides Presence information that is to be stored and distributed. Presentity can also be

Avaya IPS Overview

12 Series 2_March 2009_SP1_IPS Installation and Configuration Guide

defined as the term for the person, whose presence is being reported. Watcher is the person interested in the presence of the presentity.

Intelligent Presence Server (IPS) system includes a variety of components that provide various independent services that interact to provide the aggregation and dissemination of presence information within an enterprise. The main components of the IPS system are:

● The IPS Core eXtensible Communication Platform (XCP) server : IPS Core XCP is the conduit between the collectors of presence and the distributors of presence in the system. The Core maintains a list of presence fragments for a given presentity and performs composition of these fragments.

● The SIP Bulk Subscription Server : Supports Bulk distribution of presence so transfer of presence information between IPS and LPS is efficient

● The SIP proxy : SIP Proxy (not used by default in IPS, to remove it see the note under Main Administration Page with Presence Server Component in a Stopped State on page 43)

● The SIP Presence Server : Supports SIP based clients who need to Subscribe to and Publish presence. LPS uses SIP Presence Server to Publish one-X Portal presence.

● The Presence Server : Collects Avaya Enablement Services (AES) and Real Time Communications (RTC) presence for presentities retrieved from the User Data Store.

The administration, life-cycle management, and configuration management of these IPS subsystems is performed through the XCP controller web-based GUI. Use the GUI to start, stop, and configure Presence components of IPS software.

Avaya IPS overview


The IPS server must interact with the following entities (shown in the IPS box in the diagram above):

● Application Servers hosting presence aware applications like one-X Portal. In this case, IPS will provide a Local Presence Service that runs co-resident on the application server. The Local Presence Service maintains local subscriptions, performs access control and exchanges data with the regional/central IPS server using the SIP Server-to-Server (S2S) protocol. Applications using the Local Presence Service (LPS) may be requesting presence (subscribe/notify) from IPS or may be providing presence (publish) to IPS for aggregation.

one-X Portal

Avaya IPS Overview


● Presence Sources. There are a variety of other presence sources IPS must collect presence information from. This includes

● CM (via AES) for Avaya telephony devices.

● MS-RTC (OCS) for Microsoft presence.

● User Management Services – There is much user data that IPS, Avaya Applications (one-X Portal) must share in order to provide a unified view of a specific user within the enterprise. This data includes the user’s identities within various presence domains (enterprise handle, CM extension, MS-RTC handle etc).

In addition a user has access control lists that must be shared among various applications and IPS components (IPS server and IPS LPS). Rather than implement its own User Management administration infrastructure, IPS will rely on User Management data administered on (and mastered by) some other application server deployed in the network. IPS will use web services and JMS notifications to retrieve this data from a centralized management service and get notifications of changes.

The high level architecture diagram on the previous page shows a central IPS server. However, there may be one or more central IPS servers serving all users within the enterprise.

Intended audienceThis document is intended for users who are responsible for the installation and configuration of the IPS software, including Avaya engineers, Avaya Business Partners, and, independent software vendors.

Hardware requirementsThe Intelligent Presence Server (IPS) software runs on a platform that meets the following minimum hardware requirements:

Component Minimum Requirements

CPU Intel 2.66Ghz, single quad core processor or equivalent

Front Side Bus (FDSB) 1333MHz or equivalent.

Software requirements


Software requirementsThe Intelligent Presence Server (IPS) software runs on Red Hat Linux. The customer is responsible for obtaining the appropriate version of Red Hat Linux.

The software requirements are:

● Red Hat Enterprise Linux (RHEL) ES 4.0, 32-bit version

● Update 4 or Update 5

● SMP Kernel 2.6

● Disable Red Hat Security Enhanced Linux (SE Linux) - You need to set SELinux to disabled or permissive.

! Important:Important: Avaya recommends to 'Install default software packages' when installing Red Hat

Linux.

Layer 2 cache 4 MB or equivalent.

Hyperthreading enabled/SMP Kernel 2.6

Yes/YesHyperthreading can be enabled/disabled in the BIOS. Red Hat will install SMP kernel automatically if it detects more than one processor, hyper-threading adds a virtual processor. The HT flag will be visible in the file /proc/cpuinfo if HT is available. The uname –r command will display the kernel version.

Hard Disk 73GB SAS (Serial Attached SCSI) 15000 RPM or equivalent required

Memory 4GB RAM

Network Interface 100/1000 full duplex Ethernet NIC

Component Minimum Requirements

Avaya IPS Overview


Additional requirementsThe Intelligent Presence Server (IPS) software installs and configures the following required third-party software packages.

Table 1 lists third-party software packages installed and configured by IPS.

Table 1: Third-party software packages

Package Description Release Version

Tomcat JSP/Servlet Web Container 5.5.9-Avx

JDK Java Development Kit 1.5

Apache Axis Web service 1.4

PostgresSQL Database 8.1.4

Tripwire Monitor and control changes made to servers

2,x

Apache ActiveMQ Message Broker 4.0.1

Apache mod_jk Plug in that handles communication between Tomcat and Apache

1.2.6

mon General purpose scheduler and alert management tool

0.99.2.6

mod_ssl Provides cryptography for the Apache 1.3 web server via Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TlS v1) protocols by the help of the Open Source SSL/TLS toolkit Open SSL

2.0.52

Log4j Logging package for printing log output to different local and remote destinations

1.1

Commons-logging Wrapper around a variety of logging API implementations

1.0.4

IBM JMS client The IBM Client for Java Message Service (JMS) on Java 2, Standard Edition (J2SE) with WebSphere Application Server

swversion Tool


swversion Tool

A swversion tool is provided with IPS and it is installed at /opt/IPS/tools/swversion. It provides a list of the versions of IPS related software installed.

This includes:

● The Operating System version

● Avaya Presence RPMS (rpms generated for the IPs product that are in the IPS group (rpm -qg IPS)

● Core Services rpms (rpms beginning with the name cs- or cs_)

● Third party rpms ( any rpms included in the list of third party rpms)

The tool also provides a verbose option which performs an rpm -q with the -i option.

UsageTo use the swvesion tool, simply execute the swversion.sh script as follows:

/opt/IPS/tools/swversion/swversion.sh

This will list the versions of the packages in the IPS group as well as the operating system version. Alternatively the tool provides the following usage options:

● -a or -all to list the Operating System version and all packages including third party

● -v or -verbose to list the Operating System version and all packages including third party verbosely.

XCP Jabber eXtensible Communications Platform. Presence and messaging entity.

5.3

Commons-discovery Tools for locating resources by mapping service/reference names to resource names.

0.0.2

Avaya Core Services Version 3.2.3-271

Package Description Release Version

Avaya IPS Overview


Documentation on the Avaya Support Web siteTo fully implement IPS with other supported Avaya applications, please refer to their guides, listed below.

● The Application Enablement Services platform documentation.

● The Avaya one-X Portal application, see the Implementing Avaya one-X Portal guide.

● The Avaya Communication Manager application, see the Avaya Communication Manager API Management guide (03-300086).

These documents are available at http://support.avaya.com.

You must also read the release notes for the Avaya IPS server and the related Avaya applications. The release notes contain information that was unavailable when the documentation was prepared. The release notes are available at http://support.avaya.com.

To set up user accounts for the web site’s Support area, call:

● 1 (877) 733-5511 in the United States

● 001 (978) 552-0444 outside of the United States

Or you can send an e-mail message to [email protected].

Typographic ConventionsTable 2 shows the typographical conventions that are used in this book:

Table 2: Typographic conventions

Convention Meaning

Courier type

The Courier type face is used to denote one of the following:

● Text as displayed on a monitor

● Command syntax examples

bold Bold text denotes command keywords (words that must be entered exactly as shown)

1 of 2

http://support.avaya.comhttp://support.avaya.com

Typographic Conventions


italics Italics can mean any of the following:

● filenames

● book titles

● command argument names and values

● new terms not commonly understood

< > Words enclosed in angle brackets should be replaced by user-specific data. In the following example, the words userid and password should be replaced by actual user ID and password values:

Login:

Password:

[ ] Square brackets are used to denote command line arguments that are optional.

{ } Curly braces enclose a range of choices for a required argument.

When used within square brackets, curly braces indicate that if you choose to set the optional argument indicated by the square brackets, then you must choose one of the choices enclosed in the curly brackets.

In the example below, the curly brackets indicate that either in or out is always required for the ip access-group command:ip access-group {in | out}

In the following example, the version argument is optional for the snmp-serverhost command, but if it is set it must be either 1 or 2c:snmp-serverhost [traps | inform] [version {1 | 2c}]

| A vertical bar separates multiple choices among arguments.

In the following example, the vertical bar indicates that the first argument of the clear prefix command can be either a prefix in standard, dotted-decimal format (1.2.3.4/n) or the keyword all:clear prefix { | all} [routes-only]

The second argument—the keyword routes-only—is enclosed in square brackets because it is optional.

Table 2: Typographic conventions (continued)

Convention Meaning

2 of 2

Avaya IPS Overview



Chapter 2: Installation

In this chapter● Pre-installation

● Installing the IPS software

● Uninstalling the IPS software

PrerequisitesThe following information needs to be gathered/configured before the IPS installation:

Product Required Information

IPS Avaya Services login/password.

AES When deploying multiple AES Servers, the TSAPI user account for IPS must be the same across all instances.

UMS UMS runs in one-X Portal for IPS systems integrated with one-X Portal.

● UMS administrative login/password ● Web Service host (host name or IP address of UMS) ● Web Service port ● JMS host (host name or IP address of UMS) ● JMS port

OCS (If OCS integration is required)

● Login details for the OCS 2007 Access Edge Server

● Login details for DNS used by OCS/Edge servers

Installation


It is recommended that you accept the default partition sizes. The following are minimum recommended sizes if an administrator wishes to manually configure partitions:

Installing the RHEL softwarePrior to installing the IPS software, you must first obtain and install the Red Hat Enterprise Linux ES (RHEL) version 4.0, 32-bit, Update 4 or Update 5 with default options.

! Important:Important: Avaya does not provide the Red Hat Linux software.

To install the RHEL ES software, follow the installation procedure at the Red Hat website. Go to www.redhat.com. For related documentation, go to Support at www.redhat.com.

! Important:Important: Ensure the FQDN of the server IPS is installed on uses a valid hostname.

Hostnames are composed of series of labels concatenated with dots.

Each label must be between 1 and 63 characters long, and the entire hostname has a maximum of 255 characters. Each hostname label may contain only the ASCII letters 'a' through 'z' (case-insensitive), the digits '0' through '9', and the hyphen. Hostname labels cannot begin or end with a hyphen. No other symbols, punctuation characters, or blank spaces are permitted. (See http://www.faqs.org/rfcs/rfc1035.html)

RHEL Software Installation

● It is recommended that you accept defaults for the RHEL installation. This includes accepting default partitioning. You should turn off SELinux and the firewall, see explanation below.

● You must disable or set to permissive SELinux, you can disable SELinux during the RHEL installation. Verify that you disabled SELinux by using the getenforce command. If the

Partition Size

/ 4

/opt 2 GB

/home 1 GB

/tmp 4 GB

/var 4 GB

/usr 4 GB

http://www.redhat.com

Pre-installation


SELinux default install was used, SELinux must either be disabled or set to permissive for the Platform alarms to be reported.

service iptables stop

! Important:Important: If you plan on installing the RTC Collector for OCS, then your IPS server needs to

be in a different domain or subdomain of the enterprise domain in which the OCS Server is present. See RTC Collector Overview on page 61.

Pre-installationThe Intelligent Presence Server (IPS) requires the following pre-installation steps prior to installing the IPS software on the server:

● Configure network time protocol

● If the firewall was left enabled, disable it by using the following command:


Configuring the NTP daemon

Note:Note: Network Time Protocol (NTP) daemon is not installed as part of a minimal Red

Hat Linux installation.

NTP is an operating system daemon that sets and maintains the system’s time of day in synchronism with Internet standard time servers. Prior to IPS installation, configure and start the NTP daemon. Starting the NTP daemon allows logging of events that can be correlated by time with events in other systems.

IPS should be synchronized to the same NTP time source with other integrating application(s) (one-X Portal, OCS, etc). Time synchronizaton with same NTP server as other interfacing application (one-X Portal, OCS, etc.) will be also helpful in troubleshooting. To configure NTP daemon, use the following procedure:

1. Add the NTP reference server hostname or IP address to /etc/ntp.conf.

Multiple NTP reference servers may be entered for redundancy and accuracy.

2. Add the NTP server hostname or IP address to /etc/ntp/step-tickers.

This allows the system time to be quickly synchronized with the server by reducing the drift between the system and reference clocks.

Installation


3. Add the NTP daemon to run levels 2,3,4,5: chkconfig --level 2345 ntpd on4. Start the NTP daemon service. Run: service ntpd start

! Important:Important: If ntpd restart is enabled during the installation, then you should use restart

rather than start. If restart is enabled and start is used, then you will get a Failed message.

Installing the IPS softwareThis procedure describes how to install the IPS software on a new server. This installation type assumes that the server will only be used as an IPS server, and no other software will be installed.

Before you perform this procedure, you must:

● Install the physical server that will host IPS and put it on your network

● Turn on the IPS server

● Verify disk space is available as specified in the prerequisites section.

● The installation automatically checks the Red Hat Linux release installed.

To install the IPS software:

1. Use the whoami command to verify that you are root user. The results of this command are shown in the example below.

[root@cdgsduser5 presence]# whoami

root

2. Stop the firewall (if running) by using the following command:


3. Verify that the following software packages are present in your RHEL operating system:

compat-libcom_err-1.0.5 libxml2-2.6.16-

where RHEL Operating System is 6 for RHEL Update 4 and RHEL Operating System is 10 for RHEL 4 Update 5.

Type the following command: rpm -q followed by the package name, e.g. rpm -q libxml2.The response will include the filenames and version numbers. If the files do not appear on the list or the version is below the version listed above, you need to go back to your Red Hat installation disks to install the two packages.

Installing the IPS software


Note:Note: The compat-libcom_err package is not installed as part of a minimal Linux

installation. It is, however, installed as part of a default Linux install.

4. Verify that the /etc/hosts file contains the following lines:

! Important:Important: The /etc/hosts file must contain the following two entries/lines.

127.0.0.1 localhost.localdomain localhost Machine_IP host_FQDN host_name

For example, 198.152.1.2 myserver.mycompany.com myserver for Machine_IP host_FQDN host_name

If the /etc/hosts file is edited by adding a hostname for the machine, restart network services before proceeding with installing IPS to incorporate changes made to the hosts files.

service network restart

5. Configure the server’s static IP address.

6. Configure the server’s fully qualified domain name (FQDN).

The system must also be set up with a static IP address and must be given a fully qualified domain name (FQDN), as this is used (via the hostname and hostname -s commands) by the installer for naming. Changing the FQDN or the static IP address of the IPS server after installation is not currently supported.

7. Insert the IPS software CD into the CD-ROM drive. Close the drive.

Note:Note: The CD ROM drive needs to be mounted on the server.

The script and rpm can be found on the CD in the /IPS/bin directory.

The file names follow the same naming convention, starting with IPS followed by a version number.i386 where version number is , for example IPS-01.00.00-29.i386.sh and IPS-01.00.00-29.i386.rpm.

8. Make sure all pre-configuration steps have been performed. The IPS install script can be run directly from the CD from the /IPS/bin directory. Alternatively copy the install script

Installation


and the rpm to the same directory on the IPS server and execute IPS install script from the direcory where the script and RPM is located on the server.

The install script sets some configuration environment variables and performs some pre-installation tests before initiating the Red Hat Package Manager (RPM).

./.sh -ci [ips_configuration_file_name];

Optionally you can use the IPS configuration file to preconfigure your presence service:

The IPS Configuration file is optional. If you wish to use the configuration file you need to configure the file according to your system setup prior to installing IPS.

Below is the content of a sample configuration file:

export ROUTER_SERVICE_NAME="pres.ips.avaya.com"

export PRESENCE_DOMAIN=$ROUTER_SERVICE_NAME

export ROUTER_REALM="presence"

export AESUSERNAME="admin_login"

export AESPASSWORD="Admin1_password"

export WSHOST="localhost"

export WSPORT="9443"

export WSSERVICE="/ums/services/UserMgmtServicePort"

export JMSHOST="localhost"

export JMSPORT="7286"

export WSLOGIN="websphere"

export WSPASSWORD="avaya01"

export SECURECONNECTION="1"

Note:Note: After an install there is only one Presence Server Component. AESUSERNAME,

AESPASSWORD, WSHOST, WSPORT, WSSERVICE, JMSHOST, JMSPORT, WSLOGIN, WSPASSWORD, SECURECONNECION properties apply to this component. When there are multiple one-X Portal systems, new Presence Server components must be added to the IPS and configured after an install. You cannot preconfigure additional Presence Server components.

Names must comply with domain and hostname naming conventions, as per http://tools.ietf.org/html/rfc3696#section-2.

http://tools.ietf.org/html/rfc3696#section-2http://tools.ietf.org/html/rfc3696#section-2

Parameter Description Default value

ROUTER_SERVICE_NAME XCP service name. pres.ips.avaya.com

PRESENCE_DOMAIN XCP domain. pres.ips.avaya.com

ROUTER_REALM XCP realm. presence

ROUTER_IP_ADDRESS XCP IP address.ROUTER_IP_ADDRESS: this is the default ip address value used throughout the install:When deciding what to use for an ip address the installer will first choose ROUTER_IP_ADDRESS then HOST_IPADDRESS, then the ip address on eth0 and finally eth1.If all of these values fail, then the installer will fail and exit.

N/A

AESUSERNAME The username used for logging into the AES.

AESPASSWORD The password used for logging into the AES.

WSHOST Hostname on which the UMS server is running.

WSPORT Port number for UMS. 9443

WSSERVICE The service name URL for the UMS.

/ums/services/UserMgmtServicePort

JMSHOST JMS broker hostname.

JMSPORT JMS broker port number 7286

WSLOGIN UMS server login websphere

WSPASSWORD UMS server password Avaya01

SECURECONNECTION Enable secure (TLS) communications .

1

Installing the IPS software


Configuration file parameter description

Installation


Note:Note: Note that the ROUTER_SERVICE_NAME and the PRESENCE_DOMAIN hold

the same value; this is because these values are set in separate locations, but will generally hold the same value. The use of different names is to help clarify the differences and support the possibility of alternate configurations.

ROUTER_SERVICENAME, ROUTER_REALM, ROUTER_CLUSTER: These are equivalent and have the same purpose as the configuration values of a similar name described in the xcp configuration documentation.

AESUSERNAME, AESPASSWORD, WSHOST, WSPORT, WSSERVICE, JMSHOST, JMSPORT, WSLOGIN, WSPASSWORD and SECURECONNECTION map directly to their respective fields in the configuration page for Presence server. See IPS Server Configuration Parameters on page 50.

The product installer will make all necessary changes to the system after this point.

9. When the installation is complete, remove the CD-ROM and close the CD-ROM drive.

Note:Note: The installation typically takes 45 minutes and does not require user interaction.

10. Verify that the following new sub-directories are created in the /opt/ directory:

● /opt/coreservices/ contains the core services installation software.

● /opt/IPS/jabber/ contains the installation version of the IPS XCP product.

● /opt/IPS/install/ contains the files used to install the IPS XCP product.

11. Review the installation log to verify that the installation process was successful. The RPM will direct you to the installation log.

The log is located: /opt/IPS/install/scripts/install.log

Note:Note: Any errors in the installation log are reported near the bottom of the log.

12. Use the grep command to search the installation log for issues during the installation process. Search for the following expressions:

● ERROR: Refers to issues. The installation may fail due to errors.

● WARNING: Means information that may lead to an ERROR. This type of issue may not be terminal.

● INFO: Are informational messages.

Note:Note: Also, see Appendix A: Known Installation Issues and Resolutions on page 93.

13. If there was a problem during the installation process, uninstall the IPS software, restart the server, and reinstall the IPS software. To check the installation log, it is located: /opt/ips/install/scripts/install.log.

Uninstalling the IPS software


Uninstalling the IPS softwareThe uninstall process removes all software packages installed or updated during the IPS installation. The uninstall process restores the system to a new installation state. Uninstalling the IPS software will not restore the previous version of software packages that were modified during installation.

! Important:Important: The uninstall process will attempt to remove all packages in the IPS installation

regardless of existence prior to the IPS installation. Some of these packages include: Postgres, Java, apr, mon, Apache, and Open LDAP.

During the installation process, uninstall verification scripts are available from the /opt/IPS/install/scripts/test directory. These scripts are removed by the uninstall process, therefore the verify_uninstall.sh script in addition to the test-vars.sh script must be moved to an alternate location before uninstalling the IPS software. These scripts will indicate any known issues with the uninstall process.

To uninstall the IPS software:

1. Log in as root user.

2. Uninstall the IPS software with the following uninstall script:

/opt/IPS/install/install/scripts/uninstall/uninstall.sh

Alternately locate the installation script on the IPS installation CD.

Note:Note: The installation script is in the same directory where the IPS RPM is located.

To uninstall IPS, all related packages and any third-party packages which IPS installed, enter ./ -cu

Substitute the appropriate script name where the name indicates the version of IPS to be uninstalled.

Note:Note: Please use the same IPS version script which was used to install the IPS.

During an uninstall process, a log is created and stored in a temporary directory. The location of this temporary directory is reported at the completion of the uninstall process. Check this log for errors.

Installation


Starting and stopping servicesUse the following procedure to start, restart, or stop IPS services. All services must be stopped and started in sequence. Using the sequence allows time for the services to fully stop or fully start.

Note:Note: In the following procedure, substitute start, stop, or restart as required.

! Important:Important: If you need to stop and start just the XCP components (Presence Server, SIP

Bulk Distributor, SIP Presence Server, Core, Presence Session Manager) you should run:

/opt/IPS/presence/bin/stop.sh

/opt/IPS/presence/bin/start.sh

To start, stop, or restart IPS services:

1. Restart activemq. Enter service activemq restart. Wait 20 seconds for activemq to start. Activemq must be started before System Data Access Server (SDAS), SDAS is a service that is part of core services and controlled by tomcat. Core services and tomcat are started by the watchdog service.

2. Restart the watchdog service. Enter service wdinit restart.

3. Verify that the watchdog service restarted. Enter service wdinit status.

4. Go to /opt/coreservices/watchd or $CSBASE/watchd.

Uninstalling the IPS software


5. Execute listwatch. Enter ./listwatch.

Observe the output. The output should be similar to the following (may take a few minutes for all services to be listed):

Watchdog is monitoring the following applications:

rmiregistry, /opt/coreservices/lifecycle/bin/rmireg.sh, Application, Running, 10114

ServiceLocator, /opt/coreservices/dss/bin/sl, Application, Running, 10115

LCM, /opt/coreservices/lifecycle/bin/lcp2srv, Application, Running, 10188

postgres, /usr/bin/postgres, Service, Running, 10269

webcontroller, /opt/IPS/jabber/xcp/bin/cm, Service, Running, 10332

httpd, /usr/sbin/httpd, Service, Running, 10418

tomcat5, /usr/java/jdk1.5.0_15/bin/java, Service, Running, 16483

mon, /usr/bin/perl, Service, Running, 10499

syslogreader, ./wrapper, Service, Running, 10514

snmpagent, jsvc, Service, Running, 10632

ipscore, /opt/IPS/jabber/xcp/bin/jabberd, Service, Running, 584

6. Go to /opt/coreservices/lifecycle/bin.

7. Execute the lc script passing the list command. Enter ./lc list.

Installation


The following output is normal:

List of services :

postgres : Postgresql Database : STARTED

httpd : Apache httpd : STARTED

syslogreader : Core Services Syslogreader : STARTED

tomcat5 : Tomcat : STARTED

webcontroller : Intelligent Presence Server Controller : STARTED

mon : Mon : STARTED

snmpagent : SNMP Agent : STARTED

ipscore : Intelligent Presence Server Core : STARTED

The lifecycle (lc) script can be used to manage the processes listed, use:./lc help to list all usage options.

Changing IP address of IPS ServerChanging the IP address of the IPS Server is currently not supported. If the IP address has to be changed, the IPS software must be first uninstalled.

1. Uninstall IPS software. See Uninstalling the IPS software.

2. Change IP address.

3. Install IPS. See Installing the IPS software.

Note: Any IPS backups taken on the server prior to the IP address change cannot be used to restore on the server after the IP address change. If you need to save any configuration settings you could take some screen shots prior to uninstalling.

Series 2 _March 2009_SP1_IPS Installation and Configuration Guide 33

Chapter 3: Upgrading IPS Software

IntroductionThis chapter provides instructions for upgrading the IPS software to a new release.

Upgrading the IPS SoftwareTo upgrade the IPS software, use the following instructions:

1. Transfer the appropriate installation files to the IPS server:

● Use scp, WinSCP, or other file transfer utility to copy the new software RPM file and kickoff shell script onto the IPS server (put it in /tmp or other convenient directory, as desired): example filenames:

- IPS-01.00.00-29.i386.rpm

- IPS-01.00.00-29.i386.sh

● Make sure that a copy of the kickoff shell script for the currently-installed software is also present. That is, if the current software is load 29, you must have available the kickoff shell script for load 29, IPS-01.00.00-29.i386.sh, so that you can uninstall the current software before you install the new software. You can confirm the currently running IPS version by executing:

/opt/IPS/install/swversion/swversion.sh2. On the one-X Portal server, stop the one-X Portal server's presence adapter as follows:

a. Log in to the one-X Portal Admin web page (http:///1xp/admin).

b. Click on the "Monitors" tab.

c. Select "Presence" in the left column of the frame.

d. Click the "Stop" button under "Actions".

e. Confirm that the presence adapter enters the stopped state.

3. On the IPS server:

a. Log in with root access.

http:///1xp/admin

Upgrading IPS Software

34 Series 2 _March 2009_SP1_IPS Installation and Configuration Guide

b. Stop all IPS services by executing:

service wdinit stop

or

/etc/init.d/wdinit stop

c. Back up the current installation, by executing the IPS back-up script, /opt/IPS/presence/bin/backup.sh without arguments. The script creates a back-up file located in /var/presence/backup/archive.

d. Make a note of the file’s name, which will be in the format, "backup_.tgz".

example: /var/presence/backup/archive/backup_2008_07_01_17_09_42.tgz

4. While IPS is stopped,

a. Change directory to the directory where you put the RPM file and kickoff scripts.

b. Perform a clean uninstall of the current version of IPS software, using the appropriate kickoff script with the “-cu” option:

c. example: ./IPS-01.00.00-29.i386.sh -cu

Note:Note: You MUST use the same kickoff script to uninstall software that you used to

install it!

5. Perform a clean install of the new version of IPS, using the appropriate version of kickoff script with the “-ci” option:

example: ./IPS-01.00.00-29.i386.sh -ci

6. When the kickoff shell script completes successfully, verify by logging into an XCP console web session (https://:7300/admin) that all component status is displayed as green.

7. Stop all IPS services by executing:

service wdinit stop

or

/etc/init.d/wdinit stop

8. Log out and log back into a new CLI root session on the IPS Server.

https://:7300/adminhttps://:7300/adminhttps://:7300/admin

Upgrading the IPS Software

35


9. Restore the backup created in step (3) above, by executing the restore script, /opt/IPS/presence/bin/restore.sh -f . The restore script will reconfigure IPS with settings saved in the backup file.

Example: cd /var/presence/backup/archive /opt/IPS/presence/bin /restore.sh -f backup_2008_07_01_17_09_42.tgz

10. Start all IPS services by executing the following:

service wdinit start

or

/etc/init.d/wdinit start

11. Allow several minutes for all services to come back up. Then verify IPS operation by logging into the XCP console web interface (https://:7300/admin) and confirm that the status is green for all components.

12. On the one-X Portal server’s admin session (see step (2) above), start the presence adapter, and confirm that its state quickly changes to "Connected".

13. Launch your destop one-X Portal client, and confirm that presence is working, i.e., that you can see presence information for the people on your favorites list, and that your own presence is accurately reported whether you force it (e.g., busy, available, out-of-office, etc.) or select “automatic” and let the system determine it.

Upgrading IPS Software



Chapter 4: Configuring Intelligent Presence Server

In this chapter● Server Maintenance Configuration (OAM)

● Maintenance Pages

● Presence Component Configuration (XCP)

● RTC Collector Related Configuration

● RTC Collector Overview

● Certificates

● RTC Collector Configuration

● Add RTC collector as an IM service provider

● Add a DNS SRV record for the RTC Collector

● MOC client notification of RTC collector subscription

● Debug Logs and Tools for RTC collector integration

IntroductionThe IPS configuration is available between two sets of Web Pages. Both are accessible by accessing the server IP address in a web browser.

http://

'This will present a launch page for accessing the Server Maintenance Configuration pages and the Presence Component Configuration pages.

! Important:Important: If you intend to use IPS with one-X Portal, see Configure IPS Server for one-X

Portal Server(s) on page 122 for a configuration specific to that integration.

Configuring Intelligent Presence Server


Server Maintenance Configuration (OAM)

Maintenance PagesIPS provides a set of pages for server maintenance. This section provides a brief overview of each page. The list of pages below is the full list of pages available to users with full access rights.

● User Management

● Administer Users

● Unlock User Accounts

● System Maintenance

● Log Viewer

● Alarm Viewer

● System Status

● Statistics

● System Configuration

● Manage Administrative Data

● Administer Log and Alarm Options

● Utility

● Ping

● System Properties

● Administer Login Session Properties

● Connection Management

● Administer Connections

● Security

● Administer Server Certificates

● View Pending Certificate Requests

● Administer Certificate Defaults

● Trusted Certificates

● SNMP Configuration

● SNMP Traps

Server Maintenance Configuration (OAM)


Page Description

User Management

Note:Note: User management is disabled for customer login accounts.

Administer Users Add, edit and remove users from the system

Unlock User Accounts Unlock any user accounts that have become locked out of the system

System Maintenance

Log Viewer View system logs (pop-ups must be enabled)

Alarm Viewer View system alarms (pop-ups must be enabled)

System Status Page Displays the status (started/stopped) of processes controlled by watchdog. The status of the following components are displayed:

● Intelligent Presence Server Controller● Intelligent Presence Server Core● Postgresql Database● Apache httpd● Core Services Syslogreader● Tomcat● Mon

Statistics page Displays the following information:

● Number of administered presentities for this server● Uptime – how long the system has been running in

days/hrs/mins● Number of presence packets published● Average packet size

System Configuration

Manage Administrative Data

This option is not in use for IPS 1.0

Administer Log and Alarm Options

Allows the setting of options for logging and alarming, specifically, whether the logs/alarms should be purged, and how often

Utility

Configuring Intelligent Presence Server


Presence Component Configuration (XCP)An Avaya Intelligent Presence Service (IPS) system is composed of a number of components, which provide various independent services and which collaborate to provide the aggregation and dissemina

Date post:	22-Sep-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times

Intelligent Presence Server (IPS) Installation and ...€¦ · Intelligent Presence Server (IPS)...

Documents