Netra Modular System: FMM firmware version is LOWER than 3.2.6.36

Asset ID:	1-71-2240158.1
Update Date:	2017-03-02
Keywords:

Solution Type Technical Instruction Sure

Solution 2240158.1 : Netra Modular System: FMM firmware version is LOWER than 3.2.6.36

Applies to:

Netra Modular System - Version All Versions and later
Information in this document applies to any platform.

Goal

During FMM firmware upgrade, you see this note:

IMPORTANT: If your FMM firmware version is LOWER than 3.2.6.36, call Oracle Service to help upgrade.

Solution

Mandatory steps to upgrade FMM to R1.1 firmware

===============================================
rajeev.bharol@oracle.com
5/24/2016
Rev 3

Step 1:
======
Load the new R1.1 FMM image normally using 'load' command as:

> load -source tftp://<your tptp server>/path/file.pkg

After the update FMM reboots by itself. Let the FMM come to normal root prompt.
login as root.

IMPORTANT: AT THIS STAGE DO NOT POWER CYCLE THE FMM, UNTIL ALL STEPS ARE
COMPLETED. If any of the following steps fail retry the step or in worst
case reboot FMM by typing running reset command. It will bring FMM back to
linux prompt and then retry steps 2 and beyond.

Step 2:
=======
Reboot FMM by typing "reset /FMM" (without quotes), when FMM is booting and
about to start Diagnostics and when you see the following message:

<DIAGS> ncgf-fmm Service Processor POST - Start

Type "xyzzy" (without quotes) and hit enter.
Please note that there is no echo of what you type. You just have to type
as FMM is printing other messages and wait for FMM to finish diagnostics.
After diags are finished FMM will stop at Preboot prompt as shown below:

Preboot>

Note: typing xyzzy more than once doesn't hurt and if you miss it or fail to
type in time, just let FMM to boot all the way, login as root and run this
step again.

Step 3
======
On Preboot prompt type "uboot" (without quotes) and hit enter. It will take
you to Uboot prompt which looks like:

On uboot prompt, type the command "flctrl pbs version" (without quotes)
It will display the version of the stoneware and a few error messages similar
to the ones shown in the example output. Note down the version number displayed
in the output. We'll compare this version number with the new stoneware later.

If you see the message similar to:
"Permanent environment at 0x0003f000 is not currently valid."
You must run step 4. Otherwise you can skip Step 4.

---------------------Example output for step 3 -----------------------
Preboot>
Preboot> uboot
=>flctrl pbs version
Current Primary Bootstrap StoneWare build: r84360 <------ VERSION #
Checking; Permanent environment at 0x0003f000 is not currently valid.
This U-Boot would set RO_permenv_build='r109674 (Apr 27 2016)'
permenv: Perm-env is not programmed, or RO_K_SP (-1) is invalid or wrong.
Date ='Fri May 20 00:26:22 PDT 2016', Build ='r109923'
uboot @0c0000 OK, kernel @142000 OK, root @340000 OK,
pbsw @eb0000 OK
Date ='Mon Jan 4 14:59:27 EST 2016', Build ='r106541'
uboot @20c0000 OK, kernel @2142000 OK, root @2340000 OK
....done
Build of new PBSW within ILOM package: r109755
=>
------------------------ End of example output ------------------------

Step 4
=======
At the uboot prompt type permenv and hit enter.
We intend to change "Service Processor hardware model" to 96 and
"Number of MAC addresses on label" to 0 so that stoneware update goes through
smoothly. See actual output below and do the same.

IMPORTANT: Run this step even if the values already appear to be 96 and 0
respectively.

---------------- Example output for Step 4 --------------------------
=>
=>permenv
Checking; Permanent environment at 0x0003f000 is not currently valid.

Choices for SP hardware model (these are VI_SP_* codes):
83 = pilot3evb 96 = ncgf-fmm
90 = x4_4 90 = x4_8
90 = x4_ex 90 = nebula32
84 = sparc_t5-5 84 = sparc_t5-2
84 = sparc_t5-4 95 = sparc_t7-10
95 = sparc_t7-11 95 = sparc_t7-12
86 = river_main 87 = river_proxy
84 = sparc_t5-6 91 = x5_2
91 = x5_2l 91 = nx5_2
91 = qx5_4 98 = nm3_leaf
Press Enter by itself to reach the next question.

Service Processor hardware model? [98] 96 <===== Type 96 here and enter
Service Processor hardware model? [96]
Answer 0 for MACs on label if SP MACs do not belong in perm-env.
Number of MAC addresses on label (6 to 10)? [0] 0 <== Type 0 here and enter
Number of MAC addresses on label (6 to 10)? [0]
Will set RO_K_SP=96 (NCGF_FMM_PILOT3)
Will set 'RO_SP_PLATFORM=ncgf-fmm'
Will set RO_IMAGE0_ADDR_HINT=0xc0000
Will set 'RO_permenv_build=r89593 (Jun 18 2014)'
Enter 'y' to program permanent settings [no]: y
Stored 128 stri' - try 'help'rm. environment at 0x3f000.
=>
------------- End of example output -------------------------------

You may want to run "flctrl pbs version" again to see if that error message
about permenv has gone away. This is optional.

Step 5 (Update the stoneware):
===============================
Now update the stoneware by running the command "flctrl pbs update-sw" as
illustrated below. Ignore the output messages about SP_debug jumper. This
command automatically extracts stoneware from already updated firmware image
and programs it in the right place the flash:

------------------- Example output for Step 5 -----------------------
=>
=> flctrl pbs update-sw
Current Primary Bootstrap StoneWare build: r84360
Checking; Permanent environment at 0x0003f000 IS currently valid.
Perm-env has RO_permenv_build='r109674 (Apr 27 2016)'
This U-Boot would set RO_permenv_build='r109674 (Apr 27 2016)'

The SP_Debug jumper must be inserted so this utility can reprogram the
permanent boot sector. Remember to remove the SP_Debug jumper afterward.
Currently the SP_Debug jumper IS inserted.
Build of new PBSW within ILOM package: r109755
.... done
Erased 4 sectors
Copying new PBSW image to permanent boot sector...
Copying saved perm-env back to permanent boot sector...
=>
------------------------- End of example output ----------------------

Step 6:
=======
Now check the stoneware version of the newly programmed stoneware and compare
with the previous version you noted in step 3. Version number and date stamp
should have changed now.

--------------------- Example output for Step 6 -----------------------
=>
=>flctrl pbs version
Current Primary Bootstrap StoneWare build: r109755
Checking; Permanent environment at 0x0003f000 IS currently valid.
Perm-env has RO_permenv_build='r109674 (Apr 27 2016)'
This U-Boot would set RO_permenv_build='r109674 (Apr 27 2016)'
Build of new PBSW within ILOM package: r109755
=>
-----------------------------------------------------------------------

Step 7:
=======
Reset the FMM and let it boot linux. You are done!
Make sure you see the messages similar to following. This indicates that the
stoneware has been updated.

------------------------ Example output for Step 7 -------------------
=>
=>reset
resetting ...
+****
Primary Bootstrap.
Initialize GPIOs
SYSRST = 0x1
Reading RO_Hw_Straps
Searching for packages
Good uboot CRC for data=[*000c0000, len=52cb8] in pkg *0013f800 (crc:
0x1f6a404d)
Good uboot CRC for data=[*000c0000, len=80000] in pkg *00140000 (crc:
0xb2da8288)
Good uboot CRC for data=[*020c0000, len=51ff8] in pkg *0213f800 (crc:
0x23235be9)
Good uboot CRC for data=[*020c0000, len=80000] in pkg *02140000 (crc:
0x771b3403)
Starting U-Boot at 0x000c0000?
.
.
------------------------------ End of example output ------------------

Attachments

This solution has no attachment