cisco.nxos.nxos_ntp – Manages core NTP configuration.
Note
This plugin is part of the cisco.nxos collection (version 2.8.2).
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.nxos
.
To use it in a playbook, specify: cisco.nxos.nxos_ntp
.
New in version 1.0.0: of cisco.nxos
DEPRECATED
- Removed in
major release after 2024-01-01
- Why
Updated module released with more functionality.
- Alternative
nxos_ntp_global
Parameters
Parameter |
Comments |
---|---|
Authentication key identifier to use with given NTP server or peer or keyword ‘default’. |
|
Network address of NTP peer. |
|
Makes given NTP server or peer the preferred NTP server or peer for the device. Choices:
|
|
Deprecated Starting with Ansible 2.5 we recommend using Starting with Ansible 2.6 we recommend using This option will be removed in a release after 2022-06-01. For more information please see the https://docs.ansible.com/ansible/latest/network/user_guide/platform_nxos.html. A dict object containing connection details. |
|
Specifies the password to use if required to enter privileged mode on the remote device. If authorize is false, then this argument does nothing. If the value is not specified in the task, the value of environment variable |
|
Instructs the module to enter privileged mode on the remote device before sending any commands. If not specified, the device will attempt to execute all commands in non-privileged mode. If the value is not specified in the task, the value of environment variable Choices:
|
|
Specifies the DNS host name or address for connecting to the remote device over the specified transport. The value of host is used as the destination address for the transport. |
|
Specifies the password to use to authenticate the connection to the remote device. This is a common argument used for either cli or nxapi transports. If the value is not specified in the task, the value of environment variable |
|
Specifies the port to use when building the connection to the remote device. This value applies to either cli or nxapi. The port value will default to the appropriate transport common port if none is provided in the task. (cli=22, http=80, https=443). |
|
Specifies the SSH key to use to authenticate the connection to the remote device. This argument is only used for the cli transport. If the value is not specified in the task, the value of environment variable |
|
Specifies the timeout in seconds for communicating with the network device for either connecting or sending commands. If the timeout is exceeded before the operation is completed, the module will error. NX-API can be slow to return on long-running commands (sh mac, sh bgp, etc). |
|
Configures the transport connection to use when connecting to the remote device. The transport argument supports connectivity to the device over cli (ssh) or nxapi. Choices:
|
|
If Choices:
|
|
Configures the transport to use SSL if set to Choices:
|
|
Configures the username to use to authenticate the connection to the remote device. This value is used to authenticate either the CLI login or the nxapi authentication depending on which transport is used. If the value is not specified in the task, the value of environment variable |
|
If Choices:
|
|
Network address of NTP server. |
|
Local source address from which NTP messages are sent or keyword ‘default’. |
|
Local source interface from which NTP messages are sent. Must be fully qualified interface name or keyword ‘default’ |
|
Manage the state of the resource. Choices:
|
|
Makes the device communicate with the given NTP server or peer over a specific VRF or keyword ‘default’. |
Notes
Note
Limited Support for Cisco MDS
For information on using CLI and NX-API see the NXOS Platform Options guide
For more information on using Ansible to manage network devices see the Ansible Network Guide
For more information on using Ansible to manage Cisco devices see the Cisco integration page.
Examples
# Set NTP Server with parameters
- cisco.nxos.nxos_ntp:
server: 1.2.3.4
key_id: 32
prefer: enabled
host: '{{ inventory_hostname }}'
username: '{{ un }}'
password: '{{ pwd }}'
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
check to see if a change was made on the device Returned: always Sample: true |
|
k/v pairs of ntp info after module execution Returned: always Sample: {“address”: “192.0.2.2”, “key_id”: “48”, “peer_type”: “server”, “prefer”: “enabled”, “source”: “192.0.2.3”, “source_type”: “source”} |
|
k/v pairs of existing ntp server/peer Returned: always Sample: {“address”: “192.0.2.2”, “key_id”: “32”, “peer_type”: “server”, “prefer”: “enabled”, “source”: “ethernet2/1”, “source_type”: “source-interface”} |
|
k/v pairs of parameters passed into module Returned: always Sample: {“address”: “192.0.2.2”, “key_id”: “48”, “peer_type”: “server”, “prefer”: “enabled”, “source”: “192.0.2.3”, “source_type”: “source”} |
|
command sent to the device Returned: always Sample: [“ntp server 192.0.2.2 prefer key 48”, “no ntp source-interface ethernet2/1”, “ntp source 192.0.2.3”] |
Status
This module will be removed in a major release after 2024-01-01. [deprecated]
For more information see DEPRECATED.
Authors
Jason Edelman (@jedelman8)