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

Similar Messages

  • Configure Nexus 7k for TACACS in Cisco ACS

    Hi,
    Please advise on how to configure Cisco Nexus 7k for TACACS to authenticate in Cisco ACS. Our Cisco ACS is getting users from the Active
    Directory.
    Please advise if the below config are acceptable:
    feature tacacs+
    tacacs-server key KEY
    tacacs-server timeout 20
    tacacs-server host 1.1.1.1 key KEY
    aaa group server tacacs+ TEST
        server 1.1.1.1
        use-vrf management
        source-interface mgmt0
    tacacs-server directed-request
    aaa authentication login default group TEST
    aaa authentication login console none
    aaa authorization commands default group TEST
    aaa accounting default group TEST
    aaa authentication login error-enable

    Hi,
    What OS version are u using on your servers?
    Craig

  • Configuring Nexus 5k for SAN switching between UCS 6100s and NetApp storage

    We are trying to get our UCS environment setup to do SAN boot to LUNs on our NetApp storage. We have a pair of Nexus 5Ks with the Enterprise / SAN license on them and the 6-port FC module installed. What needs to be done to configure the Nexus 5000 to operate as the SAN switch between the storage target and the UCS environment?

    I'm still not seeing the LUN on the NetApp device from my service profile. Here are the outputs from the two
    commands you referenced here along with a few other commands if they help at all.
    Port fc2/1 is the conneciton to the UCS 6100 with FCID 0x640004 being the vHBA in my Server profile.
    Port fc2/5 is the NetApp target. I have the LUN masked to the vHBA port name 20:00:00:25:b5:01:00:ff
    I have just the wwpn from the vHBA in my server profile and the wwpn of the NetApp target port zoned together. I'm not seeing any FC traffic at the NetApp though from looking at the statistics. Do I need to include something else in my zoning?
    Again, any assistance would be appreciated. This is obviously our first venture into FC...

  • 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

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

  • Urgent help: L3 daughter card for Nexus 5548

    Hi
    We have 2 Nexus 5548 which is in one vPC doamin. All the servers are teamed to these switches
    Requirement
    We have to install New L3 daughter card.(N55-D160L3-V2(=))
    I have gone through the Cisco websites and found that we have to do the following things
    1. software version:
    i Nexus 5548P Daughter Card (N55-D160L3)
    Before installing a Layer 3 daughter card (N55-D160L3) into a Cisco Nexus 5548P switch, you must upgrade to Cisco NX-OS Release 5.0(3)N1(1b) or NX-OS Release 5.0(3)N1(1c) and then install the card into the chassis. 
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_0_3_N2_1/Nexus5000_Release_Notes_5_0_3_N2.html
    2. license: 
    Also in order to enable this module following license should present on N5k device:
    LAN_BASE_SERVICES_PKG  - it's free and lifetime.
    https://supportforums.cisco.com/thread/2121574 
    I have 2 questions
    1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
    Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
    Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
    2- I have heard there is  a known bug which keep rebooting the switch after installation of L3 card
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
    has that been address in any version of license or NS-OS yet???
    Thanks heaps guys
    If the module is still offline when the requirements are met above, it could be a bug.(CSCtl45495) Try reloading the switch.

    1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
    Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
    Answer: -- Yes no reboot is required.
    Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
    Answer: As you are installing the license for the first time reboot of the box is not required.
    2- I have heard there is  a known bug which keep rebooting the switch after installation of L3 card
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
    has that been address in any version of license or NS-OS yet???
    Answer;--No this is not fixed yet.
    HTH
    Regards
    Inayath
    ********Please do not forget to rate the post if this info is helpfull.

  • Install pbr feature nexus 5548

    I am in need of Policy Based Routing for a new project.  At my core I have a couple of Nexus 5548s clustered together.  I go into configure terminal and run the command "feature pbr" and the return is invalid.  So I check the license with the command "show license usage" and I get the following output:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             No    -   Unused             -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
    LAN_ENTERPRISE_SERVICES_PKG   Yes   -   Unused Never       -
    From here I see that the enterprise package is installed and is unused.  How can I gain access to the enterprise features?  I found a document here that says "Ensure that you are in the correct VDC (or use the switchto vdc command). "  The switchto vdc command is also invalid.  What am I missing?
    Eric

    I realise this is a very old post however I wanted to post here in case others are still looking for this feature. PBR is now supported in version 6.0(2)N2(1) on Nexus 5k.
    RELEASE NOTES: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/release/notes/6_02/Nexus5500_Release_Notes_6_02.html#pgfId-472355

  • EEM on Nexus 5548

    Hi all,
    I'm new to EEM and we are investigating using it to solve some issues that we are having, However, I can't seem to find any definitive information which tells me whether EEM is available in the nexus 5548 switches. Can anyone here help to confirm if this is the case? If not yet avalable for the 5548s, are there any indications as to when it might become available?
    thanks,
    Ram

    Might want to try the 6.0(2)N1(2) and later code.  I have it loaded on a N6004 and EEM is available there.  It is of course the NX-OS flavor of EEM but it is there. 
    N6K-Switch# show ver | grep 'System version'
      System version: 6.0(2)N1(2)
    N6K-Switch# conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    N6K-Switch(config)# event manager ?
      applet       Create/Modify an Event Manager Policy
      environment  Configure an environment variable
      policy       Register a script policy and activate it
    N6K-Switch(config)# event manager
    Mike

  • 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

  • NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

    Hi All,
             Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
    The Server are connected to FEX.
    Attached the diagram.

    Hi,
    If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
    here is doc to follow:
    ISSU Support for vPC Topologies
    An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
    While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
    This example shows how to determine the vPC operational role of the switch:
    link:
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
    HTH

  • FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

    All,
    I have the following configuration and problem that I am not sure how to fix:
    I  have three Dell R910 servers with 1TB of memory and each has two  brocade 1020 CNA cards dual port.  I am using distributed switches for  the VM network and a second distributed switch for VMotion.  I have two  of the 10G ports configured in each distributed switch using IP Hash.   The management network is configured using a standard switch with two 1G  ports.
    The  Nexus configuration is we have two nexus 5548 switch connected together  with a trunk.  We have two VPC's configured to each ESX hosts  consisting of two 10gig ports in each VPC with one port going to each  switch.  The VPC is configured for static LAG.
    What  I am seeing is that after a few hours the virtual machines will not be  accessible via network anymore.  So if you ping the VM it will not work  and if you get on the console of the VM then ping the gateway then  nothing as well but if you try to ping another virtual machine on the  same host on the same VLAN then it will work so traffic is going through  the ESX backplane.  If I reboot the ESX host then things will work  again for another few hours or so then the problem repeats.
    The version of vSphere I am using is ESXi4.1
    Please assist I am stuck.
    Thanks...

    Here is the link for Nexus and Brocade interoperability Matrix
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
    usually this table would show those models those have been tested and verified
    However I do not see  Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

  • Nexus 5548 and Define static route to forward traffic to Catalyst 4500

    Dear Experts,
    Need your technical assistance for the Static routing in between Nexus 5548 and Catalyst 4500.
    Further I connected both Nexus 5548 with Catalyst 4500 as individual trunk ports because there is HSRP on Catalyst 4500. So I just took 1 port from each nexus 5548, make it trunk with the Core Switch (Also make trunk from each Switch each port). Change the speed on Nexus to 1000 because other side on Catalyst 4500 line card is 1G RJ45.
    *Here is the Config on Nexus 5548 to make port a Trunk:*
    N5548-A/ N5548-B
    Interface Ethernet1/3
    Switchport mode trunk
    Speed 1000
    Added the static route on both nexus for Core HSRP IP: *ip route 0.0.0.0/0 10.10.150.39 (Virtual HSRP IP )*
    But I could not able to ping from N5548 Console to core Switch IP of HSRP? Is there any further configuration to enable routing or ping?
    Pleas suggest

    Hello,
    Please see attached config for both Nexus 5548. I dont have Catalyst 4500 but below is simple config what I applied:
    Both Catalyst 4500
    interface gig 3/48
    switchport mode trunk
    switchport trunk encap dot1q
    On Nexus 5548 Port 1/3 is trunk
    Thanks,
    Jehan

  • 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

Maybe you are looking for