05/23/2005 version 2.4.0.3
Analyzing SNMP trap information

   The Enterprise Storage Server (ESS) sends SNMP traps to the addresses that is specified in the
Communication Resources work sheet. The work sheet is filled out during the planning process.
  The ESS generates SNMP traps, which are both product specific and generic alert traps and
supports a read-only management information base (MIB) to allow monitoring by the network.
   A MIB is a schema for defining a tree structure that identifies and defines certain objects
that can be passed between units using an SNMP protocol. The objects passed typically contain
certain information about the product such as the physical  or logical characteristics of the
product.
  For more information about SNMP traps, see the ibm2100.mib and README files that are
available in the SNMP directory on the IBM System Storage Enterprise Storage Server CD, which is
shipped with each ESS.

Product specific alert traps

 Product specific alert traps provide information about hardware or software problems detected
by the ESS that require action by  the service provider or customer.

1) For machine model Fxx, when an error is encountered, the ESS generates the generic trap 6
product specific trap 1.The ESS Service Guide provides information of the problem detected.
Each trap provides the following information:

Problem ID
This  identifier is assigned by the ESS for the particular problem that caused the trap.

Presenting time
The time and date of the most recent problem presented.

Exception symptom code (ESC)
The exception symptom value for the problem ID.

Description
The error condition description for the problem ID.

User action
The recommended actions for the user.

 The trap severity can be determined by using the ESC=xxxx field in the problem alert trap.
The ESS also reports a problem event to S/390 host systems as a service information message (SIM),
which does contain a severity field. The SIM reporting process uses the following rule
to determine a Severity field value:

Severity = Serious if ESC=38xx, 4xxx, 5xxx or Exxx (where x = 0-F)
 	Data access performance is degraded, or in the most serious case, write data
                access is temporarily inhibited.
Severity = Moderate if ESC=2xxx, 33xxx or 8xxx
  	Problem can impact data access performance.
Severity = Service if ESC is any other value
	Problem has negligible or no impact to ESS data access performance.

 The trap contains the identifier assigned by the ESS for the particular
problem that caused the trap. The character string Problemid=n (where n is the
problem identifier) is in the description field of the trap. The time and date of the most recent
problem presented is in  day of week month day hour:minute:second year format.

2) For machine model 8xx, when an error is encountered, the ESS generates the generic trap 6
product specific trap 1 or 2. The functionality for generic trap 6 product specific trap 1 and trap 2
on ESS are the same. There is a problem trap configuration option on SNMP SMIT panel on ESS
for user to select. Also user can  specify which problem trap (1 or 2) by CLI. The ESS Specialist
panel does not allow user to do the generic trap 6 product specific trap 2 configuration. Default
configuration on ESS is  generic trap 6 product specific trap 1.  The ESS Service Guide provides
 information of the problem detected. Each trap provides the following information:

The time and date of the most recent problem occurred
data
partnumber
description


where the time and date is in yyyy/mm/dd hh:mm:ss zzz format.
yyyy is year, mm is month, dd is day, hh is hour, mm is minute, ss is second, zzz is a
time zone indication, data provides the ESS machine type, model, serial number, problem id,
and severity, partnumber is FRU (failure resource unit) and FRU part number, description contains
the Exception symptom code (ESC) and ESC description of the trap.


3) When a service personal logins or logoffs the ESS as service, the ESS generates the generic
trap 6 product specific trap 13. Each trap provides the following information:
yyyy/mm/dd hh:mm:ss zzz
description
data

where yyyy is year, mm is month, dd is day, hh is hour, mm is minute, ss is second, zzz is a
time zone indication, description is short text description of the trap, data provides the
ESS machine type, model, serial number, and state of service availability.


4) When a Copy Service error/event is encountered, the ESS generates the generic trap 6
product specific trap 100, 101, 102, 200, 202, 210, 211, 212, 213, 214, 215, or 216. The Red
book of IBM System Storage Enterprise Storage Server Implementing Copy Services in an
Open Environment provides information of the Copy Service error/event.
Each trap provides the following information:
yyyy/mm/dd hh:mm:ss zzz
description
data

where yyyy is year, mm is month, dd is day, hh is hour, mm is minute, ss is second, zzz is a
time zone indication, description is a short textual description of the trap, data provides
detailed information about the trap.

Generic alert traps

The ESS generates the following generic alert traps:

1) coldStart (Generic 0)
This trap is issued whenever the SNMP agent is reinitializing. Configuration data may have
changed.

2) warmStart  (Generic 1)
This trap is issued whenever the SNMP agent is reinitializing. Configuration data have not
changed.

3) authenticationFailure (Generic 4)
This trap is issued whenever an SNMP message was received that could not be authenticated.

Ibm2100 MIB

   The ibm2100.mib and README files are available in the SNMP directory on the IBM System Storage
Enterprise Storage Server CD, which is shipped with each ESS.  Use the following information
within the ibm2100.mib for additional details or latest product specific trap information.

1. System objects

ssSystemAccess
A count of the number of times this private MIB variable is accessed.

ssSystemElapsed
The time (in hundredths of a second) since the ESS  agent  was restarted.

ssSystemObjectId
The object identifier of this MIB variable.

ssSystemNumTraps
A count of the number of ESS traps encountered.

ssSystemSendTrap
Specific trap 1 format:
'day of week month day hour:minute:second year problem id dd, ESC eeee, description descr'
where descr is problem description.
Specific trap 2 format:
'yyyy/m/dd hh:mm:ss zzz\ndata\npartnumber\ndescription\n'
where \n is a return, zzz is a time zone indication, data is more information about the trap,
partnumber is FRU part number, and description is ESC description.
Check the problem id of this trap on both clusters. Truncated if greater than 1024 bytes.
Specific trap 3 format:
'yyyy/MM/dd hh:mm:ss tzn\nManufacturer=IBM\nReportingMTMS=tttt-mmm*ppzzzzz\n
ProbNm=nnnnn\nLparName=SFaESSbc\nFailingEnclosureMTMS=tttt-mmm*ppzzzzz\n
SRC=ssssssssss\nEventText=79 char string\n
Fru1Loc=71 char string\nFru2Loc=71 char string\nFru3Loc=71 char string\n'
Where: \n = RETURN, yyyy = year, MM = month, dd = day, hh = hour(24) ,
mm = minute, ss = seconds, tzn = time zone, tttt = type number (e.g. 2107),
mmm = model number (e.g. 921), pp = plant of manufacture (e.g. 75),
zzzzz = sequence number (e.g. FA123), nnnnn = problem number,
SFaESSbc = logical partition name, ssssssssss = system reference code
FruNLoc = location code of FRU N, where n is 1,2,3"

ssSystemMtMod
The Storage Server Machine Type and Model.

ssSystemSn
The Storage Server Machine Serial Number.

ssSystemDate
The date of machine manufacture ddd/yyyy.

ssSystemClID
Storage server local cluster ID 0/1.

ssSystemLIC
Storage server local cluster LIC.

2. Problem objects

Each ESS problem has the following fields:

ssProblemIndex
A unique value for each problem record listed in the table.

ssProblemId
The problem record identifier in the cluster problem log.  Cluster 0 problem records have
even number ID values.  Cluster 1 problem records have odd number ID values.

ssProblemStatus
The problem record state in the Storage server problem log.

ssProblemDate
The time and date the first error occurred.

ssProblemCount
The number of error events logged.

ssProblemLast
The time and date the most recent error occurred.

ssProblemPres
The time and date of the most recent problem report.

ssProblemEsc
The Exception Symptom Code (ESC) value for the problem ID.

ssProblemSrn
The System Reference Number (SRN) for the problem ID.

ssProblemDescr
Error condition description.

ssProblemMessage
An optional message that contains additional information.

ssProblemUAction
Recommended actions for user or customer.

3. Event objects

ssEventLast
Contents of latest event trap presented including:generic trap and specific trap
and ssEventDescr. Truncated if greater than 1032 bytes

ssEventDescr
Contents of latest event trap presented. Truncated if greater than 1024 bytes.

4. Traps

ssPbmTrap
 The ESS sends the ssPbmTrap when a  failure resource is detected. The ssPbmTrap
is  a generic trap 6 product specific alert trap 1 for machine  model Fxx and 8xx.
For the most current trap information, see ssSystemSendTrap object.
Example of ssPbm Trap:
 52
 Fri Oct 10 05:14:40 2003
 1204
 FRU FAILURE
 NONE

ssProblemTrap
 If  the problem trap configuration on ESS is this trap, the ESS sends it when a  failure
resource is detected. The ssProblemTrap is  a generic trap 6 product specific alert trap
2 for machine model 8xx only. For the most current trap information, see
ssSystemSendTrap object.
Example of ssProblem Trap:
2003/10/07 14:27:23 PDT
Mnf=IBM
Type-Mod=2105-800
SerialNm=13-FCA13
ID=72
Severity=Serious
DESC=# ESC 3840: Cluster 1 failover/failback failure

ssSystemNotifyTrap
 If  the problem trap configuration on ESS is this trap, the ESS sends it when a  failure
is detected. The ssSystemNotifyTrap is  a generic trap 6 product specific alert trap
3 for machine model 2170 and 1750. For the most current trap information, see
ssSystemSendTrap object (specific type 3 format).
Example of ssSystemNotifyTrap Trap:
2005/06/04 00:01:57
Manufacturer=IBM
ReportingMTMS=1750-511*13AACMA
ProbNm=2005-06-17-11.51.04.025056
LparName=
FailingEnclosureMTMS=1750-511*13AACMA
SRC=0xBEB30010
EventText=


ssEventTrap13
 The ESS sends the ssEventTrap13 for Specialist Availability Change event. The
ssEventTrap13 is a generic trap 6 product specific alert trap 13. For the most current
 trap information, see ssEventLast or ssEventDescr object.
Example of  ssEventTrap 13:
2003/10/07 14:27:23 PDT
Specialist Availability Change
Mnf Type-Mod SerialNm
IBM 2105-800 13-FCA13
State: Available

ssEventTrap100
 The ESS sends the ssEventTrap100 for a PPRC Links Degraded event.
The ssEventTrap100 is a generic trap 6 product specific alert trap 100 for machine
model 8xx only. For the most current trap information, see ssEventLast or
ssEventDescr object.
Example of ssEventTrap 100:
2003/11/07 17:05:39 PDT
PPRC Links Degraded
UNIT: Mnf Type-Mod SerialNm LS
PRI:    IBM 2105-800 75-FA123 01
SEC:   IBM 2105-800 13-FA246 01
Path: Type      PP   PLink  SP    SLink  RC
1:      ESCON 0000 00       0080 01       OK
2:      FIBRE   0001 00       0081 01       08
3:      FIBRE   0001 00       0081 01       08

ssEventTrap101
 The ESS sends the ssEventTrap101 for a PPRC Links Down event. The
ssEventTrap101 is  a generic trap 6 product specific alert trap 101 for machine
model 8xx only.  For the most current trap information, see ssEventLast or
ssEventDescr object.
Example of ssEventTrap 101:
2003/11/07 17:05:39 PDT
PPRC Links Down
UNIT: Mnf Type-Mod SerialNm LS
PRI:    IBM 2105-800 75-FA123 01
SEC:   IBM 2105-800 13-FA246 01
Path: Type      PP   PLink  SP   SLink  RC
1:      ESCON 0000 00       0080 01      08
2:      ESCON 0000 00       0080 01      08

ssEventTrap102
 The ESS sends the ssEventTrap102 for a PPRC Links Up event.
The ssEventTrap102 is a generic trap 6 product specific alert trap 102 for machine
model 8xx only.  For the most current trap information, see ssEventLast or
ssEventDescr object.
Example of ssEventTrap 102:
2003/11/07 17:05:39 PDT
PPRC Links Up
UNIT: Mnf Type-Mod SerialNm LS
PRI:    IBM 2105-800 75-FA123 01
SEC:   IBM 2105-800 13-FA246 01
Path: Type    PP   PLink  SP   SLink  RC
1:      FIBRE 0001 00       0081 01     OK
2:      FIBRE 0001 00       0081 01     OK
3:      FIBRE 0001 00       0081 01     OK
4:      FIBRE 0001 00       0081 01     OK
5:      FIBRE 0001 00       0081 01     OK
6:      FIBRE 0001 00       0081 01     OK
7:      FIBRE 0001 00       0081 01     OK

ssEventTrap200
The ESS sends the ssEventTrap200  for a LSS-Pair Consistency Group PPRC-Pair error event.
The ssEventTrap200 is a generic trap 6 product specific alert trap 200 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap 200:
2003/11/07 17:05:29 PDT
LSS-Pair Consistency Group PPRC-Pair Error
UNIT: Mnf Type-Mod SerialNm LS LD SR
PRI:    IBM 2105-800 75-FA123 01 2B 21
SEC:   IBM 2105-800 13-FB456 4E 38

ssEventTrap202
The ESS sends the ssEventTrap202  for Primary PPRC Devices on LSS Suspended Due
to Error.The ssEventTrap202 is a generic trap 6 product specific alert trap 202 for machine
model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap 202:
2003/11/07 17:05:29 PDT
Primary PPRC Devices on LSS Suspended Due to Error
UNIT: Mnf Type-Mod SerialNm LS LD SR
PRI:    IBM 2105-800 75-FA123 01 12 13
SEC:   IBM 2105-800 13-FA246 01 12
Start: 2003/11/07 17:05:30 PDT
PRI Dev Flags (1 bit/Dev, 1=Suspended):
00003E0000000000000000000000000000000000000000000000000000000000

ssEventTrap210
The ESS sends the ssEventTrap210 for Asynchronous PPRC Initial Consistency Group Successfully
Formed. The ssEventTrap210 is a generic trap 6 product specific alert trap 210 for machine
 model 8xx only. For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap 210:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Initial Consistency Group Successfully
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap211
The ESS sends the ssEventTrap211 for Asynchronous PPRC Session is in a Fatal State.
The ssEventTrap211 is a generic trap 6 product specific alert trap 211 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap211:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Session is in a Fatal State
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap212
The ESS sends the ssEventTrap212 for Asynchronous PPRC Consistency Group
Failure - Retry will be attempted.The ssEventTrap212 is a generic trap 6 product
specific alert trap 212 for machine model 8xx only.  For the most current trap
information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap 212:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Consistency Group Failure - Retry will be attempted
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap213
The ESS sends the ssEventTrap213 for Asynchronous PPRC Consistency Group Successful Recovery.
The ssEventTrap213 is a generic trap 6 product specific alert trap 213 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap 213:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Consistency Group Successful Recovery
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap214
The ESS sends the ssEventTrap214 for Asynchronous PPRC Master Terminated.
The ssEventTrap214 is a generic trap 6 product specific alert trap 214 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap214:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Master Terminated
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap215
  The ESS sends the ssEventTrap215 for Asynchronous PPRC FlashCopy Operation at Remote Site
Unsuccessful.The ssEventTrap215 is a generic trap 6 product specific alert trap 215 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example:
2003/11/07 17:05:29 PDT
Asynchronous PPRC FlashCopy at Remote Site Unsuccessful
UNIT:   Mnf Type-Mod SerialNm
Master:  IBM 2105-800 75-FA123
Slave:    IBM 2105-800 13-FB456
Session ID: 1234

ssEventTrap216
The ESS sends the ssEventTrap216 for Asynchronous PPRC Slave Termination Unsuccessful.
The ssEventTrap216 is a generic trap 6 product specific alert trap 216  for machine
 model 8xx only. For the most current trap information, see ssEventLast or ssEventDescr object.
Example:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Slave Termination Unsuccessful
UNIT:   Mnf Type-Mod SerialNm
Master:  IBM 2105-F20 75-FA123
Slave:     IBM 2105-F21 72-FB456
Session ID: 1234

ssEventTrap217
The ESS sends the ssEventTrap217 for Asynchronous PPRC Paused.
The ssEventTrap217 is a generic trap 6 product specific alert trap 217 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap217:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Paused
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap218
The ESS sends the ssEventTrap218 for Asynchronous PPRC Number of Consistency Group failures exceed threshold.
The ssEventTrap218 is a generic trap 6 product specific alert trap 218 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap218:
2003/11/07 17:05:29 PDT
Asynchronous PPRC Number of Consistency Group failures exceed threshold
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

ssEventTrap219
The ESS sends the ssEventTrap219 for Asynchronous PPRC First successful Consistency Group after prior failures.
The ssEventTrap219 is a generic trap 6 product specific alert trap 219 for machine
 model 8xx only.  For the most current trap information, see ssEventLast or ssEventDescr object.
Example of ssEventTrap219:
2003/11/07 17:05:29 PDT
Asynchronous PPRC First successful Consistency Group after prior failures
UNIT: Mnf Type-Mod SerialNm
          IBM 2105-800 75-FA123
Session ID: 1234

Test Trap 1
 For  verification of reception of an alert trap in  the workstation, use the "send test trap"
option in the ESS Specialist, in CLI  or on SMIT . The test trap is the generic trap 6
 product specific alert trap 1.This test trap information will not be in  the
ssSystemSendTrap object and the ssProblem object.
Example of the test trap is sent out and has the following information:
  ssProblemId: 9999
  ssProblemPres: Sun Jul  6 00:10:22 2003
  ssProblemEsc:  9999.
  ssProblemDescr: THIS IS A TEST
  ssProblemUAction: None.

Test Trap 2
  For  verification of reception of an alert trap in  the workstation, use the "send test trap"
command in CLI or on SMIT . The test trap is the generic trap 6 product specific alert trap 2.
This test trap information will not be in  the ssSystemSendTrap object and the ssProblem
object.
 Example of the test trap is sent out and has the following information:
  2004/03/20 10:07:27 PST
  Mnf=IBM
  Type-Mod=2105-800
  SerialNm=13-FCA13
  ID=9999
  Severity=Service
  FRU:PN=rsDDM0101:17P6637 ssa002:27H0722
  Desc=# ESC 9999: This is a test trap.

SNMP Configuration
 For displaying the ibm2100 MIB objects and/or receiving the ESS alert traps,  the system
to be receiving the alert traps must have network management software and SNMP
configuration enable. The SNMP configuration on the ESS requires the MIB access
(readonly) and product specific traps enable. During installation the TCP/IP network
address of the systems management console, along with the community to which the
ESS alerts will be posted will need to be configured.

SNMP Configuration Using ESS Specialist
 There is SNMP Configuration information in the Web Interface User 's guide
 Chapter 2, Using ESS Specialist.

Configuring ESS SNMP Notification on Tivoli Netview
 The ESS only supports Tivoli Netview. Depends on which Netview version and operating
 system, the Netview application menus are different.

MIB Installation
1. Install the ibm2100.mib file from the IBM System Storage Enterprise Storage Server CD to
 /usr/OV/snmp_mibs/ directory.
2. From "Tivoli NetView" main menu, select "Tools", then select " MIB",  then select "Load",
 and the "MIB Loader" panel will appear.
3. From the "MIB Loader" panel, select "Load", and the "Load" panel will appear.
4. From the "Load" panel, select "ibm2100.mib", then select "Open" to load the MIB.

MIB Browser
1. From Tivoli NetView main menu, select "Tools", then select "MIB",  then select "Browser",
 and the "MIB Browser" panel will appear.
2. From the "MIB Browser" panel,  type the IP address of the ESS in the "Node Name or Address"
 box.
3. From the "MIB Browser" panel,  type the community name in the "Community Name" box.  This
 name value should match the community name value configured in the ESS.
4. From the  "MIB Browser" panel, use the "Down Tree" or "Up Tree" button in the "MIB object
 ID" box to follow the MIB object tree   "Iso.org.dod.internet.private.ibm.ibmProd.ibm2100".
 Then click  "Get  values" button to see the object information within the MIB objects.
Or click  the "Properties" button to see the description of a particular MIB object.

The ESS Alert Trap Configuration
1. From the Tivoli NetView main menu, select "Options", then select "Trap settings",  and the
"Trap settings" panel will appear.
2. From the "Trap setting" panel,  select "New" in the "Select an Enterprise" box, and the
"Add New Enterprise"  panel will appear.
3. From the "Add New Enterprise" panel,  enter the following values:
          Enterprise Name: ibm2100
          Enterprise ID:   1.3.6.1.4.1.2.6.130
4. Then select "OK" to update the values.
5. Back to the "Trap settings" panel, select "ibm2100" in the "Select an Enterprise" box in
 the top.
6. Select "New" in the "Select a trap" box,  and the "Add trap" panel will appear.
7. From the "Add trap" panel, do the following:
           -Enter "ssPbmTrap" in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "1"  for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
8. From the "Add trap" panel, do the following:
           -Enter "ssProblemTrap" in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "2"  for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
9. From the "Add trap" panel, do the following:
           -Enter "ssSystemNotifyTrap" in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "3"  for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
10. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap13 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "13"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
11. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap100 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "100"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
12. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap101 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "101"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
13. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap102 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "102"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
14. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap200 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "200"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
15. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap202 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "202"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
16. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap210 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "210"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
17. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap211 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "211"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
18. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap212 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "212"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
19. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap213 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "213"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
20. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap214 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "214"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
21. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap215 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "215"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
22. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap216 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "216"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
23. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap217 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "217"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
24. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap218 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "218"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.
25. From the "Add trap" panel, do the following:
           -Enter "ssEventTrap219 " in the "Trap Name" box.
           -Select "specific" in the "Trap type" box.
           -Type "219"   for the "Specific trap number".
           -Select "Error Event" in the "Trap category" box.
           -Select "OK" to update the values.

Event Browser
  From the Tivoli NetView main menu, select "Monitor", then select "Events",  then select "All"
, and the "Event Browser" panel will appear.  The current trap information will display in the
 "Event Browser" panel.
