Monitor Alerts from GUI

There are no "Fault LEDs" on the system and/or any of the CRUs.

• So, you will not get a physical indication when a CRU is malfunctioning.
• The system does have a "green LED" (front of unit) to indicate the system had booted up.
• The system does have a "blue LED" (front of unit) to indicate the system is transferring data.

Each time that the magazine drive is brought into the data center, you should check out the "System Logs" to see if there might be any malfunctions occurring within the system.

Note: If the OMV/GUI defaults have been changed, use that data to log onto the system.

Complete the following process to access the "Diagnostics System Information screens" for possible system malfunctions.

1. Access the OMV/GUI.
   1. Default Address: 10.0.0.1
   2. Default Username: admin
   3. Default Password: password

   

2. Ensure the following screen appears.

   

3. Select the following: > Diagnostics> System Information

4. Click on "Overview" and ensure the following screen appears.

   Note: This screen provides hostname, version of software, processor, kernel, system time, uptime, load average, CPU usage and memory usage.

   

5. Select the following: > Diagnostics> System Information

6. Click on "Processes" and ensure the following screen appears.

   Note: This screen provides users, load average, tasks, CPU usage, etc.

   

7. Select the following: > Diagnostics> System Information

8. Click on "Performance statistics" and ensure the following screen appears.

   Note: This screen provides CPU usage by hour, day, week, month, and year.

   

9. Select the following: > Diagnostics> System Information

10. Click on "Report" and ensure the following screen appears.

    Note: This screen provides system information, interface, location, uptime, driver information, etc.

    

11. Select the following: > Diagnostics> System Information

12. Click on "Serial Numbers" and ensure the following screen appears.

    Note: This screen provides chassis, magazine, and drive serial numbers. Notice there are six (6) drives installed. If a drive is malfunctioning, a drive serial number will be missing; thus, only five (5) drives will be shown.

    

13. Select the following: > Diagnostics> System Information

14. Click on "Main board info" and ensure the following screen appears.

    Note: Currently this system has no (zero) faults. If you scan the list of devices, they are all "OK". If a device was malfunctioning, the list would show a "failed" status. The "ns" stands for "no status" (device not installed).

    

15. Select the following: > Diagnostics> System Information

16. Click on "Fault Report" and ensure the following screen appears

    Note: Currently this system has no (zero) faults. If there were faults, they would be listed here.

    

    Note: If your refer to the screen below, a user can select the following: Fault Report, Fault Reset, Fault On, and Fault Off.

    

There are no "Fault LEDs" on the system and/or any of the CRUs.

• So, you will not get a physical indication when a CRU is malfunctioning.
• The system does have a "green LED" (front of unit) to indicate the system had booted up.
• The system does have a "blue LED" (front of unit) to indicate the system is transferring data.

Each time that the magazine drive is brought into the data center, you should check out the "System Logs" to see if there might be any malfunctions occurring within the system.

Note: If the OMV/GUI defaults have been changed, use that data to log onto the system.

Complete the following process to access the "Diagnostics System Logs screens" for possible system malfunctions.

1. Access the OMV/GUI.
   1. Default Address: 10.0.0.1
   2. Default Username: admin
   3. Default Password: password

   

2. Ensure the following screen appears.

   

3. Select the following: > Diagnostics> System Logs

4. Click on "Logs" and ensure the following screen appears.

   Note: This screen provides the "Syslog" with date, time, and message. Notice this screen provides the user with a "Clear" and a "Download" function (right side of screen). Clear or download the log as needed.

   

5. Scan the log for any possible malfunctions of the system.

6. Remove and replace any malfunctioning CRUs.

7. Select the following: > Diagnostics> System Logs

8. Click on "Settings" and ensure the following screen appears

   Note: This screen provides a "Save" and "Reset" function for "Remote syslog. Save or reset the syslog as needed.