Oracle® Communications Session Monitor

Installation Guide

Release 3.3.80

E57620-01

January 2015

Oracle Communications Session Monitor Installation Guide, Release 3.3.80

E57620-01

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Document Revision History

1 Overview of Session Monitor Installation

- Session Monitor System Architecture

- About Installing Session Monitor

- Session Monitor Hardware Requirements

- Types of Installation Media

2 Installing Session Monitor

- Installing Session Monitor

3 Configuring Session Monitor

- About the Platform Setup Application

- Platform Setup Application Initial Log In

- Changing Your Password

- Restarting or Powering Off Session Monitor

- Selecting the Machine Type

- Configuring Session Monitor

- Configuring the Network Settings

- Editing a Network Interface

- Adding a Network Interface

- Deleting a Network Interface

- Resetting the Network Interface Settings

- Mediation Engine Connection List

- Typical Connection Scenarios

- Configuring the SMTP Settings

- Setting Up the Mail Server

- Setting Up the Email Notifications

- Setting the System Date and Time

- Setting the System Time Using the Internet Time

- Setting the System Time Using your Local Network Time

- Setting the System Time Manually

- Configuring Data Retention

- Secure Configuration

- Server Certificate

- Trusted Certificates

- Installing the Products

4 Session Monitor Post-Installation Tasks

- Access to Session Monitor by Oracle Support

- Installing Software Update

- Media

- Filters

- Status

- Implementation

- Signaling

- Packet Deduplication

- Statistics Per Protocol

- Global statistics

- Caveat

- System Diagnostics

- Creating a Report

- Report Contents

- Filter Syntax

5 Installing Operations Monitor Probe

- Operations Monitor Probe System Requirements

- Hardware Requirements

- Software Requirements

- System Configuration

- Setting Up Huge Pages

- Making CPUs Exclusive

- Network Connectivity

- Installing and Configuring Operations Monitor Probe

- Adjusting Configurations in the RAT Configuration File for Your System

- RAPID Configuration Files

- Basic Configuration

- Configuring Encrypted Communication

- Setting the Configurations for Packet Inspector

- Common System Settings

- Adding a Kernel Command Line Option

- Persistent Loading of a Kernel Module

A Preparing Session Monitor Installation Media

- Preparing the Installation Media

- Preparing a USB Flash Drive Using UNetBootin

- Preparing a USB Flash Drive (alternative, Linux/Mac OS X)

- Creating a Bootable USB on Windows

Glossary

Preface

This guide provides instructions for installing Oracle Communications Session Monitor.

The Oracle Communications Session Monitor product family includes the following products:

- Operations Monitor

- Enterprise Operations Monitor

- Fraud Monitor

- Control Plane Monitor

Audience

This guide is intended for the person or team that installs and maintains the Session Monitor products.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Document Revision History

The following table lists the revision history for this document:

Version

Date

Description

E57620-01

January 2015

Initial release.

1 Overview of Session Monitor Installation

This chapter provides an overview of the Oracle Communications Session Monitor system architecture and the installation process.

Session Monitor System Architecture

The Session Monitor system works by capturing the traffic from your network, correlating it in real-time, and storing it in indexed formats so that they are available for the various reports offered by the web interface.

The Session Monitor system architecture has three layers:

- Probe layer: This layer is responsible for capturing the traffic from your network and performing the Media Quality analysis. The probes send meta-data for each of the signaling messages to the Mediation Engine layer and analyze the RTP streams locally, sending the results of this analysis to the Mediation Engine layer.

- Mediation Engine (ME) layer: This layer is responsible for understanding in real-time the traffic received, correlating it and storing it for future reference. This layer is also responsible for measuring, managing, and storing the KPIs. In the common case, there is one ME per geographical site. It is possible, however, to have the probes from multiple geographical sites sending the traffic to a single ME. It is also possible to have multiple ME installations in the same geographical site.

- Aggregation Engine (AE) layer: This layer is responsible for aggregating the global KPIs, on-demand correlation of calls passing multiple geographical sites, and for the global search features. In a typical setup, there is only one AE for the whole network.

Figure 1-1 shows the Session Monitor system architecture.

Figure 1-1 Session Monitor System Architecture

Each of the three layers supports high-availability by deploying two identical servers in active-passive or active-active modes of operation. For small setups, it is possible to run the probe layer and the ME layer on the same physical hardware. The AE layer always requires its own hardware.

From the Session Monitor products perspective, the Operations Monitor and the Control Plane Monitor (CPM) run on the Mediation Engine (ME) while the Mediation Engine Connector (MEC) and the Fraud Monitor products run on the Aggregation Engine (AE).

About Installing Session Monitor

The installation of Session Monitor includes these steps:

1. Reviewing the system requirements and selecting the hardware that is needed.

2. Using the Session Monitor Installer to do the software installation.

3. Using the Platform Setup Application for initial system configuration.

Session Monitor Hardware Requirements

For lab installations with little traffic, the following minimum requirements must be met to install any of the Session Monitor machine types:

- 2.6 GHz Intel Xeon processor, 64-bit with 8 processing threads

- 8 GB RAM

- 70 GB storage on a hardware RAID controller

- 2 Ethernet ports

Note:
For production use, Oracle recommends to complete a sizing exercise together with your Oracle sales engineer. Higher performance hardware may be required, for example, in cases with:

- High levels of monitored traffic

- High numbers of concurrent users

- High volumes of historical information

On the Mediation Engine machines, Oracle recommends using a RAID-10 array for the operating system and the database. A separate RAID-5 array is recommended for storing long-term data.

Session Monitor is supported on the following hardware:

Servers

- HP DL380p G8, Embedded Smart Array P420i Controller

- HP DL580 G7, Embedded Smart Array P410i Controller

Network Adapters

- HP NC364T PCIe Quad Port Gigabit Server Adapter

- HP NC375T PCIe Quad Port Gigabit Server Adapter

- HP Ethernet 1Gb 4-port 366FLR Adapter

Capture cards

- Napatech NT4E (4x 1Gbe ports)

- Napatech NT20E2 (2x 10Gbe ports)

Note:
Only one Napatech capture card per server is supported.

Types of Installation Media

Session Monitor may be installed using a DVD or USB flash drive. If you are going to use a USB flash drive, make sure that its size is at least 1GB. See "Preparing Session Monitor Installation Media" for instructions on how to prepare a USB flash drive.

Important:
When updating from a Palladion2.X installation, no data is carried over. If you want to keep the settings, create a configuration savepoint using the web interface and export it to a file. After completing the installation, you can upload the savepoint file and restore the settings.

Note:
Oracle recommends the following:

- Use brand drives, as issues have been reported when using low-quality thumb drives.

- If the hardware on which Session Monitor is installed supports iLO or another out-of-band management technology, Oracle recommends to configure it before starting the installation.

2 Installing Session Monitor

This chapter describes how to install Oracle Communications Session Monitor.

Installing Session Monitor

To install Session Monitor:

1. Insert the DVD or attach the USB flash drive and power on the system. Make sure that the machine boots from the installation media. This is usually done using a one-time boot option.

Note:
Booting from EFI without BIOS emulation is not supported.

If booting from the installation media succeeds, you should see the Session Monitor installer Boot Menu screen.

Figure 2-1 shows the Boot Menu screen.

Figure 2-1 Session Monitor Boot Menu Screen

Press ENTER on your keyboard to continue the installation. The installer is subsequently loaded which can take a few minutes.

The installer checks whether the hardware passes the minimum system requirements for Session Monitor. If the minimum system requirements are not met, installation does not continue. See "Session Monitor Hardware Requirements" or contact your Oracle sales engineer for more information about the system requirements.

2. Select the network adapter that is to be used for the management Web interface. A list of the supported network interfaces together with their hardware addresses (MAC) is shown.
Figure 2-2 shows the network adapter selection screen.

Choose the interface to use for accessing Session Monitor. Access via this interface is required to finish the installation. Refer to the documentation of the machine for further information about the location of network interfaces.

Figure 2-2 Network Adapter Selection

3. Select the IP configuration for the management network adapter. You can select to configure static IP settings manually or using DHCP.
Figure 2-3 shows the network adapter IP configuration selection screen.

Note:
No error checking is performed to validate the network configuration; verify your inputs before proceeding.

Figure 2-3 Network Adapter IP Configuration Selection

4. If you select static IP configuration, the installer prompts for the IP address, netmask, and the default gateway of your network.
Figure 2-4 shows the network adapter IP address specification screen.

Figure 2-4 Network Adapter IP Address Specification

5. Select the primary disk or disk array for the installation. The primary disk will hold the Session Monitor operating system and the database. In the second step you can choose to use another disk for long-term stored data or to keep all data on one disk.
Figure 2-5 shows the primary disk selection screen.

Figure 2-5 Primary Disk Selection

Note:
The primary disk can have a size between 70GB and 2TB. If you want to use a larger disk array for data storage, configure it as a secondary disk.

Important:
Configuring a machine with a secondary disk as a standalone Probe is not supported. Only Mediation Engine and Mediation Engine with embedded Probe machines can use a secondary disk.

6. The installer prepares the disks and sets up the system. This installation process usually takes about 10 minutes.
Figure 2-6 shows the installation screen.

Figure 2-6 Session Monitor Installation

7. The installer updates the firmware required for the hardware components on the machine. This process can take several minutes to complete. Do not power off the machine during this process, as this may leave components in an unusable state.
Figure 2-7 shows the firmware update screen.

Figure 2-7 Firmware Update

8. The installer reboots the system. When instructed, remove the USB flash drive or DVD used for the installation. Make sure that the machine boots from the primary hard disk that you selected in the previous steps.
Figure 2-8 shows the system reboot screen.

Figure 2-8 System Reboot

9. After rebooting, the machine shows the IP address that it uses. Open the URL https://ip-address/ in your Web browser to continue with the configuration of the Session Monitor system. You should see the login dialog to the Session Monitor Platform Setup Application (see "Configuring Session Monitor").

3 Configuring Session Monitor

This chapter describes how to configure Oracle Communications Session Monitor.

About the Platform Setup Application

The Platform Setup Application (PSA) guides you through the configuration steps to get the Session Monitor system running, including configuring the machine type, network settings, DNS settings, and SMTP settings.

The menu on the right shows your progress in the overall configuration.

The Machine Type page lets you choose the applications you want to install. In the License page you can upload a license file that also configures the applications.

The subsequent sections help you in configuring the machine for your network and time zone. These steps are optional and can be skipped by clicking on Continue.

You can review and change these settings at any time by visiting the Platform Setup Application at the https://ip-address/setup/ URL. This URL is valid for any Session Monitor server.

In the final step, the applications that are selected are installed. After the successful installation, you are taken to the applications.

Platform Setup Application Initial Log In

All Session Monitor interfaces can only be accessed through encrypted HTTPS connections. At initial login, your Web browser may not recognize the server and display the "This Connection is Untrusted" a warning message. Confirm the security exception to proceed.

Figure 3-1 shows the security exception confirmation screen.

Figure 3-1 Security Exception Confirmation

See "Secure Configuration" for information about how to protect connections to the system and avoid the untrusted certificate warning in the future.

The login page allows you to access the Platform Setup Application. Enter your user name and password into the indicated fields then click Sign in.

Figure 3-2 shows the Platform Setup Application Login page.

Figure 3-2 Platform Setup Application Login Page

If the user name or password entered are incorrect, a warning message appears below the login button and you'll have the opportunity to retry.

You can log into the Platform Setup Application using the default user name sysadmin and password oracle.

After you log in, you are prompted to review and accept the license of the software. You must agree to the license terms to continue.

Changing Your Password

To change your password, click your user name in the top right-hand corner of the screen and select Change Password from the drop-down menu.

Figure 3-3 shows the drop-down menu when you click your user name.

Figure 3-3 Change Password Menu Item

In the Change Password dialog box, enter the old and the new passwords in the indicated fields and click Change to complete the action.

Note:
The password can only contain digits, letters and white spaces.

Restarting or Powering Off Session Monitor

The restart and power off buttons are accessible through the power button on the top right-hand corner of the screen.

Figure 3-4 shows the drop-down menu when you click the power button.

Figure 3-4 Restarting or Powering Off Session Monitor

After selecting an option, you are prompted a final time to confirm that you wish to proceed.

Selecting the Machine Type

Figure 3-5 shows the Machine Type Settings page.

Figure 3-5 Machine Type Settings

The Machine Type Settings page allows you to select which products you want to install. This page only appears the first time you configure Session Monitor prior to the products installation.

Select your machine type by clicking Probe or Mediation Engine or Aggregation Engine button. This will enable the corresponding product selection.

Note:
You can select only one machine type per installation.

Next, select the check boxes next to the products that you want to install. Only checked items are included in the installation.

Note:
The products are machine type specific and cannot be interchanged between machine types.
Some machine types require certain product. For example, the probe machine type requires a probe product, and the Mediation Engine machine type requires the Operations Monitor product.

After selecting the products, click continue to proceed with the installation. Your machine type and product selections should appear in the status panel located on the right under the navigation menu.

Configuring Session Monitor

This step in the configuration process allows you to configure Session Monitor settings for this machine in accordance with the terms of your license.

Note:
If you do not have a valid Session Monitor license, contact Oracle.

Figure 3-6 shows the Configuration page.

Figure 3-6 Configuration Page

On the left side of the page you must enter the number of concurrent calls printed on your license. On the right side you must check the product extensions you have a license to use. All enterprise customers should automatically check Media quality.

Note:
The number of Concurrent RTP streams can cause performance and stability issues if it is set higher than the hardware and the network permits. Values above 20 are not recommended. Changes to the RTP recording setting take effect only after a restart of the system.

Click the continue button to navigate to the Network Settings page.

Configuring the Network Settings

The Network Settings page contains a list of configured network interfaces, with a toolbar for adding, deleting, and editing interfaces, as well as a restore button to reset the last applied settings (usually, you want to add interfaces you didn't add during the installation procedure).

There's also a check box below the network list that can be checked if you wish to apply network settings that won't allow you to reconnect to the Platform Setup Application again.

Figure 3-7 shows the Network Settings page.

Figure 3-7 Network Settings Page

Editing a Network Interface

To edit the settings of a network interface, select the entry in the list and click Edit in the toolbar (or double-click the entry).

Figure 3-8 shows the dialog box to edit the network interface.

Figure 3-8 Edit Network Interface

To change the IP method, select the radio button. If you select Static IP configuration, you will get additional options.

The following fields are compulsory for static IP configuration:

- IP Address

- Netmask

- Default Gateway

Static routes are optional; the left column contains the target IP/netmask in CIDR format and the right one the target IP.

Note:
You can save yourself filling out the netmask by typing in CIDR format in the IP address field, for example 192.168.0.1/24, and the netmask field will get 255.255.255.0 filled in automatically.

Link modes can be changed by clicking Link modes and the text Select.... This will open a pane with check boxes. There's usually no reason to touch this setting.

Monitoring can be enabled by checking the corresponding check box. This option is only available if your machine is a probe.

To save the network interface setting, click Save. The settings are not used until you click Apply/Continue.

To use and keep any changes you made in the Edit Interface dialog box, you have to click Apply/Continue in the lower-right corner. The settings are applied and the browser will try to connect to the machine. If the browser fails to connect to the machine within a given amount of time, the settings are reverted. This is to prevent locking yourself out. If you want to change the interface settings so that you won't be able to connect (for example, to deploy the server on another network), check the check box Skip connectivity check when applying new settings before clicking Apply/Continue.

If you are configuring Session Monitor for the first time you are guided to "Configuring the SMTP Settings".

Adding a Network Interface

To add a new network interface, its physical port has to be already configured on the machine. Press Add on the toolbar. Then select an interface from the drop-down menu. You can also create a VLAN interface by entering a VLAN ID in the VLAN port.

Figure 3-9 shows the dialog box to add an interface.

Figure 3-9 Add Network Interface

Deleting a Network Interface

To delete a network interface, select the interface in the list and click Delete on the toolbar.

Resetting the Network Interface Settings

To reset your network settings to the last state before you clicked Apply/Continue, click Reset in the toolbar.

Note:
Monitoring is only enabled for machines that are configured as probes. On other machines, the monitoring check box is grayed out.

Important:
Do not configure dummy interfaces with DHCP if there is no DHCP server to give an IP.
When applying settings with a dummy interface using the DHCP method wait for the DHCP client to time out (usually one minute).

Mediation Engine Connection List

For a Probe machine type, the Mediation Engine Connection List page allows you to configure which Mediation Engines the Operations Monitor Probe connects to.

Figure 3-10 shows the ME Connection List page.

The Operations Monitor Probe can connect to one or more Mediation Engines, using TLS encryption, or with some configurations, also cleartext. Likewise, a Mediation Engine can connect to more than one Operations Monitor Probe (as well as Session Border Controller Probes).

On the Mediation Engine, cleartext connections are usually on port 4741 and encrypted connections on port 4742. For encrypted connections, the Operations Monitor Probe and the Mediation Engine need to be able to verify the certificate of the other party. See "Secure Configuration" for more information.

Figure 3-10 ME Connection List Page

The Mediation Engine machines by default only accept encrypted connections (unless the Mediation Engine and Probe are on the same machine); for unencrypted connections the check box Accept insecure connections from remote probes on the Trusted Certificate page must be checked.

Figure 3-11 shows the Trusted Certificate page.

Figure 3-11 Trusted Certificate Page

Typical Connection Scenarios

Mediation Engine and Operations Monitor Probe Are on the Same Machine

For setups with a Mediation Engine machine with an embedded Probe, a cleartext connection is automatically added to the ME connection list. For cleartext connections, no certificates are exchanged.

One Mediation Engine and Two Operations Monitor Probes

For setups with one Mediation Engine and two Operations Monitor Probes, the self-signed server certificates of both Operations Monitor Probes are uploaded as trusted certificates on the Mediation Engine, and the self-signed server certificate of the Mediation Engine is uploaded on both Operations Monitor Probes as a trusted certificate. On each Operations Monitor Probe, the IP of the Mediation Engine is added to the ME connection list with TLS check box selected.

Table 3-1 describes the actions to configure the connections between one Mediation Engine and two Operations Monitor Probes.

Table 3-1 One Mediation Engine and Two Operations Monitor Probes

Machine

Action

Mediation Engine

- Download the Server Certificate

- Upload the Server Certificate of the Operations Monitor Probe1 to Trusted Certificate

- Upload the Server Certificate of the Operations Monitor Probe2 to Trusted Certificate

Operations Monitor Probe 1

- Download the Server Certificate

- Upload the Server Certificate of the Mediation Engine to Trusted Certificate

- Add IP of the Mediation Engine to the ME Connection List, with TLS connection.

Operations Monitor Probe 2

- Download Server Certificate

- Upload Server Certificate of the Mediation Engine to Trusted Certificate

- Add IP of Mediation Engine to ME Connection List, with TLS connection.

Two Mediation Engines and One Operations Monitor Probe

For setups with two Mediation Engines and one Operations Monitor Probe, the self-signed server certificate of the Operations Monitor Probe is uploaded as trusted certificate on both Mediation Engines, and the self-signed server certificates of the Mediation Engine are uploaded on the Operations Monitor Probe as a trusted certificate. On the Operations Monitor Probe, the IPs of the Mediation Engines are both added to the ME connection list with TLS check box selected.

Table 3-2 describes the actions to configure the connections between two Mediation Engines and one Operations Monitor Probe.

Table 3-2 Two Mediation Engine and One Operations Monitor Probe

Machine

Action

Mediation Engine 1

- Download the Server Certificate

- Upload the Server Certificate of the Operations Monitor Probe to Trusted Certificate

Mediation Engine 2

- Download the Server Certificate

- Upload the Server Certificate of the Operations Monitor Probe to Trusted Certificate

Operations Monitor Probe

- Download the Server Certificate

- Upload the Server Certificate of Mediation Engine 1 to Trusted Certificate

- Upload the Server Certificate of Mediation Engine 2 to Trusted Certificate

- Add IP of Mediation Engine 1 to ME Connection List, with TLS connection.

- Add IP of Mediation Engine 2 to ME Connection List, with TLS connection.

All Other Scenarios

For setups with more than two Operations Monitor Probes or Mediation Engines, Oracle recommends that you use PKI (Public Key Infrastructure) with root certificates as described in Session Monitor Security Guide.

Configuring the SMTP Settings

Figure 3-12 shows the SMTP Configuration page.

Figure 3-12 SMTP Configuration Page

Session Monitor can send notifications and alerts directly to users' email addresses. Which notification to send to which address is configured in the relevant products. However, you first need to configure the SMTP settings properly for this feature to be available.

Setting Up the Mail Server

To use the email notification feature, select Enable SMTP check box. The system will need an SMTP server to send emails. Contact your network administrator to find out the address of the server your organization uses. The default port is the standard port 25.

If the server requires a valid email account, you will need to create one for Session Monitor. Then, select Enable authentication check box and enter the credentials.

Setting Up the Email Notifications

You can choose how the emails from Session Monitor will look like in the users' mailboxes.The field Mail sender is the email address Session Monitor will use; users will see this address in the Sender: or From: field of the emails. You can optionally specify a Subject prefix; this will appear at the beginning of the subject of the emails and make it easy to identify Session Monitor's emails in users' inbox.

If you are configuring Session Monitor for the first time you will be guided to "Setting the System Date and Time".

Setting the System Date and Time

Figure 3-13 shows the Date and Time Settings page.

Figure 3-13 Date and Time Settings Page

In the Date and Time Settings page you can choose how the system will synchronize its time. Make sure that the correct method will be used, as it is important to have a correct and stable time:

- For correctness of the data recorded by Session Monitor

- To have automatic maintenance running during the night

- To have correct journals to diagnose potential problems

It is recommended to use automatic time synchronization by choosing the NTP method (default). This will set the time automatically and keep it synchronized with the global internet time.

Note:
In setups with multiple Session Monitor machines, make sure to use the exact same time source for all machines. Some features might not work as expected if the machines clocks differ from each other.

Setting the System Time Using the Internet Time

Session Monitor system needs a time server to synchronize with. Session Monitor is configured to use a public server pool by default (0.pool.ntp.org). This requires that the Session Monitor machine has access to the Internet. More specifically, make sure that the system is able to resolve network names with DNS (see Network Settings) and to communicate over the UDP port 123 through your internet gateway and firewall. You can specify up to three servers, in case one of them is unreachable or gives erroneous times.

Setting the System Time Using your Local Network Time

If your organization runs an NTP server (ask your network administrator about this), use that instead of a public one. To do so, select Set via NTP, and enter the network name or the IP address of this relay.

Setting the System Time Manually

If the system does not have access to any time server, you need to set the current time manually. It will then use the server's internal clock, but this will slowly drift away from the real time the rest of the world is on (for instance, 1 second more difference per day). Therefore, you should come back to the Date and Time Settings page and adjust it every week or so. To do so, get a reliable time yourself (such as a computer using network synchronization), select Set manually, and enter the correct date (YYYY-MM-DD) and time (HH:MM:SS).

Make sure to apply the settings by clicking Apply/Continue button, and wait for the synchronization to complete.

If you are configuring Session Monitor for the first time, you will be guided to "Installing the Products".

Configuring Data Retention

The Data Retention page is used for configuring data retention in database for different data sources. Some settings depend on the license settings and will be available only if the associated configuration is set.

Figure 3-14 shows the Data Retention page.

Figure 3-14 Data Retention Page

Data retention is configured in days per data type. A value of 0 disables time based data retention.

Note:
The settings only affect the maximal lifespan of the data. Data availability is limited by available storage capabilities.

Note:
Retention times does not affect the amount of storable data.

CPM Subscriber Data: Delete Diameter S6 transaction data. Enabled by the CPM module.

RTP Recording: Delete RTP Recordings. Enabled by RTP recording configuration.

Subscriber Data - Calls: Delete call meta data and signaling.

Note:
Saved calls are not deleted by this option. Saved calls must be deleted by operators. (Optional) Disable user permissions for saved call functionality.

Subscriber Data - Registration: Delete registration events.

Note:
CDR/MDRs are not supported. Data retention affects data in the database only. For deleting CDR/MDRs, use FTP to delete files after downloading.

Secure Configuration

To help protect users of Session Monitor and consumers' data, see the Session Monitor Security Guide for information on the security features of Session Monitor.

During the installation of a Session Monitor server, you will encounter the server certificate and trusted certificate pages.

Server Certificate

The Server Certificate page is used to see and change the certificate used by this server. This step is recommended to protect users' data.

For more information, see the discussion about encryption and certificates in the Session Monitor Security Guide.

Trusted Certificates

The Trusted Certificates page is used to configure the authentication of session border controllers (SBCs). This step is necessary before attempting to connect SBCs to Session Monitor.

For more information, see the discussion about connection with Oracle Session Border Controller in Session Monitor Security Guide.

Installing the Products

The Install page summarizes the components to install. Check that you selected the correct components; after the installation is complete, the selection of the components cannot be changed.

Figure 3-15 shows the Install page.

Figure 3-15 Install Page

Click Install to start with the installation. The Platform Setup Application initiates the installation process and reports back the progress. The installation process might take a few minutes to complete.

You can click on the Session Monitor button when the installation is complete. This will bring you to the installed products' interface.

4 Session Monitor Post-Installation Tasks

This chapter provides instructions for Oracle Communications Session Monitor post-installation tasks.

Access to Session Monitor by Oracle Support

To authorize Oracle Support access to your Session Monitor servers, you must provide direct shell access using Secure Shell (SSH). Shared desktop access is not direct shell access.

Oracle Support provides you the SSH credentials for authentication and authorization. You configure the credentials on the Remote Access page in Platform Setup Application (PSA). You can modify the credentials or disable shell access at anytime in PSA.

Oracle Support connects to your Session Monitor server using a VPN connection. Ensure that a VPN connection is created and tested, in the event that Oracle Support needs to use the VPN connection for an urgent issue.

Installing Software Update

After you log in to the product interface, you can see the status of the system or update the system. A system update will update all applications as well as the Platform Setup Application itself.

The Software Version page shows the currently installed components and the software version.

To install a software update, go to the Software Version page and select the update file (file type .bin) that was provided by Oracle or your service provider. Click Apply to initiate the upload.

When the upload has finished, the page will show the version number and issue the date of the update. Click Install to proceed with upgrading the system. You can also abort the upgrade by clicking Clear.

Important:
Session Monitor or parts of it may not be available during the update process.

Platform Setup Application will show the progress during the upgrade. You may click Close to hide the progress window.

Note:
If you have a setup with multiple servers (for example, one ME and multiple Probe servers), upgrade all of them at the same time. Running different servers of the Session Monitor at different versions is not supported.

Media

The Media page is only available after the installation process has finished and only for machines which have the probe type (that includes the machine type Mediation Engine with Probe).

Filters

Only traffic which doesn't match this will be passed on to the signaling protocols.

Check all traffic for signaling: When this check box is enabled, all the traffic (not only which doesn't match RTP filters) will be passed on to the signaling protocols. This may decrease performance.

BPF filter: This is used to identify the RTP traffic. Only the traffic matched by the given rule is considered.

For more information about filters, see "Filter Syntax".

Status

Active streams: The number of RTP streams found. Only traffic matching the (applied) filters are counted.

Packets processed: The packets matched by the filter and successfully processed.

Packets dropped: The packets matched by the filter but not processed due to insufficient resources.

Implementation

If the machine has a Napatech card installed, this card performs the filtering. Detection of this card is automatic and does not need to be configured.

Signaling

The Signaling menu is only enabled after the installation process has finished and only for machines which have the probe type.

The Signaling page is used to configure the characteristics of the types of traffic the various probes (which sniff traffic) look for. Only the traffic matched by the given rule will be considered.

Reasons to configure tight rules:

- All matching traffic will be processed by the probes. For most installations, the high volume of traffic makes inspecting every packet infeasible. Ignoring unnecessary packets, therefore, puts less stress on your system and makes subsequent analysis easier. For example, you may want to make sure the signaling probe, which monitors SIP, doesn't also get all the RTP traffic as well.

- You might not be interested in certain sources of traffic, even though the machine would pick it up.

- More complex VLAN configurations.

The default filters given should make sense and should at the very least be a sane starting point.

After applying the filters it takes a few seconds to reconfigure the probe(s). After that, the statistics on this page should count the new situation. Keeping an eye on the 'Packets processed' gives an idea of how the filters are performing.

For more information about filters, see "Filter Syntax".

Packet Deduplication

Turn on packet deduplication for the associated traffic type. A time value in milliseconds must be provided if deduplication is turned on. The value should be greater than 0.

Packet deduplication is done at L3 and above and it is best effort. Some types of traffic might not get de-duplicated (duplicates on nested VLANs, ipv6, and so on).

There is a System Setting to enable Deduplication in the core, which should be enabled if there are multiple Probes connected to one ME, and seeing the same traffic. If traffic is seen without and with vlan tags, it is recommend to also disable VLAN awareness (System Setting).

Statistics Per Protocol

Rate: This is the full amount of traffic this probe gets after the filtering.

Packets processed: This is the amount of packets in the last seconds. Only packets which match the filter can be processed.

Global statistics

Total sniffed: This is the amount of packets sniffed across all configured devices.

Total dropped: This is the amount of packets which should have been processed.Due to performance reasons they have been dropped by either the NICs or during processing. If possible, tighten the filters and disable the Check all traffic for signaling option (Signaling protocols) so the probe has less unnecessary work to do. If that's not possible, upgrade the machine.

Caveat

- Be sure to use vlan keywords in the filters when that's used on the network.

- Be sure to change the default filters if you use non-standard ports or other options.

- Traffic will first be filtered by the Media Protocols setting. Only traffic not matching there will be passed on to the signaling probes. Except if Check all traffic for signaling is enabled.

System Diagnostics

The System Diagnostics menu allows the creation of a report with information on the installation. This report may be requested by the support team in case of issues.

Creating a Report

A report can be created by clicking Create. This may take several minutes to complete. Afterwards, the report can be downloaded as a file by clicking Download. This file can then be sent to the support team, for example by email.

If a report exists, its creation date will be shown. It can be downloaded as often as necessary, but there can be only one report at a time; creating a new report will overwrite any existing one.

Reports are deleted around midnight UTC.

Report Contents

The contents of a report include:

- Information on the available hardware of the machine that the monitoring solution is running on

- Log files

- Configuration of the monitoring solution

- Statistics about the performance and status of components of the system and of the monitoring solution

- If the check box Include mysql dump... is checked, the report includes a dump of most of the database tables. Note that the respective tables might be huge.

- If the check box Include mysql dump... is not checked, the report will include only minimal information about the database tables.

Note:
Sensitive information is removed before report creation, including, but not limited to, passwords, keys, and certificates.

Filter Syntax

The filter syntax used is the same as tcpdump or libpcap. For an example, see http://wiki.wireshark.org/CaptureFilters.

The following filters are also known as BPF filters:

- (tcp port 5060)

- ((udp or tcp) and port 5060)

- (vlan (udp or tcp) and port 5060)

- (tcp portrange 5060-5070)

- (not port 5060)

- (host 10.10.0.5 and port 5060)

- (not host 10.10.0.5 and port 5060)

- (not ether dst 12:34:56:78:90:ab)

Entries with a vlan keyword must be included for networks using VLANs. It is harmless to include them on networks which don't use VLANs, but do make sure there is a separate identical filter without the vlan. For example, (tcp port 5060) or (vlan and tcp port 5060).

5 Installing Operations Monitor Probe

This chapter provides instructions for installing and configuring Session Monitor Operations Monitor probe.

Operations Monitor Probe System Requirements

The following sections describe the hardware and software requirements for Operations Monitor probe.

Hardware Requirements

Supported Servers

The following Sun servers are supported:

- Sun Server X4-2

- Sun Server X4-2L

Additionally, the following are minimum requirements:

- 2 processors, each with 8 cores

- 64 GB main memory

Supported Networking Cards

The following networking cards are supported:

- Sun Dual Port 10 GbE PCle 2.0 Networking Card with Intel 82599 10 GbE Controller

- Sun Quad Port GbE PCIe 2.0 Low Profile Adapter, UTP

- Sun Dual Port GbE PCIe 2.0 Low Profile Adapter, MMF

Software Requirements

Operating System

The Operations Monitor probe requires Oracle Linux 7 operating system. Ensure that you are running Oracle Linux 7 and that the packages are up to date. To update the packages, execute:

# yum update

Reboot the system if the packages have been updated since the last reboot.

Dependencies

Some of the needed libraries are not available in the Oracle Linux 7 repositories. However, the libraries are made available by the EPEL (Extra Packages for Enterprise Linux) Special Interest Group from the Fedora Project.

To add their repository to your system, execute:

# curl -f -O http://www.mirrorservice.org/sites/dl.fedoraproject.org/\
pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
# rpm -ivh epel-release-7-5.noarch.rpm

In addition to this, it will be necessary to install the package vrb.

Required Kernel Modules

Operations Monitor probe needs direct access to the Intel network interfaces. You need to unload the normal network driver for selected ports and associate them with a different driver that allows direct access. There are two options to accomplish this.

The Linux kernel as of version 3.6 provides a module named vfio-pci which fits the needs of DPDK. However, this solution has some limitations. The alternative solution is the igb_uio driver provided by Intel. It is more versatile than the native solution but requires extra steps to set up.

Using the igb_uio Kernel Module

Verify that the igb_uio loadable kernel module is installed on your system. The following command either displays information about the installed module or informs about the absence of the module:

# modinfo igb_uio

If the module is not installed on your system, follow these steps to install the module:

1. Download the Intel Data Plane Development Kit from http://dpdk.org.

# curl -f -O http://dpdk.org/browse/dpdk/snapshot/dpdk-1.7.0.tar.gz

Make sure to download version 1.7.0.

2. Install the development tools on the machine.

# yum group install Development tools

3. Install the kernel development files.

# yum install kernel-uek-devel

4. Navigate to the download location of the DPDK and unpack the files.

# tar xzf dpdk-1.7.0.tar.gz

5. Change to the folder where the DPDK files are extracted.

# cd dpdk-1.7.0

6. Configure and build the module.

# make config T=x86_64-native-linuxapp-gcc && make

7. Install the igb_uio loadable kernel module:

# install build/kmod/igb_uio.ko /lib/modules/&rsquor;uname -r&rsquor;/extra
# depmod -a

8. Load the kernel modules uio and igb_uio to be persistent (see "Persistent Loading of a Kernel Module".)

Using the vfio-pci Kernel Module

Verify that you are running the Red Hat compatible kernel and that it is used as the default kernel when booting using the following command:

# grub2-editenv list

The command should return:

saved_entry=Oracle Linux Server, with Linux 3.10...

If you are not running a Red Hat compatible kernel, do the following:

1. Obtain the list of kernels currently configured on your system using the following command:

# grep "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2

2. Select the line that starts with:

Oracle Linux Server, with Linux 3.10

3. Set the new default using the following command:

# grub2-set-default "line picked in previous step"

4. Add the kernel command line option (see "Adding a Kernel Command Line Option").

intel_iommu=on

5. Set the kernel module to be loaded when the system boots (see "Persistent Loading of a Kernel Module").

vfio-pci

System Configuration

The following sections describe the system configurations.

Setting Up Huge Pages

The Operations Monitor probe needs huge pages provided by the Linux kernel. Each port or each configured sniffer (see "Section sniffer/name") needs at least 1GB of huge pages. Furthermore, a Operations Monitor probe requires a huge page size of 1GB.

For example, to set up 8GB of huge pages each of 1GB size, add the following options to your kernel command line options (see "Adding a Kernel Command Line Option"):

default_hugepagesz=1G hugepagesz=1G hugepages=8

To configure a different amount of memory:

1. Replace the 8 with the desired number of huge pages.

default_hugepagesz=1G hugepagesz=1G hugepages=8

2. Create the following directory:

# mkdir -p /mnt/huge

3. Edit /etc/fstab and add the following line:

hugetlbfs  /mnt/huge  hugetlbfs  defaults,pagesize=1G  0  0

4. Reboot the system for the changes to apply.

Making CPUs Exclusive

This step is optional but leads to a better performance of the Operations Monitor probe.

To hide the CPUs used by Operations Monitor probe from the Linux scheduler, add the following Kernel command line option (see "Adding a Kernel Command Line Option"):

isolcpus=a,b,c,d...

where a,b,c,d.. are selected CPU IDs provided by the /usr/share/pld/rat/system_layout.py utility.

Note:
Do not add CPU IDs 0 and 1.

Network Connectivity

Ensure that the Operations Monitor Probe can establish a TCP connection on port 4741 or 4742 (depending on the configuration described later) of the Mediation Engine.

Additionally, the daemons rat and rapid use some ports on localhost for internal communication; therefore, it is necessary to ensure that no other services use these same ports. The port numbers used by these daemons can be obtained from their configuration files.

Installing and Configuring Operations Monitor Probe

Download the Operations Monitor probe rpm package from http://pirate.de.oracle.com/storage/tmp/palladion-9.9.9-1.x86_64.rpm. The package and its dependencies can be installed using the following command:

# yum palladion-9.9.9-1.x86_64.rpm

Adjusting Configurations in the RAT Configuration File for Your System

The default RAT configuration file is in the directory /etc/iptego/rat.conf.

You may need to adjust some of the configurations to fit your system configuration. The configuration file is divided into several sections, each containing options and possible references to other sections of the file, so be careful and make sure you write a valid configuration. A section is denoted by brackets and contains one or several assignment statements.

After adjusting the configurations you can enable the daemon using the following commands:

# systemctl enable pld-rat
# systemctl start pld-rat

Section dpdk

The dpdk section is denoted by:

[dpdk]

Table 5-1 lists and describes the entries in the dpdk section.

Table 5-1 Entries in the dpdk Section

Entry

Description

mem_channels = N

Sets the number, N, of memory channels of your system.

mem_layout = X, Y

Sets the memory allocated using huge pages per memory channel. This must be a colon separated list with one entry per specified memory channel. An entry must be a multiple of 1024 including 0.

rat_cpu_id = I

Sets the CPU ID, I, to which the main thread will be pinned. CPU IDs start at 0. Use the /usr/share/pld/rat/system_layout.py utility to get an overview of the available CPUs.

The selected CPU ID should not be 0 or 1.

driver = kernel_module_name

Sets the kernel module to use. This can be either vfio-pci or igb_uio. See "Required Kernel Modules" for further information.

Ensure that the specified amount of huge pages is available on your system. The Linux kernel distributes huge pages equally across memory channels. For example, the following configuration would be valid if you set up 8 huge pages of size 1024MB on a system with 2 memory channels:

[dpdk]
mem_channels = 2
mem_layout = 2048,2048
rat_cpu_id = 3
driver = vfio-pci

However, the following would be invalid, since the 8 huge pages are distributed between two channels:

mem_channels = 2048,6144

Section sniffer/name

The sniffer section specifies a sniffer and a name for this sniffer. You can later use this name to refer to this sniffer.

The section is denoted by:

[sniffer/name]

For example, if port1 is the sniffer name, the section would be denoted by:

[sniffer/port1]

Table 5-2 lists and describes the entries in a sniffer section.

Table 5-2 Entries in the sniffer Section

Entry

Description

type = dpdk

Specifies to use the Intel DPDK to access the networking cards. This entry must be set to dpdk.

port_masks = X+Y

Specifies the ports that are used by the sniffer. It can either be a single PCI ID or multiple PCI IDs combined by using a + sign. A valid PIC ID consists of 5 (lower case) hexadecimal digits with the following layout:

AA:BB.C

Use the /usr/share/pld/rat/system_layout.py utility for an overview of the available cards and their PCI IDs. For example, to listen only on the port with the PCI ID 88:00.0, set the entry as follows:

port_masks = 88:00.0

To listen on ports 88:00.0, 88:00.1 and a0:00.2 using only one sniffer, set the entry as follows:

port_masks = 88:00.0+88:00.1+a0:00.2

Note: Do not put white spaces between a port and the + sign and always use lower case characters for hex numbers.

disable_rtp = 0

Specifies whether media traffic should be analyzed. Setting this to 1 disables media traffic analyzing.

all_traffic_signaling = 0

Setting this to 1 passes all traffic to the signaling analyzer, regardless if it is categorized as media traffic.

Note: Enabling this entry may result in a notable decrease of performance.

rtp_filter = pcap filter expression

Specifies a filtering rule to categorize packets as media traffic. Only packets for which the filter applies will be passed to the media analyzer, except when all_traffic_signaling is enabled.

buf_size = M

Sets the buffer size for the sniffer. This number should be a power of 2 - 1. Ensure that the combined amount of buffers do not conflict with the configured memory layout. The amount of huge pages memory a sniffer requires depends on this buffer size. The exact amount a sniffer requires with a buffer size of M equals 2240 x M / 2^20.

workers = N

Sets the number of media traffic worker threads to create for this sniffer.

worker_cpus = X Y Z

Specifies the CPU IDs X,Y,Z to use for the media traffic threads. Assign a list of the length according to the configured number of threads.

filter_cpus = X

Sets the CPU ID, X, for the signaling analyzer thread.

cpu_affinity = X

Sets the CPU ID, X, for the main thread of this sniffer.

Note: Ensure that you select CPU IDs that belong to the same NUMA node that the configured port belongs to. Assign each CPU ID only once for best performance. Hyperthread cores can be used, but keep in mind that you are using hyperthreading and not real cores in that case. You must not configure ports on different NUMA nodes in a single sniffer.

Section signaling/name

There are multiple signaling sections, one for each supported protocol plus some additional. Following is a list of the valid signaling sections:

[signaling/sip]
[signaling/rudp]
[signaling/diameter]
[signaling/megaco]
[signaling/mgcp]
[signaling/enum]
[signaling/pinted]

Table 5-3 lists the entries in a signaling section.

Table 5-3 Entries in the signaling Sections

Entry

Description

filter = pcap_filter_expression

Specifies a filtering rule that a packet has to fulfill to be categorized into the protocol type of this signaling section.

deduplication_timelimit = X

Specifies the maximal delta in which a duplication packet can be recognized.

Note: Setting this to a value larger than 0 may decrease the performance.

Section base

In the base section, you specify which sniffers you want to activate and which signaling types you want to analyze.

[base]
sniffer = <name1> <name2> ...
signaling = sip ...

For example, if you configured a sniffer section for a sniffer named port1 and you want to activate the sniffer, then the list of sniffer would contain port1 as follows:

[base]
sniffer = ... port1 ...

Valid elements of the signaling list are:

sip rudp diameter megaco mgcp enum pinted

They are valid only if the according signaling/name section has been configured correctly.

RAPID Configuration Files

The communication between this probe and the Mediation Engines is handled by the service pldrapid. After the service is configured, you must enable it using:

# systemctl enable pld-rapid
# systemctl start pld-rapid

Basic Configuration

Rapid's configuration file is /etc/iptego/rapid.conf. It may not be necessary to edit this file; however, you need to configure the list of Mediation Engines in the file /etc/iptego/psa/probe_me.conf, which is included in /etc/iptego/rapid.conf file.

The following example shows the configuration for a list of Mediation Engines:

[MEList]
names = me1

[MEList/me1]
ip = aaa.bbb.ccc.ddd
name = ME
tls = no
port = 4741

where aaa.bbb.ccc.ddd is the IP address of the Mediation Engine. The value of the name field is arbitrary.

In the above example configuration, the Probe connects using an unencrypted connection to the Mediation Engine. Unencrypted connections must be enabled on the Mediation Engine. For an encrypted connection, the tls field must be set to yes and the port must be set to 4742. For encrypted connections, additional configuration is necessary (see "Configuring Encrypted Communication").

If connections to more Mediation Engines are desired then further sections, say MEList/me2 and MEList/me3, have to be added for those, and they have to be referenced in the names field of the MEList section as in the following example:

To configure connections to additional Mediation Engines (for example, me2 and me3), add the Mediation Engines to the names field in the MEList section and add the corresponding MEList/me2 and MEList/me3 sections.

[MEList]
names = me1 me2 me3

For proper operation, a valid /etc/iptego/psa/probe_uuid.conf file is also necessary. This file is created during packet installation. Otherwise, the write_rapid_uuid.sh script can be used to perform this task.

Configuring Encrypted Communication

If encrypted (TLS) communication with one or several Mediation Engines is enabled, then you must set up appropriate certificates.

For encrypted connections, it is required that the Probe authenticate the Mediation Engine and vice versa. Therefore, both the Probe and the Mediation Engine needs a signed (possibly self-signed) certificate and corresponding secret key, as well as the certificate of the Certification Authority (CA) that signed the peer's certificate. A machine which uses a certificate signed by a CA needs the CA's certificate to build its own certificate chain.

All of the needed certificates are stored in an Oracle Wallet. The wallet must reside in a disk file whose standard location (configured in rapid.conf ) is /etc/iptego/wallet. Several tools are available from Oracle that allow the creation and manipulation of wallets. Since a wallet is a directory that contains only the file ewallet.p12 in PKCS #12 format, it is also possible to create and maintain the wallet using third-party tools.

If a password is necessary to open the wallet, then that password must be stored in a separate file whose standard location (configured in rapid.conf) is /etc/iptego/apid.key (sic!). This is a text file containing only the password.

Setting the Configurations for Packet Inspector

If you want to enable the packet inspector, you can use the systemd command:

# systemd enable pld-pinted
# systemd start pld-pinted

Note:
Running packet inspector has a massive impact on performance.

The configuration file of packet inspector is in the directory:

# /etc/iptego/pinted.conf

It contains the section storage denoted by:

[storage]

Table 5-4 lists the entries in the storage section.

Table 5-4 Entries in the storage Section

Entry

Description

limit_mb = 2048

Specifies the amount of space used to save packets.

You can change this setting to adjust the amount of space used to save packets.

storage_path = path

Specifies the location where packet inspector saves the traffic to.

Common System Settings

The following sections describe common system settings.

Adding a Kernel Command Line Option

To add a kernel command line option, follow these steps:

1. Open the file /etc/default/grub in an editor (for example, vi).

2. Locate the line that begins with:

GRUM_CMDLINE_LINUX

If the line does not exist, append it to the file.

3. Append the command line option to the end of the line inside the double quotes. For example:

GRUB_CMDLINE_LINUX="... ... option_a"

where option_a is the command line option you want to add.

4. Save the file and close your editor.

5. Generate the new grub configuration file using the following command:

# grub2-mkconfig -o /boot/grub2/grub.cfg

The new kernel command line option will be used the next time the system boots.

Persistent Loading of a Kernel Module

To load a loadable kernel module on boot, follow these steps:

1. Create a start up script with the following name.

/etc/sysconfig/module/module_name.modules

where module_name is the name of your module.

2. Add the following to the script's content.

#!/bin/sh
exec /sbin/modprobe module_name

3. Make the script executable.

# chmod +x /etc/sysconfig/modules/module_name.modules

A Preparing Session Monitor Installation Media

This chapter provides instructions for creating the Oracle Communications Session Monitor installation media.

Preparing the Installation Media

Session Monitor may be installed using a DVD or USB flash drive. If you are going to use a USB flash drive, make sure that its size is at least 1GB. Oracle recommends using brand drives, as issues have been reported when using low-quality thumb drives.

Download the Session Monitor Installer ISO image from the repository indicated to you by Oracle or your service provider. If you want to use the DVD installation method, create a new DVD from the image. Otherwise follow the instructions below to create a bootable USB flash drive.

Caution:
Following the instructions writes the image directly to the device, which can be very dangerous when done without care, if you give the wrong device name, for example, the one representing your internal hard drive instead of the one representing the USB flash drive, all data from the running system can be deleted.

Preparing a USB Flash Drive Using UNetBootin

Note:
Using UNetBootin is the recommended way to prepare a USB flash drive for the installation. For Linux and Mac OS X, if this approach fails, an alternative preparation method is described in "Preparing a USB Flash Drive (alternative, Linux/Mac OS X)".

1. Download the UNetBootin tool matching your operating system from:
http://unetbootin.sourceforge.net/

This site also contains more information on using and troubleshooting the tool.

2. Plug the USB flash drive into the computer.

3. Start UNetBootin. Select Diskimage and ISO as the source. Click ... next to the empty text entry and select the Session Monitor ISO image.

4. Select the type USB Drive and the USB flash drive you just plugged in.

5. Double check the selections you have made. If they are all correct, click OK to start the writing process. UNetBootin informs you about the progress.

Figure A-1 shows the UNetbootin dialog box.

Figure A-1 Using UNetBootin to Prepare a USB Flash Drive for the Installation

Preparing a USB Flash Drive (alternative, Linux/Mac OS X)

Important:
The method described below only applies to Linux and Mac OS X and should only be used if the preferred method using UNetBootin does not work.

1. Plug the USB flash drive into the computer.

2. Find out which device name has been given to the USB flash drive:
Linux Execute lsblk on the command line. A tree of devices with their names, sizes and other information is shown. If lsblk is not available on your system, you can use dmesg.

Example output:

scsi 8:0:0:0: Direct-Access USB Flash Disk PMAP PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: [sdb] 7827456 512-byte hardware sectors (4008 MB)
sd 8:0:0:0: [sdb] Write Protect is off
sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1

In this example, sdb is the device name to use. A tree of devices with their names, sizes and other information is shown.

Mac OS X Execute diskutil list on the command line. A list of devices with their names, sizes and other information is shown.

3. Unmount the partitions of the USB flash drive in case any have been mounted automatically.
On Linux, execute:

umount USB device name

For example:

umount /dev/sdb1

On Mac OS X, execute:

diskutil unmountdisk USB device name

For example:

diskutil unmountdisk /dev/disk1

4. Write the image to the USB flash drive:
dd if=/path/to/palladion-x.x.x-xxx.iso of=USB device name bs=1m

where /path/to/palladion-x.x.x-xxx.iso is the path to the image file.

Important:
All data from the USB flash drive will be deleted.

5. Synchronize the disk caches and wait until disk activity stops to assure that all data has been completely written to the USB flash drive:
On Linux, execute sync on the command line

On Mac OS X, execute:

diskutil eject USB device name

For example:

diskutil eject /dev/disk1

Creating a Bootable USB on Windows

- If running Windows 7, use the Windows7 USB/DVD Download Tool.

1. Download the Windows 7 USB/DVD Download Tool from:
http://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool

2. In the Setup Wizard, click Next> Install.

3. After installing, click Finish and open the program.

4. Click Browse and locate the ISO file.

5. Click USB device.

6. Locate your USB device and click Begin copying.

7. If prompted, click Erase USB Device and then Yes.

- If running Windows XP, use UNetbootin.

1. Download UNetbootin from:
http://unetbootin.sourceforge.net/

2. Open the downloaded file and click Run.

3. When the program opens, click the Diskimage radio button and set to ISO.

4. Click . . . and locate the ISO file.

5. Set the Type to USB Drive, and set the Drive to the drive where the USB is mounted.

6. Click OK.

Glossary

Napatech card

A specialized network card which does part of the packet filtering and processing in dedicated hardware, as opposed to doing filtering and processing on the CPU.

Probe

A machine which filters and processes network traffic. It doesn't calculate the statistics.

RTP

The voice part of the network traffic, as opposed to the signaling (meta) part.

VLAN

VLAN (Virtual Local Area Network) is a technique to separate a network into distinct, isolated broadcast domains. See

https://en.wikipedia.org/wiki/Virtual_LAN

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.