All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Colocation and Network Equipment
juniorrrrr
Member
Hello everyone,
I’m starting my journey with colocation and currently have 3 servers. I pay unitary colocation fee for each server, which means they are spread across different racks in the data center. Additionally, I pay a small monthly fee for the IP announcements handled by the data center.
Recently, I decided to allocate a new /24 block for new servers and, to ensure greater traffic security, I requested a separate VLAN for these new servers. However, the data center informed me that to implement this VLAN, I would need to provide my own switch and router to the data center.
My question is: Is this a common practice in the colocation industry, even for those who have only 3 or 4 servers? Is it normal for providers to require clients to supply their own networking equipment in such scenarios?
Comments
Sounds normal to me. They don't want to get into becoming your network engineer.
Depending how much they care for the customers or if their infra allows it.
Not all routers know to handle vlan transport properly or it's just too much of a hassle to re-map vlan IDs and it's much simpler to have the customer bring their own switch. So, it depends on if they use routers or switches for the core.
So, a really caring provider would probably help you free of charge with this. A "fuck-you-we-only-need-your-money" DC like M247, would give you the answer you already received.
This really depends on the provider itself. I know we have done this for customers assigning things to their own vlan and all of their servers.
However, there are also times when a customers requirements need their own switch typically this is when you do more like 1/4 or half a rack of colo you should have your own switch.
3-4 servers is a bit strange. But having systems in different racks can complicate things depending on how that companies network is configured.
There is very little profit in a lot of colocation unless you own the data center itself or don't charge super low prices. So it's possible the company is on the not worth our time get your own switch type of deal.
Hard to really say without being the provider.
happy to help with this, if you ever feel like changing providers.
Personally i think they probably misunderstood what you asked. Did you ask them for an extra network drop/cable per server for private networking? because it sounds to me, like they understood that you wanted to go bring your own router.
They understood correctly. Currently, I have three servers, with the third server being installed just yesterday. I requested the announcement of a new /24 IP block and a separate VLAN distinct from the other two servers. This VLAN would be for server number 3 only, and soon server number 4.
Do your servers have two drops? Public and private on separate physical cables?
Why do you need/want this? What is the goal?
Is the cost the same per U? Or does your per-U cost go down as you increase the quantity? Maybe setup a separate account for the 3rd and 4th server, that way they can/will provide the same configuration as servers 1 and 2?
It isn't uncommon to be asked to provide your own switch and router.
The server uses 2x SFP+ connections linked to the switch, and the IP announcements are delivered via the VLAN.
Server 3 is intended for another end user, and they should not have access to the /24 block previously announced on the VLAN.
Approximately $70–$80 per server, depending on the configuration. Placing this server in another account is an option, but it wasn't discussed beforehand because the sales team mentioned that it would be possible to configure it the way I need.
Even with few servers and paying per U unit?
Yes, but all depends on the provider.
Being you mentioned that all boxes are in different racks makes things a tad tricky.
Myself if all boxes were in the same rack I would say get your own switch. (however they aint that expensive if know what to look for)
Every setup is different so hard to say exactly what is right or wrong in this case.
Then have fun figuring out how to configure the switch.
10~160 hours, depending on your IQ.
Why two?
Delivered via the VLAN? So you need to setup tagging in the server software?
Unless they have some black-hat traits, you could set them on the same VLAN and they would never notice.. Give them the IPs and gateway for the /24 they are allowed to use..
While you figure out how to get a separate network for them.
Keep it simple for them.. Do that. After it is configured, maybe murge the accounts back together specifying no network changes.
If each server was 2U, 4 servers would be approaching 1/4 rack, so yes.
But if you supply your own switch and router, will they be giving you cross-connects from the various locations in the datacentre where your servers are actually installed back to your router and switch?
Not common if you're renting by the U. The provider probably doesn't have the ability to extend your VLAN across the racks and will need to move you to a single cabinet. They probably want you to provide your own switch or router to keep the config simple and consistent on their side.
What you talking about...
At least the RPi Zero has an actual LAN cable connected to it and it not only only wifi.
Link Aggregation Group, required by the data center. I had to add network cards compatible with SFP+ on all servers.
"Delivered via the VLAN" — Sorry if I used the wrong term, networking isn't my area, but they are announcing the /24 and making it available to all servers on the same VLAN
Yes, I did that and I'm hoping that the "server 3 user" won't try to exploit the network.
I only have 3 x 1U servers, so currently I am using 3U.
I have no idea how that would be configured. I do not have access to the data center; only they have access to install and manage the equipment.
But by providing my own router and switch, would they need to keep my servers grouped in the same rack? However, I don't currently have a full rack; I'm only using 3U.
Switches are configured remotely via NETCONF or RESTCONF protocol.
You don't need physical access to configure the switch.
What happens if you are unsuccessful within the 160 hour time limit?
The customer would have asked for a refund, if you cannot get their service online after four weeks.