HP Virtual Connect Enterprise Manager Software - Manual (Page 60)

NOTE: To create profiles for Integrity Blades that boot from SAN, you must manually configure the SAN
boot entries in the blade server EFI console.
Configuring the target boot LUN
When creating or editing server profiles, you can specify a target boot LUN for the FC SAN connections
designated as Primary and Secondary in the boot priority column.
Target boot LUN values must be compliant with proper ranges.
▲ VC Domains—You can provide the target boot LUN in either of the possible formats:
When using LUN values from 0–255, you can specify the LUN and either decimal or in 16-digit
hexadecimal number format.
•
•
When using LUN values greater than 255, you must specify the LUN in 16-digit hexadecimal
number format.
To specify the LUN and a 16-digit hexadecimal number format, place the desired hexadecimal number
preceded by leading zeros as shown in the following examples:
•
1023 can be represented in 16-digit hexadecimal format as 00000000000003ff or
00000000000003FF (not case-sensitive).
•
18446744073709551615 is represented in 16-digit hexadecimal format as ffffffffffffffff or
FFFFFFFFFFFFFFFF.
Configuring multiple networks
When creating or editing a profile in a VC Domain, you can configure multiple networks to use as a same
Ethernet connection port.
1. In the Ethernet connections table expand the network name menu and select Multiple Networks. The
Server VLAN tag to vNet Mappings window appears.
Figure 5-3 Server VLAN tag to vNet Mappings window
2. Select the vNet name server VLAN ID.
3. To add a vNet mapping, click Add Mapping. To remove a mapping, click the Delete icon.
You can select one mapping to be untagged, meaning the VLAN ID is applied to that mapping.
4. (Optional) Instead of deleting mappings manually, the Copy from button enables you to copy the
mappings from an existing profile or from a Shared Uplink Set.
60 Managing server profiles