san insite professional user’s guide - fujitsu · sanview client; discovery, monitoring, and...

User Guide

ii

REVISION NOTICEThis is the second release of this manual. A complete revision history is provided at the end of the manual.

ABSTRACTThe Softek SANView User’s Guide (ML-145012) describes configuring the Softek SANView Server; navigating the Softek SANView Client; discovery,monitoring, and management; and reference information, including the Client menu options, the Server file locations and log file descriptions, moduleinformation, and shortcuts.

FOR FURTHER INFORMATIONIf you wish to obtain further information about the Fujitsu Softek product discussed in this publication, contact your Fujitsu Softek marketing representative,or write to Fujitsu Softek, Marketing Communications, Mail Stop 215, P.O. Box 3470, Sunnyvale, CA 94088-3470.

TECHNICAL SUPPORTTo obtain technical support on the Fujitsu Software Technology Corporation product discussed in this publication, please call 1-800-66SOFTEK.

RESTRICTION ON USEThe information contained in this manual is the licensed property of Fujitsu Software Technology Corporation. Use of the information contained herein isrestricted pursuant to the terms and conditions of a license agreement.Fujitsu Softek and Softek SANView are trademarks of Fujitsu Software Technology Corporation.Vixel is a registered trademark of Vixel Corporation.Microsoft and Windows are registered trademarks and Windows NT and XP are trademarks of Microsoft Corporation.All other trademarks and product names are the property of their respective owners.© 2002 Fujitsu Software Technology Corporation.All rights reserved. Printed in U.S.A.All specifications are subject to change without notice.

This product includes software developed by Walt Disney Internet Group (http://opensource.go.com/), used per the Tea Software License. Text of thislicense follows:The Tea Software License, Version 1.0Copyright (c) 2000 Walt Disney Internet Group. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentationand/or other materials provided with the distribution.3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:"This product includes software developed by Walt Disney Internet Group (http://opensource.go.com/)."Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names "Tea", "TeaServlet", "Kettle", "Trove", "BeanDoc", "GO.com", and "Walt Disney Internet Group" must not be used to endorse or promoteproducts derived from this software without prior written permission. For written permission, please contact [email protected]. Products derived from this software may not be called "Tea", "TeaServlet", "Kettle", "Trove" or "BeanDoc" nor may "Tea", "TeaServlet", "Kettle", "Trove" or"BeanDoc" appear in their name, without prior written permission of Walt Disney Internet Group.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL GO.COM OR ITSCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

• LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION

About This Guide

This manual describes configuring the Softek SANView Server; navigating the Softek SANView Client; discovery, monitoring, and management; and reference information, including the Client menu options, the Server file locations and log file descriptions, module information, and shortcuts.

Audience

The Softek SANView User Guide is for users, such as system and network administrators and managers, who use Softek SANView to monitor or manage their Storage Area Networks (SANs).

Contents of this Manual

Chapter Description

Chapter 1: Introduction Softek SANView features and functionality (overview)

Chapter 2: Installation How to install Softek SANView

Chapter 3: Setting Up the Server Softek SANView Server SAN Administration window, including notification, log, discovery, scheduler, agent, SNMP traps, archivingSoftek SANView Root Directory

Chapter 4: Navigating the Client

Softek SANView main window overviewViewing and refreshing the Softek SANView Client framesCustomizing the topology frameFinding devicesSaving a topology snapshot

Chapter 5: Discovery Discovering and adding agents, devices, and subnets

Chapter 6: Monitoring the SAN Features for status monitoringConfiguring thresholdsTroubleshooting tips/techniques

Chapter 7: Managing Devices Performing configuration tasksAnalysis modulesCondition reports

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • iii

SO

FTE

KA

bout

Thi

s G

uide

iv

Contacting Technical Support

At Fujitsu Software Technology Corporation, we work hard to provide products and service that anticipate and solve our customers’ increasingly complicated application management challenges. In addition, we try to provide clear and easy-to-use online and printed documentation to enable you to work independently in managing application recovery issues. If you have a technical issue that you can’t answer with the provided resources, please contact our Technical Support department. All of our Support Representatives are eager to answer your questions and help you simplify your application management.

To obtain technical support on the Fujitsu Softek product discussed in this publication, call:

- From North America, please dial 1-800-66 SOFTEK.

- From Europe, please dial 00800-66 SOFTEK (country code is not required).

Chapter 8: Client Menus File, View, Options, Tools, and Help menus

Chapter 9: Server Files Device configuration, device firmware, and log files on the Softek SANView Server

Chapter 10: Modules Features and functionality of Brocade, Crossroads, Chaparral, Fibre Channel MIB, Gadzoox, McData, Vixel, GR, and Host Agent modules.

Chapter 11: Host Agent Features and functionality of the Host Agent and its components: Fibre Channel HBA, Fujitsu PFCA HBA, and the SDS Virtualization Agent.

Appendix A: Backing Up and Restoring the Database

Backing up and restoring the Softek SANView database

Appendix B: Shortcuts Shortcuts and Solaris commands for common tasks

Appendix C: Event Messages SAN Event message descriptions

Appendix D: Reference Materials

Information on obtaining reference material for Fibre Channel

Glossary Networking and SAN-related terminology

• Fujitsu Softek Global Support Center (World-Wide) 800-66 SOFTEK(763835)

Chapter Description


Abo

ut T

his

Gui

deso

ftek.

fujit

su.c

om

Notices

The following notices are used throughout this manual.

Related Publications

The following publications contain related information.

��

!CAUTION:Alerts readers to a situation that could damage the software or interrupt operations.

NOTE Gives readers additional significant information about the subject to increase their knowledge or to guide their actions.

TIP Helps users apply the techniques and procedures described in the text to their specific needs.

Title Part Number

Softek SANView Software and Installation Release Notes, Version 4.1

ML-145014

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • v

CONTENTS

CHAPTER 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

What is Softek SANView? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

CHAPTER 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Getting Ready to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

All Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Softek SANView Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Softek SANView Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installing and Starting Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . 9Installing the Softek SANView Host Agent . . . . . . . . . . . . . . . . . . . . . . 11Uninstalling Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Upgrading Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Upgrading Softek SANView from versions prior to version 3.5 . . . . . . . . . . . . . . 13

CHAPTER 3: Setting Up the Server . . . . . . . . . . . . . . . . . . . . . . 15

SAN Administration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Notification Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Discovery Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Persisting the SAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Discovering Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Scheduler Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Agent Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24SNMP Traps Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Archiving Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • vii

viii

License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Softek SANView’s Root Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Running the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

CHAPTER 4: Navigating the Client . . . . . . . . . . . . . . . . . . . . . . 29

Starting Softek SANView Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Using Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Other Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Using the Softek SANView Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Detaching the Tree and Topology Frames . . . . . . . . . . . . . . . . . . . . 35Resizing the Tree and Topology Frames . . . . . . . . . . . . . . . . . . . . . 35

Understanding the Softek SANView Client . . . . . . . . . . . . . . . . . . . . . . 36Devices and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Understanding Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Color-Independent Indication of Device Health . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Tool Tips in Topology Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Understanding the Topology Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Topology Frame Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Creating Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Creating Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Creating Manual Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Group Path Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Topology Frame Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Device Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Group Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Enclosure Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Contained Devices Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Device Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Connected Devices Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Device Password Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Understanding the Tree Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Grouping Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Sorting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50


Tool Tips in Tree Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Understanding the SAN Events Frame . . . . . . . . . . . . . . . . . . . . . . . . . 51Finding Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Saving a Snapshot of the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

CHAPTER 5: Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Discovering Agents and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Discovering Agents Outside the Local Subnet . . . . . . . . . . . . . . . . . . 58

CHAPTER 6: Monitoring the SAN . . . . . . . . . . . . . . . . . . . . . . . 61

Checking Health Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Viewing and Logging Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . 64

Understanding SAN Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Understanding Device Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Setting Up Email Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Interpreting Device Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Configuring Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Statistic Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Troubleshooting your SAN with Softek SANView . . . . . . . . . . . . . 76Softek SANView Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring Analysis Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Port Configuration Analysis Module . . . . . . . . . . . . . . . . . . . . . . . . 79Detect Port Link Fa ilures Analysis Module . . . . . . . . . . . . . . . . . . . 80Condition Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Viewing the Condition Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Condition Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

CHAPTER 7: Managing Devices . . . . . . . . . . . . . . . . . . . . . . . . 85

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Performance Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Archive Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Delete Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Historical and Real-time Graphing View . . . . . . . . . . . . . . . . . . . . . 92World-Wide Name Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Understanding How WWN Zoning Works . . . . . . . . . . . . . . . . . . . . 93

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • ix

x

Current WWN Zoning Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Configuring & Activating WWN Zoning . . . . . . . . . . . . . . . . . . . . . . 94

Creating a Zone Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Creating Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Creating Zone Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Saving a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Loading a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Importing the Active Zone Set into the Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Changing the Switch Used to Manage the Zoning Change in the Fabric: . . . . . . 97Hiding Unselected Items in the Detail of Selected Object box . . . . . . . . . . . . . . . 97Renaming a Zone Set or Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Deleting a Zone Set, Zone, or Zone Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Default Zoning (Vixel Devices Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Activating the New Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Representing Devices Using an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

CHAPTER 8: Client Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

CHAPTER 9: Server Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Device Configuration & Firmware Files . . . . . . . . . . . . . . . . . . . . . . . . 115Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

CHAPTER 10: Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Brocade Module v3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121GR Family Module v1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Chaparral Module v2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Crossroads Module v2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Fibre Channel MIB Module v2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Gadzoox Module v1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125McData Module v1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125SCSI Target Module v1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Device View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128


Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Vixel Module v1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

CHAPTER 11: Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Features & Supported Device s for the Host Agent’s Fibre Channel HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Running the Host Agent (FC HBA Proxy, PFCA Proxy, or SDS Proxy). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Discovering HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Understanding HBA Displays in Softek SANView . . . . . . . . . . . . . . . 135

Finding Health Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Locating World-Wide Names and Other Information . . . . . . . . . . 136Viewing HBA Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Back-of-box View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Port Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Port Statistics View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Understanding Recorded Events . . . . . . . . . . . . . . . . . . . . . . . . . . 140Fujitsu PFCA HBA Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 141PFCA Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142List of properties captured by this module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Hardware Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Optical module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142SIG (Signal Detect) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143HB (Heart Beat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143LINK (Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143CHK (Check) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

SDS Virtualization Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Appendices

A Backing Up and Restoring the Database . . . . . . . . . . . . . . . . . . . 145

B Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

C Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

D Reference Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • xi

xii

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Figures

Discovery Tab in the SAN Administration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Softek SANView SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Notification tab in the SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Log tab in the SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Discovery Tab in the San Administration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Scheduler Tab in the San Administration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Agent tab in the SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24SNMP Traps tab in the SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . 25Archiving tab in the SAN Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Windows Shortcut for Launching the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Solaris Shortcut for Launching The Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Profiles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Softek SANView Client Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Detach Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Maximize/Minimize Arrows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Remove Agent dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Remove Device dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Failed Device Health State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Tool Tip for a Vixel 9200 Switch Device Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39The Overview window and yellow box-of-focus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48The Overview window, with yellow box-of-focus enlarged . . . . . . . . . . . . . . . . . . . . . 49Tool tip for a Brocade device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Find Device menu option and resulting dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Tool tips for a Brocade device in the Tree and Topology frames . . . . . . . . . . . . . . . . 52Options used for setting up discovery before the Server starts (discovery is attempted upon Server start) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Options used for setting up discovery during a Client session(discovery is attempted immediately) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Discover Subnets Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Setup Discovery Target dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Health States in Softek SANView Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63SAN Events frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Saving SAN Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Device Events Window for a Vixel 7100 Fibre Channel Switch . . . . . . . . . . . . . . . . . 66Saving Device Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Configuring Automatic Notification Through the SAN Administration Window . . . . . . 68Configure Thresholding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Analysis Module Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Port Configuration Analysis Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Port Link Failure Analysis Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Condition Log window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Determining the Ports to which the links are connected . . . . . . . . . . . . . . . . . . . . . . . 87Viewing the Device Window for a Brocade Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 87


Traffic Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Launching an Alternate Tool for a Brocade Device . . . . . . . . . . . . . . . . . . . . . . . . . . .89Performance Data Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Performance Data Management Delete tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Historical and Real-Time Graphing View Window . . . . . . . . . . . . . . . . . . . . . . . . . . .92WWN Zoning Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Frames in the Softek SANView Client Main Window . . . . . . . . . . . . . . . . . . . . . . . .103File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Show All Device Ports Option Has Been Selected . . . . . . . . . . . . . . . . . . . . . . . . . .105Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111GR740 Device Tool Tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123GR740 Port Tool Tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Storage Device View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Storage Device Port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128System Overview (FC-compliant HBA and Softek SANView) . . . . . . . . . . . . . . . . . .134Tool tips for an HBA, in the Tree and Topology frames . . . . . . . . . . . . . . . . . . . . . .136Back-of-Box display for a Fibre Channel HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Back-of-Box display for a PFCA HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Back-of-Box display for an SDS HBA (Virtualization) . . . . . . . . . . . . . . . . . . . . . . . .138FC HBA Port Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138PFCA HBA Port Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139SDS HBA Port Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139HBA Port Statistics View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140SAN Events frame (isolated) showing events recorded for an HBA . . . . . . . . . . . . .141

Tables

Softek SANView SAN Administration Window Buttons . . . . . . . . . . . . . . . . . . . . . . . 17Notification Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Discovery Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Scheduler Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24SNMP Trap Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Archiving Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Link Health State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Color-Independent Device Health Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Topology Frame Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Port LED Indications for Vixel Hubs and Switches . . . . . . . . . . . . . . . . . . . . . . . . . . .69Configure Thresholding Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Configure Thresholding Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Condition Log Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Log Files in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Storage Device Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • xiii

xiv

Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Arbitrated Loop Physical Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

��


1

Introduction

• What is Softek SANView? 3

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION • 1

softe

k.fu

jitsu

.com

Cha

pter

1 –

Wha

t is

Sof

tek

SA

NV

iew

?

What is Softek SANView?Softek SANView is a Storage Area Network (SAN) management software product that helps SAN administrators understand how the SAN is configured, isolate SAN problems, and monitor and manage their SAN devices through the following features:

• Automatically detects and discovers host bus adapters (HBAs) and Fibre Channel Management Integration MIB-compliant switches, hubs, routers, bridges, disks, and arrays in the SAN for management; collects and interprets management data; and allows you to launch alternate management tools (such as Telnet or Web-based tools).

• Monitors and displays the health of SAN devices and the interconnections between them.

• Enables World-Wide Name Zoning in SAN environments utilizing Brocade or Vixel devices.

• Allows creation of groups and enclosures to customize the Topology view to resemble the actual SAN environment.

• Scales easily (through its advanced architecture) to accommodate updates of Softek SANView Modules. A Softek SANView Module is a software subset that allows Softek SANView to discover, monitor, and manage specific SAN devices. Options include specialized discovery, performance, data collection and interpretation, graphical user interfaces, and launch of alternate management tools.

• Quickly troubleshoots and isolates problems through health monitoring, user-filtered event logs, performance management, analysis modules, and advanced diagnosis capabilities. These features help you quickly identify, isolate, and fix issues to keep your SAN operating reliably.

• Manages agents in-band and out-of-band to facilitate SAN management configuration, allows remote management capability, and ensures continually available management data (even if parts of the SAN transport are down).

• Proactively monitors status and detects problems at every level, and can notify administrators via email when failure-marked events occur. All events are shown in the SAN Events frame as well. The health of all SAN devices is continually monitored and displayed.

• Tracks bandwidth usage with configurable traffic threshold alerts for easy capacity planning.

• Secures both monitoring and management options through user-defined passwords, passed between Client and Server through the MD5 encryption algorithm.

• Runs on Solaris and Windows.

��


http://softek.fujitsu.com

2

Installation

• Getting Ready to Install 7

• Installing and Starting Softek SANView 9

• Installing the Softek SANView Host Agent 11

• Uninstalling Softek SANView 12

• Upgrading Softek SANView 13


softe

k.fu

jitsu

.com

Cha

pter

2 –

Get

ting

Rea

dy to

Inst

all

This chapter provides information on installing Softek SANView, as well as starting and configuring the Softek SANView Server and Client.

Getting Ready to InstallRead through this section before installing Softek SANView.

System Requirements

Requirement UNIX Windows

Operating System

• Solaris 8 (US English locale)• Solaris 7 (US English locale)

• Windows XP Professional (SP1 English)

• Windows 2000 Server (SP2 English)

• Windows 2000 Professional (SP2 English)

• Windows NT 4.0 (SP6a English, SP5 Japanese)

CPU 450 MHz 500 MHz

RAM 384 MB (for up to 256 Ports1)(Server: 256 MB, Client: 128 MB)

1.When using over 256 Ports, a general recommendation is to add 1 MB per Port added. Example: To support 512 Ports, the Server should have 512 MB of RAM. The SANView SAN configuration supports up to 1024 ports for interconnection devices, including hubs and switches.

384 MB (for up to 256 Ports1)(Server: 256 MB, Client: 128 MB)

Other • Disk space: 120-200 MB, depending on installation components• Availability of the following sockets (Ports):

- 69 (TFTP Port, for downloading firmware)- 162 (SNMP UDP Port, for receiving traps)- 1098 (RMID Port)- 6875 (UPD Port, for discovering the Host Agent)- 8181 (web/classfile server Port, used by JINI)- Dynamically allocated TCP port to communicate with the

Host Agent• System must have a CD-ROM drive, TCP/IP, and access to the

network.• For a Client installation, the system must have a screen resolution

of at least 1024 by 768.



SO

FTE

KC

hapt

er 2

– G

ettin

g R

eady

to In

stal

l

8

Prerequisites

All Components

• Ensure that DNS (Domain Name Server) is configured with the correct system name or the local hosts file can resolve the “Local host” to an IP Address. Softek SANView will not install properly if the DNS system name is not properly defined.

• Note the system’s address. Be sure to use the DNS name if the IP Address is dynamic—that is, if the address is assigned through DHCP.

• You cannot install Softek SANView unless you are logged in as Administrator (Windows) or root (Solaris). Solaris users cannot install Softek SANView while logged in under a SUDO account.

• The system on which the Client runs must have permissions set to display windows (see the documentation on the xhost command).

• Ensure that all other applications are closed prior to installing Softek SANView. Other applications may interfere with the Softek SANView installation.

• Windows users must close the Services Control Panel before the Softek SANView install or uninstall process.

• Make sure all devices are set up to communicate with your network (DNS names or IP addresses must be compatible).

Softek SANView Server

• Verify the Softek SANView Server’s IP address is correct before installing Softek SANView. An invalid IP address may cause installation issues.

• Some laptop computers cannot run Softek SANView due to bus limitations of the laptop. Therefore, the installation of SANView on a laptop is not recommended.

Softek SANView Host Agent

• If installing the Host Agent, obtain the vendor-specific libraries (see Chapter 11: Host Agent).

!CAUTION:During installation, Softek SANView 4.1 will discover previous versions of Softek SANView and will ask you if you want to remove them. If you want to keep an older version of Softek SANView on that computer, do not install Softek SANView 4.1. Softek SANView 4.1 and previous versions are incompatible and cannot reside on the same system.

Also, the old version of the database will also have to be removed before the new one is installed.


softe

k.fu

jitsu

.com

Cha

pter

2 –

Inst

allin

g an

d S

tart

ing

Sof

tek

SA

NV

iew

Installed Components

Typical installation encompasses the following:

• Softek SANView Server (including Softek SANView Modules, such as the Brocade Module and the Softek SANView V4.1 Service, which starts the Softek SANView Server)

• Softek SANView Client (which includes the online help)

• Host Agent

• User documentation. The documentation can be viewed and printed through Adobe Acrobat Reader (free copies are available at www.adobe.com)

For a list of the Softek SANView modules included in the installation, please refer to Quick Reference on page 119.

Installing and Starting Softek SANViewSoftek SANView is packaged on one CD for both Solaris and Windows operating systems.

� To install Softek SANView:

1. Insert the CD into the system’s CD-ROM drive.

- Windows: If the installation program doesn’t automatically run (as on most Windows systems), open the Windows_Installer file (.EXE file for Windows).

- Solaris: The File Manager should open a window displaying the CD contents. Double-click Solaris_Installer.bin to start the installation program.

If the File Manager does not automatically open a window, use the following shortcuts:

• cd /mnt/cdrom (the actual command may vary by system)

• ./Solaris_Installer.bin

2. Follow the displayed instructions. The default installation settings are recommended for most systems.

3. At the Choose Product Components window, select all desired components for installation. Click additional check box options if desired. (The components may be installed at a later time.)

4. At the Choose Install Folder window, select the directory in which to install Softek SANView. Once the directory is selected, all components will install to the specified directory. Ensure the directory has a minimum of 100MB of disk space available.

5. In the Verify Localhost Name window, ensure the DNS name/IP Address displayed in the text box is correct.

NOTE Softek SANView won’t be installed on Linux anymore because the Brocade API does not support Linux.



SO

FTE

KC

hapt

er 2

– In

stal

ling

and

Sta

rtin

g S

ofte

k S

AN

Vie

w

10

You may need to change the DNS name/IP address if you want the Softek SANView Client to connect to a Softek SANView Server on another system.

6. At the Choose Shortcut Folder window, select where you want to install the product icons.

7. Softek SANView 4.1 requires that a MySQL database reside on the server system. The Install Database Component dialog box appears during the installation to confirm that the installation program should install a database.

Click Yes if you want the program to install and configure a MySQL database for you.

Click No if you already have a MySQL database installed on the server system that is active and has the required tables loaded.

8. When the Pre-Install Summary window is displayed, click Install to proceed with the installation.

9. In the Enter License Information dialog box, enter the temporary license provided to you with your copy of Softek SANView. If you wish to obtain a permanent license, please contact your Fujitsu Softek representative.

The installation process is now almost complete. If the Softek SANView Server was selected for installation, the SAN Administration window appears.

10. In the SAN Administration window, click the Discovery tab to enter addresses for the devices you would like to manage.

� To enable the saved SAN configuration when Softek SANView starts:

• Click Restore persisted SAN configuration.

For more information on storing your SAN configuration, see Persisting the SAN Configuration on page 22.

If you plan to manage several devices, click the Agent tab to increase the poll interval accordingly.

Additional settings in the SAN Administration window are discussed in SAN Administration Window on page 17.

Once all desired settings have been configured, click Save Configuration and then Exit to continue with the installation.

NOTE Ensure that the DNS (Domain Name Server) is configured with the correct system name or /etc/hosts, /etc/host.equiv, and /etc/host.conf are configured for name resolution. Softek SANView will not install properly if the DNS system name is not properly defined.

NOTE You may select only one option (location) for creating the product icons.


softe

k.fu

jitsu

.com

Cha

pter

2 –

Inst

allin

g th

e S

ofte

k S

AN

Vie

w H

ost A

gent

Discovery Tab in the SAN Administration Window

11. If selected, the Host Agent and Softek SANView documentation are installed next.

12. When the installation is complete, the Install Complete window appears. Click Done to close the installation program.

Softek SANView is now installed and the Server is running.

Installing the Softek SANView Host AgentThis module (like most Softek SANView Modules) is installed automatically as part of the Softek SANView installation. It may also be installed separately as described below.

The Host Agent is a stand-alone application that manages device services. This agent should be installed on any system that contains the HBA(s). The Host Agent supports HBAs compliant with SNIA HBA API (FC HBA), Fujitsu PFCA HBAs, and the Fujitsu SDS Virtualization Agent. The Host Agent automatically determines which of these areas is applicable, and loads the appropriate proxy software. Only one proxy will be loaded on any system.

The system requirements for the Host Agent follow.

• For use with SNIA HBA API-compliant HBAs, both the driver and the vendor-specific library for each HBA must be installed. Most of the latest driver installations include this library. These components must support SNIA’s Fibre Channel HBA API Library. (Contact your HBA vendor if you need the latest library that meets these requirements.)

• Operating System:

- FC HBA: see System Requirements on page 7.

- PFCA: Prime Power.

- SDS: in conjunction with Softek Virtualization. Please refer to the Softek Virtualization 1.5.0 Administration Guide (ML-144905).

• Disk space: 20 MB (needed for installation only)

• UDP Port (default: 6875) and TCP Port (dynamically allocated at run-time)

NOTE To start the Softek SANView Client, please refer to Starting Softek SANView Client on page 31.



SO

FTE

KC

hapt

er 2

– U

nins

talli

ng S

ofte

k S

AN

Vie

w

12

� To install the Host Agent:

1. Log in to the Host Agent system as the same account that will be used to run the proxy. Installing under the Administrator account is recommended. (The shortcuts are created under the profile of the account used to install the proxy.)

2. On each system containing the FC-compliant HBA(s), Softek Virtualization, or Fujitsu PFCA HBAs, insert the Softek SANView CD, select the Host Agent, and follow the displayed instructions.

Host management is now integrated into Softek SANView management. Once the Host Agent is started and the HBAs are discovered, Softek SANView monitors the health of the HBAs.

You can stop and restart the Softek SANView Server for maintenance or for other reasons without affecting the Host Agent.

Uninstalling Softek SANViewSoftek SANView allows you to uninstall a component or the entire software package.

� To uninstall a Softek SANView component or the entire program:

1. In Windows: Choose Start > Programs > SANView_V4.1 > SVremove

In Solaris: /usr/local/bin/SANView_V4.1/SVremove

2. Select the components that you want to uninstall. You may use the selection buttons to enable all selections (All On), clear all selections (All Off).

3. Click Go.

NOTE To find out if you have Administrator privileges in Windows, log in, right-click Network Neighborhood, and select Properties. If the Change button is visible in the Identification tab, you probably have Administrator privileges. (Confirm with your system administrator.)

!CAUTION:Components are listed in a hierarchical structure so that a component can only be uninstalled if the one above it in the list has been selected. For example, to uninstall the Classes component, the Client and Server components must also be selected.

The Uninstall program will delete the current MySQL database when the Database option is selected. The MySQL database stores historical data for your SAN. Deleting this database destroys this data. You can manually back up and restore the database. For further information, please refer to Backing Up and Restoring the Database on page 145.


softe

k.fu

jitsu

.com

Cha

pter

2 –

Upg

radi

ng S

ofte

k S

AN

Vie

w

Upgrading Softek SANViewDuring installation, Softek SANView will auto-detect the current Softek SANView version on your machine. It will then ask you if you wish to remove the existing SANView version before installing the version 4.1.

If you want to keep an older version of Softek SANView on that computer, do not install Softek SANView 4.1. Softek SANView 4.1 and previous versions are incompatible and cannot reside on the same system.

For installation instructions, please refer to Installing and Starting Softek SANView on page 9.

Upgrading Softek SANView from versions prior to version 3.5

Very old versions of Softek SANView must be uninstalled before installing Softek SANView 4.1. This is because the installation of Version 3.2 and older is not compatible with the autodetection of more recent versions of SANView.

� To upgrade Softek SANView version 3.2 or older to version 4.1:

1. Uninstall the old version of Softek SANView per the instructions of that version’s User Guide.

2. Delete the install directory with a name beginning with SANView or SAN InSite.

3. Proceed with the installation of SANView 4.1 per the instructions on page 9.

��



3

Setting Up the Server

• SAN Administration Window 17

• Softek SANView’s Root Directory 27

• License Information 27

• Running the Server 28


softe

k.fu

jitsu

.com

Cha

pter

3 –

SA

N A

dmin

istr

atio

n W

indo

w

SAN Administration WindowMost configuration settings for the Softek SANView Server are entered through the SAN Administration window. This window is automatically displayed during Softek SANView installation, but you can view it any time. Softek SANView uses these settings across Server sessions (every time the Server starts).

Softek SANView SAN Administration window

Other Server configuration settings include entering a new Softek SANView license (see License Information on page 27) or changing the location of Softek SANView’s root directory (see Softek SANView’s Root Directory on page 27).

For Server configuration to take effect, the Server must be restarted. (For instructions, see Running the Server on page 28.)

� To view the SAN Administration window:

• Windows: Choose Start > Programs > SANView_V4.1 > Local_SVServer > config.

• Solaris: /usr/local/bin/SANView_V4.1/config

The buttons that line the bottom of the SAN Administration window are described here.

Each tab is explained in further detail on the following pages.

Softek SANView SAN Administration Window Buttons

Button Definition

Save Configuration Saves changes to Server configuration settings. (The Server must be restarted for settings to take effect.)

Restore defaults Displays default values for all Server configuration settings.

Exit Closes the SAN Administration window.



SO

FTE

KC

hapt

er 3

– S

AN

Adm

inis

trat

ion

Win

dow

18

Notification Tab

Softek SANView can be configured to automatically notify users via email when a SAN event of a particular severity occurs. You can also designate the severity level (Fail, Warning, Config, or Info) that triggers email notifications. For more information, see Log Tab on page 19.

Notification tab in the SAN Administration window

� To enable email notifications:

1. Click Send notifications to specified email address.

2. Type the correct parameters into the textboxes for SMTP Mail server hostname/IP address and Email address for notifications. (Double-check these parameters with your system administrator.)

The event priority at which to send email notifications is set in the Log tab.

Notification Settings

Setting Definition Default Value

Send notifications to the specified email address

When enabled (checked), Softek SANView emails notifications of events at the designated severity to the specified email account.

disabled (unchecked)

SMTP Mail server host name/IP address

Host name or IP Address of mail server (for email notifications to the specified email address).

<empty>

Email address for notifications

Email address for notifications of events.

<empty>


softe

k.fu

jitsu

.com

Cha

pter

3 –

SA

N A

dmin

istr

atio

n W

indo

w

Log Tab

The Log tab sets parameters for log files, enables you to view logs in the Windows Event Viewer, and designates which severity levels (for SAN event entries) trigger email notifications.

Log tab in the SAN Administration window

The default severity level for sending email notifications is “fail” (for Fail-marked events). Fail-marked events include loss of contact with agent, detection of duplicated IP Address, and the following health-related events:

• Bypassed; No Valid Signal; Faulty Module

• Disabled; Inoperative; Disabled

• No Media; Inoperative; Faulty Module

• No Valid Signal; Faulty Module

• Disabled; Disabled

• No Valid Signal; Faulty Module; Tx Fault



SO

FTE

KC

hapt

er 3

– S

AN

Adm

inis

trat

ion

Win

dow

20

Log Settings

Setting DefinitionDefault Value

Log rollover size (bytes) The maximum size for an event log file.* When this maximum is reached, the file’s contents are moved to filename.old, where filename is the original filename. The default value is sufficient for 20,000-35,000 event log entries. Note: Old files are overwritten when the related event log file reaches maximum size. If you want to save the old files, copy them to another directory.

5000000(5 MB)

Append new event log entries to existing log file

Specifies how event log* entries are handled when the Softek SANView Server starts (that is, in a new Server session).When enabled (checked), appends new event log entries to the existing event log file, if any.When disabled (unchecked), overwrites the existing event log file with the new event log entries.


Log SAN events to file When enabled (checked), logs SAN events* to root_dir\logs\sanevents.txt (root_dir is Softek SANView’s root directory^).


Log device events to file When enabled (checked), logs events* for each device (that tracks events) to root_dir\logs\vendor\

DeviceIP. log (vendor is the device’s vendor and IP is the device agent’s IP Address; root_dir is Softek SANView’s root directory^).


Log SAN events to Windows Event Viewer

When enabled (checked), logs SAN events* directly into the Windows Event Viewer.


Log conditions to file When enabled (checked), logs conditions reported by analysis modules to root_dir\logs\conditions.txt

(root_dir is Softek SANView’s root directory^).


Log conditions to Windows Event Viewer

When enabled (checked), logs conditions reported by analysis modules directly into the Windows Event Viewer.


* For information on Softek SANView’s event log files, see Log Files on page 115.^ For information about Softek SANView’s root directory, see Softek SANView’s Root Directory on page 27.


softe

k.fu

jitsu

.com

Cha

pter

3 –

SA

N A

dmin

istr

atio

n W

indo

w

Discovery Tab

The Discovery tab designates the device agents to be discovered when the Softek SANView Server starts. When the Softek SANView Client launches, all discovered agents are immediately displayed.

Discovery Tab in the San Administration Window

Notify administrators of all SAN events at these priority levels

Designates which severity levels (for SAN event entries) trigger email notifications. (Email notification parameters are set in the Notification tab.) Available options are:• fail• warning, fail• config, warning, fail• info, config, warning, fail

fail

Log Settings


* For information on Softek SANView’s event log files, see Log Files on page 115.^ For information about Softek SANView’s root directory, see Softek SANView’s Root Directory on page 27.



SO

FTE

KC

hapt

er 3

– S

AN

Adm

inis

trat

ion

Win

dow

22

Persisting the SAN Configuration

Softek SANView automatically saves the current SAN configuration when the Softek SANView Server system is properly shut down from a Softek SANView Client logged in with “Manage” permissions. The next time the Softek SANView Server system is started, the previous SAN configuration is reconstructed, which includes the agents, devices, Ports, and links, and the collective health status displays are updated.

� To enable the saved SAN configuration when Softek SANView starts:

• Click Restore persisted SAN configuration.

Discovering Agents

You can discover agents on the subnet of the Softek SANView Server system, on router-connected subnets, or both. The Discovery tab settings define what discovery occurs when the Softek SANView Server starts.

� To discover all agents on the Server’s subnet:

• Click Discover all agents in subnet.

� To discover agents on different (router-connected) subnets:

• Click Add and enter each IP Address. If agents cannot be added, confirm that the router is properly configured by using ping or Telnet from the Softek SANView Server system to contact the device. No reply from the device means that the router is not properly configured to communicate with the Softek SANView Server system.

� To add an agent to the agent list (titled “IP Address/DNS Host name of Agents”):

• Click Add.

� To correct an entry in the agent list (titled “IP Address/DNS Host name of Agents”):

• Click the mistaken entry and then click Edit.

� To remove an entry from the agent list (titled “IP Address/DNS Host name of Agents”):

• Click the desired entry and then click Delete.

The settings are described below.

NOTE This enables to restore the persisted SAN configuration. When your SAN configuration is ready to be saved, see Saving a Snapshot of the Topology on page 53.

Discovery Settings


Restore persisted SAN configuration

When enabled (checked), restores the last saved SAN configuration when the Softek SANView Server starts.



softe

k.fu

jitsu

.com

Cha

pter

3 –

SA

N A

dmin

istr

atio

n W

indo

w

Scheduler Tab

The Scheduler tab defines the interval for the Scheduler.

Scheduler Tab in the San Administration Window

Discover all agents in subnet

When enabled (checked), broadcasts queries to (discovers) all agents on subnet every time the Softek SANView Server starts.*


Discover agents listed below

When enabled (checked), broadcasts queries to (discovers) the agents listed within the IP Addresses of Agents list every time the Softek SANView Server starts.*


IP Address/DNS Host name of Agents

Lists agents for explicit discovery.* <empty>

* Agents that respond to Softek SANView queries are then managed by Softek SANView. All discovered agents are displayed immediately upon launch of the Softek SANView Client.

Scheduler Settings


Scheduler interval (seconds)

Amount of time in seconds that the Scheduler waits to check again for tasks (such as zoning) that need to be executed.

60

NOTE To ensure that all scheduled tasks are executed, base the Scheduler interval on the task with the lowest time measurement. For example, if one task needs to be executed every 60 seconds and the other task needs to be executed every 30 seconds, set the Scheduler interval for 30 seconds.

Discovery Settings




SO

FTE

KC

hapt

er 3

– S

AN

Adm

inis

trat

ion

Win

dow

24

Agent Tab

The Agent tab defines the interval for polling agents.

Agent tab in the SAN Administration window

� To ensure a speedy discovery and a smooth operation overall:

• Set the poll interval according to the number of devices being managed. A good rule of thumb: Add 60 seconds to the poll interval for each additional set of 20 agents you wish to monitor and manage.

You can set the poll interval in either the Softek SANView Client’s Tools menu (Set Poll Interval option) or the Agent tab of the SAN Administration window. Both methods are retained across Server sessions.

Agent Settings


Agent poll interval (seconds)

Amount of time in seconds that Softek SANView waits to check again for agent status and messages. (The poll interval can also be configured through the Client's Tools menu.)

300


softe

k.fu

jitsu

.com

Cha

pter

3 –

SA

N A

dmin

istr

atio

n W

indo

w

SNMP Traps Tab

The SNMP Traps tab determines whether the Softek SANView Server can receive traps and which Port on the Server’s system receives the traps.

SNMP Traps tab in the SAN Administration window

Traps are a useful way to get notifications when you want to poll infrequently, or when you want immediate notification for particular severities of event occurrences. When traps are configured, devices send traps to the Softek SANView Server system (or other SNMP manager on the network) when events that meet the severity level filter criteria occur.

Traps involve configuring the Softek SANView Server system to listen for traps and setting trap destinations for the desired devices.

For information on setting trap destinations for a particular device, see the vendor documentation.

SNMP Trap Settings


Enable SAN device agent trap processing (allow traps to be received)

Configures Softek SANView to listen for traps.

enabled (checked)

Receive traps on TCP/IP Port

The number of the trap-listening Port on the Server’s system.

162



SO

FTE

KC

hapt

er 3

– S

AN

Adm

inis

trat

ion

Win

dow

26

Archiving Tab

The Archiving tab enables the capture of performance data for selected devices and ports for historical purposes.

Archiving tab in the SAN Administration window

� To archive performance data:

• Click the Archive performance channel data checkbox. A check appears in the box when the feature is enabled.

Once you have enabled performance data archiving, you need to select the specific devices. You can specify the devices and ports for which you want to capture performance data in the Historical and Real-time Graphing View in Softek SANView Client. Performance data is not recorded for unselected devices and ports.

For further information on performance channel data and selecting devices, see Historical and Real-time Graphing View on page 92.

Archiving Settings


Archive performance channel data

When enabled (checked), all specified devices record their performance data in the database.


Archiving poll interval (in seconds)

Amount of time in seconds that the Archiving tool waits to check again for new performance data.

300


softe

k.fu

jitsu

.com

Cha

pter

3 –

Lic

ense

Info

rmat

ion

License InformationThe Softek SANView license entered determines the number of manageable Ports. You can display the current license or enter a new one on the Softek EnView Server.

� To view the current Softek SANView license:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> About.

• Solaris: /usr/local/bin/SANView_V4.1/about

� To enter a new or changed license:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> UpdateLicense.

• Solaris: /usr/local/bin/SANView_V4.1/UpdateLicense

Make sure you restart the Server so changes go into effect.

Softek SANView’s Root DirectorySoftek SANView’s root directory is not configured in the SAN Administration window. Softek SANView’s root directory is the designated location for SAN event log files, device event log files, device config files, and firmware image files. These files may potentially take up to 60 MegaBytes (MB) of disk space. This amount of space is usually available in the default location: install_dir\FileSystemRoot\ (where install_dir is the directory in which Softek SANView was installed). If the default location does not have adequate disk space, edit the SVserverconfig.ini file as instructed below.

� To change Softek SANView’s root directory:

1. Open the SVserverconfig.ini file (in the config subdirectory of the installation directory), locate the SIFSROOT parameter, edit as needed, and save the file. (Do not edit other parameters.)

2. Copy all subdirectories from the original root directory to the new location.

3. Enable or disable the Append new event log entries to existing log file option (in the Log tab of the SAN Administration window) as desired.

4. Restart the Softek SANView Server.

Softek SANView now saves log files, device log files, device config files, and firmware image files in the newly configured location.

NOTE When the Append new event log entries to existing log file option is enabled (checked), existing log files are kept and event entries from a new Server session are added. When this option is disabled (unchecked), Softek SANView overwrites existing log files with the new session’s entries. This option is disabled (unchecked) by default.



SO

FTE

KC

hapt

er 3

– R

unni

ng th

e S

erve

r

28

Running the Server

� To find out whether the Softek SANView Server is running:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> status.

• Solaris: /usr/local/bin/SANView_V4.1/status

� To stop the Softek SANView Server:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> stop

• Solaris: /usr/local/bin/SANView_V4.1/stop

� To start the Softek SANView Server:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> start

• Solaris: /usr/local/bin/SANView_V4.1/start

��


4

Navigating the Client

• Starting Softek SANView Client 31

• Using the Softek SANView Client 34

• Understanding the Softek SANView Client 36

• Understanding the Topology Frame 40

• Understanding the Tree Frame 49

• Understanding the SAN Events Frame 51

• Finding Devices 52

• Saving a Snapshot of the Topology 53


softe

k.fu

jitsu

.com

Cha

pter

4 –

Sta

rtin

g S

ofte

k S

AN

Vie

w C

lient

Starting Softek SANView ClientThe Softek SANView Client graphically displays updated health status of several SAN devices at a glance, tracks traffic patterns on device ports, and schedules zoning.

� To start the Softek SANView Client:

1. First make sure that the Softek SANView Server has been running for at least 30 seconds, then do the following:

• Windows: Choose Start> Programs> SANView_V4.1> SVClient.

• Solaris: /usr/local/bin/SANView_V4.1/SVclient

Windows Shortcut for Launching the Client

Solaris Shortcut for Launching The Client

2. The Client prompts you to confirm the address of the Softek SANView Server (DNS name or IP Address), then for the log-on access level, corresponding password, and user profile.

NOTE The Softek SANView Client may be connected to any server. Using a command line, add the DNS system name to the end of path. For example:Windows: c:\SANView_V4.1\bin\SVClient server.xyz.comSolaris: /opt/SANView_V4.1/SVClient server.xyz.comYou may also edit the shortcut properties and add the DNS system name to the end of the Target directory path.



SO

FTE

KC

hapt

er 4

– U

sing

Pro

files

32

3. Select the appropriate Access Level.

4. Enter the appropriate password for the specified access level in the Password text box.

The default passwords for each access level follow:

- “Monitor” : monitor

- “Manage” : manage

5. Ensure that your user profile is selected. If you need to select a profile, click Profiles. The Profiles dialog box appears.

6. Choose a profile from the list.

7. Click Save and Proceed to start the Softek SANView Client.

Using ProfilesProfiles enable you to customize the Softek SANView Client appearance for a specific individual or task. User settings such as custom groups or enclosures, manually created links, and which devices have ports expanded in the Topology frame, are saved when you exit the Softek SANView Client.

Creating a Profile

� To create a profile:

1. Select the Manage Access Level.

2. Enter the appropriate password for the specified access level in the Password text box.

3. Click Profiles. The SANView Profiles dialog box appears. The Profiles dialog box displays the currently available profiles.

NOTE Manage allows you to make changes to the SAN (software and device configuration, performance and analysis); whereas Monitor only allows you to view the current SAN configuration and settings.

NOTE To maintain a high level of security, change the default passwords the first time you log on to the Softek SANView Client (choose Tools> Change Password).

NOTE New users will need to create a profile before using Softek SANView. See Using Profiles for more information.

NOTE The use of profiles is not dependent on the login access level. When logged in under Monitor, you may select any available profile but you will not be able to create a profile.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Usi

ng P

rofil

es

Profiles Dialog Box

4. Select Default Profile from the list if you want to create a new profile using the default settings. If you want to use settings from an existing profile, select that profile.

5. Click Duplicate.

6. Select CopyOfDefault Profile from the list.

7. Click Rename.

8. Enter a name for the new profile in the Input dialog box and click OK.

9. Once you have made changes and selected a profile, click Save and Proceed to start the Softek SANView Client. If you want to return to the User Authorization dialog box, click Save and Return.

Other Profile Options

� To duplicate a profile:

• Select the profile and click Duplicate.

� To rename a profile:

• Select the profile and click Rename. Enter a name for the profile in the Input dialog box and click OK.

� To remove a profile:

• Select the profile and click Delete.

� To select a different profile:

1. Select the profile you wish to use by clicking on it once to highlight it.

2. Click Save and Proceed to start the Softek SANView Client using the desired profile.

NOTE Clicking Exit terminates the User Authorization process and prevents the Softek SANView Client from starting. To log in, you will need to restart the Softek SANView Client.



SO

FTE

KC

hapt

er 4

– U

sing

the

Sof

tek

SA

NV

iew

Clie

nt

34

Using the Softek SANView ClientThe Softek SANView Client shows agent and device health status, links, unique identification, and recorded events within its three frames.

Softek SANView Client Main Window

Device health status is updated according to the frequency (poll interval) set through Tools > Set Poll Interval.

You can reload the Tree and Topology frame to ensure that the agents and devices displayed on the Softek SANView Client match those being managed by the Softek SANView Server.

� To reload the Tree and Topology frames:

• Choose Tools > Redraw.

NOTE Selecting Redraw also returns the Topology frame to the Select and Move default cursor mode.

The Tree frame lists your devices, agents, and groups according to the selected grouping and sorting options.

The SAN Events frame dynamically updates to show you the latest 20 events.

The Topology frame lets you see your multivendor SAN connections.

The Overview window easily zooms to the required level of detail.

All frames show health status of the SAN


softe

k.fu

jitsu

.com

Cha

pter

4 –

Usi

ng th

e S

ofte

k S

AN

Vie

w C

lient

Detaching the Tree and Topology Frames

You can detach the Tree and Topology frames to isolate this information in separate windows, if desired. The Topology frame’s Map and Detail tabs may also be detached independently to allow additional viewing options.

� To detach a frame:

• Click the Detach button in the top right portion of the frame.

Detach Button

The frame now appears in a separate window, which you can minimize, maximize, or close.

� To re-attach a frame:

• Click the detached window’s close button.

Resizing the Tree and Topology Frames

You can resize the Tree and Topology frames to customize the window sizes.

� To resize a frame:

• Place the cursor on the vertical bar between the Tree and Topology frames. When the cursor changes into a directional pointer, drag the vertical bar to the left or right as desired.

� To maximize or minimize a frame:

• Use the arrows located between the two frames.

Maximize/Minimize Arrows

Use these arrows to maximize and minimize the frames.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Sof

tek

SA

NV

iew

Clie

nt

36

Understanding the Softek SANView Client

Devices and Agents

Softek SANView enables you to manage devices through their representative agents. At times, the distinction between what is a device and what is an agent may become confusing.

Device refers to an actual device (a switch, HBA, storage drive, etc.).

An agent is an interface used by a device to exchange event messages, configuration settings, and other information with management applications. All device management commands issued through Softek SANView are communicated through the device’s agent.

An agent may represent more than one device in Softek SANView.

Devices are added and removed from Softek SANView through their agents. When you want to add a device, you enter the IP address of the agent. Softek SANView searches for that agent and discovers any devices represented by that particular agent.

� To view agents in the Tree frame:

• In the Grouping box, click Agents, No Groups.

� To add an agent:

• On the Tools menu, click Discover Agent.

� To remove an agent:

1. Ensure that the Tree frame Grouping option is set to Agents, No Groups.

2. Right-click the agent and click Remove Agent on the submenu. The Remove Agent dialog box appears.

Remove Agent dialog box

3. Click Remove Agent.

� To view devices in the Tree frame:

• In the Grouping box, click Groups or No Agents, No Groups.

NOTE If you remove a device and then want to re-discover it, you must first remove the device’s agent and then re-add the agent.

NOTE As stated in the Remove Agent dialog box, removing an agent deletes the agent and all devices represented by that agent. If you do not want to remove the agent, click Cancel.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e S

ofte

k S

AN

Vie

w C

lient

� To add a device:

• On the Tools menu, click Discover Agent.

� To remove a device:

1. Right-click the device and click Remove Device on the submenu. The Remove Device dialog box appears.

Remove Device dialog box

2. Click Remove Device.

Understanding Health

Color-Coding

Health status for all managed devices and their Ports is shown in the Tree and Topology frames; health status for agents is shown in the Tree frame. Health states for the SAN and for each device, agent, and Port are color-coded in Softek SANView as follows.

NOTE Removing a device does not remove the agent associated with that device. If you want to also remove the agent, you must follow the steps to remove an agent. You may want to write down the displayed IP address to make your search for the associated agent easier.

NOTE In the Topology frame, device health states are also indicated in a color-independent fashion—by the position of the filled-in block at the bottom of the device icon. See Color-Independent Indication of Device Health on page 38.

Health State Color-Coding

Color of Icon Health State

Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Sof

tek

SA

NV

iew

Clie

nt

38

Device and Port health status is reflected in the health of the entire SAN, which is shown in the SAN title at the top of the Tree frame. If the SAN title indicates a non-functional state (yellow or red), look through the Tree and Topology frames for an agent or device in a non-functional state, and review the SAN events. A possible cause of a non-functional health state is communications failure on the link or loop segment supported by a device Port.

Links between devices also display health status. When the server detects that a link is missing, the link turns red. You may remove the link by deleting it. Manually added links do not display health status but can be deleted.

The severity of each event message in the SAN Events frame is color-coded as follows.

Color-Independent Indication of Device Health

In addition to indicating health state by color (see Understanding Health on page 37), device icons in the Topology frame also indicate health state by position of the filled-in block at the bottom of the icon. For example, a Failure health state is indicated by a filled-in block in the first (left-most) position.

Failed Device Health State

Link Health State

Color of Link Health State

Black Functional

Red Failure

Gray Unknown/Manually added link

Event Message Severities

Color of SAN Event Text Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e S

ofte

k S

AN

Vie

w C

lient

The positions of color-independent health state indications are as follows:

Tool Tips in Topology Frame

The tool tips in the Topology frame display useful information about the device icon over which the mouse pointer is placed.

Tool Tip for a Vixel 9200 Switch Device Icon

The fields displayed in these tool tips (when information is known) are listed below and on the following page. (When information is not available to Softek SANView, the value of the field is Unknown.)

Managed device:

• Vendor and Device Type

• Name (user-configured)

• Location (user-configured)

• Serial number

• Number of Ports

• Vendor (manufacturer)

Color-Independent Device Health Indications

Position of Filled-in Block in Icon (from the left) Health State

1st (left-most)

Failure

2nd

Attention

3rd (middle)

Functional

4th

Unused

5th (right-most)

Unknown



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Top

olog

y F

ram

e

40

• Model (device model, such as “Brocade 2800”)

• Agent ID (usually an IP Address)

• World-Wide Name (WWN)

• Type (of SAN device)

• Health (aggregate health status for device and enclosure)

Unmanaged device (in many cases, only the Vendor and WWN fields are populated):

• Vendor and Device Type



• Agent ID (usually an IP Address)

• World-Wide Name (WWN)

• Type (of SAN device)

• Health

Device Port:

• Port (Port number)

• Health

• Name (user configured)

• Other Ports in Zone

Understanding the Topology FrameThe Topology frame (upper-right frame) displays a layout of all the devices in the SAN, their current health state, and the status of the links connecting devices.

There are two main views in the Topology frame controlled by tabs at the top of the frame:

1. Map View (default view)

2. Detail View

Map View

The Map View displays how SAN devices are connected and the health state for each device. Each device is identified by device-type icon (such as a hub or switch icon), model number (such as “Brocade 2800”), and user-configured device name, in addition to World-Wide Name and other unique identification, which appears when the mouse pointer is placed on the icon. You can show or hide device Ports, zoom in or out, and reorganize the links. Right-clicking the device icon displays available management options.

Use the Map View to:

• Group and sort devices and agents.

• Add host and JBOD devices to enclosures.

• Launch the WWN Zoning Configuration tool.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e T

opol

ogy

Fra

me

• Manually place devices in the frame.

• Select multiple map nodes.

• Verify link locations and health status between devices.

• View health status of devices and their Ports (colorless indication is available for devices—see Color-Independent Indication of Device Health on page 38).

• View World-Wide Names and other unique identification for a device. (Place the mouse pointer on the icon.)

• Search for a device by address, name, or model number. (Choose View> Find Device, or right-click an empty area in the Topology frame.)

• Manage a device (right-click the icon.)

You may customize the Map View, if desired, in the following ways:

• Organize links (new hierarchy structure).

• Create device groups and enclosures.

• Expand a device icon to show its Ports (right-click the icon) or expand all device icons to show Ports (choose View> Device Ports).

• Zoom in or out, or fit all icons into the frame:

- Use the buttons and selections at the top of the Topology frame.

- Right-click an empty area in the Topology frame and choose View.

- To easily navigate the Topology frame, move or size the yellow box within the Overview window. (To view the Overview window, right-click an empty area in the Topology frame and choose View> Show Topology overview.)

• Show or hide the grid and/or tool tips.

Topology Frame Toolbar

At the top of the Topology frame is a toolbar with several buttons. Their functions are described below.

Topology Frame Toolbar Buttons

Toolbar Buttons Description

Zoom In buttonIncreases magnification level of the Topology frame so that more detail can be seen. Each click of the Zoom In button increases the magnification level by ten percent.

Zoom Magnificationbutton

• Zoom to Fit (Decreases or increases magnification as necessary to fit all devices in the Topology frame.)

• Zoom to 100% (Sets magnification level to 100%.)

• Select the zoom magnification using 5, 10, 25, 50, 75, 100, 150, and 200 magnification percentages.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Top

olog

y F

ram

e

42

Zoom Out buttonDecreases magnification level of the Topology frame so that more interconnections and devices can be seen. Each click of the Zoom Out button decreases the magnification level by ten percent.

Cursor Navigation button

• Select and Move (Enables you to select one or more devices and move those devices in the Topology frame. Note: You must have the Manual Placement option enabled for the main group.)

• Drag-to-Zoom (Allows you to highlight one or more devices and zoom in on their location.

• Draw Links (Creates a link between two specific devices by drawing a line from one device to another device and selecting the appropriate Ports.)

Create button• Create New Enclosure (Adds an enclosure

entity to the Topology frame.)• Create New Group (Adds a group entity to

the Topology frame. This feature is only available when Groups is selected under the Grouping drop-down.)

• Create New Link (Adds a link between one device and any other available device in the SAN.)

Layout buttonAdjusts the layout of devices in Topology frame. This feature is especially useful when the Manual Placement option is enabled.

Detach buttonOpens the Map or Detail view in its own window.

Manual Placement button

Toggling this button enables/disables the Manual Placement option for the Topology view. When enabled, devices and groups can be moved as desired within the Topology view to customize the SAN view for the user. Alternately, this feature may be enabled via the Details tab as explained in the note below.

Topology Frame Toolbar Buttons

Toolbar Buttons Description


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e T

opol

ogy

Fra

me

Creating Groups

Grouping enables you to create custom groups and place specific devices into the group. If, for example, you wanted to designate all the devices in the Accounting group, you could create an “Accounting” group and place the appropriate devices into the group.

The group’s health status is an aggregated health status based on each device in the group. If all the devices are functional, the group’s health status is functional. If one device has failed then the group’s health status displays as failed.

� To create a group:

• Click the Create button on the Topology frame toolbar and select Create New

Group. A new group box appears in the Topology frame.

� To add devices to a group:

• Select the desired devices and drag them into the group box.

• You can also add devices to a group by right-clicking on the device and selecting Move into Group> and then the appropriate group.

� To remove all devices and delete a group:

• Right-click the group and select Disband.

You can highlight a group by clicking on it. If you double-click a group icon, you can view the devices in that group.

� To view additional information on the group:

• Select the group and click the Detail tab in the Topology frame. The Group Details tab displays the information and settings for the group.

NOTE To move objects in a particular group in the Topology frame, you must enable the Manual Placement option for that specific group. To enable manual placement, use the Manual Placement button in the Topology View; or select the group name in the Tree frame, click the Details tab in the Topology frame, click the Enable Manual Placement checkbox, and then click Apply.

NOTE Groups do not display in the Topology or Tree frames unless selected as the Grouping option. To view groups, click Groups in the Grouping box above the Tree frame.

NOTE When renaming a group, keep the group name to 30 characters or less.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Top

olog

y F

ram

e

44

Creating Enclosures

Enclosures display multiple devices as one single device in the Topology frame. Enclosures are especially useful for hosts and JBODs. If a host has two HBAs then both HBAs can be placed in one enclosure to represent the host. When you view an enclosure, the connected devices within an enclosure are divided into Port bands.

The enclosure’s health status is an aggregated health status based on each device in the enclosure. If all the devices are functional, the enclosure’s health status is functional. If one device has failed then the enclosure’s health status displays as failed.

� To create an enclosure:

• Click the Create button on the Topology frame toolbar and select Create New Enclosure. A new enclosure icon appears in the Topology frame.

� To add devices to an enclosure:

• Select the desired devices and drag them onto the enclosure icon.

� To view devices inside the enclosure:

• Click the Detail tab in the Topology frame and then click the Contained Devices tab. Select the desired device from the Contained Devices drop-down box.

� To rename an enclosure:

• Select the enclosure and click the Detail tab in the Topology frame. Enter a new name in the Name text box under Labeling and Display Properties.

� To remove all devices and delete an enclosure:

• Right-click the enclosure icon and click Disband.

Creating Manual Links

You can manually create links between devices if the links are not discovered by Softek SANView. By manually adding links, you can better illustrate the true SAN environment. manual links do not display health status and appear in the Topology frame as gray links.

� To create a link:

1. Click the Create button on the Topology frame toolbar and select Create New Link. The Create User Specified Link dialog box appears.

2. Double-click the appropriate device in each Select Linking Port box to view the Ports for each device.

3. Select a device Port in each Select Linking Port box to create the link.

4. Click Create Link. A gray link appears in the Topology frame between the two device Ports you selected.

� To view the device at either end of the link:

• Right-click the link and click Go to Endpoint: <device name and IP Address>.

NOTE HBA devices are automatically added into enclosures and are grouped by Agent ID (IP Address).


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e T

opol

ogy

Fra

me

� To delete a link:

• Right-click the link and click Delete Link. You can only delete manual links and red links (links that Softek SANView shows as failed - no longer connected).

Any enclosures, groups, or links that you create are stored in your profile information. The next time you log in using your profile, the enclosures, groups, and links that you created previously will appear.

Group Path Listing

The Group Path Listing appears on the Topology frame toolbar. It displays the full group path for the selected device.

Layout

When selected, the Layout button displays the entire topology in the Topology frame. The Layout button is used primarily in conjunction with Manual Placement. If you perform a Discovery, the discovered devices may be spread all over the Topology frame. If you click Layout, the icons fall into place and the Topology frame is more organized.

� To switch the layout view of the Topology frame:

• Click the Layout button in the Map View.

Topology Frame Submenu

If you right-click the open space in the Topology frame, a submenu appears with the following options:

• Find Node

• View> Zoom to Fit/Show Overview…/Zoom In/Zoom Out

• Show Grid

• Show Tooltips.

Device Submenu

If you right-click a device icon in the Topology frame, a submenu appears with the following options:

• Show Device Ports (displays the Ports for the device)

• View Device (brings up BoB view)

• WWN Zoning (opens WWN Zoning Configuration window)

• Show Performance Statistics (opens the Traffic Performance Monitor for the device)

• Launch Alternate Tool

• Move into Group> Group names

NOTE If the deleted link does not disappear immediately, select Tools> Redraw to refresh the Topology frame.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Top

olog

y F

ram

e

46

Detail View

The Detail View displays information for a selected device, group, or enclosure. The Detail View enables you to modify information, enable/disable settings, and view additional information specific to that device.

� To display the Detail View:

• Click the device, group, or enclosure icon in the Topology frame to highlight it and then click the Detail tab.

Use the Detail View to:

• Modify device information

• Change device settings or layout properties

• View connected or contained devices (if applicable)

• Display a device’s logical view

• Store passwords for Telnet sessions on Brocade devices

� To detach the Detail view:

• Click Detach. The Detail view opens in its own window.

� To re-attach the Detail view to the Topology frame:

• Click the close (“X”) button in the top-right corner of the window.

Group Detail View

The Group Detail View displays the properties for the selected group.

• Labeling and Display Properties

Enter the name, model, and any notes you may want to record for the group.

• Layout Properties

� To change the Topology frame layout:

• Select Hierarchical or Orthogonal from the Auto Layout Scheme drop-down box.

� To enable manual placement:

• Click the Enable Manual Placement checkbox. If the option is checked (enabled), you can use the Select and Move cursor navigation to move devices around freely in the Topology frame. If the option is cleared (disabled), you can move devices around but they will immediately return to their original position once you release them.

� To update all the groups with the current settings:

• Click Apply Layout Settings to All Groups checkbox.

NOTE Interconnections are best displayed when Ports are shown, or when links are laid out in the Orthogonal view.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e T

opol

ogy

Fra

me

• Group Properties

Displays the overall health status of the group. You can also determine whether the group’s icon displays the group’s contents or not. If the option is checked (enabled), each device is represented in the group icon. If the option is cleared (disabled), the group icon is a solid block and does not display the devices inside.

After making any changes, click Apply to accept those changes.

Enclosure Detail View

The Enclosure Detail View incorporates two tabs: Properties and Contained Devices.

Properties Tab

The Properties tab enables you to add or modify general information for the device, such as the name, model, and notes.

� To restore the original labeling information:

• Click Restore Default Labeling.


Contained Devices Tab

The Contained Devices tab enables you to select a particular device in the enclosure and view additional information specific to that device. You can add or modify general information for the device. In addition, you can view the device’s health status, type, vendor name, World-Wide Name, and serial number.

� To display information for a specific device:

• Select the specific device from the Select Contained Device drop-down box.

� To change the vendor name:

• Enter the new name in the Vendor text box.

� To restore the original vendor name:

• Click Restore Default Vendor.


Device Detail View

The Device Detail View displays information for the specified device. You can make changes to certain device properties, view other devices connected to the device, and store a device management password.

Properties Tab

The Properties tab enables you to add or modify general information for the enclosure, such as the name, model, and notes.

� To restore the original labeling information:

• Click Restore Default Labeling.

The Device Properties displays the device’s health status, type, vendor name, World-Wide Name, and serial number.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Top

olog

y F

ram

e

48


Connected Devices Tab

If in Fabric mode, selecting a device displays all connected devices in a table view. If the device is an HBA, you can view the zoning status (if available).

You can select to view all the connected devices together or by Port. You can also click the Show Fabric Devices checkbox to include Fabric devices in the list.


Device Password Tab

The Device Password feature is only available for Brocade devices. You must enter the Telnet login information for the Brocade device if you want to use it with Softek SANView. Softek SANView uses the login information to establish a connection with the Brocade device and retrieve information for zoning and health status.

The Device Password feature does not change the login information on the Brocade device or allow you to bypass the Telnet login request when you launch an alternate tool.

� To enter a Telnet Password:

• Click the Set up a password for this protocol checkbox. Enter your Login Name and Password. You will have to enter your password once again to verify that the correct password has been entered. If the password you entered is an administrative password, click the checkbox.

After entering the Telnet login information, click Apply to accept the settings.

Overview Window

The Overview window displays the entire SAN, along with a yellow navigation box, which you can use to quickly focus the Topology frame on a particular area of the SAN.

The Overview window and yellow box-of-focus

The yellow box in the Overview window can be moved, sized, or even redrawn around a desired area for a more targeted focus.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e T

ree

Fra

me

The Overview window, with yellow box-of-focus enlarged

Understanding the Tree FrameThe Tree frame (upper-left frame) shows the health states of all devices, groups, and agents in the SAN. The total number of devices being managed in the SAN is shown at the top of the Tree frame. All the items may be grouped and sorted. Each device can be expanded to show the health states of its Port(s).

Use the Tree frame to:

• View health status of agents, their devices, and their Ports.

• Find out how many agents are being managed by Softek SANView.

• Group by devices, groups, or agents.

• Sort devices, groups, and agents.

• Locate an agent by IP Address.

• Center the Topology frame on the device(s) of the selected agent.

• Remove agents and their devices from Softek SANView management. (Right-click the agent icon.)

Grouping Options

You can group the devices, groups, and agents in three variations:

• No Agents, No Groups – Displays the individual device names.

• Agents, No Groups – Displays the agents for each device.

• Groups (must be selected to view groups in the Topology frame) – Displays the groups at the top of the list and any devices or enclosures that are not part of a group below. This is the default setting.

Groups display the number of devices within the group in their titles.



SO

FTE

KC

hapt

er 4

– U

nder

stan

ding

the

Tre

e F

ram

e

50

Sorting Options

You can sort the devices, groups, and agents in six variations:

• By Name

• By Health Severity

• By IP Address

• By World-Wide Name

• By Device Type

• By Vendor

You can use the grouping and sorting options together to display the list of devices, groups, and agents in several different layouts.

Tool Tips in Tree Frame

The tool tips in the Tree frame display useful information about the agent or device over which the mouse pointer is placed.

Tool tip for a Brocade device

The fields displayed in these tool tips (when information is known) are listed below. (When information is not available to Softek SANView, the value of the field is “unknown.”)

Agent

• Agent Address (usually an IP Address)

• Management Family (the Softek SANView Module being used to manage this agent)

Device


• Agent Address (usually an IP Address)



softe

k.fu

jitsu

.com

Cha

pter

4 –

Und

erst

andi

ng th

e S

AN

Eve

nts

Fra

me

Understanding the SAN Events FrameThe SAN Events frame lists the 20 most recent SAN event messages, with dynamic update and sorting capabilities. These messages reflect Softek SANView’s interpretation of changes in the SAN.

By default, the columns in the SAN Events frame display in the order listed below; you can change the order and/or sort by the desired column.

• Seq (relative sequence in which the event message was recorded)

• Date

• Time

• Severity (assigned by Softek SANView):

- Info (green)—reading of configuration file, trap enabling or disabling, improvement in device health, or indication of event storm.

- Warn (yellow)—device health decline; deletion of an agent, hub, or stack; device being reset or becoming inactive; attempt to delete a nonexistent agent; duplicate MAC addresses on agents.

- Fail (red)—change in device health to failure, duplicate IP Address detected.

- Unknown (black)—severity level of device before initialization.

• Type (device type, such as agent, hub, switch, Port, or SAN device)

• Product (vendor-specific identification that Softek SANView can decipher through the FibreChannel MIB)

• Agent (IP Address of agent)

• Device (device identifier—serial number)

• Port (Port number)

• FC (the device Port Fibre Channel Identifier or LoopID)

• Category (the event category)

• Description

The latest 1000 SAN event messages are cached for review and analysis.

� To view the SAN event messages cache:

• Choose View> SAN events.

� To save the SAN events to a file:

• Click File> Save Displayed Events to a file, enter a filename in the Name text box and click OK.

� To record event messages beyond the latest 1000:

• Choose Options> Log SAN events to file on Softek SANView Server computer or Log SAN events to Windows Event Viewer on Softek SANView Server computer.

� To print the SAN events:

• Click File> Print and select your print options. Click Print to print the current page or PrintAll to print all the pages.



SO

FTE

KC

hapt

er 4

– F

indi

ng D

evic

es

52

� To refresh the SAN events message cache:

• Click Tools> Upload new events.

For more information about SAN events, see Viewing and Logging Event Messages on page 64.

Finding Devices

Through the Find Device dialog box, you can search for a device by its agent address, user-configured name, or model number. For example, you can search for a device that is identified by one of these strings: “168.168.11.15” or “Backbone Server” or “Vixel 9200.”

The Find Device dialog box can be launched through the View> Find Device option or by right-clicking in the Topology frame and choosing Find Device from the sub-menu.

Find Device menu option and resulting dialog box

You can verify a WWN or other identifier by resting the mouse pointer over the device icon in question and reviewing the resulting tool tips.

Tool tips for a Brocade device in the Tree and Topology frames

NOTE It may take a few moments to upload the new events, and the task may be CPU-intensive.

NOTE While an agent address is usually an IP Address, Softek SANView allows for other types of agent addresses.


softe

k.fu

jitsu

.com

Cha

pter

4 –

Sav

ing

a S

naps

hot o

f the

Top

olog

y

Saving a Snapshot of the TopologyThe Save Topology Snapshot feature saves the SAN’s agents, links, discovered devices, and customized appearance at that time. By preserving the current topology configuration, you can reduce the amount of time it takes Softek SANView to return to normal operating mode after stopping the server for an extended period of time. Since there is no need to re-discover devices immediately, the Softek SANView Server resumes operations promptly.

If you save a snapshot of the topology before stopping the server, the topology will appear as it did before the server went down when you start up the Softek SANView Server. Softek SANView will then start to synchronize the existing SAN state with the current SAN configuration. If a device or link has been removed from the SAN, Softek SANView notifies you of the change by displaying the device or link in red in the Topology and Tree frames. All changes to the SAN are also captured in the SAN events log.

� To save the current topology:

• Click File> Save Topology Snapshot.

��



5

Discovery

• Discovering Agents and Devices 57

• Discovering Agents Outside the Local Subnet 58


softe

k.fu

jitsu

.com

Cha

pter

5 –

Dis

cove

ring

Age

nts

and

Dev

ices

Discovering Agents and DevicesYou can configure discovery options during a Softek SANView Client session or before the Softek SANView Server starts. Discovery during a Client session is configured through the Tools menu; discovery before the Server starts is configured through the Softek SANView SAN Administration window. Both options allow you to discover all agents on the subnet of the Softek SANView Server system and/or to specify agents for discovery by DNS name or IP Address (the agent may be on a router-connected subnet).

These options differ only in persistence; discovery settings configured in the Softek SANView Client’s Tools menu are discarded when the Softek SANView Server restarts, but settings configured in the SAN Administration window are retained across Server sessions. If you want a list of several agent addresses for discovery to be available after the Server restarts, enter the list through the SAN Administration window.

Another discovery option available only through the Softek SANView Client is the automatic discovery of agents in subnets other than the local subnet. You can initiate the Discover Subnet command through the Tools menu.

Options used for setting up discovery before the Server starts

(discovery is attempted upon Server start)

Options used for setting up discovery during a Client session

(discovery is attempted immediately)

NOTE To view the Softek SANView SAN Administration window, do the following:Windows - Choose Start>Programs>SANView_V4.1>Local_SVServer>configSolaris - /usr/local/bin/SANView_V4.1/config



SO

FTE

KC

hapt

er 5

– D

isco

verin

g A

gent

s O

utsi

de th

e Lo

cal S

ubne

t

58

The Discover all Agents in subnet option (in both the SAN Administration window and the Client) broadcasts queries to your subnet for standards-compliant SAN agents and devices. The SAN Administration window’s Discover agents listed below option adds specified devices to a persistent discovery list while the Client’s Discover Agent option targets discovery to a particular agent and its device(s).

For discovery to occur, the agent addresses (IP Addresses or DNS names) for all managed devices must be registered in at least one of the following locations:

• The Domain Name System (DNS) (check with your system administrator).

• The host name file on the Softek SANView Server system (typically located in C:\WINNT\system32\drivers\etc\Hosts [Windows] or /etc/hosts [Solaris]).

• A sample host name file is shown below:

Discovering Agents Outside the Local SubnetIn addition to discovering agents in the local subnet, you can also discover agents OUTSIDE the local subnet. This feature allows you to automatically discover agents in subnets other than the local subnet across the entire SAN.

� To discover agents outside the local subnet:

• Click File > Discover Subnets. The Discover Subnets dialog box appears.

Discover Subnets Dialog Box

� To retrieve a list of available subnets:

• Click Retrieve Subnets. This will populate the table with a list of identified subnets. This may take a few moments if a large number of subnets can be “seen” from the server system.

127.0.0.1 localhost

168.168.20.248 7200

168.168.20.71 2100

NOTE If the subnet has 4094 addresses in the Number of Addresses field and you click the Discover checkbox, a message box appears stating that the discovery process will take approximately 30 minutes to complete.


softe

k.fu

jitsu

.com

Cha

pter

5 –

Dis

cove

ring

Age

nts

Out

side

the

Loca

l Sub

net

� To discover a subnet from the list:

• Click the Discover checkbox for the appropriate subnet. A check appears in the box. Click Start Discovery to begin the discovery process.

The Agent Control Status Monitor displays the Agent address and Contact status for each IP address it attempts to locate. The Contact status displays the current state for the specific IP address: either “Attempting to add” or “Unable to add”. If an agent is successfully added then it is removed from the list.

� To add a known host or subnet:

1. Click Add. The Setup Discovery Target dialog box appears.

Setup Discovery Target dialog box

2. Select to add either a Subnet or Host from the Type drop-down box.

3. Enter the IP Address on which to base the discovery. A subnet address must end with "0".

4. If you need to change the subnet mask, select the appropriate setting from the Mask drop-down box.

5. Enter the starting IP Address in the Start address text box.

6. Enter the ending IP Address in the Stop address text box.

7. Click Add to add the subnet address or host to the discovery table.

8. Click the Discover checkbox for the appropriate subnet. A check appears in the box.

9. Click Start Discovery to begin the discovery process.

� To remove a subnet address or host from the discovery table:

• Click the appropriate subnet or host once to highlight it. Click Remove to delete the selected subnet address or host.

You can delete multiple subnet addresses or hosts. Select the desired subnets or hosts and click Remove.

� To clear out the entire discovery table:

• Click Clear.



SO

FTE

KC

hapt

er 5

– D

isco

verin

g A

gent

s O

utsi

de th

e Lo

cal S

ubne

t

60


• Set the poll interval according to the number of devices being managed. We recommend that the poll interval be set to 5 minutes for up to 40 devices, then add 1minute to the poll interval for each additional set of 20 devices you wish to monitor and manage.


The time needed for the discovery process depends on the following factors:

• Number of agents on the network.

• Poll interval—the frequency of Softek SANView Server requests for management data from device agents.

• Registration of agents in either the Domain Name System (DNS) or the system’s host name file.

• Amount of traffic on the network.

• Available RAM (memory) and CPU (processing power) on the Softek SANView Server system.

��


6

Monitoring the SAN

• Checking Health Status 63

• Viewing and Logging Event Messages 64

• Setting Up Email Notification 67

• Interpreting Device Port LEDs 69

• Configuring Thresholds 70

• Troubleshooting 76

• Configuring Analysis Modules 78


softe

k.fu

jitsu

.com

Cha

pter

6 –

Che

ckin

g H

ealth

Sta

tus

Monitoring storage area networks (SANs) involves checking health status, reviewing events, setting up email notification, interpreting device Port LEDs, and configuring thresholds.

Troubleshooting SAN issues involves isolating the problem, checking event messages, tracking traffic patterns, checking switch error statistics, and using the analysis modules.

Checking Health Status

Device health is a combination of its device-specific information (such as device enclosures and Port health) and the links that the device supports. Health status is color-coded and is indicated by textual tool tips. (For more information on color-coding, see Understanding Health on page 37.)

The overall SAN health is reflected in the SAN group title at the top of the Tree frame. If any health state is other than functional, you can view the status of the related agent, device, or device Port through the Tree frame, or you can view the device window by double-clicking the desired device in the Topology frame.

Health States in Softek SANView Client

If agent contact is lost (that is, Softek SANView does not receive an agent response within a certain amount of time), Softek SANView displays a message in the SAN Events frame to notify you, and the health state of the agent, device, and device Ports becomes unknown. Softek SANView continues to poll the agent and displays its health status when the agent responds.

The amount of time Softek SANView waits before displaying a message and changing the health status is dependent upon the selected poll interval. A 5-minute poll interval translates into approximately 12 minutes of no-response time (based on two poll intervals).

NOTE An agent is an interface used by a device to exchange event messages, configuration settings, and other information with management applications. All device management commands issued through Softek SANView are communicated through the device’s agent.

...of each agent, device, and Port(s)

...of each device and its Ports

...each event message

...of the entire SAN

Health at a glance...



SO

FTE

KC

hapt

er 6

– V

iew

ing

and

Logg

ing

Eve

nt M

essa

ges

64

Viewing and Logging Event MessagesSoftek SANView monitors and interprets changes in the SAN and records an event message when a change occurs. The latest 1000 SAN event messages are cached for review and analysis.

� To view this cache:

• Choose SAN events from the View menu.

� To record event messages beyond the latest 1000:

• Choose either Options > Log SAN events to file on SANView Server computer or Log SAN events to Windows Event Viewer on SANView Server computer from the main window. The most recent 20 events are displayed in the Softek SANView Client’s SAN Events frame (lower frame) with dynamic update.

Device events are messages generated by device agents. These events are viewed (for supported devices) through the appropriate menu option in the related device window. You can also choose to log device events to a file, if desired.

In addition to health changes and device configurations, SAN event messages indicate situations that are not recorded by devices, such as causes of a loop-down condition or a power-off or removal of a managed device.

Understanding SAN Events

The SAN Events frame is the lower frame in Softek SANView’s main window. This frame displays the latest 20 SAN events, dynamically updated. The SAN events can be saved, printed, and/or continuously logged to a file on the Softek SANView Server system.

SAN Events frame

You can sort SAN events by column to focus on the desired dates, severities, and/or descriptions, so that you can learn more about recurrent problems, pinpoint device responsibility, or establish trends. For example, you can better understand a recurrent problem if you sort the events by description, or you can find out whether one agent is responsible for most SAN events if you sort the events by agent.

� To continuously log the SAN events (beyond the latest 1000):

• Choose Options > Log SAN events to file on Softek SANView Server computer or Log SAN events to Windows Event Viewer on SANView Server computer from the main window.

NOTE For more information on the columns shown in the SAN Events frame, see Log Files on page 115.


softe

k.fu

jitsu

.com

Cha

pter

6 –

Vie

win

g an

d Lo

ggin

g E

vent

Mes

sage

s

The SAN event log file (named sanevents.txt) is saved to:

- Windows: C:\SANView_V4.1\FileSystemRoot\logs\

- Solaris: /opt/SANView_V4.1/FileSystemRoot/logs/

When the file reaches its maximum size, its contents are moved to sanevents.txt.old to make room for continued logging of messages. (The default maximum file size is 5 MB, or approximately 35,000 SAN Event entries.)

� To view the cache of the latest 1000 SAN events:

• Choose View> SAN events. This display is static; to update the display, choose Tools> Upload new events.

� To save the displayed SAN events:

• Choose View> SAN events and choose the desired option from the File menu of the resulting window. The file can be named as desired (with no embedded spaces), but it must be saved to the location specified above.

Saving SAN Events

� To print the SAN events:

• Click File > Print and select your print options. Click Print to print the current page or PrintAll to print all the pages.

Understanding De vice Events

Device events can be accessed through the appropriate menu of the device window. The device events can be saved, printed, and/or continuously logged to a file on the Softek SANView Server system. (Note that content of these messages is determined by the device vendor.)

NOTE Files are located on the Softek SANView Server system. The listed locations assume that the default installation directory for Softek SANView was accepted and that Softek SANView’s Root Directory parameter is unchanged. (By default, Softek SANView’s Root Directory is named “FileSystemRoot” and is placed inside the accepted installation directory.)

NOTE Vixel switches have the option to restrict event logs to a minimum severity level. To change this setting, open the switch window and choose Tools> Configure Switch, then click the Logging tab.



SO

FTE

KC

hapt

er 6

– V

iew

ing

and

Logg

ing

Eve

nt M

essa

ges

66

Device Events Window for a Vixel 7100 Fibre Channel Switch

� To continuously log device events:

• Choose Options> Log Device events to file on Softek SANView Server computer from the main window.

Each agent-specific device log file is named DeviceIP.txt (where IP is the device agent’s IP Address) and is saved to the appropriate vendor directory in:



When the file reaches its maximum size, its contents are moved to DeviceIP.log.old to make room for continued logging of messages. (The default maximum file size is 5 MB, or approximately 20,000 Device Event entries.)

� To print or save the displayed device events:

• Choose the desired option from the File menu of the Device Events window. The file can be named as desired (with no embedded spaces), but it must be saved to the location specified above.



softe

k.fu

jitsu

.com

Cha

pter

6 –

Set

ting

Up

Em

ail N

otifi

catio

n

Saving Device Events

Setting Up Email NotificationSoftek SANView gives you peace of mind by automatically notifying you via email when a failure-marked event (or event of specified severities) occurs.

The email address, email server address, and desired severities for triggering notification are set up through the Softek SANView SAN Administration window.

� To view the SAN Administration window (on the Softek SANView Server system):



The email information for automatic notification is entered in the Notification tab; the severity (priority level) for triggering events is selected in the Log tab.



SO

FTE

KC

hapt

er 6

– S

ettin

g U

p E

mai

l Not

ifica

tion

68

Configuring Automatic Notification Through the SAN Administration Window

In the Notification tab, enter your email address and the mail server identification.

In the Log tab, select the desired event severity for triggering notification.


softe

k.fu

jitsu

.com

Cha

pter

6 –

Inte

rpre

ting

Dev

ice

Por

t LE

Ds

Interpreting Device Port LEDs

Many devices have green and amber (yellow) LEDs on each Port to indicate module and Port health. The green LED indicates module presence and health while the yellow LED indicates whether the Port is participating in the data flow. The Port LED indications for Vixel hubs and switches are provided below for your information.

NOTE When rebooted, some vendor’s devices use their Port LEDs to indicate results of the power-on self test (POST). The Port LEDs indicate health after the test is complete. For more information about the device’s POST, see the device documentation.

Port LED Indications for Vixel Hubs and Switches

Port LED Appearance Health Indication (Vixel Hubs and Switches)

green unlit;yellow unlit

No module (SFP or GBIC) inserted.

green unlit;yellow lit

Port is bypassed; the module may have a transmitter (Tx) fault.

green lit;yellow unlit

Module is inserted and good; communication is established.

green lit;yellow lit

For switches: Module is inserted and good, but no link is established.For hubs: Module is inserted and good, but the Port is bypassed because one of the following events has occurred:• Loss of signal amplitude from the device (RX-

LOS).• Receipt of invalid Fibre Channel command

characters (K28.5).• Improper initialization of an attached node (as

indicated by the node’s streaming LIP(F8) primitives).

• No response from the attached node when hub sent a LIP(F7) primitive.

green blinking;yellow blinking

Port has been set to “beaconed” through Softek SANView or another management tool.

blinking yellow Port LED

Port is being manually controlled (for example, taken off-line or beaconed) through Softek SANView or another management tool.

For switches: A steadily blinking green LED (lit for 1/2 second, unlit for 1/2 second) and solid yellow LED combination indicate that the Port is attempting to bring the link up and establish protocol connection with a device. (This information does not apply to Vixel 8100.)



SO

FTE

KC

hapt

er 6

– C

onfig

urin

g T

hres

hold

s

70

Softek SANView extends this Port legend to its graphical user interface, so you can understand the SAN health status at a glance.

Configuring ThresholdsSetting thresholds provides another option to monitoring your SAN performance. You can set threshold parameters to monitor devices, like hubs, switches, and HBAs.

Configure Thresholding dialog box

Each device has a specific set of statistics for creating thresholds. Example statistics include Link Failure, Loss of Signal, MBytes per Second Received, MBytes per Second Transmitted. For descriptions of some of the available statistics, see Statistic Descriptions on page 72.

Other configurable options include:

flickering green Port LED

Port is active; traffic is going through the Port. (This information does not apply to Vixel 8100 or Vixel 2100.)

Configure Thresholding Settings

Threshold Options Descriptions

Active Port on Selected Device Displays the active Ports for the selected devices.

Threshold Value When the statistic value exceeds this value, a warning is issued if the other parameters warrant it. This value is based on the selected statistic.

Port LED Indications for Vixel Hubs and Switches

Port LED Appearance Health Indication (Vixel Hubs and Switches)

For switches: A steadily blinking green LED (lit for 1/2 second, unlit for 1/2 second) and solid yellow LED combination indicate that the Port is attempting to bring the link up and establish protocol connection with a device. (This information does not apply to Vixel 8100.)


softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Thr

esho

lds

� To configure thresholding for a device:

1. Select a device from the Device drop-down box.

2. Select a statistic parameter to use from the Statistic drop-down box.

3. Select a Port number in the Active Port on Selected Device box.

4. Enter a threshold value.

5. Select the threshold poll interval in second or minutes.

6. Enter the tolerance level based on the number of occurrences or time (in seconds or minutes).

7. Enter a rearm value.

8. Select the Launch Command check box and choose a command from the drop-down box, if you want to launch a command when a threshold parameter is exceeded. For more information on launching commands, see Commands on page 72

9. The Send email check box is selected by default. If you do not want to receive email notifications, clear the checkbox by clicking it. The email address is assigned in the Softek SANView SAN Administration window.

10. Click Start Now to start the thresholding session. Once the threshold session is running, the Stop Now button is available. If you need to stop a running threshold session, highlight the threshold session in the Currently Running Threshold Sessions table and click Stop Now.

Threshold Poll Interval The number of seconds or minutes between threshold polling intervals.

Tolerance The number of occurrences or time above a threshold value before a condition report is created.

Rearm Once a statistic value falls below the rearm value, the exceeded threshold is cleared and the number of tolerances is reset.

Launch Command Enables administrators to add custom scripts and programs to retrieve additional information or perform an action when a threshold is exceeded. All programs and scripts are executed on the server machine.

Send Email When a threshold has been exceeded., an email notification is sent to the email account provided under the Notification tab in the SAN Administration window.

NOTE The Condition Log and Condition Report are also used for indicating when a threshold has been exceeded. For more information, see Condition Log Window on page 82 and Condition Reports on page 84.

Configure Thresholding Settings

Threshold Options Descriptions



SO

FTE

KC

hapt

er 6

– C

onfig

urin

g T

hres

hold

s

72

Commands

The Launch Command option allows you to run specified scripts or programs when a threshold parameter is exceeded.

� To use custom scripts or programs in the Launch Command:

• Place your script or program in the appropriate directory:

- Windows: C:\SANView_V4.1\FileSystemRoot\execution_commands\

- Solaris: /opt/SANView_V4.1/FileSystemRoot/execution_commands/

When you start the Softek SANView Client and go to the Configure Thresholding dialog box, your scripts or programs will be available under the Launch Command drop-down box.

Statistic Descriptions

The following table describes the statistics available in the Configure Thresholding dialog box.

NOTE If no files are present in the "execution_command" directory, the Launch Command feature is disabled. Softek SANView includes sample commands for each operating system.

Configure Thresholding Statistics

Statistic Description

4-Byte Words Received The number of 4-byte words that are received.

4-Byte Words Transmitted The number of 4-byte words that are transmitted.

Active Devices The total number of active devices.

Answer PRLI Probe Devices The number of devices that answered the PRLI probe.

Average The average Port utilization rate.

Class 2 Discards Frames The number of Class 2 frames discarded by this FxPort.

Class 2 F_BSY Frames The number of F_BSY frames generated by this FxPort against Class 2 frames.

Class 2 F_RJT Frames The number of F_RJT frames generated by this FxPort against Class 2 frames.

Class 2 In Frames The number of Class 2 frames received by this FxPort from its attached NxPort.

Class 2 Out Frames The number of Class 2 frames delivered through this FxPort to its attached NxPort.

Class 3 Frames Discarded The number of Class 3 frames that were discarded.

Class 3 In Frames The number of Class 3 frames received by this FxPort from its attached NxPort.

Class 3 Out Frames The number of Class 3 frames delivered through this FxPort to its attached NxPort.


softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Thr

esho

lds

Dumped Frames The number of frames dumped due to a lack of host buffers available.

Encoding Errors Inside of Frames The number of encoding error within frames.

Encoding Errors Outside of Frames The number of encoding errors outside of frames.

Error Frames The number of frames received in error.

Frames with Bad End-Of-Frame The number of frames with EOF errors.

Genl Stat Receive ABTS Count The number of Abort Sequences received.

Genl Stat Receive FCP Command Count

The number of Fibre Channel Protocol commands received.

High The maximum Port utilization rate.

Input Discard Packets The number of discarded packets received.

Input Good Packets The number of successful packets received.

Input Packets The total number of incoming packets.

Invalid CRC Count The number of frames received with invalid CRC.

Invalid Transmission Word Count The number of invalid transmitted words.

Last LIP Received The actual LIP received.

Link Control Frames Received The number of link control frame that are received.

Link Failure Count The number of Link failures that have occurred.

Link Resets Received Count The number of Link Resets received.

Link Resets Transmitted Count The number of Link Resets transmitted.

Link Timeout Count The number of Link Timeouts that have occurred.

LIP Count The number of LIP events that have occurred on an Arbitrated Loop.

LIPs In The number of LIPs that were received.

LIPs Out The number of LIPs that were transmitted.

Loop Connection Timeout Count The number of Loop Connection Timeouts that have occurred.

Loss of Receive Clock Count The number of Receive Clocks lost.

Loss of Signal Count The number of times Loss of Signal has occurred.

Loss of Synchronization Count The number of times Loss of Sync has occurred.

Low The minimum Port utilization rate.

MBytes Per Sec Rx The number of megabytes/second received.

MBytes Per Sec Tx The number of megabytes/second transmitted.

Multicast Frames Received The number of multicast frames that are received.





SO

FTE

KC

hapt

er 6

– C

onfig

urin

g T

hres

hold

s

74

Multicast Frames Transmitted The number of multicast frames that are transmitted.

Multicast Timeouts The number of multicast frames that are timed out.

NOS Count The number of NOS events that have occurred on the switched Fabric.

OLS Received Count The number of OLS Received.

OLS Transmitted Count The number of OLS Transmitted.

Port Number The identification number of the Port on the HBA.

Primitive Sequence Error Count The number of Primitive Sequence errors that have occurred.

Primitive Sequence Protocol Err Count

The number of Primitive Sequence Protocol errors that have occurred.

Receive CRC Error Count The number of receive CRC errors on link that have occurred.

Receive FIFO Overrun Count The number of Receive FIFO Overrun.

Receive Frame Too Short Count The number of Receive Frames that are too short.

Received Frame Too Long Count The number of Received Frames that are too long.

Received Missing Delimiter Count The number of missing delimiters that are received.

Received a CLS in Response to an Open Request Error Count

Received a CLS in response to an Open Request Error count.

Response Time Vector The response time vector.

Rx Frames The number of total received FC frames across all protocols and classes.

Rx Words The number of total received FC words across all protocols and classes.

Seconds Since Last Reset The number of seconds since the last time this Port was reset.

Self Register FC4 Devices The number of devices that self-register their FC4 type.

Sent a CLS in Response to an Open Request Error Count

Sent a CLS in response to an Open Request Error count.

Time BB Credit Zeroa The model of buffer-to-buffer flow control used. The regular is between N and F ports; the alternate is between FL and NL ports.

Time R_RDY High Prioritya For Class 2 and Class 2 Data and Link Control Frames: it indicates that the interface buffer receiving the frame is ready for further reception.




softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Thr

esho

lds

Transmit CRC Error Count The number of transmitted CRC errors on link that have occurred.

Transmit FIFO Underrun Count The number of Transmit FIFO Underruns.

Transmit Missing Delimiter Count The number of missing delimiters that are transmitted.

Transmit Parity Error Count The number of parity errors that are transmitted.

Transmit Tag Error Count The number of tag errors that are transmitted.

Tx Frames The number of total transmitted FC frames across all protocols and classes.

Tx Words The number of total transmitted FC words across all protocols and classes.

a.The sending N_Port or F_Port shall not transmit a Class 2, Class 3, or Class 1/SOFc1 frame unless the allocated BB_Credit is greater than zero and the BB_Credit_CNT is less than the current BB_Credit. To avoid possible overrun at the receiver, each port manages BB_Credit_CNT less than BB_Credit. Further, each port sets BB_Credit_CNT value to Zero at the end of Fabric logon or Fabric re-login. Each port increments BB_Credit_CNT by one for each Class 2, Class 3, or Class 1/SOFc1 frame transmitted. Each port decrements BB_Credit_CNT by one for each Class 2, Class 3, or Class 1/SOFc1 frame received. Each port issues an R_RDY for each Class 2, Class 3, or Class 1/SOFc1.





SO

FTE

KC

hapt

er 6

– T

roub

lesh

ootin

g

76

Troubleshooting This section covers both SAN troubleshooting and application issues (Softek SANView Server and Client).

Troubleshooting your SAN with Softek SANView

The first step in troubleshooting is to isolate the issue to a device or connection. Look for non-functional health (indicated by red or yellow; also indicated by textual tool tips) in the following areas:

• SAN, agents, devices, and device Ports in the Tree frame.

• Event messages for devices and for the SAN in the SAN Events frame.

• Enclosure status in the device window (where available).

Following are some other areas to check when isolating or troubleshooting issues.

• SAN: Data communication is slow

Look for unusual traffic trends in the Port performance gauges for the device (available for Vixel hubs and switches). You may want to log traffic over a period of time to track these trends, or set a traffic threshold for alert messages. If traffic is continually high and/or streaming traffic (such as back-ups) are continually interrupted by bursty traffic, zoning may help isolate Ports and lighten the traffic load. If traffic continually meets maximum throughput, the network may need a higher-bandwidth SAN device or a network reconfiguration to balance the load.

• Device communication: One of the SAN devices does not seem to be communicating with the network

If a previously discovered device is not shown in the Softek SANView Client, go to a command line prompt on the Softek SANView Server system (the system on which the Server was installed) and use the Packet InterNet Groper (PING) program to send an Internet Control Message Protocol (ICMP) echo request. (Type ping IPAddress from a command line prompt on a system that has access to the network.) If no reply is received, the device is not communicating with the network. Check the device connections.

• Switches: For some reason, the switch health state is not functional

In the Switch window, check the Port status (double-click a Port for more information). From the View menu, check Port Link Statistics, Frame Link Statistics, and Device Events. (For more information on these statistics, see the module or vendor documentation.) Also make sure that all connected devices are shown in the SNS Table and that the other switches shown in the routing table (RIP or FSPF) are functional.

Softek SANView Issues

Following are some areas to check when having issues with the Server or Client.

• The Server seems to be overloaded and/or data communication is slow.

Check for high amounts of polling activity. You can decrease activity through:

- Increasing the Poll Interval (choose Tools> Set Poll Interval).


softe

k.fu

jitsu

.com

Cha

pter

6 –

Tro

uble

shoo

ting

- Reducing the number of managed devices.

• The Server does not start, or an error message appears at Client launch indicating that Server is not available.

Check the Server status. Is it running? If so, be sure to let the Server run for a minute or two (longer if discovering several device agents) before starting the Client. If the Server is not running, look at the SIServer.out or SIServer.err files in the bin directory; the default location is:

- Windows: C:\SANView_V4.1\bin\

- Solaris: /opt/SANView_V4.1/bin/

Possible reasons for a non-starting Server include an expired license or a license that can’t be found. If one of these situations occurs (as confirmed by the SVPro.out or SVPro.err file), reenter your license and restart the Server.

Another reason for the Server not starting could be a change of the Server system’s IP Address since installation. To prevent this situation, re-install Softek SANView using the Server system’s DNS name (instead of IP Address).

� To enter a new or changed license (on the Softek SANView Server system):

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> UpdateLicense.


If the license is not an issue, try stopping and re-starting the Server.

• LAN: Data collection is slow and/or health changes intermittently between green and red

User data may have risen, causing Ethernet collisions and missed poll intervals (cycles) for gathering device data.

• The Run Softek SANView Client menu option on Windows was executed, but now the initial “Server Specification” window isn’t visible

The Server Specification window could be covered up by other windows. (The Server Specification window isn’t iconified, so it does not appear on the task bar.) Minimize all active windows, one by one, until you see the Server Specification window. In addition, you may use the Show Desktop shortcut, which minimizes all windows; if this shortcut is used, the Server Specification window display when you press the Alt and Tab keys simultaneously.

• Softek SANView Client: Text is hard to read

Set up your screen for optimal color usage; for example, 65536 colors instead of 256 colors. (On Windows, choose Start> Settings> Control Panel> Display> Settings tab> Color Palette.)

NOTE To ensure a speedy discovery and a smooth operation overall, set the poll interval according to the number of devices being managed. We recommend that the poll interval be set to 5 minutes for up to 40 devices, then add 1minute to the poll interval for each additional set of 10 devices you wish to monitor and manage.



SO

FTE

KC

hapt

er 6

– C

onfig

urin

g A

naly

sis

Mod

ules

78

Configuring Analysis ModulesAnalysis modules provide information to users to assist in the resolution of SAN performance or device configuration issues. Once configured, the analysis modules gather data on the specified devices and warn users when issues arise or thresholds have been exceeded. You can customize the threshold settings to fit your specific needs in your SAN environment.

Analysis modules can be activated or deactivated at any time. When an analysis module is activated, it monitors the specified device. If a problem is detected, the analysis module creates an entry in the Softek SANView Condition Log. The Condition Log entry is a condition report that describes the problem, lists supporting data, and provides suggestions on how to resolve the problem. You can configure the analysis modules to also send you email notification when a condition report is generated.

The analysis modules control the status of a condition report. Once the condition report is issued, the status is set to Unresolved. The analysis module continues to monitor the device’s status. After you correct the problem, the analysis module will detect any changes to the device’s status on the next poll interval. If the problem has been corrected, the analysis module will change the status of the condition report to resolved.

� To configure the analysis modules:

• Click Tools> Analysis Module Configuration. The Analysis Module Configuration tool appears.

Analysis Module Configuration window

The Analysis Module Configuration tool enables you to view the analysis modules by device or by analysis module.

Analysis modules shown in green are running and analysis modules shown in red are stopped.

NOTE Under Device view, devices shown in red do not have analysis modules available for them.


softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Ana

lysi

s M

odul

es

There are two analysis modules in Softek SANView:

1. Port Configuration Analysis Module

2. Detect Port Link Failures Analysis Module - Device-specific

Port Configuration Analysis Module

The Port Configuration analysis module detects when a configured Port on one device cannot communicate with a configured Port on another device. This problem occurs when incompatible device Port types are connected between two devices.

Softek SANView informs users of incompatible Port types through the condition report, which is accessed through View> Condition log. The condition reports displays a description of the problem, provides additional information if it is available, and lists acceptable Port types for the transceiver.

� To configure the Port Configuration analysis module:

1. Select the desired device and click PortConfigAM under the device name.

Port Configuration Analysis Module

2. Set the Poll Interval for the analysis module.

This setting determines how much activity is being performed on the Softek SANView Server. The more frequently the data is retrieved, the higher the Softek SANView Server performance load. The default poll interval is 1 minute and can range from 1 minute to 24 hours.

3. If you want to receive email notification when a condition occurs, ensure that the Send email notification when a condition is detected checkbox is selected.

NOTE All conditions are automatically reported in the Condition Log table.



SO

FTE

KC

hapt

er 6

– C

onfig

urin

g A

naly

sis

Mod

ules

80

When a condition occurs, an email is sent to the email address assigned in the Softek SANView SAN Administration window.

4. Select the Launch command on new condition checkbox if you want to run specified scripts or programs when a condition occurs.



• Windows: C:\SANView_V4.1\FileSystemRoot\execution_commands\

• Solaris: /opt/SANView_V4.1/FileSystemRoot/execution_commands/

When you start the Softek SANView Client, your scripts or programs will be available under the Launch Command drop-down box.

Select a command from the Command drop-down box. When a condition occurs, the analysis module will run the command.

5. To start the analysis module, click Start Now.

Once the analysis module is running, the Stop Now button becomes available.

� To stop a running analysis module:

• Click Stop Now.

� To restore the original analysis module configuration settings:

• Click Reset Defaults.

Detect Port Link Fail ures Analysis Module

The Detect Port Link Failures Analysis Module detects if a Port is experiencing errors and identifies isolated Ports, which occur due to Fabric incompatibilities during principal switch negotiation or WWN Zoning configuration.

� To configure the Detect Port Link Failures analysis module:

1. Select the desired device and click PortLinkFailureAM for that device.



softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Ana

lysi

s M

odul

es

Port Link Failure Analysis Module

2. Set the Poll Interval for the analysis module.

This setting determines how much activity is being performed on the Softek SANView Server. The more frequently the data is retrieved, the higher the Softek SANView Server performance load. The default poll interval is 1 minute and can range from 1 minute to 24 hours.

3. If you want to receive email notification when a condition occurs, ensure that the Send email notification when a condition is detected checkbox is selected.

When a condition occurs, an email is sent to the email address assigned in the Softek SANView SAN Administration window.

4. Select the Launch command on new condition checkbox if you want to run specified scripts or programs when a condition occurs.



• Windows: C:\SANView_V4.1\FileSystemRoot\execution_commands\

• Solaris: /opt/SANView_V4.1/FileSystemRoot/execution_commands/

When you start the Softek SANView Client, your scripts or programs will be available under the Launch Command drop-down box.

• Select a command from the Command drop-down box. When a condition occurs, the analysis module will run the command.

NOTE All conditions are automatically reported in the Condition Log table.




SO

FTE

KC

hapt

er 6

– C

onfig

urin

g A

naly

sis

Mod

ules

82

5. Set the threshold values for the number of link errors, the number of loss of syncs, and the number of loss of signals that may occur before an alert is sent.

6. To start the analysis module, click Start Now.

Once the analysis module is running, the Stop Now button is available.

� To stop a running analysis module:

• Click Stop Now.

� To restore the original analysis module configuration settings:

• Click Reset Defaults.

Condition Log Window

The Condition Log frame window condition report entries based on information from the analysis modules. Condition report entries are created and managed by the analysis modules. Each entry has an associated condition report.

Condition Log window

Viewing the Condition Log

The condition log table has the following columns: Condition Log Table

Column Title Description

Condition ID A unique identifier for each condition report.

Date The date on which the condition log entry was created or last updated.

Time The time of day during which the condition log entry was created or last updated.

Severity The severity of the condition report:fail (red), warning (yellow), info (green), and config (blue).

Status Displays the current state of the condition report:resolved/closed, unresolved/open, re-occurring/intermittent


softe

k.fu

jitsu

.com

Cha

pter

6 –

Con

figur

ing

Ana

lysi

s M

odul

es

You can sort the columns, select/highlight entries, and scroll down pages of condition reports that are color-coded to the severity level.

� To view the full condition report:

• Double-click the desired condition log entry to display the condition report.

� To update the condition log entries:

• Click Tools> Upload new conditions. The condition log table displays the latest list of conditions that the Softek SANView Server has detected.

� To print or save the disp layed condition log entries:

• Choose the desired option from the File menu of the Condition Log frame. The file can be named as desired (with no embedded spaces), but it must be saved to the specified location.

You can delete conditions if they have been resolved or are older than a certain date.

� To delete conditions:

• Click Tools> Delete conditions. Select whether you want to delete all resolved conditions or conditions older than a date that you may specify.

� To hide resolved conditions in the table:

• Click Tools> Hide resolved conditions. If you wish to view the resolved conditions at a later date, click Tools> Show resolved conditions and the resolved conditions will appear.

Acknowledged

Indicates if someone is reviewing the condition report. Each condition report has a checkbox to signify that the condition report is being addressed. There is also an Annotations section to allow users to enter comments.

Title Displays the condition report title and relevant device information (if available).

NOTE Condition report status is controlled by the analysis modules. If an analysis module determines that a problem has been resolved, the analysis module will update the condition report status to resolved.

NOTE If you have sorted the data, any new entries in the Condition Log frame will cause the table to revert back to the default date/time sorting criteria. The new condition report entry appears at the top of the table.

Condition Log Table

Column Title Description



SO

FTE

KC

hapt

er 6

– C

onfig

urin

g A

naly

sis

Mod

ules

84

Condition Reports

A condition report provides more detailed information for the associated entry in the condition log table. The condition report displays the report title, condition severity and status, the timestamp for when the condition was reported, and the condition ID. The report also provides a description of the problem, any supporting data that is available, and suggestions for how to correct the problem.

Each condition report includes an acknowledge option. By acknowledging a condition report, you can alert other users that someone is reviewing the problem. To acknowledge a condition report, click the Condition acknowledged checkbox.

If you want to add comments to the condition report, enter the comments in the Annotations box. You can enter comments such as resolution progress, the person assigned to the condition report, or issues found.

You can print a condition report to a printer and save a condition report to a file.

� To save a condition report:

• Click Save to file. The file can be named as desired (with no embedded spaces), but it must be saved to the specified location.

� To print a condition report:

• Click Print.

��


7

Managing Devices

• Overview 87

• Performance Management 90

• World-Wide Name Zoning 93


softe

k.fu

jitsu

.com

Cha

pter

7 –

Ove

rvie

w

OverviewAvailability of management features depends on the module Softek SANView is using to manage the device. Features include link display, performance monitoring, management through a device window, basic health and identification, launch of alternate management tools, and SAN events indicating changes in health or other status changes. For information on feature availability by module, see Chapter 10: Modules.

� To find out which Ports the links are connected to:

• Right-click the desired device and choose Show Device Ports.

Determining the Ports to which the links are connected

� To view a device window:

• Go to the Topology frame, right-click the desired device icon, and choose View Device.

Viewing the Device Window for a Brocade Device



SO

FTE

KC

hapt

er 7

– O

verv

iew

88

From the device window, you can launch detailed management views, including (depending on the module being used) Port detail, enclosure status, traffic performance, configuration, and much more.

� To jump directly to a Traffic Performance Monitor window:

• Right-click the desired device in the Topology frame and choose Show Traffic Performance from the resulting drop-down menu.

Traffic Performance Monitor

� To add an Alternate Manage tool to manage a device:

1. Go to the Topology frame, right-click the desired device icon, and choose Add a Management Tool.

2. Add the management application path or URL.

3. Click Add to all ... devices if you want to use this application or URL to manage all devices of this type.

4. Click Test to test the application path or URL.

5. Click Save to save this information.


softe

k.fu

jitsu

.com

Cha

pter

7 –

Ove

rvie

w

� To launch an alternate management tool (such as a tool that is Telnet- or web-based):

1. Go to the Topology frame, right-click the desired device icon, and choose Launch Alternate Tool.

Launching an Alternate Tool for a Brocade Device

2. From the Alternate Management Tools dialog box, select the method you wish to use to connect to the device:

- Manageable via Telnet

- Manageable via URL

- Manageable via [added Management Application path]

- Manageable via [added URL]

3. Follow the prompts to access the device.

NOTE Changes made using CLI or Web Management tools may not immediately update settings in Softek SANView. To display the revised settings in Softek SANView, close and re-open the relevant device window. You may also remove and re-add the device agent to view the new settings.



SO

FTE

KC

hapt

er 7

– P

erfo

rman

ce M

anag

emen

t

90

Performance ManagementPerformance management enables you to collect data to assist in the detection and resolution of device-specific and SAN-wide problems. Softek SANView uses automated analysis modules to track SAN performance traffic, analyze failures, and validate the SAN and device configurations.

Softek SANView displays problems in the form of condition reports. Conditions encompass many events that relate to the same problem and assist in isolating the cause of the problem. Conditions may contain one or more events or alerts. The conditions are displayed using View> Condition Log from the Softek SANView Client main window.

Performance Da ta Management

The Performance Data Management window enables you to select devices for which you want to collect performance data and store that data in the Softek SANView database.

Performance Data Management window

The Performance Data Management window has two tabs: the Archive tab and the Delete tab.

Archive Tab

The Archive tab enables you to select which devices and ports for which to store performance data. The Archive table lists the device description, Port number, and Port GUID for every active device in the SAN.

� To archive performance data for a device:

• Click the Archiving checkbox for the desired device.

You can adjust the poll interval for how often the data is collected and archived to the database in seconds, minutes, or hours.

The Enable Archiving for all Selected Devices option is enabled by default. This option ensures that performance data is being captured by Softek SANView. If you should need to turn-off archiving for a period of time (for example, server maintenance or holidays), clear


softe

k.fu

jitsu

.com

Cha

pter

7 –

Per

form

ance

Man

agem

ent

the Enable Archiving for all Selected Devices checkbox. All selected devices are persisted in the database. When you want to continue archiving performance data, click the checkbox to enable this option.

• Click Apply to accept any changes you have made.

Delete Tab

The Delete tab allows you to select a device, port, and time period prior to which all performance data is deleted from the database.

Performance Data Management Delete tab

� To remove a device’s performance data from the database:

1. Select an active device and port from the drop-down box.

2. Select the time before which all the performance data for the selected switch will be deleted from the database.

3. Click Apply to remove the performance data from the database for the selected device.



SO

FTE

KC

hapt

er 7

– P

erfo

rman

ce M

anag

emen

t

92

Historical and Real -time Graphing View

The Historical and Real-time Graphing View displays the performance data in a graphical layout. The data displayed depics real time, current, and historical data that has been archived to the SANView database. The information displayed in the graph is based on the selected device, statistic, port, and time frame. Using these selections, you can create a variety of graphs for trending purposes.

Historical and Real-Time Graphing View Window

� To view the performance data:

1. Select a device from the Device drop-down box.

2. Select the statistic for which you want to view data from the Statistic drop-down box.

3. Select the port number from the Active Port on Selected Device drop-down box.

4. Select the timeframe for the graph to display. The available options are Live data, Last hour, Last day, Last week, Last month, and Last year.

5. Click Graph Data. The graph displays the data in a bar chart view with labels and a legend.

NOTE Make sure that Archive Performance Channel Data is enabled in the Archive tab of the SAN Administration window.

NOTE The graph has a finite number of data points it can chart. If you wish to view long-term trends, you will need to set a higher archiving poll interval in the Performance Data Management view.


softe

k.fu

jitsu

.com

Cha

pter

7 –

Wor

ld-W

ide

Nam

e Z

onin

g

World-Wide Name ZoningWorld-Wide Name Zoning enables you to configure device access and restrict visibility between devices in a Fabric environment.

You can use zoning to:

• Separate test or maintenance areas from production areas.

• Separate different operating system environments.

• Temporarily block or grant access during backup and other tasks.

• Consolidate equipment logically.

• Designate closed user groups for increased security.

WWN zoning can accomplish the above objectives in both multi-switch and single-switch topologies. WWN Zoning is displayed in the SCSI Target Module and in the Connected Devices tab under the Topology’s Detail View. Softek SANView’s World-Wide Name (WWN) zoning configuration complies with T-11 standards (SW-2 and GS-3).

Understanding How WWN Zoning Works

WWN zoning configurations consist of Zone Sets, Zones, and Members. Zone Sets contain Zones, and Zones contain Members. (A specific Member may be used in more than one Zone, and a specific Zone may be used in more than one Zone Set.) Only one Zone Set may be enforced on the Fabric at a time. Below is an example of a Zone Set called “Backup” which is used to back up data within two Zones, called “backupNT” and “backupUNIX”; the Members (WWPNs) are contained within the Zones.

BackupbackupNT

FF EE DD CC BB AA 99 88DD EE AA DD DD EE AA DD

backupUNIX11 22 33 44 55 66 77 88DD EE AA DD DD EE AA DD



SO

FTE

KC

hapt

er 7

– W

orld

-Wid

e N

ame

Zon

ing

94

Current WWN Zoning Conditions

WWN Zoning in Softek SANView incorporates the following conditions:

• Only Brocade (v2.3, 2.4, 2.5, 2.6 and 3.0) and Vixel devices are supported.

• Fabrics cannot include mixed device vendors; switches must be all Brocade or all Vixel.

• Using World-Wide Node Names is only available for Brocade devices.

• The Fabric must abide by the following guidelines:

1) All switches in the Fabric must support zoning.

2) All switches in the Fabric must be managed switches.

3) Every device in the Fabric must be able to see every other device in the Fabric.

• The following guidelines apply only to Brocade switches:

1) Brocade zoning is enabled through Telnet commands. Only one active Telnet session may communicate with the switch at a time.

2) All Brocade switches must have matching interopmode settings. Otherwise, a message stating that the Fabric does not meet minimum requirements appears.

3) The zoning features available for a Brocade Fabric vary depending on whether the switches are in interopmode or not.

4) There should only be one instance of Softek SANView Server managing a Fabric.

5) If the switch is not in Interop mode, you can specify zoning (domain, port pairs).

Configuring & Acti vating WWN Zoning

Before WWN zoning can be put into effect, Zone Set(s) and Zone(s) must be defined and Members added. Before you attempt to Zone devices, you must perform a discovery to ensure that the Fabric is complete.

� To open the WWN Zoning Configuration tool:

• Highlight the desired device in the Topology frame and right-click the device icon. A command submenu appears. Select WWN Zoning to open the WWN Zoning Configuration tool.

NOTE If an abandoned or inactive Telnet session is left running on the device, the WWN Zoning tool in Softek SANView will be disabled. You may need to reset the Telnet session using Brocade’s WEBTOOLS or through the Operation menu on the device’s front panel.

NOTE If you are logged in under “Monitor” privileges, you may only view the current settings in the WWN Zoning Configuration Tool.


softe

k.fu

jitsu

.com

Cha

pter

7 –

Wor

ld-W

ide

Nam

e Z

onin

g

WWN Zoning Configuration Tool

You can select what zoning configuration the WWN Zoning Configuration Tool displays. The default display is All Installable Zone Sets.

� To view the current Zone Set:

• Select Currently Installed Zone Set from the Display drop-down box. You cannot make any changes to the currently installed Zone Set.

You can navigate through the selections in the Zoning Objects and Detail of Selected Object boxes using the Back and Forward buttons. While making changes to a zoning configuration, “Modified” appears in the status box in the lower right-hand corner of the tool.

Creating a Zone Set

� To create a Zone Set:

1. Click the Create button.

The Create an Object dialog box appears.

2. Choose Zone Set from the Type drop-down box.

3. Enter a name for the Zone Set.

4. If you do not want the new Zone Set to be the active Zone Set, uncheck the Make this the active Zone Set checkbox.

NOTE If the Fabric changes while you are using the WWN Zoning Configuration Tool, the tool will close down after allowing you to save your current changes to file.



SO

FTE

KC

hapt

er 7

– W

orld

-Wid

e N

ame

Zon

ing

96

5. Click OK.

The new Zone Set appears in the Zoning Objects box and is highlighted. All defined Zones in the Fabric are listed in the Detail of Selected Object box.

� To add Zones to the selected Zone Set:

• Click the box next to each Zone’s name.

Creating Zones

� To create a Zone:



2. Choose a Zone type from the Type drop-down box.

3. Enter a name for the Zone.

If you do not want the new Zone to be added to the active Zone Set, uncheck the Add this to the active zone set box.

4. Click OK.

The new Zone appears in the Zoning Objects box and is highlighted. All defined Zone Members in the Fabric are listed in the Detail of Selected Object box.

� To add Zone Members to the selected Zone:

• Click the box next to each Zone Member’s name.

Creating Zone Members

� To create a Zone Member:



2. Choose a Zone Member type from the Type drop-down box.

3. Enter the definition of the Zone Member.

4. Click OK.

The new Zone Member appears in the Detail of Selected Object box.

Saving a Zone Configuration

� To save a Zone configuration to file:

1. Click File > Save Zone configuration to a file. A message box appears informing you that any changes you have made are being saved to a file and not installed into the Fabric.

2. Enter a name for the file in the Name text box. The file can be named as desired (with no embedded spaces), but it must be saved to the specified location.

3. Click OK to save the file.


softe

k.fu

jitsu

.com

Cha

pter

7 –

Wor

ld-W

ide

Nam

e Z

onin

g

Loading a Zone Configuration

� To load a previously saved Zone configuration:

• Click File> Load Zone configuration from a file. A message box appears stating the configuration file is only being loaded locally into the WWN Zoning Configuration tool. To install the configuration into the Fabric, load the configuration file and click Apply.

Importing the Active Zone Set into the Tool

You can import the active Zone State and merge it into the editable Zone sets in the WWN Zoning Configuration Tool. The active Zone State is then available for configuration.

� To import the active Zone State:

• Click File> Import active Zone State to configuration.

Changing the Switch Used to Manage the Zoning Change in the Fabric:

� To change the Zone switch:

• Click File> Change switch used to originate Zone change.

Hiding Unselected Items in the Detail of Selected Object box

The Detail of Selected Object box displays all defined Zones and Zone Sets. However, you can hide unselected devices in the displayed list by clicking Hide unselected devices.

� To show all devices:

• Clear the Hide unselected devices checkbox.

Renaming a Zone Set or Zone

� To rename a Zone Set or Zone:

1. Highlight the desired Zone Set or Zone.

2. Click Rename.

3. Enter the new name in the Please Confirm Rename dialog box.

4. Click OK.

Deleting a Zone Set, Zone, or Zone Member

� To delete a Zone Set or Zone:

1. Highlight the desired Zone Set or Zone.

2. Click Delete. A Please Confirm Delete dialog box appears.

3. If you are sure that you want to delete the Zone Set or Zone, click OK.

NOTE You must click Refresh to hide newly deselected items.



SO

FTE

KC

hapt

er 7

– W

orld

-Wid

e N

ame

Zon

ing

98

� To delete a Zone Member (primitive):

1. Click Delete Primitive.

2. Select the Zone Member (primitive) from the Primitive to delete drop-down box.

3. Click OK.

Default Zoning (Vixel Devices Only)

For Vixel devices, you can select the Default Zoning configuration unless the switch is set to MCDT Open Fabric mode. All devices connected to an unzoned switch can access all other connected devices if the Default Zone setting is set to enabled. Default zoning is applied when you install the configuration into the Fabric.

Select the desired zoning configuration from the Default Zoning drop-down box.

Activating the New Zone Configuration

Once the WWN zoning is configured, you can activate the new Zone configuration.

� To install the new zoning configuration into the Fabric:

• Click Apply. When you click Apply, the zoning tool takes the active Zone Set and applies it to the Fabric and then stores it in the database. You do not need to deactivate the active Zone Set before activating a new Zone Set.

� To verify that the Zone Set is active throughout the Fabric:

• Click Currently Installed Zone Set from the Display drop-down box.

� To discard any changes that you have made to the edited Zone configuration:

• Click Reset.

� To exit the WWN Zoning Configuration Tool without saving any of your changes:

• Click Close.

NOTE This only allows you to delete Zone primitives that were manually entered and are not currently referenced.

NOTE The default value Disabled allows you to block access if no zoning is in effect.

NOTE When a new zoning configuration is applied to the Fabric, the WWN Zoning Configuration Tool clears all existing zoning, including all inactive zone sets currently defined in the switch.


softe

k.fu

jitsu

.com

Cha

pter

7 –

Wor

ld-W

ide

Nam

e Z

onin

g

Representing Devices Using an Alias

� To determine what devices an alias represents:

• Click the alias name.

The alias name appears in the Zoning Objects box. The Detail of Selected Object box displays information on the alias.

To return to the previous view, click Back.

��



8

Client Menus

• Overview 103

• File Menu 103

• View Menu 104

• Options Menu 106

• Tools Menu 108

• Help Menu 111


softe

k.fu

jitsu

.com

Cha

pter

8 –

Ove

rvie

w

OverviewThis section describes the functions and selections of the menus in the Softek SANView Client’s main window (for module-specific information, see Chapter 10: Modules). Each accessed dialog box and window is referred to by the name that appears in its title bar. Please note that because some windows and dialog boxes are not meant to be maximized, the maximize button (if shown) does nothing.

In the Softek SANView Client’s main window, you can quickly determine the health of the entire SAN. If the SAN title at the top of the Tree frame is green or gray, no more attention is needed. Yellow or red highlighting signals a problem that should be further investigated; locate and double-click each device icon that is displayed in yellow or red to view the related device window.

Frames in the Softek SANView Client Main Window

File MenuThe File menu has the options described below.

File Menu

• Save Topology Snapshot saves the SAN’s agents, links, discovered devices, and customized appearance at that time.

Tree frame

SAN Events frame

Topology frame

Overview window



SO

FTE

KC

hapt

er 8

– V

iew

Men

u

104

• Save Image saves the Topology view as a .jpeg file in a location and with a name of your choosing. The image saved is the image shown (that is, the portion of screen you zoomed to in the current Topology).

• Print allows printing of the Topology view (that is, the portion of screen you zoomed to in the current Topology). You can size the printout by choosing how many pages wide and how many pages tall it will be.

• Exit Softek SANView (TM) Client closes the Softek SANView Client. (The Softek SANView Server continues to run.)

View MenuThe View menu has the options described below.

View Menu

• Find Device allows you to search for a device (SAN component) by the agent address (usually an IP Address) or model number (such as “Brocade 2800”).

• Show Topology overview displays a small navigation window showing the entire SAN. This overview window is a useful way to navigate to a particular area of the SAN.

• Show All Device Ports and Hide All Device Ports allow you to show or hide the Ports for all managed devices. You can also show or hide Ports for a specified device. Right-click the desired device icon and choose Show Device Ports or Hide Device Ports.


softe

k.fu

jitsu

.com

Cha

pter

8 –

Vie

w M

enu

Show All Device Ports Option Has Been Selected

• SAN events displays the latest 1000 SAN events (since the Softek SANView Server started) in a separate window. These events can be sorted by the desired column. For example, you can sort the messages by time to find out if many issues occur around a particular time of day. You can also print or save the displayed messages to a file.

• Condition log displays condition report entries based on information from the analysis modules and thresholding sessions. Condition report entries are created and managed by the analysis modules and thresholding sessions. Each entry has an associated condition report. The conditions can be sorted by the desired column. You can also print or save the displayed conditions to a file. To view a condition report, click the desired report entry.



SO

FTE

KC

hapt

er 8

– O

ptio

ns M

enu

106

Options MenuThe Options menu has the options described below.

Options Menu

• Log SAN events to file on Softek SANView Server computer continuously logs the SAN event messages (shown in the SAN Events frame) to a file in an appending fashion.

The SAN event log file (named sanevents.txt) is saved to:



When the file reaches its maximum size, its contents are moved to sanevents.txt.old to make room for continued logging of messages. (The default maximum file size is 5 MB, or approximately 35,000 SAN Event entries.) The maximum log file size is configured in the Log Tab of the SAN Administration window.

• Log Conditions to file on Softek SANView Server computer continuously logs the condition report entries for selected devices to a file in an appending fashion.

The Condition log file (named conditions.txt) is saved to:



NOTE These options are also available in the Log tab of the Softek SANView SAN Administration window. These settings are persistent across Server sessions (regardless of where they are configured).




softe

k.fu

jitsu

.com

Cha

pter

8 –

Opt

ions

Men

u

When the file reaches its maximum size, its contents are moved to conditions.txt.old to make room for continued logging of messages. (The default maximum file size is 5 MB, or approximately 35,000 Condition entries.)

• Log Device events to file on Softek SANView Server computer continuously logs the device event messages for all managed devices (shown in the Device Events window, available from the View menu) to a file in an appending fashion.

Each agent-specific device log file is named DeviceIP.txt (where IP is the device agent’s IP Address) and is saved to the appropriate vendor directory in:



When the file reaches its maximum size, its contents are moved to DeviceIP.log.old to make room for continued logging of messages. (The default maximum file size is 5 MB, or approximately 20,000 Device Event entries.)

• Log SAN events to Windows Event Viewer on Softek SANView Server computer continuously logs the SAN event messages (shown in the SAN Events frame) to the Window’s Event Viewer. You can use the Windows Event Viewer to view the SAN events messages.

• Log conditions to Windows Event Viewer on Softek SANView Server computer continuously logs the condition report entries for selected devices to the Window’s Event Viewer. You can use the Windows Event Viewer to see the SAN events messages.

NOTE This option is also available in the Log tab of the Softek SANView Administration window. This setting is persistent across Server sessions (regardless of where it’s configured).




SO

FTE

KC

hapt

er 8

– T

ools

Men

u

108

Tools MenuThe Tools menu has the options described below.

Tools Menu

• Set Poll interval

Allows you to configure the number of seconds or minutes between agent polling for health and other changes. Each agent is polled once during a poll interval, but total SAN polling activity is spread throughout the interval. The valid range is 5 seconds to one hour (either 5-300 seconds or 1-60 minutes).


• Set the poll interval according to the number of devices being managed. We recommend that the poll interval be set to 5 minutes for up to 40 devices, then add 1minute to the poll interval for each additional set of 10 devices you wish to monitor and manage.


NOTE Health status becomes red (“Failure”) for an agent that does not respond within a determined amount of time. The amount of time Softek SANView waits before displaying a message and changing the health status is dependent upon the selected poll interval. A 5-minute poll interval translates into approximately 12 minutes of no-response time (based on two poll intervals). Softek SANView continues to poll the agent and displays the agent’s health when communication is reestablished.


softe

k.fu

jitsu

.com

Cha

pter

8 –

Too

ls M

enu

• Redraw

Reloads the Client’s Tree and Topology frames to synchronize their displays with the management data maintained on the Softek SANView Server. To reload device windows and other secondary windows, close and reopen them.

• Discover all Agents in Subnet

Broadcasts queries to your subnet for standards-compliant SAN agents and devices. While discovery is occurring (as indicated by the Agent Discovery Progress window), you are free to perform other tasks through the Softek SANView Client. A message appears when discovery is complete.

• Discover Agent

Displays the Discover Agent dialog box, which allows you to target the discovery process to a particular agent and its device(s). While discovery is occurring (as indicated by the Agent Contact Status Monitor area), you are free to perform other tasks through the Softek SANView Client.

When contact with the specified agent is completed, the associated entry in the Agent Contact Status Monitor area is removed. If contact cannot be made, the entry remains and the information shown in the Contact status field changes.

� To re-attempt contact:

• Double-click the desired entry (so that the address reappears in the IP Address or DNS name textbox), then click Add Agent and Discover Devices.

NOTE The Softek SANView Client generally synchronizes its Tree and Topology frames without user intervention. The Tools> Redraw option can be used to verify that the Softek SANView Client is updated.

NOTE On a busy Ethernet network, discovery can take up to five minutes. You can configure Softek SANView to automatically discover agents on the subnet every time the Softek SANView Server starts. All discovered agents are displayed immediately upon launch of the Softek SANView Client.

NOTE Softek SANView retains the list of agents added through the Tools menu for the current Server session only, discarding the settings when the Server stops. If you want Softek SANView to remember your customized list of agents across Server sessions, enter them into the Discovery tab of the Softek SANView Server Configuration dialog box.



SO

FTE

KC

hapt

er 8

– T

ools

Men

u

110

• Discover Subnets

Enables you to automatically discover agents in subnets other than the local subnet across the entire SAN.

• Analysis Module Configuration

Each Analysis Module detects if a specific problem exists for the specified device on which it is focused. This view enables users to configure which Analysis Modules are active for all the active devices. Users may also customize the Analysis Module configuration on a per-device basis. Customized settings include the Analysis Module poll interval, sending email, launching a command, and other optional, Analysis Module-specific attributes for tailoring the on-going analysis. Once configured, the analysis modules gather data on the specified devices and warn users when issues arise by adding conditions to the Condition Log.

• Configure Thresholding

Enables users to create custom thresholding parameters for a selected device. When a thresholding parameter is exceeded, an optional email notification is sent out and/or a pre-configured command is launched.

• Performance Data Management

Enables you to select devices and ports for which you want to collect and archive performance data to the Softek SANView database.

• Graph Historical/Real-time Data

The Historical and Real-time Graphing View displays historical (from the database) and live performance data in a graphical layout. The information displayed in the graph is based on the selected device, statistic, port, and time frame.

• Schedule tasks

Allows you to schedule Port-based zoning configurations or other supported tasks on devices in the selected module.

• Change Password

Displays the Change Password dialog box, which allows you to specify the password for each level of access: Monitor or Manage.

The default passwords are listed below.

NOTE Softek SANView retains the list of agents added through the Tools menu for the current Server session only, discarding the settings when the Server stops. If you want Softek SANView to remember your customized list of agents across Server sessions, enter them into the Discovery tab of the Softek SANView Server Configuration dialog box or ensure the Persistence feature is enabled under the Discovery tab in the SAN Administration window.

NOTE To ensure that scheduled zoning and other tasks are executed, base the Scheduler interval on the task with the lowest time measurement. For example, if one task needs to be executed every 60 seconds and the other task needs to be executed every 30 seconds, set the Scheduler interval for 30 seconds. The Scheduler interval is set in the Softek SANView SAN Administration window.


softe

k.fu

jitsu

.com

Cha

pter

8 –

Hel

p M

enu

• Monitor: monitor

• Manage: manage

These passwords are case-sensitive; that is, you must type them in all lower-case as shown. To maintain a high level of security, change the default passwords the first time you log on to the Softek SANView Client. Note: You must be logged on at the “Manage” access level to set passwords.

Manage access grants you full permissions to use Softek SANView Client.

Monitor access restricts what you can do in the Softek SANView Client. You can view the SAN and its configuration, but you cannot make any changes to the SAN configuration.

Menu options available for the "Monitor" access level include:

- File> Save Topology Snapshot

- File> Exit SANView Client

- View> Find Device

- View> Show Topology Overview

- View> Show All Device Ports

- View> SAN Events

- View> Condition Log

- Tools> Set Poll Interval

- Tools> Redraw

- Tools> Discover all Agents in subnet

- Tools> Discover Agent

- Tools> Discover Subnets

- Help> Contents

- Help> About SANView

• Manage Licenses

Allows you to enable purchased features on devices in the selected module.

Help MenuThe Help menu contains two options: Contents displays the online help and About Softek SANView displays version and system information, including current Port-based license and version numbers of installed modules.

Help Menu

��



9

Server Files

• Device Configuration & Firmware Files 115

• Log Files 115


softe

k.fu

jitsu

.com

Cha

pter

9 –

Dev

ice

Con

figur

atio

n &

Firm

war

e F

iles

The Server saves device configuration, device firmware, and log files onto the Softek SANView Server system. All files are saved in the root directory at the default location of: install_dir\FileSystemRoot\ (where install_dir is the directory in which Softek SANView was installed).

Device Configuration & Firmware FilesAll device configuration files and firmware image files are accessed from the appropriate vendor directory in:

• Windows: C:\SANView_V4.1\FileSystemRoot\deviceconf\

• Solaris: /opt/SANView_V4.1/FileSystemRoot/deviceconf/

Availability of configuration and/or firmware files for a particular device depends on the Softek SANView Module used to manage that device. For more information, see Chapter 10: Modules.

Log FilesSoftek SANView uses log files to track different types of events or messages. Each log file is described in the table below (files are listed in alphabetical order).


Log Files in Softek SANView

Log File Types of Events/Messages that are Logged

ClientLog.txt Messages from the Softek SANView Client and errors that Softek SANView Client encountered.

DebugLog.txt (Used for troubleshooting.)

DeviceIP.log(where IP is the device’s IP Address)

Event log entries that are maintained by the device's agent. (The Log Device Events option must be enabled (checked) for device events to be logged.)

errorlog.txt Devices errors, uncaught exceptions and other errors that Softek SANView encountered.

SVServer.err in the install_dir/bin directory)

Informational and error messages from the Softek SANView Server, including reasons for the Server not staying up (such as expiration of a trial license while the Server was running).

SVServer.out in the install_dir/bin directory)

Informational and error messages from the Softek SANView Server, including reasons for the Server not to start (such as an expired license).

SVServerLog.txt Activities of the Softek SANView Server (not currently supported).



SO

FTE

KC

hapt

er 9

– L

og F

iles

116

Unless otherwise noted, the event log files are saved to:

• Windows: C:\SANView_V4.1\FileSystemRoot\logs\

• Solaris: /opt/SANView_V4.1/FileSystemRoot/logs/

��

sanevents.txt Softek SANView SAN events. (The Log SAN Events... option must be enabled (checked) for SAN events to be logged.)

conditions.txt Softek SANView condition report entries. (The Log Conditions... option must be enabled (checked) for SAN events to be logged.)


Log Files in Softek SANView

Log File Types of Events/Messages that are Logged


10

Modules

• Quick Reference 119

• Detailed Information 121


softe

k.fu

jitsu

.com

Cha

pter

10

– Q

uick

Ref

eren

ce

A Softek SANView Module is a software subset that allows Softek SANView to discover, monitor, and manage specific SAN devices. Options include specialized discovery, data collection and interpretation, graphical user interfaces, and launch—with context—of alternate management tools (such as Telnet or Web-based tools).

Quick Reference

In the table below, you can find out which features are supported for each module. Feature descriptions follow the table.

NOTE A particular vendor’s collection of devices may contain models that are managed through a standards-based module such as FC MIB (instead of a vendor-specific module).

Mod

ule

and

Ver

sion

Dev

ices

Bas

ic H

ealth

& I

D

SA

N E

vent

s

Link

Inf

o

Teln

et A

vaila

ble

Web

Ava

ilabl

e

Dev

ice

Win

dow

Enc

l. S

tatu

s M

on.

Aut

o. I

nsta

ll

Oth

er F

eatu

res

& N

otes

Brocade v3.0

38002800240020102050

X X X X X X X X ISL and links are displayed.

GR Family Module v1.0

GR840GR820GR740GR730GR720GR710

X X X X X X The GR Family Module supports Fujitsu Eternus GR series devices.

Chaparral v2.0

FS1310 X X X X X

Crossroads v2.0

4200 X X X X X Other models are supported through the FC MIB Module.

Host Agent v1.0

FC HBA API-compliant HBAs, SDS Virtualiza-tion Agent, PFCA HBAs

X X The installation of this agent automatically detects the system configuration, and installs the appropriate proxy.

* See asterisked (“*”) note in last column.



SO

FTE

KC

hapt

er 1

0 –

Qui

ck R

efer

ence

120

Descriptions of each feature follow.

• Basic Health & ID

Device health is monitored in the Tree frame and Topology frame, as is Port health, if Port information is available in this module. Agent health is monitored in the Tree frame. The variables that are used to determine health vary from module to module. For more information, see Detailed Information on page 121. Unique identification for each device and agent is displayed through tool tips in the Topology and Tree frames. For information on health color-coding and tool tips, see “Understanding Health” on page 37.

• SAN Events

The SAN Events frame records addition/deletion of device agents or devices plus other health or status changes for devices and Ports. For event message severities and color-coding, see Log Files on page 115.

FibreChannel MIB v2.0

FibreChannel MIB-compliant devices

X X * * * X * Link display requires FC MIB 2.2 or 3.0. Telnet or Web availability varies by model and firmware.

Gadzoox v1.2

Gibraltar-GS

X X X X X

McData v1.1

ED-6064ED-5000ES-3032ES-3016

X X X * X EFCM launch from Topology frame (for ES-3016, ES-3032, and ED-6064).* Web availability refers to the EFCM application.

SCSI Target v1.1

SCSI storage devices

X X X X

Vixel v1.4 9300920091008100720071002100

X X X X * X X X * Web availability varies by model and firmware.

Mod

ule

and

Ver

sion

Dev

ices

Bas

ic H

ealth

& I

D

SA

N E

vent

s

Link

Inf

o

Teln

et A

vaila

ble

Web

Ava

ilabl

e

Dev

ice

Win

dow

Enc

l. S

tatu

s M

on.

Aut

o. I

nsta

ll

Oth

er F

eatu

res

& N

otes

* See asterisked (“*”) note in last column.


softe

k.fu

jitsu

.com

Cha

pter

10

– D

etai

led

Info

rmat

ion

• Link Info

This device’s agent provides information about nearest-neighbor connected devices (whether managed or not).

• Telnet Available

An alternate Telnet-based tool for management can be launched from the Topology frame by right-clicking the desired device icon.

• Web Available

An alternate web-based tool for management can be launched from the Topology frame by right-clicking the desired device icon.

• Device Window

A device window can be opened from the Topology frame. Device health is monitored in this window, as is Port health, if Port information is available in this module. For details, see Detailed Information on page 121.

• Encl. Status Mon.

Information on the status of a device’s enclosure (fans, power supplies, etc.) is monitored and factored into health.

• Auto. Install

This module is automatically installed with Softek SANView.

To find out whether Port information and/or device events are available for a particular module, see the related module in Detailed Information on page 121.

Detailed InformationRequired firmware versions and details about supported features are below, sorted by module name.

Brocade Module v3.0

• Information on the Brocade devices is gathered via the Brocade API.

• Firmware version required: 2.2 or newer.

• Brocade’s WebTools management tool must be available, with the switch’s SNMP agent enabled.

• For ISLs (Inter-Switch Links) to display, switches must be running version 2.2 or newer firmware.

• The Brocade switch’s overall health is calculated through its switch sensors (fans, temperature, power supply) status, Port health, and switch operation status.

• Port health depends on the Brocade Port Status.

NOTE The Fibre Channel HBA, PFCA HBA, and SDS Virtualization Agent modules are documented in another chapter. Please refer to Host Agent on page 131.



SO

FTE

KC

hapt

er 1

0 –

Det

aile

d In

form

atio

n

122

• Events logged for Brocade switches (in addition to the standard addition/removal of agents/devices and loss/gain of agent contact) include the following types:

From a Brocade switch:

- Health: <old state> -> < new state>

- Operation Status changed: <old state> -> <new state>

- Enclosure Sensor <sensor type>[<sensor index>] Status is: <status>

- Enclosure Sensor <sensor type>[<sensor index>] Status changed: <old status> -> <new status>

From a Brocade Port:

- Port Module changed: < old Module> -> < new Module>

- Port Type changed: < old Type> -> < new Type>

- Port State changed: <old state> -> <new state>

• The Brocade Switch window displays the following information:

- Device Make and Model

- Serial Number (World-Wide Name is used for Brocade device serial numbers)

- World-Wide Name (WWN)

- Module type and health status for each Port (Note: Ports are numbered using Brocade’s numbering convention (that is, the first Port is numbered “0”).)

- Health status for device and enclosure (displayed in lower-left icon)

- Standard File and Help menus

- Tools menu with Launch Web Manager option to manage the switch via the web and Poll Now option to immediately poll the switch’s agent for status

• Port windows show Port type, state, health, and Port module information.

The GBIC icons supported for the Brocade Module are described below.

GBIC Icon GBIC Type

Intra CopperInter Copper

FC LW Laser (Longwave)Serial FC LW Laser (Longwave)

FC SW Laser (Shortwave)Serial FC SW Laser (Shortwave)

GBIC UnknownNo Module


softe

k.fu

jitsu

.com

Cha

pter

10

– D

etai

led

Info

rmat

ion

GR Family Module v1.0

• For links to display, devices must be compliant with Version 2.2 or 3.0 of the FibreChannel MIB.

• Agent health status is based on Softek SANView’s ability to communicate with the agent using SNMP, HTTP, and NIM-PCC.

• Device health status is based on the unitStatus and icpStatus of Private MIB; vendor and firmware determine the variables that drive the value of this OID.

• Port health is based on the connUnitPortStatus OID and is used as long as the device complies with Version 2.2 or higher of the FibreChannel MIB.

• The GR Module Device window displays the following information:

- Box ID: Device ID of the GR Device

- Serial Name: GR series Name (GR710, GR740, etc.)

- Model Name: GR model Name (GR72A01, GR73B02, etc.)

- Serial Number: Serial Number of the GR Device

- SysName: SNMP MIB-II sysName

- Enterprise Code: SNMP MIB-II sysObjectId

- Location: SNMP MIB-II sysLocation

- Firmware version

- Management Software: Managed GUI Tool URL of the GR Device

- Account: User ID Name of the managed GUI Tool

- Password: User Password of the managed GUI Tool

GR740 Device Tool Tip

• The GR Module Port window displays the following information:

- Port ID: Index Number of CA in the GR Device

- Exchange Unit Number: The exchangeable unit number of CA in the GR Device

- Logical ID: Logical ID of CA in the GR Device

- WWNN: World-Wide Node Name

- WWPN: World-Wide Port Name

- Port Type: NL Port or N Port



SO

FTE

KC

hapt

er 1

0 –

Det

aile

d In

form

atio

n

124

GR740 Port Tool Tip

• SNMP Trap Analysis: The GR Family Module analyzes a trap sent from the GR Device and then registers the Event. The Events are registered for problems only.

• Launch function of the the GR Family Module: the browser that displays the login window of the Managed GUI Tool is started. The Managed GUI Tool differs in the domestic model and overseas model. The domestic model Managed GUI Tool is called GR Manager (GRmgr), and the overseas model is called GR Service Console (GRSC). These tools are not used simultaneously.

GRmgr is constructed with a CGI part and a monitoring part of the GR Device. The launched login window displayed in the browser is located in the CGI part in the GR Device. The URL of login window differs in GR710/GR720/GR730 and GR740/GR820/GR840.

GRSC can manage plural GR devices which are connected on LAN with GRSC host . These GR devices are distinguished by a Virtual Name given to each device, and managed by GRSC. The virtual names in the URL differ.

Chaparral Module v2.0

• Firmware version required: R413 or M120.

• Agent health status is based on Softek SANView’s ability to communicate with the agent using SNMP.

• Device health status is based on the connUnitStatus OID in the device’s SNMP MIB.

• Port health is based on the connUnitPortStatus OID.

• Because Port information is not available, Port state changes are not logged.

Crossroads Module v2.0

• Firmware version required for the 4200: 2.2 9913a.

• Other models are supported through the FC MIB Module.



softe

k.fu

jitsu

.com

Cha

pter

10

– D

etai

led

Info

rmat

ion

Fibre Channel MIB Module v2.0

• FibreChannel MIB version required: 1.5, 2.2, or 3.0. (Compliance is detected through the Fibre Alliance MIB revision number.)

• For links to display, devices must be compliant with Version 2.2 or 3.0 of the FibreChannel MIB.

• Agent health status is based on Softek SANView’s ability to communicate with the agent using SNMP. Device health status is based on the connUnitStatus OID in the device’s SNMP MIB; vendor and firmware determine the variables that drive the value of this OID. Port health is based on the connUnitPortStatus OID and is used as long as the device complies with Version 2.2 or higher of the FibreChannel MIB.

Gadzoox Module v1.2

• Firmware version required for Gibraltar-GS: 4.0.

• Agent health status is based on Softek SANView’s ability to communicate with the agent using SNMP. Device health status is based on the connUnitStatus OID in the device’s SNMP MIB.


• The Gadzoox Hub window displays the following information:

- Device Make and Model

- Serial Number

- World-Wide Name (WWN)

- Number of Ports

- Health

- Device up time

- Standard File and Help menus

- Tools menu with Poll Now option to immediately poll the agent for status

McData Module v1.1

• Firmware version required:

- ES-3016: 01.01.00

- ES-3032: 01.01.00

- ED-5000: 03.01.0025

- ED-6064: 01.01.027

• Agent health status is based on Softek SANView’s ability to communicate with the agent (EFC Manager application) using SNMP. Agent health is based on an aggregate device health, which is based on aggregate Port health. Port health is based on the connUnitStatus OID in the device’s SNMP MIB.

• Events logged for McData devices (in addition to the standard addition/removal of agents/devices and loss/gain of agent contact) include “Management Server” and “Health” messages.



SO

FTE

KC

hapt

er 1

0 –

Det

aile

d In

form

atio

n

126

• The EFCM (EFC Manager) serves as the agent for McData devices and the EFCM Client must be installed to manage McData devices. Instructions below.

� Prerequisites for EFCM launch from Softek SANView:

• EFC Manager (not EFCM Lite) must be installed on a separate system. Refer to McData’s documentation.

• EFCM agent must be managed by Softek SANView.

� To launch EFCM launch and install the client for the first-time:

1. In the Topology frame of the Softek SANView Client, right-click the desired McData device icon, choose Launch Alternate Tool from the drop-down menu, and select McData EFCM Client.

The following message appears in a browser window: “Have you already installed the EFC Manager application?”

2. In the browser window, click No.

A security warning appears.

3. Click OK for the security warning, review the resulting display of instructions (for your platform), click the related installation button, and follow the reviewed instructions. (You may close the browser window after installation is complete.)

The EFC Manager application (remote client) is now installed, but the external viewer may still need to be configured (as indicated by the appearance of the “Unknown File Type” dialog box).

4. Repeat Step 1: In the Topology frame of the Softek SANView Client, right-click the desired McData device icon, choose Launch Alternate Tool from the drop-down menu, and select the Web Manager tool.

The following message appears in a browser window: “Have you already installed the EFC Manager application?”

5. In the browser window, click Yes.

6. If the Unknown File Type dialog box appears (Netscape on Windows), follow these instructions:

a. Click Pick App.

b. In the resulting Configure External Viewer dialog box, click Browse.

c. In the resulting Select an appropriate viewer dialog box, enter the path for the EFC_Manager.exe file and click OK.

!CAUTION:On an Internet Explorer browser, clicking Yes when the client is not yet installed causes the launching procedure to bypass client installation and unsuccessfully attempt to open an EFCM file. If this situation occurs, cancel the launching procedure, clear the browser cache & history, remove all cookies from the Temporary Internet Files directory, and retry.


softe

k.fu

jitsu

.com

Cha

pter

10

– D

etai

led

Info

rmat

ion

d. In the Configure External Viewer dialog box, click OK.

The browser’s standard alert message (which asks you to choose between saving or opening the file) appears.

7. In the browser’s standard alert message, click Open (instead of Save).

The EFC Manager Login prompt appears.

8. Log in (default user name and password: Administrator and password).

EFC Manager is launched.

� To launch EFCM (after client is installed and the external viewer is configured):

1. In the Topology frame of the Softek SANView Client, right-click the desired McData device icon, choose Launch Alternate Tool from the drop-down menu, and select McData EFCM Client.

2. If the “Have you already installed...?” message appears, click Yes.

The browser’s standard alert message (which asks you to choose between saving or opening the file) appears.

3. Click Open.

The EFC Manager Login prompt appears.

4. Log in (default user name and password: Administrator and password).

EFC Manager is launched.

SCSI Target Module v1.1

The SCSI Target Module uses multiple agents to retrieve information on a single storage device. This additional information includes the LUN (Logical Unit Number), vendor name, model name, Port health status, and Port information.

With the SCSI Target Module, you can have multiple agents communicating information about a single device. For example, you can view information for a storage device or tape library provided by multiple HBAs. This feature is especially useful if the switch is running in Stealth mode because you can view information for the storage devices behind the routers.

The level of manageability depends on the agent(s). If the agents cannot communicate with device, the device will turn red. The SCSI Target Module is limited in what it can see when Fabric is running and zoning is enabled.

The health of a device is determined by whether or not it can communicate with its hosts. The HBA sends a request (“ping”) the storage device for a response. You may have multiple hosts making requests to a device to get a collective status. If there is a loss of connection to the host, you can route to a failover source. If all hosts fail, the device will show a loss of connection.

Storage devices are defined by a World-Wide Name (WWN). The SCSI Target Module retrieves the Port name (WWPN) and node name (WWNN). You can then view one device with multiple Ports instead of multiple devices.

Devices managed by the SCSI Target Module show up in the Tree frame under a special agent (FCP/SCSI Targets).



� To view the special agents:

• You must discover the agents in the subnet (Tools > Discover Agents in Subnet).

Device View

� To display the device view:

• Double-click the device icon.

Storage Device View

The device view displays the device name and model, the WWN, and all Ports represented by agents.

Double-click a Port to view further information about the Port, such as the type of configuration, link speed, connection status, and LUN (Logical Unit Number) information.

Port View

� To display the Port view:

• Double-click the Port icon.

Storage Device Port view

softe

k.fu

jitsu

.com

Cha

pter

10

– D

etai

led

Info

rmat

ion

The Port view displays information for the selected Port.

Vixel Module v1.4

• Firmware version required:

- Vixel 2100: v1.x

- Vixel 7100/7200: v3.3 or v3.5

- Vixel 8100: v1.x

- Vixel 9100/9200/9300: v5.0 or v6.0

��

Storage Device Port View

Feature Description

Node WWN Displays the World-Wide Node Name.

Port WWN Displays the World-Wide Port Name.

Port Type Configuration Displays the Fibre Channel Address and Port Type for the selected Port.

Port Link Speed Identifies if this feature is supported and detected.

Port Connect Displays the current Port state and inquiry status.

FCP-LUNs Displays the available Logical Unit Numbers (LUNs) for the Port. LUN information includes vendor name, product number, revision number, vendor information, type, block size, and capacity.

Including Zones Displays the Port zoning information. If the Port is not zoned, a message is displayed stating that no zoning is present. Otherwise, all zones are displayed.



11

Host Agent

• Overview 133

• Features & Supported Devices for the Host Agent’s Fibre Channel HBA

133

• Running the Host Agent (FC HBA Proxy, PFCA Proxy, or SDS Proxy)

134

• Discovering HBAs 135

• Understanding HBA Displays in Softek SANView 135

• Fujitsu PFCA HBA Module 141

• SDS Virtualization Agent 143


softe

k.fu

jitsu

.com

Cha

pter

11

– O

verv

iew

OverviewThe Host Agent Module is one of several Softek SANView Modules. A Softek SANView Module is a software subset that allows Softek SANView to discover, monitor, and manage specific SAN devices. Options include specialized discovery, data collection and interpretation, graphical user interfaces, and launch—with context—of alternate management tools (such as Telnet or Web-based tools).

The Host Agent is composed of the following components:

• The Fibre Channel HBA, which enables the management of all HBAs that comply with the industry’s standard HBA API Library (Host Bus Adapter Application Program Interface Library). The industry standard is the Fibre Channel HBA API Library, which was submitted by the Storage Networking Industry Association (SNIA).

• The PFCA module, which enables the discovery and management of the Fujitsu PFCA HBA.

• The SDS, which enables the discovery and management of the SDS Virtualization Agent.

Features & Supported Devices for the Host Agent’s Fibre Channel HBA

This module supports all HBAs that are compliant with SNIA’s Fibre Channel HBA API Library. The features specific to the FC HBA Module follow.

• Support of multiple HBAs on one HBA Proxy Server.

• Health monitoring and identification of compliant HBAs, shown in Tree frame (left frame), Topology frame (right frame), and HBA window. Health for the HBAs is monitored in the Tree frame.

• HBA-specific device information available through back-of-box, Port details, and Port statistics views.

• Recorded events in SAN Events frame (lower frame) for addition/deletion of device agents/devices and other health or status changes of the monitored HBAs.



SO

FTE

KC

hapt

er 1

1 –

Run

ning

the

Hos

t Age

nt (

FC

HB

A P

roxy

, PF

CA

Pro

xy, o

r S

DS

Pro

xy)

134

System Overview (FC-compliant HBA and Softek SANView)

Running the Host Agent (FC HBA Proxy, PFCA Proxy, or SDS Proxy)

The HBA Proxy Server enables communication between the FC-compliant HBA(s) on its system and the Softek SANView Server system. The proxy listens on the UDP Port for Softek SANView Server’s discovery requests and on the TCP Port for data requests.

The HBA Proxy Server runs differently depending on the operating system. On Windows the proxy runs as the “SANView HBA Proxy Service,” which starts automatically when the host starts. Make sure you log in under the same account that was used to install the proxy. Installing and running under the Administrator account is recommended.

On Solaris, the proxy runs as a daemon. Make sure you log in under the same account that was used to install the proxy. Installing and running under root is recommended.

� To find out whether the Host Agent is running:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> status.


� To stop the Host Agent:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> stop.



softe

k.fu

jitsu

.com

Cha

pter

11

– D

isco

verin

g H

BA

s

� To start the Host Agent:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> start.


� To view logged events:

• Windows (HBA Proxy Service): Open the application log in the Event Viewer from the Administrative Tools, then look for messages from SANViewHBAProxyServices.

(Administrative Tools is accessed through Start> Programs on Windows NT and from the Control Panel on Windows 2000.)

• Solaris (HBA Proxy daemon): Open the /var/adm/messages file.

Discovering HBAsYou can configure discovery options during a Softek SANView Client session or before the Softek SANView Server starts. Discovery during a Client session is configured through the Tools menu; discovery before the Server starts is configured through the Softek SANView SAN Administration window. Both options allow you to discover all agents on the subnet of the Softek SANView Server system and/or to specify agents for discovery by DNS name or IP Address (the agent may be on a router-connected subnet).

These options differ only in persistence; discovery settings configured in the Softek SANView Client’s Tools menu are discarded when the Softek SANView Server restarts, but settings configured in the SAN Administration window are retained across Server sessions. If you want a list of several agent addresses for discovery to be available after the Server restarts, enter the list through the SAN Administration window.

Another discovery option available only through the Softek SANView Client is the automatic discovery of agents in subnets other than the local subnet. You can initiate the Discover Subnet command through the Tools menu.

Understanding HBA Displays in Softek SANViewThe Softek SANView Client shows HBA health status, unique identification, HBA-specific device information, and recorded events for devices in its Tree, Topology, and SAN Events frames.

Device health status is updated according to the frequency (poll interval) set through Softek SANView.

� To change the poll interval:

• Choose Tools> Set Poll Interval in Softek SANView’s main window.

NOTE To view the Softek SANView SAN Administration window:Windows: Choose Start>Programs>SANView_V4.1>Local_SVServer>config.Solaris: /usr/local/bin/SANView_V4.1/config



Finding Health Status

Health status for all managed devices (including those for this module) and their Ports is shown in the Tree and Topology frames; health status for agents is shown in the Tree frame. Health states for the SAN and for each device, agent, and Port are color-coded in Softek SANView as follows.

Device and Port health status is reflected in the health of the entire SAN, which is shown in the SAN title in the Tree frame. If the SAN title indicates a non-functional state (yellow or red), look through the Tree and Topology frames for an agent or device in a non-functional state. A possible cause of this health state is communications failure on the link or loop segment supported by a device Port.

For the FC HBA Proxy, agent health status is based on Softek SANView’s ability to communicate with the HBA Proxy Server using TCP and the status return from SNIA’s Fibre Channel HBA API Library calls. Device health status is based on the aggregate of HBA Port health. Port health (Port State) is returned from SNIA’s Fibre Channel HBA API Library calls.

Locating World-Wide Names and Other Information

An HBA’s World-Wide Name and other unique device, agent, or Port identification are displayed through tool tips.

Tool tips for an HBA, in the Tree and Topology frames

Health State Color-Coding

Color of Icon Health State

Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused

softe

k.fu

jitsu

.com

Cha

pter

11

– U

nder

stan

ding

HB

A D

ispl

ays

in S

ofte

k S

AN

Vie

w

Viewing HBA Information

You can view HBA-specific device information through back-of-box, Port details, and Port statistics views.

Back-of-box View

The Back-of-box View displays HBA information such as name, serial number, firmware version, number of Ports, power status, HBA status, and additional information.

� To view an HBA device window:

• Go to the Topology frame, right-click the desired host icon, and choose View Device.

� To launch a detailed Port view from the HBA device window:

• Double-click the Port icon.

Back-of-Box display for a Fibre Channel HBA

Back-of-Box display for a PFCA HBA



SO

FTE

KC

hapt

er 1

1 –

Und

erst

andi

ng H

BA

Dis

play

s in

Sof

tek

SA

NV

iew

138

Back-of-Box display for an SDS HBA (Virtualization)

Port Details View

The Port Details View displays information for the HBA Port including the Port state, Port WWN, Port type and speed, and additional information. The Port Details View also shows information for the Port of the target storage device connected to the HBA (called a “discovered Port”) for FC HBAs.

� To launch the Port Details View:

• Double-click the Port icon on the HBA device window.

FC HBA Port Details View

The discovered Port information includes Port WWN, Port node WWN, Port symbolic name, Port OS device name, Port type, Port state, Port speed, and Port supported speed.


softe

k.fu

jitsu

.com

Cha

pter

11

– U

nder

stan

ding

HB

A D

ispl

ays

in S

ofte

k S

AN

Vie

w

PFCA HBA Port Details View

SDS HBA Port Details View



SO

FTE

KC

hapt

er 1

1 –

Und

erst

andi

ng H

BA

Dis

play

s in

Sof

tek

SA

NV

iew

140

Port Statistics View

The Port Statistics View displays Port statistics information for each configured Port.

HBA Port Statistics View

� To view Port statistics:

• Click View> Port Statistics on HBA device window.

� To save the Port statistics information to a file:

• Click File> Save HBA Port Statistics Table to file. This file will be saved to FileSystemRoot/deviceconf/HostAgent.

Understanding Recorded Events

Softek SANView monitors device agents for changes in health or configuration, then records an event message when a change occurs. The last 20 events are displayed in the Client’s SAN Events frame (lower frame); the last 500 events are shown through View> SAN events. When the Log SAN events to file option is enabled, these events are also recorded as text files on the Softek SANView Server system. If you select Log SAN events to Windows Event Viewer, you can view events in the Windows Event Viewer on the Softek SANView Server system.

When you choose View> SAN events, an isolated SAN Events frame appears. This isolated frame displays the latest 500 events that have occurred since the Softek SANView Server started. You can sort events by the desired column. You can save or print the displayed events, or upload more events as desired.

NOTE The PFCA and SDS proxies do not show Port Statistics.


softe

k.fu

jitsu

.com

Cha

pter

11

– F

ujits

u P

FC

A H

BA

Mod

ule

SAN Events frame (isolated) showing events recorded for an HBA

The severity of each event message in the SAN Events frame is color-coded as follows.

For more information on SAN Events, please refer to Understanding SAN Events on page 64.

Fujitsu PFCA HBA ModuleThe PFCA Module (PCI Fibre Channel HBA Module) is one of several Softek SANView Modules.

A Softek SANView Module is a software subset that allows Softek SANView to discover, monitor, and manage specific SAN devices. Options include specialized discovery, data collection and interpretation, graphical user interfaces, and launch-with context-of alternate management tools (such as Telnet or Web-based tools).

The PFCA Module is similar to FC HBA Module in functionality, which enables the management of all HBAs (Fujitsu PFCA HBA) that are not capable of supporting industry standard HBA API Library.

Features & Supported Devices

This module supports Fujitsu PFCA HBAs that are non-compliant with SNIA’s Fibre Channel HBA API Library. For collecting the required information, the module uses general Solaris commands and PFCA HBA driver-related commands. These are:

• Prtconf

• Fc_info

• /etc/path_to_inst

Event Message Severities

Color of SAN Event Text Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown



PFCA Module Features

• Support of multiple HBAs on one HBA Proxy Server.

• Health monitoring and identification of compliant HBAs, shown in the Tree frame (left frame), Topology frame (right frame), and HBA window. Health for the HBAs is monitored in the Tree frame.

• HBA-specific device information is available through back-of-box, Port details views.

• Recorded events in SAN Events frame (lower frame) for addition/deletion of device agents/devices and other health or status changes of the monitored HBAs.

List of properties captured by this module

Due to lack of support for SNIA HBA API, this module performs very limited actions compared to the FC HBA Module.

• Model is hard coded to GP7B8fc1

• NodeWWN (Determined from the prtconf command)

• PortWWN

• Number of Ports (Always equal to 1)

• Port Symbolic Name

• Port Type

• Ports State

• Port Device Name

• Port FC Id

• Port Max Frame Size

Supported Platforms

Fujitsu PFCA module is available only for Solaris 8 systems.

Hardware Properties

The following figure shows the front of the Fibre Channel card.

The various parts, together with their features, are as follows:

Optical module

The optical module is connected to a Fibre Channel hub or Fabric or a disk array device with an optical fiber cable.

softe

k.fu

jitsu

.com

Cha

pter

11

– S

DS

Virt

ualiz

atio

n A

gent

SIG (Signal Detect)

This LED lights when optical signals from the connected device are detected at the receiving end of the optical module on the adapter. SIG lights only if the optical fiber cable is connected. If the LED does not light even though the optical fiber is connected and the device to which the other end of the cable is connected is in operational status, it may be because the optical fiber cable is broken, the optical module on the adapter is faulty, or the optical module on the connected device is faulty.

HB (Heart Beat)

This LED lights when the Fibre Channel control LSI chip on the adapter is operating. (Actually, the LED blinks so quickly that it appears dimly lit.)

LINK (Link)1

This LED lights when Fibre Channel is in the communication-enabled state.

CHK (Check)1

This LED is not currently used.

SDS Virtualization AgentFor a complete description of the SDS Virtualization Agent, please refer to the Softek Virtualization 1.5.0 Administration Guide (ML-144905).

��

1. LED of LINK and CHK can be blinked by using the fc_adm command.



A

Backing Up and Restoring the Database

• Backing Up the Database 147

• Restoring the Database 148


softe

k.fu

jitsu

.com

App

endi

x A

– B

acki

ng U

p th

e D

atab

ase

Softek SANView 4.1 uses a database to store information related to the SAN, including configuration and historical performance data. A scheduled, ongoing backup of the database is recommended to protect against data loss due to system instability. When necessary, the database may be restored to return the system to its original operating state (at the time of the last backup).

Backing Up the DatabaseBefore backing up the database, you should save a topology snapshot in the Softek SANView Client (see Saving a Snapshot of the Topology on page 53) and ensure that the persistence option is enabled on the Discovery tab of the SAN Administration window (see Persisting the SAN Configuration on page 22).

The backup procedure is accomplished using the following instructions.

� To back up the Softek SANView database:

1. Shut down the Softek SANView Server using the following commands:

- Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> stop

• If an automated script is used, execute the following command from the SANView bin directory: StopSVServer.exe

- Solaris: /usr/local/bin/SANView_V4.1/stop

2. Create backup copies of the following folders:

- $INSTALL_DIR/config

- $INSTALL_DIR/FileSystemRoot

where $INSTALL_DIR is the local Softek SANView directory (the default directory is SANView_4.1).

3. Run the following MySQL command from the MySQL bin directory to copy the database to a file:

- ./mysqldump --opt san_manager > backup.sql

4. Copy the backup.sql file to the same location as the folders in step 2.

5. Restart the Softek SANView Server using the following commands:

- Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> start

• If an automated script is used, execute the following command from the SANView bin directory: StartSVServer.exe

- Solaris: /usr/local/bin/SANView_V4.1/start

The database backup procedure is now complete.

NOTE Depending on database size, the backup process may take up to two hours to complete.



SO

FTE

KA

ppen

dix

A –

Res

torin

g th

e D

atab

ase

148

Restoring the DatabaseThe restore procedure is accomplished using the following instructions. This procedure is intended for restauration of same-version databases only. It is not recommended to use a database from an old version of Softek SANView as the database for Softek SANView 4.1 because tabular changes may have occurred between versions. If the old database version is required in the new installation, please contact your Softek representative to discuss data migration.

� To restore the Softek SANView database:

1. Remove and re-install Softek SANView after a system crash, loss of data, or other system failure.

� To remove Softek SANView:

• Windows: Choose Start> Programs> SANView_V4.1> SVremove.

• Solaris: /usr/local/bin/SANView_V4.1/SVremove

� To re-install Softek SANView:

1) Insert the Softek SANView CD-ROM.

2) If autorun is disabled, open this file:

• Windows: Windows_Installer.exe

• Solaris: Solaris_Installer.bin

2. Shut down the Softek SANView Server using the following commands:

- Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> stop

• If an automated script is used, execute the following command from the SANView bin directory: StopSVServer.exe

- Solaris: /usr/local/bin/SANView_V4.1/stop

3. Restore the following folders:

- $INSTALL_DIR/config

- $INSTALL_DIR/FileSystemRoot

where $INSTALL_DIR is the local Softek SANView directory (the default directory is SANView_4.1).

4. Run either of the following MySQL commands from the MySQL bin directory to restore the database:

- ./mysql san_manager < backup.sql

or

- ./mysql -e ‘source backup.sql’ san_manager

NOTE Depending on database size, the restore process may take up to two hours to complete.

NOTE If the Softek SANView system is operating correctly but the database or configuration is corrupted, proceed directly to Step 2.


softe

k.fu

jitsu

.com

App

endi

x A

– R

esto

ring

the

Dat

abas

e

5. Ensure that the persistence option is enabled on the Discovery tab of the SAN Administration window (see Persisting the SAN Configuration on page 22).




6. Restart the Softek SANView Server using the following commands:

- Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> start

If an automated script is used, execute the following command from the SANView bin directory: StartSVServer.exe

- Solaris: /usr/local/bin/SANView_V4.1/start

The database restore procedure is now complete. The server should return to the state at which the backup occurred.

��



B

Shortcuts

• Shortcuts and Solaris Commands 153


softe

k.fu

jitsu

.com

App

endi

x B

– S

hort

cuts

and

Sol

aris

Com

man

ds

Shortcuts and Solaris CommandsThis section lists shortcuts and Solaris commands for common tasks.

� To install Softek SANView, insert the CD. If autorun is disabled, open this file:

• Windows: Windows_Installer.exe

• Solaris: Solaris_Installer.bin

� To uninstall Softek SANView:

• Windows: Choose Start> Programs> SANView_V4.1> SVremove

• Solaris: /usr/local/bin/SANView_V4.1/SVremove


• Windows: Choose Start > Programs > SANView_V4.1 > Local_SVServer > config


� To find out whether the Softek SANView Server is running:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> status


� To stop the Softek SANView Server:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> stop


� To start the Softek SANView Server:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> start


� To view the current Softek SANView license (on the Softek SANView Server system):

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> about

• Solaris: /usr/local/bin/SANView_V4.1/about

NOTE The Uninstall program does not automatically delete the Softek SANView database. The Softek SANView database stores historical data for your SAN. Deleting this database destroys the data.



SO

FTE

KA

ppen

dix

B –

Sho

rtcu

ts a

nd S

olar

is C

omm

ands

154

� To enter a new or changed license (on the Softek SANView Server system):

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVServer> UpdateLicense


� To start the Softek SANView Client:

1. Make sure that the Softek SANView Server has been running for at least 30 seconds.

2. Then do the following:

- Windows: Choose Start> Programs> SANView_V4.1> SVClient

- Solaris: /usr/local/bin/SANView_V4.1/SVclient

The Client prompts you to confirm the address of the Softek SANView Server (DNS name or IP Address), then for the log-on access level, corresponding password, and user profile.

� To find out whether the Host Agent is running:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> status


� To start the Host Agent:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> start


� To stop the Host Agent:

• Windows: Choose Start> Programs> SANView_V4.1> Local_SVHostAgent> stop


��


C

Event Messages

• Overview 157

• SAN Events 157


softe

k.fu

jitsu

.com

App

endi

x C

– O

verv

iew

OverviewThis document lists some of the most common event messages for Softek SANView.

The SAN Events are listed by severity. Also included are the event messages, descriptions, and recommended actions.

The severity levels are listed below:

• Info (green)—reading of the configuration file, trap enabling or disabling, improvement in device health, or indication of event storm. These messages are for informational purposes and normally no action is required.

• Warn (yellow)—device health decline; deletion of an agent, hub, or stack; device being reset or becoming inactive; attempt to delete a nonexistent agent; duplicate MAC addresses on agents. This message occurs when something changes in the SAN which may or may not require the attention of the administrator.

• Fail (red)—change in device health to failure, duplicate IP Address detected. This message requires action as a major change has occurred in the SAN. This normally requires user action to correct.

• Config (blue)—change in device health between Functional and Unused, device addition, device removal. A change has occurred in the SAN configuration. Informative - may be intentional or unintentional.

• Unknown (black)—severity level of device before initialization. Either uninitialized or event is not recognized by Softek SANView.

SAN Events

Severity Event Message Description Recommended Action

info Health: Unknown->Unused

The device or Port is currently not in use or is not recognized by Softek SANView.

Verify that the change is expected. No action required.

info Health: Failure->Unused

The device and/or Port is not in use.


info State: Active The agent is participating in the SAN.


info Health: Attention->Unused

The device and/or Port is not in use.


info Health: Unknown->Functional Status: OK

The device and/or Port is operational.




SO

FTE

KA

ppen

dix

C –

SA

N E

vent

s

158

config Health: Unknown->Functional

The device and/or Port is now connected and operational.


config Added device A device has been added to the SAN.


config Added Agent An agent has been added to the SAN.


config Health: Unused->Functional

The device and/or Port is now connected and operational.


config Health: Unknown->Functional, State: Active

The agent or device is now operational and participating in the SAN.


config Health: Failure->Functional

The device and/or Port has recovered from a failure state and is now operational.


config Health: Attention ->Functional

The device and/or Port has recovered and is now operational.


config Health: Unused->Functional Status: OK

The device and/or Port has become operational.


config Health: Failure->Functional, State: Active

The agent or device has recovered from a failure state and is now operational.


config Health: Unknown->Unused, State: Unknown

The agent or device is not operating, most likely unused.


warning Health: Unknown->Attention, Link Down; Inoperative

The device and/or Port is inoperative due to a bad link.

Make sure that the Inter-Switch Links (ISLs) are up and running and all connections are functional.

warning Health: Functional->Attention, Link Down; Inoperative

The device and/or Port is operational but cannot communicate with the SAN because of a bad link.




softe

k.fu

jitsu

.com

App

endi

x C

– S

AN

Eve

nts

��

warning Health: Functional->Attention, Pwr2: Off

The switch is working properly but the second power supply is off.

Make sure that the redundant power supply is plugged in or replace it as soon as possible.

warning Health: Functional->Attention, Link Down; LoopInit

The device is operational but there is a bad link which is causing a LIP.


warning Health: Unknown->Attention, Link Down; LoopOpenInit1

The device is operational but there is a bad link which is causing a LIP.


fail Health: Unknown->Failure, Faulty Module

The device or port is non-operational due to a failed SFP or GBIC transceiver.

Make sure that the transceiver is plugged in or replace it as soon as possible.

fail Health: Unused->Failure, State: Unknown

The agent has failed and is not communicating with the SAN.

Make sure that the transceiver is plugged in or replace it as soon as possible.

unknown

Health: Unknown->Unused

The device and/or Port is currently not in use or is not recognized by Softek SANView.

No action required.




D

Reference Materials

• System Addresses 163

• Loop ID—AL_PA Cross References 164

• Ordered Set Definitions 166

• Fibre Channel References 168


softe

k.fu

jitsu

.com

App

endi

x D

– S

yste

m A

ddre

sses

This section contains information on obtaining reference material for Fibre Channel.

System AddressesYou can easily find or look up the DNS name and/or IP Address of a particular system. You can also assign an IP Address to a Windows system.

� To find the system’s DNS name from a known IP Address (or vice versa):

• Use the nslookup command. For example, to find the DNS name for a host with an IP Address of 168.16.4.20, type: nslookup 168.168.4.20 at a command prompt.

� To look up the system’s DNS name (“Host Name”) and/or IP Address:

• Windows: Use the ipconfig.exe file.

At a command prompt, type: ipconfig /all

• Solaris: Type: ifconfig -a

� To assign an IP Address to a Windows system (TCP/IP must be installed):

• Choose Settings> Control Panel from the Start menu, then select Network> Protocols tab> TCP/IP Protocol (properties)> IP Address tab.

(To install TCP/IP, see the Windows CD and related documentation, then make sure the Service Packs are updated afterwards.)

NOTE Windows’ ipconfig /all command displays the IP addresses of any existing DNS Servers and the enabled/disabled status of Dynamic Host Configuration Protocol (DHCP). If no DNS Server is listed, make sure all agents’ IP Addresses are included in the system’s Host name file. If DHCP is enabled, the system’s DNS name (instead of IP address) should be entered when prompted during the installation of Softek SANView.



SO

FTE

KA

ppen

dix

D –

Loo

p ID

—A

L_P

A C

ross

Ref

eren

ces

164

Loop ID—AL_PA Cross References

Arbitrated Loop Physical Addresses

AL_PA Loop ID AL_PA Loop ID AL_PA Loop ID

(hex) (hex)(decimal) (hex) (hex)

(decimal) (hex) (hex)

(decimal)

EF 00 0 A3 2B 43 4D 56 86

E8 01 1 9F 2C 44 4C 57 87

E4 02 2 9E 2D 45 4B 58 88

E2 03 3 9D 2E 46 4A 59 89

E1 04 4 9B 2F 47 49 5A 90

E0 05 5 98 30 48 47 5B 91

DC 06 6 97 31 49 46 5C 92

DA 07 7 90 32 50 45 5D 93

D9 08 8 8F 33 51 43 5E 94

D6 09 9 88 34 52 3C 5F 95

D5 0A 10 84 35 53 3A 60 96

D4 0B 11 82 36 54 39 61 97

D3 0C 12 81 37 55 36 62 98

D2 0D 13 80 38 56 35 63 99

D1 0E 14 7C 39 57 34 64 100

CE 0F 15 7A 3A 58 33 65 101

CD 10 16 79 3B 59 32 66 102

CC 11 17 76 3C 60 31 67 103

CB 12 18 75 3D 61 2E 68 104

CA 13 19 74 3E 62 2D 69 105

C9 14 20 73 3F 63 2C 6A 106

C7 15 21 72 40 64 2B 6B 107

C6 16 22 71 41 65 2A 6C 108

C5 17 23 6E 42 66 29 6D 109

C3 18 24 6D 43 67 27 6E 110

BC 19 25 6C 44 68 26 6F 111

BA 1A 26 6B 45 69 25 70 112


softe

k.fu

jitsu

.com

App

endi

x D

– L

oop

ID—

AL_

PA

Cro

ss R

efer

ence

s

B9 1B 27 6A 46 70 23 71 113

B6 1C 28 69 47 71 1F 72 114

B5 1D 29 67 48 72 1E 73 115

B4 1E 30 66 49 73 1D 74 116

B3 1F 31 65 4A 74 1B 75 117

B2 20 32 63 4B 75 18 76 118

B1 21 33 5C 4C 76 17 77 119

AE 22 34 5A 4D 77 10 78 120

AD 23 35 59 4E 78 0F 79 121

AC 24 36 56 4F 79 08 7A 122

AB 25 37 55 50 80 04 7B 123

AA 26 38 54 51 81 02 7C 124

A9 27 39 53 52 82 01 7D 125

A7 28 40 52 53 83 00 7E 126

A6 29 41 51 54 84 --- 7F 127

A5 2A 42 4E 55 85 --- --- ---

Arbitrated Loop Physical Addresses

AL_PA Loop ID AL_PA Loop ID AL_PA Loop ID

(hex) (hex)(decimal) (hex) (hex)

(decimal) (hex) (hex)

(decimal)



SO

FTE

KA

ppen

dix

D –

Ord

ered

Set

Def

initi

ons

166

Ordered Set DefinitionsOrdered sets that are specific to Fibre Channel Arbitrated Loop consist of primitive signals (Sig) and primitive sequences (Seq). Signals typically indicate actions (events) while sequences indicate states (conditions).

Prerequisites for ordered set recognition depend on the type of ordered set and the loop protocol being used. While signals typically need only to occur once for recognition, sequences are usually transmitted continuously until the state changes, with a minimum requirement of three consecutive occurrences before the sequence is recognized and action is taken. Many loop protocols require that a specific sequence be transmitted continuously until it has traveled completely around the loop and is received by the original sender.

When you use the Diagnostics dialog box to detect the presence or absence of these ordered sets, select Match Sig (1x) for signals and Match Seq (3x) for sequences.

AbbreviationPrimitive Type Definition

ARB(F0) Sig During loop initialization, ARB (F0) signals loop Ports that an initialization master has been selected and the LISM phase of initialization is complete. ARB(F0) is also used as the current fill word in place of IDLE when a node has possession of the loop.

ARB(F7) Sig Allows a Port without an AL_PA to temporarily use AL_PA=x’F7' to arbitrate and begin a loop initialization.

ARB(FF) Sig Used as a substitute for the IDLE primitive in some implementations when a vendor’s equipment is sensitive to jitter. Reduces electromagnetic interference (EMI).

ARB Sig Indicates that a Port is arbitrating for access to the loop and is in the arbitrating state.

CLS Sig Sent by a loop Port to begin the process of closing the current loop circuit.

Comma Sig The Comma contains a series of 7 bits, which will not occur in any valid Data Transmission Character, or combination of characters. The Comma notifies the receiver that the transmitter is sending control information rather than data information.

EOF Sig End of frame (EOF) delimiters are ordered sets that immediately follow the CRC of a frame and signal the frame’s end.

IDLE Sig A transmission word between frames that contain no essential information. Used to maintain link activity and indicate the end of a fairness window.


softe

k.fu

jitsu

.com

App

endi

x D

– O

rder

ed S

et D

efin

ition

s

LPB Seq Causes a designated Port or all Ports to set the LP_Bypass variable and optionally activate a control line to an external Port bypass circuit, if present.

LPE Seq Causes a designated Port or all Ports to reset the LP_Bypass variable and optionally deactivate a control line to an external Port bypass circuit, if present.

LIP Seq Loop Initialization Primitive.

LIP(F7,F7) Seq Indicates that the loop Port in the initializing state is requesting loop initialization.

LIP(F8,F7) Seq Indicates that the loop Port in the initializing state is requesting loop initialization due to a loop failure. The loop Port does not currently have a valid AL_PA and uses ‘F7’ instead.

LR Seq Link Reset is used to abnormally end a Class-1 connection.

LRR Seq Link Reset Response is used to reset the receiving Port after ending a Class-1 connection.

MRK Sig Used as a synchronization primitive.

NOS and OLS Seq The Fibre Channel standard defines the Not Operational and Offline primitive sequences link initialization in a point-to-point or Fabric-attached link. The loop Port state machine recognizes these primitive sequences while in selected states in order to support the associated protocols should the loop Port receive one of these sequences.

OPN Sig The Port owning the Loop uses OPN commands (either OPNyx or OPNyy) to open communications with another Port on the Loop. OPNyx indicates a full-duplex communication mode while OPNyy indicates a half-duplex communication mode.

R_RDY Sig The R_RDY primitive signal indicates that the receiving node is ready for a frame to be transmitted over the link.




SO

FTE

KA

ppen

dix

D –

Fib

re C

hann

el R

efer

ence

s

168

Fibre Channel ReferencesThe following books give useful information about Fibre Channel.

• Alan F. Benner, Fibre Channel. McGraw-Hill, 1996. ISBN 0-07-005669-2.

• Tom Clark, Designing Storage Area Networks. Addison Wesley Longman, 1999. ISBN 0-201-61584-3.

• Jan Dedek, Fibre Channel - The Basics. ANCOT Corporation, 1997. ISBN 0-9637439-3-7.

• Marc Farley, Building Storage Networks. Osborne Press, 1999. ISBN 0-07-212050-9.

• Robert Kembel, Arbitrated Loop. Connectivity Solutions, 1996. ISBN 0-931836-82-4.

• Robert Kembel, A Comprehensive Introduction. Connectivity Solutions, 1998. ISBN 0-931836-84-0.

• Robert W. Kembel, Fibre Channel Switched Fabrics. Northwest Learning Associates, Inc., 2001. ISBN 0-931836-71-9.

��

SOF Sig Start of frame (SOF) delimiters are ordered sets that immediately precede the frame content. The SOF delimiter is always transmitted on a word boundary.

SOFc1 Sig “SOF Connect Class 1” is used to request a Class 1 Dedicated Connection. The delimiter may also identify the start of the first sequence, functioning as an implicit SOFi1.

SOFi2 Sig The first sequence of a Dedicated connection is initiated with SOFc1. All subsequent sequences within that Dedicated Connection are delimited with “SOF Initiate Class 1”.

SOFi3 Sig “SOF Initiate Class 3” is used on the first Frame to initiate a Sequence for Class 3 service.



softe

k.fu

jitsu

.com

Glo

ssar

y

Glossary

For further information on networkingterms, see the dictionary at the StorageNetworking Industry Association’s (SNIA’s)website: www.snia.org (within the “resourcecenter”). See also the T11 website at:www.t11.org.

AAgent

An interface used by a device to exchangeevent messages, configuration settings, andother information with managementapplications. All device managementcommands issued through Softek SANVieware communicated through the device’sagent.

AL_PAArbitrated Loop Physical Address; a one-bytevalue used to identify a Port in an ArbitratedLoop topology. The value of the AL_PAcorresponds to bits 7:0 of the 24-bit NativeAddress Identifier.

Arbitrated LoopA Fibre Channel topology structured as aloop and requiring a Port to successfullyarbitrate prior to establishing a circuit to sendand/or receive frames.

DDiscovery

For Softek SANView, the process by whichthe Server broadcasts queries to your subnet(or to the specified devices) for standards-compliant SAN agents and devices andidentifies their type. A device must bediscovered by Softek SANView before it canbe monitored and managed.

DNSDomain Name Service; a distributed dataquery service that translates host names intoInternet (or network) addresses.

DNS NameThe host name that relates to the host’s IPAddress, as noted in the Domain NameService.

EE_Port

Expansion Port; a switch Port that isconnected through an Inter-Switch Link(ISL) to another switch Port. See also: ISL.

Enclosure StatusStatus of a device’s fans, airflow, temperature,power supplies, and/or battery.

FF_Port

Fabric Port; a switch Port that is not capableof Arbitrated Loop operations and isconnected to a single N_Port. (Definitionfrom Robert W. Kembel, Fibre ChannelSwitched Fabrics. Northwest LearningAssociates, Inc., 2001. ISBN 0-931836-71-9.)

FabricA switch topology—consisting of one ormultiple Fibre Channel switches—in whichdata can be physically transmitted betweenany two switch Ports.

FC-FLAFibre Channel - Fabric Loop Attachmentstandard, which specifies Fibre Channeloptions between Public NL_Ports and Portsof these types: other Public NL_Ports,FL_Ports, and N_Ports. Refer to thespecification on the T11 website(www.t11.org) for more information.

Fibre ChannelFibre Channel is a data transfer interfacetechnology that maps several commontransport protocols including IP and SCSI,allowing it to merge high-speed I/O andnetworking functionality in a singleconnectivity technology, at speeds of 1- or 2-gigabits per second. Fibre channel is an openstandard as defined by ANSI and OSI



Glo

ssar

y

170

SO

FTE

K

standards and operates over copper and fiberoptic cabling at distances of up to 10Kilometers. It is unique in its support ofmultiple inter-operable topologies includingpoint-to-point, arbitrated-loop andswitching and it offers several qualities ofservice for network optimization. With itslarge packet sizes, Fibre Channel is ideal forstorage, video, graphic and mass data transferapplications.

FirmwareSoftware stored in read-only memory (ROM)or programmable ROM (PROM) thatcontrols the operation of the device. Newfirmware can be easily downloaded to adevice to upgrade its capabilities.

FL_PortA switch Port that is capable of ArbitratedLoop operations and is connected to one ormore NL_Ports in an Arbitrated Looptopology. (Definition from Robert W.Kembel, Fibre Channel Switched Fabrics.Northwest Learning Associates, Inc., 2001.ISBN 0-931836-71-9.)

Flash MemoryA type of constantly-powered nonvolatilememory that can be erased andreprogrammed in blocks or chips (ratherthan bytes) for speedy updates.

FLOGIFabric Login; the process used by nodes toestablish a logical connection to a switch.

FSPFFabric Shortest Path First; the standardrouting protocol for Fibre Channel switchesand Fabrics. See also: RIP.

Full-Duplex TransmissionTransmission in both directions,simultaneously (transmitting on one,receiving on the other).

GGBIC

Giga-Bit Interface Converter Module. OpenStandard developed by Vixel Corp., Sun,Compaq, and Amp. Industry’s first hotpluggable, gigabit transceiver.

HHBA

Host Bus Adapter; used as the interfacebetween a host (computer) and a FibreChannel network.

HostA computer to which disks, disk subsystems,or file servers are attached and accessible fordata storage and input/output operations.Mainframes, servers, workstations, andpersonal computers are hosts.

HubA device to which nodes on a multi-point busor loop are physically connected. Unlikeswitches, hubs do not aggregate bandwidth.Hubs are commonly used in Ethernet andFibre Channel networks to improve themanageability of physical cables and isolatefailures.

IInitiator

The system component that originates input/output commands over a bus or network.Hosts are initiators.

ISLInter-Switch Link; a link directly connectingone switch’s E_Port to another switch’sE_Port.

JJBOD

Just a Bunch Of Disks. Originally used tomean a collection of disks without thecoordinated control provided by controlsoftware; today the term JBOD most oftenrefers to a cabinet of disks whether or notRAID functionality is present.

JINI™A SUN Microsystems specification forbuilding communities of cooperatingnetwork services. Softek SANView’sadvanced architecture is enabled by JINI.


softe

k.fu

jitsu

.com

Glo

ssar

y

LLED

Light-Emitting Diode. A status indicator onan electronic device (such as a hub or switch).

LinkA transmit/receive connection between twoFibre Channel Ports.

LIPLoop Initialization Primitive; used inArbitrated Loop topologies to initiate anaddressing procedure, indicate a loop failure,or reset a node.

MMAC Address

The hardware address of a device connectedto a network. MAC stands for Media AccessControl, which is the interface between anode's (device’s) Logical Link Control andthe network's physical layer.

Mb/sMegabits per second, 1,024,000 bits persecond.

MB/sMegabytes per second, 8,192,000 bits persecond. One byte = 8 bits.

MIBManagement Information Base; an SNMPstructure used to manage devices andapplications.

ModuleA Softek SANView Module is a softwaresubset that allows Softek SANView todiscover, monitor, and manage specific SANdevices. Options include specializeddiscovery, data collection and interpretation,graphical user interfaces, and launch—withcontext—of alternate management tools(such as Telnet or Web-based tools).

NN_Port

A Port within a node that is assumed to beincapable of Arbitrated Loop operations.(Definition from Robert W. Kembel, FibreChannel Switched Fabrics. Northwest

Learning Associates, Inc., 2001. ISBN 0-931836-71-9.)

NL_PortA Port within a node that is capable ofArbitrated Loop operations. (Definition fromRobert W. Kembel, Fibre Channel SwitchedFabrics. Northwest Learning Associates, Inc.,2001. ISBN 0-931836-71-9.)

NodeAn entity with one or more N_Ports orNL_Ports. SAN devices are usually nodes.

Node WWNNode World-Wide Name; a 64-bit worldwideunique identifier assigned to a node. See also:WWN.

OOrdered Set

A transmission word (sequence of four 10-bitcode bytes) with a special character in its first(left-most) position and data characters inthe remaining three positions. Used for low-level Fibre Channel link functions such asframe transport, initialization, and mediaaccess.

PPLOGI

A Port-to-Port login process used byinitiators to establish sessions with targets.

PollingFor Softek SANView, the periodic queryingof managed device agents to update thedisplay of health state, configuration, andother attributes. Queries of managed deviceagents are spread uniformly throughout thepoll interval.

PortAn access point on a device (node) to whichanother device attaches.

Port WWNPort World-Wide Name; a 64-bit worldwideunique identifier assigned to a Port. See also:WWN.

Port-based ZoningA feature of some switches and hubs by whichdevices on a particular Port communicateonly with devices on specified Ports.



Glo

ssar

y

172

SO

FTE

K

PRLIFibre Channel Process Login; required bysome protocols or applications, and used tocommunicate FC-4 specific information.

RRAID

Redundant Array of Independent Disks. Afamily of disk array data protection andmapping techniques.

RIPRouting Information Protocol; a routingprotocol defined in STD 34, RFC 1058, andupdated by RFC 1388. See also: FSPF.

RMIRemote Method Invocation; a protocol thatJava applications use to communicate over anIP network. Softek SANView uses RMI forClient/Server communication.

RouterA device that forwards packets (betweennetworks) based on network layerinformation and routing tables.

SSAN

Storage Area Network; a configuration ofinterconnected systems and storage devicesthat communicate through storage commandprotocols.

SFPSmall Form-Factor Pluggable. Thesetransceivers are fully compliant with theGigabit Ethernet standard and occupy lessthan half the board space of the existing GBICproducts.

SNMPSimple Network Management Protocol; aprotocol used for network management andmonitoring functions.

SNMP TrapSee Trap.

SNSSimple Name Server; a directory service on aswitch that simplifies discovery of devices.(SNS allows initiators to find targets.)

SwitchA device to which several devices attach.Unlike hubs, switches typically have internalbandwidth that is a multiple of linkbandwidth. A typical switch canaccommodate several simultaneous full linkbandwidth transmissions between differentpairs of devices.

TTarget

A system component that receives input/output commands. Storage devices aretargets.

TopologyThe logical and/or physical arrangement ofstations on a network. Fibre Channeltopologies include point-to-point, ArbitratedLoop, and switched Fabric.

TransceiverA device that converts one form of signalingto another for both transmission andreception. SFPs and GBICs are transceivers.

TrapAn SNMP message used to signal that anevent has occurred. Trap configuration isavailable through Softek SANView for somedevices, depending on the module used todiscover and manage them. See also: SNMP.

WWWN

World-Wide Name; a 64-bit worldwideunique identifier assigned to a Fibre Channelentity. Both nodes and Ports can haveWWNs, respectively called “Node WWNs”and “Port WWNs” (or “WWPNs,” whichstands for “World-Wide N_Port_Names”).

WWN ZoningA feature of some switches by which devicesare segregated by their World-Wide Names(or some variant, such as World-WideN_Port_Names, or WWPNs).


softe

k.fu

jitsu

.com

Inde

x

Index

AAccess Levels (Passwords) 110Administration Panel

Discovery tab 22Agent tab 24Agents 36

Discovering 109AL_PA--Loop ID Cross References 164Analysis Modules

configuring 78Detect Port Link Failures 80Port Configuration 79

Archiving Tab 26Audience for this Manual iiiAutomatic Notification Via Email 67

BBacking Up the Database 147Back-of-box View 137

CChecking Health Status 63Color-Independent Indication of Device Health

38Condition Log 82Condition Reports 84

DDatabase

backup 147restoring 148

Default Passwords 110Detach Frames 35Detail View 46

devices 47enclosures 47groups 46

Detail viewdetaching 46re-attaching 46

Detect Port Link Failures Analysis Modules 80Device Events 65

Logging 107

Device Ports, Showing 104Devices 36

Detail view 47Discovering 109Finding 52submenu 45

Discovering Agents and Devices 21, 109Discovering via Routers 21Discovery

agents outside local subnet 58Discovery Tab 21

EEmail Notification, Automatic 67Email Notifications 18

Severity Levels 19Enabling Features 111Enclosures

adding devices 44creating 44Detail view 47removing devices 44viewing contained devices 44

Event Messages 157Events

Fail-Marked 19Log Files 19messages 157

FFail-Marked Events 19Features, Enabling 111Fibre Channel References 168File Menu 103Finding Devices 52

GGlossary 169Graphing 92Group Path Listing 45Grouping 49Groups

adding devices 43



Inde

x

174

SO

FTE

K

creating 43Detail view 46removing devices 43viewing 49viewing details 43

HHBAs

Understanding HBA Displays 135Health States, Device (Color-Independent) 38Health Status 136Health, Checking 63Help Menu 111Historical and Real-time Graphing View 92Host Agent

Fibre Channel HBA 133Running the 134

IInterpreting Port LEDs 69

LLayout

Topology Map view 45LED Descriptions (Port LEDs) 69Levels of Access 110License Information 27Licenses 111Locating World Wide Names 136Log Files, Location 27Log Rollover Size 19Log Tab 19Logging Device Events 107Logging SAN Events 106Logs

Condition Logs 82Loop ID--AL_PA Cross References 164

MMail Server for Email Notifications 18Map View 40Map view

Layout button 45Menus, Softek SANView Client

File 103Help 111Options 106

Tools 108View 104

Monitor Access Level Restrictions 110

NNotification Tab 18

OOptions Menu 106Ordered Set Definitions 166Overview Window 48

Yellow Box-of-Focus 48

PPasswords, Default 110Performance Data Management 90

Archive tab 90Delete tab 91enabling archiving option 26

Performance Management 90Persisting the SAN 22PFCA HBA Module 141Poll Interval 108Port Configuration Analysis Module 79Port Details View 138Port Statistics View 140Ports, Showing for Devices 104Printing the Topology 103Profiles 32

RRecorded Events 140Redrawing Tree & Topology Frames 109Refreshing (Redrawing) 109Reports

Condition Reports 84Restoring the Database 148Restrictions of Monitor Access Level 110Root Directory, Softek SANView 27Router-Connected Discovery 21

SSAN Administration Window

Agent tab 24Archiving tab 26Discovery tab 21


softe

k.fu

jitsu

.com

Inde

x

Log tab 19Notification tab 18Scheduler tab 23SNMP Traps tab 25

SAN Configurationpersistence 22

SAN Events 64, 157Logging 106

Saving Topology Snapshot 53Scheduler Interval 23Scheduler Tab 23Scheduling Tasks 110Severity Levels, Email Notifications 19SNMP Traps Tab 25Sorting

options 50Status, Checking 63Submenu

Device 45Topology Frame 45

Subnet Discovery 21discovering agents outside local subnet 58

SVserverconfig.ini file 27

TTasks, Scheduling 110Terms

See Glossary 169Thresholds

configuring 70launch commands 72statistics 72

Tool tipsTree Frame 50

Toolbar buttonsTopology Frame 41

Tools Menu 108Topology

Snapshot 53Topology Frame

buttons 41detaching 35Detail view 46Device submenu 45Layout button 45Map view 40resizing 35Submenu 45

Topology, Printing 103Trap Port 25

Trap Settings 25Tree Frame

detaching 35grouping options 49resizing 35sorting options 50Tool tips 50

Troubleshooting Issues 76

UUninstalling Softek SANView 12Upgrading Softek SANView 13User authorization

profiles 32

VView Menu 104

WWorld-Wide Name Zoning (WWN) 93

conditions 94configuring 94understanding 93

ZZoning, WWN 93

conditions 94configuring 94understanding 93



softe

k.fu

jitsu

.com

Rev

isio

n H

isto

ry

Revision History

This revision history lists all revisions of this publication and their effective dates.

Revision Level Change Summary

ML-144912-001August 2001

Original release of the Softek SANView User Guide.

ML-144912-002November 2001

This is the second release of the Softek SANView User Guide. This edition provides technical and editorial updates and replaces all previous editions of this manual.

ML-145012-001June 2002

This is the first release of the Softek SANView User Guide. This edition provides technical and editorial changes for Version 4, Release 0, and replaces all previous editions of this manual.

ML-145012-002October 2002

This is the second release of the Softek SANView User Guide. This edition provides technical and editorial changes for Version 4, Release 1, and replaces all previous editions of this manual.



san insite professional user’s guide - fujitsu · sanview client; discovery, monitoring, and...

Documents