Cisco Cisco Workload Automation 6.3 User Guide

Page of 412
208
Actions and Alerts
Actions Interface
Description Tab
The 
Description
 field is a free text field for up to 255 characters.
Configuring SNMP on the Master
By default, the SNMP action sends the trap to just the “public” community but CWA can be configured to send SNMP 
traps to multiple communities and hosts. Older versions of CWA used the Master.Props file to configuration the use of 
SNMP traps. The designated recipients of the SNMP traps are now specified in an XML file called snmpconfig.xml
To create the configuration file, the following information must be gathered beforehand:
A list of the communities that will receive traps from CWA
A list of the hostnames of the machines in each community 
The port number, if a host machine is not using the standard port number (162) for receiving the traps
From the information that you have gathered, you must designate a default community, host machine and port number, 
in that order. 
The default community is the community that the trap will be sent to when the action definition of the trap is not filled 
in. 
The default host is the hostname that the trap will be sent to if the default community contains no hosts. The 
hostname is only used if the default community is unavailable or incorrectly defined.
The default port is the port number that the trap will use unless the host is specifically configured for a different port. 
The default port number used in SNMP trapping is 162, though this could have been configured differently in your 
system.
The information in the snmpconfig.xml configuration file is organized as follows, first the default properties and then a 
listing of the communities and their host members, if any.
The following rules must be followed when creating the snmpconfig.xml file:
The default attributes for community, hostname and port number must be defined. 
There can only be one default designated for each attribute and the defaults must be listed in the correct order.
The default community and its attributes must be listed first.
The community name is case-sensitive. Type the community name in the configuration file exactly as it is defined.
No other community besides the default is necessary in the configuration file but as many communities as needed 
can be defined after the default. 
Communities cannot nest inside each other. Instead each community should be listed in individual blocks of its 
attributes.
Hostnames are optional in the other communities listed, but if used, they must be placed in the community they 
belong. Note that a host machine can belong to multiple communities. 
If the same host machine is named twice in a community block, then that host machine will receive two copies of 
every trap sent to that community.
Define a port number attribute if the designated host machine is using a port number for its traps that differs from 
the default port number. Any host machine without a port attribute will receive traps via the designated default port.
An example of an snmpconfig.xml file illustrating the proper file formatting and using the rules stipulated above is shown 
below. In this example, the default community=public, the default hostname=localhost and the default port number=162.
<?xml version=”1.0” encoding=”UTF–8”?>