Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 - Release: 1.0 to 2.0
Sun StorageTek VTL Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221 [Release: 4.0 to 4.0]
- Getting "The primary server is not in a healthy state for failback..." when trying to failback via VTL Console
For certain failover events, VTL GUI will retain in unhealthy status as a safety net and has to be cleared manually via server command line.
If the GUI is reporting the primary server as unhealthy when trying failback, do the following:
1. Login to primary server (i.e., putty, ssh, etc.) and issue: sms -v
Note: Use the Heartbeat IP for login. The Virtual IP is transferred over to secondary server during failover.
2. Look for "FailOverStatus" in output
a. If status is "2 (Ready)", then the GUI is reporting an older status:
Note: GUI will retain unhealthy status as a safety net and has to be cleared manually via command line.
i. To clear unhealthy message and force failback, logon to secondary server (using it's Heartbeat IP) and stop the failover module: vtl stop fm
ii. Verify primary server has taken back control (verify through GUI or issue sms -v again on primary server until it returns "1 (UP)")
iii. Once primary server is verified, start the failover module on secondary server: vtl start fm
OR
i. From Console GUI, right click on secondary server name, select Failover>Stop Takeover
ii. Popup message will appear with message:
WARNING: The primary server is not in a healthy state for failback.
If you still want to fail back to the primary server, please type the word
YES to proceed. Otherwise, click cancel to exit.
iii. Type YES in box and click OK.
Note: If GUI reports back, discovering servers, close Console and reconnect. This sometimes happens when Virtual IP is switched back to primary server.
b. If sms -v reports any other status than "2 (Ready)":
- Generate Xrays from both servers and send them to Oracle VTL support(refer to Knowledge doc General information for collecting VTL Xray for customer and field).
Please Note: Xray for failed server, will have to be generated via command line.
Refer to the VTL Users Guide and Knowledge doc How to Failback Failed server or more information on failover/failback.
Additional Information
Sample 'sms -v' outputs
During normal operating status:
[root@camstore1 root]# sms -v
Last Update by SM: Thu Jan 26 14:27:03 2006
Last Access by RPC: Thu Jan 26 14:27:04 2006
FailOverStatus: 1(UP)
Status of IPStor Server (Transport) : OK
Status of IPStor Server (Application) : OK
Status of IPStor Authentication Module : OK
Status of IPStor Logger Module : OK
Status of IPStor Communication Module : OK
Status of IPStor Self-Monitor Module : OK
Status of IPStor NAS Modules: OK(0)
Status of IPStor Fsnupd Module: OK
Status of IPStor ISCSI Module: OK
Status of FC Link Down : OK
Broadcast Arp : NO
reservation conflict : 0
Quorumrepository Status : OK
Number of reported failed devices : 0
Status of Network Connection: OK
NAS health check : NO
XML Files Modified : NO
IPStor Failover Debug Level : 0
IPStor Self-Monitor Debug Level : 0
Do We Need To Reboot Machine(SM): NO
Do We Need To Reboot Machine(FM): NO
Please using sms -u to get usage
Example of sms -v output:
(After failover secondary server took over primary server, log into primary (using Heartbeat IP) and check FailOverStatus)
[root@primary root]# sms -v
Last Update by SM: Thu Jan 26 10:03:52 2006
Last Access by RPC: Thu Jan 26 10:03:49 2006
FailOverStatus: 2(READY)
Status of IPStor Server (Transport) : OK
Status of IPStor Server (Application) : OK
===============================================================
Previously Published As
STKKB73313
