Menu
▾
▴
Re: [Devmon] Can someone send the steps for adding a new device type and MIB to snmp & devmon?
|
From: Don K. <Don...@sc...> - 2013-01-25 17:45:01
|
Hi folks. I'm not getting emails from the list so I'm looking into that. So I apologize that this thread had answers (Ken, Jeremy, etc) but thanks for the replies.
I went directly to the message board and saw your responses. Here are the results to Jeremy's question about the snmpwalk:
[root@Systems_Monitor disk]# snmpwalk -v 2c -c public 10.1.xxx.xxx 1.3.6.1.4.1.24681.1.2.17.1
SNMPv2-SMI::enterprises.24681.1.2.17.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.24681.1.2.17.1.1.2 = INTEGER: 2
SNMPv2-SMI::enterprises.24681.1.2.17.1.2.1 = STRING: "[RAID5 Disk Volume: Drive 10 11 12]"
SNMPv2-SMI::enterprises.24681.1.2.17.1.2.2 = STRING: "[RAID6 Disk Volume: Drive 1 2 3 4 5 6 7 8 9]"
SNMPv2-SMI::enterprises.24681.1.2.17.1.3.1 = STRING: "EXT4"
SNMPv2-SMI::enterprises.24681.1.2.17.1.3.2 = STRING: "EXT4"
SNMPv2-SMI::enterprises.24681.1.2.17.1.4.1 = STRING: "3.61 TB"
SNMPv2-SMI::enterprises.24681.1.2.17.1.4.2 = STRING: "12.62 TB"
SNMPv2-SMI::enterprises.24681.1.2.17.1.5.1 = STRING: "3.01 TB"
SNMPv2-SMI::enterprises.24681.1.2.17.1.5.2 = STRING: "10.04 TB"
SNMPv2-SMI::enterprises.24681.1.2.17.1.6.1 = STRING: "Ready"
SNMPv2-SMI::enterprises.24681.1.2.17.1.6.2 = STRING: "Ready"
[root@Systems_Monitor disk]#
Don K
From: Don Kuhlman <don...@sc...<mailto:don...@sc...>>
Date: Thu, 24 Jan 2013 08:02:26 -0600
To: "Dev...@li...<mailto:Dev...@li...>" <Dev...@li...<mailto:Dev...@li...>>
Subject: RE: Can someone send the steps for adding a new device type and MIB to snmp & devmon?
Good morning. I'm adding my templates/disk values for this QNAP Nas device.
Not sure why I can't display the : branch values, but the : leaf values work by themselves.
Any tips would be appreciated.
Thanks
Don K
OIDS file:
VolName : .1.3.6.1.4.1.24681.1.2.17.1.2 : branch
VolFileSystem : .1.3.6.1.4.1.24681.1.2.17.1.3 : branch
VolSize : .1.3.6.1.2.1.24681.1.2.17.1.4 : branch
VolFree : .1.3.6.1.2.1.24681.1.2.17.1.5 : branch
VolStatus : .1.3.6.1.2.1.24681.1.2.17.1.6 : branch
OtherVol1Name : .1.3.6.1.4.1.24681.1.2.17.1.2.1 : leaf
OtherVol1FileSystem : .1.3.6.1.4.1.24681.1.2.17.1.3.1 : leaf
OtherVol1Size : .1.3.6.1.4.1.24681.1.2.17.1.4.1 : leaf
OtherVol1Free : .1.3.6.1.4.1.24681.1.2.17.1.5.1 : leaf
OtherVol1Status : .1.3.6.1.4.1.24681.1.2.17.1.6.1 : leaf
OtherVol2Name : .1.3.6.1.4.1.24681.1.2.17.1.2.2 : leaf
OtherVol2FileSystem : .1.3.6.1.4.1.24681.1.2.17.1.3.2 : leaf
OtherVol2Size : .1.3.6.1.4.1.24681.1.2.17.1.4.2 : leaf
OtherVol2Free : .1.3.6.1.4.1.24681.1.2.17.1.5.2 : leaf
OtherVol2Status : .1.3.6.1.4.1.24681.1.2.17.1.6.2 : leaf
MESSAGE file:
Volume Information
{OtherVol1Name}
{OtherVol1FileSystem}
{OtherVol1Size}
{OtherVol1Free}
{OtherVol1Status}
{OtherVol2Name}
{OtherVol2FileSystem}
{OtherVol2Size}
{OtherVol2Free}
{OtherVol2Status}
This piece doesn't work - it's giving the "missing repeater data for primary OID VolName"
TABLE:plain
Volume|Filesystem|Capacity|Available|Status
{VolName}|{VolFileSystem}|{VolSize}|{VolFree}|{VolStatus}
|
