Avaya Integrated Management Application Notes: Release 3.0 Windows Installation Properties - Issue 1.0 Abstract This paper attempts to provide the customer with relevant information about the Integrated Management Microsoft Windows-based applications in order for customers to make an assessment of the necessary protocols and services needed to run on their Windows server. Editor: A. Garcia; Reviewed: JD Sipes, J. Jeppson, N. Kaufman & D.
Table of Contents 1. INTRODUCTION................................................................................................................. 3 1.1. 2. NOTATION, TERMINOLOGY AND ACRONYMS .................................................................. 4 INTEGRATED MANAGEMENT RELEVANT DIRECTORIES:................................. 5 2.1. INTEGRATED MANAGEMENT COMMON COMPONENTS:.................................................... 5 2.2. INTEGRATED MANAGEMENT LAUNCH PAGE:.............................
1. Introduction This paper covers information on what the Integration Management software configures on the customer-provided Windows Server. It covers the following: 1. Installed Files, Default Directory Locations and Registry Entries 2.
1.1. Notation, Terminology And Acronyms The following table gives meanings for most of the terms and acronyms used in this document.
2. Integrated Management Relevant Directories: This section lists the directories used and created by various Integrated Management applications. The directories are the locations on the Windows server where the Integrated Management files are installed. 2.1. Integrated Management Common Components: Default Directories: C:\Program Files\Avaya\Required Components C:\Program Files\Avaya\JRE contains Integrated Management Client and Server Configuration GUI files, launchApp, and *.
2.3. Avaya Site Administration: Default Directories: C:\Program Files\Avaya\Site Administration\bin program executable files and *.dll files C:\Program Files\Avaya\Site Administration\data data files; such as bitmaps, defaults and list files C:\Documents and Settings\\ Application Data\Avaya\Site Administration\user location of persist.
2.4.
2.5. VoIP Monitoring Manager: Default Directories: C:\Program Files\Avaya\VoIP Monitoring Manager\bin contains program executable Jar files Registry Entries: HKLM\SOFTWARE\Avaya\Avaya Integrated Management\ HKLM\SOFTWARE\Avaya\Avaya Integrated Management\Databse Password\ HKLM\SOFTWARE\Avaya\Avaya Integrated Management Monitoring Server 3.
2.6. Network Management: Default Directories: C:\Program Files\Avaya\Network Management contains program executable Jar files Registry Entries: HKLM\SOFTWARE\Apache Group\Apache\2.0.54\ HKLM\SOFTWARE\Avaya\Avaya Integrated Management\ HKLM\SOFTWARE\Avaya\Avaya Integrated Management Windows Enterprise Server 3.0\ HKLM\SOFTWARE\Avaya\CVS\CajunView\ HKLM\SOFTWARE\Avaya\CVS\CajunView\Components\ HKLM\SOFTWARE\Avaya\CVS\CajunView\Versions\ HKLM\SOFTWARE\Avaya\JRE 1.4.2_03\ HKLM\SOFTWARE\Avaya\JRE 1.4.
2.8. Network Management System Integration (NMSI): The installation of NMSI will follow the directory structure created by the HPOV installation. Since NMSI only integrates with HPOV, all files for NMSI will be installed under the HPOV installation directory. Default Directories: Following subdirectories are created under the main installation directory of HPOV: \classes\ mfpma.jar \bin\ nmsiTalk.
Table 1: Windows-Based Application Network Communication Information Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction IP Phones Yes VMM Server 5005 Yes TCP RTCP In Medpro Boards Media Gateways VMM 20493027 20493027 5005 Yes VMM Server 5005 Yes TCP RTCP In Yes VMM Server 5005 Yes TCP RTCP In 1024+ No SQL Database 1433 No TCP sql In WebLM 1024+ No Tomcat 3999 Yes TCP http In P
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) 1024+ No Multiple 2401 No TCP Multiple In Used for Client access, RMI, Login, Database, and Trap services; cv.launcher.
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) 1024+ No Multiple 2406 No TCP Multiple In Used for Client access, RMI, Login, Database, and Trap services; userver.socket.
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) Network Management (Standalone or NNM Integration) 1024+ No Multiple 2411 No TCP Multiple In Used for Client access, RMI, Login, Database, and Trap services; nmlogin.remote.
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Description 1024+ No Multiple 2331 No TCP RMI In Used for Client access, RMI, Login, Database, and Trap services; amProcess.rmi.port 1024+ No Multiple 2332 No TCP Multiple In Used for Client access, RMI, Login, Database, and Trap services; llm.amClient.
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Description 162 No UDP SNMP Out 80 Yes TCP http In Tomcat Servlet Container Optional VMM SNMP Traps VMM Server 1024+ No Management PC 1024+ No Network Management System Tomcat Management PC 1024+ No Apache 8080 Yes TCP http In Management PC 1024+ No Apache 443 No TCP https In Management PC Management PC Management PC VMM, Network Man
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Description ASA 1024+ No Voice Mail Servers (e.g. Intuity Audix) 23 No TCP telnet Out Telnet access to elements ASA 1024+ No Voice Mail Servers (e.g.
Source Source Port Source Port Configurable? Destination Destination Port Destination Port Configurable? Transport Protocol Direction Description SAT Service ports on Voice Systems – depends on voice system SAT service administration for port number Note: The value shown is for SAT access to the Linux-based Media Servers LDAP connection to Modular Messaging for administration of subscribers NMSI: HP OpenView Solaris ovwdb service daemon NMSI: HP OpenView GUI Map API Access (port=3700 + gui display
2.9. Tomcat Servlet Container The tomcat web server installs into the standard Tomcat Windows installation locations including the following directories: Default Directories: C:\Program Files\Apache Group\Tomcat 4.1 contains executable files Registry Entries: HKLM\SOFTWARE\Apache Group\Tomcat\ 2.10.
3. Conclusion With the information in this white paper, the customer has been provided with the relevant information about the Integrated Management Windows-based applications. This information will allow the customer to make an assessment of the necessary protocols and services needed to run on their Windows server. 4. Additional References 1. Avaya™ Integrated Management Release 3.0 Standard Management Installation and Upgrade, 14-300479, 700364094, Issue 1, June 2005, http://support.avaya.
©2005 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in this White Paper is subject to change without notice. The technical data provided in this White Paper are believed to be accurate and dependable, but are presented without express or implied warranty.
