With our providers, when we request new addresses we have to be able to
justify them.  By that I mean they want to see that we will actually be
using 80% of the assigned addresses within three months.  In the case of a
company wanting to multihome some web servers, chances are that they're
really only going to use a handfull of addresses.

So (and I admit I've had to do this myself--twice) you have to fib when you
apply for the addresses.    If you were to say that you only intended to
use 10 addresses but you really need an entire /24, they might not approve
it.  Our current provider, Sprint, would *not* approve a /24 assignment on
my first request when I stated our actual usage expectations.  Miraculously,
by the time of our second request our usage expectations had risen
enormously.  :-)

|  Re the below, if you decide after some consideration that you want
|  different links from different isps, by default if you tell them you're
|  going to do that, you should be able to get at least a /24.  If you
cannot
|  get that after telling them you're multihoming, cross em off your list.
|  
|       Brian
|  
|  >
|  > Yet another related issue is that of getting at least a /24 so that
your
|  > routes won't get filtered.  Many ISPs filter prefixes with masks longer
than
|  > /24.  If you don't really need a /24 but you really want redundancy,
you're
|  > still wasting addresses that might have been used better elsewhere.
|  >
|  >
|  > Regards,
|  > John
|  >
|  >
|  >
|  >
|  >
|  > _______________________________________________________
|  > Send a cool gift with your E-Card
|  > http://www.bluemountain.com/giftcenter/
|  >
|  >
|  >
|  >
|  >
|





_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=7865&t=7835
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to