cisco.aci.aci_l3out_bgp_protocol_profile module – Manage BGP Protocol Profile (bgp:ProtP)
Note
This module is part of the cisco.aci collection (version 2.8.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_bgp_protocol_profile
.
Synopsis
Manage BGP Protocol Profile for The Logical 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 name of the bgp best path control policy. |
|
The name of an existing bgp timers policy. |
|
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 |
|
The name of an existing L3Out. |
|
The alias for the current object. This relates to the nameAlias field in ACI. |
|
The name of an existing logical 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 |
|
Use Use 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
andnode_profile
used must exist before using this module in your playbook. The cisco.aci.aci_tenant, cisco.aci.aci_l3out and cisco.aci.aci_l3out_logical_node_profile modules can be used for this.If
bgp_timers_policy
and/orbgp_best_path_policy
are used, they must exist before using this module in your playbook. The cisco.aci.aci_bgp_timers_policy and cisco.aci.aci_bgp_best_path_policy modules 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_bgp_timers_policy
Manage BGP timers policy (bgp:CtxPol).
- cisco.aci.aci_bgp_best_path_policy
Manage BGP Best Path policy (bgp:BestPathCtrlPol).
- APIC Management Information Model reference
More information about the internal APIC class bgp:ProtP.
- 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: Create a l3out BGP protocol profile
cisco.aci.l3out_bgp_protocol_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: production
l3out: prod_l3out
node_profile: prod_node_profile
bgp_timers_policy: prod_bgp_timers_policy
bgp_best_path_policy: prod_bgp_best_path_policy
state: present
delegate_to: localhost
- name: Delete a l3out BGP protocol profile
cisco.aci.l3out_bgp_protocol_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: production
l3out: prod_l3out
node_profile: prod_node_profile
state: absent
delegate_to: localhost
- name: Query all l3out BGP protocol profiles
cisco.aci.l3out_bgp_protocol_profile:
host: apic
username: admin
password: SomeSecretPassword
state: query
delegate_to: localhost
register: query_result
- name: Query a specific l3out BGP protocol profile
cisco.aci.l3out_bgp_protocol_profile:
host: apic
username: admin
password: SomeSecretPassword
tenant: production
l3out: prod_l3out
node_profile: prod_node_profile
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: |