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

SAM 5.0 - SNMP Monitor Help

Hello,

I am evaluating SAM 5.0 and I am trying to get the SNMP monitor to work using OIDs that I currently use in NPM. I am using some of the most basic OIDs for HP disk drives and Dell DIMMs to test since I know they work in NPM. I must be doing something wrong - each test I do when I create the monitor comes back with "No Such Name".

Here's a snip of the current configuration for an HP disk OID:

SNMP Monitor.PNG

It's got to be something simple. The server tested works fine for the built-in hardware monitoring. Obviously I won't need to add a disk OID, but since I knew it worked in NMP and SAM this is what I wanted to test with. I get the same result when testing a working Dell DIMM OID against a Dell machine.

Thanks

Find more posts tagged with

Accepted answers

All comments

Petr.Vilem

Try adding ".0" i.e. use "1.3.6.1.4.1.232.3.2.5.1.1.6.0" instead of "1.3.6.1.4.1.232.3.2.5.1.1.6".

SNMP monitor behavior is more similar to snmpget command than snmpwalk (getnext).

mcbridea

I think 1.3.6.1.4.1.232.3.2.5.1.1.6 is the drive table. The table root (.0) may retrieve the table, as Petr suggests. If that does not work you will need to specify the drive index from the table.

LGentile

I did try .0 and had the same result. Here is the table and line data from a current query from NPM:

Are you saying i need to drill down to the row ID? You would think the functionality would be the same, the .6 is the lowest component i can get to, it's an element of the drive table.

Thanks for your assistance thus far.

Petr.Vilem

Yes, I believe that for example 1.3.6.1.4.1.232.3.2.5.1.1.6.2.0 should work and return 2 in your case.

mcbridea

It looks like that is working using .6 on UnDP. I scanned through support cases with a "No such name" error and it looks like that error is pretty generic. Can you open a ticket for this issue?

http://www.solarwinds.com/support/ticket/supportticket.aspx

LGentile

Well, Petr is right - when i put in the full OID down to the line number, it did return an 'up' status. Now i just need to figure out how to get the actual value.

If you think this is working as intended, then i suppose it is resolved. I am little concerned that it needs to be that specific vs. returning the table since NPM does it. I don't know for sure I will need this functionality right now, but I am testing for gaps and differences between the products. I can submit a ticket if you think I should - however this is a trial edition so i may not be able to get support on it. It's also version 5.0, not the current one. I would be happy to check out 5.1 though if i should be looking at that version instead. i see there's been a LOT of good fixes/updates.

Thank you,

lance

DONDERKA

I think that the problem is that SNMP Monitor is designed to get concrete OID not entire table. If the exact mach is not found the it returns error.

The monitor is looking for that particular OID. The OID (1.3.6.1.4.1.232.3.2.5.1.1.6) which you used before represent Physical Drive table but when you try create SNMP walk you will not found it there. In fact this OID exist only in definition MIB and will be never returned through the SNMP protocol. The reason why this OID works for you in NPM, UnDP and in SAM HH polling is that they all are going through the MIB tree and get every SNMP starting with 1.3.6.1.4.1.232.3.2.5.1.1.6 .