The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter explains how to configure owners and regions that can be applied to DHCP address blocks, subnets, prefixes, links, and zones.
You can create owners to associate with address blocks, subnets, prefixes, links, and zones. You can list and add owners on a single page. Creating an owner involves creating a tag name, full name, and contact name.
nrcmd> owner owner-1 create "First Owner" contact="Contact at owner-1"
You can create regions to associate with address blocks, subnets, prefixes, links, and zones. You can list and add regions on a single page. Creating a region involves creating a tag name, full name, and contact name.
Use region tag create name . For example:
nrcmd> region region-1 create "Boston Region" contact="Contact at region-1"
As a regional or local CCM administrator, you can:
Each of these functions involves having at least one regional CCM administrator subrole defined (see Roles, Subroles, and Constraints).
The following table describes the subroles required for these operations.
Central Administrator Management Action |
Required Regional Subroles |
---|---|
Create, modify, pull, push, or delete owners or regions |
owner-region |
You can push owners or regions to, and pull them from, local clusters on the List/Add Owners page or List/Add Regions page, respectively, in the regional cluster web UI.
Pushing owners or regions to local clusters involves choosing one or more clusters and a push mode.
When you pull an owner or region, you are actually pulling it from the regional cluster replica database. Creating the local cluster initially replicates the data, and periodic polling automatically updates the replication. However, to ensure that the replica data is current with the local cluster, you can force an update before pulling the data.
Step 1 | From the Administration menu in the regional cluster web UI, choose Owners or Regions under the Settings submenu. | ||
Step 2 | On the List/Add Owners or List/Add Regions page, click the Pull Replica icon in the left pane. This opens the Select Replica Owner Data to Pull or Select Replica Region Data to Pull page. | ||
Step 3 | Click the Replicate icon in the Update Replica Data column for the cluster. (For the automatic replication interval, see Replicating Local Cluster Data.) | ||
Step 4 | Choose a
replication mode using one of the Mode radio buttons.
Leave the default Replace mode enabled, unless you want to preserve any existing owner or region properties at the local cluster by choosing Ensure.
| ||
Step 5 | Click Pull All Owners or Pull All Regions next to the cluster, or expand the cluster name and click Pull Owner or Pull Region to pull an individual owner or region in the cluster. | ||
Step 6 | On the Report Pull Replica Owners or Report Pull Replica Regions page, click Run. | ||
Step 7 | On the Run Pull Replica Owners or Run Pull Replica Region page, view the change set data, then click OK. You return to the List/Add Owners or List/Add Regions page with the pulled owners or regions added to the list. |