UCS FI wiring

Similar Questions

• UCS Fiber Channel FI for San switch wiring & config

  My question is about the correct wiring & vSAN configuration by the UCS FI switch San (Cisco MDS).

  Currently my wiring is as follows:

  Fi1 port 25 - SW1 port 3

  Fi1 port 26 - SW2 port 3

  Fi2 port 25 - SW1 port 4

  Fi2 port 26 - SW2 4 port

  On the side of the switch San, our guys of storage configured vlan10 SW1 and SW2 as vlan20. For this reason, I was not able to have a vSAN by FI, I read is recommended, because the VLAN switch cross FIs. Now, when I created vHBAs I have 4 vHBAs per server, 2 by IFS by vlan if I want redundancy with a switch or a loss of FI.

  Question: Is this the correct configuration on the side of the SAN switch? Do I actually create 4 vHBAs per server? I do not have my incorrect wiring & I should just be linking FI1 to SW1 on two ports & FI2 to SW2?

  Help or advice would be appreciated!

  ~ Tara

  Hi Tara,

  There are two ways of wiring of your SAN infrastructure.  It boils down to a design decision. Traditionally the SAN admins prefer to keep their separate/isolated tissue.  In this design THAT MDS-1 only connect to FI - A and MDS-2 would connect only to the FI - B.

  Another option is to connect each MDS at each END.  This gives each FI SAN fabric access and allows to create double VSANS (that exists on each FI) rather than separate them.

  You don't need four vHBAs by UCS Server - some adapters support no more than two in any case.   What you do is create two vHBA by the Service profile, each host will have access both to VSAN 10 and 20.  What you can do is to shift your tissue of vHBA while 1/2 access your Service VSAN 10 via FI - profiles and the other half access VSAN 10 FI - B.  This will help to distribute the load accordingly.

  E.g.

  First 1/2 of SPs

  vHBA0 - VSAN10 - fabric-A

  vHBA1 - VSAN20 - fabric-B

  1/2 second of SPs

  vHBA0 - VSAN20 - fabric-A

  vHBA1 - VSAN10 - fabric-B

  As you can see a bit of a manual balancing can act.  The best scenario would be to isolate (re-cable) to your network SAN fabrics according to the traditional SAN design above.

  Kind regards

  Robert

• Max UCS C-Series rack servers

  Is there a document that indicates the maximum number of rack servers supported in UCS C-series? I did some research and did not happen to a hard number as there are blades.

  Thomas

  Currently with 1.4, the supported maximum is 19 (with a 6120) / 39 (with a 6140).

  If you look at the attached picture, it shows the wiring necessary for the integration of the series c with UCSM.

  Management (CIMC) passes through a 2248 while data cards (10 Gig ports) go directly into each of the 6100's.

  Assuming no B series and 1 connection to the each FI 2248, you end up with ports 19 or 39 for a 6120 and 6140 data respectively as only fixed ports on YEW can be Server deal with. It is here that the limitation origin currently.

  Thank you

  -Matt

• Vsan UCS - Nexus - questions

  Hello

  I need some advice on setting up a SAN between a UCS and link configuration, I checked a large number of document, but nothing is clear (to me) to understand the correct configuration and apply.

  First of all, I have an err - disable on nexus (VLAN L2 problem) and ucs (SFP incompatibility).

  I have 2 (twinax cables) connected between 5548UP ucs6248 and nexus

  Should what configuration I configure on the NGC? FC or fcoe

  Should what configuration I configure on the Nexus? CF or vfc

  Can I use a twinax cable or a wired fiber sfp module?

  Use the switch or NPIV mode?

  using the switchport E or F?

  Or I need a link that explains the process to follow.

  Concerning

  Eric,

  Do you have a chance to look at the pdf that I provided in my previous email. He has the list of SFP supported on YEW, SFP part number can be found on the FPS itself.

  . / Afonso

• FI/IOM: better design of wiring

  In our UCS system with 2 chassis, we have 2 links between the IOM 2208 and FI 6248:

  For an IOM, what is the best design wiring:

  -connect theIOM to Eth1/1-2

  -connect the IOM to Eth1/1; Eth1/8

  ... On average, it is preferable to use the same Unified Port Controller (UPC) ASIC [called Carmel, I think only] or use 2 different UPC?

  and why?

  THX.

  Nicolas.

  The 6200 and 2208 the best design option is actually to ensure all the server bindings (FI <->IOM) are related to the SAME UPC (carmel ASIC).  This will give you the number alive at the system max.  By spreading your connections through different UPCs may increase redundancy, but it will decrease your bright max County at the same time.

  If you want to see UPC mapping, you can connect to the CLI, connect to the NXOS context and run the following command:

  FI-A-6248-A (nxos) # display all-hardware ports internal carmel

  News Port of Carmel:

  name | Journal | Auto | Mac | flag | SMA | Opr | m:s:l | IPT | Fab | xcar | xpt | if_index | diag | ucVer

  -------+---+---+---+----+---+---+-----+---+---+----+---+--------+----+-----

  xgb1/1 | 0 | 0 | 0 | B7 | tell | DN | 0:0:f | 0 | 92. 0 | 0 | 1A 000000 | pass | 0.00

  xgb1/2 | 1. 0 | 1 | B7 | tell | DN | 1:1:f | 1. 88. 0 | 0 | 1A 001000 | pass | 0.00

  xgb1/3 | 2. 0 | 2 | B7 | tell | DN | 2:2:f | 2. 93. 0 | 0 | 1A 002000 | pass | 0.00

  xgb1/4 | 3. 0 | 3 | B7 | tell | DN | 3:3:f | 3. 89. 0 | 0 | 1A 003000 | pass | 0.00

  xgb1/5 | 4. 0 | 4 | B7 | tell | DN | 4:4:f | 4. 90. 0 | 0 | 1A 004000 | pass | 0.00

  xgb1/6 | 5. 0 | 5 | B7 | tell | DN | 5:5:f | 5. 94. 0 | 0 | 1A 005000 | pass | 0.00

  xgb1/7 | 6. 0 | 6 | B7 | tell | DN | 6:6:f | 6. 95. 0 | 0 | 1A 006000 | pass | 0.00

  xgb1/8 | 7. 0 | 7 | B7 | tell | DN | 7:7:f | 7. 91. 0 | 0 | 1A 007000 | pass | 0.00

  xgb1/9 | 8. 1. 0 | B7 | tell | DN | 0:0:f | 0 | 80. 0 | 0 | 1A 008000 | pass | 0.00

  xgb1/10 | 9. 1. 1 | B7 | tell | DN | 1:1:f | 1. 87. 0 | 0 | 1A 009000 | pass | 0.00

  xgb1/11 | 10. 1. 2 p | B7 | en | up | 2:2:f | 2. 81. 0 | 0 | 1a00a000 | pass | 0.00

  xgb1/12 | 11. 1. 3 P | B7 | en | up | 3:3:f | 3. 86. 0 | 0 | 1a00b000 | pass | 0.00

  xgb1/13 | 12. 1. 4 P | B7 | en | up | 4:4:f | 4. 82. 0 | 0 | 1a00c000 | pass | 0.00

  xgb1/14 | 13. 1. 5 p | B7 | en | up | 5:5:f | 5. 85. 0 | 0 | 1a00d000 | pass | 0.00

  xgb1/15 | 14. 1. 6 P | B7 | en | up | 6:6:f | 6. 83. 0 | 0 | 1a00e000 | pass | 0.00

  xgb1/16 | 15. 1. 7 p | B7 | en | up | 7:7:f | 7. 84. 0 | 0 | 1a00f000 | pass | 0.00

  xgb1/17 | 16. 2. 0 p | B7 | en | up | 0:0:f | 0 | 75. 0 | 0 | 1A 010000 | pass | 0.00

  xgb1/18 | 17. 2. 1 | B7 | tell | DN | 1:1:f | 1. 76. 0 | 0 | 1A 011000 | pass | 0.00

  xgb1/19 | 18. 2. 2 | B7 | tell | DN | 2:2:f | 2. 74. 0 | 0 | 1A 012000 | pass | 0.00

  xgb1/20 | 19. 2. 3 | B7 | tell | DN | 3:3:f | 3. 77. 0 | 0 | 1A 013000 | pass | 0.00

  xgb1/21 | 20. 2. 4 | B7 | tell | DN | 4:4:f | 4. 78. 0 | 0 | 1A 014000 | pass | 0.00

  xgb1/22 | 21. 2. 5 | B7 | tell | DN | 5:5:f | 5. 73. 0 | 0 | 1A 015000 | pass | 0.00

  xgb1/23 | 22. 2. 6 | B7 | tell | DN | 6:6:f | 6. 72. 0 | 0 | 1A 016000 | pass | 0.00

  xgb1/24 | 23. 2. 7 | B7 | tell | DN | 7:7:f | 7. 79. 0 | 0 | 1A 017000 | pass | 0.00

  xgb1/25 | 24. 3. 0 | B7 | tell | DN | 0:0:f | 0 | 71. 0 | 0 | 1A 018000 | pass | 0.00

  xgb1/26 | 25. 3. 1 | B7 | tell | DN | 1:1:f | 1. 64. 0 | 0 | 1A 019000 | pass | 0.00

  xgb1/27 | 26. 3. 2 | B7 | tell | DN | 2:2:f | 2. 65. 0 | 0 | 1a01a000 | pass | 0.00

  xgb1/28 | 27. 3. 3 | B7 | tell | DN | 3:3:f | 3. 70. 0 | 0 | 1a01b000 | pass | 0.00

  29/MFC1 | 28. 3. 4 | B7 | tell | DN | 4:4:0 | 4. 66. 0 | 0 | 0101 c 000 | pass | 0.00

  MFC1/30 | 29. 3. 5 | B7 | tell | DN | 5:5:1. 5. 69. 0 | 0 | 0101 d 000 | pass | 0.00

  MFC1/31 | 30. 3. 6 | B7 | tell | DN | 6:6:2 | 6. 67. 0 | 0 | 0101e000 | pass | 0.00

  MFC1/32 | 31. 3. 7 | B7 | tell | DN | 7:7:3. 7. 68. 0 | 0 | 0101f000 | pass | 0.00

  sup0 | 32. 4. 4 | B7 | en | DN | 4:4:0 | 4. 62. 0 | 0 | 15020000 | pass | 0.00

  sup1 | 33. 4. 5 | B7 | en | DN | 5:5:1. 5. 59. 0 | 0 | 15010000 | pass | 0.00

  The column with what you fear is a labeled "car" (carmel).  As you can probably see the first column corresponds to the Interface.

  FYI - I have yet to see a controller failing port ASIC.  Its MTBF is well beyond many other components including SPFS, cables, etc.  I don't sweat worrying about redundancy of ASIC level in this regard.

  Kind regards

  Robert

• UCS General questions

  Hello

  I have a few questions about UCS. Do not hesitate to reply to all the of them, thank you!

  1. What are the main benefits of using FCoE vs FC to UCS?
  2. can someone point me to performance data of FCoE vs FC in the UCS?
  3. What is the difference between the fixed modules and expansion on made them other than being able to replace the plug-ins? A difference that I noticed is that when you select "Configure the Ports unified" on the FI, it says that all FI will have to reboot if you use fixed ports, but the port expansion module can restart independently. There are other differences between the fixed modules and expansion?
  4. What is the best practice for creating organizations? The limit is usually the data center? What are the benefits for the combination of several data centers (which could be in the same geographic area) into a single entity?
  5. most people configure UCS of 'root', or they always configuring everything in specific OUs they create?
  6. This setup of most of the organizations mentioned here video separates VSAN for each fabric (A & B)
  a. How are the fiber channel pass setup to accommodate the VSAN on made them?
  7. is there an advantage to having separate VSANS / VLAN ID between fabric A and B? A few examples I see use the same ID of the VSAN on both fabrics, while others are not
  8. in this diagram (link), there are 4 connections from the FIs to the San. Each FI is wired to each storage processor. In this configuration, how it the SAN be configured - ALUA?
  9 (for ESXi hosts) what are the advantages/disadvantages of creating a model vNIC for each tissue, compared to one model for each vmnic vNIC?
  10. under what circumstances should you not check "Activate the failover" for models vNIC for esxi hosts?

  11. What is the best practice for the connection of FEX-to - IOM to the title of the material > policies > policies > chassis/FEX discovered political? Many companies set it up as a Port channel or not?

  (1) complex is the best I can say.  For us, we decided to stay with native CF that we already have the buildout FCC native. Our network group is for us to move to FCoE (we use N5K for our data center fabric switches).  But for our SAN group, we all all comfortable with native CF right now and didn't want to convolute our UCS deployment at a crossing FCoE.

  2) UCS FCoE, comes from the back of the interconnection.  There is no difference in performance. Once FC lands to interconnection, interconnection opens the package and converts it to the headers of FCoE, laying on a VLAN you configure (must be a VLAN unique, it will leave you not overlap with production VLAN defined in UCS already) and sends it to the VIC. The VIC then opens the package FCoE and hands to the BONE as if it were native fiber channel.  The difference in performance between the two is negligible.

  (3) the fixed module is controlled a.  When you change the unified ports any interconnection charges.  When you load a plug-in only the plug-in restarts if you change its setting unified ports.  Another thing to note when buying a plug-in you get you license additional ports that can be used everywhere where (it doesn't have a plug-in port license).  Other than that, the performance and the functionality is the same as fixed.

  (4) create us organizations for each type of OS because different groups managing different OS'. For example, we have an org for VMare, one for Linux, for windows, and then a special one oracle for our DBAs. We then assign permissions via AD to local so the groups have access to their servers with a minimum of effort on our part.

  (5) while root except if necessary below (haven't run this yet)

  (6) as a "best practice", you should always have two separate fabrics. UCS must put the FCoE VLAN fabrics.  To avoid confusion, it is best to put each fabric in its own VSAN. For example, we run our SAN fabric production in VSAN around 10 and FCoE VLAN 3210.  SAN fabric B is to VSAN 11, FCoE VLAN 3211.
  (6A) the prospect of a MDS/Nexus that you put in place a "f-port trunk." Newspapers of the UCS in the fabric as a nport with NPIV (ucs connects and then tells the fiber switch "also, these additional WWPN are also on this port, I just connected to, send their data to me").  You put the f-port channel you create on the mds/nexus device in the VSAN you want (in my example, 10 for A VSAN and VSAN 11b). Also to note: you cross never interconnection fabrics up to your SAN infrastructure. InterConnect will have a port channel to A SAN fabric and
  Interconnect B to B SAN fabric.  Consider the interconnections as HBA on a normal server.  You do not mix the tissues A and B.  That's how you get redundancy SAN.

  (7) see above.  I strongly recommend that create you separate VSANS for each fabric.  This will ensure that nothing ever gets through.

  (8) If you connect directly FIs them processors SAN you must activate the switch for on the UCS fabric mode.  You won't be able to connect the UCS for all fiber switches once do you it, and all the zoning must be done in UCSM. It does not work (we do in our test environment), be aware that it fits well beyond an area.  You would provide the same as before your San.  Activate ALUA.  The first port on each SP would go to FI - A and the second port on each SP would go to the FI - B.  Then the appropriate area in UCSM.

  (9) our ESXi hosts get a minimum of six models of vNIC.  We create an A, B mgmt, A vmotion, vmotion mgmt B, features and data B.  As you can guess, pin us each model to a cloth and do not switch.  This gives us a ton of flexibility within ESXi.  Furthermore, I believe that it is the 'best practice' is not to use the failover fabric for VMware. (If you chose, you will get alarms in vmware indicating that there is no redundancy nic.  There is an advanced disable setting.  Do not have casual, you would need to google that.). I recommend you to make a template for each tissue and keeping them up-to-date as a pair.

  (10) I wouldn't use fabric failover for everything related to VMware, VMware does a great job of redundancy management.  Let it do its work.  We only use the fabric failover for windows and Linux host running the SCU.

  (11) Yes set up as a port channel.  Before you connect the chassis as you can not no interruption of service do this later.  When a frame is automatically recognized, port channels or groups of pine are configured behind the scenes.  You cannot change these directly. Therefore, if you switch to port channels later, the only way to 'rebuild' is to re - emphasize the chassis, which will be the frame and everything in it in offline mode.  Bad day.  If you do not port channels, use the vETH blade interfaces get pinned to an uplink (following the defined process of cisco, google for UCS once again pinning get more information).  The channels of port pine servers to the interface port-channel instead of the uplink interface which makes it much more stable and resistant to link failure.  Pinning, if memory is, if a link to a server is pinned breaks down, the interface of the server is down.  It is not "repin" the link.  Thus, for example, if you do not use channel ports and a server gets pinned to uplink 1/1, and it breaks down, the server will see this interface out of service.  With a port channel, as long as a link in the chain is in place, the server will be displayed.

  I hope this helps. I typed this from my ipad - do not hesitate to respond and I'll try to clarify.

• Cisco UCS

  Still someone deployed Cisco UCS with vSphere. It's an interesteding offering that seems to take blades to a whole new level. Some of the interesting aspects include:

  Hardware virtualization

  Memory - can use 192 or 384 GB of memory per Blade model

  Wiring - use about half of the normal wiring

  CPU - CPU density is much greater than the current blades.

  Integration with other Cisco devices. Call Manager and integrity are now options for virtualization.

  A single pane of glass management. This can be managed in Virtual Center.

  E/S. With Fibre Channel over Ethernet (FCoE) and a significant improvement of the CNA inputs and outputs.

  I'm looking to see what kind of gotcha people have met others and cost. Upgrades were necessary SAN or any other

  the hidden costs or requirements?

  Mike

  Well, it is a wonderful solution and works very well!

  as long as you have a switch for the CF that supports the NPV (like MDS), then you will have your SAN ready!

  Jose Ruelas B

  http://aservir.WordPress.com

• Connection keyboard and mouse USB Wired stall

  Hello

  My computer repeatedly interrupts the connection to my Wired USB mouse and keyboard.  Usually around one every 30 seconds, the connection falls for 1 to 1.5 seconds, then comes back.  Meanwhile, the cursor hangs - I can't click anything, and I can't press any keys on the keyboard.  For example - when I type, I have my keyboard will stop working for a while, and no text will appear.  This is particularly problematic when I play games.

  I tried to reboot the computer, reset the SMC and the mouse and keyboard.  I also tried all USB entries on my mac (4 in total), and the problem persisted with each of them.  This leads me to believe that it is either a problem with all the USB inputs, or a software problem.

  I have an iMac 27 inches, mid-2011 with OS X El Capitan 10.11.6 (specifications: 3.4 GHz Intel Core i7 processor, 16 GB with 1333 MHz DDR3 memory and storage capacity of 2 TB).

  I use a wired USB (Logitech G402) mouse and keyboard USB Wired (Razer BlackWidow Stealth).  I have the latest version of Logitech Gaming Software and Razer Synapse installed for support.

  I would appreciate help.

  Check if there are updates available driver.

  To check if the problem is with the USB to your Mac controller, test with a different keyboard or mouse.

  To check the extensions conflicts, etc., try the startup mode.

  -----

  Restart in Safe Boot mode by holding down the SHIFT key at startup. Secure boot is quite slow because the operating system performs some cleanup and verification tasks, so give it time. Once you're completely connected, restart normally.

• Give preference to a wired connection

  Hi all

  I'm lucky enough in my house to have a Wi - Fi network and witeless.

  Although my 2015 Macbook Pro has no Ethernet RJ45 port, I installed a USB extenderes with a Rj45 Ethernet port included and now patched in the cable system.

  Q: are there in all cases that I can configure the Mac Book Pro to use the network wired and not on the wireless network if it is plugged?

  Then it is simply wireless when it is not plugged in?

  Appreciate your help

  SImon.

  In the system preferences network move the Ethernet connection to the top of the list. The Ethernet connection is used and if the Ethernet connection is not connected connection method will fall to the second item in the list, your wifi connection.

• Why am I being asked for WiFi connection on my Wired iMac?

  So I installed the macOS Sierra point on my iMac and I was at the research/assistance to Siri and cards and noticed that whenever I do something that requires location services, he asked to be connected to WiFi. I don't understand because my iMac is wired to the internet via an ethernet cable. Is there something I'm missing, maybe something I am doing wrong?

  Location Services can be used from a Wi - Fi connection. So anything that need localization service needs a Wi - Fi connection. You can't be located in Ethernet.

• Controls does not not on Wired Powerbeats2 w / iPhone 7

  Hello

  I was testing my wired Powerbeats2 with my iPhone 7 (iOS 10.0.1) and noticed that controls online did not work (I used lightning Apple taken adapter headset).

  Did someone of another expierencing this problem?

  Kind regards

  JC

  There seems to be a common problem, and Apple is reportedly working on a fix.

• Can I have 2 Airport Extreme with running in a single wired network DHCP server

  Hello friends,

  Just a teenager from the windows world crawling as a child in the MAC world.

  I'm curious to know if we can have 2 extreme airport, acting as 2 DHCP servers in the same local network. I really doubt if it is possible, but still want to have Advisor by experts. I am considering a wired LAN. If possible, please help me understand how this can be done in detail.

  Thank you.

  In fact, you can. The key is to assign different DHCP scopes for each base station in the same IP address space.

  For example, you could assign the range 10.0.1.2 through 10.0.1.99 to a base station and have the other on: 10.0.1.100 via 10.0.1.200.

  You set the DHCP scope or range using AirPort Utility, as follows:

  • Run the AirPort Utility.
  • Select the base and then station, select change.
  • Select the network tab.
  • Select Network Options...
  • The range is set with the option "IPv4 DHCP Range".

  

  But the question would be why would you?

• USB printer via wired airport

  Hye everyone,

  Can I share my usb printer on my express airport, through my cable modem? What I mean: my iMac 27 "is wired, my MacBook can be wired or wireless.

  Can I connect my Airport with an ethernetcable to my modem, just received the impression of two computers from there?

  Thanks for all your answers!

  Greetz,

  Jan

  It would be useful to know if your "cable modem" is just a modem or a modem combination and router or gateway. To address this issue if it please provide brand and model please?

• setting up time capsule and express wired after disconnection of the airport

  I have a 2 TB Time Capsule and three 3 wired express airport throughout my house.  I know that when I added first the cable express, that I had to call apple to change some settings.  Now I can't service because they are more than a year and after a recent quick breakdown (two or three) power is the airport expresses link is more and a bunch of my settings seem to have changed on the Time Capsule.  Any help would be greatly appreciated.  Thank you

  If you think there are setting changes, then it would be better to start over.

  • First of all, you want to make a 'factory' reset on all of your base stations. This will return them to their "out-of-the-box" configuration Once finished, leave them turned off.
  • Then, we put up the Time Capsule (TC). Since it has been reset, it will broadcast a Wi - Fi unsecured network with a network name of something like: Apple network NNNNNN.
  • Use AirPort Utility on your iPhone, Mac or PC to configure the TC as a stand-alone wireless router. In other words, configure it to provide a secure WiFi network.
  • Once the TC has been configured, verify that the clients on your network can access the Internet with it.
  • If he succeeds, proceed to the next step. If this is not the case, stop and post back with your results.
  • We will now configure all of your base stations for a roaming network.
  • Power-up one of the three stations based AirPort Express.
  • Once again, you will need to use AirPort Utility to continue. The utility must now find the Express, and if all goes well, it will offer to the Express allows to extend the TC using Ethernet. It's what you want and just go through the steps automated window 'Installation '. And then on actually.
  • Do the same for the other two express base stations.

• iMac not followed to the top of wired mouse

  Hi all

  I have an iMac with OS X 10.9.5 two years.  I have a wired mouse, not the bluetooth mouse. For some reason I can't find out, using the little grey ball allows me to scroll through the pages, but not to the top. So I have to go on the side of the window and back grey box. It's a drag.
  Maybe I changed the settings to my wired mouse, and that could be the cause of the problem.   After changing all the settings in different ways, I still can't fix.  I cleaned up the grey ball (head down, rub it around on clean paper) and clean grime the grip of the track.  Here are the current settings.

  Can someone tell me what I should try next?  I would really appreciate it.  Thank you!

  Try resetting the SMC, it may take 2 or 3 attempts. Please follow the instructions of iMac SMC and the PRAM reset