Solution Guide
Table Of Contents
- Introduction to the Active System 1000 Solution
- Audience
- Support
- Technical Documentation
- Overview
- Active System 1000-Supported Configurations
- Active System Manager Deployment
- Deployment Options
- Deployment Prerequisites
- Deploying OVF
- Changing Key Access Credentials
- Assigning IP Address to the Active System Manager
- Accessing the Active System Manager Web Client for the First Time
- Adding Additional Licenses
- Configuring Active System Manager Services
- Installing the Active System Manager Client
- Active System Manager Setup
- User and Group Management
- Discovering Active System 1000 Components
- Software Repositories in Active System Manager Appliance
- Updating Repository Elements for ISO Bootable Images
- Updating Repository Elements for IOA Switch configuration and Images
- Updating Repository Elements for Brocade Firmware Repository
- Updating Repository Elements for Brocade Switch Configuration
- Updating Repository Elements for ToR Switch Configurations and Images
- Updating Repository Elements for VMware Baseline Images
- Configuring Networks
- Physical Templates and Orchestration
- Workload Provisioning Using Logical Templates
- Operation Center View—Administrative Operations
- Dashboard Reports
- Resource Allocation by Sessions Report
- Resource Allocation by Hosts Report
- Resource Allocation by Groups Report
- Top Ten Resource Allocation Report
- Top Ten Resource Utilization Report
- VM Utilization by Session Report
- Host Utilization (Consolidated) Report
- Cluster Utilization (Consolidated) Report
- Storage Utilization (Consolidated) Report
- CPU and Memory Utilization Showback Report
- Appendix A—Deployment Activities
- Appendix B—Build of Materials
- Appendix C—Firmware and Software Base Lineup
- Appendix E—Adding New ESXi ISO Images
- Appendix G— Planning Worksheet
- Appendix I—FAQs
98
• Total of 4 sessions, i.e. 16 VMs can be scheduled at a time.
To workaround this, provide value (in %) to the 'Over Subscription' property of the
inventory level capacity parameters 'CPU/RAM'.
For example:
• Updating 'Over Subscription' at cluster level, to '100' results in 8 sessions,
i.e. 32 VMs can be scheduled at a time.
• Updating 'Over Subscription' at cluster level, to '200' results in 12 sessions,
i.e. 48 VMs can be scheduled at a time.
30. Cloning of VMs across data centers is not supported in Active System Manager 7.1
The VM template or gold VMs should be in the inventory of the datacenter where
you are deploying VMs to hosts.
31. Why are orchestrations failing on servers with dual SD cards?
If a server has dual SD cards, the BIOS setting must be set to mirror mode to avoid
orchestration failures.
32. How do I increase the number of logical deployments that can run concurrently on
the system?
If a server has dual SD cards, the BIOS setting must be set to mirror mode to avoid
orchestration failures.
For better performance of the individual sessions the appliance has a default limit
of 10 parallel actions. Logical sessions are long-running so deploying more than 10
at a time will cause the system to queue up sessions greater than 10. This will also
prevent other logical or virtual actions from being run until the logical jobs clear. If
you need to run large batches of logical jobs the SSH session limit can be increased
to allow other actions to be performed while those jobs are running.
The SSH session limit for parallel execution is set to 10 by default on the appliance.
However, the session limit can be configured based on the requirement and if you
face bottleneck because of it. ASM has been validated with parallel executions.
Therefore, to reduce the waiting time, it is recommended to set the thread pool
size and parallel execution count to less than or equal to 50.
To change the Parallel SSH execution limit on the appliance to 50:
1. Log in as delladmin user.
2. Open the ./common/etc folder using the following command:
cd asm-galefore/gf/common/etc
3. Open the remoteExecServer.xml file and set the value for the following
parameters to less than equal to 50:
a. Set poolsize – Attribute in the threadpool node
b. Set executioncount – Attribute in maxparallel node
4. Run the reboot command to restart the server.