# Accessing Extreme Network devices via CLI running on BOSS **URL:** \ **Category:** Get Help\ **Tags:** network\ **Created:** [June 20, 2024, 9:41am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677 "2024-06-20T09:41:27Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Mittens66](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mittens66/32/3020_2.png) [@Mittens66](https://forum.ansible.com/u/Mittens66)\ **Post date:** [June 20, 2024, 9:41am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/1 "2024-06-20T09:41:27Z")
Hello dear community, I am currently working on a small Ansible project. We are currently using XIQ to access various ERS and VSP devices from Extreme Networks. This is being phased out as the license costs are far too high. With Ansible, I have already managed to access the VSP using a module (community.network.voss). However, I am having trouble executing CLI commands on devices running BOSS (Baystack Operating System Switching), such as the ERS3626GTS-PWR+. Unfortunately, I have not found a module for this; is there one that I might be overlooking? The goal is simply to execute CLI commands on the devices. Kind Regards ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [June 20, 2024, 9:52am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/2 "2024-06-20T09:52:29Z")
Are you aware of the [ansible.builtin.command module](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/command_module.html), [ansible.builtin.shell module](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/shell_module.html) and [ansible.builtin.expect module](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/expect_module.html) these might provide all you need? Or perhaps I have misunderstood the issue? ---
**Author:** ![Mittens66](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mittens66/32/3020_2.png) [@Mittens66](https://forum.ansible.com/u/Mittens66)\ **Post date:** [June 20, 2024, 10:00am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/3 "2024-06-20T10:00:55Z")
I have tried using ansible.builtin.ssh which resulted in the following error message: fatal: [X.X.X.X]: FAILED! =\> {“msg”: “network os ansible.builtin.ssh is not supported”} But I may have missed the modules you’ve listed. I’ll give them a try once I arrive at work. ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [June 20, 2024, 10:26am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/4 "2024-06-20T10:26:09Z")
Ah, I was assuming you can SSH to the devices, is this not the case? ---
**Author:** ![Mittens66](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mittens66/32/3020_2.png) [@Mittens66](https://forum.ansible.com/u/Mittens66)\ **Post date:** [June 20, 2024, 10:30am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/5 "2024-06-20T10:30:35Z")
Yes I can SSH to the devices, they have a normal CLI which you can access via SSH. Maybe there is a problem in my Inventory.ini since thats the place where I defined the network os which then uses the ansible.builtin.ssh ---
**Author:** ![rolfd](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rolfd](https://forum.ansible.com/u/rolfd)\ **Post date:** [July 30, 2025, 1:46pm UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/6 "2025-07-30T13:46:42Z")
Hello to all, I habe the same issue with the BOSS based Switches. Has anyone found a solution on this? As far as I’ve figured out, it’s due to the command pass from Ansible to sshpass. Ansible is passing a shell call that can’t work because no shell is present. The shell call is as follows: ‘/bin/sh -c ‘"’“‘echo ~RW && sleep 0’”’"‘’ Does anyone have any idea how to disable this shell call? Regards and many thanks in Advance for your support Rolf ---
**Author:** ![Rohit\_Kashinath\_Pawa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rohit_kashinath_pawa/32/9184_2.png) [@Rohit\_Kashinath\_Pawa](https://forum.ansible.com/u/Rohit_Kashinath_Pawa)\ **Post date:** [July 30, 2025, 6:51pm UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/7 "2025-07-30T18:51:32Z")
Great to know !!! ---
**Author:** ![rolfd](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rolfd](https://forum.ansible.com/u/rolfd)\ **Post date:** [July 31, 2025, 3:05pm UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/8 "2025-07-31T15:05:40Z")
Hello, does anyone have an idea to solve the problem? The ping module behaves the same way. In addition to the “show clock” argument, a shell call is passed. sudo -H -S -n -u root /bin/sh -c ‘"’“‘echo BECOME-SUCCESS-kimxyplsdcwnvuwrtjfsymyvmgniumwn ; show clock’”‘"’'- Is there a way to prevent this shell call? Regards Rolf ---
**Author:** ![rohitthakur2590](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rohitthakur2590/32/1922_2.png) [@rohitthakur2590](https://forum.ansible.com/u/rohitthakur2590)\ **Post date:** [August 8, 2025, 5:17am UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/9 "2025-08-08T05:17:45Z")
so looks like the default connection plugin attempts to run commands via `/bin/sh -c`, which doesn’t exist on BOSS. I think this behavior might driven by `ansible_shell_type` and `ansible_shell_executable`, which are used in the `ConnectionBase` class to load the appropriate shell plugin via `get_shell_plugin()`.So If you don’t know the CLI binary path or don’t want Ansible to wrap commands at all, I believe we can try to prevent Ansible from using _any_ shell at all: may be something like this would work ```auto ansible_shell_type=none ansible_shell_executable=/bin/true ``` ---
**Author:** ![rolfd](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rolfd](https://forum.ansible.com/u/rolfd)\ **Post date:** [August 8, 2025, 12:47pm UTC](https://forum.ansible.com/t/accessing-extreme-network-devices-via-cli-running-on-boss/6677/10 "2025-08-08T12:47:21Z")
Hello, many thanks for your hint. I tried ist, but no luck. The failure message below: FAILED! =\> {“msg”: “Could not find the shell plugin required (none).”} I checked the documentation about possible sheels and I see root@ansible:/etc/ansible# ansible-doc -t shell -l ansible.builtin.cmd Windows Command Prompt ansible.builtin.powershell Windows PowerShell ansible.builtin.sh POSIX shell (/bin/sh) ansible.posix.csh C shell (/bin/csh) ansible.posix.fish fish shell (/bin/fish) root@ansible:/etc/ansible# There is no option to use no shell. regards Rolf