Data Mismatch - Nortel DMS-100 Series Maintenance Manual

An enhancement to exception recovery deals with the Direct Memory
Access Memory Management Unit (MX77 DMA MMU). You must take
special action when you attempt to recover from an MX77 DMA MMU
error. In the past, when a DMA MMU error occurred, the exception
processing system selected the interrupted task. This action also occurred if
the software on the MX77 did not involve the error. The task selected
determines if the error was fatal because an MMU error is not fatal. The
results of the fatal evaluation depend on the trapped task.
The failed processor is the processor that caused the fault. The failed
processor can not process that a problem occurred. If the access is for a read
from MX77 memory, the external processor will receive invalid data. If the
access is to write to MX77 memory, data will not be written. The trap is
considered fatal. The trap causes maintenance action to initiate to restart or
you reset the unit.

Data mismatch

Three types of updates keep the inactive unit of the SMS provided with the
data needed to control maintenance and call processing:
static data
bulk
dynamic
Static data
Static data holds SMS-RCS configuration information, like the association
between SMS P-side ports and RCS link numbers. The CM sends the
SMS-RCS configuration information to both units of the SMS when the
SMS returns to service. The CM also sends this information to an in-service
SMS when Table RCSINV or Table LNINV is modified.
When operating company personnel alter configuration information, the
system sets the SMS to in-service trouble (ISTb). The system provides
information that a static data mismatch is present. The system also provides
information for the correct action to take.
Static data defines the RSC-S configuration. Static data does not change as
calls connect and disconnect. When static data in the host computer and
static data in the SMS do not match, data damage can result. A mismatch of
static data can cause the host computer to act like a line is present. The SMS
does not act like a line is present. and this mismatch of data can result in lost
calls.
Feature AF5678, Node Table Sync Redesign, alters the method of clearing
the ISTb condition for XPMs with software loads. The software loads
support configuration data table (CDT) management.
DMS-100 Family SMS Maintenance Manual XPM10 and up
Maintenance overview 1-63