Readme File for SANavigator Diagnostic and Management Software for Windows NT4 and Windows 2000. This README file contains the latest information about installing SANavigator Diagnostic and Management Software for Windows NT4 and Windows 2000. For other OS CD installations, open the respective folder in the SANavigator CD to access the readme file. Refer to the IBM Support Website for the latest information and updated README file (See Section 13.0 below). For details on the installation and use of SANavigator refer to the Problem Determination MAPS document, Chapter 5 "Introduction to SANavigator" located on the IBM Support web site (http://www.ibm.com/pc/support). Category is Fibre Channel Solutions -->Diagnostics. Last update: 05/06/2003 CONTENTS -------- This readme file includes the following information: 1.0 Overview 2.0 Change History 3.0 OS Support 4.0 Components 5.0 Configuration 6.0 Requirements 7.0 Obtaining the SANavigator Package 8.0 Installing the Host Bus Adapter SNIA API Library 9.0 Installing SANavigator 10.0 Starting SANavigator 11.0 Uninstalling SANavigator 12.0 Limitations 13.0 Web Sites and Support Phone number 14.0 Trademarks and Notices 15.0 Disclaimer 1.0 OVERVIEW ------------ SANavigator management software provides easy, centralized management and diagnosis of your SAN, and quick access to all device configuration applications. It provides an intuitive interface and powerful point and click functionality. Through its graphical display of the complete SAN, administrators of all levels can manage their networks with ease. With SANavigator you can monitor the health of your SAN and identify potential problems that may impact the performance and/or the availability of your SAN. Along with the available Problem Determination MAPS (PDs), SANavigator greatly facilitates problem isolation and repair of your SAN. Some of the features include: · Intuitive GUI with physical topology display. · Out-of-band and in-band management (requires API library) · Quick identification of port connections for each of your devices · Launch capability of applications and tools such as the IBM FAStT Storage Manager and IBM FAStT MSJ diagnostic. · Event logging · Ability to easily export SAN files so that they can be imported into a remote SANavigator system, displayed and analyzed. 2.0 CHANGE HISTORY ------------------ 11/06/2001: Initial release version 2.6 02/15/2002: Version 2.6.1i: added support for Problem Determination Maps. You can access the PD MAPS (now part of the HMM) by going to the IBM Suport Web Site - Fibre Channel Solutions - Publications. See section 13.0. 03/22/2002: Version 2.7.1i new features: - Zoomable map view buttons in the Physical Map. - Expand/Collapse buttons in the Physical Map to quickly display topology details - Quick Device Search from the main toolbar. Any device pertinent information can be used as the search argument. - A reporting tool that produces several new reports as well as the device list, physical map, plan map diagram all with direct printing from a browser. - HBA Link speed reporting - In-band detection of Active Speed and Supported Speed (requires device driver 8.1.4.6 or higher) - Identification of FAStT HBA's to differentiate them from generic Qlogic cards (requires device driver 8.1.4.6 or higher and in-band enablement). 05/07/2002: Version 2.7.2i - Fixes a problem whereas SANavigator report generation would fail for large SANs. 1/29/2003: Version 3.1i - Initial release of SANavigator 3.1 3.0 OS SUPPORT -------------- This application has been tested with Windows NT 4.0 SP6,Windows 2000 SP2. 4.0 COMPONENTS -------------- SANavigator consists of a Client, Server and a Remote Discovery Connector You can install SANavigator as a client, a server, both client and server, or as a Remote Discovery Connector. The major benefit of using the Client/Server feature is that a SAN running on a server can have a number of clients working simultaneously on the same SAN. Each client can monitor what all other clients are doing, whether across the room or halfway around the world. Each client can access all servers for which it is authorized. Clients can set personal preferences; preferences are saved locally. You install the Remote Discovery Connector on Host(s) that you want to In-Band manage remotely. In addition the Host(s) must have the HBA API library installed · SANavigator Client: This is a Java based GUI application that runs on any Windows NT\W2K system. It allows you to manage a Server connected to the network · SANavigator Server: This is a Java based application running on a system and providing the discovery engine and maintenance of the SAN database. For in-band-discovery, the API library needs to be installed on the server where the Host Bus Adapters are located. Out-of-band discovery (through the network)requires that the SAN be connected to a fabric (either switch or managed hub). · SANavigator Remote Discovery Connector: This is a Java based application running on a remote host. In previous versions of the SANavigator application, the SANavigator server could only discover a network using its internal resources. In version 3.x, you can use the Remote Discovery Connector (RDC) to pool the resources of other hosts in the network to perform discovery. 5.0 CONFIGURATION ----------------- The discovery configuration that SANavigator supports can be divided into two types: In-band and Out-of-band (Network). 5.1 In-Band If your SAN is directly connected to your FAStT Storage Server or to an un-managed hub (that is no switch or managed hub is present) only in-band discovery is possible. In-band discovery takes place on the Server where the Host Bus Adapters are located. Both the client and the server need to be installed. 5.2 Out-of-band (Network) If your SAN is connected to a fabric (switches and\or managed Hubs network connected to your server) out-of-band management is required. The SAN discovery is done through SNMP communication. You can have both in-band and out-of-band management of your SAN. It is recommended that both in-band and out-of-band management be enabled to get the most benefit of SANavigator's discovery and monitoring capabilities. 6.0 REQUIREMENTS ----------------- 6.1 MINIMUM HARDWARE REQUIREMENTS · 700 MHz Intel Pentium III · CD ROM · 512 MB RAM · 150 MB Free Disk Space · VGA 256 Colors or Greater 6.2 SOFTWARE REQUIREMENTS · Microsoft Windows NT 4.0 Server, Enterprise Server, or Workstation with Service Pack 6, or · Windows 2000 Server, Advanced Server, or Professional · FAStT HBA device drivers at level 8.1.5.60 or higher. · HBA SNIA API Library (installed automatically when the driver is installed) 7.0. OBTAINING THE SANavigator PACKAGE -------------------------------------- You can install SANavigator using the CD supplied in the FAStT Storage Server carton or from the IBM Support web site. Check the web site for latest information on SANavigator and to ensure that you have the latest level. 7.1 CD Installation Follow the installation instructions that are enclosed in the CD package. 7.2 Web Download Go to the IBM Support WEB site - http://www.pc.ibm.com/ to access the WEB page. The package located on the web site includes the following: - A link to the SANavigator web site - http://www.sanavigator.com/ibm/xseries to allow you to download SANavigator. This will ensure that you are downloading the latest version of SANavigator. In order to download the package, you will need to register. Please have your FAStT Storage Server model number and serial number to complete the registration. 8.0. INSTALLING the HBA library ------------------------------- 8.1 When the IBM FAStT HBA driver version 8.1.5.6 and above is installed, the API library is automatically installed. Therefore there is no need to install the library separately. 9.0. INSTALLING SANavigator --------------------------- 9.1 Before you begin, obtain your network information, including the IP address and subnets of SAN switches and servers. 9.2 To install SANavigator on your Windows based computer: Unzip the downloaded file and run the Setup.exe file. Follow instructions displayed on the screen. Note: If the default directory is chosen, SANavigator will be installed into C:\Program Files\SANavigator3.1\ 10.0 Starting the SANavigator Server and Client and the Remote Discovery Connector ---------------------------------------------------------------------------------- 10.1 Once the application has been installed,you can start it. Launch SANavigator by clicking on the desktop icon. This will start both the Client and the Server. 10.2 To launch only the client, select SANavigator Client by clicking on Start-->Programs-->SANavigator Client. 10.3 The first time the SANavigator server is started the Welcome Wizard is displayed. The Wizard allows you to configure SANavigator. Note: The wizard will request a license key. You may bypass the license key entry as it is not required for the base version of SANavigator. The full version of SANavigator will be in effect for 30 days. Thereafter the premium features will be disabled. Therefore register your SANavigator application in order to get the latest updates and to continue to have access to all the powerful features of SANavigator. 10.4 In the General tab of the Discovery dialog (Click Discovery--->Setup), select in-band and out-of-band. Make sure Discovery is turned on. 10.5 For in-band, select the IBM FAStT HBA(s) that you want to in-band manage. It is recommended that you select all of them to enhance the discovery and monitoring of your SAN. 10.6 If you installed the Remote Discovery Connector on a remote Host, launch it by clicking on Start-->Programs-->SANavigator Remote Discovery. Although the process starts, no user interface is displayed. Note: to run RDC, the server needs to be configured. Please refer to the online help file or Chapter 25 of the HMM - Setting up SANavigator Remote Discovery Connection for in-band management of remote hosts. Please refer to the online help file or the Problem Determination Maps (PD's) for more information. PD's (now part of the HMM)can be found on the IBM Support Web site. 11.0 Uninstalling SANavigator ------------------------------ 11.1 Before uninstalling SANavigator, the SANavigator Server needs to be terminated. Make sure that no other client is using the server prior to ending the process. To terminate the server and client, click Server -> Shutdown from the menu bar. A dialog is displayed asking you to confirm the Shutdown and whether or not you want to also exit the client. If you do not uncheck the "Shutdown Client also" box, both the Client and Server (on the local machine) will be terminated provided no other remote clients are running. 11.2 Uninstall SANavigator by clicking: Start button-->Programs-->SANavigator3.1-->Uninstall SANavigator 12.0 LIMITATIONS ----------------- 12.1 Discovery 12.1.1 SANavigator defaults to your local subnet for initial discovery. You will need to enter the IP and subnet of the SAN you wish to discover in the Out-of-Band tab of the Discover Setup dialog. 12.1.2 It is more efficient to discover a large subnet by using the broadcast method rather than the sweep or individual IP method. The individual IP method may be faster when discovering a SAN on a subnet that is congested or that has long latencies. 12.1.3 Verify that there is an Ethernet connection to the SANavigator System and all SAN devices (switches and hubs connections are mandatory) before doing a discovery. Otherwise, the message "SAN loaded, no devices present" will be displayed. 12.1.4 SANavigator Servers can be managed by remote SANavigator Clients. To accomplish this, the Client and Server have to be on the same IP subnet address. However, if multiple NICs (Network Interface Cards) are present in the system where the SANavigator Server is running, a remote SANAvigator Client may not be able to connect to the Server unless the common subnet address is assigned to the first NIC in the Server system. Therefore, when you want to manage a SAN from a remote Client ensure that the NIC for the local subnet is first in the binding order. 12.1.5 In the Discovery Setup dialog box General Tab, you can clear the current SAN. This will remove any configuration that you may have previously set up. Therefore, MAKE SURE you export your SAN setup prior to clearing it. 12.1.6 When in-band discovery is enabled, storage devices such as the FAStT Storage Servers will be discovered by their IBM machine type (3526, 3542, 3552, 1742 etc..). However, if no LUNs are present during the in-band discovery, the Storage Servers will be reported as Symbios devices or IBM Universal Xport. This is an indication that the Storage Servers have not yet been configured for use. 12.2 Topology Representation and Display 12.2.1 Changing the color depth of the computer display may cause the window to turn black. This occurs when changing color depth and also when changing from a high resolution to a lower resolution. If your resolution is set at more than 1280 x 1024 pixels, some fields in the Port and LUN Performance dialogs are outside the boundary of the dialog. Increase the size of the dialog manually and they will display properly. 12.2.2 To obtain the best depiction of bridges and routers and the devices connected to them, enter the IP address for each(bridge and router) in the individual addresses table on the Out-of-Band tab of the Discover Setup dialog. Ensure the Ethernet ports of the bridges\routers are connected to the same subnetwork as the switches and associated Hosts. 12.2.3 Delete off line (red) connections and devices from the topology before connecting any new devices to the same port. 12.2.4 Unidentified devices attached to a supported device may display as a Storage or Unknown device. To change the icon to the correct device type, right-click on the device,select "Properties," and then select the correct device type from the drop-down list. 12.2.5 In-band reporting of Configured\Supported speed is valid only for HBAs. Ignore the speed reporting for other devices (FAStT Storage Servers for ex.) 12.2.6 When in a Fabric environment and in-band only is enabled, the in-band discovered devices will be displayed as isolated devices with no interconnections. 12.2.7 In version 2.7, SANavigator displayed the SAN topology as one single fabric. In version 3.x, each switch and associated devices are shown as an individual Fabric. If the switches are connected through ISL (Inter-Switch Link) SANavigator will then display the topology as a single fabric and assign the WWNN of one the switch to the fabric. 12.3 General 12.3.1 In-band Management is not functional when the FAStT MSJ Diagnostics and Configuration application versions below 2.0 rls 32 is running. Ensure that you use FAStT MSJ at version 2.0 Rls 32 or above. 12.3.2 When in-band is enabled, the configured and supported speed of the HBA is displayed in the pop-up device tip. The supported speed refers to the HBA speed capability (either 1Gbps or 2Gbps). The configured speed is dependent on the link connections (1 or 2Gb). To determine the link speed, rely on the HBA device tip information rather than that of a device as this information may not be accurate. 12.4 Release Notes Please refer to the ReleaseNotes.pdf (portable document format) file in the SANavigator install folder for additional limitations and hints. 13.0 WEB SITES AND SUPPORT PHONE NUMBER ---------------------------------------- 13.1 IBM TotalStorage Support Web Site: http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/disk 13.2 IBM TotalStorage Web Site: http://www.storage.ibm.com/ssg.html 13.3 If you have any questions about this update, or problem applying the update go to the following Help Center World Telephone Numbers URL: http://www.ibm.com/planetwide 14.0 TRADEMARKS AND NOTICES ---------------------------- 14.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM Microsoft, Windows, and Windows 2000 are trademarks of Microsoft Corporation in the United States, other countries, or both. SANavigator is a trademark of SANavigator, Inc. Other company, product, and service names may be trademarks or service marks of others. 15.0 Disclaimer ----------------- 15.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 15.2 Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.