How to discover F5 BigIP LTM.

[pratiksha5]

Hi I am new to F5 discovery. Can someone help with the procedure. SNMP community credentials will be enough? I need to populate firmware version as well. Looks like it is not present OOB. Please suggest the best possible way to do it. 

I haven't used REST api for discovery. Docs suggest might need to use that. Also SNMP community string wont be enough. 

Lastly, Will the pool members populate along with the discovery (load balancer pool members) or customization will be needed for same. 

[Rahul Priyadars]

Hi Pratiksha

There will always the DAY 1 for everyone 🙂

Please follow the steps given as per docs- https://docs.servicenow.com/en-US/bundle/sandiego-it-operations-management/page/product/discovery/concept/c_LoadBalancerF5BIGIP.html

Run discovery on Dev Instance First. Once discovery is done then Go for your additional requirements which is not available OOTB. 

Regards

RP

[pratiksha5]

Thank you Rahul. I will post once it is done. 🙂

Will this work for f5 too?

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0793931

[pratiksha5]

@Rahul Priyadarshy I could discover the BIG IP load balancer now. We already have manually created CI's for this. Discovery updated them with more information. But for one it created a CI. My identification rule is as follows. 

I have two identifier entries. 

1) main table setting is name and serial number and lookup table serial number and serial number type (here the serial number type was different  ) order 100

2) Name and serial number order is 200

Now It should have matched the second one and updated the old CI. But discovery created a new one.  

Discovery log : Identifier: , Rule 1 Searched on <> for attributes: :Skipped Identifier Entry.

Identifier: Load Balancer, Rule 2 Searched on <cmdb_serial_number> for attributes: serial_number,serial_number_type with hybrid attributes: name,serial_number:No Match.

Identifier: Load Balancer, Rule 3 Searched on <cmdb_ci_lb> for attributes: name,serial_number:No Match.

I have only two identifier rules. Please suggest a solution. 

[Mike I2 · Accepted solution]

Yep, SNMP V3 credentials should be enough. You also shouldn't need to configure traps on the devices. Watch out for firewall rules opening TCP161 instead of UDP161 though, that's caught me out a couple of times. You'll know if the correct port protocol isn't being used from the Shazzam payload. Also, be aware that'll you'll likely get false positive SSH credential errors as these devices commonly also have port 22 open.