Re: Inline interface problems after upgrade to 4.1.3b
so, I shouldn't be worried about this?
I had other customers running 4.1.3b, that is why I chose that one. Is there any major problem with 4.1.3b?
sh interface inlineport 1/0/lan or sh interface inlineport 1/0/wan show same as above
Customer had the WAN router disconnected from WAE, and when we've tried to reconnect the WAE, there were latency and connectivity problems. Customer is sure it's a SP issue, I just wanted to be sure because this output was very strange. So, even with the WAE running fine, could I have that output due to the bug?
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...