UC Monitor calculates baseline routes by running regular traceroutes to selected Cisco IP endpoints. The route information is included for route comparison in the Traceroute Investigation Details report for Locations where you defined a key phone. The key phone serves as the target device for the traceroutes.
Routine traceroutes to find a baseline are a Cisco-only feature. Routine traceroute monitoring is performed regularly on all Cisco voice gateways, including gateways that UC Monitor discovers and gateways that you add. An administrator can disable the option to “Perform routine traceroutes for baseline” when adding or editing a voice gateway definition.
Tip: Endpoints in Microsoft and Avaya deployments do not support routine traceroutes for deriving a baseline route. To find out more about a particular Avaya call path, perform a Traceroute Investigation with the phone, gateway, or Communication Manager as the target.
Routine traceroute tests are launched every four hours, starting at 2:00 a.m. The time zone of the collector determines the schedule, but the times that appear in reports reflect the time zone of the management console.
In general, only one collector runs a routine traceroute to a target, but under certain circumstances, multiple collectors run traceroutes to the same target. In such a case, baseline path results are less accurate. Different collectors get different results, and baselines are calculated based on the frequency of path results.
|
Copyright © 2012 CA.
All rights reserved.
|
|