From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Oct 22 2004 - 05:31:24 GMT-3
It's a bug in fast switching that has something to do with this
specific topology. Issue the "no ip route-cache" command on the
multilink interface and it should be fine.
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Nico van Niekerk
> Sent: Friday, October 22, 2004 3:28 AM
> To: ccie2be; Group Study
> Subject: RE: mlp over F/R -- IE lab 8
>
> I got the same message... and everything seemed to work.
> After I did the routing protocols, my routing tables looked fine, and
I
> could ping from R3 to anywhere behind R2, and from R2 anywhere on R3,
but
> not behind R3. The route to dest is there and there's a route back to
> source, the problem is not in the routing. Also the first time I ping,
> only
> the first packet gets back, then no ping gets through. After 10min the
> first
> packet agian gets through. I suppose some sort of cache has something
to
> do
> with this. Also, I suspect the problem is on R2 where the MLPoFR
bundles
> the
> 2 subinterfaces. Did you have the same issue?
> Any ideas of how to fix this?
>
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
Of
> > ccie2be
> > Sent: Monday, 18 October 2004 11:34 PM
> > To: Group Study
> > Subject: mlp over F/R -- IE lab 8
> >
> >
> > Hi guys,
> >
> > I was configuring R2 to connect to R3 using mlp over f/r when I
> > got this error
> > message:
> >
> >
> >
> > Rack1R2#
> > *Mar 1 09:41:29.950: %LINK-3-UPDOWN: Interface Virtual-Access4,
> > changed state
> > t
> > o up
> > *Mar 1 09:41:30.014: %FR-3-MLPOFR_ERROR: MLPoFR not configured
> > properly on
> > Link
> > Virtual-Access4 Bundle Multilink1 :Missing service policy
> > config in Virtual
> > Te
> > mplate
> > *Mar 1 09:41:30.018: %FR-3-MLPOFR_ERROR: MLPoFR not configured
> > properly on
> > Link
> > Virtual-Access4 Bundle Multilink1 :Frame Relay traffic shaping must
be
> > enabled
> > Rack1R2#
> > *Mar 1 09:41:30.859: %SYS-5-CONFIG_I: Configured from console by
> console
> > *Mar 1 09:41:31.016: %LINEPROTO-5-UPDOWN: Line protocol on
Interface
> > Virtual-Ac
> > cess4, changed state to up
> >
> > However, pings across the f/r cloud still work.
> >
> > Here's the config on R2:
> >
> > interface Multilink1
> > ip address 174.3.23.2 255.255.255.0
> > ppp multilink
> > multilink-group 1
> > !
> > interface Serial0/0
> > no ip address
> > encapsulation frame-relay
> > !
> > interface Serial0/0.203 point-to-point
> > frame-relay interface-dlci 203 ppp Virtual-Template1
> > !
> > interface Serial0/0.213 point-to-point
> > frame-relay interface-dlci 213 ppp Virtual-Template1
> > !!
> > interface Virtual-Template1
> > no ip address
> > ppp multilink
> > multilink-group 1
> > ********************************************************************
> >
> > R3's config:
> >
> > interface Multilink1
> > ip address 174.3.23.3 255.255.255.0
> > ppp multilink
> > multilink-group 1
> > !
> > interface Serial1/0
> > no ip address
> > encapsulation frame-relay
> > frame-relay interface-dlci 302 ppp Virtual-Template1
> > !
> > interface Serial1/1
> > no ip address
> > encapsulation frame-relay
> > frame-relay interface-dlci 312 ppp Virtual-Template1
> > !
> > interface Virtual-Template1
> > no ip address
> > ppp multilink
> > multilink-group 1
> >
> > But, pings between R2 and R3 work:
> >
> > Rack1R3#p 174.3.23.2
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 174.3.23.2, timeout is 2 seconds:
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16
ms
> >
> > So, what should I make of that error message? Is it OK for me to
> > ignore it or
> > will it bite me in the butt at some point?
> >
> > Thanks, Tim
> >
> >
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:51 GMT-3