Thanks, James. It does the job for me.
I also have the following 2 statements in the config of the switch:
snmp-server enable traps stackwise
snmp-server host X.X.X.X version 2c xxxxxx ( X.X.X.X is IP address of your
IM server and xxxxxx is your read only community string)
Intermapper is also enabled to accept traps on UDP port 162. (available in
Server Preferences/Server Setting/SNMP)
When the stack looses a switch, the icon for the switch stack turns 'dark
orange' with the little triangle with the ! in it indicating a problem.
On 4/12/07 11:33 AM, "Ashe, James P." <[EMAIL PROTECTED]> wrote:
> The (throw-together) probe I wrote for the 3750's work if the stack has
> 1 member or 9.
> Cut n' Paste n' Try. Suggestions welcome.
>
> <header>
> "type" = "custom-snmp"
> "package" = "edu.etsu"
> "probe_name" = "snmp.cisco3750"
> "human_name" = "Cisco Catalyst 3750"
> "version" = "1.0"
> "address_type" = "IP, AT"
> "port_number" = "161"
> </header>
>
> <snmp-device-properties>
> pdutype="get-request"
> </snmp-device-properties>
>
> <description>
> </description>
>
> <parameters>
> </parameters>
>
> <snmp-device-variables>
> module1, 1.3.6.1.4.1.9.5.1.3.1.1.10.1, Default, "module 1 status"
> module2, 1.3.6.1.4.1.9.5.1.3.1.1.10.2, Default, "module 2 status"
> module3, 1.3.6.1.4.1.9.5.1.3.1.1.10.3, Default, "module 3 status"
> module4, 1.3.6.1.4.1.9.5.1.3.1.1.10.4, Default, "module 4 status"
> module5, 1.3.6.1.4.1.9.5.1.3.1.1.10.5, Default, "module 5 status"
> module6, 1.3.6.1.4.1.9.5.1.3.1.1.10.6, Default, "module 6 status"
> module7, 1.3.6.1.4.1.9.5.1.3.1.1.10.7, Default, "module 7 status"
> module8, 1.3.6.1.4.1.9.5.1.3.1.1.10.8, Default, "module 8 status"
> module9, 1.3.6.1.4.1.9.5.1.3.1.1.10.9, Default, "module 9 status"
> stack1a, 1.3.6.1.2.1.2.2.1.8.5180, Default, "module 1, stackport 1
> status"
> stack1b, 1.3.6.1.2.1.2.2.1.8.5181, Default, "module 1, stackport 2
> status"
> stack2a, 1.3.6.1.2.1.2.2.1.8.5183, Default, "module 2, stackport 1
> status"
> stack2b, 1.3.6.1.2.1.2.2.1.8.5184, Default, "module 2, stackport 2
> status"
> stack3a, 1.3.6.1.2.1.2.2.1.8.5186, Default, "module 3, stackport 1
> status"
> stack3b, 1.3.6.1.2.1.2.2.1.8.5187, Default, "module 3, stackport 2
> status"
> stack4a, 1.3.6.1.2.1.2.2.1.8.5189, Default, "module 4, stackport 1
> status"
> stack4b, 1.3.6.1.2.1.2.2.1.8.5190, Default, "module 4, stackport 2
> status"
> stack5a, 1.3.6.1.2.1.2.2.1.8.5192, Default, "module 5, stackport 1
> status"
> stack5b, 1.3.6.1.2.1.2.2.1.8.5193, Default, "module 5, stackport 2
> status"
> stack6a, 1.3.6.1.2.1.2.2.1.8.5195, Default, "module 6, stackport 1
> status"
> stack6b, 1.3.6.1.2.1.2.2.1.8.5196, Default, "module 6, stackport 2
> status"
> stack7a, 1.3.6.1.2.1.2.2.1.8.5198, Default, "module 7, stackport 1
> status"
> stack7b, 1.3.6.1.2.1.2.2.1.8.5199, Default, "module 7, stackport 2
> status"
> stack8a, 1.3.6.1.2.1.2.2.1.8.5201, Default, "module 8, stackport 1
> status"
> stack8b, 1.3.6.1.2.1.2.2.1.8.5202, Default, "module 8, stackport 2
> status"
> stack9a, 1.3.6.1.2.1.2.2.1.8.5204, Default, "module 9, stackport 1
> status"
> stack9b, 1.3.6.1.2.1.2.2.1.8.5205, Default, "module 9, stackport 2
> status"
> </snmp-device-variables>
>
> <snmp-device-thresholds>
> Critical: ${module1} != 2 && "$module1" != "" "problem with stack module
> 1"
> Critical: ${module2} != 2 && "$module2" != "" "problem with stack module
> 2"
> Critical: ${module3} != 2 && "$module3" != "" "problem with stack module
> 3"
> Critical: ${module4} != 2 && "$module4" != "" "problem with stack module
> 4"
> Critical: ${module5} != 2 && "$module5" != "" "problem with stack module
> 5"
> Critical: ${module6} != 2 && "$module6" != "" "problem with stack module
> 6"
> Critical: ${module7} != 2 && "$module7" != "" "problem with stack module
> 7"
> Critical: ${module8} != 2 && "$module8" != "" "problem with stack module
> 8"
> Critical: ${module9} != 2 && "$module9" != "" "problem with stack module
> 9"
> Alarm : ${stack1a} != 1 && "$module2" != "" "problem with stack module
> 1 stackport"
> Alarm : ${stack1b} != 1 && "$module2" != "" "problem with stack module
> 1 stackport"
> Alarm : ${stack2a} != 1 && "$module2" != "" "problem with stack module
> 2 stackport"
> Alarm : ${stack2b} != 1 && "$module2" != "" "problem with stack module
> 2 stackport"
> Alarm : ${stack3a} != 1 && "$module3" != "" "problem with stack module
> 3 stackport"
> Alarm : ${stack3b} != 1 && "$module3" != "" "problem with stack module
> 3 stackport"
> Alarm : ${stack4a} != 1 && "$module4" != "" "problem with stack module
> 4 stackport"
> Alarm : ${stack4b} != 1 && "$module4" != "" "problem with stack module
> 4 stackport"
> Alarm : ${stack5a} != 1 && "$module5" != "" "problem with stack module
> 5 stackport"
> Alarm : ${stack5b} != 1 && "$module5" != "" "problem with stack module
> 5 stackport"
> Alarm : ${stack6a} != 1 && "$module6" != "" "problem with stack module
> 6 stackport"
> Alarm : ${stack6b} != 1 && "$module6" != "" "problem with stack module
> 6 stackport"
> Alarm : ${stack7a} != 1 && "$module7" != "" "problem with stack module
> 7 stackport"
> Alarm : ${stack7b} != 1 && "$module7" != "" "problem with stack module
> 7 stackport"
> Alarm : ${stack8a} != 1 && "$module8" != "" "problem with stack module
> 8 stackport"
> Alarm : ${stack8b} != 1 && "$module8" != "" "problem with stack module
> 8 stackport"
> Alarm : ${stack9a} != 1 && "$module9" != "" "problem with stack module
> 9 stackport"
> Alarm : ${stack9b} != 1 && "$module9" != "" "problem with stack module
> 9 stackport"
> </snmp-device-thresholds>
>
> <snmp-device-display>
> ___________________________
> module 1 : ${module1}
> module 1, stackport 1 : ${stack1a}
> module 1, stackport 2 : ${stack1b}
> module 2 : ${module2}
> module 2, stackport 1 : ${stack2a}
> module 2, stackport 2 : ${stack2b}
> module 3 : ${module3}
> module 3, stackport 1 : ${stack3a}
> module 3, stackport 2 : ${stack3b}
> module 4 : ${module4}
> module 4, stackport 1 : ${stack4a}
> module 4, stackport 2 : ${stack4b}
> module 5 : ${module5}
> module 5, stackport 1 : ${stack5a}
> module 5, stackport 2 : ${stack5b}
> module 6 : ${module6}
> module 6, stackport 1 : ${stack6a}
> module 6, stackport 2 : ${stack6b}
> module 7 : ${module7}
> module 7, stackport 1 : ${stack7a}
> module 7, stackport 2 : ${stack7b}
> module 8 : ${module8}
> module 8, stackport 1 : ${stack8a}
> module 8, stackport 2 : ${stack8b}
> module 9 : ${module9}
> module 9, stackport 1 : ${stack9a}
> module 9, stackport 2 : ${stack9b}
> ___________________________
> </snmp-device-display>
>
> __________________________
> James P. Ashe
> East Tennessee State University
> Office of Information Technology
> 4 2 3 * 4 3 9 * 4 6 4 8
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of Chris Romo
> Sent: Thursday, April 12, 2007 11:33 AM
> To: InterMapper Discussion
> Subject: Re: [IM-Talk] Has anyone used a probe to watch Cisco 3750
> switch stacks?
>
> Dave,
>
> Do you create different probes for each size stack to ensure the correct
>
> number of switches are monitored and prevent false alerts?
>
> Chris
>
>
>
>
> <[EMAIL PROTECTED]>
> Sent by: <[email protected]>
> 02/08/2007 09:57 AM
> Please respond to
> "InterMapper Discussion" <[email protected]>
>
>
> To
> <[email protected]>
> cc
>
> Subject
> Re: [IM-Talk] Has anyone used a probe to watch Cisco 3750 switch stacks?
>
>
>
>
>
>
>
> We do this - here is the key OID:
>
>
> Object moduleStatus
> OID 1.3.6.1.4.1.9.5.1.3.1.1.10
> Type INTEGER
> Permission read-only
> Status current
> Values
> 1 : other
> 2 : ok
> 3 : minorFault
> 4 : majorFault
>
> MIB CISCO-STACK-MIB ; - View Supporting Images
> Description The operational status of the module. If the
> status is not ok, the value of moduleTestResult
> gives more detailed information about the
> module's failure condition(s).
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 08, 2007 7:00 AM
> To: InterMapper Discussion
> Subject: InterMapper-Talk Digest - 02/08/07
>
> InterMapper-Talk Digest - Thursday, February 8, 2007
>
> Has anyone used a probe to watch Cisco 3750 switch stacks?
> by "Steven Good" <[EMAIL PROTECTED]>
> Re: [IM-Talk] Has anyone used a probe to watch Cisco 3750 switch
> stacks?
> by "Chip Old" <[EMAIL PROTECTED]>
> Re: [IM-Talk] Has anyone used a probe to watch Cisco 3750 switch
> stacks?
> by "Paul Worth" <[EMAIL PROTECTED]>
> RE: [IM-Talk] Has anyone used a probe to watch Cisco 3750 switch
> stacks?
> by "Steven Good" <[EMAIL PROTECTED]>
> ____________________________________________________________________
> List archives:
> http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> To unsubscribe: send email to: [EMAIL PROTECTED]
>
>
> ____________________________________________________________________
> List archives:
> http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> To unsubscribe: send email to: [EMAIL PROTECTED]
>
> ____________________________________________________________________
> List archives:
> http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> To unsubscribe: send email to: [EMAIL PROTECTED]
>
**********************************************
Daniel Albaugh
Senior Network Technician
Univ. of TN, Health Science Center
Memphis, TN
901.448.7044
[EMAIL PROTECTED]
**********************************************
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
