Example: Configuring Chassis Cluster Redundant Ethernet Interfaces (CLI)

A redundant Ethernet interface is a pseudointerface that contains two or more physical interfaces, with at least one from each node of the cluster. Once the physical interfaces have been assigned to the redundant Ethernet interface, you then set the configuration that pertains to them at the level of the redundant Ethernet interface, and each of the child interfaces inherits the configuration.

Note: A redundant Ethernet interface is referred to as a reth in configuration commands.

Before you begin, complete the following tasks:

Use the following commands to bind redundant child physical interfaces to reth1 and reth2, respectively:

{primary:node1}user@host# set interfaces ge-0/0/0 gigether-options redundant-parent reth1{primary:node1}user@host# set interfaces ge-7/0/0 gigether-options redundant-parent reth1{primary:node1}user@host# set interfaces fe-1/0/0 fast-ether-options redundant-parent reth2{primary:node1}user@host# set interfaces fe-8/0/0 fast-ether-options redundant-parent reth2

Use the following commands to:

Use the following command to associate reth1.0 with a security zone named Trust. Security zone configuration is the same for redundant Ethernet interfaces as for any other interface.

{primary:node1}user@host# set security zones security-zone Trust interfaces reth1.0

Note: You can enable promiscuous mode on redundant Ethernet interfaces. When promiscuous mode is enabled on a Layer 3 Ethernet interface, all packets received on the interface are sent to the central point or Services Processing Unit regardless of the destination MAC address of the packet. If you enable promiscuous mode on a redundant Ethernet interface, promiscuous mode is then enabled on any child physical interfaces.

To enable promiscuous mode on a redundant Ethernet interface, use the promiscuous-mode statement at the [edit interfaces] hierarchy.

Related Topics