{"id":183,"date":"2014-04-27T12:54:21","date_gmt":"2014-04-27T19:54:21","guid":{"rendered":"http:\/\/blog.gptnet.net\/?p=183"},"modified":"2014-04-27T12:57:31","modified_gmt":"2014-04-27T19:57:31","slug":"hp-broadcom-based-network-adapters-firmware-7-8-21-fix-c04258318","status":"publish","type":"post","link":"https:\/\/blog.gptnet.net\/?p=183","title":{"rendered":"HP Broadcom-Based Network adapters firmware 7.8.21 fix &#8211; c04258318"},"content":{"rendered":"<p>&#8220;HP has released a very serious customer advisory saying that some Broadcom Nics which are used in G2-G6 servers and blades could be killed by a firmware update component in their HP Service Pack for Proliant 2014.02.<\/p>\n<p>Using HPSUM, HP SPP or Smart Components for VMware to update the \u201cComprehensive Configuration Management\u201d (CCM) firmware version to 7.8.21 can kill the nics which would require a hardware swap out to fix!&#8221;<\/p>\n<p>You can find advisory here:<br \/>\n<a title=\"HP Messed up\" href=\"http:\/\/h20566.www2.hp.com\/portal\/site\/hpsc\/template.PAGE\/public\/psi\/topIssuesDisplay\/?javax.portlet.begCacheTok=com.vignette.cachetoken&amp;javax.portlet.endCacheTok=com.vignette.cachetoken.&amp;javax.portlet.prp_efb5c0793523e51970c8fa22b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c04258304-1%257CdocLocale%253Den_US&amp;javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&amp;sp4ts.oid=1121516&amp;ac.admitted=1398619148164.876444892.199480143\" target=\"_blank\">HP Broadcom-Based Network Adapters &#8211; Updating Comprehensive Configuration Management Firmware Version 7.8.21 on Certain HP Broadcom-Based Network Adapters May Result in the Network Adapter becoming Nonfunctional<\/a><\/p>\n<p>If your server is out of warranty or you just don&#8217;t want to wait for hardware swap please read below. You need access to the server via remote management such as KVM or iLO. Of course, if you&#8217;re lucky you can perform this operation locally. In this post I will demonstrate how to recover BL460c G1 blade with bricked HP NC373i Multifunction Gigabit Server Adapter.<\/p>\n<p>I will be recovering NIC remotely using iLO.<br \/>\n<!--more--><br \/>\nHere&#8217;s what we are going to need:<br \/>\n&#8211; Bootable DOS iso: I prefer Freedos (please see below for download link)<br \/>\n&#8211; xdiag utility from Broadcom<br \/>\n&#8211; NIC firmware, which you can extract from HP&#8217;s update package. Firmware file will have .bin extension, which you will find after extracting HP&#8217;s package.<br \/>\n&#8211; iso editing software. I chose Ultraiso (please see below for download link)<\/p>\n<p>1. Download firmware upgrade package for NC373i and extract it. In our case file is cp021548.exe and firmware is located here: NIC_FW\\bootcode\\bc08s196.bin<br \/>\n2. Download xdiag utility and Freedos iso<br \/>\n3. Open Freedos iso and inject xdiag and firmware file. I put them in BIN folder.<br \/>\n4. Boot from our updated image via iLO and select Use Freedos in Live environment from the menu:<br \/>\n<a href=\"http:\/\/blog.gptnet.net\/wp-content\/uploads\/2014\/04\/freedos_boot.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-185\" src=\"https:\/\/blog.gptnet.net\/wp-content\/uploads\/2014\/04\/freedos_boot-300x141.png\" alt=\"freedos_boot\" width=\"300\" height=\"140\" \/><\/a><br \/>\n5. When freedos is loaded you will se command prompt. Go to root directory <em>cd ..<\/em>. Next change to folder with our utility and firmware. In our case it&#8217;s <em>cd bin<\/em>.<br \/>\n6. Run xdiag in engineering mode <em>xdiag -b06eng<\/em><br \/>\n7. <em>type device 1<\/em><br \/>\n6. <em>nvm fill 0 0x600 0<\/em><br \/>\n7. <em>nvm upgrade -bc bc08c740.bin<\/em><br \/>\n8. <em>nvm cfg<\/em> and typed &#8220;default&#8221; then typed 16=10 wich sets the BAR size to 32 for this NIC. At this point our NIC is functioning and it&#8217;s set with default Broadcom settings. If you save at this poing NIC will be detected as Broadcom instead of HP branded one. It will not allow you to be teamed. You have an option to type <em>SAVE<\/em> or set all HP options. Please see attached file nc373i_nvm.txt for HP&#8217;s options. You can enter them by typing settingnumber=value. After making changes don&#8217;t forget to type SAVE.<br \/>\n9. <em>device 2<\/em> and repeat steps 6-8 and don&#8217;t forget to change MAC address. Here&#8217;s the formula used by HP for MAC address assignment:<br \/>\n-&gt; NIC1 MAC=00:1e:0b:xx:e8:52<br \/>\n-&gt; NIC1 iSCSI MAC=00:1e:0b:xx:e8:53 (+1)<br \/>\n-&gt; NIC2 MAC=00:1e:0b:xx:e8:50 (-2 of NIC1)<br \/>\n-&gt; NIC2 iSCSI MAC=00:1e:0b:xx:e8:51 (+1 of NIC2)<br \/>\n10. <em>SAVE<\/em><br \/>\n11. <em>EXIT<\/em><br \/>\n12. At this point you should see DOS prompt. Perform\u00a0coldboot by issuing the following command <em>fdapm coldboot<\/em><\/p>\n<p>That&#8217;s it. After reboot you should have NICs in working condition.<\/p>\n<p>Here&#8217;s the list of NICs and their firmwares. I&#8217;ve included them in attached iso.<br \/>\nHP NC373T PCIe Multifunction Gig Server Adapter &#8211; bc08c196.bin<br \/>\nHP NC373F PCIe Multifunction Gig Server Adapter &#8211; bc08s196.bin<br \/>\nHP NC373i Multifunction Gigabit Server Adapter &#8211; bc08c196.bin<br \/>\nHP NC374m PCIe Multifunction Adapter &#8211; bc08c196.bin<br \/>\nHP NC373m Multifunction Gigabit Server Adapter &#8211; ???<br \/>\nHP NC324i PCIe Dual Port Gigabit Server Adapter &#8211; NC324I_v3.25.bin<br \/>\nHP NC326i PCIe Dual Port Gigabit Server Adapter &#8211; NC326I_v3.28S.bin or NC326I_v3.29C.bin<br \/>\nHP NC326m PCI Express Dual Port Gigabit Server Adapter &#8211; NC326I_v3.28S.bin or NC326I_v3.29C.bin<br \/>\nHP NC325m PCIe Quad Port Gigabit Server Adapter NC325M_v3.28S.bin<br \/>\nHP NC320i PCIe Gigabit Server Adapter &#8211; NC320M_v3.58.bin<br \/>\nHP NC320m PCI Express Gigabit Server Adapter &#8211; NC320M_v3.58.bin<br \/>\nHP NC382i DP Multifunction Gigabit Server Adapter &#8211; bc09x523.bin<br \/>\nHP NC382T PCIe DP Multifunction Gigabit Server Adapter &#8211; bc09x523.bin<br \/>\nHP NC382m DP 1GbE Multifunction BL-c Adapter &#8211; bc09x523.bin<br \/>\nHP NC105i PCIe Gigabit Server Adapter &#8211; NC105I_v3.09.bin<\/p>\n<p><a href=\"http:\/\/blog.gptnet.net\/wp-content\/uploads\/files\/fd11src_live_xdiag.iso\" target=\"_blank\">Download ISO here<\/a><br \/>\n<a href=\"http:\/\/blog.gptnet.net\/wp-content\/uploads\/2014\/04\/nc737i_nvm.txt\">nc737i_nvm.txt<\/a><\/p>\n<p>P.S If nic is working on another server you can create  a NVRAM-dump:<br \/>\n1. <em>xdiag \u2013b06eng<\/em><br \/>\n2. Select working device with device x (nr. of device)<br \/>\n3. <em>device 1<\/em><br \/>\n4. <em>nvm dump filename.nvr<\/em><br \/>\n5. <em>exit<\/em><\/p>\n<p>Restoe a dump, e.g. on NIC2 of the same server:<br \/>\n1. <em>xdiag \u2013b06eng<\/em><br \/>\n2. Select reanimated device with device x (nr. of device)<br \/>\n3. <em>nvm prg 0 filename.nvr<\/em><br \/>\n4. <em>nvm cfg<\/em> (check if all MAC-Addressen fit)<br \/>\n5. Press [ANYKEY] to check all parameters<br \/>\n6. enter save [ENTER]<br \/>\n7. exit<br \/>\n8. reboot server<\/p>\n<p>Reference:<br \/>\nhttp:\/\/h30499.www3.hp.com\/t5\/ProLiant-Servers-ML-DL-SL\/HP-Proliant-DL380-G5-NIC-s-not-found-after-firmware-update\/td-p\/6256615#.U0yd_53D8ug<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;HP has released a very serious customer advisory saying that some Broadcom Nics which are used in G2-G6 servers and blades could be killed by a firmware update component in their HP Service Pack for Proliant 2014.02. Using HPSUM, HP &hellip; <a href=\"https:\/\/blog.gptnet.net\/?p=183\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[57,54,58,59,55,56,60],"class_list":["post-183","post","type-post","status-publish","format-standard","hentry","category-random-stuff","tag-document-id-c04258318","tag-hp-broadcom-nic","tag-hp-nc373i","tag-hp-nc373i-firmware","tag-hp-proliant-bricked-nic","tag-hp-spp-version-2014-02-0","tag-nc326i"],"_links":{"self":[{"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/posts\/183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=183"}],"version-history":[{"count":14,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/posts\/183\/revisions"}],"predecessor-version":[{"id":199,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=\/wp\/v2\/posts\/183\/revisions\/199"}],"wp:attachment":[{"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.gptnet.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}