Configure Parameters
This step is the second step of applying a configuration file to devices.
At this step, you need to specify parameters in the configuration file.
The Configure Parameters page is displayed repeatedly for each of the
selected devices. The configuration file with parameters specified will be applied
to the devices.
Operation Procedure
- Input fixed parameter values or MIB variable expressions, or click the
Select Parameters link to add variables.
- Click Next.
- If multiple devices are selected, you can select the Use the Same
Parameters for the Following Devices checkbox to apply parameters specified
in current page to all the other devices you have selected.
- If the current device is the last one in the selected devices, the
Set Task Attributes page is
displayed; otherwise, you need to repeat the preceding step
- If multiple devices are selected, you can select the Import Parameters option
and import a parameter file that defines parameters for each device.
Configure the parameter file according to the parameter template on the page.Click Export Parameters to download a template that contains all devices selected in the previous step.
Configure the template parameters, then click Import Parameters, and select the template to complete the configuration.
Precautions
- For a stack device, you must set the parameters for each stack unit.
Parameters
- The parameter value must be within 128 characters.
Notes
- Each selected device corresponds to a configuration file, that is,
the complete configuration file with parameters specified.
- If you select a configuration file containing no parameters, you will be
directed to the third step of Deploy Configuration , that is,
the Set Task Attributes page.
- The dollar sign and braces combination ( ${} ) indicates the
definition of a parameter in the configuration segment. For example,
${solution} indicates a parameter named solution.
- The vertical bar ( | ) is used to separate possible values of a parameter.
For example, v1 | v2c indicates that the parameter value
can be v1 or v2c.
- The hyphen ( - ) indicates that the value range consists of successive numbers.
For example, 0 - 3 indicates that the parameter value is an
integer in the range of 0 to 3.
- The parentheses ( () ) indicates the range of an input parameter.
You can input values one by one, or specify a range. Note that both extremes of
the range are excluded. For example, ${SNMPversion(v1|v2c)} indicates
that the value of the parameter named SNMPversion can be v1 or v2c.
${level (0-3)} indicates that the value of the parameter named
level can be 1 or 2.
- The square brackets ( [] ) indicates the input range of a parameter
with both extremes included. For example, ${level [0-3]} indicates that
the parameter named level has four possible values, 0, 1, 2, and 3.
- The question mark ( ? ) indicates that the specified value can
appear once or not appear. For example, n [0-4]? indicates that the
value of the parameter can range from 0 to 4, or is not specified.
- The asterisk ( * ) indicates that one or more values can be
selected. For example, SNMPversion( v1 | v2c )* indicates that
the value of the parameter named 'SNMPversion' can be v1 or v2c, or both.
- The colon ( : ) indicates the category of a range. It is usually
used together with the enumeration values to define a parameter. For example,
(aux:[0] | vty:[0-4]) indicates that the value is 0 if aux
is used, and the value ranges from 0 to 4 if vty is used.
The parameters aux and vty are the enumerated values of
another parameter.
- The letter m indicates the start value of a parameter, while the letter n
indicates the end value. The end value must be greater than the start value.
For example, m[0-4] n[0-4] indicates that the start value ranges from
0 to 4, and the end value ranges from 0 to 4. The start value and the end value
are separated with a space.
- The dollar sign and parentheses combination ( $() ) indicates a MIB
variable. At least two vertical bars are included in the format of
$(mibName|mibVariable|index) or (mibName|mibValue=conditionValue).
Built-in MIB parameters are supported. The at sign (@) indicates a built-in
parameter. For example, @(mib| mibVariable =conditionValue) indicates
that the index value of the mibVariable parameter when the value of mibVariable
is conditionValue. If a conditional expression has multiple return index values,
the first return value is used.
- The percent sign and angle brackets combination ( %<> ) indicates an
variable. The expression includes at least a half-width dot ( . )
in the format of %<moduleName.paramExpression>.
Parameter Examples
- ${username} indicates that you can specify only a single value
rather than a range for the parameter named username .
- ${SNMPversion(v1|v2c)} indicates that the parameter named
SNMPversion has two possible values, v1 and v2c.
- ${level [0-3]} indicates that the value of the parameter
named level can be 0, 1, 2, or 3.
- ${range(aux:[0]|vty:m[0-4] n[0-4]?)} indicates that the value is
0 if aux is used, and the value ranges from 0 to 4 is vty is
used. The end value must be greater than the start value. You can specify no
end value. The start value is separated from the end value with a space.
- Input a fixed value, such as IP address 10.24.56.78.
- Input a MIB variable, for example, $(INC-SYS-MAN-MIB|incSysImageSize|65537)
or$(INC-SYS-MAN-MIB|incSysImageSize|@(INC-SYS-MAN-MIB|incSysReloadImage|65536)).
- Select or input an variable expression, for example,
%<icc.telnet.userName>.
Related Topics