Update using Tools and Drivers CD v1.3 before you update to v1.4 firmware.
|
Sun Fire X2100 M2 Server Product Notes |
This document contains late-breaking information and issues for the Sun Fire X2100 M2 server.
The following issues are covered in these product notes:
The following table provides information on service support, documentation and supported operating systems. Updated information for each is available at the corresponding URL.
An ISO image of the Tools and Drivers CD v1.7.0 is available online for download at:
http://www.sun.com/servers/x64/x2100/downloads.jsp
The following is a list of new features available in the Tools and Drivers CD v1.7.0:
The following sections describe the changes resulting from the latest firmware update:
The following table lists the BIOS and SP versions available on each release of the Tools and Drivers CD:
The following table describes what happens when you update the BIOS/SP remotely (not booting from the Tools and Drivers CD locally). Test the update on one system before performing a remote multiple system update:
Use the option to preserve CMOS settings when downgrading firmware from release v1.4 to an earlier version, see “Firmware Update Options” on page 9.
| Note - Some downgrade paths might require user intervention due to checksum errors. Always test the downgrade on one system before performing a remote multiple system downgrade. |
During the update from BIOS v1.2 to BIOS v1.4, a checksum error occurs which requires user intervention. This interferes with scripted remote updates of multiple systems.
Update using Tools and Drivers CD v1.3 before you update to v1.4 firmware.
The SP/BIOS flash process includes an “Update Successful” message. This message signals the end of the SP flash activity only. At this point in the process the BIOS has not been flashed, and premature termination of the process (for example, a manual reboot) will result in BIOS corruption. Review the sequence below to avoid accidentally corrupting the BIOS:
| Note - Before writing a script to flash the BIOS/SP remotely, observe the sequence in real-time and test the script on a single system before updating all systems. |
1. SP begins the flash process.
2. SP finishes the flash process.
3. CLI returns an Update Successful message.
4. The system reboots and the BIOS begins the flash process.
5. The BIOS flash process finishes.
This section contains SP recovery procedures for the Sun Fire X2100 M2.
This procedure will be added to a future revision of the Service Manual.
|
1. Download the Tools and Drivers CD ISO image file from the Sun Fire X2100 M2 download site.
http://www.sun.com/servers/entry/x2100/downloads.jsp
2. Mount the ISO image or burn a CD using the ISO image file and insert the CD into a CD/DVD drive.
3. Insert the bootable USB device into the USB port.
4. Copy all the files from the BMCrecovery directory on the Tools and Drivers CD or mounted ISO image to the bootable USB device.
5. Remove the AC power from the server, and, if necessary, remove the server from the rack.
6. To access the server motherboard, remove the server top cover.
7. Using a jumper cap, short the pins of jumper J34.
J34 is located on the server motherboard between CPU0 and the fan.
8. Set up the server with a KVM so that you can respond to server POST messages.
9. Apply AC power to the server.
10. If the server has a CD/DVD drive, remove CD/DVD media from the drive.
11. Insert the DOS-bootable USB device into the server’s USB port.
12. Power on the server and enter the BIOS Setup Utility.
13. To enter the BIOS Setup Utility, watch the output for the BIOS prompt and press F2 when prompted.
The BIOS Setup Utility main screen appears.
14. Set the USB device as the first or primary boot device.
15. Save and exit the BIOS Setup Utility.
The server boots from the USB device and a DOS prompt appears.
16. At the DOS prompt, enter the following command:
17. When the flash process finishes, remove the AC power from the server and the jumper cap from jumper J34.
18. Prepare the server for operation and boot the server.
When performing a firmware update or downgrade of both the BIOS and the SP, using the web GUI or the CLI and the Tools and Drivers CD v1.6, the SP update succeeds, but the BIOS update might fail. The BIOS remains functional, but is not updated. This issue might be related to the BIOS COM port setting. The COM port must be set to COM1 and not COM2.
This issue is resolved with Tools and Drivers CD v1.7.0.
Update the firmware using the Tools and Drivers CD v1.7.0 to resolve this issue.
Use the BIOS Setup Utility to set the COM port to COM1 before performing a firmware update.
The console does not start when the external COM port is used to access the SP.
Set the COM port to COM2 as the default in the BIOS Setup Utility.
The firmware update options in the ELOM have changed. The BMC version included on the Tools and Drivers CD v1.3 contains two methods for updating the firmware remotely. You can clear or preserve CMOS. The default is set to Clear CMOS. The default setting avoids BIOS checksum errors, and facilitates remote updates.Both methods are available in the web GUI and the CLI and are described below.
| Note - This issue pertains to firmware contained on the Tools and Drivers CD v1.3. Sun recommends that you always update your server to the latest version of firmware. |
Changes in the web GUI include two additional options in the Control -> Firmware Update screen. Both methods described below preserve the SP settings. The options are:
Method B is recommended for users that would like the firmware to preserve the user’s customized BIOS settings.
Use the set command and the UpdateMethod target before updating the BIOS CMOS:
To clear the system BIOS CMOS and load optimized defaults, use:
To update the firmware and preserve the system BIOS date, use:
This section contains the following operating systems-related issues:
This section contains issues that apply to Sun Fire X2100 M2 servers running the Solaris 10 operating system.
|
“Baud Rates for Installing the Solaris OS Using ssh console” on page 10 |
|
“Some KVM Switches Get Out of Sync Following Solaris Installation” on page 12 |
To install the Solaris OS on ttyb using ssh console, use the web GUI to set the internal serial port baud rate to 9600. In the BIOS, set the COM2 baud rate to 9600. To be able to set the internal serial port baud rate, you must have updated your server to BIOS v3A16 and BMC v3.09 (Tools and Drivers CD v 1.5).
In order to start the Solaris Xserver, you must connect all of the configured network interface cards (NIC) to the network. If a NIC is not configured, you do not need to connect it.
During initialization, Solaris might fail to properly clear the RX_EN register. As a result, TCP/UDP connections via the nge ports will fail.
Install patch #122530-06, which requires patch #118855-03.
Reconfigure the system immediately after installing the patches. Both patches are available at http://www.sun.com/sunsolve. Use Patchfinder to locate the patch.
Installing BMC firmware v3.09 strengthens system security and is a recommended update. The X2100 M2 is susceptible to unauthorized access when the BMC firmware is at v2.91. Security vulnerability is greatly reduced by upgrading to BMC v3.09.
Update BMC (SP) firmware using Tools and Drivers CD v1.5 or higher.
For more information, see “Security Vulnerability in SP Email” on page 18.
The Solaris 10 6/06 and 11/06 OS distributions have a telnet security vulnerability issue.
A patch is available on the Tools and Drivers CD v1.4.
When installing Solaris 10 6/06 in a rack with a KVM switch, the monitor might get out of sync when the Xserver starts to log into the OS.
Install Solaris in text mode, then do the following:
a. Run the install.sh script from the Tools and Drivers CD.
Running install.sh resolves the issue, as it installs the updated AST2000 VGA driver. See the Sun Fire X2100 M2 Server Operating System Installation Guide, 819-6592, for additional instructions on running the install.sh script for Solaris.
Use KVMS over IP with the Embedded Lights Out Manager (ELOM) GUI.
See the Embedded Lights-Out Management Administration Guide, 819-6588, for additional instructions on KVMS over IP.
Install Solaris in GUI mode, then do the following:
a. Boot failsafe or kill the Xserver prior to starting.
b. Run the install.sh script on the Tools and Drivers CD.
See the Sun Fire X2100 M2 Server Operating System Installation Guide, 819-6592, for additional instructions on running the install.sh script for Solaris.
The following issue applies to Sun Fire X2100 M2 servers running the supported Red Hat or SUSE operating systems.
|
“System Halts With AMD-Based Servers Running 64-bit RHEL Versions 4 - 4.5” on page 13 |
On AMD-based servers running 64-bit RHEL versions 4 through 4.5, the system might hang because of issues related to the management of process memory data. This problem occurs when running x86 64-bit RHEL 4 on an AMD processor that supports greater than 40-bit physical addressing. See the Red Hat Linux knowledge base and article #11696 at:
http://kbase.redhat.com/faq/FAQ_85_11696.shtm
Red Hat strongly recommends that you update to 4.6 or to the 4.5 errata kernel as soon as possible.
When typing characters on a Linux operating system running on the Sun Fire X2100 M2 server, the keystokes will auto-repeat. You can use the following workaround or install an updated kernel from Red Hat, see RHSA-2006:0710-7 at:
http://rhn.redhat.com/errata/RHSA-2006-0710.html
1. Select Preferences - > Keyboard from the desktop menu.
2. Uncheck the selection: keyboard repeats when key is held down.
The following issues apply to Sun Fire X2100 M2 servers running the supported versions of the Widows OS:
If you are running the web GUI on Windows with an Internet Explorer browser and the web GUI times out, or you log out with the remote console window still open, a dialog box will appear stating:
If remote console is opened, it will be closed. Click OK.
Clicking OK will not close the remote console window. You will need to close the window manually.
This section contains issues that apply to Sun Fire X2100 M2 server hardware.
|
“Baud Rate for the Internal Serial Port and COM2 Must be the Same Value” on page 14 |
With the update available on the Tools and Drivers CD v1.5, BIOS v3A16 allows you set the COM2 baud rate, and BMC v3.09 allows you to set the internal serial port. The default baud rate setting for both COM2 and the internal serial port is 9600. If changed the setting for both these values must match.
Please note the following issues regarding PCI Express (PCIe) card installation.
To identify an early version of the riser assembly, check if the riser assembly is protruding out the back of the system beyond the top cover, approximately
2.5 mm.
The front USB ports will only support a 3-meter cable to an attached device.
Support for Nvidia Quadro Plex is available using the Nvidia Quadro Plex Interface Card (QPIC) and the x16 PCIe card and riser assembly. A BIOS option is available to direct the video to either the on-board AST2000 or the Nvidia PCIe card. The video will default to the AST2000 until this BIOS option is changed.
|
Caution - When changing the BIOS option to direct video to the PCIe card, all remote access to the system console is temporarily lost. |
|
1. Enter the system BIOS by pressing F2 at the Sun splash screen.
2. Select Advanced tab -> Onboard Device Configuration -> Primary Graphics Adapter.
3. Change to PCI Express, and hit F10 to save changes.
You can use a system BIOS option to set the write cache for the LSI card to Enable or Disable. By default the option is Disable.
|
|
Caution - Enabling the write cache increases the risk of corrupting data when an unexpected power outage occurs. However, enabling the write cache will improve the install/rebuild performance. |
|
1. Enter the system BIOS by pressing F2 at the Sun splash screen.
2. Select Advanced -> Onboard Device Configuration -> LSI 3041E disk cache.
3. Change to Enable, and press the F10 key to save changes.
The following issues apply to the Sun Fire X2100 M2 Server Embedded Lights Out Manager (ELOM) Service Processor (SP):
Information about the ELOM is available in the Embedded Lights Out Manager Administration Guide for the Sun Fire X2100 M2 and Sun Fire X2200 M2.
Direct Reading of the SPD memory is not supported in IPMItool 1.8.9. Using the IPMItool fru print command will result in a return of incorrect memory information. An updated IPMItool utility is required for this to work properly. Software support has been added on the server.
The BMC web GUI has been redesigned for ease of use and to align its “look and feel” with other Sun products. See the revised Embedded Lights Out Manager Administration Guide for the Sun Fire X2100 M2 and Sun Fire X2200 M2 Servers. This and other Sun Fire Server documentation is available at:
http://docs.sun.com/app/docs/coll/x2100m2
If you change the IP address or netmask of the BMC, the routing table will change after you update the BMC network configuration. Therefore, you will need to re-enter the gateway information or reset the BMC.
| Note - This issue pertains to firmware contained on the Tools and Drivers CD v1.2. Sun recommends that you always update your server to the latest version of firmware. |
When running either Mozilla or Firefox on a Solaris operating system, you can only mount one device at a time.
This issue is under investigation.
When the SP is reset, time synchronization between the SP and BIOS is lost. As a result, the SP date is reset to 01/01/1970, and the time is reset to 00:00.
This issue is resolved with Tools and Drivers CD v1.7.0
Update using the Tools and Drivers CD v1.7.0
Sun Fire X2100 M2 server systems with SP/BMC firmware v2.91 have susceptibility to unauthorized access via the SP.
Upgrade the SP to v3.09 using the Tools and Drivers CD v1.5.
Sun recommends this update for all Sun Fire X2100 M2 servers.
With firmware versions available on Tools and Drivers CD v1.2 and lower, the SP might reset when you issue a power-on command following a power-off command via IPMItool or the command line interface (CLI).
1. Update the Sun Fire X2100 M2 firmware with v1.3 or later.
You can download firmware from the following site.
http://www.sun.com/servers/entry/x2100/downloads.jsp
2. Power down the system gracefully before powering it back on.
ipmitool -A password -H IP_address -I lan -U user -P password chassis power soft
IP_address the SP IP address
user the SP user name
password the SP password
When running the start /SP/AgentInfo/console command you must configure the OS to see the output. Refer to the procedures below for configuring each OS:
|
| Note - Minimum versions for this procedure: RHEL 3U7 and RHEL 4U3 |
1. Use a text editor to edit the /etc/grub.conf file.
2. Append the following to the kernel boot parameter line:
console=tty1 console=ttyS1, baudrate
baudrate 9600 (default value) or the same baud rate set in the BMC and BIOS.
For example, the new kernel boot parameter line should look similar to this:
kernel /vmlinuz-2.x.x ro root=LABEL/1 rhgb quiet console=tty1 console=ttyS1, 9600
3. Edit the /etc/securetty file.
a. Add ttyS1 to the bottom of the file.
4. Edit the /etc/inittab file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under the section “Run gettys in standard runlevels” add the following as the first line:
co:2345:respawn:/sbin/agetty ttyS1 baudrate vt100
|
| Note - Minimum versions for this procedure: SLES 9 SP3 |
1. Use a text editor to edit the /boot/grub/menu.lst file.
2. Append the following to the kernel boot parameter line:
baudrate 9600 (default value) or the baud rate set in the BMC and BIOS.
For example, the new kernel boot parameter line should look similar to this:
kernel /boot/vmlinuz root=/dev/sda2 resume=/dev/sdal splash:silent showps console=tty0 console:ttyS1, 9600
3. Edit the /etc/securetty file.
a. To the bottom of the file, add:
4. Edit the /etc/inittab file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under “getty-programs for normal runlevels:” add the following line:
S0:12345:respawn:/sbin/agetty -L baudrate ttyS1 vt100
|
1. Edit the /boot/solaris/bootenv.rc file to read:
setprop ttyb-mode baudrate,8,n,1,-
baudrate 9600 (default value) or the baud rate set in the BMC and BIOS.
2. Edit the /boot/grub/menu.lst file to read:
kernel /platform/i86pc/multiboot -B console=ttyb
3. Edit the /kernel/drv/asy.conf file and add the following:
name=”asy” parent=”isa” reg=1, 0x2f8 interrupts=3;
4. Edit the /var/svc/manifest/system/console-login.xml file to read:
<propval name=’label’ type=’astring’ value=’baudrate’/>
baudrate 9600 (default value) or the baud rate set in the BMC and BIOS.
6. Use the following command to Reboot the system:
When booting the system with the console output directed to the serial port, the Sun splash screen will not appear, and you will not see the prompt to press F2 to enter the BIOS. You must disable the Sun splash screen to see the prompt.
|
1. Press the F2 key to enter the BIOS Setup Utility.
2. Select Boot, and then select Boot Setting Configuration.
3. Set the boot setting to quiet boot - disable.
This will enable a prompt to press F2.
| Note - This issue pertains to firmware contained on the Tools and Drivers CD v1.3. Sun recommends that you always update your server to the latest version of firmware. |
The Embedded Lights Out Manager (ELOM) service processor (SP) functionality has been updated with the Tools and Drivers v1.3 CD.
The remote power control options in the ELOM have changed.
The new options for PowerCtrl are:
The following issues are related to a virtual device connected to the ELOM remote console system:
|
“Some Virtual USB Flash Devices Do Not Mount in Solaris” on page 24 |
|
“Virtual CD-ROM Appears To Be Unmounted in SLES 9 SP3” on page 24 |
If you connect to the service processor using the hostname rather than the IP address, the remote virtual device function (DVD/ISO/floppy) might fail to work (CR 667047).
Connect to the ELOM web GUI using the IP address of the SP instead of the hostname.
The virtual CD-ROM appears to be unmounted when the remote console is run on a SLES 9 SP3 system. This is because the dialog box does not pop up when the CD is mounted.
Access the virtual CD-ROM from the /media directory.
For some USB flash devices, the virtual device will appear mounted in the ELOM, when it is not actually mounted.
This issue is under investigation.
The following issues are related the Embedded Lights Out Manager (ELOM) Remote Console and web GUI:
The Tools and Drivers CD v1.5 includes a new easy-to-use ELOM web GUI with a “look and feel” that more closely matches other Sun products. The Tools and Drivers CD v1.5 is available at:
http://www.sun.com/servers/entry/x2100/downloads.jsp
More information about the new ELOM web GUI is available in the Embedded Lights Out Manager Administration Guide for the Sun Fire X2100 M2 and Sun Fire X2200 M2
http://www.sun.com/products-n-solutions/hardware/docs/Servers/ x64_servers/x2100m2/index.html
When running the web GUI remotely from a Sparc-based system, the minimum supported Solaris OS is Solaris 10.
If you have a pop-up blocker enabled in Firefox, and you try to run the remote console through the ELOM web GUI, the blocker may prevent the remote console from launching. If the remote console does not launch, check to see if the pop-up blocker has blocked it.
If you are running Solaris on your remote console system, you must log into the operating system as root (superuser) to mount any virtual devices.
Installing BMC firmware v3.09 strengthens system security and is a recommended update. The X2100 M2 is susceptible to unauthorized access when the BMC firmware is at v2.91. Security vulnerability is greatly reduced by upgrading to BMC v3.09.
Update BMC (SP) firmware using Tools and Drivers CD v1.5 or higher.
For more information, see “Security Vulnerability in SP Email” on page 18.
When you launch a Remote Console session on a Solaris system, the system will prompt you for a decision regarding the javaRKVM.jnlp file.You have the following two options:
Select the option to open this file using its default application.
1. Select the option to save the file.
The javaRKVM.jnlp file is downloaded.
The download manager will display the location of this file.
3. Move the javaRKVM.jnlp file to the /tmp directory.
# mv /location_of_javaRKVM.JNLP/javaRKVM.JNLP /tmp
location_of_javaRKVM.JNLP The directory where javaRKVM.JNLP resides.
4. To find the location of the javaws application, enter the following in a terminal window:
5. Execute the following command from the terminal window:
# /location_of_javaws/javaws /tmp/javaRKVM.JNLP
location_of_javaws The directory where javaws resides.
Assume the javaws application is run from the /usr/bin directory:
# /usr/bin/javaws /tmp/javaRKVM.JNLP
This will open a Remote Console session. Once the remote console window is closed, the /tmp/javaRKVM.jnlp is removed.
The web GUI, which is available on the Tools and Drivers CD v1.5, supports Firefox versions 1 and 2 on Windows systems and no longer requires an ActiveX plugin. Update to the Tools and Drivers CD v1.5 to use Firefox versions 1 or 2 without an ActiveX plugin, or, to continue running remote console, and using Firefox v1.x without updating to the Tools and Drivers CD v1.5, install the ActiveX plugin by performing the following procedure:
|
1. Retrieve the latest ActiveX plugin (mozactivex-ff-15.xpi) at:
2. Open the Firefox 1.5 browser, and drag the mozactivex-ff-15.xpi file from its location to the open browser.
OCX is installed automatically.
3. Open the file C:\installation_path\defaults\perf\activex.js
The default path is c:\programfiles\MozillaFireFox\defaults\perf\activex
4. Change pref("security.classID.allowByDefault",false) to
pref("security.classID.allowByDefault",true)
5. Save the text file, and exit the text editor.
7. Go to Tools -> Options, and click on Content.
8. On the Content page, make sure that Enable Java and Enable Java Script are selected.
It is best to disable the web GUI time-out function when performing remote installations.
|
When running the remote console on the Solaris 10 operating system, the mouse performance might be slow.
|
1. Log in to the ELOM web GUI, and start the Remote Console.
2. Using the Remote Console window, run the following in a Solaris terminal window on the Sun Fire X2100 M2 system:
The following issues are contained in this section:
|
“Configuring Java Runtime Environment for Each Browser” on page 30 |
|
“Error Message When Launching the Remote Console Using JRE 1.6.0” on page 30 |
The following table shows the minimum versions that are supported for running the ELOM web GUI for the Sun Fire X2100 M2 server on Solaris and Linux operating systems.
The keyboard, video, mouse and storage (KVMS) over IP feature of the ELOM SP is designed for administering your system. Applications requiring heavy video bandwidth (for example, watching videos) will not perform well with KVMS over IP.
Java Runtime Environment (JRE) 5 Update 7 is the minimum supported version for the browsers to run the ELOM web GUI. Follow the steps below to download the JRE 5 Update 7 for Mozilla and Firefox browsers.
|
1. Go to http://www.java.sun.com/.
2. Click on the Get Java Software button.
3. Click Download Now in the new window that opens.
The web site will display the appropriate plug-in options for the operating system that you are running.
4. Click Download to download the appropriate plug-in.
Installation instructions and plug-in verification are also available on this site.
The error message, “Cannot Connect to Host” occurs when launching the remote console using JRE v1.6.0. This is a known bug.
|
1. Launch the java control panel.
path to jre jre1.6.0/bin/jcontrol
2. Select the General tab -> Network Settings, and click on “Direct Connection.”
The following issues in this section apply to the Pc-Check diagnostics software, v6.05d:
|
“Limited Connectivity to Service Processor When Running NIC2 Tests” on page 31 |
|
“Pc-Check Will Hang When Running Keyboard LED Test” on page 32 |
Support for NMI has been added in the web GUI beginning with CD v1.4.
When running the Pc-Check Network Test, access to the service processor shared network port might become sluggish or stop.
After creating a RAID 1 device in the BIOS, the Pc-Check diagnostics software fails to identify the device as a RAID device.
The text for the keyboard LED test is not included in the diagnostics scripts. You can only run the test manually.
This issue is under investigation.
If you encounter any of the following system issues, update your system firmware with the Tools and Drivers CD v1.1 to fix the issues:
| Note - This issue pertains to firmware contained on the Tools and Drivers CD v1.1. Sun recommends that you always update your server to the latest version of firmware. |
With the Tools and Drivers CD v1.1, there is an updated power control enhancement in the Embedded Lights Out Manager (ELOM) web GUI and CLI functionality that allows remote users to reboot the system and have it enter the system BIOS automatically.
If you are using the ELOM web GUI:
1. Click the Power Control tab.
2. Select Boot Option: BIOS Setup.
If you are using the ELOM CLI.
Bus uncorrectable errors will appear in SEL log with the Emulex host bus adapter (HBA). Testing has found no functional issues.
After unmounting the virtual CD-ROM, Network will move to the top of the boot order replacing the CD-ROM, if one is present.
Enter the BIOS, and change the boot order.
When you are using the web GUI with Mozilla or Firefox on a Solaris operating system, the virtual storage device is not readable in some instances.
In some instances, the virtual device will not remount after it has been unmounted.
Reboot the system that is running the remote console.
In some instances, the web GUI will suddenly disappear.
When logging into the web GUI, the Hostname Mismatch dialog box is displayed for a few seconds, and then it moves behind the web browser window. If Run is not clicked in the Hostname Mismatch dialog box, the web GUI will not react to any mouse clicks until the other dialog box is closed.
Minimize the web browser windows, and click Run on the Hostname Mismatch dialog box.
This issue only happens on a small number of remote installations. If the connectivity is lost, a new installation is required.
You will not be able to see the system time when using CLI commands with the ELOM SP. You will need to use the ELOM web GUI to view the system time.
|
Copyright |
Copyright 2007 - 2009 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, Sun Fire, docs.sun.com, 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 - 2009 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, Sun Fire, docs.sun.com, 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.
To Recover From a Corrupt SP