- capture session
- change-password
- class (policy map)
- class-map type control-plane
- clear aaa local user blocked
- clear access-list counters
- clear accounting log
- clear copp statistics
- clear cts role-based counters
- clear cts cache
- clear cts policy
- clear dot1x
- clear eou
- clear hardware rate-limiter
- clear ip access-list counters
- clear ip arp inspection log
- clear ip arp inspection statistics vlan
- clear ip device tracking
- clear ip dhcp relay statistics
- clear ip dhcp snooping binding
- clear ipv6 access-list counters
- clear ipv6 dhcp-ldra statistics
- clear ipv6 dhcp relay statistics
- clear ldap-server statistics
- clear mac access-list counters
- clear port-security
- clear radius-server statistics
- clear ssh hosts
- clear tacacs-server statistics
- clear user
- clear vlan access-list counters
- copp copy profile
- copp profile
- CRLLookup
- crypto ca authenticate
- crypto ca crl request
- crypto ca enroll
- crypto ca export
- crypto ca import
- crypto ca lookup
- crypto ca remote ldap crl-refresh-time
- crypto ca remote ldap server-group
- crypto ca test verify
- crypto ca trustpoint
- crypto certificatemap mapname
- crypto cert ssh-authorize
- cts cache enable
- cts device-id
- cts dot1x
- cts l3 spi (interface)
- cts manual
- cts refresh environment-data
- cts l3 spi (global)
- cts l3 spi (interface)
- cts refresh role-based-policy
- cts rekey
- cts role-based access-list
- cts role-based counters enable
- cts role-based detailed-logging
- cts role-based enforcement
- cts role-based monitor
- cts role-based sgt
- cts role-based sgt-map
- cts sgt
- cts sxp allow default-route-sgt
- cts sxp connection peer
- cts sxp default password
- cts sxp default source-ip
- cts sxp enable
- cts sxp mapping network-map
- cts sxp reconcile-period
- cts sxp retry-period
C Commands
This chapter describes the Cisco NX-OS Security commands that begin with C.
capture session
To enable a capture session for the access control list (ACL), use the capture session command.
Syntax Description
Defaults
Command Modes
ACL capture configuration mode (config-acl-capture)
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to configure an ACL capture session configuration:
Related Commands
|
|
|
|---|---|
change-password
To change your password, use the change-password command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command does not require a license. If secure-mode is enabled, all local user is forced to use this command for changing their own password. Admin users can use username admin_user_name password new_password_for_this_admin command also for changing their own password.
Examples
This example shows how to change your password:
Related Commands
|
|
|
|---|---|
Displays configuration information for control plane policy maps. |
class (policy map)
To specify a control plane class map for a control plane policy map, use the class command. To delete a control plane class map from a control plane policy map, use the no form of this command.
class { class-map-name [ insert-before class-map-name2 ] | class-default }
Syntax Description
(Optional) Inserts the control plane class map ahead of another control plane class map for the control plane policy map. |
|
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Examples
This example shows how to configure a class map for a control plane policy map:
This example shows how to delete a class map from a control plane policy map:
Related Commands
|
|
|
|---|---|
Specifies a control plane policy map and enters policy map configuration mode. |
|
Displays configuration information for control plane policy maps. |
class-map type control-plane
To create or specify a control plane class map and enter class map configuration mode, use the class-map type control-plane command. To delete a control plane class map, use the no form of this command.
class-map type control-plane [ match-all | match-any ] class-map-name
no class-map type control-plane [ match-all | match-any ] class-map-name
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You cannot use match-all, match-any, or class-default as names for control plane class maps.
You can use this command only in the default virtual device context (VDC).
Examples
This example shows how to specify a control plane class map and enter class map configuration mode:
This example shows how to delete a control plane class map:
Related Commands
|
|
|
|---|---|
Displays control plane policy map configuration information. |
clear aaa local user blocked
To clear the blocked local user, use the clear local user blocked command.
clear local user blocked username {all | username}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to clear all the blocked users.
Related Commands
|
|
|
|---|---|
clear access-list counters
To clear the counters for all IPv4, IPv6, and MAC access control lists (ACLs) or a single ACL, use the clear access-list counters command.
clear access-list counters [ access-list-name ]
Syntax Description
(Optional) Name of the ACL whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear counters for all IPv4, IPv6, and MAC ACLs:
This example shows how to clear counters for an IPv4 ACL named acl-ipv4-01:
Related Commands
|
|
|
|---|---|
Displays information about one or all IPv4, IPv6, and MAC ACLs. |
clear accounting log
To clear the accounting log, use the clear accounting log command.
clear accounting log [logflash]
Syntax Description
(Optional) Clears the accounting log stored in the logflash for the current VDC. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
The clear accounting log command operates only in the default virtual device context (VDC 1).
Examples
This example shows how to clear the accounting log:
Related Commands
|
|
|
|---|---|
clear copp statistics
To clear control plane policing (CoPP) statistics, use the clear copp statistics command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Examples
This example shows how to specify a control plane class map and enter class map configuration mode:
Related Commands
|
|
|
|---|---|
clear cts role-based counters
To clear the role-based access control list (RBACL) statistics so that all counters are reset to 0, use the clear cts role-based counters command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the RBACL statistics:
Related Commands
|
|
|
|---|---|
Displays the configuration status of RBACL statistics and lists statistics for all RBACL policies. |
clear cts cache
To clear the Cisco TrustSec authentication and authorization information cache, use the clear cts cache command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to clear the Cisco TrustSec authentication and authorization cache:
Related Commands
|
|
|
|---|---|
clear cts policy
To clear the Cisco TrustSec security group access control list (SGACL) policies, use the clear cts policy command.
clear cts policy { all | peer device-id | sgt sgt-value }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to clear all the Cisco TrustSec SGACL policies on the device:
Related Commands
|
|
|
|---|---|
clear dot1x
To clear 802.1X authenticator instances, use the clear dot1x command.
clear dot1x { all | interface ethernet slot / port }
Syntax Description
Specifies the 802.1X authenticator instances for a specified interface. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must use the feature dot1x command before you configure 802.1X.
Examples
This example shows how to clear all 802.1X authenticator instances:
This example shows how to clear the 802.1X authenticator instances for an interface:
Related Commands
|
|
|
|---|---|
clear eou
To clear Extensible Authentication Protocol over User Datagram Protocol (EAPoUDP) sessions, use the clear eou command.
clear eou { all | authentication { clientless | eap | static } | interface ethernet slot / port | ip-address ipv4-address | mac-address mac-address | posturetoken type }
Syntax Description
Specifies sessions authenticated using clientless posture validation. |
|
Specifies sessions authenticated using statically configured exception lists. |
|
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must enable EAPoUDP by using the feature eou command before using the clear eou command.
Examples
This example shows how to clear all the EAPoUDP sessions:
This example shows how to clear the statically authenticated EAPoUDP sessions:
This example shows how to clear the EAPoUDP sessions for an interface:
This example shows how to clear the EAPoUDP sessions for an IP address:
This example shows how to clear the EAPoUDP sessions for a MAC address:
This example shows how to the EAPoUDP sessions with a posture token type of checkup:
Related Commands
|
|
|
|---|---|
clear hardware rate-limiter
To clear rate-limit statistics, use the clear hardware rate-limiter command.
clear hardware rate-limiter { access-list-log | all | copy | layer-2 { l2pt | mcast-snooping | port-security | storm-control | vpc-low } | layer-3 { control | glean | glean-fast | mtu | multicast { directly-connected | local-groups | rpf-leak } | ttl } | receive }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You can use the command only in the default virtual device context (VDC).
Examples
This example shows how to clear all the rate-limit statistics:
This example shows how to clear the rate-limit statistics for access-list log packets:
This example shows how to clear the rate-limit statistics for Layer 2 storm-control packets:
This example shows how to clear the rate-limit statistics for Layer 3 glean packets:
This example shows how to clear the rate-limit statistics for Layer 3 directly connected multicast packets:
This example shows how to clear the rate-limit statistics for received packets:
Related Commands
|
|
|
|---|---|
clear ip access-list counters
To clear the counters for all IPv4 access control lists (ACLs) or a single IPv4 ACL, use the clear ip access-list counters command.
clear ip access-list counters [ access-list-name ]
Syntax Description
(Optional) Name of the IPv4 ACL whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear counters for all IPv4 ACLs:
This example shows how to clear counters for an IP ACL named acl-ipv4-101:
Related Commands
|
|
|
|---|---|
Displays information about one or all IPv4, IPv6, and MAC ACLs. |
|
clear ip arp inspection log
To clear the Dynamic ARP Inspection (DAI) logging buffer, use the clear ip arp inspection log command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the DAI logging buffer:
Related Commands
|
|
|
|---|---|
clear ip arp inspection statistics vlan
To clear the Dynamic ARP Inspection (DAI) statistics for a specified VLAN, use the clear ip arp inspection statistics vlan command.
clear ip arp inspection statistics vlan vlan-list
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the DAI statistics for VLAN 2:
This example shows how to clear the DAI statistics for VLANs 5 through 12:
This example shows how to clear the DAI statistics for VLAN 2 and VLANs 5 through 12:
Related Commands
|
|
|
|---|---|
clear ip device tracking
To clear IP device tracking information, use the clear ip device tracking command.
clear ip device tracking { all | interface ethernet slot / port | ip-address ipv4-address | mac-address mac-address }
Syntax Description
Clears IP device tracking information for an IPv4 address in the A.B.C.D format. |
|
Clears IP tracking information for a MAC address in the XXXX.XXXX.XXXX format. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear all the IP device tracking information:
This example shows how to clear the IP device tracking information for an interface:
This example shows how to clear the IP device tracking information for an IP address:
This example shows how to clear the IP device tracking information for a MAC address:
Related Commands
|
|
|
|---|---|
clear ip dhcp relay statistics
To clear the DHCP relay statistics, use the clear ip dhcp relay statistics command.
clear ip dhcp relay statistics [interface interface]
Syntax Description
(Optional) Clears the DHCP relay statistics for a specific interface. The supported interface types are ethernet, port-channel, and VLAN. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the global DHCP relay statistics:
Related Commands
|
|
|
|---|---|
clear ip dhcp snooping binding
To clear the DHCP snooping binding database, use the clear ip dhcp snooping binding command.
clear ip dhcp snooping binding
clear ip dhcp snooping binding [ vlan vlan-id mac mac-address ip ip-address interface ethernet slot / port [. subinterface-number ]]
clear ip dhcp snooping binding [ vlan vlan-id mac mac-address ip ip-address interface port-channel channel-number [. subchannel-number ]]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
This command was modified to support clearing a specific binding database entry. The optional vlan keyword and the arguments and keywords that follow it were added. |
|
Usage Guidelines
Examples
This example shows how to clear the DHCP snooping binding database:
This example shows how to clear a specific entry from the DHCP snooping binding database:
Related Commands
|
|
|
|---|---|
Displays IP-MAC address bindings, including the static IP source entries. |
|
Displays DHCP snooping configuration, including the IP Source Guard configuration. |
clear ipv6 access-list counters
To clear the counters for all IPv6 access control lists (ACLs) or a single IPv6 ACL, use the clear ipv6 access-list counters command.
clear ipv6 access-list counters [ access-list-name ]
Syntax Description
(Optional) Name of the IPv6 ACL whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear counters for all IPv6 ACLs:
This example shows how to clear counters for an IPv6 ACL named acl-ipv6-3A:
Related Commands
|
|
|
|---|---|
Displays information about one or all IPv4, IPv6, and MAC ACLs. |
|
clear ipv6 dhcp-ldra statistics
To clear Lightweight DHCPv6 Relay Agent (LDRA) related statistics, use the clear ipv6 dhcp-ldra statistics command.
clear ipv6 dhcp-ldra statistics
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the DHCP feature and LDRA feature.
Examples
This example shows how to clear the LDRA related statistics:
Related Commands
|
|
|
|---|---|
clear ipv6 dhcp relay statistics
To clear the DHCPv6 relay statistics, use the clear ipv6 dhcp relay statistics command.
clear ipv6 dhcp relay statistics [interface interface]
Syntax Description
(Optional) Clears the DHCPv6 relay statistics for a specific interface. The supported interface types are ethernet, port-channel, and VLAN. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the global DHCPv6 relay statistics:
Related Commands
|
|
|
|---|---|
clear ldap-server statistics
To clear the Lightweight Directory Access Protocol (LDAP) server statistics, use the clear ldap-server statistics command.
clear ldap-server statistics { ipv4-address | ipv6-address | host-name }
Syntax Description
Server name. The name is alphanumeric, case sensitive, and has a maximum of 256 characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear the statistics for an LDAP server:
Related Commands
|
|
|
|---|---|
Specifies the IPv4 or IPv6 address or hostname for an LDAP server. |
|
clear mac access-list counters
To clear the counters for all MAC access control lists (ACLs) or a single MAC ACL, use the clear mac access-list counters command.
clear mac access-list counters [ access-list-name ]
Syntax Description
(Optional) Name of the MAC ACL whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear counters for all MAC ACLs:
This example shows how to clear counters for a MAC ACL named acl-mac-0060:
Related Commands
|
|
|
|---|---|
Displays information about one or all IPv4, IPv6, and MAC ACLs. |
|
clear port-security
To clear a single, dynamically learned, secure MAC address or to clear all dynamically learned, secure MAC addresses for a specific interface, use the clear port-security command.
clear port-security dynamic interface ethernet slot / port [ vlan vlan-id ]
clear port-security dynamic interface port-channel channel-number [ vlan vlan-id ]
clear port-security dynamic address address [ vlan vlan-id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Support was added for port-security on port-channel interfaces. |
|
Usage Guidelines
You must enable port security by using the feature port-security command before you can use the clear port-security command.
Examples
This example shows how to remove dynamically learned, secure MAC addresses from the Ethernet 2/1 interface:
This example shows how to remove the dynamically learned, secure MAC address 0019.D2D0.00AE:
Related Commands
|
|
|
|---|---|
clear radius-server statistics
To clear the statistics for a RADIUS server host, use the clear radius-server statistics command.
clear radius-server statistics { ipv4-address | ipv6-address | server-name }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear statistics for a RADIUS server:
Related Commands
|
|
|
|---|---|
clear ssh hosts
To clear the Secure Shell (SSH) host sessions and the known host file for a virtual device context (VDC), use the clear ssh hosts command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear all SSH host sessions and the known host file:
Related Commands
|
|
|
|---|---|
clear tacacs-server statistics
To clear the statistics for a TACACS+ server host, use the clear tacacs-server statistics command.
clear tacacs-server statistics { ipv4-address | ipv6-address | server-name }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear statistics for a TACACS+ server:
Related Commands
|
|
|
|---|---|
clear user
To clear a user session for a virtual device context (VDC), use the clear user command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Use the show users command to display the current user sessions on the device.
Examples
This example shows how to clear all SSH host sessions:
Related Commands
|
|
|
|---|---|
clear vlan access-list counters
To clear the counters for all VLAN access control lists (VACLs) or a single VACL, use the clear vlan access-list counters command.
clear vlan access-list counters [ access-map-name ]
Syntax Description
(Optional) Name of the VLAN access map whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to clear counters for all VACLs:
This example shows how to clear counters for a VACL named vlan-map-101:
Related Commands
|
|
|
|---|---|
Displays information about one or all IPv4, IPv6, and MAC ACLs. |
|
copp copy profile
To create a copy of the Control Plane Policing (CoPP) best practice policy, use the copp clone profile command.
copp copy profile {lenient | moderate | strict} {prefix | suffix} string
Syntax Description
Prefix or suffix string. The suffix or prefix can be any alphanumeric string up to 20 characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
When you use the copp copy profile command, CoPP renames all class maps and policy maps with the specified prefix or suffix.
Examples
This example shows how to create a clone of the CoPP best practice policy:
Related Commands
copp profile
To apply the default Control Plane Policing (CoPP) best practice policy on the Cisco NX-OS device without rerunning the setup utility, use the copp profile command. To remove the default CoPP policy from the Cisco NX-OS device, use the no form of this command.
copp profile { dense | lenient | moderate | strict}
no copp profile { dense | lenient | moderate | strict}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
In Cisco NX-OS releases prior to 5.2(1), you must use the setup utility to change or reapply the default CoPP policy. You can access the setup utility using the setup command.
Beginning with Cisco NX-OS Release 5.2, the CoPP best practice policy is read-only. If you want to modify its configuration, you must clone it using the copp clone profile command. Cloned policies are treated as user configurations.
When you use in-service software downgrade (ISSU) to upgrade to Cisco NX-OS Release 5.2, the policy attached to the control plane is treated as a user-configured policy. Check the CoPP profile using the show copp profile command and make any required changes.
If you use ISSU to downgrade from Cisco NX-OS Release 5.2, CoPP reports the incompatible configuration and instructs you to clone the CoPP profile. In the lower version, all configurations are restored in user-configuration mode.
Examples
This example shows how to apply the default CoPP best practice policy on the Cisco NX-OS device:
This example shows how remove the default CoPP best practice policy from the Cisco NX-OS device:
Related Commands
|
|
|
|---|---|
Displays the CoPP status, including the last configuration operation and its status. |
|
Displays the CoPP configuration in the running configuration. |
CRLLookup
To configure the attribute name, search filter, and base-DN for the certificate revocation list (CRL) search operation in order to send a search query to the Lightweight Directory Access Protocol (LDAP) server, use the CRLLookup command. To disable this configuration, use the no form of this command.
CRLLookup attribute-name attribute-name search-filter filter base-DN base-DN-name
Syntax Description
Defaults
Command Modes
Lightweight Directory Access Protocol (LDAP) search map configuration
Command History
|
|
|
Usage Guidelines
Examples
This example shows how to configure the attribute name, search filter, and base-DN for the CRL search operation in order to send a search query to the LDAP server:
Related Commands
|
|
|
|---|---|
crypto ca authenticate
To associate and authenticate a certificate of the certificate authority (CA) and configure its CA certificate (or certificate chain), use the crypto ca authenticate command. To remove the association and authentication, use the no form of this command.
crypto ca authenticate trustpoint-label
no crypto ca authenticate trustpoint-label
Syntax Description
Name of the trustpoint. The name The name is alphanumeric, case sensitive, and has a maximum length of 64 characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use this command to authenticate the CA to the Cisco NX-OS device by obtaining the self-signed certificate of the CA that contains the public key of the CA. Because the CA signs its own certificate, you should manually authenticate the public key of the CA by contacting the CA administrator when you execute this command. The CA certificate or certificate chain must be available in Privacy Enhanced Mail (PEM) (base-64) encoded format.
Use this command when you initially configure certificate authority support for the device. First create the trustpoint using the crypto ca trustpoint command using the CA certificate fingerprint published by the CA. You must compare the certificate fingerprint displayed during authentication with the one published by the CA and accept the CA certificate only if it matches.
If the CA to authenticate is a subordinate CA (it is not self-signed), then another CA certifies it, which in turn may be certified by yet another CA, and so on, until there is a self-signed CA. In this case, the subordinate CA has a CA certificate chain. You must enter the entire chain during CA authentication. The maximum length that the CA certificate chain supports is ten.
The trustpoint CA is the certificate authority that you configure on the device as the trusted CA. The device accepts any peer certificate if it is signed by a locally trusted CA or its subordinates.
Note The trustpoint configuration that you create with the crypto ca trustpoint command persists across device reboots only if you save it explicitly using the copy running-config startup-config command. The certificates and CRL associated to a trustpoint are automatically persistent when you save the trustpoint configuration in the startup configuration. Otherwise, if you do not saved the trustpoint in the startup configuration, the associated certificates and CRL are not automatically persistent because they cannot exist without the corresponding trustpoint after the device reboots.
To ensure that the configured certificates, CRLs, and key pairs are persistent, always save the running configuration in the startup configuration.
Examples
This example shows how to authenticate a CA certificate called admin-ca:
Related Commands
|
|
|
|---|---|
crypto ca crl request
To configure a new certificate revocation list (CRL) downloaded from the certificate authority (CA), use the crypto ca crl request command.
crypto ca crl request trustpoint-label source-file
Syntax Description
Location of the CRL in the form bootflash : filename. The maximum size is 512. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The crypto ca crl request command allows you to pre-download CRLs for the trustpoints and cache the CRLs in the certificate (cert) store. The CRL file specified should contain the latest CRL in either the Privacy Enhanced Mail (PEM) format or Distinguished Encoding Rules (DER) format.
Note The trustpoint configuration that you create with the crypto ca trustpoint command persists across device reboots only if you save it explicitly using the copy running-config startup-config command. The certificates and CRL associated to a trustpoint are automatically persistent when you save the trustpoint configuration in the startup configuration. Otherwise, if you do not save the trustpoint in the startup configuration, the associated certificates and CRL are not automatically persistent because they cannot exist without the corresponding trustpoint after the device reboots.
To ensure that the configured certificates, CRLs and key pairs are persistent, always save the running configuration in the startup configuration.
Examples
This example shows how to configure a CRL for the trustpoint or replaces the current CRL:
Related Commands
|
|
|
|---|---|
crypto ca enroll
To request a certificate for the device RSA key pair created for this trustpoint CA, use the crypto ca enroll command.
crypto ca enroll trustpoint-label
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A Cisco NX-OS device enrolls with the trustpoint CA to obtain an identity certificate. You can enroll your device with multiple trustpoints and obtain a separate identity certificate from each trustpoint.
When enrolling with a trustpoint, you must specify an RSA key pair to certify. You must generate the key pair and associate it to the trustpoint before generating the enrollment request.
Use the crypto ca enroll command to generate a request to obtain an identity certificate from each of your trustpoints that correspond to authenticated CAs. The certificate signing request (CSR) generated is per the Public-Key Cryptography Standards (PKCS) #10 standard and is displayed in the PEM format. You then cut and paste the certificate and submit it to the corresponding CA through an e-mail or on the CA website. The CA administrator issues the certificate and makes it available to you either through the website or by sending it in an e-mail. You need to import the obtained identity certificate that corresponds to the trustpoint using the crypto ca import trustpoint-label certificate command.
Note
The device does not save the challenge password with the configuration. Record this password so that you can provide it if you need to revoke your certificate.
Examples
This example shows how to generate a certificate request for an authenticated CA:
Related Commands% The 'show crypto ca certificate' command will also show the fingerprint.
|
|
|
|---|---|
Imports the identity certificate obtained from the CA to the trustpoint. |
|
Configures and associates the RSA key pair details to a trustpoint. |
|
crypto ca export
To export the RSA key pair and the associated certificates (identity and CA) of a trustpoint within a Public-Key Cryptography Standards (PKCS) #12 format file to a specified location, use the crypto ca export command.
crypto ca export trustpoint-label pkcs12 destination-file-url pkcs12 - password
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can export the identity certificate with the associated RSA key pair and CA certificate (or certificate chain) to a PKCS #12 format file for backup purposes. You can later import the certificate and RSA key pair to recover from a system crash on your device.
Examples
This example shows how to export a certificate and key pair in the PKCS #12 format:
Related Commands
crypto ca import
To import the identity certificate in the Privacy Enhanced Mail (PEM) format or the identity certificate and associated RSA key pair and CA certificate (or certificate chain) in the Public-Key Cryptography Standards (PKCS) #12 format, use the crypto ca import command.
crypto ca import trustpoint-label { certificate | pkcs12 source-file-url pkcs12-password }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the certificate keyword to import (by cut and paste means) the identity certificate obtained from the CA, corresponding to the enrollment request generated earlier in the trustpoint and submitted to the CA.
Use the pkcs12 source-file-url pkcs12-password keyword and argumen t to import the complete identity information, which includes the identity certificate and associated RSA key pair and CA certificate or certificate chain, into an empty trustpoint. This method allows you to restore the configuration after a system crash.
Note The trustpoint configuration that you create with the crypto ca trustpoint command persists across device reboots only if you save it explicitly using the copy running-config startup-config command. The certificates and CRL associated to a trustpoint are automatically persistent when you save the trustpoint configuration in the startup configuration. Otherwise, if you do not saved the trustpoint in the startup configuration, the associated certificates and CRL are not automatically persistent because they cannot exist without the corresponding trustpoint after the device reboots.
To ensure that the configured certificates, CRLs and key pairs are persistent, always save the running configuration in the startup configuration.
Examples
This example shows how to install an identity certificate obtained from a CA corresponding to an enrollment request made and submitted earlier:
This example shows how to import a certificate and key pair in a Public-Key Cryptography Standards (PKCS) #12 format file:
Related Commands
|
|
|
|---|---|
Exports the RSA key pair and associated certificates of a trustpoint. |
|
crypto ca lookup
To specify the cert-store to be used for certificate authentication, use the crypto ca lookup command.
crypto ca lookup {local | remote | both}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you plan to configure a remote cert-store, you must set up an LDAP server in a remote device and make sure that the CA certificates that are used for authentication are loaded to the Active Directory.
Examples
This example shows how to specify the remote cert-store for certificate authentication:
Related Commands
|
|
|
|---|---|
Configures the refresh time to update the certificate revocation list from the remote cert-store. |
|
Configures the LDAP server group to be used while communicating with LDAP. |
|
crypto ca remote ldap crl-refresh-time
To configure the refresh time to update the certificate revocation list (CRL) from the remote cert-store, use the crypto ca remote ldap crl-refresh-time command.
crypto ca remote ldap crl-refresh-tim e hours
Syntax Description
Refresh time value in hours. The range is from 0 to 744 hours. If you enter 0, the refresh routine runs once. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To use this command, you must configure a remote cert-store and the LDAP server group.
Examples
This example shows how to configure the refresh time to update the CRL from the remote cert-store:
Related Commands
|
|
|
|---|---|
Specifies the cert-store to be used for certificate authentication. |
|
Configures the LDAP server group to be used while communicating with LDAP. |
crypto ca remote ldap server-group
To configure the Lightweight Directory Access Protocol (LDAP) server group to be used while communicating with LDAP, use the crypto ca remote ldap server-group command.
crypto ca remote ldap server-group group-name
Syntax Description
Server group name. You can enter up to 64 alphanumeric characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To use this command, you must configure a remote cert-store.
Examples
This example shows how to configure the LDAP server group to be used while communicating with LDAP:
Related Commands
|
|
|
|---|---|
Specifies the cert-store to be used for certificate authentication. |
|
Configures the refresh time to update the certificate revocation list from the remote cert-store. |
crypto ca test verify
To verify a certificate file, use the crypto ca test verify command.
crypto ca test verify certificate-file
Syntax Description
Certificate filename in the form bootflash : filename. The filename is case sensitive. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to verify the specified certificate in the PEM format by using the trusted CAs configured and by consulting the certificate revocation list (CRL), if needed, as indicated by the revocation checking configuration.
Examples
This example shows how to verify a certificate file:
Note
The verify status code value of 0 indicates that the verification is successful.
Related Commands
|
|
|
|---|---|
crypto ca trustpoint
To create a trustpoint certificate authority (CA) that the device should trust and enter trustpoint configuration mode, use the crypto ca trustpoint command. To remove the trustpoint, use the no form of this command.
crypto ca trustpoint trustpoint-label
no crypto ca trustpoint trustpoint-label
Syntax Description
Name of the trustpoint. The name is alphanumeric, case sensitive, and has a maximum of 64 characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Trustpoints have the following characteristics:
- A trustpoint corresponds to a single CA, which a Cisco NX-OS device trusts for peer certificate verification for any application.
- A CA must be explicitly associated to a trustpoint using the crypto ca authenticate command.
- A Cisco NX-OS device can have many trustpoints and all applications on the device can trust a peer certificate issued by any of the trustpoint CAs.
- A trustpoint is not restricted to a specific application.
- The Cisco NX-OS device can optionally enroll with a trustpoint CA to get an indemnity certificate for itself.
You do not need to designate one or more trustpoints to an application. Any application should be able to use any certificate issued by any trustpoint as long as the certificate satisfies the application requirement.
You do not need more than one identity certificate from a trustpoint or more than one key pair associated to a trustpoint. A CA certifies a given identity (name) only once and does not issue multiple certificates with the same subject name. If you need more than one identity certificate for a CA, define another trustpoint for the same CA, associate another key pair to it, and have it certified if the CA allows multiple certificates with the same subject name.
Note
Before using the no crypto ca trustpoint command to remove the trustpoint, you must first delete the identity certificate and CA certificate (or certificate chain) and then disassociate the RSA key pair from the trustpoint. The device enforces this sequence of actions to prevent the accidental removal of the trustpoint with the certificates.
Examples
This example shows how to declare a trustpoint CA that the device should trust and enter trustpoint configuration mode:
switch# configure terminal
This example shows how to remove the trustpoint CA:
switch# configure terminal
Related Commands
|
|
|
|---|---|
crypto certificatemap mapname
To create a filter map, use the crypto certificatemap mapname command.
crypto certificatemap mapname map-name
Syntax Description
Name of the filter map. You can enter up to 64 alphanumeric characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To use this command, you must configure a cert-store for certificate authentication.
Examples
This example shows how to create a new filter map:
Related Commands
|
|
|
|---|---|
Configures one or more certificate mapping filters within the filter map. |
|
crypto cert ssh-authorize
To configure a certificate mapping filter for the SSH protocol, use the crypto cert ssh-authorize command.
crypto cert ssh-authorize [default | issuer-CAname ] [map map-name1 [ map-name2 ]]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to configure a certificate mapping filter for the SSH protocol:
Related Commands
|
|
|
|---|---|
Configures one or more certificate mapping filters within the filter map. |
|
Displays the mapping filters configured for SSH authentication. |
cts cache enable
To enable Cisco TrustSec authentication and authorization information caching, use the cts cache enable command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable Cisco TrustSec authentication and authorization caching:
This example shows how to disable Cisco TrustSec authentication and authorization caching:
Related Commands
|
|
|
|---|---|
cts device-id
To configure a Cisco TrustSec device identifier, use the cts device-id command.
cts device-id device-id password [ 7 ] password
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
The Cisco TrustSec device identifier name must be unique in your Cisco TrustSec network cloud.
Examples
This example shows how to configure a Cisco TrustSec device identifier:
Related Commands
|
|
|
|---|---|
cts dot1x
To enable Cisco TrustSec authentication on an interface and enter Cisco TrustSec 802.1X configuration mode, use the cts dot1x command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command is not supported for F1 Series modules and F2 Series modules.
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
After using this command, you must enable and disable the interface using the shutdown / no shutdown command sequence for the configuration to take effect.
Examples
This example shows how to enable Cisco TrustSec authentication on an interface:
This example shows how to disable Cisco TrustSec authentication on an interface:
Related Commands
|
|
|
|---|---|
Displays Cisco TrustSec configuration information for interfaces. |
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure Layer 3 Cisco TrustSec global mapping for an SPI and subnet:
This example shows how to remove Layer 3 global mapping for a subnet:
Related Commands
|
|
|
|---|---|
Displays the Layer 3 Cisco TrustSec mapping for SPI values to IPv4 subnets. |
cts l3 spi (interface)
To enable Layer 3 Cisco TrustSec and configure a security parameter index (SPI) on an interface, use the cts l3 spi command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable Layer 3 Cisco TrustSec for an interface:
This example shows how to disable Layer 3 Cisco TrustSec for an interface:
Related Commands
|
|
|
|---|---|
Displays the Layer 3 Cisco TrustSec configuration on the interfaces. |
cts manual
To enter Cisco TrustSec manual configuration for an interface, use the cts manual command. To remove the manual configuration, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
After using this command, you must enable and disable the interface using the shutdown / no shutdown command sequence for the configuration to take effect.
Examples
This example shows how to enter Cisco TrustSec manual configuration mode for an interface:
This example shows how to remove the Cisco TrustSec manual configuration from an interface:
Related Commands
|
|
|
|---|---|
Displays Cisco TrustSec configuration information for interfaces. |
cts refresh environment-data
To refresh the Cisco TrustSec environment data downloaded from the AAA server, use the cts refresh environment-data command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Ensure that you are using the Cisco Identity Services Engine (ISE) Release 1.0 or later releases.
Examples
This example shows how to refresh the Cisco TrustSec environment data downloaded from the AAA server:
Related Commands
|
|
|
|---|---|
cts l3 spi (global)
To enable Layer 3 Cisco TrustSec and map a security parameter index (SPI) and subnet for the device, use the cts l3 spi command. To remove the mapping to an IPv4 subnet, use the no form of this command.
cts l3 spi spi-number A. B. C. D / length
no cts l3 spi A. B. C. D / length
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure Layer 3 Cisco TrustSec global mapping for an SPI and subnet:
This example shows how to remove Layer 3 global mapping for a subnet:
Related Commands
|
|
|
|---|---|
Displays the Layer 3 Cisco TrustSec mapping for SPI values to IPv4 subnets. |
cts l3 spi (interface)
To enable Layer 3 Cisco TrustSec and configure a security parameter index (SPI) on an interface, use the cts l3 spi command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable Layer 3 Cisco TrustSec for an interface:
This example shows how to disable Layer 3 Cisco TrustSec for an interface:
Related Commands
|
|
|
|---|---|
Displays the Layer 3 Cisco TrustSec configuration on the interfaces. |
cts refresh role-based-policy
To refresh the Cisco TrustSec security group access control list (SGACL) policies downloaded from the Cisco Secure ACS, use the cts refresh role-based-policy command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enter Cisco TrustSec manual configuration mode for an interface:
Related Commands
|
|
|
|---|---|
cts rekey
To rekey an interface for Cisco TrustSec policies, use the cts rekey command.
cts rekey ethernet slot / port
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to rekey an interface for Cisco TrustSec:
Related Commands
|
|
|
|---|---|
Displays Cisco TrustSec configuration information for interfaces. |
cts role-based access-list
To create or specify a Cisco TrustSec security group access control list (SGACL) and enter role-based access control list configuration mode, use the cts role-based access-list command. To remove an SGACL, use the no form of this command.
cts role-based access-list list-name
no cts role-based access-list list-name
Syntax Description
Name for the SGACL. The name is alphanumeric and case-sensitive. The maximum length is 32 characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to create a Cisco TrustSec SGACL and enter role-based access list configuration mode :
This example shows how to remove a Cisco TrustSec SGACL:
Related Commands
|
|
|
|---|---|
cts role-based counters enable
To enable role-based access control list (RBACL) statistics, use the cts role-based counters enable command. To disabled RBACL statistics, use the no form of this command.
cts role-based counters enable
no cts role-based counters enable
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
To use this command, you must enable RBACL policy enforcement on the VLAN and VRF.
When you enable RBACL statistics, each policy requires one entry in the. If you do not have enough space remaining in the, an error message appears, and you cannot enable the statistics.
When you modify an RBACL policy, statistics for the previously assigned access control entry (ACE) are displayed, and the newly assigned ACE statistics are initialized to 0.
RBACL statistics are lost only when the Cisco NX-OS device reloads or you deliberately clear the statistics.
Examples
This example shows how to enable RBACL statistics:
This example shows how to disable RBACL statistics:
Related Commands
|
|
|
|---|---|
Clears the RBACL statistics so that all counters are reset to 0. |
|
Displays the configuration status of RBACL statistics and lists statistics for all RBACL policies. |
cts role-based detailed-logging
To enable the displaying of ACE-Action details for the RBACL policies, use the cts role-based detailed-logging command. To revert to the default, use the no form of this command.
cts role-based detailed-logging
no cts role-based detailed-logging
Note
To view the detailed ACLLOGS, you need to enable logging ip access-list detailed after enabling cts role-based detailed logging.
Syntax Description
Defaults
Command Modes
Global configuration
VRF configuration
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure RBACL ace level permission and monitor logging:
This example shows how to disable RBACL ace level permission and monitor logging:
Related Commands
|
|
|
|---|---|
Displays the Cisco TrustSec SGACL policy enforcement configuration. |
cts role-based enforcement
To enable Cisco TrustSec security group access control list (SGACL) enforcement in a VLAN or Virtual Routing and Forwarding instance (VRF), use the cts role-based enforcement command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Global configuration
VLAN configuration
VRF configuration
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable Cisco TrustSec SGACL enforcement in the default VRF:
This example shows how to enable Cisco TrustSec SGACL enforcement in a VLAN:
This example shows how to enable Cisco TrustSec SGACL enforcement in a nondefault VRF:
This example shows how to disable Cisco TrustSec SGACL enforcement:
Related Commands
|
|
|
|---|---|
Displays the Cisco TrustSec SGACL policy enforcement configuration. |
cts role-based monitor
To configure RBACL monitor, use the cts role-based monitor command. To revert to the default, use the no form of this command.
cts role-based monitor {all | enable | permissions from { sgt | unknown} to { dgt | unknown} [ipv4 | ipv6]
no cts role-based monitor {all | enable | permissions from { sgt | unknown} to { dgt | unknown} [ipv4 | ipv6]
Syntax Description
Enables monitoring permissions for all source groups to all destination groups. |
|
Specifies the range for the SGT and DGT that needs to be monitored. |
|
Defaults
Command Modes
Global configuration
VRF configuration
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable monitoring permissions for all source groups to all destination groups:
This example shows how to disable monitoring permissions for all source groups to all destination groups:
Related Commands
|
|
|
|---|---|
Displays the Cisco TrustSec SGACL policy enforcement configuration. |
cts role-based sgt
To manually configure mapping of Cisco TrustSec security group tags (SGTs) to a security group access control list (SGACL), use the cts role-based sgt command. To remove the SGT mapping to an SGACL, use the no form of this command.
cts role-based sgt { sgt-value | any | unknown } dgt { dgt-value | unknown }
access-list list-name
no cts role-based sgt { sgt-value | any | unknown } dgt { dgt-value | unknown }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
You must configure the SGACL before you can configure SGT mapping.
Examples
This example shows how to configure SGT mapping for an SGACL:
This example shows how to remove SGT mapping for an SGACL
Related Commands
|
|
|
|---|---|
cts role-based sgt-map
To manually configure the Cisco TrustSec security group tag (SGT) mapping to IP addresses, use the cts role-based sgt-map command. To remove an SGT, use the no form of this command.
cts role-based sgt-map ipv4-address sgt-value
no cts role-based sgt-map ipv4-address
Syntax Description
Defaults
Command Modes
Global configuration
VLAN configuration
VRF configuration
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure mapping for a Cisco TrustSec SGT:
This example shows how to remove a Cisco TrustSec SGT mapping:
Related Commands
|
|
|
|---|---|
cts sgt
To configure the security group tag (SGT) for Cisco TrustSec, use the cts sgt command.
Syntax Description
Local SGT for the device that is a decimal value or a hexadecimal value with the format 0x hhhh. The decimal range is from 2 to 65519, and the hexadecimal range is from 0x0 to 0xffff. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure the Cisco TrustSec SGT for the device:
Related Commands
|
|
|
|---|---|
cts sxp allow default-route-sgt
To enable the default route for SGT bindings, use the cts sxp allow default-route-sgt command. To disable, use the no form of this command.
cts sxp allow default-route-sgt
no cts sxp allow default-route-sgt
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec SXP feature using the cts sxp enable command.
Examples
This example shows how to expand the network limit:
This example shows how to disable the network limit:
Related Commands
|
|
|
|---|---|
cts sxp connection peer
To configure a Security Group Tag (SGT) Exchange Protocol (SXP) peer connection for Cisco TrustSec, use the cts sxp connection peer command. To remove the SXP connection, use the no form of this command.
cts sxp connection peer peer-ipv4-addr [ source src-ipv4-addr ] password { default | none | required { password | 7 encrypted-password }} mode { speaker | listener } [ vrf vrf-name ]
no cts sxp connection peer peer-ipv4-addr [ vrf vrf-name ]
Syntax Description
Defaults
Configured default SXP password for the device
Configured default SXP source IPv4 address for the device
Default VRF
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
You can use only IPv4 addressing with Cisco TrustSec.
If you do not specify a source IPv4 address, you must configure a default SXP source IPv4 address using the cts sxp default source-ip command.
If you specify default as the password mode, you must configure a default SXP password using the cts sxp default password command.
Examples
This example shows how to configure an SXP peer connection:
This example shows how to remove an SXP peer connection:
Related Commands
|
|
|
|---|---|
Configures the default SXP source IPv4 address for the device. |
|
Displays the Cisco TrustSec SXP peer connection information. |
cts sxp default password
To configure the default Security Group Tag (SGT) Exchange Protocol (SXP) password for the device, use the cts sxp default password command. To remove the default, use the no form of this command.
cts sxp default password { password | 7 encrypted-password }
Syntax Description
Clear text password. The password is alphanumeric and case-sensitive. The maximum length is 32 characters. |
|
Specifies an encrypted password. The maximum length is 32 characters. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure the default SXP password for the device:
This example shows how to remove the default SXP password:
Related Commands
|
|
|
|---|---|
cts sxp default source-ip
To configure the default Security Group Tag (SGT) Exchange Protocol (SXP) source IPv4 address for the device, use the cts sxp default source-ip command. To revert to the default, use the no form of this command.
cts sxp default source-ip ipv4-address
no cts sxp default source-ip ipv4-address
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to configure the default SXP source IP address for the device:
This example shows how to remove the default SXP source IP address:
Related Commands
|
|
|
|---|---|
cts sxp enable
To enable the Security Group Tag (SGT) Exchange Protocol (SXP) peer on a device, use the cts sxp enable command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
Examples
This example shows how to enable SXP:
This example shows how to disable SXP:
Related Commands
|
|
|
|---|---|
cts sxp mapping network-map
To expand the network limit, use the cts sxp mapping network-map command. To revert to the default, use the no form of this command.
cts sxp mapping network-map num_bindings
no cts sxp mapping network-map num_bindings
Syntax Description
Number of bindings to be expanded. The range is from 0 to 65535. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature by using the feature cts command.
Examples
This example shows how to expand the network limit:
This example shows how to disable the network limit:
Related Commands
|
|
|
|---|---|
cts sxp reconcile-period
To configure a Security Group Tag (SGT) Exchange Protocol (SXP) reconcile period timer, use the cts sxp reconcile-period command. To revert to the default, use the no form of this command.
cts sxp reconcile-period seconds
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
After a peer terminates an SXP connection, an internal hold down timer starts. If the peer reconnects before the internal hold down timer expires, the SXP reconcile period timer starts. While the SXP reconcile period timer is active, the Cisco NX-OS software retains the SGT mapping entries learned from the previous connection and removes invalid entries.
Note
Setting the SXP reconcile period to 0 seconds disables the timer and causes all entries from the previous connection to be removed.
Examples
This example shows how to configure the SXP reconcile period:
This example shows how to revert to the default SXP reconcile period value:
Related Commands
|
|
|
|---|---|
cts sxp retry-period
To configure a Security Group Tag (SGT) Exchange Protocol (SXP) retry period timer, use the cts sxp retry-period command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To use this command, you must enable the Cisco TrustSec feature using the feature cts command.
The SXP retry period determines how often the Cisco NX-OS software retries an SXP connection. When an SXP connection is not successfully set up, the Cisco NX-OS software makes a new attempt to set up the connection after the SXP retry period timer expires.
Note
Setting the SXP retry period to 0 seconds disables the timer and retries are not attempted.
Examples
This example shows how to configure the SXP retry period:
This example shows how to revert to the default SXP retry period value:
Related Commands
|
|
|
|---|---|
Displays the Cisco TrustSec SXP peer connection information. |
Feedback