Hey Terry, This is WAY late, but I just now saw your post :) Anyways, here's how to split a class-c among a group of Maxes: 0/26 - pool1 (6096-1) 64/27 - pool2 (6096-1) 96/27 - pool1 (6096-2) 128/26 - pool2 (6096-2) 192/27 - pool1 (4048-1) 224/28 - pool2 (4048-1) 240/28 - static IP assignments Congratulations, you've just split a class C to support 10 PRI and 15 static IP customers. Of course, if you have a 3rd 6096 and no 4048, you can use the last 64 addresses of that class-c and the first 32 addresses of the next class-c as the dialup pools, then go from there. -- Troy Settle Pulaski Networks 540.994.4254 - 866.477.5638 http://www.psknet.com > -----Original Message----- > From: owner-ascend-users at max.bungi.com > [mailto:owner-ascend-users at max.bungi.com] On Behalf Of Terry > Lee, Publisher > Sent: Monday, April 08, 2002 12:59 PM > To: ascend-users at bungi.com > Subject: (ASCEND) MAXen and route summarization > > > Hello friends, > > Can any of you clue me in as to the most efficient way to use Class C > address blocks when assigning MAX6000 IP pools that will also > take advantage > of the so-called "route summarization" feature? The docs call > for setting up > address pools which are "network aligned" in order to facilitate route > summarization. > > Since a MAX has (in our particular case) 92 usable modems, > would it not seem > best to break the class C's in half and subnet mask at > 255.255.255.192 , > allowing 2 "network aligned" MAXen to occupy each Class C? > The only downside > to this that I can see is a waste of 35 IPs per subnet. > > Any counter-suggestions? > > > > --==\T/==-- > > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/