Users Guide

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.1.1 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 “\”.
To log in to ASM using Active Directory, use forward slash “/”. For example: <domain>/ <username>.
NOTE: Domain is the name for the Active Directory service you have created in ASM.
Chain booting issue occurs while booting microkernel in
a multi-hop DHCP environment
The chain booting error occurs if the DHCP server is configured in a different subnet or network or
connected to a different switch.
In such scenarios, the DHCP network is tagged.
To resolve this issue, in switch configuration, modify the native VLAN of server or computer facing ports
to PXE VLAN.
Sample native VLAN configuration in Dell PowerConnect switch:
interface Gi1/0/2
spanning-tree portfast
switchport mode general
switchport general pvid 3000
147