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. 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..................................................................
Customizing Linux Template..............................................................................................................38 Customizing Windows Template....................................................................................................... 39 5 Configuring ASM Virtual Appliance for NetApp Storage Support............. 41 Adding NetApp Ruby SDK to ASM Virtual Appliance..........................................................................
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.
• Port view virtualization – A graphical view that provides a mapping of physical to virtual infrastructure and clear notification of connectivity issues. • Brownfield support to facilitate installing ASM into the existing environment – Includes support for importing existing ESXi hosts and clusters as ASM resources, and the ability use them without requiring ASM to have originally provisioned them. It also enables key features including infrastructure level health and firmware updates.
• Active System Manager Release 8.2 Release Notes • Active System Manager Release 8.2 Compatibility Matrix • Active System Manager Release 8.2 SDK Reference Guide • Active System Manager Integration for VMware vRealize Orchestrator user’s Guide • Active System Manager Release 8.2 API Reference Guide For more information about ASM including how to videos, white papers, blogs and support forum, see Dell Active System Manager page on Dell TechCenter: www.dell.
5. • License Type • Number of Resources • Number of Used Resources • Number of Available Resources • Expiration Date To replace the evaluation license with standard license click the same Add button under License Management section, click Browse button beside Upload License and select a regular standard license file, and then click Open. You get information regarding license type, number of resources and expiration date of the uploaded license on License Management window. 6.
Ports Protocols Port Type Direction Use 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 NIFS share 9
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 Dell PowerEdge Servers Prerequisite • 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. • 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 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 in switchport 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. • Switches have SSH connectivity enabled.
Specification Dell 8 | 4 I/O modules Prerequisite • If ASM is used to perform the initial configuration of credentials and IPs on the IOM in the blade chassis, you need to make sure, no enabled password is configured on the switches. • Switches have SSH connectivity enabled. • 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.
Specification Prerequisite ! interface TenGigabitEthernet 0/15 no ip address mtu 12000 portmode hybrid switchport flowcontrol rx on tx off spanning-tree 0 portfast spanning-tree pvst edge-port dcb-map DCB_MAP_PFC_OFF ! protocol lldp advertise management-tlv management-address system-name dcbx port-role auto-downstream no shutdown Sample port-channel member interface configuration FTOSA1#show running-config interface tengigabitethernet 0/ ! interface TenGigabitEthernet 0/41 no ip address mtu 12000 dcb-map D
Specification Prerequisite 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. • Appropriate licenses are deployed on the VMware vCenter. System Center Virtual Machine Manager (SCVMM) • See System Center Virtual Machine Manager (SCVMM) Prerequisites.
Configure an FCoE map Applied on the Downstream (Server-Facing) Ethernet and Upstream (CoreFacing) FC Ports. Assuming FCoE VLAN is 1002 the same command needs to be executed on both FCoE Switches.
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 Table 4. Prerequisites for Rack Server, S5000, and Compellent Resource Prerequisites S5000 • DCB needs to be enabled. • VLT needs to be disabled. • Enable Fibre Channel capability and Full Fabric mode.
Prerequisites for M1000e (with MXL), S5000, Brocade, and Compellent The following table describes the prerequisites for the FCoE solution offered using M1000e (with MXL), S5000, Brocade, and Compellent. For more information, see http://en.community.dell.com/techcenter/ extras/m/white_papers/20387203 Table 5. Prerequisites for M1000e (with MXL), S5000, Brocade, and Compellent Resource Prerequisites MXL • DCB needs to be enabled. • VLT needs to be disabled. • Switches have SSH connectivity enabled.
Resource Prerequisites • 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 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
Resource Prerequisites • VLT needs to be disabled. • Enable Fibre Channel capability and Full Fabric mode. feature fc • 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.
Table 7. Prerequisites for M1000e (with MXL), Cisco Nexus, and Compellent 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 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, and Compellent The following table describes the prerequisites for the FCoE solution offered using Rack Server, Cisco Nexus and Compellent. Table 8. Prerequisites for Rack Server, Cisco Nexus, and Compellent Resource Prerequisites Cisco Nexus Following is the prerequisite for Cisco Nexus. • Enable required features.
Resource Prerequisites 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. Compellent Create fault domain as per Compellent best practices. Prerequisites for M1000e (with MXL), Cisco Nexus, Brocade, and Dell Compellent The following table describes the prerequisites for the FCoE solution offered using M1000e (with MXL), Cisco Nexus, Brocade, and Dell Compellent. Table 9.
Resource Prerequisites protocol lldp dcbx port-role auto-downstream no shutdown exit Cisco Nexus Following is the prerequisite for Cisco Nexus: • Enable “npv” feature on the switch. This requires switch reboot and old configuration will be wiped off. (Ensure to backup the configuration before enabling the feature) conf feature npv • Enable required features . feature fcoe feature npiv feature lacp • Create new VSAN — instantiate it in the VSAN database.
Resource Prerequisites 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 Dell Compellent • Alias needs to be created having Dell Compellent fault domain WWPN accessible on Brocade switch. Create a single alias including the virtual ports for the Compellent fault domain, WWPN accessible on Brocade switch.
Resource Prerequisites • Create 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.
Resource Prerequisites default password does not impact ASM's ability to ssh into the switch. Dell Compellent Create fault domain as per Dell Compellent best practices. Prerequisites for M1000e (with MXL and FC FlexIOM), Brocade, and Dell Compellent The following table describes the prerequisites for the FCoE solution offered using M1000e (with MXL and FC FlexIOM), Brocade, and Dell Compellent. Table 11.
Resource Prerequisites • Dell Compellent Brocade root password needs to be changed so that the banner presented to change the default password does not impact ASM's ability to ssh into the switch. Create fault domain as per Dell Compellent best practices. Prerequisites for System Center Virtual Machine Manager (SCVMM) ASM manages resource on Microsoft System Center Virtual Machine Manager through Windows Remote Management (WinRM).
• 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.
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 4, and then in the Memory section, change the memory value to 16 GB. NOTE: The number of "big" processes that can be executed in parallel by default is set to the number of processors assigned to a VM.
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.
Configuring Static IP Address in the Virtual Appliance 1. In VMware Sphere, click the Console tab to open the console of the virtual appliance or use the SSH protocol to connect to ASM virtual appliance IP (ssh needs to be enabled on the appliance). 2. Log in to the console with the user name delladmin, enter current password, and then press Enter. NOTE: The default password for delladmin account is delladmin. 3. At the command line interface, run the command asm_init_shell. 4.
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.
• 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. If the virtual machine being customized has network access to the ASM appliance, you can connect to this same directory as a network share directory using the address: \\\razor\puppet-agent .
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.
RHEL 7 Remove MAC Address from the interface configuration file. For example, sed -i "/^HWADDR/d" /etc/sysconfig/network-scripts/ifcfg-ens192 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 6. Configure cronjob to execute the puppet_certname.
NOTE: The version of the INI file in puppet certificate script should be specified as 2.0.2. To verify this, open the puppet_certname.sh file and check that the INI file version is specified as 2.0.2 or not. 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.
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.
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 43
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 Release 8.2 User’s Guide. NOTE: If you use the ASM 8.
A Installing Windows ADK 8.2 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 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.
To add an OS image repository, perform the following tasks in the ASM GUI: 1. In the left pane, 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, enter the name of the repository. 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.
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.
4. In the New Class dialog box, enter the following information and click OK to create a user class. 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.
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. For PXE service to function properly, click 067 Bootfile Name and enter undionly.kpxe in the Value column. Additionally, in the right pane, based on you 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.
} } 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.
