- Preface
- Introduction
- UCS Central Implementation: Approaches and Challenges
- Small Cisco UCS Central Environment
- Medium Cisco UCS Central Environment
- Large Cisco UCS Central Environment
- Sizing and Scaling Considerations
- Domain Groups
- Registration
- Migrating Brownfield to Greenfield
- Organization
- Understanding Policy Differences in Cisco UCS Manager and Cisco UCS Central
- Configuration
- Deploying Global VLANs and VSANs
- Pools
- Authentication
- Firmware Management
- Backup and Import
- High Availability
- General Best Practices
- UCS Central Internal Processes Defined
- UCS Central Communications - Required Ports
- Creating a Testing & Development Environment
- Online Resources
Registration
Cisco UCS Manager-Cisco UCS Central Registration
Name Space Conflicts
![]() Caution | Be careful during periods when registered domains are unregistered or are unintentionally deregistered. |
Any global objects that are locally cached when unregistered may cause namespace conflicts when reregistered with Cisco UCS Central. A problem occurs if the identical name still exists for an object owned by Cisco UCS Central. To resolve such naming conflicts, and return to global control of the local object, use the option on the local object.
![]() Note | The Use Global operation overwrites any changes that were performed on the local policy during the unregistered state. |