search

napalm-automation-community / napalm-aruba-cx

NAPALM driver for Aruba AOS-CX
Apache License 2.0
14 stars 7 forks source link

Issue with get_config #5

Open legalla opened 3 years ago

legalla commented 3 years ago

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

if retrieve in ["running", "all"]:
    config_dict['running'] = self._get_json_configuration("running-config", **self.session_info)
if retrieve in ["startup", "all"]:
    config_dict['startup'] = self._get_json_configuration("startup-config", **self.session_info)
sleppelm commented 3 years ago

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.

alagoutte commented 3 years ago

push the similar fix on #13 but always get [Object] [Object] on Netbox...

legalla commented 3 years ago

It has to be troubleshooted on Netbox side as if you call the get_config method using Netbox APIs, everything works fine.

sleppelm commented 3 years ago

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 notifications@github.com 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 https://github.com/napalm-automation-community/napalm-aruba-cx/issues/5#issuecomment-768418408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHNNMLQRT7JM43MF6HQR57DS4A7VPANCNFSM4TPLSTQA .

alvinc13 commented 3 years ago

Hi @sleppelm , can you please tell me which Aruba switch you're running this against and which software version? Thanks!

sleppelm commented 3 years ago

Hi, I've troubleshooted with every version of 10.06.

Thank you!

On Wed, Jan 27, 2021 at 11:45 AM alvinc13 notifications@github.com wrote:

Reopened #5 https://github.com/napalm-automation-community/napalm-aruba-cx/issues/5.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/napalm-automation-community/napalm-aruba-cx/issues/5#event-4257418142, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHNNMLVFBWAYJ47TXJLUXBDS4BNMTANCNFSM4TPLSTQA .

a83r commented 3 years ago

Hi, the issue still is there. We are running 10.06 and when calling get_config I get:

HTTP 200 OK Allow: GET, HEAD, OPTIONS Content-Type: application/json Vary: Accept

{ "get_config": { "error": "Method get_config failed: 'url'" } }

alagoutte commented 3 years ago

Hi @a83r, what release of napalm module do you are using ? because it is not yet available on last release (on pip)

a83r commented 3 years ago

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. It now shows "[object Object]" Would be great if it would be implemented, but for us it isn't a critical feature. As long as the LLDP Neighbors work we are very happy.

alagoutte commented 3 years ago

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. It now shows "[object Object]" i get also this issue but no yet found time to look why...

alvinc13 commented 3 years ago

Hello, We are currently working on a major update for the pyaoscx Python libraries which the AOS-CX NAPALM drivers depend on. Once that is released, these NAPALM drivers will get an updated overhaul where I also plan to include some Netmiko usage to expand the driver capabilities and test against the newest Netbox instance. Thanks for your patience.

a83r commented 3 years ago

@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.

alagoutte commented 3 years ago

@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)

a83r commented 3 years ago

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.

alagoutte commented 3 years ago

push the similar fix on #13 but always get [Object] [Object] on Netbox...

This part is a Netbox issue and fixed on 3.0.0 ( https://github.com/netbox-community/netbox/issues/7041 )

alagoutte commented 3 years ago

(the issue can be close :))