When the reconfiguration is done, the OA generates blade remove events for the first two blades, resulting in VCM treating the AA partition as having been removed. Then the OA generates a blade add event for the first blade that identifies it as a single-blade partition, and likewise for the second blade. No events (remove or add) occur for the third and fourth blades because the C and D partitions are not affected by the reconfiguration.

The profile assigned to the first bay is now shown as assigned to the A partition and is applied to the first blade. The profile assigned to the second bay is now shown as assigned to the B partition and is applied to that blade. There is no change in the profiles assigned to the third and fourth blades.

Example 3: Reconfiguration from ABCD to ABCC

The current profile assigned to the first bay is applied to the A partition, the profile assigned to the second bay is applied to the B partition, the profile assigned to the third bay is applied to the C partition, and the profile assigned to the fourth bay is applied to the D partition.

When the reconfiguration is done, the OA generates blade remove events for the third and fourth blades, resulting in VCM treating the C and D partitions as having been removed. Then the OA generates blade add events for the last two blades that identify those two blades as belonging to one partition (the CC partition).

The profile assigned to the third bay is now shown as assigned to the CC partition and is applied to the third and fourth blades. The profile assigned to the fourth bay is now shown as covered and is not used. There is no change in the profiles assigned to the first and second blades.

Appendix A: Using Virtual Connect with nPartitions 291