Prior to Cisco IOS Release 12.3(14)T, ISAKMP-profile and ISAKMP-keyring configurations could be only global, meaning that
the scope of these configurations could not be limited by any locally defined parameters (VRF instances were an exception).
For example, if an ISAKMP keyring contained a preshared key for address 10.11.12.13, the same key would be used if the peer
had the address 10.11.12.13, irrespective of the interface or local address to which the peer was connected. There are situations,
however, in which users prefer that associate keyrings be bound not only with virtual route forwarding (VRF) instances but
also to a particular interface. For example, if instead of VRF instances, there are virtual LANS, and the Internet Key Exchange
(IKE) is negotiated with a group of peers using one fixed virtual LAN (VLAN) interface. Such a group of peers uses a single
preshared key, so if keyrings could be bound to an interface, it would be easy to define a wildcard key without risking that
the keys would also be used for other customers.
Sometimes the identities of the peer are not in the control of the administrator, and even if the same peer negotiates for
different customers, the local termination address is the only way to distinguish the peer. After such a distinction is made,
if the traffic is sent to different VRF instances, configuring an ISAKMP profile is the only way to distinguish the peer.
Unfortunately, when the peer uses an identical identity for all such situations, the ISAKMP profile cannot distinguish among
the negotiations. For such scenarios, it would be beneficial to bind ISAKMP profiles to a local termination address. If a
local termination address could be assigned, identical identities from the peer would not be a problem.