Configuring SAN managers to be managed by HPE OneView

You must configure SAN managers using the management software provided by the SAN manager vendor to properly manage them in HPE OneView. After properly configuring the SAN manager, you can add it to HPE OneView.

CAUTION:

Performing zone operations from multiple switches without executing a full zone set distribution might result in the loss of zoning data.

NOTE:

Switch vendors support fabric world wide name (FWWN) or node port world wide name (PWWN) zone memberships. HPE OneView only uses PWWN for zone membership.

Best Practice: SAN managers

  • Always use a single switch to perform all zoning operations, regardless of the management software you use to perform the zoning.

  • Always use the full zone set distribution commands and settings when making zone changes. HPE OneView does this on the SAN manager and SAN through which it is managing by default.

Configuring HPE SAN managers

  • You must have a valid SNMPv3 user with default

    read permissions. See the HPE OneView User Guide.
  • HPE SANs must only be managed by a single HPE OneView appliance.

Configuring Cisco SAN manager

  • You must have a valid SNMPv3 user with write permissions. See the HPE OneView User Guide.

  • Cisco SANs must only be managed by a single HPE OneView appliance.

Configuring Brocade Network Advisor (BNA) SAN manager

  • You must have a valid user account with SMIS running. See the documentation for your SAN manager for more information.

  • To allow HPE OneView to see SAN fabric topology changes automatically, you must disable Track Fabric Changes on the BNA. Otherwise, you must perform an Accept Changes operation on the BNA whenever you make changes to the SAN fabric topology for HPE OneView to see them. See the BNA documentation for more information on disabling Track Fabric Changes.

  • BNA based SANs can be managed by one or more HPE OneView appliances.