07-21-2009 07:59 AM
Has anyone else had problems with SAN Health 3.2 losing connection to switches? It loses connection within a minute or so to almost all the switches. I've reverted to SAN Health 3.1.4a and that seems fine.
07-22-2009 04:22 PM
SAN Health 3.2.0 added a few new commands to the group of commands that run against the switches. It could be that your switches don't respond to one of the new commands. There were also some minor timing adjustments made between 3.2.0 and 3.2.0c which may have corrected the issue for you. This is especially true for M-Series switches. If you'd like to use SAN Health 3.2.0c (available at www.brocade.com/sanhealth), you can send the logs in from the failed audits to firstname.lastname@example.org and we can help you troubleshoot.
07-31-2009 07:53 AM
I have the same problem.
It seems that the connection is lost when running the uRouteShow command towards the Director 48000 switches during Diagnostics. uRouteShow runs fine towards the other switch types in our fabrics.
I have tried to change the "Diagnostic Response Timeout" parameter with no success.
Disabling the uRouteShow under Switch Diagnostics did the job.
07-31-2009 09:23 AM
You can test this out by manually telnetting to the 48000 and issuing the uRouteShow command to see if the switch responds. If so, please let us know at email@example.com and we can help you troubleshoot SAN Health. If uRouteShow doesn't respond, or telnet disconnects when you run it, you'll need to contact your support provider or Support@brocade.com for assistance. There could be a known fix for the problem.
SAN Health Admin