Citrix ADC

SNMP traps for GSLB configuration synchronization

Starting with Citrix ADC 12.1 build 49.xx, the Citrix ADC appliance generates SNMP traps for both local and remote sites when you synchronize the GSLB configuration. SNMP traps are generated for both manual synchronization and real-time synchronization.

When you synchronize the GSLB configuration for the first time, SNMP traps are generated. In the subsequent synchronization attempts, the SNMP traps are generated only if there is a change in the synchronization status from the previous synchronization status. Also, the SNMP traps are generated only for sites for which the synchronization status changed from the previous state.

For example, consider that the first GSLB configuration synchronization is successful. When you synchronize the configuration for the second time and if the synchronization is successful again, then SNMP traps are not generated because the status is not changed. However, in the third attempt, if the synchronization fails for one of the sites, then SNMP trap is generated for that site alone.

In a high availability and a cluster setup, the appliance generates the SNMP traps when you synchronize the GSLB configuration from the new node irrespective of the previous synchronization status. Also, if SNMP trap option was previously disabled and then enabled, SNMP traps are generated from that point onwards irrespective of previous synchronization status.

The SNMP traps of GSLB configuration synchronization provide the following details:

  • Name of the GSLB site for which the SNMP trap is sent.
  • GSLB configuration synchronization status: Success or Failure.
  • GSLB configuration synchronization mode: Incremental sync or Full sync.
  • (Optional) Detailed information about the SNMP traps.

The SNMP traps are generated in the following scenarios:

  • GSLB synchronization status for a GSLB site flips from Success to Failure, and conversely.
  • GSLB synchronization mode changes from incremental synchronization to full synchronization, and conversely.

Note:

Even when incremental synchronization is enabled, if full synchronization is performed on a GSLB site for some reason, the reason for Full sync is mentioned in the “Detailed information” section of the trap message. For example, when a new GSLB site is added to the GSLB configuration.

Sample SNMP trap messages

The following figure displays a sample SNMP trap for gslb_site2, where the GSLB configuration synchronization is successful using the Full sync mode.

SNMP trap message for successful Full sync

The following figure displays a sample SNMP trap for gslb_site2, where the GSLB configuration synchronization is successful using the incremental sync mode.

SNMP trap message for successful incremental sync mode

The following figure displays a sample SNMP trap for gslb_site2, where the GSLB configuration synchronization using the incremental sync mode is failed. The error message indicates that you must manually fix the errors to complete the synchronization.

Incremental sync failure

The following figure displays a sample SNMP trap for gslb_site2, where the GSLB configuration synchronization using the incremental sync mode is failed. It also indicates the reason for sync failure, that is the site monitor is DOWN.

Incremental sync failure when site is down

SNMP traps for GSLB configuration synchronization

In this article