Known limitations

This topic lists all of the known limitations with Advanced Settings Utility.

  1. RDCLI supports only ISO/CDROM/DVDROM as the mount source.
  2. RDCLI does not support non-IMM systems.
  3. ASU does not support the loaddefault value for the boot order on IMM-based systems. The loaddefault command does not change the boot order to the default value.
  4. In Flex system, there are two types of user accounts due to the security design: CMM user (LDAP user) and IMM2 user (local user). CMM users are available for Web, CLI, and CIM interfaces. IMM2 users are available for IPMI and SNMPv3 interfaces. Generally, ASU needs a IMM2 user to work on IMM, but it needs a CMM user in FoD key management if --device CMM or --interface CIM is specified.
  5. ASU failed to set uEFI.LegacyRomExecution through ESXi, although uEFI rebooted.
  6. On ESXi, ASU does not support the creation of iSCSI by setting iSCSI.AttemptName.x. You must create iSCSI by using the F1 menu first, then using ASU to modify the iSCSI attribute.
  7. On ESXi on the IMMv1 platform and IMMv2 platform earlier than 1AOO49Z, ASU does not support changes to the syslog status by setting IMM.RemoteAlertRecipient_Status.x. You might be able to change the setting, but the new value will neither be shown by ASU nor take effect.
  8. After ASU sets some IMM network settings, which might lead to an IMM IP address change or ASU connection close, ASU might fail to get the set result.
  9. On ESXi, if the CIM ports have been changed on IMM (the default is http 5988 https 5989), you must manually disable the ESXi5.x firewall by using the command esxcli network firewall set -e false, or ASU will not connect to ESXi.
  10. In Flex System, the settings IMM.IMMInfo_Contact, IMM.IMMInfo_Location, and IMMInfo_RoomId cannot be set with the value of null string.
  11. On ESXi4.1, ESXi5.0 and ESXi5.1, OpenSSL can only support TLS level 1.0; therefore, if you set the IMM TLS min level to 1.1 or 1.2, ASU will fail to get and set IMM configuration through those ESXi systems.
  12. When using the comparedefault command, some settings might not match their default values, even though the loaddefault command was run before the comparedefault command.
  13. On VMware ESXi with Lenovo Customized Image 5.0, ASU cannot set bootorder (and wolbootorder) settings. This is a permanent limitation on VMware ESXi with Lenovo Customized Image 5.0, and the workaround in limitation 14.does not work for it.
  14. On VMware ESXi with Lenovo Customized Image 5.1 and 5.5u1, ASU cannot set bootorder (and wolbootorder) settings. This is caused by a conflict of the class name for bootorder in the Broadcom CIM Provider and IMM. The Broadcom CIM Provider must be disabled for ASU to set the bootorder (and wolbootorder) settings.
    To disable the Broadcom CIM Provider, run the following commands on the ESXi command terminal:
    1. . esxcli system settings advanced list | grep brcm

      The following example illustrates what the output might look like:
      Path: /UserVars/CIMvmw_brcmProviderEnabled
                Description: Enable or disable the CIM vmw_brcm provider
    2. . esxcli system settings advanced set -o [PATH] -i 0

      Where [PATH] is the path of the Broadcom CIM Provider listed in the output of the command run in step a. In the previous example, it is /UserVars/CIMvmw_brcmProviderEnabled

    3. . /etc/init.d/sfcbd-watchdog restart
    Note: This issue has been fixed on VMware ESXi with Lenovo Customized Image 5.5u2 and later version.
  15. There is a rebranding issue in all VMware ESXi with Lenovo Customized Image. Ensure that you have installed patch2.1 or later into VMware ESXi with Lenovo Customized Image. To obtain the latest patch for ESXi, go to
  16. ASU uses IMM Lan over USB, which uses the "169.254.95.xx" network by default. If "169.254.95.xx" is used by another application, such as Oracle RAC, running ASU changes the network route table which can cause the other application to behave unexpectedly. In this case, you can use the command option "--kcs" to use KCS instead of the IMM Lan-over-USB to avoid the issue.