Missing pattern-based outgoing connections from load balancer. Please check the correctness of the incoming connection

[pavanyuvi]

Hi All,

We are getting the below issue

"Missing pattern-based outgoing connections from load balancer. Please check the correctness of the incoming connection"

only loadbalancer information is populating,please find the attached image.

In discovery log it is showing it is taking as "citrix netscaler pattern",Identification is running fine but in connections

Executing SSH command: show vserver | grep ciname

2018-09-24 11:48:29: Executing SSH command: command -v sudo

2018-09-24 11:48:42: Command result: ERROR: No such command

2018-09-24 11:48:46: Command result: Warning: Feature(s) not enabled [GSLB]

2018-09-24 11:48:46: Execution time: 16956 ms

get policies rules and actions relations

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

get our vip policies

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

keep all relevant rules

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

keep policies matching our port or not matching on port

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

get all actions

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

merge actions and actions name

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

extract vservers from actions

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

get vserver info

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

extract members and ports

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

 Create connection

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

verify no connections

2018-09-24 11:48:46: Execution time: 0 ms

filter out all connections with non operational status and without ip address

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

keep all connections with port 0 empty * or null on seperate table

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

remove all connections with port 0 empty * or null on seperate table

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

replace empty ports with real ports

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

union both tables

2018-09-24 11:48:46: setAttribute(connections,[])

2018-09-24 11:48:46: Execution time: 0 ms

Create connection

2018-09-24 11:48:46: Step condition is false. step not executed.

2018-09-24 11:48:46: Execution time: 0 ms

Regards,
Pavan

[angel_jimenez]

Hi @pavanyuvi!

Did you get to solve this issue? I'm facing same error and don't know how to continue here... 😞

Thanks in advance!

[HamzehAlsheikh]

Hi, did you find out the solution to this please?

[HamzehAlsheikh]

UPDATING, I have found the solution!
That happened when you have F5 loader balancer. when the load balancer has no IRule, the pool wont forward the connection further, the Pattern will pick FQDN instead of the IP, so what you need to do:

• Go your F5 in your CMDB -> load balancer pool 
• Locate you application service and open it
• Go down to load balancer pool members 
• Under the name you find the ip addresss
• Under the IP address you might find a fake FQDN instead of the ip ( here is the problem)  because under the ip address should be an ip matching the one under the name

you can fix this manually, but whenever you run discovery, it will come up again as fqdn. to fix this problem permanently:

• Go to Discovery Pattern -> search for  F5REST
• F5 LB REST identification
• Search for fqdn step

change the fqdn attribute to ip

• Save -> push
• Sync the pattern to the mid server -> run discovery again 

Please mark it green answer so everyone gets the solution 🙂 

[Poojamk]

Hi @HamzehAlsheikh , I am facing same issue and I tried your solution. However it is not helping. Please suggest. Thanks

[HamzehAlsheikh]

UPDATING, I have found the solution!
That happened when you have F5 loader balancer. when the load balancer has no IRule, the pool wont forward the connection further, the Pattern will pick FQDN instead of the IP, so what you need to do:

• Go your F5 in your CMDB -> load balancer pool 
• Locate you application service and open it
• Go down to load balancer pool members 
• Under the name you find the ip addresss
• Under the IP address you might find a fake FQDN instead of the ip ( here is the problem)  because under the ip address should be an ip matching the one under the name

you can fix this manually, but whenever you run discovery, it will come up again as fqdn. to fix this problem permanently:

• Go to Discovery Pattern -> search for  F5REST
• F5 LB REST identification
• Search for fqdn step

change the fqdn attribute to ip

• Save -> push
• Sync the pattern to the mid server -> run discovery again 

Please mark it green answer so everyone gets the solution 🙂