SIMs for Dynamic Provisioning

Provisioning Guide for VSP One Block

Version
10.2.x
Audience
anonymous
Part Number
MK-23VSP1B012-00

Service information messages (SIMs) report the status of Dynamic Provisioning V-VOLs and pools when specific events occur. If an event associated with a pool occurs, a SIM and an SNMP trap are reported.

An example of a SIM condition is when the used capacity of a pool reaches or exceeds the warning threshold set for the pool. For example, if the warning threshold is set to 50% and the used capacity of the pool reaches or exceeds 50%, a SIM and an SNMP trap are reported.

This table lists and describes the SIM reference codes associated with Dynamic Provisioning operations and provides solutions for the conditions.

SIM code

(SIM level)

Event

Thresholds or values

Types of reports

Solutions

Sent to host?

Sent to maintenance personnel?

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

Yes

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

  • Remove pools that are not used.
  • Remove V-VOLs that are not used.
  • Shrink the pool capacities.

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.
      • Reclaim zero pages to release pages in which zero data are stored.
      • Delete V-VOLs that are not used.*
    • 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 in CCI.

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 zero data pages to release pages in which zero data are stored.

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 zero data pages to release pages in which zero data are stored.

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 zero data pages to release pages in which zero data are stored.

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 zero data pages to release pages in which zero data are stored.

62Dxxx

(Moderate)

xxx = hexadecimal pool number

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

90%

Yes

No

Solutions

  • Verify the available pool capacity, and then increase the pool capacity.
  • Reclaim zero data pages to release pages in which zero data are stored.

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 DDP 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 DP-VOLs

None

Yes

Yes

If a deduplication system data volume is associated with the pool of the selected DP-VOLs, take the following actions.

  1. Back up the data of all DP-VOLs that are associated with the pool and for which Deduplication Data shows Enabled.
  2. Block DP-VOLs in the following order:

    1. All DP-VOLs for which Deduplication Data shows Enabled

    2. All deduplication system data volumes

  3. Select the pool with which deduplication system data volumes are associated, and initialize the duplicated data.
  4. Format all volumes that are associated with the pool in the following order:

    1. All deduplication system data volumes (data store)

    2. All DP-VOLs for which Deduplication Data shows Enabled

  5. Verify the compression accelerator settings for the DRD-VOLs with deduplication data enabled (with deduplication and compression enabled) in the pool initialized in step 3, and for the deduplication system data volumes (data store) in the pool.
  6. Retry the operation of changing the setting of the capacity saving.
  7. Restore the backup data. If a deduplication system data volume is not associated with the pool, block and format the selected DP-VOLs, and then retry the operation.

681xxx

(Moderate)

xxx = hexadecimal pool number

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

None

Yes

No

Take the following actions:

  1. Block DP-VOLs in the following order:

    1. All DP-VOLs for which Deduplication Data shows Enabled

    2. All deduplication system data volumes

  2. Select the pool with which deduplication system data volumes are associated, and initialize the duplicated data.
  3. Format all volumes that are associated with the pool in the following order:

    1. All deduplication system data volumes (data store)

    2. All DP-VOLs for which Deduplication Data shows Enabled

  4. Verify the compression accelerator settings for the DRD-VOLs with deduplication data enabled (with deduplication and compression enabled) in the pool initialized in step 3, and for the deduplication system data volumes (data store) in the pool.
  5. Delete deduplication system data volumes 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.
  • Capacity Saving Status of DP-VOLs indicates Deleting Volume, and if the progress cannot be increased, see the troubleshooting for Dynamic Provisioning.
* If you delete DP-VOLs for which the compression accelerator function setting is compression only or duplication and compression, the deletion processing might increase the pool usage.