Active System Manager Version 8.
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, 2009 – 2015 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..................................................................
5 Configuring ASM Virtual Appliance for NetApp Storage Support.............38 Adding NetApp Ruby SDK................................................................................................................... 38 Enable HTTP or HTTPs for NFS share................................................................................................ 39 Configuring NetApp Storage Component.........................................................................................
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.
• Deployment improvements including the ability to assign a specific hostname to IP address and pick a specific server for a deployment Accessing Online Help ASM online help system provides context-sensitive help available from every page in ASM user interface. Log in to ASM user interface with the user name admin and then enter password admin, and press Enter.
If you are using ASM for the first time, you must upload the license file through the Initial Setup wizard. To upload and activate subsequent licenses, click Settings → Virtual Appliance Management. 1. On the Virtual Appliance Management page, under the License Management section, click Add. License Management window is displayed. 2. Click Browse button beside Upload License and select an Evaluation license file, and then click Open.
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.
Deployment Prerequisites Specification Prerequisite Connection Requirements • The virtual appliance is able to communicate with the out-of-band management network and any other networks from which you want to discover the resources. • The virtual appliance is able to communicate with the PXE network in which the appliance is deployed. It is recommended to configure the virtual appliance directly on the PXE network, and not on the external network.
Specification Prerequisite C-Series Server • • 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.
Specification Dell PowerEdge M I/O Aggregator Dell Networking MXL 10/40GbE blade switch Dell 8 | 4 I/O modules Prerequisite • Server facing ports must be in hybrid mode. • Server facing ports must be in switch port mode. • 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. • Server facing ports must be in hybrid mode. • Server facing ports must be in switchport mode.
Specification Prerequisite Compellent Storage Array • The management IP address is configured for Storage Array • All storage array members are added to the group. • Virtual ports must be enabled on compellent. • Follow Compellent best-practices for storage configuration. • VMware vCenter 5.1 or 5.5 is configured and accessible through the management and hypervisor management network. • Appropriate licenses are deployed on the VMware vCenter.
Specification Prerequisite NOTE: Prior to deployment of FX2 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. • Server facing ports must be configured for spanning tree portfast.
Resource Prerequisites • Server facing ports need to have following configuration.. portmode hybrid switchport protocol lldp dcbx port-role auto-downstream no shut exit S5000 Following is the prerequisite for S5000. • Enable Fibre Channel capability and Full Fabric mode. feature fc fc switch-mode fabric-services • Enable FC ports connecting to Compellent storage array and FC ports connecting to other S5000 switch via ISL links. interface range fi 0/0 - 7 no shut • Create DCB Map.
Prerequisites for Rack Server, S5000, and Compellent The following table describes the prerequisites for the FCoE solution offered using Rack Server, S5000, and Compellent. For more information, see http://en.community.dell.com/techcenter/extras/m/ white_papers/20387203 Resource Prerequisites S5000 • DCB needs to be enabled. • VLT needs to be disabled. • Enable Fibre Channel capability and Full Fabric mode.
Resource Prerequisites MXL • DCB needs to be enabled. • VLT needs to be disabled. • FIP Snooping feature needs to be enabled on the MXL. conf Feature fip-snooping • Port-channel member interfaces needs to have below configuration.
Resource Prerequisites • Create a FCoE VLAN interface vlan [Create VLAN for FCoE] exit • Create FCoE Map fcoe-map default_full_fabric fabric-id vlan fc-map exit • Apply FCoE MAP to interface interface fibrechannel 0/0 fabric default_full_fabric no shutdown NOTE: Below is the process of generating the FC MAP For generating the fc-map use below ruby code. Here VLAN ID is FCoE VLAN ID fc_map = vlanid.to_i.to_s(16).upcase[0..1] fc_map.
Resource Prerequisites • Enable FC ports connecting to Compellent storage array and FC ports connecting to other S5000 switch via ISL links. interface range fi 0/0 - 7 no shut • Create DCB Map. dcb-map SAN_DCB_MAP priority-group 0 bandwidth 60 pfc off priority-group 1 bandwidth 40 pfc on priority-pgid 0 0 0 1 0 0 0 0 exit • Create a FCoE VLAN. interface vlan [Create VLAN for FCoE] exit • Create FCoE Map.
Resource Prerequisites port-channel-protocol lacp port-channel 128 mode active exit protocol lldp no advertise dcbx-tlv ets-reco dcbx port-role auto-upstream no shut exit • Port-channel connecting Cisco Nexus switch needs to have following configuration. interface port-channel 128 portmode hybrid switchport fip-snooping port-mode fcf • Server facing ports needs to have following configuration.
Resource Prerequisites Example interface vfc101 bind mac-address 5C:F9:DD:16:EF:07 no shutdown interface vfc102 bind mac-address 5C:F9:DD:16:EF:21 no shutdown • Move back into the VSAN database and create entries for the new VFC just created and create entries for the FC port(s) that will be used. vsan database vsan 2 interface vfc101 vsan 2 interface vfc102 vsan 2 interface fc2/1 vsan 2 interface fc2/2 NOTE: All the Compellent ports needs to part of the same VSAN.
Resource Prerequisites • Configure regular ethernet VLANs, and then the FCoE VLAN is created with an assignment to its respective VSAN. vlan fcoe vsan • Instantiate but do not configure the upstream port-channel (LAG) to the core /aggregation switch. • Instantiate but do not configure the downstream port-channel (LAG) to the IOA4. • Create the VFC interface to bind to the servers CNA FIP MAC address. This can be located in the CMC WWN table or the IDRAC page for the server.
Resource Prerequisites MXL • DCB needs to be enabled. • VLT needs to be disabled. • FIP Snooping feature needs to be enabled on the MXL. conf Feature fip-snooping • Port-channel member interfaces needs to have following configuration.
Resource Prerequisites • Create new VSAN — instantiate it in the VSAN database. conf vsan database vsan • Configure regular Ethernet VLANs, and then the FCoE VLAN is created with an assignment to its respective VSAN vlan fcoe vsan • Instantiate but do not configure the upstream port-channel (LAG) to the core /aggregation switch. • Instantiate but do not configure the downstream port-channel (LAG) to the IOA4.
Prerequisites for Rack Server, Cisco Nexus, Brocade, and Dell Compellent The following table describes the prerequisites for the FCoE solution offered using Rack Server, Cisco Nexus, Brocade, and Dell Compellent. For more information, see http://en.community.dell.com/ techcenter/extras/m/white_papers/20387203 Resource Prerequisites Cisco Nexus Following is the prerequisite for Cisco Nexus: • Enable “npv” feature on the switch. You need to reboot the switch and delete the old configuration.
Resource Prerequisites • Move back into the VSAN database and create entries for the new VFC just created and create entries for the FC ports that are used. vsan database vsan 2 interface vfc101 vsan 2 interface vfc102 vsan 2 interface fc2/1 vsan 2 interface fc2/2 NOTE: All the Dell Compellent ports need to part of the same VSAN. Brocade Alias needs to be created having Compellent fault domain WWPN, accessible on Brocade switch.
Resource Prerequisites • Server facing ports needs to have following configuration. portmode hybrid switchport protocol lldp dcbx port-role auto-downstream no shut exit Brocade Alias needs to be created having Dell Compellent fault domain WWPN accessible on Brocade switch. Dell Compellent Create fault domain as per Dell Compellent best practices.
3. On the Source page, click Browse, and then select the OVF package. Click Next to continue. 4. On the OVF Template Details page, review the information that is displayed. Click Next to continue. 5. On the End User License Agreement page, read the license agreement and click Accept. To continue, click Next. 6. On the Name and Location page, enter a name with up to 80 characters and then, select an Inventory Location where the template will be stored. Click Next to continue. 7.
d. From the list of sources, select VHD -> Dell-ActiveSystemManager-8.1- .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. On the Configure Hardware page, do the following: 1. In the Compatibility section, set Cloud Capability Profile to Hyper-V. 2. In the Processors section, change the processor value to 2, and then in the Memory section, change the memory value to 8 GB. 3.
11. Select ASM virtual appliance, and then click Start under Actions. Rectifying mounting errors during Hyper–V deployment For HyperV Cluster deployment, if the cluster configuration fails to mount the disk and create the cluster storage volume: Error 01 SCVMM reports DNS error during mounting of the available storage on SCVMM cluster. This is due to intermittent network failure during the mounting operation. Resolution Retry the deployment, so that ASM can retry to mount the volume(s).
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.
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. 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.
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.
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. • To install the puppet agent on the virtual machine, copy the puppet agent install files to the virtual machine. The puppet agent is available on the ASM appliance for both Windows and Linux in /var/lib/razor/repo-store directory.
[master] server=dellasm [agent] server=dellasm NOTE: Additional lines may be present in the puppet.conf file for your system. It is not necessary to delete any information from this file. You just need to ensure the previously noted section is present in the file. Customizing Linux Template Perform the following task to customize Linux template: 1. Ensure all instructions have been completed for VMware or Hyper-V virtual machines as noted in the previous section. a. b. c. d. e. 2.
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/ch-Consistent_Network_Device_Naming.html#secNaming_Schemes_Hierarchy Debian/Ubuntu: rm /lib/udev/rules.d/75-persistent-net-generator.rules 5. Configure cronjob to execute the puppet_certname.sh script and restart or start the puppet service. Type the following commands: crontab –e a.
b. On a Windows virtual machine, you must copy these scripts to “C:\” 3. Make sure the virtual machine has access to the internet, as this is required to download and install the necessary ruby gem files. If your virtual machine will not have access to the Internet, then download the ruby gem files for "inifile" and "hashie" and place them in the "C:\" directory where you copied the puppet certname scripts. 4. Launch Windows Task Scheduler and create a new task. 5.
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.
sudo patch /etc/pupetlabs/puppet/modules/netapp/lib/puppet/util/ network_device/netapp/NaServer.rb < /tmp/NaServer.patch 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.
• The Space Reservation Mode • Snapshot percentage • The Percentage of Space to Reserve for Snapshot • Auto-increment • Persistent • NFS Target IP 40
Completing Initial Configuration 6 Log in to ASM using the appliance IP address, After logging into ASM, you need to complete the basic configuration setup in the Initial Setup wizard. After that you will get four other wizards that allow you to define Networks, discover resources, configure resources and publish template. For more information , see the Active System Manger Version 8.1 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. Please 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 deploy Windows to VMWare VMs, the WinPE drivers for the VMXNET3 virtual network adapter from VMWare required.
b. In the Image Type box, enter the image type. c. In the Source File or Path Name box, enter the path of the OS Image file name in a file share. d. If using a CIFS share, enter 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.
a. In the Display Name box, enter 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. 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.
1. Create DHCP User Class 2. Create DHCP Policy 3. Create Boot File Scope Option For additional information, see http://ipxe.org/howto/msdhcp 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. • Click 066 Boot Server Host Name and enter the IP address or DNS name of ASM server in the Value column. • For PXE service to function properly, click 067 Bootfile Name and enter undionly.kpxe in the Value column.
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"; } } 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...
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.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.
# 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.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.
