Question of MMIC UCS

Similar Questions

• MMIC UCS C200 M2 blade - cannot access

  Hi all

  I was hoping someone in this forum could help with a problem I have on a customer site. We have therefore two blades UCS C200 M2 we cannot access MMIC of. When I try to reach the IP address, the browser just sits there, but the IP address is an echo request ICMP who responded. I rebooted a systems press F2 and tried to launch the utility BIOS Setup MMIC but received a message "no attention not found" and the only option was to hit very well.

  What would cause this? And should I update the firmware? If I need to update the firmware how can I go about this...?

  In addition, these systems are running ESXi 4.1, but I believe that the version of VMware is not compatible. Could someone help me confirm this?

  Any help is greatly appreciated!

  -Bobby

  Hello

  It worked before?

  If this is not the case, try resetting the MMIC or it could be a browser/java problem too. The problem exists across the browser and several pc user.

  See doc below to configure the Mmic

  http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/c/SW/CLI/CONF...

  -
  Siva

• To access the DNS - MMIC - UCS direct KVM ip address name

  Hello community,

  I have a little problem. We use 2.2 (3d) UCS and 32 M3 B200. Now, I want to use a direct KVM access.

  For all 32 blade servers, we have created the DNS for their IP MMIC entries addresses.

  example: ESXserver1.rc (servername + ".rc") 192.168.0.1 <-- --="">(address IP of MMIC)

  If I enter the IP address of MMIC in the browser, direct access KVM works very well.

  If I get the DNS name in the browser, direct access KVM page load, I connect and get the following error message:

  GetKVMLaunchUrl: Invalid or IP address of zero MMIC spent

  Can someone help me? What do I have to configure something?

  Concerning

  Hugo

  Hi Danny Sander,

  By DNS name it won't work even if you have created in the DNS entries also, because it works through the address IP of MMIC mangement.

  Please go through the link

  https://www.safaribooksonline.com/library/view/CCNA-data-center/97801338...

• Question of the UCS Manager

  Hello

  I have problem with manager Cisco UCS, after have logged you in the UCS Manager, I get an error.

  Print.PNG

  

  Cristobal,

  It certainly is a cause of what UCSM bug doesn't do what it is supposed to and the only bug which is really (according to the version you are using) is https://tools.cisco.com/bugsearch/bug/CSCum95854/?reffering_site=dumpcr and seems to be fixed in the latest versions...  2.2.2c; 2.2.3A; 2.5.1a; 3.0.2c (UCS Mini)

  Advice is to contact TAC for assistance (if necessary).

  -Kenny

• 1225 VIC Port Virtualization question on Cisco UCS C240, 460 servers without FI

  Dear all,

  I have installed & configured the hypervisor, its running fine.  But the servers are connected directly to the nexus & there is no FI here.

  But the business must virtulize the adapter VIC & use for multiple purposes such as vmotion, FT etc...

  When I create a vNIC on CIMC & map the uplink port 0 or 1, even if those who signed off on the esxi console, even if the status of uplinks in the esxi console are shows connected.

  Will be that the adapter Virtualization is supported wireless?  Please tell us the best practices, how to use the Cisco VIC 1225/1227 wireless & how to virtualize the adapter.

  It would be a great help...

  Thanks in advance.

  Kind regards

  Gopi G

  Hello

  These guides should be useful:

  http://www.Cisco.com/c/en/us/support/docs/switches/nexus-5000-series-SWI...

  http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5500/SW/ad...

  HTH,

  Wes

• UCS C220 M3 with MegaRAID 9266-8i - degraded cache

  Hello

  I have a C220 M3 of 1.5.1g BIOS and firmware 1.5.1f MMIC UCS.

  There is a controller LSI MegaRaid 9266-8i (Firmware 23.9.0 - 0023) Super-cap inside.

  MMIC know that the virtual drive has a moderate faulted state, cache is degraded and capacitance is at 0%. The current cache policy is on direct Scripture instead of the configured return entry.

  What is a Cisco TAC case?

  

  

  Juergen,

  Open a TAC case to replace the SuperCap module, you can even refer to this thread to make the process faster

  -Kenny

• UCS and multicast

  I'm looking for some direction on two questions of the ucs as it relates to the multicast and 6200 fabric interconnects.

  1 - Igmp v3 and igmp snooping configuration

  2 - Configuration of modules e/s and fabric goes to support the follow-up to link such that if a channel of uplink port of the IOM from uplink FI or FI runs aground, it would the vswitch uplink bear appropriate in the low not of 'black hole' packages.

  Is there a specific document that covers these?

  See, for example. https://communities.Cisco.com/thread/37174

  V2.1 added additional features of IGMP (see attachment)

• MMIC vs IPMI on B and C series UCS

  Hi guys,.

  any chance someone can explain the difference between CIMC and IPMI. A few pages on ORC are indicating that the CIMC applies on the C series, while other pages are mention it when we talk too many blades. Can I open a web browser and type in the IP address that will show me MMIC running on B200M2? It's looking like similar MMIC on C series?

  I found about UCS Manager CLI command that allows to disable IPMI and now I'm even more confused because some docs on ORC say MMIC is just an old name for BMC and I know that BMC is embedded CPU which takes care of IPMI feature...

  Kind regards

  Taenarum

  So the MMIC has had many names.

  WORKING IS BMC = MMIC. So if you see WORKING or BMC in all documents safely, you can replace it with CIMC. Also please bring that to our attention if you still see the WORKING or BMC in our documentation.

  The MMIC chip is the same on the B and the C series. The interface is a little different, but both provide the same functionality. On a stand-alone C series the MMIC provides much more information because there is no UCSM to show inventory, to alter the BIOS and to allow that do you other things.

  You can download the standalone KVM that will allow you to go directly to the KVM for a series B, but it will be different then the interface for the stand-alone version of the C-series. If a C series is integrated at the UCSM, he gets the B series interface.

  The MMIC access IPMI. So now a C series if you don't have the MMIC configured you can not perform IPMI on the server. CIMC is still active for series B but IPMI is selectable via the Service profile.

  Hope that answers the questions

  Louis

• Question on UCS C series

  Hello

  I have a question about the series C UCS. Is it possible that some now to connect to 6120 fabric Manager and manage as the blade series. Or are they only manageable through their port MMIC.

  In depth.

  The 1.3.x of the code, it is not possible.  This feature will be available in 1.4 which is just QA and should be available next month.

  Kind regards

  Robert

• MMIC access after integration of series C with UCS Manager

  My question is on the following terms:

  This guide contains information and procedures for installing Cisco UCS C200, C210 and C250 servers for integration with Cisco UCS Manager version 1.4 or 2.0.1.

  Cisco UCS C-Series-Rack mounting servers are managed by the autonomous integrated software, Cisco (CIMC) integrated management controller. When a series C Rack-Mount Serveris integrated with Cisco UCS Manager, the MMIC manages nor the server. Instead, it is run with the Cisco UCS Manager software. You'll control the server using the Cisco UCS Manager or Cisco UCS Manager CLI user interface.

  This means that you literally can't website to the graphical interface of MMIC?  Or means that, although you can still access the MMIC, the management of the C series is recommended to run through the UCS Manager?

  They are mutually exclusive?

  Thank you

  Amir

  That's right, all the features are moved to Service UCSM profiles and can't do anything of CIMC.

  CIMC will report "managed by UCSM" or something like that.

• UCS C200 Server Power Supply Question

  We make some changes in our data center and which involves electric grid.  We had to replace our Dustribution of power rack and to respond to the charge, we moved 208V, 3 phase power distribution.  Read the literature, I see that the power supply to the UCS C200 servers can operate 115V to 230V AC.

  My questions are: is it everything I have on power supply from 120V AC 208 v power supply power supply power supply?  Can I have a power running at 120 v and the other operating at 208V?  I try to avoid the closure of the server.

  According to specifications

  http://www.Cisco.com/c/dam/en/us/products/collateral/servers-unified-com...

  Table 41 UCS C220 M3 SFF 450w Power Supply Specificationspescription
  Input AC voltage
  90 to 264 VAC auto-ranging,
  100 to 120 VAC nominal
  200 to 240 VAC nominal

• Can't access UCS MMIC after power on

  Hi all

  I am deploying a new server of UCS-C210, but we are facing some problems:

  1. when the connection of a monitor to it the monitor does not show anything, as the server is off power

  2. with the server off, I can access the MMIC, but after I turn on I lose acess to the MMIC and computer not responding ping.

  3 - the server has done a lot of noise more than other UCS C210 we have.

  Everyone faces that? I'm starting to think it's a hardware problem.

  Thank you

  Rafael

  If there is a problem with the MMIC HW he will probably be replaced.

  Please open a TAC next case.

  Kind regards

  Robert

• UCS B420 M3 config problem / question

  Hi all

  at this time I had 2 questions requiring my consultation with the community:

  1. I try to get set up on the CCW the sku for UCS B420 M3, but the only part that shows is UCS-B230M2-VCDL1 and does not show any other SKUS for UCS - B series servers, where we cannot set config to get a quote?
  2. In the CET record says that the UCS B420 M3 may had 4 processors, each processor with 8 cores. in this order, you had 32 total cores in the blade?

  The SKU is UCSB-B420-M3-you and for the complete solution, you can also use n20-z0001.

  Yes B420 M3 has 4 processors with 8 cores per processor, so you can have 32 cores in B420 M3

• UCS B / Manager of UCS Upgrade 1.3 to 2 questions

  Hello world

  I have problems with the download of the image for the interconnection of fabric, in event file will this message

  Description: [FSM:STAGE:STALE - FAIL]: remove downloadable ucs-k9-bundle-infra. 2

  . 0-3. A.bin on local(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:DeleteLocal)

  Affected object: sys/fw-catalogue/dnld-ucs-k9-bundle-infra.2.0.3a.A.bin

  Trigger: special

  User: internal

  Cause: Transition

  Code: E4195295

  Creation date: 2012-07 - 12 T 20: 36:19.006

  ID: 74438

  Description: [FSM:STAGE:REMOTE - ERROR]: result: end-point - doesn't have a Code: unspecifie

  d Message: end point has expired. Check IP, password, space or associate access

  questions.

  (sam:dme:FirmwareDownloaderDownload:DeleteLocal)

  Affected object: sys/fw-catalogue/dnld-ucs-k9-bundle-infra.2.0.3a.A.bin

  Trigger: special

  User: internal

  Cause: Transition

  Code: E4195295

  Creation date: 2012-07 - 12 T 20: 36:18.995

  ID: 74435

  Description: [FSM:STAGE: FAILURE]: download image ucs-k9-bundle-infra. 2.0.3 a .to.

  10.8.224.244(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:Local) bin

  Affected object: sys/fw-catalogue/dnld-ucs-k9-bundle-infra.2.0.3a.A.bin

  Trigger: special

  User: internal

  Cause: Transition

  Code: E4195293

  Creation date: 2012-07 - 12 T 20: 36:18.995

  I had a SFTP / SCP seber on the same network of the fabric, but I can't do the download. the server is a host/PC, no antivirus and firewall that cannot block the transmission on the side of the host/PC

  any ideas?

  Thanks for your help!

  Hello Hans,.

  You can follow the guide to upgrade the following link UCS Manager. Make sure that you are correct steps.

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/upgrading/From1.3/TO2.1/b_UpgradingCiscoUCSFrom1.3To2.1.html

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