Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > Path based IPSLA Operations: Historical traceroute resource missing history

Path based IPSLA Operations: Historical traceroute resource missing history

Created by Matthew Lamb, last modified by MindTouch on Jun 16, 2016

Views: 935 Votes: 0 Revisions: 3

Overview

 

This article describes the issue when a series of path based IPSLA operations being monitored in VNQM (ICMP Path Echo and ICMP Path Jitter) and in the IPSLA Details view, the Current and Historical traceroute only display limited information. 

Environment

  • VNQM version 4+
  • Network devices utilizing ICMP Path Echo and ICMP Path Jitter

 

Cause 

The Historical Traceroutes resource only displays the latest historical traceroute information. In some cases, if multiple different traceroutes are gathered from the device, then it will display the latest historical traceroutes per each different traceroute.

 

This is working by design. If you would like for it to change, you will need to submit a feature request for it. Otherwise, they will need to use reports to gather the information.

 

Resolution

  1. Utilize stock report in Report Writer for the Path based historical data.
  2. Create a new report for select data

The query below is also usable to gather traceroute information directly from the database as well. Can be utilized as a SQL based report in Report Writer:

select top 1000
vhopresults.VoipOperationInstanceID as OperationID,
vhopnames.operationname as Name,
ipslaoperationnumber as OperationNumber,
CONVERT(datetime, 
               SWITCHOFFSET(CONVERT(datetimeoffset, 
                                    vhopresults.recordtimeutc), 
                            DATENAME(TzOffset, SYSDATETIMEOFFSET()))) 
       AS Time,
hopindex as HopIndex,
HopIpAddress,
AvgRoundTripTime
from VoipPathHopOperationResults vhopresults inner join voipoperationnames vhopnames on vhopresults.voipoperationinstanceid=vhopnames.voipoperationinstanceid
INNER JOIN VoIPOperations vpo on vhopresults.voipoperationinstanceid=vpo.VoipOperationInstanceID
where vpo.ipslaoperationnumber = 40000 and vpo.operationtype = 'ICMP Path Echo'
-- You will need to make sure to set the 2 above where statements to the value want for the operation number and the operation type
-- The types of operation type are: vpo.operationtype = 'ICMP Path Echo' or 'ICMP Path Jitter'
order by vhopresults.VoipOperationInstanceID asc, vpo.ipslaoperationnumber asc, time asc, hopindex asc

 

 

Last modified

Tags

Classifications

Public