- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2022 10:13 AM
Hello. I searched and failed to find an answer as to why Discovery fails to classify these load balancers. I did find the link below and followed what the OP said worked but Discovery still fails to classify. Can someone help please?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2022 08:42 AM
Josh,
If you are using SNMP to discover the Load Balancer, check if an OID exists for this model. We recently had a F5 BIG-IP i2600 that we were not able to discover and it also failed at classify. The OID didn't exist in the OID table [discovery_snmp_oid]. Once we added an OID for this Model, discovery was successful.
Steps for Checking and Adding OID
1) On the ECC Queue tab, open the SNMP - Classify: OIDs input.
2) In the XML, search for the SnmpObjectId that is grouped in the system OID (the model should show up in the sysDescr section). Copy the value of the SnmpObjectId (minus the leading period .). In this example, the value is 1.3.6.1.4.1.3375.2.1.3.4.104.
3) Navigate to the OID table (Discovery Definition->CI Classification->SNMP System OIDs) and search on the OID attribute for the copied value. If the OID doesn't exist in the table, then add it. In this example, the values for a F5 BIG-IP i2600 are:
- Oid: 1.3.6.1.4.1.3375.2.1.3.4.104
- Operator: Is
- Manufacturer: F5 Networks
- Model BIG-IP i2600
- Table: F5 BIG-IP
- Classifier: F5 BIG-IP Load Balancer
4) Re-discover the Load Balancer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2022 11:42 PM
As per docs,
Discovery treats load balancers as licensable entities and attempts to discover them primarily using SNMP. If a load balancer in your system, running on a Linux host, has SNMP and SSH ports open, Discovery might classify it based on the SSH port. This classification has priority over SNMP. To ensure that Discovery properly classifies your hardware load balancers, create a Discovery behavior for load balancers that includes SNMP but not SSH. Software load balancers are treated as applications.
what credentials you are using? and what error you see there in discovery logs/ ecc queue i, any screenshot?
I think in your case ssh are attempting first due to priority of port probes. Also you need to provide the APIs permissions
Please read the docs for F5 BIG-IP load balancers .
Hope its helpful
Anshu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2022 08:42 AM
Josh,
If you are using SNMP to discover the Load Balancer, check if an OID exists for this model. We recently had a F5 BIG-IP i2600 that we were not able to discover and it also failed at classify. The OID didn't exist in the OID table [discovery_snmp_oid]. Once we added an OID for this Model, discovery was successful.
Steps for Checking and Adding OID
1) On the ECC Queue tab, open the SNMP - Classify: OIDs input.
2) In the XML, search for the SnmpObjectId that is grouped in the system OID (the model should show up in the sysDescr section). Copy the value of the SnmpObjectId (minus the leading period .). In this example, the value is 1.3.6.1.4.1.3375.2.1.3.4.104.
3) Navigate to the OID table (Discovery Definition->CI Classification->SNMP System OIDs) and search on the OID attribute for the copied value. If the OID doesn't exist in the table, then add it. In this example, the values for a F5 BIG-IP i2600 are:
- Oid: 1.3.6.1.4.1.3375.2.1.3.4.104
- Operator: Is
- Manufacturer: F5 Networks
- Model BIG-IP i2600
- Table: F5 BIG-IP
- Classifier: F5 BIG-IP Load Balancer
4) Re-discover the Load Balancer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2022 05:44 AM
Thanks Chuck! That worked!!!