Active System Manager Release 8.
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. or its subsidiaries. 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................................................................................................................................................
7 Completing Initial Configuration.................................................................................... 30 A Installing Windows ADK 8.1 for OS Prep for Windows................................................... 31 Creating WinPE Image and Updating Install Media for Windows 2008 R2, Windows 2012 and Windows 2012 R2............31 Adding OS Image Repositories...................................................................................................................................
1 Overview 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.
• To open context-sensitive online help for a dialog box, click? in the dialog box. Also, 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 See http://www.dell.com/asmdocs for additional supporting documents such as: • Active System Manager Release 8.3 User’s Guide • Active System Manager Release 8.3 Release Notes • Active System Manager Release 8.
4. After uploading the license file, the following information about the license is displayed: • License Type • Number of Resources • Number of Used Resources • Number of Available Resources To replace the evaluation license with standard license, click Add under License Management section, click Browse beside Upload License and select a regular standard license file, and then click Open. 5.
Ports Protocols Port Type Direction Use 162, 11620 SNMP UDP Inbound SNMP Synchronization 443 HTTPS TCP Inbound /Outbound Secure HTTP Communication 443, 4433 WS-MAN TCP Outbound iDRAC and CMC Communication 129, 445 CIFS TCP Inbound /Outbound Back up program date to CIFS share 2049 NFS TCP Inbound /Outbound Back up program data to NIFS share 8
2 Installation and Quick Start 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 Pre-requisite • vCenter The DHCP server is fully functional with appropriate PXE settings to PXE boot images from ASM in your deployment network. Ensure that the Virtual SAN Default Storage Policy is set to the following default values: • • • • • Number of failures to tolerate: 0 Number of disks stripes per disk: 1 Force Provisioning: No Object space reservation: 0% Flash read cache reservation: 0.
Specification Pre-requisite • Network must be configured on top-of-rack (ToR) switch which is connected to C-Series server. • Necessary VLAN must be configured on the service facing port of that top of rack switch. NOTE: You need to place PXE VLAN-untagged for any kind of OS deployment. If it is Windows and Linux bare metal OS installation, you need to set workload network and you need to set Hypervisor management network for ESXi deployment.
Specification Pre-requisite • 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. • Fault Domain and IP Address configuration of iSCSI controllers needs to be done before discovery Element Manager in ASM. • Discovery of EM needs to be done with same credentials which are used for add storage center in Element Manager.
Specification Pre-requisite interface TenGigabitEthernet 0/41 no ip address mtu 9216 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.0 is configured and accessible through the management and hypervisor management network.
Specification Pre-requisite EMC storage • VNX alias must be created in the Brocade switches. For more information on creating alias, see Brocade for EMC VNX section in this topic. NOTE: Select the Thin LUN option only to create thin volumes. Pre-requisites for System Center Virtual Machine Manager (SCVMM) ASM manages resource on Microsoft System Center Virtual Machine Manager through Windows Remote Management (WinRM).
• To preallocate physical storage space to virtual machines at the time a disk is created, click thick provisioned format. Click Next to continue. 10. On the Ready to Complete page, review the options you selected on previous pages and click Finish to run the deployment job. A completion status window displays where you can track job progress.
m. Review the summary, select the Start Virtual machine after deploying it option, and then click Create. 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.
6. On SCVMM, refresh the host and the cluster 7. Retry the deployment from ASM. Deploying the ASM appliance as Kernel-based Virtual Machine (KVM) Before you begin deploying the ASM appliance as KVM, ensure that you have the following minimum connection requirements for the hypervisor: • An ethernet interface that uses a static IP to connect to the operating system. • An ethernet interface that is bound to the bridge device. 1. Extract the .
3 Configuring ASM Virtual Appliance 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.
7. Select Manual from the Method drop-down list. 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. Configuring Virtual Appliance with Two NICS If the OS Installation network is not routed, you must add an extra vNIC to the ASM appliance to make it communicate and respond to TFTP requests on the OS Installation network. 1. In VMware vSphere, select the Virtual Appliance and select “Power Off”.
4 Customizing Virtual Machine Templates for VMware and Hyper-V 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.
• Log in to the operating system of the virtual machine and run the VMware tools installer within the OS running on the virtual machine. For more information on installing VMware tools, see VMware documentation. The following customization is required for both VMware and Hyper-V virtual machine. Install the puppet agent on the virtual machine: • If the virtual machine being used was successfully created by ASM, the puppet agent will already be installed.
Customizing Linux Template Perform the following task to customize Linux template: 1. Ensure that 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 that it is configured to run on startup Make sure that ASM appliance and virtual machine time are synchronized by NTP. Make sure that DNS is configured for “dellasm” to resolve. Make sure puppet.
NOTE: Interface naming on RHEL 7 VM depends on the various factors provided at https://access.redhat.com/ documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/chConsistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy Debian/Ubuntu: rm /lib/udev/rules.d/75-persistent-net-generator.rules 6. Configure cronjob to execute the puppet_certname.sh script and restart or start the puppet service. Type the following commands: crontab –e a.
7. Make sure the task can run even you are not logged in and you must be able to run it with highest privilege. To enable this option, right-click the puppet_certname.bat and click Properties. In the puppet_certname properties dialog box, under Security options, select Run whether user is logged on or not. 8. Ensure that the check box is selected in the scheduled task settings for "If the running task does not end when requested, force it to stop." and select "Stop the existing instance" drop-down menu.
5. Ensure that DNS is configured for dellasm to resolve. Creating an entry in DNS with forward and lookup pointers enables you to pull and resource your ASM appliance instance. 6. Ensure that the file on the system with the guest operating puppet.conf system is updated to include dellasm as the server for each of the entries. 7. Open the puppet.
• Select the Run whether user is logged on or not option. • Select the Run with highest privileges option. • Type the operating system name in the Configure for field. NOTE: Ensure that the operating system you select aligns with the guest operating system you are preparing. 4. 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.
5 Configuring ASM Virtual Appliance for NetApp Storage Support 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.
Enabling HTTP or HTTPs for NFS share Connect to the NetApp Filer using ssh and run the option httpcommand to see the current settings. If the property httpd.admin.ssl is set to off, then run the command option httpd.admin.ssl.enable on to enable HTTPS. ADC-NetApp01> options http httpd.access legacy httpd.admin.access legacy httpd.admin.enable on httpd.admin.hostsequiv.enable on httpd.admin.max_connections 512 httpd.admin.ssl.enable on httpd.admin.top-page.authentication on httpd.autoindex.enable on httpd.
6 Installing Plug-ins for EMC to Support Volume Provisioning To support volume provisioning on a EMC VNX 5300 and VNX 5400 storage array, ensure that you install the plug-ins on a storage array. To install the Software Enabler feature: 1. Start Unisphere Service Manager (USM). 2. Log in to the storage array. 3. Copy the enabler (.ena file) to the c:\emc\repository\Downloads\VNX folder on the windows host where you installed USM. Create the folder in case the folder does not exist.
7 Completing Initial Configuration 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.3 User’s Guide. NOTE: If you use the ASM 8.
A Installing Windows ADK 8.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.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-razor-winpe.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.
c. In the Source File or Path Name box, type the path of the OS Image file name in a file share. d. If using a CIFS share, type the User Name and Password to access the share. These fields are only enabled when entering a CIFS share. For more information about firmware repositories, see ASM Online Help.
B Configuring DHCP or PXE on External Servers 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.
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. • Select User Class from the Criteria list. • Select iPXE from the list of Values and click Add. 6. On the Configure Conditions for the policy page, select the AND operator and click Next. 7.
Creating the DHCP Policy Use the new User Class to create a DHCP policy scope option. 1. Open the Windows 2008 DHCP Server DHCP manager. 2. Add a scope option to the DHCP scope that services ASM PXE environment. 3. In the Scope Options dialog box, click the Advanced tab, select the 067 Bootfile Name check box, and in the String value box, enter bootstrap.ipxe. NOTE: For PXE service to function properly, you must enter bootstrap.ipxe for the 067 Bootfile Name. 4.
} filename "undionly.kpxe"; Secondly, add the following code to the subnet declaration within your dhcpd.conf file. This code instructs a legacy PXE server to boot to a legacy boot file, and then directs to the iPXE boot file. For more information, see the Sample DHCP Configuration. The configuration file must contain the following information: # dhcpd.conf # Sample configuration file for ISC dhcpd next-server 192.168.123.
#subnet 192.168.123.0 netmask 255.255.255.0 { #} # This is a very basic subnet declaration. subnet 192.168.123.0 netmask 255.255.255.0 { range 192.168.123.24 192.168.123.29; option subnet-mask 255.255.255.0; option routers 192.168.123.1; if exists user-class and option user-class = "iPXE" { filename "bootstrap.ipxe"; } else { filename "undionly.kpxe"; } } # This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend. #subnet 10.254.239.32 netmask 255.255.255.
# # # # You can declare a class of clients and then do address allocation based on that. The example below shows a case where all clients in a certain class get addresses on the 10.17.224/24 subnet, and all other clients get addresses on the 10.0.29/24 subnet. #class "foo" { # match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; #} #shared-network 224-29 { #subnet 10.17.224.0 netmask 255.255.255.0 { #option routers rtr-224.example.org; # } # subnet 10.0.29.0 netmask 255.255.255.
