RackloomDocs
Open the app →
Docs/Guide/Device Configuration

Device Configuration

Configure a device across its property tabs.

Relevant for:Professional ServicesEnterprise / NetOps

Select any device on the canvas to open its properties panel. Configuration is organized into tabs, in the same order on every device (and on Site Areas), so a setting always lives where you expect it.

The tabs#

A standard switch or router carries these, left to right. Config is deliberately last: it is the output of everything before it.

GeneralIdentity: hostname, name abbreviation, model, serial/asset, rack & location, site membership.
MgmtThe management plane: DNS, AAA (TACACS+/RADIUS), password policy, NTP, console/VTY lines, CDP/LLDP, local users.
InterfacesPhysical port settings: speed, duplex, MTU, negotiation, load-interval, ACL/flow/QoS bindings, storm control, port security, CDP/LLDP per port.
L2VLANs, spanning tree, port-channels, switchports, SVIs.
L3Routed interfaces, VRFs, OSPF/EIGRP/BGP, static routes with IP SLA tracking, loopbacks, and FHRP on SVIs or sub-interfaces.
FeaturesNamed objects: ACLs, prefix-lists, route-maps, QoS policies, NetFlow monitors.
MonitoringSNMP (v2c/v3), Syslog, and SPAN/port-mirroring sessions.
TemplateBind an organization config template as the device baseline.
AdvancedLogin banner and raw additional CLI.
ConfigThe generated configuration for this device, rendered on open — copy it or download it without leaving the panel.

How a tab set is chosen#

The set follows the device, so what you see is what that platform can actually render:

  • Firewalls swap L2 and Features for a Firewall tab: General · Mgmt · Interfaces · L3 · Firewall · Monitoring · Template · Advanced · Config.
  • Azure resources show General · Azure · Advanced — they deploy as Terraform, so there is no device config to render.
  • Attached endpoints (servers, load balancers, end-user networks) show General · Interfaces · Advanced. They are drawn for context and generate no config, so a management plane typed onto one would render nowhere. Interfaces stays, because their NICs are real and the cable plan depends on them.
  • Routers have no SVI section — an SVI on a router was accepted, saved, and then silently dropped at generation, so first-hop redundancy now lives on sub-interfaces instead. An access switch that needs to route can opt in from its L3 tab.
Note
Anything a platform cannot render is omitted from its generated config and flagged by validation rather than silently invented.

Inheritance#

Fields left blank fall back to inherited values— from the device's Site Area, then project-wide defaults — shown as placeholder text with an “inherited” hint. Type a value to override for that device only.