SPM v2 - AIX Client Guide. Download the PDF HERE
SPM v2 - AIX Client Guide
|
Contents
Overview of SPM v2. 3
AIX Client Guide Overview.. 3
Downloading SPM v2 Client Software. 3
Basic Installation and Configuration. 3
Data Collection. 4
Additional Configuration Options. 4
‘config/spam2.conf’ file. 4
‘config/spam2chkprocs.conf’ file. 6
‘config/spam2chkfiles.conf’ file. 6
‘config/tunable.regexp’ file. 7
Complete list of AIX commands used by the SPM v2 client code. 7
SPM v2 is a set of tools to help manage change in an AIX environment. The product is a client-server architecture and is focused on five functional areas: collection of configuration, reporting configuration changes, comparing configurations, extracting configuration, and searching for configuration changes. Each of these functional areas also includes reporting and export capabilities.
The collection of configuration is achieved by installing a client package on all systems that will be managed in SPM v2. The client package is provided in native AIX ‘.bff’ format. The package installs software on your client system and runs a regularly scheduled job to collect information and update the SPM v2 server.
The other functional areas (reporting configuration changes, comparing configurations, extracting configuration, and searching for configuration changes) are accessed via web browser through the SPM v2 Server’s web interface.
This guide provides detailed information on installing and configuring the AIX client parts of SPM v2.
1. Navigate in your browser to http://www.sinc-all.com
2. Login to the site via the ‘Login’ link on the left side of the page.
a. If you have not registered, take a moment to register and create an account.
3. Once you are logged in, click the ‘Client Download’ link on the left side of the page.
4. To download the client, click the ‘SPM v2 Client (AIX)’ package.
5. The package will be downloaded as ‘.gz’ compressed ‘.bff’ file. The package will need to be uncompressed before it can be installed, so the `gunzip` utility will be required.
Once downloaded, perform the following steps to install and configure the SPM v2 client:
1. Copy the uncompressed ‘.bff’ file into ‘/tmp’ on the client system.
2. Install the package using AIX `installp`.
a. `installp –aYd /tmp/sincall.spam2-2.2.0.x.bff all`
b. All files are installed into ‘/opt/spam2’
c. A cron entry is created in ‘/var/spool/cron/crontabs/root’
3. Edit the ‘/opt/spam2/config/spam2.conf’ file.
a. Modify the ‘cvsroot’ variable by replacing ‘localhost’ with the name of your SPM v2 Server’s hostname. The SPM v2 Server’s hostname must be pingable from the client.
b. Optional: Modify the ‘cvsroot’ variable by replacing ‘/opt/spam2/cvs/ServerChanges’ with the fully qualified path of the repository on the SPM v2 Server.
After a basic configuration has been completed, you can manually initiate a client collection and make sure everything is configured correctly instead of waiting for it to run via cron.
· On the client(s): Run `/opt/spam2/spam2`
The collection has a series of high-level steps:
1. If the ‘cvsPush’ parameter is ‘on’ in the ‘config/spam2.conf’ file, or the ‘-x’ was not specified at the command line:
a. Connect to the Server (specified by the ‘cvsroot’ parameter) and download data for the client.
2. Perform data collection on each data modules specified by ‘modules’ in the ‘config/spam2.conf’ file, or by the ‘-m’ command line flag.
a. Data collection is stored locally on the client in the path specified by ‘fsReportPath’. XML versions of the data are stored locally in ‘fsReportPath’/xml.
3. If the ‘cvsPush’ parameter is ‘on’ in the ‘config/spam2.conf’ file, or the ‘-x’ was not specified at the command line:
a. Connect to the Server (specified by the ‘cvsroot’ parameter) and upload data for the client.
The following configuration files and options can be used to further customize the SPM v2 client:
‘config/spam2.conf’ file
· Description: primary configuration file for the SPM v2 client. This file must be in ‘.ini’ format with a ‘[prod]’ header section.
· Parameters:
a. fsHomePath
i. Description: specifies the root location of the SPM v2 installation. Although the package installer uses ‘/opt/spam2’, SPM v2 could be relocated to any directory.
ii. Default: ‘/opt/spam2’
iii. Valid Values: any fully qualified directory name.
iv. NOTE: if this variable is changed, you must also change the ‘spam2server.conf’ configuration file. *Changing this variable is not recommended.
b. fsReportPath
i. Description: specifies the location to read and write files that determine configuration state.
ii. Default: ‘/opt/spam2/reports’
iii. Valid Values: any fully qualified directory name.
iv. NOTE: Each host will have six state files that will always be approximately 8KB in size.
c. logFacility
i. Description: specifies the syslog facility or fully qualified file name to use for logging.
ii. Default: ‘/tmp/spam2.log’
iii. Valid Values: any fully qualified file name, or any user syslog facility (local1-local9).
d. cvsroot
i. Description: specifies the CVS root destination for the client.
ii. Default: ‘:pserver:root@localhost:2403/opt/spam2/cvs/ServerChanges’
iii. Valid Values: any fully qualified directory name, or a CVS pserver location string.
|
CVS pserver location string syntax
:pserver:root@{SPM_server}:{CVS_serverport}/{path_to_cvsroot}
· {SPM_server} is the hostname of the SPM v2 Server instance.
· {CVS_serverport} is the CVS port listening on the Server instance, default is 2403.
o !! client must have network access to the server on this port !!
· {path_to_cvsroot} is the CVS root destination on the SPM v2 Server instance.
|
e. cvsPush
i. Description: specifies the network behavior of the client. If this parameter value is set to ‘on’, the client will attempt to connect to the SPM v2 Server instance’s CVS root destination (as specified by the ‘cvsroot’ parameter).
ii. Default: ‘on’
iii. Valid Values: ‘on’, or ‘off’
iv. NOTE: this parameter can be overridden to ‘off’ at the command line using the ‘-x’ flag.
f. modules
i. Description: specifies which modules of data the client will collect. Modules of data are simply logical groupings (i.e. network, file system, etc.)
ii. Default: ‘all’
iii. Valid Values: comma separated list of available modules, or ‘all’ to collect all data.
iv. NOTE (a): when using ‘all’, modules can be individual excluded by prefixing modules with a hyphen (i.e. ‘all,-fs’).
v. NOTE (b): modules can be overridden at the command line using the ‘-m’ flag followed by a comma separated list of module names.
vi. Note (c): because of several unfixed known bugs, the ‘fcs’ module is not included when ‘all’ is specified. ‘fcs’ must be used explicitly (i.e. ‘all,fcs’) and is a subcategory of data inside the Device and Network modules.
|
Available modules
· dev,net,fs,nfs,vg,lv,pv,ps,lpar,lpp,prnt,pgsp,tune,sys,usr,grp,file,nim,rsct,fcs
· Located within the ‘fsReportPath’ directory, the data collected by these values translate into files named (respectively): Device, Network, FileSystem, VolumeGroup, LogicalVolume, PhysicalVolume, Process, Partition, LPP, Printer, PagingSpace, Tunable, System, User, Group, SysFile, NIM, RSCT
|
· Default File:
|
[prod]
fsHomePath = /opt/spam2
fsReportPath = /opt/spam2/reports
logFacility = /tmp/spam2.log
cvsroot = :pserver:root@localhost:2403/opt/spam2/cvs/ServerChanges
cvsPush = on
modules = all
|
‘config/spam2chkprocs.conf’ file
· Description: extension of the primary configuration for monitoring specific processes. The file must contain one entry per line. By default this file is empty.
· Line Syntax:
a. ‘user’ ‘process_name’
i. ‘user’ is any valid Unix username listed in /etc/passwd.
ii. ‘process_name’ must be the process command name without path.
b. NOTE: active processes listed from 'lssrc' are automatically checked by SPM v2 client, and do not need to be specified.
· Example:
|
root diagd ## monitor diagd processes owned by the root user
wasadmin java ## monitor java processes owned by the wasadmin user
|
‘config/spam2chkfiles.conf’ file
· Description: extension of the primary configuration for monitoring specific files. The file must contain one entry per line. By default this file is empty.
· Line Syntax:
a. /full_path/to_filename
i. any fully qualified file name
b. NOTE (a): If the file is a text file its contents will be included in CVS. Binary files will only store a checksum.
c. NOTE (b): including extremely large text files may degrade performance of the client.
· Included Files:
a. The following files are automatically checked by SPM v2 client, and do not need to be specified:
|
/var/spool/cron/crontabs/root
/var/spool/cron/crontabs/adm
/etc/inittab
/etc/inetd.conf
/etc/protocols
/etc/shells
/etc/profile
/etc/environment
/etc/hosts.lpd
/etc/hosts.equiv
/etc/hosts.allow
/etc/hosts.deny
/usr/lib/security/methods.cfg
/usr/lib/Mail.rc
/etc/security/services
/.profile
/opt/spam2/config/spam2.conf
/opt/spam2/config/spam2chkfiles.conf
|
‘config/tunable.regexp’ file
· Description: extension of the primary configuration for overriding tunable exclusions. Some tunables change dynamically and generate “noise”. SPM v2 client has some built-in exclusions that can be overridden by this file. The file must contain one entry per line. By default this file is empty.
· Line Syntax:
a. ‘lowercase_tunable_command’:’regular_expression’
i. ‘lowercase_tunable_command’ is one of the following: ‘vmo’,’ioo’,’schedo’,’no’,’nfso’.
ii. ‘regular_expression’ is a match for the tunable name.
b. NOTE: if this file contains any uncommented lines, the built-in tunable exclusions will be ignored.
· Example:
|
vmo: ^pinnable_frames$|^maxpin$ ## if using this file, recommend include
ioo: ^lvm_bufcnt$|^maxpgahead$
schedo: ^pacefork$
no: ^tcp_sendspace$|^udp_recvspace$
nfso: ^nfs_rfc1323$
|
Although commands listed here may be used to modify a system’s configuration, SPM only uses command flags that provide read-only display of current configuration.
|
audit
|
bootinfo
|
bootlist
|
bosdebug
|
cat
|
df
|
|
diaggetrto
|
emgr
|
fcstat
|
fixmgr
|
getlvmodm
|
hostent
|
|
ioo
|
ioscli
|
lparstat
|
lpstat
|
lquerylv
|
lquerypv
|
|
lqueryvg
|
lqueryvgs
|
ls
|
lsallq
|
lsattr
|
lsauthent
|
|
lscfg
|
lscondition
|
lscondresp
|
lscons
|
lscore
|
lsdev
|
|
lsfilt
|
lsfs
|
lsgroup
|
lslicense
|
lslpp
|
lsnfsexp
|
|
lsnfsmnt
|
lsnim
|
lsps
|
lsque
|
lsquedev
|
lsrsrc
|
|
lssec
|
lssrc
|
lsuser
|
lsvfs
|
lswpar
|
lvmo
|
|
namerslv
|
netstat
|
nfso
|
no
|
oslevel
|
powermt
|
|
schedo
|
ssaxlate
|
suma
|
syscorepath
|
uname
|
vmo
|
|
vmtune
|
|
|
|
|
|