Florin_Neamtu@3com.com writes...
The automated way to do this is with NMC chassis awareness, dynamic slot assignment and dsa idle rebalancing.
. . .
As far as IP pool assignment...the best way to get this to work with the above setup is to set each Arc with two ip pools and
set: disable ip address_pool_round_robin
Then set the first arc with pool 1 first, pool 2 second, and the second arc with pool 2 first and pool 1 second.
Unless you set these as no_aggregate, both ARC's will announce routes for both pools. And even if you do set them no_aggregate, replacing the failed ARC will cause it start using addresses the other backup ARC had been assigning (assuming it used up all of it's first pool). In any case, this doesn't sound like such a good idea. The only obvious solution is to assign 2x the number of addresses to each ARC, or use some kind of radius-based IP address resource allocation. -- Aaron Nabil - 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.