# Unable to run sh run playbook on cisco\_csr

**URL:** <https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945>\
**Category:** Get Help\
**Tags:** playbook\
**Created:** [February 19, 2024, 10:36am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945 "2024-02-19T10:36:40Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 19, 2024, 10:36am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/1 "2024-02-19T10:36:40Z")

</div>

I can run other sh commands like sh version, sh ip int brief but the sh run doesn’t work on the cisco CSR. What I am missing here?

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/e/e39658522f0055deae8e57dcd77b0273acd6c7fb.png)

swapna@jumphost1:~/ansible$ ansible-playbook shrun.yml  
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

PLAY [Backup show run (enable mode commands)] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
[WARNING]: While constructing a mapping from /home/swapna/ansible/host\_vars/cisco\_csr.yml, line 1, column 1, found a duplicate dict key (ansible\_host). Using last defined value only.  
[WARNING]: ansible-pylibssh not installed, falling back to paramiko

TASK [run enable level commands] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
fatal: [cisco\_csr]: FAILED! =\> {“changed”: false, “msg”: “show running-config\r\nshow running-config\r\n ^\r\n% Invalid input detected at ‘^’ marker.\r\n\r\nCSR2\>”}

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
cisco\_csr : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

swapna@jumphost1:~/ansible$

## swapna@jumphost1:~/ansible$ cat shrun.yml

- name: Backup show run (enable mode commands)  
hosts: all  
gather\_facts: false  
connection: local

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 19, 2024, 11:42am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/2 "2024-02-19T11:42:38Z")

</div>

@chinmasw Hello.

The user who login to devices does not have privilege permission.

Maybe you can execute `show version` not `show running-config`.

You should use a privilege user or privilege escalation to execute `show running-config`.

See also: [IOS Platform Options — Ansible Documentation](https://docs.ansible.com/ansible/latest/network/user_guide/platform_ios.html#ios-platform-options)

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 19, 2024, 12:56pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/3 "2024-02-19T12:56:50Z")

</div>

Thank you that worked.

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 19, 2024, 1:02pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/4 "2024-02-19T13:02:41Z")

</div>

![image](https://us1.discourse-cdn.com/ansible/original/2X/d/d93e234920294ecbc1e167053ddc9fbf0ad54f3e.png)

I am trying to backup the config and save it in backups folder, it is falling here “msg”: “can not use content with a dir as dest”

swapna@jumphost1:~/ansible$ ansible-playbook backup.yml  
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

PLAY [cisco\_csr] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
[WARNING]: ansible-pylibssh not installed, falling back to paramiko

TASK [Gathering Facts] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
ok: [cisco\_csr]

TASK [Get ansible dat/time facts] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
ok: [cisco\_csr]

TASK [Store DTG as fact] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
ok: [cisco\_csr]

TASK [Create Directory 2024-02-19] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
changed: [cisco\_csr]

PLAY [cisco\_csr] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK [show run on device] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
ok: [cisco\_csr]

PLAY [cisco\_csr] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK [Save output to ~/ansible/backups] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
fatal: [cisco\_csr]: FAILED! =\> {“changed”: false, “msg”: “can not use content with a dir as dest”}

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
cisco\_csr : ok=5 changed=1 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

swapna@jumphost1:~/ansible$ cd backups  
swapna@jumphost1:~/ansible/backups$ ls  
2024-02-19  
swapna@jumphost1:~/ansible/backups$ cat 2024-02-19/  
cat: 2024-02-19/: Is a directory  
swapna@jumphost1:~/ansible/backups$ cd 2024-02-19/  
swapna@jumphost1:~/ansible/backups/2024-02-19$ ls  
swapna@jumphost1:~/ansible/backups/2024-02-19$ ls  
swapna@jumphost1:~/ansible/backups/2024-02-19$

swapna@jumphost1:~/ansible$ cat backup.yml

## Playbook to get system time and append it to backup files

* * *

- hosts: cisco\_csr

- hosts: cisco\_csr  
gather\_facts: false

- hosts: cisco\_csr  
gather\_facts: false

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 19, 2024, 1:07pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/5 "2024-02-19T13:07:25Z")

</div>

@chinmasw

As per the error message `can not use content with a dir as dest`, you should specify file path to `dest` option of copy module.

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 19, 2024, 1:13pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/6 "2024-02-19T13:13:10Z")

</div>

@chinmasw

For example, how about the following.

```yaml
- name: Save output to ~/ansible/backups
  copy:
    content: "{{ config.stdout[0] }}"
    dest: "~/ansible/backups/{{ hostvars.cisco_csr.DTG }}/show_running-config.txt"

```

In this case the `dest` option needs a file path.

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 19, 2024, 11:48pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/7 "2024-02-19T23:48:38Z")

</div>

> [@akira6592](#):
>
> ```auto
> - name: Save output to ~/ansible/backups
> copy:
> content: "{{ config.stdout[0] }}"
> dest: "~/ansible/backups/{{ hostvars.cisco_csr.DTG }}/show_running-config.txt"
> 
> ```

Your Awesome it works. As a extension to the playbook, I am adding some of the show commands output. l guess I need to use some template like j2 for storing multiple sh commands output as the .txt you can only save 1 show command output. Is there a way out of not using j2?

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 20, 2024, 12:16pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/8 "2024-02-20T12:16:52Z")

</div>

@chinmasw

There are two ways to store the results of multiple show commands.

1. Store one result to per file.  
like `show_running-config.txt`, `show_version.txt` and so on.

2. Store multiple results to one file.

Which way do you like?

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 21, 2024, 3:58am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/9 "2024-02-21T03:58:43Z")

</div>

Option 2 storing in 1 file with multiple results.

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 21, 2024, 1:06pm UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/10 "2024-02-21T13:06:34Z")

</div>

@chinmasw

There are several ways to do it… How about this one?

```yaml
  tasks:
    - name: show run on device
      ios_command:
        commands:
          - show running-config
          - show version
      register: config

    - name: Save output to ~/ansible/backups
      blockinfile:
        path: "~/ansible/backups/{{ hostvars.cisco_csr.DTG }}/show_results.txt"
        block: "{{ item }}"
        marker: "======================================" # separator
        create: true
      loop: "{{ config.stdout }}"
      loop_control:
        label: " " # suppressing log output

```

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 22, 2024, 12:31am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/11 "2024-02-22T00:31:41Z")

</div>

Works perfectly. Thank you for your help

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 22, 2024, 12:36am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/12 "2024-02-22T00:36:02Z")

</div>

@chinmasw My pleasure.  
Could you mark my answer as solution to explicit closing this topic?

---

<div class="post-metadata">

**Author:** ![chinmasw](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@chinmasw](https://forum.ansible.com/u/chinmasw)\
**Post date:** [February 22, 2024, 12:42am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/13 "2024-02-22T00:42:48Z")

</div>

Yes, how do I close this conversation ?

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [February 22, 2024, 1:10am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/14 "2024-02-22T01:10:13Z")

</div>

It was marked as solution [this comment](http://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/7), so this topic will close a month after the last reply.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [March 23, 2024, 1:10am UTC](https://forum.ansible.com/t/unable-to-run-sh-run-playbook-on-cisco-csr/3945/15 "2024-03-23T01:10:35Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.