Re: ACE: cmd exec error with "copy startup-config running-config
I noticed that all the errors are related to configuration commands that, in configuration mode, would cause a "duplicate" or "already exist" error (e.g commands such as "access-list", "script file" or "match" lines in a class-map).
So I reread the manual for "copy startup-config running-config"
states "Specifies to replace the running-configuration file that currently resides on the ACE in RAM (volatile memory)."
it looks like that the behaviour is also a merge.
- What is the trick to edit a full configuration file on your workstation and load it to the ACE in the running configuration?
- Is there a "replace running-config" option or command?
I assume that copying to the startup config then rebooting the ACE would work, but I'd like to avoid that. Also putting lots of "no ..." statements in the proper order would be cumbersome and prone to errors; I'd rather have the system infer the dependencies among
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...