Checking Exalogic 2.0.1.1.0 Readiness
Back to overview

Checking Exalogic 2.0.1.1.0 Readiness

Published on: Category: Oracle

The new Exalogic stack version 2.0.1.1.0 brings PaaS style virtualization to the Exalogic by introducing Exalogic Control. Our Exalogic quarter rack is currently at version 2.0.0.0.1 (april 2012 PSU). Let’s see if we are ready to upgrade to this new version!

A lot of information can be found in a new manual called the Exalogic Cloud Administration Guide. Here’s what this guide has to say about the minimum required versions to upgrade (see section 3.2) :

3.2 Verifying Firmware and Software Versions
Before reimaging Exalogic compute nodes from Oracle Linux to Oracle VM Server, you must verify that the versions of software and firmware on Exalogic machine components are as follows:

Firmware on Sun Network QDR InfiniBand Gateway Switches (NM2-GW): 2.0.6-1

Firmware on Sun Datacenter InfiniBand Switch 36 (NM2-36P): 2.0.6-1

Sun ZFS Storage 7320 appliance: 2011.04.24.1.0,1-1.8

ILOM and BIOS on storage heads: SW1.4 3.0.16.10 r65138

ILOM and BIOS on compute nodes: SW1.5 3.0.16.10.a r68533

Mellanox InfiniBand card: 2.9.1000

Now checking software versions can be a bit of a challenge if you are not so familiar with the Exalogic platform. Here’s how to do it….

1. Checking the gateway switches

Checking the firmware version on the infiniband switches is fairly simple (see also this post). First login to the switch and and then type the version command :

  1. JNs-MBP3-QA-2:~ jnwerk$ <strong>ssh root@xxxxgw01.qualogy.com
  2. </strong>root@xxxxgw01.qualogy.com's password:
  3. Last login: Fri Jul 27 19:58:19 2012 from 192.168.110.17
  4. You are now logged in to the root shell.
  5. It is recommended to use ILOM shell instead of root shell.
  6. All usage should be restricted to documented commands and documented
  7. config files.
  8. To view the list of documented commands, use "help" at linux prompt.
  9. [root@xxxxgw01 ~]# <strong>version
  10. </strong>SUN DCS gw version: <strong>2.0.6-1
  11. </strong>Build time: Jan 17 2012 14:29:13
  12. FPGA version: 0x33
  13. SP board info:
  14. Manufacturing Date: 2010.12.30
  15. Serial Number: "NCD600077"
  16. Hardware Revision: 0x0006
  17. Firmware Revision: 0x0000
  18. BIOS version: SUN0R100
  19. BIOS date: 06/22/2010

Also check any other infiniband switches you have in your system to be certain they are all running this same version. In our case (we have a quarter rack) we also check the second gateway switch :

  1. [root@xxxxgw02 ~]# <strong>version
  2. </strong>SUN DCS gw version: <strong>2.0.6-1
  3. </strong>Build time: Jan 17 2012 14:29:13
  4. FPGA version: 0x33
  5. SP board info:
  6. Manufacturing Date: 2010.12.31
  7. Serial Number: "NCD600233"
  8. Hardware Revision: 0x0006
  9. Firmware Revision: 0x0000
  10. BIOS version: SUN0R100
  11. BIOS date: 06/22/2010

OK, good : we are at version 2.0.6-1 across the board, as required. Let’s move on the the storage (we cannot check the NM2-36P switch as it only comes on half- and full rack configurations).

2. Checking the storage appliance version

Login to the ILOM of storage head 1 to check the version :

  1. [root@xxxxcn01 ~]# <strong>ssh root@xxxxsn01-c
  2. </strong>Password:
  3. Last login: Tue Apr 17 14:11:42 2012 from 192.168.110.83
  4. xxxxsn01:&gt; maintenance
  5. xxxxsn01:maintenance&gt; system updates
  6. xxxxsn01:maintenance system updates&gt; show
  7. Updates:
  8.  
  9. UPDATE                           DATE                      STATUS
  10. ak-nas@2010.08.17.1.1,1-1.16     2010-11-1 12:46:16        previous
  11. ak-nas@2010.08.17.2.1,1-1.21     2011-3-10 23:49:47        previous
  12. ak-nas@2010.08.17.3.0,1-1.25     2011-4-29 15:48:52        previous
  13. <strong>ak-nas@2011.04.24.1.0,1-1.8      2011-12-21 22:32:50       current
  14. </strong>...
  15. etc.

OK, our current storage version qualifies, as we are on the required version 2011.04.24.1.0,1-1.8. To be thorough, also check storage head 2 :

  1. qnlexasn02:&gt; <strong>maintenance system updates
  2. </strong>qnlexasn02:maintenance system updates&gt; <strong>show
  3. </strong>Updates:
  4.  
  5. UPDATE                           DATE                      STATUS
  6. ak-nas@2010.08.17.1.1,1-1.16     2010-11-1 12:46:16        previous
  7. ak-nas@2010.08.17.2.1,1-1.21     2011-3-10 23:49:47        previous
  8. ak-nas@2010.08.17.3.0,1-1.25     2011-4-29 15:48:52        previous
  9. <strong>ak-nas@2011.04.24.1.0,1-1.8      2011-12-21 22:32:50       current</strong>
  10.  
  11. ...

3. Checking the ILOM and BIOS versions on the storage heads

Now we need to check the ILOM and BIOS firmware on both storage heads, so we log into the ILOM interface on both :

  1. <strong>SN01
  2. </strong> 
  3. # <strong>ssh root@xxxxsn01-c.qualogy.com
  4. </strong>Password:
  5.  
  6. Oracle(R) Integrated Lights Out Manager
  7.  
  8. <strong>Version 3.0.16.10 r65138
  9. </strong> 
  10. Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved.
  11.  
  12. -&gt; version
  13. <strong>SP firmware 3.0.16.10</strong>
  14. <strong>SP firmware build number: 65138</strong>
  15. SP firmware date: Wed Jun 15 08:02:17 EDT 2011
  16. SP filesystem version: 0.1.23
  17.  
  18. <strong>SN02
  19. </strong> 
  20. # <strong>ssh root@xxxxsn02-c.qualogy.com
  21. </strong>Password:
  22.  
  23. Oracle(R) Integrated Lights Out Manager
  24.  
  25. <strong>Version 3.0.16.10 r65138
  26. </strong> 
  27. Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved.
  28.  
  29. -&gt; version
  30. SP firmware 3.0.16.10
  31. SP firmware build number: 65138
  32. SP firmware date: Wed Jun 15 08:02:17 EDT 2011
  33. SP filesystem version: 0.1.23

OK, good, both heads are on the same version and it is the required level 3.0.16.10 r65138. It’s not exactly clear to me what is meant by “checking the BIOS version” here, but as only version 3.0.16.10 r65138 is mentioned it is safe to assume we are OK here.

4. Checking the ILOM and BIOS versions on the compute nodes

Checking the versions on the compute nodes is very similar to the storage heads, as they are both based on SunFire X4170 M2 blade servers. Therefore, to keep things interesting we will do the version check via the ILOM webui this time around :

Go to the Integrated Lights Out Manager webconsole and login, then to the System Information > Overview tab.

Figure 1 : checking the ILOM version via the graphical webui

(by the way : there’s lot’s more useful information and functions to be found in the ILOM interfaces, but that’s for a future post…)

However for “CLI gung-ho” readers, no worries this  can also be done via the terminal by logging into it’s interface via ssh :

  1. JNs-MBP3-QA-2:~ jnwerk$ <strong>ssh root@qnlexacn08-c.qualogy.com
  2. </strong>Password:
  3.  
  4. Oracle(R) Integrated Lights Out Manager
  5.  
  6. <strong>Version 3.0.16.10.a r68533
  7. </strong>...
  8. ...

Note the slight difference in version notation, we’got an extra a here : v3.0.16.10 r65138a

Again it’s not exactly clear what is meant by “checking the BIOS version” here, but as only version 3.0.16.10 r65138a is mentioned it is safe to assume we are OK here.

5. Checking the Mellanox IB version

Our infiniband version needs to be up to date as well :

Mellanox InfiniBand card: 2.9.1000

How do we check this? We can find the infomation in the Exalogic PSU Infrastructure Upgrade Guide [MOS ID 1367093.1]. It turns out we can use the ibstat command for this :

[root@xxxxcn01 ~]# ibstat | grep “Firmware version”

Firmware version: 2.9.1000

=> OK here as well. You can also retreive this information via the CheckHWnFWProfile script in the Exalogic tools.

We have now ascertained that our Exalogic infrastructure is ready for upgrading to the new version 2.0.1.x. We are ready to “rock ’n roll” with Exalogic Control ! Now it’s time to make some backups of what we have, before we put on our “new shoes”….

Publicatiedatum: 13 augustus 2012

Jos Nijhoff
About the author Jos Nijhoff

Jos Nijhoff is an experienced Application Infrastructure consultant at Qualogy. Currently he plays a key role as technical presales and hands-on implementation lead for Qualogy's exclusive Exalogic partnership with Oracle for the Benelux area. Thus he keeps in close contact with Oracle presales and partner services on new developments, but maintains an independent view. He gives technical guidance and designs, reviews, manages and updates the application infrastructure before, during and after the rollout of new and existing Oracle (Fusion) Applications & Fusion Middleware implementations. Jos is also familiar with subjects like high availability, disaster recovery scenarios, virtualization, performance analysis, data security, and identity management integration with respect to Oracle applications.

More posts by Jos Nijhoff
Comments
Reply