So.... I'm a little confused how this is supposed to work now...
previously, net-snmp's listen ip wasn't clobbered by ha config sync.... so each node's listen IP would properly bind.
now, the primary node's config is propagated to the secondary... which... I mean... that's mostly what it's supposed to do.... however, both the primary and secondary are active snmp polling targets....
I figured it would be as simple as excluding snmp from the configuration sync options....
but there's not an option in the ha config for snmp....
Which makes me wonder, how is this SUPPOSED to work? Can anyone point me in the direction of some insight? I imagine I'm just doin it wrong.
Config in net snmp is not synced, just use the main IPs of respective Firewalls in config
Hm.... musta been a glitch in an interim version:
[root@secondary /usr/local/etc]# opnsense-version
OPNsense 24.7.a_20
as I can confirm that the behavior I *WAS* experiencing, where the active node's address being injected into the webui for snmp.... is no longer occurring... YAY! :)