No data for Selected time period,???
If i'm viewing a voip call path, the graphs "MOS, Jitter, etc.." state No data for Selected time period. does not matter if I select a time period of 5 minutes to whatever. If I click on the view reverse call path, I get the information in the Graphs...
Also, a related issue, if I'm at the voip site view -> Voip Call Path, some sites states "Data not collected yet. Please wait a few minutes."
Does anybody have an Idea of what could be happening? or how to troubleshoot this?
Thank you in advance
I'm Running
Voip Monitor 2.0 SP 1
ORION NPM 8.5.1 SP3
It sounds like you are only collecting data for one of the call paths. I recommend following the steps athttp://thwack.com/forums/p/7855/32986.aspx#32986 to ensure the appropriate operation number is assigned to the call path and to update the IP SLA operation number if it is not correct.
Thank you for that document, it did not specifically fix my current issue. However your response "It sounds like you are only collecting data for one of the call paths." Spawned a thought process, I checked the router that i'm currently having a problem with for any IP SLA configurations and there was none configured.
I have the router set up for "automatic" configurations
A few questions:
1.) what is the best way to get IP Sla configured on this router?
2.) Also, what is the best way to start over?,.. Delete everything that I currently have and try this process again?
3.) how do I find this "auto-discovery" feature? I've been looking, and I just can not find it.
Thank you for your time,
You must have the read/write community string specified within Orion for VoIP Monitor to configure and collect IP SLA data for the desired Cisco device. You can double-check that the device has this read/write community string specified by right-clicking on the device within the Orion System Manager and selecting Node Details. One possibility is that the device had the proper read/write community string when it was added, the read/write community string was changed, the IP SLA operation on the device was deleted due to a reboot or other device change, and VoIP Monitor did not have rights to re-create the IP SLA operation. Updating the read/write community string should resolve the issue.
If you want to start over for one of the devices, then you can remove the device as a Site within the Sites section under VoIP Settings, wait a couple of minutes, add the device back into VoIP Monitor as a Site, and configure the call path settings (if these settings need to be modified).
This setting is only available if you are manually configuring some of the devices for IP SLA data.
Thank you Haley for your response back, I do Appreciate your help in this matter.
I'm still having the issue of "No data for Selected time period".
I’m not sure what the problem is, I was able to get one site working to satisfaction but it entailed
removing it and re adding it several times. Initially when I installed the voip monitor I had added
all of the sites at once. Nothing has changed in regards to snmp ro/rw strings, the Orion NPM module
is working just fine.
I don’t think it’s a problem with snmp. All other tools that we use from Solar winds is working as to be
expected, just some minor tweaking is needed. The routers that we are using for Voip monitoring support
Ip Sla, the routers are running the same IOS.
The sites that we are having the problem with, I can remove them from IP Sla, and re add them.
I then can go to the router directly and look at the command line interface and see that no configurations
have been applied to IP sla. When I make an addition to the voip monitor should it make those additions
to the router immediately?
With the site that I was able to get working, I removed it and then added it. I started checking the
command line for ip sla all that day and it wasn’t being configured. I was then preoccupied for a
few days and was not able to return to it. A few days had past and I then checked ip sla through the
command line and was able to see it configured.
Is this a normal practice for solarwinds to delay configurations?
thank you for your time
I have noticed similar things. The VoIP monitor does not always recover when an IP SLA router reboots. Sometimes both paths to/from another node are not collecting, sometimes only one. It seems to me that if the VoIP monitor has "X" number of paths collecting and yet it is not retrieving data for some of them it should alert us to that fact. Otherwise the only way to know is to check every chart path, every day... Not a likely scenario for most folks I would suspect.
Sometimes it recovers after a few hours or days, sometimes I notice first and shake things up by changing something about the site to cause it to refresh...
I think a "Refresh" button that would cause Orion to delete all the IP SLAs it had created for the node and then re-add them back would be good. It would be better if it figured it out on its own. Also if it is having trouble like this then a record of this should be logged somewhere so the problem can be logged, diagnosed, fixed, etc...
Just my observations and opinions though...
-Corey
Your Right Corey, that would be nice.
Ended up having to do all of our sites manually,