CommandPoint MonitorTM V1.1 runs on a PC running Windows NTTM and monitors major components of NUMA-Q® systems using the Simple Network Management Protocol (SNMP).
Version 1.1 of CommandPoint Monitor features the following:
Problem report fixes (a list of fixed bugs is included in these release notes)
Corrected usability issues from V1.0
Monitoring of NUMA-QTM 2000 systems and DASS devices
Usage-threshold reporting for system resources such as filesystem space and inode usage
CommandPoint Monitor reports the following details:
A high-level summary of node activity such as uptime, system load, processor load, swap-space usage, and streams-buffer usage
Node- or cluster-specific error information
ptx/CLUSTERS configuration information
ptx/SVM configuration in a graphical format
Disk layout or topography in a graphical format
Physical devices (such as processors and memory) information
Logical storage devices (such as filesystems and streams buffers) information
These Release Notes contain the following information:
Compatibility information
Installation instructions
Related documentation
Problems fixed since the previous release
How to report problems
Open problem reports
The following software products are prerequisites for the CommandPoint Monitor Version 1.1 software product:
Windows NT V3.51 operating system, including Service Pack, 4 or Windows NT 4.0. (The Windows NT V3.51 Service Pack 4 contains some fixes which CommandPoint Monitor relies upon.)
ATTENTION You can ftp the Windows NT Service Pack 4 from the following ftp site:ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351. If you are unable to access the Microsoft ftp site, please contact Microsoft Corporation.
The following list shows the NUMA-Q software (and version number) that reports information to CommandPoint Monitor.
DYNIX/ptx Base Version 4.1.4 or later, or 4.2.x, or 4.4.x. (If you are running DYNIX/ptx 4.1.4 or 4.2.0, you need to request fast patch number 219496.)
ATTENTION CommandPoint Monitor cannot monitor DYNIX/ptx 4.3.
ptx/AGENTTM V1.2.0 or later
ptx/SVM V1.5.0 or later
ptx/LAN Version 4.1.0 or later
ptx/TCP/IP Version 4.1.2 or later
ptx/CLUSTERS V1.3.0 or later
ATTENTION If you are running NetView® and CommandPoint Monitor, there is an incompatibility problem with the mfc30.dll file in NetView's home directory. This file should be in the system directory of the Windows NT installation directory, not in NetView's home directory.
ATTENTION Running CP Monitor over Citrix® WinFrameTM is NOT supported by NUMA-Q.
Informal testing suggests that you can run CommandPoint Monitor from an X session using Citrix Systems' WinFrame product including X sessions started from an X terminal or from a PC running X emulation software such as Hummingbird's eXceed® product.
We have successfully run CommandPoint Monitor over Citrix WinFrame 1.6 and, for NCD terminal support, Network Computing Devices' WinCenter 2.0 allowing X-terminal access to the application. However, running CommandPoint Monitor over Citrix WinFrame is not supported by us.
WinFrame is an extension of Microsoft's Windows NT Server product.
The hardware requirements are as follows:
PC with a 50 MHz 486 processor or better
10 MB disk space for program files
24 MB of RAM
Network card and TCP/IP support
PC with a 90 MHz Pentium® processor or better
10 MB disk space for program files
32 MB of RAM
Network card and TCP/IP support
ATTENTION A minimally-configured PC should monitor no more than 2 systems; a PC running with the recommended configuration should monitor no more than 10 systems. Performance will also vary depending on the refresh rate as well as the number of peripherals, disks, and SVM objects on the systems being monitored. For example, when installed on a PC running the recommended configuration and monitoring 10 NUMA-Q systems containing 100 SVM objects each, CommandPoint Monitor's performance will be better than when monitoring 5 NUMA-Q systems containing 1,000 SVM objects each.Lowering the refresh rate from the default value of 5 minutes will also impact performance. However, whether the impact will degrade performance on the PC to an unacceptable level will vary from site to site. We recommend that for each instance of CommandPoint Monitor, you space the addition of systems to monitor over a course of several hours to observe how the addition of each new system affects the performance of one instance of CommandPoint Monitor. If CommandPoint Monitor's performance degrades to an unacceptable level, you should consider monitoring one or more of the systems from another instance of CommandPoint Monitor.
ATTENTION These installation instructions assume that Windows NT V3.51 or Windows NT 4.0 is installed and running and that there is a network card providing TCP/IP support.
ATTENTION Please Uninstall any existing version of CommandPoint Monitor that you may be running prior to installing V1.1.0. There are some minor installation problems if V1.1.0 is installed over an existing version.
ATTENTION If you a logged in as a Windows NT administrator when you install CommandPoint Monitor, the CommandPoint Monitor software will create a Common Program group. If you are not logged in as an administrator, CommandPoint Monitor will create a Personal Program group.
ATTENTION If a user uninstalls CommandPoint Monitor, it will be uninstalled for all users on that PC. Also, each time a user reinstalls CommandPoint Monitor, it will be updated for all users on that PC. (This is common to all Windows NT-based software products.)
Perform the following steps to install CommandPoint Monitor:
Log in to your PC.
Insert the CD into the CD-ROM drive.
If you are running Windows NT 3.51, open the NT File Manager. If you are running Windows NT4.0, start Explorer.
Double-click on the CD-ROM icon.
Double-click on setup.exe for the CommandPoint Monitor product.
The CommandPoint Monitor Setup window appears. You should read the instructions in each of the windows and use any default values supplied.
The setup windows of CommandPoint Monitor installation are as follows:
Welcome
User Information
Registration Confirmation
Setup Type
Select Program Folder
Start Copying Files
Setup Complete
Notepad - README.txt
After the you see the Setup Complete window, you need to add the system(s) you want monitored. These steps are described in these release notes.
To start CommandPoint Monitor, double-click on the CommandPoint Monitor icon in the CommandPoint Monitor program group.
The first time you start CommandPoint Monitor, you will see the following message:
Launcher Initialization Cache directory name missing/invalid. This is normal if you are running CommandPoint Monitor for the first time on this system. Please update the name in the options window which will now be displayed.
Click on OK. The Options window will appear. The Options window will list a path for the cache directory. If that path is OK, enter y. If not, enter another pathname for the cache directory.
Once the CommandPoint Monitor software is installed and running (as described in this document) you need to perform the following tasks to start monitoring of your NUMA-Q system(s):
Select New from the File menu in the CommandPoint Monitor Launcher window. The Monitor a New Node window will appear.
ATTENTION If the "New" File menu option is disabled or "greyed out", click in the left pane of Launcher.
Enter the Network Name for the node you want to monitor. Note that the Node Name field will also be filled in as you enter the Network Name.
A network name can be either a Qualified Domain hostname or an IP address. If you use an IP address, you will have to fill in the Node Name field.
Press Return to use the default Community String field value, ``public". Otherwise, enter an SNMP community name that provides access to the node you want to monitor.
An icon representing the node will now appear in the left pane of Launcher.
ATTENTION ptx/AGENT is shipped with a pre-defined SNMP community of "public". By default, this community provides read-only access to all the SNMP variables used by CommandPoint Monitor. You can add or modify SNMP communities by editing /usr/agent/config/agt/agt.pty on your NUMS-Q system.The Community String value that you supply to CommandPoint Monitor must match a community in /usr/agent/config/agt/agt.pty on your NUMA-Q system.
ATTENTION Depending on the size of your NUMA-Q system, it may take CommandPoint Monitor several minutes to initialize its view of your system. During this time, the message ``Refreshing host" will appear in the status bar (bottom left of the Launcher window). Windows related to disks, ptx/SVM, and ptx/CLUSTERS are typically the last to be populated. For each of those windows, progress is indicated in the bottom right corner.You can initialize multiple hosts concurrently.
Repeat steps 1-3 for each node you want to monitor. If the node is part of a cluster, it will automatically be grouped by cluster. However, the other cluster nodes are not automatically added. You will need to add the other cluster nodes as you would any other monitored node.
CommandPoint Monitor will now report health and configuration information about the listed node(s).
Once you have completed these installation steps, you can refer to the CommandPoint User's Guide or to the online help for more information about CommandPoint Monitor.
The following documentation is available for CommandPoint Monitor. Contact your sales representative for order information:
CommandPoint Monitor User's Guide
TCP/IP now reports the correct status of csme devices. (218366)
TCP/IP now reports the correct information about EthernetTM devices. (218511)
Find now matches throughout a string. (220433)
ptx/SVM Agent now reports correct value for BCL. (220467)
ptx/SVM sqntSvmVolumePreferredPlex field is no longer empty. (222165)
ptx/AGENT now reports correct information for CD-ROMs. (222227)
ptx/SVM subdisk information is no longer lost when a subdisk is split and then rejoined. (222741)
The Disk Resources application no longer is confused by numeric Internet addresses. (223325)
CommandPoint Monitor no longer crashes on exit under any known circumstance. (224913)
The offline processor state in now correctly reported to CommandPoint Monitor. (222292)
Projection now behaves correctly (previously, you had to have all views that would be affected opened before invoking projection). (224117)
Horizontal object sizing now behaves correctly in the SVM Configuration window. (224659)
Vertical object sizing behaves correctly in the SVM Configuration window. (224675)
A ``refresh in progress" is now visible. (224885)
RAID devices are now correctly monitored by CommandPoint Monitor. (224967)
A large number of error messages no longer appear in the Error Details window when many ptx/SVM configuration changes are made over a short period of time. (225202)
The Color Legend window title now appears at the initial window opening. (228316)
The F5 (Refresh) key now works correctly in all windows. (221586)
The File-->Print option in the Error Details view now works correctly. (228742)
When you press F5 (Refresh) in the Disks view, the device status is now immediately updated. (228903)
Pressing the Abort button while printing a lengthy report no longer causes Monitor to crash. (228632)
Symmetry® systems running ptx/AGENT V1.3 now show up in Launcher as the correct system type. (228493)
All fields in the Node Summary now correctly copy or print. (228494)
All fields in the SVM Summary now correctly copy or print. (228495)
Spurious characters no longer appear at the end of the buffer when doing a copy in the Network Interfaces window. (228497)
All fields in the Clusters Summary now correctly copy or print. (228558)
In Windows NT 3.51, a minimized view's health shows the correct state. (224623)
If two Options dialogs are brought up at the same time and changes are made to one of them, the other one does not show the changed values even if Apply or OK is pressed in the changed dialogue. (221539)
``Copy" and ``Save As" store all columns available. This behavior will not be changed in CommandPoint Monitor V1.1. (222177)
``Print" of ``Save As" can now be open when Command Point Monitor exits. (230267)
The are no longer internal errors when ptx/AGENT is restarted. (223402)
If the SVM Summary window shows a Critical health status, there is now a corresponding event in the Error Details window. (223622)
CommandPoint Monitor no longer forgets that an object such as an SVM volume or plex has been acknowledged. (228652)
In graphical views, closing a clone no longer makes the previous window's color legend window lose its window settings, thereby becoming really huge. (228708)
ptx/SVM V2.x volumes now have correctly associated filesystems and swap area. (229042)
Swap areas are now correctly associated with the appropriate partitions and correct information is now reported if swap is on a shared volume. (229100)
A Filesystem/Partitions Refresh no longer caused the loss of projection. (230377)
In the Disks view, the ``Use Zero Range" function no longer causes invalid coloring. (230375)
In the SVM Configuration view, a Refresh no longer causes ``Scale to Fit" to fail. (228924)
The Cluster Summary's "ptx/CLUSTERS Version No.:" field problem has been fixed. (230258)
ptx/AGENT now returns the correct value for a SCSI channel's controller ID (sqntPtxBusCtlrId). (224364)
ptx/AGENT now correctly reports the device unit numbers on DASS Raid devices (rd and rdc). (224607)
Losing a quorum disk no longer hangs ptxagt. (228835)
The clustersagt now reports a node leaving a cluster. (228835)
svmagt now implements sqntSvmFreeSpaceDIndex.
ptx/SVM subagent no longer terminates when shared object is removed. (222769)
The ptx/SVM 1.5.1p1 subagent no longer returns the incorrect version number. (225159)
CommandPoint Monitor now reports correct values for the sqntSvmSummaryInfo group in the SVM Summary view.
CommandPoint Monitor can now correlate the VM disk with the sd3s12 partition.
If you have problems with CommandPoint Monitor, please write down the date and time the problem occurred, which windows you were viewing, what was happening (if known) on the systems being monitored, and any error messages you see on the screen or in the Error Details window. Please report this information to NUMA-Q Customer Support.
The number that appears in parentheses in problem report titles is the internal number assigned to the report. These problems will be corrected in a future release unless otherwise noted.
quad and fabric objects in the Disk view do not have Properties windows.
Workaround. None.
CommandPoint Monitor will not indicate that a host is unreachable if the console's network connection is not in place.
Workaround. None.
CommandPoint Monitor will behave badly if you try to monitor multiple hosts with the same name (such as hq.oracle.com and hq.informix.com) with the same instance of CommandPoint Monitor.
Workaround. None.
When you first start CommandPoint Monitor, the information about previously monitored nodes is ``stale" and is being refreshed. If you Mark As Acknowledged a Critical event, the ``acknowledged" health is not reflected in the Launcher window until the refresh operation is completed.
Workaround. Wait until the refresh operation has completed.
When a node is renamed, the registry information for that node is deleted.
Workaround. None.
In the SVM Configuration window, the Zoom In feature may not work correctly with a large number of objects (such as 209 volumes, 1644 plexes, and 2148 subdisks).
Workaround. None.
The base node names reported by uname -n and hostname for a node should not be different. If they are different, a CommandPoint Monitor error might occur.
Workaround. None.
If no information can be loaded for a node, no windows are available, except for Error Details. If you double-click on the Error Details icon, no window opens.
Workaround. Delete and re-add the node in Launcher.
In the Disks view, when a Refresh occurs, the Color Legend flashes several times and the ``Time since refresh" clock resets to zero each time. This is because CommandPoint Monitor updates the associated inform in several steps.
Workaround. None.
Help text will not be available for the following (because of a printer driver constraint):
File/Print/Properties/Help
File/Print/Properties/Options/Help
File/Page Setup/Printer/Help
File/Page Setup/Printer/Properties/Help
File/Page Setup/Printer/Properties/Options/Help
Workaround. None.
In the Property->Members tab of the Cluster Summary view, the columns don't always size properly.
Workaround. None.
Projection does not work between the Misc Devices view and the disk resource views.
Workaround. None.
When a Refresh occurs, the horizontal scroll (if any) can misbehave.
Workaround. None.
When a host is down or in HALTED or MAINTENANCE state, it is not guaranteed to be recognized as part of a cluster when initially added to LaunchPoint.
Workaround. None.
Scrolling in the SVM Configuration view using the scroll bar can be slow and jerky.
Workaround. Use the Page Up, Page Down, up arrow and down arrow keys instead of the vertical scroll bar.
The following example explains this bug:
1. User opens up disk view and projects a controller.
2. Projection is applied to all the views.
3. Now the system configuration changes and a new disk comes on line for the projected controller.
4. The displayed projection is now obsolete and incomplete.
Workaround. Re-apply the projection.
If you minimize either the Disks or SVM Configuration window before the data is loaded, the Color Legend dialog box pops up on the screen.
Workaround. None.
In the SVM Configuration view if plexes are very long graphically, there is a lot of empty space prior to the display of subdisks in the "Subdisks" column and a lot of empty space after it. This makes the view wider than necessary and is not visually appealing. It also forces the user to scroll too much.
Workaround. None.
The SVM Configuration view can be slightly wider than the desktop.
Workaround. Resize the SVM Configuration view.
CommandPoint Monitor may report errors for new Raid devices it doesn't recognize.
Workaround. None.
The Cluster Summary's "ptx/CLUSTERS Version No.:" field may be blank; the version number is correct in the MIB. This may also cause printing and copying to assert.
Workaround. None.
The status bar in the lower right corner may report "No Connection, Showing Cached Data", when data may be current.
Workaround. None.
Sometimes the svmagt does not give CommandPoint Monitor the diskgroup name (it is given a blank name). This causes CommandPoint Monitor to assume that the diskgroup names are unique.
Workaround. None. CommandPoint Monitor will give the diskgroup the UUID name.
CLARiiON® ArrayGUIdeTM doesn't register itself in the registry. This bug has been reported to CLARiiON.
Workaround. To register the CLARiiON's ArrayGUIde product, perform the following procedure:
Go to the directory where you installed CommandPoint Monitor and edit the arraymgr.reg file. (The contents of the file are included here for your reference.)
// Register Launcher.
// The AppName is used in all the views (and needs to be identical).
[HKEY_LOCAL_MACHINE\SOFTWARE\Sequent\CommandPoint\CurrentVersion\ArrayGUIde]
"AppName"="ArrayGUIde"
"Path"="D:\\ARRAYMGR\\ARRAYMGR.EXE -host %1"
"WorkingDir"="D:\\ARRAYMGR"
[HKEY_LOCAL_MACHINE\SOFTWARE\Sequent\CommandPoint\CurrentVersion\Launcher\Views
\
Node\RightPane\PhysicalDevices\ArrayGUIde]
"AppName"="ArrayGUIde"
"ViewName"="ArrayGUIde"
"ViewID"="ArrayGUIde"
"ObjType"="Application"
"Icon"="ArrayMgr.ico"
"Order"=dword:00000135
"State"=dword:00000208
Locate the "Path"="D:\\ARRAYMGR\\ARRAYMGR.EXE -host %1" and the "WorkingDir"="D:\\ARRAYMGR" lines.
Replace the Path and WorkingDir values to match the values on your system.
Save the file.
Merge the saved registry file into the system registry by either double clicking on the file, or by using the regedt32.exe program. This program is a native Windows NT program, and is part of the Windows NT installation.