Filter
Top Products
Guidelines and Limitations for Port Profiles
Port profiles have the following configuration guidelines and limitations:
• Each port profile must have a unique name across interface types and the network.
• Commands that you enter under the interface mode take precedence over the port profile’s commands
if there is a conflict. However, the port profile retains that command in the port profile.
• The port profile’s commands take precedence over the default commands on the interface, unless the
default command explicitly overrides the port profile command.
• After you inherit a port profile onto an interface or range of interfaces, you can override individual
configuration values by entering the new value at the interface configuration level. If you remove the
individual configuration values at the interface configuration level, the interface uses the values in the
port profile again.
• There are no default configurations associated with a port profile.
• A subset of commands are available under the port profile configuration mode, depending on which
interface type that you specify.
• You cannot use port profiles with Session Manager.
About the Debounce Timer Parameters
The port debounce time is the amount of time that an interface waits to notify the supervisor of a link going
down. During this time, the interface waits to see if the link comes back up. The wait period is a time when
traffic is stopped.
You can enable the debounce timer for each interface and specify the delay time in milliseconds.
When you enable the port debounce timer the link up and link down detections are delayed, resulting in
a loss of traffic during the debounce period. This situation might affect the convergence and reconvergence
of some protocols.
Caution
About MTU Configuration
The Cisco Nexus device switch does not fragment frames. As a result, the switch cannot have two ports in
the same Layer 2 domain with different maximum transmission units (MTUs). A per-physical Ethernet interface
MTU is not supported. Instead, the MTU is set according to the QoS classes. You modify the MTU by setting
class and policy maps.
When you show the interface settings, a default MTU of 1500 is displayed for physical Ethernet interfaces
and a receive data field size of 2112 is displayed for Fibre Channel interfaces.
Note
Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1)
78-26881-OL 9
Configuring Layer 2 Interfaces
About the Debounce Timer Parameters