Installation Guide—QConvergeConsole GUI

Installation Guide—QConvergeConsole GUI
Installation Guide
QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000,
8100, 8200, 8300, 8400, 45000, and 10000 Series
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000
This document is provided for informational purposes only and may contain errors. QLogic reserves the right, without
notice, to make changes to this document or in product design or specifications. QLogic disclaims any warranty of any
kind, expressed or implied, and does not guarantee that any results or performance described in the document will be
achieved by you. All statements regarding QLogic's future direction and intent are subject to change or withdrawal
without notice and represent goals and objectives only.
Document Revision History
Revision A, January 31, 2014
Revision B, April 24, 2014
Revision C, March 3, 2017
Revision D, March 24, 2015
Revision E, August 24, 2015
Revision F, February 22, 2015
Revision G, April 14, 2016
Revision H, April 19, 2016
Revision J, April 25, 2016
Revision K, August 29, 2016
Revision L, September 30, 2016
Revision M, January 17, 2017
Revision N, March 3, 2017
Changes
Sections Affected
Removed obsolete note regarding downloading
the QLogic Storage Networking Interoperability
Guide.
“Hardware Requirements” on page 1
Removed reference to “Port 8443 for SSL connection (if the SSL option is selected upon installation).”
“Software Requirements” on page 2
Removed reference to Windows 2008. Added a
note stating: “The following adapters currently do
not support Solaris:
“Operating System Requirements” on page 3
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network
Adapters”
ii
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000,\r 8100, 8200, 8300, 8400, 45000, and 10000 Series
Added a new bullet: “If installing SSMC and NFS
along with QConvergeConsole GUI, ensure that
TCP ports 8080, 8443, and 111 are not in use.
Doing so helps proper installation of QConvergeConsole GUI. For more information, see “Installing
QLogic QConvergeConsole Beside SSMC and
vPower NFS Service” on page 58.”
“Before installing QConvergeConsole GUI:” on
page 6
Renamed the section from “Installing the Agents
from the QLogic Website” to “Installing the Agents”
“Installing the Agents” on page 7
In the procedure, “To install agents on Windows
and Linux (all supported versions),” deleted the
reference to the SuperInstaller in Step 2 and
Step 3.
In the procedure, “To install agents on Solaris,”
added a new note: “The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network
Adapters”
Updated reference from “libtc18.4” to “libtcl 8.4” in
Step 4.
“To install agents on Ubuntu 14.04 (for qlremote
and qlnxremote agents only):” on page 8
Added a new note: “The following adapters currently do not support Solaris:
“Agent Installation on Solaris 10, 11” on page 9
“Installation with Package Files (Solaris 10, 11)” on
page 10
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
“Installation with p5p Files (Solaris 11 or Later)” on
page 10
 FastLinQ 45000 Series Converged Network
Adapters”
“Installing QConvergeConsole GUI in a Solaris
Environment” on page 16
“Uninstalling QConvergeConsole GUI in a Solaris
Environment” on page 24
Added the following new Step 11: In the Tomcat
SSL Port Number Setup dialog box, type a valid
SSL port number in the range 1025–65536, or
accept the default port number, 8443. Then click
Next to continue.
“Installing QConvergeConsole GUI in a Linux Environment” on page 14
Added the following new Step 10: In the Tomcat
SSL Port Number Setup dialog box, type a valid
SSL port number in the range 1025–65536, or
accept the default port number, 8443. Then click
Next to continue.
“Installing QConvergeConsole GUI in a Solaris
Environment” on page 16
iii
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000,\r 8100, 8200, 8300, 8400, 45000, and 10000 Series
“Installing QConvergeConsole GUI in a Console
Window” on page 18
Added the following new parameters and note:
-DSECURITY_LOGIN=<1_OR_0>: Use this option
to enable Security Login feature. Default value is 0.
-DSECURITY_LOGIN_STR=<String>: Login setting for Security Login feature. Default value is
QCC.
-DSECURITY_PASSWORD_STR=<String>: Password setting for Security Login feature. Default
value is config.
-DUSER_INPUT_SSL_PORT_NUMBER: Use this
option to change Tomcat SSL Port Number.
-DLOG_LOCATION: Use this option to change Log
directory. Default value is installation folder.
Note: The -D options listed above are applicable to
silent install only.
Added a new section.
“Installing the QLNXRemote Agent on Windows
Nano Server” on page 28
Changed “8443” to “<SSL_port number>” in
Step 2.
“Opening QCC GUI on the Local Server” on
page 31
Changed “8443” to “<SSL_port number>” in
Step 2.
“Opening QCC GUI on a Remote Server” on
page 31
Added a new paragraph, “The default security
login password is config.”
“Password Protection for Access Control” on
page 37
Added a new section for program numbers used
for QConvergeConsole and SANsurfer agents.
“Program Numbers Used for QConvergeConsole
and SANsurfer Agents” on page 38
Removed the section, “Changing the Tomcat Port
Number.”
Chapter 5 Troubleshooting
Removed the section, “Changing the Default Port
Reference Using the QConvergeConsole Shortcut”.
Added a new section, Installing QLogic QConvergeConsole Beside SSMC and vPower NFS
Service
iv
SN0051105-00 N
Table of Contents
Preface
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Is in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Is in the Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
System Requirements
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported QLogic Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
ix
ix
x
xi
xii
xiii
xiv
xiv
xv
xv
xv
1
2
3
4
Installing QConvergeConsole GUI
Downloading QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading and Installing Management Agents . . . . . . . . . . . . . . . . . . . .
Installing the Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Installation on Solaris 10, 11 . . . . . . . . . . . . . . . . . . . . . .
Installing the Agents Using the Built-in Agent Installer . . . . . . . . . . . . . . . . .
Installing the QLNXRemote Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing QConvergeConsole GUI in a Windows Environment. . . . . .
Installing QConvergeConsole GUI in a Linux Environment. . . . . . . . .
Installing QConvergeConsole GUI in a Solaris Environment . . . . . . .
Installing QConvergeConsole GUI in a Console Window . . . . . . . . . .
v
7
7
7
9
11
12
12
13
14
16
18
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
Uninstalling QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling QConvergeConsole GUI in a Windows Environment . . .
Uninstalling QConvergeConsole Agents in Windows . . . . . . . . .
Uninstalling QConvergeConsole GUI in a Linux Environment . . . . . .
Uninstalling QConvergeConsole Agents in Linux . . . . . . . . . . . .
Uninstalling QConvergeConsole GUI in a Solaris Environment . . . . .
Uninstalling QConvergeConsole Agents on Solaris . . . . . . . . . .
Uninstalling QConvergeConsole GUI in a Console Window . . . . . . . .
Installing the QLRemote Agent on Windows Nano Server. . . . . . . . . . . . . .
Installing the QLNXRemote Agent on Windows Nano Server . . . . . . . . . . .
3
Getting Started
Starting QConvergeConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the QConvergeConsole GUI Main Page. . . . . . . . . . . . . . . .
Opening QCC GUI on the Local Server . . . . . . . . . . . . . . . . . . .
Opening QCC GUI on a Remote Server . . . . . . . . . . . . . . . . . .
Connecting to a Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Forward Error Correction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exiting QConvergeConsole GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Browsing Help Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing QConvergeConsole GUI Version Details . . . . . . . . . . . . . . . .
4
21
22
23
23
24
24
25
25
26
28
30
30
31
31
32
33
33
33
34
35
Security Considerations
Management Connectivity Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectivity Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password Protection for Access Control . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Program Numbers Used for QConvergeConsole and
SANsurfer Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firewall Configuration in Windows Server 2008, 2012,
and 2016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Red Hat Enterprise Linux (RHEL) 7.x and SLES 12.x . . . . . . . .
Red Hat Enterprise Linux (RHEL) 5.x and 6.x . . . . . . . . . . . . . .
SUSE 11.x, 10.x, and 12.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web Server (Apache Tomcat) Security . . . . . . . . . . . . . . . . . . . . . . . .
Secure Sockets Layer (SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
36
37
37
37
37
38
38
38
39
41
41
42
43
44
44
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
5
Troubleshooting
Recommendations for Solaris Hot Swap, Dynamic Reconfiguration,
Suspend and Resume Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping the QCC GUI Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the QCC Agents Without Rebooting the Server . . . . . . . . . . .
Removing QCC GUI Agents for an Ongoing Hot Swap, Dynamic
Reconfiguration, Suspend or Resume Operation . . . . . . . . . . . . . . .
Setting a Tomcat Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure on Windows-based Systems . . . . . . . . . . . . . . . . . . . . . . .
Procedure on Linux-based Systems . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure on Solaris-based Systems . . . . . . . . . . . . . . . . . . . . . . . . .
Installing QLogic QConvergeConsole Beside SSMC and vPower
NFS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
45
45
46
46
46
49
50
51
Glossary
Index
vii
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
List of Figures
Figure
Page
2-1
Example of Console Window Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
2-2
Example of Console Window Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
3-1
QConvergeConsole GUI Main Page (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
3-2
Hostname or IP Address (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
3-3
About QConvergeConsole GUI (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
4-1
QCC GUI Management Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
4-2
Default Windows Firewall Settings—QCC Blocked from Remote Hosts . . . . . . . . .
40
4-3
Modified Firewall Settings—QCC Able to Connect to Remote Hosts . . . . . . . . . . .
40
5-1
Tomcat Program Files Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
5-2
Apache Tomcat Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
5-3
Stopping Server Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
5-4
Changing Locations of Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
5-5
General Page of Apache Tomcat Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
5-6
TCP Ports 8080, 8443, and 111 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
5-7
HPE 3PAR StoreServ Management Console Server Properties Window . . . . . . . .
52
5-8
Veeam vPower NFS Service Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
5-9
Security Login Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
5-10 QConvergeConsole Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
5-11 TCP Ports 8080,8443, and 111 in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
5-12 MBA Boot Cfg Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
5-13 Boot Config Updated Successfully Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
viii
SN0051105-00 N
Preface
This guide describes how to install, uninstall, and start QConvergeConsole® GUI,
a Web-based management tool for configuring and managing QLogic Fibre
Channel adapters, Intelligent Ethernet adapters, and Converged Network
Adapters within SANs.
Throughout this guide, the QConvergeConsole GUI management tool is also
referred to as QCC GUI, and the terms target and device are used
interchangeably.
NOTE
QLogic now supports QConvergeConsole GUI as the only GUI management
tool across all adapters. QLogic Control Suite GUI is no longer supported for
the 3400/8400 Series Adapters and adapters based on 57xx/57xxx
controllers, and has been replaced by the QConvergeConsole GUI
management tool. QConvergeConsole GUI provides single-pane-of-glass
GUI management for all QLogic adapters.
In Windows environments, when you run the QCS CLI and Management
Agents Installer, it will uninstall QLogic Control Suite (QCS) GUI (if installed
on system) and any related components from your system. To obtain the
new GUI, download QConvergeConsole GUI for your adapter from the
QLogic Downloads Web page:
http://driverdownloads.qlogic.com
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:
driverdownloads.qlogic.com

QConvergeConsole Read Me and Release Notes documents contain
information about installation, OS support, and known issues.
ix
SN0051105-00 N
Preface
What Is in This Guide

User’s Guide—QConvergeConsole CLI (part number SN0054667-00)
contains information detailed information on how to install and use the
QConvergeConsole CLI management tool.

User’s Guide—QConvergeConsole Plug-Ins for 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
QConvergeConsole GUI.
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
QConvergeConsole GUI.

Chapter 2 Installing QConvergeConsole GUI describes how to install and
uninstall QConvergeConsole GUI.

Chapter 3 Getting Started describes how to start and exit
QConvergeConsole GUI and how to access the QCC GUI help system.

Chapter 4 Security Considerations provides information on security-related
topics for QConvergeConsole GUI.

Chapter 5 Troubleshooting provides procedures that may be helpful for
troubleshooting.
Included also are a glossary of terms used and an index to help you quickly find
information.
x
SN0051105-00 N
Preface
What Is in the Help System
What Is in the Help System
NOTE
To access help, see “Getting Help” on page 33.
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 QConvergeConsole GUI.
For instructions on accessing the help system, refer to “Getting Help” on page 33.
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.

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, and 2700 Series)
or Converged Network Adapter (8100, 8200, and 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 the Fibre Channel and Fibre
Channel over Ethernet (FCoE) driver.
xi
SN0051105-00 N
Preface
Documentation Conventions

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, and 8400 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,
and 3400 Series Intelligent Ethernet Adapters, as well as for 8100, 8200,
8300, 8400, and 45000 Series Converged Network Adapters.

Managing FabricCache® Adapters and Ports shows and describes how to
display and edit information for 10000 Series FabricCache Adapters (FCAs)
and ports, as well as how to configure port parameters.

Managing FabricCache Adapter Settings shows and describes how to
use the system tree on the QCC GUI Storage page, 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, Fibre Channel and FCoE parameters,
parameter files, passwords, and agents, and to configure FCA clusters.

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.

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 websites are shown in underlined blue. For example:

Table 9-2 lists problems related to the user interface and remote
agent.
xii
SN0051105-00 N
Preface
License Agreements






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.
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
For a complete list of all license agreements affecting this product, refer to the
QLogic Software End User License Agreement.
xiii
SN0051105-00 N
Preface
Technical Support
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 Website 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:
http://www.qlogic.com/Support/Pages/ServicePrograms.aspx
Downloading Updates
The QLogic Website provides periodic updates to product firmware, software, and
documentation.
To download firmware, software, and documentation:
1.
Go to the QLogic Downloads and Documentation page:
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, software, or
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.
6.
Save the file to your computer.
7.
If you have downloaded firmware, software, drivers, or boot code, follow the
installation instructions in the Read Me document.
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.
xiv
SN0051105-00 N
Preface
Training
Training
QLogic Global Training maintains a Website 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:
support.qlogic.com
Support Headquarters
QLogic Corporation
12701 Whitewater Drive, Suite 230
Minnetonka, MN 55343 USA
QLogic Website
www.qlogic.com
Technical Support Website
support.qlogic.com
Technical Support E-mail
support@qlogic.com
Technical Training E-mail
training@qlogic.com
Knowledge Database
The QLogic knowledge database is an extensive collection of QLogic product
information that you can search for specific solutions. QLogic is constantly adding
to the collection of information in the database to provide answers to your most
urgent questions. Access the database from the QLogic Support Center:
support.qlogic.com
xv
SN0051105-00 N
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, QConvergeConsole GUI runs as an Apache Tomcat™
application server. After QConvergeConsole GUI is launched on the application
server, you can connect to 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

Software Requirements

Operating System Requirements

Supported QLogic Adapters
Hardware Requirements
QConvergeConsole GUI requires the following minimum hardware:
Apache Tomcat application server

Server—Single processor or multiprocessor equivalent to an Intel® or AMD
Core™ Duo running at 1GHz or greater. For operating systems on which the
Web browser can run, see “Operating System Requirements” on page 3.

Memory—2GB of physical RAM to run QConvergeConsole GUI; 4GB
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
1
SN0051105-00 N
1–System Requirements
Software Requirements
Server agent
Adapters—One or more of the QLogic adapters listed under “Supported
QLogic Adapters” on page 4

SAN

Storage—Fibre Channel or iSCSI devices, such as disks and RAID
subsystems
Software Requirements
This section lists the minimum software requirements.
NOTE
For details on supported software versions, see the QConvergeConsole
Read Me. To download support documents, go to:
driverdownloads.qlogic.com

QLogic adapter drivers for your operating system (To download QLogic
adapter drivers, go to driverdownloads.qlogic.com.)

QLogic adapter management agents for your operating system

TCP/IP protocol for Windows® remote management

Administrative privileges to perform management functions

User access control disabled on Windows Server® 2008,
Windows Server 2012, Windows 2012 R2, and Windows 2016 to run the
agent service. A LocalHost Only feature is available if needed.

Domain name service (DNS) running in the network is required if Hostname
is used for connection
Apache Tomcat Application Server Requirements
Apache Tomcat application server must have the following:

Apache Tomcat (installed automatically by QCC GUI installer if not present)

QConvergeConsole GUI (before installing, refer to the Note on page 6)
Web Browser Requirements
Web Browser must be one of the following:

Google Chrome™

Mozilla® Firefox®

Microsoft® Internet Explorer®

Opera®

Apple® Safari®
2
SN0051105-00 N
1–System Requirements
Operating System Requirements
NOTE
Some auxiliary help features, such as the Search and Index tools, may not
work properly in every Web browser.
Operating System Requirements
The client, Apache Tomcat application server, and server agent each have their
own operating system requirements.
Client
The client requires one of the following operating systems to host a supported
Web browser (see “Software Requirements” on page 2):

Windows Server 2008 R2, 2012, 2012 R2, 2016

Red Hat® Linux® Advanced Server and Enterprise Server

Novell® SUSE® Linux Enterprise Server (SLES®)

Oracle Linux—Unbreakable Enterprise Kernel (UEK)

Solaris® 10, 11
NOTE
To run QConvergeConsole GUI on Solaris 10 or 11, you must disable the
firewall by entering the following command after each boot-up and before
running QCC GUI: netservices open
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
Apache Tomcat Application Server
The server requires one of the following operating systems to host the Tomcat
server for QConvergeConsole GUI:

Windows Server 2008 R2, 2012, 2012 R2, 2016

Red Hat Linux Advanced Server and Enterprise Server

Novell SUSE Linux Enterprise Server (SLES)

Oracle Linux—Unbreakable Enterprise Kernel (UEK)

Solaris 10, 11

Citrix® XenServer®
3
SN0051105-00 N
1–System Requirements
Supported QLogic Adapters
Server Agent
Multiple operating system support allows control of heterogeneous environments.
The QConvergeConsole GUI server agent works with the following operating
systems:

Windows Server 2008 R2, 2012, 2012 R2, 2016, Nano

Red Hat Linux Advanced Server and Enterprise Server

Novell SUSE Linux Enterprise Server (SLES)

Solaris 10, 11

CentOS®

Ubuntu® Server
NOTE
For details on operating system versions, see the QConvergeConsole Read
Me, which you can download from driverdownloads.qlogic.com.
Supported QLogic Adapters
QConvergeConsole GUI supports the following QLogic-branded adapters. For
support of OEM-branded adapters, contact your OEM.

2400, 2500, 2600, and 2700 Series Fibre Channel Adapters

3200 Series Intelligent Ethernet Adapters

FastLinQ® 3400 Series Intelligent Ethernet Adapters

4000 Series iSCSI Adapters

8100, 8200, 8300, and 8400 Series Converged Network Adapters

FastLinQ 45000 Series Converged Network Adapters

10000 Series FabricCache Adapters
NOTE
For information about QLogic adapters, refer to the QLogic website:
http://www.qlogic.com/Products/adapters
4
SN0051105-00 N
2
Installing
QConvergeConsole GUI
This chapter provides information on downloading, installing, and uninstalling
QConvergeConsole GUI, and downloading, and installing management agents:

Downloading QConvergeConsole GUI

Downloading and Installing Management Agents

Installing QConvergeConsole GUI

Uninstalling QConvergeConsole GUI

Installing the QLRemote Agent on Windows Nano Server

Installing the QLRemote Agent on Windows Nano Server
5
SN0051105-00 N
2–Installing QConvergeConsole GUI
NOTE
Before installing QConvergeConsole GUI:
 QLogic now supports QConvergeConsole GUI as the only GUI
management tool across all adapters. QLogic Control Suite GUI is no
longer supported for the 3400 Series Adapters and adapters based on
57xx/57xxx controllers, and has been replaced by the
QConvergeConsole GUI management tool. QConvergeConsole GUI
provides single-pane-of-glass GUI management for all QLogic adapters.
In Windows environments, when you run the QCS CLI and Management
Agents Installer, it will uninstall QLogic Control Suite (QCS) GUI (if
installed on system) and any related components from your system. To
obtain the new GUI, download QConvergeConsole GUI for your adapter
from the QLogic Downloads Web page:
http://driverdownloads.qlogic.com
 If installing SSMC and NFS along with QConvergeConsole GUI, ensure
that TCP ports 8080, 8443, and 111 are not in use. Doing so helps
proper installation of QConvergeConsole GUI. For more information, see
“Installing QLogic QConvergeConsole Beside SSMC and vPower NFS
Service” on page 51.
 Read the documents listed in “Related Materials” on page ix, as
applicable, for important, up-to-date product information.
 If using Windows firewalls, refer to “Windows Firewall Configuration” on
page 38 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 at 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 37. (You can also
manually specify the Tomcat port number.)
 For information on creating a Tomcat log file for troubleshooting, refer to
“Setting a Tomcat Log File” on page 46.
 To enable access to the adapters on a host server, the management
agents—qlremote (Fibre Channel/FCoE), qlnxremote (FastLinQ),
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
“Downloading and Installing Management Agents” on page 7.
6
SN0051105-00 N
2–Installing QConvergeConsole GUI
Downloading QConvergeConsole GUI
Downloading QConvergeConsole GUI
To download QConvergeConsole GUI, follow the procedure in “Downloading
Updates” on page xiv.
Downloading and Installing Management Agents
To manage the adapters on a local or remote host, the management agents (also
called agents) used by the host’s adapters must already be installed on the host.
To connect to a remote host, at least one management agent used by any of the
host’s adapters must be installed and running on the host. Only protocols whose
agents are installed and running are shown under the host’s system tree node.
The management agents include the following:

netqlremote for Ethernet Networking (NIC)

qlremote for Fibre Channel and FCoE

iqlremote for iSCSI

qlremote_fca for FabricCache Adapter

qlnxremote for 3400 and 45000 Adapters
The management agents are not automatically installed by the QCC GUI installer
and must be downloaded and installed separately. You can download the agents
from the QLogic Website Downloads page, or using the built-in Agent Installer.
Installing the Agents
Use the following procedure to install the netqlremote, qlremote, iqlremote, and
qlnxremote agents from the QLogic Website. For qlremote_fca, see “Installing the
Agents Using the Built-in Agent Installer” on page 11 for download and installation
instructions.
To install agents on Windows and Linux (all supported versions):
1.
Go to the QLogic Downloads page at driverdownloads.qlogic.com.
2.
Download the following for each adapter on the host server:
3.

Read Me

Release Notes
Install the agents by running the appropriate installer. Refer to the Read Me
and Release Notes for detailed information on running the installer.
7
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the Agents
To install agents on Solaris:
NOTE
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
1.
Go to the QLogic Downloads page at driverdownloads.qlogic.com.
2.
Download the following for each adapter on the host server:
3.

Solaris 10, 11: Installer package files

Solaris 11: p5p files
Install one or more agents as described in “Agent Installation on Solaris 10,
11” on page 9.
To install agents on Ubuntu 14.04 (for qlremote and qlnxremote agents
only):
1.
To install the alien, issue the following command:
apt-get install alien
2.
To install rpcbind, issue the following command:
apt-get install rpcbind
3.
Issue the following command:
alien -i --scripts -k ./<installer name.rpm>
4.
To install libtcl 8.4 (for qlnxremote agents only), issue the following
command:
apt-get install libtcl8.4
5.
To disable the firewall, issue the following command:
ufw disable
NOTE
S
For more detailed Firewall configuration, go to
https://help.ubuntu.com/community/UFW.
8
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the Agents
Agent Installation on Solaris 10, 11
NOTE
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
To install the agents on Solaris, follow the instructions in the appropriate section:

Installation with Package Files (Solaris 10, 11)

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.
9
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the Agents
Installation with Package Files (Solaris 10, 11)
NOTE
S
QLNXRemote agent is not available in Solaris 10 and 11.
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
To install the Solaris agents using package files:
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
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
Select one of the following options to install the p5p installer:

Option 1: Install the Solaris agents by issuing the p5p installer command:
pkg install -g <agent>-<version>-solaris-<arch>.p5p qlremote

Option 2: Install the Solaris agents using p5p files:
1.
Set the environment by issuing the following command:
export PKGREPO=/pkgrepo
10
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the Agents Using the Built-in Agent Installer
2.
Create the repository by issuing the following command:
pkgrepo create $PKGREPO
3.
Receive the package in your repository 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.
Continue the installation by issuing the following command:
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, you must uninstall it before installing a
new version.
Installing the Agents Using the Built-in Agent
Installer
To access the Agent Installer within QConvergeConsole GUI:
1.
Point to the gear icon
Installers.
, point to Help, and then click Download Agent
2.
Follow the window prompts.
For detailed installation instructions, refer to the QConvergeConsole GUI
, point to Help, and then click
help system. (Point to the gear icon
Browse Contents. In the QConvergeConsole Help window, click the
Search tab, and then search for “agent installer”).
11
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the QLNXRemote Agent
Installing the QLNXRemote Agent
To run the QLNXRemote Install Wizard for Windows x64 or Windows x86:
In Windows Explorer, double-click the following file:
QLNXRemote_xxx-<x.xx.xxxx>\setup.exe
NOTE
Complete the following for adapter management in a Windows Nano Server:
1.
Unzip and extract the QConvergeConsole GUI Management Agents
in the Windows QConvergeConsole GUI package.
2.
Copy the Nano-specific QConvergeConsole GUI Management Agent
individual files (after extracting them) into the Nano Server system.
3.
To install the agent, run the InstallOrUpgradeAgents.ps1
PowerShell script.
Installing QConvergeConsole GUI
Refer to the appropriate installation procedure for your operating system:

Installing QConvergeConsole GUI in a Windows Environment

Installing QConvergeConsole GUI in a Linux Environment

Installing QConvergeConsole GUI in a Solaris Environment

Installing QConvergeConsole GUI in a Console Window
NOTE
Read the note Before installing QConvergeConsole GUI on page 6.
12
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Windows Environment
Installing QConvergeConsole GUI in a Windows Environment
The QConvergeConsole Installer for Windows is a self-extracting utility that
installs QConvergeConsole GUI and related files. Follow the steps in this section
to install QConvergeConsole GUI on a Windows system.
NOTE
 For information on firewall configuration on Windows systems, refer to
“Windows Firewall Configuration” on page 38.
 The location of the installed QConvergeConsole files depends on which
QCC GUI version you run, and the operating system on which you install
it, as follows:
 QCC GUI x86 version on 64-bit Windows operating system:
All QCC files are installed in the folder Program Files (x86).
 QCC GUI x86 version on 32-bit Windows operating system:
All QCC files are installed in the folder Program Files.
 QCC GUI x64 version on 64-bit Windows operating system:
All QCC files are installed in the folder Program Files.
To install QConvergeConsole GUI in a Windows environment:
1.
In the folder 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.
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.
4.
Click Next.
5.
In the next dialog box, select the appropriate option:


Yes - For localhost-only installation.
No - For non-localhost-only installation.
NOTE
The localhost-only option installs QCC GUI 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.
13
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Linux Environment
6.
In the Pre-Installation Summary dialog box, verify that the information is
correct, and then click Install.
7.
(Optional) Complete the following in the Security Login Configuration:
a.
Type a value in the Login ID box.
b.
Type a value in the Password box.
c.
If applicable, select the Check this box to enable Security Login
check box.
NOTE
If you enable the Security Login option, the login ID and
password will be required to open QCC GUI. QCC GUI will also
automatically log out if it remains idle for more than a few
minutes.
d.
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:


9.
Click Next.
Yes - Click to enable the SSL feature.
No - Click to disable the SSL feature.
In the Install Complete dialog box, click Done to exit the installer.
NOTE
To start QConvergeConsole GUI, see “Starting QConvergeConsole GUI” on
page 30.
Installing QConvergeConsole GUI in a Linux Environment
NOTE
Read the note Before installing QConvergeConsole GUI on page 6.
You have the option of installing QConvergeConsole GUI in a Linux environment
using either a GUI or command line method.
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.
14
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Linux Environment
To install QConvergeConsole GUI in a Linux environment:
1.
Open the directory containing one of the following installer file:
QConvergeConsole_Installer_Linux_i386_<version>.bin
QConvergeConsole_Installer_Linux_IA64_<version>.bin
QConvergeConsole_Installer_Linux_x64_<version>.bin
QConvergeConsole_Installer_Linux_ppc64_<version>.bin
QConvergeConsole_Installer_Linux_ppc64_LE_<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.
4.
Click Run in Terminal.
The installer extracts the files and installs QConvergeConsole GUI in the
directory /opt/QLogic_Corporation/QConvergeConsole.
5.
In the installation Introduction dialog box, click Next.
6.
In the Tomcat Port Number Setup dialog box, type 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. Or,
if you do not want a localhost-only installation, select No.
NOTE
The localhost-only option installs QConvergeConsole GUI locally so
that you must run it locally (a 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.
In the Pre-Installation Summary dialog box, read the information, and then
click Install.
9.
(Optional) Complete the following in the Security Login Configuration:
a.
Type a value in the Login ID box.
b.
Type a value in the Password box.
c.
If applicable, select the Check this box to enable Security Login
check box.
d.
Click Next.
15
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Solaris Environment
10.
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:


Yes - Click to enable the SSL feature.
No - Click to disable the SSL feature.
11.
In the Tomcat SSL Port Number Setup dialog box, type a valid SSL port
number in the range 1025–65536, or accept the default port number, 8443.
Then click Next to continue.
12.
In the Install Complete dialog box, click Done to exit the installer.
NOTE
See “Starting QConvergeConsole GUI” on page 30 to start
QConvergeConsole GUI
Installing QConvergeConsole GUI in a Solaris Environment
NOTE
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
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.
To install QConvergeConsole GUI in a Solaris environment:
1.
Open the appropriate directory containing the installer file:


QConvergeConsole_Installer_Solaris_SPARC_<version>.bin
QConveregConsole_Installer_Solaris_x86_<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, issue the appropriate command on the
console:

For SPARC:
sh QConvergeConsole_Installer_Solaris_SPARC_<version>.bin
16
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Solaris Environment

For x86:
sh QConvergeConsole_Installer_Solaris_x86_<version>.bin
The InstallAnywhere GUI utility prepares to install QConvergeConsole GUI
and opens the installation Introduction dialog box.
4.
Click Next.
5.
In the Tomcat Port Number Setup dialog box, type 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 locally installs QConvergeConsole GUI 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.
8.
(Optional) Complete the following in the Security Login Configuration:
9.
a.
Type a value in the Login ID box.
b.
Type a value in the Password box.
c.
If applicable, select the Check this box to enable Security Login
check box.
d.
Click Next.
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:


10.
Yes - Click to enable the SSL feature.
No - Click to disable the SSL feature.
In the Tomcat SSL Port Number Setup dialog box, type a valid SSL port
number in the range 1025–65536, or accept the default port number, 8443.
Then click Next to continue.
17
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Console Window
11.
In the Install Complete dialog box, click Done to exit the installer.
NOTE
S
 See “Starting QConvergeConsole GUI” on page 30 to start
QConvergeConsole GUI
 Some 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.
Installing QConvergeConsole GUI in a Console Window
On Windows, Linux, and Solaris systems, you can use a console window to install
QConvergeConsole GUI. You can also use the silent option to install QCC GUI in
silent mode.
NOTE
Read the note Before installing QConvergeConsole GUI on page 6.
To run the installer from a console window:
Issue the following command:
<installer_file_name>
Optional parameters include the following:

-i console: Use this option to run the installer in a console window
for command line-driven installation (user interaction is required).

-i silent: Use this option to install in silent mode. This mode is
used when no user interaction is required.

-DLOCALHOST_ACCESS_ONLY=<value>: Use this option to enable
the localhost-only feature (disables QCC GUI from being run from
remote host). Allowed values are 1 (enable) or 0 (disable). Default
value is 0.

-DSSL_ENABLE=<value>: Use this option to enable the SSL feature.
Allowed values are 1 (enable) or 0 (disable). Default value is 1.

-DUSER_INPUT_PORT_NUMBER=<port>: Use this option to change
the Tomcat port number. The default Tomcat port number is 8080.
18
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Console Window

-DSECURITY_LOGIN=<1_OR_0>: Use this option to enable Security
Login feature. Default value is 0.

-DSECURITY_LOGIN_STR=<String>: Login setting for Security
Login feature. Default value is QCC.

-DSECURITY_PASSWORD_STR=<String>: Password setting for
Security Login feature. Default value is config.

-DUSER_INPUT_SSL_PORT_NUMBER: Use this option to change
Tomcat SSL Port Number.

-DLOG_LOCATION: Use this option to change Log directory. Default
value is installation folder.
NOTE
The -D options listed in the preceding are applicable to silent install only.
To run the installer in silent mode on Windows, Linux, and Solaris:
The following examples show how to run the silent command on Windows, Linux,
and Solaris:
Windows
QConvergeConsole_Installer_Windows_x64_x_x_x_xxx -i silent -DSSL_ENABLE=0
-DLOCALHOST_ACCESS_ONLY=1
-DUSER_INPUT_PORT_NUMBER=8998
-DSECURITY_LOGIN=1
-DSECURITY_LOGIN_STR=admin
-DSECURITY_PASSWORD_STR=password
-DLOG_LOCATION=”c:\tmp\newLogLocation”
-DUSER_INPUT_SSL_PORT_NUMBER=9999
Linux
QConvergeConsole_Installer_Linux_x64_x_x_x_xxx -i silent -DSSL_ENABLE=0
-DLOCALHOST_ACCESS_ONLY=1
-DUSER_INPUT_PORT_NUMBER=8998
-DSECURITY_LOGIN=1
-DSECURITY_LOGIN_STR=admin
-DSECURITY_PASSWORD_STR=password
-DUSER_INPUT_SSL_PORT_NUMBER=9999
19
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing QConvergeConsole GUI in a Console Window
Solaris
QConvergeConsole_Installer_Solaris_x86_x_x_x_xxx -i silent -DSSL_ENABLE=0
-DLOCALHOST_ACCESS_ONLY=1
-DUSER_INPUT_PORT_NUMBER=8998
-DSECURITY_LOGIN=1
-DSECURITY_LOGIN_STR=admin
-DSECURITY_PASSWORD_STR=password
-DUSER_INPUT_SSL_PORT_NUMBER=9999
NOTE
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
For detailed information on the silent mode command parameters, refer to the
readme_installer.txt file.
20
SN0051105-00 N
2–Installing QConvergeConsole GUI
Uninstalling QConvergeConsole GUI
Figure 2-1 shows an example of running the installer in a console window.
Figure 2-1. Example of Console Window Installation
Uninstalling QConvergeConsole GUI
Refer to the appropriate uninstallation procedure for your operating system:

Uninstalling QConvergeConsole GUI in a Windows Environment

Uninstalling QConvergeConsole GUI in a Linux Environment

Uninstalling QConvergeConsole GUI in a Solaris Environment

Uninstalling QConvergeConsole GUI in a Console Window
21
SN0051105-00 N
2–Installing QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Windows Environment
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.
In the Uninstall QConvergeConsole GUI dialog box, click Next to continue.
3.
In 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.
4.
When the Uninstall Complete dialog box informs you that the uninstallation
is complete, click Done.
QConvergeConsole GUI has been uninstalled.
22
SN0051105-00 N
2–Installing QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Linux Environment
Uninstalling QConvergeConsole Agents in Windows
Follow these steps in Windows to uninstall the QConvergeConsole agents.
NOTE
For Windows Nano server, use the UninstallAgents.ps1 Power Shell
script.
To uninstall the QConvergeConsole agents in Windows:
1.
Navigate to Uninstall A Program.
2.
Locate the agent to uninstall:

SANsurfer FastLinQ HBA Management Agent—for the FastLinQ
agent

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.
To remove the agent, click Uninstall.
4.
If required, repeat the preceding steps 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.
To start the uninstallation, open the Uninstall_QConvergeConsole
directory in a virtual network, and then double-click the
QConvergeConsoleUninstaller file.
3.
When the message box asks whether you want to run or view the contents
of the QConvergeConsoleUninstaller.bin file, click Run in
Terminal.
4.
In the Uninstall QConvergeConsole dialog box, click Next to continue.
23
SN0051105-00 N
2–Installing QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Solaris Environment
5.
In 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.
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
qlnxremote for 3400 and 45000 Adapters
Uninstalling QConvergeConsole GUI in a Solaris Environment
NOTE
The following adapters currently do not support Solaris:
 3400 Series Intelligent Ethernet Adapters
 8400 Series Converged Network Adapters
 FastLinQ 45000 Series Converged Network Adapters
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
24
SN0051105-00 N
2–Installing QConvergeConsole GUI
Uninstalling QConvergeConsole GUI in a Console Window
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® and x86
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
Uninstalling QConvergeConsole GUI in a Console Window
On Windows, Linux, and Solaris systems, you can use a console window to
uninstall QConvergeConsole GUI.
To run the uninstaller from a console window:

Issue the following command:
<uninstaller_file_name>
Where <uninstaller_file_name> is the name of the executable file
for the QCC GUI uninstaller.
25
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the QLRemote Agent on Windows Nano Server
Figure 2-2 shows an example of running the uninstaller in a console window.
Figure 2-2. Example of Console Window Uninstallation
Installing the QLRemote Agent on Windows Nano
Server
This section provides instructions for installing and uninstalling the QLRemote
Agent on a Windows Nano Server.
To install the QLRemote Agent on a Nano Server:
1.
From remote management server, create or add a PSSession to the
Windows Nano Server.
2.
Add a TrustedHost item by following the instructions located here:
http://winintro.ru/windowspowershell2corehelp.en/html/f23b65e2-c608-485d
-95f5-a8c20e00f1fc.htm
For example:
PS C:\Users\Administrator> Set-Item WSMan:\localhost\Client\TrustedHosts -Value 172.27.1.44
WinRM Security Configuration.
This command modifies the TrustedHosts list for the WinRM client. The computers in the
TrustedHosts list might not be authenticated. The client might send credential information to
these computers. Are you sure that you want to modify this list?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y
PS C:\Users\Administrator> Get-Item WSMan:\localhost\Client\TrustedHosts
WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client
Type
Name
SourceOfValue
Value
-----------------------
26
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the QLRemote Agent on Windows Nano Server
System.String
TrustedHosts
172.27.1.44
PS C:\Users\Administrator> $cs=New-PSSession -ComputerName 172.27.1.44 -Credential
Administrator
PS C:\Users\Administrator> Enter-PSSession $cs
[172.27.1.44]: PS C:\Users\Administrator\Documents>
3.
Copy the QLogic package (script) to the Nano Server.
a.
If necessary, disable the firewall on the Nano Server by issuing one of
the following commands:
netsh advfirewall set allprofile state off
Set-NetFirewallProfile -Profile Domain,Public,Private
-Enabled false
b.
4.
Using File Explorer, copy the script (\\172.27.1.44\c$).
To install the QLRemote agent:
a.
Run the script by issuing the following command:
.\ InstallOrUpgradeQLRemoteAgent.ps1
b.
Check for running service by issuing the following command.
Get-Service QLManagementaAgentJava
c.
Status
Name
DisplayName
------
----
-----------
Running
Agent
QLManagementAge... QLogic Management Suite Java
Start or restart services for the agent (QLManagementAgentJava). For
example:
Restart-Service QLManagementAgentJava
WARNING: Waiting for service 'QLogic Management Suite
Java Agent (QLManagementAgentJava)' to stop...
5.
In QConvergeConsole GUI, connect to a Nano virtual hard disk (VHD) by
adding a host and entering the IP address to the Nano Server.
To uninstall the QLRemote Agent on a Nano Server:

Issue the following command:
[172.27.1.44]: PS C:\nanoapp>.\UninstallQLRemoteAgent.ps1
Stopping QLManagementAgentJava
WARNING: Waiting for service 'QLogic Management Suite Java
Agent (QLManagementAgentJava)' to stop...
WARNING: Waiting for service 'QLogic Management Suite Java
Agent (QLManagementAgentJava)' to stop...
27
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the QLNXRemote Agent on Windows Nano Server
Uninstalling QLRemote...
Done
Stopping oncportmap
Uninstalling ONCPortMap...
Done
[172.27.1.44]: PS C:\nanoapp>
Installing the QLNXRemote Agent on Windows
Nano Server
This section provides instructions for installing and uninstalling the QLNXRemote
Agent on a Windows Nano Server.
To install the QLNXRemote Agent on a Nano Server:
1.
From remote management server, create or add a PSSession to the
Windows Nano Server.
2.
Add a TrustedHost item by following the instructions located here:
http://winintro.ru/windowspowershell2corehelp.en/html/f23b65e2-c608-485d
-95f5-a8c20e00f1fc.htm
For example:
PS C:\Users\Administrator> Set-Item WSMan:\localhost\Client\TrustedHosts -Value 172.27.1.44
WinRM Security Configuration.
This command modifies the TrustedHosts list for the WinRM client. The computers in the
TrustedHosts list might not be authenticated. The client might send credential information to
these computers. Are you sure that you want to modify this list?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y
PS C:\Users\Administrator> Get-Item WSMan:\localhost\Client\TrustedHosts
WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client
Type
Name
SourceOfValue
Value
----------------------System.String
TrustedHosts
172.27.1.44
PS C:\Users\Administrator> $cs=New-PSSession -ComputerName 172.27.1.44 -Credential
Administrator
PS C:\Users\Administrator> Enter-PSSession $cs
[172.27.1.44]: PS C:\Users\Administrator\Documents>
3.
Copy the QLogic package (script) to the Nano Server.
a.
If necessary, disable the firewall on the Nano Server by issuing one of
the following commands:
netsh advfirewall set allprofile state off
28
SN0051105-00 N
2–Installing QConvergeConsole GUI
Installing the QLNXRemote Agent on Windows Nano Server
Set-NetFirewallProfile -Profile Domain,Public,Private
-Enabled false
b.
4.
Using File Explorer, copy the script (\\172.27.1.44\c$).
To install the QLNXRemote agent:
a.
Run the script by issuing the following command:
.\InstallOrUpgradeAgents.ps1
b.
Check for running service by issuing the following command:
Get-Service QLogicManagementSuiteNXRemote
Status
Name
DisplayName
------
----
-----------
Running QLogicManagemen... QLogic Management Suite
FastLinQ
c.
Uninstall services for the agent (UninstallAgents.ps1). For example:
.\UnInstallAgents.ps1
WARNING: Waiting for service 'QLogic Management Suite
FastLinQ (QLogicManagementSuiteNXRemote)' to stop...
5.
In QConvergeConsole GUI, connect to a Nano virtual hard disk (VHD) by
adding a host and entering the IP address to the Nano Server.
To uninstall the QLNXRemote Agent on a Nano Server:

Issue the following command:
[172.27.1.22]: PS C:\> .\UnInstallAgents.ps1
WARNING: Waiting for service 'QLogic Management Suite FastLinQ
(QLogicManagementSuiteNXRemote)' to stop...
WARNING: Waiting for service 'QLogic Management Suite FastLinQ
(QLogicManagementSuiteNXRemote)' to stop...
WARNING: Waiting for service 'QLogic Management Suite FastLinQ
(QLogicManagementSuiteNXRemote)' to stop...
QLManagementAgentJava is currently running. Skipping uninstall
ONCPortMap service...
29
SN0051105-00 N
3
Getting Started
This chapter includes procedures for starting and exiting QConvergeConsole GUI,
and getting help:

Starting QConvergeConsole GUI

Enabling Forward Error Correction

Exiting QConvergeConsole GUI

Getting Help
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

Connecting to a Host Server
Opening the QConvergeConsole GUI Main Page
You can open QConvergeConsole GUI locally on the server or from a remote
computer. You can also open it 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.
30
SN0051105-00 N
3–Getting Started
Opening the QConvergeConsole GUI Main Page
Opening QCC GUI on the Local Server
To locally open QCC GUI:
1.
Open a Web browser window.
2.
In the address bar, type the following, and then press the ENTER key.
For a non-secure connection:
http://localhost:<port_number>/QConvergeConsole
Where <port_number> is the port number you specified during
QConvergeConsole installation. The default port number is 8080.
For a secure (SSL) connection:
https://localhost:<SSL_port_number>/QConvergeConsole
The main page of QConvergeConsole GUI opens. Figure 3-1 shows an
example.
Figure 3-1. QConvergeConsole GUI Main Page (Example)
Opening QCC GUI on a Remote Server
To open QCC GUI on a remote server:
1.
Open a Web browser.
2.
In the address bar, type the following, and then press ENTER.
For a non-secure connection:
http://<server_ip>:<port_number>/QConvergeConsole/
31
SN0051105-00 N
3–Getting Started
Connecting to a Host Server
Where <server_ip> is the IP address of the QCC GUI server, and
<port_number> is the access port number you specified during
QConvergeConsole GUI installation. The default port number is 8080.
For a secure (SSL) connection:
https://<server_ip>:<SSL_port_number>/QConvergeConsole
Where <server_ip> is the IP address of the QConvergeConsole GUI
server.
The main page of QConvergeConsole GUI opens, as shown in Figure 3-1
on page 31.
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, and the agent service must
be running.
1.
In the upper-left corner of the QConvergeConsole GUI window, locate the
hostname/address text box. Figure 3-2 shows an example.
Figure 3-2. Hostname or IP Address (Example)
2.
Type the host name or its IP address.
3.
To initiate the connection, click CONNECT.
If successful, the host and its adapters appear in the QCC GUI system tree
in the left pane.
NOTE
S
To choose the protocols that QConvergeConsole will display, select
the appropriate FC/FCoE, Ethernet, iSCSI, and FabricCache check
boxes. The default is all protocols. For more information, refer to the
help system.
32
SN0051105-00 N
3–Getting Started
Enabling Forward Error Correction
Enabling Forward Error Correction
To enable FEC from QConvergeConsole GUI:
1.
Download and install QConvergeConsole GUI.
NOTE
S
To download QConvergeConsole GUI, see “Downloading Updates” on
page xiv.
2.
Launch QConvergeConsole GUI.
3.
Connect to the appropriate host.
4.
Follow the steps in the Using FEC Enable/Disable Wizard topic in the
QConvergeConsole GUI Help.
NOTE
S
For FEC to work, the switch port that connects to QLogic HBA must
have the FEC option enabled.
To enable FEC from a Brocade switch:
Refer to the portcfgfec command in the Brocade Fibre Channel 16G switch.
For example: portcfgfec -help
Exiting QConvergeConsole GUI
To exit QConvergeConsole GUI, point to the gear icon
click Exit.
, point to File, and then
Getting Help
This section provides the following information:

Browsing Help Contents

Viewing QConvergeConsole GUI Version Details
33
SN0051105-00 N
3–Getting Started
Browsing Help Contents
Browsing Help Contents
Access the QConvergeConsole GUI help system to view detailed information
about using QCC GUI. For a high-level list of topics covered in the help system,
see “What Is in the Help System” on page xi.
To view the help system from the main page:
1.
Point to the gear icon
, point to Help, 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.
NOTE
While QCC GUI supports all the Web browsers listed in “Software
Requirements” on page 2, some of the help system's features, such as
the Search and Index tools, may not work properly in all browsers.
34
SN0051105-00 N
3–Getting Started
Viewing QConvergeConsole GUI Version Details
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.
Point to the gear icon
, point to Help, and then click About.
Figure 3-3 shows an example of the About QConvergeConsole box, which
shows the version numbers for QConvergeConsole, as well as copyright
information. (The About box that you view shows the actual product version
numbers and copyright year.)
Figure 3-3. About QConvergeConsole GUI (Example)
2.
To close the message box and return to the QConvergeConsole GUI main
window, click OK.
35
SN0051105-00 N
4
Security Considerations
This chapter provides security-related information for QConvergeConsole GUI:

Management Connectivity Model

Managing Security
Management Connectivity Model
Figure 4-1 shows how QConvergeConsole GUI communicates in typical
deployments.
QConvergeConsole GUI runs as an Apache Tomcat application server. After it is
launched on the application server, you connect to QCC GUI through a Web
browser.
QCC GUI
Application
QCC
Management
Agents
Console
Apache Tomcat
Web Server
Host server
QCC
Management
Agents
Host server
Figure 4-1. QCC GUI Management Connectivity
36
SN0051105-00 N
4–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 4-1, you can connect to QCC GUI using:


A localhost connection (on the Web application server)
A remote connection (from another computer)
For information on how to connect to QCC GUI from the local host server or from
a remote connection, see “Connecting to a Host Server” on page 32.
For information on how to install QConvergeConsole GUI for localhost
connections only, see:

Installing QConvergeConsole GUI in a Windows Environment

Installing QConvergeConsole GUI in a Linux Environment

Installing QConvergeConsole GUI in a Solaris Environment
Password Protection for Access Control
NOTE
S
Password protection does not apply to QLogic 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)
The default security login password is config.
Requirements
To set up password protection on a host, you must have administrator or root
privileges on that host.
37
SN0051105-00 N
4–Security Considerations
Program Numbers Used for QConvergeConsole and SANsurfer Agents
Procedure
For detailed information on password protection on a host server, refer to the
following topics in the QCC GUI help system:



Setting QConvergeConsole GUI Security
Viewing Host Security
Using Security Check
Program Numbers Used for QConvergeConsole and
SANsurfer Agents
Program numbers will be mapped to dynamic ports that can be seen by means of
the rpcinfo -p command. The program numbers used for QConvergeConsole
and SANsurfer agents are:





Program 4397 for qlremote
Program 4398 for SANsurfer FC HBA manager
Program 351502 for iqlremote
Program 351503 for SANsurfer iSCSI HBA manager
Program 252525 for QLNXRemote (E3/E4 management agent)
For example:
[root@rp-R800-RHEL65x64 ~]# rpcinfo -p 172.27.3.21
program vers proto
port
351504
1
tcp
871
351504
1
udp
869
4397
1
tcp
739
4397
1
udp
737
351502
1
tcp
959
351502
1
udp
957
351523
1
tcp
679
351523
1
udp
677
service
[root@rp-R800-RHEL65x64 ~]#
Windows Firewall Configuration
When Windows Firewall is enabled with default settings, connections between
QCC GUI and remote hosts are blocked. To use Windows Firewall but allow
connections between 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 and agents:
C:\Program Files\QLogic Corporation\QConvergeConsole\
tomcat-x64\apache-tomcat-x.x.xx\bin\tomcatx.exe
C:\Program Files\QLogic Corporation\portmap\portmap.exe
C:\Program Files\QLogic Corporation\nQAgent\ethernet.exe
38
SN0051105-00 N
4–Security Considerations
Windows Firewall Configuration
C:\Program
C:\Program
C:\Program
C:\Program

Files\QLogic
Files\QLogic
Files\QLogic
Files\QLogic
Corporation\QLRemote\qlremote.exe
Corporation\iQLRemote\iqlremote.exe
Corporation\QLFca\qlremote_fca.exe
Corporation\QLNXRemote\qlnxremote.exe
For x64 running x86 GUI and agents:
C:\Program Files (x86)\QLogic Corporation\QConvergeConsole\
tomcat-x64\apache-tomcat-x.x.xx\bin\tomcatx.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
C:\Program Files (x86) \QLogic Corporation\QLNXRemote\qlnxremote.exe

For x86 running native x86 GUI and agents:
C:\Program Files (x86)\QLogic Corporation\QConvergeConsole\
tomcat-x86\apache-tomcat-x.x.xx\bin\tomcatx.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
C:\Program Files (x86) \QLogic Corporation\QLNXRemote\qlnxremote.exe
Next, configure the Windows Firewall as described in the following section.
Firewall Configuration in Windows Server 2008, 2012, and 2016
To configure the firewall on a host or client using Server Manager:
1.
Follow the appropriate instructions for your operating system:


Windows Server 2008:
a.
Click Start, click Administrative Tools, and then 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.
Windows Server 2012: Do one of the following:

Click Start, click Administrative Tools, and then click Windows
Firewall with Advanced Security.

Run the Server Manager application, click Tools, and then click
Windows Firewall with Advanced Security.
39
SN0051105-00 N
4–Security Considerations
Windows Firewall Configuration
2.
Refer to the list of programs in “Windows Firewall Configuration” on page 38.
For the first program in the list:
a.
Right-click Inbound Rules, and then click New Rule.
b.
In the New Inbound Rule wizard, select Program, and then click Next.
c.
Click Browse to specify the path to the .exe file, and then click Next.
d.
Select Allow the connection, and then click Next.
e.
Follow the instructions for your operating system:
f.

Windows Server 2008: Select Domain and then click Next.

Windows Server 2012: Select Domain and Public. Then click
Next.
Enter a name and description for the rule, and then click Finish.
Server Manager displays the new rule under Inbound Rules.
3.
RepeatStep 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 4-2 shows how the default Windows firewall settings prevent the QCC GUI
from connecting to remote hosts, and Figure 4-3 shows how modifying the
settings lets the QCC GUIconnect to remote hosts.
Figure 4-2. Default Windows Firewall Settings—QCC Blocked from Remote Hosts
Figure 4-3. Modified Firewall Settings—QCC Able to Connect to Remote Hosts
40
SN0051105-00 N
4–Security Considerations
Linux Firewall Configuration
Linux Firewall Configuration
If the Linux firewall (iptable rules) is enabled with default settings, connections
between the QCC GUI and remote hosts are not allowed. To use Linux firewall but
allow connections between the QCC GUI and remote hosts, set up the rules for
your Linux distribution as described in the following sections.
Red Hat Enterprise Linux (RHEL) 7.x and SLES 12.x
To configure the firewall on RHEL 7:
1.
Determine the Fedora® FirewallD status (enabled or disabled):
# systemctl status firewalld
2.
If FirewallD is enabled:
a.
Identify the current active zone and related interface:
# firewall-cmd --get-active-zones
public interfaces: em1
b.
Set a permanent port range of 1–1024 for TCP and UDP protocols (to
allow management agents qlremote, netqlremote, iqlremote, and
qlremote_fca to communicate with the outside world):
# firewall-cmd --permanent --zone=public --add-port=1-1024/tcp
# firewall-cmd --permanent --zone=public --add-port=1-1024/udp
c.
Allow QCC GUI servers to connect to client machines:

Identify the current active zone and related interface (displayed
by the command in Step a for the server machine.

Set options permanently to allow port 8080 for http and 8443 for
https:
# firewall-cmd --permanent --zone=public --add-port=8080/tcp
# firewall-cmd --permanent --zone=public --add-port=8080/udp
# firewall-cmd --permanent --zone=public --add-port=8443/tcp
# firewall-cmd --permanent --zone=public --add-port=8443/udp
NOTE
The preceding commands reflect the default port numbers of
8080 for http and 8443 for https. If different port numbers were
specified during QCC GUI installation, replace the port numbers
in the preceding commands with the port numbers specified
during installation.
41
SN0051105-00 N
4–Security Considerations
Linux Firewall Configuration
3.
Reload the firewall settings to make the current permanent settings the new
runtime settings. Issue the following command:
# firewall-cmd --reload
NOTE
Make sure the rpcbind service is running by entering the following in
the command line:
# service rpcbind start
# systemctl enable rpcbind.service
Red Hat Enterprise Linux (RHEL) 5.x and 6.x
To configure the firewall on RHEL 5 and 6:
1.
To check the firewall status (by default, the command shows chain and rules
set for the host), issue the following command:
# service iptables status
2.
If iptables service is set or started:
a.
Set a port range of 1–1024 for the TCP and UDP protocols (allow
management agents qlremote, netqlremote, iqlremote, and
qlremote_fca to communicate with the outside world):
# iptables -I INPUT 4 -p tcp -m state --state NEW -m tcp --dport 1:1024 -j ACCEPT
# iptables -I INPUT 5 -p udp -m state --state NEW -m udp --dport 1:1024 -j ACCEPT
b.
To set the options permanently to allow port 8080 for http and 8443 for
https (allow QCC GUI servers to connect to clients), issue the following
commands:
# iptables -I INPUT 6 -p tcp -m state --state NEW -m udp --dport 8080 -j ACCEPT
# iptables -I INPUT 7 -p udp -m state --state NEW -m udp --dport 8080 -j ACCEPT
# iptables -I INPUT 8 -p tcp -m state --state NEW -m udp --dport 8443 -j ACCEPT
# iptables -I INPUT 9 -p udp -m state --state NEW -m udp --dport 8443 -j ACCEPT
NOTE
The preceding commands reflect the default port numbers of
8080 for http and 8443 for https. If different port numbers were
specified during QCC GUI installation, replace the port numbers
in the preceding commands with the port numbers specified
during installation.
42
SN0051105-00 N
4–Security Considerations
Linux Firewall Configuration
3.
To make the current settings the new runtime settings, issue the following
command to save the firewall settings:
# service iptables save
SUSE 11.x, 10.x, and 12.x
To configure the firewall on SUSE 10, 11, and 12:
1.
Check the firewall status (by default, the command shows chain and rules
set for the host) by issuing the following command:
# iptables -L
2.
To add customized rules in iptables, provide the path for customized rules in
/etc/sysconfig/SuSEfirewall2:
FW_CUSTOMRULES="/etc/sysconfig/scripts/SuSEfirewall2-custom"
#FW_CUSTOMRULES=""
3.
Allow the management agents qlremote, netqlremote, iqlremote, and
qlremote_fca to communicate with the outside world. In
/etc/sysconfig/scripts/SuSEfirewall2-custom in the
fw_custom_before_port_handling( ) function, add the following
rules:
# iptables -I INPUT 4 -p tcp -m state --state NEW -m tcp --dport 1:1024 -j ACCEPT
# iptables -I INPUT 5 -p udp -m state --state NEW -m udp --dport 1:1024 -j ACCEPT
4.
Set port 8080 for http and 8443 for https to allow QCC GUI servers to
connect to clients. In
/etc/sysconfig/scripts/SuSEfirewall2-custom in the
fw_custom_before_port_handling( ) function, add the following
rules:
# iptables -I INPUT 6 -p tcp -m state --state NEW -m udp --dport 8080 -j ACCEPT
# iptables -I INPUT 7 -p udp -m state --state NEW -m udp --dport 8080 -j ACCEPT
# iptables -I INPUT 8 -p tcp -m state --state NEW -m udp --dport 8443 -j ACCEPT
# iptables -I INPUT 9 -p udp -m state --state NEW -m udp --dport 8443 -j ACCEPT
NOTE
 The preceding commands reflect the default port numbers of 8080
for http and 8443 for https. If different port numbers were specified
during QCC GUI installation, replace the port numbers in the
preceding commands with the port numbers specified during
installation.
 Providing the FW_CUSTOMRULES file path causes custom rules to
persist across reboots.
43
SN0051105-00 N
4–Security Considerations
Web Server (Apache Tomcat) Security
5.
To reload customized rules at runtime, issue the following command:
# /etc/init.d/SuSEfirewall2_setup reload
Web Server (Apache Tomcat) Security
This section describes security considerations for the Web application server
where Apache Tomcat is run.
Secure Sockets Layer (SSL)
QCC GUI 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 GUI
(refer to “Installing QConvergeConsole GUI in a Windows Environment” on
page 13 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 GUI using SSL, see “Opening the
QConvergeConsole GUI Main Page” on page 30.
44
SN0051105-00 N
5
Troubleshooting
This chapter lists known issues and describes procedures that may be helpful for
troubleshooting, including:

Recommendations for Solaris Hot Swap, Dynamic Reconfiguration,
Suspend and Resume Operations

Setting a Tomcat Log File
Follow the instructions in this section to set up a log file for troubleshooting.

Installing QLogic QConvergeConsole Beside SSMC and vPower NFS
Service
Recommendations for Solaris Hot Swap,
Dynamic Reconfiguration, Suspend and Resume
Operations
The QConvergeConsole GUI application must be stopped before performing any
hot swap, dynamic reconfiguration, suspend and resume operations in a Solaris
operating system. Use the following procedures as needed.
Stopping the QCC GUI Agents
To stop the QCC GUI, issue the following in the command line:
# ./etc/rc3.d/S99qlremote stop
# ./etc/rc3.d/S99netqlremote stop
NOTE
All QCC-GUI applications will restart after the system is rebooted.
Starting the QCC Agents Without Rebooting the Server
To start the QConvergeConsole application without rebooting the server, issue the
following in the command line:
# ./etc/rc3.d/S99qlremote start
# ./etc/rc3.d/S99netqlremote start
45
SN0051105-00 N
5–Troubleshooting
Removing QCC GUI Agents for an Ongoing Hot Swap, Dynamic Reconfiguration, Suspend or Resume
Removing QCC GUI Agents for an Ongoing Hot Swap,
Dynamic Reconfiguration, Suspend or Resume Operation
To remove the QConvergeConsole GUI application for an ongoing hot swap,
suspend, dynamic reconfiguration, or resume operation, issue the following In the
command line:
#pkgrm QLRemote
#pkgrm NQLRemote
NOTE
QLogic highly recommends that you remove the QCC GUI agents during an
ongoing hot swap, dynamic reconfiguration, suspend, and resume
operation.
Setting a Tomcat Log File
This section explains how to configure Tomcat to direct debug message output
from QConvergeConsole GUI to a specific file location. Refer to the appropriate
procedure for your OS:

Procedure on Windows-based Systems

Procedure on Linux-based Systems

Procedure on Solaris-based Systems
Procedure on Windows-based Systems
To set a Tomcat log file in Windows:
1.
On the Tomcat Program Files menu, click Configure Tomcat, as shown in
Figure 5-1.
Figure 5-1. Tomcat Program Files Menu
46
SN0051105-00 N
5–Troubleshooting
Procedure on Windows-based Systems
The Apache Tomcat Properties open, as shown in Figure 5-2.
Figure 5-2. Apache Tomcat Properties
2.
If the Tomcat server is running, the Stop button is enabled. Click Stop to
stop the server.
The Apache Commons Daemon Service Manager dialog box shows the
service status. Figure 5-3 shows an example.
Figure 5-3. Stopping Server Progress
3.
On the Apache Tomcat Properties, click the Logging tab.
47
SN0051105-00 N
5–Troubleshooting
Procedure on Windows-based Systems
4.
Modify the Logging page as follows:
a.
To the right of Redirect Stdout, click the browse button, and then
select the file location for standard output from QCC GUI.
b.
To the right of Redirect Stderror, click the browse button, and then
select the file location for standard error output from QCC GUI.
In Figure 5-4, "C:\Temp\stdout from QCC.txt" and
"C:\Temp\stderr from QCC.txt" are used as examples.
Figure 5-4. Changing Locations of Output Files
c.
Click Apply to make the changes.
48
SN0051105-00 N
5–Troubleshooting
Procedure on Linux-based Systems
5.
Restart the Tomcat service as follows:
a.
Click the General tab.
b.
On the General page (Figure 5-5), click Apply, and then click Start.
Figure 5-5. General Page of Apache Tomcat Properties
6.
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
7.
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.
To update the log file name in Linux:
1.
Stop the Tomcat server by entering the following command on a command
line:
". /catalina.sh stop"
2.
Open catalina.sh file for editing. The full path to catalina.sh on
Linux systems is:
49
SN0051105-00 N
5–Troubleshooting
Procedure on Solaris-based Systems
/opt/QLogic_Corporation/QConvergeConsole/apache-tomcat-6.0.35
/bin
3.
Locate 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 entering the following command 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. The
script contains three references to the log file.
To update the log file name in Solaris:
1.
Stop the Tomcat server by issuing the following command on a command
line:
". /catalina.sh stop"
2.
Open catalina.sh file for editing. The full path to catalina.sh on
Solaris systems is:
/opt/QLogic_Corporation/QConvergeConsole/apache-tomcat-6.0.35
/bin
3.
Locate 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, locate the following line:
>> "$CATALINA_BASE"/logs/catalina.out 2>&1 &
Make a similar change to this line as was done in Step 4:
>> "$CATALINA_BASE"/logs/QCC.out 2>&1 &
50
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
6.
About 12 lines farther down, locate 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 issuing the following command on the
command line:
". /catalina.sh start"
Installing QLogic QConvergeConsole Beside
SSMC and vPower NFS Service
To install QLogic QConvergeConsole SSMC and vPower NFS service:
1.
Download and extract the QCC installer.
2.
To ensure that TCP port 8080,8443, and 111 are not in use (Figure 5-6),
issue the following command:
netstat -ano | find "0.0.0.0:<port number>"
Figure 5-6. TCP Ports 8080, 8443, and 111 Usage
3.
4.
Complete the appropriate procedure that apply:

If any ports listed in Step 2 are in use, continue with Step 4.

If no ports listed in Step 2 are in use, skip to Step 6.
Complete the following to temporarily stop SSMC and VBR vPower NFS
service:
a.
Open Task Manager or Process Explorer.
b.
Select and right-click the ssmc service, and then select Properties.
51
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
c.
In the HPDE 3PAR StoreServ Management Console Server
Properties, General page, under Service status, click Stop, as shown
in Figure 5-7.
Figure 5-7. HPE 3PAR StoreServ Management Console Server Properties Window
d.
Select and right-click the VeeamNFSSvc service, and then click
Properties.
52
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
e.
In the Veeam vPower NFS Service Properties, General page, under
Service status, click Stop, as shown in Figure 5-8.
Figure 5-8. Veeam vPower NFS Service Properties
5.
Repeat Step 2.
6.
Launch the QCC installer as an Administrator.
7.
Click Next until you reach the Please enter desired port number window.
8.
Click Install.
9.
Click Yes to restrict access to localhost only (if applicable).
10.
In the Security Login Configuration window (Figure 5-9), complete the
following:
a.
Type a value in the Login ID box.
b.
Type a value in the Password box.
53
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
c.
Select the Check this box to enable Security Login check box (if
applicable).
d.
Click Next.
Figure 5-9. Security Login Configuration Window
11.
Click Yes to enable SSL feature (if applicable).
54
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
12.
Take note of the URL provided as shown in Figure 5-10, and then click
Done.
Figure 5-10. QConvergeConsole Installer
13.
Start installing the necessary management agents.
NOTE
When you start the installation, the installer will install the
ONCPortmap service.
14.
To check if TCP ports 8080, 8443, and 111 are in use (after all the
management agents have been installed), issue the following command:
netstat -ano | find "0.0.0.0:<port number>"
NOTE
All three ports should now be in use as shown in Figure 5-11.
55
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
Figure 5-11. TCP Ports 8080,8443, and 111 in Use
15.
Set the following services to manually start:






ONC/RPC Portmapper
QLManagementAgentJava
QLogic Management Suite FastLinQ
QLogic Management Suite Java iQAgent
QLogicManagementSuitenQLRemote
Tomcat7
16.
Open a Web browser and go to the URL provided in Step 12.
17.
In the Host Selection box, type localhost, and then click Connect.
18.
Select one of the ports in the QConvergeConsole system tree.
56
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
19.
Click the MBA Boot Cfg tab, and then complete the following on the MBA
Boot Cfg page (Figure 5-12):
a.
For the Hide Setup Prompt option, select Enabled.
b.
Click Apply.
Figure 5-12. MBA Boot Cfg Page
20.
Complete the password information as follows:
a.
Type the appropriate password in the Password box.
NOTE
If the password is not yet set up, the default password is config.
b.
Select the Save password for current session check box (if
applicable).
57
SN0051105-00 N
5–Troubleshooting
Installing QLogic QConvergeConsole Beside SSMC and vPower NFS Service
c.
Click OK.
NOTE
If you provide the correct password, the message, “Boot config
updated successfully, Reboot required” as shown in Figure 5-13.
Figure 5-13. Boot Config Updated Successfully Message
21.
Reboot the system.
22.
Start the SSMC and VBR Services after reboot.
58
SN0051105-00 N
Glossary
adapter
The board that interfaces between the
host system and the target devices.
Adapter is synonymous with host bus
adapter (HBA), host adapter, and adapter
board.
driver
The software that interfaces between the
file system and a physical data storage
device or network media.
Enhanced Ethernet
Also called Data Center Ethernet or
Converged Enhanced Ethernet. Refers to
new enhancements to the existing
Ethernet standard that eliminate Ethernet’s
inherently lossy nature and make 10Gb
Ethernet a viable storage networking
transport.
adapter port
A port on the adapter board.
CLI
Command line interface. A program interface driven by entering commands and
parameters.
Ethernet
The most widely used LAN technology that
transmits information between computer,
typically at speeds of 10 and 100 million
bits per second (Mbps).
Converged Network Adapter
QLogic Converged Network Adapters.
support both data networking (TCP/IP)
and storage networking (Fibre Channel)
traffic on a single I/O adapter using two
new technologies: Enhanced Ethernet and
Fibre Channel over Ethernet (FCoE).
FC
See Fibre Channel.
command line interface
See CLI.
FCoE
Fibre Channel over Ethernet. A new
technology defined by the T11 standards
body that allows traditional Fibre Channel
storage networking traffic to travel over an
Ethernet link by encapsulating Fibre
Channel frames inside Layer 2 Ethernet
frames. For more information, visit
www.fcoe.com.
device
A target, typically a disk drive. Hardware
such as a disk drive, tape drive, printer, or
keyboard that is installed in or connected
to a system. In Fibre Channel, a target
device.
59
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
Fibre Channel
A high-speed serial interface technology
that supports other higher layer protocols
such as SCSI and IP.
Because a path is a combination of an
adapter and a target port, it is distinct from
another path if it is accessed through a
different adapter or it is accessing a
different target port. Consequently, when
switching from one path to another, the
driver might be selecting a different
adapter (initiator), a different target port, or
both.
This is important to the driver when
selecting the proper method of failover
notification. It can make a difference to the
target device, which might have to take
different actions when receiving retries of
the request from another initiator or on a
different port.
Fibre Channel over Ethernet
See FCoE.
Internet Protocol
See IP.
Internet small computer system interface
See iSCSI.
IP
Internet Protocol. A method by which data
are sent from one computer to another
over the Internet. IP specifies the format of
packets, also called datagrams, and the
addressing scheme.
port
Access points in a device where a link
attaches. The four major port types are:
 N_Port—a Fibre Channel port that
supports point-to-point topology.
 NL_Port—a Fibre Channel port that
supports loop topology.
 F_Port—a port in a fabric where an
N_Port can attach.
 FL_Port—a port in a fabric where an
NL_Port can attach.
iSCSI
Internet small computer system interface.
Protocol that encapsulates data into IP
packets to send over Ethernet connections.
management workstation
PC workstation used to manage routers
remotely by connecting to the routers
using the QConvergeConsole GUI or CLI
commands.
port instance
The number of the port in the system.
Each adapter may have one or multiple
ports, identified with regard to the adapter
as port 0, port 1 and so forth. To avoid
confusion when dealing with a system
containing numerous ports, each port is
assigned a port instance number when the
system boots up. So Port 0 on an adapter
might have a port instance number of 8, for
example, if it is the eighth port discovered
by the system.
path
A path to a device is a combination of a
adapter port instance and a target port as
distinct from internal paths in the fabric
network. A fabric network appears to the
operating system as an opaque network
between the adapter (initiator) and the
target.
60
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
RAID
Redundant array of independent/inexpensive disks. RAID are fault-tolerant disks
that look like either single or multiple
volumes to the server.
storage area network
See SAN.
target
The storage-device endpoint of a SCSI
session. Initiators request data from
targets. Targets are typically disk-drives,
tape-drives, or other media devices.
Typically a SCSI peripheral device is the
target but an adapter may, in some cases,
be a target. A target can contain many
LUNs.
A target is a device that responds to a
requested by an initiator (the host system).
Peripherals are targets, but for some
commands (for example, a SCSI COPY
command), the peripheral may act as an
initiator.
RAM
Random-access memory. The most
common computer memory that can be
used by programs to perform necessary
tasks while the computer is on; an
integrated circuit memory chip. RAM
allows information to be stored or
accessed in any order (randomly), and all
storage locations are equally accessible.
random-access memory
See RAM.
redundant array of
independent/inexpensive disks
See RAID.
TCP
Transmission control protocol. A set of
rules to send data in packets over the
Internet protocol.
SAN
Storage area network. Multiple storage
units (disk drives) and servers connected
by networking topology.
transmission control protocol
See TCP.
SCSI
Small computer system interface. A
high-speed interface used to connect
devices, such as hard drives, CD drives,
printers, and scanners, to a computer. The
SCSI can connect many devices using a
single controller. Each device is accessed
by an individual identification number on
the SCSI controller bus.
secure sockets layer
See SSL.
SSL
Secure sockets layer. A cryptographic
protocol that provides communications
security over the Internet.
61
SN0051105-00 N
Index
A
C
About box 35
adapters
definition of 59
port, definition of 59
supported series 4
agent (server), requirements 4
agent installer, built-in 11
agents
downloading 7, 8, 11
Ethernet 7
FabricCache 7
FCoE 7
Fibre Channel 7
installing 7, 8, 9, 10, 11
iSCSI 7
QLRemote agent, installing 26, 28
agreements, license xiii
Apache Tomcat
requirements 2
server, system requirements 3
setting up log file for 37, 46
audience, intended ix
CLI
definition of 59
tool x
client browser requirements 3
closing QCC GUI 33
CNA, See Converged Network Adapter
command line interface, See CLI
connecting to host server 32
console window
installing QCC 18
silent mode 18
uninstalling QCC 25
contents, help system 34
conventions, documentation xii
Converged Network Adapter, definition of 59
D
definitions of terms 59
devices
definition of 59
requirements 2
disk space requirements 1
documentation
conventions xii
related ix
downloading agents 7, 11
downloading QConvergeConsole GUI 7
drivers
definition of 59
required 2
software requirements 2
B
Boolean help system search 34
browsers
requirements, client 3
supported 2
browsing help content 34
62
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
E
installing QCC
in console window 18
on Linux 14
on Solaris 16
on Windows 13
steps to perform before 6
instance (port), definition of 60
intended audience ix
Internet Protocol, See IP
Internet small computer system interface, See
iSCSI
Introduction dialog box (installation) 15, 17
IP, definition of 60
iSCSI, definition of 60
Ethernet
definition of 59
ports, managing xii
EULA, software xiii
exiting QCC GUI 33
F
FCoE, definition of 59
FEC 33
Fibre Channel over Ethernet, See FCoE
firewall configuration
Linux 41
Windows 38
L
L2 cache 59
license agreements xiii
Linux
firewall configuration 41
installing agents on 7
installing QCC on 14
uninstalling agents on 24
uninstalling QCC on 23
local server, opening QCC GUI on 31
G
getting help 33, 34
getting started 30
glossary of terms 59
graphics adapter, requirements 1
H
hardware requirements 1
help system
contents of xi
viewing 34
host server, connecting to 32
M
main page, opening 30
management agent, See agents
management agents, installing 26, 28
management connectivity 36
management workstation, definition of 60
materials, related ix
memory requirement 2
I
index, help system 34
installing
QLRemote Agent, Nano Server 26, 28
installing agents
FabricCache 7, 11
on Linux 7
on Solaris 8, 9, 10
on Windows 7
O
opening QCC GUI
on remote server 31
on the local server 31
operating system requirements 3
63
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
P
S
path, definition of 60
port
definition of 60
instance, definition of 60
port number, Tomcat 13, 15, 16, 17
preface ix
product information, viewing 35
SAN
adapters, managing ix
definition of 61
hardware requirements 2
SCSI, definition of 61
search, help system 34
secure sockets layer, See SSL
security
firewall configuration, Linux 41
firewall configuration, Windows 38
local vs remote connectivity 37
password protecting access 37
SSL 44
server (host), connecting to 32
server agent requirements 4
server requirements 2
Apache Tomcat 3
silent mode, console window installation 18
small computer system interface (SCSI),
definition of 61
small computer system interface, See SCSI
software EULA xiii
software requirements 2
Solaris
installing agents on 8
installing QCC on 16
uninstalling agents on 25
uninstalling QCC on 24
SSL
definition of 61
enabling during installation 14, 16, 17, 30
opening QCC GUI using 31, 32
requirement 2
starting QCC GUI 30
storage area network, See SAN
SuperInstaller
installing agents 7
support, technical xiv
supported adapters 4
system requirements 1
Q
QLogic adapters, supported 4
QLRemoteAgent, installing for Nano Server
26, 28
R
RAID
definition of 61
SAN subsystems 2
RAM
definition of 61
requirement 2
random-access memory, See RAM
redundant array of independent/inexpensive
disks, See RAID
related materials ix
remote host, connecting to 32
remote server, opening QCC GUI on 31
requirements
Apache Tomcat 2
Apache Tomcat server 3
client browser 3
hardware 1
managing adapters on a host
operating system 3
server agent 4
software 2
system 1
64
SN0051105-00 N
Installation Guide—QConvergeConsole GUI
2400, 2500, 2600, 2700, 3200, 3400, 4000, 8100, 8200, 8300, 8400, 45000, and 10000 Series
T
V
target, definition of 61
TCP, definition of 61
technical support xiv
terms and definitions 59
Tomcat Port Number Setup dialog box 13,
15, 16, 17
transmission control protocol, See TCP
version (product), viewing 35
video card, requirements 1
W
Web browsers, supported 2
what’s in this guide x
Windows
firewall configuration 38
installing agents on 7
installing QCC on 13
Nano Server QLRemote agent, installing
26, 28
uninstalling agents on 23
uninstalling QCC on 22
workstation (management), definition of 60
U
Uninstall Complete dialog box 22, 24
Uninstall Options dialog box 22, 24
Uninstall QConvergeConsole dialog box 22,
23, 24
uninstalling agents
on Linux 24
on Solaris 25
on Windows 23
uninstalling QCC
on Linux 23
on Solaris 24
on Windows 22
using console window 25
65
SN0051105-00 N
Corporate Headquarters
Cavium, Inc.
2315 N. First Street
San Jose, CA 95131
408-943-7100
International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan | Israel
© 2014–2017 QLogic Corporation. QLogic Corporation is a wholly owned subsidiary of Cavium, Inc. All rights reserved worldwide. FabricCache, FastLinQ, 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. CentOS, Red Hat, Enterprise Linux, and Fedora 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. Ubuntu is a registered trademark
of Canonical Ltd. 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.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising