I stand corrected!!!  Thank you Steve.  I knew something seemed fishy about
that, as I could have swore I had also done this before successfully...

R2(config-router)#do sh access-list
Standard IP access list 36
    10 permit 36.36.36.36 (4 matches)
Standard IP access list 70
    10 permit 141.41.70.0, wildcard bits 0.0.0.255 (1 match)

router ospf 1
 router-id 2.2.2.2
 log-adjacency-changes
 area 12 nssa no-summary
 area 256 authentication message-digest
 area 256 virtual-link 6.6.6.6
 area 256 virtual-link 5.5.5.5
 redistribute eigrp 2 subnets
 redistribute rip subnets
 network 141.41.12.2 0.0.0.0 area 12
 network 141.41.26.2 0.0.0.0 area 256
 *distance 36 36.36.36.36 0.0.0.0 36
 distance 111 6.6.6.6 0.0.0.0 70*
 redistribute ospf 1 metric 3

R2(config-router)#do sh ip route | i 36.36.36.36|141.41.70.0
O E2    141.41.70.0 [*111*/20] via 141.41.26.6, 00:01:16, Serial0/1/0
O       36.36.36.36 [*36*/2] via 141.41.12.36, 00:01:16, FastEthernet1/0

Note the RID of 141.41.26.6 in our OSPF domain is 6.6.6.6


On Sat, Sep 5, 2009 at 11:30 PM, Steve Shaw <[email protected]> wrote:

> Joe,
>
> Make sure you specify the mask in your ACL. The 141.41.70.0 route is a /32
> in the ACL instead of a /24 and not being matched (not sure why there are
> hits on the ACL). I've raised the distance of an E2 default route in the
> past to prefer iBGP so it should work with external ospf routes.
>
> Steve
>
>
> On Sep 5, 2009, at 11:10 PM, Joe Astorino <[email protected]> wrote:
>
> It sure looks that way for OSPF as well from my testing...As you can see
> below the 141.41.70.0 is an O E2 route, while the 36.36.36.36 is an internal
> route.  Only the internal route 36.36.36.36 has it's distance changed.  Also
> don't forget with OSPF you have to specify the RID of the router that
> advertises the route, not the IP address of where you learn it.
>
> router ospf 1
>  router-id 2.2.2.2
>  log-adjacency-changes
>  area 12 nssa no-summary
>  area 256 authentication message-digest
>  area 256 virtual-link 6.6.6.6
>  area 256 virtual-link 5.5.5.5
>  redistribute eigrp 2 subnets
>  redistribute rip subnets
>  network 141.41.12.2 0.0.0.0 area 12
>  network 141.41.26.2 0.0.0.0 area 256
>  *distance 111 6.6.6.6 0.0.0.0 70
>  distance 36 36.36.36.36 0.0.0.0 36*
>  redistribute ospf 1 metric 3
>
> R2(config-router)#do sh access-list 70
> Standard IP access list 70
>     10 permit 141.41.70.0 (5 matches)
> R2(config-router)#do sh access-list 36
> Standard IP access list 36
>     10 permit 36.36.36.36 (3 matches)
>
> R2(config-router)#do sh ip ospf neigh
>
> Neighbor ID     Pri   State           Dead Time   Address         Interface
> 6.6.6.6           0   FULL/  -           -        141.41.26.6     OSPF_VL1
> 5.5.5.5           0   FULL/  -           -        141.41.26.5     OSPF_VL0
> 1.1.1.1           1   FULL/BDR        00:00:34    141.41.12.1
> FastEthernet1/0
> 36.36.36.36       1   FULL/DR         00:00:36    141.41.12.36
> FastEthernet1/0
> 5.5.5.5           0   FULL/DROTHER    00:00:32    141.41.26.5
> Serial0/1/0
> 6.6.6.6           0   FULL/DROTHER    00:00:32    141.41.26.6
> Serial0/1/0
>
> R2(config-router)#do sh ip route 141.41.70.0
> Routing entry for 141.41.70.0/24
>   Known via "ospf 1", distance 110, metric 20, type extern 2, forward
> metric 64
>   Redistributing via rip
>   Advertised by rip metric 3
>   Last update from 141.41.26.6 on Serial0/1/0, 00:01:06 ago
>   Routing Descriptor Blocks:
>   * 141.41.26.6, from 6.6.6.6, 00:01:11 ago, via Serial0/1/0
>       Route metric is 20, traffic share count is 1
>
> R2(config-router)#do sh ip route 36.36.36.36
> Routing entry for 36.36.36.36/32
>   Known via "ospf 1", distance 36, metric 2, type intra area
>   Redistributing via rip
>   Advertised by rip metric 3
>   Last update from 141.41.12.36 on FastEthernet1/0, 00:01:19 ago
>   Routing Descriptor Blocks:
>   * 141.41.12.36, from 36.36.36.36, 00:01:19 ago, via FastEthernet1/0
>       Route metric is 2, traffic share count is 1
>
>
>
>
>
> On Sat, Sep 5, 2009 at 9:39 PM, Rob < <[email protected]>
> [email protected]> wrote:
>
>> Thanks Joe.  Is that true for the distance command in other routing
>> protocols as well?
>>
>> -----Original Message-----
>> From: Joe Astorino [mailto: <[email protected]>
>> [email protected]]
>> Sent: Saturday, September 05, 2009 8:32 PM
>> To: Rob; <[email protected]>
>> [email protected]; CCIE OSL
>> Subject: Re: [OSL | CCIE_RS] Use of the distance command in EIGRP
>>
>> The distance command in EIGRP for individual routes does not apply to
>> external routes.
>>
>> Regards,
>>
>> Joe Astorino - CCIE #24347 R&S
>> Technical Instructor - IPexpert, Inc.
>> Cell: +1.586.212.6107
>> Fax: +1.810.454.0130
>> Mailto:   <[email protected]>[email protected]
>>
>> -----Original Message-----
>> From: "Rob" < <[email protected]>
>> [email protected]>
>>
>> Date: Sat, 5 Sep 2009 20:24:00
>> To: 'CCIE OSL'< <[email protected]>[email protected]>
>> Subject: [OSL | CCIE_RS] Use of the distance command in EIGRP
>>
>>
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit <http://www.ipexpert.com>www.ipexpert.com
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - <http://www.avg.com>www.avg.com
>> Version: 8.5.409 / Virus Database: 270.13.71/2334 - Release Date: 09/05/09
>> 17:50:00
>>
>>
>>
>
>
> --
> Regards,
>
> Joe Astorino - CCIE #24347 R&S
> Technical Instructor - IPexpert, Inc.
> Cell: +1.586.212.6107
> Fax: +1.810.454.0130
> Mailto:   <[email protected]>[email protected]
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit <http://www.ipexpert.com>www.ipexpert.com
>
>


-- 
Regards,

Joe Astorino - CCIE #24347 R&S
Technical Instructor - IPexpert, Inc.
Cell: +1.586.212.6107
Fax: +1.810.454.0130
Mailto:  [email protected]
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to