HP XP P9500 User Manual page 56

Table 21 RAID Manager error codes (SSB1 code: b9a0/b9a1/b9a2/b9a5/b9a6/b9ae/b9af)
(continued)
SSB2 code
209e
20a0
20a2
20a3
20a9
20aa
20ab
20b0
20b1
20b4
20b5
20b7
20b8
20d0
20d1
22f6
22f7
22f9
2301
2302
2306
2309
230A
230B
56 Troubleshooting
Description
Because the volume specified as the P-VOL was a Mainframe Fibre Data Migration volume, the pair
operation was rejected.
The specified pairs contain the Continuous Access Synchronous asynchronous volumes. Because the
CLPRs of the P-VOL and S-VOL of the specified pair were different, the quick restore operation was
rejected.
Because the P-VOL was a Thin Provisioning or Smart Tiers V-VOL whose capacity was increasing, the
create pair operation was rejected.
Because the S-VOL was a Thin Provisioning or Smart Tiers V-VOL whose capacity was increasing, the
create pair operation was rejected.
Because the specified consistency group number was being used by Snapshot, the pair operation
was rejected.
Because the volume specified as the P-VOL was a Thin Provisioning or Smart Tiers V-VOL and its zero
data area was being discarded, the pair creation was rejected.
Because the volume specified as the S-VOL was a Thin Provisioning or Smart Tiers V-VOL and its zero
data area was being discarded, the pair creation was rejected.
Because the volume specified as the P-VOL was a Thin Provisioning or Smart Tiers V-VOL and its
capacity was increasing, the pair creation was rejected.
Because the volume specified as the S-VOL was a Thin Provisioning or Smart Tiers V-VOL and its
capacity was increasing, the pair creation was rejected.
Because the volume specified as the P-VOL was a Thin Provisioning or Smart Tiers V-VOL which was
not associated with a pool, the pair operation was rejected.
Because the volume specified as the S-VOL was a Thin Provisioning or Smart Tiers V-VOL which was
not associated with a pool, the pair operation was rejected.
Because no LU path was defined to the volume specified as P-VOL, the pair operation was rejected.
Because no LU path was defined to the volume specified as S-VOL, the pair operation was rejected.
The volume specified as P-VOL rejected operation for creating the pair because THP pool is initializing
in the V-VOL of Thin Provisioning or Smart Tiers.
The volume specified as S-VOL rejected operation for creating the pair because THP pool is initializing
in the V-VOL of Thin Provisioning or Smart Tiers.
Because the volume specified as the P-VOL was a Compatible FlashCopy Version 2 S-VOL, the pair
operation was rejected.
Because the volume specified as the S-VOL was a Compatible FlashCopy Version 2 P-VOL or S-VOL,
the pair operation was rejected.
Because the volume specified as the S-VOL was a Compatible FlashCopy Version 2 P-VOL or S-VOL,
the quick restore or the reverse copy operation was rejected.
The pair operation was rejected because shared memory is not allocated or Business Copy is not
installed.
Because the volume specified as the P-VOL or S-VOL was not the top volume of the LUSE volume, the
pair operation was rejected.
Because the LBA size of the specified P-VOL was not the same as the size of the specified S-VOL, the
pair operation was rejected.
Because the number of pairs exceeded the maximum number of pairs, the pair creation was rejected.
Because the volume specified as the S-VOL was the P-VOL of the Business Copy pair whose MU
number is 0, the pair creation was rejected.
Because the pair was being suspended or deleted, the pair operation was rejected.