Issues with basic gets
sleppelm opened this issue · comments
Hi, I get this error or something similar for every get I try to run. I'm using a basic test script to test on our CX gear. Any suggestions would help greatly! Thanks! On 10.0.5.0011. The rest session is connecting.
Thanks!
Traceback (most recent call last):
File "Test-Napalm.py", line 12, in
print(json.dumps(device.get_facts(), sort_keys=True))
File "/home/netauto/.local/lib/python3.8/site-packages/napalm_aoscx/aoscx.py", line 123, in get_facts
'serial_number': productinfo['product_info']['serial_number'],
KeyError: 'product_info'
Hello,
I've found the issue is due to a broken URI in a recent pyaoscx package update. I've created an issue here: aruba/pyaoscx#2
I'm working with the team to get this fixed in a release today. Once that is updated, I'll test and close the issue.
pyaoscx version 0.2.2 now has the fix in place. In my own tests I no longer run into the issue. @sleppelm could you please verify whether you're still running into it? Thanks!
Hi, I appreciate your help with the previous issue. I wanted to get some clarification. I see all the get commands that are supported as of right now on napalm aos cx, but are configuration commands supported? I get a NotImplementedError. I'm assuming there isn't full support yet for this? Thanks! [image: image.png] [image: image.png]
…
On Thu, Oct 1, 2020 at 9:26 AM Scott @.> wrote: Works great. Thank you for your efforts! On Wed, Sep 30, 2020 at 10:58 AM Scott @.> wrote: > I will check it out and get back to you as soon as I can. Thanks! > > On Wed, Sep 30, 2020 at 10:40 AM alvinc13 @.***> > wrote: > >> pyaoscx version 0.2.2 now has the fix in place. In my own tests I no >> longer run into the issue. @sleppelm https://github.com/sleppelm >> could you please verify whether you're still running into it? Thanks! >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <#1 (comment)>, >> or unsubscribe >> https://github.com/notifications/unsubscribe-auth/AHNNMLVRZ3HUINWRU3LJBX3SINNQ7ANCNFSM4RXYG7WQ >> . >> >
The configuration commands are currently being worked on, but due to the API not being to handle CLI, a separate transport structure would need to be implemented (such as NetMiko). We are looking to add this in future releases though.
To clarify, I meant that we are looking to add the configuration NAPALM methods in future napalm-aruba-cx releases. I can't speak to if/when CLI commands via API will be an upcoming AOS-CX feature.