RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1937380 - RFE: Support automatically configure network using LLDP
Summary: RFE: Support automatically configure network using LLDP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Fernando F. Mancera
QA Contact: Mingyu Shi
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks: 1935910
TreeView+ depends on / blocked
 
Reported: 2021-03-10 14:19 UTC by Fernando F. Mancera
Modified: 2023-12-27 05:00 UTC (History)
8 users (show)

Fixed In Version: nmstate-1.1.0-1.el8
Doc Type: Technology Preview
Doc Text:
.Network state configuration using `nmstate-autoconf` is now available as a Technology Preview Network devices can use the Link Layer Discovery Protocol (LLDP) to advertise their identity, capabilities, and neighbors in a LAN. This enhancement adds the `nmstate-autoconf` utility as a Technology Preview to the `nmstate` package. The `nmstate-autoconf` utility can use the LLDP information to automatically configure local network interfaces. For further details, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/assembly_using-nmstate-autoconf-to-automatically-configure-the-network-state-using-lldp_configuring-and-managing-networking[Using nmstate-autoconf to automatically configure the network state using LLDP].
Clone Of:
Environment:
Last Closed: 2021-11-09 17:43:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github nmstate nmstate pull 1658 0 None open WIP: nmstate-autoconf: introduce nmstate-autoconf support 2021-07-02 06:16:39 UTC
Red Hat Issue Tracker NMT-1013 0 None None None 2023-12-27 05:00:10 UTC
Red Hat Product Errata RHBA-2021:4157 0 None None None 2021-11-09 17:44:01 UTC

Description Fernando F. Mancera 2021-03-10 14:19:35 UTC
Description of problem:

User story:

As an user of Nmstate I want to configure the network state automatically based on the LLDP VLAN announced information. That mean Nmstate will use the LLDP information to identify the existing vlans and configure the interfaces.

Comment 10 Fernando F. Mancera 2021-07-02 06:16:42 UTC
Upstream patch: https://github.com/nmstate/nmstate/pull/1658

Comment 11 Gris Ge 2021-07-14 16:04:03 UTC
Tested upstream patch.

Current limitation is user need to manually enable LLDP on interfaces before call `nmstate-autoconf`.

Comment 14 Mingyu Shi 2021-07-29 02:49:51 UTC
Verified with versions:
nmstate-1.1.0-1.el8.noarch
nispor-1.1.1-1.el8.x86_64
NetworkManager-1.32.3-0.z.2.20e3975fd2.el8.x86_64

The topology:
local   |  peer
--------|---------
veth0 --|-- a vlan with id 200
veth1 --|-- a vlan with id 255
veth2 --|-- a veth in bond0 --+
                              |-- a vlan(over bond0) with id 300
veth3 --|-- a veth in bond0 --+

Using default lldpd configuration, run nmstate-autoconf in local host:
# nmstate-autoconf -d 2> /dev/null
---
interfaces:
- name: veth0_ep.200
  type: vlan
  state: up
  vlan:
    base-iface: veth0
    id: 200
- name: veth1_ep.200
  type: vlan
  state: up
  vlan:
    base-iface: veth1
    id: 255
- name: bond300
  type: bond
  state: up
  link-aggregation:
    mode: balance-rr
    port:
    - veth2
    - veth3
- name: bond0_p.300
  type: vlan
  state: up
  vlan:
    base-iface: bond300
    id: 300

Comment 25 errata-xmlrpc 2021-11-09 17:43:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4157


Note You need to log in before you can comment on or make changes to this bug.