CommandReference - infosight.hpe.com · Onset time: Oct 20 2016 16:49:30 Array: - Object type: volume Object name: test Description: Volume test string from alert gen space usage

Command Reference

Version 5.1.x

Published May, 2020

Legal Notices© Copyright 2020 Hewlett Packard Enterprise Development LP. All rights reserved worldwide.

NoticesThe information contained herein is subject to change without notice. The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying such productsand services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterpriseshall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, orcopying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documen-tation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standardcommercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprisehas no control over and is not responsible for information outside the Hewlett Packard Enterprise website.

AcknowledgmentsIntel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the UnitedStates and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Java® and Oracle® are registered trade-marks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Publication DateThursday May 14, 2020 16:08:15

Document IDaqf1582234556259

SupportAll documentation and knowledge base articles are available on HPE InfoSight at https://infosight.hpe.com.To register for HPE InfoSight, click the Create Account link on the main page.Email: [email protected] all other general support contact information, go to https://www.nimblestorage.com/customer-support/.

Copyright © 2020 by Hewlett Packard Enterprise Development LP. All rights reserved.

Documentation Feedback: [email protected] Notices

https://infosight.hpe.commailto:[email protected]://www.nimblestorage.com/customer-support/mailto:[email protected]?subject=[DOC FEEDBACK] - Command Reference , Version 5.1.x&body=Date: 05/14/2020%0D%0ATopic or Content Referenced: (please add information) %0D%0AComment: (please add information) %0D%0A

Contents

The Nimble CLI.............................................................................................5CLI Help................................................................................................................................................5

Nimble Administrative Commands.............................................................7alarm.....................................................................................................................................................7alert.....................................................................................................................................................11array...................................................................................................................................................13auditlog...............................................................................................................................................19cert......................................................................................................................................................22chapuser.............................................................................................................................................30ctrlr......................................................................................................................................................34date.....................................................................................................................................................36disk.....................................................................................................................................................37encryptkey..........................................................................................................................................43failover................................................................................................................................................46fc.........................................................................................................................................................47folder...................................................................................................................................................51group..................................................................................................................................................57halt......................................................................................................................................................87initiatorgrp...........................................................................................................................................89ip.........................................................................................................................................................98migration...........................................................................................................................................104netconfig...........................................................................................................................................106nic.....................................................................................................................................................110partner..............................................................................................................................................114pe......................................................................................................................................................122perfpolicy..........................................................................................................................................123pool...................................................................................................................................................131prottmpl.............................................................................................................................................136reboot...............................................................................................................................................151route.................................................................................................................................................153setup.................................................................................................................................................155shelf..................................................................................................................................................160snap..................................................................................................................................................162snapcoll............................................................................................................................................168software............................................................................................................................................171sshkey..............................................................................................................................................174stats..................................................................................................................................................177


subnet...............................................................................................................................................183timezone...........................................................................................................................................188useradmin.........................................................................................................................................189userauth............................................................................................................................................192userpolicy.........................................................................................................................................196usersession......................................................................................................................................198vcenter..............................................................................................................................................200vm.....................................................................................................................................................202version..............................................................................................................................................204vmwplugin.........................................................................................................................................205vol.....................................................................................................................................................208volcoll................................................................................................................................................232witness..............................................................................................................................................248

Regulatory Information................................................................................................250Regulatory Warnings........................................................................................................................250


The Nimble CLI

Run NimbleOS administrative commands from the command line interface (CLI) to configure and monitor aNimble Storage array.

Use a secure shell (SSH) utility to log in to the management IP of an HPE Nimble Storage array to runadministrative commands. Your role determines your permission level, which in turn determines the commandoptions you can run.

After you log in, you see a security message for array usage. You do not have to acknowledge the securitymessage. Type ? to display a list of administrative commands. Then use any or all of the following optionsto get more information about the commands:

• To display available options for a specific command, type command_name --help.

The output lists each option and suboption, and provides brief descriptions of each.

• To display a man page that introduces all the commands, type man intro.

The output lists each command, and provides brief descriptions of each. Press the space bar to pagethrough the list. Type q to quit when you get to the end of the introduction.

• To display detailed information for a specific command, type man command_name.

The output lists the command name and brief description, synopsis of each option and suboption, anddetailed descriptions of each option and suboption, including valid values. Press the space bar to pagethrough the list. Type q to quit when you get to the end of the man page.

CLI HelpThe ? command lists the NimbleOS administrative commands or all commands.

Note The ? and help commands are similar. The major difference is that help command has a man page;the ? command does not.

Synopsis

?

? --help

? --all

Options

RoleDescriptionArguments and SuboptionsOption

GuestShow usage information for thecommand.

N/A--help

GuestShow all available commands, notjust the Nimble-specific administra-tive commands.

N/A--all

5Copyright © 2020 by Nimble Storage, Inc. All rights reserved.

Documentation Feedback: [email protected] Nimble CLI

mailto:[email protected]?subject=[DOC FEEDBACK] - Command Reference , Version 5.1.x&body=Date: 05/14/2020%0D%0ATopic or Content Referenced: (please add information) %0D%0AComment: (please add information) %0D%0A

Examples

This example lists the administrative commands used to manage a Nimble array.

Nimble OS $ ?? fc pool subnetalert group prottmpl timezonearray halt reboot useradminauditlog help route usersessioncert initiatorgrp setup versionchapuser ip shelf vmwpluginctrlr migration snap voldate netconfig snapcoll volcolldisk nic softwareencryptkey partner sshkeyfailover perfpolicy stats

This example shows partial output from ? --all. The output is truncated to save space.

Nimble OS $ ? --all? expr nohup subnet[ failover nslookup sum[[ false od syncalert fc partner tacarp fgrep patch tailarray find perfpolicy tee......encryptkey mv stats zcatenv netconfig stringsexpand nic stty

6Copyright © 2020 by Hewlett Packard Enterprise Development LP. All rights reserved.

Documentation Feedback: [email protected] Nimble CLI


Nimble Administrative Commands

A wide variety of administrative commands are provided to configure, manage, and monitor HPE NimbleStorage arrays.

Use either the NimbleOS graphical user interface (GUI) or the command line interface (CLI) to performadministrative operations on an HPE Nimble Storage array or group of arrays.

These interfaces provide comparable management capabilities. The GUI has tool tips, embedded userassistance, and help to guide you through administrative operations interactively. The CLI is useful to scriptfrequently performed operations.

alarmThe alarm command lets you view and manage alarms and notifications. By default, all alarms are displayedwhen you use the alarm command with the --list option. However, you can filter for severity levels, categories,and time spans. For example, you might want to generally limit alarms to only recent ones, but regularly viewa longer-term list of alarms to look for patterns of error. Filtering lets you manage only the alarms you areinterested in. You can also add andmodify reminders or notifications to alarms such as changing the frequencyor alarm notifications or .

Synopsis

alarm --help

alarm --list[--from [[yyyy-]mm-dd,]hh:mm[:ss]][--to [[yyyy-]mm-dd,]hh:mm[:ss]][--category name][--severity level]

alarm --info id

alarm --acknowledge id[--remind_every period][--remind_every_unit {minutes|hours|days}]

alarm --unacknowledge id

alarm --edit id[--remind_every_period][--remind_every_unit {minutes|hour|days}]

alarm --delete id

Options



N/A--help

7Copyright © 2020 by Nimble Storage, Inc. All rights reserved.

Documentation Feedback: [email protected] Administrative Commands



OperatorList all alarms and their IDs. Forexample alarm --list showsall info, while alarm --list --from 08-14,11:26:00 lists onlyalarms that appear after August14th at 11:26 am. You can specifytime with no date, but if you specifya date you must include a time.

The --list option takes the followingsub-options.

N/A--list

List alarms starting from a specifiedtime. Often used with the --to optionto frame an alarm list. Use only thetime, or the date and time, for exam-ple, alarm --list --from2015-08-25,12:10:00 oralarm --list --from12:10:00.

[--from [[yyyy-]mm-dd,]hh:mm[:ss]]

List alarms until specified time. Of-ten used with the --from option. Ifnot specified, continues with no endtime. Use only the time, or the dateand time, for example, alarm --list --to 2017-08-25,12:10:00 or alarm --list--from 05:15 --to12:10:00.

[--to [[yyyy-]mm-dd,]hh:mm[:ss]]

Restrict the list of alarms to onlyinclude the specified category.Valid categories are hardware,service, replication, volume, up-date, config and security.

[--category name]

Restrict the list of alarms to onlyinclude the specified severity. Validseverities are warning and critical.The option will only return alarmsof the severity specified.

[--severity level]

GuestShow detailed information about aspecified alarm. For example,alarm --info 668 displays in-formation about a specific alarm.To determine the alarm ID, usealarm --list.

id--info





GuestAcknowledge an alarm with thecurrent username. For example,alarm --acknowledge 668makes the currect user the acknowl-edger of alarm 668, and set theacknowledge date as the currentdate. To determine the alarm ID,use alarm --list.

The --acknowledge option takesthe following sub-options.

id--acknowledge

Frequency of alarm notification. Ifthis option is unspecified, it defaultsto 1 and remind_every_unit to day,so an alarm notification is sent ev-ery hour. The valid range is 0-60.If the --remind_every option is setto 0, a reminder email will not besent.

[--remind_every period]

Units for reminder frequency --minutes, hours or days. If this op-tion is unspecified, the default unitof day is used.

[--remind_every_unit {min-utes|hours|days}

OperatorWhen you unacknowledge analarm, it clears the acknowledgeduser and date fields. To determinethe alarm ID, use alarm --list.

id--unacknowledge

OperatorEdit the notification frequency of aspecified alarm. To determine thealarm ID, use alarm --list. The--edit option takes the followingsub-options.

id--edit

The frequency of alarm notifica-tions. If this option is unspecified,it defaults to 1 and remind_ev-ery_unit to day, so that an alarmnotification is sent every hour. Thevalid range is 0-60. If the --re-mind_every option is set to 0, a re-minder email will not be sent.

[--remind_every period]

Units for reminder frequency --minutes, hours or days. If this op-tion is unspecified, the default unitof day is used.

[--remind_every_unit {min-utes|hours|days}





PoweruserDelete a specified alarm. For exam-ple, alarm --delete 1 deletesthe current alarm 1 if it exists. Becareful using this command be-cause an alarm indicates severeconditions on the system andshould not be ignored. To deter-mine the alarm ID, use alarm --list.

id--delete

Example

The following example lists all alarms in the group where you run the command.

Nimble OS $ alarm --list-----+----------+---------------------+---------+--------+--------------------------------ID Severity Time Status Array Detail-----+----------+---------------------+---------+--------+--------------------------------5 CRITICAL Oct 20 2016 16:49:30 Open - Volume test stringfrom alertgen space usage is at 0% and approaching quota of 0%. It will be taken offlineif it exceedsthe quota

The following example lists all the alarms on the array (there is only one) and then acknowledges that alarmsetting the notifications of the alarm to remind the user every day.

Nimble OS $ alarm --list-----+----------+---------------------+---------+---------+--------------------------------ID Severity Time Status Array Detail-----+----------+---------------------+---------+---------+--------------------------------5 CRITICAL Oct 20 2016 16:49:30 Open - Volume test stringfrom alertgen space usage is at 0% and approaching quota of 0%. It will be taken offlineif it exceedsthe quota

Nimble OS $ alarm --acknowledge 5 --remind_every 1 --remind_every_unit days

The following example lists detailed information about the alarm with ID 5.

Nimble OS $ alarm --info 5ID: 5Severity: criticalCategory: volumeOnset time: Oct 20 2016 16:49:30Array: -Object type: volumeObject name: testDescription: Volume test string from alert gen space usage is at 0% andapproaching quota of 0%.It will be taken offline if it exceeds the quotaStatus: AcknowledgedAcknowledged by: adminAcknowledged time: Oct 26 2016 15:59:55




Repeat period: Every 1 daysNext reminder time: Oct 27 2016 16:00:48

alertThe alert command options manage array alerts, which include certain events. You can also use the commandoptions to display information about alerts and events. Alerts and events can use both email and SMTPnotification methods.

Note The terms event and alert are sometimes used interchangeably. While an event can have differentseverity levels, the term event is often used to refer to a non-critical issue, such as a change to yourenvironment. The term alert refers to real-time notifications about issues, such as warning events, that canadversely affect your system. You can use alerts and events as a diagnostic and preventative tool. For moreinformation about alerts and events, see either theGUI Administration Guide or theCLI Administration Guide.

By default, all alerts and events are displayed when you use the alert --list command. You can filter the displaybased on severity levels, categories, and time spans so that you display only the alerts that you are interestedin. For example, you can filter for the most recent alerts, and periodically list all of them to look for potentialerrors.

You can also send a test alert to verify that the system is configured properly to send alerts.

Synopsis

alert --help

alert --list[--array array_name][--from [[yyyy-]mm-dd,]hh:mm[:ss]][--to [[yyyy-]mm-dd,]hh:mm[:ss]][--severity {info|warning|critical}][--category {hardware|service|replication|volume|update|config}]

alert --info id

alert --test[--severity {info|notice|warning|critical}]

Options



N/A--help


Documentation Feedback: [email protected]



GuestList alerts and events for the speci-fied array.

[--array array_name]--list

List alerts that start from the speci-fied time. Use only the time, or usethe date and time. For example,alert --list --from 08-14,12:10:00 or alert --list--from 12:10:00. Use this op-tion with or without the --to option.If used alone, --to is assumed to benow.


List alerts until the specified time.Use only the time, or use the dateand time. For example, alert --list --to 08-14,12:10:00or alert --list --to12:10:00. Use this option with orwithout the --from option.


List alerts and events of the speci-fied severity level. Alert levels arenot cumulative. For example, select-ing critical does not show the infoor warning severity levels.

[--severity {info|notice|warning|criti-cal}]

List alerts and events of the speci-fied category.

[--category {hardware|service|repli-cation|volume|update|config|securi-ty}]

GuestList detailed information about thespecified alert ID. To determinevalid alert IDs, use alert --list.

id--info

Power Us-er

Generate a test alert with thespecified severity level.

--severity {info|notice|warning|criti-cal}]

--test

Examples

This example lists all alert messages on the array where you run the command. The output is truncated tosave space.

Nimble OS $ alert --list----------+--------+--------------------+------+-----------+----------+---------ID Severity Time Type Category Array Detail----------+--------+--------------------+------+-----------+----------+---------

8 INFO Jun 27 2014 11:13:40 2101 service AA-102081 Systemservices started...

9 INFO Jun 27 2014 11:14:02 12714 hardware AA-102081 A newshelf is detected......

This example lists information about the alert with the ID 23.




Nimble OS $ alert --info 23ID: 23Active: yesPriority: INFOCategory: hardwareType: 12201Time: Feb 24 2014 17:10:00Cleared: N/AArray: AC-102266Target type: NICTarget: 192.168.1.3Detail: IP interface 192.168.1.3 up on controller A NIC port eth1

This example sends an alert test email with the warning severity level.

Nimble OS $ alert --test --severity warning

From: AdminSent: Wednesday, August 14, 2013 12:12 PMTo: eng-solSubject: Nimble Alert on sol / mars (AC-109828) - WARNING: Test alertTime: Wed Aug 14 15:11:40 2013

Type: 5005Id: 31645Message: Test message at warn level

Group Name: AdminGroup ID: 2070866469188534807Array name: marsSerial: AC-109828Version: 2.0.3.8-46920-opt

Arrays in the group:----------------+-----------------+-----------+----------------+-----------Name Serial Model Version Status----------------+-----------------+-----------+----------------+-----------moon AC-103234 CS460G-X2 2.0.3.8-46920-opt reachablesaturn AC-103236 CS460G-X2 2.0.3.8-46920-opt reachablejupiter AC-103242 CS460G-X2 2.0.3.8-46920-opt reachablemercury AC-103235 CS460G-X2 2.0.3.8-46920-opt reachable

arrayThe array command options manage a Nimble array.

Note Minimize the amount of time between running array --resetup and the setup command. On a FibreChannel array, there is no I/O between running array --resetup and setup. On an iSCSI array, existingconnections may be unaffected, but new connections are refused.

Synopsis

array --help

array --list

array --discover




array --info {name|serial_number}

array --edit name[--name new_name]

array --resetup[--non_interactive]

array --add serial_number[--name name][--subnet_label subnet_label][--data_ipaddr ipaddr][--nic nic][--tagged tag][--support_ipaddr ipaddr][--pool pool][--create_pool][--pool_description pool_description][--allow_lower_limits]

array --remove name[--force]

Options



N/A--help

GuestList all discovered and groupmember arrays.

N/A--list

Power Us-er

Discover non-member arrays onthe same management subnet.

N/A--discover

GuestProvide detailed information aboutthe specified group-member array.

{name | serial_number}--info

Power Us-er

Modify the name of the array. Thename must conform to iSCSI nam-ing conventions. It can be anycombination of up to 63 alphanu-meric characters and hyphen, butcannot begin with a hyphen, orcontain spaces or other punctua-tion.

[--name new_name]--edit





Administra-tor

Set a standalone array in a statewhere you can run the setup com-mand again. This reenables thezeroconf process and lets you resetthe array password, IP address,and most other configuration set-tings. No data will be lost. Afterrunning this command, any comput-er on the same subnet as the arraycan be used to reset the arraypassword and then control the ar-ray. Use this command with cau-tion. Minimize the time betweenresetting the array with this com-mand and running setup again tolimit I/O disruption. On a FibreChannel array, there is no I/O be-tween running array --resetup andsetup. On an iSCSI array, existingconnectionsmay be unaffected, butnew connections are refused.

N/A--resetup

Override the default behavior ofhaving to type "yes" to completethe command. Use this suboptionwith care to avoid unexpectedlysetting up the array.

[--non_interactive]





Power Us-er

Serial number of a discovered arrayto add to a group.

serial_number--add

Name of a array to add to a group.The group must exist.

[--name name]

Subnet label on the NIC. Repeatthis option to specify more than onesubnet label. The first subnet labelis assigned to the first NIC, suchas eth1, the second subnet label isassigned to the second NIC, suchas eth2, and so on. To skip a sub-net label, enter a blank argument.

[--subnet_label subnet_label]

The network IP address(es) thatwill manage data traffic. Repeat thisoption to set multiple IP addressesfor multiple NICs. Then the first IPaddress is assigned to the first NIC,such as eth1, and the second tothe second NIC, such as eth2, andso on. To skip a NIC, type a blankargument.

[--data_ipaddr ipaddr]

NIC and subnet setting.[--nic nic]

Specify tagged assignment. Repeatthis option to specify more than oneassignment. The first tag is as-signed to the first NIC, such aseth1, the second tag is assigned tothe second NIC, such as eth2, andso on. To skip an assignment, entera blank argument.

[--tagged tag]

Include this argument twice. Thenthe first IP address entered is as-signed to Controller A and the sec-ond to Controller B. You must as-sign static IP addresses to allowarray access if the management IPaddress is not accessible.

[--support_ipaddr ipaddr]

Pool to assign the array to. If youspecify this suboption, then thepool must exist. If you do notspecify this suboption or the --cre-ate_pool suboption, then the arrayis assigned to the default pool.

[--pool pool_name]

Create a new storage pool and au-tomatically assign the array to it. Ifyou do not specify this suboptionalong with the --pool suboption,then the array is assigned to thedefault pool.

[--create_pool]




RoleDescriptionArguments and SuboptionsOption[--pool_description pool_descrip-tion]

If you create a new pool for an ar-ray, type a description for the pool.If there are spaces in the descrip-tion, enclose the text in quotationmarks.

If you add an array to an existingpool and the pool's limits are higherthan the array's limits, the resultingpool will have the lower limits of thearray being added, which could al-so change the group limits to lowervalues.

[--allow_lower_limits]

Power Us-er

Name of the array to remove froma group. Use the pool commandto remove the array from any pools.

name--remove

Forcibly remove the specified arrayfrom a group even if it is unreach-able. This may lead to loss of dataif a volume is currently stripedacross disks on the array.

[--force]

Examples

This example displays a list of member arrays.

Nimble OS $ array --list-----------------+---------------+-----------+-----------------+-----------Name Serial Model Version Status-----------------+---------------+-----------+-----------------+-----------c12-array3 AC-100159 CS210 2.0.4.1-44556-opt reachablec12-array6 AC-100209 CS220 2.0.4.1-44556-opt reachable

This example discovers non-member arrays.

Nimble OS $ array --discover-------------+----------+-----------------+--------------------------------Serial Number Model Version Link-Local IP Addresses-------------+----------+-----------------+--------------------------------AC-100159 CS210 2.0.3.8-44640-opt 169.254.8.98, 169.254.8.93...

This example shows information for the array named c20-array1.

Nimble OS $ array --info c20-array1Model: CS220...Array name: c20-array1...Member of pool: defaultStatus: reachable

This example shows information for the array with the serial number AC-102566.

Nimble OS $ array --info AC-102566Model: CS220




Serial: AC-102566...Array name: c20-array1...Member of pool: defaultStatus: reachable

This example renames the MKTG array to Marketing.

Nimble OS $ array --edit MKTG --name Marketing

This example resets a standalone array so the setup command can be run.

Note Use this command option with caution.

Nimble OS $ array --resetupWARNING: This operation will reset the array configuration. Minimize the timebeforerunning setup again to limit I/O disruption. Existing iSCSI connections maybeunaffected, but new iSCSI connections will be refused.Type yes to continue, no to cancel: yesSuccessfully initiated array reset.Minimize the time before running setup again to limit I/O disruption. ExistingiSCSIconnections may be unaffected, but new iSCSI connections will be refused.WARNING: While the volume data and some of the configuration data are preserved,afuture setup of the array could change the group name and the networkconfiguration.This will invalidate the replication partner and the host configuration, whichmaydisrupt replication and iSCSI connections to this array.

This example adds the serial number of an uninitialized array and assigns a new name to the array duringthis process.

Although only one set of name, subnet_label, data_ipaddr, and pool options is required, you can use multiplesets of these options to specify values for more than one NIC on an array, such as eth1, eth2, tg1, tg2.

Nimble OS $ array --add AC-100159 --name c12-array3\

--data_ipaddr '' --subnet_label management \--data_ipaddr '' --subnet_label management \--data_ipaddr 198.51.100.61 --subnet_label data \--data_ipaddr 198.51.100.62 --subnet_label data \--support_ipaddr 10.19.0.57 --support_ipaddr 10.19.0.58

This example removes an existing member array named greydient from a group.

Note The array to remove must not be assigned to a pool. If needed, run pool --unassign to remove the arrayfrom a pool before you run this command.

Nimble OS $ array --remove greydient




auditlogThe auditlog command options manage array audit log entries.

The NimbleOS audit log keeps records of all non-read operations performed on the array, and which userperformed the operation. You can search the audit log by activity and object type/name. You can also filterthe audit log by time range, username, userid, activity category, and access type. Administrators can viewthe audit log in a summary table with faceted browsing by time, activity category, and across access type.

Synopsis

auditlog --help

auditlog --list[--from [[yyyy-]mm-dd,]hh:mm[:ss]][--to [[yyyy-]mm-dd,]hh:mm[:ss]][--username username][--userid userid][--category {provision|protection|dataaccess|useraccess|sysconfig|swupdate}][--access_type {gui|cli|api}]

auditlog --info id

Options



N/A--help





Administra-tor

List all audit log records.N/A--list

List audit logs that start from thespecified time. Use only the time,or use the date and time. For exam-ple, auditlog --list --from08-14,12:10:00 or auditlog--list --from 12:10:00.Use this option with or without the--to option. If used alone, --to isassumed to be now.


List audit logs until the specifiedtime. Use only the time, or use thedate and time. For example,audit-log --list --to 08-14,12:10:00 or auditlog --list --to 12:10:00. Use thisoption with or without the --fromoption.


List audit logs by username.[--username {username}]

List audit logs by userid.[--userid {userid}]

List audit logs of the specified cate-gory.

[--category {provision|protec-tion|dataaccess| userac-cess|sysconfig|swupdate}]

List audit logs using the specifiedaccess type.

[--access_type {gui|cli|api}]

Administra-tor

List detailed information about thespecified audit log ID. To determinevalid audit log IDs, use auditlog--list.

id--info

Examples

This example lists all alert messages on the array where you run the command. The output is truncated tosave space.

Nimble OS $ auditlog --list--------+--------------------+---------------+---------+------------------------ID Time User Status Activity--------+--------------------+---------------+---------+------------------------1 Mar 25 2015 09:10:52 admin Succeeded Login attempt

2 Mar 25 2015 09:10:53 admin Succeeded Complete setup on ...3 Mar 25 2015 09:45:52 admin Succeeded User admin session ...4 Mar 26 2015 13:22:41 Succeeded Logout user

5 Mar 26 2015 13:43:21 Succeeded Logout user






This example lists all alert messages on the array where you run the command, filtered by username. Theoutput is truncated to save space.

Nimble OS $ auditlog --list--username pAdmin--------+--------------------+---------------+---------+------------------------ID Time User Status Activity--------+--------------------+---------------+---------+------------------------

57 Apr 22 2015 11:45:20 pAdmin Succeeded Login attempt

78 Apr 22 2015 13:16:40 pAdmin Succeeded Logout user pAdmin










This example lists information about the audit log with the ID 23.

Nimble OS $ auditlog --info 23ID: 23Type: 8015Object name: vol2Object type: VolumeScope: -Time: Mar 25 2015 09:28:06Status: SucceededError code: SM_http_okUser ID: 3Username: pAdminUser full name: Administrator UserSource IP: 10.20.21.168Access Type: GUIApplication name: GUICategory: Data ProtectionActivity type: otherActivity: Associate volume vol2 with volume collection volcoll2




certThe cert command is used to manage certificates used by a number of components that support SSL/TLS.These include the web GUI interface, the VASA provider, the CIM server, and Group Management RESTAPIs. It is possible to select different certificate chains for each of these. In addition, a list of trusted certificatescan be managed for use by internal clients, for example to provide verification of an external key managerthat presents its own self-signed certificate on connection.

To establish a secure connection with a website or other server, the array presents a certificate to authenticateits identity. Certificates are an important component of the Secure Sockets Layer (SSL), because they preventothers from impersonating a secure website or other server.

The default values used for the subject, dnslist, and iplist are taken from the existing group certificate, if nocorresponding options are provided.

There are three certificate chains that are managed using the cert command: array, group, and custom.

Array certificate chain:The array certificate is generated automatically before group setup.

Group certificate chain:The group certificate is generated after the group leader has been configured.

Custom certificate chain:A custom certificate may also be installed and used. It can be either a self-signed (custom), or a CertificateSigning Request (custom-csr) that can be exported to be signed by a local Certificate Authority (CA). TheCA certificate and the resulting signed custom certificate may then be imported for use.

Synopsis

cert --help

cert --list

cert --info cert-name

cert --gen {array|group|custom|custom-csr}[--subject subject_name][--dnslist dns_list][--iplist ip_list][--num_days days][--check][--force]

cert --import cert-name[--pks12][--password unlock_password][--trusted][--from_host host:port][--force]

cert --delete {cert-name}

cert --use {array|group|custom}[--https][--apis]




cert --verify cert-name[--checkend days][--oscp]

Options


AdministratorShows usage informationfor the command.

N/A--help

AdministratorList each of the certificatesinstalled, and which are be-ing used for HTTPS and APIaccess.

N/A--list

AdministratorPrint output that shows allof the details, as well as thePEM encoding, of the givencertificate or CSR.

{cert-name}--info





AdministratorInitiates the creation of ei-ther a self-signed certificate,or a Certificate Signing Re-quest (CSR). The argumentspecifies whether to createa certificate of the typespecified or to create a CSRfor a custom certificate.Thecustom option generates aself-signed certificate withthe parameters specified,while the custom-csr optiongenerates a CSR with theparameters specified. Acustom certificate and beeither self-signed or signedby an external CertificateAuthority (CA). The arrayand group certificates aregenerated automatically foruse by HTTPS and API ser-vices.

{array|group| custom|custom-csr}

--gen

Subject or common namefor the certificate. The de-fault value for the subjectname will be the groupname. If the value is "-" orthe option is not present,then an attempt is made toextract the subject namefrom the existing group cer-tificate, if there is one. Thevalue is treated as a fullsubject name if it beginswith "/", in the format thatOpenSSL uses. Otherwise,it is taken as the CommonName value.

[--subject subject-name]

A comma separated list ofDNS names to add to thesubject alternate name fieldof the host certificate. If thevalue is "-" or the option isnot specified, an attempt ismade to extract the DNSnames from the existinggroup certificate, if there isone.

[--dnslist dens-list]

[--iplist ip-list]




RoleDescriptionArguments and SuboptionsOptionA comma separated list ofIP addressess to add to thesubject alternate name fieldof the host certificate. If thevalue is "-" or the option isnot specified, an attempt ismade to extract the DNSnames from the existinggroup certificate, if there isone. To specify an empty IPlist, use "--ip-list ''"

Number of days for whichthe certificate will be valid.The default value of thenumber of valid days is3650.

[--num_days days]

Check the current subject,DNS list, and IP list of thecurrent group certificateagainst the provided inputs.A new certificate chain isonly generated if thechecked values do notmatch the group certificatevalues.

[--check]

Force overwriting of an exist-ing certificate chain. Other-wise, the existing certificateis left as is.

[--force]





AdministratorImport a custom CA (cus-tom-ca), signed customcertificate (custom), or atrusted certificate to be usedby internal clients. The cus-tom-ca certificate must beimported before the signedcustom certificate. After thecustom certificate is import-ed and verified, it will be in-stalled for use. The import-ed certificate should be validfor use as both SSL serverand client, since it may beused as an outbound clientcertificate.

A combined bundle of key,CA certificate, and signedcertificate may also be im-ported using the PKCS12format. This format is mostuseful for installing a wild-card certificate.

cert-name--import

AdministratorImport a PKCS12 file thatcontains a private key, CAcertificate(s), and signedhost certificate. Use thecustom command argu-ment.

[--pkcs12]

AdministratorThe password to unlock aPKCS12 input file.

[--password unlock-password]

AdministratorImport a certificate to add tothe list of certificates trustedby internal SSL clients. Thecertificate can either be readfrom standard input, or re-trieved from the specifiedhost. When this flag is set,the names custom-ca,custom, group, and arrayare reserved.

[--trusted]

AdministratorWhen used with the --trust-ed option, attempt an SSLconnection to the specifiedhost and port, and importthe presented certificate tothe trusted certificate list.

[--from_host host:port]

[--force]




RoleDescriptionArguments and SuboptionsOptionForce overwriting of an exist-ing certificate. Otherwise,the existing certificate is leftas is.

AdministratorDelete a certificate, alongwith any associated privatekey and optional certificates.Deleting the array or array-ca certificate is not allowed.

{cert-name}--delete

AdministratorSelect one of the array,group, or custom certificatechains to use for HTTPSaccess or API use.

Use the named certificatefor HTTPS service.

Use the named certificatechain for access to NimbleAPIs (REST and internalNimble APIs).

{array|group|custom}

[--https]

[--apis]

--use

AdministratorVerify the signature, expira-tion time, and (optionally)the OCSP status of thenamed certificate. Whenused with no suboptions,verify the signature andwhether the certificate hasexpired.

cert-name--verify

AdministratorCheck if the certificate ex-pires withing the specifiednumber of days. If notpresent, the default value is0.

[--checkend days]

AdministratorIf the certificate as an OSCPreference included, contacttheOSCPservice and deter-mine the status of the certifi-cate.

[--oscp]

Examples

To create and install a custom certificate on an array, you must perform the following steps from an sshsession:

Nimble OS $ cert --gen custom-csr --subject '/C=US/ST=CA/L=San Jose/O=NimbleStorage/OU=Engineering/CN=AF106656' --dnslistgroup-kent-vma.nimblestorage.com,kent-vma.nimblestorage.com

-----BEGIN CERTIFICATE REQUEST-----MIICuTCCAaECAQAwWDELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMREwDwYDVQQHDAhTYW4gSm9zZTEXMBUGA1UECgwOTmltYmxlIFN0b3JhZ2UxEDAOBgNVBAMMB2xuLWtlbnQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQD1p+rdq/GvuALc




qqam6AIoKfC8X4WFN+xOSmco7cQliZnmYNyX1Rzrw0RyIYwfBOeSff+47pw6Hv6STY54lMMf7/5vMmEoR56DaolkI9RgmMnQM8Ay6YnRjWZtE7TFRiId+r7cYlPlREWd0Mq25psKqEaNl8QzNVFhxOdPCe//cP6Z91R2GanR+cafAmSZ8ELfkFvdlWnU5VdvcCHH73IkHtZbgWVy9yJJ2ZZT9Lv31rPjx2rP+h305VrWWa7xWyTI0FD86y5n41ZnYx8ypE8E0dcSENlNX9evRzGyPfhIg11JaHTkad/REpAwXSDilEcl4/0jRfKBaq/MYD6U1Z8tAgMBAAGgHDAaBgkqhkiG9w0BCQ4xDTALMAkGA1UdEQQCMAAwDQYJKoZIhvcNAQEFBQADggEBABcwx0s4dvaBbVv2NYNs/tYq/pwynGcF19+MIVtrCxoYQ3h3MObHTu0k0+LgWNZeJKDfD2AKHGnQMjP1lWqHqbZLwxbioFotxIYd/XwIMSlshBLSWegYzrCbfDTeQMLV7XozIfcGEUZzQF+hSY7SPJGLRZTHCAl/hD0LXthl6fUB2ynZQsjA3q38+OV/H37vkXA0jY5oxFcPwPGGh6jLVMBspY2OHnxGiUIEganpxk3XtOAhbYdvo88B0WRV7chDfL2/VzythDL8vOPxSsY8leCdXOq8dnUb2t5Yo8cBqc2J58ONHiDL7gI4YR/EafXDuHJwGnqMqGGlddktAQkTWWI=-----END CERTIFICATE REQUEST-----

You must then cut-and-paste the certificate request output into a signing request to the CA.

Then cut-and-paste the CA certificate and the output from the signing into the command inputs below:

Nimble OS $ cert --import custom-caNimble OS $ cert --import custom

-----BEGIN CERTIFICATE-----MIIEADCCAuigAwIBAgIJALkB09sKkc1IMA0GCSqGSIb3DQEBBQUAMF0xCzAJBgNVBAYTAlVTMQswCQYDVQQIDAJDQTERMA8GA1UEBwwIU2FuIEpvc2UxFzAVBgNVBAoMDk5pbWJsZSBTdG9yYWdlMRUwEwYDVQQDDAxrZW50YXJyYXktQ0EwHhcNMTUwNjIyMjIxNDMxWhcNMjUwNjE5MjIxNDMxWjBdMQswCQYDVQQGEwJVUzELMAkGA1UECAwCQ0ExETAPBgNVBAcMCFNhbiBKb3NlMRcwFQYDVQQKDA5OaW1ibGUgU3RvcmFnZTEVMBMGA1UEAwwMa2VudGFycmF5LUNBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmLA18pIh44mkgGPll9jpey+IXso+mwJAckrfgxh8Z7+54L9K5/sGy4FenN8+DsPc7qtNl1lnQ0nptkDjmQph3sV34NB1nOg+cI+pSMRC1kZk2ZAfW0xWeJJI/JBTQFWOzbe2PgmJNMN0gMI8eeco9PmR3n9+WEGsos6SsUsW/WHSNo41ujuZV0wmLmLP/mv1WuoUWpDZwyzk0uovSihkcTbCihm7yHYpKMxvYMy88/Hea7rBbQaid9z/xceEZ6cnEotZcEyJP+u0Z7FMiPfzcPY77XV1IsiVB1eVohOP1GURlD2J9v1XIi1U1H98R4vGeynI7rjxo7dhsZu1K9xVIwIDAQABo4HCMIG/MB0GA1UdDgQWBBShBlOmmIP2S84mJ3wTMoWJgEYumzCBjwYDVR0jBIGHMIGEgBShBlOmmIP2S84mJ3wTMoWJgEYum6FhpF8wXTELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMREwDwYDVQQHDAhTYW4gSm9zZTEXMBUGA1UECgwOTmltYmxlIFN0b3JhZ2UxFTATBgNVBAMMDGtlbnRhcnJheS1DQYIJALkB09sKkc1IMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAGTzXWDcMI/OnP/KerhpGPfns0VUMzvvYaKn5Db5ADEPL5vafawhsOyTMgnu7hwiL11Zy6qJ+e0g85Zm0v0mg4wKyM3QKvbf86lu8YKvEoYoCWcOcsRDt2ijrbx7IkRyXOypI0nIN76vNQpo1NtZ+e3XvzAShrFdZNtsi8ILZqEOepr/PBNJOv1hAszvCpcZ6uBMxodez2lHT7ceb5ZxYJZnOoNkLTMKp9MV7Qt0v8xDKWMy9ED9PuJ79f+vpzmJPTcv2pFHrMoPXqZFxXVTXk5GwjORGlbqvAdsGexZ3vqbmfgQvVuDdw9Zd60vqkg4gT6MJsnfdgsOgpRg5/4CRao=-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----MIIDhTCCAm2gAwIBAgIJAId2ciTqy7mCMA0GCSqGSIb3DQEBBQUAMF0xCzAJBgNVBAYTAlVTMQswCQYDVQQIDAJDQTERMA8GA1UEBwwIU2FuIEpvc2UxFzAVBgNVBAoMDk5pbWJsZSBTdG9yYWdlMRUwEwYDVQQDDAxrZW50YXJyYXktQ0EwHhcNMTUwNjIyMjIxNDMyWhcNMjUwNjE5MjIxNDMyWjBYMQswCQYDVQQGEwJVUzELMAkGA1UECAwCQ0ExETAPBgNVBAcMCFNhbiBKb3NlMRcwFQYDVQQKDA5OaW1ibGUgU3RvcmFnZTEQMA4GA1UEAwwHbG4ta2VudDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAPWn6t2r8a+4AtyqpqboAigp8LxfhYU37E5KZyjtxCWJmeZg3JfVHOvDRHIhjB8E55J9/7junDoe/pJNjniUwx/v/m8yYShHnoNqiWQj1GCYydAzwDLpidGNZm0TtMVGIh36vtxiU+VERZ3QyrbmmwqoRo2XxDM1UWHE508J7/9w/pn3VHYZqdH5xp8CZJnwQt+QW92VadTlV29wIcfvciQe1luBZXL3IknZllP0u/fWs+PHas/6HfTlWtZZrvFbJMjQUPzrLmfjVmdjHzKkTwTR1xIQ2U1f169HMbI9+EiDXUlodORp39ESkDBdIOKURyXj/SNF8oFqr8xgPpTVny0CAwEAAaNNMEswCQYDVR0TBAIwADAdBgNVHQ4EFgQUdudH4pEro5KcsujvyGr728sKSyAwHwYDVR0jBBgwFoAUoQZTppiD9kvOJid8EzKFiYBGLpswDQYJKoZIhvcNAQEFBQADggEBAJcsLauYn1AmaApF4uag6kljGls2K2qm




DNBQy2w2IWM9ffxSR+j0DhVgbgHQrMkTwCy9pgFAXS9MXCVF3BfLW1J9UdZXmegtAsITa9xDthJqMwvweT7s3Gzwlc8zRXZOCXe79+YF3sZhWlFV5E1ex1iHmIwA7x9TTwe4timzAsyjKQFOSm8ggQxbizoTDXpehiDgSDxzqL+8wggi13sC4ibAgGDzGAvCu4EwtNlluIKBGnDHaGyfxv8ZT0jkHEB/KTFZAq8a0TVRZHi9TpnGszNcA9aV8ZKCVHZPdBqjcDJBjFiLFZa9palRHIl3Q3laLVU+lEQZhD0M/x0TZwvPIUY=-----END CERTIFICATE-----

The following example is used to change APIs to use the group certificate.

Display the current status.

sjc-array289-A:/# cert --listName Subject===================array: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=AF-106720group: /C=US/ST=CA/L=San Jose/O=NimbleStorage/CN=sjc-array289.WIN2K8R2AD.NETcustom: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=sjc-array289-Acustom-csr: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=sjc-array289-A

Use Name===================HTTPS: customAPIs: custom

Run the command to change APIs to use the group certificate.

sjc-array289-A:/# cert --use group --apisINFO: group certificate chain installed for API use

Run the command to display the updated status.

sjc-array289-A:/# cert --listName Subject===================array: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=AF-106720group: /C=US/ST=CA/L=San Jose/O=NimbleStorage/CN=sjc-array289.WIN2K8R2AD.NETcustom: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=sjc-array289-Acustom-csr: /C=US/ST=CA/L=San Jose/O=Nimble Storage/CN=sjc-array289-A

Use Name===================HTTPS: customAPIs: group




chapuser

Synopsis

The chapuser command options manage Challenge-Response Handshake Authentication Protocol (CHAP)user accounts. CHAP users are one method of access control for iSCSI initiators. Each CHAP user has aCHAP password, sometimes called a CHAP secret.

CHAP passwords must be the same on the array and the iSCSI initiator before the array can authenticatethe iSCSI initiator and permit access. The CHAP user information must exist on both the array and the iSCSIinitiator. Target authentication provides security only for a specific iSCSI target. Multiple iSCSI initiators canuse the same CHAP secret when connecting or each iSCSI initiator can have its own. The CHAP user namecannot include certain special characters.

Arrays that use the Fibre Channel protocol do not require CHAP user accounts.

chapuser --help

chapuser --list

chapuser --info user_name

chapuser --create user_name--password password[--description text]

chapuser --delete user_name[--force]

chapuser --edit user_name[--name new_name][--description text][--password password]

chapuser --add_initators user_name[--initiator_name iqn]

chapuser --remove_initator user_name[initiator_name iqn]

Options



N/A--help

OperatorList all configured CHAP users forthis array.

N/A--list

OperatorShow information about a specificCHAP user.

user_name--info





OperatorCreate a new CHAP user andshared password for the CHAPuser, who then gets assigned to anaccess control list (ACL)-associat-ed volume. CHAP user authentica-tion requires a CHAP secret thatagrees as the challenge response.

user_name--create

The CHAP secret. The CHAP se-cret must be must be between 12and 16 alphanumeric characters,with no spaces or special charac-ters, including ' " ` ~ ! @ # $ ^ & ( )+ [ ] {} * ; : ' " . , | < > ? / \ = % .

--password password

Plain-text description of the CHAPuser. If there are spaces in the de-scription, enclose the text in quota-tion marks.

[--description text]

OperatorDelete the specified CHAP user. Itdeletes the CHAP user connectionfrom the iSCSI initiator. If the CHAPuser is assigned to any accesscontrol records, you must use the--force to delete.

user_name--delete

Forcibly delete the specified CHAPuser even if that user has activeconnections. It disregards any ACLrecords that have been applied.

[--force]

OperatorModify the name of the CHAP user.Changing the CHAP user namerequires reconfiguring the iSCSIinitiators to use the newCHAP username.

user_name [--name new_name]--edit

Modify the description of the CHAPuser. If there are spaces in the de-scription, enclose the text in quota-tion marks.

user_name [--description text]

Modify the CHAP secret (sharedpassword) used by the a CHAPuser. This value must be between12 and 16 alphanumeric charac-ters, with no spaces or specialcharacters, including ' " ` ~ ! @ # $^ & ( ) + [ ] {} * ; : ' " . , | < > ? / \ =%

user_name [--password password]





OperatorUse --add_initiators to associatethe specified CHAP user to specificiSCSI initiators. iSCSI Group Tar-get uses this information to authen-ticate CHAP access to iSCSI initia-tors.

user_name--add_initiators

Associate this CHAP user to thespecified iSCSI initiators. If anyspecified initiator is already associ-ated with another CHAP user, thatuser will be replaced by this CHAPuser for future CHAP authentica-tion.

[--initiator_nameiqn]

Use --remove_initiator to disassoci-ate the CHAP user from a specificiSCSI initiator. iSCSI Group Targetwill not do CHAP authentication tothis iSCSI initiator.

user_name--remove_initiator

Disassociate the CHAP user fromthe specified iSCSI initiator. iSCSIGroup Target will not do CHAPauthentication to this iSCSI initiator.

[--initiator_nameiqn]

Examples

This example lists CHAP users in the array. In this example, two CHAP users exist.

Nimble OS $ chapuser --list------------------------------+--------------------------------------------CHAP User Name Password------------------------------+--------------------------------------------nimblechap nimblechapuserguestchap minimalaccess

This example shows information about a CHAP user named "nimblechap".

Nimble OS $ chapuser --info nimblechapName: nimblechapDescription: generic chap user for the nimble arrayPassword: nimblechapuserCreated: Dec 17 2010 12:50:25Last configuration change: Dec 17 2010 12:50:25

This example creates a CHAP user with the name "nimblestorage" and a valid password.

Nimble OS $ chapuser --create nimblestorage--description "nimble storage user" --password n1mblechapu5er

This example forcibly deletes a CHAP user named "storageuser".

Nimble OS $ chapuser --delete storageuser --force

This examplemodifies the name, description, and password for the CHAP user previously named "nimblechap".




Note If you change the name or password of a CHAP user, it invalidates logins. Update the hosts with thechange.

Nimble OS $ chapuser --edit nimblechap --name nimchap--description "nimble user" --password nimchapusr




ctrlrThe ctrlr command options display information about a controller on a Nimble array. Each array has an Aand B controller (case-sensitive identifiers). One controller is always active and the other always takes thestandby role. Controllers share IP addresses except for the support IP address. Each controller is alsoconfigured with the same set of NICs to provide redundancy in case of a failure. This configuration ensuresthat there is never a conflict during a failover. The IP addresses that are assigned to each NIC and interfaceremain the same. If a failover is triggered, then the new active controller has the same number of links to theswitch as was the case before a failover occurred.

Synopsis

ctrlr --help

ctrlr --list[--array array_name]

ctrlr --info controller_name[--array array_name]

Options



N/A--help

GuestList basic information about thecontrollers in the array where youare logged in.

--list

List basic information about allcontrollers on the specified array.

[--array array_name]

GuestList detailed information about thespecified controller. Valid controllernames are A and B, which are casesensitive.

controller_name--info

List detailed information about thespecified controller on the specifiedarray.


Examples

This example lists basic information about the controllers on an array named greyhound.

Nimble OS $ ctrlr --list --array greyhound----+----------+--------------------+----------------+--------+-------+--------Name State Hostname Support IP Power Fans Temper-

Supplies Status -ature

Status Status----+----------+--------------------+----------------+--------+-------+--------A standby greyhound-A 192.0.2.54 alerted OK OKB active greyhound-B 192.0.2.55 alerted OK OK




This example shows information about controller B on an array named greyhound.

Nimble OS $ ctrlr --info B --array greyhoundName: BSerial number: AC-102724-C2State: activeHostname: greyhound-BSupport IP address: 192.0.2.55Support IP netmask: 255.255.255.0Support IP nic: eth1Hostname:Power supply: alerted

power-supply1 at left rear: okpower-supply2 at right rear: missing

Cooling fans: OKfan1 at lower front of controller B: ok, speed: 10608rpmfan2 at lower left rear of controller B: ok, speed: 10608rpmfan3 at lower right rear of controller B: ok, speed: 10608rpmfan4 at upper right front of controller B: ok, speed: 8295rpmfan5 at upper left front of controller B: ok, speed: 8910rpmfan6 at upper left rear of controller B: ok, speed: 8520rpm

Temperature sensors: OKmotherboard at motherboard: ok, temperature: 22Cbp-temp2 at right-side backplane: ok, temperature: 34C

System partition status: OKLast AutoSupport contact: N/A




dateThe date command options display or modify the date and time of the array. If the array is connected to avalid NTP server IP address, then the time settings on the array synchronize with the time settings on theNTP server. In this case, do not modify the date locally. However, if the array is connected to an invalid NTPserver IP address, then the time settings on the array do not synchronize with the time settings on the NTPserver.

Synopsis

date --help

date[--utc][--edit {hh:mm[:ss]|'YYYY-MM-DD hh:mm[:ss]']

Options



N/A--help

GuestList the Coordinated UniversalTime on an array.

N/A--utc

Power Us-er

Use --edit with care. Modify thedate and time on an array and dis-able the connection between thearray and a previously specifiedNTP server. If specified with --utc,modify Coordinated Universal Timeto the supplied argument.

{hh:mm[:ss]|'YYYY-MM-DDhh:mm[:ss]''

--edit

Examples

This example lists the date and time on an array as Pacific Daylight Time.

Nimble OS $ dateWed Jul 9 15:29:59 PDT 2014

This example lists the date and time on an array as Coordinated Universal Time.

Nimble OS $ date --utcWed Jul 9 22:29:37 UTC 2014

This example modifies the date and time on an array.

Nimble OS $ date --edit '2013-07-08 15:33:27'WARNING: Setting date manually disables the NTP server setting




diskThe disk command options manage disks on an array. An array supports hard disk drives (HDDs) and solidstate drives (SSDs). The size of the disk depends on the array model. Some HDDs are used to build theRAID and others can be spares that are used to replace failing drives. SSDs can only be active, and they arenot part of the RAID configuration.

When you remove a hard disk drive (HDD) from an array, it is either removed from the existing RAID orreplaced as a spare, depending on the state of the RAID. If you remove a solid state disk (SSD), it is removedfrom the existing cache capacity.

Synopsis

disk --help

disk --list[--array array_name][--shelf_location shelf_location]

disk --info slot[--array array_name][--shelf_location shelf_location]

disk --add slot[--array array_name]--shelf_location shelf_location[--force]

disk --remove slot[--array name]--shelf_locationshelf_location

Options



N/A--help

GuestList basic information about thedisks on an array, showing thetype, slot, serial number, size, diskstate, RAID status, shelf serialnumber, and shelf location foreach.

--list

List basic information about thedisks on the specified array. Speci-fy this option in a multi-array config-uration. It is optional in a single-ar-ray configuration.


List basic information about thedisks on the specified shelf. If thisoption is not specified, then alldisks on all shelves are listed.

[--shelf_location shelf_location]





GuestList detailed information about thedisk at a specified slot number in asingle-array configuration.

slot--info

List detailed information about alldisks for a specified array in amulti- array configuration. Includethis option in a multi-array configu-ration. It is optional in a single-arrayconfiguration.


List detailed information about thedisk at the specified shelf location.If this option is not specified, thenonly disks for the head shelf A (A.0)or B (B.0) are listed.

[--shelf_location shelf_location]

Power Us-er

Add a disk at the specified slot ona single-array configuration.

slot--add

Add a disk at the specified slot ona multi-array configuration. Includethis option in a multi-array configu-ration. It is optional in a single-arrayconfiguration.


Add a disk at the specified shelflocation on a specified array. Thisoption is mandatory.

--shelf_location shelf_location

Forcibly add the specified disk. Thisoption is mandatory if the disk toadd is in a foreign state.

[--force]

Power Us-er

Remove a disk from the specifiedslot in a single-array configuration.

slot--remove

Remove a disk from the specifiedslot on a specified array in a multi-array configuration. Include thisoption in a multi-array configura-tion. It is optional in a single-arrayconfiguration.


Remove a disk from the specifiedslot on the specified shelf location.This option is mandatory.

--shelf_locationshelf_location

Examples

This example lists all disks on a standalone (single) array.

Nimble OS $ disk --list------+--------------------+----+---------+-------+--------+---------+-----Slot # Serial # Type Disk Size Disk RAID Shelf Shelf

(GB) State Status Serial Loca--tion

------+--------------------+----+---------+-------+--------+---------+-----




1 WD-WCAW32373319 HDD 1000.20 in use spare AA-100257 A.02 WD-WCAW30555873 HDD 1000.20 in use okay AA-100257 A.03 WD-WMAW30010098 HDD 1000.20 in use okay AA-100257 A.04 WD-WCAW30549295 HDD 1000.20 in use okay AA-100257 A.05 N/A N/A N/A void N/A AA-100257 A.06 N/A N/A N/A void N/A AA-100257 A.07 N/A N/A N/A void N/A AA-100257 A.08 CVPO040402ZP080JGN SSD 80.03 in use N/A AA-100257 A.09 CVPO04030150080JGN SSD 80.03 in use N/A AA-100257 A.010 N/A N/A N/A void N/A AA-100257 A.011 N/A N/A N/A void N/A AA-100257 A.012 N/A N/A N/A void N/A AA-100257 A.013 WD-WCAW30597086 HDD 1000.20 in use okay AA-100257 A.014 WD-WCAW30606284 HDD 1000.20 in use okay AA-100257 A.015 WD-WCAW30606703 HDD 1000.20 in use okay AA-100257 A.016 WD-WCAW30527176 HDD 1000.20 in use okay AA-100257 A.01 CVPR208103WZ600FGN SSD 600.13 in use N/A AC-100182 A.12 Z29036W600009136H45Q HDD 3000.59 in use okay AC-100182 A.13 Z290LRCK00009136H440 HDD 3000.59 in use spare AC-100182 A.14 9XK0H5N600009135E6GN HDD 3000.59 in use okay AC-100182 A.15 9XK06BFJ0000S111K944 HDD 3000.59 in use okay AC-100182 A.16 Z290LAW80000S110DX86 HDD 3000.59 in use okay AC-100182 A.17 Z290372V0000914024J2 HDD 3000.59 in use okay AC-100182 A.18 9XK0KBZ400009131N1NV HDD 3000.59 in use okay AC-100182 A.19 Z2909KED00009133BHZ5 HDD 3000.59 in use okay AC-100182 A.110 Z290KYG600009138MTYB HDD 3000.59 in use okay AC-100182 A.111 Z290LNP9000091380XUM HDD 3000.59 in use okay AC-100182 A.112 9XK06NF00000S111K9X6 HDD 3000.59 in use okay AC-100182 A.113 9XK07TQN0000S112MQAQ HDD 3000.59 in use okay AC-100182 A.114 9XK06B6G0000S111K9MH HDD 3000.59 in use okay AC-100182 A.115 9XK06AYR0000S110UGRY HDD 3000.59 in use okay AC-100182 A.116 9XK06NEP0000S110UGCD HDD 3000.59 in use okay AC-100182 A.1

This example lists only the disks on the specified shelf.

Nimble OS $ disk --list --shelf_location A.0------+--------------------+----+---------+-------+--------+---------+-----Slot # Serial # Type Disk Size Disk RAID Shelf Shelf


------+--------------------+----+---------+-------+--------+---------+-----1 WD-WCAW32373319 HDD 1000.20 in use spare AA-100257 A.02 WD-WCAW30555873 HDD 1000.20 in use okay AA-100257 A.03 WD-WMAW30010098 HDD 1000.20 in use okay AA-100257 A.04 WD-WCAW30549295 HDD 1000.20 in use okay AA-100257 A.05 N/A N/A N/A void N/A AA-100257 A.06 N/A N/A N/A void N/A AA-100257 A.07 N/A N/A N/A void N/A AA-100257 A.08 CVPO040402ZP080JGN SSD 80.03 in use N/A AA-100257 A.09 CVPO04030150080JGN SSD 80.03 in use N/A AA-100257 A.010 N/A N/A N/A void N/A AA-100257 A.011 N/A N/A N/A void N/A AA-100257 A.012 N/A N/A N/A void N/A AA-100257 A.013 WD-WCAW30597086 HDD 1000.20 in use okay AA-100257 A.014 WD-WCAW30606284 HDD 1000.20 in use okay AA-100257 A.015 WD-WCAW30606703 HDD 1000.20 in use okay AA-100257 A.016 WD-WCAW30527176 HDD 1000.20 in use okay AA-100257 A.0

This example shows information about the hard disk drive in slot 1 in a single-array configuration. The outputis truncated to avoid line wrapping.




Nimble OS $ disk --info 1Shelf location #: A.0Slot #: 1HBA: 0Port: 15Serial: WD-WCAW32373319Type: HDDDisk size: 1000.2 GBDisk state: in useRaid state: sparePercent resynchronized: N/ACurrent resync speed: N/AAverage resync speed: N/AModel: WDC WD1003FBYX-0Vendor: NimbleFirmware version: 1V01Smart Data Attributes:Raw read error rate(value/trough/threshold/raw/updated): 200/200/51/5/Ju...Spin up time(value/trough/threshold/raw/updated): 174/172/21/4291/Jul 15...Start stop count(value/trough/threshold/raw/updated): 100/100/0/393/Jul ...Reallocated sector count(value/trough/threshold/raw/updated): 200/200/1 ...Seek error rate(value/trough/threshold/raw/updated): 200/200/0/0/Jul 15 ...Power on hours(value/trough/threshold/raw/updated): 91/91/0/6890/Jul 15 ...Power cycle count(value/trough/threshold/raw/updated): 100/100/0/392/Jul...Power off retract count(value/trough/threshold/raw/updated): 200/200/0/3...Temperature C(value/trough/threshold/raw/updated): 116/99/0/31/Jul 15 20...Current pending sector(value/trough/threshold/raw/updated): 200/200/0/0/...Offline uncorrectable(value/trough/threshold/raw/updated): 200/200/0/0/ ...UDMA CRC error count(value/trough/threshold/raw/updated): 200/200/0/0/Ju...

This example shows information about the disk in slot 1. Because the --shelf_location option is specified inthis example, only the disks that are located in slot 1 at the specified shelf location are listed. The output istruncated to avoid line wrapping.

Nimble OS $ disk --info 1 --shelf_location A.1Shelf location #: A.1Slot #: 1HBA: 0Port: 15Serial: CVPR208103WZ600FGNType: SSDDisk size: 600.127 GBDisk state: in useRaid state: N/APercent resynchronized: N/ACurrent resync speed: N/AAverage resync speed: N/AModel: INTEL SSDSA2CW60Vendor: NimbleFirmware version: 0362Smart Data Attributes:Spin up time(value/trough/threshold/raw/updated): 100/100/0/0/Jul 15 201...Start stop count(value/trough/threshold/raw/updated): 100/100/0/0/Jul 15...Reallocated sector count(value/trough/threshold/raw/updated): 100/100/0/...Power on hours(value/trough/threshold/raw/updated): 100/100/0/10495/Jul ...Power cycle count(value/trough/threshold/raw/updated): 100/100/0/27/Jul ...Power off retract count(value/trough/threshold/raw/updated): 100/100/0/2...Host write count(value/trough/threshold/raw/updated): 100/100/0/344912/J...Available reserved space(value/trough/threshold/raw/updated): 100/100/10...Media wearout indicator(value/trough/threshold/raw/updated): 99/99/0/0/J...




This example adds a disk to slot 13 at the specified shelf location A.0 and verifies the change in a single-arrayconfiguration. The disk resynchronizes with the rest of the array. The --shelf_location option is mandatory inthis example.

Nimble OS $ disk --add 13 --shelf_location A.0Nimble OS $ disk --list------+--------------------+----+---------+-------+--------+---------+-----Slot # Serial # Type Disk Size Disk RAID Shelf Shelf


------+--------------------+----+---------+-------+--------+---------+-----1 WD-WCAW32373319 HDD 1000.20 in use okay AA-100257 A.02 WD-WCAW30555873 HDD 1000.20 in use okay AA-100257 A.03 WD-WMAW30010098 HDD 1000.20 in use okay AA-100257 A.04 WD-WCAW30549295 HDD 1000.20 in use okay AA-100257 A.05 N/A N/A N/A void N/A AA-100257 A.06 N/A N/A N/A void N/A AA-100257 A.07 N/A N/A N/A void N/A AA-100257 A.08 CVPO040402ZP080JGN SSD 80.03 in use N/A AA-100257 A.09 CVPO04030150080JGN SSD 80.03 in use N/A AA-100257 A.010 N/A N/A N/A void N/A AA-100257 A.011 N/A N/A N/A void N/A AA-100257 A.012 N/A N/A N/A void N/A AA-100257 A.013 WD-WCAW30597086 HDD 1000.20 in use spare AA-100257 A.014 WD-WCAW30606284 HDD 1000.20 in use okay AA-100257 A.015 WD-WCAW30606703 HDD 1000.20 in use okay AA-100257 A.016 WD-WCAW30527176 HDD 1000.20 in use okay AA-100257 A.0

This example removes a disk from slot 13 at the specified shelf location A.0 and verifies the change in asingle-array configuration. The --shelf_location option is mandatory in this example.

Nimble OS $ disk --remove 13 --shelf_location A.0Nimble OS $ disk --list------+--------------------+----+---------+-------+------------------+-----Slot # Serial # Type Disk Size Disk RAID Shelf Shelf


------+--------------------+----+---------+-------+--------+---------+-----1 WD-WCAW32373319 HDD 1000.20 in use resynch AA-100257 A.02 WD-WCAW30555873 HDD 1000.20 in use okay AA-100257 A.03 WD-WMAW30010098 HDD 1000.20 in use okay AA-100257 A.04 WD-WCAW30549295 HDD 1000.20 in use okay AA-100257 A.05 N/A N/A N/A void N/A AA-100257 A.06 N/A N/A N/A void N/A AA-100257 A.07 N/A N/A N/A void N/A AA-100257 A.08 CVPO040402ZP080JGN SSD 80.03 in use N/A AA-100257 A.09 CVPO04030150080JGN SSD 80.03 in use N/A AA-100257 A.010 N/A N/A N/A void N/A AA-100257 A.011 N/A N/A N/A void N/A AA-100257 A.012 N/A N/A N/A void N/A AA-100257 A.013 WD-WCAW30597086 HDD 1000.20 removed N/A AA-100257 A.014 WD-WCAW30606284 HDD 1000.20 in use okay AA-100257 A.015 WD-WCAW30606703 HDD 1000.20 in use okay AA-100257 A.016 WD-WCAW30527176 HDD 1000.20 in use okay AA-100257 A.01 CVPR208103WZ600FGN SSD 600.13 in use N/A AC-100182 A.12 Z29036W600009136H45Q HDD 3000.59 in use okay AC-100182 A.13 Z290LRCK00009136H440 HDD 3000.59 in use spare AC-100182 A.14 9XK0H5N600009135E6GN HDD 3000.59 in use okay AC-100182 A.15 9XK06BFJ0000S111K944 HDD 3000.59 in use okay AC-100182 A.16 Z290LAW80000S110DX86 HDD 3000.59 in use okay AC-100182 A.17 Z290372V0000914024J2 HDD 3000.59 in use okay AC-100182 A.18 9XK0KBZ400009131N1NV HDD 3000.59 in use okay AC-100182 A.1




9 Z2909KED00009133BHZ5 HDD 3000.59 in use okay AC-100182 A.110 Z290KYG600009138MTYB HDD 3000.59 in use okay AC-100182 A.111 Z290LNP9000091380XUM HDD 3000.59 in use okay AC-100182 A.112 9XK06NF00000S111K9X6 HDD 3000.59 in use okay AC-100182 A.113 9XK07TQN0000S112MQAQ HDD 3000.59 in use okay AC-100182 A.114 9XK06B6G0000S111K9MH HDD 3000.59 in use okay AC-100182 A.115 9XK06AYR0000S110UGRY HDD 3000.59 in use okay AC-100182 A.116 9XK06NEP0000S110UGCD HDD 3000.59 in use okay AC-100182 A.1




encryptkeyThe encryptkey command options manage the encryption master key and its associated passphrase.

The master key is protected by a passphrase and is used to encrypt the keys that are used to encrypt volumedata. This command provides options to cr

Documents

CommandReference - infosight.hpe.com · Onset time: Oct 20 2016 16:49:30 Array: - Object type: volume Object name: test Description: Volume test string from alert gen space usage