cisco.aci.aci_l3out_dhcp_relay_label module – Manage Layer 3 Outside (L3Out) DHCP Relay Label (dhcp:Lbl)
Note
This module is part of the cisco.aci collection (version 2.10.1).
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_l3out_dhcp_relay_label
.
Synopsis
Manage DHCP Relay Labels for L3Out Logical Interface Profiles on Cisco ACI fabrics.
A DHCP Relay Label contains the name of an existing DHCP Relay Policy for the label, the scope, and a DHCP Option Policy.
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 description of the DHCP Relay Label. |
|
The name of an existing DHCP Option Policy to be associated with the DCHP Relay Policy. The DHCP option policy supplies DHCP clients with configuration parameters such as domain, nameserver, and subnet router addresses. Passing an empty string will delete the current linked DHCP Option Policy. However, this will associate the DHCP Relay Label to the default DHCP Option Policy from the common Tenant. |
|
The name/label of an existing DHCP Relay Policy. |
|
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 interface profile. |
|
The name of an existing L3Out. |
|
The name of an existing node profile. |
|
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 |
|
User-defined string for the ownerKey attribute of an ACI object. This attribute represents a key for enabling clients to own their data for entity correlation. If the value is not specified in the task, the value of environment variable |
|
User-defined string for the ownerTag attribute of an ACI object. This attribute represents a tag for enabling clients to add their own data. For example, to indicate who created this object. 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 |
|
The scope is the owner of the relay server. 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. |
|
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
,l3out
,node_profile
,interface_profile
andrelay_policy
must exist before using this module in your playbook. The cisco.aci.aci_tenant, cisco.aci.aci_l3out, cisco.aci.aci_l3out_logical_node_profile, cisco.aci.aci_l3out_logical_interface_profile and cisco.aci.aci_dhcp_relay can be used for this.If
dhcp_option_policy
is used, it must exist before using this module in your playbook. The cisco.aci.aci_dhcp_option_policy can be used for this.
See Also
See also
- cisco.aci.aci_tenant
Manage tenants (fv:Tenant).
- cisco.aci.aci_l3out
Manage Layer 3 Outside (L3Out) objects (l3ext:Out).
- cisco.aci.aci_l3out_logical_node_profile
Manage Layer 3 Outside (L3Out) logical node profiles (l3ext:LNodeP).
- cisco.aci.aci_l3out_logical_interface_profile
Manage Layer 3 Outside (L3Out) logical interface profiles (l3ext:LIfP).
- cisco.aci.aci_dhcp_relay
Manage DHCP relay policies (dhcp:RelayP).
- cisco.aci.aci_dhcp_option_policy
Manage DHCP Option Policy (dhcp:OptionPol).
- APIC Management Information Model reference
More information about the internal APIC classes
- 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 L3Out DHCP Relay Label
cisco.aci.aci_l3out_eigrp_interface_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
interface_profile: my_interface_profile
dhcp_relay_label: my_dhcp_relay_label
scope: tenant
dhcp_option_policy: my_dhcp_option_policy
state: present
delegate_to: localhost
- name: Delete an L3Out DHCP Relay Label
cisco.aci.aci_l3out_eigrp_interface_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
interface_profile: my_interface_profile
dhcp_relay_label: my_dhcp_relay_label
state: absent
delegate_to: localhost
- name: Query an L3Out DHCP Relay Label
cisco.aci.aci_l3out_eigrp_interface_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
interface_profile: my_interface_profile
dhcp_relay_label: my_dhcp_relay_label
state: query
delegate_to: localhost
register: query_result
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: |