Unexpected troubles were occurredwhen one MSCS server connected to Network.

[Former Member]

Hi Experts,

Recently, one of two MSCS Server was down.

After repair , we connected network.

And then Unexpected troubles were occurred.

I don't have no known cause,

therefore I might ask vague question.

If anyone has knowledge, please help me!

Example,

[Tue]

1.N/W connection trouble started on each server.

2.As we found that SAP DB Server (one of two MSCS, I call Server A) generated many packets,

we drew cable.

-> We are runnning under Fail over.

It means just Server B.

[Wed]

3.H/W vendor replace LAN Borad to Server A.

->it remain the same.

3#.When we started Server A,

Quorum moved to Server A from Serve B automatically.

Also SAP might started...

We judged that it was issue,

therefore we didn't execute Fail back.

Serve A remained stop.

4.About 2-3 hours, Unexpected troubles were occurred.

Example,

- Many Jobs stoped abnormaly.

- Non SAP Systems became unstable.

Thank you in advance.

Best Regards,

Toshi

Edited by: Toshikazu Takahashi on Oct 23, 2008 10:17 AM

[Former Member · Accepted solution]

For the failed job logs, is there anything being saved in the logs? One of the things to check is to see if you have the correct permissions set on the SAPMNT directory (a quick test would be to log in as sidadm and create test files in the various directories).

Have you looked at the dev_disp, dev_w0, dev_rd trace logs?

Post more info if it is available.

Thanks,

J. Haynes