Release Notes

Issue: ASM-2599 : Issue with Configure Resources when IOM Firmware is out-of-date with
minimum firmware requirements.
Description : The following error message is displayed while configuring
resources when a firmware running on the I/O module does not meet the
minimum requirements. If the IOM firmware is not within the Compatibility
Matrix minimum firmware, The following error is displayed when it attempts
to show the discovered resources.
An Unexpected error has occurred on the system Please try
again later
.
Resolution/Workaround : You must update the I/O module firmware and
retry initial discovery and configuration of the chassis.
Issue: ASM-2951 : Error message is displayed during firmware update on C series.
Description : While performing firmware update on C series servers, the
health status of the C series switch changes to <gray> and the following error
message is displayed.
Unknown error querying ipmi on host 172.31.32.142: Could
not retrieve IPMI status: ipmi_sensor_read: internal IPMI
error
.
Resolution/Workaround: 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.
Issue: ASM-3133 : ASM performs the discovery operation on the FX2 chassis after you
update the CMC firmware.
Description : 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.
Resolution/Workaround : 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.
Issue : ASM 3490 : Host and sub host groups cannot be used in separate deployments for
Hyper-V deployments
.
Description
: Hyper-V deployments uses one logical network and all hosts are
assigned the same logical network. In case of two deployments, if the first
deployment uses the parent host group and the second deployment uses a
user defined host group, then the second deployment with the user defined
host group fails.
Resolution/Workaround : None
Issue: ASM-3545 : C-series cannot be taken as a reference server though it is displayed in
the import list.
Description : This is an expected behavior. C-series servers cannot be
referenced as reference servers as they do not have iDRAC supported.
Resolution/Workaround : None
Issue: ASM-3639 : Time difference between the installed operating system and ASM
appliance may cause the operating system post-install configuration on servers and virtual
machines to fail while waiting for puppet agent to check in.