MVPIt ended up being that the following was configured so I had to add in the additional subnet.
MVPI guess the routing part is ok. I mean you can ping the F5 from Solarwinds and vice versa.
If you have a firewall in between udp port 161 is permitted I guess.
What errors do you get when you run snmpwalk from solarwinds? have you checked the logs of F5 and Solarwinds server?
MVPmihaicI can ping from Solarwinds to F5 but not the other way around but that is by design. On the firewall I do see that udp/161 is being allowed and I see the connection arrive at the F5 in the tcpdump. I do not see anything on the Solarwinds server other than the connection failed. Sadly on the F5 side I haven't found anything in the logs or the particular log setting to provide me the information that I'm looking for in regards to SNMP connections. I did a test just now where I allowed all IPs in the agent allow list and it still doesn't work. I did notice that when I allow nothing to reach the F5 for SNMP both snmpget from any of my other F5s ends up having the same behavior as Solarwinds where the connection arrives but no response is sent back. It might be possible that the allow list is not functioning correctly or possibly that because the Solarwinds server sits on a different subnet it is acting different than the F5s on the same management network. I might have to reach out to F5 on this one to see if maybe this is a bug. I appreciate your assistance on this one though.