Return code	Description
02	The initialization failed. The ESCON link reject threshold is exceeded when you attempt to send ELP or RID frames.
03	There is a timeout. No reason is available.
04	There are no resources available in the primary storage unit for establishing logical paths because the maximum number of logical paths are already established.
05	There are no resources available in the auxiliary storage unit for establishing logical paths because the maximum number of logical paths are already established.
06	There is an auxiliary storage unit sequence number, or logical subsystem number, mismatch.
07	There is a secondary LSS subsystem identifier (SSID) mismatch, or failure of the I/O that collects the secondary information for validation.
08	The ESCON link is offline. This situation is caused by the lack of light detection that is coming from a host, peer, or switch.
09	The establish failed. It is tried again until the command succeeds or a remove paths command is run for the path. The attempt-to-establish state persists until the establish path operation succeeds or the remove Remote Mirror and Copy paths command is run for the path.
0A	The primary storage unit port or link cannot be converted to channel mode if a logical path is already established on the port or link. The establish paths operation is not tried within the storage unit.
10	Configuration error. The source of the error is one of the following conditions: •The specification of the SA ID does not match the installed ESCON adapters in the primary controller. •For ESCON paths, the auxiliary storage unit destination address is zero and an ESCON Director (switch) was found in the path. •For ESCON paths, the auxiliary storage unit destination address is not zero and an ESCON director does not exist in the path. The path is a direct connection.
14	The Fibre Channel path link is down.
15	The maximum number of Fibre Channel path retry operations is exceeded.
16	The Fibre Channel path secondary adapter is not Remote Mirror and Copy capable. This situation might be caused by one of the following conditions: •The secondary adapter is not configured correctly or does not have the current firmware installed. •The secondary adapter is already a target of 32 different logical subsystems (LSSs).
17	The secondary adapter Fibre Channel path is not available.
18	The maximum number of Fibre Channel path primary login attempts is exceeded.
19	The maximum number of Fibre Channel path secondary login attempts is exceeded.
1A	The primary Fibre Channel adapter is not configured correctly or does not have the correct firmware level installed.
1B	The Fibre Channel path is established but is degraded because of a high failure rate.
1C	The Fibre Channel path was removed because of a high failure rate.

Triggering this alert: This alert can also be triggered depending on your actions. For example, the alert is triggered if you manually suspend the replication.

Note: The SNMP traps 221 to 224 are used for other purposes: •SNMP traps 221 and 223 is sent for Extent Space Efficient (ESE) volume or Extentpool warnings. •SNMP trap 222 is sent if the Encryption Key Management has issued an alert •SNMP trap 224 is used when a rank reaches I/O saturation.

Suspension reason code (SRC)	Description
03	The host system sent a command to the primary volume of a Remote Mirror and Copy volume pair to suspend copy operations. The host system might have specified either an immediate suspension or a suspension after the copy completed and the volume pair reached a Full Duplex state.
04	The host system sent a command to suspend the copy operations on the secondary volume. During the suspension, the primary volume of the volume pair can still accept updates but updates are not copied to the secondary volume. The out-of-sync tracks that are created between the volume pair are recorded in the change recording feature of the primary volume.
05	Copy operations between the Remote Mirror and Copy volume pair were suspended by a primary storage unit secondary device status command. This system resource code can be returned only by the secondary volume.
06	Copy operations between the Remote Mirror and Copy volume pair were suspended because of internal conditions in the storage unit. This system resource code can be returned by the control unit of either the primary volume or the secondary volume.
07	Copy operations between the Remote Mirror and Copy volume pair were suspended when the auxiliary storage unit notified the primary storage unit of a state change transition to the simplex state. The specified volume pair between the storage units is no longer in a copy relationship.
08	Copy operations were suspended because the secondary volume was suspended as a result of internal conditions or errors. This system resource code can be returned only by the primary storage unit.
09	The Remote Mirror and Copy volume pair was suspended when the primary or auxiliary storage unit was rebooted or when the power was restored. The paths to the auxiliary storage unit might not be disabled if the primary storage unit was turned off. If the auxiliary storage unit was turned off, the paths between the storage units are restored automatically, if possible. After the paths are restored, run mkpprc to resynchronize the specified volume pairs. Depending on the state of the volume pairs, you might have to run rmpprc to delete the volume pairs and run mkpprc to reestablish the volume pairs.
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 be returned only if a primary volume was queried.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.1	The state of session X has transitioned to Defined.
1.3.6.1.4.1.2.6.208.0.2	The state of session X has transitioned to Preparing.
1.3.6.1.4.1.2.6.208.0.3	The state of session X has transitioned to Prepared.
1.3.6.1.4.1.2.6.208.0.4	The state of session X has transitioned to Suspended.
1.3.6.1.4.1.2.6.208.0.5	The state of session X has transitioned to Recovering.
1.3.6.1.4.1.2.6.208.0.6	The state of session X has transitioned to Target Available.
1.3.6.1.4.1.2.6.208.0.19	The state of session X has transitioned to Suspending.
1.3.6.1.4.1.2.6.208.0.20	The state of session X has transitioned to SuspendedH2H3.
1.3.6.1.4.1.2.6.208.0.21	The state of session X has transitioned to SuspendedH1H3.
1.3.6.1.4.1.2.6.208.0.22	The state of session X has transitioned to Flashing.
1.3.6.1.4.1.2.6.208.0.23	The state of session X has transitioned to Terminating.
1.3.6.1.4.1.2.6.208.0.26	The recovery point objective (RPO) for the role pair of X in session Y has passed the warning threshold of Z seconds.
1.3.6.1.4.1.2.6.208.0.27	The RPO for the role pair of X in session Y has passed the severe threshold of Z seconds.
1.3.6.1.4.1.2.6.208.0.28	A suspend event occurred triggering the auto restart feature for session X. The session will be restarted in Y seconds.
1.3.6.1.4.1.2.6.208.0.29	Session X was enabled for auto restart. However, the session could not be restarted.
1.3.6.1.4.1.2.6.208.0.33	The state of session X has transitioned to Protected.
1.3.6.1.4.1.2.6.208.0.34	The state of session X has transitioned to Unprotected.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.7	One or more copy sets have been added or deleted from this session. An event is sent for each session at least every 15 minutes.
1.3.6.1.4.1.2.6.208.0.8	Peer-to-Peer Remote Copy (PPRC) path definitions has been changed. An event is sent for each path configuration change.
1.3.6.1.4.1.2.6.208.0.30	One or more logical paths between storage systems have entered an error state or have been removed.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.9	The session is in a severe state due to an unexpected error.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.10	Server X has timed out attemptong to communicate with storage system Y.
1.3.6.1.4.1.2.6.208.0.11	Server X has encountered errors attempting to communicate with storage system Y.
1.3.6.1.4.1.2.6.208.0.12	Active server X has terminated communication with standby server Y as a result of communication errors.
1.3.6.1.4.1.2.6.208.0.13	Standby server X has encountered communication errors with active server Y.

Important: For Communication-failure traps, after an SNMP trap for a failure is sent, it is not resent unless communication is reestablished and failed again.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.14	The copy services management server HA connection X → Y has changed state to Unknown (previously Offline).
1.3.6.1.4.1.2.6.208.0.15	The copy services management server HA connection X → Y has changed state to Synchronized.
1.3.6.1.4.1.2.6.208.0.16	The copy services management server HA connection X → Y has changed state to Disconnected Consistent (previously Consistent Offline).
1.3.6.1.4.1.2.6.208.0.17	The copy services management server HA connection X → Y has changed state to Synchronization Pending.
1.3.6.1.4.1.2.6.208.0.18	The copy services management server HA connection X → Y has changed state to Disconnected.

Object ID (OID)	Description
1.3.6.1.4.1.2.6.208.0.31	The scheduled task ibmTPCRtaskname has finished running.
1.3.6.1.4.1.2.6.208.0.32	Scheduled task ibmTPCRtaskname failed due to an error that was encountered while it was running.

Terminology note: Due to space constraints, Table B-9 on page 595 uses the terms MM for Metro Mirror, GM for Global Mirror, and MGM for Metro/Global Mirror.

Error trap code	Remote Copy type	Source error message	Target error message	Possible actions
Trap 100	MM/GM/MGM	PPRC Links Degraded	PPRC Links Degraded	Check connectivity on both sides. The message describes which IOPORT failed. Check whether connectivity is still available for the mentioned ports. At least one path is still available.
Trap 101	MM/GM/MGM	PPRC Links Down	PPRC Links Down	Check connectivity on both sides. The message describes which IOPORT failed. Check whether connectivity is still available for the mentioned ports. All paths are down.
Trap 202	MM/GM/MGM	Primary PPRC Devices on LSS Suspended Due to Error	PPRC Links Down. This error can come first on any of the available systems that are reporting the message.	This error message can be reported after a Trap 102. In this case, it means that the copy was suspended on the primary because of connectivity problems. Recheck the connectivity and resume the PPRC copy.
Trap 202	MM/GM/MGM	Primary PPRC Devices on LSS Suspended Due to Error	None	The PPRC relationship was manually paused or an error with the volume on primary system caused the error. Check the volume status and connectivity and resume operations after you correct the issues. If the volume status depends on the DDM status, call IBM for a complete health check before you continue. This message can also be issued after you remove a PPRC relationship. In this case, no further action is needed.
Trap 218	GM/MGM	Global Mirror Number of consistency group failures exceed threshold	None	Check the connectivity and bandwidth capacities. Recheck your session’s configurations on GM/MGM. Also, this error can appear when the secondary site has issues with the LUNs.
Trap 219	GM/MGM	Global Mirror First successful Consistency Group after prior failures	None	There is no needed action for this trap. It means only that it can successfully restore after a previous failure.
Trap 210	GM/MGM	Global Mirror Master terminated	None	The session was manually terminated. Reestablish a new session between the primary / secondary or tertiary site.
Trap 221	GM/MGM	Devices on LSS suspended due to error	Space-Efficient Repository or Over-provisioned Volume has reached a warning watermark.	Check for your ESE repositories sizes. Resume PPRC operations after you correct the problem.
Trap 223	MM/GM/MGM	Extent Pool capacity threshold reached	None or Extent Pool capacity threshold reached.	Check for your ESE repositories sizes. Resume PPRC operations after you correct the problem.