For those of you that use tipping point ..you might find this probe
useful....
This is an updated version ...
<<com.mtv.snmp.tippingpoint.txt>>
<!--
Prototype Custom SNMP Probe (com.dartware.snmp.prototype)
Custom Probe for InterMapper (http://www.intermapper.com)
Please feel free to use this as a base for further development.
Original version 24 November 2003 by reb.
Updated 29 July 2005 -
Updated 28 Oct 2005 - include display_name so it displays properly in
InterMapper 4.4 -reb
updated 8/24 added tier 3 and more useful stats
-->
<header>
"type" = "custom-snmp"
"package" = "com.mtv"
"probe_name" = "snmp.tippingpoint"
"human_name" = "tipping point"
"version" = "1.0"
"address_type" = "IP,AT"
"port_number" = "161"
display_name = "tipping point"
</header>
<snmp-device-properties>
-- none required
</snmp-device-properties>
-- The <description> contains text that will be displayed in the probe
configuration window.
-- Describe the probe as much as necessary so that people will understand what
it does and how it works.
<description>
\GB\tipping point\P\
this probes monitors the tipping point health.
the tipping point 600 to 5000 are limited by tier 3 ..if this value hits 280 is
cause for concern.
maximun tier 3 is 300 megs
cpu reaches 90 be concerned packets may drop ..it will be a combination of tier
3 utilization and cpu.
it also monitors dropped packets due to tipping point congestion (mean tipping
point is dropping packets due to it cannot process them )
Pedro (el pingu)
</description>
-- Parameters are user-settable values that the probe uses for its comparisons.
-- Specify the default values here. The customer can change them and they will
be retained for each device.
<parameters>
"CPU Busy - Alarm" = "90"
"CPU Busy - Warning" = "75"
"tier3 - Alarm" = "280"
"tier3 - Warning" = "180"
</parameters>
<snmp-device-variables>
resourceHPCPUBusyPercent.0, 1.3.6.1.4.1.10734.3.3.2.5.4.1 , INTEGER, "The
percentage of host processor CPU busy."
memory, 1.3.6.1.4.1.10734.3.3.2.5.3.1 , INTEGER, "The
percentage of host processor memory in use."
critical-log, 1.3.6.1.4.1.10734.3.3.2.5.7.1 , INTEGER, "The
number of system log entries of type 'critical'."
policyPacketsBlocked, 1.3.6.1.4.1.10734.3.3.2.1.2.0 , PER-MINUTE,
"The cumulative number of packets blocked because of policy actions."
policyPacketsPermitted, 1.3.6.1.4.1.10734.3.3.2.1.7.0 ,
PER-MINUTE, "The cumulative number of packets permitted because of policy
actions."
policyPacketsIncoming,1.3.6.1.4.1.10734.3.3.2.1.3.0 , PER-MINUTE, " The total
number of incoming packets."
policyPacketsoutgoing,1.3.6.1.4.1.10734.3.3.2.1.4.0 , PER-MINUTE, " The total
number of outgoing packets."
resourceMetricFastpath,1.3.6.1.4.1.10734.3.3.2.5.8.1.0 , INTEGER, " Fast path
throughput in bits per second."
resourceMetricSmartpath, 1.3.6.1.4.1.10734.3.3.2.5.8.2.0 , INTEGER, " Smart
path throughput in bits per second."
resourceMetricCongestion, 1.3.6.1.4.1.10734.3.3.2.5.8.3.0 , INTEGER, "
Congestion count in packets.."
npstatsTiersReceiveMbps, 1.3.6.1.4.1.10734.3.3.2.10.2.1.2.1 , INTEGER, " The
current receive rate in Mbps. fastpath.."
npstatsTiersTransmitMbps, 1.3.6.1.4.1.10734.3.3.2.10.2.1.3.1 , INTEGER,
"The current transmit rate in Mbps.fastpath"
npstatsTiersReceiveMbps, 1.3.6.1.4.1.10734.3.3.2.10.2.1.2.3 , INTEGER,
"NP Tier Mbps Received (from fastpath to smartpath)"
npstatsTiersTransmitMbps, 1.3.6.1.4.1.10734.3.3.2.10.2.1.3.3 , INTEGER,
"NP Tier Mbps Transmitted (to fastpath to smartpath)"
totalppsin ,1.3.6.1.4.1.10734.3.3.2.1.3.0 , INTEGER, "Total packets per
second in to the IPS"
totalppsout ,1.3.6.1.4.1.10734.3.3.2.1.4.0 , INTEGER, "Total packets per
second out of the IPS"
packetsdrop , 1.3.6.1.4.1.10734.3.3.2.5.8.3.0 , INTEGER, "Number of packet
dropped due to Congestion"
</snmp-device-variables>
-- Specify rules for setting the device into Alarm or Warning state
<snmp-device-thresholds>
alarm: ${resourceHPCPUBusyPercent.0} > ${cpu Busy -
Alarm} "Critically high CPU utilization please check device"
warning: ${resourceHPCPUBusyPercent.0} > ${Cpu Busy -
Warning} "High cpu utilization"
alarm: ${npstatsTiersReceiveMbps} >
${tier3 - Alarm} "tier 3 abonormally high please check device"
warning: ${npstatsTiersReceiveMbps} >
${tier3 - Warning} "tier 3 above normal warning"
</snmp-device-thresholds>
-- The <snmp-device-display> section specifies the text that will be appended
-- to the device's Staus Window.
<snmp-device-display>
\B5\Prototype SNMP Probe\0P\
\4\cpu\0\ ${resourceHPCPUBusyPercent.0}
\4\memory\0\ ${memory} \3IG\(of last poll)\P0M\
\4\critical logs\0\ ${critical-log} \3IG\(of last poll)\P0M\
\4\policyPacketsBlocked\0\ ${policyPacketsBlocked} \3IG\(of last poll)\P0M\
\4\policyPacketsPermitted\0\ ${policyPacketsPermitted} \3IG\(of last poll)\P0M\
\4\policyPacketsIncoming\0\ ${policyPacketsIncoming} \3IG\(of last poll)\P0M\
\4\policyPacketsoutgoing\0\ ${policyPacketsoutgoing} \3IG\(of last poll)\P0M\
\4\resourceMetricFastpath\0\ ${resourceMetricFastpath} \3IG\(of last poll)\P0M\
\4\resourceMetricSmartpath\0\ ${resourceMetricSmartpath} \3IG\(of last
poll)\P0M\
\4\resourceMetricCongestion\0\ ${resourceMetricCongestion} \3IG\(of last
poll)\P0M\
\4\npstatsTiersReceiveMbps\0\ ${npstatsTiersReceiveMbps} \3IG\(of last
poll)\P0M\
\4\npstatsTiersTransmitMbps\0\ ${npstatsTiersTransmitMbps} \3IG\(of last
poll)\P0M\
\4\npstatsTiersReceiveMbps\0\ ${npstatsTiersReceiveMbps} \3IG\(of last
poll)\P0M\
\4\npstatsTiersTransmitMbps\0\ ${npstatsTiersTransmitMbps} \3IG\(of last
poll)\P0M\
\4\pps-in\0\ ${totalppsin} \3IG\(of last poll)\P0M\
\4\pps-out\0\ ${totalppsout} \3IG\(of last poll)\P0M\
\4\packetsdrop \0\ ${packetsdrop} \3IG\(of last poll)\P0M\
</snmp-device-display>
