QuestionQ7

Troubleshoot Basic Virtual Server Connectivity Issues

An LTM Specialist is diagnosing a problem with a new virtual server. When clients connect through the virtual server, their browser displays "Unable to connect", even though direct connections to the pool member confirm that the application is working correctly. The LTM device configuration is:

ltm virtual /Common/vs_https \{  
    destination /Common/10.10.1.110:443  
    ip-protocol udp  
    mask 255.255.255.255  
    pool /Common/pool_https  
    profiles \{  
        /Common/udp \{ \}  
    \}  
    translate-address enabled  
    translate-port enabled  
    vlans-disabled  
\}  
  
ltm pool /Common/pool_https \{  
    members \{  
        /Common/172.16.20.1:443 \{  
            address 172.16.20.1  
        \}  
    \}  
\}  

What problem is the LTM Specialist experiencing?

  • A The virtual server is disabled on all VLANs.
  • B The pool member is marked down by a monitor.
  • C The pool member is marked down administratively.
  • D The virtual server is configured for the incorrect protocol.
Explanation

HTTPS client traffic uses TCP, whereas the virtual server listens only for UDP traffic on port 443 and has a UDP profile attached. TCP connection attempts therefore do not match the virtual server. F5 documents that a virtual server’s ip-protocol specifies the IP protocol for traffic it directs, including TCP and UDP.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!