I'm running a cluster of 3 APICs with version 1.0(1e). After initial provisioning process using the console port on the back of the APIC servers, all runs well. I have access to HTTPS, SSH etc, but I lost console access to APIC servers. Is that a planned behavior? Do I need to now move to Out-Of-Band port only from now on?
You be able to access the APIC via the APIC CIMC - and continue so after the APIC is configured and all components in the fabric are discovered. Once the fabric discovery is complete, however you should be able to access the APIC via 'ssh' as 'admin' which would be more convenient.
I ran into this problem on a case. After the initial setup dialog, the console port stops working. Immediately after hitting enter after the dialog asks if "the above configuration is correct". found an old case from Andres where i see that the console port is disabled on purpose?
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...