201 · Question #248
A new BIG-IP VE is deployed with default settings. The BIG-IP Administrator completes the setup utility in the Configuration Utility. The internal self IP address fails to respond to a ping request. W
The correct answer is A. Port lockdown on internal self IP is set to Allow None. If an internal self IP fails to respond to ping after initial setup on a new BIG-IP VE, a common cause is the Port Lockdown setting.
Question
A new BIG-IP VE is deployed with default settings. The BIG-IP Administrator completes the setup utility in the Configuration Utility. The internal self IP address fails to respond to a ping request. What is a possible cause of this issue?
Options
- APort lockdown on internal self IP is set to Allow None
- BRoute is NOT assigned to internal self IP.
- CInternal interface VLAN is set to untagged
- DInternal interface VLAN is set to tagged
How the community answered
(26 responses)- A85% (22)
- B4% (1)
- C4% (1)
- D8% (2)
Why each option
If an internal self IP fails to respond to ping after initial setup on a new BIG-IP VE, a common cause is the Port Lockdown setting.
By default, or due to a restrictive configuration, a self IP's Port Lockdown setting is often set to 'Allow None' or a custom list that does not include ICMP. This prevents the self IP from responding to ping requests, and it must be explicitly configured to 'Allow Default,' 'Allow All,' or include ICMP to enable ping responses.
An internal interface VLAN set to tagged is a valid configuration in an environment using VLAN tagging and would not by itself prevent a self IP from responding to ping if the tagging is correctly handled by the network infrastructure.
Concept tested: F5 BIG-IP self IP configuration and Port Lockdown
Source: https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-local-traffic-management-concepts/self-ip-addresses.html#_14
Topics
Community Discussion
No community discussion yet for this question.