You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
get_bgp_neighbors for NXOS returns global local-as setting rather than the per-session local-as
Looking at the internals of napalm it uses 'show bgp all summary vrf all' in the NXOS driver for gt_bgp_neighbors.
This command only returns the global ASN for the BGP router. It does not return the actual local-as for each BGP peering session. You'd need to combine the data from 'show running-config bgp' output in order to return the correct local-as for each individual BGP session.
Actually I just noticed that 'show ip bgp neighbors vrf all' returns local AS for eBGP neighbors so it could be used for more accurate information.
# show ip bgp neighbors vrf all
BGP neighbor is 11.11.11.1, remote AS 65001, local AS 12345, ebgp link, Peer index 5
Description: test_descr
BGP version 4, remote router ID 1.1.1.2
Neighbor previous state = OpenConfirm
BGP state = Established, up for 02:54:10
Neighbor vrf: default
...
Description of Issue/Question
get_bgp_neighbors for NXOS returns global local-as setting rather than the per-session local-as
Looking at the internals of napalm it uses 'show bgp all summary vrf all' in the NXOS driver for gt_bgp_neighbors.
This command only returns the global ASN for the BGP router. It does not return the actual local-as for each BGP peering session. You'd need to combine the data from 'show running-config bgp' output in order to return the correct local-as for each individual BGP session.
Did you follow the steps from https://github.com/napalm-automation/napalm#faq
(Place an
x
between the square brackets where applicable)Setup
napalm version
(Paste verbatim output from
pip freeze | grep napalm
between quotes below)Network operating system version
(Paste verbatim output from
show version
- or equivalent - between quotes below)Steps to Reproduce the Issue
The text was updated successfully, but these errors were encountered: