IBM DS8000 User Manual page 192

Hide thumbs Also See for DS8000:
Table of Contents

Advertisement

164
DS8000 User's Guide
Table 6. Copy Services suspension reason codes (continued)
Suspension
reason code
(SRC)
SRC explanation
X'07'
Copy operations between the remote mirror and copy volume pair were
suspended when the secondary storage unit notified the primary storage
unit of a state change transition to simplex state. The specified volume pair
between the storage units is no longer in a copy relationship.
X'08'
Copy operations were suspended because the secondary volume became
suspended as a result of internal conditions or errors. This system resource
code can only be returned by the primary storage unit.
X'09'
The remote mirror and copy volume pair was suspended when the primary
or secondary storage unit was rebooted or when the power was restored.
Note: The paths to the secondary storage unit might not be disabled if the
primary storage unit was turned off. If the secondary storage unit was
turned off, the paths between the storage units are restored automatically, if
possible. After the paths have been restored, issue the mkpprc command to
resynchronize the specified volume pairs. Depending on the state of the
volume pairs, you might have to issue the rmpprc command to delete the
volume pairs and reissue a mkpprc command to reestablish the volume
pairs.
X'0A'
The remote mirror and copy pair was suspended because the host issued a
command to freeze the remote mirror and copy group. This system resource
code can only be returned if a primary volume was queried.
Specific trap 202 - Primary remote mirror and copy devices on the LSS
were suspended because of an error
This trap displays when one or more primary remote mirror and
copy devices become suspended because of an error that occurs
over a 5-second period. The trap information indicates first pair to
suspend as well as all of the primary devices on the primary
logical subsystem that were suspended because of the error. The
following information is shown for specific trap 202:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm LS LD SR
PRI: xxx tttt-ooo pp-zzzzz ll jj kk
SEC: xxx tttt-ooo pp-zzzzz ll jj
Start: yyyy/mm/dd hh:mm:ss tzn
PRI Dev Flags (1 bit/Dev, 1=Suspended):
fffffffffff...ffffffffffffffff
where yyyy/MM/dd hh:mm:ss tzn is the time that the alert was sent
(year, month, day, hour, minute, second, and time zone);
-error_description- is the event description; xxx is the manufacturer;
tttt-ooo is the machine type and model number; pp-zzzzz is the
serial number (a combination of the plant of manufacture and the
sequence number); ll is the LSS number in hexadecimal format; jj is
the logical volume number in hexadecimal format; kk is the
suspension reason code in hexadecimal format; and
fffffffffff...ffffffffffffffff represents 256 1-bit flags, one per
primary device on the primary LSS that are shown as a
64-character hexadecimal number. The time indicated on the Start
line is the beginning of the error condition period. The time that
the alert is sent (as shown on the first line of the trap) indicates the
end of the error condition period.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents