Forum Discussion
good way to document
- Sep 20, 2016
For basic requirements, you can create a bash script which invokes
commands and parses the output according to your preference. Every now and then, execute the script manually, and also manually update the documentation in your corporate Sharepoint (or w/e you have). This is a low-cost solution.tmsh list
In case of complex requirements where real-time visibility of current config and/or system metrics are required 24/7, no manual solution will work. This is where companies turn to API (REST). Also a front-end component other than F5 must be used (this can be any NIX/Apache server). A Typical F5 visibility automation project from start to finish will cost a company anywhere from 50k-200k USD, regardless if internal employees or external contractors are used for the job.
Also note there are a few iApps and other visibility tools F5 offers for free. One example being the F5 and Splunk Analytics collaboration (https://splunkbase.splunk.com/app/3161/). Before building a custom tool, it's advised to check whether any of the freely available tools cover your needs.
Depends what you're wanting to document.
I've worked in organisations that simple document Layer 3 Topology - Depicted by Vlans/Subnets etc.
Going to individual configuration items - Good luck! I believe Netbrain is F5 compatible, so might be worth exploring.
If not, its going to be a custom CMDB with customisable fields which needs to be kept up to date...
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com