Fabric Interconnect ISSU support

I was asked by many cutomers about ISSU support for the UCS Fabric Interconnect ? They all know, that N5K (without L3 module) supports ISSU. Is it on the roadmap ?            

Hello wdey,
This is a different concept, the nexus control plane need keep relationships during the upgrade process.
In the UCS Fabric Interconnect, you have others tecnologies to provide high avability to the system overall. (fabric failover, UCSM cluster, FC multipath).
Although the N5K and the FI is almost the same box, the systems running are completly different. The ISSU in the FI is not necessary, as all functions can be transfered to the pair FI that remained running.
Richard

Similar Messages

  • Failed:Error disabled - SFP vendor not supported on Fabric Interconnect 6248UP

    We are connecting a FC-uplink on a Fabric Interconnect 6248UP to a MDS9124. On the Fabric Interconnect side we use a 8Gbps SFP (DSpSFP-FC8G-SW) on the MDS9124 side there is a 4 Gbps SFP.This should work when speed is at fixed speed 4 Gbps on both sides (I was told). When the SFP's and cabling is connected I get an error in the UCS manager on the FC-uplink port we are using:
    Failed:Error disabled - SFP vendor not supported.
    I cannot change the speed on the FC-Uplink ( I can only set user-label). The Fabric Interconnect is configured for FC on the last 8 ports and that is where the SFP for the storage is located (port 31).

    I have a similar problem.  I'm using port 1/41 and gets this output
    show system firmware expand | head lines 10
    UCSM:
       Running-Vers: 2.1(3a)
       Package-Vers: 2.1(3a)A
       Activate-Status: Ready
    Catalog:
       Running-Vers: 2.1(3a)T
       Package-Vers: 2.1(3a)A
       Activate-Status: Ready
    sh interface fc 1/41
    fc1/41 is down (Error disabled - SFP vendor not supported)
       Hardware is Fibre Channel, SFP is Unknown(0)
       Port WWN is 20:29:00:2a:6a:7e:7b:00
       Admin port mode is F, trunk mode is off
       snmp link state traps are enabled
       Port vsan is 1
       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
         0 frames input, 0 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
         0 input OLS, 0 LRR, 0 NOS, 0 loop inits
         0 output OLS, 0 LRR, 0 NOS, 0 loop inits
       last clearing of "show interface" counters never
    show int fc 1/41 transceiver details
    fc1/41 sfp is present but not supported
       name is CISCO-FINISAR  
       part number is FTLX8571D3BCL-C2
       revision is A  
       serial number is FNS17401NYG    
       FC Transmitter type is Unknown(0)
       FC Transmitter supports Unknown(0) link length
       Transmission medium is Unknown(0)
       Supported speeds are - Min speed: -1 Mb/s, Max speed: -1 Mb/s
       Nominal bit rate is 10300 MBits/sec
       Link length supported for 50/125mm fiber is 80 m(s)
       Link length supported for 62.5/125mm fiber is 20 m(s)
       No tx fault, no rx loss, no sync exists, diagnostic monitoring type is 0x68
       SFP Diagnostics Information:
                                         Alarms                 Warnings
    Is this a firmware problem?

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • Info about Cisco Fabric Interconnect 6140 Operating System

    Hello. We're looking for tech specs about Cisco Fabric Interconnect 6140 Operating System. For us is important to know if the os is NX-OS or not.
    Posted by WebUser Federica Rossi

    The underlying OS is built on NX-OS, but there is a lot of software running on top that is the actual UCSM itself.
    The UCSM software controls the NXOS portions directly - there is no ability to actually configure the system from an NXOS level.
    UCS-250-A(nxos)# sh ver
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Software
      BIOS:      version 1.5.0
      loader:    version N/A
      kickstart: version 5.0(3)N2(2.1m)
      system:    version 5.0(3)N2(2.1m)

  • No link between IOM port 2/2/3 and fabric interconnect B

    Hello
    I am trying to remove an uplink from an IOM to the fabric interconnect as its not required.  I have tried to reset the I/O module and re-acknowledge the chassis with no luck, it is still shown in the GUI with the error message as in the subject.  We are currently running 2.0(1s).  The kit isn't in production yet.
    Thanks for any help

    Yes i agress thats a pretty heavy approach to clean it. No if you left it there as it is, there would have been no operational issues. It would have just left this fault in the UCSM.
    ./Abhinav

  • 6500 / fabric interconnect

    Hi all,
    its any issue to get a fabric interconnect cluster connected to a 6504??
    becuase we are reviewing to get a connection betwen this 2 devices without any nexus devices.... is any problem with that??

    Hello ,
    Yes, you can connect UCS FI to 6500 switch.
    Make sure you configure STP port fast on the 6K switch ports connecting to FI ( if operating in End host mode ).
    Padma

  • 6248UP - Fabric Interconnect [id], HA functionality not ready

    Hello
    Having an HA issue with a FI cluster and have not able to find much info.
    The error I get (in the subject) leads me the the below URL with 5 steps to check.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/2.0/UCS_SEMs.html
    Step 1 - Not sure how to check this - Any input on this ?
    Step 2 - Have checked and even replaced the cables
    Step 3 - Checked and confirmed under Equipments -> Rack-Mounts -> Fex ( 2 x N2K-C2232PP-10GE)
    Step 4 - Checked and confirmed under Equipments -> Rack-Mounts -> Servers ( 4 x UCSC-C220-M3)
    Step 5 - New installation no active contract as yet.
    Anyone had similar issues, any assistance would be appreciated.
    Thanks

    Step 1
    Management all setup with initial setup-script, confirmed in extract from running config below
    scope fabric-interconnect a
         set out-of-band ip 172.16.1.4 netmask 255.255.255.0 gw 172.16.1.1
    scope fabric-interconnect b
         set out-of-band ip 172.16.1.5 netmask 255.255.255.0 gw 172.16.1.1
    scope system
         set virtual-ip 172.16.1.6
    Double confirmed via show commands below
    CTCPFIHA-A# scope fabric-interconnect a
    CTCPFIHA-A /fabric-interconnect # show detail
    Fabric Interconnect:
        ID: A
        Product Name: Cisco UCS 6248UP
        PID: UCS-FI-6248UP
        VID: V01
        Vendor: Cisco Systems, Inc.
        Serial (SN): SSI163308YF
        HW Revision: 0
        Total Memory (MB): 16232
        OOB IP Addr: 172.16.1.4
        OOB Gateway: 172.16.1.1
        OOB Netmask: 255.255.255.0
        Operability: Operable
        Thermal Status: Ok
        Current Task 1:
        Current Task 2:
    CTCPFIHA-A /fabric-interconnect # scope fabric-interconnect b
    CTCPFIHA-A /fabric-interconnect # show detail
    Fabric Interconnect:
        ID: B
        Product Name: Cisco UCS 6248UP
        PID: UCS-FI-6248UP
        VID: V01
        Vendor: Cisco Systems, Inc.
        Serial (SN): SSI16330FY1
        HW Revision: 0
        Total Memory (MB): 16232
        OOB IP Addr: 172.16.1.5
        OOB Gateway: 172.16.1.1
        OOB Netmask: 255.255.255.0
        Operability: Operable
        Thermal Status: Ok
        Current Task 1:
        Current Task 2:
    CTCPFIHA-A /fabric-interconnect # scope system
    CTCPFIHA-A /system # show detail
    Systems:
        Name: CTCPFIHA
        Mode: Cluster
        System IP Address: 172.16.1.6
        System Owner:
        System Site:
        Description for System:
    Step 2
    L1<>L1 L2<>L2 confirmed and new cables tried.

  • UCS-Fabric Interconnect Replacement

    Hello everybody,
    I have a UCS domain with a failed Fabric Interconnect and i have to replace this Fabric. For me there is no action to do in the configuration of the new FI i just have to add it in the existing domain and give it the IP address, but i have a question about the firmware version. is the firmware automatically installing in the new Fabric or have i to install it manually ? the firmware version in my domain is 2.2(1b).
    Thanks for the answer
    Best Regards 
    François Fiocre

    Hi Claudio
    I assume you talk about 10G copper, not 1G copper;
    and if 10G: CX-4 (Twinax) cables, or 10G Base-T ? 
    There is a 12-port 10GBASE-T module, but this is only supported on the Nexus 5596T so of no use on Nexus 5596UP switch, nor UCS FI.
    Anyway, it is a not recommended to connect UCS FI Uplinks to a Nexus 22xx ? just think about the oversubscription ! you would like to have as much bandwidth Northbound as possible.

  • Connecting Fabric Interconnect with MDS

    Dear Team,
    Kindly share how to configure connectivity between Fabric Interconnect and MDS
    what are the steps to be followed in establishing a successful connection between FI and MDS
    We have a tape library from IBM and trying to connect the same to FI via MDS and want this Tape library to be detected on the guest VM running windows 2008 on Esxi( Service profile with 2 vhba already added),we are trying using Fibre connectivity.
    Also please advice in which mode should we keep the FI (FC switching,end host etc)
    Thanks and Regards
    Jose

    Hi Jose,
    The common steps to configure FC on FI and MDS as following :
    1. FI configured in NPV mode, ensure that all FC uplinks and vHBA of Blades have been assigned on correct VSAN
        Verify if vHBA Flogi into the FI
        show npv flogi-table
        show npv status
    Example
    FI-A(nxos)# sh npv flogi-table
    SERVER                                                                  EXTERNAL
    INTERFACE VSAN FCID             PORT NAME               NODE NAME       INTERFACE
    vfc703    10   0x330001 20:00:00:cc:1e:dc:01:0a 20:00:00:25:b5:00:00:03 San-po102
    vfc711    10   0x330002 20:00:00:cc:1e:dc:02:0a 20:00:00:25:b5:00:00:02 San-po102
    Total number of flogi = 2.
    FI-A(nxos)# sh npv status
    npiv is enabled
    disruptive load balancing is disabled
    External Interfaces:
    ====================
      Interface: san-port-channel 102, State: Up
            VSAN:   10, State: Up, FCID: 0x330000
      Number of External Interfaces: 1
    Server Interfaces:
    ==================
      Interface: vfc703, VSAN:   10, State: Up
      Interface: vfc711, VSAN:   10, State: Up
      Number of Server Interfaces: 2
    2. Enable NPIV mode on MDS, configure the link to FI as F port. Assign this port into correct VSAN
        FI will become Node proxy, so verify if all vHBA have been detect on Upstream NPIV switch
    SW2(config)# sh npiv status
    NPIV is enabled
    SW2(config)# sh flogi database
    INTERFACE        VSAN    FCID           PORT NAME               NODE NAME      
    San-po102        10    0x330000  24:66:00:2a:6a:05:e9:00 20:0a:00:2a:6a:05:e9:01
    San-po102        10    0x330001  20:00:00:cc:1e:dc:01:0a 20:00:00:25:b5:00:00:03
                               [BLADE1-SAN-A]
    San-po102        10    0x330002  20:00:00:cc:1e:dc:02:0a 20:00:00:25:b5:00:00:02
                               [BLADE2-SAN-A]
    3. Configure zoning on the MDS (to make sure whether the issue on zoning or not, you can configure the default zone to permit)
    Example : zone default-zone permit vsan 1
    Verify the zoning on Upstream NPIV switch
    SW2(config)# SH ZONESet active vsan 10
    zoneset name ZONESET-VSAN10 vsan 10
      zone name INE-VSAN10 vsan 10
      * fcid 0x330001 [device-alias BLADE1-SAN-A]
      * fcid 0x330002 [device-alias BLADE2-SAN-A]
      * fcid 0x2a0000 [device-alias FC-SAN10]
    4. Ensure that vHBA of BLADE had been discovered on the storage device. Configure LUN masking on the storage
    I really don't have enough knowledge of VMware hahaha.....so can't help for troubleshooting the VM....Really sorry
    Thanks,
    Gofi

  • UCS Fabric Interconnect Stuck on Loader

    Hi, 
    I've UCS with 2 Fabric interconnect, today one of FI not working and from Console its boot but not respond to Ctrl+J or Crtl+Shft+R then Hung on "Loader>" ? 
    Any suggest Please

    Hi Balhomaish,
    for this particular issue I would recommend you to call cisco TAC and open a case with them. 

  • Fabric Interconnect 6248 & 5548 Connectivity on 4G SFP with FC

    Hi,
    Recently I came across a scenario when I connected a 4G SFP on Expansion Module of 6248 Fabric Interconnect at one end and at other end 4G SFP on 5548UP. I was unable to establish FC connectivity between both of the devices and the momemt I connected 4G SFP on Fixed Module of 6248 connectivity got established between both the devices
    I would like to know do I have to do any changes on FI's Expansion module to get the connectivity working or this kind of behivor is expected behavior
    Do let me know if you need any other information on this
    Regards,
    Amit Vyas

    Yes, On FI-B port 15-16 should be in VSAN 101 instead of 100, I have made that correction
    Q. are you migrating the fc ports from the fixed to the expansion module ?
         A: As off now I am not migrating FC port but in near future I have to migrate FC ports to Expansion module and I don't want to waste my time for troubleshooting at that time.
    Is my understanding correct, that you have 2 links from each FI to a 5548, no port fc port-channel ?
         A: Yes, your understanding is correct we have 2 links from each FI to 5548 and no FC port-channel is configured
    I will do the FC port-channel later on once I am able to fix the connectivity issue
    I will try to put 4G SFP on expansion module and will provide you output of "show interface brife"
    Following is the out of "show interface brife" from both 5548UP switches
    Primary5548_SW# show interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/29     100    auto   on      up               swl    F       4    --
    fc1/30     100    auto   on      up               swl    F       4    --
    fc1/31     100    auto   on      up               swl    F       4    --
    fc1/32     100    auto   on      up               swl    F       4    --
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  access down    Link not connected          10G(D) --
    Eth1/2        1       eth  access down    Link not connected          10G(D) --
    Eth1/3        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/4        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/5        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/6        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/7        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/8        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/1        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/2        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/3        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/4        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/5        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/6        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/7        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/8        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/16       1       eth  access down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           up     172.20.10.82                            1000     1500
    Interface  Vsan   Admin  Admin   Status      Bind                 Oper    Oper
                      Mode   Trunk               Info                 Mode    Speed
                             Mode                                            (Gbps)
    vfc1       100    F     on     errDisabled Ethernet1/1              --
    Primary5548_SW#
    Secondary5548_SW# show interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/29     101    auto   on      up               swl    F       4    --
    fc1/30     101    auto   on      up               swl    F       4    --
    fc1/31     101    auto   on      up               swl    F       4    --
    fc1/32     101    auto   on      up               swl    F       4    --
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  access down    Link not connected          10G(D) --
    Eth1/2        1       eth  access down    Link not connected          10G(D) --
    Eth1/3        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/4        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/5        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/6        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/7        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/8        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/1        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/2        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/3        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/4        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/5        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/6        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/7        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/8        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth2/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth2/16       1       eth  access down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           up     172.20.10.84                            1000     1500
    Interface  Vsan   Admin  Admin   Status      Bind                 Oper    Oper
                      Mode   Trunk               Info                 Mode    Speed
                             Mode                                            (Gbps)
    vfc1       1      F     on     errDisabled Ethernet1/1              --
    Secondary5548_SW#

  • Fabric interconnect and Native Vlan

    Hi
    I just want to ask a simple question
    is there any precautions with native vlan between the Switched infrastructure and the Fabric interconnect ?! 
    I mean can I use any vlan as a native vlan ex.999 "anything but not 1" ?! 

    As a security best practice on trunks carrying multiple VLANs you should not allow the native vlan on the line.  When you have a single VLAN going to a device, an end node for example, the port should be configured as an access port with a single data VLAN, and potentially a voice vlan if that will be used.  
    For example, our N5Ks have a trunk to each of our UCS interconnects.  We set the native VLAN on the n5k side to 999. 999 is not in the allowed list for the trunk then, so the native VLAN never makes it to the ucs.  On the ucs then, any server that can handle VLANs (esxi for example) we send only tagged VLANs -- no VLAN is marked native, thus accomplishing the same thing as we did for the n5k to FI link.
    It is recommended to not leave your native VLAN as 1 as best practice.  It's less of a concern if the native VLAN isn't in the allowed list, but to avoid mis configuration issues you should set it to another VLAN. 

  • How to recover from a software failure on the 6120 Fabric Interconnect

    Hi all,
    Had a software failure while upgrading the fabric interconnects. Does anyone know the process to recover from a software failure.
    Ive copied up the kickstart and system images, from the loader prompt ive booted the kickstart image and then loaded the system image but the fabric interconnect still reboots to the "switch(boot)" prompt.
    Thanks in Advance
    Darren

    Hi Robert,
    Thanks for the tips, but unfortunately im still stuck on the switch(boot): prompt.
    The bootflash: only has 2 files in it, the kickstart and system image.
    Each time i get the FI to the boot prompt, i can ping the device, but not access via the GUI. (i dont have a local copy of UCSM installed)
    What files should i have in the bootflash: for the FI to correctly load.
    below is a log of the FI as it loads the kickstart image from the Loader prompt.
    loader> boot bootflash:ucs-6100-k9-kickstart.4.1.3.N2.1.3c.bin                
    Booting kickstart image: bootflash:ucs-6100-k9-kickstart.4.1.3.N2.1.3c.bin....
    ....................................................................Image verif
    ication OK
    Starting kernel...
    Usage: init 0123456SsQqAaBbCcUu
    INIT: version 2.85 booting
    Starting Nexus5010 POST...
      Executing Mod 1 1 SEEPROM Test......done
      Executing Mod 1 1 GigE Port Test.......done
      Executing Mod 1 1 Inband GigE Test.....done
      Executing Mod 1 1 NVRAM Test....done
      Executing Mod 1 1 PCIE Test..............................done
      Mod 1 1 Post Completed Successfully
      Mod 2 Post Completed Successfully
    POST is completed
    Creating /callhome..
    Mounting /callhome..
    Creating /callhome done.
    Callhome spool file system init done.
    Checking all filesystems..... done.
    Warning: switch is starting up with default configuration
    Checking NVRAM block device ... done
    The startup-config won't be used until the next reboot.
    Loading system software
    INIT: Sending processes the KILL signalkernel daemon...don
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, 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
    switch(boot)#
    From here i can the load the system image, but it always fails and drops me back to the same prompt, output show below
    Uncompressing system image: bootflash:/ucs-6100-k9-system.4.1.3.N2.1.3c.bin
    Loading plugin 0: core_plugin...
    plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
    Loading plugin 1: eth_plugin...
    plugin_link_to_exec_path: plugin_path = /isan/plugin/1, tar_log = /isan/plugin_extract_log/1
    plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/etc/plugin_exclude.conf is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
    plugin_file_is_excluded_from_exec_path: /boot/etc/plugin_exclude.conf is excluded from linking
    Loading plugin 2: fc_plugin...
    plugin_link_to_exec_path: plugin_path = /isan/plugin/2, tar_log = /isan/plugin_extract_log/2
    plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
    INIT: Sending processes the TERM signal /boot/lib/ is excluded from lin
    INIT: (boot)# l
    INIT: Sending processes the KILL signaldaemon...don
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, 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
    switch(boot)#
    please let me know if you require any further information.
    Thanks in Advance
    Darren

  • Is there a way to see SAN luns from the UCS fabric interconnect.

                       Hello,
    I have recently added a 3rd and 4th vHBA to a B440 running RHEL5.
    Originally I had 2 vHBAs', and each created a path to 172 luns. (I was multipathed to 172 luns)
    Now I have added two additional vHBA's and my SAN admin assures me he has mapped, zoned and masked all 172 luns to the 2 new vHBA's.
    So, at this time I should have 4 paths to 172 luns....but I don't.
    What I see is 4 paths to 71 luns.
    I still see 2 paths to all 172 luns, but only see 4 paths on 71 of them.
    Its almost like my SAN admin either mapped or masked only 71 of the 172 luns to my 3rd and 4th path.
    Via the RHEL5 OS I have rescaned the FC paths, rebooted, done lsscsi, looked in the lowest level places for what devices are present on my FC channels, always I see 172 devices on the 2 original FC paths and 71 devices on the 2 new FC paths.
    My question is....is there a way to see all devices (luns) accociated with an vHBA from the command line in the Fabric Interconnect?
    My configuration is UCS w 2 FI's, using 8Gb FC connections to Cisco 9500 directors, to an EMC DMX4.
    Thanks in advance,
    Gene

    wdey,
    The link you supplied in your response is the answer.
    You can look at the devices on the FC boot paths, but not while the OS is running.
    I have a test server I could reeboot to try what you have in your document, and it does work.
    Too bad Cisco could not create a linux util rpm that would allow looking down the fabric while running. Im quit sure emulex has this kind of util, called HBAanywhere...at least for solaris.
    In any case, thanks for the link to your article, it was VERY good!
    My problem with seeing a shorter list of luns on 2 of my FC paths may get solved this afternoon by a change my SAN admin is going to make.. If it does I will post the fix.

  • Can the system name of the Fabric Interconnects be changed

    I need to change the system name of the Fabric interconnects
    I have given eg. EDCD
    the FI now have EDCD-A
    EDCD-B
    I need to change it to ... ECCD-A
    ECCD-B..
    is it possible ?

    Shyam,
    You can definitely do it and for sure is not disruptive and take effect right away.    Just go to the Admin tab> All> Management Interfaces> Name > Edit it with what you need > Apply.
    It is so easy and fast that if at the same time you have an SSH session, as soon as you change the name, the system makes the change on your SSH session too.
    Note: There is no need to look for the way to do this on each fabric. The name you are changing is for both FIs and the system will then add the xya-A or xya-B by itself.
    Rate ALL helpful answers.
    -Kenny

Maybe you are looking for

  • MSIE6 required for website; Safari3 not working

    I am unable to properly access my bank's website using Safari 3 as they only support MS IE6.0 . I tried using Tinkertool to emulate IE6 and it still didn't work. When I click on GO and another screen is supposed to pop up nothing happens. Allowoing p

  • OS 10.4 freezing

    Often, after my screensaver comes on, my OS freezes. I am unable to use the mouse and have to restart the computer. This seems to be the only situation where this happens. This type of thing is the reason I switched from Windows to Mac in the first p

  • Enterprise Compliance Report not showing any Pc

    I've MBAM going for a day or to, i can see computers in the computer compliance report if I type the test computers in; however, i dont see any computers under the Enterprise Compliance Report. i am running mbam 2.0 sp1 on 2012, and sql on server 08

  • Display output page by page in ALV

    HI all, can anyone pls tell me how to display output page by page in ALV this is urgent.. Thanks

  • SHIP TO PARTY NOT DEFINED FOR CERTAIN SALES AREA

    Hi ... I am creating a specific type of sales order in va01 by reffering a billing document . But soon after entering billing document no it is showing " SHIP TO PARTY NOT DEFINED FOR CERTAIN SALES AREA..." The sales area --- which it's showing in er