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..................................................................
Adding NetApp Ruby SDK................................................................................................................... 29 Enable HTTP or HTTPs for NFS share................................................................................................ 30 Configuring NetApp Storage Component......................................................................................... 30 6 Completing Initial Configuration....................................................................
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.
• Service Lifecycle Enhancements supports: – Ability to scale up storage, hosts, and virtual machines. – Ability to retry and deploy a failed service. Accessing Online Help ASM online help system provides context-sensitive help available from every page in ASM user interface. After you log in to ASM user interface, you can access the online help in any of the following ways: • To open context-sensitive online help for the active page, click ?, and then click Help.
After uploading an initial license, subsequent uploads replace the existing 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.
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 Client or SCVMM. Only one instance of ASM should be installed within a network environment. Exceeding this limit can cause conflicts in device communication. Information Prerequisites Before you begin the installation process: • Gather TCP/IP address information to assign to the virtual appliance.
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 • Users have access to the switches with passwords enabled.. • Switches have SSH connectivity enabled. • 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.
System Center Virtual Machine Manager (SCVMM) Prerequisites ASM manages resource on Microsoft System Center Virtual Machine Manager through Windows Remote Management (WinRM). Windows RM must be enabled on the SCVMM server. ASM requires Windows RM to utilize default port and basic authentication.
Deploying ASM using SCVMM To deploy ASM using SCVMM: 1. Extract the .zip file for 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: 12 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 ASM .vhd file: \Virtual Hard Disks\Dell-ActiveSystemManager-7.6-.vhd d.
3. To deploy 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.6- .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 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 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 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.
Configuring ASM Virtual Appliance as PXE Boot Responder ASM requires both PXE and DHCP network services to function. ASM virtual appliance contains a PXE service that is used to register resources with ASM so that workloads can be deployed. ASM virtual appliance must be deployed directly on the network configured for the PXE service. The PXE service requires a DHCP server configured to provide boot server (TFTP PXE server) information and specific start-up file information.
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. In the Add/Edit Condition dialog box, perform the following actions, and then click OK.
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 the ASM appliance.
Creating WinPE Image and Updating Install Media for Windows 2012 and Windows 2012 R2 To create WinPE Image and update Install Media for Windows 2008, 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. For example, ADK machine directory may be c:\buildpe. 2. In the razor-client.
5. Obtain a copy of the VMware Windows drivers for the VMXNET 3 adapter from VMware. To obtain the VMware Windows drivers: a. Install VMware tools on a running Windows 2012 or Windows 2012 R2 and on the virtual machine. b. Go to the C:\Program Files\Common Files\VMware\Drivers directory. c. Copy the contents in the Drivers folder to the directory that contains your WinPE build scripts. 6. Copy the files boot.wim and install.wim from the ASM virtual appliance to the directory on your ADK machine.
6. Make sure that the right privileges are granted to the repository files. "sudo chmod 755 /var/lib/razor/repo-store//bootmgr.exe" "sudo chmod 755 /var/lib/razor/repo-store//razorwinpe.wim" "sudo find -print0 | sudo xargs -0 chown razor:razor" “sudo setsebool -P samba_export_all_ro 1” Importing Linux ISOs on the Virtual Appliance for Operating System Deployment The following steps provide instructions to import Red Hat Enterprise Linux 6.
Customizing Virtual Machine Templates for VMware and Hyper-V 4 For ASM virtual machine (VM) cloning to work in conjunction with application components, you must customize the virtual machine and virtual machine templates, install the puppet agent, and then install the appropriate startup scripts.
connect to the same razor shared by connecting to \\\razor\puppetagent NOTE: The puppet agent version should be greater than 3.0.0 and lower than 3.4. After you install the puppet agent, make sure the puppet agent service is enabled to run on system start. For Windows, this must be done by viewing the services and setting the puppet agent service to "automatic".
Customizing Linux Template Perform the following task to customize Linux template. 1. You must update the Network Interfaces so that they will not be associated with the base virtual machine MAC address (varies based on OS, examples below). To update, run the following command: RHEL/CentOS: rm /etc/udev/rules.d/70-persistent-net.rules rm/lib/udev/rules.d/75-persistent-net-generator.rules sed -i "/^HWADDR/d" /etc/sysconfig/network-scripts/ifcfg-eth0 Debian/Ubuntu: rm /lib/udev/rules.
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 license is enabled for NFS on NetApp. To obtain and install the license, refer NetApp documentation.
8. Update the permissions on the NetApp module. To update the permissions, run the following command: sudo chmod 755 /etc/puppetlabs/puppet/modules/netapp/lib/puppet/util/ network_device/netapp/* 9. Change the owner of the files.
• Persistent • NFS Target IP 31
Completing Initial Configuration 6 Log in to ASM 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.6 User’s Guide.
