Need help with SG 11.18 & above

[Manix]

Hi ALl !!

I am well worst with SG 11.17 ( non modular packages ) configuration and implementation ,
would like to know the steps and changes to configure SG version & above 11.8 with modular packages.

Thanks in advance !!

[Manix]

referred to following links

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=10008&contentType=SupportManual&docIndexId=64255&prodTypeId=18964&prodSeriesId=4162060

[hpuxrocks]

Hi Manix ,
apologies for replying in this thread, I really wanted to email you with regard to a response you gave out on a different thread. It was ..MCSG debug mode

cd /etc/cmcluster
touch debug
cd /etc/cmcluster/
touch debug
cmrunpkg

To undo what you have done, just delete the two debug files you just created.

There was a recent discussion on this Where
Duncan quoted "DEBUGMODE is a mechanism which generally allows you to start a package up, but not start the actual application in the package - so volume groups get activated, filesystems get mounted and IP addresses get added, but no processes are started. DEBUGMODE also usually stops package monitoring so processes can be started/stopped without causing a package failover."

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1467586

Hope this helps.

Manix
.....

So my questions would be:

1. Isnt debugmode a cluster level thing , so wouldnt you need to restart the cluster to bring up a package in debugmode ?
If you just start the package, the cluster is still monitoring the resources etc ?..therefore I would have thought that bringing down the application under said package would still cause the package to come down ?

2. You suggested 2 debug files, 1 at cluster level at the other at package level. Are 2 needed (without a restart) ?

3. Again, how would the config files be updated by simply removing the files, wouldnt you need to restart the cluster / package ?

4. If shutting down the applications, without the package stopping is what is required, why not just shut off resource monitoring for that package ? wouldnt that achieve the same end without the need to restart the cluster / package ?

Im asking these question because I actually dont know the answers to them rather than challenging your answers. If one looks at the answers to "what is debugmode" etc ...there doesnt seem to be a standard answer. Again I hope you dont mind me asking in the way I have and in a closed thread, I figured at least you would receive it.

[Manix]

I believe it`s more a package related thing..
so restart of package is required not the cluster ,I may see that this mode is more
applicable for the Oracle /SAP instances running in the cluster.

There are couple of ways to achieve it,
one as mentioned by Steven Doud that do the
changes in start /stop scripts in the
package.cntrl script.

And other could be to stop the application monitors but that may impact the other packages too !!

Need to check if it documented in other
MCSG manuals as well, do read the below
licks ,would be helpful.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1341634

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1182832

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02047909/c02047909.pdf?jumpid=reg_R1002_USEN

Thanks
Manix

[hpuxrocks]

thks ! the last link implied that the "debug" file seemed to be very specific to the Message server monitor ...of course it doesnt help if you dont actuallu have one running. I suppose to achieve a similar end, you would either edit the control script or remove the resourse check/ dependancy as long as you were sure that it wouldnt affect anyother package. Thks !