A customer wants to use the automated zoning feature of HPE OneView. A customer complains that this functionality does not work, even if 3PAR and CPGs are added to HPE OneView. Which other steps…

Question

Options

• AEnable Data Center Bridging functionality on VC modules
• BApply extended FC licenses to Virtual Connect downlink ports using HPE OneView
• CActivate WBEM Providers on supported 3Par arrays
• DAdd the supported SAN Manager to HPE OneView
• EAssociate managed SANs with a FC or FCoE network

• A
  8% (3)
• B
  17% (6)
• C
  3% (1)
• D
  72% (26)

Explanation

Automated zoning in HPE OneView requires the platform to actively communicate with and control SAN fabric switches. D is correct because without a supported SAN Manager (such as Brocade Network Advisor or Cisco DCNM) added to OneView, there is no pathway for OneView to push zone configurations to the physical fabric - the 3PAR and CPG additions alone only cover the storage side. E is correct because even with a SAN Manager present, OneView must know which physical SAN fabric corresponds to each FC/FCoE logical network; without that association, OneView cannot determine where to create zones when a server profile is deployed.

The distractors are wrong for these reasons: A (DCB on VC modules) is a prerequisite for FCoE transport itself, not for automated zoning logic. B (extended FC licenses on downlink ports) enables FC connectivity on VC ports but has no bearing on the zoning automation workflow. C (WBEM Providers on 3PAR) enables storage monitoring and management visibility in OneView but is irrelevant to SAN fabric zone creation.

Memory tip: Think of it as a two-link chain - OneView needs a manager to talk to the fabric (SAN Manager, D) and a map connecting networks to that fabric (SAN-to-network association, E). Both links must exist before zones can be automated.

No community discussion yet for this question.