LantronixAutonomous Out-of-Band

Resources

Frequently asked questions

What is Lantronix Autonomous Out-of-Band?

Autonomous Out-of-Band (AOOB) is out-of-band management that does the predictable work itself. Most OOB work repeats. A new site needs the same firmware and the same baseline configuration as the last fifty, and when the answer is already known, nobody should have to type it in again. So the system applies it, and your team sets the policy once and gets back to the network that runs the business. Today that means an SLC 9000 calls home to the Lantronix Percepxion platform the first time it powers on, picks up its firmware and configuration, and joins the fleet with nobody on site configuring it. From there, Percepxion runs firmware, configuration and backups across the whole fleet, and it connects to the automation you already use. Out-of-band should take work off your team, not add another fleet of boxes to babysit.

How does zero-touch provisioning work?

When a new SLC 9000 powers on, it calls home to Percepxion over an encrypted, outbound-only TLS connection on the standard HTTPS port, so there are no inbound firewall rules to open at the site. Percepxion Smart Groups match the unit to the firmware and configuration policy you've set for that group and apply it. The site comes up without anyone configuring the unit by hand, and every new unit in the group starts from the same build.

What configurations are available for the SLC 9000?

The SLC 9000 comes in 16, 32 and 48 serial port models, in RJ45, USB or a mix of both, plus models with up to 32 ports of integrated 1GbE Ethernet switching. Every model has two 1GbE and two 1/10G SFP+ uplinks with failover, and dual AC or dual DC power. Ports are fixed at the factory, so you order the configuration the rack needs.

Is a cellular option available?

Yes. The SLC 9000 adds 5G through the NTC-500 cellular kit, the NTC-501-SLC9 in North America and the NTC-502-SLC9 in EMEA and APAC. The SLC 9000 powers the cellular router and manages it, so it works as part of the appliance rather than a second box to look after. And because the router sits outside the chassis, you can mount it at the top of the rack with short antenna leads instead of running long antenna cables that cost signal.

What security is built into the SLC 9000?

The SLC 9000 is built so the management network isn't the weak spot. Every unit verifies its firmware at boot, carries a discrete TPM 2.0 chip, exposes no shell, and ships with its own unique default credentials that are changed at setup. Logins go through the RADIUS, TACACS+ or LDAP you already run, with Duo MFA through a RADIUS proxy.

What access control does Percepxion support?

Percepxion works with the identity system you already have. Sign in with SAML 2.0 single sign-on through Okta, Azure AD or any SAML 2.0 provider, or with RADIUS and TACACS+ group mapping, with MFA. Role-based access sets what each person can do, and the audit log records management actions against the named user, so changes trace back to a person.

How do I reach a managed device's serial console?

Two ways. From Percepxion, open the console in your browser, with no VPN and no need to know the SLC 9000's IP address. Or SSH straight to the port on the SLC 9000 at TCP 3000 plus the port number, so port 12 is TCP 3012.

Which devices can the SLC 9000 automate?

Console access works with any device that has a serial console, from any vendor. For Cisco IOS and IOS-XE devices, the SLC 9000 goes further and automates the work itself, pulling and pushing configurations, running health checks and taking interface actions.

What can I automate with APIs and tools?

AOOB is built to plug into the automation you already run. The SLC 9000 and Percepxion each have a REST API described in OpenAPI, so your tools can generate clients instead of hand-coding calls, and Percepxion's event log can be queried through it. The lantronix.oob Ansible collection is certified on Red Hat Automation Hub, so the same playbooks that build your network can onboard SLC 9000s, roll out firmware and configuration, manage users and pull audit logs. Two MCP servers, one for Percepxion and one for the SLC 9000, let an AI assistant work with the fleet in plain language, for example to find the units running old firmware, pull a device's configuration or check who did what in the audit log.

Does the SLC 9000 log console output?

Yes. It captures device console output in real time and sends it where you want it, to local storage, NFS, syslog or a USB drive, so the record of what a device printed is there when you need it.

What is the lifecycle of the SLC 8000?

The SLC 8000 reaches end of sale on December 31, 2026 and end of life on December 31, 2031. New deployments should plan on the SLC 9000.

These answers are checked against the generally available releases listed on About this site. For ordering, pricing and support, go to lantronix.com.