
Troubleshooting operational problems 17-9
AML problems
Standard 1.0 Modular Option EC Installation and Maintenance Guide November 1999
• Meridian 1 hardware input/output address conflicts (for
example, two SDI, ESDI/MSDL, or D-channel cards
with the same addresses)
• Meridian 1 or Meridian Mail software upgrades or
conversions
• ESDI/MSDL, cable, or Local Data Set failures
• Loose cable connections
• Manual or overlay-controlled disabling of the link
• External equipment as a source of electromagnetic
interference (EMI)
• Loss of commercial power
• Other critical failures
When any of these events occur, AML messages indicating a
change of call status may be lost. This may result in a conflict
between the Meridian 1 and Meridian Mail regarding the
status of a terminal or an established call. Once the failure has
been recovered, a series of AML messages are used to resolve
these conflicts. This activity is controlled by Meridian Mail.
When a system reload occurs, a database discrepancy
between Meridian Mail and the Meridian 1 may result in the
message waiting indicator not reflecting the actual message
waiting status.
AML status
The AML commands used to determine the link status or to
place the link in a state will vary according to the software
release of X11 and I/O card type used.
X11 Release 17 or earlier X11 Release 18 or later
ENL ESDI n use: ENL AML n LYR2
DIS ESDI n use: DIS AML n LYR2
ENL CMS n use: ENL AML n LYR7
DIS CMS n use: DIS AML n LYR7
CON ESDI n use: EST AML n LYR2
DSC ESDI n use: RLS AML n LYR2
ACMS n use: ENL AML n ACMS
use: ENL AML n AUTO (MSDL)
Comentarios a estos manuales