Feedback
Table Of Contents
clear logging ip access-list cache
C Commands
This chapter describes the Cisco NX-OS system management commands that begin with the letter C.
callhome
To enter the CLI Call home configuration mode, use the callhome command.
callhome
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enter the Call home configuration mode:
switch(config)#callhomeswitch(config-callhome)#Related Commands
callhome send
To send a Call home message to all configured destinations, use the callhome send command.
callhome send [configuration | diagnostic]
Syntax Description
configuration
(Optional) Sends a configuration message.
diagnostic
(Optional) Sends a diagnostic message.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to send a Call home configuration message:
switch(config)#callhome send configurationtrying to send configuration callhome messageswitch(config)#Related Commands
callhome
Enters the Call home configuration mode.
callhome test
Sends a test message to all configured Call home destinations.
show callhome
Displays the Call home configuration.
callhome test
To send a test message to all configured Call home destinations, use the callhome test command.
callhome test {inventory}
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to send a Call home test message:
switch(config)#callhome testtrying to send test callhome messageswitch(config)#Related Commands
cdp advertise
To configure the Cisco Discovery Protocol (CDP) version supported by the device, use the cdp advertise command. To remove the CDP configuration, use the no form of this command.
cdp advertise {v1 | v2}
no cdp advertise [v1 | v2]
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
if-ethernet-all configuration (config-if-ethernet-all)
if-gig-ether configuration (config-if-gig-ether)
if-eth-base (config-if-eth-base)
if-mgmt-ether (config-if-mgmt-ether)Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure the CDP version:
switch(config)#cdp advertise v2switch(config)This example shows how to remove the CDP configuration:
switch(config)#no cdp advertise v2switch(config)Related Commands
cdp enable
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable command. To disable CDP, use the no form of this command.
cdp enable
no cdp enable
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enable CDP on an interface:
switch(config)#enable cdpswitch(config)#This example shows how to disable CDP on an interface:
switch(config)#no cdp enableRelated Commands
cdp format device-id
To configure a device ID format for Cisco Discovery Protocol (CDP), use the cdp format device-id command. To remove the device ID format, use the no form of this command.
cdp format device-id {mac-address | serial-number | system-name}
no cdp format device-id {mac-address | serial-number | system-name}
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure a device ID format for CDP:
switch(config)#cdp format device-id mac-addressswitch(config)#This example shows how to remove the device ID format:
switch(config)#no cdp format device-id mac-addressswitch(config)#Related Commands
cdp holdtime
To configure the time that Cisco Discovery Protocol (CDP) holds onto neighbor information before refreshing it, use the cdp holdtime command. To remove the CDP hold time, use the no form of this command.
cdp holdtime seconds
no cdp holdtime seconds
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure a time that CDP holds onto neighbor information:
switch(config)#cdp holdtime 30switch(config)#This example shows how to remove the CDP hold time:
switch(config)#no cdp holdtime 30switch(config)#Related Commands
cdp timer
To configure the Cisco Discovery Protocol (CDP) refresh time interval, use the cdp timer command. To remove the CDP refresh time interval configuration, use the no form of this command.
cdp timer seconds
no cdp timer seconds
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure the CDP refresh time interval:
switch(config)#cdp timer 45switch(config)#This example shows how to remove the CDP refresh time interval:
switch(config)#no cdp timer 45switch(config)#Related Commands
cdp holdtime
Configures the time that CDP holds onto neighbor information before refreshing it.
cfs distribute
To globally enable Cisco Fabric Services (CFS) distribution for the device, use the cfs distribute command. To disable CFS distribution, use the no form of this command. To remove the CFS configuration, use the no form of this command.
cfs distribute
no cfs distribute
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
In order to distribute configuration information, CFS distribution must be enabled for both the device and the application.
CFS is enabled by default for the device. All devices in the fabric must have CFS enabled or they do not receive distributions.
If CFS distribution is disabled for an application, that application does not distribute any configuration and it does not accept a distribution from other devices in the fabric.
Examples
This example shows how to enable CFS distribution:
switch(config)#cfs distributeRelated Commands
cfs eth
To globally configure the device to use Ethernet to distribute changes for all Cisco Fabric Services (CFS)-enabled applications, use the cfs eth command. To remove the CFS configuration, use the no form of this command.
cfs eth {distribute}
no cfs eth distribute
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure the device to use Ethernet to distribute changes for all CFS-enabled applications:
switch(config)#cfs eth distributeswitch(config)#This example shows how to remove the CFS configuration:
switch(config)#no cfs eth distributeThis will prevent CFS from distributing over Ethernet network.Are you sure? (y/n) nswitch(config)#Related Commands
cfs distribute
Globally enables CFS distribution for the device.
show cfs status
Displays the CFS distribution status.
cfs ipv4
To globally configure the device to use IPv4 to distribute changes for all Cisco Fabric Services (CFS)-enabled applications, use the cfs ipv4 command. To remove the CFS configuration, use the no form of this command.
cfs ipv4 [mcast | distribute]
no cfs ipv4 [mcast | distribute]
Syntax Description
Defaults
The default IPv4 multicast address is 239.255.70.83.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
CFS cannot distribute over both IPv4 and IPv6 from the same device.
In order to distribute configuration information, CFS distribution must be enabled for both the device and the application.
CFS is enabled by default for the device. All devices in the fabric must have CFS enabled or they do not receive distributions.
If CFS distribution is disabled for an application, that application does not distribute any configuration and it does not accept a distribution from other devices in the fabric.
CFS over IP must be disabled before you can change the multicast address.
Examples
This example shows how to first disable CFS distribution over IPv4 and then configure the IPv4 multicast address over which configuration changes are distributed:
switch(config)#no cfs ipv4 distributeThis will prevent CFS from distributing over IPv4 network.Are you sure? (y/n) [n]yswitch(config)#cfs ipv4 mcast-address 239.255.1.1Distribution over this IP type will be affectedChange multicast address for CFS-IP ?Are you sure? (y/n) [n]yRelated Commands
cfs region
To create a Cisco Fabric Services (CFS) region that limits the distribution scope of an application, use the cfs region command. To remove the region or the application, use the no form of this command.
cfs region region_id
application_name
no cfs region
no application_name
Syntax Description
Defaults
The default region ID is 0.
Command Modes
Global configuration
CFS region configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
If a feature is moved, that is, assigned to a new region, its scope is restricted to that region; it ignores all other regions for distribution or merging purposes.
You can set up a CFS region to distribute configurations for multiple applications. However, on a given device, only one CFS region at a time can distribute the configuration for a given application.
Once you assign an application to a CFS region, its configuration cannot be distributed within another CFS region.
If you remove an application from a region, and do not assign it into a different region, it is added to the default region, region 0.
If you attempt to add an application to the same region more than once, the following message appears:
Application already present in the same region.In order to distribute configuration information, CFS distribution must be enabled for both the device and the application.
CFS is enabled by default for the device. All devices in the fabric must have CFS enabled or they do not receive distributions.
If CFS distribution is disabled for an application, then that application does not distribute any configuration and it does not accept a distribution from other devices in the fabric.
This command does not require a license.
Examples
This example shows how to create region 4 and add the NTP application to it. When you create a region, the CLI places you into region configuration mode for that region, where you can then add an application.
switch(config)# cfs region 4
switch(config-cfs-region)# callhome
switch(config-cfs-region)# show cfs region brief
---------------------------------------
Region Application Enabled
---------------------------------------
4 ntp no
4 callhome no
6 igmp yes
6 radius no
switch(config-cfs-region)#
Related Commandsswitch(config-cfs-region)#
check logflash
To check the compactFlash, use the check logflash command.
check logflash [bad-blocks]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to check compactFlash:
switch# check logflash
checkpoint
To configure the rollback checkpoint, use the checkpoint command. To delete the checkpoint, use the no form of this command.
checkpoint {name | description description | file name}
no checkpoint name
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
If you use the checkpoint command without a name, Cisco NX-OS creates the file with the name auto-x, where x is a decimal number that increases each time you create an unnamed checkpoint file.
This command does not require a license.
Examples
This example shows how to configure the rollback checkpoint:
switch# checkpoint stable
switch#
This example shows how to delete the checkpoint file:
switch# no checkpoint stable
switch#
Related Commands
clear callhome session
To clear a Call home Cisco Fabric Services (CFS) distribution session, use the clear callhome session command.
clear callhome session
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear a Call home CFS distribution session:
switch(config)#clear callhome sessionRelated Commands
clear cdp
To clear Cisco Discovery Protocol (CDP) statistics on an interface, use the clear cdp command.
clear cdp {counters [interface interface] | table [interface interface]}
Syntax Description
counters
Clears CDP counters on all interfaces.
interface interface
(Optional) Clears CDP counters on an interface.
table
Clears CDP cache on all interfaces.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear CDP statistics on an interface:
switch(config)#clear cdp countersswitch(config)#Related Commands
clear checkpoint database
To delete all checkpoint files in the database, use the clear checkpoint database command.
clear checkpoint database
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the checkpoint database:
switch# clear checkpoint databaseProcessing the Request... Please Wait..... Doneswitch#Related Commands
clear cores
To clear the core files, use the clear cores command.
clear cores [archive]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
Use the show system cores command to display information about the core files.
This command does not require a license.
Examples
This example shows how to clear the core file:
switch# clear coresThis example shows how to clear the core on the logflash file system:
switch# clear cores archiveRelated Commands
show system cores
Displays the core filename.
system cores
Configures the core filename.
clear flow exporter
To clear the statistics for a Flexible NetFlow flow exporter, use the clear flow exporter command.
clear flow exporter {name exporter-name | exporter-name}
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
You must have already enabled traffic monitoring with Flexible NetFlow using an exporter before you can use the clear flow exporter command.
This command does not require a license.
Examples
This example clears the statistics for the flow exporter named NFC-DC-PHOENIX:
switch# clear flow exporter name NFC-DC-PHOENIXswitch#Related Commands
clear flow exporter
Clears the statistics for exporters.
flow exporter
Creates a flow exporter.
show flow exporter
Displays flow exporter status and statistics.
clear flow monitor
To clear a Flexible NetFlow flow monitor, flow monitor cache, or flow monitor statistics and to force the export of the data in the flow monitor cache, use the clear flow monitor command.
clear flow monitor {name monitor-name | monitor-name} [cache [force-export] | statistics]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
You must enable Flexible NetFlow monitor before you can use the clear flow monitor command.
Use the clear flow monitor monitor-name cache command to remove all entries from the flow monitor cache. These entries will not be exported and the data gathered in the cache is lost.
The statistics for the cleared cache entries are maintained.
Use the clear flow monitor monitor-name force-export command to remove all entries from the flow monitor cache and exports them to all flow exporters that are assigned to the flow monitor. This process can result in an short term increase in the CPU utilization.
CautionBe careful when you use the clear flow monitor monitor-name force-export command becasue using this command might cause a short-term increase in the CPU utilization.
Use the clear flow monitor monitor-name statistics command to clear the statistics and cache entries for this flow monitor.
The Current entries statistic is not cleared because this statistic indicates how many entries are in the cache.
This command does not require a license.
Examples
This example shows how to clear the statistics and cache entries for the flow monitor named NFC-DC-PHOENIX:
switch# clear flow monitor name NFC-DC-PHOENIXswitch#This example shows how to clear the statistics and cache entries for the flow monitor named NFC-DC-PHOENIX and forces an export:
switch# clear flow monitor NFC-DC-PHOENIX force-exportswitch#This example shows how to clear the cache for the flow monitor named NFC-DC-PHOENIX and forces an export:
switch# clear flow monitor NFC-DC-PHOENIX cache force-exportswitch#This example shows how to clear the statistics for the flow monitor named NFC-DC-PHOENIX:
switch# clear flow monitor NFC-DC-PHOENIX statisticsswitch#Related Commands
clear flow monitor
Clears the flow monitor.
flow monitor
Creates a flow monitor.
show flow sw-monitor
Displays flow monitor status and statistics.
clear hardware flow ip
To clear the NetFlow hardware IP flow, use the clear hardware flow ip command.
clear hardware flow ip [{{vdc vdc_id} | {monitor name} | {profile profile-id} | {vlan vlan-id} | {interface if-type if-number}}] [instance inst] [force-export] [module num]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the NetFlow hardware IP flow:
switch(config)# clear hardware flow ip module 8 ethernet 2/1switch(config)#Related Commands
show hardware flow {ip | ipv6}
Displays information about NetFlow hardware IP / IPV6 flows.
clear logging ip access-list cache
To clear all the entries from the Optimized ACL Logging (OAL) cache and send them to the syslog, use the clear logging ip access-list cache command.
clear logging ip access-list cache
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear all the entries from the OAL cache and send them to the syslog:
switch# clear logging ip access-list cacheswitch#Related Commands
clear logging logfile
To clear messages from the logging file, use the clear logging logfile command.
clear logging logfile
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear messages from the logging file:
switch# clear logging logfileswitch#Related Commands
clear logging nvram
To clear the NVRAM logs, use the clear logging nvram command.
clear logging nvram
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the NVRAM logs:
switch# clear logging nvramswitch#Related Commands
clear logging onboard
To clear the onboard failure logging (OBFL) entries in the persistent log, use the clear logging onboard command.
clear logging onboard [counter-stats] [environmental-history] [error-stats] [exception-log] [interrupt-stats] [module num] [obfl-log] [stack-trace]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the OBFL environmental history entries:
switch# clear logging onboard environmental-historyswitch#This example shows how to clear the OBFL error statistics:
switch# clear logging onboard error-statsswitch#This example shows how to clear the OBFL exception-log entries:
switch# clear logging onboard exception-logswitch#This example shows how to clear the OBFL interrupt statistics:
switch# clear logging onboard interrupt-statsswitch#This example shows how to clear the OBFL information for a specific module:
switch# clear logging onboard module 2switch#This example shows how to clear the OBFL (boot-uptime/device-version/obfl-history) entries:
switch# clear logging onboard obfl-logswitch#This example shows how to clear the OBFL stack trace entries:
switch# clear logging onboard stack-traceswitch#Related Commands
hw-module logging onboard
Enables OBFL based on the error type.
show logging onboard
Displays onboard failure logs.
clear logging session
To clear the current logging session, use the clear logging session command.
clear logging session
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the current logging session:
switch# clear logging sessionswitch#Related Commands
clear ntp session
To clear the Network Time Protocol (NTP) session, use the clear ntp session command.
clear ntp session
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the NTP session:
switch(config)#clear ntp sessionclear ntp statistics
To clear the Network Time Protocol (NTP) statistics, use the clear ntp statistics command.
clear ntp statistics {all-peers | io | local | memory}
Syntax Description
all-peers
Clears statistics for all NTP peers.
io
Clears IO statistics.
local
Clears local statistics.
memory
Clears memory statistics.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear statistics for all NTP peers:
switch(config)#clear ntp statistics all-peersRelated Commands
clear nvram
To clear the NVRAM, use the clear nvram command.
clear nvram
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear NVRAM:
switch(config)#clear nvramclear platform flow ip
To clear NetFlow hardware IPv4 entries, use the clear platform flow ip command.
clear platform flow ip [type] [force-export] [module mod-num]
Syntax Description
Defaults
If you do not specify the type, all types are cleared.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to specify a forced export of the cleared data to a collector:
switch# clear platform flow ip forced-exportswitch#This example shows how to clear the NetFlow statistics for a module:
switch# clear platform flow ip module 2switch#Related Commands
clear processes log archive
To delete a log file on a log flash, use the clear processes log archive command.
clear processes log archive [file file-number]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to delete a log file on a log flash:
switch(config)# clear processes log archiveswitch(config)#Related Commands
clear rmon
To delete the Remote Network Monitoring (RMON) tables from a simple network management protocol (SNMP) notification, use the clear rmon command.
clear rmon {alarms | events | hcalarms | all-alarms}
Syntax Description
alarms
Clears all 32-bit alarms.
events
Clears the RMON log and also clears the RMON event table.
hcalarms
Clears all 64-bit RMON alarms.
all-alarms
Clears all 32-bit and 64-bit RMON alarms.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to delete RMON tables:
switch(config)#clear rmon alarmsswitch(config)#Related Commands
clear session state name
To clear the state information for a session, use the clear session state name command.
clear session state name name
Syntax Description
name
Name of the session. The name can be any case-sensitive, alphanumeric string up to 63 characters.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the internal state for a configuration session:
switch# clear session state name myACLsRelated Commands
show configuration session
Displays information about the configuration sessions.
clear snmp counters
To delete Simple Network Management Protocol (SNMP) counters, use the clear snmp counters command.
clear snmp counters
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to delete SNMP counters:
switch(config)#clear snmp countersswitch(config)#Related Commands
clear snmp hostconfig
To delete the Simple Network Management Protocol (SNMP) host configuration, use the clear snmp hostconfig command.
clear snmp hostconfig
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to delete the SNMP host configuration:
switch(config)#clear snmp hostconfigswitch(config)#Related Commands
show snmp sessions
Displays SNMP sessions.
clear snmp counters
Deletes SNMP counters.
clear system reset-reason
To clear the device reset-reason history, use the clear system reset-reason command.
clear system reset-reason
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the device reset-reason history:
switch# clear system reset-reasonRelated Commands
collect counter
To configure the number of bytes or packets in a flow as a nonkey field and collect the counter values (number of bytes or packets seen) for a Flexible NetFlow flow record, use the collect counter command. To disable the use of the number of bytes or packets in a flow (counters) as a nonkey field for a Flexible NetFlow flow record, use the no form of this command.
collect counter {bytes [long] | packets [long]}
no collect counter {bytes [long] | packets [long]}
Syntax Description
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
Use the collect counter packets command to configure a 32-bit counter that is incremented for each packet seen in the flow. For extremely long flow it is possible for this counter to wrap when it reaches the limit of 4 billion or more packets. When the flow monitor detects a scenario that could cause a wrap, the flow monitor with a normal cache type exports the flow and starts a new flow.
Use the collect counter packets long command to configure a 64-bit counter that is incremented for each packet seen in the flow. It is unlikely that a 64-bit counter will ever wrap.
This command does not require a license.
Examples
This example shows how to enable collecting the total number of bytes from the flows as a nonkey field:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect counter bytesThis example shows how to enable collecting the total number of bytes from the flows as a nonkey field using a 64 bit counter:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect counter bytes longThis example shows how to enable collecting the total number of packets from the flows as a nonkey field:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect counter packetsThis example shows how to enable collecting the total number of packets from the flows as a nonkey field using a 64-bit counter:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect counter packets longRelated Commands
collect flow
To configure the flow direction or the flow sampler ID number as a nonkey field and collect their values for a Flexible NetFlow flow record, use the collect flow command. To disable the use of the flow direction or the flow sampler ID number as a nonkey field for a Flexible NetFlow flow record, use the no form of this command.
collect flow {direction | sampler}
no collect flow {direction | sampler}
Syntax Description
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
Use the collect flow direction command to indicate the direction of the flow. Use this command when you configure a single flow monitor for input and output flows and to find and eliminate flows that are being monitored twice: once on input and once on output.
Use the collect flow sampler command to collect the ID of the flow sampler that is used to monitor the flow. Use this command when more than one flow sampler is being used with different sampling rates. The option sampler-table command exports option records with mappings of the flow sampler ID to the sampling rate so that the collector can calculate the scaled counters for each flow.
This command does not require a license.
Examples
This example shows how to configure the direction of the flow nonkey that was monitored as a nonkey field:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect flow directionThis example shows how to configure an ID of the flow sampler that is assigned to the flow as a nonkey field and collects the ID of the flow sampler:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect flow samplerRelated Commands
collect interface
To configure the input or output interface as a nonkey field and collect the values for a Flexible NetFlow flow record, use the collect interface command. To disable the use of the input or output interface as a nonkey field for a Flexible NetFlow flow record, use the no form of this command.
collect interface {input | output}
no collect interface {input | output}
Syntax Description
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
This command does not require a license.
Examples
This example shows how to configure the input interface as a nonkey field and collect the input interface value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect interface inputThis example shows how to configure the input interface as a nonkey field and collect the output interface value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect interface outputRelated Commands
collect routing
To configure a routing attribute as a nonkey field and collect the value of the field for a Flexible NetFlow flow record, use the collect routing command. To disable the use of a routing attribute as a nonkey field for a Flexible NetFlow flow record, use the no form of this command.
collect routing {{destination | source} as [peer] | traffic-index | forwarding-status | next-hop address ipv4 [bgp]}
no collect routing {{destination | source} as [peer] | traffic-index | forwarding-status | next-hop address ipv4 [bgp]}
Syntax Description
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to captures the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
Use the collect routing source as [peer] command to collect the 16-bit AS number based on a lookup of the router's routing table using the source IP address. The optional peer keyword provides the expected next network, not the originating network.
Note
not be accurate for asymmetrical routes.
Use the collect routing destination as [peer] command to collect the 16-bit AS number based on a lookup of the router's routing table using the destination IP address. The optional peer keyword provides the expected next network, not the destination network.
Use the collect routing source traffic-index command to collect the traffic index field based on the source AS for this flow. The traffic-index field is a value that is propagated through BGP.
Use the collect routing forwarding-status command to collect a field to indicate if the packets were successfully forwarded. The field is in two parts and may be up to 4 bytes in length. At this time, only the status field is used:
+-+-+-+-+-+-+-+-+| S | Reason || t | codes || a | or || t | flags || u | || s | |+-+-+-+-+-+-+-+-+0 1 2 3 4 5 6 7Status:00b=Unknown, 01b = Forwarded, 10b = Dropped, 11b = ConsumedThis command does not require a license.
Examples
This example shows how to configure the 16-bit AS number based on a lookup of the router's routing table using the source IP address as a nonkey field and collects the 16-bit AS number value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect routing source asThis example shows how to configure the 16-bit AS number based on a lookup of the router's routing table using the destination IP address as a nonkey field and collects the 16-bit AS number value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect routing destination asThis example shows how to configure the value in the traffic index field based on the source AS for a flow as a nonkey field and collects the value in the traffic index field value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect routing source traffic-indexThis example shows how to configure the forwarding status as a nonkey field and collects the forwarding status value:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect routing forwarding-statusRelated Commands
collect timestamp sys-uptime
To configure the TIMESTAMP SYS-UPTIME field as a nonkey field and collect the values in them for a Flexible NetFlow flow record, use the collect timestamp sys-uptime command. To disable the use of the TIMESTAMP SYS-UPTIME field as a nonkey for a Flexible NetFlow flow record, use the no form of this command.
collect timestamp sys-uptime {first | last}
no collect timestamp sys-uptime {first | last}
Syntax Description
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
This command does not require a license.
Examples
This example shows how to configure timestamps based on the sys-uptime for the time that the first packet was seen from the flows as a nonkey field and collects the sys-uptime for the time that the first packet was seen from the flows:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect timestamp sys-uptime firstThis example shows how to configure timestamps based on the sys-uptime for the time that the most recent packet was seen from the flows as a nonkey field and collects the sys-uptime for the time that the most recent packet was seen from the flows:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect timestamp sys-uptime lastRelated Commands
collect transport tcp flags
To configure a Transmission Control Protocol (TCP) field as a nonkey field and collect the value in it for a Flexible NetFlow flow record, use the collect transport tcp flags command. To disable the use of a TCP field as a nonkey field for a Flexible NetFlow flow record, use the no form of this command.
collect transport tcp flags
no collect transport tcp flags
Syntax Description
This command has no arguments or keywords
Defaults
This command is not enabled by default.
Command Modes
Flow record configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Flexible NetFlow commands that start with collect are used to configure nonkey fields for the flow monitor record and to enable capturing the values in the fields for the flow created with the record. The values in nonkey fields are added to flows to provide additional information about the traffic in the flows. A change in the value of a nonkey field does not create a new flow. In most cases, the values for nonkey fields are taken from only the first packet in the flow.
This command does not require a license.
Examples
This example shows how to configure the TCP flags as a nonkey field:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)# collect transport tcp flagsRelated Commands
commit (Call home)
To distribute a Cisco Fabric Services (CFS) configuration, use the commit command.
commit
Syntax Description
This command has no arguments or keywords
Defaults
None
Command Modes
Call home configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The commit command results in the distribution of the CFS configuration to the running configuration of all CFS-enabled devices in the fabric.
You can only use the commit command on the specific device where the fabric lock was acquired.
Configuration changes that have not been committed yet (still saved as a working copy) are not in the running configuration and do not display in the output of show commands.
An empty commit is allowed to distribute a current configuration if you want to make sure that all devices are synchronized.
This command does not require a license.
Examples
This example shows how to commit a CFS configuration and verify that the commit was successful:
switch(config-callhome)# commitswitch(config-callhome)# show callhome session statusLast Action Time Stamp : Tue Dec 23 11:15:02 2008Last Action : CommitLast Action Result : SuccessLast Action Failure Reason : noneRelated Commands
commit (Session Manager)
To validate and apply the commands in the Session Manager configuration session, use the commit command.
commit [verbose]
Syntax Description
Defaults
None
Command Modes
Session configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The commit command results in a validation of the entire Session Manager configuration, and, if valid, the configuration is applied to the device,
This command does not require a license.
Examples
This example shows how to commit a Session Manager configuration:
switch# config session ACL_tcp_inConfig Session started, Session ID is 1Enter configuration commands, one per line. End with CNTL/Z.switch(config-s)# verifyVerification Successfulswitch(config-s)# commitCommit Successfulswitch#Related Commands
configure session
To create or modify an access contol list (ACL) configuration session with the Session Manager feature, use the configure session command.
configure session name
Syntax Description
name
Name of the session. The name can be any case-sensitive, alphanumeric string up to 63 characters.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Session Manager supports only the ACL feature.
Examples
This example shows how to create an ACL configuration session:
switch# configure session myACLsswitch(config-s)#Related Commands
show configuration session
Displays information about the Session Manager configuration sessions.
contract-id
To specify a service agreement contract ID in Call home, use the contract-id command. To remove it, use the no form of this command.
contract-id contract_id_number
no contract-id
Syntax Description
contract_id_
numberContract number for this device from the service agreement. The contract number can be up to 255 alphanumeric characters in free format.
Defaults
None
Command Modes
Call home configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure a service agreement contract ID in Call home:
switch(config-callhome)# contract-id Contract5678Related Commands
counter
To configure a Simple Network Management Protocol (SNMP) port-monitor counter, use the counter command. To remove the port-monitor counter configuration, use the no form of this command.
counter {invalid-crc [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | invalid-words [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | link-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | protocol-error [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | rx-performance [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | signal-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | sync-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | tx-performance [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}]}
no counter {invalid-crc [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | invalid-words [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | link-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | protocol-error [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | rx-performance [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-thresholdevent event-id]}] | signal-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | sync-loss [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}] | tx-performance [poll-interval poll-interval {absolute rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id] | delta rising-threshold rising-threshold event event-id [falling-threshold falling-threshold event event-id]}]}
Syntax Description
Defaults
None
Command Modes
Port-monitor configuration (config-port-monitor)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure an SNMP counter:
switch(config) port-monitor name PM1switch(config-port-monitor)# counter invalid-crc poll-interval 30 absolute rising-threshold 10000000 event 100switch(config-port-monitor)#This example shows how to remove an SNMP counter configuration:
switch(config)#no counter invalid-crc poll-interval 30 absolute rising-threshold 10000000 event 100switch(config-port-monitor)#Related Commands
customer-id
To specify a service agreement customer ID in Call home, use the customer-id command. To remove it, use the no form of this command.
customer-id contract_id_number
no customer-id
Syntax Description
contract_id_
numberCustomer number for this device from the service agreement. The customer number can be up to 255 alphanumeric characters in free format.
Defaults
None
Command Modes
Call home configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure a service agreement customer ID in Call home:
switch(config-callhome)# customer-id Customer123456Related Commands
