Difference between revisions of "TUT:DisMan Monitoring"
(link rfc) |
(→Defining the Query Credentials) |
||
| Line 7: | Line 7: | ||
== Getting Started == | == Getting Started == | ||
| − | === Defining the Query Credentials === | + | === Defining the Query Access Credentials === |
| + | |||
| + | The internal monitoring actually makes its internal queries through SNMP itself. Thus you need to "authorize" the service to actually browse the data from the agent. | ||
The first requirement is that you define a SNMPv3 username to use when performing self-management. First, we must define a user, add access control for it, and create it. '''PLEASE PICK A NAME DIFFERENT THAN ''myMonitorName'' and ''mysecretepassword''''', which is used below. Any name unique to your institution will work just fine. | The first requirement is that you define a SNMPv3 username to use when performing self-management. First, we must define a user, add access control for it, and create it. '''PLEASE PICK A NAME DIFFERENT THAN ''myMonitorName'' and ''mysecretepassword''''', which is used below. Any name unique to your institution will work just fine. | ||
Revision as of 23:47, 11 March 2011
The DisMan (Distributed Management) working group in the IETF produced RFC:2981, which defines a set of MIB tables describing an Event Management System. With this system employed, devices are able to monitor themselves and neighboring devices for problems and report the problems via SNMP notifications. This can greatly relieve the amount of traffic a network management station needs to send to every device on the network.
The snmpd.conf manual page describes this feature at length.
Because it's the most typical usage, the remainder of this page discusses self-management (the agent querying itself) as opposed to querying other external devices. This document also specifies how to perform self-management using snmpd.conf configuration directives. It is actually possible to completely configure an agent using SNMP SETs to the EVENT-MIB tables themselves.
Getting Started
Defining the Query Access Credentials
The internal monitoring actually makes its internal queries through SNMP itself. Thus you need to "authorize" the service to actually browse the data from the agent.
The first requirement is that you define a SNMPv3 username to use when performing self-management. First, we must define a user, add access control for it, and create it. PLEASE PICK A NAME DIFFERENT THAN myMonitorName and mysecretepassword, which is used below. Any name unique to your institution will work just fine.
createUser myMonitoringName SHA mysecretpassword AES rouser myMonitoringName iquerySecName myMonitoringName
