1) Dis-accociate the service profile from the current blade (keep an eye on the blade FSM for this to finish, about 10 mins)
2) Since you are replacing the blade, its good to decommission the blade (Equipment tab -> Select the blade -> Server maintenace -> Decommission (keep an eye on the FSM, might take another 5-10 mins for it to finish)
3) remove the blade physically from the slot
4) Put the new blade in
5) Wait for the blade to get discovered (you might get a "resolve slot" note and you might be required to accept the blade in the slot) for the discovery to start.
6) Once the blade is discovered, assocaite the SP back to the blade.
Thank. Customer digged deeper with other questions related to the same question:
q1. The blade is local booted with Raid-1 (mirrored with Protect Configuration) with Disk Scrub policy (MBR & BIOS scrub). In this case, I want to keep the 2 local drives' configuration.
Is the following correct?
I have to remove the Disk Scrub policy and the Protect Configuration option tied to the Local Disk Policy first before I dis-associate the Service Profile from the blade. I understand Protect Configuration is buggy in the older releases, is it OK now?
q2. With Host Firmware Package configured with BIOS policy, what will happen if I remove the Host Firmware Package with new BIOS firmware from the Service Package after I have successfully upgraded the BIOS firmware for the blade? Basically, customer is asking:
Do they need to have the Host Firmware Package associated with the Service Profile all the times knowing that the BIOS firmware had been upgraded when the Host Firmware Package was created the first time with the right BIOS firmware and the server had been rebooted before to take effect the new BIOS?
Q1/ If you want to keep the 2 local drives configuration, you'd rather remove the Scrub policy before disassociating the SP, otherwise all the bios settings will be set to default and you may loose the data in the hard drives.
Q2/ It's better to keep the Host firmware package for the current version in use on the UCSM, in case you need to recover from a corrupt bios. Instead, you can delete old firmware packages that may have been uploaded to UCSM.
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...