HP StorageWorks 2/140 CLI reference guide for directors and edge switches - Page 16

Entering Command Line Interface Commands, Documentation Conventions, Navigation Conventions

Page 16 highlights

Introduction The purpose of the CLI is to automate management of a large number of Directors and Edge Switches through scripts. Although the primary use of the CLI is in host-based scripting environments, CLI commands can also be entered directly at a command line. Because the CLI is not an interactive interface, no prompts are displayed to guide the user through a task. If an interactive interface is needed, the HAFM application or EWS application should be used instead of the CLI. Entering Command Line Interface Commands CLI commands can be entered directly at the command line of a workstation or coded in a script. CLI commands are not case sensitive. Documentation Conventions Throughout this publication, periods are used to separate components of a command name. However, periods cannot be included when the command is actually entered at a workstation or coded in a script. How to enter commands is explained in Navigation of the CLI Command Tree on page 1-7. Even though commands cannot be entered with periods, command line prompts do include periods as shown below: Config.Port> Navigation Conventions Basic command line navigation conventions are supported. The following table includes asynchronous commands recognized by the CLI. Table 1-1: CLI Command Tree Navigation Conventions Character Sequence Common Name Carriage Return Action or Description Pass a completed line to the parser. Delete New Line Space Backspace one character and delete the character. Pass a completed line to the parser. Used to separate keywords. 1-2 CLI reference guide for directors and edge switches

  • 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
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

1–2
CLI reference guide for directors and edge switches
Introduction
The purpose of the CLI is to automate management of a large number of Directors and
Edge Switches through scripts. Although the primary use of the CLI is in host-based
scripting environments, CLI commands can also be entered directly at a command
line.
Because the CLI is not an interactive interface, no prompts are displayed to guide the
user through a task. If an interactive interface is needed, the
HAFM
application or
EWS
application should be used instead of the CLI.
Entering Command Line Interface Commands
CLI commands can be entered directly at the command line of a workstation or coded
in a script. CLI commands are not case sensitive.
Documentation Conventions
Throughout this publication, periods are used to separate components of a command
name. However, periods cannot be included when the command is actually entered at
a workstation or coded in a script. How to enter commands is explained in
Navigation
of the CLI Command Tree on page 1–7
. Even though commands cannot be entered
with periods, command line prompts do include periods as shown below:
Config.Port>
Navigation Conventions
Basic command line navigation conventions are supported. The following table
includes asynchronous commands recognized by the CLI.
Table 1–1:
CLI Command Tree Navigation Conventions
Character
Sequence
Common
Name
Action or Description
<CR>
Carriage
Return
Pass a completed line to the parser.
<DEL>
Delete
Backspace one character and delete the
character.
<NL>
New Line
Pass a completed line to the parser.
<SP>
Space
Used to separate keywords.