Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[NSM API] Common problems and troubleshooting

0

0

Article ID: KB12931 KB Last Updated: 24 Mar 2009Version: 2.0
Summary:
NSM2008.1r1 introduced a new SOAP API functionality.
This article explains how to troubleshoot problems accessing the API and describe common issues.
Symptoms:
How to troubleshoot common issues like:
  • Authentication failure
  • Communication problem
  • Application error
Solution:

Communication problems

  • NSM API communication uses port TCP/8443 on NSM running on Linux/Solaris Server and TCP/443 on NSMExpress.  These ports must be open and reachable from the test PC.

Authentication failure/application errors

Access to the API is logged in 3 different files located in the NSM GuiSvr log directory /var/netscreen/GuiSvr/errorLog

guiDaemon.0
-----------------

This is the standard log file for the guiSvrManager process.  In this file the API client activity is logged as an incoming GUI connection. The login through a script using the API is equivalent to a login from an NSM GUI client.  This is the log of a correct login procedure:
[11/30/2008 06:34:45.022] [Notice] [11101888-gdNetConfig.c:401] Incoming GUI connection 83000401
[11/30/2008 06:34:45.022] [Notice] [11101888-connectionMgr.c:826] Setting transport mask 10000000
[11/30/2008 06:34:45.100] [Notice] [90733488-nsAuthGUIComm.c:325] client version(2008.2r1), server version(2008.2r1)


NOTE: Using 2008.1r2 with 'schema update' it's possible to have authentication failures with the following logs:
[12/08/2008 22:02:40.769] [Notice] [4391680-gdNetConfig.c:395] Incoming GUI connection 83000401
[12/08/2008 22:02:40.770] [Notice] [4391680-connectionMgr.c:823] Setting transport mask 10000000
[12/08/2008 22:02:40.778] [Notice] [2288427936-nsAuthGUIComm.c:325] client version(2008.1r2), server version(2008.1r2 Updates: 1.10_020_6.1)
[12/08/2008 22:02:40.778] [Error] [2288427936-nsAuthUtils.c:805] Error executing 'authenticate'

This indicated that there is a mismatch between the client version (2008.1r2) and the server version (2008.1r2 Updates: 1.10_020_6.1).
This problem is solved in NSM2008.2.


web_access.[yyyy-mm-dd].log
----------------------------------------
This log file contains the access logs from the HTTP daemon included in NSM.  Normal API logs are similar to followings:
172.26.124.90 - - [30/Nov/2008:06:36:41 +0100] "POST /axis2/services/SystemService HTTP/1.1" 200 890

webproxy.log
-----------------
Standard login logs:
2008/11/30-06:37:54.314 WARN [http-172.30.73.249-8443-Processor24] systemservice.SystemServiceSkeleton - User super domain global: auth success with token c1e9b619-ba26-42aa-a4f7-67a5d5c4f205
2008/11/30-06:37:54.539 DEBUG [http-172.30.73.249-8443-Processor25] core.StandardWrapper - Returning non-STM instance

Consult KB12930 - [NSM API] How to login to the NSM API server for a simple script to verify the authentication; which can also be run on the NSM server itself to exclude network problems.


Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search