UCS Fabric interconnect reboot Question:

When you reboot an FI what is the expected behavior of UCS manager logs, faults, etc? What should we see to know what is a normal reboot and what are normal faults. We are trying to troubleshoot our FI's after an outage and can't find any info on how these normally log faults of this type.

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.

Similar Messages

  • 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

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

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

  • Fabric Interconnect 6120xp question

    I have two fabric interconnect 6120xp in cluster on one i find the ip in running config and on the partner i dont. It might be due to this i dont get the ipaddress of the fabric interconnect (shows as 0.0.0.0) on my san switch when querying fcns database. Any help is appreciated.
    lhr02-wxp00-fic01-B(nxos)# sh run |inc ip
    ip host lhr02-wxp00-fic01-B 10.255.96.78
      ip address 10.255.96.78/24
    lhr02-wxp00-fic01-A(nxos)# sh run |inc ip
    role name server-equipment
    lhr02-wxp00-fic01-A(nxos)#
    lhr02-wxif-san02#  show fcns database  npv
    VSAN 20:
    NPV NODE-NAME           NPV IP_ADDR     NPV IF  CORE SWITCH WWN         CORE IF
    20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/4   20:00:54:7f:ee:07:6e:80 fc1/6
    20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/2   20:00:54:7f:ee:07:6e:80 fc1/5
    lhr02-wxif-san01#  show fcns database  npv
    VSAN 10:
    NPV NODE-NAME           NPV IP_ADDR     NPV IF  CORE SWITCH WWN         CORE IF
    20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/1   20:00:54:7f:ee:17:eb:80 fc1/3
    20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/3   20:00:54:7f:ee:17:eb:80 fc1/4

    On the FI with the 0.0.0.0 ipaddress  run the sho npv inter info | inc IP.
    Next go into UCSM and select the equipment tab.Then pick the FI in question. On the right select General tab and then Access.
    What is the ipaddress? Does it also show 0.0.0.0 here as well?
    If it does, try changing it to the address you wanted and check it again.
    If that does not work then you can try to erase the config on that FI and reconfiguring it from the begining.
    Verify they it joins the cluster and HA is ready and the ipaddress is available.

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

  • 6248UP Fabric Interconnect Configuration Question

    We are in the middle of integrating VOIP into our enmvironment. The provider is asking for a VM to be built and a router to be connected directly to the VM. Can you integrate a GLC-T module into the 6248UP and connect the router directly to it. Configure the port and have that port provide access to the VM they are requesting? If you can, what should I configure the Interconnect port to be (Server or Appliance)? If this will not work, what will?

    Did you configure the port as 1G first ? btw. which FI are you using ? on a 62xx, each port can be 1 or 10G, on a 61xx, there are some limitations.
    Storage appliance port is used to connect IP storage Systems (NFS, iSCSI,....) not Switches / Routers.

  • UCS fabric Interconnect storage ports

    Hi experts,
    Is it possible in FI to connect storage switches directly to fixed FCOE ports rather than having  FC expansion module.
    Thanks,
    Mazhar

    Sorry think I replyed in error to your question. Was thinking strictly FC. If you are doing FCOE, well that is ethernet. Think you would need to go appliance port to plug straight into device without a switch between. Shouldn't need anything special.
    Craig

  • UCS Fabric Interconnect-switch mode

    Hi
    Can I connect my old HP server with DAS(to be used as a backup server) to a UCS FI operating in switch-mode-I guess I would need to connect the server to a network ports?
    Rgds
    Sumesh

    As of UCSM version 2.0 you no longer need "switch mode" to directly connect storage devices.  You can set devices as Appliance ports.  There's a wealth of community posts on setting this up.  Pre 2.0 you would need switch mode, which gets really messy - you're far better directly connecting storage with Appliance ports on 2.0 or later.
    As Eric mentioned, we only support Netapp & EMC devices for direct connect. 
    Please see the Storage Interop matrix for more detail.
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html#wp323848
    That being said, it doesn't mean it will not work, just that TAC would not be able to assist if you ran into issues.
    Regards,
    Robert

  • 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

  • UCS/Nexus and FCoE Question

    Hi, All:
    Can one connect an FCoE target directly to a Fabric Interconnect or a Nexus 5xxx FCF when in NPV mode and not connected to an FC switch for fabric services and still be able to have the initiator see the target and be able to provision storage accordingly?
    So, the scenario would be the following:
    a rack server with a CNA connected to a Nexus 5xxx FCF in NPV mode
    OR
    a blade server with a CNA connected to a UCS Fabric Interconnect (which is also an FCF) in NPV mode
    AND
    In either of the cases above, there is NO CONNECTION between the FCF and an FC switch.
    Will I be able to have the CNA (FCoE initiator) see the Strorage array (FCoE target)?
    Thank you

    Ganesh, your answers make sense, and given my understanding of FCoE and the FLOGI and PLOGI processes, I want to agree with you. BUT I have had a person who I believe to be very knowledgeable in UCS (former Cisco solutions engineer) tell me that you CAN connect an FCoE storage array directly to an FI FCoE port while the FI is in NPV mode and be able to provision storage, even if the FI is not connected to an FC switch. To me, that doesnt make sense because, in such a case, there is no appliance to provide FC services to support the FIP FLOGI and PLOGI processes - and therefore, how would an E_Node (VN_Port) be able to log into the fabric, get an FC-ID and FPMA, register with the name server and engage in peer VN_Port capability discovery? How would a server CNA even know that there is a storage array that is reachable without the PLOGI process?

  • UCS 6248 Fabric Interconnect loud fan RPM noise

    Hello,
    Our currently installed 6248 Fabric Interconnect pair are generating a loud FAN noise.
    Is there any way to reduce theirs RPM? So then can be quieter? The server room have proper air conditioning.
    Some logs as bellow:
    FABRIC-A(nxos)# show environment fan detail
    Fan:
    Module  Fan  Airflow        Speed(%)  Speed(RPM)
                 Direction
    1       1    Front-to-Back  60        15428
    1       2    Front-to-Back  60        11065
    1       3    Front-to-Back  60        14835
    1       4    Front-to-Back  60        10997
    2       1    Front-to-Back  60        15000
    2       2    Front-to-Back  60        11134
    2       3    Front-to-Back  60        14835
    2       4    Front-to-Back  60        11065
    Power Supply:
    Module  Airflow        Configured
            Direction      Speed (%)
    1       Front-to-Back  60
    2       Front-to-Back  60
    FABRIC-A(nxos)#
    FABRIC-A(nxos)#
    FABRIC-A(nxos)# show environment
    Fan:
    Fan             Model                Hw         Status
    Chassis-1       UCS-FAN-6248UP       --         ok
    Chassis-2       UCS-FAN-6248UP       --         ok
    PS-1            UCS-PSU-6248UP-AC    --         ok
    PS-2            UCS-PSU-6248UP-AC    --         ok
    Temperature
    Module   Sensor     MajorThresh   MinorThres   CurTemp     Status
                        (Celsius)     (Celsius)    (Celsius)
    1        Outlet     67            58           35          ok
    Power Supply:
    Voltage: 12 Volts
    PS  Model                Input Power       Power     Status
                             Type  (Watts)     (Amp)
    1   UCS-PSU-6248UP-AC    AC     780.00     65.00     ok
    2   UCS-PSU-6248UP-AC    AC     780.00     65.00     ok
    Mod Model                   Power     Power       Power     Power       Status
                                Requested Requested   Allocated Allocated
                                (Watts)   (Amp)       (Watts)   (Amp)
    1    UCS-FI-6248UP-SUP      492.00    41.00       492.00    41.00       powered-up
    3    UCS-FI-DL2             24.00     2.00        24.00     2.00        powered-up
    Power Usage Summary:
    Power Supply redundancy mode:                 Redundant
    Power Supply redundancy operational mode:     Redundant
    Total Power Capacity                             1560.00 W
    Power reserved for Supervisor(s)                  492.00 W
    Power currently used by Modules                    24.00 W
    Total Power Available                            1044.00 W
    FABRIC-A(nxos)#

    UPDATE
    I opened a TAC, then after several reviews of the LOGs and huge sh tech files, we concluded that all was normal. This loud noise is normal   and within in normal operational ranges.
    However as the server room is not fully acoustics proof and located near production  work desks, we managed to get a RMA for the fan modules for the version 2 modules which are MUCH quieter than V1 due new design.
    I have upload both pictures for comparison of the designs.
    Thank You!

  • Error: Failed to parse path in URl (Cisco UCS 6100 Series Fabric Interconnect)

    I have to shut down parts of my network due to an electrical outage this weekend. I have a Cisco UCS 6100 Server Fabric Interconnect. I am trying to backup the configuration. This is the command I am using create backup tftp://*.24.1.88 full-state enabled.  The error I receive is Error: failed to parse URI.  Which I believe URI means URL.

    Hi Parakiteiz,
    Looks like the format is incorrect and you have an extra 't' on the tftp command you provided.  Please take a look at the link below for configuration assistance.
    Creating backup operaiton.
    http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/cli/config/guide/1-1-1/b_CLI_Config_Guide_1_1_1/CLI_Config_Guide_1_1_1_chapter38.html#task_4704260519853629974
    Please let me know if this help

  • Cisco UCS 6200 Fabric InterConnects Needed?

    Currently looking to put Cisco UCS 5100 blades into our datacenter. Our core currently has a 7K with F2 48-Port blades with FCOE licenses. We currently have our ESXi servers terminating directly to the 7K for both 10G Ethernet and storage via FCOE. If we decide to replace our standalone rackmount servers with UCS blades, can we connect the blade chassis directly to the 7K, or are the 6200 fabric interconnects required? If so, what purpose do they serve. Thanks.

    Yes, fabric interconnect is required for a UCS blade solution; it can aggregate a maximum of 20 chassis a 8 blades, or a total of 160 blades.
    On the fabric interconnect runs UCS manager as a application, which allows you to do firmware management for the server farm (bios, I/O adaptor, CIMC,....); the concept of service profiles implements server abstraction and mobility across hardware.

  • Monitoring traffic between UCS fabric extenders and fabric interconnect?

    What is the best way to monitor the traffic between UCS fabric extenders (chassis) and fabric interconnect? Specifically I am looking for parameters to keep an eye on to determine when we may need to move from 2 links per fabric extender to 4 to handle greater IO needs.
    Thanks.
    - Klaus

    One way you could monitor usage is by looking at the interface stats just as you would for any switch uplink.
    Connect to the Cluster CLI
    connect NXOS
    Look at the input/output rate of your Server Uplink interfaces.
    In my example I'm using fixed ports 1 through 4 on my FI's connecting to the IOM of the Chassis.
    UCS-A(nxos)# show int eth1/1-4 | include rate
      30 seconds input rate 17114328 bits/sec, 1089 packets/sec
      30 seconds output rate 8777736 bits/sec, 693 packets/sec
        input rate 5.07 Mbps, 198 pps; output rate 1.03 Mbps, 99 pps
      30 seconds input rate 2376 bits/sec, 0 packets/sec
      30 seconds output rate 1584 bits/sec, 2 packets/sec
        input rate 1.58 Kbps, 0 pps; output rate 1.58 Kbps, 3 pps
      30 seconds input rate 2376 bits/sec, 0 packets/sec
      30 seconds output rate 31680 bits/sec, 20 packets/sec
        input rate 1.58 Kbps, 0 pps; output rate 30.89 Kbps, 18 pps
      30 seconds input rate 2376 bits/sec, 0 packets/sec
      30 seconds output rate 1584 bits/sec, 1 packets/sec
        input rate 1.58 Kbps, 0 pps; output rate 1.58 Kbps, 3 pps
    If you notice your two links pushing near 10G consistently, it might be time to add another 2 link.
    Other than this you can use SNMP to log the stats and look based on daily/weekly/monthly usage.
    Robert

Maybe you are looking for