Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1982911.1
Update Date:2018-05-04
Keywords:

Solution Type  Troubleshooting Sure

Solution  1982911.1 :   Troubleshooting NSP Alarm Forwarding by Email (SMTP)  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Purpose
Troubleshooting Steps
References


Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 7.1 and later
Information in this document applies to any platform.

Purpose

This document describes main steps to troubleshoot problem for email forwarding by NSP.

Troubleshooting Steps

Steps below must be followed to find the cause of email not being forwarded:

  1. Check that mail.server host is defined in /etc/hosts file of Weblogic server(s).
  2. Check connectivity:
    telnet mail.server 25
    Example of failed output:  
    Trying 127.0.0.1...
    telnet: connect to address 127.0.0.1: Connection refused
    If test is failing, mail.server must be defined via platcfg menu (see customer integration documentation) and test email forwarding again.
  3. Check JMS queues:
    1. Login to NSP Weblogic console http://<ip_of_nsp>/console
    2. Click Services => Messaging => JMS Servers => NSPJMSServer1a => Monitoring tab => Active Destinations tab
    3. Check each queue knowing that events are following this path:
      Messages Pending must not increase and, in normal situation, is even equal to 0.
      Messages Received must increased for each event forwarded.
      1. JMX2ListernerQueue
      2. EventListenerQueue
      3. EvaluationObjectQueue
      4. JMSForwardingQueue
      5. jmsSMTPQueue.
        If this queue is filling, it means that weblogic is probably not able to reach mail.server or mail.server rejects emails. Check application.log for possible causes.
    4. Repeat steps b and c for each JMS servers:
      1. On one box NSP: NSPJMSServer1a and NSPJMSServer1b
      2. On four boxes NSP: NSPJMSServer1a, NSPJMSServer1b, NSPJMSServer2a and NSPJMSServer2b
  4. If application.log has following error:
    Caused by: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25;
    NspMailSession properties must be checked:
    1. Login to NSP Weblogic console http://<ip_of_nsp>/console
    2. Click Services
    3. Click MailSessions
    4. Click NspMailSession
    5. JavaMail Properties should not include spaces and should look similar to:

        
      mail.transport.protocol=smtp 

      mail.smtp.host=mail.server 

      mail.smtp.from=noreply@tekelec.com 

      mail.smtp.timeout=500 

      mail.smtp.connectiontimeout=500
      Any changes to this field requires a nspservice restart.

References

<NOTE:2012407.1> - Troubleshooting NSP Alarm Forwarding by SNMP traps

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback