Maybe you could try to remove the authentication settings in the [proto isis 
level] config on the MX, and add instead some hello-authentication-* in the 
[proto isis interface blahblah level X] ?

Or better, configure the CRS to also authenticate LSP with lsp-password 
hmac-md5 blah level X, of course ?

-- 
regards,
Olivier Benghozi

Le 12 juin 2013 à 17:08, John Neiberger <[email protected]> a écrit :
> 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.


_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to