Unsolved
This post is more than 5 years old
1 Rookie
•
2 Posts
0
538
April 27th, 2007 07:00
Nic to Nic Failover
How to configure a "NIC TO NIC FAILOVER" with autostart 5.2.2 over WINDOWS 2003 R2
regards
regards
No Events found!
Unsolved
This post is more than 5 years old
1 Rookie
•
2 Posts
0
538
April 27th, 2007 07:00
Top
amediratta
2 Intern
•
2K Posts
0
April 27th, 2007 19:00
If I remember correctly, AutoStart does not support NIC to NIC failover.
I had the same query earlier and support told me that.
rericamg
1 Rookie
•
2 Posts
0
April 30th, 2007 00:00
- I have install autostart 5.2.2 on the 2 servers
- Each server has 3 nics (nic1, nic2, nic3)
- nic3 is dedicate for data sync
- nic1 is for domain network 1 and is connect to the 1st SWITCH
- nic2 is the "backup" of nic1 and is connect to the second SWITCH
The training that i made describe this fonction but do not explain how to setup it.
IKP1
198 Posts
0
May 1st, 2007 02:00
In your configuration with only 3 nics and 1 of these used for data sync ( I am assuming you are using the Mirror'd Disk Data Source) You are better using the remaining two lines as seperate Domain Lines and allowing EAS Heartbeat traffic to communicate between the two nodes.
If you need additional resilience on the "public" interface for the shared IP connection to your cluster, then I would suggest you add a fourth nic to each node and then configure Nic to Nic between your public facing interfaces. Alterativly if your hardware vendor provides a device driver which allows the OS to "team" the two public facing NICs you would be strongly advised to use this rather than the Nic to Nic configuration within EAS.