Destination settings

Three types of destination settings appear in the trap-notify.conf file:

• Destinations

  Example: Destinations = { {"localhost", 162, "V1"}, {"other-host", 
             30162, "V2C"}}
  

• DestinationsWithCommunity

  Example: DestinationsWithCommunity = { {"localhost", 162, "V1", 
             "public1"}, {"other-host", 30162, "V2C", ""}}
  

• DestinationsSNMPv3

  Example: DestinationsSNMPv3 = {{"localhost", 9010,"V3","public","md5DesUser","MD5","DES","authPass","privPass","" }}
  

  The first two settings are for sending notifications as SNMPv1 or v2c traps, and the third setting is for sending notifications as SNMPv3 traps. Syntax descriptions as well as other destination setting examples are included in the trap-notify.conf file.

  The difference between the Destinations and DestinationsWithCommunity settings is that the latter lets you specify the community string that you want to assign to the sent traps, while the former assigns the sent traps the default community string “public.”

  The destination host “localhost” represents the loopback address of the local host, and the destination host “other-host” serves as a placeholder for the name of a remote host. A destination host may be identified by an IP address or a hostname. An example IP address is [3FFE:80C0:22C:101:219:56FF:FE3F:8A50] or 192.35.144.12, and an example hostname is myserver.example.com:v6. An IPv6 address must be enclosed within square brackets ([]).

  The syntax for hostname is described in "Controlling the IP version for name resolution" section of Chapter 2, Configuration, in VMware Smart Assurance IP Manager User Guide. If no IP protocol suffix is included with a hostname (for example, myserver.example.com), the IP protocol setting for environment variable SM_IP_VERSIONS is used to resolve the hostname to an IP address. SM_IP_VERSIONS is described in "SM_IP_VERSIONS environment variable" section of Chapter 8, IPv6 Address Conventions, in VMware Smart Assurance IP Manager Reference Guide.