This article explains the difference in the available maximum redundancy-group number between Junos 12.1X44 and 12.1X46 or later.

When the maximum redundancy-group number is configured in Junos 12.1X44, the commit command will fail after upgrading to Junos 12.1X46 or later releases.

The configurable maximum number of redundancy groups has been changed in Junos 12.1X46 and later releases.

The following explanation shows the difference in the maximum configurable redundancy-group number between Junos 12.1X44 and Junos 12.1X46 or later:

Note: "n" stands for maximum configurable number of reth interfaces. Please refer to the table below for the maximum numbers for each SRX platform.

• Maximum number of reth-count and redundancy groups in Junos 12.1X44 :

reth-count starts from 1 to "n"

redundancy-group is 0 to "n"

            Possible completions:

            Possible completions:

• Maximum number of reth-count and redundancy-group in Junos 12.1X46 or later :

reth-count starts from 1 to "n"

redundancy-group is 0 to "n-1"

Possible completions:

Possible completions:

Caution: In this example of SRX550, when redundancy group 58 is configured in Junos 12.1X44, the commit command will fail after upgrading to Junos 12.1X46 or later.  Please change redundancy group number within n-1 before upgrade.

Table: Maximum Number of Redundant Ethernet Interfaces Allowed

See also:

• Understanding Chassis Cluster Redundant Ethernet Interfaces(15.1X49-D40 for SR300 and SRX1500)
• Understanding Chassis Cluster Redundant Ethernet Interfaces (12.3X48)

• Understanding Chassis Cluster Redundant Ethernet Interfaces (15.1X49-D40 for SR300 and SRX1500)
• Understanding Chassis Cluster Redundant Ethernet Interfaces (12.3X48)