Migrating from SNMP to gNMI and OpenConfig: A Practical Guide
·2 min read·220 words
SNMP → gNMI + OpenConfig migration: modern streaming telemetry for data center and service provider monitoring. Push model, sub-second granularity, and JSON/Protobuf. Increasing adoption by hyperscalers. 2026 migration guide.
Why Migrate from SNMP
- SNMP: poll-based, with typical intervals of 30-60s
- Resource-intensive SNMP OID parsing
- SNMP v2c is insecure
- gNMI: push streaming with sub-second granularity
- gNMI: structured data (Protobuf/JSON)
- OpenConfig: cross-vendor standard
gNMI Architecture
- gRPC over TLS (HTTP/2)
- OpenConfig YANG models
- Subscribe (stream) and Get/Set operations
- Modes: STREAM, ONCE, POLL
Vendor Support
- Cisco IOS-XE 16.10+ + NX-OS 9.3+
- Arista EOS: excellent support
- Juniper Junos 19.4+
- Nokia 7750 SR: native support
- Not all legacy equipment is supported
Tools
- gnmic: gNMI CLI client (hub.docker.com)
- gnxi: Python gNMI library
- Cisco Crosswork: commercial platform
- Telegraf gNMI plugin: Grafana integration
gnmic Example
- gnmic -a 10.0.0.1 -u admin -p pass --skip-verify subscribe --path '/interfaces/interface[name=Ethernet1]/state/counters'
- Output: JSON streaming every 500ms
Available Metrics
- /interfaces/interface/state/counters: bytes, packets
- /bgp/neighbors/neighbor/state: BGP sessions
- /components/component/state: CPU, temperature, power
- /system/processes: process statistics
- /acl/acl-sets: ACL hits
Time-Series Storage
- InfluxDB: conventional choice
- Prometheus + OpenTelemetry
- Thanos / Cortex / Mimir: scaling
- Kafka: intermediate streaming layer
Phased Migration
- Phase 1: gNMI alongside SNMP (6 months)
- Phase 2: gNMI as primary, SNMP as backup (6 months)
- Phase 3: decommission SNMP
- Legacy equipment: retain SNMP v3
Order from OPTINOC
gNMI + OpenConfig streaming migration. Cisco/Juniper/Arista. Grafana integration. Quote within 48h.