Dynamic Modeling, Instrumentation & SNMP v3

Hi Jamey,

I am new to dynmodel ... still in developing phase.

but a few questions that pop up to my mind ...

did you try a snmpwalk to that variable? do yo get a valid reply?
is snmpv3 supported by SMARTS&dynmodel?

cheers

F.

I am using the same MIB to pull DNS stats from a RedHat Linux box. We had a devil of a time getting it to work (2 hours) and prior to my involvement the customer has just given up on getting snmpd to work to pull net-snmpd stats. Here is what we did.

SMARTS - Implementing SNMP reporting for Bind 9 DNS (BT Diamond DNS) running on Redhat Linux 4.2.

Modify /etc/snmpd.conf file and uncomment what you want supported. Snmpd must be configured to start on the box. Uncomment the "exec /var/net-snmp/bind9.sh" and whatever else you need (read the included instructions at the link below from Neldon).

Warning the named.stats file is really in /var/named/chroot/var/log/named.stats So yours may vary. You will have to edit the bind9.sh file to point to whereever your stats file is kept. You run "rcnd stats" command then go find the named.stats file it wrote. That will tell you the location....then edit your bind9.sh file to reflect where the stats are truly being written. Yours might be /var/usr/log for example.

Use this command from a Smarts server to see if the DNS stats are answering up.
\incharge6\ip\smarts\bin\sm_snmpwalk.exe -c communityname -o .1.3.6.1.4.1.2021.8.1 143.166.83.13

Or locally on the linux box "snmpwalk -v 2 -c communityname -o .1.3.6.1.4.1.2021.8.1 143.166.83.13"

This is what you should get back from that command. .1.3.6.1.4.1.2021.8.1.1.1: 1
.1.3.6.1.4.1.2021.8.1.1.2: 2
.1.3.6.1.4.1.2021.8.1.2.1: bind9-ok
.1.3.6.1.4.1.2021.8.1.2.2: bind9-fail
.1.3.6.1.4.1.2021.8.1.3.1: /var/net-snmp/bind9.sh ok
.1.3.6.1.4.1.2021.8.1.3.2: /var/net-snmp/bind9.sh fail
.1.3.6.1.4.1.2021.8.1.100.1: 1
.1.3.6.1.4.1.2021.8.1.100.2: 0
.1.3.6.1.4.1.2021.8.1.101.1: 689744421
.1.3.6.1.4.1.2021.8.1.101.2: 146404139
.1.3.6.1.4.1.2021.8.1.102.1: 0
.1.3.6.1.4.1.2021.8.1.102.2: 0
.1.3.6.1.4.1.2021.8.1.103.1:
.1.3.6.1.4.1.2021.8.1.103.2:

Of course in your case you will just used OID .1.3.6.1.4.1.2021 to get all the net-snmp info back from your device. Or omit the oid altogether and it will return every feature on the device that snmpd knows about (mib2, net-snmp, etc)



-----Original Message-----
From: Neldon
Sent: Thursday, May 22, 2008 2:13 PM
To: Redwine, David
Subject: Emailing: bind9


The message is ready to be sent with the following file or link attachments:

Shortcut to: http://www.packetmischief.ca/network/monitoring/bind9/

I think your missing an instrumentation declaration for the SNMP variables you want to monitor.

For SNMP, an instrumentation
declaration connects the instrumented attributes to an SNMP object identifier (OID).
The SNMP accessor, the Domain Manager component that performs SNMP polling,
retrieves the value of the corresponding MIB variable and updates the value of the
instrumented attribute.
The Domain Manager automatically manages the interconnection between the SNMP
accessor, the monitoring system, and the subscription mechanism. As noted
previously, the Domain Manager only monitors for those attributes and events
necessary to diagnose the problems to which an EMC Smarts client has subscribed.

SEE PAGE 147 (SECTION 14-1) OF THE
EMC® Smarts® 7.0
MODEL Reference Guide
P/N 300-003-968
A01

This is just a hunch. I am trying to do a similar thing for DNS stats from net-snmp running on a Redhat linux box.

Sorry it is "rndc stats" , I misjumbled the letters.