The first screenshot indicates mature SAs and most importantly you have bytes registered on both the IN and OUT selector. Mature SAs means that the IPsec tunnel is up. Bytes on the IN and OUT SAs means that you even have bi-directional traffic happening over the tunnel.
The second screenshot appears to have output from the racoon log at the top of the screen indicating that the IPsec-SA is established in both directions. This also supports the idea that the IPsec tunnel is up.
The third screenshot is just a repeat of the second I think.
From what I see, the problem is not to do with the tunnel itself because the tunnel is up and handling packets in both directions. Do you have AFM configured? AFM or packet filtering may be in the way. It's difficult for me to guess what could be going wrong, but you really need to look at tcpdump on the BIG-IP to look at the private flows and verify whether the BIG-IP is forwarding the private packets off the tunnel.
Try a tcpdump filter similar to this:
tcpdump -nni 0.0 net 10.0.8.0/24 and net 10.111.0.0/24
That looks for any packets that match the selectors. Anything that matches this filter must be put into, or come out of the IPsec tunnel (according to your selector description earlier).