Discovery - Issues exploring Solaris LDOM devices

vikrantsharma
Kilo Guru

Hi All,

We are performing discovery and things are smooth.

However, the only issue that we are facing is that we have all our Solaris servers as LDOM, and they don't really get discovered correctly.

The issue we are getting is that when we try to explore a LDOM physical device, and they have n number of logical separation on them, Discovery only identifies it as a single device, which makes sense as I have seen the logs and it find a match on the Serial number or Network. And as LDOM would share the same hardware it would not explore the rest of them, however it does recognize that there are separate logical devices.

I have raised incident with SNOW, and they have advice that there is not a current support for LDOM. They have mentioned, and it can be seen on the wiki and ocs website, that Zones are specifically mentioned that they are supported, but nothing is mentioned for LDOMs.

I wanted to know if someone has already produced a work around for this, before I start exploring the scripts to find a custom solution?

doug.schulze. Apologies for tagging you in, but would you be able to put some light on this, if possible?

Regards,

Vikrant Sharma

Please make it correct or helpful if this solves or help you with your issue for other to make use it.

Thanks & Regards,
Vikrant Sharma
2 REPLIES 2

Tomko
Tera Expert

We ran into the same issue.   While I can't help with truly discovering LDOMs and building relationships between them automatically, the solution we employed was to create a new identifier rule for Solaris Servers, which matches only name and IP Address (from cmdb_solaris_server).   This will be run instead of the generic hardware identifier, allowing each of the LDOMs to generate a separate CI record.



It's not perfect, and you do run the risk of duplicating CIs if you ever rename and re-IP a server, but at least it prevents discovery from over-merging.


vikrantsharma
Kilo Guru

Thanks John,


I did the same as well after giving this a though, but I discussed with the UNIX Administrators, and they suggested me to have a unique Identity of dns_domain and host_name. I did that and it started working, but now I get a different error for some of the servers "it gives an error "CMDB Identification Error: Can't find any rule to apply to independent record with payload index 0 and className 'cmdb_ci_solaris_server'".


Any suggestions?



Thanks in advance.


Please make it correct or helpful if this solves or help you with your issue for other to make use it.

Thanks & Regards,
Vikrant Sharma