macnugetz Posted: Fri, Oct 23 2009 4:42 PM

rated by 0 users

Here is a quick look at some things we've got brewing for IP SLA Manager.

1. User Interface - we are working on simplifying the process of creating and managing IP SLA operations (things like being able to edit SNMP credentials, and being able to specify an external target for certain operations).
2. IP SLA Node Discovery - we are making it easier to discover and add IP SLA capable nodes.
3. More Operations - we are looking at adding support for RTP operations.  What other IP SLA operations would you like to see us support in the product?

What are your thoughts on these, and what else would you like to see in the product?  What are your use cases around IP SLA operations that the product doesn't currently address?  Thanks in advance for your feedback; we look forward to hearing from you!

Thanks!

-Craig

HankF replied on Sat, Oct 24 2009 11:59 PM

rated by 0 users

How about not requiring devices at both ends of a SLA probe to be managed in NPM?  I have a situation where I can not manage one end of a WAN link since it is part of a private network.  However, I can probe it (it is configured with rtr repsonder and will respond).  

The side I can manage will be actively probing the responder and would be under management in NMP.  I have a lot of devices that fall into this category.

Thanks -

markvl replied on Mon, Oct 26 2009 9:24 AM

rated by 0 users

I second the above request.

We manage servers on remote sites through VPN clouds, so we are unable to discover the routers on the path (except the last router in our own network).

We need to be able to have the test connect to a port on a server in order to report on any VPN issues.

Regards,
Mark

mikep1230 replied on Wed, Oct 28 2009 11:00 AM

rated by 0 users

This would be huge for us, too.  We have several of the above scenarios, plus SLA's monitoring more than one interface on a remote device.  I don't want to add each interface as a node.

HankF replied on Wed, Oct 28 2009 2:56 PM

rated by 0 users

One more request (not just for IP/SLA) would be to have all charts auto scale or at least have the option to be auto scaled.  It would also be desirable to change a charts type or the look of the chart.  I think you have the ability to do that in do that in the System Monitor (?) application now... not sure why you that ability isn't (a) in the Report Writer app and (b) not something you can do for all charts displayed in NPM. 

Thanks -

macnugetz replied on Wed, Oct 28 2009 6:04 PM

rated by 0 users

Good news; we are already working on this.  We have had many requests to be able to target a device outside of the WAN for certain IP SLA operations.

slinky103 replied on Thu, Nov 12 2009 4:31 PM

rated by 0 users

How about the ability to select what source interface the SLA traffic is sent from?

chris.smouse replied on Thu, Nov 12 2009 4:37 PM

rated by 0 users

slinky - see this thread.

You can specify the source IP address for a node in IPSLA Manager 3.0, which effectively specifies the source interface for the operation.  Is this what you're talking about?

slinky103 replied on Fri, Nov 13 2009 11:14 AM

rated by 0 users

Chris,

Yes it is.  I have not had a chance to play with this much since the upgrade.  Thank you!

dricha07 replied on Wed, Dec 16 2009 2:30 PM

rated by 0 users

One of the main reasons we moved from Cisco IPM to Orion SLA Manager was because VoIP Monitor could discover the SLA probes from a source router.  The new process with SLA Manager would very manual for us as we have ~1000 probes and it wouldn’t be realistic for us to get each index number.  I am not sure why the feature was taken out but could you provide more insight in the following:

1.    When is the functionality of discovering SLA probes on a source device going to be put back into the application?
2.    Is there any other way to import 1,000 probes easily since IP SLA Manager no longer can discover configured probes?

macnugetz replied on Wed, Dec 16 2009 3:01 PM

rated by 0 users

Dan,

Thanks for posting.  When we transitioned the product from the old VoIP Monitor to the new IP SLA Manager we attempted to ensure we didn't lose any functionality as well as make sure you didn't lose any of your configurations during the migration; obviously this is an area where we fell short.  That's the bad news.  The good news is we WILL be adding this functionality back in a future release. 

When we start working on this feature, I will definitely reach out and share our requirements with you to make sure we get it right.

-Craig

dricha07 replied on Wed, Dec 16 2009 3:25 PM

rated by 0 users

Also on another note during the upgrade from VoIP monitor to SLA Manager we noticed that if the nodes that were being managed in IP SLA didn't reside on the same Orion server as SLA Manager then the probes would fail after the upgrade.

It appears that the only way this new IP SLA Manager will work is if the devices are being managed on the same poller as the SLA Manager install.  With VoIP Manager, it didn't matter which poller the devices were being polled on.

We have multiple poller servers and it would be difficult to track which poller has what devices given the amount of SLA probes we have.  Are there any plans to make it so regardless of the polling engine, the SLA Manager can manage a device?

chris.smouse replied on Wed, Dec 16 2009 3:46 PM

rated by 0 users

Hi dricha07 -

What you describe here should not be the case.  If you have additional pollers with Orion installed, you should be able to install IPSLA Manager on the additional poller (an important step) and IPSLA Manager should have no trouble managing the devices from the additional poller.

dricha07 replied on Wed, Dec 16 2009 3:50 PM

rated by 0 users

Yes but wouldn't you have to purchase another SLA license for each poller?

With VoIP Monitor we purchased one license and we were able to manage SLA probes on any device regardless of which polling engine it was on.

Jason Ferree replied on Wed, Dec 16 2009 3:57 PM

rated by 0 users

You should not need a separate license for IP SLA manager when installing on an additional poller.  Use the same installer you used on your primary Orion NPM server.  It will not ask you for licensing information when installed on an additional server.

dricha07 replied on Wed, Dec 16 2009 3:59 PM

rated by 0 users

Great, I will give that a shot

sjweinstein replied on Tue, Jan 5 2010 8:09 PM

rated by 0 users

works as stated I have it insatlled on 5 pollers