Network Registrar Help

Close Window

Address blocks provide an organizational structure for addresses used across the network. Address blocks can consist of static or dynamic addresses allocated to DHCP servers for lease assignment. An address block can have any number of child address blocks and can culminate in one or more child subnets. The address block administrator is responsible for these objects. This administrator can create parent and child address blocks or subnets, which are always the leaf nodes of the address space. Static subnets can be further subdivided into one or more IP address ranges.

The address block administrator role manages address space at a higher level than that of specific subnet or static address allocations. This is actually a middle manager role, as there is likely to be a higher authority handing out address blocks to the system.

• View the unified address space
• Manage address blocks
• Manage subnets
• Manage owners
• Manage regions
• Manage address destinations
• Query and view subnet utilization
• Query and view lease history
• Set rules for and check data consistency

You can view the static and dynamic address space on the View Unified Address Space page. At the local cluster, you must be an addrblock-admin; at the regional cluster, you must be a regional-addr-admin.

This unified address space is a hierarchical tree of address blocks and subnets, sorted in IP address order. You can choose the level of depth to display in the tree. You can also expand and collapse nodes, which recursively expands or collapses all child nodes. If you pick a new level, this overrides the previous expansion or collapsing.

An address block is an aggregate of IP addresses based on a power-of-two address space that can be delegated to an authority. For example, the 192.168.0.0/16 address block (part of the RFC 1918 private address space) includes 2 to the 16th (or 65536) addresses. Address blocks can be further divided into child address blocks and subnets. For example, you might want to delegate the 192.168.0.0/16 address block further into four child address blocks -- 192.168.64.0/17, 192.168.128.0/17, 192.168.192.0/17, and 192.168.256.0/17.

A subnet is the leaf node of the address space and cannot be further subdivided. Also, an address block and subnet cannot have the same addresses. For example, if you create the 192.168.50/24 subnet, you can subsequently create only three child address blocks or subnets from the 192.168.0.0/16 space-192.168.64.0/18, 192.168.128/18, and 192.168.192.0/18. You cannot further subdivide or delegate the 192.168.50.0/24 subnet. Subnets can have one or more defined address ranges. Address blocks cannot have address ranges. When you create an address range for a subnet using the Web UI, it becomes a static range, meaning that it cannot be allocated dynamically using DHCP. However, the Web UI shows any dynamic ranges defined by DHCP scopes for the subnet. Displaying the ranges as such indicates where overlaps may have occurred between assigning static addresses for the address space and dynamic addresses for scopes.

The address space view shows the hierarchy of address block and subnets and their parent-child relationships. The hierarchy does not go down to the level of address ranges for each subnet. These are displayed when you access the subnet. You can expand and collapse each level in the tree by clicking the + and - symbols next to each address.

The structure of the list is designed to keep the hierarchical view intact. Scrolling through long and deeply embedded lists displays ancestor nodes at the top of the list that are hierarchically organized. These ancestor nodes are in addition to the number of visible entries determined by the value in the Change Page Size field. You can navigate at each level of the hierarchy by clicking the arrow icons to the right of the header entry names. The arrow icons appear only if the node is expanded -- an up arrow means that there are children for the node that precede the first one displayed; a down arrow means that there are child nodes following the ones displayed.

Address spaces that were assigned dynamically are indicated by a D (for "Delegated") in the Type column on this page. Note that you cannot delete these delegated address blocks until you reclaim them.

Note that if VPNs are predefined, you can choose which VPN this address space is in, from the drop-down list next to Select VPN. If you choose [none], the address space is in no particular VPN.

Choose from the line of numbers under the Address/Mask column to set the level of depth. The numbers range from zero to ten levels of depth, or you can choose All for all levels. The number you choose depends on how much of the hierarchy you want to display. You may not want to see all levels for a deep hierarchy. The Type, Owner, Region, and Address Type columns identify if the address space is an address block or subnet and if the address space has an owner, region, or address type.

The View icon () in the Current Usage column opens the View Current Utilization Report page.

On this page, you can pull the address spaces from the regional replica database of the local cluster address spaces. To do so, click Pull Replica Address Space to open the Select Pull Replica Address Space page.

This page also lets you edit an address block or edit a subnet by clicking its network address in the Address/Mask column. Click the Refresh icon () after you return to this page after adding or editing address blocks or subnets. Note that the page shows only up to the number of entries indicated by the Change Page Size value; you may need to scroll through the entries using the arrow icons to display any new entries you add, or increase the Change Page Size value.

This page appears if you click the View icon () in the Current Usage column of the View Unified Address Space, List/Add Address Blocks, or List/Add Subnets page. It is a read-only page that shows the details of the current address utilization in address blocks, subnets, and scopes.

The Utilization Detail column items are expandable so that you can view the scope data for an address block or subnet. If you click the address block, subnet, or scope name in this column, this opens the View Utilization Detail page.

The other columns that appear for the report are:

Column	Description
Type	Whether the address space is an address block, subnet, or scope.
Active Dynamic	Addresses that are part of a dynamic range managed by DHCP and that are currently leased, but not reserved.
Free Dynamic	Addresses that are not currently leased.
Active Reserved	Addresses that are part of a dynamic range and are reserved.
View Utilization History	This appears for the regional cluster only. Clicking the Report icon () opens the List Subnet Utilization Records page for the last ten days.

This page appears if you click the address block, subnet, or scope name on the View Current Usage column of the View Current Utilization Report page. It is a read-only page that shows detailed address utilization attributes for the address block, subnet, or scope.

The utilization attributes show their values and data types, and are:

To return to the View Current Utilization Report page, click Return to Tree View.

At the regional cluster only, this page appears if you click Pull Replica Address Space on the View Unified Address Space page. It shows a table of the data to pull and the synchronization effects when choosing the Update, Complete, or Exact Data Synchronization Mode. Based on this table, click the radio button for the applicable synchronization mode, then click Report or Cancel. Clicking Report opens the Report Pull Replica Address Space page.

NOTE: Pulling replica address space from a local cluster where subnets were removed does not clear the server name on the subnet. Although the subnet is no longer used, it is still considered allocated to the server. Hence, the delete operation does not appear for the subnet, so that you cannot delete the subnet from the regional cluster. To push or re-allocate the subnet to a different cluster, or remove it from the regional cluster, you must first reclaim the subnet. This clears the reference to the local server.

At the regional cluster only, this page appears when you click Report on the Select Pull Replica Address Space page. To run the report, click Run. To cancel, click Cancel. If you run the report, click OK on the Run Pull Replica Address Space page to return to the View Unified Address Space page.

An address block is a range of IP addresses that are within properly aligned power-of-two boundaries and that can be subdivided by further address blocks and subnets. An address block consists of an IP address and a netmask. This network address is set aside for DHCP leases or statically assigned host addresses.

NOTE: The DHCP server also uses address blocks to manage subnet allocation for on-demand address pools. See the DHCP chapters of the Network Registrar User's Guide for further information on this feature. Address blocks used for this purpose must be created in the CLI. The unified address view in the Web UI also displays these DHCP-related address blocks, but does not provide an edit link to them, because they have been delegated in their entirety to the DHCP server. They should not be further subdivided by an administrator for subnet allocation. The DHCP server automatically handles these address blocks as it receives subnet requests.

Delegated address blocks are identified with a D (for "Delegated") next to the address block name on this page. Note that you cannot delete the delegated address block until you reclaim it.

The List/Add Address Blocks page displays any created address blocks and lets you add additional ones, unless you are a read-only administrator. Once created, you can also edit and delete an address block from this page.

Note that if VPNs are predefined, you can choose which VPN to place all the address blocks on this page, from the drop-down list next to Select VPN. If you choose [none], the address blocks are placed in no particular VPN.

The fields and choices you use to add an address block are:

Field/Choice	Description
Address/Mask	Enter the network address, in quad format, such as 192.168.50.0, and choose the network prefix mask from the drop-down list. If you choose a mask of 24, for example, the network address/mask would be 192.168.50.0/24. Required.
Owner	Owner of the address block. Choose from the predefined owners in the drop-down list, as set up by clicking Owners on the Secondary Navigation bar. Optional.
Region	Administrative region for the address block. Choose from the predefined regions in the drop-down list, as set up by clicking Regions on the Secondary Navigation bar. Optional.
Address Type	Type of address. Choose from the predefined address types in the drop-down list, as set up by clicking Address Types on the Secondary Navigation bar. Optional.
Current Usage	View the current address usage of the address block. Click the View icon () to open the View Current Utilization Report page.
Description	Description of the address block. Optional.

After you complete these fields, click Add Address Block. This adds the address block to the bottom of the list so that you can edit or delete it. You can return to the View Unified Address Space page, refresh the page, and view the newly created address block in the tree.

You can edit an address block from the View Unified Address Space or List/Add Address Blocks page, unless you are a read-only administrator. Click the network address of the address block on one of these pages.

The name of the page identifies the name of the current address block. If the address block has a parent address block, it is identified under the Parent Block heading. The bottom of the page lets you add child address blocks and child subnets.

The fields on the page are:

You can also go to the View Unified Address Space page, refresh the page, and view the modified address block in the tree.

Subnets that represent the address ranges used by the DHCP server are automatically created from the DHCP scope configuration. You must manually create subnets for static IP address assignment.

The List/Add Subnets page displays any created subnets and lets you add additional ones. Once created, you can also edit and delete a subnet from this page, unless you are a read-only administrator.

Note that if VPNs are predefined, you can choose which VPN to place all the subnets on this page, from the drop-down list next to Select VPN. If you choose [none], the subnets are placed in no particular VPN.

The fields you use to add an address block are:

Field	Description
Address/Mask	Enter the network address, in quad format, such as 192.168.50.0, and choose the network prefix mask from the drop-down list. If you choose a mask of 24, for example, the network address/mask would be 192.168.50.0/24.
Owner	Owner of the address block. Choose from the predefined owners in the drop-down list, as set up by clicking Owners on the Secondary Navigation bar. Optional.
Region	Administrative region for the address block. Choose from the predefined regions in the drop-down list, as set up by clicking Regions on the Secondary Navigation bar. Optional.
Address Type	Type of address. Choose from the predefined address types in the drop-down list, as set up by clicking Address Types on the Secondary Navigation bar. Optional.
Current Usage	View the current address usage of the subnet. Click the View icon () to open the View Current Utilization Report page.
Description	Description of the subnet. Optional.

After you complete these fields, click Add Subnet. This adds the subnet to the bottom of the list. You can go to the View Unified Address Space page, refresh the page, and view the newly created subnet in the tree. The address blocks and subnets appear in numerical order on that page.

At the regional cluster only, when you click Push Subnet on the Edit Subnet page, you can push the subnet to a local cluster DHCP server, router interface, or failover pair. Here are the choices you can make (not all of these items may appear, depending on the source of the subnet):

• Scope Template -- If using a predefined scope template to push the subnet, choose a template from the drop-down list.

• Router -- If pushing to a router, choose the router from the drop-down list.

• Router interface -- If pushing to a router interface, also choose the router interface from the drop-down list.
• Failoverpair -- If pushing to a DHCP failover pair, choose one from the list.

• DHCP Server -- If pushing to a DHCP server at a local cluster, choose the local cluster from the list.

After making your choices, click Push Subnet. You return to the Edit Subnet page.

You can edit a subnet from the View Unified Address Space page or from the List/Add Subnets page, unless you are a read-only administrator. Click the network address of the subnet on one of these pages.

The name of the page identifies the name of the subnet. If the subnet has a parent block, you can edit the parent block by clicking its name under the Parent Block heading, or you can click Return to return to the List/Add Subnets page. If the subnet does not have a parent block, you can modify the subnet's owner, region, address type, or description. After you modify any of these fields, click Modify Subnet.

On the regional cluster, you can also push the subnet to the local clusters or router interface by clicking Push Subnet to open the Push Subnet page.

Reclaiming a subnet removes it from a DHCP server allocation, router, or failover pair. If the subnet is in that state and you want to remove it, click Reclaim Subnet to open the Reclaim Subnet page.

The Edit Subnet page also identifies the subnet state (available, dhcp-allocated, ric-allocated, allocated to both, or reclaiming) and any failover pairs that include it.

To add address ranges for the subnet, enter the host part of the addresses in the Start and End fields. Click Add IP Range to add each range. The start and end addresses for each range appear under the Start and End fields, respectively. If you want to delete a static range, click the Delete icon () next to the beginning address of the range.

You can also go to the View Unified Address Space page, refresh the page, and view the modified subnet in the tree.

At the regional cluster only, when you click Reclaim Subnet on the Edit Subnet page, you can force the subnet to be reclaimed from a DHCP server allocation, router, or failover, and be made available. This page identifies the DHCP server to which it is allocated. You can also force deletion of the subnet by clicking a check mark in the Force Delete box. Then, click Reclaim Subnet, or Cancel to cancel the reclamation. You return to the Edit Subnet page.

Forcing a deletion means to remove the scope from DHCP or the failover pair regardless of whether the scope has active leases or reservations. If you do not force a scope deletion when you reclaim the subnet, the scope is disabled if it has active leases or reservations.

You can list address types that you can use to define address blocks and subnets. You can also add these address types from this page.

You can base address type definitions on scope templates, client-classes, and scope selection tags, and you can set a subinterface number and apply a matching expression.

To add an address type, click Add Address Type to open the Add Address Type page.

You can add an address type to the List Address Types page from this page. The attributes you can set on this page are:

Attribute	Description
Name	Unique tag for the address type. Required.
Scope Template	Choose a predefined scope template for the address type. Optional.
Client-Class	Choose a predefined DHCP client-class for the address type. Optional.
Scope Selection Tags	Enter a scope selection tag for the address type in the Tag Value field and click Add Selection Tag. Optional. To delete a selection tag, click the Delete icon () next to its name.

You can also add a description for the address type. To add the address type, click Add Address Type, or click Cancel to cancel.

You can edit an address type found on the List Address Types page on this page, or you can view them if you have read-only privileges. The attributes you can set on this page are:

Attribute	Description
Name	Unique tag for the address type. Required.
Scope Template	Choose a predefined scope template for the address type. Optional.
Client-Class	Choose a predefined DHCP client-class for the address type. Optional.
Scope Selection Tags	Enter a scope selection tag for the address type in the Tag Value field and click Add Selection Tag. Optional. To delete a selection tag, click the Delete icon () next to its name.

You can also modify the description for the address type, and unset fields. To modify the address type, click Modify Address Type, or click Cancel to cancel.

You can associate an owner with a zone, address block, subnet, router, or router interface. At the regional cluster, you can also constrain certain administrator roles by these owners. The owner has a unique tag, a description, and a contact name. This page lists the owners, and you can add, edit and delete owners, and push and pull them to and from the local clusters, unless you are a read-only administrator.

The fields you use to add an owner explicitly on the current page are:

When you complete the fields for adding an owner, click Add Owner. Each owner appears in the list and becomes available for managing address blocks and subnets.

• To edit an owner, click the owner's name in the list.

• To delete an owner, click the Delete icon () next to its name to open a Confirm Delete page.

• At the regional cluster, you can push individual owners to the local clusters by clicking Push Owner next to its name, or push all the created owners by clicking Push All Owners. You would then choose the clusters and update them on the Push Owner Data to Local Clusters page.

• At the regional cluster, you can also pull owners from the replica data of the local clusters. To do this, click Pull Replica Owners to open the Select Replica Owner Data to Pull page.

This page appears if you click Push Owner or Push All Owners on the List/Add Owners page. It shows the owner to be pushed (or All Owners) and a choice of local clusters to which to push them.

The fields and choices on this page are:

TIP: The cluster choice and radio buttons are persistent, so that any future operations on this page will retain these settings.

After making these choices, click Push Data to Clusters to open the View Push Owner Data Report page, or click Cancel to return to the List/Add Owners page.

This page appears if you click Push Data to Clusters on the Push Owner Data to Local Clusters page. It shows a read-only summary of the results of the push operation. Click OK to return.

At the regional cluster only, this page appears if you click Pull Replica Owners on the List/Add Owners page. It shows a tree view of the regional server's replica data for the local clusters' owners. The tree has two levels, one for the clusters and one for the owners in each cluster.

The columns on this page are:

Column	Description
Name	Name of the local cluster and its owners. If necessary, click the cluster name to open the Edit Server Cluster page. You can also view the owner data by clicking its name to open the View Owner page.
Update Replica Data	To update the replica data for the local cluster on the regional cluster, click the Replica icon ().
Pull Data	To pull a specific owner, choose a synchronization mode, then click Pull Owner next to its name. To pull all the owners from the cluster, click Pull All Owners to open the Report Pull Replica Owners page. The synchronization modes are: Ensure -- Ensures that the regional cluster has the replica data without affecting any existing data. Replace -- The default: Replaces the data without affecting other objects that are unique to the regional cluster. Exact -- Use with caution, because it puts an exact copy of the object data at the regional cluster, thereby overwriting any existing data and deleting objects that are unique to the regional cluster.

To return to the List/Add Owners page without making changes, click Cancel.

At the regional cluster only, this page appears when you pull an owner or owners on the Select Replica Owner Data to Pull page. It shows the changes to be made with the pull operation. Click Run to open the Run Pull Replica Owners page, or Cancel to cancel the operation.

At the regional cluster only, this page appears when you click Run on the Report Pull Replica Owners page. After looking at the report data, click OK to complete the pull operation.

To edit an owner, choose its name on the List/Add Owners page. On the Edit Owner page, change the Tag, Name, and Contact field values as is necessary. (In read-only mode, this is the View Owner page.)

You can also unset the Contact field. When you are done editing the fields, click Modify Owner, or Cancel. You return to the List/Add Owners page.

You can associate a geographic region with a zone, address block, subnet, router, or router interface. This association is purely arbitrary, but can help in tracking the zone, address block, or subnet. At the regional cluster, you can also constrain certain administrator roles by regions. This page lists the regions, and you can add, edit and delete regions, and push and pull them to and from the local clusters, unless you are a read-only administrator.

At the regional cluster, you can pull regions from the replica data of the local clusters. To do this, click Pull Replica Regions to open the Select Replica Region Data to Pull page.

The fields you use to add a region explicitly on the current page are:

When finished adding a region, click Add Region. Each region appears in the list and becomes available for managing address blocks and subnets.

• To edit a region, click its name in the list.

• To delete a region, click the Delete icon () next to its name to open a Confirm Delete page.

• At the regional cluster, you can also push individual regions to the local clusters by clicking Push Region next to its name, or push all the created regions by clicking Push All Regions. You would then choose the clusters and update them on the Push Region Data to Local Clusters page.

This page appears if you click Push Region or Push All Regions on the List/Add Regions page. It shows the region to be pushed (or All Regions) and a choice of local clusters to which to push them.

The fields and choices on this page are:

TIP: The cluster choices and radio buttons are persistent, so that any future operations on this page will retain these settings.

After making these choices, click Push Data to Clusters to open the View Push Region Data Report page, or click Cancel to return to the List/Add Regions page.

This page appears if you click Push Data to Clusters on the Push Region Data to Local Clusters page. It shows a read-only summary of the results of the push operation. Click OK to return.

At the regional cluster only, this page appears if you click Pull Replica Regions on the List/Add Regions page. It shows a tree view of the regional server's replica data for the local clusters' regions. The tree has two levels, one for the clusters and one for the regions in each cluster.

The columns on this page are:

Column	Description
Name	Name of the local cluster and its regions. If necessary, click the cluster name to open the Edit Server Cluster page. You can also view the region data by clicking its name to open the View Region page.
Update Replica Data	To update the replica data for the local cluster on the regional cluster, click the Replica icon ().
Pull Data	To pull a specific region, choose a synchronization mode, then click Pull Region next to its name. To pull all the regions from the cluster, click Pull All Regions to open the Report Pull Replica Regions page. The synchronization modes are: Ensure -- Ensures that the regional cluster has the replica data without affecting any existing data. Replace -- The default: Replaces the data without affecting other objects that are unique to the regional cluster. Exact -- Use with caution, because it puts an exact copy of the object data at the regional cluster, thereby overwriting any existing data and deleting objects that are unique to the regional cluster.

To return to the List/Add Regions page without making changes, click Cancel.

At the regional cluster only, this page appears when you pull a region or regions on the Select Replica Region Data to Pull page. It shows the changes to be made with the pull operation. Click Run to open the Run Pull Replica Regions page, or Cancel to cancel the operation.

At the regional cluster only, this page appears when you click Run on the Report Pull Replica Regions page. After looking at the report data, click OK to complete the pull operation.

You can edit a region by choosing its name on the List/Add Regions page. On the Edit Regions page, change the Tag, Name, and Contact fields as is necessary. (In read-only mode, this is the View Region page.)

You can also unset the Contact field. When you are done editing the fields, click Modify Region, or Cancel to cancel your changes. You return to the List/Add Regions page.

At the regional cluster, an address destination is a local cluster Network Registrar Central Configuration Management (CCM) server to which you can send messages to delegate, query, or reclaim address blocks. Ultimately all of these operations occur on the DHCP server, but you can have the local cluster CCM server relate them to the DHCP server. At the local cluster, you can delegate only to the local DHCP server, and the List/Add Address Destinations page would not appear.

To add a destination on this page, enter a distinguishing name for the the destination server, then choose the cluster for the server from the drop-down list. Click Add Address Destination. You can add as many destination servers as you want; they do not even need to have unique names.

To edit the destination data, click the destination name to open the Edit Address Destination page.

This page appears only if you created an address destination. To edit the destination data on this page, change the destination name or choose another server cluster from the drop-down list. Then, click Modify Address Destination. You return to the List/Add Address Destinations page.

At the regional cluster only, use this page to set up the subnet utilization data query criteria, and then query the data. To capture subnet utilization history data, you must:

1. Configure the local DHCP server with scopes and address ranges so that it can issue leases, and DHCP clients need to issue lease requests.

2. Because collecting subnet utilization data is disabled by default, set up the local DHCP server to enable it. The DHCP server attributes to set in the Subnet Utilization Settings attributes section of the Edit DHCP Server page are:
   • collect-addr-util-duration -- Maximum period the DHCP server maintains data. You must change this from the default of 0 (no collection) to some reasonable value (see the context sensitive help for the attribute).

   • collect-addr-util-interval -- Frequency the server collects snapshots of the data (set to 15m by default). How you juggle this value with that of the collect-addr-util-duration attribute determines how much memory you use (see the context sensitive help for the attribute).

3. Click Modify Server on the Edit DHCP Server page.

4. Click the Reload icon () for the DHCP server on the Manage Servers page.

5. On the regional cluster, create the cluster that includes this DHCP server. Go to the Subnet Utilization Settings section of the Add Server Cluster or Edit Server Cluster page. Change these attributes:
   • poll-subnet-util-interval -- Be sure that this is set to a reasonable time interval greater than 0.

   • poll-subnet-util-retry -- By default, this is set to one retry in the case of a polling failure. Change this as needed.

   • poll-subnet-util-offset -- Difference between the local and regional cluster system clocks, if any.

6. Click Modify Cluster.

7. On the regional List Server Clusters page, click the Poll Subnet Utilization icon () for the cluster involved.

The parameters that you can set to execute a query on the resulting data on the Query Subnet Utilization page are:

After entering or choosing these values, click Query Subnet Utilization to open the List Subnet Utilization Records page.

At the regional cluster only, this page lists the subnet utilization records as requested in the query from the Query Subnet Utilization page. It lists each subnet, its VPN (if relevant); a time stamp; and the number of active dynamic leases reported in the subnet. To view the details for a record, click it to open the View Subnet Utilization Record page. To refine the query on the Query Subnet Utilization page, click Refine Query.

The icon next to the Subnet heading varies by browser. For Internet Explorer, the Save icon is to save the report in a text or spreadsheet format. For Netscape, the icon opens a text version of the record output.

At the regional cluster only, this page shows the details for each subnet utilization record when you click the name of the record on the List Subnet Utilization Records page. To return to the listing page, click Return to Subnet Utilization List.

At the regional cluster only, use this page to set up the lease history data query criteria, and then query the data. You can also set up a criteria to capture the To capture lease history data, you must:

1. Configure the local DHCP server with scopes and address ranges so that it can issue leases, and DHCP clients need to issue lease requests.

2. Because collecting lease history data is disabled by default, set up the local DHCP server to enable it. The DHCP server attributes to set in the Lease History Settings attributes section of the Edit DHCP Server page are:
   • Lease History (ip-history) -- Explicitly set this to enabled.

   • ip-history-detail -- Set this to true to enable getting detailed lease history data.

   • ip-history-max-age -- Limit on the age of the history records (set to 4w by default). Change this as desired.

3. Click Modify Server on the Edit DHCP Server page.

4. Click the Reload icon () for the DHCP server on the Manage Servers page.

5. On the regional cluster, create the cluster that includes this DHCP server. Go to the Lease History Settings section of the Add Server Cluster or Edit Server Cluster page. Change these attributes:
   • poll-lease-hist-interval -- Be sure that this is set to a reasonable time interval greater than 0.

   • poll-lease-hist-retry -- By default, this is set to one retry in the case of a polling failure. Change this as needed.

   • poll-lease-hist-offset -- Difference between the local and regional cluster system clocks, if any.

6. Click Modify Cluster.

7. On the regional List Server Clusters page, click the Poll Lease History icon () for the cluster involved.

NOTE: When the state of an existing lease changes, such as when it is configured as a reserved address or it is de-activated, the change does not appear as a lease history change at the regional cluster. A lease history change appears only when the lease expires or is assigned to another client.

The parameters that you can set to execute a query on the resulting data on the Query Lease History page are:

After entering or choosing these values, click Query Lease History to open the List Lease History Records page.

At the regional cluster only, this page lists the lease history records as requested in the query from the Query Lease History page. It lists each lease's IP address, MAC address, state, host name, flags, and binding start and end times. To view the history attributes for the lease, click the name of its IP address to open the View Lease History Record page. To view the details for a record, click the View icon () in the View Detail column to open the View Lease History Detail page. To return to the query, click Return to Lease History Query.

The icon next to the IP Address heading varies by browser. For Internet Explorer, the Save icon is to save the report in a text or spreadsheet format. For Netscape, the icon opens a text version of the record output.

At the regional cluster only, this page shows the attributes for each lease history record when you click the name of the record on the List Lease History Records page. Click each attribute name to open descriptive help for the attribute. To return to the listing page, click Return to Lease History List.

At the regional cluster only, this page shows the details for each lease history record when you click the View icon () in the View Detail column of the List Lease History Records page. This page appears only if you have ip-history-detail enabled for the DHCP server you are polling.

The page lists the time-stamped change entries for the lease that show the change in binding data. To return to the listing page, click Return to Lease History List.

At the regional cluster only, this page lists the current leases for an IP address after requesting the query from the Query Lease History page.

The icon next to the IP Address heading varies by browser. For Internet Explorer, the Save icon is to save the report in a text or spreadsheet format. For Netscape, the icon opens a text version of the record output.

At the regional and local clusters, consistency rules let you check data inconsistencies, such as overlapping address ranges and subnets. On this page, you can choose the following consistency rules:

At the regional cluster:

• Attributes Consistency Rule - Ensures that policies and client-classes with the same names at replica have the same values.

• Broadcast Address Rule -- Ensures that the dynamic address range for a scope should not include a broadcast address.

• Cable Helper Consistency Rule - Ensures that cable helpers and DHCP failover are consistent.

• Client-Class Selection Match Tag Rule -- Ensures that all client classes have a selection tag defined by some scope.

• Ensure Scope for Subnet Rule - Ensures that a scope is present for every subnet.

• Ensure Subnets for Scopes Rule - Ensures that a subnet is present for every scope.

• IP Range Consistency Rule -- Determines any overlapping static or dynamic address ranges.

• Owner Match Rule - Ensures that each subnet on the router has the same owner as the subinterface.

• Router Subnets in Database Rule - Ensures that each subnet on the router has a corresponding subnet in the regional database.

• Selection Tags Consistency Rule - Ensures that selection tags on scopes match with one of those defined in the address space types.

• Subnet Consistency Rule -- Determines any overlapping subnets.

• Utilization Collection Rule - Ensures that the DHCP server collection interval is greater than the regional server collection interval.

At the local cluster:

• Broadcast Address Rule -- Ensures that the dynamic address range for a scope should not include a broadcast address.

• Client-Class Selection Match Tag Rule -- Ensures that all client-classes have a selection tag defined by some scope.

• IP Range Consistency Rule -- Determines any overlapping static or dynamic address ranges.

• Subnet Consistency Rule -- Determines any overlapping subnets.

Click a check mark in one or all of the boxes, then click Run Rules. This opens the Consistency Rules Result page.

When you choose the consistency rule or rules on the List Consistency Rules page, the Consistency Rules Result page shows the data inconsistencies found, if any. The page shows any violations with their respective rules, and you can drill down to the detail level for each violation.

To move from this page, click one of the other choices on the Navigation bar.