Troubleshooting > Troubleshooting storage

  

 next

Troubleshooting storage

Brocade Network Advisor (BNA) SAN manager fails to add

Symptom Possible cause and recommendation

Adding the SAN manager fails with the error “No SAN manager can be found at the specified location.”

The BNA or the Standalone SMI Agent is not installed on a server

  • See the BNA software documentation.

A BNA administrator account with full access is not configured and available for use by the appliance

  • See the BNA software documentation.

The Common Information Model Object Manager (CIMOM) is not installed and configured on the server

  • See the BNA software documentation.

The BNA SSL setting and the SSL setting for the BNA on the appliance do not match

  1. Use the BNA software to verify whether or not SSL is enabled. See the BNA software documentation for more information.

  2. From the SAN Managers screen, verify that the Use SSL setting on the appliance for BNA matches the SSL setting in the BNA software. If the SSL setting does not match:

    1. From the main menu, select SAN Managers, and do one of the following:

      • In the master pane, select the BNA and select Actions→Edit.

      • Hover your pointer device in the details pane and click the Edit icon.

  3. For Use SSL, change the value so that it matches the SSL setting in the BNA software.

  4. Click Ok to save your changes.

Unable to establish connection with Brocade Network Advisor (BNA) SAN manager

Symptom Possible cause and recommendation

Unable to establish a connection with the SAN manager

The CIMOM is not bound to the NIC that is on the same subnet as the appliance

Binding the CIMOM to an NIC on the same subnet as the appliance is required for the appliance to connect and communicate with the BNA network management software.

  • See the BNA software documentation.

Volume not available to server hardware

Symptom Possible cause and recommendation

Volume not accessible on the server

A possible cause of a volume not being accessible on the server is that the SAN zone is improperly configured or missing. The following are recommended solutions:

Re-enable the attachment (Managed SAN case)

  1. From the main menu, select Server Profiles.

  2. In the master pane, select a server profile and select Actions→Edit.

  3. Under SAN Storage locate the volume attachment and select Enable.

  4. Click OK.

Create or configure the zone using the SAN management software (no managed SAN)

  • See the SAN manager documentation.

Using managed SANs

  1. Verify that the SAN manager and SAN is associated with the network.

  2. Verify that Automate zoning is enabled.

Automated zoning is not enabled on the SAN

Verify that the zone has been manually configured.

  1. See the SAN manager documentation.

A possible cause of a volume not being accessible on the server is that the Server initiators are not logged into the fabric because the interconnect port is disabled. The following are recommended solutions:

Enable the interconnect port on the appliance

  1. From the main menu, select Interconnects.

  2. In the master pane, select an interconnect and select Actions→Edit.

  3. Locate the port you want to enable and select Enable.

  4. Click OK.

You can also use the REST API to complete this task.

REST API: /rest/interconnects/{id}/ports

See the HPE OneView REST API Reference for more information.

Reconfigure the logical interconnect group

  1. From the main menu, select Logical Interconnect Groups.

  2. In the master pane, select a logical interconnect group and select Actions→Edit.

  3. Edit the uplink sets to connect the networks with the desired interconnect ports.

  4. Click OK.

  5. Verify that the logical interconnect group link comes online.

  6. From the main menu, select Logical Interconnects.

  7. In the master pane, select a logical interconnect and select Actions→Update from group.

You can also use the REST API to complete this task.

REST API: /rest/logical-interconnect-groups/{id} and /rest/logical-interconnects/{id}/compliance

See the HPE OneView REST API Reference for more information.

Verify the cabling

  1. Verify the physical cabling is configured as intended.

A possible cause of a volume not being accessible on the server is that the connection has not been defined in the server profile.

Add a connection to a network in the server profile

  1. From the main menu, select Server Profiles.

  2. In the master pane, select a server profile and select Actions→Edit.

  3. Under Connections click Add Connection.

  4. For Device type select Fibre Channel over Ethernet.

  5. For Network select a network that is connected to the storage system and click Add.

  6. Click OK.

Volume is visible from the storage system but not visible on the appliance

Symptom Possible cause and recommendation

Volume is not in a normal state

A possible cause of a volume not being visible on the appliance is that the volume has been moved to a storage pool that is not managed by the appliance.

Move the volume to a pool that is managed by the appliance and refresh the volume using the storage system software

  • See the storage system documentation.

Bring the storage pool in which the volume resides under management of the appliance
[NOTE: ]

NOTE: If the volume was moved by Adaptive Optimization, Hewlett Packard Enterprise recommends bringing all pools that Adaptive Optimization might use under management of the appliance. This will ensure that the volume is still available to the appliance if it is moved by Adaptive Optimization.

  1. From the main menu, select Storage Pools, and do one of the following:

    • Click + Add storage pool in the master pane.

    • Select Actions→Add.

  2. For Storage System, select the storage system that contains the storage pools you want to add.

  3. For Storage Pool, select the storage pool you want to add.

  4. Click Add to add the storage pool, or click Add + add another pool.

You can also use the REST API to complete this task.

REST API: /rest/storage-pools

See the HPE OneView REST API Reference for more information.

Target port failure

Symptom Possible cause and recommendation

Target port is in a failure state

One cause of target port failure is that the Actual and Expected network are mismatched. Possible causes for this are the following:

The expected network needs to be updated on the appliance

  1. From the main menu, select Storage Systems.

  2. In the master pane, select the storage system and select Actions→Edit.

  3. For the port change the Expected Network so that it matches the Actual Network.

  4. Click OK.

You can also use the REST API to complete this task.

REST API: /rest/storage-systems/{id}

See the HPE OneView REST API Reference for more information.

The enclosure that is physically connected to the storage system has not been added to the appliance (Direct attach)

  • Use the Enclosures screen to add the enclosure to the appliance.

You can also use the REST API to complete this task.

REST API: /rest/enclosures

See the HPE OneView REST API Reference for more information.

The physical cabling is improperly configured (Fabric attach)

  • Verify that the cabling between the storage system and the SAN switch is properly configured.

The physical cabling is improperly configured (Direct attach)

  • Verify that the cabling between the storage system and the enclosure interconnects is properly configured.

Port failed on device

  • Examine your storage system hardware. Repair as necessary.

Zone operations fail on Cisco SAN manager

Symptom Possible cause and recommendation

Zone operations on Cisco SAN manager fail

The snmpd service has crashed

  • View the SAN manager log from the SAN manager software to verify that the snmpd service has crashed. One cause of the snmpd service crashing is out-of-date firmware on the SAN manager.

    Update the firmware on the SAN manager to the latest version

    1. Follow the manufacturer’s instructions for updating the firmware on the SAN manager.

    2. Re-try the zone operation on the appliance.

Storage system port is in an undesired state

Storage system port is in a failing over state
Cause

The port is offline and is in the process of failing over to the partner port.

Action

Wait for the state to change.

Storage system port is in a failed over state
Cause

The port is offline and has failed over to the partner port.

Action

Resolve the issue with the port on the storage system.

Verify connectivity to the infrastructure.

Storage system port is in a failed state
Cause

The port is off offline and cannot fail over to the partner port.

Action

Verify the status and configuration of both storage ports.

Verify cabling or other infrastructure issues.

Storage system port is in a recovering state
Cause

The port is online and in the process of returning to a normal state.

Action

Wait for the state to change.

Storage system port is in a partner port failed over state
Cause

The partner port has failed over and the port is the partner port traffic.

Action

Resolve the issue with the partner port on the storage system.

Verify port connectivity to the infrastructure.

Storage system port is in a partner failed state
Cause

The partner port has failed and the fail over operation was not successful.

Action

Verify the status and configuration of both storage ports.

Verify for cabling or other infrastructure issues.

prev

 

up

 next

Troubleshooting server profiles 

home

 Troubleshooting switches

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP