Chapter 1
About This Release


1.1 Compatibility Information

The NUMA-Q console software products are compatible with the Sequent NUMA-Q system console PC. The console software products are not compatible with any other Sequent platforms.

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 Sequent 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 Sequent 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.1


1.4.1 versioninfo Script

There is a new script to report the version of the NUMA -Q CSW, VCS, TSCL, NUMA-Q Online Diags,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 001VCS 1.7.0 Build 219TSCL 1.7.0 Build 219Lynxer 1.7.0 Build 213 Wed Sep 01 11:21:38 PDT 1999Multiquad Test v1.7.0 Build 213 Wed Sep 01 11:21:38 PDT 1999MDC firmware 1.7.0 Build 4 3/10/99QBB BIOS 1.7.0 SCLIC firmware Rev 12SBB BIOS 1.7.0 DSCLIC firmware Rev 03BSCLIC firmware Rev 02ptx 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.5 Changes in Console Software Version 1.7.0


1.5.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.5.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 Sequent Customer Service for the access code.


1.5.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.5.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.6 Changes in Console Software Version 1.6.0 and 1.6.1


1.6.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.6.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.6.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.6.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.7 Changes in Console Software Version 1.5.1


1.7.1 Syntax Change for Automatic Flashing

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

-> sysflash.txt numaq_1


1.7.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.7.3 Problems Fixed in Version 1.5.1

The following problem has been fixed:

MDC Does Not Reconnect after Quad Error Recovery


1.8 Changes in Console Software Version 1.5.0


1.8.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.8.2 New CLI Commands

There are several new CLI commands:


1.8.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.9 Changes in Console Software Version 1.4

Version 1.4 was an internal release.


1.10 Call Sequent Customer Support for Assistance

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