Updated April 8, 2024
PDF
Is this helpful? Feedback

New and Changed Information

The following table provides an overview of the significant changes up to this current release. The table does not provide an exhaustive list of all changes or of the new features up to this release.

Release Version Feature Description

NDFC release 12.1.3

Reorganized content

Content within this document was originally provided in the Cisco NDFC-Fabric Controller Configuration Guide or the Cisco NDFC-SAN Controller Configuration Guide. Beginning with release 12.1.3, this content is now provided solely in this document and is no longer provided in those documents.

Host Path Redundancy

The SAN Host Path Redundancy check enables you to view the non-redundant host storage paths. It helps you identify the host enclosure errors along with the resolution to fix the errors.

note.svg

All fabrics that are discovered must be licensed or this feature will be disabled in the Cisco Nexus Dashboard Fabric Controller Web Client. When the feature is disabled, a notification is displayed stating unlicensed fabrics are discovered.
Host Path Redundancy determines that the ports are part of the same enclosure by using the enclosure name displayed in NDFC. If the enclosure names are not exactly the same, then they will be viewed as separate devices. When the names are not exactly the same, the user must manually change the names in the edit enclosure dialog in NDFC, in order for Host Path Redundancy and other features to consider them the same device.


Choose SAN > Host Path Redundancy.

Diagnostic Test

  1. Choose SAN > Host Path Redundancy > Diagnostic Test.

  2. Under the Diagnostic Test tab, use the check boxes to select the host redundancy optional checks.

  3. Check the Automatically run tests every 24 hours check box to enable periodic running of the checker. The checker will run every 24 hours starting 10 minutes after the server starts.

  4. Check Limit by VSANs check box, and select*inclusion* or exclusion. Enter VSAN or VSAN range in the text field to include or skip the host enclosures that belong to VSANs from the redundancy check.

  5. Check other optional checks to perform the relevant check.

  6. Click Clear Results to clear all the errors displayed.

  7. Click Run Tests Now to run the check at anytime.

  8. The results are displayed in the relevant tabs that are next to the Diagnostic Test tab.

Hostpath Errors

Choose SAN > Host Path Redundancy > Hostpath Errors tab to display the host path redundancy errors table. The top of the table displays the colored Good, Errored, and Skipped host enclosure counts.

The following table describes the fields that appear on SAN > Host Path Redundancy > Hostpath Errors.

Field

Description

Host Enclosure

Specifies the hosts that contain the errors. These are counts of each path in the host enclosures seeing an error.

Storage Enclosure

Specifies the connected storage that is encountering the error.

Description

Specifies the description of the error.

Fix

Specifies a solution to fix the error. Point to the error to view a solution to fix the error.

First Seen

Specifies when the error was first seen.

The following table describes the action items, in the Actions menu drop-down list, that appear on SAN > Host Path Redundancy > Hostpath Errors.

Action Item

Description

Ignore Host

Select a row from the table and choose Ignore Host to add the selected rows host enclosure to an exclusion list. The errors from that host will no longer be reported and the current errors will be purged from the database.

Ignore Storage

Select a row from the table and choose Ignore Storage to add the selected rows storage enclosure to an exclusion list.

Ignore Host Storage Pair

Select a row from the table and choose Ignore Host Storage Pair to add the selected rows host-storage pair enclosure to an exclusion list.

Clear Results

Select a row from the table and choose Clear Results to clear the results.

Ignored Host

Choose SAN > Host Path Redundancy > Ignored Host tab to display the list of host enclosures that have been skipped or ignored by the redundancy check along with the reason for skipping.

The following table describes the fields that appear on SAN > Host Path Redundancy > Ignored Host. Select a host enclosure and click Unignore to remove the host from the ignored list and begin receiving errors about the host you had chosen to ignore.

Field

Description

Host Enclosure

Specifies the hosts that contain the errors.

Ignore Reason

Specifies the reason for which the host was ignored.The following reasons may be displayed:

  • Skipped: Enclosure has only one HBA.

  • Host was ignored by the user.

  • Host ports managed by more than one federated servers. Check can’t be run.

  • Skipped: No path to storage found.

Ignored Storage

Choose SAN > Host Path Redundancy > Ignored Storage tab to display the list of storage enclosures that have been selected to be ignored during the redundancy check.

The following table describes the fields that appear on SAN > Host Path Redundancy > Ignored Storage. Select a storage enclosure and click Unignore to remove the storage from the ignored list and begin receiving errors about the storage you had chosen to ignore.

Field

Description

Storage Enclosure

Specifies the connected storage that is encountering the error.

Ignore Reason

Specifies the reason for which the storage was ignored.

Ignored Host Storage Pair

Choose SAN > Host Path Redundancy > Ignored Host Storage Pair tab to display the list of host-storage pairs that have been selected to be ignored during the redundancy check.

The following table describes the fields that appear on SAN > Host Path Redundancy > Ignored Host Storage Pair. Select a row and click Unignore to remove the host-storage pair from the ignored list.

Field

Description

Host Enclosure

Specifies the hosts that contain the errors.

Storage Enclosure

Specifies the connected storage that is encountering the error.

Ignore Reason

Specifies the reason for which the storage was ignored.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

© 2017-2024 Cisco Systems, Inc. All rights reserved.