[j-nsp] MC-LAG error on MX-104

Marcelio Webster marcelio.webster at gmail.com
Fri Dec 11 11:49:19 EST 2015


Hi!


Send us the configurations
Tks

2015-12-11 10:39 GMT-02:00 Brijesh Patel <brju.patel at gmail.com>:

> Hello All,
>
> I am trying to setup MC-LAG between tow MX104 .For the same status of ICCP
> is up but interface MC-AE state is "Current State Machine's State: *mcae
> config exchange error*"
>
> Below is snap of
>
> manager at MX1# *run show interfaces mc-ae*
>  Member Link                  : ae1
> * Current State Machine's State: mcae config exchange error*
>  Local Status                 : active
>  Local State                  : down
>  Peer Status                  : Unknown
>  Peer State                   : down
>      Logical Interface        : ae1.0
>      Topology Type            : bridge
>      Local State              : up
>      Peer State               : Unknown
>      Peer Ip/MCP/State        : 10.8.0.2 ae0.0 up
>
> manager at MX1#* run show iccp detail*
>
> Redundancy Group Information for peer 10.8.0.2
>   TCP Connection       : Established
>   Liveliness Detection : Up
>   Redundancy Group ID          Status
>     1                           Up
>
> Client Application: l2ald_iccpd_client
>   Redundancy Group IDs Joined: 1
>
> Client Application: lacpd
>   Redundancy Group IDs Joined: 1
>
> Any one has idea what could be reason for *mcae config exchange error*
> and *peer
> status is down.*
>
> Many Thanks,
>
> Brijesh Patel
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list