Ansible - Unable to set Third Party VPN Peer.

NeilB
Getting noticed

Ansible - Unable to set Third Party VPN Peer.

Hi,

I'm trying to set a Third Party VPN Peer using cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers: but getting the below error.

 

NoneType: None
fatal: [localhost]: FAILED! => {
"changed": false,
"msg": "Object does not exists, plugin only has update"

 

Sample Playbook

 

---
  - name: Set Third Party VPN
    hosts: localhost
    gather_facts: false
    tasks:

      - name: Set Third Party VPN
        cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers:
          state: present
          organizationId: XXXX
          peers:
            - ikeVersion: '2'
              ipsecPolicies:
                childAuthAlgo:
                  - sha256
                childCipherAlgo:
                  - aes256
                childLifetime: 28800
                childPfsGroup:
                  - group14
                ikeAuthAlgo:
                  - sha256
                ikeCipherAlgo:
                  - aes256
                ikeDiffieHellmanGroup:
                  - group14
                ikeLifetime: 28800
                ikePrfAlgo:
                  - prfsha256
              name: TEST
              networkTags:
                - all
              privateSubnets:
                - 192.168.1.0/24
              publicIp: 123.123.123.1
              secret: Sample_Password

 
I have raised this on GitHub already as Issue #125

Any help gratefully appreciated.

Cheers
N

1 Reply 1
alemabrahao
Kind of a big deal
Kind of a big deal

The cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers module does not support creating new VPN peers from scratch. It only supports updating the entire list of third-party VPN peers for an organization.

 

 

cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers module – Resource module for organizat...

 

 

To use this module successfully, you must First retrieve the current list of VPN peers using the cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers_info module. Them append your new peer to that list, and use the update module to push the full list (including the new peer) back to Meraki.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Get notified when there are additional replies to this discussion.