Description

When a RETH interface is configured only on one node, its status is always down. The article points out that this behavior is expected, and indicates that for the RETH interface to be up, it needs to be configured on both nodes.

 

Symptoms

If a RETH interface is configured only on one node and this node is secondary, the RETH interface is always down.

Example

Consider that RETH2 interface is configured on ge-7/0/3 of node 1, which is the secondary node, on SRX1500. 

root@jtac-SRX1500-r001# run show interfaces terse | grep reth2
ge-7/0/3.0              up    up   aenet    --> reth2.0
reth2                   up    down
reth2.0                 up    down inet

Redundancy group: 0 , Failover count: 1
node0  100      primary        no      no       None
node1  200      secondary      no      no       None

Redundancy group: 1 , Failover count: 1
node0  100      primary        no      no       None
node1  200      secondary      no      no       None

 

Solution

This is expected behavior.

Normally, a RETH interface should be configured on both nodes. If all the physical interfaces in one RETH interface are on one node and this node is secondary, the RETH interface is down although all its physical interfaces are up.

As seen, after adding ge-0/0/3 of node 0 for the RETH2 interface, RETH2 is up: 

root@jtac-SRX1500-r001# run show interfaces terse | grep reth2
ge-0/0/3.0              up    up   aenet    --> reth2.0
ge-7/0/3.0              up    up   aenet    --> reth2.0
reth2                   up    up
reth2.0                 up    up   inet