RE: ISIS adjacence with ip address

From: Paresh Khatri (Paresh.Khatri@aapt.com.au)
Date: Wed Jul 20 2005 - 20:22:38 GMT-3


Hi Dillon,

Since you are using Integrated ISIS (or DUAL ISIS), you've gotta remember that this protocol supports routing for both CLNS and IP simultaneously. Every pair of neighboring routers forms only one adjacency (or two, in case they are configured as L1/2) - this adjacency is for both CLNS and IP. If either of them have problems that prevent adjacency formation, neither protocol will work. Now, if you had separate adjacencies for CLNS and IP, a problem with the IP adjacency would not have impacted the CLNS adjacency. However, that is not the case so both IP and CLNS suffer in your case...

HTH,
Paresh.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Dillon Yang
Sent: Saturday, 16 July 2005 01:00 PM
To: Paresh Khatri
Cc: Group Study
Subject: Re: ISIS adjacence with ip address

Hi, Paresh:
  Yes!
  First, I just set "clns router isis" and it was fine.
  Second, I added "ip router isis" and ip address, and it was fine.
  Third, I changed the subnet or deleted either, the messages I post appeared.
  Finally, I changed it back to the same subnet, it was fine again.

So , My question is, since ip is upon the clns, why the ip config will down the clns adjacence?

TIA
dillon

----- Original Message -----
From: "Paresh Khatri" <Paresh.Khatri@aapt.com.au>
To: "Dillon Yang" <dillony@gmail.com>; "Group Study" <ccielab@groupstudy.com>
Sent: Saturday, July 16, 2005 9:59 AM
Subject: RE: ISIS adjacence with ip address

Hi Dillon,

For a ISIS adjacency to form, the two ends of the link must be in the same subnet. Is that what you were asking for ?

Paresh.

-----Original Message-----
From: nobody@groupstudy.com on behalf of Dillon Yang
Sent: Sat 16/07/2005 1:56 AM
To: Group Study
Cc:
Subject: ISIS adjacence with ip address
Hi, group:

  I just found that the IP subnet will shutdown the ISIS adjacence.
I labbed it with "ip router isis " and "clns router isis", so far as good, until I change the IP address by changing subnet or deleting it, and got the messages:

!
interface Serial0
 bandwidth 125
 ip address 15.3.24.4 255.255.255.0
 ip router isis bb
 encapsulation frame-relay
 no fair-queue
 frame-relay map clns 402 broadcast
 frame-relay map ip 135.3.24.2 402 broadcast
 no frame-relay inverse-arp
end
!
interface Serial0
 bandwidth 125
 ip address 135.3.24.2 255.255.255.0
 ip router isis r2
 encapsulation frame-relay
 no fair-queue
 clockrate 125000
 frame-relay map clns 204 broadcast
 frame-relay map ip 135.3.24.4 204 broadcast
 no frame-relay inverse-arp
 isis circuit-type level-2-only
 isis metric 40
 isis priority 73
end
*Mar 1 01:36:58: ISIS-Adj (bb): Rec L2 IIH from DLCI 402 (Serial0), cir type L2, cir id 2
222.2222.2222.01, length 1500
*Mar 1 01:36:58: ISIS-Adj (bb): No usable IP interface addresses in LAN IIH from Serial0
R4#
*Mar 1 01:36:59: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:03: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:04: ISIS-Adj (migration): Sending L1 LAN IIH on Ethernet0, length 1497
R4#
*Mar 1 01:37:06: ISIS-Adj (bb): Rec L2 IIH from DLCI 402 (Serial0), cir type L2, cir id 2
222.2222.2222.01, length 1500
*Mar 1 01:37:06: ISIS-Adj (bb): No usable IP interface addresses in LAN IIH from Serial0
*Mar 1 01:37:06: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
*Mar 1 01:37:06: ISIS-Adj (bb): Sending L2 LAN IIH on Serial0, length 1500
R4#
*Mar 1 01:37:08: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:12: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
*Mar 1 01:37:12: ISIS-Adj (migration): Sending L1 LAN IIH on Ethernet0, length 1497
R4#
*Mar 1 01:37:14: ISIS-Adj (bb): Sending L2 LAN IIH on Serial0, length 1500
*Mar 1 01:37:15: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:16: ISIS-Adj (bb): Rec L2 IIH from DLCI 402 (Serial0), cir type L2, cir id 2
222.2222.2222.01, length 1500
*Mar 1 01:37:16: ISIS-Adj (bb): No usable IP interface addresses in LAN IIH from Serial0
R4#
*Mar 1 01:37:18: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:19: ISIS-Adj (migration): Sending L1 LAN IIH on Ethernet0, length 1497
*Mar 1 01:37:20: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:22: ISIS-Adj (bb): Sending L2 LAN IIH on Serial0, length 1500
*Mar 1 01:37:23: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#
*Mar 1 01:37:24: ISIS-Adj (bb): Rec L2 IIH from DLCI 402 (Serial0), cir type L2, cir id 2
222.2222.2222.01, length 1500
*Mar 1 01:37:24: ISIS-Adj (bb): No usable IP interface addresses in LAN IIH from Serial0
R4#
*Mar 1 01:37:26: ISIS-Adj (migration): Rec L1 IIH from 0010.7b81.6ca4 (Ethernet0), cir ty
pe L1, cir id 9999.9999.9999.02, length 1497
R4#

Any advice?

TIA
dillon



This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:30 GMT-3