Hello, I'm a bit confused with some distribute-list OUT options. I hope somebody can clarify. I found this page with documentation of the distribute-list OUT command: http://www.cisco.com/en/US/docs/ios/iproute_pi/command/reference/iri_pi1.html#wp1012176 These are the options that I'm really sure what they are for: interface-name(Optional) Name of a particular interface. The interface-name argument cannot be used in address family configuration mode.routing-process(Optional) Name of a particular routing process, or the static or connected keyword.
Not sure what they mean by "interface-name". Firewalls can "name" interfaces. But in a Router I don't know what it means. This does NOT refer to an Interface Type/Numberbecause the the documentation refers to that in a different way; at least in the case of distribute-list IN distribute-list in (IP) interface-type(Optional) Interface type. The interface-type argument cannot be used in address family configuration mode.interface-number(Optional) Interface number on which the access list should be applied to incoming updates. If no interface is specified, the access list will be applied to all incoming updates. The interface type and number arguments can apply if you specify an access list, not a route map. The interface-number argument cannot be used in address family configuration mode. So I guess that by "interface-name" they are referring to something elsebut I'm not sure what. Frankly, I have never seen distribute-list OUT being used with an "Interface" The other argument (routing-process or the static or connected keywords) are also a bit strange. Typically the static or connected keywords are used with the redistribute command. But I had never seen it with distribute-list I had never seen ospf <> or eigrp <> either with distribute-list Perhaps I had, but I can't remember now. Does anybody know how these arguments (interface-name, routing-process, static, connected) can be used with a distribute-list? (if they are used at all) Thank you!! --- --- On Mon, 11/23/09, [email protected] <[email protected]> wrote: From: [email protected] <[email protected]> Subject: Re: [OSL | CCIE_RS] EIGRP distribute-list To: [email protected], [email protected] Date: Monday, November 23, 2009, 5:44 PM True, but an offset-list will only allow you to add to the metric - not rewrite it to whatever absolute value you want. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy L. Gaddis Sent: Monday, November 23, 2009 10:12 PM To: [email protected] Subject: Re: [OSL | CCIE_RS] EIGRP distribute-list On Nov 23, 2009, at 12:52 AM, <[email protected]> <[email protected]> wrote: > Every "set metric" example explicitly identifies BGP, OSPF, and RIP as > supported - not EIGRP. I am not 100% sure why you can't manipulate an > inbound metric within IOS to reflect whatever you like. It might be a > software deficiency. It seems like it could be useful to manipulate > route metrics to easily implement load balancing between EIGRP routes. The composite metric can be manipulated by using an offset-list. -- Jeremy L. Gaddis http://evilrouters.net/ _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
