UCS 6120 uplink and 1 Gbps

Similar Questions

• GLC - T allows to connect problem failed validation ucs 6120 and 2960 s (RJ45), are SFP

  Hi, all.

  I use GLC - T to connect ucs 6120 and cisco2960s (RJ45), are sfp validation doesn't have a problem.

  

  I did the speed at 1 G, and then I get error "connection not connected" even, I plugged the cable of nnetwork...

  

  Hello

  I recommend to see if the dealer you bought the glc - t from Exchange.  There seems to be problems with the SFP modules.

• Connection Cisco UCS 6120 FI directly to Cisco Catalyst 6500?

  I watch a lot of design with the Cisco UCS solution guide and everywhere it is Cisco Nexus 5000/7000 connects to the uplink ports of Cisco UCS 6120 FI with the benefits of technology to the vPC.

  How about connect Cisco UCS 6120 FI directly to 10GE ports in Cisco Catalyst 6500 (without VSS and VSS)? It is possible to design?

  If I use C6500VSS there will be port-channel of the aggregation of the UCS Nx10GE all the bandwidth?

  And what happens if I use C6500 (without VSS) - how it will be on the many links between UCS and two boxes C6500? It will be blocked by STP? A little on the other?

  Please explain to me, because we have only C6500 switches in our data center and want to test a Cisco UCS schassis.

  Yes, you can connect the 6120 s to cat6500s with or without vs. With VSS, you get a vPC as port channel where 2 links to a single 6120 can be connected to different 2 6500 s in a port LACP-channel.

  VSS is not necessary, you can connect a 10 G uplinks / 1 G of 1 or more of a 6120 at cat6500s. I you have 2 cat6500s (non - vss) and 2 uplinks by 6120, then you want to connect 1 cat6500-1 and the other to cat6500-2. I would recommend going ahead and creating a single port-channel port so that you can easily add the uplinks in the furture without interruption of service.

  Ideally, for non - vss, I would have 4 10 uplinks by 6120; 2 in a channel port cat6500-1 and 2 in a port in cat6500-2 channel

• Can I mix 6 Gbps and 12 Gbps SAS HDD?

  Hi all

  I use R350 server. As data are growing rapidly and my storage server is almost full. Therefore, I intend to buy more disk. Unfortunately, 6 Gb/s SAS HDD is end of line.

  Thus,.

  1. can I mix 6 Gbps and 12 Gbps SAS HDD in my R350 Server?

  2. If it is possible to do, I owe nothing to rebuild my RAID?

  For your information, I use RAID-5. My RAID controller is H730

  Help, please. Thank you.

  You can make use of the re - configure feature of the PERC H730 expand RAID 5. While in OMSA, go in->-> PERC H730-> virtual disks and storage under available tasks drop-down list, select reconfigure and Execute. See the schematic illustration below:

  

  On the next page, select the physical disk that you want to add and follow the instructions accordingly.

• UCS to UCS UCS 2104XP 6248UP AND to 2208XP of the UCS 6120XP

  Hello

  1. UCS 6248UP is compatible with the UCS 2104XP? AND
  2. The UCS 6120XP is compatible with the UCS 2208XP?

  Thank you.

  Hi Michael,

  Coupling of the FI with the IOM shouldn't matter.

  With 2208 the number for the day of plane ports increased to 32, while they are 8 with 2104.

  The only requirment is to have a minimal version of 2.0(1m)

  Please visit the link below to confirm the same.

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/release/notes...

  Thank you

  Majid

• 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

• Configuration of Nexus 5 k for SAN switching between UCS 6100 s and NetApp storage

  We strive to get our configuration of the UCS environment make start SAN LUN on our NetApp storage. We have a pair of Nexus 5Ks with the company / SAN license on them and the 6-port FC module. What to do to configure Nexus 5000 to operate as the SAN switch between the target storage and environment of the UCS?

  You see the 6120 WWPN on the N5Ks? What is the result of 'show flogi database' and 'show int br '.

  You have mapped the FC ports on the 6120 for the proper VSAN?

  NPIV is enabled?

• Is possible let activate domain multi UCS VM - FEX and sign up for the same vCenter

  Hi Experts,

  We have 7 domain UCS. But only a vCenter. Now, we want to enable VM - FEX on each UCS area and sign up for the same vCenter. Is - it work? I have found no description limit configuration on this relationship.

  Or we create 7 vCenter for each UCS area? (But I think it's not sense.)

  Best regards
  Meng-Yuan Hsieh (Nick)

  Hi Moua!

  I open a TAC case on that, and after that many discussions with Cisco, connecting several areas a single vCenter UCS is supported.  However, it turns out that Cisco failed to document this and how to make it work.  You will find that the procedures were written in old documentation for VN-LINK and others for VM - FEX.  This documentation shows that it is necessary to create new certificates, and it must match the key to expansion.  This is NOT true nor with the new versions of UCSM and vCenter.  Cisco, said they will update their documentation.

  Here are the steps that we took to connect two UCS areas for the same vCenter using default self-signed certificates.  I hope this helps...  Please mark this message as the right answer when you get a chance.  Thank you!!

  vCenter Version: 5.5

  UCSM Version: 2.2(5a)

  1. On the VM in UCS Manager tab, click VMware.
  2. Set up a key of the unique extension for every area of UCS.
  3. Click on "Configure VMware integration" on each area of UCS and export expansion of local storage.
  4. Install each UCS domain extensions in vCenter.
  5. After you install the extensions, back to UCSM and click Next where you left off in configure integration with VMware
  6. Run the wizard and after that it's over, areas of the UCS should now be connected to the vCenter.

  

• What is the difference between UCS - SD - 16 and UCS - SD - 16G =?

  Hello

  I have a few Cisco B200 m3 blades and will install 16 GB SD cards in them.  The documentation says that I need cards SD - UCS - 16G, but I received cards telling UCS - SD - 16 G =.  Does anyone know what, if any, difference the fact of '='?  They are the same card?  I have to make a large purchase of these cards and want to make sure that these are the correct type before ordering.  Thank you

  Hi @EBendixen,

  They are of the same type of cards are supported equal. The main difference is that:

  • SD cards with '=': are blank cards. The image that is required for the server can be downloaded on the map
  • SD cards without '=': are cards that come with the server image

  You can buy cards with this in mind. It all depends on if you already have the image of the server you need.

  Rgrds,

  Martin, computer scientist

• DLR Uplink and GSS internal transit same VXLAN cannot ping each other.

  Start with, I run NSX 6.2.2 firewall rules on 'allow all' to 'all' to 'all' "all protocols", in other words disabled...

  I have a VXLAN 5000 transit, with an uplink DLR interface attached to it, and an internal interface GSS in the appendix in which neither of the parties can ping to another. So for troubleshooting, I added 2 VM Windows attached to the same transit VXLAN 5000, a virtual machine is on ESXi host 1 and the other is on host ESXi 4. They can fine ping each other, and two virtual machines can ping both the uplink of DLR and internal interfaces of the GSS.

  This question has puzzled me because it makes no sense, why the DLR and the GSS cannot ping each other but 2 virtual machines that VXLAN can ping all adjacent devices. I can even put bridges on those virtual machines with a rule NAT on the GSS and those virtual machines can get internet through the GSS, but no matter what I try, the DLR cannot ping the GSS, and the GSS cannot ping DLR...

  I need to define a static route between the GSS DLR <>- but if I can't even answer ping interfaces I'm dead in the water.

  If I install virtual machines in a network LAN DLR interface such as WebApp and test for example database, I can ping throughout the DLR together until the IP DLR Uplink, but then he cannot ping the GSS internal.

  Does anyone have suggestions for troubleshooting? Test commands that I can run? I tried many things and then lots of websites with the troubleshooting steps. Everything seems fine, all green checks in the installation steps... All roads, MACs, ARP tables appear as expected when I run test on host computers commands and controllers. I don't know what is the cause except for a bug in the code...

  All ideas are welcome... Thank you

  UPDATE:

  Yes, so it has need of a static NAT rule on the GSS...

  In my environment, I added a SNAT rule on adapter: ESG_Uplink with 0.0.0.0/24 CBC-translation dst: 1.1.1.101 (my lab ESG IP Uplink).

  It works now... VM tenant box connected to WebApp portgroup (192.168.13.115) can now ping gateway DLR, through routing OSPF to the GSS and ping on physical bridge of...

  I learned a lot on this one... I'm not going to worry about why the static route, I tried first post didn't work, since I was the OSPF running instead (which is more appropriate for my laboratory for realistic scenario anyway), and the Foundation will now suffice to build the rest of this POC vRA / vRO lab...

  Thank you in any case, sometimes it's just nice to have someone to listen.

• 2960 x FPS-L-48 uplinks and flow

  I have a pile of (4) 2960 X FPS-L-48 switches that support SFP only this will be the uplink, through fiber, to another pile of (2) 2960 FPS - L - 48 FPS X switches only.  A port channel will be created between the two batteries.  I need to know what would be the flow on the channel of port between the batteries.

  Thanks in advance.

  The potential flow will be the combined speed of the interfaces in the etherchannel.

  Keep in mind, but that, for the same conversation between two end devices etherchannel uses the same physical link across it is so important to choose the right method of load balancing.

  The Guide configuration for more details-

  http://www.Cisco.com/c/en/us/TD/docs/switches/LAN/catalyst2960x/software/15-2_2_e/Layer2/configuration_guide/b_layer2_1522e_2960x_cg/b_layer2_1522e_2960x_cg_chapter_0100.html#con_1275731

  Jon

• layout error place vm - fex on UCS c-series and UCSM

  I seem to keep getting an error about the policy of the SRIOV bios settings, or "cannot be derived from the mac address of the virtual port" when I followed guides to configure the VM - FEX for ucsm and vmware 5.1.

  Y at - it fully equipped guides that go through more than just each "side" of the configuration (ucsm or vmware)?

  I want to know, from the beginning, what ucsm method should I use if I want ucsm manage the vlan / dvs in vmware so that I'm not "must continue to create VLAN in ucsm, adding them to the service and then profiles in vmware by creating networks of vm for VLANs and finally assign a virtual machine to use this new vlan."

  and then, assuming it's vm - fex, how to get actually configured in ucsm and how to properly configure the service for this purpose profiles.

  When you integrate vmware and ucsm, should existing virtual machines appear in ucsm, or that once they are set to use the dvs?  All I see is port dvs and thos profiles.

  All documentation I found simply shows a 'part' of this entire Setup, and I was not able to find a solution guide to describe how to configure the service profiles in ucsm to take advantage of vm - fex that work for me... I get the above mentioned errors when I try to associate the service with my ucs210 gear profile.

  Thoughts?

  Solved.

  Jason used VM-Pass through the adapter policy and did her properly configured static vNIC.

  Robert

• Dell TL4000 Tape Library on Cisco UCS 6120

  Hello

  We have Cisco UCS 5108 2 6120XP fabric of interconnection. We are running VMware on my Cisco blades. I have I need to connect my Dell TL 4000 LTO3 tape library this Cisco UCS so that I can configure a virtual machine with the EMC Networker software for backup of virtual machine data. When I connect the Cisco UCS library, it does not recoginize as tape drive.

  Please suggest how to set up the same.

  Thank you

  Amit,

  We do not support direct damage attach FC tape library to the FI currently.

  It may be a CF or CF storage end switch.

  . / Afonso

• NSX design with cisco UCS/fabric interconnects and Nexus switches

  Hi Experts

  I am new to NSX design and deployment and working on a project. We deploy NSX for applications of level 4 (web, app, db, DC). I use logic, DLR, ESG and DFW switches. I next we intend to use roads static confusion..

  1. do we cover all the VLAN from the virtual to the physical environment? for example mgmt VLAN, level vlans(web,app,db), vxlan transport vlan or it should be only a VLAN specific?  which means would be I have set all the VLANS in environment NSX in my physical switching environment?

  2 vds? don't we create not only 1 vds initially during the deployment of vcenter or more? Should we take any special consideration while deploying to the deployment of the NSX?

  3 static routes - we configure static routes on the DLR and the GSS? Should I use the default routes upstream? on the physical router should we be routing all subnets from virtual environment to the GSS.

  4. where and who should create virtual machines? Via vCenter or before the deployment of the nsx NSX?

  5. we have a level of domain controller. Should it be part of 3 or separate applications with allow any any rule on DFW?

  Thank you

  Sam

  (1) the VLANs which exist for physical Machines span the logical switch VXLAN NSX in the following cases:

  • If the current deployment there are physical Machines in the same Vlan and subnet IP with Virtual Machines. If this common Port Vlan group is migrated to a switch logic VXLAN Backed port group and not possible to change the IP addresses of the virtual machines, and then a bridge DLR (Distributed logical router) works as the conversion between Vlan physical and virtual VXLAN
  • If Conversion of P-to-V of the physical Machines continue on this Vlan

  VLAN which cover only the virtual machines or virtual local networks which cover only physical Machines must not be delayed.

  (2) for the deployment of the NSX, there may be more than 1 dVS or only 1 vDS according to the design. There may be another type of traffic other VXLAN base of virtual machines such as backup, storage, VMotion and the overall design, management, best practices apply here as well.  A requirement of the NSX is a common VDS that spans the entire Cluster. For each Cluster, this "common VDS' may be different. Yet once this VDS maybe a separate VDS dedicated VTEP or VTEP features functionality can be added to the existing VDS. It may be best to separate the VTEP vDS.

  (3) for the DLR, a default gateway is usually sufficient. If static routes are used, the GSS must then drive by default upstream and the static routes with the next hop of the DLR downstream for the subnets in the subnets IP VM logical switch. On the physical router static route to the VM, but also DLR - ESG logical subnets Subnet switch is required. Management of static routes is easier if route summarization is possible, or if necessary, close to the IP subnets, so it may be a good idea to use the dynamic routing such as Ospf or BGP protocol. There are also features of IP address management in Vrealize and other IPAM solutions if Automation is necessary for large and dynamic environments.

  (4) NSX has no functionality in the creation of the VM, it only creates Services network such as switches, routers, Firewalls, Load Balancing. The creation of the part VM continiues the same way as before. A point to note is maybe the logic is created appear as VXLAN named port groups on the VDS. NSX Manager creates groups of ports on the VDS, the only difference is that the name includes VXLAN. The virtual machine is like before added to this group of VXLAN Backed Port settings, or added to the logical switch from NSX Manager interface that appears again as a Plugin for VCenter. VCENTER is so point to create virtual machines and add these VMs to the logic is.

  (5) level of domain controller can be a separate layer, or other third party, may be preferable to upgrade separated except 3 applications. Usually, it's the same design without NSX. dFW rules can help protect the domain controller with allowing only ports of the virtual machine or physical Machines being admitted. dFW rules can apply to VXLAN based logical switches NSX so that VLAN based DVS Port groups because it's the kernel module.

• UCS &lt; 1.4.2b &gt;, N1K and uplink

  Hi all

  I have a UCS (cluster) connected in vPC mode to a Nexus 7010.

  UCS 4.1U1 VMware ESXi, N1K with EHM PC blade-based UCS NIC is 71KR.

  Question is what happens if the two uplink of interconnection fails? I mean maybe cut fibres or stuff like that. N1K channel will be still two active link?

  Maybe the redundancy is performed by re arping for finding a mac (i've got UCS in switch mode) address, but I'm not sure. I saw a feature in the new version for a link status tracking rising full failure handling system (how?).

  last question about redundancy... what happens if a UCS IOM resets? I have some traffic disruption?

  TNX

  Dan

  Dan,

  Just to be clear, check the following:

  -UCS in switch mode

  -Adapters M71KR

  -N1k using Mac-pinning (I guess)

  -Connectivity upstream of each FI is a VPC to a pair of N7Ks.

  In this case, the N1K has no visibility of uplinks UCS.  See all your hosts VEM are two uplinks for each host (a session each fabric interconnect.)  If one of the two uplinks fails on interconnection, traffic will be the uplink remaining on this FI re-hairpin.  If the TWO uplinks on a financial institution fail, then UCS will be down (called the link at the bottom) server links and traffic should be routed through the MEC is another uplink will the other.  You can change this behavior to follow links to Server (for local switching only) but the default action of UCSM's close links to corresponding server if there are no links available on a financial institution.   Make sense?

  Now, in the last version of N1K here (1.4) is a new feature called followed by the State of the network (NST) for use with VPC - HM (such as Mac pinning).  This feature will allow to test the connectivity of a VLAN sends a probe packet and expect to get fired on another group of liaison rising/sup.   If you have a network VLAN which SHOULD be identified, you can follow with TSN.  If the network becomes unavailable, you can choose to close the uplink and re - route traffic to an another uplink.  This is useful to detect failures beyond the first jump (which would be the interconnections) as a failure somewhere in your N7K level or beyond.

  Setup Guide: http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1284321

  White paper: https://communities.Cisco.com/docs/doc-20657

  Order code: http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/command/reference/n1000v_cmds_t.html#wp1295608

  For your last question about a failure/reset of the IOM, the cards corresponding to each blade will lose connectivity.  This is redundancy at the host level comes into play to reroute traffic.  In the case of your hosts N1K VEM, they would simply be re - route traffic on the access road to functional IOM of the chassis.

  Another point to consider is the M71 and M81 adapters support Fabric Failover.  He is tilting at the adapter level if there is a failure with any device between the adapter and uplink (like the IOM or FI).  Fabric failover is a configurable option adapter which re - will route traffic in Menlo ASIC adapters to the fabric in the 'other', such that the host will NOT see one of the two ports down.  Without switch fabric, a failure of a MOI or FI consider the adapter and this port would descend.  FF only adds a level of redundancy in the adapter without having to rely on any OS host grouping/failover.  M51KR, M61 KR and M72KR adapters do NOT support this feature.

  Kind regards

  Robert