Server Profile Templates > Server Profile Templates screen details |  | next

# Server Profile Templates screen details

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

The Server Profile Templates master pane lists all of the server profile templates that you have defined.

- General

- Firmware

- Connections

- Local storage

- SAN Storage

- Boot Settings

- BIOS Settings

- Advanced

- Add or edit SAN volume

- Add SAN storage path

- Edit SAN storage targets

## General

#### Description

Description of the server profile template that enables you to easily identify it.

#### Server profile description

Description of the server profile associated with the server profile template.

#### Server hardware type

Identifies the server hardware provisioned. The server hardware type determines the provisioning settings available, such as the BIOS settings.

#### Enclosure group

Defines the enclosure group used to configure the enclosure. The enclosure group provides the interconnect information you need to determine the available networks.

#### Affinity

Controls 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. 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.
Device bay + server hardware | The server profile assigned to the device bay is not applied if you insert a server into the bay and it does not match the serial number and server hardware type listed in the server profile.

Default value: | `Device bay`

#### Connections

The number of connections specified in the server profile template

#### SAN volume attachments

The number of SAN volume attachments specified in the server profile template

#### Logical drives

The number of logical drives specified in the server profile template

#### Logical JBODs

The number of logical JBODs with no associated logical drive specified in the server profile template.

#### Firmware baseline

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 template 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.

  Default value: | `Managed manually`. Not managed by HPE OneView.

See HPE Smart Update Tools for additional information.

#### BIOS

The BIOS setting for the server profile template.

`managed manually` | The BIOS is not managed by HPE OneView.
`Manage BIOS` | If HPE OneView is managing the BIOS, this field displays the number of BIOS settings and the number of settings that you have modified.

## Firmware

Screen component | Description
--- | ---
Firmware baseline | Firmware bundles like a Service Pack for ProLiant (SPP) enable you to systematically update firmware, drivers, utilities, and the hardware configuration for enclosures, enclosure groups, and interconnects. An SPP 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 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. For additional information, see HPE Smart Update Tools.
Default value: | `Managed manually`. Not managed by HPE OneView.
| 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, perhaps 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 template. When a firmware baseline associated with a server profile template is deleted from the firmware repository, an indicator is placed next to the firmware baseline attribute to note that the server profile template is in a degraded state. To resolve this issue, edit the server profile template and update the firmware baseline to a valid firmware baseline or choose the `managed manually` option. For information about adding and managing firmware bundles on the appliance, see Firmware bundles.
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

You can configure connections in a server profile template. Setting network connections through a server profile template 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 configured in a server profile template.
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 or FCoE 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.
| 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 the network(s) 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 connection configured in a server profile template.
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 or FCoE 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.
| 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 the network(s) 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. 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.
Requested bandwidth (Gb/s) | Specify the bandwidth for the connection. When you select a network, the appliance automatically populates this box with the preferred bandwidth. 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, which is determined by the adapter. For Virtual Connect Fibre Channel connections, the available discrete values are based on the adapter and the Fibre Channel interconnect module. With FCoE connections, you can select from a full range of speeds.
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`
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 template to apply to the profiles created from template. When the connections appear in the details pane, you can edit or delete them by clicking the appropriate link.

#### 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.

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).

## Local storage

#### Integrated storage controller mode

The mode of the integrated storage controller. See Edit local storage for more information on controller modes.

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

Controller will be re-initialized on next profile application | This displays if you have selected for the integrated storage controller to be re-initialized when it is applied to a server profile. See Edit local storage for more information on configuring server profiles for internal storage.
Logical drive details | Displays the details of the logical drives on the controller.

#### Logical drive details

Name | The name of the logical drive or SAS logical JBOD, depending on the controller mode.
Logical drive | 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 as `pending`.
RAID level | 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 or SAS logical JBOD. When in RAID mode, only values that meet the constraints of the RAID level are available.
Min GB | The minimum size in GB (gigabytes), of the physical drives allocated for the logical drive or SAS logical JBOD.
Max GB | The maximum size in GB (gigabytes), of the physical drives allocated for the logical drive or SAS logical JBOD.
Drive Technology | The type of drive technology. Can be `SAS HDD`, `SATA HDD`, `SAS SSD`, `SATA SSD`, or `Not specified` (integrated controller only).
Boot | Whether or not (`Yes` or `No`) the logical drive is set to boot.

## SAN Storage

Configuring SAN storage through a server profile template is supported for ProLiant server blades but is not supported for rack mount servers.

Associating a server profile template with a volume attaches that volume to every server profile created from the server profile template.

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 |
Type |
Existing volume | A shared volume is attached to the server profile template. All server profiles created from this server profile template will be attached to the volume.
New volume | A new private volume is created and attached to a server profile that is created from the server profile template. A new volume will not be displayed in the Volumes until a server profile is created from the server profile template.
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 non-permanent 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 | Fibre Channel port on the physical server that sends SCSI commands to the storage system.
Storage Targets | Fibre Channel port on the storage system that processes 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 template. The available options are determined by the server hardware type you select in the 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. For a complete list of supported servers, see the appropriate support or compatibility matrix on the Hewlett Packard Enterprise Information Library.

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 should be 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. In order 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, server boot order is determined by the BIOS on the selected server hardware. 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. In order 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 appliance. When you enable the Manage BIOS option, all appliance default settings are applied, in addition to whatever explicit overrides you specify.

By selecting to manage BIOS settings, you have the option to 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.

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 server profile template, the Manage BIOS check box is disabled if the appliance cannot manage these settings for the target server model (for example, when the server hardware type defines a ProLiant G7 server model). For a complete list of supported servers, see the HPE OneView Support Matrix.
If you keep the default setting and do not select the Manage BIOS check box, the server profile template will not contain any BIOS settings. 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. 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.
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 BIOS settings button | Allows you to edit all BIOS settings.

## Advanced

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

Screen component | Description
--- | ---
MAC addresses | Determines whether the server profiles created from the server profile template uses virtual or physical 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 template is that when you assign the template 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.
WWN addresses | Determines whether the server profiles created from the server profile template uses physical or virtual World Wide Name (WWN) addresses (for Fibre Channel networks). 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 template 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.
Serial number/UUID | Determines whether the server profiles created from the server profile template uses virtual or physical serial number and UUIDs. Virtual serial numbers and UUIDs are generated by the appliance and enable flexibility. The benefit of virtual serial numbers is that when you use a virtual serial in a server profile template and assign the template 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.
Hide unused FlexNICs | This setting provides the ability 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 you have a full complement of eight FlexNICs defined in your server profile but map only four, your operating system will see only the four mapped FlexNICs instead of eight. 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.

See also

- Server Profile Templates

prev | up | next
When to use a server profile template | home | Create a server profile template

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP