# Get Information

# Perform Nexus Health and Configuration Check

<div class="docHeaderComponent base-blowout" id="bkmrk-updated%3Anovember-7%2C-"><div class="infobarClearFix"><div class="infobar"><div class="updatedDate">Updated:November 7, 2023</div><div class="documentId">Document ID:217990<button></button></div></div></div></div>## Contents

<div id="bkmrk-introduction-prerequ"><div class="lia-message-template-summary-zone"><div id="bkmrk-introduction-prerequ-1"><div id="bkmrk-introduction-prerequ-2"><div class="toc-h2">[Introduction](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--504483000)</div><div class="toc-h2">[Prerequisites](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId-1983029833)</div><div class="toc-h3">[Requirements](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--1621375989)</div><div class="toc-h3">[Components Used](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId-866136844)</div><div class="toc-h3">[Conventions](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--941317619)</div><div class="toc-h2">[Health and Configuration Check Procedure](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--951820723)</div><div class="toc-h2">[Health and Configuration Check Modules](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--271762353)</div><div class="toc-h2">[Reports and Caveats](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--405447077)</div><div class="toc-h2">[FAQs](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId-2082065756)</div><div class="toc-h2">[Feedback](https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/217990-configure-an-automated-nexus-health-chec.html#toc-hId--1532843170)</div></div></div><div class="lia-message-template-content-zone">  
</div></div></div>

## Introduction

This document describes the procedure and requirements to perform automatic health and configuration checks for Nexus 3000/9000 and 7000 platforms.

## Prerequisites

### Requirements

Automated Health and Configuration Check is supported only for the Nexus platforms that run standalone NX-OS software, and not the switches that run ACI software.

These hardware platforms are supported:

<div id="bkmrk-nexus-3000%2F9000-seri"><div class="lia-message-template-summary-zone"><div class="lia-message-template-content-zone">- Nexus 3000/9000 series switches that run unified NX-OS software image: 7.0(3)Ix or newer
- Nexus 7000/7700 series switches that run NX-OS software version 7.x or newer

</div></div></div>### Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

### Conventions

Refer to [Cisco Technical Tips Conventions](https://www.cisco.com/c/en/us/support/docs/dial-access/asynchronous-connections/17016-techtip-conventions.html) for more information on document conventions.

## Health and Configuration Check Procedure

  
Please collect **` show tech-support details`** or **`show tech-support `**logs from the Nexus switch for which you would like to perform health and config check. The **`show tech-support details` is preferred, as it provides higher value with more checks done. Please make sure the logs are captured either in .txt or .gz/.tar format. Currently the **`show tech-support`** or **`show tech-support details`** file captured in ASCII and UTF-8 text formats are supported.

  
 Open a regular TAC Service Request at Cisco [Support Case Manager](https://mycase.cloudapps.cisco.com/) with these set of keywords (Technology / Sub-Technology / Problem Code):

**Tech:** Data Center and Storage Networking

**Sub-Tech:** (choose an appropriate platform)  
Nexus 3000 (N3000 series only) - Health and Config Check (AUTOMATED)  
Nexus 3000 (N3100-N3600 series) - Health and Config Check (AUTOMATED)  
Nexus 7000 Series Switch - Health and Config Check (AUTOMATED)  
Nexus 9200 - Health and Config Check (AUTOMATED)  
Nexus 9300 (Non EX/FX/R Series) - Health and Config Check (AUTOMATED)  
Nexus 9300 (EX/FX/R Series) - Health and Config Check (AUTOMATED)

Nexus 9400 series switches - Health and Config Check (AUTOMATED)  
Nexus 9500 (Non EX/FX/R Series) - Health and Config Check (AUTOMATED)  
Nexus 9500 (EX/FX/R Series) - Health and Config Check (AUTOMATED)

Nexus 9800 series switches - Health and Config Check (AUTOMATED)

**Problem Code:** Health and Config Check

  
Once the SR opened, a Cisco [Guided Workflow](https://community.cisco.com/t5/online-tools-and-resources-blogs/introduction-to-guided-workflow/ba-p/4563039) walks you through the steps to upload the**` show tech-support details`** or **`show tech-support` logs.

After the required output uploaded, Cisco analyzes the logs and provides a report (in PDF format) attached to an email sent to you. The report contains a list of issues detected, relevant steps to troubleshoot the problems, and recommended actions plan.

If there are questions in regards to the health check failures reported, users are advised to open a separate service request(s) with appropriate keywords to get further expert assistance. It is strongly recommended to refer the Service Request (SR) number opened for the Automated Health and Config Check along with the report generated to expedite the investigation.


## Health and Configuration Check Modules

Automated Nexus Health and Configuration Check **Version 1**, August 2022 release, performs the checks listed in the Table 1.

**Table 1: Health Check Modules and Associated CLIs used by the Modules**

<div id="bkmrk-index-health-check-m"><div class="lia-message-template-summary-zone"><div class="lia-message-template-content-zone"><table class="sptable"><tbody><tr><td height="44px" width="42.0625px">**Index**

</td><td height="44px" width="154.225px">**Health Check Module**

</td><td height="44px" width="344.513px">**Brief Description of the Module**

</td><td height="44px" width="258.4px">**CLI(s) Used to Perform Health Check**

</td></tr><tr><td height="44px" width="42.0625px">1\.

</td><td height="44px" width="154.225px">NX-OS Release Check

</td><td height="44px" width="344.513px">Checks if the device runs a Cisco recommended NX-OS software release

</td><td height="44px" width="258.4px">**`show version`**

</td></tr><tr><td height="64px" width="42.0625px">2\.

</td><td height="64px" width="154.225px">Nexus EoS/EoL Product Check

</td><td height="64px" width="344.513px">Verifies if any of the components (hardware/software) has reached End-of-Life (EOL) or End-of-Sale (EOS)

</td><td height="64px" width="258.4px">`<strong>show versionshow moduleshow inventory</strong>`

</td></tr><tr><td height="126px" width="42.0625px">3\.

</td><td height="126px" width="154.225px">Field Notice Check

</td><td height="126px" width="344.513px">Checks if the device is potentially affected by a known PSIRT/CVE or Field Notice.

</td><td height="126px" width="258.4px">**`show versionshow moduleshow inventoryshow running-config`**  
and, any command needed to check the file against a given FN/PSIRT.

</td></tr><tr><td height="85px" width="42.0625px">4\.

</td><td height="85px" width="154.225px">NX-OS CPU Health Check

</td><td height="85px" width="344.513px">Checks the symptoms for the elevated CPU utilization. It is reported when the current/historical CPU usage is &gt;60%.

</td><td height="85px" width="258.4px">**`show processes cpushow processes cpu sortshow processes cpu historyshow system resources`**

</td></tr><tr><td height="64px" width="42.0625px">5\.

</td><td height="64px" width="154.225px">NX-OS Memory Health Check

</td><td height="64px" width="344.513px">Checks if memory usage on the device is over the system memory thresholds (default or user configured values).

</td><td height="64px" width="258.4px">**`show versionshow processes memoryshow system resources`**

</td></tr><tr><td height="64px" width="42.0625px">6\.

</td><td height="64px" width="154.225px">NX-OS Interfaces Check

</td><td height="64px" width="344.513px">Checks if any of the interfaces reported drops in either RX or TX direction. The module prints 5 interfaces with the highest error rates in each direction.

</td><td height="64px" width="258.4px">**`show interfaceshow interface briefshow queuing`**

</td></tr><tr><td height="105px" width="42.0625px">7\.

</td><td height="105px" width="154.225px">CoPP Health Check

</td><td height="105px" width="344.513px">Checks if CoPP is disabled, or incorrectly configured (for example, all CPU-bound traffic that hits default-class), or have outdated CoPP policy (for example, carried over from older releases), or &gt;1000 drops reported in non-default classes.

</td><td height="105px" width="258.4px">`<strong>show copp statusshow policy-map interface control-plane</strong><strong>show running-config</strong>`

</td></tr><tr><td height="64px" width="42.0625px">8\.

</td><td height="64px" width="154.225px">Inter-process Communication (MTS) Health Check

</td><td height="64px" width="344.513px">Detects if there are any inter-process communication (referred as MTS) messages stuck for more than 1 day.

</td><td height="64px" width="258.4px">`<strong>show system internal mts buffer summaryshow system internal mts buffer details</strong>`

</td></tr><tr><td height="64px" width="42.0625px">9\.

</td><td height="64px" width="154.225px">Nexus Module Health Check

</td><td height="64px" width="344.513px">Checks if any of the modules (linecard, fabric, and so on) reported diagnostic failures or in powered down / failed state

</td><td height="64px" width="258.4px">**`show moduleshow inventoryshow diagnostic result module all detail`**

</td></tr><tr><td height="64px" width="42.0625px">10\.

</td><td height="64px" width="154.225px">PSU &amp; FAN Health Check

</td><td height="64px" width="344.513px">Detects if any of the power supplies is not in operational state.

</td><td height="64px" width="258.4px">**`show inventoryshow environment <options>show logging logshow logging nvram`**

</td></tr><tr><td height="167px" width="42.0625px">11\.

</td><td height="167px" width="154.225px">vPC Best Practices Check

</td><td height="167px" width="344.513px">Validates the device configuration meets vPC best practices, like peer-router, peer-switch, and peer-gateway configurations.

</td><td height="167px" width="258.4px"><u>Layer3 Peer Router:  
</u>**`show running-config`** (to check if OSPF, EIGRP and BGP adjacencies formed)

<u>Peer-Gateway / Peer-switch:</u>

**`show running-configshow spanning-treeshow vpc briefshow interface brief`**

</td></tr><tr><td height="146px" width="42.0625px">12\.

</td><td height="146px" width="154.225px">MTU Check

</td><td height="146px" width="344.513px">Detects inconsistent MTU configurations, like Layer2 Interface and Layer3 SVI have mismatch MTU configs, Incorrect MTU on OTV Join Interfaces, or Jumbo MTU not enabled on interfaces where it is needed and so on.

</td><td height="146px" width="258.4px">**`show running-configshow interfaceshow ip arp <options>show mac address-tableshow ip route detail <options>show ip eigrp neighbors <options>show ip ospf neighbors <options>show bgp <options>`**

</td></tr><tr><td height="64px" width="42.0625px">13\.

</td><td height="64px" width="154.225px">Layer2 feature Configuration Health Check

</td><td height="64px" width="344.513px">Checks if any L2 feature enabled but not used

</td><td height="64px" width="258.4px">**`show running-config`**

</td></tr><tr><td height="44px" width="42.0625px">14\.

</td><td height="44px" width="154.225px">NX-OS vPC Compatibility Check

</td><td height="44px" width="344.513px">Checks if type1/type 2 incompatibility errors reported of Virtual Port-Channels (vPC).

</td><td height="44px" width="258.4px">**`show running-configshow vpc <options>`**

</td></tr><tr><td height="208px" width="42.0625px">15\.

</td><td height="208px" width="154.225px">Spanning Tree Protocol Health Check

</td><td height="208px" width="344.513px">Checks the attached outputs for an indication of Spanning Tree Protocol instabilities or in unexpected state. Module reports vlans where most recent topology changes occurred together with some additional information:

timestamp, interface and Root bridge ID.

Currently, this health check module supports only RSTP; the support for MST is planned for the future versions.

</td><td height="208px" width="258.4px">**`show spanning-tree detailshow spanning-tree internal errorsshow spanning-tree internal event-history <options>show spanning-tree activeshow logging log`**  
**`show mac address-table notification mac-move`**  
**`show system internal <L2FM, MTM, L2DBG options>`**

</td></tr><tr><td height="44px" width="42.0625px">16\.

</td><td height="44px" width="154.225px">PortChannel Health Check

</td><td height="44px" width="344.513px">Detects if any of the configured port-channel members is in unhealthy state: (I), (s) (D) or (H)

</td><td height="44px" width="258.4px">**`show port-channel summary`**

</td></tr><tr><td height="44px" width="42.0625px">17\.

</td><td height="44px" width="154.225px">SFP Validation Check

</td><td height="44px" width="344.513px">Detects any transceivers which reported "SFP Validation Failed" error

</td><td height="44px" width="258.4px">`<strong>show interface brief</strong>`

</td></tr><tr><td height="64px" width="42.0625px">18\.

</td><td height="64px" width="154.225px">Layer3 Feature Configuration Health Check

</td><td height="64px" width="344.513px">Checks if any L3 feature enabled but not used

</td><td height="64px" width="258.4px">**`show running-config`**

</td></tr><tr><td height="44px" width="42.0625px">19\.

</td><td height="44px" width="154.225px">Default Route via Management VRF Check

</td><td height="44px" width="344.513px">Checks if the device has a default route configured in the Default vrf pointing through Management vrf.

</td><td height="44px" width="258.4px">**`show running-configshow accounting log`**

</td></tr><tr><td height="64px" width="42.0625px">20\.

</td><td height="64px" width="154.225px">Unsupported Multicast Routing over vPC Check

</td><td height="64px" width="344.513px">Checks for unsupported PIM adjacency over vPC

</td><td height="64px" width="258.4px">`<strong>show running-configshow ip pim interface vrf all internalshow ip pim neighbor vrf all detail</strong>`

</td></tr><tr><td height="193px" width="42.0625px">21\.

</td><td height="193px" width="154.225px">OSPF Health Check

</td><td height="193px" width="344.513px">Checks for a possible adjacency issues observed on the device.For example:

- multiple neighbors detected on interface configured as P2P
- router ID not configured manually or that used a loopback IP
- adjacencies not in FULL state
- adjacencies which reached FULL state recently and indicates potential instability

</td><td height="193px" width="258.4px">**`show running-configshow ip interface brief vrf allshow ip ospf neighbors detail vrf all privateshow ip ospf interface vrf all privateshow logging log`**

</td></tr><tr><td height="195px" width="42.0625px">22\.

</td><td height="195px" width="154.225px">EIGRP Health Check

</td><td height="195px" width="344.513px">Checks for a possible adjacency issues observed on the device. For example:

- AS number not configured
- No active neighbors detected
- High Values of SRTT, RTO or Q Cnt detected
- High number of dropped EIGRP packets detected
- Lesser than 15 mins uptime of adjacency, and indicates potential instability
- Adjacency went down in last 7 days

</td><td height="195px" width="258.4px">**`show running-configshow logging logshow ip eigrp neighbors detail vrf allshow ip eigrp detail vrf all`**

</td></tr><tr><td height="44px" width="42.0625px">23\.

</td><td height="44px" width="154.225px">BGP Peers Health Check

</td><td height="44px" width="344.513px">Checks for BGP adjacency in IDLE state.

</td><td height="44px" width="258.4px">**`show running-configshow bgp vrf all all summary`**

</td></tr><tr><td height="50px" width="42.0625px">24\.

</td><td height="50px" width="154.225px">First-Hop Redundancy Protocol (FHRP)

</td><td height="50px" width="344.513px">Checks for the non-default timer configurations, as these configurations can result in a sub-optimal performance.

This health check module covers ONLY Hot-Standby Routing Protocol (HSRP)

</td><td height="50px" width="258.4px">**`show running-config`**

</td></tr></tbody></table>

</div></div></div>## Reports and Caveats  


<div id="bkmrk-the-health-and-confi"><div class="lia-message-template-summary-zone"><div class="lia-message-template-content-zone">- The Health and Config Check SR is automated and handled by the Virtual TAC Engineer.
- The report (in PDF format) is usually generated within 24 business hours after all necessary logs attached to the SR.
- The report is automatically shared over email (sourced at <u>jhwatson@cisco.com)</u> with all contacts (primary as well as secondary) associated with the service request.
- The report is also attached to the Service Request to allow its availability at any later point in time.
- Be advised that the issues listed in the report are based on the logs provided and within the scope of the health check modules listed previously in Table 1.
- The list of health and configuration checks performed is non-exhaustive and users are advised to perform further health checks as needed.
- For Nexus 7000 with multiple Virtual Device Context (VDC) a show tech-support details file can be needed from each VDC for best results.

</div></div></div>## FAQs

**Q1: Can I upload `show tech-support details` for more than one switch in the same SR to get Health Check report for all the switches?**

A1: This is an automated case handling and the health checks are performed by the Virtual TAC Engineer. The health check is done for <u>only the first </u> **`show tech-support details`** uploaded.

**Q2: Can I upload more than one *`s`*`how tech-support details` for the same device say, captured few hours apart, to get health check done for both?**

A2: This is an automated and stateless case handling performed by the Virtual TAC Engineer and the Health and Config Check is done for the first the **`show tech-support details`** file uploaded to the SR, irrespective of whether the files uploaded are from the same switch or different switches.

**Q3: Can I get health checks done for the switches whose `show tech-support details` files compressed as a single rar/gz file and uploaded to the SR?**

A3: No. if multiple **`show tech-support details`** are uploaded as a single rar/zip/gz file, only the first file in the archive is processed for health checks.

**Q4: I do not see the health and configuration check that covers the Nexus 5000/6000 platforms. Is it covered at later point in time?**

A4: No. As of now, there is no plan to cover Nexus5000/6000 platforms in near future.

**Q5: What can I do if I have questions about one of the health check failures reported?**

A5: Please open a separate TAC Service Request to get further assistance on the specific health check result. It is highly recommended to attach the health check report and refer the Service Request (SR) Case number opened for the automated health and config check.

**Q6: Can I use the same SR opened for the Automated Health and Config Check to troubleshoot the issues found?**

A6: No. As the proactive health check is automated, please open a new Service Request to troubleshoot and resolve the issues reported. Please be advised that the SR opened for health check is closed with in 24 hours after the health report published.

**Q7: Does the automated health and config check run against the `show tech-support details` file for the switch that runs versions older than the one mentioned previously?**

A7: The automated health and configuration check is built for the platforms and software releases mentioned below. For devices that run older versions, it is best effort and there is no guarantee on the accuracy of the report.

<div id="bkmrk-nexus-3x00-series-sw"><div class="lia-message-template-summary-zone"><div class="lia-message-template-content-zone">- Nexus 3x00 series switches that run unified NX-OS software image: 7.0(3)Ix or newer
- Nexus 7000/7700 series switches that run NX-OS software version 7.x or newer
- Nexus 9x00 series switches that run unified NX-OS software image: 7.0(3)Ix or newer

</div></div></div>**Q8: How do I close the SR opened for Health Check?**

A8: The SR is closed within 24 hours after the first Health Check report is sent. No action needed from the user towards SR closure.

**Q9: How do I share comments or feedback about the Proactive health and configuration Check?**

A9: Please share them through email to [Nexus-HealthCheck-Feedback@cisco.com](mailto:nexus-healthcheck-feedback@cisco.com)


**Q10. What is the recommended method to capture `show tech-support ` or `show tech-support details` from a switch?**

A10: It is highly recommended to capture the output of **`show tech-support`** or **`show tech-support details`** command by directing it to **`bootflash:`** (as shown in the next example) rather than capturing it to a log file in the terminal application (for example, SecureCRT, PuTTY). Please remember the log file captured by the terminal application could be in UTF-8-BOM format (or similar) which is NOT supported by the automated health check. The Automated Health &amp; Config check supports file only in ASCII or UTF-8 formats.

Example CLIs to redirect the output to **`bootflash:`** and compress the file.

**`SwitchA# show tech-support details >> bootflash:show-tech-support-details-SwitchA-2023Jan01.txtSwitchA# gzip bootflash:show-tech-support-details-SwitchA-2023Jan01.txt`**

## Feedback

Any feedback on the operations of these tool is highly appreciated. If you have any observations or suggestions (for example, about the ease of use, scope, quality of the reports generated) please share them with us at [Nexus-HealthCheck-Feedback@cisco.com.](mailto:nexus-healthcheck-feedback@cisco.com)

### Revision History

<div id="bkmrk-revision-publish-dat"><div id="bkmrk-revision-publish-dat-1"><div><table border="1" id="bkmrk-revision-publish-dat-2"><tbody><tr><th>Revision</th><th>Publish Date</th><th>Comments</th></tr><tr class="published"><td><div align="center">9.0</div></td><td><div align="center">07-Nov-2023</div></td><td><div align="left">Update</div></td></tr><tr class="published"><td><div align="center">8.0</div></td><td><div align="center">08-Jun-2023</div></td><td><div align="left">Recertification. Informational update.</div></td></tr><tr class="published"><td><div align="center">7.0</div></td><td><div align="center">07-Jun-2023</div></td><td><div align="left">Informational update.</div></td></tr><tr class="published"><td><div align="center">5.0</div></td><td><div align="center">09-Jan-2023</div></td><td><div align="left">Updated.+</div></td></tr><tr class="published"><td><div align="center">4.0</div></td><td><div align="center">19-Oct-2022</div></td><td><div align="left">Informational update</div></td></tr><tr class="published"><td><div align="center">3.0</div></td><td><div align="center">04-Sep-2022</div></td><td><div align="left">Revision</div></td></tr><tr class="published"><td><div align="center">2.0</div></td><td><div align="center">25-Jul-2022</div></td><td><div align="left">Initial Release</div></td></tr><tr class="published"><td><div align="center">1.0</div></td><td><div align="center">25-Jul-2022</div></td><td><div align="left">Initial Release</div></td></tr></tbody></table>

</div></div></div>