Cisco ISIS Network Types and Frame Relay Interfaces

Cisco ISIS Network Types and Frame Relay Interfaces

Table of Contents
ISIS Network Types and Frame Relay Interfaces.........................................................................................1 Introduction..............................................................................................................................................1 Correct Configuration Example...............................................................................................................1 Configuration Mismatch Problem...........................................................................................................5 What Causes the Problem?......................................................................................................................6 What's the Solution?................................................................................................................................7 Related Information.................................................................................................................................8

ISIS Network Types and Frame Relay Interfaces

Introduction Correct Configuration Example Configuration Mismatch Problem What Causes the Problem? What's the Solution? Related Information

Introduction
In Intermediate SystemtoIntermediate System (ISIS) there are two types of networks, pointtopoint and broadcast. Unlike Open Shortest Path First (OSPF), ISIS does not have a pointtomultipoint network type. For each type of network, a different type of ISIS Hello (IIH) packet is exchanged to establish adjacency. On pointtopoint networks, pointtopoint IIHs are used and on broadcast networks Level 1 and/or Level 2 LAN IIHs are exchanged. This document gives an example of a configuration mismatch and demonstrates how to diagnose and fix the problem.

Correct Configuration Example

Multipoint serial interfaces are treated the same way as broadcast interfaces. For example, in the network diagram below, the WAN multipoint connection between the three fully meshed routers is treated just like a LAN connection. As on a LAN, a Designated Intermediate System (DIS) is elected. In the diagram below, all three routers are connecting to the Frame Relay cloud on pointtomultipoint interfaces. Main interfaces like Serial 1 on Router E and Serial 0 on Router G are multipoint by default. Routers H and F have a pointtopoint connection. The router configurations are shown below the diagram.

Router E
clns routing

Cisco ISIS Network Types and Frame Relay Interfaces

! !Connection to Backbone interface Ethernet0 ip address 172.17.1.1 255.255.255.0 ip router isis clns router isis ! interface Serial1 ip address 10.10.10.1 255.255.255.0 ip router isis encapsulation framerelay clns router isis framerelay map clns 123 broadcast framerelay map clns 121 broadcast framerelay map ip 10.10.10.3 121 broadcast framerelay map ip 10.10.10.4 123 broadcast framerelay lmitype ansi isis circuittype level1 ! router isis net 49.0001.1111.1111.1111.00

Router G
clns routing ! interface Serial0 ip address 10.10.10.3 255.255.255.0 ip router isis encapsulation framerelay clns router isis framerelay map clns 112 broadcast framerelay map clns 113 broadcast framerelay map ip 10.10.10.1 112 broadcast framerelay map ip 10.10.10.4 113 broadcast framerelay lmitype ansi ! router isis net 49.0001.3333.3333.3333.00 istype level1

Router H
clns routing ! interface Serial0 no ip address no ip directedbroadcast no ip mroutecache encapsulation framerelay framerelay lmitype ansi ! interface Serial0.1 multipoint ip address 10.10.10.4 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay map clns 132 broadcast framerelay map clns 131 broadcast framerelay map ip 10.10.10.1 132 broadcast

Cisco ISIS Network Types and Frame Relay Interfaces

framerelay map ip 10.10.10.3 131 broadcast ! interface Serial0.2 pointtopoint ip address 10.20.20.4 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay interfacedlci 130 ! router isis passiveinterface Ethernet0 net 49.0001.4444.4444.4444.00 istype level1

Router F
clns routing ! interface Serial2 no ip address no ip directedbroadcast encapsulation framerelay framerelay lmitype ansi ! interface Serial2.1 pointtopoint ip address 10.20.20.2 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay interfacedlci 103 ! router isis net 49.0001.2222.2222.2222.00 istype level1

You can use the show clns neighbor, show isis database, and show isis database details commands on all the routers in the mesh to observe the effects of the ISIS configuration on the multipoint WAN connection. Below is the output from show clns neighbor command on all the routers:
Router_H#show clns neighbor System Id Router_E Router_F Router_G SNPA DLCI 132 DLCI 130 DLCI 131 Interface Se0.1 Se0.2 Se0.1 State Up Up Up Holdtime 26 23 26 Type L1 L1 L1 Protocol ISIS ISIS ISIS

Router_G#show clns neighbor System Id Router_E Router_H SNPA DLCI 112 DLCI 113 Interface Se0 Se0 State Up Up Holdtime 25 7 Type Protocol L1 ISIS L1 ISIS

Router_E#show clns neighbor System Id Router_H Router_G Backbone SNPA DLCI 123 DLCI 121 *HDLC* Interface Se1 Se1 Se0 State Up Up Up Holdtime 6 22 22 Type L1 L1 L2 Protocol ISIS ISIS ISIS

Router_F#show clns neighbor System Id Interface SNPA State Holdtime Type Protocol

Cisco ISIS Network Types and Frame Relay Interfaces

Router_H

Se2.1

DLCI 103

Up

27

L1

ISIS

The output from show isis database tells us that Router H is the DIS:
Router_H#show isis database ISIS Level1 Link State Database LSPID LSP Seq Num Router_E.0000 0x000001EC Router_F.0000 0x00000124 Router_G.0000 0x00000130 Router_H.0000 * 0x0000012F Router_H.0100 * 0x00000123 Router_G#show isis database ISIS Level1 Link State Database LSPID LSP Seq Num Router_E.0000 0x00000E8F Router_F.0000 0x00000DC0 Router_G.0000 * 0x00000DD0 Router_H.0000 0x00000DDA Router_H.0100 0x00000DBE Router_E#show isis database ISIS Level1 Link State Database LSPID LSP Seq Num Router_E.0000 * 0x00000EA6 Router_F.0000 0x00000DD7 Router_G.0000 0x00000DE7 Router_H.0000 0x00000DF0 Router_H.0100 0x00000DD5 ISIS Level2 Link State Database LSPID LSP Seq Num Router_E.0000 * 0x00000F19 Backbone.0000 0x00000E94

LSP Checksum 0x1D12 0x63A2 0x0C3B 0xEA6C 0xBA21

LSP Holdtime 44 54 33 42 43

ATT/P/OL 1/0/0 0/0/0 0/0/0 0/0/0 0/0/0

LSP Checksum 0xD2FD 0x0657 0xA6F3 0x6F30 0x2C08

LSP Holdtime 46 45 41 42 50

ATT/P/OL 1/0/0 0/0/0 0/0/0 0/0/0 0/0/0

LSP Checksum 0xA415 0xD76E 0x780B 0x4346 0xFD1F

LSP Holdtime 54 46 40 37 46

ATT/P/OL 1/0/0 0/0/0 0/0/0 0/0/0 0/0/0

LSP Checksum 0x1598 0x5C24

LSP Holdtime 38 56

ATT/P/OL 0/0/0 0/0/0

You can also examine the linkstate packet (LSP) for the DIS. In the output below, the pseudonode LSP Router_H.0100 represents the fullymeshed WAN, showing all the routers attached to the mesh just like the pseudonode LSP does on a LAN.
Router_H#show isis database details Router_H.0100 ISIS Level1 LSP Router_H.0100 LSPID LSP Seq Num Router_H.0100 * 0x00000126 Metric: 0 IS Router_H.00 Metric: 0 IS Router_G.00 Metric: 0 IS Router_E.00

LSP Checksum 0xB424

LSP Holdtime 55

ATT/P/OL 0/0/0

Router_G#show isis database details Router_H.0100 ISIS Level1 LSP Router_H.0100 LSPID LSP Seq Num Router_H.0100 0x00000DBE Metric: 0 IS Router_H.00 Metric: 0 IS Router_E.00 Metric: 0 IS Router_G.00

LSP Checksum 0x2C08

LSP Holdtime 35

ATT/P/OL 0/0/0

Router_E#show isis database details Router_H.0100 ISIS Level1 LSP Router_H.0100 LSPID LSP Seq Num

LSP Checksum

LSP Holdtime

ATT/P/OL

Cisco ISIS Network Types and Frame Relay Interfaces

Router_H.0100 0x00000DD6 Metric: 0 IS Router_H.00 Metric: 0 IS Router_E.00 Metric: 0 IS Router_G.00

0xFB20

42

0/0/0

Configuration Mismatch Problem

Let's examine a problem due to a configuration mismatch. By changing Router F's Serial 2.1 interface from pointtopoint to multipoint, we introduce a problem between Routers F and H. As you can see below, the configuration of Router H has been changed. Router H
clns routing ! interface Serial0 no ip address no ip directedbroadcast no ip mroutecache encapsulation framerelay framerelay lmitype ansi ! interface Serial0.1 multipoint ip address 10.10.10.4 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay map clns 132 broadcast framerelay map clns 131 broadcast framerelay map ip 10.10.10.1 132 broadcast framerelay map ip 10.10.10.3 131 broadcast ! interface Serial0.2 pointtopoint ip address 10.20.20.4 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay interfacedlci 130 ! router isis passiveinterface Ethernet0 net 49.0001.4444.4444.4444.00 istype level1

Router F
clns routing ! interface Serial2 no ip address no ip directedbroadcast encapsulation framerelay framerelay lmitype ansi ! interface Serial2.1 multipoint ip address 10.20.20.2 255.255.255.0 no ip directedbroadcast ip router isis clns router isis framerelay interfacedlci 103

Cisco ISIS Network Types and Frame Relay Interfaces

! router isis net 49.0001.2222.2222.2222.00 istype level1

Now, Router H no longer sees Router F as an ISIS neighbor.

Router_H#show clns neighbor System Id Router_G Router_E SNPA DLCI 131 DLCI 132 Interface Se0.1 Se0.1 State Up Up Holdtime 6 21 Type Protocol L1 ISIS L1 ISIS

Router F sees Router H as an ISIS neighbor, but the state is INIT, meaning that Router F has an adjacency problem.
Router_F#show clns neighbor System Id Router_H Interface Se2.1 SNPA DLCI 103 State Init Holdtime 26 Type Protocol L1 ISIS

What Causes the Problem?

The problem revolves around the fact that Router F sends Serial IIHs on its pointtopoint interface and Router H sends Serial IIHs on its multipoint interface. If we turn on debug isis adj packets on Router H, we do not see any IIHs coming via serial 2.1 although Router F is sending LAN IIHs on Serial 2.1.
Router_H#debug isis adj packets ISIS Adjacency related packets debugging is on ISISAdj: Rec L1 IIH from DLCI 132 (Serial0.1), ISISAdj: Sending serial IIH on Serial0.2 ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Sending L1 IIH on Serial0.1 ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Rec L2 IIH from DLCI 132 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 132 (Serial0.1), ISISAdj: Sending serial IIH on Serial0.2 ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Rec L2 IIH from DLCI 132 (Serial0.1), ISISAdj: Sending L1 IIH on Serial0.1 ISISAdj: Rec L1 IIH from DLCI 132 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Sending serial IIH on Serial0.2 ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1), ISISAdj: Sending L1 IIH on Serial0.1 ISISAdj: Rec L2 IIH from DLCI 132 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 132 (Serial0.1), ISISAdj: Rec L1 IIH from DLCI 131 (Serial0.1),

cir type 3, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 1, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 3, cir id Router_H.01 cir type 1, cir id Router_H.01

If we turn on the same debugging on Router F, you can see that Router F is receiving the Serial IIHs from Router H on its Serial2.1 interface. The LAN IIHs that Router F is trying to send are dropped with encapsulation failures.
Router_F#debug isis adj ISIS Adjacency related ISISAdj: Encapsulation ISISAdj: Encapsulation packets packets debugging is on failed for level 1 IIH on Serial2.1 failed for level 1 IIH on Serial2.1

Cisco ISIS Network Types and Frame Relay Interfaces

ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj:

Encapsulation failed for level 1 IIH on Serial2.1 Rec serial IIH from DLCI 103 (Serial2.1), cir type rcvd state DOWN, old state INIT, new state INIT Action = GOING UP, new type = L1 Encapsulation failed for level 1 IIH on Serial2.1 Encapsulation failed for level 1 IIH on Serial2.1 Rec serial IIH from DLCI 103 (Serial2.1), cir type rcvd state DOWN, old state INIT, new state INIT Action = GOING UP, new type = L1 Encapsulation failed for level 1 IIH on Serial2.1 Encapsulation failed for level 1 IIH on Serial2.1 Encapsulation failed for level 1 IIH on Serial2.1 Rec serial IIH from DLCI 103 (Serial2.1), cir type rcvd state DOWN, old state INIT, new state INIT Action = GOING UP, new type = L1 Encapsulation failed for level 1 IIH on Serial2.1 Encapsulation failed for level 1 IIH on Serial2.1 Encapsulation failed for level 1 IIH on Serial2.1 Rec serial IIH from DLCI 103 (Serial2.2), cir type

L1, cir id 00

L1, cir id 00

L1, cir id 00

L1, cir id 00

Here is an analysis of what is going on between Routers F and H when the link types are mismatched: LAN adjacencies utilize a handshake, which results in one of three possible states: DOWN, INIT, or UP. There are encapsulation failures for the Level 1 IIHs outbound from Router F on the serial 2.1 subinterface. Router H does not receive any LAN IIH from Router F because Router F had encapsulation failures when sending them. Router F does see the IIHs coming from Router H, but doesn't realize it is a pointtopoint IIH because the subinterface of Router F is multipoint. Router F does detect that there is something missing or wrong in the IIH from Router H, so Router F creates a LAN adjacency but puts the adjacency into the INIT state.

What's the Solution?

The solution is to make sure that both sides of a link are either pointtopoint or multipoint. In this case, we will change Router F's Serial 2.1 interface back to pointtopoint to match what is configured on Router H's Serial 2.1 interface. After the change, we flap the interface. The debug output below shows what happens after the change has been made and the Serial 2 interface on Router F is flapped. Now Router F is able to send and receive serial IIHs on its Serial 2.1 interface.
%LINEPROTO5UPDOWN: Line protocol on Interface Serial2.1, changed state to down %LINK5CHANGED: Interface Serial2, changed state to administratively down %FR5DLCICHANGE: Interface Serial2 DLCI 103 state changed to DELETED %FR5DLCICHANGE: Interface Serial2 DLCI 101 state changed to DELETED %LINEPROTO5UPDOWN: Line protocol on Interface Serial2.1, changed state to up %FR5DLCICHANGE: Interface Serial2 DLCI 103 state changed to ACTIVE %SYS5CONFIG_I: Configured from console by console %LINK3UPDOWN: Interface Serial2, changed state to up %FR5DLCICHANGE: Interface Serial2 DLCI 101 state changed to ACTIVE ISISAdj: Sending serial IIH on Serial2.1 ISISAdj: Sending serial IIH on Serial2.1 ISISAdj: Rec serial IIH from DLCI 103 (Serial2.1), cir type L1, cir id 00 ISISAdj: rcvd state INIT, old state DOWN, new state INIT

Cisco ISIS Network Types and Frame Relay Interfaces

ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj:

Action = GOING UP, new type = L1 New serial adjacency Sending serial IIH on Serial2.1 Rec serial IIH from DLCI 103 (Serial2.1), cir type L1, cir id 00 rcvd state UP, old state INIT, new state UP Action = GOING UP, new type = L1

From the perspective of Router H, things are back to normal:

Router_H#show clns neighbor System Id Router_F Router_G Router_E SNPA DLCI 130 DLCI 131 DLCI 132 Interface Se0.2 Se0.1 Se0.1 State Up Up Up Holdtime 28 8 29 Type L1 L1 L1 Protocol ISIS ISIS ISIS

The debug isis adj packets command output is also back to normal:
ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: ISISAdj: Rec serial IIH from DLCI 130 on Serial0.2, cir rcvd state 0, old state 0, new state 0 Action = 2, new_type = 0 Rec L1 IIH from DLCI 131 (Serial0.1), cir type Sending serial IIH on Serial0.2 Sending L1 IIH on Serial0.1 Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec serial IIH from DLCI 130 on Serial0.2, cir rcvd state 0, old state 0, new state 0 Action = 2, new_type = 0 Rec L1 IIH from DLCI 132 (Serial0.1), cir type Rec L2 IIH from DLCI 132 (Serial0.1), cir type Rec L1 IIH from DLCI 131 (Serial0.1), cir type Sending L1 IIH on Serial0.1 Sending serial IIH on Serial0.2 Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec serial IIH from DLCI 130 on Serial0.2, cir Rec L1 IIH from DLCI 132 (Serial0.1), cir type Rec L2 IIH from DLCI 132 (Serial0.1), cir type Sending serial IIH on Serial0.200 Rec L2 IIH from DLCI 132 (Serial0.1), cir type Sending L1 IIH on Serial0.1 Sending serial IIH on Serial0.2 Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec L1 IIH from DLCI 131 (Serial0.1), cir type Rec serial IIH from DLCI 130 on Serial0.2, cir rcvd state 0, old state 0, new state 0 Action = 2, new_type = 0 Rec L2 IIH from DLCI 132 (Serial0.1), cir type type 1, cir id 00

1, cir id Router_H.01

1, cir id Router_H.01.01 1, cir id Router_H.01.01 type 1, cir id 00

3, cir id Router_H.01.01 3, cir id Router_H.01.01 1, cir id Router_H.01.01

1, cir id Router_H.01.01 1, cir id Router_H.01.01 type 1, cir id 00 3, cir id Router_H.01.01 3, cir id Router_H.01.01 3, cir id Router_H.01.01

1, cir id Router_H.01.01 1, cir id Router_H.01.01 type 1, cir id 00

3, cir id Router_H.01.01

Related Information
ISIS Support Page

All contents are Copyright 19922002 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Updated: Dec 31, 2002

Document ID: 13794

Cisco ISIS Network Types and Frame Relay Interfaces