check_point.mgmt.cp_mgmt_vpn_community_star module – Manages vpn-community-star objects on Check Point over Web Services API
Note
This module is part of the check_point.mgmt collection (version 6.5.0).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install check_point.mgmt.
To use it in a playbook, specify: check_point.mgmt.cp_mgmt_vpn_community_star.
New in check_point.mgmt 1.0.0
Synopsis
- Manages vpn-community-star objects on Check Point devices including creating, updating and removing objects. 
- All operations are performed over Web Services API. 
- Available from R80 management version. 
Parameters
| Parameter | Comments | 
|---|---|
| Advanced properties. Available from R82 JHF management version. | |
| Indicates whether to support IP compression. Choices: 
 | |
| Indicates whether to use aggressive mode. Choices: 
 | |
| Publish the current session if changes have been performed after task completes. Choices: 
 | |
| Collection of center VPN Gateway and VPN Device objects identified by the name or UID. | |
| Color of the object. Should be one of existing colors. Choices: 
 | |
| Comments string. | |
| The level of detail for some of the fields in the response can vary from showing only the UID value of the object to a fully detailed representation of the object. Choices: 
 | |
| Indicates whether to disable NAT inside the VPN Community. Available from R82 JHF management version. Choices: 
 | |
| Indicates on which gateways to disable NAT inside the VPN Community. Available from R82 JHF management version. Choices: 
 | |
| Encrypted traffic settings. Available from R82 JHF management version. | |
| Indicates on which community members to accept all encrypted traffic. Choices: 
 | |
| Indicates whether to accept all encrypted traffic. Choices: 
 | |
| The encryption method to be used. Available from R80.10 management version. Choices: 
 | |
| The encryption suite to be used. Available from R80.10 management version. Choices: 
 | |
| Collection of services that are excluded from the community identified by the name or UID.<br> Connections with these services will not be encrypted and will not match rules specifying the community in the VPN community. Available from R82 JHF management version. | |
| VPN granular encryption settings. Available from R81 management version. | |
| The encryption method to be used. Choices: 
 | |
| The encryption suite to be used. Choices: 
 | |
| Externally managed or 3rd party gateway identified by name or UID. | |
| Ike Phase 1 settings. Only applicable when the encryption-suite is set to [custom]. | |
| The hash algorithm to be used. Choices: 
 | |
| The Diffie-Hellman group to be used. Choices: 
 | |
| The encryption algorithm to be used. Choices: 
 | |
| Indicates the time interval for IKE phase 1 renegotiation. Available from R81 management version. | |
| Indicates the time unit for [ike-p1-rekey-time-unit] parameter, rounded up to minutes scale. Available from R81 management version. Choices: 
 | |
| Ike Phase 2 settings. Only applicable when the encryption-suite is set to [custom]. | |
| The hash algorithm to be used. Choices: 
 | |
| The encryption algorithm to be used. Choices: 
 | |
| The Diffie-Hellman group to be used. Choices: 
 | |
| Indicates the time interval for IKE phase 2 renegotiation. Available from R81 management version. | |
| Indicates the time unit for [ike-p2-rekey-time-unit] parameter. Available from R81 management version. Choices: 
 | |
| Indicates whether Perfect Forward Secrecy (PFS) is being used for IKE phase 2. Choices: 
 | |
| Internally managed Check Point gateway identified by name or UID, or ‘Any’ for all internal-gateways participants in this community. | |
| Apply changes ignoring errors. You won’t be able to publish such a changes. If ignore-warnings flag was omitted - warnings will also be ignored. Choices: 
 | |
| Apply changes ignoring warnings. Choices: 
 | |
| Ike Phase 1 settings. Only applicable when the encryption-suite is set to [custom]. Available from R80.10 management version. | |
| The hash algorithm to be used. Choices: 
 | |
| The Diffie-Hellman group to be used. Choices: 
 | |
| The encryption algorithm to be used. Choices: 
 | |
| Indicates the time interval for IKE phase 1 renegotiation. Available from R81 management version. | |
| Indicates the time unit for [ike-p1-rekey-time-unit] parameter, rounded up to minutes scale. Available from R81 management version. Choices: 
 | |
| Ike Phase 2 settings. Only applicable when the encryption-suite is set to [custom]. Available from R80.10 management version. | |
| The hash algorithm to be used. Choices: 
 | |
| The encryption algorithm to be used. Choices: 
 | |
| The Diffie-Hellman group to be used. Choices: 
 | |
| Indicates the time interval for IKE phase 2 renegotiation. Available from R81 management version. | |
| Indicates the time unit for [ike-p2-rekey-time-unit] parameter. Available from R81 management version. Choices: 
 | |
| Indicates whether Perfect Forward Secrecy (PFS) is being used for IKE phase 2. Available from R81 management version. Choices: 
 | |
| Multiple Entry Point properties. Available from R82 JHF management version. | |
| Priority rule for all satellite gateways. Relevant only if ‘entry-point-selection-mechanism’ is set to ‘manual’. | |
| Collection of first priority center gateways identified by the name or UID. | |
| Collection of second priority center gateways identified by the name or UID. | |
| Collection of third priority center gateways identified by the name or UID. | |
| Enable center gateways as Multiple Entry Points. Choices: 
 | |
| The method by which the final entry point gateway will be chosen when the chosen mechanism returns more than one optional entry point. Choices: 
 | |
| The method by which the entry point gateway will be chosen from the gateways in the center. Choices: 
 | |
| Exception priority rules for specific satellites gateways. Relevant only if ‘entry-point-selection-mechanism’ is set to ‘manual’. | |
| Collection of first priority center gateways identified by the name or UID. | |
| Collection of satellite gateways to apply priority rules on identified by the name or UID. | |
| Collection of second priority center gateways identified by the name or UID. | |
| Collection of third priority center gateways identified by the name or UID. | |
| Tracking option for the MEP. Choices: 
 | |
| Indicates whether the meshed community is in center. Choices: 
 | |
| Object name. | |
| The Overrides VPN Domains of the participants GWs. Available from R80.40 management version. | |
| Participant gateway in override VPN domain identified by the name or UID. | |
| VPN domain network identified by the name or UID. | |
| Permanent tunnels properties. Available from R82 JHF management version. | |
| List of gateways to set all their tunnels to permanent with specified track options. Will take effect only if set-permanent-tunnels-on is set to all-tunnels-of-specific-gateways. | |
| Gateway to set all is tunnels to permanent with specified track options.<br> Identified by name or UID. | |
| Gateway tunnel down track option. Relevant only if the track-options is set to ‘override track options’. Choices: 
 | |
| Gateway tunnel up track option. Relevant only if the track-options is set to ‘override track options’. Choices: 
 | |
| Indicates whether to use the community track options or to override track options for the permanent tunnels. Choices: 
 | |
| Route Injection Mechanism settings. | |
| Indicates whether to enable automatic Route Injection Mechanism on center gateways. Choices: 
 | |
| Indicates whether to enable automatic Route Injection Mechanism on satellite gateways. Choices: 
 | |
| Indicates whether Route Injection Mechanism is enabled. Choices: 
 | |
| Route injection track method. Choices: 
 | |
| Indicates which tunnels to set as permanent. Choices: 
 | |
| VPN community permanent tunnels down track option. Choices: 
 | |
| Permanent tunnels up track option. Choices: 
 | |
| List of tunnels to set as permanent with specified track options. Will take effect only if set-permanent-tunnels-on is set to specific-tunnels-in-the-community. | |
| First tunnel endpoint (center gateway). Identified by name or UID. | |
| Gateway tunnel down track option. Relevant only if the track-options is set to ‘override track options’. Choices: 
 | |
| Gateway tunnel up track option. Relevant only if the track-options is set to ‘override track options’. Choices: 
 | |
| Second tunnel endpoint (center gateway for meshed VPN community and satellite gateway for star VPN community). Identified by name or UID. | |
| Indicates whether to use the community track options or to override track options for the permanent tunnels. Choices: 
 | |
| VPN Community Routing Mode. Available from R82 JHF management version. Choices: 
 | |
| Collection of Gateway objects representing satellite gateways identified by the name or UID. | |
| Shared secrets for external gateways. Available from R80.10 management version. | |
| External gateway identified by the name or UID. | |
| Shared secret. | |
| State of the access rule (present or absent). Choices: 
 | |
| Collection of tag identifiers. | |
| VPN tunnel sharing option to be used. Available from R81 management version. Choices: 
 | |
| Indicates whether the shared secret should be used for all external gateways. Available from R80.10 management version. Choices: 
 | |
| Version of checkpoint. If not given one, the latest version taken. | |
| Enable VPN routing to satellites. Available from R82 JHF management version. Choices: 
 | |
| Wait for the task to end. Such as publish task. Choices: 
 | |
| How many minutes to wait until throwing a timeout error. Default:  | |
| VPN Community Wire mode properties. Available from R82 JHF management version. | |
| Allow members to route uninspected encrypted traffic in VPN routing configurations. Choices: 
 | |
| Allow uninspected encrypted traffic between Wire mode interfaces of this Community members. Choices: 
 | 
Examples
- name: add-vpn-community-star
  cp_mgmt_vpn_community_star:
    center_gateways: Second_Security_Gateway
    encryption_method: prefer ikev2 but support ikev1
    encryption_suite: custom
    ike_phase_1:
      data_integrity: sha1
      diffie_hellman_group: group 19
      encryption_algorithm: aes-128
    ike_phase_2:
      data_integrity: aes-xcbc
      encryption_algorithm: aes-gcm-128
    name: New_VPN_Community_Star_1
    state: present
- name: set-vpn-community-star
  cp_mgmt_vpn_community_star:
    encryption_method: ikev2 only
    encryption_suite: custom
    ike_phase_1:
      data_integrity: sha1
      diffie_hellman_group: group 19
      encryption_algorithm: aes-128
    ike_phase_2:
      data_integrity: aes-xcbc
      encryption_algorithm: aes-gcm-128
    name: New_VPN_Community_Star_1
    state: present
- name: delete-vpn-community-star
  cp_mgmt_vpn_community_star:
    name: New_VPN_Community_Star_1
    state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| The checkpoint object created or updated. Returned: always, except when deleting the object. | 
