BIG-IP Virtual Edition Configuration Utility log in failures
I have just installed my BIG-IP Virtual Edition trial and I am having trouble logging in to the Configuration Utility. I have configured the VM and can connect my browser to the Configuration Utility and I get the login screen, but it keeps telling me there is an Authentication problem. I get Authentication required! This server could not verify that you are authorized to access the URL "/tmui/logmein.html" .... ... I've tried the default login and password of 'admin' and 'admin' and 'admin' and 'default' I've see both pairs mentioned online but neither works for me. What am I missing?
SSL Offload performance in F5 LTM Virtual Edition
Can anyone tell me what the performance of SSL Offload is like using F5 LTM Virtual Edition. I am trying to save costs and not purchase hardware right now, and wondered what the limitations were in the Virtual Edition. Surely, performance still scales based on VMware host hardware/Virtual Machine specs? Any advice or links to white papers appreciated :) Mark
VE lost communication after upgrade to ESXi 6.7 Update 2
After upgrade ESXi 6.7 from build 13004448 (last public patch before Update 2) to 13006603 (Update 2), VE 14.1.0.3 lost communication on TMM interfaces (mgmt worked fine). I did some research then. Egress traffic from TMM went correctly (another VM could see it), but ingress traffic did not fall into TMM. Tried to send burst of 10k broadcast ARP requests in VLAN with TMM interfaces connected, but with no adequate change in stats (tmsh show net interface all-properties raw) on TMM interfaces (stats of mgmt interface, connected to the same VLAN, are increased adequately). Restarting VE did not help. Restarting ESXi did not help. After rolling the ESXi back to the previous build, everything started to work. Tried once again upgrade to 6.7u2 and rollback, with the same results. Speculation: Since Update 2 release notes mention bugfix in vmxnet3, this may be related. AFAIK, TMM takes care of interfaces by itself (in linux, these are visible in lspci, but neither in ifconfig, ip link nor /sys/class/net/), so there could have been made some change in host-side vmxnet3 that is not yet reflected in TMM code. Has anyone similar experience with ESXi 6.7u2? Best regards, OndrejUpgrade/Downgrade BIG-IP VE (lab license)
I'm finding differing information on upgrading/downgrading BIG-IP VE and would like to confirm the process. I have a lab license and would like to be able to switch between versions (11.2, 12.x - 13) to be able to lab new configurations as well as legacy configs and exercises around certification. Before doing so I wanted to be sure that this could be done simply performing normal upgrade/downgrade procedures (install new version on partition and boot into it). I understand that re-configuration may be required when switching between versions and that will not be a problem. This link references v13 and notes that the VM does not need to be re-installed, just perform a normal update (download image, install image, boot into new partition) This link for Hyper-V and v12 indicates that when upgrading to v12.1 the VM should be re-installed and Support contacted to transfer the license. This link also for Hyper-V and for older versions (10.2 - 11.1) lists a more involved process. It may not be applicable due to being for an older version. The answer may simply be use the normal upgrade process. However given that some references appear to indicate that the VM should be re-installed when moving between certain versions, I'd like to be sure that I do this 'properly' to ensure the final system is stable and accounts for any changes between versions (maybe larger disks were provisioned or something...). My environment is VMWare ESXi, in case the above refs were strictly related to HyperV environments.
VE F5 not passing tagged vlan traffic across Vxrail ESXI
Hi Guys, Been working on this and cannot come to a conclusion, our VE F5 which sits in an esxi enclosure, does not work when tagged vlan is configured (this is the way, rest of the other VE F5s are configured across the estate). However If we untag 1 vlan (and only allows you to untag 1 vlan on the VE) This works for the backend server and traffic passes as we can now see the pool members up, however the front end sits on another vlan and we cannot untag. The only difference is the other f5s sit on a 'UCS' or HP chassis and the problematic one sits on the 'vxrail'. my f5 version is 12.1.2 HF2 And the ESXI is version 6.0. Many thanks if someone can give me a descent answer, i have read most of the forums and nothing helpful.
How to best Create Big-IP lab on VE from Physical production configuration to test upgrade?
I'm in the process of upgrading our physical Big-IP LTMs and would like to import as much of the configuration as possible (while maintaining VE management configuration) into a virtual edition lab to perform a mock upgrade. I exported the SCF from the source physical and the VE for comparison. I found K81271448: Merging BIG-IP configuration objects into the running configuration using tmsh https://support.f5.com/csp/article/K81271448 So it looks like I could remove portions from physical source configuration file and massage the rest, and merge. I converted the vlans to use the last interface on the VE (and disconnected from the VM). But which parts of the config should I keep, and which should I remove prior to merging? I also read that a UCS configuration might be more appropriate to export and import. What is the best recommendation to migrate production Big-IP configuration to a VE lab to test an upgrade prior to actual upgrade?
BIG-IP VE - VMWare ESXi recommended settings
How well does Big-IP F5 work on VMWare Dynamic resource scheduler ? we have successfully migrated a standalone physical to Virtual but soon after we had to revert as their were reach-ability issues with the virtual servers ? any guess on what could have caused the issue ? currently the security settings on VMware for Promiscuous mode, mac address change and forged transits are set to reject. -- I suspect the issue might have been because of this setting.. but our device is only standalone. changing the vm settings is not easy without justification.
Virtual edition unable to deploy on vmware workstation
Team, Please help ,, I am trying to deploy Virtual edition of BIG-IP (BIGIP-11.6.0.0.0.401.ALL-scsi.ova) on VMware workstation pro12. When I try to import the .ova file it just sits on the import screen forever. not sure how long the actual import takes but after few hours like 10-12hrs my C drive disk space will go low from 175GB free. I tried different 11.4 ova file with VMworkstation 11. still the same problem. Please help me to get the labsetup running .. -Bhaskar