201 · Question #249
The BIG-IP Administrator is unable to access the management console via Self-IP 10.10 1.33 and port 443. What is the reason for this problem?
The correct answer is C. Self IP is configured to allow UDP 443. The inability to access the BIG-IP management console via Self-IP on port 443 is likely due to the Self-IP being configured to allow UDP 443, rather than the required TCP 443 for HTTPS management access.
Question
The BIG-IP Administrator is unable to access the management console via Self-IP 10.10 1.33 and port 443. What is the reason for this problem?
Options
- APacket Filter needs to be configured to allow a source
- BSelf IP is configured to allow TCP All
- CSelf IP is configured to allow UDP 443
- DPacket Filter is configured to allow port 443
How the community answered
(48 responses)- A8% (4)
- B15% (7)
- C73% (35)
- D4% (2)
Why each option
The inability to access the BIG-IP management console via Self-IP on port 443 is likely due to the Self-IP being configured to allow UDP 443, rather than the required TCP 443 for HTTPS management access.
Packet filters are separate from Self-IP port lockdown settings and, while they can block traffic, the Self-IP's own port configuration is a more direct control for access to the Self-IP itself.
If the Self-IP was configured to allow TCP All, then TCP 443 would be allowed, and the administrator would be able to access the management console, contradicting the problem statement.
If the Self-IP is configured to allow only UDP 443, it will block incoming TCP 443 connections required for HTTPS access to the management console, preventing the administrator from connecting.
Packet filters allowing port 443 would suggest access should be possible, which contradicts the problem of being unable to access the management console.
Concept tested: BIG-IP Self-IP port lockdown
Topics
Community Discussion
No community discussion yet for this question.