Command terminated normally.
Explanation
The command was executed successfully.
System action
The command is completed normally.
System administrator response
None
Since the selected LogicalVolume has already been set for another HBA, there is a possibility of data corruption when the system is not used for a multi path driver/ Cluster environment.
Explanation
An access path has already been set by another host bus adapter (HBA) for the area (LUN) of the GR series (storage) for which the access path is to be set. Therefore, the data via the relevant access path may be damaged by access from that host bus adapter, except when constructing a system that requires common area access setting in a SynfinityCLUSTER or another cluster (nodal failover) environment or multipath disk control (MPLB, MPHD) environment.
System action
The command is completed normally.
System administrator response
Because it is dangerous to set a relevant access path except when constructing a cluster or multipath control environment, cancel this setting. When constructing a cluster or multipath environment, check and set the access path carefully.
Unexpected condition detected for diagnostic access path.
Explanation
Access path diagnosis cannot be performed.
System action
Interrupt the access path diagnosis.
System administrator response
The access path cannot be diagnosed. Check the LAN connection with the server node to be diagnosed.
A path failure was detected.
Explanation
A path error was detected as a result of access path diagnosis.
System action
Interrupts the processing upon the detection of a path error during access path diagnosis
System administrator response
Check the connection of the physical fibre channel that forms the access path.
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Reboot the sever node in reconfigure mode.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, the host affinity was set for the storage.
To reconfigure the device special file on the server node, first restart the storage and, after it has restarted normally, reboot the target server node in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Restart the storage and then reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set on the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Reboot the server node in reconfigure mode. (This is necessary if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
A host affinity operation was performed for the storage. Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
The command terminated normally.
Explanation
The command was executed successfully.
System action
The command is completed normally.
System administrator response
None
Access path was defined normally for switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch to define the access path.
System action
The command is completed normally.
System administrator response
The target server node must be rebooted in reconfigure mode to enable the access path settings. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
For access path definition, HBA WWPN binding was set for the server node, /kernel/drv/sd.conf was set, and zoning was set for the switch.
System action
The command is completed normally.
System administrator response
The target server node must be rebooted in reconfigure mode to enable the access path settings. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
For access path definition, HBA WWPN binding was set for the server node, /kernel/drv/sd.conf was set, and zoning was set for the switch.
System action
The command is completed normally.
System administrator response
To enable the access path settings, restart the target storage and, after it has started normally, reboot the target server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
For access path definition, HBA WWPN binding was set for the server node, /kernel/drv/sd.conf was set, and zoning was set for the switch.
System action
The command is completed normally.
System administrator response
The target server node must be rebooted in reconfigure mode to enable the access path settings. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for switch and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
To define the access path, zoning was set for the switch and host affinity was set for the storage.
System action
The command is completed normally.
System administrator response
To enable the access path settings, restart the target storage and, after it has started normally, reboot the target server node in reconfigure mode. (This is necessary only if the server node does not
port the dynamic reconfiguration function.)
The access path setting was executed normally.
Explanation
Access path setting was performed normally.
System action
The command is completed normally.
System administrator response
None
New device(s) was/were detected.
Explanation
A new device was detected.
System action
The command is completed normally.
System administrator response
Register the device for management.
The selected IP device cannot be found.
Explanation
No new device could be detected at the specified IP address.
System action
The command is completed normally.
System administrator response
Check whether the specified IP address and network environment settings for the Managed device and the settings for detecting the Managed device are valid.
Refer to "Chapter 4 Environment Configuration" and "D.4.1 No detection of device is possible" in the ETERNUS SF Storage Cruiser User's Guide.
Some devices' access path was modified (XXXX_NAME). Reboot of some device are required to enable definition (REBOOT_XXXX_NAME). 'EDIT_HBA_NAME' means checking driver configuration file (sd.conf/st.conf/etc...) and editing by manual if necessary is required. :
XXXX_NAME="%name"
REBOOT_XXXX_NAME="%name"
EDIT_HBA_NAME=%name
Explanation
SAN configuration information (access path definition) for some devices was changed. For the server node, the HBA WWPN binding and /kernel/drv/sd.conf settings were changed. For the switch, the zoning settings were changed. For the storage, the host affinity settings were changed. The device is indicated by XXXX_NAME, where XXXX shows the device type such as HOST, SWITCH, or STORAGE.
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
The device may need to be restarted depending on the device type or the software or hardware status. In this case, the device is indicated by REBOOT_XXXX_NAME, where XXXX is the device type, such as HOST, SWITCH, or STORAGE.
Parameters
%name : Device name
System action
The command is completed normally.
System administrator response
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
Restart the device that needs to be restarted.
A problem occurred during this command operation affecting some devices. Some operation(s) failed or was/were skipped (ERR_XXXX_NAME/SKIP_XXXX_NAME). 'EDIT_HBA_NAME' means checking driver configuration file (sd.conf/st.conf/etc...) and editing by manual if necessary is required. :
ERR_XXXX_NAME="%name", "%msg"
SKIP_XXXX_NAME="%name", "%msg"
EDIT_HBA_NAME="%name"
Explanation
An attempt was made to change the SAN configuration information (access path definition) for some devices but it failed or was skipped for a certain device or devices.
If SAN configuration information (access path definition) could not be changed for a device, the device is indicated by ERR_XXXX_NAME, where XXXX shows the device type such as HOST, SWITCH, or STORAGE. The failure cause is also indicated.
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
If processing was skipped for a device, the device is indicated by SKIP_XXXX_NAME, where XXXX shows the device type such as HOST, SWITCH, or STORAGE.
Parameters
%name : Device name
%msg : Detail information (message)
System action
Partially completes the command
System administrator response
Check the error information and then re-enter the command.
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
(Re-execution may not be necessary depending on the command option. Change the SAN configuration information for each device directly (using Telnet or the Web server node function.). )
The access path for some devices was modified (XXXX_NAME). Reboot of some devices required to enable definition (REBOOT_XXXX_N AME). Also, a problem occurred during this operation. Some operation(s) failed or was/were skipped (ERR_XXXX_NAME/SKIP_XXXX_NAME). 'EDIT_HBA_NAME' means checking driver configuration file(sd.conf/st.conf/etc..) and editing by manual if necessary is required. :
XXXX_NAME="%name"
REBOOT_XXXX_NAME="%name"
ERR_XXXX_NAME="%name", "%msg"
SKIP_XXXX_NAME="%name", "%msg"
EDIT_HBA_NAME="%name"
Explanation
An attempt was made to change the SAN configuration information (access path definition) for multiple devices.
That device for which the SAN configuration information (access path definition) could be changed is indicated by XXXX_NAME, where XXXX is the device type such as HOST, SWITCH, or STORAGE. (For the server node, the HBA WWPN binding and /kernel/drv/sd.conf settings were changed. For the switch, the zoning settings were changed. For the storage, the host affinity settings were changed.) The device may need to be restarted depending on the device type or the software or hardware status. In this case, the device is indicated by REBOOT_XXXX_NAME.
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
If the SAN configuration information could not be changed for a device, the device is indicated by ERR_XXXX_NAME and the failure cause is also indicated. Any device for which processing was skipped is indicated by SKIP_XXXX_NAME.
Parameters
%name : Device name
%msg : Message code message
System action
Partially completes the command
System administrator response
Restart the device that needs to be restarted.
If the device definition files (sd.conf/st.conf etc.) are relevant to HBA of a server node and are checked and deemed it is a necessity, then it is necessary to edit.
Check the information for the device for which processing failed or was skipped, and then re-execute the processing.
(Re-execution may not be performed depending on the command option. Change the SAN configuration information for each device directly (using Telnet or the Web server node function). )
The selected IP device already exists in DB of administrative server.
Explanation
The device that responds to the specified IP address already exists in the database.
System action
The command is completed normally.
System administrator response
Check whether the entered IP address is valid.
Deleting the device terminated normally.
Explanation
The registered device was deleted successfully.
System action
The command was executed successfully.
System administrator response
None
Deleting the device terminated normally. During deleting the device, some processing of deleting access paths was done.
%detail_Information
Explanation
Registered devices were deleted. The access path subject to the deletion processing was processed.
Parameters
%detail_information : Detail information on the result of access path processing
System action
The command was executed successfully.
System administrator response
Follow the instructions given in the detail information. If necessary, save the detail information.
Deleting the device terminated. During deleting the device, some processing of deleting access paths was done. Some problems found.
%detail_Information
Explanation
Registered devices were deleted. The access path subject to deletion processing was processed. A problem was detected during the access path processing.
Parameters
%detail_information : Detail information on the result of access path processing
System action
Partially completes the command.
System administrator response
Follow the instructions given in the detail information. If necessary, save the detail information.
A new Fujitsu RAID device (Managed by GRSC) was detected.
Explanation
A new Fujitsu-manufactured RAID device was detected.
System action
The command was processed normally.
System administrator response
None
The selected IP Fujitsu RAID device cannot be found.
Explanation
A Fujitsu RAID device having the specified IP address could not be detected.
System action
The command was processed normally.
System administrator response
Check the IP address.
The selected IP Fujitsu RAID device (Managed by GRC) already exists in DB of administrative server.
Explanation
The Fujitsu RAID device having the specified IP address is already registered in the database.
System action
The command was processed normally.
System administrator response
Check the IP address.
Adding WWPN Zoning to the switch terminated normally. :
DONE_SWITCH_NAME="%name"
Explanation
WWPN Zoning has been set for the switch.
Parameters
%name : Switch name
System action
The command was processed normally.
System administrator response
None
Processing to switch is skipped. :
SKIP_SWITCH_NAME="%name"
Explanation
No processing was performed for the switch.
Parameters
%name : Switch name
System action
Interrupts the command processing.
System administrator response
For the skipped switch, check whether the device monitoring status is normal or check the firmware version, and then re-enter the command.
Adding WWPN Zoning to the switch terminated normally. Also processing to switch is skipped. :
DONE_SWITCH_NAME="%name"
SKIP_SWITCH_NAME="%name"
Explanation
The zone setting command was executed for one switch and processing was skipped for another.
Parameters
%name : Switch name
System action
Partially completes the command.
System administrator response
Check the error information and then re-enter the command.
For the skipped switch, check whether the device monitoring status is normal or check the firmware version, and then re-enter the command.
Deleting WWPN Zoning from the switch terminated normally. :
DONE_SWITCH_NAME="%name"
Explanation
The WWPN zoning setting has been deleted from the switch.
Parameters
%name : Switch name
System action
The command is completed normally.
System administrator response
None
Deleting WWPN Zoning from the switch terminated normally. Also processing to switch is skipped. :
DONE_SWITCH_NAME="%name"
SKIP_SWITCH_NAME="%name"
Explanation
The zone setting command was executed for one switch and processing was skipped for another.
Parameters
%name : Switch name
System action
Partially completes the command.
System administrator response
Check the error information and then re-enter the command.
For the skipped switch, check whether the device monitoring status is normal or check the firmware version, and then re-enter the command.
Some storage's access path was modified. Reboot of the storages are required to enable definition. :
REBOOT_STORAGE_NAME="%name"
Explanation
SAN configuration information for some storage devices was changed.
Parameters
%name : Storage name
System action
The command was executed successfully.
System administrator response
Restart the displayed storage.
A problem occurred during this command operation affecting some storages/switch. Some operation(s) failed or was/were skipped. :
SKIP_STORAGE_NAME="%name"
ERR_STORAGE_NAME="%name"
ERR_SWITCH_NAME="%name"
Explanation
A problem was detected during command processing for some storages or switches such that some devices were terminated abnormally, or processing for some devices was interrupted.
Parameters
%name : Device name
System action
Partially completes the command.
System administrator response
For the switch or storage for which processing was skipped or which was terminated abnormally, check whether the device status is normal. For the switch for which processing was skipped, also check the firmware version.
The access paths for same storages were modified. Reboot of the storages are required to enable definition. Also, a problem occurred during this operation. Some operation(s) failed or was/were skipped. :
REBOOT_STORAGE_NAME="%name"
SKIP_STORAGE_NAME="%name"
ERR_STORAGE_NAME="%name"
ERR_SWITCH_NAME="%name"
Explanation
A problem was detected during command processing for some storages or switches such that some devices were terminated abnormally, or processing for some devices was interrupted.
Parameters
%name : Device name
System action
Partially completes the command.
System administrator response
For the switch or storage for which processing was skipped or which was terminated abnormally, check whether the device status is normal. For the switch for which processing was skipped, also check the firmware version.
The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
None
(WWPN zoning can also be set for a switch to increase the security level of the entire SAN configuration. )
Skipped processing storage, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for storage that has the host affinity function.
(WWPN zoning can also be set for a switch to increase the security level of the entire SAN configuration. )
Skipped processing server node, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Skipped processing server node and Storage, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node (or FC-HBA adapter) and storage device (or FC-CA adapter) because the devices were set up using the manual embedding function.
Perform manual access path processing for the storage that has the host affinity function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Perform manual access path processing for storage that has a host affinity function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Please modify HBA and driver configuration file(sd.conf/st.conf/etc..) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Changing the access path definition for a combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After this setting has been made, the target server node must be rebooted in reconfigure mode (this is not necessary if the server node supports the dynamic reconfiguration function.).
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Skipped processing storage, cause it is a Manually Embedded Device. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped."
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After the server node access path definition has been changed, the target server node must be rebooted in reconfigure mode (the server node need not be rebooted if the server node supports the dynamic reconfiguration function.).
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Perform manual access path processing for the storage that has the host affinity function.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.) after the reboot of selected storage. Skipped processing server node, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function.
Perform manual access path processing for the server node that has a storage affinity function, such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. And after the reboot of selected storage, you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported.
Set the server node access path manually.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
None
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Skipped processing server node, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After this setting has been made, the target server node must be rebooted in reconfigure mode (this is not necessary if the server node supports the dynamic reconfiguration function.).
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted in reconfigure mode to reconfigure the server node special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
The server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage.
To reconfigure the device special file on the server node, first restart the storage and then, after it has restarted normally, reboot the target server node in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Restart the storage and then reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of the Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings. Then, the server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
Reboot the server node in reconfigure mode.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set for the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file on the server node. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
The command is completed normally.
System administrator response
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of the Fibre Channel HBA was edited. The appropriate driver configuration file (such as /kernel/drv/st.conf) must be edited manually first.
A host affinity operation was performed for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
None
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Skipped processing storage, cause it is a Manually Embedded Device. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition after the reboot of selected storage. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings and the server node must be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Ends the processing normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
None
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition. The switch is NO_SECURITY status. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted.
Zoning processing for a switch was skipped because the switch status was NO_SECURITY.
System action
Partially completes the command.
System administrator response
Reboot the server node.
(WWPN zoning can also be set for the switch to increase the security level of the entire SAN configuration.)
Processing to switch is skipped. Skipped Switch Name (SKIP_SWITCH_NAME):
SKIP_SWITCH_NAME="%name"
Explanation
No processing was performed for the switch.
Parameters
%name : Switch name
System action
Interrupts the command processing.
System administrator response
For the switch for which processing was skipped, also check the firmware version.
New device(s) was/were detected and added.
Explanation
A new device was detected and registered.
System action
Ends the processing normally.
System administrator response
None
New device(s) was/were detected and added. Reboot or SNMP Agent restart of the client server node machine is required to enable the problem-reporting function of client server node machine.
Explanation
A new device was detected and registered. To enable management of the error report settings for the server node, the server node must be rebooted or the SNMP agent in the server node must be restarted.
System action
Ends the processing normally.
System administrator response
Reboot the target server node, or restart the SNMP agent on the target server node.
An Internal Program inconsistency was detected.
Explanation
An internal fatal error was detected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A critical problem was found in DB of administrative server.
Explanation
Fatal inconsistent data was detected in the CIM database.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An inconsistency was detected in DB of administrative server.
Explanation
Inconsistent data was detected in the CIM database.
System action
Partially completes the command.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A CIM access error was detected.
Explanation
A CIM error was detected during CIM database access.
System action
Interrupts the processing.
System administrator response
One of the reasons for this message being output may be that the CIM data area is full (/var/sadm/wbem/logr).
Use the "df -k /var/sadm/wbem/logr" command to check whether the disk is full.
If the disk is not full, re-execute processing.
If re-executing the processing fails to solve this problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Input value is invalid. An Internal Program inconsistency was detected.
Explanation
An unexpected value was detected as an input parameter.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The input IP address or device name is incorrect.
Explanation
The format of the input IP address or device name is invalid.
System action
Interrupts the processing.
System administrator response
Check the format of the input IP address or device name.
The Input AffinityGroup was not found in the configuration of the Storage/Ca.
Explanation
An AffinityGroup name that was not defined for the storage device was specified.
System action
Interrupts the processing.
System administrator response
Check whether the AffinityGroup name defined for the storage device was specified correctly.
The input LUN(s) is/are not included in the configured Luns on Storage/CA.
Explanation
An LUN that was not defined for the storage device was specified.
System action
Interrupts the processing.
System administrator response
Check whether the LUN defined for the storage device was specified correctly.
The input Lun lists includes Lun DELETE requirement. Lun deleting is not supported function.
Explanation
LUN cannot be deleted directly.
System action
Interrupts the processing.
System administrator response
LUN can be deleted by deleting the corresponding LUN statement from the /kernel/drv/sd.conf file on the target server node.
An Internal Program Error occurred: The input Hba does not have the information on the last WWPN of the Hba.
Explanation
An internal error was detected in the program.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
TargetID cannot be changed.
Explanation
An existing target ID that was set in the server node during access path setting cannot be changed.
System action
Interrupts the processing.
System administrator response
To change the target ID, first delete the access path and then perform access path setting again using a new target ID.
TargetID is already being used.
Explanation
The same target ID as that used for an access path that was already set from the target host bus adapter (HBA) was specified for access path setting.
System action
Interrupts the processing.
System administrator response
Multiple access paths cannot be set with the same target ID from one HBA. Use another target ID.
The device observe status is not appropriate for the operation.
Explanation
The device monitoring status is inappropriate for command execution.
System action
Interrupts the processing.
System administrator response
If the device is not registered, first register the device and then re-enter the command.
If the device status is abnormal, restore the device to the normal status and then re-enter the command.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node is not appropriate for the operation.
Explanation
The server node device monitoring status is inappropriate for command execution.
System action
Interrupts the processing.
System administrator response
If the server node device is not registered, first register the device and then re-enter the command.
If the server node device status is abnormal, restore the device to the normal status and then re-enter the command.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA is not appropriate for the operation.
Explanation
The device monitoring status of the target HBA is inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Open to the property window of the target HBA from the side view of the Resource View, and check the monitoring status. According to the monitoring status, do the following:
When the status is "timeout"
The target HBA cannot be recognized. Check whether hardware and drivers function normally. Also check whether the SNIA HBA API library is installed normally. For installation, refer to "Appendix B SNIA HBA API library installation" in the ETERNUS SF Storage Cruiser Installation Guide.
When the status is "The access path must be inherited"
For details on the required action, refer to the "ETERNUS SF Storage Cruiser User's Guide", section "Operation" > "Access Path Management" > "Access path inheritance".
For details on access path settings, refer to the "ETERNUS SF Storage Cruiser User's Guide", section "Troubleshooting" > "Configuration management functionality" > "Access path setting has failed".
The device observe status of the server node and the HBA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node and HBA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node and HBA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the Storage is not appropriate for the operation.
Explanation
The device monitoring status of the target storage is inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target storage to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node and the Storage are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node and storage are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node and storage to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA and the Storage are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node and HBA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target HBA and storage to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, HBA and the Storage are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node and storage are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node, HBA, and storage to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the CA is not appropriate for the operation.
Explanation
The device monitoring status of the target CA is inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the HBA and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target HBA and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, HBA and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the server node, HBA, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node, HBA, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the Storage and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target storage and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target storage and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, Storage and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node, storage, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node, storage, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA,Storage and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target HBA, storage, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the HBA, storage, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, HBA,Storage and the CA are not appropriate for the operation.
Explanation
The device monitoring statuses of the target server node, HBA, storage, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Restore the target server node, HBA, storage, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The storage affinity of one HBA is WWNN_BINDING, It is not appropriate for adding to the server node.
Explanation
WWNN (World Wide Node Name) binding is defined for the server node HBA. Because the management unit of this program is WWPN (World Wide Port Name), registration of the relevant server node is restricted.
System action
Interrupts the processing.
System administrator response
Define WWPN binding instead of WWNN binding for the HBA of the server node to be registered, and then perform server node registration again.
The storage affinity of one HBA is PID_BINDING. It is not appropriate for adding to the server node.
Explanation
PID (Fibre Channel PID) binding is defined for the server node HBA. Because the management unit of this program is WWPN (World Wide Port Name), registration of the relevant server node is restricted.
System action
Interrupts the processing.
System administrator response
Define WWPN binding instead of PID binding for the HBA of the server node to be registered, and then perform server node registration again.
The storage affinity of one HBA is TID_BINDING. It is not appropriate for adding to the server node.
Explanation
PID (Fibre Channel TID) binding is defined for the server node HBA. Because the management unit of this program is WWPN (World Wide Port Name), registration of the relevant server node is restricted.
System action
Interrupts the processing.
System administrator response
Define WWPN binding instead of TID binding for the HBA of the server node to be registered, and then perform server node registration again.
The zoning configuration of the switch is WWNNZoning. It is not appropriate for adding to switch.
Explanation
The switch zoning definition includes WWNN.
System action
Interrupts the processing.
System administrator response
Use WWPN for the switch zoning definition to implement correct zoning management.
The switch is connected to a device which is not confirmed whether it is CA or HBA.
Explanation
An adapter, which cannot be recognized as either CA or HBA, is connected to the switch.
System action
Interrupts the processing.
System administrator response
Register CA and HBA information.
Communication with the device could not be executed.
Explanation
The state of device subject to command processing is such that it cannot be detected on the LAN.
System action
Interrupts the processing.
System administrator response
Check the LAN connection of the target device.
No device could be found that was being managed by administrative server for the IP address.
Explanation
An attempt to find the monitored device with the specified IP address failed.
System action
Interrupts the processing.
System administrator response
Check whether the specified IP address is valid.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the administrative server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the administrative server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
For the server, check the network environment and Agent activation.
Also check whether the settings required for device detection have been made. For details of the settings, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
To execute this operation, the Port Type of HBA must be 'N' port.
Explanation
This operation cannot be performed because the HBA FC port type is not set to N.
System action
Interrupts the processing.
System administrator response
Set the HBA FC port type to N. Refer to the manual for information on how to set the port to N.
The Fibre Channel cable is not physically connected.
Explanation
The Fibre Channel cable for the path between the operation target HBA and CA is broken.
System action
Interrupts the processing.
System administrator response
Execute "Refresh" in the resource view, determine where the Fibre Channel cable between the HBA and CA is broken, and then physically re-connect the cable.
If information cannot be obtained from the Fibre Channel cable refer to "D.4.3 Device is not possible to communicate" in the ETERNUS SF Storage Cruiser User's Guide.
There is a critical problem with the FC Port type of HBA, CA or Switch.
Explanation
HBA or CA is not set for the N-type port, or the switch is not set for the F-type port.
System action
Interrupts the processing.
System administrator response
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For details of the settings, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
If re-executing the processing displays the same message, it is assumed that the switch port cannot be set to F type for some reasons.
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
There is a problem with the FC port type of HBA/CA (1).
Explanation
The HBA and CA ports were not set to N type.
System action
Interrupts the processing.
System administrator response
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For setting procedures, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
There is a problem with the FC port type of HBA/CA (2).
Explanation
The HBA and CA ports were not set to N type.
System action
Interrupts the processing.
System administrator response
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For setting procedures, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
The connection route and setup for connection between HBA and CA is not appropriate for setAccessPath().
Explanation
The specified connection route/combination between the HBA and CA is not supported.
System action
Interrupts the processing.
System administrator response
Refer to the manual to determine which connection route/combinations are supported.
A fatal error occurred during the server node operation.
Explanation
An error was detected during command processing for the server node.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
A fatal error occurred during the server node operation. Please call our engineer.(Do not run this operation again.)
Explanation
A fatal error occurred during command execution for the server node.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A fatal error occurred during the storage operation.
Explanation
An error was detected during command processing for the storage.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Server node configuration has already been updated.
Explanation
An error was detected during the execution of this command for the storage. The server node configuration information has been changed from the state existing before the execution of this command.
System action
Setting for the server node was executed but other processing was interrupted.
System administrator response
Re-enter the command.
Fatal error occurred during storage operation and server node error recovery failed. Server node configuration has already been updated.
Explanation
An error was detected during execution of this operation command for the storage.
System action
Setting for the server node was executed but other processing was interrupted.
System administrator response
Re-enter the command.
Fatal error occurred during storage operation and server node error recovery failed. Please call our engineer.(Do not run this operation again.)
Explanation
An error was detected during the execution of this operation command for the storage.
Also, a fatal error was detected in the server node operation.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during storage operation. Please call our engineer.(Do not run this operation again.)
Explanation
An error was detected during the execution of this operation command for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during storage operation. Please call our engineer.(Do not run this operation again.) Server node configuration has already been updated.
Explanation
The command was executed for the server node but a fatal error was detected during command execution for the storage.
System action
Setting on the server node was executed but processing for the storage was interrupted.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during storage operation and server node error recovery failed. Server node configuration has already been updated. Please call our engineer.(Do not run this operation again.)
Explanation
A serious error was detected during the execution of this command for the storage. An error was detected during the execution of ERP processing for the server node. The server node configuration information has been changed from the state existing before the execution of this command.
System action
Setting for the server node was executed but processing for the storage was interrupted.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during storage operation and server node error recovery failed. Please call our engineer.(Do not run this operation again.)
Explanation
A serious error was detected during the execution of this command for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation.
Explanation
An error was detected during the execution of this operation on the switch.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Server node configuration has already been updated.
Explanation
An error was detected during the execution of this command for the switch.
The command was executed successfully for the server node.
System action
Executes the setting on the server node but interrupts the processing on the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Server node error recovery failed and server node configuration was updated.
Explanation
An error was detected during the execution of this command for the switch.
The command was executed successfully for the server node.
System action
Setting for the server node was executed but processing for the switch was interrupted.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation and server node error recovery failed. Please call our engineer. (Do not run this operation again.)
Explanation
A serious error was detected during the execution of this command for the storage.
The command was executed for the server node.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Server node configuration has already been updated.
Explanation
An error was detected during the execution of this command for the switch.
The command was executed successfully for the server node.
System action
Executes the processing for the server node but interrupts that for the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation and server node error recovery failed. Server node configuration was updated.
Explanation
An error was detected during the execution of this operation for the switch.
The operation was executed successfully for the server node.
System action
Executes the processing on the server node but interrupts that on the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation and server node error recovery failed. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation for the switch.
Also, a fatal error was detected during the execution of this operation for the server node.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Storage recovery procedure failed and storage configuration was updated.
Explanation
An error was detected during the execution of this operation for the switch.
This operation was executed successfully for the storage.
System action
Executes the processing for the storage but interrupts that for the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Storage recovery procedure failed and storage configuration was updated.
Explanation
An error was detected during the execution of this operation for the switch.
This operation was executed for the storage.
System action
Executes the processing for the storage but interrupts that for the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Storage recovery procedure failed and storage and server node configuration was updated.
Explanation
An error was detected during the execution of this operation for the switch.
This operation was executed successfully for the storage and server node.
System action
Executes the processing for the storage and server node but interrupts that for the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Storage and server node recovery procedure failed and storage and server node configuration was updated.
Explanation
An error was detected during the execution of this operation for the switch.
This operation was executed successfully for the storage and server node.
System action
Executes the processing for the storage and server node but interrupts that for the switch.
System administrator response
Re-enter the command.
Fatal error occurred during switch operation. Storage and server node recovery procedure failed and storage configuration was updated. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation for the switch.
Also, a fatal error was detected during the execution of this operation for the server node.
This operation was executed successfully for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Storage recovery procedure failed. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation for the switch.
Also, a fatal error was detected during the execution of this operation for the server node.
This operation was executed successfully for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Storage recovery procedure failed. Server node configuration was updated. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation for the switch.
Also, a fatal error was detected during the execution of this operation for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Storage and server node recovery procedure failed. Server node configuration was updated. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation on the switch.
Also, a fatal error was detected during the execution of this operation for the storage.
This operation was executed successfully for the server node.
System action
Executes this operation for the server node but interrupts all other processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Fatal error occurred during switch operation. Storage and server node recovery procedure failed. Please call our engineer. (Do not run this operation again.)
Explanation
An error was detected during the execution of this operation for the switch.
Also, a fatal error was detected during the execution of this operation for the server node.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unable to obtain Storage Affinity Information. This operation could not be processed.
Explanation
Storage Affinity Information from the HBA could not be obtained.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Server node agent is already communicating with another manager.
Explanation
The Agent of the target server node is busy communicating with another administrative server.
System action
Interrupts the processing.
System administrator response
Re-execute the processing later.
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unexpected Exception occurred
Explanation
Unexpected exception processing was detected during a management operation.
This message may be output as a result of one of the following reasons:
The target server node failed while it was processing a request issued by the Manager, or communication failed because of a LAN error.
The Agent on the relevant server node is stopped.
Exception processing other than the above was detected in the program. An unexpected exception occurred.
System action
Interrupts the processing.
System administrator response
If the relevant server node failed or a LAN error occurred during communication with the relevant server, remove the cause of the error.
If the Agent is stopped, start it.
When none of the above items apply,
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
SNMP error occurred in communication with server node.
Explanation
An SNMP error occurred during communication with the server node.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
Socket error occurred in communication with server node.
Explanation
A SOCKET error occurred during communication with the Agent. A possible cause is that the resources (memory and process tables) of the server node on which the Manager is running have been exhausted. A socket error occurred during communication with the server node.
System action
Interrupts the processing.
System administrator response
Check whether any application that causes a server node resource shortage is running. Also check whether there is an application that generates processes in succession. If resource shortages tend to occur frequently, expand the amount of installed memory.
Unable to find selected server node.
Explanation
The IP address of the server node on which the Manager is running could not be determined.
System action
Interrupts the processing.
System administrator response
Review the definition of the address of the server node on which the Manager is running.
Check whether the system resources, such as process tables and memory, have been exhausted.
Check the LAN for errors.
When none of the above items apply, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
No response from server node agent.
Explanation
This message may be output as a result of any one of the following:
The server node to which a processing request was issued by the Manager failed, or communication failed because of a LAN error.
The Agent on the relevant server node has stopped.
System action
Interrupts the processing.
System administrator response
If the relevant server failed or a LAN error occurred during communication with the relevant server, remove the failure cause.
When none of the above items apply, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Socket error occurred in switch/hub communication. The target device address: %IP_ADDRESS
Explanation
A socket error occurred during communication between the Manager and the switch or hub.
Parameters
%IP_ADDRESS : Indicates the IP address of the destination switch or hub on which the error occurred.
System action
Interrupts the processing.
System administrator response
Check whether the target switch or hub is connected to the LAN. Alternatively, check the LAN environment for problems.
Unable to find selected switch/hub. The target device address: %IP_ADDRESS
Explanation
The specified switch or hub was not found.
Parameters
%IP_ADDRESS : Indicates the IP address of the specified switch or hub.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Network I/O error occurred in switch/hub communication. The target device address: %IP_ADDRESS
Explanation
A network I/O error occurred during communication between the Manager and the switch or hub.
Parameters
%IP_ADDRESS : Indicates the IP address of the destination switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Check the applicable switch or hub for errors. Alternatively, check the LAN environment for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Timeout error occurred in switch/hub communication. The target device address: %IP_ADDRESS
Explanation
A time-out was detected during communication between the Manager and the switch or hub.
Parameters
%IP_ADDRESS : Indicates the IP address of the destination switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Check whether the target switch or hub is connected to the LAN. Alternatively, check the LAN environment for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
No response from switch/hub. The target device address: %IP_ADDRESS
Explanation
The specified switch or hub was not found.
Parameters
%IP_ADDRESS : Indicates the IP address of the specified switch or hub.
System action
Interrupts the processing.
System administrator response
Check whether the target switch or hub is connected to the LAN. Alternatively, check the LAN environment for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
This device is not supported. The target device address: %IP_ADDRESS
Explanation
The device with the specified IP address is not to be managed.
Parameters
%IP_ADDRESS : Indicates the IP address of the specified switch or hub.
System action
Interrupts the processing.
System administrator response
Check whether the specified IP address is valid.
User Name or Password is incorrect for switch/hub. The target device address: %SYS_NAME:%IP_ADDRESS
Explanation
Login to the switch or hub failed because the user name or password was invalid.
Parameters
%SYS_NAME : Indicates sysName that is set for the switch or hub to which login failed.
%IP_ADDRESS : Indicates the IP address of the switch or hub to which login failed.
System action
Interrupts the processing.
System administrator response
If this message was displayed during device registration, re-execute the processing and enter a valid user name and password.
If this message is displayed on a device that has already been registered, first determine the relevant device from "Detail" and then turn off the device power. Select "Refresh" and then "Delete device". Then, select "Equipment registration" again and enter a valid user name and password.
Another user has logged into switch/hub. Logout and run function again. The target device address: %SYS_NAME:%IP_ADDRESS
Explanation
The Manager could not login to the switch or hub because another user has already logged into the device.
Parameters
%SYS_NAME : Indicates sysName that is set for the switch or hub to which login failed.
%IP_ADDRESS : Indicates the IP address of the switch or hub to which login failed.
System action
Interrupts the processing.
System administrator response
Log out the process logged into the target device, and then re-execute.
If the target device is unknown, determine it from "Detail".
Parse error on telnet for switch/hub. The target device address: %SYS_NAME:%IP_ADDRESS
Explanation
Analysis of the execution results of the TELNET command issued to the switch or hub failed.
Parameters
%SYS_NAME : Indicates sysName that is set for the switch or hub to which login failed.
%IP_ADDRESS : Indicates the IP address of the switch or hub to which login failed.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Command failure on telnet for switch/hub. The target device address: %IP_ADDRESS
Explanation
Execution of the TELNET command issued to the switch or hub failed.
Parameters
%IP_ADDRESS : Indicates the IP address of the switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Re-enter the command. If execution still fails, the following are possible causes.
Check if all the cascade-connected fibre channel switches are registered to this software.
If not so, register all the switches.
Make sure that the icon statuses of all the cascade-connected fibre channel switches are normal (green). If they are not, then check the status of devices. For details on how to do that, refer to the " ETERNUS SF Storage Cruiser User's Guide", section "Operation" > "Resource View" > "Main view", table "Device status indications".
If the above are not applicable, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Index out of bounds. The target device address: %IP_ADDRESS
Explanation
An attempt was made to access an address outside of the range of the Manager's internal buffer.
Parameters
%IP_ADDRESS : Indicates the IP address of the switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
This is not supported device. : %IP_ADDRESS
Explanation
The device with the specified IP address is not to be managed for errors.
Parameters
%IP_ADDRESS : IP address of the device not to be managed
System action
Interrupts the processing.
System administrator response
Check the devices to be managed.
Unrecovered SNMP error occurred. The target device address:%IP_ADDRESS
Explanation
An unrecoverable error occurred during processing of the SNMP protocol.
Parameters
%IP_ADDRESS : Indicates the IP address of the switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Administrative server using zone name is already registered in this switch. Registered zoning name: %TYPE:%NAME (IP:%IP_ADDRESS)
Explanation
The zoning name used by the Manager is already registered as Zone or Alias for a switch.
Parameters
%TYPE : Zoning type (Zone or Alias) of the name that is already used
%NAME : Name that is already used
%IP_ADDRESS : Indicates the IP address of the switch in which an error occurred.
System action
Interrupts the processing.
System administrator response
To set zoning manually, use a name beginning with other than "SNM".
Too many zones for switch. The target device address:%IP_ADDRESS
Explanation
The zone setting limit has been reached.
Parameters
%IP_ADDRESS : Indicates the IP address of the switch in which an error occurred.
System action
Interrupts the processing.
System administrator response
Delete any unnecessary zone settings. If there are no unnecessary zone settings that can be deleted, configure another SAN.
Unable to delete zone for switch. This is because of port zoning possibly due to zone setting not being one-to-one. Zone setting: %ZONES (IP:%IP_ADDRESS)
Explanation
The Manager can delete only one-to-one correspondent WWPN (World Wide Port Name) zone settings.
Parameters
%ZONES : Indicates the zone setting that could not be deleted.
%IP_ADDRESS : Indicates the IP address of the switch in which an error occurred.
System action
Interrupts the processing.
System administrator response
Login directly to the switch and then adjust the zone setting manually.
Firmware version switch/hub not supported. Firmware Version: %VERSION (IP:%IP_ADDRESS)
Explanation
The switch or hub is of an unsupported firmware version.
Parameters
%VERSION : Unsupported firmware version
%IP_ADDRESS : Indicates the IP address of the switch or hub in which an error occurred.
System action
Interrupts the processing.
System administrator response
Firmware not supported ETERNUS SF Storage Cruiser is used for the target device.
Contact your Fujitsu engineer (CE or SE) because patches need to be applied to ETERNUS SF Storage Cruiser.
Registration of SNMP Trap address is full on switch/hub. Failed Registration: %REGISTRATION (IP:%IP_ADDRESS)
Explanation
No more switch or hub SNMP trap send destinations can be registered because the registry is full.
Parameters
%REGISTRATION : Indicates the IP address of the SNMP trap send destination that could not be registered
%IP_ADDRESS : Indicates the IP address of the switch or hub in which the error occurred.
System action
Interrupts the processing.
System administrator response
Login to the switch or hub directly and delete any unnecessary SNMP trap send destinations.
Device-specific class loading error. The target device address: %IP_ADDRESS
Explanation
The device-specific class could not be loaded.
Parameters
%IP_ADDRESS : Indicates the IP address of the device to be processed.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unexpected Interrupt occurred during processing. The target device address: %IP_ADDRESS
Explanation
An interrupt occurred during processing.
Parameters
%IP_ADDRESS : Indicates the IP address of the device to be processed.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unexpected error occurred. %IP_ADDRESS
Explanation
An unexpected error occurred.
Parameters
%IP_ADDRESS : Indicates the IP address of the device to be processed.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error occurred.
Explanation
An internal program error was detected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
SNMP error occurred on storage communication.
Explanation
An SNMP error occurred during communication between the storage and server.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
When the target device is an ETERNUS disk array, the following environment settings may not be correct. For details, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
The network environment settings in the disk array (Check whether the network settings for communication with the Manager have been made.)
SNMP agent environment settings in the disk array
In some cases, the community name of a device such as an ETERNUS disk array, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the admin server may not be changed.
If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
Socket error occurred on storage communication.
Explanation
A socket error occurred during communication between the storage and server.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
Selected storage is not found.
Explanation
The specified storage is not found.
System action
Interrupts the processing.
System administrator response
Check whether the specified storage is connected to the LAN.
When the target device is an ETERNUS disk array, the following environment settings may not be correct. For details, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
The network environment settings in the disk array (Check whether the network settings for communication with the Manager have been made.)
SNMP agent environment settings in the disk array
In some cases, the community name of a device such as an ETERNUS disk array, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
Network I/O Error on storage communication.
Explanation
An I/O error occurred during communication with the storage.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
Timeout Error on storage communication.
Explanation
A time-out occurred during communication with the storage.
System action
Interrupts the processing.
System administrator response
Check the LAN environment for problems.
Poor and slow communications can cause a timeout when one communication mode is set to "Auto Negoiation" and the other is set to "Full (all dual)".
No response from storage.
Explanation
A required storage was not found.
System action
Interrupts the processing.
System administrator response
Check whether the specified storage is connected to the LAN.
When the target device is an ETERNUS disk array, the following environment settings may not be correct. For details, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
The network environment settings in the disk array (Check whether the network settings for communication with the Manager have been made.)
SNMP agent environment settings in the disk array
In some cases, the community name of a device such as an ETERNUS disk array, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
This device is not supported.
Explanation
Management of the specified IP device is not supported.
System action
Interrupts the processing.
System administrator response
Check whether the specified IP device is valid.
User ID for storage is incorrect.
Explanation
An attempt to login to the storage failed because the user ID was invalid.
System action
Interrupts the processing.
System administrator response
If this message is displayed for device registration, re-execute the processing and then enter a valid user ID.
If this message is displayed for a device that has already been registered, determine the relevant device from "Detail" and then turn off the device power. Select "Refresh" and then "Delete device". Then, execute "Equipment registration" again and enter a valid user ID and password.
Password for storage is incorrect.
Explanation
An attempt to login to the storage failed because the entered password was invalid.
System action
Interrupts the processing.
System administrator response
If this message is displayed for device registration, re-execute the processing and then enter a valid password.
If this message is displayed for a device that has already been registered, determine the relevant device from "Detail" and then turn off the device power. Select "Refresh" and then "Delete device". Then, execute "Equipment registration" again and then enter a valid password.
Another user is logged into the storage. Logout and run function again. login IP: %IP_ADDRESS
Explanation
The command issued from the Manager cannot be executed because another user has already logged into the storage.
Parameters
%IP_ADDRESS : Login source IP address. (For the GR720/GR730, the login user name is displayed after IP_ADDRESS. This may not be displayed depending on the type of the storage device.)
System action
Interrupts the processing.
System administrator response
Logout the process logged into the target device, and then re-execute it. If the user fails to explicitly log out from ETERNUSmgr/GRmgr after login, such as when the user terminates the Web server while logging into ETERNUSmgr/GRmgr, ETERNUSmgr/GRmgr remains logged in. In this case, login to ETERNUSmgr/GRmgr again and forcibly logout the invalid login process.
User lacks storage-setting authority.
Explanation
The user is not authorized to make settings for the storage.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
No root password is registered in storage.
Explanation
The root password is not set in the storage.
System action
Interrupts the processing.
System administrator response
Set the root password in the storage.
CGI access error occurred in storage communication.
Explanation
An error occurred during CGI access to the storage.
System action
Interrupts the processing.
System administrator response
Check the LAN status.
CGI internal command error occurred in storage communication.
Explanation
An error occurred during send of the CGI command to the storage.
System action
Interrupts the processing.
System administrator response
Check the LAN status.
Internal Program Error: (Added HBA WWPN for a HBA of Security MODE off)
Explanation
An internal program error was detected. (An attempt was made to register HBA WWPN in the CA for which the security function is invalid.)
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error: (Tried defining indefinable host affinity for storage)
Explanation
An internal program error was detected. (An attempt was made to set an access path for the storage for which AffinityGroup setting is disabled.)
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error: (No Affinity Group setting for device run with affinity group function.)
Explanation
An internal program error was detected. (An affinity group was not set for the device on which the affinity function is active.)
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
CA has another affinity group definition for selected HBA.
Explanation
The CA selected for access path setting already has another affinity group definition for the relevant HBA.
Only one affinity group can be defined from one HBA.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Selected affinity group not defined in storage
Explanation
The storage affinity group specified for access path setting is not defined in the storage device.
System action
Interrupts the processing.
System administrator response
Check whether a correct affinity group has been selected.
Internal Program Error: (Different Affinity Group selected)
Explanation
An internal program error was detected. (The zone assigned to the HBA to be deleted differs from the specified zone.)
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Internal Program Error: (Invalid CA Logical ID)
Explanation
An internal program error was detected. (An invalid CA ID was specified. )
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Registration of Host affinity HBA WWPN is full on storage CA.
Explanation
No more host affinity HBAs can be registered for the storage CA specified for access path setting because the registry is full.
System action
Interrupts the processing.
System administrator response
Delete any unnecessary access paths for the specified CA, or expand the size of the storage CA.
Registration of SNMP Trap address is full on storage.
Explanation
Another IP address cannot be set for the SNMP trap send destination on the storage side because the number of the registered IP addresses has reached the maximum.
System action
Interrupts the processing.
System administrator response
Delete any unnecessary SNMP trap send destination IP addresses from those defined in the storage. Use the appropriate storage tool to delete them.
Registration of SNMP Trap address area is full on storage.
Explanation
The SNMP trap setting area in the storage is full and no additional registration is permitted.
System action
Interrupts the processing.
System administrator response
Delete any unnecessary SNMP trap send destination IP addresses from those defined in the storage. Use the proper tool to delete them from storage.
CGI processing failed in storage communication. (Some storage settings made.)
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage has not been changed.
System administrator response
Re-enter the command.
CGI processing failed in storage communication. (Some storage settings made.)
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage is unclear.
System administrator response
Re-enter the command.
CGI processing failed in storage communication. (Some storage settings made.)
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage has been partially changed.
System administrator response
Re-enter the command.
Incorrect Storage Configuration.
Explanation
A storage internal configuration information error was detected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Selected path is using by other application
Explanation
The diagnostic path is being used (open) by another application.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Administrative server detected error for selected path
Explanation
An error occurred during diagnosis of the selected path.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Manager cannot diagnose access path
Explanation
Path diagnosis cannot be executed.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Path error detected on server node.
Explanation
The Agent detected a path error.
System action
Interrupts the processing.
System administrator response
Re-enter the command.
Server node environment error detected. detail: [s1]
Explanation
An environment error was detected on the administrative server.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
Invalid information on server node. detail: [s1]
Explanation
Invalid information was detected on the administrative server.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
Invalid parameter at SNMP command is detected on server node. detail: [s1]
Explanation
An invalid value was detected during communication with the administrative server.
The operator made a specification mistake, or the LAN environment may have a problem.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
Invalid operation server node. detail: [s1]
Explanation
The Agent detected an operation error.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
System error occurred on server node. detail: [s1]
Explanation
A system error was detected.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
Internal Program Error occurred on server node.
Explanation
The Agent detected a program internal error.
System action
Interrupts the processing.
System administrator response
If the command for changing the IP address of SNMP Trap destination (sanadmsh chtraprcvip) is executed, check the argument and re-execute the command.
If the problem is not solved or other cases, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Failed to update definition file. detail: [s1]
Explanation
The Agent failed to update the server node device and Fibre Channel environment definition files.
Parameters
s1 : Detail message output by the Agent
System action
Interrupts the processing.
System administrator response
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to "Chapter 2 Agent Messages".
Internal Program error occurred.
Explanation
An internal program error was detected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Timeout occurred to startup of snmp trap handler thread.
Explanation
A thread start time-out occurred when the SNMP trap handler was started.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
unable to find SNMP library.
Explanation
A library required for the SNMP trap handler was not detected.
System action
Interrupts the processing.
System administrator response
The SNMP library may not be installed normally. Check whether the library has been installed normally.
Unable to update zoning configuration, because current zoning configuration is inconsistent. The zoning configuration:
Explanation
The current zoning setting could not be updated because the current zoning setting contained an error.
System action
Interrupts the processing.
System administrator response
Check the zoning setting, and then re-execute.
Not supported switch/hub. The target device address: %IP_ADDRESS
Explanation
The relevant switch or hub is not supported.
Parameters
%IP_ADDRESS : Indicates the IP address of the device to be processed.
System action
Interrupts the processing.
System administrator response
Check whether the device with the relevant IP address is supported by this software. Also, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
The device does not support Beacon function,
Explanation
The specified device does not support the beacon function.
System action
None
System administrator response
None
The instance is already in DB of SANmgr.
Explanation
The specified device or instance already exists in the database.
System action
None
System administrator response
Check the device status or selection again.
The association of same kind device is already in DB of administrative server.
Explanation
The association for the same device type already exists in the database. For instance, HBA can have a physical line only with a single hub.
System action
Interrupts the processing.
System administrator response
Check the device status or selection again.
More than one device has a same IP address.
Explanation
Two or more devices have the same IP address.
System action
Interrupts the processing.
System administrator response
Check the IP address of each device.
More than one HBA/Storage FC Port has a same WWPN.
Explanation
Two or more HBA/Storage FC Ports have the same WWPN.
System action
Interrupts the processing.
System administrator response
Check the environment. Particularly, confirm the following.
Pay careful attention to the Agent configuration file in the Windows operating system. Some values may present a problem.
Turn back WWPN to before it changes, when the WWPN of Storage FC Port is changed by using the storage migration function.
When this message is output during detects the device in the subnet, there is a possibility that IP address on the Slave CM side is set with ETERNUS. Please correspond either as follows when IP address on the Slave CM side is set with ETERNUS.
Please execute "Detect device in subnet" again after invalidating IP address on the Slave CM side.
Please put into the state that the communication between the administrative server and Slave CM cannot be done, and execute "Detect device in subnet" again.
Do not perform "Detect device in subnet", please detect devices by "Detect by IP address".
The specified device is Manually Embedded Device.
Explanation
The specified device was set up using the manual embedding function.
This operation cannot be applied to a device that was set up using the manual embedding function.
System action
None
System administrator response
None
An Internal Program Error occurred: The specified device is Manually Embedded Device.
Explanation
An internal program error was detected. (The specified device was set up using the manual embedding function.)
This operation cannot be applied to a device that was set up using the manual embedding function.
System action
Interrupts the processing.
System administrator response
None
The specified device is not Manually Embedded Device.
Explanation
The specified device was not set up using the manual embedding function.
This operation cannot be applied to a device that was set up using the manual embedding function.
System action
Interrupts the processing.
System administrator response
None
An Internal Program Error occurred: The specified device is not Manually Embedded Device.
Explanation
An internal program error was detected. (The specified device was not set up using the manual embedding function.)
System action
Interrupts the processing.
System administrator response
None
An Internal Program Error occurred: The logical number of inputted HBA is null.
Explanation
An internal program error was detected. (The specified HBA logical number is invalid.)
System action
Interrupts the processing.
System administrator response
None
The cascaded hub group which the inputted Hub included already has one association to Switch.
Explanation
The FC rules permit only one Fibre Channel cable to be connected from a group of hubs that are cascaded with Fibre Channel cables to the switch. (Normally, only a single connection is permitted.)
System action
None
System administrator response
None
The specified FC Port type is not FC-AL.
Explanation
The type of the FC port specified for connection is not FC-AL. The FC port type must be FC-AL for connection between the hub and physical line.
System action
None
System administrator response
Check the FC port type.
Set the HBA and CA Fibre Channel port connection types to Loop connection (FC-AL type port). For information on how to set the ports, refer to the respective HBA driver manuals and the manuals for individual devices.
The kind of specified FC-Adaptor is changed. Need try again.
Explanation
The FC adapter type (HBA or CA) has been changed. Re-enter the command.
System action
None
System administrator response
Re-enter the command.
An Internal Program Error occurred: Bad combination for Manager association.
Explanation
An internal program error was detected. (An invalid device combination was specified.)
System action
Interrupts the processing.
System administrator response
Check the device combination.
An Internal Program Error occurred: Bad combination for administrative server association.
Explanation
An internal program error was detected. (An invalid device combination was specified.)
System action
Interrupts the processing.
System administrator response
Check the device combination.
An Internal Program Error occurred: Specified devices are same.
Explanation
An internal program error was detected. (An association cannot be set up between the same devices.)
System action
Interrupts the processing.
System administrator response
None
An Internal Program Error occurred: Specified devices are same.
Explanation
An internal program error was detected. (An association cannot be set up between the same devices.)
System action
Interrupts the processing.
System administrator response
None
The device observe status of the Bridge is not appropriate for the operation.
Explanation
The device monitoring status of the bridge is inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node and the Bridge is not appropriate for the operation.
Explanation
The device monitoring statuses of the server node and bridge are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA and the Bridge is not appropriate for the operation.
Explanation
The device monitoring statuses of the HBA and bridge are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, HBA and the Bridge is not appropriate for the operation.
Explanation
The device monitoring statuses of the server node, HBA, and bridge are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the Bridge and the CA is not appropriate for the operation.
Explanation
The device monitoring statuses of the bridge and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, Bridge and the CA is not appropriate for the operation.
Explanation
The device monitoring statuses of the server node, bridge, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the HBA, Bridge and the CA is not appropriate for the operation.
Explanation
The device monitoring statuses of the HBA, bridge, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The device observe status of the server node, HBA, Bridge and the CA is not appropriate for the operation.
Explanation
The device monitoring statuses of the server node, HBA, bridge, and CA are inappropriate for executing the specified operation.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status is normal, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
Could not find any accessible switch.
Explanation
No enabled switch is found. Check the device monitoring status.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status of the switch is normal and that the model name and the firmware version number are correct, and then re-execute the processing.
Could not find any accessible switch.
Explanation
No enabled switch is found. Check the device monitoring status.
System action
Interrupts the processing.
System administrator response
Make sure that the device monitoring status of the switch is normal and that the model name and the firmware version number are correct, and then re-execute the processing.
For access path settings, refer to "D.4.7 Access path setting has failed" in the ETERNUS SF Storage Cruiser User's Guide.
The FC Adaptor has some access-path(s), could not delete the device which has access-path.
Explanation
Device deletion cannot be continued because the FC adapter holds an access path.
System action
Interrupts the processing.
System administrator response
Delete the access path associated with the FC adapter, and then re-execute the processing.
Deleting the device finished. But stopping SNMP Trap function to administrative server failed.
Explanation
Device deletion has been executed. Send of the SNMP trap to the administrative server could not be stopped.
System action
None
System administrator response
If necessary, cancel the SNMP Trap send setting that has been manually specified for the device.
Internal Program Error occurred (The input value is not appropriate), or the device was already deleted by another Management Window.
Explanation
The specified device has already been deleted from another management screen, or a program internal error (abnormal input value) may have occurred.
System action
Interrupts the processing.
System administrator response
Check whether multiple clients were used and "Delete device" was executed from another client. Also, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
CGI access error occurred in storage communication. Please check that ETERNUSmgr or GRmgr or GR Service Console is working surely.
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage is unclear.
System administrator response
Re-enter the command.
Agent version is incorrect.
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage is unclear.
System administrator response
Re-enter the command.
HBA type is incorrect.
Explanation
An error occurred during CGI processing from the Manager to the storage.
System action
Interrupts the processing. The setting for the storage is unclear.
System administrator response
Re-enter the command.
As other operation of the same Manager is being executed to the storage, this operation could not be executed.
Explanation
As the storage is being logged in by other operation of the same Manager, the command cannot be executed.
System action
Interrupts the processing.
System administrator response
Re-execute on completion of other operation of the same Manager.
Invalid CA port was specified.
Explanation
The access path cannot be set to the specified CA.
System action
Interrupts the processing.
System administrator response
Confirm the adapter type of the CA port to set the access path.
The adapter type that can be set the access path is FCCA only.
Command processing for devices ended abnormally on detection of processing error (ERR_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
Command processing was stopped because an error was detected during processing.
System action
Interrupts the processing after changing the access path settings for some devices.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the error information displayed in "Detail" and then re-enter the command.
Command processing for devices ended abnormally on detection of processing error (ERR_XXXX_NAME). Some devices' access path was modified (XXXX_NAME). Reboot of some devices are required to enable definition (if the device is server node and supports dynamic reconfiguration function, unnecessary) (REBOOT_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
The processing could not be performed for the device because the status of a certain device was not normal.
System action
Interrupts the processing after changing the access path settings for some devices.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the error information displayed in "Detail", and then re-enter the command.
Some device processing was skipped (SKIP_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
Completes the processing by skipping the access path setting for some devices.
System action
Command processing was stopped because an error was detected during processing.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the status of the storage (for which processing was skipped) indicated in "Detail", and then re-enter the command.
Some device processing was skipped (SKIP_XXXX_NAME). And some devices' access path were modified (XXXX_NAME). Reboot of some devices are required to enable definition (if the device is server node and supports dynamic reconfiguration function, unnecessary) (REBOOT_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
Completes the processing by skipping access path setting for some devices.
System action
Command processing was stopped because an error was detected during processing.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the status of the storage (for which processing was skipped) indicated in "Detail", and then re-enter the command.
Command processing for devices ended abnormally on detection of processing error (ERR_XXXX_NAME). And some device processing was skipped (SKIP_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
Errors were detected in the access path settings of several devices.
Also, the processing was skipped for a certain device because the device status was not normal.
System action
Command processing was stopped because an error was detected during processing.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the status of the storage for which processing was skipped and error information indicated in "Detail", and then re-enter the command.
Command processing for devices ended abnormally on detection of processing error (ERR_XXXX_NAME). And some device processing was skipped (SKIP_XXXX_NAME). And some devices' access path were modified (XXXX_NAME). Reboot of some devices are required to enable definition (REBOOT_XXXX_NAME). 'EDIT_HBA_NAME' means checking device definition file (e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
Errors were detected in the access path setting for several devices.
Also, the processing was skipped for a certain device because the device status was not normal.
System action
Command processing was stopped because an error was detected during processing.
System administrator response
It will edit, if the device definition files (sd.conf/st.conf etc.) relevant to HBA of a server node are checked and there is necessity.
Check the status of the storage (for which processing was skipped because of an error) indicated in "Detail", and then re-enter the command.
A problem was found in DB of administrative server. Some device's access path configuration was MODIFIED. Reboot device to make this configuration valid(if the device is server node and supports dynamic reconfiguration function, unnecessary). 'EDIT_HBA_NAME' means checking device definition file(e.g. sd.conf/st.conf) and editing by manual if necessary is required. :
Explanation
An inconsistency was detected in the database data. Also, the access path settings for several devices were changed. To validate the settings, the devices must be rebooted.
System action
Command processing was stopped because an error was detected during processing.
System administrator response
Contact your Fujitsu systems engineer.
Unable to delete zone for switch. This is because of port zoning possibly due to zone setting not being one-to-one. Zone setting: %ZONES
Explanation
The Manager can delete only a WWPN (World Wide Port Name) zone with one-to-one zone setting.
Parameters
%ZONES : Indicates the zone setting that could not be deleted.
System action
Interrupts the processing.
System administrator response
Login to the switch directly and then manually adjust the zone setting.
The specified switch is NO SECURITY state, it does not have any Zoning setting. All ports are accessible but it is low level security. The user setting is 'KEEP this state'. If you set the switch as 'Set WWPN Zoning', you can get higher security level when connection new Access Path. (Note: 'Set WWPN Zoning' may cause the problem of current Access Path). Please refer the user/operation manual for the problem of current Access Path, how to change the switch setting and details.
Explanation
The status of the specified switch is NO_SECURITY.
System action
None
System administrator response
Check the system security.
The specified switch is NO SECURITY state; it does not have any Zoning setting. All ports are accessible but it is low level security. The user setting is 'Set WWPN Zoning', so you can get higher security level when connection new Access Path. But 'Set WWPN Zoning' may cause the problem of current AccessPath, to avoid the problem, you can set the switch as 'KEEP this state'. Please refer the user/operation manual for the problem of current Access Path, how to change the switch setting and details.
Explanation
The status of the switch to be operated is NO_SECURITY.
System action
None
System administrator response
Check the system security.
The specified switch is NO SECURITY state, it does not have any Zoning setting. The user setting is 'Set WWPN Zoning'. Setting WWPN Zoning to the switch bring you higher security level, but it may cause the problem of current Access Path. Please refer the user/operation manual for the problem of current Access Path, how to change the switch setting and details. If you really want to continue to set WWPN Zoning, change the argument and Try again.
Explanation
The status of the switch to be operated is NO_SECURITY.
System action
None
System administrator response
Check the system security.
The specified switch is NO SECURITY state; it does not have any Zoning setting. Processing stopped because the user setting is 'KEEP this state'. If you change the switch setting to 'Set WWPN Zoning', you can get higher security level when connection new Access Path. (Note: 'Set WWPN Zoning' may case the problem of current Access Path). Please refer the user/operation manual for the problem of current Access Path, how to change the switch setting and details.
Explanation
The status of the switch to be operated is NO_SECURITY.
System action
None
System administrator response
Check the system security.
Input value is invalid. Deleting the UnknownFcPort is only supported with process level=0. An Internal Program inconsistency was detected.
Explanation
A device deletion request was issued with the access path deletion option to an UnknownFcPort device.
System action
None
System administrator response
None
An error occurred when processing WWPN Zoning to the switch. Error switch name (ERR_SWITCH_NAME), Skipped switch name (SKIP_SWITCH_NAME), Processed switch name (SWITCH_NAME):
Explanation
A problem was detected during the processing for the WWPN zoning of a switch
System action
None
System administrator response
None
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system.
System action
None
System administrator response
Delete the access path with the server powered down
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of HBA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring status of HBA is also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Storage is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring status of the storage is also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Storage and HBA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of the storage and HBA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of CA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring status of CA is also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of HBA and CA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of HBA and CA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Storage and CA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of the storage and CA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Storage, CA and HBA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of HBA, storage, and CA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Bridge is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring status of the bridge is also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Bridge and HBA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of the bridge and HBA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Bridge and CA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of the bridge and CA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
The device observe status of server node should be 'TIMEOUT' for deleting MultiPath driver on Windows system. And one of Bridge, CA and HBA is also not appropriate for this operation.
Explanation
The device monitoring status of the server node must be "communication disabled" to enable deletion of the MultiPath driver under Windows system. The device monitoring statuses of the HBA, bridge, and CA are also inappropriate.
System action
None
System administrator response
Delete the access path with the server powered down.
After access path deletion, start the server to execute "Recreation of MultiPath" from the GUI of the MultiPath driver. For "Recreation of MultiPath", refer to the manual for MultiPath driver.
Processing stopped. PORT Zoning to the switch is not supported yet.
Explanation
Zoning processing in the PORT ZONING format was specified for the switch. The present Manager does not support PORT ZONING.
System action
None
System administrator response
None
The WWPN of source and destination is SAME. Command terminated.
Explanation
The move source WWPN matches the move destination WWPN. Processing was interrupted.
System action
None
System administrator response
None
The HBA WWPN of Host Affinity for Create already exists in another AffinityGroup, Please set or check Affinity setting by ETERNUSmgr or GRmgr or GR Service Console.
Explanation
The HBA WWPN for host affinity to be created has already been set for another affinity group. Use ETERNUSmgr/GRmgr or GR service console to set host affinity directly.
System action
None
System administrator response
Set host affinity directly.
Inputted device does not support Performance function for administrative server.
Explanation
The performance display function does not support the specified device.
System action
None
System administrator response
None
The device does not support Port Beacon function.
Explanation
The specified device does not support the port beacon function.
System action
None
System administrator response
None
An Internal Program Error occurred: IP address is required for Performance function.
Explanation
An internal program error was detected (IP address information is needed to execute the performance display function.).
System action
None
System administrator response
None
An Internal Program Error occurred: Enterprise code is required for Performance function.
Explanation
An internal program error was detected (ENTERPRISE CODE is needed to execute the performance display function.).
System action
None
System administrator response
None
An Internal Program Error occurred: Inputted LUN information is invalid.
Explanation
An internal program error was detected (LUN information is needed to execute the performance display function.).
System action
None
System administrator response
None
Source and Destination WWPN is same. Command processing is terminated.
Explanation
The inheritance source and destination WWPNs are the same. Processing was interrupted.
System action
None
System administrator response
None
The Fc-Port type of two FcPorts must be same.
Explanation
The port types of the two specified FC ports do not match. A connection cannot be set up.
System action
None
System administrator response
Change the port connection type settings according to the environment.
A port connected to the Fibre Channel switch needs to be set to Fabric connection (N-type port). Set individual ports according to the device type by referring to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
For a port connected to a hub or ports not connected to a Fibre Channel switch, the connection type needs to be set to Loop connection (FC-AL type port). Set the ports by referring the respective driver manuals for HBA or the device manuals for the CA-type port.
The Fibre Channel cable is not physically connected via Switch. Connect Access Path in this case is not supported.
Explanation
When a Fibre Channel cable is not physically connected via a switch, an access path is not connected. (Normally, an access path need not be connected.)
System action
None
System administrator response
None
Manager could not set the SNMP Trap destination address of the device automatically. Please set following IP address as SNP Trap destination address by appropriate way.
Explanation
The SNMP trap send destination IP address of the specified device cannot be set. Set the IP address, which is displayed in an appropriate manner for the device, for the SNMP trap send destination.
System action
None
System administrator response
Set the IP address, which is displayed in an appropriate manner for the device, for the SNMP trap send destination.
New device was found, but auto-adding the device failed. %MESSAGE
Explanation
A new device was detected as the result of device search. However, a problem was detected during automatic device registration.
Parameters
%MESSAGE : Detail information on the problem detected during device registration
System action
Interrupts the processing.
System administrator response
Register the device again.
The operation for this OS kind or OS version of server node is not supported.
Explanation
This operation for the selected OS type or version number of server node
is not supported.
System action
Interrupts the processing.
System administrator response
None
CA's WWPN for HBA storage affinity is plurally saved. An appropriate process(e.g disks -C command) may be not done after Access Path processing on Solaris environment. Or an internal program error occurred.
Explanation
The specified WWPN for HBA storage affinity and the WWPN for a CA were found to be duplicate during the processing.
If the host node is a Solaris OS environment proper procedures (for example, commands such as "disks -C") may not have performed, or an internal program error may have occurred.
System action
Interrupts the processing.
System administrator response
If the host node is a Solaris OS environment, then check procedures such as access path definition. For details, refer to the "ETERNUS SF Storage Cruiser User's Guide", section "Operation" > "Access Path Management".
If the host node is not a Solaris OS environment or this issue is not solved after taking measures according to the paragraph above, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
The operation is not appropriate for this device.
Explanation
An instruction for an operation that is not supported on the specified device was issued.
System action
Interrupts the processing.
System administrator response
None
Unexpected error has occurred.
Explanation
An unexpected exception occurred.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE)..
Network communication error occurred. The target device address:
Explanation
A network communication error occurred.
System action
Interrupts system processing.
System administrator response
Check the LAN environment for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unable to find the device. The target device address:
Explanation
The specified device was not found.
System action
Interrupts system processing.
System administrator response
Check whether the entered IP address, the network settings of that device, and the settings required to manage that device are valid.
When the device to be detected is an ETERNUS disk array, the following environment settings may not be correct.
For details, refer to "Chapter 4 Environment Configuration" in the ETERNUS SF Storage Cruiser User's Guide.
The network environment settings in the disk array (Check whether the network settings for communication with the Manager have been made.)
SNMP agent environment settings in the disk array
In some cases, the community name of an ETERNUS disk array or a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
Network I/O error occurred. The target device address:
Explanation
An I/O error occurred during network communication.
System action
Interrupts system processing.
System administrator response
Check the LAN environment for problems. Or, check the target device for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Timeout error occurred in communication with the device. The target device address:
Explanation
A time-out occurred during communication with the specified device.
System action
Interrupts system processing.
System administrator response
Check the LAN environment for problems. Alternatively, check the target device for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
No response from the device. The target device address:
Explanation
No response was received from the specified device.
System action
Interrupts system processing.
System administrator response
Check the LAN environment for problems. Alternatively, check the target device for problems.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
SNMP protocol error occurred. The target device address:
Explanation
An SNMP protocol error occurred.
System action
Interrupts system processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unrecovered SNMP error occurred. The target device address:
Explanation
An unrecoverable SNMP error occurred.
System action
Interrupts system processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The device is not a SAN manager server node agent. The target device address:
Explanation
A server node device was detected but is not an Agent.
System action
Interrupts system processing.
System administrator response
Check whether the IP address of the specified device is correct. If the detected server node device is an Agent, the Agent may not run normally on the server node. Alternatively, check the target device for problems.
Unable to find a GRSC managing the GR. The target GR address:
Explanation
A GR disk array unit managed by GRSC was detected but GRSC was not found.
System action
Interrupts system processing.
System administrator response
Check the LAN environment for problems. Alternatively, check the target device for problems.
Internal program error occurred.
Explanation
An internal program error was detected.
System action
Interrupts system processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The device is not supported by the administrative server. The target device address:
Explanation
The specified device is not supported.
System action
Interrupts system processing.
System administrator response
Check whether the IP address of the specified device is correct.
The FCMGMT-MIB Revision of the device is not supported by the administrative server. FCMGMT-MIB Revision:
Explanation
The FCMGMT-MIB revision of the specified device is not supported.
System action
Interrupts system processing.
System administrator response
Check whether the IP address of the specified device is correct.
The FCMGMT-MIB Unit Type of the device is not supported by the administrative server. FCMGMT-MIB Unit Type:
Explanation
The FCMGMT-MIB device type of the specified device is not supported.
System action
Interrupts system processing.
System administrator response
Check whether the IP address of the specified device is correct.
Unexpected interrupt occurred during processing. The target device address:
Explanation
An interrupt occurred during processing.
System action
Interrupts system processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Unexpected error occurred. The target device address:
Explanation
An unexpected error occurred.
System action
Interrupts system processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The physical connection between the specified devices is not supported.
Explanation
The physical connection between the specified devices(except between router devices and switch devices) is not supported.
System action
None
System administrator response
None
Plural physical connections between one router device and one switch device is not supported.
Explanation
Multiple physical connections between one router device and one switch device is not supported.
System action
None
System administrator response
None
The SNMPTrap transmission address for the specified device was not able to be chosen automatically: %IPAddress%
Explanation
During device registration, the automatic SNMP Trap destination address setting function attempted to select the SNMP Trap destination address, but it could not select an appropriate address for the specified device.
Parameters
%IPAddress% : IP address of the target device
System action
None.
System administrator response
The network settings of the management server may be incorrect.
Check the IP address, host name, and other various network settings of the management server.
If no network routing daemon (such as "routed") is used, verify that the default gateway setting is correct.
If the same error occurs even though the setting is correct, refer to "MANAGER_LAN_CARD_IP" in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and set all IP addresses of the management server.
If the same error occurs even after taking the above measures, disable the automatic SNMP Trap destination address setting function, and add the device.
Note that the correct SNMP Trap destination address cannot be selected if the network address conversion such as the NAT function is performed. In such cases, disable the automatic SNMP Trap destination address setting function, and add the device.
When the automatic SNMP Trap destination address setting function is disabled, refer to the device manual, and manually specify an appropriate SNMP Trap destination address.
Command canceled.
Explanation
The command was canceled.
System action
The system closes the command.
System administrator response
None
syntax error. detail=%DETAIL
Explanation
The command syntax is invalid. 'usage' is displayed.
Parameters
%DETAIL : One of the following is displayed:
If the command was not specified:
command is not specified.
If the specified command (value) is invalid:
command[value] is invalid.
If the specified parameter is invalid:
parameter is invalid.
If the specified option [value] is invalid:
option[value] is invalid or duplicated.
If the value or format of the option [value] is invalid:
[value] is invalid value or format.
System action
The system displays 'usage' and interrupts the processing.
System administrator response
The system administrator reviews the command syntax and and then re-executes the operation.
Unexpected error has occurred.
Explanation
An unexpected exception occurred.
System action
Interrupts the processing
System administrator response
Please remove the following causes. Afterwards, please operate it again.
Please start the Manager when the Manager has stopped.
Please log out when you log in the switch.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Skipped processing server node and Storage, cause it is a Manually Embedded Device.
Explanation
Access path processing was not performed for the server node (or FC-HBA adapter) or storage device (or FC-CA adapter) because the devices were set up using the manual embedding function.
Perform manual access path processing for the storage that has the host affinity function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Perform manual access path processing for the storage that has the host affinity function.
Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After the setting has been made, the target server node must be rebooted in reconfigure mode. (This is not necessary if the server node supports the dynamic reconfiguration function.)
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Skipped processing storage, cause it is a Manually Embedded Device. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After the server node access path definition is changed, the target server node must be rebooted in reconfigure mode (the server node need not be rebooted if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Perform manual access path processing for the storage that has the host affinity function.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.) after the reboot of selected storage. Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function.
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. After the reboot of selected storage, you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported.
Set the server node access path manually.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
System action
Completes the commands partially.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted in reconfigure mode to reconfigure the server node special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported.
Set the server node access path manually.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Completes the command partially.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node and Storage, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch.
Access path processing was not performed for the server node (or FC-HBA adapter) and storage device (or FC-CA adapter) because the devices were set up using the manual embedding function.
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding. Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Next, to reconfigure the device special file, the target server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. Skipped processing storage, cause it is a Manually Embedded Device. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Perform manual access path processing for the storage that has the host affinity function.
Next, to reconfigure the device special file, the target server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch and storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.) after the reboot of selected storage. Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch to define the access path. A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function.
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch and storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. And after the reboot of selected storage, you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch to define the access path. A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch to define the access path.
System action
The command is completed normally.
System administrator response
The target server node must be rebooted in reconfigure mode to enable the access path settings. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for switch. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Zoning was set for the switch.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Next, to reconfigure the device special file, the target server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for switch and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
To define the access path, zoning was set for the switch and host affinity was set for the storage.
System action
The command is completed normally.
System administrator response
The target server node must be rebooted in reconfigure mode to enable access path setting. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for switch and storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device.
Explanation
To define the access path, zoning was set for the switch and host affinity was set for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
After this setting has been made, the target server node must be rebooted in reconfigure mode. (This is not necessary if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
The target server node must be rebooted in reconfigure mode to enable access path setting. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for switch and storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
To define the access path, zoning was set for the switch and host affinity was set for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After this setting has been made, the target server node must be rebooted in reconfigure mode. (This is not necessary if the server node supports the dynamic reconfiguration function.).
System action
The command is completed normally.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
The target server node must be rebooted in reconfigure mode to enable access path setting. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Could not find any accessible switch. Processing with switch was skipped.
Explanation
An attempt was made to search for a switch that can be used for access path definition but none was found.
This error occurs if no switch is registered or if the switch status is abnormal.
System action
Partially completes the command.
System administrator response
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command.
Skipped processing storage, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for storage that has the host affinity function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing server node, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing server node and Storage, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node (or FC-HBA) and storage device (or FC-CA adapter) because the devices were set up using the manual embedding function.
Perform manual access path processing for the storage that has the host affinity function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Perform manual access path processing for the storage that has the host affinity function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After this setting has been made, the target server node must be rebooted in reconfigure mode. (This is not necessary if the server node supports the dynamic reconfiguration function.).
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing storage, cause it is a Manually Embedded Device. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually.
After the server node access path definition is changed, the target server node must be rebooted in reconfigure mode (the server node need not be rebooted if the server node supports the dynamic reconfiguration function.).
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Perform manual access path processing for the storage that has the host affinity function.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.) after the reboot of selected storage. Skipped processing server node, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function.
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. And after the reboot of selected storage, you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported.
Set the server node access path manually.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Restart the storage to enable the storage settings, and then reboot the server node in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Could not find any accessible switch. Processing with switch was skipped.
Explanation
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing server node, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. After this setting has been made, the target server node must be rebooted in reconfigure mode (not needed if the server node supports the dynamic reconfiguration function.).
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Then, the target server node must be rebooted in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted in reconfigure mode to reconfigure the server node special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Switch processing was skipped because the switch version was not supported or no available switch was found.
System action
Partially completes the command.
System administrator response
Reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. You can make device path of server node (Manually Embedded server node) using server node device awareness method (e.g. server node reboot or dynamic reconfigure function.). Skipped processing server node, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Access path processing was not performed for the server node or FC-HBA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the server node that has a storage affinity function such as HBA WWPN binding.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. Please modify HBA and driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage.
Changing of the access path definition for the combination of the specified FC-HBA and storage type is not supported. Set the server node access path manually. Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually change the access path definition related to the specified FC-HBA and storage type.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings. Then, the server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Reboot the server node in reconfigure mode.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file on the server node. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
For access path definition, HBA WWPN binding was set for the server node, /kernel/drv/sd.conf was set, and zoning was set for the switch.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and switch. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and switch. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and switch and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Zoning was set for the switch.
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings. Then, the server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Reboot the server node in reconfigure mode.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
Access path was defined normally for server node and switch and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage. Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file on the server node. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The
server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node and switch and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.).
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage. Zoning was set for the switch.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
The server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
The server node must be rebooted in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Skipped processing storage, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Perform manual access path processing for the storage that has the host affinity function.
Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. Could not find any accessible switch. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage.
To reconfigure the device special file on the server node, first restart the storage and then, after it has restarted normally, reboot the target server node in reconfigure mode. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Restart the storage and then reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.) after the reboot of selected storage. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings. Then, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
Restart the storage to enable the storage settings. Then, reboot the server node in reconfigure mode. (This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Reboot the server node in reconfigure mode.
(This is necessary only if the server node does not support the dynamic reconfiguration function.)
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. However, a server node that supports the dynamic reconfiguration function need not be rebooted.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf). Next, the server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node and storage. You can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
WWPN binding for Fibre Channel HBA was set in the server node, and LUN information was set in kernel/drv/sd.conf. Also, host affinity was set for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file on the server node. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for server node and storage. Please modify driver configuration file (sd.conf/st.conf/etc...) manually for new devices. Then you can make device path of server node using server node device awareness method (e.g. server node reboot or dynamic reconfiguration function.). Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path operation was performed for the server node. For server node access path setting, only the configuration file (WWPN binding) of Fibre Channel HBA was edited. First edit the appropriate driver configuration file (such as /kernel/drv/st.conf) manually.
A host affinity operation was performed for the storage.
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Manually edit the appropriate driver configuration file (such as /kernel/drv/st.conf).
The server node must be rebooted in reconfigure mode to reconfigure the device special file. The server node need not be rebooted, however, if it supports the dynamic reconfiguration function.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition after the reboot of selected storage.
Explanation
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings and the server node must be rebooted.
System action
The command is completed normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node.
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition.
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted.
System action
The command is completed normally.
System administrator response
Reboot the server node.
Access path was defined normally for switch. Reboot of the selected server node is required to enable definition.
Explanation
Zoning was set for the switch.
System action
The command is completed normally.
System administrator response
Reboot the server node.
Access path was defined normally for switch. Reboot of the selected server node is required to enable definition. Skipped processing storage, cause it is a Manually Embedded Device.
Explanation
Zoning was set for the switch.
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
The server node must be rebooted.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
Reboot the server node.
Access path was defined normally for switch and storage. Reboot of the selected server node is required to enable definition after the reboot of selected storage.
Explanation
Zoning was set for the switch. A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings and the server node must be rebooted.
System action
The command is completed normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node.
Access path was defined normally for switch. Reboot of the selected server node is required to enable definition.
Explanation
Zoning was set for the switch.
System action
The command is completed normally.
System administrator response
Reboot the server node.
Access path was defined normally for switch and storage. Reboot of the selected server node is required to enable definition.
Explanation
Zoning was set for the switch. A host affinity operation was performed for the storage. The server node must be rebooted.
System action
The command is completed normally.
System administrator response
Reboot the server node.
Could not find any accessible switch. Processing with switch was skipped.
Explanation
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Skipped processing storage, cause it is a Manually Embedded Device. Could not find any accessible switch. Processing with switch was skipped.
Explanation
Access path processing was not performed for the storage device or FC-CA adapter because the device was set up using the manual embedding function. Perform manual access path processing for the storage that has the host affinity function.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Perform manual access path processing for the storage that has the host affinity function.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition after the reboot of selected storage. Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The storage must be restarted to enable the storage settings and the server node must be rebooted.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Restart the storage to enable the storage settings. Then, reboot the server node.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Could not find any accessible switch. Processing with switch was skipped.
Explanation
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
Partially completes the command.
System administrator response
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
Access path was defined normally for storage. Reboot of the selected server node is required to enable definition. Could not find any accessible switch. Processing with switch was skipped.
Explanation
A host affinity operation was performed for the storage. The server node must be rebooted.
An attempt was made to search for a switch that can be used for access path definition but none was found.
This problem occurs if the switch version is not supported, if no switch is registered, or if the device status of the switch is abnormal.
System action
The command is completed normally.
System administrator response
Reboot the server node.
Check the switch between the specified FC ports. If no switch is present or if none is registered, no action is required.
If the device status of each switch is abnormal, wait until the device statuses become normal and then re-enter the command. If the switch version is not supported, operate the switch directly.
The Input CA was not found.
Explanation
The specified CA cannot be found. Either the specified CA is invalid, or the storage device that was used to install the CA has not been registered.
System action
Interrupts the processing
System administrator response
Perform either of the following actions and then re-execute the operation.
If the specified CA is invalid,
Check whether the CA that was installed in the storage device has been specified correctly.
If the storage device has not been registered,
Register the storage device that was used to install the specified CA.
The specified switch is NO SECURITY state, it does not have any Zoning setting. Setting WWPN Zoning to the switch bring you higher security level, but it may cause the problem of current Access Path. Please refer the user/operation manual for the problem of current Access Path, how to change the switch setting and details.
Explanation
The status of the operation target switch is that there are NO_SECURITY settings.
System action
None
System administrator response
The system administrator checks the system security.
Access path addition or deletion went wrong.
Explanation
In the state of the device that relates to access path setting, access path cannot be set.
System action
Interrupts the processing
System administrator response
Please remove the following causes. Afterwards, please operate it again.
When the server node equipped with HBA specified for the -hba option is registered in this software
Please start this server node when you specify "add". Moreover, please remove the cause when the monitoring status of HBA is not normal.
Please stop this server node when you specify "delete".
Please register when storage or bridge is not registered in this software.
Please remove the cause when the monitoring status of storage or bridge is not normal.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Exit Performance Manager.
Explanation
Confirm whether or not to end performance management.
System action
If <OK> button is clicked, performance management ends.
System administrator response
To end performance management, click <OK> button. Otherwise, click <Cancel> button.
Close All Performance Management Windows.
Explanation
Confirm whether or not to close all the performance management windows.
System action
If <OK> button is clicked, all the performance management windows close.
System administrator response
To close the performance management windows, click <OK> button. Otherwise, click <Cancel> button.
The device with IP Address %IP_ADDRESS% was registered.
Explanation
This message indicates that the device with IP address %IP_ADDRESS% has been registered in the performance management window. %IP_ADDRESS% is used as the device name.
Parameters
%IP_ADDRESS% : IP address of the device registered in the performance management window
System action
Registers the device in the performance management window and displays the device configuration as a tree view.
System administrator response
None
The device with IP address %IP_ADDRESS% was registered with device name %NAME%.
Explanation
This message indicates that the device with IP address %IP_ADDRESS% has been registered in the performance management window. %NAME% is used as the device name.
Parameters
%IP_ADDRESS% : IP address of the device registered in the performance management window
%NAME% : Name assigned to the device
System action
Registers the device in the performance management window and displays the device configuration as a tree view.
System administrator response
None
The device with IP address %IP_ADDRESS% has already been registered.
Explanation
This message indicates that the device with the specified IP address was not newly registered because it has already been registered in the performance window.
Parameters
%IP_ADDRESS% : IP address of the device already registered in the performance window
System action
None
System administrator response
Use a device that has already been registered.
The device with IP address %IP_ADDRESS% has already been registered with device name %NAME%.
Explanation
This message indicates that the device with the specified IP address was not newly registered because it has already been registered in the performance window.
Parameters
%IP_ADDRESS% : IP address of the device already registered in the performance window
%NAME% : Name of the device already registered in the performance window
System action
None
System administrator response
Use a device that has already been registered.
Uncompleted to register the device %IP_ADDRESS%
Explanation
A device could not be registered successfully because the configuration file for the device was not found or could not be read.
Parameters
%IP_ADDRESS% : IP address of the device registered in the performance management window
System action
Registers the device but does not display the device internal structure in tree view format.
System administrator response
A performance graph cannot be displayed under this condition. Select "Create Configuration Information File" from the performance management window for the target device.
Failed to register the device with IP address %IP_ADDRESS.
Explanation
This message indicates that the device could not be registered in the performance management window because an error occurred during network communication with the device or the device did not support the performance monitoring function.
Parameters
%IP_ADDRESS% : IP address of the device to be registered in the performance management window
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. Check the device and network environment for errors, and then re-execute the processing.
Failed to register the device %NAME%(%IP_ADDRESS%).
Explanation
This message indicates that the device could not be registered in the performance management window because an error occurred during network communication with the device or the device did not support the performance monitoring function.
Parameters
%NAME% : Name of the device to be registered in the performance management window
%IP_ADDRESS% : IP address of the device to be registered in the performance management window
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. Check the device and network environment for errors, and then re-execute the processing.
Failed to update the registration information for device %NAME%(%IP_ADDRESS%).
Explanation
The device registration information could not be updated because an error occurred while the configuration file was read or written.
Parameters
%NAME% : Name of the registered device
%IP_ADDRESS% : IP address of the registered device
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. If the system failed to read the configuration file, select "Create Configuration Information File" and then update the registration information again. If the system failed to write to the configuration file, update the registration information again.
All performance graph of the device is deleted. A device configuration file for device %NAME%(%IP_ADDRESS%) will be created and the tree view will be updated. Also, all the performance graphs of device %NAME%(%IP_ADDRESS%) will be deleted. And the setting of threshold monitoring will be deleted. If you continue threshold monitoring, please set the threshold again after the device configuration.
Explanation
Configuration information is read from the specified device and saved to a file. The device tree is updated and the device performance graph is deleted from the display. The settings for device threshold monitoring are also deleted.
Parameters
%NAME% : Name of the device subject to performance monitoring
%IP_ADDRESS% : IP address of the device subject to performance monitoring
System action
When <OK> button is clicked, the system creates a configuration file, updates the device tree, deletes the performance graph, and then deletes the threshold monitoring settings.
System administrator response
To create a configuration file, click <OK> button. Otherwise, click <Cancel> button.
Creation of the device configuration file for device %NAME%(%IP_ADDRESS%) has been completed.
Explanation
This message indicates that configuration information was read from the specified device and has been successfully saved to a file.
Parameters
%NAME% : Name of the device subject to performance monitoring
%IP_ADDRESS% : IP address of the device subject to performance monitoring
System action
Creates a configuration file, updates the device tree, and deletes the displayed performance graph.
System administrator response
None
Failed to create the device configuration file for device %NAME%(%IP_ADDRESS%).
Explanation
This message indicates that an error occurred while configuration information was being read from the device or while the read configuration information was being saved to a file.
Parameters
%NAME% : Name of the device subject to performance monitoring
%IP_ADDRESS% : IP address of the device subject to performance monitoring
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. If an error occurred during network communication with the device, check the device and network environment for errors. Also check whether the user is authorized to write to the file system to which the configuration information is to be saved or whether the file system has sufficient free space. Then, re-execute processing.
Failed to set up the performance monitoring on device %NAME%(%IP_ADDRESS%).
Explanation
This message indicates that performance monitoring setting failed because an error occurred during network communication with the device or during processing for saving the monitoring status data to the performance management definition file.
Parameters
%NAME% : Name of the device subject to performance monitoring
%IP_ADDRESS% : IP address of the device subject to performance monitoring
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. If an error occurred during network communication with the device, check the device and network environment for errors. Also, check whether the file system which is to be written into the performance management definition file has the written permission and whether the file system has enough free space. Then, re-execute processing.
Device %NAME%(%IP_ADDRESS%) will be deleted.
Explanation
Confirm whether or not to delete the specified device from the performance management window. When deleting the device, select whether to stop performance monitoring for the device.
Parameters
%NAME% : Name of the registered device
%IP_ADDRESS% : IP address of the registered device
System action
When <OK> button is clicked, deletes the specified device and no longer displays it in the performance management window.
System administrator response
To delete the device, click <OK> button. Otherwise, click <Cancel> button. Also, select whether to stop performance monitoring for the device.
The performance monitoring on device %NAME%(%IP_ADDRESS%) will be deleted without being stopped.
Explanation
Confirm whether or not to delete the device from the performance management window without stopping performance monitoring.
Parameters
%NAME% : Name of the registered device
%IP_ADDRESS% : IP address of the registered device
System action
When <OK> button is clicked, the specified device is deleted but performance monitoring for the device continues. When the <Cancel> button is clicked, a configuration dialog box asking whether to delete the device is displayed again.
System administrator response
To delete the device without stopping performance monitoring, click <OK> button. Otherwise, click <Cancel> button.
Failed to delete device %NAME%(%IP_ADDRESS%).
Explanation
This message indicates that the specified device could not be deleted from the performance management window because of an error in the stopping processing of performance monitoring for deleting the device. The error occurred during network communication with the device or during processing for saving performance monitoring status data to the performance management definition file.
Parameters
%NAME% : Name of the target device
%IP_ADDRESS% : IP address of the target device
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. When performance monitoring is stopped for deletion of the device, an error may occur during network communication with the device or during the processing for saving the performance monitoring status data to the performance management definition file. Check the device and network environment for errors, and then re-execute the processing.
Failed to view the performance graph.
Explanation
This message indicates that the performance graph could not be displayed because an error occurred while the performance information file or device configuration information file was read.
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. If a performance information file that may not be read successfully exists, the performance cannot be graphed. Delete the performance information file or move it to another location. If the configuration information file could not be read, select "Create Configuration Information File" from the performance management window and re-execute performance graph display processing.
Failed to load the registered device.
Explanation
This message indicates that the device on which a configuration information file was created could not be registered automatically when the system started. The performance information file may contain an error.
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. Execute "Create Configuration Information File" from the performance management window.
If this fails to solve the problem when the Manager is restarted, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Failed to automatically start the performance monitoring.
Explanation
When the Manager was started, the performance monitoring facility that was running previously could not be started automatically. An error may have occurred in the performance management definition file or in the configuration information file of the target device.
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. Start performance monitoring again or select "Create Configuration Information File" from the performance management window.
If this fails to solve the problem when the Manager is restarted, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Failed to show device %NAME%(%IP_ADDRESS%) as a tree view.
Explanation
This message indicates that the device configuration could not be displayed as a tree view because the configuration information file of the target device could not be read and device configuration information could not be obtained.
Parameters
%NAME% : Name of the target device
%IP_ADDRESS% : IP address of the target device
System action
Interrupts the processing.
System administrator response
If a detail message is output, check the message content. If the configuration information file could not be read, select "Create Configuration Information File" from the performance management window.
Failed to show device %NAME%(%IP_ADDRESS%) as a tree view.
Explanation
This message indicates that device configuration information cannot be created because the target device is under threshold monitoring.
Parameters
%NAME% : Name of the target device
%IP_ADDRESS% : IP address of the target device
System action
Interrupts the processing.
System administrator response
Stop threshold monitoring for the target device by selecting "Set Threshold/Start Monitoring/Stop Monitoring" from the menu. Execute "Create Configuration Information File" from the performance management window.
A network socket error occurred in communication with a device {0}. Please check the device or the network infrastructure.
Explanation
This message indicates that an error occurred during network communication with the device subject to performance monitoring.
Parameters
{0} : IP address of the target device
System action
If an error occurs during performance monitoring, processing is retried and continued. In other cases, processing is interrupted.
System administrator response
Check the target device or network environment for errors.
A network I/O error occurred in communication with a device {0}. Please check the device or the network infrastructure.
Explanation
This message indicates that an error occurred during network communication with the device subject to performance monitoring.
Parameters
{0} : IP address of the target device
System action
If an error occurs during performance monitoring, processing is retried and continued. In other cases, processing is interrupted.
System administrator response
Check the target device or network environment for errors.
A network timeout error occurred in communication with a device {0}. Please check the device or the network infrastructure.
Explanation
This message indicates that a time-out occurred during network communication with the device subject to performance monitoring.
Parameters
{0} : IP address of the target device
System action
If an error occurs during performance monitoring, processing is retried and continued. In other cases, processing is interrupted.
System administrator response
Check the target device or network environment for errors.
An address {0} is wrong.
Explanation
This message indicates that the specified address is invalid for the IP address.
Parameters
{0} : Specified address
System action
Interrupts the processing.
System administrator response
Specify a valid IP address.
A communication error occurred in communication with the Performance Monitor Engine. Please check the Performance Monitor Engine or the network infrastructure.
Explanation
This message indicates that a communication error occurred during processing driven from the performance management window.
System action
Interrupts the processing.
System administrator response
Make sure that the product version/level is the same between the Manager and Client.
If a patch has been applied, refer to the application conditions provided in the patch description about the patch applied to the Manager, and make sure that the patch has also been applied to the Client.
If re-executing processing does not solve the problem, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A SNMP protocol error occurred in communication with a device {0}. Please check the device or the network infrastructure.
Explanation
This message indicates that an error occurred during SNMP protocol communication for obtaining performance information from the device subject to performance monitoring.
Parameters
{0} : IP address of the target device
System action
Interrupts the processing.
System administrator response
Check the device or network environment for errors.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to find the performance configuration file {0}.
Explanation
This message indicates that various settings for the performance management program could not be performed because the performance management definition file was not found.
Parameters
{0} : Name of performance management definition file
System action
Interrupts the processing.
System administrator response
Allocate the performance management definition file to the specified directory and then restart the OpenCIMOM daemon. (For an explanation of the restart procedure, refer to "Chapter 12 Command References" in the ETERNUS SF Storage Cruiser User's Guide.)
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to create the performance configuration file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that the current definition information could not be saved because a performance management definition file could not be created.
Parameters
{0} : Name of performance management definition file
System action
Interrupts the processing.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then re-execute the processing.
Unable to read the performance configuration file {0}. The contents of the file may be incorrect.
Explanation
This message indicates that settings for the performance management program could not be made because the performance management definition file could not be read. The definition file may not exist or may contain an error.
Parameters
{0} : Name of the performance management definition file
System action
Interrupts the processing.
System administrator response
Allocate the error-free performance management definition file to the specified directory and then restart the OpenCIMOM daemon. (For an explanation of the restart procedure, refer to "Chapter 12 Command References" in the ETERNUS SF Storage Cruiser User's Guide.)
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to write the performance configuration file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that the current definition information could not be saved because a performance management definition file could not be created.
Parameters
{0} : Name of performance management definition file
System action
Interrupts the processing.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then re-execute the processing.
Unable to find a config XML file {0}.
Explanation
This message indicates that the configuration information file for the device subject to performance monitoring was not found.
Parameters
{0} : Name of configuration information file
System action
Interrupts the processing.
System administrator response
Execute "Create Configuration Information File" from the performance management window.
Unable to create a config XML file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that a configuration information file for the device subject to performance monitoring could not be created.
Parameters
{0} : Name of configuration information file
System action
Interrupts the processing.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then execute "Create Configuration Information File" from the performance management window.
Unable to read a config XML file {0}. The contents of the file may be incorrect.
Explanation
This message indicates that the configuration information file for the device subject to performance monitoring could not be read. The configuration information file may not exist or may contain an error.
Parameters
{0} : Name of configuration information file
System action
Interrupts the processing.
System administrator response
Execute "Create Configuration Information File" from the performance management window.
Unable to write a config XML file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that a configuration information file could not be created because an error occurred while device configuration information required for device tree-view display was being saved to a file.
Parameters
{0} : Name of configuration information file
System action
Interrupts the processing.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then execute "Create Configuration Information File" from the performance management window.
Unable to find a performance data file {0}.
Explanation
This message indicates that the performance information file required for displaying a performance graph was not found. A performance information file is not created when performance monitoring is not performed. So, this message does not indicate an error if a performance information file is not found when an attempt is made to display performance information while performance monitoring is not being performed. If a performance information file is not found even when performance monitoring is being performed, the file system may be write-protected or may not have sufficient free space.
Parameters
{0} : Name of performance information file
System action
Continues the processing.
System administrator response
None
Unable to create a performance data file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that a performance information file could not be created during performance monitoring and performance information obtained from the device subject to performance monitoring could not be saved.
Parameters
{0} : Name of performance information file
System action
Interrupts performance monitoring.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then restart performance monitoring from "Set Performance Monitoring".
Unable to read a performance data file {0}. The contents of the file may be incorrect.
Explanation
This message indicates that the performance information file could not be read during displaying a performance graph. The performance information file may contain an error.
Parameters
{0} : Name of performance information file
System action
Interrupts performance graph display.
System administrator response
If a performance information file that may not be read successfully exists, performance cannot be graphed. Delete the performance information file or move it to another location.
For information on the performance information file that cannot be read, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to write a performance data file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
This message indicates that the performance information obtained from the device subject to performance monitoring could not be saved to the performance information file during performance monitoring.
Parameters
{0} : Name of performance information file
System action
Interrupts performance monitoring.
System administrator response
Check whether the file system is write-protected or check the size of the file system, and then restart performance monitoring from "Set Performance Monitoring".
A device {0} is not supported the representational function in the performance window.
Explanation
The performance management function does not support the display function at the performance management window for the specified device.
Parameters
{0} =Device name (IP address of target device)
System action
Interrupts the processing.
System administrator response
Check that the correct device is specified.
Check whether the performance management function supports the display function at the performance management window for the specified device.
For details on how to check whether the performance management function supports the display function at the performance management window for the specified device, refer to the " ETERNUS SF Storage Cruiser User's Guide", section "Overview" > "Summary of Each Function" > "1.3.7 Support Levels".
If this does not solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
A device {0} is not supported performance monitoring.
Explanation
This message indicates that the specified device cannot be used in the performance management window because the device does not support the performance monitoring function.
Parameters
{0} : IP address of the target device
System action
Interrupts the processing.
System administrator response
Check whether the device specification is correct.
Check whether the specified device supports the performance monitoring function. For details, refer to the "ETERNUS SF Storage Cruiser User's Guide", section "Overview" > "Summary of Each Function" > "1.3.7 Support levels".
If this fails to solve the problem, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A device (class {0}) is not supported by this program
Explanation
This message indicates that the specified device is not supported for the performance management window.
Parameters
{0} : Name of the class file to be loaded to control the specified device
System action
Interrupts the processing.
System administrator response
Check whether the device specification is correct.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
An unexpected error occurred.
Explanation
This message indicates that an unexpected error such as a program internal error occurred.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The device {0} is under threshold monitoring. Please stop the threshold
monitoring first and stop the performance monitoring.
Explanation
The device is under threshold monitoring.
Parameters
{0} : IP address of the target device
System action
Interrupts the processing.
System administrator response
Stop threshold monitoring and then stop performance monitoring.
The LogicalVolume within specified range does not exist.
Explanation
LogicalVolume does not exist within the range (minimum LUN_V to maximum LUN_V) input on the Performance Management dialog.
System action
Interrupts the processing.
System administrator response
Specify the range within which LogicalVolume exists.
When changes were made on the device configuration, execute "configuration
information file creation" and update the configuration file.
After these procedures, specify the range including LogicalVolume.
The definition file has been reloaded.
Explanation
The performance control function definition file perf.conf has been reloaded.
System action
The performance control function definition file perf.conf has been reloaded and reflected dynamically.
System administrator response
None
It failed on the reload of the definition file.
Explanation
The performance control function defition file perf.conf has failed.
System action
Interrupts the processing
System administrator response
Follow the detailed messages.
If detailed messages are not displayed, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to login a device {0}. Login name or password is incorrect.
Explanation
This message indicates that an attempt was made to login to the target device to set performance monitoring for the device or read the configuration information but failed because an invalid login name or password was specified.
Parameters
{0} : IP address of the target device
System action
Interrupts the processing.
System administrator response
Check the login name or password set in the target device. Alternatively, check the login name or password of the registered target device.
Unable to login a device {0}. Another user has a login session from {1}.
Explanation
This message indicates that an attempt was made to login to the target device to set performance monitoring for the device or to read the configuration information but failed because another user has already logged into the device.
Parameters
{0} : IP address of the target device
{1} : IP address of the server node that logged into the target device
System action
Under performance monitoring, retries processing until another login ends so that the processing can continue. In other cases, interrupts the processing.
System administrator response
Log out the process that logged into the target device and then re-execute the processing. Under performance monitoring, processing is automatically re-executed.
A communication error occurred with a device {0}. Please check the device.
Explanation
This message indicates that an error occurred during command processing for the target device for setting performance monitoring or reading configuration information.
Parameters
{0} : IP address of the target device
System action
Interrupts the processing.
System administrator response
Check the target device for errors, and then re-execute the processing.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Unable to login a GRSC {1} managing a device {0}. Login name or password is incorrect.
Explanation
This message indicates that an attempt to login to GRSC to set performance monitoring for the target device, or to read the configuration information, failed because an invalid login name or password was specified.
Parameters
{0} : IP address of the target device
{1} : IP address of GRSC that manages the target device
System action
Interrupts the processing.
System administrator response
Check the settings for the GRSC or target device. Alternatively, check the login name or password of the registered target device.
Unable to login a GRSC {1} managing a device {0}. Another user has a login session.
Explanation
This message indicates that an attempt to login to GRSC to set performance monitoring for the target device, or to read the configuration information, failed because another user had already logged into the device.
Parameters
{0} : IP address of the target device
{1} : IP address of GRSC that manages the target device
System action
Under performance monitoring, processing is retried until another login ends, after which the processing continues. In other cases, the processing is interrupted.
System administrator response
Log out the process that logged into the GRSC managing the target device and then re-execute the processing. Under performance monitoring, processing is automatically re-executed.
A user '{2}' on a GRSC '{1}' managing a device {0} not authorized to set up the device."
Explanation
This message indicates that the specified login name cannot be used to set performance monitoring for the device because it does not have setting authority for the device.
Parameters
{0} : IP address of the target device
{1} : IP address of GRSC that manages the target device
{2} : Specified login name
System action
Interrupts the processing.
System administrator response
Check the GRSC settings. Alternatively, check the login name or password of the registered target device.
Unable to access to a device {0} with a GRSC {1}. The device {0} is not managed by the GRSC.
Explanation
This message indicates that an attempt was made to access a GR series RAID device via GRSC but the GRSC does not manage the GR series RAID device.
Parameters
{0} : IP address of the target device
{1} : IP address of GRSC that manages the target device
System action
Interrupts the processing.
System administrator response
Check the GRSC settings. Alternatively, check the URL address of the registered target device.
A communication error occurred with a GRSC {1} managing a device {0}. Please check the device or the GRSC.
Explanation
This message indicates that an attempt to set performance monitoring for a GR series RAID device managed by GRSC or to read configuration information on the device failed because an error occurred during command processing for the GRSC.
Parameters
{0} : IP address of the target device
{1} : IP address of GRSC that manages the target device
System action
Interrupts the processing.
System administrator response
Check the target device for errors, and then re-execute the processing.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
CM Command '{0}' Failed. Please check the device.
Explanation
This message indicates that an attempt to set performance monitoring for a GR series RAID device or to read configuration information on the device failed because CM command execution failed.
Parameters
{0} : Name of the CM command to be executed
System action
Interrupts the processing.
System administrator response
Check the target device for errors, and then re-execute the processing.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Internal Program error occurred.
Explanation
An internal program error was detected.
System action
Interrupts system processing.
System administrator response
Contact your Fujitsu systems engineer.
SNMP error occurred in bridge communication.
Explanation
An SNMP error occurred during communication with the bridge.
System action
None
System administrator response
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Socket error occurred in bridge communication.
Explanation
A socket error occurred during communication with the bridge.
System action
None
System administrator response
Contact your Fujitsu systems engineer.
Unable to find selected bridge.
Explanation
The specified bridge was not found.
System action
None
System administrator response
Check the specified device.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Network I/O Error on bridge communication.
Explanation
An I/O error occurred during communication with the bridge..
System action
None
System administrator response
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
No response from bridge.
Explanation
A required bridge was not found.
System action
None
System administrator response
Check the target device.
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
User Name or Password is incorrect for bridge. Device:
Explanation
An attempt to login to the bridge failed. The user name or password is invalid.
System action
None
System administrator response
None
Another user has logged into bridge. Logout and run function again. Device:
Explanation
Another user has already logged into the bridge. Log out the user and then re-execute.
System action
None
System administrator response
None
Parse error on telnet for bridge.
Explanation
Analysis of the execution results of the TELNET command issued to the bridge failed.
System action
None
System administrator response
None
A wrong point was detected in SCSI Cable connected to Bridge.
Explanation
An error was detected on the SCSI cable connected to the bridge.
System action
None
System administrator response
Contact your Fujitsu systems engineer.
Are you sure you want to register this device?
Explanation
The selected device will be added to the management server.
System action
None
System administrator response
None
The device has been registered.
Explanation
Registering of the device on the administrative server ended normally.
System action
None
System administrator response
None
The user name or password cannot be changed.
Explanation
The account information on the registered device could not be updated.
System action
None
System administrator response
None
Are you sure you want to configure SNMP traps on this device?
Explanation
A device, for which SNMP trap is not set, will be set as an SNMP trap destination so that the device can be managed by the Manager.
System action
None
System administrator response
None
Are you sure you want to delete xxxxx?
Explanation
Target device xxxxx will be excluded from management.
Parameters
xxxxxx : Device name for a server node, system name for a switch, system name for a storage
System action
None
System administrator response
None
xxxxxxx has been deleted.
Explanation
Device xxxxxx has been excluded from management.
Parameters
xxxxxx : Device name for a server node, system name for a switch, system name for a storage
System action
None
System administrator response
None
All access paths to xxxxx will be deleted.
Explanation
The access paths set for device xxxxxx are deleted.
Parameters
xxxxxx : Device name for a server node, system name for a storage
System action
None
System administrator response
None
The device is in the 'normal' state. Are you sure you want to delete it?
Explanation
A device in the normal state will be deleted.
System action
None
System administrator response
None
Enter a network address for device search.
Explanation
Enter the network address (IP address) of the device to be searched for.
System action
None
System administrator response
None
xxxxx devices were found.
Explanation
The device with IP address xxx.xxx.xxx.xxx was found.
Parameters
xxx.xxx.xxx.xxx : IP address
System action
None
System administrator response
None
Are you sure you want to create the access path using the above settings?
Explanation
An access path will be set as shown in the window.
System action
None
System administrator response
None
The access path has been created.
Explanation
The access path has been set normally. To use the set access path, the server node storage must be rebooted.
System action
None
System administrator response
None
Select devices to be shown.
Explanation
Select the server node or storage for which an access path is to be set.
System action
None
System administrator response
None
There are no devices that can be shown.
Explanation
There is no storage device for which an access path is to be set.
System action
None
System administrator response
None
The WWPN for xxxxx has been changed to yyyyy. Do you want to proceed with the access path auto-reset?
Explanation
WWPN of xxxxx was changed to WWPN HBA of yyyyy. Confirm whether or not to change the previously set access path for WWPN to the xxxxx HBA.
Parameters
xxxxx : Device name
yyyyy : Device name
System action
None
System administrator response
None
Access path inheritance has been completed.
Explanation
The configuration information for the access path that was set for the old HBA/FC port was set to the specified HBA/FC port and processing for inheriting the access path configuration information has been completed.
System action
None
System administrator response
None
Select devices to be hidden.
Explanation
Select a device to be deleted from those displayed in the window.
System action
None
System administrator response
None
There are no devices that can be hidden.
Explanation
There are no devices that can be deleted.
System action
None
System administrator response
None
Are you sure you want to delete the access path?
Explanation
The access path setting will be deleted.
System action
None
System administrator response
None
The access path has been deleted.
Explanation
Deletion of the access path setting has completed normally.
System action
None
System administrator response
None
Are you sure you want to use the following LUN for access path diagnosis?
Explanation
Access path diagnosis will be executed using the specified LUN.
System action
None
System administrator response
None
The URL is invalid.
Explanation
The specified URL address is not found.
System action
None
System administrator response
None
The Help URL is invalid.
Explanation
The specified HELP URL address is not found.
System action
None
System administrator response
None
The path is invalid.
Explanation
It was not possible to execute the application which registered as management software because it was not found. Please confirm the registered information.
System action
None
System administrator response
None
A status change has been detected. Are you sure you want to update the administrative server status information?
Explanation
Because a change in the device information was detected, the current status display will be updated to reflect the latest information.
System action
None
System administrator response
None
When the operation completes, select "Refresh" from the "View" menu.
Explanation
Upon the completion of the current operation, select "Refresh" from the menu options to update the display with the operation results.
System action
None
System administrator response
None
The device name has already been registered. Please enter a different name.
Explanation
The name specified for the new name of the device cannot be used because that name has already been registered for another device in the database. Specify another device name.
System action
None
System administrator response
None
A name must be entered for device registration.
Explanation
Processing for changing the device name cannot be continued because no device name is specified. Specify a device name to continue the processing for changing the device name.
System action
None
System administrator response
None
The device name must be 24 characters or less.
Explanation
The specified device name consists of over 24 characters. As for RAID devices, GR series and ETERNUS series, specify the device name consisting of below 24 characters and execute the procedure to change the name.
System action
None
System administrator response
Specify the device name that consists of below 24 characters.
Icon positions have been saved.
Explanation
Icon position setting data has been saved successfully.
System action
None
System administrator response
None
The notes will be saved. Are you sure you want to save the notes?
Explanation
This message confirms the update of the memo information because a change was found in the notepad information.
System action
None
System administrator response
None
The notes have been saved.
Explanation
The notepad information has been saved successfully.
System action
None
System administrator response
None
Are you sure you want to save the notes?
Explanation
Confirm whether or not to update the memo information because a change was found in the notepad information.
System action
None
System administrator response
None
Are you sure you want to change the management software location?
Explanation
Confirm whether or not to continue to change management software information.
System action
None
System administrator response
None
The notes have been edited but not saved. Are you sure you want to close the properties window?
Explanation
The property was about to be ended with the note pad in the property edited. Please end the property after executing "Save Notepad" of the note pad when you want to save edited note pad information.
System action
None
System administrator response
None
Error code list for SAN GUI Control could not be developed.
Explanation
The error code file (GuiCtrlErrCode.csv) for GUI control does not exist, the file data is invalid, or a fatal error occurred during data loading.
System action
Interrupts the processing.
System administrator response
Collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
SANMA GUI MODEL could not be initialized.
Explanation
Initialization of the SANMA GUI MODEL failed because of a CIM interface error.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
SANMA GUI MODEL has not been initialized.
Explanation
The SANMA GUI MODEL has not been initialized because of an error in the interface with CIM.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Failed to initialize the Storage Cruiser(control module).
Explanation
The client GUI control module could not be initialized because client GUI configuration information could not be read.
System action
Interrupts the processing.
System administrator response
If message java.rmi.RemoteException is output as a detail message, probably the RMI is not started. Please restart this software.
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Failed to initialize the Storage Cruiser.
Explanation
The client GUI display could not be initialized because illegal processing was detected during the initialization of the client GUI display system.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An internal program inconsistency was detected.
Explanation
An access path is not set. Therefore, the data to be displayed in the table information could not be initialized.
System action
Interrupts the processing.
System administrator response
None
Please enter an IP address or name to search for.
Explanation
Information to search the device isn't input. Please input search condition and search it again.
System action
None
System administrator response
None
Select the icons of the HBA and FC port to be linked by an access path.
Explanation
Select and execute both icons of the HBA and CA for which access paths are to be set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Select the HBA and FC port to be linked by an access path.
Explanation
Select and execute both icons of the HBA and CA for which access paths are to be set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Enter a number between 0 and 255.
Enter a number between 0 and 511.
Enter a number between 0 and 1023.
Explanation
Enter a number from 0 to 255 to make the setting.
Enter a number from 0 and 511 to make the setting.
Enter a number from 0 and 1023 to make the setting.
System action
None.
System administrator response
Please input the LUN information.
No LUN has been configured.
Explanation
A required LUN was not specified.
System action
None
System administrator response
Enter LUN information.
The HBA/FC port to status is other than "changed" so it cannot be automatically reset.
Explanation
The status of the relevant HBA is other than "changed" and cannot be automatically re-set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An HBA icon must be selected.
Explanation
No HBA icon is selected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Affinity group 0 has not been configured.
Explanation
AffinityGroup 0 has not been set.
System action
Interrupts the processing.
System administrator response
Configure AffinityGroup0 in the disk array and reexecute.
If AffinityGroup0 already exists, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The specified Target ID is already in use. Enter another Target ID.
Explanation
The specified Target ID is already set. Specify another Target ID.
System action
Interrupts the processing.
System administrator response
Specify another Target ID.
Unexpected exception was detected.
Explanation
A client GUI internal error or a SAN configuration error was detected.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The LUN mapping for the access path is not defined.
Explanation
The access paths cannot be set because LUNMapping information has not been specified for CA ports with security off.
System action
Interrupts the processing.
System administrator response
Configure LUNMapping for the CA port with security off, for which an access path is to be set in the disk array.
The affinity group for the access path is not defined.
Explanation
The access paths cannot be set because AffinityGroup information has not been specified for CA ports with security on.
System action
Interrupts the processing.
System administrator response
Configure AffinityGroup in the disk array and re-execute.
A remote CA was chosen when trying to create an access path.
Explanation
CA port which was going to perform an access path setup cannot perform an access path setup because of Remote CA.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "Operation" > "Access Path Management" > "Access path setting", then contact your Fujitsu systems engineer (SE).
The access paths of two registered devices in the domain cannot be connected to each other.
Explanation
The access paths of two registered devices in the domain cannot be connected to each other.
System action
Interrupts the processing.
System administrator response
None
The access paths created during provisioning cannot be deleted.
Explanation
The access paths that are connected by the provisioning operation cannot be deleted.
System action
Interrupts the processing.
System administrator response
None
An access path cannot be created using the selected FC port.
Explanation
An access path to the selected port cannot be set up.
System action
Interrupts the processing.
System administrator response
Confirm the type of port for which you want to set the access path.
A CA that is assigned to an ETERNUS VD800 transaction server cannot be connected to an access path.
The FC port that the FC-Initiator type is set cannot be connected to an access path.
You attempted to delete an access path that was not a WWPN connection.
Explanation
An attempt was made to delete an access path other than WWPN BINDING (WWPN connection).
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An HBA and FC port were selected that are not connected by an access path.
Explanation
Select and execute both icons of the HBA and CA for which access paths are to be set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Select the HBA and FC port of the access path to be deleted.
Explanation
Select the HBA and CA for which access paths are set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Select the HBA and FC port icons of the access path to be deleted.
Explanation
Select the HBA and FC port for which access paths are set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
No access path has been configured.
Explanation
No access paths have been set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Access path diagnosis is disabled (Under Solaris, diagnosis can only be performed on an access path with WWPN_Zoning).
Explanation
The selected access path cannot be diagnosed because it was set by switch zoning (Another Binding).
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A monitoring or device status error was detected for the selected HBA or FC port.
Explanation
The status of the HBA or CA of the selected access path is other than "OK."
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Select the HBA and FC port that have an access path configured.
Explanation
Select the HBA and CA for which access paths are set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Select the HBA and FC port icons on which the diagnosis should be performed.
Explanation
Select the icon for the access path to be diagnosed or the icons for the HBA and CA for which access paths are set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Access path diagnosis is disabled (because a Target ID has not been configured for the selected access path).
Explanation
An attempt was made to diagnose an access path for which no Target ID was set.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Diagnosis cannot be performed because the LUN to be diagnosed has not been entered.
Explanation
Access path diagnosis has been interrupted because LUN information was not entered.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Access path diagnosis is disabled (because diagnosis cannot be performed on a tape device).
Explanation
Access path diagnosis has been interrupted because an attempt was made to diagnose a tape device access path.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Input parameter error was deleted from SAN manager GUI.
Explanation
An invalid value was specified.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Error detected in format of message information data.
Explanation
The format of the message code data used for internal processing was invalid.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Null information was received.
Explanation
Null data was received as a response to the processing.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Null object was assigned.
Explanation
Null information was included in a parameter specified for processing.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Can not find file.
Explanation
The message code file or error code file cannot be obtained.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Input-Output error.
Explanation
An error occurred while reading or writting a file in Client.
System action
Interrupts the processing.
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Could not save icon positions.
Explanation
Icon position data could not be saved.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The search has completed. There are no more devices to be found.
Explanation
Information was searched for based on the specified search conditions but no relevant information was found.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Please enter a term to search for.
Explanation
Enter the search conditions.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An area overflow that could affect the Storage Cruiser GUI was detected.
Explanation
An error occurred because the GUI display area defined by Java overflowed.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An unexpected error occurred. Please try the operation again and check the result.
Explanation
A processing error or an unexpected error was detected. Perform the same operation again to check the processing.
System action
None
System administrator response
When this is output following an operation in the "Eco-mode information and set" window
If the window is not displayed when the [ECO-mode information and set] tab is selected in the ETERNUS storage device property display, verify that the target storage device supports the Eco-mode.
If the target storage device supports the Eco-mode and the information is still not displayed, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
Other case
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The selected device is not being performance monitored.
Explanation
An error occurred because an attempt was made to make performance settings for a device that does not support performance management.
System action
None
System administrator response
None
There is no default browser registered with operating system.
Explanation
URL information could not be displayed because the Web browser used to reference URL information is not installed or registered.
System action
Interrupts web display.
System administrator response
Check the Web browser environment of the PC with the client installed.
Select an available port and then the device that it will be connected to.
Explanation
To automatically register the detected FC and SCSI ports during manual embedding, select the FC and SCSI ports to be registered and the registration destination device.
System action
None
System administrator response
None
Do you want to update the administrative server with the latest information?
Explanation
Information was edited on the Manual Configuration window. Please update the management information of client.
System action
None
System administrator response
None
The device cannot be registered until all mandatory fields are completed.
Explanation
Information required for manual embedding has not been entered.
System action
None
System administrator response
Enter the data for the items required for manual embedding.
Please enter the required information then try again.
Explanation
Information required for manual embedding has not been entered.
System action
None
System administrator response
Enter the data for the items required for manual embedding.
The device name is the same as one already registered with the administrative server. Please enter a device name other than xxxxxx.
Explanation
The registration name specified for manual embedding is already being used. Enter another name for registration.
System action
None
System administrator response
Specify another device name.
A device with this SCSI ID or LUN has already been registered.
Explanation
The SCSI ID or LUN specified for manual embedding is already being used. Specify another SCSI ID or LUN to register it.
System action
None
System administrator response
The specified information may have already been defined. Check the system information and enter valid information.
Enter a bridge device name.
Explanation
A bridge device name has not been entered for manual embedding.
System action
None
System administrator response
None
Enter the number of SCSI buses for this bridge.
Explanation
The number of SCSI buses has not been entered for manual embedding.
System action
None
System administrator response
None
Enter a numerical value for the number of SCSI buses.
Explanation
The number of SCSI buses has not been entered in numeric format for manual embedding.
System action
None
System administrator response
None
A physical line already exists between the ports.
Explanation
During manual embedding, an attempt was made to connect a physical line to a port to which a physical line is already connected.
System action
None
System administrator response
Check whether a physical line has already been connected to the port to which a physical line is to be connected.
A physical line already exists for the hub port.
Explanation
During manual embedding, an attempt was made to connect an end of a physical line to a hub port to which a physical line is already connected.
System action
None
System administrator response
Check whether an end of a physical line has already been connected to the hub port to which a physical line is to be connected.
A physical line already exists between the hubs.
Explanation
During manual embedding, an attempt was made to connect both ends of a physical line to hub ports to each of which a physical line is already connected.
System action
None
System administrator response
Check whether a physical line has already been connected to each of the hub ports to each of which each end of a physical line is to be connected.
A physical line already exists between the routers.
Explanation
A physical line has already existed between devices though it tried to connect the port of the router device with the port of other devices on the Manual Configuration window.
System action
None
System administrator response
None
A physical line already exists for the router FC port.
Explanation
A physical line has already existed between the FC port of the device though it tried to connect between the ports of the two router devices on the Manual Configuration window.
System action
None
System administrator response
None
Please use a value less than or equal to 65534 for the controller number.
Explanation
Please set up a controller number of HBA for 65534 or less numerical value.
System action
None
System administrator response
None
Please use a value less than or equal to 65534 for the group number.
Explanation
Please set up a group number of CA or SCSI-CA for 65534 or less numerical value.
System action
None
System administrator response
None
Please use a value less than or equal to 65534 for the exchange unit number.
Explanation
Please set up an exchange unit number of CA or SCSI-CA for 65534 or less numerical value.
System action
None
System administrator response
None
Please use a value less than or equal to 65534 for the port.
Explanation
Please set up a port number of CA or SCSI-CA for 65534 or less numerical value.
System action
None
System administrator response
None
Comma ',' and backslash '\' characters cannot be used in manual embedding device names.
Explanation
Comma (,) and backing slash (\) cannot be used for the device name needed when a new device is registered on the Manual Configuration window.
System action
None
System administrator response
None
A device with the entered IP address could not be found. Please check that the IP address is correct.
An LT130 device with the entered IP address could not be found. Please check that the IP address is correct.
A built-in bridge 0 with the entered IP address could not be found. Please check that the IP address is correct.
A built-in bridge 1 with the entered IP address could not be found. Please check that the IP address is correct.
Explanation
IP address input by the device making does not exist in the network or the form of input IP address is wrong. Please input correct IP address after confirming to the Manager.
System action
None
System administrator response
In some cases, the community name of a device such as fibre channel switch that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the admin server may not be changed. If so, communication is disabled because of a mismatch of the community name. The community name of the target device needs to be set for the admin server.
Set the community name by referring to the "SNMP_COMMUNITY_NAME_FOR_IP" parameter provided in "C.2 sanma.conf Parameter" in the ETERNUS SF Storage Cruiser User's Guide, and reflect the contents of the setting file on this software.
If the problem persists even after checking the above environment settings, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
A device name must consist of more than just space characters. Please also use other characters in the device name.
Explanation
In the device making operation, input device names are all blank.
Please decide the device name by using characters other than the blank.
System action
None
System administrator response
None
Manual configuration window is started. Please close the manual configuration window before attempting this action.
Explanation
When the manual operation built-in window is started, switching windows by using a tab operation is inhibited. To switch to the logic resource management window, first close the manual embedding window, then select the tab item for switching to the logic resource management window.
System action
None
System administrator response
None
Please enter a numerical value in the range 1-1000.
Explanation
Please input the numerical value to 1-1000 when setting the number of lines displayed on SystemEvent.
System action
None
System administrator response
None
Failed.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Possible reasons for this message being output are as follows:
The OpenCIMOM daemon being used failed or was restarted.
OpenCIMOM is restarted in instances such as when the OS on the administrative server is restated or when cluster switching occurs on the administrative server.
Check whether OpenCIMOM is active. If OpenCIMON is down, restart it in accordance with the description in "Chapter 12 Command References" in the ETERNUS SF Storage Cruiser User's Guide.
The CIM data area is full.
Check whether the disk is full by the following method.
Platform of Manager | How to check |
|---|---|
Windows | Confirm the property information of the disk where CIM data base is stored. |
Solaris OS, | Use the "df -k /var/opt/FJSVssmgr/current/opencimom/logr" command. |
If the disk is full, take appropriate measures to ensure that the required free space can be reserved on the disk, and then restart the OpenCIMOM daemon (refer to "Chapter 12 Command References" in the ETERNUS SF Storage Cruiser User's Guide).
If the command or service confirms that OpenCIMOM is active or after OpenCIMOM is restarted, close the client management window and then reopen it.
If no error can be found by the above operations, other causes must be assumed.
Collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An invalid parameter is passed to a method.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
An invalid class is specified.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The specified element cannot be found.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The specified element already exists.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
The memory is low.
Explanation
An OpenCIMOM internal error was detected.
System action
None
System administrator response
Restart the OpenCIMOM daemon and restart this software.
If this fails to solve the problem, then collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information" and contact your Fujitsu systems engineer (SE).
unable to find the equipment/adapter.
Explanation
A required device or adapter is not found.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
no such association.
Explanation
The specified association is not found.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
failed to serialize the object.
Explanation
Object serialization failed.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
failed to create a new instance.
Explanation
Instance generation failed.
System action
None
System administrator response
Collect the data needed for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
%MPType% access path(%MPAccessPath%) fault in %SystemName%(%OSName%%OSVersion%[%IPAddress%]).
Explanation
A path was blocked during server node multipath disk control. The system is degraded.
Parameters
%MPType% : Type of multipath disk control
%MPAccessPath% : Access path name
%SystemName% : Server node name
%OSName% : OS name
%OSVersion% : OS version
%IPAddress% : IP address
System action
None
System administrator response
Take corrective measures on the server node for multipath disk control errors on the server node.
%MPType% access path(%MPAccessPath%) fault and no more path in %SystemName%(%OSName%%OSVersion%[%IPAddress%]).
Explanation
All paths have been blocked under server node multipath control.
Parameters
%MPType% : Type of multipath disk control
%MPAccessPath% : Access path name
%SystemName% : Server node name
%OSName% : OS name
%OSVersion% : OS version
%IPAddress% : IP address
System action
None
System administrator response
Take appropriate corrective measures on the server node for any multipath disk control errors on the server node.
Some paths could not be detected in %SystemName%(%OSName%%OSVersion%[%IPAddress%]).
Explanation
Part of paths could not be detected on server node startup.
Multipath control operation could not be started normally.
Parameters
%SystemName% : Name of the server node
%OSName% : OS name
%OSVersion% : OS version
%IPAddress% : IP address
System action
None
System administrator response
This event occurs when a server node is started, and it may occur even if multipath disk control can be used normally after the startup is complete. After server node startup is complete, execute "Refresh" in the resource view and check the status of the server node.If this issue is not solved, take corrective measures on the server node for multipath disk control errors on the server node.
LMF fault in %SysName%(%OSName%%OSVersion%[%IPAddress%])
Explanation
An error occurred in the magnetic tape library device.
Parameters
%SysName% : SysName
%OSName : Name of administrative server node OS
%OSVersion% : Version of administrative server node OS
%IPAddress% : administrative server node IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Central Memory FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
Self-diagnosis detected a central memory error in the Fibre Channel switch.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Embedded Port FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
Self-diagnosis detected an embedded port error.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
FC Port No.%PortNo% FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
A port failure was detected.
Parameters
%PortNo% : Port number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
FC Port No.%PortNo% %Status% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
The status change of the port was detected. This message is notified when the FC cable is pulled out and put in for instance.
Parameters
%PortNo% : Port number
%Status% : Port status(Online/Offline)
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Please confirm connected situation of the FC cable. Please contact Fujitsu maintenance technology member(CE) when it is not solved by the problem.
If this fails to solve the problem, contact your Fujitsu customer engineer (CE).
Power Supply #%PSNo% FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
The power supply fault was detected.
Parameters
%PSNo% : Power supply unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Fan #%FanNo% FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
The fan unit fault was detected.
Parameters
%FanNo% : Fan unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Temp #%TempNo% FAULT in %SysName%(%ProductID%[%IPAddress%]).
Explanation
A thermal sensor failure was detected.
Parameters
%TempNo% : temperature sensor number
%SysName% : SysName
%ProductID% : device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%EventMessage% in %SysName(%ProductID%[%IPAddress%]).
Explanation
An event trap was detected. The unit trap message is output without any change.
Parameters
%EventMessage% : Event message
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Please refer to the manual attached to the device. If this fails to solve the problem, contact your Fujitsu customer engineer (CE).
%ElementName%(%ItemId%) degraded in %SystemName%(%ProductID%[%IPAddress%]).
Explanation
A component failure was detected.
Parameters
%ElementName% : Element name
%ItemId% : Item ID
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%ElementName(%ItemId%) expiration in %SystemName%(%ProductID%[%IPAddress%]).
Explanation
The battery requires replacement.
Parameters
%ElementName% : Element name
%ItemId% : Item ID
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%partBrokenMessage% in %SysName%(%ProductID%[%IPAddress%])
Explanation
A possible failure was detected.
Parameters
%partBrokenMessage% : Possible failure content
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%sensorStatusChangeMessage% in %SysName%(%ProductID%[%IPAddress%])
Explanation
State change of thermal sensor or voltage sensor was detected.
Parameters
%sensorStatusChangeMessage% : Content of change in state of sensor
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%maintenanceInfo% in %SysName%(%ProductID%[%IPAddress%])
Explanation
Maintenance information was received.
Parameters
%maintenanceInfo% : Maintenance information
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
CM(%ItemId%) Warning(%PartsName%) in %SystemName%(%ProductID%[%IPAddress%]).
Explanation
CM Warning was detected.
Parameters
%ItemId% : Item ID of CM
%PartsName% : Part name
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
%automaticRestorationInfo% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
Auto recovery notification was received.
Parameters
%automaticRestorationInfo% : Auto recovery information
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
This message is output when the abnormal status was released. It is no necessary to response.
Acute Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A failure that causes the entire subsystem to stop was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Serious Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A failure that causes the failed part to stop was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Moderate Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A partial failure was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Service Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A minor failure was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
System down occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A local controller failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Drive blocking occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A data drive blockage was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Fan failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A fan alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Power supply failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A DC power failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Battery failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A battery alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Cache memory failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A cache memory blockage was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
UPS failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A UPS alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
AC line or inbox failure occurred in %SysName%(%productID%[%IPAddress%])
Explanation
An Inbox Failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Cache backup circuit failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A battery charging circuit alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Other controller failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A remote controller blockage was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Warning occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The warning status of the disk array was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Spare drive failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A spare drive blockage was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Enclosure controller failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
An ENC alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Loop failure occurred in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A loop failure alarm was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
%EventMessage% in %SystemName%(%ProductID%[%IPAddress%])
Explanation
An event message was detected.
Parameters
%EventMessage% : Message
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library fault in %SysName%(%productID%[%IPAddress%])
Explanation
An alarm occurred in the magnetic tape library device.
Parameters
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The media error occurred. (Barcode label: %value%) in %SysName%(%productID%[%IPAddress%])
Explanation
A drive media error was detected.
Parameters
%value% : Version and level
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The drive unit%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A drive error was detected.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The drive unit%value% became offline in %SysName%(%productID%[%IPAddress%])
Explanation
The drive went offline.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Check the state of the drive.
The drive unit%value% FAN alarm occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A drive fan error was detected.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The drive unit%value% needs cleaning in %SysName%(%productID%[%IPAddress%])
Explanation
The drive needs cleaning.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The drive unit%value% Link Down occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A drive link down occurred.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The adapter%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A Fibre Channel port failure was detected.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The CM reader error or CM error in medium occurred in %SysName%(%productID%[%IPAddress%])
Explanation
The CM reader error or CM error in medium was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The barcode reader error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A barcode reader failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The CAS unit%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A cartridge access station (CAS) failure was detected.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The battery unit error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A battery failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The library FAN(1) error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A fan failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The library FAN(2) error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A fan failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The library system error occurred. (FSC=%code%) in %SysName%(%productID%[%IPAddress%])
Explanation
A library failure was detected.
Parameters
%FSC% : Fault symptom code
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The front door opened on the library system in %SysName%(%productID%[%IPAddress%])
Explanation
The front door is open.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Check the state of the front door.
The library system became offline in %SysName%(%productID%[%IPAddress%])
Explanation
The library is offline.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Check the state of the library.
The CIC sensor error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A CIC sensor failure was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The CAS unit%value% open error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
An error was detected during open of the cartridge access station.
Parameters
%value% : Message
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The adapter%value% Link Down occurred in %SysName%(%productID%[%IPAddress%])
Explanation
The Fibre Channel port link is down.
Parameters
%value% : Unit number
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Check the state of the Fibre Channel port.
The FlashROM error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
An error was detected in the library boot ROM.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
No install adapter card in library system in %SysName%(%productID%[%IPAddress%])
Explanation
A required Fibre Channel port is not mounted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Read Data Error in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The drive read error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Write Data Error in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The drive write error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Read or Write Data Error in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The read or write data error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Detected Faulty Media in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Drive media error was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Read Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The tape or drive error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Write Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The tape or drive error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Reach end of Media in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Use of media reached the limit.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Not Data Grade Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
This tape is not data grade.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Attempted Backup to Write-protected Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Writing was performed to write-protected media.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Tape Drive is in use in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Since a drive is in use, a cartridge cannot be taken out.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Attempted Backup/Restore To Cleaning Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Backup/Restore to cleaning tape was performed.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Unsupported Media in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Unsupported media was inserted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Detected Snapped Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Snapped tape was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Detected Snapped Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Snapped tape was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device without taking out a tape.
Memory Chip in Cartridge Failure in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Memory tip error in cartridge was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Tape Cartridge was ejected in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The tape cartridge was ejected during read or write processing.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Detected Read-only Media in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Read-only media was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Detected Currupted Directory On Tape in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Currupted directory on tape cartridge was detected.The performance of file reference may fall.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
Detected Worn Out Media in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Worn out Media was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please exchange media.
Tape Device Needs Cleaning in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Tape device needs cleaning.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please perform cleaning of a tape device.
Drive Needs Routine Cleaning in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Tape device needs routine cleaning.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please perform cleaning of a tape device.
Detected Worn Out Cleaning Cartridge in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Worn out cleaning cartridge was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please exchange the cleaning cartridge in a tape drive.
Detected Invalid Cleaning Cartridge in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Invalid cleaning cartridge was detected.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please exchange for an effective cleaning cartridge.
Request retention in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The request of processing was suspended.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please refer to the manual attached to the device.
A Redundant Interface Port Failed in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the interface port where it overlaps on a tape drive.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Fan Failed in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the fan on a tape drive.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Power Supply Failed in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the power supply where it overlaps on a tape drive.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please replace unusual power supply with normal power supply. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Power Consumption is outside the specified range in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Power consumption of a tape drive is outside the specified range.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Require Preventative Maintenance in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Preventative maintenance of a tape drive is required.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please perform preventative maintenance of a tape drive.
Drive Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Drive hardware error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please take out a tape from the tape drive and reset the drive. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Drive Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Drive hardware error occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reboot the tape drive and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Server node Interface Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error has occurred in the server node interface.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please re-execute after checking the cable and the connection state of a cable. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Eject Media Request in %SystemName%(%ProductID%[%IPAddress%])
Explanation
It is the extraction request of media.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please put in a tape again and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Firmware Download Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Download of a firmware failed.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please use an effective firmware and re-execute.
Humidity Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The state in a tape drive exceeded humidity specification.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Temperature Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The state in a tape drive exceeded temperature specification.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Voltage Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The voltage to a tape drive is unusual.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Tape Device Predicted to Fail in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The hardware error of a tape drive is predicted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Drive Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The hardware error is predicted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
When the diagnostic test was carried out and abnormalities are detected, contact the Fujitsu customer engineer (CE) responsible for the device.
Autoloader Communications Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Communication between AutoLoader and a tape drive has an error.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reboot AutoLoader and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Detected Stray Tape In Autoloader in %SystemName%(%ProductID%[%IPAddress%])
Explanation
According to a former hardware error, a tape is in AutoLoader.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please insert an empty magazine in a drive. Please reboot AutoLoder, when a problem is not solved.When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Autoloader Mechanism Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred in AutoLoader.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Autoloader Door Open in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The door of AutoLoader is open.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please remove an obstacle from the door of AutoLoader and put in a magazine. Please reboot AutoLoder, when a problem is not solved. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Autoloader Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of hardware may have occurred in AutoLoader.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reboot AutoLoder. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Autoloader Cannot Operate Without Magazine in %SystemName%(%ProductID%[%IPAddress%])
Explanation
AutoLoader cannot work without a magazine.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please insert a magazine in AutoLoader and re-execute.
Autoloader Predicted to Fail in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in AutoLoader are predicted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Media Statistics have been Lost in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Media statistics have been lost.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Tape Directory has been currupted in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The tape directory was destroyed.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Tape just unloaded could not write its system area in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Since the tape is unloaded, it was not able to write to the system area normally.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please insert a tape and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Could not read System Area in %SystemName%(%ProductID%[%IPAddress%])
Explanation
System Area was not able to be normally read at the time of loading.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Start of Date Not Found in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The start of the date in a tape was not able to be found.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please use the tape of an effective format and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Drive Communications Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Communication between a library mechanism and a drive is unstable.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reboot a library. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Changer Mechanism Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred to the library mechanism.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reset a library and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Library Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please reboot a library and re-execute. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Library Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
When the diagnostic test was carried out and abnormalities are detected, contact the Fujitsu customer engineer (CE) responsible for the device.
Library Server node Interface Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error has occurred in the server node interface.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please re-execute after checking the cable and the connection state of a cable. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Library Predicted to Fail in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in library are predicted.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Require Preventative Maintenance in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Preventative maintenance of a library is required.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Humidity Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The state in a library exceeded humidity specification.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Temperature Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The state in a library exceeded temperature specification.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Voltage Specification Exceeded in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The voltage to a library is unusual.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Detected Stray Tape In Drive in %SystemName%(%ProductID%[%IPAddress%])
Explanation
According to a former hardware error, a cartridge is in library.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please remove a cartridge from a drive.
Picking Cartridge From Slot Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A potential problem is in the drive which emits a cartridge, or in the library mechanism which pick a cartridge from a slot.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Picking Cartridge Into Slot Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A potential problem is in the library mechanism which arranges a cartridge in a slot.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Loading Cartridge Into Drive Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
There is the drive which loads a cartridge, or the potential problem about a library mechanism, or the cartridge of non-compatibility.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library Door Open in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The door of a library is open.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please remove the obstacle from the door of the library and shut the door of the library. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Mailslot Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A mechanical problem is in library media reading/writing mailslot.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library Cannot Operate Without Magazine in %SystemName%(%ProductID%[%IPAddress%])
Explanation
A library cannot work without a magazine.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please re-execute after inserting a magazine in a library.
Library Security Compromised in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Library security is compromised.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library Security Mode Changed in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The security mode of a library was changed.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
None
Library Manually Turned Offline in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Since the library is manually set as offline, it cannot use.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please re-execute after starting a library.
Library Drive Turned Offline in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The drive in a library turned offline.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Reading Barcode Labels Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
In a library mechanism, there is a potential problem in barcode labels or scanner hardware.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Library Inventory is Inconsistent in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The library detected inconsistency in the catalog.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please redo a library catalog, in order to correct inconsistency. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Invalid Library Operation Attempted in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Invalid library operation was carried out.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please re-execute after checking that library operation is effective. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Redundant Interface Port Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the interface port where it overlaps on library.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Fan Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the fan on library.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Power Supply Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the power supply where it overlaps on library.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Please replace unusual power supply with a normal thing. When it carries out and the state does not change, contact the Fujitsu customer engineer (CE) responsible for the device.
Power Consumption Warning in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Power consumption of library is outside the specified range.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Robot Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a robot have occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Robot Hardware Fault in %SystemName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a robot have occurred.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
Barcode Read Error in %SystemName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred in reading of a barcode.
Parameters
%SystemName% : SysName
%ProductID% : Device name
%IPAddress% : IP adress
System action
None
System administrator response
Contact the Fujitsu customer engineer (CE) responsible for the device.
The PDU%value% error occurred.
Explanation
PDU power supply error was detected.
Parameters
%value% : PDU number
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
The PDU%value% power off occurred.
Explanation
PDU power supply interception was detected.
Parameters
%value% : PDU number
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Unit status changed(%status%) in %SysName%(%productID%[%IPAddress%])
Explanation
The status change of the unit was detected.
Parameters
%status% : unit status
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
When it shows abnormality, contact the Fujitsu customer engineer (CE) responsible for the device.
%EventMessage% in %SysName%(%productID%[%IPAddress%])
Explanation
Event message was detected.
Parameters
%EventMessage% : Message
%SysName% : SysName
%productID% : device name
%IPAddress% : IP address
System action
None
System administrator response
None
Unit Sensor status changed(%status%) in %SysName%(%productID%[%IPAddress%])
Explanation
The status change of the sensor was detected.
Parameters
%status% : Sensor status
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
When it shows abnormality, contact the Fujitsu customer engineer (CE) responsible for the device.
Unit Port state changed(%state%) in %SysName%(%productID%[%IPAddress%])
Explanation
The status change of the port was detected.
Parameters
%status% : Port status
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
None
%EventMessage%
Explanation
An event message was detected.
Parameters
%EventMessage% : Message
System action
None
System administrator response
None
%EventMessage% in %SysName%(%productID%[%IPAddress%])
Explanation
A device event defined in the SNMP Trap XML definition file was detected.
Parameters
%EventMessage% : Message defined in the SNMP Trap XML definition file
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
The response varies depending on the device and event type. For a device for which the XML definition file is provided, check the event type while referring to the following manual:
"Chapter 2 Events in Notifications Sent from Monitored Devices" in the ETERNUS SF Storage Cruiser Event Guide
Depending on the event type, take corrective action such as notifying your Fujitsu customer engineer (CE). For a device for which an original XML definition file was created, perform troubleshooting according to the predetermined maintenance procedure for the device.
%EventMessage% in %SysName%(%productID%[%IPAddress%])
Explanation
The status change of the device was detected.
Parameters
%EventMessage% : Message defined by SNMP Trap XML definition file
%SysName% : SysName
%productID% : Device name
%IPAddress% : IP address
System action
None
System administrator response
When the status indicates Error or Warning, check the device status using the device management software.
When the messages indicated a timeout, check the following:
Check the load on the network as this status may occur if the load is high.
Check the load of the target server as this status may occur if the load is high.
Check the communication modes, if one is set to "Auto Negotiation" and the other is set to "Full (all dual)" this status may occur.
If the problem happens infrequently, collect the data required for troubleshooting as explained in the "ETERNUS SF Storage Cruiser User's Guide", section "D.1 Troubleshooting information", then contact your Fujitsu systems engineer (SE).
Setup failed. Reason = Can't setup machine attribute
Explanation
An attempt to add a machine attribute to the node management file failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't setup vendor name
Explanation
An attempt to add a vendor name to the node management file failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't setup registry
Explanation
An attempt to register the node management file in the registry failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't setup MIB information
Explanation
Addition to the MIB management file failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't find file
Explanation
A node icon definition file does not exist.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't setup event icon
Explanation
Addition of the event type icon file failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't setup event category
Explanation
Addition of event types failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Systemwalker Centric Manager is not installed
Explanation
Systemwalker Centric Manager has not been installed.
System action
None
System administrator response
Check that Systemwalker Centric Manager has been installed normally and then re-enter the command on the server node on which Systemwalker Centric Manager has been installed.
Setup failed. Reason = Systemwalker Centric Manager is unsupported version
Explanation
The version of Systemwalker Centric Manager is not supported.
System action
None
System administrator response
Check the Systemwalker Centric Manager version, and then re-enter the command on the server node with a supported version.
Server setup completed
Explanation
Server node setup is completed.
System action
None
System administrator response
None
Setup failed. Reason = Can't lock file
Explanation
The file used to add event types could not be locked.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't read file
Explanation
The file used to add event types could not be read.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't write file
Explanation
An attempt to write to the file used to add event types failed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't unlock file
Explanation
The file used to add event types could not be unlocked.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Invalid OS
Explanation
The command was executed on an operating system that is not supported.
System action
None
System administrator response
Re-enter the command in a valid environment.
Setup failed. reason = Can't get current directory
Explanation
The current directory could not be obtained.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't copy icon file
Explanation
The icon file could not be copied.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Systemwalker Centric Manager is not installed
Explanation
Systemwalker Centric Manager has not been installed.
System action
None
System administrator response
Check that Systemwalker Centric Manager has been installed normally and re-enter the command in the client in which Systemwalker Centric Manager has been installed.
Setup failed. reason = Can't open registry file
Explanation
The registry file could not be opened.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't read registry file
Explanation
Registry key values could not be obtained.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't open setup file
Explanation
The event type icon definition file could not be opened.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Setup failed. Reason = Can't write setup file
Explanation
Writing to the event type icon definition file failed.
System action
None
System administrator response
None
Setup failed. Reason = Can't close setup file
Explanation
The event type icon definition file could not be closed.
System action
None
System administrator response
Contact your Fujitsu customer engineer (CE).
Client setup completed.
Explanation
Client setup has been completed.
System action
None
System administrator response
None
Setup failed. Reason = Systemwalker Centric Manager is unsupported version
Explanation
The version of Systemwalker Centric Manager is not supported.
System action
None
System administrator response
Check the Systemwalker Centric Manager version and then re-enter the command on the client with a supported version.
[XXX] device's supportLevel is PARTIAL. Not FULL.
Explanation
XXX device is a Manually Embedded Device.
System action
None
System administrator response
This is not the device that the setting is supported.
[XXX] device has no IP address.
Explanation
XXX device does not have IP address.
System action
None
System administrator response
This is not the device that the setting is supported.
Device does not exists in DB of SANmgr.
Explanation
The specified device does not exist in the database.
System action
None
System administrator response
Ensure the specified device and then re-execute.
Process is skipped.
This device is not set the SNMP Trap transmission place by user operation.
Explanation
The specified device is not the one that the SNMP Trap transmission destination setting is set by user action. Processing to set was skipped.
System action
None
System administrator response
None
Process is skipped.
This device is not support the SNMP Trap transmission function.
Explanation
The specified device does not support the SNMP Trap transmission function.Processing to set was skipped.
System action
None
System administrator response
None
Process is skipped.
This device is a not support device on this function. Please set the SNMP Trap transmission place manually.
Explanation
The specified device supports the SNMP Trap transmission destination, however this software does not support the automatic setting function. Processing to set was skipped. Execute the SNMP Trap transmission destination setting on the device manually.
System action
None
System administrator response
Execute the SNMP Trap transmission destination setting on the device manually.
An authentication error occurred with the entered account information. Please check the user name and password and enter it again.
Explanation
An error was detected during security checking. Check the user name and password in the account information defined in the attestation mechanism management and then re-enter the correct information.If this information is not defined in the attestation mechanism, ask the system administrator.
System action
Interrupts the processing
System administrator response
Check the user name and password that were entered.
Login with administrator authority and then define the account information again.
If the user name and password are correctly input and the account is newly added, the password that was specified at account creation was incorrect. Ask the administrator who created the account to specify again the password according to the procedure for [Password change].
The account information could not be updated. A possible reason for this error is that the account information management file has been corrupted or deleted.
Explanation
Attestation processing for updating the account information failed. A possible reason for this error occurring is that the account information management file has been destroyed.
System action
Interrupts the processing for updating account information
System administrator response
Have your Fujitsu systems engineer (SE) notify the Fujitsu technical department.
An account with this user name has already been registered.
Explanation
The specified account information cannot be registered because it is already registered in the account management.
System action
Interrupts the processing
System administrator response
Use a user name that has not been registered in account information.
The account information required to perform the requested operation cannot be found. Another administrator may have deleted the account.
Explanation
Account information required for executing the specified processing is not found. Another administrator may have deleted the account.
System action
Interrupts the processing
System administrator response
Check that the account required for executing the processing is registered.
There is a problem with the password information for this account. Please check and enter it again.
Explanation
An error was detected in the password information specified for account registration.
System action
Interrupts the processing
System administrator response
Check the password both in the password and password confirmation fields, and then execute registration again.
Nothing was entered in the password and/or password confirmation fields.
Explanation
An attempt was made to register an account without entering the password for registration in the password or password confirmation field.
System action
Interrupts the processing
System administrator response
Register an account by specifying the information required for account registration.
The user name is reserved by the system. Please choose another one.
Explanation
Account information registered in the program cannot be added. (manage/monitor)
System action
Interrupts the processing
System administrator response
Register account information with an account other than "manage" or "monitor".
Some of the required user information was not entered.
Explanation
A user name required for account registration was not specified.
System action
Interrupts the processing
System administrator response
Register an account after specifying the information required for account information registration.
There is a problem with the password information for this account. Please check and enter it again.
Explanation
The information on the current password in the selected account information is incorrect in the procedure of the password change under the account administration.Check the password information and specify it again.
System action
None
System administrator response
Specify the valid password information that is set in the account which executes the password change.
Please check whether the entered administrative server name or port number is wrong.
Explanation
An attempt to set up a network connection to the server that manages attestation management information failed.
System action
Interrupts the processing
System administrator response
Check the specified information on the administrative server.
Or a manager is not found, the case where the administrative server is not started can be considered. Please check whether the wrong administrative server name is entered or the administrative server is started normally.
Explanation
If a connection cannot be set up because the server name entered in the login window does not exist in the network, check whether the specified server name is valid. Alternative, if the administrative server (Manager) is not active, check whether the Manager has been started normally.
System action
Interrupts the processing
System administrator response
Check whether the specified server name is valid. For starting and stopping the administrative server, refer to "12.1.2.2 Starting and stopping the daemons of the administrative server at specific times" in the ETERNUS SF Storage Cruiser User's Guide.
Check whether the Agent is setup valid in case the Agent is installed. Refer to "Chapter 6 Agent installation and setup" in the ETERNUS SF Storage Cruiser Installation Guide.
Access to an account information file went wrong. Please check whether there is any problem in a file.
Explanation
An attempt to access the account management database failed. Check whether the management database can be accessed. Directory under /var/opt/FJSVssmgr
System action
Interrupts the processing
System administrator response
Check whether the directories and files under /var/opt/FJSVssmgr can be accessed. Also check the disk capacity.
%NAME% is not found on the network. Please check that the correct administrative server name was entered.
Explanation
The input administrative server name couldn't find in the network. Please confirm whether input administrative server name is correct. Or, please confirm the thing that the administrative server device starts normally.
Parameters
%NAME% : administrative server name
System action
Interrupts the processing
System administrator response
Please confirm the administrative server device starts normally.
An authentication error occurred with the entered account information. Please check the user name and password and enter it again.
Explanation
The input account isn't registered in the account administrative information. Please confirm the account to the Manager.
System action
Interrupts the processing
System administrator response
Please login in the account of the Manager authority, and confirm account information.
Nothing was entered in the password and/or password confirmation fields.
Explanation
The information that is necessary to change the password has not been specified in the procedure of the password change.
System action
None
System administrator response
Specify the necessary information in The Password Change Input dialog and execute the password change procedure.
No port number was entered for the administrative server.
Explanation
The port number used to connect to the admin server is not specified.
System action
None
System administrator response
Enter the port number used to connect to the admin server.
To be started in Systemwalker Centric Manager failed. Parameters are insufficient or parameters are not correct.
Explanation
The client could not be started in Systemwalker Centric Manager because parameters for the client program are insufficient or parameters are incorrect.
System action
The client start in Systemwalker Centric Manager is stopped.
System administrator response
Refer to "10.2.4.1 Setup from Systemwalker Centric Manager Administrative Client" or "12.4.1 Systemwalker Centric Manager Window Linkage Command (mpaplreg)" in the ETERNUS SF Storage Cruiser User's Guide, and review the setting.
