Application Notes - Avaya



|Avaya Integrated Management Application Notes: |

|Release 2.1 Linux Installation Properties - Issue 1.0 |

Abstract

| |

|This paper attempts to provide the customer with relevant information about the Integrated Management Linux-based applications in order for|

|customers to make an assessment of the necessary protocols and services needed to run on their Linux server. |

Table of Contents

1. Introduction 3

1.1. Notation, Terminology And Acronyms 4

2. Avaya installed RPM’s 5

3. Third Party RPMs 6

4. Integrated Management Relevant Directories: 7

4.1. Integrated Management Homepage: 7

4.2. Fault and Performance Manager (FPM): 8

4.3. MVMAINT (maintenance package): 11

4.4. Proxy Agent (PA): 13

4.5. Multi-Site Administration (MSA): 15

4.6. Integrated Management Database (IMD) 18

4.7. PostgreSQL Database Management System 20

4.8. Tomcat Web Server 21

4.9. PHP/PHP-PGSQL 22

5. Conclusion 23

6. Additional References 23

Introduction

This paper covers information on what the Integration Management software configures on the customer-provided Linux Server. It covers the following:

1. Avaya Installed RPMs

2. Required third-party RPMs

3. Installed Files and Directory Locations

4. Application Network Communication Information

• Service

• Default Port

• Transport

• Protocol

• Direction

This paper attempts to provide the customer with relevant information about the Integrated Management Linux-based applications in order for customers to make an assessment of the necessary protocols and services needed to run on their Linux server.

1 Notation, Terminology And Acronyms

The following table gives meanings for most of the terms and acronyms used in this document.

|Term |Meaning |

|API |Application Programming Interface |

|CLAN |Control-LAN, a Communication Manager IP interface circuit pack |

|FIFO |First In First Out |

|FPM |Fault and Performance Manager |

|FTP |File Transfer Protocol |

|GUI |Graphical User Interface |

|HTML |HyperText Markup Language |

|HTTP |HyperText Transfer Protocol |

|HTTPS |HyperText Transfer Protocol Secure |

|IMD |Integrated Management Database |

|IP |Internet Protocol |

|MSA |MultiSite Administration |

|NMSI |Network Management System Integration |

|OV |HP OpenView |

|PA |Proxy Agent |

|PPP |Point-to-Point Protocol |

|PSQL |PostgreSQL interactive terminal - Terminal-based front-end to PostgreSQL (enables you to type in |

| |queries interactively, issue them to PostgreSQL, and see the query results) |

|RMATS |Remote Maintenance and Test System |

|RMI |Remote Method Invocation |

|RPM |RedHat Package Manager |

|SAT |System Access Terminal |

|SMTP |Simple Mail Transfer Protocol |

|SNMP |Simple Network Management Protocol |

|SSH |Secure Shell |

|T&M |Time and Materials |

|TCP |Transmission Control Protocol |

|TSC |Technical Service Center |

|UDP |User Datagram Protocol |

|VNC |Virtual Network Computing - software that makes it possible to view and fully-interact with one |

| |computer from any other computer or mobile device anywhere on the Internet |

|VPN |Virtual Private Network |

Avaya installed RPM’s

The following Linux packages are installed by the Avaya Integrated Management software on either Red Hat Linux Enterprise Server Version 2.1, Red Hat Linux Advanced Server Version 2.1, Red Hat Linux Enterprise Server 3.0 or Red Hat Linux Advanced Server Version 3.0, where an RPM is specific to a Red Hat Linux version that version is listed in parentheses ():

avaya-imd-2.1-75

avaya-IMHomePages-2.1-12

avaya-web_page-2.1-12

mcm-server-2.1-122

mfpm-server-2.1-242

mpa-server-2.1-23

mvmaint-server-2.1-14

j2sdk-1.4.2-fcs

php-4.3.2-8.ent (for AS/ES 3.0)

php-4.1.2-2.1.6.ent (for ES 2.1)

php-pgsql-4.3.2-8.ent (for AS/ES 3.0)

php-pgsql-4.1.2-2.1.6.ent (for ES 2.1)

postgresql-7.2.4-2_0_71

postgresql-devel-7.2.4-2_0_71

postgresql-docs-7.2.4-2_0_71

postgresql-jdbc-7.2.4-2_0_71

postgresql-libs-7.2.4-2_0_71

postgresql-odbc-7.2.4-2_0_71

postgresql-perl-7.2.4-2_0_71

postgresql-server-7.2.4-2_0_71

tomcat4-webapps-4.1.24-full.2jpp

tomcat4-4.1.24-full.2jpp

Third Party RPMs

The following Linux packages are either required or suggested, but not installed directly from Integrated Management CD-ROMs:

Proxy Agent analog modem alarm reception or forwarding:

Uucp – required for adjunct alarming, or non-IP voice system alarming (Note: The installer does not prevent installation, but a warning is issued if not installed on the Linux server.)

Remote Services:

ppp – used by TSC for remote maintenance via modem on COM1

mgetty – used by TSC for remote maintenance via modem on COM1

(not required if customer provides alternate PPP or VPN access to systems for Avaya remote services personnel)

vncserver – used by TSC for remote maintenance access to Graphical User Interfaces. Vncserver does not need to be configured to start automatically, but allow for a remote Avaya services technician to start a VNC session for troubleshooting, and kill the session when troubleshooting is complete. (If not installed, it may warrant T&M charges for maintenance support.) Avaya recommends using TightVNC software, which is available from the following website:



Required for Integrated Management Database:

(Note: Fault and Performance Manager/Proxy Agent/MultiSite Administration require Integrated Management Database for administrative purposes.)

apache (AS/ES 2.1) – required by Integrated Management Database

httpd (AS/ES 3.0) – required by Integrated Management Database

Integrated Management Relevant Directories:

This section lists the directories used and created by various Integrated Management applications. The directories are the locations on the Linux server where the Integrated Management files are installed.

Directories:

/usr/sbin contains user accessible commands from many Integrated Management applications

/opt/avaya/VisAbility/IMDataUtilitiy contains GUI for Backing up and restoring Integrated Management Data.

/var/avaya/install contains log files for installer and some other Integrated Management applications

/root/vpd.properties a registry file created by the Integrated Management installer, should not be deleted.

/root/im-install.log log file created by the Integrated Management installer

owner:root

1 Integrated Management Homepage:

Directories:

/opt/avaya/VisAbility/html Integrated Management homepage files plus client self-extract file

/opt/avaya/VisAbility/AdminGUI contains Integrated Management Server Configuration GUI files

owner:root

2 Fault and Performance Manager (FPM):

Directories:

/opt/avaya/mfpm configuration files associated with Fault and Performance Manager

/opt/avaya/mfpm/bin Program files and executables

/opt/avaya/mfpm/snmp_mib Contains SNMP ASN1 MIB files for supported products

/var/avaya/db database directory for Integrated Management postgreSQL database

/var/avaya/mfpm/logs informational and debugging logs for Fault and Performance Manager application and services

/var/tomcat4/webapps/mfpm applet configuration files for running Fault and Performance Manager applet under tomcat

/opt/avaya/VisAbility/html/WEB-INF/cgi/mfpm CGI scripts for Fault and Performance Manager

/usr/share/gnome/apps/Avaya/MFPM KDE/Gnome desktop integration

/usr/share/pixmaps/Avaya KDE/Gnome desktop integration (icons)

/usr/share/man/man1 Contains Fault and Performance Manager shell command line manual pages

Files:

/etc/services * MFPMxxx ports are added

/etc/init.d/mfpm-server sets up for autostart/stop of Fault and Performance Manager services at boot/shutdown time

/etc/init.d/postgresql sets up for autostart/stop of postgreSQL database server at boot/shutdown

* NOTE: These are the default ports entered into the services file. The port numbers can change if they are already in use by another service

Logins created: mfpmadm

Groups created: mfpm

Table 1: Fault and Performance Manager Network Communication Information

|Service Alias |Default Port |Transport |Protocol |Direction |Description |

|MFPMrmi |*5000 |TCP |Rmi |Bi-direct |RMI Service for Fault and Performance Manager |

|MFPMnmsi |*5021 |TCP |http |In |NMSI Server Daemon |

|Postgresql |5234 |TCP |psql |In |PostgreSQL Database Server |

|MFPMtrap |162 |UDP |SNMP |In |Incoming SNMP Traps |

|Tomcat |80 |TCP |http |In |Tomcat Web/Servlet Server |

|Httpd |8080 |TCP |http |In |Apache Web Server (Integrated Management Database) |

|Httpd |443 |TCP |https |In |Apache Secure Web Server (Integrated Management |

| | | | | |Database) |

|Ssh |22 |TCP |Ssh |In |Incoming SSH access |

|telnet |23 |TCP |telnet |In |Optional: Incoming Telnet |

|ftp |21 |TCP |ftp |In |Optional: Incoming FTP |

| | | | | | |

|Remote Port |161 |UDP |SNMP |Bi |SNMP Access for Mgmt |

|Remote Port |23 |TCP |telnet |Out |Telnet access to elements |

|Remote Port |22 |TCP |Ssh |Out |SSH access to elements |

|Remote Port |25 |TCP |Smtp |Out |Email server access |

|Remote Port |80 |TCP |Html |Out |Web client access to elements |

|Remote Port |*5022 |TCP |Ssh |Out |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 |

|Remote Port |*5023 |TCP |telnet |Out |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 |

|Remote Port |2447 |TCP |OV-API |Out |NMSI: HP OpenView Solaris ovwdb service daemon |

| |ovwdb | | | | |

|Remote Port |3700+ |TCP |OV-API |Out |NMSI: HP OpenView GUI Map API Access (port=3700 + gui|

| | | | | |display number) |

* These port numbers are not fixed and may vary based upon previously installed co-resident application services on the Linux Server or on the NMSI Windows/Solaris server.

3 MVMAINT (maintenance package):

Directories:

/opt/avaya/mvmaint maintenance package configuration files

/opt/avaya/mvmaint/bin executable scripts for maintenance and support

/opt/avaya/VisAbility/html server status web pages

/opt/avaya/VisAbility/html/WEB-INF/cgi server status CGI scripts

/var/avaya/mvmaint log files

/etc/ppp/peers/avaya ppp configuration file

/usr/share/gnome/apps/Avaya KDE/Gnome desktop integration

/usr/share/pixmaps/Avaya KDE/Gnome desktop integration (icons)

/usr/share/desktop-menu-files KDE/Gnome desktop integration (menus)

/usr/ncsc Services ‘ncsc’ login home directory

Logins created: ncsc, root2

Groups created: avaya

Files:

/opt/avaya/mvmaint/mvmaint.conf Integrated Management maintenance task configuration file

/etc/passwd modified by the installer; adds service logins

/etc/inittab modified by the installer; adds remote maintenance port monitoring task

/etc/ppp/options.ttyS0 modified by the installer; adds remote services PPP configuration

/etc/hosts modified by the installer; adds IP and node-ame configuration

/etc/cron.allow modified by the installer; adds scheduled maintenance tasks

4 Proxy Agent (PA):

Directories:

/opt/avaya/mpa Proxy agent executables, configuration and agent cache files

/opt/avaya/VisAbility/html/WEB-INF/cgi/mpa CGI scripts for Proxy Agent

/usr/share/gnome/apps/Avaya/MPA KDE/Gnome desktop integration

/usr/share/pixmaps/Avaya KDE/Gnome desktop integration (icons)

/usr/bin location of server-level process executables for Proxy Agent

/usr/sbin location of Proxy Agent configuration and daemon tools

Files:

/etc/services * PALM###, DPA###, and MPATRAP services are added

/etc/rc.d/init.d/mpa sets up for autostart/stop of Proxy Agent server at boot/shutdown

/etc/profile.d/mpa.sh shell login environment setup script for Proxy Agent

/etc/sysconfig/mpa boot time configuration for Proxy Agent services

* NOTE: These are the default port #’s entered into the services file (see Table 2 below). The port numbers can change if they are already in use by another service.

Table 2: Proxy Agent Network Communication Information

|Service Alias |Default Port |Transport |Protocol |Direction |Description |

|Postgresql |5234 |TCP |Psql |In |PostgreSQL Database Server |

|Snmp |161 |UDP |SNMP |In |Incoming SNMP requests |

|Tomcat |80 |TCP |http |In |Tomcat Web/Servlet Server |

|Httpd |8080 |TCP |http |In |Apache Web Server (Integrated Management |

| | | | | |Database) |

|Httpd |443 |TCP |https |In |Apache Secure Web Server (Integrated |

| | | | | |Management Database) |

|Ssh |22 |TCP |Ssh |In |Incoming SSH access |

|telnet |23 |TCP |telnet |In |Optional: Incoming Telnet |

|ftp |21 |TCP |ftp |In |Optional: Incoming FTP |

|PALM### |5010-5024 |TCP |RMATS |In |Incoming IP VS alarm services |

|DPA### |4200-4350 |UDP |SNMP |In |Proxy Agent Sub-Agent process connection to|

| | | | | |SNMP master agent |

|MPATRAP |5009 |UDP |SNMP |In |Proxy Master Agent Trap Port |

| | | | | | |

|Remote Port |162 |UDP |SNMP |Out |SNMP Traps Sent to Network Management |

| | | | | |System |

|Remote Port |23 |TCP |telnet |Out |Telnet access to elements |

|Remote Port |Customer-defined |TCP |telnet |Out |CLAN SAT Service ports on Voice Systems – |

| | | | | |depends on voice system SAT service |

| | | | | |administration for port number Note: The |

| | | | | |Linux-based Media Servers are not supported|

| | | | | |by Proxy Agent |

Sym Link created from /usr/local/avaya/mpa ( /usr/g3-ma

Logins created: g3maadm

groups created: g3ma

5 Multi-Site Administration (MSA):

Directories:

/var/avaya/msa all MultiSite Administration system, switch data & setting files. All files owned by 'mcm'

/var/avaya/msa/pc all MultiSite Administration web files including the client and terminal emulator JAR's. All files owned by 'root' configurations, scripts, client GUI layout definitions, station types

/var/avaya/msa/bin: all executable MultiSite Administration main programs (mcmstart and mcmstop)

/var/avaya/msa/utils: all executables of MultiSite Administration utility programs

/var/avaya/msa/database: all MultiSite Administration server-based database files, users profiles, passwords, others

/var/avaya/msa/switch: cache data of all switches, this is the key directory for MultiSite Administration ops. This directory will be expanded when number of switches increases, or number of stations are growing larger per switch.

/var/avaya/msa/public: configurations, templates

/var/avaya/msa/pipe: FIFO files (a.k.a. named pipe) for Linux inter-process communications (IPC)

/var/avaya/msa/logs: main directory for software trace/error logs, event logs, others

/usr/lib MultiSite Administration shared libraries install location

logins created: mcm

groups: avaya

Files:

/etc/services: mcm, mcmlogin services are added

/etc/xinetd.d/mcm: define the details of mcm service – listens for Client connections

/etc/xinetd.d/mcmlogin: define the details of mcmlogin service – authenticates client login

/etc/syslog.conf: mcm reserves "local1" for its software syslog

/etc/logrotate.d/mcmlog: for rotating the syslog files up to 7-day history

/etc/init.d/msa-server: adds the msa-server service (script); allows control via sysconfig tools for starting, stopping, restarting and checking status of MultiSite Administration; runs at levels 2, 3 and 5

/var/spool/cron/mcm: adds crontab file for login “mcm”; for control of all the scheduled maintenance tasks in MultiSite Administration (found in the application under MSA Manager>Task Scheduler)

Table 3: MultiSite Administration Network Communication Information

|Service Alias |Default Port |Transport |Protocol |Direction |Description |

|Posgresql |5234 |Tcp |psql |In |PostgreSQL Database Server |

|Tomcat |80 |Tcp |http |In |Tomcat Web/Servlet Server |

|Httpd |8080 |Tcp |http |In |Apache Web Server (Integrated Management Database) |

|Httpd |443 |Tcp |https |In |Apache Secure Web Server (Integrated Management |

| | | | | |Database) |

|Ssh |22 |Tcp |Ssh |In |Incoming SSH access |

|telnet |23 |Tcp |telnet |In |Optional: Incoming Telnet |

|ftp |21 |Tcp |ftp |In |Optional: Incoming FTP |

|Mcm |6609 |Tcp |http |In |Client – server communication |

|Mcmlogin |6614 |Tcp |http |In |Client – server authentication |

| | | | | | |

|Remote Port |23 |Tcp |telnet |Out |Telnet access to elements |

|Remote Port |22 |Tcp |Ssh |Out |SSH access to elements |

|Remote Port |25 |Tcp |Smtp |Out |Email server access |

|Remote Port |80 |Tcp |Html |Out |Web client access to elements |

|Remote Port |*5022 |TCP |Ssh |Out |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 |

|Remote Port |*5023 |Tcp |telnet |Out |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 |

|Remote Port |21 |Tcp |ftp |Out |ftp capability for remote backup and reports! |

6 Integrated Management Database (IMD)

Directories:

/opt/avaya/imd Integrated Management Database base directory

/opt/avaya/imd/bin Integrated Management Database executables

/var/avaya/db Integrated Management Database actual database

/var/www/html/imdadmin web page for Integrated Management Database

/var/avaya/imd Log files for Integrated Management Database

/usr/include Integrated Management Database Header files

/usr/lib libimd.so file

/usr/share/gnome/apps/Avaya KDE/Gnome desktop integration

logins created: imd

Files:

/etc/init.d/postgresql sets up for autostart/stop of postgreSQL database server at boot/shutdown

/etc/logrotate.d/imlog configuration file for rotation of syslog and userlog files for Integrated Management Database

Table 4: Integrated Management Database Network Communication Information

|Service Alias |Default Port |Transport |Protocol |Direction |Description |

|Postgresql |5234 |Tcp |psql |In |PostgreSQL Database Server |

|Tomcat |80 |Tcp |http |In |Tomcat Web/Servlet Server |

|Httpd |8080 |Tcp |http |In |Apache Web Server (Integrated Management |

| | | | | |Database) |

|Httpd |443 |Tcp |https |In |Apache Secure Web Server (Integrated |

| | | | | |Management Database) |

|Ssh |22 |Tcp |Ssh |In |Incoming SSH access |

|telnet |23 |Tcp |telnet |In |Optional: Incoming Telnet |

|ftp |21 |Tcp |ftp |In |Optional: Incoming FTP |

| | | | | | |

7 PostgreSQL Database Management System

The Avaya Integrated Management custom version of the PostgreSQL database RPMs (i.e. postgres-*-7.2.4-2_0_71) are installed in standard RedHat PostgreSQL database locations including the following directories:

Directories:

/usr/bin

/usr/share/doc

/usr/share/man

/usr/lib

/usr/share/locale

/etc/rc.d/init.d

/var/lib/pgsql

/usr/share/pgsql

/usr/include

/usr/lib/perl5/site-perl/5.6.1/i386-linux

Logins Created: postgres

Groups Created: postgres

8 Tomcat Web Server

The tomcat web server installs into the standard Apache/Tomcat Red Hat Linux installation locations including the following directories:

Directories:

/etc/logrotate.d

/etc/rc.d/init.d

/etc/tomcat4

/usr/bin

/usr/share/doc/tomcat4-4.1.24

/var/tomcat4

/var/log/tomcat4

/var/cache/tomcat4

Logins Created: tomcat4

Groups Created: tomcat4

9 PHP/PHP-PGSQL

PHP and PHP-PGSQL are Red Hat Linux standard support RPMs that are included on the CD as a matter of convenience. These RPMs will install files into the following locations, if the php or php-pgsql RPMs are not already on the system and at minimum version levels from the version that is shipped with the Integrated Management suite CD. Once installed, up2date from RedHat Network may update either of these packages to newer versions if needed. Files for these RPMs will be installed in the following locations:

Directories:

/usr/bin

/usr/lib/apache

/usr/share/doc/php-4.1.2

/usr/share/pear

/usr/lib/php4

Files:

/etc/php.ini

Conclusion

With the information in this white paper, the customer has been provided with the relevant information about the Integrated Management Linux-based applications. This information will allow the customer to make an assessment of the necessary protocols and services needed to run on their Linux server.

Additional References

1. Avaya™ Integrated Management Release 2.1 Configuring Red Hat Linux, 555-233-152, Issue 4, July 2004, .

2. Avaya™ Fault and Performance Manager Release 2.1 Configuration, 555-233-138, Issue 6, July 2004, .

3. Avaya™ Integrated Management Database Release 2.1 Configuration, 14-300039, Issue 2, July 2004, .

4. Avaya™ MultiSite Administration Release 2.1 Configuration, 555-233-137, Issue 6, July 2004, .

5. Avaya™ Proxy Agent Release 2.1 Configuration, 555-233-139, Issue 6, July 2004, .

6. Avaya™ Integrated Management Release 2.1 Advanced Converged Management Installation and Upgrade, 555-233-160, 700315997, Issue 3, July 2004, .

| |

|©2004 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. Users are responsible for their application of any products specified in this White Paper. |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download