Symantec VERITAS Cluster - Heartbeat on HP Blade server
Hello,
I just want to make sure what the best practice for Symantec VERITAS Cluster for Linux RedHat nodes running on HP Blade Server.
I have read "VCS considerations for Blade server environments" but i am still confused.
Kindly, find below some details :
HP Blade Virtual connect : 2 Shared uplink set and 1 Ethernet Network
SUS 1: Uplaink A ( using X5,X6,X7 - Interconnect Bay 1)
SUS2: Uplaink B ( using X5,X6,X7 - Interconnect Bay 2)
Ethernet Network: Internal ( without any uplink )
Now the server profile for Linux node :
Port 1 : Uplink A (public and lowpri)
Port 2 : Uplink B (public and lowpri)
**** bonding is done for Port 1 and Port 2 inside the Linux
Port 3: internal (Heartbeat)
Is that consedered as Symantec Cluster best practice or not ?
Hello,
Please read through below posts,
https://www-secure.symantec.com/connect/forums/bonded-interface-or-multiple-private-networks-heartbeat
Also, from the technote
http://www.symantec.com/docs/TECH18949
Q: I have blade servers, with just two shared NICs for each chassis. What's the best way to configure my interconnect?
A: Symantec recommends dedicating one of the shared NICs to a private LLT connection, and using the second shared NIC as the public interface, with a lowpri LLT link connection configured.G
The key thing is to make sure your llt heartbeat links are independent, and as you only have 2 physical interfaces you should only have 2 heartbeats, therefore I would recommend the following:
- Create 2 virtuals in each of the physical interfaces, so for example you have:
virtual interfaces A1 and A2 on physical interface A
virtual interfaces B1 and B2 on physical interface B
- Create bond for public interface using A1 and B1
- Use A2 and B2 as 2 high-pri (normal) heartbeats
- Do not configure a low-pri heartbeat.
Mike
- Create 2 virtuals in each of the physical interfaces, so for example you have:
