CommandPointTM SVM V2.1.0 Release Notes


Introduction

These release notes support CommandPointTM SVM V2.1.0, an application for administering ptx®/SVM. CommandPoint SVM V2.1.0 is based on the VERITAS® Volume ManagerTM Storage Administrator V1.0 product from VERITAS Software Corporation, with changes and extensions to support DYNIX/ptx® and ptx/SVM.

CommandPoint SVM is an optional, JavaTM-based application for administering ptx/SVM on either Symmetry® or NUMA-Q® hosts. CommandPoint SVM can be used instead of, or in conjunction with, the command-line utilities and svmadmin menu system for administering ptx/SVM volumes and disks.

The CommandPoint SVM server runs on a Symmetry or NUMA-Q host that is running ptx/SVM and executes commands to administer ptx/SVM volumes and disks. CommandPoint SVM clients provide the graphical user interface to administer ptx/SVM volumes and disks through a local or remote CommandPoint SVM server. A CommandPoint SVM client runs on a host running DYNIX/ptx or on a PC running the Windows NT® 4.0 operating system.

This document contains information on product compatibility, release-specific installation instructions, an overview of CommandPoint SVM, how to get started, and known problems. Read this document before you install or run this release of CommandPoint SVM.


Features in this Release

CommandPoint SVM includes the following features:


Software and Hardware Compatibility Information


CommandPoint SVM Server and Client Performance by Platform

The following table summarizes CommandPoint SVM performance on various platforms:

Table 1. CommandPoint SVM Performance by Platform
System Type CommandPoint SVM Client CommandPoint SVM Server

Windows NT

OK

NA

NUMA-Q

OK

OK

Symmetry, floating-point workarounds disableda

Not recommendedb

OK

Symmetry, floating-point workarounds enableda

Not supportedc

Not supportedc


a. A floating-point chip-bug workaround is considered active (and CommandPoint SVM should not be used) if the system contains 60- or 66-MHz Pentium CPUs, and the FDIV_BUG and/or FIST_BUG kernel parameters are enabled in the kernel. For more information, refer to "Floating-Point Workarounds on Symmetry Platforms and CommandPoint SVM Performance."

b. The CommandPoint SVM client runs very slowly on Symmetry systems. For example, on a NUMA-Q or Windows NT system, the client's initial window typically appears in 6-10 seconds. On a Symmetry system, this may take a minute or more.

c. In this configuration, CommandPoint SVM performance is so slow that it appears to be hung for minutes at a time. It also places a heavy load on the system due to all the floating-point traps.


Floating-Point Workarounds on Symmetry Platforms and CommandPoint SVM Performance

If kernel workarounds for FDIV floating-point chip bugs in 60- and 66-Mhz Pentium systems are enabled on Symmetry platforms, CommandPoint SVM server and client performance is so slow that CommandPoint SVM appears to be hung. The floating-point workarounds are enabled or disabled based on the values of the FDIV_BUG and FIST_BUG kernel parameters. By default, FIST_BUG is set to 0 (zero), which disables this FIST workaround, and FDIV_BUG is set to 1 (one), which enables the FDIV workaround. If you have either or both of these kernel parameters set to 1 (one) on your Symmetry host, you cannot use CommandPoint SVM server or client on that host.

However, disabling the floating-point workarounds will allow you to run the CommandPoint SVM server with reasonable performance. (As on any Symmetry system, client performance will be mediocre; run the client on NT or a NUMA-Q.)


ATTENTION

Disabling the FDIV_BUG and FIST_BUG chip-bug workarounds may allow the processors to give incorrect values on certain division and conversion operations. Review the subsection entitled "Pentium Error Workarounds" in Chapter 5 of the DYNIX/ptx System Configuration and Performance Guide to evaluate whether your site should disable these workarounds.


Complete the following steps to disable the floating-point workarounds:

  1. Determine whether the floating-point workarounds are enabled by issuing the following commands:

    bp -s /unix /dev/kmem fdiv_bug
    bp -s /unix /dev/kmem fist_bug

    A response of 0x1 means the workaround is enabled, 0x0 means the workaround is disabled. Note that setting fdiv_bug or fist_bug to 0 using the bp command will not disable the workarounds. You must boot a new kernel.

  2. If either of the floating-point workarounds are enabled, use ptx/ADMIN to set the values of the FDIV_BUG and FIST_BUG kernel parameters to 0 (zero) as needed. (A value of zero disables the workaround.) For more information about configuring the kernel, refer to the DYNIX/ptx System Configuration and Performance Guide.

  3. Recompile and boot with the newly configured kernel.


DYNIX/ptx Server and Client Requirements

The following software products are required on the Symmetry or NUMA-Q hosts that will be running the CommandPoint SVM server or client software:


Windows NT Client Requirements


Software Requirements

CommandPoint SVM is compatible with the following software products running on a PC:


ATTENTION

CommandPoint SVM requires approximately 40 MB of space, including 2 MB for the Java Runtime Environment (JSE). If JSE is already installed on your PC (for example, if CommandPoint Clusters is already installed), then it will not be reinstalled.



Hardware Requirements


ATTENTION

Do not use the VCS console on a NUMA-Q system to run CommandPoint SVM.


If you plan to use the Windows NT-compatible client to administer your ptx/SVM system, then the following minimum requirements apply to the PC that you will be using. (These requirements are in addition to the DYNIX/ptx requirements listed in the previous section.)


ATTENTION

The minimum configuration will allow you to run all three CommandPoint products (CommandPoint Admin, CommandPoint Clusters and Command Point SVM) simultaneously. However, the performance will be better is you use the recommended hardware configuration.

Whichever configuration you choose to use, the performance of the system will be impacted by the number and size of the applications that you run simultaneously.



Minimum Hardware Configuration

The minimum hardware requirements are:


Recommended Hardware Configuration

The recommended hardware requirements are:


Disk Space Requirements

Installing CommandPoint SVM software on DYNIX/ptx requires 14 MB. Installing CommandPoint SVM software on Windows NT requires 40 MB. (The disk space requirements for Windows NT are different than for DYNIX/ptx because Windows NT allocates disk space differently than does DYNIX/ptx.) Additionally, you should allocate 25 MB of swap space for the CommandPoint SVM server and for each CommandPoint SVM client that will be run.


Software Installation

The CommandPoint SVM server software must be installed on the DYNIX/ptx host that you want to administer. The client software can be installed on the same host that you want to administer, on any other DYNIX/ptx host, or an a PC running Windows NT.


DYNIX/ptx Server and Client Installation

The CommandPoint SVM server and client software for DYNIX/ptx is located on the Systems Management Software CD-ROM. Other required software for use with CommandPoint SVM (including DYNIX/ptx, ptx/SVM, ptx/LAN, and ptx/TCP/IP) is located on the DYNIX/ptx V4.4.x Operating System and Layered Products Software CD-ROM. You can install all of these software products through the installation process described in the version of the DYNIX/ptx and Layered Products Software Installation Release Notes that is applicable to the version of DYNIX/ptx running on the host.


Windows NT Client Installation

The CommandPoint SVM software for Windows NT clients is located on the Systems Management Software CD-ROM.

Install the software as follows:

  1. Log in to the PC as any user. You do not have to be logged in as administrator to install CommandPoint SVM client software.

  2. Insert the Systems Management Software CD-ROM into the CD-ROM drive on the PC.

  3. Click on the Start button. From the Settings menu, click on Control Panel.

  4. Double-click on Add/Remove Programs.

  5. Click on the Install button to begin.


    ATTENTION

    During the Windows NT installation of CommandPoint SVM, you will be prompted to respond to a licensing query. In order to install CommandPoint SVM, you will need to agree to the terms of the electronic license by clicking on the Yes button, which will allow the installation to proceed. (If you answer No, the installation will stop.)

    Answering Yes allows you to install and use the Windows NT client component of CommandPoint SVM on one or more workstations that will be used for the purpose of administering ptx/SVM hosts. In this regard, the Windows NT client component is an exception to Paragraph 1.2 of the Software License Agreement.


  6. On the Run Installation Program dialog box, the CommandPoint SVM setup program CommandPointSVM.exe should be located. If not, browse to the location of this file. Make sure there is not a disk in the floppy drive. Once the CommandPointSVM.exe file is located, click Open in the Browse dialog box and then click Finish in the Run Installation Program dialog box to begin the installation.

  7. The Choose Destination Location dialog box is displayed. The default installation directory is c:\Program Files\Sequent\Cpsvm. You can change this location if you want. Once the desired location is entered, click Next to continue.

  8. The Select Program Folder dialog box is displayed. The default program folder is CommandPoint SVM. This is the name that will be listed when you select Start->Programs->Sequent. You can change this name if you want. Once the desired name is entered, click Next to continue.

  9. The Start Copying Files dialog box is displayed. This dialog box lists pertinent details about where the files will be installed. Click Next to continue. Note that it can take 10 to 20 seconds to copy the files to the PC.

  10. The Setup Complete dialog box is displayed after the files have been copied. Click OK to proceed. If necessary, click OK to close the Add/Remove Programs dialog box.

  11. Remove the CD-ROM from the drive.


Set Up Security for CommandPoint SVM Clients

After you install the CommandPoint SVM server, you can specify which users will have access. By default, only root can run the CommandPoint SVM client. To set up a list of users with permission to use the CommandPoint SVM client, add a group named cpsvm to the group file (/etc/group), NIS (Network Information Name Service) group table, or NIS+ group table on the host to be administered. The cpsvm group should include the user names of any users (including root) who require access to the CommandPoint SVM client. For example, the line defining the group cpsvm in the /etc/group file could look as follows:

cpsvm::999:root,joe,bill

If the cpsvm group does not exist, only root has access to the CommandPoint SVM client.

cpsvm is the default group name. However, you can change this name to another name by setting the vrts.server.adminGroup property to another value. To do so, edit the following line in the file /opt/commandpoint/cpsvm/vxvm/properties:

vrts.server.adminGroup=new_groupname

Ensure that the name you define in the vrts.server.adminGroup is the same name defined in the /etc/group file or NIS/NIS+ group table.


Start the CommandPoint SVM Server

Before you can use CommandPoint SVM to monitor and administer ptx/SVM you must start the CommandPoint SVM server on the host to be administered.


ATTENTION

Before you can use CommandPoint SVM to administer ptx/SVM, you must enable the volume configuration daemon (vxconfigd) and create the rootdg disk group. You will not be able to create ptx/SVM objects or perform any other ptx/SVM operations with CommandPoint SVM until vxconfigd is running and the rootdg disk group is created. The procedure to do these tasks is described in Chapter 2 of the ptx/SVM Administration Guide under "Start the ptx/SVM Configuration Daemon."


Co mplete the following steps to start the CommandPoint SVM server:

  1. Log in as superuser:

    $ su root
  2. If the currently executing shell is not a C-shell, start a C-shell:

    # csh

    Starting the CommandPoint SVM server from a C-shell, prevents the cmdserver daemon from dying when the shell that launched the CommandPoint SVM server exits. For more information, refer to cmdserver Connection Errors Occur After Shell That Started CommandPoint SVM Server Exits (250634) in the "Problem Reports" section of these release notes.

  3. Change directories to the directory where CommandPoint SVM is installed:

    # cd /opt/commandpoint/cpsvm/bin
  4. Start the CommandPoint SVM server:

    # ./cpsvmSvr.sh &

    Three lines of status messages are output to the screen (or nohup.out) almost immediately, but the remainder of the server status messages are written to a file named server.log in the /var/opt/commandpoint/cpsvm/logs directory.

    If the CommandPoint SVM server starts successfully, the server.log file should contain the following line after a few seconds:

    rebound //host:2410/vrts.remote.vrtsServer
    

Use the following command to confirm that the CommandPoint SVM server is running:

# ./cpsvmSvr.sh -q

To stop the CommandPoint SVM server, use the following command.

# ./cpsvmSvr.sh -k

This will kill all processes started by the previous invocation of cpsvmSvr.sh. To verify that all such processes are killed, run the following command and verify that only the egrep process itself is listed in the output:

# ps -ef | egrep 'vrts|cmdserver'

The cpsvmSvr.sh -q and cpsvmSvr.sh -k commands do not need to be executed from a C-shell.


Start the CommandPoint SVM Server in Read-Only Mode

The CommandPoint SVM server can be configured in a read-only mode that is useful for monitoring or browsing purposes. Read-only mode allows the administrator to view objects on the system through CommandPoint SVM, but prevents administrative actions from taking effect. This mode is enabled via the properties file (/opt/commandpoint/cpsvm/vxvm/properties). The default mode is full operational mode.


ATTENTION

You must stop and restart the CommandPoint SVM server when changing to or from read-only mode. Furthermore, when the CommandPoint SVM server is operating in read-only mode, no CommandPoint SVM clients can administer ptx/SVM on that host; they can only monitor or browse.


To start the CommandPoint SVM server in read-only mode, change the properties file (/opt/commandpoint/cpsvm/vxvm/properties) so that it contains the following line:

vrts.server.readonly=true

The user interface remains the same in read-only mode. The only difference from full operational mode is that when you try to apply a configuration change an error message is displayed indicating that the CommandPoint SVM server is operating in read-only mode. (Note that no task is registered in the Request Monitor window, so you are unable to see what command would have been executed.)

To restore the CommandPoint SVM server to full operational mode, use the following line in the properties file and then stop and restart the CommandPoint SVM server:

vrts.server.readonly=false

Start the CommandPoint SVM Client

You can use the CommandPoint SVM client to administer a local or remote host. Before you can use a CommandPoint SVM client to monitor and administer ptx/SVM you must first start the CommandPoint SVM server on the host to be administered.


ATTENTION

Only users with appropriate privileges can run CommandPoint SVM clients. Refer to "Set up Security for CommandPoint SVM" earlier in these release notes for more information.


The CommandPoint SVM client can be run from DYNIX/ptx on a Symmetry or NUMA-Q host or from Windows NT on a remote PC.

If, after the CommandPoint SVM main window appears, the Object Tree is not populated within 10 seconds or so, the server system may be having trouble finding the client system on the IP network. From the server system, try issuing the /etc/ping n1.n2.n3.n4 command, where n1.n2.n2.n4 is the client's numeric Internet address. If the ping fails, the server cannot communicate with the client.


Start the CommandPoint SVM Client on DYNIX/ptx

To start the CommandPoint SVM client on DYNIX/ptx, complete the following steps:

  1. Set the DISPLAY environment variable to the X server (typically your PC) on which you want to display the CommandPoint SVM client. For example, if your X server is w-smith.acme.com and you are using Korn shell, enter the following command at the UNIX prompt:

    # export DISPLAY=w-smith.acme.com:0.0

    Alternatively, you can set the DISPLAY environment variable in your .profile file (for Korn shell) or .login file (for C shell) in your home directory.

  2. Enter the following command to start the CommandPoint SVM client for the local host:

    $ cpsvm

    Alternatively, you can designate a remote host to administer when you enter the cpsvm command. The syntax is as follows:

    $ cpsvm remote_hostname
  3. When the Session Initiation dialog box is displayed, enter the name of the DYNIX/ptx host that you want to administer and your login and password on that host, and then click Ok. By default, the name of the local host is already entered.

    Entries for your user name and password must exist in the password file or corresponding NIS/NIS+ table on the machine to be administered. Your user name must also be included in the CommandPoint SVM group entry (cpsvm, by default).


    ATTENTION

    It can take several seconds for the Session Initiation dialog box to appear. Note that if you are running the CommandPoint SVM client on a Symmetry platform (which is not recommended), it can take even longer, possibly a minute or more.


Once the Session Initiation dialog box is displayed and you have entered your name and password, you can then click Ok to continue.

If the CommandPoint SVM server is running but not responding during startup of a CommandPoint SVM client, that client can hang. Also, the CommandPoint SVM client can sometimes become unresponsive after startup. If the client hangs, kill the cpsvm process listed in the ps output and then restart the client.

If this action does not resolve the situation, kill the cpsvm process, stop the CommandPoint SVM server with the ./cpsvmSvr.sh -k command, restart it from a C-shell with the ./cpsvmSvr.sh command, and then restart the client.


Start the CommandPoint SVM Client on Windows NT

To start the CommandPoint SVM client on Windows NT to administer a remote DYNIX/ptx host, complete the following steps:

  1. Choose Start->Programs->Sequent-> CommandPoint SVM from the Windows NT task bar. Alternatively, you can double-click on the CommandPoint SVM program icon.

  2. When the Session Initiation dialog box is displayed, enter the name of the DYNIX/ptx host that you want to administer and the login and password, and then click Ok.


    ATTENTION

    It can take several seconds for the Session Initiation dialog box to appear.


If the CommandPoint SVM server is running but not responding during startup of a CommandPoint SVM client, that client can hang. When this happens, the client might not be listed in the Applications tab of the Task Manager; instead it might be listed in the Processes tab as jrew.exe. In this case, kill the jrew.exe process and restart the client. Note that other Java-based applications such as CommandPoint Admin clients and CommandPoint Clusters clients also show up as jrew.exe processes.

If the CommandPoint SVM client should become unresponsive after startup, you can kill it just like any other Windows NT application using the Task Manager.

If killing and restarting the client does not resolve the situation, then kill the client on your PC, stop the CommandPoint SVM server on the DYNIX/ptx host with the ./cpsvmSvr.sh -k command, restart it from a C-shell with the ./cpsvmSvr.sh command, and then restart the client on your PC.


Getting Started

Once you have successfully started the CommandPoint SVM server and client, the CommandPoint SVM main window will appear. See the CommandPoint SVM User's Guide for a description of the components of CommandPoint SVM and for information on how to set up and use CommandPoint SVM.


CommandPoint SVM Is Not a Disk-Health Monitor

If a disk fails, yielding I/O errors on the disk, the situation may or may not be detected and reported by CommandPoint SVM. The CommandPoint SVM server maintains its own view of the ptx/SVM configuration, and updates that view based on event and configuration information from ptx/SVM, propagating those updates to the CommandPoint SVM clients.

In some cases, a disk failure results in no change in the ptx/SVM configuration, and thus no change in the CommandPoint SVM display. This is the case, for example, if the failed disk contains plexes only from unmirrored volumes.

In other cases, a disk failure may result in ptx/SVM configuration changes that are reported by commands such as vxprint and vxdisk list, but are not successfully communicated to CommandPoint SVM. In some such cases, the CommandPoint SVM server may pick up on the changes if you run System -> Scan Disks from the client. In other cases, the CommandPoint SVM server will not notice the changes until it is restarted.

For this reason, we recommend against using CommandPoint SVM as a monitor of disk health.


CommandPoint SVM Cannot Create Disk Groups for Cluster Failover

ptx/SVM enables you to create private disk groups that you can set up, through ptx/CTC, to fail over to another cluster node. These disk groups are assigned the failover attribute by using the vxdg -x command. However, Command Point SVM does not enable you to create or import private disk groups for cluster failover. Furthermore, CommandPoint SVM does not indicate whether a given disk group is assigned the failover attribute. It only shows that the disk group is private. You must use ptx/SVM to create disk groups for cluster failover. For more information, refer to the ptx/SVM Release Notes.


Man Pages

CommandPoint SVM on DYNIX/ptx includes the following man pages. (Windows NT does not provide man pages.) To view these man pages, use the man command at the UNIX® prompt.

cpsvm(1M)
Invokes the CommandPoint SVM GUI client application for administering ptx/SVM on a DYNIX/ptx host.
cpsvmSvr.sh(1M)
Starts the CommandPoint SVM server software on the DYNIX/ptx host that you want to administer with cpsvm.
cpsvm.properties(4)
File that describes default properties for both the CommandPoint SVM server and client.

Product Documentation

CommandPoint SVM includes online help files that are accessed by clicking the Help button in a dialog box or selecting the appropriate item from the Help menu on the main CommandPoint SVM window.

Additionally, the following documents are available on the online documentation CD or at http://webdocs.numaq.ibm.com:

CommandPoint SVM User's Guide
ptx/SVM Administration Guide

Problem Reports

This section lists open problems in this release of CommandPoint SVM. The numbers in parentheses identify the problems in the problem-tracking system.


Invalid Client Login Results in Multiple EES Messages (239610)

Every time the CommandPoint SVM server rejects a client connection (for example, due to an invalid user name or password), it logs six messages to the error event subsystem (EES). Three errors are event type 3004 and three are event type 2002.

Workaround. None. Ignore the redundant messages in the EES.


Menu Bar in Main Window Incompletely Displayed When Uninitialized Disks Are Selected (239637)

When CommandPoint SVM is run as a Windows NT application, the main window menu name may be incompletely displayed if it's long. The "Selected" menu changes names as different objects or groups are selected in the Grid or Object Tree. Some of these names are very long (for example, "Uninitialized Disks" or "Free Disk Pool"), and do not fit in the same space as "Selected."

Workaround. None.


CommandPoint SVM Online Help Cannot Be Printed From Windows NT Client (239649)

The CommandPoint SVM online help cannot be printed from a client running as a Windows NT application.

Workaround. None.


Uninitialized Disk Sizes Are Incorrectly Reported as Zero (239729)

CommandPoint SVM incorrectly reports that the size of every uninitialized disk is zero.

Workaround. Use the DYNIX/ptx diskid command.


deport/import Operations Yield Incorrect View of nopriv Disks (239745)

When a disk group that contains a nopriv disk is deported, the nopriv disk completely disappears from CommandPoint SVM's view.

When such a disk group is reimported, its nopriv disks are listed in that disk group, but their state may be incorrectly listed as Free.

Workaround. To make a nopriv disk reappear in CommandPoint SVM's view, run System ->Scan Disks. To correctly list the state of nopriv disks, restart the client.


Resize of Window Lasts for Only One Operation (239738, 239632)

If the user changes the size of a window by dragging the lower right corner, the window stays resized only until you click on an object or group. The window is then redrawn and restored to its original size.

Workaround. Change the default size of the window instead of resizing it. To change the default size of the window, select Options-> Preferences-> Geometry.

Alternatively, in the client's properties file (see cpsvm.properties(4)) set the "resizeWorkaround" property to true. This affects the label of the Selected menu.


Main Window Cursor Changes to "move" Cursor (239863)

The cursor in the CommandPoint SVM main window occasionally changes to the "move" cursor (shaped like a cross) when items in the Object Tree or Grid are clicked. Also, sometimes a wait cursor won't change back to the regular cursor until you move the cursor.

Workaround. Proceed as if it were the regular ("arrow") cursor.


Client Reports Cryptic Errors When Server Dies (239873, 241652)

If the CommandPoint SVM server is shut down or otherwise dies, its clients do not always handle the event gracefully. Your client may report no error at all until you attempt an operation that requires contact with the server. Once the client attempts such an operation, it may present a dialog with an appropriate message, or the message may be more cryptic, such as "Host connection refused." When you exit the client, you may see one or more empty dialogs titled "Error." You may even have to kill the client by hand (so to speak).

Workaround. Exit all clients before shutting down the server, if possible.


CommandPoint SVM Does Not Let You Remount a CFS Filesystem as Such (240328)

An unmounted EFS/CFS filesystem shows up as an EFS filesystem. When you ask CommandPoint SVM to mount such a filesystem, it mounts it as an EFS filesystem, neglecting to check whether you want to mount it as CFS.

Workaround. Use the mount command. If there is an entry for the filesystem in /etc/vfstab, you need only specify the mount directory.


NT Client Goes to Background (240329)

At times, typically when closing a dialog, the CommandPoint SVM Windows NT client goes to the background and then application previously in the background comes to the foreground.

Workaround. Minimize the application that has come to the foreground so that the NT client is in the foreground.


A Shared Disk Group Becomes Unshared When It Is Renamed (241346)

When a shared disk group is renamed through CommandPoint SVM (through Disk Groups->Rename), it becomes unshared.

Workaround. Rename a disk group with these two steps:

  1. Deport the disk group through Disk Groups->Deport.

  2. Import the disk group through System->Disk Group. In the "Import Disk Group" dialog, specify the name (in the "New Name" box) and check "Import as Shared."


StripeColumns and StripeUnitSize Change When maxsize Button Is Used (242920)

If the number of columns and stripe unit size have been changed with the "striped layout" option of the Create Volume dialog, these values change back to their defaults when the maxsize button is clicked.

Workaround. None.


Removing a Volume Removes vfstab Entries for All Volumes with Similar Names (242921)

If two volumes in the same disk group have names that overlap (such as vol01 and vol011), when the volume with the shorter name is removed, /etc/vfstab entries for all volumes that contain the shorter volume's name are also removed. The volumes themselves are not removed.

Workaround. Issue the grep volume_name /etc/vfstab command before removing the volume.


CommandPoint SVM May Not Detect When Quorum Is Regained (242860)

CommandPoint SVM often does not immediately detect when cluster quorum is regained, and sometimes does not detect it at all. Failure to detect that quorum is regained may cause CommandPoint SVM to refuse to attempt most operations on shared disk groups or shareable disks.

Workaround. Exit the clients and restart the server.


CommandPoint SVM NT Client Is Not Startable from the CommandPoint Admin Launcher (242997)

The CommandPoint SVM NT client is not startable from the CommandPoint Admin launcher as a Java application.

Workaround. Start it from the NT Start menu.


Sometimes CommandPoint SVM Clients Hang on NT or DYNIX/ptx (243270)

Rarely, one or more CommandPoint SVM clients connected to a particular server may hang. This can happen for either NT or DYNIX/ptx clients.

Workaround. Kill the hung client(s) and try again. If a new client also hangs, the server itself may be dead or hung. If so, kill the server and restart it using the following commands:

# ./cpsvmSvr.sh -k
# csh
# ./cpsvmSvr.sh &

Setting Environment Variables in ksh ENV File Could Cause CommandPoint SVM Problems (243408)

Setting the CLASSPATH and possibly other environment variables used by Java (such as CLASSPATH, LD_LIBRARY_PATH, SHLIB_PATH, and PATH) in your ksh ENV file could create problems with the CommandPoint SVM scripts (/opt/commandpoint/cpsvm/bin/*).

Workaround. Set environment variables in your .profile, or edit each script, adding unset ENV.


CommandPoint SVM Server Running on a Big System May Crash (244337)

To avoid CommandPoint SVM crashes on a big system, you may need to adjust a script so that Java allocates more memory for the server.

Workaround. In /opt/commandpoint/cpsvm/bin/cpsvrSvr.sh, change "java" to "java -mx40m" in the only Java command line that isn't indented (~line 126). Then restart the server.


cmdserver Connection Errors Occur After Shell That Started CommandPoint SVM Server Exits (250634)

When the cmdserver daemon is not running, any commands executed by the CommandPoint SVM client on Windows NT fail with "cmdserver connection errors." One way the cmdserver daemon dies is when the shell that launches cpsvmSvr.sh (the CommandPoint SVM server) exits.

Workaround. Launch cpsvmSvr.sh from a C-shell (csh). This prevents the cmdserver daemon from dying when the shell exits.


Documentation Additions


Print CommandPoint SVM Help Text

When you print help text from CommandPoint SVM to a file, unless you specify a full pathname for the file, the file is created in the directory /opt/commandpoint/cpsvm/vxvm/java.

Help text can only be printed from DYNIX/ptx clients, not Windows NT clients.


Monitor Access to CommandPoint SVM

Once you have set up security for CommandPoint SVM, you can monitor access to it by reviewing the contents of the access log file on the CommandPoint SVM server host. The access log file contains information about all client connections (who is logging in). By default, the access log file is located in the directory /var/opt/commandpoint/cpsvm/logs.

The access log file contains entries similar to the following:

Fri Jan 23 10:22:17 PST 1998: user xyz login succeeded 
Fri Jan 23 10:59:52 PST 1998: user xyz login failed with error 
"User password invalid"

Entries for failed access may be logged multiple times. This is due to a security requirement and is not an error.

Additionally, CommandPoint SVM logs these same client-connection messages to ptx/EES. Note that CommandPoint SVM logs other messages, for example server start up and shut down messages and internal errors, to ptx/EES as well.


New "Usage Type" Control in Create Volume Dialog

A new "Usage Type" control has been added to the Create Volume dialog (right below the Size box). A volume's usage type can be either:

fsgen
For filesystems.
swap
For primary swap
gen
For other uses, such as raw database components or secondary swap.


Do Not Modify Font Settings if Already Modified for eXceed

If you followed the procedures for modifying font settings described in the CommandPoint Admin V4.4.0 Overview and Release Notes, then do not configure fonts directly from CommandPoint SVM (via Options->Properties->Font). Doing so will cause the font sizes to increase.