Cisco Prime Network Registrar 10.0 Administration Guide - Managing the Central Configuration [Cisco Prime Network Registrar 10.0] (2024)

From the Administration menu, choose Licenses under the User Access submenu to open the List Licenses page.

Add the details of the regional cluster.

Check the Generate new host identifier check box.

Click Register.

Activate

cluster name activate

Deactivate

cluster name deactivate

Resynchronize

cluster name resynchronize

Synchronize

cluster name sync

Update Replica Data

cluster name updateReplicaData

Remove Replica Data

cluster name removeReplicaData

Recover Data

cluster name recoverData

Poll Lease History

cluster name pollLeaseHistory

Get Lease History State

cluster name getLeaseHistoryState

Poll Subnet Utilization

cluster name pollSubnetUtilization

View Replica Data

cluster name viewReplicaData < class-name | cli-command > [-listbrief | -listcsv]

To access the CCM server properties, choose Manage Servers under the Operate menu to open the Manage Servers page.

Click Local CCM Server in the Manage Servers pane on the left. The Edit Local CCM Server page appears. This page displays all the CCM server attributes.

Modify the settings as per your requirement.

Click Save to save the CCM server attribute modifications.

From the Operate menu, choose Manage Servers under the Servers submenu to open the Manage Servers page (see Managing Servers).

Click the Local TFTP Server link in the left pane to open the Edit Local TFTP Server page.

To unset any attribute value, check the check box in the Unset? column.

Click Save to save the changes or Revert to cancel the changes.

cenAlarmVersion

1.3.6.1.4.1.9.9.311.1.1.2.1.2

SnmpAdminString (SIZE(1..16))

"1.2"

cenAlarmTimestamp

1.3.6.1.4.1.9.9.311.1.1.2.1.3

Timestamp

Time of last resource event state change

cenAlarmUpdatedTimeStamp

1.3.6.1.4.1.9.9.311.1.1.2.1.4

Timestamp

"current" time

cenAlarmInstanceID

1.3.6.1.4.1.9.9.311.1.1.2.1.5

SnmpAdminString (SIZE(1..20))

A unique id for the event - just hexadecimal digits

cenAlarmStatus

1.3.6.1.4.1.9.9.311.1.1.2.1.6

Integer32 (1..250)

1 (for Not acknowledged)

cenAlarmStatusDefinition

1.3.6.1.4.1.9.9.311.1.1.2.1.7

SnmpAdminString (SIZE(1..255))

"1,Not acknowledged"

cenAlarmType

1.3.6.1.4.1.9.9.311.1.1.2.1.8

Integer

Not Used

cenAlarmCategory

1.3.6.1.4.1.9.9.311.1.1.2.1.9

Integer32 (1..250)

100 (for Raw alarm)

cenAlarmCategoryDefinition

1.3.6.1.4.1.9.9.311.1.1.2.1.10

SnmpAdminString (SIZE(1..255))

"100,Raw alarm"

cenAlarmServerAddressType

1.3.6.1.4.1.9.9.311.1.1.2.1.11

InetAddressType

Cluster server address type - IPv4(1) or IPv6(2)

cenAlarmServerAddress

1.3.6.1.4.1.9.9.311.1.1.2.1.12

InetAddress

Cluster address (based on local cluster's object)

cenAlarmManagedObjectClass

1.3.6.1.4.1.9.9.311.1.1.2.1.13

SnmpAdminString (SIZE(1..255))

"Application"

cenAlarmManagedObjectAddressType

1.3.6.1.4.1.9.9.311.1.1.2.1.14

InetAddressType

Not used

cenAlarmManagedObjectAddress

1.3.6.1.4.1.9.9.311.1.1.2.1.15

InetAddress

Not used

cenAlarmDescription

1.3.6.1.4.1.9.9.311.1.1.2.1.16

OctetString (SIZE(1..1024))

Description formatted as " , "

cenAlarmSeverity

1.3.6.1.4.1.9.9.311.1.1.2.1.17

Integer32

0 for Clear, 2 for Warning, and 5 for Critical

cenAlarmSeverityDefinition

1.3.6.1.4.1.9.9.311.1.1.2.1.18

SnmpAdminString (SIZE(1..255))

String alarm severity, one of "0,Clear", "2,Warning", or "5,Critical"

cenAlarmTriageValue

1.3.6.1.4.1.9.9.311.1.1.2.1.19

Integer32 (0..100)

Not used

cenEventIDList

1.3.6.1.4.1.9.9.311.1.1.2.1.20

OctetString (SIZE(1..1024))

Not used

cenUserMessage1

1.3.6.1.4.1.9.9.311.1.1.2.1.21

SnmpAdminString (SIZE(1..255))

Name of monitored resource

cenUserMessage2

1.3.6.1.4.1.9.9.311.1.1.2.1.22

SnmpAdminString (SIZE(1..255))

Server name (dhcp, dns, cdns, ...)

cenUserMessage3

1.3.6.1.4.1.9.9.311.1.1.2.1.23

SnmpAdminString (SIZE(1..255))

"Network Registrar"

cenAlarmMode

1.3.6.1.4.1.9.9.311.1.1.2.1.24

Integer

3 (event)

cenPartitionNumber

1.3.6.1.4.1.9.9.311.1.1.2.1.25

Guage (0..100)

Not used

cenPartitionName

1.3.6.1.4.1.9.9.311.1.1.2.1.26

SnmpAdminString (SIZE(1..255))

Not used

cenCustomerIdentification

1.3.6.1.4.1.9.9.311.1.1.2.1.27

SnmpAdminString (SIZE(1..255))

Not used

cenCustomerRevision

1.3.6.1.4.1.9.9.311.1.1.2.1.28

SnmpAdminString (SIZE(1..255))

Not used

cenAlertID

1.3.6.1.4.1.9.9.311.1.1.2.1.29

SnmpAdminString (SIZE(1..20))

Same as cenAlarmInstanceID

Click the desired trap name in the Traps pane to open the Edit Trap Configuration page

Modify the name, mode, or threshold percentages.

Click the on option for the enabled attribute to enable the trap configuration.

Click Save for the changes to take effect.

To edit the alarm poll interval, you need to edit the user preferences by going to User Preferences under the Settings drop-down list (at the top of the main page).

After making the user preference settings, click Modify User Preferences.

Click the Alarms icon at the top of the web UI to open the Alarms page.

Select the Alarm for which you want to reset the peak value.

Click the Reset Alarm button to clear the peak value.

Click the Alarms icon at the top of the web UI to open the Alarms page.

Click Export to CSV.

The File Download pop-up window displays. Click Save.

In the Save As pop-up window, choose the location you want to save the file to and click Save.

At the Boston local cluster, log in as superuser (usually admin ).

In Basic mode, from the Administration menu, choose Administrators .

Add the local cluster administrator (with superuser access)—On the List/Add Administrators page:

1. Click the Add Administrators icon in the Administrators pane, enter example-cluster-admin in the Name field.

2. Enter exampleadmin in the Password and Confirm Password fields, then click Add Admin.

3. Check the Superuser check box.

4. Do not choose a group from the Groups list.

5. Click Save .

Add the local zone administrator on the same page:

1. Click the Add Administrators icon in the Administrators pane, enter example-zone-admin in the Name field, and examplezone in the Password and Confirm Password fields, then click Add Admin.

2. Click Add in the Groups section of the Edit Administrator page to open the Groups window. Select ccm-admin-group , dns-admin-group , and host-admin-group and click Select. The selected groups appear under the Groups section of the Edit Administrator page. The dns-admin-group is already predefined with the dns-admin role to administer DNS zones and servers. The ccm-admin-group guarantees that the example-zone-admin can set up the example-host-admin with a constrained role later on. The host-admin-group is mainly to test host creation in the zone.

3. Click Save .

Add the local host administrator on the same page:

1. Click the Add Administrators icon in the Administrators pane, enter example-host-admin in the Name field, and examplehost in the Password field, then click Add Admin.

2. Do not choose a group at this point. (The example-zone-admin will later assign example-host-admin to a group with a constrained role.)

3. Click Save.

   Note	For a description on how to apply constraints to the administrator, see the Create a Host Administrator Role with Constraints.

At the local cluster, log out as superuser, then log in as the example-cluster-admin user with password exampleadmin . Because the administrator is a superuser, all features are available.

Click Advanced to enter Advanced mode.

From the Design menu, choose Subnets under the DHCPv4 submenu to open the List/Add Subnets page.

On the List/Add Subnets page, enter the boston.example.com subnet address:

1. Click the Add Subnets icon in the Subnets pane, enter 192.168.50 in the Address field.

2. Choose 24 in the mask drop-down list—This subnet will be a normal Class C network.

3. Leave the Owner, Region, and Address Type fields as is. Add description if desired.

4. Click Add Subnet .

Click the 192.168.50.0/24 address to open the Edit Subnet page.

In the IP Ranges fields, enter the static address range:

1. Enter 100 in the Start field. Tab to the next field.

2. Enter 200 in the End field.

3. Click Add IP Range . The address range appears under the fields.

Click Save .

Click Address Space to open the View Unified Address Space page. The 192.168.50.0/24 subnet should appear in the list. If not, click the Refresh icon.

As the example-zone-admin user, click Advanced to enter Advanced mode.

From the Design menu, choose Hosts under the Auth DNS submenu. This opens the List/Add Hosts for Zone page. You should see boston.example.com and example.com in the Select Zones box on the left side of the window.

Click example.com in the list of zones.

Add the first static host with address 192.168.50.101:

1. Enter userhost101 in the Name field.

2. Enter the complete address 192.168.50.101 in the IP Address(es) field. Leave the IPv6 Address(es) and Alias(es) field blank.

3. Ensure that the Create PTR Records? check box is checked.

4. Click Add Host .

Add the second host, userhost102 , with address 192.168.50.102 , in the same way. The two hosts should now appear along with the nameserver host on the List/Add Hosts for Zone page.

Log out as the example-zone-admin user and log in as the example-cluster-admin user (with password exampleadmin ).

Click Advanced to enter Advanced mode.

From the Administration menu, choose Roles under the User Access submenu to open the List/Add Administrator Roles page.

Add the example-host-role:

1. Click the Add Role icon in the Roles pan to open the Add Roles dialog box.

2. Enter example-host-role in the Name field.

3. Click Add Role. The example-host-role should now appear in the list of roles on the List/Add Administrator Roles page.

Add the constraint for the role:

1. Click Add Constraint .

2. On the Add Role Constraint for Role page, scroll down to Host Restrictions.

3. For the all-forward-zones attribute, click the false radio button.

4. For the zones attribute, enter boston.example.com .

5. For the ipranges attribute, enter the range 192.168.50.101–192.168.50.200 .

6. The zone-regexpr and host-regexpr attribute fields are for entering regular expressions to match zones and hosts, respectively, in regex syntax. (See the following table for the commonly used regex values.)

   Table 7. Common Regex Values

   Value	Matches
   . (dot)	Any character (a wildcard). Note that to match a literal dot character (such as in a domain name), you must escape it by using a backslash (\ ), such that \.com matches.com.
   \ char	Literal character (char) that follows, or the char has special meaning. Used especially to escape metacharacters such as the dot (. ) or another backslash. Special meanings include \d to match decimal digits, \D for nondigits, \w for alphanumerics, and \s for whitespace.
   char?	Preceding char once or not at all, as if the character were optional. For example, example\.?com matches example.com or examplecom.
   char*	Preceding char zero or more times. For example, ca*t matches ct, cat, and caaat. This repetition metacharacter does iterative processing with character sets (see [ charset] ).
   char+	Preceding char one or more times. For example, ca+t matches cat and caaat (but not ct).
   [ charset]	Any of the characters enclosed in the brackets (a character set). You can include character ranges such as [a–z] (which matches any lowercase character). With the * repetition metacharacter applied, the search engine iterates through the set as many times as necessary to effect a match. For example, a[bcd]*b will find abcbd (by iterating through the set a second time). Note that many of the metacharacters (such as the dot) are inactive and considered literal inside a character set.
   [^ charset]	Anything but the charset, such that [^a-zA-Z0-9] matches any nonalphanumeric character (which is equivalent to using \W ). Note that the caret outside a character set has a different meaning.
   ^	Beginning of a line.
   $	End of a line.

7. Click Add Constraint . The constraint should have an index number of 1.

Click Save .

As example-cluster-admin, still in Advanced mode, from the Administration menu, choose Groups submenu to open the List/Add Administrator Groups page.

Create the example-host-group and assign the example-host-role to it:

1. Click the Add Groups icon in the Groups pane, enter example-host-group in the Name field.

2. From the Base Role drop-down list, choose example-host-role .

3. Click Add Group .

4. Add a description such as Group for the example-host-role , then click Save.

Log out as example-cluster-admin, then log in as the example-zone-admin user (with password examplezone ).

As example-zone-admin, assign the example-host-group to the example-host-admin:

1. In Basic mode, from the Administration menu, choose Administrators .

2. On the List/Add Administrators page, click example-host-admin to edit the administrator.

3. On the Edit Administrator page, choose example-host-group in the Available list, then click << to move it to the Selected list.

4. Click Save . The example-host-admin should now show the example-host-group in the Groups column on the List/Add Administrators page.

At the local cluster, log out as example-zone-admin, then log in as example-host-admin (with password examplehost ).

Click Advanced to enter Advanced mode.

From the Design menu, choose Hosts from the Auth DNS submenu.

On the List/Add Hosts for Zone page, try to enter an out-of-range address (note the range of valid addresses in the Valid IP Ranges field):

1. Enter userhost3 in the Name field.

2. Deliberately enter an out-of-range address (192.168.50.3 ) in the IP Address(es) field.

3. Click Add Host . You should get an error message.

Enter a valid address:

1. Enter userhost103 .

2. Enter 192.168.50.103 in the IP Address(es) field.

3. Click Add Host . The host should now appear with that address in the list.

Log into the regional cluster as superuser.

From the Administration menu, choose Administrators under the User Access submenu to open the List/Add Administrators page for the local cluster version of this page, which is essentially identical.

Click the Add Administrators icon in the Administrators pane, enter example-regional-admin in the Name field, then examplereg in the Password and Confirm Password fields in the Add Admin dialog box, then click Add Admin.

Click Add in the Groups section of the Edit Administrator page to open the Groups window. Select central-cfg-admin-group (for cluster administration) and regional-admin-group (for user administration) and click Select. The selected groups appear under the Groups section of the Edit Administrator page.

Click Save .

Log out as superuser, then log in as example-regional-admin with password examplereg . Note that the administrator has all but host and address space administration privileges.

From the Administration menu, choose Administrators under the User Access submenu to open the List/Add Administrators page.

Click the Add Administrators icon in the Administrators pane, enter example-cfg-admin in the Name field, then cfgadmin in the Password and Confirm Password fields in the Add Admin dialog box, then click Add Admin.

Click Add in the Groups section of the Edit Administrator page to open the Groups window. Select central-cfg-admin-group and regional-addr-admin-group and click Select. The selected groups appear under the Groups section of the Edit Administrator page.

Click Save . The example-cfg-admin now appears with the two groups assigned.

Log out as example-regional-admin, then log in as example-cfg-admin with password cfgadmin .

From the Operate menu, choose Manage Clusters from the Servers submenu to open the List/Add Remote Clusters page.

Click the Add Manage Clusters icon in the Manage Clusters pane .

On the Add Cluster dialog box, create the Boston cluster based on data provided by its administrator:

1. Enter Boston-cluster in the name field.

2. Enter the IPv4 address of the Boston server in the IPv4 Address field.

3. Enter the IPv6 address of the Boston server in the IPv6 Address field.

4. Enter example-cluster-admin in the Admin Name field, then exampleadmin in the Admin Password field.

5. Enter in the SCP Port field the SCP port to access the cluster as set at installation (1234 is the preset value).

6. Click Add Cluster .

Create the Chicago cluster in the same way, except use Chicago-cluster in the name field, enter the remaining values based on data provided by the Chicago administrator, then click Add Cluster . The two clusters should now appear on the List/Add Remote Clusters page.

Connect to the Boston cluster. Click the Go Local icon next to Boston-cluster. If this opens the local cluster Manage Servers page, this confirms the administrator connectivity to the cluster. To return to the regional cluster web UI, click the Go Regional icon.

Connect to the Chicago cluster to confirm the connectivity in the same way.

Confirm that you can replicate data for the two forward zones from the Boston cluster synchronization:

1. From the Operate menu, choose View Replica Data under the Servers submenu.

2. On the View Replica Class List page, click Boston-cluster in the Select Cluster list.

3. In the Select Class list, click Forward Zones .

4. Click Replicate Data.

5. Click View Replica Class List . On the List Replica Forward Zones for Cluster page, you should see the boston.example.com and example.com zones.

As example-cfg-admin, from the Deploy menu, choose Router List under the Router Configuration submenu.

On the List/Add Routers page, click the Add Router icon in the Router List pane.

On the Add Router dialog box, add the router based on data from its administrator:

1. Give the router a distinguishing name in the name field. For this example, enter router-1 .

2. Enter the router description in the description field.

3. Enter the management interface address for the router in the address field.

4. Enter the IPv6 management interface address for the router in the ip6address field.

5. Choose a owner and a region.

6. Click Add Router . The router should now appear on the List/Add Routers page.

Confirm that the router is created. Click Router Tree to view the hierarchy of router interfaces for router-1 on the View Tree of Routers page.

Configure a DHCP relay agent for the router:

1. Create a new interface for the router.

2. Click the interface names on the View Tree of Routers page to open the Edit Router Interface page. (Alternatively, from the List/Add Routers page, click the Interfaces icon associated with the router, then click the interface name on the List Router Interfaces for Router page.)

3. On the Edit Router Interface page, enter the IP address of the DHCP server in the ip-helper field.

4. Click Save at the bottom of the page.

Confirm with the router administrator that the DHCP relay agent was successfully added.

Log out as example-cfg-admin, then log in as example-regional-admin .

From the Administration menu, choose Administrators under the User Access submenu.

On the List/Add Administrators page, click example-cfg-admin from the Administrators pane.

On the Edit Administrator page, click central-dns-admin-group in the Groups Available list, then move it (using << ) to the Selected list. The Selected list should now have central-cfg-admin-group, regional-addr-admin-group, and central-dns-admin-group.

Click Save . The change should be reflected on the List/Add Administrators page.

Log out as example-regional-admin, then log in as example-cfg-admin .

From the Design menu, choose Forward Zones under the Auth DNS submenu.

Click the Add Forward Zone icon in the Forward Zones pane .

On the Add Zone dialog box, enter:

1. Name —chicago.example.com .

2. Nameserver FQDN —ns1 .

3. Contact E-mail —hostadmin .

4. Nameservers —ns1 (click Add Nameserver ).

5. Click Add DNS Zone .

Click the Reverse Zones submenu.

On the List/Add Reverse Zones page, create the 60.168.192.in-addr.arpa reverse zone for the Chicago zone, with the proper attributes set.

As example-cfg-admin, from the Design menu, choose Views under the Auth DNS submenu to view the List/Add Zone Views page.

On the List/Add Zone Views page, pull the zone from the replica database:

1. Click the Pull Data icon in the Views pane .

2. On the Select Replica DNS View Data to Pull dialog box, leave the Data Synchronization Mode defaulted as Update, then click Report to open the Report Pull Replica Zone Data page.

3. Notice the change sets of data to pull, then click Run .

4. On the Run Pull Replica Zone Data page, click OK .

On the List/Add Zone Views page, notice that the Boston cluster zone distribution is assigned an index number (1 ) in the Name column. Click the number.

On the Edit Zone Views page, in the Primary Server field, click Boston-cluster. (The IP address of the Boston-cluster becomes the first master server in the Master Servers list.)

Because we want to make the Chicago-cluster DNS server a secondary server for the Boston-cluster:

1. Click Add Server in the Secondary Servers area.

2. On the Add Zone Distribution Secondary Server page, choose Chicago-cluster in the Secondary Server drop-down list.

3. Click Add Secondary Server .

On the Edit Zone Distribution page, in the Forward Zones area, move chicago.example.com to the Selected list.

In the Reverse Zones area, move 60.168.192.in-addr.arpa to the Selected list.

Click Modify Zone Distribution .

As example-cfg-admin, from the Design menu, choose Subnets under the DHCPv4 submenu to open the List/Add Subnets page. You should see the subnets created by adding the router (in the Add a Router and Modify an Interface).

Create an additional subnet, 192.168.70.0/24 by clicking the Add Subnets icon in the Subnets pane:

1. Enter 192.168.70 (the abbreviated form) as the subnet network address in the Address/Mask field.

2. Leave the 24 (255.255.255.0) selected as the network mask.

3. Click Add Subnet .

Click Address Space to confirm the subnet you created.

On the View Unified Address Space page, click Pull Replica Address Space .

On the Select Pull Replica Address Space page, leave everything defaulted, then click Report .

The Report Pull Replica Address Space page should show the change sets for the two subnets from the clusters. Click Run .

Click OK . The two pulled subnets appear on the List/Add Subnets page.

As example-cfg-admin, from the Design menu, choose Policies under the DHCP Settings submenu.

On the List/Add DHCP Policies page, click the Add Policies icon in the Policies pane .

On the Add DHCP Policy dialog box, create a central policy for all the local clusters:

1. Enter central-policy-1 in the Name field. Leave the Offer Timeout and Grace Period values as is.

2. Click Add DHCP Policy.

3. On the Edit DHCP Policy page, under the DHCPv4 Options section, choose dhcp-lease-time [51] (unsigned time) from the Name drop-down list, and then enter 2w (two weeks) for the lease period in the Value field.

4. Click Add Option .

5. Click Save.

Push the policy to the local clusters:

1. Select the policy, central-policy-1 and click the Push button .

2. On the Push DHCP Policy Data to Local Clusters page, leave the Data Synchronization Mode as Ensure . This ensures that the policy is replicated at the local cluster, but does not replace its attributes if a policy by that name already exists.

3. Click Select All in the Destination Clusters section of the page.

4. Click << to move both clusters to the Selected field.

5. Click Push Data to Clusters .

6. View the push operation results on the View Push DHCP Policy Data Report page.

As the example-cfg-admin user, from the Design menu, choose Scope Templates under the DHCPv4 submenu.

On the List/Add DHCP Scope Templates page, click the Add Scope Templates icon in the Scope Templates pane . Enter scope-template-1 in the Name field, then click Add DHCP Scope Template.

The template should appear on the List/Add DHCP Scope Templates page. Set the basic properties for the scope template—Enter or choose the following values in the fields:

1. Scope Name Expression —To autogenerate names for the derivative scopes, concatenate the example-scope string with the subnet defined for the scope. To do this, enter (concat “example-scope-” subnet) in the field (including the parentheses).

2. Policy —Choose central-policy-1 in the drop-down list.

3. Range Expression —Create an address range based on the remainder of the subnet (the second through last address) by entering (create-range 2 100) .

4. Embedded Policy Option Expression —Define the router for the scope in its embedded policy and assign it the first address in the subnet by entering (create-option “routers” (create-ipaddr subnet 1)) .

Click Save .

As the example-cfg-admin user, from the Deploy menu, choose Failover Pairs under the DHCP submenu.

On the List/Add DHCP Failover Pairs page, click the Add Failover Pair icon in the Failover Pairs pane.

On the Add DHCP Failover Pair dialog box, enter or choose the following values:

1. Failover Pair Name —Enter central-fo-pair .

2. Main Server —Click Boston-cluster .

3. Backup Server —Click Chicago-cluster .

4. Scope Template —Click scopetemplate-1 .

5. Click Add Failover Pair .

Synchronize the failover pair with the local clusters:

1. On the List/Add DHCP Failover Pairs page, click the Report icon in the Synchronize column.

2. On the Report Synchronize Failover Pair page, accept Local Server as the source of network data.

3. Accept Main to Backup as the direction of synchronization.

4. Accept the operation Update .

5. Click Report at the bottom of the page.

6. On the View Failover Pair Sync Report page, click Run Update .

7. Click Return .

Confirm the failover configuration and reload the server at the Boston cluster:

1. On the List/Add DHCP Failover Pairs page, click the Go Local icon next to Boston-cluster.

2. On the Manage DHCP Server page, click the Reload icon.

3. Click the Go Regional icon at the top of the page to return to the regional cluster.

Confirm the failover configuration and reload the server at the Chicago cluster in the same way.