The "tcp any" will allow connections to that Virtual IP on any TCP port. If it is
working using the specific port, it should be working using any. Keep in mind that the CSM will accept and load balance using "tcp any," b
ut your server may not be listening on that port and will reset the connection.
As a best practice, you should define the specific port on the vserver for load balancing. Using the "any" statement has it's purposes, but for general load blancing define the tcp/udp port number for your application. This is also more secure.
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...