We upgraded our test environment last week. All seemed to be running without any problems.
Today i logged in to the Admin context, changed to a user context and then all connectivity was gone.
I logged on to our terminal server router to view the ACE's console. Appearently it was rebooting. I don't know what has caused it, but i know for sure we'll keep testing a bit longer than we first had in mind.
Thought you guys might be interested in a productive DC environment running Release 2.0.
We moved our productive applications from datacenter A: running release 1.6x to datacenter B: running release 2.x this weekend. So far everything runs smooth and fast.
We had some minor issues with redirections of https terminated traffic prior to 2.x code which have been resolved after the upgrade. The Code feels stable, we had no crashes or service failures from the ACE side in a couple of testing weeks.
The whole application feels a lot faster now and more responsive.
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...