To configure the SNMP Trap Adapter configured as a trap exploder, you open and edit the Service Assurance BASEDIR/smarts/conf/trapd/trapd.conf file to forward the appropriate traps to VoIP Availability Manager, IP Availability Manager, the VoIP Notification Trap Adapter, and the SNMP Trap Adapter configured as a trap receiver. You use the FORWARD parameter in the trapd.conf file to determine which incoming traps are sent to what destinations.

The traps to be forwarded to VoIP Availability Manager and to the VoIP Notification Trap Adapter are listed in the following files in the VoIP Management Suite installation area. These files contain list of traps that you can copy as described later in this section. The files are not used during trap processing by the product suite.

  • BASEDIR/smarts/conf/voip/avaya/avaya-trapd.conf

    Contains a list of Avaya VoIP traps to be used by VoIP Availability Manager for analysis purposes, and a list of Avaya VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

  • BASEDIR/smarts/conf/voip/nortel/cisco-trapd.conf

    Contains a list of Cisco VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

  • BASEDIR/smarts/conf/voip/cisco/nortel-trapd.conf

    Contains a list of Nortel VoIP traps to be used by VoIP Availability Manager for analysis purposes, and a list of Nortel VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

  • BASEDIR/smarts/local/conf/voip/pm/pm_trapd.conf

    Contains a list of VoIP Performance Manager default threshold traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes. The procedure is described in “Configure components to forward VoIP Performance Manager threshold traps” on page 97.

    In addition to configuring the trapd.conf file, you need to configure the managed network devices to forward SNMP traps to the host where the trap exploder is running, and to the port on which the trap exploder is listening for traps.

    If the --port=<port number> option is not specified in the trap exploder’s startup command, the trap exploder listens for traps on the port specified by the PORT parameter in the trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the trapd.conf file. The trap exploder startup options are described in “Start the trap exploder” on page 114.

    Mapping of trap exploder configuration steps to configured forwarded trap paths maps the steps (circled numbers) in the trap exploder configuration procedure to the configured forwarded trap paths.

    Figure 1. Mapping of trap exploder configuration steps to configured forwarded trap paths

    To configure the trapd.conf file for the trap exploder:

    1. Go to the BASEDIR/smarts/bin directory in the Service Assurance Manager installation area and type the following command to open the trapd.conf file:

                           sm_edit conf/trapd/trapd.conf

    2. To forward Avaya, Cisco, and Nortel VoIP traps to VoIP Availability Manager, copy and paste the following FORWARD entries from the avaya-trapd.conf, cisco-trapd.conf, and nortel-trapd.conf files to the trapd.conf file.

      Open the appropriate vendor file:

                           sm_edit conf/voip/avaya/avaya-trapd.conf
sm_edit conf/voip/cisco/cisco-trapd.conf
sm_edit conf/voip/nortel/nortel-trapd.conf
# Copy the following section to trapd.conf to forward traps from 
# Trap Forwarder to VoIP Availability Manager

    3. Optional, to forward network traps to IP Availability Manager, add your choice of FORWARD entries to the trapd.conf file.

      The following commented-out lines are the predefined FORWARD statements for IP Availability Manager and IP Performance Manager in the trapd.conf file.

      Uncomment the forwarding statements that you would like to use. For the uncommented forwarding statements, specify the <host>:<port> (host name and port number) of the IP Availability Manager destination that is to receive the trap messages.

      # Traps required by InCharge IP Availability Manager (AM)
#
# Generic: coldStart, warmStart, LinkUp, LinkDown
#FORWARD: * .* <0-3> * host:port
# Cisco: STACK module inserted, removed
#FORWARD: * .1.3.6.1.4.1.9.5 6 <3-4> host:port
# 3Com: CoreBuilder 9000 module inserted
#FORWARD: * .1.3.6.1.4.1.43.28.2 6 6 host:port
# AI: SLC card down, up
#FORWARD: * .1.3.6.1.4.1.539 6 10 host:port
#FORWARD: * .1.3.6.1.4.1.539 6 111 host:port
#FORWARD: * .1.3.6.1.4.1.629 6 10 host:port
#FORWARD: * .1.3.6.1.4.1.629 6 111 host:port
#
# Cisco ISDN demandNbrLayer2Change
#
#FORWARD: * .1.3.6.1.4.1.9.9.26.2 6 3 host:port
#
# Cisco cHsrpStateChange
#
#FORWARD: * .1.3.6.1.4.1.9.9.106.2 6 1 host:port
#
# Traps required by InCharge IP Performance Manager (PM)
#
# Cisco: EnvMon Voltage, Temperature, Fan, RedundantSupply
#FORWARD: * .1.3.6.1.4.1.9.9.13.3 6 <2-5> host:port

    4. To forward Avaya, Cisco, and Nortel VoIP traps to the VoIP Notification Trap Adapter, copy and paste the following FORWARD entries from the avaya-trapd.conf, cisco-trapd.conf, and nortel-trapd.conf files to the trapd.conf file.

      Open the appropriate vendor file:

                           sm_edit conf/voip/avaya/avaya-trapd.conf
sm_edit conf/voip/cisco/cisco-trapd.conf
sm_edit conf/voip/nortel/nortel-trapd.conf
# Copy the following section to trapd.conf to forward traps from
# Trap Forwarder to VoIP Notification Trap Adapter

    5. To forward non-VoIP informational traps to the SNMP Trap Adapter configured as a trap receiver, add your choice of FORWARD entries to the trapd.conf file. Specify the <host name>:<port no> of the trap receiver destination that is to receive the trap messages.

      Note:

      By default, the trap receiver listens for traps on port 9000. Insight into how to change this port number is given in “Configure the trap receiver for Adapter Platform” on page 96.

      # Traps for Trap Receiver and Adapter Platform
<Add your matching criteria for the traps and the forwarding destination: the IP address and trap port of the trap receiver.>

    6. To forward all incoming VoIP analysis traps from managed IPv6 devices to VoIP Availability Manager, add your choice of FORWARD entries (and comments for usability purposes) to the trapd.conf file.

      The following example FORWARD entries forward all incoming IPv6 traps to VoIP Availability Manager. Specify the <host name>:<port no> (for example, myserver.example.com:9001) of the VoIP Availability Manager destination that is to receive the trap messages.

      # Forward all IPv6 traps to VoIP Availability Manager—example
# Match on network prefix
FORWARD: 3ffe:80c0:22c:60:*:*:*:* .* * * <host name>:<port no>

    7. To forward all incoming VoIP informational traps from managed IPv6 devices to VoIP Notification Trap Adapter, add your choice of FORWARD entries (and comments for usability purposes) to the trapd.conf file.

      The following example FORWARD entries forward all incoming IPv6 traps to VoIP Notification Trap Adapter. Specify the <host name>:<port no> of the VoIP Notification Trap Adapter destination that is to receive the trap messages.

      # Forward all IPv6 traps to VoIP Notification Trap
		  Adapter—example
# Match on network prefix
FORWARD: 3ffe:80c0:22c:60:*:*:*:* .* * * <host name>:<port no>

    8. To forward all incoming non-VoIP informational traps from managed IPv6 devices to the SNMP Trap Adapter configured as a trap receiver, add your choice of FORWARD entries to the trapd.conf file. Specify the <host name>:<port no> of the trap receiver destination that is to receive the trap messages.

      # Forward all IPv6 traps to SNMP Trap Adapter—example
# Match on network prefix
FORWARD: 3ffe:80c0:22c:60:*:*:*:* .* * * <host name>:<port no>

    9. Ensure that the ENABLE_FWD parameter is TRUE (default).

    10. Save the file. The modified version of the trapd.conf file is saved to the BASEDIR/smarts/local/conf/trapd directory in the Service Assurance Manager installation area.

    11. Restart the trap exploder as described in “Start the trap exploder” on page 114.

      Any received trap not matching any of the FORWARD entries is discarded.