Configuring IS-IS in a Network
There are two ways to configure your network model to use IS-IS.
- Import router configuration files. These files automatically set model attributes. Some of the attributes set from router configuration files are not yet used in discrete event simulation. For procedures about performing an import, see the eXpress Data Import User Guide.
- Manually configure IS-IS parameters on each router running IS-IS. Note that not all attributes appearing in the dialog boxes are used in the simulation — only those described in Model Attributes: IS-IS are implemented. The remainder of this section describes manual configuration.
This section covers two methods for configuring IS-IS:
Basic Configuration of an IS-IS Model
When manually configuring IS-IS, you can run IS-IS using the default configuration, or you can customize it. To use the default settings, you need to do the following two steps:
Procedure 72: Configuring IS-IS in a Network (Basic Configuration)
-
Designate IS-IS on appropriate router interfaces. See “Configuring Routing Protocols” on page 18 for more information.
-
Assign a Network Entity Title (NET) to each router in the network that is running IS-IS. A NET identifies the router in the IS-IS domain, like the Router ID does in OSPF. There are three parts in a NET: an Area ID, a System ID, and an N-Selector.
Figure 307: Parts of a Network Entity Title (NET)

The NET is specified in the IP Routing Protocols > IS-IS Parameters > Processes > Process Parameters > Network Entity Titles > Network Entity Title attribute. You can specify more than one NET for a router, but they must have the same N-Sel and System ID—only the Area ID can vary.
When selecting a NET for a router, observe the following rules.
- Use hexadecimal digits, with two hexadecimal digits per byte. Typically, one dot is placed as a separator after every four hexadecimal digits. Separators are not required, but when they are used, they may only be dots. No other characters are permitted in the NET.
- The N-Selector is always 00.
- Each router must have a unique System ID. The number of digits in the System ID depends on the System ID length, a configurable parameter in the model.
- The Area ID comprises all digits preceding the System ID. There is no fixed length for the Area ID. Usually a length of 2 bytes (4 hex digits) is good enough. Different routers in the network can have the same Area ID, which places these routers in the same IS-IS area.
End of Procedure 72
Following Procedure 72 is sufficient to run the IS-IS protocol with default parameters. Using this procedure, you are configuring the following IS-IS features in a default manner:
- Use of Levels and Areas. The IS-IS protocol allows you to configure two-level hierarchical routing and areas. Areas typically enable you to restrict the amount of routing information exchanged between routers of different areas. By default, all routers operate at both levels; in this configuration, partitioning the network into areas produces no significant differences.
- System ID Length. The model permits a variable System ID length. On most routers, the System ID length is fixed at 6 bytes, which is the model’s default value. When defining the System ID in the NET, a System ID length of 6 bytes corresponds to 12 hexadecimal digits.
- No route redistribution into IS-IS. IS-IS does not learn routes from other routing protocols.
- IS-IS parameters on a per interface basis (circuit type, metric, router priority, and so on). These parameters are discussed later in this section, should you choose to configure them.
Advanced Configuration of an IS-IS Model
In addition to using Procedure 72, you can configure advanced IS-IS parameters. This section provides the following:
- Reducing the IS-IS Routing Table Size for Flow Analysis Studies
- Configuring Advanced IS-IS Parameters
Reducing the IS-IS Routing Table Size for Flow Analysis Studies
If you have a rather large network model and want to study basic connectivity between loopback interfaces on given IS-IS routers, use the following preference:
- Advertise loopback interfaces only for IGP routing protocols—Specifies if IGP routing protocols will only advertise loopback interfaces during the process of routing table generation. Enabling this preference may improve analysis performance due to fewer prefixes being advertised, thereby keeping the routing tables small. By default, this preference is disabled.
Note: This preference affects Flow Analysis only.
Configuring Advanced IS-IS Parameters
If you want to configure IS-IS to its fullest extent, use the following procedure as a guideline for configuring each router’s IS-IS Parameters.
Procedure 73: Configuring IS-IS in a Network (Additional Steps for Advanced Configuration)
-
Partition your network into Levels and Areas.
You can partition your network into areas and define a backbone that will be used for routing between areas. Routers that are part of the same area will know how to reach each other through other routers in the area. To reach a router in a different area, the routers must go through the backbone. Routers in the backbone are Level-2 routers and routers that are part of a particular area are Level-1 routers. You can configure some routers to belong to a particular area and to the backbone. These are Level-1-2 routers. A router’s level is configured in the System Type attribute. Areas are configured by appropriately defining the Area ID portion of the NET.
-
Configure the Metric Style.
The original IS-IS specification (ISO 10589) defined the maximum link metric as 63 (Narrow metrics). Extensions to the protocol increased the maximum metric value to 16777215 (Wide metrics). This parameter is configured in the IP Routing Protocols > IS-IS Parameters > Processes > Process Parameters > Metric Style attribute.
-
Configure the SPF Calculation Parameters.
You can specify how often IS-IS calculates its routing tables for each level, Level-1 and Level-2. This is done in the Minimum Interval attribute. A lower value for these attributes will result in faster convergence times but can require more processing time, thus slowing down the simulation.
-
Configure the System ID Length.
By default, the system ID length is 6 bytes. This value is not usually modified since most vendors use a fixed value of 6 bytes. If you would like to try out other values to see the effect of different system ID lengths, make sure that the same system ID length is used throughout the network. Also, remember that the system ID length affects the NET, so be sure to adjust the system ID portion of the NETs in the network accordingly.
-
Configure the Maximum Area Addresses.
IS-IS allows you to specify more than one Area ID for an area. These multiple Area IDs are like multiple aliases for the same area. This allows you to merge two areas by configuring one router to have the Area IDs of both areas. The Maximum Area Addresses attribute sets an upper limit on the number of Area IDs a router can have. Most vendors fix this parameter at 3, which is the model’s default value. Since only the Area ID portion of the NET can vary, this value is the maximum number of NETs that can be configured on the router.
-
Configure the interface Circuit Type.
If you set the router’s System Type to either Level-1 or Level-2, you must set the Circuit Type for each interface to the same Level. However, if the router’s System Type is Level-1-2, any value can be selected as the Circuit Type for each interface. The circuit type determines the kind of adjacency (Level-1, Level-2 or both) formed with the neighbor on that interface.
-
Configure the Metric for an interface.
Configure the metric corresponding to the interface’s circuit type: Level 1, Level 2, or both for Level-1-2.
Note: When you have a single link selected in the project editor, you can select the “Asymmetric metrics” checkbox and apply a different metric to each interface on the link.
End of Procedure 73