All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
IPMI is dead and GetDedi.com refuse to fix it
I ordered a dedicated server on GetDedi.com before. But since I assigned the IPMI IP address to a network interface, I am no longer able to access IPMI.
When I ask the support to reboot my server to BIOS (so that I can mount an ISO and reinstall the OS myself), they asked me to pay for $37.5 before they will help.
Is there any alternative that I could try to fix it myself? In my case, is it a "must" to pay them $37.5?
My god! US$37.5 is enough for me to purchase other dedicated servers in other providers. Even the whole server is just $54/month. Why the hel1 do I have to pay a lot to restart the server? Maybe $5, $10 is fine, but they are greedy enough. Even I asked them to lower the price a bit, they said $37.5 to perform a reboot is already much cheaper than other providers/companies.
Really, that's a very bad experience. They got an attitude when I asked them to lower the price.
Comments
Dont assign the IPMI to the adaptor in future and pay the remote hands fee since you borked it instead of calling them out on LET.
Well, you assigned the IPMI IP to a network interface, why should they do free work when you screw up?
They give you IPMI so that you can reboot and/or reinstall OS etc if you screw up. I find it reasonable that they charge you for this as it is a self managed server.
If you had not messed with the IPMI IP, you could have rebooted the server as much as you wanted, for free. Even to BIOS.
I know, but....is it reasonable to pay $37.5 for a single reboot?
Its not a reboot its a half hour remote hands fee no?
I doubt that is for a single reboot. It should include the reconfiguring the IPMI interface, too. Are you sure?
I didn't ask for free, did I? I'm asking for a more reasonable price. I think an acceptable range should be $10~15. That's OK, I'd have paid it.
$37.5 is just too much.
No, I'm asking them to reboot. No other things to do. JUST REBOOT: $37.5.
Fun enough.
You sure?
As the price you quoted sounds like a remote hands fee which includes a reboot and fix for/to IPMI.
They don't own their own datacenter with their in-house staff. So they have to pay for remote hand fees. And most datacenters charge $125/hour with 15 min intervals. So that price is fair.
Just reboot. I didn't even ask them to fix the IPMI. They insist to charge me $37.5.
Remember, just reboot to BIOS. There's nothing more to do.
As @serverian said they do not own the DC, so doing a manual hands on reset will cost them a remote hands fee.
@peter08po what box did you get for $54?
So you are telling me that GetDedi.com is only a middleman.
They are providing false information on their webpage. My server is located in Dallas.
They own their network and their cabinets and their hardware. They don't own the datacenter space. There are very few companies who actually own the datacenter space. Even the bigger companies just rent space. They are not a middle man. They are not a reseller.
It was an offer that their admin sent me via private message.
Nice, paid the remote hands and got IPMI online yet?
Did not pay.
Have been negotiating with their support for 2 days.
No hope.
(Though the offer was really a great one.)
So is the server dead / not responding? Can you ssh in and remove that IP from the network interface?
SSH is inaccessible as well.
rds to the rescue!
It's not just a reboot. The full details was nicely explained in the ticket. A single reboot won't fix the described issue, since the OP has explained that the IPMI IP has been assigned to something else.
We provided a workaround free of charge as a courtesy the first time. I'm not sure how it's unfair. Please don't create drama out of it.
It shouldn't matter if someone owns the DC or not. The fee still has to be paid. Onsite staff still needs to be fed lol.
Sorry? That's just 15 mins of remote hands fee. Equinix, Internap and like charges something like $300/hour paid in 30mins or even hourly for any work.
To be clear: we're not refusing to fix it. We offered solutions and you can confirm with the OP. The server is self-managed and we've made it clear in a welcome email to please leave the IPMI IP alone (something most users should be aware of).
Think everyone here knows what went down concerto49...
Who's creating drama? You!
On about 11:19 PM you told me you can offer 1st help for free. I replied "Yes" on 11:56 PM. I've been waiting in front of the computer till 1:00 AM. No response.
The next day when I woke up, I saw you sent me a message on 2:51 AM, telling me you have shut down IPMI port for 40 minutes and ask me to quickly finish within that period.
Would you expect a person to stay in front of the computer for a whole night just to wait for the support replies? No, and you think this is fair. You think I'm creating drama but you have admitted what you have said in the ticket.
Correct, this was courtesy extended towards you since this was the first time -- one you appear to not appreciate.
What time it might be at your place is up to you to consider, there's no way for us to 'be considerate' of this since someone's midnight is someone else's morning, and vice versa.
You failed to get it done within the first, freely offered period (Something we're under no obligation to even offer, but did solely as a courtesy) -- secondary attempts are no longer free, as explained to you. I don't assume there's a need to 'explain' why this might be the case.
Either way, your options have been outlined to you -- it's up to you now.
Why in the world would you allow an OOB network IP to be bound to any servers at all. The OOB IP block should be on a completely separate network with it's own switches and IP Blocks, if the inverse is the case then they seem to have a much bigger issues. The IPMI network is a last resort and should be always online and it should be the hosts prerogative to keep it online. While I'm not saying customer is not completely free from fault (he bound is OOB IP to a NIC), there should be systems in place to ensure this doesn't happen as IPMI is kind of important in these situations.
Yup, it is a courtesy to ask somebody wake up in 3 AM to fix the problem....
It is a courtesy to suddenly shut off the IPMI port without prior notice, provided that the user have been waiting 2 hrs in the midnight.
Whine
You're welcome to come up with some, if you so wish.
That is, implement binding of a single IP from a block (of a specific vlan) onto a specific mac address and nothing else. The only way to do this on JunOS is creating extensive firewall rules for every single RVI subinterface, and applying them; maintenance will of course be a huge pita.
Even then, you don't 'block' anything, you'd simply be dropping traffic where the mac doesn't match.
This however, is not something a L3 aggregator should be having to waste CPU cycles on. Inline firewalling is usually not the forte here.
If your solution is actually elegant (which I know it won't be), I'm more than open to suggestions. Please also do not recommend two separate vlans per box, that is also impractical.
VPNing and using a completely separate range do not fall under this, and we may implement that later down the road.
Unrelated, it was a problem you caused; I don't think there's a need for us to expand further here.
This will be our last reply on this topic, because there's pretty much nothing to do but go around in circles.
@peter08po - this is because they need to pay their datacentre provider for remote hands, so they are just passing it on to you. As others have said here, these datacentres will charge anywhere between $150-300/hour depending on the site and time of day.
Its always good to find out upfront whether a dedicated server provider will charge should you need hardware assistance as in this case. Some won't charge you a penny, others will milk you dry. I am not sure who's rackspace they rent in Dallas and LA but I'd say there is little to no profit in $37.50
Circles can be fun, on a skid pan.