[c-nsp] MLPPP bridged

Rodney Dunn rodunn at cisco.com
Wed Sep 1 17:40:02 EDT 2004


Ok.  You have most of the fixes I had helped with
except:

CSCed29590
Externally found severe defect: Resolved (R)
Multilink PPP link flap causes output frozen for member link

If you set it back up and can recreate it let me know.

It would save some time if you could do it on 12.3(10)
but if it's production and you don't want to upgrade
first that's fine too.

It's gonna take some debugging to figure out in
which direction the packets are getting dropped
and why.  Figuring out direction is the first
step in isolating the problem for something like this.

Rodney


On Wed, Sep 01, 2004 at 04:03:45PM -0500, Kevin wrote:
> I'm using 12.3(5a) on my 7513.
> 
> Kevin, 
> 
> -----Original Message-----
> From: Rodney Dunn [mailto:rodunn at cisco.com] 
> Sent: Tuesday, August 31, 2004 12:46 PM
> To: Kevin
> Cc: Rodney Dunn; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] MLPPP bridged
> 
> On Tue, Aug 31, 2004 at 11:17:21AM -0500, Kevin wrote:
> > I've been having really odd issue with MLPPP on the 7513, for one I'm 
> > using an 8 port FSIP board instead of a PA,
> 
> Ok. So you don't get dCEF in/out of this slot.
> 
>  
> > And the main problems I've been having are based on the cpu load, I 
> > have an RSP4 which could be a problem.
> 
> Depends on overall traffic load.
> 
> 
> > But basically If I have dCEF enabled, then the multilink breaks, can't
> 
> > ping the other side, BGP session does'nt come up, etc. Between 2 BGP 
> > sessions and 1 MLPPP on the 7513,
> 
> Do I recommend this setup on the 75xx? No.
> Should it work, yes if you are not in 12.0S code.
> 
> What code are you on?
> 
> > it's really taxing the RSP4.
> 
> Bundling a few T1's together should not be a big deal for an RSP4
> assuming the other transit traffic through the box is dCEF switched for
> the cards that support it.
> 
> If you want to debug it let me know.
> 
> > 
> > Kevin,
> > 
> > -----Original Message-----
> > From: Rodney Dunn [mailto:rodunn at cisco.com]
> > Sent: Tuesday, August 31, 2004 9:53 AM
> > To: Kevin
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] MLPPP bridged
> > 
> > On Mon, Aug 30, 2004 at 05:54:29PM -0500, Kevin wrote:
> > > With all the issues I have with MLPPP on a 7513,
> > 
> > Could you elaborate on the issues?  I've posted a list of MLPPP bugs 
> > that have been fixed in the last 6 months for the 75xx with dMLPPP and
> 
> > if you are not running code that has those fixes you surely will have 
> > some problems.
> > 
> > > I decided todo a setup which includes a 3620 with the multilink 
> > > bundle
> > 
> > > and a fastethernet interface to the 7513, On the 3620 I disabled ip 
> > > routing and put the multilink interface and the fastethernet in the 
> > > same bridge-group, All the interfaces are up and looks like I have 
> > > incoming and outgoing packets, But I can't ping from the 7513 to the
> > otherside.
> > > Does anyone have any suggestions to why this would happen?
> > 
> > a) You don't have an ip address on the 36xx so any pings to/from it 
> > will no work
> > b) On the 75xx side it's important if you have a BVI to interface
> >    the bridge to the L3 side of the router.
> >    I would need to see the 75xx configuration.
> > 
> > I don't know what you are trying to do here but I highly do NOT 
> > recommend you do this because the bridging code for something like 
> > this is performance wise would be horrible.
> > 
> > Rodney
> > 
> >  
> > 
> > > 
> > > Kevin,
> > > 
> > > Here's the running config on the 3620:
> > > 
> > > version 12.2
> > > service timestamps debug uptime
> > > service timestamps log uptime
> > > no service password-encryption
> > > !
> > > hostname mlppp-router
> > > !
> > > !
> > > ip subnet-zero
> > > no ip routing
> > > !
> > > !
> > > !
> > > call rsvp-sync
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > interface Multilink1
> > >  no ip address
> > >  ppp multilink
> > >  multilink-group 1
> > >  bridge-group 1
> > > !
> > > interface FastEthernet0/0
> > >  no ip address
> > >  no ip route-cache
> > >  no ip mroute-cache
> > >  speed 100
> > >  full-duplex
> > >  bridge-group 1
> > > !
> > > interface Serial1/0
> > >  no ip address
> > >  encapsulation ppp
> > >  no ip route-cache
> > >  no ip mroute-cache
> > >  serial restart-delay 0
> > >  ppp multilink
> > >  multilink-group 1
> > > !
> > > interface Serial1/1
> > >  no ip address
> > >  encapsulation ppp
> > >  no ip route-cache
> > >  no ip mroute-cache
> > >  serial restart-delay 0
> > >  ppp multilink
> > >  multilink-group 1
> > > !
> > > interface Serial1/2
> > >  no ip address
> > >  encapsulation ppp
> > >  no ip route-cache
> > >  no ip mroute-cache
> > >  serial restart-delay 0
> > >  ppp multilink
> > >  multilink-group 1
> > > !
> > > interface Serial1/3
> > >  no ip address
> > >  no ip route-cache
> > >  no ip mroute-cache
> > >  shutdown
> > >  serial restart-delay 0
> > > !
> > > ip classless
> > > no ip http server
> > > !
> > > bridge 1 protocol ieee
> > > !
> > > dial-peer cor custom
> > > !
> > > !
> > > !
> > > !
> > > line con 0
> > > line aux 0
> > > line vty 0 4
> > >  login
> > > !
> > > end
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > 
> > 
> > 
> 
> 
> 


More information about the cisco-nsp mailing list