05 Chapter5 Is Is Configuration

Operation Manual - IP Routing Volume
Quidway NetEngine20 Series Routers Table of Contents

Huawei Technologies Proprietary
i
Table of Contents
Chapter 5 IS-IS Configuration ...................................................................................................... 5-1
5.1 Introduction ........................................................................................................................ 5-1
5.1.1 Basic Concepts ....................................................................................................... 5-1
5.1.2 IS-IS Areas.............................................................................................................. 5-4
5.1.3 IS-IS Network Types ............................................................................................... 5-6
5.1.4 PDU Formats........................................................................................................... 5-8
5.1.5 IS-IS Features Supported by NE20 ...................................................................... 5-15
5.1.6 Protocols and Specifications................................................................................. 5-19
5.2 Configuring IS-IS Basic Functions................................................................................... 5-19
5.2.1 Establishing the Configuration Task...................................................................... 5-19
5.2.2 Enabling IS-IS Processes ..................................................................................... 5-20
5.2.3 Configuring NET.................................................................................................... 5-21
5.2.4 Enabling IS-IS on the Specified Interface ............................................................. 5-21
5.2.5 Configuring the Router Type................................................................................. 5-21
5.2.6 Configuring the Interface Type.............................................................................. 5-21
5.2.7 Configuring the Interface as Silent ........................................................................ 5-22
5.3 Controlling IS-IS Routing Information.............................................................................. 5-22
5.3.2 Configuring the Preference of IS-IS Protocol ........................................................ 5-23
5.3.3 Configuring the Link Cost...................................................................................... 5-24
5.3.4 Configuring IS-IS Route Aggregation.................................................................... 5-26
5.3.5 Configuring IS-IS to Generate Default Routes...................................................... 5-26
5.3.6 Configuring IS-IS to Filter the Received Routing Information............................... 5-26
5.3.7 Configuring IS-IS to Import External Routes......................................................... 5-27
5.3.8 Configuring Route Leaking.................................................................................... 5-27
5.4 Adjusting and Optimizing IS-IS........................................................................................ 5-27
5.4.2 Configuring DIS Priority of the Interface ............................................................... 5-29
5.4.3 Configuring IS-IS Packet Timers........................................................................... 5-29
5.4.4 Configuring LSP Parameters ................................................................................ 5-31
5.4.5 Configuring SPF Parameters ................................................................................ 5-33
5.4.6 Enabling LSP Fast Flooding.................................................................................. 5-34
5.4.7 Configuring Dynamic Hostname Mapping ............................................................ 5-35
5.4.8 Configuring IS-IS Authentication........................................................................... 5-36
5.4.9 Configuring LSDB Overload Flag Bit..................................................................... 5-37
5.4.10 Configuring to Log Peer Changes....................................................................... 5-37
5.5 Maintaining IS-IS.............................................................................................................. 5-38
Quidway NetEngine20 Series Routers Table of Contents

ii
5.5.1 Displaying the Running of IS-IS............................................................................ 5-38
5.5.2 Clearing IS-IS Data Structure................................................................................ 5-38
5.5.3 Resetting a Specific IS-IS Peer............................................................................. 5-39
5.5.4 Debugging IS-IS.................................................................................................... 5-39
5.6 Configuration Examples................................................................................................... 5-41
5.6.1 Example of Basic IS-IS Configurations................................................................. 5-41
5.6.2 Configuring the DIS Election of IS-IS.................................................................... 5-48
5.7 Troubleshooting............................................................................................................... 5-53
5.7.1 Neighbor Relationship Is Not Established with A Specific Peer ........................... 5-53
5.7.2 The Level-1 Router Has No Default Route to a Destination External to Its Area . 5-54

Quidway NetEngine20 Series Routers Chapter 5 IS-IS Configuration

5-1
As an Interior Gateway Protocol (IGP), IS-IS is used inside Autonomous System (AS).
5.1.1 Basic Concepts
I. Terms of IS-IS Routing Protocol
router of TCP/IP. It is the basic unit in the IS-IS
protocol. It is used for transmitting routing information and generating routes. In the
e communications
domain.
nk states in the network form the LSDB. In an IS,
and the LSDB to
generate its own routes.
LSDB.
router on a broadcast network. It can also be a DR.
Chapter 5 IS-IS Configuration
5.1 Introduction
Intermediate System-to-Intermediate System intra-domain routing information
exchange protocol (IS-IS) is a dynamic routing protocol. The International
Organization for Standardization (ISO) initially issued it for its Connectionless Network
Protocol (CLNP).
To support IP routing, the Internet Engineering Task Force (IETF) extends and
modifies IS-IS in RFC1195. This allows IS-IS to be applied to TCP/IP and OSI
environments at the same time. This kind of IS-IS is called the Integrated IS-IS or Dual
IS-IS.
IS-IS is a link state protocol. It uses the Shortest Path First (SPF) algorithm for route
calculation. It highly resembles the Open Shortest Path First (OSPF) protocol.
Intermediate System (IS): equals a
following text, "IS" has the same meaning as the "router".
End System (ES): equals the host system of TCP/IP. ES is not involved in IS-IS
processing. ISO has the dedicated ES-IS protocol to define th
between an ES and an IS.
Routing Domain (RD): a group of ISs exchange routing information through the same
routing protocol in a routing
Area: is the division unit in the routing domain.
Link State Database (LSDB): all the li
at least one LSDB is available. The IS uses the SPF algorithm
Link State Protocol Data Unit (LSP): in IS-IS, each IS generates an LSP which
contains all the link state information of the IS. Each IS collects all the LSPs in the local
area to generate its own
Network Protocol Data Unit (NPDU): it is the network layer packets of ISO and equals
the IP packet of TCP/IP.
Designated IS (DIS): an elected

5-2
access point and describes the network address structure of
II
address structure NSAP as shown in the following figure. NSAP
ain Specific Part (DSP).
ain network number of the IP address, and DSP the subnet
dress of the IP address.
chanism
ODSP), System ID and SEL. HODSP
Network Service Access Point (NSAP): a network layer address of ISO. It identifies an
abstract network service
the ISO model.
. Address Structure of IS-IS Protocol
1) NSAP
ISO adopts the
consists of the Initial Domain Part (IDP) and the Dom
IDP is equivalent to the m
number and host ad
Stipulated in the ISO, the IDP consists of Authority and Format Identifier (AFI) and
Initial Domain Identifier (IDI). The AFI specifies the address assignment me
and the address format. The IDI is used to identify a domain.
The DSP consists of High Order DSP (H
partitions areas, System ID identifies a host and SEL indicates the service type.
The length of IDP and DSP is variable. Their maximum total length is 20 bytes and
minimum is 8 bytes.
AFI IDI
SEL
High Order DSP SyStem ID
(1 octet)
DSP IDP
Area Address
Figure 5-1 Schematic diagram of the address structure of IS-IS
2) Area address
IDP, along with HODSP of DSP, can identify both a routing doma
routing domain. The combination of (IDP, HODSP) is therefore called as

in and areas in a
ea Address.
ry with areas.
Generally, a router needs to be configured with one area address only. Moreover, all
e area must have the same area address. To support seamless
Ar
It is equivalent to the area ID in OSPF. The area addresses va
the nodes in the sam
combination, division and transformation of areas, a router can be configured with at
the most three area addresses.
3) System ID
A system ID is used to uniquely identify a host or a router in an area. Its invariable
length is 48 bits (6 bytes).

5-3
of the interface Loopback0 as its router ID,.Then its
IS-IS can be transformed with the following method:
ress 168.010.001.001 into three parts, with each part
can uniquely
4)
protocol ID of IP d to different SELs. The
over IP
f address structure definitely defines an area, Level-1 routers can easily
ckets sent to an outside area. These packets are to be forwarded to Level-2
plement intra-area routing. Once a Level-1 router
acket is out of its own area, it will forward it to a
r.
III k Entity Title
th of NET is the same as that of NSAP. It can be 20 bytes

only consider NET, regardless of NSAP.
nly configured with one NET. When it is necessary to
can be configured on an IS-IS process of a
router, three NETs can be configured at most. When configuring multiple NETs, make
Area = ab.cdef, System ID = 1234.5678.9abc, SEL = 00.
Normally, a router ID is adopted to correspond with a system ID. Suppose a router
takes the IP address 168.10.1.1
system ID used in
Extend every part of the IP address 168.10.1.1 to three bits. Add 0 to the front of
the part that includes less than three bits.
Divide the extended add
consisting of four decimal digits.
The reconstructed 1680.1000.1001 is just the system ID.
Actually, there are many ways to designate a system ID, as long as it
identify an ES or a router.
SEL
The role of an SEL (NSAP Selector, or N-SEL as called sometimes) is similar to the
. Different transportation protocols correspon
SEL is uniformed into "00.
5) Routing
As this kind o
identify pa
routers.
Level-1 routers use system ID to im
finds that the destination address of a p
nearest Level-1-2 route
Based on their addresses (IDP, HODSP), Level-2 routers perform inter-area routing.
. Networ
Network Entity Title (NET) indicates the network layer information of an IS itself. It
excludes the transport layer information (SEL = 0). It can be regarded as a special
NSAP. Therefore, the leng
long at most and 8 bytes long at least. When configuring IS-IS on a router, you can
Generally, a router is o
reconstruct an area, multiple NETs should be configured on a router. For example, to
combine many areas together or to divide an area into separate areas, we need to
configure multiple NETs. Route correctness is thus guaranteed even upon
reconfiguration.
Since at the most three area addresses
sure that their system IDs are identical.
For example, there is a NET ab.cdef.1234.5678.9abc.00, in which,

5-4
5.1.2 IS-IS
I.
as. Intra-area routing is managed by Level-1
II
1) Level-1 router
router manages the intra-area routing. It establishes the neighbor
relationship only with Level-1 and Level-1-2 routers in the same area. It maintains a
).
A Level-2 router manages the inter-area routing. It can form the neighbor relationship
Level-1-2 routers in other areas. It maintains a Level-2 LSDB.
information between the areas. All Level-2 routers form the
f the backbone network. Only Level-2 routers can
exchange the data packets or the routing information with routers outside the routing
ngs to both Level-1 area and Level-2 area, is called a Level-1-2
relationship with the Level-2 routers and Level-1-2 routers in other areas.
Areas
Two-Level Structure
To support large-scale routing networks, IS-IS adopts a two-level structure in an RD. A
large RD is divided into one or more are
routers while inter-area routing is managed by Level-2 routers.
. Level-1 and Level-2
A Level-1
Level-1 link state database (LSDB
The LSDB contains the routing information for the local area. A packet to a destination
outside this area is forwarded to the nearest Level-1-2 router.
2) Level-2 router
with Level-2 routers and
The LSDB contains routing
backbone network of the routing domain. They are responsible for communication
between the different areas. The Level-2 routers in the routing domain must be in
succession to ensure the continuity o
domain.
3) Level-1-2 router
A router, which belo
router. It can form the Level-1 neighbor relationship with the Level-1 routers and
Level-1-2 routers in the same area. In addition, it can form the Level-2 neighbor
A Level-1 router must be connected to other areas through a Level-1-2 router. A
Level-1-2 router maintains two LSDBs. The Level-1 LSDB is used for intra-area
routing and the Level-2 LSDB for inter-area routing.

Note:

The Level-2 routers can form neighbor relationships regardless of areas.
The Level-1 routers in different areas cannot form a neighbor relationship.


5-5
s. They are connected to Area 1
h Level-1-2 routers.
Figure 5-2 illustrates an IS-IS enabled network, similar to an OSPF typology with
multiple areas. The Area 1 is a backbone area. All routers in this area are Level-2
routers. The other four areas are non-backbone area
throug
Area1
Area3
Area5
Area4
Area2
L1
L1/2
L1/2
L2
L2
L2 L2
L1 L1
L1
L1
L1
L1/2
L1/2

Level-1-2 routers are not only
so form the backbone network
a is defined as a backbone
They may belong to different
Figure 5-2 IS-IS topology I
Figure 5-3 shows another kind of IS-IS typology. The
used to connect Level-1 and Level-2 routers, but al
together with other Level-2 routers. In this typology, no are
area. The backbone network contains all Level-2 routers.
areas, but they must be successive.
Area1
Area3
Area4 Area2
L1
L2
L1/L2
L1
L1

Note:
L1/L2
L2
L2

Figure 5-3 IS-IS typology II
The IS-IS backbone network does not indicate a specific area.


5-6
S-IS and OSPF. For
one area, and the SPF
nd Level-2 routers
(SPT) respectively.
ghbor relationship with
nship with another peer.
You can limit the relationships that can be established on the interface by configuring
xample, you can specify that the level-1 interfaces only
establish Level-1 neighbor relationships and the level-2 interfaces only establish
eighbor relationships.
For a Level-1-2 router, you can configure some interfaces to Level-2. This prevents
packets from being sent to the Level-2 backbone network. It helps save
IV. Route Leaking
Usually, an IS-IS area is called a Level-1 area and the intra-area routes are managed
not be
mutually connected.
otify their routing information to the Level-2 area through the
Level-1-2 routers. Thus, the routers in the Level-2 area can obtain the routing
Level-2 routers, by default, do not advertise the routing information of Level-1 areas
utes are allowed to leak from Level-2 to Level-1. This
5.1.3 IS-IS Network Types
I. Network Types
Broadcast links: for example, Ethernet and Token-Ring.
Point-to-point links: for example, PPP and HDLC.
This kind of networking scheme shows the difference between I
OSPF, the inter-area routes are forwarded by the backb
algorithm is only used in the same area. For IS-IS, both Level-1 a
use the SPF algorithm to generate the Shortest Path Tree
III. Interface Types
The Level-1-2 routers may need to establish the Level-1 nei
only a certain peer and establish the Level-2 neighbor relatio
the interface types. For e
Level-2 n
Level-1 hello
the bandwidth.
by Level-1 routers. All Level-2 routers form a Level-2 area. Therefore, a routing
domain can contain multiple Level-1 areas but only one Level-2 area.
The Level-1 areas can only be connected to the Level-2 area. They can
All Level-1 areas n
information of the entire IS-IS routing domain.
and the Level-2 areas known to any Level-1 area. Therefore, routers in Level-1 area
cannot obtain routing information outside the area. This makes the optimal routing to
the destination addresses outside the area, unavailable.
To address the problem, IS-IS ro
enables routers in the specified Level-1 area to learn the routing information outside
the area.
IS-IS only supports two network types, which can also be divided based on physical
links:

5-7
ces for it and configure the sub-interfaces as point-to-point or
II
In broadcast networks, the IS-IS needs to elect a Designated Intermediate System
e same priority in the
S broadcast networks, the routers of the same level in the same network
segment can form adjacencies. All non-DIS routers can also form adjacencies. This is
s shown in Figure 5-4.
For Non-Broadcast Multi-Access (NBMA) networks such as ATM, you only need to
configure sub-interfa
broadcast networks. IS-IS cannot run on Point to MultiPoint (P2MP) networks.
. DIS and Pseudonodes
(DIS) from all the routers.
The DISs of Level-1 and Level-2 are elected respectively, and you can configure
different priorities for them. The higher the priority is, the more possible that the router
is selected as the DIS. If there are two or more routers with th
broadcast network, the one with the largest MAC address will be selected. The DISs of
different levels can be a same router or different routers.
In the IS-I
different from OSPF, a
L1/L2
L1 Adjacencies
L2 Adjacencies
L1/L2
L1
DIS
L2
DIS

Figure 5-4 DISs and adjacencies in IS-IS broadcast networks
, which describe the available routers on the network.
d thus SPF consumes less
Note:
DIS is used to create and update pseudo-nodes. It is also responsible for generating
LSPs of the pseudo-nodes
The pseudo-nodes simulate a virtual node in the broadcast network and are not real
routers. In the IS-IS, the pseudo-nodes are identified by the System ID of DIS and the
1-byte Circuit ID.
With the pseudo-nodes, the network typology is simpler and the LSP is shorter. When
the network changes, the router generate fewer LSPs an
resources.

In the IS-IS broadcast networks, although all routers form adjacencies with each other,
the synchronization of LSDBs are still ensured by DIS.

5-8
5.1.4 PDU Form
s. PDU consists of the
r consists of a common
e for all PDUs, but

ats
I. PDU Header
The IS-IS packets are directly encapsulated in data link frame
packet header and the variable length fields. The packet heade
header and a specific header. The common headers are the sam
the specific headers vary with PDUs, as shown in Figure 5-5.
PDU Common
Header
PDU Specific
Header
Variable Length
Fields(CLV)

II
the same common header, as shown in Figure 5-6.
Figure 5-5 PDU format
. Common Header
All the PDUs have
1
No. of Octets
Intradomain Routeing Protocol Discriminator
Length Indicator
PDU Type
Version
Reserved
R
Version/Protocol ID Extension
ID Length
Maximum Area Address
1
1
1
1
1
1
R R
1

Figure 5-6 PDU header format
The main fields are explained as follows:
Routing Protocol Discriminator: it is set to 0x83
icator: indicates the length of the PDU header (including the common
PDU Type: for details, refer to Table 5-1
Version: it is set to 1 (0x01)
Maximum Area Address: indicates the maximum number of areas supported
Intradomain
Length Ind
header and the specific header) in bytes
Version/Protocol ID Extension: it is set to 1 (0x01)
ID Length: indicates the ID lengths of the NSAP address and NET
R (Reserved): it is set to 0

5-9
Table 5-1 The PDU types
Type
value
PDU types Acronym
15 Level-1 LAN IS-IS Hello PDU L1 LAN IIH
16 Level-2 LAN IS-IS Hello PDU L2 LAN IIH
17 Point-to-Point IS-IS Hello PDU P2P IIH
18 Level-1 Link State PDU L1 LSP
20 Level-2 Link State PDU L2 LSP
24 Level-1 Complete Sequence Numbers PDU L1 CSNP
25 Level-2 Complete Sequence Numbers PDU L2 CSNP
26 Level-1 Partial Sequence Numbers PDU L1 PSNP
27 Level-1 Partial Sequence Numbers PDU L2 PSNP

II
Hello packets, also called IS-to-IS Hello PDUs (IIH), are used to establish and
em, the Level-1 LAN IIH applies to Level-1
te ters on broadcast
The ferent formats. The Hello packets in
gray is the common header):
I. Hello Packets
maintain neighbor relationship. Among th
rou rs on broadcast LAN, Level-2 LAN IIH applies to Level-2 rou
LAN and P2P IIH applies to non-broadcast networks.
packets in different networks have dif
broadcast networks have the following format (the part in

5-10
ID Length
No. of Octets
1
Intradom
PDU Length
Priority
LAN ID
R
Reserved/Circuit Type
Holding Time
Source ID
Variable Length Fields
ID Length+1
1
2
2
2
PDU Type
Version
Reserved
R
ain Routeing Protocol Discriminator
Length Indicator
ID Length
1
1
1
1
1
1
R
R
1

Figure 5-7 L1/L2 LAN IIH format
Reserved/Circuit Type: The first six bits are reserved and are all 0s. The last two
bits indicate the type of the router (01 indicate
indicates L1/L2).
Source ID: indicates the System ID of the router sen
Holding Time: If a router does not receive Hello pa
period of time, it terminates the established neighbo
PDU Length: indicates the total length of a PDU in bytes.
Priority: priority configured for DIS election. It range
LAN ID: includes System ID of DIS and 1-byte pseu
The Hello packets in point-to-point networks have the
s L1, 10 indicates L2 and 11
ding Hello packets.
ckets from its neighbor in this
r relationship.
s from 0 to 127.
do-node ID.
following format:

5-11
PDU Length
Local Circuit ID
. of Octets No
1
In adomain Routeing Protocol Discriminator 1
1
ID Length
Reserved/Circuit Type
Holding Time
Source ID
1
1
2
2
PDU Type
Version
Reserved
tr
Length Indicator
ID Lengt
1
1
h
R R R
1
1
Maximum Area Address 1

Figure 5-8 P2P IIH format
As shown in Figure 5-8, most fields in P2P IIH are the same as those in LAN IIH. P2P
IIH does not have the Priority and LAN ID fields, but has a Local Circuit ID field.
IV. LSP
Link State PDUs (LSP) are used to exchange link state information. There are two
kinds of LSPs, which are Level-1 LSP and Level-2 LSP. The Level-2 routers transmit
Level-2 LSPs. The Level-1 routers transmit Level-1 LSPs. The Level-1-2 routers can
transmit both types of LSPs.
Both types of LSPs have the same format, as shown Figure 5-9. in

5-12
Sequency Number
Checksum
ID Length+2
No. of Octets
PDU Length
LSP ID
Remaining Lifetime
2
2
4
2
PDU Type
Version
Reserved
R
1
Length Indicator
ID Length
1
1
1
1
1
1
R R
1
ATT IS Type OL P
1

Figure 5-9 L1/L2 LSP format
connected with Router B are not affected.
PDU Length: the total length of a PDU in bytes.
Remaining Lifetime: the lifetime of the LSP in seconds.
LSP ID: consists of System ID, pseudo-node ID (one byte) and the number of
LSPs (one byte) after fragmentation.
Sequence Number: indicates the sequence number of the LSP.
Checksum: indicates the checksum of the LSP.
P (Partition Repair): relates only to the L2 LSP. It indicates whether or not the
router supports automatic partition repair.
ATT (Attachment): generated by L1/L2 routers and only relates to L1 LSPs. It
indicates the router (the L1/L2 router) generating this LSP is attached to multiple
areas.
OL (LSDB Overload): indicates the LSDB of the local router is incomplete for the
lack of memories. When other routers learn this message, they do not send the
packets which need to be forwarded by this router. However, the packets to a
destination connected directly with the local router can still be forwarded by this
router.
As shown in Figure 5-10, the packets from Router A to Router C are all forwarded by
Router B normally. However, if the OL field of the Router B packet is set to 1, Router
A considers that the Router B routes are incomplete, and thus forwards the packet to
Router C through Router D and Router E. The packets to the destinations directly

5-13
Overload
RouterA
RouterB
RouterC
RouterD RouterE

Figure 5-10 Schematic diagram of LSDB overload
IS Type: indicates the type of the router generating the LSP.
V. SNP
Sequen art of databases to
nize and maintain LSDB.
CSNP contains all the LSP summary information in the LSDB. This maintains the
. (the default
ce Number PDUs (SNPs) describe LSPs in all or p
synchro
SNP include CSNP (complete SNP) and PSNP (partial SNP). They are further divided
into Level-1 CSNP, Level-2 CSNP, Level-1 PSNP and Level-2 PSNP.
synchronization between the neighboring routers.
On a broadcast network, DIS periodically transmits the CSNP
transmission period is 10 seconds). On a point-to-point link, CSNP is only transmitted
when a neighbor relationship is initially set up.
The packet format of CSNP is shown in Figure 5-11.
No. of Octets
Length Indicator
End LSP ID
ID Length+2
PDU Length
Start LSP ID
Source ID
2
PDU Type
Version
Reserved
R
1
ID Length
1
1
1
1
1
1
R R
1
ID Length+1
ID Length+2

Figure 5-11 L1/L2 CSNP format

5-14
sequence numbers. It can
und asynchronous, PSNP is also
PSNP only lists lately received one or more LSP
acknowledge multiple LSP at a time. Once LSDB is fo
adopted to request a neighbor to send a new LSP.
The packet format of PSNP is shown in Figure 5-12.
No. of Octets
PDU Length
Length Indicator
Source ID
2
PDU Type
Version
Reserved
R
1
ID Length
1
1
1
1
1
1
R R
1
ID Length+1

VI. CLV
h-Values (CLVs). The format is
Figure 5-12 L1/L2 PSNP format
The variable length fields are the multiple Code-Lengt
shown in Figure 5-13.
No. of Octets
Length
Code
Length
Value
1
1
Figure 5-13 CLV format
The CLVs vary with PDU types, as shown in Table 5-2.
Table 5-2 PDU types and the included CLV names

CLV Code Name Applied PDU type
1 Area Addresses IIH, LSP
2 IS Neighbors (LSP) LSP
4 Partition Designated Level2 IS L2 LSP

5-15
CLV Code Name Applied PDU type
6 IS Neighbors (MAC Address) LAN IIH
7 IS Neighbors (SNPA Address) LAN IIH
8 Padding IIH
9 LSP Entries SNP
10 Authentication Information IIH, LSP, SNP
128 IP Internal Reachability Information LSP
129 Protocols Supported IIH, LSP
130 IP External Reachability Information L2 LSP
131 Inter-Domain Routing Protocol Information L2 LSP
132 IP Interface Addre IIH ss , LSP

The CLVs who nge of 1 to 10 are defined in ISO10589 (two types
are not listed i defined in RF
5.1.5 IS-IS atures S
I. Multi-Instance and Multi-Process
For easy management and effective control, IS-IS supports multi-process and
multi-instance features. Multi-process feature allows a set o faces to be attached
to a particular that the particula rms all the
protocol operations only on that set of interfaces. Thus, multiple IS-IS protocol
p ses can rocess i onsible for a unique
s nterface
For routers that support VPN, each IS-IS process is associated with a particular
VPN-instance. hed to an IS-IS process must be
a ated to t s ciated to.
II. nistrati
he administrative tags carry administrative information about an IP address prefix.
They are used to control the route importing between different levels and areas,
d communities.
se codes are in the ra
n the table). The other CLVs are C1195.
Fe upported by NE20

f inter
IS-IS process. This ensures r process perfo
roces work on a single router and each p s resp
et of i s.
In this case, all the interfaces attac
ssoci he same VPN-instance that this IS-IS proce s is asso
Admi ve Tags
T
control different routing protocols and multiple IS-IS instances running on the same
router. Besides, they control carrying of the BGP standard or extende

5-16
iated with some attributes. When the IS-IS
advertises an IP address prefix with these attributes, it adds the administrative tag to
that prefix. In this way, sticking to the prefix, the
tag is flooded throughout the routing domain.
III.
of fragments that can be generated by any IS-IS router is 256.
virtual
system that can generate 256 LSP fragments. With more additional System IDs (up to
e IS-IS router can generate a maximum of 13056 LSP
l
allow a single IS-IS process to advertise its LSPs as multiple "virtual" routers, the
Additional System ID
ns an additional System ID. Each Additional System
LSP
t this feature. In this mode, the Originating System advertises a link to
al Systems in its LSPs. Similarly, each of the Virtual Systems
Originating System. In this way, the Virtual Systems look
like the actual routers that are connected to the Originating System in the network.
The administrative tag value is assoc
the IP reachability information TLV for
LSP Fragments Extension
When the link state PDUs to be advertised by IS-IS contain more information, they are
advertised in multiple LSP fragments of the same system. Each LSP fragment is
identified by the LSP identifier field of each LSP. This field is one byte long, and so the
maximum number
The IS-IS LSP fragments extension feature allows an IS-IS router to generate more
LSP fragments. To implement this feature, you can enable the network administrator to
configure additional System IDs on the router. Each System ID represents a
50 virtual systems), th
fragments.
1) Related terms
Originating System
It is a router that physically runs the IS-IS protocol. As the methods in this manua
Originating System represents the single "physical" IS-IS process.
Normal System ID
It is the System ID of an Originating System.
The network administrator assig
ID allows the generation of 256 additional or extended LSP fragments. Like the normal
System ID, the additional System ID must be unique in the routing domain.
Virtual System
The system, identified by an Additional system-id, is used to generate extended
fragments. These fragments carry the additional System IDs in their LSP IDs.
2) Operation Modes
Based on the type of routers in the network, the IS-IS router can run the LSP
fragments extension feature in the following two modes:
mode-1: used in the case when some of the older routers in the network do not
suppor
each of the Virtu
advertises a link to the

5-17
twork support this
e, all the routers in the network can understand that the LSPs
ally belong to the Originating System.
nformation that can be advertised in the
stems.
IV.
dynamic
echanism is introduced. The mechanism provides a mapping
xchange mechanism also provides a service of associating a
config
this ho
V. IS-I
1)
In IS
chan
take ch CPU, and affects the convergence speed.
ged nodes except that it
calculates all the nodes at the first time. The SPT generated at last is the same as that
ed nodes, but
nges, PRC only processes all the leaves on that changed
node. If the SPT remains unchanged, PRC only processes the changed leaves.
The one restriction in this mode is that only Leaf Information should be advertised
in the LSPs of the Virtual Systems.
mode-2: used in the case when all of the routers in the ne
feature. In this mod
generated by the Virtual systems actu
There is no restriction on the link-state i
LSPs of the Virtual Sy
Dynamic Hostname Exchange Mechanism
To manage and maintain the IS-IS networks more conveniently, the
hostname exchange m
service from the hostname to System ID for routers in the IS-IS domain. This dynamic
name information is advertised in the form of a dynamic hostname TLV.
The dynamic hostname e
host name with the DIS in the broadcast network. Then, this mechanism advertises
this association information through pseudo node LSP of the router in the form of
dynamic hostname TLV.
The host name is easier to identify and memorize than System ID. After this function is
ured, the display commands configured on the routers in the network display
st name for the router, instead of System ID..
S Fast Convergence
Incremental SPF (I-SPF)
I-SPF only calculates the changed routes at a time rather than recalculates all the
routes.
O-10589, the Dijkstra algorithm is adopted to calculate routes. When a node
ges in the network, this algorithm needs to recalculate all the nodes. Thus, it
s a long time, occupies too mu
I-SPF improves this algorithm. It only calculates the chan
generated by the previous algorithm. This reduces the CPU utilization and speeds up
the network convergence.
2) Partial Route Calculation
It has the same principle as I-SPF. Both of them only calculate the chang
Partial Route Calculation (PRC) is to update leaves (routes) calculated by I-SPF,
instead of calculating the shortest path.
In route calculation, a route represents a leaf, and a router a node. If the SPT
calculated by I-SPF cha

5-18
proves the convergence performance of the
l algorithm for SPF calculation and replaces it.
te:
For example, only one IS-IS interface is enabled on a node, and then the SPT
calculated by I-SPF remains unchanged. In this case, PRC only updates the routes of
this interface, thus occupying less CPU.
PRC cooperating with I-SPF further im
network. It betters the origina

No
In VRPv5 implementation, I-SPF and PRC is the only algorithm for route calculation.

3) LSP Fast Flooding
To speed up the network convergence, when a router receives newer LSPs from other
routers, it floods out the LSPs in its own LSDB periodically according to the original
RFC. Thus, LSDB is synchronized slowly.
LSP fast flooding addresses the problem. When the router configured with this feature
LSPs, it floods out the LSPs less than the specified
cupy
too much CPU. The SPF intelligent timer addresses the earlier-mentioned problems. It
le. Too much network changes occur rarely,
and the IS-IS router does not calculate routes frequently. Thus, set the first time for
thus the
terval becomes longer. This avoids occupying too much CPU.
LSP generation intelligent timer is similar to the SPF intelligent timer. When the LSP
ntelligent timer falls due, the system generates a new LSP of its own

intervals and thus cannot achieve fast convergence and low CPU utilization. Thus, the
SP generation timer is designed as an intelligent timer to respond to the burst events
c or down) quickly and speed up the network convergence. In
receives one or more newer
number before route calculation. Thus, LSDB can be synchronized quickly. This
improves the network convergence speed greatly.
4) Intelligent Timer
Although the route calculation algorithm is improved, the long interval of triggering
route calculation also affects the convergence speed. You can shorten the interval by
using a millisecond-level timer. However, frequent network changes will also oc
responds to few burst events quickly, and avoids occupying CPU excessively.
An IS-IS network running normally is stab
triggering route calculation to be short (in milliseconds). If the network changes
frequently, the intelligent timer increases with the calculation times and
in
generation i
based on the current topology. The original mechanism adopts a timer with uniform
L
(su h as interface is up
addition, when the network changes frequently, the interval of the intelligent timer
becomes longer automatically to avoid occupying CPU excessively.


5-19
Note:
Be cautious to configure timers of this kind according to the practical networks and
router performances.

5.1.6 Prot
ISO 8348/Ad2 Network Services Access Points
RFC 3847 Restart signaling for IS-IS
5.2 Configuring IS-IS Basic Functions
5.2.1 Esta
I. Applicable Environments
nable IS-IS processes first before configuring IS-IS. Specify NET and enable IS-IS on
the interfaces before configuring other functions.
fo te the following tasks.
eep the network layers of the
III
To configure IS-IS, you need the following data.
ocols and Specifications
ISO 10589 ISO IS-IS Routing Protocol
ISO 9542 ES-IS Routing Protocol
RFC 1195 Use of OSI IS-IS for Routing in TCP/IP and Dual Environments
RFC 2763 Dynamic Hostname Exchange Mechanism for IS-IS
RFC 2966 Domain-wide Prefix Distribution with Two-Level IS-IS
RFC 2973 IS-IS Mesh Groups
RFC 3277 IS-IS Transient Black hole Avoidance
RFC 3358 Optional Checksums in ISIS
RFC 3373 Three-Way Handshake for IS-IS Point-to-Point Adjacencies
RFC 3567 Intermediate System to Intermediate System (IS-IS) Cryptographic
Authentication
RFC 3719 Recommendations for Interoperable Networks using IS-IS
RFC 3786 Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit
RFC 3787 Recommendations for Interoperable IP Networks using IS-IS
RFC 3784 IS-IS extensions for Traffic Engineering
blishing the Configuration Task
E
II. Preconfigured Tasks
Be re configuring IS-IS, you need to comple
Configuring the link layer protocol
Configuring the network layer addresses to k
adjacent nodes reachable
. Data Preparations

5-20
N . o Data
1 NET
2 Process number
The router t 3 ype and its interface type

IV o . C nfiguration Procedures
No. Procedure
1 Enabling IS-IS processes
2 Configuring NET
3 Configuring the router type
erface
5 Configuring the interface type
interface as silent
4 Enabling IS-IS on the specified int
6 Configuring the IS-IS

5.2.2 Enabling IS-IS Processes
Step Action Command
1 Enter system view. system-view
2 Enable IS-IS processes and
enter IS-IS view. vpn-instance-name ]
isis process-id [ vpn-instance

ate an IS-IS routing process and activate it on
ters.
T rameter process-id identifies an IS-IS process. The parameter vpn-instance is
used to asso process with a VPN-instance.

Not
To enable IS-IS protocol, you must cre
the interface, which may associate with other rou
he pa
ciate the IS-IS
e:
The following are all examples of the configurations in common IS-IS view.


5-21
5.2.3 Configuring NET
Step Action Command
2 Enter IS-IS view. isis process-id
-entity net 3 Configure NET. network

A Network Entity Title (NET) define the current IS-IS area address and the system ID
of the router. You can configure up to three NETs on a process of one router.
5.2.4 Enab g IS ified Inte lin -IS on the Spec rface
Step Action Command
1 . Enter system view system-view
2 Enter interface view. interface interface-type interface-number
3 Enable IS-IS on the specified
interface.
isis enable [ process-id ]

5.2.5 Configuring the Router Type
Step Action Command
3 Configure the router type. is-level { level-1 | level-1-2 | level-2 }

e of the router is level-1-2.
5.2.6 Configuring the Interface Type
By default, the typ
Step Action Command
3
Configure the interface type.
isis circuit-level [ level-1 | level-1-2 |
level-2 ]

By default, the interface type is Level-1-2.


5-22
Note:
Only when the rou is Level-1-2, changing the makes sense.
Otherwise, the route nes the stablished.
On point-to d Level se the same Hello packets.
Thus, thi no sense
ter type interface type
r type determi
-point links, the Level-1 an
adjacencies that can be e
-2 routers u
s configuration makes .

5.2.7 Configuring the Interface as Silent
Step Action Command
1 Enter syste system-view m view.
2 Enter interface view. face-type interface-number
rface as
interface inter
3 Configure the inte
silent.
isis silent

After the parameter silent is configured, the IS-IS packets sent and received through
utes in this network segment where the
interface resides can still be advertised through other interfaces.
5.3 Controlling IS-IS Routing Information
5.3.1 Establishing th
This sec he g and receiving of the IS-IS routing
n. For example, advertise aggregated routes, filter the received routes and
routes.
f the routing information such as the priority
nd the cost. After these configurations, you can control the transmission of the IS-IS
routing information in the AS more accurately.
II. Preconfigured Tasks
tasks.
Configuring IS-IS basic functions
III Data Preparations
To configure IS-IS routing information, you need the following data.
this interface are suppressed. However, the ro
e Configuration Task
tion describes how to control t advertisin
informatio
import the external
It introduces how to change the attributes o
a
Before configuring IS-IS routing information, you need to complete the following
Configuring the network layer addresses to keep the network layers of the
adjacent nodes reachable
.

5-23
No. Data
1 The priority of the IS-IS protocol
2 The cost of each interface
for filtering routing information
5 l name and process num ternal routes to be imported
3 Aggregated route
4 Filtering list that is needed
Protoco ber of the ex

IV. Configuration Procedures
No. Procedure
1 Configuring the preference of IS-IS protocol
2 Configuring the link cost
3 Configuring IS-IS route aggregation
ult routes
5 Configuring IS-IS to filter the received routing information
mport external routes
4 Configuring IS-IS to generate defa
6 Configuring IS-IS to i
7 Configuring route leaking

5.3.2 Configuring the Preference of IS-IS Protocol
Step Action Command
3 Configure the preference of
IS-IS protocol.
preference [ route-policy
route-policy-name ] preference-value

erence for the learned routes. The smaller the
higher the preference is. With the route policy, you can set the
preference for a particular route. By default, the preference of IS-IS protocol is 15.
n multiple routing
pr s discover routes to the same de , the protocol with the highest
preferen
This command is to configure the pref
configured value is, the
One router can run multiple routing protocols at the same time. Whe
otocol stination
ce takes effect.

5-24
5.3.3 Configuring the Link Cost
I S de ce
descend
interface cost: the link cost configured for a single interface
global cost: the link cost configured for all the interfaces
ulated automatically based on the interface bandwidth
If no command is configured explicitly, the of the IS-IS interface is 10.
I. C figu
S-I termines the link cost of the interface in three ways. In the preferen
ing order, they are:

auto-cost: the link cost calc
default cost
on ring the Cost Style
Step Action Command
| wide |
atible } | { narrow-compatible |
} [ relax-spf-limit ]
3 Configure the cost style. cost-style { narrow
wide-comp
compatible

The cost range varies with cost styles.
or compatible, the cost range is
he cost style r wide-compatible, the cost 1 to 16777215.
II. nfig e IS-IS Int
If the cost style is narrow or narrow-compatible
from 1 to 63.
If t is wide o range is from
Co uring the Cost of th erface
Step Action Command
3 Configure the cost of the
IS-IS interface.
isis cost cost-value [ level-1 | level-2 ]

With this command, you can configure the cost of a particular interface.
III. Configuring the Global Cost
Step Action Command
3 Configure the global cost. circuit-cost cost-value [ level-1 | level-2 ]

With this command, you can change the cost of all the interfaces at a time.

5-25
IV n . E abling Auto-Cost
Step Action Command
Configure t th
ence value
e
3 he bandwid
reference value.
bandwidth-refer
4 Enable auto-cost. auto-cost enabl

When the cost style is wide or wide- ence value
onfigured in step 3 is valid.
dwidth reference/interface bandwidth) x 10.
compatible, the bandwidth refer
c
Then, the cost of each interface = (ban
When the cost style is narrow or narrow-compatible or compatible, the cost of each
interface can be obtained from the following table
Table 5-3 The corresponding relationship between the interface cost and the
bandwidth
Cost Interface bandwidth range
60 interface bandwidth <= 10M
50 e bandwidth <= 100M 10M < interfac
40 100M < interface bandwidth <= 155M
30 155M < interface bandwidth <= 622M
20 622M < interface bandwidth <= 2.5G
10 2.5G < interface bandwidth

Note:
If you want to chan cost of the Loopback interf e the isis cost
comman
ge the ace, configur
d in interface view.


5-26
5.3.4 Co Aggregation nfiguring IS-IS Route
Step Action Command
3 Configure IS-IS ro
aggregation.
ute
[ avoid-feedback ]
oute ] [ tag tag ]
| level-2 ]
summary ip-address mask
[ generate_null0_r
[ level-1 | level-1-2

You can set the routes with the same next hops as one route, thus reducing the entries
in the routing table.
5.3.5 Configuring IS-IS to Generate Default Routes
Step Action Command
3 Configure IS-IS to generate
default r
default-r icy
route-po el-2 | outes.
oute-advertise [ route-pol
licy-name ] [ level-1 | lev
level-1-2 ]

The default routes generated by this com of the
same level. With the route policy, you can only if
there is a route in the routing table match
5.3.6 Configuring IS-IS to Filter the Receiv n
mand are advertised only to the routers
force IS-IS to generate default routes
ing the policy.
ed Routing Informatio
Step Action Command
3 Configure IS-IS to filter the
received routing information.
filter-policy { acl-number | ip-prefix
ip-prefix-name | route-policy
route-policy-name } import


5-27
outes 5.3.7 Configuring IS-IS to Import External R
Step Action Command
3 Import routes of other
protocols.
import-route protocol [
[ cost-type { external | inter
level-2 | level-1-2 ] [ route-
route-policy-name ] [tag tag ]
cost cost ]
nal } ] [ level-1 |
policy
4 Filter the imported routes. filter-policy { acl-number | ip-prefix
prefix-list-name | route-policy
route-policy-name } export [ protocol ]

IS-IS regards the routes discovered by other routing proto
When importing routes of other protocols, you can spe
cols as external routes.
cify their default costs.
By default, level-2 i d. If no level is specified in oute command,
import ro outing table
5.3.8 Configuring Route Leaking
s adopte the import-r
utes to the Level-2 r .
Step Action Command
1 Enter system view. w system-vie
me } ] [ tag tag ]
3 Enable IS-IS route leaking. import-route isis level-2 into level-1
[ filter-policy { acl-number | ip-prefix
ip-prefix-name | route-policy
route-policy-na

The command is configured on the Level-1-2 router which connects with the external
area. By default, th information of the Level-2 r dvertised to the
L el-1 a
W this er in Level-2 se the routing information in
L el-1 a
5.4 Adjusting and Optimizing IS-I
5.4.1 Establishing the Configuration Task
This section mainly introduces the adjusting and optimizing of the IS-IS networks by
adjusting IS-IS packet timers and the parameters related to LSP and SPF. It also
e routing outer is not a
ev rea.
ith command, a rout area can adverti
ev rea and Level-2 area to a router in Level-1 area.
S

5-28
ostname and authentication for
maintenance and security requirements.
II. con
B ore a izing IS-IS, yo te the following tasks.
Con
adja achable
Configuring IS-IS basic functions
III. Data P
To adjust and optimize IS-IS, you need th
introduces the configuration of IS-IS dynamic h
Pre figured Tasks
ef djusting and optim u need to comple
figuring the network layer add
cent nodes re
resses to keep the network layers of the
reparations
e following data.
No. Data
1 DIS priority of the interface
2 The value of each timer
3 The mapping between system ID and hostname
d 4 Authentication mode and passwor

IV. Configuration Procedures
No. Procedure
1 Configuring DIS priority of the interface
2 Configuring IS-IS packet timers

4 Configuring SPF parameters
5 Configuring LSP fast flooding
6 Configuring IS-IS dynamic hostname
9 Configuring to output the adjacencies
3 Configuring LSP parameters
7 Configuring IS-IS authentication
8 Configuring LSDB overload flag bit


5-29
5.4.2 Configuring DIS Priority of the Interface
Step Action Command
of the
isis dis-priority value [ level-1 | level-2 ]
3 Configure DIS priority
interface.

Only in the broadcast network, configuring DIS priority makes sense. On point-to-point
links, this configuration makes no sense.
The DISs of Level-1 and Level-2 are elected respectively and you can configure
different priorities for them. If no level is specified in the command, the DIS priority of
there ith the same priority in the broadcast network, the one
ed. If the DIS priorities of all routers are 0, the
C address is selected.
5.4.3 Con
I. Configuring the Interval of Sending Hello Packets
Level-1-2 is configured by default.
The higher the priority is, the more possible that the router is selected as the DIS. If
are two or more routers w
with the largest MAC address is select
one with the largest MA
figuring IS-IS Packet Timers
Step Action Command
sending Hello packets.
isis timer hello seconds [ level-1 | level-2 ]
3 Configure the interval of

On the broadcast links, there are Level-1 and Level-2 hello packets. For different
pa s, different intervals can be set. O int links, the hello packets have
n evel d be configured.
II. nfig ello Packets
cket n point-to-po
o l distinction, and so the level does not nee
Co uirng the Invalid Number of H
Step Action Command
timer holding-multiplier value
level-1 | level-2 ]
3 Configure the invalid number isis
of hello packets. [


5-30
The IS-IS protocol maintains the adjacencies among routers by sending or receiving
t hello eive hello packets from its peer within
the holding time, namely, it does not receive the specified number of hello packets
ontinuously within this time, it declares that the hello packets of the neighbor are
dead.
ckets to adjust the holding time.
III. guring the of Sending CSNP Packet
he packets. If a local router does not rec
c
You can configure the invalid number of hello pa
Confi Interval s
Step Action Command
sending CSNP packets.
isis timer csnp seconds [ level-1 | level-2 ]

CSNP packets are transmitted by the Designated IS (DIS) over the broadcast network
IV transmitting LSPs
to synchronize the link state database (LSDB). If the level is not specified, it defaults to
configuring the interval of broadcasting the CSNP packets of the current level.
. Configuring the Interval of Re
Step Action Command
a
isis timer retransmit seconds
retransmitting LSPs on
point-to-point link.

On a point-to-point link, if the local router does not receive the onse within a
p f time after an LSP packet, it considers smitted
LSP pac dropped. T liable transmissions, the local
router re SP packe
T LSP ast lin
V. Configuring the Minimum Interval of Sending LSP
resp
that the originally tran eriod o it sends
ket has been lost or o guarantee re
transmits the original L t.
he s transmitted on a broadc k do not need responses
Step Action Command
3 Configure the minimum
interval of sending LSPs.
isis timer lsp-throttle interval

5-31
on the interface, namely, the
delay for sending one LSP after another.
5.4.4 Conf rin rs
I. C figu
You can configure the minimum interval of sending LSPs
igu g LSP Paramete
on ring LSP Refreshment Period
Step Action Command
3 Configure LSP refreshment
period.
timer lsp-refresh seconds

To synchronize all LSPs in the whole area, all the current LSPs are transmitted
aller
than the lifetime of the LSP.
II. Configuring LSP Lifetime
periodically. When configuring LSP refreshment period, note that it must be sm
Step Action Command
3 Configure LSP lifetime. timer lsp-max-age seconds

When a router generates an LSP, it configures the lifetime for it. When this LSP is
transmitted in the area, its lifetime decreases as time goes by. If the router does not
receive the update LSP all the time and the lifetime of this LSP decreases to 0, this
LSP is deleted from the LSDB.
III. Configuring the Intelligent Timer for Generating LSPs
Step Action Command
3 Configure the intelligent timer
used for generating LSPs. [
timer lsp-generation max-interval
initial-interval [ incremental-interval ]
[ level-1 | level-2 ]

In IS-IS, when the local routing information changes, the router needs to generate new
LSPs to advertise this change. However, when the change is frequent, the interval of

5-32
ance.
routing information
cannot be advertised to the neighbors timely and thus the network converges slowly.
g the delay automatically
according to the ne anges. The interval to initiall e LSP is called
the initia tly, add one terval to it when each change
occurs u ma hen the interval reaches the
m -inte ps to the in
IV. Config ecks
generating a new LSP must be delayed. This avoids occupying too many system
resources, which impairs the system perform
On the other hand, if the delay is too long, the changes of the local
The intelligent timer solves these problems by adjustin
twork ch y generate th
l-interval. Subsequen
ntil the interval is up to the
incremental-in
x-interval. W
ax rval three times, it dro itial-interval again.
uring to Ignore LSP Ch um Error
Step Action Command

checksum error.
ignore-lsp-checksum-error
3 Configure to ignore LSP

W he local IS- es an LSP, it checks its ch he checksum is
inconsis ed checksu the aging time and checksum
o e LS e LSP packet u ignore the checksum error
through ror command, this packet will be processed as a
normal o er
V Configuring the LSP Cache Size
hen t IS receiv ecksum. If t
tent with the calculat m, you can set
f th P to 0. Namely, th is aged. But if yo
the ignore-lsp-checksum-er
ne even if the LSP checksum rors are found.
.
Step Action Command
he
s.
lsp-length originate size [ level-1 |
level-2 ]
Configure t f the
lsp-length rece
3 Configure the size of t
cache originating LSP
4 he size o
cache receiving LSPs.
ive size

N e tha L size of cache
ceiving LSPs.
When enabling the IS-IS functions, the MTU on the interface should not be smaller
ot t the size of cache originating SPs must be smaller than the
re
than the two size. Otherwise, the failure occurs in receiving or sending the IS-IS
packets.

5-33
VI. Configuring the Mesh-Group of the Interface
Step Action Command
2 Enter interface view. ce-type interface-number interface interfa
3 Configure the interface to join
a mesh group.
isis mesh-group [ mesh-group-number |
mesh-blocked ]

A network, the interface of a router floods the received LSP to other
e the group to other interfaces of
V
On the NBM
interfaces. However, for a network with a higher connectivity and multiple p2p links,
the flooding method causes repeated LSP flooding and wastes bandwidth.
To avoid such problem, you can configure several interfaces into a mesh group. The
interface does not flood the LSP received from insid
the same group, but floods it outside the group. When the parameter mesh-blocked is
configured on an interface, the interface is blocked and cannot flood LSPs.
II. Configuring LSP Fragments Extension
Step Action Command
3 Enable the LSP fragments lsp-fragments-extend [ mode-1 | mode-2 ]
evel-2 | level-1-2 ]
Configure a v m. virtual-system virt -id
extension of IS-IS processes. [ level-1 | l
4 irtual syste ual-system

A east ID must be c er for the router to generate
e nded S process can be configured up to 50 virtual system
IDs.
5.4.5 Configuring SPF Parameters
I.
t l one virtual system onfigured in ord
xte LSP fragments. One IS-I
Configuring SPF Intelligent Timer
Step Action Command
2 Enter IS-IS view. isis [ process-id ]
timer spf max-interval initial-interval
incremental-interval
3 Configure SPF intelligent
timer.


5-34
When th anges, the ro the shortest path. If
t shor on ea sources
and affe ying S ation improves router efficiency to
some ex consumption. However, a long delay also slows the
network
he SPF intelligent timer is a good solution to the problem. It can adjust the delay
automatically according to the LSDB changes. The interval to initially calculate the
curs until the interval is up to the max-interval. When the interval
II
e LSDB of IS-IS ch uter needs to recalculate
he test path is recalculated up
ct router efficiency. Dela
ch change, it will occupy too many re
PF calcul
tent and reduces resource
convergence.
T
SPF is called the initial-interval. Subsequently, add one incremental-interval to it when
each change oc
reaches the max-interval three times, it drops to the initial-interval again.
. Configuring the Duration for SPF Calculation
Step Action Command
2 Enter IS-IS isis process-id
ation for
n.
duration-time
view.
3 Configure the dur
each SPF calculatio
spf-slice-size

When th uting entries (m in a routing table, the SPF
alculation of IS-IS will occupy CPU for a long time. To avoid this, you can divide the
SPF calculation into slices. The routes not processed at a time can be calculated one
5.4.6 Ena
ere are many ro ore than 150,000)
c
second later.
bling LSP Fast Flooding
Step Action Command
3 Enable LSP fast flooding. flash-flood [ lsp-count ]
-timer-interval timer ] [ level-1 |
level-2 ]
[ max

U g th mand, you ca ou can specify the
number of LSPs flooded each time for all interfaces. If the LSPs to be sent exceed this
number, r
time out before route calculation, LSPs se, LSPs are
transmitted when the time times out.
sin e flash-flood com n speed up LSP flooding. Y
LSPs of the specified numbe are flooded. If the configured timer does not
are flooded instantly. Otherwi

5-35
5.4.7 Con
I. iguring the Hostname for the Local IS
figuring Dynamic Hostname Mapping
Conf
Step Action Command
3 Configure the hostname for
the local IS
is-name sys-name
.

T com a symbolic l IS-IS process and also
enables
the LSP rtised to other routers in
ou must configure the is-name command first before the dynamic hostname
II.
his mand configures name for the loca
the mapping of system ID to ho
is adve
stname. The configured name in the form of
the area.
Y
mapping of IS-IS processes is enabled. Otherwise, the display command cannot
display the mapping between the system ID and the hostname.
Configuring the Hostname for the Remote IS
Step Action Command
the remote IS.
is-name map sys-id-1 sys-name-1

This command is to locally configure a symbolic name for a remote IS-IS router. Each
system ID can only correspond to one name.
If any router in the network advertises a mapping betwee nd system ID in
it SPs des the stat e local router.
III.
n hostname a
s L , that mapping overri ic mapping in th
Configuring the Hostname for DIS
Step Action Command
DIS.
isis dis-name symbolic-name

This configuration makes sense only on the DIS. The dis-name command configured
on an interface is used to advertise the configured symbolic name in the form of

5-36
y the local router for the network connected to that
particular interface. Hence, this command is used to associate a symbolic name for
th ated Router (DR). Note that this command tak on point-to-point
i rface
5.4.8 Configuring IS-IS Authentication
I. Configuring Area or Domain Authen
pseudo-node LSP generated b
e Design es no effect
nte s.
tication
Step Action Command
3 Configure area authentication
mode.
area-authentication-mode [ { simple |
md5 } password [ ip | osi ] ]
4 Configure domain
authentication mode.
domain-authentication-mode { simple |
md5 } password [ ip | osi ]

If area authentication is needed, the area authenti
into the Level-1 LSP, CSNP and PSNP packets in
cation password is encapsulated
the specified mode. If other routers
in ame area al arted the area authenticati ntication modes
and pas st be ident ones, so that they can work
normally.
Similarly, n authentication, s also encapsulated into the
L el-2 e. If the routers in the
backbone layer (Level-2) also need routing domain authentication, the authentication
ode and password must be identical to the old ones.
II
the s so have st on, the authe
swords of them mu ical to the old
for routing domai the password i
ev LSP, CSNP and PSNP packets in the specified mod
m
. Configuring the Interface Authentication
Step Action Command
3 Configure the authentication
mode and password for the
isis authentication-mo
md5 } password [level-1
interface. osi ]
de { simple |
| level-2 ] [ ip |

T auth e interface in the hello packet so as to
confirm the v ctness of its cation passwords at the
s e lev ical on all the i twork.

he entication set on th
alidity and corre
is mainly used
peers. The authenti
am el should be ident nterfaces of a ne

5-37
Note:
Use the isis enable command to enable the Ethernet interface, and then such
parameters as level-1, level-2 are visible.

5.4.9 Co nfiguring LSDB Overload Flag Bit
Step Action Command
3 Configure the overload flag
bit.
timeout |
tem-id ] ]
[ allow { interlevel | external }* ]
set-overload [ on-startup [
[ wait-for-bgp | start-from-nbr sys

be forwarded by this router. However, the packets to a destination
connected directly with this router are still forwarded to this router.
ncounter some problems in operation, and thus
error may occur in the whole routing area. To avoid this problem, you can set the
e IS-IS network temporarily. Then,
you can locate the fault easily.
5.4.10 Con uri hanges
After the LSPs are set with the overload fields, they do not flood in the network.
Meanwhile, these LSPs are not adopted when calculating the routes to pass the
overload routers.
When the overload flag bit is set for the router, other routers will not send the packets
that should
In the IS-IS domain, the router may e
overload flag bit for this router to isolate it from th
fig ng to Log Peer C
Step Action Command
2 ew. Enter IS-IS vi isis process-id
3 Configure to log peer
changes.
log-peer-change

When the terminal monitor switch is locally enabled, after peer changes log is enabled,
the IS-IS peer changes will be outputted on the configuration terminal until the log is
disabled.

5-38
5.5 Mai
5.5.1 Disp
ay command in any view to display the
running of IS-IS configuration, and to verify the effect of the configuration.
T le 5- ng of IS-IS
ntaining IS-IS
laying the Running of IS-IS
After the above configuration, execute the displ
ab 4 Displaying the runni
Action Command
Vie
enabl
w th
ed
[ ]
e interfaces where IS-IS is
.
display isis interface verbose
[ traffic-eng ] [ tunnel ] [ process-id |
vpn-instance vpn-instance-name ]
View the LSDB of IS-IS.
display isis lsdb [ [ level-1 | l1 ] | [ level-2 |
l2 ] ] [ verbose ] [ local ] [ lsp-id ]
[ process-id | vpn-instance
vpn-instance-name ]
View the mesh-group of IS-IS
display isis mesh-group [ process-id |
[vpn-instance vpn-instance-name ] ]
View the mapping table from the local
router name to system ID.
display isis name-table [ process-id
[vpn-instance vpn-instance-name ]
View IS-IS peers.
display isis peer [ verbose ] [ process-id |
[ vpn-instance vpn-instance-name ] ]
View IS-IS routing information.
di [ | ]
[ v
splay isis route level-1 level-2
erbose ] [ process-id | vpn-instance
vpn-instance-name ]
View the SPF calculation logs of
IS-IS.
display isis spf-log [ process-id |
View the SPF tree of IS-IS.
splay isis spf-tree [ level-1 | level-2 ]
[process-id | vpn-instance
vpn-instanc-nam e ]
di
e ] [ verbos
View th ense e license of IS-IS. display isis lic
View the st
istics [ level-1 | level-2 |
atistics of IS-IS processes
display isis stat
level-1-2 ] [ process-id | [ vpn-instance
vpn-instance-name ]

5.5.2 Clearing IS-IS Data Structure
If you want to refresh some LSPs instantly, execute the following operations in user
view.

5-39
Table 5-5 Clearing all IS-IS data structures
Action Command
Clear IS-IS data structure
reset isis all [ process-id | vpn-instance
vpn-instance-name ]

By default, the IS-IS data structure is not cleared.
5.5.3 Rese ng a eer
I u w bor a specific peer, execute the
f wing .
Table 5-6 Resetting a specific IS-IS peer
tti Specific IS-IS P
f yo ant to re-establish the neigh relationship with
ollo operation in user view
Action Command
Reset a specific IS-IS peer.
reset isis peer system-id [ process-id |

5.5.4 Debugging IS-IS
Execute the debugging command in user view to debug IS-IS.
Table 5-7 Debugging IS-IS
Action Command
Enable all debugging of IS-IS.
debugging isis all
pn-instance vpn-instance-name ]
[ process-id |
v
Enable the debug
adjacencies.
debugging isis process-id |
vpn-instance v ame ]
ging of IS-IS adjacency [
pn-instance-n
Enable the debugging of IS-IS
authentication error.
debugging isis authentication-error
vpn-instance-name ]
Enable the debugging of L
checksum error.
SP
debugging isis checksum-error
[ process-id |vpn-instance
vpn-instance-name ]
Enable the debugging of the interfa
level information.
ce
debugging isis circuit-information
vpn-instance-name ]
configuration error.
[
debugging isis configuration-error
process-id | vpn-instance
vpn-instance-name ]
Enable the debugging when the IS-IS
data link receives packets.

vpn-instance-name ]
debugging isis datalink-receiving-packet

5-40
Action Command
Enable the debugging when the IS-IS

ance
data link sends packets.
debugging isis datalink-sending-packet
[ process-id | vpn-inst
vpn-instance-name ]
events.
debugging isis event [ process-id |
vpn-instance vpn-instance-name ]
general errors.
process-id
e ]
debugging isis general-error [
| vpn-instance vpn-instance-nam
ace-information
interface information.
debugging isis interf
vpn-instance-name ]
memory allocation.
y-allocating
vpn-instance-name ]
debugging isis memor
miscellaneous errors.
debugging isis miscellaneous-errors
Enable the debugging of the received
packet
debugging isis receiving-packet-content
s.
vpn-instance-name ]
Enable the debugging of the local
deb
[ proce
update packets.
ugging isis self-originate-update
ss-id | vpn-instance
vpn-instance-name ]
Enable the debugging of the
transmitted packets.

stance
vpn-instance-name ]
debugging isis sending-packet-content
[ process-id | vpn-in
Enable the debugging of the SNP debugging isis snp-packet [ process-id |
vpn-instance-name ] packets. vpn-instance
Enable the debugging of the SPF debugging isis spf-event [ process-id |
vpn-instance vpn-instance-name ] ] event.
Enable the debugging of the SPF debugging isis spf-summary [ process-id
summary. | [ vpn-instance vpn-instance-name ] ]
Enable the debugging of the SPF
timers.
debugging isis spf-timer [ process-id |
[ vpn-instance vpn-instance-name ]
Enable the debugging of the task debugging i
error.
sis task-error [ process-id |
vpn-instance v ame ] pn-instance-n
Enable the debugging of the timers.
debugging isis timer [ process-id |
Enable the debugging of the IS-IS
update packets.
debugging isis update-packet [ process-id
| vpn-instance vpn-instance-name ]


5-41
5.6 Con les
5.6.1 Exam uratio
I. N
A igure 5-14, Router A, Rou g to the
same autonomous system. The IS-IS ro
i ction.
Router A and Router B are Level-1 router . Router C
s to conne Router A,
R er C are all 10, and th
II.
figuration Examp
ple of Basic IS-IS Config ns
etworking Requirements
s shown in F ter B, Router C and Router D belon
uting protocol is run in these four routers to
mplement IP network interconne
s, and Router D is a Level-2 router
ct the two areas. The area ID of
at of Router D is 20.
erves as the Level-1-2 router
outer B and Rout
Networking Diagram
RouterB
L1
RouterC
L1
1
POS2/0/0
10.1.2.1/24
10.1.1.1/24
/2
3/0/0
192.168.0.1/24
92
10.1.2.2/24
POS1/0/0
RouterD
L2
POS3/0/0
.168.0.2/24
POS
RouterA
L1
IS-IS
Area10
POS2/0/0
IS-IS
Area20
Eth2/0/0
172.16.1.1/16
POS1/0/0
10.1.1.2/24

F configurations
III. cedures
1) Configuring the IP addresses of the interfaces
2 tions
# Configure Router A.
[
[RouterA-isis-1] is-level level-1
[ 10.
[RouterA-isis-1] quit
[RouterA] interface pos 1/0/0
[RouterA-Pos1/0/0] isis enable 1
[RouterA-Pos1/0/0] quit
igure 5-14 Basic IS-IS
Configuration Pro
(omitted)
) Configuring basic IS-IS func
RouterA] isis 1
RouterA-isis-1] network-entity 0000.0000.0001.00

5-42
# Configure Router B.
[RouterB]
[ evel-1
[RouterB-isis-1] network-entity 10.
[
[RouterB] interface pos 2/0/0
[ 1
[RouterB-Pos2/0/0] quit
#
[RouterC]
[RouterC-isis-1] 10.
[
[RouterC]
[RouterC-Pos1/0/0] isis enable 1
[
[RouterC]
[RouterC-Pos2/0/0]
[RouterC-Pos2/0/0] quit
RouterC] interface pos 3/0/0
# Configure Router D.
[RouterD-isis-1] is-level level-2
tity 20.0000.0000.0004.00
[RouterD-isis-1] quit
# Display the LSDB of each router and check whether the LSP is complete.
[RouterA] display isis lsdb

Database information for ISIS(1)
--------------------------------

Level-1 Link State Database

isis 1
RouterB-isis-1] is-level l
0000.0000.0002.00
RouterB-isis-1] quit
RouterB-Pos2/0/0] isis enable
Configure Router C.
isis 1
network-entity 0000.0000.0003.00
RouterC-isis-1] quit
interface pos 1/0/0
RouterC-Pos1/0/0] quit
interface pos 2/0/0
isis enable 1
[
[RouterC-Pos3/0/0] isis enable 1
[RouterC-Pos3/0/0] quit
[RouterD] isis 1
[RouterD-isis-1] network-en
[RouterD] interface ethernet 2/0/0
[RouterD-Ethernet2/0/0] isis enable 1
[RouterD-Ethernet2/0/0] quit
[RouterD] interface pos 3/0/0
[RouterD-Pos3/0/0] isis enable 1
[RouterD-Pos3/0/0] quit
3) Verifying the configuration

5-43
Num Checksum Holdtime Length ATT/P/OL
649 68 0/0/0
68 0/0/0
111 1/0/0
ecksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
-----
0006 0xbf7d 642 68 0/0/0
68 0/0/0
0 0x3340 574 111 1/0/0

f LSP(Extended), ATT-Attached, P-Partition, OL-Overload
abase information for ISIS(1)
---------------------
el-1 Link State Database
Seq Num Checksum Holdtime Length ATT/P/OL
638 68 0/0/0
533 68 0/0/0
569 111 1/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
LSPID Seq
--------------------------------------------------------------------------
-----
0000.0000.0001.00-00* 0x00000006 0xbf7d
0000.0000.0002.00-00 0x00000003 0xef4d 545
0000.0000.0003.00-00 0x00000008 0x3340 582

*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload

[RouterB] display isis lsdb

--------------------------------


LSPID Seq Num Ch
0000.0000.0001.00-00 0x0000
0000.0000.0002.00-00* 0x00000003 0xef4d 538
000 .0000.0003.00-00 0x00000008
*-Self LSP, +-Sel

[RouterC] display isis lsdb

Dat
-----------

Lev

LSPID
--------------------------------------------------------------------------
-----
0000.0000.0001.00-00 0x00000006 0xbf7d
0000.0000.0002.00-00 0x00000003 0xef4d
0000.0000.0003.00-00* 0x00000008 0x3340


5-44
Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------
0000008 0x55bb 650 100 0/0/0
1 0x12d8 0 (933) 27 0/0/0
0x651 629 84 0/0/0
ded), ATT-Attached, P-Partition, OL-Overload
db
--------------------------------


LSPID Seq Num Checksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
-----
0000.0000.0003.00-00 0x00000008 0x55bb 644 100 0/0/0
0000.0000.0004.00-00* 0x00000005 0x651 624 84 0/0/0
*-Self L
ation of each router. A default route must be available
the Level-1 routing table and the next hop is a Level-1-2 router. The Level-2 routing
[RouterA] display isis route

Route information for ISIS(1)
-----------------------------

ISIS(1) Level-1 Forwarding Table
--------------------------------

IPV4 Destination IntCost ExtCost ExitInterface NextHop Flags
--------------------------------------------------------------------------
------
10.1.1.0/24 10 NULL S1/0/0 Direct R/L/-
10.1.2.0/24 20 NULL S1/0/0 10.1.1.1 R/-/-
192.168.0.0/24 20 NULL S1/0/0 10.1.1.1 R/-/-
0.0.0.0/0 10 NULL S1/0/0 10.1.1.1 R/-/-
LSPID Seq
-------------------------------
-----
0000.0000.0003.00-00* 0x0
0000.0000.0003.00-01* 0x0000000
0000.0000.0004.00-00 0x00000005

*-Self LSP, +-Self LSP(Exten

[RouterD] display isis ls

SP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload

# Display the IS-IS routing inform
in
table must include all Level-1 and Level-2 routes.

5-45
Down Bit Set
outerC] display isis route
gs
------------------------------------------------------------------------
0.1.1.0/24 10 NULL S1/0/0 Direct R/L/-
NULL S2/0/0 Direct R/L/-
92.168.0.0/24 10 NULL S3/0/0 Direct R/L/-
Down Bit Set
tCost ExtCost ExitInterface NextHop Flags
-
0.1.2.0/24 10 NULL S2/0/0 Direct R/L/-
72.16.0.0/16 20 NULL S3/0/0 192.168.0.2 R/-/-
-Up/Down Bit Set
ExtCost ExitInterface NextHop Flags
Flags: R-Added to RM, L-Advertised in LSPs, U-Up/

[R

-----------------------------

--------------------------------

IPV4 Destination IntCost ExtCost ExitInterface NextHop Fla
--
------
1
10.1.2.0/24 10
1

Flags: R-Added to RM, L-Advertised in LSPs, U-Up/

--------------------------------

IPV4 Destination In
-------------------------------------------------------------------------
------
10.1.1.0/24 10 NULL S1/0/0 Direct R/L/-
1
192.168.0.0/24 10 NULL S3/0/0 Direct R/L/-
1

Flags: R-Added to RM, L-Advertised in LSPs, U

[RouterD] display isis route

-----------------------------

--------------------------------

IPV4 Destination IntCost

5-46
--------------------
92.168.0.0/24 10 NULL S3/0/0 Direct R/L/-
192.168.0.1 R/-/-
0.1.2.0/24 20 NULL S3/0/0 192.168.0.1 R/-/-
ags: R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set
IV. Configuration Files
is-level level-1
network-entity 10.0000.0000.0001.00
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.2 255.255.255.0
isis enable 1
#
return
#
sysname RouterB
#
isis 1
is-level level-1
network-entity 10.0000.0000.0002.00
#
interface Pos2/0/0
link-protocol ppp
ip address 10.1.2.2 255.255.255.0
isis enable 1
return
3) Configuration file of Router C
#
sysname RouterC
#
------------------------------------------------------
------
1
10.1.1.0/24 20 NULL S3/0/0
1
172.16.0.0/16 10 NULL Eth2/0/0 Direct R/L/-

Fl

1) Configuration file of Router A
#
sysname RouterA
#
isis 1
2) Configuration file of Router B

5-47
-entity 10.0000.0000.0003.00
terface Pos2/0/0
otocol ppp
Configuration file of Router D
ysname RouterD
is 1
otocol ppp
isis 1
network
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.1 255.255.255.0
isis enable 1
#
in
link-protocol ppp
ip address 10.1.2.1 255.255.255.0
isis enable 1
#
interface Pos3/0/0
link-pr
ip address 192.168.0.1 255.255.255.0
isis enable 1
#
return
4)
#
s
#
is
is-level level-2
network-entity 20.0000.0000.0004.00
#
interface Ethernet2/0/0
ip address 172.16.1.1 255.255.0.0
isis enable 1
#
interface Pos3/0/0
link-pr
ip address 192.168.0.2 255.255.255.0
isis enable 1
#
return

5-48
5.6.2 Co ction of IS-IS
I. Netw
5-15, the IS-IS routing protocol is run in Router A, Router B,
uter C and Router D to implement IP network interconnection. These four routers
the same area 10, and the network type is broadcast (Ethernet). Router A
vel-1-2 routers, Router C is a Level-1 router and Router D is a
can change the DIS priority of the interface to configure Router A to a Level-1-2
II.
RouterB
L1/L2
RouterA
L1/L2
erD
th1/0/0
10.1.1.2/24 10.1.1.1/24
nfiguring the DIS Ele
orking Requirements
As shown in Figure
Ro
belong to
and Router B are Le
Level-2 router.
You
DIS (DR).
Networking Diagram
Rout
L2
E Eth1/0/0
Eth1/0/0
10.1.1.4/24
RouterC
L1
Eth1/0/0
1.1.3/24 10.

g the DIS election of IS-IS
III. Configuration
s of the interfaces (omitted)
IS-IS
ure Router A.
uterA-isis-1] network-entity 10.0000.0000.0001.00
-isis-1] quit
uterA-Ethernet1/0/0] isis enable 1
/0] quit
network-entity 10.0000.0000.0002.00
quit
isis enable 1
Figure 5-15 Configurin
Procedures
1) Configuring the IPv4 addresse
2) Enabling
# Config
[RouterA] isis 1
[Ro
[RouterA
[RouterA] interface ethernet 1/0/0
[Ro
[RouterA-Ethernet1/0
# Configure Router B.
[RouterB] isis 1
[RouterB-isis-1]
[RouterB-isis-1]
[RouterB] interface ethernet 1/0/0
[RouterB-Ethernet1/0/0]

5-49
r C.
[RouterC] isis 1
[RouterC-isis-1] network-entity 10.0000.0000.0003.00
[RouterC-isis-1] is-level level-1
[RouterC-isis-1] quit
[RouterC] interface ethernet 1/0/0
[RouterC-Ethernet1/0/0] isis enable 1
onfigure Router D.
uterD-isis-1] network-entity 10.0000.0000.0004.00
-isis-1] is-level level-2
it
uterD-Ethernet1/0/0] isis enable 1
display isis peer

Peer information for ISIS(1)
----------------------------
System Id Interface Circuit Id State HoldTime Type PRI
Eth1/0/0 0000.0000.0003.01 Up 21s L1(L1L2) 64
0000.0000.0003 Eth1/0/0 0000.0000.0003.01 Up 27s L1 64
.0002 Eth1/0/0 0000.0000.0004.01 Up 28s L2(L1L2) 64
0000.0000.0004 Eth1/0/0 0000.0000.0004.01 Up 30s L2 64
-IS interfaces of Router C.
Interface information for ISIS(1)
---------------------------------
Interface Id IPV4.State IPV6.State MTU Type DR
[RouterB-Ethernet1/0/0] quit
# Configure Route
[RouterC-Ethernet1/0/0] quit
# C
[RouterD] isis 1
[Ro
[RouterD
[RouterD-isis-1] qu
[RouterD] interface ethernet 1/0/0
[Ro
[RouterD-Ethernet1/0/0] quit
# Display the IS-IS peers of Router A.
[RouterA]
0000.0000.0002
0000.0000
# Display the IS-IS interfaces of Router A.
[RouterA] display isis interface

---------------------------------
Eth1/0/0 001 Up Down 1497 L1/L2 No/No
# Display the IS
[RouterC] display isis interface


5-50
Up Down 1497 L1/L2 Yes/No
for ISIS(1)
State MTU Type DR
Down 1497 L1/L2 No/Yes
Eth1/0/0 001
# Display the IS-IS interfaces of Router D.
[RouterD] display isis interface

Interface information
---------------------------------
Interface Id IPV4.State IPV6.
Eth1/0/0 001 Up

Note:
As displayed
Level-1 DIS and Router D is a Level-2 DIS. T
in the interface information, with the default DIS priority, Router C is a
he Level-1 pseudo-node and Level-2
pseudo-node are 0000.0000.0003.01 and 0000.0000.0004.01 respectively.

/0] isis dis-priority 100
eers of Router A.

for ISIS(1)
----------------------------
0/0 0000.0000.0001.01 Up 21s L1(L1L2) 64
1/0/0 0000.0000.0001.01 Up 27s L1 64
8s L2(L1L2) 64
0000.0000.0001.01 Up 30s L2 64
.

nterface information for ISIS(1)
---------------------------------
MTU Type DR
Down 1497 L1/L2 Yes/Yes
3) Configuring the D
[RouterA] interface ethernet 1/0/0
IS priority of Router A
[RouterA-Ethernet1/0
# Display the IS-IS p
[RouterA] display isis peer
Peer information
0000.0000.0002 Eth1/
0000.0000.0003 Eth
0000.0000.0002 Eth1/0/0 0000.0000.0001.01 Up 2
0000.0000.0004 Eth1/0/0
# Display the IS-IS interfaces of Router A
[RouterA] display isis interface
I

Interface Id IPV4.State IPV6.State
Eth1/0/0 001 Up


5-51
Note:
As displayed above, after the DIS priority of the IS-IS interface is changed, Router A
s 0000.0000.0001.01. becomes a Level-1-2 DR (DIS) instantly and its pseudo-node i

# Display the IS-IS peers and interfaces of Router C.
for ISIS(1)
Id Interface Circuit Id State HoldTime Type PRI
Up 25s L1 64
Up 7s L1 100
Down 1497 L1/L2 No/No
s of Router D.
display isis peer
0000.0001.01 Up 9s L2 100
000.0000.0001.01 Up 28s L2 64
outerD] display isis interface
Down 1497 L1/L2 No/No
IV. Configuration Files
sis 1
[RouterC] display isis peer

Peer information
----------------------------
System
0000.0000.0002 Eth1/0/0 0000.0000.0001.01
0000.0000.0001 Eth1/0/0 0000.0000.0001.01
[RouterC] display isis interface

---------------------------------
Eth1/0/0 001 Up
# Display the IS-IS peers and interface
[RouterD]

Peer information for ISIS(1)
----------------------------
0000.0000.0001 Eth1/0/0 0000.
0000.0000.0002 Eth1/0/0 0
[R

---------------------------------
Eth1/0/0 001 Up
[RouterD]
1) Configuration file of Router A
#
sysname RouterA
#
i

5-52
10.0000.0000.0001.00
#
isis dis-priority 100

3) Configuration files of Router C
nterface Ethernet1/0/0
ip address 10.1.1.3 255.255.255.0
e 1
4) Configuration file of Router D

sysname RouterD
s-level level-2
ip address 10.1.1.4 255.255.255.0
network-entity
ip address 10.1.1.1 255.255.255.0
isis enable 1
#
return
2) Configuration file of Router B
#
sysname RouterB
#
isis 1
network-entity 10.0000.0000.0002.00
#
ip address 10.1.1.2 255.255.255.0
isis enable 1
#
return
#
sysname RouterC
#
isis 1
is-level level-1
network-entity 10.0000.0000.0003.00
#
i
isis enabl
#
return
#
#
isis 1
i
network-entity 10.0000.0000.0004.00
#

5-53
5.7 Trou
5.7.1 Neighbor Relationship Is Not Established with A Specific Peer
I.
the physical link of other routers, but the peer
not displayed through the display isis peer command. Thus, the neighbor
II.
They have different authentication password.
II
isis enable 1
#
return
bleshooting
Fault Description
When the router intercommunicates with
is
relationship is not established.
Analysis
Fail to establish the relationship results from the following causes.
Two routers are in different levels.
They have different area number.

System ID configuration is repeated.
I. Troubleshooting
Step Action
1
ke sure that the IS-IS process is enabled on the interfaces which connect
the two routers.
Ma
2 these tow routers, execute
TYPE.
Check whether these two routers belong to the same type. In IS-IS view of
the display isis interface command to view their
3
er these two routers are in the same area. In any view of the
two routers, execute the display isis lsdb verbose command to view their
Isp area number.
Check whether their System ID is configured repeatedly. In any view,
onfiguration command to view their
SystemID.
interface authentication is enabled and password is
ces, execute the display this command to
configuration.
e MTUs of two routers are identical. Execute the display
isis interface command to view MTU configuration.
Check IS-IS packet timers. Make sure that the invalid number of hello
e is not less than 3.
Check wheth
4 execute the display current-c
5 identical. In view of each interfa
Check whether the
view the
6
Check whether th
7
packets on a same interfac

5-54
5.7.2 The Level-1 Router Has No Default Route to a Destination External to
Its Area
I. Fault
evel-1 router has no default routes to a destination external to
II. is
with the Level-1-2 router of the same area.
e to a destination external to its area is not available.
III. Troubleshooting
Description
The routing table of the l
its area.
Analys
The Level-1 router can exchange LSP
Otherwise, the default rout
Step Action
1 Check whether the adjacency is established using the display isis peer
command.
2 If the adjacency is not established, use the ping command to check whether
the physical connection and the lower layer protocol are normal.
hether there is the Level-1-2 router in the local area.
Use the display isis Isdb command to view LSDB information. Make sure
that the LSP is complete, and whether LSDB can receive the LSP
is set to 1 from the Level-1-2 router.
3 Check w
4
information which the ATT

05 Chapter5 Is Is Configuration

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

05 Chapter5 Is Is Configuration

Hochgeladen von

Copyright:

Verfügbare Formate

Operation Manual - IP Routing Volume

Quidway NetEngine20 Series Routers Table of Contents

Das könnte Ihnen auch gefallen