HP Ethernet 10Gb 2-port 530T Adapter - Manual (Page 29)

Scripting mode 29
Based on the previous algorithm, you can use the -set operation to set the encrypted password only to the
same NIC and port of the -get operation. If you use the -set operation to set the encrypted password to
a different NIC or port, the password string is treated as a non-encrypted string. In this case, because of the
binary-to-ASCII conversion and extra tails added during encryption process, the encrypted string is longer
than the original string and is likely to cause an over-length error. The -set log file indicates whether CCM
treats the password field as an encrypted string (with a ; L[LineNo] Encrypted comment following the
difference line) or a non-encrypted string (with a ; L[LineNo] Clear comment following the difference
line) during the -set operation.
To manually type in a clear password, modify the password field with a clear password string. The encrypted
password string is generated only by the -get operation. Users cannot manually generate an encrypted
password string for security reasons.
Script execution order
In CCM versions earlier than 6.2.2, the script order is requested for mutual dependent parameter
configurations or errors occur. For example, IP version configuration must occur before the corresponding
dependent IP address configuration. CCM version 6.2.2 and later handles dependent parameter
configuration so that script order is no longer requested. In the previous example, IP address configuration
can occur before IP version configuration as long as the two parameters match. This eases the script
automation process from -get converted to -set.
Convert -get result for use by -set
The -get script can be used directly by -set. However, if -get is taken from different devices or a different
port in a NIC, you must manually modify some parameters. For example, in 10G devices supporting NIC
partitioning, if the script to perform the -get operation from port 0 is used to perform the -set operation to
port 1, port-specific parameters such as NIC partition functions are rejected because port 0 contains 0, 2, 4,
and 6 NIC partition numbers and port 1 contains 1, 3, 5, and 7 NIC partition numbers. In this case, a
manual modification is requested.
When you use a configuration file obtained from -get as a base to create a new file for the -get operation,
configuration errors can be introduced due to loss of consistency. For example, when you change NPAR from
enable to disable, the detailed configuration items for each partition in the original file obtained from the
-get operation when NPAR was enabled become invalid. If you use the modified inconsistent file to perform
the -set operation, error messages appear.
To resolve errors, do one of the following:
• Ignore the errors.
By default, the -setmode of the -set operation is <Force>, which ignores any errors and saves the
valid part of configuration file. A concern with this approach is the possibility of overlooking other
errors.
• Modify the rest of configuration file to keep configuration file consistent.
For example, if the -get operation obtains a file with NPAR enabled, and then you disable NPAR,
comment out the NPAR configuration items for each partition that is invalid with NPAR disabled to keep
the configuration file consistent.