Overview

Screen component

Description

Status icon

Displays the status of the connection.

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. To access an iSCSI device with an Ethernet connection, you must select UEFI or 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.
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.

You can deploy Large network sets when using the HPE Virtual Connect SE 100Gb F32 Module for HPE Synergy. Large network sets can contain up to 4,094 networks minus the number of networks that are in the reserved VLAN range, which can range from 60 to 128 networks. The default is 128 networks. Generally, the maximum number of networks is 3,966 networks. A maximum of 60 distinct large network sets can be simultaneously deployed per logical interconnect.

Port

You can place a connection on:
  • A specific FlexNIC

  • 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:
  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.

Before you assign a connection to a FlexNIC, the following conditions must be met:
  • You cannot configure the same network on multiple FlexNICs of a single physical port. This includes networks in a network set.

  • For the number of networks you can configure on a single physical port, see the Support Matrix.

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

    NOTE:

    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.

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 subnet mask

Subnet mask of the iSCSI initiator.

Initiator gateway

Subnet gateway of the iSCSI initiator.

Boot target

Name of the boot target.

WWPN for volumes that use Fibre Channel protocol.

IQN for volume that use iSCSI protocol.

Boot LUN

Storage LUN (logical unit number) from the storage array.

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.

Requested virtual functions
The requested virtual functions setting:
None

(Default)

Custom

Select the number of requested virtual functions, up to the maximum number available on the port.

Auto

Virtual functions are distributed automatically across the physical ports.

Allocated virtual functions

Number of allocated virtual functions.