HP 3PAR StoreServ 7450 4-node HP 3PAR Command Line Interface Administrator& - Page 42

Table 3 Global CLI Options and Environment Variables

Page 42 highlights

NOTE: Environment variables can only be used if the CLI is set up remotely. Environment variables cannot be used if you are accessing the CLI through SSH. Table 3 Global CLI Options and Environment Variables Global Option -sockssl -sys -password Environment Variable TPDSOCKSSL TPDSYSNAME -- Specifies... that the connection between the client and server is secure. This is the default setting. For additional information, see "Using SSL" (page 44). the system name of the system you are accessing. For additional information, see "Setting the TPDSYSNAME Environment Variable" (page 45). the encrypted password. This value should be protected for security purposes. For additional information, see "Setting Your Name and Password" (page 46). -pwf TPDPWFILE -user -- the password file the system references upon starting the CLI. This value should be protected for security purposes. For additional information, see "Setting Your Name and Password" (page 46). your user name. For additional information, see "Setting Your Name and Password" (page 46). Specifying the -user option also requires specifying the -password option. These options override the -pwf option. CAUTION: By setting the system name, user name, and password using environment variables, you are not prompted for this information when running the CLI, which can be useful for scripting. However, passwords must be kept secure. Using encrypted passwords in scripts, using an encrypted pwfile, or the encrypted password on the command line raises the risk of password exposure. It is imperative that the script, pwfile, or command line history file be strictly maintained to avoid compromise of the encrypted password. Failure to do so can leave the user open to impersonation by anyone with access to the encrypted string. -nosockssl -- -- - csvtable -listdom -nohdtot -hafter NOTPDSOCKSSL TPDCACHEDIR TPDSTARTFILE TPDCSVTABLE TPDLISTDOM TPDNOHDTOT TPDHAFTER that the CLI client should attempt to connect to the storage server on port 5782, without using SSL. This makes the connection insecure, and all data including authentication data passes in plain text packets. the location of the cache directory where the code that determines the version of the HP 3PAR software on the system resides. For additional information, see "Caching Client Bytecode" (page 47). the Tcl script that the system sources before entering the command loop. For additional information, see "Startup Files" (page 48). that commands that use the table formatting routines will print comma-separated output. For additional information, see "Comma Separated Values" (page 48). that domains are listed. For additional information, see "Listing Domains" (page 49). that headers and totals are not printed after commands are executed. For additional information, see "Table Headers and Totals" (page 50) the number of lines after which the header is printed again. For additional information, "Table Headers and Totals" (page 50). 42 Running the HP 3PAR Command Line Interface

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

NOTE:
Environment variables can only be used if the CLI is set up remotely. Environment variables
cannot be used if you are accessing the CLI through SSH.
Table 3 Global CLI Options and Environment Variables
Specifies...
Environment Variable
Global Option
that the connection between the client and server is secure.
This is the default setting. For additional information, see
“Using SSL” (page 44)
.
TPDSOCKSSL
sockssl
the system name of the system you are accessing. For
additional information, see
“Setting the TPDSYSNAME
Environment Variable” (page 45)
.
TPDSYSNAME
sys <system_name>
the encrypted password. This value should be protected for
security purposes. For additional information, see
“Setting
Your Name and Password” (page 46)
.
––
password <encrypw>
the password file the system references upon starting the
CLI. This value should be protected for security purposes.
TPDPWFILE
pwf <password_file>
For additional information, see
“Setting Your Name and
Password” (page 46)
.
your user name. For additional information, see
“Setting
Your Name and Password” (page 46)
. Specifying the -user
––
user <user_name>
option also requires specifying the -password option. These
options override the -pwf option.
CAUTION:
By setting the system name, user name, and password using environment variables, you are not prompted
for this information when running the CLI, which can be useful for scripting. However, passwords must be kept secure.
Using encrypted passwords in scripts, using an encrypted pwfile, or the encrypted password on the command line
raises the risk of password exposure. It is imperative that the script, pwfile, or command line history file be strictly
maintained to avoid compromise of the encrypted password. Failure to do so can leave the user open to impersonation
by anyone with access to the encrypted string.
that the CLI client should attempt to connect to the storage
server on port 5782, without using SSL. This makes the
NOTPDSOCKSSL
-nosockssl
connection insecure, and all data including authentication
data passes in plain text packets.
the location of the cache directory where the code that
determines the version of the HP 3PAR software on the
TPDCACHEDIR
––
system resides. For additional information, see
“Caching
Client Bytecode” (page 47)
.
the Tcl script that the system sources before entering the
command loop. For additional information, see
“Startup
Files” (page 48)
.
TPDSTARTFILE
––
that commands that use the table formatting routines will
print comma-separated output. For additional information,
see
“Comma Separated Values” (page 48)
.
TPDCSVTABLE
csvtable
that domains are listed. For additional information, see
“Listing Domains” (page 49)
.
TPDLISTDOM
-listdom
that headers and totals are not printed after commands are
executed. For additional information, see
“Table Headers
and Totals” (page 50)
TPDNOHDTOT
-nohdtot
the number of lines after which the header is printed again.
For additional information,
“Table Headers and Totals”
(page 50)
.
TPDHAFTER
-hafter
42
Running the HP 3PAR Command Line Interface