Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

M3 Controller BIOS Module is incorporated in the FS1-2 Controller Software Module

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-11218414771>

Applies to:

Symptoms

Before or after an upgrade to 6.1.18 or higher, you may see the error "Package version: unsupported package combination" in the Installed Software and Firmware window:

Cause

The Controller BIOS module is now embedded in the Controller software module, and therefore this Controller BIOS module is no longer needed separately. Unfortunately the Graphical User Interface (GUI) and Command Lines (CLI) have not been updated to take this change in account.

 

Solution

You can ignore this error and select the "Ignore compatibility" option next time you will perform either a Non-Disruptive (NDU) or Disruptive Upgrade (DU).

This issue has been observed both before and after an upgrade to 6.1.18. If unresolved, it may also be seen after upgrades to later releases as well.

If you received a SR (Service Request) for this issue, please read the following carefully:

• If the FS1-2 is running a release below 6.1.18 and reports this error, it likely means that the package "oraclefs-spbios-firmware-060100-031500.x86_64" is missing from one or both Pilot nodes whereas the compatibility matrix is expecting it to be installed on both. You can follow the instructions below to remove this package, however if you remain with a release below 6.1.18, the error will still remain too. It is recommended to upgrade to 6.1.18 or higher and you will have to select the "Ignore compatibility" option during the NDU or DU upgrade.
• If the FS1-2 is running 6.1.18 or a higher release of 6.1.x, and reports this error, it likely means that the package "oraclefs-spbios-firmware-060100-031500.x86_64" is installed in one or both Pilot nodes whereas the compatibility matrix has been updated to remove its reference. You can follow the instructions below to remove this package.

Instructions:

1. Enable SSH access to the Pilot. Refer to <Document 2029847.1> FS System: How to Enable SSH Access to the Pilot.
   
   
2. Open an SSH connection using the physical IP address of the active Pilot.
   
   
3. Verify if the M3 Controller package is installed on the active Pilot:
   
   Example:
   
   [root@pilot1 ~]# rpm -qa | egrep oraclefs-spbios-firmware-060100-031500.x86_64
   
   oraclefs-spbios-firmware-060100-031500.x86_64
    
   
   
   • If the package exists:
     
     
     1. Uninstall the package:
        
        Example:
        
        [root@pilot1 ~]# rpm -e oraclefs-spbios-firmware-060100-031500.x86_64
          
        
        
     2. Confirm that the package has been removed:
        
        Example:
        
        [root@pilot1 ~]# ls /var/images/pds/spbios
        
        ls: cannot access /var/images/pds/spbios: No such file or directory
         
        
   • If the package does not exist, proceed to next step.
     
     
4. Delete the file oraclefs-spbios-firmware-060100-031500.x86_64.rpm if it is existing in any of the following directories:
   
   
   • /rpms/AxiomONE-SW-staged/
   • /rpms/AxiomONE-SW-installed/
   • /rpms/AxiomONE-SW-previous/
     
     
5. Open a separate SSH connection using the physical IP address of the passive Pilot.
   
   
6. Repeat the above step 3-4 on the passive Pilot.
   
   
7. Stop pilotcfg on the passive Pilot:
   
   Example:
   
   [root@pilotX ~]# service pilotcfg stop
     
   
   
8. Restart pilotcfg on the active Pilot:
   
   Example:
   [root@pilotY ~]# service pilotcfg restart
    
9. Wait for the virtual IP (aka public FS1 IP) to come back and start pilotcfg on the passive Pilot, it takes about 1 min 35 sec to complete:
   
   Example:
   [root@pilotX ~]# service pilotcfg start
    
10. Log on to the GUI and verify that both Pilots are in a Normal status and the Software and Firmware page is reporting the correct Package version.
    
    
11. For the FS1-2 that are running 6.1.17 and below, this cosmetic error will still get displayed. You will have to select the "Ignore compatibility" option during the next NDU or DU. Oracle strongly urges all customers to upgrade to the current software version, please refer to <Document 1967797.1> FS System: How to Download Software and Firmware Updates for the FS1-2.

References

This solution has no attachment