Exit status
This table lists the exit statuses that might be returned and the meaning of each status.
| Status Value | Error Name | Meaning | 
|---|---|---|
| 0 | SUCCESSFUL | The command terminated without an error. | 
| 1 | INVALID_USAGE | The command terminated with an error. Information about the error also appears. | 
| 2 | SCRIPT_FILE_DOES_NOT_EXIST | The script file does not exist. | 
| 3 | ERROR_OPENING_OUTPUT_FILE | An error occurred while opening an output file. | 
| 4 | NO_STORAGE_ARRAY_AT_ADDRESS | A storage array was not at the specified address. | 
| 5 | ADDRESSES_SPECIFY_DIFFERENT_ARRAYS | Addresses specify different storage arrays. | 
| 6 | NO_SANAME_FOR_HOST_AGENT_CONNECT | A storage array name does not exist for the host agent that is connected. | 
| 7 | SANAME_NOT_AT_ADDRESS | The storage array name was not at the specified address. | 
| 8 | SANAME_NOT_UNIQUE | The storage array name was not unique. | 
| 9 | SANAME_NOT_IN_CONFIG_FILES | The storage array name was not in the configuration file. | 
| 10 | NO_MANAGEMENT_CLASS_FOR_SA | A management class does not exist for the storage array. | 
| 11 | NO_SA_IN_CONFIG_FILE_FOUND | A storage array was not found in the configuration file. | 
| 12 | INTERNAL_ERROR | An internal error occurred. This exit status indicates that you do not have privileges for running a CLI command from the command line. You must have administrator privileges to run all of the CLI commands from a command line.  | 
| 13 | INVALID_SCRIPT_SYNTAX | Invalid script syntax was found. | 
| 14 | UNABLE_TO_COMMUNICATE | The controller was unable to communicate with the storage array. | 
| 15 | DUPLICATE_ARGUMENT | A duplicate argument was entered. | 
| 16 | EXECUTION_ERROR | An execution error occurred. | 
| 17 | NO_HOST_AT_ADDRESS | A host was not at the specified address. | 
| 18 | WWNAME_NOT_IN_CONFIG_FILES | The WWID was not in the configuration file. | 
| 19 | WWNAME_NOT_AT_ADDRESS | The WWID was not at the address. | 
| 20 | UNKNOWN_IP | An unknown IP address was specified. | 
| 21 | PM_CONFIG_FILE_CORRUPTED | The Event Monitor configuration file was corrupted. | 
| 22 | UNABLE_TO_COMMUNICATE_TO_PM | The storage array was unable to communicate with the Event Monitor. | 
| 23 | UNEXIST_ALERT | The controller was unable to write alert settings. | 
| 24 | WRONG_ORGANIZER_NODE | The wrong organizer node was specified. | 
| 25 | CMD_NOT_AVAILABLE | The command was not available. | 
| 26 | DEVICE_NOT_IN_CONFIG_FILE | The device was not in the configuration file. | 
| 27 | ERROR_UPDATING_CONFIG_FILE | An error occurred while updating the configuration file. | 
| 28 | UNKNOWN_HOST_ERROR | An unknown host error occurred. | 
| 29 | SENDER_CONTACT_FILE_NOT_FOUND | The sender contact information file was not found. | 
| 30 | READ_SENDER_CONTACT_FILE_FAILED | The sender contact information file could not be read. | 
| 31 | USERDATA_FILE_EXISTS | The userdata.txt file exists. | 
| 32 | BAD_EMAIL_INFORMATION_TO_INCLUDE | An invalid -I value in the email alert notification was specified. | 
| 33 | BAD_EMAIL_FREQUENCY | An invalid -f value in the email alert notification was specified. | 
| 34 | OPTION_REMOVED | The -r option is not supported anymore. | 
| 35 | UNKNOWN_ALERT_PRIORITY | Invalid alert severity specified. | 
| 36 | PASSWORD_REQUIRED | The operation needs either the Administrator or Monitor password to be set. | 
| 37 | INVALID_MONITOR_PASSWORD | The operation cannot be completed because an invalid Monitor password was entered. | 
| 38 | INVALID_ADMIN_PASSWORD | The operation cannot be completed because an invalid Administrator password was entered. | 
| 39 | EXCEEDED_MAX_CHARS_FOR_PASSWORD | The password provided is exceeding the character limit. | 
| 40 | INVALID_MONITOR_TOKEN | The -R monitor is not supported for this array. Use a valid role and retry the operation. | 
| 41 | ASUP_CONFIG_ERROR | An error occurred while writing to or reading from the AutoSupport configuration file. Please retry this operation again. | 
| 42 | MAIL_SERVER_UNKNOWN | Host address or mail server address is incorrect. | 
| 43 | ASUP_SMTP_REPLY_ADDRESS_REQUIRED | No healthy ASUP enabled arrays detected while attempting ASUP configuration test. | 
| 44 | NO_ASUP_ARRAYS_DETECTED | Reply email request required if ASUP delivery type is SMTP. | 
| 45 | ASUP_INVALID_MAIL_RELAY_SERVER | Unable to validate ASUP mail relay server. | 
| 46 | ASUP_INVALID_SENDER_EMAIL | Sender email address you specified is not a valid format. | 
| 47 | ASUP_INVALID_PAC_SCRIPT | Proxy Auto-Configuration (PAC) script file is a not a valid URL. | 
| 48 | ASUP_INVALID_PROXY_SERVER_HOST_ADDRESS | The Host address specified cannot be found or is in an incorrect format. | 
| 49 | ASUP_INVALID_PROXY_SERVER_PORT_NUMBER | The port number you specified is an invalid format. | 
| 50 | ASUP_INVALID_AUTHENTICATION_PARAMETER | The username or password you specified is invalid. | 
| 51 | ASUP_INVALID_DAILY_TIME_PARAMETER | The daily time parameter specified is invalid. | 
| 52 | ASUP_INVALID_DAY_OF_WEEK_PARAMETER | The -dayOfWeek parameter(s) that have been entered are invalid. | 
| 53 | ASUP_INVALID_WEEKLY_TIME_PARAMETER | The weekly time parameter is not valid. | 
| 54 | ASUP_INVALID_SCHEDULE_PARSING | Unable to successfully parse the schedule information provided. | 
| 55 | ASUP_INVALID_SA_SPECIFIED | Invalid storage array specifier provided. | 
| 56 | ASUP_INVALID_INPUT_ARCHIVE | The input archive entered is invalid. The input archive parameter must be in the form of -inputArchive=<n> where -n is an integer from 0 to 5. | 
| 57 | ASUP_INVALID_OUTPUT_LOG | A valid output log was not specified. | 
| 58 | ASUP_TRANSMISSION_FILE_COPY_ERROR | There was an error trying to copy the AutoSupport transmission log file. The transmission log either does not exist or there was an IO error trying to copy its data. | 
| 59 | ASUP_DUPLICATE_NAMED_ARRAYS | More than one storage array with the same name was found. Please retry the command using the world-wide-name parameter, -w <WWID> . | 
| 60 | ASUP_NO_SPECIFIED_ARRAY_FOUND | The specified storage array with the -n <storage-system-name> parameter is not present or is not supported for this command. | 
| 61 | ASUP_NO_SPECIFIED_WWID_FOUND | The specified storage array with the -w <WWID> parameter is not present or is not supported for this command. | 
| 62 | ASUP_FILTERED_TRANSMISSION_LOG_ERROR | There was an unknown error trying to obtain the filtered transmission log. | 
| 63 | ASUP_TRANSMISSION_ARCHIVE_DOES_NOT_EXIST | The AutoSupport input archive transmission log specified with the -inputArchive=<n> parameter does not exist. | 
| 64 | NO_VALID_REST_CLIENT_DISCOVERED | Unable to communicate with the storage array via https. | 
| 65 | INVALID_CLI_VERSION | The client CLI version is not compatible with the CLI version running on the storage array. | 
| 66 | INVALID_USERNAME_OR_PASSWORD | The username or password entered is invalid. | 
| 67 | UNTRUSTED_CONNECTION | Unable to establish a secure connection to the storage array. | 
| 68 | INVALID_PASSWORD_FILE | The password file cannot be found or is not readable. | 
Give documentation feedback