Service Mapping - Azure LoadBalancer TD Patttern Issues

Tyson Elder
Tera Contributor

Hello Everyone,

Really hoping someone out there can help me with this issue. 

What I'm trying to do:
Map via a URL, that takes a public IP to an Azure LB, kicks it to a backend pool (the backend pool is 2x F5 Loadbalancers). 

The error: When using the URL as an EP, I get 'Failed to recognize application'. I've dug into the Azure LB TD Pattern, and it fails when trying to find a match on private IPs/Entry point IP. This makes sense since the EP is a Public IP. ServiceNow can see this public IP (it's listed against the LB in the CI). But for some reason, the OOB pattern seems to only look for private IPs? 

Has anyone else seen this or am I missing a step here? I've got read only access to the Loadbalancer, and visually I can see what it's doing is very very simple. I do also have access to the F5 Loadbalancer, I've got REST access issues at the moment, which means I can't read the irule. But To me, that should mean my map will fail at the F5 Level.

Basically my map should look like
Azure LB -> F5 LB -> App Host -> Database Host. I can 'spoof' the EP by entering in the Virtual IP from the backend pool on the F5 LB, so my map looks like F5 LB -> App Host -> Database Host...except I then run into an array of issues downstream as the 'EP' is no longer the URL but a hack job I cobbled together. 

2 REPLIES 2

Tyson Elder
Tera Contributor

For a bit of context, this is the Step that fails: 

TysonElder_0-1714350096855.png

Since the EP IP is a public IP, it finds no match and it's all sad news from here. 

Do you have any updates abou this issue?