Can't get cluster of SRX100 working

Two SRX100. Ports 5 and 7 are connected using crossover. Port 6 (on both) are connected to our management network. node0:

 

## Last commit: 2017-02-14 01:26:13 UTC by indeni
version 12.1X46-D35.1;
groups {
    node0 {
        system {
            host-name juniper_srx01;
            backup-router 172.16.20.1 destination [ 0.0.0.0/0 172.16.16.0/24 ];
        }
        interfaces {
            fxp0 {
                unit 0 {
                    family inet {
                        address 172.16.20.51/24;
                    }
                }
            }
        }
    }
    node1 {
        system {
            host-name juniper_srx02;
            backup-router 172.16.20.1 destination [ 0.0.0.0/0 172.16.16.0/24 ];
        }
        interfaces {
            fxp0 {
                unit 0 {
                    family inet {
                        address 172.16.20.52/24;
                    }
                }
            }
        }
    }
}
apply-groups "${node}";
system {
    root-authentication {
        encrypted-password BLAHBLAH
    }
    name-server {
        208.67.222.222;
        208.67.220.220;
        8.8.8.8;
    }
    login {
        user admin {
            uid 2000;
            class super-user;           
        }
        user myuser {
            uid 2001;
            class super-user;
            authentication {
        encrypted-password BLAHBLAH
            }
        }
    }
    services {
        ftp;
        ssh;
        telnet;
        xnm-clear-text;
        web-management {
            http {
                interface vlan.0;
            }
            https {
                system-generated-certificate;
                interface vlan.0;
            }
        }
    }
    max-configurations-on-flash 5;
    max-configuration-rollbacks 5;
    license {
        autoupdate {
            url https://ae1.juniper.net/junos/key_retrieval;
        }
    }
}
chassis {
    cluster {
        reth-count 2;
        redundancy-group 0 {
            node 0 priority 100;
            node 1 priority 1;
        }
        redundancy-group 1 {
            node 0 priority 100;
            interface-monitor {
                fe-0/0/0 weight 255;
                fe-0/0/1 weight 255;
                fe-1/0/0 weight 255;
                fe-1/0/1 weight 255;
            }                           
        }
    }
}
interfaces {
    fe-0/0/0 {
        fastether-options {
            redundant-parent reth0;
        }
        unit 0 {
            family inet;
        }
    }
    fe-0/0/1 {
        fastether-options {
            redundant-parent reth1;
        }
    }
    fe-1/0/0 {
        fastether-options {
            redundant-parent reth0;
        }
    }
    fe-1/0/1 {
        fastether-options {
            redundant-parent reth1;
        }
    }
    fab0 {
        fabric-options {
            member-interfaces {
                fe-0/0/5;
            }
        }
    }
    fab1 {
        fabric-options {
            member-interfaces {
                fe-1/0/5;
            }
        }
    }
    reth0 {
        redundant-ether-options {
            redundancy-group 1;
        }
        unit 0 {
            family inet {               
                address 10.10.10.200/24;
            }
        }
    }
    reth1 {
        redundant-ether-options {
            redundancy-group 1;
        }
    }
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop 172.16.20.1;
    }
}
security {
    zones {
        security-zone untrust;
        security-zone trust;
    }
}

{primary:node0}

 

show chassis cluster information:

node0:
--------------------------------------------------------------------------
Redundancy Group Information:

    Redundancy Group 0 , Current State: primary, Weight: 255

	Time            From           To             Reason
        Feb 14 01:00:21 hold           secondary      Hold timer expired
        Feb 14 01:00:37 secondary      primary        Only node present

    Redundancy Group 1 , Current State: primary, Weight: -510

	Time            From           To             Reason
        Feb 14 01:06:32 hold           secondary      Hold timer expired
        Feb 14 01:06:58 secondary      primary        Control & Fabric links down

Chassis cluster LED information:
    Current LED color: Amber
    Last LED change reason: Monitored objects are down
Control port tagging:
    Disabled

Failure Information:

    Interface Monitoring Failure Information:
        Redundancy Group 1, Monitoring status: Unhealthy
	  Interface                 Status
          fe-0/0/1                  Down          
          fe-0/0/0                  Down          

    Fabric-link Failure Information:
        Fabric Interface: fab0
          Child interface   Physical / Monitored Status     
          fe-0/0/5              Down / Down 
 error: Could not connect to node1 : No route to host

 On node1:

The config didn't sync, it's still with a basic config:

## Last commit: 2017-02-14 08:53:32 UTC by indeni
version 12.1X44-D35.5;
system {
    root-authentication {
        encrypted-password BLAHBLAH
    }
    name-server {
        208.67.222.222;
        208.67.220.220;
    }
    login {
        user admin {
            uid 2000;
            class super-user;
        }
        user myuser {
            uid 2001;
            class super-user;
            authentication {
        encrypted-password BLAHBLAH
            }
        }
    }                                   
    services {
        ssh;
        telnet;
        xnm-clear-text;
        web-management {
            http {
                interface vlan.0;
            }
            https {
                system-generated-certificate;
                interface vlan.0;
            }
        }
        dhcp {
            router {
                192.168.1.1;
            }
            pool 192.168.1.0/24 {
                address-range low 192.168.1.2 high 192.168.1.254;
            }
            propagate-settings fe-0/0/0.0;
        }
    }                                   
    max-configurations-on-flash 5;
    max-configuration-rollbacks 5;
    license {
        autoupdate {
            url https://ae1.juniper.net/junos/key_retrieval;
        }
    }
}
interfaces {
    fe-0/0/0 {
        unit 0 {
            family inet;
        }
    }
}

 

Another point worth noting is that when I connect port 5 on node0 to a switch, it lights up. When I do the same with node1, it doesn't. Could this be a hardware issue?