by Jeff Liebermann (email@example.com)
Latest version at: Jeff's site
1. Run: mkdev snmp 2. Edit: /etc/snmpd.conf This is mine. Do NOT change the descr and objid fields. descr=SCO TCP/IP Runtime Release 2.0.0 objid=SCO.188.8.131.52 contact=Jeff Liebermann location=Comix World Headquarters 3. Edit: /etc/snmpd.comm Comment out or remove any lines with WRITE permission. The default community name is "public". This is mine: # test1 0.0.0.0 READ # test2 127.0.0.1 WRITE public 0.0.0.0 READ Public is a password. If security is an issue, pick a different community name (password) and set the IP address for the local host (127.0.0.1) only as in: secret 127.0.0.1 READ so that only MIB browser running on the local machine can read SNMP parameters. Using the local machine IP address will also work. 4. Edit: /etc/snmpd.peers The SCO supplied configuration hostmib OID is wrong. (Actually, the OID is correct, but the MIB is compiled with the wrong OID. Therefore, the hostmib line must be tweaked to compensate. See the corrected hostmib OID line below. This is mine: # "unixd" 184.108.40.206.220.127.116.11.1.2 "aintNoThing" # "triald" 18.104.22.168.22.214.171.124.23.1 "aintNoThing" # "gated" 126.96.36.199.188.8.131.52.23.2 "aintNoThing" # "foosmuxd" 184.108.40.206.220.127.116.11.23.3 "mypasswd" "scoDoctorMIB" 18.104.22.168.22.214.171.124.1.1 "mypasswd" ####"hostmib" 126.96.36.199.188.8.131.52.1 "aintNoThing" "hostmib" 184.108.40.206.2.1.25 "aintNoThing" The first 4ea lines don't do anything. Only the last hostmib line is really necessary. Note the change in OID number. The SCO supplied ...32.99.1 is wrong. 5. Edit: /etc/snmpd.trap No traps should be set at this time. 6. Verify that SNMP is working with: getmany localhost public iso which belches everything in the tree. When the hostmib is grafted onto the tree, the list will grow substantially. 7. Run: mkdev hostmib Select install. Verify that the line: /etc/smuxtcl /etc/sysadm.d/hostmib.tcl is in the process table with: ps -ef | grep smux 8. Create a table of object names to mib numbers with: cd /etc/sysadm.d post_mosy -i hostmib.defs -o hostmib.dfn The hostmib.dfn file was missing from the SCO SNMP distributions and is required for the getone and getmany commands to belch descriptive names instead of cryptic numeric only OID's. 8. Shutdown and restart networking with: /etc/rc2.d/S89hostmib stop # stop smux hostmib ps -e | grep snmpd # get PID for snmpd 1176 ? 00:11 snmpd # typical ps -e output line ^^^^---PID kill -1 1176 # tell snmpd to re-read config files. /etc/rc2.d/S89hostmib start # restart smux hostmib 9. Test with: getone -f /etc/sysadm.d/hostmib.dfn sloth public mib-220.127.116.11.0 getone -f /etc/sysadm.d/hostmib.dfn sloth public 18.104.22.168.22.214.171.124.6.0 getmany -f /etc/sysadm.d/hostmib.dfn sloth public hrSystemProcesses getone -f /etc/sysadm.d/hostmib.dfn sloth public hrSystemProcesses.0 These should all identically return the number of processes currently being run. (Why doesn't smuxtcl program read the text definitions into memory like the RFC1155-SMI stuff?) Sloth is the name of my test machine. SNMP status is displayed with: /usr/bin/snmpstat -s sloth 10. Bugs: The SNMP "getmany" program has a bug in its inability to handle long OID's. My guess is that the super long NT OID's below are overrunning a fixed length buffer of insufficient length. The following was run on 3.2v4.2 with tcp/ip 1.2.1 with net382e. The exact same problem appears with getmany on 3.2v5.0.0, 3.2v5.0.2, and 3.2v5.0.4. The target machine (bloat) is an NT4.0 SP3 server. The equivalent mib walker command under Linux 2.0.30 (snmpwalk) from CMU_SNMP works fine so it's not NT that's causing this problem. According to "The Simple Book" by Marshall Rose, the maximum length for an OID is 128 fields which is far more than "getmany" will apparently tolerate. # getmany nt4server public iso (...trimmed...) Name: enterprises.126.96.36.199.188.8.131.52.184.108.40.206.220.127.116.11.18.104.22.168 .22.214.171.124.126.96.36.199.188.8.131.52.114.101 Value: Gateway Service for NetWare Name: enterprises.184.108.40.206.220.127.116.11.18.104.22.168.22.214.171.124.126.96.36.199 .188.8.131.52.184.108.40.206.220.127.116.11.18.104.22.168 Value: Remote Access Autodial Manager Memory fault(coredump) 11. For displaying SNMP derived values, I recomment MRTG (Mutli Router Traffic Grapher) at: https://www.ee-staff.ethz.ch/~oetiker/webtools/mrtg/mrtg.html It compiles and runs nicely under 3.2v4.2 and 3.2v5.0.x. There are numerous examples of the output all over the web.© Jeff Liebermann (firstname.lastname@example.org) All rights reserved
Got something to add? Send me email.
More Articles by Jeff Liebermann © 2009-11-07 Jeff Liebermann
The teaching of BASIC should be rated as a criminal offence: it mutilates the mind beyond recovery. (Edsger W. Dijkstra)