Forum Discussion
mikeshimkus_111
Jun 09, 2015Historic F5 Account
In your config, lyncweb.domain.org isn't in the secure_reverse_proxy iRule that forwards traffic to the RP server pool. Requests for that FQDN will be dropped since there is no default pool for that VS.
- Chase_AbbottJun 09, 2015EmployeeThat would definitely drop a connection. Guessing there's no vIP? If so, wonder what's responding to ICMP...
- vitalsign0_2058Jun 09, 2015Nimbostratuslyncweb.domain.org is in the iRule. when HTTP_REQUEST { switch -glob [string tolower [HTTP::host]] { lyncweb.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } { pool Lync2013_reverse_proxy_front_end_4443_pool } meet.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } dialin.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } lyncdiscover.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } }
- mikeshimkus_111Jun 09, 2015Historic F5 AccountLooks like that wasn't in the iHealth config from June 5. You can add a log statement to that rule see how far the request is getting (you'll need to disable strictness on the iApp first) and tail /var/log/ltm from the command line while trying to connect to see the log entries: when HTTP_REQUEST { switch -glob [string tolower [HTTP::host]] { lyncweb.domain.org* { log local0. "Request for [HTTP::host] forwarded to reverse proxy pool." pool Lync2013_reverse_proxy_front_end_4443_pool } { pool Lync2013_reverse_proxy_front_end_4443_pool } meet.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } dialin.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } lyncdiscover.domain.org* { pool Lync2013_reverse_proxy_front_end_4443_pool } } }