Regression in bgpLocalAs discovery

• Hi,

We identified what seems to be a regression in our last update:
Observium updated: 22.4.11952 (stable) -> 22.5.12000 (stable)

On several devices, the Local AS is discovered wrong.
Running discovery.php -m bgp-peers -d  for a Cisco ASR920 device leads me to think the following commands are used in order to determine bgpLocalAs:

CMD[/usr/bin/snmpget -t '3' -r '5' -v2c -c *** -Pud -OQUv -m BGP4-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'frgre-cog-a9h1.as29075.net':'161' bgpLocalAs.0]

CMD[/usr/bin/snmpget -t '3' -r '5' -v2c -c *** -Pud -OQUv -m CISCO-BGP4-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/cisco 'udp':'frgre-cog-a9h1.as29075.net':'161' cbgpLocalAs.0]

CMD[/usr/bin/snmpgetnext -t '3' -r '5' -v2c -c *** -Pud -OQUs -m CISCO-BGP4-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/cisco 'udp':'frgre-cog-a9h1.as29075.net':'161' cbgpPeer2LocalAs]

These commands yield, respectively:

• 29075, which is correct and the expected value
• No Such Instance currently exists at this OID
• cbgpPeer2LocalAs.ipv4."185.96.184.156" = 50618, which is the local AS for the first BGP peer (that is also in a VRF)

This issue is critical for us because we rely on Observium discovery for configuring our monitoring tools and we can't currently update these tools to reflect the current network status.

Thanks for your help.