What results do you get from a
snmpwalk <your host ip> -v1 -c <your read communityname>
.1.3.6.1.4.1.23.2.28.2.14.1 from your Zenoss server?
That *should* return something like this (from one of my cluster servers that
also has some traditional volumes for BorderMangler caching):
Code:
zen...@tcnm06l:~> snmpwalk xxx.xxx.xxx.xxx -v1 -c xxxxxxxx
.1.3.6.1.4.1.23.2.28.2.14.1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.2 = INTEGER: 2
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.3 = INTEGER: 3
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.4 = INTEGER: 4
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.5 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.249 = INTEGER: 249
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.250 = INTEGER: 250
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.251 = INTEGER: 251
SNMPv2-SMI::enterprises.23.2.28.2.14.1.1.254 = INTEGER: 254
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.1 = STRING: "SYS"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.2 = STRING: "_ADMIN"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.3 = STRING: "CACHE1"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.4 = STRING: "CACHE2"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.5 = STRING: "MGMT"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.249 = STRING: "SHARE"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.250 = STRING: "STUHOME"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.251 = STRING: "HOME"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.2.254 = STRING: "PWAY"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.1 = INTEGER: 28399560
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.2 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.3 = INTEGER: 3145648
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.4 = INTEGER: 3144704
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.5 = INTEGER: 10485760
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.249 = INTEGER: 209715200
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.250 = INTEGER: 10485760
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.251 = INTEGER: 209715200
SNMPv2-SMI::enterprises.23.2.28.2.14.1.3.254 = INTEGER: 52271656
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.1 = INTEGER: 23917252
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.2 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.3 = INTEGER: 3059872
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.4 = INTEGER: 3060976
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.5 = INTEGER: 8257596
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.249 = INTEGER: 32293900
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.250 = INTEGER: 4470292
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.251 = INTEGER: 27328656
SNMPv2-SMI::enterprises.23.2.28.2.14.1.4.254 = INTEGER: 25177200
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.1 = INTEGER: 46444
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.2 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.3 = INTEGER: 32
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.4 = INTEGER: 32
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.5 = INTEGER: 9804
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.249 = INTEGER: 16824956
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.250 = INTEGER: 1078068
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.251 = INTEGER: 59264188
SNMPv2-SMI::enterprises.23.2.28.2.14.1.5.254 = INTEGER: 932696
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.1 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.2 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.3 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.4 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.5 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.249 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.250 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.251 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.6.254 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.1 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.2 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.3 = INTEGER: 16384
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.4 = INTEGER: 16384
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.5 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.249 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.250 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.251 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.7.254 = INTEGER: 4096
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.1 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.2 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.3 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.4 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.5 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.249 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.250 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.251 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.8.254 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.1 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.2 = INTEGER: -2147483424
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.3 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.4 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.5 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.249 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.250 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.251 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.9.254 = INTEGER: -2147483456
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.1 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.2 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.3 = INTEGER: 17
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.4 = INTEGER: 17
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.5 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.249 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.250 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.251 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.10.254 = INTEGER: 23
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.1 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.2 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.3 = INTEGER: 12416
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.4 = INTEGER: 12416
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.5 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.249 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.250 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.251 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.11.254 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.1 = INTEGER: 73095
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.2 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.3 = INTEGER: 5208
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.4 = INTEGER: 4760
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.5 = INTEGER: 5851
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.249 = INTEGER: 312034
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.250 = INTEGER: 41868
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.251 = INTEGER: 738679
SNMPv2-SMI::enterprises.23.2.28.2.14.1.12.254 = INTEGER: 371881
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.1 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.2 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.3 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.4 = INTEGER: 1
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.5 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.249 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.250 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.251 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.13.254 = INTEGER: 0
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.1 = STRING:
".CN=TCPD01N_SYS.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.2 = STRING:
".CN=ADMIN_TCPD01N.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.3 = STRING:
".CN=TCPD01N_CACHE1.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.4 = STRING:
".CN=TCPD01N_CACHE2.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.5 = STRING:
".CN=TCPD01N_MGMT.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.249 = STRING:
".CN=TC-PDcluster1_SHARE.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.250 = STRING:
".CN=TC-PDcluster1_STUHOME.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.251 = STRING:
".CN=TC-PDcluster1_HOME.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.14.254 = STRING:
".CN=TC-PDcluster1_PWAY.OU=SRV.OU=TC.O=GISD.T=GISD-FP-TREE."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.1 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.2 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.3 = INTEGER: 3
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.4 = INTEGER: 3
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.5 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.249 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.250 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.251 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.15.254 = INTEGER: 5
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.1 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.2 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.3 = STRING: "NW 5 Traditional File
Sys."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.4 = STRING: "NW 5 Traditional File
Sys."
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.5 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.249 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.250 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.251 = STRING: "Novell NSS File System"
SNMPv2-SMI::enterprises.23.2.28.2.14.1.16.254 = STRING: "Novell NSS File System"
If that snmpwalk command doesn't return anything then the filesystem modeling
(and the performance collecting) will fail, because that's where we get the
entries from that we populate the OS tab/tables with in the NWFileSystemMap
plugin (and the performance data is calculated/pulled from too).
That would be the first thing I would troubleshoot.
Specifically the modeling plugin is pulling from:
'.1': 'nwVolId',
'.2': 'nwVolPhysicalName',
'.3': 'nwVolSize',
'.4': 'nwVolFree',
'.5': 'nwVolFreeable',
'.6': 'nwVolNonFreeable',
'.7': 'nwVolBlockSize',
'.8': 'nwVolMounted',
'.15': 'nwVolFileSystemID',
Actually all we really care about from the NetwareFileSystemMap is the .1, .2,
.3 and .15 (block size in the plugin is locked at 1024 so that the
computations work, since these tables report in bytes). The other entries
exist in the plugin but I wasn't able to make them work effectively in modeling
so they don't get written to any tables....someday I will get back to that, but
I haven't had the time since this one is working for me.
The Performance Collector script uses some of the same OID tables to calculate
UsedBlocks for Zenoss (since the Zenoss-provided code that is supposed to try
and do that itself didn't seem to work like I wanted, it kept multiplying the
results by 1024) - I took the NetWareFS_Get_usedBlocks shell script in /libexec
right from the code in the AIX ZenPack but it's against the NetWare OIDs.
Might check the permissions on the script to make sure that runs, or you can
test it directly from that path and pass it the three arguments and you should
get "standard" output with the totalBlocks and usedBlocks formatted how Zenoss
wants it :
NetWareFS_Get_usedBlocks <device ip> <read community string> <filesystem index>
Code:
#! /usr/bin/env bash
device=$1
community=$2
fs_index=$3
base_fs_table_oid=.1.3.6.1.4.1.23.2.28.2.14.1
totalBlocks_oid=$base_fs_table_oid.3.$fs_index
freeBlocks_oid=$base_fs_table_oid.4.$fs_index
output=`snmpget -v1 -c $community $device $totalBlocks_oid $freeBlocks_oid |
awk '{ print $NF; }'`
usedBlocks=`echo $output - p | /usr/bin/dc`
formatted=`echo $output | sed -e 's/ / freeBlocks:/'`
echo "totalBlocks:$formatted usedBlocks:$usedBlocks"
So you can see that snmpwalk against the device on the
.1.3.6.1.4.1.23.2.28.2.14.1 *has* to work for both the modeler and performance
collector or you won't get any data to work with.
As to what to troubleshoot on the NetWare server side if the snmpwalk doesn't
work:
1. Server's snmp config (I prefer to use INETCFG to set it) - community name
must be set unless you are using 'public' since that is the default
2. NMA agent must be loaded (SYS:\SYSTEM\NMA\NMA5.NCF command in AUTOEXEC.NCF
file...should be there by default from a base 6.5 install) - this is the
instrumentation that SNMP reads from and is required
3. MRTGEXT.NLM doesn't matter to this, all the filesystem work is done from
SNMP. MRTGEXT.NLM only kicks in for the OS statistics (since so much of what I
wanted to gather was exposed through that module and I didn't have to waste
lots of time walking SNMP).
Hope that helps some, the process itself isn't too complicated, it was the
trial and error of figuring out what the heck I was doing that made this
difficult. It made perfect sense once I put it together (I won't mention how
many weeks of headscratching were involved with this to get to that
point...lots of trial and error because I am not a programmer).
Oh yes, one note with NetWare clusters...Zenoss won't catch cluster resource
failovers/migrations until the next modeling attempt. I haven't even started
trying to figure out how to handle that (perhaps based on receiving a trap
event on a cluster node change forcing a remodel of the device/node? sounds
feasible anyway). I won't have time to try and figure that out for a while
though, summer patching/upgrades just kicked in here.
-Eric
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=35716#35716
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
