From: Jonathan V Hays (jhays@jtan.com)
Date: Mon Apr 21 2003 - 16:27:48 GMT-3
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf Of Alec Pun
> Sent: Monday, April 21, 2003 12:43 PM
> To: 'CCIE LAB (E-mail)'
> Cc: alec.cl.pun@pccw.com
> Subject: Distribute-list OUT for OSPF
>
>
> Dear group,
>
> Would you mind to explain why distribute-list OUT can not be
> applied for OSPF? I've heard of some sayings related to OSPF
> link-state behaviour but still can't understand. Thanks! - alec
>
> 1601A(config)#router ospf 1
> 1601A(config-router)#distribute-list 1 out e0 % Interface not
> allowed with OUT for OSPF
>
>
It's not well documented on Cisco's Doc CD.
However, see page 228 of William Parkhurst's "Cisco OSPF Command and
Configuration Handbook", under section 7-8, entitled "distribute-list
access-list-name out" -
"For distance vector protocols (RIP, IGRP, EIGRP) this command prevents
routes selected by the named access list from being advertised to a
neighbor. OSPF is a link-state protocol and does not advertise routes to
a neighbor but advertises a link-state database. The neighbor determines
the routes from the information in the link-state database. Therefore,
this command has no effect when used with OSPF."
However, note that a slightly different command "distribute-list
access-list-name out routing-process" can be used to control which
routes are redistributed into OSPF. Of course, you can do the same with
a route-map.
For example, this configuration allows only network 1.2.3.0 to be
redistributed from EIGRP into OSPF and installed into the OSPF
link-state database:
router ospf 1
redistribute eigrp 1 metric 20 subnets
distribute-list 10 out eigrp 1
!
ip access-list 1 permit 1.2.3.0 0.0.0.255
HTH
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:00 GMT-3