[j-nsp] Strange BGP behaviour on 10.0R3

[Alex]

William,
Looks like someone is proxy-ARP-ing on behalf of your peer - and "proxy-arp" 
is the default Cisco Ethernet interface behaviour, BTW.
Configure a static ARP entry on Your MX for Your peer and You should be OK.
Rgds
Alex

----- Original Message ----- 
From: "William Jackson" <wjackson at sapphire.gi>
To: <juniper-nsp at puck.nether.net>
Sent: Tuesday, October 12, 2010 10:48 AM
Subject: [j-nsp] Strange BGP behaviour on 10.0R3


> Hi
>
>
>
> We are seeing some strange behavior on an MX with 10.0R3.
>
>
>
> We have an Ethernet link to a switch where we have multiple eBGP peers.
>
> We and the peer are seeing the session come up and then expiring with
> hold-time received messages, other peers on the same segment work 100%.
>
>
>
> When doing a pcap we are seeing the following happen:
>
>
>
> Setup and establish session BGP session.
>
> Once established our router then starts to send the updates to the
> correct IP address but a different MAC.  The pcap doesn't show any
> strange ARP behaviour, the MAC address that is suddenly used belongs to
> another peer.
>
>
>
> The session then obviously times out, we haven't seen messages or
> indicators as to why this is happening.  JTAC are looking at it but
> don't seem to know why either.
>
> Anyone else seen this type of behavior?
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>