Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

To use TRAP or use UnDP for Adv Alert - which is best?

I have just rec'd a request to alert on a disk failure trap and can use some pointers getting started with TRAPS. I was expecting to use UnDP for this but perhaps using the trap is just as good.

Would the trigger be "currentStatusEvent"? and where are those potential values defined? do i get those from Dell?

thanks.

*****************************************************************************************

3/8/2009 9:25:00 PM 10.206.110.196 Myservername StorageManagement-MIB:storageManagementEvent.0.903 snmpTrapEnterprise = StorageManagement-MIB:storageManagementEvent

experimental.1057.1 = 10.206.110.196

previousStatusEvent = 4

currentStatusEvent = 4

objectNexusEvent = \0\0\0\3

objectOIDEvent = 1.3.6.1.4.1.674.10893.1.20.130.4.1.1.4

objectNameEvent = Physical Disk 0:0:3

locationEvent = Controller 0, Connector 0 descriptionEvent = SCSI sense data Sense key: 0 Sense code: 5D Sense qualifier: 2 messageIDEvent = 2095 snmpTrapOID = StorageManagement-MIB:storageManagementEvent.0.903

sysUpTime = 4 days 3 hours 55 minutes 24.13 seconds

*****************************************************************************************

3/8/2009 9:24:59 PM 10.206.110.196 Myservername StorageManagement-MIB:storageManagementEvent.0.903 snmpTrapEnterprise = StorageManagement-MIB:storageManagementEvent

experimental.1057.1 = 10.206.110.196

previousStatusEvent = 4

currentStatusEvent = 4

objectNexusEvent = \0\0\0\3

objectOIDEvent = 1.3.6.1.4.1.674.10893.1.20.130.4.1.1.4

objectNameEvent = Physical Disk 0:0:3

locationEvent = Controller 0, Connector 0 descriptionEvent = Predictive Failure reported messageIDEvent = 2094 snmpTrapOID = StorageManagement-MIB:storageManagementEvent.0.903

sysUpTime = 4 days 3 hours 55 minutes 23.10 seconds

Find more posts tagged with

traps_alerts

Accepted answers

All comments

Yann

Hi,

As per the StorageManagement-MIB:arrayDiskState OID (1.3.6.1.4.1.674.10893.1.20.130.4.1.1.4) here are the possible states:

The current condition of the array disk.
Possible states:
0: Unknown
1: Ready - Available for use , but no RAID configuration has been assigned.
2: Failed - Not operational.
3: Online - Operational. RAID configuration has been assigned.
4: Offline - The drive is not available to the RAID controller.
6: Degraded - Refers to a fault-tolerant array/virtual disk that has a failed disk.
7: Recovering - Refers to state of recovering from bad blocks on disks.
11: Removed - Indicates that array disk has been removed.
15: Resynching - Indicates one of the following types of disk operations: Transform Type , Reconfiguration , and Check Consistency.
24: Rebuild
25: No Media - CD-ROM or removable disk has no media.
26: Formatting - In the process of formatting.
28: Diagnostics - Diagnostics are running.
34: Predictive failure
35: Initializing: Applies only to virtual disks on PERC , PERC 2/SC , and PERC 2/DC controllers.
39: Foreign
40: Clear
41: Unsupported
53: Incompatible

I attached to the post an example about how you could configure the condition. I simply typed in the OID name.

Concerning which one between Traps and UnDP is the best. I would say UnDP is active monitoring and Traps passive. Both will work but I would need to compare pro and cons of both before to give you my personal opinion.

HTH,

Yann

trapcondition.JPG

lchance

Thanks Yann for the reply - that's helpful info and I appreciate it.

lchance

Yann,

I've set up both, Alerts for this SNMP TRAP and for Adv Alerts for the Custom Poller, and my notifications trigger on the SNMP TRAP but do not trigger off my Adv Alert.

I've moved my Adv Alerts down into Seconds, but still I'm not able to trigger on Custom Node Poller.

Any ideas how to troubleshoot this?

Thanks.

Yann

Could you post some details about the advanced alert you setup?

a screenshot of the Trigger condition would be great.

Thanks.

lchance

here's the ADV ALERT made for the Custom Poller (NODE) and NOTE: This NODE has an ongoing SNMP TRAP (see earlier entry) which comes in about once every 5 minutes.

And I've tried watching its Status value change using SNMP MIB Browser by refreshing the table, but never see it change from 3. But yet the TRAP always has the previous value of 4 (Offline) (See earlier entry in thread).

this is my first Adv Alert on a Custom Poller value changing, so i would very much like to see it work.