Cabletron Systems CBU-NM User Manual page 24

First, PCNC must decide whether or not the incoming message is both
In a valid ALERT format (See Chapter 13)
A legal ALERT string
If not, PCNC can make no sense of it and will discard it as unreadable.
If the message is valid, PCNC will extract the Poll number and look it up
in the Network Database to find out which device sent the message.
Once it knows the Device's name and product type, PCNC decodes the
message as an alarm.
If the device type specified is not supposed to produce the ALERT that
PCNC has received, it means that the Database is not configured
correctly. PCNC then creates its own alarm to indicate the problem (see
Section 3.3.3).
At this stage, if required, the alarm is converted into an SNMP trap and
forwarded to an NMS (see Chapter 5).
Alert messages often indicate a change in device status, eg that a
device has gone offline. PCNC stores the current status of each device
in the Network Database and updates the relevant one whenever an alert
comes in. Thus the latest information is always displayed in Network
Inspector window.
Finally, the alarm is stored in the Alarm Database.
The logging of PCNC alarms and the creation of SNMP traps can be
enabled or disabled in PCNC.INI (see Chapter 7).
3.3.2 Alarms
When an alarm has been processed, PCNC stores it in the Alarm
Database and notifies you of its arrival - with the Audible warning (if
enabled) and a flashing panel in the toolbar. The status of the device is
decoded from the message and shown in the Network Inspector window.
80-60100000-02
Alarms and Filters
3–3