Junos OS

I'm having problems migrating a MC-LAG configuration from a QFX5100 to a QFX10002.  I'm able to assign the local IP and commit.  Then when I go to add the peer it fails.  This is the error:

error: Failed Reading Default configuration database:

error: configuration check-out failed

Here's the config for ICCP:

local-ip-addr 10.255.255.0;

peer 10.255.255.1 {

    session-establishment-hold-time 50;

    liveness-detection {

        minimum-receive-interval 1000;

        transmit-interval {

            minimum-interval 1000;

        }

    }

}

Hello,

For ICCP link, local & peer IP addresses should be any valid IP addresses on two units of QFX.

Can you share configuration of interfaces on both nodes/units which you are trying to configure as Local & Peer?

Regards,

Rushi

Here's the configuration of the interfaces.  They are pingable... 10.255.255.0 can ping 10.255.255.1 and 10.255.255.1 can ping 10.255.255.0.

** Common interface configurations on both switches:

et-0/0/70 {

    ether-options {

        802.3ad ae0;

    {

{

et-0/0/71 {

    ether-options {

        802.3.ad ae0;

    }

}

ae0 {

    unit 0 {

        family ethernet-switching {

            interface-mode trunk;

            vlan {

                members ICCP-VLAN;

            }

        }

    }

}

** Common VLAN configuration on both switches:

ICCP-VLAN {

    vlan-id 4094;

    l3-interface irb.4094;

}

** Switch 1 interface configuration:

irb {

    unit 4094 {

        family inet {

            address 10.255.255.0/31;

        }

    }

}

** Switch 2 interface configuration:

irb {

    unit 4094 {

        family inet {

            address 10.255.255.1/31;

        }

    }

}

i am curious if perhaps QFX10k requires the "redundancy-group" construct that MX / EX9200 requires, but the QFX5100 does not.

try:

set protocols iccp peer <peer-ip> redundancy-group-id-list 1

and then if you have any MC-LAGs configured yet, do:

set interfaces aeX aggregated-ether-options mc-ae redundancy-group 1

Thanks,

Will

Yes, that was the solution... our local Juniper RE queried folks inside Juniper with more knowledge on the QFX10K's and that's what they told us.