This Chapter describes messages related to the PRIMECLUSTER Wizard for NAS and corrective action. These messages appear in the internal log files or syslog(daemon.notice).
Online/Offline script
[Description]
Volume export operation on NAS output Message and terminated with EXIT_CODE.
[Corrective action]
Check Message and EXIT_CODE, and take corrective action.
[Description]
Volume unexport operation on NAS output Message and terminated with EXIT_CODE.
[Corrective action]
Check Message and EXIT_CODE, and take corrective action.
[Description]
Script failed to acquire a node state.
[Corrective action]
Check if there is sufficient memory in the failed node.
[Description]
Cluster nodes cannot be connected to NAS using SSH 2.0.
[Corrective action]
Check if a NAS name is correct, SSH 2.0 can be used on NAS, and there is no problem with a network system.
[Description]
Volume export operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
[Description]
Volume unexport operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
[Description]
Export of Export point failed on NAS.
[Corrective action]
See [Error] [0203] that is previously output and take corrective action.
[Description]
Unexport of Export point failed on NAS.
[Corrective action]
See [Error] [0204] that is previously output and take corrective action.
Error messages in scalable operation
[Description]
Cluster nodes cannot be connected to NAS using SSH 2.0.
[Corrective action]
Check if a NAS name is correct, SSH 2.0 can be used on NAS, and there is no problem with a network system.
[Description]
The detector failed to monitor the resource state.
[Corrective action]
Check if there is enough space in /opt, and if there is sufficient memory in the failed node.
[Description]
The detector failed to monitor the node state.
[Corrective action]
Check if there is enough space in /opt, and if there is sufficient memory in the failed node.
[Description]
NetApp Filer name is Unknown.
[Corrective action]
Check if the NAS name(NetApp Filer name) is correct, and there is no problem with a network system. Verify that the access to the NAS device is possible by the type of IPaddress of NetappClusterPingIPType at "2.5.2 userApplication creation"
[Description]
The failover of the NAS-Cluster will be done because the ping / ping6 command for the NAS name(NetApp Filer name) failed.
[Corrective action]
See "3.4 Recovery sequence after control facility of the NAS-Cluster" and take corrective action.
[Description]
The all of the NAS-Cluster are down.
[Corrective action]
Recover the all of the NAS-Cluster.
[Description]
The ping / ping6 command for the NAS name(NetApp Filer name) failed.
If COUNT reaches to the value of NetappClusterPingCount, the failover of the NAS-Cluster will be done.
[Corrective action]
Check if the NAS name(NetApp Filer name) is correct, and there is no problem with a network system.
Error messages in standby operation
[Description]
Cluster nodes cannot be connected to NAS using SSH 2.0.
[Corrective action]
Check if a NAS name is correct, SSH 2.0 can be used on NAS, and there is no problem with a network system.
[Description]
The failover of the NAS-Cluster will be done because the ping / ping6 command for the NAS name(NetApp Filer name) failed.
[Corrective action]
See "3.4 Recovery sequence after control facility of the NAS-Cluster" and take corrective action.
[Description]
The all of the NAS-Cluster are down.
[Corrective action]
Recover the all of the NAS-Cluster.
[Description]
The ping / ping6 command for the NAS name(NetApp Filer name) failed.
If COUNT reaches to the value of NetappClusterPingCount, the failover of the NAS-Cluster will be done.
[Corrective action]
Check if the NAS name(NetApp Filer name) is correct, and there is no problem with a network system.
hvnasdisable/hvnasenable messages
See
For details of hvnasdisable or hvnasenable command, refer to "4.1 hvnasdisable - Discontinue monitoring resource", "4.2 hvnasenable - Restart monitoring resource".
[Description]
Internal error occurred.
[Corrective action]
Contact your system administrator.
[Description]
Cannot disable or enable monitoring.
[Corrective action]
Contact your system administrator.
[Description]
hvgdconfig file does not exist.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Description]
Cannot get a local SysNode name.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
[Description]
Cannot get RMS configuration name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Description]
Cannot execute RMS command hvw(1M) correctly.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Description]
Cannot disable or enable monitoring because of details.
[Corrective action]
Check if PRIMECLUSTER installation, cluster setup and building a cluster application (userApplication) have been completed.
[Description]
There is no Wizard for NAS resources in the specified userApplication userApplication_name.
[Corrective action]
Retry with a correct userApplication name.
[Description]
There is no Wizard for NAS resources in the current RMS configuration.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Netapp resources are included in the userApplication.
[Description]
There is no Wizard for NAS resources on a local node SysNode_name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Netapp resources are included in the userApplication.
[Description]
The specified userApplication name or resource name is invalid.
[Corrective action]
Retry with a correct userApplication name and resource name.
[Description]
The specified resource does not exist on a local node SysNode_name.
[Corrective action]
Retry with a correct resource name or retry on a correct node.
