Troubleshoot an issue if traps are not being received by the STA server, or traps are not being processed by STA.

1. Log in to the STA server as the system root user.
2. Verify that the STA server is using a static IP address.
3. Monitor TCP/IP packets sent between the STA server and the library.

   # tcpdump –v host <IP address of library public port> > /var/tmp/<output file name> &
   

4. In the output, look for .snmptrap and SNMPv3. Network traffic for data collection requests contain .snmp.

   If there is activity on the library, but no traps are being received, check the library trap recipient entry for accuracy. See Troubleshoot a Failed Trap Channel Test.

5. Verify that SNMP port 162 is available for STA. The STA trap listener processes traps through this port.
   If necessary, troubleshoot communications over this port:
   1. Check the /Oracle_storage_home/Middleware/user_projects/domains/tbi/servers/staAdapter/logs/staAdapter.log file for a "SEVERE" error, such as:
      "SEVERE: SNMP Trap/Inform Listener Port 162 is NOT bindable. Stop the application currently bound to that port."
   2. If port 162 is already in use, determine what process is using it.

      # netstat –ap |grep –I snmp
      # netstat –anp |grep ":162"
      

   3. Follow the process associated with the port, or check what services may have started during system boot.

      # chkconfig ––list
      

6. If the snmpd or snmtrapd services are running, ensure they are disabled:
   1. Deconfigure SNMP services.

      # systemctl stop snmpd
      # systemctl stop snmptrapd
      

   2. Stop SNMP services.

      # systemctl disable snmpd
      # systemctl disable snmptrapd
      

   3. Stop and restart STA services.

      # STA stop all
      # STA start all
      

7. If some traps are being reported in the STA Notifications screen, verify that all trap levels were specified when creating a trap recipient on the library. See the SNMP v3 trap recipient creation procedure in the Create the STA SNMP v3 Trap Recipient for the list of supported trap levels.
8. For the SL500, verify that you configured the library with a supported version of SL Console. Earlier versions of SL Console restrict the number of trap level characters that can be entered.
9. For SL500 and SL150 libraries, verify that the Volume Label Format is set properly.