errors
3 Topics
"Configuration problem" when setting up a trial LTM VM
I have downloaded the 90 day trial version of LTM VE and am having trouble configuring it. I have installed it on an ESXi server and run 'config' to set up a static IP address for the management interface. However this is not persistent - if I reboot the VM the IP address gets forgotten and I have to re-enter it. Next I managed to log into the UI and install the trial license. However the UI then displays this message when logging in: This BIG-IP system has encountered a configuration problem that may prevent the Configuration utility from functioning properly. To prevent adverse effects on the system, F5 Networks recommends that you restrict your use of the Configuration utility to critical tasks only until the problem is resolved. Beware that attempting to modify your configuration in this state with the Configuration utility may cause your configuration to be overwritten. and when I have logged in I get this across the top of the page: The configuration has not yet loaded. If this message persists, it may indicate a configuration problem. and most UI options just show the message "An error has occurred while trying to process your request." So what have I done wrong, and how do I fix it? Edit: Config files requested by emi: /config/bigip.conf: [root@localhost:Offline:Standalone] config cat /config/bigip.conf apm resource remote-desktop citrix-client-bundle /Common/default-citrix-client-bundle { } apm sso saml-sp-connector /Common/saml_office365 { assertion-consumer-uri https://login.microsoftonline.com/login.srf description "Predefined SP connector object for Office 365" entity-id urn:federation:MicrosoftOnline } ltm default-node-monitor { rule none } ltm classification signature-version { version-number 0 } net ipsec ike-daemon /Common/ikedaemon { } wom endpoint-discovery { } /config/bigip_base.conf: [root@localhost:Offline:Standalone] config cat /config/bigip_base.conf cm cert /Common/dtca-bundle.crt { cache-path /config/filestore/files_d/Common_d/trust_certificate_d/:Common:dtca-bundle.crt_26609_1 checksum SHA1:1220:e4fe95d5e7d778cfa0b5fae3aae90196e97e2ccd revision 1 } cm cert /Common/dtca.crt { cache-path /config/filestore/files_d/Common_d/trust_certificate_d/:Common:dtca.crt_26603_1 checksum SHA1:1220:e4fe95d5e7d778cfa0b5fae3aae90196e97e2ccd revision 1 } cm cert /Common/dtdi.crt { cache-path /config/filestore/files_d/Common_d/trust_certificate_d/:Common:dtdi.crt_26612_1 checksum SHA1:1172:75c02118a7daba3e3b84b6d4414063953b92ed1b revision 1 } cm device /Common/bigip1 { base-mac 0:50:56:96:4d:6c build 39.0 cert /Common/dtdi.crt chassis-id 4216b78b-1ce8-729f-88f19ffa5a46 edition "VE Trial 11.3.0-HF1 (based on BIGIP 11.3.0HF6)" hostname bigip1 key /Common/dtdi.key management-ip 192.168.1.245 marketing-name "BIG-IP Virtual Edition" platform-id Z99 product BIG-IP self-device true time-zone PDT version 11.3.0 } cm device-group /Common/device_trust_group { auto-sync enabled devices { /Common/bigip1 { } } hidden true network-failover disabled } cm device-group /Common/gtm { devices { /Common/bigip1 { } } hidden true network-failover disabled } cm key /Common/dtca.key { cache-path /config/filestore/files_d/Common_d/trust_certificate_key_d/:Common:dtca.key_26606_1 checksum SHA1:1675:e5fe1aeae877dceabf0788f00716d9a20fcfb6e2 revision 1 } cm key /Common/dtdi.key { cache-path /config/filestore/files_d/Common_d/trust_certificate_key_d/:Common:dtdi.key_26615_1 checksum SHA1:1679:2ed0adc0939945269c13060d99da4d2916558f6d revision 1 } cm traffic-group /Common/traffic-group-1 { unit-id 1 } cm traffic-group /Common/traffic-group-local-only { } cm trust-domain /Common/Root { ca-cert /Common/dtca.crt ca-cert-bundle /Common/dtca-bundle.crt ca-devices { /Common/bigip1 } ca-key /Common/dtca.key status standalone trust-group /Common/device_trust_group } net interface 1.1 { media-fixed 10000T-FD } net interface 1.2 { media-fixed 10000T-FD } net interface 1.3 { media-fixed 10000T-FD } net route-domain /Common/0 { description "Default Route Domain" id 0 } net self-allow { defaults { ospf:any tcp:161 tcp:22 tcp:4353 tcp:443 tcp:53 udp:1026 udp:161 udp:4353 udp:520 udp:53 } } net stp /Common/cist { } security firewall port-list /Common/_sys_self_allow_tcp_defaults { ports { 22 { } 53 { } 161 { } 443 { } 1028 { } 4353 { } } } security firewall port-list /Common/_sys_self_allow_udp_defaults { ports { 53 { } 161 { } 520 { } 1026 { } 4353 { } } } security firewall rule-list /Common/_sys_self_allow_all { rules { _sys_allow_all { action accept } } } security firewall rule-list /Common/_sys_self_allow_defaults { rules { _sys_allow_tcp_defaults { action accept destination { port-lists { /Common/_sys_self_allow_tcp_defaults } } ip-protocol tcp } _sys_allow_udp_defaults { action accept destination { port-lists { /Common/_sys_self_allow_udp_defaults } ip-protocol ospf } } } security firewall rule-list /Common/_sys_self_allow_management { rules { _sys_allow_ssh { action accept destination { ports { 22 { } } } ip-protocol tcp } _sys_allow_web { action accept destination { ports { 443 { } } } ip-protocol tcp } } } sys feature-module cgnat { disabled } sys folder / { device-group none inherited-devicegroup false inherited-traffic-group false traffic-group /Common/traffic-group-1 } sys folder /Common { device-group none inherited-devicegroup true inherited-traffic-group true traffic-group /Common/traffic-group-1 } sys management-dhcp /Common/sys-mgmt-dhcp-config { request-options { subnet-mask broadcast-address routers domain-name domain-name-servers host-name ntp-servers } } sys management-ip 192.168.1.245/24 { dhcp-enabled true } sys provision afm { } sys provision apm { } sys provision asm { } sys provision avr { } sys provision gtm { } sys provision lc { } sys provision ltm { level nominal } sys provision pem { } sys provision psm { } sys provision wam { } sys provision wom { } sys provision woml { }Solved2KViews0likes13Comments
Receiving Error stating "General Error"?? 4000-LTM
Hi I am seeing an error message stating "General Error" on f5 4000 EM 3.1.0 Build. Tacacs was recently configure not sure if this can display the error. this prevents us from accessing the enterprise management and looking at the devices. thanks Kind Regards377Views0likes2Comments"No handler" errors
Hi, on a production LTM, we are currently experiencing intermittent connectivity problems to some of the VIPs. With the "tmsh show /sys tmm-traffic", I see a relativelly large number of "No handler" errors. Other error counters in the same output are zero. Does anybody have an idea what do these errors indicate?748Views0likes2Comments