Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Operation Details in IP SLA 3.1 incorrect

The way I add IP SLA probes is by configuring them on the router then using IP SLA Manager to discover the operation by the number I input. I have noticed that under the Operation Details of the probe, the IP addresses don't match the source and target address in which I configured manually on the router. Instead, it appears that IP SLA manager shows the IP address it knows about within NPM.

The issue is that it is misleading for someone viewing the operation in IP SLA Manager because the source and destination listed is not actually the source and target configured for the probe.

Is this a bug?

Find more posts tagged with

Accepted answers

All comments

chris.smouse

I wouldn't necessarily call it a bug. Have you tried setting the source IP address for the operation? Once you set up the operation to monitor in IPSLA Manager, you can go to the Operations Management grid, edit the operation and set the Source IP address. That source IP address will then show as the source of the operation when you look at the details for that Operation.

Let us know if that helps you or not. Thanks!

dricha07

Yes I can set a source IP but not a destination. Therefore, the operation on the device is correct since I created it manually. The issue here is that IP SLA Manager doesn't look at what I configured the source and destination IPs to on the SLA probe on the device. Instead it just shows the IP address that Orion manages the devices from which isn't the same IPs the probes run between. For example, if I manage devices in Orion through the loopback but create a probe running between the WAN interfaces then Orion will show that the operation details is that I am running the probe through the loopback addresses. I know that it isn't since I manually configured the device's SLA probe. However, anyone looking at it in IP SLA Manager is misled into believing it is being sourced and targeted to the wrong interface.

The workaround you suggested doesn't work since I can't alter the destination IP. Either way, if IP SLA Manager has the ability for me to add the probe from a device then it should be able to detect the correct source and destination IP address.

FormerMember

funny, i was just looking at a similar thing... i am using Ip SLA to create probes, but if i create one incorrect, i might want to go in and change the destination as a test, but there does not seem to be a way to do it.....

any ideas? looks like something got missed on the design phase...

dricha07

From I can tell toilet, is that changing the IP address from within IP SLA Manager only changes what it displays within IP SLA Manager and not what is actually configured as the SLA probe on the device. It is misleading and well, useless. I would hope in the next version they fix this and allow you to define a destination IP.