The official answer is we only support removing mime types, not the addition of them to the internal mimetypes.conf file. The reason is simply that we have tested the list that currently exists to work correctly with the compression engine. If there was a protocol that was not RFC compliant that was added, bad things could happen (core dumps/stalls/etc).
Send me a message to email@example.com. I can help you to modify the internal config file. If you were to do something like this, aside from being unsupported by TAC as stated above, you would have to agree to/understand the implications of the change on a production box.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...