Short overview about Cisco Aci Naming Convention Best Practices and what's good to know about.
When it comes to Cisco ACI naming conventions, best practices dictate that you should use a consistent, logical naming scheme that will make it easy for you and others to identify specific objects within the ACI fabric. There are a few different ways to go about this, but one popular method is to use a prefix or suffix that denotes the object type, followed by a dash, and then the object’s specific name. For example, you might use the following convention:
So, an application profile within ACI would be named something like “App-MyApp”, while a network endpoint group would be named “EPG-MyEPG”. This naming scheme is not only easy to remember and use, but it also makes it easy to search for specific objects within the ACI fabric using tools like the Cisco ACI GUI or CLI.
Another best practice when it comes to Cisco ACI naming conventions is to use descriptive names that will give you and others a clear idea of what the object is and what it does. For example, rather than using a generic name like “EPG-1”, you might use a more descriptive name like “EPG-WebServers”. This will make it much easier to identify the purpose of the EPG, and it will also make it easier to search for specific EPGs within the ACI fabric.
Finally, you should also avoid using special characters or spaces in Cisco ACI names, as this can make it difficult to work with the objects using some tools. If you do need to use special characters or spaces in a name, you can use underscores to separate the different parts of the name. For example, you might use a name like “EPG_WebServers”.
By following these best practices, you can ensure that your Cisco ACI naming conventions are both consistent and descriptive, making it easy for you and others to work with the ACI fabric.