- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2018 04:57 AM
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
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2018 11:52 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2018 05:08 AM
Hi RowlandW - did you make any progress with this? I'm seeing the same issue.
Thanks
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2018 05:35 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2018 05:47 AM
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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2018 11:52 PM
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.