Configure IP Ranges for Management Zones at Domain Level

Starting with UCMDB version 10.30, it is possible to configure IP ranges for management zones at domain level, instead of Data Flow Probe/probe clusters level. This enables discovery administrators to define management zones with more flexibility to reflect business discovery strategy.

The enhancements implemented in UCMDB 10.30 include the following:

  • Decoupled IP Range configuration from Data Flow Probe/probe clusters level for management zones
  • Removed IP range type setting for management zones, and
  • Allow binding of excluded IPs from one IP range to a different IP range as a sub-range at domain level

All this adds flexibility in managing IP ranges with management zones and eliminates the limitation of IP ranges bound to Data Flow Probe/probe clusters. Now you can perform the following on management zones easily:

  • Configure independent IP ranges at domain level for management zones
  • Bind IPs excluded from one IP range to a different IP range as sub-range for management zones, without the limitation of types of IP addresses

UI Change

The screenshots and the table below illustrates UI changes implemented for the enhancements:

UCMDB 10.22 UCMDB 10.30 and later Behavior Change
Define partial ranges on Data Flow Probes Define partial ranges on domains In 10.30 and later, you can define partial IP ranges at domain level, instead of at probe level.
Domains and Probes Domains Removed "Probes" in 10.30 and later, and only domains are displayed in the Domains tree. You select a domain and define IP ranges at domain level for the management zone.
Open Data Flow Probe Setup n/a Removed in 10.30 and later. No need to configure IP ranges at probe level. Note that this change has no impact to the existing Data Flow Probe Setup dialog box where you can define IP ranges for Data Flow Probes/probe clusters.
n/a New Range

Opens the New Range dialog box, enabling you to set sub-ranges for management zones. For details on creating new ranges for management zones, see New/Edit Range Dialog Box.

Compared to the New Range dialog box you open from Data Flow Management > Data Flow Probe Setup, the Type setting is removed.

n/a Edit Range

Opens the Edit Range dialog box, enabling you to edit the sub-ranges you want to include or exclude from the full range of the selected domain. This button is available only if you have previously added at least one sub-range of the domain to the Management Zone. For details on editing the existing ranges for management zones, see New/Edit Range Dialog Box.

Compared to the Edit Range dialog box you open from Data Flow Management > Data Flow Probe Setup, the Type setting is removed.

Select Range Select Range In UCMDB version 10.22 and earlier, you select and add sub-ranges at probe level, and those sub-ranges are not editable; In version 10.30 and later you can edit the sub-ranges after selecting and adding them to the selected domain.
Type column n/a Removed in 10.30 and later. It means that, unlike range configuration at probe level, IP ranges configured at domain level are not bound to any type. This offers flexibility in IP range configuration for management zones.

Zone-Based Discovery Behavior Change

When saving IP ranges on management zones, UCMDB server automatically calculates the corresponding probe IP ranges to which the discovery jobs should be dispatched.

When changing the probe IP ranges, UCMDB server adjusts the dispatching of IP ranges of the management zones.

Export and import of a management zone using JMX methods getManagementZone and addManagementZone are also supported. During the import, probe-based IP ranges will be converted to domain-based IP ranges.

Also, during UMCDB server upgrade, for example, from UCMDB 10.22 to UCMDB 10.30 (or later), probe-based IP ranges are converted to domain-based IP ranges.

When running a zone-based discovery, the system dynamically dispatches discovery jobs to live IP addresses only in the IP ranges defined for management zones. During the dispatch, domain-based IP ranges will be converted to probe-based IP ranges, and invalid IP addresses will be skipped.

Related Topics Link IconRelated Information