From: Gerard Robinson (gerardrobinson@xxxxxxxxxxxxxx)
Date: Sat Jul 15 2000 - 09:19:46 GMT-3
IS-IS can dynamically route IP and CLNS so if you do a 'clns router
isis 1' on all the serial interfaces then the routers will establish CLNS
adjacencies and you should be able to CLNS ping R5 from R1 and vice-versa.
----- Original Message -----
From: Cliff Stewart <cliffstewart@go.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, July 15, 2000 7:04 AM
Subject: ISIS Routing
> I wanted to know if anyone could shed some light on this configuration.
>
> R1
> router isis 1
> net 47.0001.1111.1111.1111.00
> interface serial 1
> ip router isis 1
> encapsulation ppp
> clockrate 125000
>
> (directed connected to R3)
>
> R3
> router isis 1
> net 47.0003.3333.3333.3333.00
> interface serial 0
> ip router isis 1
> encapsulation ppp
>
> (R3's serial 1 is connected to serial 1 on R5)
> router isis 1
> net 47.0005.5555.5555.5555.00
> interface serial 1
> ip router isis
> encapsulation ppp
>
> Here's the situation if I want to ping R5 from R1 I have to enter the
following command...
>
> clns net 47.0005.5555.5555.5555.00
>
> If I want to ping R1 from R5 I have to enter the following command....
>
> clns net 47.0001.1111.1111.1111.00
>
> Is the correct procedure or am I violating a routing rule? Meaning do you
guys know of a better method to achieve connectivity to a router not
directly connected? It would have been nice to have a feature like next-hop
self, but that's life:) Thanks guys.
>
> Cliff
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:53 GMT-3