During a NetScaler SNMP outage, alerts were not received. Which configuration detail most likely caused the failure?

During a NetScaler SNMP outage, alerts were not received. Which configuration detail most likely caused the failure?

• A. The NetScaler only has Standard licensing.
• B. The Community Name was NOT configured on the NetScaler SNMP Trap Destination settings.
• C. The NetScaler is configured for SNMP version 1.
• D. The NetScaler Application Firewall is blocking the alerts from going out.

Answer: (B)

SNMP traps rely on a shared community string to authorize messages between the NetScaler and the management station. In NetScaler, the Trap Destination must include this SNMP community name. If the Community Name isn’t configured, the destination cannot authenticate the traps, so the management system will ignore them and no alerts will be received. This direct misconfiguration stops alerts from arriving even if the network path is fine or SNMP version is set, whereas licensing or firewall settings are less likely to be the immediate cause.

SNMP traps rely on a shared community string to authorize messages between the NetScaler and the management station. In NetScaler, the Trap Destination must include this SNMP community name. If the Community Name isn’t configured, the destination cannot authenticate the traps, so the management system will ignore them and no alerts will be received. This direct misconfiguration stops alerts from arriving even if the network path is fine or SNMP version is set, whereas licensing or firewall settings are less likely to be the immediate cause.