cisco.mso.ndo_route_map_policy_route_control_context module – Manage Route Map Policy for Route Control Context on Cisco Nexus Dashboard Orchestrator (NDO).
Note
This module is part of the cisco.mso 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.mso.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.mso.ndo_route_map_policy_route_control_context.
New in cisco.mso 2.12.0
Synopsis
Manage Route Map Policy for Route Control Context on Cisco Nexus Dashboard Orchestrator (NDO).
This module is only supported on ND v4.1 and later.
Requirements
The below requirements are needed on the host that executes this module.
Multi Site Orchestrator v2.1 or newer
Parameters
Parameter |
Comments |
|---|---|
The action of the Route Control context. Defaults to Choices:
|
|
The description of the Route Control context. Providing an empty string |
|
IP Address or hostname of the ACI Multi Site Orchestrator host. If the value is not specified in the task, the value of environment variable |
|
The login domain name to use for authentication. The default value is Local. If the value is not specified in the task, the value of environment variable When using a HTTPAPI connection plugin the inventory variable |
|
The list of Match Rule Policy references. Providing an empty list When the The old |
|
The reference of the Match Rule Policy. This parameter can be used instead of |
|
The name of the Match Rule Policy. |
|
The template associated with the Match Rule Policy. This parameter or |
|
The template ID associated with the Match Rule Policy. This parameter or |
|
The UUID of the Match Rule Policy. This parameter can be used instead of |
|
The name of the Route Control context. |
|
The order of the Route Control context. The value must be a number between 0 and 9. Defaults to |
|
Influence the output of this MSO module.
If the value is not specified in the task, the value of environment variable Choices:
|
|
The password to use for authentication. If the value is not specified in the task, the value of environment variables |
|
Port number to be used for the REST connection. The default value depends on parameter `use_ssl`. If the value is not specified in the task, the value of environment variable |
|
The name of the Route Map Policy for Route Control. This parameter or |
|
The UUID of the Route Map Policy for Route Control. This parameter or |
|
The Set Rule Policy reference details for the Route Control context. Providing an empty dictionary |
|
The reference details of the Set Rule Policy. This parameter can be used instead of |
|
The name of the Set Rule Policy. |
|
The template associated with the Set Rule Policy. This parameter or |
|
The template ID associated with the Set Rule Policy. This parameter or |
|
The UUID of the Set Rule Policy. This parameter can be used instead of |
|
Use Use Use Choices:
|
|
The name of the template. The template must be a tenant template. This parameter or |
|
The ID of the tenant template. This parameter or |
|
The socket level timeout in seconds. The default value is 30 seconds. If the value is not specified in the task, the value of environment variable |
|
If If the value is not specified in the task, the value of environment variable The default is Choices:
|
|
If If the value is not specified in the task, the value of environment variable When using a HTTPAPI connection plugin the inventory variable The default is Choices:
|
|
The username to use for authentication. If the value is not specified in the task, the value of environment variables |
|
If This should only set to If the value is not specified in the task, the value of environment variable The default is Choices:
|
Notes
Note
The
templatemust exist before using this module in your playbook. Use cisco.mso.ndo_template to create the Tenant template.The
route_map_policymust exist before using this module in your playbook. Use cisco.mso.ndo_route_map_policy_route_control to create the Route Map Policy for Route Control.The
set_rulemust exist before using it with this module in your playbook. Use cisco.mso.ndo_set_rule_policy to create the Set Rule Policy.The
match_rulesmust exist before using it with this module in your playbook. Use cisco.mso.ndo_match_rule_policy to create the Match Rule Policy.This module was written to support Multi Site Orchestrator v2.1 or newer. Some or all functionality may not work on earlier versions.
See Also
See also
- cisco.mso.ndo_template
Manage Templates on Cisco Nexus Dashboard Orchestrator (NDO).
- cisco.mso.ndo_route_map_policy_route_control
Manage Route Map Policy for Route Control on Cisco Nexus Dashboard Orchestrator (NDO).
- cisco.mso.ndo_set_rule_policy
Manage Tenant Set Rule Policies on Cisco Nexus Dashboard Orchestrator (NDO).
- cisco.mso.ndo_match_rule_policy
Manage Match Rule Policies on Cisco Nexus Dashboard Orchestrator (NDO).
Examples
- name: Add Route Map Policy for Route Control Context
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
name: route_map_policy_context_1
order: 1
set_rule:
uuid: "{{ add_set_rule_policy_1.current.uuid }}"
match_rules:
- uuid: "{{ add_match_rule_policy_1.current.uuid }}"
- reference:
template_id: "{{ add_ansible_tenant_template.current.templateId }}"
name: ansible_match_rule_policy_2
state: present
- name: Update Route Map Policy for Route Control Context
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
name: route_map_policy_context_1
order: 2
set_rule:
reference:
template_id: "{{ add_ansible_tenant_template.current.templateId }}"
name: ansible_set_rule_policy_2
match_rules:
- reference:
template_id: "{{ add_ansible_tenant_template.current.templateId }}"
name: ansible_match_rule_policy_2
state: present
- name: Update and remove Set Rule and Match Rules from Route Map Policy for Route Control Context
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
name: route_map_policy_context_1
order: 2
set_rule: {}
match_rules: []
state: present
- name: Query Route Map Policy for Route Control Context using name
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
name: route_map_policy_context_1
state: query
register: query_one
- name: Query all Route Map Policy for Route Control Context
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
state: query
register: query_one
- name: Delete Route Map Policy for Route Control Context
cisco.mso.ndo_route_map_policy_route_control_context:
host: mso_host
username: admin
password: SomeSecretPassword
template: ansible_tenant_template
route_map_policy: ansible_test_route_map_policy
name: route_map_policy_context_1
state: absent