nimble os snmp reference guide - static.spiceworks.com · for example, if a system has 15 volumes...

Nimble OS SNMP Reference Guide

P/N 990-0207-001 09/13/11

Contents

Copyright notices..................................................................................................................3

Preface.................................................................................................................................4

SNMP Basics............................................................................................................6Setting up SNMP on the Nimble array......................................................................................7

IANA and OID numbers............................................................................................................8

Nimble MIB.............................................................................................................10Volume Information table........................................................................................................11

Global Stats table...................................................................................................................11

SNMP Traps............................................................................................................13Traps and trap variables.........................................................................................................14

Event list ................................................................................................................................15

Nimble SNMP FAQ.............................................................................................................28

ii | TOC

Copyright notices

Copyright © 2010-2011 Nimble Storage, Inc. All rights reserved worldwide.

No part of this document may be reproduced, stored in a retrieval system, or transmitted in any formor by electronic, mechanical, recording, photocopy, scanning or other means without prior writtenpermission from Nimble Storage, Inc.

The product described in this documentation may be protected by one or more U.S. patents or pendingpatent applications.

Nimble Storage, Incorporated ("Nimble"), has used the best and latest information available in producingthis document. Nimble makes no warranty, expressed or implied, with regard to accuracy andcompleteness.

All brand names and product names mentioned in this document are trademarks of their respectiveowners.Where known, trademarked, registered trademarks, and service marks are designated as such.

Nimble Storage, Inc.2645 Zanker RoadSan Jose, CA 95134

Tel: +1 408.432.9600Web: www.nimblestorage.comEmail: [email protected]

http://www.nimblestorage.com

mailto:[email protected]

Preface

The Nimble array scales to multiple terbytes of storage capacity, is simple to install and deploy, and isdesigned to ensure data availability and integrity in the face of failures.

This guide gives you information about the concepts, references, and procedures necessary to installand manage the system. Many parts of the Nimble array are self-explanatory and need no furtherdiscussion.

Audience assumptionsThis document is for administrators and evaluators. It is based on certain assumptions. The Nimblearray was designed to be as intuitive and easy to use as possible: you do not need extensive trainingin network or SAN management to manage its day-to-day use. However, you should understand:

• basic networking• your network environment• snapshots and replication tasks• your system usage trends• the requirements and configuration specific to your applications

Conventions used in this documentThroughout the documentation, the following conventions are used:

It means:If you see:

the actual text to type. If text appears in italic in this area, replace the italicizedtext with the information it indicates. Usually shows a command, path,parameter, or URL

fixed width

a tab on the GUI or emphasis on the textitalics

select the first option named, followed by the secondA > B

example output is shown with a slightly shaded backgroundexamples

a field name, button, or other unspecified component of the UIbold

The CLI icon provides the basic method for a procedure using the command line. For completedetails about the commands, see the Nimble OS Command Line Reference Guide.

The GUI icon indicates that the method that follows is performed using the GUI.

Accessing informationInformation that addresses individual areas of the array is logically grouped in the general order of use.Each chapter and section discusses an aspect of array management. Some aspects of array managementoverlap or affect multiple areas of administration. In those cases, the information is located where it willmost likely be used. Use the Table of Contents, index, and search feature to find specific information.

A fully integrated online help system is available through the use of tool tips and information icons.Select Help > User Guide to see the online version of the user documentation. Wherever you see theInformation icon ( ), hover over the icon for more information.

4 | Preface

Troubleshooting and other help is available from the Nimble Storage support site atwww.nimblestorage.com/support or you can email support at [email protected] needto have a username and password to access the Support site. This should have been sent to you byemail when the array was shipped. If you did not receive this information, contact technical support byemail.

Screen shots and information fieldsAll screen shots, fields, and parameters shown in this document were accurate at the time the documentwas produced. As enhancements are added in newer releases, they may differ slightly from what yousee on your screen.

Preface | 5

http://www.nimblestorage.com/support.html

mailto://[email protected]

SNMP Basics

Nimble Storage software provides an SNMP option for monitoringNimble arrays.You should be familiar with Simple Network

Topics:

• Setting up SNMP on the Nimblearray

Management Protocol (SNMP) before enabling SNMP monitoring.RFC1155 is a good place to start if you are not familiar with SNMPand MIBs.• IANA and OID numbers

On each array, an SNMP agent provides information about thenetwork configuration and operations. These SNMP objects arestored in a Management Information Base (MIB). The MIB is avirtual database by the IETF/IEEE as well as device providers likeNimble to ensure a standard method to view network managementinformation on devices from different vendors.

Nimble Storage provides a Nimble array-specific MIB. The NimbleMIB can be downloaded from the Nimble Support site.

6 | SNMP Basics

http://tools.ietf.org/html/rfc1155

Setting up SNMP on the Nimble arrayThe Nimble array uses SNMP to communicate with network management systems. Configure the SNMPsettings from the Administration menu.

The Nimble array supports SNMP versions 1, 2, and 2c. The device sends traps but does not receivethem.You can download the Nimble SNMP MIB from the Nimble Support site.

Note: The array uses the alert level settings for email alerts to determine which events are sent as SNMPtraps.

SNMP gets information to the network in one of two ways. In the first method, shown as 1 in the diagram,is when the network management system sends a request to get information and in turn receives aresponse. In the second method, shown as 2,the traps are sent automatically, based on trap levelsettings.

You can set SNMP configuration using the CLI command array --snmp_trap_host and to set theSNMP trap destination, use array --snmp_trap_dest.

To configure SNMP using the GUI:

1. From the main menu, choose Administration > SNMP.

SNMP Basics | 7

2. Ensure that the Enable SNMP Get box is checked.

3. Enter the community string and SNMP port.

By default, public is used along with the port 161. The community string is essentially a password sharedbetween the client and server (network management system). The community string can be up to 64alphanumeric characters, and can contain a hyphen, colon, or period, but only alphanumerics are allowedto begin the string. Contact Technical Support before changing the community string.

4. If you choose not to use the default SNMP Get port (161), enter a different port for SNMP Get.

5. Ensure that the Enable SNMP Trap box is checked.

6. Enter the trap destination.This is the hostname of the network management system to which SNMP trapsare sent. Enter a host name or fully qualified domain name.

7. If you choose not to use the default SNMP Trap destination port (162), enter a different port to use.

8. Click Save to save the settings.

IANA and OID numbers

The Internet Assigned Numbers Authority (IANA) number assigned to Nimble Storage is 37447: everythingin the Nimble MIB is under the OID

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).nimble(37447)

Wherever you see references to variable names, you can find the corresponding OID numbers in thefollowing section. For details about IANA, visit www.iana.org.

OIDsThe following shows the OID numbers for the variables, tables, and traps in the MIB. The indentationsshow the level for each item.

Indexed table entries in SNMP, such as those in the volTable, are accessed by appending the indexnumber after the OID of the entry desired.

8 | SNMP Basics

For example, if a system has 15 volumes (indicated by the variable volNumberOfVolumes value of15), the name of the 8th volume is obtained by polling (performing an SNMP GET operation) on the OID1.3.6.1.4.1.37447.1.2.1.3.8.

(1) iso (3) org (6) dod (1) internet (4) private (1) enterprises (37447) nimble (1) nimbleVariables (1) volNumberOfVolumes (2) volTable (1) volEntry (1) volIndex (2) volID (3) volName (4) volSizeLow (5) volSizeHigh (6) volUsageLow (7) volUsageHigh (8) volReserveLow (9) volReserveHigh (10) volOnline (11) volNumConnections (3) nimbleGlobalStats (1) statTimeEpochSeconds (2) ioReads (3) ioSeqReads (4) ioWrites (5) ioSeqWrites (6) ioReadTimeMicrosec (7) ioWriteTimeMicrosec (8) ioReadBytes (9) ioSeqReadBytes (10) ioWriteBytes (11) ioSeqWriteBytes (12) diskVolBytesUsedLow (13) diskVolBytesUsedHigh (14) diskSnapBytesUsedLow (15) diskSnapBytesUsedHigh (16) ioNonseqReadHits

SNMP Basics | 9

Nimble MIB

The following entries are provided with the Nimble MIB.Topics:

• Volume Information table• Global Stats table

10 | Nimble MIB

Volume Information table

OverviewWhen network management protocols use names of MIB variables in messages, each name has anappended suffix. This suffix is called an instance identifier. For simple variables, the instance identifier0 refers to the instance of the variable with that name. A MIB also can contain tables of related variables.

Typically, an instance identifier might be a unique interface number or a 0. An instance identifier canalso be an IP address. For example, to find the network mask for the route with a destination addressof 131.104.211.243, use the variable locRtMask (locate route mask) with an instance identifier of131.104.211.243. The format is locRtMask. 131.104.211.243.

Volume Info Table

DescriptionIndexed (part of table)?TypeName

Number of volumes.NoUnsigned32volNumberOfVolumes

Volume index.YesUnsigned32volIndex

Volume ID.YesUnsigned32volID

Volume name.YesDisplayStringvolName

Max. size in bytes (loworder bytes).

YesUnsigned32volSizeLow

Max. size in bytes (highorder bytes).

YesUnsigned32volSizeHigh

Usage in bytes (loworder bytes).

YesUnsigned32volUsageLow

Usage in bytes (highorder bytes).

YesUnsigned32volUsageHigh

Reserved bytes (loworder bytes).

YesUnsigned32volReserveLow

Reserved bytes (highorder bytes).

YesUnsigned32volReserveHigh

Volume online (true orfalse).

YesTruthValuevolOnline

Number of connectionsto the volume.

YesUnsigned32volNumConnections

Global Stats table

The below variables store various global statistics. They are not updated realtime, but at periodicintervals. The variable statTimeEpochSeconds indicates the UNIX timestamp (in number of secondssince UNIX epoch) at which the current reading was taken.

To determine a delta value between two time periods, take one reading and note the timestamp andvalue desired.Then, take a later reading. If the statistics have been updated in the interim, the timestamp

Nimble MIB | 11

for the second reading will be higher, and the delta can be computed between the number of secondsin between readings and the difference in the statistic values.


UNIX time (number of secondssince the UNIX epoch) when statswere recorded.

NoCounter64statTimeEpochSeconds

Total cumulative number of ReadI/Os (sequential and random).

NoCounter64ioReads

Total cumulative number ofSequential Read I/Os.

NoCounter64ioSeqReads

Total cumulative number of WriteI/Os (sequential and random).

NoCounter64ioWrites

Total cumulative number ofSequential Write I/Os.

NoCounter64ioSeqWrites

Total cumulative microseconds thesystem has spent processingRead I/Os.

NoCounter64ioReadTimeMicrosec

Total cumulative microseconds thesystem has spent processing WriteI/Os.

NoCounter64ioWriteTimeMicrosec

Total cumulative number of ReadI/O bytes (sequential and random).

NoCounter64ioReadBytes

Total cumulative number ofSequential Read I/O bytes.

NoCounter64ioSeqReadBytes

Total cumulative number of WriteI/O bytes (sequential and random).

NoCounter64ioWriteBytes

Total cumulative number ofSequential Write I/O bytes.

NoCounter64ioSeqWriteBytes

Total number of bytes used ondisk for volumes (low order bytes).

NoUnsigned32diskVolBytesUsedLow

Total number of bytes used ondisk for volumes (high orderbytes).

NoUnsigned32diskVolBytesUsedHigh

Total number of bytes used ondisk for snapshots (low orderbytes).

NoUnsigned32diskSnapBytesUsedLow

Total number of bytes used ondisk for snapshots (high orderbytes).

NoUnsigned32diskSnapBytesUsedHigh

Total cumulative number of cachehits for Non-Sequential Read I/Os.

NoCounter64ioNonseqReadHits

12 | Nimble MIB

SNMP Traps

All alerts that can be sent via email to administrators can be sentas SNMP traps.

Topics:

• Traps and trap variables• Event list

Traps and trap variables

SNMP trap variablesThe two variables that follow are included (bound) with traps/notifications.


Message numberNoUnsigned32nimbleTrapCode

Message stringNoUnsigned32nimbleTrapMsg

SNMP 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.

DescriptionName

Traps related to general data services.nimbleDataServiceTrap

Traps related to controller operation and status.nimbleControllerTrap

Traps related to miscellaneous services.nimbleServiceTrap

Traps related to the sending of test alerts and traps.nimbleTestTrap

Traps related to software updates.nimbleSoftwareUpdateTrap

Traps related to interaction with the data service.nimbleDataServiceInteractionTrap

Traps related to volumes and snapshots.nimbleVolAndSnapshotTrap

Traps related to volume collections.nimbleVolumeCollectionTrap

Traps related to system space utilization.nimbleSystemSpaceTrap

Traps related to replication.nimbleReplicationTrap

Traps related to general hardware.nimbleHardwareTrap

Traps related to disks.nimbleDiskTrap

Traps related to NICs.nimbleNicTrap

Traps related to environmental components (sensors,temperature, NVRAM batteries, fans, power supplies).

nimbleEnvironmentalTrap

Traps related to RAID.nimbleRaidTrap

Traps related to iSCSI connections.nimbleConnectionTrap

Traps related to system resource limits.nimbleResourceLimitTrap

14 | SNMP Traps

Event 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.

Notes/ActionsDescription/Possible CauseSeverityAlert/Event

Delete unneeded snapshots or volumesto regain free space.

Free space is down to the stated level,write operations will be slowed.

warning0101

Free space has been reclaimed and hasreturned to the level shown. Writeoperations are back to normal speed.

information0102

Delete unneeded snapshots or volumesto regain free space or add capacity tothe array.

Free space is critically low, at the levelshown, and write operations will bedisabled.

critical0103

Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.

The system is currently nearing full.warning0104

The space usage has been restored toless than the defined minimum warninglevel.

information0105

Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.

The system has reached the criticalusage level.

critical0106

Application writes will be progressivelyslowed as space continues to decline.

The system has only minimal spaceavailable for writing.

critical0107

Application writes will time out.The system has reached critically lowspace availability for writing.

critical0110

Controllers, HANotes/ActionDescription/Possible CauseSeverityAlert/Event

A software error has occurred. ContactNimble support.

An error occurred on the specifiedcontroller.

critical2001

The specified controller has assumedthe active role and is now supporting

A takeover occurred on the specifiedcontroller.

information2002

data services. Check for failuresymptoms on the peer controller.

The array is running in a redundantcontroller configuration. No actionneeded.

The standby controller specified isavailable.

information2003

SNMP Traps | 15

Notes/ActionDescription/Possible CauseSeverityAlert/Event

This could be caused by successivepower failures or persistent controller

Excessive restarts on the specifiedcontroller were detected. The specified

critical2005

hardware or software issues. Thecontroller detected repeated failures ina short period of time. controller will not attempt to start data

services and will remain in this state inorder to provide a stable environmentfor support personnel to diagnose theissue. Attempts to manually restart thecontroller once in this state can fail forup to 30 minutes.

After the controller restart, verify that theservice has restarted.

The specified controller is beingrestarted in order to recover the statedservice.

critical2006

The array received a request from theadministrator to reboot the specifiedcontroller.

information2007

Contact Nimble support.The array was not able to complete therequest to reboot the controller.

warning2008

The array received a request from theadministrator to halt the specifiedcontroller.

information2009

Contact Nimble support.The array was not able to complete therequest to halt the controller.

warning2010

A software error occurred while in aredundant controller configuration.Contact Nimble support.

An error occurred on the specifiedcontroller.

warning2013

A software error occurred while in anon-redundant controller configuration.Contact Nimble support.

An error occurred on the specifiedcontroller and all services have stopped.

critical2014

The array is not running in a redundantcontroller configuration. Check for failuresymptoms on the peer controller.

The standby controller has not beenavailable for the amount of time shown.

warning2015

ServicesNotes/ActionDescription/Possible CauseSeverityAlert/Event

The system services were started, andthe system shows the currently installedsoftware version.

information2101

The specified service is unable to runreliably and is being shut down. ContactNimble support.

The specified service has stoppedunexpectedly but is not restartingautomatically.

warning2103

A secure tunnel was created on thespecified controller to allow NimbleStorage support personnel access.

information2104

16 | SNMP Traps


The secure tunnel to Nimble Storagesupport has been terminated.

information2105

Test messagesThese messages appear when an alert --test command has been issued from the CLI.


No action needs to be taken.A test command has triggered aninformation-level alert.

information5001

No action needs to be taken.A test command has triggered anerror-level alert.

error5002

No action needs to be taken.A test has been triggered for anote-level alert. (Deprecated)

note5004

No action needs to be taken.A test command has triggered awarning-level alert.

warning5005

No action needs to be taken.A test command has triggered acritical-level alert.

critical5006

Software updateNotes/ActionDescription/Possible CauseSeverityAlert/Event

Verify that the software version iscompatible, and retry or redownload. Ifthe problem persists, contact Support.

The system failed to unpack thesoftware update package on thespecified controller.

warning6000

The system has begun the softwareupdate to the specified version.

information6001

Verify that the software version iscompatible, and retry or redownload. Ifthe problem persists, contact Support.

The system is reverting the software tothe previous version.

warning6002

The software update was successful onthe specified controller.

information6003

The system is rolling back the softwareto the specified version.

information6004

Retry the download. If the problempersists, contact Support.

The precheck failed on the updatepackage.

warning6005

Contact Support.Precheck failed because the file systemis out of space.

warning6007

Check standby controller network links,switches links, and retry softwareupdate.

Precheck failed indicating that networkconnectivity will degrade after thesoftware update.

The system is unpacking the specifiedupdate package on the namedcontroller.

information6008

SNMP Traps | 17


The unpacking process has completedon the software update package.

information6009

To complete a software update, thesystem is rebooting the specifiedcontroller.

information6010

Make sure the network connections areactive and retry.

Failed to download software updatepackage.

warning6011

Schedule to reboot the target controller(by pulling it out and pushing it in)

The software update failed because the"/tmp" directory is full.

warning6012

Contact Support.The software update failed because thescratch space is full.

warning6013

Contact Support.The software update failed because the"/var" directory is full.

warning6014

Contact Support.The software update failed because theconfiguration space is full.

warning6015

Contact Support.The software update failed because theRecovery OS space is full.

warning6016

Download the package again and retrythe update.

The software update package was notfound.

warning6017

Make sure that your firewall doesn'tchange the update package. Retry to

The software update package has thewrong signature.

warning6018

download or upload. If upload is used,make sure that the uploaded packageis a Nimble update package.

Retry the download. If upload is used,make sure that the update package isnot corrupted.

The software update package has thewrong checksum.

warning6019

Check network connectivity on thestandby controller.

The software update precheck failed.Network connectivity will degrade aftersoftware update is complete.

warning6020

Bring the other controller back tostandby mode.

The software update failed because onlyone controller is available.

warning6021

GeneralNotes/ActionsDescription/Possible CauseSeverityAlert/Event

Cache was cleared by the administrator(using the CLI).

information10101

Volumes, snapshots, and clonesNotes/ActionsDescription/Possible CauseSeverityAlert/Event

Add more space to the volume, or resetthe warning limit.

The space usage of the specifiedvolume is over the configured warninglimit.

warning10200

18 | SNMP Traps


The space usage of the specifiedvolume has returned to below theconfigured warning limit.

information10201

Extend the quota limit or add morespace to the volume.

The space usage of the specifiedvolume is over the configured quota.

warning10202

The space usage of the specifiedvolume has returned to below theconfigured quota.

information10203

Add more space or reset the warninglimit.

The snapshot space usage on thespecified volume is over the configuredwarning limit.

warning10204

The snapshot space usage on thespecified volume has returned to belowthe configured warning limit.

information10205

Add more space or reset the snapshotquota.

The snapshot space usage on thespecified volume is over the configuredquota.

error10206

The snapshot space usage on thespecified volume has returned to belowthe configured quota.

information10207

The system will automatically retrysynchronization.

Volume attribute synchronization hasbeen delayed.

warning10208

If usage exceeds the quota, the volumewill be taken offline.

The volume usage exceeds the criticalquota threshold.

critical10209

The volume usage has dropped tobelow the defined critical quota level.

information10210

The volume will be taken offline if thesnapshot levels exceed the quota.

The amount of space on the volumedefined for snapshots is exceeding thedefined quota.

critical10211

The snapshot levels have returned tobelow the defined snapshot quota.

information10212

A volume is above the snapshot quotalevel and is being taken offline.

warning10213

This is a one-time action. Adjust volumequotas appropriately.

The quota for the volume is being set to100% because it is above its quota.

warning10214

Adjust the quota or add capacity andbring the volume back online.

The volume is being taken offlinebecause it exceeds its snapshot quota.

warning10215

This is a one-time action. Adjustsnapshot quotas appropriately.

The snapshot quota for the volume isbeing set to unlimited because it isabove its quota.

warning10216

Adjust the reserve, add more capacity,and bring the volume back online.

The volume being taken offline becauseit is above its reserve, and the systemis out of free space.

warning10217

SNMP Traps | 19


This is a one time action. Adjust volumereserves appropriately.

The volume reserve is being reset tozero because it is above its reserve, andthe system is out of free space.

warning10218

Adjust reserve settings and add morecapacity, then bring the volume backonline.

The volume being taken offline becauseit is above its snapshot reserve, andsystem is out of free space .

warning10219

Adjust volume snapshot reservesappropriately and add capacity ifneeded.

The volume snapshot reserve is beingset to zero because it is above itsreserve, and system is out of free space.

warning10220

Adjust space usage limits or addcapacity.

Volume space use has reached thedefined warning limit.

warning10221

The volume space that was previouslyover limit has returned to below warninglimit level.

information10222

Increase the quota or add capacity.The consumed volume space is overthe configured quota.

error10223

The volume space that was previouslyover quota has returned to belowdefined quota limits.

information10224

Adjust space usage limits or addcapacity.

The volume snapshot space usage hasexceeded the defined warning limit.

warning10225

The volume snapshot space that waspreviously over quota has returned tobelow defined warning limit.

information10226

Increase the quota or add capacity.The consumed volume snapshot spaceis over the configured quota.

warning10227

The volume space that was previouslyover quota has returned to belowdefined quota limits.

information10228

Performance policies and protection setsNotes/ActionsDescriptionSeverityAlert/Event

The system successfully took allsnapshots on volumes associated with

information10300

the specified volume collectionschedule.

Verify that the system is active andhealthy, that the volumes are

The system failed to completesnapshots on volumes associated with

warning10301

accessible, that there is space available,the specified volume collectionschedule. and that there are no conflicting

schedules.

Snapshots cannot be taken during ahandover.

The system skipped a scheduledsnapshot collection because a handoverin progress.

information10303

20 | SNMP Traps

Notes/ActionsDescriptionSeverityAlert/Event

The system successfully created thesnapshot for volumes associated with

information10304

the specified volume collectionschedule, and shows details about theschedule.

Verify that the vCenter authentication iscorrect.

A VMware-based snapshot failedbecause the system could not log intothe vCenter server.

warning10305

Verify that the connection is active andthat the defined server name and IPaddress are correct.

A VMware-based snapshot failedbecause the connection to the vCenterserver timed out.

warning10306

Verify that the connection is active andthat the defined server name and IPaddress are correct.

A VMware-based snapshot failedbecause the vCenter server refused theconnection.

warning10307

Verify the connections.A VMware-based snapshot failedbecause the vCenter server is not

warning10308

connected to the Nimble ProtectionManager.

Check network connections.A VMware-based snapshot failedbecause the system could not find aroute to the vCenter server.

warning10309

A VMware-based snapshot failedbecause because the socket read fromthe vCenter server timed out.

warning10310

Check network connections.A VMware-based snapshot failedbecause the network is unreachable.

warning10311

Some VMWare products such as MVDIand Lab Manager create virtual

A VMware-based snapshot failedbecause because snapshots aredisabled.

warning10312

machines with restricted controls. Donot use datastores in VolumeCollections that usevCenter-synchronized snapshots on theNimble array.

A VMware-based snapshot failedbecause the volume doesn't exist.

warning10313

Configure the system with properpermissions or log in as a user with theproper permissions.

A VMware-based snapshot failedbecause the system does not have theproper permissions to perform theaction.

warning10314

Verify the vCenter server name and IPaddress.

A VMware-based snapshot failedbecause the system was unable to lookup the vCenter server.

warning10315

Use UTF-8 browser encoding when youenter the vCenter server, user name,and password.

A VMware-based snapshot failed dueto an encoding error, usually from abrowser using foreign-languageencoding for English.

warning10316

SNMP Traps | 21


A VMware-based snapshot failedbecause the server socket was closedbefore a reply was written.

warning10317

Locate the datacenter.A VMware-based snapshot failedbecause no Datacenter exists.

warning10318

Without the serial number for the array,the the vCenter server cannot determinewhat array to use.

A VMware-based snapshot failedbecause the Nimble volume serialnumber is empty.

warning10319

A VMware-based snapshot failed dueto an unknown error.

warning10320

Associate the VM to a datastore withthe appropriate block size.

A VMware-based snapshot failedbecause the VMFS datastore block sizeis not large enough to accommodate thefiles in the VM.

warning10321

Space usageAction/NotesDescriptionSeverityAlert/Event

Free some space or add capacity.The amount of space used on the arrayhas exceeded the defined warning limit.

warning10401

The amount of space used has beenlowered to below the defined warninglimit.

information10402

Volumes above their reserve will betaken offline once the free space hasbeen exhausted. Adjust reserves.

The amount of space used on the arrayhas exceeded critical level settings.

critical10403

The space usage has returned to levelsbelow critical settings.

information10404

The message shows the actual spaceusage level.

The space usage for the array is okay.information10405

Delete unneeded snapshots or volumesto reduce space usage.

The space available on the array is low.information10406


The space available on the array isbelow defined warning levels.

warning10407


The array space is currently above thedefined critical level.

critical10408

ReplicationAction/NotesDescriptionSeverityAlert/Event

The system successfully replicated thespecified snapshot collection to thereplication partner.

information11000

22 | SNMP Traps

Action/NotesDescriptionSeverityAlert/Event

Make sure that the replication partnerscan communicate, that replication has

There is an excessive delay replicatingthe specified volume collection to itsreplication partner.

warning11002

not been paused, and that there are nooverlapping schedules or configurationconflicts.

Make sure that the replication partnerscan communicate and that there are noconfiguration conflicts.

Failed to synchronize the replicationconfiguration to the replication partnerspecified.

warning11003

Remove the specified volume on thepartner.

A replication has stalled.warning11004

Ownership has been transferred.The system has completed thehandover of the volume collection.

information11005

General hardwareNotes/ActionsDescriptionSeverityAlert/Event

Check the environmental temperaturewhere the array is placed, and make

The specified controller is over the safeoperating temperature and is being shutdown.

critical12000

sure the temperature is withinacceptable range and that air flow is notblocked. If there are fan alerts or theproblem persists, contact Support..

The specified controller is over the safeoperating temperature.

critical12001

The backplane is over the safeoperating temperature.

critical12002

System monitor - diskNotes/ActionsDescriptionSeverityAlert/Event

The disk in the specified slot has failed,and only the shown number of disks areleft.

critical12100

Replace the disk.The disk in the specified slot has failed.warning12101

Verify that the disk is in place andseated correctly, or reseat the disk. Ifnecessary, reinsert or replace the disk.

The disk in the specified slot is missing.warning12102

A disk has been added to the specifiedslot.

information12103

The disk in the specified slot wasremoved by an administrator, using theCLI.

information12104

Replace the SSD disk.An SSD has failed at the specified slot.warning12105

Verify that the disk is seated properly.Reinsert or replace the disk.

An SSD is missing from the specifiedslot.

warning12106

SNMP Traps | 23


An SSD has been added at the specifiedslot.

information12107

The SSD in the specified slot wasremoved by an administrator, using theCLI.

information12108

Replace the disk with a Nimble disk.The specified disk is not a Nimble arraydisk.

warning12109

Replace the SSD with a Nimble disk.The specified SSD is not a Nimble arraydisk.

warning12110

Replace the disk with one of the correctsize (shown on the alert).

The specified disk is not the right sizedisk for this hardware model.

warning12111

System monitor - NICNotes/ActionsDescriptionSeverityAlert/Event

The specified IP interface is down.warning12200

The specified IP interface is up.information12201

The group IP interface is unavailable.warning12202

Verify that the network is active and thatthe connection configuration is valid.

All of the data IP interfaces areunavailable.

warning12203

Check the network.IP connectivity has been lost, all linksare down.

critical12204

Edit the configuration if necessary.The NIC for the specified subnet doesnot exist. The system is migratingconfiguration to the named NIC.

warning12205

Edit the configuration to ensure that thesubnet is configured for an existing NIC.

The NIC for the specified subnet doesnot exist.

warning12206

Edit the configuration if necessary.The NIC for the displayed IP addressdoes not exist. The system is migratingthe configuration to the NIC shown.

warning12207

Edit the configuration to ensure that theIP address is configured for the NIC.

The NIC for the specified IP addressdoes not exist

warning12208

Edit the configuration if necessary.The NIC for the configured routegateway does not exist. Migratingconfiguration to the named NIC.

warning12209

Edit the configuration to ensure that aroute is configured for this NIC.

The NIC for the configured routegateway does not exist.

warning12210

System management monitorNotes/ActionsDescription/Possible CauseSeverityAlert/Event

A sensor has reported a warning for thetemperature, and shows the lasttemperature reading.

warning12301

24 | SNMP Traps


The sensor reports that the temperaturehas returned to within the acceptablerange.

information12302

A temperature sensor has failed.warning12303

The sensor has returned to normal.information12304

The specified temperature sensor ismissing.

warning12305

Contact Technical Support.The NVRAM battery on the specifiedcontroller has been disabled.

warning12306

Contact Technical Support.All NVRAM batteries on the specifiedcontroller have been disabled.

critical12307

The specified NVRAM battery hasreturned to normal.

information12308

Temperature sensorsNotes/ActionsDescription/Possible CauseSeverityAlert/Event

Check the ambient temperature andmake any needed corrections. If the

The specified temperature sensorreports that the current temperature ishigh, and shows the temperature.

warning12323

ambient temperature is good, attemptto locate the hot spot.

The specified temperature sensorreports that the current temperature islow, and shows the temperature.

warning12324

System temperature is now withinacceptable range and the currenttemperature for the sensor shown.

information12325

The specified temperature sensor is notoperational.

warning12326

The specified temperature sensor isoperational, and the current temperatureis shown.

information12327

Fan sensorsNotes/ActionsDescription/Possible CauseSeverityAlert/Event

The specified fan is running fast: thesystem shows the current speed.

information12328

The specified fan is running slow: thesystem shows the current speed.

information12329

The specified fan is now running atnormal speed.

information12330

SNMP Traps | 25


Verify that the fan is seated correctlyand is receiving power, and repair orreplace the fan as necessary.

The specified fan stopped working.warning12331

Verify that the fan is correctly seated,and if necessary, restore or replace thefan.

The specified fan is missing.warning12332

Power supplyNotes/ActionsDescription/Possible CauseSeverityAlert/Event

Check the power supply and replace ifnecessary.

The specified power supply is either notconnected or has failed.

warning12333

Determine if the power supply has beenremoved or failed and replace or reseatif necessary.

The specified power supply is missing.warning12334

The specified power supply is workingcorrectly.

information12335

RAID managementNotes/ActionsDescription/Possible CauseSeverityAlert/Event

Replace any failed disks.The RAID array is degraded by thenumber of disks shown.

warning12400

The RAID array has started rebuildingthe specified disk.

information12401

The RAID array has successfullycompleted rebuilding the specified disk.

information12402

The system failed to rebuild the RAIDarray because not enough disks areavailable.

warning12403

The system failed to rebuild the RAIDarray on the specified disk due to I/Oerrors.

warning12404

Determine if the disk has failed or hasbeen removed and take correctiveaction.

The specified disk is missing from theRAID array.

warning12405

The specified disk has been marked asa spare.

information12406

Fix any conditions that could be causingdisks to fail or not been seen. If theproblem persists, contact Support.

There were not enough spare disksavailable to assemble RAID on thearray.

critical12407

26 | SNMP Traps

System management (ACL) messagesNotes/ActionDescription/Possible CauseSeverityAlert/Event

Multiple initiator logins are not allowed.iSCSI login is rejected.information12500

Reduce the number of iSCSIconnections to the array.

Unable to connect another iSCSIconnection: too many iSCSI connections

warning12501

System management (resource) messagesNotes/ActionDescription/Possible CauseSeverityAlert/Event

Consider moving some volumes to otherarrays.

The total number of volumes on thissystem is approaching system limit.

warning13101

The number of volumes on this systemhas been reduced to an acceptablelevel.

information13102

SNMP Traps | 27

Nimble SNMP FAQ

SNMP v1, v2, and v2cWhat versions of SNMP does Nimble support?

Not in the current version. UDP traps are supported.Are acknowledged traps (informs) supported?

Through the GUI using the Administration >SNMP menu or the CLI snmp command.

How can I configure SNMP?

Community name.What security features are supported?

One.How many trap recipients are supported on eachdevice?

No. In this release, the device only sends traps.Does the device receive and forward traps?

28 | Nimble SNMP FAQ

Index

A

ACL events 15audience 4

B

bindings 14

C

community stringsetting 7

configuringSNMP 7

controller 15conventions used 4

D

drive events 15

E

eventsdescription of 15events list 15

F

fan events 15

G

global statistics table 11

H

hardware events 15

I

IANA number 8

L

list of events 15

M

MIB 6, 7, 11

N

nimbleTrapCode 14

O

OID 8overview 6

P

polling 8power supply events 15

R

RFC1155 6

S

settingSNMP 7

SNMP 7SNMP events 15Support login 4

T

tableglobal statistics 11volume information 11

traps 14trap destination setting 7trap variables 14

V

variable names 8volume information table 11

Index | 29

nimble os snmp reference guide - static.spiceworks.com · for example, if a system has 15 volumes...

Documents