- Notes, cautions, and warnings
- Overview
- Getting started with ASM 8.2
- Initial Setup
- Dashboard
- Services
- Deploy Service
- Add existing service
- Viewing Service Details
- Editing service information
- Deleting service
- Exporting service details
- Retry Service
- View All Settings
- Migrating servers (service mobility)
- Migrating servers
- Upgrade Components
- Adding components to an existing service deployments
- Deleting resources from service
- Templates
- Manage templates
- Viewing template details
- Creating template
- Editing template information
- Building template overview
- Building and publishing template
- Importing template
- Export Template
- Upload External Template
- Editing template
- Viewing template details
- Deleting template
- Cloning template
- Deploying service
- Deploy Multiple Instances of Service
- Add Attachments
- Decommissioning services provisioned by ASM
- Component types
- Storage
- Storage settings
- Server
- Server settings
- Adding New Interface
- Server (OS Installation only) Component Setting
- Importing from existing template
- Uploading Server Configuration Profile
- Cluster
- Cluster component settings
- Virtual Machine
- Application
- VMware vSAN
- Sample templates
- Template — deploy Citrix XenDesktop for 500 users
- Template – deploy operating system to hard drive
- Template — deploy virtual machines to cluster
- Template – deploy Hyper-V host with iSCSI storage
- Template – deploy Hyper-V cluster with iSCSI storage
- Template – deploy Hyper-V cluster with Fibre Channel storage to SCVMM
- Template – deploy VMware cluster with NetApp storage
- Template – boot from Fibre Channel SAN
- Template — boot from iSCSI SAN
- Template – deploy virtual machine template clone on Hyper-V cluster
- Template – deploy SQL Server 2012
- Template-deploy Hyper-V Cluster with iSCSI Storage To SCVMM
- Template-deploy VMware Cluster with FC Storage
- Template-deploy VMware Cluster with FCoE Storage
- Template-deploy VMware Cluster with iSCSI Storage
- Template-deploy VMware Cluster with iSCSI Storage Using Software Initiator
- Template-deploy VMware VSAN with Virtual Distributed Switch
- Application component settings
- Component combinations in templates
- Additional template information
- Manage templates
- Resources
- Resource health status
- Resource operational state
- Port View
- Resource firmware compliance status
- Updating firmware
- Removing resources
- Viewing firmware 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
- Add-On Modules
- Backup and restore
- Credentials management
- Getting Started
- Application logs
- Networks
- Repositories
- Jobs
- Users
- Virtual appliance management
- Virtual identity pools
- Troubleshooting
Active System Manager Release 8.2 User’s Guide
Troubleshooting
This topic includes details for resolving common issues encountered in ASM 8.2.
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.2 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.
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 mode general
switchport general allowed
vlan add 3000
switchport general allowed
vlan add 20,30,40 tagged
exit
In the above example:
- 3000: Indicates Native PXE VLAN
- 20,30,40: Indicates Management or vMotion or ISCSI
In case of production environments with large networks, routers may be configured with IP Helper Addresses to point to a DHCP on another network.
The health status for Compellent storage devices displays as Unknown on the Resources page
Make sure that the Compellent SNMP agent is configured with the same public string that is used in the Compellent credentials, the SNMP agent is started, and enabled on the device.
Scaling down a server that is part of a cluster with HA and DRS disabled does not remove the server from vCenter. The associated virtual machines may also appear in a Disconnected state.
It is recommended that before you scale down a server, you must migrate the VMs to a different host if HA and DRS are not enabled on the cluster.
Proporcione calificaciones (1 a 5 estrellas).
Proporcione calificaciones (1 a 5 estrellas).
Proporcione calificaciones (1 a 5 estrellas).
Seleccione si el artículo fue útil o no.
Los comentarios no pueden contener estos caracteres especiales: <>"(", ")", "\"