Citrix Netscaler Load balancer showing incorrect CI name with same serial number

[Prahlad Kumar]

Hi All,

Please anyone help me on this. screenshot attached.

I am getting a bug while discovery of Citrix Netscaler Load balancer, Its runnning on Virtual Server as a load balancer.

I am trying to discover 3 IP addresses for load balancers which are configured, and the devices which are discovered is showing incorrect CI name with same serial number, but I have checked locally it all have different Host ID.

In CMDB actually only one CI has been created but in discovery status it is showing 3 CIs based on IP ranges, and whenever I am running discovery these all 3 IPs updating the same CI which is created in CMDB.

Goal: I want it to create separate CI in CMDB based on configured 3 IPs in IP ranges after discovery based on Host ID, because it is updating same CI with same Serial Number. 

#discovery #cmdb #itomforum @discovery @itom @CMDB  

Thanks,

Prahlad Kumar

[Pratiksha]

Hi @Prahlad Kumar,

You need discover it using management ip. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0722913

[Prahlad Kumar]

Hi @Pratiksha  ,

Thanks for your response, my queries are different from article.

Attached Screenshot on above main Queries.

Could you please suggest on this and what is the reason behind it?

Thanks

Prahlad Kumar

[Community Alums]

Hi @Prahlad Kumar: this issue is because of sysname that discovery is bringing, you can connect with your Network team to change the name as mentioned in below KB : 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0786203

Please mark answer as helpful if answered your query

[SalilD]

Hi Prahlad, how were you able to scan the virtual Citrix NetScaler Load balancers. In the documentation it's mentioned virtual load balancers cannot be scanned using ServiceNow Discovery. Thanks !

[AbdulBadi]

Hi @Prahlad Kumar @SalilD @Sohail Khilji @Pratiksha  @VedantJ 

I am experiencing a related NetScaler identification issue. SDX Discovery creates the hosted VPX CI correctly, but when the same VPX is discovered directly through SNMP, IRE does not match the existing CI. Instead, it creates another CI with the generic name netscaler, even though the payload contains the serial number and management IP.

Did you eventually resolve your identification issue? If so, could you share the final identifier configuration that worked? I am particularly interested in whether using name and IP address resolved the issue or whether additional identifier, hosting, or reconciliation changes were required.

Thank you.