Timeswitch diagnostics with the aid of the Timeswitch device driver perform diagnostic
tests on the following components:
A 200i/200ix's or
MPB-16M's embedded Timeswitch FPGA.
The Timeswitch FPGA is responsible for routing PCM traffic. This inludes
voice, fax, tones, DTMF and all other types of telephony data. It has
the capability of routing PCM data from any DS30X, DSP, or SCBUS channel
to any other DS30X, DSP, or SCBUS channel. A typical example of the how
the Timeswitch is used is given below: An end-user makes uses a phoneset
to make a call that is detected by a PBX switch. The PBX switch routes
the call to a particular DS30X channel on a particular DS30X device on
a MPB. The Timeswitch is then used to transfer this inbound data to an
intermediary SCSA bus channel and then to a particular MPC channel for
digital signal processing. Once the data has been processed, the Timeswitch
is once again used to route PCM data (ie: a response to a user's command)
from the DSP channel, to an SCBUS channel, to a DS30X channel and thus
to switch software for processing. Switch software then routes this data
back to a destination phoneset.
A C52 MPC DSP's
DMA Engine.
Each C52 type DSPs contain a Direct Memory Access engine. The DMA engine
is responsible for transferrring PCM data between particular DSP channels
and intermediary Timeswitch memory elements.
SCBUS Logical and
Physical device.
In TRP platforms, an SCBUS ribbon cable allows communition of PCM data
between several MPB-16M’s. In TRP platforms that contain only a single
MPB-16M, the SCBUS serves as an intermediary logical bridge between DSP
and DS30X devices. As an example, inbound PCM data from a phoneset will
be forwarded to a particular MPB-16M's DS30X channel. From here, the MPB's
Timeswitch will be used to route the data to an SCBUS channel. Once the
data is "on" the SCBUS, any DSP channel on any of the installed
MPB-16M’s is capable of receiving and processing the data. The ultimate
decision of which DSP and which DSP channel will be used is controlled
by higher level software that programs the Timeswitch.
Timeswitch diagnostics include the following suite of tests:
Timeswitch Memory Diagnostic - Tests a Timeswitch's functional memory elements.
C52 DMA Memory Diagnostc - Tests a C52 DSP's DMA engine.
Timeswitch Loopback Diagnostic - Uses several C52 DSPs with functional DMA engines to test Timeswitch functionality.
SCBUS Diagnostic - Tests the ability of SCBUS to receive and transmit PCM data. This includes testing board to board communication and whether the SCBUS ribbon cable is not damaged.
Severity Minor
Description There was an unknown signal received for Signal Detector handler
Impact No impact by receiving unknown signal but this may indicate line noise
Recovery Action If proplem persists contact the design community
Technical Support Action If proplem persists contact the design community
Severity Minor
Description There was an error occured during the processing of a callback function for Signal Detector in LLS
Impact Events received by Signal dector LLS may not reach the Application
Recovery Action If proplem persists contact the design community
Technical Support Action If proplem persists contact the design community
Severity Minor
Description There was an error occured when trying tcommunicate with the DSP in the LLS layer
Impact Signal Detector may not function properly
Recovery Action If proplem persists contact the design community
Technical Support Action If proplem persists contact the design community
Severity Minor
Description There was an error occured Signal Generator handler in the LLS layer
Impact Signal Generator may not function properly
Recovery Action If proplem persists contact the design community
Technical Support Action If proplem persists contact the design community
Severity Critical
Description The Timeswitch Memory Diagnostic failed to ENABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet), the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Minor
Description The Timeswitch Memory Diagnostic was run while the Timeswitch's target MPB/200i was not in an off-duty state. A usage error most likely occurred while attempting to run diagnostics from the SERVER. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: the Timeswitch's target 200i/MPB board is in an off-duty state prior to running diagnostics. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to DISABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet), the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elelments (PCM Control Register). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elelments (Connection Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elelments (TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elelments (UNUSED TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elelments (PCM Control Register). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elelments (CONNECTION Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elelments (TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elelments (UNUSED TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (UNUSED TAP Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (CONNECTION Memory). Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Major
Description The Timeswitch Memory Diagnostic failed due to a critical internal SOFTWARE bug. Consult the Event Log for further details.
Impact The Timeswitch Memory Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and then re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Critical
Description The Timeswitch Memory Diagnostic failed due to a critical internal SOFTWARE error (System low on virtual memory). Consult the MAS server's Windows NT Event Log for further details.
Impact The Timeswitch Memory Diagnostic will not operate as expected.
Recovery Action If call processing is being affected, try shutting down and rebooting the MAS server and then re-running the Timeswitch Memory diagnostics. Contact CTS to report the bug.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (TAP Memory Bank#2). Consult the MAS server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (UNUSED TAP Memory Bank#2). Consult the MAS server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (TAP Memory Bank#2). Consult the MAS server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (UNUSED TAP Memory Bank#2). Consult the MAS server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Minor
Description The C52 DSP DMA Diagnostic was run while the MPC's parent MPB/200i was not in an off-duty state. A usage error most likely occurred while attempting to run diagnostics from the SERVER. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: the Timeswitch's target 200i/MPB is in an off-duty state prior to running diagnostics. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Critical
Description The C52 DSP DMA Diagnostic failed to ENABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The C52 DSP DMA Diagnostic failed to DISABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The C52 DSP DMA Diagnostic failed to CONNECT a link using the MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The C52 DSP DMA Diagnostic failed to DISCONNECT a link using the MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Major
Description The C52 DSP DMA Diagnostic failed to OPEN the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the MPC is properly inserted into its MPC-slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The C52 DSP DMA Diagnostic failed to CLOSE the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The C52 DSP DMA Diagnostic failed to RESET the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The C52 DSP DMA Diagnostic failed to QUERY the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Minor
Description An attempt was made to run the C52 DSP DMA Diagnostic against a non-C52 type MPC. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: the C52 DSP DMA diagnostic is only run against C52-type MPCs. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Major
Description The C52 DSP DMA Diagnostic failed to write to the MPC's memory elelments (SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to read from the MPC's memory elelments (SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to write to the MPC's memory elelments (IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to ACCESS the MPC's memory elelments (MAP SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to ACCESS the MPC's memory elelments (MAP IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to HALTACCESS to the MPC's memory elelments (UNMAP SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The C52 DSP DMA Diagnostic failed to HALTACCESS to the MPC's memory elelments (UNMAP IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The target MPC failed the C52 DSP DMA Diagnostic. Data was looped back through the Timeswitch - the received data was not equal to the transmitted data. Consult the Event Log for further details.
Impact The MPC or its parent MPB's Timeswitch may be faulty. Call processing might be greatly impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run other DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action If replacing the MPC does not solve the problem, try restarting the EMCI service. If the problem persists, replace the MPC's parent MPB/200i.
Severity Critical
Description The C52 DSP DMA Diagnostic failed due to a critical internal SOFTWARE bug. Consult the Event Log for further details.
Impact The C52 DSP DMA Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Minor
Description The Timeswitch Local Loopback Diagnostic was run against an MPB/200i that was not in an off-duty state. A usage error most likely occurred while attempting to run diagnostics from the SERVER. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: the Timeswitch's target 200i/MPB is in an off-duty state prior to running diagnostics. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to ENABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to DISABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to CONNECT a link using the MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to DISCONNECT a link using the MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to OPEN the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the MPC is properly inserted into its MPC-slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to CLOSE the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to RESET the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to QUERY the specified MPC. Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the ntbus.sys & c52.sys device drivers are running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run Timeswitch Memory Diagnostics and the DSP Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Minor
Description An attempt was made to run the Timeswitch Local Loopback Diagnostic using a non-C52 type MPC. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: the C52 DSP DMA diagnostic is only run against C52-type MPCs. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to write to the MPC's memory elelments (SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to read from the MPC's memory elelments (SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to write to the MPC's memory elelments (IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to ACCESS the MPC's memory elelments (MAP SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to ACCESS the MPC's memory elelments (MAP IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to HALTACCESS to the MPC's memory elelments (UNMAP SRAM Memory). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Major
Description The Timeswitch Local Loopback Diagnostic failed to HALTACCESS to the MPC's memory elelments (UNMAP IO REGISTERS). Consult the Event Log for further details.
Impact The MPC may be faulty and call processing might be impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run DSP Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action Not Applicable
Severity Critical
Description The specified MPC caused the Timeswitch Local Loopback Diagnostic to fail. Data was looped back through the Timeswitch - the received data was not equal to the transmitted data. Consult the Event Log for further details.
Impact The MPB's Timeswitch or one or more MPCs may be faulty. Call processing might be greatly impacted.
Recovery Action Ensure the following: All MPCs are properly inserted into their MPC-slots. Run the C52 DSP DMA Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action Not Applicable
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed due to a critical internal SOFTWARE bug. Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description The indicated Board's first DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s second DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s third DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s fourth DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s fifth DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s sixth DSP device could not be opened.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description The indicated Board’s first DSP device could not be closed.
Impact The DSP might not be present or might be defective. The DSP can not be used for call processing and must be disabled.
Recovery Action The DSP might be defective. Confirm the results of the diagnostic by running the DSP Diagnostics.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to ENABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action On TRP platforms, run the nbtswsyn.exe Server support tool and ensure that the specified MPC appears. Shutdown and restart the server and re-run all DSP diagnostics on the target MPC. If the error re-occurs, replace the MPC (or 200i/MPB if embedded).
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed to DISABLE an MPBs/200i's Timeswitch. Consult the Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the 200i/MPB is properly seated into its backplane/PCI slot. Run the Timeswitch Memory Diagnostic and the C52 DSP DMA diagnostic to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (BEGINTHREAD). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (CLOSETHREAD). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (THREADSOFTWARE). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (GETTHREADEXITCODE). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (WAITFOROBJECTS). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description A Timeswitch loopback of data using an MPC did not complete within a hardcoded time out limit. Consult the Event Log for further details.
Impact The MPB's Timeswitch or the specified MPC may be faulty. Call processing might be greatly impacted.
Recovery Action Ensure the following: the MPC is properly inserted into its MPC-slot. Run the DSP Diagnostics and the C52 DSP DMA Diagnostics to confirm,reproduce,and isolate the failure. If the error re-occurs, replace the MPC.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running all DSP and Timeswitch diagnostics.
Severity Major
Description An internal software error occurred while running the Timeswitch Local Loopback Diagnostic (WAITFORABANDONED). Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Critical
Description The specified MPC caused the Timeswitch Local Loopback Diagnostic to fail. Data was looped back through the Timeswitch - the received data was not equal to the transmitted data. Consult the Event Log for further details.
Impact The MPB's Timeswitch or one or more MPCs may be faulty. Call processing might be greatly impacted.
Recovery Action Ensure the following: All MPCs are properly inserted into their MPC-slots. Run the C52 DSP DMA Diagnostics to confirm,reproduce,and isolate the failure.
Technical Support Action Not Applicable
Severity Critical
Description The Timeswitch Local Loopback Diagnostic failed due to a critical internal SOFTWARE bug. Consult the Event Log for further details.
Impact The Timeswitch Local Loopback Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the Timeswitch Memory diagnostics. Please contact Nortel Designers to report this bug.
Severity Major
Description A call to the "c52.sys" DSP device driver that queries the type of the DSP failed when the indicated Board's first DSP was specified as an argument.
Impact The diagnostic will not be run on the indicated DSP and will fail.
Recovery Action A low-level software component or one of its interfaces failed. Please contact your Nortel Networks service personnel.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description A call to the "c52.sys" DSP device driver that queries the type of the DSP failed when the indicated Board's second DSP was specified as an argument.
Impact The diagnostic will not be run on the indicated DSP and will fail.
Recovery Action A low-level software component or one of its interfaces failed. Please contact your Nortel Networks service personnel.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description A call to the "c52.sys" DSP device driver that queries the type of the DSP failed when the indicated Board's third DSP was specified as an argument.
Impact The diagnostic will not be run on the indicated DSP and will fail.
Recovery Action A low-level software component or one of its interfaces failed. Please contact your Nortel Networks service personnel.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Major
Description A call to the "c52.sys" DSP device driver that queries the type of the DSP failed when the indicated Board's fourth DSP was specified as an argument.
Impact The diagnostic will not be run on the indicated DSP and will fail.
Recovery Action A low-level software component or one of its interfaces failed. Please contact your Nortel Networks service personnel.
Technical Support Action Ensure that the indicated DSP is properly plugged in if it is a PCMCIA DSP. Using Microsoft's "Windows NT Diagnostics" utility to ensure that the "ntbus.sys" and "c52.sys" device drivers are installed and that the indicated DSP device was created.
Severity Minor
Description The SCBUS Diagnostic was run on a non-TRP type platform (eg:200i). A usage error most likely occurred while attempting to run diagnostics from the SERVER. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Minor
Description The SCBUS Diagnostic was run while at least one MPB was not in an off-duty state. A usage error most likely occurred while attempting to run diagnostics from the SERVER. Consult the Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severly impacted. If being run from the SERVER, there will be no impact on call processing.
Recovery Action Ensure the following: all Timeswitch MPB targets are in an off-duty state prior to running the diagnostic. If the diagnostic was being run from the CLIENT GUI, contact CTS.
Technical Support Action If the diagnostic was being run from the CLIENT GUI then please report this bug to Nortel designers.
Severity Critical
Description The SCBUS Diagnostic failed to ENABLE an MPB's Timeswitch. Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description The SCBUS Diagnostic failed to DISABLE an MPB's Timeswitch. Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the ntbus.sys device driver is running (Devices Applet),the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Run the nbtswsyn.exe support tool from the Server and ensure that the specified board appears. Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description The SCBUS Diagnostic failed to read from an MPB's memory elelments (TAP Memory). Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description The SCBUS Diagnostic failed to write to an MPB's memory elelments (UNUSED TAP Memory). Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description The SCBUS Diagnostic failed to write to an MPB's memory elelments (CONNECTION Memory). Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description The SCBUS Diagnostic failed to write to an MPB's memory elelments (PCMREGISTER Memory). Consult the Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Technical Support Action Shutdown and restart the server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB.
Severity Critical
Description Data was transferred from one MPB to another or the same MPB using MPB Timeswitches - the received data was not equal to the transmitted data. Consult the Event Log for further details.
Impact The SCBUS Cable, or MPB Timeswitches may be faulty and call processing might be severly impacted.
Recovery Action Ensure the following: all MPBs are properly seated into their PCI slots,the SCBUS Cable is properly connected to all MPBs,the SCBUS Cable is not defective.Run the nbtswsyn.exe support tool from the server and ensure the synchronization scheme is valid
Technical Support Action Run the nbtswsyn.exe support tool from the server and ensure that the synchronization scheme is valid. Ensure that the SCBUS Cable is plugged in correctly. If the error persists, try replacing the SCBUS Cable or one or more MPBs.
Severity Critical
Description The SCBUS Diagnostic failed due to a critical internal SOFTWARE bug. Consult the Event Log for further details.
Impact The SCBUS Diagnostic will not operate as expected.
Recovery Action Contact CTS.
Technical Support Action If call processing is being affected, try shutting down and restarting the EMCI service and re-running the SCBUS diagnostics. Please contact Nortel Designers to report this bug.
Severity Critical
Description The SCBUS Diagnostic failed due to a critical internal SOFTWARE error (System low on virtual memory). Consult the MAS server's Windows NT Event Log for further details.
Impact The SCBUS Diagnostic will not operate as expected.
Recovery Action If call processing is being affected, try shutting down and rebooting the MAS server and then re-running the Timeswitch diagnostics. Contact CTS to report the bug.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The SCBUS Diagnostic failed remove a Timeswitch connection. Consult the MAS server's Windows NT Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the MPB is properly seated into its PCI slot. Run the Timeswitch Memory Diagnostic and to confirm, reproduce, and isolate the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB. Contact CTS to report the bug.
Technical Support Action Please contact MAS Designers to report this bug.
Severity Critical
Description The SCBUS Diagnostic failed to write to an MPB's memory elements (UNUSED TAP Memory Bank#2). Consult the MAS server's Windows NT Event Log for further details.
Impact An MPB's Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action If call processing is being affected, try shutting down and rebooting the MAS server and then re-running the Timeswitch diagnostics. Contact CTS to report the bug.
Technical Support Action Not applicable
Severity Critical
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values(TAP Memory Bank#2). Consult the server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Not applicable
Severity Critical
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (UNUSED TAP Memory Bank#2). Consult the Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the 200i/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the MAS server and re-run Timeswitch diagnostics. If the error re-occurs, replace the MPB/200i.
Technical Support Action Not applicable