cisco.aci.aci_l3out_logical_node module – Manage Layer 3 Outside (L3Out) logical node profile nodes (l3ext:RsNodeL3OutAtt)
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_logical_node
.
Synopsis
Bind nodes to node profiles on Cisco ACI fabrics.
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 |
|
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 |
|
Name of an existing L3Out. |
|
The loopback IP address. The BGP-EVPN loopback IP address for Infra SR-MPLS L3Outs. A configured loopback address can be removed by passing an empty string (see Examples). |
|
The MPLS transport loopback IP address for Infra SR-MPLS L3Outs. |
|
Existing nodeId. |
|
Name of the 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 |
|
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 |
|
Existing podId. |
|
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 |
|
Router ID in dotted decimal notation. |
|
Configure the router ID as a loopback IP. Choices:
|
|
The Segment ID (SID) Index for Infra SR-MPLS L3Outs. |
|
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:
|
|
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:
|
See Also
See also
- aci_l3out
The official documentation on the aci_l3out module.
- aci_l3out_logical_node_profile
The official documentation on the aci_l3out_logical_node_profile module.
- APIC Management Information Model reference
More information about the internal APIC classes l3ext:RsNodeL3OutAtt
- 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 node to a node profile
cisco.aci.aci_l3out_logical_node:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
pod_id: 1
node_id: 111
router_id: 111.111.111.111
loopback_address: 111.111.111.112
state: present
delegate_to: localhost
- name: Add a node to a infra SR-MPLS l3out node profile
cisco.aci.aci_l3out_logical_node: &aci_infra_node_profile_node
host: apic
username: admin
password: SomeSecretPassword
tenant: infra
l3out: ansible_infra_sr_mpls_l3out
node_profile: ansible_infra_sr_mpls_l3out_node_profile
pod_id: 1
node_id: 113
router_id_as_loopback: 'no'
loopback_address: 50.0.0.1
mpls_transport_loopback_address: 51.0.0.1
sid: 500
delegate_to: localhost
- name: Remove a loopback address from a node in node profile
cisco.aci.aci_l3out_logical_node:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
pod_id: 1
node_id: 111
loopback_address: ""
delegate_to: localhost
- name: Delete a node from a node profile
cisco.aci.aci_l3out_logical_node:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
pod_id: 1
node_id: 111
state: absent
delegate_to: localhost
- name: Query a node
cisco.aci.aci_l3out_logical_node:
host: apic
username: admin
password: SomeSecretPassword
tenant: my_tenant
l3out: my_l3out
node_profile: my_node_profile
pod_id: 1
node_id: 111
state: query
delegate_to: localhost
register: query_result
- name: Query all nodes
cisco.aci.aci_l3out_logical_node:
host: apic
username: admin
password: SomeSecretPassword
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: |