SNMP

You should probably edit this post and sanitize out the community strings and real IP addresses ASAP.

Are you attempting to reach these devices via SNMP on their management interface, or on a production (TMM) interface?

Cory, this post is sanitized, but I made sure to use the same characters so that I could get the answer to why some devices are not accepting that string. We are going to the TMM interface.

Okay, just making sure.

So the self IP address on the BIG-IP that you are directing the SNMP queries to, what is the port lockdown setting configured to on the non-working BIG-IP devices? Is it the same as the device that's working?

Cory, thank you! It never hit me to go back into the self-IP ports. Do you have any idea why it won't take the community string on some devices and not others?

Did you find any differences in the port lockdown settings on the self IPs? And is your SNMP agent client allow list properly populated with the SNMP polling IP addresses/ranges?

You can also try running a tcpdump and capturing on the target self IP on the BIG-IP that should be receiving the SNMP communications.

Cory, yes there was differences, and I changed those and now they can discover the devices. However, it still doesn't make since that some of the devices will not take that one community string, while other devices will.

I don't think the issue is with the community string. Port lockdown was likely not permitting SNMP traffic to the interface at all.

http://support.f5.com/kb/en-us/solutions/public/13000/200/sol13250.html

Yes, agree that the port lockdown was the issue of not being able to discover the devices. However, some of the devices will not take the community string at all, and I need it to be in there. Other then that, everything is working like it is supposed to work.

Are the devices giving an error about the format of the community string?

I just put in your community string Ov3r_S!ght into a v11.2.0, a v11.3.0, and a v11.4.1 device and they all took it without issue.