cancel
Showing results for 
Search instead for 
Did you mean: 

Symantec VERITAS Cluster - Heartbeat on HP Blade server

meeran
Level 2

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 ?

2 ACCEPTED SOLUTIONS

Accepted Solutions

Gaurav_S
Moderator
Moderator
   VIP    Certified

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

View solution in original post

mikebounds
Level 6
Partner Accredited

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:

  1. 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
     
  2. Create bond for public interface using A1 and B1
     
  3. Use A2 and B2 as 2 high-pri (normal) heartbeats
     
  4. Do not configure a low-pri heartbeat.

Mike

View solution in original post

3 REPLIES 3

Gaurav_S
Moderator
Moderator
   VIP    Certified

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

meeran
Level 2

Thanks Gaurav for your reply.

I have read the posts before but still confused because in the posts they are talking about balde chasiss not blade server .

Each blade server havce two NICs but from HP virtual connecto you can add up to 8 network (virtual).

So, when they said " 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" what did they mean ? is it the two physical NICs inside the blade or eight virtual NIC (HP Virtual connect).

 

 

mikebounds
Level 6
Partner Accredited

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:

  1. 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
     
  2. Create bond for public interface using A1 and B1
     
  3. Use A2 and B2 as 2 high-pri (normal) heartbeats
     
  4. Do not configure a low-pri heartbeat.

Mike