cisco.aci.aci_l4l7_concrete_interface_attachment module – Manage L4-L7 Concrete Interface Attachment (vns:RsCIfAttN)
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_concrete_interface_attachment.
New in cisco.aci 2.12.0
Synopsis
- Manage Layer 4 to Layer 7 (L4-L7) Concrete Interface Attachment to Logical Interfaces. 
Aliases: aci_l4l7_concrete_interface_attach
Parameters
| Parameter | Comments | 
|---|---|
| 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  | |
| The name of an existing Concrete Device. | |
| The name of an existing Concrete Interface. | |
| 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  | |
| The name of an existing Logical Device. | |
| The name of an existing Logical Interface. | |
| 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  | |
| 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. | |
| 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, logical_device, logical_interface and concrete_device must exist before using this module in your playbook. The cisco.aci.aci_tenant, cisco.aci.aci_l4l7_device, cisco.aci.aci_l4l7_logical_interface and cisco.aci.aci_l4l7_concrete_device modules can be used for this. 
See Also
See also
- cisco.aci.aci_tenant
- Manage tenants (fv:Tenant). 
- cisco.aci.aci_l4l7_device
- Manage L4-L7 Devices (vns:LDevVip). 
- cisco.aci.aci_l4l7_logical_interface
- Manage L4-L7 Logical Interface (vns:LIf). 
- cisco.aci.aci_l4l7_concrete_device
- Manage L4-L7 Concrete Devices (vns:CDev). 
- cisco.aci.aci_l4l7_concrete_interface
- Manage L4-L7 Concrete Interfaces (vns:CIf). 
- APIC Management Information Model reference
- More information about the internal APIC class vns:RsCIfAttN 
- 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 concrete interface attachment
  cisco.aci.aci_l4l7_concrete_interface_attachment:
    host: apic
    username: admin
    password: SomeSecretPassword
    tenant: my_tenant
    device: my_log_device
    logical_interface: my_log_intf
    concrete_device: my_conc_device
    concrete_interface: my_conc_intf
    state: present
  delegate_to: localhost
- name: Query a concrete interface attachment
  cisco.aci.aci_l4l7_concrete_interface_attachment:
    host: apic
    username: admin
    password: SomeSecretPassword
    tenant: my_tenant
    device: my_log_device
    logical_interface: my_log_intf
    concrete_device: my_conc_device
    concrete_interface: my_conc_intf
    state: query
  delegate_to: localhost
  register: query_result
- name: Query all concrete interface attachments
  cisco.aci.aci_l4l7_concrete_interface_attachment:
    host: apic
    username: admin
    password: SomeSecretPassword
  delegate_to: localhost
  register: query_result
- name: Delete a concrete interface attachment
  cisco.aci.aci_l4l7_concrete_interface_attachment:
    host: apic
    username: admin
    password: SomeSecretPassword
    tenant: my_tenant
    device: my_log_device
    logical_interface: my_log_intf
    concrete_device: my_conc_device
    concrete_interface: my_conc_intf
    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:  | 
