Resetting the Service Processor Using Oracle ILOM

If the Oracle ILOM service processor (SP) is hung, Oracle ILOM provides two methods to reset it:

From the Oracle ILOM command-line interface (CLI), type: reset /SP.

From the Oracle ILOM web interface, click Administration > Maintenance > Reset SP.

If the Oracle ILOM SP is hung and you cannot reset it using the Oracle ILOM web interface or the Oracle ILOM CLI command, use the following procedure to reset the SP from the server back panel.

Using a stylus, press the Reset SP pinhole button that is located on the server back panel.

Figure SP Reset Pinhole Button Location

References: https://docs.oracle.com/cd/E37831_01/html/E48558/z40002791433422.html

https://docs.oracle.com/cd/E37831_01/html/E48558/z40002791433048.html

D: When a server boots, the network card will negotiate with the network switch how to communicate. Various settings such as speed and duplex are often part of the auto-negotiation protocol. Occasionally, a server will not negotiate with the network switch the highest possible throughput. The duplex setting may improperly negotiate to half, which could result in collisions and errors, but this can be resolved through manually setting the port characteristics.

References: http://netmgt.blogspot.se/2011/05/sun-v890-forcing-qfe-full-duplex.html

NFS Service properties include:

Minimum supported version - Use this to control which versions of NFS the appliance supports.

Maximum supported version - Use this to control which versions of NFS the appliance supports.

Setting the NFS minimum and maximum versions to the same value causes the appliance to only communicate with clients using that version. This may be useful if you find an issue with one NFS version or the other (such as the performance characteristics of an NFS version with your workload), and you want to force clients to only use the version that works best.

Block size is included Share properties.

Volume Block Size is the native block size for LUNs. This can be any power of 2 from 512 bytes to 1M, and the default is 8K.

References: Oracle ZFS Storage Appliance Administration Guide (June 2014), page 281

Synchronous writes to the Oracle ZFS Storage Appliance are not acknowledged immediately upon landing in DRAM. Instead, they are acknowledged only once they are persistently stored on disk or flash.

References: http://www.oracle.com/technetwork/server-storage/sun-unified-storage/documentation/o14-001-architecture-overview-zfsa-2099942.pdf