Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Datacenter StorageEnterprise Storage
All Forum Topics
Options

6 Posts

04-14-2021

Greenland

4 Signins

30 Page Views

  • Posts: 6
  • Registered: ‎04-14-2021
  • Location: Greenland
  • Views: 30
  • Message 1 of 12

Expanding DS2200 with a new enclosure

2021-04-14, 23:54 PM

Hi,

I've added an expansion unit to an existing DS2200 enclosure but have few questions.


The DS2200 is running the following firmware

Bundle A Version:GT265R008-03

MC A Version:GXM265R015-01

SC A Version:GTS265R12-01

Expander code version: 5134

 

Upon connecting and powering up the expansion unit the following warning pops up

Firmware versions do not match those in the firmware bundle. (controller: B, mismatched components: EC)

 

I was under the impression that the controller would automagically update the expansion unit. Is that not so? Do I need to upload a new firmware bundle?

 

Follow up question regarding the new expansion unit - is it not possible to create a pool containing only disks from the new unit? I already have two pools with the disks from the main DS2200 split between them. I *think* I would prefer to have a dedicated pool just containing the disks from the new unit, as it will be dedicated to a specific department/task.

 

Sincerely

Mikkel

Reply
Options

738 Posts

08-06-2018

United States of America

896 Signins

9864 Page Views

  • Posts: 738
  • Registered: ‎08-06-2018
  • Location: United States of America
  • Views: 9864
  • Message 2 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 2:45 AM

Hi Mikkel

 

Yes, we recommend to update the same firmware for these DS2200 enclosures when connect two storage.

About the virtual pool creation, you can refer the Lenovo Storage Manager Guide section 5 Working in the Pools topic to setup the pool for the storage.

Reply
Options

425 Posts

03-07-2017

United States of America

2025 Signins

30633 Page Views

  • Posts: 425
  • Registered: ‎03-07-2017
  • Location: United States of America
  • Views: 30633
  • Message 3 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 2:51 AM

Hi MikkelAnd

 

The firmware update procedure must be performed manually. Especially when connecting a new extension to an existing controller, it is recommended to update the firmware before using it. For the firmware update procedure, please refer to Lenovo Storage Manager Gudie page 60 Updating expansion module firmware.

 

You can try to update expansion unit firmware to see if the problems you are experiencing still exist after updating the firmware.

Please feel free to leave your comment, thank you for support Lenovo
Reply
Options

50 Posts

11-09-2018

Bulgaria

91 Signins

770 Page Views

  • Posts: 50
  • Registered: ‎11-09-2018
  • Location: Bulgaria
  • Views: 770
  • Message 4 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 9:37 AM

Hello Mikkel,

The firmware upgrade will be automatic on the 2 paths(one by one) and respectively the ESMs of the new enclosure should be updated. From your output we see only FW for Controller A and its EC code. What you have is inline - G265R008 and 5134 are correct, however we need to have controller B and expansion enclosure ESM A and ESM B versions. Easiest way is to go to CLI and check:

#show enclosures
#show versions detail

Sometimes the upgrade is not triggered, also G265R008 is known to have issues with the FW leveling mechanism. You are running 5 versions behind on the FW code, also since the expansion is added later there might be a slim chance the EC code on the ESMs is newer (higher than 5134) which will not trigger the update and might explain the error you mentioned.  Here is the latest code:

https://datacentersupport.lenovo.com/si/en/products/storage/lenovo-storage/thinksystem-ds2200/4599/downloads/ds547662-lenovo-thinksystem-ds2200ds4200-controller-firmware-update-bundle-gt280r008-for-anyos

As DannyHsueh and RyanTsai mentioned the update should be done manually. I would recommend the FTP method - it is described in the Storage Manger Guide.

Before proceeding, please check the 2 commands and share the output here. Most likely one of the sub-components has mismatching version. This is usually very trivial and easy to fix.

In regards to the Pool question - maximum 2 Pools per system are possible. You can create new DGs and add them to the Pools. Ideally you would want even split of resources. I would encourage you to check best practices section to ensure you have optimal selection of RAID type and number of disks so you don't suffer from poor performance in future.


Regards,
486

Reply
Options

6 Posts

04-14-2021

Greenland

4 Signins

30 Page Views

  • Posts: 6
  • Registered: ‎04-14-2021
  • Location: Greenland
  • Views: 30
  • Message 5 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 10:12 AM

Hi 486,

 

I should have included the full error messages from both controllers - they report identical firmware (as should be expected)

 

Firmware versions do not match those in the firmware bundle. (controller: B, mismatched components: EC)
EVENT ID:#B7187
EVENT CODE:363
EVENT SEVERITY:Error
EVENT TIME:2021-04-15 20:05:15
Midplane Serial Number:
System Name:
System Location:
System Contact:
IP Address:
Bundle A Version:GT265R008-03
MC A Version:GXM265R015-01
SC A Version:GTS265R12-01
Bundle B Version:GT265R008-03
MC B Version:GXM265R015-01
SC B Version:GTS265R12-01


Firmware versions do not match those in the firmware bundle. (controller: A, mismatched components: EC)
EVENT ID:#A7492
EVENT CODE:363
EVENT SEVERITY:Error
EVENT TIME:2021-04-15 19:55:37

Midplane Serial Number:redacted
System Name:
System Location:
System Contact:
IP Address:
Bundle A Version:GT265R008-03
MC A Version:GXM265R015-01
SC A Version:GTS265R12-01
Bundle B Version:GT265R008-03
MC B Version:GXM265R015-01
SC B Version:GTS265R12-01

 

 

I'll get a firmware update scheduled *before* including the new disks in the exisiting pools

 

Mikkel

Reply
Options

6 Posts

04-14-2021

Greenland

4 Signins

30 Page Views

  • Posts: 6
  • Registered: ‎04-14-2021
  • Location: Greenland
  • Views: 30
  • Message 6 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 10:25 AM

Hi Ryan,

Having read the document you linked to I seem a difference in my setup - I can only select firmware bundles from the "Update controllers" tab of the Update Firmware function.From the "Expander Firmware" tab it only shows basic info.

 

Is that due to running an older firmware?

 

 

Reply
Options

50 Posts

11-09-2018

Bulgaria

91 Signins

770 Page Views

  • Posts: 50
  • Registered: ‎11-09-2018
  • Location: Bulgaria
  • Views: 770
  • Message 7 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 13:17 PM

Thanks for the outputs. Your expansion enclosures are running older code. The "EC" stands for Expander Controller and is the code running on the SAS expander inside each ESM(IOM). The 2 DS controllers also have EC code as seen, and it is 5134 (equivalent to G265R008-03 or 5.1.0.52 depending where in the logs you look). The enclosure is with 512C(I can't find exactly but it is earlier older G265 code-  R007/R006/R004 one of those). If you look at the events both controllers /or paths/ are reporting EC code error - which is expected since they are outdated. Just flash the bundle of the DS and it will take care of the EC code on both ESMs. One path at a time is being flashed. You can't manually update just the expansions... at least not from GUI or with the standard bundle in the Lenovo portal.


One more thing as I almost forgot... You need to run the upgrade on 2 passes. You need to first flash to G265R010-06 otherwise you are running a risk of hitting a bug related with the ambient temperature sensor.

It is described in the below article:

https://datacentersupport.lenovo.com/si/en/products/storage/lenovo-storage/thinksystem-ds2200/4599/solutions/ht509936-lenovo-storage-ds-series-2u-enclosure-reports-temperature-above-threshold-43c-lenovo-storage

 

R010-06 code

https://datacentersupport.lenovo.com/si/en/downloads/DS540680

 

To summarize:

- Flash to G265R010-06 - it will take ~ 30-40 minutes
- Flash to G280R008

 

This should solve the issue with the error you are getting.

 

Regards,
486

Reply
Options

6 Posts

04-14-2021

Greenland

4 Signins

30 Page Views

  • Posts: 6
  • Registered: ‎04-14-2021
  • Location: Greenland
  • Views: 30
  • Message 8 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 13:35 PM

Hi 486,

 

That's bloody marvelous :)

 

I already gathered it was a multistep process going from the older firmware to the latest one, but was under the impression that I needed to do

Step 1: lnvgy_fw_storage_gt265r010-06_anyos_noarch

Step 2: lnvgy_fw_storage_gt280r002-03_anyos_noarch

Step 3: lnvgy_fw_storage_gt280r008_anyos_noarch

 

I read https://datacentersupport.lenovo.com/si/en/products/storage/lenovo-storage/thinksystem-ds2200/downloads/DS547662 and it says 

 

--------------------------------------------------------------------------
2.0 Prerequisites and dependencies
--------------------------------------------------------------------------

Prerequisite: GT280R002-03

 

Is that not the case? 

 

One additional question that I'm pretty sure I know the answer to, but the firmware process is entirely online but should be done during off hours with minimal activity on the system. Right?

 

/mikkel

Reply
Options

50 Posts

11-09-2018

Bulgaria

91 Signins

770 Page Views

  • Posts: 50
  • Registered: ‎11-09-2018
  • Location: Bulgaria
  • Views: 770
  • Message 9 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-15, 13:50 PM

Mikkel,

I'm pretty certain you can skip the G280R002 - the way documents for these are organized is that they can't refer to older branch/generation of the code. In your instance G265 level. I've seen cases where we had G250 go to latest build with no issues. Still, for your piece of mind if you prefer go ahead and do the 3 step upgrade although I think might not be required. 

As for your other question - : ) you are correct - can be done online while you serve data, but is not recommended and best course would be maintenance window or low IO time frame to be selected.

In any case, please update here for the results : )

486

Reply
Options

6 Posts

04-14-2021

Greenland

4 Signins

30 Page Views

  • Posts: 6
  • Registered: ‎04-14-2021
  • Location: Greenland
  • Views: 30
  • Message 10 of 12

Re:Expanding DS2200 with a new enclosure

2021-04-18, 12:03 PM

@ 486DX2 wrote:

Mikkel,

I' pretty certain you can skip the G280R002 - the way documents for these are organized is that they can' refer to older branch/generation of the code. In your instance G265 level. I' seen cases where we had G250 go to latest build with no issues. Still, for your piece of mind if you prefer go ahead and do the 3 step upgrade although I think might not be required. 

As for your other question - : ) you are correct - can be done online while you serve data, but is not recommended and best course would be maintenance window or low IO time frame to be selected.

In any case, please update here for the results : )

486

 

Just a brief follow up.

Did a full backup the between Friday and Saturday and started the firmware update Saturday morning (v GT265R010-06) - all went exceedingly well initially. The firmware of the controllers and expansion module were upgraded. 

However, my two VMware hosts lost all connectivity to the presented LUNs. Rescanning the HBAs did nothing and storage was unavailable.

Rebooted one host and when that came back up storage was available (and HA started all my servers back up again).
Rebooted the other host and got storage back there as well.

 

After that scare i held back on upgrading to the latest 280 firmware.

 

Followup question: From the GUI I can still see old errors related to mismatch firware, and can't seem to find a way to clear them?

 

/mikkel

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms