How to ship a machine for installation

Mail it to the DC


IO Cooperative, Inc, c/o Honeycomb Internet Services
77 13th Ave. NE Suite 210
Minneapolis, MN 55413

In SCL2:
We have many members near the SCL2 DC who can help. Open a ticket and we’ll arrange for you to ship it to a local Coop member. It’s also possible to ship directly to the DC, but there’s a specific procedure that needs to be followed:
Send an email to with “Delivery for IO Cooperative” in subject line.

Include in the email the contact information, equipment type, number of packages and expected
delivery date. On all of your shipments, be sure to label accurately including all of the following information:

  • The full address of the Telx facility.

    telx - Santa Clara, LLC
    Attn. Telx c/o IO Cooperative, Inc.
    2820 Northwestern Parkway Santa Clara, CA 95051

  • Print IO Cooperative on all shipments.
  • Place an “Attention” on all boxes along with e-mail (Attn. Telx c/o IO Cooperative, Inc.).
  • Clearly indicate Cage/Cabinet # (if known).
  • Specify “Inside Delivery”

When the shipment is received Telx will send an email to you which will include a ticket number
(Example: “TST 1234”), which is the number you will use to request the equipment once you or another Coop member arrives to rack it.

Helpful steps

  • Include a photo of the front and back of the machine with annotation numbers added.
  • Annotation list should include things like which NIC is which, which serial port is which but doesn’t need to be silly and include which one is the power plug. :)
  • It should include the MAC address and IP address settings for each NIC.
  • Serial port info should include “has getty @ Speed(n81)”
  • We do not have remote serial at MSP, so you will probably want to have a system that supports IPMI or some other ethernet based console.

If shipping disks non-mounted (say in a nice padded pelican case) of course you should document the correct mounting positions.

Some configuration suggestions for shipping machines

  • Having one NIC setup for DHCP is probably a good idea.
  • Setting up a dynamic dns account may also be a good idea.

Mounting rails

We still need to document what kind of hardware is required in our racks.

Last updated: 2014-05-01 11:56:12 by ops