topic Re: Tunnel Monitor Configuration question in General Topics

Tunnel Monitor Configuration question

rking13 — Tue, 04 Feb 2014 22:31:20 GMT

Operation	Commit
Result	Failed
DetailsIPSec tunnel #NAME enabled tunnel monitoring while binding to tunnel interface tunnel which has no IP address assigned to it yet.

I receive this error when configuring a tunnel monitor to the IPSec tunnel. I'm guessing the actual tunnel interface needs an IP, what what kind of configuration is needed when that IP address is added to the tunnel? Will that IP be of local significance or do I have to add that IP to the other end of my tunnel?

Thanks,

Ryan

Re: Tunnel Monitor Configuration question

Phoenix — Tue, 04 Feb 2014 22:40:32 GMT

Hello rking13,

Yes you are right, for tunnel monitoring we will have to configure the IP address for the tunnel as it would initiate keep alives to the other end. This IP is a local significance after the tunnel is established. Can you test by providing a private IP and it would start to work.

Thanks

Re: Tunnel Monitor Configuration question

Mystique — Tue, 04 Feb 2014 22:42:46 GMT

Please refer to below links:

How to Verify if the IPSec Tunnel Monitoring is Working?

Selecting an IP Address to use for PBF or Tunnel Monitoring

Re: Tunnel Monitor Configuration question

rking13 — Tue, 04 Feb 2014 22:46:56 GMT

Does the private IP assigned to the tunnel need to be a part of any of the protected networks? For example, 192.168.0.1/24 is a protected network currently being sent over the tunnel, so my tunnel address would be 192.168.0.2?

EDIT: OK so I'm going to configure my tunnel with IP 172.16.25.1/32, add it to the crypto map for both local and remote endpoints, and that should do it? I'll have to try testing it out when no one is on

Re: Tunnel Monitor Configuration question

HULK — Wed, 05 Feb 2014 02:03:16 GMT

Hello Sir,

You can configure the tunnel interface with any IP address as long as the IPSEC Peer is configured with the appropriate proxy ID/route (not necessary should be part of same subnet i.e. 192.168.0.2).

For example, you can set the tunnel interface to 10.10.10.100/24 - this would require the peer to have 10.10.10.100/24 or 10.10.10.100/32 configured as the remote(PaloAlto) proxy ID ( Along with protected resources 192.168.0.0/24). Also, when configuring an IP address to 'monitor' you will want to set an IP address in the peer's proxy ID so the traffic will get pushed through the tunnel.

Hope this helps.

Thanks