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

SNMP Disabled

We're trying to see how far we can get without SNMP. We're deploying in our DMZ and can't use SNMPv2 and don't want to add Net-SNMPv3.

So when you add a node in the 'ICMP only', the node is added with an 'unknown' status. So how can we get APM to learn whether its Windows, Linux or whatever?

Find more posts tagged with

Accepted answers

All comments

jiri.tomek

Hello Brent,
with "ICMP only" node status is determined by "ping" status.

APM can use other ways than SNMP to get application status of node. One is WMI. If you can use WMI, you can use APM quite well without SNMP. However you can't monitor Linux without SNMP except custom Linux scripts.

BrentPapworth

Hey Jiří,

Thanks for the quick reply -- yes, we've made considerable progress in our WMI only approach. We still have the following issue. When a Windows machine is added using the ICMP only mode, it is assigned in the node tree to an 'unknown' group. That is, it won't appear in the Cisco, Windows or APC groups. Instead, it appears in the Unknown group, apparently permanently. Subsequently assigning WMI templates does not change this status.

The only work-around I've figured out is to temporarily enable SNMP on the Windows machine, discover the Windows machine, then disable SNMP. However, this won't be possible in our production DMZ.

Any suggestions? Thanks in advance.

jiri.tomek

Hello Brent,

machine type resolution requires SNMP, you can't get this data without SNMP enabled.

What about enabling SNMPv2 and configure it so it would provide just machine type info and nothing else? Is this still too risky for your network?

BrentPapworth

Hey Jiří,

What about enabling SNMPv2 and configure it so it would provide just machine type....

That's a practical suggestion and one that we'll consider. The real problem is that we're a government agency, and any clear text protocol induces preemptive anxiety attacks among the security people who would approve such an approach in our DMZ.

The real villain here is Microsoft with their refusal to support an industry-standard, secure management protocol.

Anyway, thanks for the suggestion compadre -- Brent