Alarm and Event Handling (2024)

Table of Contents
CORBA SNMP

Product Description

Alarm and Event Handling (1)Alarm and Event Handling (2)Alarm and Event Handling (3)Alarm and Event Handling (4)
Get
Adobe Reader

The following sections describe WebLogic Network Gatekeeper alarm and event handling:

All the WebLogic Network Gatekeeper software modules can raise alarms and events. The difference between alarms and events is that alarms are unexpected and might need corrective action, while events are expected and of importance to the operator.

All alarms are stored in the alarm list in the WebLogic Network Gatekeeper database. The type of information stored for each alarm is presented in Table10-1 on page2.

Table 10-1 Alarm Entry Information

Information

Description

Unique ID

A sequential number to identify the alarm.

Source

Specifies the name of the SLEE service (software module) that raised the alarm and the IP address of the SLEE the service is installed in.

Severity

Specifies the alarm's severity level. One of the following:
1 - warning
2 - minor
3 - major
4 - critical

The individual alarms' severity level can be reconfigured by the operator.

Identifier

Specifies the alarm type using a number and a heading.

Info

Alarm information provided by the software module the raised the alarm.

Timestamp

Specifies the date and time the alarm was raised.

All alarms have a default severity level.

It is possible to set an alarm filter specifying an alarm severity level. Only alarms with a severity level equal to, or higher than the specified filtering level will be written to the alarm list.

Alarms are retrieved from the alarm list based on software module, severity level, and time period. The different alarm types and recommended corrective actions are presented in User's Guide - WebLogic Network Gatekeeper.

All events are logged in the event log in the WebLogic Network Gatekeeper database. The type of information stored for each event is presented in Table10-2.

Table 10-2 Event Log Entry Information

Information

Description

Unique ID

A sequential number to identify the event.

Source

Specifies the name of the SLEE service (software module) that raised the event and the IP address of the SLEE the service is installed in.

Level

Specifies the event's importance level. One of the following:
1 - low
2 - medium
3 - high

Identifier

Specifies the event type using a number and a heading.

Info

Event information provided by the software module the raised event.

Timestamp

Specifies the date and time the event was raised.

It is possible to set an event filter specifying an importance level. Only events with a importance level equal to, or higher than the specified filtering level will be written to the event log.

Events are retrieved from the event log based on software module, importance level, and time period.

CORBA

An Operation Support System (OSS) integrates with the WebLogic Network Gatekeeper alarm and event services through registration of alarm and event listeners over a CORBA/IDL interface.

SNMP

In addition, the WebLogic Network Gatekeeper supports sending of alarms as SNMP traps to SNMP managers. The alarms sent to the SNMP managers can be filtered on alarm severity.

Alarm and Event Handling (2024)
Top Articles
Latest Posts
Article information

Author: Carmelo Roob

Last Updated:

Views: 5567

Rating: 4.4 / 5 (65 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Carmelo Roob

Birthday: 1995-01-09

Address: Apt. 915 481 Sipes Cliff, New Gonzalobury, CO 80176

Phone: +6773780339780

Job: Sales Executive

Hobby: Gaming, Jogging, Rugby, Video gaming, Handball, Ice skating, Web surfing

Introduction: My name is Carmelo Roob, I am a modern, handsome, delightful, comfortable, attractive, vast, good person who loves writing and wants to share my knowledge and understanding with you.