Citrix Netscaler pattern

[Michael Skov2]

Hi

I am having lots of trouble getting the default Citrix Netscaler pattern to work. One of two things happens:

- The pattern stops at "get vservers table" in the identification section. In debug mode the connection fails to the snmp device 8/10 times

- The identification section runs, but connections are not made. On the connectivity sections, i get this groovy script error:

Have anyone seens this behaviour before?

[Michael Skov2 · Accepted solution]

For anyone experiencing this, in the end this was a problem with the MID server selection and ip ranges. Once i got the ip ranges properly configured the pattern worked.

[SupriyaR4553017]

I am also facing issue with the citrix NetScaler patterns (screen shots are attached). The IP is active and even a quick discovery on it was a success. But the OID mentioned is not on the OID table. Should i try adding this OID there and then ran the discovery

[AbdulBadi]

Hi @Michael Skov2  @SupriyaR4553017 

I am troubleshooting a similar Citrix NetScaler VPX Discovery issue and saw that the accepted solution involved correcting MID Server selection and IP ranges.

In my case, the out-of-box SNMP pattern completes and retrieves the serial number, management IP, interfaces, vServers/VIPs, services, pools, and members. However, IRE creates a new generic CI named “netscaler” instead of matching the existing VPX CI previously created through SDX Discovery.

Could you please clarify what was incorrect in the MID Server or IP-range configuration and what changes resolved the issue? Was it related to MID Server IP ranges, Discovery Behavior, MID capabilities, affinity, or pattern routing?

I am trying to confirm whether MID Server selection could also affect VPX identification and reconciliation even when the pattern completes successfully.

Thank you.