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
47
Following is the mapping of the Default Server Template networks with the networks
configured on the ESXi server
Table 7. Default ESXi Network Mapping
Type of Network
Server Template Network
Name
VMware ESXi Network Mapping
Hypervisor
Management
DefaultHypervisorManagement ESXi Management Network
Public LAN
DefaultWorkload
Virtual Machine Network
Private LAN DefaultvMotionLiveMigration ESXi vMotion Network
• Server Template names should not contain spaces.
• Server Templates for Active System 1000 VMware should have VM NICs with
the names: HypervisorManagement, vMotion, or Workload.
• Attaching more than one Server Profile Template to a physical orchestration
template will cause the physical orchestration to fail.
• In case multiple VM Workload VLANS are required, then use the “Add..” button to
add more. The networks needs to be added with naming convention “Workload-
<VLANID” e.g. Workload-20
Active System Manager does not pick up the workload VLAN based on the VLAN ID
defined in the Network setting. The workload VLANs are randomly picked up based
on the VLAN range defined for the layer 2 switch in the Active System Manager
Inventory System. If a specific workload VLAN ID is needed, it should be specified in
the VLAN Resource Type
Provisioning settings in the physical template.
• All the four networks listed above needs to have unique VLAN ID.
The network names should contain following substring for enabling RA to identify
proper networks
• Hypervisor Management network should contain "HypervisorManagement"
substring.
• Compute Live Migration network should contain "vMotionLiveMigration"
substring.
• Compute Cluster Private network should contain "HyperVClusterPrivate"
substring
• DHCP and static configurations are supported for Hypervisor Management, vMotion
and WorkLoad networks