Nimble OS SNMP Reference Guide - Spiceworks

2y ago
29 Views
2 Downloads
421.26 KB
29 Pages
Last View : 13d ago
Last Download : 5m ago
Upload by : Annika Witter
Transcription

Nimble OS SNMP Reference GuideP/N 990-0207-001 09/13/11

ii TOCContentsCopyright notices.3Preface.4SNMP Basics.6Setting up SNMP on the Nimble array.7IANA and OID numbers.8Nimble MIB.10Volume Information table.11Global Stats table.11SNMP Traps.13Traps and trap variables.14Event list .15Nimble SNMP FAQ.28

Copyright noticesCopyright 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 95134Tel: 1 408.432.9600Web: www.nimblestorage.comEmail: sales@nimblestorage.com

4 PrefacePrefaceThe 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 networkingyour network environmentsnapshots and replication tasksyour system usage trendsthe requirements and configuration specific to your applicationsConventions used in this documentThroughout the documentation, the following conventions are used:If you see:It means:fixed widththe 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 URLitalicsa tab on the GUI or emphasis on the textA Bselect the first option named, followed by the secondexamplesexample output is shown with a slightly shaded backgroundbolda field name, button, or other unspecified component of the UIThe CLI iconprovides 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 iconindicates 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.

Preface 5Troubleshooting and other help is available from the Nimble Storage support site atwww.nimblestorage.com/support or you can email support at support@nimblestorage.com. You 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.

6 SNMP BasicsSNMP BasicsTopics: Setting up SNMP on the NimblearrayIANA and OID numbersNimble Storage software provides an SNMP option for monitoringNimble arrays. You should be familiar with Simple NetworkManagement Protocol (SNMP) before enabling SNMP monitoring.RFC1155 is a good place to start if you are not familiar with SNMPand MIBs.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.

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

8 SNMP Basics2. 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 numbersThe Internet Assigned Numbers Authority (IANA) number assigned to Nimble Storage is 37447: everythingin the Nimble MIB is under the erprises(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.

SNMP Basics 9For example, if a system has 15 volumes (indicated by the variable volNumberOfVolumes value ofth15), the name of the 8 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

10 Nimble MIBNimble MIBTopics: Volume Information tableGlobal Stats tableThe following entries are provided with the Nimble MIB.

Nimble MIB 11Volume Information tableOverviewWhen 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 TableNameTypeIndexed (part of table)? DescriptionvolNumberOfVolumesUnsigned32NoNumber of volumes.volIndexUnsigned32YesVolume index.volIDUnsigned32YesVolume ID.volNameDisplayStringYesVolume name.volSizeLowUnsigned32YesMax. size in bytes (loworder bytes).volSizeHighUnsigned32YesMax. size in bytes (highorder bytes).volUsageLowUnsigned32YesUsage in bytes (loworder bytes).volUsageHighUnsigned32YesUsage in bytes (highorder bytes).volReserveLowUnsigned32YesReserved bytes (loworder bytes).volReserveHighUnsigned32YesReserved bytes (highorder bytes).volOnlineTruthValueYesVolume online (true orfalse).volNumConnectionsUnsigned32YesNumber of connectionsto the volume.Global Stats tableThe 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

12 Nimble MIBfor 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.NameTypeIndexed (part of table)? DescriptionstatTimeEpochSecondsCounter64NoUNIX time (number of secondssince the UNIX epoch) when statswere recorded.ioReadsCounter64NoTotal cumulative number of ReadI/Os (sequential and random).ioSeqReadsCounter64NoTotal cumulative number ofSequential Read I/Os.ioWritesCounter64NoTotal cumulative number of WriteI/Os (sequential and random).ioSeqWritesCounter64NoTotal cumulative number ofSequential Write I/Os.ioReadTimeMicrosecCounter64NoTotal cumulative microseconds thesystem has spent processingRead I/Os.ioWriteTimeMicrosecCounter64NoTotal cumulative microseconds thesystem has spent processing WriteI/Os.ioReadBytesCounter64NoTotal cumulative number of ReadI/O bytes (sequential and random).ioSeqReadBytesCounter64NoTotal cumulative number ofSequential Read I/O bytes.ioWriteBytesCounter64NoTotal cumulative number of WriteI/O bytes (sequential and random).ioSeqWriteBytesCounter64NoTotal cumulative number ofSequential Write I/O bytes.diskVolBytesUsedLowUnsigned32NoTotal number of bytes used ondisk for volumes (low order bytes).diskVolBytesUsedHighUnsigned32NoTotal number of bytes used ondisk for volumes (high orderbytes).diskSnapBytesUsedLowUnsigned32NoTotal number of bytes used ondisk for snapshots (low orderbytes).diskSnapBytesUsedHigh Unsigned32NoTotal number of bytes used ondisk for snapshots (high orderbytes).ioNonseqReadHitsNoTotal cumulative number of cachehits for Non-Sequential Read I/Os.Counter64

SNMP TrapsTopics: Traps and trap variablesEvent listAll alerts that can be sent via email to administrators can be sentas SNMP traps.

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 s related to general data services.nimbleControllerTrapTraps related to controller operation and status.nimbleServiceTrapTraps related to miscellaneous services.nimbleTestTrapTraps related to the sending of test alerts and traps.nimbleSoftwareUpdateTrapTraps related to software updates.nimbleDataServiceInteractionTrapTraps related to interaction with the data service.nimbleVolAndSnapshotTrapTraps related to volumes and snapshots.nimbleVolumeCollectionTrapTraps related to volume collections.nimbleSystemSpaceTrapTraps related to system space utilization.nimbleReplicationTrapTraps related to replication.nimbleHardwareTrapTraps related to general hardware.nimbleDiskTrapTraps related to disks.nimbleNicTrapTraps related to NICs.nimbleEnvironmentalTrapTraps related to environmental components (sensors,temperature, NVRAM batteries, fans, power supplies).nimbleRaidTrapTraps related to RAID.nimbleConnectionTrapTraps related to iSCSI connections.nimbleResourceLimitTrapTraps 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/Event SeverityDescription/Possible CauseNotes/Actions0101warningFree space is down to the stated level, Delete unneeded snapshots or volumeswrite operations will be slowed.to regain free space.0102information Free space has been reclaimed and hasreturned to the level shown. Writeoperations are back to normal speed.0103criticalFree space is critically low, at the level Delete unneeded snapshots or volumesshown, and write operations will beto regain free space or add capacity todisabled.the array.0104warningThe system is currently nearing full.0105information The space usage has been restored toless than the defined minimum warninglevel.0106criticalThe system has reached the criticalusage level.Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.0107criticalThe system has only minimal spaceavailable for writing.Application writes will be progressivelyslowed as space continues to decline.0110criticalThe system has reached critically lowspace availability for writing.Application writes will time out.Alert/Event SeverityDescription/Possible CauseNotes/Action2001criticalAn error occurred on the specifiedcontroller.A software error has occurred. ContactNimble support.2002information A takeover occurred on the specifiedcontroller.The specified controller has assumedthe active role and is now supportingdata services. Check for failuresymptoms on the peer controller.2003information The standby controller specified isavailable.The array is running in a redundantcontroller configuration. No actionneeded.Delete unneeded snapshots or volumesto reduce space usage or add capacityto the array.Controllers, HA

16 SNMP TrapsAlert/Event SeverityDescription/Possible CauseNotes/Action2005criticalExcessive restarts on the specifiedcontroller were detected. The specifiedcontroller detected repeated failures ina short period of time.This could be caused by successivepower failures or persistent controllerhardware or software issues. Thecontroller will not attempt to start dataservices 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.2006criticalThe specified controller is beingAfter the controller restart, verify that therestarted in order to recover the stated service has restarted.service.2007information The array received a request from theadministrator to reboot the specifiedcontroller.2008warning2009information The array received a request from theadministrator to halt the specifiedcontroller.2010warningThe array was not able to complete the Contact Nimble support.request to halt the controller.2013warningAn error occurred on the specifiedcontroller.2014criticalAn error occurred on the specifiedA software error occurred while in acontroller and all services have stopped. non-redundant controller configuration.Contact Nimble support.2015warningThe standby controller has not beenThe array is not running in a redundantavailable for the amount of time shown. controller configuration. Check for failuresymptoms on the peer controller.The array was not able to complete the Contact Nimble support.request to reboot the controller.A software error occurred while in aredundant controller configuration.Contact Nimble support.ServicesAlert/Event SeverityDescription/Possible Cause2101information The system services were started, andthe system shows the currently installedsoftware version.2103warning2104information A secure tunnel was created on thespecified controller to allow NimbleStorage support personnel access.The specified service has stoppedunexpectedly but is not restartingautomatically.Notes/ActionThe specified service is unable to runreliably and is being shut down. ContactNimble support.

SNMP Traps 17Alert/Event Severity2105Description/Possible CauseNotes/Actioninformation The secure tunnel to Nimble Storagesupport has been terminated.Test messagesThese messages appear when an alert --test command has been issued from the CLI.Alert/Event SeverityDescription/Possible CauseNotes/Action5001information A test command has triggered aninformation-level alert.No action needs to be taken.5002errorA test command has triggered anerror-level alert.No action needs to be taken.5004noteA test has been triggered for anote-level alert. (Deprecated)No action needs to be taken.5005warningA test command has triggered awarning-level alert.No action needs to be taken.5006criticalA test command has triggered acritical-level alert.No action needs to be taken.Alert/Event SeverityDescription/Possible CauseNotes/Action6000warningThe system failed to unpack thesoftware update package on thespecified controller.Verify that the software version iscompatible, and retry or redownload. Ifthe problem persists, contact Support.6001information The system has begun the softwareupdate to the specified version.6002warning6003information The software update was successful onthe specified controller.6004information The system is rolling back the softwareto the specified version.6005warningThe precheck failed on the updatepackage.6007warningPrecheck failed because the file system Contact Support.is out of space.Software updateThe system is reverting the software to Verify that the software version isthe previous version.compatible, and retry or redownload. Ifthe problem persists, contact Support.Retry the download. If the problempersists, contact Support.Precheck failed indicating that network Check standby controller network links,connectivity will degrade after theswitches links, and retry softwaresoftware update.update.6008information The system is unpacking the specifiedupdate package on the namedcontroller.

18 SNMP TrapsAlert/Event SeverityDescription/Possible CauseNotes/Action6009information The unpacking process has completedon the software update package.6010information To complete a software update, thesystem is rebooting the specifiedcontroller.6011warningFailed to download software updatepackage.6012warningThe software update failed because the Schedule to reboot the target controller"/tmp" directory is full.(by pulling it out and pushing it in)6013warningThe software update failed because the Contact Support.scratch space is full.6014warningThe software update failed because the Contact Support."/var" directory is full.6015warningThe software update failed because the Contact Support.configuration space is full.6016warningThe software update failed because the Contact Support.Recovery OS space is full.6017warningThe software update package was not Download the package again and retryfound.the update.6018warningThe software update package has thewrong signature.Make sure that your firewall doesn'tchange the update package. Retry todownload or upload. If upload is used,make sure that the uploaded packageis a Nimble update package.6019warningThe software update package has thewrong checksum.Retry the download. If upload is used,make sure that the update package isnot corrupted.6020warningThe software update precheck failed. Check network connectivity on theNetwork connectivity will degrade after standby controller.software update is complete.6021warningThe software update failed because only Bring the other controller back toone controller is available.standby mode.Make sure the network connections areactive and retry.GeneralAlert/Event Severity10101Description/Possible CauseNotes/Actionsinformation Cache was cleared by the administrator(using the CLI).Volumes, snapshots, and clonesAlert/Event SeverityDescription/Possible Cause10200The space usage of the specifiedAdd more space to the volume, or resetvolume is over the configured warning the warning limit.limit.warningNotes/Actions

SNMP Traps 19Alert/Event SeverityDescription/Possible CauseNotes/Actions10201information The space usage of the specifiedvolume has returned to below theconfigured warning limit.10202warning10203information The space usage of the specifiedvolume has returned to below theconfigured quota.10204warning10205information The snapshot space usage on thespecified volume has returned to belowthe configured warning limit.10206error10207information The snapshot space usage on thespecified volume has returned to belowthe configured quota.10208warningVolume attribute synchronization hasbeen delayed.10209criticalThe volume usage exceeds the critical If usage exceeds the quota, the volumequota threshold.will be taken offline.10210information The volume usage has dropped tobelow the defined critical quota level.10211critical10212information The snapshot levels have returned tobelow the defined snapshot quota.10213warningA volume is above the snapshot quotalevel and is being taken offline.10214warningThe quota for the volume is being set to This is a one-time action. Adjust volume100% because it is above its quota.quotas appropriately.10215warningThe volume is being taken offlineAdjust the quota or add capacity andbecause it exceeds its snapshot quota. bring the volume back online.10216warningThe snapshot quota for the volume isbeing set to unlimited because it isabove its quota.10217warningThe volume being taken offline because Adjust the reserve, add more capacity,it is above its reserve, and the system and bring the volume back online.is out of free space.The space usage of the specifiedvolume is over the configured quota.Extend the quota limit or add morespace to the volume.The snapshot space usage on theAdd more space or reset the warningspecified volume is over the configured limit.warning limit.The snapshot space usage on theAdd more space or reset the snapshotspecified volume is over the configured quota.quota.The system will automatically retrysynchronization.The amount of space on the volumeThe volume will be taken offline if thedefined for snapshots is exceeding the snapshot levels exceed the quota.defined quota.This is a one-time action. Adjustsnapshot quotas appropriately.

20 SNMP TrapsAlert/Event SeverityDescription/Possible Cause10218warningThe volume reserve is being reset toThis is a one time action. Adjust volumezero because it is above its reserve, and reserves appropriately.the system is out of free space.10219warningThe volume being taken offline because Adjust reserve settings and add moreit is above its snapshot reserve, andcapacity, then bring the volume backsystem is out of free space .online.10220warningThe volume snapshot reserve is being Adjust volume snapshot reservesset to zero because it is above itsappropriately and add capacity ifreserve, and system is out of free space. needed.10221warningVolume space use has reached thedefined warning limit.10222information The volume space that was previouslyover limit has returned to below warninglimit level.10223error10224information The volume space that was previouslyover quota has returned to belowdefined quota limits.10225warning10226information The volume snapshot space that waspreviously over quota has returned tobelow defined warning limit.10227warning10228information The volume space that was previouslyover quota has returned to belowdefined quota limits.The consumed volume space is overthe configured quota.Notes/ActionsAdjust space usage limits or addcapacity.Increase the quota or add capacity.The volume snapshot space usage has Adjust space usage limits or addexceeded the defined warning limit.capacity.The consumed volume snapshot space Increase the quota or add capacity.is over the configured quota.Performance policies and protection setsAlert/Event SeverityDescriptionNotes/Actions10300information The system successfully took allsnapshots on volumes associated withthe specified volume collectionschedule.10301warning10303information The system skipped a scheduledSnapshots cannot be taken during asnapshot collection because a handover handover.in progress.The system failed to completesnapshots on volumes associated withthe specified volume collectionschedule.Verify that the system is active andhealthy, that the volumes areaccessible, that there is space available,and that there are no conflictingschedules.

SNMP Traps 21Alert/Event SeverityDescriptionNotes/Actions10304information The system successfully created thesnapshot for volumes associated withthe specified volume collectionschedule, and shows details about theschedule.10305warningA VMware-based snapshot failedbecause the system could not log intothe vCenter server.10306warningA VMware-based snapshot failedVerify that the connection is active andbecause the connection to the vCenter that the defined server name and IPserver timed out.address are correct.10307warningA VMware-based snapshot failedVerify that the connection is active andbecause the vCenter server refused the that the defined server name and IPconnection.address are correct.10308warningA VMware-based snapshot failedbecause the vCenter server is notconnected to the Nimble ProtectionManager.Verify the connections.10309warningA VMware-based snapshot failedbecause the system could not find aroute to the vCenter server.Check network connections.10310warningA VMware-based snapshot failedbecause because the socket read fromthe vCenter server timed out.10311warningA VMware-based snapshot failedbecause the network is unreachable.Check network connections.10312warningA VMware-based snapshot failedbecause because snapshots aredisabled.Some VMWare products such as MVDIand Lab Manager create virtualmachines with restricted controls. Donot use datastores in VolumeCollections that usevCenter-synchronized snapshots on theNimble array.10313warningA VMware-based snapshot failedbecause the volume doesn't exist.10314warningA VMware-based snapshot failedConfigure the system with properbecause the system does not have the permissions or log in as a

Nimble Storage software provides an SNMP option for monitoring Nimble arrays.You should be familiar with Simple Network Topics: Setting up SNMP on the Nimble array Management Protocol (SNMP) bef ore enab ling SNMP monitor ing. RFC1155 is a good place to star t if you are not f amiliar with SNMP IANA and OID numbers and MIBs.

Related Documents:

NIMBLE STORAGE REQUIREMENTS VERSION(S) vRealize Operations v6.x (Advanced or Enterprise editions) NOTE: For OS monitoring, vROps v6.1 is required. Nimble Storage CS210 Nimble OS 2.x Nimble API 1.3 CREDENTIALS N/A Nimble User Name/Password Optional for group performance data: SNMP v2 Community String

ACI SNMP Overview SNMP Basic components are: Managed Device: the hardware device to be monitored Agent (SNMP software running on the Managed Device) Network Management System: the monitoring system which has SNMP Client to communicate with the Agent running on the Managed Device SNMP is widely supported across several Cisco platforms. For more information on SNMP, please refer to the Cisco .

SNMP Informant - Installation and Configuration Guide - v2014.1 Page 4 Product Description SNMP Informant agents are DLL (Dynamic Link Libraries) extensions to the Microsoft Windows SNMP service. The Windows SNMP Service must be installed properly, configured and running before the SNMP Informant agent is accessible.

SNMP / net-snmp SNMP: Simple Network Monitoring Protocol – Versions 1 (RFC 1157), 2c (1901), 3 (2571) net-snmp: dominant toolkit to implement SNMP – applications (snmpwalk etc.) and libraries – sn

Nimble Storage vs Pure Storage: A Comparison Snapshot How They Compare: Nimble: - Data reduction features Nimble leverages disk-optimized data layout to deliver capacity density in addition to performance density. * Sub-millisecond write latency A Nimble

9 2017 Nimble Storage. Nimble Secondary Storage Value Proposition Primary Storage Nimble Secondary Cloud Object Storage Nimble Primary Always verified backups High performance allows dev/test, analytics on backup Inline dedupe (and encryption) without sacrificing random IOPS No hassle, automated archiving to cloud Global monitoring & analytics

System Source & Nimble Storage: Nimble Storage Partner since 2011 100 Nimble SAN installations Nimble Storage beneficial for: Server Virtualization VDI - Virtual Desktop Infrastructure Microsoft Applications: Exchange, SQL Server & SharePoint Applications requiring high IOPS at lower price point Offsite Backup / Replication Keep storage and applications up

Care and compassion? Report of the Health Service Ombudsman on ten investigations into NHS care of older people Fourth report of the Health Service Commissioner for England Session 2010-2011 Presented to Parliament pursuant to Section 14(4) of the Health Service Commissioners Act 1993 Ordered by The House of Commons to be printed on 14 February 2011 HC 778 London: The Stationery Office 15.50 .