Active System Manager Solution Guide Active System 1000 for VMware Version 7.
This document is for informational purposes only and may contain typographical errors and technical inaccuracies. The content is provided as is, without express or implied warranties of any kind. © 2013 Dell Inc. Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™, OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc.
Contents Introduction to the Active System 1000 Solution .................................................................... 8 Audience .................................................................................................................... 8 Support ...................................................................................................................... 8 Technical Documentation ................................................................................................
Configuring Networks ................................................................................................... 44 Accessing the Network Configuration Setup .................................................................. 44 Configuring the Networks ........................................................................................ 44 Configuring Default Server Templates ......................................................................... 46 Physical Templates and Orchestration ........
Storage Utilization (Consolidated) Report ....................................................................... 79 CPU and Memory Utilization Showback Report .................................................................. 79 Appendix A—Deployment Activities .................................................................................. 82 Verifying Active System Manager Services ....................................................................... 82 Appendix B—Build of Materials .................
Tables Table 1. Solution Component ....................................................................................... 9 Table 2. Active System 1000-Supported Configurations ...................................................... 10 Table 3. Deployment Options ..................................................................................... 11 Table 4. Deployment Prerequisites .............................................................................. 11 Table 5. Key Access Credentials ..
Figures Figure 1. Security Management—Users and Groups ............................................................ 26 Figure 2. Adding System Details ................................................................................... 28 Figure 7. Multiple Blade Server for Cluster Provisioning ...................................................... 48 Figure 8. Multiple Blade Server for Cluster Provisioning ...................................................... 49 Figure 9.
Introduction to the Active System 1000 Solution Today, many IT organizations are missing deadlines or cannot respond fast enough to customer demands, have insufficient IT budgets, or have to manage trade-offs. In response, convergence in the data center has emerged as a trend in IT to address the growing needs for agility, efficiency, and quality.
Technical Documentation The Dell Active System Manager documentation enables you to better understand your current Active Infrastructure, its deployment, and management software. For this release, we recommend that you familiarize yourself with the following documentation: • Active System 1000 Spec Sheet • Active System 1000 VMware ESX 5.x Reference Architecture • Active System Manager 7.1 User Guide • Active System Manager 7.
Management components Dell Active System Manager hosted in the management infrastructure VMware vCenter Server Compellent Enterprise Manager Dell Management Plug-in for VMware vCenter Dell OpenManage Essentials VMware vCloud Connector Compellent Plugin for VMware vCenter Active System 1000-Supported Configurations Table 1 lists the Active System Manager solution for the Active System 1000-supported configurations. Table 2.
Active System Manager Deployment The following topics describe how to deploy the Active System Manager: • Deploying OVF • Assigning IP Address to the Active System Manager Appliance • Installing Active System Manager License • Configuring Active System Manager Services Deployment Options The Active System Manager solution for Active System 1000 is packaged as a virtual appliance and is made available for VMware vCenter 5.
• For the Active System 1000 chassis, blade server, and IO aggregators: • • • Force10 S4810 switches (Top-of-Rack [ToR]) • • • • Brocade 6510 Fiber Switch and Dell 8 | 4 I/O modules Compellent Storage Array • • • VMware vCenter 5.
Importing OVF from the vSphere Client To import OVF from the vSphere Client, perform the following steps: 1. On the vSphere Client menu, click File > Deploy OVF Template. 2. Browse the OVF file and select “Next”. 3. Provide name of the Virtual Machine and select “Next”.
4. Select the appropriate datastore name where VM needs to be hosted. 5. Select the disk format. Thin provisioning is supported and recommended. 6. Select the network name. The VM needs to be mapped to the Hypervisor Management Network. All the networks (e.g. OOB, Hypervisor Management, vMotion, iSCSI and VM workloads) are expected to be accessible from the appliance. 7. Table 5 lists the necessary key access credentials to use. Table 5.
./stopasm.sh Make sure that all of the services are stopped before continuing. 2. Change the passwords using the standard Linux command passwd to change the passwords for any of the three stock accounts. o o o root delladmin oracle You will need root access to modify the passwords. Run the following commands: su passwd delladmin 3. Repeat these steps until all three user accounts have been modified.
2. Login as root user. Root user credentials are given in Table 5 - Key Access Credentials. 3. Go to System ->Preferences ->Network Connections. This will open a wizard. 4.
5. Selecting the Edit button on Network connections Wizard will open up the following dialog. For updating the IP address, select the IPv4 settings and select the method as “Manual” as shown in the below dialog. 6. Select Add button in dialog above to provide the IP address and other networking details like DNS as shown in the dialog below. 7. Add the ASM IP address to the /etc/hosts file and update the system to use an NTP server for date and time a. Stop ASM services.
8. Once this is done, open the terminal by clicking on Applications -> System Tools -> Terminal 9. Then execute the command “/etc/init.d/network restart”. 10. Login to the appliance with the newly configured IP Address. This will ensure that IP address is configured correctly on appliance.
3. In the License Deployment page, copy and paste the content of the license file provided in the License File text box. Click Submit to log on to the Active System Manager. Adding Additional Licenses To add a license: 1. Perform one of the following methods: • To add a license using web client, click SettingsLicense on the menu bar. • To add a license using thick client, click ToolsSettings on the menu bar, and click License tab.
cd $HOME/asm-galeforce/gf/sbin ./startasm.sh NOTE: The Active System Manager services must not be started by user “root” Stopping Services Following are the steps for stopping the services manually. 3. Log in as user “delladmin”. The password is listed in section Deploying OVF 4. Execute following command cd $HOME/asm-galeforce/gf/sbin ./stopasm.sh Verifying Service Status To verify that all Active System Manager services are up and running, perform the following steps: 5. Log in as user “delladmin”.
Lab: DEMO Status: Running Domain Services ---------------1.
2. Unzip the file into a specific folder destination on your hard drive. 3. Create the Active System Manager folder and move the file contents to this location. 4. In the console, execute the file “Active System Manager” Accessing Active System Manager using Windows client software 1.
2. Create the account setup. Select button “Setup…” 3. Select button “Add” 4. Provide the name of the connection and IP Address of the appliance.
5. Select “OK” and close the “Setting up Account” dialog box. 6. Select the account created in earlier step 7. Provide the username and the password for the appliance. The default username and password is admin/admin and select OK. This will launch the Active System Manager Application.
Active System Manager Setup This section captures the sequence of steps which should be followed within Active System Manager for managing deploying the blade servers in the Active System 1000. The sequence of steps includes: 1. User and Group Management 2. Discovering Active System 1000 Components 3.
Discovering Active System 1000 Components Discovery of the Active System 1000 components includes: • Dell M1000e Chassis • Dell M620 Blade servers NOTE: If your blade servers are configured to boot using UEFI, you must manually change the boot mode to BIOS before running discovery.
• In general for all the devices, when defining names and provisioning parameters, you should avoid using the following special characters: @ # $ % ^ () + = " | } { [ ] . , |:;"'?/> • The volume names of the Compellent Storage Array can contain only alphanumeric characters, and the following special characters: colon (:), period (.), and dash (-).
1. Select the individual components and provide the required IP address/login credentials. • Assettag—Required. Unique key or name used to import or identify the Dell M1000e Chassis within Active System Manager. For example Assettag Dell_Chassis_001 (a unique name) can be used to track the chassis in Active System Manager • Username—Username to access and manage the Dell M1000e Chassis. • Password—Password to access and manage the Dell M1000e Chassis. • IP Address—Required.
2. Provide the following element properties for the Dell Compellent Storage Array system: • Assettag—Required. Unique key or name for the Compellent Storage Array, which is used to import or identify a Compellent Storage Array in the Active System Manager. For example, Assettag Dell_Compellent_PS6100_1 (a unique name) can be used to track the storage array in Active System Manager • Username—Required. Username to access and manage the Compellent Storage Array. • Password—Required.
3. For Dell Force10 Switch (ToR) discovery, provide the following element properties and discovery attributes: • Assettag—Required. Unique key or name for Dell Force10 Switch which is used to import or identify the Force10 Switch in Active System Manager. For example, Assettag Dell_Force10-S4810_1 (a unique name) can be used to track the Force10 Switch in Active System Manager • Username—Required. Username to manage the Force10 switch. • Password—Required. Password to manage the Force10 switch.
4. For Brocade 6510 Fibre Switch (ToR) discovery, provide the following element properties and discovery attributes: • Assettag—Required. Unique key or name for Brocade 6510 Switch which is used to import or identify the Brocade Switch in Active System Manager. For example, Assettag Dell_Force10-S4810_1 (a unique name) can be used to track the Brocade Switch in Active System Manager • Username—Required. Username to manage the Brocade switch. • Password—Required. Password to manage the Brocade switch.
2. For VMware vCenter discovery, provide the following system properties: • Name—Required. Unique key or name for VMware vCenter which is used to import or identify vCenter in the Active System Manager. • Username—Required. Username to access and manage the vCenter. This user must have full administrator rights to the vCenter. If the vCenter Server is part of a Windows Domain, then enter the username as username@domain. • Password—Required. Password to access and manage the vCenter.
3. After completing the Active System 1000 components discovery, update the following information manually in the Active System Manager for all blade servers. These parameters will be used for configuring the ESXi Server. This information can be updated by using the multi-editor feature or by opening individual server instances. You can launch the multi-editor by selecting multiple server instances and then clicking Open with Multi-Editor.
Software Repositories in Active System Manager Appliance Configuring the following repositories is described in the Active System Manager User’s Guide, Chapter 6 – Firmware Management: • Updating Repository Elements for Dell Servers Configuring the following repositories is described in this document: • Updating Repository Elements for ISO Bootable Images • Updating Repository Elements for IOA Switch Configuration and Images • Updating Repository Elements for Brocade Firmware • Updating Repository
NOTE: User needs to copy the Windows 2012 System Center ISO image under /var/nfs folder on the ASM appliance with the same name WS2012_DC.iso.This will be used for installing the ISO image on Blade servers. NOTE: Before initiating ‘Discover’, please make sure ISO image files should be copied at required location ‘/home/delladmin/ISOBootImages’. 7. Right-click the selected discovered elements and update the Type to Image File, and click Finish.
Host: ASM server IPAddress BaseDirPath: Image Base Directory file location exists at tftpboot location. For example: Dell/IOM TFTPROOTPATH: TFTP Root path location located in ASM server. For example: /var/lib/tftpboot SSH Username: ASM server SSH username SSH Password: ASM server SSH password 6. Click Discover to initiate the discovery of the repository files.
Password: Repository server password Base Directory: Repository server base directory path where Brocade switch image files are copied. If image files are located at /var/lib/tftpboot/images/Brocade/6510 folder then base directory path value would be ‘/var/lib/tftpboot’. 6. Click Discover to initiate the discovery of the repository files.
/var/lib/tftpboot/configurationFiles/Brocade/6510/ then base directory path value would be ‘/var/lib/tftpboot’. 6. Click Discover to initiate the discovery of the repository files. The list of discovered elements in the repository display. NOTE: Before initiating ‘Discover’, please make sure Brocade switch configuration files should be copied at required location for each switch.
images are located at /var/lib/tftpboot/images/Dell/Force10/ then base directory path value would be ‘/var/lib/tftpboot’. 6. Click Discover to initiate the discovery of the repository files. The list of discovered elements in the repository display: NOTE: Before initiating ‘Discover’, please make sure Force10 switch configuration files and images should be copied at required location for each switch.
4. Using the drop-down menu, select VMware Baseline Images Repository and click Next. 5. Update the VMware vCenter host (IP address), username, and password, and click Next. 6. Click Discover to initiate the discovery of the repository files. The list of VMs managed by the vCenter display.
7. Right-click the selected discovered element, select Set Type > Image File, and click Finish. 8. Click Associate to associate the selected element with the VMware VM resource type and click Finish.
Configuring Networks This section discusses configuring networks required for Orchestration and end-to-end configuration. The various networks have to be configured prior to executing an orchestration: • Accessing the Network Configuration Setup • Configuring the Networks • Configuring Default Server Templates Accessing the Network Configuration Setup The network configuration setup can be accessed from the Tools->Discovery->Networking as shown in the below picture.
Figure 4. Editing an existing network Configuring Static Network If the static network ranges have to be configured, then selecting the “configure static IP address ranges” check box enables the other options where the static ranges can be configured as shown below. Figure 5. Editing an existing Static network In order to configure a new ip address range, press “Add IP Range” button, this will open new textboxes in the same window where the starting and ending ipaddress can be specified.
Figure 6. Ip Address range In order to configure the existing ip range, select the already configured range and select “Edit IP Range” button to modify the existing range and save them. The below table summarizes the list of values that needs to be configured for a network. Table 6. Values required for configuring network Entry Details VLAN ID The vlan ID that configured on the switch for this network type.
Following is the mapping of the Default Server Template networks with the networks configured on the ESXi server Table 7. Type of Network Hypervisor Management Public LAN Private LAN • Default ESXi Network Mapping Server Template Network Name VMware ESXi Network Mapping DefaultHypervisorManagement ESXi Management Network DefaultWorkload DefaultvMotionLiveMigration Virtual Machine Network ESXi vMotion Network • Server Template names should not contain spaces.
Figure 7. Multiple Blade Server for Cluster Provisioning For more information about server templates and profiles, see the Active System Manager 7.1 User Guide Chapter 7, "Server Templates and Profiles".
Physical Templates and Orchestration This section describes the following topics related to physical templates and orchestration: • Multiple Blade Server for Cluster Provisioning • Single Blade Server for Standalone ESX Host Provisioning • Associated Orchestrations with Cluster and Standalone Host Templates • Additional Storage for Cluster or Host • Updating Physical Templates Multiple Blade Server for Cluster Provisioning Template ‘AS1000 - Hypervisor Deployment ESXi - ISO – Cluster’ can be used
While scheduling the template, user would be prompted to provide values for the following orchestration parameters: Figure 9. Global Orchestration parameters The parameters such as ServerProfileTemplate with an icon associated with it are mandatory, while other parameters such as ESXServerLicenseKey are optional. Below table describes the global parameters that can be provided to orchestration. NOTE: Traffic shaping can limit the bandwidth usage of your VMs.
servers Storage VCenter ASMServerIPAddress Mandatory ASM appliance IP address ImageName Mandatory Selects the ESXi image from the repository. The orchestration is already mapped with an existing ESXi image available on the appliance.
When this template is scheduled, this template performs the following sequence of operations: 1. Reserves single or multiple VLANs for VM traffic using a VLAN component. In case the VLAN reserved in the session are not already configured on the ToR switches then VLANs are created and tagged to appropriate port-channels. 2. IOA Configuration based on Networks defined in Server Profile template and VLAN defined in VLAN component.
Navigate to Cluster → Edit Settings → vSphere HA dialog box and select the Enable: Disallow VM power on operations that violate availability constraints check box under Admission Control section. Navigate to Cluster → Edit Settings → VM Monitoring dialog box and select the Custom check box under Default Cluster Settings section. Single Blade Server for Standalone ESX Host Provisioning Template ‘AS1000 - Hypervisor Deployment ESXi – ISO – Standalone’ and can be used for installing ESXi 5.
8. Deselect Status. 9. Click OK. 10. Click Close When this template is scheduled, this template performs the following sequence of operations: 1. Reserves single or multiple VLANs for VM traffic using a VLAN component. In case the VLAN reserved in the session are not already configured on the ToR switches then VLANs are created and tagged to appropriate port-channels. 2.
Associated Orchestrations with Cluster and Standalone Host Templates Each physical template has three orchestrations (Figure 11 13) associated with it: Figure 11. On-demand Orchestrations 1. On-demand—VMFS Datastore Provision This orchestration can be executed on-demand when the session is in a Running state. 2. Setup—Configures the ESXi Servers using ISO Boot This orchestration executes when template provisioning starts and the session is in the Setting Up state. 3.
c. Execute the On-Demand orchestration. Alternatively, if you do not want to update the global parameter: a. Disable (uncheck) the ClusterVolumeSize parameter under Global Parameters Storage b. Specify the custom size directly on the “Input Values” screen c. Execute the orchestration For executing on demand orchestration, open the session by double-clicking it. On the session, right click and select the VMFS Datastore Provisioning orchestration for execution; see Figure 12. Figure 12.
• Allows access to specific cluster or standalone ESXi hosts, as applicable. • Creates a VMFS datastore on a cluster or standalone ESXI hosts, as applicable. Updating Physical Templates To update cluster and standalone templates that require specific data before scheduling a template for cluster provisioning, perform the following steps: 1. Update the template for a blade server. Updates the blade server count for cluster provisioning. 2.
4. Select the VLAN Component, click the Inventory tab, and update the VLANCount with the number of VLANs to be provisioned. The VLAN defined in the VLAN component are the Workload VLAN’s, other VLAN’s should be statically configured on the ToR switches. 5. Update the VLAN ID range, as applicable, and update the VLANId parameter. 6.
Workload Provisioning Using Logical Templates This section describes the following workload provisioning options using the Logical templates: • Pre-requisite to provision a Virtual Machine • Two VMs with a VLAN • Single Virtual Machine with a VLAN • Updating a Baseline VM Image on Logical Templates NOTE: Refer to the VMware RA readme.
• Once the VMs are provisioned the user can also launch custom applications as applicable using custom methods from Active System Manager- Windows client.
1. Select the VM object in the template and click the Image Files tab. 2. Select the already associated image file and click Remove to remove the existing association.
3. Click Add and select the gold VM image to be associated with the VM object. Customizing the Guest OS (Optional) Active System Manager supports Windows 2012 and Windows 2008 based Guest OS for VM creation. However, during Windows 2008 VM creation, Active System Manager is not able to retrieve the VM IP address. In this case, the Windows 2008 VM does have an IP address, but Active System Manage is not able to retrieve the IP address using the supported API set.
c. WindowsTimeZone d. GuestCUstomizationRequired e. GuestWindowsDomainAdministrator Figure 15.
Operation Center View—Administrative Operations This section describes the administrative operations available in the Operation Center view: • Managing Dell Blade Server • Managing Dell Force10 IOA • Managing Dell Force10 ToR Switch • Managing Brocade Switch • Managing VMware vCenter Objects Managing Dell Blade Server Blade servers along with their attributes are discovered and populated in the Active System Manager Operation Center view.
Power On Server This method is used to power on the blade servers using server iDRAC. Update firmware on server This method applies firmware DUPs for components (LC, iDRAC, BIOS etc) for a server. Managing Dell Force10 IOA Switch Dell Force10 IOA along with their attributes are discovered and populated in the Active System Manager Operation Center view. This view (Figure 17) enables methods to be executed on Dell Force10 IOA for on demand provisioning, as required. Figure 17.
Figure 18. Force10 ToR Switch view Table 10. Force10 ToR Switch operations Operation Description Configure Switch This method is used to upgrade or downgrade a firmware version on a Dell Force10 ToR switch. Managing Brocade Switch Brocade switches along with their attributes are discovered and populated in the Active System Manager Operation Center view. This view (Figure 19) enables methods to be executed on Brocade switch for on demand provisioning, as required.
Figure 19. Brocade Switch view Table 11. Operation Configure Brocade Switch Brocade Switch operations Description This method is used to upgrade or downgrade a firmware version on a Brocade switch. Also method can be used to update the switch configuration.
Figure 20. VMware Clusters view Table 12. VMware Cluster Operations Operation Description Add DataStore to an existing cluster This method adds the data store to an existing cluster. List Cluster Datastore This method lists the datastores on the cluster. Move Host to Cluster This method moves the host that is present in data center level to the existing cluster. VMware Hosts VMware hosts, along with their attributes, are discovered and populated in the Active System Manager Operation Center view.
Figure 21. VMware Host view Table 13. VMware Hosts operations Operation Description Add DataStore to Host This method is used to add an existing datastore to a cluster visible in Operations View. Apply Host Profile This method is used for applying the specified profile to a specified Host. While applying the host profile please make sure both the Hosts physical configuration should be same. User can not apply the profile having more than one physical NIC to a host having single NIC.
VMware Virtual Machines VMware Virtual Machines, along with their attributes, are discovered and populated in the Active System Manager Operation Center view. This view (Figure 22) enables methods to be executed on VMware Virtual Machines for on demand provisioning, as required. Figure 22. VMware Virtual Machines view Table 14. VMware Virtual Machines operations Operation Description Clone to Template This method is used to clone a Virtual Machine to a template.
VMware Datastores VMware Datastores, along with their attributes, are discovered and populated in the Active System Manager Operation Center view. This view (Figure 23) enables methods to be executed on VMware Datastores for on demand provisioning, as required. Figure 23. VMware Datastores view Table 15. VMware Datastore operations Operation Description Remove Datastore This method is used to remove a data store from vCenter.
Dashboard Reports The Active System Manager Dashboard displays allocation and utilization graphs for various resources like VM, cluster, host, storage, and so on, including: • 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 • Storag
Resource Allocation by Hosts Report This report provides resource allocation data for hosts on which some virtual resources are provisioned in running sessions. This report displays CPU and memory allocations grouped by hosts, and can be used to view a current usage of the CPU and memory allocation per host for a data center. Figure 25 displays an example of a Resource Allocation by Hosts report. Figure 25.
Figure 26. Resource Allocation by Groups Report Top Ten Resource Allocation Report This report includes three sub-options for different groupings: • By Host—Lists top ten hosts which are currently in use and have allocated maximum CPU and memory attributes. • By User—Displays the list of top 10 users who are currently consuming the maximum number of CPUs and memory. • By Group—Similar to “By User”, but consolidated at the group level.
Figure 27. Top Ten Resource Allocation Report Top Ten Resource Utilization Report This report is similar to the Top Ten Resource Allocation report; however, this report provides utilization data as opposed to allocation. The required data is made available using a monitoring method that continuously keeps polling the device, VM, or cluster for current utilization data. The data is persisted in the database and the last polled data is provided to the user.
Figure 28. Top Ten Resource Utilization Report VM Utilization by Session Report This report provides the most recent data for CPU and memory utilized on any VM, grouped by sessions. This data is available in terms of percentage with respect to the allocated limits.
Figure 2930 displays an example of a VM Utilization by Session Report. Figure 29. VM Utilization by Session Report Host Utilization (Consolidated) Report This report displays information about how much capacity is being utilized on a host by all running VMs, with respect to the allocated capacity. This report is available for CPU and memory attributes.
Figure 30 displays an example of a Host Utilization (Consolidated) report. Figure 30. Host Utilization (Consolidated) Report Cluster Utilization (Consolidated) Report This report is similar to the Host Utilization (Consolidated) report, except that it works for clusters. Figure 31 displays an example of a Cluster Utilization (Consolidated) report. Figure 31.
Storage Utilization (Consolidated) Report This report provides storage utilization as a percentage of allocated storage for clusters. Figure 32 displays an example of a Storage Utilization (Consolidated) Report. Figure 32. Storage Utilization (Consolidated) Report CPU and Memory Utilization Showback Report This report provides CPU and memory utilization of Hosts in percentage over a period of given time (e.g. Weekly, Daily, and Hourly).
Figure 33 displays an example of a CPU and Memory Utilization Showback report. Figure 33. CPU & Memory Utilization Showback Report You can view the data for a specific time interval (with a minimum time interval limit of ten minutes between two data points). To view the specific time interval data, select a point and drag the mouse to a desired data point; this will show the data for the specific time interval. You can rest the time interval to default by clicking Reset Zoom (see Figure 34).
Figure 34.
Appendix A—Deployment Activities Verifying Active System Manager Services To verify that all Active System Manager services are up and running, perform the following steps: 1. Log in as the user who installed the services. 1. Run the following script to display the current status of all services, including the Oracle database status: cd asm-galeforce/gf/sbin ./asmstatus.sh Below is sample output: Active System Manager Services Status Installation ---------------Release Version: 7.
Appendix B—Build of Materials Table 10 displays a list of build of materials, grouped by Resource Adapters. Table 16.
Appendix C—Firmware and Software Base Lineup The following table lists the minimum recommended firmware/software versions. Table 18. Firmware and Software versions Device Revision Hypervisor Server – M620 BIOS 1.7.6 CPLD 1.0.4 A00 iDRAC7 Enterprise 1.40.40 Build 13 LCC (Life Cycle Controller) 2 1.1.5.165 Network Controller Broadcom FW 7.6 QLogic QME2572 8Gb FC 4.0.0.18 VMware ESXi 5.1 U1 (1065491) A01 Management Server – R620 BIOS 1.6.0 iDRAC7 Enterprise 1.40.
Device Revision Management VMs and Software Windows Server 2012 1.6.0 VMware vCenter 5.1 U1 (1064983) Compellent Enterprise Manager 6.3 Compellent Plugin for vCenter™ 1.5.3 Management Plugin for vCenter (Spectre) 1.7 OpenManage Essentials 1.2 VMware vCloud Connector vCCServer 2.0 Active System Manager 7.1 vCCNode 2.
Appendix E—Adding New ESXi ISO Images This appendix describes the following topics related to adding new ESXi images: • Download Image ISO • Modifying the ESXi boot.cfg Configuration File • Creating a Kickstart Configuration File • Adding the new image to the software repositories Preparing the VMware ESXi 5.x Installation Media To prepare the VMware ESXi 5.x installation media, perform the following steps: Download Image ISO 1. Login to www.dell.com 2. Open the support and driver page http://www.
# mkdir /home/delladmin/ISOBootImages/esxi5.1_dell_ISOBoot_New # mount -o loop VMware-VMvisor-Installer-5.1.0-799733.x86_64Dell_Customized_RecoveryCD_A00.iso /tmp/dellISO # cp -fr /tmp/dellISO /home/delladmin/ISOBootImages/esxi5.1_dell_ISOBoot_New # chmod +w /home/delladmin/ISOBootImages/esxi5.1_dell_ISOBoot_New/* NOTE: In case the newly added image need to replace the existing image, then execute following commands mv /home/delladmin/ISOBootImages/esxi5.
Creating a Kickstart Configuration File To create a kickstart configuration file, perform the following steps: 1. Create the image directory on the HTTP server base location: # cd /home/delladmin/ISOBootImages/esxi5.1_dell_ISOBoot_New The name of the directory needs to be same as the image directory created on the TFTP server. 2. Create a file named “ks.cfg” inside the image directory.
o ESXi license Key. The value is added if the license key information is available in the resource adapter configuration file. o Name of the Local datastore 3. Copy the ks.cfg file to the HTTP Server base location. mkdir –p /var/www/html/esxi5.1_dell_ISOBoot_New/ cp /home/delladmin/ISOBootImages/esxi5.1_dell_ISOBoot_New/ks.cfg /var/www/html/esxi5.1_dell_ISOBoot_New/ks.cfg In case the existing image directory is replaced, then skip above commands and execute the following mkdir –p /var/www/html/esxi5.
Appendix G— Planning Worksheet Out of Band Management IP Address Configuration Equipment IP Address Subnet Mask Gateway Username Chassis 1 CMC Chassis 2 CMC iDRAC for all M620 Force10 S4810 Switch1 Force10 S4810 Switch2 Compellent Management Active System Manager Appliance vCenter ESXI Server IP Configuration Following parameters for each server is required: • ESXServerHostname—Hostname to be assigned to the ESXi server.
• This volume needs to contain the base line VMs that will be used for creating the VM workloads NOTE: The base line VMs needs to have VMware Tools installed.
Appendix I—FAQs 1. The orchestrations assume that Port Channel 2 is configured on the switches. If not, you get a failure indicated by red links on the session. The list of port-channels are configurable, based on the environment this list could be controlled by updating the “portChannelList” in the “ssi.properties” file under “$HOME/asm-galeforce/gf/common/integrations/Dell/Force10-S4810” 2.
• Operation center view • Link information Synchronize process discovers only the Operation center view hierarchy. 5. SSI properties will be overwritten when upgrading RA Yes upgrading the RA will override the ssi.properties file.
Appendix B—Build of Materials. Images and firmware versions that are released after Active System Manager 7.1 should work but this should be validated with the solution. 7. What is base level configuration and what is consists of for Dell Force10 switches? Base level configuration is the minimal set of configuration running on the switches so as to bring them to an operational state. Additional details of these configurations can be found in the embedded sample configuration file.
types and instances before they can be used for provisioning various resources in the environment. Refer section Updating Repository Elements for ISO Bootable Images for an example 13. How to change the hostname of the Active System Manager Server? To change the host name of the Active System Manager server: a. Log in to the Active System Manager appliance as a root user. b. Open the /etc/sysconfig/network file and specify the new host name in the HOSTNAME field. c.
18. Can I remove a server from a session, to either free up the unused servers or to removing servers that have gone bad. No. This is not a supported use case. 19. While creating/editing the server profile template or attaching server profile to a server, can I select firmware files from different repositories? No, selected firmware files must belong to a single repository. For example, if you choose iDRAC and BIOS firmware for update; both should be from the same repository. 20.
template should be a subset of VLANs defined on the VLAN component in ASM template. 25. Does ASM configure NTP on the ESXi host? NTP is not configured on the ESXi host; user needs to manually configure the NTP setting on the ESXi host. 26. Interface mapping (DIS links) between the end devices is not correct as they don’t represent the actual location of the end devices. Links discovered during discovery don’t represent the actual connection between the end devices, those are dummy connections.
• 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.
33. How do I use the Gold/Base VM ? Go to ASM logical template , Click on VirtualMachine resource type , Click on Add button associate the discovered VM images as shown in below screenshot: 34. Can I add new VLANs to a running physical session? Yes, you can add new VLANs to a running session. To add VLANs to a running session, perform the following steps: a. From Components view, drag and drop a new VLAN component in a running session. b. Click Save in order to save the changes done to the running session.
d. Add the new VLAN ID added in the running session manually to the list of Networks by going into the Networking Configuration tab available under Setup. Figure 36. Add a PUBLIC_LAN Configuration e. Update the Server Profile Template to incorporate the new VLAN ID. Figure 37. Edit vNIC Configuration f.
Figure 38. Attach Server Profile g. Execute the Dell Server custom operation VMware - Update ESXi Server Port Group VLAN Info to configure the required port-groups on the vSwitch corresponding to new VLAN component in session. This step adds the new VLANs to the ESXi Host.
