Controller Diagnostics and Command Testing

Administrators can use two features of the Oracle FS System Manager (GUI) to help characterize and isolate the source of Controller issues. These issues can be related to Controller hardware or software, or can be related to the connections between the Controller and the public data network.
The Controller diagnostics feature performs a suite of diagnostic tests on the hardware components and the software modules in a Controller. The hardware that is tested includes, for example, the motherboard, the network interface cards, the fans, and the power supplies that are contained within the Controller.
Note: During startup, the Oracle FS System always performs diagnostics on the Controller nodes.
The diagnostic tests on the hardware and software return detailed information to help a support administrator to characterize and to isolate specific faults in the system. With this information, the support administrator can more easily determine which field replaceable unit (FRU) needs to be replaced.
Important! Close all of the applications that are using the Controller before running diagnostics, then disconnect the Controller from the public data network.

While the diagnostic tests are being run, the status of the Controller appears as Failed Over. When the tests are complete, the status changes to Normal.

To run diagnostics on a Controller, the system disables the write cache in the target Controller, moves all the resources of the Controller to its partner Controller, and takes the target Controller offline. All of the LUNs that are assigned to the Controller are put into Conservative mode. During the diagnostic period, the performance of the partner Controller is diminished because all I⁠/O is performed directly to disk.