Active System Manager Version 7.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview......................................................................................................................5 About this Document............................................................................................................................ 5 What is New in this Release.................................................................................................................. 5 Accessing Online Help..............................................................
Updating Unattended Installation for Windows 2012 Version other than Windows 2012 Standard.........................................................................................................................................29 Updating Unattended Installation for Windows Hyper-V for Versions other than Windows 2012 R2 Datacenter.......................................................................................................................
Overview 1 Active System Manager (ASM) is Dell’s unified management product that provides a comprehensive infrastructure and workload automation solution for IT administrators and teams. ASM simplifies and automates the management of heterogeneous environments, enabling IT to respond more rapidly to dynamic business needs.
Additionally, in the online help, use the Enter search items option in the Table of Contents to search for a specific topic or keyword. Other Documents You May Need In addition to this guide, the following documents available on the Dell Support website at dell.com/ support/manuals provide additional information about the Active System Manager (ASM).
Operating System Internet Explorer Mozilla Firefox Google Chrome Windows 7 Version 9 and Later Version 26 and Later Version 32 and Later Red Hat Enterprise Linux 6.5 Not Supported Version 26 and Later Version 32 and Later Cent OS 6.5 Not Supported Version 26 and Later Version 32 and Later Supported Resources This section provides information about the resources supported by Active System Manager (ASM). The information has been segmented based on the resource types.
Resource Firmware Supported Cisco UCS B230 M2 2.1(3b) Cisco UCS B250 M1 2.1(3b) Cisco UCS B200 M3 2.1(3b) Supported Storage and Firmware Matrix The following table provides information about the supported storage resources. Resources Firmware Supported Dell PS4100 7.0 Dell PS6100 7.0 Dell PS6110 7.0 Dell PS6210 7.0 Dell SC8000* 6.3 Dell SC200* 6.3 Dell SC220* 6.3 * Indicates that the resource is supported only in ASM 7.5.1 and later versions.
Resource Firmware Supported Brocade M5424 * Brocade 6510 * * Indicates v7.2.0.a v7.2.0.a that the resource is supported only in ASM 7.5.1 and later versions. (Only for ESXi) Supported Adapters and Firmware Matrix The following table provides information about the supported adapters. Resource Firmware Supported Broadcom 5719 Quad-Port 1GbE Network Daughter Card 7.8 Broadcom 57810 -k Dul-Port 10Gb Mezzanine 7.8 Broadcom 57810 Dual-Port 10GbE Network Daughter Card 7.
Installation and Quick Start 2 The following sections provide installation and quick start information, including step-by-step instructions for deploying and configuring Active System Manager (ASM) in VMware vSphere Client or SCVMM. Only one instance of ASM should be installed within a network environment. Exceeding this limit can cause conflicts in device communication.
Specification Prerequisite deployed. It is recommended to configure the virtual appliance directly on the PXE network, and not on the external network. • The virtual appliance is able to communicate with the hypervisor management network. • The DHCP server is fully functional with appropriate PXE settings to PXE boot images from ASM in your deployment network.
Specification Prerequisite Dell Force10 S4810 switches (Top-of-Rack [ToR]) • The management IP address is configured for the ToR switches. • Any VLAN which is dynamically provisioned by ASM must exist on the ToR switch. • Server facing ports must be in hybrid mode. • Server facing ports must be in switchport mode. • Server facing ports must be configured for spanning tree portfast. • ASM creates the virtual machine (VM) traffic VLANs dynamically.
ASM requires Windows RM to utilize default port and basic authentication. To enable these settings, on the SCVMM server, open a Windows PowerShell interface with administrator permissions and run the following commands: winrm set winrm/config/client/auth '@{Basic="true"}' winrm set winrm/config/service/auth '@{Basic="true"}' winrm set winrm/config/service '@{AllowUnencrypted="true"}' The default amount of memory allocated for WinRM processes is limited to 150 MB.
Deploying Active System Manager using SCVMM To deploy Active System Manager (ASM) using SCVMM: 1. Extract the .zip file for the ASM build to a local folder on your SCVMM appliance . 2. To add ASM to the Library of Physical Library Objects in SCVMM, do the following: a. In the left pane, click Library. b. In the Home tab, click Import Physical Resource. c. Click the Add Resource button. Browse to the location of the ASM .
3. To deploy the ASM virtual appliance: a. In the left pane, click VMs and Services. b. Click the Create Virtual Machine button. c. Select Use an existing virtual machine, VM template, or virtual hard disk, and then click the Browse button d. From the list of sources, select VHD -> Dell-ActiveSystemManager-7.5.2- .vhd, and then click OK. e. Click Next. f. In the Virtual machine name text box, type the virtual machine name for your appliance, and then click Next. g.
9. After the ASM virtual appliance is deployed, right-click the ASM virtual appliance, and then click Settings. 10. In the Settings wizard, to enable the virtual switch, select VM-Bus Network Adapter. Optionally, provide a VLAN ID, if the host is tagged on a particular network, and then click OK. 11. Select the ASM virtual appliance, and then click Start under Actions.
Configuring the Active System Manager Virtual Appliance 3 You must configure the following settings in the virtual appliance console before you start using Active System Manager (ASM): • Change Dell administrator password. For more detailed information, see Changing Delladmin Password • Configure static IP Address in the virtual appliance. For detailed information, see Configuring Static IP Address in the Virtual Appliance • Configure ASM Virtual Appliance as PXE boot responder.
8. In the Addresses table, type the static IP address, subnet mask, gateway, and then click Add. 9. Click Apply to set the static IP address of the appliance. 10. For Hyper-V only, reboot ASM virtual appliance. Configuring ASM Virtual Appliance as PXE Boot Responder Active System Manager (ASM) requires both PXE and DHCP network services to function. The ASM virtual appliance contains a PXE service that is used to register resources with ASM so that workloads can be deployed.
5. Click Close. Create the DHCP Policy 1. Open the Windows 2012 DHCP Server DHCP Manager. 2. In the console tree, expand the scope that will service your ASM PXE network. Right click Policies and select New Policy. The DHCP Policy Configuration Wizard is displayed. 3. Next to Policy Name, type iPXE and enter the description as iPXE Client. Click Next. 4. On the Configure Conditions for the policy page, click Add. 5.
Create the DHCP User Class You must create the user class for the DHCP server before creating the DHCP Policy. 1. Open the Windows 2008 DHCP Server DHCP manager. 2. In the console tree, navigate to IPv4. Right click IPv4, and then click Define User Classes from the drop-down menu. 3. In the DHCP User Class dialog box, click Add to create a new user class. 4. In the New Class dialog box, enter the following information and click OK to create a user class. 5. a. In the Display Name box, enter iPXE.
Configuring DHCP for Linux You can manage the configuration of the Linux DHCPD service by editing the dhcpd.conf configuration file. The dhcpd.conf is located at /etc/dhcp directory of most Linux distributions. If the DHCP is not installed on your Linux server, install the Network Infrastructure Server or similar services. Before you start editing the dhcpd.conf file, it is recommended to back up the file. After you install the appropriate network services, you must configure the dhcpd.
After you modify the dhcpd.conf file based on your environment, you need to start or restart your DHCPD service. For more information, see http://ipxe.org/howto/dhcpd Sample DHCP Configuration # dhcpd.conf # # Sample configuration file for ISC dhcpd # #option definitions common to all supported networks... #option domain-name "example.org"; #option domain-name-servers 192.168.203.46; #filename "pxelinux.0"; next-server 192.168.123.
#subnet 10.254.239.32 netmask 255.255.255.224 { #range dynamic-bootp 10.254.239.40 10.254.239.60; #option broadcast-address 10.254.239.31; #option routers rtr-239-32-1.example.org; #} #A slightly different configuration for an internal subnet. #subnet 10.5.5.0 netmask 255.255.255.224 { #range 10.5.5.26 10.5.5.30; #option domain-name-servers ns1.internal.example.org; #option domain-name "internal.example.org"; #option routers 10.5.5.1; #option broadcast-address 10.5.5.
# # # # # # # # #} pool { allow members of "foo"; range 10.17.224.10 10.17.224.250; } pool { deny members of "foo"; range 10.0.29.10 10.0.29.230; } Deploying WinPE on the Virtual Appliance You need to perform the following configuration tasks before using ASM to deploy Windows OS. NOTE: You should use Microsoft ADK 8.1 or ADK 8.0 installed in the default location.. 1. Create a Windows repository with Windows installation media on ASM appliance.
7. Update permissions for the directory, by running the command: "sudo find -print0 | sudo xargs -0 chown razor:razor" Creating WinPE Image and Updating Install Media for Windows 2012 and Windows 2012 R2 To create WinPE Image and update Install Media for Windows 2012 and Windows 2012 R2: 1. Log in to the ASM virtual appliance and copy the scripts build-razor-winpe.ps1 and razor-client.ps1 from the /opt/razor-server/build-winpe directory to a folder created in the ADK machine.
8. To run the build script, run the command: powershell -executionpolicy bypass -noninteractive -file build-razorwinpe.ps1 NOTE: This step takes some time to complete. After completion, it creates a directory with the name razor-winpe under the current working directory. The final custom WinPE image, bootmgr.exe (for Windows 2012 R2 repositories), boot.wim, and install.wim are copied to this directory.
4. Go to the /opt/razor-server/installers/windows/ folder on your ASM virtual appliance, and using sudo and a text editor open the wim_boot.erb file. 5. Replace the two instances of bootmgr with bootmgr.exe and save the file. Updating Unattended Installation for Windows 2012 Version other than Windows 2012 Standard Windows 2012 operating system deployments other than Windows 2012 Standard require modifications to the default-unattended.xml.erb file. The current default-unattended.xml.
3. Enter the correct string required for the Windows image. Examples of the strings for Windows 2012 are: • Windows Server 2012 SERVERDATACENTER, • Windows Server 2012 SERVERDATACENTERCORE, • Windows Server 2012 SERVERSTANDARD, • Windows Server 2012 SERVERSTANDARDCORE.
7. Make sure that the correct privileges are granted to the repository files. “sudo find -print0 | sudo xargs -0 sudo chown razor:razor” 8. Active System Manager uses a default kickstart file to automate the installation of Linux. If you want to customize while installing the operating system, you can customize the kickstart file template “kickstart.erb” used to automate the installation. Use the sudo command to edit the kickstart.
Completing Initial Configuration 4 Log in to Active System Manager using the appliance IP address after completing the steps in this guide, After logging into ASM, you need complete the basic configuration setup in the Initial Setup wizard. For more information about completing the initial setup see the Active System Manger Version 7.5 User’s Guide.
