Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

16 Posts

625

February 10th, 2023 02:00

Poweredge C6400 change from C6420 to c6525

I  have been using several PowerEdge C6400 chassis with C6420 sleds successfully.

I now wish to use the same chassis now with 4 x C6525 sleds, but on boot of sled, message advises that I am using a C6525 in a chassis configured for c6420 chassis.

I also have some C6400 using C6525 sleds successfully too.

How do I make the C6525 work in the C6400 chassis which seems to only want C6420 sleds.

The CM board seems to be the same in both arrangements.

I have worked with RACADM AND chassis FW updates and also jumpers and DIP switches on chassis board to no success in conversion.   Even tried different BIOS and IDRAC versions. 

How can this be so difficult

Anyone know how to resolve this?

 

Moderator

 • 

5.1K Posts

April 28th, 2025 01:56

Hello, I think it's possible what Charles has linked may not have been open for you.
I say in this case, it's best that you contact Sales. You'll need APOS kits. Your chassis will need to be in warranty as well as new sleds and have a case open to your region support. 
https://www.dell.com/support/incidents-online/en-us/contactus/dynamic

Respectfully,

(edited)

Moderator

 • 

4.4K Posts

April 25th, 2025 14:39

Hello,

 

Maybe a user that has done this successfully without calling in to support can share their results

 

I have found this information, from the KB article #000063872 that Erman referenced.

https://www.dell.com/support/kbdoc/en-us/000063872

 

See if you can pull it up. You may need to log in and if that fails then it's an Internal KB.

 

Pertinent information I see:

 

Upgrade parts:

 

1)         APOS FAN Customer Kit

 

2)         Service Manpower to do Chassis Manager F/W Upgrade, Sticky Bit change, and NON-AVC Fan swapping

 

*The KB does not provide how that is done, only that it requires technician.

 

 

Ensure that the chassis does not have a mixed architecture of PowerEdge C6420 and PowerEdge C6525 sled configurations.

 

Moderator

 • 

2.8K Posts

February 10th, 2023 07:00

Hello, I found that adopting PE C6525 Sleds while reusing the existing PE C6400 Chassis to replace C6420 Sleds requires some steps and this is done via the service manpower. An upgrade combination is needed I can suggest contacting your local support and sales team. APOS FAN Customer Kit and Service Manpower to do Chassis Manager F/W Upgrade,  Sticky Bit change, and NON-AVC Fan swapping. 

 

Regards,

1 Rookie

 • 

16 Posts

February 14th, 2023 04:00

Hi Erman,

Thanks for providing information.

This must be something new as I have previously changed one of these chassis without problem using Racadm and the cm.sc files.

What do you mean by service manpower?
Is this something that could be resolved via a login with a Dell Tech to remove the sticky bit?

Please advise.

 

Moderator

 • 

2.8K Posts

February 14th, 2023 06:00

Hi, I found an internal article about it and it mentioned this process being done with a service technician. That's what I meant by service manpower.

1 Rookie

 • 

1 Message

January 23rd, 2025 19:31

Hi, i got the same problem. Tried flashing the firmware from the new node via RACADM withput any success. Tried different jumper positions and flashed the firmware again but with the same outcome.
While changing the jumper positions i found the serial connection on the CM board. After a few tries with different baud rates, i got the serial connection working (115200 baud) . When i plug in the newer node i get a message complaining about the sled planner type code being wrong. If i'm not mistaking i need to change it from 0x1C (old nodes) to 0x56 (new nodes). If i run "getChasIds" i get "CHASSIS ID from hidden configuration : 0x1c " so i probably need to change this also to 0x56 ? Is there a way to do this throug the serial connection ?

1 Rookie

 • 

13 Posts

April 24th, 2025 22:19

Hi TimothyMcGeek

I got same problem. Have you found a way to configure node 6525 on the C6400 chassis yet ?
Looking forward from you. Thanks !

1 Rookie

 • 

13 Posts

April 24th, 2025 22:22

Hi DELL-Erman O !

Can you provide sticky bit for node C6525 ?
Thank and best regards !

Moderator

 • 

5.1K Posts

April 25th, 2025 01:49

1 Rookie

 • 

13 Posts

April 25th, 2025 10:05

Hi DELL-Young E 
I tried with all firmware version (1.45, 2.37, 2.40, 2.62, 3.71) but still no luck.
Do you have other solution ?
Thank and best regards !

1 Rookie

 • 

13 Posts

April 28th, 2025 01:52

Hi DELL-Charles R

Can you provide documentation or instructions so I can do it myself.
Thanks you.

1 Rookie

 • 

1 Message

May 8th, 2025 15:43

We have the same issue, one of our chassis just needed updating and it now works fine with the C6525s, the other one doesn't even after many tries with different firmware.

We have the same output on the serial, CHASSIS ID from hidden configuration : 0x1C on the one that doesn't work and 0x56 on the one that does.

It's very frustrating as both have exactly the same spec and were on the same firmware to start with, even the service tags are in a similar range.

1 Rookie

 • 

2 Posts

June 13th, 2025 16:40

I just finished Update firmware for C6400 Chassis Manager Module. Here are my steps:

Requirements:

- You need a sled node with working iDRAC. Make sure you can login into iDRAC Web GUI and enable IPMI. In the iDRAC web interface, navigate to iDRAC Settings > Connectivity > Network > IPMI Settings and select Enable IPMI over LAN from the dropdown

Steps:

1. Install software (I'm using Windows => link for Windows)

Install IPMITOOL https://github.com/ipmitool/ipmitool/releases

Install Dell DRAC Tools: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=9dd9y

2. Download firmware for Chassis Manager

https://www.dell.com/support/product-details/en-us/product/poweredge-c6400/drivers

Version 2.70:

https://dl.dell.com/FOLDER06590162M/1/V270-2020-09-14-External.zip?uid=cbef9d37-c888-4a93-74f6-cea8810fbb08&fn=V270-2020-09-14-External.zip

Latest V3.71:

https://dl.dell.com/FOLDER10153260M/1/V371-2023-06-07-External.zip?uid=a1f96244-cc7d-480a-98b3-335058535c4d&fn=V371-2023-06-07-External.zip

4. Unzip the firmware file to have the cm.sc firmware file

5. Use ipmitool to check the FW version of the CM (You can Ask AI to translate the hex bytes to Dec version)

ipmitool -I lanplus -H <iDRAC IP> -U root -P <PASSWORD> raw 0x30 0x12

IANA PEN registry open failed: No such file or directory

01 ca 1b 02 46 01 00 00 00 02 02 00 01 2d 37 ff

ff 08 c2 00 00 00 08 01 08 10 64 23 fa 01

Major version: byte 4 => 02 Hex = 02 Dec
Minor version: byte 5 => 46 Hex = 70 Dec
Version = 2.70.x

6. Use DRAC Tool to install the firmware. You should try 2.x version first and then 3.x later

racadm -r <iDARC IP> -u root -p <PASSWORD> update -f cm.sc

Security Alert: Certificate is invalid - Certificate is not signed by Trusted Third Party
Continuing execution. Use -S option for racadm to stop execution on certificate-related errors.
The Copying Operation has begun,
This might take several minutes to complete, depending on the network.
Do not interrupt the operation.
RAC1066: Firmware update for cm.sc initiated successfully.

Wait for the process to complete and reboot the CM.

Use step #5 to check the new version of the firmware

1 Rookie

 • 

2 Posts

August 1st, 2025 13:35

Quick question, how do I change the sticky bit. This is the message I get.  

Moderator

 • 

4.4K Posts

August 1st, 2025 13:58

Hello,

 

Maybe someone has done this without contacting support can give their experience.

From the forum side I can only recommend contact Support directly (Service Manpower is technician required)

 

I have found this information, from the KB article #000063872 that Erman referenced.

https://www.dell.com/support/kbdoc/en-us/000063872

 

See if you can pull it up. You may need to log in and if that fails then it's an Internal KB.

 

Pertinent information I see:

Upgrade parts:

1)         APOS FAN Customer Kit

2)         Service Manpower to do Chassis Manager F/W Upgrade, Sticky Bit change, and NON-AVC Fan swapping

*The KB does not provide how that is done, only that it requires technician.

No Events found!

Top