Fc port 47 on fabric interconnect A oper state: failed, reason: Link failure: OLS received

Hi,
this UCS is connected to a qlogics SAN Fabric. We can see the LUN in ESX 5, but can't write. If we want write something to the LUN, we get the error above. We know that the qlogic Fabric is not supported by UCS, but its NPIV and i have a similar Installation which is doing fine.
Any Ideas?
Thanks, Marco

Hello,
NOS refers to "No operatioal sequence". Fibre channel has primitive seqences which are used to establish and maintain a link among the devices.
During the initial login phase,
1.Fiber channel switch sends a NOS signal
2.HBA connected to it sends an "OLS (offline sequence) signal.
3.Switch would send  a "Link reset"(LR)
4.HBA responds with a "LRR (link reset response)"
When a NOS received condition is met,
•A signal loss or sync loss condition is detected.
•The port is administratively shut down.
•The port is operationally down.
When the port status is in "link failure or not-connected" state, it means that the physical path is not completely active or no active signals has been sent. Check the cables/SFP's if pluged in properly and check the configuration (port type, speed and vsan settings) for further troubleshooting.

Similar Messages

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

  • Appliance port on 6248 Fabric Interconnects

    Is it possible to setup a storage device with a CIFS share on the 6248's through a port defined as an appliance port?  The GUI guide says this:
    "Appliance ports are only used to connect fabric interconnects to directly attached NFS storage."
    But what would be the difference if it were a CIFS share rather than an NFS mount?
    I'm trying to setup a storage unit that does both NFS and CIFS, but the backup software that I want to point to it through the FI's needs to have it as a CIFS share due to being a Windows platform.
    Any and all comments welcome.
    Thanks,
    Chad

    iSCSI, CIFS and NFS targets are all valid uses for the appliance port. 
    All the appliance port does is allow MAC learning on the interface. 
    Regards,
    Robert

  • Use UCS Fabric Interconnect 6100 with Extension Module E0060 (6 FC Ports)

    Hi Everybody,
    I have problem in my Architecture !!!   I THINK
    I want to use Extension Module E0060 (6 FC Ports) for UCS Fabric Interconnect 6100 for interconnectiong my Storage Array ( 2 Controlers with 2 FC Ports by cont.)  instead of use Nexus 5000 between FI 6100 and my Storage Array
    I tried to find details or case study for this way but No thing find !!!!!!!!!!!!
    I just find that th e best practices is to use Nexus 5000 but I have enough FC Ports with this Module ......  I THINK   but I m not an Expert
    Thanks for your help.

    Thanks for your answer Michael,
    But I really don't understand why I can't use the Module E0060 (6 FC Ports) in the FI 61xx instead of NEXUS 500 (I hope that's not commercial goal ) ????
    As you now the hardware architecture of FI 61xx is the same that Nexus 5000, the difference is that 61xx have features added and UCS Manager embedded.
    Now, If they have a features limited in 61xx like NPV or other things, I wil understand But until this moment I don't find Real ANswer in Cisco site of forum ( Al cisco documents mentionned that the best practices and the perfect design is to use 61xx and Nexus 5000 and MDS Switch between UCS and Storage Array ???????
    I Hope that you understand my problem

  • Port-channel Problem between Fabric Interconnect and N7K vPC

    Dear all,
    I have a problem with Port-channel Uplink between Fabric Interconnect with N7K using vPC
    This is my network topology for UCS Deployment
    In N7K I has configured vPC for red link and green link, at Fabric Interconnect A I has configured Port-Channel with member is Port 1 and Port 2, uplink is red link. At Fabric Interconnect B, I has configured Port-Channel with member is Port 1 and Port 2, uplink is green link.
    The show interface port-channel on N7K is good, every port-channel is up and have all member. But At Fabric Interconnnect, when I see on UCS Manager, the status of Port-Channel on Fabic A and Fabric B is fault with Additional Info: No operational member. Although all link is link up and I has status of Port-Channel is enable on UCS Manager. When I see the Properties of Port 1, Port 2 on Port-channel, I see the membership status is : individual. This mean port-channel is not up and no membership in this configuration. I want to using port-channel for load balance and plus more bandwidth for uplink to 20Gig. I don't understand why ?
    Please help me resolve this problem, I has send the capture screen of UCS Manager when I show status of Port-channel and Port-member in port-channel in attach items.
    Anyone can help me to resolve this, thanks you very much. Please reference attach items for more detail about fault.
    Thanks,
    Trung.

    Thanks Matthew very much,
    I has resolved this problem. The reason of problem is miss match protocol of port-channel between N7K and Fabric Interconnect. The Fabric Interconnect always use LACP protocol, but N7K using Port-channel mode on, that why the port-channel failed. I has configured LACP for port-channel in N7K, it has resolved the problems.
    Thanks,
    Trung.

  • Fabric Interconnect Uplink port channeling...

    Hi,
    We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
    However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
    Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
    I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
    Thank you                   

    Hello,
    You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
    --------  NXOS output -----------------
    FI-A(nxos)# sh run int port-channel 1
    interface port-channel1
      description U: Uplink
      switchport mode trunk
      speed 10000
    FI-A(nxos)# show int port-channel 1
    port-channel1 is up
      Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
      Description: U: Uplink
      MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
    FI-A(nxos)# sh int bri
    Port-channel VLAN  Type Mode   Status  Reason                    Speed  Protocol
    Interface                                                               
    Po1          1     eth  trunk  up      none                       a-10G(D)  lacp
    There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
    FI-A /eth-uplink/fabric # show port-channel detail
    Port Channel:
        Port Channel Id: 1
        Name: FIA
        Admin State: Enabled
        Oper State: Up
       Speed: 10 Gbps
        Oper Speed: 10 Gbps
        State Reason:
        flow control policy: default
    HTH
    Padma

  • 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

  • - No link between IOM port 3/2/2 and fabric interconnect B:1/18

    Specifically I'm trying to find out what the 3/2/2 means in - No link between IOM port 3/2/2 and fabric interconnect B:1/18

    This from the fault reference guide:
    "No link between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]"
    http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/UCS_SEMs.html#wp1306388

  • Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

    Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
    Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
    These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
    Thanks

    Hello,
    Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
    Padma

  • 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

  • Fabric Interconnect Ports Inventory

    Hello,
    I am looking togather inventory of all FI ports inventory with  below information. Is there any CLI command or Power shell script availble to gather this sort of information?
    SFTP type
    Serial Number
    Up/Down/SFP present status
    Server Port/Network Uplink/FCOE uplink
    Thanks
    Hetal Soni

    Hello Hetal,
    Following link has all the CLI commands you might be interested in.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/command/reference/1.1.1/command_reference_1_1_1_chapter4.html#wp248629215
    Shahzad

  • 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

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

  • 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

  • Why would Fabric Interconnects populate in fabric topology?

    If the Fabric Interconnects are configured in End-Host mode, why would it be sending management traffic through an F port link making it populate on our fabric topology.  We don’t have this on our existing Blades centers and would expect that we would be able to suppress this for these UCS interconnect devices.  These devices are not managed by the SAN teams and they would prefer them NOT to appear as though they are.
    Any advice?

    Release notes in 2.0(5a) showed 
    CSCua91672
    The fcoe_mgr hap reset will no longer cause FI reboot.
    http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_25363.html
    I am really never on the Fiber Interconnects to execute any CLI commands.  But a memory leak for some other reason would certainly be a possibility. The fact that its own High Availability process causes double reset in its own High Availability architecture is troubling. 

Maybe you are looking for