This chapter describes the restrictions of using TPSSM in the IRIX environment, identifying volumes by device names, stopping and starting TPSSM, disabling and enabling the Event Monitor, and uninstalling storage management software.
Table 4-1 provides information on the restrictions that apply to using TPSSM in the IRIX environment.
 | Note: Always check for a README file on the CD-ROM. This README file might contain important, late-breaking information that was not available when this Administration Guide was written. Also, see release notes, which contain a list of known issues, bug fixes, as well as enhancements. See the README file on the CD-ROM for instructions on how to view the release notes. |
Table 4-1. Restrictions for the IRIX Operating Environment
The host-util software includes a utility that lets you see which Storage Array volume is associated with a particular operating system device name. Tpssmdevice provides a detailed listing of IRIX device names to the Storage Array Volume names and their World Wide Name IDs. This capability is useful for operations such as data placement and volume deletion.
To use the utility, enter the following:
> tpssmdevices |
The software displays device identification information. The table below shows an example output with a description of each column.
| Note: If /usr/sbin is not contained in the PATH environment variable, the full path name is required on the command line (/opt/tpssm/util/tpssmdevices). |
Table 4-2. Device Identification Information
Entry in IRIX | Controller Name | Volume Group | Vol. Name | |
|---|---|---|---|---|
/dev/scsi/sc11d1l8 | [Storage Array RAID7/8, | Volume LUN 0, | LUN 0, | WWN <600a0b80000664d400000073396cd12f>] |
On IRIX systems, follow these procedures to stop and start the host-agent software installed on the host.
You must stop the host-agent software if you want to add Storage Arrays. When you restart the software, the host-agent discovers the new Storage Arrays and adds them to the management domain.
To stop the host-agent software, enter the following:
> /etc/init.d/tpssmagent stop
The host-agent software automatically starts after you reboot the host. However, you must start the software manually if you stop it to add Storage Arrays.
To start the host-agent software, enter the following:
> /etc/init.d/tpssmagent start
Note: It might take several minutes for the agent deamon startup process to complete. Note: The agent will not be started if the tpssmagent configuration flag is set to off (see chkconfig(1M) for details).
On Linux systems, follow these procedures to stop and start the host-agent software installed on the host.
You must stop the host-agent software if you want to add Storage Arrays. When you restart the software, the host-agent discovers the new Storage Arrays and adds them to the management domain.
To stop the host-agent software, enter the following:
> /etc/rc.d/init.d/tpssmagent stop
The host-agent software automatically starts after you reboot the host. However, you must start the software manually if you stop it to add Storage Arrays.
To start the host-agent software, enter the following:
> /etc/rc.d/init.d/tpssmagent start
Note: It might take several minutes for the agent deamon startup process to complete. Note: For Altix systems with 2.4.x kernels and XSCSI software subsystem, you must invoke the following before starting the agent, where CDROM is the mount point of the CD-ROM drive.
> cp /CDROM/Linux/client/xscsi_to_sg_utm_init /opt/tpssm/agent
> /opt/tpssm/agent/xscsi_to_sg_utm_init
The Event Monitor, which is packaged with TPSSM client software, monitors storage arrays and handles error notification through e-mail or SNMP traps when the storage management software is not actively running on the storage management station or host.
| Note: If you installed TPSSM client software and configured alert notifications on multiple machines, you may receive duplicate error messages from the same storage array. To avoid receipt of duplicate error messages, disable the Event Monitor on all but one machine. It is recommended that you run the Event Monitor on one machine that will run continually. |
| Note: If using direct (network) management, only one machine should be running the Event Monitor software. |
You can disable and enable the event monitor without having to reboot a management station (workstation) or host (server), or you can permanently disable or enable the boot-time loading of the event monitor.
On IRIX systems, enter the following to disable the Event Monitor:
> /etc/init.d/tpssmmonitor stop |
On Linux systems, enter the following to disable the Event Monitor:
> /etc/rc.d/init.d/tpssmmonitor stop |
On IRIX systems, enter the following to enable the Event Monitor:
> /etc/init.d/tpssmmonitor start |
| Note: The Event Monitor will not be started if the tpssm monitor configuration file is set to off (see chkconfig(1M) for details). |
On Linux systems, enter the following to enable the Event Monitor:
> /etc/rc.d/init.d/tpssmmonitor start |
On IRIX systems, enter the following to disable boot-time loading of the Event Monitor:
> chkconfig tpssmmonitor off |
On Linux systems, enter the following to disable boot-time loading of the Event Monitor, where CDROM is the mount point of the CD-ROM drive:
> cp /CDROM/Linux/client/tpssmmonitor_symlink /opt/tpssm/client > /opt/tpssm/client/tpssmmonitor_symlink delete |
On IRIX systems, enter the following to enable boot-time loading of the Event Monitor:
> chkconfig tpssmmonitor on |
On Linux systems, enter the following to enable boot-time loading of the Event Monitor, where CDROM is the mount point of the CD-ROM drive:
> cp /CDROM/Linux/client/tpssmmonitor_symlink /opt/tpssm/client > /opt/tpssm/client/tpssmmonitor_symlink create |