topic Re: Peer identifier for azure is required to be set in General Topics

Peer identifier for azure is required to be set

CATSatIDS — Wed, 08 Aug 2012 21:38:09 GMT

I have got a tunnel set up successfully to Azure but have had to specify the peer identifier by IP address which will not be very stable. Azure support advise that the peer identifier set by azure is dynamic and that some firewall vendors (Cisco, Juniper) do not require the peer identifier to be statically set. On Palo Alto I got:

ike-generic event - peer identifier (type idaddr [10.1.1.2]) does not match remote AzureCloud

Please see Azure VPN with Sonicwall - peer IKE ID for details

Is there any more stable work around?

Thanks

David

Re: Peer identifier for azure is required to be set

jrhjrh — Wed, 03 Oct 2012 12:42:25 GMT

Hi David,

I am facing the same issue with this - did you make any progress?

Thanks,

James

Re: Peer identifier for azure is required to be set

sdurga — Wed, 03 Oct 2012 16:14:14 GMT

Since the peerid on the Azure side changes on PA side you would need to be able to identify the peer by using various means instead of IP like FQDN or email address or Key IDinstead of IP. Azure will send local ID as FQDN (i.e.azure.domain.com). PA side should have same for peer ID. You will also need to have both sides in aggressive mode as well (default is main mode). In this case Azure should be initiating tunnel all the time. The sample config on PA looks like this

Re: Peer identifier for azure is required to be set

infra — Sun, 09 Dec 2012 20:37:24 GMT

Hello David, James,

currently I'm trying to setup the VPN connection with Azure. But I'm having trouble with the basic setup of the IPSec connection.

Can you share with me a configuration of the IPsec setup to Azure?

Thanks

Rob