Support Center > Search Results > SecureKnowledge Details
Machine sends SNMP Traps only to one sink server, although several sink servers were configured; SNMP Traps are always sent with 'public' community name Technical Level
  • Although multiple 'trap2sink' commands were added to /etc/snmp/snmpd.conf file, the 'snmpmonitor' sends traps only to the sink server specified in the last 'trap2sink' entry in /etc/snmp/snmpd.conf file.

  • SecurePlatform sends SNMP Traps with 'public' community name, although different community was configured in /etc/snmp/snmpd.conf file
  1. Sending SNMP Traps to multiple sink servers is not supported by standard 'snmpmonitor' utility.

  2. Check Point 'snmpmonitor' daemon sends SNMP Requests to 'snmpd' daemon with parameters configured in /etc/snmp/snmpd.conf file:
    • SNMP Community configured in 'trap2sink' line
    • OID configured in 'cp_monitor' line

    However, Community Name 'public' is hard-coded - as a result, the 'snmpd' daemon does not respond.

Note: To view this solution you need to Sign In .