Secondary Controller Equallogic PS50

You may not have the same version of the Firmware version on both controllers.

First telnet/ssh to the member IP to check the FW versions of the CM (if this is a group with more than one member, use the member IP address, and NOT the group IP)

Login as grpadmin, then at the group name prompt type the following:

If multi-member group type the following to ensure you are looking at the right member:

GroupName> show member

GroupName> Member select

Then (for both single member group and mulit-member group) type the following

GroupName> Show controller

Look for the entry that is “FW Rev :”  both controllers need to be the same.

If they are different, the fix is a bit involved, and typically (depending on the FW version) is copying the newer of the two CM firmware to the array (via FTP) and running update again.  This is a bit involved, so you may need to call support to have them walk you through it.

-joe

Hi DELL-Joe S,

Thanks for taking the time to respond to my question.  So here is where I'm at now.  I let the controller sit in the unit over night and I came in this morning and much to my surprise I don't see a warning any longer.

Under controllers I see the primary and secondary both battery status and NVRAM status GOOD.  The new controller I installed firmware version 4.1.5(R97813) has now become the primary.  The older controller, now the secondary has firmware version 4.3.4(R112816).  

When I do a 'show member' it shows the version 4.1.5 of the primary, as expected but if the controller were to fail, will it use the secondary running a higher firmware version?

In good practice, both controllers should have the same firmware, but this unit is out of warranty so trying to make it work.

I'm thinking I should try that update one more time, what do you think? 

*edit* Nevermind I tried it again and got the same error, "no update kit files found in /mgtdb/update

Regarding running mixed versions of the firmware on the same array, this is not recommended at all.

However, in your particular instance, the two version of firmware are within the required revisions and you can do an update without the firmware kit file (ex.; the FW cannot be “x” number of revisions apart in order to do this procedure, but in your case, they fall within this limiting factor).

Use the following instructions:

You will first need to failover to the CM with the higher FW version, so that it is the active control module

Note: Remember to "unset CRLF" first, if you're using Microsoft Telnet. If using another terminal program that adds a line feed ensure this is disable (check vendor documentation for how to do this).  

1. Telnet/SSH into the array (again use an IP address from the member - do NOT use group IP, if this is a multi-member group)

2. Login with grpadmin

3. At the GroupName> prompt, Type: restart

This will cause a CM failover (will take 20-45 seconds, so ensure you plan accordingly for this).

Once the CM with the v4.3.4 is the active (primary) CM:

1. Telnet/SSH, Putty into the array

2. At the Groupname> Prompt type: update

3. The Update will then check to see if the secondary controller is running the same version of firmware as the primary

4. In your case, it will not be, so the "update" command will ask permission to copy the current firmware to the passive CM.  Say "y" to allow update to sync the firmware on the passive controller.

5. After the sync (update) completes, the command will then ask you if you now want to do an actual firmware upgrade of the whole array.  Ensure you respond 'no' to this!

6. When completed, restart the array

You may want to check with your sales person to see about getting a support contract. The version of FW you are running is @year old now, and the newer versions have additional features, and data integrity enhancements that my make the cost of the contract and technical support beneficial to you.

-joe

I ran the update and broke the secondary now.  I get the error message 'Array firmware update from version 4.3.4 to failed. Reason: No update kit files found in /mgtdb/update. Aborting update.

I see failed for both the Battery status and NVRAM now on the secondary controller in the GUI. <ADMIN NOTE: Profanity removed as per TOU>

I'm using SecureCRT.  The messaged appeared after I entered "y"

So since I've reboot the unit I see the same firmware on both controllers.  After the reboot I did notice that the Battery Status, and NVRAM battery read FAILED for about 2 to 3 min but eventually turned to good.

Even thought I got that error message, it appears as though the firmware did indeed update.  I run a 'show member' and I see the version 4.3.4

Awesome!  Thanks for the guidance and help Joe.  Very much appreciated!!

Cheers mate!

Are you using ms telnet or putty?

if using MS telent, you need to first type the following command "unset CRLF"

Was that message at step #4, where you are prompted to to answered "y"?

-joe

Excellent… I think what might have happened is that it tried to update both controllers after the sync completed, which is why you got the message (the firmware kit files are needed for this).  I’m not familiar with SecrueCRT, so maybe it inserted a line feed that got you past the second prompt (the default is 'yes').

Since both are at the same version now, you should be set.

-joe