This package is the IBM POS SSD Life Monitor Drivers for Linux 1.0 instrumentation. This package monitors fixed Solid State Disks on an IBM POS system to determine when the number of writes to an SSD is reaching lifetime maximum.
The ibm-ssddrv-suse-1.0.0-1.0.i586.rpm contains the user mode libraries and support files that form the main part of the instrumentation. This rpm requires that the sblim-sfcb cimserver and the sysfsutils packages are already installed.
% rpm -ivh ibm-ssddrv-suse-1.0.0-1.0.i586.rpm
This will install the ssddrv libraries, update the SFCB repository with class definitions for RSS_SSDLifeMonitor and RSS_SSDLifeMonitorFailureImminent CIM classes. It will also install a boot script into /etc/init.d called ibm-vpdacpi which is used to start the accomanying IBM kernel module - aipvpdacpi.ko. The module allows the BIOS system event log to be updated when an SSD approaches the end of its useable (writeable) life. This is only supported on the latest IBM POS systems and is not implemented for earlier systems. The driver is open-source and available from the PLDP release site for Service Pack 2. This driver is optional and the instrumentation will run without it. If utilized the ibm-vpdacpi script needs to be enabled (by root) as shown below:
% insserv ibm-vpdacpi
Currently supported systems are:
The instrumentation may run on IBM POS systems other than those listed above but no testing has been done on such systems.
Most IBM customers will want to use RMA to allow interconnection of the instrumentation CIM classes to remote systems management software such as IBM Director. After install of the instrumentation the RMA General Agent daemon on the POS machine should be stopped and restarted in order to pick up cimserver repository and other system changes.
More about RMA can be found at: IBM Remote Management Agent V2 R6
The drivers have two configuration options available by editing the /etc/ssddrv/ssddrv.ini file.
min=10% max=100% default 95%
default is every 10 seconds
The drivers log abnormal conditions to /var/log/ssddrv/ssddrv.log. For normal production usage there is no need to change this behaviour. In fact it is not recommended. If any problems surface however additional information may be logged for purposes of support.
To enable detailed logging edit the /etc/ssddrv/log.conf file. Change the Level property to 4 to enable very detailed trace logging. You may also wish to change the MaxLength property if you wish to log for any length of time as the logfile will fill quickly. Recycle the SFCB cimserver so that the instrumentation libraries pick up the logger configuration changes.
Log Levels:
Wed Feb 8 2012 - Initial version