SNMP Input Adapter Sample

In the Package Explorer view, double-click snmp.sbapp.

If you wish the adapter to listen on a UDP port different from the standard for SNMP traps (port 162):

Click the Run button. This opens the SB Test/Debug perspective and starts the application.

In the Test/Debug Perspective, open the Application Output view. Look for a tuple emitted on the Status stream with its action value set to Connected, indicating that the adapter has established a connection to the configured port and is listening for traps.

In the Manual Input view, select the Commands stream. Enter disconnect in the command field. Click Send Data and observe that a tuple has been emitted on the Status stream, and a message has been printed to the console to indicate the adapter has disconnected from the configured port.

In the Manual Input view, select the Commands stream again. Enter connect in the command field. Click Send Data and observe that a tuple has been emitted on the Status stream, and a message has been printed to the console to indicate the adapter has reconnected to the port and is again listening for traps.

To see traps being emitted by the adapter, you may cause one to be sent via the use of an application capable of acting as an SNMP agent and sending traps, such as the snmptrap utility included in the open-source Net-SNMP project. You can use the following snmptrap command to generate a v1 trap:

snmptrap -v 1 -c private localhost 
  NET-SNMP-EXAMPLES-MIB::netSnmpExampleHeartbeatNotification 
  "" 6 17 "" netSnmpExampleHeartbeatRate i 123456

(Lines in the single command above are shown wrapped for clarity.)

As traps are received by the adapter you will see a tuple emitted on the Traps stream describing its contents.

When done, press F9 or click the Stop Running Application button.

Open three terminal windows on UNIX, or three StreamBase Command Prompts on Windows. In each window, navigate to your workspace copy of the sample, as described above.

In window 1, type:

sbd snmp.sbapp

In window 2, type:

sbc dequeue -v

This window displays the tuples dequeued from the adapter's output ports.

In window 3, disconnect from the UDP port:

echo disconnect | sbc enqueue Commands

Observe in window 2 that a Disconnected Tuple is emitted from the Status port and a message is issued in window 1 to indicate the adapter has disconnected from the UDP port and is no longer listening for traps.

In window 3, reconnect to the UDP port:

echo connect | sbc enqueue Commands

Observe in window 2 that a Connected Tuple is again emitted from the Status stream. A message is issued in window 1 to indicate the adapter has reconnected to the UDP port and listening to SNMP traps.

To see traps being emitted by the adapter, you may cause one to be sent via the use of an application capable of acting as an SNMP agent and sending traps, such as the snmptrap utility included in the open-source Net-SNMP project. You can use the following snmptrap command in window 3 to generate a v1 trap: snmptrap -v 1 -c private localhost NET-SNMP-EXAMPLES-MIB::netSnmpExampleHeartbeatNotification "" 6 17 "" netSnmpExampleHeartbeatRate i 123456

Observe in window 2 that a new tuple has been emitted on the Traps stream for each trap received by the adapter.

In window 3, type the following command to terminate the server and dequeuer:

sbadmin shutdown