port

To configure a unified port on a Cisco Nexus 5548UP switch or Cisco Nexus 5596UP switch,
use the port command. To remove the unified port, use the no form of this command.

port port-number type { ethernet | fc }

no port port-number type { ethernet | fc }

Syntax Description
port- Port number. The range is from 1 to 199.
number
type Specifies the type of port to configure on a slot in a
chassis.
ethernet Specifies an Ethernet port.
fc Specifies a Fibre Channel (FC) port.

Command Default

None

Command Modes

Slot configuration mode

Command History
Release Modification
5.0(3)N1(1) This command was introduced.

Usage Guidelines

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 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.

You must configure Ethernet ports and FC ports in a specified order:

 FC 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 FC ports start from port 1/32 backwards to
port 1/1.

Examples

This example shows how to configure a unified port on a Cisco Nexus 5548UP switch or
Cisco Nexus 5596UP switch:

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

This example shows how to configure a unified port on a Cisco N55-M16UP expansion
module:

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

This example shows how to configure 20 ports as Ethernet ports and 12 as FC ports:

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
Basic Nexus 5k configuration for native FC
Answered Question

TEDDY LLANO 8 months ago

Hello,

Does anyone have steps on how to configure Nexus 5k for native fc to a storage
controller? See topology:

[SERVER] hba <------> FC Port [NEXUS 5548UP] FC Port <-------> FC Port

[STORAGE ARRAY]

Any info that anyone could provide regarding this would be greatly appreciated.

I have this problem too.

0 votes
Correct Answer by marcel.zehnder about 7 months 2 weeks ago
Hi Teddy

Assuming you use the last two ports as FC-ports:

feature fcoe (this includes the native FC-features)

slot 1

port 31-32 type fc

reload switch

vsan database

vsan 10

interface fc1/31-32

switchport mode F

no shut

vsan database

vsan 10 interface fc 1/31

vsan 10 interface fc 1/32

Check FLOGI:

show flogi database vsan 10 (you should see a flogi from each FC port)

ZONIG:

zoneset name ZS-VSAN-10 vsan 10

zone name Z1

member pwnn (PWNN of ARRAY)

member pwnn (PWNN of HBA)

zoneset activate name ZS-VSAN-10 vsan 10

HTH

Marcel
Setting QoS for fcoe on Nexus 5548up

FCoE login failure when connecting to Nexus

5548
A couple of months ago while we were installing our Nexus 5548s in the E-
Lab, we noticed an FCoE login problem. Although we configured the 5548s
in exactly the same manner described for the Nexus 5020 / 5010 in the FCoE
TechBook, the FCoE ENodes would not log in. At first we thought it was a
problem with the ENodes, but an xgig trace showed that the 5548 was not
transmitting any DCBX or FIP frames. As a result, I sent an email off to my
friends at Cisco that essentially asked “WTFF?” (Where’s The FIP
Frames?). A short time later, Cisco sent a message similar to the following:
Hi Erik,
QoS class-fcoe is not enabled by default on 5548 (to conserve buffers). You
should have seen a warning when you enabled feature fcoe.
Switch(config)# feature fcoe
FC license checked out successfully
fc_plugin extracted successfully
FC plugin loaded successfully
FCoE manager enabled successfully
FC enabled on all modules successfully
Warning: Ensure class-fcoe is included in qos policy-maps of all types
To accomplish this, attach these qos policies under system qos
**********************************************
switch (config)# system qos
switch (config-sys-qos)# service-policy type qos input
fcoe-default-in-policy
switch (config-sys-qos)# service-policy type queuing input
fcoe-default-in-policy
switch (config-sys-qos)# service-policy type queuing output
fcoe-default-out-policy
switch (config-sys-qos)# service-policy type network-qos
fcoe-default-nq-policy
**********************************************
Please run the above commands on the switch and let us know if that
resolves your issue.
This is also documented in the Cisco QOS document.
I ran the commands they provided and the ENodes immediately logged
in. I’ve since discussed the “Warning” message with Cisco and have
encouraged them to consider providing a prompt to the user that would ask
if they would like to automatically enable the appropriate service policy.
In any case, since the 5548 was added to the January EMC Support Matrix
and the 5548 specific information will not be in the EMC FCoE TechBook
until February, I wanted to make sure that these new QOS settings were
clearly spelled out somewhere by EMC.

------------------------
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy