Every NVIDIA GB300 NVL72 Rack Has 18 Consoles Most Builds Never Cable

The rack, console by console

The console count is the same for DGX and ODM builds. The difference is BlueField-3 data processing units: DGX builds have two per compute tray and ODM builds have one. That changes the Ethernet port count (89 OOB ports on DGX, 71 on ODM), and those BMC and management ports stay on the rack’s two 48-port OOB switches. The SLC sits beside those switches and takes their consoles too.

The SLC9016-32U pairs 16 RJ45 serial ports with 32 USB serial ports. In the DGX GB300 build, that covers all 11 RJ45 and 18 USB consoles in the rack. The SLC 9000s are available with dual AC or dual DC. Multiple uplinks provide a variety of connection options: 2 x RJ45 and 2 x SFP+, with failover.

SLC9016-32U: 16 RJ45 Serial Ports & 32 USB Serial Ports

Burn-in becomes a record

Every SLC port can log its full console stream: device output plus the echoed commands. Logs go to syslog, NFS, a USB drive, or a local buffer, in any combination. Sent to syslog, each line arrives timestamped and tagged with its port name.

For an integrator, that means:

• A boot log for every compute tray, captured during burn-in and stored with the rack’s serial number
• Failures the BMC doesn’t see, like early-boot and firmware-stage errors on the Grace CPU, captured as they happen
• A QA packet that ships with the rack, so the operator receiving it knows what passed and when

Catching a bad tray on your build floor costs a lot less than catching it on the customer’s.

Hand over a rack, not a project

The integrator builds it and the neocloud runs it for five years. The SLC works for both, because it doesn’t need anything new from either.

• REST API documented with OpenAPI 3.1. Port names, logging targets and users are all scriptable.
• The Red Hat certified OOB Ansible collection, on Automation Hub.
• Zero-touch provisioning, so the same configuration lands on rack 1 and rack 500.
• Standalone operation. Percepxion fleet management is optional, for operators who want one view across sites and standardize workflows.

Name the ports on the integration floor, and the operator inherits a rack where port 23 is already labeled “compute-tray-07”.

Access your security team will sign off on

Console access authenticates against your existing LDAP, RADIUS or TACACS+ directory, with Duo two-factor support. The SLC 9000 has a TPM 2.0 hardware root of trust. The serial path has no IP adjacency to the compute or NVLink fabrics it manages. Port logs go to your syslog, so they land in your SIEM.

And once the rack is in production, those same 29 consoles stay reachable over the out-of-band path when a node stops answering on the fabric.

Not building on GB300? The same pattern fits any rack that mixes RJ45 and USB consoles: count them, map them, and likely be able to put them on one 1U.

Let’s figure out the port map for your build

We’re happy to talk through your build and what configuration of the SLC 9000 makes the most sense. Talk to a Lantronix engineer

FAQ

Does the SLC 9000 replace the OOB switches in a GB300 rack? No. The SLC9016-32U works alongside them. The BMCs, BlueField-3 BMCs and power shelves stay on the OOB switches, and the SLC takes every console, including the consoles of the OOB switches themselves.

How do the compute tray consoles connect? Through a Micro-USB to USB-A cable, from the tray’s console port to one of the SLC9016-32U’s 32 USB serial ports. Ask us to confirm compatibility with your tray model.

Does it need Percepxion? No. The SLC 9000 runs standalone. Percepxion is optional fleet management.

How is it automated? Through the REST API (OpenAPI 3.1) and the Red Hat certified lantronix.oob Ansible collection.

Where do console logs go? To any mix of syslog, NFS, USB storage, or a local buffer, configured per port.

NVIDIA, DGX, GB300, NVLink, BlueField and Grace are trademarks of NVIDIA Corporation. Lantronix is not affiliated with or endorsed by NVIDIA. Rack layouts are illustrative. Verify port counts against your build.