Can you use syslog (via EMS) for those instead?
From: <toasters-bounces@teaparty.net> on behalf of "basilberntsen@gmail.com" <basilberntsen@gmail.com>
Date: Monday, June 22, 2015 at 3:01 PM
To: Steve Francis <sfrancis@logicmonitor.com>
Cc: "toasters@teaparty.net" <toasters@teaparty.net>
Subject: Re: snmp and cdot 8.3
We use snmp for environmental things like failovers, power events, hardware events, etc.
Sent from my BlackBerry 10 smartphone on the Bell network.
The CDOT MIB doesn't expose most of the things you care to monitor. 7-mode did, with the exception of things like volume or aggregate latency, but for CDOT, almost everything you want to know is only accessible via the API. Very little SNMP support.
On Mon, Jun 22, 2015 at 9:59 AM, Basil <basilberntsen@gmail.com> wrote:
There's a MIB file for the CDOT box, as well as one for oncommand unified manager. The one for CDOT is backward compatible to the 7-mode version- we have our 7-mode systems and CDOT systems using the same MIB file.
On Mon, Jun 22, 2015 at 12:51 PM, Jordan Slingerland <Jordan.Slingerland@independenthealth.com> wrote:
_______________________________________________In 7m you can find the mib in /etc/mib.
I do a lot of snmp monitoring of 7 mode but not cm. Here are some oid’s I use in 7m polling. (not trap based)
#Cp type oids
cpFromTimeroid=.1.3.6.1.4.1.789.1.2.6.2.0
cpFromSnapshotoid=.1.3.6.1.4.1.789.1.2.6.3.0
cpFromLowWateroid=.1.3.6.1.4.1.789.1.2.6.4.0
cpFromHighWateroid=.1.3.6.1.4.1.789.1.2.6.5.0
cpFromLogFulloid=.1.3.6.1.4.1.789.1.2.6.6.0
cpFromCpoid=.1.3.6.1.4.1.789.1.2.6.7.0
cpTotaloid=.1.3.6.1.4.1.789.1.2.6.8.0
cpFromFlushoid=.1.3.6.1.4.1.789.1.2.6.9.0
cpFromSyncoid=.1.3.6.1.4.1.789.1.2.6.10.0
#general performance
cpuidleoid=.1.3.6.1.4.1.789.1.2.1.5.0
cifsopsoid=.1.3.6.1.4.1.789.1.7.3.1.1.1.0
nfssopsoid=1.3.6.1.4.1.789.1.2.2.1.0
cifsreadsoid=.1.3.6.1.4.1.789.1.7.3.1.1.5.0
cifswritesoid=.1.3.6.1.4.1.789.1.7.3.1.1.6.0
#failed components
##should be zero
diskFailedCountoid=.1.3.6.1.4.1.789.1.6.4.7.0
envOverTemperatureoid=.1.3.6.1.4.1.789.1.2.4.1.0
failedFanCountoid=.1.3.6.1.4.1.789.1.2.4.2.0
failedPowerSupplyoid=.1.3.6.1.4.1.789.1.2.4.4.0
#system Status
##global status of 3 is normal
GlobalStatusoid=.1.3.6.1.4.1.789.1.2.2.4.0
##interconnect status of 4 is up
InterconnectStatusoid=.1.3.6.1.4.1.789.1.2.3.8.0
#partner status of 2 us okay
PartnerStatusoid=.1.3.6.1.4.1.789.1.2.3.4.0
#Failover state of 2 is good. Means ready to take over if needed, but active-active
FailoverStateoid=1.3.6.1.4.1.789.1.2.3.2.0
#nvram status of 1 means good
NvramBatteryStatusoid=.1.3.6.1.4.1.789.1.2.5.1.0
#ambient temp in C
ambienttmpoid=.1.3.6.1.4.1.789.1.21.1.2.1.25.1
##advanced NFS stats
nfsv3cRenamesoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.15.0
nfsv3cAccessesoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.5.0
nfsv3cCreatesoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.9.0
nfsv3cGetattrsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.2.0
nfsv3cLinksoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.16.0
nfsv3cLookupsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.4.0
nfsv3cMkdirsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.10.0
nfsv3cNullsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.1.0
nfsv3cReadCallsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.7.0
nfsv3cReaddirPlussoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.18.0
nfsv3cReadDirsoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.17.0
nfsv3cRemovesoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.13.0
nfsv3cSymlinksoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.11.0
nfsv3cWritesoid=.1.3.6.1.4.1.789.1.3.1.2.4.1.8.0
snapmirrorWrittenBytesoid=.1.3.6.1.4.1.789.1.9.10.0
snapmirrorReadBytesoid=.1.3.6.1.4.1.789.1.9.11.0
snapmirrorActiveDstNumberoid=.1.3.6.1.4.1.789.1.9.12.0
snapmirrorActiveSrcNumberoid=.1.3.6.1.4.1.789.1.9.13.0
snapmirrorFilerTotalDstSuccessesoid=.1.3.6.1.4.1.789.1.9.14.0
snapmirrorFilerTotalSrcSuccessesoid=.1.3.6.1.4.1.789.1.9.15.0
snapmirrorFilerTotalSrcFailuresoid=.1.3.6.1.4.1.789.1.9.16.0
snapmirrorFilerTotalDstFailuresoid=.1.3.6.1.4.1.789.1.9.17.0
snapmirrorFilerTotalDstDefermentsoid=.1.3.6.1.4.1.789.1.9.18.0
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Sayla, Mustafa
Sent: Monday, June 22, 2015 12:31 PM
To: toasters@teaparty.net
Subject: snmp and cdot 8.3
Anyone has experience with monitoring CDOT 8.3 with snmp? I have configured the CDOT system and configured SNMP trap host and community string yet we are not receiving traps. We were told by our third party vendor Solar Winds that netapp does not use standard snmp OID. We are not using snmp v3.
Mustafa Sayla
Visit us on the Web at mesirowfinancial.com
This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product.
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters
--
Steve Francis | Chief Product Officer
Cloud-based performance monitoring
