The only time you really need to specify the port under the serverfarm/rserver is if the port the client hits the vip on is different from what the application on the server is using.
For example if the class-map was for udp port 53, but the server was listening on port 54 you would need to specify the port number.
If for example your class-map was like this
class-map match-any vips
match virtual address 188.8.131.52 udp any
Since this vip is listening for any udp port you would not want to use the port under serverfarm/rserver. Whatever destination port the client sends to the vip by default will be passed on to the backend server. Putting the port on the rserver forces the ACE to change the destination port to whatever you specify.
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...