fervin

Oh, okay. I guess continuing on using Startup and ignoring the conflicts is currently the best approach then. Thanks again! -Frank

in F5 LTM Startup, Running configs don't match which breaks compliance reporting Comment by fervin June 2013

Thanks! I don't know how I missed that option... You wouldn't by any chance know how hard it would be to save bigip_base.conf to Baseline instead of Startup would you? This would clean up the conflicts and make the whole backup configuration more logical, I think. -Frank

in F5 LTM Startup, Running configs don't match which breaks compliance reporting Comment by fervin June 2013

Does "F5 Interface polling" include the ability to alert when a node is marked down or a pool has no available members? This information is essentially already in NPM so it would be really, really useful to be able to alert on it. It would make NPM a total slam-dunk for F5 monitoring. We'd be happy to test / preview as…

in WHAT WE ARE WORKING ON POST NPM 10.5 Comment by fervin May 2013

fervin

Comments