Metasys N2, Technical Manual

Page: 42 / 67

42 N2 Dialer Module—N2 Dialer Module (NDM)
Table 9: Metasys Network-Specific Troubleshooting Chart
Symptom Possible Cause Corrective Action
Local N2 device becomes
disconnected every time
remote NDM becomes
disconnected - The local N2 address
was incorrectly added to
the remote NDM
configuration (in the
Remote N2 addresses
field in the remote NDM
Phone Number
Configuration dialog box). - Remove address from
remote NDM
configuration
A remote device goes
offline (instead of
disconnected) when the
remote NDM becomes
disconnected - The remote N2 address
was not added to the
remote NDM
configuration (in the
Remote N2 Addresses
field in the remote NDM
Phone Number
Configuration dialog box). - Add address to remote
NDM configuration
Remote NDM continuously
dials in - A remote N2 device was
not defined as an object
in Metasys, but its
address was configured
in the remote NDM, and
this NDM is configured to
dial in on alarm. Since
the device was not added
to Metasys, the alarm
cannot be acknowledged,
so the remote NDM
continuously dials in. - Define remote device on
Metasys
Devices randomly going
offline/online - Local NDM is mistakenly
configured to call a
remote NDM on another
N2 trunk, or, a second N2
trunk is connected to the
port defined for the first
N2 trunk. This can result
in overlapping N2
addresses, which cause
serious communication
errors. - Do not have a local
NDM call a remote NDM
on another trunk. Make
sure N2 trunks are
connected to the correct
port.