Serviceguard command to get resources in a package

[Michelle_61]

Hi All,

I wonder if there are any commands in ServiceGuard that return resources (IP, file system, etc) defined in a package. For other clusters such as Veritas Cluster Server or SUN Cluster, there are commands that can display the resource information. How do we do the same on ServiceGuard? cmviewcl and cmgetconf only display package names and node names.

[Patrick Wallek]

Add the '-v' option to both commands and see if that helps.

When I ran 'cmgetconf -v' it returned VGs, IP address, etc.

[Michelle_61]

Do you define IP and FS in the package config file or do you defined them in the control file? For me I only define them in the package control file. Running "cmgetconf -v" still does not return IP and FS information. I guess it only shows information in the package config file?

[Michelle_61]

Actually the "cmgetconf -v" command display the information in the cluster config file. So the volume groups and IPs are not specific to any package. What I want is the information regarding to a specified package only.

[melvyn burnard · Accepted solution]

try cmviewcl -v -p
or for more info (if you have a later version of SG) cmviewcl -f line -v -p

[Michelle_61]

I did try the two commands you suggested, still not what I need. The information in the control file is not printed out. Below is the output of 'cmviewcl -f line -v -p xclock' (xclock is my package name):

bash-2.05a# cmviewcl -f line -v -p xclock
name=xclock
type=failover
status=down
state=halted
highly_available=no
summary=critical
autorun=disabled
owner=unowned
id=28161
all_cluster_nodes=true
initial_autorun=enabled
failover_policy=configured_node
failback_policy=manual
local_lan_failover_allowed=enabled
failfast=disabled
run_script=/etc/cmcluster/xclock/xclock.control
run_script_timeout=1200
halt_script=/etc/cmcluster/xclock/xclock.control
halt_script_timeout=1200
priority=no_priority
successor_halt_timeout=no_timeout
node:bu-donum|name=bu-donum
node:bu-donum|status=down
node:bu-donum|switching=enabled
node:bu-donum|last_run_time=1273698893
node:bu-donum|last_halt_time=1273699190
node:bu-donum|available=yes
node:bu-donum|type=Primary
node:bu-donum|order=1
node:bu-offero|name=bu-offero
node:bu-offero|status=down
node:bu-offero|switching=enabled
node:bu-offero|last_run_time=0
node:bu-offero|last_halt_time=0
node:bu-offero|available=yes
node:bu-offero|type=Alternate
node:bu-offero|order=2
subnet:10.5.162.0|name=10.5.162.0
subnet:10.5.162.0|node:bu-donum|status=up
subnet:10.5.162.0|node:bu-offero|status=up
service:xclock|name=xclock
service:xclock|id=1
service:xclock|failfast=disabled
service:xclock|halt_timeout=300
service:xclock|node:bu-donum|status=down
service:xclock|node:bu-donum|restart_limit=unknown
service:xclock|node:bu-donum|restart_count=0
service:xclock|node:bu-offero|status=down
service:xclock|node:bu-offero|restart_limit=unknown
service:xclock|node:bu-offero|restart_count=0
bash-2.05a#

[Michelle_61]

I found I was using a legacy package. If I use the new process to create a modular package, then all the VG, FS and IP information will be in the package config file. Therefore the command "cmgetconf -v 0 -p " will get what I need. Thanks for all the previous responses!

Just want to confirm, for the new modular packages, there will be no package control script for each package, is it correct?

[Uday_S_Ankolekar]

In modular package you don't have a control script.
If you want to run customer defined start and stop scripts use one from example directory called external_script

USA..