Which version of Ansible are you using? Thanks.

That is why I suggest to use plain-text-password-value and not plain-text-password Regards,

Persistent NAT will give you a full cone while the mapping is alive (you can adjust some timers for that). Once the mapping expires, the next session initiated from the internal host could result in a completely different mapping. Here's a really cool write-up: https://www.blackhole-networks.com/SRXNAT/snat_persist.html ...

Hi, thank you for the response. I've tried this approach already, along with just using "plain-text-password". The former produces the same error message as the encrypted-password method, and "plain-text-password" is only meant for CLI changes. ------------------------------ ETHAN JOHNSON -------- ...

Hi, We are trying to set up full-cone NAT on an ISP SRX5K with SPC3, specifically for STUN/P2P applications. From our documenataion, it appears that Junos supports full-cone NAT using Persistent NAT, and also through a combination of Address Pooling Paired (APP), Endpoint-Independent ...

Not sure if you have taken a look at the following KB: https://supportportal.juniper.net/s/article/EX-QFX-How-to-troubleshoot-var-partition-usage-is-high?language=en_US Regards,

Probably it is complaining about encrypted_password ? Perhaps try this approach instead. --- # Playbook to change the password on Juniper Switches - name: Change password on Juniper Switch hosts: Juniper_ex4300 # Switch group from inventory file gather_facts: no # Not needed collections: ...