XenServer on UCS Manager 2.1

Similar Questions

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

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

• UCS Manager 2.0 (1W) read only role grayed out

  Hi, I want to create a user authenticated locally in UCS Manager with read-only permissions, but when I go to add the role of read-only user is not available for selection (it is grayed out). No idea how to solve this problem and make the read-only role available for selection? Screenshot attached. Thank you.

  It is activated by default.

  Don't assign it not all roles to your new user and they will automatically get the read-only.

  Kind regards

  Robert

• 6120 link down on mgmt0 triggers not UCS Manager failover cluster - is?

  Hello friends

  We have recently installed a cluster consisting of two 6120 UCS s configured for HA. When executing fail during test cases, we removed the network cable in mgmt0 on 6120 elementary. Immediately the cluster IP address is not responding ping (as expected) and we lost connectivity to the UCS Manager GUI (also as expected.) At one point, however, we expected the 6120 subordinate to detect that this link was down and launch a failure over the UCS. This is not moved after 20 minutes of waiting.

  My questions are the following:

  1. Is this expected behavior?
  2. If this is not the case, what should us review to ensure that failover occurs in the future?

  I know we can force a failover of the subordinate by issuing a command to the main cluster of local-mgmt but would be interested to see if it should be automatically produced on the failure of primary mgmt0 binding.

  Thank you for your time.

  Configured by default which is the expected behavior.

  You can configure management interface and failover if the management interface loses connectivity such as your test scenario.  That's what you're looking for.

  Admin - Communication Management - Management Interfaces - Management Interface tab strategy control tab.

  

  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

• installation document ucs Manager

  someone can tell us where ucs manager is executed or can antbody can tell us where we can find a facility for ucs document manager with c-series single pedestal.

  Thanks in advance

  Erick,

  I think you are talking about two different things.  UCS Manager is for blades of series B and C-Series, which are built/managed by UCSM.  Stand-alone C-series is no manager of UCS.  Each C-Series is managed independently by the MMIC (Cisco integrated management controller).

  Kind regards

  Robert

• 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

• Users unable to SSH to UCS Manager

  I have the LDAP users who are not able to ssh in the UCS Manager even though they can connect through the GUI.  But locally defined users are able to get through the GUI and ssh.

  Users who authenticate to UCS Manager via LDAP are able to connect via SSH as well?

  Thank you.

  Hello Bruce,.

  Are you adding "ucs -" domain name?

  For example, for access via SSH.

  # Linux terminal.

  SSH ucs-------@.

  SSH-l ucs-------.

  # Of putty client

  Connect as: ucs-------.

  And the domain name is case-sensitive.

  HTH

  Padma

• 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

• Looking for a UCS Manager 'lite' or stand-alone

  We have a dozen UCS C-series servers spread over 5 different sites.  Is there a free utility or inexpensive to manage all servers in our series C from a single point?  UCS Manager is great, but its exaggerated and way too expensive.  I think of something as a UCS Manager-Lite or even a third party utility that I can install it on my workstation.

  Hi Tod

  Is Cisco Cisco Integrated Management Controller (IMC) supervisor-1.

  It's a solution under license; don't know if it fits your needs 'too cheap' ;-)

  Walter.

• UCS Manager 2.2 - LDAP authentication

  Hello

  I have some general questions about authentication LDAP and UCS Manager.

  I hope it's unterstandable...

  We have the following structure:

  • DC = Company.domain.com
    • OU = Domain Administration
      • OU =Administrators
        • UO = Germany
          • CN = User1-SMA
          • CN = SMA-user2
      • OU = Test-UO
        • CN = ucstestuser
        • CN = ucsadmingroup--> Member = SMA-user1, user2-SMA
          

  I added an LDAP provider

  binduser is the SMA-User1

  Base DN = OU = Domain Administration, DC = company, DC = domain, DC = com

  attribute = empty

  filter = sAMAccountName = $userid

  password for User1 SMA

  group permission / recursive enabled.

  I have not add some attributes or map the group. Now I can connect with ucstestuser (read-only), but not with SMA-user1 user2 SMA oder.

  If I add ucstestuser to ucsadmingroup a map of this group, ucstestuser can access and have right to admin, ADM-user1 and user2-adm cannot access (user authentication failed).

  I don't understand, why ucstestuser can access and other users in a different OU not. Unique database name is domain Administration, so that UCSM should see all three users, not?

  Can anyone help? Thank you.

  / Danny

  With UCS remote authentication when a user connects using a temporary account on the FI as a UCS-MyAuthDomain\myusername, which is limited to a total of 32 characters.  If you shorten the name of domain authentication defined in UCSM domain.com to a shorter name as AD, it will allow for the use of a username any longer.

  Note

  For systems using the remote authentication protocol, the authentication domain name is considered to be part of the user name and the limit of 32 characters for usernames created locally. Because Cisco UCS inserts 5-character formatting, the authentication will fail if the name and the user character domain name combined total is greater than 27.

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/SW/GUI/config/Guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/b_UCSM_GUI_Configuration_Guide_2_1_chapter_01000.html

• 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="">

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