When a single UCS Manager domain contains a heterogeneous mix of different blade types with different processors and different memory footprints, it can be challenging to find the ideal blade for a given workload. I like to create a custom user label for each blade so that I can easily glance at the equipment tab and see what compute resources are available to me. The user label for each blade is shown in parenthesis as seen in the graphic below. By default, the user label field is blank and nothing is displayed next to the server on the equipment tab.
User label applied to each blade
No user label (default)
Easy to create a meaningless label
It's actually quite easy to set a custom label for all of your blades using PowerTool. Try this:
If it were really that easy, I wouldn't need to write a blog about it. If you tried that code, you found that you just gave every blade in your entire environment the same label. What is the point of labeling if everything is going to have the same label? Instead, let's examine how to set a unique label for each blade. We will start with serial number.
If you run that code, you will likely get an error because PowerShell doesn't recognize the function "Get-FriendlyProcName". You can read my last blog about generating friendly names for processors and just use the function I've created; or you can grab the one snippet from that function that you actually need and use this code instead:
That code will combine the model name, CPU name, and memory footprint of each blade to create a very useful user label as shown below.
Taking it further
Just a few lines of code can provide a very useful user label. What else can you display? How about the model of the mezz card installed? Firmware version(s)? Number and size of disks? MAC addresses? All of these are possible. Taking it a step further, I might only want to display a user label for blades that are available for me to use. If you want to label only blades that are not already in use, take a look at the Association property of each blade.
Did you know you can apply a user label to a chassis? You could display number of uplinks, number of power supplies -- or even something as drab as the serial number of the chassis.
User labels can be utilized to display information useful to your administrators, and I've just shown you that it is easy to do. Enjoy!
Hi,I received a minor warning on a server displaying CATERR_N:Sensor Failure Asserted.Looking at the SEL log I can see this happening like 1-4 times a year since the server was first initialized but has now occurred multiple times in the last few days. Sh...
I am upgrading our blades from m2 to m5. I put two m5's in and they are not recognized and giving the error f999560.When upgrading do you have to do it in order or can i just get the newest firmware or basic requirements for the blades and start from ther...
Hi all, I inherited a UCS domain that is registered to UCS Central. The WWPN, UID and MAC pools are managed using UCS Central along with the service profile templates. The UCS domain lost-visibility at some point to UCS Central. I need to un-register UCS ...
Hi, I have a customer that implemented DJL2 for a temporary project and DJL2 was setup correctly by placing the VLANs (via lan uplink mgr) on the appropriate uplinks. The environment is 10 chassis 4.0(4b). Currently there is only one port chann...
Hi experts,I have just deployed a Hyperflex cluster that uses the 4 port VIC 1457 interface card. Only two of the ports (1 & 3) are connected to the Fabric Interconnects as per these instructions.But UCS Manager now reports a Major error. T...