Command terminated normally.
Explanation
The command was executed successfully.
System Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The system terminates the access path diagnosis.
System Administrator Corrective Action
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 Response
The system terminates the processing upon the detection of a path error during access path diagnosis
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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.)
The access path setting was executed normally.
Explanation
Access path setting was performed normally.
System Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
New device(s) was/were detected.
Explanation
A new device was detected.
System Response
The command is completed normally.
System Administrator Corrective Action
Register the device for management.
The selected IP device cannot be found.
Explanation
One of the following has occurred:
The device of the specified IP address could not be detected on the device registration operation.
The IP address or the SNMP community name could not be changed on the changing operation.
System Response
The command is completed normally.
System Administrator Corrective Action
Check whether the specified IP address or the SNMP community name and network environment settings for the Managed device and the settings for detecting the Managed device are valid.
Refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command
System Administrator Corrective Action
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 Response
Partially completes the command
System Administrator Corrective Action
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
One of the following has occurred:
The device that responds to the specified IP address already exists in the database.
The device that responds to the specified IP address has been already registered with the IP version different from the specified IP address.
System Response
The command is completed normally.
System Administrator Corrective Action
Check whether the entered IP address is valid.
This message is also output if device registration with an IP version different from the IP address specified was cancelled before completion sometime in the past. In this case, finish the device registration with the IP version which is different from the specified IP address for now. And then, delete the target device and re-execute the command.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Deleting the device terminated normally.
Explanation
The registered device was deleted successfully.
System Response
The command was executed successfully.
System Administrator Corrective Action
No action is required.
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 Response
The command was executed successfully.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command was processed normally.
System Administrator Corrective Action
No action is required.
The selected IP Fujitsu RAID device cannot be found.
Explanation
A Fujitsu RAID device having the specified IP address could not be detected.
System Response
The command was processed normally.
System Administrator Corrective Action
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 Response
The command was processed normally.
System Administrator Corrective Action
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 Response
The command was processed normally.
System Administrator Corrective Action
No action is required.
Processing to switch is skipped. :
SKIP_SWITCH_NAME="%name"
Explanation
No processing was performed for the switch.
Parameters
%name : Switch name
System Response
The system terminates the command processing.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command was executed successfully.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
(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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
No action is required.
(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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
No action is required.
(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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Ends the processing normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
No action is required.
(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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The system terminates the command processing.
System Administrator Corrective Action
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 Response
Ends the processing normally.
System Administrator Corrective Action
No action is required.
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 Response
Ends the processing normally.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
A critical problem was found in DB of administrative server.
Explanation
Fatal inconsistent data was detected in the CIM database.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
An inconsistency was detected in DB of administrative server.
Explanation
Inconsistent data was detected in the CIM database.
System Response
Partially completes the command.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
A CIM access error was detected.
Explanation
A CIM error was detected during CIM database access.
System Response
The system terminates processing.
System Administrator Corrective Action
One of the reasons for this message being output may be that the CIM data area is full (/var/opt/FJSVssmgr/current/opencimom/logr).
Use the "df -k /var/opt/FJSVssmgr/current/opencimom/logr" command to check whether the disk is full.
If the disk is not full, re-execute processing.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Input value is invalid. An Internal Program inconsistency was detected.
Explanation
An unexpected value was detected as an input parameter.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Disk storage system. Please correspond either as follows when IP address on the Slave CM side is set with ETERNUS Disk storage system.
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 Management 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".
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The input IP address or device name is incorrect.
Explanation
The format of the input IP address or device name is invalid.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
TargetID cannot be changed.
Explanation
An existing target ID that was set in the server node during access path setting cannot be changed.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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 "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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 "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Check whether the HBA and drivers function normally. Also check whether the SNIA HBA API library is installed normally. For SNIA HBA API library installation, refer to "SNIA HBA API library installation (HP-UX environment excluded)" in the ETERNUS SF Installation and Setup Guide.
When the HBA is changed, refer to "Access path inheritance" in the ETERNUS SF Storage Cruiser Operation Guide and perform the appropriate action.
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 Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Restore the target server node and HBA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Restore the target storage to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Restore the target server node and storage to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target HBA and storage to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target server node, HBA, and storage to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target server node and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target HBA and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target server node, HBA, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target storage and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the target server node, storage, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Restore the HBA, storage, and CA to the normal status and then re-execute the operation.
For access path settings, refer to "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
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 "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation Guide.
The storage affinity of one HBA is WWNN_BINDING, It is not appropriate for adding to the server node.
Explanation
World Wide Node Name (WWNN) binding is defined for the server node HBA. Because the management unit of this program is World Wide Port Name (WWPN), registration of the relevant server node is restricted.
System Response
The system terminates processing.
System Administrator Corrective Action
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 World Wide Port Name (WWPN), registration of the relevant server node is restricted.
System Response
The system terminates processing.
System Administrator Corrective Action
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 World Wide Port Name (WWPN), registration of the relevant server node is restricted.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
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 "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 "Device is not possible to communicate" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For details of the settings, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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. Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For setting procedures, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
Set the HBA and CA Fibre Channel port connection types to Fabric connection (N-type port). For setting procedures, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
A fatal error occurred during the storage operation.
Explanation
An error was detected during command processing for the storage.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
Setting for the server node was executed but other processing was interrupted.
System Administrator Corrective Action
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 Response
Setting for the server node was executed but other processing was interrupted.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
Setting on the server node was executed but processing for the storage was interrupted.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
Setting for the server node was executed but processing for the storage was interrupted.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Fatal error occurred during switch operation.
Explanation
An error was detected during the execution of this operation on the switch.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
Executes the setting on the server node but interrupts the processing on the switch.
System Administrator Corrective Action
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 Response
Setting for the server node was executed but processing for the switch was interrupted.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
Executes the processing for the server node but interrupts that for the switch.
System Administrator Corrective Action
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 Response
Executes the processing on the server node but interrupts that on the switch.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
Executes the processing for the storage but interrupts that for the switch.
System Administrator Corrective Action
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 Response
Executes the processing for the storage but interrupts that for the switch.
System Administrator Corrective Action
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 Response
Executes the processing for the storage and server node but interrupts that for the switch.
System Administrator Corrective Action
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 Response
Executes the processing for the storage and server node but interrupts that for the switch.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
Executes this operation for the server node but interrupts all other processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unable to obtain Storage Affinity Information. This operation could not be processed.
Explanation
Storage Affinity Information from the HBA could not be obtained.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System Response
The system terminates processing.
System Administrator Corrective Action
This event occurs if the free disk space of the Management Server is insufficient. Check the free disk space.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Server node agent is already communicating with another manager.
Explanation
The Agent of the target server node is busy communicating with another Management Server.
System Response
The system terminates processing.
System Administrator Corrective Action
Re-execute the processing later.
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program Error occurred.
Explanation
An internal error was detected in the program.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
SNMP error occurred in communication with server node.
Explanation
An SNMP error occurred during communication with the server node.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the destination switch or hub on which the error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the specified switch or hub
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the destination switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
Check the applicable switch or hub for errors. Alternatively, check the LAN environment for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the destination switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
No response from switch/hub. The target device address: %IP_ADDRESS
Explanation
The specified switch or hub was not found.
Parameters
%IP_ADDRESS : IP address of the specified switch or hub
System Response
The system terminates processing.
System Administrator Corrective Action
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 that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the specified switch or hub
System Response
The system terminates processing.
System Administrator Corrective Action
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 : SysName that is set for the switch or hub to which login failed
%IP_ADDRESS : IP address of the switch or hub to which login failed
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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 : SysName that is set for the switch or hub to which login failed
%IP_ADDRESS : IP address of the switch or hub to which login failed
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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
or
Parse error response for switch. The target device address: %SYS_NAME:%IP_ADDRESS
Explanation
Analysis of the execution results of the TELNET/SSH command issued to the switch or hub failed.
Parameters
%SYS_NAME : SysName that is set for the switch or hub to which login failed
%IP_ADDRESS : IP address of the switch or hub to which login failed
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Command failure on telnet for switch/hub. The target device address: %IP_ADDRESS
or
Control failure for switch. The target device address: %IP_ADDRESS
Explanation
Execution of the TELNET/SSH command issued to the switch or hub failed.
Parameters
%IP_ADDRESS : IP address of the switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 statuses of all the cascade-connected fibre channel switches are normal.
If the above are not applicable, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 : IP address of the switch in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the switch in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 World Wide Port Name (WWPN) zone settings.
Parameters
%ZONES : Zone setting that could not be deleted
%IP_ADDRESS : IP address of the switch in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the switch or hub in which an error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
Firmware not supported Storage Cruiser is used for the target device.
Contact your Fujitsu customer engineer or system engineer because patches need to be applied to 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 : IP address of the SNMP trap send destination that could not be registered
%IP_ADDRESS : IP address of the switch or hub in which the error occurred
System Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the device to be processed
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unexpected Interrupt occurred during processing. The target device address: %IP_ADDRESS
Explanation
An interrupt occurred during processing.
Parameters
%IP_ADDRESS : IP address of the device to be processed
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unexpected error occurred. %IP_ADDRESS
Explanation
An unexpected error occurred.
Parameters
%IP_ADDRESS : IP address of the device to be processed
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program Error occurred.
Explanation
An internal program error was detected.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
SNMP error occurred on storage communication.
Explanation
An SNMP error occurred during communication between the storage and server.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems.
When the target device is an ETERNUS Disk storage system, the following environment settings may not be correct. For details, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 storage system, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
Socket error occurred on storage communication.
Explanation
A socket error occurred during communication between the storage and server.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems.
Selected storage is not found.
Explanation
The specified storage is not found.
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the specified storage is connected to the LAN.
When the target device is an ETERNUS Disk storage system, the following environment settings may not be correct. For details, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 storage system, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
Network I/O Error on storage communication.
Explanation
An I/O error occurred during communication with the storage.
System Response
The system terminates processing.
When using Storage Cruiser:
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Check the LAN environment for problems.
Timeout Error on storage communication.
Explanation
A time-out occurred during communication with the storage.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems.
Poor and slow communications can cause a timeout when one communication mode is set to "Auto Negotiation" and the other is set to "Full (all dual)".
No response from storage.
Explanation
A required storage was not found.
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the specified storage is connected to the LAN.
When the target device is an ETERNUS Disk storage system, the following environment settings may not be correct. For details, refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 storage system, which uses the SNMP protocol for communication, may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
This device is not supported.
Explanation
Management of the specified IP device is not supported.
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the specified IP device is valid.
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 (This may not be displayed depending on the storage device type.)
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Logout the process logged into the target device, and then re-execute it. If the user fails to explicitly log out from ETERNUS Web GUI after login, such as when the user terminates the Web server while logging into ETERNUS Web GUI, ETERNUS Web GUI remains logged in. In this case, login to ETERNUS Web GUI 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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
No root password is registered in storage.
Explanation
The root password is not set in the storage.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
If the specified information is correct, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program Error: (Invalid CA Logical ID)
Explanation
An internal program error was detected. (An invalid CA ID was specified. )
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing. The setting for the storage has not been changed.
System Administrator Corrective Action
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 Response
The system terminates processing. The setting for the storage is unclear.
System Administrator Corrective Action
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 Response
The system terminates processing. The setting for the storage has been partially changed.
System Administrator Corrective Action
Re-enter the command.
Incorrect Storage Configuration.
Explanation
A storage internal configuration information error was detected.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Selected path is using by other application
Explanation
The diagnostic path is being used (open) by another application.
System Response
The system terminates processing.
System Administrator Corrective Action
Re-enter the command.
Administrative server detected error for selected path
Explanation
An error occurred during diagnosis of the selected path.
System Response
The system terminates processing.
System Administrator Corrective Action
Re-enter the command.
Manager cannot diagnose access path
Explanation
Path diagnosis cannot be executed.
System Response
The system terminates processing.
System Administrator Corrective Action
Re-enter the command.
Path error detected on server node.
Explanation
The Agent detected a path error.
System Response
The system terminates processing.
System Administrator Corrective Action
Re-enter the command.
Server node environment error detected. detail: [s1]
Explanation
An environment error was detected on the Management Server.
Parameters
s1 : Detail message output by the Agent
System Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
Invalid information on server node. detail: [s1]
Explanation
Invalid information was detected on the Management Server.
Parameters
s1 : Detail message output by the Agent
System Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
Invalid parameter at SNMP command is detected on server node. detail: [s1]
Explanation
An invalid value was detected during communication with the Management Server.
The operator made a specification mistake, or the LAN environment may have a problem.
Parameters
s1 : Detail message output by the Agent
System Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
Invalid operation server node. detail: [s1]
Explanation
The Agent detected an operation error.
Parameters
s1 : Detail message output by the Agent
System Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
System error occurred on server node. detail: [s1]
Explanation
A system error was detected.
Parameters
s1 : Detail message output by the Agent
System Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
Internal Program Error occurred on server node.
Explanation
The Agent detected a program internal error.
System Response
The system terminates processing.
System Administrator Corrective Action
If the sanadmsh chtraprcvip command is executed, check the argument and re-execute the command.
If you still have a problem or other cases, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Apply countermeasures as described in the detail message output by the Agent. For an explanation of the detail message, refer to its message in this manual.
Internal Program error occurred.
Explanation
An internal program error was detected.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Timeout occurred to startup of snmp trap handler thread.
Explanation
A thread start time-out occurred when the SNMP trap handler was started.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
unable to find SNMP library.
Explanation
A library required for the SNMP trap handler was not detected.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 : IP address of the device to be processed
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the device with the relevant IP address is supported by this software.
If the device is supported, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The device does not support Beacon function,
Explanation
The specified device does not support the beacon function.
System Response
None
System Administrator Corrective Action
No action is required.
The instance is already in DB of SANmgr.
Explanation
The specified device or instance already exists in the database.
System Response
None
System Administrator Corrective Action
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.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Disk storage system. Please correspond either as follows when IP address on the Slave CM side is set with ETERNUS Disk storage system.
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 Management 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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
Could not find any accessible switch.
Explanation
No enabled switch is found. Check the device monitoring status.
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 "Access path setting has failed" in the ETERNUS SF Storage Cruiser Operation 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 Response
The system terminates processing.
System Administrator Corrective Action
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 Management Server could not be stopped.
System Response
None
System Administrator Corrective Action
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 operation, or a program internal error (abnormal input value) may have occurred.
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Check whether multiple Web Consoles were used and "Delete device" was executed from another Web Console.
If not executed, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing. The setting for the storage is unclear.
System Administrator Corrective Action
Re-enter the command.
Agent version is incorrect.
Explanation
An error occurred during the CGI processing from the Manager to the storage.
System Response
The system terminates processing. The setting for the storage is unclear.
System Administrator Corrective Action
Re-enter the command.
HBA type is incorrect.
Explanation
An error occurred during CGI processing from the Manager to the storage.
System Response
The system terminates processing. The setting for the storage is unclear.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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.
The iSCSI Host has already been registered. Processing is terminated because there was setting different from a specified content.
Explanation
The specified iSCSI host has already been registered. The specified iSCSI host setting is different from the registered one.
System Response
The system terminates processing.
System Administrator Corrective Action
The content of the iSCSI host setting cannot be changed. Check the content of the iSCSI host setting, and then re-execute.
iSCSI Port has another affinity group definition for selected iSCSI Host.
Explanation
The specified iSCSI port already has another Affinity group setting for the selected iSCSI host.
System Response
The system terminates processing.
System Administrator Corrective Action
If you want to change the Affinity group setting, delete Affinity groups that have already been set, and then re-execute.
More than one iSCSI Port has a same iSCSI Name and same IP Address.
Explanation
At least two iSCSI ports have the same iSCSI name and IP address.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the iSCSI port setting of each device.
The specified HostResponse number does not in the specified storage device.
Explanation
The specified HostResponse number does not exist in the specified storage device.
System Response
The system terminates processing.
System Administrator Corrective Action
Specify the HostResponse number that is set in the storage device and then re-execute.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Specified HBA WWPN is set to a different HostResponse number.
Explanation
The specified HBA WWPN is set to a different HostResponse number.
System Response
The system terminates processing.
System Administrator Corrective Action
Specify the HostResponse number that is set in the specified HBA WWPN and then re-execute.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
It failed in the setting or the information acquisition of the storage device.
Explanation
Setting or information collection failed for the storage device.
System Response
The system terminates processing.
When using Storage Cruiser:
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Check for hardware abnormality in the storage device.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
A communication error occurred with the storage device.
Explanation
A communication error occurred with the storage device.
System Response
The system terminates processing.
When using Storage Cruiser:
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
Check the system environment LAN for possible trouble.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing after changing the access path settings for some devices.
System Administrator Corrective Action
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 Response
The system terminates processing after changing the access path settings for some devices.
System Administrator Corrective Action
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 Response
Command processing was stopped because an error was detected during processing.
System Administrator Corrective Action
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 Response
Command processing was stopped because an error was detected during processing.
System Administrator Corrective Action
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 Response
Command processing was stopped because an error was detected during processing.
System Administrator Corrective Action
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 Response
Command processing was stopped because an error was detected during processing.
System Administrator Corrective Action
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 Response
Command processing was stopped because an error was detected during processing.
System Administrator Corrective Action
Contact Fujitsu Technical Support.
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 World Wide Port Name (WWPN) zone with one-to-one zone setting.
Parameters
%ZONES : Zone setting that could not be deleted
System Response
The system terminates processing.
If the access path deletion option has been specified when deleting a device, the device has been deleted properly but the access path deletion processing has been interrupted.
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
No action is required.
The WWPN of source and destination is SAME. Command terminated.
Explanation
The move source WWPN matches the move destination WWPN. Processing was interrupted.
System Response
None
System Administrator Corrective Action
No action is required.
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 ETERNUS Web GUI to set host affinity directly.
System Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
No action is required.
The device does not support Port Beacon function.
Explanation
The specified device does not support the port beacon function.
System Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
Source and Destination WWPN is same. Command processing is terminated.
Explanation
The inheritance source and destination WWPNs are the same. Processing was interrupted.
System Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
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 "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation 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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
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 environment proper procedures (for example, commands such as "disks -C") may not have performed, or an internal program error may have occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
If the host node is a Solaris environment, then check procedures such as access path definition. For details, refer to "Access Path Management" in the ETERNUS SF Storage Cruiser Operation Guide.
If the host node is not a Solaris environment or this issue is not solved after taking measures according to the paragraph above, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
No action is required.
Unexpected error has occurred.
Explanation
An unexpected exception occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Network communication error occurred. The target device address:
Explanation
A network communication error occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unable to find the device. The target device address:
Explanation
The specified device was not found.
System Response
The system terminates processing.
System Administrator Corrective Action
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 storage system, the following environment settings may not be correct.
Refer to "Environment Configuration" in the ETERNUS SF Storage Cruiser Operation Guide for details.
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 storage system 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 Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
Network I/O error occurred. The target device address:
Explanation
An I/O error occurred during network communication.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems. Or, check the target device for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Timeout error occurred in communication with the device. The target device address:
Explanation
A time-out occurred during communication with the specified device.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems. Alternatively, check the target device for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
No response from the device. The target device address:
Explanation
No response was received from the specified device.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the LAN environment for problems. Alternatively, check the target device for problems.
In some cases, the community name of a device that uses the SNMP protocol for communication may be set to something other than "public" and the community name of the Management 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 Management Server. Try the operation again after changing the community name of the target device on the Web Console.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
SNMP protocol error occurred. The target device address:
Explanation
An SNMP protocol error occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unrecovered SNMP error occurred. The target device address:
Explanation
An unrecoverable SNMP error occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The device is not supported by the administrative server. The target device address:
Explanation
The specified device is not supported.
System Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unexpected error occurred. The target device address:
Explanation
An unexpected error occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
None
System Administrator Corrective Action
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 "sanma.conf Parameter" in the ETERNUS SF Storage Cruiser Operation 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 cancelled.
System Response
The system closes the command.
System Administrator Corrective Action
No action is required.
syntax error. detail=%DETAIL
In the case that this message is displayed with the execution of the command:
The command syntax is invalid. 'usage' is displayed.
%DETAIL : One of the following is displayed:
Strings Displayed in %DETAIL | Error Cause |
|---|---|
command is not specified. | The command was not specified. |
command[value] is invalid. | The specified command (value) is invalid. |
parameter is invalid. | The specified parameter is invalid. |
option[value] is invalid or duplicated. | The specified option [value] is invalid. |
[value] is invalid value or format. | The value or format of the option [value] is invalid. |
The system displays 'usage' and terminates processing.
Review the command syntax and then re-executes the operation.
In the case that this message is displayed with the operations of the Web Console:
There is an error with the details configured with the Web Console.
%DETAIL : The following is displayed:
Strings Displayed in %DETAIL | Error Cause |
|---|---|
[value] is invalid value or format. | There is an error with the details configured with the Web Console. |
The system terminates processing.
Perform the operation again after reviewing the details configured with the Web Console.
In the case that this message is displayed when creating a volume, it is possible that the number exceeds the maximum number of volumes that can be created at once with this product. For the maximum number of volumes that can be created at once with this product, refer to the following manual:
When using Express:
"Operations related to Volume" in the ETERNUS SF Express Operation Guide
When using Storage Cruiser:
"Volume Management" in the ETERNUS SF Storage Cruiser Operation Guide
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unexpected error has occurred.
Explanation
An unexpected exception occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
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 you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
Partially completes the command.
System Administrator Corrective Action
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 Response
The command is completed normally.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Please remove the following causes. Afterwards, please operate it again.
When the server node equipped with the specified HBA is registered in this software
Please start this server node when an access path is set up. Moreover, please remove the cause when the monitoring status of HBA is not normal.
Please stop this server node when an access path is deleted.
Please register when storage is not registered in this software.
Please remove the cause when the status of storage is not normal.
Authentication failure may be occurred because the number of sessions of SSH communication to storage has reached the upper limit. In that case, set the user name and password again with the Web Console.
If the password of either of the following devices is changed, set the correct user name and password that have been set in the device with the Web Console.
Device that relates to access path setting
Device connected with the device that relates to access path setting
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Exit Performance Manager.
Explanation
Confirm whether or not to end performance management.
System Response
If OK is clicked, performance management ends.
System Administrator Corrective Action
To end performance management, click OK. Otherwise, click Cancel.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
When OK 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 Corrective Action
To create a configuration file, click OK. Otherwise, click Cancel.
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 Response
Creates a configuration file, updates the device tree, and deletes the displayed performance graph.
System Administrator Corrective Action
No action is required.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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.
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 Response
If an error occurs during performance monitoring, processing is retried and continued. In other cases, processing is terminated.
System Administrator Corrective Action
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 Response
If an error occurs during performance monitoring, processing is retried and continued. In other cases, processing is terminated.
System Administrator Corrective Action
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 or the device which is executing Automated Storage Tiering.
Parameters
{0} : IP address of the target device
System Response
If an error occurs during performance monitoring or the execution of Automated Storage Tiering, processing is retried and continued. In other cases, processing is terminated.
System Administrator Corrective Action
Check the target device or network environment for errors.
Or, check whether the account information of the target device has been changed since the initial registration.
An address {0} is wrong.
Explanation
This message indicates that the specified address is invalid for the IP address.
Parameters
{0} : Specified address
System Response
The system terminates processing.
System Administrator Corrective Action
Specify a valid IP address.
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 Response
The system terminates processing.
System Administrator Corrective Action
Check the device or network environment for errors.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unable to find the performance configuration file {0}.
or
Unable to find the system 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} : Performance management definition file name
System Response
The system terminates processing.
System Administrator Corrective Action
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 "Command References" in the ETERNUS SF Storage Cruiser Operation Guide.)
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unable to create the performance configuration file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
or
Unable to create the 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} : Performance management definition file name
System Response
The system terminates processing.
System Administrator Corrective Action
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.
or
Unable to read the 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} : Performance management definition file name
System Response
The system terminates processing.
System Administrator Corrective Action
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 "Command References" in the ETERNUS SF Storage Cruiser Operation Guide.)
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Unable to write the performance configuration file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
or
Unable to write the 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} : Performance management definition file name
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the file system is write-protected or check the size of the file system, and re-execute the processing.
Unable to find a config XML file {0}.
Explanation
The configuration information file of the performance monitoring device could not be found.
Parameters
{0} : Configuration information file name
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Updating configuration information" in the ETERNUS SF Storage Cruiser Operation Guide to update the configuration information file.
Unable to create a config XML file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
The configuration information file of the performance monitoring device could not be created.
Parameters
{0} : Configuration information file name
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the file system is write-protected or check the size of the file system. Then, refer to "Updating configuration information" in the ETERNUS SF Storage Cruiser Operation Guide to update the configuration information file.
Unable to write a config XML file {0}. Please check write permission of the filesystem or the capacity of the filesystem.
Explanation
The configuration information file could not be created because an error occurred while the configuration information of the device was being saved to a file.
Parameters
{0} : Configuration information file name
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the file system is write-protected or check the size of the file system. Then, refer to "Updating configuration information" in the ETERNUS SF Storage Cruiser Operation Guide to update the configuration information file.
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. Therefore, this message does not indicate an error if the 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} : Performance information file name
System Response
The system continues processing.
System Administrator Corrective Action
No action is required.
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} : Performance information file name
System Response
The system terminates performance monitoring.
System Administrator Corrective Action
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.
or
Unable to read a performance data file {0}. The file does not exsist or the contents of the file are 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} : Performance information file name
System Response
The system terminates performance graph display.
System Administrator Corrective Action
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, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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} : Performance information file name
System Response
The system terminates performance monitoring.
System Administrator Corrective Action
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 performance monitoring.
Explanation
The performance of the specified device cannot be monitored because the specified device does not support the performance monitoring function.
Parameters
{0} : Configuration information file name
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the correct device is specified.
Refer to "Support levels" in the ETERNUS SF Storage Cruiser Operation Guide to check whether the specified device supports the performance monitoring function.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
A device (class {0}) is not supported by this program.
or
A device (class {0}) is not supported.
Explanation
The performance monitoring function does not support the specified device.
Parameters
{0} : Name of class file that tried to be loaded to control the specified device
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the correct device is specified.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
An unexpected error occurred.
Explanation
This message indicates that an unexpected error such as a program internal error occurred.
System Response
The system terminates processing.
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Stop threshold monitoring and then stop performance monitoring.
The LogicalVolume within specified range does not exist.
Explanation
The logical volume does not exist within the performance monitoring range (from minimum LUN_V to maximum LUN_V).
System Response
The system terminates processing.
System Administrator Corrective Action
Specify the range where the logical volume exists.
When the device configuration is changed, refer to "Updating configuration information" in the ETERNUS SF Storage Cruiser Operation Guide to update the configuration information file.
The definition file has been reloaded.
Explanation
The performance control function definition file perf.conf has been reloaded.
System Response
The performance control function definition file perf.conf has been reloaded and reflected dynamically.
System Administrator Corrective Action
No action is required.
It failed on the reload of the definition file.
Explanation
The performance control function definition file perf.conf has failed.
System Response
The system terminates processing.
System Administrator Corrective Action
Follow the detailed messages.
If detailed messages are not displayed, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 or IP address of the target device
System Response
Under performance monitoring, retries processing until another login ends so that the processing can continue. In other cases, terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Check the target device for errors, and then re-execute the processing.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
Under performance monitoring, processing is retried until another login ends, after which the processing continues. In other cases, the processing is terminated.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Check the target device for errors, and then re-execute the processing.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
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 Response
The system terminates processing.
System Administrator Corrective Action
Check the target device for errors, and then re-execute the processing.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Internal Program error occurred.
Explanation
An internal program error was detected.
System Response
The system terminates processing.
System Administrator Corrective Action
Contact Fujitsu Technical Support.
No access path has been configured.
Explanation
Access path setting failed.
System Response
The system terminates processing.
System Administrator Corrective Action
The zoning operation of switch supports only one-to-one correspondent World Wide Port Name (WWPN) zone. If the zone to be operated is not one-to-one correspondent WWPN zone, log in the switch directly, and adjust the zoning setting manually.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Failed.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
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 Management Server is restated or when cluster switching occurs on the Management Server.
Check whether OpenCIMOM is active. If OpenCIMON is down, restart it in accordance with the description in "Command References" in the ETERNUS SF Storage Cruiser Operation Guide.
The CIM data area is full.
Check whether the disk is full by the following method.
Platform of Manager | Action Plan |
|---|---|
Windows | Confirm the property information of the disk where CIM data base is stored. |
Solaris, | 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 "Command References" in the ETERNUS SF Storage Cruiser Operation Guide).
If the command or service confirms that OpenCIMOM is active or after OpenCIMOM is restarted, close the Web Console and restart it.
If no error can be found by the above operations, other causes must be assumed. Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
An invalid parameter is passed to a method.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
An invalid class is specified.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The specified element cannot be found.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The specified element already exists.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
The memory is low.
Explanation
An OpenCIMOM internal error was detected.
System Response
None
System Administrator Corrective Action
Restart the OpenCIMOM daemon and restart this software.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
unable to find the equipment/adapter.
Explanation
A required device or adapter is not found.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
no such association.
Explanation
The specified association is not found.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
failed to serialize the object.
Explanation
Object serialization failed.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
failed to create a new instance.
Explanation
Instance generation failed.
System Response
None
System Administrator Corrective Action
Refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
%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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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% : Server node name
%OSName% : OS name
%OSVersion% : OS version
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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, perform Reload Conf. on the Web Console 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 Management Server node OS
%OSVersion% : Version of Management Server node OS
%IPAddress% : Management Server node IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Please confirm connected situation of the FC cable.
If you still have a problem, contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
%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 Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%itemDegradeMessage% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
A component failure was detected.
The unit trap message is output without any change.
Parameters
%itemDegradeMessage% : Failure content
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%batteryExpirationMessage% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
The battery requires replacement.
The unit trap message is output without any change.
Parameters
%batteryExpirationMessage% : Battery expiration information
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%partBrokenMessage% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
A possible failure was detected.
The unit trap message is output without any change.
Parameters
%partBrokenMessage% : Possible failure content
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%sensorStatusChangeMessage% in %SysName%(%ProductID%[%IPAddress%])
Explanation
State change of thermal sensor or voltage sensor was detected.
The unit trap message is output without any change.
Parameters
%sensorStatusChangeMessage% : Content of change in state of sensor
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%maintenanceInfo% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
Maintenance information was received.
The unit trap message is output without any change.
Parameters
%maintenanceInfo% : Maintenance information
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
%automaticRestorationInfo% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
Auto recovery notification was received.
The unit trap message is output without any change.
Parameters
%automaticRestorationInfo% : Auto recovery information
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
Acute Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SysName%(%ProductID%[%IPAddress%])
Explanation
A failure that causes the entire subsystem to stop was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Serious Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SysName%(%ProductID%[%IPAddress%])
Explanation
A failure that causes the failed part to stop was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Moderate Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SysName%(%ProductID%[%IPAddress%])
Explanation
A partial failure was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Service Event (REFCODE=%xxxxx% Parts=%yyyyy%) in %SysName%(%ProductID%[%IPAddress%])
Explanation
A minor failure was detected.
Parameters
%xxxxx% : Message code
%yyyyy% : Part code
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
System down occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A local controller failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Drive blocking occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A data drive blockage was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Fan failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A fan alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Power supply failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A DC power failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Battery failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A battery alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Cache memory failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A cache memory blockage was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
UPS failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A UPS alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
AC line or inbox failure occurred in %SysName%(%productID%[%IPAddress%])
Explanation
An Inbox Failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Cache backup circuit failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A battery charging circuit alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Other controller failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A remote controller blockage was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Warning occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
The warning status of the disk array was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Spare drive failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A spare drive blockage was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Enclosure controller failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
An ENC alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Loop failure occurred in %SysName%(%ProductID%[%IPAddress%])
Explanation
A loop failure alarm was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
%EventMessage% in %SysName%(%ProductID%[%IPAddress%]).
Explanation
An event message was detected.
The unit trap message is output without any change.
Parameters
%EventMessage% : Message
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
If you still have a problem, contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The media error occurred. (Barcode label: %value%) in %SysName%(%productID%[%IPAddress%])
Explanation
A drive media error was detected.
Parameters
%value% : Version and level
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The drive unit%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A drive error was detected.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The drive unit%value% became offline in %SysName%(%productID%[%IPAddress%])
Explanation
The drive went offline.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The drive unit%value% needs cleaning in %SysName%(%productID%[%IPAddress%])
Explanation
The drive needs cleaning.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The drive unit%value% Link Down occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A drive link down occurred.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The adapter%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A Fibre Channel port failure was detected.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The barcode reader error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A barcode reader failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The CAS unit%value% error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A cartridge access station (CAS) failure was detected.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The battery unit error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A battery failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The library FAN(1) error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A fan failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The library FAN(2) error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A fan failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The library system error occurred. (FSC=%code%) in %SysName%(%productID%[%IPAddress%])
Explanation
A library failure was detected.
Parameters
%code% : Fault symptom code
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The front door opened on the library system in %SysName%(%productID%[%IPAddress%])
Explanation
The front door is open.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Check the state of the front door.
The library system became offline in %SysName%(%productID%[%IPAddress%])
Explanation
The library is offline.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Check the state of the library.
The CIC sensor error occurred in %SysName%(%productID%[%IPAddress%])
Explanation
A CIC sensor failure was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The adapter%value% Link Down occurred in %SysName%(%productID%[%IPAddress%])
Explanation
The Fibre Channel port link is down.
Parameters
%value% : Unit number
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
No install adapter card in library system in %SysName%(%productID%[%IPAddress%])
Explanation
A required Fibre Channel port is not mounted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Read Data Error in %SysName%(%ProductID%[%IPAddress%])
Explanation
The drive read error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Write Data Error in %SysName%(%ProductID%[%IPAddress%])
Explanation
The drive write error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Read or Write Data Error in %SysName%(%ProductID%[%IPAddress%])
Explanation
The read or write data error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Detected Faulty Media in %SysName%(%ProductID%[%IPAddress%])
Explanation
Drive media error was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Read Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The tape or drive error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Write Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The tape or drive error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Reach end of Media in %SysName%(%ProductID%[%IPAddress%])
Explanation
Use of media reached the limit.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Not Data Grade Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
This tape is not data grade.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Attempted Backup to Write-protected Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
Writing was performed to write-protected media.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Tape Drive is in use in %SysName%(%ProductID%[%IPAddress%])
Explanation
Since a drive is in use, a cartridge cannot be taken out.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Attempted Backup/Restore To Cleaning Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
Backup/Restore to cleaning tape was performed.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Unsupported Media in %SysName%(%ProductID%[%IPAddress%])
Explanation
Unsupported media was inserted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Detected Snapped Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
Snapped tape was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Detected Snapped Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
Snapped tape was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device without taking out a tape.
Memory Chip in Cartridge Failure in %SysName%(%ProductID%[%IPAddress%])
Explanation
Memory tip error in cartridge was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Tape Cartridge was ejected in %SysName%(%ProductID%[%IPAddress%])
Explanation
The tape cartridge was ejected during read or write processing.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Detected Read-only Media in %SysName%(%ProductID%[%IPAddress%])
Explanation
Read-only media was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Detected Currupted Directory On Tape in %SysName%(%ProductID%[%IPAddress%])
Explanation
Corrupted directory on tape cartridge was detected. The performance of file reference may fall.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
Detected Worn Out Media in %SysName%(%ProductID%[%IPAddress%])
Explanation
Worn out Media was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please exchange media.
Tape Device Needs Cleaning in %SysName%(%ProductID%[%IPAddress%])
Explanation
Tape device needs cleaning.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please perform cleaning of a tape device.
Drive Needs Routine Cleaning in %SysName%(%ProductID%[%IPAddress%])
Explanation
Tape device needs routine cleaning.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please perform cleaning of a tape device.
Detected Worn Out Cleaning Cartridge in %SysName%(%ProductID%[%IPAddress%])
Explanation
Worn out cleaning cartridge was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please exchange the cleaning cartridge in a tape drive.
Detected Invalid Cleaning Cartridge in %SysName%(%ProductID%[%IPAddress%])
Explanation
Invalid cleaning cartridge was detected.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please exchange for an effective cleaning cartridge.
Request retention in %SysName%(%ProductID%[%IPAddress%])
Explanation
The request of processing was suspended.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please refer to the manual attached to the device.
A Redundant Interface Port Failed in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the interface port where it overlaps on a tape drive.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Fan Failed in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the fan on a tape drive.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Power Supply Failed in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the power supply where it overlaps on a tape drive.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please replace unusual power supply with normal power supply. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Power Consumption is outside the specified range in %SysName%(%ProductID%[%IPAddress%])
Explanation
Power consumption of a tape drive is outside the specified range.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Require Preventative Maintenance in %SysName%(%ProductID%[%IPAddress%])
Explanation
Preventative maintenance of a tape drive is required.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please perform preventative maintenance of a tape drive.
Drive Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Drive hardware error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please take out a tape from the tape drive and reset the drive. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Drive Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Drive hardware error occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reboot the tape drive and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Server node Interface Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error has occurred in the server node interface.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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 a Fujitsu customer engineer responsible for the device.
Eject Media Request in %SysName%(%ProductID%[%IPAddress%])
Explanation
It is the extraction request of media.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please put in a tape again and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Firmware Download Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Download of a firmware failed.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please use an effective firmware and re-execute.
Humidity Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The state in a tape drive exceeded humidity specification.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Temperature Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The state in a tape drive exceeded temperature specification.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Voltage Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The voltage to a tape drive is unusual.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Tape Device Predicted to Fail in %SysName%(%ProductID%[%IPAddress%])
Explanation
A hardware error of a tape drive is predicted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Drive Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
A hardware error is predicted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
When the diagnostic test was carried out and abnormalities are detected, contact a Fujitsu customer engineer responsible for the device.
Autoloader Communications Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Communication between AutoLoader and a tape drive has an error.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reboot AutoLoader and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Detected Stray Tape In Autoloader in %SysName%(%ProductID%[%IPAddress%])
Explanation
According to a former hardware error, a tape is in AutoLoader.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please insert an empty magazine in a drive. Please reboot AutoLoader, when a problem is not solved. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Autoloader Mechanism Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred in AutoLoader.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Autoloader Door Open in %SysName%(%ProductID%[%IPAddress%])
Explanation
The door of AutoLoader is open.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please remove an obstacle from the door of AutoLoader and put in a magazine. Please reboot AutoLoader, when a problem is not solved. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Autoloader Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of hardware may have occurred in AutoLoader.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reboot AutoLoader. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Autoloader Cannot Operate Without Magazine in %SysName%(%ProductID%[%IPAddress%])
Explanation
AutoLoader cannot work without a magazine.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please insert a magazine in AutoLoader and re-execute.
Autoloader Predicted to Fail in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in AutoLoader are predicted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Media Statistics have been Lost in %SysName%(%ProductID%[%IPAddress%])
Explanation
Media statistics have been lost.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Tape Directory has been currupted in %SysName%(%ProductID%[%IPAddress%])
Explanation
The tape directory was destroyed.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Tape just unloaded could not write its system area in %SysName%(%ProductID%[%IPAddress%])
Explanation
Since the tape is unloaded, it was not able to write to the system area normally.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please insert a tape and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Could not read System Area in %SysName%(%ProductID%[%IPAddress%])
Explanation
System Area was not able to be normally read at the time of loading.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Start of Date Not Found in %SysName%(%ProductID%[%IPAddress%])
Explanation
The start of the date in a tape was not able to be found.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please use the tape of an effective format and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Drive Communications Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Communication between a library mechanism and a drive is unstable.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reboot a library. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Changer Mechanism Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred to the library mechanism.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Library Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reset a library and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Library Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please reboot a library and re-execute. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Library Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a library have occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
When the diagnostic test was carried out and abnormalities are detected, contact a Fujitsu customer engineer responsible for the device.
Library Server node Interface Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error has occurred in the server node interface.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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 a Fujitsu customer engineer responsible for the device.
Library Predicted to Fail in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in library are predicted.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Require Preventative Maintenance in %SysName%(%ProductID%[%IPAddress%])
Explanation
Preventative maintenance of a library is required.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Humidity Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The state in a library exceeded humidity specification.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Temperature Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The state in a library exceeded temperature specification.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Voltage Specification Exceeded in %SysName%(%ProductID%[%IPAddress%])
Explanation
The voltage to a library is unusual.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Detected Stray Tape In Drive in %SysName%(%ProductID%[%IPAddress%])
Explanation
According to a former hardware error, a cartridge is in library.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please remove a cartridge from a drive.
Picking Cartridge From Slot Fault in %SysName%(%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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Picking Cartridge Into Slot Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
A potential problem is in the library mechanism which arranges a cartridge in a slot.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Loading Cartridge Into Drive Fault in %SysName%(%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
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Library Door Open in %SysName%(%ProductID%[%IPAddress%])
Explanation
The door of a library is open.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
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 a Fujitsu customer engineer responsible for the device.
Mailslot Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
A mechanical problem is in library media reading/writing mailslot.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Library Cannot Operate Without Magazine in %SysName%(%ProductID%[%IPAddress%])
Explanation
A library cannot work without a magazine.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please re-execute after inserting a magazine in a library.
Library Security Compromised in %SysName%(%ProductID%[%IPAddress%])
Explanation
Library security is compromised.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Library Security Mode Changed in %SysName%(%ProductID%[%IPAddress%])
Explanation
The security mode of a library was changed.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
No action is required.
Library Manually Turned Offline in %SysName%(%ProductID%[%IPAddress%])
Explanation
Since the library is manually set as offline, it cannot use.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please re-execute after starting a library.
Library Drive Turned Offline in %SysName%(%ProductID%[%IPAddress%])
Explanation
The drive in a library turned offline.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Reading Barcode Labels Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
In a library mechanism, there is a potential problem in barcode labels or scanner hardware.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Library Inventory is Inconsistent in %SysName%(%ProductID%[%IPAddress%])
Explanation
The library detected inconsistency in the catalog.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please redo a library catalog, in order to correct inconsistency. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Invalid Library Operation Attempted in %SysName%(%ProductID%[%IPAddress%])
Explanation
Invalid library operation was carried out.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please re-execute after checking that library operation is effective. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Redundant Interface Port Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the interface port where it overlaps on library.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Fan Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the fan on library.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Power Supply Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
Error occurred in the power supply where it overlaps on library.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Please replace unusual power supply with a normal thing. When it carries out and the state does not change, contact a Fujitsu customer engineer responsible for the device.
Power Consumption Warning in %SysName%(%ProductID%[%IPAddress%])
Explanation
Power consumption of library is outside the specified range.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Robot Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a robot have occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Robot Hardware Fault in %SysName%(%ProductID%[%IPAddress%])
Explanation
The abnormalities of the hardware in a robot have occurred.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
Barcode Read Error in %SysName%(%ProductID%[%IPAddress%])
Explanation
Abnormalities have occurred in reading of a barcode.
Parameters
%SysName% : SysName
%ProductID% : Device name
%IPAddress% : IP address
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer responsible for the device.
The PDU%value% error occurred.
Explanation
PDU power supply error was detected.
Parameters
%value% : PDU number
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
The PDU%value% power off occurred.
Explanation
PDU power supply interception was detected.
Parameters
%value% : PDU number
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
None
System Administrator Corrective Action
When it shows abnormality, contact a Fujitsu customer engineer 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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
When it shows abnormality, contact a Fujitsu customer engineer 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 Response
None
System Administrator Corrective Action
No action is required.
%EventMessage%
Explanation
An event message was detected.
Parameters
%EventMessage% : Message
System Response
None
System Administrator Corrective Action
No action is required.
%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 Response
None
System Administrator Corrective Action
The response varies depending on the device and event type. For a device for which the XML definition file is provided, refer to the ETERNUS SF Event Guide to check the event type.
Depending on the event type, take corrective action such as notifying a Fujitsu customer engineer. 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 Response
None
System Administrator Corrective Action
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, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
Setup failed. Reason = Can't setup machine attribute
Explanation
An attempt to add a machine attribute to the node management file failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't setup vendor name
Explanation
An attempt to add a vendor name to the node management file failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't setup registry
Explanation
An attempt to register the node management file in the registry failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't setup MIB information
Explanation
Addition to the MIB management file failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't setup event category
Explanation
Addition of event types failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Systemwalker Centric Manager is not installed
Explanation
Systemwalker Centric Manager has not been installed.
System Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
No action is required.
Setup failed. Reason = Can't lock file
Explanation
The file used to add event types could not be locked.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't read file
Explanation
The file used to add event types could not be read.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't write file
Explanation
An attempt to write to the file used to add event types failed.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't unlock file
Explanation
The file used to add event types could not be unlocked.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Invalid OS
Explanation
The command was executed on an operating system that is not supported.
System Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Systemwalker Centric Manager is not installed
Explanation
Systemwalker Centric Manager has not been installed.
System Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
Setup failed. Reason = Can't read registry file
Explanation
Registry key values could not be obtained.
System Response
None
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing for updating account information
System Administrator Corrective Action
Contact a Fujitsu customer engineer.
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
Interrupts the processing
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
The system terminates processing.
System Administrator Corrective Action
Check the specified information on the Management 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 Management Server (Manager) is not active, check whether the Manager has been started normally.
System Response
The system terminates processing.
System Administrator Corrective Action
Check whether the specified server name is valid. Refer to "Starting and stopping the Manager" in the ETERNUS SF Storage Cruiser Operation Guide for starting and stopping the Management Server.
Check whether the Storage Cruiser's agent is setup valid in case it is installed. Refer to "Setup of Storage Cruiser's agent" in the ETERNUS SF Installation and Setup 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 Response
The system terminates processing.
System Administrator Corrective Action
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 Management Server name could not find in the network. Please confirm whether input Management Server name is correct. Or, please confirm the thing that the Management Server starts normally.
Parameters
%NAME% : Management Server name
System Response
The system terminates processing.
System Administrator Corrective Action
Please confirm the Management 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 is not registered in the account management. Please confirm the account to the Manager.
System Response
The system terminates processing.
System Administrator Corrective Action
Please login in the account of the Manager authority, and confirm account information.
No port number was entered for the administrative server.
Explanation
The port number used to connect to the Management Server is not specified.
System Response
None
System Administrator Corrective Action
Enter the port number used to connect to the Management Server.
[XXX] device's supportLevel is PARTIAL. Not FULL.
Explanation
XXX device is a Manually Embedded Device.
System Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
No action is required.
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 Response
None
System Administrator Corrective Action
Execute the SNMP Trap transmission destination setting on the device manually.
Unable to connect virtualization management server.
Explanation
It failed to connect with vCenter Server or Hyper-V host.
System Response
The system terminates processing.
System Administrator Corrective Action
Check the network environment for vCenter Server or Hyper-V host.
When you use Hyper-V host, refer to "In the case of Hyper-V (Windows version Manager only)" in "Displaying End to End list" in the ETERNUS SF Storage Cruiser Operation Guide and check the settings. Also, check whether the user name and password are correct. Specify a user name with the format of "netBIOSName\userName" or "domainName\userName".
Unable to log in virtualization management server.[ipAddress]
Explanation
It failed to log in the specified vCenter Server, because the username or password is incorrect or the password has expired.
Parameters
ipAddress : IP address
System Response
The system terminates processing.
System Administrator Corrective Action
Specify the correct username and password, and re-execute.
Unsupport device was specified.[ipAddress]
Explanation
The specified vCenter Server version is not supported.
Parameters
ipAddress : IP address
System Response
The system terminates processing.
System Administrator Corrective Action
Specify the vCenter Server 4.0 or later, and execute the registration of the vCenter Server.
The specified environment doesn't have necessary software.
Explanation
The settings of Hyper-V host or Management Server are incorrect.
System Response
None
System Administrator Corrective Action
Refer to "In the case of Hyper-V (Windows version Manager only)" in "Displaying End to End list" in the ETERNUS SF Storage Cruiser Operation Guide.
Internal error occurred.
Explanation
Internal error occurred.
System Response
None
System Administrator Corrective Action
Check the status of vCenter Server or Hyper-V host.
If you still have a problem, refer to "Collecting the troubleshooting information" in the Operation Guide (ETERNUS SF Express Operation Guide or ETERNUS SF Storage Cruiser Operation Guide) of the product in use to collect the information required for troubleshooting and contact Fujitsu Technical Support.
