Which parameters can be defined in a server profile template for HPE Synergy Compute Modules? (Select two.)

Question

Options

• Apartition layout for servers running Linux.
• BIL0 IPv4 or IPv6 address.
• Clocal storage and BIOS settings.
• DNIC teaming setup at OS level.
• Enetwork and storage connectivity.

• B
  5% (1)
• C
  89% (17)
• D
  5% (1)

Explanation

Server profile templates in HPE Synergy (managed via HPE OneView) operate at the hardware and firmware layer, defining how a compute module is configured before the OS is ever involved. Local storage and BIOS settings (C) are directly configurable - you can define RAID logical drives and BIOS parameters such as boot order, power management, and processor settings within the template. Network and storage connectivity (E) is also a core function - templates specify which networks, VLANs, and SAN/FC fabrics the module's connections map to, enabling consistent, repeatable connectivity profiles.

Why the distractors are wrong:

• A (Linux partition layout): Disk partitioning is handled by the OS installer or provisioning tools (e.g., kickstart, Ansible) - far above the hardware abstraction layer that server profiles target.
• B (iLO IPv4/IPv6 address): iLO IP addresses are assigned through dedicated iLO network configuration or DHCP, not within a server profile template.
• D (NIC teaming at OS level): NIC teaming/bonding is configured inside the OS (e.g., via nmcli or Windows Server NIC teaming) - the template only defines which physical connections exist, not how the OS aggregates them.

Memory tip: Think of server profile templates as defining the physical hardware blueprint - what the server is (BIOS, storage) and how it's wired (network/SAN connectivity). Anything that requires an OS to be running (partitioning, NIC teaming) or a separate management network (iLO IP) falls outside the template's scope.

No community discussion yet for this question.