Do you have Native SACM enabled?

Could you please check the Studio field configuration for one of the fields mentioned, like CPU?

Hello Brindusa,

Yes Native SACM is enabled but Enrichment rules can not be applied so, I can't update CPU, Disks of imported devices (non discovered) also can't update these fields of discovered Devices.

Could you please post a screenshot like the one below? Would like to check your configuration.

of course

and this screenshot shows that enrichment rules don't include CPU or this type of fields

Complex attributes such as a list of CPUs, File Systems, or IP addresses can't be created/updated in SMA anymore. These details are synchronized directly from UCMDB. Plus, if a value was updated it would be updated/overwritten the next time the CI was updated in UCMDB and sync'd to SMAX via NSACM.

Specifically, CPU is complex type in SMAX and is actually representing 4 different fields from the UCMDB CPU CI, which are Name, CpuClockSpeed, Core number, & CpuId.

So how can we update undiscovered assets like PCs and Laptops which are inserted directly in SMAX not discovered in UCMDB ?

Hi Mohamed,

When you enabled Native SACM you should have had the dialog box appear to migrate data from SMAX to UCMDB. This would mean any devices that existed in SMAX regardless of whether you could discover them in UCMDB would still have been migrated across.

Once migrated the device can then be updated in UCMDB which in turn would federate the data back to SMAX. So you could update the CPU details manually in UCMDB and this would show in SMAX regardless of whether UD was discovering the device.

By the sounds of what you are saying it looks like you had an issue with migrating the data as part of the Enabling Native SACM if the device doesn't show up in UCMDB.

 https://docs.microfocus.com/doc/SMAX/24.4/EnableNativeSACMinSMA#Data_migration

You'd need to check the Migration report as to why these devices didn't get migrated if you still have the report.

Hello Dave Dave Heckford ,

I think I didn't make my point clear, the Devices are synchronized from SMA to UCMDB but CPU is not updatable from both sides so, How to update CPU, DIsks .. ?

Brindusa Kevorkian 

BradB 

Hi Mohamed,

In which case you have to use UCMDB to update the CPU details. Whether that be manually within UCMDB or by Enrichment Rule that is the only option. If UCMDB isn't letting you update you'd need to check any errors as to why you can't update the CPU CIs in question.

For example here is a Device that was created in SMAX and pushed to UCMDB via the Migration process. I can just use the properties window to update the CPU details:

I'll update this in UCMDB to 8

Now in SMAX it says 8 for the Cores

Yousuf,

Once nativeSACM is enabled, the functionality of updating these complex types from SMAX UI (customer facing interface) becomes quite limited unfortunately and I can understand it becomes quite counter intuitive asking customer (Hardware asset management team) to login to another portal (CMS UI in this case) to manage some attributes of the devices where all other attributes are otherwise manageable from SMAX UI. Moreover, you may not want users to access CMS UI. 
We had similar issues where customer wants to maintain the IP addresses and MAC for the devices (which can't be discovered ever) and asking these to be maintained by creating relationships via modeling CMS UI wasn't an easy task.
We had two choices to offer, one is to create service model in UCMDB and open access to CMS UI so customer can manually maintain the relationship between Nodes and IP / MAC, and also create some csv to UCMDB import routine to bulk import these information.

Other option (which we end up implementing) is to create a custom table to store this information and have a one to many relationship shown on the Device table. Using this feature allows customer to maintain , import data in SMAX UI in same manner as it does for other record types. But that comes with a nuance that the devices which are discoverable shows the information in a OOTB readonly view, whereas devices which are not discoverable shows informaiton in the custom view. Also, we couldn't make use of auto identification of CIs based on the IP address.. but given the ease and consistent way of maintaining the needed attribute outweighs any benefit that one would get from the auto recognition of CIs based on IP or MAC.

Hope this gives some ideas to consider.

I think there's an idea already to allow product to update these complex type fields from SMAX without needing to go to UCMDB.


Regards,

Shishir