If you are wanting to limit the role permissions for a user to specific equipment, then you will need to create ORGs and Locales. You will create your ORG, then create a locale associating it with the specific orgs (containing the equipment) As you create your new user inside the org, you then reference the locale based role(that only has permissions for that org and suborg level) https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Admin-Management/3-1/b_Cisco_UCS_Admin_Mgmt_Guide_3_1/b_UCSM_Admin_Mgmt_Guide_chapter_01.html   Former Cisco Employee has a couple of examples on his website at https://benincosa.com/?p=578   Kirk... ... View more

DIMM Slot numbering: |=======================| | Memory | DIMM Number | | Channel | 1 2 | |=======================| | A | 01 02 | | B | 03 04 | | C | 05 06 | | D | 07 08 | | E | 09 10 | | F | 11 12 | | G | 13 14 | | H | 15 16 | |=======================|  Are you certain it was DIMM in slot G2 you removed?   Maybe try rebooting the CIMC (admin tab, utilities, reboot/restart CIMC), and see if the CIMC reboot's rescan of hardware reports differently. Kirk... ... View more

I believe your approach  should work. UCSM 2.24 and later allowed the per IOM re-ack instead of the whole chassis (which is actually just both IOMs at once)   Kirk... ... View more

If you are dropping the blades and FI/IOM modules into a new chassis, then you may have a new chassis # assigned due to the changed serial # when it discovers. I believe you should be able to decomission the chassis, and edit the chassis # in while it is listed in the decomissioned tab be fore re-ack'ing.   Kirk... ... View more

Assuming you are only replacing the 5108 chassis, and not replacing the 6324 FI/IOMs, then your configs should be retained. As always, make sure you make backups of your logical, system, and full state, for worse cast scenarios.   Kirk... ... View more

Since that's a call manager appliance server, they lock down the various options you have vs a standard C240M5 that you could install/order wide variety of NIC/adapters in. Appliances typically have a much narrower focus and have passed a lot of validation checks against that specific set of hardware. Kirk... ... View more

Are you asking if there are newer UCSM A, B, C series type firmware bundles out there? What happened when you checked the UCSM download area at https://software.cisco.com/download/home/283612660/type/283655658/release/4.0(4b) ? Maybe I'm not understanding your question...     Kirk...   ... View more

Managed vs non-managed is a feature set of a particular component.  Those particular Intel cards do not have a out of band mechanism (such as I2C) built in to provide thermal information up to the CIMC such as do most RAID cards or the CISCO VIC cards that do. It's not an overlooked setting that was missed.   Kirk... ... View more

You are posting in the UCS compute section. Please try moving your post over the the Unified communications call manager forums for better response.   Kirk... ... View more

So based on the RPMs, those are running about 55-60% duty cycle, which is probably normal for the M5s with a couple of un-managed PCI-E cards. The cooling requirements for the M5 is definitely different than the M4s. I'm not sure if there is a published expected DB level for the different duty cycle ranges... There is a bug published, https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvj21242/?rfs=iqvred that noted that the default power/cooling policy was set to low for M4s but balanced for M5s.  I think the M4/M5s have around the same noise level when running at the low power profile, but the M5 hardware options have  higher potential cooling needs as well as higher RPM capable fans.   Kirk... ... View more

If both FIs, all FC ports are loosing FLOGI with brocade ports, I would tend to suspect something in the brocade fabric. This may ultimately require some sort of FC analyzer/TAP (i.e. Finisar) inserted between the FIs and brocade to determine root cause. Are there any other non-UCS FC devices connected to the same linecards on the brocade switches? Kirk... ... View more

What are the actual fan RPMs? Connect to CIMC via ssh #connect debug-shell #sensors Should give an output similar to: MOD1_FAN1_SPEED | 10504.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD1_FAN2_SPEED | 10192.000 | RPM | OK | 784.000 | na | na | na | na | na | MOD2_FAN1_SPEED | 10504.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD2_FAN2_SPEED | 10192.000 | RPM | OK | 784.000 | na | na | na | na | na | MOD3_FAN1_SPEED | 10100.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD3_FAN2_SPEED | 10682.000 | RPM | OK | 784.000 | na | na | na | na | na | MOD4_FAN1_SPEED | 10504.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD4_FAN2_SPEED | 10682.000 | RPM | OK | 784.000 | na | na | na | na | na | MOD5_FAN1_SPEED | 10504.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD5_FAN2_SPEED | 10682.000 | RPM | OK | 784.000 | na | na | na | na | na | MOD6_FAN1_SPEED | 10504.000 | RPM | OK | 808.000 | na | na | na | na | na | MOD6_FAN2_SPEED | 10192.000 | RPM | OK | 784.000 | na | na | na | na | na | Also note the value for: TEMP_SENS_FRONT : TEMP_SENS_FRONT | 27.000 | degrees C | OK | na | na | na | na | 45.000 | 50.000 | Fan policy of 'balanced' will normally not suffice when multiple PCI-E cards are present, and you mention your config includes 2 of them. I don't believe those particular intel cards provide out of band thermal information to the CIMC, so the CIMC has to generally play it 'safe' and keep the fans in the upper ranges. I believe the M5 fans can hit 20,000 RPMs, so am curious as to what yours are actually running at. Please see: https://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-c-series-rack-servers/214478-ucs-c-series-m5-server-components-relati.pdf Kirk...   ... View more

Does this happen to one Xenserver at a time, only one side (A|B), and then eventually seem to spread, or all at the same time? Are your A and B FC fabrics completely separate? When you say 'drop an uplink' you mean the FI FC port goes into an error disabled state or down? It is possible for a erroring host/vHBA to send a bunch of CRC'd frames that could cause the pinned uplink port (or connected device s port) to auto disable, although this should't take an entire environment down unless we are hitting some sort of slow drain scenario... I'm assuming you have no actual FI FC port counter errors, or FI eth port counter errors going to the IOMs? There are a lot of ports that should probably be checked, vic adapter level stats, IOM ports, FIs Eth and FC ports.   What kind of errors have your FC ports logged from show int fc x/y?   What's the output of #show int fc x/y transceiver detail on your FI ports? Is there a particular host and pinned FC uplink that seems to go down first? What version of FNIC driver are you running?   You have a TAC case open for this I'm assuming?   Kirk...   ... View more

If it's UCSM integrated, you can disable/re-enable the vnic in the equipment view (there is also a 'reset' that would accomplish the same).  Are you trying force pinning for that host out one specific side of the FIs?  You could also adjust the vswitch/dVS teaming, and disable the vmnic out the side in question at the vmware level. If all else fails, take a capture at vmware level to see what is/isn't responding: pktcap-uw --uplink vmnicX https://kb.vmware.com/s/article/2051814   Also, confirm the vmnic for that physical host MAC address matches the vnic mac address in service profile, to confirm the vlans you think are programmed for the vnic/veth are really the interface you think it is at the vmware vmnic level assignment level.   It would also be helpful to understand the L2 connectivity between guestVM and the PXE/tftp server...  Perhaps your vnic/VMnic disabling can force connectivity such that both guestVM/and ESXi host,,, and the PXE server are pinned to the same FI (this assumes your PXE server is hosted in same UCSM), as this would avoid northbound switching.   Kirk...     ... View more