[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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange BGP behaviour on 10.0R3
Hi William, Have you tried enable pmtud in this session ? Tks On 10/12/10, William Jackson wjack...@sapphire.gi wrote: 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- Sent from my mobile device ./diogo -montagner ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange BGP behaviour on 10.0R3
Hello, Checking for bgp msgs stuck in the outgoing queue is also a good clue for mtu issues :-) Rgds, Christian Le 12/10/2010 13:42, Diogo Montagner a écrit : Hi William, Have you tried enable pmtud in this session ? Tks On 10/12/10, William Jacksonwjack...@sapphire.gi wrote: 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange BGP behaviour on 10.0R3
Stupid question, but have you tried simply clearing the arp cache and seeing what comes back? On Tue, Oct 12, 2010 at 5:48 AM, William Jackson wjack...@sapphire.giwrote: 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange BGP behaviour on 10.0R3
Also you could statically configure the correct MAC address to see if that works too... From: William Jackson wjack...@sapphire.gi To: juniper-nsp@puck.nether.net Sent: Tue, October 12, 2010 4:48:09 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
