- Notes, cautions, and warnings
- Overview
- Getting started with ASM 8.1.1
- Initial Setup
- Dashboard
- Services
- 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
- Server (OS Installation only) Component Setting
- Configuring interface on rack servers
- Configuring Interface on Blade or FX Servers
- Importing Configuration from Reference Server
- Importing from existing template
- Uploading Server Configuration Profile
- Cluster
- Cluster component settings
- Virtual Machine
- Virtual Machine settings
- Application
- Application component settings
- Component combinations in templates
- Sample templates
- Template – deploy Citrix XenDesktop for 500 users
- Template – deploy operating system to hard drive
- Template – deploy physical server and virtual machine
- Template – deploying with Compellent iSCSI
- Template – deploy virtual machines to cluster
- Template – install ESXi to SD card with Fibre Channel storage
- Template – install ESXi to SD card with iSCSI storage
- 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 virtual machine template clone on VMware cluster
- Template – deploy SQL Server 2012
- Additional template information
- Manage templates
- Resources
- Understanding
All Resources tab
- Resource health status
- Resource operational state
- Resource firmware compliance status
- Updating firmware
- 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
- Removing resources
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Understanding
All Resources tab
- Settings
- Backup and restore
- Credentials management
- Getting Started
- Application logs
- Networks
- Repositories
- Jobs
- Users
- Virtual appliance management
- Virtual identity pools
- Troubleshooting
- LC operation times out while deploying server profile to a server
- Hyper-V host deployments using network storage only support certain configurations
- iSCSI storage network only support static IP addressing
- Unable to deploy a service for Compellent component with same server object and volume names
- Unable to deploy a service using the template with two EqualLogic CHAP components
- Unable to log in to ASM using active directory using “”
- Chain booting issue occurs while booting microkernel in a multi-hop DHCP environment
Active System Manager Release 8.1.1 User’s Guide
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
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.
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: <>"(", ")", "\"