Well, the captures and the info I got from the router proved that the router was not sending neighbor solicitations when new traffic was arriving. However, when I pinged that destination from the directly connected router itself, it did work. It's probably a bug and Juniper will just tell us to upgrade, and rightfully so. I just hope we can find a workaround in the interim.
On Tue, Dec 24, 2013 at 9:04 AM, John Neiberger <jneiber...@gmail.com> wrote: > We're in the process of upgrading all of our MXs running older code, > but we haven't gotten to this router just yet. We are upgrading to > some flavor of 11.4, as I recall. I have someone working on getting a > capture, but I will grab what I can using "monitor traffic interface". > > Thanks! > John > > On Tue, Dec 24, 2013 at 3:08 AM, <sth...@nethelp.no> wrote: >>> I'm running into an odd problem that seems to be related to v6 >>> neighbor discovery on an MX960 running 9.6R4. Here is a simplified >>> topology for explanation: >> ... >>> Have any of you run into this type of situation? it sure is starting >>> to look like a bug in this code where it isn't actually sending an NS >>> message upon the arrival of traffic destined for a neighbor not in the >>> cache. >> >> Sorry, never seen this. Getting a packet capture from the server >> sounds like a good idea - however, you should also be able to see >> any IPv6 NS/ND activity by using "monitor traffic interface ..." >> on the RouterB interface towards the host. >> >> Also, you might want to consider a newer JunOS release. 9.6 is EOL. >> Personally I would recommend at least 11.4R8. >> >> Steinar Haug, Nethelp consulting, sth...@nethelp.no _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp