FC ports on nexus 5548?

Hi, I would like to know how many maximum FC ports can one have on a Nexus 5548 (N5K-C5548UP) without any expansion module? I have the FC_FEATURES_PKG license installed.

Cisco Nexus 5548UP Switch
The Cisco Nexus 5548UP (Figure 2) is a 1RU 10 Gigabit Ethernet, Fibre Channel, and FCoE switch offering up to 960 Gbps of throughput and up to 48 ports. The switch has 32 unified ports and one expansion slot.

Similar Messages

UCS FI 6248 to Nexus 5548 San port-channel - not working

Hi all,
I'm sure I am missing something fairly obvious and stupid but I need several sets of eyes and help.
Here is the scenario:
I want to be able to create san port-channels between the FI and Nexus. I don't need to trunk yet as I can't even get the channel to come up.
UCS FI 6248:
Interfaces fc1/31-32
Nexus 5548
interfaces fc2/15-16
FI is in end-host mode and Nexus is running NPIV mode with fport-channel-trunk feature enabled.
I'm going to output the relevants configurations below.
Nexus 5548:
NX5KA(config)# show feature | include enabled
fcoe                  1         enabled
fex                   1         enabled
fport-channel-trunk   1         enabled
hsrp_engine           1         enabled
interface-vlan        1         enabled
lacp                  1         enabled
lldp                  1         enabled
npiv                  1         enabled
sshServer             1         enabled
vpc                   1         enabled
interface san-port-channel 133
channel mode active
no switchport trunk allowed vsan all
switchport trunk mode off
interface fc2/15
switchport trunk mode off
channel-group 133 force
no shutdown
interface fc2/16
switchport trunk mode off
channel-group 133 force
no shutdown
NX5KA# show vsan membership
vsan 1 interfaces:
    fc2/13            fc2/14
vsan 133 interfaces:
    fc2/15            fc2/16            san-port-channel 133
vsan 4079(evfp_isolated_vsan) interfaces:
vsan 4094(isolated_vsan) interfaces:
NX5KA# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port-      Type    Protocol               Member Ports
       Channel
133    San-po133 FC      PCP      (D) FC       fc2/15(D)    fc2/16(D)
UCS Fabric Interconnect outputs:
UCS-FI-A-A(nxos)# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port-      Type    Protocol               Member Ports
       Channel
133    San-po133 FC      PCP      (D) FC       fc1/31(D)    fc1/32(D)
UCS-FI-A-A(nxos)#
UCS-FI-A-A(nxos)# show run int fc1/31-32
!Command: show running-config interface fc1/31-32
!Time: Fri Dec 20 22:58:51 2013
version 5.2(3)N2(2.21b)
interface fc1/31
switchport mode NP
channel-group 133 force
no shutdown
interface fc1/32
switchport mode NP
channel-group 133 force
no shutdown
UCS-FI-A-A(nxos)#
UCS-FI-A-A(nxos)# show run int san-port-channel 133
!Command: show running-config interface san-port-channel 133
!Time: Fri Dec 20 22:59:09 2013
version 5.2(3)N2(2.21b)
interface san-port-channel 133
channel mode active
switchport mode NP

!Command: show running-config interface san-port-channel 133
!Time: Sat May 16 04:59:07 2009
version 5.1(3)N1(1)
interface san-port-channel 133
channel mode active
switchport mode F
switchport trunk mode off
Changed it as you suggested...
Followed the order of operations for "no shut"
Nexus FC -> Nexus SAN-PC -> FI FC -> FI SAN-PC.
Didn't work:
NX5KA(config-if)# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port-      Type    Protocol               Member Ports
       Channel
133    San-po133 FC      PCP      (D) FC       fc2/15(D)    fc2/16(D)
NX5KA(config-if)#
Here is the output as you requested:
NX5KA(config-if)# show int san-port-channel 133
san-port-channel 133 is down (No operational members)
    Hardware is Fibre Channel
    Port WWN is 24:85:00:2a:6a:5a:81:00
    Admin port mode is F, trunk mode is off
    snmp link state traps are enabled
    Port vsan is 133
    1 minute input rate 1256 bits/sec, 157 bytes/sec, 0 frames/sec
    1 minute output rate 248 bits/sec, 31 bytes/sec, 0 frames/sec
      3966 frames input, 615568 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      2956 frames output, 143624 bytes
        0 discards, 0 errors
      46 input OLS, 41 LRR, 73 NOS, 0 loop inits
      257 output OLS, 189 LRR, 219 NOS, 0 loop inits
    last clearing of "show interface" counters never
    Member[1] : fc2/15
    Member[2] : fc2/16
NX5KA(config-if)#
NX5KA(config-if)# show int brief
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc2/13     1      auto   on      sfpAbsent        --     --           --
fc2/14     1      auto   on      sfpAbsent        --     --           --
fc2/15     133    F      off     init             swl    --           133
fc2/16     133    F      off     init             swl    --           133

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Telephony Issues on Nexus 5548

Dear Viewers,
I have Nexus 5548 devices in one of my client data centers and i have one 3750 switch to which all of these Avaya voice servers connect.
The 3750 switch was initially connected through a L2 Link to a 6509 catalyst switch and the telephony applications were working correctly.
The problem arises when i move this 3750 layer 2 link to a Nexus 5548 (OS version 5.1(3)N1 switch. All telephony calls coming from the outside (External calls) are not working as required but the internal calls work as usual.
What is odd is that when i migrate this L2 link back to the 6509 switch, all works as usual. This is just a layer 2 connection and i am wondering why this is not possible.
The vlan is accepted on all relevant trunks. I also deactivated igmp snooping on this voice vlan on the Nexus 5548 thinking it would help but in vain.
Any ideas and suggestions are welcome.
regards.
Alain

This is my radius config...... on a 5K
radius-server timeout 7
radius-server host 10.28.42.20 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
radius-server host 10.28.42.21 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
aaa group server radius Radius-Servers
server 10.28.42.20
server 10.28.42.21
aaa authentication login default group Radius-Servers
ip radius source-interface Vlan1
aaa authentication login default fallback error local
And it is currently working. On the radius server i also had to do this to make the users admins once logged in:
https://supportforums.cisco.com/document/137181/nexus-integration-admin-access-free-radius

Command to see transmit qeueing drops in Nexus 5548

Hello, 10g links in our core are getting rather congested as seen by MRTG graphs. Any command on Nexus 5548 to show transmit queuing drops on a given interface?

You could use #show queing interface eth 1/1
it shows you output similar as below:
NEXUS-1# show queuing interface ethernet 1/1
Ethernet1/1 queuing information:
TX Queuing
    qos-group sched-type oper-bandwidth
        0       WRR            100
RX Queuing
    qos-group 0
    q-size: 470080, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 470080
    Statistics:
        Pkts received over the port             : 222434
        Ucast pkts sent to the cross-bar        : 199674
        Mcast pkts sent to the cross-bar        : 22760
        Ucast pkts received from the cross-bar : 101087
        Pkts sent to the port                   : 145083
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Active), Tx (Inactive)
Total Multicast crossbar statistics:
    Mcast pkts received from the cross-bar      : 43996

Nexus 5548 L3 daughter card flapping

Hi guys,
Anyone of you here that experienced the logs below on their Nexus box:
2011 Dec 12 06:24:45 GDCNXS5K01 %BTCM-2-BTCM_LOG_ROUTER_ERR: router card in slot 3 has internal link(s) flapped: router ports down: 0x1a108000 0x1a109000 0x1a10a000 0x1a10b000 0x1a10c000 0x1a10d000 0x1a10e000 0x1a10f000
I am getting this log at least once a day. Seems like it is shutting down the SVI of the box after the said log occured. Good thing I have enable vPC and I am able to access the NXS5K through the vCP keepalive link (mgmt).
I have two Nexus 5548, but only one is experiencing the said error.
Any inputs, suggestions would be greatly appreciated.
Thanks,
Edzel

We had this same problem this past weekend, only in module 2 on a 5596.
In our case, we had rebooted our primary Nexus and found the following message immediately preceeded the BTCM error you noted:
%$ VDC-1 %$ %NOHMS-2-NOHMS_DIAG_ERROR: Module 2: Bootup diag detected major event: Forwarding ASIC failure: Ethernet2/9 Ethernet2/10 Ethernet2/11 Ethernet2/12 Ethernet2/13 Ethernet2/14 Ethernet2/15 Ethernet2/16
We replaced the module. A "show diag results module 3" would probably show you the same thing. However, I don't think the error message will show up until you reboot.
If your flapping Nexus is secondary, you probably won't notice anything major, but if it is your primary, it would probably affect your routing.

Servers connected to Nexus 5548 only getting 200 Mbps of throughput

Servers connected to NExus 5k were only getting 100 Mbps of throughput. So I disabled Flow control recieve on all the ports. After this we are getting 200 Mbps of speed. The servers are connected throuh 10 gig port. Could you guys please suggest why the throguhput is still low? Atleast we should get 1Gbps of thrpoughput.

Hi Adam,
I think we probably need a little more information to go on. Can you answer the following?
What type of servers and NICs?
What OS are you running on the servers?
What cables do you have from the servers to the switch?
Are the two servers in the same subnet or is the traffic between them routed?
If routed, is that in the Nexus 5548 or some other router?
How are you testing throughput?
Presumably you're not seeing any errors on the switch ports that the servers are connected to?
Regards

Configuring FET-10G-SR for NEXUS 5548/2248

Hey everyone-
I am a little newer with configuring switches and routers, and I have been asked to troubleshoot a FET-10G-SR in our NEXUS 5548 and NEXUS 2248. I am aware that the ports need to be configured to except FET parts, and I have tried using the "switchport mode fex-fabric" command to configure the ports, but the command will not work for some reason. Can anyone help me with configurations step by step to have these parts work properly? Any help will be greatly appreciated. Thank you!
Chris Hazell

It should normally work unless the port is not the proper type of has a configuraiton applied that's incompatible.
Can you provide the output for "show run int eth ___" and "show int eth___" (substituting your interface number for the "___") for the interface in question?
Also, if it's the first fex you are adding, you must have enabled "feature fex" globally.

Nexus 5548 Layer 3 daughter card insertion

Hello there,
I am planning to install Nexus 5548 Layer 3 daughter card. I found the hardware removal procedure on Cisco website but it doesn't say whether it's hot plugged or not. (Since I've to remove existing L2 module so I guess the box needs to be powered off but not sure). Has anybody had the experience in doing the upgrade to share?
Thanks in advance
Regards,
Chinnawoot
PS. Detail of the running system
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
AUUT05TRUSDS03# show ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 7.0(1)N1(1)
system:    version 7.0(1)N1(1)
Power Sequencer Firmware:
             Module 1: version v2.0
             Module 3: version v2.0
Microcontroller Firmware:        version v1.2.0.1
SFP uC:    Module 1: v1.0.0.0
QSFP uC:   Module not detected
BIOS compile time:       05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.7.0.1.N1.1.bin
kickstart compile time: 3/19/2014 14:00:00 [03/20/2014 10:09:46]
system image file is:    bootflash:///n5000-uk9.7.0.1.N1.1.bin
system compile time:     3/19/2014 14:00:00 [03/20/2014 13:54:43]
Hardware
cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")
Intel(R) Xeon(R) CPU         with 8253860 kB of memory.
Processor Board ID FOC172441CQ
Device name: AUUT05TRUSDS03
bootflash:    1966080 kB
Kernel uptime is 172 day(s), 21 hour(s), 56 minute(s), 9 second(s)
Last reset at 126063 usecs after Wed May 21 12:35:50 2014
Reason: Reset Requested by CLI command reload
System version: 7.0(1)N1(1)
Service: power-sequence cycled
plugin
Core Plugin, Ethernet Plugin
AUUT05TRUSDS03# show lic usage
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                No    -   Unused             -
FC_FEATURES_PKG               No    -   Unused             -
VMFEX_FEATURE_PKG             No    -   Unused             -
ENHANCED_LAYER2_PKG           Yes   -   Unused Never       -
LAN_BASE_SERVICES_PKG         No    -   Unused             -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -

I ended up getting the answer from TAC. First put in these two commands:
test ethpm l3 enable-show-iport
test port-channel l3 enable-show-ipc
Then you will get some new port channels showing up (127 and 128).
I'm not sure what 128 is for, but 127 is the internal port channel for the L3 card. Then you can view stats and poll with SNMP against the interface...
show interface port-channel 127

Link Error Nexus 5548

Hi All,
I have issues with Nexus 5548 ports 1000Gb ports. They go down after sometime with the error " Link not connected " while the links are connected. When i move the connections to other ports they work but after a while the go down again with the same error. I can confirm that is currently down was working and its currently connected. Has anyone seen the error before?
Kindly see the output from the interface thats currently down below:
VNX_NEXUS# sho interface eth1/11
Ethernet1/11 is down (Link not connected)
Hardware: 1000/10000 Ethernet, address: 002a.6a71.1f92 (bia 002a.6a71.1f92)
Description: Link_to_EMC_RPA3
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, 1000 Mb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 2d23h
Last clearing of "show interface" counters 5w6d
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
43384443 unicast packets 30 multicast packets 1496 broadcast packets
43385969 input packets 7837558138 bytes
0 jumbo packets 0 storm suppression bytes
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
56587244 unicast packets 3937125 multicast packets 1487058 broadcast packets
62011427 output packets 14141808286 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
18 interface resets

Hi Leo,
What confuses me is that the connection was working. I used the correct cable and the port type as well. How do i resolve this?

Upgrading Nexus 5548

Hi,
We want to upgrade our pair of Nexus 5548 to the new NX-OS 5.1(3)N2(1a) from the 5.0(3)N1(1c) version. We would like to use the ISSU procedure. But when we execute the command "show spannig-tree issu-impact" we get the following output:
No Active Topology change Found!
Criteria 1 PASSED !!
No Ports with BA Enabled Found!
Criteria 2 PASSED!!
List of all the Non-Edge Ports
Port VLAN Role Sts Tree Type Instance
Ethernet2/8 1803 Desg FWD PVRST 1803
The 1803 vlan is only used for the peer-keepalive link and it only exists on these two Nexus. So one of the two Nexus needs to be the STP root. That makes the ports on that vlan to be in designated-forwarding state, which is not supported for the ISSU:
sh run int e2/8
!Command: show running-config interface Ethernet2/8
!Time: Fri Jun 8 17:04:33 2012
version 5.0(3)N1(1c)
interface Ethernet2/8
switchport access vlan 1803
speed 1000
That is the only port that belongs to that VLAN and it is directly connected to the other Nexus 5548. So the only way we see to avoid this port of being in designated-forwarding state is to apply the "no spanning-tree vlan 1803" command. Would it be a problem?
We can imagine that introducing the "spanning-tree port type edge" should not be a good idea, shouldn´t it?
Thank you very much for your help!
Josu

Hi,
Reviewing all the prerequisites for the ISSU, we have seen the following:
SSU and Layer 3
Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non disruptive upgrade) when Layer 3 is enabled. It is required to unconfigure all Layer 3 features to be able to upgrade in a non disruptive way with an ISSU.
We have the interface-vlan feature enabled. But it is only used for two interfaces:
- interface-vlan 510 --> It is only used in order connect to the switch
- interface-vlan 1803 --> The one used for the keepalive
We could administratevely shutdown the interface-vlan 510. But we could not do so with the interface-vlan 1803, since it is used for the keepalive. If we execute "no feature interface-vlan", would the keepalive stop working?
When we execute "sh install all impact ..." command the Nexus does not tell anything about this feature. Is really recommended to disable it? Is it needed for the ISSU procedure?
Thank you very much in advance!!
JOSU

Connectivity Issue between Nexus 5548 to VNX 5300

Hi All,
I am doing a lab setup where i want to connect Nexus 5548 UP to VNX 5300 storage directly. The physical connectivity is established between switch and storage but On Nexus the status of the port shows "linkFailure". I tried matching the port mode (like Auto, F) and speed but the port always shows "linkFailure".
The connectivity from Nexus to VNX is FC.
Anyone can suggest the root cause or any troubleshooting steps.
Regards,
Abhilash

LinkFailure might be a GUI status.
show interface fcx/y might say,
Link failure or not connected
The physical layer link is not operational.
This means the switch is not detecting light, so the phyiscal layer is the cable and lasers (sfp's, HBAs or whatever adapter the VNX uses). It could mean you need to turn the interfaace up from the vnx side.

C220 M4 w/ VIC1225 and Nexus 5548

I have four UCS C220 M4 servers that each have a VIC 1225 and are connected up to a Nexus 5548. I have set them to trunk ports and have set the appropriate VLANs in ESX and the portgroups. I can ping the gateway and other hosts on the network, but for some reason I can't ping any of the other C220 M4 servers that have a VIC1225. All of the C220's can ping other devices on the network, but not each other. Is there some setting I need to modify on the VIC or switch? Currently the VIC is running as Classical Ethernet mode.

There is no special configuration to make connectivity work in the rack servers, I assume these servers are in standalone mode and not integrated with UCSM.
What L3 device is doing your Inter-Vlan routing? Is it the N5K these servers are connected to or there is another device doing this job? If it is the N5K, are all the servers in the same network segment? I mean, is there a single SVI or multiple? can your Nexus 5K ping each of the servers?
-Kenny

Creating VPC's between 2 NExus 5548's

I am just about to setup my 2 Nexus 5548's in the
lab for VPc. I see that I have to setup an etherchannel using 2 10 gig ports for the Peer link and
I also have to setup a Peer keepalive.
Do I also have to burn a 10 gig port on both switches for this keepalive ?
I dont have any 1 gig ports on these switches.
Any help would be appreciated.
Cheers
Dave

The best way is to connect the mgmt0 ports to a CORE switch for out of band management. Also, when you configure the vrf context management, make sure you specify a route to the management subnet via vrf management.

Connecting IBM v7000 to Nexus 5548

20-Sep-2012 16:51 (in response to feisalb)
IBM V7000 with Nexus 5548UP and Nexus 4000 Design/implemetation guide
Hi Guys
I have a question in regards to connecting IBM v7000 directly to Nexus5548.
CAN WE DO THIS?
Our current setup is IBM v7000 -> MDS 9124 -> Nexus 5548.
But our MDS 9124 are out of warranty now and we need to take them out of production. And only way we can do this is if we connect our IBM v7000 fibre ports directly to our Nexus 5548.
Can someone please point me to the right direction any knowledge base articles etc.
Thanks Heaps
Sid

Dear prkrishn
I am working on the Data Center Solution between two Data Center, details underneath
DC 1 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
DC 2 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
With the above mention setup, can I configure FCIP between DC1 & DC2 using Nexus 7009? or I need FCIP capable Switch such as IBM SAN Switch (SAN06-BR), I was wondering if I can configure FCIP on Nexus 7009 DC Switch.
Hoping for your kind response at earliest.
Kind Regards,
Arnold

FC ports on nexus 5548?

Similar Messages

Maybe you are looking for