Infrastructure – Administrator Guide

The Infrastructure menu keeps a record of your own hardware and network: where it is (locations and racks), what it is (devices) and which IP addresses it uses (VLANs, subnets and addresses). It needs the role permission "Manage infrastructure". Nothing here changes a server or a router: it is the record your staff work from.

Infrastructure > Overview#

/admin/infra has count cards (devices in use or spare, faulty devices, locations and racks, addresses given out and subnets), the racks with how many units and how much power their devices use against what the rack is allowed, the fullest subnets, and devices whose warranty ends within 60 days (or has ended). A new site shows a button to add the first location.

Infrastructure > Locations and Racks#

A location is a datacentre or room: name, the datacentre company, city, country and notes (address, access hours, the support contact). Each location lists its racks as cards with a bar of units used and the power drawn. Add a rack with its location, name, height in units (1 to 60, 42 by default) and the power it is allowed in kW.

A rack's page draws the rack from the top unit down. Each device fills its units, with a coloured edge by kind (servers teal, network gear purple, storage amber, power grey; faulty devices red) and its status. Clicking an empty unit opens a new device already placed there. Devices assigned to the rack without a unit are listed beside it. A rack cannot be made shorter than its highest device, and a rack or location with something in it cannot be deleted.

Infrastructure > Devices#

The list has count cards per status (Active, Spare, Faulty, Retired) and filters by kind, status and location, and a search across name, hostname, serial number, asset tag and IP addresses. Retired devices are hidden unless asked for.

A device has:

Field	What it does
Kind	Server, switch, router, firewall, storage, power (PDU) or other.
Name, hostname, status	Status is Active, Spare, Faulty or Retired.
Management IP	The IPMI, iDRAC or iLO address.
Make and model, serial number, asset tag, CPU, RAM, disks	The hardware.
Rack, lowest unit, height, power	Where it sits. Two devices cannot share a unit, and a device must fit inside the rack. A device in a rack takes the rack's location.
Location	For a device that is not in a rack.
Runs the server	The server under Settings > Servers that lives on this hardware.
Client service number	For a dedicated server rented to a client; the service's page in the admin area links back.
Bought on, warranty until, cost, notes	Warranty dates feed the overview.

A saved device lists its IP addresses and can be given one from any subnet (the next free one, or a chosen address). Deleting a device frees the addresses that belonged only to it.

Infrastructure > IP Addresses#

Subnets are listed with their gateway, location, VLAN and a bar of how many usable addresses are given out. Add a subnet as an address and prefix (IPv4 /8 to /32, IPv6 /16 to /128); it is saved as its network address (192.0.2.77/24 becomes 192.0.2.0/24). Subnets of the same family may not overlap, and the gateway must be inside. VLANs (1 to 4094, unique per location) have a name, location and notes.

A subnet's page has cards for addresses given out, free addresses, the next free address and the gateway. An IPv4 subnet of up to 4,096 addresses lists every address, marking the network, broadcast and gateway (free ones can be hidden); larger subnets and IPv6 list what is given out. Give out an address to a device and/or a client service, as Used or Reserved, with reverse DNS and a note. Left empty, the address is the next free one, skipping the gateway (and, in IPv4 subnets of /30 and larger, the network and broadcast addresses). With "Make it the service's dedicated IP when it has none" ticked, the address also becomes the service's dedicated IP. Each address can be edited or freed. A subnet with addresses given out cannot be deleted or shrunk past them.

The admin page of a service shows its devices and addresses under Infrastructure.

Infrastructure > IP Transit#

The upstream links of each location: IP transit bought from a carrier, private peering, a port on an exchange point (IX) or a private link. Each link has a provider, its kind and status (Active, Planned, Ended), the location, the device of yours it ends on, the other side's AS number (written as AS64500), the port speed and the committed rate in Mbps, the circuit ID, the monthly cost and the price of each Mbps above the commit (for 95th-percentile billing) in the default currency, the contract end date, both addresses on the link and notes. The committed rate cannot be more than the port speed.

The page shows the port capacity and committed rate of the active links, what they cost a month and the cost of each committed Mbps, overall and by location, and warns about contracts ending within 60 days (the Overview shows the same). Ended links are hidden unless "Show ended links" is ticked.

Infrastructure > VPS Fleet#

Every service of a product of the type "VPS or server", listed with the node (Settings > Servers) it runs on. The top cards count the running and suspended services and nodes, what they bring in a month and what is left after the nodes' own monthly costs (the "Monthly cost" of each server). Amounts of clients paying in another currency are turned into the default currency with its exchange rate, and a year's price counts as a twelfth a month.

The Nodes table has, for each node: its address, the device and location it is in the inventory (a device whose "CoreInto server" is that node), how many services it holds against its "Maximum accounts", the monthly income, the node's cost and the difference. Services without a node are grouped as "Not on a node". Below, the services can be searched by hostname, IP address, client, username or service number, and filtered by node, product and status (active and suspended by default), each with its client, IP addresses, disk and traffic use, monthly amount, next due date and status.