community.network.ce_vxlan_tunnel – Manages VXLAN tunnel configuration on HUAWEI CloudEngine devices.
Note
This plugin is part of the community.network collection (version 3.0.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 community.network
.
To use it in a playbook, specify: community.network.ce_vxlan_tunnel
.
Synopsis
This module offers the ability to set the VNI and mapped to the BD, and configure an ingress replication list on HUAWEI CloudEngine devices.
Parameters
Parameter |
Comments |
---|---|
Specifies a bridge domain ID. The value is an integer ranging from 1 to 16777215. |
|
Specifies the working mode of an NVE interface. Choices:
|
|
Specifies the number of an NVE interface. The value ranges from 1 to 2. |
|
Specifies the IP address of a remote VXLAN tunnel endpoints (VTEP). The value is in dotted decimal notation. |
|
The operation type of routing protocol. Choices:
|
|
Specifies an IP address for a source VTEP. The value is in dotted decimal notation. |
|
Manage the state of the resource. Choices:
|
|
Specifies a VXLAN network identifier (VNI) ID. The value is an integer ranging from 1 to 16000000. |
Notes
Note
This module requires the netconf system service be enabled on the remote device being managed.
Recommended connection is
netconf
.This module also works with
local
connections for legacy playbooks.
Examples
- name: Vxlan tunnel module test
hosts: ce128
connection: local
gather_facts: no
vars:
cli:
host: "{{ inventory_hostname }}"
port: "{{ ansible_ssh_port }}"
username: "{{ username }}"
password: "{{ password }}"
transport: cli
tasks:
- name: Make sure nve_name is exist, ensure vni_id and protocol_type is configured on Nve1 interface.
community.network.ce_vxlan_tunnel:
nve_name: Nve1
vni_id: 100
protocol_type: bgp
state: present
provider: "{{ cli }}"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
check to see if a change was made on the device Returned: always Sample: true |
|
k/v pairs of configuration after module execution Returned: always Sample: {“nve_interface_name\””: “Nve1”, “nve_mode\””: “mode-l3”, “source_ip”: “0.0.0.0”} |
|
k/v pairs of existing rollback Returned: always Sample: {“nve_interface_name\””: “Nve1”, “nve_mode\””: “mode-l3”, “source_ip”: “0.0.0.0”} |
|
k/v pairs of parameters passed into module Returned: always Sample: {“nve_interface_name\””: “Nve1”, “nve_mode\””: “mode-l2”, “source_ip”: “0.0.0.0”} |
|
command sent to the device Returned: always Sample: [“interface Nve1”, “mode l3”] |
Authors
Li Yanfeng (@QijunPan)