Release Notes

o This is an expected behavior because connection is not established with the
BMC for a few seconds when you initiate firmware update operation, and the
firmware update continues after the connectivity is established with BMC.
• ASM-3133: ASM performs the discovery operation on the FX2 chassis after you update the
CMC firmware.
o The Chassis firmware update will trigger the Chassis inventory which will
trigger the Chassis discovery in order to detect any newly inserted blades or
IOMs.
o This is an expected behavior. When you update the CMC firmware on FX2
chassis, the chassis firmware update operation initiates the Chassis inventory
operation, which in turn initiates the chassis discovery operation to collect
the information about the blades or IOMs that are newly inserted.
• ASM-3520: Deployments fail if SD and HDD are enabled and operating system is installed
on SD.
o ESXi Operating System installation was done on the SD card with HDD and
SD card enabled on the server. The configuration sequence was first HDD
and then SD. After the operating system was installed the server was not able
to boot from the HDD.
o Check for ESXi management IP Address access.
• ASM-3545: C-series cannot be taken as a reference server though it is displayed in the
import list.
o This is an expected behavior. C-series servers cannot be referenced as
reference servers as they do not have iDRAC supported.
• ASM-3328: Import from R430 reference server sets server type undefined in networking
section
o For all servers prior to ASM discovery, ensure the RAID controller is enabled if
it is available, and that any unsupported 1Gb NICs are disabled. After updating
these devices setting, you should reboot the server to ensure that Lifecycle
Controller system inventory is updated.
• ASM-2144: Server with bare hard drive fails to get HddSeq set properly
o If you choose SD boot and the server has a bare hard drive (not connected
through a RAID controller) the HddSeq may fail to get set properly, Leaving
the bare hard drive at the top of the list. The server may boot off the bare
hard drive instead of the SD card where the operating system was installed.
• ASM-3734: Backups from ASM versions prior to 8.1 will not contain the appliance NTP
settings.
o When restoring from a backup file created prior to 8.1, the user is required to
configure NTP settings in the Virtual Appliance Management settings section.
• ASM-3504: When you clone a template from Hyper-V to ESX, the deployment fails with
Hype-V exception
o Cloning a template built for Hyper-V and changing it to ESX results in "Install
Hyper-V" flag being cached in the back end. The new template with ESX,
when deployed fails with the following exception.
#<Exception: HyperV does not work with target boot device
SD>
/opt/asm-deployer/lib/asm/processor/server.rb:22:in
`munge_hyperv_server'
/opt/asm-deployer/lib/asm/service_deployment.rb:3234:in
`process_server'
/opt/asm-deployer/lib/asm/service_deployment.rb:682:in
`process_components