Simplify your Datacenter Infrastructure Discovery with Zone-Based Discovery in HP Universal
Discovery webinar Q&A
Q: How to calculate number of probes necessary to process all nodes in infrastructure
A: Performance and Sizing in UCMDB Support Matrix is a great place to start. Ultimately it depends on
schedule, type and number of discovery jobs you are running on that probe.
Q: Discovery zone will be defined based on IP rang only?
A: For configuring Zones, Yes. But IP address will ultimately lead to certain category such as location or
Service.
Q: How does ranking work? For example, if I have a computer that has 2 different IP addresses and I
want to run a specific discovery pattern for first IP and a different pattern for IP 2, is that possible?
A: Only one of the two IP addresses will be recorded in the protocol CI (WMI/SSH/etc.) attribute
(Application IP). This IP address will be used for the communication irrespective of the Zone ranking
assuming discovery patterns use same protocol.
Q: How does uCMDB deal with DHCP ranges, not static ranges
A: UCMDB will discovery IP address on the network. Aging mechanism is used to clear IP addresses that
do not respond anymore. Discovery schedule is also critical in this case to keep data up to date
Q: Can we control the order of job seq execution
A: Job execution order within the zone is based on trigger CI. In two different zones can be controlled
using Ranking
Q: Can we perform zone based discovery from OMi console?
A: OMi 10.X uses RTSM platform and has capability to run Zone-Based Discovery. It will be
recommended to review use case and check best practices guide for the same. Also, this will not be a
replacement for UCMDB
Q: is it possible to export import these configurations
A: Only at a database level with some limitations
Q: Does Impact Analysis work across zones
A: Yes
Q: in UD zone as some of the jobs have trigger CI to be created for the next job
A: Trigger CI's will be discovered in the zone itself
Q: does ZB discoveries have trigger limits..
A: Limited based on IP ranges of for the zone
Q: Can discovery of SQL App be trigger not by Node / IP address. Good for a Cloud PaaS SQL instance
A: Discovery adapters could be modified for different Input CIType
Q: this Use Case indicates... you have to discover all trigger CI´s multiple times... does it make sense?
A: In this use case we saved at least 70+ unnecessary triggers. It makes complete sense and zone
ranking will take care of overlap
Q: what is the limit for zones?
A: There is no numeric limit. But it is recommended to have limited zone
Q: we running a multi tenant env. with 15 tenant 45 probes 40 000 Server .... can you imagine if zones
can handle that...
A: Yes, capability is there