Instructions for getting the cumulative I/O density data:
    1. Log in with user name and password
    2. Type 'get logs:heatmap <filename.csv> is a file to capture the cumulative
        I/O density data
    3. Example: 'get logs:heatmap IO_density.csv'

Instructions for updating firmware in controller modules:
    1. Type 'put <filename> flash' where <filename> is the new firmware image to load.
    2. It will take approximately 10 minutes for the new firmware to load and
        for the automatic restart to complete. Progress messages will be
        displayed in this FTP interface during that time. Wait for the progress
        messages to indicate that the code load has completed.
    3. If the partner firmware upgrade (PFU) feature is enabled, allow
        an additional 20 minutes for the partner controller to be updated.
        No messages will be displayed in the FTP interface during PFU.
        If PFU is NOT enabled, log into the other controller and repeat steps 1-2.
    4. WARNING! Do not power cycle or restart during the firmware update
        as this can result in loss of capabilities for this unit.
    5. If you attempt to load an incompatible firmware version (such as code
        that is intended only for an iSCSI system on an FC system) the message
        "*** Code Load Fail. Bad format image. ***" will be displayed and the FTP
        prompt will come back in just a few seconds. The code will not be loaded.

Instructions for updating firmware in expansion modules:
    1. Obtain the address of each enclosure management processor (EMP) in the form
        <EMP-channel-ID>:<EMP-target-ID> (for example, 0:63 and 1:63)
        and obtain the firmware revision of each EMP.
        Determine which EMPs need to be updated based on the revision.
        Note: In the WBI, the EMP addresses are displayed by clicking on each
        enclosure in the Configuration View. The needed data is displayed
        in the fields labeled 'EMP A Bus ID', 'EMP B Bus ID', 'EMP A Target ID',
        'EMP B Target ID', 'EMP A Revision', and 'EMP B Revision'. (The terms
        'bus' and 'channel' are equivalent.)
        Note: In the CLI, enter 'show enclosures'. The needed data is displayed
        in the columns labeled 'EMP A CH:ID Rev' and 'EMP B CH:ID Rev'.
    2. Log in via FTP with user name and password.
    3. Type 'put <filename> encl:<EMP-channel-ID>:<EMP-target-ID>'
        where <filename> is the new firmware image to load.
    4. It typically takes several minutes for the new firmware to load. Progress
        messages will be displayed in this FTP interface during that time. Wait
        for the progress messages to indicate that the code load has completed.
        WARNING! Do not power cycle or restart during the firmware update
        as this can result in loss of capabilities for this unit.
    5. Repeat steps 3-4 for each EMP to update in each enclosure.

Instructions for updating disk firmware:
    1. Obtain the address of each disk to be loaded in the form
        <enclosure-ID>.<slot-number> (for example, 0.1 and 1.9)
        and obtain the firmware revision of each of these disks.
        Determine which disks need to be updated based on the revision.
        Note: In the WBI, the disk addresses are displayed by clicking on each
        enclosure in the Configuration View and then selecting the desired
        disk. The needed data is displayed in the fields labeled 'Enclosure ID',
        'Slot', and 'Revision'.
        Note: In the CLI, enter 'show disks'. The needed data is displayed
        in the columns labeled 'Location' and 'Revision'.
    2. Log in via FTP with user name and password.
    3. Type 'put <filename> disk:<disk-list>'
        where <filename> is the new firmware image to load,
        and <disk-list> is a list of the form currently supported in the CLI.
        You can specify:
        - A disk (Example: 0.4)
        - A hyphenated range of disks (Example: 0.4-7)
        - A comma-separated list of individual disks, ranges, or both with no spaces.
          (Example: 0.4,0.6-9)
        If "disk" with no disk-list is entered, all disks compatible with the
        specified firmware will be updated.
    4. It typically takes several minutes for the new firmware to load. Progress
        messages will be displayed in this FTP interface during that time. Wait
        for the progress messages to indicate that the code load has completed.
        WARNING! Do not power cycle or restart during the firmware update
        as this can result in loss of capabilities for this unit.
    5. Repeat steps 3-4 for each disk to update in each enclosure.

Instructions for getting debug logs:
    1. Log in with a user name and password.
    2. Type 'get logs <filename.zip>'
        where <filename.zip> is the file to capture the system debug logs.
        Note the debug logs are in a compressed archive format and will need to be
        uncompressed before viewing.

Instructions for getting historical disk-performance statistics:
    1. Log in as a user that has permission to use the FTP interface.
    2. Type 'get perf[:<date/time-range>] <filename>.csv'
        where <filename>.csv is the file to capture the historical
        disk-performance statistics and <date/time-range> is optional
        and specifies the time range of data to transfer, in the format:
        start.<yyyy>-<mm>-<dd>.<hh>:<mm>.[AM|PM].end.<yyyy>-<mm>-<dd>.<hh>:<mm>.[AM|PM].
        The <date/time-range> string must contain no spaces.
    3. Example: 'get perf:start.2015-01-03.04:00.AM.end.2015-01-05.10:00.PM. statistics.csv'

Instructions for loading a license file:
    1. Log in with a user name and password.
    2. Type 'put <certificate.txt> license'
        where <certificate.txt> is the name of the license file generated
        for your specific system.

Instructions for loading security certificate files:
    1. The security certificate files will consist of a pair of files.
       You will have a certificate file and a key file.
    2. Log in with a user name and password.
    3. Type 'put <certificate-file-name> cert-file'
        where <certificate-file-name> is the name of the certificate file
        for your specific system.
    4. Type 'put <key-file-name> cert-key-file'
       where <key-file-name> is the name of the security key file for
        your specific system.
    5.  Restart both Management Controllers to have the new security
        certificate take effect.


