PRIMECLUSTER Wizard for NAS (PRIMEQUEST) 4.2 Configuration and Administration Guide - Linux -
|
Contents

|
Chapter 6 Messages
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
- [Error] [0203] exportfs Error Message: Message,EXIT_CODE:EXIT_CODE
[Description]
Volume export operation on NAS output Message and terminated with EXIT_CODE.
[Corrective action]
Check Message and EXIT_CODE, and take corrective action.
- [Error] [0204] exportfs -u Error Message: Message,EXIT_CODE: EXIT_CODE
[Description]
Volume unexport operation on NAS output Message and terminated with EXIT_CODE.
[Corrective action]
Check Message and EXIT_CODE, and take corrective action.
- [Error] [0205] unlock Error Message: Message
[Description]
Unlock operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
- [Error] [0206] Failed to acquire a host name
[Description]
Script failed to acquire a node state.
[Corrective action]
Check if there's sufficient memory in the failed node.
- [Error] [0207/0209/0211/0213/0215] Cannot connect to NetApp Filer(NetApp Filer name) with rsh
[Description]
Cluster nodes cannot be connected to NAS using rsh.
[Corrective action]
Check if a NAS name is correct, rsh can be used on NAS, and there is no problem with a network system.
- [Error] [0208/0210] Failed to cancel the NFS locking on the NAS storage (Details host name, NetApp Filer name)
[Description]
Script failed to cancel the lock on the NAS(NetApp Filer name) kept by the host(host name).
[Corrective action]
See [Error] [0205] that is previously output and take corrective action.
- [Warn] [0301] exportfs Message:Message
[Description]
Volume export operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
- [Warn] [0302] exportfs -u Message:Message
[Description]
Volume unexport operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
- [Warn] [0303/0305] Cannot export Export point on NetApp Filer(NetApp Filer name)
[Description]
Export of Export point failed on NAS.
[Corrective action]
See [Error] [0203] that is previously output and take corrective action.
- [Warn] [0304] Cannot unexport Export point on NetApp Filer(NetApp Filer name)
[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
- [Error] [1204] unlock Error Message : Message
[Description]
Unlock operation on NAS output Message.
[Corrective action]
Check Message and take corrective action.
- [Error] [1205/1207/1209/1210/1211/1213] Cluster nodes cannot be connected to NetApp Filer($NetApp Filer name) with rsh
[Description]
Cluster nodes cannot be connected to NAS using rsh.
[Corrective action]
Check if a NAS name is correct, rsh can be used on NAS, and there is no problem with a network system.
- [Error] [1206/1208/1212/1214] Failed to cancel the NFS locking on the NAS storage (Details host name, NetApp Filer name)
[Description]
Script failed to cancel the lock on the NAS(NetApp Filer name) kept by the host(host name).
[Corrective action]
See [Error] [0205] that is previously output and take corrective action.
- [Error] [1217] Failed to check resources
[Description]
The detector failed to monitor the resource state.
[Corrective action]
Check if there's enough space in /opt, and if there's sufficient memory in the failed node.
- [Error] [1218] Failed to check nodes
[Description]
The detector failed to monitor the node state.
[Corrective action]
Check if there's enough space in /opt, and if there's sufficient memory in the failed node.
- [Warn] [1301/1302] Unknown host(NetApp Filer name)
[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.
- [Warn] [1303/1304/1305/1306] The ping(NetApp Filer name) failed, Takeover is executed
[Description]
The failover of the NAS-Cluster will be done because ping command for the NAS name(NetApp Filer name) failed.
[Corrective action]
See "3.3 Recovery sequence after control facility of the NAS-Cluster" and take corrective action.
- [Warn] [1307] The ping of both host(NetApp Filer name, NetApp Filer name) failed
[Description]
The all of the NAS-Cluster are down.
[Corrective action]
Recover the all of the NAS-Cluster.
- [Warn] [1308] The ping(NetApp Filer name) failed, count COUNT.
[Description]
Ping 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
- [Error] [2203/2204] Cluster nodes cannot be connected to NetApp Filer(NetApp Filer name) with rsh
[Description]
Cluster nodes cannot be connected to NAS using rsh.
[Corrective action]
Check if a NAS name is correct, rsh can be used on NAS, and there is no problem with a network system.
- [Warn] [2301/2302] Unknown host(NetApp Filer name)
[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.
- [Warn] [2303/2304/2305/2306] The ping(NetApp Filer name) failed, Takeover is executed
[Description]
The failover of the NAS-Cluster will be done because ping command for the NAS name(NetApp Filer name) failed.
[Corrective action]
See "3.3 Recovery sequence after control facility of the NAS-Cluster" and take corrective action.
- [Warn] [2307] The ping of both host(NetApp Filer name, NetApp Filer name) failed
[Description]
The all of the NAS-Cluster are down.
[Corrective action]
Recover the all of the NAS-Cluster.
- [Warn] [2308] The ping(NetApp Filer name) failed, count COUNT.
[Description]
Ping 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

For details of hvnasdisable or hvnasenable command, refer to "4.1 hvnasdisable - Discontinue monitoring resource", "4.2 hvnasenable - Restart monitoring resource".
- command: ERROR: Internal error! (details)
[Description]
Internal error occurred.
[Corrective action]
Contact your system administrator.
- command: ERROR: Failed to disable/enable resource monitoring - resource_name
[Description]
Cannot disable or enable monitoring.
[Corrective action]
Contact your system administrator.
- command: ERROR: hvgdconfig does not exist!
[Description]
hvgdconfig file does not exist.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
- command: ERROR: Obtaining local SysNode Name failed!
[Description]
Cannot get a local SysNode name.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
- command: ERROR: Obtaining RMS configuration Name failed!
[Description]
Cannot get an RMS configuration name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
- command: ERROR: Result of hvw is invalid!
[Description]
Cannot execute an RMS command hvw(1M) correctly.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
- command: ERROR: Failed to disable/enable resource monitoring! (details)
[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.
- command: ERROR: No Wizard for NAS resources belong to specified userApplication! - userApplication_name
[Description]
There are no Wizard for NAS resources in the specified userApplication userApplication_name.
[Corrective action]
Retry with a correct userApplication name.
- command: ERROR: No Wizard for NAS resources are in the current RMS configuration!
[Description]
There are 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.
- command: ERROR: No Wizard for NAS resources exist on this node! - SysNode_name
[Description]
There are 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.
- command: ERROR: Invalid userApplication or Resource!
[Description]
The specified userApplication name or resource name is invalid.
[Corrective action]
Retry with a correct userApplication name and resource name.
- command: ERROR: The specified resource does not exist on SysNode_name! - 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.
Copyright FUJITSU LIMITED 2010