# Configuration update failing: understand how to handle

**URL:** <https://forum.ansible.com/t/configuration-update-failing-understand-how-to-handle/25021>\
**Category:** Ansible Developer\
**Created:** [July 19, 2017, 8:58pm UTC](https://forum.ansible.com/t/configuration-update-failing-understand-how-to-handle/25021 "2017-07-19T20:58:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gavin\_McKee](https://avatars.discourse-cdn.com/v4/letter/g/7993a0/32.png) [@Gavin\_McKee](https://forum.ansible.com/u/Gavin_McKee)\
**Post date:** [July 19, 2017, 8:58pm UTC](https://forum.ansible.com/t/configuration-update-failing-understand-how-to-handle/25021/1 "2017-07-19T20:58:25Z")

</div>

Hi,

I’m trying to work around a failure.

I generate a config using a Jina template. I’m trying to handle the case where I have a possible weird community name like TEST

snmp-server host 4.4.4.4 traps version 2c publ1cr0  
snmp-server host 4.4.4.4 traps version 2c publ1cr0  
snmp-server host 3.3.3.3 use-vrf management  
snmp-server host 3.3.3.3 traps version 2c publ1cr0  
snmp-server host 2.2.2.2 use-vrf management  
snmp-server host 2.2.2.2 traps version 2c publ1cr0  
**snmp-server host 1.1.1.1 traps version 2c TEST**