level (Global IS-IS)

The IS-IS device level number, which can be 1 or 2. The default is for the device to operate as both a Level 1 and 2 device.

Authentication key (password). Neighboring devices use the password to verify the authenticity of packets sent from this interface. For the key to work, you also must include the authentication-type statement. All devices must use the same password. If you are using the Junos OS IS-IS software with another implementation of IS-IS, the other implementation must be configured to use the same password for the domain, the area, and all interfaces adjacent to the Juniper Networks device.

• key—Authentication password. The password can be up to 1024 characters long. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”).

Apply and enable an authentication key-chain to the routing device. The variable key-chain-name is the authentication key-chain name. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”).

Enable authentication and specify the authentication scheme for IS-IS. If you enable authentication, you must specify a password by including the authentication-key statement. If you do not include this statement and the authentication-key statement, IS-IS authentication is disabled. Following are the valid values for authentication:

• md5—Use HMAC authentication in combination with MD5. HMAC-MD5 authentication is defined in RFC 2104, HMAC: Keyed-Hashing for Message Authentication.

• simple—Use a simple password for authentication. The password is included in the transmitted packet, making this method of authentication relatively insecure.

  Note:

  Juniper Networks does not recommend using the simple authentication method, because it is not as secure as MD5.

Disable IS-IS on the routing device, on an interface, or on a level. Enabling IS-IS on an interface (by including the interface statement at the [edit protocols isis] or the [edit routing-instances routing-instance-name protocols isis] hierarchy level), disabling it (by including the disable statement), and not actually having IS-IS run on an interface (by including the passive statement) are mutually exclusive states. IS-IS is enabled for Level 1 and Level 2 routers on all interfaces on which family iso is enabled.

Configure the preference of external routes. The value for preference can be 0 through 4,294,967,295 (2³² – 1). The default is 15 (for Level 1 internal routes), 18 (for Level 2 internal routes), 160 (for Level 1 external routes), 165 (for Level 2 external routes).

Generate authenticated packets and check the authentication on received packets, but do not reject packets that cannot be authenticated.

Suppress authentication check on complete sequence number PDU (CSNP) packets.

Suppress authentication check on complete sequence number hello packets.

Suppress authentication check on partial sequence number PDU (PSNP) packets.

Configure the preference of internal routes. Route preferences (also known as administrative distances) are used to select which route is installed in the forwarding table when several protocols calculate routes to the same destination. The route with the lowest preference value is selected. To change the preference values, include the preference statement (for internal routes) or the external-preference statement. The value for preference can be 0 through 4,294,967,295 (2³² – 1). The default is 15 (for Level 1 internal routes), 18 (for Level 2 internal routes), 160 (for Level 1 external routes), 165 (for Level 2 external routes).

Enable purge originator identification (POI) by adding the type, length and value (TLV) with the Intermediate System (IS) identification to the LSPs that do not contain POI information. If an IS generates a purge, Junos adds this TLV with the system ID of the IS to the purge. If an IS receives a purge that does not include this TLV, it adds this TLV with both its own system ID and the system ID of the IS from which it received the purge. This allows the IS that receives this purge to log the system ID of the originator, or the upstream source of the purge and makes it easier to locate the origin of the purge.

• empty—(Optional) Add POI to a purge received from an IS that does not contain POI information.

• self—(Optional) (Optional) Add POI only to self-originated purge LSPs.

Configure IS-IS to generate metric values greater than 63 on a per IS-IS level basis. Normally, IS-IS metrics can have values up to 63, and IS-IS generates two type, length, and value (TLV) tuples, one for an IS-IS adjacency and the second for an IP prefix. To allow IS-IS to support traffic engineering, a second pair of TLVs has been added to IS-IS, one for IP prefixes and the second for IS-IS adjacency and traffic engineering information. With these TLVs, IS-IS metrics can have values up to 16,777,215 (2²⁴ – 1).

To configure IS-IS to generate only the new pair of TLVs and thus to allow the wider range of metric values, include the wide-metrics-only statement.