4 ms·

I use F5s at work, heres some responses: 1) You can, if you are careful about what your doing. UCS archives are only intended to be restored on the same mach

by kayfox 8y ago

I use F5s at work, heres some responses: 1) You can, if you are careful about what your doing. UCS archives are only intended to be restored on the same machines, restoring them on a different machine requires considering the master key for secret encryption and omitting the license from the UCS. If your restoring it on another model F5, you might be going about things in a sub-optimal way. 2) This typically relates to how stuff like VMWare deals with disk issues or migration. In (some versions) VMWare if there is a disk IO operation thats taking too long, it will pause the VM. It also pauses the VM when you use DRS or live migrate. IF your using a failover pair or cluster this will cause a failover because well, the other device went away for a period of time. 3) Ive only ever seen ASM config lost after an upgrade, and its usually because the unit was not relicensed before upgrading and wasnt licensed for the new version as a result. 4) Ive seen this happen an it was usually because something was in a bad state and rebooting just poked it into failing. Also, always save sys config after making changes in tmsh, it doesnt auto-save (same behavior as Cisco). 5) Because F5 has a policy of publishing a bug in the release notes and in bug tracker if it was ever seen by a customer. Contrast this with some other vendors who very selectively publish bug information.

elagost 8y ago
Thanks for your responses. A good foil to my complaints. My experience is very selective. I agree on 5, too - I'd rather have the bug published and at least know that it's been seen and is being worked on, but still, it's a little disheartening to look at an update you're about to install and see its list of breaks is longer than its list of fixes.
throw0101a 8y ago
> [...] omitting the license from the UCS. I believe this has improved in recent releases. It used to be that if you tried importing a config, and you were not properly licensed, the import would bomb out in annoying ways. In newer versions the import will at least pull in and save everything (AFAICT), but anything not licensed will simply not be active. Once you cut the proper cheques then things should work.

by kayfox 8y ago

elagost 8y ago

Thanks for your responses. A good foil to my complaints. My experience is very selective. I agree on 5, too - I'd rather have the bug published and at least know that it's been seen and is being worked on, but still, it's a little disheartening to look at an update you're about to install and see its list of breaks is longer than its list of fixes.

throw0101a 8y ago

> [...] omitting the license from the UCS. I believe this has improved in recent releases. It used to be that if you tried importing a config, and you were not properly licensed, the import would bomb out in annoying ways. In newer versions the import will at least pull in and save everything (AFAICT), but anything not licensed will simply not be active. Once you cut the proper cheques then things should work.