PDA

View Full Version : startup


princee18
06-20-2008, 04:39 AM
i am looking for information on how to organize a colo startup if I manage to get a cage with 2-3 cabinets in a Peer1 datacentre.

From my knowledge, Peer1 handles firewalling, BGP, etc on their end so I probably won't need it.

But how can I organize it, what do you guys do when you get a new client?
Have cables readily dangling in the racks or something so you can connect it to the clients right away?
What kind of reboot privs do you give out?

JaguarpcNick
07-28-2008, 01:36 PM
i am looking for information on how to organize a colo startup if I manage to get a cage with 2-3 cabinets in a Peer1 datacentre.

From my knowledge, Peer1 handles firewalling, BGP, etc on their end so I probably won't need it.

But how can I organize it, what do you guys do when you get a new client?
Have cables readily dangling in the racks or something so you can connect it to the clients right away?
What kind of reboot privs do you give out?

You could leave wires dangling and use apc remote reboot for reboot privileges, but Id suggest if its not your DC to check with the owning company you may have to be onsite for hardware installs, and to get your new clients access.

linkline_5
08-07-2008, 06:16 PM
This may not be the first piece to your startup puzzle, but I'd feel remiss if I didn't attempt to steer you toward solidifying your business' typical Service Level Agreement. The majority of problems may arrise from miscommunications or implications about what you're are/aren't providing for the client. Having a clearly deliniated set of procedures and services will go a long way in guiding customer expectations (not to mention lowering your average frustration level as well).

As always, your SLA should resound your provider's procedures and policies.
If you take a look at MCI's COLO SLA, it's a pretty good starter (http://global.mci.com/ca/customer/sla/colocation.xml?SetLang=en).

Also, a quick example I cribbed from the Web and sanitized:

Network Quality

Internet Connectivity
XXXXXXX's Availability Guarantee ensures Internet connectivity is provided to XXXXXXX customers 100% of the time and, as set forth below; XXXXXXX will credit Customer's account if XXXXXXX fails to meet this Network Uptime Guarantee during any given calendar month. At Customer's request, XXXXXXX will calculate Customer's "Network Unavailability" in a calendar month. "Network Unavailability" consists of the number of minutes that the XXXXXXX Network was not available to the customer, but will not include unavailability which Customer fails to report to XXXXXXX within five days, or any unavailability resulting from

(a) Scheduled XXXXXXX Network Maintenance,
(b) any Customer owned/maintained circuits or equipment failure,
(c) Customer's applications or equipment,
(d) acts or omissions of Customer
(e) any use or user of the service authorized by Customer or
(f) reasons of Force Majeure.

For each cumulative one half hour (30 minutes) of Network Unavailability or fraction thereof in any calendar month, Customer's account shall be credited for the pro-rated charges for one day of the XXXXXXX's Monthly Fee, up to but not exceeding the monthly hosting fee. This does not include additional charges such as bandwidth overages.

Customer Equipment Monitoring

Reporting and Notification
XXXXXXX's Reporting and Notification guarantee is to notify Customers within 1 hour after XXXXXXX's determination that Customer's service is unavailable. XXXXXXX's standard procedure is to ping Customer's equipment housed in our data center every 300 seconds. If Customer's equipment does not respond after two consecutive 300-second ping cycles, XXXXXXX will deem the service unavailable and will contact Customer's designated point of contact by a method elected by XXXXXXX (telephone, email, fax or pager). Customer is solely responsible for providing XXXXXXX accurate and current contact information for Customer's designated point of contact. XXXXXXX will be relieved of its obligations under this Network Uptime Guarantee if XXXXXXX's contact information for customer is out of date or inaccurate due to Customer's action or omission or if XXXXXXX's failure is due to reasons of Force Majeure.

If XXXXXXX fails to meet this Network Uptime Guarantee, at Customer's request, Customer's account shall be credited the pro-rated charges for one day of the XXXXXXX Monthly Fee for the service with respect to which this Guarantee has not been met; provided, that Customer may obtain no more than one credit per day, irrespective of how often in that day XXXXXXX failed to meet the Network Uptime Guarantee.

Technical Support Guarantee
XXXXXXX's Technical Support Guarantee is that XXXXXXX staff will be available in the event customers need to request technical support 24 hours per day, 7 days per week. XXXXXXX's technical support is only guaranteed through XXXXXXX's online support system. Customers requiring support shall complete the online form and indicate the level of urgency. If emergency support is required (server not responding) select the emergency support window. XXXXXXX guarantees that any emergency support ticket submitted to Technical Support will receive a response from XXXXXXX support staff within 2 hours of delivery.

If XXXXXXX fails to meet this Technical Support Guarantee, at Customer's request, Customer's account shall be credited the pro-rated charges for one day of the XXXXXXX Monthly Fee for the service with respect to which this Guarantee has not been met; provided, that Customer may obtain no more than one credit per day, irrespective of how often in that day XXXXXXX failed to meet the Technical Support Guarantee.

Infrastructure Quality

AC Power Availability
XXXXXXX's Power Availability Guarantee is to have AC power provided to XXXXXXX's Data Center and Customer's co-located equipment, 100% of the time and, as set forth below, XXXXXXX will credit Customer's account if XXXXXXX fails to meet this Power Availability Guarantee during any given calendar month. "Power Unavailability" consists of the number of minutes that power was not available to Customer's co-located equipment, but will not include co-location power unavailability, which Customer fails to report to XXXXXXX within five days, or any unavailability resulting from (a) any Customer circuits or equipment, (b) Customer's application or equipment, (c) acts or omissions of Customer, or any use or user of the service authorized by Customer or (d) reasons of Force Majeure. For each cumulative hour of Power Unavailability or fraction thereof in any calendar month, Customer's account shall be credit the charges for one day of the XXXXXXX Monthly fee.

Facilities Security
The data center facilities are controlled access environments. All entrance into the data center is restricted via biometric access equipment and database logged for on-demand review.

Network Infrastructure
XXXXXXX guarantees the data center facility will utilize a "dual entrance fiber facility" with a minimum of two competing fiber-optic telecommunication providers. The fiber-optic networks connected to the host management facility will enter the building in different concealed locations and leave the facility in a minimum of two diversified geographical paths with a minimum of 500ft of buried and concealed underground cable.

Limitations of Guarantee

The total credit granted to customer by any aspect of this Service Level Guarantee during any calendar month will not exceed the monthly rental or co-location fee for the same calendar month.

All guarantees will not apply if downtime or unavailability occurs during standard XXXXXXX maintenance windows, when Customer is notified at least 24-hours in advance of maintenance activities or unavailability of service guarantees. XXXXXXX will use the Customer's designated point of contact as set forth in the Reporting and Notification guarantee.

Credits or remedy will be provided only upon request of the customer. Requests for credit due to Internet Connectivity must be received within 5-days of the failure. All other requests for credit must be received within one weeks of XXXXXXX's failure to perform under the obligations outlined in this agreement.

No guarantee or remedy will be provided at any time for failures determined attributable to reasons of Force Majeure.

This SLA is subject to change at the sole discretion of XXXXXXX, without notice to Customer. The most recent revision of this document will be posted to XXXXXXX's web site at http://XXXXXXX.com/support/sla.action. All changes made to the SLA will be effective five (5) days after the first publishing date.

This SLA in no way construes XXXXXXX will guarantee performance against failures of application specific failures, such as web server software, operating system software, failing hardware, web site application features, database performance or related components. It will be at XXXXXXX's sole discretion to determine fault and identify failure to perform under the obligations of this SLA.

attagirl
10-30-2008, 05:24 PM
I have to agree, that you need to start at the beginning and it appears that you are trying to start a bit into it. I would conduct a quick search and see what you might need to start it and then go from there. There is a lot of good information on the web.