Documentation
Network platforms (Cisco, Arista, Juniper, HPE Aruba, Palo Alto Networks and others)
Connecting REAP to Network platforms (Cisco (opens in a new tab), Arista (opens in a new tab), Juniper (opens in a new tab), HPE Aruba (opens in a new tab), Palo Alto Networks (opens in a new tab) and others): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Device access for configuration retrieval, state and telemetry through the connector cluster, and for approved runbooks. Coverage for Fortinet (opens in a new tab), SONiC (opens in a new tab) and other platforms is confirmed per pilot against your platforms and versions.
Prerequisites
- Read-only device accounts (see credentials)
- Syslog/gNMI destinations set to the connector VIP; NetFlow or IPFIX exporters pointed at it where you choose to send flow records
- SNMP read community or SNMPv3 user
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Show commands, configuration retrieval, SNMP read, telemetry subscription, flow records where configured | Observe |
| Write (optional) | Scoped account limited to approved runbook commands | Act, under approval |
Setup
- Provision accounts via AAA; configure command authorization for the runbook account.
- Point syslog and gNMI (opens in a new tab) at the VIP; enable SNMP for the connector source address; configure flow exporters to the VIP where you want flow records collected.
- Verify discovery, configuration retrieval and telemetry per platform.
What REAP reads
- Running/startup configuration and history, interface and protocol state, logs and streaming telemetry
- Flow records (NetFlow or IPFIX) where you configure exporters; no payload inspection
What REAP writes
- Only approved runbook commands, with approval, pre-execution impact analysis, reverse steps where the change is reversible, and audit
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Device not discovered | ACL blocks connector or wrong credentials | Test SSH from the connector |
| No telemetry | Destination not set to VIP | Check device logging/telemetry config |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- Supported OS versions per platform; telemetry modes per platform
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai