Table of Contents
Advertisement
Applying Changes
The
command is used to apply changes. There is one
command per
ApplySet
ApplySet
program group in the MIB and the syntax varies slightly according to the group. Use this
command, for example
, to actually apply the change(s) you made
vbrickSlot1ArchiveApplySet
with an
or a
. An
is always written in the following format with the
SVAR
STAB
ApplySet
trailing
.
=2
VBrick> SVAR vbrickSlot1ArchiveApplySet=2
It is important to note that some ApplySets can cause the VBrick appliance to send
unsolicited messages. For example, the appliance may reboot with the following message:
$!Rebooting ...
Saving Changes
Once you are done, you must save to persistent storage if you want your edits saved in the
configuration file. Unless you save the configuration, any changes you have made will be lost
if the appliance reboots. A save is always written in the following format with the trailing
.
=2
Note that some changes to the configuration will reboot the VBrick in which case you must
wait for it to reset.
VBrick> SVAR vbrickSysSaveConfiguration=2
Error Handling
Programming errors, for example syntax errors, illegal values, etc. display informational
messages in the CLI, for example
. Other system or network
$!ERROR=Value out of range
issues, for example a dropped connection or a failed save (see below) are shown in the System
Log (open IWS and go to
to see the log). You can also detect
Status: System Log > Config
potential errors in advance by getting the value of various status parameters in the VBrick.
For example, if you are writing a script, you might want to check
or
Archiver State
FTP
before you set parameters for a related task.
Status
56
© 2008 VBrick Systems, Inc.
Advertisement
Table of Contents
