| Thanks for your reply,
The customer wants to have the trace of all LSM commands success or
not through the ASE. He think that is missing a LSM log files
(optionally configurable or not )
This customer had a problem referenced in note 1895, and I
explained him he did bad ASE processing ( see 1895.2)
But he would be happy if he saw what LSM commands occurs when he
does somrthing under asemgr like , modifying a service, relocarting,
putting it offline
Gilles.
|
| The customer wants to have the trace of all LSM commands success or
not through the ASE. He think that is missing a LSM log files
(optionally configurable or not )
One would have to modify the scripts themselves to get these commands to
echo to some location. There is no option right now to turn this action
on.
This customer had a problem referenced in note 1895, and I
explained him he did bad ASE processing ( see 1895.2)
But he would be happy if he saw what LSM commands occurs when he
does somrthing under asemgr like , modifying a service, relocarting,
putting it offline
It might be OK for him to turn on informational logging and look for
'lsm_dg_action start ...' run. This script is the one that configures
the LSM diskgroup. If this is run with success he can assume that the
commands I gave you in a previous note.
If indeed you have the same ase as in 1895, then the problem is not in
the start/configure of the LSM disk group. It is in the failure to
stop/deconfigure the LSM disk group on another node. When you force a
stop as in 1895 the administrator needs to do clean up himself before
the service should be put online anywhere.
If he really wants the exact commands, the other thing you/he can do is
read the shell scripts and follow the code path to see which ones get
run. I know this is ugly, but we just do not echo them anywhere. Here
is what you will find:
LSM configure during the start of a service:
voldisk online disk1 disk2 ... diskN
voldg -fC import diskGroup1
volrecover -sb -g diskGroup1
LSM deconfigure during the stop of a service:
voldg deport diskGroup1
(If this fails, we stop the LSM volumes if is OK to do so
volume -f -g Diskgroup1 stop volumeN
then retry the deport )
volutil voldisk offline disk1 disk2 ... diskN
-- Greg
[Posted by WWW Notes gateway]
|