# Ansible - save config - Small business SG 500

**URL:** <https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544>\
**Category:** Ansible Project\
**Created:** [January 28, 2019, 3:25pm UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544 "2019-01-28T15:25:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jean\_berjonneau](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@Jean\_berjonneau](https://forum.ansible.com/u/Jean_berjonneau)\
**Post date:** [January 28, 2019, 3:25pm UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544/1 "2019-01-28T15:25:30Z")

</div>

**Ansible version = 2.7.5**

Hello all,

I am using Ansible to save configurations of all my switches but they are CISCO small businesses.

I am curently using a playbook like this :

`

---

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [January 28, 2019, 3:32pm UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544/2 "2019-01-28T15:32:32Z")

</div>

Your ‘register’ statement should be less indented

---

<div class="post-metadata">

**Author:** ![Jean\_berjonneau](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@Jean\_berjonneau](https://forum.ansible.com/u/Jean_berjonneau)\
**Post date:** [January 30, 2019, 7:59am UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544/3 "2019-01-30T07:59:19Z")

</div>

Hello,

thanks for your answer, actually when i do this with “show clock” it works fine.  
Taking your advice i tried, this is my ne  
`

- name: IOS | Datadump + Show run  
ios\_config:  
authorize: yes  
provider: “{{ provider }}”  
commands:
- terminal datadump  
register: showrun

`

And it answered back with more errors than before…

`  
The full traceback is:  
Traceback (most recent call last):  
File “/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py”, line 113, in   
\_ansiballz\_main()  
File “/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py”, line 105, in \_ansiballz\_main  
invoke\_module(zipped\_mod, temp\_path, ANSIBALLZ\_PARAMS)  
File “/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py”, line 48, in invoke\_module  
imp.load\_module(‘ **main** ’, mod, module, MOD\_DESC)  
File “/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py”, line 541, in   
File “/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py”, line 472, in main  
File “/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py”, line 333, in edit\_config\_or\_macro  
File “/tmp/ansible\_ios\_config\_payload\_5TvH1X/ansible\_ios\_config\_payload.zip/ansible/module\_utils/connection.py”, line 173, in **rpc**  
ansible.module\_utils.connection.ConnectionError: operation requires privilege escalation

fatal: [BX-COM-SW6]: FAILED! =\> {  
“changed”: false,  
“module\_stderr”: “Traceback (most recent call last):\n File "/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py", line 113, in \n \_ansiballz\_main()\n File "/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py", line 105, in \_ansiballz\_main\n invoke\_module(zipped\_mod, temp\_path, ANSIBALLZ\_PARAMS)\n File "/root/.ansible/tmp/ansible-tmp-1548834885.34-267057542623206/AnsiballZ\_ios\_config.py", line 48, in invoke\_module\n imp.load\_module(‘ **main** ’, mod, module, MOD\_DESC)\n File "/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py", line 541, in \n File "/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py", line 472, in main\n File "/tmp/ansible\_ios\_config\_payload\_5TvH1X/ **main**.py", line 333, in edit\_config\_or\_macro\n File "/tmp/ansible\_ios\_config\_payload\_5TvH1X/ansible\_ios\_config\_payload.zip/ansible/module\_utils/connection.py", line 173, in **rpc** \nansible.module\_utils.connection.ConnectionError: operation requires privilege escalation\n”,  
“module\_stdout”: “”,  
“msg”: “MODULE FAILURE\nSee stdout/stderr for the exact error”,  
“rc”: 1  
}  
`

---

<div class="post-metadata">

**Author:** ![Krisztian\_Toth](https://avatars.discourse-cdn.com/v4/letter/k/2acd7d/32.png) [@Krisztian\_Toth](https://forum.ansible.com/u/Krisztian_Toth)\
**Post date:** [January 30, 2019, 10:55am UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544/4 "2019-01-30T10:55:09Z")

</div>

Hello,

You should try, what the documentation recommends:  
"Starting with Ansible 2.5 we recommend using `"connection: network_cli"` and “`become: yes"` with `"become_pass"`”

From the error, that is clear you have privilege escalation problem:  
" `ansible.module_utils.connection.ConnectionError: operation requires privilege escalation` "

Other deprecated features are used like “provider” and “authorize”.  
See [here](https://docs.ansible.com/ansible/latest/modules/ios_command_module.html).

Bye,

Krisztian

Jean berjonneau \<[jin.berjonneau@gmail.com](mailto:jin.berjonneau@gmail.com)\> ezt írta (időpont: 2019. jan. 30., Sze, 8:59):

---

<div class="post-metadata">

**Author:** ![Jean\_berjonneau](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@Jean\_berjonneau](https://forum.ansible.com/u/Jean_berjonneau)\
**Post date:** [February 12, 2019, 1:18pm UTC](https://forum.ansible.com/t/ansible-save-config-small-business-sg-500/29544/5 "2019-02-12T13:18:12Z")

</div>

Hello,

I finally got the answer after weeks of trying:

`
