Nexus 6001 native FC

Does the Nexus 6001 support native FC?  I'm having issues changing the port type;
 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 1.5.0
 loader:    version N/A
 kickstart: version 7.0(5)N1(1)
 system:    version 7.0(5)N1(1)
 Power Sequencer Firmware:
            Module 1: version v4.0
            Module 2: version v4.0
 Fabric Power Sequencer Firmware: Module 1: version v4.0
 Microcontroller Firmware:        version v1.2.0.5
 QSFP Microcontroller Firmware:
            Module 2: v1.3.0.0
 SFP Microcontroller Firmware:
            Module 1: v1.1.0.0
 BIOS compile time:       12/29/2012
 kickstart image file is: bootflash:///n6000-uk9-kickstart.7.0.5.N1.1.bin
 kickstart compile time:  10/29/2014 22:00:00 [10/30/2014 11:46:56]
 system image file is:    bootflash:///n6000-uk9.7.0.5.N1.1.bin
 system compile time:     10/29/2014 22:00:00 [10/30/2014 11:47:58]
Hardware
 cisco Nexus 6001 Chassis ("Nexus 64 Supervisor")
 Intel(R) Xeon(R) CPU  @ 2.00 with 8238120 kB of memory.
 Processor Board ID FOC181506P3
  Device name: xxxxxxxxxxxxxx
 bootflash:    7823360 kB
Kernel uptime is 3 day(s), 17 hour(s), 25 minute(s), 49 second(s)
Last reset at 642096 usecs after  Fri Feb 27 15:24:40 2015
  Reason: Disruptive upgrade
 System version: 6.0(2)N2(3)
 Service:
plugin
 Core Plugin, Ethernet Plugin, Fc Plugin
xxxxxx# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
xxxxxx(config)# slot 1
xxxxxx# port 47-48 type fc
ERROR: Module type doesn't support this CLI
Any help would be appreciated.  Thanks

Sorry, should have mentioned that I'd already enabled feature fcoe;
xxxxx(config)# show feature
Feature Name          Instance  State
Flexlink              1         disabled
amt                   1         disabled
bfd                   1         disabled
bfd_app               1         disabled
bgp                   1         disabled
bulkstat              1         disabled
cable-management      1         disabled
cts                   1         disabled
dhcp                  1         disabled
dot1x                 1         disabled
eigrp                 1         disabled
eigrp                 2         disabled
eigrp                 3         disabled
eigrp                 4         disabled
eth_port_sec          1         disabled
evmed                 1         disabled
extended_credit       1         disabled
fabric-access         1         disabled
fabric-binding        1         disabled
fabric_mcast          1         disabled
fc-port-security      1         disabled
fcoe                  1         enabled
xxxxxxxxx(config)# slot 1
xxxxxxxxx(config-slot)# port 47-48 type fc
ERROR: Module type doesn't support this CLI

Similar Messages

  • Connecting a Dell B22 FEX to Nexus 6001 and storage

    Hi Folks,
    We have a setup where we are running a Dell B22 FEX in Blade enviornment and want to connect the B22 FEX to a cisco Nexus 6001 switch. As per NX-OS release note, B22 FEX and 6001 Nexus connectivity is supported.
    Now after connecting to Nexus 6001, how do i get access to storage pool or SAN fabric ?  As per another thread of discussion, Nexus 6001 does not support direct fabric attachment at this point in time. So how do we bridge these two elements to a storage fabric ??
    As per 6.02 release note:
    "Support for DELL FEX
    Added support for the Cisco Nexus B22 Dell Fabric Extender for Cisco Nexus 6000 Series switches starting with the 6.0(2)N1(2) release."
    This is the exact reason we bought it. We have a enviornment where we are running Dell B22 FEX.  Idea is to connect the B22 FEX into Nexus 6001. We are confuse at this point. After connecting the Dell B22 FEX to Nexus 6001, how to access the storage network or storage fabric ??
    Thanks,

    Hi Rays,
    The function should be the same for all FEXs regardless of what parent switch they connect to. to.
    if you are referring to this comment:
    You can connect any edge switch that leverages a link redundancy mechanism not dependent on spanning tree such as Cisco FlexLink or vPC
    FelxLink is a different technology that does not use STP, but not every switch platform supports FelxLink. FlexLink is not used very often, as other technologies like VSS, VPC and stacking has emerged.
    HTH

  • Cisco nexus 6001 not a supported device on cisco prime infrastructure 2.1?

    I have installed Cisco Prime Infrastructure 2.2 and Prime Infrastructure still doesn't seem to support the Nexus 6001 platform? Can someone tell me if Cisco Prime Infrastructure will ever support the Cisco Nexus 6001 platform or is there any plans to support it in any future device packs? 

    The Nexus 6001 isn't currently supported in PI 2.1. There's no workaround except to wait for a device or product update that adds support. Right now I know the 9000 series is on the 2.2 roadmap but I haven't seen any reference to the 6001 and PI.
    Interestingly, Prime LMS does support both the 6001 and 6004. Reference.

  • Nexus 6001 for small DC as a collapsed core/distribution instead of 4500X

    Hi,
    I am looking for a switch platform for a small DC that can provide high density 10G and good L3 performance. I was thinking of Nexus 6001 as L3 performance is better thant 5548/5596 and it supports FabricPath. Than I have also looked at the 4500X but I think that it is more a campus switch than a DC switch. Moreover I would like to get rid of Spanning Tree ;-)
    My last concern is what is the difference in the buffer capacity (when talking 10G to 1G conversion) when comparing the Nexus 6001 to the CAT4500X?
    Thanks in advance,
    Regards,
    Laurent

    Hi,
    Any ideas?
    Regards,
    Laurent

  • Bash Prompt on Nexus 6001

    Anybody seen this or know how to get the switch to boot back into NX-OS?  We upgraded a pair of Nexus 6001s to 6.0(2)N2(1)... one came up fine, the other keeps coming up to a BASH-3.2# prompt and we appear to have full root access.
    I'm guessing this is not normal behavior but I'm trying to see if anybody has seen this while we get TAC on it.  I attached a screenshot for your viewing pleasure.
    Thanks.                  

    Hello,
    I am from TAC. you are hitting a bug. CSCuh28244
    Symptom:
    Nexus 6000 might experience unexpected reload when the switch is getting booted up after being upgraded using
    install all
    command. It will take a long time for the switch to boot up. Instead of  booting all the way, the console will boot in bash mode. Eventually the  switch would experience a crash.
    Conditions:
    Issue happens after upgrading switch from
    6.0(2)N1(2)
    to
    6.0(2)N2(1)
    and when using
    install all
    command to upgrade.
    Workaround:
    power cycle the switch to restore services.
    Thanks,
    Richard
    * Rate if this is useful

  • Converting Eth port to FC port in a cisco 6001 switch

    Hi,
    Back to forum after a long time. I have one issue to discuss regarding cisco 6001 switch. We purchased a new 6001 switch. Want to convert some of the Ethernet ports out of total 48 to FC to join the switch into a existing fabric.
    cisco Nexus 6001 Chassis ("Norcal 64 Supervisor")  - This is what H/W version look like from show version command.
    In the past, we have quite a few Cisco 5548UP switch and the way convert the Ethernet port into FC port is, by going to correct slot/module and then
    (config)# slot 1
    (config-slot)# port 41-48 type fc
    Then "reload" willl complete the conversion. But in the new 6001 switch, it throws the following error when above command is typed. We have full license for the switch including  FC_FEATURES_PKG
    "ERROR: Module type doesn't support this CLI"
    We are running firmware : 6.0(2)N2(2)
    Any help in this regard will be helpful.
    Thanks.

    I have this exact same error;
     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 1.5.0
      loader:    version N/A
      kickstart: version 7.0(5)N1(1)
      system:    version 7.0(5)N1(1)
      Power Sequencer Firmware:
                 Module 1: version v4.0
                 Module 2: version v4.0
      Fabric Power Sequencer Firmware: Module 1: version v4.0
      Microcontroller Firmware:        version v1.2.0.5
      QSFP Microcontroller Firmware:
                 Module 2: v1.3.0.0
      SFP Microcontroller Firmware:
                 Module 1: v1.1.0.0
      BIOS compile time:       12/29/2012
      kickstart image file is: bootflash:///n6000-uk9-kickstart.7.0.5.N1.1.bin
      kickstart compile time:  10/29/2014 22:00:00 [10/30/2014 11:46:56]
      system image file is:    bootflash:///n6000-uk9.7.0.5.N1.1.bin
      system compile time:     10/29/2014 22:00:00 [10/30/2014 11:47:58]
    Hardware
      cisco Nexus 6001 Chassis ("Nexus 64 Supervisor")
      Intel(R) Xeon(R) CPU  @ 2.00 with 8238120 kB of memory.
      Processor Board ID FOC181506P3
      Device name: xxxxxxxxxxxxxx
      bootflash:    7823360 kB
    Kernel uptime is 3 day(s), 17 hour(s), 25 minute(s), 49 second(s)
    Last reset at 642096 usecs after  Fri Feb 27 15:24:40 2015
      Reason: Disruptive upgrade
      System version: 6.0(2)N2(3)
      Service:
    plugin
      Core Plugin, Ethernet Plugin, Fc Plugin
    xxxxxx# conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    xxxxxx(config)# slot 1
    xxxxxx# port 47-48 type fc
    ERROR: Module type doesn't support this CLI

  • Nexus 7004 with N2K-B22HP-P FEX won't connect

    Hello
    I'm trying to connect an HP Blade server with an N2K-B22HP-P to our Nexus 7004 but it stays in de download mode.
    # sh fex
      FEX         FEX           FEX                       FEX
    Number    Description      State            Model            Serial
    116        FEX0116        Image Download         N2K-B22HP-P   FOCxxxxxxxx
    # sh fex detail
    FEX: 116 Description: FEX0116   state: Image Download
      FEX version: 5.2(1)N1(1a) [Switch version: 6.1(4)]
      FEX Interim version: 5.2(1)N1(1a)
      Switch Interim version: 6.1(4)
      Module Sw Gen: 12594  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth3/44
      Fabric interface state:
        Po116 - Interface Up. State: Active
        Eth3/44 - Interface Up. State: Active
      Fex Port        State  Fabric Port
    Logs:
    08/07/2013 18:04:24.424401: Requesting satellite to download image
    08/07/2013 18:04:46.442690: Module register received
    08/07/2013 18:04:46.443233: Registration response sent
    08/07/2013 18:04:46.443516: Requesting satellite to download image
    08/07/2013 18:05:10.475657: Module register received
    08/07/2013 18:05:10.476109: Registration response sent
    08/07/2013 18:05:10.476390: Requesting satellite to download image
    08/07/2013 18:05:36.703639: Module register received
    08/07/2013 18:05:36.704118: Registration response sent
    08/07/2013 18:05:36.704434: Requesting satellite to download image
    08/07/2013 18:06:04.741774: Module register received
    08/07/2013 18:06:04.742505: Registration response sent
    08/07/2013 18:06:04.742628: Requesting satellite to download image

    Hi Martin,
    At this point in time the N2K-B22-HP FEX is not supported with the Nexus 7000 series switches as the parent switch. If you look at Table 2 in the Cisco Nexus B22 Blade Fabric Extender Data Sheet you'll see it only lists the following:
    Cisco Nexus parent switch model or line card
    Cisco Nexus 5010 or 5020 Switch for Cisco Nexus B22HP and B22F
    Cisco Nexus 5548P Switch
    Cisco Nexus 5548UP Switch
    Cisco Nexus 5596UP Switch
    Cisco Nexus 6001 Switch
    Cisco Nexus 6004 Switch
    Regards

  • Nexus 6K: Port-Channel Load-Balance

    Hi all,
    I configured "port-channel load-balance ethernet source-dest-mac" on Nexus 6001. But when I use "show run all | in load-balance", it displays module 1 and module 2 are still using source-dest-ip for port-channel load-balance. And for command "show port-channel load-balance" and "show port-channel load-balance forwarding-path interface", it still shows switch using MAC for hash algorithm. The NXOS is 6.0(2)N1(2a).
    Does anybody know:
    -  What is the function of "port-channel load-balance ethernet source-dest-ip module" and in which situation this command will be effective?
    -  It shows "port-channel load-balance ethernet source-dest-ip module" command for both module 1 and 2. Module 1 is N6K Supervisor and module 2 is 4xQSFP Ethernet Module. Is it possible to set different load-balance algorithm  to these 2 modules?   
    # show run all | in load-balance
    port-channel load-balance ethernet source-dest-mac
    port-channel load-balance ethernet source-dest-ip module 1
    port-channel load-balance ethernet source-dest-ip module 2
    # show port-channel load-balance
    Port Channel Load-Balancing Configuration:
    System: source-dest-mac
    Port Channel Load-Balancing Addresses Used Per-Protocol:
    Non-IP: source-dest-mac
    IP: source-dest-mac
    # show port-channel load-balance forwarding-path interface port-channel 30 vlan 150 src-ip 172.25.228.6 dst-ip 172.25.226.97
    Missing params will be substituted by 0's.
    Load-balance Algorithm on switch: source-dest-mac
    crc_hash: 977 Polynomial: CRC10b        Outgoing port id  Ethernet1/2
    Param(s) used to calculate load-balance:
            seed: 0x701
            dst-mac:  0000.0000.0000
            src-mac:  0000.0000.0000
    # show module
    Mod Ports Module-Type                         Model                  Status
    1   48    Norcal 64 Supervisor                N6K-C6001-64P-SUP      active *
    2   10    Nexus 4xQSFP Ethernet Module        N6K-C6001-M4Q          ok
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    6.0(2)N2(3)     1.0     --
    2    6.0(2)N2(3)     1.0     --

    Hi all,
    I configured "port-channel load-balance ethernet source-dest-mac" on Nexus 6001. But when I use "show run all | in load-balance", it displays module 1 and module 2 are still using source-dest-ip for port-channel load-balance. And for command "show port-channel load-balance" and "show port-channel load-balance forwarding-path interface", it still shows switch using MAC for hash algorithm. The NXOS is 6.0(2)N1(2a).
    Does anybody know:
    -  What is the function of "port-channel load-balance ethernet source-dest-ip module" and in which situation this command will be effective?
    -  It shows "port-channel load-balance ethernet source-dest-ip module" command for both module 1 and 2. Module 1 is N6K Supervisor and module 2 is 4xQSFP Ethernet Module. Is it possible to set different load-balance algorithm  to these 2 modules?   
    # show run all | in load-balance
    port-channel load-balance ethernet source-dest-mac
    port-channel load-balance ethernet source-dest-ip module 1
    port-channel load-balance ethernet source-dest-ip module 2
    # show port-channel load-balance
    Port Channel Load-Balancing Configuration:
    System: source-dest-mac
    Port Channel Load-Balancing Addresses Used Per-Protocol:
    Non-IP: source-dest-mac
    IP: source-dest-mac
    # show port-channel load-balance forwarding-path interface port-channel 30 vlan 150 src-ip 172.25.228.6 dst-ip 172.25.226.97
    Missing params will be substituted by 0's.
    Load-balance Algorithm on switch: source-dest-mac
    crc_hash: 977 Polynomial: CRC10b        Outgoing port id  Ethernet1/2
    Param(s) used to calculate load-balance:
            seed: 0x701
            dst-mac:  0000.0000.0000
            src-mac:  0000.0000.0000
    # show module
    Mod Ports Module-Type                         Model                  Status
    1   48    Norcal 64 Supervisor                N6K-C6001-64P-SUP      active *
    2   10    Nexus 4xQSFP Ethernet Module        N6K-C6001-M4Q          ok
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    6.0(2)N2(3)     1.0     --
    2    6.0(2)N2(3)     1.0     --

  • Nexus 5000 switches - what is a universal port?

    Please forgive the noob question, but I would really appreciate any advice on a network I'm trying to put together. I need the switches for a network with both FC and 10Gb-E (around 30 and 15 of each respectively - to start) and was thought the 5000 series looked like it was just what we needed.
    I'm trying to understand what the Universal Ports are. The documentation says they can support ethernet or FC, but what kind of connector do they use? Looking at the images they seem to be fibre connectors, but can they take an RJ45 plug for ethernet as well?

    See https://supportforums.cisco.com/discussion/11912046/configure-nexus-5548-native-fc
    Cisco Nexus 5548UP and Nexus 5596UP are Unified Fabric switches that have 32 and 48 Fixed SFP+ ports, respectively. This fixed or built-in ports are unified ports which means that each of the ports can be used for conventional Ethernet, FCoE or FC. Out of the box, all of the 32 or 48 ports are "Ethernet" port type. As the name implies, with this port type, the port are ready for us to be used as conventional Ethernet port or for FCoE. Remember that FCoE is basically transporting FC traffic over Ethernet, so we need "Ethernet" port type for FCoE.
    First you configure e.g. a port as FC; then of course you have to insert the proper SPF; same is true for Ethernet: 1 or 10G SFP.

  • Which port to use for the peer-keep alive

    Hi All,
    We have 2 Nexus 6001s in our data center.
    The management port of each 6001 is connected to the other and this link is used as the peer keep alive link.
    My colleague is suggesting that we use one of the inline data ports as the keep alive link.
    Can you please advise on the pros and cons of using management/inline port as keep live link and the best practise to follow in this case?
    Thanks,
    Pete

    Hi Pete,
    Here are the best recommendation in order of preference.
    1. Use mgmt0 (along with management traffic)
         * Pros: whats good on this option is you are totally separating the VPC Peer keepalive link on another VRF (management) and does not mingle with the data or global vrf..
         * Cons: VPC PKL is dependent on the OOB management switch.
    2. Use dedicated 1G/10GE front panel ports. 
        * Pros - can just be a direct link between the N6K pair and not dependent on other boxes. 
        * Cons - you need extra SFPs for VPC PKL while the VPC PKL traffic join the global VRF.
    HTH
    Jay Ocampo

  • ASR9k L2VPN attachment circuit into switch (untagged frame)

    Hi guys,
    I'm trying to look at the best solution for creating a pseudo-wire on an ASR9k and extending the attachment circuit into either a 6500 or Nexus 6001 switch.
    The attachment circuit needs to be untagged so the customer can push whatever VLAN they want onto their frames. The scenario I'm looking at would involve either a Nexus 6001 or 6500 which would sit downstream of the PE and provide the physical presentation to the customer.
    I've thought of an EVC using a Dot1q tunnel with each customer associated with an S-tag on the PE and switch, but haven't tested this. Another way might be to use a bridge-domain to link two interfaces together on the PE, but this would still potentially require Q-in-Q to isolate each customer and allow each customer to push whatever C-tags they want onto the frames.
    Any help on this would be much appreciated!
    Steve

    the best way to me, and i've tested this, would be:
    customer--(dot1q)--qinq/tunnel----6500----(AC)---(dot1q-SVLAN)ASR9k(mpls)
    that way you can provide vlan transparency without having to re-provision each customer.

  • Configure Nexus 5548 for native FC

    hi
    does anyone have steps on how to configure n5k for native fc to a storage controller and then map that to an interface running fcoe to a fabric interconnect say 6200 ?
    appreciate any pointers

    I hope this helps. For integrating UCS in FC NPV mode, you need to enable NPIV on the N5k (feature NPIV)
    Fiber Channel (FC) Ports on Nexus 5000
    Cisco Nexus 5000 is a Cisco Data Center switch platform that supports conventional Ethernet, Storage Area Network (SAN) and Fiber Channel over Ethernet (FCoE). The switch platform has support for connection directly to native Fiber Channel (FC) SAN network with its FC ports. This is needed at least for now as most of customers' storages are still using FC or are behind FC network.
    This post will look at specifically on how to enable FC ports on Nexus 5500 (Nexus 5548UP and Nexus 5596UP) when we need to connect and integrate to FC network. In addition to that, we will look at some of the rules or restrictions that are worth to note based on the current hardware implementation when allocating ports on the switch for FC.
    Cisco Nexus 5548UP and Nexus 5596UP are Unified Fabric switches that have 32 and 48 Fixed SFP+ ports, respectively. This fixed or built-in ports are unified ports which means that each of the ports can be used for conventional Ethernet, FCoE or FC. Out of the box, all of the 32 or 48 ports are "Ethernet" port type. As the name implies, with this port type, the port are ready for us to be used as conventional Ethernet port or for FCoE. Remember that FCoE is basically transporting FC traffic over Ethernet, so we need "Ethernet" port type for FCoE.
    In that case, what if we need to use some of the built-in ports for FC?
    To use some of the ports as FC ports, we need to change the port type of the port(s) that we intent to use for FC connection. Here's an example of commands to change port type on the switch:
    N5K(config)#slot 1
    N5K(config-port)#port 41-48 type fc
    N5K(config-port)#copy running-config startup-config
    N5K(config-port)#Reload
    As the above command example, we change ports 31 and 32 from the default "Ethernet" to "FC" type. Similarly, to convert back from FC to Ethernet port type:
    N5K(config)#slot 1
    N5K(config-port)#port 41-48 type ethernet
    N5K(config-port)#copy running-config startup-config
    N5K(config-port)#Reload
    Note: Refer to this Cisco's Command Reference document for further detail of this command: http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/command/reference/layer2/n5k-l2_cmds_p.html#wp2326019
    You might surprise that there's a reload command in the end? Yes, you need to reload the entire switch to convert  port type. So...one of the important notes here is that, as much as possible, convert the ports before the switch is in production.
    After the port type has been changed from Ethernet to FC, the FC port will not be enabled on the switch until FCOE feature is enabled:
    N5K(config)#feature FCOE
    C license checked out successfully
    fc_plugin extracted successfully
    FC plugin loaded successfully
    FCoE manager enabled successfully
    FC enabled on all modules successfully
    Enabled FCoE QoS policies successfully
    After that, we verify that the port type is changed successfully and the FC ports appear on the switch:
    N5K# show interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/41     1      auto   on      sfpAbsent        --     --           --
    fc1/42     1      auto   on      sfpAbsent        --     --           --
    fc1/43     1      auto   on      sfpAbsent        --     --           --
    fc1/44     1      auto   on      sfpAbsent        --     --           --
    fc1/45     1      auto   on      sfpAbsent        --     --           --
    fc1/46     1      auto   on      sfpAbsent        --     --           --
    fc1/47     1      auto   on      sfpAbsent        --     --           --
    fc1/48     1      auto   on      sfpAbsent        --     --           --
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  trunk  down    SFP validation failed       10G(D) 22
    Eth1/2        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/3        1       eth  trunk  down    SFP validation failed       10G(D) 32
    Eth1/4        1       eth  access down    SFP not inserted            10G(D) --
    Besides the fixed ports, each of the switch model have slot for expansion module for increasing the port density. The number of slot is 1 for Nexus 5548UP and 3 for 5596UP. For supporting FC, the following modules are available to choose from:
    - Fibre Channel plus Ethernet module that provides eight Ethernet port and eight native Fibre Channel ports.
       The first 8 ports of this module is Ethernet port and the remaining 8 ports are FC ports. The location of  Ethernet and FC ports are indicated with different colors.
    http://3.bp.blogspot.com/-46A5Xu-iy3g/UALOGhdiW-I/AAAAAAAAAF4/DuhCP59VX54/s1600/Nexus+5000+-+Module2.PNG
    - Unified port module that provides up to sixteen Ethernet ports OR up to sixteen native Fibre Channel ports
       This is unified port, similar to the fixed or built-in ports whereby it's up to us to use the ports either for  Ethernet or FC. Probably you only want to use some of the ports or even the entire module for FC.
    http://4.bp.blogspot.com/-f95sJ9tsntM/UALOPrUXNpI/AAAAAAAAAGA/M4VA-C2Yh3U/s1600/Nexus+5000+-+Module3.PNG

  • Basic Nexus 5k configuration for native FC

    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.

    Hi wdey,
    Pls find below
    switch(config-if)# show flogi database
    No flogi sessions found.
    switch(config-if)# show interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/29     10     F      on      notConnected     swl    --           --
    fc1/30     10     F      on      notConnected     swl    --           --
    fc1/31     1      auto   on      trunking         swl    TE      4    --
    fc1/32     10     F      auto    notConnected     swl    --           --
    switch(config-if)# sh int fc1/32
    fc1/32 is down (Link failure: loss of sync)
        Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
        Port WWN is 20:20:00:2a:6a:51:9a:c0
        Admin port mode is F, trunk mode is auto
        snmp link state traps are enabled
        Port vsan is 10
        Receive data field Size is 2112
        Beacon is turned off
        1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
        1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
          3676827 frames input, 147073080 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          0 frames output, 0 bytes
            0 discards, 0 errors
          2 input OLS, 2 LRR, 0 NOS, 0 loop inits
          170 output OLS, 2 LRR, 86 NOS, 0 loop inits
        last clearing of "show interface" counters Tue Sep 22 08:24:49 2009

  • Nexus 7k and native vlan 1

    Hi, is it recommended to use a native vlan other than 1 on the trunks connecting Nexus box's. It used to be that you should not use native vlan 1 on the trunks between switches. Is this not an issue anymore.
    Thanks

    Hi Chuck,
    It is recomended to use a different vlan other than vlan 1 as your default vlan.
    This is one of the best practices for secure the overall network.
    For eg.
    In a switch spoofing attack, an attacking host imitates a trunking  switch by speaking the tagging and trunking protocols (e.g. Multiple  VLAN Registration Protocol, IEEE 802.1Q, VLAN Trunking Protocol) used in  maintaining a VLAN. Traffic for multiple VLANs is then accessible to  the attacking host. 
    HTH,
    Aman

  • BB Credits in Nexus 5500UP running Native FC

    We are running nexus 5548up with NX-OS 5.2(1) connected to MDS 9222i. The nexus ports are in native FC mode. The nexus FC port should support a maximum of 240 Receive BB Credits according to "show interface fc1/30 capabilities" command, and also according to the Cisco documentation: http://cisco.sitecelerate.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_1_3_N2_1/Nexus5000_Release_Notes_5_1_3_N2.html
    However my FC ports still don't accept more than 64 BB credits:
    n5kup(config-if)# switchport fcrxbbcredit 65
    fc1/30: (error) Invalid rxb2b credit for desired port-mode and rate-mode
    n5kup(config-if)# switchport fcrxbbcredit 64
    n5kup(config-if)#
    I have tried putting all other ports out-of-service to make sure there is enough resources. Tried reducing the speed from 4Gb to 2Gb. Still the maximum BB credits that can be assigned is 64, not 240 as documented.

    The problem is documented in the following caveat:
    CSCub96331
    Unable to configure bbcredit on nexus for values bigger than 64.
    CCO Bug Toolkit:
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCub96331
    This is documented as part of resolved caveats for 5.2.1.N1.1b release
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_2_1_N1_1/Nexus5000_Release_Notes_5_2_1_N1.html#wp452031
    hope this helps,
    Vinayak

Maybe you are looking for

  • Two ISPs - A&B

    Hi Experts, I am stucked with a scenerio and requesting suggestion to make that functional. 1) We having two locations (eg Location A & B) with nearby distance. Both location are having WAN connectivities with different ISPs say ISP A & ISP B.. 2) At

  • CDROM Mount Solaris 10 x86

    BACKGROUND: In support of the U.S Navy, I've developed an IETM in XML and distributed it as PDF documents (in the Windows XP environment) meeting the current Military standards. My new tasking; However, is to ensure that this project can run on both

  • EBP SUS scenario ---sending a PO output from EBP to SUS

    Hi All, We are working on EBP SUS scenario with SRM 5.0 and ECC6.0 as the backend. We are creating a PO in the EBP which is to be sent to SUS for creating a POR in SUS from vendor. 1) How do we configure the PO output from EBP to SUS system? We could

  • How can I record the MASTER BUS?

    We use Audition to record programs for airing. I would like to record the output of the effects rack (after applying a limiter, etc). How can I record the output of the Master or other Bus? George Weston KSFR-FM Santa Fe, NM

  • Can I Call a 10g Form from 10 Report???

    Can I Call a 10g Form from 10 Report??? I'm using Developer Suite 10g Rel.2.