User guide

Configuring IS-IS Configuring IS-IS
OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 3-21
To disable the authentication check for IS-IS PDUs, enter the following:
-> ip isis auth-check disable
If disabled, the authentication PDUs are generated and the IS-IS PDUs are authenticated on receipt. An
error message will be generated in case of a mismatch; but PDUs will not be rejected.
IS-IS authentication can be enabled globally for Hello, CSNP, and PSNP packets.
To enable the authentication of Hello PDUs globally, enter the following:
-> ip isis hello-auth
To enable the authentication of CSNP PDUs globally, enter the following:
-> ip isis csnp-auth
To enable the authentication of PSNP PDUs globally, enter the following:
-> ip isis psnp-auth
Level Authentication
You can enable authentication and configure the authentication types for specific IS-IS levels globally
using ip isis level auth-type command. For example:
-> ip isis level 2 auth-type md5 encrypt-key 7a1e441a014b4030
The above example configures the authentication type as MD5 for level 2 IS-IS PDUs and the key.
IS-IS authentication can be enabled for specific IS-IS PDUs such as Hello, CSNP, and PSNP packets at
specific IS-IS levels (Level-1, Level-2, or Level-1/2). Enabling authentication on specific IS-IS levels
over-rides the global authentication.
To enable the authentication of Hello PDUs for IS-IS Level-1, enter the following:
-> ip isis level 1 hello-auth
To enable the authentication of CSNP PDUs for IS-IS Level-2, enter the following:
-> ip isis level 2 csnp-auth
To enable the authentication of PSNP PDUs for IS-IS Level-2, enter the following:
-> ip isis level 2 psnp-auth
Note. By default, authentication check is enabled.
Note. You can configure the authentication of either simple or MD5 type with the password specified either
in plain text or in encrypted form. For the explanations about the authentication types and the key types
refer Simple authentication and MD5 authentication.
Note. On a point-to-point link with both levels enabled, if no authentication is configured for Level 1, the
hello packets are sent without any password regardless of the Level 2 authentication configurations.