User's Manual

Uniwave Understanding Alarms & Reporting

User Manual

13.4.4 3000 SNMP Traps

The following SNMP traps are supported:

• Hub3000Notify.Hub3000Heartbeat – This is a heartbeat trap which is sent every 20 minutes

to the listening SNMP manager. It contains the following objects: Hub3000String,

Hub3000DeviceType, Hub3000ModelName, Hub3000FaultRelayState

• Hub3000Notify.Hub3000FaultRelayStatus – This trap is sent each time a new alarm is raised

in the system, and when the fault relay is manually cleared from the PH GUI. It contains the

following objects: Hub3000String, Hub3000DeviceType, Hub3000ModelName,

Hub3000FaultDescription, Hub3000FaultRelayState

The IP address and port of the SNMP trap receiver (SNMP Manager), is set via the LAN Setup page

of the Hub graphical user interface.

Some notes on the SNMP interface and alarms:

• During start-up alarms will be written to the event log, but the fault relay will not set, and no

trap will be sent. This start-up period lasts 5 minutes.

• If any alarms remain or any units are still missing once start-up has completed, the Hub will

loop through the alarm conditions and send out traps.

13.4.5 Additional 5000 SNMP Objects

The unitivity5000Module group contains notifications which augment the ext3000UnitConfigTable from

ZINWAVE-MIB.

13.4.5.1 unitivity5000Notifications

This group supersedes both the Hub3000Events and the ext3000NotificationsGroup.

The unitivity5000Notifications group contains these notifications :

• unitivity5000Heartbeat

• unitivity5000FaultRelayStatus

• unitivity5000DASoperationalStatusChange

• unitivity5000ServiceLossOfServiceChange

• unitivity5000RUconfigLossOfServiceChange

• unitivity5000ModuleLossOfServiceChange

• unitivity5000ModuleServiceWarningChange

• unitivity5000ModuleHardwareWarningChange

• unitivity5000NotificationsLost

• unitivity5000RMPSUAlarmsChange

Which replace similar notifications in ZINWAVE-MIB and should be used in the same manner