10-07-2009 07:51 AM - edited 03-11-2019 09:23 AM
Hi,
I've noticed two set of commands on my asa 5520:
One states: "isakmp policy"
and the other states: "crypto isakmp policy"
Can someone please explain why there are two sets and what the difference is, and when would you use one over the other?
Thanks
Dan
Solved! Go to Solution.
10-07-2009 08:05 AM
Dan
They do the same thing. The isakmp policy commands have been replaced with the crypto isakmp policy commands -
http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/c5.html#wp2191760
Jon
10-07-2009 08:11 AM
Dan-
There is no difference between the two.
ASA1(config)# isakmp ?
configure mode commands/options:
am-disable Disable inbound aggressive mode connections
client Set client configuration policy (DEPRECATED - see 'help
isakmp')
disconnect-notify Enable disconnect notification to peers
enable Enable ISAKMP on the specified interface
identity Set identity type (address, hostname or key-id)
ipsec-over-tcp Enable and configure IPSec over TCP
keepalive Set keepalive interval (DEPRECATED - see 'help isakmp')
key Set pre-shared key for remote peer (DEPRECATED - see 'help
isakmp')
nat-traversal Enable and configure nat-traversal
peer Set xauth and config mode exemption for the specified peer
(DEPRECATED - see 'help isakmp')
policy Set ISAKMP policy suite
reload-wait Wait for voluntary termination of existing connections
before reboot
ASA1(config)# crypto isakmp ?
configure mode commands/options:
am-disable Disable inbound aggressive mode connections
client Set client configuration policy (DEPRECATED - see 'help
isakmp')
disconnect-notify Enable disconnect notification to peers
enable Enable ISAKMP on the specified interface
identity Set identity type (address, hostname or key-id)
ipsec-over-tcp Enable and configure IPSec over TCP
keepalive Set keepalive interval (DEPRECATED - see 'help isakmp')
key Set pre-shared key for remote peer (DEPRECATED - see 'help
isakmp')
nat-traversal Enable and configure nat-traversal
peer Set xauth and config mode exemption for the specified peer
(DEPRECATED - see 'help isakmp')
policy Set ISAKMP policy suite
reload-wait Wait for voluntary termination of existing connections
before reboot
"iskamp policy" is left over from the 6.x code, I have to assume for backwards compatibility.
Hope that helps.
10-07-2009 08:05 AM
Dan
They do the same thing. The isakmp policy commands have been replaced with the crypto isakmp policy commands -
http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/c5.html#wp2191760
Jon
10-07-2009 08:11 AM
Dan-
There is no difference between the two.
ASA1(config)# isakmp ?
configure mode commands/options:
am-disable Disable inbound aggressive mode connections
client Set client configuration policy (DEPRECATED - see 'help
isakmp')
disconnect-notify Enable disconnect notification to peers
enable Enable ISAKMP on the specified interface
identity Set identity type (address, hostname or key-id)
ipsec-over-tcp Enable and configure IPSec over TCP
keepalive Set keepalive interval (DEPRECATED - see 'help isakmp')
key Set pre-shared key for remote peer (DEPRECATED - see 'help
isakmp')
nat-traversal Enable and configure nat-traversal
peer Set xauth and config mode exemption for the specified peer
(DEPRECATED - see 'help isakmp')
policy Set ISAKMP policy suite
reload-wait Wait for voluntary termination of existing connections
before reboot
ASA1(config)# crypto isakmp ?
configure mode commands/options:
am-disable Disable inbound aggressive mode connections
client Set client configuration policy (DEPRECATED - see 'help
isakmp')
disconnect-notify Enable disconnect notification to peers
enable Enable ISAKMP on the specified interface
identity Set identity type (address, hostname or key-id)
ipsec-over-tcp Enable and configure IPSec over TCP
keepalive Set keepalive interval (DEPRECATED - see 'help isakmp')
key Set pre-shared key for remote peer (DEPRECATED - see 'help
isakmp')
nat-traversal Enable and configure nat-traversal
peer Set xauth and config mode exemption for the specified peer
(DEPRECATED - see 'help isakmp')
policy Set ISAKMP policy suite
reload-wait Wait for voluntary termination of existing connections
before reboot
"iskamp policy" is left over from the 6.x code, I have to assume for backwards compatibility.
Hope that helps.
10-07-2009 08:18 AM
Sorry for the hijacking Jon, you're still quicker than I am.
10-07-2009 08:21 AM
Collin
No need to apologize, i've done it to you before.
Key thing is that we both agree :-)
Jon
10-07-2009 08:29 AM
Im not hijacking here just commenting - the more additional info the better
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide