Previous Topic: Enable Automatic Formatting of TrapsNext Topic: TRAP and MIB Table Manipulation


How catrap Issues Traps

The catrap command can issue SNMP traps to any destination in your network and supports all operands accepted as Open System standards for an SNMP trap command. You can use it interactively, through UNIX/Linux shell scripts or in Windows .bat files, or as part of automated event handling policies defined to Event Management.

Note: This command makes it simple for user applications, shell scripts that are part of production jobs, or Event Management policies to issue their own SNMP traps, simply by executing the command and passing it the appropriate arguments. Unlike some other SNMP trap commands, catrap does not restrict itself to any particular set of ISO or Enterprise MIBs and is totally open for use with any MIB or pseudo-MIB with no dependencies on any third-party network management components.

For more information on catrap, see the online CA Reference.

Binary and Hex Octet String Varbinds

The Windows SNMP service treats octet string varbinds containing binary or hex string data in traps as printable strings unless one of the following is true:

If either of the preceding cases is true, the octet string is displayed in hex.

Octet string varbinds containing binary or hex string data in traps when using catrapmuxd with v1, v2c, and v3 SNMP support are converted to printable strings with a potential for truncation of data in the Console when the octet string contains non-printable data. If this occurs, you can modify the aws_snmp.cfg file to specify that certain varbind OIDs are always displayed in hex. This ensures that the octet string data is displayed fully, in hex, on the Console.