-
Cisco Security Appliance Command Reference, Version 8.0
-
About This Guide
-
Using the Command Line Interface
- A through B Commands
- C Commands
- D through F Commands
- G through I Commands
- J through L Commands
- M through O Commands
- P though R Commands
-
S Commands
-
same-security-traffic -- show asdm sessions
-
show asp drop -- show curpriv
-
show ddns -- show ipv6 traffic
-
show isakmp sa -- show route
-
show running-config -- show running-config isakmp
-
show running-config ldap -- show running-config webvpn auto-signon
-
show service-policy -- show xlate
-
shun -- sysopt radius ignore-secret
-
- T through Z Commands
-
Table Of Contents
crypto ca authenticate through customization Commands
crypto ca server user-db allow
crypto ca server user-db email-otp
crypto ca server user-db remove
crypto ca server user-db show-otp
crypto ca server user-db write
crypto dynamic-map match address
crypto dynamic-map set nat-t-disable
crypto dynamic-map set reverse route
crypto dynamic-map set transform-set
crypto ipsec security-association lifetime
crypto ipsec security-association replay
crypto ipsec transform-set (create or remove transform set)
crypto isakmp disconnect-notify
crypto isakmp policy authentication
crypto isakmp policy encryption
crypto map ipsec-isakmp dynamic
crypto map set connection-type
crypto map set security-association lifetime
crypto ca authenticate through customization Commands
crypto ca authenticate
To install and authenticate the CA certificates associated with a trustpoint, use the crypto ca authenticate command in global configuration mode. To remove the CA certificate, use the no form of this command.
crypto ca authenticate trustpoint [fingerprint hexvalue] [nointeractive]
no crypto ca authenticate trustpoint
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
If the trustpoint is configured for SCEP enrollment, the CA certificate is downloaded through SCEP. If not, the security appliance prompts you to paste the base-64 formatted CA certificate onto the terminal.
The invocations of this command do not become part of the running configuration.
Examples
The following example shows the security appliance requesting the certificate of the CA. The CA sends its certificate and the security appliance prompts the administrator to verify the certificate of the CA by checking the CA certificate fingerprint. The security appliance administrator should verify the fingerprint value displayed against a known, correct value. If the fingerprint displayed by the security appliance matches the correct value, you should accept the certificate as valid.
hostname(config)# crypto ca authenticate mycaCertificate has the following attributes:Fingerprint: 0123 4567 89AB CDEF 0123Do you accept this certificate? [yes/no] y#hostname(config)#In the next example, the trustpoint tp9 is configured for terminal-based (manual) enrollment. In this case thesecurity appliance prompts the administrator to paste the CA certificate to the terminal. After displaying the fingerprint of the certificate, the security appliance prompts the administrator to confirm that the certificate should be retained.
hostname(config)# crypto ca authenticate tp9Enter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itselfMIIDjjCCAvegAwIBAgIQejIaQ3SJRIBMHcvDdgOsKTANBgkqhkiG9w0BAQUFADBAMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExETAPBgNVBAcTCEZyYW5rbGluMREwDwYDVQQDEwhCcmlhbnNDQTAeFw0wMjEwMTcxODE5MTJaFw0wNjEwMjQxOTU3MDhaMEAxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTERMA8GA1UEBxMIRnJhbmtsaW4xETAPBgNVBAMTCEJyaWFuc0NBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCdjXEPvNnkZD1bKzahbTHuRot1T8KRUbCP5aWKfqViKJENzI2GnAheArazsAcc4EazLDnpuyyqa0j5LA3MI577MoN1/nll018fbpqOf9eVDPJDkYTvtZ/X3vJgnEjTOWyzT0pXxhdU1b/jgqVE74OvKBzU7A2yoQ2hMYzwVbGkewIDAQABo4IBhzCCAYMwEwYJKwYBBAGCNxQCBAYeBABDAEEwCwYDVR0PBAQDAgFGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFBHr3holowFDmniI3FBwKpSEucdtMIIBGwYDVR0fBIIBEjCCAQ4wgcaggcOggcCGgb1sZGFwOi8vL0NOPUJyaWFuc0NBLENOPWJyaWFuLXcyay1zdnIsQ049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9YnJpYW5wZGMsREM9YmRzLERDPWNvbT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Y2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnQwQ6BBoD+GPWh0dHA6Ly9icmlhbi13Mmstc3ZyLmJyaWFucGRjLmJkcy5jb20vQ2VydEVucm9sbC9CcmlhbnNDQS5jcmwwEAYJKwYBBAGCNxUBBAMCAQEwDQYJKoZIhvcNAQEFBQADgYEAdLhc4Za3AbMjRq66xH1qJWxKUzd4nE9wOrhGgA1rj4B/Hv2K1gUie34xGqu9OpwqvJgp/vCU12Ciykb1YdSDy/PxN4KtR9Xd1JDQMbu5f20AYqCG5vpPWavCgmgTLcdwKa3ps1YSWGkhWmScHHSiGg1a3tevYVwhHNPA4mWo7sQ=Certificate has the following attributes:Fingerprint: 21B598D5 4A81F3E5 0B24D12E 3F89C2E4% Do you accept this certificate? [yes/no]: yesTrustpoint CA certificate accepted.% Certificate successfully importedhostname(config)#Related Commands
crypto ca certificate chain
To enter certificate chain configuration mode for the indicated trustpoint, use the crypto ca certificate chain command in global configuration mode. To return to global configuration mode, use the exit command.
crypto ca certificate chain trustpoint
Syntax Description
Syntax DescriptionSyntax Description
Defaults
This command has no default values.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
•
—
:
Command History
Examples
The following example enters CA certificate chain submode for trustpoint central:
hostname<config># crypto ca certificate chain centralhostname<config-cert-chain>#Related Commands
crypto ca certificate map
To enter CA certificate map mode, use the crypto ca configuration map command in global configuration mode. Executing this command places you in ca-certificate-map mode. Use this group of commands to maintain a prioritized list of certificate mapping rules. The sequence number orders the mapping rules. To remove a crypto CA configuration map rule, use the no form of the command.
crypto ca certificate map {sequence-number | map-name sequence-number}
no crypto ca certificate map {sequence-number | map-name [sequence-number]}
Syntax Description
Defaults
No default behavior or values for sequence-number.
The default value for map-name is DefaultCertificateMap.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
•
—
:
Command History
Usage Guidelines
Issuing this command places the security appliance in CA certificate map configuration mode where the user can configure rules based on the certificate's issuer and subject distinguished names (DNs). The general form of these rules is as follows:
DN match-criteria match-value
DN is either subject-name or issuer-name. DNs are defined in the ITU-T X.509 standard. For a list of certificate fields, see Related Commands.
match-criteria comprise the following expressions or operators:
attr tag
Limits the comparison to a specific DN attribute, such as common name (CN).
co
Contains
eq
Equal
nc
Does not contain
ne
Not equal
The DN matching expressions are case insensitive.
Examples
The following example enters CA certificate map mode with a map named example-map and a sequence number of 1 (rule # 1), and specifies that the common name(CN) attribute of the subject-name must match Example1:
hostname(config)# crypto ca certificate map example-map 1hostname(ca-certificate-map)# subject-name attr cn eq Example1hostname(ca-certificate-map)#The following example enters CA certificate map mode with a map named example-map and a sequence number of 1, and specifies that the subject-name contain the value cisco anywhere within it:
hostname(config)# crypto ca certificate map example-map 1hostname(ca-certificate-map)# subject-name co ciscohostname(ca-certificate-map)#Related Commands
crypto ca crl request
To request a CRL based on the configuration parameters of the specified trustpoint, use the crypto ca crl request command in crypto ca trustpoint configuration mode.
crypto ca crl request trustpoint
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Crypto ca trustpoint configuration
•
•
•
•
—
Command History
Usage Guidelines
Invocations of this command do not become part of the running configuration.
Examples
The following example requests a CRL based on the trustpoint named central:
hostname(config)# crypto ca crl request centralhostname(config)#Related Commands
crypto ca enroll
To start the enrollment process with the CA, use the crypto ca enroll command in global configuration mode. For this command to execute successfully, the trustpoint must have been configured correctly.
crypto ca enroll trustpoint [noconfirm]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
•
—
:
Command History
Usage Guidelines
When the trustpoint is configured for SCEP enrollment, the security appliance displays a CLI prompt immediately and displays status messages to the console asynchronously. When the trustpoint is configured for manual enrollment, the security appliance writes a base-64-encoded PKCS10 certification request to the console and then displays the CLI prompt.
This command generates interactive prompts that vary depending on the configured state of the referenced trustpoint.
Examples
The following example enrolls for an identity certificate with trustpoint tp1 using SCEP enrollment. The security appliance prompts for information not stored in the trustpoint configuration.
hostname(config)# crypto ca enroll tp1%% Start certificate enrollment ..% Create a challenge password. You will need to verbally provide this% password to the CA Administrator in order to revoke your certificate.% For security reasons your password will not be saved in the configuration.% Please make a note of it.Password:Re-enter password:% The fully-qualified domain name in the certificate will be: xyz.example.com% The subject name in the certificate will be: xyz.example.com% Include the router serial number in the subject name? [yes/no]: no% Include an IP address in the subject name? [no]: noRequest certificate from CA [yes/no]: yes% Certificate request sent to Certificate authority.% The certificate request fingerprint will be displayed.% The `show crypto ca certificate' command will also show the fingerprint.hostname(config)#The next command shows manual enrollment of a CA certificate.
hostname(config)# crypto ca enroll tp1
% Start certificate enrollment ..% The fully-qualified domain name in the certificate will be: xyz.example.com% The subject name in the certificate will be: wb-2600-3.example.comif serial number not set in trustpoint, prompt:% Include the router serial number in the subject name? [yes/no]: noIf ip-address not configured in trustpoint:% Include an IP address in the subject name? [no]: yesEnter Interface name or IP Address[]: 1.2.3.4Display Certificate Request to terminal? [yes/no]: yCertificate Request follows:MIIBFTCBwAIBADA6MTgwFAYJKoZIhvcNAQkIEwcxLjIuMy40MCAGCSqGSIb3DQEJAhYTd2ItMjYwMC0zLmNpc2NvLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQDTIdvHa4D5wXZ+40sKQV7Uek1E+CC6hm/LRN3p5ULW1KF6bxhA3Q5CQfh4jDxobn+AY8GoeceulS2Zb+mvgNvjAgMBAAGgITAfBgkqhkiG9w0BCQ4xEjAQMA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQQFAANBACDhnrEGBVtltG7hp8x6Wz/dgY+ouWcAlzy7QpdGhb1du2P81RYn+8pWRA43cikXMTeM4ykEkZhLjDUgv9t+R9c=---End - This line not part of the certificate request---Redisplay enrollment request? [yes/no]: nohostname(config)#Related Commands
crypto ca export
To export the security appliance trustpoint configuration with all associated keys and certificates in PKCS12 format, or to export the device's identity certificate in PEM format, use the crypto ca export command in global configuration mode.
crypto ca export trustpoint identify-certificate
Syntax Description
Syntax DescriptionSyntax Description
Defaults
This command has no default values.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
•
—
:
Command History
7.0
This command was introduced.
8.0(2)
This command was changed to accommodate certificate exporting in PEM format.
Usage Guidelines
Invocations of this command do not become part of the active configuration. The PEM or PKCS12 data is written to the console.
Web browsers use the PKCS12 format to store private keys with accompanying public key certificates protected with a password-based symmetric key. The security device exports the certificates and keys associated with a trust point in base64-encoded PKCS12 format. This feature can be used to move certificates and keys between security devices.
PEM encoding of a certificate is a base64 encoding of an X.509 certificate enclosed by PEM headers. This provides a standard method for text-based transfer of certificates between security devices. PEM encoding can be used to export the proxy-ldc-issuer certificate utilizing SSL/TLS protocol proxy when the security device is acting as a client.
Examples
The following example exports the PEM-formatted certificate for trustpoint 222 as a console display:
hostname (config)# crypto ca export 222 identity-certificateExported 222 follows:-----BEGIN CERTIFICATE-----
MIIGDzCCBXigAwIBAgIKFiUgwwAAAAAFPDANBgkqhkiG9w0BAQUFADCBnTEfMB0G
CSqGSIb3DQEJARYQd2Jyb3duQGNpc2NvLmNvbTELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAk1BMREwDwYDVQQHEwhGcmFua2xpbjEWMBQGA1UEChMNQ2lzY28gU3lzdGVt
czEZMBcGA1UECxMQRnJhbmtsaW4gRGV2VGVzdDEaMBgGA1UEAxMRbXMtcm9vdC1j
YS01LTIwMDQwHhcNMDYxMTAyMjIyNjU3WhcNMjQwNTIwMTMzNDUyWjA2MRQwEgYD
VQQFEwtKTVgwOTQwSzA0TDEeMBwGCSqGSIb3DQEJAhMPQnJpYW4uY2lzY28uY29t
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCvxxIYKcrb7cJpsiFKwwsQUph5
4M5Y3CDVKEVF+98HrD6rhd0n/d6R8VYSfu76aeJC5j9Bbn3xOCx2aY5K2enf3SBW
Y66S3JeZBV88etFmyYJ7rebjUVVQZaFcq79EjoP99IeJ3a89Y7dKvYqq8I3hmYRe
uipm1G6wfKHOrpLZnwIDAQABo4IDujCCA7YwCwYDVR0PBAQDAgWgMBoGA1UdEQQT
MBGCD0JyaWFuLmNpc2NvLmNvbTAdBgNVHQ4EFgQUocM/JeVV3fjZh4wDe0JS74Jm
pvEwgdkGA1UdIwSB0TCBzoAUYZ8t0+V9pox+Y47NtCLk7WxvIQShgaOkgaAwgZ0x
HzAdBgkqhkiG9w0BCQEWEHdicm93bkBjaXNjby5jb20xCzAJBgNVBAYTAlVTMQsw
CQYDVQQIEwJNQTERMA8GA1UEBxMIRnJhbmtsaW4xFjAUBgNVBAoTDUNpc2NvIFN5
c3RlbXMxGTAXBgNVBAsTEEZyYW5rbGluIERldlRlc3QxGjAYBgNVBAMTEW1zLXJv
b3QtY2EtNS0yMDA0ghBaZ5s0Ng4SskMxF2NlIoxgMIIBSAYDVR0fBIIBPzCCATsw
geuggeiggeWGgeJsZGFwOi8vd2luMmstYWQuRlJLLU1TLVBLSS5jaXNjby5jb20v
Q049bXMtcm9vdC1jYS01LTIwMDQsQ049d2luMmstYWQsQ049Q0RQLENOPVB1Ymxp
YyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24s
REM9RlJLLU1TLVBLSSxEQz1jaXNjbyxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0
aW9uTGlzdD9iYXNlP29iamVjdGNsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50MEug
SaBHhkVodHRwOi8vd2luMmstYWQuZnJrLW1zLXBraS5jaXNjby5jb20vQ2VydEVu
cm9sbC9tcy1yb290LWNhLTUtMjAwNC5jcmwwggFCBggrBgEFBQcBAQSCATQwggEw
MIG8BggrBgEFBQcwAoaBr2xkYXA6Ly8vQ049bXMtcm9vdC1jYS01LTIwMDQsQ049
QUlBLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNv
bmZpZ3VyYXRpb24sREM9RlJLLU1TLVBLSSxEQz1jaXNjbyxEQz1jb20/Y0FDZXJ0
aWZpY2F0ZT9iYXNlP29iamVjdGNsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkw
bwYIKwYBBQUHMAKGY2h0dHA6Ly93aW4yay1hZC5mcmstbXMtcGtpLmNpc2NvLmNv
bS9DZXJ0RW5yb2xsL3dpbjJrLWFkLkZSSy1NUy1QS0kuY2lzY28uY29tX21zLXJv
b3QtY2EtNS0yMDA0LmNydDANBgkqhkiG9w0BAQUFAAOBgQBlh7maRutcKNpjPbLk
bdcafJfHQ3k4UoWo0s1A0LXzdF4SsBIKQmpbfqEHtlx4EsfvfHXxUQJ6TOab7axt
hxMbNX3m7giebvtPkreqR9OYWGUjZwFUZ16TWnPA/NP3fbqRSsPgOXkC7+/5oUJd
eAeJOF4RQ6fPpXw9LjO5GXSFQA==
-----END CERTIFICATE-----
hostname (config)#Related Commands
crypto ca import
To install a certificate received from a CA in response to a manual enrollment request or to import the certificate and key pair for a trustpoint using PKCS12 data, use the crypto ca import command in global configuration mode. The security appliance prompts you to paste the text to the terminal in base 64 format.
crypto ca import trustpoint certificate [ nointeractive ]
crypto ca import trustpoint pkcs12 passphrase [ nointeractive ]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Examples
The following example manually imports a certificate for the trustpoint Main:
hostname (config)# crypto ca import Main certificate% The fully-qualified domain name in the certificate will be: securityappliance.example.comEnter the base 64 encoded certificate.End with a blank line or the word "quit" on a line by itself[ certificate data omitted ]quitINFO: Certificate successfully importedhostname (config)#The following example manually imports PKCS12 data to trustpoint central:
hostname (config)# crypto ca import central pkcs12Enter the base 64 encoded pkcs12.End with a blank line or the word "quit" on a line by itself:[ PKCS12 data omitted ]quitINFO: Import PKCS12 operation completed successfullyhostname (config)#Related Commands
crypto ca server
To set up and manage a local CA server on the security appliance, use the crypto ca server command in global configuration mode to enter config-ca-server configuration mode and access the CA configuration commands. To delete the configured local CA server from the security appliance, use the no form of this command.
crypto ca server
no crypto ca server
Defaults
A certificate authority server is not enabled on the security appliance.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
There can only be one local CA on a security appliance.
The crypto ca server command configures the CA server but does not enable it. Use the no version of the shutdown command in config-ca-server mode to enable the local CA.
When you activate the CA server with the no shutdown command, you establish the RSA keypair of the CA and a trustpoint named LOCAL-CA-SERVER to hold the self-signed certificate. This newly-generated self-signed certificate always has `digital signature', `crl signing' and `certificate signing' key usage settings set.
Caution
Examples
The following example uses the command to enter config-ca-server configuration mode and then uses the question-mark to list the local CA server commands available in that mode:
hostname(config)# crypto ca serverhostname(config-ca-server)# ?CA Server configuration commands:cdp-url CRL Distribution Point to be included in the issuedcertificatesdatabase Embedded Certificate Server database locationconfigurationenrollment-retrieval Enrollment-retrieval timeout configurationexit Exit from Certificate Server entry modehelp Help for crypto ca server configuration commandsissuer-name Issuer namekeysize Size of keypair in bits to generate for certificateenrollmentslifetime Lifetime parametersno Negate a command or set its defaultsotp One-Time Password configuration optionsrenewal-reminder Enrollment renewal-reminder time configurationshutdown Shutdown the Embedded Certificate Serversmtp SMTP settings for enrollment E-mail notificationssubject-name-default Subject name default configuration for issuedcertificatesThe following example uses the no form of the crypto ca server command in config-ca-server mode to delete the configured and enabled CA server from the security appliance:
hostname(config-ca-server)#no crypto ca serverCertificate server 'remove server' event has been queued for processing.hostname(config)#Related Commands
crypto ca server crl issue
To force the issuance of a Certificate Revocation List (CRL), use the crypto ca server crl issue command in privileged EXEC mode.
crypto ca server crl issue
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
This seldom-used command is employed to recover a lost CRL. Normally, the CRL is reissued automatically upon expiration by resigning the existing CRL. The crypto ca server crl issue command regenerates the CRL based on the certificate database and should only be used as required to regenerate a CRL based on the certificate database contents.
Examples
The following example forces the issuance of a CRL by the local CA server:
hostname(config-ca-server)# crypto ca server crl issueA new CRL has been issued.
hostname(config-ca-server)#Related Commands
crypto ca server revoke
To mark a certificate issued by the local Certificate Authority (CA) server as revoked in the certificate database and the CRL, use the crypto ca server revoke command in privileged EXEC mode.
crypto ca server revoke cert-serial-no
Syntax Description
cert-serial-no
Specifies the serial number of certificate to be revoked. Enter the serial number in hexadecimal format.
Defaults
No default behavior or value.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
You revoke a specific certificate that has been issued by the local CA on a security appliance by entering the crypto ca server revoke command on that security appliance. Revocation is accomplished when this command marks the certificate as revoked in the certificate database on the CA server and in the CRL. You specify the certificate to be revoked by entering the certificate serial number in hex format.
The CRL is regenerated automatically after the specified certificate is revoked.
Examples
The following example revokes the certificate with the serial number 782ea09f issued by the local CA server:
hostname(config-ca-server)## crypto ca server revoke 782ea09fCertificate with the serial number 0x782ea09f has been revoked. A new CRL has been issued.
hostname(config-ca-server)#Related Commands
crypto ca server unrevoke
To unrevoke a previously revoked certificate issued by the local CA server, use the crypto ca server unrevoke command in privileged EXEC mode.
crypto ca server unrevoke cert-serial-no
Syntax Description
cert-serial-no
Specifies the serial number of certificate to be unrevoked. Enter the serial number in hexadecimal format.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
You unrevoke a previously revoked certificate issued by the local CA on a security appliance by entering the crypto ca server unrevoke command. The validity of the certificate is restored when this command marks the certificate as valid in the certificate database and removes it from the CRL. You specify the certificate to be unrevoked by entering the certificate serial number in hexadecimal format.
The CRL is regenerated automatically after the specified certificate is unrevoked.
Examples
The following example unrevokes the certificate with the serial number 782ea09f issued by the local CA server:
hostname(config-ca-server)# crypto ca server unrevoke 782ea09fCertificate with the serial number 0x782ea09f has been unrevoked. A new CRL has been issued.
hostname(config-ca-server)#Related Commands
crypto ca server user-db add
To insert a new user into the CA server user database, use the crypto ca server user-db add command in privileged EXEC mode.
crypto ca server user-db add user [dn dn] [email e-mail-address]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
The user argument can be a simple username such as jandoe or an e-mail address such as jandoe@example.com. The username must match the username specified by the end user in the enrollment page.
The username is added to the database as a user without privileges. You must use the crypto ca server allow command to grant enrollment privileges.
username, along with the one-time password, is used to enroll the user on the enrollment interface page.
Note
The user argument, email, is used only as an e-mail address to notify the user for enrollment and renewal reminders and does not appear in the issued certificate.
Inclusion of the e-mail address ensures that the user can be contacted with any questions and is notified of the required one-time password for enrollment.
If a optional dn is not specified for a user, the subject name dn is formed using the username and the subject-name-default DN setting as cn=username,subject-name-default.
Examples
The following example adds a user to the user database with a username of jandoe@example.com along with a complete subject-name DN:
hostname(config-ca-server)# crypto ca server user-db add dn "cn=Jan Doe, ou=engineering, o=Example, l=RTP, st=NC, c=US"hostname(config-ca-server)#
The following example grants enrollment privileges to the user named jondoe.
hostname(config-ca-server)# crypto ca server user-db allow jondoehostname(config-ca-server)
Related Commands
crypto ca server user-db allow
To permit a user or a group of users to enroll in the local CA server database, use the crypto ca server user-db allow command in privileged EXEC mode. This command also includes options to generate and display one-time passwords or to e-mail them to the users.
crypto ca server user-db allow {username | all-unenrolled | all-certholders} [display-otp] [email-otp] [replace-otp ]
Syntax Description
Defaults
No default behavior or values.
.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
The replace-otp keyword generates OTPs for all specified users. These new OTPs replace any valid ones previously generated for the specified users.
Note that the OTP is not stored on the security device but is generated and regenerated as required to notify a user or to authenticate a user during enrollment.
Examples
The following example grants enrollment privileges to all users in the database who have not enrolled yet:
hostname(config-ca-server)# crypto ca server user-db allow all-unenrolledhostname(config-ca-server)#The following example grants enrollment privileges to the user named user1:
hostname(config-ca-server)# crypto ca server user-db allow user1hostname(config-ca-server)#Related Commands
crypto ca server user-db email-otp
To e-mail the OTP to a specific user or a subset of users in the local CA server database, use the crypto ca server user-db email-otp command in privileged EXEC mode.
crypto ca server user-db email-otp {username | all-unenrolled | all-certholders}
Syntax Description
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Examples
The following example e-mails the OTP to all unenrolled users in the database:
hostname(config-ca-server)# crypto ca server user-db email-otp all-unenrolledhostname(config-ca-server)#The following example e-mails the OTP to the user named user1:
hostname(config-ca-server)# crypto ca server user-db email-otp user1hostname(config-ca-server)#Related Commands
crypto ca server user-db remove
To remove a user from the local CA server user database, use the crypto ca server user-db remove command in privileged EXEC mode.
crypto ca server user-db remove username
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
This command removes a username from the CA user database so that user cannot enroll. The command also providees the option to revoke previously issued, valid certificates.
Examples
The following example removes a user with a username, user1, from the CA server user database :
hostname(config-ca-server)# crypto ca server user-db remove user1WARNING: No certificates have been automatically revoked. Certificates issued to user user1 should be revoked if necessary.hostname(config-ca-server)#Related Commands
crypto ca server user-db show-otp
To display the OTP for a specific user or a subset of users in the local CA server database, use the crypto ca server user-db show-otp command in privileged EXEC mode.
crypto ca server user-db show-otp {username | all-certholders | all-unenrolled}
Syntax Description
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Examples
The following example displays the OTP for all users who have valid or invalid certificates in the database:
hostname(config-ca-server)# crypto ca server user-db show-otp all-certholdershostname(config-ca-server)#The following example displays the OTP for the user named user1:
hostname(config-ca-server)# crypto ca server user-db show-otp user1hostname(config-ca-server)#Related Commands
crypto ca server user-db write
To configure a directory location to store all the local CA database files, use the crypto ca server user-db write command in privileged EXEC mode.
crypto ca server user-db write
Syntax Description
This command has no keywords or arguments.
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
CA server configuration
•
—
•
—
—
Global configuration
•
—
•
—
—
Privileged EXEC
•
—
•
—
—
Command History
Usage Guidelines
The crypto ca server user-db write command is used to save new user-based configuration data to the storage specifed by the database path configuration. The information is generated when new users are added or allowed with the crypto ca server user-db add and crypto ca server user-db allow commands.
Examples
The following example writes the user information configured in the local CA database to storage:
hostname(config-ca-server)# crypto ca server user-db writehostname(config-ca-server)#Related Commands
crypto ca trustpoint
To enter the trustpoint configuration mode for the specified trustpoint, use the crypto ca trustpoint command in global configuration mode. To remove the specified trustpoint, use the no form of this command.
crypto ca trustpoint trustpoint-name
no crypto ca trustpoint trustpoint-name [noconfirm]
Syntax Description
noconfirm
Suppresses all interactive prompting
trustpoint- name
Identifies the name of the trustpoint to manage. The maximum name length is 128 characters.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
Use the crypto ca trustpoint command to declare a CA. Issuing this command puts you in crypto ca trustpoint configuration mode.
This command manages trustpoint information. A trustpoint represents a CA identity and possibly a device identity, based on a certificate issued by the CA. The commands within the trustpoint sub mode control CA-specific configuration parameters which specify how the security appliance obtains the CA certificate, how the security appliance obtains its certificate from the CA, and the authentication policies for user certificates issued by the CA.
You can specify characteristics for the trustpoint using the following commands listed alphabetically in this command reference guide:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following example enters CA trustpoint mode for managing a trustpoint named central:
hostname(config)# crypto ca trustpoint centralhostname(ca-trustpoint)#Related Commands
crypto dynamic-map match address
To match address of anaccess list for the dynamic crypto map entry, use the crypto dynamic-map match address command in global configuration mode. To disable the address match, use the no form of this command.
crypto dynamic-map dynamic-map-name dynamic-seq-num match address acl_name
no crypto dynamic-map dynamic-map-name dynamic-seq-num match address acl_name
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
See the crypto map match address command for additional information about this command.
Examples
The following example shows the use of the crypto dynamic-map command to match address of an access list named aclist1:
hostname(config)# crypto dynamic-map mymap 10 match address aclist1hostname(config)#Related Commands
crypto dynamic-map set nat-t-disable
To disable NAT-T for connections based on this crypto map entry, use the crypto dynamic-map set nat-t-disable command in global configuration mode. To enable NAT-T for this crypto may entry, use the no form of this command.
crypto dynamic-map dynamic-map-name dynamic-seq-num set nat-t-disable
no crypto dynamic-map dynamic-map-name dynamic-seq-num set nat-t-disable
Syntax Description
dynamic-map-name
Specifies the name of the crypto dynamic map set.
dynamic-seq-num
Specifies the number you assign to the crypto dynamic map entry.
Defaults
The default setting is off.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
Use the isakmp nat-traversal command to globally enable NAT-T. Then you can use the crypto dynamic-map set nat-t-disable command to disable NAT-T for specific crypto map entries.
Examples
The following command disables NAT-T for the crypto dynamic map named mymap:
hostname(config)# crypto dynamic-map mymap 10 set nat-t-disablehostname(config)#Related Commands
crypto dynamic-map set peer
See the crypto map set peer command for additional information about this command.
crypto dynamic-map dynamic-map-name dynamic-seq-num set peer ip_address | hostname
no crypto dynamic-map dynamic-map-name dynamic-seq-num set peer ip_address | hostname
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Examples
The following example shows setting a peer for a dynamic-map named mymap to the IP address10.0.0.1:
hostname(config)# crypto dynamic-map mymap 10 set peer 10.0.0.1hostname(config)#Related Commands
crypto dynamic-map set pfs
To specify the dynamic crypto map sets, use the crypto map dynamic-map set pfs command in global configuration mode. To remove the specified dynamic-map crypto map set, use the no form of this command.
See the crypto map set pfs command for additional information about this command.
crypto dynamic-map dynamic-map-name dynamic-seq-num set pfs [group1 | group2 | group5]
no crypto dynamic-map dynamic-map-name dynamic-seq-num set pfs [group1 | group2 | group5]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
The crypto dynamic-map commands, such as match address, set peer, and set pfs are described with the crypto map commands. If the peer initiates the negotiation and the local configuration specifies PFS, the peer must perform a PFS exchange or the negotiation fails. If the local configuration does not specify a group, the security appliance assumes a default of group2. If the local configuration does not specify PFS, it accepts any offer of PFS from the peer.
When interacting with the Cisco VPN Client, the security appliance does not use the PFS value, but instead uses the value negotiated during Phase 1.
Examples
The following example specifies that PFS should be used whenever a new security association is negotiated for the crypto dynamic-map mymap 10. The group specified is group 2:
hostname(config)# crypto dynamic-map mymap 10 set pfs group2hostname(config)#Related Commands
crypto dynamic-map set reverse route
See the crypto map set reverse-route command for additional information about this command.
crypto dynamic-map dynamic-map-name dynamic-seq-num set reverse route
no crypto dynamic-map dynamic-map-name dynamic-seq-num set reverse route
Syntax Description
dynamic-map-name
Specifies the name of the crypto map set.
dynamic-seq-num
Specifies the number you assign to the crypto map entry.
Defaults
The default value for this command is off.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Examples
The following command enables RRI for the crypto dynamic-map named mymap:
hostname(config)# crypto dynamic-map mymap 10 set reverse routehostname(config)#Related Commands
crypto dynamic-map set transform-set
To specify the transform sets to use in a dynamic crypto map entry, use the crypto dynamic-map set transform-set command in global configuration mode.
crypto dynamic-map dynamic-map-name dynamic-seq-num set transform-set transform-set-name1 [... transform-set-name11]
Specify the names of the transform sets in the no form of this command to remove them from a dynamic crypto map entry.
no crypto dynamic-map dynamic-map-name dynamic-seq-num set transform-set transform-set-name1 [... transform-set-name11]
Using the no form of the command while specifying all or none of the transform sets removes the dynamic crypto map entry.
no crypto dynamic-map dynamic-map-name dynamic-seq-num set transform-set
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0
This command was introduced.
7.2(1)
Changed maximum number of transform sets in a crypto map entry.
Usage Guidelines
A dynamic crypto map is a crypto map without all of the parameters configured. It acts as a policy template where the missing parameters are later dynamically learned, as the result of an IPSec negotiation, to match the peer requirements. The security appliance applies a dynamic crypto map to let a peer negotiate a tunnel if its IP address is not already identified in a static crypto map. This occurs with the following types of peers:
•
Both LAN-to-LAN and remote access peers can use DHCP to obtain a public IP address. The security appliance uses this address only to initiate the tunnel.
•
Peers requesting remote access tunnels typically have private IP addresses assigned by the headend. Generally, LAN-to-LAN tunnels have a predetermined set of private networks that are used to configure static maps and therefore used to establish IPSec SAs.
As an administrator configuring static crypto maps, you might not know the IP addresses that are dynamically assigned (via DHCP or some other method), and you might not know the private IP addresses of other clients, regardless of how they were assigned. VPN clients typically do not have static IP addresses; they require a dynamic crypto map to allow IPSec negotiation to occur. For example, the headend assigns the IP address to a Cisco VPN client during IKE negotiation, which the client then uses to negotiate IPSec SAs.
Dynamic crypto maps can ease IPSec configuration and we recommend them for use in networks where the peers are not always predetermined. Use dynamic crypto maps for Cisco VPN clients (such as mobile users) and routers that obtain dynamically assigned IP addresses.
Tip
Dynamic crypto maps work only to negotiate SAs with remote peers that initiate the connection. The security appliance cannot use dynamic crypto maps to initiate connections to a remote peer. With a dynamic crypto map configured, if the outbound traffic matches a permit entry in an access list and the corresponding SA does not yet exist, the security appliance drops the traffic.
A crypto map set may include a dynamic crypto map. Dynamic crypto map sets should be the lowest priority crypto maps in the crypto map set (that is, they should have the highest sequence numbers) so that the security appliance evaluates other crypto maps first. It examines the dynamic crypto map set only when the other (static) map entries do not match.
Similar to static crypto map sets, a dynamic crypto map set consists of all of the dynamic crypto maps with the same dynamic-map-name. The dynamic-seq-num differentiates the dynamic crypto maps in a set. If you configure a dynamic crypto map, insert a permit ACL to identify the data flow of the IPSec peer for the crypto access list. Otherwise the security appliance accepts any data flow identity the peer proposes.
Caution
You can combine static and dynamic map entries within a single crypto map set.
Examples
The following example creates a dynamic crypto map entry named "dynamic0" consisting of the same ten transform sets. The "crypto ipsec transform-set (create or remove transform set)" section shows ten transform set example commands.
hostname(config)# crypto dynamic-map dynamic0 1 set transform-set 3des-md5 3des-sha 56des-md5 56des-sha 128aes-md5 128aes-sha 192aes-md5 192aes-sha 256aes-md5 256aes-shahostname(config)#Related Commands
crypto ipsec df-bit
To configure DF-bit policy for IPSec packets, use the crypto ipsec df-bit command in global configuration mode.
crypto ipsec df-bit [clear-df | copy-df | set-df] interface
Syntax Description
Defaults
This command is disabled by default. If this command is enabled without a specified setting, the security appliance uses the copy-df setting as default.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
The DF bit with IPSec tunnels feature lets you specify whether the security appliance can clear, set, or copy the Don't Fragment (DF) bit from the encapsulated header. The DF bit within the IP header determines whether a device is allowed to fragment a packet.
Use the crypto ipsec df-bit command in global configuration mode to configure the security appliance to specify the DF bit in an encapsulated header.
When encapsulating tunnel mode IPSec traffic, use the clear-df setting for the DF bit. This setting lets the device send packets larger than the available MTU size. Also this setting is appropriate if you do not know the available MTU size.
Examples
The following example, entered in global configuration mode, sets the IPSec DF policy to clear-df:
hostname(config)# crypto ipsec df-bit clear-df insidehostname(config)#Related Commands
crypto ipsec fragmentation
To configure the fragmentation policy for IPSec packets, use the crypto ipsec fragmentation command in global configuration mode.
crypto ipsec fragmentation {after-encryption | before-encryption} interface
Syntax Description
Defaults
This feature is enabled by default.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
When a packet is near the size of the MTU of the outbound link of the encrypting security appliance, and it is encapsulated with IPSec headers, it is likely to exceed the MTU of the outbound link. This causes packet fragmentation after encryption, which makes the decrypting device reassemble in the process path. Pre-fragmentation for IPSec VPNs increases the performance of the device when decrypting by letting it operate in the high performance CEF path instead of the process path.
Pre-fragmentation for IPSec VPNs lets an encrypting device predetermine the encapsulated packet size from information available in transform sets, which are configured as part of the IPSec SA. If the device predetermines that the packet will exceed the MTU of the output interface, the device fragments the packet before encrypting it. This avoids process level reassembly before decryption and helps improve decryption performance and overall IPsec traffic throughput.
Examples
The following example, entered in global configuration mode, enables pre-fragmentation for IPSec packets globally on the device:
hostname(config)# crypto ipsec fragmentation before-encryption insidehostname(config)#The following example, entered in global configuration mode, disables pre-fragmentation for IPSec packets on the interface:
hostname(config)# crypto ipsec fragmentation after-encryption insidehostname(config)#Related Commands
crypto ipsec security-association lifetime
To configure global lifetime values, use the crypto ipsec security-association lifetime command in global configuration mode. To reset a crypto ipsec entry lifetime value to the default value, use the no form of this command.
crypto ipsec security-association lifetime {seconds seconds | kilobytes kilobytes}
no crypto ipsec security-association lifetime {seconds seconds | kilobytes kilobytes}
Syntax Description
Defaults
The default number of kilobytes is 4,608,000; the default number of seconds is 28,800.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
The crypto ipsec security-association lifetime command changes global lifetime values used when negotiating IPSec security associations.
IPSec security associations use shared secret keys. These keys and their security associations time out together.
Assuming that the particular crypto map entry has no lifetime values configured, when the security appliance requests new security associations during negotiation, it specifies its global lifetime value in the request to the peer; it uses this value as the lifetime of the new security associations. When the security appliance receives a negotiation request from the peer, it uses the smaller of the lifetime value proposed by the peer or the locally configured lifetime value as the lifetime of the new security associations.
There are two lifetimes: a "timed" lifetime and a "traffic-volume" lifetime. The security association expires after the first of these lifetimes is reached.
The security appliance lets the user change crypto map, dynamic map, and ipsec settings on the fly. If this is changed, the security appliance brings down only the connections affected by the change. If the user changes an existing access-list associated with a crypto map, specifically by deleting an entry within the access-list, the result is that only the associated connection is brought down. Connections based on other entries in the access-list are not affected.
To change the global timed lifetime, use the crypto ipsec security-association lifetime seconds command. The timed lifetime causes the security association to time out after the specified number of seconds have passed.
To change the global traffic-volume lifetime, use the crypto ipsec security-association lifetime kilobytes command. The traffic-volume lifetime causes the security association to time out after the specified amount of traffic (in kilobytes) has been protected by the security associations' key.
Shorter lifetimes can make it harder to mount a successful key recovery attack, because the attacker has less data encrypted under the same key to work with. However, shorter lifetimes require more CPU processing time for establishing new security associations.
The security association (and corresponding keys) expires according to whichever occurs sooner, either after the number of seconds has passed or after the amount of traffic in kilobytes has passed.
Examples
The following example specifies a global timed lifetime for security associations:
hostname(config)# crypto ipsec-security association lifetime seconds 240hostname(config)#Related Commands
crypto ipsec security-association replay
To configure the IPSec anti-replay window size, use the crypto ipsec security-association replay command in global configuration mode. To reset the window size to the default value, use the no form of this command.
crypto ipsec security-association replay {window-size n | disable}
no crypto ipsec security-association replay {window-size n | disable}
Syntax Description
n
Sets the window size. Values can be 64, 128, 256, 512, or 1024. The default is 64.
disable
Disables anti-replay checking.
Defaults
The default window size is 64.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
Cisco IPsec authentication provides anti-replay protection against an attacker duplicating encrypted packets by assigning a unique sequence number to each encrypted packet. (Security association anti-replay is a security service in which the receiver can reject old or duplicate packets to protect itself against replay attacks.) The decryptor checks off the sequence numbers that it has seen before. The encryptor assigns sequence numbers in an increasing order. The decryptor remembers the value X of the highest sequence number that it has already seen. N is the window size, and the decryptor also remembers whether it has seen packets having sequence numbers from X-N+1 through X. Any packet with the sequence number X-N is discarded. Currently, N is set at 64, so only 64 packets can be tracked by the decryptor.
At times, however, the 64-packet window size is not sufficient. For example, QoS gives priority to high-priority packets, which could cause some low-priority packets to be discarded even though they could be one of the last 64 packets received by the decryptor; this event can generate warning syslog messages that are false alarms. The crypto ipsec security-association replay command lets you expand the window size, allowing the decryptor to keep track of more than 64 packets.
Increasing the anti-replay window size has no impact on throughput and security. The impact on memory is insignificant because only an extra 128 bytes per incoming IPsec SA is needed to store the sequence number on the decryptor. It is recommended that you use the full 1024 window size to eliminate any future anti-replay problems.
Examples
The following example specifies the anti-replay window size for security associations:
hostname(config)# crypto ipsec security-association replay window-size 1024hostname(config)#Related Commands
crypto ipsec transform-set (create or remove transform set)
To create or remove a transform set, use the crypto ipsec transform-set command in global configuration mode. With crypto ipsec transform-set command, the user can identify the IPSec encryption and hash algorithms to be used by the transform set. Tto remove a transform set, use the no form of this command.
crypto ipsec transform-set transform-set-name encryption [authentication]
no crypto ipsec transform-set transform-set-name encryption [authentication]
Syntax Description
Defaults
The default authentication setting is esp-none (no authentication).
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
Following the configuration of a transform set, you assign it to a crypto map. You can assign up to six transform sets to a crypto map. When the peer attempts to establish an IPSec session, the security appliance evaluates the peer against the access list of each crypto map until it finds a match. The security appliance then evaluates all of the protocols, algorithms, and other settings negotiated by the peer against those in the transform sets assigned to the crypto map until it finds a match. If the security appliance matches the peer's IPSec negotiations to the settings in a transform set, it applies them to the protected traffic as part of its IPSec security association. The security appliance terminates the IPSec session if it fails to match the peer to an access list and find an exact match of the security settings of the peer to those in a transform set assigned to the crypto map.
You can specify either the encryption or the authentication first. You can specify the encryption without specifying the authentication. If you specify the authentication in a transform set you are creating, you must specify the encryption with it. If you specify only the authentication in a transform set you are modifying, the transform set retains its current encryption setting.
If you are using AES encryption, we recommend that you use the isakmp policy priority group 5 command, also in in global configuration mode, to assign Diffie-Hellman group 5 to accommodate the large key sizes provided by AES.
Tip
Examples
The following commands show all possible encryption and authentication options, excluding those that specify no encryption and no authentication:
hostname(config)# crypto ipsec transform-set 3des-md5 esp-3des esp-md5-hmachostname(config)# crypto ipsec transform-set 3des-sha esp-3des esp-sha-hmachostname(config)# crypto ipsec transform-set 56des-md5 esp-des esp-md5-hmachostname(config)# crypto ipsec transform-set 56des-sha esp-des esp-sha-hmachostname(config)# crypto ipsec transform-set 128aes-md5 esp-aes esp-md5-hmachostname(config)# crypto ipsec transform-set 128aes-sha esp-aes esp-sha-hmachostname(config)# crypto ipsec transform-set 192aes-md5 esp-aes-192 esp-md5-hmachostname(config)# crypto ipsec transform-set 192aes-sha esp-aes-192 esp-sha-hmachostname(config)# crypto ipsec transform-set 256aes-md5 esp-aes-256 esp-md5-hmachostname(config)# crypto ipsec transform-set 256aes-sha esp-aes-256 esp-sha-hmachostname(config)#Related Commands
crypto isakmp am-disable
To disable inbound aggressive mode connections, use the crypto isakmp am-disable command in global configuration mode. To enable inbound aggressive mode connections, use the no form of this command.
crypto isakmp am-disable
no crypto isakmp am-disable
Syntax Description
This command has no arguments or keywords.
Defaults
The default value is enabled.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp am-disable command was introduced.
7.2.(1)
The crypto isakmp am-disable command replaces the isakmp am-disable command.
Examples
The following example, entered in global configuration mode, disables inbound aggressive mode connections:
hostname(config)# crypto isakmp am-disableRelated Commands
crypto isakmp disconnect-notify
To enable disconnect notification to peers, use the crypto isakmp disconnect-notify command in global configuration mode. To disable disconnect notification, use the no form of this command.
crypto isakmp disconnect-notify
no crypto isakmp disconnect-notify
Syntax Description
This command has no arguments or keywords.
Defaults
The default value is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp disconnect-notify command was introduced.
7.2.(1)
The crypto isakmp disconnect-notify command replaces the isakmp disconnect-notify command.
Examples
The following example, entered in global configuration mode, enables disconnect notification to peers:
hostname(config)# crypto isakmp disconnect-notifyRelated Commands
crypto isakmp enable
To enable ISAKMP negotiation on the interface on which the IPSec peer communicates with the security appliance, use the crypto isakmp enable command in global configuration mode. To disable ISAKMP on the interface, use the no form of this command.
crypto isakmp enable interface-name
no crypto isakmp enable interface-name
Syntax Description
interface-name
Specifies the name of the interface on which to enable or disable ISAKMP negotiation.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Preexisting
This isakmp enable command was preexisting.
7.2(1)
The crypto isakmp enable command replaces the isakmp enable command.
Examples
The following example, entered in global configuration mode, shows how to disable ISAKMP on the inside interface:
hostname(config)# no crypto isakmp enable insideRelated Commands
crypto isakmp identity
To set the Phase 2 ID to be sent to the peer, use the crypto isakmp identity command in global configuration mode. To return to the default setting, use the no form of this command.
crypto isakmp identity {address | hostname | key-id key-id-string | auto}
no crypto isakmp identity {address | hostname | key-id key-id-string | auto}
Syntax Description
Defaults
The default ISAKMP identity is crypto isakmp identity auto.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Preexisting
The isakmp identity command was preexisting.
7.2(1)
The crypto isakmp identity command replaces the isakmp identity command.
Examples
The following example, entered in global configuration mode, enables ISAKMP negotiation on the interface for communicating with the IPSec peer, depending on connection type:
hostname(config)# crypto isakmp identity autoRelated Commands
crypto isakmp ipsec-over-tcp
To enable IPSec over TCP, use the crypto isakmp ipsec-over-tcp command in global configuration mode. To disable IPSec over TCP, use the no form of this command.
crypto isakmp ipsec-over-tcp [port port1...port10]
no crypto isakmp ipsec-over-tcp [port port1...port10]
Syntax Description
Defaults
The default value is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp ipsec-over-tcp command was introduced.
7.2.(1)
The crypto isakmp ipsec-over-tcp command replaces the isakmp ipsec-over-tcp command.
Examples
This example, entered in global configuration mode, enables IPSec over TCP on port 45:
hostname(config)# crypto isakmp ipsec-over-tcp port 45hostname(config)#Related Commands
crypto isakmp nat-traversal
To enable NAT traversal globally, check that ISAKMP is enabled (you enable it with the crypto isakmp enable command) in global configuration mode. To disable the NAT traversal, use the no form of this command.
crypto isakmp nat-traversal natkeepalive
no crypto isakmp nat-traversal natkeepalive
Syntax Description
Defaults
By default, NAT traversal is enabled.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
NAT including PAT is used in many networks where IPSec is also used, but there are a number of incompatibilities that prevent IPSec packets from successfully traversing NAT devices. NAT traversal enables ESP packets to pass through one or more NAT devices.
The security appliance supports NAT traversal as described by Version 2 and Version 3 of the IETF "UDP Encapsulation of IPsec Packets" draft, available at http://www.ietf.org/html.charters/ipsec-charter.html, and supports NAT traversal for both dynamic and static crypto maps.
This command enables NAT-T globally on the security appliance. To disable in a crypto-map entry, use the crypto map set nat-t-disable command.
Examples
The following example, entered in global configuration mode, enables ISAKMP and then sets NAT traversal with a keepalive interval of 30 seconds:
hostname(config)# crypto isakmp enablehostname(config)# crypto isakmp nat-traversal 30Related Commands
crypto isakmp policy authentication
To specify an authentication method within an IKE policy, use the crypto isakmp policy authentication command in global configuration mode. IKE policies define a set of parameters for IKE negotiation. To remove the ISAKMP authentication method, use the related clear configure command.
crypto isakmp policy priority authentication {crack | pre-share | rsa-sig}
Syntax Description
Defaults
The default ISAKMP policy authentication is pre-share.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp policy authentication command was preexisting.
7.2.(1)
The crypto isakmp policy authentication command replaces the isakmp policy authentication command.
Usage Guidelines
If you specify RSA signatures, you must configure the security appliance and its peer to obtain certificates from a CA server. If you specify preshared keys, you must separately configure these preshared keys within the security appliance and its peer.
Examples
The following example, entered in global configuration mode, shows how to use the crypto isakmp policy authentication command. This example sets the authentication method of RSA Signatures to be used for the IKE policy with the priority number of 40.
hostname(config)# crypto isakmp policy 40 authentication rsa-sigRelated Commands
crypto isakmp policy encryption
To specify the encryption algorithm to use within an IKE policy, use the crypto isakmp policy encryption command in global configuration mode. To reset the encryption algorithm to the default value, which is des, use the no form of this command.
crypto isakmp policy priority encryption {aes | aes-192| aes-256 | des | 3des}
no crypto isakmp policy priority encryption {aes | aes-192| aes-256 | des | 3des}
Syntax Description
Defaults
The default ISAKMP policy encryption is 3des.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp policy encryption command was preexisting.
7.2.(1)
The crypto isakmp policy encryption command replaces the isakmp policy encryption command.
Examples
The following example, entered in global configuration mode, shows use of the crypto isakmp policy encryption command; it sets 128-bit key AES encryption as the algorithm to be used within the IKE policy with the priority number of 25.
hostname(config)# crypto isakmp policy 25 encryption aesThe following example, entered in global configuration mode, sets the 3DES algorithm to be used within the IKE policy with the priority number of 40.
hostname(config)# crypto isakmp policy 40 encryption 3deshostname(config)#Related Commands
crypto isakmp policy group
To specify the Diffie-Hellman group for an IKE policy, use the crypto isakmp policy group command in global configuration mode. IKE policies define a set of parameters to use during IKE negotiation. To reset the Diffie-Hellman group identifier to the default value, use the no form of this command.
crypto isakmp policy priority group {1 | 2 | 5}
no crypto isakmp policy priority group
Syntax Description
Defaults
The default group policy is group 2.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
There are three group options: 768-bit (DH Group 1), 1024-bit (DH Group 2), and 1536-bit (DH Group 5). The 1024-bit and 1536-bit Diffie-Hellman Groups provide stronger security, but require more CPU time to execute.
Note
AES support is available on security appliances licensed for VPN-3DES only. Due to the large key sizes provided by AES, ISAKMP negotiation should use Diffie-Hellman (DH) group 5 instead of group 1 or group 2. To configures group 5, use the crypto isakmp policy priority group 5 command.Examples
The following example, entered in global configuration mode, shows how to use the crypto isakmp policy group command. This example sets group 2, the 1024-bit Diffie Hellman, to use for the IKE policy with the priority number of 40.
hostname(config)# crypto isakmp policy 40 group 2Related Commands
crypto isakmp policy hash
To specify the hash algorithm for an IKE policy, use the crypto isakmp policy hash command in global configuration mode. IKE policies define a set of parameters to be used during IKE negotiation. To reset the hash algorithm to the default value of SHA-1, use the no form of this command.
crypto isakmp policy priority hash {md5 | sha}
no crypto isakmp policy priority hash
Syntax Description
Defaults
The default hash algorithm is SHA-1 (HMAC variant).
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp policy hash command was preexisting.
7.2.(1)
The crypto isakmp policy hash command replaces the isakmp policy hash command.
Usage Guidelines
There are two hash algorithm options: SHA-1 and MD5. MD5 has a smaller digest and is considered to be slightly faster than SHA-1.
Examples
The following example, entered in global configuration mode, shows how to use the crypto isakmp policy hash command. This example specifies the MD5 hash algorithm for the IKE policy, with the priority number of 40.
hostname(config)# crypto isakmp policy 40 hash md5Related Commands
crypto isakmp policy lifetime
To specify the lifetime of an IKE security association before it expires, use the crypto isakmp policy lifetime command in global configuration mode. You can specify an infinite lifetime if the peer does not propose a lifetime. To reset the security association lifetime to the default value of 86,400 seconds (one day), use the no form of this command .
crypto isakmp policy priority lifetime seconds
no crypto isakmp policy priority lifetime
Syntax Description
Defaults
The default value is 86,400 seconds (one day).
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp policy lifetime command was preexisting.
7.2.(1)
The crypto isakmp policy lifetime command replaces the isakmp policy lifetime command.
Usage Guidelines
When IKE begins negotiations, it seeks to agree upon the security parameters for its own session. Then the security association at each peer refers to the agreed-upon parameters. The peers retain the security association until the lifetime expires. Before a security association expires, subsequent IKE negotiations can use it, which can save time when setting up new IPSec security associations. The peers negotiate new security associations before current security associations expire.
With longer lifetimes, the security appliance sets up future IPSec security associations more quickly. Encryption strength is great enough to ensure security without using very fast rekey times, on the order of every few minutes. We recommend that you accept the default.
Note
Examples
The following example, entered in global configuration mode, sets the lifetime of the IKE security association to 50,4000 seconds (14 hours) for the IKE policy with the priority number of 40.
hostname(config)# crypto isakmp policy 40 lifetime 50400The following example, entered in global configuration mode, sets the IKE security association to an infinite lifetime.
hostname(config)# crypto isakmp policy 40 lifetime 0Related Commands
crypto isakmp reload-wait
To enable waiting for all active sessions to voluntarily terminate before rebooting the security appliance, use the crypto isakmp reload-wait command in global configuration mode. To disable waiting for active sessions to terminate and to proceed with a reboot of the security appliance, use the no form of this command.
crypto isakmp reload-wait
no crypto isakmp reload-wait
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
7.0(1)
The isakmp reload-wait command was introduced.
7.2.(1)
The crypto isakmp reload-wait command replaces the isakmp reload-wait command.
Examples
The following example, entered in global configuration mode, tells the security appliance to wait until all active sessions have terminated before rebooting.
hostname(config)# crypto isakmp reload-waitRelated Commands
crypto key generate dsa
To generate DSA key pairs for identity certificates, use the crypto key generate dsa command in global configuration mode.
crypto key generate dsa {label key-pair-label} [modulus size] [noconfirm]
Syntax Description
Defaults
The default modulus size is 1024.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
Use the crypto key generate dsa command to generate DSA key pairs to support SSL, SSH, and IPSec connections. The generated key pairs are identified by labels that you provide as part of the command syntax. If you do not provide a label, the security appliance displays an error message.
Note
Examples
The following example, entered in global configuration mode, generates an DSA key pair with the label mypubkey:
hostname(config)# crypto key generate dsa label mypubkeyINFO: The name for the keys will be: mypubkeyhostname(config)#The following example, entered in global configuration mode, inadvertently attempts to generate a duplicate DSA key pair with the label mypubkey:
hostname(config)# crypto key generate dsa label mypubkeyWARNING: You already have dSA keys defined named mypubkeyDo you really want to replace them? [yes/no] noERROR: Failed to create new DSA keys named mypubkeyhostname(config)#Related Commands
crypto key zeroize
Removes the DSA key pairs.
show crypto key mypubkey
Displays the DSA key pairs.
crypto key generate rsa
To generate RSA key pairs for identity certificates, use the crypto key generate rsa command in global configuration mode.
crypto key generate rsa [usage-keys | general-keys] [label key-pair-label] [modulus size] [noconfirm]
Syntax Description
Defaults
The default key-pair type is general key. The default modulus size is 1024.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
Use the crypto key generate rsa command to generate RSA key pairs to support SSL, SSH, and IPSec connections. The generated key pairs are identified by labels that you can provide as part of the command syntax. Trustpoints that do not reference a key pair can use the default one <Default-RSA-Key>. SSH connections always use this key. This does not affect SSL, since SSL generates its own cert/key dynamically, unless a trustpoint has one configured.
Caution
Examples
The following example, entered in global configuration mode, generates an RSA key pair with the label mypubkey:
hostname(config)# crypto key generate rsa label mypubkeyINFO: The name for the keys will be: mypubkeyKeypair generation processhostname(config)#The following example, entered in global configuration mode, inadvertently attempts to generate a duplicate RSA key pair with the label mypubkey:
hostname(config)# crypto key generate rsa label mypubkeyWARNING: You already have RSA keys defined named mypubkeyDo you really want to replace them? [yes/no] noERROR: Failed to create new RSA keys named mypubkeyhostname(config)#The following example, entered in global configuration mode, generates an RSA key pair with the default label:
hostname(config)# crypto key generate rsaINFO: The name for the keys will be: <Default-RSA-Key>Keypair generation process begin. Please wait...hostname(config)#Related Commands
crypto key zeroize
Removes RSA key pairs.
show crypto key mypubkey
Displays the RSA key pairs.
crypto key zeroize
To remove the key pairs of the indicated type (rsa or dsa), use the crypto key zeroize command in global configuration mode.
crypto key zeroize {rsa | dsa} [label key-pair-label] [default] [noconfirm]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
•
—
:
Command History
Examples
The following example, entered in global configuration mode, removes all RSA key pairs:
hostname(config)# crypto key zeroize rsaWARNING: All RSA keys will be removed.WARNING: All router certs issued using these keys will also be removed.Do you really want to remove these keys? [yes/no] yhostname(config)#Related Commands
crypto key generate dsa
Generates DSA key pairs for identity certificates.
crypto key generate rsa
Generate RSA key pairs for identity certificates.
crypto map interface
To apply a previously defined crypto map set to an interface, use the crypto map interface command in global configuration mode. To remove the crypto map set from the interface, use the no form of this command.
crypto map map-name interface interface-name
no crypto map map-name interface interface-name
Syntax Description
Syntax DescriptionSyntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
Use this command to assign a crypto map set to any active security appliance interface. The security appliance supports IPSec termination on any and all active interfaces. You must assign a crypto map set to an interface before that interface can provide IPSec services.
You can assign only one crypto map set to an interface. If multiple crypto map entries have the same map-name but a different seq-num, they are part of the same set and are all applied to the interface. The security appliance evaluates the crypto map entry with the lowest seq-num first.
Note
Every static crypto map must define three parts: an access list, a transform set, and an IPsec peer. If one of these is missing, the crypto map is incomplete and the security appliance moves on to the next entry. However, if the crypto map matches on the access-list but not on either or both of the other two requirements, this security appliance drops the traffic.
Use the show running-config crypto map command to ensure that every crypto map is complete. To fix an incomplete crypto map, remove the crypto map, add the missing entries, and reapply it.Examples
The following example, entered in global configuration mode, assigns the crypto map set named mymap to the outside interface. When traffic passes through the outside interface, the security appliance evaluates it against all the crypto map entries in the mymap set. When outbound traffic matches an access list in one of the mymap crypto map entries, the security appliance forms a security association using that crypto map entry's configuration.
hostname(config)# crypto map mymap interface outsideThe following example shows the minimum required crypto map configuration:
hostname(config)# crypto map mymap 10 ipsec-isakmphostname(config)# crypto map mymap 10 match address 101hostname(config)# crypto map mymap set transform-set my_t_set1hostname(config)# crypto map mymap set peer 10.0.0.1Related Commands
clear configure crypto map
Clears all configuration for all crypto maps.
show running-config crypto map
Displays the crypto map configuration.
crypto map ipsec-isakmp dynamic
To require a given crypto map entry to refer to a pre-existing dynamic crypto map, use the crypto map ipsec-isakmp dynamic command in global configuration mode. Use the no form of this command to remove the cross reference.
Use the crypto dynamic-map command to create dynamic crypto map entries. After you create a dynamic crypto map set, use the crypto map ipsec-isakmp dynamic command to add the dynamic crypto map set to a static crypto map.
crypto map map-name seq-num ipsec-isakmp dynamic dynamic-map-name
no crypto map map-name seq-num ipsec-isakmp dynamic dynamic-map-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which
Global configuration
•
—
•
—
—
you can enter the command:
Command History
Usage Guidelines
After you define crypto map entries, you can use the crypto map interface command to assign the dynamic crypto map set to interfaces.
Dynamic crypto maps provide two functions: filtering/classifying traffic to protect, and defining the policy to apply to that traffic. The first use affects the flow of traffic on an interface; the second affects the negotiation performed (via IKE) on behalf of that traffic.
IPSec dynamic crypto maps identify the following:
•
•
•
•
A crypto map set is a collection of crypto map entries, each with a different sequence number (seq-num) but the same map name. Therefore, for a given interface, you could have certain traffic forwarded to one peer with specified security applied to that traffic, and other traffic forwarded to the same or a different peer with different IPSec security applied. To accomplish this you create two crypto map entries, each with the same map name, but each with a different sequence number.
The number you assign as the seq-num argument should not be arbitrary. This number ranks multiple crypto map entries within a crypto map set. A crypto map entry with a lower seq-num is evaluated before a map entry with a higher seq-num; that is, the map entry with the lower number has a higher priority.
Note
Examples
The following command, entered in global configuration mode, configures the crypto map mymap to refer to a dynamic crypto map named test.
hostname(config)# crypto map mymap ipsec-isakmp dynamic testhostname(config)#Related Commands
clear configure crypto map
Clears all configuration for all crypto maps.
show running-config crypto map
Displays the crypto map configuration.
crypto map match address
To assign an access list to a crypto map entry, use the crypto map match address command in global configuration mode. To remove the access list from a crypto map entry, use the no form of this command.
crypto map map-name seq-num match address acl_name
no crypto map map-name seq-num match address acl_name
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
This command is required for all static crypto maps. If you are defining a dynamic crypto map (with the crypto dynamic-map command), this command is not required but is strongly recommended.
Use the access-list command to define the access lists.
The security appliance uses the access lists to differentiate the traffic to protect with IPSec crypto from the traffic that does not need protection. It protects outbound packets that match a permit ACE, and ensures that inbound packets that match a permit ACE have protections.
When the security appliance matches a packet to a deny statement, it skips the evaluation of the packet against the remaining ACEs in the crypto map, and resumes evaluation of the packet against the ACEs in the next crypto map in sequence. Cascading ACLs involves the use of deny ACEs to bypass evaluation of the remaining ACEs in an ACL, and the resumption of evaluation of traffic against the ACL assigned to the next crypto map in the crypto map set. Because you can associate each crypto map with different IPSec settings, you can use deny ACEs to exclude special traffic from further evaluation in the corresponding crypto map, and match the special traffic to permit statements in another crypto map to provide or require different security.
Note
In transparent mode, the destination address should be the IP address of the security appliance, the management address. Only tunnels to the security appliance are allowed in transparent mode.Related Commands
clear configure crypto map
Clears all configuration for all crypto maps.
show running-config crypto map
Displays the crypto map configuration.
crypto map set connection-type
To specify the connection type for the Backup Site-to-Site feature for this crypto map entry, use the crypto map set connection-type command in global configuration mode. Use the no form of this command to return to the default setting.
crypto map map-name seq-num set connection-type {answer-only | originate-only | bidirectional}
no crypto map map-name seq-num set connection-type {answer-only | originate-only | bidirectional}
Syntax Description
Defaults
The default setting is bidirectional.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
—
—
Command History
Usage Guidelines
The crypto map set connection-type command specifies the connection types for the Backup Lan-to-Lan feature. It allows multiple backup peers to be specified at one end of the connection.
This feature works only between the following platforms:
•
•
•
To configure a backup Lan-to-Lan connection, we recommend you configure one end of the connection as originate-only using the originate-only keyword, and the end with multiple backup peers as answer-only using the answer-only keyword. On the originate-only end, use the crypto map set peer command to order the priority of the peers. The originate-only security appliance attempts to negotiate with the first peer in the list. If that peer does not respond, the security appliance works its way down the list until either a peer responds or there are no more peers in the list.
When configured in this way, the originate-only peer initially attempts to establish a proprietary tunnel and negotiate with a peer. Thereafter, either peer can establish a normal Lan-to-Lan connection and data from either end can initiate the tunnel connection.
In transparent firewall mode, you can see this command but the connection-type value cannot be set to anything other than answer-only for crypto map entries that are part of a crypto map that has been attached to the interface.
Table 9-1 lists all supported configurations. Other combinations may result in unpredictable routing issues.
Table 9-1 Supported Backup LAN-to-LAN Connection Types
Originate-Only
Answer-Only
Bi-Directional
Answer-Only
Bi-Directional
Bi-Directional
Examples
The following example, entered in global configuration mode, configures the crypto map mymap and sets the connection-type to originate-only.
hostname(config)# crypto map mymap 10 set connection-type originate-onlyhostname(config)#Related Commands
clear configure crypto map
Clears all configuration for all crypto maps.
show running-config crypto map
Displays the crypto map configuration.
crypto map set inheritance
To set the granularity (single or multiple) of security associations generated for this crypto map entry, use the set inheritance command in global configuration mode. To remove the inheritance setting for this crypto map entry, use the no form of this command.
crypto map map-name seq-num set inheritance {data| rule}
no crypto map map-name seq-num set inheritance {data | rule}
Syntax Description
Defaults
Default value is rule.
Command Modes
The following table shows the modes in which
Global configuration
•
—
•
—
—
you can enter the command:
Command History
Usage Guidelines
This command works only when the security appliance is initiating the tunnel, not when responding to a tunnel. Using the data setting may create a large number of IPSec SAs. This consumes memory and results in fewer overall tunnels. You should use the data setting only for extremely security-sensitive applications.
Examples
The following example, entered in global configuration mode, configures the crypto map mymap and sets the inheritance type to data.
hostname(config)# crypto map mymap 10 set inheritance datahostname(config)#Related Commands
clear configure crypto map
Clears all configuration for all crypto maps.
show running-config crypto map
Displays the crypto map configuration.
crypto map set nat-t-disable
To disable NAT-T for connections based on this crypto map entry, use the crypto map set nat-t-disable command in global configuration mode. To enable NAT-T for this crypto may entry, use the no form of this command.
crypto map map-name seq-num set nat-t-disable
no crypto map map-name seq-num set nat-t-disable
Syntax Description
map-name
Specifies the name of the crypto map set.
seq-num
Specifies the number you assign to the crypto map entry.
Defaults
The default setting for this command is not on (therefore NAT-T is enabled by default).
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
Use the isakmp nat-traversal command to globally enable NAT-T. Then you can use the crypto map set nat-t-disable command to disable NAT-T for specific crypto map entries.
Examples
The following command, entered in global configuration mode, disables NAT-T for the crypto map entry named mymap.
hostname(config)# crypto map mymap 10 set nat-t-disablehostname(config)#Related Commands
crypto map set peer
To specify an IPSec peer in a crypto map entry, use the crypto map set peer command in global configuration mode. Use the no form of this command to remove an IPSec peer from a crypto map entry.
crypto map map-name seq-num set peer {ip_address | hostname}{...ip_address | hostname10}
no crypto map map-name seq-num set peer {ip_address | hostname}{...ip_address | hostname10}
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command
Global configuration
•
•
•
—
—
:
Command History
Usage Guidelines
This command is required for all static crypto maps. If you are defining a dynamic crypto map (with the crypto dynamic-map command), this command is not required, and in most cases is not used because, in general, the peer is unknown.
Configuring multiple peers is equivalent to providing a fallback list. For each tunnel, the security appliance attempts to negotiate with the first peer in the list. If that peer does not respond, the security appliance works its way down the list until either a peer responds or there are no more peers in the list. You can set up multiple peers only when using the backup LAN-to-LAN feature (that is, when the crypto map connection type is originate-only). For more information, see the crypto map set connection-type command.
Examples
The following example, entered in global configuration mode, shows a crypto map configuration using IKE to establish the security associations. In this example, you can set up a security association to either the peer at 10.0.0.1 or the peer at 10.0.0.2.
hostname(config)# crypto map mymap 10 ipsec-isakmphostname(config)# crypto map mymap 10 match address 101hostname(config)# crypto map mymap 10 set transform-set my_t_set1hostname(config)# crypto map mymap 10 set peer 10.0.0.1 10.0.0.2Related Commands
