nxos_interface_ospf - Manages configuration of an OSPF interface instance.¶
New in version 2.2.
Parameters¶
Parameter | Choices/Defaults | Comments | |
---|---|---|---|
area
required |
Ospf area associated with this cisco_interface_ospf instance. Valid values are a string, formatted as an IP address (i.e. "0.0.0.0") or as an integer.
|
||
cost |
The cost associated with this cisco_interface_ospf instance.
|
||
dead_interval |
Time interval an ospf neighbor waits for a hello packet before tearing down adjacencies. Valid values are an integer or the keyword 'default'.
|
||
hello_interval |
Time between sending successive hello packets. Valid values are an integer or the keyword 'default'.
|
||
interface
required |
Name of this cisco_interface resource. Valid value is a string.
|
||
message_digest
bool |
|
Enables or disables the usage of message digest authentication.
|
|
message_digest_algorithm_type |
|
Algorithm used for authentication among neighboring routers within an area. Valid values are 'md5' and 'default'.
|
|
message_digest_encryption_type |
|
Specifies the scheme used for encrypting message_digest_password. Valid values are '3des' or 'cisco_type_7' encryption or 'default'.
|
|
message_digest_key_id |
Md5 authentication key-id associated with the ospf instance. If this is present, message_digest_encryption_type, message_digest_algorithm_type and message_digest_password are mandatory. Valid value is an integer and 'default'.
|
||
message_digest_password |
Specifies the message_digest password. Valid value is a string.
|
||
ospf
required |
Name of the ospf instance.
|
||
passive_interface
bool |
|
Setting to true will prevent this interface from receiving HELLO packets.
|
|
provider |
Deprecated
Starting with Ansible 2.5 we recommend using
connection: network_cli .This option is only required if you are using NX-API.
For more information please see the NXOS Platform Options guide.
A dict object containing connection details.
|
||
username |
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
ANSIBLE_NET_USERNAME will be used instead. |
||
authorize
bool (added in 2.5.3) |
|
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
ANSIBLE_NET_AUTHORIZE will be used instead. |
|
ssh_keyfile |
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
ANSIBLE_NET_SSH_KEYFILE will be used instead. |
||
use_proxy
bool (added in 2.5) |
|
If
no , the environment variables http_proxy and https_proxy will be ignored. |
|
auth_pass
(added in 2.5.3) |
Default: none
|
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
ANSIBLE_NET_AUTH_PASS will be used instead. |
|
host
required |
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.
|
||
timeout
(added in 2.3) |
Default: 10
|
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).
|
|
use_ssl
bool |
|
Configures the transport to use SSL if set to true only when the
transport=nxapi , otherwise this value is ignored. |
|
password |
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
ANSIBLE_NET_PASSWORD will be used instead. |
||
validate_certs
bool |
|
If
no , SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. If the transport argument is not nxapi, this value is ignored. |
|
port |
Default: 0 (use common port)
|
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).
|
|
transport
required |
Default: cli
|
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.
|
|
state |
|
Determines whether the config should be present or not on the device.
|
Notes¶
Note
- Tested against NXOSv 7.3.(0)D1(1) on VIRL
- Default, where supported, restores params default value.
- To remove an existing authentication configuration you should use
message_digest_key_id=default
plus all other options matching their existing values. state=absent
removes the whole OSPF interface configuration.- 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.
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description |
---|---|---|
commands
list
|
always |
commands sent to the device
Sample:
['interface Ethernet1/32', 'ip router ospf 1 area 0.0.0.1']
|
Status¶
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
Maintenance¶
This module is flagged as network which means that it is maintained by the Ansible Network Team. See Module Maintenance & Support for more info.
For a list of other modules that are also maintained by the Ansible Network Team, see here.
Support¶
For more information about Red Hat’s support of this module, please refer to this Knowledge Base article
Author¶
- Gabriele Gerbino (@GGabriele)
Hint
If you notice any issues in this documentation you can edit this document to improve it.