Custom Monitors Configured on NetScaler Missing After an Upgrade

Custom Monitors Configured on NetScaler Missing After an Upgrade

book

Article ID: CTX206715

calendar_today

Updated On:

Description

After upgrading or rebooting a NetScaler device, custom user monitors located in /netscaler/monitors are no longer present which might cause services or service groups to be marked down as the monitor scrip is no longer in the correct directory.

Resolution

Important! Starting with release 10.1 build 122.17, the script files for user monitors are in a new location.

If you upgrade an MPX or VPX virtual appliance to release 10.1 build 122.17 or later, the changes are as follows:

  • A new directory named conflicts is created in /nsconfig/monitors/ and all the built-in scripts of the previous builds are moved to this directory.
  • All new built-in scripts are available in the /netscaler/monitors/ directory. All custom scripts are available in the/nsconfig/monitors/ directory.
  • You must save a new custom script in the /nsconfig/monitors/ directory.
  • After the upgrade is completed, if a custom script is created and saved in the /nsconfig/monitors/ directory, with the same name as that of a built-in script, the script in the /netscaler/monitors/ directory takes priority. That is, the custom script does not run.
If you provision a virtual appliance with release 10.1 build 122.17 or later, the changes are as follows:
  • All built-in scripts are available in the /netscaler/monitors/ directory.
  • The /nsconfig/monitors/ directory is empty.
  • If you create a new custom script, you must save it in the /nsconfig/monitors/ directory.

For the scripts to function correctly, the name of the script file must not exceed 63 characters, and the maximum number of script arguments is 512. To debug the script, you must run it by using the nsumon-debug.pl script from the NetScaler command line. You use the script name (with its arguments), IP address, and the port as the arguments of the nsumon-debug.pl script. Users must use the script name, IP address, port, time-out, and the script arguments for the nsumon-debug.pl script.

Problem Cause

Change in file structure.

Issue/Introduction

Custom monitors configured on NetSclaer missing after an upgrade.

Additional Information

The ns.log will also display the below messages where the script name will be for each respective monitor script:

Fri Jan 15 08:39:52 GMT 2016: Scriptname conflict found between /netscaler/monitors and /nsconfig/monitors. Moving /nsconfig/monitors/nsftp.pl to /nsconfig/monitors/conflicts directory.
Fri Jan 15 08:39:52 GMT 2016: Scriptname conflict found between /netscaler/monitors and /nsconfig/monitors. Moving /nsconfig/monitors/nsldap.pl to /nsconfig/monitors/conflicts directory.
Fri Jan 15 08:39:53 GMT 2016: Scriptname conflict found between /netscaler/monitors and /nsconfig/monitors. Moving /nsconfig/monitors/nsmysql.pl to /nsconfig/monitors/conflicts directory.
Fri Jan 15 08:39:53 GMT 2016: Scriptname conflict found between /netscaler/monitors and /nsconfig/monitors. Moving /nsconfig/monitors/nsnntp.pl to /nsconfig/monitors/conflicts directory.
Fri Jan 15 08:39:53 GMT 2016: Scriptname conflict found between /netscaler/monitors and /nsconfig/monitors. Moving /nsconfig/monitors/nsntlm-lwp.pl to /nsconfig/monitors/conflicts directory.

Citrix Documentation - Understanding User Monitors

Powered by Wolken Software