Important Information About the Sun Fire V445 Server
These product notes contain important and late-breaking information about your Sun Fire V445 server.
For additional information, read the release notes which come with your Solaris documentation, as well as the latest Solaris 10 Sun Hardware Platform Guide. Also, check the documentation web page for any additional supplements to this book.
The most up-to-date information is posted at http://www.sun.com/documentation/
This document contains the following sections:
Complete the following to register your system and use the Sun Update Connection to obtain the latest Solaris OS patches.
1. Copy the /usr/lib/breg/data/RegistrationProfile.properties to /tmp/myreg.profile directory.
2. Edit the /tmp/myregprofile to add your user name, password, and, if necessary, a network proxy.
3. Register your system by typing:
4. Obtain the correct patches for your system by typing:
5. Display a list of patches to be installed by typing:
6. Install the downloaded patches by typing:
7. For more information about the Sun Update Connection, see your Solaris OS documentation.
To download the latest software patches, see the Sunsolve web site at http://sunsolve.sun.com.
The following minimum revision Solaris operating system (Solaris OS) patches are required for a fresh Solaris 10 6/06 installation on the Sun Fire V445:
The following minimum revision patch is required for SunVTS 6.2:
The minimum supported release of SNMP Management Agent is SNMP Management Agent 1.4 Update 2. This release will be available no later than September 12, 2006.
The following bugs and defects affect the Sun Fire V445 server hardware or components.
Normally, the ALOM system controller initializes as soon as the system is connected to a live AC circuit. However, under some conditions, the ALOM system controller may fail to boot following a power interruption or during AC power on. This will prevent you from powering on the system. (Issue fixed in ALOM 1.6.1).
To correct this issue, disconnect the system from AC power, wait ten seconds, and reconnect the system. The ALOM system controller boots normally, and you can power on the system.
An attempt to power on the system may fail with false power supply errors. (Issue fixed in ALOM 1.6.3).
To correct this issue, reset the ALOM system controller and reissue the poweron command.
Type the following:
The ALOM showenv command correctly indicates a power supply fault, but the command output does not correctly display the status of the power supply indicators in the affected power supply. (Issue fixed in ALOM 1.6.1).
sc> showenv ... ------------------------- SC Alert: PSU @ PS3 has FAULTED. -------------------------------------------- Power Supply Indicators: -------------------------------------------- Supply Active Standby Service -------------------------------------------- PS0 ON ON OFF PS1 ON ON OFF PS2 ON ON OFF PS3 UNKNOWN UNKNOWN OFF
However, the power supply status is correctly displayed:
---------------------------------------------------------------- Power Supplies: ---------------------------------------------------------------- Supply Status Underspeed Overtemp Overvolt Undervolt Overcurrent ---------------------------------------------------------------- PS0 OK OFF OFF OFF OFF OFF PS1 OK OFF OFF OFF OFF OFF PS2 OK OFF OFF OFF OFF OFF PS3 FAULTED ON ON ON ON ON
Check the physical power supply status indicators when servicing the system.
The ALOM showkeyswitch command does not report the correct state. (Issue fixed in OPB 4.22.19).
To make sure that the keyswitch variable is set as desired, use the setkeyswitch command. See the ALOM documentation for more information about the setkeyswitch command.
Some system keyboards are unresponsive after the system is brought down to the ok prompt under the following conditions:
All keyboards work correctly when connected to the back panel USB port. (Issue fixed in Solaris 10u4_01).
The following PCIe and PCI-X properties are not captured in a device node dump (using the .properties command):
There is no loss of device functionality.
Systems equipped with the XVR-2500 (P25) frame buffer cards sometimes indicate that a correctable error has occurred. This error is harmless, and does not compromise data integrity.
To correct this issue, append the following lines to the /etc/system file:
Reboot the system to implement the changes.
Sometimes after adding these lines to the /etc/system file, the following message appears during Solaris boot:
If you experience this error message, delete the final line in the /etc/system file (set pcie_expected_ce_mask=0x11C1), and reboot the system.
If your system resets repeatedly, do the following:
1. Change the system keyswitch variable:
2. Reboot the system.
(Issue fixed in OBP 4.22.13).
On rare occasions, the console may become unresponsive following a boot -v command under certain configurations.
If your console becomes unresponsive following a boot -v command, use the rlogin command to access and reboot the system.
If you use the asr-disable command on empty DIMM slots, the empty DIMM slots appear as extra entries in prtdiag. For example:
Do not use the asr-disable command on empty DIMM slots. Read the section, “About DIMMs” in the Sun Fire V445 Server Administration Guide to determine proper DIMM addresses.
The picl subsystem does not acknowledge a fan tray removal during a hot-swap procedure.
The ALOM system controller accurately acknowledges fan tray removal and insertion events, and can be used in place of the picl subsystem to obtain fan tray status. (Issue fixed in Solaris 10u4_01).
To obtain accurate fan tray status via the picl driver, restart the picl subsyste:
|Caution - To retain N+1 redundancy, working fan trays must be installed in all fan tray slots. If you cannot install a replacement fan tray immediately, keep a failed fan tray in its slot until a replacement fan tray is available.|
The picl subsystem should report power supply status (temperature, current, voltage and indicator state) after a hot-swap procedure. However, it only reports that a power supply is present.
In addition, during a hot-swap event, the prtdiag command and SunMC should report that a power supply has been removed. Instead, they report that the power supply affected is still present. (Issue fixed in Solaris 10u3_07).
To obtain accurate power supply status, restart the picl driver:
Though failed fan trays are reported by the picl subsystem and by ALOM, the Sun Management Center (SunMC) software does not report failed fan trays.
Use the picl subsystem and the ALOM software to monitor fan trays. Investigate any Service Required alerts using the system status indicators or ALOM software. You can also use SunMC to diagnose a failed fan tray if you monitor fan tachometer settings in conjunction with the ALOM software. (Issue fixed in Sun Managment Center 3.6.1).
When updating OpenBoot PROM from 4.22.11 to a later version, the update fails with the following error:
(Issue fixed in OPB 4.22.19).
If you encounter this error, set the keyswitch variable to normal.
1. Switch from the system console to the ALOM system controller prompt. Type:
2. Change the keyswitch system variable to normal. Type:
3. Return to the system console to update the OpenBoot PROM image. Type:
Continue with the OpenBoot PROM update. (Issue fixed in OBP 4.22.19).
When a root user attempts to use the time of day (TOD) device to schedule an automatic power-on event, the system will panic. Automatic power on is not supported on the Sun Fire V445. Do not use the TOD (powerd) feature. (Issue fixed in Solaris 10 u3_07).
The Customer Data Record timestamp in each system component should contain the date of the most recent update to the Customer Data Record. This field is initialized to an invalid value by the manufacturer, which is displayed either as a UNIX zero date or with an error message. The Solaris prtfru and ALOM showfru utilities display invalid dates in this field until the Customer Data Record timestamp is changed. For example:
This field displays a meaningful value after the Customer Record is updated. (Issue fixed in Solaris 10u4_01).
The following bugs and defects affect the Sun Fire V445 server software, or the Solaris operating system (Solaris OS) release supporting this server.
This bug can occur under heavy load on systems being used as NFS/RDMA servers over an infiniband device. If you are using the Sun Fire V445 as an NFS server, use the IP over Infiniband protocol. See your Solaris OS documentation for more information about how to configure IP over Infiniband.
When using the format utility in Solaris 10 U2, the following error occurs:
This error can be ignored.
You can avoid this warning message by typing the following command before using the format utility:
Under heavy load, Intel Northstar dual-Gigabit Ethernet cards experience errors, such as the following:
(Issue fixed in Solaris 10u3).
To fix this error, append the following line to the /kernel/drv/e1000g.conf file:
Initialization link errors may occur in systems equipped more than one bge device installed and configured for Internet protocol multi-pathing (IPMP). The system erroneously reports an IPMP link failure before all of the bge devices have come online.
Wait a few seconds after system startup before initializing the IPMP subsystem (in.mpathd). (Issue fixed in Solaris 10u3_07).
The cfgadm command shows the secondary disk as unconfigured after creating a RAID volume. This erroneous secondary disk line does not appear after rebooting the system, and the RAID array functions normally.
To avoid this error, create RAID volumes using the raidctl command, or restart the picl subsystem.
On rare occasions, the system panics under severe stress when equipped with the Intel Northstar dual-Gigabit card running the e1000g driver. (Issue fixed in Solaris 10u3_01).
You can avoid this error by adding the following line to the /etc/system file:
Solaris 10 systems that have the e1000g driver configured for use with the Intel Gigabit NIC might experience data integrity issues during periods of high stress on the network interfaces.
When the system is under high network stress, application data could be corrupted. It can only be detected by the application or the user when unexpected application data is seen. (Issue fixed in Solaris 10u3_09).
You must determine that the e1000g driver is configured. If the driver is configured, you must then add an entry to the /etc/system file to check the data integrity.
1. Use the uname(1M) command to identify the version of the Solaris OS running on the server:
The output should read 5.10.
2. Use the ifconfig(1M) command to verify that an e1000g interface is configured.
The output should read e1000gX where X is the number of the interface (for instance, 0, 1, or 2).
3. Add the following line to the /etc/system file.
A patch is being developed. After you install the patch, the entry in the /etc/system file should be removed. If not removed, the system performance will be lower.
When the auto poweron feature is enabled and AC power is restored to a system running OpenBoot PROM revision 4.22.11, POST might encounter read errors. (Issue fixed in OBP 4.22.23).
To avoid this bug, chose one of two options; disable the auto poweron feature in ALOM, or install Sunsolvesm patch 121680-02.
To disable the auto poweron feature in ALOM, type this command:
If you chose to install the Sunsolve patch, you must also change the diag-level or verbosity parameters to something other than the default. For example, from the Openboot console prompt, type:
Pages 5 and 53 of the Sun Fire V445 Server Installation Guide (819-3743) incorrectly states that the rackmounting kit supports installing the server in to a 4-Post EIA-compliant rack up to 34 inches in depth. The standard rackmounting kit supports installation of the server in to a 4-Post EIA compliant rack up to 31 inches in depth. Rackmount kits that support racks depths from 31 to 34 inches are available by request.
Page 8 of the Sun Fire V445 Server Administration Guide (819-3741) omits the following new feature:
Table 4-2 on page 79 of the Sun Fire V445 Server Administration Guide (819-3741) incorrectly lists the PCI slot capacities of Slot 6 and Slot 7. The correct capacities are:
Slot 6 x8 (wiredx4)
Slot 7 x8 (wiredx4)
Pages 120, 127, 128, 172, 173, 177, 179, and 188 of the Sun Fire V445 Server Administration Guide (819-3741) contain sample data that refers to the Alternate SAS controller configuration.
Page 111 of the Sun Fire V445 Server Administration Guide (819-3741) includes a procedure to enable the hardware watchdog mechanism using the set watchdog_enable command. This manual procedure is no longer necessary because Solaris automatically performs this procedure during the boot process.
Forcing the set watchdog_enable=1 command generates an error message, but does no harm to the system. Solaris will properly configure this parameter later in the boot process, and the system will function normally.
Pages 2, 3, 29, 44, 46, 78, and 99 of the Sun Fire V445 Server Administration Guide (819-3741) provide incorrect information about the Sun Fire V445 server serial management port (TTYA). This port is a dedicated non-POSIX compliant serial port that does not support modems.
The Sun Server Site Planning Guide provides background information and methodology for configuring and equipping your data center to support Sun servers. Use it in conjunction with the Site Planning Data Sheet which comes with your server to calculate power, cooling, airflow and maintenance requirements for your server.
The Sun Server Site Planning Guide is available on the Sun documentation web site at http://www.sun.com/documentation.
Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, UltraSPARC, OpenBoot, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
U.S. Government Rights--Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, États-Unis. Tous droits réservés.
Sun Microsystems, Inc. possède les droits de propriété intellectuels relatifs à la technologie décrite dans ce document. En particulier, et sans limitation, ces droits de propriété intellectuels peuvent inclure un ou plusieurs des brevets américains listés sur le site http://www.sun.com/patents, un ou les plusieurs brevets supplémentaires ainsi que les demandes de brevet en attente aux les États-Unis et dans d’autres pays.
Ce document et le produit auquel il se rapporte sont protégés par un copyright et distribués sous licences, celles-ci en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.
Tout logiciel tiers, sa technologie relative aux polices de caractères, comprise, est protégé par un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produit peuvent dériver des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux États-Unis et dans d’autres pays, licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, Java, AnswerBook2, docs.sun.com, UltraSPARC, OpenBoot, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux États-Unis et dans d’autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux États-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.
L’interface utilisateur graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox dans la recherche et le développement du concept des interfaces utilisateur visuelles ou graphiques pour l’industrie informatique. Sun détient une license non exclusive de Xerox sur l’interface utilisateur graphique Xerox, cette licence couvrant également les licenciés de Sun implémentant les interfaces utilisateur graphiques OPEN LOOK et se conforment en outre aux licences écrites de Sun.
LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DÉCLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA LIMITE DE LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L’ABSENCE DE CONTREFAÇON.