Active System Manager Release 8.3.
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. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Overview......................................................................................................................... 5 About this Document......................................................................................................................................................... 5 What’s New in this Release................................................................................................................................................
B Configuring DHCP or PXE on External Servers............................................................. 32 Configure DHCP on Windows 2012 DHCP Server............................................................................................................32 Creating the DHCP User Class...................................................................................................................................32 Creating the DHCP Policy...............................................................
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 the active page, click? , and then click Help. • 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 .1 User’s Guide • Active System Manager Release 8.3.
• Standard License—A standard license grants full access. After purchasing ASM, an email is sent from customer service containing instructions for downloading ASM software components, the ASM license file, and the ASM Service Tag. If you are using ASM for the first time, you must upload the license file using the Initial Setup wizard. To upload and activate subsequent licenses, click Settings → Virtual Appliance Management. 1.
Ports Protocols Port Type Direction Use 69 TFTP UDP Inbound Firmware Updates 80, 8080 HTTP TCP Inbound /Outbound HTTP Communication 123 NTP UDP Outbound Time Synchronization 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 NIF
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 vCenter Pre-requisite • 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. For more information, see the "Configuring DHCP or PXE on External Servers" section in this guide. • When deploying the ASM Appliance, ensure that the Default Gateway is specified.
Specification Pre-requisite Cisco servers • Network and BIOS configuration cannot be complete using Appliance. You must do it manually. 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 configured for spanning tree portfast. • If DCB settings are used, it must be properly configured on the switch for converged traffic.
Specification Pre-requisite For more information about creating alias, see Brocade for the Dell Compellent Compellent section in this topic. Dell Compellent iSCSI on MXL with Hyper V • Before initiating ASM service to create a volume on a newly configured Dell Compellent Storage array, create a temporary volume. A Storage type is instantiated on the Compellent Storage array, and used in creating a volume by ASM. • Enable LLDP and its corresponding attributes.
Specification Pre-requisite ! 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, 6.0, or 6.5 • VMware vCenter 5.1, 5.5, 6.0, or 6.5 is configured and accessible through the management and hypervisor management network. • Appropriate licenses are deployed on the VMware vCenter.
Pre-requisites for System Center Virtual Machine Manager (SCVMM) ASM manages resource on Microsoft System Center Virtual Machine Manager through Windows Remote Management (WinRM). Windows RM must be enabled on the SCVMM server and on Active Directory and DNS servers used in SCVMM/HyperV deployments. ASM deployments support Active Directory and DNS servers which exist on the same machine.
• If resource pools are configured—On the Resource Pool page, select the pool of virtual servers to deploy the Appliance virtual machine. • If resource pools are NOT configured—On the Hosts/Clusters page, select the host or cluster on which you want to deploy the Appliance virtual machine. Click Next to continue. 8. If there is more than one datastore available on the host, the Datastore page displays. Select the location to store virtual machine (VM) files, and then click Next to continue. 9.
3. In the Network Adapter 1 section, assign the adapter to your PXE VM Network. 4. Click Next. h. On the Select Destination page, select the destination host group that contains the Hyper-V server where you want to deploy ASM VM. Click Next. i. On the Select Host page, select the host on which you want to deploy ASM, and then click Next. j. On the Configuration Settings page, make the changes for your environment, if necessary. k.
virsh destroy [vm name] NOTE: To remove the virtual machine from the list, run the following command: virsh undefine [vm name] Downloading Catalog File To download the catalog file: 1. Go to Dell.com/asmdocs. 2. Click the latest version of the document, and then click Drivers & downloads → Systems Management. 3. Download the .zip file and extract file (ASMCatalog.xml) to a network (NFS or CIFS) share. 4. In ASM, click Settings → Repositories → Firmware/Software Repositories → Add. 5.
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.
Depending on your operating system, the installer may require extra packages (.rpms) which are dependencies and you must install it first. If the installer reports such dependencies, use the correct method for your operating system to find and install the dependencies, and then retry installation of the puppet agent. 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 that the puppet agent service is enabled to run on system start.
ssldir = $vardir/ssl [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig 1. Copy the puppet_certname.sh and puppet_certname.rb from the /opt/asm-deployer/scripts directory on the ASM Appliance to the /usr/local/bin on the source Linux virtual machine. NOTE: Ensure that the version of the inifile gem installed by the puppet certname script is specified as 2.0.2. To verify the version, open the puppet_certname.sh file and check that the inifile version is specified as 2.0.2. 2.
7. Create /etc/sysconfig/network-scripts/ifcfg-eth0 with the following content: BOOTPROTO=dhcp ONBOOT=yes HOTPLUG=yes DEVICE=eth0 TYPE=Ethernet PEERDNS=no NM_CONTROLLED=no Create /etc/sysconfig/network with the following content: NETWORKING=yes NETWORKING_IPV6=no 8. Configure a cron job that executes the puppet_certname.sh script and restarts the puppet service in reboot events.
– Installing the VMware tools—VMware only. – Installing the puppet agent and ensure that it is configured to run on startup. * You can install the puppet agent by accessing the agent on the ASM Appliance using the CIFS connection on the guest operating system or from the \\dellasm\razor folder in the local system. NOTE: It is recommended that you install the puppet agent version 3.6.2. * Run the puppet-3.6.2.msi file on the system with the guest operating system using an administrator access.
a. b. c. d. 5. Click the Actions tab. a. b. c. d. e. 6. Create theNew trigger. Select the At startup option from the Begin the task drop-down menu. Select Enabled under the Advanced Settings section. Click OK. Create New Action. Select Start a program from the Action drop-down menu. Click Browse to navigate to the C: drive and select the puppet_certname.bat script. In the Start in (optional) field, type C:\ Click OK. Click the Conditions tab. a.
• You can install the puppet agent by accessing the agent on the ASM Appliance using the CIFS connection on the guest operating system or at the following path in the local system \\dellasm\razor: • Move the puppet agent directory to a default location on the system with the guest operating system. NOTE: It is recommended that you install the puppet agent version 3.6.2. 3. Run the agent 3.2.1 .msi file on the system with the guest operating system. Perform this step using an administrator access. 4.
5 Enabling EMC VNX Support ASM uses Navicli to perform operations on EMC VNX. For discovery and deployments that involve VNX, the ASM Appliance must be installed with Navicli. You must install the Navicli tool manually, because the tool is available only to licensed Customers of EMC VNX. To install Navicli: 1. Download the Navicli Tool. a. 2. 3. To download the supported RPM version, go to Support.emc.com. b. Navigate to Downloads → Downloads for VNX/VNXe Family → Recommended → Navisphere CLI 7.33.8.1.
6 Completing Initial Configuration Log in to ASM using the appliance IP address, After logging in to ASM, you must 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.1 User’s Guide. NOTE: If you use the ASM 8.3.
A Installing Windows ADK 8.1 for OS Prep for Windows You must 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. Ensure 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.
