System information

Figure 124. Alert Flow in a Corporate Environment
•
From each local network the workstations and servers report all their alerts
to the Alert Manager of the local TME 10 NetFinity Manager.
•
The local Alert Manager forwards the alerts to the focal point Alert Manager.
•
The focal point Alert Manager writes the alerts to its log file and resends the
alerts according to the alert type and severity to the alert manager on the
workstation of the responsible person.
This alert forwarding can involve different operating systems for clients and
managers and also use multiple network protocols. For example, a Novell Server
reports a RAID error to the local manager running on Windows NT over IPX.
This forwards the error alert over the WAN through TCP/IP to the focal point
manager running on OS/2. From here the alert goes on an SNA link to the host
system and to the hardware administrator′s terminal.
This is only one of the ways of how an alert flow can be defined. It is also
possible to involve more hierarchy stages or route alerts to multiple systems.
Alert forwarding is defined from the action button in the Alert Manager. It can be
defined in two ways:
•
By alert conditions
•
By profiles
3.2.1.1 Defining Alert Forwarding by Alert Conditions
To define alerts that can be forwarded by other systems do the following:
1. Open the Alert Manager.
2. Click on Action.
3. Click on New to add a new forwarding action.
4. Choose Bind to... from the top menu and select Alert Conditions.
Chapter 3. Alert Flows 97