SIMs for Dynamic Provisioning

623xxx

(Moderate)

xxx = hexadecimal pool number

Error occurred in the Dynamic Provisioning pool

None

Yes

Yes

Contact customer support.

624000

(Moderate)

No space in the shared memory

None

Yes

No

Perform one of the following actions to increase free space on shared memory:

• Remove pools that are not used. (See the raidcom delete pool command.)
• Remove V-VOLs that are not used. (See the raidcom delete ldev command.)
• Shrink the pool capacities. (See the raidcom delete pool command.)

627xxx

(Moderate)

xxx = hexadecimal pool number

Pool-VOL is blocked

None

Yes

Yes

Contact customer support.

628000

(Service)

Protect attribute of Data Retention Utility is set

None

Yes

Yes

1. Perform the following actions depending on the V-VOL protection function setting.
   • If Protect V-VOLs when I/O fails to Full Pool is enabled, perform one of the following actions to solve the full pool problem:
     • Add pool-VOLs to the pool to increase the free space in the pool. (See the raidcom add dp_pool command.)
     • Reclaim a zero data page to release a page in which zero data is stored.
     • Delete V-VOLs that are not used. (See the raidcom delete ldev command.)
   • If Protect V-VOLs when I/O fails to Blocked Pool VOL is enabled, perform either of the following actions:
     • Contact customer support to restore the pool-VOL.
     • If the blocked pool-VOL is an external volume, verify the status of the path blockade and the external storage system.
2. After taking actions in step 1, release the protect attribute of the V-VOL by using the raidvchkset command.

629xxx

(Moderate)

xxx = hexadecimal pool number

In the Dynamic Provisioning pool, the used capacity reserved for writing exceeded the Warning Threshold.

1% to 100% (in 1% increments)

Default: 70%

Yes

No

Perform one of the following actions to increase free space in the pool:

• Verify the available pool capacity, and then increase the pool capacity.
• Reclaim a zero data page to release a page in which zero data is stored.
• Delete V-VOLs that are not used. (See the raidcom delete ldev command.)

62Axxx

(Moderate)

xxx = hexadecimal pool number

In the Dynamic Provisioning pool, the capacity reserved for writing is full.

100%

Yes

No

Perform one of the following actions to increase free space in the pool:

• Verify the available pool capacity, and then increase the pool capacity.
• Reclaim a zero data page to release a page in which zero data is stored.
• Delete V-VOLs that are not used. (See the raidcom delete ldev command.)

62B000

(Moderate)

In the Dynamic Provisioning pool, the used capacity reserved for writing continues to exceed the highest pool threshold. SOM 734 must be enabled. If SOM 734 is set to ON, the SIM is output every eight hours.

Highest pool threshold of Dynamic Provisioning

Yes

No. If SOM 741 is set to ON, the SIM trap is reported to maintenance personnel.

Perform one of the following actions to increase free space in the pool:

• Verify the available pool capacity, and then increase the pool capacity.
• Reclaim a zero data page to release a page in which zero data is stored.
• Delete V-VOLs that are not used. (See the raidcom delete ldev command.)

62Cxxx

(Moderate)

xxx = hexadecimal pool number

In the Dynamic Provisioning pool, the used capacity reserved for writing exceeded the Depletion Threshold.

1% to 100% (in 1% increments)

Default: 80%

Yes

No

Perform one of the following actions to increase free space in the pool:

• Verify the available pool capacity, and then increase the pool capacity.
• Reclaim a zero data page to release a page in which zero data is stored.
• Delete V-VOLs that are not used. (See the raidcom delete ldev command.)

633xxx

(Moderate)

xxx = hexadecimal pool number

The processing is suspended because a failure occurred when one of following operation is being performed on a DP pool.

• Creating pool
• Expanding pool
• Deleting pool

LDEVs or parity groups that a pool does not contain might remain.

None

Yes

Yes

Contact customer support.

680001

(Moderate)

Failure occurred while performing the capacity saving function

None

Yes

Yes

Follow the instructions in Actions to take when SIM 680001 is output.

680002

(Moderate)

Failure occurred while deleting V-VOLs

None

Yes

Yes

If a DSD-VOL is associated with the pool of the selected V-VOLs, take the following actions.

1. Back up the data on both of the following volumes:
   • All V-VOLs with deduplication data enabled that are associated with the pool
   • A V-VOL with the vClone attribute that belongs to a family of a V-VOL with the vClone Parent attribute enabled and with deduplication data enabled
2. Block V-VOLs in the following order:
   1. All V-VOLs with the vClone attribute that belong to the family of the V-VOL with the vClone Parent attribute enabled and with deduplication data enabled
   2. All V-VOLs with deduplication data enabled
   3. All DSD-VOLs
3. Select the pool with which DSD-VOLs are associated, and initialize the duplicated data.
4. Format V-VOLs in the following order:
   1. All DSD-VOLs (data store)
   2. All V-VOLs with the vClone attribute that belong to the family of the V-VOL with the vClone Parent attribute enabled and with deduplication data enabled

      Caution: Performing this operation changes the vClone Parent attribute of the V-VOLs with the vClone Parent attribute in the family to disabled.

   3. All V-VOLs with deduplication data enabled
5. Verify the compression accelerator settings for the V-VOLs with deduplication data enabled (with deduplication and compression enabled) in the pool initialized in step 3, and for the DSD-VOLs (data store) in the pool. (See the raidcom modify ldev command.)
6. Retry the operation of changing the setting of the capacity saving.
7. Re-create the V-VOL with the vClone attribute.
8. Restore the backup data.

   If a DSD-VOL is not associated with the pool, block and format the selected V-VOLs, and then retry the operation.

681xxx

(Moderate)

xxx = hexadecimal pool number

Deduplication system data volumes cannot be deleted. Failure occurred while deleting the DSD-VOLs, then the processing terminated abnormally.

None

Yes

No

Take the following actions:

1. Block V-VOLs in the following order:
   1. All V-VOLs with the vClone attribute that belong to a family of a V-VOL with the vClone Parent attribute enabled and with deduplication data enabled
   2. All V-VOLs with deduplication data enabled
   3. All DSD-VOLs
2. Select the pool with which DSD-VOLs are associated, and initialize the duplicated data.
3. Format V-VOLs in the following order:
   1. All DSD-VOLs (data store)
   2. All V-VOLs with the vClone attribute that belong to the family of the V-VOL with the vClone Parent attribute enabled and with deduplication data enabled

      Caution: Performing this operation changes the vClone Parent attribute of the V-VOLs with the vClone Parent attribute in the family to disabled.

   3. All V-VOLs with deduplication data enabled
4. Verify the compression accelerator settings for the V-VOLs with deduplication data enabled (with deduplication and compression enabled) in the pool initialized in step 3, and for the DSD-VOLs (data store) in the pool. (See the raidcom modify ldev command.)
5. Delete DSD-VOLs by using the CCI command, raidcom modify pool -pool -delete dsd_volumes.

682000

(Moderate)

Deduplication system data volumes cannot be deleted from the pool, and the deleting process is stopped.

None

Yes

No

Verify the configuration information, and then take the following actions.

• The maintenance operation must be completed.
• If LDEVs cannot be created or deleted, retry the operation.