Also sprach Michael J. Hartwick
The consensus seems to be go with multiple pools and be happy. :) It looks like I need to number into temporary address space, delete the current pool, then create the new ones. If I could get the aggregate to work the way I think it should I would be happy.
You might be better off letting your next hop handle the aggregation. Aggregates never worked the way I (personally) thought they should on the Arcs. I was always of the idea that combining network aggregation with IP pool definitions was a bad idea. I always thought they should have defined IP pools, and then handled aggregation of routes in a seperate control area, but, 3Com has a history of not listening to me, so here we are. :)
I have version 4.1.59 on the ARC so am stuck with RIP. :(
My suggestion would be to go ahead and let the Arc advertise out everything as individual routes. Let your next hop (cisco?) pick up those rip routes (hint: passive-interface in IOS is your friend!) and redistribute them and/or aggregate them into the routing protocol of your choice, in the manner of your choosing. This is what I do. Despite being on new enough code to have OSPF on the Arcs, I've stuck with RIPv2, and let my next hop cisco redistribute into OSPF, aggregating in the process. With liberal use of passive-interface settings on the Cisco, I have very low CPU usage on the cisco boxes (including a 2500 in one city), as the cpu hit with RIP in IOS is keeping track of timers for re-broadcasting the routes. If you passive-interface all of your RIP interfaces on your cisco system, it doesn't have to keep track of all of those timers (on a per-route basis!) and as such will significantly lower your CPU usage. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.