Chapter 1
About This Release


1.1 Compatibility Information

The NUMA-Q console software products are compatible with the IBM NUMA-Q system console PC. The console software products are not compatible with any other IBM NUMA-Q platforms. This version of CSW supports DYNIX/ptx version 4.4.4 and higher, 4.5.x, or 4.6.x.

The NUMA-Q system console PC must be running Microsoft Windows NT 4.0 with Service Pack 5.


ATTENTION

If you are running a VCS version prior to 1.3.2, contact Customer Support for instructions. Use the VCS CLI command vcsrev to determine your VCS version.



DANGER

The Console PC is verified with specific settings, configurations, BIOS, operating system, service pack level, and software/firmware versions. Changing any of these things without consulting Customer Service can result in the Console PC becoming incompatible with the Console Software.



1.2 Maximum Systems per Console

The following are the maximum numbers of quads and systems (as configured with the sysdef -c command) in various configurations that can be managed from a single Console PC:


1.3 Powering Off the Console PC

The console PC includes circuitry that prevents powering off the PC while it is performing power-on self tests. After the 5-10 seconds of testing, you can power off the PC using one of these methods:


1.4 Changes in Console Software Version 1.7.5

This is a maintenance release to support DYNIX/ptx version 4.5.2.


1.5 Changes in Console Software Version 1.7.4


1.5.1 masterid bootflag

The masterid bootflag is now used by DYNIX/ptx and should be set as part of the 4.6.0 installation. The bootflag can be set from the VCS CLI window or from the VCS Console window. The masterid should be set to the lowest nodeid for the quads. The masterid can be set through the VCS Console window or from the VCS CLI. If nodeid is not set, contact your Service representative.

From the Console window, click the Settings button. Click on the Advanced tab, and enter the appropriate value in the masterid field.

From the VCS CLI window, use the command:

-> cd \\numaq1\quad0
-> bootflags masterid master_id
where numaq1 is your system name, and master_id is the masterid value.


1.6 Changes in Console Software Version 1.7.3


1.6.1 New or Modified CLI Commands


1.6.2 Autoconfiguration Tool for Partitioning

An autoconfig tool has been developed. This tool can only be run by an IBM NUMA-Q representative. A special password in required. When the tool is run, the existing system is saved. If you exit from the tool, the existing configuration is restored.


ATTENTION

Before running the autoconfig tool, verify which quad is set up as the boot quad. The name of the boot quad must be entered during the configuration.


Once the tool is started, the existing systems are deleted. You are prompted for the password for each system to be deleted. After the deletions, a list of configuration choices is displayed. The number of choices vary, depending on the number of quads and LASHs available for configuration. Enter the Selection number for the desired configuration or enter the number for Exit to restore the system to the previous configuration.

In the following example, 7 quads are available:

-> autoconfig
===================================================================
Please note the following before running these scripts:
 1. If any Quad or Lash is added or removed from the configuration, 
the following files must be deleted prior to running the scripts -
c:\winnt\connections.tbl
c:\winnt\resourceXref.tbl
c:\winnt\probe.tbl

2. It is recommended that the Pbay connections be made after running the scripts
because, before running the scripts, it may not be clear as to how the script
will partition the available resources in reference to the BOOT QUAD.
===================================================================


Press <ESC> followed by <Enter> to exit or <Enter> to continue 
Saving the Existing Partition information
Please Enter PassWord for system creation/deletion :
sysdef: 'sys1' deleted successfully



SELECTION |PARTITION 1|PARTITION 2|PARTITION 3|PARTITION 4|
==========|===========|===========|===========|===========|
    1.    |    1Q     |     1Q    |    1Q     |     5Q    |
    2.    |    1Q     |     1Q    |    2Q     |     4Q    |
    3.    |    1Q     |     1Q    |    3Q     |     3Q    |
    4.    |    1Q     |     2Q    |    5Q     |           |
    5.    |    3Q     |     5Q    |           |           |
    6.    |    8Q     |           |           |           |
___________________________________________________________
    7. Exit

Enter your selection ==> 6
Once you enter a Selection number (5 for this example), the list of resources is displayed. You are prompted to enter the number for the boot Quad. In this example, Quad255 is the boot quad. You are prompted for the password for each system that the configuration tool creates.

A 8 Quad configuration is going to be created now ..

 The Quads available are : 
Quad255
Quad209
Quad104
Quad256
Qsq053
Qcq024
Qcq005
Qcq025
Enter the boot Quad name (should be one among
the list shown above): Quad255

 The Quads available are : 
Quad209
Quad104
Quad256
Qsq053
Qcq024
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Quad209

 The Quads available are : 
Quad104
Quad256
Qsq053
Qcq024
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Quad104

 The Quads available are : 
Quad256
Qsq053
Qcq024
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Quad256

 The Quads available are : 
Qsq053
Qcq024
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Qsq053

 The Quads available are : 
Qcq024
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Qcq024

 The Quads available are : 
Qcq005
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Qcq005

 The Quads available are : 
Qcq025
Enter the next Quad name to be part of the system
(should be one among the list shown above): Qcq025
Please enter the name for this partition (system name): sys1
Please Enter PassWord for system creation/deletion :
->


1.6.3 Adding or Removing a Quad or LASH

If a quad or LASH is added or removed from a system or partition, the following steps must be performed:

  1. Add or remove the physical unit, following the procedures in the hardware installation manual.

  2. Delete the files: C:\winnt\connections.tbl, c:\winnt\resourceXref.tbl, c:\winnt\probe.tbl

  3. Run the C:\vcs\scripts\autoconfig tool.


1.7 Changes in Console Software Version 1.7.2


1.7.1 Firmware Support for CQuads and Midrange CQuads

New firmware files are included to support the CQuad and Midrange CQuad: cstr1_XX.obj and cmstr1_XX.obj, where XX is the revision number for the file.


1.7.2 EES Supported in CSW

The EES feature is integrated with CSW. Error, Warning, and Fatal log messages occurring during initial powerup, successive bootup or while the OS is running, are sent to DYNIX/ptx.This transfer is through the QMI. The new VCS CLI command eeslog <sysid> <mesg> can be used to write mesg to the EES log to test EES functionality. If the EES-QMI connection cannot be made, messages are stored in a buffer. The buffered messages are resent when one of the following conditions occur


1.7.3 Different Processor Notification

If different processors or different steppings of the same processor are installed in a quad, a warning message is displayed. If Windows NT is the operating system on the quad, the processors will have to be replaced. Windows NT requires all processors in the system to be identical.


1.7.4 Console Input Blocked Until Single or Multi User State is Reached

The console window no longer accepts user input while the system is starting. The console remains blocked until the system is in either a single user or a multi-user state.


1.7.5 New Online Diagnostics Menu Option

A new menu choice, Exit Online Diags, has been added to the File menu of the Online Diagnostics GUI. This command closes all Online Diagnostics windows.


1.7.6 New or Modified CLI Commands


1.8 Changes in Console Software Version 1.7.1


1.8.1 versioninfo Script

There is a new script to report the version of the NUMA -Q CSW, VCS, TSCL, Lynxer, and MultiQuad Tests. It also prints the available Baseboard BIOS, SCLIC, sak.dat, and ptxldr.elf information. A versioninfo.man has also been added. Here is an example of the versioninfo report:

NUMA-Q Console Software V1.7.1 Rev 001
VCS 1.7.0 Build 219
TSCL 1.7.0 Build 219
Lynxer 1.7.0 Build 213 Wed Sep 01 11:21:38 PDT 1999
Multiquad Test v1.7.0 Build 213 Wed Sep 01 11:21:38 PDT 1999
MDC firmware 1.7.0 Build 4 3/10/99
QBB BIOS 1.7.0 
SCLIC firmware Rev 12
SBB BIOS 1.7.0 DSCLIC firmware Rev 03
BSCLIC firmware Rev 02
ptx Standalone Kernel V4.4.6 Tue Apr 13 18:48:06 GMT 1999 
ptx Loader V4.4.6 03/18/99 
ptx Standalone Kernel V4.4.7 Mon Nov 29 23:11:01 GMT 1999 
ptx Loader V4.4.7 11/29/99 
ptx Standalone Kernel V4.5.0 Fri Sep  3 15:47:28 GMT 1999 
ptx Loader V4.5.0 08/23/99 

1.9 Changes in Console Software Version 1.7.0


1.9.1 Automatic Remote Application ARA

The ARA (Automatic Remote Application) is an alternative to an interactive VCS telnet session, especially in cases where you want to remotely execute and capture the output of a single CLI command or script. An advantage of ARA is that it can be used even if VCS is not running on the remote console. Using ARA for audits and query commands is a low performance impact on anyone using VCS locally. Other commands, such as building an offline diagnostics test tree, are a higher impact to the local session.


ATTENTION

For secure environments, installing ARA should be carefully considered. ARA does not require a password. Anyone with a local ARA client and the IP address or system name can access the CLI.


The following are required to run ARA:

The ARA client and ARA server use TCP/IP communications via standard sockets. You can use the ping command (when available) to test the connection between your local machine and the remote console. For example, if the remote console's IP address is 188.95.122.23, type ping 188.95.122.23.

This example uses ARA from your local machine to list the current system definition (sysdef -l):

ara 188.95.122.23 sysdef -l

This example uses ARA to perform a console audit, using the conaudit.cli script:

ara 188.95.122.23 conaudit
The conaudit.cli script audits all hardware connected to the console via the MDC net.


1.9.2 New CLI Commands

There are several new VCS CLI commands:

FatalError
Lists or clears the fatal errors and fatal error status.
fwgoldosfile
Get or set the firmware golden OS file used by fwgold.
reg
Sets or displays a Windows NT registry key.

There is also a new option for the diary command:

-z zapitcode specifies the access code for clearing everything (required with the -c option). Contact Customer Service for the access code.


1.9.3 Flash Script Update

The flash script displays a list of available ptx versions when it is run. Type the option number (appearing in the parenthesis) and press Enter. The script flashes only the firmware components necessary for each quad or IQ-Ring module. If the OTHER choice is selected, flash does not update the OS firmware.


1.9.4 CommandPoint Launcher No Longer Supported

CommandPoint Launcher is no longer supported. Instructions for removing the existing Launcher information is included as part of the installation. Launcher information must be removed prior to installing the new files.


1.10 Changes in Console Software Version 1.6.0 and 1.6.1


1.10.1 Syntax Change for Automatic Flashing

The sysflash.txt script has been renamed flash. It does not require a system name. For example: -> flash


1.10.2 Boot ptx or Windows NT on NUMA-Q 1000 Systems

OS boot choices have been added to the Console window Settings dialog (and bootflags) to determine which operating system to boot on a NUMA-Q 1000 system. The specified operating system must have been previously installed on the system. Boot flag values that do not apply to the selected operating system are grayed (stippled) out.


1.10.3 CommandPoint Launcher No Longer Supported

CommandPoint Launcher is no longer supported. Instructions for removing the existing Launcher information is included as part of the installation. Launcher information must be removed prior to installing the new files.


1.10.4 New CLI Commands

The following commands have been added to the VCS CLI:

'bootcheckflag -S statusVar -O outputVar <no args>'
# Set/clear/display boot check enable flag.
'bootcheckscript -S statusVar -O outputVar <no args>'     
# Set/display boot check script name flag.
'forcePOSTcodelogging -S statusVar -O outputVar [-p path] on|auto'     
# Controls whether POST codes are logged
'lashdeconfig -S statusVar -O outputVar [ -p path ] [on | off] '     
# Turn Lash De-Configuration on or off
'matrix -S statusVar -O outputVar [-r] [partno] [rev]'     
# Get compatibility matrix information.
'nteventredirect -S statusVar -O outputVar [ -p path ] [y|n] '     
# display or set NtEventRedirect flag
'vcspriority -S statusVar -O outputVar [-h | -n]'     
# set VCS priority to either High or Normal

The following commands have been added to both the VCS CLI and the Online Diagnostics CLI:
'clint -S statusVar -O outputVar [-l] [-b] script_file'
# scan a script file and find undefined symbols.
'fastforeach -S statusVar -O outputVar <no args>'     
'ffe -S statusVar -O outputVar <no args>'     
'findfile -S statusVar -O outputVar fileName'     
# Find a file in the VCS install base. Returns nothing if file not found.
'fwgold -S statusVar -O outputVar <no args>'     
# Returns a description/list of the firmware which should be at the current 
# hardware path.
'fwgoldfile -S statusVar -O outputVar <no args>'     
# Get/Sets the firmware golden file used by fwgold.
'islash -S statusVar -O outputVar <no args>'     
# Returns 1 if current hardware path is a lash. Otherwise returns 0.
'isquad -S statusVar -O outputVar <no args>'     
# Returns 1 if current hardware path is a quad. Otherwise returns 0.
'issystem -S statusVar -O outputVar <no args>'     
# Returns 1 if current hardware path is a system. Otherwise returns 0.
'substring -S statusVar -O outputVar sourcestring offset length terminator'     
# return substring of sourcestring deliminated by offse
t and length, or optionally by terminator
'timezonebias -S statusVar -O outputVar <no args>'     
# Returns the difference, in minutes, between C
oordinated Universal Time (UTC) and local time.
'tolower -S statusVar -O outputVar string'     
# Convert string to all lower case characters.
'undeclare -S statusVar -O outputVar -g|-l varName1 varName2 ...'     
# undeclare a local or global variable. Default is local.


1.11 Changes in Console Software Version 1.5.1


1.11.1 Syntax Change for Automatic Flashing

The sysflash.txt script now requires a system name. For example:

-> sysflash.txt numaq_1


1.11.2 Support for Large Systems

The console software supports up to 16 quads and 4 IQ-Ring Modules (LASHs).


ATTENTION

If you set up an alternate boot quad for a large system, use one that is on a different IQ-Ring Module than the primary boot quad. This provides a boot alternative if the IQ-Ring Module with the boot quad fails.



1.11.3 Problems Fixed in Version 1.5.1

The following problem has been fixed:

MDC Does Not Reconnect after Quad Error Recovery


1.12 Changes in Console Software Version 1.5.0


1.12.1 Automatic Flashing

The script /vcs/scripts/sysflash.txt can be used to automatically flash all of the MDC firmware and system files and the SBB and QBB BIOS. Host Adaptor firmware flashing must still be performed manually.


1.12.2 New CLI Commands

There are several new CLI commands:


1.12.3 Problems Fixed in Version 1.5

The following problems have been fixed:

Console Panic button locks the console power button.

qct -a command causes a Dr. Watson.


1.13 Call Customer Support for Assistance

If your shipment is incomplete or you encounter problems while installing the console software, contact your local Customer Support representative.