See details in the parent issue napalm-automation/napalm#199

Like allready mentioned in #36, here is the patch wich ports my implementation for get_lldp_neighbors_detail back to the root.

https://github.com/Sprinterfreak/napalm-vyos-temp/commit/e95534e63f5706216dd5d8a691e8460839a2307a

Sadly github doesn't let me fork napalm-vyos as long as I have napalm-edgeos forked, wich in turn is itself a greatly diverged fork from this.

See details in the parent issue napalm-automation/napalm#327

Installation fails when using pip 18.1 (with Python 3.6 in CentOS 7)

[vagrant@default ~]$ pip3 --version
pip 18.1 from /usr/local/lib/python3.6/site-packages/pip-18.1-py3.6.egg/pip (python 3.6)
[vagrant@default ~]$ pip3 install --user napalm-vyos
Collecting napalm-vyos
  Using cached https://files.pythonhosted.org/packages/e0/ff/2d70e5c7b9925688e000bcc89e140c3bddb61868b1b6cb25414080390700/napalm-vyos-0.1.5.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-kh0bects/napalm-vyos/setup.py", line 6, in <module>
        from pip.req import parse_requirements
    ModuleNotFoundError: No module named 'pip.req'
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-kh0bects/napalm-vyos/

Issue:- napalm-vyos getter for bgp_neighbors is not returning any information.

vyos version:- 1.3-rolling-202001081700

~/Automation/scripts_napalm  pip3 list | grep napalm                                                                           
napalm                3.2.0    
napalm-vyos           0.2.1    
 ~/Automation/scripts_napalm  pip3 list | grep netmiko                                                                           
netmiko               3.4.0    
 ~/Automation/scripts_napalm  

BGP output from vyos

vyos@vyos:~$ show ip bgp summary 

IPv4 Unicast Summary:
BGP router identifier 192.168.1.1, local AS number 65360 vrf-id 0
BGP table version 1042
RIB entries 2024, using 364 KiB of memory
Peers 2, using 41 KiB of memory

Neighbor        V         AS MsgRcvd MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd
172.16.12.2     4      65501   88274   88273        0    0    0 08w5d06h           18
172.16.13.2     4      65361   97094   88274        0    0    0 08w5d06h         1001

Total number of neighbors 2
vyos@vyos:~$ 

naplam output

napalm --user ansible --password ansible123  --vendor vyos vyos call get_bgp_neighbors       
{}

New vyos version introduces changes in configuration syntax but also sometimes in outputs.

Few getters seem to be affected as:
get_facts, get_bgp_neighbors

Ref: napalm-automation/napalm-base#185

See details in the parent issue napalm-automation/napalm-base#99

Hello,
community drivers are going to be maintained by the community or considered deprecated and unmaintained. For that reason we are looking for people willing to maintain this repo. Owners will have full admin rights on this repo and on its pypy package.

Pinging top contributors to see if they are interested; @mirceaulinic

If you have questions/comments let me know.

Regards

This is necessary to support network discovery of VyOS routers.

Ref: napalm-automation/napalm-base#105

See details in the parent issue napalm-automation/napalm-base#107

See details in the parent issue napalm-automation/napalm-base#214

See details in the parent issue napalm-automation/napalm-base#137

Is there any plan to support Ubiquiti EdgeOS (a fork of VyOS)? The main difference I've noted is that the terminal length command needs a workaround in netmiko (set terminal length isn't supported on EdgeOS).

Before making it official we have to ensure documentation is updated. Could you take a look?

https://napalm.readthedocs.io/en/latest/support/index.html

Also, you will need a PR to tell napalm this is py3 compliant. Something like this:

https://github.com/napalm-automation/napalm-base/pull/177/files

Hello guys,
allow me to invite you to https://slack.vyos.io
so we can assist with anything (for testing, and what's more)
Thanks for your work!

See details in the parent issue napalm-automation/napalm-base#217

Hello @ppieprzycki,
I enabled travis and tests are failing. Could you take a look, please?

Thanks!
David

When applying a commit that ultimately fails the errors are not shown to the user, looking at Netmiko it does capture these errors and passes it back when a ValueError exception is raised https://github.com/ktbyers/netmiko/blob/5f9eaa9e54401a758375574c656655e44bee3746/netmiko/vyos/vyos_ssh.py#L94-L95

napalm-vyos just catches the ValueError and raises a CommitError with it's own message.

TASK [Apply Configuration] **********************************************
fatal: [dev]: FAILED! => changed=false 
  msg: 'cannot install config: Failed to commit config on the device'

In trying to deploy napalm-vyos as part of a Netbox deployment I've been doing recently, I noticed that napalm-vyos requires napalm==2.*, but the current Napalm release is 3.x.

So one issue I experienced is that I applied a config from napalm-vyos with the vyos user which was to add my personal user. This works fine.

However on the next run if I try to do a diff/commit with my personal user I get an error

fatal: [router1]: FAILED! => changed=false 
  msg: |-
    cannot load config: scp: /var/tmp/candidate_running.conf: Permission denied

This seems to be because the /var/tmp/candidate_running.conf file is left around from previous runs and has 644 permissions, only allowing the vyos user to write to it. This wouldn't become an issue if these files were cleaned up after the operation(s) are finished, which it seems the code as of now does not do that.

vyos@dev:~$ ls -la /var/tmp
total 20
drwxrwxrwt  6 root  root   180 Jun 11 16:50 .
drwxr-xr-x  1 root  
-rwxr-xr-x  1 vyos  users 1896 Jun 11 16:48 backup_running.conf
-rw-r--r--  1 vyos  users 1784 Jun 11 16:48 candidate_running.conf
-rw-r--r--  1 yzguy users  182 Jun 11 16:50 test.sh