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

RuggedCom SNMPV3 and Devices OTHER than Cisco using SNMPV3

SNMPV3 is the standard for my network, therefore I would like it to work with the many Ruggedcom devices that we have deployed.

I can get V2C to work...but not V3...

Ruggedcom devices support SNMPV3.

I called the Rugged Com tech support and confirmed that I was setting it up correctly and the engineer could not understand why it would not work...

I am trying to add an RS900 switch with no firewalls nor any ACLS restricting access to anything...

Has anyone gotten V3 to work with RuggedCom?

Also, I cannot for the life of me, get V3 to work with Adtran devices....in fact, the only devices that I can get to work with V3 are Cisco..

Find more posts tagged with

Accepted answers

All comments

MarieB

Phil--

If you don't hear back from the community soon, check out the SW Knowledgebase for more information.

If that doesn't help, open a support ticket. When you open a support ticket, would you:

--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.

Many thx,

Phil.Vansickle

I have a ticket in with the support desk....just wondering if anyone has run into similar issues and what they did if anything...

I have also forwarded this to the folks at Ruggedcom...

Subject: Case # 251274

Phil,

Going through the packet capture the issue is that the device is not responding back with the ContextEngineID. When we send the request to the device both the msgAuthoritativeEngineID and the ContextEngineID are missing, that is by design and their is no way to set that in NPM. We depend on the device to reply back with those fields filled in, so that we can reply back with the fields, which it does with the msgAuthoritativeEngineID but not with the ContextEngineID, it is still missing. I believe that issue is caused by how the views and groups are set up on the user Netman, but it may just be how that device uses SNMPv3. If it is a issue with the device and it just does not reply with that field then there is no way to add the device using SNMP v3 in NPM. Attached are some screenshots of what I am looking at in the packet capture to get that information.

Adrian Cook
Solarwinds Tech Support

Phil.Vansickle

I can't even get a Read/Write string in SNMP V1/V2c to work...all I can get is the read string to work....

AlexP

Hi Phil,

We would like to help you in getting this issue resolved. Could you please write back to support@ruggedcom.com refferencing you ticket number opened with us.

Same time feel free to provide any relevant data captures from RuggedCom device which you think could be relevant to the issue.

Thank you!