Generic and specific alert traps

SNMP alerts can contain a combination of a generic and a specific alert trap. This list outlines the explanations for each of the possible combinations of generic and specific alert traps.

SNMP alert traps provide information about problems that the storage unit detects. Either you or the service provider must perform corrective action for the following problems, as required:

Generic trap 0 - coldstart
Issued whenever the SNMP agent is reinitializing. Configuration data has changed.
Generic trap 1 - warmstart
Issued whenever the SNMP agent is reinitializing. Configuration data might change.
Generic trap 4 - authenticationFailure
Issued whenever an SNMP message was received but could not be authenticated.
Generic trap 6 - Problem notification and Copy Services traps
The storage unit generates the following specific traps in combination with generic trap 6:
Specific trap 3 - Problem log entry created
This trap displays when a problem log entry is generated in the problem log for the storage unit. The following information is provided for specific trap 3:
ssSystemNotifyTrap=yyyy/MM/dd hh:mm:ss tzn
Manufacturer=IBM
ReportingMTMS=tttt-mmm*ppzzzzz
ProbNm=nnnnn
LparName=SFaESSbc
FailingEnclosureMTMS=tttt-mmm*ppzzzzz
SRC=ssssssssss
EventText=79 char string
Fru1Loc=71 char string
Fru2Loc=71 char string
Fru3Loc=71 char string

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); tttt-mmm is the machine type and model number; ppzzzzz is the serial number (which is a combination of the plant of manufacture and the sequence number); nnnnn is the problem number; SFaESSbc is the logical partition name, which can be ignored for DS6000™; ssssssssss is the system reference code (SRC); and FruNLoc is the location code of hardware resource N, where n is 1, 2, and 3.

Specific trap 100 - Remote mirror and copy links degraded
This trap displays when an established remote mirror and copy path between a primary and secondary logical subsystem pair becomes inoperable, but there is at least one operational path remaining between the two logical subsystems. The following information is provided for specific trap 100:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm LS
PRI: xxx tttt-ooo pp-zzzzz ll
SEC: xxx tttt-ooo pp-zzzzz ll
Path: Type PP PLink SP SLink RC
1: aaaaa bbbb cccccc dddd eeeeee gg
.
.
.
w: aaaaa bbbb cccccc dddd eeeeee gg

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; aaaaa is "ESCON" or "FIBRE"; bbbb is the primary I/O port number; cccccc is the primary link address in hexadecimal format; dddd is the secondary port number for ESCON direct connection or FIBRE (this value is XXXX if you are connected through an ESCON switch); eeeeee is the secondary link address in hexadecimal format; gg is the reason code in hexadecimal format (see Table 1) if there is a problem (otherwise, gg is "OK" if there is no problem); and w represents the last of up to 8 path descriptions. Only established paths are listed.

Table 1 lists remote mirror and copy return codes that can appear for gg.

Table 1. Remote mirror and copy return codes
Return code Return code explanation
X'02'

Initialization failed. The ESCON link rejected threshold was exceeded when attempting to send ELP or RID frames.

X'03'

Timeout. No reason is available.

X'04'

There are no resources available in the primary storage unit for establishing logical paths because the maximum number of logical paths have already been established.

X'05'

There are no resources available in the secondary storage unit for establishing logical paths because the maximum number of logical paths have already been established.

X'06'

There is a secondary storage unit sequence number, or logical subsystem number, mismatch.

X'07'

There is a secondary LSS subsystem identifier (SSID) mismatch, or failure of the I/O that collects the secondary information for validation.

X'08'

The ESCON link is offline. This is caused by the lack of light detection coming from a host, peer, or switch.

X'09'

The establish failed. It is retried until the command succeeds or a remove paths command is run for the path.

Note: 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.
X'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 retried within the storage unit.

X'10'

Configuration error. The source of the error is one of the following:

  1. The specification of the secondary adapter ID does not match the installed ESCON adapter in the primary storage unit.
  2. For ESCON paths, the secondary storage unit destination address is zero and the ESCON director (switch) was found in the path.
  3. For ESCON paths, the secondary storage unit destination address is not zero and an ESCON director does not exist in the path. The path is a direct connection.
X'14'

The fibre-channel path link is down.

X'15'

The maximum number of fibre-channel path retry operations has been exceeded.

X'16'

The fibre-channel path secondary adapter is not remote mirror and copy capable. This could be caused by one of the following conditions:

  • The secondary adapter is not configured properly or does not have the current firmware installed.
  • The secondary adapter is already a target of 32 different logical subsystems (LSSs).
X'17'

The secondary adapter fibre-channel path is not available.

X'18'

The maximum number of fibre-channel path primary login attempts has been exceeded.

X'19'

The maximum number of fibre-channel path secondary login attempts has been exceeded.

X'1A'

The primary fibre-channel adapter is not configured properly or does not have the correct firmware level installed.

X'1B'

The fibre-channel path established but degraded due to a high failure rate.

X'1C'

The fibre-channel path was removed due to a high failure rate.

Specific trap 101 - Remote mirror and copy links are inoperable
This trap displays when an established remote mirror and copy path between a primary and secondary logical subsystem pair becomes inoperable, and there are no other operational paths between the two logical subsystems. The following information is provided for specific trap 101:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm LS
PRI: xxx tttt-ooo pp-zzzzz ll
SEC: xxx tttt-ooo pp-zzzzz ll
Path: Type PP PLink SP SLink RC
1: aaaaa bbbb cccccc dddd eeeeee gg
.
.
.
w: aaaaa bbbb cccccc dddd eeeeee gg

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; aaaaa is "ESCON" or "FIBRE"; bbbb is the primary I/O port number; cccccc is the primary link address in hexadecimal format; dddd is the secondary port number for ESCON direct connection or FIBRE (this value is XXXX if you are connected through an ESCON switch); eeeeee is the secondary link address in hexadecimal format; gg is the reason code in hexadecimal format (see Table 1) if there is a problem (otherwise, gg is "OK" if there is no problem); and w represents the last of up to 8 path descriptions. Only established paths are listed.

Specific trap 102 - Remote mirror and copy links are operational
This trap displays when an established remote mirror and copy path between a primary and secondary logical subsystem pair becomes operational after previously being inoperable. All other established paths between the two logical subsystems are operational. The following information is shown for specific trap 102:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm LS
PRI: xxx tttt-ooo pp-zzzzz ll
SEC: xxx tttt-ooo pp-zzzzz ll
Path: Type PP PLink SP SLink RC
1: aaaaa bbbb cccccc dddd eeeeee gg
.
.
.
w: aaaaa bbbb cccccc dddd eeeeee gg

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; aaaaa is "ESCON" or "FIBRE"; bbbb is the primary I/O port number; cccccc is the primary link address in hexadecimal format; dddd is the secondary port number for ESCON direct connection or FIBRE (this value is XXXX if you are connected through an ESCON switch); eeeeee is the secondary link address in hexadecimal format; gg is the reason code in hexadecimal format (see Table 1) if there is a problem (otherwise, gg is "OK" if there is no problem); and w represents the last of up to 8 path descriptions. Only established paths are listed.

Specific trap 200 - LSS pair consistency group remote mirror and copy pair error
This trap displays when the first remote mirror and copy pair that is associated with the consistency group enters the suspended state because of an error. This trap is managed by automation code. Reporting for this trap is reenabled when either of the following conditions occurs:
  • An extended long busy timeout occurs on the remote mirror and copy pair that is reported in the SNMP trap.
  • A consistency group-created operation is directed to the LSS pair that is associated with the consistency group.
The following information is shown for specific trap 200:
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

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; and kk is the suspension reason code (SRC) in hexadecimal format.

The suspension reason codes explain the cause of the error that suspended the remote mirror and copy group. Table 2 explains the suspension reason codes.

Table 2. Copy Services suspension reason codes
Suspension reason code (SRC) SRC explanation
X'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.

X'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.

X'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 only be returned by the secondary volume.

X'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.

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.

The suspension reason codes explain the cause of the error that suspended the primary remote mirror and copy devices. Table 2 explains the suspension reason codes.

Specific trap 210 - Global Mirror initial consistency group successfully formed
This trap displays when the first consistency group in a Global Mirror configuration has formed successfully. The following information is shown for specific trap 210:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 211 - Global Mirror session is in a fatal state
This trap displays when an error occurs that prevents the formation of a consistency group and that requires you to correct the problem before you can reform the consistency group. The following information is shown for specific trap 211:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 212 - Global Mirror consistency group failure - Retry will be attempted
This trap displays when a consistency group fails to form. The storage unit automatically continues to attempt to form a consistency group. The following information is shown for specific trap 212:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 213 - Global Mirror consistency group successful recovery
This trap displays when a consistency group forms successfully after it had previously failed. The following information is shown for specific trap 213:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 214 - Global Mirror master terminated
This trap displays when a Global Mirror master is terminated by a command. The following information is shown for specific trap 214:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 215 - Global Mirror FlashCopy at remote site unsuccessful
This trap displays when the FlashCopy operation at the remote site failed in a Global Mirror configuration. The following information is shown for specific trap 215:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
Master: xxx tttt-ooo pp-zzzzz
Slave: xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 216 - Global Mirror slave termination unsuccessful
This trap displays when a Global Mirror master receives a Terminate command and is unable to terminate a Global Mirror slave. The following information is shown for specific trap 216:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
Master: xxx tttt-ooo pp-zzzzz
Slave: xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 217 - Global Mirror paused
This trap displays when Global Mirror is paused because of a command received by the Global Mirror master. The following information is shown for specific trap 217:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 218 - Global Mirror number of consistency group failures exceed threshold
This trap displays when Global Mirror has exceeded the allowed threshold for failed consistency group formation attempts. The following information is shown for specific trap 218:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 219 - Global Mirror first successful consistency group after prior failures
This trap displays when Global Mirror has successfully formed a consistency group after one or more formation attempts had previously failed. The following information is shown for specific trap 219:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Specific trap 220 - Global Mirror number of FlashCopy commit failures exceed threshold
This trap displays when Global Mirror has exceeded the allowed threshold of failed FlashCopy commit attempts. The following information is shown for specific trap 220:
ssEventDescr=yyyy/MM/dd hh:mm:ss tzn
-error_description-
UNIT: Mnf Type-Mod SerialNm
xxx tttt-ooo pp-zzzzz
Session ID: qqqq

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); and qqqq is the session identifier.

Related concepts
Notification methods
Related tasks
Enabling support options
Setting up SNMP notifications using the DS CLI
Setting up Call Home, SNMP, and SIM notifications (real-time only)
Related reference
Global Mirror failures
Configure notifications — SNMP
setsnmp
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2004, 2007. All Rights Reserved.