Abort "decommission process" for a non present device
Hello Ladies, Gents,
I've a very stupid issue and I don't know how to go on. So may be you've some additional ideas.
I joined a project where UCS is the plattform for the core business. Unfortunately the last service provide who was responsible for the system had a knowledge lack by administrating a UCS.
The stupid situation is, that there is a chassis shown in UCSM with ID 3, which dosen't physically exist. As far as I know they tried to add a chassis, plugged everything in and plugged it out because the chassis was needed somewhere else. The current status of Chassis 3 is: decommissioning... with communication error - so it hangs. Unfortunately I can't stop that process - cause I don't know how.
After stoping the process I'd like to use the Remove link to delete the chassis from the configuration.
It's absolutly crazy but it is a high critical business critical environment where I can't go on with "erase and reconfigure"
Guidelines for Removing and Decommissioning Chassis
Decommissioning a Chassis Decommissioning is performed when a chassis is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned chassis will be eventually recommissioned, a portion of the chassis' information is retained by Cisco UCS Manager for future use.
Removing a Chassis Removing is performed when you physically remove a chassis from the system. Once the physical removal of the chassis is completed, the configuration for that chassis can be removed in Cisco UCS Manager. You cannot remove a chassis from Cisco UCS Manager if it is physically present and connected. If you need to add a removed chassis back to the configuration, it must be reconnected and then rediscovered. During rediscovery Cisco UCS Manager will assign the chassis a new ID that may be different from ID that it held before.
I would try to remove the chassis; of this doesn't work, please open a TAC case !
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...