Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Andy_N
Contributor

ClusterXL different hardware

Hello,

Does anybody have experience to bring online failing node on different HW?

E.g. node 1 (online) has 2 cores per CPU and 5 network ports, new node has 10 cores per CPU and 4 network ports.

We haven’t exactly HW configuration faulted node was.

It was appliance 5200, but we have server Dell PE R630 and wanna bring it online as a second node.

Cluster configuration is HA mode.

 

Regards

 

0 Kudos
8 Replies
G_W_Albrecht
Champion
Champion

sk93306: ATRG: ClusterXL

In order to avoid unexpected behaviour, ClusterXL is supported only between machines with identical CPU characteristics.

In addition, in order to avoid unexpected fail-overs due to issues with CCP packets on cluster interfaces, it is strongly recommended to pair only identical physical interfaces as cluster interfaces.

Number of CoreXL FW instances: number of instances on all members must be identical.

0 Kudos
Bob_Zimmerman
Advisor

For sync to work, the CoreXL config must match between the two nodes. That's the only real, functional concern, though. I've done this dozens of times.

Each system should ideally have at least as many interfaces as you are actually using. It's possible to define an interface only on one member, if you're willing to accept that traffic not working when you run on the other member.

I haven't personally tried clustering between an untagged interface on one firewall and a tagged interface on another, but I don't know of a reason it definitely would not work. That might let you get around the interface count concern above.

 

NOTE: there is a difference between "will work" and "is supported". Doing weird things like this will probably work, but the TAC may not be able to help with problems. As a result, I would not run a cluster like this for long.

0 Kudos
PhoneBoy
Admin
Admin

One other factor to consider is if this is R80.40/R81 and Dynamic Workloads is enabled.
In that situation, the clusters will definitely have different CoreXL configs (it's dynamic, after all), but sync still works (assuming same CPU characteristics).

No question this is an unsupported configuration.
I would do thorough testing on this prior to even considering doing this in production. 

0 Kudos
_Val_
Admin
Admin

Dynamic Workloads leverage Multi-Queue for both HW and SW interrupts. That allows FW to maintain a constant amount of instances, with variable amount of CPUs serving them. For that matter, Dynamic Workflow does not cause any clustering issue, but it still works with the limitation of exactly the same amount of CPUs on all cluster members

0 Kudos
Andy_N
Contributor

Thanks for answer

E.g if I restrict CoreXL on new node board to 2 cores – cluster will works?

Actually when I tried bring online a new node (w/o CoreXL matching between 2 nodes) after policy was installed a new node got loop reboot w/o login prompt.

It fixed only get node in maintained mode and disabling Cluster membership.

0 Kudos
Wolfgang
Leader
Leader

You spent so much time to trying to get running an unsupported solution. I would prefer to get a replacement for the failing node.

In the meantime you can use your open server as cold standby. Copy you're configuration from one to the other node. And in case of a failure you can switch to the new node, reset SIC and you had a running node. 

Wolfgang

Andy_N
Contributor

Hello, Wolfgang

We are thinking about it and probably what this right way.

U r right – time was spent so much…

Thanks everyone for answers

Regards

0 Kudos
_Val_
Admin
Admin

As already mentioned, you have to run two identical machine in a cluster. Anything else in a not supported config, and most probably will not work. This includes not just the amount of CPUs, other HW as well.

0 Kudos