MENU
An LTM Specialist is troubleshooting an issue with a new virtual server. When connecting through the virtual server, clients receive the message "Unable to connect" in the browser, although connections directly to the pool member show the application is functioning correctly. The LTM 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
}
}
}
How should the LTM Specialist resolve this issue?
Suggested Answer: D
Get Premium 301b Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
LA
Lashawna
10 months ago
Adding an HTTP profile sounds like a solid move.
XO
Xochitl
10 months ago
Totally agree, switching to TCP would fix this!
DO
Domitila
11 months ago
Disagree, I think enabling the pool member on the right VLAN is key.
ST
Stefany
11 months ago
Wait, why is UDP even being used here? Seems off.
ES
Estrella
11 months ago
The virtual server is using UDP, but HTTP needs TCP.
MA
Marjory
11 months ago
I keep thinking about the UDP protocol in this configuration. It feels off for a web application, so option D might actually be the best way to resolve the issue.
CA
Carrol
12 months ago
I thought we learned that adding an HTTP profile could help with connection issues, but I can't recall if it applies here. Option B seems plausible, but I'm not confident.
TH
Theron
12 months ago
I'm not entirely sure, but I feel like we practiced a similar question where enabling the pool member on the correct VLAN was the key. So maybe option C could be worth considering.
IV
Ivory
12 months ago
I remember we discussed the importance of matching the protocol for virtual servers. I think option D might be the right choice since it mentions selecting the correct protocol.
VE
Veda
1 year ago
I'm a bit confused by the pool configuration. Maybe I should double-check that the pool member is enabled and accessible on the correct VLAN.
CA
Carry
1 year ago
I think the key here is to match the virtual server protocol to the client traffic. Changing the protocol to TCP or HTTP/HTTPS should resolve the "Unable to connect" error.
DE
Devorah
1 year ago
Okay, let's see here. The virtual server is set to UDP, but the clients are connecting through a browser, which typically uses HTTP/HTTPS. That could be the issue.
KI
Kimberlie
1 year ago
Hmm, this one seems tricky. I'll need to carefully review the configuration details to figure out what's going on.
DE
Denise
1 year ago
Okay, let's think this through. The clients can't connect, but the pool member is working fine. That points to a configuration issue, and the protocol mismatch is the most likely culprit. D) is the way to go, unless the LTM Specialist is feeling particularly mischievous and wants to try B) just to see what happens. *chuckles*
CH
Chaya
1 year ago
Let's go with D) and see if that resolves the problem.
CA
Carrol
1 year ago
Yeah, I agree. It seems like the protocol mismatch is causing the issue.
BL
Blair
1 year ago
I think D) Select the correct protocol for the virtual server is the best option here.
CY
Cyril
1 year ago
Ha! The LTM Specialist must have been daydreaming when they set this up. UDP for a web server? That's a bold move, Cotton. D) is the obvious choice, unless they want to make it even more interesting by trying C) and enabling the VLAN. *shakes head*
NO
Noah
1 year ago
Hmm, I'm not sure about this one. The configuration looks a bit strange, but I think the key is the protocol mismatch. D) is the way to go, unless the LTM Specialist is really feeling adventurous and wants to try B) just for fun.
JE
Jestine
1 year ago
The issue is clearly with the protocol. The virtual server is set to use UDP, but the pool member is probably expecting TCP/HTTP. D) Select the correct protocol for the virtual server seems like the right answer here.
RI
Rima
1 year ago
That makes sense. The protocol mismatch is likely causing the connection issue.
RI
Rima
1 year ago
D) Select the correct protocol for the virtual server.
AL
Alisha
1 year ago
Yes, D) Select the correct protocol for the virtual server should fix the issue.
AS
Ashton
1 year ago
Select the correct protocol for the virtual server.
RO
Rodolfo
1 year ago
I think the virtual server is using the wrong protocol.
FA
Fausto
1 year ago
The virtual server is using UDP, but the pool member is expecting TCP/HTTP.
VE
Veronica
1 year ago
Should we also consider adding an HTTP profile to the virtual server?
LA
Lavonna
1 year ago
I agree, selecting the correct protocol for the virtual server could help.
JA
James
1 year ago
I think the issue might be with the protocol.