RolandW1
Tera Expert

Hi mb_uk,

Unfortunately not. We created a ticket in Hi and eventually an enhancement request was created (FTASK30074) but is under consideration for over a year now. No progress whatsoever.

They did make a suggestion to maybe make a SSH probe which also fetches the mac address and make it unique. But I personally find this a defect and not an enhancement request because it is not documented that this doesn't work for virtual netscalers. This should work OOTB.

Maybe you can create a ticket too and refer to FTASK30074. If I am the only customer there will be no priority.

I am now creating a probe for discovery of windows certificates which roughly works now and after that I want to check this issue again and try to create my own probe/sensor if SN is not fixing this. They did not respond to my question about the status.

 

Regards,

 

Roland

mb_uk
Giga Contributor

Thanks for the quick reply! I'll raise a HI ticket like you suggest. Hopefully we'll see a fix come through in the future.

 

Thanks

Mark

Michael Skov2
Kilo Guru

Hi

I had this issue before. You simply need to change the identifier for Citrix Netscalers in the CI Class Manager, do the unique key isnt serialnumber. I believe i used name and ip address instead.

View solution in original post

Dewin Albert2
Mega Expert

Yes! recently we were facing this issue.

If a virtual netscaler is cloned or the same image is used to create more than one LB, then the serial number will be duplicated.

Create an independent identification rule on netscaler table "cmdb_ci_lb_netscaler" with IP and serial number as attributes.

 

The name discovered via SNMP is also common for all netscalers. to resolve that refer below link.

Ref Link: 

https://devopstree.com/servicenow/fix-for-common-netscaler-hostname-while-discovering/

 

Hope it helps 🙂

mb_uk
Giga Contributor

Thanks Michael & Dewin - I'm now discovering all my Netscalers.

Mark