IBM Tivoli Storage Resource Manager: A Practical Introduction

Chapter 8. Integration with Tivoli Enterprise Console 427

򐂰 Severity: severity level of the event. Possible values in order of decreasing severity are

FATAL, CRITICAL, MINOR, WARNING, HARMLESS, and UNKNOWN.

򐂰 alertName: name of the triggered alert.

򐂰 alertType: type of the triggered alert.

򐂰 resourceName: name of the alerting resource.

򐂰 resourceType: type of the alerting resource.

򐂰 threshold: The alert’s triggering threshold.

򐂰 currentValue: alerting resource’s current value.

򐂰 previousValue: alerting resource’s previous value.

򐂰 freespace: free space of the alerting resource.

򐂰 violatorName: name of the over quota user or OS/Group.

򐂰 violatorType: type of the storage consumer – user or OS/Group.

򐂰 filerName: filer triggering the alert.

򐂰 currentCapacity: current capacity of the alerting resource.

򐂰 targetCapacity: target capacity of the alerting resource.

򐂰 scheduleName: name of the failed job schedule.

򐂰 scheduleType: type of schedule that failed.

򐂰 scheduleRun: schedule run number that failed.

򐂰 rdbmsName: name of the alerting RDBMS.

򐂰 rdbmsType: type of RDBMS that triggered the alert.

򐂰 databaseName: name of the alerting database.

򐂰 segmentName: creator and name of the alerting Oracle segment.

򐂰 segmentType: type of Oracle segment that triggered the alert.

The event classes IBM Tivoli Storage Resource Manager uses are:

򐂰 Ram_Changed: the amount of RAM on an Agent has changed

򐂰 VirtualMemory_Changed: the amount of virtual memory on an Agent has changed.

򐂰 Disk_New: a new disk has been discovered on an Agent

򐂰 Disk_Missing: a disk has been removed from an Agent

򐂰 Disk_Failure: a managed disk has predicted that a disk failure is imminent.

򐂰 Disk_Defect: a new defect has been detected on a managed disk.

򐂰 Filesystem_New: a new filesystem has been discovered on a managed computer.

򐂰 Filesystem _Missing: a filesystem has been removed or unmounted from an Agent

򐂰 Filesystem_Reconfigured: the physical space definition of an Agent filesystem has been

reconfigured.

򐂰 Filesystem _FreeSpace_Low: a managed filesystem is low on free space.

򐂰 Filesystem _Inode_Low: a managed UNIX filesystem is low on free inodes.

򐂰 Filesystem_Constraint_Violated: a Constraint on a managed filesystem has been violated.

򐂰 Filesystem_Auto_Extend: a managed filesystem will be extended.

򐂰 Filesystem_Stopped_Auto_Extend: extension of a managed filesystem is prevented.

򐂰 Directory_Missing: a monitored directory has been removed from a managed computer.

򐂰 Directory_Quota_Exceeded: a user or directory storage quota has been exceeded.

򐂰 Computer_Offline: an Agent is offline.

򐂰 Computer_Discovered: a new unmanaged computer has been discovered.

򐂰 NasComputer_Discovered: a new filer has been discovered.

򐂰 Filer_Missing: a filer is no longer accessible through the specified resource.

򐂰 DiskArray_Missing: a disk array is no longer visible to a managed computer.

򐂰 DiskArray_New: a new Disk Array has been discovered.

򐂰 Job_Failure: a scheduled job has failed

8.6 Tivoli Storage Resource Manager event forwarding

After we have prepared the Tivoli Event Console Server (TEC) to receive events from IBM

Tivoli Storage Resource Manager, we must enable IBM Tivoli Storage Resource Manager

428 IBM Tivoli Storage Resource Manager: A Practical Introduction

itself to forward events to TEC. Open the IBM Tivoli Storage Resource Manager Desktop and

navigate to

Administrative Services -> Configuration -> Alert Disposition and enter the

hostname of your TEC server and the port (Windows 5529, UNIX 0) in the TEC section on the

right (Figure 8-23).

Figure 8-23 Setting the TEC server properties

Save your changes by clicking on the Save button under the top menu.

This configuration only defines where TEC events should be sent to - we have not yet actually

enabled any events. To enable events for a specific topic in IBM Tivoli Storage Resource

Manager, you have to select the TEC check box on every Alert properties tab that you want ti

activate. For example, if you want a TEC event sent when the Default Scan fails, navigate to

its properties page and enable it (Figure 8-24).

Chapter 8. Integration with Tivoli Enterprise Console 429

Figure 8-24 Enabling TEC events for the default scan

You can configure IBM Tivoli Storage Resource Manager to send a TEC event for any Alerts.

Another example is to send an event when a new computer is discovered, as shown in

Figure 8-25.

430 IBM Tivoli Storage Resource Manager: A Practical Introduction

Figure 8-25 Enable TEC events for discovery of new computers