Forum Discussion
Come to think of it, validating configs between data centres is an ideal job for diff.
You could pull the F5 config file bigip.conf from each host as this contains only the non-box specific information such as virtual's, pools, nodes. Then use diff to list differences. If the backend should be the same then the only differences you should find are the virtual IP addresses which then you could easily ignore. Any other differences you find could then be immediately flagged as an issue.
Given we can verify our config this way you can then push config to multiple data center's using iControl. Then as part of your post change verification if there is anything other than the virtual configuration different between DC's you can immediately rollback the change.
Of course this kind of system requires extensive testing, is usually written in-house using python or other iControl supported languages. It's just not a simple task as you need to understand the implications of changing objects on a live production F5 which usually houses many hundreds of applications, not just the one you are making a change for.