No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

FAQ-What Are the Conditions That Trigger a SIR Cluster Failover

Publication Date:  2015-08-04  |   Views:  931  |   Downloads:  0  |   Document ID:  EKB1000083575


Issue Description

What are the conditions that trigger a SIR cluster failover?


Products and versions:

VTL6000 V100R003
VTL6900 V100R005

On the command-line interface (CLI), run the sms -v command to query the SIR cluster status. Any change to the status (bold text) in the command output can trigger a failover.

[root@SIRServer-51 ~]# sms -v

Last Update by SM: Wed Dec 23 10:16:23 2009
Last Access by RPC: Thu Jan  1 08:00:00 1970
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
Status of IPStor ISTOR Module: OK
Status of Remote Link :OK
Status of Raid :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
FM loading resource 0
SM loading resource 0
vdevs status  : OK
communication module hung : NO(0)
istor status: OK
remote link status: UP
quorum disabled status: NO
fc configuration information: OK(0)
Please use sms -u to get usage