Note
This plugin is part of the cisco.aci collection (version 2.1.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_l3out_static_routes
.
Parameter | Choices/Defaults | Comments |
---|---|---|
annotation string | User-defined string for annotating an object. If the value is not specified in the task, the value of environment variable ACI_ANNOTATION will be used instead. | |
bfd string |
| Determines if bfd is required for route control. The APIC defaults to null when unset during creation. |
certificate_name string | The X.509 certificate name attached to the APIC AAA user used for signature-based authentication. If a private_key filename was provided, this defaults to the private_key basename, without extension.If PEM-formatted content was provided for private_key , this defaults to the username value.If the value is not specified in the task, the value of environment variable ACI_CERTIFICATE_NAME will be used instead.aliases: cert_name | |
description string | The description for the static routes. aliases: descr | |
host string / required | 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 ACI_HOST will be used instead.aliases: hostname | |
l3out string | Name of an existing L3Out. aliases: l3out_name | |
logical_node string | Name of an existing logical node profile. aliases: node_profile, node_profile_name | |
name_alias string | The alias for the current object. This relates to the nameAlias field in ACI. | |
node_id integer | Existing nodeId. | |
output_level string |
| Influence the output of this ACI module. normal means the standard output, incl. current dictinfo adds informational output, incl. previous , proposed and sent dictsdebug adds debugging output, incl. filter_string , method , response , status and url informationIf the value is not specified in the task, the value of environment variable ACI_OUTPUT_LEVEL will be used instead. |
output_path string | 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 ACI_OUTPUT_PATH will be used instead. | |
owner_key string | 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 ACI_OWNER_KEY will be used instead. | |
owner_tag string | 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 ACI_OWNER_TAG will be used instead. | |
password string | The password to use for authentication. This option is mutual exclusive with private_key . If private_key is provided too, it will be used instead.If the value is not specified in the task, the value of environment variables ACI_PASSWORD or ANSIBLE_NET_PASSWORD will be used instead. | |
pod_id integer | Existing podId. | |
port integer | Port number to be used for REST connection. The default value depends on parameter use_ssl .If the value is not specified in the task, the value of environment variable ACI_PORT will be used instead. | |
preference integer | Administrative preference value for the route. | |
prefix string | Configure IP and next hop IP for the routed outside network. aliases: route | |
private_key string | Either a PEM-formatted private key file or the private key content used for signature-based authentication. This value also influences the default certificate_name that is used.This option is mutual exclusive with password . If password is provided too, it will be ignored.If the value is not specified in the task, the value of environment variable ACI_PRIVATE_KEY or ANSIBLE_NET_SSH_KEYFILE will be used instead.aliases: cert_key | |
state string |
| Use present or absent for adding or removing.Use query for listing an object or multiple objects. |
tenant string | Name of an existing tenant. aliases: tenant_name | |
timeout integer | Default: 30 | The socket level timeout in seconds. If the value is not specified in the task, the value of environment variable ACI_TIMEOUT will be used instead. |
track_policy string | Relation definition for static route to TrackList. | |
use_proxy boolean |
| If no , it will not use a proxy, even if one is defined in an environment variable on the target hosts.If the value is not specified in the task, the value of environment variable ACI_USE_PROXY will be used instead. |
use_ssl boolean |
| If no , an HTTP connection will be used instead of the default HTTPS connection.If the value is not specified in the task, the value of environment variable ACI_USE_SSL will be used instead. |
username string | Default: "admin" | The username to use for authentication. If the value is not specified in the task, the value of environment variables ACI_USERNAME or ANSIBLE_NET_USERNAME will be used instead.aliases: user |
validate_certs boolean |
| If no , SSL certificates will not be validated.This should only set to no when used on personally controlled sites using self-signed certificates.If the value is not specified in the task, the value of environment variable ACI_VALIDATE_CERTS will be used instead. |
Note
tenant
, l3out
, logical_node
, fabric_node
and prefix
used must exist before using this module in your playbook. The cisco.aci.aci_tenant and cisco.aci.aci_l3out modules can be used for this.See also
The official documentation on the cisco.aci.aci_tenant module.
The official documentation on the cisco.aci.aci_l3out module.
More information about the internal APIC class l3ext:Out.
Detailed information on how to manage your ACI infrastructure using Ansible.
Detailed guide on how to write your own Cisco ACI modules to contribute.
- name: Create static routes cisco.aci.aci_l3out_static_routes: host: apic username: admin password: SomeSecretPassword tenant: tenantName l3out: l3out logical_node: nodeName node_id: 101 pod_id: 1 prefix: 10.10.0.0/16 delegate_to: localhost - name: Delete static routes cisco.aci.aci_l3out_static_routes: host: apic username: admin password: SomeSecretPassword tenant: tenantName l3out: l3out logical_node: nodeName node_id: 101 pod_id: 1 prefix: 10.10.0.0/16 delegate_to: localhost - name: Query for a specific MO under l3out cisco.aci.aci_l3out_static_routes: host: apic username: admin password: SomeSecretPassword tenant: tenantName l3out: l3out logical_node: nodeName node_id: 101 pod_id: 1 prefix: 10.10.0.0/16 delegate_to: localhost - name: Query for all static routes cisco.aci.aci_l3out_static_routes: host: apic username: admin password: SomeSecretPassword tenant: production state: query delegate_to: localhost register: query_result
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description |
---|---|---|
current list / elements=string | success | The existing configuration from the APIC after the module has finished Sample: [{'fvTenant': {'attributes': {'descr': 'Production environment', 'dn': 'uni/tn-production', 'name': 'production', 'nameAlias': '', 'ownerKey': '', 'ownerTag': ''}}}] |
error dictionary | failure | The error information as returned from the APIC Sample: {'code': '122', 'text': 'unknown managed object class foo'} |
filter_string string | failure or debug | The filter string used for the request Sample: ?rsp-prop-include=config-only |
method string | failure or debug | The HTTP method used for the request to the APIC Sample: POST |
previous list / elements=string | info | The original configuration from the APIC before the module has started Sample: [{'fvTenant': {'attributes': {'descr': 'Production', 'dn': 'uni/tn-production', 'name': 'production', 'nameAlias': '', 'ownerKey': '', 'ownerTag': ''}}}] |
proposed dictionary | info | The assembled configuration from the user-provided parameters Sample: {'fvTenant': {'attributes': {'descr': 'Production environment', 'name': 'production'}}} |
raw string | parse error | The raw output returned by the APIC REST API (xml or json) Sample: <?xml version="1.0" encoding="UTF-8"?><imdata totalCount="1"><error code="122" text="unknown managed object class foo"/></imdata> |
response string | failure or debug | The HTTP response from the APIC Sample: OK (30 bytes) |
sent list / elements=string | info | The actual/minimal configuration pushed to the APIC Sample: {'fvTenant': {'attributes': {'descr': 'Production environment'}}} |
status integer | failure or debug | The HTTP status from the APIC Sample: 200 |
url string | failure or debug | The HTTP url used for the request to the APIC Sample: https://10.11.12.13/api/mo/uni/tn-production.json |
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/latest/collections/cisco/aci/aci_l3out_static_routes_module.html