Cisco Config Cleaner. Beta testing
Friends!
We are testing a new idea on our website, namely, checking the cisco IOS configuration files for consistency and consistency. At the moment, we have implemented the functionality for identifying "garbage" access lists, as well as identifying such dangerous "tails" as binding an access list without the list itself.
Briefly tell you why it may be necessary:
')
1. You do not remember which access list is used where, where it is applied and whether it is needed at all.
2. You do not know exactly what and where is applied, because your predecessors generally wrote a config
3. You would like to improve your config, but you are not sure whether it is possible to remove the thread or “leave it as it is, you never know what.”
4. You are curious
To check the config, take a text file, drop it here and get a report.
I want you to appreciate this new piece of ours and express your opinion.
For example, you will notice an inaccuracy, saying that we say that the access list is not applied, but it is actually applied there. Tell me and we will gratefully fix the script. We could miss something too.
Therefore, by the way, all reports are BACKGROUND. Do not rush headlong to change something dramatically.
Plans for the future are:
1. Add new checks on created but not attached or linked but not created constructions (route-map, crypto-map, class-map, etc.)
2. Add recommendations for improving the config based on the analysis
3. Add specific commands that can be applied on the router in order to save and paste the config file.
4. Add similar checks on the ASA
Tell me your wishes, criticism and thanks plz to me in any way possible:
4u@anticisco.ru
here
on the forum antitsiski
on Twitter: @Fedia_anticisco
Together we will create an interesting product for KMK.
We are testing a new idea on our website, namely, checking the cisco IOS configuration files for consistency and consistency. At the moment, we have implemented the functionality for identifying "garbage" access lists, as well as identifying such dangerous "tails" as binding an access list without the list itself.
Briefly tell you why it may be necessary:
')
1. You do not remember which access list is used where, where it is applied and whether it is needed at all.
2. You do not know exactly what and where is applied, because your predecessors generally wrote a config
3. You would like to improve your config, but you are not sure whether it is possible to remove the thread or “leave it as it is, you never know what.”
4. You are curious
To check the config, take a text file, drop it here and get a report.
I want you to appreciate this new piece of ours and express your opinion.
For example, you will notice an inaccuracy, saying that we say that the access list is not applied, but it is actually applied there. Tell me and we will gratefully fix the script. We could miss something too.
Therefore, by the way, all reports are BACKGROUND. Do not rush headlong to change something dramatically.
Plans for the future are:
1. Add new checks on created but not attached or linked but not created constructions (route-map, crypto-map, class-map, etc.)
2. Add recommendations for improving the config based on the analysis
3. Add specific commands that can be applied on the router in order to save and paste the config file.
4. Add similar checks on the ASA
Tell me your wishes, criticism and thanks plz to me in any way possible:
4u@anticisco.ru
here
on the forum antitsiski
on Twitter: @Fedia_anticisco
Together we will create an interesting product for KMK.
Source: https://habr.com/ru/post/92350/
All Articles