FS System: How to Check the Drive Mode Page Setting on an FS1-2 System

Asset ID:	1-71-1969899.1
Update Date:	2016-01-15
Keywords:

Solution Type Technical Instruction Sure

Solution 1969899.1 : FS System: How to Check the Drive Mode Page Setting on an FS1-2 System

Applies to:

Oracle FS1-2 Flash Storage System - Version 6.1.0 and later
Information in this document applies to any platform.

Goal

This document will show how to verify that the mode pages are set properly in an FS1-2 system. Mode pages are used to define how the Hard Disk Drives (HDD) and Solid State Drives (SDD) will behave in the FS1-2 System environment. If improperly set drive behavior cannot be predicted and may endanger customer data.

Solution

Attached to this document is the checkmode utility that must run on the active Pilot to check the mode page status of all the drives.

Using WinSCP or a similar program, copy the checkmode.tar attachment in this document to the Active Pilot's /var/tmp directory.
Ssh into the active Pilot using the shared IP address of the FS1-2.

Extract the utility from the tar file:

# tar xvf checkmode.tar
checkmode
lib/PcliCommand.pm
lib/Retryable.pm
chmod 777 -R lib directory:

# chmod 777 -R lib/
Execute the utility using its absolute path:

# /var/tmp/checkmode
password:

NOTE: By default the checkmode utility uses the pillar username account, the utility will prompt the user to enter the pillar username account password

If you want to use a different user account run checkmode using the -u option and enter the username, for example if you want to execute the utility using the administrator username account:
# /var/tmp/checkmode -u administrator
password:
If no output is produced, then the mode pages are properly set.
If the mode pages are improperly set, output like this will be seen:

# /var/tmp/checkmode
password:
5080020001688F4C:18 -- timeout=0x0000 CAWT=0x46 TB=C4 Model=H109030SESUN300G StorageClass=STORAGE_CLASS_PERF_HDD timeout doesn't match expected value
TB doesn't match expected value

NOTE: If any output is discovered, rerun the command again with -v (see below) and save the output to a file for Engineering if requested.

To fix the problem will require a restart of ths FS1-2 System. Using the fscli, login and execute the following command:

# fscli system -restart -resetModePages

If there are any reporting issues or issues executing the checkmode utility capture the following output:

# /var/tmp/checkmode -v
password:

The -v (verbose) option will display the output from the pcli commands, for more detailed output use the -d option:

# /var/tmp/checkmode -d
password:

The -d (debug) option will display more output details from the pcli commands.

For further infomation on how to use checkmode, execute checkmode with the -h option to display the help menu.

# /var/tmp/checkmode -h
checkmode: <hostname> [-v] [-d] [-u <user>]

   Verify certain mode page values on a given Axiom.
   The values verified are:
      Mode Page 25: timeout == 0x7d0
                    CAWT    == 0x46
      Mode Page 1: TB      == 0xc0
   If <hostname> is given, that machine will be checked. If not, 'localhost' will be used (assumes the sript is run on a Slammer)

   the script will prompt for a password for the user given by the -u option (or user 'pillar' if -u is not given)

   [-v]:          turn on verbose mode - prints pcli command issued and results
   [-d]:          higher level of debug output from the pcli response
   [-u <user>]:   user name to use for executing pcli commands - default is 'pillar'

Attachments

This solution has no attachment