[AusNOG] AWS Direct Connect & Juniper

[Chris Kawchuk]

Check for a firewall filter on the egress of the interface, or a firewall filter applied to lo0.0 that's denying it/dropping it. (firewall family inet, interface unit x family inet filter input/output <x>, etc..)

If the interface is in a VR, you'll need to ping <1.1.1.1> routing-instance <your-VR>; likewise if in a VR, your BGP configuration needs to be in the [routing-instance <vrf> protocols bgp ] stanza.

JunOS "show arp" is always your friend, to see if you can at least L2-ARP for an address on that network. Posting relevant configlets/stanzas may also help.

- Ck.

On 23/01/2015, at 9:24 AM, Andrew Cowan <andycowan at gmail.com> wrote:

> 
> Layer 2 is up, we have done some port mirroring and can see the TCP SYN packets coming in on port 179, but the router isn’t sending anything back.  It may be routing rather than BGP because we can’t ping either.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20150123/6eebd886/attachment.html>