HowTo: Quickstart on System Manager and Session Manager
From Jaymzworld
Contents |
Introduction
This page covers the initial installation and configuration of System Manager (IMSM) and Session Manager (SM). It does not cover adding Communication Manager into the mix, creating dial plans, or routing policies. When you are done you will have an IMSM instance that can talk to and control a SM instance, but you won't be at the stage of making calls yet. That will be covered in a different How To. For upgrades, see Ugrading to System Manager 6.0 or Installing Session Manager 6.0.
Configuring System Manager
Prerequisites
At a minimum, you will need the following to run System Manager (IMSM)
The following are the minimum hardware requirements for IMSM. If you have an Avaya S8510, it meets these requirements.
- A machine with a minimum Intel Xeon Dual Core 3Gig processor.
- It's recommended to have at least 4GB RAM installed.
- 2GB of free disk space.
The following are the minimum software requirements for IMSM.
- One of the following operating systems installed:
- Solaris 10 (SPARC)
- Red Hat Linux Enterprise 5.2 (CentOS should work as well)
- Solaris x86
- Java Runtime Environment (JRE) 1.6 update 11. If you don't have this installed, the installer will do it for you.
- If you don't have PostgreSQL 8.2.6 installed, the installer will do it for you.
- SELinux should be set to disabled In /etc/sysconfig/selinux. If you have to change this, reboot the machine after making the change.
Installing the software
The following software will be installed:
- System Manager (aka Panther)
- Includes Postgres 8.2.6 database
- Java 1.6 will be automatically installed if not detected
- Session Manager Element Manager
- SIP A/S Console
We will use the install.sh script to install IMSM.
[admin@imsm asm]$ ./install.sh --help
Usage: install.sh [OPTION]
-a, --auto Auto install
-h, --help Displays this help
-v, --version Displays installer version
--rollback Uninstall current version of System Manager,
reverting to the previously installed version if
one exists.
--nosm Do not install System Manager components
- only upgrades Session Manager Element Mgr.
--clean Force a clean install (remove all System Manager data)
- *WARNING: All Postgres data will be lost
--nosipas Do not install SIP A/S Console
--nopatch Do not install patch
--nosem Do not install Element Manager
-d, --debug Debug mode
Once you've and mounted the installer CD, extract its contents to disk. In this example the directory /tmp/asm was created and used.
[root@imsm ~]# mkdir /tmp/asm/ [root@imsm ~]# unzip /media/AVMGMT-1.1.4.0.111013/avmgmt-installer-1.1.4.0.111013.zip -d /tmp/asm/
Now change directory to /tmp/asm and begin the install.
[admin@imsm ~]$ cd /tmp/asm/ [root@imsm ~]# ./install.sh Avaya System Manager Installation for imsm started at: Mon Jun 29 10:38:29 CDT 2009 Log file is /var/log/Avaya/system_manager_master_install_log-2009-06-29-10:38:29 Installer Version: 1.1.4.0.111013 Checking for JDK jdk-1.6.0_11-fcs ...
The System Manager base software is installed first.
############################################################ # Starting the base System Manager install at: Mon Jun 29 10:38:32 CDT 2009 # This part of the installation will take 20 - 30 minutes # mostly in the [Processing package: System Manager] step ############################################################ Launching System Manager Installer Inflating installer file... Correct version of Postgres not detected Correct version of Postgres not detected - doing a clean install Pre-install clean Removing postgres Stopping Spirit Stopping HTTPD
If PostgreSQL is not installed, or the wrong version is, the installer will update the system.
Correct version of Postgres not detected
Correct version of Postgres not detected - doing a clean install
grep: /root/.profile: No such file or directory
/usr/bin/id: postgres: No such user
Enter the Encryption Key :Please Wait
Log file has been created at location: /tmp/avaya_aura_system_manager_install-log_2009-06-29_10.39.03.txt
[ Starting automated Installation ]
User Agreed to the licence terms
Checking if the system has sufficient space as required by the selected packs.
Available Space: 207.89 GB
Total space Required: 828.29 MB
[ Starting processing ]
Starting process Pre-Install Configuration Audit (1/2)
Checking OS_Version...
OS version: PASS
Required:Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Actual:Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Checking RAM...
RAM: PASS
Required:3984588 kB
Actual:8306924 kB
Checking Java Version...
Java Version Information: PASS
Required:1.6
Actual:1.6
Checking Java Vendor...
Java Vendor Information: PASS
Required:Sun Microsystems Inc.
Actual:Sun Microsystems Inc.
Checking JAVA_HOME Env Var...
JAVA_HOME Env Var: PASS
Checking LoopBack Address Entry...
LoopBack Address Entry: PASS
Checking Host Entry...
Host Entry: PASS
Checking SNMP RPM Status...
SNMP RPM Status: PASS
Starting process Pre-Install Configuration Audit (2/2)
Checking SELINUX disability status...
disabled
SELINUX disability status: PASS
(success)
[ Processing finished ]
[ Starting to unpack ]
[ Processing package: SAL Agent (1/4) ]
.............
[ Processing package: Postgres (2/4) ]
..........
[ Processing package: JBoss (3/4) ]
....................
[ Processing package: System Manager (4/4) ]
......
Parsing files
..............
File execution started for pack : SPIRIT
....
File execution started for pack : PostgresID
..................
File execution started for pack : JBossID
..
File execution started for pack : MgmtID
............
[ Unpacking finished ]
[ Starting processing ]
Starting process Post-Install Configuration Audit (1/4)
Checking Product Installation...
For MgmtID: PASS
(success)
Starting process Post-Install Configuration Audit (2/4)
Checking Product Installation...
For PostgresID: PASS
(success)
Starting process Post-Install Configuration Audit (3/4)
Checking Product Installation...
For SPIRIT: PASS
(success)
Starting process Post-Install Configuration Audit (4/4)
Checking Product Installation...
For JBossID: PASS
(success)
[ Processing finished ]
[ Writing the uninstaller data ... ]
output.response.file /opt/Avaya/autoInstall_AVAYA_AURA_SYSTEM_MANAGER.properties generated
[Automated Installation Completed with Warnings!]
Log file has been moved to location:
/opt/Avaya/install_logs/avaya_aura_system_manager_install-log_2009-06-29_10.39.03.txt
from location: /tmp/avaya_aura_system_manager_install-log_2009-06-29_10.39.03.txt
System Manager Install User Responses:
Modifying pg_hba_conf
Modifying pg_hba.conf
Restarting Postgres
Stopping postgresql service: [ OK ]
Starting postgresql service: [ OK ]
END System Manager Install
The SIP A/S console is installed next.
############################################################ # Starting SIP A/S Console install at: Mon Jun 29 10:44:08 CDT 2009 # This part of the installation will take less than 5 minutes ############################################################ START SIP A/S Console Install Uninstalling SIP AS Console Enter the Encryption Key :Please Wait Log file has been created at location: /tmp/avaya_uninstaller_uninstall-log_2009-06-29_10.44.08.txt [ Starting automated Uninstall ] output.response.file /opt/Avaya/autoUninstall.properties generated [Automated Uninstall Completed !] Log file has been moved to location: /opt/Avaya/install_logs/avaya_uninstaller_uninstall-log_2009-06-29_10.44.08.txt from location: /tmp/avaya_uninstaller_uninstall-log_2009-06-29_10.44.08.txt Launching SIP A/S Console Installer Enter the Encryption Key :Please Wait Log file has been created at location: /tmp/avaya_sip_as_management_console_install-log_2009-06-29_10.44.09.txt [ Starting automated Installation ] User Agreed to the licence terms Checking if the system has sufficient space as required by the selected packs. Available Space: 207.03 GB Total space Required: 14.64 MB [ Starting to unpack ] [ Processing package: SIP/AS Console Pages (1/1) ] .......... Parsing files File execution started for pack : Pack.SIPAS.console .. [ Unpacking finished ] [ Writing the uninstaller data ... ] output.response.file /opt/Avaya/autoInstall_Avaya_SIP_AS_Management_Console.properties generated [Automated Installation Completed !] Log file has been moved to location: /opt/Avaya/install_logs/avaya_sip_as_management_console_install-log_2009-06-29_10.44.09.txt from location: /tmp/avaya_sip_as_management_console_install-log_2009-06-29_10.44.09.txt
Finally, the System Manager Element Manager software is installed.
############################################################
# Starting the SM Element Manager install at: Mon Jun 29 10:44:34 CDT 2009
# This part of the installation will take about 10 minutes
############################################################
Launching Element Manager Installer
Service was not running
Stopping SPIRIT Agent Application 1.0.25...
Stopped SPIRIT Agent Application 1.0.25.
Please Wait
Log file has been created at location: /tmp/elementmanager_install-log_2009-06-29_10.44.37.txt
[ Starting automated installation ]
[ Starting processing ]
Starting process Pre-Install Configuration Audit (1/1)
Checking OS_Version...
OS version: PASS
(Required: Red Hat Enterprise Linux Server release 5.1)
(Actual: Red Hat Enterprise Linux Server release 5.1 (Tikanga))
Checking RAM...
RAM: PASS
(Required: 2 GB)
(Actual: 8306924 kB)
Checking Disk Space...
Available disk space for partition containing /opt: PASS
(Required: 500 MB)
(Actual: 217067828 kB)
[ Processing finished ]
Checking if the system has sufficient space as required by the selected packs.
Available Space: 222277447680
Total space Required: 16790331
[ Starting to unpack ]
[ Processing package: ElementManager (1/1) ]
[ Unpacking finished ]
[ Writing the uninstaller data ... ]
output.response.file /opt/Avaya/autoInstall_ElementManager.properties generated
[Automated Installation Completed !]
Log file has been moved to location: /opt/Avaya/elementmanager_install-log_2009-06-29_10.44.37.txt from location:
/tmp/elementmanager_install-log_2009-06-29_10.44.37.txt
STARTING SERVICES...
Installation completed at: Mon Jun 29 10:48:00 CDT 2009
Other installation notes
Use ./install.sh --clean to force a clean install. This will clear out the database and do a fresh install. This option is quite destructive and should only be used under circumstances where you need to remove the entire contents of the PostgreSQL database.
Use ./install.sh --nosm --nosipas to bypass the installation of the base System Manager and SIP AS console components and only install a new SM Element Manager. This is normally only used in a development environment.
For upgrades, just use the ./install.sh script and it will recognized that IMSM has already been installed, and perform an upgrade.
To uninstall, change directory into the base directory of the installer. The script uninstall.sh should be in this directory. Execute the script, (./uninstall.sh) and enter yes when prompted for confirmation. You will be prompted to log out of the current terminal and log back in (as to restore your environment to its state before a System Manager installation was executed).
Post-Installation configuration
The System Manager (IMSM) Common Console is the management interface for Session Manager. Access it at the URL of https://SystemManagerhostname/IMSM.
SIP Domain
First off, create the SIP domain to enable the SM to use domain-based routing. This information is used to determine if a SIP user is part of the SIP network.
Locations
Create Locations as needed. These are used to set up and configure gateway and user locations. Call processing uses locations to determine the location of the calling and the called gateways or users. The IP address of the device determines the current physical location of the caller or the called user. Session Manager matches the IP address against the patterns defined on location screens. If there is no match in the IP address patterns, Session Manager uses the SIP entity's location as the location.
Session Manager uses the calling user location information to calculate the destination where the call has to go (which could be the final destination or the next hop). This is also known as originating location based routing.
Locations are also used to limit the number of calls coming out of or going to a physical location. This is useful for those locations where the network bandwidth is limited. This is also known as Call Admission Control (CAC). You can enable CAC in Session Manager by specifying Average bandwidth per call and Managed Bandwidth on the Locations screen. If the Managed Bandwidth field has a non-blank value, Session Manager keeps track of the bandwidth in use based on the calls coming out of and going to that specific location and denies new calls when the bandwidth in use reaches the limit.
If the Managed Bandwidth field is blank for a location, no CAC is done for that location.
SIP Entities
Create a SIP Entity for the Session Manager, CM, SIP/PSTN Gateways, SIP Trunks, Outbound Proxy, etc. For Session Manager, the IP address listed here is for the SM100 card, not the server management interface. This is how the SM100 will get its IP information. Note that SM must be added as a SIP Entity before it can be added under Session Manager Administration.
To administer minimal routing via Session Manager, you need to configure a SIP entity of type CM and a second SIP entity of type Session Manager.
Session Manager administration
Now add the Session Manager. SM instances must be administered as Management Access points to allow them to join the network of SM instances in an enterprise. After the SM instance has been added to the ASM Element Manager then the SM instance will be able to participate in data replication. Additionally, various other SM Element Manager status and monitoring screens will work because communications between the SM Element Manager and the SM instance will be enabled.
The IP address used here is the management interface (eth0).
Trust Management
Session Manager uses the enrollment password during the initial installation and deployment process. This password is also referred to as the certificate enrollment password. Create the certificate password that you will use when installing Session Manager.
NOTE: Select at least ten certificates per Session Manager instance
The Generate button does not save the password, it just generates a random password. Press the Done button to save the password.
You should now be ready to install and configure Session Manager.
Configuring Session Manager
Installing the software
If you've received an Avaya branded S8510 (Dell 1950) server, then all software needed for session manager (SM) has been loaded already. To set up the system, log in as craft and run the command SMnetSetup.
-bash-3.2$ ./SMnetSetup Avaya Session Manager OS initial configuration
In the following menus you'll setup the SM IP addresses. The S8510 comes with 2 GB Ethernet ports, and the quad port SM100 (ASSET) card. At least one of the GB Ethernet ports will be used to link to system manger (IMSM) for management. At least one of the ports on the SM100 will be used for SIP traffic. You will NOT be administering the SM100 as part of these steps.
The following two menus allow you to assign IP addresses and DNS servers.
Press ENTER to run the RedHat Linux Network Configuration tool
Use this tool to configure the eth0 network interface and your local
DNS settings. Do not make any changes to the eth1 network interface
as it is used by Avaya Services.
âââââââ⤠Select Action ââââââââ
â â
â Edit a device params â
â Edit DNS configuration â
â â
â â
â â
â âââââââââââââ ââââââââ â
â â Save&Quit â â Quit â â
â âââââââââââââ ââââââââ â
â â
â â
âââââââââââââââââââââââââââââââ
Note that eth1 was listed first. Don't modify its settings when eth0 is what you're really looking for. eth1 is reserved for Avaya services, so it shouldn't be touched at all.
ââââââââââââââââââââââââââââ⤠Select A Device ââââââââââââââââââââââââââââââ
â â
â eth1 (eth1) - Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet â
â eth0 (eth0) - Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet â
â eth2 (eth2) - Intel Corporation 82571EB Gigabit Ethernet Controller â
â eth3 (eth3) - Intel Corporation 82571EB Gigabit Ethernet Controller â
â <New Device> â
â ââââââââ ââââââââââ â
â â Save â â Cancel â â
â ââââââââ ââââââââââ â
â â
â â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
DHCP is shown as an option below for configuring this interface. Although there is nothing stopping you from selecting DHCP here, there is no software installed on the S8510 to support the assignment of IP addresses through DHCP. Therefore, ignore the DHCP option and assign the required static address.
ââââââââ⤠Devernet Configuration ââââââââââ
â â
â â
â Name eth0________________ â
â Device eth0________________ â
â Use DHCP [ ] â
â Static IP 10.0.24.10__________ â
â Netmask 255.255.255.0_______ â
â Default gateway IP 10.0.24.1___________ â
â â
â ââââââ ââââââââââ â
â â Ok â â Cancel â â
â ââââââ ââââââââââ â
â â
â â
âââââââââââââââââââââââââââââââââââââââââââ
Here you assign the hostname and IP addresses of any Domain Name servers on your network.
ââââââ⤠DNS configuration âââââââ
â â
â â
â Hostname asm____________ â
â Primary DSN 10.0.5.100_____ â
â Secondary DNS _______________ â
â Tertiary DNS _______________ â
â Search iptlab.com_____ â
â â
â ââââââ ââââââââââ â
â â Ok â â Cancel â â
â ââââââ ââââââââââ â
â â
â â
âââââââââââââââââââââââââââââââââ
Select the appropriate time zone, and verify date and time.
configure local timezone
âââââââââ⤠Timezone Selection ââââââââââ
â â
â Select the timezone for the system. â
â â
â America/Boise â â
â America/Cambridge_Bay â â
â America/Campo_Grande â® â
â America/Cancun â â
â America/Caracas â â
â America/Cayenne â â
â America/Cayman â â
â America/Chicago â â
â â
â [*] System clock uses UTC â
â â
â ââââââ ââââââââââ â
â â OK â â Cancel â â
â ââââââ ââââââââââ â
â â
â â
ââââââââââââââââââââââââââââââââââââââââ
Configure local date and time
Enter Date in MM/DD/YYYY format (i.e. 12/25/2008)
[07/01/2009]
Enter Time in HH:MM 24 hour clock format (i.e. 13:30)
[09:13]
Is 07/01/2009 09:13 correct?
[y]:
System Clock: Wed Jul 1 09:13:01 CDT 2009
Hardware Clock: Wed 01 Jul 2009 09:13:01 AM CDT -0.000356 seconds
Time and Date has been set. Enter y to continue or n to exit
[y or n]: y
If you are using NTP on your network (and you should be), configure the IP addresses of the remote servers here.
Checking NTP... NTP not currently running. Would you like to enable NTP? [yes] : Starting ntpd: [ OK ] NTP is currently running Enter IP/FQDN of Primary NTP Server [10.0.5.100] : Enter IP/FQDN of Secondary NTP Server (or 'none') [] : Enter IP/FQDN of Teritiary NTP Server (or 'none') [] :
The first time you run this script you will create a customer account for subsequent maintenance purposes. If you are running this script at a later time, it will ask if you want to modify the account you created earlier.
Current Customer Login is admin Keep this login? [y]: Set password for Customer Login [admin] Changing password for user admin. New UNIX password: Retype new UNIX password: passwd: all authentication tokens updated successfully.
Now enter the IP address of your IMSM instance. As you can see, an address had already been entered before, and it now shows as the default value.
Enter the IP Address of the System Manager server that will be used to manage this Session Manager server. [10.0.24.253] :
The script will now show you a summary of your settings. Make sure everything is right.
Verify the settings below: Sysname=asm hosts for ETH0=asm.iptlab.com asm DNS Domain=iptlab.com DNS Search=iptlab.com DNS Server1=10.0.5.100 DNS Server2= NTP Status=Enabled NTP Server1=10.0.5.100 NTP Server2= NTP Server3= Eth0 Boot Protocol=static ETH0 IP Address=10.0.24.10 System Manager IP=10.0.24.253 Customer Login=admin Press ENTER to continue or Ctrl-C to abort
When you press enter your changes will be initiated.
Updating installation properties file...
Configuring hosts file...
Restarting Network Services
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Configuring ntp.conf file...
Shutting down ntpd: [ OK ]
Starting ntpd: [ OK ]
Avaya Session Manager OS Platform setup is complete.
Checking network connections...
Checking DNS settings...
The System Manager IP address is resolving in DNS to a hostname of
imsm.iptlab.com. If this does not match the host name of the System
Manager server, Session Manager will not function properly. Make
sure your DNS server(s) have the correct hostname before proceeding.
Press ENTER to continue
Now reconfiguring ASM on this server.. this will take a while
Avaya Session Manager Installation started at Wed Jul 1 09:18:13 CDT 2009
auto install selected
Stop Watchdog
Stop spirit
Stopping SPIRIT Agent Application 1.0.24...
SPIRIT Agent Application 1.0.24 was not running.
Running cleanSM.sh ...
Stopping JBoss Application Server (Session Manager)...
JBoss Application Server (Session Manager) was not running.
Stopping JBoss Application Server (Session Manager)...
JBoss Application Server (Session Manager) was not running.
Remove /opt/Avaya/Session_Manager
Remove /opt/Avaya/bin
Stop and remove spiritAgent
Stopping SPIRIT Agent Application 1.0.24...
SPIRIT Agent Application 1.0.24 was not running.
Remove /opt/Avaya/SPIRIT
Remove watchdog rpm cs_watchd-3.2.6-444
WARNING: buconfig does not exist. Backup set not removed.
Remove asset rpm asset-gefanuc-1.1.3.0.18003-1
Removing .cer protection
Stopping ASSET HW service
Detected PASS2.1 board
Stopping ASSET SW on board
Stopping Board....
ASSET board stopped[ OK ]
Removing ASSET HW service
Finalize ASSET HW uninstall
Deleting asset user:asset from the hosting server
Deleting target related users files (passwd,group,shadow & gshadow)
Deleting logrotation file /etc/logrotate.d/assetLogRotate
Deleting log files links /var/log/asset.log , /var/log/spirit_asset.log,
/var/log/tracer_asset.log
/usr/bin/chattr: No such file or directory while trying to stat
/opt/Avaya/asset/packages/asset*
cleanSM.sh completed
Checking for JDK jdk-1.6.0_11-fcs ...
JAVA_HOME=/usr/java/jdk1.6.0_11
Stop SIPAS
Stopping the Management Server ...
Stopping the Service Director ...
Stopping the Service Host 0 ...
Stopping the Logging Extraction Service ...
Stopping the Log Harvester Agent ...
Running cleanSIPAS.sh ...
Stop and remove ManagementServer
Stopping the Management Server ...
Stop and remove ServiceDirector
Stopping the Service Director ...
Stop and remove ServiceHost0
Stopping the Service Host 0 ...
Stop and remove LoggingExtractionService
Stopping the Logging Extraction Service ...
Stop and remove LogHarvesterAgent
Stopping the Log Harvester Agent ...
Remove /opt/Avaya/SIPAS
Stop and remove spiritAgent
Remove SIPAS SPIRIT
cleanSIPAS.sh completed
Launching SIP A/S Installer
auto install SIPAS using autoInstall_SIPAS_SM_SingleBox.properties
INFO : Default Configuration file (defConfParam.properties) not found
Please Wait
Log file has been created at location:
/tmp/avaya_sip_application_server_install-log_2009-07-01_09.18.28.txt
[ Starting automated Installation ]
User Agreed to the licence terms
Checking if the system has sufficient space as required by the selected packs.
Available Space: 71.76 GB
Total space Required: 225.86 MB
[ Starting to unpack ]
[ Processing package: SIP A/S Logging Extraction Service (1/7) ]
[ Processing package: Pack.SIPAS (2/7) ]
[ Processing package: SIP A/S Management Server (3/7) ]
[ Processing package: SIP A/S Service Host (4/7) ]
[ Processing package: SIP A/S Service Director (5/7) ]
[ Processing package: SIP A/S Log Harvester Agent (6/7) ]
[ Processing package: SPIRIT Agent (7/7) ]
[ Unpacking finished ]
[ Writing the uninstaller data ... ]
output.response.file
/opt/Avaya/autoInstall_Avaya_SIP_Application_Server.properties generated
[Automated Installation Completed !]
Log file has been moved to location:
/opt/Avaya/install_logs/avaya_sip_application_server_install-log_2009-07-01_09.18.28.txt
from location:
/tmp/avaya_sip_application_server_install-log_2009-07-01_09.18.28.txt
fix cli.properties to use 10.0.24.10
Stop JBoss servers if running
Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: filter [ OK ]
Unloading iptables modules: [ OK ]
Launching Session Manager/System Manager Installer
Previous install autoInstall_Session_Manager.properties found
copy and modify autoinstall_Session_Manager.properties
INFO : Default Configuration file (defConfParam.properties) not found
Enter the Encryption Key :Please Wait
Log file has been created at location:
/tmp/session_manager_install-log_2009-07-01_09.19.35.txt
[ Starting automated installation ]
[ Starting processing ]
Starting process Pre-Install Configuration Audit (1/1)
Checking OS_Version...
OS version: PASS
(Required: Red Hat Enterprise Linux Server release 5.1)
(Actual: Red Hat Enterprise Linux Server release 5.3 (Tikanga))
Checking RAM...
RAM: PASS
(Required: 2 GB)
(Actual: 8306808 kB)
Checking Disk Space...
Available disk space for partition containing /opt: PASS
(Required: 500 MB)
(Actual: 75096032 kB)
[ Processing finished ]
Checking if the system has sufficient space as required by the selected packs.
Available Space: 76898328576
Total space Required: 239969762
getParams() Failed: java.lang.ClassCastException: com.avaya.panther.panels.SimpleProcessingClient
cannot be cast to com.izforge.izpack.panels.PasswordGroup
[ Starting to unpack ]
[ Processing package: Postgres Database Server (1/2) ]
[ Processing package: Session Manager (2/2) ]
[ Unpacking finished ]
[ Starting processing ]
Starting process Updating System Packages (1/3)
Installing system level updates...
Performing Automatic RPM installations...
Performing Manual RPM installations...
Performing post install steps...
Post install steps finished
System Update Install Succeeded!
Starting process Starting Watchdog Software (2/3)
[ OK ]
Watchd started...
Starting process Configuring Trust Management (3/3)
Waiting for Session Manager components to startup...
Waiting for Session Manager components to startup...
Initializing Session Manager Trust Management
Failed to update Trust Management for Session Manager
[ Processing finished ]
[ Writing the uninstaller data ... ]
output.response.file /opt/Avaya/autoInstall_Session_Manager.properties generated
[Automated Installation Completed !]
Log file has been moved to location: /opt/Avaya/session_manager_install-log_2009-07-01_09.19.35.txt
from location: /tmp/session_manager_install-log_2009-07-01_09.19.35.txt
Restoring Asset's certificates
The next step is key as it is what will allow SM and IMSM to speak to each other.
Initializing Trust Management You will now be asked to enter the enrollment password that was entered on the System Manager server to allow this Session Manager to be trusted by the System Manager. Enrollment Password:
NOTE: You get one chance to enter the password correctly. If you see a message indicating that you entered it incorrectly, do not restart SM.
You can either rerun the SMnetSetup script, or use the /opt/Avaya/bin/initTM script. This script can also be used to update the enrollment password.
[admin@asm ~]$ /opt/Avaya/bin/initTM Enrollment Password: Initializing Session Manager Trust Management Finished configuring Trust Management Restarting Session Manager Maintenance shutdownsvc succeeded addsvc succeeded
If you don't enter a password, or entered the wrong one, you may see an error message like this:
Got request for end entity INBOUND_OUTBOUND_TLS with invalid password. Verify the password (expiry date and enrollment count if it exists).
After entering the password, the security layer is restarted.
Initializing Session Manager Trust Management Restarting Security Module WARNING: clean shutdown not possible. forced termination of process addsvc succeeded Restarting Session Manager Maintenance shutdownsvc succeeded addsvc succeeded Restarting Session Manager Management shutdownsvc succeeded addsvc succeeded Restarting SPIRIT Agent shutdownsvc succeeded addsvc succeeded Installation is complete /root Reconfiguration complete.
With configuration complete, you are given the option of rebooting the server. If for some reason you don't want to reboot now, just type n and reboot at your leisure.
The server should be rebooted to allow the system to boot with it's new settings. Would you like to reboot the server now? [y on n]: y Rebooting the server now... Broadcast message from root (pts/0) (Wed Jul 1 10:33:20 2009): The system is going down for reboot NOW!
Finally, set the Product ID.
Upgrades
Use the supplied ./upgrade.sh script that comes with the new load or patch.
Testing the Installation
Now that everything is installed and configured, you have to make sure it works. IMSM has a page that allows you to test various objects on the SM. This makes sure that not only can IMSM speak to SM, but that SM is configured properly as well.
- Log in to the system management interface and click Session Manager > Maintenance Tests in the left navigation pane
- Select the System Manager server in the pull-down list, and click Execute All Tests.
- If the data replication test fails, click Session Manager > Data Replication Status in the left navigation pane to identify which Session Manager is having replication problems.
- Click Session Manager > Security Module Status to display SM100 card status.
- Verify that Security Module Deployment is Up for all Session Managers.
- Click Session Manager > System State Administration in the left navigation pane.
- Verify that the installed software versions of all Session Managers are the same version and that all Session Manager servers are in the Management Enabled state.
- Click Session Manager > Maintenance Tests in the left navigation pane.
- Select each Session Manager instance, and click Execute All Tests.
- Verify that all tests show Success status.
- Note
- The SM100 card will not come up if host name resolution is not working correctly on the network. Ensure that the system manager host name is resolvable using DNS, or add an entry to the session manager's /etc/hosts file.
Software compatibility
Note that unless SM and IMSM are on the same load of software, integration may not work. If upgrading or patching your session manager installation, always make sure to do the same to the controlling system manager.
References
- Avaya "Installing and Administering Avaya Aura Session Manager". Avaya, May 4, 2009
