v2.2(7b) UCSM. B200M3 2.2 (2 c). Questions KVM

Hello guys! How everyone else is doing?

We have recently improved our FIs to v2.2(7b), so that our environment could receive a new knife B200M4 (according to the release notes, this is the proposed version of this material). And according to the same release notes the FIs on 2.2(7b) are compatible with the server on 2.2 bundle (2 c).

But after upgrade FI, we are unable to connect to the KVM B200M3 blades. We got a timeout. It is not a Java problem, as we have always done and it worked.

I found a bug (cscux24085) who have exactly the same problem (but different versions) and it is recommended to install the same version of the FIs MMIC.

So the question is: should I upgrade only the MMIC of blades through activation manual or is - this too risky? If I do it's the blade will restart?

Thank you

Rafael

Hello

Looks like you beat this:

https://BST.cloudapps.Cisco.com/bugsearch/bug/CSCux24085/?reffering_site...

A test, you can improve the MMIC on a slide to 2.2.3 version and see if the problem persists. Remember, to be in a supported configuration, all components must be on the same version of firmware. You do not want MMIC on 2.2.3 and then the BIOS on 2.2.2.

Yes the upgrade of blade will require downtime, however only upgrade CIMC will not.

HTH,

Wes

Tags: Cisco DataCenter

Similar Questions

  • VSAN membership down on the CF mapped uplink port

    Hello

    Since I upgrade Cisco UCS Manager, all frame and fabric of interconnections of version 2.2 (1), I have a few minor flaws.

    I configure ports 31 and 32 as FC uplink ports and mapped each port to a vsan:

    Port 31 = VSAN 'blue '.

    32 port = "red" VSAN

    (I know, it is not common to map two different VSAN to the same fabric, but I have to)

    Since the update, I get minor flaws:

    31--> FCoE or FC uplink port is broken on 'red' VSAN / membership-down

    32--> FCoE or FC uplink port is broken on 'blue' VSAN / membership-down

    I have no channels of port FC or FC enabled link mode. Interconnection of fabric is EHM.

    Even in other tissues.

    Can anyone help me or is it the same cosmetic problem as stated in the quote?

    FCoE Uplink vsan membership fault for any vsan not configured upstream Symptom:

    Fabric Vsan Membership Down fault message on FCoE uplink ports

    Severity: Major

    Code: F1083

    Name: Fabric Vsan Membership Down

    Conditions:

    Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect

    Workaround:

    None.Error message is cosmetic.

    Thanks in advance

    / Danny

    Hello Danny,

    Yes, it is a cosmetic issue in UCSM 2.2.1

    the question is followed by

    https://Tools.Cisco.com/bugsearch/bug/ CSCum89468

    The one that you cited ( CSCud81857 ) is specific to the rising FI FCoE in version 2.1 of UCSM.

    HTH

    Padma

  • Dependent Service in UCSM material of blade profiles? Is that we can assign the same service to a B200M2 profile, B230 M2 and a blade of B200M3?

    Dependent Service in UCSM material of blade profiles?

    Is that we can assign the same service to a B200M2 profile, B230 M2 and a blade of B200M3?

    An example: if my B200 M2 goes down because of a hardware failure, I replaced the same slot with a B200 M3 Blade.Then is possible that I have separate Service of B200M2 profile and associate the same Service profile with B200M3?

    Hi Deepak,

    It is certainly possible.

    If there is no problem, because of incompatibilities, it triggers a failed configuration error, the service profile is related to the new blade.

    I hope this helps.

    Thank you

    Michael

  • 2.0(1t) UCSM dislikes Java 1.7

    Guys,

    I have no chance whatsoever with UCSM 2.0(1t) departure on a Windows 2003 R2 (32-bit) machine: it says "Java detected 1.7, Java 1.6 (or MORE) required.

    The notes say: "the Cisco UCS Manager GUI is a Java application that requires Sun JRE 1.6 or higher.

    So what's the bottom line - will I expect UCSM 2.0 to work with Java 1.7, or not?

    Kind regards

    Radek

    Javea 1.7 is supported on version 2.0 (3) and newer.  2.0 (3) is currently available for download from EAC.

    Kind regards

    Robert

  • How to check on UCSM NTP synchronization?

    Hi all

    Just my feet wet with UCS and have our first basically installation system.

    However, I have defined 2 NTP servers in UCSM but it doesn't seem to work.   I have hunted for an equivalent display status ntp IOS, but so far, have not found a.

    Is there a way to check the status of time synchronization? Or would be seized errors in a newspaper anywhere?

    Thank you

    Anthony

    Anthony

    YEW running that controls several aircraft viz NXOS and UCSM local administration.

    UCSM is the only way to configure the system while others are read-only.

    You can check the status of the plan NXOS ntp.

    To do this, ssh for the VIP.

    connect nxos

    At this point, you are connected to the NXOS plan and view orders / debugs are applicable.

    'See the ntp?' and you will see the options as the State and peers.

    Thank you

    -Matt

  • UCSM showing the reason: NHS source pinning failed.

    Hello

    I have UCSM 2.2.3g and B200M4 with UCS FI 6248.

    I'm getting NHS source pinning is not...

    How can I solve this problem...

    Please see attached screenshot for details...

    Unless you configure VLAN disjoint, all the VLANS defined on UCS FI are included automatically in the trunks ethernet to the North; nothing special to do.

    See also

    http://ciscoquicklinks.com/Tip-Datacenter-UCS-uplink-port-configuration-...

  • Stop the service UCSM on FI

    Anyone know how to stop the UCSM service on a financial institution active to force the failover? Either from the FI

    CLI or the UCSM?

    Deliver the cluster host and verify that HA is running and that is main first, then plug it local-mgmt [has | b] command

    In the example below, the A is initailly primary, after the main group b, B is the main

    FI6100-1A # show cluster extended State
    The ID of the cluster: 0x79c0e920540811e0-0x9239000decd35dc4

    Start time: Sat Mar 26 02:35:30 2011
    Last election: Sat Mar 26 02:35:57 2011

    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 READY
    Detailed statement of the unit selected for storage HA:
    Chassis, serial: FOX1326G5KH, status: Active

    FI6100-1A # local-mgmt to connect a
    FI6100-1-A(local-Mgmt) # cluster lead
    a and b
    FI6100-1-A(local-Mgmt) # cluster lead b
    The ID of the cluster: 0x79c0e920540811e0-0x9239000decd35dc4
    FI6100-1-A(local-Mgmt) # connection to 172.25.183.132 closed by the remote host.
    Connection to 172.25.183.132 closed.

    Check

    FI6100-1-B # show cluster extended State
    The ID of the cluster: 0x79c0e920540811e0-0x9239000decd35dc4

    Start time: Sat Mar 26 02:36:43 2011
    Last election period: Sun Apr 5 00:32:55 2011

    B: UPWARD, PRIMARY
    R: UP, SUBORDINATE

    B: Member State UP, lead, State State PRIMARY, mgmt services: UP
    A: 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 READY
    Detailed statement of the unit selected for storage HA:
    Chassis, serial: FOX1326G5KH, status: Active

  • UCS B200M3 and Flex Flash (SD card)

    Hello

    I migrate fews UCS B200M3 to boot from SAN SD card because it is supported by the firmware 2.1.

    I am running the latest firmware, 2.1(1a) and ESXi 5.1.0 1157734 with a custom image from Cisco.

    After a few days, my lost ESX connectivity with SD card and in vSphere it is said: connectivity lost unit mpx.vmhba32:C0:T0:L0 supporting system startup files... (see attachment) (I got the error one all my ESX on SD card).

    If I restart the agent management ESX or reboot, the message disappeared and everything works.

    There is a problem with ESXi 5.1 on SDCard and B200M3?

    Thank you

    Hello

    At this point, we are trying to see if the problem is related to the one seen on C-series.

    I'll try to update you in a few days, if not, please post again here as a reminder so I can update you.

    -Kenny

  • List UCSM offshore all Webinterface .jar files / McAfee blocked ccore.jar

    Hi guys,.

    I'm looking for a list of all the .jar files UCSM loads at startup, basically the folder/ucsm/unpacked.

    We are using MCafee Enterprise 8.8 AV and it seems to block access to the ccore.jar file.

    I'm trying to get a rule file for exclusion from our IT for management servers, and I was wondering if someone could give me a list of these files.

    If you know of a fix for the issue that has no exception rules you are welcome to help me

    Kind regards

    Constantin

    If you open the file ucsm.jnlp (the file that will be downloaded on your machine when you try to launch UCSM GUI) in a text editor, then you will see entries like:

    and this will give you the complete list of jar files downloaded from the switch on your machine for the launch of GUI de UCSM.

    for example

    http://java.sun.com/products/autodl/j2se' java-vm-args = "" - Dsun.java2d.d3d = false - XX: + HeapDumpOnOutOfMemoryError - XX: MaxPermSize = 256 m "initial heap size ="128 M"max-heap-size ="768 M"/ >"

    Thank you
    Varun

  • UCSM integration with the series C - non-nexus 2 k for the management?

    Is it possible to integrate the grid of series C rises (particularly C250 M2) with UCSM without using the 2248 management in accordance with this article for the C200 http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/ucsm-integration.html

    I guess we would be able to plug ports LOM on the C250 on a different switch IE of 3750 which would be connected by uplink to the FI 61xx. The ANC on the C250 map would be connected directly to the FI 61xx. Would this work?

    The integration guide refers only to the Nexus 2248 FEX which we do not have and I can find no confirmation elsewhere.

    Thanks in advance

    Tim

    Of course, the Nexus 2 k is similar to the IOM module (2104) in 5108 chassis.

    To keep the same logic of control plan the Nexus 2 k provides similar functionality.

    All under the Nexus 2 k will have a chassis 'rack mount '. The nexus 2 k is not a switch by saying but a 'slave' off the parent device "switch / stop host mode" (6100). A normal switch / normal typical would not work in this case.

  • UCSM / VMware vCenter Server dependencies for vDS

    I'm still trying to wrap my head around the differences between the vDS created via UCSM / VMware vCenter integration and the traditional N1K.

    If correctly, the vDS UCSM (1.4) does not require the VSM device which is necessary with the N1K.  And if that is correct, is there any dependency on vCenter?  If vCenter falls down the vDS will continue to operate normally as made them act as the VSM?

    Pete,

    There is a dependency on vCenter, similar to N1kv (software) and UCSM vDS (hardware), applies to both methods of implementation. However, if vCenter goes down the current state of the operation continues. When a change occurs on the virtual machine, that is where should be upward a vCenter race.

    Concerning best practices, I was that it is better to have everything on the vDS for operational reasons. You can then apply and manage the kernal ports in the same case that VM vNIC. QoS, etc... There is a nice documentation on www.cisco.com/go/designzone data Center on this topic.

    HTH

    Thank you

    Eric

  • Only access via UCSM KVM

    I am able to restrict users to the KVM console only in UCSM?

    What are the roles I have to assign to the user to ensure that all they can do is access the KVM Console?

    It is not a huge problem if they get the UCSM itself read-only rights.

    Create a role called "KVM-Only" or similar and affect only the privilege of "service-profile-server-oper.  Then, create a user as "KVM User" and him given that the role of KVM only.  They will be able to launch the full UCSM or KVM Launcher, but only have privileges access KVM.

    Alternative if you want to only grant access KVM while preventing access by connection/UCSM.     Configure an IPMI profile with ipmi-user named something like 'helpdesk' for example. Creating 'helpdesk' offer the privilege of ipmi admin. assign this IPMI-profile to the profile of your server service.      Then use the following link on your browser

    http:///ucsm/kvm.jnlp

    or

    http:///ucsm/kvm.jnlp?kvmIpAddr=w.x.y.z (where w.x.y.z is the Management IP
    of the blade or Service profile you wish to provide access to)

    It will open a KVM connection screen. Enter the username 'helpdesk' and assigned password and the MMIC-server you have configured IP address.  Address IP of MMIC lie on the Hardware tab, by selecting the blade, then the right selection inventory - MMIC.  The MMIC IP is listed under the section "Management Interface."             This will open the KVM from that server. Also, the ipmi vinay-kvm user only WILL NOT be able to connect to regular UCSM GUI Note that in version 1.3 - MMIC IP is static and will remain with the hardware of server/slot.  In the latest version 1.4, you can join the IP of CIMC/IPMI address your service profile so that it will follow him around everywhere where the profile is associated with.

    Kind regards

    Robert

  • UCSM VM - FEX create when port-profile name cannot be used. (dot)

    UCSM q with 6120XP 2.01

    I can create using port-profile. (dot) for example "VLAN30 - 192.168.1", but it causes a warning message (pictured below)

    so I try to change the name of VLAN30-192-168-1 it can work very well

    My question is can I use. (point) in my profile of the port name?

    PS. I checked the manual of cisco

    This name can be between 1 and 31 ASCII alphanumeric. You can not

    Use spaces or other special characters as - (dash) _

    (underscore character). (period), and: (colon), and you cannot change this name

    Once the object has been saved.

    Thank you

    We have logged a bug for this CSCtw50228 - thanks to Yasmin!

    Our developers have confirmed that while other objects have name validation, virtual computer Port profiles are not, who raises the error you see because NXOS cannot process ".» (periods).  The names of service profiles are another matter that NXOS has no knowledge of these objects.

    The solution is to avoid using periods in the VM profile names.  Use a dashboard.

    Kind regards

    Robert

  • Out of the understanding of: ucsm-B (nxos) # sh int br

    Hi all

    Could you please help me understand the output of the following command:

    ucsm-B (nxos) # sh int br

    I have a few questions about the number of interfaces eth1/1/1 to 1/1/8 eth:

    What governs the convetion of naming used for the ethernet ports from eth1/1/1 to 9/1/eth1?

    If I connect another chassis to YEW, he will start by eth2/1/1?

    I would like to understand how Eth1/x/x or x/x/Eth2 is decided by the UCS to name...

    --------------- truncated -----------------------------------------------------------------------------------------------------

    -------------------------------------------------------------------------------

    Vsan Admin Admin Port SFP Oper Oper status interface

    Mode Trunk Channel Speed Mode

    Mode                                 (Gbps)

    -------------------------------------------------------------------------------

    vfc684 102 F trunking - auto TF-

    vfc688 102 F trunking - auto TF-

    --------------------------------------------------------------------------------

    Ethernet port VLAN Mode State reason speed Type

    Interface                                                                   Ch #

    --------------------------------------------------------------------------------

    Vntag eth eth1/1/1 1 place no 10G (D)-

    Vntag eth 1 eth1/1/2 room no 10G (D)-

    Vntag eth eth1/1/3 1 place no 10G (D)-

    Eth1/1/4 1 eth access down administratively 10G (D).

    Eth1/1/5 1 eth access down administratively 10G (D).

    Eth1/1/6 1 eth access down administratively 10G (D).

    Eth1/1/7 1 eth access down administratively 10G (D).

    Eth1/1/8 1 eth access down administratively 10G (D).

    Trunk eth 4044 eth1/1/9 up to 10G (D) none-

    Hi Vikas,

    These are interfaces of hosts (HIF) / backplane ports on the FEX / IOM linking the impeller.

    ETH.

    "view details of fex" would provide additional information on ports FEX.

    The ninth interface offers a MMIC connectivity to blades,

    HTH

    Padma

  • How to clear faults on UCSM 1.4(3q)

    Hello

    I run a 1.4(3q) platform and I would erase all faults displayed on the UCSM.

    How can I do?

    I would like to remove the flaws because in some cases it very old flaws.

    All faults are Acknoledged but I can't delete it.

    Thank you

    Can you make a screenshot of the fault or the details of the flaws of the CLI and fix here.

    as well as a screenshot of the backup jobs.

    One quick thing, you can try, if its for a job back that is still present in the UCSM: try to delete the job and that should fix the problem. You can then recreate the work once the problem is resolved.

    . / Afonso

Maybe you are looking for