I am trying to use Service Mapping to discover an application that has an F5 GTM policy applied. I can successfully discover the LTM configuration for the LB Pool in a single data center, but the discovery pattern is unsuccessful for the Global Traffic Manager (GTM).
While the two GTM and LTM patterns are similar in their functionality, I would expect that the service map would result in processing two LTM configurations - one for each F5 device located in two separate data centers.
The production instance I'm working against is Geneva, but I've also verified this on my personal instance which is running Istanbul. It appears that there is an error in the OOTB pattern for GTM in both of those releases. The scripts look identical. I don't have ready access to a Helsinki instance, but I'm guessing it's the same.
Show below, you can see that Line 5 of the GTM Identification process is labeled "populate IP" and transforms the 'virtual_servers_table' (it is both the source and target table). This table is retrieved via SNMP in the previous step. However, the actual update produces an obvious error due to syntax. The Target Field name is "ip" and the Value is "EVAL(".
The script goes on to read the GTM MIBs and so forth. The LTM pattern, while similar, does not have that transform step after reading the virtual server data.
Has anyone had success with the F5 GTM pattern? Any clue as to the purpose of this step of the pattern? I obviously can see that it's an IP address, but is it the VIP for the application? What should the eval function be?
I'll close this question. I missed the fact that the evaluation attribute is an extended field and clicking the small icon to the right of the single line brought up the window with the full eval script.
Doh!
I'll close this question. I missed the fact that the evaluation attribute is an extended field and clicking the small icon to the right of the single line brought up the window with the full eval script.
Doh!
