Sunday, 25 November 2007

IS-IS over Frame Relay

running IS-IS over FR is also not easy task.
I have setup where R3 and R2 connected FR cloud (PVC). connection is confogured using major interface, inverse arp also in place:

R2#

!
interface Serial0/0
ip address 24.1.23.2 255.255.255.0
ip router isis
encapsulation frame-relay
no fair-queue
clockrate 128000
no dce-terminal-timing-enable
!
router isis
net 49.1a33.0000.1801.0202.00
log-adjacency-changes
!

R3#
!
interface Serial0/1/0
ip address 24.1.23.3 255.255.255.0
ip router isis
encapsulation frame-relay
no fair-queue
clockrate 128000
!
router isis
net 49.1a33.0000.1801.0303.00
log-adjacency-changes
!

R2#sho frame map
Serial0/0 (up): ip 24.1.23.3 dlci 203(0xCB,0x30B0), dynamic,
broadcast,
CISCO, status defined, active
R2#sho clns in ser 0/0
Serial0/0 is up, line protocol is up
Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching enabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 36 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x1, local circuit ID 0x2
Level-1 Metric: 10, Priority: 64, Circuit ID: R2.02
DR ID: 0000.0000.0000.00
Level-1 IPv6 Metric: 10
Number of active level-1 adjacencies: 0
Level-2 Metric: 10, Priority: 64, Circuit ID: R2.02
DR ID: 0000.0000.0000.00
Level-2 IPv6 Metric: 10
Number of active level-2 adjacencies: 0
Next IS-IS LAN Level-1 Hello in 7 seconds
Next IS-IS LAN Level-2 Hello in 7 seconds
R2#sho isis nei

System Id Type Interface IP Address State Holdtime Circuit Id
R2#

R3#sho frame map
Serial0/1/0 (up): ip 24.1.23.2 dlci 302(0x12E,0x48E0), dynamic,
broadcast,
CISCO, status defined, active
R3#
R3#
R3#
R3#
R3#sho clns int ser 0/1/0
Serial0/1/0 is up, line protocol is up
Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching enabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 31 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x1, local circuit ID 0x2
Level-1 Metric: 10, Priority: 64, Circuit ID: R3.02
DR ID: 0000.0000.0000.00
Level-1 IPv6 Metric: 10
Number of active level-1 adjacencies: 0
Level-2 Metric: 10, Priority: 64, Circuit ID: R3.02
DR ID: 0000.0000.0000.00
Level-2 IPv6 Metric: 10
Number of active level-2 adjacencies: 0
Next IS-IS LAN Level-1 Hello in 6 seconds
Next IS-IS LAN Level-2 Hello in 3 seconds
R3#sho isis nei

System Id Type
Interface IP Address State Holdtime Circuit Id
R6 L1 Fa0/0 24.1.36.6 UP 29 R3.01
R6 L2 Fa0/0 24.1.36.6 UP 29 R3.01
R3#

Real problem!!!! everything seams ok but no adjacencies build :(

lets debug isis
R2#debug isis adj-packets
R2#
*Apr 20 12:23:50.695: ISIS-Adj: Sending L2 LAN IIH on Loopback0, length 1514
*Apr 20 12:23:51.143: ISIS-Adj: Encapsulation failed for L2 LAN IIH on Serial0/0
*Apr 20 12:23:51.671: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0/0
*Apr 20 12:23:55.111: ISIS-Adj: Sending L1 LAN IIH on Loopback0, length 1514
*Apr 20 12:23:58.467: ISIS-Adj: Sending L2 LAN IIH on Loopback0, length 1514
*Apr 20 12:23:59.479: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0/0
*Apr 20 12:24:00.351: ISIS-Adj: Encapsulation failed for L2 LAN IIH on Serial0/0
*Apr 20 12:24:04.195: ISIS-Adj: Sending L1 LAN IIH on Loopback0, length 1514
*Apr 20 12:24:07.039: ISIS-Adj: Sending L2 LAN IIH on Loopback0, length 1514
*Apr 20 12:24:07.979: ISIS-Adj: Encapsulation failed for L2 LAN IIH on Serial0/0
*Apr 20 12:24:08.475: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0/0
R2#

some technologilac background - ISIS is not running on top of IP. it uses own protocol nr xxx.
problem is clear - frame relay map is not mapping clns next hop addresses.

lets help him:

R2(config-if)#frame-relay map clns 203 br
R2(config-if)#
*Apr 20 12:29:41.923: %CLNS-5-ADJCHANGE: ISIS: Adjacency to R3 (Serial0/0) Up, new adjacency
*Apr 20 12:29:47.923: %CLNS-5-ADJCHANGE: ISIS: Adjacency to R3 (Serial0/0) Down, adjacency type changed
*Apr 20 12:29:48.923: %CLNS-5-ADJCHANGE: ISIS: Adjacency to R3 (Serial0/0) Up, new adjacency
R2(config-if)#^Z
R2#sho fr
*Apr 20 12:30:21.175: %SYS-5-CONFIG_I: Configured from console by consolea
R2#sho frame map
Serial0/0 (up): CLNS dlci 203(0xCB,0x30B0), static,
broadcast,
CISCO, status defined, active
Serial0/0 (up): ip 24.1.23.3 dlci 203(0xCB,0x30B0), dynamic,
broadcast,
CISCO, status defined, active
R2#sho isis nei

System Id Type Interface IP Address State Holdtime Circuit Id
R3 L1 Se0/0 24.1.23.3 UP 7 R3.02
R3 L2 Se0/0 24.1.23.3 UP 7 R3.02
R2#

R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#int ser 0/1/0
R3(config-if)#frame map cln
R3(config-if)#frame map clns 302 br
R3(config-if)#^Z
R3#
*Nov 25 19:28:12.609: %CLNS-5-ADJCHANGE: ISIS: Adjacency to R2 (Serial0/1/0) Up, new adjacency
*Nov 25 19:28:13.521: %SYS-5-CONFIG_I: Configured from console by console
R3#

cisco major interfaces treated as multipoint interfaces by default. thats why we see L1 and L2 adjancencies. on a pure p-t-p interfaces we see only L1L2

R4#sho cln
R4#sho clns int ser 0/0.401
Serial0/0.401 is up, line protocol is up
Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching enabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 12 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x2, local circuit ID 0x100
Neighbor System-ID: R1
Level-1 Metric: 10, Priority: 64, Circuit ID: R4.00
Level-1 IPv6 Metric: 10
Number of active level-1 adjacencies: 1
Level-2 Metric: 10, Priority: 64, Circuit ID: R4.00
Level-2 IPv6 Metric: 10
Number of active level-2 adjacencies: 1
Next IS-IS Hello in 1 seconds
if state UP
R4#sho runn int ser 0/0.401
Building configuration...

Current configuration : 134 bytes
!
interface Serial0/0.401 point-to-point
ip address 24.1.14.4 255.255.255.0
ip router isis
frame-relay interface-dlci 401
end

R4#


and finaly different hello is send over ptp and ptmp inerfaces (LAN hello and serial hello).

something from CCO:
http://www.cisco.com/warp/public/97/isis-frint.html

1 comment:

Unknown said...

Thanks a lot !!!

For the detailed logs and observation!!