- deadtime
- debug logfile
- debug logging
- default ip arp inspection limit
- default ip arp inspection trust
- default segment distribution mac
- default segment mode unicast-only
- default switchport (port profile)
- default shutdown (port profile)
- default shutdown (interface)
- default switchport port-security (VEthernet)
- default (table map)
- delay
- delete
- deny (IPv4)
- deny (MAC)
- description (interface)
- description (NetFlow)
- description(Network Segmentation Policy)
- description (Port Profile Role)
- description (QoS)
- description (role)
- description (SPAN)
- destination (NetFlow)
- destination interface (SPAN)
- dir
- disable-loop-detection
- domain id
- dscp (NetFlow)
- duplex
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.
Syntax Description
Defaults
Command Modes
RADlUS server group configuration ( config-radius)
TACACS+ server group configuration ( config-tacacs+)
Global configuration ( config)
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:
This example shows how to set a global dead-time interval to 5 minutes for all TACACS+ servers and server groups:
This example shows how to set the dead-time interval to 5 minutes for a TACACS+ server group:
This example shows how to revert to the dead-time interval default:
Related 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
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The logfile is created in the log: file system root directory.
Examples
This example shows how to specify a debug logfile:
This example shows how to revert to the default debug logfile:
Related Commands
|
|
|
|---|---|
debug logging
To enable debug command output logging, use the debug logging command. To disable debug logging, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to enable the output logging for the debug command:
This example shows how to disable the output logging for the debug command:
Related Commands
|
|
|
|---|---|
default ip arp inspection limit
To remove a configured rate limit for dynamic ARP inspection, use the default ip arp inspection limit command. This resets the inspection limit to its defaults.
default ip arp inspection limit { rate [ burst interval ] | none }
Syntax Description
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
Examples
This example shows how to remove a configured rate limit for dynamic ARP inspection from vEthernet interface 3, and reset the rate limit to the default:
n1000v# config t
n1000v( config)# interface vethernet 3
Related Commands
|
|
|
|---|---|
default ip arp inspection trust
To remove a trusted vEthernet interface configuration for dynamic ARP inspection, use the default ip arp inspection trust command. This returns the interface to the default untrusted state.
default ip arp inspection trust
Syntax Description
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
Examples
This example shows how to remove the trusted vEthernet interface configuration for dynamic ARP inspection; and return vEthernet interface 3 to the untrusted state:
n1000v# config t
n1000v( config)# interface vethernet 3
Related Commands
|
|
|
|---|---|
Displays the trust state and ARP packet rate for a specific interface. |
|
Configures a trusted vEthernet interface for dynamic ARP inspection. |
default segment distribution mac
To configure default MAC distribution mode of the bridge-domain. Global Configuration will take effect only on BDs which have default configuration.
default segment distribution mac
Syntax Description
Defaults
Command Modes
bridge-domain configuration (config-bd)
Command History
|
|
|
Usage Guidelines
Global Configuration will take effect only on BDs which have default configuration.
Examples
This example shows how to configure the default MAC distribution mode per bridge-domain:
Related Commands
|
|
|
|---|---|
Configure the default segment mode unicast-only per bridge-domain. |
default segment mode unicast-only
To configure default segment mode of the bridge-domain. Global Configuration will take effect only on BDs which have default configuration.
default segment mode unicast-only
Syntax Description
Defaults
Command Modes
bridge-domain configuration ( config-bd)
Command History
|
|
|
Usage Guidelines
Global Configuration will take effect only on BDs which have default configuration.
Examples
This example shows how to configure the default segment mode unicast-only per bridge-domain:
Related Commands
|
|
|
|---|---|
Configure the default MAC distribution mode per bridge-domain. |
default switchport (port profile)
To remove a particular switchport characteristic 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
Command Modes
Port profile configuration ( config-port-prof)
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:
Examples
This example shows how to revert port profile ports to switch access ports.
n1000v(config-port-prof)# default switchport mode
This example shows how to remove the trunking allowed VLAN characteristics of a port profile.
This example shows how to remove the private VLAN host association of a port profile.
This example shows how to remove port security characteristics of a port profile.
Related Commands
|
|
|
|---|---|
default shutdown (port profile)
To remove a configured administrative state from a port profile, and return its member interfaces to the default state (shutdown), use the default shutdown command.
Syntax Description
Defaults
Command Modes
Port profile configuration ( config- port-prof)
Command History
|
|
|
Examples
This example shows how to change the member interfaces in the port profile named DataProfile to shutdown:
n1000v# config t
n1000v# port-profile DataProfile
n1000v(config-port-prof)# default shutdown
n1000v(config-port-prof)#
Related Commands
|
|
|
|---|---|
default shutdown (interface)
To remove a configured administrative state from an interface, use the default shutdown command.
Syntax Description
Defaults
Command Modes
Interface configuration ( config- if)
Command History
|
|
|
Usage Guidelines
When you use the default shutdown command on a port profile member interface, it also allows the port profile configuration to take affect.
Examples
This example shows how to change interface Ethernet 3/2 to shutdown:
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
Defaults
Command Modes
Interface configuration ( config-if)
Command History
|
|
|
Examples
This example shows how to disable port security n1000von VEthernet 2:
Related Commands
|
|
|
|---|---|
default (table map)
To specify the default action for mapping input field values to output field values in a table map, use the default command.
Syntax Description
Default value to use for the output value in the range from 0 to 63. |
|
Specifies that the default action is to copy all equal values to an equal output value. |
Defaults
Command Modes
Table map configuration (config-tmap)
Default table map configuration
Command History
|
|
|
Usage Guidelines
The copy keyword is available only in the table map configuration mode. In the default table map configuration mode, the copy keyword is not available because all values must be assigned a mapping.
Examples
This example shows how to remove the default mapping action copy. The resulting default action is ignore:
n1000v(config)# table-map my_table1
Related Commands
|
|
|
|---|---|
Specifies input field to output field mappings in table maps. |
|
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.
Syntax Description
Specifies the throughput delay time in tens of microseconds. |
Defaults
Command Modes
Interface configuration (config-if)
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:
This example shows how to remove the delay time configuration:
no delay 10000
Related Commands
|
|
|
|---|---|
delete
To delete a file, use the delete command.
delete [ filesystem : [ // directory / ] | directory / ] filename
Syntax Description
(Optional) Name of the file system. Valid values are bootflash or volatile. |
|
(Optional) Name of the directory. The directory name is case sensitive. |
|
Defaults
Command Modes
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:
Related 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.
[ sequence-number ] deny protocol source destination [ dscp dscp | precedence precedence ]
no deny protocol source destination [ dscp dscp | precedence precedence ]
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 ]
[ sequence-number ] deny ip source destination [ dscp dscp | precedence precedence ]
[ 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 ]
[ sequence-number ] deny udp source operator port [ port ] destination [ operator port [ port ] [ dscp dscp | precedence precedence ]
Syntax Description
dscp
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)
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.
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:
- Address and network wildcard—You can use an IPv4 address followed by a network wildcard to specify a host or a network as a source or destination. The syntax is as follows:
The following example shows how to specify the source argument with the IPv4 address and network wildcard for the 192.168.67.0 subnet:
- Address and variable-length subnet mask—You can use an IPv4 address followed by a variable-length subnet mask (VLSM) to specify a host or a network as a source or destination. The syntax is as follows:
The following example shows how to specify the source argument with the IPv4 address and VLSM for the 192.168.67.0 subnet:
- Host address—You can use the host keyword and an IPv4 address to specify a host as a source or destination. The syntax is as follows:
This 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:
- Any address—You can use the any keyword to specify that a source or destination is any IPv4 address. For examples of the use of the any keyword, see the examples in this section. Each example shows how to specify a source or destination by using the any keyword.
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:
- administratively-prohibited —Administratively prohibited
- alternate-address —Alternate address
- conversion-error —Datagram conversion
- dod-host-prohibited —Host prohibited
- dod-net-prohibited —Net prohibited
- echo —Echo (ping)
- echo-reply —Echo reply
- general-parameter-problem —Parameter problem
- host-isolated —Host isolated
- host-precedence-unreachable —Host unreachable for precedence
- host-redirect —Host redirect
- host-tos-redirect —Host redirect for ToS
- host-tos-unreachable —Host unreachable for ToS
- host-unknown —Host unknown
- host-unreachable —Host unreachable
- information-reply —Information replies
- information-request —Information requests
- mask-reply —Mask replies
- mask-request —Mask requests
- mobile-redirect —Mobile host redirect
- net-redirect —Network redirect
- net-tos-redirect —Net redirect for ToS
- net-tos-unreachable —Network unreachable for ToS
- net-unreachable —Net unreachable
- network-unknown —Network unknown
- no-room-for-option —Parameter required but no room
- option-missing —Parameter required but not present
- packet-too-big —Fragmentation needed and DF set
- parameter-problem —All parameter problems
- port-unreachable —Port unreachable
- precedence-unreachable —Precedence cutoff
- protocol-unreachable —Protocol unreachable
- reassembly-timeout —Reassembly timeout
- redirect —All redirects
- router-advertisement —Router discovery advertisements
- router-solicitation —Router discovery solicitations
- source-quench —Source quenches
- source-route-failed —Source route failed
- time-exceeded —All time-exceeded messages
- timestamp-reply —Time-stamp replies
- timestamp-request —Time-stamp requests
- traceroute —Traceroute
- ttl-exceeded —TTL exceeded
- unreachable —All unreachables
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)
domain —Domain Name Service (53)
drip —Dynamic Routing Information Protocol (3949)
ftp —File Transfer Protocol (21)
ftp-data —FTP data connections (2)
hostname —NIC hostname server (11)
irc —Internet Relay Chat (194)
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)
uucp —UNIX-to-UNIX Copy Program (54)
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)
dnsix —DNSIX security protocol auditing (195)
domain —Domain Name Service (DNS, 53)
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)
sunrpc —Sun Remote Procedure Call (111)
tacacs —TAC Access Control System (49)
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:
Related 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 ]
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)
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.
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:
- Address and mask—You can use a MAC address followed by a mask to specify a single address or a group of addresses. The syntax is as follows:
The following example specifies the source argument with the MAC address 00c0.4f03.0a72:
The following example specifies the destination argument with a MAC address for all hosts with a MAC vendor code of 00603e:
- Any address—You can use the any keyword to specify that a source or destination is any MAC address. For examples of the use of the any keyword, see the examples in this section. Each of the examples shows how to specify a source or destination by using the any keyword.
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:
- aarp —Appletalk ARP (0x80f3)
- appletalk —Appletalk (0x809b)
- decnet-iv —DECnet Phase IV (0x6003)
- diagnostic —DEC Diagnostic Protocol (0x6005)
- etype-6000 —EtherType 0x6000 (0x6000)
- etype-8042 —EtherType 0x8042 (0x8042)
- ip —Internet Protocol v4 (0x0800)
- lat —DEC LAT (0x6004)
- lavc-sca —DEC LAVC, SCA (0x6007)
- mop-console —DEC MOP Remote console (0x6002)
- mop-dump —DEC MOP dump (0x6001)
- vines-echo —VINES Echo (0x0baf)
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:
Related 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.
Syntax Description
Describes the interface. The maximum number of characters is 80. |
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
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 1
This example shows how to remove the interface description.
n1000v(config-if)# no description Ethernet port 3 on module 1
Related 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.
Syntax Description
Defaults
Command Modes
NetFlow flow record (config-flow-record)
NetFlow flow exporter (config-flow-exporter)
Netflow flow monitor (config-flow-monitor)
Command History
|
|
|
Examples
This example shows how to add a description to a flow record:
This example shows how to add a description to a flow exporter:
This example shows how to add a description to a flow monitor:
Related Commands
|
|
|
|---|---|
description(Network Segmentation Policy)
To add a description to the network segmentation policy, use the description command. To remove the description, use the no form of this command.
no description [ description ]
Syntax Description
The description of the network segmentation policy. The description can be up to 80 ASCII characters. |
Defaults
Command Modes
Network Segment Policy configuration (config-network-segment-policy)
Command History
|
|
|
Examples
This example shows how to add a description to the network segmentation policy:
Related Commands
|
|
|
|---|---|
description (Port Profile Role)
To add a description to a port profile role, use the description command. To remove the description, use the no form of this command.
Syntax Description
Defaults
Command Modes
Port profile role configuration (config-port-profile-role)
Command History
|
|
|
Examples
This example shows how to add a description to a role:
n1000v# config t
n1000v(config-port-profile-role)# description adminOnly
This example shows how to remove the role description:
n1000v# config t
n1000v(config-role)# no description
Related Commands
description (QoS)
To add a description to a QoS class map, policy map, or table map use the description command. To remove the description, use the no form of this command.
Syntax Description
Description, of up to 200 characters, for the class map or policy map. |
Defaults
Command Modes
QoS class map configuration ( config-cmap-qo s)
QoS table map configuration ( config-tmap-qo s)
QoS policy map configuration ( config-pmap-qos)
Command History
|
|
|
Examples
This example shows how to add a description to a policy map:
n1000v(config)# policy-map my_policy1
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Defaults
Command Modes
Role configuration ( config-role)
Command History
|
|
|
Examples
This example shows how to add a description to a role:
n1000v(config-role)# description admin
This example shows how to remove the role description:
n1000v(config-role)# no description admin
Related 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.
Syntax Description
Specifies a description of up to 32 alphanumeric characters. |
Defaults
Command Modes
SPAN monitor configuration (config-monitor)
Command History
|
|
|
Examples
This example shows how to add a description to a SPAN session:
n1000v# config t
n1000v(config)# monitor session 8
n1000v(config-monitor)# description span_session_8a
n1000v(config-monitor)#
This example shows how to remove a description from a SPAN session:
n1000v# config t
n1000v(config)# monitor session 8
n1000v(config)# no description span_session_8a
n1000v(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 ]
Syntax Description
Defaults
Command Modes
NetFlow flow exporter configuration (config-flow-exporter)
Command History
|
|
|
Examples
This example shows how to add a destination IP address to a Netflow flow exporter:
This example shows how to remove the IP address from a flow exporter:
Related 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
Designates the SPAN destination(s) virtual Ethernet interface(s). |
Defaults
Command Modes
SPAN monitor configuration ( config-monitor)
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 t
n1000v(config)# monitor session 8
n1000v(config-monitor)# destination interface ethernet 2/5, ethernet 3/7
This example shows how to remove the SPAN configuration from destination interface ethernet 2/5:
n1000v# config t
n1000v(config)# monitor session 8
n1000v(config-monitor)# no destination interface ethernet 2/5
Related Commands
|
|
|
|---|---|
Displays the interface trunking configuration for the specified destination interface. |
|
dir
To display the contents of a directory or file, use the dir command.
dir [ bootflash: | debug: | log: | volatile:]
Syntax Description
Defaults
Command Modes
Command 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
|
|
|
|---|---|
disable-loop-detection
To disable the loop detection mechanism to support a redundant routing protocol, use the disable-loop-detection command. To enable the loop detection mechanism, use the no form of this command.
disable-loop-detection {carp|hsrp| vrrp| custom-rp {[ src-mac-range mac_range_start mac_range_end ] [ dest-ip dest_ip ] [ ip-proto proto_no ] [ port port_no ]} }
no disable-loop-detection {carp|hsrp| vrrp|custom-rp {[ src-mac-range mac_range_start mac_range_end ] [ dest-ip dest_ip ] [ ip-proto proto_no ] [ port port_no ]} }
Syntax Description
Defaults
Command Modes
Interface configuration (config-if)
Port profile configuration (config-port-prof)
Command History
|
|
|
Usage Guidelines
- If you configure a vEthernet Interface and a port profile to run multiple protocols on the same virtual machine, then the configuration on the vEthernet Interface overrides the configuration on the port profile.
- Disable IGMP Snooping on both Cisco Nexus 1000 and upstream switches between the servers to support most redundant routing protocols.
- Disable loop detection configuration is not supported on PVLAN ports.
- Disable loop detection configuration is not supported on the port security ports.
Examples
This example shows how to disable loop detection for redundant routing protocols:
Related Commands
|
|
|
|---|---|
domain id
To assign a domain-id, use the domain id command. To remove a domain-id, use the no form of this command.
Syntax Description
Specifies the domain-id number. The allowable domain IDs are 1 to 4095. |
Defaults
Command Modes
Domain configuration (config-svs-domain)
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 t
n1000v(config)# sve-domain
n1000v(config-svs-domain)# domain-id number 32
n1000v(config-svs-domain)#
This example shows how to remove the domain-id:
n1000v# config t
n1000v(config)# sve-domain
n1000v(config-svs-domain)# no domain-id number 32
n1000v(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.
Syntax Description
Defaults
Command Modes
NetFlow flow exporter configuration (config-flow-exporter)
Command History
|
|
|
Examples
This example shows how to configure DSCP for a NetFlow flow exporter:
n1000v# config t
This example shows how to remove DSCP from the NetFlow flow exporter:
n1000v# config t
Related Commands
|
|
|
|---|---|
duplex
To set the duplex mode for an interface as full, half, or autonegotiate, use the duplex command. To revert back to the default setting, use the no form of this command.
no duplex [ full | half | auto ]
Syntax Description
Sets the duplex mode on the interface to autonegotiate with the connecting port. |
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
Usage Guidelines
When you use the no version of this command, an argument (such as full, half, or auto) is optional. To return to the default duplex setting, you can use either of the following commands (if, for example, the setting had been changed to full):
Examples
This example shows how to set the Ethernet port 1 on the module in slot 3 to full-duplex mode:
This example shows how to revert to the default duplex setting for the Ethernet port 1 on the module in slot 3:
Related Commands
|
|
|
|---|---|
Displays the interface status, which includes the speed and duplex mode parameters. |
Feedback