02-06-2015 09:39 AM - edited 03-01-2019 12:01 PM
I am working on understanding the impact of an acknowledge chassis process. Documentation would be great of this process.
Questions
Will traffic through the chassis stop?
Will I loose connection to the SAN for my VMs?
Will the blades in the chassis go through a reboot?
If so will I be able to move VM's to a different blade during that process and not experience an outage for the VM's storage?
Will both Fabric Interconnects reboot?
If so will they reboot at the same time or staggered?
How will this affect my VMware environment running on this Chassis?
Thanks for any information.
Sam
Solved! Go to Solution.
02-07-2015 02:28 AM
answers inline wdey>>
Will traffic through the chassis stop?
wdey>> yes, for about 40+- seconds; most OS can tolerate this; however, as Steven mentions, it is best practise to take no risk and vmotion off the VM's from this chassis
Will I loose connection to the SAN for my VMs?
wdey>> yes, see above
Will the blades in the chassis go through a reboot?
wdey>> no !
If so will I be able to move VM's to a different blade during that process and not experience an outage for the VM's storage?
wdey>> yes, to a different blade in another chassis
Will both Fabric Interconnects reboot?
wdey>> No
If so will they reboot at the same time or staggered?
How will this affect my VMware environment running on this Chassis?
The question is: when is it necessary to ack the chassis ? in my opinion only in rare cases, eg. selecting port channel between IOM and FI !
02-07-2015 02:27 AM
Acknowledging an existing working chassis will cause everything within the chassis and both IOM modules to restart. You will have no network or San traffic through the affected chassis during the acknowledge process. You should vmotion off all the blades operating in the chassis you want to acknowledge and then they won't be impacted.
I retract what I said earlier. Acking a chassis won't reboot the blades but they will lose connectivity for 30-60 seconds. Note that will include SAN traffic. Plan accordingly.
02-07-2015 02:28 AM
answers inline wdey>>
Will traffic through the chassis stop?
wdey>> yes, for about 40+- seconds; most OS can tolerate this; however, as Steven mentions, it is best practise to take no risk and vmotion off the VM's from this chassis
Will I loose connection to the SAN for my VMs?
wdey>> yes, see above
Will the blades in the chassis go through a reboot?
wdey>> no !
If so will I be able to move VM's to a different blade during that process and not experience an outage for the VM's storage?
wdey>> yes, to a different blade in another chassis
Will both Fabric Interconnects reboot?
wdey>> No
If so will they reboot at the same time or staggered?
How will this affect my VMware environment running on this Chassis?
The question is: when is it necessary to ack the chassis ? in my opinion only in rare cases, eg. selecting port channel between IOM and FI !
10-12-2023 01:42 AM
Could I perform an acknowledge IOM one at a time? I look at this option in each IO Module and then acknowledge the chassis. Has anyone tried to do this? I will do the fabric interconnect migration from 6200 to 6400 family.
10-13-2023 07:10 AM
That is OLD information. The IOMs can be acknowledged one at a time since UCSM 2.2(4) which was released 2015 July.
Cisco UCS Manager Release 2.2(4) introduces the ability to acknowledge a specific IO module in a chassis.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide