netplex. Early Access is open. Join the list to get in first.

Set the hardware defaults a device gets on the canvas

Reference3 min readUpdated July 2026

When a device lands on the canvas, its starting settings (virtual CPUs, RAM, number of network cards and disk type) have to come from somewhere. Device Defaults is where an admin sets them for every vendor and platform on this machine. Get it right once here, and every future drag-and-drop of a Cisco vIOS or a Juniper vSRX starts with hardware that actually boots, instead of a generic guess.

1

Open System → Nodes → Device Defaults. Every known device platform is listed with its recommended vCPU, RAM, NIC count and default image - the same table the palette reads from when a device is dropped onto a lab.

Step 1: Set the hardware defaults a device gets on the canvas
2

Editing a row changes what every user gets from that point on - raise a heavy platform's RAM so it stops restarting over and over on first boot, or correct a NIC count that was wrong for a newly imported vendor image. This is a one-time admin fix that pays off on every lab built afterwards.

Step 2: Set the hardware defaults a device gets on the canvas

Device Defaults is the platform-wide fallback; a user can still override CPU/RAM per node in that node's own Inspector for a one-off lab. See "Configure node hardware" for the per-node version of this same control.