! "#$

  
Legal notice:

The information presented is subject to change without notice.

ALE International assumes no responsibility for inaccuracies contained

herein.

Copyright © ALE International, 2016

Disclaimer:

While efforts were made to verify the completeness and accuracy of the
information contained in this documentation, this document is provided “as
is”. To get more accurate content concerning Cross Compatibilities, Product
Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.

In the interest of continued product development, ALE International reserves

the right to make improvements to this documentation and the products it
describes at any time, without notice or obligation.

The CE mark indicates that this product conforms to the following Council
Directives:
- 2014/53/EU for radio equipment
- 2014/35/EU and 2014/30/EU for non radio equipment (including wired
Telecom Terminal Equipment)
- 2014/34/EU for ATEX equipment
- 2011/65/EU (RoHS)
  
        

Chapter 1
Reference documents

Chapter 2
Overview

Chapter 3
System Administration

 Installing packages ................................................................................. 12

 Configuring the firewall ........................................................................ 13
 Adding a static ACCEPT rule ......................................................................... 13
 Adding complex static rules ............................................................................ 14

Chapter 4
Maintenance portal

      !"  #        3/73

     

 Overview ..................................................................................................... 15

 Accessing the portal .............................................................................. 15
 Maintenance portal ................................................................................. 15
 Interface and operations ................................................................................. 15
 Easy and expert administration modes .......................................................... 18

Chapter 5
Server monitoring

 Server monitoring using AppGuard ................................................. 20

 Server monitoring using SNMP .......................................................... 23
 SNMP agent configuration .............................................................................. 23
 Verifying your configuration ............................................................................ 24
 OpenTouch MIBs ............................................................................................ 24
 OpenTouch alarms management ...................................................... 24
 Configure the OpenTouch server to send its alarms to the OmniVista 8770 . 25
 Configure alarm reception on the OmniVista 8770 ......................................... 25
 Alarm catalog .................................................................................................. 26
 Supervision of OpenTouch alarms from the OmniVista 8770 ........................ 26
 OpenTouch server supervision .......................................................... 27
 Overview ......................................................................................................... 27
 Description ...................................................................................................... 27
 System Status ................................................................................................ 28

Chapter 6
Administration and troubleshooting commands

 listtool.sh .................................................................................................... 30

 otconsole.sh command ........................................................................ 31
 timout command ...................................................................................... 32

4/73       !"  #       

      

 Information tools ..................................................................................... 33

 listerm ............................................................................................................. 33
 getVersion ...................................................................................................... 34
 getHardInfo ..................................................................................................... 35
 getaluid ........................................................................................................... 36
 collectLicenses ............................................................................................... 37
 Maintenance tools ................................................................................... 37
  ot-config.sh ..................................................................................................... 37
  otbr.sh ............................................................................................................. 42
  reset-firstsetup.sh ........................................................................................... 43
  switchover.sh .................................................................................................. 43
  VM management commands .......................................................................... 44
  CertificateTool.sh ............................................................................................ 44
  prepareUsbdisk .............................................................................................. 45
 Troubleshooting tools ........................................................................... 45
  checkAll.sh ..................................................................................................... 46
  Service ............................................................................................................ 48
  Serverstatus ................................................................................................... 49
  Ot-moni.sh ...................................................................................................... 51
  checkClock.sh ................................................................................................ 55
  checkCertificate.sh ......................................................................................... 57
  checkLicensing.sh .......................................................................................... 57
  checkdns ........................................................................................................ 59
  raidstatus ........................................................................................................ 59
  checkSystem .................................................................................................. 59
  checkCms ....................................................................................................... 60
 Log management tools ......................................................................... 61
  DLA – dynamic log activation ......................................................................... 61
  loglevel.sh ....................................................................................................... 61
  logzipper ......................................................................................................... 62
  netcapture.sh .................................................................................................. 63
  getSupport ...................................................................................................... 65
 Miscellaneous tools ............................................................................... 66
  lmutil ............................................................................................................... 66
  RoutingConfigConsole.sh ............................................................................... 67
  tsa_maintenance ............................................................................................ 72

      !"  #        5/73

     

  clean_logs_and_restart_udas.sh .................................................................... 73
  dumpxs ........................................................................................................... 73

6/73       !"  #       

   

   

The OpenTouch documentation consists in separated documents, each corresponding to a

specific aspect of necessary and optional installations/administrations.
The full set of all available documents is updated every week and can be accessed on the
BPWS TDL.
In the present document, cross-references are identified by the number in the first column of
the table below.
Part numbers are given in the last column, where the first two xx correspond to the language
code of the document.
The documents for OpenTouch are:
table 1.1: OpenTouch documentation structure
Documentation title Part number
[1] OTBE Installation Manual on a Physical Machine 8AL90504xxxx
Summary: this document describes the software layout of an
OpenTouch Business Edition on the provided hardware. Hard-
ware and software installation are explained in detailed proced-
ures. Post installation, connection and the basic configuration are
also described with procedures. Software major and minor up-
dates are explained and troubleshooting guidelines are provided.
[2] OTMS Installation Manual on a Physical Machine 8AL90512xxxx
Summary: this document describes the software layout of an
OpenTouch Multimedia Services on the provided hardware. Hard-
ware and software installation are explained in detailed proced-
ures. Post installation, connection and the basic configuration are
also described with procedures. Software major and minor up-
dates are explained and troubleshooting guidelines are provided.
[3] OTBE/OTMS Administrator Manual 8AL90505xxxx
Summary: this document describes all the necessary procedures
to implement an OpenTouch Business Edition or OpenTouch Mul-
timedia Services system: from user configuration to advanced ap-
plications, devices (including video devices), conferencing and
collaboration features, as well as call restriction management.
CAC management, backup and restore procedures and IP flows
are also detailed.
[4] Installation Manual on a Virtual Machine 8AL90507xxxx
Summary: this document describes prerequisites and topologies
for an installation of the system on a virtual machine. The installa-
tion procedure is described in detail for every system element. Li-
cense management and license updates are also explained. Ap-
pendixes provide guidelines on the recommended software install-
ation tools.

      !"  #        7/73

Chapter 1 $%  ! 

Documentation title Part number

[5] ALEDS 8AL90508xxxx
Summary: this document describes the implementation of this de-
ployment tool in the various compatible topologies. This docu-
ments includes requirements and procedures to install each soft-
ware, among which the OpenTouch. Software deployments and
updates are explained for physical and virtual machines.
[6] OpenTouch General Architecture 8AL90509xxxx
Summary: this document presents the available systems in rela-
tion to the actual customer needs. Topologies and software archi-
tectures are presented for OpenTouch Multimedia Services,
OpenTouch Business Edition, and the native contact center.
Hardware compatibilities are detailed per system.
[7] OpenTouch System Documentation 8AL90510xxxx
Summary: this document describes the services and applications
specific for Conversation users, as well as the One Number Ser-
vice for Connection users. It also includes up-to-date recommend-
ations on system security, certificates, encryption and best prac-
tices.
[8] OpenTouch Maintenance and Supervision 8AL90511xxxx
Summary: this document describes the available tools to monitor
and/or troubleshoot the OpenTouch and its ecosystem. This docu-
ment also provides guidelines on the maintenance portal and the
supervision of server(s), devices and calls. A list of useful main-
tenance command is included, with explanations and examples.
[9] OT-C2D Administrator Guide 8AL90527xxxx
[10] OT-C2D User Guide 8AL90528xxxx
[11] Description of IP flows in OpenTouch solution 8AL220303381xx
Summary: this document describes the IP flows involved for the xxx
system. This allows to configure firewall rules precisely, to open
the optimal amount of ports required for an operating OpenTouch
system, according to customer requirements.
[12] OpenTouch Web Services Technical Overview 8AL90532xxxx
Summary: this document describes how to develop, integrate and
deploy third party applications with an OpenTouch, via API. This
document includes a description of the available web services as
well as information on authentication and licensing.
[13] OpenTouch Edge Server - Installation and administration manual 8AL90535xxxx
Summary: this document describes the implementation of this
server to control data flows (conferencing, data sharing, instant
messaging or web presentations) between OpenTouch client ap-
plications used off-site and the OpenTouch server, so as to se-
cure the system. Installation and configuration procedures are
provided, as well as upgrade and maintenance guidelines.

8/73       !"  #       

 $%  ! 

Documentation title Part number

[14] OpenTouch XMPP federation with Microsoft© Lync™ Server 8AL90539xxxx
Summary: this document describes how to implement the XMPP
protocol to achieve transparency of features between OpenTouch
applications and the MS Lync collaboration application. Configura-
tion procedures and maintenance commands are provided for the
OpenTouch and the MS servers.
[15] OpenTouch Client Administration Manual 8AL90638xxxx
Summary: this document describes the implementation of an
OpenTouch ecosystem for clients connecting from remote loca-
tions. It also provides deployment and configuration procedures,
for each client - on tablets, PCs, smartphones, or from the web.
[16] OTMC Installation Manual 8AL90120xxxx
Summary: this document describes the installation of an
OpenTouch Message Center server on a physical server or on a
virtual machine. Procedures detail the various steps of installation,
as well as post-installation, initial configuration on an OmniPCX
Enterprise, TUI configuration and software upgrades.
[17] OTMC Administrator Manual 8AL90121xxxxx
Summary: this document provides all the necessary configuration
procedures to implement an OTMC, from voice mail and user pro-
files, to mailboxes, e-mail, sms notifications, automated attendant,
VPIM, IMAP and backup/restore.
[18] OTMC High Availability 8AL90123xxxx
Summary: this documents explains how to implement a high avail-
ability solution, consisting of having a backup system taking over
in case of failure of the main OTMC system. The installation pro-
cedure is completed by configuration details on the control of the
solution, FQDNs, data replication and service continuity. Backup/
restore procedures are provided along with information on monit-
oring and system repair.
[19] ENT_MLE_015903 OpenTouch Suite for Medium and Large En- ENT_MLE_01590
terprises: Virtualized offers. 3
[20] OpenTouch Conversation for PC User Guide 8AL90631xxxx
[26] OpenTouch Message Center User Guide 8AL90122xxxx
[27] OpenTouch Conversation for 8002/8012 Deskphone R110 User 8AL90879xxxx
Manual
[28] OpenTouch Conversation for 8082 My IC Phone R300 User 8AL90835xxxx
Manual
[29] OpenTouch Conversation for 8082 My IC Phone R300 User 8AL90877xxxx
Guide
[30] OpenTouch Conversation for iPhone Release 2.0.x User Guide 8AL90884xxxx
[31] OpenTouch Documentation Note 8AL90911xxxx
This document lists all the modifications and updates since the
previous documentation release.
[32] Alcatel-Lucent 8001 DeskPhone User Manual 8AL90895xxxx

      !"  #        9/73

Chapter 1 $%  ! 

Documentation title Part number

[33] Dongle IP / Raspberry for OpenTouch Suite 8AL90617xxxx
Summary: this document covers the deployment of USB over IP
dongle with OpenTouch and OmniPCX Enterprise systems. Re-
quirements and possible topologies are presented before proced-
ures detailing the installation and necessary configuration.
[34] ALE NFC Extended OXE Mobility Administration 8AL90614xxxx
Summary: this administration manual describes the implementa-
tion of transparent call shifts from a device to the other via NFC
tags. NFC tag generation is detailed with screenshots from the
application.
[35] OTBE/OTMS High Availability 8AL90534xxxx
Summary: this document explains how to implement a high avail-
ability solution, consisting of having a backup system taking over
in case of failure of the main OpenTouch system (OpenTouch
Multimedia Services or OpenTouch Business Edition). The install-
ation procedure is completed by configuration details on the vari-
ous network elements (edge server, reverse proxy), as well as
system options (Exchange server, external gateway for a fax) and
a backup/restore procedure.
[36] OpenTouch Session Border Controler Configuration Guide 8AL90065xxxx
Summary: this document describes the implementation of this
server to control media (voice/video) communications between
OpenTouch client applications used off-site and the OpenTouch
server, so as to secure the system. Installation, configuration and
maintenance procedures are detailed in this document.

10/73       !"  #       

   

 

This document describes the tools and interfaces for the system administration, the
management and/or troubleshooting of the OpenTouch and its ecosystem (devices, users).

      !"  #        11/73

   

    

This chapter is solely concerned with ensuring that SLES is properly configured and that the
required services on the network are available to allow correct operation.
This does not cover the installation of SUSE Linux Enterprise Server and KVM packages on
the server, nor the process of ensuring compatibility with the system application software.
The installation of KVM virtualization packages requires SLES 12 (or higher) as operating
system. To install the SLES operating system and KVM packages, refer to the technical
documentation of the manufacturer (see:
https://www.suse.com/documentation/sled-12/pdfdoc/book_sle_admin/book_sle_admin.pdf).
The SLES OS is customized by ALE International. The release notes, available on the DVD,
allows to verify that the DVD is compatible for installation.
System administration features are:
- Installation of all the specific packages : otms, otmc, otbe, otvxxx, ost64, oms, oxesw, otas
- Network installation via PXE and NFS, compatible with ALEDS
- First login configuration (password and network)
- Boot Dvd installation
- Hardening
- Dependency integration for OpenTouch applications
- Firewall
- Coredump management
Only are described below:
- Installing packages
- Configuring the firewall

3.1 Installing packages

The zypper search <pattern> command is used to find the package name from a
pattern.
suse-test:~ # zypper search libstdc++
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+-------------------------+-------------------------------------------------------+--------
| libstdc++-devel | The system GNU C++ development files | package
| libstdc++-devel-32bit | The system GNU C++ 32bit development files |
package
| libstdc++33 | The standard C++ shared library | package
i | libstdc++33-32bit | The standard C++ shared library | package
| libstdc++48-devel | Include Files and Libraries mandatory for Development
| package
| libstdc++48-devel-32bit | Include Files and Libraries mandatory for
Development | package
i | libstdc++6 | The standard C++ shared library | package
i | libstdc++6-32bit | The standard C++ shared library | package
The zypper search -f <filename> command is used to find the package name from a
filename or from a part of a filename (pattern). This command only works for already installed
rpms.

12/73       !"  #       

 &  !  ! 

Other options can be used by running the man zypper command:

suse-test:~ # zypper search -f libstdc++.so.5
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+-------------------+---------------------------------+-------- |
| libstdc++33 | The standard C++ shared library | package
i | libstdc++33-32bit | The standard C++ shared library | package
The cnf command is used to give the package providing the <filename>. Once the package is
located, install this package by running the zypper install command.
suse-test:~ # zypper install libstdc++33-32bit
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
libstdc++33-32bit
1 new package to install.
Overall download size: 189.3 KiB. Already cached: 0 B After the operation,
additional 747.2 KiB will
be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package libstdc++33-32bit-3.3.3-12.15.x86_64
(1/1), 189.3 KiB (747.2 KiB unpacked)
Checking for file conflicts:
...................................................
[done]
(1/1) Installing: libstdc++33-32bit-3.3.3-12.15
...................................................[done]
To uninstall a package, run the zypper remove command.
suse-test:~ # zypper remove libstdc++33-32bit
Building repository 'sled12' cache
...................................................[done]
Building repository 'sled12' cache
...................................................[done]
Building repository 'sles12-sdk' cache
...................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be REMOVED:
libstdc++33-32bit
1 package to remove.
After the operation, 747.2 KiB will be freed.
Continue? [y/n/? shows all options] (y): y
(1/1) Removing libstdc++33-32bit-3.3.3-12.15
...................................................[done]

3.2 Configuring the firewall

Firewall management consists in adding:
- A static ACCEPT rule
- Complex static rules

3.2.1 Adding a static ACCEPT rule

Add a file to::
/etc/sysconfig/SuSEfirewall2.d/services
containing TCP and/or UDP parameters to define the ports to allow.
Example : openldap

      !"  #        13/73

Chapter 3 &  !  ! 

## Name: OpenLDAP Server

## Description: Opens ports for the OpenLDAP Server (slapd).
# space separated list of allowed TCP ports
TCP="ldap ldaps"
# space separated list of allowed UDP ports
UDP="ldap"
ldap and ldaps are registered service ports, with a numerical value. Port ranges can be also
defined.
Example:
## Name: VNC
## Description: Opens VNC server ports so that viewers can connect.
TCP="5900:5999"
To be taken into account, this filename must be added to the list:
FW_CONFIGURATIONS_EXT = in /etc/sysconfig/SuSEfirewall2

3.2.2 Adding complex static rules

To define your complex rules, create .rule file in:
/etc/sysconfig/scripts/rules/
containing the iptables command that create the rules.
Example: for port rediredction, for the fax server
(/etc/sysconfig/scripts/rules/fax.rule):
## Iptables rules for the fax server
iptables -t nat -I PREROUTING 1 -p tcp --dport 25 --destination ${host_ip}
-j REDIRECT --
to-port 8825

14/73       !"  #       

   

    

4.1 Overview
The aim of the maintenance portal is to provide a single interface for OpenTouch maintenance
and troubleshooting commands.
The maintenance portal provides:
- Clear identification and description of maintenance and monitoring operations
- Easy execution of the tools

4.2 Accessing the portal

You can access the maintenance portal at the following url: https://<server FQDN>:4448
A link to the maintenance portal is available from the WebAdmin application.
All the administrator accounts declared on the OpenTouch server can log in, with their user
name and password.

4.3 Maintenance portal

4.3.1 Interface and operations

      !"  #        15/73

Chapter 4   '

Figure 4.1: Maintenance portal welcome page example

On the left hand side, the portal displays the list of tools available for maintenance or
troubleshooting. Tools are organized by categories. The main tools in each category are
detailed in the following chapters.
Each tool offers an embedded help, providing a description of the aim, content, limits and
parameters of the tool.

16/73       !"  #       

   '

Figure 4.2: Embedded help example

The search feature allows to find all information relating to a specific keyword. For instance, if
you enter "license" in the search field, the results includes all the available tools to collect,
verify and configure the license service.

Figure 4.3: Search result example

The portal allows the execution of a tool. The tool execution log is displayed in the portal.

      !"  #        17/73

Chapter 4   '

Figure 4.4: Logzipper tool execution example

When applicable, the output generated by the tool can be downloaded via clickable links. In
the example above, the archive produced by the LogZipper tool can be directly downloaded on
your PC.
The execution of a command is logged and can be saved as a text file on your PC, by clicking
the icon at the bottom of the window.

4.3.2 Easy and expert administration modes

By default, the portal opens in easy administration mode, to provide quick access to the
execution of most administration and troubleshooting commands.
The information displayed is command oriented than tool oriented.
For example, when looking to troubleshoot the system, all troubleshooting related commands
are displayed in the same panel, to facilitate switching from one operation to another.
The same layout is provided for several sets of related commands (System Identity,
Backup/Restore Operations, Inactive Partition Management, Log Management).
In this mode no online help is available. Commands are self-explanatory and take no
argument. When a command is executed the result window is displayed as explained above.

18/73       !"  #       

   '

Figure 4.5: Easy administration display example

To switch to the expert mode, slide the Expert Mode button on the top right of the window.
The application returns to a tool oriented display as described above.
Advanced tools are displayed in expert mode only.

Figure 4.6: Expert mode backup/restore display example

      !"  #        19/73

   

  

The chapter describes the tools used for server monitoring.

5.1 Server monitoring using AppGuard

AppGuard is a real-time monitoring tool accessible via the maintenance portal. It displays, in
charts or tables, the most important data coming from an OpenTouch system, as well as alerts
(such as process restarting or CPU usage over limit). The control center allows the edition of
the Appguard configuration file either locally or remotely.
This service has its own service command: service appguardd
status|restart|stop|start

Figure 5.1: AppGuard interface example

The columns of the tables can be sorted (with a click on the header), resized or reordered (via
the header or a drag-and-drop).
Charts and tables can be rearranged by drag-and-drop. Double click a chart or table to show it
in a separate window (which can be resized and moved independently).
In tables, several values (free space left on partition, CPU consumption) can be highlighted
(displayed with an orange or red border) if they are above a given threshold.
The full range of the metrics collected by AppGuard can be viewed. Metrics are displayed in
tables with sorting and columns resizing/reordering capabilities.

20/73       !"  #       

    !(

Figure 5.2: AppGuard collected metrics example

AppGuard can send alerts when potential issues are detected. These alerts can be displayed,
and acknowledged. The shield icon on the left navigation bar is red when there is at least one
unacknowledged alert. It is green otherwise.

      !"  #        21/73

Chapter 5    !(

Figure 5.3: AppGuard alerts example

The columns of the tables can be sorted (with a click on the header), resized or reordered (via
the header or a drag-and-drop).
The clear button clears the selected alerts.
AppGuard configuration relies on an XML file. The most important parameters are available to
edition through the AppGuard control center. All parameters can be edited directly in the xml
file, but this may prove tricky.
It is possible to load (for editing or visualization purposes) a configuration which is either local
(i.e. on the user PC) or remote (i.e. corresponding to the OpenTouch server the user is
connected to). Once modifications are finished, the resulting configuration can be saved either
locally (as a file on the user PC) or as a new configuration for the AppGuard running on the
connected OpenTouch. In this case AppGuard takes modifications into account dynamically (in
less than ten seconds).
A question mark to the left of parameters shows the appropriate help, when passing the
mouse cursor over it.

22/73       !"  #       

    !(

Figure 5.4: AppGuard configuration example

Note:
The Appguard control center is compatible with Internet Explorer and Mozilla Firefox, Safari, Opera and
Google Chrome. On Chrome, a warning may be displayed when accessing the application (the NPAPI
plugin support has ended). Java release 7 (or later version) is mandatory.

5.2 Server monitoring using SNMP

An SNMP agent is deployed on the OpenTouch making it possible to manage the system
using an SNMP hypervisor such as, for instance, HP Openview.

5.2.1 SNMP agent configuration

SNMPV3 is the version used by default in the system, with SHA used as default authentication
protocol and AES128 as default privacy protocol.
A default SNMPV3 user is configured in the system. This configuration can be modified via the
OmniVista 8770.
To modify SNMP agent configuration:
1. Launch the OmniVista 8770 client and open the Configuration application
2. From the Networks tab, expand the tree structure and select OpenTouch
3. Access the contextual menu and click Configure
The OpenTouch configuration window opens

      !"  #        23/73

Chapter 5    !(

4. Expand the tree structure to: System services > Security > SNMP Agent
5. Configure SNMP agent parameters:
• Engine ID: displays the SNMP Engine ID default value (read-only)
• Custom data engine ID: enter the OpenTouch node name
• SNMP agent port: displays the port number used by the OpenTouch node as SNMP
agent (read-only)
• Community name: enter the SNMP community name (defining the relationship
between the SNMP server and SNMP agent)
• V3 user name: enter the SNMP agent login name required for authentication with the
SNMP server
• V3 user password: enter the SNMP agent password required for authentication with
the SNMP server
• V3 user passphrase: enter the passphrase
6. Click the validate icon to apply your modifications
Note:
SNMP v2c may also be used.

5.2.2 Verifying your configuration

To verify that your configuration of the agent is correct, issue the following command:
snmpwalk -v 3 -u <snmpsecurityname> -l authPriv -a SHA -A <snmpauthpassword> -x AES -X
<snmpprivpassword> localhost -c ice

This command returns everything that has been defined as SNMP data.
Filtering is possible. For example, to retrieve statistics on voice mail usage on a system using
SNMP v2c, the command:
/usr/bin/snmpwalk -v2c -c internal localhost .1.3.6.1.4.1.1729.200.149.1.1.114.112

can return:
SNMPv2-SMI::enterprises.1729.200.149.1.1.114.112 = Gauge32: 0

5.2.3 OpenTouch MIBs

The MIB files can be collected from the system itself. A list of the MIB files and their location
can be obtained using the following command, as root:
find $ECC_HOME -name "*.mib"
Note:
Example of result:
[root@server1ot ~]# find $ECC_HOME -name "*.mib" | grep -v backup | tee
/nfs1/wwwroot/temp/miblist.txt
/opt/Alcatel-Lucent/oamp/omp/metrics/ICE-OAMP-METRICS-MIB.mib
/opt/Alcatel-Lucent/oamp/omp/ams/http-resources/mib/ICEAlarmMgnt.mib
/opt/Alcatel-Lucent/serviceability/appguard/mib/AppGuardRule.mib

5.3 OpenTouch alarms management

24/73       !"  #       

    !(

The OpenTouch generates alarms whenever fault conditions arise in the system.
These alarms can be notified to the OmniVista 8770 network management systems and/or
external hypervisors, using SNMP traps.
To enable alarm notification to the OpenTouch:
- Configure the OpenTouch server SNMP agent as specified: SNMP agent configuration
- Configure the OpenTouch server to send its alarms to the OmniVista 8770
- Configure alarm reception on the OmniVista 8770

5.3.1 Configure the OpenTouch server to send its alarms to the OmniVista
8770
1. Launch the OmniVista 8770 client and open the Configuration application
2. From the Networks tab, expand the tree structure and select the OpenTouch node
3. Access the contextual menu and click Configure
The OpenTouch configuration window opens
4. Expand the tree structure to: Eco system >IT Server
5. Access the contextual menu and select Create > SNMP Server
6. In the properties area, select the General tab and configure the following parameters:
• Display name: enter the name of the SNMP server
• FQDN: enter the FQDN of the OmniVista 8770 application
7. In the properties area, select the Configuration tab and configure the following SNMP
agent parameters:
• v.3 User name: enter the SNMP agent login name
• v.3 User password: enter the SNMP agent password
• v.3 User privacy passphrase: enter the passphrase
8. Click the validate icon to apply your modifications
Reminder:
Several SNMP hypervisors can be configured in the OpenTouch, making it possible to send alarms to
both an OmniVista 8770 and an external hypervisor.

5.3.2 Configure alarm reception on the OmniVista 8770

1. Launch the OmniVista 8770 client and open the Configuration application
2. From the Networks tab, expand the tree structure and select the OpenTouch node
3. In the properties area, select the Connectivity tab
4. Complete the corresponding fields:
• SNMP V3 user: enter the SNMP agent login name
• SNMP Authentication password: enter the SNMP agent password
• SNMP Authentication protocol: SHA
• SNMP Encryption password: enter the SNMP agent privacy passphrase
• SNMP Encryption protocol: AES

      !"  #        25/73

Chapter 5    !(

• SNMP Security Level: Authentication, Privacy

• SNMP Community String: enter the community name used to identify exchanges
between the SNMP agent and SNMP server
5. In the properties area, select the OT MS tab and validate the Alarm Monitoring check box
6. Click the validate icon to apply your modifications

5.3.3 Alarm catalog

The alarm catalog is accessible from the Maintenance Portal in the Information Category.
This catalog provides the list of all alarms emitted by OpenTouch components.

5.3.4 Supervision of OpenTouch alarms from the OmniVista 8770

The OmniVista 8770 client provides access to the Alarms application, via the Applications >
Network menu or the alarm icon from the Setup group.

Figure 5.5: Alarms Application Window Example

The Alarms application contains:
- A tree structure displaying the OpenTouch components which have triggered alarms
Selecting a component displays its associated alarms in a table
- An alarm table providing information about current delivered alarms
Each alarm displayed in the table can be selected with a mouse click. According to the
severity level, the contextual menu provides access to actions to perform on the alarm:
• Acknowledge: This action acknowledges the alarm

26/73       !"  #       

    !(

• Clear: This action marks the alarm problem as solved

• Delete: This action removes the alarm from the table
• Detail: This action provides additional information on the selected alarm, as for
example the managed object, event type, notification date, probable cause, severity,
and diagnostic
- A set of filters to define the alarms display in the Alarms application
For more information on the Alarms application, refer to the OmniVista 8770 administrator
manual or the OnLine Help of the OmniVista 8770 client.

5.4 OpenTouch server supervision

5.4.1 Overview
The supervision tool provides supervision and maintenance features via a web interface.
You can access the Supervision tool:
- From a web browser: enter the address:
http://<server FQDN>/WebAdmin
Note:
If SSL is enabled you are automatically redirected to:
https://<server FQDN>/authenticationform/jsp/logonWeb.jsp
- From the OmniVista 8770 application: in the configuration window, right-click an
OpenTouch node and select WBM
A login/password is required to access the web admin home page. Access is limited to
declared OpenTouch administrators associated to WBM application.
Creating and modifying an administrator account can be performed:
- On the OmniVista 8770 (see the OpenTouch administrator manual for more details)
- On the web admin interface: menu System services > Security > Administrator
From the home page, you can access the pages to display:
- System status
- Application status

5.4.2 Description
The Supervision window is divided into panes. The left hand panes contains links to the
options: Home (for the homepage and login/logout), System status, Application status, and
Alarms.

      !"  #        27/73

Chapter 5    !(

Figure 5.6: Web admin home page example

5.4.3 System Status

System status indicates the state of the various elements in the network, in a tree structure .
Each element has a color marker representing its current status. The elements change color
according to the alarm level .

28/73       !"  #       

    !(

Figure 5.7: System Status Example

Click a service name to display a contextual menu. The menu indicates the short name for the
services and an option allowing to restart the service.

      !"  #        29/73

   
   
    
The following paragraphs list all the commands used to administer and/or troubleshoot the
OpenTouch. These tools are command line tools available from an OpenTouch terminal or via
the Maintenance Portal.

6.1 listtool.sh
listtool.sh displays the available maintenance commands.
[root@tssf161 ~]# listtool.sh

Information Description
listerm.sh Displays user and devices information
getVersion Shows host and VM applications software versions
getHardInfo Shows host hardware information
getaluid Displays the ID of the hardware platform, used for the signature
of licenses
collectLicenses Collects all OpenTouch core, OmniPCX Enterprise VM and VM
licenses into one archive

Maintenance Description
ot-config.sh Toolbox grouping: HA activation; storage, ntp, dns forward con-
figuration; rehosting launching
otbr.sh Backup restore tool
reset-firstsetup.sh Resetting to factory setup
switchover.sh Manage the inactive partition
oxe_cmd Manage and give information on the OmniPCX Enterpriseand
its virtual machine
management_cmd Manage and give information on the OmniVista 8770 and its
virtual machine
oms_cmd Manage and give information on the OXE-MS virtual machine
CertificateTool.sh Select the level of network security for the OpenTouch
prepareUsbdisk Prepare and format the USB disk used for backup/restore

Troubleshooting Description
checkAll.sh This tools runs all other check tools and shows the statuses of
services
service Display the status, and start or stop a component
serverstatus Shows the High Availability status
ot-moni.sh Diagnosis and information on the host (partitions, load...)
checkClock.sh Diagnosis and information collection on Clock and NTP
checkCertificates.sh Diagnosis and information collection on Certificates

30/73       !"  #       

  !    "' )( !!

Troubleshooting Description
checkLicensing.sh Diagnosis and information collection on Licensing
checkdns Verifies the DNS configuration of the host
raidstatus_cmd Shows HDD raid status on physical servers
checkSystem.sh Checks the consistency between the bics.conf file and the
system configuration

Log Description
dla.sh Sets log level, resets and clears logs for a specific feature
loglevel.sh Sets the level of traces for several infra component
Logzipper.bin Collects the logs
netcapture.sh Manages (start, stop, list, zip, clean) tcpdump network traces
getSupport Collects logs from OpenTouch commands, syslog and applica-
tions including OpenTouch Business Edition VMs

Components Description
lmutil FlexLM (license service) management
See: lmutil .
routingConfigConsole.sh Martin: Collects, displays, changes and resets routing configur-
ation for a user
See: RoutingConfigConsole.sh
tsa_maintenance OTS: Gets information, used for standard users
clean_logs_and_restart_udas UDAS: Clean logs and restart
.sh
checkAcapi.sh Check if Acapi services are running
dumpxs.sh Configuration for extensible services

6.2 otconsole.sh command

This command provides a menu-based tool for fast and easy access to most administration
and maintenance commands.
It is context-dependent. The operations offered from the console depend on system type
(OTBE, OTMS) and whether or not the system runs in High Availability. The root menu in the
console offers easy and advanced maintenance operations.
For a complete help on console option, run: otconsole -help.
[root@localhost ~]# otconsole.sh
ALE INTERNATIONAL
OT Console OT Console Version 11.0.000.008 SNAPSHOT
1 Easy Administration
2 Advanced Administration
Q Exist
Your choice [1..2,Q]:
Advanced administration is reserved for experienced administrators.
The commands supported in the console can be retrieved using otconsole.sh
–-list_cmd.

      !"  #        31/73

Chapter 6  !    "' )( !!

[root@myot165 toolexec]# otconsole.sh -l

Easy Administration [id=easyAdmin]
Backup Restore [id=backupRestore]
Backup Operations [id=backup]
Backup Host
Backup Music on Hold
List Periodic Backup
Restore Operations [id=restore]
Restore Host
Restore Host Without Music on Hold
Restore Music on Hold
Storage Configuration [id=storage]
Show Storage Configuration
Configure Storage
Storage Status
Format USB Disk
Troubleshooting [id=troubleshooting]
All Verifications
System Resources Verification
Clock Verification
Certificates Verification
License Verification
Collect Licenses
DNS Verification
System Verification
HDD Raid Status
Configuration Server Verification
System Management [id=easySystemMgnt]
Solution Status
Start Solution
Stop Solution
Change Passwords
Information [id=information]
Software Versions
Hardware information
Get ALUID
List Users/Devices
List Core Files
Command History
Log Management [id=logManagement]
Dynamic Logs Activation
Collect Logs [id=zipLogs]
Collect All Host Logs
Collect Today Host Logs
Collect This Week Host Logs
Collect Linux Logs
Advanced Administration [id=advanceAdmin]
System Management [id=advancedSystemMgnt]
Re-host Server
Add High Availability
Configure NTP Server
Configure External Flex Server
Configure DNS
Configure DNS Forwarders
Reset to First Setup
Switch partitions [id=switchPartitions]
Partitions Status
Switch to Inactive Partition Without Datacopy
Switch to Inactive Partition With Datacopy

6.3 timout command

The timout command allows to manage the delay after which an interactive shell is
automatically closed when no input is received from the terminal.
The timeout is by default set to 300 seconds.
To modify the timeout, enter the command followed by the timeout in seconds, for example, to
set the delay to 100 seconds, enter the command:
timout 100

32/73       !"  #       

  !    "' )( !!

To disable the timeout, enter the command:

timout 0
To display the current value, enter the command:
timout

6.4 Information tools

6.4.1 listerm
The listerm command is used to display information about users and devices. It can:
1. Dump user information
2. Dump device information
3. Dump users routing information
4. Dump current calls information
5. Dump SIP registration information
6. Dump Current telephony and routing events
The listerm command interfaces to interact with bash scripts.
The arguments for this command (listerm.sh [options]) are:
- -a or --all: Display the information about all users, devices, routing profiles and current
calls
- -c or --calls: Display the information about all current calls
- -d or --devices: Display the information about all devices
- -e or --events: Display the telephony and the routing events concerning a user
- -F or --filter: Use a search filter on a given information
- -h or --help: Show the help guide
- -r or --routing: Display the routing rules
- -s or --sip: Display the SIP registration information
- -u or --users: Display the information about all users
When no argument is sent to listerm, the menu mode starts. This mode allows the user to
perform advanced operations in a more interactive interface.
[root@otms-192 listerm]# ./listerm.sh
- 1 ALL
- 2 USERS
- 3 DEVICES
- 4 ROUTING
- 5 CALLS
- 6 EVENTS
- 7 SIP

      !"  #        33/73

Chapter 6  !    "' )( !!

The type of information can be selected to dump all information or to select a filter depending
of the type of information selected.

6.4.2 getVersion
This command shows host and VM applications software versions. Login as root.
The arguments for this command are:
- host: Get the application versions of the host
- applioxe Get the application versions of the OXE Virtual Machine
- applioms Get the application versions of the OMS Virtual Machine
- appliwin Get the application versions of the Management Virtual Machine
- all Get all the application versions

34/73       !"  #       

  !    "' )( !!

[root@tssf161 ~]# getVersion

Get applications versions in host management OXE OMS...
VERSIONS OF ACTIVE PARTITION:
Business Edition: 2.1.000.071
Hotfixes: ALF0001418902193464 ALF0001418983057093_MIG
ALF0001418984915203
ALF0001418998137165 ALF0001419039035265 ALF0001419039175828
ALF0001419234145222
ALF0001419007278165 ALF0001419598980254
Linux:
Boot DVD: 12.0.002.004 (otbenfs)
Kernel: 3.12.28-4-default
HW platform: x86_64
OS: SUSE Linux Enterprise Server 12
RPM:
bics_host: bics_host-11.0.009.007-ice.i386
aksusbd: aksusbd-2.5-1.i386
nut: nut-2.7.1-4.84.x86_64
nut-client: nut-client-2.6.5-1.el6.x86_64
Core components:
SIPServer: 11.0.009.15
Voice Plaform: 11.0.012.00-IP0002
AMS RM: 11.0.012.00
AMS MCP: 11.0.012.00
XS: 11.0.009.04
Config proxy: 11.0.009.03
CMS: 11.0.009.002
ACS: 11.0.0b7635
Devices & Clients:
OTCv PC*: 2.2.005.000
OTCt PC*: 2.1.203.003
OTC web: 2.20.5501
OTC sharing: 2.11.4904
MyProfile: 11.0.000.002
WebAdmin: 11.0.000.011
Other:
OFS: 7.5.2-66.i386
Flex: 11.12.0.0
Nuance: 4.0.3.3-57
Windows VM:
8770: 2.6.02.00
Patches:
Patch_200901A_JAR_SAR Patch_200901B_VITAL_PATCH#1
Patch_200901C_VITAL_PATCH#2_V1
Patch_200901D_VITAL_PATCH#3 Patch_200901E_WEBCLIENT_V1
Patch_200901F_WEB_CLIENT_AAR Patch_200901G_AAR_EXE_V1
Patch_200901H_SQL_KPI
Patch_200901I_LDIF Patch_200901J_AAR_CLIENT
Patch_200901K_CLIENT Patch_200901L_DLL Patch_200901M_AAR_LDIF
Patch_200901N_CLIENT
Patch_200901O_SQL_V1
Patch_200901P_CLIENT Patch_200901Q_LDIF_V1 Patch_200901R_DLL
Patch_200901S_VBS_V2
Patch_200901T_TICKET_DLL
Patch_200901U_TICKET_DLL Patch_200901V_EXE Patch_200901W_VITAL_PATCH#4
Patch_260200A_JAR_SAR
CopSSH: 4.4.1
OMS VM: OMS: 3.05
OXE VM: OXE: l1.301.21.b
ASM Server is running but you don't have any license
CCA Server is running but you don't have any license
CCS Server is running but you don't have any license
---------------------------------
INACTIVE PARTITION NOT INSTALLED:

6.4.3 getHardInfo
The getHardInfo command shows hardware information. Login as root.
The arguments for this command are:
- all Get all the harware and id information
- hard Get hardware information

      !"  #        35/73

Chapter 6  !    "' )( !!

- id Get all id
- aluid Get only aluid
Note:
getHardInfo aluid command is same as getaluid
[root@tssf161 bin]# getHardInfo all
AluID
Unchanged ALUID=11841D789BD7EBBA4F0003604786C229
UtcDate=2014-09-26_13:20:56 (Aluid was set on utcDate=2014-09-15_11:16:23)
ID
- UUID: 35353736-3739-5A43-3334-313735424259
- Mac address: 40:A8:F0:75:BF:84
Server Type
- Manufacturer: HP
- Product Name: ProLiant DL320e Gen8
Chassis
- Manufacturer: HP
- Type: Rack Mount Chassis
Processor
- Family: Xeon
- Manufacturer: Intel
- Version: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz
Memory
- Total Size: 19 GB, 19952 MB
Hard Drives
- Total Size: 1000.1 GB RAID
- 1 x RAID bus controller: Intel Corporation 6 Series/C200 Series Chipset
Family SATA RAID Controller (rev 05)
- 1 x RAID bus controller: Hewlett-Packard Company Smart Array Gen8
Controllers (rev 01) Ethernet
- 2 x Ethernet controller: Broadcom Corporation NetXtreme BCM5717 Gigabit
Ethernet PCIe (rev 10) USB
- 1 x USB controller: Intel Corporation 6 Series/C200 Series Chipset Family
USB Enhanced Host Controller #2
- 1 x USB controller: Intel Corporation 6 Series/C200 Series Chipset Family
USB Enhanced Host Controller #1
- 1 x USB controller: Hewlett-Packard Company Integrated Lights-Out
Standard Virtual USB Controller (rev 02)

6.4.4 getaluid
This command shows the ALU ID of the hardware platform.
[root@tssf161 bin]# getaluid
Unchanged ALUID=11841D789BD7EBBA4F0003604786C229
UtcDate=2014-09-26_12:51:05 (Aluid was set on utcDate=2014-09-15_11:16:23)
USB dongle control is not required anymore for the OpenTouch Business Edition on the
pre-integrated appliance server as of release 2.0 (new eLP declaration required for
OpenTouch Business Edition installed base).
This evolution of the licensing control for OpenTouch Business Edition also applies to an
OpenTouch Multimedia Services configuration pre-integrated on the appliance server:
OpenTouch Multimedia Services as of release 2.0 also uses the ALU ID (instead of MAC@
control in previous OpenTouch releases).
Notes:
- OTBE-V or OTMS-V configuration still require the usage of the USB dongle for licensing control
- When the OpenTouch Multimedia Services/OpenTouch Business Edition/OTMC server is ordered
directly from an HP reseller, the server is delivered with raw data, on which you must:
a. Set the BIOS parameters
b. Install from scratch the version and hotfix required
c. At next restart, cancel the post install and recover the ALU_ID using the script getaluid

36/73       !"  #       

  !    "' )( !!

d. Order the license

e. Restart the server to complete the post installation
- When the OpenTouch Multimedia Services/OpenTouch Business Edition is installed in a previous
version, you must migrate, and:
a. Collect the script getaluid from the OpenTouch Core DVD of R2.x (under
/scripts/getaluid) and copy it on the server in /usr/bin
b. Grant rights of execution for the script: chmod 777 getaluid
c. Run the script and recover the ALU_ID
d. Order the license
e. Upgrade the software to backup the current system
f. Install the system from scratch

6.4.5 collectLicenses
This tool gathers all OpenTouch Business Edition licenses (OpenTouch core, OXE VM,
Management VM, internal OFS) and stores them in one archive, such as:
/tmp/licenses-hostname-date.zip.
Licenses for other applications are not collected by this tool.
A <file> can be used to specify the output zip file path and name, for example:
/var/backup/licenses.zip
This archive can be used either for license backup, or to facilitate ordering of add-on of
features.

6.5 Maintenance tools

6.5.1 ot-config.sh
This command is a toolbox grouping various commands:
Arguments Description
--ha_active Enables High Availability (HA). The backup server has to be
operational
This command executes a procedure to verify the associated
services/systems for HA requirements and activates HA if
everything is OK
--recovery primary Adds a new server with the primary role (after it has crashed).
The server has to be operational
--recovery backup Adds a new server with the backup role (after it has crashed).
The server has to be operational

      !"  #        37/73

Chapter 6  !    "' )( !!

Arguments Description
--storage [help] Configures the storage media (local disk, USB disk or NFS)
for the backup/restore feature. The help argument displays
the other options of the storage action
Caution:
- Backup on the local disk is not recommended for the
OpenTouch Business Edition (if the system crashes, the
backup crashes with it).
- In a virtualized configuration with no /var/backup/ parti-
tion, backup must not be performed on the local disk.
See: Examples of backups (ot-config.sh --storage)
--ntp Configures the NTP feature on the host
See: Example of ot-config.sh --ntp
--forward Configures and activates DNS forwarders on the host
--dns Configures the DNS on the host and VMs in an OpenTouch
Business Edition
--rehost Rehosts the system
See: ot-config.sh --rehost
--rehost –suspend Rehosts the system and suspends operations in order to
move the servers to another place
See: ot-config.sh --rehost
--restart_ups Restarts the UPS services (when the OpenTouch is installed
with UPS
--cc_active Enables or disables the Contact Center applications on the
management VM and OmniPCX Enterprise VM
See: ot-config.sh --cc_active
--8770_active In an HA configuration, starts the OmniVista 8770 in local VM
and stops the remote OmniVista 8770.
When this command is launched, the remote OmniVista 8770
switches to standby. The local OmniVista 8770 switches to
active and a restore operation is launched with the last
backup, saved in: C:\8770_ARC\TWIN_BACKUP(rehosting
of the data is automatic, which means that all information with
hostname or IP address of the previous active OmniVista
8770 are modified in the database).
--oms_active Enables the OMS
When the OXE-MS is not activated at post-installation, it is
possible to activate it later with this command
--passwords Re-enters the server passwords
--external_flex Switches from an internal to an external flex `server
--check_system Checks the state of the system
This command is used to check the state of the system, the
host in case of HA (uses the serverstatus command), the
VMs in case of OpenTouch Business Edition (use the check
option of each VM script, such as: management_cmd,
oms_cmd or oxe_cmd).
--splitbrain Selects the preferred server in case of split brain

38/73       !"  #       

  !    "' )( !!

Arguments Description
--cloud Configures the cloud connect

6.5.1.1 Examples of backups (ot-config.sh --storage)

6.5.1.1.1 Backup on NFS
[root@tssf161 ~]# ot-config.sh --storage
--- Configure storage for Backup archives ---
Backup archives are configured to be stored on the network (NFS).
NFS server : 172.27.132.240
NFS directory : /volume1/ccd/temp/ET/immersion/OTBE2.1.000.061
NFS already mounted and is writable, size 4.5T, available 1.1T
Would you like to change these settings ? (Y)es/(N)o [N]: y
Do you want to backup on local storage space ? (Y)es/(N)o [N]: n
Do you want to backup on an NFS share ? (Y)es/(N)o [N]: y
NFS already mounted and is writable, size 4.5T, available 1.1T
Backup archives NFS server : 172.27.132.240
Backup archives NFS directory :
/volume1/ccd/temp/ET/immersion/OTBE2.1.000.061
Do you want to change values (Y)es/(N)o [N]: y
Enter the Backup archives NFS server : 172.27.132.240
Enter the Backup archives NFS directory :
/volume1/ccd/temp/ET/immersion/OTBE2.1.000.071
NFS: This directory is empty
NFS can be mounted and is writable, size 4.5T, available 1.1T
If you do not mount the Backup archives storage now, otbr.sh will mount it
automatically.
Do you want mount NFS now (Y)es/(N)o [N]: y
The backup archives directory is mounted.
--- Result of configuration ---
Backup is configured to store or restore archives by a NFS
172.27.132.240:/volume1/ccd/temp/ET/immersion/OTBE2.1.000.071 share.
Backup & restore done by otbr.sh can be performed
ot-config.sh is completed.
------------------------------------------------------------------------------------

6.5.1.1.2 Backup on a USB disk

[root@frbreseuro2ice ~]# ot-config.sh --storage
Backup are configured on network (NFS).
NFS server : 192.168.201.139
Directory : /OpenTouch/nfs/export1
Would you like to change these settings ? (Y)es/(N)o [N]: Y
Do you want to back up on local storage space ? (Y)es/(N)o [N]: N
Do you want to back up on an NFS share ? (Y)es/(N)o [N]: N
Do you want to back up on a USB disk ? (Y)es/(N)o [N]: Y
Backup will be done on an USB share.
ot-config.sh succeeded.

6.5.1.1.3 Backup on a local disk

[root@tssf161 otuser]# ot-config.sh --storage
Backup will be done on an USB disk.
Directory : /media/usbdisk
Would you like to change these settings ? (Y)es/(N)o [N]: y
Do you want to back up on local storage space ? (Y)es/(N)o [N]: y
Backup will be done on an local share.
ot-config.sh is completed.
------------------------------------------

6.5.1.1.4 ot-config.sh --storage options

The help argument (ot-config.sh --storage --help) displays the other options
available for storage. This option can be used to get the status/management as per the
requirement:

      !"  #        39/73

Chapter 6  !    "' )( !!

connectionStatus: displays the state of connections (ethernet, USB disk, NFS)

[root@tssf161 ~]# ot-config.sh --storage connectionStatus
Ethernet port 1 is connected.
Ethernet port 2 is not connected.
USB disk is not plugged
NFS already mounted and is writable, size 4.5T, available 1.1T
ot-config.sh is completed.
------------------------------------------

6.5.1.1.5 backupStatus: display backup configuration

[root@tssf161 ~]# ot-config.sh --storage backupStatus
Backup archives are configured to be stored on the network (NFS).
NFS server : 172.27.132.240
NFS directory : /volume1/ccd/temp/ET/immersion/OTBE2.1.000.081
Backup & restore done by otbr.sh can be performed
ot-config.sh is completed.
------------------------------------------

6.5.1.2 Example of ot-config.sh --ntp

This command is used to view and configure the NTP feature in the OpenTouch host. This
command is the same as configureNtp.
[root@tssf161 ~]# ot-config.sh --ntp
Host FQDN : tssf161.fr.alcatel-lucent.com
Host IP : 172.27.139.161
The Time Reference is local clock
NTP Server 1 : 172.27.139.161
NTP Server 2 :
Would you like to change these settings ? (Y)es/(N)o [N]: y
Do you want to use local clock ? (Y)es/(N)o [N]: n
NTP Server 1 : 135.120.0.18
NTP Server 2 :
/etc/ntp.conf written
/etc/ntp/step-tickers updated
Activating ntpd service at boot time.
Restarting ntpd
Shutting down ntpd: [ OK ]
Starting ntpd: [ OK ]
ot-config.sh is completed.
------------------------------------------

Note:
The ot-config.sh--ntp command updates automatically the bics.conf file

6.5.1.3 ot-config.sh --rehost

This command can be used to rehost (in other words, re-configure the IP parameters,
hostnames etc.) the OpenTouch server. It is similar to the server-rehosting.sh command
/opt/Alcatel-Lucent/serviceability/bics_applications/bin/server-
rehosting.sh.
Back up the system before you proceed with rehosting, in case of failure. The Contact Center
must be configured again after re-hosting.
A wizard opens up to enter the new IP address/hostname parameters.
The network environment (router/DNS etc.) has to be configured properly and reachable
before launching this command in the OpenTouch server.
6.5.1.3.1 ot-config.sh --rehost --suspend
The suspend argument allows time to move the servers to another place. This can be done in
the following scenario:
1. The future network environment is not yet operational. Depending on the new

40/73       !"  #       

  !    "' )( !!

configuration, the new remote IP address, the new router address and the new DNS may
not be reachable) at the moment when the rehosting operation is launched. You need to
physically move the servers from one location to another.
2. Launch the command: ot-config.sh --rehost--suspend. During this operation the
server (both servers in case of HA) are stopped.
3. Physically move the server and restart it in the new environment. The process resumes at
the step where it stopped.
Caution:
Once the process is launched there is no possibility for roll-back (cancellation of the rehosting
operation).
When rehosting restarts, the new network environment must operational for the operation to
finish successfully.
This can prove useful for lab tests before installing servers in a customer environment.
6.5.1.3.2 Status messages displayed on the console during rehosting operations
At system login, a message is displayed if rehosting is not over with an approximate remaining
time.
Previous rehosting is not ended
Time remaining less than: xx mn
WARNING: Rehosting is not ended. It is recommended to wait

During operation: a message after each item has been rehosted:

OXE rehosting is ended
OMS rehosting is ended
Management rehosting is ended

At the end of the process, if all is OK, a message is displayed via the wall on all consoles:
Broadcast message from [email protected] (pts/4) (Tue Oct 29 13:16:29 2013):
INFORMATION: Rehosting is ended. You can execute any command.

At the end of a timeout of 75 minutes, if the operation is not finished a message is displayed
via the wall on all consoles. It is recommended to stop the consoles and verify operations. This
does not mean that all operations aborted, you may check each VM log files to find out where
a problem may have occurred:
Broadcast message from [email protected] (pts/4) (Tue Oct 29 10:53:30
2013):
WARNING: Rehosting delay (75 mn) is reached. Check the VMs.

In case of failed operation(s) a message is displayed (depending on which operations failed):

Rehosting in OXE failed, see in VM the log files /opt/bics/log/*.log
Rehosting in Management failed, see in VM the log files in C:\temp\log\*.log
Rehosting in OMS failed, see in VM the log file /opt/Alcatel-
Lucent/bics_applications/log/bicsrehosting.log

      !"  #        41/73

Chapter 6  !    "' )( !!

6.5.1.4 ot-config.sh --cc_active

The Contact Center can be activated or disabled at any time by calling the script
ot-config.sh --cc_active. This script launches a Wizard. In the 8770 tab, activate or
deactivate the state of the Contact Center.
When the wizard closes, after clicking the Finish button, the new configuration is applied the
Management VM and in OXE VM. In any case (activation or deactivation), the OmniPCX
Enterprise reboots to take into account the new configuration.
[root@tssf161 ~]# ot-config.sh --cc_active
Checking requirements on PRIMARY server
-----------------------------------------------
The existing configuration file /var/data/bics/bics.conf exists : OK
--- An OMS vm is detected, checking vm requirements ---
vmOMS is running : OK
Checking vmOMS connectivity (172.27.139.164).
tssf164.fr.alcatel-lucent.com lookup succeeded : OK
Remote command on 172.27.139.164 succeeded : OK
vmOms connectivity is operational : OK
--- An OXE vm (172.27.139.163) is detected, checking vm requirements ---
vmOXE is running : OK
Checking vmOXE connectivity (172.27.139.163).
vmOXE connectivity is operational : OK
k2_oxepostinstall is installed in vmOXE (172.27.139.163).
vmOXE is installed.
A management vm is detected, checking vm requirements.
vmManagement is running : OK
tssf162.fr.alcatel-lucent.com lookup succeeded : OK
172.27.139.162 ping succeeded : OK
Remote command on 172.27.139.162 succeeded : OK
vmManagement connectivity is operational : OK
Contact center is find.
Requirements are all PASSED
-----------------------------------------------
-----------------------------------------------
Launching the configuration wizard
No graphic display possible.
The wizard can not run.
The process must be executed in a local console.
An error occurred when executing the wizard.
Configuration wizard FAILED
-----------------------------------------------

6.5.2 otbr.sh
This is the backup/restore utility included in OpenTouch systems. This utility writes the backup
on the media (local disk or USB disk or NFS) configured in the OpenTouch system. This tool
can also be used to restore the database available in the configured media.
[root@tssf161]# otbr.sh [backup|restore] host (backup/restore host data)
[root@tssf161]# otbr.sh [backup|restore] VMoxe (backup/restore OXE virtual
machine)
[root@tssf161]# otbr.sh [backup|restore] VMwin (backup/restore Windows
virtual machine)
[root@tssf161]# otbr.sh [backup|restore] VMoms (backup/restore OMS virtual
machine)
[root@tssf161]# otbr.sh [backup|restore] VMall (backup/restore the 3 virtual
machines)
[root@tssf161]# otbr.sh [backup|restore] appliwin (backup/restore 8770 data)
[root@tssf161]# otbr.sh [backup|restore] appli8770 (backup/restore 8770

42/73       !"  #       

  !    "' )( !!

and Windows CCX data)

[root@tssf161]# otbr.sh [backup|restore] applioxe (backup/restore OXE data)
[root@tssf161]# otbr.sh [backup|restore] appliccx (backup/restore Windows
CCX data)
[root@tssf161]# otbr.sh [backup|restore] appliall (backup/restore 8770,
windows CCX and OXE data)
[root@tssf161]# otbr.sh [backup|restore] moh (backup/restore Music on Hold
(MOH) files)
[root@tssf161]# otbr.sh [backup|restore] nomoh (backup/restore excluding
Music on Hold (MOH) files)

6.5.3 reset-firstsetup.sh
This command is used to reset the OpenTouch system/database to factory default settings.
This script can be used to re-configure the OpenTouch from the post installation wizard.
1. This command requests confirmation:
All data will be cleared. Post-installation will be resumed
Are you sure ? (Y)es/(N)o [Y]:
2. The available database is deleted, and the command configures the system to run the
post-installation wizard at the next boot.
In case of an OpenTouch Business Edition, reset-firstsetup.sh checks the virtual
machine connectivity before making any change:
--- An OXE vm is detected, checking vm requirements ---
vmOXE is running : OK
Checking vmOXE connectivity.
vmOXE connectivity is operational : OK
k2_oxepostinstall is installed in vmOXE (172.27.176.104).
vmOXE is installed.
OXE is not secured : OK
--- A management vm is detected, checking vm requirements ---vmManagement
is running : OK
Checking vmManagement connectivity.
icedev2mgmt.alcatel-lucent.com lookup succeeded : OK
172.27.176.106 ping succeeded : OK
Remote command on 172.27.176.106 succeeded : OK
vmManagement connectivity is operational : OK
--- An OMS vm is detected, checking vm requirements ---vmOMS is running :
OK
Checking vmOMS connectivity (172.27.176.105).
icedev2oms.alcatel-lucent.com lookup succeeded : OK
172.27.176.105 ping succeeded : OK
Remote command on 172.27.176.105 succeeded : OK
vmOms connectivity is operational : OK
If one or more commands cannot be triggered remotely, the reset process stops. Fix the issue
before launching the reset-firstsetup.sh script again.

6.5.4 switchover.sh
The switchover.sh command is used to switch partitions from active to inactive, where you
load the OpenTouch software. The active partition becomes inactive and vice versa when
running this script.
To switch partitions, log in as root and type switchover.sh.
The switchover.sh can be used with the following syntaxes:

      !"  #        43/73

Chapter 6  !    "' )( !!

- switchover.sh: (without any option) switch to the other partition without any data
duplication
- switchover.sh status: display information on installed versions on the different
partitions
- switchover.sh --datacopy: switch to the inactive partition with data duplication if the
version on the inactive partition is greater or equal to the version on active partition
- switchover.sh --help: display these help option

6.5.5 VM management commands

The following commands must be launched from a root session.
To view the virtual machine status:
- OXE: oxe_cmd status
- Management: management_cmd status
- OMS: oms_cmd status
To start the virtual machine:
- OXE: oxe_cmd start
- Management: management_cmd start
- OMS: oms_cmd start
To stop the virtual machine:
- OXE: oxe_cmd stop
- Management: management_cmd stop
- OMS: oms_cmd stop
To force the virtual machine to stop:
- OXE: oxe_cmd forcestop
- Management: management_cmd forcestop

6.5.6 CertificateTool.sh
The certificate tool allows to select the level of network security for the OpenTouch:
- Network security disabled: a pre-loaded and generic Certificate Trust List is used
- Network security enabled: a customized certificate is used
When network security is enabled, the certificate tool allows to:
- Generate an internal autogenerated certificate
- Import a PKCS12 certificate
The certificate tool is automatically launched by the post-installation wizard. It can also be
launched manually, as described in the following paragraphs.
The certificate tool can be used:
- In console mode: the parameter -console

44/73       !"  #       

  !    "' )( !!

- In graphical mode: the no parameter mode

After using the certificate tool:
- If you have enabled network security by installing a customized server certificate during
post- installation, perform the following mandatory operations:
a. Create at least one 8082 My IC Phone that will execute CTL signature operations
b. Perform CTL signature and CTL installation operations
- If you have disabled the network security, there is no need of an 8082 My IC Phone to
execute CTL signature operations. In this configuration, the Master VHE device MAC
address is automatically set to the default value 00:80:9F:7B:08:40. A CTL signed by this
"virtual" set is used. It is then necessary to deploy the certificate.
In console mode:
1. Open a root session on the OpenTouch console
2. Navigate to: /opt/Alcatel-Lucent/serviceability/certificate_tool
3. Enter the ./CertificateTool.sh -console command
The screen displays:
Testing parameters
All parameters are correct
--------------------------------------------------------------------------------
Alcatel - Lucent Certificate Tool
--------------------------------------------------------------------------------
0 Off
1 On
Select network security level :
There is no option selected by default
4. Enter:
• 0 to disable network security: a pre-loaded and generic Certificate Trust List is used.
• 1 to enable network security: a customized certificate is used.
In graphical mode, select:
- Off to disable network security: a pre-loaded and generic Certificate Trust List is used
- On to enable network security: a customized certificate is used

6.5.7 prepareUsbdisk
This tool is used to prepare/format the USB disk using for backup/restore. It must run as root:
[root@tssf161 otuser]# /opt/Alcatel-
Lucent/serviceability/bics_applications/bin/prepareUsbdisk -f
Please choose the format to use :
4 - FAT32
3 - NTFS-long (takes several hours)
2 - NTFS-quick
1 - EXT3
0 - Quit the current program.
Your choice : 1
You chose EXT3
All data will be erased on /dev/sdb1
Are you sure ? (Y)es/(N)o [N]: y
Disk is now formatted [ OK ]
Disk is now ready [ OK ]

6.6 Troubleshooting tools

      !"  #        45/73

Chapter 6  !    "' )( !!

6.6.1 checkAll.sh
The aim of this tool, which operates for all OpenTouch systems, when connected as root, is to
help troubleshooting by running all embedded diagnoses at once (checkCertificates.sh),
and verifying that all mandatory services are running, just as service opentouchd status
would do.
Use checkAll.sh -l to list auto-diagnoses tools embedded in this tool.
Example:

46/73       !"  #       

  !    "' )( !!

[root@tssf161]# checkAll.sh
================ Start checkAll.sh in version 2.1 build 20141209
===============
Troubleshooting
System Config [ OK ]
OXE VM [ OK ]
DNS [ OK ]
OMS VM [ OK ]
Certificates check failed with code 1: [FAILED]
For more details, run: checkCertificates.sh
Clock check failed with code 4: [FAILED]
For more details, run: checkClock.sh
Host Resources [ OK ]
Linux Config [ OK ]
Licensing check failed with code 2: [FAILED]
[FAILED] 02. The OT version (2.1.000.071) does not match the one in the
license (ICE_RELEASE=6 is 2.0 IT3 <= version < 2.1 IT5).
Please install a new valid license
[FAILED] 09. There are some (1) inconsistent features, this means that your
license does not match what is installed on your OT.
Please request a new adapted license.
The inconsistency is checked every night at 2:00 AM and 15 minutes after
the start of the CMS, thus new licenses will become consistent only 15
minutes after restart or tomorrow after 2:00 AM.
Inconsistent features: ICE_RELEASE.
8770 VM [ OK ]
Services
Nuance [ OK ]
OFS mySQL [ OK ]
OFS Tomcat [ OK ]
Acapi [ OK ]
ACS PostgreSQL [ OK ]
AMS Media Control [ OK ]
Apache [ OK ]
CMS [ OK ]
Connector 2007 [ OK ]
ECS [ OK ]
ICS Group [ OK ]
Lama [ OK ]
Maintenance Tool [ OK ]
Masc [ OK ]
OTS [ OK ]
PRS [ OK ]
Scorpio [ OK ]
Shrew [ OK ]
Solution Control [ OK ]
Tomcat [ OK ]
OFS Services [ OK ]
ACS Group [ OK ]
AMS Resource Manager [ OK ]
Chameleon [ OK ]
Config Proxy [ OK ]
CRS [ OK ]
Extensible Services [ OK ]
Flexlm [ OK ]
Martin [ OK ]
Message Broker [ OK ]
Mule [ OK ]
OMP [ OK ]
PMS [ OK ]
PostgreSQL Infra [ OK ]
SIP Server [ OK ]
UDAS [ OK ]
ACS [ OK ]
imap4fe [ OK ]
============================= Potential issue(s): 3
============================
[FAILED] Certificates check failed with code 1:
For more details, run: checkCertificates.sh
[FAILED] Clock check failed with code 4:
For more details, run: checkClock.sh
[FAILED] Licensing check failed with code 2:
[FAILED] 02. The OT version (2.1.000.071) does not match the one in the
license (ICE_RELEASE=6 is 2.0 IT3 <= version < 2.1 IT5).
Please install a new valid license
[FAILED] 09. There are some (1) inconsistent features, this means that your

      !"  #        47/73

Chapter 6  !    "' )( !!

license does not match what is installed on your OT.

Please request a new adapted license.
The inconsistency is checked every night at 2:00 AM and 15 minutes after
the start of the CMS, thus new licenses will become consistent only 15
minutes after restart or tomorrow after 2:00 AM.
Inconsistent features: ICE_RELEASE.
For more details, run: checkLicensing.sh

6.6.2 Service
This command is used to display the status and to start/stop/restart OpenTouch services. It
must be launched as root. This command can be used as follows:
[root@tssf161 /]# service <service/service group name> status

[root@tssf161 /]# service <service/service group name> start

[root@tssf161 /]# service <service/service group name> stop

[root@tssf161 /]# service <service/service group name> restart

All the necessary services for the OpenTouch operations are grouped into opentouchd. You
can verify the status/start/stop/restart of these services using the following command:
[root@tssf161 /]# service opentouchd status (or stop or start or restart)
You can use this command for any one of the services in the opentouchd group (for
example: flexlmd) or separately for services outside the opentouchd group (for example:
ntp) as follows:
[root@tssf161 /]# service flexlmd status (or start or stop or restart)
[root@tssf161 /]# service ntpd status (or start or stop or restart)
List of the OpenTouch services
- acapid
- alclrd
- apached
- cmsd
- connector2007d
- crsd
- ecsd
- imap4fed
- imsd
- lamad
- larkd
- liond
- mainttoold
- martind
- mascd
- otsd
- pmsd

48/73       !"  #       

  !    "' )( !!

- prsd
- scorpiod
- shrewd
- tomcatd
- udasd

6.6.3 Serverstatus
This command displays a consolidated view of the server statuses for a redundant pair of
OpenTouch servers.
The command can be invoked from any of the two servers, providing a status of the two
servers in the same output. The output provides a consolidated HA role for both servers
(Primary, Backup, Unknown). The static Primary or Backup type of server, as defined at post
installation, is also displayed.
The consolidated role depends on:
- The running state of OpenTouch components managed by the solution control. This
excludes, for example, the Fax server or the message broker. In case of groups (ICS or
ACS groups) only the top level status is taken into account
- The HA state of OT components
- The state of virtual IPs
- The state of DRBD replication
- The state of message broker cluster
A given host is an operational Primary when:
- All OpenTouch components are running properly on the host
- All components are Primary on this host
Exception: the Resource Manager is always Primary on the default Primary host
- All 9 service FQDN are mounted on this host
Exception: media service always is mounted on the default Primary host
- DRBD is operational with this host for all three partitions: ics group, postgresql5433,
oamp:
• Acting as Primary on this host
• If the partition is mounted
• With the proper state for cs, ds, p attributes
Note 1:
As the backup may be disconnected, the fact that DRBD replication is not operational is not a
relevant criterion.
A given host is an operational backup when:
- All OpenTouch components are running properly on the host
- All components are Backup on this host.
Exception: the Resource Manager is always Primary on the default Primary host
- All 9 service FQDN are not mounted on this host
Exception: media service is always mounted on the default Primary host, even if role is

      !"  #        49/73

Chapter 6  !    "' )( !!

Backup
- DRBD replication is operational with this host for all three partitions: ics group,
postgresql5433, oamp:
• Acting as Secondary on this host and Primary on the other
• If data replication is taking place from the remote host to this host
• If the partition is not mounted
- The message broker cluster contains two running nodes (primary and backup)
Note 2:
A correctly running message broker cluster is mandatory for operation of backup server and
consequent failover from primary to backup. It is not the case for the primary server, which can
operate regardless of the state of the cluster.
Theoretical role of a host :
When asserting the server role, the assumption is that it should have the same role as the
component in charge of the global switch over (i.e. FSM, Full Switch over Manager). In case of
inconsistency, the display is based on this assumption, and shows all the components that run
on the host with the wrong role. A given host is marked as unknown if any of the conditions is
not met, and the display states the reason why. A given pair of redundant hosts is an
operational HA pair if it has an operational Primary and an operational Backup
Examples:
- Status command on otmsp host:
otmsp# serverstatus
Checking solution control status... PRIMARY
Checking DRBD status... PRIMARY
Checking service IPs status... PRIMARY
Wed Dec 18 17:35:14 CET 2014
Local server otmsp static role is PRIMARY, current role is PRIMARY
Remote server otmsb static role is BACKUP, current role is BACKUP
- Status command on otmsb host:
otmsb# serverstatus
Checking solution control status... BACKUP
Checking DRBD status... BACKUP
Checking service IPs status... BACKUP
Wed Dec 18 17:37:21 CET 2014
Local server otmsp static role is BACKUP, current role is BACKUP
Remote server otmb static role is PRIMARY, current role is PRIMARY
- Status command on otmsp host with HA not ok:

50/73       !"  #       

  !    "' )( !!

otmsp# serverstatus
Checking solution control status... UNKNOWN
Checking DRBD status... UNKNOWN
Checking service IPs status... UNKNOWN
Wed Dec 18 17:35:14 CET 2014
Local server otmsp static role is PRIMARY, current role is UNKNOWN
Remote server otmsb static role is BACKUP, current role is UNKNOWN
Application issue(s):
- ICS_1 should be Backup but is Primary
- confserv_1 should be Backup but is Primary
- OMPInfra_1 should be Backup but is Primary
- SolutionControlServer_1 should be Backup but is Primary
DRBD issue(s):
- there is a mix of Primary and Secondary resources
- ics-group is Primary
- oamp is Primary
- postgresql5433 is Secondary
Service IP issue(s):
- the mounted IPs on this server don't correspond to PRIMARY or BACKUP
role
- HA_VOICE_SERVICE_IP (172.27.169.173) is not mounted
- HA_ICS_SERVICE_IP (172.27.169.174) is mounted
- HA_INFRA_SERVICE_IP (172.27.169.175) is mounted
- HA_DB_SERVICE_IP (172.27.169.176) is not mounted
- HA_SIP_SERVICE_IP (172.27.169.172) is not mounted
- HA_MEDIA_SERVICE_IP (172.27.169.178) is not mounted
- HA_LICENSE_SERVICE_IP (172.27.169.177) is not mounted
- HA_ACS_SERVICE_IP (172.27.169.179) is not mounted
- Status command on otmsp host and otmsb not running:
otmsp# serverstatus
Checking solution control status... PRIMARY
Checking DRBD status... PRIMARY
Checking service IPs status... PRIMARY
Wed Dec 18 17:35:14 CET 2014
Local server otmsp static role is PRIMARY, current role is PRIMARY
Remote server otmsb static role is BACKUP, current role is UNKNOWN
Application issue(s):
- remote server is down or LCA is not running
- Status command on otmsb host and otmsp not running:
otmsp# serverstatus
Checking solution control status... UNKNOWN
Checking DRBD status... BACKUP
Checking service IPs status... BACKUP
Wed Dec 18 17:37:21 CET 2014
Local server otmsp static role is BACKUP, current role is UNKNOWN
Remote server otmb static role is PRIMARY, current role is PRIMARY
Application issue(s):
- Local server is down or LCA is not running

6.6.4 Ot-moni.sh
Ot-moni.sh allows to display lot of information concerning the server:
- Monitoring hardware (Aluid, UUID, MAC address, server type, memory, hard disks)
- Monitoring partition
- Monitoring inodes
- Monitoring swap
- Monitoring virtualization
- Monitoring time
- Monitoring load
- Monitoring Ethernet
- Monitoring USB

      !"  #        51/73

Chapter 6  !    "' )( !!

- Monitoring NFS
- Monitoring DRBD

52/73       !"  #       

  !    "' )( !!

[root@tssf161 ~]# ot-moni.sh

******************************* MONITORING
HARD ********************************
AluID Unchanged ALUID=11841D789BD7EBBA4F0003604786C229
UtcDate=2015-01-12_09:52:10 (Aluid was set on utcDate=2014-09-15_11:16:23)
ID - UUID: 35353736-3739-5A43-3334-313735424259
- Mac address: 40:A8:F0:75:BF:84
Server Type - Manufacturer: HP - Product Name: ProLiant DL320e Gen8
Chassis - Manufacturer: HP - Type: Rack Mount Chassis
Processor - Family: Xeon - Manufacturer: Intel - Version: Intel(R) Xeon(R)
CPU E3-1230 V2 @ 3.30GHz
Memory - Total Size: 19 GB, 19952 MB
Hard Drives - Total Size: 1000.1 GB
RAID : - 1 x RAID bus controller: Intel Corporation 6 Series/C200 Series
Chipset Family SATA RAID Controller (rev 05) - 1
x RAID bus controller: Hewlett-Packard Company Smart
Array Gen8 Controllers (rev 01)
Ethernet - 2 x Ethernet controller: Broadcom Corporation NetXtreme BCM5717
Gigabit Ethernet PCIe (rev 10)
USB - 1 x USB controller:
Intel Corporation 6 Series/C200 Series Chipset Family
USB Enhanced Host Controller #2 (rev 05) - 1 x USB
controller: Intel Corporation 6 Series/C200 Series
Chipset Family USB Enhanced Host Controller #1 (rev
05) - 1 x USB controller: Hewlett-Packard Company
Integrated Lights-Out Standard Virtual USB Controller (rev 02)
******************************* MONITORING
PARTTIONS ***************************
Filesystem Size Used AvailUse% Mounted on
/dev/mapper/vg_root_02-lv_root 32G 18G 13G 59% / [ OK ]
/dev/mapper/vg_root_02-lv_logs 22G 800M 20G 4% /logs [ OK ]
/dev/mapper/vg_common-lv_libvirt 111G 80G
26G 76% /mnt/virtualmachines [ OK ]
/dev/mapper/vg_common-lv_var_backup 402G 4.1G
378G 2% /var/backup [ OK ]
/dev/mapper/vg_root_02-lv_drbd1 81G 222M
76G 1% /var/data/ics-group [ OK ]
/dev/mapper/vg_root_02-lv_drbd4 163M 13M
142M 8% /var/data/moh [ OK ]
/dev/mapper/vg_root_02-lv_drbd3 11G 241M
9.8G 3% /var/data/oamp [ OK ]
/dev/mapper/vg_root_02-lv_ofs 8.5G 206M
7.9G 3% /var/data/ofs [ OK ]
/dev/mapper/vg_root_02-lv_postgresql 11G 257M
9.8G 3% /var/data/postgresql5432 [ OK ]
/dev/mapper/vg_root_02-lv_drbd2 11G 311M
9.8G 4% /var/data/postgresql5433 [ OK ]
/dev/mapper/vg_root_02-lv_slides 54G 193M
51G 1% /var/data/slides [ OK ]
******************************* MONITORING
INODES ******************************
Filesystem Inodes IUsedIFreeIUse% Mounted on
/dev/mapper/vg_root_02-lv_root 2.0M 322k 1.7M 17% / [ OK ]
/dev/mapper/vg_root_02-lv_logs 1.4M 940 1.4M 1% /logs [ OK ]
/dev/mapper/vg_common-lv_libvirt 6.9M
25 6.9M 1% /mnt/virtualmachines [ OK ]
/dev/mapper/vg_common-lv_var_backup 25M
555 25M 1% /var/backup [ OK ]
/dev/mapper/vg_root_02-lv_drbd1 5.0M
207 5.0M 1% /var/data/ics-group [ OK ]
/dev/mapper/vg_root_02-lv_drbd4 41k
43 41k 1% /var/data/moh [ OK ]
/dev/mapper/vg_root_02-lv_drbd3 656k
264 656k 1% /var/data/oamp [ OK ]
/dev/mapper/vg_root_02-lv_ofs 525k
2.2k 523k 1% /var/data/ofs [ OK ]
/dev/mapper/vg_root_02-lv_postgresql 656k
1.3k 655k 1% /var/data/postgresql5432 [ OK ]
/dev/mapper/vg_root_02-lv_drbd2 656k
5.1k 651k 1% /var/data/postgresql5433 [ OK ]
/dev/mapper/vg_root_02-lv_slides 3.4M
509 3.4M 1% /var/data/slides [ OK ]
******************************** MONITORING
SWAP *******************************

      !"  #        53/73

Chapter 6  !    "' )( !!

total used free (Gb)

Swap: 15 0 15
[ OK ]
**************************** MONITORING VIRTUALISATION
*************************
Server running on a physical environment
product ProLiant DL320e Gen8
******************************* MONITORING
TIME ********************************
Current date: Mon Jan 12 10:52:11 CET 2015
Date UTC : Mon Jan 12 09:52:11 UTC 2015
Server started since: 21 day(s), 1 hour(s), 9 minute(s) et 25 second(s)
******************************* MONITORING
LOAD ********************************
CPU usage (8 cpu) : 3% [ OK ]
Load average (8 cpu) : (during 1 minute) 0.27, (15 minutes) 0.19 [ OK ]
Memory load: 90%
***************************** MONITORING ETHERNET
******************************
Settings for eth0:
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Link detected: yes
rx_octets: 11634268998
rx_fragments: 0
rx_ucast_packets: 5902109
Settings for eth1:
Link detected: no
********************************* MONITORING
USB *******************************
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
bDeviceClass 9 Hub
bDeviceProtocol 0 Full speed (or root) hub
iProduct 2 EHCI Host Controller
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
bDeviceClass 9 Hub
bDeviceProtocol 0 Full speed (or root) hub
iProduct 2 EHCI Host Controller
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
bDeviceClass 9 Hub
bDeviceProtocol 0 Full speed (or root) hub
iProduct 2 UHCI Host Controller
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
bDeviceClass 9 Hub
bDeviceProtocol 1 Single TT
iProduct 0
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
bDeviceClass 9 Hub
bDeviceProtocol 0 Full speed (or root) hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
bDeviceClass 9 Hub
bDeviceProtocol 1 Single TT
iProduct 0
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
bDeviceClass 9 Hub
bDeviceProtocol 0 Full speed (or root) hub

54/73       !"  #       

  !    "' )( !!

Bus 001 Device 004: ID 0a81:0205 Chesen Electronics

Corp. PS/2 Keyboard+Mouse Adapter
bDeviceClass 0 (Defined at Interface level)
bDeviceProtocol 0
iProduct 2 PS2 to USB Converter
(Bus Powered)
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
Bus 002 Device 003: ID 0424:2660 Standard Microsystems Corp.
bDeviceClass 9 Hub
bDeviceProtocol 1 Single TT
iProduct 0
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
bDeviceClass 9 Hub
bDeviceProtocol 1 Single TT
********************************* MONITORING
NFS *******************************
Serveur 172.27.132.240:
Filesystem Size Used Avail Use% Mounted on
172.27.132.240:/volume1/ccd/temp/ET/immersion/OTBE2.1.000.071
5.0T 3.8T 1.2T 77% /mnt/nfs
172.27.132.240:/volume1/ccd/temp/ET/immersion/OTBE2.1.000.071 /mnt/nfs nfs
rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,prot
o=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.27.132.240,mountvers=3,mountport=892,mount
proto=udp,local_lock=none,addr=172.27.132.240 0 0
********************************* MONITORING
DRBD ******************************
There is no drbd

6.6.5 checkClock.sh
The aim of this tool is to gather clock and NTP information and verify the most common issues,
such as: no reliable NTP server. A file is created to collect all the information that can be sent
to technical support.

      !"  #        55/73

Chapter 6  !    "' )( !!

[root@tssf161 ~]# checkClock.sh

INFO : checkClock version 1.18
INFO : IP address : 172.27.139.161
INFO : FQDN : tssf161.fr.alcatel-lucent.com
INFO : Result of command ifconfig is added to the log file
INFO : test 1 - Hyperthreading
INFO : dmidecode output has been sent to /tmp/dmidecode.log
WARNING : Hyper-threading is activated in the BIOS of this computer, 8 CPUs
counted for 4 cores
INFO : It is recommended to avoid it.
INFO : collecting information - hwclock
INFO : Mon 12 Jan 2015 11:34:16 AM CET -0.515967 seconds
INFO : collecting information - date
INFO : Mon 12 Jan 2015 11:34:16 AM CET
INFO : test 2 - hardware clock vs system time
SUCCESS : No time difference between system time and hardware clock
INFO : test 3 - chkconfig ntpd
SUCCESS : ntpd is scheduled to start in the current runlevel
INFO : test 4 - service ntpd status
SUCCESS : ntpd is started
INFO : test 5 - crontab -l
INFO : crontab -l output has been sent to /tmp/crontab.log
SUCCESS : crontab does not call ntpdate
INFO : test 6 - logfile
SUCCESS : logfile = /var/log/ntpd.log
INFO : collecting information - bics.conf
INFO : NTP parameters in bics.conf :
HOST_NTP1="172.27.139.161"
HOST_NTP2=""
INFO : collecting information - ntpdc -p
INFO : remote local st
poll reach delay offset disp
=======================================================================
*LOCAL(0) 127.0.0.1 5 64 377 0.00000 0.000000 0.03062
INFO : collecting information - ntpdc -pn
INFO : remote local st
poll reach delay offset disp
=======================================================================
*127.127.1.0 127.0.0.1 5 64 377 0.00000 0.000000 0.03062
INFO : test 7 - local time source
INFO : The local time source 127.127.1.0 is declared in /etc/ntp.conf. This
system has no other time source listed so this local time source is needed
to sync the OXE VM.
INFO : test 8 - sync status
INFO : The system is synchronized on the local time source
INFO : test 9 - checking the number of NTP servers defined in /etc/ntp.conf
ERROR : No NTP server defined in /etc/ntp.conf
INFO : collecting information - ntpq peers
remote refid st t when poll reach delay offset
jitter
=======================================================================
*127.127.1.0 .LOCL. 5 l 24
64 377 0.000 0.000 0.000
INFO : collecting information - ntpq associations
ind assID status conf reach auth condition last_event cnt
===========================================================
1 50953 9614 yes yes none sys.peer reachable 1
INFO : test 10 - query of potential NTP server 172.27.139.161 found in VHE
sync sources (dmictouch xml config files)
INFO : ntpdate -q 172.27.139.161 :
SUCCESS : 172.27.139.161 is a potential NTP source
INFO : test 11 - query of potential NTP server
tssf161.fr.alcatel-lucent.com found in VLE sync sources (dmictouch txt
config files)
INFO : ntpdate -q tssf161.fr.alcatel-lucent.com :
SUCCESS : tssf161.fr.alcatel-lucent.com is a potential NTP source
INFO : The results have been archived in
/tmp/checkClock.tssf161.201501121134.tgz
Issues detected :
1 - Hyper-threading is activated in the BIOS of this computer, 8 CPUs
counted for 4 cores
2 - No NTP server defined in /etc/ntp.conf
ERROR : 2 issue(s) out of 11 tests
If a time drift issue appears, the script must be used as follows, before proceeding with an
OpenTouch Business Edition server restart which will solve the issue:

56/73       !"  #       

  !    "' )( !!

1. Open an eSR and the script (checkClock-xx.zip) will be provided by Technical

Support team. Otherwise, the script is also available from the Customer Care article
https://businessportal.alcatel- lucent.com/kcs?articleID=000013312
2. Upload and unzip on OmniPCX Enterprise vm and OpenTouch Business Edition systems
(ex: under /tmp)
3. Execute: chmod +x ./checkClock-xx.sh
4. Run it as root on the OmniPCX Enterprise and OpenTouch Business Edition:
./checkClock-xx.sh
5. Collect and attach the generated files to the eSR: (files
/tmp/checkClock.XXXXX.YYYY.tgz for the OmniPCX Enterprise and OpenTouch
Business Edition systems)
6. Request to proceed with virtualisation layer restart test before rebooting the OpenTouch
Business Edition server. Please contact the Technical Support for procedure details

6.6.6 checkCertificate.sh
This command diagnoses and displays information related to the OpenTouch server
certificates. It verifies the consistency of Certificates on the host. A file is created to collect all
the information that can be sent to the technical support. Login as root.
[root@tssf161 bin]# checkCertificates.sh

The verifications performed by this command include:

- Checking the consistency of certificates (ca.key, ca.pem, ca.srl, keystore,
server.ctl, server.key, server.pem and truststore) under
/var/data/certificates
- Checking the consistency of certificates (rsa.<OT FQDN>.cert.pem) under
/usr/muxer. Among others, it will indicate if the certificate is a pre-loaded and generic
one or a customized one (internal auto- generated one or generated on an external PKI).
- Verification of server certificate
- Verification of serial/issuer/subject information
- Verification of signature algorithm information
- Evaluation of expiration date
- Verification of the keystore and truststore
- Verification of the server certificate sent by the SSL/TLS server...
- Match of OT certificate versus OT server.ctl
- Match of OT certificate versus OT ctl_VHE8082 or OT ctl_VHE8088
- Verification of the signature for ctl_VHE8082 or OT ctl_VHE8088

6.6.7 checkLicensing.sh
This command provides diagnostic and information collection on licensing. Login as root.
The script can be used on OpenTouch Multimedia Services, OpenTouch Business Edition,
OTMC and on flexlm servers on any version.

      !"  #        57/73

Chapter 6  !    "' )( !!

The aim of this tool is to:

- Gather information on the server (hardware model, Host ID, ALU ID, Dongle ID…) and the
deployed licenses (type, version…)
- Check if the licensing configuration is consistent, for instance: did the administrator deploy
the licenses files in the right place ? The script also offers a correction if applicable.
- Check if internal or external flexlm server is used and if HA is active or not
- Store all licensing information and logs in an archive in /tmp. This archive can then be
shared with your support team if you suspect a licensing issue
The script makes an analysis on the current host only. If using HA and/or external flex server,
run the script on each host and share the generated archive of each host with your support
team.
[root@tssf161 bin]# checkLicensing.sh
##### Start checkLicensing.sh 2.0.1 build 20140630 #####
##### Server info #######
Package = OTBE
Version = 2.0.100.032
Hardware = ProLiant DL320e Gen8
Flex = internal
HostID = 40a8f075bf84 40a8f075bf85
ALUID = 11841D789BD7EBBA4F0003604786C229
HA = FALSE
##### Installed licenses #######
Licenses in: /var/data/licenses
140625-OTBE_HA_2.0_Eric-OTBE2.0-HA-intflex-primary.ice
OTBE 2.0 flex license
HostID = ALUID=11841D789BD7EBBA4F0003604786C229
OXE Virtual CPU-ID = K00010031
OTID = O000014434
With HA, role = PRIMARY
OK | 13. This file contains USE_SERVER in second line.
OK | 14. This licenses hostid matches the host.
OK | 18. Your license expires in 270 days.
alchostid.cfg
OT nodelock file
OTID = O000014434
OK | 10. File format is OK. alcotuc.lic
alcotuc.lic
OT alcotuc.lic default license (taken into account)
LicInfo.sh
Dummy SBC license
nmc8770R13_LAB.sw8770
8770 1.3 license file
8770Handle = 123456AB
##### Running some basic tests #######
OK | 01. Only one OT license has been deployed
OK | 02. The OT version (2.0.100.032) matches the one in the license
(ICE_RELEASE=6 is version >= 2.0 IT3).
OK | 08. OT nodelocking (OTID) is correct.
OK | 03. Ping of own FQDN successful.
OK | 05. Flex service is running.
OK | 06. ALCFIRM daemon is running.
OK | 09. There are no inconsistent features
##### Creating an archive of licensing info and logs... Please wait.
#######
##### /tmp/licDump-tssf161-20140926-125006.tgz (567K) can now be downloaded
#######
##### Launch this command on any OT server of your solution to have a full
view of licenses, especially with external flex server #####
##### /!\ Do not forget to delete the old result files in the server
(/tmp/licDump-*) to save disk space #####
##### Potential issues: 0 #######
To locate all the generated files on your OpenTouch server:
root@tssf161 licenses]# ls -lhtr /tmp/lic*
To skip archive generation, execute:
[root@tssf161 bin]# checkLicensing.sh –d

58/73       !"  #       

  !    "' )( !!

6.6.8 checkdns
This tool is used to verify the DNS management on the OpenTouch and the resolution of
necessary hostnames.
It verifies forward/reverse resolution of all defined FQDNs (OpenTouch/OmniPCX
Enterprise//FlexLM) and the forward resolution OmniPCX Enterprise node name FQDN
(reverse resolution is not required for node name) with the DNS server.
Example of a successful DNS verification
[root@tssf161 /]# checkdns
Using external DNS1: 135.120.0.245
External DNS2 unused
DNS resolution of HOST: tssf161.fr.alcatel-lucent.com [ OK ]
Reverse resolution of HOST: 172.27.139.161 [ OK ]
DNS resolution of FLEXLM_SERVER: tssf161.fr.alcatel-lucent.com [ OK ]
Reverse resolution of FLEXLM_SERVER: 172.27.139.161 [ OK ]
FLEXLM_SERVER at 172.27.139.161 is reachable
DNS resolution of WIN:
tssf162.fr.alcatel-lucent.com [ OK ]
Reverse resolution of WIN:
172.27.139.162 [ OK ]
DNS resolution of OXE: tssf163.fr.alcatel-lucent.com [ OK ]
Reverse resolution of OXE: 172.27.139.163 [ OK ]
DNS resolution of OXE_NODENAME: node00106.fr.alcatel-lucent.com [ OK ]

6.6.9 raidstatus
Use this command to determine the current state of the raid unit. This command returns one of
the following statuses:
- DEGRADED: one hard disk has been removed or is out of order
- RECOVERING: resynchronization between master and slave hard disks (further to
desynschronization) is now starting
- OK: the unit is in optimal state
Hard disk problems (crash or failure) can also be detected on a server with Raid 1 hot swap:
- Led [!] in front of rack comes on (orange color)
- No more green led flashing on erroneous hard disk
- Logged information in the files /var/log/messages*
- Alarm appears on the management console

6.6.10 checkSystem
This command allows to verify the consistency between the bics.conf file and the system
configuration, it also allows to find network and VM issues.

      !"  #        59/73

Chapter 6  !    "' )( !!

[root@tssf161 ~]# checkSystem.sh

============== Start checkSystem.sh in version 2.1 build 20141127
==============
================================================================================
= Server details
=
Type = otbe
Version = 2.1.000.071
Hardware = ProLiant DL320e Gen8
Configuration parameter HOST_NAME = tssf161
Configuration parameter HOST_DOMAIN = fr.alcatel-lucent.com
Configuration parameter HOST_IP = 172.27.139.161
Configuration parameter HOST_MASK = 255.255.0.0
Configuration parameter HOST_ROUTER = 172.27.132.1
Configuration parameter LOCAL_DNS = 0
Configuration parameter HOST_DNS1 = 135.120.0.245
Configuration parameter HOST_DNS2 =
Configuration parameter HOST_NTP1 = 172.27.139.161
Configuration parameter HOST_NTP2 =
Configuration parameter HA_MODE = FALSE
Configuration parameter HA_TYPE = PRIMARY
Configuration parameter HA_PRIMARY_IP = 172.27.139.161
================================================================================
= Running host
tests =
================================================================================
01. Host name (tssf161) is equal [ OK ]
02. Domain (fr.alcatel-lucent.com) is equal [ OK ]
03. IP (172.27.139.161) is equal [ OK ]
04. Mask (255.255.0.0) is equal [ OK ]
05. Gateway (172.27.132.1) is equal [ OK ]
================================================================================
= Running DNS
tests =
================================================================================
DNS server is external.
10. Check if all DNS name servers found in /etc/resolv.conf
are also defined in
/var/data/bics/bics.conf
11. Check if all DNS name servers found in /var/data/bics/bics.conf
are also defined in
/etc/resolv.conf [ OK ]
================================================================================
= Running Forwarder
tests =
================================================================================
DNS server is external. To check DNS forwarders,
it has to be local. [SKIPPED]
================================================================================
= Running NTP
tests =
================================================================================
30. Check if all NTP servers found in /etc/ntp.conf are also defined in
/var/data/bics/bics.conf
[ OK ]
31. Check if all NTP servers found in /var/data/bics/bics.conf
are also defined in
/etc/ntp.conf
[ OK ]
=============================
Potential issue(s): 0 ============================

6.6.11 checkCms
The tool allows to verify the consistency of the OpenTouch configuration service.
It displays the current status of the service and gives feedback on the latest data migration
when upgrading to a new version.

60/73       !"  #       

  !    "' )( !!

[root@frcolv10icecms20 toolexec]# checkCms.sh

State: READY
no HA
product type | addon
product version | 10.0.000.040
cms version | 10.0.040.001
datamodel version| 10.0.040.001
CMS status [ OK ]
Migration status | COMPLETED
EasyAdmin status | COMPLETED
PostReady migration status | NOT_COMPLETED

6.7 Log management tools

6.7.1 DLA – dynamic log activation

DLA enables and collects logs. Login as root.
To access and operation DLA, see: Maintenance and Supervision - Maintenance portal

6.7.2 loglevel.sh
This command enables/disables logs for components.
Loglevel.sh component=<Component_Name> logger=<Logger_Name> level=>Level_name>

To find the name of the component: enter loglevel.sh list. They are:
- ams
- authenticationbasic
- authenticationform
- AMSResourceManager
- AMSMediaControl
- chameleon
- cmpa4fe
- cms
- configproxy
- connector2007
- crs
- ExtensibleServices
- eccnoe
- ecs
- lama
- martin
- masc
- metrics
- mpcnoe
- mule

      !"  #        61/73

Chapter 6  !    "' )( !!

- my_assistant
- my_phone
- my_messaging
- noe_teamwork
- ots
- otsControl
- my_phone_outlook_coupling
- perf
- pms
- prs
- prsControl
- sc
- scorpio
- shrew
- shrewControl
- SIPServer
- tomcat
- uda
- udas
- unifiedLogin
- voice_applications
- wbm
To find the logger for the component: enter loglevel.sh component=
<Component_Name> list.
Example:
[root@tssf161 ~]# loglevel.sh component=pms list
Component: pms
Logger : root, level: off
Logger : exceptions, level: off
Logger : protocoles, level: off
Logger : com.alcatel, level: INFO
Logger : com.alu, level: WARN
Examples of syntax:
loglevel.sh component=pms logger=* level=debug
loglevel.sh component=pms logger=com.alcatel level=debug
loglevel.sh component=pms logger=com.alu level=debug

6.7.3 logzipper
This tool is used to collect the entire logs available in the OpenTouch system in one archive.
By default, the archive is saved in /var/backup/tmp.
The collected log files are:

62/73       !"  #       

  !    "' )( !!

- /logs directory
- /var/log/ICE/InstallLog directory
- $ACAPI_HOME/log directory
- $ECC_HOME/version.txt file
- $OTS_HOME/dyn directory
- /logs directory in the inactive partition
- $DATA_HOME/bics/bics.conf file
- ECC_HOME/topology/topology.xml file
To collect all logs files, enter: logzipper.sh all
To collect log files for the last two days, enter: logzipper.sh 02 days
To collect log files for the last two weeks, enter: logzipper.sh 02 weeks
To collect log files for the last two months, enter: logzipper.sh 02 months
Example:
[root@tssf161 ~]# Logzipper.bin 02 days
Log Zipper
Initializing Log Zipper...
Searching for Java(tm) Virtual Machine...
........
Running Log Zipper...
no directory as parameter using default : /var/backup/tmp
Creating compressed file(s)...
Compressing
/mnt/inactive_partition/opt/Alcatel-Lucent/infra_services/acapi/log
Log files created since 2015-01-10 are collected.
Adding
_mnt_inactive_partition_opt_Alcatel-Lucent_infra_services_acapi_log.tgz
Compressing /mnt/inactive_partition/logs Log files created since 2015-01-10
are collected.
Adding _mnt_inactive_partition_logs.tgz Compressing
/mnt/inactive_partition/var/log Log files created since 2015-01-10 are
collected.
Adding _mnt_inactive_partition_var_log.zip
Compressing /mnt/inactive_partition/var/data/licenses Log files created
since 2015-01-10 are collected.
Adding _mnt_inactive_partition_var_data_licenses.tgz
Adding
_mnt_inactive_partition_opt_Alcatel-Lucent_infra_services_ots_dyn.notfound
Generating /mnt/inactive_partition/opt/Alcatel-Lucent/version.txt
Adding _mnt_inactive_partition_opt_Alcatel-Lucent_version.txt
Compressing /opt/Alcatel-Lucent/infra_services/acapi/log
Log files created since 2015-01-10 are collected.
Adding _opt_Alcatel-Lucent_infra_services_acapi_log.tgz
Compressing /logs Log files created since 2015-01-10 are collected.
Adding _logs.zip Compressing /var/log
Log files created since 2015-01-10 are collected.
Adding _var_log.zip Compressing /var/data/licenses
Log files created since 2015-01-10 are collected.
Adding _var_data_licenses.tgz
Adding _opt_Alcatel-Lucent_infra_services_ots_dyn.notfound
Generating /opt/Alcatel-Lucent/version.txt
Adding _opt_Alcatel-Lucent_version.txt
Make final file
Logzipper file created :
/var/backup/tmp/logs_tssf161_12-01-15_14h35m36s.tgz

6.7.4 netcapture.sh
The aim of this tool is to make the management of network traces easier and hide the
complexity of the tcpdump command. This tool works on OpenTouch as well as flexVM.

      !"  #        63/73

Chapter 6  !    "' )( !!

To view details on the tool, enter: netcapture.sh –h

6.7.4.1 Starting a capture
To start a new tcpdump trace, enter: netcapture.sh start.
The trace is stored in a rotating buffer. This means that the same files are used, limiting trace
size to a specific amount of space in the directory.
The name of the file takes the form: netcapture- <ipaddress> <datetime>.pcap
The capture only starts if there is no other active capture and if there is enough place on the
target partition.
The following options can be used to change the default behavior:
- -c <count>, --count <count>
This limits the number of files created to the number of your choice. Files are overwritten
from the beginning, creating a "rotating" buffer. The default value is 3.
- -s <size>, --size <size>
This specifies the size of each pcap file in Mb. The default value is 30.
- -o <folder>, --output-folder <folder>
This specifies the location for pcap files. The default directory is /tmp/netcaptures.
- - f <filters>, --filter <filters>
This executes tcpdump with the specified filters, allowing to capture only part of the traffic.
Examples of filters:
• Capture all packets arriving at or departing from host1, where host1 can be an FQDN
or an IP address: host host1
• Capture all packets except those from or to host1 or host2: host not host1 and
not host2
• Capture traffic between host1 and either host2 or host3: host host1 and \(
host2 or host3 \)
• Capture traffic of a range of mac adresses, here proprietary hardphones having a
mac@ starting with 00809f: ‘ether[0:4] & 0xffffff00 = 0x00809f00 or
ether[6:4] & 0xffffff00 = 0x00809f00'
• Capture HTTP traffic on TCP port 80: tcp port 80
6.7.4.2 Stopping a capture
To stop the current tcpdump capture, enter: netcapture.sh stop
6.7.4.3 Getting capture status
Use netcapture.sh status to verify if a capture is running, and view details on the
captures in the output directory.
Example:

64/73       !"  #       

  !    "' )( !!

============================ tcpdump service status

============================
tcpdump is (PID=5185) [RUNNING]
================================ Available space
===============================
There are 13G available on working partition (/ is 56% used)
With current profile (3 files(s), each 30M max), trace will take up to 90M.
============================== List existing dumps
=============================
Listing files in /tmp/netcaptures
/tmp/netcaptures/netcapture-localhost-20141030-181518.pcap0
1.8M, from 18:15:19 to 18:34:24, duration: 00:19:05
/tmp/netcaptures/netcapture-localhost-20141030-183424.pcap0
110K, from 18:34:25 to 18:35:06, duration: 00:00:41
With to current profile (90M), trace will record about 09h00m.
The status attribute provides an estimation of the capture time based on already captured
traces and the target file size.
The current capture files are displayed in yellow. The former captures are in white.
The start and end time, duration and size are displayed for each capture file, making it easier
to save for analysis the sole file where the problem arose.
The status attribute lists all current and former traces files in the default directory, and in the
directory specified with netcapture.sh status -o <folder2> option, and the directroy
which was used previously netcapture.sh start -o <folder2>
6.7.4.4 Archiving captures
To create an archive of all tcpdump traces in the output directory, enter: netcapture.sh
zip.
This attribute stops the running trace, if any.
The attributes: -o <folder>, --output-fodler <folder> can be used to zip files from a
directory different from the default directory.
A text file describing all captures is stored in the zip file and all zipped files are deleted from
the output directory.
6.7.4.5 Cleaning captures
To delete all tcpdump traces and zip files in the output directory, in other words, to free space
on the server, enter: netcapture.sh clean.
This attribute stops the running trace, if any.
The attributes: -o <folder>, --output-fodler <folder> can be used to clean files from
a directory different from the default directory.

6.7.5 getSupport
The getSupport script collects logs from OpenTouch commands, syslog and applications
within virtual machines and puts them in a gzip file. Login as root.
This command can be run with the following options to collect necessary information:
- getSupport loghost to collect available log files whithin the host
- getSupport logvmOXE to collect available log files within vmOXE
- getSupport logvmManagement to collect available log files within vmManagement
- getSupport logallVM to collect available log files within all VMs

      !"  #        65/73

Chapter 6  !    "' )( !!

- getSupport logall to collect available log files within the OpenTouch

Example:
[root@tssf161 ~]# getSupport logall
Collecting logs on host ...
Success
Collecting logs on vmOXE ...
Getting log files ...
Success
Collecting logs on vmManagement ... Success Make archive
/mnt/nfs/bics/save/logs/tssf161.fr.alcatel-lucent.com-2015-01-12-
14h53.tar.bz2

6.8 Miscellaneous tools

6.8.1 lmutil
This command is used for FlexLM (license service) management. Login as root
To read all the options available, enter: [root@tssf161 var]#
/opt/Alcatel-Lucent/platform/flexlm/lmutil or [root@tssf161 /]#
$FLEXLM_HOME/lmutil
Example:
[root@tssf161 /]# $FLEXLM_HOME/lmutil
usage:
lmutil lmborrow -status
lmutil lmborrow -purge
lmutil lmborrow -purge -status
lmutil lmborrow -clear
lmutil lmborrow {all|vendor} dd-mmm-yyyy:[time]
lmutil lmborrow -return [-c licfile] [-d display_name] [-fqdn] [- vendor
name] feature
lmutil lmdiag [-c licfile] [-n]
lmutil lmdown [-c licfile] [-q] [-all] [-vendor name] [-force] [-help]
lmutil lmhostid [-ptype (VMW|HPV|PHY|AMZN|LMB|VM)] [-ether|-internet
(v4|v6)|-user|-n|
-display|-hostname|-hostdomain|-string|-long|-uuid
-eip|-ami|iid|-flexid]
lmutil lminstall [-i infile] [-o outfile]
[-overfmt {2, 3, 4, 5, 5.1, 6, 7.1, 8}] [-odecimal] [-maxlen n]
[-odecimal] [-maxlen n]
lmutil lmnewlog [-c licfile] vendor new-file, or
lmutil lmnewlog [-c licfile] feature new-file
lmutil lmpath -status
lmutil lmpath -override {all | vendor } path
lmutil lmpath -add {all | vendor } path
lmutil lmremove [-c licfile] feature user host display
lmutil lmremove [-c licfile] -h feature host port handle
lmutil lmreread [-c licfile] [-vendor name] [-all]
lmutil lmswitchr [-c licfile] vendor new-file, or
lmutil lmswitchr [-c licfile] feature new-file
lmutil lmstat [-c licfile] [lmstat-args]
lmutil lmswitch [-c licfile] vendor new-file, or
lmutil lmswitch [-c licfile] feature new-file
lmutil lmver flexlm_binary lmutil -help (prints this message)
lmutil utility_name -help (display detailed usage information)
To read all the feature values from the licenses file, enter: [root@tssf161 flexlm]#
$FLEXLM_HOME/lmutil lmstat -i
Example:

66/73       !"  #       

  !    "' )( !!

Feature Version
#licenses Expires Vendor
_______ _________ _________ __________
______
K00010031
1.0 1 24-jun-2015 ALCFIRM
O000014434 1.0 1 24-jun-2015
ALCFIRM
ICE_RELEASE
1.0 6 24-jun-2015 ALCFIRM
ICE_BUSINESS_COMMUNICATION
1.0 1500 24-jun-2015 ALCFIRM
ICE_CONFERENCING 1.0 1500 24-jun-2015
ALCFIRM
ICE_DESKTOP_MM
1.0 1500 24-jun-2015 ALCFIRM
ICE_DESKTOP_STD 1.0 1500 24-jun-2015
ALCFIRM
ICE_ENCRYPTION
1.0 1500 24-jun-2015 ALCFIRM
ICE_GR_LOCK 1.0 2 24-jun-2015
ALCFIRM
ICE_HA
1.0 1 24-jun-2015 ALCFIRM
ICE_HA_PRIMARY 1.0 2 24-jun-2015
ALCFIRM
ICE_ICM_ACU_USER
1.0 1500 24-jun-2015 ALCFIRM
ICE_IMAP_SESSION 1.0 1000 24-jun-2015
ALCFIRM
ICE_MESSAGING
1.0 1500 24-jun-2015 ALCFIRM
…
To read the licenses status on the flexlm servern enter: [root@tssf161 flexlm]#
$FLEXLM_HOME/lmutil lmstat -a
Example:
[root@tssf161 flexlm]# $FLEXLM_HOME/lmutil lmstat -a
License server status: 27000@tssf161
License file(s) on tssf161: /var/data/licenses/140625-OTBE_HA_2.0_Eric-
OTBE2.0-HA-intflex-primary.ice:/var/data/licenses/alcotuc.lic: tssf161:
license server UP (MASTER) v11.12.0
Vendor daemon status (on tssf161):
ALCFIRM: UP v11.12.0
Feature usage info:
Users of K00010031: (Total of 1 license issued; Total of 1 license in use)
"K00010031" v1.0, vendor: ALCFIRM floating license mtcl tssf163 /dev/tty
(v1.0) (tssf161/27000 1901), start Wed 9/24 16:49
Users of K000014434: (Total of 1 license issued; Total of 0 licenses in
use)
Users of ICE_RELEASE: (Total of 6 licenses issued; Total of 0 licenses in
use)
Users of ICE_BUSINESS_COMMUNICATION: (Total of 1500 licenses issued; Total
of 2 licenses in use)
To read the dongle ID on the flexlm server, enter: [root@tssf161 flexlm]#
$FLEXLM_HOME/lmutil lmhostid –flexid
Example:
[root@tssf161 flexlm]# $FLEXLM_HOME/lmutil lmhostid –flexid
Copyright (c) 1989-2007 Macrovision Europe Ltd. and/or Macrovision
Corporation. All Rights reserved.
The FLEXnet host ID of this machine is "FLEXID=9-4c0ef9ed"

6.8.2 RoutingConfigConsole.sh
This tool is used to get more information about the users routing profiles and its managements.
To leave the console, enter: exit

      !"  #        67/73

Chapter 6  !    "' )( !!

6.8.2.1 help attribute

Example:
[root@tssf161 ~]# routingConfigConsole.sh
Connected (Martin version 2.0.500.110)
spy> help
Martin provides routing management services.
It is mainly in charge of the configuration of the routing rules of the
users. Commands (use <tab> for auto-completion) :
applyProfileRoute <login profileId|profileName>: apply the user routing profile
getManagers: display all managers with their state
getProfiles <login>: display the user routing profiles
getProfiles <login|companyPhone>: display a global overview of the user
getUsers: display all users by login
getVersion: display the component version
getXmlRules <login>: display the user routing rules
reloadPropertyFile: reload the property file
resetUser <login>: reset the user (with loss of his custom profiles)
synchronizeUser <login>: synchronize the user
6.8.2.2 getUsers
Use this command to list all users from the Martin cache.
They are ordered by login. Company phone and category are also indicated.
Example:
[root@tssf161 ~]# routingConfigConsole.sh
Connected (Martin version 2.0.500.110)
spy> getUsers
SaurezJohn 31535 ACU-ComServ
afakoto 32000 ACU-OXE
alegaulois 32003 ACU-ComServ
atarac 32001 ACU-ComServ
barsingh 31040 ACU-OXE
bsauron 32004 ACU-OXE
dbergdal 32005 ACU-ComServ
gkerbuzuc 32006 ACU-OXE
gkorch 32007 ACU-ComServ
myuasa 32008 ACU-ComServ
ruthaug 32009 ACU-ComServ
sbhansali 32011 ACU-ComServ
smasrafi 32010 ACU-OXE
ACU-OXE : is connection user
ACU-ComServ : is conversation user
You can retrieve the list of users with a login starting with a prefix (case sensitive).
Example:
spy> getUsers g
gkerbuzuc 32006 ACU-OXE gkorch 32007 ACU-ComServ
gkorch 32007 ACU-ComServ

6.8.2.3 getUser
Use this command to get a general overview of a user from the Martin cache and the
configuration in CMS.
Attribute: login or company phone.
This results in the following information:

68/73       !"  #       

  !    "' )( !!

- User configuration
- Routing state
- Profiles
- Nomadic number
- Routing rules
- OmniPCX Enterprise routing status
Non synchronized data is indicated.
Example:

      !"  #        69/73

Chapter 6  !    "' )( !!

spy> getUser 32001

User overview (2015-01-07 15:20:16)
-- config: id=81802 login=atarac category=ACU-ComServ companyPhone=32001
dialingRule=1651 desktop=true tablet=true voiceMailRight=true
-- barringProfile: routeToLocal=true routeToExternalPstn=true
overflowOnBusy=true overflowOnNoResponse=true
overflowOnBusyOrNoResponse=true cancelOverflow=true
-- devices:
type=OTHER model=OTHER deviceId=NOMADIC_atarac status=UNDEFINED
-- appliedProfile=DEFAULT activeLocationProfileId=ALL_DEVICES
activeCurrentDeviceId=null
-- activeRoutes:
type=OVERFLOW overflowType=BUSY_NO_ANSWER
destinations:
type=MOBILE acceptable=false selected=false
type=HOME acceptable=false selected=false
type=OTHER acceptable=false selected=false
type=VOICEMAIL acceptable=true selected=true
type=USER acceptable=true selected=false
type=PRESENTATION name=FALLBACK service=CALLROUTING
destinations:
type=OFFICE acceptable=false selected=true
type=PC acceptable=false selected=true
type=TABLET acceptable=false selected=true
type=MOBILE acceptable=false selected=true
type=VIDEO acceptable=false selected=true type=HOME
acceptable=false selected=false
type=OTHER deviceId=NOMADIC_atarac acceptable=true
selected=false
type=FORWARD
destinations:
type=VOICEMAIL acceptable=true selected=false
type=USER acceptable=true selected=false
type=ASSISTANT acceptable=false selected=false
-- profiles:
id=0 name=DEFAULT default=true activable=true removable=false
renameable=false updatable=false currentDeviceId=null
routes:
type=FORWARD
destinations:
type=VOICEMAIL acceptable=true selected=false
type=USER acceptable=true selected=false
type=ASSISTANT acceptable=false selected=false
type=PRESENTATION name=FALLBACK service=CALLROUTING
destinations:
type=OFFICE acceptable=false selected=true
type=PC acceptable=false selected=true
type=TABLET acceptable=false selected=true
type=MOBILE acceptable=false selected=true
type=VIDEO acceptable=false selected=true
type=HOME acceptable=false selected=false
type=OTHER deviceId=NOMADIC_atarac acceptable=true
selected=false
selected=false
-- nomadicNumber:
value=none
-- routingRules:
<rule active="true" type="BUSY" id="BUSY_37802"> <actionPArt>
<routeTotype="FORWARD" forking="PARALLEL" <dest dynamicDN="voicemail"/>
</routeTo> </actionPart> </rule>
<rule active="true" type="NO_ANSWER" id="NO_ANSWER_37802">
<actionPArt> <routeTotype="FORWARD" forking="PARALLEL" <dest
dynamicDN="voicemail"/> </routeTo> </actionPart> </rule>

6.8.2.4 resetUser
Use this command resetUser to reinitialize a user in the Martin cache.
This command removes the user in the Martin cache and re-creates her/him from her/his
configuration read in CMS. For Conversation users, this resets the current profile and removes
all custom profiles.
Attribute: login.

70/73       !"  #       

  !    "' )( !!

Example:
spy> resetUser atarac
user 'atarac' resetted

6.8.2.5 synchronizeUser
Use this command to synchronize a user in the Martin cache from her/his configuration read in
CMS.
Attribute: login.
Example:
spy> synchronizeUser atarac
user 'atarac' modified by synchronization on routing state
spy> synchronizeUser atarac
user 'atarac' let unchanged by synchronization

6.8.2.6 getProfiles
Use this command to list all profiles of a user from the Martin cache.
Attribute: login.
Example:
spy> getProfiles alegaulois
profile-id='0', profile-name='DEFAULT', presentation='<*OFFICE 32100>, <*PC
32101>, <*TABLET>, <*MOBILE>, <*VIDEO>, <HOME>, <OTHER>',
forward='<VOICEMAIL>, <USER>' current-device='32100'
profile-id='10', profile-name='VHE', presentation='<*OFFICE 32100>, <*PC
32101>, <*TABLET>, <*MOBILE>, <*VIDEO>, <HOME>, <OTHER>',
forward='<VOICEMAIL>, <USER>' current-device='32100'
profile-id='11', profile-name='PC', presentation='<*OFFICE 32100>, <*PC
32101>, <*TABLET>, <*MOBILE>, <*VIDEO>, <HOME>, <OTHER>',
forward='<VOICEMAIL>, <USER>' current-device='32101'
The asterisk (*) indicates that the option is available to the user.
6.8.2.7 applyProfileRoute
Use this command to apply a routing profile to a user.
Attribute: login, profile name or id.
Example:
spy> applyProfileRoute alegaulois 11
Profile applied

Note:
Use the getProfiles command to view profile numbers.

6.8.2.8 getXmlRules
Use this command to read the routing rules for a Conversation user from the Martin cache.
Attribute: login.
The routing rules must be synchronized with the routing rules stored in XS cache.
Example:

      !"  #        71/73

Chapter 6  !    "' )( !!

spy> getXmlRules alegaulois

<rule active="true" type="PRESENTATION" id="41378"> <actionPart> <routeTo
type="PRESENTATION" forking="PARALLEL"> <dest dn="32101"/> </routeTo>
</actionPart> </rule>
<rule active="true" type="BUSY" id="BUSY_37807"> <actionPart> <routeTo
type="FORWARD" forking="PARALLEL"> <dest dynamicDN="voicemail"/> </routeTo>
</actionPart> </rule>
<rule active="true" type="NO_ANSWER" id="NO_ANSWER_37807"> <actionPart>
<routeTo type="FORWARD" forking="PARALLEL"> <dest dynamicDN="voicemail"/>
</routeTo> </actionPart> </rule>

6.8.2.9 getManagers
Use this command to list all manager / assistant links from the Martin cache.
This retrieves the login of the active backup assistant and the filtering mode.
The filtering mode is one of:
- NO_FILTER (F0N0)
- ASSISTANT_NOTIFICATION (F0N1)
- FORWARD_TO_ASSISTANT (F1N0)
- MANAGER_NOTIFICATION (F1N1)
spy> getManagers
atarac principalAssistant=sbhansali backupAssistant=null
mode=NO_FILTER
myuasa principalAssistant=ruthaug backupAssistant=null mode=NO_FILTER

6.8.3 tsa_maintenance
This tool is used to connect and get information from the OTS (Open Telephony Service
connected to OXE using CSTA) component in the OpenTouch. This component is used for
(OXE/Standard) users.
Login as root.
Example:

72/73       !"  #       

  !    "' )( !!

[root@tssf161 /]# /opt/Alcatel-Lucent/infra_services/ots/tsa_maintenance

Usage: [hostname]
Trying connect: tssf161.fr.alcatel-lucent.com 3595
Connection with tssf161.fr.alcatel-lucent.com , port 3595 is OK
You can give arguments -xxx-yyy in command-line, forwarded to main_tsa!
Local commands:
>>filenamenb_filessize_file to record in local files
writeset_client: nbe=
Press return
0 p|rparameter : put(ex: 0 p -v) or remove(ex:0 r -tcsta)
-1[1=I 2=I+timout] StartTracesMsg -2(ido|*,op|*) AddMask -3
StopTracesMsg
-4 Threads -5 Timer -6 MailBox -7 RecMsg
<time stamp>MenuMsgStdin
Menu Ots:
1 + 0|1|2|4|8|16 - Dump TRAD: 1=u 2=l 4=crid, 8=ll 16=2nd 31=all
2 [+ min max] ----- Dump LocalLines
3 [+ min max] ----- Dump LocalUsers
4 ---------------------- Dump AgAdm
...
57 [+ 1]---------------- Force loading Qmcdu from Pbx (0 to force): To
force load all number from OXE to
OpenTouch OTS
100 -------------------- MENU PROTECTED by secret code
200 -------------------- TRACE OPTIONS
300 -------------------- GLOBAL STATE: Shows the status of the OTS
connection with OXE
500 -------------------- TSAPI MENU
600 -------------------- T-SERVER MENU
-----------------------------------------------------------------------
Version: 5.201.32_0
Args : 3595 / -http_port:3695 / -PMS-monoproc:0 / -Squirrel / -DM
These numbers/commands can be run to execute the mentioned action (example option 300
shows the status of OTS connection with the OmniPCX Enterprise).
Menu 200 provides trace options (different modules traces must be enabled); you can activate
the traces as follows after executing command 200:
0 p –txxx (to set up a trace)
Traces can be removed using the following option:
0 r –txxx (to remove a trace)
Use the >> <fileName> option to write traces into a file.

6.8.4 clean_logs_and_restart_udas.sh
This tool is used to remove the UDAS logs available in the OpenTouch server and restart the
UDAS service.
Login as root.

6.8.5 dumpxs
This tool allows to dump configuration data for the extensible services component.
[root@myot165 toolexec]# dumpxs.sh
1)All 7)Miscs 13)RoutingRules(o)

      !"  #        73/73