FlashSystem Partnership Error

I’ve installed dozens of IBM FlashSystem storage units throughout the years and replication on about a third of them primarily for migration. But I recently had a different experience.

When attempting to create a partnership between a FlashSystem FS5200 with code level (8.4.2.1) and a FlashSystem FS5300 with code level 8.7.0.2, though we zoned them correctly via their REAL WWPNs, the GUI reported nothing was found on the fiber. Upon further review,  we discovered that the  system “layer” setting differed on the two units via the lssystem command as shown below:

IBM_FlashSystem:P9FS5200:superuser>lssystem |grep layer

layer storage

IBM_FlashSystem:P10FS5300:superuser>lssystem |grep layer

layer replication

 This is because the default system layer changed to replication in 8.6.3. In order to establish a proper relationship the system layer setting MUST match.

More information on system layers can be found at: https://www.ibm.com/docs/en/flashsystem-c200/9.1.0?topic=system-layers


When attempting to change the original FS5200 to replication, which is the recommendation, to match the FS5300, another error was encountered about other system/cluster nodes were detected.

This is because the zoning in place, does allow them to “see” other but not effectively talk to each other. So the resolution was to stop the communication between them. This can be done by removing the zone, disabling the port(s) the new storage unit is attached to, or physically unplugging the cables designated for the replication. In our case, we removed the zone. Then run the command below to change the layer on the FS5200 to match the new FS5300 (and is the recommendation) and then zone it back.

Disabled the zone.

Executed: chsystem -layer replication

Enable the zone.

This inturn allowed us to create the partnership successfully.

Flashsystem GUI USB Drive Issue

I’ve installed dozens of IBM FlashSystem storage units throughout the years. Over a few month period from the end of 2024 until March or so of 2025 I performed ~5 IBM Flashsystem installs. The models were mostly FS5300 but this problem wasn’t limited to just that model. Which is means it most likely was a software code level issue, but yet I’ve never been able to find a known issue/defect about it.

Long story short, when creating the USB encryption keys the GUI would never acknowledge the USB keys were inserted to continue. Tried several different browsers that didn’t seem to matter either. So ultimately the only way we were able to do so was via the CLI shared below. If anybody knows an exact level this affects I would gladly update this article to include it. Drop me an email at sbodily@cleartechnologies.net

The steps below are available at https://www.ibm.com/docs/en/flashsystem-9×00/9.1.0?topic=drives-enabling-encryption-usb-flash

To enable the encryption that uses USB flash drives, enter the following command:

chencryption -usb enable

Verify via the lsencryption command output as italicized below.

  • status enabled
  • error_sequence_number….

Insert the USB keys. Enter the following command to prepare a new USB master key:

chencryption -usb newkey -key prepare

The new key has been created successfully when the usb_rekey_filename field shows the name of the new key upon executing lsencryption command as shown below in italics.

  • status enabled
  • error_sequence_number
  • usb_rekey no
  • usb_key_copies 4
  • usb_key_filename encryptionkey_alphanum_alphanum_fsname
  • usb_rekey_filename
  • keyserver_status licensed
  • keyserver_rekey no_key
  • keyserver_pmk_uid
  • keyserver_pmk_rekey_uid
  • recovery_key_status enabled
  • recovery_key_rekey no
  • recovery_key_name recoverykey_alphanum_alphanum_fsname
  • recovery_key_rekey_name

After all copies are completed, run the following command to complete the enablement process:

chencryption -usb newkey -key commit