Module Guide - Fujitsusoftware.fujitsu.com/jp/manual/fm_e/d025c114/b1jn5541/01/... ·...

Module Guide

vi

Revision NoticeThis is the first release of this manual. A complete revision history is provided at the end of the manual.AbstractThe Softek SANView Modules - Reference Guide (ML-144914-001) describes the features and functionality of Vixeldevices, Softek SANView windows and dialog boxes used for Vixel devices, and Vixel-specific parameters. For Further InformationIf you wish to obtain further information about the Fujitsu Softek product discussed in this publication, contactyour Fujitsu Softek Marketing Representative, or write to Fujitsu Softek Marketing Communications, Mail Stop315, Sunnyvale, CA 94085.Ordering Additional PublicationsIf you wish to order additional copies of this publication or publications related to the products described inthis manual, call (800) 1-866-6SOFTEK worldwide. Reader Comment Form A reader comment form is provided at the end of this manual. If this form is not available, comments andsuggestions may be sent to Fujitsu Software Technology Corporation, Enterprise Publishing Services, Mail Stop323, P.O. Box 3470, Sunnyvale, CA 94088-3470. All comments and suggestions become the property of FujitsuSoftware Technology Corporation.Restriction On UseThe information contained in this manual is the licensed property of Fujitsu Software Technology Corporation.Use of the information contained herein is restricted pursuant to the terms and conditions of a license agreement.Fujitsu Softek and Softek SANView are trademarks of Fujitsu Software Technology Corporation.Vixel and SAN InSite Professional are trademarks of Vixel Corporation.Microsoft and Windows are registered trademarks and Windows NT is a trademark of Microsoft Corporation.All other trademarks and product names are the property of their respective owners.© 2001 Fujitsu Software Technology Corporation.All rights reserved. Printed in U.S.A.All specifications are subject to change without notice.

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION

Contents

Preface

Chapters

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What is Softek SANView? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Softek SANView Brocade Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Discovering Brocade Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Understanding Brocade Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Finding Health Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Locating World-wide Names and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Understanding Recorded Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Viewing the Brocade Switch Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Viewing the Brocade Port Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Softek SANView CA Unicenter TNG Integration Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installation and Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Uninstallation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Understanding Vixel Device Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20To change the poll interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20To launch Softek SANView for Vixel device management . . . . . . . . . . . . . . . . . . . . 20

Troubleshooting Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Are the Vixel devices registered in DNS or the host name file? . . . . . . . . . . . . . . . . 21Were the correct CA Unicenter parameters entered during installation? . . . . . . . . 21Does the CA Unicenter 2D Map show the Vixel devices with Vixel icons and their DNS names (not IP Addresses)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Does the CA Unicenter 2D Map reflect health state changes from Softek SANView in a reasonable amount of time (15 seconds or so)? . . . . . . . . . . . . . . . . . . . . . . . . . . 22Are Softek SANView messages logged in the Unicenter TNG Console window (CA Unicenter’s message log)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

i

4 Softek SANView Chaparral Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Discovering Chaparral Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Understanding Chaparral Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Finding Health Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Locating World-wide Names and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Understanding Recorded Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 Softek SANView Crossroads Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Discovering Crossroads Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Understanding Crossroads Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


6 Softek SANView Fibre Alliance MIB Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Discovering FA MIB-compliant Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Understanding Device Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


7 Softek SANView Fibre Alliance HBA Module & Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Installing the FC HBA Module & Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

System requirements for the HBA Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43To install the HBA Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Running the HBA Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45To find out whether the HBA Proxy Server is running . . . . . . . . . . . . . . . . . . . . . . . 45To stop the HBA Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45To start the HBA Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45To view logged events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Discovering HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Understanding HBA Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


8 Softek SANView Gadzoox Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Features & Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Discovering Gadzoox Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

ii

Understanding Gadzoox Displays in Softek SANView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Finding Health Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Locating World-wide Names and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Understanding Recorded Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Viewing the Gadzoox Hub Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figures

Tool Tips for a Brocade Device in Tree Frame and in Topology Frame . . . . . . . . . . . . . . . . . . . . . . . . 10SAN Events frame (isolated) showing events recorded for a Brocade 2400 . . . . . . . . . . . . . . . . . . . . 11Brocade Switch Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Brocade Port Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Vixel devices shown in CA Unicenter’s 2D Map view, with right-click menu visible . . . . . . . . . . . 17Vixel device events shown in the Unicenter TNG Console window . . . . . . . . . . . . . . . . . . . . . . . . . . 17Server Processes After Installation of CA Unicenter TNG Integration Module . . . . . . . . . . . . . . . . . 18Tool tips for a Chaparral device in Tree frame and in Topology frame . . . . . . . . . . . . . . . . . . . . . . . . 27SAN Events frame (isolated) showing events recorded for a Chaparral router . . . . . . . . . . . . . . . . . 28Tool tips for a Crossroads device in Tree frame and in Topology frame . . . . . . . . . . . . . . . . . . . . . . . 33SAN Events frame (isolated) showing events recorded for a Crossroads device . . . . . . . . . . . . . . . . 33Tool tips in Tree and Topology frames for a device managed through the FA MIB Module . . . . . . 39SAN Events frame (isolated) showing events recorded for a device managed through the FA MIB Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40System overview (FC-compliant HBA and Softek SANView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Tool tips for two HBAs on one host, in Tree frame and in Topology frame . . . . . . . . . . . . . . . . . . . . 47SAN Events frame (isolated) showing events recorded for an HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Tool tips for a Gadzoox device in Tree frame and in Topology frame . . . . . . . . . . . . . . . . . . . . . . . . . 53SAN Events frame (isolated) showing events recorded for a Gadzoox hub . . . . . . . . . . . . . . . . . . . . 53Gadzoox Hub Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Tables

Softek SANView Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viBrocade Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Brocade Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11CA Unicenter Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Chaparral Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Chaparral Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Crossroads Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Crossroads Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FA MIB Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38FA MIB Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40FA HBA Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46FA HBA Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Gadzoox Health State Color-Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Gadzoox Event Message Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

iii

Preface

Description of the Manual

This manual describes:

• Features and functionality of Vixel devices.

• Softek SANView 3.2 windows and dialog boxes used for Vixel devices.

• Vixel-specific parameters.

If you have any questions or need more information, please contact your Fujitsu Softek representative.

Audience for this Manual

This manual is intended for Softek SANView customers and Softek SANView support personnel.

Contents of this Manual

Chapter DescribesIntroduction What Softek SANView isSoftek SANView 3.2 Brocade Module

Features & supported devicesDiscovering Brocade devicesUnderstanding Brocade displays in Softek SANView

Softek SANView 3.2 CA Unicenter TNG Integration Module

FeaturesInstalling the moduleUnderstanding Vixel displays Troubleshooting installation and configuration

Softek SANView 3.2 Chaparral Module

Features & supported devicesDiscovering Chaparral devicesUnderstanding Chaparral displays in Softek SANView

Softek SANView 3.2 Crossroads Module

Features & supported devicesDiscovering Crossroads devicesUnderstanding Crossroads displays in Softek SANView

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION v

Con

tent

s of

this

Man

ual

vi

Softek SANView 3.2 Fibre Alliance MIB Module & Proxy

Features & supported devicesDiscovering FA MIB-compliant devicesUnderstanding device displays in Softek SANView

Softek SANView 3.2 Fibre Alliance HBA Module

Features & supported devicesInstalling the FC HBA module & proxyRunning the HBA Proxy ServerDiscovering HBAsUnderstanding HBA displays in Softek SANView

Softek SANView 3.2 Gadzoox Module

Features & supported devicesDiscovering Gadzoox devicesUnderstanding Gadzoox displays in Softek SANView


softe

k.fu

jitsu

.com

Not

atio

n C

onve

ntio

ns

Notation Conventions

Notices

At different locations throughout this manual information may appear in notes as follows:

� NOTE: This note clarifies or emphasizes text that precedes or follows it.

Softek SANView Notations

Item Convention Example

alias text "...device alias, tape1..."

application text aplpkg

command bold, uppercase CONNECT causes...

computer text "...two computers, machine_a and B1."

database when a pathwhen namedelse text

/aaa/bbbb/,/ccc, database......database named db1....alpha database...

default textunderscore

"...default for TIME is NO."TIME=YES|NO

field monospace, upper case The DISTRICT field on the System View display...

file name text Robotlog.dat performs... The tstdata file is named Robotlog.dat....uses the Robotlog.dat file to...

Windows file path text c:\Softek SANView\tables

Unix file path and commands

text in Courier format, bold /etc/init.d/volmgt stop

keyboard entry text, uppercase Press the ENTER key.

parameter/keyword monospace, UPPER CASE PAUSE keyword...NODEID parameter...

program text Use Sentutil.exe to... ...uses the program named Sentutil.exe...uses the Sentutil.exe program to...

viiLICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION

Rel

ated

Pub

licat

ions

viii

Related Publications

The following publications contain related information.

��

Softek SANView 3.2 Quick Start Guide(ML-144913-001)Softek SANView 3.2 User’s Guide(ML-144912-001)Softek SANView 3.2 Vixel Module Reference Guide(ML-144957-001)Softek SANView 3.2 Software Installation & Release Notes (SIRN)(ML-144915-001)


LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPO

1

Introduction

• What is Softek SANView? 3

RATION 1

2

softe

k.fu

jitsu

.com

Wha

t is

Soft

ek S

AN

Vie

w?

What is Softek SANView?

Softek SANView manages heterogeneous multi-vendor SANs, streamlining SAN management through the following features:

• Automatically detects and discovers host bus adapters (HBAs) and Fibre Channel Management Integration MIB (Fibre Alliance 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 the interconnections between SAN devices.

• 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, data collection and interpretation, graphical user interfaces, and launch of alternate management tools.

• Integrates with and reports events to Enterprise Management Applications such as CA Unicenter (when related Softek SANView Module is installed).

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

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

• Proactively monitors status and detects problems at every level, notifying 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. (MD5 is Message Digest 5, a public one-way hash function used for password encryption. MD5 is defined in RFC 1321.)

• Runs on UNIX and Windows®.

��

LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION 3


2

Softek SANView Brocade Module

• Features & Supported Devices 7

• Discovering Brocade Devices 8

• Understanding Brocade Displays in Softek SANView 8

RATION 5

6

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Brocade 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 of alternate management tools (such as Telnet or Web-based tools).

This module (like most Softek SANView Modules) is installed automatically as part of the Softek SANView Server.

Features & Supported Devices

The features specific to the Brocade Module follow.

• Health monitoring of Brocade® switch and ports, shown in Tree frame (left frame), Topology frame (right frame), Switch window, and Port window. Agent health is monitored in the Tree frame.

• Recorded events in SAN Events frame (lower frame) for addition/deletion of device agents and other health or status changes for devices and ports.

• Identification of device, ports, and port module types plus health status of device, ports, and switch enclosure in Switch window.

• Launch of alternate tools for device management (Telnet or Brocade WebTools) from Softek SANView’s Topology frame.

The Brocade Module supports the Brocade 2800, Brocade 2400, Brocade 2010, and Brocade 2050. To be managed with Softek SANView, the Brocade switches must meet the following requirements:

• The running firmware must be version 2.1 or 2.2.

� NOTE: To show Inter-Switch Links (ISLs) in Softek SANView, in addition to the device-port interconnections already shown, the switch must run version 2.2 firmware.

• Brocade’s WebTools management tool must be available, with the related HTTP server running under the same IP Address as the switch’s SNMP agent.


Dis

cove

ring

Bro

cade

Dev

ices

8

Discovering Brocade Devices

� NOTE: For discovery of Brocade switches to occur, the Brocade switches must have the default value “Fibre Channel Switch.” for the sysDescr variable (from MIB II).

You 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, while discovery before the Server starts is configured through the Softek SANView Server Configuration dialog box.

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 Server Configuration dialog box are retained across Server sessions.

Understanding Brocade Displays in Softek SANView

The Softek SANView Client shows Brocade device health status, unique identification, and recorded events. This information is shown in its Tree, Topology, and SAN Events frames and in the Brocade Switch window. The related Port windows show port type, state, health, and port module information.

� NOTE: Ports are numbered using Brocade’s numbering convention (that is, the first port is numbered “0”).

Device health status is updated according to the frequency (poll interval) set through Softek SANView.

To change the poll interval, choose Change Poll Interval from the Tools menu in Softek SANView’s main window.


softe

k.fu

jitsu

.com

Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

Finding Health Status

Health status for all managed devices (including those for this module) and their ports is shown in the relevant device window and in the Tree and Topology frames; health status for agents (including those for this module) 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 health bar at the top of the Softek SANView Client window. If the SAN health bar 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.

The events that cause changes to Brocade switch health status are logged in Softek SANView’s SAN Events frame. For more information, see Understanding Recorded Events on page 10.

Brocade Health State Color-Coding

Color of Icon Health State

Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

10

Locating World-wide Names and Other Information

� NOTE: For complete descriptions of tool tips, see the Softek SANView User’s Guide.

Brocade devices’ World-wide Names and other unique device, agent, and port identification are displayed through tool tips and through the Switch window. For information on the Switch window, see Viewing the Brocade Switch Window on page 12.

Tool Tips for a Brocade Device in Tree Frame and in Topology Frame

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). When the Log SAN events option is enabled, these events are also recorded on the Softek SANView Server system.

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>


softe

k.fu

jitsu

.com

Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

• 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>

When you choose SAN events... from the View menu, an isolated SAN Events frame appears. This isolated frame displays the latest 1000 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.

SAN Events frame (isolated) showing events recorded for a Brocade 2400

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

For more information about SAN Events, see the Softek SANView User’s Guide or online help.

Brocade Event Message Severities

Color of SAN Event Text Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown


Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

12

Viewing the Brocade Switch Window

The Brocade Switch window identifies port module types (such as “Copper”) and allows you to poll just the switch’s agent (rather than the entire SAN) for updated status.

To view the Brocade Switch window, right-click the desired Brocade icon in Softek SANView’s Topology frame and choose View Device (or double-click the icon).

Brocade Switch Window

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

• Module type and health status for each port

• Health status for device and enclosure (displayed in lower-left icon)


softe

k.fu

jitsu

.com

Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

The File menu and Help menu are standard across all Softek SANView windows.

The File menu has two options: Close window dismisses the current window (the device window). Exit Softek SANView Client exits the Softek SANView Client. (The Softek SANView Server continues to run.)

The Help menu has two options: Contents displays the online help and About Softek SANView... displays system and version information.

The Tools menu for the Brocade Switch window has a Poll now option to immediately poll the switch’s agent for status.

The GBIC icons supported for the Brocade Module are described below.

Viewing the Brocade Port Window

The Brocade Port window displays port state and other port-specific information.

To view a Port window, double-click the desired port in the Brocade Switch window.

Brocade Port Window

GBIC Icon GBIC Type

• Intra Copper• Inter Copper

• FC LW Laser (Longwave) • Serial FC LW Laser (Longwave)

• FC SW Laser (Shortwave)• Serial FC SW Laser (Shortwave)

• GBIC Unknown• No Module


Und

erst

andi

ng B

roca

de D

ispl

ays

in S

ofte

k SA

NV

iew

14

The Brocade Port window displays the following information:

• Port health

• Port Type

• State

• Port module information

• Health status

��



3

Softek SANView CA Unicenter TNG Integration Module

• Features 17

• Installing the Module 18

• Understanding Vixel Device Displays 20

• Troubleshooting Installation and Configuration 21

RATION 15

16

softe

k.fu

jitsu

.com

Feat

ures

The CA Unicenter TNG Integration Module integrates Softek SANView into the CA Unicenter TNG Framework. This module is called out as a separate component during Softek SANView installation.

Features

The features specific to the CA Unicenter TNG Integration Module follow.

• Vixel device identification, health display, and health updates in CA Unicenter’s 2D Map view.

• Easy Softek SANView launch from CA Unicenter’s 2D Map view to manage Vixel devices.

• Recording of Vixel device event messages (that show a change in health state) in the Unicenter TNG Console (CA Unicenter’s event log).

Vixel devices shown in CA Unicenter’s 2D Map view, with right-click menu visible

Vixel device events shown in the Unicenter TNG Console window


Inst

allin

g th

e M

odul

e

18

The figure below depicts the flow of information within the management server.

Server Processes After Installation of CA Unicenter TNG Integration Module

Installing the Module

The CA Unicenter TNG Integration Module supports Vixel integration with CA Unicenter TNG Framework when CA Unicenter TNG Framework and Softek SANView are installed on the same system. The module must be installed at the same time as all other Softek SANView components are installed.

System Requirements

• Operating System: WindowsNT® 4.0

• Other requirements as specified in the Softek SANView Quick Start Guide

Prerequisites

• CA Unicenter TNG Framework (2.2.0 or 2.2.1) is already installed.

• The IP Addresses of all Vixel devices are listed in either the Domain Name Service (DNS) or the hostname file on the system (typical location is C:\winnt\system32\drivers\etc\hosts).

Installation and Configuration Instructions

To install the CA Unicenter TNG Integration Module & Softek SANView Server (and other desired Softek SANView components):

1. Locate the desired Softek SANView Server system.

2. Make sure that CA Unicenter is already installed and that the system has been rebooted since CA installation.


softe

k.fu

jitsu

.com

Inst

allin

g th

e M

odul

e

� NOTE: To find out if you have Administrator privileges, 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.)

3. Log in as Administrator (or as an account with Administrator privileges).

4. Go to the CA Unicenter 2D Map view and find and delete all Vixel devices that have been discovered (or delete the subnet they are on).

5. Note: Deletion of Vixel devices from CA Unicenter ensures proper re-discovery and classification after installation. During installation, any Vixel devices in CA Unicenter’s repository that are properly classified as “Vixel_Hub” or “Vixel_Switch” are detected and automatically deleted, but improperly classified Vixel devices are not detected.

6. Insert the Softek SANView CD; if autorun is disabled, open the SIPro.exe file from the CD-ROM directory.

7. The Softek SANView installation window appears.

8. Follow the displayed instructions, making sure to click the Customize button when asked to choose an item for installation; in the Customize section, select the CA Unicenter TNG Integration Module and the Softek SANView Server. If other components are desired, be sure to select them now—all Softek SANView components for a system must be installed at the same time.

9. After Softek SANView installation, initiate and complete the CA Unicenter discovery process (ensure that the “Use Domain Name Server/Host File” checkbox configuration setting is checked).

10. Stop and restart the Softek SANView Server, then complete the Softek SANView discovery process for all devices that are to be monitored through CA Unicenter. (Discovery can be configured either before Server start through the Softek SANView Server Configuration dialog box or after Server start through the Client’s Tools menu.)

The CA Unicenter TNG Integration Module is now installed, configured, and running.

Uninstallation Instructions

The CA Unicenter TNG Integration Module is uninstalled along with all other installed Softek SANView components.

To uninstall Softek SANView, do the following:

• Windows: Choose Uninstall SIPro from the Start> Programs> Softek SANView> Softek SANView Server> menu.

• UNIX: Use the following shortcut: usr/local/bin/SIuninstall

Files or directories remaining after uninstallation may be deleted.


Und

erst

andi

ng V

ixel

Dev

ice

Dis

play

s

20

Understanding Vixel Device Displays

The CA Unicenter TNG Integration Module displays and continually updates Vixel device identification and health status within the Unicenter 2D Map view, logs Vixel device event messages (that show a change in health state) in CA Unicenter’s event log (the Unicenter TNG Console window), and facilitates the launch of Softek SANView for Vixel device management.

Vixel device identification matches the detected Vixel class (“Vixel_Hub” or “Vixel_Switch”).

Vixel health states (from Softek SANView’s SAN Events) are mapped to CA Unicenter’s health states, and the color indications are consistent with those displayed in Softek SANView. The Softek SANView device, agent, and port health states are mapped to CA Unicenter’s health states as follows.

The frequency (poll interval) of health updates shown in the Unicenter 2D Map view is the same as those shown in Softek SANView. For updates to occur, the Softek SANView Server (under which the CA Unicenter TNG Integration Module resides) must be running.

To change the poll interval

Choose Change Poll Interval from the Tools menu in Softek SANView’s main window.

To launch Softek SANView for Vixel device management

Right-click the desired Vixel device in the Unicenter 2D Map view and choose Softek SANView.

CA Unicenter Health State Color-Coding

Health State Color of Icon in Softek SANView or

CA UnicenterSoftek SANView CA Unicenter

Functional Normal Green

Attention Warning Yellow

Failure Critical Red

Unknown/Unused Unknown Gray


softe

k.fu

jitsu

.com

Tro

uble

shoo

ting

Inst

alla

tion

and

Con

figur

atio

n

Troubleshooting Installation and Configuration

When troubleshooting, first make sure that CA Unicenter and the Softek SANView Server are both running on the system. (Note that the CA Unicenter TNG Integration Module runs in tandem with the Softek SANView Server; the module is part of the Service that starts the Softek SANView Server.) Below are some items to check if the Vixel devices’ health states do not appear in CA Unicenter, or if their status does not update as expected.

Are the Vixel devices registered in DNS or the host name file?

Make sure that the IP Addresses for all managed devices are 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 [UNIX]). A sample host name file is shown below:

Were the correct CA Unicenter parameters entered during installation?

Open the VixelMainService.ini file in an editor such as Notepad and search for “CA_PARAMS” to view the entered repository, Softek SANView Server IP Address, user name, and password. (This file is located in C:\SANView\bin\ if the default installation directory was accepted.)

If any of the parameters are incorrect, uninstall all Softek SANView components, then reinstall, entering the correct parameters for the CA Unicenter TNG Integration Module (all Softek SANView components must be installed at the same time). In the sample list of parameters below (shown from a VixelMainService.ini file), the repository name is LDARROW_TNGDB, the Softek SANView Server IP Address is 24.244.18.141, the user name is sa, and the password is an empty string.

127.0.0.1 localhost

168.168.20.248 7200

168.168.20.71 2100

CA_PARAMS=-R LDARROW_TNGDB -url jini://24.244.18.141 -U "sa" -P ""


Tro

uble

shoo

ting

Inst

alla

tion

and

Con

figur

atio

n

22

Does the CA Unicenter 2D Map show the Vixel devices with Vixel icons and their DNS names (not IP Addresses)?

Does the CA Unicenter 2D Map reflect health state changes from Softek SANView in a reasonable amount of time (15 seconds or so)?

Are Softek SANView messages logged in the Unicenter TNG Console window (CA Unicenter’s message log)?

If not, make sure all installation instructions were followed, particularly the deletion of Vixel devices before installation of the CA Unicenter TNG Integration Module. (See Installing the Module on page 18.)

Reinstallation may be necessary.

��



4

Softek SANView Chaparral Module


• Discovering Chaparral Devices 25

• Understanding Chaparral Displays in Softek SANView 25

RATION 23

24

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Chaparral 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 of alternate management tools (such as Telnet or Web-based tools).



The features specific to the Chaparral Module follow.

• Health monitoring of Chaparral® routers, shown in Tree frame (left frame) and Topology frame (right frame). Agent health is monitored in the Tree frame.

• Recorded events in SAN Events frame (lower frame) for addition/deletion of device agents and other health or status changes for devices.

• Launch of Telnet from Softek SANView’s Topology frame.

The Chaparral Module supports the Chaparral FS1310 FC-SCSI Router. To be managed with Softek SANView, the Chaparral routers must be running firmware version R413 or M120.

Discovering Chaparral Devices

You 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 while discovery before the Server starts is configured through the Softek SANView Server Configuration dialog box.


Understanding Chaparral Displays in Softek SANView

The Softek SANView Client shows Chaparral device health status, unique identification, and recorded events. This information is shown in its Tree, Topology, and SAN Events frames.




Und

erst

andi

ng C

hapa

rral

Dis

play

s in

Sof

tek

SAN

Vie

w

26


Health status for all managed devices (including those for this module) and their ports is shown in the relevant device window and in the Tree and Topology frames; health status for agents (including those for this module) 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 health bar at the top of the Softek SANView Client window. If the SAN health bar 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.

Chaparral Health State Color-Coding


Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


softe

k.fu

jitsu

.com

Und

erst

andi

ng C

hapa

rral

Dis

play

s in

Sof

tek

SAN

Vie

w



Chaparral devices’ World-wide Names and other unique device, agent, or port identification are displayed through tool tips.

Tool tips for a Chaparral device in Tree frame and in Topology frame


� NOTE: Since port information is not available for this module, port state changes are not logged.


When you choose SAN events frame from the View menu, an isolated SAN Events frame appears. This isolated frame displays the latest 1000 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.


Und

erst

andi

ng C

hapa

rral

Dis

play

s in

Sof

tek

SAN

Vie

w

28

SAN Events frame (isolated) showing events recorded for a Chaparral router



��

Chaparral Event Message Severities

Color of SAN Event Text

Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown



5

Softek SANView Crossroads Module


• Discovering Crossroads Devices 31

• Understanding Crossroads Displays in Softek SANView 31

RATION 29

30

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Crossroads 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 of alternate management tools (such as Telnet or Web-based tools).



The features specific to the Crossroads Module follow.

• Health monitoring of Crossroads® devices, shown in Tree frame (left frame) and Topology frame (right frame). Agent health is monitored in the Tree frame.



The Crossroads Module supports the Crossroads 4200. To be managed with Softek SANView, the Crossroads devices must be running firmware version 2.2 9913a.

Discovering Crossroads Devices



Understanding Crossroads Displays in Softek SANView

The Softek SANView Client shows Crossroads device health status, unique identification, and recorded events. This information is shown in its Tree, Topology, and SAN Events frames.




Und

erst

andi

ng C

ross

road

s D

ispl

ays

in S

ofte

k SA

NV

iew

32


Health status for all managed devices (including those for this module) and their ports is shown in the relevant device window and in the Tree and Topology frames; health status for agents (including those for this module) is shown in the Tree frame.




Crossroads Health State Color-Coding


Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


softe

k.fu

jitsu

.com

Und

erst

andi

ng C

ross

road

s D

ispl

ays

in S

ofte

k SA

NV

iew



Crossroads devices’ World-wide Names and other unique device, agent, or port identification are displayed through tool tips.

Tool tips for a Crossroads device in Tree frame and in Topology frame




SAN Events frame (isolated) showing events recorded for a Crossroads device


Und

erst

andi

ng C

ross

road

s D

ispl

ays

in S

ofte

k SA

NV

iew

34



��

Crossroads Event Message Severities


Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown



6

Softek SANView Fibre Alliance MIB Module


• Discovering FA MIB-compliant Devices 37

• Understanding Device Displays in Softek SANView 37

RATION 35

36

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Fibre Alliance MIB Module (FA MIB 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 of alternate management tools (such as Telnet or Web-based tools).

The FA MIB Module enables management of all devices that comply with the Fibre Alliance MIB.



The features specific to the FA MIB Module follow.

• Health monitoring of devices that are compliant with the Fibre Alliance MIB, shown in Tree frame (left frame) and Topology frame (right frame). Agent health is monitored in the Tree frame.



Devices must be compliant with the Fibre Alliance MIB (Version 1.5, 2.2, or 3.0) to be managed by Softek SANView through this module.

Discovering FA MIB-compliant Devices



Understanding Device Displays in Softek SANView

The Softek SANView Client shows device health status, unique identification, and recorded events for FA MIB-compliant devices in its Tree, Topology, and SAN Events frames.


To change the poll interval, choose Change Poll Interval from the Tools menu in the Softek SANView Client.


Und

erst

andi

ng D

evic

e D

ispl

ays

in S

ofte

k SA

NV

iew

38


Health status for all managed devices and their ports is shown in the relevant device window and in the Tree and Topology frames; health status for agents is shown in the Tree frame.




FA MIB Health State Color-Coding


Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


softe

k.fu

jitsu

.com

Und

erst

andi

ng D

evic

e D

ispl

ays

in S

ofte

k SA

NV

iew



All devices’ World-wide Names and other unique device, agent, and port identification are displayed through tool tips.

Tool tips in Tree and Topology frames for a device managed through the FA MIB Module



Events logged for FA MIB-compliant devices (in addition to the standard addition/removal of agents/devices and loss/gain of agent contact) vary according to vendor.



Und

erst

andi

ng D

evic

e D

ispl

ays

in S

ofte

k SA

NV

iew

40

SAN Events frame (isolated) showing events recorded for a device managed through the FA MIB Module



��

FA MIB Event Message Severities


Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown



7

Softek SANView Fibre Alliance HBA Module & Proxy


• Installing the FC HBA Module & Proxy 43

• Running the HBA Proxy Server 45

• Discovering HBAs 46

• Understanding HBA Displays in Softek SANView 46

RATION 41

42

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Fibre Channel HBA Module (FC 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 of alternate management tools (such as Telnet or Web-based tools).

The Fibre Channel HBA Module enables 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).


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.

• Recorded events in SAN Events frame (lower frame) for addition/deletion of device agents and other health or status changes of the monitored HBAs.

Installing the FC HBA Module & Proxy


The HBA Proxy Server is a stand-alone application that manages device services. This proxy should be installed on the system that contains the HBA(s).

System requirements for the HBA Proxy Server

• Both the driver and the vendor-specific library for each HBA must be installed. These components must support SNIA’s Fibre Channel HBA API Library.

• Operating System:

- WindowsNT® Service Pack 5 or 6

- Windows2000

- SUN Solaris

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

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


Inst

allin

g th

e FC

HB

A M

odul

e &

Pro

xy

44

To install the HBA Proxy Server

To find out if you have Administrator privileges, 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.)

1. Log in to the HBA 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), insert the Softek SANView CD, select the HBA Proxy Server, and follow the displayed instructions. (Make sure you enter the correct IP address for the Softek SANView Server system.)

HBA management is now integrated into Softek SANView management. Once the HBA Proxy Server 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 communication to the HBA(s).

The Softek SANView Server is periodically polled by all HBA Proxy Servers, which re-initiate communication when the Softek SANView Server restarts.


softe

k.fu

jitsu

.com

Run

ning

the

HB

A P

roxy

Ser

ver

Running the HBA Proxy Server

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.

� NOTE: To find out if you have Administrator privileges, 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.)

The HBA Proxy Server runs differently depending on the operating system. On Windows the proxy runs as the “SANInSite 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 UNIX 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 HBA Proxy Server is running

• Windows: Choose Display Status from the Start> Programs> Softek SANView> HBA Proxy Server> menu.

• UNIX: Use the following shortcut: usr/local/bin/HBAstatus

To stop the HBA Proxy Server

• Windows: Choose Stop Proxy from the Start> Programs> Softek SANView> HBA Proxy Server> menu.

• UNIX: Use the following shortcut: usr/local/bin/HBAstop

To start the HBA Proxy Server

• Windows: Choose Start Proxy from the Start> Programs> Softek SANView> HBA Proxy Server> menu.

• UNIX: Use the following shortcut: usr/local/bin/HBAstart

To view logged events

• Windows (HBA Proxy Service): Open the Event Viewer from the Administrative Tools, then look for messages from “SANInSiteHBAProxyService.” (Administrative Tools is accessed through Start> Programs on WindowsNT and from the Control Panel on Windows2000.)

• UNIX (HBA Proxy daemon): Open the /var/adm/messages file.


Dis

cove

ring

HB

As

46

Discovering HBAs



Understanding HBA Displays in Softek SANView

The Softek SANView Client shows HBA health status, unique identification, and recorded events for devices in its Tree, Topology, and SAN Events frames.




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.


FA HBA Health State Color-Coding


Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


softe

k.fu

jitsu

.com

Und

erst

andi

ng H

BA

Dis

play

s in

Sof

tek

SAN

Vie

w



An HBA’s World-wide Name and other unique device, agent, or port identification are displayed through tool tips.

Tool tips for two HBAs on one host, in Tree frame and in Topology frame




SAN Events frame (isolated) showing events recorded for an HBA


Und

erst

andi

ng H

BA

Dis

play

s in

Sof

tek

SAN

Vie

w

48



��

FA HBA Event Message Severities


Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown



8

Softek SANView Gadzoox Module


• Discovering Gadzoox Devices 51

• Understanding Gadzoox Displays in Softek SANView 51

RATION 49

50

softe

k.fu

jitsu

.com

Feat

ures

& S

uppo

rted

Dev

ices

The Gadzoox 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 of alternate management tools (such as Telnet or Web-based tools).



The features specific to the Gadzoox Module follow.

• Health monitoring of Gadzoox® hubs, shown in Tree frame (left frame), Topology frame (right frame), and Hub window. Agent health is monitored in the Tree frame.


• Identification of device and its health status in Hub window.


The Gadzoox Module supports the Gadzoox Gibraltar-GS hub. To be managed with Softek SANView, the Gadzoox hubs must be running firmware version 4.0.

Discovering Gadzoox Devices



Understanding Gadzoox Displays in Softek SANView

The Softek SANView Client shows Gadzoox device health status, unique identification, and recorded events. This information is shown in its Tree, Topology, and SAN Events frames.




Und

erst

andi

ng G

adzo

ox D

ispl

ays

in S

ofte

k SA

NV

iew

52


Health status for all managed devices (including those for this module) and their ports is shown in the relevant device window and in the Tree and Topology frames; health status for agents (including those for this module) 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.




Gadzoox devices’ World-wide Names and other unique device, agent, and port identification are displayed through tool tips and through the Hub window. For information on the Hub window, see “Viewing the Gadzoox Hub Window” on page 54.

Gadzoox Health State Color-Coding


Green Functional

Yellow Attention

Red Failure

Light Gray Unknown

Dark Gray Unused


softe

k.fu

jitsu

.com

Und

erst

andi

ng G

adzo

ox D

ispl

ays

in S

ofte

k SA

NV

iew

Tool tips for a Gadzoox device in Tree frame and in Topology frame



Events logged for Gadzoox hubs (in addition to the standard addition/removal of agents/devices and loss/gain of agent contact) include hub health changes. Note: Since port information is not available for this module, port state changes are not logged.


SAN Events frame (isolated) showing events recorded for a Gadzoox hub


Und

erst

andi

ng G

adzo

ox D

ispl

ays

in S

ofte

k SA

NV

iew

54



Viewing the Gadzoox Hub Window

The Gadzoox Hub window identifies the hub and allows you to poll just the hub (rather than the entire SAN) for updated status.

To view the Gadzoox Hub window, right-click the desired Gadzoox icon in Softek SANView’s Topology frame and choose View Device (or double-click the icon).

Gadzoox Hub Window

Gadzoox Event Message Severities


Severity

Green Info

Blue Config

Yellow Warn

Red Fail

Black Unknown


softe

k.fu

jitsu

.com

Und

erst

andi

ng G

adzo

ox D

ispl

ays

in S

ofte

k SA

NV

iew

The Gadzoox device window displays the following information:

• Device Make and Model

• Serial Number

• World-wide Name (WWN)

• Number of ports

• Health

• Device up time

The File menu and Help menu are standard across all Softek SANView windows.

The File menu has two options: Close window dismisses the current window (the device window). Exit Softek SANView Client exits the Softek SANView Client. (The Softek SANView Server continues to run.)

The Help menu has two options: Contents displays the online help and About Softek SANView... displays system and version information.

The Tools menu for the Gadzoox Hub window has a Poll now option to immediately poll the hub’s agent for status.

��



Revision History

This revision history lists all revisions of this publication and their effective dates.

��

Revision Level Change Summary

ML-144914-001August 2001

Original release of the Softek SANView Module Reference Guide.

Module Guide - Fujitsusoftware.fujitsu.com/jp/manual/fm_e/d025c114/b1jn5541/01/... ·...

Documents

Transcript of Module Guide - Fujitsusoftware.fujitsu.com/jp/manual/fm_e/d025c114/b1jn5541/01/... ·...