Upgrade of the UCS Manager

Similar Questions

• Can I see faults offset and deleted in the UCS Manager?

  Is there a way to see the flaws that have been deleted in the UCS Manager and deleted once the retention period has expired?

  Thank you.

  .. .Brian

  No, unless you use an external syslog server.  It is the only way to maintain indefinitely offset flaws.

  Robert

• 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

• How to configure the UCS Manager?

  Hi, this is the first time im using the Cisco server and we have Cisco c240. My task now to monitor this server using SCOM. Research, I understand that it will take to install/configure the UCS Manager. But I'm not really sure how to set it up, I know it's similar with Dell OMSA, but for the OMSA, just install the application. But how do the Cisco server?

  Hello

  Although it is not clearly documented, integration SCOM is supported only for the blades of the series B and C-series rack mounts, which are integrated with UCS Manager. No support for stand-alone C-Series.

  Walter.

• The UCS Manager LDAP question

  Hi guys,.

  I was wondering if anyone could help with a weird problem that we seem to have met with our UCS Manager.  We set it up to use LDAP authentication for log on which works very well for four of the five members of the team, but we have a user that although it is in exactly the same groups as the rest of us continually gets unautheticated errors to the user.

  We did the habit of checking that it is not his machine or installation and in the newspapers that it even does not save an attempt to log on default so not sure what I can check any thoughts would be much appreciated!

  We use UCSM v2.1 (1e) in case it's relevant?

  Thank you very much

  John

  I ran into the same issue.  Has proved to be a bug in the firmware DN was too long.

  CSCth96721

  It is more a limitation of 128 characters for the number of units of organization or the length of the distinguished name (DN) when you use LDAP to Active Directory authentication.

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/release/notes/UCS_28313.html

• rename objects in the UCS Manager

  How to rename objects in UCSM - things like service profiles.

  models, policies, etc. I can't find anything in the GUI or CLI for this.

  Thank you.

  Mark,

  With the current code review is not possible to rename the Service profile, or templates.  It is a future improvement in the pipe, but there is no committed date at this stage.

  Kind regards

  Robert

• UCS Manager release Upgrade Advisor

  Hello

  We have a UCS with UCS Manager 2.0 infrastructure (3) output and vSphere 4.1.

  Now, we would like to improve our infrastructure to vSphere to version 5.1. Taking into account the fact that 2.0 (3) UCS Manager does not support vSphere 5.1, is it interesting in the UCS Manager upgrade to 2.0 (4) or 2.0 (5) compared to upgrade to the latest version 2.1 (1)? I think the stability, or maybe other reasons...?

  Thank you

  Yes - all build train which is more mature (ie. more frequently patched) must inheritly be more stable.  When you introduce new features, as there are a lot of difficulties in the case of 2.1 added after that we discover strange things visitors try to do with the product.  It is impossible to QA a product for each customer & deployment disparity.

  If you don't need the new features, specific HW or SW OS supports, then stay with the current 2.0 train.  It's just more mature than 2.1.  We should have our first 2.1 patch temporarily to come in a few months.  At that point I would start to promote the 2.1 as being the more stable & recommended version.

  Kind regards

  Robert

• Manager of the UCS of 1.2 update (1 d) to 1.3 (1o)

  I use the instructions in the UCSM_GUI_Configuration_Guide_1_3_1.pdf to upgrade my equipment ucs.  There are several questions and I had.

  (1) it says to update the firmware for the IOM and wait until you activate the firmware on the fabric of interconnections that will restart the interconnection fabric and IOM, date on which IOM will be updated.  I did the firmware was not updated on IOM.  The backup version still shows 1.3 (1o) and the current version is 1.3 (1 c) IOM for, even if the fabric of interconnections successfully updated.  When I try to manually activate the firmware on the IOM, I get error combined modification.  The compatibility check failed. What is this?

  (2) I have treid activating the UCS Manager according to page 141 of the guide of version 1.2 (1 d) 1.3 (1o) and I find failed to start activation.  The check of the compatibiity failed. 

  (3) I tried to update the individual servers of 1.2 interface cards (1 d) to 1.3 (1o) and I will meet with the same errors of compatibility check.

  This is the first time I went through and tried to update the firmware on my new box of UCS.  Any help would be appreciated.

  Thank you

  During the activation of the new firmware, you must check the box to ignore the compatibility check.

• Use management/KVM ip addresses several areas of the UCS

  Hello

  We organize several servers UCS blades in two areas of the UCS. In all areas, we configured an IP ext-mgmt pool to join the MMIC of the blades. As our two infrastructure is developing, I was wondering if we could use the IP addresses that we use for pools in both areas?

  I read the guide management (http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/G...) and as far as I understand it, if we use the inband IPv4 addresses these addresses are used between the fabric interconnects and server blades?

  So I could not addressed the KVM from "outside" so through the UCS Manager (equipment-> frame-> Server-> Actions "Console KVM"). Am I wrong? I did a few tests well failed to start KVM without our current configuration (IP ext-mgmt pool provides extrabande for each unique server IPv4 addresses).

  Thanks in advance!

  Concerning

  Martin

  Hi Martin

  I think that's not possible! as soon as you insert a blade, it will have an IP address from the ext-mgmt pool and assigns it to the MMIC! That's why this IP address is assigned to a chassis / slot, which means that if you move the blade to another location, most likely, it will get another address. It is a challenge, if you want a DNS entry for a blade / KVM access.

  Walter.

• Error UCS Manager Console KVM to open after Java Update

  After the upgrade to version 1.7_21 Java I tried to access the KVM console from within the UCS Manager (v2.1 (1 d)) and get the error message:

  "Cannot run the program"C:\\Program": CreateProcess = 2 error, the system cannot find the file specified."

  I tried to remove installed applications and applets as well as temporary files from the Java console inside, but it does not solve the problem. We also tried to launch the console KVM in KVM Manager and that works very well. Everything works correctly when you run Java 1.7_17.

  Everyone knows about this problem since upgrade to 1.7_21?

  Thank you.

  In the meantime, you can install Java in a directory path that has no space to work around the problem. For example: c:\Java\jre7

  This will give you access KVM again.

• The UCS firmware update

  Hi all

  What would be the recommended way to upgrade the firmware on a current environment UCS run 1.4.3x?

  wouldn't be better to go from 1.4.3x to 2.0 and 2.1.

  or go straight from 1.4.3x to 2.1 x?

  Thank you

  Kass

  Kass,

  Since you're currently at 1.4, you can directly pass to 2.1 (2) - last version if you wish.  This process can be facilitated in particular by using the function Auto Install of 2.1 Firmware.

  Review the complete upgrade procedure, but essentially you first download the new 2.1 (2) 'A' and 'B' your system UCS beams, then activate the image of the UCS Manager first to the new version 2.1 (2).  After restarting UCSM you can use the feature of Firmware Auto Installer to upgrade the rest of the Infrastructure (IOM and FIs) and then the firmware of server endpoints.

  Kind regards

  Robert

• UCS Manager logon box Java problem

  I'm testing Java 7 update 55 with the UCS Manager to verify that all features working. When I opened UCS manager connection poster box but I noticed that the 'Domain' option does not appear. Without it, I can't choose between LDAP or local authentication.

  Someone at - it solved this problem with versions of Java (more recent than the 45 update)?

  Thank you.

  You can upgrade UCSM whitout put to rest, but the supported configuration is to have UCSM, fabric and IOM (which is included with the 'Infrastructure package') running the same version...

  Now you can just upgrade the infrastructure bundle and check 'Table 2' both of the links below to confirm compatibility with the Server Bundle (bundle Server = MMIC, BIOS, adapter card controller, etc.) to see what you pouvez/may not combine:

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

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

  -Record ALL responses and marked the question as answered if what you are looking for.

  Kenny

• Upgrade failure of UCS-5801 FI 6248UP

  Hi all

  I did an upgrade of the UCS system. I moved from 2.0 to the latest news. While performing the upgrade, everything seemed ok, but after that whole process is finished, the two 6248UP FI won't come. LEDs seems to be ok, but the console port not responding or the IP address of the UCS Manager. Although I changed the settings to the CONSOLE PORT, it will not respond. I connected to see a start and no output received.

  Is there a way to reset check o what happens?

  Thanks in advance,

  Fernando

  Hi Fernando

  I don't understand, why the two IFS are dead? You fact so the upgrade on the second FI, knowing that the original is not ok?

  I have seen the IF (and IOM) goes wrong during an upgrade! Urgent, I opened a case of TAC, nothing that you can do on your side.

  Walter.

• Integrating Active Directory and UCS Manager

  I'm looking to create an LDAP authentication provider in the UCS Manager that will authenticate users in Active Directory. I see the configuration guide UCS that a schema change is required to add a new attribute for user accounts and the guide details what the new attribute should be. However there are no detailed instructions on how to make the change to AD. I imagine some sort of import LDIFDE is required, but does anyone have more detailed steps on how to do it?

  Thank you

  You can ssh in your UCS, go to the NxOS prompt and test authentication as follows:

  Laurel - A (nxos) # test cpaggen aaa cisco group ldap
  the user has been authenticated
  Laurel - A (nxos) # test aaa group ldap cpaggen cisco1
  user authentication failed
  Laurel - A (nxos) # test aaa group ldap foo doesntexist
  user authentication failed
  Laurel-a. (nxos) #

  Make sure that this part of work. The role assignment comes from CiscoAVPair and the value must be a shell: roles = 'admin' If you want the user to be an administrator. CiscoAVPair must be an attribute of the user object. I've attached a screenshot of Wireshark for a successful authentication and authorization.

  You will also find the definition of the user and configuration of my UCS.

• UCS Manager & Vmware

  Hi guys,.

  Before we set our Cisco UCS solution in we have Vmware running with Nexus 1000v switch. After the installation of the Cisco UCS solution, we migrated a lot off the coast of the old system to the new. By reading the manual on setting up vCenter, Port and VMS profiles in UCS Manager, it seems that this creates a new on the nexus 1000v vsm. Anyway is to import what we have so that we see in the UCS Manager?

  David, the functionality of the UCS you speak is known as VN-Link in the material while the Nexus 1000v is known as VN-link in the software. Installation and configuration is very similar to the Nexus 1000v but they are separated distributed virtual switches.

  Unfortunately, you can't use both because they require the VEM loaded on ESX hosts and the UCS VN-link requires a login policy dynamic UCS vNIC. If you use the 1000v, you will not be able to use the VM tab in UCSM and you will not see anything on the virtual computers tab on a Service profile.

  In my opinion the Nexus 1000v is preferable because is offer more features, more scalable and is managed/set NX - OS. Of the UCS VN-link option also limits the number of virtual machines, you can run on a host computer, because the dynamic vNIC takes in charge a maximum of 56 depending on how rising your chassis to your FIs. If you have only 2 uplinks of your chassis then the max machines virtual host when using the UCS VN-Link is 20-24, according to the number of vNIC ESX host, you create as part of your Service profile.