cisco.aci.aci_l4l7_device module – Manage L4-L7 Devices (vns:LDevVip)
Note
This module is part of the cisco.aci collection (version 2.12.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 cisco.aci
.
To use it in a playbook, specify: cisco.aci.aci_l4l7_device
.
New in cisco.aci 2.12.0
Synopsis
Manage Layer 4 to Layer 7 (L4-L7) Devices.
Parameters
Parameter |
Comments |
---|---|
The active active mode on the device. This is only applicable when The APIC defaults to false when unset during creation. Choices:
|
|
User-defined string for annotating an object. If the value is not specified in the task, the value of environment variable If the value is not specified in the task and environment variable Default: |
|
The X.509 certificate name attached to the APIC AAA user used for signature-based authentication. If a If PEM-formatted content was provided for If the value is not specified in the task, the value of environment variable |
|
Is device Single or Multi context aware. The APIC defaults to Choices:
|
|
The type of the device. The APIC defaults to Choices:
|
|
The domain to bind to the device. The type of domain is controlled by the device_type setting. |
|
The function type of the device. The APIC defaults to Choices:
|
|
IP Address or hostname of APIC resolvable by Ansible control host. If the value is not specified in the task, the value of environment variable |
|
Is the device a managed device. The APIC defaults to true when unset during creation. Choices:
|
|
The name of the L4-L7 device. |
|
Influence the output of this ACI module.
If the value is not specified in the task, the value of environment variable Choices:
|
|
Path to a file that will be used to dump the ACI JSON configuration objects generated by the module. If the value is not specified in the task, the value of environment variable |
|
The password to use for authentication. This option is mutual exclusive with If the value is not specified in the task, the value of environment variables |
|
Port number to be used for REST connection. The default value depends on parameter If the value is not specified in the task, the value of environment variable |
|
Either a PEM-formatted private key file or the private key content used for signature-based authentication. This value also influences the default This option is mutual exclusive with If the value is not specified in the task, the value of environment variable |
|
Enable promiscuous mode. The APIC defaults to false when unset during creation. Choices:
|
|
The service type running on the device. The APIC defaults to Choices:
|
|
Use Use Choices:
|
|
If If the value is not specified in the task, the value of environment variable The default value is WARNING - This causes the previous return value to be empty. The previous state of the object will not be checked and the POST update will contain all properties. Choices:
|
|
If If the value is not specified in the task, the value of environment variable The default value is WARNING - This causes the current return value to be set to the proposed value. The current object including default values will be unverifiable in a single task. Choices:
|
|
The name of an existing tenant. |
|
The socket level timeout in seconds. If the value is not specified in the task, the value of environment variable The default value is 30. |
|
Enable trunking. The APIC defaults to false when unset during creation. Choices:
|
|
If If the value is not specified in the task, the value of environment variable The default value is true. Choices:
|
|
If If the value is not specified in the task, the value of environment variable The default value is true when the connection is local. Choices:
|
|
The username to use for authentication. If the value is not specified in the task, the value of environment variables The default value is admin. |
|
If This should only set to If the value is not specified in the task, the value of environment variable The default value is true. Choices:
|
Notes
Note
The tenant must exist before using this module in your playbook. The cisco.aci.aci_tenant modules can be used for this.
See Also
See also
- cisco.aci.aci_tenant
Manage tenants (fv:Tenant).
- APIC Management Information Model reference
More information about the internal APIC class vns:LDevVip
- Cisco ACI Guide
Detailed information on how to manage your ACI infrastructure using Ansible.
- Developing Cisco ACI modules
Detailed guide on how to write your own Cisco ACI modules to contribute.
Examples
- name: Add a new L4-L7 device
cisco.aci.aci_l4l7_device:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
name: my_device
state: present
domain: phys
function_type: go_to
context_aware: single
managed: false
device_type: physical
service_type: adc
trunking: false
promiscuous_mode: true
delegate_to: localhost
- name: Query an L4-L7 device
cisco.aci.aci_l4l7_device:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
name: my_device
state: query
delegate_to: localhost
register: query_result
- name: Query all L4-L7 devices
cisco.aci.aci_l4l7_device:
host: apic
username: admin
password: SomeSecretPassword
state: query
delegate_to: localhost
register: query_result
- name: Delete an existing L4-L7 device
cisco.aci.aci_l4l7_device:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
name: my_device
state: absent
delegate_to: localhost
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The existing configuration from the APIC after the module has finished Returned: success Sample: |
|
The error information as returned from the APIC Returned: failure Sample: |
|
The filter string used for the request Returned: failure or debug Sample: |
|
The HTTP method used for the request to the APIC Returned: failure or debug Sample: |
|
The original configuration from the APIC before the module has started Returned: info Sample: |
|
The assembled configuration from the user-provided parameters Returned: info Sample: |
|
The raw output returned by the APIC REST API (xml or json) Returned: parse error Sample: |
|
The HTTP response from the APIC Returned: failure or debug Sample: |
|
The actual/minimal configuration pushed to the APIC Returned: info Sample: |
|
The HTTP status from the APIC Returned: failure or debug Sample: |
|
The HTTP url used for the request to the APIC Returned: failure or debug Sample: |