Active System Manager Release 8.2.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. © 2016 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’s New in this Release................................................................................................................... 5 Accessing Online Help..................................................................
Configuring NetApp Storage Component..........................................................................................31 6 Completing Initial Configuration.................................................................... 33 A Installing Windows ADK 8.2.1 for OS Prep for Windows............................ 35 Creating WinPE Image and Updating Install Media for Windows 2008 R2, Windows 2012 and Windows 2012 R2.........................................................................................
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.
Support for Dell PowerEdge R730xd server with Virtual vSAN ready node 6.2 (HY-6 Series). Accessing Online Help ASM online help system provides context-sensitive help available from every page in the ASM user interface. Log in to the ASM user interface with the user name admin and then enter password admin, and press Enter.
Licensing ASM licensing is based on the total number of managed resources, except for the VMware vCenter and Windows SCVMM instances. ASM 8.2.1 supports following license types: • Trial License — A trial license can be procured through the account team and it supports up to 25 resources for 90 days. • Standard License — A standard license grants full access. You receive an email from customer service with instructions for downloading ASM and your license.
Important Note Engaging support requires that all prerequisites are fulfilled by customer or deployment team. Third-party hardware support is not provided by Dell services. Discovery, inventory, and usage of third-party hardware must be in the expected state as described in the prerequisites and configuring sections of this guide. ASM Port and Protocol Information The following ports and communication protocols used by ASM to transfer and receive data. Table 1.
Installation and Quick Start 2 The following sections provide installation and quick start information, including step-by-step instructions for deploying and configuring ASM in VMware vSphere or Microsoft virtualization environment. Only one instance of ASM should be installed within a network environment. Exceeding this limit can cause conflicts in device communication.
Specification vCenter Pre-requisite • The virtual appliance is able to communicate with the OS Installation network in which the appliance is deployed. It is recommended to configure the virtual appliance directly on the OS Installation 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 C-Series Server Pre-requisite • Server facing ports must be configured for spanning tree portfast. • Network and BIOS configuration cannot be done using appliance. You need to do it manually. Hard Disk should be available for server to install OS. • • You need to set single NIC to PXE boot. This should be set as first boot device and hard disk should be set as second boot device. • Network must be configured on top-of-rack (ToR) switch which is connected to C-Series server.
Specification Pre-requisite • ASM performs certain basic port configuration for the server-side ports such as setting the server facing ports in portfast mode and configuring spanning-tree pvst edge-port. If you want to perform additional base or advanced port configuration at a port or global level on the switches, you must ensure that the configuration is performed before attempting any deployment with ASM.
Specification Pre-requisite Dell Compellent Storage Array • The management IP address is configured for the Storage Array. • All storage array members are added to the group. • Virtual ports must be enabled on Dell Compellent. Dell Compellent iSCSI on MXL with Hyper V • Follow Dell Compellent best-practices for storage configuration. • Storage Centers needs to be added to the Enterprise Manager before initiating the Element Manager discovery in ASM.
Specification Pre-requisite Sample port-channel member interface configuration FTOSA1#show running-config interface tengigabitethernet 0/ ! interface TenGigabitEthernet 0/41 no ip address mtu 12000 dcb-map DCB_MAP_PFC_OFF ! port-channel-protocol LACP port-channel 1 mode active ! protocol lldp advertise management-tlv management-address system-name no advertise dcbx-tlv ets-reco dcbx port-role auto-upstream no shutdown FTOSA1# VMware vCenter 5.1, 5.5 or 6.0 • VMware vCenter 5.1, 5.5 or 6.
Specification Pre-requisite NOTE: Prior to deployment of M1000e server, you need to disable FlexAddress every server in the chassis. To disable FlexAddress, follow the path:CMC > Server Overview > Setup > FlexAddress. You need to turn off server to disable FlexAddress. Ideally this should be done prior discovering the server. This setting applies to the chassis and the servers in the chassis, not to the IOM switches such as MXL or IOA.
Make sure that the SCVMM has its time synchronized with time of the associated timer server. If the SCVMM timer is set to 'off' mode by using the deployed Hyper-V hosts, you cannot add hosts and create clusters in SCVMM. Deploying ASM on VMware vSphere 1. Extract the .zip file to a location accessible by VMware vSphere Client. It is recommended to use a local drive or CD/DVD, because installing from a network location can take up to 30 minutes. 2. In vSphere Client, select File → Deploy OVF Template.
3. c. Click the Add Resource button. Browse to the location of ASM .vhd file: \Virtual Hard Disks\Dell-ActiveSystemManager-8.2.1-.vhd d. Under the Select library server and destination for imported resources section, click Browse. Select the destination folder in which ASM install VHD is located (for example, My_SCVMM -> MSCVMMLibrary -> VHDs), and then click OK. e. Click Import. To deploy ASM virtual appliance: a. In the left pane, click VMs and Services. b.
Deploying ASM on Hyper-V host To deploy ASM on Hyper-V host: 1. Open Hyper-V Manager in the Windows 2012 host. The Windows 2012 host should be displayed under Hyper-V Manager. 2. Select the host and select Action → Import Virtual Machine. 3. Select the folder containing ASM virtual appliance including snapshots, virtual hard disks, virtual machines, and import files. Click Next. 4.
This volume needs to be formatted manually from one of the servers that needs to be added to the cluster. 1. RDP to the Server using local administrator account. 2. Select Server Manager → Tools → Computer Management → Disk Management. 3. Select the volume that is failing 4. Select Online → Initialize disk (Partition Style MBR). 5. Create Simple Volume. Ensure to clear the drive letter. 6. On SCVMM, refresh the host and the cluster 7. Retry the deployment from ASM.
Configuring ASM Virtual Appliance 3 You must configure the following settings in the virtual appliance console before you start using ASM: • Change Dell administrator password. For more information, see Changing Delladmin Password • Configure static IP Address in the virtual appliance. For more information, see Configuring Static IP Address in the Virtual Appliance • Configure ASM Virtual Appliance as PXE boot responder.
NOTE: The default password for delladmin account is delladmin. 3. At the command line interface, run the command asm_init_shell. 4. In the Appliance Configuration dialog box, click Network Configuration. 5. In the Network Connections dialog box, click Wired → Auto eth0, and then click Edit. 6. In the Editing Auto eth0 dialog box, click IPv4 Settings tab. 7. Select Manual from the Method drop-down list. 8.
Customizing Virtual Machine Templates for VMware and Hyper-V 4 ASM supports cloning virtual machines (VM) or virtual machine templates in VMware, and cloning virtual machine templates in Hyper-V and in Red Hat Enterprise Linux.
• If the virtual machine being used does not have a DVD drive, you must add one. To do this, edit the settings of the virtual machine and add a DVD drive through your VMware management console. • Once a DVD drive is available, right-click the virtual machine and select Guest → Install/Upgrade VMware Tools. This mounts the media for VMware tools. • Log in to the operating system of the virtual machine and run the VMware tools installer within the OS running on the virtual machine.
• Configure the puppet.conf file to use "dellasm" as a server. To configure the puppet.conf file, perform the following: – Identify the location of the puppet.conf file. To do this, run the following command as "administrator" in Windows or "root" in Linux which displays the directory of the puppet.conf file. puppet config print config – Open the puppet.conf file by using a text editor and add the line "server = dellasm" to the [main], [master], and [agent] section.
NOTE: The puppet_certname.sh script that runs on startup of the VM clone attempts to install the ruby “inifile” and “hashie” gems from the Internet. If there is no internet connection, it generates error messages to communicate with rubygems.org. 4. It would be less error-prone to require the user to install the gems in the source VM rather than having them installed when the clone VM starts up. To do this, you need to: • Remove the gem install lines from puppet_certname.sh. • 5.
Customizing Windows Template Perform the following task to customize Windows template: 1. Make sure all instructions have been completed for VMware or Hyper-V virtual machines as noted in the previous section. a. b. c. d. e. 2. Install VMware tools (VMware only). Install puppet agent and ensure it is configured to run on startup. Make sure ASM appliance and virtual machine time are synchronized by NTP. Make sure DNS is configured for “dellasm” to resolve. Make sure puppet.
NOTE: After preparing the base virtual machine, in case the virtual machine is restarted, the puppet verification file will need to be deleted from system. This file can be found in Windows at C:\ProgramData\puppet_verification_run.txt or in Linux at /var/lib/ puppet_verification_run.txt. NOTE: Ensure that the VM template is not created using the Microsoft System Preparation Tool (sysprep) to avoid any failure during unattended operating system installation.
server=dellasm agent] server=dellasm NOTE: The puppet.conf file is available at the following location on the system with the guest operating system that you preparing: C:\ProgramData\PuppetLabs\puppet\etc. 8. Update the etc host file on the system with the guest operating system to ensure that the guest operating system is able to resolve dellasm. NOTE: The etc file is at C:\Window\System32\drivers\etc. To edit the etc host file, perform the following steps: 9. a. Open Notepad using the Start menu. b.
• Select the Run with highest privileges option. • Type the operating system name in the Configure for field. 4. NOTE: Ensure that the operating system you select aligns with the guest operating system you are preparing. Click OK. 5. Click Triggers. 6. On the Triggers page, select At startup and click Edit. 7. On the Edit Trigger window, update the following: • Select At startup from the Begin the task: drop-down menu. 8. • Select Enabled under Advanced Settings section. Click OK. 9.
Configuring ASM Virtual Appliance for NetApp Storage Support 5 For ASM to support NetApp, perform the following tasks: • Add NetApp Ruby SDK libraries to the appliance. For more information about adding SDK libraries, see Adding NetApp Ruby SDK. • Enable HTTP/HTTPs for the NFS share. For more information, see Enabling HTTP or HTTPs for NFS Share. Make sure that license is enabled for NFS on NetApp. To obtain and install the license, refer NetApp documentation.
5. Apply the patch(es) to update the NetApp SDK Ruby files. # sudo patch /etc/puppetlabs/puppet/modules/netapp/lib/puppet/util/network_device/netapp/ NaServer.rb
• Snapshot percentage • The Percentage of Space to Reserve for Snapshot • Auto-increment • Persistent • NFS Target IP 32
Completing Initial Configuration 6 Log in to ASM using the appliance IP address, After logging in to ASM, you need to complete the basic configuration setup in the Initial Setup wizard. After that you get four other wizards that allow you to define Networks, discover resources, configure resources, and publish template. For more information, see the Active System Manager Release 8.2.1 User’s Guide. NOTE: If you use the ASM 8.2.
A Installing Windows ADK 8.2.1 for OS Prep for Windows You need to perform the following configuration tasks before using ASM to deploy Windows OS. NOTE: You should use Microsoft ADK 8.2.1 installed in the default location. Make sure to install all options during ADK installation process. 1. Create a Windows .iso that has been customized for use with ASM using ADK and build-razorwinpe.ps1 script.
NOTE: • If any additional drivers are required, add the drivers under the “Drivers” folder in the build directory you created on your ADK machine. The drivers are installed into the Windows image, if applicable. The drivers that do not apply to the OS being processed are ignored. • If you want to deploy Windows to VMware VMs, the WinPE drivers for the VMXNET3 virtual network adapter from VMware required.
To add an OS image repository, perform the following tasks in the ASM GUI: 1. On the home page, click Settings → Repositories. 2. On the Repositories page, click OS Image Repositories tab, and then click Add. 3. In the Add OS Image Repository dialog box, perform the following actions: a. In the Repository Name box, type the name of the repository. b. From the Image Type drop-down menu, select the appropriate image type. c.
Configuring DHCP or PXE on External Servers B The PXE service requires a DHCP server configured to provide boot server (TFTP PXE server) information and specific start-up file information. ASM PXE implementation uses the iPXE specification so that the configuration details include instructions to allow legacy PXE servers and resources to boot properly to this iPXE implementation. This section provides information about configuring DHCP on the following servers.
4. In the New Class dialog box, type the following information and click OK to create a user class. a. In the Display Name box, type iPXE. NOTE: The binary for the output of the ASCII “iPXE” is (69 50 58 45). 5. b. In the Description box, enter iPXE Clients. c. In the data pane, under ASCII, enter iPXE. Click Close. Creating the DHCP Policy 1. Open the Windows 2012 DHCP Server DHCP Manager. 2. In the console tree, expand the scope that services your ASM OS Installation network.
1. Create DHCP User Class 2. Create DHCP Policy 3. Create Boot File Scope Option For additional information, see http://ipxe.org/howto/msdhcp Creating 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 an user class.
• 4. For PXE service to function properly, click 067 Bootfile Name and enter undionly.kpxe in the Value column. Also, in the right pane, based on your network settings, configure the following: • 003 Router (default gateway that is on the PXE network) • 006 Name Server (DNS server IP address) 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 at /etc/dhcp directory of most Linux distributions.
} } else { filename "undionly.kpxe"; } 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.
# This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend. #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.
# # # # # # # # # # # # #} } subnet 10.0.29.0 netmask 255.255.255.0 { option routers rtr-29.example.org; } 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.
