napalm-automation/napalm

Rework EOS BGP neighbors

Open

#2316 opened on Apr 20, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (2,145 stars) (553 forks)batch import
eosget_bgp_neighbors_detailhelp wanted

Description

Since we now mandate that only EOS > 4.23.0F is supported, we can switch from TextFSM processing to JSON output for show ip[v6] bgp neighbors vrf all. This should (hopefully) simplify some logic and remove edge cases such as #2280

Contributor guide

Tech stack
python
Domain
backendapi
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python basicsNapalm library structureBGP neighbor understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current implementation in napalm/eos.py or related files that handle 'show ip[v6] bgp neighbors vrf all' using TextFSM. Review the linked issue #2280 for edge cases that were previously tricky. The goal is to replace TextFSM parsing with JSON output from the device (EOS > 4.23.0F). Ensure backward compatibility and test on a live EOS device or simulation.