Users Guide

9
Troubleshooting
This topic includes details for resolving common issues encountered in ASM 8.3.
LC operation times out while deploying server profile to a server
While updating the server configuration using config XML, the LC job remains in the RUNNING state and eventually gets timed out.
This is observed in case there is "bootseq" attribute in the request XML. This is identified as an issue in LC and fix for this is available
along with 13G.
To resolve this issue, remove the content "bootseq" attribute from the config XML.
Hyper-V host deployments using network storage only support certain
configurations
Currently, while deploying Hyper-V, exactly two EqualLogic storage volumes using IP/IQN authentication are required. For Hyper-V,
CHAP authentication is not supported.
iSCSI storage network only support static IP addressing
Currently, while creating a network in ASM for iSCSI connectivity, specify the network using static IPs. Setting an iSCSI network to
DHCP causes issues during deployment.
Unable to deploy a service for Compellent component with same
server object and volume names
You cannot deploy a service for Compellent component if the server object is already mapped to the volume. This error occurs
because a volume name available in recycle bin is same as the volume that the resource module is trying to create using ASM UI.
You must have unique names for Volumes and Server Objects in the system (even if the volumes and server objects are in different
folders) because of the issues caused in Compellent API and UI behavior.
Unable to deploy a service using the template with two EqualLogic
CHAP components
Unable to deploy a service using the template with two EqualLogic CHAP components.
In ASM 8.3 release, you cannot create a template with two EqualLogic CHAP components and deploy a service that includes ESXi
hosts attached to storage. Currently, ESXi deployments support a single EqualLogic component.
Unable to log in to ASM using active directory using ""
You cannot log in to ASM using Active Directory with the domain name and user name separated by back slash "\".
119