ConX-SFP - Serial Console redfined and packaged as an SFP

Driven from a need to connect RS232 console ports in complex Data Centre environments for out of band management where traditional console servers just didn’t work.

Wetatronics took a fresh approach and packaged a powerful Micro Controller with multiple RS232 interfaces and gave it a 1Gbps Ethernet interface. Providing either a full serial ports with hardware handshaking or two serial ports with a breakout cable.

The ConX-SFP is ready to go out of the box, it looks like a normal 1G SFP to the switch, router or firewall it is installed. Using DHCP it is ready for local access to the console port and with the ConX portal you get full cloud remote connectivity.

Connecting to the network devices console port directly and providing secure transport provides a robust and high fidelity view of network events. Keeping the events off the production network allows faster deployment and quickly reaching cohesive network visibility

How It Works (High-Level)

  1. SFP form factor: ConX-SFP presents as a standard 1G SFP to the host device, so it fits seamlessly into existing network gear.
  2. Serial interface inside: RS-232 console connectivity (with hardware handshaking, or dual-port via breakout).
  3. Network identity & IP: It uses site DHCP for IP assignment.
  4. Managed access via portal: Your ops team uses the ConX portal to reach the console remotely. For environments with no Internet dependency, deploy the On-Premises Cloud-Free portal.

Security & Control

  • Outbound-initiated access: Minimizes inbound exposure; works with typical NAT/CGNAT scenarios.
  • Tenant boundary: Devices appear only within your ConX portal tenant for role-based access.
  • Asset tracking: Registered MAC address allocation enables consistent device identity management across fleets.
  • Air-gapped option: Fully local, Internet-independent portal for classified or sovereign environments.

Network & Site Requirements

  • SFP slot: Any spare 1G SFP cage on a gateway, router, switch, or firewall.
  • DHCP: Standard IPv4 DHCP for initial address assignment.
  • Outbound connectivity: Allow outbound connectivity from the ConX-SFP to the ConX portal (or to your on-prem portal host for air-gapped deployments).
  • Console cabling: RS-232 console on the target device (single with handshaking, or dual via breakout).

Day-2 Operations

  • Fleet view: See deployed ConX-SFPs in the portal, filter by site/customer, open a console in a click.
  • Standard runbooks: Use the same browser-based console workflow for every vendor and model.
  • Auditability: Centralize who accessed what and when (portal activity logging).
  • Air-gapped sites: Mirror the same workflow with the on-prem portal.

FAQ

Does ConX-SFP require a site VPN?
No. ConX-SFP is designed for cloud remote connectivity—it uses DHCP on-site and connects to the ConX portal. For environments that prohibit Internet access, use our On-Premises Cloud-Free deployment.

What gear does it work with?
Anything with a spare 1G SFP slot and a serial console port—broadband gateways, routers, switches, firewalls, PDUs, servers with RS-232 adaptors, etc.

We operate in classified/air-gapped environments.
Deploy the On-Premises Cloud-Free portal: same experience, fully local, air-gapped from the Internet.