User’s Guide

QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000
Series

SN0054669-00 G
User’s Guide—QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no
responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its
use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications
described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no
representation nor warranty that such applications are suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.

Document Revision History

Revision A, December 10, 2010

Revision B, March 8, 2011

Revision C, October 18, 2011

Revision D, June 1, 2012

Revision E, March 11, 2013

Revision F, March 27, 2013

Revision G, October 18, 2013

Changes Sections Affected

Added information on how to access help system “What Is in the Help System” on page viii

Updated Apache Tomcat hardware requirements “Hardware Requirements” on page 1-1

Added 4000 Series iSCSI adapters “Supported QLogic Adapters” on page 1-4

Updated Note with FabricCache agent “Installing the QConvergeConsole GUI” on

page 2-1

Documented localhost-only installation option in “Installing QConvergeConsole GUI in a Windows

Windows installation procedure for the application Environment” on page 2-5

Added localhost-only and SSL options to applica- “Installing QConvergeConsole GUI in a Linux Envi-
tion installation procedures for Linux and Solaris ronment” on page 2-6, “Installing QConvergeCon-
sole GUI in a Solaris Environment” on page 2-7

Added information on uninstalling QCC agents in “Uninstalling QConvergeConsole Agents in Win-

Windows and Linux environments dows” on page 2-10, “Uninstalling QConvergeCon-
sole Agents in Linux” on page 2-11

Added information on how to connect to QCC “Opening the QCC GUI on the Local Server” on
using SSL page 3-2, “Opening the QCC GUI on a Remote
Server” on page 3-3

Added FabricCache to Note on the “more” option “Connecting to a Host Server” on page 3-4

Added new appendix Appendix A: Security Considerations

Corrected Ethernet agent name, added FCA agents, “Windows Firewall Configuration” on page A-3
added pathnames for x64 running x86 GUI/agents

ii SN0054669-00 G
 Table of Contents

Preface
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
What Is in this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
What Is in the Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Downloading Firmware and Documentation . . . . . . . . . . . . . . . . . . . . xi
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
1 System Requirements
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Supported QLogic Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
2 Installing the QConvergeConsole GUI
Downloading the QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Downloading and Installing Management Agents . . . . . . . . . . . . . . . . . . . . 2-2
Installing the Agents from the QLogic Web Site . . . . . . . . . . . . . . . . . 2-2
Installation with Package Files (Solaris 10 and 11) . . . . . . . . . . 2-3
Installation with p5p Files (Solaris 11 or later) . . . . . . . . . . . . . . 2-3
Installing the Agents Using the Built-in Agent Installer . . . . . . . . . . . . 2-4
Installing QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing QConvergeConsole GUI in a Windows Environment. . . . . . 2-5
Installing QConvergeConsole GUI in a Linux Environment. . . . . . . . . 2-6
Installing QConvergeConsole GUI in Silent Mode. . . . . . . . . . . . . . . . 2-7
Installing QConvergeConsole GUI in a Solaris Environment . . . . . . . 2-7
Uninstalling the QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Uninstalling QConvergeConsole GUI in a Windows Environment . . . 2-9
Uninstalling QConvergeConsole Agents in Windows . . . . . . . . . 2-10

SN0054669-00 G iii
User’s Guide—QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

Uninstalling QConvergeConsole GUI in a Linux Environment . . . . . . 2-10

Uninstalling QConvergeConsole Agents in Linux . . . . . . . . . . . . 2-11
Uninstalling QConvergeConsole GUI in a Solaris Environment . . . . . 2-11
Uninstalling QConvergeConsole Agents on Solaris . . . . . . . . . . 2-11
3 Getting Started
Starting QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Opening the QConvergeConsole GUI Main Page. . . . . . . . . . . . . . . . 3-2
Opening the QCC GUI on the Local Server . . . . . . . . . . . . . . . . 3-2
Opening the QCC GUI on a Remote Server . . . . . . . . . . . . . . . 3-3
Connecting to a Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Exiting QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Browsing Help Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Viewing QConvergeConsole GUI Version Details . . . . . . . . . . . . . . . . 3-6
A Security Considerations
Management Connectivity Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Managing Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Connectivity Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Password Protection for Access Control . . . . . . . . . . . . . . . . . . . . . . . A-2
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Windows Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Web Server (Apache Tomcat) Security . . . . . . . . . . . . . . . . . . . . . . . . A-5
Secure Sockets Layer (SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
B Troubleshooting
How to Change the Tomcat Port Number. . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
How to Change the Default Port Reference Using the 
QConvergeConsole Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
How to Set Up a Tomcat Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Procedure on Windows-based Systems . . . . . . . . . . . . . . . . . . . . . . . B-5
Procedure on Linux-based Systems . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Procedure on Solaris-based Systems . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Glossary
Index

iv SN0054669-00 G
 User’s Guide—QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

List of Figures
Figure Page
3-1 QConvergeConsole GUI Main Page (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-2 Specifying the QConvergeConsole GUI Web Address (Example). . . . . . . . . . . . . . 3-4
3-3 Hostname or IP Address Input (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3-4 About QConvergeConsole GUI (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
A-1 QCC GUI Management Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A-2 Default Windows Firewall Settings—QCC Blocked from Remote Hosts . . . . . . . . . A-4
A-3 Modified Firewall Settings—QCC Able to Connect to Remote Hosts . . . . . . . . . . . A-5
B-1 QCC GUI Shortcut Properties with Default Port Number. . . . . . . . . . . . . . . . . . . . . B-3
B-2 QCC GUI Shortcut Properties with New Port Number . . . . . . . . . . . . . . . . . . . . . . . B-4
B-3 Tomcat Program Files Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B-4 Configure Tomcat Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B-5 Stopping Server Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B-6 Logging Tab on Configure Tomcat Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B-7 Changing Locations of Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
B-8 Locations of Output Files Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
B-9 General Tab of Configure Tomcat Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

SN0054669-00 G v
User’s Guide—QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

vi SN0054669-00 G
Preface
The QConvergeConsole GUI User’s Guide describes the QConvergeConsole®
GUI, a Web-based management tool for configuring and managing QLogic Fibre
Channel adapters, Intelligent Ethernet adapters, and Converged Network
Adapters within storage area networks (SANs).

NOTE
Throughout this guide, the QConvergeConsole GUI management tool is
also referred to as QConvergeConsole GUI or QCC GUI, and the terms
target and device are used interchangeably.

Intended Audience
This guide is for system administrators who are responsible for installing,
configuring, and managing QLogic adapters using QConvergeConsole GUI.

Related Materials
For additional information, refer to the following documents that are available on the
Downloads and Documentation page of the QLogic Web site:
http://driverdownloads.qlogic.com:
 QConvergeConsole Readme and Release Notes documents contain
information about installation, OS support, and known issues.
 User’s Guide, QConverge Console CLI (part number SN0054667-00)
contains information detailed information on how to install and use the
QConvergeConsole command line interface (CLI) management tool.
 User’s Guide, QConvergeConsole Plug-Ins for VMware vSphere (part
number SN0054677-00) provides information on using the QLogic plug-ins
that provide QConvergeConsole functionality in VMware vSphere.

What Is in this Guide

This user’s guide contains the basic information you need to get started with the
QConvergeConsole GUI.

SN0054669-00 G vii
Preface
What Is in the Help System

This preface describes the organization of the QConvergeConsole GUI help

system, specifies the intended audience, lists related documents, explains
typographic conventions used in this guide, refers you to the QLogic license
agreements, and provides technical support and contact information.
The remainder of the user's guide is organized into the following chapters:
 Chapter 1 System Requirements lists the hardware, software, and operating
system requirements that must be met to ensure successful operation of the
QConvergeConsole GUI.
 Chapter 2 Installing the QConvergeConsole GUI describes how to install
and uninstall QConvergeConsole GUI.
 Chapter 3 Getting Started describes how to customize QConvergeConsole
GUI. It includes starting and exiting the QConvergeConsole GUI user
interface, and getting help.
 Appendix A Security Considerations provides information on security-related
topics for QConvergeConsole GUI.

 Appendix B Troubleshooting describes procedures that may be helpful for

troubleshooting.

Included also are a glossary of terms used and an index to help you quickly find
information.

What Is in the Help System

NOTE
To access help, see “Getting Help” on page 3-5.

The QConvergeConsole GUI help system contains detailed information on

features and functionality not covered in this guide, including instructions on
configuring and managing adapters using the QConvergeConsole GUI.
For instructions on accessing the help system, refer to “Getting Help” on page 3-5.
The help system’s table of contents includes the following top-level topics:
 QConvergeConsole Overview briefly summarizes the purpose of the
QConvergeConsole GUI management tool and the adapters that it supports.
 Getting Started shows how to start using QConvergeConsole GUI and the
help system. It also describes how to initiate automatic e-mail notifications
and set security on adapters installed for a selected host.
 Managing Host Connections describes how to connect to a host, create
and use a host group, view host information, and disconnect from one or
more host servers.

viii SN0054669-00 G
 Preface
What Is in the Help System

 Displaying Host Information describes how to view general host

information.
 Displaying Adapter Information describes how to view general adapter
information.
 Displaying Device Information shows how to view information about a
device (disk or tape).
 Using Reports describes the different types of reports and how to generate,
view, and save them using QConvergeConsole GUI's report facility.
 Managing Fibre Channel and FCoE Adapters describes how to do the
following for a Fibre Channel Adapter (2400/2500/2600 Series) or
Converged Network Adapter (8100/8200/8300 Series):
 Display and edit adapter-specific information for the selected adapter.
 View and modify adapter configuration and settings.
 Update the adapter’s flash memory or FC/FCoE driver
 Managing Fibre Channel and FCoE Ports describes how to do the
following for a port on a Fibre Channel Adapter or a Converged Network
Adapter:
 View and modify the parameters and statistics for the selected port.
 Use the advanced utilities, manage virtual ports, and run diagnostics.
 Managing iSCSI Ports shows and describes the parameters on the iSCSI
port management pages for the 4000 Series iSCSI adapters and the
8200/8300 Series Converged Network Adapters.
 Managing Ethernet (NIC) Ports shows and describes the parameters and
configuration options provided on the NIC port management pages for 3200
Series Intelligent Ethernet Adapters, as well as 8100/8200/8300 Series
Converged Network Adapters.
 Managing FabricCache Adapters and Ports shows and describes how to
display and edit information for 10000 Series FabricCache Adapters (FCA)
and ports, as well as how to configure port parameters.
 Managing FabricCache Adapter Storage shows and describes how to use
the system tree on the Storage tab, how to display clusters, how to use the
logical and physical views, how to display information for FCA cluster
adapters, ports, SSDs, and LUNs, and how to configure LUN caching.
 Using the Wizards describes how to use the QCC GUI wizards to update
the flash, drivers, NIC parameters, FC/FCoE parameters, parameter files,
passwords, and agents, and to configure FCA clusters.

SN0054669-00 G ix
Preface
Documentation Conventions

 Troubleshooting describes tools you can use to resolve the problems that
can occur when installing and using QConvergeConsole GUI. It also
provides the procedures for tracing QConvergeConsole GUI application and
agent activity, if directed to do so by your authorized service provider.
 Frequently Asked Questions provides the answers to frequently asked
questions about QConvergeConsole GUI.
 Technical Support explains how to obtain technical support, gives
instructions for downloading software and documentation, and provides
contact information.

Documentation Conventions
This guide uses the following documentation conventions:

 NOTE provides additional information.

 Text in blue font indicates a hyperlink (jump) to a figure, table, or section in
this guide, and links to Web sites are shown in underlined blue. For
example:
 Table 9-2 lists problems related to the user interface and remote agent.
 See “Installation Checklist” on page 3-6.
 For more information, visit www.qlogic.com.
 Text in bold font indicates user interface elements such as a menu items,
buttons, check boxes, or column headings. For example:
 Click the Start button, point to Programs, point to Accessories, and
then click Command Prompt.
 Under Notification Options, select the Warning Alarms check box.
 Text in Courier font indicates a file name, directory path, or command line
text. For example:
 To return to the root directory from anywhere in the file structure:
Type cd /root and press ENTER.
 Enter the following command: sh ./install.bin

 Key names and key strokes are indicated with UPPERCASE:

 Press CTRL+P.
 Press the UP ARROW key.

x SN0054669-00 G
 Preface
License Agreements

 Text in italics indicates terms, emphasis, variables, or document titles. For

example:
 For a complete listing of license agreements, refer to the QLogic
Software End User License Agreement.
 What are shortcut keys?
 To enter the date type mm/dd/yyyy (where mm is the month, dd is the
day, and yyyy is the year).

 Topic titles between quotation marks identify related topics either within this
manual or in the online help, which is also referred to as the help system
throughout this document.

License Agreements
Refer to the QLogic Software End User License Agreement for a complete list of
all license agreements affecting this product.

Technical Support
Customers should contact their authorized maintenance provider for technical
support of their QLogic products. QLogic-direct customers may contact QLogic
Technical Support; others will be redirected to their authorized maintenance
provider.
Visit the QLogic support Web site listed in Contact Information for the latest
firmware and software updates.
For details about available service plans, or for information about renewing and
extending your service, visit the Service Program Web page at
http://www.qlogic.com/services.

Downloading Firmware and Documentation

To download firmware and documentation:
1. Go to the QLogic Downloads and Documentation page:
http://driverdownloads.qlogic.com.
2. Under QLogic Products, type the QLogic model name in the search box.
3. In the search results list, locate and select the firmware and documentation
for your product.
4. View the product details Web page to ensure that you have the correct
firmware, software, or documentation. For additional information, click the
Read Me and Release Notes icons under Support Files.
5. Click Download Now.

SN0054669-00 G xi
Preface
Training

6. Save the file to your computer.

7. If you have downloaded firmware, software, drivers, or boot code, follow the
installation instructions in the Readme file.
Instead of typing a model name in the search box, you can perform a guided
search as follows:
1. Click the product type tab: Adapters, Switches, Routers, or ASICs.
2. Click the corresponding button to search by model or operating system.
3. Click an item in each selection column to define the search, and then click Go.
4. Locate the firmware, software, or document you need, and then click the
icon to download or open the item.

Training
QLogic Global Training maintains a Web site at www.qlogictraining.com offering
online and instructor-led training for all QLogic products. In addition, sales and
technical professionals may obtain Associate and Specialist-level certifications to
qualify for additional benefits from QLogic.

Contact Information
QLogic Technical Support for products under warranty is available during local
standard working hours excluding QLogic Observed Holidays. For customers with
extended service, consult your plan for available hours. For Support phone
numbers, see the Contact Support link at http://support.qlogic.com.
Support Headquarters QLogic Corporation
4601 Dean Lakes Blvd.
Shakopee, MN 55379 USA
QLogic Web Site www.qlogic.com
Technical Support Web Site http://support.qlogic.com
Technical Support E-mail [email protected]
Technical Training E-mail [email protected]

Knowledge Database
The QLogic knowledge database is an extensive collection of QLogic product
information that you can search for specific solutions. We are constantly adding to
the collection of information in our database to provide answers to your most
urgent questions. Access the database from the QLogic Support Center:
http://support.qlogic.com.

xii SN0054669-00 G
1 System Requirements

QConvergeConsole GUI is a Web-based client and server GUI management tool

that provides centralized management and configuration of QLogic adapters
within the entire network (LAN and SAN).
On the server side, the QConvergeConsole GUI runs as an Apache Tomcat™
application server. After the QConvergeConsole GUI is launched on the
application server, you can connect to the QCC GUI through a browser, either
locally on the server or remotely from another computer. Your browser window
becomes the client used to connect to servers that host the QLogic adapters and
connected storage devices within the network.
For optimum performance, QConvergeConsole GUI requires the hardware,
software, and operating systems listed in this chapter:
 “Hardware Requirements” on page 1-1
 “Software Requirements” on page 1-2
 “Operating System Requirements” on page 1-3
 “Supported QLogic Adapters” on page 1-4

Hardware Requirements
The minimum hardware requirements are as follows:
Apache Tomcat application server:
 Server—Single processor or multiprocessor equivalent to an Intel® Core™
Duo running at 1GHz or greater. See “Operating System Requirements” on
page 1-3 for operating systems on which the Web browser can run.
 Memory—1GB of physical RAM to run QConvergeConsole GUI; 2GB
recommended. Running with less memory can cause disk swapping, which
severely affects performance.
 Video card—Capable of 16K colors and a resolution of 1280 × 960 pixels
 Hard disk space—512MB disk space

Server agent:
 Adapters—One or more of the QLogic adapters listed under “Supported
QLogic Adapters” on page 1-4

SN0054669-00 G 1-1
1–System Requirements
Software Requirements

SAN:
 Storage—Fibre Channel or iSCSI devices, such as disks and RAID subsystems

NOTE
QConvergeConsole GUI supports most Fibre Channel and iSCSI devices.
See the QLogic Storage Networking Interoperability Guide, which you can
download from: http://connect.qlogic.com/interopguide/info.asp

Software Requirements
The minimum software requirements are as follows:
Server where adapter is installed—must have the following:
 QLogic adapter drivers for your operating system
 QLogic adapter management agents for your operating system

NOTE
To download QLogic adapter drivers, go to: http://driverdownloads.qlogic.com

 TCP/IP protocol for Windows® remote management

 Administrative privileges to perform management functions
 User access control disabled on Windows Server® 2008 and
Windows Server 2012 to run the agent service
 Port 8443 for SSL connection (if the SSL option is selected upon installation)

Apache Tomcat application server—must have the following:

 Apache Tomcat (installed automatically by QConvergeConsole GUI if not
already present)
 QConvergeConsole GUI (before installing, refer to the Note on page 2-1)
Web browser—must be one of the following:
 Google Chrome™
 Mozilla® Firefox®
 Microsoft® Internet Explorer®
 Opera®
 Apple® Safari®

NOTE
 For details on browser versions, see the QConvergeConsole Readme,
which you can download from: http://driverdownloads.qlogic.com
 Some auxiliary help features, such as the Search and Index tools, may
not work properly in every Web browser.

1-2 SN0054669-00 G
 1–System Requirements
Operating System Requirements

Operating System Requirements

The client, Apache Tomcat application server, and server agent each have their
own operating system requirements, as follows:
 Client—requires one of the following operating systems to host a supported
Web browser (see “Software Requirements” on page 1-2):
 Windows Server 2008, Windows Server 2012
 Red Hat® Linux® Advance Server and Enterprise Server
 Novell® SUSE® Linux Enterprise Server (SLES®)
 Solaris®

NOTE
To run QCC GUI on Solaris 10/11, you must disable the firewall by issuing
the following command after each boot-up and before running QCC:
netservices open

 Apache Tomcat application server—requires one of the following

operating systems to host the Tomcat server for QConvergeConsole GUI:
 Microsoft® Windows Server® 2008 or Windows Server 2012
 Red Hat Linux Advance Server and Enterprise Server
 Novell SUSE Linux Enterprise Server (SLES)
 Citrix® XenServer®

 Server agent—Multiple operating system support allows control of

heterogeneous environments. The QConvergeConsole GUI server agent
works with the following operating systems:
 Microsoft Windows Server 2008, Windows Server 2012
 Red Hat Linux Advance Server and Enterprise Server
 Novell SUSE Linux Enterprise Server (SLES)
 Solaris 10, Solaris 11

NOTE
For details on operating system versions, see the QConvergeConsole
Readme, which you can download from: http://driverdownloads.qlogic.com.

SN0054669-00 G 1-3
1–System Requirements
Supported QLogic Adapters

Supported QLogic Adapters

QConvergeConsole GUI supports the following QLogic-branded adapters. For
support of OEM-branded adapters, contact your OEM.
 2400, 2500, and 2600 Series Fibre Channel Adapters
 3200 Series Intelligent Ethernet Adapters
 4000 Series iSCSI Adapters
 8100, 8200, and 8300 Series Converged Network Adapters
 10000 Series FabricCache Adapters

NOTE
For information about QLogic adapters, refer to the QLogic Web site at
http://www.qlogic.com/Products/adapters.

1-4 SN0054669-00 G
2 Installing the
QConvergeConsole GUI
Installing the QConvergeConsole GUI consists of installing the
QConvergeConsole GUI user interface, a platform-specific management agent,
and help components, as appropriate.
 “Downloading the QConvergeConsole GUI” on page 2-2
 “Downloading and Installing Management Agents” on page 2-2
 “Installing QConvergeConsole GUI” on page 2-5
 “Uninstalling the QConvergeConsole GUI” on page 2-9

NOTE
Before installing QConvergeConsole GUI:
 Read the documents listed in “Related Materials” on page vii, as
applicable, for important, up-to-date product information.
 If using Windows firewalls, refer to “Windows Firewall Configuration” on
page A-3 for information on Windows firewall configuration.
 If upgrading QConvergeConsole GUI from an older version, be sure to
clear the browser cache before installing the new version. See your
browser’s documentation or help for instructions. Additional information
can be found here: http://kb.iu.edu/data/ahic.html.
 If using the default Tomcat port number (8080) will cause a conflict, refer
to “Password Protection for Access Control” on page A-2. (You can also
manually specify the Tomcat port number.)
 For information on creating a Tomcat log file for troubleshooting, refer to
“How to Set Up a Tomcat Log File” on page B-5.
 To enable access to the adapters on a host server, the management
agents—qlremote (Fibre Channel/FCoE), netqlremote (Ethernet [NIC]),
iqlremote (iSCSI), and qlremote_fca (FabricCache)—must already be
installed on the host. For detailed information on obtaining and installing the
management agents, refer to in “Downloading and Installing Management
Agents” on page 2-2.

SN0054669-00 G 2-1
2–Installing the QConvergeConsole GUI
Downloading the QConvergeConsole GUI

Downloading the QConvergeConsole GUI

To download the QCC GUI, use the procedure in “Downloading Firmware and
Documentation” on page xi, where QConvergeConsole GUI is the item being
downloaded.

Downloading and Installing Management Agents

To manage adapter(s) on a local or remote host, the management agents (also
called agents) used by the adapter(s) must already be installed on that host.
(To simply connect to a remote host, at least one management agent used by the
host’s adapters must be installed on that host.)
The management agents are:
 netqlremote for Ethernet Networking (NIC)
 qlremote for Fibre Channel and FCoE
 iqlremote for iSCSI
 qlremote_fca for FabricCache Adapter

The management agents are not automatically installed by the QCC GUI package
and must be downloaded and installed separately. You can download the agents
from the QLogic Web site Downloads page, or using the built-in Agent Installer.

Installing the Agents from the QLogic Web Site

To download the netqlremote, qlremote, and iqlremote agents from the QLogic
Web site and install them (for qlremote_fca, see “Installing the Agents Using the
Built-in Agent Installer” on page 2-4 for download and installation instructions):
Windows and Linux (all versions):
1. Go to the QLogic Downloads page at http://driverdownloads.qlogic.com and
download the SuperInstaller, Readme, and Release Notes for each adapter
on the host server.
2. Install the agents by running the SuperInstaller. Refer to the Readme and
Release Notes for detailed information on running the SuperInstaller.
Solaris:
1. Go to the QLogic Downloads page at http://driverdownloads.qlogic.com and
download the following for each adapter on the host server:
 Solaris 10 or 11: Installer package files
 Solaris 11 only: p5p files
2. Install the agent(s) by referring to the applicable section:
 “Installation with Package Files (Solaris 10 and 11)” on page 2-3
 “Installation with p5p Files (Solaris 11 or later)” on page 2-3

2-2 SN0054669-00 G
 2–Installing the QConvergeConsole GUI
Installing the Agents from the QLogic Web Site

Installation with Package Files (Solaris 10 and 11)

NOTE
In each Solaris command in this section:
 <agent> is the name of one of the following management agents (issue
each command once per agent being installed):
 qlremote for Fibre Channel or FCoE
 iqlremote for iSCSI
 netqlremote for NIC
 <version> is the version number found in the package file name.
 <platform> is either i386 or SPARC.

To install the QCC GUI on Solaris using package files, follow these steps:
1. Each agent installer package is provided in compressed format and must be
uncompressed to obtain the installable package. To uncompress the
package, issue the following Solaris command:
uncompress <agent>-<version>-solaris-<platform>.pkg.Z

2. The uncompress command creates a package file named as follows:

<agent>-<version>-solaris-<platform>.pkg
3. To install QConvergeConsole Solaris agents in .pkg format, issue the
following Solaris command:
pkgadd -d <agent>-<version>-solaris-<platform>.pkg 

Installation with p5p Files (Solaris 11 or later)

NOTE
In each Solaris command in this section:
 <agent> is the name of one of the following management agents (issue
each command once per agent being installed):
 qlremote for Fibre Channel or FCoE
 iqlremote for iSCSI
 netqlremote for NIC
 <version> is the version number found in the package file name.
 <platform> is either i386 or SPARC.

SN0054669-00 G 2-3
2–Installing the QConvergeConsole GUI
Installing the Agents Using the Built-in Agent Installer

To install the QCC GUI on Solaris 11 using p5p files, follow these steps:
1. Set the environment by issuing the following command:
export PKGREPO=/pkgrepo

2. Create the repo by issuing the following command:

pkgrepo create $PKGREPO

3. Receive the package in your repo by issuing the following command:

pkgrecv -s /<agent>-<version>-solaris-<platform>.p5p -d
$PKGREPO <agent>

4. Set the publisher by issuing the following command:

pfexec pkg set-publisher -p $PKGREPO

5. Proceed with the installation by issuing the following commands:

pkg install <agent>

NOTE
S

 Be sure to use same installer type for all the agents that you install. For
example, if you use the .pkg installer type for qlremote, you must also
use the .pkg installer type for netqlremote and iqlremote. Mixing
installer types, such as using the .pkg type for qlremote and the .p5p
type for netqlremote, results in an error.
 If an agent is already installed, it must be uninstalled before a new
version can be installed.

Installing the Agents Using the Built-in Agent Installer

To access the Agent Installer within the QConvergeConsole GUI:
1. Click Help in the QCC GUI menu bar, and then select Download Agent
Installers.
2. Follow the on-screen prompts. For detailed installation instructions, refer to
the QConvergeConsole GUI online help (select Help from the menu bar,
and then select Browse Contents; search for agent installer).

2-4 SN0054669-00 G
 2–Installing the QConvergeConsole GUI
Installing QConvergeConsole GUI

Installing QConvergeConsole GUI

Refer to the installation procedure for your operating system:
 “Installing QConvergeConsole GUI in a Windows Environment” on page 2-5
 “Installing QConvergeConsole GUI in a Linux Environment” on page 2-6
 “Installing QConvergeConsole GUI in Silent Mode” on page 2-7
 “Installing QConvergeConsole GUI in a Solaris Environment” on page 2-7

NOTE
Before installing QCC GUI, be sure to read the Note on page 2-1.

Installing QConvergeConsole GUI in a Windows Environment

The QConvergeConsole Installer for Windows is a self-extracting utility that
installs the QConvergeConsole GUI and related files. Follow these steps to install
QConvergeConsole GUI on a Windows system.

NOTE
For information on firewall configuration on Windows systems, refer to
“Windows Firewall Configuration” on page A-3.

To install QConvergeConsole GUI in a Windows environment:

1. In the directory where you downloaded the installation file, double-click the
QConvergeConsole_Installer_Windows_<version>.exe file.
2. If an Open File security dialog box appears, click Run.
The InstallAnywhere® utility prepares to install QConvergeConsole GUI.
3. In the Tomcat Port Number Setup dialog box, type a valid port number in the
range 1025–65536, or keep the default port number, 8080. Then, click Next.
4. In the next dialog box, select Yes if you want a localhost-only installation. If
you do not want a localhost-only installation, select No.

NOTE
The localhost-only option installs QCC locally so that you must run it locally
(remote connection is not possible). To disable the option, you must uninstall
QCC GUI and then re-install it, selecting No in this step.

5. On the Pre-Installation Summary dialog box, verify that the information is

correct, and then click Install to proceed.
The installer displays the progress of the installation.

SN0054669-00 G 2-5
2–Installing the QConvergeConsole GUI
Installing QConvergeConsole GUI in a Linux Environment

6. A message box prompts you to confirm if you want to enable the Secure
Socket Layer (SSL) feature, which allows data to be encrypted within a
secure layer before passing it to and from the server.
To enable the SSL feature, click Yes. To disable SSL, click No.
7. On the Install Complete dialog box, click Done to exit the installer.
You have installed QConvergeConsole GUI on your server.
8. Start QConvergeConsole GUI (see “Starting QConvergeConsole GUI” on
page 3-2 for detailed information).

Installing QConvergeConsole GUI in a Linux Environment

NOTE
Before installing QCC GUI, be sure to read the Note on page 2-1.

You have the option of installing QConvergeConsole GUI in a Linux environment

using either a GUI or command line method. To install from the command line, see
“Installing QConvergeConsole GUI in Silent Mode” on page 2-7.
You can graphically install QConvergeConsole GUI on a Linux host by running a
Virtual Network Computing (VNC®) program on a Windows host. The TightVNC
Viewer, a VNC program, can remotely control QConvergeConsole GUI installation
on a Linux host.

To install QConvergeConsole GUI in a Linux environment:

1. Open the directory containing the installer file, which is one of the following:
QConvergeConsole_Installer_Linux_i386_<version>.bin
QConvergeConsole_Installer_Linux_IA64_<version>.bin
QConvergeConsole_Installer_Linux_x64_<version>.bin
QConvergeConsole_Installer_Linux_ppc64_<version>.bin
2. In the terminal window, verify that the installer file has permission to execute
by issuing the ls -lt command at the prompt.
3. To install QConvergeConsole GUI, double-click the QConvergeConsole GUI
installer .bin file.
A prompt asks if you want to run or view the contents of the .bin file.
4. Click Run in Terminal.
The installer extracts the files and installs QConvergeConsole GUI in the
directory /opt/QLogic_Corporation/QConvergeConsole.
The InstallAnywhere window prepares to install QConvergeConsole GUI.
5. On the installation Introduction dialog box, click Next.

2-6 SN0054669-00 G
 2–Installing the QConvergeConsole GUI
Installing QConvergeConsole GUI in Silent Mode

6. On the Tomcat Port Number Setup dialog box, enter a valid port number in
the range 1025–65536, or accept the default port number, 8080. Then click
Next to continue.
7. In the next dialog box, select Yes if you want a localhost-only installation. If
you do not want a localhost-only installation, select No.

NOTE
The localhost-only option installs QCC locally so that you must run it locally
(remote connection is not possible). To disable the option, you must uninstall
QCC GUI and then re-install it, selecting No in this step.

8. On the Pre-Installation Summary dialog box, read the information, and then
click Install.
During the installation, the installer notifies you of the status.
9. A message box prompts you to confirm if you want to enable the Secure
Socket Layer (SSL) feature, which allows data to be encrypted within a
secure layer before passing it to and from the server.
To enable the SSL feature, click Yes. To disable SSL, click No.
10. On the Install Complete dialog box, click Done to exit the installer.
You have installed QConvergeConsole GUI on your server.
11. Start QConvergeConsole GUI (see “Starting QConvergeConsole GUI” on
page 3-2 for detailed information).

Installing QConvergeConsole GUI in Silent Mode

You can install QConvergeConsole GUI from a command prompt in silent mode.

NOTE
Before installing QCC GUI, be sure to read the Note on page 2-1.

To run the installer in silent mode, issue the following command:

<installer_file_name> -i silent -DUSER_INPUT_PORT_NUMBER=<A_NUMBER>

Installing QConvergeConsole GUI in a Solaris Environment

You can graphically install QConvergeConsole GUI on a Solaris host by running a
Virtual Network Computing (VNC) program on a remote host. The TightVNC
Viewer, a VNC program, can remotely control QConvergeConsole GUI installation
on a Solaris host.

SN0054669-00 G 2-7
2–Installing the QConvergeConsole GUI
Installing QConvergeConsole GUI in a Solaris Environment

To install QConvergeConsole GUI in a Solaris environment:

1. Open the directory containing the installer file: 
QConvergeConsole_Installer_Solaris_<platform>_<version>.bin
2. From the terminal window, verify that the installer file has permission to
execute by issuing the ls -lt command at the prompt.
3. To install QConvergeConsole GUI, type the following command on the console: 
sh QConvergeConsole_Installer_Solaris_<platform>_<version>.bin
The InstallAnywhere GUI utility prepares to install QConvergeConsole GUI
and opens the installation Introduction dialog box.
4. Click Next.
5. On the Tomcat Port Number Setup dialog box, enter a valid port number in
the range 1025–65536, or accept the default port number, 8080. Then click
Next to continue.
6. In the next dialog box, select Yes if you want a localhost-only installation. If
you do not want a localhost-only installation, select No.

NOTE
The localhost-only option installs QCC locally so that you must run it locally
(remote connection is not possible). To disable the option, you must uninstall
QCC GUI and then re-install it, selecting No in this step.

7. The Pre-Installation Summary dialog box opens. Read the information, and
then click Install.
During the installation, the installer notifies you of the status.
8. A message box prompts you to confirm if you want to enable the Secure
Socket Layer (SSL) feature, which allows data to be encrypted within a
secure layer before passing it to and from the server.
To enable the SSL feature, click Yes. To disable SSL, click No.
9. On the Install Complete dialog box, click Done to exit the installer.
You have installed QConvergeConsole GUI on your server, and the
management agents for NIC, FCoE, and iSCSI (see the note at the end of this
section) to manage the server in which your adapter is physically installed.
10. Start QConvergeConsole GUI (see “Starting QConvergeConsole GUI” on
page 3-2 for detailed information).

2-8 SN0054669-00 G
 2–Installing the QConvergeConsole GUI
Uninstalling the QConvergeConsole GUI

NOTE
S

 Certain adapters may not support all three protocol agents; check your
adapter’s specifications to confirm.
 QConvergeConsole GUI records all installation activities in the log file,
QConvergeConsole_InstallLog.log, located in the installation
directory /opt/QLogic Corporation/QConvergeConsole. If the
installation fails, review this log file to find a possible source of failure.

Uninstalling the QConvergeConsole GUI

Refer to the uninstallation procedure for your operating system:
 “Uninstalling QConvergeConsole GUI in a Windows Environment” on
page 2-9
 “Uninstalling QConvergeConsole GUI in a Linux Environment” on page 2-10
 “Uninstalling QConvergeConsole GUI in a Solaris Environment” on
page 2-11

Uninstalling QConvergeConsole GUI in a Windows Environment

Follow these steps to uninstall QConvergeConsole GUI from a Windows system.
To uninstall QConvergeConsole GUI in a Windows environment:
1. Start the uninstaller using one of these methods:
 Using Windows Explorer:
a. Change to the directory that contains the QConvergeConsole
files. The default location is:
C:\Program Files\QLogic Corporation\QConvergeConsole

b. Open the Uninstall_QConvergeConsole folder, and then

double-click the QConvergeConsoleUninstaller.exe file.
 Using Add or Remove Programs:
a. From the Windows Control Panel, double-click Add or Remove
Programs.
b. From the list of currently installed programs, select
QConvergeConsole, and then click Change/Remove.
2. On the Uninstall QConvergeConsole GUI dialog box, click Next to continue.
3. On the Uninstall Options dialog box, click Complete Uninstall. Then, click Next.
During uninstallation, the uninstaller reports the status and displays a
request to wait while the uninstaller removes the components.

SN0054669-00 G 2-9
2–Installing the QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Linux Environment

4. When the Uninstall Complete dialog box informs you that the uninstallation
is complete, click Done.
QConvergeConsole GUI has been uninstalled.
Uninstalling QConvergeConsole Agents in Windows
To uninstall the QConvergeConsole agents in Windows, follow these steps:
1. Navigate to Uninstall a Program.
2. Locate the agent to uninstall:

 SANsurfer iSCSI HBA Management Agent—for the iSCSI agent

 SANsurfer FC HBA Management Agent—for the Fibre Channel and
FCoE agent
 QLogic NIC HBA Management Agent—for the NIC agent
 QLremoteFca and HCLI - for the FabricCache agent
3. Select Uninstall to remove the agent.
4. If required, repeat steps 1 to 3 for each additional agent to be uninstalled.

Uninstalling QConvergeConsole GUI in a Linux Environment

Follow these steps to uninstall QConvergeConsole GUI from a Linux system.

To uninstall QConvergeConsole GUI in a Linux environment:

1. Change to the directory where QConvergeConsole GUI is installed. The
default location is:
/opt/QLogic_Corporation/QConvergeConsole/Uninstall_QConvergeConsole/

2. In the Uninstall_QConvergeConsole directory, double-click the

QConvergeConsoleUninstaller file to start the uninstallation.
3. When the message box asks whether you want to run or view the contents
of the QConvergeConsoleUnnstaller.bin file, click Run in Terminal.
4. On the Uninstall QConvergeConsole dialog box, click Next to continue.
5. On the Uninstall Options dialog box, click Complete Uninstall. Then, click
Next.
During uninstallation, the uninstaller indicates its progress, and a message
box asks you to wait the while the uninstaller removes the components.
6. When the Uninstall Complete dialog box informs you that the uninstallation
is complete, click Done.
QConvergeConsole GUI has been uninstalled.

2-10 SN0054669-00 G
 2–Installing the QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Solaris Environment

Uninstalling QConvergeConsole Agents in Linux

To uninstall the QConvergeConsole NIC, Fibre Channel, FCoE, or iSCSI agents in
Linux, issue the following command:
rpm -e <agent>

where:
 <agent> is one of the following:
 netqlremote for Ethernet NIC
 qlremote for Fibre Channel or FCoE
 iqlremote for iSCSI
 qlremote_fca for FabricCache

Uninstalling QConvergeConsole GUI in a Solaris Environment

Follow these steps to uninstall QConvergeConsole GUI from a Solaris system. Be
sure to exit QConvergeConsole GUI before you uninstall.

To uninstall QConvergeConsole GUI in a Solaris environment:

1. From the console, change to the directory where the QCC uninstaller file,
QConvergeConsoleUninstaller, is installed. The default location is:
/opt/QLogic_Corporation/QConvergeConsole/Uninstall_QConvergeConsole

2. To start the uninstallation process, type the following at the console prompt:
./QConvergeConsoleUninstaller

Uninstall messages appear on the console during the uninstallation process.

Uninstalling QConvergeConsole Agents on Solaris
To uninstall the QConvergeConsole agents on Solaris, follow the instructions that
correspond to the method used to install the agents.
To uninstall agents installed using package files (Solaris 10 or 11):
To uninstall QConvergeConsole Solaris agents that were installed using .pkg
format files, issue the following command:
pkgrm <agent>

where:
 <agent> is one of the following:
 QLRemote for Fibre Channel or FCoE
 iqlremote for iSCSI
 NetQLRemote for Ethernet NIC on x86
 NQLRemote for Ethernet NIC on SPARC

SN0054669-00 G 2-11
2–Installing the QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Solaris Environment

To uninstall agents installed using p5p files (Solaris 11 only):

To uninstall QConvergeConsole Solaris agents that were installed using .p5p
format files, issue the following command:
pkg uninstall <agent>

where:
 <agent> is one of the following:
 qlremote for Fibre Channel or FCoE
 iqlremote for iSCSI
 netqlremote for Ethernet NIC

2-12 SN0054669-00 G
3 Getting Started

This chapter includes procedures for starting and exiting the QConvergeConsole
GUI user interface, and getting help:
 “Starting QConvergeConsole GUI” on page 3-2
 “Exiting QConvergeConsole GUI” on page 3-5
 “Getting Help” on page 3-5

SN0054669-00 G 3-1
3–Getting Started
Starting QConvergeConsole GUI

Starting QConvergeConsole GUI

Start QConvergeConsole GUI by opening its main page in your browser window.
You can do this either locally on the server where QConvergeConsole GUI is
installed or remotely from another computer. From the main page, you can
connect to servers that host QLogic adapters and devices you want to manage.
The procedures are the same in Windows, Linux, and Solaris environments.
This section provides information about:
 “Opening the QConvergeConsole GUI Main Page” on page 3-2
 “Connecting to a Host Server” on page 3-4

Opening the QConvergeConsole GUI Main Page

You can open QConvergeConsole GUI locally on the server or from a remote
computer. You can also open QCC GUI using a non-secure or a secure (SSL)
connection.

NOTE
SSL is enabled during installation. To use SSL when it has not been
enabled, first uninstall QConvergeConsole GUI, and then re-install it,
selecting Yes when prompted to enable SSL.

Opening the QCC GUI on the Local Server

To open the QCC GUI locally, follow these steps:
Non-secure connection:
1. Open a Web browser, and in the address bar, type the following:
http://localhost:<port_number>/QConvergeConsole

Where <port_number> is the port number you specified during

QConvergeConsole GUI installation. The default port number is 8080.
2. The main page of QConvergeConsole GUI opens, as shown in Figure 3-1.

Secure (SSL) connection:

1. Open a Web browser, and in the address bar, type the following:
https://localhost:8443/QConvergeConsole

2. The main page of QConvergeConsole GUI opens, as shown in Figure 3-1.

3-2 SN0054669-00 G
 3–Getting Started
Opening the QConvergeConsole GUI Main Page

Figure 3-1. QConvergeConsole GUI Main Page (Example)

Opening the QCC GUI on a Remote Server
To open the QCC GUI on a remote server, follow these steps:

Non-secure connection:
1. Open a Web browser, and in the address bar, type the following:
http://<server_ip>:<port_number>/QConvergeConsole/

Where <server_ip> is the IP address of the QConvergeConsole GUI

server, and <port_number> is the access port number you specified
during QConvergeConsole GUI installation. The default port number is
8080.

2. The main page of QConvergeConsole GUI opens, as shown in Figure 3-1.

Secure (SSL) connection:

1. Open a Web browser, and in the address bar, type the following:
https://<server_ip>:8443/QConvergeConsole

Where <server_ip> is the IP address of the QConvergeConsole GUI

server.
2. The main page of QConvergeConsole GUI opens, as shown in Figure 3-1.

SN0054669-00 G 3-3
3–Getting Started
Connecting to a Host Server

Figure 3-2 shows how to type in the address of the QConvergeConsole GUI
server. After you type the address and press ENTER, the QCC GUI opens to its
main page (shown in Figure 3-1).

Figure 3-2. Specifying the QConvergeConsole GUI Web Address (Example)

Connecting to a Host Server

To connect to a host server from the QConvergeConsole GUI main window:

NOTE
S

To connect to a remote host, at least one management agent used by

the host’s adapters must be installed on that host.

1. Locate the Input hostname/address box in the upper-left corner of the

QConvergeConsole GUI window.
2. Type the host name or its IP address; Figure 3-3 shows an example.

Figure 3-3. Hostname or IP Address Input (Example)

3. To initiate the connection, click Connect.

If successful, the host and its adapters appear in the system tree.

NOTE
S

Use the more check box to select the protocols (FC/FCoE, Ethernet,
iSCSI, FabricCache) that QCC GUI will display. The default is all
protocols. For more information, refer to the help system.

3-4 SN0054669-00 G
 3–Getting Started
Exiting QConvergeConsole GUI

Exiting QConvergeConsole GUI

To exit the QConvergeConsole GUI, open the File menu on the
QConvergeConsole GUI main window and click Exit.

Getting Help
This section provides the following information:
 “Browsing Help Contents” on page 3-5
 “Viewing QConvergeConsole GUI Version Details” on page 3-6

Browsing Help Contents

Access the QConvergeConsole GUI help system to view detailed information
about using the QCC GUI. For a high-level list of topics covered in the help
system, see “What Is in the Help System” on page viii.

To view the help system from the main page:

1. Open the Help menu, and then click Browse Contents.
The help window opens, showing a navigation pane on the left and a topic
pane on the right.
2. In the navigation pane, select one of the following tabs to locate the
information you want to view:
 Contents lists topics organized by task, much like the table of contents
in this user's guide. This list also includes book icons that you can
open and close to show and hide topics related to the book title. Click a
closed book icon to open it and view a list of topics. Click an opened
book icon to close it and hide its topics. Click the title of any book or
topic to view its content in the topic pane.
 Index provides an alphabetically arranged list of keywords. To jump to
a keyword, start typing it in the text box. Click any index entry to view a
related topic in the topic pane. If a keyword has more than one topic
associated with it, a popup menu opens, listing related topics you can
select.
 Search provides access to all topics in the help system using
advanced search capabilities. Type one or more keywords in the text
box, and then press ENTER. The search tool lists all topics that meet
your search criteria. Select any topic to view its contents in the topic
pane. The search tool accepts Boolean expressions (such as AND, OR,
and NOT), as well as nested expressions. It also accepts exact strings
entered between quotation marks. It does not support wild cards.

SN0054669-00 G 3-5
3–Getting Started
Viewing QConvergeConsole GUI Version Details

NOTE
While the QCC GUI supports all the Web browsers listed in “Software
Requirements” on page 1-2, some of the help system's features, such
as the Search and Index tools, may not work properly in all browsers.

Viewing QConvergeConsole GUI Version Details

If you need technical assistance with QConvergeConsole GUI, your technician will
request the version number.
To view the QConvergeConsole GUI version:
1. On the QConvergeConsole GUI main window Help menu, click About.
A message box opens; Figure 3-4 shows an example. (The message box
you view shows the actual product version number and copyright year.)

Figure 3-4. About QConvergeConsole GUI (Example)

This message box provides the following information:
 Version number
 Copyright information

2. To close the message box and return to the QConvergeConsole GUI main
page, click OK.

3-6 SN0054669-00 G
A Security Considerations

This appendix provides information on security-related topics for the

QConvergeConsole GUI.

Management Connectivity Model

Figure A-1 shows how QConvergeConsole GUI communicates in typical
deployments.
The QConvergeConsole GUI runs as an Apache Tomcat™ application server.
After it is launched on the application server, you connect to QCC through a Web
browser.

QCC GUI
Application

QCC
Console Management
Agents
Apache Tomcat
Web Server Host server

QCC
Management
Agents

Host server

Figure A-1. QCC GUI Management Connectivity

SN0054669-00 G A-1
A–Security Considerations
Managing Security

Managing Security
QCC security includes local connectivity, password and access control, Windows
firewall configuration, and Secure Sockets Layer (SSL) data encryption.

Connectivity Options
As shown in Figure A-1 on page A-1, you can connect to QCC using:
 A localhost connection (on the web application server)
 A remote connection (from another computer)
For information on how to connect to QCC from the local host server or from a
remote connection, see “Connecting to a Host Server” on page 3-4.
For information on how to install QConvergeConsole GUI for localhost
connections only, see “Installing QConvergeConsole GUI in a Windows
Environment” on page 2-5, “Installing QConvergeConsole GUI in a Linux
Environment” on page 2-6, and “Installing QConvergeConsole GUI in a Solaris
Environment” on page 2-7.

Password Protection for Access Control

NOTE
Password protection does not apply to FabricCache 10000 Series adapters.

You can password-protect a host server to prevent unauthorized changes to that

host’s installed adapters. When you do this, authorization is required to make
changes to the following on the host or any of its adapters:
 Adapter parameters
 Flash BIOS
 Adapter driver
 Port configuration
 Password (updates to the password itself)

Requirements
To set up password protection on a host, you must have administrator or root
privileges on that host.
Procedure
For detailed information on password protection on a host server, refer to the
following topics in the QCC online help:
 Setting QConvergeConsole GUI Security
 Viewing Host Security
 Using Security Check

A-2 SN0054669-00 G
 A–Security Considerations
Windows Firewall Configuration

Windows Firewall Configuration

When Windows Firewall is enabled with default settings, connections between the
QCC GUI and remote hosts are blocked. To use Windows Firewall but allow
connections between the QCC GUI and remote hosts, add the following programs
to the exceptions list in the firewall settings on both client and server machines:
 For x64 running native x64 GUI/agents:
C:\Program Files\QLogic Corporation\QConvergeConsole\
tomcat-x64\apache-tomcat-6.0.35\bin\tomcat6.exe
C:\Program Files\QLogic Corporation\portmap\portmap.exe
C:\Program Files\QLogic Corporation\nQAgent\ethernet.exe
C:\Program Files\QLogic Corporation\QLRemote\qlremote.exe
C:\Program Files\QLogic Corporation\iQLRemote\iqlremote.exe
C:\Program Files\QLogic Corporation\QLFca\qlremote_fca.exe
 For x64 running x86 GUI/agents:
C:\Program Files (x86)\QLogic Corporation\QConvergeConsole\
tomcat-x64\apache-tomcat-6.0.35\bin\tomcat6.exe
C:\Program Files (x86)\QLogic Corporation\portmap\portmap.exe
C:\Program Files (x86)\QLogic Corporation\nQAgent\ethernet.exe
C:\Program Files (x86)\QLogic Corporation\QLRemote\qlremote.exe
C:\Program Files (x86)\QLogic Corporation\iQLRemote\iqlremote.exe
C:\Program Files (x86)\QLogic Corporation\QLFca\qlremote_fca.exe
 For x86 running native x86 GUI/agents:
C:\Program Files\QLogic Corporation\QConvergeConsole\
tomcat-x86\apache-tomcat-6.0.35\bin\tomcat6.exe
C:\Program Files\QLogic Corporation\portmap\portmap.exe
C:\Program Files\QLogic Corporation\nQAgent\ethernet.exe
C:\Program Files\QLogic Corporation\QLRemote\qlremote.exe
C:\Program Files\QLogic Corporation\iQLRemote\iqlremote.exe
C:\Program Files\QLogic Corporation\QLFca\qlremote_fca.exe

Next, configure the Windows Firewall as described in the following section.

Firewall Configuration in Windows Server 2008 and Windows Server 2012

To configure the firewall on a host or client using Server Manager:
1. Follow the instructions for your operating system:
 Windows Server 2008:
a. Click Start, click Administrative Tools, and click Server Manager.
b. On the left side of the Server Manager window, expand the
Configuration node, and then expand Windows Firewall with
Advanced Security.

SN0054669-00 G A-3
A–Security Considerations
Windows Firewall Configuration

 Windows Server 2012: Do one of the following:

 Click Start, click Administrative Tools, and click Windows
Firewall with Advanced Security.
 Run the Server Manager application, click Tools, and click
Windows Firewall with Advanced Security.
2. Refer to the list of programs in “Windows Firewall Configuration” on page A-3.
For the first program in the list:
a. Right-click Inbound Rules and click New Rule.
b. The New Inbound Rule wizard opens. Select Program and click Next.
c. Click Browse to specify the path to the .exe file, and then click Next.
d. Select Allow the connection and click Next.
e. Follow the instructions for your operating system:
 Windows Server 2008: Select Domain and click Next.
 Windows Server 2012: Select Domain and Public, and then
click Next.
f. Enter a name and description for the rule, and then click Finish.
g. Server Manager displays the new rule under Inbound Rules.
3. Repeat step 2 for each program in the list, except in step 2a, click
Outbound Rules and New Rules to open the New Outbound Rule wizard.
4. If any agent was previously running, restart it.
Figure A-2 shows how the default Windows firewall settings prevent the QCC GUI
from connecting to remote hosts, and Figure A-3 shows how modifying the
settings lets the QCC GUI connect to remote hosts.

Figure A-2. Default Windows Firewall Settings—QCC Blocked from Remote Hosts

A-4 SN0054669-00 G
 A–Security Considerations
Web Server (Apache Tomcat) Security

Figure A-3. Modified Firewall Settings—QCC Able to Connect to Remote Hosts

Web Server (Apache Tomcat) Security

This section discusses security considerations for the web application server
where Apache Tomcat is run.
Secure Sockets Layer (SSL)
QCC supports Secure Sockets layer (SSL) connections, in which all information
being sent over the connection is encrypted.
To use SSL, the SSL feature must be enabled during the installation of QCC (refer
to “Installing QConvergeConsole GUI in a Windows Environment” on page 2-5 for
detailed information). To use SSL when it has not been enabled, first uninstall
QConvergeConsole GUI, and then re-install it, selecting Yes when prompted to
enable SSL.
For information on how to connect to QCC using SSL, see “Opening the
QConvergeConsole GUI Main Page” on page 3-2.

SN0054669-00 G A-5
A–Security Considerations
Web Server (Apache Tomcat) Security

A-6 SN0054669-00 G
B Troubleshooting

This appendix describes procedures that may be helpful for troubleshooting.

 “How to Change the Tomcat Port Number” on page B-2
If using the default Tomcat port number (8080) causes a port conflict, use
this procedure to change the Tomcat port number to a different port number.
 “How to Set Up a Tomcat Log File” on page B-5
Follow the instructions in this section to set up a log file for troubleshooting.

SN0054669-00 G B-1
B–Troubleshooting
How to Change the Tomcat Port Number

How to Change the Tomcat Port Number

Tomcat by default runs on port number 8080. However, port number 8080 is
widely used in other programs. In order to avoid port conflict, you can change the
Tomcat port number.

NOTE
The Tomcat port number must be within the range starting with 1,025 and
ending at 65,535.

To change the Tomcat port number:

1. Edit file server.xml, located in the conf folder of the Tomcat folder.
Path to server.xml on 32-bit Windows host: 
{Program Files}\QLogic Corporation\QConvergeConsole\
tomcat-x86\apache-tomcat-6.0.35\conf
Path to server.xml on Linux host:
/opt/QLogic_Corporation/QConvergeConsole/
apache-tomcat-6.0.35/conf

Path to server.xml on Solaris host:
/opt/QLogic_Corporation/QConvergeConsole/
apache-tomcat-6.0.35/conf
2. Find the following statement:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
3. Change 8080 to a new port number. For example, port number 6789:
<Connector port="6789" protocol="HTTP/1.1" 
connectionTimeout="20000" 
redirectPort="8443" />
4. Save the change and close file server.xml.
5. Restart Tomcat.

B-2 SN0054669-00 G
 B–Troubleshooting
How to Change the Default Port Reference Using the QConvergeConsole Shortcut

How to Change the Default Port Reference Using the

QConvergeConsole Shortcut
The QConvergeConsole installer installs a shortcut named QCC GUI (localhost)
in the Program Files menu. If the Tomcat port number is changed from 8080, the
port number in the shortcut will also need to be changed from the default value of
8080.
To change the port number for the QCC GUI shortcut:
1. Select the QCC GUI shortcut—select Start, point to All Programs, point to
QLogic Corporation, point to QConvergeConsole, and point to QCC GUI
(localhost).
2. Right-click on the QCC GUI shortcut to display the context menu.
3. Select Properties. The dialog box shown in Figure B-1 appears:

Figure B-1. QCC GUI Shortcut Properties with Default Port Number

SN0054669-00 G B-3
B–Troubleshooting
How to Change the Default Port Reference Using the QConvergeConsole Shortcut

4. In the Target field, change the port number 8080 to the port number set in
file server.xml. Port number 6789 is used in this example. 

The Properties dialog box should appear as shown in Figure B-2:

Figure B-2. QCC GUI Shortcut Properties with New Port Number
5. Click Apply to save the change, and then click OK to close the Properties
dialog box.

B-4 SN0054669-00 G
 B–Troubleshooting
How to Set Up a Tomcat Log File

How to Set Up a Tomcat Log File

This section explains how to configure Tomcat to direct debug message output
from the QCC GUI to a given file location.

Procedure on Windows-based Systems

1. Select Configure Tomcat from the Tomcat Program Files menu as shown in
Figure B-3.

Figure B-3. Tomcat Program Files Menu

The Configure Tomcat dialog box appears, as shown in Figure B-4.

Figure B-4. Configure Tomcat Dialog Box

SN0054669-00 G B-5
B–Troubleshooting
Procedure on Windows-based Systems

2. If the Tomcat server is running, the Stop button will be enabled. Click Stop
to stop the server. The screen shown in Figure B-5 appears:

Figure B-5. Stopping Server Progress

3. Select the Logging tab on the Configure Tomcat dialog box (see
Figure B-6).

Figure B-6. Logging Tab on Configure Tomcat Dialog Box

4. Click the box to the right of Redirect Stdout to enter the file location for
output from Stdout from the QCC GUI.
Click the box to the right of Redirect Stderror to enter the file location for
output from Stderror from the QCC GUI.
In Figure B-7, "C:\Temp\stdout from QCC.txt" and
"C:\Temp\stderr from QCC.txt" are used as examples.

B-6 SN0054669-00 G
 B–Troubleshooting
Procedure on Windows-based Systems

Figure B-7. Changing Locations of Output Files

5. Click Apply to make the change, as shown in Figure B-8.

Figure B-8. Locations of Output Files Changed

SN0054669-00 G B-7
B–Troubleshooting
Procedure on Linux-based Systems

6. Click the General tab as shown in Figure B-9. Click Start to restart the
Tomcat service.

Figure B-9. General Tab of Configure Tomcat Dialog Box

7. Start QConvergeConsole GUI by pointing your Web browser to:

http://localhost:8080/QConvergeConsole
To run QConvergeConsole GUI in SSL mode, point your Web browser to:
https://localhost:8443/QConvergeConsole
8. Open the log files from the locations entered in Step 4.

Procedure on Linux-based Systems

The QConvergeConsole installer installs Tomcat version 6.0.35 on Linux systems.
For Tomcat 6.0.35, the log file is set up in script file catalina.sh.
Follow these steps to change the file name of the log file:
1. Stop the Tomcat server by running the following on a command line:
". /catalina.sh stop"
2. Open file catalina.sh for editing.

B-8 SN0054669-00 G
 B–Troubleshooting
Procedure on Solaris-based Systems

The full path to catalina.sh on Linux systems is:

/opt/QLogic_Corporation/QConvergeConsole/
apache-tomcat-6.0.35/bin

3. Find the following statement:

CATALINA_OUT="$CATALINA_BASE"/logs/catalina.out

4. Change the file name in "$CATALINA_BASE"/logs/catalina.out to

the appropriate file name. For example:
CATALINA_OUT="$CATALINA_BASE"/logs/QCC.out

5. Save the change and close the file.

6. Restart the Tomcat server by running the following on a command line:
"./catalina.sh start"

Procedure on Solaris-based Systems

The QConvergeConsole installer installs Tomcat version 6.0.35 on Solaris
systems. For Tomcat 6.0.35, the log file is set up in script file catalina.sh.
There are three references to the log file in the script.
Follow these steps to update the name of the log file:
1. Stop the Tomcat server by entering the following on a command line:
". /catalina.sh stop"
2. Open file catalina.sh for editing.
The full path to catalina.sh on Solaris systems is:
/opt/QLogic_Corporation/QConvergeConsole/
apache-tomcat-6.0.35/bin

3. Find the following statement:

touch "$CATALINA_BASE"/logs/catalina.out
4. Change the file name in "$CATALINA_BASE"/logs/catalina.out to
the appropriate file name. For example:
touch "$CATALINA_BASE"/logs/QCC.out

5. About 12 lines farther down, look for the following line:

>> "$CATALINA_BASE"/logs/catalina.out 2>&1 &

Make a similar change to this line as was done in the previous step:
>> "$CATALINA_BASE"/logs/QCC.out 2>&1 &

SN0054669-00 G B-9
B–Troubleshooting
Procedure on Solaris-based Systems

6. About 12 lines farther down, look for the following line:

>> "$CATALINA_BASE"/logs/catalina.out 2>&1 &

Make the same change to this line as was done previously:

>> "$CATALINA_BASE"/logs/QCC.out 2>&1 &

7. Save the change and close the file.

8. Restart the Tomcat server by entering the following on the command line:
". /catalina.sh start"

B-10 SN0054669-00 G
 Glossary

adapter driver
The board that interfaces between the The software that interfaces between the
host system and the target devices. file system and a physical data storage
Adapter is synonymous with host bus device or network media.
adapter (HBA), host adapter, and adapter
board. Enhanced Ethernet
Also called Data Center Ethernet or
adapter port Converged Enhanced Ethernet. Refers to
A port on the adapter board. new enhancements to the existing
Ethernet standard that eliminate Ethernet’s
CLI inherently lossy nature and make 10Gb
Command line interface. A program inter- Ethernet a viable storage networking
face driven by entering commands and transport.
parameters.
Ethernet
Converged Network Adapter The most widely used LAN technology that
QLogic Converged Network Adapters. transmits information between computer,
support both data networking (TCP/IP) typically at speeds of 10 and 100 million
and storage networking (Fibre Channel) bits per second (Mbps).
traffic on a single I/O adapter using two
new technologies: Enhanced Ethernet and FC
Fibre Channel over Ethernet (FCoE). See Fibre Channel.

command line interface FCoE

See CLI. Fibre Channel over Ethernet. A new
technology defined by the T11 standards
device body that allows traditional Fibre Channel
A target, typically a disk drive. Hardware storage networking traffic to travel over an
such as a disk drive, tape drive, printer, or Ethernet link by encapsulating Fibre
keyboard that is installed in or connected Channel frames inside Layer 2 Ethernet
to a system. In Fibre Channel, a target frames. For more information, visit
device. www.fcoe.com.

SN0054669-00 G Glossary-1
User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

Fibre Channel path

A high-speed serial interface technology A path to a device is a combination of a
that supports other higher layer protocols adapter port instance and a target port as
such as SCSI and IP. distinct from internal paths in the fabric
network. A fabric network appears to the
Fibre Channel over Ethernet operating system as an opaque network
See FCoE. between the adapter (initiator) and the
target.
Internet Protocol
Because a path is a combination of an
See IP. adapter and a target port, it is distinct from
another path if it is accessed through a
Internet small computer system interface
different adapter or it is accessing a
See iSCSI. different target port. Consequently, when
switching from one path to another, the
IP
driver might be selecting a different
Internet Protocol. A method by which data adapter (initiator), a different target port, or
are sent from one computer to another both.
over the Internet. IP specifies the format of
This is important to the driver when
packets, also called datagrams, and the
selecting the proper method of failover
addressing scheme.
notification. It can make a difference to the
iSCSI target device, which might have to take
different actions when receiving retries of
Internet small computer system interface.
the request from another initiator or on a
Protocol that encapsulates data into IP
different port.
packets to send over Ethernet connec-
tions. port
management workstation Access points in a device where a link
attaches. There are four types of ports, as
PC workstation used to manage routers
follows:
remotely by connecting to the routers
using the QConvergeConsole GUI or CLI  N_Port—a Fibre Channel port that
commands. supports point-to-point topology.
 NL_Port—a Fibre Channel port that
NIC supports loop topology.
Network interface card. Computer card  F_Port—a port in a fabric where an
installed to enable a dedicated network N_Port can attach.
connection.  FL_Port—a port in a fabric where an
NL_Port can attach.

Glossary-2 SN0054669-00 G
 User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

port instance SCSI

The number of the port in the system. Small computer system interface. A
Each adapter may have one or multiple high-speed interface used to connect
ports, identified with regard to the adapter devices, such as hard drives, CD drives,
as port 0, port 1 and so forth. To avoid printers, and scanners, to a computer. The
confusion when dealing with a system SCSI can connect many devices using a
containing numerous ports, each port is single controller. Each device is accessed
assigned a port instance number when the by an individual identification number on
system boots up. So Port 0 on an adapter the SCSI controller bus.
might have a port instance number of 8, for
example, if it is the eighth port discovered secure sockets layer
by the system. See SSL.

RAID SSL
Redundant array of independent/inexpen- Secure sockets layer. A cryptographic
sive disks. RAID are fault-tolerant disks protocol that provides communications
that look like either single or multiple security over the Internet.
volumes to the server.
storage area network
RAM See SAN.
Random-access memory. The most
common computer memory that can be target
used by programs to perform necessary The storage-device endpoint of a SCSI
tasks while the computer is on; an session. Initiators request data from
integrated circuit memory chip. RAM targets. Targets are typically disk-drives,
allows information to be stored or tape-drives, or other media devices.
accessed in any order (randomly), and all Typically a SCSI peripheral device is the
storage locations are equally accessible. target but an adapter may, in some cases,
be a target. A target can contain many
random-access memory LUNs.
See RAM. A target is a device that responds to a
requested by an initiator (the host system).
redundant array of
Peripherals are targets, but for some
independent/inexpensive disks
commands (for example, a SCSI COPY
See RAID. command), the peripheral may act as an
initiator.
SAN
Storage area network. Multiple storage TCP
units (disk drives) and servers connected Transmission control protocol. A set of
by networking topology. rules to send data in packets over the
Internet protocol.

SN0054669-00 G Glossary-3
User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

Glossary-4 SN0054669-00 G
 Index

A C
About box 3-6 CLI
adapters definition of Glossary-1
definition of Glossary-1 tool vii
port, definition of Glossary-1 client browser requirements 1-3
server requirements 1-2 closing the QCC GUI 3-5
supported series 1-4 CNA, See Converged Network Adapter
agent (server), requirements 1-3 command line interface, See CLI
agent installer, built-in 2-4 connecting to host server 3-4
agents contents, help system 3-5
downloading 2-2, 2-4 conventions, documentation x
Ethernet 2-2 Converged Network Adapter, definition of
FabricCache 2-2 Glossary-1
FCoE 2-2
Fibre Channel 2-2
installing 2-2, 2-3, 2-4 D
iSCSI 2-2
definitions of terms Glossary-1
agreements, license xi
devices
Apache Tomcat
definition of Glossary-1
changing default port B-2, B-3
requirements 1-2
requirements 1-2
disk space requirements 1-1
server, system requirements 1-3
documentation
setting up log file for A-2, B-5
conventions x
audience, intended vii
related vii
downloading agents 2-2, 2-4
downloading QConvergeConsole GUI 2-2
B drivers
Boolean help system search 3-5 definition of Glossary-1
browsers required 1-2
requirements, client 1-3 software requirements 1-2
supported 1-2
browsing help content 3-5

SN0054669-00 G Index-1
User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

E installing QCC
in silent mode 2-7
Ethernet on Linux 2-6
definition of Glossary-1 on Solaris 2-7
ports, managing ix on Windows 2-5
EULA, software xi steps to perform before 2-1
exiting the QCC GUI 3-5 instance (port), definition of Glossary-3
intended audience vii
Internet Protocol, See IP
F Internet small computer system interface, See
iSCSI
FCoE Introduction dialog box (installation) 2-6, 2-8
definition of Glossary-1 IP, definition of Glossary-2
Fibre Channel over Ethernet, See FCoE iSCSI
definition of Glossary-2

G
getting help 3-5 L
getting started 3-1 license agreements xi
glossary of terms Glossary-1 Linux
graphics adapter, requirements 1-1 installing agents on 2-2
installing QCC on 2-6
uninstalling agents on 2-11
H uninstalling QCC on 2-10
hardware requirements 1-1 local server, opening QCC GUI on 3-2
help system
contents of viii
viewing 3-5 M
host server, connecting to 3-4 main page, opening 3-2
management agent, See agents
management connectivity A-1
I management workstation, definition of
Glossary-2
index, help system 3-5
materials, related vii
installing agents
memory requirement 1-2
FabricCache 2-2, 2-4
on Linux 2-2
on Solaris 2-2, 2-3
on Windows 2-2 N
network interface card, See NIC
NIC
definition of Glossary-2

Index-2 SN0054669-00 G
 User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

O requirements
Apache Tomcat 1-2
opening QCC GUI Apache Tomcat server 1-3
on a remote server 3-3 client browser 1-3
opening the QCC GUI hardware 1-1
on the local server 3-2 managing adapters on a host
operating system requirements 1-3 operating system 1-3
server agent 1-3
server, adapter 1-2
P software 1-2
system 1-1
path, definition of Glossary-2
port
definition of Glossary-2
instance, definition of Glossary-3
S
port number, Tomcat 2-5, 2-7, 2-8 SAN
preface vii adapters, managing vii
product information, viewing 3-6 definition of Glossary-3
hardware requirements 1-2
SCSI, definition of Glossary-3
Q search, help system 3-5
secure sockets layer, See SSL
QLogic adapters, supported 1-4
security
firewall configuration, Windows A-3
local vs remote connectivity A-2
R password protecting access A-2
RAID SSL A-5
definition of Glossary-3 server (host), connecting to 3-4
SAN subsystems 1-2 server agent requirements 1-3
RAM server requirements 1-2
definition of Glossary-3 Apache Tomcat 1-3
requirement 1-2 silent mode, installing QCC in 2-7
random-access memory, See RAM small computer system interface (SCSI),
redundant array of independent/inexpensive definition of Glossary-3
disks, See RAID small computer system interface, See SCSI
related materials vii software EULA xi
remote host, connecting to 3-4 software requirements 1-2
remote server, opening QCC GUI on 3-3 Solaris
installing agents on 2-2
installing QCC on 2-7
uninstalling agents on 2-11
uninstalling QCC on 2-11

SN0054669-00 G Index-3
User’s Guide QConvergeConsole GUI
2400, 2500, 2600, 3200, 4000, 8100, 8200, 8300, and 10000 Series

SSL video card, requirements 1-1

definition of Glossary-3
enabling during installation 2-6, 2-7, 2-8, 3-2
opening QCC GUI using 3-2, 3-3 W
requirement 1-2
starting the QCC GUI 3-2 Web browsers
storage area network, See SAN supported 1-2
SuperInstaller what’s in this guide vii
installing agents 2-2 Windows
support, technical xi installing agents on 2-2
supported adapters 1-4 installing QCC on 2-5
system requirements 1-1 uninstalling agents on 2-10
uninstalling QCC on 2-9
workstation (management), definition of
Glossary-2
T
target, definition of Glossary-3
TCP, definition of Glossary-3
technical support xi
terms and definitions Glossary-1
Tomcat Port Number Setup dialog box 2-5,
2-7, 2-8
Tomcat, See Apache Tomcat
transmission control protocol, See TCP

U
Uninstall Complete dialog box 2-10
Uninstall Options dialog box 2-9, 2-10
Uninstall QConvergeConsole dialog box 2-9,
2-10
uninstalling agents
on Linux 2-11
on Solaris 2-11
on Windows 2-10
uninstalling QCC
on Linux 2-10
on Solaris 2-11
on Windows 2-9

V
version (product), viewing 3-6

Index-4 SN0054669-00 G
 Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com
International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan

© 2010–2013 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic, the QLogic logo, and QConvergeConsole
are registered trademarks of QLogic Corporation. Apache Tomcat and Tomcat are trademarks of The Apache Software Foundation. Apple and Safari are registered
trademarks of Apple, Inc., registered in the U.S. and other countries. Citrix and XenServer are registered trademarks of Citrix Systems, Inc. Google Chrome is a trademark
of Google, Inc. InstallAnywhere is a trademark or registered trademark of Zero G Software, Inc. Intel is a registered trademark and Core is a trademark of Intel Corporation
in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Microsoft, Internet Explorer, Windows, Windows Server 2008, and Windows
Server 2012 are registered trademarks of Microsoft Corporation in the United States and other countries. Mozilla and Firefox are registered trademarks of the Mozilla
Foundation. Novell, SLES, and SUSE are registered trademarks of Novell, Inc. in the United States and other countries. Opera is a registered trademark of Opera Software
ASA. Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries. Solaris is a trademark of Oracle Corporation, in
the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an architecture
developed by Sun Microsystems, Inc. VNC is a registered trademark of RealVNC Ltd. in the United States and other countries. All other brand and product names are
trademarks or registered trademarks of their respective owners. Information supplied by QLogic Corporation is believed to be accurate and reliable. QLogic Corporation
assumes no responsibility for any errors in this brochure. QLogic Corporation reserves the right, without notice, to make changes in product design or specifications.