Feedback
Table Of Contents
default switchport (port profile)
default shutdown (port profile)
default switchport port-security (VEthernet)
D Commands
This chapter describes the Cisco Nexus 1000V commands that begin with the letter D.
deadtime
To configure the duration of time for which a non-reachable RADIUS or TACACS+ server is skipped, use the deadtime command. To revert to the default, use the no form of this command.
deadtime minutes
no deadtime minutes
Syntax Description
Defaults
0 minutes
Command Modes
RADlUS server group configuration (config-radius)
TACACS+ server group configuration (config-tacacs+)
Global Configuration (config)Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Before you can configure it, you must enable TACACS+ using the tacacs+ enable command.
The dead-time can be configured either globally and applied to all RADIUS or TACACS+ servers; or per server group.
If the dead-time interval for a RADIUS or TACACS+ server group is greater than zero (0), that value takes precedence over the global dead-time value.
Setting the dead-time interval to 0 disables the timer.
When the dead-time interval is 0 minutes, RADIUS and TACACS+ servers are not marked as dead even if they are not responding.
Examples
This example shows how to set the dead-time interval to 2 minutes for a RADIUS server group:
n1000v# config tn1000v(config)# aaa group server radius RadServern1000v(config-radius)# deadtime 2This example shows how to set a global dead-time interval to 5 minutes for all TACACS+ servers and server groups:
n1000v# config tn1000v(config)# tacacs-server deadtime 5n1000v(config)#This example shows how to set the dead-time interval to 5 minutes for a TACACS+ server group:
n1000v# config tn1000v(config)# aaa group server tacacs+ TacServern1000v(config-tacacs+)# deadtime 5This example shows how to revert to the dead-time interval default:
n1000v# config tn1000v(config)# feature tacacs+n1000v(config)# aaa group server tacacs+ TacServern1000v(config-tacacs+)# no deadtime 5Related Commands
debug logfile
To direct the output of the debug commands to a specified file, use the debug logfile command. To revert to the default, use the no form of this command.
debug logfile filename [size bytes]
no debug logfile filename [size bytes]
Syntax Description
Defaults
Default filename: syslogd_debugs
Default file size: 4194304 bytes
Command Modes
Any
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The logfile is created in the log: file system root directory.
Use the dir log: command to display the log files.
Examples
This example shows how to specify a debug logfile:
n1000v# debug logfile debug_logThis example shows how to revert to the default debug logfile:
n1000v# no debug logfile debug_logRelated Commands
dir
Displays the contents of a directory.
show debug
Displays the debug configuration.
show debug logfile
Displays the debug logfile contents.
debug logging
To enable debug command output logging, use the debug logging command. To disable debug logging, use the no form of this command.
debug logging
no debug logging
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Any
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to enable the output logging for the debug command:
n1000v# debug loggingThis example shows how to disable the output logging for the debug command:
n1000v# no debug loggingRelated Commands
default switchport (port profile)
To remove a particular switchport characteristc from a port profile, use the default switchport command.
default switchport {mode | access vlan | trunk {native | allowed} vlan | private-vlan {host-association | mapping [trunk]} | port-security}
Syntax Description
Defaults
None
Command Modes
Port Profile Configuration (config-port-prof)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The functionally of this command is equivalent to using the no form of a specific switchport command. For example, the effect of the following commands is the same:
•
default switchport mode command = no switchport mode command
•
•
Examples
This example shows how to revert port profile ports to switch access ports.
n1000v(config-port-prof)# default switchport modeThis example shows how to remove the trunking allowed VLAN characteristics of a port profile.
n1000v(config-port-prof)# default switchport trunk allowed vlanThis example shows how toremove the private VLAN host association of a port profile.
n1000v(config-port-prof)# default switchport private-vlan host-associationThis example shows how to remove port security characteristics of a port profile.
n1000v(config-port-prof)# default switchport port-securityRelated Commands
default shutdown (port profile)
To remove the admin status characteristic (config attribute) from a port-profile, use the default shutdown command. This will set the admin status of the interfaces inheriting this port-profile to the global or interface default (usually, the default admin status is shutdown).
default shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Port Profile Configuration (config- port-prof)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to change the ports in a port profile to the shutdown state:
n1000v# config tn1000v# port-profile DataProfilen1000v(config-port-prof)# default shutdownn1000v(config-port-prof)# show port-profile name DataProfileport-profile DataProfiledescription:status: enabledcapability uplink: nocapability l3control: nosystem vlans: noneport-group: DataProfilemax-ports: 32inherit:config attributes:switchport mode accessevaluated config attributes:switchport mode accessassigned interfaces:Vethernet1switch(config-port-prof)#Related Commands
default shutdown (interface)
To remove any interface-level override for the admin status, use the default shutdown command. This command removes any configuration for admin status entered previously. This allows the port-profile config to take effect.
default shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Interface Configuration (config- if)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to change the ports to the shutdown state:
n1000v# config tn1000v(config)# interface ethernet 3/2n1000v(config-if)# default shutdownn1000v(config-if)#Related Commands
default switchport port-security (VEthernet)
To remove any user configuration for the switchport port-security characteristic from a VEthernet interface, use the default switchport port-security command. This has the effect of setting the default (disabled) for port-security for that interface.
default switchport port-security
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface Configuration (config-if)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to disable port security on VEthernet 2:
n1000v# config tn1000v(config)# interface veth 2n1000v(config-if)# default switchport port-securityn1000v(config-if)#Related Commands
show running-config port-security
Displays the port security configuration.
show port-security
Displays the port security status.
delay
To assign an informational throughput delay value to an Ethernet interface, use the delay command. To remove delay value, use the no form of this command.
delay value
no delay [value]
Syntax Description
delay_val
Specifies the throughput delay time in tens of microseconds.
Allowable values are between 1 and 16777215.
Defaults
None
Command Modes
Interface Configuration (config-if)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The actual Ethernet interface throughput delay time does not change when you set this value—the setting is for informational purposes only.
Examples
This example shows how to assign the delay time to an Ethernet slot 3 port 1 interface:
n1000v# config tn1000v(config)# interface ethernet 3/1n1000v(config-if)# delay 10000n1000v(config-if)#This example shows how to remove the delay time configuration:
n1000v# config tn1000v(config)# interface ethernet 3/1n1000v(config-if)# no delay 10000n1000v(config-if)#Related Commands
delete
To delete a file, use the delete command.
delete [filesystem:[//directory/] | directory/]filename
Syntax Description
Defaults
None
Command Modes
Any
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Use the dir command to locate the file you that want to delete.
Examples
This example shows how to delete a file:
n1000v# delete bootflash:old_config.cfgRelated Commands
deny (IPv4)
To create an IPv4 ACL rule that denies traffic matching its conditions, use the deny command. To remove a rule, use the no form of this command.
General Syntax
[sequence-number] deny protocol source destination [dscp dscp | precedence precedence]
no deny protocol source destination [dscp dscp | precedence precedence]
no sequence-number
Internet Control Message Protocol
[sequence-number] deny icmp source destination [icmp-message] [dscp dscp | precedence precedence]
Internet Group Management Protocol
[sequence-number] deny igmp source destination [igmp-message] [dscp dscp | precedence precedence]
Internet Protocol v4
[sequence-number] deny ip source destination [dscp dscp | precedence precedence]
Transmission Control Protocol
[sequence-number] deny tcp source [operator port [port] | portgroup portgroup] destination [operator port [port] | portgroup portgroup] [dscp dscp | precedence precedence] [fragments] [log] [time-range time-range-name] [flags] [established]
User Datagram Protocol
[sequence-number] deny udp source operator port [port] destination [operator port [port] [dscp dscp | precedence precedence]
Syntax Description
Defaults
A newly created IPv4 ACL contains no rules.
If you do not specify a sequence number, the device assigns the rule a sequence number that is 10 greater than the last rule in the ACL.
Command Modes
IPv4 ACL configuration (config-acl)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
When the device applies an IPv4 ACL to a packet, it evaluates the packet with every rule in the ACL. The device enforces the first rule that has conditions that are satisfied by the packet. When the conditions of more than one rule are satisfied, the device enforces the rule with the lowest sequence number.
Source and Destination
You can specify the source and destination arguments in one of several ways. In each rule, the method that you use to specify one of these arguments does not affect how you specify the other argument. When you configure a rule, use the following methods to specify the source and destination arguments:
•
IPv4-address network-wildcardThe following example shows how to specify the source argument with the IPv4 address and network wildcard for the 192.168.67.0 subnet:
switch(config-acl)# deny tcp 192.168.67.0 0.0.0.255 any•
IPv4-address/prefix-lenThe following example shows how to specify the source argument with the IPv4 address and VLSM for the 192.168.67.0 subnet:
switch(config-acl)# deny udp 192.168.67.0/24 any•
host IPv4-addressThis syntax is equivalent to IPv4-address/32 and IPv4-address 0.0.0.0.
The following example shows how to specify the source argument with the host keyword and the 192.168.67.132 IPv4 address:
switch(config-acl)# deny icmp host 192.168.67.132 any•
ICMP Message Types
The icmp-message argument can be the ICMP message number, which is an integer from 0 to 255. It can also be one of the following keywords:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
TCP Port Names
When you specify the protocol argument as tcp, the port argument can be a TCP port number, which is an integer from 0 to 65535. It can also be one of the following keywords:
bgp—Border Gateway Protocol (179)
chargen—Character generator (19)
cmd—Remote commands (rcmd, 514)
daytime—Daytime (13)
discard—Discard (9)
domain—Domain Name Service (53)
drip—Dynamic Routing Information Protocol (3949)
echo—Echo (7)
exec—EXEC (rsh, 512)
finger—Finger (79)
ftp—File Transfer Protocol (21)
ftp-data—FTP data connections (2)
gopher—Gopher (7)
hostname—NIC hostname server (11)
ident—Ident Protocol (113)
irc—Internet Relay Chat (194)
klogin—Kerberos login (543)
kshell—Kerberos shell (544)
login—Login (rlogin, 513)
lpd—Printer service (515)
nntp—Network News Transport Protocol (119)
pim-auto-rp—PIM Auto-RP (496)
pop2—Post Office Protocol v2 (19)
pop3—Post Office Protocol v3 (11)
smtp—Simple Mail Transport Protocol (25)
sunrpc—Sun Remote Procedure Call (111)
tacacs—TAC Access Control System (49)
talk—Talk (517)
telnet—Telnet (23)
time—Time (37)
uucp—UNIX-to-UNIX Copy Program (54)
whois—WHOIS/NICNAME (43)
www—World Wide Web (HTTP, 8)
UDP Port Names
When you specify the protocol argument as udp, the port argument can be a UDP port number, which is an integer from 0 to 65535. It can also be one of the following keywords:
biff—Biff (mail notification, comsat, 512)
bootpc—Bootstrap Protocol (BOOTP) client (68)
bootps—Bootstrap Protocol (BOOTP) server (67)
discard—Discard (9)
dnsix—DNSIX security protocol auditing (195)
domain—Domain Name Service (DNS, 53)
echo—Echo (7)
isakmp—Internet Security Association and Key Management Protocol (5)
mobile-ip—Mobile IP registration (434)
nameserver—IEN116 name service (obsolete, 42)
netbios-dgm—NetBIOS datagram service (138)
netbios-ns—NetBIOS name service (137)
netbios-ss—NetBIOS session service (139)
non500-isakmp—Internet Security Association and Key Management Protocol (45)
ntp—Network Time Protocol (123)
pim-auto-rp—PIM Auto-RP (496)
rip—Routing Information Protocol (router, in.routed, 52)
snmp—Simple Network Management Protocol (161)
snmptrap—SNMP Traps (162)
sunrpc—Sun Remote Procedure Call (111)
syslog—System Logger (514)
tacacs—TAC Access Control System (49)
talk—Talk (517)
tftp—Trivial File Transfer Protocol (69)
time—Time (37)
who—Who service (rwho, 513)
xdmcp—X Display Manager Control Protocol (177)
Examples
This example shows how to configure an IPv4 ACL named acl-lab-01 with rules that deny all TCP and UDP traffic from the 10.23.0.0 and 192.168.37.0 networks to the 10.176.0.0 network and a final rule that permits all other IPv4 traffic:
n1000v# config tn1000v(config)# ip access-list acl-lab-01n1000v(config-acl)# deny tcp 10.23.0.0/16 10.176.0.0/16n1000v(config-acl)# deny udp 10.23.0.0/16 10.176.0.0/16n1000v(config-acl)# deny tcp 192.168.37.0/16 10.176.0.0/16n1000v(config-acl)# deny udp 192.168.37.0/16 10.176.0.0/16n1000v(config-acl)# permit ip any anyRelated Commands
deny (MAC)
To create a MAC access control list (ACL)+ rule that denies traffic matching its conditions, use the deny command. To remove a rule, use the no form of this command.
[sequence-number] deny source destination [protocol] [cos cos-value] [vlan VLAN-ID]
no deny source destination [protocol] [cos cos-value] [vlan VLAN-ID]
no sequence-number
Syntax Description
Defaults
A newly created MAC ACL contains no rules.
If you do not specify a sequence number, the device assigns the rule a sequence number that is 10 greater than the last rule in the ACL.
Command Modes
MAC ACL Configuration (config-mac-acl)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
When the device applies a MAC ACL to a packet, it evaluates the packet with every rule in the ACL. The device enforces the first rule that has conditions that are satisfied by the packet. When the conditions of more than one rule are satisfied, the device enforces the rule with the lowest sequence number.
Source and Destination
You can specify the source and destination arguments in one of two ways. In each rule, the method that you use to specify one of these arguments does not affect how you specify the other argument. When you configure a rule, use the following methods to specify the source and destination arguments:
•
MAC-address MAC-maskThe following example specifies the source argument with the MAC address 00c0.4f03.0a72:
n1000v(config-acl)# deny 00c0.4f03.0a72 0000.0000.0000 anyThe following example specifies the destination argument with a MAC address for all hosts with a MAC vendor code of 00603e:
n1000v(config-acl)# deny any 0060.3e00.0000 0000.0000.0000•
MAC Protocols
The protocol argument can be the MAC protocol number or a keyword. The protocol number is a four-byte hexadecimal number prefixed with 0x. Valid protocol numbers are from 0x0 to 0xffff. Valid keywords are the following:
•
•
•
•
•
•
•
•
•
•
•
•
Examples
This example shows how to configure a MAC ACL named mac-ip-filter with rules that permit any non-IPv4 traffic between two groups of MAC addresses:
n1000v# config tn1000v(config)# mac access-list mac-ip-filtern1000v(config-mac-acl)# deny 00c0.4f00.0000 0000.00ff.ffff 0060.3e00.0000 0000.00ff.ffff ipn1000v(config-mac-acl)# permit any anyRelated Commands
description (interface)
To do add a description for the interface and save it in the running configuration, use the description command. To remove the interface description, use the no form of this command.
description text
no description
Syntax Description
Defaults
None
Command Modes
interface configuration (config-if)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
.
Examples
This example shows how to add the description for the interface and save it in the running configuration.:
n1000v(config-if)# description Ethernet port 3 on module 1This example shows how to remove the interface description.
n1000v(config-if)# no description Ethernet port 3 on module 1Related Commands
description (NetFlow)
To add a description to a flow record, flow monitor, or flow exporter, use the description command. To remove the description, use the no form of this command.
description line
no description
Syntax Description
Defaults
None
Command Modes
NetFlow flow record (config-flow-record)
NetFlow flow exporter (config-flow-exporter)
Netflow flow monitor (config-flow-monitor)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to add a description to a flow record:
n1000v# config tn1000v(config)# flow record RecordTestn1000v(config-flow-record)# description Ipv4flowThis example shows how to add a description to a flow exporter:
n1000v# config tn1000v(config)# flow exporter ExportTestn1000v(config-flow-exporter)# description ExportHamiltonThis example shows how to add a description to a flow monitor:
n1000v# config tn1000v(config)# flow monitor MonitorTestn1000v(config-flow-monitor)# description Ipv4MonitorRelated Commands
description (QoS)
To add a description to a QoS class map, policy map, use the description command. To remove the description, use the no form of this command.
description text
no description text
Syntax Description
Defaults
None
Command Modes
QoS Class Map Configuration (config-cmap-qos)
QoS Policy Map Configuration (config-pmap-qos)Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to add a description to a policy map:
n1000v(config)# policy-map my_policy1n1000v(config-pmap)# description this policy applies to input packetsn1000v(config-pmap)#Related Commands
class-map
Creates or modifies a class map.
policy-map
Creates or modifies a policy map.
description (role)
To add a description for a role, use the description command. To remove a description of a role, use the no form of this command.
description string
no description
Syntax Description
Defaults
None
Command Modes
Role Configuration (config-role)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to add a description to a role:
n1000v(config-role)# description adminThis example shows how to remove the role description:
n1000v(config-role)# no description adminRelated Commands
description (SPAN)
To add a description to a SPAN session, use the description command. To remove the description, use the no form of this command.
description string
no description
Syntax Description
Defaults
Blank (no description)
Command Modes
SPAN Monitor Configuration (config-monitor)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to add a description to a SPAN session:
n1000v# config tn1000v(config)# monitor session 8n1000v(config-monitor)# description span_session_8an1000v(config-monitor)#This example shows how to remove a description from a SPAN session:
n1000v# config tn1000v(config)# monitor session 8n1000v(config)# no description span_session_8an1000v(config-monitor)#Related Commands
destination (NetFlow)
To add a destination IP address or VRF to a NetFlow flow exporter, use the destination command. To remove the IP address or VRF, use the no form of this command.
destination {ipaddr | ipv6addr} [use-vrf vrf_name]
no destination
Syntax Description
ipaddr
Destination IP address for collector.
ipv6addr
Destination IPv6 address for collector.
use-vrf vrf_name
(Optional) Optional VRF label + VRF Label.
Defaults
None
Command Modes
NetFlow Flow Exporter Configuration (config-flow-exporter)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to add a destination IP address to a Netflow flow exporter:
n1000v# config tn1000v(config)# flow exporter ExportTestn1000v(config-flow-exporter)# destination 192.0.2.1This example shows how to remove the IP address from a flow exporter:
n1000v# config tn1000v(config)# flow exporter ExportTestn1000v(config-flow-exporter)# no destination 192.0.2.1Related Commands
destination interface (SPAN)
To configures the port(s) in a SPAN session to act as destination(s) for copied source packets, use the destination interface command. To remove the destination interface, use the no form of this command.
destination interface type number(s)_or_range
no destination interface type number(s)_or_range
Syntax Description
Defaults
None
Command Modes
SPAN Monitor Configuration (config-monitor)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
SPAN destination ports must already be configured as either access or trunk ports.
SPAN sessions are created in the shut state by default.
When you create a SPAN session that already exists, any additional configuration is added to that session. To make sure the session is cleared of any previous configuration, you can delete the session first using the command, no monitor session.
Examples
This example shows how to configure ethernet interfaces 2/5 and 3/7 in a SPAN session to act as destination(s) for copied source packets:
n1000v# config tn1000v(config)# monitor session 8n1000v(config-monitor)# destination interface ethernet 2/5, ethernet 3/7This example shows how to remove the SPAN configuration from destination interface ethernet 2/5:
n1000v# config tn1000v(config)# monitor session 8n1000v(config-monitor)# no destination interface ethernet 2/5Related Commands
dir
To display the contents of a directory or file, use the dir command.
dir [bootflash: | debug: | log: | volatile:]
Syntax Description
Defaults
None
Command Modes
Any
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
Use the pwd command to identify the directory you are currently working in.
Use the cd command to change the directory you are currently working in.
Examples
This example shows how to display the contents of the bootflash: directory
n1000v# dir bootflash:Related Commands
cd
Changes the current working directory.
pwd
Displays the current working directory.
domain id
To assign a domain-id, use the domain id command. To remove a domain-id, use the no form of this command.
domain id number
no domain id
Syntax Description
Defaults
None
Command Modes
Domain Configuration (config-svs-domain)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
During installation of the Cisco Nexus 1000V the setup utility prompts you to configure a domain, including the domain ID and control and packet VLANs.
Examples
This example shows how to assign a domain id:
n1000v# config tn1000v(config)# sve-domainn1000v(config-svs-domain)# domain-id number 32n1000v(config-svs-domain)#This example shows how to remove the domain-id:
n1000v# config tn1000v(config)# sve-domainn1000v(config-svs-domain)# no domain-id number 32n1000v(config-svs-domain)#Related Commands
dscp (NetFlow)
To add a differentiated services codepoint (DSCP) to a NetFlow flow exporter, use the dscp command. To remove the DSCP, use the no form of this command.
dscp value
no dscp
Syntax Description
Defaults
None
Command Modes
Netflow Flow Exporter Configuration (config-flow-exporter)
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Examples
This example shows how to configure DSCP for a Netflow flow exporter:
n1000v# config tn1000v(config)# flow exporter ExportTestn1000v(config-flow-exporter)# dscp 2n1000v(config-flow-exporter)#This example shows how to remove DSCP from the Netflow flow exporter:
n1000v# config tn1000v(config)# flow exporter ExportTestn1000v(config-flow-exporter)# no dscp 2n1000v(config-flow-exporter)#Related Commands