| Netra CT Server Release Notes |     |
| Netra CT Server Release Notes | |
|
Netra CT Server Release Notes |
The Netra CT Server Release Notes contain important and late-breaking information about the Netra
CT 410 and CT 810 servers, including:
The most recent versions of the Netra CT 410 and CT 810 server documentation are available at:
http://www.sun.com/products-n-solutions/hardware/docs/Servers/
The following known issues (priorities 1-3) exist in this release of the Netra CT Server hardware and software.
|
Netra CP2160 and Netra CP2140 topology should have PMC slots. |
||
|
Acceptable_Fru_Types field is not readable for MOH on alarm card until alarm card is reset. |
||
|
For MOH on host, iftable does not update to include newly created interfaces. |
||
|
Alarm card MOH does not get attribute change for UpperThresholdNonCritical. |
Connect to the host in drawerview mode to receive the correct attribute change notification. |
|
|
Provide a seamless interface between the MOH software and the Netra High Availability Suite (NHAS). |
||
|
The RoHS Netra CP2140 board resets after returning from OpenBoot |
Do not use the break command to stop Solaris OS to get to the OBP prompt. If the system is stopped in this manner, executing a go command may cause the board to reboot. |
|
|
Solaris 9 FCS Operating System fails to probe correctly the new RoHS DAT Tape HP72. |
Apply the patches listed in TABLE 5. |
|
|
Pinging the alarm card while it is resetting causes MCNet driver to panic on the Netra CP2140 host board. |
When resetting the alarm card, make sure there is no traffic across the McNet interface. Do this by bringing down the mcn0 interfaces on the host board in the chassis. |
The following paragraphs describe enhancements and new features.
As of this release, this equipment complies with the Restriction of Hazardous Substances (RoHS) directive 2002/95/EC.
Beginning July 1, 2006, Directive 2002/95/EC, of the European Union (EU), restricts the use of certain hazardous substances in electrical and electronic equipment. Those substances are Lead, Mercury, Cadmium, Hexavalent Chromium, PBBs (polybrominated biphenyls) and PBDEs (polybrominated diphenyl ethers). Netra CT 410/810 servers are now compliant with the EU RoHS mandate.
For additional information, please contact your Sales Representative or, if appropriate, your OEM.
Previously, DVD (digital video disk) removeable media modules (RMMs) were installed during manufacturing and shipped as part of the standard configuration. Now, the DVDs are no longer included as part of the standard configuration, but are available as X-option components.
The DVD drive is RoHS compliant. The DVD drive is a Toshiba TS-H-352C, which is an IDE drive. The previous DVD drive was a SCSI drive.
Because the host interface is a SCSI interface, an adapter card from ACARD Technologies Corporation is used to convert from the SCSI to IDE interface. The functionality is transparent to the end user.
The DAT (digital audio tape) drive is now RoHS compliant and available as an X-option. The DAT drive is a 16 bit SCSI DAT-72 (72GB) standard tape drive. The media that works with this tape drive is DAT-72 tape. Be advised that Digital Data Storage (DDS), DDS-1, DDS-2, and DDS-DC cartridges are not supported in DAT-72 tape drives. DDS3 and DDS4 media are backward compatible.
|
Note - The media adaptor modules (MAMs) for the DVD and DAT drives are different in RoHS systems. |
The following known issues exist in the current release of the Netra CT 410 and Netra CT 810 documentation. The changes described here will be documented in the appropriate documentation for the next major release.
A command for collecting alarm card debugging output to a log is available. This command outputs the name of the key process that exited and caused the alarm card reset, due to the process exit. The output includes a date stamp. This command will be documented in the Netra CT Server System Administration Guide with the next major release.
The command requires administrator (a) permissions:
In addition to the command, an option to reset the debug log is provided:
As documented in the Netra CT Server System Administration Guide, limitations precluded you from including userpassword as an interactive command in rsh. Now both userpassword and mohuserpassword commands are allowed as interactive commands in rsh.
|
Note - When using either command in rsh, a slight change in the command syntax is necessary. |
Use the following syntax to use userpassword or mohuserpassword commands in rsh:
where mcnet-ip-addr is the alarm card MCNet IP address.
Example: rsh 192.168.13.8 -l userpassword
After the command is accepted, users will be prompted for username and password.
Commands and associated software provide increased security for managing Managed Object Hierarchy (MOH). System administrators can separate MOH and CLI user accounts to better control access to the console and client.
The new commands are mohuseradd, mohuserpassword, mohuserperm, mohuserdel, and mohusershow. Use these commands to add user accounts, assign user passwords, manage permissions, delete user accounts, and view all MOH users.
|
Note - A maximum of five MOH user accounts can be established. |
MOH accounts are set up and managed from the CLI by a CLI user who has admin (a) permissions. The help command includes the new commands under the Administration heading.
For information about administering CLI accounts on the alarm card, refer to the Netra CT Server System Administration Guide. For information about administering MOH accounts using the new commands, see the following information.
For MOH security to be in effect, the mohsecurity flag must be enabled (value is true). You can verify that it is enabled by using the showmohsecurity command.
|
2. Set up, modify permissions, or delete user accounts as follows:
For username and password restrictions, refer to the Netra CT Server System Administration Guide.
By default, new accounts are created with read-only permission. Permission levels can be changed using the mohuserperm command.
|
Note - Users can have READONLY (r) or READWRITE (rw) permissions |
|
You can display information for a single user (by entering the username) or for all users.
|
Note - admin permission is not required to use this command. |
The Managed Object Hierarchy (MOH) software generates SNMP traps when memory errors are detected on Netra CT 410 and Netra CT 810 servers. The cediag tool analyzes memory error events and makes recommendations based on the enhanced DIMM replacement policy. The MOH ctmgx agent interacts with the cediag tool periodically to monitor memory errors and generate appropriate traps.
Previously, the memory module from the CPU kernel reported errors to a log file (/var/adm/messages), and users had to monitor the log file and take necessary action.
Now, when one or more of the DIMM management rules are broken, an SNMP trap is generated. Both advice and findings strings are sent with the SNMP trap. In addition to the usual information (such as time stamp, sysUptime, Timeticks, etc.), the traps provide new information relating to memory errors.
The polling period is configurable using the ctmgx.cediag.period parameter in the ctmgx.conf file. The default value is the time period in milliseconds at which the cediag status is checked.
Be careful when changing the default time period; setting it too low could back the system up with too many cediag processes.
The cediag default path is hardcoded to:
/opt/SUNWnetract/mgmt2.0/etc/ctmgx.conf
For systems that have not been upgraded and thus lack the required cediag tool, the MOH agent will check for the cediag tool upon startup, and enable or disable the enhancement accordingly.
The maximum number of telnet connections to the alarm card has changed from 16 to 12. If you attempt more than 12 telnetd connections, telnetd exits.
This change will be documented in the appropriate documentation for the next major release.
Starting with this release, the green Power LED on the system status panel for the alarm card will go OFF and the amber Okay to Remove LED light will be ON when it is okay to remove the alarm card. The change to the green Power LED status was made so that the behavior matches the behavior of all other card types. This change provides a consistent status indicator for technicians to know when it's okay to remove any of the cards.
|
Caution - Wait until the green Power LED stops blinking and is OFF before removing an alarm card. The amber Okay to Remove LED must be ON. |
This change affects the following documentation, which will be updated in a subsequent documentation release:
CT Server Product Overview
CT Server Service Manual
CT Server System Administration Guide
Although some users configure alarm cards using Basic Hot Swap (BHS) mode, this technique is not recommended. The problem with using BHS for configuring alarm cards is that after a host CPU reboot, alarm card watchdog reset, or graceful shutdown via the reset ac command, the alarm card comes up in a BHS disconnected or unconfigured state. All of the BHS configuration data is reset. The system administrator then must manually configure the card for BHS. Also, this scenario applies to intelligent CPUs such as satellites.
When using BHS mode with non-intelligent cards, the BHS configuration data loss after a reset is not an issue; you can use whatever mode you like.
To Reconfigure After a Reboot, Reset, or Shutdown
In case you configured an alarm card using BHS and need to reconfigure the BHS data on the alarm card, enter the following commands at the host as root user:
where value n is either a 1 for a Netra CT 410 or an 8 for a Netra CT 810. For more information about these commands, refer to Netra CT Server System Administration Guide For the Netra CT 810 Server and Netra CT 410 Server.
Solaris 9 FCS Operating System (Solaris 9 FCS OS) with patches is required for using this release of the software for the Netra CT810 and Netra CT410 servers.
To obtain the Solaris 9 FCS OS, contact either your sales representative or field service technician. This OS version is available only by special order (part number SOLZS-09AC9AYM) through a qualified Sun representative.
Solaris 9 OS patches can be downloaded from SunSolve web sites as detailed in Patches to Download and Apply.
For this release of the software, the Netra CT CPU board firmware must be at the following versions:
To display the current firmware version, use the .version command at the OpenBoot PROM prompt.
If you do not have the correct versions of the firmware, go to the SunSolveSM Web site, http://www.sun.com/sunsolve, and download the most recent versions of the following firmware patches:
Refer to the Readme file in the patch for any special installation instructions, and to the Netra CP2140 Technical Reference and Installation Manual (816-4908) or Netra CP2160 Technical Reference and Installation Manual (816-5772) for instructions on upgrading the firmware.
The Netra CT server alarm card firmware must be at the following versions:
To display the current version, use the version command at the alarm card CLI prompt. If you do not have the correct version of the firmware, go to the SunSolve Web site, http://www.sun.com/sunsolve/point, and download the following firmware patch: 116654.
Refer to the Readme file in the patch for any special installation instructions, and to the Netra CT Server System Administration Guide (816-2483) for instructions on upgrading the firmware on the alarm card.
|
Note - These instructions apply to a new installation or to an upgrade from any previously released version. The base Solaris |
This section provides information on the patches that you must download from the SunSolve web sites for the Netra CT server and instructions on how to apply these patches. These instructions are part of the Netra CT software installation procedures that are documented in the Netra CT Server Installation Guide (816-2481). At a particular point in the installation procedure, you are asked to perform these tasks.
There are two types of patches to download:
1. Download the most recent versions of the patches listed in TABLE 4.
1. If you are using a DAT drive in the system, download the patches listed in TABLE 5.
2. Move the patch zip files you downloaded (listed in TABLE 4 and, if applicable, in TABLE 5) into the image_directory/Solaris_9/Patches directory, where image_directory is the path to the directory where the Solaris 9 install image is stored.
Refer to the Netra CT Server Installation Guide for more information on the image_directory location.
3. Perform an unzip on all of the patches that you downloaded.
4. Apply the patches as follows.
Procedures for installing patches for the Netra CT vary depending upon the system you are applying them to.
a. If you are applying patches to a boot disk (if you installed the Solaris OS onto an internal or external hard drive), go to Applying Patches to a Boot Disk.
b. If you are applying patches to a network installation image for diskless clients, go to Applying Patches to a Diskless Service.
Following are instructions for installing patches. For additional information and detailed instructions for completing the software installation process, refer to the Netra CT Server Installation Guide.
1. Perform a patchadd for each of the following patches in the following order:
2. If you are using a DAT drive in the system, apply the patches listed in TABLE 5.
4. Refer to instructions in the Netra CT Server Installation Guide to complete the software installation procedures for a boot disk.
1. Change directories to the /usr/sadm/bin directory.
2. Use the smosservice patch command to apply the patches to the diskless service in the following order:
|
Caution - For patch 114349, this patch replaces patch 116100. If patch 116100 is on the system, remove it using the patchrm command before applying 114349. |
where root_password is the root password of the server and image_directory is the Solaris 9 installation image directory. You must add an additional -m -U option when you install the last patch to the installation image.
3. Manually apply the following patches:
where image_directory is the Solaris 9 installation image directory.
4. Enter the following commands:
5. Refer to instructions in the Netra CT Server Installation Guide to complete the software installation process.
| Netra CT Server Release Notes | 817-0939-17 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Add and Manage MOH User Accounts
