arif/xcat-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc updates for xcatmon

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@5463 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
linggao 2010-03-12 21:46:11 +00:00
parent ec4a054d0e
commit 30510f6dc3
4 changed files with 20 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
perl-xCAT/xCAT/Schema.pm
View File

@ -414,9 +414,9 @@ nodelist => {
groups => "A comma-delimited list of groups this node is a member of. Group names are arbitrary, except all nodes should be part of the 'all' group.",
status => 'The current status of this node. This attribute will be set by xCAT software. Valid values: defined, booting, netbooting, booted, discovering, configuring, installing, alive, standingby, powering-off, unreachable. If blank, defined is assumed. The possible status change sequenses are: For installaton: defined->[discovering]->[configuring]->[standingby]->installing->booting->booted->[alive], For diskless deployment: defined->[discovering]->[configuring]->[standingby]->netbooting->booted->[alive], For booting: [alive/unreachable]->booting->[alive], For powering off: [alive]->powering-off->[unreachable], For monitoring: alive->unreachable. Discovering and configuring are for x Series dicovery process. Alive and unreachable are set only when there is a monitoring plug-in start monitor the node status for xCAT. Please note that the status values will not reflect the real node status if you change the state of the node from outside of xCAT (i.e. power off the node using HMC GUI).',
statustime => "The data and time when the status was updated.",
appstatus => "A comma-delimited list monitored applications that are active on the node. For example 'sshd,rmcd,gmond",
appstatustime => "The date and time when appstatus was updated.",
primarysn => "Not used currently. The primary servicenode, used by this node.",
appstatus => "A comma-delimited list of application status. For example: 'sshd=up,ftp=down,ll=down'",
appstatustime =>'The date and time when appstatus was updated.',
primarysn => 'Not used currently. The primary servicenode, used by this node.',
comments => 'Any user-written notes.',
disable => "Set to 'yes' or '1' to comment out this row.",
},

BIN
xCAT-client/share/doc/xCAT2-Monitoring.odt
View File

Binary file not shown.

BIN
xCAT-client/share/doc/xCAT2-Monitoring.pdf
View File

Binary file not shown.

21
xCAT-server/lib/xcat/monitoring/xcatmon.pm
View File

@ -408,10 +408,23 @@ sub processSettingChanges {
sub getDescription {
return
" Description:
xcatmon uses fping to report the node liveness status and update the
nodelist.status column. Use command 'monstart xcatmon -n' to start
xcatmon provides node status monitoring using fping on AIX and nmap on Linux.
It also provides application status monitoring. The status and the appstatus
columns of the nodelist table will be updated periodically with the latest
status values for the nodes. Use command 'monstart xcatmon -n' to start
monitoring.
Settings:
ping-interval: the number of minutes between each fping operation.
The default value is 3.";
ping - interval: the number of minutes between each fping operation.
The default value is 3.
apps -- a list of comma separated application names whose status will be queried.
For how to get the status of each app, look for app name in the key filed
in a different row.
port -- the application daemon port number, if not specified, use internal list,
then /etc/services.
group -- the name of a node group that needs to get the application status from.
If not specified, assume all the nodes in the nodelist table.
To specify more than one groups, use group=a,group=b format.
cmd -- the command will be run locally on mn or sn.
dcmd -- the command will be run distributed on the nodes (xdsh <nodes> ...).";
}