From: Pierre-Alex (pierreg@experttraining.net)
Date: Fri Jun 04 2004 - 07:59:09 GMT-3
Hi Dan,
I think I found my mistake
Connected ----> ISIS -----> OSPF
does not mean : Connected----- > OSPF
because routing is not ransitive.
I knew the rule but did not realize that it was ALSO true for connected
routes.
Thank you for the hint,
Pierre-Alex
-----Original Message-----
From: Daniel Sheedy [mailto:dansheedy@gmx.net]
Sent: Friday, June 04, 2004 11:47 AM
To: Pierre-Alex; Ccielab@Groupstudy.Com
Subject: Re: IS-IS and OSPF connected redistribution FROM IS-IS
Hi Pierre,
You have redistributed connected into ISIS, you havent redistribute
connected it into OPF it seems.
Give that a go...
Dan
----- Original Message -----
From: "Pierre-Alex" <pierreg@experttraining.net>
To: "Daniel Sheedy" <dansheedy@gmx.net>; "Ccielab@Groupstudy.Com"
<ccielab@groupstudy.com>
Sent: Friday, June 04, 2004 12:41 PM
Subject: RE: IS-IS and OSPF connected redistribution FROM IS-IS
>
>
>
> Hi Dan, yes I did:
>
>
> router ospf 100
> router-id 1.1.1.1
> log-adjacency-changes
> redistribute isis level-1-2 metric 20 subnets tag 115
> network 10.8.0.0 0.0.255.255 area 0
> network 200.0.0.0 0.255.255.255 area 0
> !
> router isis
> net 47.0001.1111.1111.1111.00
> redistribute connected metric 1 metric-type external level-1-2
> redistribute ospf 100 metric 3 level-1-2
>
>
> BUT OSPF does not get the connected route, only the loopback on R3
>
> R1#sh ip ospf data ext self
>
> OSPF Router with ID (1.1.1.1) (Process ID 100)
>
> Type-5 AS External Link States
>
> LS age: 696
> Options: (No TOS-capability, DC)
> LS Type: AS External Link
> Link State ID: 200.3.3.0 (External Network Number )
> Advertising Router: 1.1.1.1
> LS Seq Number: 80000002
> Checksum: 0x6EEA
> Length: 36
> Network Mask: /24
> Metric Type: 2 (Larger than any link state path)
> TOS: 0
> Metric: 20
> Forward Address: 0.0.0.0
> External Route Tag: 115
>
>
> diagram:
>
> R8------R1-----R3
>
>
> Pierre
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:32 GMT-3