For more details, please see ourCookie Policy.

SAN Health Utility

What is required to install SAN Health?

by Moderator ‎04-24-2012 04:17 PM - edited ‎05-16-2014 11:47 AM (2,707 Views)

For a list of SAN Health general topics, please see SAN Health General Information.




SAN Health will run on any modern version of Windows. *NIX hosts are not supported.  SAN Health can be run in a virtual machine running Windows on a UNIX host machine.


SAN Health requires TCP/IP connectivity to the switches that are to be analyzed. Often switches are connected on their own private network or VLAN.  If this is the case, a suitable workstation should be added to this network. If performance data is not being collected then SAN Health will complete execution in less than 4 minutes. Temporarily patching or moving a workstation to the switch VLAN is often a solution.


SAN Health can be connected across Wide Area Networks to remote fabrics, however the WAN link should not be overly bursty as the communication sessions will time out if the expected response from the switch is not received within a timeout period. The Time out period may be adjusted on the Options tab under the "Telnet/SSH Session Timeout and Responsiveness"" section.


The minimum suggested machine specs are as follows:

Intel P4 or AMD Equivalent (AMD K7)
Microsoft Windows XP or higher
512 MB RAM and 20 MB available hard disk space


RAM requirements on the workstation depend on the number of switches that will be concurrently audited. Each switch session uses an incremental amount of memory. As a guide, 40 switches being concurrently audited can use around 512 MB of RAM on the workstation that is running SAN Health and 65 switches being concurrently audited uses around 1 GB of RAM. The maximum number of switches audited at once, 100, can use 2+ GB of RAM.  For very large numbers of switches, you can break the process into several separate audit sessions or groups of switches.


CPU requirements on the workstation depend on the number of switches that will be concurrently audited. CPU use is minimal unless concurrent audits of large (30+) numbers of switches are conducted. To run against the maximum of 100 switches concurrently, a minimum of a dual P4 1000 MHz server is recommended.


In addition to RAM and CPU considerations, hard disk write speed can come into play when auditing large numbers of switches.  100 concurrent telnet sessions, all sending back data that needs to be written to disk can overwhelm the connection to a network attached volume (especially if that volume is using the same network connection as the 100 telnet sessions).  For this reason, the SAN Health Working Directory should be on a fast, locally attached or SAN attached disk when auditing more than 65 switches at one time.  The Working Directory can be set in Options.


SAN Health requires and establishes a Telnet or SSH session to all switches in the identified fabrics. Switches that have the maximum number of logins active cannot be accessed.


Connection to the switches requires a username with either User or Admin access.  Root is not supported.