Forum Discussion

VinceBlack's avatar
VinceBlack
Icon for Altocumulus rankAltocumulus
Feb 19, 2023
Solved

Help with Local Traffic Policy with streaming app. and basic understanding.

This is a homelab to have a better understanding of F5 BIG-IP and appercaite any help. For testing purpose I have setup a PLEX server for streaming service and will be setting up a Horizon View UAGs...
devops
local traffic policy
vip
virtual servers
  • VinceBlack's avatar
    VinceBlack
    Feb 21, 2023

    Hey, Paulius, thank you again for the tcpdump switches.  That helped me find the reset message.  I started looking into how to debug this more, which has been a great learning experience.  I noticed in the log that when trying from the mobile device, the HTTP_Request for the Host has :443, but accessing from a web GUI or macOS app, it did not.  Both policy and iRule had equal to abc.domain.com.  I updated the iRule and policy to include or and now it works.  See below for iRule.  I like the policy features, but it was great to work with iRules too.  

    if { [HTTP::host] equals "abc.domain.com" or [HTTP::host] equals "abc.domain.com:443" }

VinceBlack's avatar
VinceBlack
Icon for Altocumulus rankAltocumulus

According to F5 docs.  "Couldn't open a connection to a pool member. This is typically the result of an iRule, Policy, or configuration that prevents the BIG-IP from choosing a pool member." I'll keep poking around and see why this happening.

Paulius's avatar
Paulius
Icon for MVP rankMVP
Feb 20, 2023

VinceBlack If you can provide the configuration we can most likely come up with a solution rather quick. If you need to redact names please do so.

  • VinceBlack's avatar
    VinceBlack
    Icon for Altocumulus rankAltocumulus
    Feb 21, 2023

    Hey, Paulius, thank you again for the tcpdump switches.  That helped me find the reset message.  I started looking into how to debug this more, which has been a great learning experience.  I noticed in the log that when trying from the mobile device, the HTTP_Request for the Host has :443, but accessing from a web GUI or macOS app, it did not.  Both policy and iRule had equal to abc.domain.com.  I updated the iRule and policy to include or and now it works.  See below for iRule.  I like the policy features, but it was great to work with iRules too.  

    if { [HTTP::host] equals "abc.domain.com" or [HTTP::host] equals "abc.domain.com:443" }