Example: Configuring Chassis Cluster Redundant Ethernet Interfaces

Requirements

Before you begin:

• Example: Setting the Chassis Cluster Node ID and Cluster ID
• Example: Configuring the Number of Redundant Ethernet Interfaces in a Chassis Cluster
• Example: Configuring the Chassis Cluster Fabric
• Example: Configuring Chassis Cluster Redundancy Groups

Overview

After physical interfaces have been assigned to the redundant Ethernet interface, you set the configuration that pertains to them at the level of the redundant Ethernet interface, and each of the child interfaces inherits the configuration.

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

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.

Configuration

CLI Quick Configuration

To quickly configure redundant Ethernet interfaces for IPv4, copy the following commands and paste them into the CLI:

To quickly configure redundant Ethernet interfaces for IPv6, copy the following commands and paste them into the CLI:

Step-by-Step Procedure

1. Bind redundant child physical interfaces to reth1.
   {primary:node0}[edit]user@host# set interfaces ge-0/0/0 gigether-options redundant-parent reth1user@host# set interfaces ge-7/0/0 gigether-options redundant-parent reth1
2. Bind redundant child physical interfaces to reth2.
   {primary:node0}[edit]user@host# set interfaces fe-1/0/0 fast-ether-options redundant-parent reth2user@host# set interfaces fe-8/0/0 fast-ether-options redundant-parent reth2
3. Add reth1 to redundancy group 1.
   {primary:node0}[edit]user@host# set interfaces reth1 redundant-ether-options redundancy-group 1
4. Set the MTU size.
   {primary:node0}[edit]user@host# set interfaces reth1 unit 0 family inet mtu 1500
5. Assign an IP address to reth1.
   {primary:node0}[edit]user@host# set interfaces reth1 unit 0 family inet address 10.1.1.3/24
6. Associate reth1.0 to the trust security zone.
   {primary:node0}[edit]user@host# set security zones security-zone Trust interfaces reth1.0

Step-by-Step Procedure

1. Bind redundant child physical interfaces to reth1.
   {primary:node0}[edit]user@host# set interfaces ge-0/0/0 gigether-options redundant-parent reth1user@host# set interfaces ge-7/0/0 gigether-options redundant-parent reth1
2. Bind redundant child physical interfaces to reth2.
   {primary:node0}[edit]user@host# set interfaces fe-1/0/0 fast-ether-options redundant-parent reth2user@host# set interfaces fe-8/0/0 fast-ether-options redundant-parent reth2
3. Add reth2 to redundancy group 1.
   {primary:node0}[edit]user@host# set interfaces reth2 redundant-ether-options redundancy-group 1
4. Set the MTU size.
   {primary:node0}[edit]user@host# set interfaces reth2 unit 0 family inet6 mtu 1500
5. Assign an IP address to reth2.
   {primary:node0}[edit]user@host# set interfaces reth2 unit 0 family inet6 address 2010:2010:201::2/64
6. Associate reth2.0 to the trust security zone.
   {primary:node0}[edit]user@host# set security zones security-zone Trust interfaces reth2.0

Results

From configuration mode, confirm your configuration by entering the show interfaces reth0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

For brevity, this show command output includes only the configuration that is relevant to this example. Any other configuration on the system has been replaced with ellipses (...).

If you are done configuring the device, enter commit from configuration mode.

Verification

To confirm that the configuration is working properly:

• Verifying Chassis Cluster Redundant Ethernet Interfaces
• Verifying Chassis Cluster Control Links

Verifying Chassis Cluster Redundant Ethernet Interfaces

Purpose

Verify the configuration of the chassis cluster redundant Ethernet interfaces.

Action

From operational mode, enter the show interfaces | match reth1 command:

ge-0/0/0.0              up    down aenet    --> reth1.0
ge-7/0/0.0              up    down aenet    --> reth0.0
reth1                   up    down
reth1.0                 up    down inet     10.1.1.3/24

Verifying Chassis Cluster Control Links

Purpose

Verify information about the control interface in a chassis cluster configuration.

Action

From operational mode, enter the show chassis cluster interfaces command:

Control link 0 name: em0

Redundant-ethernet Information:
    Name         Status      Redundancy-group
    reth1        Up          1

Interface Monitoring:
    Interface         Weight    Status    Redundancy-group
    fe-1/0/0          200       Up        1
    fe-8/0/0          200       Up        1
    ge-0/0/0          200       Up        1
    ge-7/0/0          200       Up        1

Note: On SRX1400, SRX3400, SRX3600, SRX5600, and SRX5800 devices, eight-queue configurations are not reflected on the chassis cluster interface.