nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

1. Enable IS-IS.
2. Configure the IS-IS instance.
3. Assign interfaces to the IS-IS instance.
4. Verify the IS-IS operation.
The first step to configure IS-IS is to enable it in global configuration mode using the
feature command, as demonstrated in Example 3-71. With the modular nature of NX-OS,
using the feature command loads the IS-IS modular code into memory for execution.
Without the feature enabled, it would not be resident in memory.
Example 3-71. Enabling the IS-IS Feature
Click here to view code image
Congo# config t
Enter configuration commands, one per line. End with
CNTL/Z.
Congo(config)# feature isis
Congo(config)# show run isis
!Command: show running-config isis
!Time: Fri Sep 28 16:20:04 2012
version 5.2(3a)
feature isis
The next step is to configure the IS-IS routing instance, as demonstrated in Example 3-72.
NX-OS requires an instance tag configured for the process. Traditionally in IOS this would
be a device-specific instance tag. In NX-OS, the instance tag can be a device-specific tag,
or the instance tag can be up to 20 case-sensitive, alphanumeric characters. This helps
document the network configuration and can simplify device identification. The following
example illustrates configuring IS-IS with an alphanumeric instance tag.
IS-IS also requires configuration of a Network Entity Title (NET) and an optionally defined
Level type. The NET is composed of the IS-IS system ID, which uniquely identifies this IS-
IS instance in the area and the area ID. For example, if the NET is
47.0004.004d.0001.0001.0c11.1111.00, the system ID is 0001.0c11.1111.00, and the area
ID is 47.0004.004d.0001. The Level type defaults to level-1-2 but can be configured
specifically to level-1 or level-2.
Example 3-72. Configuring the IS-IS Instance
Click here to view code image