Netscaler Discovery - Interactive Probe Shell Citrix Netscaler SDX

[Marvin5]

Hi Community

We've upgraded from Paris to Rome last year and we've noticed that sometmes our netscalers are being classed as Citrix Netscaler SDX devices. In the screenshot, this was one discovery with both Netscaler nodes. One of the nodes was discovered and updated successfully but the other wasn't and a new CI was created in Citrix Netscaler SDX class.

Just wondering if anyone else has experienced this and what could be causing it?

Thank you

[ServiceNow Tec2]

This has been resolved by ServiceNow Technical Support. Please refer to KB1008862 for more information.

[ServiceNow Tec2 · Accepted solution]

This has been resolved by ServiceNow Technical Support. Please refer to KB0755296 for more information.

[AbdulBadi]

Hi @Marvin5 @ServiceNow Tec2 

I am currently troubleshooting a Citrix NetScaler SDX/VPX Discovery issue.

The SDX Discovery pattern successfully discovers the SDX appliance and creates its hosted VPX CIs. However, when I run direct SNMP Discovery against a VPX management IP, the out-of-box NetScaler pattern collects the serial number, management IP, interfaces, VIPs, services, service groups, and pool members, but IRE does not match the existing VPX CI created through SDX Discovery.

Instead, Discovery creates a separate generic CI named netscaler, resulting in duplicate VPX records and disconnected topology.

The SSH NetScaler pattern retrieves the correct device information when tested manually, but it does not automatically trigger during normal horizontal Discovery.

Have you encountered this behavior, and could you please share what configuration or ServiceNow fix resolved the incorrect classification and duplicate-CI issue?

Thank you.