Table Of Contents
Configuring Basic Interface Parameters
Information About the Basic Interface Parameters
Unidirectional Link Detection Parameter
UDLD Aggressive and Nonaggressive Modes
Prerequisites for Configuring the Basic Interface Parameters
Configuring the Basic Interface Parameters
Specifying the Interfaces to Configure
Changing the Bandwidth-Rate Mode
Dedicating Bandwidth to One Port
Sharing the Bandwidth Among a Port Group
Enabling the Error Disable Detection
Enabling the Error Disable Recovery
Enabling the Error Recovery Interval
Configuring the MDIX Parameter
Configuring the Debounce Timer
Configuring the Interface Speed and Duplex Mode
Configuring the Interface MTU Size
Configuring the System Jumbo MTU Size
Configuring the Throughput Delay
Shutting Down and Activating the Interface
Configuring the Carrier Delay Timer
Verifying the Basic Interface Parameters
Clearing the Interface Counters
Feature History for Configuring Basic Interface Parameters
Configuring Basic Interface Parameters
This chapter describes how to configure the basic interface parameters. These parameters are shared by multiple interfaces.
This chapter includes the following sections:
•
Information About the Basic Interface Parameters
•
•
•
•
•
Note
Information About the Basic Interface Parameters
This section includes the following topics:
•
•
Description
For the Ethernet and management interfaces, you can configure the description parameter to provide a recognizable name for the interface. Using a unique name for each interface allows you to quickly identify the interface when you are looking at a listing of multiple interfaces.
For information on setting the description parameter for port-channel interfaces, see the "Configuring a Port-Channel Description" section on page 5-21. For information on configuring this parameter for other interfaces, see the "Configuring the Description" section.
Beacon
The beacon mode allows you to identify a physical port by flashing its link state LED with a green light. By default, this mode is disabled. To identify the physical port for an interface, you can activate the beacon parameter for the interface.
For information on configuring the beacon parameter, see the "Configuring the Beacon Mode" section.
MDIX
The medium dependent interface crossover (MDIX) parameter enables or disables the detection of a crossover connection between devices. This parameter applies only to copper interfaces. By default, this parameter is enabled.
For information on configuring the MDIX parameter, see the "Verifying the Basic Interface Parameters" section.
Debounce Timer
The debounce timer delays notification of a link change, which can decrease traffic loss due to network reconfiguration. You can configure the debounce timer separately for each Ethernet port and specify the delay time in milliseconds. By default, this parameter is set for 100 milliseconds.
Caution
For information on configuring the debounce-timer parameters, see the "Configuring the Debounce Timer" section.
Error Disabled
A port is in the err-disabled state if it is enabled administratively (using the no shutdown command) but disabled at runtime by any process. For example, if UDLD detects a uni-directional link, the port is shutdown at runtime. However, since the port is administratively enabled, the port status is shown as err-disable. Once a port goes into the err-disable state, it has to be manually re-enabled or a timeout can be configured to provide auto recovery. By default, the auto recovery is not configured, and by default the err-disable detection is enabled for all the causes.
When an interface is in the err-disabled state, the err-disable detection commands is used to find the nature of the error. The err-disable recovery interval command provides auto recovery after a timeout. The default value for the timeout is 300 seconds, and it can range between 30 to 86400 seconds. The recovery timeout can also be configured for a particular err-disable cause.
If the err-disable recovery is not enabled for the cause, the interface stays in the err-disabled state until a shutdown and no shutdown occurs. If the recovery is enabled for a cause, the interface is brought out of the error-disabled state and allowed to retry operation once all the causes have timed out.The show interface status command also lists the reason behind the error.
Rate Mode
On a 32-port 10 GE Ethernet module, each set of four ports can handle 10 gigabits per second (Gb/s) of bandwidth. You can use the rate-mode parameter to dedicate that bandwidth to the first port in the set of four ports or share the bandwidth across all four ports.
Table 2-1 identifies the ports that are grouped together to share each 10 Gb/s of bandwidth and which port in the group can be dedicated to utilize the entire bandwidth.
Note
Speed Mode and Duplex Mode
The speed mode and duplex mode are interrelated for each Ethernet and management interface. By default, each of these interfaces autonegotiates its speed and duplex mode with the other interface, but you can change these settings. If you change the settings, be sure to use the same speed and duplex mode setting on both interfaces, or use autonegotiation for at least one of the interfaces. Table 2-2 shows the settings that work for each type of Ethernet and management interface.
Table 2-2 Speed- and Duplex-Mode Settings Used for Ethernet and Management Interfaces
32-port 10 GE Ethernet
Auto1
Auto1
10,000
Full
48-port 10/100/1000 Ethernet
Auto1
Auto1
1000
Full
10 or 100
Half
1000
Auto1 or full
1000
Full
100
Auto1 or half
100
Half
Full
100
Full
10
Auto1 or half
10
Half
Full
10
Full
Management
Auto1
Auto1
1000
Full
10 or 100
Half
1000
Auto1 or full
1000
Full
100
Auto1 or half
100
Half
Full
100
Full
10
Auto1 or half
10
Half
Full
10
Full
1 Default setting
For information on setting the speed mode and duplex mode for port-channel interfaces, see the "Configuring the Speed and Duplex Settings for a Port-Channel Interface" section on page 5-22. For information on setting the speed and duplex speed for other interfaces, see the "Configuring the Interface Speed and Duplex Mode" section.
Flow Control
When the receive buffer for an Ethernet port that runs 1 Gbps or faster fills, flow control enables that port to send an IEEE 802.3x pause frame to the transmitting port to request it to stop transmitting data for a specified amount of time. Transmitting ports, running at any speed, can receive the pause frames to stop their transmission of data.
To allow flow control to work between two ports, you must set the corresponding receive and send flow control parameters for both ports as enabled or desired. When you set the parameter to enabled, the send or receive flow-control function is activated regardless of the setting of the other port. When you set the parameter to desired, the send or receive flow-control function is activated if you set the corresponding flow-control state of the other port to enabled or desired. If you set one of the flow control states to disabled, flow control is disabled for that transmission direction. To see how the different port flow-control states affect the link flow-control state, see Table 2-3.
For information on setting the flow-control parameters, see the "Configuring the Flow Control" section.
Port MTU Size
The maximum transmission unit (MTU) size specifies the maximum frame size that an Ethernet port can process. For transmissions to occur between two ports, you must configure the same MTU size for both ports. A port drops any frames that exceed its MTU size.
By default, each port has an MTU of 1500 bytes, which is the IEEE 802.3 standard for Ethernet frames. Larger MTU sizes are possible for more efficient processing of data with less overhead. The larger frames, called jumbo frames, can be up to 9216 bytes in size, which is also the default system jumbo MTU size.
On a Layer 3 interface, you can configure an MTU size between 576 and 9216 bytes. You can configure up to 64 MTU settings for each I/O module.
Note
For a Layer 2 port, you can configure an MTU size that is either the system default (1500 bytes) or the system jumbo MTU size (initially 9216 bytes).
Note
For information on setting the MTU size, see the "Configuring the MTU Size" section.
Bandwidth
Ethernet ports have a fixed bandwidth of 1,000,000 Kb at the physical level. Layer 3 protocols use a bandwidth value that you can set for calculating their internal metrics. The value that you set is used for informational purposes only by the Layer 3 protocols—it does not change the fixed bandwidth at the physical level. For example, the Interior Gateway Routing Protocol (IGRP) uses the minimum path bandwidth to determine a routing metric, but the bandwidth at the physical level remains 1,000,000 Kb.
For information on configuring the bandwidth parameter for port-channel interfaces, see the "Configuring the Bandwidth and Delay for Informational Purposes" section on page 5-18. For information on configuring the bandwidth parameter for other interfaces, see the "Configuring the Bandwidth" section.
Throughput Delay
Specifying a value for the throughput-delay parameter provides a value used by Layer 3 protocols; it does not change the actual throughput delay of an interface. The Layer 3 protocols can use this value to make operating decisions. For example, the IGRP can use the delay setting to differentiate between a satellite link and a land link. The delay value that you set is in the tens of microseconds.
For information on configuring the bandwidth parameter for port-channel interfaces, see the "Configuring the Bandwidth and Delay for Informational Purposes" section on page 5-18. For information on configuring the throughput-delay parameter for other interfaces, see the "Configuring the Throughput Delay" section.
Administrative Status
The administrative-status parameter determines whether an interface is up or down. When an interface is administratively down, it is disabled and unable to transmit data. When an interface is administratively up, it is enabled and able to transmit data.
For information on configuring the administrative status parameter for port channel interfaces, see the "Shutting Down and Restarting the Port-Channel Interface" section on page 5-19. For information on configuring the administrative-status parameter for other interfaces, see the "Shutting Down and Activating the Interface" section.
Unidirectional Link Detection Parameter
This section includes the following topics:
•
UDLD Overview
The Cisco-proprietary Unidirectional Link Detection (UDLD) protocol allows devices that are connected through fiber-optic or copper (for example, Category 5 cabling) Ethernet cables to monitor the physical configuration of the cables and detect when a unidirectional link exists. When a device detects a unidirectional link, UDLD shuts down the affected LAN port and alerts the user. Unidirectional links can cause a variety of problems, including spanning tree topology loops.
UDLD is a Layer 2 protocol that works with the Layer 1 protocols to determine the physical status of a link. At Layer 1, autonegotiation takes care of physical signaling and fault detection. UDLD performs tasks that autonegotiation cannot perform, such as detecting the identities of neighbors and shutting down misconnected LAN ports. When you enable both autonegotiation and UDLD, Layer 1 and Layer 2 detections work together to prevent physical and logical unidirectional connections and the malfunctioning of other protocols.
A unidirectional link occurs whenever traffic transmitted by the local device over a link is received by the neighbor but traffic transmitted from the neighbor is not received by the local device. If one of the fiber strands in a pair is disconnected, as long as autonegotiation is active, the link does not stay up. In this case, the logical link is undetermined, and UDLD does not take any action. If both fibers are working normally at Layer 1, then UDLD at Layer 2 determines whether those fibers are connected correctly and whether traffic is flowing bidirectionally between the correct neighbors. This check cannot be performed by autonegotiation, because autonegotiation operates at Layer 1.
The Nexus 7000 Series device periodically transmits UDLD frames to neighbor devices on LAN ports with UDLD enabled. If the frames are echoed back within a specific time frame and they lack a specific acknowledgment (echo), the link is flagged as unidirectional and the LAN port is shut down. Devices on both ends of the link must support UDLD in order for the protocol to successfully identify and disable unidirectional links.
Note
Figure 2-1 shows an example of a unidirectional link condition. Device B successfully receives traffic from device A on the port. However, device A does not receive traffic from device B on the same port. UDLD detects the problem and disables the port.
Figure 2-1 Unidirectional Link
Default UDLD Configuration
Table 2-4 shows the default UDLD configuration.
For information on configuring the UDLD for the device and its port, see the "Configuring the UDLD Mode" section.
UDLD Aggressive and Nonaggressive Modes
UDLD aggressive mode is disabled by default. You can configure UDLD aggressive mode only on point-to-point links between network devices that support UDLD aggressive mode. If UDLD aggressive mode is enabled, when a port on a bidirectional link that has a UDLD neighbor relationship established stops receiving UDLD frame, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is disabled.
To prevent spanning tree loops, nonaggressive UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to the forwarding state (with default spanning tree parameters).
When you enable the UDLD aggressive mode, the following occurs:
•
•
In these cases, the UDLD aggressive mode disables one of the ports on the link, which prevents traffic from being discarded.
Carrier Delay
In Cisco NX-OS 4.0(3) and later releases, you can configure the carrier delay timer.
Note
If a link goes down and comes back up before the carrier delay timer expires, the down state is effectively filtered, and the rest of the software on the device is not aware that a link-down event occurred. A large carrier delay timer results in fewer link-up/link-down events being detected. When you set the carrier delay time to 0, the device detects each link-up/link-down event that occurs.
In most environments, a lower carrier delay time is better than a higher one. The exact value that you choose depends on the nature of the link outages and how long you expect these linkages to last in your network. If your data links are subject to short outages (especially if those outages last less time than it takes for your IP routing to converge) you should set a long carrier delay value to prevent these short outages from causing unnecessary churn in your routing tables. However, if you outages tend to be longer, then you may want to set a shorter carrier delay time so that the outages are detected sooner, and the IP route convergence begins and ends sooner.
The default carrier-delay time is 2 seconds or 50 milliseconds.
Port Channel Parameters
A port channel is an aggregation of physical interfaces that comprise a logical interface. You can bundle up to eight individual interfaces into a port channel to provide increased bandwidth and redundancy. Port channeling also load balances traffic across these physical interfaces. The port channel stays operational if at least one physical interface within the port channel is operational.
You can create a Layer 2 port channel by bundling compatible Layer 2 interfaces, or you can create Layer 3 port channels by bundling compatible Layer 3 interfaces. You cannot combine Layer 2 and Layer 3 interfaces in the same port channel.
Any configuration changes that you apply to the port channel are applied to each interface member of that port channel.
For information on port channels and for information on configuring port channels, see Chapter 5, "Configuring Port Channels."
Licensing Requirements
The interface command and its sub commands do not require licenses.
Prerequisites for Configuring the Basic Interface Parameters
Before you begin configuring the basic interface parameters, make sure that you are in the correct VDC. To change the VDC, use the switch to vdc command.
Guidelines and Limitations
Follow these guidelines and limitations for configuring the basic interface parameters:
•
•
By default, each port is a Layer 3 interface.
You can change a Layer 3 interface into a Layer 2 interface by using the switchport command. Conversely, you can change a Layer 2 interface into a Layer 3 interface by using the no switchport command.
•
–
–
–
–
–
–
•
–
–
–
–
Note
Caution
Configuring the Basic Interface Parameters
When you configure an interface, you must specify the interface before you can configure its parameters.
The following sections explain how to specify the interface and configure each of its basic parameters:
•
•
•
•
•
•
•
•
Specifying the Interfaces to Configure
Before you can configure the parameters for one or more interfaces of the same type, you must specify the type and the identities of the interfaces. Table 2-5 shows the interface types and identities that you should use for specifying the Ethernet and management interfaces.
Table 2-5 Information Needed to Identify an Interface for Configurations
Ethernet
I/O module slot numbers and port numbers on the module.
Management
0 (for port 0)
The interface range configuration mode allows you to configure multiple interfaces with the same configuration parameters. After you enter the interface range configuration mode, all command parameters you enter are attributed to all interfaces within that range until you exit out of the interface range configuration mode.
You enter a range of interfaces using dashes (-) and commas (,). Dashes separate contiguous interfaces and commas separate noncontiguous interfaces.
The following example shows how to configure an interface range:
switch(config)# interface ethernet 2/29-30
switch(config-if-range)#
To verify the current configuration of interfaces, you can display their properties.
Use the show interface command along with a specification of the interface type and identities.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Note
When you are in the interface configuration mode, the commands that you enter configure the interface that you specified for this mode. The following sections explain which commands to use to configure the basic parameters.
Configuring the Description
You can provide textual interface descriptions for the Ethernet and management interfaces. Descriptions can be a maximum of 80 case-sensitive alphanumeric characters.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
To provide and interface description for Ethernet and management interfaces, follow these steps:
This example shows how to set the interface description to Ethernet port 24 on module 3.
switch# config tswitch(config)# interface ethernet 3/24switch(config-if)# description server1switch(config-if)#Configuring the Beacon Mode
You can enable the beacon mode for an Ethernet port to flash its LED to confirm its physical location.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to enable the beacon mode for the Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# beaconswitch(config-if)#This example shows how to disable the beacon mode for the Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# no beaconswitch(config-if)#Changing the Bandwidth-Rate Mode
You can specify whether each 10 Gb of bandwidth on a 32-port 10 GE Ethernet module is dedicated to one port or shared by four ports in the same port group.
This section includes the following topics:
•
•
Dedicating Bandwidth to One Port
When you dedicate the bandwidth to one port, you must first administratively shut down the four ports in the group, change the rate mode to dedicated, and then bring the dedicated port administratively up.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
This example shows how to configure the dedicated mode for Ethernet port 4/17 in the group that includes ports 4/17, 4/19, 4/21, and 4/23:
switch# config tswitch(config)# interface ethernet 4/17, ethernet 4/19, ethernet 4/21, ethernet 4/23switch(config-if)# shutdownswitch(config-if)# interface ethernet 4/17switch(config-if)# rate-mode dedicatedswitch(config-if)# no shutdownswitch(config-if)#Sharing the Bandwidth Among a Port Group
You can share 10 Gb of bandwidth among a group of ports (four ports) on a 32-port 10 Gb Ethernet module. To share the bandwidth, you must bring the dedicated port administratively down, specify the ports that are to share the bandwidth, change the rate mode to shared, and then bring the ports administratively up.
BEFORE YOU BEGIN
All ports in the same group must belong to the same VDC.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
This example shows how to configure the shared mode for Ethernet port 4/17 in the group that includes ports 4/17, 4/19, 4/21, and 4/23:
switch# config tswitch(config)# interface ethernet 4/17switch(config-if)# shutdownswitch(config)# interface ethernet 4/17, ethernet 4/19, ethernet 4/21, ethernet 4/23switch(config-if)# rate-mode sharedswitch(config-if)# no shutdownswitch(config-if)#Enabling the Error Disable Detection
You can enable error disable detection in an application. As a result, when a cause is detected on an interface, the interface is placed in an error-disabled state. This is an operational state that is similar to the link-down state.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
This example shows how to enable the error disable detection in all cases:
switch(config)# errdisable detect cause all
switch(config)#
Enabling the Error Disable Recovery
Enables the application to bring the interface out of the error-disabled state and retry operation once all the causes have timed out.
SUMMARY STEPS
1.
2.
DETAILED STEPS
This example shows how to enable error disable recovery:
switch(config)# errdisable recovery cause all
switch(config)#
Enabling the Error Recovery Interval
You can enable the error disable recovery timer value.
BEFORE YOU BEGIN
SUMMARY STEPS
1.
2.
DETAILED STEPS
This example shows how to enable the error disable recovery timer:
switch(config)# errdisable recovery interval 32switch(config)#Configuring the MDIX Parameter
If you need to detect the type of connection (crossover or straight) with another copper Ethernet port, enable the medium dependent independent crossover (MDIX) parameter for the local port. By default, this parameter is enabled.
BEFORE YOU BEGIN
MDIX must be enabled for the remote port.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to enable MDIX for Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# mdix autoswitch(config-if)#
This example shows how to disable MDIX for Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# no mdixswitch(config-if)#Configuring the Debounce Timer
You can enable the debounce timer for Ethernet ports by specifying a debounce time, in milliseconds (ms), or disable the timer by specifying a debounce time of 0.
You can show the debounce times for all of the Ethernet ports by using the show interface debounce command.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to enable the debounce timer and set the debounce time to 1000 ms for the Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# link debounce time 1000switch(config-if)#This example shows how to disable the debounce timer for the Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# link debounce time 0switch(config-if)#Configuring the Interface Speed and Duplex Mode
The interface speed and duplex mode are interrelated, so you should configure both of their parameters at the same time.
To see which speeds and duplex modes you can configure together for Ethernet and management interfaces, see Table 2-2.
Note
BEFORE YOU BEGIN
Make sure that the remote port has a speed setting that supports your changes for the local port. If you want to set the local port to use a specific speed, you must set the remote port for the same speed or set the local port to autonegotiate the speed.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
This example shows how to set the speed of Ethernet port 1 on the 48-port 10/100/1000 module in slot 3 to 1000 Mbps and full-duplex mode:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# speed 1000switch(config-if)# duplex fullswitch(config-if)#Configuring the Flow Control
For Ethernet ports that run at 1 Gbps or faster, you can enable or disable the port's ability to send and receive flow-control pause frames. For Ethernet ports that run slower than 1 Gbps, you can enable or disable only the port's ability to receive pause frames.
When enabling flow control for the local port, you either fully enable the local port to send or receive frames regardless of the flow-control setting of the remote port, or you set the local port to use the desired setting used by the remote port. If you enable both the local and remote port for flow control, or set the desired flow control of the other port, or set a combination of those two states, flow control is enabled for those ports.
Note
BEFORE YOU BEGIN
Make sure that the remote port has the corresponding setting for the flow control that you need. If you want the local port to send flow-control pause frames, the remote port has a receive parameter set to on or desired. If you want the local port to receive flow-control frames, you must make sure that the remote port has a send parameter set to on or desired. If you do not want to use flow control, you can set the remote port's send and receive parameters to off.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
This example shows how to set Ethernet port 3/1 to send flow control pause frames:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# flowcontrol send onswitch(config-if)#Configuring the MTU Size
You can configure the maximum transmission unit (MTU) size for Layer 2 and Layer 3 Ethernet interfaces. For Layer 3 interfaces, you can configure the MTU to be between 576 and 9216 bytes (even values are required). For Layer 2 interfaces, you can configure the MTU to be either the system default MTU (1500 bytes) or the system jumbo MTU size (which has the default size of 9216 bytes).
Note
By default, DCNM configures Layer 3 parameters. If you want to configure Layer 2 parameters, you need to switch the port mode to Layer 2. You can change the port mode by using the switchport command.
After changing the port mode to Layer 2, you can return to configuring Layer 3 interfaces by changing the port mode again, by using the no switchport command.
This section includes the following topics:
•
•
Configuring the Interface MTU Size
For Layer 3 interfaces, you can configure an MTU size that is between 576 and 9216 bytes.
For Layer 2 interfaces, you can configure all Layer 2 interfaces to use either the default MTU size (1500 bytes) or the system jumbo MTU size (default size of 9216 bytes).
If you need to use a different system jumbo MTU size for Layer 2 interfaces, see the "Configuring the System Jumbo MTU Size" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
This example shows how to configure the Layer 2 Ethernet port 3/1 with the default MTU size (1500).
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# switchportswitch(config-if)# mtu 1500switch(config-if)#Configuring the System Jumbo MTU Size
You can configure the system jumbo MTU size, which can be used to specify the MTU size for Layer 2 interfaces. You can specify an even number between 1500 and 9216. If you do not configure the system jumbo MTU size, it defaults to 1500 bytes.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
To configure the system jumbo MTU size, follow these steps:
This example shows how to configure the system jumbo MTU as 8000 bytes and how to change the MTU specification for an interface that was configured with the previous jumbo MTU size:
switch# config tswitch(config)# system jumbomtu 8000switch(config)# show running-configswitch(config)# interface ethernet 2/2switch(config-if)# switchportswitch(config-if)# mtu 8000switch(config-if)#Configuring the Bandwidth
You can configure the bandwidth for Ethernet interfaces. The physical level uses an unchangeable bandwidth of 1 GB, but you can configure a value of 1 to 10,000,000 Kb for Level 3 protocols.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to configure an informational value of 1,000,000 Kb for the Ethernet slot 3 port 1 interface bandwidth parameter:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# bandwidth 1000000switch(config-if)#Configuring the Throughput Delay
You can configure the interface throughput delay for Ethernet interfaces. The actual delay time does not change, but you can set an informational value between 1 and 16777215, where the value represents the number of tens of microseconds.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to configure the throughput-delay time to 100,000 microseconds for the slot 3 port 1 Ethernet interface:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# delay 10000switch(config-if)#Shutting Down and Activating the Interface
You can shut down and restart Ethernet or management interfaces. When you shut down interfaces, they become disabled and all monitoring displays show them as being down. This information is communicated to other network servers through all dynamic routing protocols. When the interfaces are shut down, the interface is not included in any routing updates. To activate the interface, you must restart the device.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
This example shows how to change the administrative status for Ethernet port 3/1 from disabled to enabled:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if)# shutdownswitch(config-if)# no shutdownswitch(config-if)#Configuring the UDLD Mode
You can configure normal or aggressive unidirectional link detection (UDLD) modes for Ethernet interfaces on devices configured to run UDLD. Before you can enable a UDLD mode for an interface, you must make sure that UDLD is already enabled on the device that includes the interface. UDLD must also be enabled on the other linked interface and its device.
To use the normal UDLD mode, you must configure one of the ports for normal mode and configure the other port for the normal or aggressive mode. To use the aggressive UDLD mode, you must configure both ports for the aggressive mode.
By default, UDLD is disabled for the 48-port, 10/100/1000 Ethernet module ports but the normal UDLD mode is enabled for the 32-port, 10 gigabit Ethernet module ports.
BEFORE YOU BEGIN
UDLD must be enabled for the other linked port and its device.
SUMMARY STEPS
1.
2.
no feature udld3.
4.
5.
6.
7.
8.
DETAILED STEPS
This example shows how to enable the UDLD for the device:
switch# config tswitch(config)# feature udldswitch(config)#This example shows how to enable the normal UDLD mode for Ethernet port 3/1:
switch# config tswitch(config)# feature udldswitch(config)# interface ethernet 3/1switch(config-if)# udld enableswitch(config-if)#This example shows how to enable the aggressive UDLD mode for Ethernet port 3/1:
switch# config tswitch(config)# feature udldswitch(config)# interface ethernet 3/1switch(config-if-range)# udld aggressiveswitch(config-if-range)#This example shows how to disable UDLD for Ethernet port 3/1:
switch# config tswitch(config)# interface ethernet 3/1switch(config-if-range)# no udld enableswitch(config-if-range)# exitThis example shows how to disable UDLD for the device:
switch# config tswitch(config)# no feature udldswitch(config)# exitConfiguring the Carrier Delay Timer
The carrier delay timer sets a time during which all link-down/link-up events are not detected by any of the other software on the device. When you configure a longer carrier delay time, fewer link-down/link-up events are recorded. When you configure the carrier delay time to 0, the device detects each link-down/link-up event.
BEFORE YOU BEGIN
Ensure that you are in VLAN interface mode. You cannot configure the carrier delay timer in any other interface mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
This example shows how to set the carrier delay timer to 20 seconds for VLAN 5:
switch# config tswitch(config)# interface vlan 5switch(config-if)# carrier-delay 20switch(config-if)#Verifying the Basic Interface Parameters
You can verify the basic interface parameters by displaying their values. You can also clear the counters listed when you display the parameter values.
Note
DETAILED STEPS
To display Layer 2 port configuration information, use the appropriate show command for the parameters you need to display.
For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 4.0.
Clearing the Interface Counters
You can clear the Ethernet and management interface counters shown with the show interfaces command. You can perform this task from the EXEC mode, configuration mode, or interface configuration mode.
SUMMARY STEPS
1.
2.
DETAILED STEPS
This example shows how to clear and reset the counters on Ethernet port 5/5:
Switch# clear counters ethernet 5/5Switch#Default Settings
Table 2-6 lists the default settings for the basic interface parameters.
Feature History for Configuring Basic Interface Parameters
Table 2-7 lists the release history for this feature.
