Oracle FS1-2 Flash Storage System
 
Pillar Axiom Replication Engine (MaxRep)
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Applies to:

Symptoms

 In order to ensure a successful disruptive upgrade on FS1-2 systems that have MaxRep3 Engine(s), Protection Plans must be deactivated.

Changes

Previously it was advocated to unregister the MaxRep3 Engine.  But upon attempting to register the MaxRep3 Engine after the disruptive upgrade, customers would have to delete and then recreate all of their Protection Plans because the Array GUID has changed.

Cause

Drive firmware and disruptive upgrades are offline activities and require the FS1-2 to be in a quiesced state.  Since the MaxRep3 Engine mounts LUNs from the FS1-2, those LUNs have to be unmounted.  If the MaxRep3 Engine is shutdown instead, the FS1-2 will enter a non-Normal state and the drive firmware upgrade cannot proceed.

Solution

In order to complete any disruptive upgrade (Software or Drive firmware) on the FS1-2 that have MaxRep3 Engine(s) registered, users must first deactivate all Protection Plans on those MaxRep3 Engine(s).

1. If the configuration has more than 1 MaxRep3 Engine, determine which is the active MaxRep3 Engine:
   1. Log into the browser based MaxRep3 Engine support interface (http://<maxrep IP or FQN>/support) of one of the MaxRep3 Engines.
   2. Under Management Tasks, select Change Configuration Server.
   3. The IP address of the active MaxRep3 Engine will be displayed:
      
       
2. Confirm that all replication services are running:
   1. Under the Task Status and Audit Log, select the Dashboard view.
   2. Using the IP address from step 1, select the proper Host.
   3. Replication Services should say Healthy:
      
       
3. Deactivate all Protection Plans: 
   1. Using the MaxRep3 Engine IP address from step 1, log into the MaxRep3 Engine User Interface (http://<maxrep IP or FQN>/ui).
   2. Select the Protection tab and under Oracle Storage, select Manage Protection Plan.
   3. Select the Deactivate for each plan listed:
      
      
      
   4. Select Deactivate in the pop-up window.
      
      Note: at this time, even though Deactivate was selected, the pop-up will say "Delete" by mistake.  It is safe to proceed if you confirm that the Deactivate Protection option was infact selected.  This issue will be fixed in a later release.
       
   5. Activation Status will change to Deactivation Pending.
   6. When the deactivation process to completes, the Activation Status will change to Inactive.
      
      Note: it may be necessary to click on the value in the Activation Status cell to toggle the update (select "<<Back" in the Activation Status screen to return).
       
      
4. Using PuTTY or a similar terminal emulation program, ssh into the MaxRep3 Engine console using the IP address from step 1.
5. Run the mount command and copy-n-paste the output for safe keeping:
   
   [root@MAXREP ~]# mount
   /dev/sda1 on / type ext4 (rw)
   proc on /proc type proc (rw)
   sysfs on /sys type sysfs (rw)
   devpts on /dev/pts type devpts (rw,gid=5,mode=620)
   tmpfs on /dev/shm type tmpfs (rw)
   /dev/sdb1 on /home type ext4 (rw,noatime,nodiratime)
   /dev/sda2 on /var/crash type ext4 (rw)
   none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
   sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
   /dev/mapper/36000b08414b3030313734383939000ff on /retention01 type ext4 (rw)
   
   
   
6. From the FS1-2, start the Disruptive Upgrade or drive firmware upgrade.
7. Once the FS1-2 upgrade completes, all LUNs should be Green and Online.
8. ssh back into the MaxRep3 Engine console and check the mount command again:
   
   [root@MAXREP ~]# mount
   /dev/sda1 on / type ext4 (rw)
   proc on /proc type proc (rw)
   sysfs on /sys type sysfs (rw)
   devpts on /dev/pts type devpts (rw,gid=5,mode=620)
   tmpfs on /dev/shm type tmpfs (rw)
   /dev/sdb1 on /home type ext4 (rw,noatime,nodiratime)
   /dev/sda2 on /var/crash type ext4 (rw)
   none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
   sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
   
   
   
9. If the mount command output is missing the retention or backup LUNs, in the example above the retention LUN did not mount, then they will need to be manually remounted:
   
   [root@MAXREP ~]# mount -t ext4 /dev/mapper/36000b08414b3030313734383939000ff /retention01
   [root@MAXREP ~]# mount
   /dev/sda1 on / type ext4 (rw)
   proc on /proc type proc (rw)
   sysfs on /sys type sysfs (rw)
   devpts on /dev/pts type devpts (rw,gid=5,mode=620)
   tmpfs on /dev/shm type tmpfs (rw)
   /dev/sdb1 on /home type ext4 (rw,noatime,nodiratime)
   /dev/sda2 on /var/crash type ext4 (rw)
   none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
   sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
   /dev/mapper/36000b08414b3030313734383939000ff on /retention01 type ext4 (rw)
    
10. Verify all Replication Services are "Healthy" from the support interface (step 2 above). 
    1. If any are not running, they will need to be restarted.
    2. Under Management Tasks, select Shutdown/Restart Services.
    3. Select the appropriate Host, select the Restart Replication Services button and then Save Task:
       
        
11. In the FS1-2 GUI, navigate to the System tab and then Status Summary under Alerts and Events to confirm that the Replication Engine Service Status is Normal and Agent Status is All Communicating.  If these services had to be restarted in the previous step, it may take up to 10 minutes to manifest itself in the FS1-2 GUI.
    
     
    
    Note: Do not proceed to the next step until both of the Service Status is "Normal" and the Agent Status is "All Communicating" on the MaxRep3 Engine.  If necessary, contact Oracle Support for assistance.
     
12. Log back into the MaxRep3 Engine user interface and activate all the Protection Plans.
    
    
    
    
    

References

This solution has no attachment