QL 4222
Chapter 4 - QL Management

Management Architecture

Cubix provides a multi-tiered approach to QL management:

QLVision

QLVision makes monitoring and control of the QL Series processors available to the system administrator or authorized user. The functions provided by QLVision include:

• Configuring Cubix Processor Recovery (CPR)
• Configuring Pending Offline (POL)
• Monitoring QL Status
• Resetting QL nodes
• Placing QL nodes online/offline
• Remotely Controlling a QL Node
• Monitoring Diagnostics
• Historical Log Reporting

To manage QL processors, QLVision requires that a QLVision Supervisor software application be loaded with the QL server driver on the device containing the QL processors. The QLVision Supervisor resides in the QL3_SUPR.NLM (for QL 3000 Series products) or QL4_SUPR.NLM (for QL 4000 Series products). This NLM should be loaded after the QL3000.LAN or QL4000.LAN server driver as part of the installation process.

The QLVision Supervisor provides QLVision with management information about the QL nodes installed on a single QL network. Refer to the QL Network Address section in Chapter 2 - Installation for an explanation of QL networks. One QLVision Supervisor is associated with each QL network.

Security

To restrict unauthorized users from accessing the QLVision functions, the system administrator is required to create a bindery object on each designated server to be managed by QLVision (for an explanation of the designated server, refer to Chapter 2 - Installation). This bindery object must be created using the Novell SYSCON utility. The directory services NETADMIN utility should not be used.

The bindery object must be created with the name QLVISION. It must be a group, and should contain the name(s) of all users authorized to manage the QL processors associated with this designated server. Only single users should be specified as members of the QLVISION group; the inclusion of other groups is not supported.

SNMP security is based on standard SNMP Communities. Refer to the SNMP section later in this chapter.

Requirements

• QLVision must be run on a NetWare workstation with a minimum of 640K RAM. QLVision should not be run on a non-dedicated server or router.
• The NetWare version must be 3.11 or higher.
• The QLRCV.COM TSR version 3.1 or higher must be installed on each QL node monitored by QLVision. QLRCV is placed in the SYS:CUBIX/QLx000/UTILITY directory of the designated server during installation (a copy is also placed in SYS:CUBIX/QLx000/LOGIN)..
• The QL nodes must be installed with QL drivers version 5.0 or higher.
• If the QL node is running OS/2, the NetWare Workstation for OS/2 v2.01 or higher must be installed on each QL node monitored by QLVision.
• The QLVision Supervisor NLM (QL3_SUPR.NLM or QL4_SUPR.NLM) must be loaded on the device containing the QL boards. Note that this requires Novell's SNMP.NLM (dated 4/6/93 or later) be installed on this device also.
• A QLVISION bindery object must exist on the designated server and must contain the name of the user running QLVision.
• Bindery emulation must be enabled on any designated server installed with NetWare 4.x.

Operation

QLVision consists of the following three files placed in the SYS:CUBIX/QLx000/UTILITY directory of the designated server during installation:

• QLVISION.EXE
• QLVISION.HLP
• QLVISION.CWA

To invoke QLVision, log onto the designated server(s) associated with the QL processors to be managed, and type:

QLVISION <ENTER>

The Main Menu will display the following options:

• QLVision Supervisor Functions - This option must be selected before the Node, Diagnostics, or Scan functions can be performed. It determines which QL network is to be managed.
• Node Functions - Monitors the status of the nodes and allows the user to perform supervisory control functions on the nodes. Also provides configuration of CPR and POL functions.
• Diagnostics - Provides diagnostics of the QL server driver.
• Historical Log Functions - Provides historical reporting of user login/logout information.
• Scan QL Nodes - Scans a QL network for added, removed, and/or replaced nodes.
• Help - Provides online help.
• Exit to DOS - Terminates the QLVision application.

Each option is described below. Note that it is also possible to perform some of the QLVision functions directly from the DOS command line. This feature is described under Advanced QLVision Features later in this section.

QLVision Supervisor Functions

One QLVision Supervisor is associated with each QL network. The Main Menu options Node Functions, Diagnostics, and Scan QL Nodes operate on the QL nodes on a single QL network. Therefore, the network must be selected before these functions may be performed. This is accomplished by choosing the QLVision Supervisor associated with the QL network.

Upon selecting QLVision Supervisor Functions from the Main Menu, a list of available QLVision Supervisors will be displayed. For a QLVision Supervisor to be included on the list of available supervisors, the user must be logged into the designated server associated with the QLVision Supervisor, and the user must be a member of the QLVISION group on this designated server.

Use the arrow keys to traverse the list, and press <ENTER> to select the currently highlighted QLVision Supervisor.

There are two reasons why a QLVision Supervisor may not be included on the list:

• The QLVision user is not logged into the designated server associated with the QLVision Supervisor. To correct this problem, press <INSERT>. A list of all QLVision Supervisors installed on the network will be displayed. Select the desired QLVision Supervisor from this list. QLVision will prompt the user for a login name and password, and will log the user into the designated server. QLVision will also verify that the user is a member of the QLVISION group on this designated server.

• The QLVision user is not a member of the QLVISION group on the designated server. To correct this problem, the system administrator must create a QLVISION group object with the name of the QLVision user specified as a member of the QLVISION group. Refer to the discussion on Security earlier in this section. Once the group membership is established, return to the QLVision Main Menu and select the QLVision Supervisor Functions option again.

Once a QLVision Supervisor is selected, the following functions are available:

• Specify Description - Enter a description for the QLVision Supervisor.
• Configure Communication Parameters - Specify the timeout values used by QLVision in network communications.

Node Functions

This selection provides monitoring and control of each of the QL nodes installed with the selected QLVision Supervisor.

Monitoring

The status and reset counters are monitored for each node as described below.

Status:

• TxHold - the processor has been reset, but the network shell has not been loaded.
• Present - the processor is physically present, but the QL drivers are not loaded.
• Download - the processor is downloading its image file.
• Active - the processor has booted and passed its memory test.
• Reset - the processor has been marked for reset.
• Timeout - a transmission timeout error has occurred.
• CPR - the processor activity is being verified.
• Not Present - the processor is no longer physically present.

NOTE: The "Not Present" status is only displayed for nodes that become absent after the Node Functions option is selected from the main menu.

Reset Counters:

• CPR Reset Counter - the number of times that the node has been reset by the CPR function.
• Manual Reset Counter - the number of times that the node has been reset by QLVision, CMS, or a SNMP management application.
• Normal Reset Counter - the number of times that the node has been reset by the user (<CTRL><ALT><DEL>) or by the reset on loss of DSR/DCD option (refer to the Hardware Reference chapter for more information on this option.

Control

The control functions available for each node are explained below.

Reset - Performs a hard reset of the specified QL node. Note that this is not a soft reset as occurs when <CTRL><ALT><DEL> is pressed, but is a hard reset as occurs when power to the processor is cycled.

Online - Places a QL node online on demand..

Offline - Places a QL node offline on demand. Note that placing a node offline will immediately terminate any active session on the node. To wait for the current session to end before placing the node offline, use the POL function.

Connect - This function allows the monitor and keyboard on the workstation running QLVision to function as if they were attached to the specified QL node. While the connection is active, the message "Session is being Monitored" will blink at the top of the screen. To terminate the connection, simultaneously press the left SHIFT and left CTRL keys.

The remote connect feature only supports DOS text-based applications. An error will be displayed if an attempt is made to connect to a QL workstation running graphics.

In an OS/2 environment, the remote connect feature only supports connection to DOS sessions on the QL workstation running OS/2. An attempt to connect to an OS/2 workstation that does not have a DOS session running will result in an error. Note that the QLRCV.TSR must be loaded in the DOS session.

Configuration

POL (Pending Offline) - If POL is enabled on a node, that node will be placed offline the next time that it goes into reset. When used in conjunction with the reset on loss of DCD/DSR, the POL function provides a mechanism for an orderly maintenance shutdown of QL processors used for remote communications. For example, if both the reset on loss of DCD/DSR and the POL functions are enabled for all of the QL processors installed in a system hosting dial in users, as each session terminates the QL hosting that session will be placed offline. When all of the QL processors are offline, the system may be shutdown without interrupting any active sessions.

CPR (Cubix Processor Recovery) - Enabling CPR instructs the QL Supervisor to automatically reset any QL node that goes inactive.

Diagnostics

This selection displays the QLVision Supervisor communication information.

Historical Log Functions

This selection describes QL node activity over time. A log may be run on any NetWare file server that has NetWare's accounting services enabled. Supervisor rights to the file server are required.

Scan QL Nodes

This option is intended for use with the Cubix Expansion Subsystem. Some revisions of the Expansion Subsystem may be powered on and off without affecting the file server or router to which they are attached. If QL boards are installed in an Expansion Subsystem, it is possible for the QL boards go online and offline dynamically. The Scan QL Nodes feature causes the selected QLVision Supervisor to scan for QL processors that have been inserted, replaced, or removed.

NOTE: Not all revisions of the Cubix Expansion Subsystem support this "hot swap" feature. Do not attempt to power an Expansion Subsystem on or off while it is attached to an active file server/ router until verifying that the subsystem supports this feature. If the Expansion interface card installed in the server/router has switches on the top edge of the board, it supports the "hot swap" feature; otherwise, it does not.

The Scan QL Nodes function should be invoked under the following circumstances:

• An Expansion Subsystem is offline and contains QL processors.
• A file server or router is running with the QL server driver loaded.
• The Expansion Subsystem is placed online on the file server or router.

Under any of the conditions listed above, the QL processors in the Expansion Subsystem are present but not initialized. The Scan QL Nodes must be invoked to initialize the QL processors and put them into an active state.

Note: While the QLVision supervisor is performing the scan function, SNMP support is suspended. This support is resumed upon completion of the scan.

Help

This selection provides detailed information on all QLVision functions.

Exit to DOS

This function terminates the QLVision session.

Helpful Hints

• At any time during the QLVision session, press <F1> for help with the current function. All QLVision help screens are context-sensitive.
• Remember to select a QLVision Supervisor before trying to perform any node, diagnostic, or scan functions.
• If the QLVision Supervisor installed on file server or router does not appear on the QLVision Supervisor screen, verify that it has software version 5.0 or higher Cubix drivers installed. Verify that the Cubix QLVision Supervisor (QL3_SUPR.NLM or QL4_SUPR.NLM) is loaded.
• To remote connect to a QL workstation running DOS, the QLRCV TSR must be loaded. To remote connect to a QL workstation running OS/2, a DOS session must be running and QLRCV must be loaded.

Advanced QLVision Features

Some QLVision functions may be invoked directly from the DOS prompt by specifying certain parameters on the QLVision command line. This feature allows experienced users to bypass the user interface while performing management functions. QLVision will not request or display any information if command line parameters are specified unless an error is encountered, in which case an error message is displayed and the function is aborted.

F QLVision security requirements are enforced whether or not command line parameters are specified. Therefore, to invoke any QLVision function, the user must be logged into the designated server associated with the QL processors to be managed and must be a member of the QLVISION group on that server.

Command Line Parameters

Option Description

-? Displays command line parameter help

-r server net node Resets a QL processor

-on server net node Places a QL processor online

-off server net node Places a QL processor offline

-cpr+ server net node Enables CPR on a QL processor

-cpr- server net node Disables CPR on a QL processor

-pol+ server net node Enables pending offline on a QL processor

-pol- server net node Disables pending offline on a QL processor

-c server net node Remote Connects to a QL processor, redirecting screen and keyboard I/O over the LAN

-s server net Scans the QL network for QL processors that have been inserted, removed, and/or replaced

where: server specifies the designated server name,

net represents the hexadecimal QL net address, and

node represents the hexadecimal QL node address

Usage

QLVISION [-r server net node]

QLVISION [-on server net node]

QLVISION [-off server net node]

QLVISION [-cpr+ server net node]

QLVISION [-cpr- server net node]

QLVISION [-pol+ server net node]

QLVISION [-pol- server net node]

QLVISION [-c server net node]

QLVISION [-s server net]

Examples

1. QLVISION -r SERVER_ONE 26 3

2. QLVISION -c SERVER_ONE 2C F

3. QLVISION -s SERVER_TWO 2C

QLVer

The Cubix Version Utility (QLVer) is useful in determining and displaying information about a file, including the specific version of a file. For any given file, the Cubix Version Utility will display:

• the file name
• the file size
• the date and time
• the file checksum
• the file version and copyright information for files which contain such information
• internal information stored in NLMs and NetWare driver files.

For example, the Cubix Version Utility can display the following information about itself:

Filename QLVER.EXE

Date/Time 10/08/92 01:07 pm

File Size 33250 (32.47K)

Version Cubix Version Utility v2.00.05 (930623)

© Copyright 1992-1993, Cubix Corporation.

All Rights Reserved.

Command Line Parameters

The QLVER command can include one or more of the following options (the order of these options is irrelevant):

Option Description

-c or -checksum - Calculates and displays a checksum value for each file found. This value is displayed as a hexadecimal digit.

-h or -help or -? - Displays the command format and list of available options with a brief description of each, then exits. This parameter overrides any other parameter, regardless of order.

-n or -nonversion - Disables searching for version and copyright strings within files. Searching through large files for these strings may be time-consuming. Specifying -N instructs the Cubix Version Utility to display only file information for each file: name, date/time, size, and (optionally) checksum information.

-s or -subdirectories - Instructs the Cubix Version Utility to search also through any subdirectories found in the same directory as a file specification.

file specification - Specifies the file or file pattern for which information is to be listed.

Usage

QLVER [options] file specification [file specification...]

Output from the QLVER command may be redirected to a device or file using standard DOS redirection techniques. Refer to the DOS documentation for more information on output redirection.

File Specification Parameter(s)

The QLVER command's file specification parameter determines which file(s) QLVer will examine for version information. The parameter may be a specific filename (e.g. MYFILE.TXT), or may be a file pattern using DOS wildcard characters (e.g. MYFILE.*). Wildcard characters are used as part of a name to represent any single character (?) or any combination of characters (*). Refer to the DOS documentation for more information on wildcard characters.

Additionally, Novell NetWare server and volume name combinations may be used in any combination (e.g. SERVER_1/SYS:SYSTEM/*.*).

At least one file specification must be included with the QLVER command. Multiple specifications may be used. In that case, the specifications are processed in the order entered.

Examples

• The following example presents information for all files located in SYS:CUBIX and its subdirectories on the default server:

QLVER SYS:CUBIX/*.* -S

• The following example presents information for all batch files located in the root directory of C:.

QLVER C:\*.BAT

• The following example presents information for all files on the SYS volume of the ADMIN server including all subdirectories, calculating a checksum value for each file and ignoring version and copyright information, redirecting pertinent file information to the file C:\FILEINFO.TXT.

QLVER ADMIN/SYS:*.* -S -C -N>C:\FILEINFO.TXT

Error Message

The QLVER utility may generate the following error message.

The Cubix Version Utility encountered a command line option which is not defined. The option will be ignored.

Use QLVER -H to show the available command line options.

CMS

The Cubix Management System (CMS) is a complete system for Cubix device management. CMS provides monitoring, alarming, supervisory control, and usage reporting of all Cubix devices on a NetWare network from a central management console. CMS performs all network communications using SNMP encapsulated in IPX packets.

CMS supports all of the functions previously described for QLVision. In addition to the QLVision functions, CMS provides the functions listed below in a graphical, Windows based environment:

• Alarming - CMS reports alarms as they occur and also stores the alarms in an alarm database for historical reporting purposes.
• Usage Reporting - CMS generates reports describing how the QL nodes are used over time.
• Component Information - information describing the hardware and software components installed on each QL node are displayed (e.g. amount of memory installed, memory management configuration, etc.).

In addition, if Cubix devices other than QL products are installed on the network, CMS manages them as well. This allows all Cubix devices to be managed from a single management console.

Installation

Installing CMS support requires changing files on the QL processor and on the server or router in which the QL boards are installed. Specific instructions for installing CMS support may be found in the Cubix Management System Installation Guide.

NOTICE! CMS will not recognize the QL Supervisor or the QL processors unless the installation instructions in the Cubix Management System Installation Guide are followed.

SNMP

The QL Series processors have been instrumented for SNMP via the QLVision Supervisor (QL3_SUPR.NLM or QL4_SUPR.NLM). The information available is defined in a Management Information Base (MIB) text file (CBXQL3S.MIB or CBXQL4S.MIB).

In addition, a standard SNMP trap is generated whenever a QL processor is reset by the CPR function.

If the QL processors are to be monitored by a SNMP management application other than CMS, it will be necessary to configure the management application to ignore certain SNMP traps. This is because some of the traps contain status information intended only for CMS and do not indicate an alarm condition.

The traps to be ignored are identified as follows:

• QL3 Supervisor Status
• QL4 Supervisor Status
• Cubix Trap

Security

Security is based on SNMP Community strings which are optional command line parameters entered when SNMP.NLM is loaded on the device containing the QL processors. The command and its parameters may be placed in the AUTOEXEC.NCF file. The QL Supervisor does not impose any additional security. There are three community strings:

• Monitor Community - (read) allows GET and GET NEXT operations, the default is "public"
• Control Community - (read/write) allows SET operations, the default is disabled
• Trap Community - default is "public"

To configure the community access privileges, specify the appropriate community names when loading SNMP.NLM:

load snmp [options] <enter>

where options are specified as:

MonitorCommunity = {community name}

ControlCommunity = {community name}

TrapCommunity = {community name}

The option name followed by = only (no community name specified) allows access by any community. The option name alone (followed by nothing) disables access by all communities.

Requirements

Novell's SNMP.NLM (file dated 4/6/93 or later) must be installed and loaded on the file server in which the QLVision Supervisor NLM is installed. SNMP.NLM is contained on the Novell SNMP Agent Update diskette v2.1. Installation instructions are contained on the diskette. The contents of this diskette may be downloaded from the Cubix BBS.

Novell NMS

The QL product provides support for the NMS browser. No other NMS support is currently included. To use the NMS browser, perform the following steps:

• Compile the following QL MIB with the NMS MIB compiler: SYS:CUBIX/QLx000/SNMP/CBXQLxS.MIB
• Use the NMS browser to monitor and control the QL processors.
• For the NMS management console to receive QL traps via SNMP, the address of the NMS management console must be placed in the SYS:ETC/TRAPTARG.CFG file on the server or MPR containing the QL boards.

HP OpenView

To manage the QL Series products via HP's OpenView management system, follow the steps below:

• Compile the MIB using the Manage Database option on the OpenView Control menu. The MIB (CBXQLxS.MIB) is located in the SYS:CUBIX/QLx000/SNMP directory, where x represents the QL product type.
• Use the OpenView browser to monitor and control the QL processors.
• OpenView does not directly support SNMP traps. However, OpenView does include a method of reporting alarms. A third party package is available to convert SNMP traps into OpenView alarms. Contact HP for further information on this product.

This document, and all Web contents, Copyright © 1997 by Cubix Corp., Carson City, NV, USA.