From: tsiartas (tsiartas@xxxxxxxxxxxxx)
Date: Fri Jul 12 2002 - 22:24:37 GMT-3
The fix for this is to make a tunnel to allow the agencies to come up.
Hellos packets don't match and we cannot tweak (like we do with ospf
interface type commands)
GRE will worked I tried it
h.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
perkinsr@WellsFargo.COM
Sent: Friday, July 12, 2002 2:24 PM
To: jhays@jtan.com; ccielab@groupstudy.com
Subject: RE: ISIS - subinterface needed?
ISIS doesn't support NBMA networks and you cannot change the ISIS
network
typ like you can with OSPF. Your ONLY option is to do point to point
subinterfaces when using ISIS. This is a good thing to keep in mind
when
going into the lab, it makes using ISIS on a frame cloud an unlikely
scenario.
-----Original Message-----
From: Jonathan V Hays [mailto:jhays@jtan.com]
Sent: Friday, July 12, 2002 11:17 AM
To: ccielab@groupstudy.com
Subject: ISIS - subinterface needed?
Group,
I just had an interesting experience configuring ISIS on two routers.
One router (R1) had two serial subinterfaces, one of which was
point-to-point to another router running ISIS (R2). Now R2 was not
configured with subinterfaces, just "interface serial 0" since it was
only connected to R1 (via frame relay). I could not get ISIS routes to
appear in the routing tables of either router.
After I changed R2 to a point-to-point subinterface the ISIS routes
popped into both routing tables.
The question is, why is the point-to-point subinterface necessary on
both ends for ISIS to propagate routes?
Jonathan
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:28 GMT-3