-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with get_config #5
Comments
I have the same problem and issues with many of the other get commands. 10.0.5 and 10.0.6. I really wish it worked more consistently with CX because there are many great applications for using Napalm, even with such a limited scope right now. Hoping it gets fixed soon. |
File "napalm-aruba-cx/napalm_aoscx/aoscx.py", line 625, in get_config config_dict['running'] = self._get_json_configuration("running-config") File "napalm-aruba-cx/napalm_aoscx/aoscx.py", line 904, in _get_json_configuration target_url = kwargs["url"] + "fullconfigs/{}".format(checkpoint) KeyError: 'url' issue also reported on napalm-automation-community#5 Signed-off-by: Alexis La Goutte <[email protected]>
push the similar fix on #13 but always get [Object] [Object] on Netbox... |
It has to be troubleshooted on Netbox side as if you call the get_config method using Netbox APIs, everything works fine. |
I can't do a get_config or several others just using Python get commands
though. Some work and some don't, that's an example of one. Latest
version of everything.
Thanks!
…On Wed, Jan 27, 2021 at 9:48 AM legalla ***@***.***> wrote:
It has to be troubleshooted on Netbox side as if you call the get_config
method using Netbox APIs, everything works fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNNMLQRT7JM43MF6HQR57DS4A7VPANCNFSM4TPLSTQA>
.
|
Hi @sleppelm , can you please tell me which Aruba switch you're running this against and which software version? Thanks! |
Hi, I've troubleshooted with every version of 10.06.
Thank you!
…On Wed, Jan 27, 2021 at 11:45 AM alvinc13 ***@***.***> wrote:
Reopened #5
<#5>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNNMLVFBWAYJ47TXJLUXBDS4BNMTANCNFSM4TPLSTQA>
.
|
Hi, HTTP 200 OK { |
Hi @a83r, what release of napalm module do you are using ? because it is not yet available on last release (on pip) |
Sorry my bad. I just installed the current dev release of napalm-aruba-cx and the release version of napalm. The netbox version is v2.11.1. |
|
Hello, |
@alvinc13 Do you work at HPE/Aruba? If yes maybe you could add a option to the switch os to create read only napalm users, currently only admin users are supported. As for netbox we don't need admin rights. |
What do you are using for authentication on the switch ? only local account ? or RBAC (with RADIUS or TACACS) |
Currently only local accounts, but we are thinking about using a hpe clearpass appliance for this. But with local accounts it is only possible to use admin accounts. |
This part is a Netbox issue and fixed on 3.0.0 ( netbox-community/netbox#7041 ) |
(the issue can be close :)) |
get_config fails as session information are not sent when it calls the _get_json_configuration function.
"**self.session_info" has to be used when get_config calls this sub-function
The text was updated successfully, but these errors were encountered: