DPS Telecom NetGuardian 420 DNP3 Hardware User Manual page 101

Display Points Alarm Point
DCP Poller
37
Inactive
38 NET1 not active The Net1 LAN port is down.
39 NET2 not active The Net2 LAN port is down.
40 LNK Alarm
Modem not
41
responding
42 No Dial Tone
SNMP Trap not
43
Sent
Pager Queue
44
Overflow
11
Notification
45
failed
46 Craft RcvQ full
Modem RcvQ
47
full
Serial 1 RcvQ
48
full
Serial 2 RcvQ
49
full
Serial 3 RcvQ
50
full
Serial 4 RcvQ
51
full
Serial 5 RcvQ
52
full
Serial 6 RcvQ
53
full
Serial 7 RcvQ
54
full
Serial 8 RcvQ
55
full
Description
The unit has not seen a poll from the
Master for the time specified by the
DCP Timer setting.
No network connection detected
An error has been detected during
modem initialization. The modem did
not respond to the initialization string.
During dial-out attempt, the unit did not
detect a dial tone.
SNMP trap address is not defined and
an SNMP trap event occurred.
Over 250 events are currently queued in
the pager queued and are still trying to
report.
A notification event, like a page or
email, was unsuccessful.
The Craft port received more data than
it was able to process.
The modem port received more data
than it was able to process.
Serial port 1 (or appropriate serial port
number) receiver filled with 8 K of data
(4 K if BAC active).
Solution
If DCP responder is not being used,
then set the DCP Unit ID to 0.
Otherwise, try increasing the DCP
timer setting under timers, or check
how long it takes to cycle through the
current polling chain on the Master
system.
Check LAN cable. Ping to and from
the unit. (If not using Net1 or Net2, set
IP, Subnet and Gateway to 255's)
Remove configured modem initialization
string, then power cycle the unit. If
alarm persists, try resetting the Modem
port from the TTY interface, or contact
DPS for possible RMA.
Check the integrity of the phone line
and cable.
Define the IP Address where you would
like to send SNMP trap events, or
configure the event not to trap.
Check for failed notification events that
may be filling up the pager queue.
There may be a configuration or
communication problem with the
notification events.
Use RPT filter debug to help diagnose
notification problems.
Disconnect whatever device is
connected to the craft serial port. This
alarm should not occur.
Check what is connecting to the
NetGuardian. This alarm should not
occur.
Check proxy connection. The serial
port data may not be getting collected
as expected.
95