Boot Server State - Not Responding

[Anon Anon]

Hi,

From time to time we get a message on our boot servers that they are "not responding". This prevents activated OS deployments from going from Activated to Pending.
Problem can be solved by rebooting the server. Does someone know if there is a workaround that lets me fix the problem without having to reboot the entire server, or maby even the root cause.

Message under: Control Panel > Scalability Servers > All Scalability Servers > [servername]

Type: Scalability Server
Server Reigstered: [timestamp that seems OK]
Last Collection: [timestamp that seems OK]
Boot Server State: not responding (displayed in red)

[Anon Anon]

To my knowledge you can try:
caf stop sdmpcserver
caf start sdmpcserver

This will stop and start the PXE Service.

[Anon Anon]

Thanks,

I've tried doing that but have been unsuccessful so far. I will give it another try next time it happens.

[Anon Anon]

The next time this happens, can you verify that ports 67 and 69 are still listening? These will both be udp. To do this on a Windows box go to the command prompt and type netstat -an. If the list is too long to verify you can always pipe it out to a text file. IE: netstat -an > C:\netstatinfo.txt

Are there any other services installed on this box, other than ITCM? If you have TFTP services, DHCP or etc then these can interfere with the boot plugin.

[Anon Anon]

Thanks, I will try this asap.

Restarting and/or disabeling the SDMPCSERVER services sadly does not do it for me.

[Richard Little]

Hi Johan

What version are you on? There are various reasons that could explain this.

If you log a support issue I will be glad to help determine the cause.

we will need detail traces of the boot server and domain

The following CAF processes are involved in OSIM and the associated trace files are indicated
•
Configuration and State Management agent (ccsmagt)
o
TRC_CSMAGENT_X.LOG
•
Configuration and State Management agent controller (ccsmact)
o
TRC_CSMACT_X.LOG
•
Configuration and State Management database api server (ccsmapi)
o
TRC_CSMAPI_X.LOG
•
Configuration and State Management server (ccsmsvr)
o
TRC_CSMSERVER_X.LOG
•
Software Delivery boot server (sdmpcserver)
o
TRC_USD_MPCWORKER_X.log
To Trace OSIM you will need Detail level traces on these processes
Boot Server on Domain Manger
•
Cftrace –c set –l detail –f cstack –pp ccsmsvr –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmagt –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmact –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmapi –s 50000
•
Cftrace –c set –l detail –f usd –pp sdmpcworker –s 50000
Boot Server on Scalability Server
Domain Manager
•
Cftrace –c set –l detail –f cstack –pp ccsmsvr –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmagt –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmact –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmapi –s 50000
Scalability Server
•
Cftrace –c set –l detail –f cstack –pp ccsmsvr –s 50000
•
Cftrace –c set –l detail –f cstack –pp ccsmagt –s 50000
•
Cftrace –c set –l detail –f usd –pp sdmpcworker –s 50000

[Anon Anon]

Hi

Try to put the bootserver i detailmode and see if you can find 'DHCPFunc: PXE is not yet enabled, no OFFER or ACK will be sent' in the loggile TRC_USD_MPCWORKER_x.LOG
This is from knowledge base articel 437268.
I have had the same problem and it works in never version on ITCM
I have used this on ITCM r12.5 and Windows 2008 R2 bootserver.

Regards,
Per-Anders

[Anon Anon]

You can also try:

Caf disable sdmpcserver
Caf enable sdmpcserver

[Richard Little]

Did you get anywhere with this?
regards
Rich

[Kenneth Domingo]

richard_little wrote:

Did you get anywhere with this?
regards
Rich

Hello...

just wondering if there's a solution for this issue... we are currently experiencing the same in our environment... (running R12.5 sp1).

thanks.

regards,
ken

[Sai_Kiran]

Hi Ken,

We would need the DETAIL logs to investigate as to what is causing this problem.
This could be caused due to different reasons.
Could you please check if ccsmagent is running or not by running the following command:
caf status ccsmagt

Thank you.

Regards,.
Sai

[Anon Anon]

Hello,

I have same problems in some our servers.

One interesting thing is that one server with this problem its seems to be "duplicated" - only when you want move some PCs from one boot server to other(server with this problem) -> you will see this server(server with this problem) 2x (with error)... Do you have this additional symptoms too?

[Richard Little]

jan.siroky wrote:

Hello,

I have same problems in some our servers.

One interesting thing is that one server with this problem its seems to be "duplicated" - only when you want move some PCs from one boot server to other(server with this problem) -> you will see this server(server with this problem) 2x (with error)... Do you have this additional symptoms too?

Hi

If you are seeing duplicate Boot Servers then this will absolutly cause an issue and this needs to be cleaned up.

Please log a support call stating you have duplicate boot server and request test fix t1ed253

This fix provides a cmmand line utility (CCSMCMD) that can list and remove bootservers cleanly from the MDB even.

with this utility we use the following procedure to identify the bad entry in the MDB and remotve it

Step 1 identify the incorrect record
1.
On Domain Manager: apply the test fix T1ED253
2.
change into folder ...\DSM\bin
3.
Run the command

ccsmcmd listbootserver -u<user> -p<password>

This will show the two boot server entries
<bootserver>
<bootserver>

4.
On the running scalability server run the commands

caf setcomputername mybootserver
caf stop
caf start

5.
on Domain Manager run the commandto list the bootservers again:

ccsmcmd listbootserver -u<user> -p<password>

This will now show
<bootserver>
mybootserver

The incorrect entry is now identified as it has not changed with renaming of the Scalability Server

Step 2 remove the duplicate
1.
delete the "old" boot server <bootserver> by running the command

ccsmcmd deletebootserver -n <bootserver> -u<user> -p<password>

Step 3 rename Scalability server back to desired name

On the scalability server run the commands
1.
caf setcomputername <bootserver>
2.
caf stop
3.
caf start

regards
Rich

[Anon Anon]

richard_little wrote:

jan.siroky wrote:

Hello,

I have same problems in some our servers.

One interesting thing is that one server with this problem its seems to be "duplicated" - only when you want move some PCs from one boot server to other(server with this problem) -> you will see this server(server with this problem) 2x (with error)... Do you have this additional symptoms too?

Hi

If you are seeing duplicate Boot Servers then this will absolutly cause an issue and this needs to be cleaned up.

Please log a support call stating you have duplicate boot server and request test fix t1ed253

This fix provides a cmmand line utility (CCSMCMD) that can list and remove bootservers cleanly from the MDB even.

with this utility we use the following procedure to identify the bad entry in the MDB and remotve it

Step 1 identify the incorrect record
1.
On Domain Manager: apply the test fix T1ED253
2.
change into folder ...\DSM\bin
3.
Run the command

ccsmcmd listbootserver -u<user> -p<password>

This will show the two boot server entries
<bootserver>
<bootserver>

4.
On the running scalability server run the commands

caf setcomputername mybootserver
caf stop
caf start

5.
on Domain Manager run the commandto list the bootservers again:

ccsmcmd listbootserver -u<user> -p<password>

This will now show
<bootserver>
mybootserver

The incorrect entry is now identified as it has not changed with renaming of the Scalability Server

Step 2 remove the duplicate
1.
delete the "old" boot server <bootserver> by running the command

ccsmcmd deletebootserver -n <bootserver> -u<user> -p<password>

Step 3 rename Scalability server back to desired name

On the scalability server run the commands
1.
caf setcomputername <bootserver>
2.
caf stop
3.
caf start

regards
Rich

Strange its this:

- server was installed only one time(it wasnt duplicated) but its seems that is duplicated... basicaly it get one day status not responding and get error which I describe up....

I will try your step maybe it help me. Thank you for now

[Richard Little]

jan.siroky wrote:

Strange its this:

- server was installed only one time(it wasnt duplicated) but its seems that is duplicated... basicaly it get one day status not responding and get error which I describe up....

I will try your step maybe it help me. Thank you for now

Hi

The duplication does not require you to have installed the SS twice but if it has occurred then it causes problems as when the OSIM manager looks up the bootsrever in the mdb it may select wither the good or the bad entry.
regards
Rich

[Anon Anon]

richard_little wrote:

jan.siroky wrote:

Strange its this:

- server was installed only one time(it wasnt duplicated) but its seems that is duplicated... basicaly it get one day status not responding and get error which I describe up....

I will try your step maybe it help me. Thank you for now

Hi

The duplication does not require you to have installed the SS twice but if it has occurred then it causes problems as when the OSIM manager looks up the bootsrever in the mdb it may select wither the good or the bad entry.
regards
Rich

I will try make your steps and I will put here feedback. Thx

[Anon Anon]

Hi Jan,

Try this.

Stop CAF on Scalability Server.
After CAF Stop copy all files from this location i.e.
<Program Files>\CA\DSM\Server\SDBS\inst\

and paste to this location.
<Program Files>\CA\DSM\Agent\CCSM\

Start CAF & check if your boot Server is working fine or not.

Also let me know if you got this error after upgrading Scalability Server to CA ITCM 12.5 SP1 & since then Boot Server is not working & showing in Not Responding state for Scalability Server.

Regards
Ravi

[Anon Anon]

Ravi.Shanker_Singh wrote:

Hi Jan,

Try this.

Stop CAF on Scalability Server.
After CAF Stop copy all files from this location i.e.
<Program Files>\CA\DSM\Server\SDBS\inst\

and paste to this location.
<Program Files>\CA\DSM\Agent\CCSM\

Start CAF & check if your boot Server is working fine or not.

Also let me know if you got this error after upgrading Scalability Server to CA ITCM 12.5 SP1 & since then Boot Server is not working & showing in Not Responding state for Scalability Server.

Regards
Ravi

Hi thank you for your ideas I will start update in this days,.. and I will inform you when I will finnish

[Anon Anon]

Hello,

its seems that helps clear all error msgs. and update CA to SP1....now its seems thats all works fine.

[Anon Anon]

Thanks for the update Jan. Make sure you check the "Mark as Accepted Solution" in the posts that helped you to resolution. You need to be logged in to see the box. It is in the upper right corner of the post.

Mary