Release Notes
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.
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.
o
Resolution/Workaround
: None
•
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.
Description
: ASM includes a puppet agent while installing the Windows or
Linux operating systems. The puppet agent communicates with the ASM
appliance to retrieve the post-install configuration and both server (ASM) and
client-side SSL certificates are checked for validity during this process. The
ASM server-side SSL certificate is created when the ASM appliance is first
started and is marked valid only after the first boot time of the appliance.
Hence, a failure may occur if the initial time set on the appliance is incorrect.
To view this issue, manually run the "puppet agent -t" command on the server
or VM that is experiencing a failure. This problem usually results in
SSL_connect errors in the output and the following message is displayed: CRL
is not yet valid for /CN=dellasm.
Resolution/Workaround
:
Ensure that the hypervisor host on which you want to install ASM is set to the
correct time and NTP is used for the ASM appliance, ASM installed servers,
virtual machines to ensure consistency in the time.