Looking at what you're trying to do, I think using a VTI would be a more streamlined configuration. It's also a little bit easier to configure. We use VTI to connect to remote locations and pass routing protocols thru it. That's highly recommended by Cisco also.
While I agree that this situation could be done with VTI and that VTI does have some advantages, that does not address the main question in the original post which is why the tunnel is not working.
I will start by observing that Cisco warns the crypto maps using access lists with permit ip any any can cause problems. So the original poster would be well advised to change that part of the configuration. In this situation all the access list needs to do is permit gre host 192.168.207.97 host 192.168.207.98
But I believe that this is not the major problem. The major problem is that for the tunnel to work there must be interesting traffic to send through the tunnel. The router has only a single physical interface that has an IP address and that has a /30 mask. So where will traffic come from that will go through the tunnel and cause the tunnel to work?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...