Open-E Knowledgebase

Failover events and Network component failure.

Article ID: 1273
Last updated: 01 Jun, 2011

Failover events can occur for many reasons. Investigations into such events can be easy if the failure is localized to the DSSV6 server or operating system. When the failure is triggered by ping node failure or Network component failure, investigation may involve administrative testing of all network componenets, and cabling related to the DSSV6 LAN. The DSSV6 can be configured to notify the administrator should such events trigger a failover. Email notification can be setup in the DSSV6 webgui: SETUP -> administrator -> Function: E-mail notification. It is advised to allow the sending address through any spam filters that may exist for the user recieving the email.

Due to various reasons for network failure, ping node failure, or network latency, it is recommended to have a plan in place to test the equipment periodically for problems with connections, and/or equipment failure. Setting up multiple ping nodes will allow more flexibility when it comes to availability to the DSSV6 appliance ( ).
It is also recommended to use certified cabling on all routes, and monitor switches and routers for packet loss, or failure. In case of such events, DSSV6 will failover, but investigation can be difficult as this falls outside the scope of DSSV6's ability to manage.

This article was:   Helpful | Not helpful Report an issue

Article ID: 1273
Last updated: 01 Jun, 2011
Revision: 1
Views: 2672
Posted: 01 Jun, 2011 by Rafinski G.
Updated: 01 Jun, 2011 by Rafinski G.
print  Print email  Subscribe email  Email to friend share  Share pool  Add to pool
Also listed in
folder Troubleshooting -> Software -> Network problems

Prev     Next
How can we setup the primary node, restart the iSCSI Failover...       Why my failback is not working although failover do??

The Knowledge base is managed by Open-E data storage software company.