we get the following error while trying to login to the fabric.
"SNMP engine discovery timeout. It could be
---no route from null/0.0.0
---10.64.18.61 snmpd is unresponsive"
but sometimes we are able to login. If we keep on trying to login after several attemps we are able to login but we get Timeout(server, client) error on the core switch and cannot do any zonings or check device manager for that switch.
Other switches in the fabric are working fine.
any suggestions, could this be some issue with ethernet card for the switch?
Attaching screenshots for more clarification on the issue.
2010.11.24 02:50:57 WARN [snmp.tcp] Response after timeout (in process packet): 02:50:57 172.27.xx.xx, 1606970293 RESP u=xxxx clmLicenseFlag.....
Of note to mention, I installed Fabric Manager 5.01a on another server and duplicated the timeout behavior. I uninstalled 5.0.1a and installed Fabric Manager 3.3.4a and it works without any of the issues we are seeing.
It looks like we may have discovered the cause for our timeout issues. Fabric Manager was attempting to manage two UCS environments for which the SNMPv3 user was not set. The explanation given was "The UCS authentication failures affect the overall performance of FM due to CPU expensive exception handling".
The timeouts went away once I established the same SNMPv3 user and password on the UCS's that we have set for the seed switches on the fabrics.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...