Redundancy Groups 1 Through 255

Note: In this release, an SRX-series chassis cluster supports the creation of only one redundancy group beyond redundancy group 0.

You can configure one or more redundancy groups numbered 1 through 255, referred to in this chapter as redundancy group x. Each redundancy group x acts as an independent unit of failover and is primary on only one node at a time.

Each redundancy group x contains one or more redundant Ethernet interfaces. A redundant Ethernet interface is a pseudo interface that contains a pair of physical Gigabit Ethernet interfaces or a pair of Fast Ethernet interfaces. Redundancy groups can contain one or more redundant Ethernet interfaces. A redundant Ethernet interface has two child links, one from each node. If a redundancy group is active on node 0, then the child links of all the associated redundant Ethernet interfaces on node 0 are active. If the redundancy group fails over to node 1, then the child links of all redundant Ethernet interfaces on node 1 become active.

On J-series chassis clusters, you can configure multiple redundancy groups to load-share traffic across the cluster (only one additional redundancy group supported on SRX-series chassis clusters). For example, you can configure some redundancy groups x to be primary on one node and some redundancy groups x to be primary on the other node. You can also configure a redundancy group x in a one-to-one relationship with a single redundant Ethernet interface to control which interface traffic flows through.

When you configure a redundancy group x, you must specify a priority for each node to determine the node on which the redundancy group x is primary. The node with the higher priority is selected as primary. The primacy of a redundancy group x can fail over from one node to the other. When a redundancy group x fails over to the other node, its redundant Ethernet interfaces on that node are active and their interfaces are passing traffic.

Table 57 gives an example of redundancy groups x in a J-series chassis cluster and indicates the node on which each group is primary. It shows the redundant Ethernet interfaces and their interfaces configured for each redundancy group x.

Table 57: Redundancy Groups Example for a J-series Chassis Cluster

As the example for a J-series chassis cluster in Table 57 shows:

• The Routing Engine on node 1 is active because redundancy group 0 is primary on node 1. (The Routing Engine on node 0 is passive, serving as backup.)
• Redundancy group 1 is primary on node 1. Interfaces fe-8/0/0 and fe-8/0/1 belonging to redundant Ethernet interface 0 and redundant Ethernet interface 1 are active and handling traffic.
• Redundancy group 2 is primary on node 1. Interfaces ge-9/0/0 and ge-9/0/1 belonging to redundant Ethernet interface 2 and redundant Ethernet interface 3 are active and handling traffic.
• Redundancy group 3 is primary on node 0. Interfaces ge-3/0/0 and ge-3/0/1 belonging to redundant Ethernet interface 4 and redundant Ethernet interface 5 are active and handling traffic.

Table 58 gives an example of redundancy group x in an SRX-series chassis cluster and indicates the node on which the group is primary. It shows the redundant Ethernet interfaces and their interfaces configured for redundancy group x.

Table 58: Redundancy Groups Example for an SRX-series Chassis Cluster

As the example for an SRX-series chassis cluster in Table 58 shows:

• The Routing Engine on node 0 is active because redundancy group 0 is primary on node 0. (The Routing Engine on node 1 is passive, serving as backup.)
• Redundancy group 1 is primary on node 0. Interfaces ge-1/0/0 and ge-1/3/0 belonging to redundant Ethernet interface 0 and redundant Ethernet interface 1 are active and handling traffic.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.