sauble.ai · connector spec sheet

Device Access Multi-protocol device access

Ask plain-English questions answered straight from your network devices — over SNMP, CLI, and gNMI, with nothing in between.

Self-hosted
SNMPCLIgNMIRead-only
Unlocks

Connect Device Access and Sauble reaches your actual switches and routers directly — over SNMP, CLI, and gNMI, with no NMS or controller in between. It reads interface health, topology, the ARP table and live AI-fabric congestion, and can drop to raw protocol calls for anything else. Read-only by design: it can look at anything on the box and change nothing — devices are addressed by name, and secrets never leave the process.

01

What sauble.ai can do

10 capabilities, grouped by what you are trying to find out.

See what a device is doing

device_get_healthThe device's identity and uptime — description, name, and how long it has been up.
device_get_interfacesEvery interface: operational up/down state and error counters — in/out errors and CRCs.

Trace how it connects

device_get_neighborsLLDP neighbors — what is physically cabled to each port (best effort; richer over CLI).
device_get_arp_macThe ARP table — which IP maps to which MAC address on the device.

AI-fabric congestion, live

device_get_fabric_countersPer-interface AI-fabric health over gNMI — ECN/PFC/queue congestion and FEC/physical errors.

Reach the device over raw SNMP, CLI & gNMI

device_snmp_getRead one SNMP OID directly.
device_snmp_walkWalk an SNMP subtree — read-only and row-capped.
device_cli_runRun one read-only CLI command — allowlist-checked and scrubbed for secrets.
device_gnmi_getRead one gNMI path directly.
device_gnmi_sampleSample a gNMI path for up to 30s — a bounded live SUBSCRIBE window.

Plus list_devices — the devices in this environment and which transports (SNMP/CLI/gNMI) each one supports.

02

Ask it things like

Natural language — sauble.ai picks the right tools for you.

>Which interfaces on core-sea-01 are down or throwing errors right now?
>What is cabled to dist-sea-02 — show me its LLDP neighbors.
>Is ECN or PFC congestion building on the fabric uplinks?
>Which IP owns that MAC on the gateway — check the ARP table.
>Run “show version” on acc-sea-11 and tell me the software release.
>Walk the interface-counter OIDs on this switch and find rising CRC errors.
03

How Device Access organizes your data

The 5 things sauble.ai reads — and how they connect.

Environment

One connector serves one Sauble environment’s device inventory — nothing outside it is reachable.

Devices

Addressed by inventory name, never raw IP; each declares which transports it supports.

SNMP

OIDs and MIBs — device health, interface counters, LLDP neighbors and the ARP table.

CLI (SSH)

Allowlisted read-only commands with a vendor driver chosen from the device platform; output scrubbed.

gNMI

Model-driven paths — a point-in-time GET or a bounded live sample, including AI-fabric counters.

Transports
SNMPCLI (SSH)gNMI

Run Device Access in your network

You run the Device Access connector inside your network, scoped to one environment’s device inventory. It reaches your devices read-only over SNMP, CLI and gNMI — addressing them by name, never exposing raw IPs or credentials to Sauble.

Read-only by design Get Device Access →