On the Juniper side we only have authentication configured under "protocols isis level 2".
On Wed, Jun 12, 2013 at 10:22 AM, Bikram Singh <[email protected]> wrote: > have you configured authentication on interface(in ISIS) as well on mx960? > > - B > > > From: [email protected] > > Date: Wed, 12 Jun 2013 09:08:54 -0600 > > To: [email protected] > > Subject: [j-nsp] ISIS authentication issue > > > > > We've got an MX960 connected to a Cisco CRS, both of which are configured > > for ISIS authentication. However, the CRS is currently configured for > only > > hello authentication. It appears that Junos enables both hello > > authentication and CSNP/PSNP authentication by default. This is allowing > > the adjacency to come up but the MX960 drops subsequent CSNP/PSNP packets > > because they are not authenticated. I wanted to disable this, so at the > > same level we configured ISIS authentication I added the following: > > > > no-psnp-authentication > > no-csnp-authentication > > > > However, that didn't work and I can't figure out why. The MX960 continued > > to drop CSNP and PSNP packets because of authentication. I suspect that I > > might have needed to clear the adjacency with that neighbor but I really > > don't know. I expected it to start working immediately. > > > > Any ideas? > > > > Thanks, > > John > > _______________________________________________ > > juniper-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
