redundancy-group 1 {
node 0 priority 100;
node 1 priority 1;
preempt;
interface-monitor {
ge-0/0/0 weight 128;
ge-0/0/1 weight 128;
ge-5/0/0 weight 128;
ge-5/0/1 weight 128;
}
}
Pretty straightforward. But here is one thing I don't get and I've never seen explicitly explained. And I've never tested this, myself.
If redundancy-group 1 is active on node 0 and node 1 interfaces ge-5/0/0 and ge-5/0/1 fail would that cause a failover from node 0 to node 1?
Normally you'd only want failover when the monitored interfaces on the current active node's interfaces fail, right? We don't care what happens to the interfaces on the other node. Is this inherently how interface monitoring and redundancy group failover works? If not, how to configure for that?
I *think* the answer is that when ge-5/0/0 and/or ge-5/0/1 fail, node 1 priority drops to zero so the redundancy group cannot fail over to node 1, despite the weight threshold being met.
Where this might be practical is with more interfaces:
redundancy-group 2 {
node 0 priority 100;
node 1 priority 1;
preempt;
interface-monitor {
ge-0/0/4 weight 85;
ge-0/0/5 weight 85;
ge-0/0/6 weight 85;
ge-0/0/7 weight 85;
ge-5/0/4 weight 85;
ge-5/0/5 weight 85;
ge-5/0/6 weight 85;
ge-5/0/7 weight 85;
}
}
In this case assume ge 4-7 on each SRX is link aggregated to the same switch. So node 0, 4-7 -> reth2 (lacp) -> Switch-A and Node 1, 4-7 -> reth2 (lacp) -> Switch-B. Reth2 is attached to redundancy group 2.
If three ports in the lacp group for reth 2 fail, redundancy group 2 will fail over. But here again, if three failed ports on are on node ONE while the RG is active on node 0, would THAT cause node 1 priority to fall to zero, or would the RG fail over to node 1, having three of it's four ports down?
Hopefully this is clear, what I mean.
Bottom line is, I'd not want failures of interface monitoring on the passive/inactive node for a RG to cause RG to fail to that node.
I guess the root of my question is a that I need a thorough technical understanding of how interface monitoring failures affect node priority, if that is the relevant mechanism here.