ProLiant Servers (ML,DL,SL)
1825768 Members
2059 Online
109687 Solutions
New Discussion

HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

 
SOLVED
Go to solution
Zaini15
Occasional Collector

HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

hello im new into maintaining a servers, my Smart Array P410 controller board (462919-001) has an 512MB BBWC memory module (462975-001) with a broken Battery charger module (462976-001). im trying to replace Battery charger module (462976-001) but no one sells it, so i've bought 1GB FBWC memory module (505908-001) with FBWC super capacitor module assembly (587324-001).

when i plug the FBWC memory module into P410 the servers not detecting P410 Controller and can't access into Option ROM configuration for arrays utility (ORCA), then i try to use BBWC memory module and P410 is detected and it could access into ORCA (it could access ORCA without any memory module too).

does my P410 controller not support FBWC memory module ? but i've search into P410 Information reference, it should support the FBWC module (505908-001) with FBWC super capacitor module(587324-001) - P410 Information Reference.

what should i do to FBWC memory module works fine with my P410 Controller ?
any answers will help me alot, thanks

Regards
-Zaini

6 REPLIES 6
support_s
System Recommended

Query: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

System recommended content:

1. HP ProLiant DL160 G6 Server Series - Option Parts

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

Suman_1978
HPE Pro

Re: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

Hi,

Please check if the P410 needs a firmware update to detect the 1GB FBWC.

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Zaini15
Occasional Collector

Re: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

@Suman_1978 

thank you for your reply,

how do i check if my P410 controller needs an firmware updates ?
if it needed, where can i download the newest firmware ? and how to i install it ?

Regards
-Zaini

Suman_1978
HPE Pro
Solution

Re: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

Hi,

To check the firmware version of the controller, you can see that during POST or by using the Array utilities like Array configuration or Array diagnostics utility.

HP ProLiant Array Configuration Utility for Windows 64-bit
Array Configuration Utility User Guide
HP ProLiant DL160 G6 Server Software Configuration Guide

My previous post has firmware link, there you can view the installation instructions and download the file.

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Zaini15
Occasional Collector

Re: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

Thanks it works perfectly now.

When entering the newer firmware setup, it says my current firmware version was 1.66.
So i installed the 6.66 firmware version, and the FBWC cachce module works flawlessly!.

-Regards
Zaini

Sunitha_Mod
Honored Contributor

Re: HP Proliant DL160 G6 not detecting P410 controller after replace cache module to FBWC

@Zaini15 

Hello Zaini, 

That's excellent! 

We are extremely glad to know the issue has been fixed.