The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco Nexus 1000V commands that begin with the letter, C.
To specify a cache size for a Netflow flow monitor, use the cache size command. To remove the cache size for a flow monitor, use the no form of this command.
cache size value
no cache size value
value |
Size in number of entries. The range is 256 to 16384 entries. |
4096 entries
Netflow monitor configuration (config-flow-monitor)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Use the cache-size command to limit the impact of the Netflow flow monitor cache on memory and performance.
This example shows how to configure the cache size for a Netflow flow monitor named MonitorTest, and then display the configuration:
n1000v# config t
n1000v(config)# flow monitor MonitorTest
n1000v(config-flow-monitor)# cache size 15000
n1000v(config-flow-monitor)# show flow monitor MonitorTestFlow
Monitor monitortest:
Use count: 0
Inactive timeout: 600
Active timeout: 1800
Cache Size: 15000
n1000v(config-flow-monitor)#
This example shows how to remove a cache size from a flow monitor:
n1000v# config t
n1000v(config)# flow monitor MonitorTest
n1000v(config-flow-monitor)# no cache size
n1000v(config-flow-monitor)#show flow monitor MonitorTestFlow
n1000v(config-flow-monitor)#
Monitor monitortest:
Use count: 0
Inactive timeout: 600
Active timeout: 1800
Cache Size: 4096
n1000v(config-flow-monitor)#
To configure the Layer 3 capability for a port profile, use the capability command. To remove a capability from a port profile, use the no form of this command.
capability l3control
no capability l3control
None
Port profile configuration (config-port-prof)
network-admin
If you are configuring a port profile for Layer 3 control, then you must first configure the transport mode as Layer 3 using the svs mode command for the VSM domain.
This example shows how to configure a port profile to be used for Layer 3 communication purposes:
n1000v# config t
n1000v(config)# port-profile testprofile
n1000v(config-port-prof)# capability l3control
n1000v(config-port-prof)#
This example shows how to remove the Layer 3 configuration from the port profile:
n1000v# config t
n1000v(config)# port-profile testprofile
n1000v(config-port-prof)# no capability l3control
n1000v(config-port-prof)#
To configure a port profile to be used with the ISCSI Multipath protocol, use the capability iscsi-multipath command. To remove the capability from a port profile, use the no form of this command.
capability iscsi-multipath
no capability iscsi-multipath
This command has no arguments or keywords.
None
Port profile configuration (config-port-prof)
network-admin
|
|
4.0(4)SV1(2) |
Added the capability iscsi multipath command. |
If you are configuring a port profile for ISCSI Multipath, then you must first configure the port-profile in switchport mode.
This example shows how to configure a port profile to be used with ISCSI Multipath protocol:
n1000v# config t
n1000v(config)# port-profile testprofile
n1000v(config-port-prof)# n1000vport mode access
n1000v(config-port-prof)# capability iscsi-multipath
n1000v(config-port-prof)#
This example shows how to remove the ISCSI multipath configuration from the port profile:
n1000v# config t
n1000v(config)# port-profile testprofile
n1000v(config-port-prof)# no capability iscsi-multipath
n1000v(config-port-prof)#
To change to a different directory from the one you are currently working in, use the cd command.
cd [filesystem:[//directory] | directory]
filesystem: |
(Optional) Name of the file system. Valid file systems are bootflash and volatile. |
//directory |
(Optional) Name of the directory. The directory name is case sensitive. |
bootflash
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
You can only change to the directories that are on the active supervisor module.
Use the present working directory (pwd) command to verify the name of the directory you are currently working in.
This example shows how to change to a different directory on the current file system:
n1000v# cd my-scripts
This example shows how to change from the file system you are currently working in to a different file system:
n1000v# cd volatile:
This example shows how to revert back to the default directory, bootflash:
n1000v# cd
|
|
---|---|
pwd |
Displays the name of the directory you are currently working in. |
To specify the CDP version to advertise, use the cdp advertise command. To remove the cdp advertise configuration, use the no form of this command.
cdp advertise {v1 | v2}
no cdp advertise [v1 | v2]
v1 |
CDP Version 1. |
v2 |
CDP Version 2. |
CDP Version 2
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to set CDP Version 1 as the version to advertise:
n1000v(
config)#
cdp advertise v1
This example shows how to remove CDP Version 1 as the configuration to advertise:
n1000v(
config)#
no cdp advertise v1
|
|
---|---|
show cdp global |
Displays the CDP configuration. |
To enable Cisco Discovery Protocol (CDP) globally on all interfaces and port channels, use the cdp enable command. To disable CDP globally, use the no form of this command.
cdp enable
no cdp enable
This command has no arguments or keywords.
Enabled on all interfaces and port channels
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
CDP can only be configured on physical interfaces and port channels.
This example shows how to enable CDP globally and then show the CDP configuration:
n1000v# config t
n1000v(config)# cdp enable
n1000v(config)# show cdp global
Global CDP information:
CDP enabled globally
Refresh time is 60 seconds
Hold time is 180 seconds
CDPv2 advertisements is enabled
DeviceID TLV in System-Name(Default) Format
This example shows how to disable CDP globally and then show the CDP configuration:
n1000v(
config)#
no cdp enable
n1000v# show cdp global
Global CDP information:
CDP disabled globally
Refresh time is 60 seconds
Hold time is 180 seconds
CDPv2 advertisements is enabled
DeviceID TLV in System-Name(Default) Format
n1000v(config)#
|
|
---|---|
show cdp global |
Displays the CDP configuration. |
cdp enable (interface or port channel) |
Enables CDP on an interface or port channel. |
To enable Cisco Discovery Protocol (CDP) on an interface or port channel, use the cdp enable command. To disable it, use the no form of this command.
cdp enable
no cdp enable
This command has no arguments or keywords.
None
Interface Configuration (config-if)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
CDP can only be configured on physical interfaces and port channels.
This example shows how to enable CDP on port channel 2:
n1000v# config t
n1000v(config)# interface port-channel2
n1000v(config-if)# cdp enable
n1000v(config-if)#
This example shows how to disable CDP on mgmt0:
n1000v# config t
n1000v(config)# interface mgmt0
n1000v(config-if)# no cdp enable
n1000v(config-if)# show cdp interface mgmt0
mgmt0 is up
CDP disabled on interface
Sending CDP packets every 60 seconds
Holdtime is 180 seconds
n1000v(config-if)#
To specify the device ID format for CDP, use the cdp format device-id command. To remove it, 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}
mac-address |
MAC address of the Chassis. |
serial-number |
Chassis serial number. |
system-name |
System name/Fully Qualified Domain Name (Default). |
System name/Fully Qualified Domain Name
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
CDP must be enabled globally before you configure the device ID format.
You can configure CDP on physical interfaces and port channels only.
This example shows how to configure the CDP device ID with the MAC address format and then display the configuration:
n1000v(
config)#
cdp format device-id mac-address
n1000v
(config)# show cdp global
Global CDP information:
CDP enabled globally
Sending CDP packets every 5 seconds
Sending a holdtime value of 10 seconds
Sending CDPv2 advertisements is disabled
Sending DeviceID TLV in Mac Address Format
This example shows how to remove the CDP device ID MAC address format from the configuration:
n1000v(
config)#
no cdp format device-id mac-address
To do set the maximum amount of time that CDP holds onto neighbor information before discarding it, use the cdp holdtime command. To remove the CDP holdtime configuration, use the no form of this command.
cdp holdtime seconds
no cdp holdtime seconds
seconds |
The range is from 10 to 255 seconds. |
180 seconds
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
CDP must be enabled globally before you configure the device ID format.
You can configure CDP on physical interfaces and port channels only.
This example shows how to set the CDP holdtime to 10 second:
n1000v(
config)#
cdp holdtime 10
This example shows how to remove the CDP holdtime configuration:
n1000v(
config)#
no cdp holdtime 10
|
|
---|---|
show cdp global |
Displays CDP global configuration parameters. |
show cdp neighbors |
Displays the upstream device from your device. |
To set the refresh time for CDP to send advertisements to neighbors, use the cdp timer command. To remove the CDP timer configuration, use the no form of this command.
cdp timer seconds
no cdp timer seconds
seconds |
The range is from 5 to 254 seconds. |
60 seconds
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to configure the CDP timer to 10 seconds:
n1000v(
config)#
cdp timer 10
This example shows how to remove the CDP timer configuration:
n1000v(
config)#
no cdp timer 10
|
|
---|---|
show cdp global |
Displays CDP global configuration parameters. |
show cdp neighbors |
Displays the upstream device from your device. |
To create and define a channel group for all interfaces that belong to a port profile, use the channel-group auto command. To remove the channel group, use the no form of this command.
channel-group auto [mode channel_mode] [sub-group {cdp | manual}] [mac-pinning]
no channel-group
None
Port profile configuration (config-port-prof)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
4.0(4)SV1(2) |
Support for manual creation of subgroups and mac-pinning. |
The channel-group auto command creates a unique port channel for all interfaces that belong to the same module. The channel group is automatically assigned when the port profile is assigned to the first interface. Each additional interface that belongs to the same module is added to the same port channel. In VMware environments, a different port channel is created for each module.
•The channel group mode must be set to on when configuring vPC-HM.
•When configuring a port channel for a port profile that connects to two or more upstream n1000ves, note the following:
–You need to know whether CDP is configured in the upstream n1000ves.
If configured, CDP creates a subgroup for each upstream n1000v to manage its traffic separately.
If not configured, then you must manually configure subgroups to manage the traffic flow on the separate n1000ves.
–When configuring a port channel for vPC-HM and the upstream n1000ves do not support port channels, you can use MAC pinning, which will automatically assign each Ethernet member port to a unique sub-group.
–If vPC-HM is not configured when port channels connect to two different upstream n1000ves, the VMs behind the Cisco Nexus 1000V receive duplicate packets from the network for broadcasts and multicasts.
–You can also configure vPC-HM on the interface. For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(2).
This example shows how to configure a port profile for a port channel that connects to a single upstream n1000v and then display the configuration:
n1000v# config t
n1000v(config)# port-profile AccessProf
n1000v(config-port-prof)# channel-group auto mode on
n1000v(config-port-prof)# show port-profile name AccessProf
port-profile AccessProf
description: allaccess4
status: disabled
capability uplink: yes
port-group: AccessProf
config attributes:
n1000vport mode access
channel-group auto mode on
evaluated config attributes:
n1000vport mode access
channel-group auto mode on
assigned interfaces:
n1000v(config-port-prof)#
This example shows how to remove the channel group configuration from the port profile and then display the configuration:
n1000v# config t
n1000v(config)# port-profile AccessProf
n1000v(config-port-prof)# no channel-group
n1000v(config-port-prof)# show port-profile name AccessProf
port-profile AccessProf
description: allaccess4
status: disabled
capability uplink: yes
port-group: AccessProf
config attributes:
n1000vport mode access
evaluated config attributes:
n1000vport mode access
assigned interfaces:
n1000v(config-port-prof)#
This example shows how to configure a port profile for a port channel that connects to multiple upstream n1000ves that have CDP enabled and then display the configuration:
n1000v# config t
n1000v(config)# port-profile uplinkProf
n1000v(config-port-prof)# channel-group auto mode on sub-group cdp
n1000v(config-port-prof)# show port-profile name uplinkProf
port-profile uplinkProf
description:
type: vethernet
status: disabled
capability l3control: no
pinning control-vlan: -
pinning packet-vlan: -
system vlans: none
port-group:
max ports: 32
inherit:
config attributes:
channel-group auto mode on sub-group cdp
evaluated config attributes:
channel-group auto mode on sub-group cdp
assigned interfaces:
To create a port channel group or to move an interface from one port channel group to another, use the channel-group command. To remove the channel group configuration from an interface, use the no form of this command.
channel-group number [force] [mode {active | on | passive}]
no channel-group [number]
The default mode is on.
Interface configuration (config-if)
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
A port channel in the on channel mode is a pure port channel and can aggregate a maximum of eight ports. It does not run LACP.
If an existing port channel is not running LACP you cannot change the mode for it or any of its interfaces. If you try to do so, the channel mode remains on and an error message is generated.
When you delete the last physical interface from a port channel, the port channel remains. To delete the port channel completely, use the no form of the port-channel command.
When an interface joins a port channel, the following attributes are removed and replaced with the those of the port channel:
•Bandwidth
•Delay
•Extended Authentication Protocol over UDP
•VRF
•IP address
•MAC address
•Spanning Tree Protocol
•NAC
•Service policy
•Quality of Service (QoS)
•ACLs
The following attributes remain unaffected when an interface joins or leaves a port channel:
•Beacon
•Description
•CDP
•LACP port priority
•Debounce
•UDLD
•MDIX
•Rate mode
•Shutdown
•SNMP trap
You do not have to create a port channel interface before you assign a physical interface to a channel group. A port channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
This example shows how to add an interface to LACP channel group 5 in active mode:
n1000v(config-if)#
channel-group 5 mode active
n1000v(config-if)#
To check the compactFlash, use the check logflash command.
check logflash [bad-blocks]
bad-blocks |
(Optional) Finds bad blocks in compactFlash. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to check compactFlash:
n1000v# check logflash
To add an existing Quality of Service (QoS) class to a policy map, use the class command. To remove a QoS class from a policy map, use the no form of this command.
class [type qos] {class-map-name | class-default} [insert-before [type qos] before-class-map-name]
no class {class-map-name | class-default}
type QoS
The default is to reference a new class map at the end of the policy map.
The class named class-default matches all traffic not classified in other classes.
Policy Map Configuration (config-pmap)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Policy actions in the first class that matches the traffic type are performed.
The class named class-default matches all traffic not classified in other classes.
This example shows how to add a class map in sequence to the end of a policy map:
n1000v(
config)#
policy-map my_policy1
n1000v(config-pmap)# class traffic_class2
n1000v(config-pmap-c-qos)#
This example shows how to insert a class map in sequence before an existing class map in a policy map:
n1000v(
config)#
policy-map my_policy1
n1000v(config-pmap-qos)# class insert-before traffic_class2 traffic_class1
n1000v(config-pmap-c-qos)#
This example shows how to add the class-default class map to a policy map:
n1000v(
config)#
policy-map my_policy1
n1000v(config-pmap-qos)# class class-default
n1000v(config-pmap-c-qos)#
This example shows how to remove a class map reference from a policy map:
n1000v(
config)#
policy-map my_policy1
n1000v(config-pmap)# no class traffic_class1
n1000v(config-pmap)#
To create or modify a class map that defines a class of traffic, use the class-map command. To remove a class map, use the no form of this command.
class-map [type qos] {match-any | match-all] class-map-name}
no class-map [type qos] {class-map-name | [match-any | match-all]}
type QoS
match-all
Global Configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Hyphen, underscore, and alphabetic characters are allowed in the class map name.
Forty characters are the maximum allowed in the class map name.
Characters in the class map name are case sensitive.
This example shows how to create a class map and enter the QoS class map configuration mode to configure the specified map:
n1000v(
config)#
class-map my_class1
n1000v(config-cmap-qos)#
This example shows how to remove the QoS class map named my_class1:
n1000v(
config)#
no class-map my_class1
n1000v(config)#
To clear the counters for IP and MAC access control list(s) (ACLs), use the clear access-list counters command.
clear access-list counters [access-list-name]
access-list-name |
(Optional) Name of the ACL whose counters the device clears. The name can be up to 64 alphanumeric, case-sensitive characters. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
If you specify an ACL, the name can be up to 64 alphanumeric, case-sensitive characters.
This example shows how to clear counters for all IP and MAC ACLs:
n1000v# clear access-list counters
n1000v#
This example shows how to clear counters for an IP ACL named acl-ip-01:
n1000v# clear access-list counters acl-ip-01
n1000v#
To clear Cisco Discovery Protocol(CDP) information on an interface, use the clear cdp command.
clear cdp {counters [interface slot/port] | table [interface slot/port]}
counters |
Clear CDP counters on all interfaces. |
interface slot/port |
(Optional) Clear CDP counters on a specified interface . |
table |
Clear CDP cache on all interfaces. |
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear CDP counters on all interfaces:
n1000V#
clear cdp counters
This example shows how to clear CDP cache on all interfaces:
n1000V#
clear cdp table
To clear the history of commands you have entered into the CLI, use the clear cli history command.
clear cli history
This command has no arguments or keywords.
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use the show cli history command to display the history of the commands that you entered at the command-line interface (CLI).
This example shows how to clear the command history:
n1000v# clear cli history
|
|
---|---|
show cli history |
Displays the command history. |
To clear the core files, use the clear cores command.
clear cores [archive]
archive |
(Optional) Clears the core file on the logflash filesystem. |
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use the show system cores command to display information about the core files.
This example shows how to clear the core file:
n1000v# clear cores
This example shows how to clear the core on the logflash filesystem:
n1000v# clear cores archive
|
|
---|---|
show system cores |
Displays the core filename. |
system cores |
Configures the core filename. |
To clear interface counters, use the clear counters command.
clear counters [ interface {all | ethernet slot/port | loopback virtual-interface-number | mgmt | port-channel port-channel-number | vethernet interface-number} ]
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear the Ethernet interface counters:
n1000v(
config)#
clear counters ethernet 2/1
|
|
---|---|
show interface counters |
Displays the interface status, which includes the counters. |
To clear the contents of the debug logfile, use the clear debug-logfile command.
clear debug-logfile filename
filename |
Name of the debug logfile to clear. |
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear the debug logfile:
n1000v# clear debug-logfile syslogd_debugs
|
|
---|---|
debug logfile |
Configures a debug logging file. |
debug logging |
Enable debug logging. |
show debug logfile |
Displays the contents of the debug logfile. |
To clear the statistics for a Flexible NetFlow flow exporter, use the clear flow exporter command in Any.
clear flow exporter {name exporter-name | exporter-name}
name |
Indicates that a flow exporter will be specified by name. |
exporter-name |
Name of an existing flow exporter. |
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
You must have already enabled traffic monitoring with Flexible NetFlow using an exporter before you can use the clear flow exporter command.
The following example clears the statistics for the flow exporter named NFC-DC-PHOENIX:
n1000v# clear flow exporter name NFC-DC-PHOENIX
n1000v#
|
|
---|---|
clear flow exporter |
Clears the statistics for exporters. |
flow exporter |
Creates a flow exporter. |
show flow exporter |
Displays flow exporter status and statistics. |
To clear the counters for IP access control lists (ACLs), use the clear ip access-list counters command.
clear ip access-list counters [access-list-name]
access-list-name |
(Optional) Name of the IP ACL whose counters you want cleared. The name can be up to 64 alphanumeric, case-sensitive characters. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
If specifying an ACL by name, it can be up to 64 alphanumeric, case-sensitive characters.
This example shows how to clear counters for all IP ACLs:
n1000v# clear ip access-list counters
n1000v#
This example shows how to clear counters for an IP ACL named acl-ip-101:
n1000v# clear ip access-list counters acl-ip-101
n1000v#
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
vlan-list |
Range of VLAN IDs from 1 to 4094 that you can clear DAI statistics from. |
None
Any
network-admin
|
|
4.0(4)SV1(2) |
This command was introduced. |
This example shows how to clear the DAI statistics for VLAN 2:
n1000v# clear ip arp inspection statistics vlan 2
n1000v#
This example shows how to clear the DAI statistics for VLANs 5 through 12:
n1000v# clear ip arp inspection statistics vlan 5-12
n1000v#
This example shows how to clear the DAI statistics for VLAN 2 and VLANs 5 through 12:
n1000v# clear ip arp inspection statistics vlan 2,5-12
n1000v#
|
|
---|---|
ip arp inspection vlan |
Enables or disables DAI for a list of VLANs. |
show ip arp inspection statistics |
Displays the DAI statistics. |
To clear dynamically added entries from the DHCP snooping binding database, use the clear ip dhcp snooping binding command.
clear ip dhcp snooping binding [vlan vlan-id mac mac-addr ip ip-addr interface interface-id]
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear dynamically added entries from the DHCP snooping binding database:
n1000v# clear ip dhcp snooping binding
n1000v#
To clear the IGMP statistics for an interface, use the clear ip igmp interface statistics command.
clear ip igmp interface statistics [if-type if-number]
if-type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
if-number |
(Optional) Interface number. |
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear IGMP statistics for an interface:
n1000v#
clear ip igmp interface statistics ethernet 2/1
n1000v#
|
|
---|---|
show ip igmp interface |
Displays information about IGMP interfaces. |
To clear the IGMP snooping statistics for VLANs, use the clear ip igmp snooping statistics vlan command.
clear ip igmp snooping statistics vlan {vlan-id | all}
vlan-id |
VLAN number. The range is from 1 to 3967 and 4048 to 4093. |
all |
Applies to all VLANs. |
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear IGMP snooping statistics for VLAN 1:
n1000v#
clear ip igmp snooping statistics vlan 1
n1000v#
|
|
---|---|
show ip igmp snooping statistics vlan |
Displays IGMP snooping statistics by VLAN. |
To clear the statistics for all interfaces for Link Aggregation Control Protocol (LACP) groups, use the clear lacp counters command.
clear lacp counters [interface port-channel channel-number]
channel-number |
(Optional) LACP port-channel number. The range of values is from 1 to 4096. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
If you clear counters for a specific port channel, the allowable port channel numbers are from 1 to 4096.
If you do not specify a channel number, the LACP counters for all LACP port groups are cleared.
If you clear counters for a static port-channel group, without the aggregation protocol enabled, the device ignores the command.
This example shows how to clear all the LACP counters:
n1000v(config)#
clear lacp counters
n1000v(config) #
This example shows how to clear all LACP counters for the LACP port-channel group 20:
n1000v(config)#
clear lacp counters interface port-channel 20
n1000v(config)#
|
|
---|---|
show lacp counters |
Displays information about LACP statistics. |
To uninstall a license file from a VSM, or to uninstall an evaluation license before installing a permanent license, use the clear license command.
clear license filename
filename |
Name of the license file to be uninstalled. |
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
If a license is in use, you cannot uninstall it. Before uninstalling the license file, all licenses must first be transferred from the VEMs to the VSM license pool.
This example shows how to remove the Enterprise.lic license file from a VSM:
n1000v# clear license Enterprise.lic
Clearing license Enterprise.lic:
SERVER this_host ANY
VENDOR cisco
Do you want to continue? (y/n) y
Clearing license ..done
n1000v#
To end a session on a specified vty, use the clear line command.
clear line word
word |
Specifies the vty name. |
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to end a session on a specified vty:
n1000v(
config)#
clear line
|
|
---|---|
show users |
Displays active user sessions. |
Use the clear logging logfile command to clear messages from the logging file.
clear logging logfile
This command has no arguments or keywords.
None
Any
Super user
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear messages from the logging file:
n1000v# clear logging logfile
n1000v#
|
|
---|---|
show logging logfile |
Displays the logs in the local log file. |
Use the clear logging session command to clear the current logging session.
clear logging session
This command has no arguments or keywords.
None
Any
Super user
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear the current logging session:
n1000v# clear logging session
n1000v#
|
|
---|---|
show logging session |
Displays logging session status |
To clear the counters for MAC access control lists (ACLs), use the clear mac access-list counters command.
clear mac access-list counters [access-list-name]
access-list-name |
(Optional) Name of the MAC ACL whose counters you want to clear. The name can be up to 64 alphanumeric, case-sensitive characters. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
If you want counters cleared for a specific MAC ACL, the name can be up to 64 alphanumeric, case-sensitive characters.
This example shows how to clear counters for all MAC ACLs:
n1000v# clear mac access-list counters
n1000v#
This example shows how to clear counters for a MAC ACL named acl-mac-0060:
n1000v# clear mac access-list counters acl-mac-0060
n1000v#
To clear the dynamic address entries from the MAC address table in Layer 2, use the clear mac address-table dynamic command.
clear mac address-table dynamic [[address mac_addr] [vlan vlan-id] [interface {type slot/port | port-channel number}]
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Use the clear mac address-table dynamic command with no arguments to remove all dynamic entries from the table.
To clear static MAC addresses from the table, use the no mac address-table static command.
If the clear mac address-table dynamic command is entered with no options, all dynamic addresses are removed. If you specify an address but do not specify an interface, the address is deleted from all interfaces. If you specify an interface but do not specify an address, the device removes all addresses on the specified interfaces.
This example shows how to clear all the dynamic Layer 2 entries from the MAC address table:
n1000v(config)#
clear mac address-table dynamic
n1000v(config) #
This example shows how to clear all the dynamic Layer 2 entries from the MAC address table for VLAN 20 on port 2/20:
n1000v(config)#
clear mac address-table dynamic vlan 20 interface ethernet 2/20
n1000v(config)#
|
|
---|---|
show mac address-table |
Displays the information about the MAC address table. |
To clear the Network Time Protocol statistics, use the clear ntp statistics command.
clear ntp statistics {all-peers | io | local | memory}
all-peers |
Clear statistics for all NTP peers. |
io |
Clear IO statistics. |
local |
Clear local statistics. |
memory |
Clear memory statistics. |
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear statistics for all NTP peers:
n1000v(
config)#
clear ntp statistics all-peers
|
|
---|---|
show ntp peers |
Displays information about NTP peers. |
To clear dynamically-learned, secure MAC address(es), use the clear port-security command.
clear port-security {dynamic} {interface vethernet veth-number | address address} [vlan vlan-id]
dynamic
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to remove dynamically learned, secure MAC addresses from the veth1 interface:
n1000v# config t
n1000v(config)# clear port-security dynamic interface veth 1
This example shows how to remove the dynamically learned, secure MAC address 0019.D2D0.00AE:
n1000v# config t
n1000v(config)# clear port-security dynamic address 0019.D2D0.00AE
To clear the counters for QoS statistics, use the clear qos statistics command.
clear qos statistics {interface [ethernet type/slot | vethernet number | port-channel number] } [input type qos | output type qos]}
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
If you do not specify an interface, the counters are cleared for all interfaces.
This example shows how to clear QoS statistics for all interfaces:
n1000v#
clear qos statistics
n1000v#
This example shows how to clear all input QoS statistics for veth2:
n1000v#
clear qos statistics veth2 input type qos
n1000v#
|
|
---|---|
qos statistics |
Enables or disables QoS statistics. |
show policy-map |
Displays the policy map configuration for all policy maps or for a specified policy map. |
To clear the Secure Shell (SSH) host sessions, use the clear ssh hosts command.
clear ssh hosts
This command has no arguments or keywords.
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear all SSH host sessions:
n1000v# clear ssh hosts
|
|
---|---|
ssh server enable |
Enables the SSH server. |
To clear the device reset-reason history, use the clear system reset-reason command.
clear system reset-reason
This command has no arguments or keywords.
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to clear reset-reason history:
n1000v# clear system reset-reason
|
|
---|---|
show system reset-reason |
Displays the device reset-reason history. |
To clear a user session, use the clear user command.
clear user user-id
user-id |
User identifier. |
None
Any
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Use the show users command to display the current user sessions on the device.
This example shows how to clear all SSH host sessions:
n1000v# clear user user1
|
|
---|---|
show users |
Displays the user session information. |
To define a command line interface (CLI) variable for a terminal session, use the cli var name command. To remove the CLI variable, use the no form of this command.
cli var name variable-name variable-text
cli no var name variable-name
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
You can reference a CLI variable using the following syntax:
$(variable-name)
Instances where you can use variables in include the following:
•Command scripts
•Filenames
You cannot reference a variable in the definition of another variable.
You can use the predefined variable, TIMESTAMP, to insert the time of day. You cannot change or remove the TIMESTAMP CLI variable.
You must remove a CLI variable before you can change its definition.
This example shows how to define a CLI variable:
n1000v# cli var name testinterface interface 2/3
This example shows how to reference the TIMESTAMP variable:
n1000v# copy running-config > bootflash:run-config-$(TIMESTAMP).cnfg
This example shows how to remove a CLI variable:
n1000v# cli no var name testinterface interface 2/3
|
|
---|---|
show cli variables |
Displays the CLI variables. |
To manually set the clock, use the clock set command.
clock set time day month year
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use this command when you cannot synchronize your device with an outside clock source, such as NTP.
This example shows how to manually set the clock:
n1000v# clock set 9:00:00 1 June 2008
|
|
---|---|
show clock |
Displays the clock time. |
To configure the summer-time (daylight saving time) offset, use the clock summer-time command. To revert to the default, use the no form of this command.
clock summer-time zone-name start-week start-day start-month start-time end-week end-day end-month end-time offset-minutes
no clock summer-time
None
Global Configuration (config)
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to configure the offset for summer-time or daylight saving time:
n1000v# configure terminal
n1000v(config)# clock summer-time PDT 1 Sunday March 02:00 1 Sunday November 02:00 60
This example shows how to remove the summer-time offset:
n1000v# configure terminal
n1000v(config)# no clock summer-time
|
|
---|---|
show clock |
Displays clock summer-time offset configuration. |
To configure the time zone offset from Coordinated Universal Time (UTC), use the clock timezone command. To revert to the default, use the no form of this command.
clock timezone zone-name offset-hours offset-minutes
no clock timezone
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to configure the time zone offset from UTC:
n1000v# clock timezone EST 5 0
This example shows how to remove the time zone offset:
n1000v# no clock timezone
|
|
---|---|
show clock |
Displays the clock time. |
To configure the number of bytes or packets in a flow as a non-key field and collect the number of bytes or packets seen for a Flexible NetFlow flow record, use the collect counter command. To disable the counters, use the no form of this command.
collect counter {bytes [long] | packets [long]}
no collect counter {bytes [long] | packets [long]}
This command is not enabled by default.
Flow Record Configuration
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
The following example enables collecting the total number of bytes from the flows as a non-key field:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect counter bytes
The following example enables collecting the total number of bytes from the flows as a non-key field using a 64 bit counter:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect counter bytes long
The following example enables collecting the total number of packets from the flows as a non-key field:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect counter packets
The following example enables collecting the total number of packets from the flows as a non-key field using a 64 bit counter:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect counter packets long
To collect the TIMESTAMP SYS-UPTIME for a NetFlow flow record, use the collect timestamp sys-uptime command. To disable the collection, use the no form of this command.
collect timestamp sys-uptime {first | last}
no collect timestamp sys-uptime {first | last}
This command is not enabled by default.
Flow Record Configuration
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
The following example enables collecting the sys-uptime for the time the first packet was seen from the flows:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect timestamp sys-uptime first
The following example enables collecting the sys-uptime for the time the most recent packet was seen from the flows:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect timestamp sys-uptime last
|
|
---|---|
flow record |
Creates a flow record. |
show flow record |
Displays flow record status and statistics. |
To collect a Transmission Control Protocol (TCP) flags for a NetFlow flow record, use the collect transport tcp flags command. To disable the collection, use the no form of this command.
collect transport tcp flags
no collect transport tcp flags
This command has no arguments or keywords
This command is not enabled by default.
Flow Record Configuration
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
The following example collects the TCP flags:
n1000v(config)# flow record FLOW-RECORD-1
n1000v(config-flow-record)# collect transport tcp flags
|
|
---|---|
flow record |
Creates a flow record. |
show flow record |
Displays flow record status and statistics. |
To access configuration commands in the CLI global configuration mode, use the configure terminal command.
configure terminal
This command has no arguments or keywords.
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
The configuration changes you make in the global configuration mode are saved in the running configuration file. To save these changes persistently across reboots and restarts, you must copy them to the startup configuration file using the copy running-config startup-config command.
This example shows how to access configuration commands in the CLI global configuration mode:
n1000v# configure terminal
n1000v(config)#
To initiate a connection with vCenter, use the connect command. To disconnect from vCenter, use the no form of this command.
connect
no connect
This command has no arguments or keywords.
no connect
SVS Connect Configuration (config-svs-conn)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Upon connection to vCenter, if a username and password have not been configured for this connection, you are prompted to enter them.
There can be only one active connection at a time. If a previously-defined connection is up, an error message displays and the connect command is rejected until the previous connection is closed by entering no connect.
This example shows how to connect to vCenter:
n1000v(config#)
svs connection vcWest
n1000v(config-svs-conn#)
protocol vmware-vim
n1000v(config-svs-conn#)
remote hostname vcMain
n1000v(config-svs-conn#)
vmware dvs datacenter-name HamiltonDC
n1000v(config-svs-conn#)
connect
This example shows how to disconnect from vCenter:
n1000v(config#)
svs connection vcWest
n1000v(config-svs-conn#)
no connect
|
|
---|---|
show svs connections |
Displays the current connections to the Cisco Nexus 1000V. |
To assign a control VLAN to the Cisco Nexus 1000V domain, use the control vlan command. To remove the control VLAN, use the no form of this command.
control vlan number
no control vlan
number |
control VLAN number. |
None
SVS Domain Configuration (config-svs-domain)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
Newly-created VLANs remain unused until Layer 2 ports are assigned to them.
If you enter a VLAN ID that is assigned to an internally allocated VLAN, the CLI returns an error message.
This example shows how to configure control VLAN 70 for domain ID 32:
n1000v# config t
n1000v(config)# svs-domain
n1000v(config-svs-domain)# domain id 32
n1000v(config-svs-domain)# control vlan 70
n1000v(config-svs-domain)#
This example shows how to remove control VLAN 70 from domain ID 32:
n1000v# config t
n1000v(config)# svs-domain
n1000v(config-svs-domain)# domain id 32
n1000v(config-svs-domain)# no control vlan 70
n1000v(config-svs-domain)#
To copy a file from a source to a destination, use the copy command.
copy source-url destination-url
The format of the source and destination URLs varies according to the file or directory location. You may enter either a command-line interface (CLI) variable for a directory or a filename that follows the Cisco NX-OS file system syntax (filesystem:[/directory][/filename]).
The following tables list URL prefix keywords by the file system type. If you do not specify a URL prefix keyword, the device looks for the file in the current directory.
Table 1 lists URL prefix keywords for bootflash and remote writable storage file systems.
Table 2 lists the URL prefix keywords for nonwritable file systems.
The default name for the destination file is the source filename.
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
The entire copying process may take several minutes, depending on the network conditions and the size of the file, and differs from protocol to protocol and from network to network.
The colon character (:) is required after the file system URL prefix keywords (such as bootflash).
In the URL syntax for ftp:, scp:, sftp:, and tftp:, the server is either an IP address or a host name.
This example shows how to copy a file within the same directory:
n1000v# copy file1 file2
This example shows how to copy a file to another directory:
n1000v# copy file1 my_files:file2
This example shows how to copy a file to another supervisor module:
n1000v# copy file1 bootflash://sup-remote/file1.bak
This example shows how to copy a file from a remote server:
n1000v# copy scp://10.10.1.1/image-file.bin bootflash:image-file.bin
To copy the running configuration to the startup configuration, use the copy running-config startup-config command.
copy running-config startup-config
This command has no arguments or keywords.
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use this command to save configuration changes in the running configuration to the startup configuration in persistent memory. When a device reload or switchover occurs, the saved configuration is applied.
This example shows how to save the running configuration to the startup configuration:
n1000v# copy running-config startup-config
[########################################] 100%