Working with configuration data for logical partitions

 

You may need to work with logical partition configuration data, typically, in order to recover from hardware failures, to correct errors, or to perform maintenance after hardware movement.

You can use DST and SST to clear, copy and update configuration data, to configure non-configured disk units, to clear non-reporting resources, to accept a disk unit as a load source, and to delete logical partitions on the server.

The server maintains the configuration data for all logical partitions on the load source of each logical partition. The configuration data maintained on the primary partition is considered the master copy. Problems can occur when the configuration information on the primary partition and a secondary partition conflicts, or after you initialize disk units during an installation.

Use iSeries™ Navigator and Dedicated Service Tools (DST) to work with configuration data for logical partitions.

• Recovering logical partition configuration data
  You can use this option to recover logical partition configuration data if one of your secondary partitions is running the i5/OS^® operating system. This procedure is part of a full server recovery.

• Saving all configuration data
  You can use iSeries Navigator to save logical partition configuration data in a file on your computer. This function is used when all of the secondary partitions on your iSeries are running a guest operating system.

• Restoring all configuration data
  You can use iSeries Navigator to restore all of your configuration data. This function is used when all of the secondary partitions on your iSeries are running a guest operating system and you have saved the configuration data to a file on the computer running iSeries Navigator. This procedure is part of a full server recovery.

• Clearing partition configuration data for logical partitions
  You can clear the configuration data for the topics.

• Updating partition configuration data on all logical partitions
  You can update the configuration data for every active logical partition by copying it manually from the primary partition to all active logical partitions.

• Clearing partition configuration data from non-configured disk units
  When you move disk units among logical partitions or servers, you may need to erase any old configuration data before the server can use the logical partition again.

• Clearing non-reporting resources on logical partitions
  After you add, remove, or move hardware within a server with logical partitions, you may have resources that are no longer available, that are listed twice, or that are no longer on the server. You can clean up these listings so that all non-reporting resources are erased from the configuration data for the logical partition.

• Accepting a disk unit as load source for a logical partition
  If you have recently moved or added disk units either within the server or from another server, they may still contain configuration data. If you do not want to use one of them as the load source, you need to clear the configuration data before proceeding.

• Copying partition configuration data between IPL sources
  Your server may experience a disk read error of logical partition configuration data if you restart from the A or B IPL source, but not both.

• Deleting all of your logical partitions
  There may be a time when you need to erase all your logical partitions to make the server nonpartitioned again.

 

Parent topic:

Troubleshooting logical partitions

Related information
Backup and Recovery