Benefits to vPC on 6200s (Fabric interconnects) in UCS

I'm a network guy, not VMware.  There are benefits to having the Nexus 5Ks vPC'd together and have a single port channel going upstream to a pair of vPC'd 7Ks.  I've heard this refered to as a 'bowtie' or 'figure 8'.
Are there similar benefits with the UCS 6Ks to the 7Ks or with the ensuing VMware cfg?  Like maybe simplifying the pinning to the uplinks.
Or is it just a plain bad idea?
Thanks,
Ken J

Ken,
The 6200's are not clustered switches as you might find with a pair of N5Ks/N7Ks.  Best practice for UCS uplinks in thei regard would be to create port channels on from each 6200 side, going up to separate N5K/N7Ks as VPCs.    This gives full mesh redundancy from each fabric.
From a VMware perspective, you would not do any specialized channeling at the vSwitch/vDS level.   You woud use the default vSwitch teaming method - which is Source-Base-On-Virtual-Port-ID.  This allows multlple uplinks connected to the same vSwitch wtihin VMware, without having to aggregate any of the links.  This would completely complement the UCS configuration.
Hope this makes sense, if not let me know.
These two deployement guide would be a good read for you:
http://www.cisco.com/en/US/docs/solutions/Enterprise/Borderless_Networks/Smart_Business_Architecture/February2012/SBA_Mid_DC_UnifiedComputingSystemDeploymentGuide-February2012.pdf
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns743/ns748/landing_dcServer-blade.html
Regards,
Robert

Similar Messages

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

  • 6200 Fabric Interconnect licensing with 2232 FEX

    I have searched and searched but can't find the document to answer this.  I know that every port on a 6248 or 6296 needs to be licensed to work whether it's Ethernet, FC, or FCoE. 
    We know it's supported and we want to connect a pair of 2232PP FEX up to our 6200 FI for C-series server connectivity.
    When connecting a 2232PP FEX up to a 6200 FI, there are a potential of 8 uplink ports from the FEX to the FI.  Do all 8 of those ports need to be licensed to work?  Do any of the new 32 ports that show up once the FEX is connected need to be licensed as well?
    Thanks!
    Chris

    Hello Chris,
    The ports on FI connecting to FEX ( Server ports ) needs to have licenses. The ports on FEX connecting to hosts ( rack servers - backplane ports  ) is not counted for licenses.
    You can use all of those back plane ports without worrying about licenses.
    HTH
    Padma

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

  • Can 6200 series Interconnects act as FC Fabrics?

    Greetings.
    I know with UCS 2.1 you can plug the FC SAN directly into the fabric without the need for an upstream mds switch for zoning.
    Can you plug the SAN directly into the interconnect as well as an external host (say some random rackmount server) and gain access to the luns on the SAN, or is there some magic with the interconnects where only the blades in the fabric can be zoned and see the storage?

    Samdeep,
    UCS can be directly connected with the storage array, however any Non-UCS server will not be able to access the array via fabric Interconnect. With UCSM 2.1 default zoning has been disabled.  and each initiator has to be specifically mapped to the target for zoning to work. Since UCSM only recognizes UCS blade and rackmount servers, only these type of servers can be zoned via UCSM to access the FC storage.
    Ali

  • Cisco UCS 6324 Fabric Interconnect Used as a FEX?

    Hi,
    Is it possible to use the Cisco UCS 6324 Fabric Interconnect as a FEX to uplink UCS 5108 Blade Chassis to Cisco UCS 6200 Series Fabric Interconnects? Thank you.

    How does it work if I want to add a second 5108 to a pair of 6324's? Having the 6324's replace the IOM (FEX) modules is cool but would you need to buy IOM's for the second chassis and then use up either 4 x 10GB ports or the 1 x 40GB or would I need to purchase 2 more 6324's?
    Thanks in advance.

  • 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

  • Fabric Interconnect B, management services are unresponsive

    Hi,
    We have configured Call Home option in UCSM and we are getting below error from Call Home option since last Saturday. We have open TAC with Cisco to troubleshoot this error but as per TAC "The error is a transient error from which the fabric interconnects can automatically recover."
    Below is the error messages we are getting
    E-mail-1:
    Subject:
    System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
    Body Message:
    System Name:System-A
    Time of Event:2011-12-27 17:54:09 GMT-00:00
    Event Description:Fabric Interconnect B, management services are unresponsive
    Severity Level:6
    E-mail-2:
    Subject:
    System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
    Body Message:
    <?xml version="1.0" encoding="UTF-8" ?>
    <soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
    <soap-env:Header>
    <aml-session:Session xmlns:aml-session="http://www.cisco.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next">
    <aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml-session:To>
    <aml-session:Path>
    <aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via>
    </aml-session:Path>
    <aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From>
    <aml-session:MessageId>1058:SSI1442BFRC:4EFA0641</aml-session:MessageId>
    </aml-session:Session>
    </soap-env:Header>
    <soap-env:Body>
    <aml-block:Block xmlns:aml-block="http://www.cisco.com/2004/01/aml-block">
    <aml-block:Header>
    <aml-block:Type>http://www.cisco.com/2005/05/callhome/diagnostic</aml-block:Type>
    <aml-block:CreationDate>2011-12-27 17:54:09 GMT-00:00</aml-block:CreationDate>
    <aml-block:Builder>
    <aml-block:Name>UCS 6100 Series Fabric Interconnect</aml-block:Name>
    <aml-block:Version>4.2(1)N1(1.43q)</aml-block:Version>
    </aml-block:Builder>
    <aml-block:BlockGroup>
    <aml-block:GroupId>1059:Serial Number:4EFA0641</aml-block:GroupId>
    <aml-block:Number>0</aml-block:Number>
    <aml-block:IsLast>true</aml-block:IsLast>
    <aml-block:IsPrimary>true</aml-block:IsPrimary>
    <aml-block:WaitForPrimary>false</aml-block:WaitForPrimary>
    </aml-block:BlockGroup>
    <aml-block:Severity>6</aml-block:Severity>
    </aml-block:Header>
    <aml-block:Content>
    <ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0">
    <ch:EventTime>2011-12-27 17:54:09 GMT-00:00</ch:EventTime>
    <ch:MessageDescription>Fabric Interconnect B, management services are unresponsive</ch:MessageDescription>
    <ch:Event>
    <ch:Type>diagnostic</ch:Type>
    <ch:SubType>GOLD-major</ch:SubType>
    <ch:Brand>Cisco</ch:Brand>
    <ch:Series>UCS 6100 Series Fabric Interconnect</ch:Series>
    </ch:Event>
    <ch:CustomerData>
    <ch:UserData>
    <ch:Email>[email protected]</ch:Email>
    </ch:UserData>
    <ch:ContractData>
    <ch:CustomerId>[email protected]</ch:CustomerId>
    <ch:ContractId>ContractID</ch:ContractId>
    <ch:DeviceId>N10-S6100@C@SSI1442BFRC</ch:DeviceId>
    </ch:ContractData>
    <ch:SystemInfo>
    <ch:Name>System-A</ch:Name>
    <ch:Contact>Name</ch:Contact>
    <ch:ContactEmail>[email protected]</ch:ContactEmail>
    <ch:ContactPhoneNumber>+00-0000000000</ch:ContactPhoneNumber>
    <ch:StreetAddress>Office Address</ch:StreetAddress>
    </ch:SystemInfo>
    </ch:CustomerData>
    <ch:Device>
    <rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0">
    <rme:Model>N10-S6100</rme:Model>
    <rme:HardwareVersion>0.0</rme:HardwareVersion>
    <rme:SerialNumber>SerialNumber</rme:SerialNumber>
    </rme:Chassis>
    </ch:Device>
    </ch:CallHome>
    </aml-block:Content>
    <aml-block:Attachments>
    <aml-block:Attachment type="inline">
    <aml-block:Name>sam_content_file</aml-block:Name>
    <aml-block:Data encoding="plain">
    <![CDATA[
    <faultInst
    ack="no"
    cause="management-services-unresponsive"
    changeSet=""
    code="F0452"
    created="2011-12-27T23:24:09.681"
    descr="Fabric Interconnect B, management services are unresponsive"
    dn="sys/mgmt-entity-B/fault-F0452"
    highestSeverity="critical"
    id="2036245"
    lastTransition="2011-12-27T23:24:09.681"
    lc=""
    occur="1"
    origSeverity="critical"
    prevSeverity="critical"
    rule="mgmt-entity-management-services-unresponsive"
    severity="critical"
    status="created"
    tags=""
    type="management"/>]]>
    </aml-block:Data>
    </aml-block:Attachment>
    </aml-block:Attachments>
    </aml-block:Block>
    </soap-env:Body>
    </soap-env:Envelope>
    We want to understand that what is the impact of this error and is there anything that we can do to prevent this error? Also want to know what might be the cause get this error?
    Let me know if anything else is needed from my side
    show-tech file uploaded.

    Padma,
    TAC Engineer sent below mail
    Hi Amit,
    I’ve checked through the show tech you’ve uploaded and have not found any indicators of errors for the error message you are seeing.
    As I mentioned in the call, the error is a transient error from which the fabric interconnects can automatically recover from. The recommended action is to wait for a few (10-15min) to see if the error clears automatically. If the error does not clear then we will need to do further troubleshooting. This error on its own is not a cause for worry. As you have HA in your system the management services would have failed over the to the other fabric interconnect and would not affect your system performance.
    We can leave the system under observation for a few days to see if other errors occur concurrently with this error.
    I will upload show-tech logs here, find my reply below
    Is the alert generated only for FI B or both FIs ->> Amit: Alert generated for FI-B only
    Any change in cluster state corresponding to alert time stamp ->> Amit: Unfortunately when this error generating we are unable to see the cluster state because of timing. If you can guide / suggest from any other location I can find the state that will be helpful
    Cluster physical link status ->> Amit: Cluster link is OK
    Does FI have any core dumps ->> Amit: I don't have any idea about this. How can check this ?
    Regards,
    Amit Vyas

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

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

  • 6248U Fabric Interconnect bootloader prompt

    Hi -
    I am setting up a couple of new 6248U Fabric Interconnects. When i console into them I noticed it at the following prompt.
    loader>
    So I would run a dir command and found this in the file listing
    ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin
    so at the prompt I would type boot  ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin
    after that boots I would get the following prompt:
    switch(boot)#
    These are not plugged into any chassis or i/o modules yet. I wante dto pre configure and put the management ip's and cluster ip into these FI's..
    What am I doing wrong

    Thanks for the reply. This is the result I got: (look at the prompt I got on the bottom)
    boot ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin ucs-6100-k9-system.5.0.3.N2.2.04b.bin
    Starting kernel...
    Usage: init 0123456SsQqAaBbCcUu
    INIT: version 2.85 booting
    I2C - Mezz absent
    sprom_drv_init_platform: nuova_i2c_register_get_card_index
    blogger: /var/log/isan.log: No such file or directory (2).
    Starting system POST.....
      Executing Mod 1 1 SEEPROM Test:...done (1 seconds)
      Executing Mod 1 1 GigE Port Test:....done (32 seconds)
      Executing Mod 1 1 PCIE Test:.................done (0 seconds)
      Mod 1 1 Post Completed Successfully
    POST is completed
    autoneg unmodified, ignoring
    autoneg unmodified, ignoring
    S10mount-ramfs.supnuovaca Mounting /isan 3000m
    Mounted /isan
    Creating /callhome..
    Mounting /callhome..
    Creating /callhome done.
    Callhome spool file system init done.
    Checking all filesystems....r. 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
    Uncompressing system image: bootflash:///ucs-6100-k9-system.5.0.3.N2.2.04b.bin
    Loading plugin 0: core_plugin...
    Loading plugin 1: eth_plugin...
    Loading plugin 2: fc_plugin...
    INIT: Entering runlevel: 3
    Exporting directories for NFS kernel daemon...done.
    Starting NFS kernel daemon:rpc.nfsd.
    rpc.mountddone.
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    INIT: Id "sm" respawning too fast: disabled for 5 minutes
    /isan/bin/first-setup: line 1663: /isan/etc/common_defs: No such file or directory
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    /isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
    INIT: Id "sm" respawning too fast: disabled for 5 minutes
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    System is coming up ... Please wait ...
    bash-2.05b#
    bash-2.05b#
    bash-2.05b#

  • 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

  • Fabric Interconnect vNic Failover

    We have the following Palo vNIC allocation for an ESXi host with 1000v in our vBlock:
    VLANs on vNIC #
    1: 14;
    2: 41
    3: 42
    4 20,12,22,24;
    5: 4,3,6
    Now the statement has been made to us that this would not provide a redundant networking configuration in the event of a Fabric Interconnect failure, and there must be pairs of vNICs carrying a VLAN – one that traverses the left FIC and one the right FIC. The suggestion to us was to only use 2 vNICs and carry all VLANs.
    My understanding is that with the M81KR vNICs, they can be set to ‘Fabric Failover Mode’ which will switch the accessible path in the event of a FIC failure seamlessly to the host. Removing the host managed failover and maintaining the HA within the fabric instead.
    Is this a correct deployment when using Fabric Failover?

    I think I have found the answer to my own question:
    https://supportforums.cisco.com/docs/DOC-14992

  • 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

Maybe you are looking for