Status icon

Displays the status of the connection.


Identifier of the connection.


Optional label for a connection. This can be configured in a server profile template or specified within the connection of a server profile.


The connection contains either an unassigned network (that reserves the associated port) or a valid Ethernet network, network set, Fibre Channel, or FCoE network.

Rack servers do not support unassigned connections. Blade servers support unassigned connections.

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. To access an iSCSI device with an Ethernet connection, you must select UEFI or UEFI optimized as the boot mode in the Boot Settings pane. Networks are filtered to both Fibre Channel and FCoE when Type is set to Fibre Channel.


Network sets are not allowed on an iSCSI connection.


Rack servers do not support 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 or server profile template. Network sets are useful with hypervisors, where server profile templates need the ability to define multiple networks.

You can deploy Large network sets to rack servers allowing you to have up to a maximum of 4,000 networks at a time.

For blade servers, duplicate networks are not allowed on the same port. This restriction also applies to networks that belong to a network set. For example, if Network_A is part of NetworkSet_A, the individual network and the network set containing it cannot be assigned to FlexibleLOM 1.


You can place a connection on:
  • A specific FlexNIC


    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


    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:
  1. Fibre Channel

  2. iSCSI

  3. Ethernet (with PXE)

  4. 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:
  • Port 1b and Port 2b must be set to the same function type: Ethernet, iSCSI, or Fibre Channel.

  • You cannot configure the same network on multiple FlexNICs 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.

The link aggregation group name, otherwise, the default is None.

Isolated Trunk

This option appears if there are networks present in the network set that is participating in private VLANs.

When isolated trunk is selected, for each PVLAN domain the primary VLAN ID tags will be translated to the isolated VLAN ID tags for traffic egressing to the downlink ports. Isolated trunk configuration is only recommended for PVLAN-unaware operating systems.


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, PXE secondary, iSCSI primary, or iSCSI secondary


    If you select iSCSI primary or iSCSI secondary with an Ethernet function type, 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

Connection details

The fields available depend on the connection type and boot settings.


Link to the interconnect of the connection.


Specifies the network technology: Ethernet, Fibre Channel or iSCSI.


The World Wide Node Name of the server connection port.


The World Wide Port Name of the server connection port.

MAC address

The MAC address of the server connection port.

Target WWPN

The first Fibre Channel boot target World Wide Port Name.

Target LUN

The first Fibre Channel boot volume LUN value.

Second WWPN

The second Fibre Channel boot target World Wide Port Name.

Second LUN

The second Fibre Channel boot volume LUN value.

Primary boot volume

Shown when the connection is configured to boot from a managed volume.

Secondary boot volume

Shown when a manage volume is configured as a Secondary boot volume.

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 allocation

Specifies if the IPv4 address for the iSCSI initiator is allocated using DHCP or User-specified.

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 HPE StoreVirtual Storage Systems, Single LUN per Target (SLPT) volumes will have LUN 0, and Multi LUN per Target (MLPT) volumes support non 0 LUN values.


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.