[IKEv1]: Group = salesgroup, Username = salesuser,(18)
IP = 220.127.116.11, Adding static route for client address:
[IKEv1]: Group = salesgroup, Username = salesuser,(19)
IP = 18.104.22.168, PHASE 2 COMPLETED (msgid=d9fcc34b)
[IKEv1 DEBUG]: Group = salesgroup, Username = salesuser,(20)
IP = 22.214.171.124, Received keep-alive of type DPD R-U-THERE
(seq number 0xa780a31f)
[IKEv1 DEBUG]: Group = salesgroup, Username = salesuser,
IP = 126.96.36.199, Sending keep-alive of type DPD R-U-THERE-ACK
(seq number 0xa780a31f)
Here's an explanation of the debug output:
The Remote (188.8.131.52) initiates a session to the appliance (acting as a Server).
The Remote sends its identity type to the Server, along with the group it wants to connect to ("salesgroup").
A matching Phase 1 policy is found: policy 5 of the Remote matches the first policy of the Server).
The Remote initiates IKE Mode Config and the appliance is determining which parameters it has configured for the associated group.
The group authentication is successful, as is the XAUTH authentication via the user account "salesuser"; notice that this message appears here rather than before IKE Mode Config, because the appliance needs to verify whether or not the user is allowed access to the group.
The Remote sends an IKE Mode Config request for the policies defined for the salesgroup group.
During IKE Mode Config, the appliance learns the client type and version.
The Server sends back the IKE Mode Config parameters.
This completes ISAKMP/IKE Phase 1.
Quick mode begins with an exchange of policies.
The internal address of the client is 192.168.2.200 and the proxy message it sends indicates that all of its traffic is to be protected (the group policy is split tunneling disabled).
A check is performed to make sure that the client isn't reconnecting (the Initial Contact feature for Easy VPN); in this example, the client is initiating a new connection.
The appliance compares the proxy information with its first crypto map entry (which is a static one) and finds that it doesn't match this entry (the proxy information doesn't match).
The appliance compares the proxy information with its second crypto map entry, which is a dynamic crypto map for remote access users.
A matching data transform is found.
There is a difference in the data SA lifetime values between the two devices: the lower one (28,800 seconds) is negotiated.
The two IPsec data SAs (inbound and outbound) are created and SPIs are assigned.
Because RRI is enabled, a static route for the Remote's internal address (192.168.2.200) is added to the Server's local routing table.
Phase 2 has completed.
Because DPD was negotiated in Phase 1, DPD now takes place; in this instance, the Remote is initiating DPD (however, both sides of the tunnel will do this periodically based on their local keepalive counters).
Hi Guys,I would like to ask what will happen if the license consumption of ISE has been exceeded? Will it still accepts new authentication requests or will it drop some endpoints which are already been authenticated in a random manner? Thanks
I have gone over the scaling guide and the install guide but it's never been clear to me why the fully distributed deployment PAN needs to have so much CPU and memory. The job of the PAN is to keep the database synchronised with all the other...
We have Cisco Asa5516-x at the data center that makes site to site vpn tunnels with remote offices, recently we are observing some of the site VPN tunnels and any connect clients are getting disconnect 1- we have 8 site to site vpn tunnels with...
Hello,We recently changes our firewall policies on our FMC to block a lot more countries by GeoLocation then we ever have. In the same coin my company does a lot of international business, mostly with Germany, Finland, Norway, Japan, Spain, Canada. W...