You are reading an unmaintained version of the Ansible documentation. Unmaintained Ansible versions can contain unfixed security vulnerabilities (CVE). Please upgrade to a maintained version. See the latest Ansible documentation .
net_l2_interface - Manage Layer-2 interface on network devices
This module provides declarative management of Layer-2 interface on network devices.
parameter
required
default
choices
comments
access_vlan
no
Configure given VLAN in access port.
aggregate
no
List of Layer-2 interface definitions.
mode
no
access
Mode in which interface needs to be configured.
name
no
Name of the interface excluding any logical unit number.
native_vlan
no
Native VLAN to be configured in trunk port.
state
no
present
State of the Layer-2 Interface configuration.
trunk_allowed_vlans
no
List of allowed VLAN's in a given trunk port.
trunk_vlans
no
List of VLANs to be configured in trunk port.
- name : configure Layer-2 interface
net_l2_interface :
name : gigabitethernet0/0/1
mode : access
access_vlan : 30
- name : remove Layer-2 interface configuration
net_l2_interface :
name : gigabitethernet0/0/1
state : absent
Common return values are documented here Return Values , the following are the fields unique to this module:
name
description
returned
type
sample
commands
The list of configuration mode commands to send to the device
always, except for the platforms that use Netconf transport to manage the device.
list
['interface gigabitethernet0/0/1', 'switchport mode access', 'switchport access vlan 30']
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
For more information about Red Hat’s this support of this module, please
refer to this knowledge base article<https://access.redhat.com/articles/rhel-top-support-policies>
For help in developing on modules, should you be so inclined, please read Community Information & Contributing , Testing Ansible and Developing Modules .
Copyright © 2017 Red Hat, Inc.
Last updated on Nov 15, 2022.
Ansible docs are generated from GitHub sources using Sphinx using a theme provided by Read the Docs . . Module documentation is not edited directly, but is generated from the source code for the modules. To submit an update to module docs, edit the 'DOCUMENTATION' metadata in the modules directory of the core source code repository .