The service processor (SP) on the Sun Fire X4170 M2 Server or Sun Fire X4270 M2 Server might reboot under a heavy workload due to lack of memory caused by a Sun Fire X4170 M2/X4270 M2 Oracle ILOM memory limitation.
To prevent SP reboots from occurring when upgrading to Oracle ILOM 3.2.x.x, or later (or to prevent SP reboots on a system already upgraded to Oracle ILOM 3.2.x.x, or later), follow these guidelines:
When running the Oracle ILOM Snapshot utiltiy, run the fewest number of command-line interface (CLI) or web interface sessions necessary. Keep only one interface session running, and ideally, run the Snapshot utility using the CLI. Do not run multiple tasks concurrently in different interface sessions.
If you need to run multiple interface sessions, run up to a maximum of five sessions. The five-session limitation can include all CLI sessions, four CLI sessions with one web interface session, or four CLI sessions with one Remote System Console session. Avoid running or trying to open more than one web interface session or more than one Remote System Console session simultaneously with the CLI sessions.
When updating Oracle ILOM, use the load -source PKG_URL CLI command with the PKG_URL as a TFTP/FTP/SFTP-based protocol. Do not use an HTTP/HTTPS protocol in the package URL, if possible. Avoid updating Oracle ILOM using the web interface by uploading a package file or providing a PKG_URL. If the Oracle ILOM update fails, Oracle ILOM will boot into Preboot. Use the CLI net flash command to rescue the update with the flash file in the release:
Use the net config command to set ipdiscovery, managementport, and other configurations. (You can list the configuration parameters using the show command.)
Use the net dhcp command to obtain the IP address if ipdiscovery is configured as DHCP.
Use the net flash TFTP-server-IP-address path-to-flash-file command to flash Oracle ILOM.