Server configuration

Every setting of a server in one place: open the server and the Configuration tab. The layout follows TenantOS: Main details and Assigned connections on top, below one card per connection (IPMI device, DHCP assignment, PXE installation, SNMP switch, PDU, power usage measurement). Each card has Update (lights up when something changed) and, except Main details and the IPMI device, a red Delete that removes that connection (clears the PXE MAC, unmaps the switch port or the PDU outlets, resets the PXE settings). A deleted card comes back through Add connection, which only offers what the server does not have yet and what exists at its datacenter (PDU only with a PDU there, PoE only on a PoE switch port). Customers see the main details and, when you share it, their BMC access; everything else is for admins.

Above the tabs the server page shows badges for CPU (model, cores, clock), memory, storage and the port speed, and the Power and Console menus next to QR label: Power has the actions the server’s power connection supports (with the usual confirmation, protected-server and maintenance rules), Console opens the KVM, the serial console or the BMC web interface (admins, and customers with an account of their own) in its own window. Consoles switched off in the IPMI device’s Features are not offered. The status next to the hostname is the BMC’s power state.

The (i) icons next to the settings explain them; hover, focus them with the keyboard, or tap them on a phone.

Execute IPMI command

The terminal icon of the IPMI device card opens the command dialog (admins, IPMI devices only): read-only commands (power and chassis status, last 20 events, sensors, FRU inventory, BMC info / GUID / self test, sessions, user list, LAN print) run directly; power actions, boot device overrides (PXE, disk, CD-ROM, BIOS, safe, diagnostic) and the identify LED (marked with a lightning icon) run as a job: protected servers, maintenance, dry-run and the audit log apply, no typed hostname is needed. A command typed by hand is accepted only when it is one of these — no options (the connection comes from the IPMI device), no shell characters; anything that changes BMC users, network or channel settings is refused. The users icon next to it holds the client IPMI account and whether the customer may see it.

Main details

Server name, hostname, installed OS, the assigned client (owner) and tags. TrixOS manages dedicated servers; older entries imported as virtual or external show their type here, read-only. Under the card: Delete server, Manage suspensions and Start maintenance (or edit / end it; see Servers & BMC).

Assigned connections

Which connection does what for this server:

Setting	Choices	Effect
Power management	BMC, PDU outlets, PoE switch port, none	Power on / off / reset / cycle go over the BMC, cut and restore power at all PDU outlets mapped to the server (dual power supplies switch together), or switch PoE on the server’s switch port. None refuses power actions and PXE jobs. PDU and PoE cannot do a soft (ACPI) shutdown.
Reinstallation provider	PXE, none	None refuses reinstall, rescue, the PXE inventory scan, disk wipe and password reset.
Remote console	BMC, none	None refuses the KVM and serial console.

PXE jobs restart the server through the same power management. The boot override (PXE once, then disk) always needs the BMC; a server powered through its PDU or PoE without a BMC has to try network boot first in its boot order.

IPMI device

Status of the BMC (OK, error with the last message, credentials missing), the datacenter whose agent carries BMC, DHCP and PXE traffic (Via agent, required: a datacenter without an agent means the panel talks to the BMC directly), address, port, username and password. The password is stored encrypted; the eye button shows it in plain text (admins only, every read is written to the audit log as bmc.password.reveal).

• ipmitool flags: extra options for ipmitool, from an allow-list only: -I lan|lanplus, -C cipher suite (0–17), -L privilege level, -R retries, -N timeout, -o OEM type, -b -t -B -T -m for bridged BMCs (blade chassis). Anything else is refused. Example for an old BMC: -C 3 -L OPERATOR.

• Install power action: how PXE jobs restart the server: power cycle (default), reset, or power off and on.

• Web BMC provider: the login automation of the browser console (HPE iLO, Dell iDRAC, Supermicro, Lenovo XCC); automatic goes by the vendor and otherwise detects it from the login page.

• Fake date: Java consoles of old BMCs refuse to start once their code-signing certificate expired. With a date set, the KVM viewer runs Java at that date (libfaketime). Rebuild the viewer image after updating: docker compose --profile tools build kvm-viewer.

• KVM console: Auto (the BMC’s HTML5 console), HTML5 or Java (the BMC’s Java console is fetched after the login and started; closing it ends the session).

• Java version: Java for the BMC’s Java console: Auto (Java 8), 8, 11 or 17.

• Console web browser: Chromium, or Chromium + legacy TLS for BMCs that only speak TLS 1.0 / 1.1.

• Console account for users: the BMC account customers’ consoles log in with: the stored account (default), a temporary BMC user per session (created with the web user privilege, deleted when the session ends; IPMI only, not on protected servers, live mode only) or the client account. With either of the last two, customers also get the BMC web interface.

• Web user privilege: IPMI privilege of temporary BMC users: User, Operator (default), Administrator.

• Login details in console: who may see the session’s BMC login in the console window: hidden, admins (default), admins and customers (never the stored account for customers).

  Details: Remote console. The KVM settings (KVM console, Java, fake date, browser) only show while the noVNC console is on.

• Features (at the bottom of the card):

  Feature	Off means
  Power usage	No power data from the BMC power sensor (metered PDU outlets keep measuring).
  Web console	Nobody can open the BMC web interface of this server, admins included.
  noVNC console	No KVM console.
  Serial console (SOL)	No serial console. With neither noVNC nor serial the remote console is off (Assigned connections).

  The Console menu only offers what is on; the API refuses the rest.

• Client IPMI account and Show IPMI credentials: create a BMC user for the customer on the BMC (operator rights are usually enough), enter it here and switch on Show IPMI credentials: the customer then sees address, user and password under Configuration → IPMI access. The admin account is never shown; every read is logged.

DHCP assignment and PXE installation

The MAC address of the NIC the server PXE-boots from (TrixOS answers DHCP only for that MAC and only while a PXE job runs) and the boot mode (automatic, legacy BIOS, UEFI; see OS installs). The iPXE binaries are always automatic (undionly.kkpxe for BIOS, ipxe.efi for UEFI). A server that still has an override from an older version (undionly.kpxe, snponly.efi) shows it with Reset to auto; the API (PATCH /servers/{id}, ipxeBiosFile / ipxeEfiFile) can still set one for a NIC whose iPXE driver fails.

SNMP switch

The switch ports mapped to the server (bandwidth graphs, port admin). Per port: an optional name, the PoE port id (<group>.<port> as in POWER-ETHERNET-MIB, e.g. 1.12) and the PoE status and control method (SNMP). With control method SNMP, Power management → PoE switch port switches PoE for power actions; Read PoE shows whether the port delivers power.

Power usage measurement

Source of the power graph and the kWh on the server overview (Advanced): automatic (the mapped PDU outlets when they are metered, otherwise the BMC power sensor), PDU outlets only, BMC sensor only, or off. The section lists the server’s PDU outlets; map outlets under Network → PDUs.