Having completed a manual failover of the redundancy groups in my previous post, this test go through the process of what would have happen if we had a link fault.

Test B (Interface Failure)⌗

In my first post creating srx cluster, I had configured Interface Monitoring. Interface monitoring can be used to trigger a failover in the event link status on an interface goes down. For this test I will be disconnecting interface ge-0/0/1, once this has been disconnected we should see that redundancy group 1 failover to Node1 from Node0.

We will check the status of the cluster and the interfaces before proceed:

Pre Verfication⌗

Chassis Cluster Status⌗

{primary:node0}root@lab_SRX220_Top# run show chassis cluster status 
Cluster ID: 1 
Node                  Priority          Status    Preempt  Manual failover

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

Redundancy group: 1 , Failover count: 33
    node0                   100         primary        yes      no  
    node1                   1           secondary      yes      no

Chassis Cluster Interfaces⌗

{primary:node0}
root@lab_SRX220_Top> show chassis cluster interfaces    
Control link status: Up

Control interfaces: 
    Index   Interface        Status
    0       fxp1             Up    

Fabric link status: Up

Fabric interfaces: 
    Name    Child-interface    Status
                               (Physical/Monitored)
    fab0    ge-0/0/5           Up   / Up  
    fab0   
    fab1    ge-3/0/5           Up   / Up  
    fab1   

Redundant-ethernet Information:     
    Name         Status      Redundancy-group
    reth0        Up          1                
    reth1        Up          1                
   
Redundant-pseudo-interface Information:
    Name         Status      Redundancy-group
    lo0          Up          0                

Interface Monitoring:
    Interface         Weight    Status    Redundancy-group
    ge-0/0/2          255       Up        1   
    ge-3/0/2          255       Up        1   
    ge-3/0/1          255       Up        1   
    ge-0/0/1          255       Up        1   

{primary:node0}

Disconnection⌗

As everything is as expected, I have disconnected interface ge-0/0/1 and by running the same commands we are able to see that the link failure has been detected by running show chassis cluster interface command

{primary:node0}[edit]
root@lab_SRX220_Top# run show chassis cluster interfaces       
Control link status: Up

Control interfaces: 
    Index   Interface        Status
    0       fxp1             Up    

Fabric link status: Up

Fabric interfaces: 
    Name    Child-interface    Status
                               (Physical/Monitored)
    fab0    ge-0/0/5           Up   / Up  
    fab0   
    fab1    ge-3/0/5           Up   / Up  
    fab1   

Redundant-ethernet Information:     
    Name         Status      Redundancy-group
    reth0        Up          1                
    reth1        Up          1                
   
Redundant-pseudo-interface Information:
    Name         Status      Redundancy-group
    lo0          Up          0                

Interface Monitoring:
    Interface         Weight    Status    Redundancy-group
    ge-0/0/2          255       Up        1   
    ge-3/0/2          255       Up        1   
    ge-3/0/1          255       Up        1   
    ge-0/0/1          255       Down      1

And running show chassis cluster status we can see that redundancy group 1 has failed over from Node0 to Node1.

{primary:node0}[edit]
root@lab_SRX220_Top# run show chassis cluster status            
Cluster ID: 1 
Node                  Priority          Status    Preempt  Manual failover

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

Redundancy group: 1 , Failover count: 34
    node0                   0           secondary      yes      no  
    node1                   1           primary        yes      no

As I have configured preempt on redundancy group 1, once the link (ge-0/0/1) is reconnected, it will automatically fail back to Node0

Post Verfication⌗

Chassis Cluster Interface⌗

{primary:node0}[edit]
root@lab_SRX220_Top# run show chassis cluster interfaces    
Control link status: Up

Control interfaces: 
    Index   Interface        Status
    0       fxp1             Up    

Fabric link status: Up

Fabric interfaces: 
    Name    Child-interface    Status
                               (Physical/Monitored)
    fab0    ge-0/0/5           Up   / Up  
    fab0   
    fab1    ge-3/0/5           Up   / Up  
    fab1   

Redundant-ethernet Information:     
    Name         Status      Redundancy-group
    reth0        Up          1                
    reth1        Up          1                
   
Redundant-pseudo-interface Information:
    Name         Status      Redundancy-group
    lo0          Up          0                

Interface Monitoring:
    Interface         Weight    Status    Redundancy-group
    ge-0/0/2          255       Up        1   
    ge-3/0/2          255       Up        1   
    ge-3/0/1          255       Up        1   
    ge-0/0/1          255       Up        1

Chassis Cluster Status⌗

{primary:node0}[edit]
root@lab_SRX220_Top# run show chassis cluster status        
Cluster ID: 1 
Node                  Priority          Status    Preempt  Manual failover

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

Redundancy group: 1 , Failover count: 35
    node0                   100         primary        yes      no  
    node1                   1           secondary      yes      no

My next post in this series, will demonstrate the methods of upgrading Junos version on a SRX cluster.