General Functionality Issues And Limitations - Sun Oracle Sun SPARC Enterprise M3000 Product Notes

General Functionality Issues and Limitations

Note – Do not use the Service Processor (SP) as the Network Time Protocol (NTP)
server. Using an independent NTP server provides optimal reliability in maintaining
consistent time on the SP and the domains. For more information about NTP, see the
Sun Blueprint document, Using NTP to Control and Synchronize System Clocks:
http://www.sun.com/blueprints/0701/NTP.pdf
For power-on after power-off, wait at least 30 seconds before turning the system
■
power back on by using the main line switch or the circuit breakers on the
distribution panel.
You cannot use the following user account names, as they are reserved for system
■
use: adm, admin, apache, bin, daemon, default, ldap, nobody, ntp,
operator, proxyuser, root, rpc, rpcuser, and sshd.
An XSCF user account user name cannot match an LDAP user name, and an
■
XSCF user account number (UID) cannot match an LDAP UID number.
If your M3000 server is running the Solaris 10 10/09 OS and IPMP, you must
■
disable probe-based failure detection to correct for CR 6888928. See InfoDoc
211105 (86869).
When you use the external power control interface of the external power
■
controller, the following notification signals are not supported:
■
■
When you import XCP or update the firmware using the XSCF you might see
■
Web session ID errors displayed on the web browser. When you specify the
timeout period as over 30 minutes in the Autologout setting, Internal Server
Errors might be displayed. To reconnect to the XSCF Web close the current
browser and open the new browser.
Before using the XSCF Web, disable pop-up blocking and remove any plug-ins
■
such as the search tool installed with the browser.
XSCF-LAN is compliant with auto-negotiation. Set the network device that
■
connects with XSCF-LAN to the auto-negotiation mode. Otherwise, when you
connect the XSCF-LAN and the network device (fixed to the full-duplex mode,
according to the IEEE 802.3 rule), the XSCF-LAN communicates in half-duplex
mode and network communication speed might slow or communication errors
may occur.
For information about I/O options and storage, such as the number of cards
■
supported in a domain, see the Sun Cross Platform IO Support page:
http://wikis.sun.com/display/PlatformIoSupport/Home/
10 Sun SPARC Enterprise M3000 Server Product Notes for XCP 1092 • May 2010
The OS panic or the server hardware error signal (*CPUN/RTNU).
The server hardware error signal (power fail, temperature error, and fan error)
(*ALARM).