Colocation & IP addresses

"Gordon Hudson" <gordon DeleteThis @usenet.hostroute.co.uk> wrote in message news:<buo8r0$nfn$1$8302bc10@news.demon.co.uk>...
 > "Gregory Toomey" <nospam DeleteThis @bigpond.com> wrote in message
 > news:bunu5j$hgaka$1@ID-202028.news.uni-berlin.de...
  > > This is a "what if" question for the Lilnux gurus.
  > >
  > > If I build my own server & place it in the local colo, do I have to set up
  > > the IP address beforehand? And what happens if the IP changes.
  > >
  > > Presumably you will want to set up the server so that you cant be "locked
  > > out" if you make a mistake with IP addresses.
 >
 > Normally what happens is you give them the root IP and they add the IP

Define "normally" - that's nothing like the experiences I have of the
colocations we use and have used.

How it works for me, is I tell them how many IPs I want now, and how
many I think I'll possibly need - they provide the block of IPs, the
subet, gateway etc, and I program them into the box while at the
data-center. I check the server is visible from from their network,
and from outside of their network BEFORE I leave the data-center.

We have a few hundred IPs at the moment, and will be getting two
class-Cs of our own shortly.

We sell a lot of dedicated IP hosting accounts - host a lof of stores
with their own SSL certs, and chew through a lot of IPs in fact, we're
the biggest user of IPs in the data-center - more than the data-center
themselves. Is this a problem for them? No... they just check once a
quarter that we're using the IPs we are given, and they are fine when
I call and ask for another block of 16 or so.

So in summary, the experience may vary from data-center to
data-center, so to the OP - ask the data-center. Try to explain how
the box will be setup - are you going to use dedicated IPs for clients
- offer SSL certs for clients etc, or are you doing everything
"virtually", your IP usage will probably be light.

hth

Greg Hewitt-Long - <a style='text-decoration: underline;' href="http://webyourbusiness.com/" target="_blank">http://webyourbusiness.com/</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses 

Greg Hewitt-Long wrote:

 > "Gordon Hudson" <gordon.TakeThisOut@usenet.hostroute.co.uk> wrote in message
 > news:<buo8r0$nfn$1$8302bc10@news.demon.co.uk>...
  >> "Gregory Toomey" <nospam.TakeThisOut@bigpond.com> wrote in message
  >> news:bunu5j$hgaka$1@ID-202028.news.uni-berlin.de...
   >> > This is a "what if" question for the Lilnux gurus.
   >> >
   >> > If I build my own server & place it in the local colo, do I have to set
   >> > up the IP address beforehand? And what happens if the IP changes.
   >> >
   >> > Presumably you will want to set up the server so that you cant be
   >> > "locked out" if you make a mistake with IP addresses.
  >>
  >> Normally what happens is you give them the root IP and they add the IP
 >
 > Define "normally" - that's nothing like the experiences I have of the
 > colocations we use and have used.
 >
 > How it works for me, is I tell them how many IPs I want now, and how
 > many I think I'll possibly need - they provide the block of IPs, the
 > subet, gateway etc, and I program them into the box while at the
 > data-center. I check the server is visible from from their network,
 > and from outside of their network BEFORE I leave the data-center.
 >
 > We have a few hundred IPs at the moment, and will be getting two
 > class-Cs of our own shortly.
 >
 > We sell a lot of dedicated IP hosting accounts - host a lof of stores
 > with their own SSL certs, and chew through a lot of IPs in fact, we're
 > the biggest user of IPs in the data-center - more than the data-center
 > themselves. Is this a problem for them? No... they just check once a
 > quarter that we're using the IPs we are given, and they are fine when
 > I call and ask for another block of 16 or so.
 >
 > So in summary, the experience may vary from data-center to
 > data-center, so to the OP - ask the data-center. Try to explain how
 > the box will be setup - are you going to use dedicated IPs for clients
 > - offer SSL certs for clients etc, or are you doing everything
 > "virtually", your IP usage will probably be light.
 >
 > hth
 >
<font color=purple> > Greg Hewitt-Long - <a style='text-decoration: underline;' href="http://webyourbusiness.com/</font" target="_blank">http://webyourbusiness.com/</font</a>>

That's how I thought it would work. Checking it out at the data centre is
the way to go. If you do colo it really must be in the local area because
there are plenty of things that can go wrong.

I raied this becuse I've seen people sending machines across the country for
colocation so they MUST get the IPs right, and idiots changing their
machine's IP and not being able to access it.

So my ultimate colo wish list is
1. be able to do a remote reboot
2. be able to remote BIOS ( I think some expensive motherboards have this -
supermicro?)
3. be able to watch the boot log if the system fails to boot (perhaps thru a
remote serial port)
4. be able to ssh no matter what (eg IP stuffup)

This may sound a bit out of the reach at the moment but I thinks its needed.
The ISP I'm using at the moment just lost a box with mirrored RAID disks &
I'm glad it wasn't my site!

gtoomey<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses 

Gregory Toomey wrote:
 > Greg Hewitt-Long wrote:
 >
  >> "Gordon Hudson" <gordon RemoveThis @usenet.hostroute.co.uk> wrote in message
  >> news:<buo8r0$nfn$1$8302bc10@news.demon.co.uk>...
   >>> "Gregory Toomey" <nospam RemoveThis @bigpond.com> wrote in message
   >>> news:bunu5j$hgaka$1@ID-202028.news.uni-berlin.de...
   >>>> This is a "what if" question for the Lilnux gurus.
   >>>>
   >>>> If I build my own server & place it in the local colo, do I have
   >>>> to set up the IP address beforehand? And what happens if the IP
   >>>> changes.
   >>>>
   >>>> Presumably you will want to set up the server so that you cant be
   >>>> "locked out" if you make a mistake with IP addresses.
   >>>
   >>> Normally what happens is you give them the root IP and they add the
   >>> IP
  >>
  >> Define "normally" - that's nothing like the experiences I have of the
  >> colocations we use and have used.
  >>
  >> How it works for me, is I tell them how many IPs I want now, and how
  >> many I think I'll possibly need - they provide the block of IPs, the
  >> subet, gateway etc, and I program them into the box while at the
  >> data-center. I check the server is visible from from their network,
  >> and from outside of their network BEFORE I leave the data-center.
  >>
  >> We have a few hundred IPs at the moment, and will be getting two
  >> class-Cs of our own shortly.
  >>
  >> We sell a lot of dedicated IP hosting accounts - host a lof of stores
  >> with their own SSL certs, and chew through a lot of IPs in fact,
  >> we're the biggest user of IPs in the data-center - more than the
  >> data-center themselves. Is this a problem for them? No... they
  >> just check once a quarter that we're using the IPs we are given, and
  >> they are fine when I call and ask for another block of 16 or so.
  >>
  >> So in summary, the experience may vary from data-center to
  >> data-center, so to the OP - ask the data-center. Try to explain how
  >> the box will be setup - are you going to use dedicated IPs for
  >> clients
  >> - offer SSL certs for clients etc, or are you doing everything
  >> "virtually", your IP usage will probably be light.
  >>
  >> hth
  >>
<font color=green>  >> Greg Hewitt-Long - <a style='text-decoration: underline;' href="http://webyourbusiness.com/</font" target="_blank">http://webyourbusiness.com/</font</a>>
 >
 > That's how I thought it would work. Checking it out at the data
 > centre is the way to go. If you do colo it really must be in the
 > local area because there are plenty of things that can go wrong.
 >
 > I raied this becuse I've seen people sending machines across the
 > country for colocation so they MUST get the IPs right, and idiots
 > changing their machine's IP and not being able to access it.
 >
 > So my ultimate colo wish list is
 > 1. be able to do a remote reboot
 > 2. be able to remote BIOS ( I think some expensive motherboards have
 > this - supermicro?)
 > 3. be able to watch the boot log if the system fails to boot (perhaps
 > thru a remote serial port)
 > 4. be able to ssh no matter what (eg IP stuffup)

This any good for you? I believe other manufacturers have similar options.

<a style='text-decoration: underline;' href="http://h18004.www1.hp.com/products/servers/management/remote-lightsout/description.html" target="_blank">http://h18004.www1.hp.com/products/servers/management/remote-lightsout...scripti</a>

 > This may sound a bit out of the reach at the moment but I thinks its
 > needed. The ISP I'm using at the moment just lost a box with mirrored
 > RAID disks & I'm glad it wasn't my site!

ouch!

--
William Tasso - <a style='text-decoration: underline;' href="http://WilliamTasso.com" target="_blank">http://WilliamTasso.com</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses 

"Gregory Toomey" <nospam DeleteThis @bigpond.com> wrote in message
news:buorck$k5shf$1@ID-202028.news.uni-berlin.de...
 > Greg Hewitt-Long wrote:
 >
  > > "Gordon Hudson" <gordon DeleteThis @usenet.hostroute.co.uk> wrote in message
  > > news:<buo8r0$nfn$1$8302bc10@news.demon.co.uk>...
   > >> "Gregory Toomey" <nospam DeleteThis @bigpond.com> wrote in message
   > >> news:bunu5j$hgaka$1@ID-202028.news.uni-berlin.de...
   > >> > This is a "what if" question for the Lilnux gurus.
   > >> >
   > >> > If I build my own server & place it in the local colo, do I have to
set
   > >> > up the IP address beforehand? And what happens if the IP changes.
   > >> >
   > >> > Presumably you will want to set up the server so that you cant be
   > >> > "locked out" if you make a mistake with IP addresses.
   > >>
   > >> Normally what happens is you give them the root IP and they add the IP
  > >
  > > Define "normally" - that's nothing like the experiences I have of the
  > > colocations we use and have used.
  > >
  > > How it works for me, is I tell them how many IPs I want now, and how
  > > many I think I'll possibly need - they provide the block of IPs, the
  > > subet, gateway etc, and I program them into the box while at the
  > > data-center. I check the server is visible from from their network,
  > > and from outside of their network BEFORE I leave the data-center.
  > >
  > > We have a few hundred IPs at the moment, and will be getting two
  > > class-Cs of our own shortly.
  > >
  > > We sell a lot of dedicated IP hosting accounts - host a lof of stores
  > > with their own SSL certs, and chew through a lot of IPs in fact, we're
  > > the biggest user of IPs in the data-center - more than the data-center
  > > themselves. Is this a problem for them? No... they just check once a
  > > quarter that we're using the IPs we are given, and they are fine when
  > > I call and ask for another block of 16 or so.
  > >
  > > So in summary, the experience may vary from data-center to
  > > data-center, so to the OP - ask the data-center. Try to explain how
  > > the box will be setup - are you going to use dedicated IPs for clients
  > > - offer SSL certs for clients etc, or are you doing everything
  > > "virtually", your IP usage will probably be light.
  > >
  > > hth
  > >
<font color=green>  > > Greg Hewitt-Long - <a style='text-decoration: underline;' href="http://webyourbusiness.com/</font" target="_blank">http://webyourbusiness.com/</font</a>>
 >
 > That's how I thought it would work. Checking it out at the data centre is
 > the way to go. If you do colo it really must be in the local area because
 > there are plenty of things that can go wrong.
 >
 > I raied this becuse I've seen people sending machines across the country
for
 > colocation so they MUST get the IPs right, and idiots changing their
 > machine's IP and not being able to access it.
 >
 > So my ultimate colo wish list is
 > 1. be able to do a remote reboot
 > 2. be able to remote BIOS ( I think some expensive motherboards have
this -
 > supermicro?)
 > 3. be able to watch the boot log if the system fails to boot (perhaps thru
a
 > remote serial port)
 > 4. be able to ssh no matter what (eg IP stuffup)
 >
 > This may sound a bit out of the reach at the moment but I thinks its
needed.
 > The ISP I'm using at the moment just lost a box with mirrored RAID disks &
 > I'm glad it wasn't my site!
 >
 > gtoomey


You don't HAVE to have a local colo place. We colo machines for customers
from all over the world. They order, we give them their IPs, they configure
their machines and ship them to us...we plug them in. If they have any
trouble initially, we gladly help out.


--Tina

--
<a style='text-decoration: underline;' href="http://www.AffordableHOST.com" target="_blank">http://www.AffordableHOST.com</a>
20% Discount Code: newsgroup
We transfer time from your current host!
Serving the web since 1997<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses 

"Tina - AffordableHOST.com" <tina DeleteThis @affordablehost.com> wrote in message
news:100vure3ftdfn51@corp.supernews.com...

 > You don't HAVE to have a local colo place. We colo machines for customers
 > from all over the world. They order, we give them their IPs, they
configure
 > their machines and ship them to us...we plug them in. If they have any
 > trouble initially, we gladly help out.

Sounds like a great service Tina. Do you do hardware repairs for them?
--
Charles Sweeney
<a style='text-decoration: underline;' href="http://www.CharlesSweeney.com" target="_blank">www.CharlesSweeney.com</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses 

William Tasso wrote:

 > Gregory Toomey wrote:
  >> Greg Hewitt-Long wrote:
  >>
   >>> "Gordon Hudson" <gordon RemoveThis @usenet.hostroute.co.uk> wrote in message
   >>> news:<buo8r0$nfn$1$8302bc10@news.demon.co.uk>...
   >>>> "Gregory Toomey" <nospam RemoveThis @bigpond.com> wrote in message
   >>>> news:bunu5j$hgaka$1@ID-202028.news.uni-berlin.de...
   >>>>> This is a "what if" question for the Lilnux gurus.
   >>>>>
   >>>>> If I build my own server & place it in the local colo, do I have
   >>>>> to set up the IP address beforehand? And what happens if the IP
   >>>>> changes.
   >>>>>
   >>>>> Presumably you will want to set up the server so that you cant be
   >>>>> "locked out" if you make a mistake with IP addresses.
   >>>>
   >>>> Normally what happens is you give them the root IP and they add the
   >>>> IP
   >>>
   >>> Define "normally" - that's nothing like the experiences I have of the
   >>> colocations we use and have used.
   >>>
   >>> How it works for me, is I tell them how many IPs I want now, and how
   >>> many I think I'll possibly need - they provide the block of IPs, the
   >>> subet, gateway etc, and I program them into the box while at the
   >>> data-center. I check the server is visible from from their network,
   >>> and from outside of their network BEFORE I leave the data-center.
   >>>
   >>> We have a few hundred IPs at the moment, and will be getting two
   >>> class-Cs of our own shortly.
   >>>
   >>> We sell a lot of dedicated IP hosting accounts - host a lof of stores
   >>> with their own SSL certs, and chew through a lot of IPs in fact,
   >>> we're the biggest user of IPs in the data-center - more than the
   >>> data-center themselves. Is this a problem for them? No... they
   >>> just check once a quarter that we're using the IPs we are given, and
   >>> they are fine when I call and ask for another block of 16 or so.
   >>>
   >>> So in summary, the experience may vary from data-center to
   >>> data-center, so to the OP - ask the data-center. Try to explain how
   >>> the box will be setup - are you going to use dedicated IPs for
   >>> clients
   >>> - offer SSL certs for clients etc, or are you doing everything
   >>> "virtually", your IP usage will probably be light.
   >>>
   >>> hth
   >>>
<font color=brown>   >>> Greg Hewitt-Long - <a style='text-decoration: underline;' href="http://webyourbusiness.com/</font" target="_blank">http://webyourbusiness.com/</font</a>>
  >>
  >> That's how I thought it would work. Checking it out at the data
  >> centre is the way to go. If you do colo it really must be in the
  >> local area because there are plenty of things that can go wrong.
  >>
  >> I raied this becuse I've seen people sending machines across the
  >> country for colocation so they MUST get the IPs right, and idiots
  >> changing their machine's IP and not being able to access it.
  >>
  >> So my ultimate colo wish list is
  >> 1. be able to do a remote reboot
  >> 2. be able to remote BIOS ( I think some expensive motherboards have
  >> this - supermicro?)
  >> 3. be able to watch the boot log if the system fails to boot (perhaps
  >> thru a remote serial port)
  >> 4. be able to ssh no matter what (eg IP stuffup)
 >
 > This any good for you? I believe other manufacturers have similar
 > options.
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://h18004.www1.hp.com/products/servers/management/remote-lightsout</font" target="_blank">http://h18004.www1.hp.com/products/servers/management/remote-lightsout</font</a>>
description.html

Looks great but what's the cost??? HP/Compaq servers seem more price
competitive these days.

gtoomey<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Colocation & IP addresses