f5 big-ip ltm ve
5 TopicsBig-IP Virtual Edition Configuration Loading Failure
I am encountering an issue with my Big-IP virtual edition where the configuration fails to load. Upon accessing the Command Line Interface (CLI), the following message is displayed: Sys::mcpd State: ------------------------------------------------------- Running Phase platform Last Configuration Load Status base-config-load-failed End Platform ID Received true ------------------------------------------------------- Additionally, when attempting to load the system configuration using the command `tmsh load sys config`, the process encounters an error and aborts. The specific error message received is: Loading system configuration... /defaults/asm_base.conf /defaults/config_base.conf /defaults/ipfix_ie_base.conf /defaults/ipfix_ie_f5base.conf /defaults/low_profile_base.conf /defaults/low_security_base.conf /defaults/policy_base.conf /defaults/wam_base.conf /defaults/analytics_base.conf /defaults/apm_base.conf /defaults/apm_oauth_base.conf /defaults/apm_saml_base.conf /defaults/app_template_base.conf /defaults/classification_base.conf /var/libdata/dpi/conf/classification_update.conf /defaults/ips_base.conf /var/libdata/ips/ips_update.conf /defaults/daemon.conf /defaults/pem_base.conf /defaults/profile_base.conf /defaults/sandbox_base.conf /defaults/security_base.conf /defaults/urldb_base.conf /usr/share/monitors/base_monitors.conf /defaults/cipher.conf /defaults/ilx_base.conf Loading configuration... Unexpected Error: No user configuration is found. Loading process is aborted. Troubleshooting Steps Attempted: 1. Checked the status of `Sys::mcpd` using `tmsh show sys mcp-stat`. 2. Attempted to reload the system configuration using `tmsh load sys config`. I seek assistance in resolving this issue. Please provide guidance on potential troubleshooting steps or solutions to rectify the configuration loading failure.121Views0likes2CommentsF5 upgrade error
Hi All, I tried to upgrade my F5 VE from 11.5.1 and 11.6.1 and got the following error on reboot. set.1./var contains a file system with errors, check forced set.1./var: Directory inode 81930, block 0, offset 0: directory corrupted set.1./var: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): Please help me in fixing this errors. I am not even able to access UI or terminal. Thanks, Sekhar760Views0likes7CommentsNoob question on VS and node
Hi all, I have a F5 here being setup by the previous F5 administrator. Our previous webserver was 10.8.6.19 and it was replace by this F5 10.8.10.12 and 10.8.10.14 are the Application server. I don't quite understand is that why is the VS is set as the web server IP and not the application server ? When I check on the firewall, the public IP is pointing to 10.8.6.19 which makes me more confusing. Ltm::Node: 10.8.10.12 (10.8.10.12) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Node: 10.8.10.14 (10.8.10.14) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Pool: test_pool_15005 Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_15005 Minimum Active Members : 0 Current Active Members : 2 Total Requests : 0 Current Sessions : 0 Ltm::Pool: test_pool_15007 Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_15007 Minimum Active Members : 0 Current Active Members : 1 Total Requests : 0 Current Sessions : 0 Ltm::Pool: test_pool_https Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_18080 Minimum Active Members : 0 Current Active Members : 1 Total Requests : 1484 Current Sessions : 18446744073709551615 Ltm::Virtual Server: test_vs_10080 Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10080 Ltm::Virtual Server: test_vs_10081 Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10081 Ltm::Virtual Server: test_vs_https Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:443 Ltm::Virtual Server: test_vs_stunnel Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10443246Views0likes1CommentNoob question on VS and node
Hi all, I have a F5 here being setup by the previous F5 administrator. Our previous webserver was 10.8.6.19 and it was replace by this F5 10.8.10.12 and 10.8.10.14 are the Application server. I don't quite understand is that why is the VS is set as the web server IP and not the application server ? When I check on the firewall, the public IP is pointing to 10.8.6.19 which makes me more confusing. Ltm::Node: 10.8.10.12 (10.8.10.12) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Node: 10.8.10.14 (10.8.10.14) Status Availability : available State : enabled Reason : Node address is available Monitor : /Common/icmp (default node monitor) Monitor Status : up Session Status : enabled Ltm::Pool: test_pool_15005 Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_15005 Minimum Active Members : 0 Current Active Members : 2 Total Requests : 0 Current Sessions : 0 Ltm::Pool: test_pool_15007 Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_15007 Minimum Active Members : 0 Current Active Members : 1 Total Requests : 0 Current Sessions : 0 Ltm::Pool: test_pool_https Status Availability : available State : enabled Reason : The pool is available Monitor : test_tcp_18080 Minimum Active Members : 0 Current Active Members : 1 Total Requests : 1484 Current Sessions : 18446744073709551615 Ltm::Virtual Server: test_vs_10080 Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10080 Ltm::Virtual Server: test_vs_10081 Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10081 Ltm::Virtual Server: test_vs_https Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:443 Ltm::Virtual Server: test_vs_stunnel Status Availability : available State : enabled Reason : The virtual server is available CMP : enabled CMP Mode : all-cpus Destination : 10.8.6.19:10443233Views0likes0Comments