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 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 issue is the LTM Specialist experiencing?
Suggested Answer: B
Get Premium 301b Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
VI
Vi
11 months ago
Not sure about that, could be something else entirely.
EM
Emily
11 months ago
Wait, is the pool member even up?
RO
Roy
11 months ago
Definitely sounds like a protocol issue to me.
FE
Felicitas
12 months ago
I think it's more likely the pool member is down.
MA
Martina
12 months ago
The virtual server is disabled on all VLANs.
JU
Julie
12 months ago
I feel like the "Unable to connect" message might relate to the virtual server being disabled on VLANs, but I need to double-check that.
MA
Maryrose
1 year ago
The protocol seems off to me. I thought virtual servers needed to match the pool member's protocol, but I'm not completely confident.
DE
Deandrea
1 year ago
I think we practiced a similar question where a pool member was down due to a monitor. Could that be what's happening here?
JA
Jacklyn
1 year ago
I remember something about VLANs being disabled could cause connectivity issues, but I'm not sure if that's the main problem here.
CL
Claudio
1 year ago
I'm a bit confused by the "translate-address" and "translate-port" settings. I'll need to research what those do to see if they could be causing the issue.
LI
Ligia
1 year ago
The pool member address is 172.16.20.1, so I'll check if that server is actually up and running the application.
RO
Rosio
1 year ago
Okay, let me think this through step-by-step. The "Unable to connect" message suggests a connectivity issue, so I'll focus on the pool member status.
IS
Isadora
1 year ago
Hmm, the virtual server is set to UDP protocol, but the pool member is likely expecting TCP. That could be the problem.
MA
Markus
1 year ago
This looks like a tricky one. I'll need to carefully review the configuration details to identify the issue.
MI
Ming
1 year ago
Looks like the LTM Specialist needs to brush up on their protocol knowledge. UDP for an HTTPS virtual server? That's like trying to pour water into a teapot!
DA
Dahlia
1 year ago
Haha, I bet the LTM Specialist was daydreaming about their next vacation when they set this up. Gotta stay focused, my friend!
MU
Murray
1 year ago
C) The pool member is marked down administratively.
LI
Ligia
1 year ago
B) The pool member is marked down by a monitor.
JA
Janet
1 year ago
A) The virtual server is disabled on all VLANs.
CR
Cristal
1 year ago
I think the pool member is marked down by a monitor. The connection directly to the pool member is working, so the issue must be with the virtual server configuration.
MA
Ma
1 year ago
C) The pool member is marked down administratively.
VI
Vivan
1 year ago
I agree, the monitor might be causing the issue.
LI
Lindsey
1 year ago
B) The pool member is marked down by a monitor.
AL
Alex
1 year ago
A) The virtual server is disabled on all VLANs.
AS
Asuncion
2 years ago
The virtual server is configured for UDP protocol, but the application is running on TCP (HTTP/HTTPS). This is likely the issue, so I would choose D.
SU
Suzi
1 year ago
We should change the virtual server configuration to use TCP protocol instead.
EU
Eulah
1 year ago
That would explain why clients are unable to connect through the virtual server.
HE
Herman
1 year ago
Yes, it seems like the application is running on TCP, not UDP.
ON
Oneida
1 year ago
I think the virtual server is configured for the wrong protocol.
KI
Kirk
2 years ago
I believe the virtual server might be configured for the incorrect protocol, causing the connection issue.
CA
Carlota
2 years ago
I agree with Barbra, the pool member being marked down could be causing the 'Unable to connect' message.
BA
Barbra
2 years ago
I think the issue is with the pool member being marked down by a monitor.