this morning we wanted to exclude some nodes, but they were already excluded.
Now I'm searching for Logs/Msgs saying, what happend.
We can I see, when and who did the exclude?
From the ISC the Domain-Log (msgAdapter.log) conatins only msgs about stopping resources.
And there is no Log-Button for a selected node.
The resource-History tells "Warning: The resource's node has been excluded from automation", but no more.
In SAMP I looked in samlog, but found nothing.
This topic has been locked.
4 replies Latest Post - 2012-02-28T08:48:56Z by nukite8d
Pinned topic Auditing Exclude Node
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-02-28T08:48:56Z at 2012-02-28T08:48:56Z by nukite8d
Enrico_Joedecke 0100003SD587 PostsACCEPTED ANSWER
Re: Auditing Exclude Node2012-02-21T13:30:13Z in response to nukite8dHello Manfred,
from the SA MP side you can check the following:
This file contains all SA MP commands executed on this node, e.g. for exclude node:
>> User root invoked "samctrl -u a node1" on Mon Feb 20 14:58:39 CET 2012
2. samlog should show this information starting with SA MP 188.8.131.52, or higher:
>> 14:30:23.072027 T(4144227536) _RCD Node excluded: node1/Node/IBM.PeerNode
Re: Auditing Exclude Node2012-02-21T13:59:01Z in response to Enrico_JoedeckeHello Enrico,
thanks for the fast answer.
I look in the /var/ct/IBM.RecoveryRM.log. but I wasn't able to find the commands.
And as we are using SAMP 184.108.40.206, I couldn't find the samlog message.
I got the information, that one operator excluded the node by using the ISC. Isn't there any log-entry like the entries for Requests?
Enrico_Joedecke 0100003SD587 Posts
Re: Auditing Exclude Node2012-02-28T08:48:56Z in response to Enrico_JoedeckeHello Enrico,
back then I couldn't find the messages, but after some testing I saw
SAMA0612I for excludes and
SAMA0613I for includes.
Node domain: TSAMP_MWA_test_2 node: node02 has been excluded from automation on behalf of user XXX.
And after even more testing I noticed, why I couldn't find the first excludes:
The log-Button shows only the local msgAdapter.log
When you exclude the node, running the samadapter,
it first writes the SAMA0612I msg into the local msgAdapter-log, then moves the samadapter.
Looking in the new local msgAdapter.log gives no Exclude-Msg!
We hoped, to get the complete cluster-spanning log, using the button in the ISC-OC.