Users Guide
Table Of Contents
- Active System Manager Release 8.3.1 User’s Guide
- Overview
- Getting started with ASM 8.3.1
- Initial Setup
- Dashboard
- Services
- Deploying service
- Add existing service
- Viewing service details
- Editing service information
- Deleting service
- Exporting service details
- Retrying service
- Viewing all settings
- Migrating servers (service mobility)
- Migrating servers
- Upgrading components
- Adding components to an existing service deployment
- Deleting resources from service
- Templates
- Managing templates
- Viewing template details
- Creating template
- Editing template information
- Building template overview
- Building and publishing template
- Importing template
- Exporting template
- Uploading external template
- Editing template
- Viewing template details
- Deleting template
- Cloning template
- Deploying service
- Deploying multiple instances of service
- Adding Attachments
- Decommissioning services provisioned by ASM
- Component types
- Component combinations in templates
- Additional template information
- Managing templates
- Resources
- Resource health status
- Resource operational state
- Port View
- Resource firmware compliance status
- Updating firmware
- Removing resources
- Viewing firmware and software compliance report
- Discovery overview
- Configuring resources or chassis
- Removing discovered resources
- Configuring default firmware repository
- Running firmware compliance
- Configuring global chassis settings
- Configuring unique chassis settings
- Configuring unique server settings
- Configuring unique I/O module settings
- I/O module configuration
- Completing the chassis configuration
- Adding or editing Chassis Management Controller (CMC) user
- Adding or editing Integrated Dell Remote Access Controller (iDRAC) user
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Settings
- Troubleshooting
9
Troubleshooting
This topic includes details for resolving common issues encountered in ASM 8.3.
LC operation times out while deploying server prole to a server
While updating the server conguration using cong 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 identied as an issue in LC and x for this is available
along with 13G.
To resolve this issue, remove the content "bootseq" attribute from the cong XML.
Hyper-V host deployments using network storage only support certain
congurations
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 dierent
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 "\".
123