Emerson 5500 SERIES Thin Web Server, Troubleshooting, Symptom, Possible, Action, Prevention

Models: 5500 SERIES A5510

1 43
Download 43 pages 45.22 Kb
Page 36
Image 36
Manual background

Thin Web Server

Troubleshooting

Symptom

7.TWS booted but cannot communicate to any remote _72E.

8.TWS reports communication error.

9.TWS email date and time received are incorrect.

Possible Problem TWS is not connected to

LAN.

72Es are not connected to the LAN.

Devices were not properly connected to the TWS. System DST, date, and time are not properly setup.

Possible

Action

Prevention

Cause

 

 

– Check first if any client

– Run your TSSP, and verify saved 72E

– Make sure the TWS and all the

station within the LAN can

record lists. Make sure the addresses

remote 72Es are configured

communicate with the

you assigned in the list are addresses

properly. They should have TCP

TWS. User can try to ping

given to you by the LAN administrator.

settings assigned by the LAN

the TWS from the client

These addresses are the actual addresses

administrator.

station. If you get no

used by the remote 72Es the TWS will

– Follow Installation Manual 381333-

response, solve this address

be communicating to.

238 to configure the Acc. 72Es.

problem before proceeding.

– After every upload, make sure to

– Confirm every 72E record before

– If your client station is able

download the configuration to make

uploading it to the TWS.

to ping the TWS, then you

sure the data was uploaded properly to

– Use the correct TSSP version for

might need to rerun your

the TWS.

the TWS. The TSSP and TWS

TSSP and try downloading

– Make sure that after every download to

firmware versions must be the

from the 72E list records.

reset the TWS for a fresh restart.

same.

Make sure there are

– You can use a client station within the

 

uploaded 72E IP addresses

LAN to verify the presence of the TWS

 

to the TWS.

and the remote 72Es. You can do this

 

– The 72Es that the TWS is

by pinging each of them through the

 

attempting to talk to are not

ping utility in DOS. Those that do not

 

configured properly to the

reply are the ones that cannot

 

LAN and may be connected

communicate within the LAN.

 

to a different LAN.

– For 72Es not responding from your ping

 

– If the TWS and the 72Es

request from a client station, you can

 

are connected locally

revisit their configuration and confirm

 

through a hub, make sure

their settings.

 

the hub is powered ON and

– Make sure to call ASI for assistance

 

can support 10/100 Mbps

when symptoms become apparent and

 

devices.

conditions worsen.

 

Same as item 6

Same as item 6

Same as item 6

– Forgot to setup the DST and

– Set the DST and system date and time

– The first time you configure the

system time.

accordingly.

TWS, make sure to check and

– Incorrect DST setting.

 

apply correct DST, sytem date, and

 

 

time.

 

 

– Make a monthly check for the

 

 

system data and time through

 

 

system configuration page to

Page 36
Image 36
Emerson 5500 SERIES, A5510 Thin Web Server, Troubleshooting, Symptom, Possible, Action, Prevention, Cause