Nimble OS SNMP Reference Guide - Spiceworks Community

More documents

Recommendations

Info

14 | SNMP TrapsTraps and trap variablesSNMP trap variablesThe two variables that follow are included (bound) with traps/notifications.NameTypeIndexed (part of table)?DescriptionnimbleTrapCodeUnsigned32NoMessage numbernimbleTrapMsgUnsigned32NoMessage stringSNMP trapsAlthough commonly referred to as traps, these are actually SNMP v2 notifications.Traps are sent as part of event notification (along with email alerts, if they have been configured). Thefollowing trap categories represent various event notification categories. The specifics of each trap areput in variable bindings, represented by the nimbleTrapCode and nimbleTrapMsg variables.NamenimbleDataServiceTrapnimbleControllerTrapnimbleServiceTrapnimbleTestTrapnimbleSoftwareUpdateTrapnimbleDataServiceInteractionTrapnimbleVolAndSnapshotTrapnimbleVolumeCollectionTrapnimbleSystemSpaceTrapnimbleReplicationTrapnimbleHardwareTrapnimbleDiskTrapnimbleNicTrapnimbleEnvironmentalTrapnimbleRaidTrapnimbleConnectionTrapnimbleResourceLimitTrapDescriptionTraps related to general data services.Traps related to controller operation and status.Traps related to miscellaneous services.Traps related to the sending of test alerts and traps.Traps related to software updates.Traps related to interaction with the data service.Traps related to volumes and snapshots.Traps related to volume collections.Traps related to system space utilization.Traps related to replication.Traps related to general hardware.Traps related to disks.Traps related to NICs.Traps related to environmental components (sensors,temperature, NVRAM batteries, fans, power supplies).Traps related to RAID.Traps related to iSCSI connections.Traps related to system resource limits.
SNMP Traps | 15Event listThe Nimble array monitors system events and displays a message or sends an SNMP trap if these eventsoccur. Some events require immediate action, while others are informational. Alerts are grouped by type.General data serviceThe three alerts following refer to "free space." In this context, free space is disk space used by the system,not space used by volumes for data. The log-structured file system design of the Nimble array can showplenty of free space from the GUI or CLI (for volumes, snapshots, and clones), but have much less space towrite new data because space reclamation has not completed. In this case, a system could send out one ofthese alerts after snapshots and volumes have been deleted, but before the system finishes its update.Alert/EventSeverityDescription/Possible CauseNotes/Actions01010102010301040105010601070110warninginformationcriticalwarninginformationcriticalcriticalcriticalFree space is down to the stated level,write operations will be slowed.Free space has been reclaimed and hasreturned to the level shown. Writeoperations are back to normal speed.Free space is critically low, at the levelshown, and write operations will bedisabled.The system is currently nearing full.The space usage has been restored toless than the defined minimum warninglevel.The system has reached the criticalusage level.The system has only minimal spaceavailable for writing.The system has reached critically lowspace availability for writing.Delete unneeded snapshots or volumesto regain free space.Delete unneeded snapshots or volumesto regain free space or add capacity tothe array.Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.Application writes will be progressivelyslowed as space continues to decline.Application writes will time out.Controllers, HAAlert/EventSeverityDescription/Possible CauseNotes/Action2001criticalAn error occurred on the specifiedcontroller.A software error has occurred. ContactNimble support.2002informationA takeover occurred on the specifiedcontroller.The specified controller has assumedthe active role and is now supportingdata services. Check for failuresymptoms on the peer controller.2003informationThe standby controller specified isavailable.The array is running in a redundantcontroller configuration. No actionneeded.
Page 1 and 2: Nimble OS SNMP Reference GuideP/N 9
Page 3 and 4: Copyright noticesCopyright © 2010-
Page 5 and 6: Preface | 5Troubleshooting and othe
Page 7 and 8: SNMP Basics | 7Setting up SNMP on t
Page 9 and 10: SNMP Basics | 9For example, if a sy
Page 11 and 12: Nimble MIB | 11Volume Information t
Page 13: SNMP TrapsTopics:• Traps and trap
Page 17 and 18: SNMP Traps | 17Alert/EventSeverityD
Page 27 and 28: SNMP Traps | 27System management (A
Page 29: Index | 29IndexAACL events 15audien

Nimble OS SNMP Reference Guide - Spiceworks Community

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?