Skip to content
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

module doesn't upgrade all switches #125

Open
hrv231 opened this issue Oct 24, 2020 · 1 comment
Open

module doesn't upgrade all switches #125

hrv231 opened this issue Oct 24, 2020 · 1 comment

Comments

@hrv231
Copy link

hrv231 commented Oct 24, 2020

Hello,

I'm having problems with the module, it doesn't upgrade all the switches.
At the beginning I thought it was the network, and I opened cases with Cisco and other vendors, we discovered that for some reason the module works well with some of my switches and some others do not.

For the ones who doesn't work, this is what is happening:

fatal: [K-IDF225-D-2540]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}
fatal: [K-IDF355-2540-C]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}
fatal: [K-IDF355-2540-48-A]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}
fatal: [K-IDF416-A-2540-48]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}
fatal: [K-IDF545-B-2540-48]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}
fatal: [K-IDF416-C-2540-48]: FAILED! => {"changed": false, "msg": "Unable to read CLI Output in given Time"}

Another point we find out is that this happens only when using the upgrading part of the module, not when we run simple show commands, it seems the problem is on the connection for the copy of the firmware itself.

It takes exactly 1 minute and 30 to 40 seconds, and then the connection is dropped by the switch.

I think there is something wrong on the module, please help.

I have ran the upgrade also alone, on a host by host to see if it is a problem of having a lot of upgrades happening at the same time, but still doesn't work.

I even manually upgraded one of the switches to see if the module would check for the version and still, it doesn't work.

Once again, it works only on some. The switches are on the same network and still after 1:38 or 1:40 seconds the connection drops.

It might be an issue on the way the module handles the TCP window size.

I'm willing to help in anything you need to see why this is happening.

the ansible playbook is simple:

hosts: device_types_2540-48G-PoE+-4SFP+  
tasks:
    - name: Upgrade Firmware via SSH CLI
      arubaos_switch_ssh_cli:
        ip: "{{ ansible_host }}"
        user: "{{ ansible_user }}"
        password: "{{ ansible_password }}"
        path_to_swi: "files/YC_16_08_0015.swi"
        boot_image: "primary"
        enable_sftp: True
        state: "upgrade"

We tried with 2540 switches and also 2530 switches, and the module only do the upgrades on certain switches, not all.

Thank you!

@hrv231
Copy link
Author

hrv231 commented Oct 24, 2020

I forgot to mention that this is happening with any Ansible version, I tried the latest of the 2.8.x and now running Ansible 2.9.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant