The manager is not online

[Anon Anon]

on Scalablity server the manager is not online. when I check the availablity of the manager on scalablity server, i get a error message stating that the manager is not online. But on the server all the services are running. can any one suggest

[Jordi Palomeras i Porta]

Hi Sahaya.

Can you please provide the commands you use to check the status on the scalability server?

What is the 'manager' which is not online on a Scalability server?

Thanks.

Jordi.

[Anon Anon]

Hi jordi,

             cserver check -c

Ths is the command I used on the scalablity to check the avaiablity of the dsm remote control manager. 

 

PsExec v1.98 - Execute processes remotely

Copyright (C) 2001-2010 Mark Russinovich

Sysinternals - www.sysinternals.com

 

 

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

 

C:\Windows\system32>cserver check -c

ITCM Common Scalability Server v12.5.1000.767

Copyright (c) 2012 CA. All rights reserved.

 

Checking manager availability on 'HOCAITSMPRD2V'...

 

[Jordi Palomeras i Porta]

Hi sahaya,

This means that the computer HOCAITSMPRD2V, which is supposed to be the Domain Manager this scalability server is depending on, cannot be contacted.

In order to verify it, please provide the output of the following commands:

ping HOCAITSMPRD2V

camping HOCAITSMPRD2V -s 8192

camping HOCAITSMPRD2V -a

caf ping HOCAITSMPRD2V

Thanks and regards,

Jordi.

 

[Anon Anon]

Hi jordi,

               Find the output below.

C:\Windows\system32>ping HOCAITSMPRD2V

 

Pinging hocaitsmprd2v.ALRAJHI.BANK [10.0.34.33] with 32 bytes of data:

Reply from 10.0.34.33: bytes=32 time=15ms TTL=119

Reply from 10.0.34.33: bytes=32 time=13ms TTL=119

Reply from 10.0.34.33: bytes=32 time=13ms TTL=119

Reply from 10.0.34.33: bytes=32 time=58ms TTL=119

 

Ping statistics for 10.0.34.33:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 13ms, Maximum = 58ms, Average = 24ms

 

C:\Windows\system32>camping HOCAITSMPRD2V -s 8192

1:  reply from HOCAITSMPRD2V, rtt 172ms

2:  reply from HOCAITSMPRD2V, rtt 172ms

3:  reply from HOCAITSMPRD2V, rtt 171ms

4:  reply from HOCAITSMPRD2V, rtt 250ms

camping: Trying 10.0.34.33 ...

 

 

HOCAITSMPRD2V: camping done, statistics:-

Sent 4, completed 4, packet size 8192 bytes.

Round-trip (ms) min/ave/max = 171.0/191.3/250.0.

Timed out 0 (0%) (detected: late discard return 0, late completion 0)

 

C:\Windows\system32>camping HOCAITSMPRD2V -a

Local reverse lookup gave: HOCAITSMPRD2V

 

CAM on "HOCAITSMPRD2V" is alive.

 

The remote computer identifies itself as:-

 

        "HOCAITSMPRD2V.alrajhi.bank" at address 10.0.34.33

 

and knows this computer as:-

 

        "bur121w01.alrajhi.bank" at address 10.184.85.69

 

Note: returned remote hostname differs from local reverse lookup!

 

This computer calls itself "bur121w01.alrajhi.bank" at address fe80::5c9f:332a:

984:bd4b%12

camping: Trying 10.0.34.33 ...

 

[Jordi Palomeras i Porta]

Hi sahaya,

Thanks for your prompt respomse.

The results look OK. So it is not expected to get this message.

Just to confirm it, did you run the previous commands from the scalability server?

Thanks

Jordi.

 

[Anon Anon]

Hi jordi,

            Yes, I ran the command from the scalablity server. If the results are fine. what might be the cause?

[Jordi Palomeras i Porta]

Hi sahaya,

hmmmm, good question.

Probably the cserver command communicates with a process in the DM side to verify that it is actually a DM.

Does 'caf status' on the Domain Manager show all the processes up and running? I think that you stated the DM was running all the processes, don't you?

If this is the case, I think it is better to open a support issue as this problem has to be worked with more detail.

Thanks and regards,

Jordi.

[Abdul Samad Mohammed]

Hi,

Could you please run the below commands on the Scalability Server to re-register it with the Domain Manager:

cserver unregister
cserver config -h domainname -j
cserver register -a
caf setserveraddress localhost
caf register all

Regards,
Samad

 

 

 

 

[Anon Anon]

Hi samad,

                  It is working fine. It seems to be issue with the database connectivity. 

[Richard Little]

Hi

Do you need further advice on this?

Rich