One thing I would recommend that you do would be to create a new classifier for your application with port 23 and your destination IP addresses to differentiate it from telnet. When it's created, it will be above the general telnet classifier and the application will utilize your Full optimization for the traffic that matches your config. That way you can leave general telnet as default and it will handle the rest of the port 23 trafic as designed. You can then track your application statistics separately by using a new Application bucket and you should start seeing it on the graphs, both on the general charts as well as the individual WAE charts..
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
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
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...