Author: | Peter Sprygada |
---|
parameter | required | default | choices | comments |
---|---|---|---|---|
interface_id | yes | the full name of the interface | ||
lacp | no | active |
|
enables the use of the LACP protocol for managing link bundles |
links | no | array of physical interface links to include in this lag | ||
logging | no |
|
enables or disables the syslog facility for this module | |
minimum_links | no | the minimum number of physical interaces that must be operationally up to consider the lag operationally up | ||
state | no | present |
|
describe the desired state of the interface related to the config |
Note
Requires Arista EOS 4.10
Note
Requires Netdev extension for EOS
Example playbook entries using the arista_lag module to manage resource
state. Note that interface names must be the full interface name not shortcut
names (ie Ethernet, not Et1)
tasks:
- name: create lag interface
action: arista_lag interface_id=Port-Channel1 links=Ethernet1,Ethernet2 logging=true
- name: add member links
action: arista_lag interface_id=Port-Channel1 links=Ethernet1,Ethernet2,Ethernet3 logging=true
- name: remove member links
action: arista_lag interface_id=Port-Channel1 links=Ethernet2,Ethernet3 logging=true
- name: remove lag interface
action: arista_lag interface_id=Port-Channel1 state=absent logging=true
Note
Requires EOS 4.10 or later
Note
The Netdev extension for EOS must be installed and active in the available extensions (show extensions from the EOS CLI)
Note
See http://eos.aristanetworks.com for details