HP iLO 4 Scripting and Command Line Guide
SNMP_USER_PROFILE INDEX sets the number (1, 2, or 3) for one of three available user
profiles for SNMPv3 authentication, and includes the following:
• SECURITY_NAME sets the user profile name. Value must be 1 to 32 alphanumeric characters
long.
• AUTHN_PROTOCOL sets the message digest algorithm to use for encoding the authorization
passphrase. The message digest is calculated over an appropriate portion of an SNMP
message and included as part of the message sent to the recipient. Valid values are 0 (for
MD5) or 1 (for SHA).
• AUTHN_PASSPHRASE sets the passphrase to be used for sign operations. Value must be 8
to 49 characters long.
• PRIVACY_PROTOCOL sets the encryption algorithm to be used for encoding the privacy
passphrase. A portion of an SNMP message in encrypted before transmission. Valid values
are 0 (for DES) or 1 (for AES).
• PRIVACY_PASSPHRASE sets the passphrase used for encrypt operations. Value must be 8 to
49 characters long. If this value is omitted, the value for AUTHN_PASSPHRASE is used.
MOD_SNMP_IM_SETTINGS runtime errors
Possible MOD_SNMP_IM_SETTINGS error messages include:
• RIB information is open for read-only access. Write access is
required for this operation.
• User does not have correct privilege for action. CONFIG_ILO_PRIV
required.
• The TRAP_SOURCE_IDENTIFIER value must not be left blank.
• TRAP_SOURCE_IDENTIFIER VALUE is too long.
• The value specified is invalid.
• SNMP V1 Traps can not be disabled in SNMP Pass-thru mode.
• SNMP_V3_ENGINE VALUE is too long.
• SECURITY_NAME VALUE is too long.
• AUTHN_PROTOCOL valid values are 0:MD5 or 1:SHA.
• AUTHN_PROTOCOL can not be left blank.
• AUTHN_PASSPHRASE VALUE is too long.
• PRIVACY_PROTOCOL valid values are 0:DES or 1:AES.
• PRIVACY_PROTOCOL can not be left blank.
• PRIVACY_PASSPHRASE VALUE is too long.
• PRIVACY_PASSPHRASE VALUE needs a minimum of 8 characters.
• INDEX can not be left blank.
MOD_ENCRYPT_SETTINGS
The MOD_ENCRYPT_SETTINGS command is used to set the communication settings for the Enterprise
Secure Key Manager (ESKM). For this command to parse correctly, the command must appear
within a RIB_INFO command block, and RIB_INFO MODE must be set to write. The user must have
the Configure iLO Settings privilege to execute this command. For example:
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="adminname" PASSWORD="password">
<RIB_INFO MODE="write">
RIB_INFO 105