Beginning in Cisco NX-OS Release 5.0(3)N1(1b), Cisco introduces unified port technology. Cisco Nexus unified ports allow you to configure a physical port on a Cisco Nexus 5500 Platform switch as a 1/10-Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), or 1-, 2-, 4-, 8-Gigabit native Fibre Channel port.

Currently, most networks have two types of switches for different types of networks. For example, LAN switches carry Ethernet traffic up to Catalyst switches and SAN switches carry FC traffic from servers to MDS switches. With unified port technology, you can deploy a unified platform, unified device, and unified wire approach. Unified ports allow you to move from an existing segregated platform approach where you choose LAN and SAN port options to transition to a single, unified fabric that is transparent and consistent with existing practices and management software. A unified fabric includes the following:

• Unified platform—Uses the same hardware platform and the same software code level and certifies it once for your LAN and SAN environments.

• Unified device—Runs LAN and SAN services on the same platform switch. The unified device allows you to connect your Ethernet and Fibre Channel cables to the same device.

• Unified wire—Converges LAN and SAN networks on a single converged network adapter (CNA) and connects them to your server.

A unified fabric allows you to manage Ethernet and FCoE features independently with existing Cisco tools.

The new Cisco Nexus 5548UP switch and the Cisco Nexus 5596UP switch provides built-in unified port technology. In addition, a new unified port expansion module and two Layer 3 modules increase the benefits of a deployed unified fabric. For information on the new Cisco Unified Port switches and modules, see the Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) and the Cisco Nexus 5000 Series Hardware Installation Guide.

An interface is in the error-disabled (err-disabled) state when the inteface is enabled administratively (using the no shutdown command) but disabled at runtime by any process. For example, if UDLD detects a unidirectional link, the interface is shut down at runtime. However, because the interface is administratively enabled, the interface status displays as err-disabled. Once an interface goes into the err-disabled state, you must manually reenable it or you can configure an automatic timeout recovery value. The err-disabled detection is enabled by default for all causes. The automatic recovery is not configured by default.

When an interface is in the err-disabled state, use the errdisable detect cause command to find information about the error.

You can configure the automatic err-disabled recovery timeout for a particular err-disabled cause by changing the time variable.

The errdisable recovery cause command provides automatic recovery after 300 seconds. To change the recovery period, use the errdisable recovery interval command to specify the timeout period. You can specify 30 to 65535 seconds.

If you do not enable the err-disabled recovery for the cause, the interface stays in the err-disabled state until you enter the shutdown and no shutdown commands. If the recovery is enabled for a cause, the interface is brought out of the err-disabled state and allowed to retry operation once all the causes have timed out. Use the show interface status err-disabled command to display the reason behind the error.

Beginning with Cisco NX-OS Release 5.0(2)N1(1), you can create a port profile that contains many interface commands and apply that port profile to a range of interfaces on the Cisco Nexus 5000 Series switch. Port profiles can be applied to the following interface types:

• Ethernet

• VLAN network interface

• Port channel

A command that is included in a port profile can be configured outside of the port profile. If the new configuration in the port profile conflicts with the configurations that exist outside the port profile, the commands configured for an interface in configuration terminal mode have higher priority than the commands in the port profile. If changes are made to the interface configuration after a port profile is attached to it, and the configuration conflicts with that in the port profile, the configurations in the interface will be given priority.

You inherit the port profile when you attach the port profile to an interface or range of interfaces, When you attach, or inherit, a port profile to an interface or range of interfaces, the switch applies all the commands in that port profile to the interfaces.

You can have one port profile inherit the settings from another port profile. Inheriting another port profile allows the initial port profile to assume all of the commands of the second, inherited, port profile that do not conflict with the initial port profile. Four levels of inheritance are supported. The same port profile can be inherited by any number of port profiles.

To apply the port profile configurations to the interfaces, you must enable the specific port profile. You can configure and inherit a port profile onto a range of interfaces prior to enabling the port profile; you then enable that port profile for the configurations to take effect on the specified interfaces.

When you remove a port profile from a range of interfaces, the switch undoes the configuration from the interfaces first and then removes the port profile link itself. When you remove a port profile, the switch checks the interface configuration and either skips the port profile commands that have been overridden by directly entered interface commands or returns the command to the default value.

If you want to delete a port profile that has been inherited by other port profiles, you must remove the inheritance before you can delete the port profile.

You can choose a subset of interfaces from which to remove a port profile from among that group of interfaces that you originally applied the profile. For example, if you configured a port profile and configured ten interfaces to inherit that port profile, you can remove the port profile from just some of the specified ten interfaces. The port profile continues to operate on the remaining interfaces to which it is applied.

If you delete a specific configuration for a specified range of interfaces using the interface configuration mode, that configuration is also deleted from the port profile for that range of interfaces only. For example, if you have a channel group inside a port profile and you are in the interface configuration mode and you delete that port channel, the specified port channel is also deleted from the port profile as well.

After you inherit a port profile on an interface or range of interfaces and you delete a specific configuration value, that port profile configuration will not operate on the specified interfaces.

If you attempt to apply a port profile to the wrong type of interface, the switch returns an error.

When you attempt to enable, inherit, or modify a port profile, the switch creates a checkpoint. If the port profile configuration fails, the switch rolls back to the prior configuration and returns an error. A port profile is never only partially applied.

1.    switch# configure terminal

2.    switch(config)# interface ethernet slot/port

3.    switch(config-if)# no switchport

4.    switch(config-if)# no shutdown

switch# configure terminal
switch(config)# interface ethernet 1/2
switch(config-if)# no switchport
switch(config-if)# no shutdown

You can configure a unified port on a Cisco Nexus 5548UP switch, a Cisco Nexus 5596UP switch, or a Cisco Nexus 5548P switch with an installed Cisco N55-M16UP expansion module.

Unified ports allow you to configure ports as Ethernet, native Fibre Channel, or Fibre Channel over Ethernet (FCoE) ports. By default, the ports are Ethernet ports but you can change the port mode to native Fibre Channel on the following unified ports:

• Any port on the Cisco Nexus 5548UP switch or the Cisco Nexus 5596UP switch.

• The ports on the Cisco N55-M16UP expansion module that is installed in a Cisco Nexus 5548P switch

Note

You must configure Ethernet ports and Fibre Channel ports in a specified order: Fibre Channel ports must be configured from the last port of the module. Ethernet ports must be configured from the first port of the module. If the order is not followed, the following errors are displayed: ERROR: Ethernet range starts from first port of the module ERROR: FC range should end on last port of the module On a Cisco Nexus 5548UP switch, the 32 ports of the main slot (slot1) are unified ports. The Ethernet ports start from port 1/1 to port 1/32. The Fibre Channel ports start from port 1/32 backwards to port 1/1.

1.    switch# configure terminal

2.    switch(config)# slot slot number

3.    switch(config-slot)# port port number type {ethernet | fc}

4.    switch(config-slot)# copy running-config startup-config

5.    switch(config-slot)# reload

6.    switch(config)# no port port number type fc

switch# configure terminal
switch(config)# slot 1
switch(config-slot)# port 32 type fc
switch(config-slot)# copy running-config startup-config
switch(config-slot)# reload

switch# configure terminal
switch(config)# slot 2
switch(config-slot)# port 32 type fc
switch(config-slot)# copy running-config startup-config
switch(config-slot)# reload

switch# configure terminal
switch(config)# slot 1
switch(config-slot)# port 21-32 type fc
switch(config-slot)# copy running-config startup-config
switch(config-slot)# reload

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.

Note	Before you begin, UDLD must be enabled for the other linked port and its device.

To configure the UDLD mode, perform this task:

1.    switch# configure terminal

2.    switch(config)# feature udld

3.    switch(config)# no feature udld

4.    switch(config)# show udld global

5.    switch(config)# interface type slot/port

6.    switch(config-if)# udld {enable | disable | aggressive}

7.    switch(config-if)# show udld interface

 switch# configure terminal

 switch(config)# feature udld

 switch# configure terminal

 switch(config)# interface ethernet 1/4

 switch(config-if)# udld enable

 switch# configure terminal

 switch(config)# interface ethernet 1/4

 switch(config-if)# udld aggressive

 switch# configure terminal

 switch(config)# interface ethernet 1/4

 switch(config-if)# udld disable

 switch# configure terminal

 switch(config)# no feature udld

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# speed speed

The following example shows how to set the speed for a 1-Gigabit Ethernet port:

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# speed 1000

This command can only be applied to a physical Ethernet interface.

Note

If the interface and transceiver speed is mismatched, the SFP validation failed message is displayed when you enter the show interface ethernet slot/port command. For example, if you insert a 1-Gigabit SFP transceiver into a port without configuring the speed 1000 command, you will get this error. By default, all ports are 10 Gigabits.

1.    switch# configure terminal

2.    (Optional) switch(config)# [no] cdp advertise {v1 | v2 }

3.    (Optional) switch(config)# [no] cdp format device-id {mac-address | serial-number | system-name}

4.    (Optional) switch(config)# [no] cdp holdtime seconds

5.    (Optional) switch(config)# [no] cdp timer seconds

switch# configure terminal

switch(config)# cdp timer 50

switch(config)# cdp holdtime 120

switch(config)# cdp advertise v2

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# cdp enable

4.    switch(config-if)# no cdp enable

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# cdp enable

1.    config t

2.    errdisable detect cause {all | link-flap | loopback}

3.    shutdown

4.    no shutdown

5.    show interface status err-disabled

6.    copy running-config startup-config

switch# config t
switch(config)#

switch(config)# errdisable detect cause all
switch(config)#

switch(config)# shutdown
switch(config)#

switch(config)# no shutdown
switch(config)#

switch(config)# show interface status err-disabled

switch(config)# copy running-config startup-config

switch(config)#errdisable detect cause all
switch(config)#

1.    config t

2.    errdisable recovery cause {all | udld | bpduguard | link-flap | failed-port-state | pause-rate-limit}

3.    show interface status err-disabled

4.    copy running-config startup-config

switch#config t
switch(config)#

switch(config)#errdisable recovery cause all
switch(config-if)#

switch(config)#show interface status err-disabled

switch(config)#copy running-config startup-config

switch(config)#errdisable recovery cause all
switch(config)#

1.    config t

2.    errdisable recovery interval interval

3.    show interface status err-disabled

4.    copy running-config startup-config

switch#config t
switch(config)#

switch(config)#errdisable recovery interval 32
switch(config-if)#

switch(config)#show interface status err-disabled

switch(config)#copy running-config startup-config

switch(config)#errdisable recovery cause all
switch(config)#

You can apply several configuration parameters to a range of interfaces simultaneously. All the interfaces in the range must be the same type. You can also inherit the configurations from one port profile into another port profile. The switch supports four levels of inheritance.

This section includes the following topics:

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# link debounce time milliseconds

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# link debounce time 1000

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# link debounce time 0

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# description test

switch# configure terminal

switch(config)# interface ethernet 1/3

switch(config-if)# description Server 3 Interface

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# shutdown

4.    switch(config-if)# no shutdown

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# shutdown

switch# configure terminal

switch(config)# interface ethernet 1/4

switch(config-if)# no shutdown