Server Profiles > Server Profiles screen details |  | next

# Server Profiles screen details

If no resources are listed, you must add a resource. See Create and apply a server profile.

The Server Profiles master pane lists all the server profiles you have defined.

- General

- Firmware

- Connections

- Local storage

- SAN Storage

- Boot Settings

- BIOS Settings

- Advanced

- Edit local storage

- Add or edit SAN volume

- Add SAN storage path

- Edit SAN storage targets

## General

Screen component | Description
--- | ---
Description | Description of the server profile that enables you to easily identify it.
Server profile template | The server profile template associated with the server profile. The server profile is checked for compliance with the server profile template.
Consistency state | The consistency state of the server profile with associated server profile template.
Server hardware | Specifies the intended target of the server profile you create.
`unassigned` | An unassigned server profile is one that is not assigned to an enclosure bay, but that you can use to set all other server provisioning aspects. When you select `unassigned`, you must specify the Server hardware type and Enclosure group (for server blades). See Capturing best-practice configurations for information on capturing best-practice configurations.
Enclosure and enclosure bay | When you select an enclosure and enclosure bay, the appliance automatically determines the appropriate profile settings based on the server hardware detected in that enclosure bay. The server hardware physical UUID appears next to the server hardware label.
IP address | When you select an IP address, you are selecting a DL server hardware. The Server hardware type is automatically determined. Enclosure group does not apply to this type of server. You can choose the firmware and BIOS settings for DL servers.
Server hardware type | Identifies the server hardware provisioned by the server profile. The server hardware type determines the provisioning settings available in the profile, such as the BIOS settings. You can change a server hardware type to migrate an existing server profile to another server with different adapters, different generations of hardware, and different server blade models.
Enclosure group | Defines the enclosure group used to configure the enclosure. The enclosure group provides the interconnect information to determine the available networks. You can change the enclosure group to move an existing server profile to a different enclosure while still supporting different adapters, different generations of hardware, and different server blade models.
Affinity | Controls server profile remove-and-replace behavior for server blades. If you apply a server profile to a server blade and the server is subsequently removed from the device bay, the Affinity setting controls whether the server profile is reapplied when you insert a server blade into the empty bay. Server profiles for rack servers do not have affinity.
Device bay | The server profile assigned to the device bay is applied to any server blade you insert into the bay, provided the server hardware type of the inserted server blade matches the server hardware type specified in the server profile.
Device bay + server hardware | The server profile assigned to the device bay is not applied if you insert a different server into the bay. The serial number and server hardware type of the inserted server blade must match the values in the server profile.
Default value: | `Device bay`
Server power | Specifies whether the server hardware is powered on or off.
Serial number | Virtual or user-defined serial number of the server hardware.
UUID | Virtual or user-defined UUID of the server hardware.
iSCSI initiator name | Virtual or user-defined name of the iSCSI initiator.

## Firmware

Screen component | Description
--- | ---
- Firmware baseline | Firmware bundles like a Service Pack for ProLiant (SPP) enable you to update firmware, drivers, utilities, and the hardware configuration for enclosures, enclosure groups, and interconnects. An SPP update contains firmware, drivers, and utilities delivered as a single PXE-bootable image. You can upload and install these firmware bundle updates in a repository to simplify maintaining baseline configurations across devices. The SPP you select as the starting point from which to compare the application of all subsequent SPPs is your firmware baseline. You can use the server profile to assign firmware levels to managed devices or you can choose the `managed manually` option to manage the firmware manually. The choices for installing an SPP are: Firmware and Operating System (OS) Drivers using Smart Update Tools—Updates the firmware and OS drivers without powering off the server hardware. Firmware only using Smart Update Tools—Updates the firmware without powering off the server hardware. Firmware only—Manages the firmware through HPE OneView. Selecting this option requires powering off.
  | NOTE: If a Service Pack for ProLiant (SPP) equal to or greater than version 2016.06 is selected as the firmware baseline when the option Firmware only is selected, the firmware update occurs through the SPP boot environment instead of Intelligent Provisioning.
See HPE Smart Update Tools for additional information.
| NOTE: If you select an HPE ProLiant Gen8 or newer model server and there is no firmware baseline installed on the appliance, a message is displayed with a link for adding a new firmware baseline.
To install an older firmware version than the version contained in the SPP, you must select the Force installation option to downgrade the firmware. You might want to install older firmware if the newer firmware is known to cause a problem in your environment, as noted in the Release Notes.
| CAUTION: Forcing a firmware downgrade might leave the server unstable.
The firmware is updated when you click create or edit to apply the server profile. When a firmware baseline associated with a server profile is deleted from the firmware repository, an indicator is placed next to the firmware baseline attribute to note that the server profile is in a degraded state. To resolve this issue, edit the server profile and update the firmware baseline to a valid firmware baseline or choose the `managed manually` option. See the Firmware bundles help for information about adding and managing firmware bundles on the appliance.
Default value: | `Managed manually`. Not managed by HPE OneView.
| NOTE: The affected components are not displayed, if the firmware baseline is `Managed manually`. for unassigned server profiles. for server profile templates.
Firmware install state | Displays the most recent firmware installation state. An alert or error message displays for all states that require your intervention. For example, if the state is StagedFailed, an alert or error message displays in HPE OneView that directs you to a resolution for the failure. The following is a list of possible actions: Pending — Action is in the queue to be performed Stage — Determines which components to be applied on the server hardware and copies those components to a stage directory. Staging — Firmware and driver components currently being copied to a stage directory Staged — Firmware and driver components successfully copied to a stage directory Stage Failed — Firmware and Driver components could not be successfully copied to a stage directory Install — Deploys components that have been staged. Installing — Firmware and driver currently being deployed on the server hardware Installed — Firmware and drivers were successfully deployed on the server hardware Install Failed — Firmware and driver deploy on the server hardware was not successful Installed Pending Reboot — Firmware and driver deploy on the server hardware was successful but a reboot is required to complete the action Activate — Reboots server hardware if a reboot is required to make the installed components usable. Activating — Server reboot is underway Activated — Server hardware successfully rebooted and component installation is successfully completed Activate Failed — Server hardware reboot was unable to complete firmware and driver installation Unknown — Components Smart Update Tools is monitoring only. This field does not display if you choose to manage the firmware manually.
Installation Method | Displays the most recent installation method used by Smart Update Tools. This field does not display if you choose to manage the firmware manually.

## Connections

Setting network connections via a server profile is supported for ProLiant server blades but is not supported for rack mount servers.

### Overview

Screen component | Description
--- | ---
ID | Identifier of the connection.
Name | Optional label for a connection. This can be configured in a server profile template or specified within the connection of a server profile.
Network | The Ethernet network, network set, Fibre Channel, FCoE, or iSCSI network for this connection. An Ethernet network or network set can be accessed by an Ethernet device; a Fibre Channel network can be accessed by a Fibre Channel device. Networks are filtered to both Fibre Channel and FCoE when Type is set to Fibre Channel. Networks are filtered to both Fibre Channel and FCoE when Type is set to Fibre Channel.
| NOTE: Network sets are not allowed on an iSCSI connection.
Typically, you assign each connection in a server profile template to a single network. Network sets enable you to select multiple networks for a single connection defined in a server profile template. Network sets are useful with hypervisors, where server profile templates need the ability to define multiple networks. For server profile templates, duplicate networks are not allowed on the same port. This also applies to networks that belong to a network set. For example, if `Network_A` is part of `NetworkSet_A`, both cannot be assigned to FlexibleLOM 1.
- Port | You can place a connection on: A specific FlexNIC
  | NOTE: In an active/active configuration, you must specify the FlexNIC on the interconnect where the uplink ports correspond to one or more networks in the connection. Traffic will pass if the connection is assigned to a port that is not connected to the interconnect; however, this is not a true active/active configuration and does not provide the desired functionality.
- Any FlexNIC of a specific adapter port An automatically selected FlexNIC
  | NOTE: In an active/active configuration, Hewlett Packard Enterprise does not recommend using this option.
You specify FlexNICs by adapter, physical port number, and FlexNIC identifier. Adapter identifiers include `LOM`, `FlexibleLOM 1`, `FlexibleLOM 2`, `Mezzanine 1`, `Mezzanine 2`, and `Mezzanine 3`. FlexNIC identifiers are `a`, `b`, `c`, and `d`. For example, selecting `Mezzanine 1:2-c` configures the connection on the third FlexNIC (c) on the second physical port of the adapter in Mezzanine slot 1. Some physical ports are identified by adapter, physical port number, and the suffix `(Auto)`. For example, selecting `FlexibleLOM 1:1 (Auto)` places the connection on the first available FlexNIC on the first physical port of the first FlexibleLOM. These connections are assigned in order of connection ID. If both connection 5 and connection 8 specify `FlexibleLOM 2:1 (Auto)`, and no other connections are assigned to `FlexibleLOM 2`, connection 5 is assigned to the first FlexNIC, and connection 8 is assigned to the second FlexNIC. Selecting `Auto` assigns the connection to a FlexNIC in a predetermined order. Connections with `Auto` specified are assigned (in connection ID order) to FlexNICs after connections with specific FlexNICs or ports are assigned. All Fibre Channel connections are assigned to FlexNICs before Ethernet connections are assigned. `Auto` connections are assigned according to function type in the following order: Fibre Channel iSCSI Ethernet (with PXE) Ethernet (without PXE) In general, you must assign a connection to the first FlexNIC on every physical port before a connection is assigned automatically to the second, third, or fourth FlexNIC of any port. The order of physical ports on HPE ProLiant Gen8 server blades is `FlexibleLOM 1:1`, `FlexibleLOM 1:2`, `FlexibleLOM 2:1`, `FlexibleLOM 2:2`, `Mezzanine 1:1`, `Mezzanine 1:2`, and so on. For HPE ProLiant G7 server blades, the FlexibleLOM entries are replaced with `LOM:1`, `LOM:2`, `LOM:3`, and `LOM:4`. Exceptions include the following: If the predetermined order causes a connection to be configured on the same physical port as another connection with the same network, the FlexNIC is skipped. If a FlexFabric converged network adapter (CNA) is connected to a Virtual Connect FlexFabric module, an Ethernet connection is not assigned to the FCoE-capable FlexNIC unless all other FlexNICs on the port are used. Before you assign a connection to a FlexNIC, the following conditions must be met: You cannot configure a network on more than one FlexNIC of a single physical port. This includes networks in a network set. The number of networks you configure on a single physical port cannot exceed 162. The sum of the requested bandwidth values cannot exceed the capacity of the port, which is determined by the adapter. In general, connections with an `Auto` FlexNIC setting are assigned to FlexNICs in a predetermined order; however, this can result in the required conditions not being met. In these cases, selecting specific FlexNICs or specific adapter ports enables you to specify a valid configuration.
Boot | You can select a connection as a primary or secondary boot device. A template can contain bootable Ethernet, Fibre Channel, and iSCSI connections. Ethernet: `Not bootable`, `PXE primary`, or `PXE secondary` Fibre Channel: `Not bootable`, `FC primary`, or `FC secondary` iSCSI: `Not bootable`, `iSCSI primary`, or `iSCSI secondary`
Connection details | The fields available depend on the connection type and boot settings.
Interconnect | Link to the interconnect of the connection.
Type | Specifies the network technology: `Ethernet`, `Fibre Channel` or `iSCSI`.
WWNN | The World Wide Node Name of the boot target.
WWPN | The World Wide Port Name of the boot target.
MAC address | MAC address of the boot target.
Requested bandwidth | The requested bandwidth for the connection.
Allocated bandwidth | The bandwidth allocated for the connection.
Max bandwidth | The maximum bandwidth setting for the connection
Initiator name | The name of the iSCSI initiator.
Initiator IP address | IPv4 address of the iSCSI initiator.
Initiator subnet mask | Subnet mask of the iSCSI initiator.
Initiator gateway | Subnet gateway of the iSCSI initiator.
Boot target | Name of the boot target. On an HPE 3PAR Storage System, this is the same as the Initiator name. On an HPE StoreVirtual Storage System, this is uniquely generated for each volume you create on the storage system.
Boot LUN | Storage LUN (logical unit number) from the storage array. On an HPE 3PAR Storage System, the LUN is a uniquely increasing value for each volume exported to a server. On an HPE StoreVirtual Storage System, the LUN is 0.
| NOTE: It is possible and supported that an OS can have duplicate LUNs that are coming from different HPE 3PAR and HPE StoreVirtual appliances.
Target IP address | Target IPv4 address of the iSCSI storage system.
Second IP address | The second IP address of the iSCSI storage system.
CHAP name | The challenge handshake authentication protocol (CHAP) name.
Mutual CHAP name | The mutual challenge handshake authentication protocol (MCHAP) name.
Add connection button | Click the Add connection button to add or edit the network connections you want this server profile to apply to the target server hardware.

### Add Connection

- General

- iSCSI Initiator

- Boot Target

- iSCSI Authentication

#### General

Screen component | Description
--- | ---
Name | Optional label for a server profile connection. This label and the server profile name are used internally to construct an initiator alias on Fibre Channel connections for SAN storage zoning. Copying the server profile clears the alias on the copy (new) server profile.
Function type | Specifies the network technology: `Ethernet`, `Fibre Channel` or `iSCSI`. When configuring an FCoE network connection in a server profile template, select Fibre Channel. FCoE networks are annotated in create, edit, and details views.
Default value: | `Ethernet`
Network | The Ethernet network, network set, Fibre Channel, FCoE, or iSCSI network for this connection. An Ethernet network or network set can be accessed by an Ethernet device; a Fibre Channel network can be accessed by a Fibre Channel device. Networks are filtered to both Fibre Channel and FCoE when Type is set to Fibre Channel. Networks are filtered to both Fibre Channel and FCoE when Type is set to Fibre Channel.
| NOTE: Network sets are not allowed on an iSCSI connection.
Typically, you assign each connection in a profile to a single network. Network sets enable you to select multiple networks for a single connection in a profile. Network sets are useful with hypervisors, where profile connections need the ability to carry multiple networks. Duplicate networks are not allowed on the same physical port. This also applies to networks that belong to a network set. For example, if `Network_A` is part of `NetworkSet_A`, both cannot be assigned to FlexibleLOM 1.
| NOTE: This constraint is enforced for unassigned server profiles when you attempt to assign the profile to server hardware. Assign duplicate VLANs on different physical ports (LOMs). Create or edit the connections to specify different networks or assign them to different physical ports.
- Port | You can place a connection on: A specific FlexNIC
  | NOTE: In an active/active configuration, you must specify the FlexNIC on the interconnect where the uplink ports correspond to one or more networks in the connection. Traffic will pass if the connection is assigned to a port that is not connected to the interconnect; however, this is not a true active/active configuration and does not provide the desired functionality.
- Any FlexNIC of a specific adapter port An automatically selected FlexNIC
  | NOTE: In an active/active configuration, Hewlett Packard Enterprise does not recommend using this option.
To prevent configuration of the connection on the server, select `None`. You specify FlexNICs by adapter, physical port number, and FlexNIC identifier. Adapter identifiers include `LOM`, `FlexibleLOM 1`, `FlexibleLOM 2`, `Mezzanine 1`, `Mezzanine 2`, and `Mezzanine 3`. FlexNIC identifiers are `a`, `b`, `c`, and `d` (or more depending on the VC version and adapter type). For example, selecting `Mezzanine 1:2-c` configures the connection on the third FlexNIC (c) on the second physical port of the adapter in Mezzanine slot 1. Some physical ports are identified by adapter, physical port number, and the suffix `(Auto)`. For example, selecting `FlexibleLOM 1:1 (Auto)` places the connection on the first available FlexNIC on the first physical port of the first FlexibleLOM. These connections are assigned in order of connection ID. If both connection 5 and connection 8 specify `FlexibleLOM 2:1 (Auto)`, and no other connections are assigned to `FlexibleLOM 2`, connection 5 is assigned to the first FlexNIC, and connection 8 is assigned to the second FlexNIC. Selecting `Auto` assigns the connection to a FlexNIC in a predetermined order. Connections with `Auto` specified are assigned (in connection ID order) to FlexNICs after connections with specific FlexNICs or ports are assigned. All Fibre Channel connections are assigned to FlexNICs before Ethernet connections are assigned. In general, you must assign a connection to the first FlexNIC on every physical port before a connection is assigned automatically to the second, third, or fourth FlexNIC of any port.The order of physical ports on HPE ProLiant Gen8 server blades is `FlexibleLOM 1:1`, `FlexibleLOM 1:2`, `FlexibleLOM 2:1`, `FlexibleLOM 2:2`, `Mezzanine 1:1`, `Mezzanine 1:2`, and so on. For HPE ProLiant G7 server blades, the FlexibleLOM entries are replaced with `LOM:1`, `LOM:2`, `LOM:3`, and `LOM:4`. Exceptions include the following: If the predetermined order causes a connection to be configured on the same physical port as another connection with the same network, the FlexNIC is skipped. If a FlexFabric converged network adapter (CNA) is connected to a Virtual Connect FlexFabric module, an Ethernet connection is not assigned to the FCoE-capable FlexNIC unless all other FlexNICs on the port are used. Before you assign a connection to a FlexNIC, the following conditions must be met: You cannot configure a network on more than one FlexNIC of a single physical port. This includes networks in a network set. The number of networks you configure on a single physical port cannot exceed 162. The sum of the requested bandwidth values cannot exceed the capacity of the port. In general, connections with a port selection of `Auto` will be assigned a FlexNIC in a predetermined order. If connections are associated with network sets, this can result in automatic assignments where at least one network in the network set is not available on the FlexNIC selected by HPE OneView. If this happens, an error message will be displayed. To resolve this error, the connection associated with the network set must have its port manually selected.
Requested bandwidth (Gb/s) | When you select a network, the appliance automatically populates this box with the preferred bandwidth. This field lets you specify the bandwidth for the connection. You can specify a bandwidth value between 100 Mb/s and the maximum bandwidth of the selected network, in 100 Mb/s increments. The sum of the requested bandwidth values for all connections configured on a physical port cannot exceed the capacity of the port. For Virtual Connect Fibre Channel connections, the available discrete values are based on the adapter and the Fibre Channel interconnect module. With Fibre Channel connections on FlexFabric adapters, you can select from a full range of speeds. However, if you change the HBA adapter speed via the BIOS setting, and then set the Requested bandwidth setting for a server profile connection to a noncompatible value, the link will not be established.
| NOTE: A discrepancy can exist between the Allocated Bandwidth of the server profile and what the server OS detects as the link speed for the connection network interface. You can take advantage of the unused bandwidth when the allocated bandwidth for a profile connection is set lower than the maximum bandwidth defined for the network or network set assigned to that connection. The server OS detects the maximum bandwidth only; the Server Profiles screen displays requested, allocated, and maximum bandwidth.
- Boot | You can select a connection as not bootable, or as a primary or secondary boot device. Ethernet: `Not bootable`, `PXE primary`, or `PXE secondary`
  | NOTE: If you select `iSCSI primary` or `iSCSI secondary`, you must also select `UEFI` or `UEFI optimized` as the boot mode in the Boot Settings pane.
Fibre Channel: `Not bootable`, `FC primary`, or `FC secondary` iSCSI: `Not bootable`, `iSCSI primary`, or `iSCSI secondary`
Use user-specified IDs | Select to enables or disable the use of user-specified IDs.
Boot from (Fibre Channel) | Select a boot target option:
`Managed volume` | Specify the boot volume by setting the boot attribute on a volume in the SAN Storage section of the server profile.
`Specify boot target` | Specify the WWPN and LUN of the boot target.
`Use Adapter BIOS` | Select to enable the BIOS on the server hardware to specify the boot target.
MAC address | MAC address of the connection.
WWPN (Fibre Channel) | WWPN (World Wide Port Name) of the connection.
WWNN (Fiber Channel) | WWNN (World Wide Node Name) of the connection.
LUN | Storage LUN (logical unit number) from the storage array.
Add connection button | Click the Add connection button to add or edit the network connections you want this server profile to apply to the target server hardware.

#### iSCSI Initiator

Screen component | Description
--- | ---
iSCSI initiator name | Select a naming option:
`Profile initiator name` | Use the initiator name defined in the Advanced section of the server profile.
`User specified` | Specify the initiator name.
Subnet mask | Specify the subnet mask of the iSCSI initiator.
Gateway | Specify the gateway mask of the iSCSI initiator.

#### Boot Target

Screen component | Description
--- | ---
Target IP address | Target IPv4 address of the boot target.
Target port | Default is 3260.
Second IP address | Second IPv4 address of the boot target. The second IPv4 address is used if the storage has redundant connections.
Second port | Default is 3260.

#### iSCSI Authentication

iSCSI initiators and targets prove their identity to each other using a challenge handshake authentication protocol (CHAP) to protect against unauthorized systems from accessing the data volumes.

Some storage systems use only one name for both the CHAP and mutual CHAP (MCHAP) name, in which case enter that name for both the CHAP and MCHAP name in HPE OneView.

Screen component | Description
--- | ---
CHAP level | Select an iSCSI authentication option:
`None` | No authentication
`CHAP` | With this level of security, only the target authenticates the initiator.
`Mutual CHAP` | With this level of security, the target and the initiator authenticate each other. A separate secret is set for each target and for each initiator in the storage area network (SAN).
CHAP name (Target name) | The iSCSI target username to use when the target (storage system) authenticates the initiator (server). A valid name is 1–223 visible (letter, digit and punctuation) characters.
CHAP secret (Target secret) | The iSCSI target secret (password) to use when the target (storage system) authenticates the initiator (server). A valid secret is either 12–16 printable (letter, digit, punctuation, and space) characters with no `0x` prefix, or `0x` followed by 24–32 hexadecimal (`0-9`, `a-f`, and `A-F`) characters. A hexadecimal secret is only valid with the iSCSI function type.
Mutual CHAP name (Initiator name) | The iSCSI initiator username to use when the initiator (server) authenticates the target (storage system). A valid name is 1–223 visible (letter, digit and punctuation) characters.
Mutual CHAP secret (Initiator secret) | The iSCSI initiator secret (password) to use when the initiator (server) authenticates the target (storage system). This secret should be different than the CHAP secret. A valid secret is either 12–16 printable (letter, digit, punctuation, and space) characters with no `0x` prefix, or `0x` followed by 24–32 hexadecimal (`0-9`, `a-f`, and `A-F`) characters. A hexadecimal secret is only valid with the iSCSI function type.

## Local storage

Setting local storage via a server profile or server profile template is supported for most server hardware.

| NOTE: If the appliance has Service Pack for Proliant (SPP) greater than or equal to version 2016.06, local storage setting updates occur through the SPP boot environment instead of Intelligent Provisioning.

### Integrated storage controller

##### Integrated storage controller mode

The method the integrated storage controller uses to configure physical drives.

Can be `managed manually`, `RAID`, or `HBA`.

Controller will be re-initialized on next profile application | This displays when you select for the integrated storage controller to be re-initialized the next time the server profile is applied.
Logical drive details | Displays the details of the logical drives on the controller.

### Logical drive details

Displays the logical drive details for integrated storage controllers.

Status icon | The icon shows the status of the logical drive.
Name | The name of the logical drive.
Logical drive (RAID mode) | The number assigned to the logical drive. The logical drive number is automatically assigned when the logical drive is created on the target server hardware. A logical drive that has not yet been created displays `pending`.
RAID level (RAID mode) | The RAID level for the logical drive. Examples: `RAID 0`, `RAID 1`, `RAID 10`, `RAID 1 ADM`, `RAID 6`
Number of drives | Number of physical drives in the logical drive . When in RAID mode, only values that meet the constraints of the RAID level are available.
Drive Technology | The type of drive technology. Can be `SAS HDD`, `SATA HDD`, `SAS SSD`, `SATA SSD`, or `Not specified` (integrated controller only).
Boot (RAID mode) | Whether or not (`Yes` or `No`) the logical drive is set to boot in RAID mode.
X icon | Click to delete the logical drive. The logical drive is deleted immediately.

## SAN Storage

Setting SAN storage via a server profile or server profile template is supported for ProLiant server blades but is not supported for rack mount servers.

Associating a server profile or a server profile template with a volume gives the server hardware to which the server profile is assigned access to storage space on a SAN storage system.

Screen component | Description
--- | ---
Manage SAN Storage | By default, SAN storage is not associated. Selecting this check box allows access to SAN storage.
Host OS type | Select a host OS type.
Default value: | `Windows 2012`
Volume attachments |
Volume Name | Unique name of the storage volume
Permanent | Identifies whether the volume is permanent. If a server profile is deleted that has an attached volume marked as permanent, only the profile is deleted and not the volume. Volumes not marked as permanent are deleted when the profile is deleted or when the nonpermanent volume is removed or detached from the profile.
LUN | Logical unit number, which points to storage in a SAN
Pool | Storage pool to which the storage volume belongs
Size | Provisioned capacity of the storage volume, in GiB
Provisioning | Provisioning setting of the storage volume: `Thin` or `Full`
Sharing | Sharing setting: `Shared` or `Private`
Boot | Whether or not the volume is set as a boot volume. Displays `n/a` if the volume is not bootable.
Connection ID | Connection ID of the storage path.
Network | SAN network to which the storage system port is connected
Server Initiator | Port on the physical server that sends SCSI commands to the storage system
Storage Targets | Ports on the storage system that receive the SCSI commands sent by the server initiator
Enabled | Check box to enable or disable the path to the storage volume
Add Volume button | Displays the Add Volume dialog box

## Boot Settings

By default, server boot behavior is controlled by the server profile or server profile template. The server hardware type determines the available options in the server profile or server profile template.

HPE ProLiant Gen9 servers support both legacy BIOS and UEFI for configuring the boot process while HPE ProLiant Gen8 are legacy BIOS mode servers only. See the appropriate support or compatibility matrix on the Hewlett Packard Enterprise Information Library for a complete list of supported servers.

Screen component | Description
--- | ---
Manage boot mode (Gen9 servers only) | Enable this option to manage the boot mode and PXE boot policy, if applicable. If Manage boot mode is disabled, HPE OneView will not change the PXE boot mode or PXE boot policy.
Boot mode | Sets the boot mode to one of the following: `UEFI` `UEFI optimized` `Legacy BIOS` If `UEFI` or `UEFI optimized` is selected, the PXE boot policy can also be specified. Additionally, the option to manage the boot order is also available if the selected server hardware is an HPE ProLiant Gen9 BL server blade. Boot order management is not available for HPE ProLiant Gen9 DL rack servers. For the `UEFI` or `UEFI optimized` boot mode options, the boot mode choice is based on the expected OS and required boot features for the server hardware. `UEFI optimized` boot mode reduces the time the system spends in POST. To select the appropriate boot mode, consider the following: If a secure boot is required, the boot mode must be set to `UEFI` or `UEFI optimized`. For operating systems that do not support UEFI (such as DOS, or older versions of Windows and Linux), the boot mode must be set to `Legacy BIOS`. When booting Windows 7, Server 2008, or 2008 R2 using UEFI, do not select `UEFI optimized`.
PXE boot policy | Controls the ordering of the network modes available to the Flexible LOM (FLB). Select from the following policies: `Auto` `IPv4 only` `IPv6 only` `IPv4 then IPv6` `IPv6 then IPv4` Setting the policy to `Auto` will configure the server hardware to use the BIOS-defined PXE boot policy.
Manage boot order | Enable this option to specify the order in which devices will be presented as boot targets. If you disable Manage boot order, the BIOS determines the server boot order on the selected server hardware.
| NOTE: On Gen9 BL servers, the Manage boot order option is available only if the Manage boot mode option is enabled. When the server hardware boots and the first device specified is unavailable, the server attempts to boot from the second device, and so on. To provide redundant paths, primary and secondary sources can be defined when booting via Ethernet or SAN connections. PXE and Hard disk selections do not control SD placement in the boot order. Boot targets can change based on the server hardware.
For Gen8 and earlier servers or Gen9 servers in Legacy BIOS boot mode: You can drag and drop targets, or edit them to change the boot order: CD Floppy (G7 and Gen8 only) USB Hard disk PXE For Gen9 BL server blades in UEFI or UEFI optimized boot mode:
Primary boot device | This setting is available when Manage boot order is enabled. Select one of the following settings: Hard disk PXE

## BIOS Settings

You manage BIOS settings through the server profile. When you enable the Manage BIOS option, all default settings are applied, and whatever explicit overrides you specify. BIOS settings can be edited only when the server hardware is powered off.

By selecting to manage BIOS settings, can view all settings, only those you have modified, or only those that are different than the default values. The BIOS settings displayed depend on the supported server hardware.

| NOTE: Some BIOS settings might not be available in the target server depending on its hardware configuration and system ROM version. Consult the HPE ROM-Based Setup Utility User Guide for additional details on hardware-specific settings. To obtain a copy from the HPE Support Center. Go to http://www.hpe.com/support/hpesc. In the Search HPE Support Center search box at the top of the home page screen, enter `HPE ROM-based Setup Utility User Guide`.

Screen component | Description
--- | ---
Manage BIOS | By default, BIOS settings are not managed through a server profile; however, selecting this check box enables you to do so on server hardware that supports these options.
| NOTE: When you are creating or editing a profile, the Manage BIOS check box is disabled if the appliance cannot manage these settings for the target server hardware (for example, when the target server hardware is an older hardware model). See the HPE OneView Support Matrix for a complete list of supported servers.
If you keep the default setting and do not select the Manage BIOS check box, the server profile will not contain any BIOS settings and managing these settings is done through the server console interface. If you select the Manage BIOS check box, all BIOS settings are set to their appliance default settings. You can then edit or override these default settings through the server profile, based on the server hardware type associated with the profile. The settings in the server profile are applied on the server hardware when the profile is created and applied. The settings applied to the server hardware by the server profile are not cleared when Manage BIOS is deselected, the server profile is deleted, or the server profile is removed from the server hardware. HPE OneView has a set of default BIOS settings for the server hardware type. Click Edit settings to display the full set of BIOS settings, organized into categories. You can click any setting to view help text and select the desired value for the setting. Any changes to the default settings are displayed in the BIOS Settings panel. If you change a setting through another means, such as at the server console, those settings are overwritten by the settings specified in the server profile. BIOS settings supported by the server hardware but not displayed in the Edit settings screen are not overwritten. For HPE ProLiant Gen9 servers, both actual and expected configuration values are displayed. Actual settings are the current values the server is using. The expected settings are the current values defined in the server profile.
| NOTE: When you apply a Gen9 profile with setting changes, the profile screen will show the expected and actual values but they will not match until the next server boot and the Power On Self Test (POST) has completed.
Inconsistent | Displays the values where the actual value is different than the expected value.
Modified | Displays the settings that you have edited and changed from the default values for the server hardware type. Modified settings are applied when the server is powered on.
All | Displays all setting values for the server hardware type.
Edit settings button | Allows you to edit all BIOS settings.
| NOTE: If the appliance has Service Pack for ProLiant (SPP) greater than or equal to version 2016.06, local storage setting updates occur through the SPP boot environment instead of Intelligent Provisioning. Gen9 server BIOS settings are updated through the iLO RIS interface.

## Advanced

ProLiant DL rack mount server models support only physical serial numbers, MAC addresses, and WWN addresses.

Screen component | Description
--- | ---
Serial number/UUID | Enables you to associate either a virtual or physical serial number or UUID with the server. Virtual serial numbers and UUIDs are assigned by the appliance and enable flexibility. The benefit of virtual serial numbers is that when you use a virtual serial in a server profile or a server profile template and assign the profile to a server bay, any server that is inserted in that server bay uses the same serial number. Physical serial numbers are reported by the server BIOS and associate a serial number to the server. When you create an unassigned profile and set the profile to use a physical serial number or UUID, the value displays `pending assignment` until you set a server in the profile. The server profile option for serial numbers or UUIDs defaults to virtual if the global setting for virtual serial numbers is enabled. The server profile option for virtual serial numbers or UUIDs is disabled if the global setting for virtual serial numbers is disabled. For more information, see Settings: Addresses and Identifiers
MAC addresses | Enables you to specify if the server uses physical or virtual MAC addresses. Virtual MAC addresses are generated by the appliance and are used by the servers. The benefit of specifying virtual MAC addresses in a server profile is that when you assign the profile to a server, any server that is inserted in that server bay uses the same MAC addresses. Thus, a server replacement does not affect the data center interconnects because they do not detect any change in MAC address. Physical MAC addresses are reported by the server BIOS and associate a MAC address to the server. Physical MAC addresses are burned in on the server NICs. If you replace a server, the physical MAC changes and you must update the data center interconnects. When you create an unassigned profile and set the profile to use a physical address, the value displays `pending assignment` until you set a server in the profile. The server profile option for MAC addresses defaults to virtual if the global setting for virtual MAC addresses is enabled. The server profile option for virtual MAC address is disabled if the global setting for virtual MAC addressed is disabled. For more information, see Settings: Addresses and Identifiers
WWN addresses | Enables you to specify if the server uses physical or virtual World Wide Name (WWN) addresses (for Fibre Channel connections). WWN addresses are generated by the appliance and are used by the servers. The benefit of specifying virtual WWN addresses in a server profile is that when you assign the profile to a server, any server that is inserted in that server bay uses the same WWN addresses. Thus, a server replacement does not affect the data center interconnects because they do not detect any change in WWN address. Physical WWN addresses are reported by the server BIOS and associate a WWN address to the server. Physical WWN addresses are burned in on the server NICs. If you replace a server, the physical WWN changes and you must update the data center interconnects. If you create a server profile with a virtual serial number, MAC, or WWN address, you cannot change these to a physical address later. If you disable the option to enable virtual serial number, MAC, or WWN addresses in Settings→Addresses and Identifiers, you can set only their physical addresses when you create a server profile. When you create an unassigned profile and set the profile to use a physical address, the value displays `pending assignment` until you set a server in the profile. The server profile option for WWN addresses defaults to virtual if the global setting for virtual WWN addresses is enabled. The server profile option for virtual WWN address is disabled if the global setting for virtual WWN addressed is disabled. For more information, see Settings: Addresses and Identifiers
Hide unused FlexNICs | This setting allows you to hide unused FlexNICs from the operating system. If Hide Unused FlexNICs is selected (enabled), FlexNICs that do not map to any server profile connections are not presented to the operating system. For example, if the server hardware supports 8 FlexNICs, but only four connections are defined in the server profile, the operating system will see only four network interfaces. If Hide Unused FlexNICs is not selected (disabled), eight FlexNICs are enumerated in the operating system as network interfaces for each Flex-10 or FlexFabric adapter. Configuring Fibre Channel connections on a FlexFabric adapter can enumerate two storage interfaces, reducing the number of network interfaces to six. FlexNICs are hidden in pairs, starting with the fourth pair. For example, if the fourth FlexNIC on either physical port corresponds to a profile connection, all eight physical functions are enumerated. If a profile connection corresponds to the second FlexNIC on either physical port, but no connection corresponds to the third or fourth FlexNIC on either physical port, only the first and second physical functions are enumerated in the operating system. By default, Hide Unused FlexNICs is enabled. This setting can be changed only when the server is powered off.
iSCSI initiator name | Virtual or user-defined name of the iSCSI initiator.

See also

- Server Profiles

## Edit local storage

Use this dialog to enable management of local storage controllers associated with the server hardware that is assigned to the server profile, and to create and delete logical drives.

Click the to edit an integrated storage controller.

##### More information

About server profiles and local storage

### Edit integrated storage controller

##### Integrated storage controller mode

managed manually | (default) The storage controller configuration is not managed by HPE OneView.
HBA | All physical drives are presented directly to the operating system and the hardware RAID engine is disabled.
Re-initialize storage on next profile application | Selected by default. This option erases all existing logical drives the next time you apply the server profile.
RAID | The physical drives can be used to configure logical drives using the hardware RAID engine.
Re-initialize storage on next profile application | Selected by default. This option erases all existing logical drives the next time you apply the server profile.
Import existing logical drives | When selected, any existing logical drives are discovered and added to the server profile. This operation supports multiple logical drives as long as there is only one logical drive per drive array.
Logical drive details | Displays the details of the logical drives on the controller.
Create logical drive | Opens the Create logical drive dialog.

| NOTE: The boot drive selection is overwritten by the server profile even when the Import existing logical drives action is selected. To boot from a an existing logical drive, import the drive and select the desired logical drive as the boot drive when the import is complete. If you have logical drives that were created using an older version of HPE OneView, use Import existing logical drives to import them. This option enables the appliance to discover attributes that will enable you to add additional logical drives.

### Create Logical Drive

Use this dialog to create a logical drive.

##### Name

Name for the logical drive.

A maximum of 255 alphanumeric characters, spaces, and special characters with no leading spaces.

##### RAID Level

The RAID level for the logical drive.

Examples: `RAID 0`,`RAID 1`, `RAID 10`, `RAID 6`

Supported RAID levels depend on the server hardware type and on the physical server configuration. Ensure you have enough physical drives present for the selected RAID level. If you do not have enough drives to support the selected RAID level, the server profile create or edit operation will fail.

##### Number of physical drives

Number of physical drives in the logical drive.

Only values that meet the constraints of the RAID level are available.

##### Drive Technology

The type of drive technology.

Can be `SAS HDD`, `SATA HDD`, `SAS SSD`, `SATA SSD`, or `Not specified` (integrated controllers only).

Ensure the target server hardware has enough physical drives of the selected drive technology to support the selected RAID level. Otherwise, the server profile create or edit operation will fail. For more information on RAID levels, see RAID levels and number of physical drives.

You can delete a logical drive by clicking the X icon at the end of the row.

For integrated controllers, you can select a technology type, or select `Not specified`, which allows any type of drive technology to be used.

| IMPORTANT: Deleting a logical drive on a server profile that is already assigned to server hardware completely removes the logical drive configuration. The data stored on the logical drive is not erased, but becomes inaccessible.

| NOTE: Once the server profile is applied to the server hardware, the new logical drives are assigned a number. You can use the number to correlate the logical drives listed in the server profile and the HPE Smart Storage Administrator tool. Logical drives created by the server profile use the maximum available disk space. Logical drives are created on the target server hardware in the order specified in the server profile. For the integrated storage controller, each logical drive allocates physical drives matching the specified drive technology. Physical drives are allocated in order from largest to smallest.

## Add or edit SAN volume

Adding or editing volumes via a server profile is supported for ProLiant server blades, but is not supported for rack mount servers.

The properties displayed depend on whether the volume is a new or existing volume.

Screen component | Description
--- | ---
General |
Type |
`Existing volume` | Selecting `Existing volume` allows you to select one of the available private or shared volumes.
`New volume` | Selecting `New volume` allows you to create a SAN storage volume.
Name | Unique name of the storage volume If adding an existing volume, a list is displayed of volumes that are reachable from the storage system. You can search the list by entering any characters contained in the volume name.
Description | Enter a description of the volume (optional).
LUN | Identifier that enables a server host OS to identify a SAN storage volume as a distinct device The LUN can be generated automatically or manually specified.
| NOTE: To reuse a host sees configuration in HPE OneView when adding an existing 3PAR volume, you must enter the exact LUN value as configured on the 3PAR array.
`Auto` | A LUN is generated automatically when you create the server profile.
`Manual` | Specify a number between 0 and 65535.
| NOTE: Most operating systems do not accept values greater than 254 (255 for Linux).
Volume Properties (New volumes) |
Storage pool | The storage pool in which to create the volume.
Capacity | The capacity for the volume: a value between 1 GiB and 16 tebibytes (TiB).
Provisioning | The provisioning type of the volume.
`Thin` | Starts with a small set of block storage that expands to fill the volume as the space is consumed.
`Full` | The volume consumes the full capacity when you create it.
Sharing | The sharing for the volume.
`Private` | The volume can be used by only one server profile. Can be used to boot from SAN.
`Shared` | The volume can be used by more than one server profile.
Permanent | Enables the volume to be set as permanent. A permanent volume is not deleted when the server profile is deleted. A nonpermanent volume is tied to the server profile and is deleted when the server profile is deleted.
Storage Paths (Existing volumes) |
Connection ID | Connection ID of the storage path. The ID corresponds to the ID in the Connections section of the server profile. Storage paths are added in connection ID order.
Network | SAN network to which the storage system port is connected.
Server Initiator | Fibre Channel port on the physical server that initiates SCSI commands to the storage system.
Storage Targets | Fibre Channel port on the storage system that processes SCSI commands sent by the server initiator. Storage targets are created automatically or you can select from available target ports.
Default value: | `Auto`
Enabled | Enables or disables the storage path.
X | Clicking the X icon removes the storage path from the server profile.
Add storage path button | Adds a storage path, if available. You access the button from when editing a volume attachment.
Remove all button | Removes all storage paths from the server profile. You access the button from when editing a volume attachment.

## Add SAN storage path

Adding a storage path via a server profile is supported for ProLiant server blades, but is not supported for rack mount servers.

Screen component | Description
--- | ---
Search box | Filters the list of storage paths to display only storage paths with names that contain the characters you enter in the box.
Connection ID | Connection ID of the storage path.
Network | SAN network to which the storage system port is connected.

## Edit SAN storage targets

Screen component | Description
--- | ---
Auto | Storage targets are assigned automatically. (Default)
Select target ports | Allows manual assignment of target ports. By selecting this option, world wide port name (WWPN), port name, and port group are displayed. Manual target selection is supported for Fabric-attach paths only, not Direct-attach paths. You can select one or more target ports which can belong to different port groups.
Selected | Check box to enable or disable the target port.
Target Port | The WWPN assigned to the target port in a fabric.
Target Port Name | The name of the port for which information is displayed.
Port Group | The port group assigned via the storage system.

See also

- About server profiles

- Create and apply a server profile

- Copy a server profile

- Edit a server profile

- Move a server profile to another server

- Activity screen details

- Map view screen details

- Labels screen details

- Server Profiles

prev | up | next
When to use a server profile | home | Server Profiles status icon definitions

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP