cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4338
Views
15
Helpful
2
Comments
Tray Stoutmeyer
Cisco Employee
Cisco Employee

UCS - Re-numbering C-series integrated servers in UCSM when matching stale id numbers exist in UCS

 

Sometimes customers forget to decommission C-series integrated servers before doing an RMA. Many times this leads to an issue with stale duplicate ID numbers in UCS. For example, you have 3 rack servers numbered 1, 2, and 3 (C-series integrated) on UCSM. Server 3 has issues that needs an RMA to resolve. The FE or end customer doesn't decommission the server in UCSM and replaces it. When they integrate server 3 back into UCSM, it now shows up as server 4 instead of the id they wanted of server 3. This is because the act of yanking the server from UCSM without decommissioning left the id in the UCS db so server 3 is already allocated and will not be re-used. In my case, the customer had replaced the server 3 a couple times leading the server to ultimately show up as server 5 instead of 3. If you try to renumber the C-series using the normal means below in the link, it will say that id was already allocated and fail to save the change.

 

See the "Renumbering a Rack Mount Server" section on this doc:

 

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

 

If you see this error when renumbering the C-series integrated server on the decommissioned tab on UCSM, there is probably a stale entry on the UCS. You can also verify the current entries in the UCS db on an FI by running the below command.

 

UCS01-A# show config all | grep "recommission server"
 recommission server "Cisco Systems Inc" N20-B6625-1 FCH152372M8 N/A
 recommission server "Cisco Systems Inc" N20-B6625-1 FCH154571AR N/A
 recommission server "Cisco Systems Inc" N20-B6625-1 FCH154671LX N/A
 recommission server "Cisco Systems Inc" N20-B6625-1 FCH1545719M N/A
 recommission server "Cisco Systems Inc" N20-B6625-1 QCI1545A434 N/A
 recommission server "Cisco Systems Inc" UCSB-B200-M3 FCH164874ZW N/A
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1538A4ZH N/A
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1538A4ZT 3
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1543AAGP 1
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1543AAH4 4
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1641A73V 4
 recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1722A0HM 2

 

Here you can clearly see the 3 id entry as well as two 4 entries. This is why, after replacing the C-series and recommissioning it on UCSM, it shows up as 5 (3 and 4 already exist as stale entries that aren't associated with any real servers).


Typically the only way around this is to get a escalation open and get a DEV to help you delete the entry out of the FI. If you don't have the time to do all that, you can do the following work around. You can just make the existing 3 and 4 entries something really high up that they will never hit to free up the id you want. In my case we changed id 3, and the double id 4 entries to 100-102. Here is how you accomplish this.

 

recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1538A4ZT 100

recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1543AAH4 101
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1641A73V 102

 

This then freed up id 3 for the existing server 5 so I could renumber it in the UCSM. So, once we had this all changed, I was able to go into the UCSM GUI per the doc above and go to the decommission tab, select 5, change it to 3, check the recommission box, click save changes and it took it. The server came up with id of 3. Now the output shows the proper id's with the proper servers.

 

UCS01-A# show config all | grep "recommission server"
recommission server "Cisco Systems Inc" N20-B6625-1 FCH152372M8 N/A
recommission server "Cisco Systems Inc" N20-B6625-1 FCH154571AR N/A
recommission server "Cisco Systems Inc" N20-B6625-1 FCH154671LX N/A
recommission server "Cisco Systems Inc" N20-B6625-1 FCH1545719M N/A
recommission server "Cisco Systems Inc" N20-B6625-1 QCI1545A434 N/A
recommission server "Cisco Systems Inc" UCSB-B200-M3 FCH164874ZW N/A
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1538A4ZH N/A
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1538A4ZT 100
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1543AAGP 1
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1543AAH4 101
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1641A73V 102
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1722A0HM 2
recommission server "Cisco Systems Inc" UCSC-BASE-M2-C460 QCI1743A25L 3

 

This helped get the customer where they needed to be and also avoid an escalation that wasn't necessarily needed. The customer will never hit the 100-102 id numbers.

2 Comments
ramondelacruz
Level 1
Level 1

Good stuff, thanks Tray!

Hi, the procedure is right!

Another way you can do this is by decommission the server and then go the the decommission tab and click 2 times in the ID, change it, check the re-commission button and save changes.

 

After the server completes his tasks, you must assign the service profile again..

You can rename the profile with no affect in the UCSM infra.

 

Cheers

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: