{"repo":"napalm-automation-community/napalm-ros","free":true,"listed":false,"github":"https://github.com/napalm-automation-community/napalm-ros","clone":"git clone https://github.com/napalm-automation-community/napalm-ros.git","description":"MikroTik RouterOS NAPALM driver","language":"Python","stars":118,"topics":["routeros","driver","napalm","api","mikrotik","python","python3"],"license":null,"category":"api-integrations-sdks","readme_excerpt":"Caveats As napalm-ros uses API, several caveats exist. No safe mode (not exposed via API). There is no commit, rollback. API is not versioned so things may break when routeros is upgraded. Missing features. This driver does not implement any configuration management. Config management on mikrotik is different than on cisco, juniper etc. which provide config replace . You provide a plain text config file and replace running config with that. MikroTik does not have this. Some menu paths (eg. /ip address) do not have any order in which entries appear. Only one unique ip address can exist within a VRF. In some paths (eg. /ip firewall filter) order matter. Implemented getters get arp table get interfaces counters get environment get facts get interfaces get interfaces ip get ntp servers get snmp information get users get ipv6 neighbors table is alive ping get lldp neighbors get lldp neighbors detail get network instances get mac address table get bgp neighbors get bgp neighbors detail get config get vlans","default_branch":null,"files":null,"tree":[],"storefront":"/r/napalm-automation-community","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/napalm-automation-community/napalm-ros/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}