Corente Reporting "we require peer to have ID 'xx.xx.xx.xx', but peer declares 'xx.xx.xx.xx'" for 3rd-Party Device
Last updated on NOVEMBER 14, 2016
Applies to:Corente Cloud Services Exchange - Version 9.4 and later
Information in this document applies to any platform.
The two locations can not establish a VPN tunnel
The 3rd-Party device is configured with 'yy.yy.yyy.yy' as its WAN IP and 'xx.xx.xxx.xx' as its visible IP.
On the CSG /var/log/secure reports:
Aug 30 10:46:47 CSG_NAME pluto: "T.3rd-Party.1062007" #15934: Main mode peer ID is ID_IPV4_ADDR: 'xx.xx.xxx.xx'
Aug 30 10:46:47 CSG_NAME pluto: "T.3rd-Party.1062007" #15934: we require peer to have ID 'yy.yy.yyy.yy', but peer declares 'xx.xx.xx.xx'
Aug 30 10:46:47 CSG_NAME pluto: "T.3rd-Party.1062007" #15934: sending encrypted notification INVALID_ID_INFORMATION to yy.yy.yyy.yy:4500
Tunnel never comes active.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms