Users Guide

Table Of Contents

1–Introduction

QCS CLI Structure

Doc No. TD-000971 Rev. 1

QCS CLI Structure

Information about the structure of QLogic Control Suite CLI includes the following:

 QCS CLI Modes

 QCS CLI Elements (Targets)

 QCS CLI Hierarchy

 Command Categories

 Client Layout Design

QCS CLI Modes

The QLogic Control Suite CLI application uses the console and can be run in

either of two modes: interactive or noninteractive.

 In the interactive mode, users make connections to local and remote hosts,

and manage them by entering commands in the QCS CLI window. The

output is displayed as either information or an error message. The

interactive mode is not menu based. You must enter a correct command to

list specific types of targets before you can manage those targets.

 In the noninteractive mode (also called CLI mode), QCS CLI can take a

command as an input argument and run the command to produce the

appropriate effect and output, and then return a meaningful exit code. This

mode is ideal for scripting CLI commands.

QCS CLI Elements (Targets)

Each manageable element is known as a target. (Target, in this context, does not

refer to the FCoE or iSCSI target, which is usually referred to as a storage system

or LUN.) When you issue a command to list a specific target or manageable

element, all the targets matching the criteria defined in the query are listed and the

first element is selected by default. When you issue a command to list a specific

type of target, the focus shifts from the target that you selected before the query

was run to the first target in the current output.

Example 1:

Suppose the currently selected target is a host. If you issue the command to list

FCoE devices, all matching FCoE devices are listed and the first FCoE device in

the list is automatically selected for management, as shown in Figure 1-3. If you

instead want to manage the NDIS device that was originally selected, you must

first list all of the NDIS devices, and then select the appropriate instance to

manage it, as shown in Figure 1-4.