Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Monitor Juniper Secure Connect

 

In case of any issues, we recommend that you follow these steps to check the log messages and locate the issue:

  • Check the logs in Junos OS

  • Check the logs in the Juniper Secure Connect application

Check Junos OS Logs

You must configure syslog to save the syslog file on your device. Currently, J-Web does not support structured logs. Only unstructured logs are supported.

Depending on the syslog format (for structured logs) you configure in the system, you might not find the log messages under Monitor > Events > System. Because of this, we recommend that you download the "messages" file from Device Administration > Operations > Files and search for the event.

For the unstructured logs (in J-Web), to find information about the success or failure of authentication:

  • For a Juniper Secure Connect application configuration download, search for "REMOTE_ACCESS".

  • For a VPN connection, search for "KMD_".

Following is the result of "REMOTE_ACCESS" search:

Figure 1: "REMOTE_ACCESS" Search Results
"REMOTE_ACCESS" Search Results

By default, J-Web displays warning and error messages. If you want to view info level messages, change the syslog configuration using CLI. Table 1 lists the supported log levels:

Table 1: Syslog Severity Levels

Log severity Level

Description

alert

Indicates conditions that require immediate correction, such as a corrupted system database.

any

Indicates all log levels.

critical

Indicates critical conditions, such as hard drive errors.

emergency

Indicates system panic or other conditions that cause the routing platform to stop functioning.

error

Indicates standard error conditions.

info

Only informational messages.

none

No messages.

notice

Indicates conditions that should be handled specially.

warning

Indicates conditions that warrant monitoring.

You can view the stream (traffic or routing engine) logs by navigating to Monitor > Events > IPsec VPN page.

Check Juniper Secure Connect Application Logs

Windows

  1. The log is continuously active in the background, even if the log window is not open. All the relevant Juniper Secure Connect communication events are displayed and saved for one week per operation day, in a log file. The files older than seven online days are automatically deleted.

    The log file is generated automatically in the installation directory under the Log folder when the communication process is completed. The log file is named in NCPyymmdd.LOG format, where yy=year, mm=month, and dd=date. Select Help > Logbook to view the log messages in the log book page.

    You can change the storage time for log files using the Extended Log Settings option. You can open and analyze the log files using a text editor.

    Figure 2: Logbook Menu Option
    Logbook Menu Option
    Figure 3: Log Message Display
     Log Message Display
  2. From the menu bar, click Help and then select Extended Log Settings.
    Figure 4: Extended Log Settings Menu Option
     Extended Log Settings Menu Option
  3. Enable all options by selecting all the check boxes, and then click OK.
    Figure 5: Extended Log Settings
    Extended Log Settings
  4. Open the logbook and check for any log messages that indicate the problem. If you cannot resolve your issue based upon the log messages, start the Support Assistant by clicking Help and then selecting Support Assistant. The Support Assistant collects all the required data.
    Figure 6: Support Assistant Menu Option
    Support Assistant Menu Option
  5. Click Add to attach any additional files, and then click Next. The Save archive file page opens.
    Figure 7: Save Archive File
     Save Archive File
    Figure 8: Log Files List
    Log Files List
  6. Select the Only create the archive file option button. Then, click Next.
    Figure 9: Create Only Archive File
    Create Only Archive File

    After the archival process is completed, Juniper Secure Connect displays the archived file location.

    Figure 10: Successful Creation of Log Files Archival
     Successful Creation of Log Files Archival
  7. Click Finish.

macOS

Following are the steps to check the Juniper Secure Connect application logs on a macOS platform:

  1. Select Log > Logbook through the Juniper Secure Connect application menu to open the logbook.
    Figure 11: Logbook Menu Option
    Logbook Menu Option

    Check for any log messages that indicate the problem.

    Figure 12: Displaying Log Information
    Displaying Log Information
  2. If you are not able to resolve the issue, save this log message into a file with the ncpmonlog.txt filename. Copy the file ncpphone.cfg to the same location where you saved the logbook file /Library/Application Support/Juniper/SecureConnect/ncpphone.cfg.
  3. To locate the ncpphone.cfg file, open the Finder and select Go in the menu bar and at the same time press down the “Option” key on your keyboard.
    Figure 13: Open File Library
    Open File Library

    The directory location where the Juniper Secure Connect files are saved is displayed.

    Figure 14: Juniper Secure Connect Directory
    Juniper Secure Connect Directory

Android

Following are the steps to check the Juniper Secure Connect application logs on an Android device:

In the Juniper Secure Connect application menu, click the three vertical dots at the top right corner and select Log from the menu.

Figure 15: Juniper Secure Connect Application Screen
Juniper Secure Connect Application Screen
Figure 16: Log Menu Option
Log Menu Option

The log output window appears, displaying the log messages.

Figure 17: Displaying Log Information
Displaying Log Information

iOS

The log is continuously active in the background, even if the log window is closed. All the relevant Juniper Secure Connect communication events are saved in the log file. Navigate to Diagnostics > Debugging > Error Log to view the log messages. Click on the export icon right on top of the screen to send the log file through the offered applications.

Figure 18 shows a sample log message for an active VPN connection.

Figure 18: Log Messages
 Log Messages