For Network Engineers

Details

What changes when the SLC 8000 refresh lands on your desk?

You pick port count and port type up front, and Percepxion handles most of what comes after. The SLC 8000 reaches end of sale on December 31, 2026, with end of life on December 31, 2031, so refresh plans for racks and branches are getting written now.

The SLC 9000 ships in 16, 24, 32 and 48 serial port configurations, in RJ45 or USB serial, with Ethernet switch-port options up to 32 ports. Every unit is 1RU with dual power supplies, two 1GbE uplinks and two 1/10G SFP+ uplinks with failover. One planning difference matters more than the rest. The SLC 8000 is modular and field-configurable. The SLC 9000 is factory-fit. So count the consoles in each rack, leave headroom, and choose the configuration at order time.

How do new branch sites come up without a truck roll?

The console server calls home and policy does the configuring. Someone at the site racks the SLC 9000, cables it and powers it on. It registers to Percepxion over an outbound-only MQTT connection, so there’s no inbound firewall request to file with the site’s network owner.

From there, Smart Groups take over. A Smart Group pairs a membership rule (which devices belong) with the firmware and configuration they should get. When a new unit calls home, Percepxion evaluates the groups and applies the matching policy. That’s zero-touch provisioning for the console layer, and it’s the difference between running fifty parallel SSH sessions and reviewing one policy.

Then you bring up the gear behind it over its console ports, from your desk, before it ever touches the production network.

What does the daily work look like?

Mostly the same moves, with fewer steps in between. Direct SSH to a console port uses TCP 3000 plus the port number, so port 2 is 3002. Or open the console in a browser through Percepxion, with no VPN and without looking up the console server’s IP.

For Cisco IOS and IOS-XE devices, define the attached gear as managed devices and the SLC 9000 runs config pulls, pushes, health checks and interface actions on a schedule. Console access itself is vendor-neutral, so the firewall, the load balancer and the odd appliance in the corner all sit on the same ports.

At fleet level, Percepxion schedules jobs, manages firmware, applies config templates, and backs up and restores the console servers’ own configuration. A firmware update across every branch becomes one scheduled job instead of a weekend of logins.

And when a device does fall off the production network, the console path is still there.