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 SNMP v3 user with default read permissions.

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

  • The default port on which the switch listens for SNMP requests is 161.

  • The SNMP security level setting can be Authentication, Authentication and privacy, or None.

  • The authentication protocol setting can be SHA or MD5.

  • The privacy protocol setting can be DES-56, AES-128, or 3DES.

Configuring Cisco SAN manager

  • You must have a valid SNMP v3 user with write permissions.

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

  • Cisco SAN managers managed by HPE OneView discover VSANs in the range of VSAN 2 to 4093, but not VSAN 1 (default VSAN) and VSAN 4094 (isolated VSAN). Cisco recommends that you do not use VSAN 1 in your production environment. All discovered VSANs are reflected in the HPE OneView SANs resources for association with HPE OneView FC networks for auto-zoning.

  • The default port on which the switch listens for SNMP requests is 161.

  • The SNMP security level setting can be Authentication or Authentication and privacy.

  • The authentication protocol setting can be SHA or MD5.

  • The privacy protocol setting can be DES-56 or AES-128.

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.

  • Brocade Network Advisor's SMI Agent listens on the following default ports:

    SSL: 5989

    Non-SSL: 598

Configuring Brocade Fabric OS (FOS) switch SAN manager

  • The HPE OneView Brocade FOS switch SAN Manager uses a REST session on the switch. Each fabric (virtual or nonvirtual) configured on the Brocade switch is discovered by the HPE OneView Brocade FOS switch SAN Manager, creating an HPE OneView SAN.

  • You can connect to the Brocade switch REST interface through HTTP (port 80) or HTTPS (port 443). To use HTTPS, configure the switch with an HTTPS certificate.

Configuring Primary SAN manager

  • You can switch between SAN managers and set the desired SAN manager as the Primary SAN manager. Use the Edit SAN dialog box to update the primary SAN manager.

  • The state and the configuration of a managed SAN remains unchanged as only the management path for the SAN is updated.

More information