Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1357354.1
Update Date:2018-05-14
Keywords:

Solution Type  Technical Instruction Sure

Solution  1357354.1 :   Sun Storage 7000 Unified Storage System: How to Update the BIOS for a 7x10 NAS Appliance  


Related Items
  • Sun Storage 7110 Unified Storage System
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun Storage 7310 Unified Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  
  • _Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
  •  




In this Document
Goal
Solution
 A. Identification of Affected Parts
 B. Upgrade the SP/ILOM and BIOS on Sun Storage 7x10
 C. Configuring the BIOS Settings
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Typically requires a 7000 trained field engineer.

Applies to:

Sun Storage 7310 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)
NAS head revision : [not dependent]
BIOS revision : [0ABMN043|0ABMN064|0ABMN080]
ILOM revision : [2.0.2.15|2.0.2.16]
JBODs Model : [not dependent]
CLUSTER related : [not dependent]


Goal

Assist TSC and field / partner engineers with 7x10 appliance SP/BIOS upgrade.

 

Solution

Please read and understand all steps before proceeding with the Service Processor (SP) upgrade.

NOTE FOR PARTNER ENGINEERS: Please ensure only engineers trained in how to support ZFSSA perform BIOS upgrades.


To check the Service Processor BIOS version refer to this document:
Sun Storage 7000 Unified Storage System: How to check the SP BIOS revision level [Document 1174698.1]

 This document assumes you are able to connect/login to a pre-configured SP via network IP address.

 

A. Identification of Affected Parts

Connect via ssh to the Service Processor and supply root credentials. The version displayed from the command "version" should now be 2.0.2.16 for 7110, 7310 and 7410. The version for 7210 is 2.0.2.15.

To display the BIOS version, type "show /SYS/MB/BIOS". Alternatively, start the system with "start /SYS". The BIOS version will be displayed in the initial BIOS banner. The current version for the 7310 and 7410 is 0ABMN080. The current version for 7210 is 0ABNF032.

Any prior version is susceptible to these issues. Checking the BIOS version via other means, such as the administrative BUI/CLI can be viewed in the OS environment.

CLI: Login to CLI by providing administrative credentials and type:

7000:> configuration ==> version ==> show


BUI: Clicking on SUN/Oracle Icon after logging into the BUI after providing administrative credentials.

Note that checking the SP version via other means, such as the administrative BUI may be unreliable. Due to a defect in some releases, version 2.0.2.16 may also be displayed as 2.0.2.22 and 2.0.2.15 may be displayed as 2.0.2.21

 

B. Upgrade the SP/ILOM and BIOS on Sun Storage 7x10

Connect to the Service Processor via ssh using root credentials. Use this interface to shut down the storage controller with :

-> stop /SYS

or in the BUI/aksh

Maintenance System Poweroff


The node will shut down. Powering it off prior ensures there are no active data pools affiliated with the node.

Connect to the Service Processor IP address via a browser - Microsoft Internet Explorer (IE) preferred - and provide the root login credentials.

NOTE: Mozilla Firefox will not work, if IE is not available please use ftp method (an example of ftp upload method is in Doc 1357409.1)

This is NOT the same BUI as the appliance browser.

Follow the quick steps below to upgrade the Service Processor and BIOS on the Sun Storage 7x10:

  1. Click on Maintenance tab
  2. Firmware Upgrade will be the default sub-tab
  3. Click on "Enter Upgrade Mode"
  4. Confirm this action with the pop up
  5. Click on "Browse" and select the appropriate image from your local filesystem (obtained from NAS Storage-TSC)
  6. Click on "Upload"
  7. Wait for upload to complete and the verification to succeed
  8. You will now see a Summary Table of the SP firmware and BIOS versions (Existing vs New). Confirm that "Preserve existing configuration" is checked for the SP Firmware  (EXCEPT when downgrading from 3.x to 2.x - see note below)
  9. Click on "Start Upgrade"
  10. Confirm this action with the pop up
  11. Now wait for the upgrade to proceed. If the storage controller was up at this point, it will be cleanly shutdown. Warning! Do not interrupt the update. Leave the browser undisturbed until the update is complete.
  12. When finished, you will see "Upgrade Complete" and the SP will reboot.

Note:  When downgrading the BIOS version from 3.x to 2.x, please uncheck "Preserve existing configuration" and then reset the IP network information after the firmware upgrade completes.

 

 

C. Configuring the BIOS Settings

Note: If the system hangs during boot following the BIOS upgrade, a workaround is to disconnect the SAS JBOD cables and reboot to enter into the BIOS setting screen. Be very certain to reconnect the SAS cables immediately after correcting the BIOS settings.

The SP firmware and BIOS will now have been updated to the correct 7000 version. Each platform has specific BIOS settings. Boot the storage controller and enter setup with:

-> start /SYS
Are you sure you want to start /SYS (y/n)? y
Starting /SYS
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (


Once you see the initial BIOS banner, hit "Control-E" several times when prompted; this will trigger the BIOS Setup menu after the initialization.

If you missed the BIOS banner, you can drop back to the SP with ESC (      Then reset the system - see below.

Note: Escape followed by shift 9 - at least open parenthesis is usually on shift 9.  Some systems substitute the escape key with control key and the [ key.... ctrl [ shift 9.

Serial console stopped.

-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (



Now, follow the specific instructions for the appropriate appliance:

  • 7110 BIOS

Disable PCIPnP Option-ROM scanning for slots 1-5

Disable I/O allocation

Use the right arrow key to page over to "PCIPnP" menu. Use the down arrow to highlight:

Scanning OPROM on PCI-E Slot1 Enabled

Press return and select "Disabled". This will now appear as:

Scanning OPROM on PCI-E Slot1 Disabled

Repeat this for slots 1-5 (the last slot is off the bottom of the screen). You should now have:

Scanning OPROM on PCI-E Slot0 Enabled
Scanning OPROM on PCI-E Slot1 Disabled
Scanning OPROM on PCI-E Slot2 Disabled
Scanning OPROM on PCI-E Slot3 Disabled
Scanning OPROM on PCI-E Slot4 Disabled
Scanning OPROM on PCI-E Slot5 Disabled

Just below these OPROM settings are a group of settings which allow IO allocation to be disabled per-slot. Disable PCI-E slots 1-4. Only slots 0 and 5 should be enabled. It should look like:

IO Allocation on PCI-E Slot0 Enabled
IO Allocation on PCI-E Slot1 Disabled
IO Allocation on PCI-E Slot2 Disabled
IO Allocation on PCI-E Slot3 Disabled
IO Allocation on PCI-E Slot4 Disabled
IO Allocation on PCI-E Slot5 Enabled

On boot, you will see the following warning message from the BIOS:

Warning: IO resource not allocated

This is an expected message and does not indicate a failure.

Exiting BIOS Setup

Use right arrow to page over to "Exit".  Press for the default "Save Changes and Exit", and again to confirm the action with the pop up.

 

 

  • 7210 BIOS

Disable I/O allocation

Disable PCIPnP Option-ROM scanning for all slots

Use the right arrow key to page over to "PCIPnP" menu. Use the down arrow to highlight:

Scanning OPROM on PCI-E Slot0 Enabled

Press return and select "Disabled". This will now appear as:

Scanning OPROM on PCI-E Slot0 Disabled

Repeat this for slots 1-5 (the last slot is off the bottom of the screen). You should now have:

Scanning OPROM on PCI-E Slot0 Disabled
Scanning OPROM on PCI-E Slot1 Disabled
Scanning OPROM on PCI-E Slot2 Disabled
Scanning OPROM on PCI-E Slot3 Disabled
Scanning OPROM on PCI-E Slot4 Disabled
Scanning OPROM on PCI-E Slot5 Disabled

Just below these OPROM settings are a group of settings which allow IO allocation to be disabled per-slot. Disable PCI-E slot 0. Only slots 1 and 2 should be enabled. It should look like:

IO Allocation on PCI-E Slot0 Disabled
IO Allocation on PCI-E Slot1 Enabled
IO Allocation on PCI-E Slot2 Enabled

On boot, you will see the following warning message from the BIOS:

Warning: IO resource not allocated

This is an expected message and does not indicate a failure.

Exiting BIOS Setup

Use right arrow to page over to "Exit". Press for the default "Save Changes and Exit", and again to confirm the action with the pop up.

 

 

  • 7310 BIOS

Disable PCIPnP Option-ROM scanning for all slots

Disable I/O allocation

Configure boot drives

Use the right arrow key to page over to "PCIPnP" menu. Use the down arrow to highlight:

Scanning OPROM on PCI-E Slot0 Enabled

Press return and select "Disabled", followed by return. This will now appear as:

Scanning OPROM on PCI-E Slot0 Disabled

Repeat this for slots 1-2. You should now have:

Scanning OPROM on PCI-E Slot0 Disabled
Scanning OPROM on PCI-E Slot1 Disabled
Scanning OPROM on PCI-E Slot2 Disabled

Just below these OPROM settings are a group of settings which allow IO allocation to be disabled per-slot. Disable PCI-E slots 1 and 2. Only slot 0 should be enabled. It should look like:

IO Allocation on PCI-E Slot0 Enabled
IO Allocation on PCI-E Slot1 Disabled
IO Allocation on PCI-E Slot2 Disabled

Next, arrow over to the Boot menu. Select the last item: "Hard Disk Drives" and press return. The list should include only 2 drives (the 2 internal SATA drives) with labels like:

SATA:11M-<drive model>
SATA:12M-<drive model>

If this list includes anything else (such as readzilla cache devices with a 'STEC MACH8' string, or JBOD attached drives) you'll need to remove them from the list by selecting the boot position and setting it to 'Disabled' for each of non-boot drives.

If the list is full (with 16 drives) you will not be able to edit the list. However, the change to the OPROM settings above will cause the JBOD drives to disappear from the list on the next boot.

You will need to exit and save changes and immediately re-enter the BIOS menu on the next boot (CTRL-E).

Exiting BIOS Setup

Once you've removed any readzilla cache or JBOD drive entries from the "Hard Disk Drives" list, press ESC to exit the "Hard Disk Drives" menu, then arrow right to the "Exit" menu. Press for the default "Save Changes and Exit", and return again to confirm the action with the pop up.

On boot, you will see the following warning message from the BIOS:

Warning: IO resource not allocated

This is an expected message and does not indicate a failure.

 

 

  • 7410 BIOS

Configure boot drives

Disable I/O allocation

Disable PCIPnP Option-ROM scanning for all slots

Use the right arrow key to page over to "PCIPnP" menu. Use the down arrow to highlight:

Scanning OPROM on PCI-E Slot0 Enabled

Press return and select "Disabled", followed by return. This will now appear as:

Scanning OPROM on PCI-E Slot0 Disabled

Repeat this for slots 1-5 (the last slot is off the bottom of the screen). You should now have:

Scanning OPROM on PCI-E Slot0 Disabled
Scanning OPROM on PCI-E Slot1 Disabled
Scanning OPROM on PCI-E Slot2 Disabled
Scanning OPROM on PCI-E Slot3 Disabled
Scanning OPROM on PCI-E Slot4 Disabled
Scanning OPROM on PCI-E Slot5 Disabled

The next actions depend on the type external storage and the HBAs. The SAS2 HBA slot restrictions require a different combination of Enabled/Disabled. Take care to use the appropriate settings.

For SAS1 configurations (Connected with J4400 JBODs)

Just below these OPROM settings (they are actually off the bottom of the screen and you will need to scroll down) are a group of settings which allow IO allocation to be disabled per-slot. Disable PCI-E slots 0-3, checking that slots 4 and 5 are Enabled. It should look like:

IO Allocation on PCI-E Slot0 Disabled
IO Allocation on PCI-E Slot1 Disabled
IO Allocation on PCI-E Slot2 Disabled
IO Allocation on PCI-E Slot3 Disabled
IO Allocation on PCI-E Slot4 Enabled
IO Allocation on PCI-E Slot5 Enabled


For SAS2 configurations (Connected with J4410 JBODs)

Just below these OPROM settings (they are actually off the bottom of the screen and you will need to scroll down) are a group of settings which allow IO allocation to be disabled per slot. Disable PCI-E slots 1-4, checking that slots 0 and 5 are Enabled. It should look like:

IO Allocation on PCI-E Slot0 Enabled
IO Allocation on PCI-E Slot1 Disabled
IO Allocation on PCI-E Slot2 Disabled
IO Allocation on PCI-E Slot3 Disabled
IO Allocation on PCI-E Slot4 Disabled
IO Allocation on PCI-E Slot5 Enabled

Next, arrow over to the Boot menu. Select the last item: "Hard Disk Drives" and press return. The list should include only 2 drives (the 2 internal SATA drives) with labels like:

SATA:11M-
SATA:12M-

If this list includes anything else (such as readzilla cache devices with a 'STEC MACH8' string, or JBOD attached drives) you'll need to remove them from the list by selecting the boot position and setting it to 'Disabled' for each of non-boot drives.

If the list is full (with 16 drives) you will not be able to edit the list. However, the change to the OPROM settings above will cause the JBOD drives to disappear from the list on the next boot.

You will need to exit and save changes and immediately re-enter the BIOS menu on the next boot (CTRL-E).

Exiting BIOS Setup

Once you've removed any readzilla cache or JBOD drive entries from the "Hard Disk Drives" list, press ESC to exit the "Hard Disk Drives" menu, then arrow right to the "Exit" menu. Press for the default "Save Changes and Exit", and return again to confirm the action with the pop up.

On boot, you will see the following warning message from the BIOS:

Warning: IO resource not allocated

This is an expected message and does not indicate a failure.

 

References

<NOTE:1174698.1> - Oracle ZFS Storage Appliance: How to check the SP BIOS revision level
<NOTE:1399040.1> - Sun Storage 7000 Unified Storage System: Recovery of 7x10 Appliance from Installation of Unsupported BIOS Release 3.x

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback