Users Guide

HBA Card Vendor Storage Networking Protocol Support for Stateless Deployment Tasks*
Mellanox iSCSI
* Deploy Virtual I/O Identities, Reclaim Virtual I/O Identities, and Replace Server
Related Tasks
Setting Up Device Configuration Auto Deployment (Stateless Deployment)
Deploying a Device Configuration Template (Stateless Deployment)
Known Limitations for Stateless Deployment
The following are the known limitations for deploying virtual I/O identities on target servers:
• To deploy virtual I/O identity attributes in Converged Network Adapter (CNA) cards for FCoE protocol,
you must predefine the octet values or import values for the FC attributes in the virtual pool even
though the values generated by OpenManage Essentials are based on the virtual FIP MAC address.
• On Broadcom network adapters, OpenManage Essentials does not support boot from ISO for
installing the operating system on a SAN along with the virtual I/O identity deployment. However, if an
operating system is already installed on the SAN, after deployment of virtual I/O identities, the server
can boot from the SAN.
• For the PowerEdge FC430, FC630, and FC830 sleds, Fiber channel (FC) cards are supported only in
the shared PCI slots of the PowerEdge FX2s chassis. Stateless deployment from OpenManage
Essentials is not supported on these FC cards. OpenManage Essentials supports stateless deployment
only for the on-board Network Daughter Cards (NDCs) for these sleds.
• OpenManage Essentials version 2.1 does not support stateless deployment on Emulex CNA cards.
• For performing stateless deployment on blade servers, the FlexAddress mode must be disabled on the
blade server to prevent the host chassis from assigning I/O identity attributes. Even if the FlexAddress
mode is enabled, OpenManage Essentials overrides the FlexAddress mode.
• While performing a stateless deployment on a server with a QLogic Converged Network Adapter,
OpenManage Essentials generates different attribute values for the virtual MAC (vMAC) and virtual FIP
(vFIP) MAC attributes. However, only the value of the vMAC attribute is deployed for both the vMAC
and vFIP MAC attributes. If you create a zone for SAN boot before the deployment, ensure that the
zone is created based on the vMAC address generating virtual WWPN (vWWPN) and virtual WWNN
(vWWNN). For example, 20:00:vMAC for vWWNN and 20:01:vMAC for vWWPN.
• Intel NIC cards do not support unique iSCSI initiator name for each port. OpenManage Essentials
deploys the same IQN value for all ports in the Intel NIC card.
Related Tasks
Setting Up Device Configuration Auto Deployment (Stateless Deployment)
Deploying a Device Configuration Template (Stateless Deployment)
Additional Information
The following Dell technical white papers and files available at delltechcenter.com provide additional
information on the device configuration template, attributes, and work flows:
• Server Cloning with Server Configuration Profiles
• Server Configuration XML File
• Configuration XML Workflows
• Configuration XML Workflow Scripts
168