Lab 2-1 is-Is Configurations
Lab 2-1 is-Is Configurations
return
<R5>display current-configuration
[V200R007C00SPC600]
sysname R5
interface GigabitEthernet0/0/0
interface LoopBack0
area 0.0.0.0
Return
Learning Objectives
Topology
Scenario
IS-IS runs as an IGP in a network. R1 and R5 run in Area 49.0002 as Level-2 routers.
R2, R3, and R4 run in Area 49.0001. R4 is a Level-1 router, while R2 and R3 are
Level-1-2 routers. The requirements are as follows: R4 can use the external routes
imported by R5. R4 connected to S5 functions as the DIS. There is a P2P link between
R1 and R5. Uplink and downlink traffic from R4 to R5 is forwarded through Ethernet
interfaces, and route selection is controlled using the cost and route leaking.
Switches do not require additional configurations and are only responsible for
transparent forwarding.
Tasks
[R1]interface loopback 0
[R1-LoopBack0]quit
[R1-GigabitEthernet0/0/0]quit
[R1-GigabitEthernet0/0/1]quit
[R1-Serial1/0/0]quit
[R2]interface LoopBack 0
[R2-LoopBack0]quit
[R2-GigabitEthernet0/0/0]quit
[R2]interface Serial1/0/0
[R2-Serial1/0/0]quit
[R3]interface LoopBack 0
[R3-LoopBack0]quit
[R3-GigabitEthernet0/0/0]quit
[R3-GigabitEthernet0/0/1]quit
[R4]interface LoopBack 0
[R4-LoopBack0]quit
[R4-GigabitEthernet0/0/0]quit
[R5]interface LoopBack 0
[R5-LoopBack0]quit
[R5-GigabitEthernet0/0/0]quit
[R1]ping -c 1 10.0.13.3
1 packet(s) transmitted
1 packet(s) received
[R1]ping -c 1 10.0.12.2
1 packet(s) transmitted
1 packet(s) received
[R1]ping -c 1 10.0.15.5
1 packet(s) transmitted
1 packet(s) received
[R4]ping -c 1 10.0.234.2
1 packet(s) transmitted
1 packet(s) received
[R4]ping -c 1 10.0.234.3
1 packet(s) transmitted
1 packet(s) received
Configure an IS-IS process 1 for each router according to the topology. The following
example configures IS-IS process 1 for R1.
[R1]isis
[R1-isis-1]network-entity 49.0002.0000.0000.0001.00
By default, after an IS-IS process is enabled on a router, the router works in Level-1-2
mode. According to the planning, R1 needs to work in Level-2 mode. Therefore, you
need to change its IS level.
[R1-isis-1]is-level level-2
[R1-isis-1]quit
[R1]interface LoopBack 0
[R1-LoopBack0]isis enable
[R1-LoopBack0]quit
[R1-GigabitEthernet0/0/0]isis enable
[R1-GigabitEthernet0/0/0]quit
[R1-GigabitEthernet0/0/1]isis enable
[R1-GigabitEthernet0/0/1]quit
[R1-Serial1/0/0]isis enable
[R1-Serial1/0/0]quit
---------------------------------
The preceding command output shows that ISIS(1) has been enabled on a total of
four interfaces, whose IPV4.State field displays Up.
Similarly, configure other routers. R2 and R3 work in Level-1-2 mode, so you do not
need to change their IS levels.
[R2]isis 1
[R2-isis-1]network-entity 49.0001.0000.0000.0002.00
[R2-isis-1]quit
[R2]interface LoopBack 0
[R2-LoopBack0]isis enable
[R2-LoopBack0]quit
[R2-GigabitEthernet0/0/0]isis enable
[R2-GigabitEthernet0/0/0]quit
[R2-Serial1/0/0]isis enable
[R2-Serial1/0/0]quit
---------------------------------
[R3]isis 1
[R3-isis-1]network-entity 49.0001.0000.0000.0003.00
[R3-isis-1]quit
[R3]interface LoopBack 0
[R3-LoopBack0]isis enable
[R3-LoopBack0]quit
[R3-GigabitEthernet0/0/0]isis enable
[R3-GigabitEthernet0/0/0]quit
[R3-GigabitEthernet0/0/1]isis enable
[R3-GigabitEthernet0/0/1]quit
---------------------------------
[R4]isis 1
[R4-isis-1]network-entity 49.0001.0000.0000.0004.00
[R4-isis-1]is-level level-1
[R4-isis-1]quit
[R4]interface LoopBack 0
[R4-LoopBack0]isis enable
[R4-LoopBack0]quit
[R4-GigabitEthernet0/0/0]isis enable
[R4-GigabitEthernet0/0/0]quit
---------------------------------
[R5]isis 1
[R5-isis-1]network-entity 49.0002.0000.0000.0005.00
[R5-isis-1]is-level level-2
[R5-isis-1]quit
[R5]interface LoopBack 0
[R5-LoopBack0]isis enable
[R5-LoopBack0]quit
[R5-GigabitEthernet0/0/0]isis enable
[R5-GigabitEthernet0/0/0]quit
---------------------------------
After the configurations are complete, check IS-IS neighbor statuses of routers. The
following example displays the IS-IS neighbor status of R1. R1 has three neighbors:
R2, R3, and R5.
----------------------------------------------------------------------------
Total Peer(s): 3
In the preceding command output, the System Id field is similar to the Router Id
field of other routing protocols. You can see that R2, R3, and R5 are in Up state. Their
IS-IS neighbor relationships with R1 are normal.
----------------------------------------------------------------------------
Total Peer(s): 4
----------------------------------------------------------------------------
Total Peer(s): 4
----------------------------------------------------------------------------
Total Peer(s): 2
----------------------------------------------------------------------------
Total Peer(s): 1
routers have the same DIS priority, the router with the highest MAC address
becomes the DIS. To ensure that R4 becomes the DIS, change its DIS priority.
[R4-GigabitEthernet0/0/0]quit
---------------------------------
----------------------------------------------------------------------------
Total Peer(s): 4
----------------------------------------------------------------------------
Total Peer(s): 4
[R1-GigabitEthernet0/0/0]quit
[R5-GigabitEthernet0/0/0]quit
During the change of the circuit-type, neighbor relationships are established again.
Check the configuration. The Circuit Id field format changes and the Circuit
Parameters field displays p2p. The following uses the display of R1 as an example.
----------------------------------------------------------------------------
---------------------------------
IP Address : 10.0.15.1
Cost : L1 10 L2 10
Ipv6 Cost : L1 10 L2 10
Static Bfd : NO
Dynamic Bfd : NO
Fast-Sense Rpr : NO
Before importing external routes into IS-IS, check current route learning. The
following command output shows that traffic from R1 to R4 is load balanced
between GE0/0/1 and S1/0/0.
-----------------------------
--------------------------------
----------------------------------------------------------------------------
S1/0/0 10.0.12.2
GE0/0/1 10.0.13.3
----------------------------------------------------------------------------
Destinations : 5 Routes : 7
Destinations : 5 Routes : 7
Destinations : 0 Routes : 0
R2 is a Level-1-2 router and so generates different routes for Level-1 and Level-2
routers. For Level-1 router, it generates a default route pointing to the null interface.
This situation also exists on R3.
-----------------------------
--------------------------------
----------------------------------------------------------------------------
0.0.0.0/0 10 NULL
--------------------------------
----------------------------------------------------------------------------
10.0.4.4/32 20 NULL
10.0.13.0/24 20 NULL
10.0.3.3/32 10 NULL
----------------------------------------------------------------------------
Destinations : 6 Routes : 6
Destinations : 6 Routes : 6
Destinations : 0 Routes : 0
-----------------------------
--------------------------------
----------------------------------------------------------------------------
0.0.0.0/0 10 NULL
--------------------------------
----------------------------------------------------------------------------
10.0.4.4/32 20 NULL
10.0.12.0/24 20 NULL
10.0.2.2/32 10 NULL
----------------------------------------------------------------------------
Destinations : 6 Routes : 6
Destinations : 6 Routes : 6
Destinations : 0 Routes : 0
R4 is a Level-1 router and can only establish IS-IS neighbor relationships with Level-1
or Level-1-2 routers in the same area. By default, a Level-1 router cannot learn
routing information of Level-2 routers and can only access external networks
through default routes. The following command output shows that R4 has two
default routes pointing to R2 and R3, and the two routes work in load balancing
mode.
-----------------------------
--------------------------------
----------------------------------------------------------------------------
GE0/0/0 10.0.234.2
----------------------------------------------------------------------------
Destinations : 5 Routes : 6
Destinations : 5 Routes : 6
Destinations : 0 Routes : 0
-----------------------------
--------------------------------
----------------------------------------------------------------------------
Destinations : 7 Routes : 7
Destinations : 7 Routes : 7
Destinations : 0 Routes : 0
Create new loopback interfaces on R5 and import direct routes into the Level-2
routing table in IS-IS process 1.
[R5]interface LoopBack 1
[R5-LoopBack1]quit
[R5]interface LoopBack 2
[R5-LoopBack2]quit
[R5]interface LoopBack 3
[R5-LoopBack3]quit
[R5]isis
[R5-isis-1]quit
-----------------------------
--------------------------------
----------------------------------------------------------------------------
----------------------------------
----------------------------------------------------------------------------
D 192.168.1.0/24 0 0
D 192.168.2.0/24 0 0
D 192.168.3.0/24 0 0
Check the IS-IS routing table of R4 again. No changes are found. This is because
Level-2 routes are not leaked into Level-1 routers by default. R4 can access
192.168.1.0/24, 192.168.2.0/24, and 192.168.3.0/24 through default routes.
----------------------------------------------------------------------------
Destinations : 5 Routes : 6
Destinations : 5 Routes : 6
Destinations : 0 Routes : 0
[R4]ping -c 1 192.168.1.1
1 packet(s) transmitted
1 packet(s) received
[R4]ping -c 1 192.168.2.1
1 packet(s) transmitted
1 packet(s) received
[R4]ping -c 1 192.168.3.1
1 packet(s) transmitted
1 packet(s) received
By default, the IS-IS interface cost is 10, which is not automatically calculated based
on the bandwidth. For R1, traffic destined for R4 is load balanced between R2 and R3.
R1 and R2 are connected using Serial interfaces, which have low bandwidth and are
prone to bandwidth bottlenecks. Therefore, you can change the IS-IS interface cost
to control route selection of R1.
[R1-Serial1/0/0]isis cost 15
[R1-Serial1/0/0]quit
-----------------------------
--------------------------------
----------------------------------------------------------------------------
Observe data forwarding on R4. R4 does not know Level-2 network information and
forwards data to R2 and R3 for load balancing. If you do not want R4 to use the link
between R2 and R1, configure route leaking to import Level-2 routes into Level-1.
According to the longest match principle, R3 forwards packets destined for R5.
[R4]tracert 192.168.1.1
3 * * *
[R4]tracert 192.168.1.1
3 192.168.1.1 8 ms 1 ms 9 ms
The preceding command output shows that tracert packets sent each time are load
balanced between two next-hop addresses and then reach R5. You can enable route
leaking on R3 to make R3 become the preferred next hop.
[R3]isis
[R3-isis-1]quit
-----------------------------
--------------------------------
----------------------------------------------------------------------------
GE0/0/0 10.0.234.2
----------------------------------------------------------------------------
Destinations : 11 Routes : 12
Destinations : 11 Routes : 12
Destinations : 0 Routes : 0
[R4]tracert 192.168.1.1
1 10.0.234.3 2 ms 1 ms 1 ms
2 10.0.13.1 2 ms 2 ms 2 ms
3 192.168.1.1 1 ms 1 ms 2 ms
The preceding tracert operation proves the impact of route leaking on IS-IS route
selection.
----End
Device Configurations
<R1>display current-configuration
[V200R007C00SPC600]
sysname R1
isis 1
is-level level-2
network-entity 49.0002.0000.0000.0001.00
interface Serial1/0/0
link-protocol ppp
isis enable 1
isis cost 15
interface GigabitEthernet0/0/0
isis enable 1
interface GigabitEthernet0/0/1
isis enable 1
interface LoopBack0
isis enable 1
return
<R2>display current-configuration
[V200R007C00SPC600]
sysname R2
isis 1
network-entity 49.0001.0000.0000.0002.00
interface Serial1/0/0
link-protocol ppp
isis enable 1
interface GigabitEthernet0/0/0
isis enable 1
interface LoopBack0
isis enable 1
return
<R3>display current-configuration
[V200R007C00SPC600]
sysname R3
isis 1
network-entity 49.0001.0000.0000.0003.00
interface GigabitEthernet0/0/0
isis enable 1
interface GigabitEthernet0/0/1
isis enable 1
interface LoopBack0
isis enable 1
return
<R4>display current-configuration
[V200R007C00SPC600]
sysname R4
isis 1
is-level level-1
network-entity 49.0001.0000.0000.0004.00
interface GigabitEthernet0/0/0
isis enable 1
interface LoopBack0
isis enable 1
return
<R5>display current-configuration
[V200R007C00SPC600]
sysname R5
isis 1
is-level level-2
network-entity 49.0002.0000.0000.0005.00
import-route direct
interface GigabitEthernet0/0/0
isis enable 1
interface LoopBack0
isis enable 1
interface LoopBack1
interface LoopBack2
interface LoopBack3
return