HP Integrity BL870c i2 Server-Blade - Manual (Page 109)

Configuring the Virtual Connect domain using the CLI 109
• If PXE, controller boot order, or SAN boot settings are made outside of Virtual Connect (using RBSU
or other configuration tools), Virtual Connect will restore the settings defined by the server profile
after the server blade completes the next boot cycle.
• To boot properly from SAN when using Linux and VMware ESX 3.0.1 and ESX 3.0.2, change the
QLogic QMH2462 4Gb FC HBA connection option to 'point-to-point only' in the QLogic BIOS
configuration utility. The Emulex LPe 1105-HP 4Gb FC HBA does not require using the 'point-to-point'
connection option to boot properly from SAN.
Server profiles are associated with a specific enclosure device bay. After a profile is assigned, the Virtual
Connect Manager configures the server blade in that device bay with the appropriate
MAC/PXE/WWN/SAN boot settings and connects the appropriate networks and fabrics. Server blades
that have been assigned a profile and remain in the same device bay do not require further Virtual
Connect Manager configuration during a server or enclosure power cycle. They will boot and gain access
to the network and fabric when the server and interconnect modules are ready.
If a server blade is inserted into a device bay already assigned a server profile, Virtual Connect Manager
automatically updates the configuration of that server blade before it is allowed to power up and connect
to the network.
If a server blade is moved from a Virtual Connect managed enclosure to a non-Virtual Connect enclosure,
local MAC addresses and WWNs are automatically returned to the original factory defaults. This feature
prevents duplicate MAC addresses and WWNs from appearing in the data center because of a server
blade redeployment.
IMPORTANT: Before assigning a profile, unassigning a profile, or modifying a profile, be
sure to review the "Server blade power on and power off guidelines."
Creating server profiles
To create a new server profile, use the add profile command:
>add profile MyProfile
After an enclosure is imported into a Virtual Connect domain, server blades that have not been assigned
a server profile are isolated from all networks to ensure that only properly configured server blades are
attached to data center networks.
A server profile can be assigned and defined for each device bay so that the server blade can be
powered on and connected to a deployment network. These profiles can then later be modified or
replaced by another server profile.
A server profile can also be assigned to an empty bay to allow deployment at a later date.
Adding enet-network connections to a profile
To add a new Ethernet network connection to an existing server profile, use the add enet-connection
command:
>add enet-connection MyProfile network=MyNetwork pxe=enabled
To add a multiple network Ethernet connection on a server port, use the following commands:
>add enet-connection MyProfile pxe=enabled
>add server-port-map MyProfile:1 MyNetwork VlanID=100
If the domain setting for SharedServerVlanID is set to true, then the VlanID property cannot be
modified. Instead, the name of the shared uplink set with which the network is associated is required.