If an Agent error (message ID = 3400) is output to /var/adm/messages during the setting or deletion of an access path, a definition file may not have been updated successfully. In this event, stop Agent, and take the following action:
As a user having root authority, enter the following command to stop Agent:
# /opt/FJSVssage/bin/pstorageagt
Execute the ps command as follows to confirm that Agent is stopped:
# /bin/ps -ef|grep FJSVssage
As necessary, save the following files to any directory:
/kernel/drv/sd.conf
/kernel/drv/fjpfca.conf
/kernel/drv/lpfc.conf
/kernel/drv/lpfs.conf
Restore the following definition files:
Restore the original file from the backup file that is stored in the backup file storage area (/var/opt//FJSVssage/backup).
Restart the server node.
Solaris 8, 9, 10 OS
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 After the server node is restarted, enter the following command: # disks -C
Other examples of major errors and the appropriate action to be taken are explained below.
Agent detects an environment error when a new HBA is added (except in cases where the HBA is a replacement).
The server node may not have been started in re-configuration mode after the addition of the HBA. In this event, restart the server node in re-configuration mode.
Agent detects an environment error when a new HBA driver is installed.
The server node may not have been started in re-configuration mode after installation of the driver. In this event, restart the server node in re-configuration mode.
