Port AppGigabitEthernet1/1 displays incorrect neighbor

[baclaeys]

The problem

I recently started using a Cisco IE-3300-8T2S with the 16 port expansion module. I noticed that in LibreNMS (as pictured) the link to the neighbor device (far right column) is displaying incorrectly. The link to the neighbor that is displayed belongs to the port that is next in line. This is true for ports up GigabitEthernet2/1-16. I have not seen a workaround for this. Other devices that have an AppGigabitEthernet port such as a Cisco C9300 do not have this problem seemingly because the AppGigabitEthernet port falls after all of the physical ports and not in the middle like with the IE-3300-8T2S with the 16 port expansion module. Any advise on resolving this would be appreciated.

Output of ./validate.php

librenms@ic-ot-nms-01:~$ ./validate.php
===========================================
Component | Version
--------- | -------
LibreNMS  | 24.4.1 (2024-04-20T09:26:51-05:00)
DB Schema | 2024_04_10_093513_remove_device_perf (292)
PHP       | 8.1.27
Python    | 3.8.10
Database  | MariaDB 10.3.39-MariaDB-0ubuntu0.20.04.2
RRDTool   | 1.7.2
SNMP      | 5.8
===========================================

[OK]    Composer Version: 2.5.8
[OK]    Dependencies up-to-date.
[OK]    Database connection successful
[WARN]  Your database schema has extra migrations (2020_02_25_101056_create_ports_lldplocportid_table). If you just switched to the stable release from the daily release, your database is in between releases and this will be resolved with the next release.
[OK]    SQL Server meets minimum requirements
[OK]    lower_case_table_names is enabled
[OK]    MySQL engine is optimal
[OK]    MySQL and PHP time match
[OK]    Active pollers found
[OK]    Dispatcher Service not detected
[OK]    Locks are functional
[OK]    Python poller wrapper is polling
[OK]    Redis is unavailable
[OK]    rrdtool version ok
[OK]    Connected to rrdcached
librenms@ic-ot-nms-01:~$ ./da
daily.sh  database/
librenms@ic-ot-nms-01:~$ ./daily.sh
Fetching new release information                   OK
Updating to latest release                         OK
Updating Composer packages                         OK
Updating SQL-Schema                                OK
Updating submodules                                OK
Cleaning up DB                                     OK
Fetching notifications                             OK
Caching PeeringDB data                             OK

What was the last working version of LibreNMS?

This has never been an issue previously, but this is also the first time that I have seen an AppGigabitEthernet port that falls in the middle of a list of physical ports. This is not an issue if the expansion module is not used on the switch because the AppGigabitEthernet port falls at the end.

Anything in the logs that might be useful for us?

No response