From: Gary Duncanson (gary.duncanson@googlemail.com)
Date: Thu Jul 12 2007 - 05:24:46 ART
No doubt. Well it's in the tool box now.
Thanks everyone.
Gary
  ----- Original Message -----
  From: Ben
  To: Gary Duncanson
  Cc: Antonio Soares ; ccielab@groupstudy.com
  Sent: Thursday, July 12, 2007 7:41 AM
  Subject: Re: How is default-information command under router eigrp used?
  Looks that way. Not much utility If you ask me.  In the lab though, cisco
like testing on such obscure commands.
  Ben
  On 7/12/07, Gary Duncanson <gary.duncanson@googlemail.com> wrote:
    And that's it? It only works with default routes generated by ip default
    network on the router, or on another router and redistributed into that
    router..i.e D EX
    ----- Original Message -----
    From: "Antonio Soares" < amsoares@netcabo.pt>
    To: "'Ivan'" <ivan@iip.net>; <ccielab@groupstudy.com >; "'Gary
Duncanson'"
    <gary.duncanson@googlemail.com>
    Cc: "'Ben'" <bmunyao@gmail.com >; <dayo@ademuyiwa.com>; <mmma@gawab.com>
    Sent: Wednesday, July 11, 2007 9:57 PM
    Subject: RE: How is default-information command under router eigrp used?
    > Yes, i've confirmed that these commands only work for the *D or *D EX
    > candidates default routes generated by the "ip default-network x.x.x.x"
    > command.
    >
    > Thanks.
    >
    > -----Original Message-----
    > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
    > Ivan
    > Sent: quarta-feira, 11 de Julho de 2007 16:25
    > To: ccielab@groupstudy.com; Gary Duncanson
    > Cc: Ben; dayo@ademuyiwa.com ; mmma@gawab.com
    > Subject: Re: How is default-information command under router eigrp
used?
    >
    > "no default-information originate" doesn't affect on the 0.0.0.0 any
way.
    > This
    > command used to permit or deny "default route" wich marked "*". Such
route
    > can be created
    > ip default-network x.x.x.x
    >
    > So try this on a lab:
    > R1:
    > R1(config)#int lo 0
    > R1(config-if)#ip address 1.1.1.1 255.255.255.0
    > R1(config)#ip default-network 192.192.192.0
    > R1(config)#ip route 192.192.192.0 255.255.255.0 1.1.1.100
    > R1#sh ip route | i Gate|S\*
    > Gateway of last resort is 1.1.1.100 to network 192.192.192.0
    > S*   192.192.192.0/24 [1/0] via 1.1.1.100
    >
    >
    > R1 --- (eigrp) --- R2
    > R1 redistribute static
    >
    > R2:
    > R2#sh ip route | i Gate|\*
    >       ia - IS-IS inter area, * - candidate default, U - per-user static
    > route
    > Gateway of last resort is 192.168.12.1 to network 192.192.192.0
    > D*EX 192.192.192.0/24 [170/156160] via 192.168.12.1, 00:02:34,
    > FastEthernet0/0
    > ^^^
    > "*" means - use this route as default.
    >
    > R2#conf t
    > R2(config)#router eigrp 100
    > R2(config-router)#no default-information in
    > R2#clear ip eigrp neighbors
    > *Jul 11 19:23:45.427: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
    > 192.168.12.1 (FastEthernet0/0) is down: manually cleared
    > *Jul 11 19:23:45.823: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
    > 192.168.12.1 (FastEthernet0/0) is up: new adjacency
    > R2#sh ip route | i Gate|\*
    >       ia - IS-IS inter area, * - candidate default, U - per-user static
    > route
    > Gateway of last resort is not set
    > ^^^
    > Here we see that default route is disappear.
    >
    >
    >
    > On Wednesday 11 July 2007 14:41, Gary Duncanson wrote:
    >> Ben,
    >>
    >> I haven't played with this myself.
    >>
    >> Perhaps it's used when you want to control the default you will learn
    >> from
    >> a peer in the same AS. From the terminology in the command reference it
    >> seems to allude to uses when you have two diifferent EIGRP AS's and
want
    >> some measure of control.
    >>
    >> default-information
    >> To control the candidate default routing information between IGRP or
    >> EIGRP
    >> processes, use the default-information command in router configuration
    >> mode. To suppress IGRP or EIGRP candidate information in incoming or
    >> outbound updates, use the no default-information in command.
    >>
    >> default-information {in | out} {access-list-number | name}
    >>
    >> no default-information {in | out}
    >>
    >> ----- Original Message -----
    >> From: "Ben" < bmunyao@gmail.com>
    >> To: "Mohamed M Moustafa" <mmma@gawab.com>
    >> Cc: < dayo@ademuyiwa.com>; "Cisco certification"
<ccielab@groupstudy.com>
    >> Sent: Wednesday, July 11, 2007 11:16 AM
    >> Subject: Re: How is default-information command under router eigrp
used?
    >>
    >> > Thank you Mohamed.
    >> >
    >> > You are quite right that eigrp does not use "default-information
    >> > originate"
    >> > command. Instead you redistribute a static default, or use the
    >> > interface
    >> > "ip
    >> > summary-add eigrp 100 0.0.0.0 0.0.0.0" command.
    >> >
    >> > The command I'm struggling with is "default-information in|out acl".
    >> >
    >> > Here is a scenario:
    >> >
    >> >
    >> > 10.1.1.1                           10.1.2.1           10.1.2.2
    >> >
    >
----eigrp--------(f0/0)R1(s0/0)-----------eigrp----------------(s0/0)R2--
    >> >--------rip----------
    >> >
    >> > R1
    >> > int f0/0
    >> >  ip add 10.1.1.1 255.255.255.0
    >> > int s0/0
    >> >  ip add 10.1.2.1 255.255.255.0
    >> >  ip summary-add eigrp 100 0.0.0.0 0.0.0.0
    >> > router eigrp 100
    >> >  net 10.1.2.1 0.0.0.0
    >> >  net 10.1.1.1 0.0.0.0
    >> >
    >> > R2
    >> > int s0/0
    >> >  ip add 10.1.2.2 255.255.255.0
    >> > router eigrp 100
    >> >  net 10.1.2.2 0.0.0.0
    >> >
    >> > In the above scenario R2 will accept the default route from R1. What
    >> > circumstance would require us to use the "default-information in
acl"
    >> > command then?
    >> >
    >> > Ben
    >> >
    >> > On 7/11/07, Mohamed M Moustafa < mmma@gawab.com> wrote:
    >> >> Hi,
    >> >>
    >> >> EIGRP don't utilize the default-information originate command, to
    >> >> advertise
    >> >> default information --> add the default route statically and the do
    >> >> redistribution.
    >> >>
    >> >> Normally, exterior/default routes are always accepted and default
    >> >> information is passed between EIGRP processes when redistribution
    >> >> occurs. when doing so, we still need to confirm the following
command
    > to
    >> >> either allow the sending or receiving of a default route (allowed by
    >> >> default):
    >> >>
    >> >> Router(config-router)#default-information ?
    >> >> allowed Allow default information
    >> >> in Accept default routing information
    >> >> out Output default routing information
    >> >>
    >> >>
    >> >> HTH,
    >> >> Mohammed Mahmoud.
    >> >>
    >> >> Ben  < bmunyao@gmail.com> wrote on 11 Jul 2007, 12:27 PM:
    >> >> Subject: Re: How is default-information command under router eigrp
    > used?
    >> >>
    >> >> >Dayo,
    >> >> >
    >> >> >Thanks for responding.
    >> >> >
    >> >> >In eigrp, the syntax for this command is:
    >> >> >
    >> >> >router eigrp 100
    >> >> >  default-information {allowed[in|out]|in|out [acl]}
    >> >> >
    >> >> >I'm having trouble figuring out how to use it, and scenarios that
    >> >> > apply.
    >> >> >
    >> >> >Ben
    >> >> >
    >> >> >On 7/11/07, dayo@ademuyiwa.com <dayo@ademuyiwa.com> wrote:
    >> >> >> Do you mean default information originate?
    >> >> >>
    >> >> >> On 7/11/07, Ben <bmunyao@gmail.com> wrote:
    >> >> >> > Hi
    >> >> >> >
    >> >> >> > I cann't seem to make sense of how to use the
    > "default-information"
    >> >> >>
    >> >> >> command
    >> >> >>
    >> >> >> > under EIGRP. Does anyone here have examples of its usage that
    > might
    >> >> >
    >> >> >help
    >> >> >
    >> >> >> me
    >> >> >>
    >> >> >> > digest this command.
    >> >> >> >
    >> >> >> > TIA
    >> >> >> >
    >> >> >> > Ben
    >> >>
    >> >>
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART