This article describes the issue of an unsupported hold-down-interval value being committed for the 0 JSRP redundancy group, due to the lack of proper configuration exception checking.

The hold-down-interval is a configuration parameter that is used to define the minimum required interval between back-to-back failover for the specified redundancy group.

Any value that is out of the above range will not be supported. However, the 0 value can be configured for RG0 and committed, without any error:

root@SRX# show chassis cluster
reth-count 2;
redundancy-group 0 {
    node 0 priority 150;
    node 1 priority 100;
    hold-down-interval 0; < configured 0 for RG0
}
redundancy-group 1 {
    node 0 priority 150;
    node 1 priority 100;
    interface-monitor {
        fe-0/0/0 weight 255;
        fe-0/0/1 weight 255;
        fe-1/0/0 weight 255;
        fe-1/0/1 weight 255;
    }
}

{primary:node0}[edit]
root@SRX#
{primary:node0}[edit]
root@SRX# commit
node0:
configuration check succeeds < passed configuration check with no error
node1:
commit complete
node0:
commit complete

{primary:node0}[edit]
root@SRX#


This issue is due to a limitation with the configuration check in the current software design.

This is a limitation with the current software design. Make sure that the configuration for the hold-down-interval on the 0 JSRP redundancy-group is within the 300-1800 range.