Philips M3150B Installation And Service Manual page 304

Troubleshooting
Table 7-4. Troubleshooting M3151 Information Center Clients
Symptom
M3151 Client
- waveforms drop out for 15-60
seconds
- applications shut down
- PC goes to Desktop for 10-20
seconds
- reboots to local database mode
- displays patient waveforms in
sectors where patients were
assigned
- locks up
M3151 Client
- waveforms dropout for 15-120
seconds
- applications shut down
- PC goes to Desktop for 10-20
seconds
- reboots to local database mode
- displays "Monitoring lost for
this patient" in sectors where
patients were assigned
7-18
Maintenance, Troubleshooting, and Repair
Possible Cause(s)
Client has lost connection to
Server, but still has active
network connection to
Information Center sourcing
data to it.
Problem probably also affects
other devices on the network
Possible causes:
- bad connection between
Switch and Server. May
include in-wall and patch
cables
- failed component (Repeater,
or Media Translator) between
Server and Switch
- Server down
- Server in Config mode
Client has lost connection to
network due to:
- bad connection between Client
and Switch including in-wall
and patch cables
- failed component (Repeater or
Media Translator) between
Client and Switch
- network Switch down
Verification
Isolate problem by observing
functionality on rest of network.
Determine if other Information
Centers can receive data from
Server
If Server's network connection is lost,
then other devices (Information
Centers and Clients) should not be
able to retrieve stored data and
should be in local database mode.
Review Event Viewer, Application
Log. An "SDProcess" error message
is logged, either
- Warning 3257 "System restarted
using the local database mode
because the server is not available"
or
- Warning 4208 "Restarting
applications because the database
server connection is unavailable.
System will come up in Local DB."
Look at Link LEDs on device ports of
LAN interfaces to identify the failed
connection
Test UTP and fiber optic cable
connections
Isolate problem by observing
functionality present on rest of
network.
Determine if Information Centers are
operational and can receive data
from Server
Review Event Log, Application Log.
An "SDProcess" error message is
logged, either
- Warning 3257 "System restarted
using the local database mode
because the server is not available"
or
- Warning 4208 "Restarting
applications because the database
server connection is unavailable.
System will come up in Local DB."
If problem is isolated to Client
connection, then other devices (ICs
and Clients) should all be operating
normally
Look at Link LEDs on device ports of
LAN interfaces to identify the failed
connection
Test UTP and fiber optic cable
connections
Corrective Action(s)
Reestablish Server connection to
network
Reboot Clients if necessary (Clients
may reboot automatically once
connection to the Database Server is
restored)
Reestablish Client connection to
network
Reboot Client if necessary (Client may
reboot automatically once connection
to the Database Server is restored)