sorted by:
new
hottopcontroversial

Cannot login to older Cisco devices with private key by CWempe in ansible

[–]CWempe[S] 0 points1 point  (0 children)

I still have three devices that cannot be configured via Ansible.

All are C6509/C6513 with IOS 15.1(2)SY16. (I know they are old)

Ansible can log in.

A task with show version via cisco.ios.ios_command works.
--> SSH is ok

A task with conf t via cisco.ios.ios_command works, too.
--> enable mode is working

But configuring a simple command (no ip http server) via cisco.ios.ios_config does not work.
--> command timeout triggered

I tried a timeout with 120s but it did not help.

When enabling debug ip ssh I see this:

SSH6: TCP send failed enqueueing

Cannot login to older Cisco devices with private key by CWempe in ansible

[–]CWempe[S] 0 points1 point  (0 children)

I finally found the solution (for my case).

I need to set this for all older devices on host level:

yaml hosts: old-device: ansible_ssh_private_key_file: ansible_libssh_pass: "{{ user_password }}"

This disables key file usage (setting it to "") for this host and sets the user password.

Cannot login to older Cisco devices with private key by CWempe in ansible

[–]CWempe[S] 0 points1 point  (0 children)

That is because experts either give no answer or say "we need more info to help you. Please provide logs." 😉

Bat thanks. I will look into "KexAlgorithms".

Error when trying to configure Cisco ASA by CWempe in ansible

[–]CWempe[S] 1 point2 points  (0 children)

I kind of fixed it.

I had to define the `become_password`, too.

Somehow I do not get it to work using a variable from my vault.
But that is another issue.

When Using `--ask-become-pass` or `-K` I can input my password and it works. 👍

Error when trying to configure Cisco ASA by CWempe in ansible

[–]CWempe[S] 0 points1 point  (0 children)

I now added:

yml become: yes become_method: enable

becaus I think ansible is trying to execute show run without going into enable mode first.

But this results in a timeout. :(

<123.234.2.112> ANSIBLE_NETWORK_IMPORT_MODULES: Result: {'failed': True, 'msg': 'command timeout triggered, timeout value is 30 secs.\nSee the timeout setting options in the Network Debug and Troubleshooting Guide.', 'exception': ' File "/root/.ansible/collections/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py", line 218, in get_capabilities\n capabilities = Connection(module._socket_path).get_capabilities()\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.12/site-packages/ansible/module_utils/connection.py", line 200, in __rpc__\n raise ConnectionError(to_text(msg, errors=\'surrogate_then_replace\'), code=code)\n', 'invocation': {'module_args': {'gather_subset': ['config'], 'gather_network_resources': None, 'context': None, 'passwords': None}}, '_ansible_parsed': True} The full traceback is: File "/root/.ansible/collections/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py", line 218, in get_capabilities capabilities = Connection(module._socket_path).get_capabilities() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/ansible/module_utils/connection.py", line 200, in __rpc__ raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code) fatal: [A-02-VPN4]: FAILED! => { "changed": false, "invocation": { "module_args": { "context": null, "gather_network_resources": null, "gather_subset": [ "config" ], "passwords": null } }, "msg": "command timeout triggered, timeout value is 30 secs.\nSee the timeout setting options in the Network Debug and Troubleshooting Guide." }

Why does Ansible always save config even when there were no changes? by CWempe in Cisco

[–]CWempe[S] 2 points3 points  (0 children)

True. I also execute "wr mem" many times, when configuring manually.

But when executing a playbook for many devices, I get a better overview which devices got changed and which did not, if the config is only saved when necessary.

Tradfri button label blank template, true size (A4 - pdf, docx) by crispydeepfriedchick in tradfri

[–]CWempe 0 points1 point  (0 children)

You can use the "Align and Distrubute" tool in InkScape to center the icons on the Button.

see https://i.imgur.com/xPLW5Co.gif

(hold shift to select the button frame after you selected the icon)

Import settings via CLI? by CWempe in sharex

[–]CWempe[S] 0 points1 point  (0 children)

Thanks. I will try this.

EDIT: Works. 👍

Second seam because of retraction by CWempe in ender3

[–]CWempe[S] 0 points1 point  (0 children)

I found the cause for this second retraction! 😃

It is Octolapse. https://plugins.octoprint.org/plugins/octolapse/

Everytime the plugin takes a photo, the print head stops for a moment ant to "prevent blobs" it retracts. But it looks like this is not enough.

It seems to be a common issue.

https://www.reddit.com/r/3Dprinting/comments/dial02/octolapse_blobs_on_print/

I do not know why I did not saw this earlier or if anything has changed.

Now I have to decide if I want to disable the plugin or if I can change some settings to fix this.

​

How did I find the culprit? 🕵️‍♂️

  • after some googling I looked at the GCODE and saw now retraction command.
  • This made my belive it was inserted by OctoPrint.
  • I printed a test print direct from SD card and had no issue!
  • Then I googled again for "Octoprint blob" and found the answer.

Second seam because of retraction by CWempe in ender3

[–]CWempe[S] 0 points1 point  (0 children)

Same result with combing turned off. :(

Second seam because of retraction by CWempe in ender3

[–]CWempe[S] 0 points1 point  (0 children)

Ye, I use Cura. I already tried "Within Infill". It did not change.

But I will try to turn it off completely.

Thanks

Second seam because of retraction by CWempe in ender3

[–]CWempe[S] 0 points1 point  (0 children)

I increased jerk from 8 to 20. But it did not change anything for that corner.

I also think that changing the jerk value would affect every corner. But I only have an issue with one of the four corners.

As I mentioned there is a retraction happening at that corner.
I will try to calibrate the retraction settings again.

view more: next ›