Sometimes you can't find local_port_name

MX104, 13.3R2:
[fisakytt@login10 ~]% snmpbulkwalk 185.50.247.3 1.0.8802.1.1.2.1.4.1.1.5
LLDP-MIB::lldpRemChassisId.181.0.1 = Hex-STRING: 10 0E 7E 9C 18 18
LLDP-MIB::lldpRemChassisId.200.0.2 = Hex-STRING: F4 B5 2F D0 F1 30
[fisakytt@login10 ~]% snmpbulkwalk 185.50.247.3 1.0.8802.1.1.2.1.3.7.1.3
LLDP-MIB::lldpLocPortId.563 = STRING: "563"
LLDP-MIB::lldpLocPortId.565 = STRING: "565"

After 'deactive lldp', 'active lldp':

[fisakytt@login10 ~]% snmpbulkwalk 185.50.247.3 1.0.8802.1.1.2.1.4.1.1.5
LLDP-MIB::lldpRemChassisId.137659711.565.3 = Hex-STRING: 10 0E 7E 9C 18 18
LLDP-MIB::lldpRemChassisId.137659728.563.4 = Hex-STRING: F4 B5 2F D0 F1 30
[fisakytt@login10 ~]% snmpbulkwalk 185.50.247.3 1.0.8802.1.1.2.1.3.7.1.3
LLDP-MIB::lldpLocPortId.563 = STRING: "563"
LLDP-MIB::lldpLocPortId.565 = STRING: "565"

In first example I would be looking for 'LLDP-MIB::lldpLocPortId.0' in both
cases, and I would fail to find correct local port name.
I had 10 MX104 with same config and 13.3R2, and two of them suffered this issue.

Maybe 'lldpRemChassisId' isn't best OID to figure out list of neighbours, but
then again shitty implementation/bug can affect any OID.

In above example I was looking for 'LLDP-MIB::lldpLocPortId.0' which does not ex