How to Verify the Policy-Based Site-to-Site VPN Policy Settings Are Correct (KB ID: KB9516)
| Article ID: | KB9516 |
|---|---|
| Former Article ID: | |
| Published: | Jan 27, 2007 |
| Last Modified: | Jan 27, 2007 |
| Visible By: | Employee, PTAC, Partner, Customer, Public |
Back to Previous Page | Knowledge Base Home
Article URL
Synopsis
This article explains how to verify the Policy-Based Site-to-Site VPN policy settings are correct.
Problem
A Policy-Based Site-to-Site VPN has been configured, but, it is not passing traffic. There is a message in the event log stating:
Phase 2: No policy exists for the proxy ID...
Solution
The Firewall's Event Log Message will list the Local ID, Remote ID, Protocol Number, and Port Number.
- The Local ID is the encryption domain the remote firewall is trying to connect.
- The Remote ID is the internal address of the remote firewall that is trying to connect.
- <0>, <0> = indicates the Protocol and Port Number the remote firewall is sending for both the Local ID and the Remote ID.
To verify the addresses in the policies are correct, compare which fields in the error codes to the policy. See example below.
In this example, Paris is the name of the local firewall and Tokyo is the remote firewall. Tokyo is initiating the traffic, which is causing the Phase 2 error message to appear in the Paris firewall. In this sample image, all of the addresses match. In actuality, one or more incorrect address could cause this error If the addresses appear to be correct, check the Address Book entries to make sure they are correct there. The name of the address book entry might be correct, but, there could be an error in the actual IP address and/or subnet mask.
Another possible cause is that one or more policy for the VPN is pointing to the wrong tunnel. This too will cause the "Phase 2: Proxy ID mismatch error".
Category Description
By Product » Hardware » Firewalls
By Product » Hardware » Firewalls » NetScreen Firewall/IPSec VPN
By Product » Software » Network Operating Systems
By Product » Software » Network Operating Systems » ScreenOS Software
Purpose