Re: error: Could not connect to node1 : No route to host - after power failure

Hi,

Thanks for reading the post this far!

I'm wondering if I've got my fabric ports set up right,

    fab0 {
        fabric-options {
            member-interfaces {
                ge-0/0/0;
                ge-0/0/7;
            }
        }
    }
    fab1 {
        fabric-options {
            member-interfaces {
                ge-5/0/0;
            }
        }
    }

ge-0/0/0 is connected to cisco Core1 switch port g0/19 which is an access port on vlan 30

ge-0/0/7 is connected to cisco Core2 switch port g0/19 which is an access port on vlan 30

ge-5/0/0 is connected to cisco Core3 switch port g0/19 which is an access port on vlan 30

vlan 30 is carried from and to Core1, Core2 and Core3 on G0/25 to the WAN switch. (see previous image)

When a node is powered down I get a lot of errors on the cisco switch about macs flapping between ports g0/19 and g0/25.

ge-0/0/1 and ge-5/0/1 are the Juniper control ports, they are connected to cisco Core1 and Core3 respectively on g0/5 which are access ports to vlan 4094. vlan 4094 is also carried between switches via g0/25 through the WAN switch. (MTU is 9014)

When a node is powered off I also get errors on the cisco switch stating that g0/5 is connected to g0/19.

--

So after a power loss I have to shutdown all juniper ports on the cisco switch except the control and reboot both SRX nodes otherwise the cluster never recovers. Surely this is wrong? 

Once I've got the cluster converged all the cisco errors cease and I can re-enable the ports one at a time, but this does mean that failback from a power failure requires 30+ minutes of hands on down time.

--

Juniper support told me this issue is out of scope for them.