cisco.nxos.nxos_vpc_interface – Manages interface VPC configuration
Note
This plugin is part of the cisco.nxos collection (version 2.7.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.nxos.
To use it in a playbook, specify: cisco.nxos.nxos_vpc_interface.
New in version 1.0.0: of cisco.nxos
Synopsis
- Manages interface VPC configuration
 
Note
This module has a corresponding action plugin.
Parameters
| Parameter | Choices/Defaults | Comments | |
|---|---|---|---|
|   peer_link    boolean    |   
  |    Set to true/false for peer link config on associated portchannel.   |  |
|   portchannel    string / required    |    Group number of the portchannel that will be configured.   |  ||
|   provider    dictionary    |    Deprecated  Starting with Ansible 2.5 we recommend using   connection: network_cli.Starting with Ansible 2.6 we recommend using   connection: httpapi for NX-API.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.   |  ||
|   auth_pass    string    |    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. |  ||
|   authorize    boolean    |   
  |    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. |  |
|   host    string    |    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.   |  ||
|   password    string    |    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. |  ||
|   port    integer    |    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).   |  ||
|   ssh_keyfile    string    |    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. |  ||
|   timeout    integer    |    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).   |  ||
|   transport    string    |   
  |    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.   |  |
|   use_proxy    boolean    |   
  |    If   no, the environment variables http_proxy and https_proxy will be ignored. |  |
|   use_ssl    boolean    |   
  |    Configures the transport to use SSL if set to   yes only when the transport=nxapi, otherwise this value is ignored. |  |
|   username    string    |    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. |  ||
|   validate_certs    boolean    |   
  |    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. |  |
|   state    string    |   
  |    Manages desired state of the resource.   |  |
|   vpc    string    |    VPC group/id that will be configured on associated portchannel.   |  ||
Notes
Note
- Tested against NXOSv 7.3.(0)D1(1) on VIRL
 - Unsupported for Cisco MDS
 - Either vpc or peer_link param is required, but not both.
 - 
state=absentremoves whatever VPC config is on a port-channel if one exists. - Re-assigning a vpc or peerlink from one portchannel to another is not supported. The module will force the user to unconfigure an existing vpc/pl before configuring the same value on a new portchannel
 - 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
- cisco.nxos.nxos_vpc_interface:
    portchannel: 10
    vpc: 100
   Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Returned | Description | 
|---|---|---|
|   commands    list / elements=string    |  always |   commands sent to the device  Sample:  ['interface port-channel100', 'vpc 10']   |  
Authors
- Jason Edelman (@jedelman8)
 - Gabriele Gerbino (@GGabriele)
 
    © 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
    https://docs.ansible.com/ansible/latest/collections/cisco/nxos/nxos_vpc_interface_module.html