Connection to a FEX N7K

Similar Questions

• Connect a mounting rack system UCS stand-alone server

  Hello

  I read somewhere on the dcoumentation this server from Cisco to stand alone as c210, c250 can be attached to the UCS Interconnect fabric. Can some expert cisco shed some light in there?

  I think I know,

  I'll have to plug the UCS FI External rack mount FEX and Cisco servers connecting to the FEX. Can someone clarify?

  What are the system requirements for the configuration above to UCS?

  I configured ports UCS FI as server ports and connect them to an external FEX with Twinaxial cable. But the ports are the link down. Cable Twinaxial is supported? I have to do additional configuration that we do when you plug a Nexus 5000 on a FEX?

  Any help would be apprciated.

  Thank you.

  The connection to a server in a stand-alone rack details are covered in this doc

  https://supportforums.Cisco.com/docs/doc-15034

  Dave

• RAW server host paths FEX & pin Network Port

  Hello

  I have a UCS - B Series chassis with 4 blades M2 B200 2 6124 FI connection with 4 Ports of server at each END.

  I wonder if someone can help me understand the BRIGHT paths & FEX "pin"?

  Here is a screenshot of the RAW paths for server 1 tab:

  

  From my understanding each blade has two host Ports of FEX (right & left) and PIN to FEX Network Ports (aka Server Ports).  Unlike SAN & LAN pinning I can't understand how to specify the Port of FEX pinning or control his behavior.

  The reason why I wonder it is because I was doing a Test Plan execution and pulled the right/1 & left/1 FEX silmultaniously Network Port.  This made me lose connectivity to my server 1 that has been pinned to these ports.  I would have thought the blade would "automatically" fail-to/use the following FEX Network available Port, either right/2, 3/right, right/4 or 2/left, left/3, left/4 but that was not the case.

  Can someone please explain?

  Thanks in advance,

  -Brian

  Pinning of the FEX/IOM of the blades is hardcoded by the FEX during initialization. It is not configurable by the user. Pinning is determined during initialization by number connects between the FEX and YEW.

  Now when you pull on a link between a FEX and FI we repin never links in case of failure. I'm not surprised that you have lost network connectivity when you pulled all the links. If you re - ack frame after pull you a FEX link will be repin connections, but we do ever automatically. Keep in mind that a re - ack will mean that the blades will have a network failure short while connections are repinned.

  With the second generation FI (6248) and the IOM (2208) second generation, you can create a channel of port between the FI and the IOM. In this case if a link fails the traffic will get re - balance between the other links.

  So, to summarize.

  GEN 1 material than anything is automatically pinned by the IOM. Failure of a link, we hear that these servers lose the network on this fabric connectivity. A chassis re - ack, the problem will be solved but could cause a short on the other servers network failure

  Material of Gen 2 has the ability to make a channel of port between the FI and the IOM. In this case by pulling a cable between the FI and the IOM should not cause a failure of the server network.

  Hope that helps.

  Louis

• C200M3, VIC 1225, Catalyst 4500 x

  Hello

  Everyone has set up a server with the installed VIC 1225 C200M3 and configured an etherchannel to a pair of Catalyst 4500 x?

  The server is freshly installed ESXi 5.1 standard vSwitch and two vNIC active/active and LB Hash IP value.

  As soon as the etherchannel is applied in the x 4500, the traffic of the host goes down.

  Have seen a few articles indicating that this will only work with the 1225 VIC if it s connected to a FEX or Nexus, is that correct?

  Concerning

  Hello Andreas,

  VIC in classical Ethernet (CE) interacts with any standards-based Ethernet switch.

  Can you please check the mac address of the interface vmkernel? Should one of the vNIC mac address?

  If so, the traffic could be running in default CSCuf65032

  As a work-around, you could recreate the vmkernel interface so that it would be the mac address which is not delong to vNIC.

  http://KB.VMware.com/kb/1031111

  HTH

  Padma

• Cisco UCS Manager does not discover C240 Server

  Hello, Cisco community!

  Currenlty UCS manager shows two interconnections of fabric and two extensions of fabric, but for some reason, my server isn't appear

  Birds seen are:

  I have my C240 connected with two 10GbE twinax cables, each going to a fabric Extender. (Total FEX 2)

  I have two 10GbE twinax cables connected each interconnections FEX fiber modulus in each tissue. (Total of 2 FI)

  The fabric interconnect ports L1 and L2 are connected to their corresponding ports. If their connected to each other.

  I run 'show cluster extended State' on the primary FI and this is what I get:

  FI - A # show cluster extended State

  The ID of the cluster: 0xebaad0e28ded11e3-0x86d4002a6a153d84

  Start time: Thu Feb 5 16:07:44 2014

  Last election period: Thu Feb 5 16:23:26 2014

  A: UPWARD ELEMENTARY SCHOOL

  B: UP, SUBORDINATE

  A: Member State UP, lead, State State PRIMARY, mgmt services: UP

  B: Member State UP, lead SUBORDINATES, mgmt services state: to the TOP

  State of PRIMARY_OK heartbeat

  INTERNAL NETWORK INTERFACES:

  eth1, up to

  eth2, up to

  HA IS NOT READY

  Any device attached to this fabric of interconnection

  After you set up server-side on each FI ports, the server still does not appear

  Any ideas are highly appreciated!

  -Alex

  Hi Miguel

  It seems to me, you're running a rather old version of UCS.

  In my screenshot you see the pool ext - mgt KVM on the LAN tab

  In an older version (I think< 2.1),="" this="" was="" under="" the="" admin="" tab.="" please="" have="" a="">

• Connect Fex 2208 to 6120 FI

  Hi all

  Is it possible to connect a chassis with modules e/s 2208 to a system with fabric UCS 6120 interconnections? If its possible, we need to update the firmware of UCSM 2.x?

  Thank you

  Kassim

  Hello Kassim,

  Yes, they are compatible.

  http://www.Cisco.com/en/us/prod/collateral/ps10265/ps10276/data_sheet_c78-675243.html

  And, Yes, we need code of 2.0.x on FI for 2208 module e/s.

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/HW/chassis/install/FRU.html#wp1337128

  HTH

  Padma

• It has been awhile, N7k now supports EvPC?

  As far as I know, in an environment of Nexus double 5 k, w/c are configured to the vPC. EvPC is available for FEX in double room, a single connection type for each of the switches to Nexus. Like the image below.

  1. jpg

  

  BUT, but but but, as documentation goes, model Nexus 7 k still do NOT support this kind of functionality that is, we cannot double home a FEX as 2 k nexus one or Nexus two, 7 k in vPC, w/c these switches NX7k are in vPC

  the question therefore, its been a while, it stand now?
  As far as my research goes, n7k still hate.
  My research, I met actually a post from 3 months ago, w/c says 'no' to my question T.T
  LINK: click ME

  Any guy entered? : D

  Hello

  You are right, but the Aru said the right thing. It supports dual domicile that see you in the diagram, but not an improved vpc.

  To be clearer, here is an explanation of the improved VVS - thanks to steve fuller on another post.

  "Improved VPC is a method that allows the connection of active way FEX using vPC between the FEX and switch upstream of Nexus and at the same time to connect a device to the host with a vPC FEX. interfaces"

  For more details, please see below.

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/op...

  Hope that this clearly indicates.

  Thank you

  Madhu

  Please note the useful messages *.

• VM - FEX and Nexus 1000v relationship

  Hello

  I'm new in the world of virtulaization and I need to know what the relationship between Cisco Nexus 1000v and Cisco VM - FEX? and when to use VM - FEX and when to use Nexus 1000v.

  Concerning

  Ahmed,

  Nexus 1000v is a Distributed Switch that allows you to manage your VEM, see this relationship as a supervisor-LineCard relationship.

  VM - FEX gives you the opportunity to bypass the vSwitch embarked on each host ESXi (VEM) for example.

  With VM - FEX, you see the virtual machines as if they were directly connected to the Parent switch (N7K / 5K for example), making it the parent spend management (cause there is more no vSwitch in the middle).

  This is a good topic that can be discussed and is difficult to summarize in a few lines, you read something in particular? any questions or doubts we can help clarify?

  -Kenny

• DualHoming 2248TP-E to of N7K?

  Hello

  What are the advantages and disadvantages of the double-Homing s Fex to N7K ruunning vPC mode. Double-homing will allow vPC connectivity for guests such as servers?

  Thank you

  Pradeep

  What are the pros and cons of Dual-Homing Fex's to N7K running in vPC mode.

  Is this - double / multiple a Nexus 2 K for a simple N7K or a double N7K in a vPC?

  If it is a simple N7K, it's OK, but, in my view, as a last resort.  If it's for a pair of N7K in a vPC, so I do not recommend him.

  Why not?  Because if you double - / stream a link 2 K with a pair of vPC N7K and you came across a rare case of brain then you you may have with your customers downstream turbulence.  I know that this design is a favorite among architects and designers, but in the wild, it is currently not recommended.   The 'best practice' proven is double - / multi-home the Nexus 2 K in a single chassis.

  With regard to my first statement as being a "last resort."  Why I say this is because of the cost of a single Nexus 7.  What happens if you hit the limit of the number of N2K the N7K can support?  If you want to very high speed (10 - or 40 Gbit/s) uplinks, then consider to terminate your N2248PQ to N6K and your N6K can go up the N7K via 40 Gbit/s (using N7K-M206FQ - 23 L).

  .

• Link 93180YC-EX and FEX

  Hi all

  We have 2 93180YC-EX with FEX 2348TQ, NXOS: 7.0 (3) I4 (2).

  And we have problem: fex ports do not properly communicate with connected devices.

  Like the ports of L3 or L2.

  We simplify our test configuration to resolve this problem and use to test a N9K and a FEX.

  So erase us config, perform the initial configuration, install and activate fex feature set, configure the port-channel for FEX and get fex module online.

  After that all ports configured as ports of L2 (access mode) and use the default vlan 1. We connect two hosts via unique to FEX ports link and they are unable to establish a connection and don't respond via ICMP.

  If configure us ports FEX as ports of L3, and connect hosts, we don't answer you via ICMP from all sides.

  However, if we use onboard N9K ports everything works fine.

  What we have to check, activate or configure to use FEX ports?

  Hello

  It looks like a configuration not supported.

  Note: The switches Cisco Nexus other than Cisco Nexus 9332PQ, 9372PX, 9372PX-E, 9396PX, and the 9500 series switches do not support FEXes (extensor of fabric).

  See release notes:

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus9000/SW/7-...

• FEX interface can be configured as L3?

  Hi FEX interface can be configured as L3? The uplink is connected to Nexus7710. Thank you

  Beginning with version 5.2 Cisco (1), you can configure a fabric port Extender (FEX) as an interface layer 3 for host connectivity, but not for routing. See the configuration of the Cisco Nexus 2000 series fabric Extender for more information on the tissue expanders.

  Reference http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/in...

  Kindly rate post useful.

• Connectivity between Interconnect and Nexus 2000 fabric options

  Hello

  I would like to know what models of fabric nexus 2000 Extenders can I use if I want to connect them to a pair of interconnections 6248UP fabric in a FEX deployment, so I can move between blade and rack servers service profiles.

  Thanks for your replies.

  Christian

  Christian,

  Take a look at this guide.  It should answer all your questions:

  http://www.Cisco.com/en/us/customer/docs/unified_computing/UCS/c-series_integration/ucsm2.0.2/b_UCSM_202_C-integration.html

  Kind regards

  Robert

• VM - fex mtu size

  Hello

  I need to set up mtu 9000 on dynamic vNIC (vm - fex vNIC).
  But I have found no guide on how to do it. I followed the guide of config vm - fex for KVM, but in the strategy of dynamic connection vnic I've not found any parameter to change the mtu size. By default all NICs for Dynamics become mtu 1500.
  Someone has documents or advice on how to set the mtu value dynamic vNIC 9000 (vm - fex)?

  Sent by Cisco Support technique iPad App

  Hi, Alois,.

  The MTU size can be changed at the interface of VM - FEX using a QoS policy in the port-profile.

  Here's how to change the MTU size when using Vvm - fex:

  (1) create a QoS policy on the LAN tab,

  (2) all by selecting a priority, choose the system QoS class that has an updated MTU size the configured.

  (3) create a profile port to be used by a NETWORK adapter to virtual machines (which, in turn, will get it one of the dynamic interfaces)

  (4) in the port-profile specify this QoS policy

  I hope this helps!

  . / Afonso

• 6200 fabric Interconnect license with 2232 FEX

  I've searched and searched, but could not find the document to answer this question.  I know that all ports on a 6248 or 6296 must be allowed to work either Ethernet, FC or FCoE.

  We know that it is supported and we want to connect a pair of 2232PP FEX until our FI 6200 for C-series server connectivity.

  When you connect a FEX 2232PP until a FI 6200, there is potential for uplink of the FEX of YEW 8 ports.  Should all 8 of these ports be allowed to work?  One of the new 32 ports that appear after plugging the FEX should be licensed as well?

  Thank you!

  Chris

  Hello Chris,

  Ports on FI connection to FEX (server ports) must have licenses. FEX ports connect to hosts (servers rack - basket bottom ports) is not counted for licenses.

  You can use all the ports in the back without worrying about licenses.

  HTH

  Padma

• FEX Uplink and Ports on the side Server

  I am very new to the environment of the UCS and having to return to the current fairly quickly. I decided to start with the chassis. But have a few questions.

  I hope someone can clarify how serverside ports are assigned less than ports uplink, 2204XP and 2208XP.

  My understanding is that the side ports server are assigned to the uplinks based on the number of uplink configured at the END.

  Once the FEX is initialized ports are hardcoded.

  Assuming 2 (6200 series) FI and 2 FEX (2204).

  2 each to their respective FI FEX uplinks

  8 blades width in the chassis.

  My understanding is;

  Uplink port 1 receive blades (1, 3, 5-7) and uplink 2 (2, 4, 6, 8)

  Question: Which ports are active for each blade and that FEX.

  For example the blade 1 assigned to Uplink on FEX A 1 with FEX B 1 uplink failover

  Blade 3 assigned to Uplink on FEX B 1 with FEX A 1 uplink failover

  Thanks in advance people...

  Hello and welcome to the community,

  "" My understanding is that the side ports server are assigned to the uplinks based on the number of uplink configured at the END.".

  Server ports are assigned to connections rising from ports either automatic (load balanced by available uplink interfaces) or manual pin (PIN LAN groups hard coded)

  2 fIs and IOM 2204 2 with 2 cables on each IOM: "UpLink port 1 receive blades (1, 3, 5-7) and uplink 2 (2, 4, 6, 8)" "< this="" is="" correct,="" odd="" blades="" through="" odd="" ports="" and="" even="" blades="" through="" even="">

  Which ports are active for each blade and that FEX.?

  In this case with a 2204, IOM provides 16 internal ports, 2 for each blade, and you can check which one is active with the command "Show software platform woodside m" mode FEX which is realized with the following commands:

  UCS # connect the IOM

  FEX-1 # display software platform woodside m

  

  You can also go to the vNIC itself in the "Servers" tab by going to the Service profile > network and then double click on in the vNIC and you will see the configuration:

  

  For example: blade 1 assigned to Uplink on FEX A 1 with FEX B 1 uplink failover

  Blade 3 assigned to Uplink on FEX B 1 with FEX A 1 uplink failover

  This will be the case if you have the 'discovery of the chassis/FEX policy' located in the 'grouping preference link' on 'None' instead of 'channel of Port "; If it is "Port Channel", I won't miss not until all other links fail in the same module e/s, see below

  

  NOTE: this option is valid only if your hardware is ALL second generation, in other words, it does not work with fabric 61xx interconnections or 2104 IOM

  I hope this helps, if it does, please note it.

  -Kenny

  Note ensure on the limitation of the function of the channel port between IOM and the tissue Message was edited by: Keny Perez