[nsp] 7206 NPE-200 with PA-A3-8T1IMA for DSL aggregation problems
Charles Sprickman
spork at inch.com
Wed Apr 23 19:11:04 EDT 2003
On Wed, 23 Apr 2003, Siva Valliappan wrote:
> you probably want to move away from an IRB style configuration to an
> RBE mode of configuration which is much more higher performing. not
> sure of your specific problem, but the recommended solution for
> aggregation of bridged DSL ATM customers is RBE, and this is the more
> intensely tested solution.
I agree with that. We're moving people to RBE slowly, and it's solved a
few very mysterious problems.
> for more information you can take a look at:
>
> http://www.cisco.com/en/US/tech/tk175/tk15/technologies_configuration_example09186a0080093e43.shtml
Any other notes people have on RBE would be appreciated. The only
downside here is that there's a lot more config per customer, and you burn
up more IDBs. I'd love to hear some nsp'ers little tips and tricks,
especially along the lines of what you discuss below:
> it also gives you support for multiple DHCP extensions. including typing
> RBE interface to provide Option 82 support so that you can limit the
> number of IP addresses that are given out to each interface, etc.
Thanks,
Charles
> cheers
> .siva
>
> On Wed, 23 Apr 2003, Denise Sandell wrote:
>
> >
> > Greetings:
> >
> > I'm experiencing problems with this configuration for DSL aggregation,
> > and was hoping for some advice:
> >
> > 7206 NPE-200 w/64MB RAM, PA-A3-8T1IMA running 12.2(16)
> >
> > First of all, 12.2(16) is quite the ram-hog, so I'm running with ~3MB
> > free memory. Previous to running 16, I was running 12.2(13), which
> > had its own set of issues (like random reloading when configuring
> > BVIs), yet it ran with ~10MB free.
> >
> > This router is aggregating DSL customers on 2 ATM T1s (no IMA group
> > configured), using IRB, and I'm running into problems where they're
> > intermittently unable to pass traffic over the BVIs. There are
> > approximately 120 customers terminated to this router with about ~25 BVIs
> > configured. This does not seem to affect other traffic on the router at
> > all, other interfaces tx/rx normally.
> >
> > The questions I have are:
> >
> > . Has anyone else run into this problem?
> > . Will upgrading to 128MB fix the problem?
> > . Are there other suggested images to run (12.0 or 12.2 track) for
> > such a configuration before attempting to upgrade memory?
> >
> > Any suggestions would be appreciated!
> >
> > --
> > - Denise Sandell network operations -
> > - dsandell at voyager.net voyager.net, a CoreComm company -
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list