Ping node/failover and redundant switches.

[AdStar]

Excellent, now I get it...

BUT..

You can indicate up to 10 ping nodes. Please use comma as the delimiter (e.g. 192.168.0.1;192.168.0.2 etc.). Automatic failover will only take place if all ping nodes become unavailable to the primary node (e.g. the server does not take action when at least one ping node is reachable).

Is that a COMMA or a SEMI-COLON (thats the help popup on the iSCSI Failover section)?

So in my case could I set 4 ping nodes, being each of the switches01 through 04, that would allow restarts of the swithes and if one of the SANS did die for good, the failover aux links would pic that up?

My next question I gather I have to turn off iscsi failover on my secondary, update the ping node settings turn it back on, failover and then repeat on the primary right?

Cheers
Adam

[AdStar]

ugh that won't work actually, all the switches are in the same subnet 202.xxx.xxx.xxx

how do I go about picking my ping nodes then?

I'm think switch01 and switch02 in the 202 subnet, but how do I handle the ping checks on the iscsi network, Im assuming I shouldn't use each san as a ping node? or is that ok to do?

[To-M]

Use a Ping node with UPS, Firewalls, Routers anything that is in the same subnets is also best and has high up time - see link below for more information. we spent allot of time on these video's that will help w/ some of your questions.

http://www.open-e.com/library/webcasts-and-videos/
2010.02 Open-E DSS V6 AutoFailover with VMware 4.0
2010.09 How to setup iSCSI Failover with Unicast Network connection mode

[AdStar]

Hi guys,

I've run into a bit of an issue, I'm just not sure how to do this.
As I stated my VIP's are
eth0 10.1.5.100
eth1 10.1.6.100
eth2 10.1.7.100
eth3 10.1.8.100

Which are only active on the active/primary node.
My VMWare hosts have all the iscsi traffic on the network 10.1.5.x/ 10.1.6.x/ 10.1.7.x 10.1.8.x I was going to add the IP's that are on my virtual hosts as ping node IP's but then relised that only the primary server will see them. As the secondary node doesn't have an IP on it in the subnet. This is all a catch 22, none of my routers/firewalls are in the same subnet as my iSCSI traffic, do you guys have any ideas on how I can do this?

If I was to add an ip from one of the above subnets to my switches etc, I'm still have the issue of only the node with the VIP's on it will see the ping nodes.

Any ideas?

Cheers
Ad

[To-M]

If I remember you can add more then 1 ping node and this can be on a different subnet so you should be ok just make sure the ping nodes are seen for each network for the Pri and Sec. Ping them first to be sure for each subnet.