PK
XJoa, mimetypeapplication/epub+zipPK XJ META-INF/container.xml
This appendix provides instructions for creating the Oracle Communications Session Monitor 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. |
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)". |
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.
Plug the USB flash drive into the computer.
Start UNetBootin. Select Diskimage and ISO as the source. Click ... next to the empty text entry and select the Session Monitor ISO image.
Select the type USB Drive and the USB flash drive you just plugged in.
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.
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. |
Plug the USB flash drive into the computer.
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.
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
Write the image to the USB flash drive:
dd if=/path/to/ocsm-3.3.90.0.0.iso of=USB device name bs=1m
where /path/to/ocsm-3.3.90.0.0.iso is the path to the image file.
Important: All data from the USB flash drive will be deleted. |
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
If running Windows 7, use the Windows7 USB/DVD Download Tool.
Download the Windows 7 USB/DVD Download Tool from:
http://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool
In the Setup Wizard, click Next> Install.
After installing, click Finish and open the program.
Click Browse and locate the ISO file.
Click USB device.
Locate your USB device and click Begin copying.
If prompted, click Erase USB Device and then Yes.
If running Windows XP, use UNetbootin.
Download UNetbootin from:
Open the downloaded file and click Run.
When the program opens, click Diskimage and set to ISO.
Click . . . and locate the ISO file.
Set the Type to USB Drive, and set the Drive to the drive where the USB is mounted.
Click OK.
This chapter provides an overview of the Oracle Communications Session Monitor system architecture and the installation process.
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.
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).
The installation of Session Monitor includes these steps:
Reviewing the system requirements and selecting the hardware that is needed.
Using the Session Monitor Installer to do the software installation.
Using the Platform Setup Application for initial system configuration.
The following sections describe the system requirements for installing Session Monitor.
Table 1-1 lists the supported client browsers:
Session Monitor is supported on Sun and HP systems.
Table 1-2 lists the hardware supported for Sun systems.
Table 1-2 Supported Hardware for Sun systems
Component | Requirement |
---|---|
Server |
The following severs are supported:
|
Network Adapter |
The following network adapters are supported:
|
Table 1-3 lists the hardware supported for HP systems.
Table 1-3 Supported Hardware for HP Systems
Component | Requirement |
---|---|
Server |
The following servers are supported:
|
Network Adapter |
The following network adapter s are supported:
|
Capture Cards |
The following capture cards are supported:
Note: Only one Napatech capture card per server is supported. |
Table 1-4 lists supported Session Border Controller (SBC) versions.
For development or demonstrations systems with little network traffic, Table 1-5 lists the minimum requirements to install any of the Session Monitor machine types.
For production systems, 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.
This section describes the software and hardware requirements for Session Monitor virtualization.
Hypervisor Support
The following hypervisors are supported:
Oracle VM version 3.2.7
VMware vSphere ESXi 5.1
Virtual Machine Requirements
Table 1-6 lists the minimum requirements for the virtual machines.
Table 1-6 Hardware Requirements for Virtual Machines
Component | Requirement |
---|---|
Processor |
8 vCPUs |
Memory |
8GB RAM |
Disk Space |
80GB |
NIC Card |
1Gbps vNIC |
In virtualized Mediation Engines, 50,000 concurrent calls (1 SIP leg per call) have been tested successfully.
Host Machine Requirements
The physical machine that hosts the virtual machines should contain at a minimum the hardware resources that are required to host all the virtual machines, in addition to the hardware that is required for the hypervisor.
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:
|
This chapter describes how to install Oracle Communications Session Monitor.
To install Session Monitor:
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.
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 System Requirements" or contact your Oracle sales engineer for more information about the system requirements.
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.
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. |
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.
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.
Caution: Session Monitor installer erases any existing files on the disk to prepare the disk with the operating system. Make sure to back up any important files on the disk before proceeding with the installation. |
Figure 2-5 shows the primary disk selection screen.
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. |
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.
The installer updates the firmware required for the hardware components on the machine. This process can take several minutes to complete.
Note: 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.
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.
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").