HALCYON-PRIMEALERT-MIB

All MIBs › HALCYON-PRIMEALERT-MIB

Organization: Halcyon Monitoring Solutions Inc.

Last Updated: 2002-11-19

Category: Alarm and Event Management

Description: Provides alerting and notification objects for Halcyon PrimeAlert monitoring solutions for IT infrastructure events.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HALCYON-PRIMEALERT-MIB?

HALCYON-PRIMEALERT-MIB is the core MIB for Halcyon PrimeAlert, an IT infrastructure event-management and alerting platform, defining the SNMP trap format used to relay events collected by PrimeAlert out to external NMS/monitoring systems. Rather than modeling a specific piece of hardware, it exposes event-oriented data: the originating host, port, module, and context of an event, its severity level, message text, and open/close timestamps. Because PrimeAlert itself aggregates alerts from many underlying sources, this MIB's real monitoring value is as a normalized software-status and fault-notification channel -- it surfaces problems (which could originate from hardware faults, service failures, or job errors on monitored systems) as a consistent trap format for downstream alerting. It functions as an SNMP trap-forwarding bridge and depends on Halcyon's own agents/collectors on the monitored endpoints rather than on a specific IETF hardware MIB. It is typically deployed in enterprise environments using Halcyon PrimeAlert as a central event-consolidation layer that forwards traps to an NMS or SIEM. Engineers can download the HALCYON-PRIMEALERT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HALCYON-PRIMEALERT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Halcyon PrimeAlert event-management server (monitors Windows/Unix servers, applications, and network infrastructure)

Monitoring Examples

An NMS would receive a PrimeAlert trap and read eventHost, eventPort, and eventModule to identify which monitored system and subsystem raised the event, eventSeverity to prioritize it, and eventMessage for the human-readable description. Comparing eventOpenTime and eventCloseTime shows whether an alert is still active or has been resolved, letting an operator track open-alert duration and mean time to resolution across the monitored estate. A flood of high-severity traps from the same eventHost would indicate that a specific server or device is experiencing a significant fault.

What Can Be Monitored

source host of an event
event port/module/context
event severity level
event message text
event open/close timestamp

Imported Objects

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString
TAddress

OIDs

OID symbolic	OID numeric	Type	Access	Description
primealert	1.3.6.1.4.1.1242.1			The core Halcyon PrimeAlert v6 MIB
traps	1.3.6.1.4.1.1242.1.0
NTF eventOpenTrap	1.3.6.1.4.1.1242.1.0.9			An open event is sent whenever an alarm condition opens on an agent.
NTF eventCloseTrap	1.3.6.1.4.1.1242.1.0.10			A close event is sent whenever an alarm condition closes on an agent.
NTF eventLogTrap	1.3.6.1.4.1.1242.1.0.11			A log event is sent whenever an alarm condition is detected on an agent and it is considered closed instantaneously (e.g. when fault conditions are reported through logging of a message, but the application logs no corresponding return-to-normal message, such faults are flagged by a log event)
NTF eventColdstartTrap	1.3.6.1.4.1.1242.1.0.12			A coldstart trap is sent whenever an agent starts up.
NTF eventAcknowledgeTrap	1.3.6.1.4.1.1242.1.0.13			An acknowledge trap is sent whenever an event is acknowledged at the agent.
NTF eventUnAcknowledgeTrap	1.3.6.1.4.1.1242.1.0.14			An unacknowledge trap is sent whenever an event is unacknowledged at the agent.
NTF eventModuleUnavailableTrap	1.3.6.1.4.1.1242.1.0.15			A module unavailable trap is sent whenever a module becomes unavailable (for example, if it is unloaded) and all open events for that module should be considered closed.
base	1.3.6.1.4.1.1242.1.1
trapInfo	1.3.6.1.4.1.1242.1.1.3
STR eventHost	1.3.6.1.4.1.1242.1.1.3.6	DisplayString	accessible-for-notify	The hostname of the agent on which the event occurred. This occurs as the first trap-specific varbind of an event trap.
I32 eventPort	1.3.6.1.4.1.1242.1.1.3.7	Integer32	accessible-for-notify	The SNMP port of the agent on which the event occurred. This occurs as the second trap-specific varbind of an event trap.
STR eventModule	1.3.6.1.4.1.1242.1.1.3.8	DisplayString	accessible-for-notify	The identifier of the Primealert module in which the event occurred. This occurs as the third trap-specific varbind of an event trap.
STR eventContext	1.3.6.1.4.1.1242.1.1.3.9	DisplayString	accessible-for-notify	The SNMP context of the Primealert module in which the event occurred, for modules which can be loaded multiple times in one agent. For modules which can only be loaded once, this is empty. This occurs as the fourth trap-specific varbind of an event trap.
STR eventSeverity	1.3.6.1.4.1.1242.1.1.3.10	DisplayString	accessible-for-notify	A human-readable string representing the severity of the event in question, such as 'Critical'. This occurs as the fifth trap-specific varbind of an event trap.
STR eventMessage	1.3.6.1.4.1.1242.1.1.3.11	DisplayString	accessible-for-notify	A human-readable string describing the event. This occurs as the sixth trap-specific varbind of an event trap.
STR eventUrl	1.3.6.1.4.1.1242.1.1.3.12	DisplayString	accessible-for-notify	A url-formatted string representing the MIB location at which the event occurred. It can be used to associate a close event with its corresponding open event. This occurs as the seventh trap-specific varbind of an event trap.
STR eventOpenTime	1.3.6.1.4.1.1242.1.1.3.13	DisplayString	accessible-for-notify	A human-readable string containing the time that the event was opened. Example: Aug 08, 2002 15:34:27.000 GMT. This occurs as the eighth trap-specific varbind of an event trap
STR eventCloseTime	1.3.6.1.4.1.1242.1.1.3.14	DisplayString	accessible-for-notify	A human-readable string containing the time that the event was closed (if applicable). Example: Aug 08, 2002 15:34:27 .000 GMT. This occurs as the ninth trap-specific varbind of an event trap

RFC description

Halcyon PrimeAlert monitoring system event traps for alarm state changes and notifications.

Start monitoring Halcyon PrimeAlert event-management server with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HALCYON-PRIMEALERT-MIB

What Is HALCYON-PRIMEALERT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description