cisco.mso.ndo_l3out_node_static_route module – Manage L3Out Node Static Routes on Cisco Nexus Dashboard Orchestrator (NDO).
Note
This module is part of the cisco.mso collection (version 2.11.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_l3out_node_static_route
.
New in cisco.mso 2.11.0
Synopsis
Manage L3Out Node Static Routes on Cisco Nexus Dashboard Orchestrator (NDO).
This module is only supported on ND v3.1 (NDO v4.3) 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 administrative distance of the static route. The value must be in the range 1 - 255. Defaults to |
|
Enable BFD tracking for the static route. Defaults to Choices:
|
|
The description of the static route. 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 name of the L3Out. This parameter or |
|
The UUID of the L3Out. This parameter or |
|
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 |
|
Create a static route to Null0 interface. This is used to drop traffic for the specified prefix. Defaults to Choices:
|
|
The ID of the node. |
|
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 |
|
The pod ID of the node (border leaf switch). |
|
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 prefix of the static route. |
|
Determines the desired state of the resource. Use Use Use Choices:
|
|
The name of the template. The template must be an L3Out template. This parameter or |
|
The ID of the L3Out 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 |
|
The track policy to be used. Providing an empty dictionary |
|
The name of the track policy. |
|
The name of the template that contains the track policy. This parameter or |
|
The ID of the template that contains the track policy. This parameter or |
|
The UUID of the track policy to be used. Providing an empty string |
|
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
template
ortemplate_id
must exist before using this module in your playbook. The cisco.mso.ndo_template module can be used for this.The
l3out
orl3out_uuid
must exist before using this module in your playbook. The cisco.mso.ndo_l3out_template module can be used for this.The
track_policy
ortrack_policy_uuid
must exist before using this module in your playbook. The cisco.mso.ndo_ipsla_track_list module can be used for this.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_l3out_template
Manage L3Outs on Cisco Nexus Dashboard Orchestrator (NDO).
- cisco.mso.ndo_ipsla_track_list
Manage IPSLA Track Lists on Cisco Nexus Dashboard Orchestrator (NDO).
Examples
- name: Create a L3Out Node Static Route
cisco.mso.ndo_l3out_node_static_route:
host: mso_host
username: admin
password: SomeSecretPassword
template: l3out_template
l3out: l3out_name
pod_id: 1
node_id: 101
prefix: 10.0.0.0/24
state: present
- name: Update an existing L3Out Node Static Route
cisco.mso.ndo_l3out_node_static_route:
host: mso_host
username: admin
password: SomeSecretPassword
template_id: "{{ l3out_template.current.templateId }}"
l3out_uuid: "{{ l3out.current.uuid }}"
pod_id: 1
node_id: 101
prefix: 10.0.0.0/24
description: "Static route for 10.0.0.0/24"
administrative_distance: 10
bfd_tracking: true
next_hop_null: true
track_policy:
name: "track_policy_name"
template: "track_policy_template"
state: present
- name: Query an existing L3Out Node Static Route
cisco.mso.ndo_l3out_node_static_route:
host: mso_host
username: admin
password: SomeSecretPassword
template: l3out_template
l3out: l3out_name
pod_id: 1
node_id: 101
prefix: 10.0.0.0/24
state: query
register: query_with_name
- name: Query all existing L3Out Node Static Routes in a L3Out Node
cisco.mso.ndo_l3out_node_static_route:
host: mso_host
username: admin
password: SomeSecretPassword
template: l3out_template
l3out: l3out_name
pod_id: 1
node_id: 101
state: query
- name: Delete an existing L3Out Node Static Route
cisco.mso.ndo_l3out_node_static_route:
host: mso_host
username: admin
password: SomeSecretPassword
template: l3out_template
l3out: l3out_name
pod_id: 1
node_id: 101
prefix: 10.0.0.0/24
state: absent