CMS Idea Exchange

It is needed to synchronize all important Cis between 2 UCMDB to have all of them in one main UCMDB. It is also needed to synchronise the data with a “UCMDB Push”, including the deletion of Cis, and is needed to discover and synchronise everything every day. Since the data is huge, cannot do full push all the time, so it is needed to do delta sync.   Problem: 1- UCMDB doesn’t look what the target UCMDB have when he wants to sync. The sender UCMDB just keep a baseline of what he thought was previously transferred, so it’s already not really robust at first. And if you modify a   TQL, then the baseline change, so it’s creating more problems to know what needs to be deleted or not in the target system. 2- The new specific problem that we saw, is that a CI will be deleted in the target system as soon as it’s not in a   TQL   anymore, even if the CI still exist, only because a relationship is not there anymore. Example: Let’s take the next 2 little   TQL (See attachments). The relationship is 1-N, to avoid pushing everything everywhere all the time. So on day 1, a computer has a   tcp   port and installed software, so it’s in both   TQL   and send the data correctly to the other UCMDB. On day 2, this computer doesn’t have   tcp   ports anymore but still have the software. Since it’s not in the first   TQL   anymore, the server would be deleted in the destination UCMDB, ouch. Possible solution : A) Merge both   TQL   in 1   TQL. But since in reality I have many tql and some a lot more complex, it would be really big to include everything with optional Cis in the same TQL. And in this case, if a node have 0 ports and 0 software at a given time, it would delete the node anyway execpt if I include my soluation #B. And it would be long to test to confirm that there’s no error. B) In each   TQL, do 0-N relationship instead of 1-N everywhere. That way, all the servers would be   push   in both   TQL, even if they have no port or no software at a given time. In theory, it would work, but it would make my   TQL   containing a lot more CI. In a simple example like that it would not be too big to include all nodes in both, but since I have many   tql, and some are more complex, it would create a really big load to try to put   0-N   relationship on everything. Some   tql   would move from few thousands Cis to few millions Cis, and many would be duplicate from other   TQL. And I would have to include my solution #A at the same time to avoid duplicate data as much as possible. And it would   be long   to test to confirm that there’s no error. C) Was tried to “hide” some object in my   tql, to only push the main CI in a   TQL   and the relationship, but it failed because the node or other related Cis were often mandatory. D) Could stop to include the deletion in the push job. The problem is that there would be no way to clean up the data in the destination UCMDB.  Could not have aging   unabled, cause aging doesn’t support multi   ucmdb. I say this because the delta push doesn’t sync data when there was only a touch to it. So if a CI doesn’t change, in the first system, it would become old in the target system without any way to know if it should really be deleted or not. And even if you could include the delta sync to sync when there’s only a touch since we discover everything every day, it means or delta sync would become a full sync, and it would be too big. ... View more

Currently the probe cluster will spread the discovery range IPs over the available probe servers, but if a lot of the probe ranges dont have active devices, the IP addresses are still assigned to a probe meaning anything other then IP discovery will not be balanced. I would like to see the IP addressed balanced based on the outcome of the IP scans so only active IP addresses are considered.  ... View more

What:  Add DNS discovery to Host Connection by Shell, thereby populating primary_dns_name and authoritative_dns_name to the node and IP Address CI Types, respectively. Why: The running of a second job, modifying only 2 attributes makes the node go back through reconciliation again... with very small bulks (4 CIs on average) and ties up the data-in queue with data that could and should be added to a prior job. I would also add an option to the job to turn this on/off in the properties of the job. ... View more

VLAN-ID Detail missing in Hyper-V Discovery • Brief Description  • Hyper-V Topology by Shell/WMI does not discover any VLAN information for Hyper-V like it does with Vmware vCenter. • Benefits / Value  • VLAN Information is critical configuration management information. If a VLAN were to change then connectivity of a server could be affected.  • We do this for Vmware – so why not for Hyper-V…  • Our Business is related to Recovery (DR), so missing VLAN configuration information means we cannot support customers wishing to be recovered from Hyper-V environments. • Design details  • Out of the box Hyper-V discovery should provide VLAN ID for each server.  • VLAN ID of 0 (zero) is a valid VLAN ID in Hyper-V setup, so you should not filter this value. A VLAN can have a value of zero. ... View more

We do need the configuration possibilty to hide specific CI types (and all its element instances) from being shown in UCMDB Browser (for single users, a group of users or all users). ... View more

Please provide a Last Accessed By attribute (and associated functionality to populate/update the attribute). This would be associated with the Last Access Time, similar to how to Create Time and Last Modified Time are associated to the Created By and Updated By fields (respectively). Today we only have the Last Access Time to work with but don't know what process keeps touching the CI (for example, a CI is never a candidate for deletion because some process keeps it active by "touching" it). ... View more

Currently, it is not possible to rename objects in the uCMDB UI. This includes: - Queries, vues, reports, Enrichment rules, Folders - Jobs, adapters - Package names, schedules - Even CIs created manually: Value for fields set as "key" cannot be changed in the UI but they can be changed using the API - etc. There is a "Save as" option but not always. The main issue is after years of having the uCMDB in place, we have junks all over the place. Without the possibility to rename things, a good clean up are pretty hard to do. ... View more

Due to security within the company, we need to be able to use the UCMDB API with AD Authenticated ids, and not local ids only in order to execute the UCMDB API. This appears to be not capable at this time and only works with local accounts.  We are embarking on significant use of the UCMDB API for a variety of use cases and security does not allow us to use local accounts for such matters. ... View more

The regular scheduler for e.g. integrations ignores the common DST (daylight saving time) in Europe. This causes the integration jobs to start one hour too early or too late for each DST change. To solve the problem, you either have to re-create the jobs (leading to the loss of history) or use the "cron" functionality (can not be used so well) of the scheduler. Therefore, the regular scheduler should also handle DST.     ... View more

I think the subject is self describing.... Make the linux probe have the same functionality as the windows Probe. ... View more

We have Nodes with IP address CIs in UCMDB from Integrations or manually entered. We do not have any subnet CIs. We want to query / enrich all Nodes with IPs that belong to specific subnet range. Example: Subnet 10.140.160.128/25 has a range from 10.140.160.129 to 10.140.160.254 We use RTSM/UCMDB 10.33 ... View more

Hello, we are from Europe and use different format of date & time values. The UCMDB GUI and unfortunatelly exports (that are often consumed by users and management) show  date&time in format "Fri May 4 2018 10:25 PM CEST"  This format is not "normal and accepted" here. Please make the format configurable (in one place for all UCMDB).  Thank you.   Ivan   04/05/2018 10:25    :) ... View more

Currently the Management Zone job schedule has an optional "Start At" date/time. This works fine for initiating the job, but when the probe is restarted the job schedule's start time becomes the same as the probe's restart time. This occurs for any job set with "Allow Discovery to run at: <>". This is confirmed by viewing the Jobs Statuses in the probe JMX console. ... View more

Assuming NNMI is discovering switches and is replicating them to UCMDB, and UD is discovering servers, enable an integration that can build the Layer2 connections in UCMDB by connecting UD-discovered servers to NNMI-discovered switches ... View more

We would like to be able to view CIs that were deleted in the UI, with the ability to recover CIs and make the part of the active CMS data again. In different scenarios CIs have been deleted by error, and having the ability to recover them can restore operation faster. The system should be able to show all the Cis deleted by date or period of time , the root cause of the deletion and the option to recover the information. ... View more

It is not possible to trigger an integration job from command line. Because we are working in a large company, we have a central scheduler (BMC).  To start the UCMDB integration jobs depending on other jobs outside the UCMDB, we need the possibility to start the jobs from a command line, which can be triggered from our BMC central scheduler. This would allow us to build complex processes and ensure that the UCMDB jobs are started in the correct order only depending on external events.     ... View more

Our organization is using Oracle Enterprise Manager to manage the Oracle Stacks. In Oracle Enterprise Manager we can find all the information we need regarding databases, nodes, virtual nodes, weblogic application servers and performance information. Using this information would be easier than getting access to the systems themselves. ... View more

Apple is slowly closing macOS to non-verified development. As for macOS High Sierra every running process must be signed, and the installer must also be signed. AND it must be a PKG based, encrypted installer ... View more

Implement a method to get an status report via email of an Integation Point and the jobs held within, immediately upon completion of the integration job or the overall integration point.  Provide details within the report that tell me if it was successful, or if warnings or errors were genreated.  If possible, let me know what CIs caused the warnings or errors. ... View more