[APM] - Error: failed to reset strict operations; disconnecting from mcpd
Hello Experts , When we try to verify the sys config with the command "load sys config verify" , we are getting beow error message followed with the services restart ...Bug ID 997793 (f5.com) , We tried to remove the old epsec-package file and restarted , but no luck . Can anyone please advise on this ? Validating configuration... /config/bigip_base.conf /config/bigip_user.conf /config/bigip.conf /config/bigip_script.conf Error: failed to reset strict operations; disconnecting from mcpd. Will reconnect on next command. The connection to mcpd has been lost, try again.11Views0likes1CommentR-Series Appliance No GUI ( host system gui ) after 1.7.0 upgrade
After running the 1.7.0 upgrade for the r-series 5000 appliance - the login screen does not display in a browsers. Admin and Root passwords are as they were before upgrade. mgmt-ip settings are the same. Device can ping it's upstream router in the mgmt-ip network. the device mgmt-ip address does not reply to ping ( or any request [ ssh, http...]) from the console I can see the whole running config - it is the same as before the upgrade Any help is appreciated, Dave Mehlberg101Views0likes5CommentsF5OS R4800 upgrade to 1.7.0
Hi All, I have installed a F5 R4800 platform in our test environment, now i want it to upgrade to 1.7.0. After the upload the new image via GUI, it stays in "Signature Verification Failed" status. I have installed a R5900 platform in production, over there i no issue to upgrade to version 1.7.0 Dont know if the platform is doing verification through internet or not. Does anyone knows by chance. Thanks in advance.Solved82Views0likes4CommentsHow to free up the HD1 physical disk space ?
Hello Experts , How to free up the HD1 disk space ? We have 2 volume HD1.1 and HD1.2 , to create a new volume how much free space is required ? How can we free up the space for the same ? Hardware Version Information Name HD1 Type physical-disk Model WDC Parameters -- -- SerialNumber WD-WM Size 465.76G Firmware Version 01.01S03 Media Type HDD --- Volume group --- VG Name vg-db-sda System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 127 VG Access read/write VG Status resizable MAX LV 0 Cur LV 13 Open LV 8 Max PV 0 Cur PV 1 Act PV 1 VG Size 465.75 GiB PE Size 4.00 MiB Total PE 119233 Alloc PE / Size 116260 / 454.14 GiB Free PE / Size 2973 / 11.61 GiB VG UUID NRa4BZ-TYJm-gTFW-AVO3-7bEd-Evpj-lqgYbW LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert dat.appdata vg-db-sda -wi-ao---- 357.25g dat.boot vg-db-sda -wi-a----- 468.00m dat.log vg-db-sda -wi-ao---- 21.02g dat.share vg-db-sda -wi-ao---- 42.03g dat.swapvol vg-db-sda -wi-ao---- 5.00g set.1._config vg-db-sda -wi-a----- 3.17g set.1._usr vg-db-sda -wi-a----- 6.09g set.1._var vg-db-sda -wi-a----- 4.50g set.1.root vg-db-sda -wi-a----- 440.00m set.2._config vg-db-sda -wi-ao---- 3.17g set.2._usr vg-db-sda -wi-ao---- 6.09g set.2._var vg-db-sda -wi-ao---- 4.50g set.2.root vg-db-sda -wi-ao---- 440.00m62Views0likes3CommentsF5 ASM upgrade
As it is aware that version (BIG-IP 15.1) of the existing software used on our F5 devices ( i2600 ) will expire after year 2024. We are planning software upgrade to keep equipment in our environment are actively supported by product vendor. When checking from F5 web site, there are two upstream version 16.1 and 17.1 respectively. I would like to check ( in terms of viability and stability and the support of JSON format for ASM policies ), may I know which version (16.1 or 17.1) would be recommended? Thanks.274Views0likes2CommentsTwo virtual servers go down after an upgrade
Hi Everyone, I'm wondering if anyone has seen this behaviour before. After I perform an upgrade, two virtual servers out of about 10 go down. The applications using these VSs stop working, from the looks of it outbound traffic out to the internet stops. The health monitor used is the default HTTPS. I've created a custom monitor to GET a file from the backend pool members which marks the nodes as up, but the apps still don't work. The backend servers are running IIS10.0. Some versions of the F5 software work, most do not. Working versions are 14.1.2.8, 14.1.4, and 15.1.3.1. All other versions seem to not work. As soon as the upgraded device is made active (in the HA pair) the VSs go down. Packet captures don't seem to show the issue, but they do indicate for some reason there's a 75 second+ pause in the response from the pool members. This isn't there when one of the working versions is active so I don't think this is an issue with the pool member. The traffic passes through two sets of Checkpoint firewalls, and is NATed each time on these firewalls on the way to the internet. Could anyone provide information as to why this would work with some versions of the BIG-IP software, and not others? Thanks,Solved1.2KViews0likes6CommentsBIG-IP : upgrade fails to transfer configuration
BIG-IP 11.4.0 Build 2384.0 Final I want to upgrade to 11.4.1 retaining current configuration. I downloaded BIGIP-11.4.1.608.0.iso and uploaded to BIG-IP and installed to volume HD1.2 ( HD1.1 has 11.4.0 ). System > Software Management : Boot Locations I select HD1.2 , set Install Configuration to Yes , set Source Volume = "HD1.1:11.4.0" , and click Activate However on reboot the message is displayed : The configuration has not yet loaded. If this message persists, it may indicate a configuration problem.1KViews0likes11CommentsTrying to upgrade the lab enviroment, from 10.1.0.3341.0.1 to 11.5.3.0.0.163
Hi, Im trying to upgrade our lab enviroment from 10.1.0.3341.0.1 to 11.5.3.0.0.163, but its failing and i cannot figure out why. root@lb01a(Active)(tmos) / sys software status root@lb01a(Active)(tmos.sys.software.status) show Sys::Software Status Volume Product Version Build Active Status -------------------------------------------------- HD1.1 none none none no complete HD1.2 BIG-IP 10.1.0 3341.0 yes complete root@lb01a(Active)(tmos) install sys software image BIGIP-11.5.3.0.0.163.iso volume HD1.1 root@lb01a(Active)(tmos) show sys soft status Sys::Software Status Volume Product Version Build Active Status ---------------------------------------------------------------------------------- HD1.1 BIG-IP 11.5.3 0.0.163 no failed (Can't find requested disk HD1.) HD1.2 BIG-IP 10.1.0 3341.0 yes complete MD5 checksum is OK. The same happens when i try to go via the webgui... Any ideas? I cant figure this one out. Regards, Rikard334Views0likes6Comments