CA ehealth. Monitoring Motorola/Winphoria Mobile Wireless Devices User Guide. r6.1

Transcription

1 CA ehealth Monitoring Motorola/Winphoria Mobile Wireless Devices User Guide r6.1

2 This documentation and any related computer software help programs (hereinafter referred to as the Documentation ) is for the end user s 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 protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the related software is limited to the period during which the applicable license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, 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 THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any product referenced in the Documentation is governed by the end user s applicable license agreement. 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 , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2008 CA. All rights reserved.

3 Contents Chapter 1: Overview Element Overview Control Switch Element Resident Applications Element Application Element Transaction Element Session Initiation Protocol (SIP) Status Element Chassis Element Card Element Active Directory Elements Resident Applications Element Application Element Transaction Element Chassis Element Card Element Chapter 2: Reporting Available Reports At-a-Glance Reports Sample At-a-Glance Report Trend Reports Sample Trend Report Top N Reports Sample Top N Report Supported Trend and Top N Variables Variable Data Mappings Contents 1

4

5 Chapter 1: Overview Push-to-Talk services allow users to instantly connect with one or more users over a cellular wireless network. The devices operate as walkie-talkies users push a button and instantly speak to each other. Push-to-Talk advantages include much faster connection times than a typical telephone call, and the ability to connect to several users at the same time. The ehealth software supports Motorola devices (formerly Winphoria Inc. devices) that support Push-to-Talk over Cellular (PoC) services. With the ehealth solution, you can monitor the performance of the Motorola PoC services and devices. For example, using ehealth reports, you can identify whether services are available and operating normally, or if the call volume is high and devices are over utilized. The ehealth solution helps you determine whether your customers are receiving the best possible levels of service. Motorola Active Directory applications maintain subscriber information Motorola Control Switches manage call processing Push-to-Talk handsets connect to the network over the cellular wireless network Overview 5

6 Element Overview Element Overview As shown in Figure 1, there are two main devices that ehealth manages within the Motorola PoC service: Control Switches and Active Directory devices. The Control Switch provides call processing and signaling services, and collects information necessary to generate call records. The Active Directory maintains subscriber (or user) information. You can monitor these devices with ehealth to ensure that your service is performing as expected. When performance does not meet expectations, ehealth reports can help you identify possible sources of the problem. To monitor Motorola devices with ehealth, it is important to understand how the devices map to ehealth elements, the variables that are supported for each element, and the reports that you can run on those elements. ehealth creates an element for each Motorola device that it discovers. ehealth also creates elements for several subordinate applications of the Motorola devices. These elements are arranged in a hierarchy based on the Motorola device and subordinate application hierarchy. For example, Figure shows that application elements are subordinate elements of the resident applications element, and the parent element is the Control Switch element. Control Switch Element Resident Applications Element Transaction Elements SIP Status Element Chassis Element Application Elements Card Elements Figure 1 Control Switch Element Hierarchy ehealth collects data from the devices for which it establishes elements and maintains this information in its database. When updates are made to the Motorola devices, ehealth updates the element information. ehealth displays this element information in ehealth TopN, Trend, and At-a-Glance reports. You can run these reports on most elements. The exceptions are those elements that do not contain any variables for which ehealth can collect data. These are noted in the sections that follow. 6 Monitoring Winphoria/Motorola Mobile Wireless Devices User Guide

7 Element Overview Variables (also known as trend variables) are the performance indicators used to monitor elements. The types of variables vary from element to element. For example, some variables for the Control Switch element are average call length in seconds, average attempted calls, and percentage of lost calls. When you generate ehealth reports, you select the element type and the variables for which you want to view data for that element. Control Switch Element For each Control Switch, ehealth creates one main Control Switch element and several sub-elements. The Control Switch element has variables for the entire switch, such as call attempts per subscriber, lost calls, and failed calls. Since this element contains variables, reports display data for it as well as for the subordinate elements described in the following sections. If you used a prior release of the ehealth Winphoria support, note that this element is an upgrade to the prior Control Switch element (now under the Motorola name). When you upgrade ehealth to the latest patch, the historical data will be preserved. Resident Applications Element The resident applications element allows the grouping of the subordinate application elements, described in the next section. Although you cannot run reports for the resident applications element (because it has no variables), you can run At-a-Glance reports for the subordinate elements. Application Element Each application element contains variables associated with a particular type of application. For the Media Resource Provisioning (MRP) application, you can choose to display data for the number of application restarts, the amount of CPU and memory utilization, and the peak VoIP media streams. A device can have multiple instances of one application or several different applications. Most applications contain a standard set of variables for: Average and peak memory and CPU utilization The number of application restarts However, some applications contain more specific variables. There are four application elements in each Control Switch: CCSW GCR Media Resource Provisioning (MRP) HLR Overview 7

8 Element Overview Transaction Element Each transaction element contains variables associated with a particular type of transaction. Each Control Switch has four transaction elements: Database operations Provisioning and Web server SNMP TL1 Session Initiation Protocol (SIP) Status Element This element contains variables for the various types of SIP status codes that have been returned. Chassis Element This single element is used to group the subordinate card elements. Although it does not have variables of its own, you can run an At-a-Glance report that displays data for all of the subordinate card elements. Card Element There is one element for each card plugged into the chassis. For one Control Switch, it is not unusual for ehealth to create up to 55 elements. If you used a prior release of the ehealth Winphoria support, note that this element is an upgrade to the prior Control Switch element (now under the Motorola name). When you upgrade ehealth to the latest patch, the historical data will be preserved. Active Directory Elements For each Active Directory, ehealth creates one main Active Directory element. This element has no variables of its own, but it is used to group all of the subordinate elements shown in Figure 2. The At-a-Glance report for this element shows the aggregate performance data of its subordinate elements. 8 Monitoring Winphoria/Motorola Mobile Wireless Devices User Guide

9 Element Overview Active Directory Element Resident Applications Element Transaction Elements Chassis Element Application Elements Card Elements Figure 2 Active Directory Element Hierarchy Resident Applications Element This element has no variables, therefore reports do not reflect data for the element itself. The resident applications element allows grouping of subordinate application elements for which an inclusive At-a-Glance report can be run. It is the same element type as its counterpart in the Control Switch. Application Element Each application element contains variables associated with a particular type of application. This is the same element type as its counterpart in the Control Switch. Transaction Element Each transaction element contains variables associated with a particular type of transaction. There are five transaction elements in each Active Directory switch: Active Directory Database operations Provisioning and Web server SNMP TL1 This is the same element type as its counterpart in the Control Switch. However, the Control Switch does not contain the Active Directory transactions element. Overview 9

10 Element Overview Chassis Element This single element is used to group the subordinate card elements. Although it does not have variables of its own, you can run an At-a-Glance report that displays data for all of the subordinate card elements. This is the same element type as its counterpart in the Control Switch. Card Element There is one element for each card plugged into the chassis. For one Active Directory, it is not unusual for ehealth to create up to 50 elements. This is the same element type as its counterpart in the Control Switch. 10 Monitoring Winphoria/Motorola Mobile Wireless Devices User Guide

11 Chapter 2: Reporting Available Reports ehealth offers Trend, Top N, and At-a-Glance reports for Motorola elements. Use these reports to gain insight to the performance of your devices and applications. At-a-Glance Reports At-a-Glance reports contain a set of pre-defined charts that provide insight to the performance of the elements. For example, the Control Switch At-a-Glance report displays the following charts: Calls in progress Average call length Average number of callers Calls per second MRS usage Average media setup time Average GCR time Average latency SIP invites Disconnects per second, due to floor timeout Disconnects per second, due to radio interface failure You can use the At-a-Glance reports to compare the variables and look for possible combinations that might help you to identify sources of a problem. From At-a-Glance charts, you can drill down to Trend reports to view the performance data in greater detail. ehealth supports numerous drilldowns between the At-a-Glance reports associated with the Motorola elements at different levels in the hierarchies. This allows you to navigate to a higher or lower view for the resource that can help you to troubleshoot problems by reviewing the performance of related elements.

12 The following table lists the supported At-a-Glance charts for the Control Switch and Active Directory elements and their subordinate elements. Element Control Switch CPU Active Directory Synchronization Transactions Active Directory Resident Applications Winphoria Applications (HLR, BILLNB, CCSW, CDRCP, IPMH, GCR, LOG, MTAS, SYNC, MRP) Provisioning and Web Server Transactions Charts Calls In Progress Average Call Length Average Number of Callers Per Call Attempted Calls Completed Calls Failed Calls Aborted Calls Attempted Registration Updates MRS Usage Average Media Setup Time Average GCR Time Average Latency SIP Invites Disconnects/sec, Floor Timeout Disconnects/sec, Radio Interface Failure Failures/sec, No Response to 200 OK CPU Utilization Memory Utilization Associations CPU Utilization Memory Utilization Restarts Swap Utilization Associations Active Directory Operations Received from Peer/Second Active Directory Operations Sent to Peer/Second CPU Utilization Memory Utilization Associations CPU Utilization Memory Utilization Associations CPU Utilization Memory Utilization Restarts/Second Call Attempt/hour Group Members GCR Queries Simultaneous VoIP Media Stream HLR Queries Associations Provisioning and Web Server Queries Provisioning and Web Server Updates Average Response Time for Queries Average Response Time for Updates

13 Element SNMP Transactions Database Operations Chassis TL1 Transactions SIP Status NOTE: At-a-Glance reports on SIP Status elements may fail because certain Winphoria devices do not fully support statistics for this element type. Charts SNMP Gets SNMP GetNexts SNMP GetBulks SNMP Sets Average Response Time for SNMP Get Average Response Time for SNMP GetNext Average Response Time for SNMP GetBulk Average Response Time for SNMP Set Database Selects Database Inserts Database Updates Database Deletes Database Truncates Average Response Time for Database Select Average Response Time for Database Update Average Response Time for Database Delete Average Response Time for Database Truncate CPU Utilization Memory Utilization TL1 RTRV Commands/Second TL1 ED Commands/Second TL1 CRTE Commands/Second TL1 DLT Commands/Second Average Response Time for TL1 RTRV Command Average Response Time for TL1 ED Command Average Response Time for TL1 CRTE Command Average Response Time for TL1 DLT Command 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authent Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required Request Entity Too Large or URL Too Long 415 Unsupported Media Type 420 Bad Extension 480 Temporarily Unavailable 481 Call/Trans Does Not Exist Loop Detected, Too Many Hops or Address Incomplete

14 Element SIP Status (continued) NOTE: At-a-Glance reports on SIP Status elements may fail because certain Winphoria devices do not fully support statistics for this element type. Charts 485 Ambiguous 486 Busy Here 487 Request Terminated 500 Server Internal Error 501 Not Implemented 502 Bad Gateway Service Unavailable or Server Timeout 505 Version Not Supported 600 Busy Everywhere 603 Decline 604 Does Not Exist Anywhere Sample At-a-Glance Report When you run At-a-Glance reports for Motorola (Winphoria) mobile wireless devices, be sure to select MWRouter or one of the Winphoria types from the Technology list in the Run Report dialogs. The sample At-a-Glance report displays four of the charts available for the Control Switch element. The charts display the average call length, number of callers, media setup time and MRS usage in the previous 12 hours. Trend Reports Trend reports allow you to view the detailed behavior of a particular variable or set of variables for an element.

15 Sample Trend Report When you run a Trend report for one of these elements, you select one or more variables. To identify the variables associated with the Motorola elements, see Supported Trend and Top N Variables on page 16. This Trend report compares the data for the number of attempted calls versus the number of completed calls for a day. It can help you to determine how well the Motorola devices supported the call loads during the day. It shows several spikes in attempted calls during the 24 hours, while the completed calls were consistent throughout the day. Top N Reports Top N reports provide information on groups of elements. These reports use the same variables as Trend reports, but in addition, they offer information such as peak values. Use this report to list the best or worst performers for a specific variable among the elements in a group. For example, you might want to understand which mobile wireless devices use the most CPU or show the highest number of failed calls. When you run Top N reports, you select a group of elements and the variables that you want ehealth to compare for each element in that group. Sample Top N Report When you generate a Top N report, you select a group of elements for which you want to view common values, and then select up to six variables for comparison. To identify the variables associated with the Motorola elements, see Supported Trend and Top N Variables on page 16. The sample Top N report displays the percentage of application CPU utilization, application memory utilization, and total number of application restarts for the members of the group of Winphoria Application elements.

16 Supported Trend and Top N Variables The following table lists the supported Trend and Top N variables for the Control Switch and Active Directory elements and their subordinate elements. Element Control Switch Trend Variables Aborted Calls Aborted Calls Total Answered Sip-originated Calls Answered Sip-terminated Calls Attempted Calls Total Attempted Registration Updates Attempted Sip-originated Calls Attempts Sip-terminated Calls Availability Average Attempted Calls Average Call Length (seconds) Average Completed Calls Average GCR Access Time Average Media Setup Time (ms) Average Num of Callers Per Call Avg CS Latency SIP Invites (ms) Busy Hour Determiner

17 Element Control Switch (Continued) Resident Applications Winphoria Applications (GCR, HLR, CCSW, CDRCP, BILLNB, IPMH, LOG, MTAS, SYNC) MRP Application Database Transactions Trend Variables CPU Usage Call Attempts per Subscriber Call Seconds per Subscriber Caller No Response to 200 OK Calls Disconn Floor Timed Out Calls Disconn RADIO Intf Failure Completed Calls Total Failed Calls Failed Calls Total In-Progress Calls Ineffective Attempts Lost Calls Memory Usage Percent Ineffective Attempts Percent Lost Calls Successful Sip-originated Calls Successful Sip-terminated Calls Total MRS Usage This element does not have any Trend variables. Application CPU Utilization Application Memory Utilization Application Peak CPU Utilization Application Peak Mem Utilization Number Application Restarts Application CPU Utilization Application Memory Utilization Application Peak CPU Utilization Application Peak Mem Utilization MRP Peak VOIP Media Streams Number Application Restarts Avg. DB Delete Response Time Avg. DB Insert Response Time Avg. DB Select Response Time Avg. DB Truncate Response Time Avg. DB Update Response Time Number Database Deletes Received Number Database Inserts Received Number Database Selects Received Number Database Truncates Received Number Database Updates Received

18 Element Provisioning and Web Server Transactions Chassis SIP Status NOTE: Trend reports on SIP status elements may display "no data available. The error appears because certain Winphoria devices do not fully support statistics for this element type. SIP Status (continued) Active Directory TL1 Transactions Trend Variables Avg. Prov. and Web Svr Qry Time Avg. Prov. and Web Svr Upd Time Prov. and Web Server Queries Prov. and Web Server Updates This element does not have any trend variables. AMBIGUOUS Errors BAD_EXTENSION Errors BAD_GATEWAY Errors BAD_REQUEST Errors BUSY_EVERYWHERE Errors BUSY_HERE Errors CALL_LEG_TRANS_NOT_EXIST Errors CONFLICT Errors DECLINE Errors DOES_NOT_EXIST_ANYWHERE Errors FORBIDDEN Errors GONE Errors INTERNAL_SERVER_ERROR Errors LENGTH_REQUIRED Errors METHOD_NOT_ALLOWED Errors NOT_ACCEPTABLE Errors NOT_FOUND Errors NOT_IMPLEMENTED Errors PAYMENT_REQUIRED Errors PROXY_AUTHEN_REQUIRED Errors REQUEST_CANCELLED Errors REQUEST_ENTITY_TOO_LARGE Errors REQUEST_TIMEOUT Errors SERVICE_UNAVAILABLE Errors SIP_VERSION_NOT_SUPPORTED Errors TEMPORARILY_NOT_AVAILABLE Errors TOO_MANY_HOPS Errors UNAUTHORIZED Errors UNSUPPORTED_MEDIA_TYPE Errors CPU Usage Memory Usage Avg. TL1 CRTE Response Time Avg. TL1 DLT Response Time Avg. TL1 ED Response Time Avg. TL1 RTRV Response Time Num TL1 CRTE Commands Received Num TL1 DLT Commands Received Num TL1 ED Commands Received Num TL1 RTRV Commands Received

19 Element CPU SNMP Transactions AD Synchronization Transactions Trend Variables CPU Usage CPU Utilization Peak Memory Usage Memory Utilization Peak Number of Card Restarts Swap Utilization Avg. SNMP GET Response Time Avg. SNMP GETBULK Response Time Avg. SNMP GETNEXT Response Time Avg. SNMP SET Response Time Num SNMP GET Reqsts Received Num SNMP GETBULK Reqsts Received Num SNMP GETNEXT Reqsts Received Num SNMP SET Reqsts Received Number AD Operations Received Number AD Operations Sent Variable Data Mappings For a complete description of the Motorola/Winphoria elements, data mappings, and trendable variables, go to the Certified Devices Web page on the Web site. As a registered user, you can obtain important information about the Motorola Push-to-Talk (PTT) devices, such as the following: Available MIB Translation Files (MTFs) General Information Database Column Mappings Polled MIB Variables Trend Variables

20 Figure 3 Certified Devices Page for a Winphoria CPU Element In addition, you can use the ehealth Element Variable report (available from the ehealth Web interface Organization Page) to obtain detailed information about the Trend variables and polled MIB OIDs for each element. Figure 4 shows a sample report with the Trend variables for the Control Switch element. It shows how ehealth combines and evaluates the MIB variables to obtain the data for each Trend variable for the element.

21 Figure 4 Element Variable Report for Winphoria Control Switch Element

22