-
Notifications
You must be signed in to change notification settings - Fork 42
Error with "get_bgp_neighbors" #177
Comments
@mirceaulinic Any updates on resolving this issue? |
@bdlamprecht We probably need the output of the following to help us debug the information. Should be able to get this by using |
As discussed in the NetworkToCode Slack channel, here is the XML file for the peer that is crashing the xml for junos_bgp_getter issue.txt Let me know if you need other information. |
The #209 should fix that as the error is exactly the same. However I cannot see the problem based on the xml file provided (ie: all ribs have the @bdlamprecht is it possible that |
@ckishimo Yes, #209 did fix the error for However, but when I checked the napalm I've done what you asked and posted the Hope that provides you with enough information to troubleshoot the problem. Note, I did change the addressing of the first two octets of the BGP peers to RFC1918 addresses. FYI, I can't guarantee that it is the same as before as these are lab devices and multiple people may have changed the configuration since the previous information was posted. |
@bdlamprecht thanks for the outputs! I was able to see an error while using
Based on the data provided,
I just pushed the change converting |
@ckishimo Yes, that fixed the issue I was having. I now get the expected values back correctly. Please submit this fix as PR so it can be merged into the main driver. Thanks again for investigating this and revolving it so quickly. |
Closed via 0fbda09 |
Description of Issue/Question
When running the NAPALM getter 'get_bgp_neighbors()' I get an
IndexError: list index out of range
error.Did you follow the steps from https://github.com/napalm-automation/napalm#faq
[X] Yes
[ ] No
Setup
napalm-junos version
(Paste verbatim output from
pip freeze | grep napalm-junos
between quotes below)JunOS version
(Paste verbatim output from
show version and haiku
between quotes below)Steps to Reproduce the Issue
Run the following code:
Error Traceback
Provides the following error:
The text was updated successfully, but these errors were encountered: