Virtual Citrix Netscaler discovery

RolandW1 · ‎06-07-2018

We have a lot of citrix netscalers for which some of them are virtual appliances and some are physical.

The physical netscalers are discovered correctly but the virtual netscalers are not because virtual netscalers have the same serial number. This results in 1 ci which have the different configurations "merged" instead of the 30 citrix netscalers which should have been created.

Did somebody came across the same problem and/or how can i fix this in Jakarta?

Thank you,

Roland

Michael Skov2 · ‎07-04-2018

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 · ‎07-05-2018

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 · ‎07-09-2018

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

Mark

Michael Skov2 · ‎07-09-2018

Awesome, good to hear! Please remember to mark the correct response as the correct answer :-).

RolandW1 · ‎07-10-2018

Thanks Michael & Dewin for the great tips.

I am still working on this with Servicenow because this should work OOTB. There is no restriction or mention in the documentation that virtual netscaler discovery does not work.

I will let you know when I have news.

Roland

Michael Skov2 · ‎07-10-2018

Have you changed the identifier, and still have the issues?