Table 2: Example options for a teamed NIC
Allow no network connection
Allow no network teaming
Not selected
Not selected
Multiple connections are required to
allow teamed configuration.
Selected
Not selected
The NIC may not be connected in the
server profile, but if connected
multiple connections for teaming are
required.
Not selected
Selected
The NIC must have a connection, but a
single connection or multiple
connections are allowed. The server
profile is allowed to determine if the
connection is teamed.
Selected
Selected
The server profile is allowed to leave
the NIC unconnected, provide a single
connection, or provide multiple
connections for teaming.
The Plan Script for a teamed NIC may or may not choose to use
.ipaddress2
. If
.ipaddress2
is used, a second IP
address will be configured for a static configuration. If
.ipaddress2
is not used, a single IP address will be given for
the teamed NIC even when multiple connections are made. Often only a single IP address is required for the OS to
configure NIC teaming.
Constraints for
NIC
custom attributes:
Default values
NIC attributes cannot have default values. The value can
either be automatically populated from the IP pool if
auto
mode is enabled in the server profile in HPE OneView or
specified by the user.
To enable DHCP mode in the server profile, select
DHCP as
the IPv4 configuration.
Rules for custom attributes
• Prior to Plan Script execution, custom attributes are replaced with values provided by the server profile or default
values. This action is called attribute expansion.
• The custom attribute name cannot contain spaces or special characters. It can contain numbers, underscores, and
dashes.
• The custom attribute default value cannot contain
@
character. Adjacent custom attributes can be used in the format
@ca1@@ca2@
.
• To include
@
character in a Plan Script, use
@@
.
• The custom attribute value can contain special characters and spaces. Hence custom attributes need to be enclosed in
single or double quotes when used in
guestfish
or
bash
commands in the Plan Script.
• The custom attribute default value given in a Plan Script may not contain a
@
character. A default value which includes
the
@
character, such as an email address, may be placed in the OS Build Plan or Deployment Plan as a default value.
The custom attribute default value can be left blank.
Artifacts
26