Release Notes
Unknown error querying ipmi on host 172.31.32.142: Could
not retrieve IPMI status: ipmi_sensor_read: internal IPMI
error.
o
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.
o
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-3157
: For SCVMM cluster provisioning, Active Directory must not contain any
hosts with the same name.
o
Description
: When you provision a SCVMM cluster using a Hyper-V cluster
creation template, if the template has the AD entries for the Cluster that are
persistent and match the name you are trying to provision, the SCVMM
cluster deployment will fail.
Resolution/Workaround
: Active Directory and DNS conflicts must be
resolved prior to a deployment if you intend to use names that may already
exist within your AD/DNS. ASM requires the names to be removed from
AD/DNS and these will be re-provisioned during the template execution.
•
Issue: ASM-3328
: Import from R430 reference server sets server type undefined in
networking section
o
Description
: 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.
o
Resolution/Workaround
: None
•
Issue: ASM-3463
: Compellent deployment fails if you type apostrophes (') or other special
characters in some fields.
o
Description
: When you try to enter apostropes or any other special
characters in a field the compellent deployment fails. You should not enter
apostropes or special characters.
Resolution/Workaround
: None
•
Issue
:
ASM 3490
: Host and sub host groups cannot be used in separate deployments for
Hyper-V deployments
.
o
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-3520
: Deployments fail if SD and HDD are enabled and operating system is
installed on SD.
o
Description
: ESXi Operating System installation was done on the SD card with
HDD and SD card enabled on the server. The configuration sequence was first