From: Cisco Net (network.cisco@gmail.com)
Date: Mon Oct 18 2004 - 19:05:52 GMT-3
I had the same issue as well.
Searched on IE mailing lists and could not find an excact reason yet.
The best answer i got was,
enable "frame relay traffic shaping" command on the interface will
supress one error message. And about the service policy error message,
later on this lab, you will be enabling the QoS on this interface....
But i am not very clear whether these 2 commands are required when i
enable mlppp or not. Functionaly everything is working without these
commands.
If you get any response with more accurate answers please let me also know.
By the way in this lab "show ppp multilink" was showing that only one
interface is part of the bundle. And this is happened when both serial
sub interfaces binded to the same virtual tem interface.
When i had different virtual interfaces for each sub interfaces it was
showing both interfaces part of the bundle.
Please let me know if you had that issue or not.
Regards
Cert
On Mon, 18 Oct 2004 09:33:38 -0400, ccie2be <ccie2be@nyc.rr.com> wrote:
> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:49 GMT-3