Knowledge Search


×
 

How to Find the VPN Entry in the Event Log?

  [KB4426] Show Article Properties


Summary:

VPN appears to be down.  How to locate the status messages in the Event Log?

Symptoms:

How to Find the VPN Entry in the Event Log?

Solution:

A VPN problem can be troubleshot more accurately and faster by reviewing the event log on the responder firewall. The responder is the "receiver" side of the VPN that is being pinged, receiving the tunnel set up requests, or receiving the tunneled traffic. The initiator is the side of the VPN from which the ping or traffic is generated. 

Note:  In the case of a Dial-Up VPN (which is a VPN between a Juniper Firewall and a PC running the NetScreen Remote Client software), the initiator is always the PC and the responder is the Juniper Firewall.

Perform the following steps on the responder firewall:

CLI Steps:

 Open the Command Line Interface (CLI). For more information on how to open the CLI, go to Accessing the Command Line Interface Using Telnet.

  Information in the event log is displayed using the CLI command:  get event.  To display information for a specific VPN, include the IP address of the VPN Peer Gateway (the initiator’s IP address).     For example: 

get event include 1.1.1.2  

Where 1.1.1.2 is the VPN Peer Gateway IP Address.


Do not use the pipe ( | ) symbol in the get event command.  It will cause the output to NOT display the complete message.

 

WebUI Steps:

Step 1.  To display the event logs via the WebUI, from the navigation tree on the left side of the screen, click on:

Reports > System Log > Event

Step 2. Search on the Peer Gateway's IP address.  This is the public IP of the initiating VPN device. 

Alternately, type the IP address of the Peer Gateway into the Search field.  Then click on the Search button.

 

The following is an example of an Event Log.   The most recent message is listed at the top.


The above steps may display IKE Phase 2 and/or Phase 1 messages.   

2004-04-06 16:24:25 system info 00536 IKE<1.1.1.2> Phase 2 msg ID <4717e7ea>: Negotiations have failed.

2004-04-06 16:24:25 system info 00536 from 1.1.1.2:500 to 1.1.1.1:500 with cookies cfaf76fe7f73ae52 and 57436be50cbe5372 because the peer sent a proxy ID that did not match the one in the SA config.

2004-04-06 16:24:25 system info 00536 IKE<1.1.1.2> Phase 2: No policy exists for the proxy ID received: local ID (<192.168.1.0>/<255.255.255.0>, <0>, <0>) remote ID (<192.168.2.0>/ <255.255.255.0>, <0>, <0>).

2004-04-06 16:24:25 system info 00536 IKE<1.1.1.2> Phase 2 msg ID <4717e7ea>: Responded to the peer's first message. 

 

If there are no messages; make sure the correct IP address was used.   It is also possible that the event log filled up with other messages, so try to ping across the tunnel in order to attempt to bring the VPN up again.  If there are still no messages, refer to KB9221- How to Troubleshoot a Site-to-Site VPN Tunnel that wont come up.

Related Links: