HP Surestore 64 HP Surestore Director FC-64 Command Line Interface User's Guid - Page 21

Limitation on Movements, Config.Port&gt, Root&gt, Maint&gt, Maint.Port&gt

Get HP Surestore 64 - Director Switch PDF manuals and user guides View all HP Surestore 64 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Introduction Config.Port> root Root> maint Maint> port Maint.Port> beacon 4 true Another approach to making the navigation more concise is to use the complete command syntax from the Root> prompt each time. For example, to issue the config.port.name command and then the maint.port.beacon command, the commands are entered as follows: Root> config port name 4 "Sam's Tape Drive" Root> maint port beacon 4 true As shown in this example, use of the complete command syntax avoids navigating up and down the branches of the CLI command tree, and the prompt stays at the root. The use of complete command syntax is particularly useful when writing scripts. When coding a script, remember to code the appropriate character sequences, which are described in Navigation Conventions. Root> config port name 4 "Sam's Tape Drive" Root> maint port beacon 4 true Limitation on Movements As the commands are entered, they are recorded in a history log. Note these limitations on movement that result from use of the history log: • If a command has more than 60 characters, the command runs, but the command is not recorded in the history log, and the position in the tree does not change, as shown in the following example. Because the command is not recorded in the history, a subsequent asynchronous command (navigation command) cannot depend on it. Root> config zoning addWwnMem TheUltimateZone 10:00:00:00:C9:22:9B: 64 Entering Command Line Interface Commands 9

  • 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
Entering Command Line Interface Commands
9
Introduction
Config.Port>
root
Root>
maint
Maint>
port
Maint.Port>
beacon 4 true
Another approach to making the navigation more concise is to use the complete command
syntax from the Root> prompt each time. For example, to issue the config.port.name
command and then the maint.port.beacon command, the commands are entered as
follows:
Root>
config port name 4 "Sam
’
s Tape Drive"
Root>
maint port beacon 4 true
As shown in this example, use of the complete command syntax avoids navigating up and
down the branches of the CLI command tree, and the prompt stays at the root. The use of
complete command syntax is particularly useful when writing scripts.
When coding a script, remember to code the appropriate character sequences, which are
described in Navigation Conventions.
Root>
config port name 4 "Sam
’
s Tape Drive"<CR>
Root>
maint port beacon 4 true<CR>
Limitation on Movements
As the commands are entered, they are recorded in a history log. Note these limitations on
movement that result from use of the history log:
•
If a command has more than 60 characters, the command runs, but the command is not
recorded in the history log, and the position in the tree does not change, as shown in the
following example. Because the command is not recorded in the history, a subsequent
asynchronous command (navigation command) cannot depend on it.
Root>
config zoning addWwnMem TheUltimateZone 10:00:00:00:C9:22:9B:
64