CA Unified Communications Monitor Installation Guide

CA Unified Communications Monitor Installation Guide
CA Unified Communications
Monitor
Installation Guide
Version 3.5
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■
Online and telephone contact information for technical assistance and customer
services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you
can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.
Contents
Chapter 1: Introduction
7
Chapter 2: System Requirements
9
Supported Operating System ....................................................................................................................................... 9
Supported Web Browsers .......................................................................................................................................... 10
Hardware Requirements for a Distributed System .................................................................................................... 10
Hardware Requirements for a Standalone System .................................................................................................... 11
Virtual Machine Requirements .................................................................................................................................. 12
Port and Protocol Requirements ................................................................................................................................ 12
Chapter 3: Configuring the Hardware
15
Configure the Server for the Management Console .................................................................................................. 15
Configure the Server for the Collector ....................................................................................................................... 16
Configure the Server for a Standalone System .......................................................................................................... 16
Configure Network Interface Cards ............................................................................................................................ 17
Chapter 4: Installing the Software
19
Installation Prerequisites ........................................................................................................................................... 19
Install the Management Console ............................................................................................................................... 20
Install the Collector .................................................................................................................................................... 21
Install All Components on One Server........................................................................................................................ 22
Chapter 5: Post-Installation Tasks
23
Install Updates............................................................................................................................................................ 23
Change the Host Name .............................................................................................................................................. 23
Update the List of Trusted Internet Sites ................................................................................................................... 23
Synchronize the System Time .................................................................................................................................... 24
Perform Configuration Tasks from the Management Console .................................................................................. 24
Chapter 6: Preparing Your Monitoring Environment
27
Preparing an Avaya Communication Manager Environment ..................................................................................... 27
Preparing a Cisco Unified Communications Manager Environment .......................................................................... 28
Preparing a Microsoft Lync Environment ................................................................................................................... 29
Preparing Acme Packet Session Border Controllers ................................................................................................... 29
Contents 5
Preparing Cisco Unified Border Elements .................................................................................................................. 31
Example of UC Monitor in a Multi-Vendor Environment ........................................................................................... 31
Index
6 Installation Guide
33
Chapter 1: Introduction
The following diagram illustrates the process of installing and configuring the hardware
and software for CA Unified Communications Monitor (UC Monitor):
Chapter 1: Introduction 7
Supported Operating System
More information:
System Requirements (see page 9)
Configuring the Hardware (see page 15)
Installing the Software (see page 19)
Post-Installation Tasks (see page 23)
Preparing Your Monitoring Environment (see page 27)
8 Installation Guide
Chapter 2: System Requirements
This section contains the following topics:
Supported Operating System (see page 9)
Supported Web Browsers (see page 10)
Hardware Requirements for a Distributed System (see page 10)
Hardware Requirements for a Standalone System (see page 11)
Virtual Machine Requirements (see page 12)
Port and Protocol Requirements (see page 12)
Supported Operating System
All servers that host UC Monitor components have the following operating system
requirements.
Management console in a distributed system, or the server in a standalone system
Microsoft Windows Server 2008 R2, Standard or Enterprise Edition
■
■
Install the Application Server role with the following role services:
–
Web Server (IIS) Support, with IIS 6 Management Compatibility
–
COM+ Network Access
Install and enable the following items:
–
.NET Framework 3.5.1 Features
Note: The UC Monitor installation process searches for .NET Framework
3.5.1 features and installs them if they are not present.
–
SNMP
–
The most recent service pack and important updates
Standard collector or small-site collector in a distributed system
Microsoft Windows Server 2008 R2, Standard or Enterprise Edition, with the
following items installed and enabled:
■
.NET Framework 3.5.1 Features
Note: The UC Monitor installation process searches for .NET Framework 3.5.1
features and installs them if they are not present.
■
SNMP
■
The most recent service pack and important updates
Chapter 2: System Requirements 9
Supported Web Browsers
Supported Web Browsers
Access to the management console is supported for the following browsers:
■
Microsoft Internet Explorer 7 and 8
■
Mozilla Firefox 9.x and later
■
Google Chrome
Other browsers or versions may work but have not been tested with UC Monitor.
Hardware Requirements for a Distributed System
In a distributed system, the collectors and the management console are installed on
separate servers.
Management Console
The management console server contains the MySQL database and supports
approximately ten standard collectors or 30 small-site collectors. CA has tested UC
Monitor on servers with the following specifications. CA supports the management
console on servers from any vendor, when the servers conform to these
specifications, at minimum:
■
Two Intel E5520 Xeon quad-core 2.66 GHz, 1333 MHz FSB processors
■
24 GB of RAM
■
Six 146-GB SAS hard drives in RAID 5 configuration
■
300 GB of space on the installation drive (to accommodate database growth)
■
Intel Copper GB or Intel Fiber GB network interface card
■
PCI Express x16 slot expansion card
■
Two 10/100/1000 Mbps Ethernet RJ-45 ports
■
Intel 82576 Gigabit Ethernet Controller
Standard Collector
CA has tested UC Monitor on servers with the following specifications. CA supports
the collector on servers from any vendor, when the servers conform to these
specifications, at minimum:
10 Installation Guide
■
Intel E5520 Xeon quad-core 2.66 GHz, 1333 MHz FSB processor
■
3 GB of RAM
■
Three 146-GB SAS hard drives in RAID 5 configuration
■
300 GB of space on the installation drive (to accommodate database growth)
Hardware Requirements for a Standalone System
■
Intel Copper GB or Intel Fiber GB network interface card
■
PCI Express x16 slot expansion card
■
Two 10/100/1000 Mbps Ethernet RJ-45 ports
■
Intel 82576 Gigabit Ethernet Controller
Small-site Collector
A distributed small-site system is available for deployments with multiple sites of
1,000 phones or fewer. CA supports the small-site collector on servers from any
vendor, when the servers conform to the following specifications, at minimum:
■
Intel Celeron E1500 2.2 GHz, 800 MHz FSB processor
■
2 GB of RAM
■
SATA II 3.5-inch hard drive
■
Intel Copper GB or Intel Fiber GB network interface card
■
10/100/1000 Mbps Ethernet RJ-45 port
■
Two Intel single-port 82576 PCI-E Gigabit Ethernet Controllers
Hardware Requirements for a Standalone System
A standalone system consists of one server on which the management console and
collector are installed. CA supports UC Monitor components on servers from any
vendor, when the servers conform to the following specifications, at minimum:
■
Two Intel E5520 Xeon quad-core 2.66 GHz, 1333 MHz FSB processors
■
24 GB of RAM
■
Six 146-GB SAS hard drives in RAID 5 configuration
■
300 GB of space on the installation drive (to accommodate database growth)
■
Intel Copper GB or Intel Fiber GB network interface card
■
PCI Express x16 slot expansion card
■
Two 10/100/1000 Mbps Ethernet RJ-45 ports
■
Intel 82576 Gigabit Ethernet Controller
Chapter 2: System Requirements 11
Virtual Machine Requirements
Virtual Machine Requirements
UC Monitor is supported in virtual environments.
■
You can install UC Monitor components on virtual machines that meet or exceed
the hardware requirements.
■
To achieve equal performance in an environment that stresses a physical server,
more memory is required on a virtual machine than on a physical server. Physical
servers outperform virtual machines in the area of disk I/O. UC Monitor tasks the
disk I/O heavily. You can expect less-than-equal performance on a virtual machine.
■
In a Cisco environment, send SPAN traffic to the monitor NIC. For more information,
see the following topics:
■
–
Configure Network Interface Cards (see page 17)
–
Preparing a Cisco Environment (see page 28)
To install the UC Monitor software on a virtual machine, follow the instructions in
Installing the Software (see page 19).
More information:
Hardware Requirements for a Distributed System (see page 10)
Hardware Requirements for a Standalone System (see page 11)
Port and Protocol Requirements
UC Monitor uses several ports and protocols to enable communications among the
management console, collectors, and monitored systems. Use the following information
to ensure that communications can pass active firewalls in your network.
TCP port 21
Open this port to allow the CA UCM Data Transformer service to receive data via
FTP for transformation into a format that UC Monitor can process.
TCP port 1000
Open this port for communication from the management console to the collectors.
The management console sends instructions, data-collection parameters, and
configuration information to the collectors. The CA UCM Collector Communication
service uses this port.
TCP port 1001
Open this port for communication from the collectors to the management console.
The CA UCM Console Communicator service uses this port.
12 Installation Guide
Port and Protocol Requirements
TCP port 9000
Open this port to receive CDR data from Avaya Communication Manager.
UDP port 162
Open this port to let the management console send SNMP traps to a trap receiver.
UDP port 5005
Open this port to receive RTCP data from Avaya endpoints.
UDP port 8381
Open this port to support Single Sign-on, enabling direct login to UC Monitor and
drill down from CA Performance Center to UC Monitor.
UCP port 8681
Open this port to let CA Performance Center access UC Monitor data for CA
Performance Center report views. The CA UCM Web Container service uses this
port.
UDP port 9995
Open this port to let medianet-enabled devices send data from Cisco IOS Flexible
NetFlow to the collector.
Internet Control Message Protocol
Enable ICMP to let the collector send traceroutes to an endpoint.
The default port settings are stored in the UC Monitor database, in configuration files,
and in the Windows Registry. You can change the settings when necessary. For
assistance, contact CA Technical Support.
Chapter 2: System Requirements 13
Chapter 3: Configuring the Hardware
When configuring the hardware, you need the following types of cables.
Power cable
Connects the UC Monitor server to a power supply, preferably a UPS.
Management NIC cable
One of the following types:
■
Copper NIC cable
■
Gb fiber NIC cable
When plugged into a switch, the management NIC provides network access to the
UC Monitor server and it enables remote viewing of the management console.
Monitor NIC cable
Collects network traffic from a SPAN port on the switch.
Configure the Server for the Management Console
The management console and the collectors are installed on separate servers in a
distributed system. The following procedure describes how to configure the server for
the management console.
Follow these steps:
1.
Connect one end of the power cable to the power outlet on the server.
2.
Connect the other end of the power cable to a power supply.
3.
Connect one end of the management cable to a NIC on the server.
4.
Connect the other end of the management cable to an appropriate switch.
5.
Turn on the server.
6.
Configure the management NIC. For more information, see Configure Network
Interface Cards (see page 17).
7.
Configure the server for the collector. For more information, see Configure the
Server for the Collector (see page 16).
Chapter 3: Configuring the Hardware 15
Configure the Server for the Collector
Configure the Server for the Collector
The management console and the collectors are installed on separate servers in a
distributed system. You can have a maximum of ten standard collectors per
management console, or 30 small-site collectors per management console. The
following procedure describes how to configure the server for the collector.
Note: In a Cisco Unified Communications Manager environment, place the UC Monitor
collector server as physically close to the Cisco call server as possible.
Follow these steps:
1.
Connect one end of the power cable to the power outlet on the server.
2.
Connect one end of the monitor and management cables to NICs on the server.
3.
Connect the monitor cable to the SPAN port.
4.
Connect the management cable to the management console server.
5.
Turn on the server.
6.
Configure the monitor and management NICs. For more information, see Configure
Network Interface Cards (see page 17).
Configure the Server for a Standalone System
In a standalone system, the management console and the collector are installed on the
same server.
Follow these steps:
16 Installation Guide
1.
Connect one end of the power cable to the power outlet on the server.
2.
Connect the other end of the power cable to a power supply.
3.
Connect one end of the monitor and management cables to NICs on the server.
4.
Connect the other end of the monitor cable to the switch where call servers are
connected.
5.
Connect the other end of the management cable to another switch, to enable
network access to the management console.
6.
Configure the monitor and management NICs. For more information, see Configure
Network Interface Cards (see page 17).
Configure Network Interface Cards
Configure Network Interface Cards
After connecting the hardware, configure the network interface cards (NICs) on the
collector and management console computers. In a standalone system, all configuration
takes place on one computer.
■
On each collector computer, set up network connections for the management and
monitor NICs.
■
On the management console computer, set the priority of the management NIC.
■
Assign a static IP address, subnet mask, and default gateway to the management
NIC.
Note: The other NICs on the collector, including the monitor NIC, do not transmit data
to the network. The IP addresses assigned to them do not need to be valid for the
network to which they are connected, nor do they require a default gateway
assignment.
When you purchase hardware from CA Technologies, components are delivered with the
NIC settings already configured. Use the following procedure to verify the settings or
update them as necessary.
When you purchase hardware from a different vendor, perform the following procedure.
Follow these steps:
1.
Navigate to the Network Connections window from the Control Panel on the
collector and management console computers.
2.
Review the names of the LAN or High-Speed Internet Connections. If necessary,
change the default names to correspond to the interfaces, as shown in the
following table:
Copper Ethernet adapter
Default name: Local Area Connection 2
New name: Management
Copper Ethernet adapter
Default name: Local Area Connection 3
New name: Monitor
Gigabit fiber port
Default name: Local Area Connection
New name: Fiber Monitor
Tip: You can identify devices by disconnecting the cable from the back of the device
and noting which interface status changes to "disconnected" in the Network
Connections dialog.
Chapter 3: Configuring the Hardware 17
Configure Network Interface Cards
3.
Disable unused monitor NICs:
a.
Right-click the NIC.
b.
Select Disable.
4.
Click Advanced, Advanced Settings.
5.
Click the up arrow to move the management NIC to the first position in the
Connections pane. This action sets the priority and enables UC Monitor to operate
correctly.
6.
Clear the following “Internet Protocol (TCP/IP)” check boxes for the monitor NIC:
■
File and Printer Sharing for Microsoft Networks
■
Client for Microsoft Networks
7.
Click OK.
8.
Navigate to the Control Panel and select Network Connections, Local Area
Connection.
9.
Click Properties on the General tab.
10. Select Internet Protocol (TCP/IP) and click Properties.
11. Select “Use the following IP address” and enter an IP address, subnet mask, and
default gateway.
12. Select “Use the following DNS Server addresses” and supply the IP address for the
DNS server.
Note: Do not use a DHCP address.
13. Repeat steps 11 and 12 for the monitor NICs, using the following suggested values:
Monitor NIC
IP address: 1.1.0.0
Subnet mask: 255.0.0.0
Fiber Monitor NIC
IP address: 1.1.0.1
Subnet mask: 255.0.0.0
18 Installation Guide
Chapter 4: Installing the Software
When you purchase hardware from CA Technologies, all components are delivered with
the UC Monitor software installed. Do not install the software.
When you purchase hardware from a different vendor, install the UC Monitor software
on the management console server and all collector servers.
Important: Do not install UC Monitor on a computer on which CA NetQoS Performance
Center is installed.
Installation Prerequisites
Before you install the UC Monitor software, perform the following tasks:
■
Install CA Performance Center in your environment. UC Monitor is a data source for
CA Performance Center. CA NetQoS Performance Center 6.1 is also supported.
■
Disable the following types of third-party software on all servers that host UC
Monitor components:
–
Anti-virus
–
Anti-spyware
–
Server monitoring and maintenance tools such as SMS, SUS, or MoM
■
Restart all servers to ensure that available operating system patches are applied.
■
Obtain the UC Monitor setup file, UCMSetup3.5.xxx.exe, from CA Technical
Support.
■
Extract or copy the UCMSetup3.5.xxx.exe file to the servers on which you want to
install the software.
Chapter 4: Installing the Software 19
Install the Management Console
Install the Management Console
Distributed systems have separate servers for the UC Monitor management console and
the collectors. Use this procedure to install the management console for a distributed
system.
Follow these steps:
1.
Double-click the setup program.
The CA Unified Communications Monitor Installer window opens.
2.
Click Next.
The License Agreement appears in the window.
3.
Read and accept the license agreement, and then click Next.
Installation options appear in the window.
4.
Select 'Unified Communications Monitor Management Console,' and then click
Next.
Installation folder options appear in the window.
5.
(Optional) Click Choose to select a different installation location. The default is
C:\CA.
6.
Click Next.
An installation summary appears in the window.
7.
Click Install.
The installation process begins. Messages indicate the progress of the installation.
When installation is complete, a "successful installation" message appears in the
window.
8.
Select 'Yes, restart my system,' and then click Done.
9.
Run the setup program on the collector servers (see page 21).
You can now perform post-installation tasks (see page 23) and prepare your
monitoring environment (see page 27).
20 Installation Guide
Install the Collector
Install the Collector
Distributed systems have separate servers for the UC Monitor console and the
collectors. Use this procedure to install the collectors in a Cisco or Avaya environment.
Note: In a Microsoft Lync environment, you configure a Microsoft server as a Lync
collector. For more information, see the UC Monitor online help. Or review the use case
titled Managing Collectors in Microsoft Lync Environments from the CA Unified
Communications Monitor bookshelf.
Follow these steps:
1.
Double-click the setup program.
The CA Unified Communications Monitor Installer window opens..
2.
Click Next.
The License Agreement appears in the window.
3.
Read and accept the license agreement, and then click Next.
Installation options appear in the window.
4.
Select 'Unified Communications Monitor Collector,' and then click Next.
Installation folder options appear in the window.
5.
(Optional) Click Choose to select a different installation location. The default is
C:\CA.
6.
Click Next.
An installation summary appears in the window.
7.
Click Install.
The installation process begins. Messages indicate the progress of the installation.
When installation is complete, a "successful installation" message appears in the
window.
8.
Select 'Yes, restart my system,' and then click Done.
You can now perform post-installation tasks (see page 23) and prepare your
monitoring environment (see page 27).
Chapter 4: Installing the Software 21
Install All Components on One Server
Install All Components on One Server
A standalone system is one server that hosts the UC Monitor management console and
the collector. Use this procedure to install the management console and the collector on
one server.
Follow these steps:
1.
Double-click the setup program.
The CA Unified Communications Monitor Installer window opens.
2.
Click Next.
The License Agreement appears in the window.
3.
Read and accept the license agreement, and then click Next.
Installation options appear in the window.
4.
Select 'Unified Communications Monitor Standalone,' and then click Next.
Installation folder options appear in the window.
5.
(Optional) Click Choose to select a different installation location. The default is
C:\CA.
6.
Click Next.
An installation summary appears in the window.
7.
Click Install.
The installation process begins. Messages indicate the progress of the installation.
When installation is complete, a "successful installation" message appears in the
window.
8.
Select 'Yes, restart my system,' and then click Done.
You can now perform post-installation tasks (see page 23) and prepare your
monitoring environment (see page 27).
22 Installation Guide
Chapter 5: Post-Installation Tasks
This section contains the following topics:
Install Updates (see page 23)
Change the Host Name (see page 23)
Update the List of Trusted Internet Sites (see page 23)
Synchronize the System Time (see page 24)
Perform Configuration Tasks from the Management Console (see page 24)
Install Updates
Install all important updates, including the most recent service pack, that are available
for the Microsoft Windows operating system.
Install any UC Monitor updates available from the CA Support Online website.
Change the Host Name
For the collectors in a distributed system, change the host name to help you identify the
collector servers in UC Monitor reports. Use a naming convention similar to the
following:
<CollectorName>-<ManagementConsoleName>-<Location>
For example:
ComMgr1-MainOffice-NYC
Update the List of Trusted Internet Sites
Add the console server to the list of trusted Internet sites. The process varies by
browser. The following instructions are for Microsoft Internet Explorer.
Follow these steps:
1.
Launch Internet Explorer on the console server.
2.
Click Tools, Options.
3.
Click the Trusted Sites icon on the Security tab.
Chapter 5: Post-Installation Tasks 23
Synchronize the System Time
4.
Click Sites.
5.
Enter http://localhost in the 'Add this Web site to the zone' field.
6.
Click Add.
Synchronize the System Time
Synchronize the system time among all servers where you installed UC Monitor
components. Perform the following steps on each server.
Follow these steps:
1.
Log in as a user who is a member of the Administrators group.
2.
Right-click the date or time on the right edge of the taskbar and select 'Adjust
date/time.'
The Date and Time dialog opens.
3.
Click the Internet Time tab.
4.
Click 'Change settings.'
The Internet Time Settings dialog opens.
5.
Select the check box labeled 'Synchronize with an Internet time server.'
6.
Select the server with which you want to synchronize. The default is
time.windows.com.
7.
Click 'Update Now.'
The system time is synchronized with the selected server.
8.
Click OK in the Internet Time Settings dialog.
9.
Click OK in the Date and Time dialog.
Note: If you have collectors in different time zones, set each device to its local time
zone. Times are converted to Greenwich Mean Time (GMT).
Perform Configuration Tasks from the Management Console
Perform the following configuration tasks from the UC Monitor management console:
24 Installation Guide
■
Organize phones, endpoints, gateways, and other network components into
Locations.
■
Add collection devices.
■
Customize collector thresholds.
■
Customize performance thresholds.
Perform Configuration Tasks from the Management Console
■
Enable incidents to trigger response notifications.
■
Register UC Monitor as a data source for CA Performance Center.
■
Configure SNMP profiles for Cisco voice gateways and Avaya Communication
Manager servers.
■
Configure users and their roles.
Note: For instructions, see the UC Monitor online help. Related documentation, such as
use cases, is also available from the CA Unified Communications Monitor bookshelf.
Chapter 5: Post-Installation Tasks 25
Chapter 6: Preparing Your Monitoring
Environment
This section contains the following topics:
Preparing an Avaya Communication Manager Environment (see page 27)
Preparing a Cisco Unified Communications Manager Environment (see page 28)
Preparing a Microsoft Lync Environment (see page 29)
Preparing Acme Packet Session Border Controllers (see page 29)
Preparing Cisco Unified Border Elements (see page 31)
Example of UC Monitor in a Multi-Vendor Environment (see page 31)
Preparing an Avaya Communication Manager Environment
UC Monitor supports unified communications deployments that use Avaya
Communication Manager for call processing. The collector monitors voice calls made
with the following Avaya components:
■
Desk phones and softphones
■
Communication Manager, including Aura Communication Manager
■
Avaya voice gateways
Avaya endpoints, including voice gateways, send frequent call-quality reports directly to
the collector while calls are in progress. The quality data is sent as RTCP packets. Using
SNMP, the collector periodically polls the Communication Manager for device
information. The Communication Manager can be configured to send CDR data to the
collector after each call is completed.
Many Avaya gateways have an AVAYA_RTP_MIB that can be polled with SNMP.
However, RTCP is supported for all Avaya gateways. Therefore, UC Monitor relies
primarily on RTCP for collecting metrics in an Avaya environment. No switch port or
SPAN is required.
An Avaya network administrator performs several tasks to prepare an Avaya
environment for monitoring with UC Monitor:
■
Enabling access to SNMP agents.
■
Enabling Avaya endpoints to send RTCP data to the UC Monitor collector, which
takes the role of the RTCP Monitor in an Avaya system.
Chapter 6: Preparing Your Monitoring Environment 27
Preparing a Cisco Unified Communications Manager Environment
■
Configuring the UC Monitor collector as a CDR recipient.
■
Using the Trunk Group Measurement Selection page (in the Communication
Manager web interface) to identify the trunk groups that you want to monitor.
Note: Detailed instructions for these tasks are provided in the use case titled Preparing
an Avaya Communication Manager Environment.
More information:
Port and Protocol Requirements (see page 12)
Preparing a Cisco Unified Communications Manager
Environment
UC Monitor supports unified communications deployments that use Cisco Unified
Communications Manager for call processing. Cisco endpoints report quality data to
their call server at the completion of every call. The UC Monitor collector inspects these
flows for performance metrics. The collector transmits to the management console only
the data necessary to calculate and report call setup and call quality.
A Cisco network administrator performs several tasks to prepare a Cisco environment
for monitoring with UC Monitor:
■
Enabling the Call Stats setting in a voice-quality-enabled SIP profile.
■
Enabling the collection of call detail records (CDRs) and call management records
(CMRs).
■
Enabling the internal web server on IP phones.
■
Configuring SPAN ports to mirror voice traffic to the collector.
■
Configuring medianet-enabled devices, including IPv4 routing, the collection
interval, a custom Flow Monitor record, and Flow Exporter.
Detailed instructions for these tasks are provided in the following documents on the CA
Unified Communications Monitor bookshelf:
28 Installation Guide
■
Preparing a Cisco Unified Communications Manager Environment
■
Best Practices for Data Acquisition
Preparing a Microsoft Lync Environment
Note: UC Monitor automatically reports on call quality metrics from authenticated SIP
traffic by parsing packets that contain Transport Layer Security (TLS) authenticated
messages.
Cisco Unified Communications Manager uses port 5061 for authenticated SIP traffic.
If you do not want to monitor SIP traffic, or you want to use a different port, contact CA
Technical Support for information about configuring the .ini file.
Preparing a Microsoft Lync Environment
UC Monitor supports unified communications deployments that use Microsoft Lync for
call processing. The flexible product architecture lets you monitor Cisco and Avaya call
servers and the Lync system, or a pure Lync system.
■
No dedicated telephony hardware is required in a Lync environment, although the
system does support optional integration with a PBX. Instead, the standard system
can process VoIP and video calls. Audio and video calls are integrated with other
Microsoft Office applications, such as Outlook, and with user contact information,
such as IP address, SIP URI, and presence status.
■
UC Monitor supports hardware-based IP phones, such as Polycom, in a Lync system.
Users can make calls from supported phones, or from the lightweight Office
Communicator application.
A Lync network administrator can configure HTTPS or use authentication certificates to
enable secure communication between Lync servers and UC Monitor. UC Monitor does
not require HTTPS or authentication certificates, but your environment may require
them.
Note: See the Microsoft website for information about managing certification authority
on Windows Server 2008 R2:
http://technet.microsoft.com/en-us/library/cc772011.aspx.
Preparing Acme Packet Session Border Controllers
UC Monitor supports Acme Packet Session Border Controllers (SBCs). SBCs are often
deployed between a unified communications system and a service provider network.
The SBCs use FTP to push specially formatted call detail records (CDRs) to the Data
Transformer service on the management console. The management console is
configured as the FTP recipient. The Data Transformer service converts the CDRs to XML
format. UC Monitor parses the XMLs for the call accounting data and QoS metrics of the
ingress and egress call segments for the SBC. The data appears in UC Monitor reports.
Chapter 6: Preparing Your Monitoring Environment 29
Preparing Acme Packet Session Border Controllers
The following diagram illustrates how an Acme Packet SBC communicates with UC
Monitor:
Notes:
■
UC Monitor automatically discovers properly configured Acme Packet SBCs
when they push CDRs to the management console. For information about
configuring the SBCs, see the use case titled Preparing Acme Packet Session
Border Controllers.
■
UC Monitor installation creates an FTP site on the management console that
supports login by an anonymous user. If your environment requires secure FTP,
you can configure any server as the secure FTP recipient, as long as that server
then pushes the CDRs to the following location on the management console:
<install directory>\VoipMonitor\FTPSite\ACME.
■
The Data Transformer service appears in the Collection Device List as
"Transformer." You can edit the Transformer to change the name and to
change the IP domain assignment (in environments with multiple IP domains).
The Update Status and Reload All features do not apply to the Transformer.
You cannot delete the Transformer.
■
In UC Monitor reports, MOS values for an Acme Packet SBC reflect the MOS at
the SBC, and not the MOS for the devices on either side of the SBC.
More information:
Port and Protocol Requirements (see page 12)
30 Installation Guide
Preparing Cisco Unified Border Elements
Preparing Cisco Unified Border Elements
UC Monitor supports Cisco Unified Border Elements (CUBEs), the Cisco session border
controller for enterprise IP networks. UC Monitor automatically discovers the devices on
which CUBE is enabled and uses SNMP to poll them for the call metrics that appear in
UC Monitor reports.
The device on which the CUBE is enabled is discovered as a session border controller
and appears in the management console on the Other Devices page.
A Cisco network administrator performs the following tasks to prepare a CUBE device
for monitoring with UC Monitor:
■
Enable SNMP on the device.
■
Enable end-of-call statistics in SIP BYE messages on the device.
■
Create an SNMP profile for the device in the UC Monitor management console.
Important: UC Monitor automatically polls a discovered CUBE device. If you do not
enable SNMP and end-of-call statistics, the metrics that UC Monitor collects from the
device may not be correct.
Example of UC Monitor in a Multi-Vendor Environment
You can use a standalone system or a distributed system to monitor an environment
that includes a combination of Cisco, Avaya, and Microsoft components. Collectors can
collect data from multiple sources, and all data is correlated at the management
console.
The following diagram illustrates a multi-vendor environment that includes medianet:
Chapter 6: Preparing Your Monitoring Environment 31
Example of UC Monitor in a Multi-Vendor Environment
32 Installation Guide
Index
A
Avaya environments
configuring • 27
B
browser support • 10
C
Cisco environments
configuring • 28
collectors
configuring the servers • 16
installing the software • 21
configuring network interface cards • 17
configuring the management console • 15
S
Session Border Controllers
configuring • 29
software
installing on one server • 22
installing the collector • 21
installing the management console • 20
prerequisites • 19
system time, synchronizing • 24
T
TCP
port requirements • 12
U
F
UDP port requirements • 12
firewall requirements • 12
V
H
virtual system requirements • 12
hardware requirements • 10, 11
host name, changing • 23
I
ICMP • 12
M
management console
configuring the server • 15
installing the software • 20
N
network interface cards, configuring • 17
O
operating system support • 9
P
port requirements • 12
post-installation tasks • 23
protocols
requirements • 12
Index 33
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising