I'm triying to change a blade of chassis, but everytime that we make the change the OS into the blade its deleted; this is hapenning with all the blades that are trying to move. We don't have any Scrub policy applied.
Before removing a blade always run a decommision, even if you are going to use the same service profile:
Server - General - Server Maintenance.
When you insert it in another slot, it will run a re-acknowldge. If you are going to apply the same service profile with the local disk configuration that you mention, the data should stay there.
If the Protect Configuration box is checked, the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile.
When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile.
If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails.
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...