What is IKE?
Well it is the protocol that is used to actually setup the SA. It is during the SA negotiation that various options are chosen. One option that can be enabled is anti-replay protection. There are other options that can be enabled, and likely should be depending on your needs. IKE itself and its role really boils down to its authenticating two IPSec end points and helping to set up a secure tunnel between them. IKE will perform this role over what are called two phases. Phase I will authenticate the identity of both IPSec end points. During Phase I, IKE will also negotiate matching SAs (security associations) between the two end points allowing them to communicate safely and securely. This in turn allows IKE to securely take care of Phase II. Another key point is that an authenticated Diffie-Hellman exchange will occur with the end result being that both end points will have matching shared secret keys. The above noted Phase I though can be broken down into two modes. These are main mod
IKE is short for Internet Key Exchange. Key Management allows you to determine whether to use IKE (ISAKMP) or manual key configuration to set up a VPN. There are two phases in every IKE negotiation- phase 1 (Authentication) and phase 2 (Key Exchange). Phase 1 establishes an moIKE SA and phase 2 uses that SA to negotiate SAs for IPSec.
IKE is short for Internet Key Exchange. Key Management allows you to determine whether to use IKE (ISAKMP) or manual key configuration to set up a VPN. There are two phases in every IKE negotiation- phase 1 (Authentication) and phase 2 (Key Exchange). Phase 1 establishes an IKE SA and phase 2 uses that SA to negotiate SAs for IPSec.
