From: Darby Weaver (darbyweaver@yahoo.com)
Date: Mon Mar 05 2007 - 04:18:15 ART
Shamin,
Is this like deja vu?
It seems you had a similar problem back in 2006...
===================================================
SHAMIN,
Use neighbour command under eigrp process. I believe
you are running
Frame-relay in NBMA
-----Original Message-----
From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com] On Behalf Of
Shamin
Sent: Monday, 1 May 2006 12:44 AM
To: Cisco certification
Subject: EIGRP over FR problem
Hi,
<----- R3 ----- FR----- R1 ----->
In the above setup, I am running EIGRP over the
frame-relay. The issue
I am
facing is as follows:
When i configure FR on R1 & R3 , for Inverse-arp , the
EIGRP forms
adjacency
between R1 and R3 without any problems.
But as per the lab requirements, the FR should be
configured with
static
mapping using the Frame-relay map statement, the EIGRP
does
not form adjacency if I restart the adjacency
formation. A vague
configuration is as below.
Rack1R1#
int s0/0
ip address 162.1.13.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 162.1.13.3 113
no frame-relay inverse-arp
router eigrp 200
eigrp router-id 150.1.1.1
network 162.1.13.1 0.0.0.0
network 150.1.1.1 0.0.0.0
**************X*************X****************
Rack1R3#
int s0/0
ip address 162.1.13.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 162.1.13.1 311
no frame-relay inverse-arp
router eigrp 200
eigrp router-id 150.1.3.3
network 162.1.13.1 0.0.0.0
******************X************************************X********************
*
************
With the above setup,I dont find the any neighbors in
my " sh ip eigrp
neighbors" command. But i am able to ping the IP of
the opposite
routers FR
interface. But I will not be able to ping R1's
Loopback interface from
R3
with the above setup.
If i change this setup to Inverse-arp and issue the "
clear frame-relay
inarp" , I see neighbors in eigrp as soon as the FR
network comes up.
I am doin the IEWB VER3.0 LAB5 TASK-FR . Any thing I
am doin wrong
here?
================================================
Anyway, I'll see what I see on my fear tomorrow - it
seems to be keeing Victor interested enough...
I've examined the output and it the EIGRP routing
updates are just not getting across.
But is it just an authentication issue? Or at this
point a more freaky issue.
Now, it seems I watching a COD for the Mock Labs and
they mentioned something about this behavior but it
seems like it was limited to OSPF. That is with 2
Virtual Templates coming from two spokes to the Hub.
Hmmm...
--- Victor Cappuccio <victor@ccbootcamp.com> wrote:
> Hi Antonio
>
> Take a look at the configuration for the spokes
> routers an you will notice
> that some ppp authentication parameters are
> missing...
>
> Now Lets the router talk With your configuration..
>
> interface Serial 0/0/0
> no ip address
> encapsulation frame-relay
> frame-relay interface-dlci 304 ppp
> Virtual-Template1
> frame-relay interface-dlci 305 ppp
> Virtual-Template2
> frame-relay lmi-type cisco
> !
> interface Virtual-Template1
> ip address 158.1.0.3 255.255.255.0
> ppp authentication pap chap
> !
> interface Virtual-Template2
> ip address 158.1.0.3 255.255.255.0
> ppp authentication pap chap
> !
>
> Topology:
> R6 -------- R8 ------- R7
>
> R6 and R7 are spokes and R8 is the Hub
>
> At one of the spokes>>
>
> rack9>7
> [Resuming connection 7 to R7 ... ]
>
> R7(config-if)#do ping 158.1.0.3
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.3, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 56/59/60 ms
> R7(config-if)#do ping 158.1.0.6
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.6, timeout
> is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> R7(config-if)#
>
> rack9>6
> [Resuming connection 6 to R6 ... ]
>
> R6(config)#do ping 158.1.0.3
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.3, timeout
> is 2 seconds:
>
> *Mar 5 01:39:30.392: IP: s=158.1.0.6 (local),
> d=158.1.0.3, len 100,
> unroutable.
> *Mar 5 01:39:32.392: IP: s=158.1.0.6 (local),
> d=158.1.0.3, len 100,
> unroutable.
> *Mar 5 01:39:34.392: IP: s=158.1.0.6 (local),
> d=158.1.0.3, len 100,
> unroutable.
> *Mar 5 01:39:36.392: IP: s=158.1.0.6 (local),
> d=158.1.0.3, len 100,
> unroutable.
> *Mar 5 01:39:38.392: IP: s=158.1.0.6 (local),
> d=158.1.0.3, len 100,
> unroutable.
> Success rate is 0 percent (0/5)
> R6(config)#
> R6(config)#
> rack9>3
> [Resuming connection 3 to R3 ... ]
>
> *Mar 5 00:05:15.371: %OSPF-4-ERRRCV: Received
> invalid packet: Bad Checksum
> from 1.1.123.1, Serial0/0/0.123
> R3(config-router)#
> R3(config-router)#
> R3(config-router)#
> rack9>8
> [Resuming connection 8 to R8 ... ]
> ..
> R8(config)#
> R8(config)#do deb ip pack
> IP packet debugging is on
> R8(config)#do ping 158.1.0.7
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.7, timeout
> is 2 seconds:
> !!
> *Mar 5 01:41:31.368: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.7
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:31.368: IP: s=158.1.0.3 (local),
> d=158.1.0.7 (Virtual-Access3),
> len 100, sending
> *Mar 5 01:41:31.428: IP: tableid=0, s=158.1.0.7
> (Virtual-Access3),
> d=158.1.0.3 (Virtual-Access3), routed via RIB
> *Mar 5 01:41:31.428: IP: s=158.1.0.7
> (Virtual-Access3), d=158.1.0.3
> (Virtual-Access3), len 100, rcvd 3
> *Mar 5 01:41:31.428: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.7
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:31.428: IP: s=158.1.0.3 (local),
> d=158.1.0.7 (Virtual-Access3),
> len 100, sending!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 60/60/60 ms
> R8(config)#
> *Mar 5 01:41:31.668: IP: s=158.1.0.7
> (Virtual-Access3), d=158.1.0.3
> (Virtual-Access3), len 100, rcvd 3do ping 158.1.0.7
> R8(config)#
> R8(config)#
> R8(config)#!See that all packets are sent out the
> Virtual-Access3
> R8(config)#!The router consider thisas a P2P
> connection
> R8(config)#
> R8(config)#
> R8(config)#do ping 158.1.0.6
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.6, timeout
> is 2 seconds:
>
> *Mar 5 01:41:38.632: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:38.632: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.
> *Mar 5 01:41:40.632: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:40.632: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.
> *Mar 5 01:41:42.632: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:42.632: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.
> *Mar 5 01:41:44.632: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:44.632: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.
> *Mar 5 01:41:46.000: IP: tableid=0, s=158.1.0.7
> (Virtual-Access3),
> d=158.1.0.3 (Virtual-Access3), routed via RIB
> *Mar 5 01:41:46.000: IP: s=158.1.0.7
> (Virtual-Access3), d=158.1.0.3
> (Virtual-Access3), len 56, rcvd 3
> *Mar 5 01:41:46.632: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:41:46.632: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.
> Success rate is 0 percent (0/5)
> R8(config)#
> *Mar 5 01:41:48.016: IP: tableid=0, s=158.1.0.7
> (Virtual-Access3),
> d=158.1.0.3 (Virtual-Access3), routed via RIB
> *Mar 5 01:41:48.016: IP: s=158.
>
> Now if you change to use only one Virtual-template
> on R3
>
>
> R8(config)#default int s0/0/0
> Building configuration...
>
> Interface Serial0/0/0 set to default configuration
> *Mar 5 01:43:45.268: %LINK-3-UPDOWN: Interface
> Virtual-Access3, changed state
> to down
> *Mar 5 01:43:45.272: %LINK-3-UPDOWN: Interface
> Virtual-Access2, changed state
> to downt s0/0
> *Mar 5 01:43:46.268: %LINEPROTO-5-UPDOWN: Line
> protocol on Interface
> Virtual-Access3, changed state to down/0
> R8(config-if)#line con 0
> R8(config-line)#logg syn
> R8(config-line)#exec-time 0 0
> R8(config-line)#exit
> R8(config)#default int s0/0/0
> Building configuration...
>
> Interface Serial0/0/0 set to default configuration
> R8(config)#int s0/0/0
> R8(config-if)#encap frame-relay
> R8(config-if)#no frame-relay inverse
> R8(config-if)#frame-relay interface-dlci 807 ppp
> virtual-templ 1
> R8(config-fr-dlci)#frame-relay interface-dlci 807
> ppp virtual-templ 1
> *Mar 5 01:44:34.272: %LINK-3-UPDOWN: Interface
> Virtual-Access2, changed state
> to up
> R8(config-fr-dlci)#frame-relay interface-dlci 806
> ppp virtual-templ 1
> *Mar 5 01:44:42.080: %LINK-3-UPDOWN: Interface
> Virtual-Access3, changed state
> to up
> R8(config-fr-dlci)#do show run int virtual-templa 1
> Building configuration...
>
> Current configuration : 72 bytes
> !
> interface Virtual-Template1
> ip address 158.1.0.3 255.255.255.0
> end
>
> R8(config-fr-dlci)#do pin
> *Mar 5 01:44:47.924: %LINK-3-UPDOWN: Interface
> Virtual-Access2, changed state
> to down
> *Mar 5 01:44:47.924: %LINK-3-UPDOWN: Interface
> Virtual-Access3, changed state
> to down
> R8(config-fr-dlci)#do ping
> *Mar 5 01:44:48.920: %LINEPROTO-5-UPDOWN: Line
> protocol on Interface
> Serial0/0/0, changed state to down
> R8(config-fr-dlci)#no sh
> R8(config-if)#do show run int s0/0/0
> Building configuration...
>
> Current configuration : 207 bytes
> !
> interface Serial0/0/0
> no ip address
> encapsulation frame-relay
> frame-relay interface-dlci 806 ppp
> Virtual-Template1
> frame-relay interface-dlci 807 ppp
> Virtual-Template1
> no frame-relay inverse-arp
> end
>
>
> R8(config-if)#! Lets test if it is working !!
> R8(config-if)#do ping 158.1.0.6
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.6, timeout
> is 2 seconds:
>
> *Mar 5 01:45:41.788: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:45:41.788: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending.!!!!
> Success rate is 80 percent (4/5), round-trip
> min/avg/max = 60/60/60 ms
> R8(config-if)#
> *Mar 5 01:45:43.788: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:45:43.788: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending
> *Mar 5 01:45:43.848: IP: s=158.1.0.6
> (Virtual-Access3), d=158.1.0.3, len 100,
> rcvd 2
> *Mar 5 01:45:43.848: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:45:43.848: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending
> *Mar 5 01:45:43.908: IP: s=158.1.0.6
> (Virtual-Access3), d=158.1.0.3, len 100,
> rcvd 2
> *Mar 5 01:45:43.908: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> R8(config-if)#
> *Mar 5 01:45:43.908: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending
> *Mar 5 01:45:43.968: IP: s=158.1.0.6
> (Virtual-Access3), d=158.1.0.3, len 100,
> rcvd 2
> *Mar 5 01:45:43.968: IP: tableid=0, s=158.1.0.3
> (local), d=158.1.0.6
> (Virtual-Access3), routed via FIB
> *Mar 5 01:45:43.968: IP: s=158.1.0.3 (local),
> d=158.1.0.6 (Virtual-Access3),
> len 100, sending
> *Mar 5 01:45:44.028: IP: s=158.1.0.6
> (Virtual-Access3), d=158.1.0.3, len 100,
> rcvd 2
> R8(config-if)#do u all
> All possible debugging has been turned off
> R8(config-if)#do ping 158.1.0.6
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.6, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 60/60/60 ms
> R8(config-if)#do ping 158.1.0.7
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.7, timeout
> is 2 seconds:
> .!!!!
> Success rate is 80 percent (4/5), round-trip
> min/avg/max = 56/58/60 ms
> R8(config-if)#
>
> rack9>6
> [Resuming connection 6 to R6 ... ]
>
> R6(config)#do u all
> All possible debugging has been turned off
> R6(config)#do ping 158.1.0.3
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.3, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 56/59/60 ms
> R6(config)#do ping 158.1.0.7
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.7, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 116/116/116 ms
> R6(config)#
>
> Seems to be working now :) :)
>
> Now a very interesting part is the output from this
> debug
>
> R8(config-if)#do ping 158.1.0.7
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.7, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 56/59/60 ms
> R8(config-if)#
> *Mar 5 02:10:04.100: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(PPP),
> datagramsize 18
> *Mar 5 02:10:04.200: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:04.260: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:04.320: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:04.380: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:04.440: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(IP),
> datagramsize 106
> R8(config-if)#
> *Mar 5 02:10:06.136: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(PPP),
> datagramsize 18
> R8(config-if)#do ping 158.1.0.
> *Mar 5 02:10:09.240: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(PPP),
> datagramsize 18
> *Mar 5 02:10:10.232: Serial0/0/0(o): dlci
> 807(0xC871), NLPID 0x3CF(PPP),
> datagramsize 18
> R8(config-if)#do ping 158.1.0.6
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 158.1.0.6, timeout
> is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip
> min/avg/max = 56/59/60 ms
> R8(config-if)#
> *Mar 5 02:10:10.968: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:11.028: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:11.088: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:11.148: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(IP),
> datagramsize 106
> *Mar 5 02:10:11.208: Serial0/0/0(o): dlci
> 806(0xC861), NLPID 0x3CF(IP),
> datagramsize 106
>
> See that if I ping from R8 to R7 it seems that the
> DLCI for 806 is used, go
> figure I need to read more about this !!!
>
> Nice topic
>
> thanks,
> Victor Cappuccio.-
> Network Learning Inc - A Cisco Sponsored
> Organization (SO) YES! We take
> Cisco Learning credits!
> victor@ccbootcamp.com
> http://www.ccbootcamp.com (Cisco Training and Rental
> Racks)
> http://www.ccbootcamp.com/groupstudy.html
> (groupstudy member discounts!)
> Voice: 702-968-5100
> FAX: 702-446-8012
>
>
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com on behalf of Antonio
> Soares
> Sent: Sun 3/4/2007 11:59
> To: Shamin; Ivan
> Cc: Cisco certification
> Subject: RE: EIGRP over PPP over Frame - Problem
>
> Try this in R3:
>
> !
> interface Serial2/0
> no ip address
> encapsulation frame-relay
> frame-relay interface-dlci 304 ppp
> Virtual-Template1
> frame-relay interface-dlci 305 ppp
> Virtual-Template2
> frame-relay lmi-type cisco
> !
> interface Virtual-Template1
> ip address 158.1.0.3 255.255.255.0
> ppp authentication pap chap
> !
> interface Virtual-Template2
> ip address 158.1.0.3 255.255.255.0
> ppp authentication pap chap
> !
>
> And let me know if it solves the problem.
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Shamin
> Sent: domingo, 4 de Margo de 2007 17:37
> To: Ivan
> Cc: Cisco certification
> Subject: Re: EIGRP over PPP over Frame - Problem
>
> Ivan,
>
> Thanks for your reply.
> I tried changing the subnet to 158.1.44.0/24 . But
> that does not solve the
> issue.
> R5 & R3 are able to ping R4's loopback but R4 does
> not receive any eigrp
> updates from the hub R3 or the spoke R5. Kind of
> peculiar situation i am in.
> Dont see a reason for this.
>
>
> Regards
> Shameen
>
> On 3/4/07, Ivan <ivan@iip.net> wrote:
> >
> > May be try ip address from another subnet on R4.
> For instance:
> > 158.1.44.4 Only suppose.
> >
> >
> >
> > On Sunday 04 March 2007 18:39, Shamin wrote:
> > > Hi,
> > >
> > > I tried that. But the point is, If split horizon
> is acting then R4's
> > > loopback should not be seen by R5 as well. But
> R5 is able to ping
> > > R4's loopback.
> > >
> > > Any other thing that can be a issue?
> > >
> > > regards
> > > shamin
> > >
> > > On 3/4/07, Darrin K. Pierce
> <darrin@dkpierce.com> wrote:
> > > > Try disabling split-horizon on R3.
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On
> > > > Behalf
> > Of
> > > > Shamin
> > > > Sent: Sunday, March 04, 2007 9:39 AM
> > > > To: Cisco certification
> > > > Subject: EIGRP over PPP over Frame - Problem
> > > >
> > > > Hi all,
> > > >
> > > > Hope your preparations are going good.
> > > >
> > > > I have a peculiar situation running EIGRP over
> PPPover Frame.
> > > >
> > > >
> > > > R5 ---------- R3 -------------R4
> > > >
> > > >
> > > > R3 is the hub and R4,R5 are the spokes. R3 &
> R4 are using main
> > > > interfaces. R5 is using a point -to - point
> interface.
> > > > The PPPoverFrame seems to be working. I can
> ping spoke to spoke .
> > > > Now when i enable EIGRP , over this there is a
> problem that
> > > > R4 is not receiving any Eigrp routes from R3
> or R5. I configured
> > Loopback
> > > > 100 on R3 with Ip 3.3.3.3 and advertised it
> into eigrp.
> > > > R5 seems to be receiving this route where as
> R4 is not.
> > > > R5 is able to receive the Loopback of R4 where
> as R4 is not
> > > > receiving
> > the
> > > > R5
> > > > Loopback route.
> > > >
> > > > Can any one help reason why this is happening.
> The debug commands
> > > > of eigrp is not very helpful in this. I dont
> think this is a split
> > horizon
> > > > issue as well.
> > > >
> > > > I will post the configuration on each router
> as below.
> > > >
> > > >
> >
>
----------------------------------------------------------------------
> > ---
> > > >--- ------------------------
> > > >
> > > > R3#
> > > > username Rack1R4 password 0 CISCO
> > > > username Rack1R5 password 0 CISCO
> > > > !
> > > > !
> > > > !
> > > > !
> > > > interface Loopback100
> > > > ip address 3.3.3.3 255.255.255.0
> > > > !
> > > > interface Serial2/0
> > > > no ip address
> > > > encapsulation frame-relay
> > > > frame-relay interface-dlci 304 ppp
> Virtual-Template1 frame-relay
> > > > interface-dlci 305 ppp Virtual-Template1
> > > >
> > > > !
> > > > interface Virtual-Template1
> > > > ip address 158.1.0.3 255.255.255.0 ppp
> authentication pap chap !
> > > > router eigrp 10
> > > > network 3.3.3.3 0.0.0.0
> > > > network 158.1.0.3 0.0.0.0
> > > > metric weights 0 1 1 1 0 0
> > > > no auto-summary
> > > > eigrp router-id 150.1.3.3
> > > > !
> > > >
> > > > R3#sh ip route eigrp
> > > > 4.0.0.0/24 is subnetted, 1 subnets
> > > > D 4.4.4.0 [90/2713700] via 158.1.0.4,
> 00:22:26, Virtual-Access1
> > > > 158.1.0.0/16 is variably subnetted, 11
> subnets, 2 masks
> > > > D 158.1.5.0/24 [90/2842603] via
> 158.1.0.5, 00:22:26,
> > > > Virtual-Access2 D 158.1.55.0/24
> [90/2842603] via 158.1.0.5,
> > > > 00:22:26,
> > > > Virtual-Access2
> > > > 150.1.0.0/16 is variably subnetted, 6
> subnets, 2 masks
> > > > D 150.1.5.0/24 [90/2713700] via
> 158.1.0.5, 00:22:26,
> > > > Virtual-Access2 D 150.1.4.0/24
> [90/2713700] via 158.1.0.4,
> > > > 00:22:26, Virtual-Access1
> > > >
> > > >
> > > >
> >
>
----------------------------------------------------------------------
> > ---
> > > >---
>
--------------------------------------------------------
> > > >
> > > > R4#
> > > > username Rack1R3 password 0 CISCO
> > > > !
> > > > !
> > > > interface Loopback0
> > > > ip address 150.1.4.4 255.255.255.0 !
> > > > interface Loopback100
> > > > ip address 4.4.4.4 255.255.255.0
> > > > !
> > > > interface Serial0/0
> > > > no ip address
> > > > encapsulation frame-relay
> > > > frame-relay interface-dlci 403 ppp
> Virtual-Template1 !
> > > > !
> > > > interface Virtual-Template1
> > > > ip address 158.1.0.4 255.255.255.0 no peer
> neighbor-route !
> > > > router eigrp 10
> > > > network 4.4.4.4 0.0.0.0
> > > > network 150.1.4.4 0.0.0.0
> > > > network 158.1.0.4 0.0.0.0
> > > > network 158.1.45.4 0.0.0.0
> > > > metric weights 0 1 1 1 0 0
> > > > no auto-summary
> > > > eigrp router-id 150.1.4.4
> > > > !
> > > >
> > > >
> > > > R4#sh ip route
> > > >
> > > > Gateway of last resort is not set
> > > >
> > > > C 204.12.1.0/24 is directly connected,
> Ethernet0/1
> > > > 4.0.0.0/24 is subnetted, 1 subnets
> > > > C 4.4.4.0 is directly connected,
> Loopback100
> > > > 158.1.0.0/24 is subnetted, 1 subnets
> > > > C 158.1.0.0 is directly connected,
> Virtual-Access1
> > > > C 192.10.1.0/24 is directly connected,
> Ethernet0/0
> > > > 150.1.0.0/24 is subnetted, 1 subnets
> > > > C 150.1.4.0 is directly connected,
> Loopback0
> > > >
> > > >
> > > >
> > > >
> > > >
> >
>
----------------------------------------------------------------------
> > ---
> > > >--- ----------------------------------------
> > > >
> > > > R5#
> > > > !
> > > > !
> > > > !
> > > > interface Loopback0
> > > > ip address 150.1.5.5 255.255.255.0 !
> > > > interface Ethernet0/0
> > > > ip address 158.1.5.5 255.255.255.0 half-duplex
> !
> > > > interface Serial0/0
> > > > no ip address
> > > > encapsulation frame-relay
> > > > !
> > > > interface Serial0/0.1 point-to-point
> frame-relay interface-dlci
> > > > 503 ppp Virtual-Template1 !
> > > > interface Ethernet0/1
> > > > ip address 158.1.55.5 255.255.255.0
> half-duplex !
> > > > interface Virtual-Template1
> > > > ip address 158.1.0.5 255.255.255.0 ppp chap
> password 0 CISCO !
> > > > router eigrp 10
> > > > network 150.1.5.5 0.0.0.0
> > > > network 158.1.0.5 0.0.0.0
> > > > network 158.1.5.5 0.0.0.0
> > > > network 158.1.45.5 0.0.0.0
> > > > network 158.1.55.5 0.0.0.0
> > > > metric weights 0 1 1 1 0 0
> > > > no auto-summary
> > > > eigrp router-id 150.1.5.5
> > > > !
> > > >
> > > > R5#sh ip route eigrp
> > > > 3.0.0.0/24 is subnetted, 1 subnets
> > > > D 3.3.3.0 [90/2713700] via 158.1.0.3,
> 00:36:01, Virtual-Access1
> > > > 4.0.0.0/24 is subnetted, 1 subnets
> > > > D 4.4.4.0 [90/5273700] via 158.1.0.3,
> 00:35:31, Virtual-Access1
> > > > 158.1.0.0/16 is variably subnetted, 5
> subnets, 2 masks
> > > > D 158.1.0.4/32 [90/5145700] via
> 158.1.0.3, 00:54:44,
> > > > Virtual-Access1 150.1.0.0/24 is subnetted, 2
> subnets
> > > > D 150.1.4.0 [90/5273700] via 158.1.0.3,
> 00:30:47,
> > Virtual-Access1
> > > >
> > > >
> >
>
----------------------------------------------------------------------
> > ---
> > > >---
> ----------------------------------------------
> > > >
> > > > Your help will be much appreciated. I dont see
> a reason why after
> > forming
> > > > an
> > > > adjacency between R3 & R4 , the routes are
> only updated one way
> > > > i.efrom
> > > > R4
> > > > to R3 and R5 but not back.
> > > >
> > > > Regards
> > > > Shameen
> > > >
> > > >
> >
>
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:50 ART