Secondary NetScaler unable to syslog messages when the syslog server configured as FQDN

Secondary NetScaler unable to syslog messages when the syslog server configured as FQDN

book

Article ID: CTX233927

calendar_today

Updated On:

Description

In a HA setup, when both the devices are configured to send the logs to an external syslog server and the syslog server is configured on the NetScaler (NS) based on the FQDN, then only the secondary NS is unable to send the logs to the syslog server.


Instructions


On Primary:
-------------------
> sh syslogaction
1) Name: sa1

Server Name: xxxxx.com (10.10.10.10)
Domain Resolve Retry: 5
Port: 514
Loglevel : EMERGENCY ALERT CRITICAL ERROR WARNING NOTICE INFORMATIONAL DEBUG
Date Format: MMDDYYYY


On Secondary:
--------------------
> sh syslogaction sa1
1) Name: sa1
Server Name: xxxxx.com (Unresolved IP)
Domain Resolve Retry: 5
Port: 514

In HA setup, the primary node sends the information about domain resolution to the secondary node as monitoring won’t happen on secondary node. The flag setting is missing due to which the information is not being passed to secondary node. Hence, domain is not getting resolved.

The issue has been fixed in 11.1 build 58.x scheduled for April 2018 release