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

IP SLA Responder without r/w?

Hi,

I'm currently evaluating the IP SLA Manager and am therefore not very knowledgeable on the product.

I have read access to our MPLS network provider's routers that are pre-configured with 'ip sla responder'. I do not have snmp write access to those routers however.

Is there any method to use these routers as IP SLA responders from our local Ciscos in Orion IP SLA Manager? If I don't have snmp write community I'm only able to configure a router in Orion NPM as 'External Node' and cannot use it in a bi-directional test path.

Thanks,

/Nils

Find more posts tagged with

ip_sla_responder

Accepted answers

ndufva

The problem was not within Orion, it was just that our lab server had been removed from the ACLs in the routers. I should have checked that earlier...

Sorry for bothering you!

Thank you,

/Nils

All comments

tom.rybka

If the routers are pre-configured already, then IPSLA Manager just verifies the configuration. RO credentials are sufficient for this process, only in case that the check fails, it tries to write the configuration which would obviously fail with RO.

Could you please describe in more details how it behaves when you use the internal IPSLA node with RO credentials as a target node?

ndufva

Hi,

As far as I remember, all nodes that I did'nt configure with a snmp write community appeared as 'unknown' and where not possible to import into the IPSLA Manager. Thus I cannot use them as responders. As I'm totally new to Orion tools, I have probably not understood the proper way of discovering new nodes. Will RTFM....

Thanks,

/Nils

ndufva

Now I have tested both to manually add routers and by performing Network Discovery. It seems like all nodes are detected as 'Unknown' unless I specify a snmp write community.

'Unknown' nodes cannot be added to IP SLA Manager. As Verizon's routers are detected as 'Unmanaged' I cannot use them as responders even though they are configured with 'ip sla monitor responder'. Verizon will not let me have the r/w community for their routers.

If someone have a solution to this I would be grateful!

/Nils

tom.rybka

You tested the scenario with RO credentials, and the nodes added to Orion or discovered by Orion are in Unknown state? They never come up? When you were adding the nodes (with the RO credentials), did the communication test passed or failed? And, only the status and statistics are not polled?

On the other hand, if you use RW credentials, the nodes become Up and everything works fine. I am asking just to make myself sure about your words...

You are right that the nodes need to be Up (i.e. running and managed) so that we can make a test that they are IPSLA capable when adding among IPSLA nodes.

Anyway, if it behaves with valid RO credentials as you described, something is wrong not only in IPSLA but in Orion generally, probably related to the connectivity to routers.