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

Only able to add 1 SLA node?

I am trying to track down a problem with the IP SLA Evaluation version. It seems I can only add 1 SLA node. I've tried removing the 1 previously added and it still will not add any of the others. Some of the nodes have different SNMP RW strings but I've tried adding nodes with the same string as the one I am able to add and it still fails.

What happens is I select a node to add, click "Add Nodes", and then it just sits there with the web page slightly grayed out. After a few minutes, it fails with no visible messages, the page goes 'bright' again, and that's it.

Is the evaluation version limited to only a single node being added? I've verified and re-verified SNMP strings. Where should I start looking to track this one down?

Find more posts tagged with

Accepted answers

JasonFerree

By chance, do you have more than one polling engine? If so, were these nodes possibly assigned to one of the other polling engines rather than the primary?

You can have this problem if those nodes were assigned to a poller other than the primary. When the nodes were removed and re-added, they were probably assigned to the primary and that is why they worked.

The fix would be to install IP SLA on your other polling engines.

All comments

mcbridea

Hi Warbird,

The eval version is good for unlimited nodes. Make sure the nodes are in Orion first then add them in IP SLAM. Let me know if this helps.

Andy

warbird

The nodes already exist in Orion. I will be working on this more this morning and will let you know if I figure anything else out.

If I cannot get it working, should I enter a ticket? Not certain how that is supposed to work with an Eval product?

warbird

Still not working. I can add the SLA node I originally had added when I first installed this product, but no other nodes. The nodes already exist in Orion. Doesn't matter what the SNMP string is, it fails in the same manner.

As a test, I changed the SNMP RW string stored in Orion for one of my SLA nodes to gibberish, then tried adding it in IP SLAM again. It fails in exactly the same way.

mcbridea

Please open a ticket and we'll help you get passed this.

warbird

My colleague discovered a work around. I had to delete the existing SLA node in Orion, readd it in Orion, then I was able to add it into IP SLAM. I believe this may be due to the fact we previously had custom pollers setup on these SLA nodes and something must have been conflicting with IP SLAM.

We are in the process of deleting/readding all of our SLA nodes in Orion, then we will proceed evaluating.

JasonFerree

By chance, do you have more than one polling engine? If so, were these nodes possibly assigned to one of the other polling engines rather than the primary?

The fix would be to install IP SLA on your other polling engines.

warbird

Interesting. Yes, I am currently running 2 engines and may eventually install a 3rd. Is this issue noted in the docs anywhere? I had been under the impression that the IP SLA module only had to be installed on the primary poller but would work with SLA nodes being polled by any of the pollers in our Orion instance.

NinjaNerd56

No...not in the docs that I could find.

I did Poller Balancing and moved the SLA targets to the Main NPM server where IP SLAM is running and viola!, everything runs like a dream.

Oh, one thing we overlooked in our process steps for your Cisco targets. (in our case, 2811 routers for VoiP use) We used IP SLAM to create the VoIP UDP Jitter Operations on the target routers with SNMP RW. Worked just fine and I had data and call path info in minutes.

BUT, we forgot to login to the routers and write the new running-config, containing the IP SLA Operations, to startup-config. So, when one of our stores had a power failure and rebooted the 2811, the Operation was no more.

So, we've added that process step to our rollout. Sometimes, it's the little things........

)

mcbridea

Ninja,

The IP SLA module should replace any operation that was created from IP SLAM. If it is not doing this for you, please open a ticket. The replacement should occur at the first polling cycle in which the missing operation is detected.

Andy

NinjaNerd56

Andy,

Actually, it does re-create at the Polling cycle, but in the meantime, a couple of Alerts are fired within the poll window; IP SLA Operation Down and VoIP Infrastructure Node Down since we're checking the voice stuff every minute for the Alerts.

Trying to avoid false alarms....

I could probably edit the Alerts to Suppress if "node rebooted" occurs, etc. I'll put that on my round-to-it list.

mcbridea

I see what you mean. Good idea to add suppression. I'm not sure but maybe try node down instead of node rebooted.