01-11-2019 09:36 PM - edited 03-03-2019 08:58 AM
Is it a bad form to name access-list, class-map, policy-map all the same or it is encouraged?
Similarly, there are several crypto related configs like authorization policy, authentication policy, keyring, etc that could also share the same name.
Solved! Go to Solution.
01-12-2019 11:49 AM - edited 01-12-2019 03:18 PM
I wouldn't consider it bad form, in fact, if they are exclusively related (i.e. only used together), I believe it especially helps to clarify such a relationship. If the relationship is non-exclusive, you might want to keep just functional names.
Meheretab's suggestion is also good, although if followed I would recommend what he is doing be done as suffixes. This so, for sorting purposes, you usually want logically related elements to sort together and the suffix indicates the kind of element.
01-11-2019 10:06 PM
01-12-2019 11:49 AM - edited 01-12-2019 03:18 PM
I wouldn't consider it bad form, in fact, if they are exclusively related (i.e. only used together), I believe it especially helps to clarify such a relationship. If the relationship is non-exclusive, you might want to keep just functional names.
Meheretab's suggestion is also good, although if followed I would recommend what he is doing be done as suffixes. This so, for sorting purposes, you usually want logically related elements to sort together and the suffix indicates the kind of element.
01-12-2019 12:31 PM - edited 01-12-2019 12:33 PM
Thank you for helping with his question. We appreciate it.
01-12-2019 12:35 PM
pingduck, If you got your question answer, don't forget to mark it as "Accepted Solution" This helps all community members to find useful answers.
Thank you!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide