On Mon, Sep 18, 2017 at 01:12:36PM +0000, Eric Van Tol wrote: > > Have you tried enabling BGP traceoptions to see if that logs more useful > > diagnostics? > > Yes, per my first message: > > >I also see absolutely nothing when I enable traceoptions on the > >peer in LS1 and with MX2 attempting to contact LS1 > > Nothing helpful in those, with all flags enabled, both sides show the same > thing: > > bgp_connect_complete: error connecting to x.x.x.x (Internal AS xxxxx): Socket > is not connected > > Again, I don't even see a TCP SYN being sent in the 'monitor traffic > interface' output on the only active interface in LS1, as though it's being > dropped before it even hits the wire.
Is the correct interface and unit number specified inside the logical-system on both sides? Have you tried deleting the config, commit full, rollback? _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
