Add LLDP local port ID discovery and mapping via ports_lldplocportid …

[jayib]

…table

Please give a short description what your pull request is for

I've added functions to save the lldpLocPortId to the new ports_lldplocportid table in the database. It saves the lldpLocPortId in a row with the LibreNMS port ID and device ID, so that these can be used for link discovery. This way even devices which advertise their MAC address for lldpLocPortId can have port links by finding the corresponding device ID and port ID.

DO NOT DELETE THE UNDERLYING TEXT

Please note

Please read this information carefully. You can run ./lnms dev:check to check your code before submitting.

• Have you followed our code guidelines?
• If my Pull Request does some changes/fixes/enhancements in the WebUI, I have inserted a screenshot of it.
• If my Pull Request makes discovery/polling/yaml changes, I have added/updated test data.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926
After you are done testing, you can remove the changes with ./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.

[jayib]

Hi @Npeca75.I know you’ve been working on related LLDP discovery changes and I don’t want to step on that work.

We’ve been seeing consistent discovery failures with devices that return MAC-style LLDP identifiers (e.g. Avaya ERS), and this MR was an attempt to make that data reusable across discovery runs.

If this conflicts with your approach or isn’t something you want merged, no worries. Just wanted to check whether I should keep this updated, rework it, or drop it entirely.

Thanks for your time.