Pxe settings – HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem User Manual
Page 109
Server management 109
Requested
Calculation
Allocation + remainder
FlexNIC a
2Gb
(2/10)*9800Mb = 1900Mb
2000Mb
FlexNIC b
8Gb
(8/10)*9800Mb = 7800Mb
7800Mb
FlexNIC c
Auto
100Mb
100Mb
FlexNIC d
Auto
100Mb
100Mb
For FlexFabric configurations, the allocated bandwidth for the assigned FCoE connections takes precedence
over the Enet connections in all cases. This implies that if you add FCoE connection bandwidth to a server
port that has both Enet and FCoE connections on different PFs, the Enet connection will have less bandwidth
according to the rules stated above.
PXE settings
Virtual Connect Manager v1.20 and higher supports three PXE options:
•
Enable—VC Manager sends a configuration update to the mezzanine NIC or embedded NIC
associated with the port to enable PXE operations.
•
Disable—VC Manager sends a configuration update to the associated mezzanine NIC or embedded
NIC to disable PXE operations.
•
Use BIOS—Current BIOS settings are used for embedded NICs and mezzanine NIC PXE operations.
VC Manager makes no changes to the current settings.
HP BladeSystem c-Class server blades have a factory default configuration for PXE to be enabled on
embedded NIC 1 only and this is included as the last entry in the RBSU IPL priority list (boot order). VC
Manager and the BIOS limit the number of PXE enabled embedded NICs to one. However, additional NIC
ports from a mezzanine adapter can be enabled simultaneously using the "Use BIOS" settings.
All mezzanine NIC ports can be enabled for PXE booting at the same time, along with one embedded NIC
port. If one or more mezzanine NIC ports are enabled for PXE booting, the user should review the RBSU IPL
list to validate or update the boot order priority.
If you need to enable PXE on more than one NIC port, you must set all of the NICs' PXE configuration option
in the VC Manager to "Use BIOS", and configure the individual PXE NIC settings using RBSU: F9 during
POST to configure an embedded NIC, and F1 during POST to configure the mezzanine NIC ports. After all
of the selected NIC ports are PXE enabled, you must configure the boot order using the RBSU boot order
settings.
Only the first FlexNIC on each physical port of a Flex-10 device can be used for PXE boot. Virtual Connect
cannot enable PXE boot on the remaining FlexNICs of a physical port.
Redundancy for PXE operations can be achieved using multiple PXE enabled NICs. However, the Virtual
Connect Manager is limited to enabling only one NIC for PXE booting. If a configuration requires more than
one NIC to have PXE enabled, you should set all NICs in the VC Manager to the "Use BIOS" setting, and
configure the NIC PXE settings through their respective BIOS utilities (F9 for embedded NICs, and F1 for
mezzanine NIC ports.)
The following table lists examples of valid configurations for PXE enabling NIC ports. This is only a sampling
of the possible valid configurations.
- Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem Virtual Connect 1.10Gb-F Ethernet Module for c-Class BladeSystem Virtual Connect 8Gb 20-port Fibre Channel Module for c-Class BladeSystem Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem 4GB Virtual Connect Fibre Channel Module for c-Class BladeSystem Virtual Connect FlexFabric 10Gb24-port Module for c-Class BladeSystem Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem