Which statement about RoCE network restrictions is true?

Question

Options

• ARoCE networks require Virtual Connect SE 32Gb FC Modules.
• BRoCE networks cannot be configured when Virtual Connect modules are used.
• CRoCE networks are supported only when PVLANs are enabled.
• DRoCE networks are not supported with HPE BladeSystem

• A
  4% (1)
• D
  96% (24)

Explanation

RoCE (RDMA over Converged Ethernet) is not supported on HPE BladeSystem because BladeSystem's networking architecture - centered around Virtual Connect - lacks the lossless Ethernet fabric and hardware capabilities required by the RoCE protocol. HPE's newer platforms (like Synergy and rack-mounted servers with appropriate adapters) support RoCE, but BladeSystem is explicitly excluded.

Why the distractors fail:

• A is wrong because Virtual Connect SE 32Gb FC Modules are Fibre Channel modules - they're unrelated to RoCE, which is an Ethernet-based protocol.
• B inverts the logic: the problem isn't that Virtual Connect prevents RoCE configuration in general; rather, BladeSystem as a whole doesn't support RoCE - the restriction is platform-level, not module-presence-level.
• C is a fabricated requirement - RoCE has no dependency on PVLANs (Private VLANs); this is simply not a real technical constraint.

Memory tip: Think "BladeSystem = Blocked from RoCE." BladeSystem is HPE's legacy blade platform, and RoCE support belongs to the newer generation. If you see BladeSystem + RoCE together, the answer is always "not supported."

No community discussion yet for this question.