How to Find SNMP OID - F5 Load Balancers

[Tom104]

Hi All,

I need to find the OIDs of our F5 Load Balancers.

I've been given the IPs by our Infrastructure team, but on discovery am getting one of the three following errors:

Alive, not active, not classified
Alive, couldn't classify, now finished
Not a reachable host (No response to target ports scanned by MID)

I have raised a ticket with our infra team to make sure ports 161 and 22 are open for SNMP and SSH respectively, but still want to identify the OIDs of the devices to eliminate any problems with classification.


Could someone therefore please provide me with a step by step guide as to how to locate this? I haven't found any guides that explain this simply.

[Prabhjyot Sing1]

Hi @Tom104 ,

There are a few things that you can check.

1. If you do not see SNMP/SSH being picked up from the shazam, you can check the ECC queue payload to see if those ports are open or not.

2. If the ports are open you can proceed to testing the SNMP or SSH credentials whichever you are using for the discovery.

3. If the above 2 steps are successful then you should be seeing the F5 LB pattern being executed in the discovery logs, if the discovery is failing at that stage then you can check the logs to see if there is any errors there.

Also if you using SSH please make sure you do the steps mentioned in this guide - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0781036

Hope this helps also attaching the documentation regarding the F5 LB Discovery -

https://docs.servicenow.com/en-US/bundle/vancouver-it-operations-management/page/product/discovery/c...

[SiD2]

Hi @Tom104 

You can check the OIDs used in classification of your exact F5 LB model from the table "SNMP System OIDs" from filter navigator.

You can also check the same credential from an alternative snmp tool or snmpwalk command from terminal in the same mid server with which you are attempting discovery.

[Tom104]

Thanks Sid, sadly I don't know what model the Load balancer is (which may be part of the problem). I've also no access to an snmp tool due to security constraints, nor do I have access to the mid server.

I'll try any of these, once I'm given the right access. Hopefully that'll resolve the issue.