Comments
-
Good deal. Thanks for the update.
-
Good to hear!
-
Thanks for posting the screenshot, Byron! Glad you got it figured out. -Craig
-
Yes, but we can't commit to dates or timeframes. -Craig
-
You will be able to use those properties with IP SLA operations in IP SLA Manager once it's released.
-
Checking...
-
Lance, Someone will be contacting you offline. We'd definitely like to clear up and address any issues you had with the sales process. -Craig
-
Supporting JMX and better out-of-the-box monitoring for Java based apps is definitely something we'd like to implement in a future release. I'd like to hear more detail on your specific requirements, and will definitely reach out at some point in the near future. -Craig
-
Andy, We are considering a feature for a future release that will allow multiple values to be returned when running scripts or queries. No timeframes or dates we can commit to right now, but it's a very common request (especially in the scripting world) and is something we're currently looking at. -Craig
-
You can do this today. Each call path is its own VoIP UPD Jitter operation. You can specify a different latency threshold for each operation. HTH, Craig
-
Please open a support ticket and reference this thread. -Craig
-
njoylif, Thanks for opening a support ticket; that would've been my recommendation, as we'd like to take a look at your diagnostics. -Craig
-
The documentation is a little hard to find, but it's in the Online Admin Guide for NPM. You can find it here. HTH, Craig
-
Sure... IPv6 is definitely on the roadmap for Orion and all of its modules, but it won't be in the next IPAM release.
-
If you're currently on VoIP 2.1 and upgrade to IP SLA, no additional configs are necessary. In addition, all of your existing VoIP operations will remain in tact.
-
warbird, We made changes in 3.1 that now allow you to set the source IP for each operation vs. globally on the node as derhally described. You can do this for existing operations, as well as newly created ones. HTH, Craig
-
Thanks for the feedback, kahmeelyon... good stuff. We understand that this is not obvious, and are looking at how to make the process of setting the source IP a little easier in a future release. Question... would you ever need to set different source IP's for different operations on the same node? Currently you can set…
-
Seashore, Without seeing exactly how your nodes are interconnected, this sounds like a feasible scenario with IP SLA. The situation you're describing is packet loss from the perspective of A -> B, not from Orion -> A or Orion -> B. IP SLA was designed to be able to assess network quality from perspectives other than where…
-
A workaround would be suppressing the other operation alerts. For example, you have an alert for each operation on the device; suppress the other alerts when one fires. HTH, Craig
-
Jon, We checked and were unable to reproduce this internally. I would suggest opening a support ticket. They can help you troubleshoot your report, and if there is an issue then we can start tracking it. -Craig
-
Let me clarify. Nothing is off the table, and any potential future enhancements around VoIP will be based on demand from customers like yourself.
-
Thanks for the additional detail, menz. Just a couple of comments... first, we'll continue to focus on service quality as we develop IP SLA, which already addresses some of the things you've listed. It's not likely that we will implement anything around phone inventory. Also, you mention syslog and traps; this is something…
-
Glad to hear that helped. Jason is spot on... if you don't have SNMP set to v2 or v3, we won't show the device in the list.
-
sirpaw, If you wouldn't mind, please open a support ticket so we can track the issue. Thanks! Craig
-
Thanks, everyone! I will be reaching out to you individually offline. -Craig
-
We are fixing this in an upcoming release. -Craig
-
Got it. If I understand correctly, you want to be able to initiate a connection from the machine where the DameWare agent (what you're referring to as the client) is installed, and you want to do this through the command line. Did I get that right?
-
You should be able to ‘swipe’ the special keys area left and right to get to the arrow keys. Hope this helps.
-
mramos- We hear you. The Alert Manager is powerful in that you can build some pretty complex alert conditions. The downside to this flexibility is that it's basically a front end to building SQL queries, which requires some SQL knowledge. We definitely have an opportunity to make this easier to use. Thanks for the feedback.
-
Thanks for the feedback and suggestions. We will consider this for a future release.