Mini H710P PERC in a server r.620 - updated the bios

Similar Questions

• Portege R600 - cannot update the BIOS using Win server 2008

  Hi all.

  Pls help...

  I tried to update my bios to the new version, but I can't.

  I just downloaded bios update of the toshiba site for portage r600 for my model number (bios update 1.80 - winner), I unzip the zip, run the exe, but error popup came:

  Package for the TOSHIBA BIOS ver.3.2.9
  Unsupported product type is installed.
  Package BIOS BIOS Version: Ver.1.80
  Current BIOS version: Ver.1.40

  So my question is what am I doing wrong? I'm trying to update my bios from windows.

  is my version of windows: windows server 2008 Enterprise Edition x 64 SP1 (don't ask why, I just have to run Server 2008)

  Thank you.

  Hello

  Your OS windows seems not to be the Windows which was preinstalled on your Portege
  You cannot update the BIOS by using the windows server 2008 Enterprise Edition x 64

  You will need to put the system which has been pre-installed by Toshiba

  Good bye

• problem with the ios certificate server does not update the CRL

  Hi all

  The background is that I'm putting a DMVPN solution with tunnels ipsec between the rays created by using certificates.

  I use a cisco 877 as the CA server (its 12.4 (6) T5) running to provide certificates for the spoke routers. This part works very well - rays can apply for a certificate and get a number very well.

  The problem is CA, life of LCR is set to 24 hours, but the CA is not updated the LCR so when the rays see CRL (as defined in their trustpoint) they point to a mistake that the CRL is obsolete and does not connect.

  If making a ' #sh cryptographic pki server ' it lists a ' CRL NextUpdate timer. It has a timestamp that is 24 hours after the last certificate was revocked. The only way I can get the LCR to be rebuilt must revoke a certificate.

  So, my question is, am I missing something here? I thought that it would automatically generations a new CRL list file every 24 hours.

  Can anyone help?

  Thank you.

  Hey Marc (?)

  This seems to correspond to this bug:

  CSCsy95838    AC IOS: LCR of the not updated, update timer not started

  However, it does not mention if 12.4 (6) T5 is affected, only that it was found 12.4 (15) T3 and resolved to 12.4 (15) T10 and other more recent versions.

  I suggest trying the last 12.4 (15) Tx, 15.0 (1) Mx or 15.1 (4) Mx version if you can.

  I assumed that you have much of it, but just in case: as a workaround, you can disable CRL checking on all routers DMVPN, of course they will still allow connections from routers with a revoked RADIUS.

  As (temporary?) substitute for a Revocation list, you can use a 'certificate ACL' with which you can create kind of a 'local CRL Manual:

    crypto pki certificate map certACL 10    serial-number ne    serial-number ne    etc. 

    crypto pki trustpoint myTP

     match certificate certACL
  
      (note the "ne" stands for "not equal" so you are permitting any certificate whose serial number is not listed) 

  Of course, you would have to configure (and maintain!) participating on each router in the DMVPN so it's heavy, but I guess if you revoke often certs, that it might be an option.
  HTH
  Herbert

  --

  If this post answered your question, please click the button of "right answer".

• Mini 311-1000NR. I lost after updating the Bios, NVIDIA graphics. I only have the standard VGA graphic

  I have a HP Mini 311-1000NR with Windows XP. After installing the update of the Bios I don't see NVIDIA video image. Instead of him, I am only the standard chart of VDA. I downloaded the driver and reinstalled but it installed only HD Audio not the NVIDIA graphics driver? How can I solve this problem? Can someone help me please?

  The problem is resolved. I installed Win7 Pro and after installing SP1, I got the graphics from NVIDIA.

  I can install the most recent driver that I have dl the NVIDIA web site

• Update the Bios ESXi server

  I use 5.1 ESXi and I want to upgrade the BIOS on the server. I downloaded the dell BIN file and place it in a tmp folder in the ESXi server. How can I install this bin file in the server? Can what commands I use to do it?

  Thank you

  Benito

  You won't be able to go in ESXi. See http://communities.vmware.com/people/vmroyale/blog/2010/12/29/how-to-install-vendor-updates-on-server-hardware-running-esxi for a set of instructions, that you can use.

• Files from the server does not update the when editing in Machine Windows 7

  I am editing the files on a server with a machine running windows 7 pro. Some files are not updated when changes are made, but the machine seems to be storing it locally. Does anyone have an idea on how to fix this? Thank you!

  Hello

  As you are working on a Windows Server environment I suggest you you posted the question under Windows Server TechNet forum for assistance from the public pro IT. see the following link:

  http://social.technet.Microsoft.com/forums/en/category/w7itpro

  Hope this helps

• Windows 2008 Server: unable to update the password. the value provided for the new password does not respect length, complexity, or history of the field requirements

  Unable to update the password. the value provided for the new password does not respect length, complexity, or history of the field requirements

  Hello

  I suggest you to send your request in this forum for better support.
  http://social.technet.Microsoft.com/forums/en/category/WindowsServer/

• How long does take to update the BIOS on a MIni 110?

  So far, my computer has worked with the message "if it please do not turn off or unplug your machine. Installation of update 1 of 1 "for more than 6 hours.  (It is still in progress!)  I'm currently in Shanghai, then holding a store of the computer seems unlikely, but I need this machine.  (Fortunately, I can use a computer at the University for some things, but not all.)

  I'm sure it was an update of the BIOS.  It finally finished the update after nearly 20 hours.

• Remote update of the BIOS r.620 with Ubuntu

  Anyone know if it is possible to update the bios of a r.620 (with iDrac Express) on Ubuntu 12.04.3 remote.

  I have problems of the E5-2630 Intel processor performance and read that it could be solved in update of the bios to the latest version:

  BIOS_T2RVC_LN_2.1.3.BIN

  I tried to run the bin file

  But I had lines like:

  . / BIOS_T2RVC_LN_2.1.3.BIN: 165:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 166:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 167:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 168:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 169:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 170:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 200:. / BIOS_T2RVC_LN_2.1.3.BIN: deal: not found
  . / BIOS_T2RVC_LN_2.1.3.BIN: 684:. / BIOS_T2RVC_LN_2.1.3.BIN: syntax error: "(" unexpected

  Kind regards
  Marcel

  Hello Marcel

  I don't think that we create updates designed to work under Ubuntu. The easiest way for you to make the updates would be through the iDRAC. Connect to the web interface via the IP address of the iDRAC and choose the option to update and restore in the left column.

  You can run windows 32 bit Dell Update Packages (DUP) from there. You can update THE system BIOS, firmware, PERC, iDRAC firmware and most other firmware the iDRAC using this method. Is the independent operating system, is a great way to make updates when you run Ubuntu, ESXi or other OS generally don't write us updates for.

  Thank you

• Problems with Dell r.620 updated

  Today, I tried to make 3 x updates 3 Dell r.620 as follows:

  • BIOS 2.4.3 to 2.5.2
  • 16.0.24 to 16.5.20 Intel NETWORK card firmware
  • iDRAC Firmware Version to 2.10.10 (iDRAC settings rest 1.65.65.04 Version)

  All 3 of r.620 had identical firmware for starters.

  I applied updates for 3 r.620 systems at the same time through iDRAC Express Web GUI update mechanism.

  On the first 2 systems, the updates worked fine.

  On the last system, I'm in trouble.  When I came back to this system, he has been "priming" and say "entering the lifecycle controller...". "but after half an hour, it does not!  I noticed that whenever I would it boot, he'd do the same thing... "Entering Lifecycle Controller"... then when it is arrived until the moment where Intel Boot Agent initialize, there are two points, then a blank line... then the machine would just stand there.

  Through racadm, I managed to reset the State of the life cycle of the inverter and remove the queue of work hoping I could reflash just updates and everything would be fine.  Now, the system does exactly the same thing, except that it does not seek to enter the controller of life cycle more.  Now, when he's sitting there, he is not "completely" hooked - in other words, if I hit F2 it will say that it is entering the system setup, press F10 he'll say he'll perform a PXE boot... etc... in fact, you can hit all the F keys and he'll say he'll enter system configuration , PXE boot, enter BIOS Boot Menu, etc...

  I am suspicious it is necessary with a failed NETWORK upgrade card... Here's what I see in the racadm for BIOS swinventory:

  -------------------------------------------------------------------

  ComponentType = BIOS
  ElementName = BIOS
  FQDD = BIOS. Setup.1 - 1
  InstallationDate = NA
  Version Rollback = 2.4.3
  -------------------------------------------------------------------

  ComponentType = BIOS
  ElementName = BIOS
  FQDD = BIOS. Setup.1 - 1
  InstallationDate = NA
  Available version = 2.5.2
  -------------------------------------------------------------------

  ComponentType = BIOS
  ElementName = BIOS
  FQDD = BIOS. Setup.1 - 1
  InstallationDate = 2015-03-12 T 12: 49:29Z
  Current version = 2.4.3
  -------------------------------------------------------------------

  Hmmm... Current version seems to be 2.4.3 with AVAILABLE version 2.5.2.  (which is strange as when starting the machine, it reports the 2.5.2 BIOS)

  and for the NETWORK card:

  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Ethernet Intel(r) 10 P 4 X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 62
  FQDD = NIC. Integrated.1 - 2-1
  InstallationDate = NA
  Rollback Version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Ethernet Intel(r) 10 P 4 X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 62
  FQDD = NIC. Integrated.1 - 2-1
  InstallationDate = NA
  Available version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Ethernet Intel(r) 10 P 4 X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 62
  FQDD = NIC. Integrated.1 - 2-1
  InstallationDate = 2015-03-13 T 10: 50:01Z
  Current version = 16.0.24
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 64
  FQDD = NIC. Integrated.1 - 3-1
  InstallationDate = NA
  Rollback Version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 64
  FQDD = NIC. Integrated.1 - 3-1
  InstallationDate = NA
  Available version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 64
  FQDD = NIC. Integrated.1 - 3-1
  InstallationDate = 2015-03-13 T 10: 50:07Z
  Current version = 16.0.24
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 65
  FQDD = NIC. Integrated.1 - 4-1
  InstallationDate = NA
  Rollback Version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 65
  FQDD = NIC. Integrated.1 - 4-1
  InstallationDate = NA
  Available version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Gigabit Intel (r) 4 p X 540/I350 rNDC - B8:CA:3 A: 69:3 A: 65
  FQDD = NIC. Integrated.1 - 4-1
  InstallationDate = 2015-03-13 T 10: 50:08Z
  Current version = 16.0.24
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:30
  FQDD = NIC. Slot.3 - 1-1
  InstallationDate = NA
  Rollback Version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:30
  FQDD = NIC. Slot.3 - 1-1
  InstallationDate = NA
  Available version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:30
  FQDD = NIC. Slot.3 - 1-1
  InstallationDate = 2015-03-13 T 10: 50:03Z
  Current version = 16.0.24
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:31
  FQDD = NIC. Slot.3 - 2-1
  InstallationDate = NA
  Rollback Version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:31
  FQDD = NIC. Slot.3 - 2-1
  InstallationDate = NA
  Available version = 16.5.20
  -------------------------------------------------------------------

  ComponentType = FIRMWARE
  ElementName = Intel Gigabit 2 p I350-t adapt - A0:36:9F:2E:F8:31
  FQDD = NIC. Slot.3 - 2-1
  InstallationDate = 2015-03-13 T 10: 50:05Z
  Current version = 16.0.24
  -------------------------------------------------------------------

  If the versions downloaded, but the current version is not the new version.

  I checked in other systems, and it is.

  Now, I tried to go back in idrac7 web GUI and rollback, but it says that it cannot do.
  At the same time, the BIOS boot screen shows the BIOS as being 2.5.2!

  I had a conversation with Dell.  The conclusion was that the motherboard and possibly the network card girl needs to be replaced... somebody's going to come out on Friday to do...  That being said, I'm 99% sure that there is a way to solve this problem by replacing the entire Board.  I 99% sure because I think to solve the problem requires the system to enter the lifecycle controller, which does not now... and no matter what job I can queue through the UI web or racadm won't do much if it cannot access the lifecycle controller.

  I can still access the idrac via web and ssh.  I tried to work on the jobqueue change LegacyBootProto None of PXE, thinking that this MIGHT get rid of the "Intel Boot Manager" prompt, but when the system boots, it does not it:

  racadm view jobqueue
  -------------------------JOB QUEUE------------------------
  [Job ID = JID_285566585779]
  Job Name = configure: NIC. Integrated.1 - 1-1
  Status = on demand
  Start time = [now]
  Timeout = [not Applicable]
  Message = [JCP001: task successfully on demand.]
  ----------------------------------------------------------

  I don't even know whether or not the problem is, really, the Boot Manager.

  I thought about another possibility... If it's Boot Manager... If I disable the NIC daughter through racadm card, then I would immediately lose access to idrac and not be able to return to the previous state, but if the deactivation of the card would let me go further so that I could get back in the lifecycle controller and fix things then maybe it's worth? Don't know.

  Any thoughts?

  Jason.

  Yes. I tried this option.  It's the same thing.  (hang after Intel Boot Agent).

  The motherboard of the server has been replaced, and I am currently re - install the updates... Already updated the BIOS which is come with this (2.2.2) server could not update 2.5.2.  I'm now trying an update of the idrac.  All these problems with the updates are frustrated to no end.

  Jason.

• Mini 110 is not to find the hard drive in the bios

  I fix this hp mini 110 1025dx for a friend model...

  I can't find the hard drive in the bios... after removing the HD (seagate 160 GB), I could not mount the drive, with windows or Linux... Re-installed the HD and the bios still cannot find HD help... Please...

  Thanks, in advance

  Hello @quickcarl,

  Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums, I would like to draw your attention to the HP Forums Guide first time here? Learn how to publish and more.

  I stumbled upon your post on the issue of BIOS and wanted to help!

  Have you tried to restore, or update the BIOS?  Try to review the following document and let me know how it goes: HP Notebook PC - BIOS recovery

  Please let me know if this information helps you solve the problem by marking this message as 'accept as Solution' , this will help others easily find the information they seek.  In addition, by clicking on the Thumbs up below is a great way to say thank you!

  Have a great day!

• Mini Compaq CQ10 - 514 is looping without end, recovery, and verification of the BIOS

  When the laptop was turned on it is initialized in a screen announcing that an update of the BIOS of HP had taken place.

  However he said then there was a problem. "THE system BIOS is damaged and needs to be recovered but must be connected to an external power supply." Connected alternating current, then it goes to "system BIOS is recovering" and continues to load. Then he performs a check and indicates "recovery is over and press to complete.

  After 25 seconds. update of the BIOS screen is displayed again indicating that the BIOS is being recovered. This update cycle, check and restart continues to always (all day). Pressing ESC didn't break it. Pressing the button while pressing the Windows key + B is not recognized.

  remove the battery and common alternative for an extended period does not help that the cycle continues to restart. What is the market to follow recommended action?

  Thought I would update this for the sake of others with similar issues.

  Support HP told me to restore the default BIOS by pressing F10 when the delivered system running. Unfortunately, the system does not recognize the key and immediately went in the loop described previously.

  At the end of the day, I returned the PC to the store where you bought it. Technical support told me there was nothing they could do and it would go back to HP so that it sets. So, basically, it was bricked.

  However the tech guy has decided to experiment and found that remove the small coin of size internal CMOS battery it caused the Mini back to deafult factory BIOS and the device is back to normal.

  Lessons learned: do not automatically update the BIOS. When all else fails try to remove the internal CMOS battery.

• Test server tries to use the old IDs after reboot etc.

  I have just formatted my drive and installed fresh xampp, pulled my web files on the net and got the testing running server.  I can access the pages that use my vidiscript DB, but for some reason when I try to access pages that use the same PB it gives me an error of:

  Access denied for user 'deafboyz_admin'@'localhost' (using password: YES)

  deafboyz_admin is the OLD username for DB, that my remote DB uses, which is painfully different than the testing server.  I updated the DB file and saved and made sure it's correct on the test server.  Restart xampp and even my computer, deleted history of cookies etc and still get this same error.  It makes me crazy b/c my main homepage must use the db file for data and it works perfectly, but video pages it attempts to use the old credentials, which are not loaded in my test server.

  as a solution, I even added the user deafboyz_admin in the db and gave full privileges, reboot, etc and still no luck.

  all my passwords are loaded into the local Database as they are in the file db.  restarted the computer and clear the history, what else could be possibly originally xampp try using the old db details?

  Thank you for your understanding!

  There is always something that connects your video to a file that is trying to connect to the DB by using the credentials of the old. You can share your PHP code with us login script? Also, check that the connection on the video page setting is correctly set in the correct file that contains the new credentials.

• Referred to Dell r.620 and H710P PERC - backplane cable?

  Read this thread:

  http://en.community.Dell.com/support-forums/servers/f/906/p/19471857/20339141.aspx

  We ordered PERC H710P customer mini kit (342-3536-PCVT5) and 2 x 800 GB Solid State Drive SATA value MLC 3Gbps 2.5 in. (342-5821) for our r.620 (which previously only had the on-board controller S110). Can someone help me identify the part number for the cable necessary? Looking around without success.

  Hello

  As you initially had the S110 and it only supports the background configuration of the 4 HARD drive backplane I'll assume that it is the bottom of basket you have. If this is the case then the part number for the cable you need is:

  WVF6J

  This is the background cable basket for a PERC 4 HDD backplane SAS A connection mini. It works with all mini girl PERC cards in the r.620; who are the H310 and H710 (p).

  Normal sales agents in general have not access to sell these parts. In general they cannot sell the new components that are designated by a 7-digit reference number in this format 111-1111. Our spare parts department is who you must contact to buy spare parts 5 figures.

  http://www.Dell.com/support/contents/us/en/04/article/contact-information/sales/sales-phone-numbers

  800 357-3355 is the number listed for them. Be sure to reference the contact page in the future as long as the number can change. It will be not updated in this post, but it will be updated on the contact page.

  Thank you

• Fake H710p PERC? -Firmware upgrade error

  Hallo,

  I recently bought a DELL PERC's H710p to the address but I can't update the firmware or install the driver. I always get an error like:
  "No controllers present or detected."

  First I thought that this is because the PERC H710p is not supported on a DELL R710 server. But after some research, I found something weird.

  The reason why the update of the firmware fails is simply the fact, that the "SUBDEV = 1f38" required when updating cannot be fond. My 'H710p' has a different SUBDEV. His SUBDEV is 1f77. So my question is, I bought some controller "false"?

  If this is not a 'fake' controller, what should I do to update my H710p and how to install the drivers?

  Thank you

  Here is the log from Megafl:

  Card #0

  ==============================================================================
  Versions
  ================
  Product name: adapter PERC H710P
  Serial number : xxxxx - Im not sure if its save to publish a sn on the internet. But if a job DELL need to check the controller, please send me a PM.
  FW Package Build: 21.0.2 - 0002

  Data from MFG.
  ================
  MFG Date: 01/04/13
  Transfer date: 01/04/13
  Revision no.: A00
  Battery FRU: n/a

  Version of the image in Flash:
  ================
  BIOS version: 5.30.00_4.12.05.00_0x05110000
  CTRL-R Version: 4.00 - 0014
  Pre-launch CLI version: 05.00 - 03: # 00008%
  FW version: 3.130.05 - 1587
  NVDATA Version: 2.1108.03 - 0093
  Boot block version: 2.03.00.00 - 0003
  STARTING version: 06.253.57.219

  Images pending in Flash
  ================
  None

  PCI Info
  ================
  Provider code: 1000
  Device ID: 005
  SubVendorId: 1028
  SubDeviceId: 1f77

  Host interface: PCIE

  Frontend Port number: 0
  The Device Interface: PCIE

  Backend Port number: 8
  Port: address
  0 4433221102000000
  1 4433221103000000
  2 0000000000000000
  3 0000000000000000
  4 0000000000000000
  5 0000000000000000
  6 0000000000000000
  7 0000000000000000

  HW configuration
  ================
  SAS address: 590b11c04b521300
  BBU: present
  Alarm: Absent
  NVRAM: present
  Debugger series: present
  Memory: present
  Flash: present
  Memory size: 1024MB
  TPM: Absent
  On board the Extender: Absent
  Key update: Absent
  Sensor of temperature for ROC: present
  For controller temperature sensor: present

  ROCK temperature: 57 degrees Celcius
  Temperature controller: 57 degrees Celcius

  Parameters
  ================
  Current time: 20:28:33 9/4, 2013
  Predictive failure polling interval: 300sec
  Interrupt the active gas number: 16
  Interrupt the completion of the throttle: 50us
  Regeneration rate: 30%
  PR rate: 30%
  BGI rate: 30%
  Consistency check rate: 30%
  Rebuild rate: 30%
  Cache flush interval: 4 s
  Max led to spin-up at the same time: 4
  Between groups of spin-up time: 12s
  Coercion of physical training mode: 128 MB
  Cluster mode: disabled
  Alarm: disabled
  Auto regeneration: enabled
  Battery warning: enabled
  ECC bucket size: 15
  ECC bucket leak rate: 1,440 Minutes
  Restore the hot spare to the Insertion: disabled
  Exposing pregnant devices: disabled
  Keep the history of the PD Fail: disabled
  Reorganization of host application: enabled
  Auto Detect Enabled BackPlane: SGPIO/i2c MS
  Load balancing mode: automatic
  Use only the FDE: Yes
  Security assigned key: No.
  Security key failed: No.
  Not saved security key: No.
  Default policy LD PowerSave: controller set
  Maximum number of disks to connect direct to the top at 01:00
  Any Cache offline VD kept: No.
  Allow booting with preserved Cache: No.
  Disable controller Reset online: No.
  KFC in NVRAM: No.
  Use the disk activity to locate: No.

  Capacity of
  ================
  RAID levels supported: RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, 11 with covering PRL, layout of PRL11-RLQ0 DDF with no span, DDF PRL11-RLQ0 available with span
  Supported disc: SAS, SATA

  Permit mixture:

  Mix allowed attachment

  Status
  ================
  ECC Bucket Count: 0

  Limits
  ================
  Max of weapons by VD: 32
  Max extends by VD: 8
  Max tables: 128
  Maximum VDs: 64
  Max parallel orders: 1008
  County EMS max: 60
  Max Data transfer size: 8192 sectors
  Max band PerIO: 42
  Band of min size: 64 KB
  Max band dimensions: 1. 0 MB
  CacheCade varied size: 512 GB
  Current size of CacheCade: 0 GB
  The current size of the Cache FW: 887 MB

  Current device
  ================
  Virtual drives: 1
  Gradient: 0
  Offline: 0
  Physical devices: 2
  Disks: 2
  Critical records: 0
  Has no records: 0

  Card operations support
  ================
  Rebuild rates: Yes
  Rate of CC: Yes
  BGI rate: Yes
  Rebuild rates: Yes
  Patrol read rate: Yes
  Alarm control: Yes
  Cluster support: No.
  BBU                             : No
  Spanning: Yes
  Dedicated backup: Yes
  Reversible spare discs: Yes
  Foreign Config import: Yes
  Auto diagnosis: Yes
  Allow the joint redundancy on table: No.
  World Relief: Yes
  Deny SCSI Passthrough: No.
  Reject the SMP Passthrough: No.
  Deny STP Passthrough: No.
  Security: Yes
  Snapshot enabled: No.
  Support ECO without adding drives: Yes
  Support the KFC: No.

  Operations supported VD
  ================
  Read the policy: Yes
  Write policy: Yes
  IO policy: Yes
  Access policy: Yes
  The strategy of Disk Cache: Yes
  Reconstruction: Yes
  Deny locate: No.
  Reject the CC: No.
  Allow encryption Ctrl: No.
  Turn on LDBBM: Yes
  Breakmirror support: Yes
  Energy savings: Yes

  PD supported operations
  ================
  Force online: Yes
  Force offline: Yes
  Rebuild the force: Yes
  Deny the Force failed: No.
  Deny the good/bad Force: No.
  Refuse to replace missing: No.
  Deny Clear: Yes
  Deny locate: No.
  Support temperature: Yes
  Disable the Copyback functionality: No.
  Enable JBOD: No.
  Enable the feature Copyback on CHIP: No.
  Activate Copyback of SSD on SMART error: No.
  Select SSD read: No.
  PR Correct unconfigured areas: Yes
  Enable Spin Down of unconfigured disks: No.
  Turn off the Spin Down of the hot spare function: Yes
  Spin-Down time: 30
  T10 power state: Yes
  Errors counters
  ================
  Memory correctable: 0
  Mistakes not rectifiable memory: 0

  Cluster information
  ================
  Authorized cluster: no
  Cluster Active: No.

  Default settings
  ================
  PHY polarity: 0
  PHY PolaritySplit: 0
  Base rate: 30
  Band size: 64 KB
  Hunting time: 4 seconds
  Write policy: WB
  Read the policy: Adaptive
  Be cached when BBU Bad: disabled
  IO caching: No.
  SMART mode: Mode 6
  Turn off the alarm: No.
  Mode of coercion: 128 MB
  ZCR Config: unknown
  Dirty disk activity LED Watch: No.
  BIOS continue on error: No.
  Spin-Down Mode: no
  Authorized device type: SAS/SATA Mix
  Allow Mix attachment: Yes
  Allow to Mix SAS/SATA HDD to VD: No.
  Allow Mix SAS/SATA SSD in VD: No.
  Allow Mix HDD/SSD in VD: No.
  Enable SATA in Cluster: No.
  Chained Max speakers: 4
  Disable Ctrl-R: No.
  Enable Web BIOS: No.
  Direct Mapping PD: Yes
  BIOS enumerate VDs: Yes
  Restore the hot spare integration: No.
  Exposing pregnant devices: No.
  Keep the history of the PD Fail: No.
  Disable any perforation: No.
  Zero based speaker enumeration: Yes
  PreBoot CLI enabled: no
  Disk activity see the LED: Yes
  Disable cluster: Yes
  Disable SAS: No.
  Auto Detect Enable BackPlane: SGPIO/i2c MS
  Use only the FDE: Yes
  Led enable header: No.
  Delay during the POST: 0
  EnableCrashDump: No.
  Disable controller Reset online: No.
  EnableLDBBM: Yes
  Uncertified hard disk drives: enable
  Treat simple span R1E as R10: Yes
  LD max by the Bay: 16
  Energy saving option: don't turn down the readers not configured
  Don't turn down hot spares
  Do not Auto centrifuge configured Drives
  Power settings apply to all readers - cannot set the individual parameters of power PD/LD
  Max power savings option is not allowed for LDs. supply Conditions only T10 should be used.
  Written in cache is not used for queue down VDs
  Annex can disable save energy at the level of the controller
  By default the spin time in minutes: 30
  Enable JBOD: No.
  Journal of the ATS in Flash: no
  Auto improved Import: No.
  BreakMirror RAID support: Yes
  Disable the join mirror: Yes
  Time required to detect the CME: 60 s

  Exit code: 0x00

  Controllers H710 series have been tested and validated in the Dell only 12 servers (such as the PE 720) generation.   Further, check your H710p came from a Precision Workstation.  The following valid this information, which came from the file nocheck.bat for this controller:

  OFF @Echo
  CLS

  put the FW = 21.0.2 - 0002
  Set ROM = H710PAWS.rom
  SUBDEV = 1f77 set
  DOS32A = set / AC /NOWARN:9004

   
  You will need this patch: http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=CGM2K which is the latest available for this particular controller.

  The controller may or may not work in your PE710, it just has not been tested or validated.  Good luck!

  Kind regards