Re: What exactly does this EIGRP command do?

From: Narbik Kocharians (narbikk@gmail.com)
Date: Tue Nov 25 2008 - 05:00:38 ARST

Next message: Bit Gossip: "BGP Backdoor Routes: wrong example"
Previous message: Narbik Kocharians: "Re: CCIE True Interview Story"
Maybe in reply to: Jason Madsen: "Re: What exactly does this EIGRP command do?"
Next in thread: GAURAV MADAN: "Re: What exactly does this EIGRP command do?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

I guess the fonts went crazy on me, but the IP address of R2's S0/0.23
should be ".2" and the IP address of R3's S0/0.32 should be ".3".

On Mon, Nov 24, 2008 at 10:55 PM, Narbik Kocharians <narbikk@gmail.com>wrote:

> *OK check this lab and i know it will help you understand this command
> totally:*
>
>
> R1 (S0/0.12)----------------------(S0/0.21) R2
> (S0/0.23)----------------------(S0/0.32) R3
> .1 *10.1.12.0/24* .2
> .3 *
> 10.1.23.0 /24 * .4
>
> The connection between the routers are frame-relay all configured in a P2P
> manner, but understand that it could be any kinda connection.
> R1 has 3 loopback interfaces (2.0.0.0/8, 3.0.0.0/8 and 4.0.0.0/8).
>
> *Task 1*
>
> * *
>
> Configure Eigrp on all routers and advertise their directly connected
> interfaces in AS 100. R1 should NOT advertise network 4.0.0.0 /8 in this
> routing protocol.
>
>
>
> * *
>
> *On R1*
>
> * *
>
> R1(config)#Router eigrp 100
>
> R1(config-router)#no au
>
> R1(config-router)#netw 2.0.0.0
>
> R1(config-router)#netw 3.0.0.0
>
> R1(config-router)#netw 10.1.12.1 0.0.0.0
>
>
>
> *On R2*
>
> * *
>
> R2(config)#Router eigrp 100
>
> R2(config-router)#no au
>
> R2(config-router)#network 10.1.12.2 0.0.0.0
>
> R2(config-router)#network 10.1.23.2 0.0.0.0
>
>
>
> *On R3*
>
>
>
> R3(config)#Router eigrp 100
>
> R3(config-router)#no au
>
> R3(config-router)#network 10.1.23.3 0.0.0.0
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R1*
>
> * *
>
> *R1#Show ip route eigrp*
>
>
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
> D 10.1.23.0 [90/2681856] via 10.1.12.2, 00:01:55, Serial0/0.12
>
>
>
> *On R2*
>
>
>
> *R2#Show ip route eigrp*
>
>
>
> D 2.0.0.0/8 [90/2297856] via 10.1.12.1, 00:02:21, Serial0/0.21
>
> D 3.0.0.0/8 [90/2297856] via 10.1.12.1, 00:02:21, Serial0/0.21
>
> * *
>
> *On R3*
>
>
>
> *R3#Show ip route eigrp*
>
>
>
> D 2.0.0.0/8 [90/2809856] via 10.1.23.2, 00:01:57, Serial0/0.32
>
> D 3.0.0.0/8 [90/2809856] via 10.1.23.2, 00:01:57, Serial0/0.32
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
>
>
> D 10.1.12.0 [90/2681856] via 10.1.23.2, 00:01:57, Serial0/0.32**
>
>
>
> * *
>
> *Task 2*
>
>
>
> Configure R1 such that R2 and R3 use network 2.0.0.0 /8 as candidate
> default.
>
>
>
>
>
> *On R1*
>
>
>
> R1(config)#*ip default-network 2.0.0.0*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R2*
>
>
>
> *R2#Show ip route eigrp*
>
> * *
>
> *D* 2.0.0.0/8 [90/2297856] via 10.1.12.1, 00:00:41, Serial1/0.21*
>
> D 3.0.0.0/8 [90/2297856] via 10.1.12.1, 00:07:55, Serial1/0.21
>
>
>
> *Note the asterisk reveals that R2 is using that network as the candidate
> default.*
>
>
>
> *To test the configuration:*
>
> * *
>
> *On R2*
>
>
>
> *R2#Ping 4.4.4.4*
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
>
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 8/26/60 ms
>
>
>
> *To verify the configuration on R3:*
>
>
>
> *R3#Show ip route eigrp*
>
>
>
> *D* 2.0.0.0/8 [90/2809856] via 10.1.23.2, 00:04:24, Serial1/0.32*
>
> D 3.0.0.0/8 [90/2809856] via 10.1.23.2, 00:10:39, Serial1/0.32
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
> D 10.1.12.0 [90/2681856] via 10.1.23.2, 00:10:39, Serial1/0.32
>
> * *
>
> *R3#Ping 4.4.4.4*
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
>
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/32/92 ms
>
>
>
>
>
> *Task 3*
>
>
>
> Configure R2 such that *R3* does NOT use network 2.0.0.0 /8 as a candidate
> default.
>
>
>
>
>
> *On R2*
>
>
>
> R2(config)#router eigrp 100
>
> R2(config-router)#*no default-information allowed out*
>
>
>
> R2#Clear ip eigrp neighbor
>
>
>
> *Note the "no default-information allowed out" disables the redistribution
> of default route, meaning R3 will no longer use network 2.0.0.0 /8 as its
> candidate default, but it will still have that network in its routing table.
> *
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R2*
>
>
>
> *R2#Show ip route eigrp *
>
>
>
> *D* 2.0.0.0/8* [90/2297856] via 10.1.12.1, 00:00:25, Serial1/0.21
>
> D 3.0.0.0/8 [90/2297856] via 10.1.12.1, 00:00:25, Serial1/0.21
>
>
>
> *On R3*
>
>
>
> *R3#Show ip route eigrp*
>
>
>
> *D 2.0.0.0/8* [90/2809856] via 10.1.23.2, 00:01:04, Serial1/0.32
>
> D 3.0.0.0/8 [90/2809856] via 10.1.23.2, 00:01:04, Serial1/0.32
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
> D 10.1.12.0 [90/2681856] via 10.1.23.2, 00:01:06, Serial1/0.32
>
>
>
> *To test the configuration:*
>
> * *
>
> *On R3*
>
> * *
>
> * *
>
> *R3#Ping 4.4.4.4*
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
>
> .....
>
> Success rate is 0 percent (0/5)
>
>
>
>
>
> *Task 4*
>
>
>
> Remove the command that was entered in the previous task from R2, and
> configure R3 to accomplish the same task, if this configuration is performed
> correctly, R3 should NOT use network 2.0.0.0 /8 as the candidate default.
>
>
>
>
>
> *To remove the command from R2:*
>
>
>
> *On R2*
>
>
>
> R2(config)#router eigrp 100
>
> R2(config-router)#*default-information allowed out*
>
>
>
> R2#cle ip eigrp neighbor
>
>
>
> *To verify R2's configuration:*
>
> * *
>
> *On R2*
>
>
>
> *R2#sh run | s router eigrp *
>
>
>
> router eigrp 100
>
> network 10.1.12.2 0.0.0.0
>
> network 10.1.23.2 0.0.0.0
>
> no auto-summary
>
>
>
> *To verify the configuration on R3*
>
> * *
>
> *On R3*
>
>
>
> *R3#Show ip route eigrp*
>
> * *
>
> *D* 2.0.0.0/8* [90/2809856] via 10.1.23.2, 00:00:58, Serial1/0.32
>
> D 3.0.0.0/8 [90/2809856] via 10.1.23.2, 00:00:58, Serial1/0.32
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
> D 10.1.12.0 [90/2681856] via 10.1.23.2, 00:01:00, Serial1/0.32
>
>
>
> *Note R3 uses network 2.0.0.0 /8 as candidate default. To configure R3 to
> accomplish the same task:*
>
>
>
> *On R3*
>
>
>
> R3(config)#router eigrp 100
>
> R3(config-router)#*no default-information allowed in*
>
>
>
> R3#cle ip eigrp nei
>
>
>
> *Note from R3's perspective it should disable the redistribution of the
> default route inbound, therefore, the direction of the command is configured
> inbound. *
>
> * *
>
> *Note if R2 enters the "no default-information allowed in", then,
> neither R2 nor R3 will receive the default route.*
>
>
>
> *To test and verify the configuration:*
>
> * *
>
> *On R3*
>
>
>
> *R3#Show ip route eigrp*
>
>
>
> *D 2.0.0.0/8* [90/2809856] via 10.1.23.2, 00:02:38, Serial1/0.32
>
> D 3.0.0.0/8 [90/2809856] via 10.1.23.2, 00:02:38, Serial1/0.32
>
> 10.0.0.0/24 is subnetted, 2 subnets
>
> D 10.1.12.0 [90/2681856] via 10.1.23.2, 00:02:38, Serial1/0.32
>
>
>
> *Task 5*
> **
> **NOW LET'S CONNECT THE THREE ROUTERS TO THE SAME ETHERNET SEGMENT WITH A
> NETWORK ADDRESS OF 10.1.1.0 /24, WHERE R1'S IP ADDRESS IS 10.1.1.1/24,
> R2'S IP ADDRESS IS 10.1.1.2/24 AND R3'S IP ADDRESS IS 10.1.1.3/24.
> R1 IS STILL CONFIGURED WITH THE THREE LOOPBACK INTERFACES 2.0.0.0/8,
> 3.0.0.0/8 AND 4.0.0.0/8.
>
> *Task 6*
> Configure Eigrp on all routers and advertise their directly connected
> interfaces in AS 100. R1 should NOT advertise network 4.0.0.0 /8 in this
> routing protocol.
> *
>
>
>
>
>
> On R1
>
>
>
> R1(config-if)#router eigrp 100
>
> R1(config-router)#no au
>
> R1(config-router)#network 2.0.0.0
>
> R1(config-router)#Network 3.0.0.0
>
> R1(config-router)#Network 10.1.1.1 0.0.0.0
>
>
>
> On R2
>
>
>
> R2(config)#Router eigrp 100
>
> R2(config-router)#no au
>
> R2(config-router)#network 10.1.1.2 0.0.0.0
>
>
>
> On R3
>
>
>
> R3(config)#Router eigrp 100
>
> R3(config-router)#no au
>
> R3(config-router)#network 10.1.1.3 0.0.0.0
>
>
>
> To verify the configuration
>
>
>
> On R2
>
>
>
> R2#Show ip route eigrp
>
>
>
> D 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:15:21, Ethernet0/0
>
> D 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:15:21, Ethernet0/0
>
>
>
> On R3
>
>
>
> R3#Show ip route eigrp
>
>
>
> D 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:15:06, Ethernet0/0
>
> D 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:15:06, Ethernet0/0
>
>
>
> Note R1 should not have any Eigrp routes in its routing table.
>
>
>
> Task 7
>
>
>
> Configure R1 to advertise Network 2.0.0.0 /8 and Network 3.0.0.0 /8 as
> candidate default in this routing domain.
>
>
>
>
>
> On R1
>
>
>
> R1(config)#ip default-network 2.0.0.0
>
> R1(config)#ip default-network 3.0.0.0
>
>
>
> To verify the configuration:
>
>
>
> On R2
>
>
>
> R2#Show ip route eigrp
>
>
>
> D* 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:02:55, Ethernet0/0
>
> D* 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:02:52, Ethernet0/0
>
>
>
> On R3
>
>
>
> R3#Show ip route eigrp
>
>
>
> D* 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:03:56, Ethernet0/0
>
> D* 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:03:52, Ethernet0/0
>
>
>
> Note both R2 and R3 use networks 2.0.0.0 /8 and 3.0.0.0 /8 as their
> candidate default.
>
>
>
> Task 8
>
>
>
> Configure R2 and R3 such that R2 uses network 2.0.0.0 /8 and R3 uses
> network 3.0.0.0 /8 as their candidate default.
>
>
>
>
>
> On R2
>
>
>
> To configure this task, an access-list is written to identify the network
> (Network 2.0.0.0 /8 in this case), then, the access-list is referenced in
> the "Default-information allowed in" command, which tells the router that
> ONLY the network that is permitted in the access-list should be used as
> candidate default.
>
>
>
> R2(config)#access-list 2 permit 2.0.0.0
>
>
>
> R2(config)#router eigrp 100
>
> R2(config-router)#default-information allowed in 2
>
>
>
> R2#cle ip eigrp neigh
>
>
>
> R2#Show ip route eigrp
>
>
>
> D* 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:01:41, FastEthernet0/0
>
> D 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:01:41, FastEthernet0/0
>
>
>
> The following shows the configuration of R3:
>
>
>
> On R3
>
>
>
> R3(config)#access-list 3 permit 3.0.0.0
>
>
>
> R3(config)#Router eigrp 100
>
> R3(config-router)#default-information allowed in 3
>
>
>
> R3#cle ip eigrp neighbor
>
>
>
>
>
> To verify the configuration:
>
>
>
> On R3
>
>
>
> R3#Show ip route eigrp
>
>
>
> D 2.0.0.0/8 [90/409600] via 10.1.1.1, 00:01:01, Ethernet0/0
>
> D* 3.0.0.0/8 [90/409600] via 10.1.1.1, 00:01:01, Ethernet0/0
>
>
>
> To test the configuration:
>
>
>
> On R2
>
>
>
> R2#Ping 4.4.4.4
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
>
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/11/24 ms
>
>
>
> On R3
>
>
>
> R3#Ping 4.4.4.4
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
>
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/13/24 ms
> * Once again i am sorry for the long post, but i hope this helped.
>
> On Mon, Nov 24, 2008 at 4:26 PM, Hobbs <deadheadblues@gmail.com> wrote:
>
>> Yep, I had the router generated via RIP, then redistributed into EIGRP
>>
>> R6-----[EIGRP]-----R7------[RIP]-------R8 <---- generates default
>>
>> R7#show ip route | inc 0.0.0.0
>> Gateway of last resort is 150.100.78.8 to network 0.0.0.0
>> 20.0.0.0/24 is subnetted, 1 subnets
>> R* 0.0.0.0/0 [120/1] via 150.100.78.8, 00:00:09, Serial1/0
>> R7#
>>
>>
>>
>> On 11/24/08, Jason Madsen <madsen.jason@gmail.com> wrote:
>> >
>> > were you testing with a default route originating in the same EIGRP AS
>> or
>> > was it from another AS or another routing protocol? try your test again
>> > with the default route originated in say...rip, and then redistribute
>> into
>> > your EIGRP AS and see if what you get.
>> >
>> > Jason
>> >
>> > On Mon, Nov 24, 2008 at 4:11 PM, Hobbs <deadheadblues@gmail.com> wrote:
>> >
>> >> I know what it does for OSPF and the rest, but it appears it does
>> >> something
>> >> different (or nothing) for EIGRP
>> >>
>> >> R7(config)#router eigrp 1
>> >>
>> >> R7(config-router)#default-information ?
>> >> allowed Allow default information
>> >> in Accept default routing information
>> >> out Output default routing information
>> >>
>> >> I tried using "no default-information out" but the default route was
>> still
>> >> sent out.
>> >> I tried using "no default-information in" on another router but it
>> still
>> >> accepted the route.
>> >>
>> >> R6#show run | sec eigrp
>> >> router eigrp 1
>> >> network 150.100.0.0
>> >> no default-information in
>> >> no auto-summary
>> >>
>> >> R6#show ip route | inc Gate
>> >> Gateway of last resort is 150.100.56.7 to network 0.0.0.0
>> >>
>> >> thanks,
>> >>
>> >>
>> >> Blogs and organic groups at http://www.ccie.net
>> >>
>> >> _______________________________________________________________________
>> >> Subscription information may be found at:
>> >> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Narbik Kocharians
> CCSI#30832, CCIE# 12410 (R&S, SP, Security)
> www.MicronicsTraining
> www.Net-Workbooks.com <http://www.net-workbooks.com/>
> Sr. Technical Instructor
>

-- Narbik Kocharians CCSI#30832, CCIE# 12410 (R&S, SP, Security) www.MicronicsTraining www.Net-Workbooks.com Sr. Technical Instructor

Blogs and organic groups at http://www.ccie.net

Next message: Bit Gossip: "BGP Backdoor Routes: wrong example"
Previous message: Narbik Kocharians: "Re: CCIE True Interview Story"
Maybe in reply to: Jason Madsen: "Re: What exactly does this EIGRP command do?"
Next in thread: GAURAV MADAN: "Re: What exactly does this EIGRP command do?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:32 ARST