Control Station problem or not?

Hi,

We use a redundant NX4 system, I could not reach a the firs Control station over http, but I can reach it on ssh. (The second work well)

I try to use "/nas/http/nas_ezadm/etc/script restart" command, but nothing happend...

After reboot I got a message:

Message from syslogd@nx4cs at Fri May 13 11:48:19 2011 ...
nx4cs EMCServer: ReportEvent: CCMD 70338543628:CS_PLATFORM(6):MasterControl(129):EMERGENCY(0):12

------------------

The getreason command output is:

10 - slot_0 primary control station
4 - slot_2 configured
4 - slot_3 configured

--------------------------

The /nas/bin/nas_checkup command output is:

[root@nx4cs sbin]# /nas/bin/nas_checkup
Check Version:  5.6.47.11
Check Command:  /nas/bin/nas_checkup
Check Log    :  /nas/log/checkup-run.110511-125415.log

-------------------------------------Checks-------------------------------------
Control Station: Checking if NBS clients are started....................... Fail
Control Station: Checking if NBS configuration exists...................... Pass
Control Station: Checking if NBS devices are accessible.................... Fail
Control Station: Checking if NBS service is started........................ Fail
Control Station: Checking if NAS partitions are mounted.................... Pass
Data Movers    : Checking status........................................... Pass
--------------------------------------------------------------------------------

One or more error-level checks have failed. Follow the instructions
below to correct the problem and try again.

-------------------------------------Errors-------------------------------------
Control Station: Check if NBS clients are started
Symptom: NBS clients (nd-clnt 0 1 and nd-clnt 4 5 and nd-clnt 5 6) are
         not started
Action : Contact EMC Customer Service and refer to EMC Knowledgebase
         emc146016. Include this log with your support request.

Control Station: Check if NBS devices are accessible
Symptom: Failed NBS (nd-clnt processes) devices access check

         NOTE: Several checks depend on NBS device access to run. These checks
               were not run.
Action :
         1. This may occur if NBS is not configured correctly or if the NBS
            service is not started. Look in the "Checks" section to see if the
            following checks passed:

            * Control Station: Check if NBS configuration exists
            * Control Station: Check if NBS service is started
            * Control Station: Check if NBS clients are started

         If either of those checks did not pass, follow the instructions for
         that check to correct the problem, then rerun "nas_checkup" to verify
         that the NBS devices can now be accessed.
         2. This may also occur if Data Movers are powered down or pulled out.
            If you are on the primary Control Station, look in the "Checks"
            section to see if the following check passed:

            * Data Movers: Check status

         If this check failed, follow its instructions to correct the
         problem, then rerun "nas_checkup" to verify that the NBS devices can
         now be accessed.
         3. If the problem persists, escalate this issue through your support
            organization. Provide this output and any errors or output that
            occurred running the commands in this procedure in the escalation.

Control Station: Check if NBS service is started
Symptom: NBS (nd-clnt processes) service is not (or not fully) started
Action : Use the command "/sbin/service nbs start" to restart the NBS
         service or reboot the Control Station.

----------------------

/sbin/service nbs start not solved our problem....

So is there any idea?