Most importantly and only in the admin VDC-1 (that is VDC-1), show logging logfile and look for EOBC errors (that is, EOBC errors are logged only in the admin VDC-1).show module in all active VDCs to view any failed diagnostic tests.clearly depicts a hardware failure, do the next steps: The 30 seconds of responsiveness is the scanning of the good hardware and then the 30 seconds of non-responsiveness is the failed hardware. When you see 30 seconds of responsiveness and then 30 seconds of non-responsiveness and then the cycle repeats, this is a clear indication of the hardware diagnostic health check scanning all hardware. impacted at the same time on the say 60-second cycle, this appears to be a hardware failure inside of the N7K control plane as the N7K runs a hardware diagnostic health check consistently. If you show running-configuration is paused - this is a serious indication.During the same exact time as the snmpwalks do not respond with the hostname, issue a show running-configuration within the ssh window.ssh to the VDC in question that has intermittent non-responding snmpwalks for the hostname from Step 1. If the snmpwalks respond say consistently for 30 seconds and then all of sudden stop and become intermittent for say another 30 seconds and then repeat the cycle - this is a serious indication.If the snmpwalks respond consistently without issues, this is most likely not your issue.
Perform a snmpwalk on the various SNMP V3 userids and/or SNMP V2 community strings (that is, walk the hostname mib). Does the intermittent issue occur on a certain cycle? Troubleshoot an Intermittent or Non-Responsive N7K Control Plane 1.
Responsive site designer 1.2 serial how to#
This document describes how to troubleshoot a hardware module in a Nexus 7k when it is non-responsive or intermittent.
0 kommentar(er)
