nerdexam
HP

HPE2-T37 · Question #22

You configured downlink aggregation for one of the HPE Synergy Compute Modules in an environment by placing two connections in the same Link Aggregation Group. After you made the changes to the…

The correct answer is C. Link Aggregation Group functionality should be enabled in advanced properties of the Logical. Option C is correct because in HPE Synergy, Link Aggregation Group functionality must be explicitly enabled in the advanced properties of the Logical Interconnect (or Logical Interconnect Group) before the server profile LAG configuration is recognized as valid - the…

Troubleshoot HPE OneView

Question

You configured downlink aggregation for one of the HPE Synergy Compute Modules in an environment by placing two connections in the same Link Aggregation Group. After you made the changes to the server profile, its status changed to critical. What can be done to fix this issue?

Options

  • AThe teaming or bonding driver in the server OS must be configured to enable the LACP and to
  • BThe server profile for a given HPE Synergy compute module should be reapplied, then the
  • CLink Aggregation Group functionality should be enabled in advanced properties of the Logical
  • DEnsure that the Link Aggregation Group time-out value matches the server set values.

How the community answered

(28 responses)
  • A
    7% (2)
  • B
    29% (8)
  • C
    54% (15)
  • D
    11% (3)

Explanation

Option C is correct because in HPE Synergy, Link Aggregation Group functionality must be explicitly enabled in the advanced properties of the Logical Interconnect (or Logical Interconnect Group) before the server profile LAG configuration is recognized as valid - the infrastructure layer must support the feature before a server profile can use it, and omitting this step causes the profile to report a critical status.

Why the distractors are wrong:

  • A is wrong because OS-level teaming/bonding configuration affects traffic behavior within the server, not the server profile compliance status managed by HPE OneView - fixing the OS doesn't resolve the critical alert.
  • B is wrong because reapplying the profile doesn't resolve the root cause; the Logical Interconnect still lacks LAG support, so the profile will remain critical after reapplication.
  • D is wrong because LACP timeout mismatches are a secondary tuning concern, not a cause of a critical server profile status, and the feature itself must first be enabled before timeouts matter.

Memory tip: Think "top-down" - in Synergy, infrastructure features (Logical Interconnect) must be enabled before server profiles can consume them. If a profile goes critical after adding LAG, look up the stack to the interconnect advanced settings, not down to the OS or sideways to the profile itself.

Topics

#downlink aggregation#Link Aggregation Group#server profile#LACP

Community Discussion

No community discussion yet for this question.

Full HPE2-T37 Practice