Just a side note, You can not delete a pool that is in use, and I believe you can not modify either. I find it nice to have 3 pools on each TC that way I can disable one and fill up the others if I need to do maint. on a pool. -Steve On Wed, May 30, 2001 at 12:37:47PM -0400, Mike Andrews wrote:
1) Try starting at .65, .129, and .193, size 62.
2) Create a new pool with a different name instead of trying to modify the old one. Then delete the old one. (It's smart enough to know if the old one is in use; it just marks it "delete pending", and then once everyone's logged out, it'll go poof on its own)
Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet access for Frankfort, Lexington, Louisville and surrounding counties www.fark.com: If it's not news, it's Fark. (Or something like that.)
On Wed, 30 May 2001, Michael J. Hartwick wrote:
Hi, we have a Hiper box that we have been adding some DSP cards to. My problem is extending the IP pool to cover the extra ports. Currently there are 4 DSP's with 2 more to be added today. They are using PRI's, but I want to put 24 IP's per DSP into the ARC.
I currently have 1 pool defined as: Name Address Size InUse State Route Status pool1 xxx.xxx.xx.112/C 96 24 PUBLIC NO_AGGREGATE ACTIVE
I want to change it to start at .64 and have 144 addresses. I think the best way would be to define 3 pools:
.64/26 size 64 .128/26 size 64 .192/28 size 64
I even tried to just change the start address and pool size and the thing complains.
set ip pool pool1 iniTIAL_POOL_ADDRESS xxx.xxx.xx.64/C size 144 CLI - Request SET IP POOL failed on field INITIAL_POOL_ADDRESS CLI - Request failed with error: BAD_VALUE on value: 0.0.0.8
Any suggestions?
Michael
---------------------------------------------------------------------- Michael J. Hartwick, VE3SLQ hartwick@hartwick.com Hartwick Communications Consulting (519) 396-7719 Kincardine, ON, CA http://www.hartwick.com ----------------------------------------------------------------------
- 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.
- 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.
-- Steve Johnson - linuxnut@sonic.net Sonic.net, Inc. System Administrator 300 B Street #100 707.522.1000 (Voice) Santa Rosa, CA 95404 707.547.2199 (Fax) http://www.sonic.net/ - 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.