misc fixes (spacing, fastiron linux password etc)
This commit is contained in:
Jon Sands
parent
7f2565bd13
commit
c227c7126d
|
|
@ -84,8 +84,12 @@ If you have a non-linux based switch (eg ICX6610) and you REALLY want to extract
|
|||
|
||||
Now run the following in the bootloader:
|
||||
```
|
||||
#dump the first 32MB of flash (this is usully enough)
|
||||
dd f4000000 8388608
|
||||
|
||||
#alternatively, dump the full 64MB flash chip
|
||||
dd f4000000 16777216
|
||||
```
|
||||
It will start printing the raw flash contents line by line in your serial window for a second, then stop. When it stops, press enter (NOT space), to make it continue dumping without user input, so it will dump overnight, and putty will be logging it.
|
||||
|
||||
This will take about 10 hours, so go to bed. In the morning, reboot the switch, and take a look at your putty log file. The dump will only be in raw hex, not ASCII - so to find your license strings you need to search the dump for `2a4220` which is the license start string `*B ` in hex. Once you find that, copy the following several blocks of hex values and paste them all into an online hex to ASCII converter, and you should get your string. Make sure you don't paste the leading memory address bits like `f40001e0:` into the converter.
|
||||
This will take about 12 hours per 32MB, so go to bed. In the morning, reboot the switch, and take a look at your putty log file. The dump will only be in raw hex, not ASCII - so to find your license strings you need to search the dump for `2a4220` which is the license start string `*B ` in hex. Once you find that, copy the following several blocks of hex values and paste them all into an online hex to ASCII converter, and you should get your string. Make sure you don't paste the leading memory address bits like `f40001e0:` into the converter.
|
||||
|
|
@ -5,10 +5,10 @@
|
|||
## Updating The Software
|
||||
Download the ZIP below, which contains the firmware files and documentation you'll need.
|
||||
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
|
||||
|
||||
**Connect** to the switches serial/console port using a program like Putty (9600 8N1), and connect the dedicated management port to your network (do not use a "normal" port).
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
## Preparation
|
||||
Download the ZIP below, which contains the firmware files and documentation you'll need.
|
||||
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
|
||||
|
||||
**Connect** to the switches serial/console port on the front using a program like Putty (9600 8N1), and connect any of the normal switch ports to your network (do NOT use the dedicated management port).
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
## Preparation
|
||||
Download the ZIP below, which contains the firmware files and documentation you'll need.
|
||||
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
[```Brocade v8030 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8030t.zip)
|
||||
```SW version: 08030t```
|
||||
```ZIP Updated: 03-21-2019```
|
||||
```MD5: 6f4b1c6b2f1faf4c8c5d1f647b6505f2```
|
||||
|
||||
|
||||
**Connect** to the switches serial/console port on the rear using a program like Putty (9600 8N1), and connect the rear copper management port to your network.
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@
|
|||
## Preparation
|
||||
Download the ZIP below, which contains the firmware files and documentation you'll need.
|
||||
|
||||
[```Brocade v8080 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8080e.zip)
|
||||
```SW version: 08080e```
|
||||
```ZIP Updated: 10-29-2019```
|
||||
```MD5: 0d9c19da7ab9c9e69596efc7235da27b```
|
||||
[```Brocade v8080 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8080e.zip)
|
||||
```SW version: 08080e```
|
||||
```ZIP Updated: 10-29-2019```
|
||||
```MD5: 0d9c19da7ab9c9e69596efc7235da27b```
|
||||
|
||||
|
||||
**Connect** to the switches serial/console port on the front using a program like Putty (9600 8N1), and connect any of the normal switch ports to your network (do NOT use the dedicated management port).
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
## Preparation
|
||||
Download the ZIP below, which contains the firmware files and documentation you'll need. The ICX7250 and ICX7450 run the same PoE firmware, bootloader, and OS image so this guide can be used for either.
|
||||
|
||||
[```Brocade v8080 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8080e.zip)
|
||||
```SW version: 08080e```
|
||||
```ZIP Updated: 10-29-2019```
|
||||
```MD5: 0d9c19da7ab9c9e69596efc7235da27b```
|
||||
[```Brocade v8080 Firmware/Docu Zip```](https://fohdeesha.com/data/other/brocade/8080e.zip)
|
||||
```SW version: 08080e```
|
||||
```ZIP Updated: 10-29-2019```
|
||||
```MD5: 0d9c19da7ab9c9e69596efc7235da27b```
|
||||
|
||||
|
||||
**Connect** to the switches serial/console port on the front using a program like Putty (9600 8N1), and connect any of the normal switch ports to your network (do NOT use the dedicated management port).
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# Welcome
|
||||
This is the home of all public documentation by Jon Sands. Originally planned as documentation to share amongst [FBOM](http://fbom.club/) members, it has become more useful on [STH](https://forums.servethehome.com/index.php?threads/brocade-icx6450-icx6610-etc.21107/). Pull requests to the [github repo](https://github.com/Fohdeesha/lab-docu) are always welcome.
|
||||
This is the home of all public documentation by Jon Sands. Originally planned as documentation to share amongst [FBOM](http://fbom.club/) members, it has become most useful on [STH](https://forums.servethehome.com/index.php?threads/brocade-icx6450-icx6610-etc.21107/). Pull requests to the [github repo](https://github.com/Fohdeesha/lab-docu) are always welcome.
|
||||
|
||||
Other documentation I have written or contributed to:
|
||||
|
||||
- [Brokeaid Crossflashing](https://brokeaid.com/)
|
||||
- [Xen Orchestra](https://xen-orchestra.com/docs/)
|
||||
- [XCP-ng](https://github.com/xcp-ng/xcp/wiki)
|
||||
- [XCP-ng](https://xcp-ng.org/docs/)
|
||||
|
|
|
|||
18
docs/jtag.md
18
docs/jtag.md
|
|
@ -39,11 +39,11 @@ On an LB6M, the connection should look like this:
|
|||
|
||||
Now that everything is plugged in and the BDI2000 is powered, power up the switch.
|
||||
|
||||
**Startup Order Summary:**
|
||||
1. Connect ethernet to the BDI2000
|
||||
2. Connect the power brick to the BDI2000
|
||||
3. Connect the BDI2000 to the switch JTAG header
|
||||
4. Power on the switch
|
||||
**Startup Order Summary:**
|
||||
1. Connect ethernet to the BDI2000
|
||||
2. Connect the power brick to the BDI2000
|
||||
3. Connect the BDI2000 to the switch JTAG header
|
||||
4. Power on the switch
|
||||
|
||||
## JTAG Commands
|
||||
|
||||
|
|
@ -95,9 +95,9 @@ Once you have confirmed it has booted succesfully - unplug/power off the switch
|
|||
|
||||
Unplug the switch power first! When the switch is off and powered down, then unplug the power cable from the BDI2000, then disconnect it from the JTAG header, and you are done. **PLEASE SEND ME THE badboot.bin FILE FROM YOUR TFTP SERVER!** This will allow me to see exactly what got corrupted on your switch.
|
||||
|
||||
**Shutdown Order Summary:**
|
||||
1. Power down the switch (unplug power)
|
||||
2. Power down the BDI2000 (unplug power brick)
|
||||
3. Disconnect the BDI2000 16 pin cable from the JTAG header
|
||||
**Shutdown Order Summary:**
|
||||
1. Power down the switch (unplug power)
|
||||
2. Power down the BDI2000 (unplug power brick)
|
||||
3. Disconnect the BDI2000 16 pin cable from the JTAG header
|
||||
|
||||
Put the switch cover back on. Now that your switch is booting into the bootloader, you can go and follow the [flashing guide](https://brokeaid.com/#booting-brocade) - start from the **Booting Brocade** section as linked.
|
||||
|
|
|
|||
|
|
@ -41,11 +41,11 @@ On an ICX6610, the connection should look like this:
|
|||
|
||||
Now that everything is plugged in and the BDI2000 is powered, power up the switch.
|
||||
|
||||
**Startup Order Summary:**
|
||||
1. Connect ethernet to the BDI2000
|
||||
2. Connect the power brick to the BDI2000
|
||||
3. Connect the BDI2000 to the switch JTAG header
|
||||
4. Power on the switch
|
||||
**Startup Order Summary:**
|
||||
1. Connect ethernet to the BDI2000
|
||||
2. Connect the power brick to the BDI2000
|
||||
3. Connect the BDI2000 to the switch JTAG header
|
||||
4. Power on the switch
|
||||
|
||||
## JTAG Commands
|
||||
|
||||
|
|
@ -97,9 +97,9 @@ Once you have confirmed it has booted succesfully - unplug/power off the switch
|
|||
|
||||
Unplug the switch power first! When the switch is off and powered down, then unplug the power cable from the BDI2000, then disconnect it from the JTAG header, and you are done. **PLEASE SEND ME THE badboot.bin FILE FROM YOUR TFTP SERVER!** This will allow me to see exactly what got corrupted on your switch.
|
||||
|
||||
**Shutdown Order Summary:**
|
||||
1. Power down the switch (unplug power)
|
||||
2. Power down the BDI2000 (unplug power brick)
|
||||
3. Disconnect the BDI2000 16 pin cable from the JTAG header
|
||||
**Shutdown Order Summary:**
|
||||
1. Power down the switch (unplug power)
|
||||
2. Power down the BDI2000 (unplug power brick)
|
||||
3. Disconnect the BDI2000 16 pin cable from the JTAG header
|
||||
|
||||
Put the switch cover back on. Now that your switch is booting into the bootloader, you can go and follow the [update guide](https://fohdeesha.com/docs/fcx/) to flash a new OS etc to the switch from the bootloader.
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Enter 'help' for a list of built-in commands.
|
|||
|
||||
/ #
|
||||
```
|
||||
**Note:** If your ICX7xxx series switch asks for a root password, it's `wYbRaMWrYIJgg`
|
||||
**Note:** If your ICX7xxx series switch asks for a password, see the note at the bottom of this page
|
||||
|
||||
Press tab twice and it'll show you all possible commands (just typing `help` will not show you all commands), there's a couple hundred, most of the utilities you'd expect including `wget`, `curl`, `vi`, and `ftpput`.
|
||||
|
||||
|
|
|
|||
128
docs/perc.md
128
docs/perc.md
|
|
@ -10,10 +10,10 @@ This guide allows you to crossflash 12th gen Dell Mini Mono & full size cards to
|
|||
* H810 Full Size
|
||||
|
||||
## Thanks
|
||||
[**Jon Sands**](https://fohdeesha.com/)
|
||||
[**fourlynx**](mailto:fourlynx@phoxden.net)
|
||||
**WildOne69**
|
||||
[**Various STH Members**](https://forums.servethehome.com/index.php?threads/perc-h710-mini-to-it-mode.25448/page-3)
|
||||
[**Jon Sands**](https://fohdeesha.com/)
|
||||
[**fourlynx**](mailto:fourlynx@phoxden.net)
|
||||
**WildOne69**
|
||||
[**Various STH Members**](https://forums.servethehome.com/index.php?threads/perc-h710-mini-to-it-mode.25448/page-3)
|
||||
|
||||
## Why
|
||||
|
||||
|
|
@ -30,10 +30,10 @@ Ensure there is only one LSI-based adapter in your system. If there are others b
|
|||
|
||||
Download the ZIP below which contains two ISOs. One is a FreeDOS live image, the other is a Debian live image. Both come prepackaged with all the required tools and files, and they can be booted either via iDRAC virtual media or by burning them to a flash drive via [Rufus](https://rufus.ie/), using `dd`, or your favorite flashing utility - up to you.
|
||||
|
||||
[```Dell Perc Flashing ZIP```](https://fohdeesha.com/data/other/perc/perc-crossflash-v1.8.zip)
|
||||
```Version: v1.8```
|
||||
```ZIP Updated: 02-23-2021```
|
||||
```MD5: 577cef6f3969f04475d50ceb71d8f52d```
|
||||
[```Dell Perc Flashing ZIP```](https://fohdeesha.com/data/other/perc/perc-crossflash-v1.8.zip)
|
||||
```Version: v1.8```
|
||||
```ZIP Updated: 02-23-2021```
|
||||
```MD5: 577cef6f3969f04475d50ceb71d8f52d```
|
||||
|
||||
>Note: If you **know** you have an H310 Mini (**not** an H710), skip all of the below and jump right to the [H310 Mini Guide](https://fohdeesha.com/docs/H310/). Otherwise, continue below.
|
||||
|
||||
|
|
@ -47,32 +47,32 @@ info
|
|||
|
||||
>WARNING: If you are flashing a card in a blade chassis (like an M620 or M820), only use the "for blades" guide for your specific card model below. For example, the **H710 Mini (D1) Blade Guide**. Following any of the "normal" guides on a blade server will brick the PERC
|
||||
|
||||
If it displays an **H310 Mini**, proceed to the [H310 Mini Guide](https://fohdeesha.com/docs/H310/)
|
||||
If it displays an **H710 Mini B0** revision, proceed to the [H710 Mini (B0) Guide](https://fohdeesha.com/docs/H710-B0/)
|
||||
If it displays an **H710 Mini D1** revision, proceed to the [H710 Mini (D1) Guide](https://fohdeesha.com/docs/H710-D1/)
|
||||
If it displays an **H710 Mini D1** revision **and it's in a blade server**, proceed to the [H710 Mini (D1) Blade Guide](https://fohdeesha.com/docs/H710-D1-Blade/)
|
||||
If it displays an **H710P Mini B0** revision, proceed to the [H710P Mini (B0) Guide](https://fohdeesha.com/docs/H710P-B0/)
|
||||
If it displays an **H710P Mini D1** revision, proceed to the [H710P Mini (D1) Guide](https://fohdeesha.com/docs/H710P-D1/)
|
||||
If it displays an **H710 Adapter B0** revision, proceed to the [H710 Full Size (B0) Guide](https://fohdeesha.com/docs/H710-B0-full/)
|
||||
If it displays an **H710 Adapter D1** revision, proceed to the [H710 Full Size (D1) Guide](https://fohdeesha.com/docs/H710-D1-full/)
|
||||
If it displays an **H710P Adapter B0** revision, proceed to the [H710P Full Size (B0) Guide](https://fohdeesha.com/docs/H710P-B0-full/)
|
||||
If it displays an **H710P Adapter D1** revision, proceed to the [H710P Full Size (D1) Guide](https://fohdeesha.com/docs/H710P-D1-full/)
|
||||
If it displays an **H810 Adapter B0** revision, proceed to the [H810 Full Size (B0) Guide](https://fohdeesha.com/docs/H810-B0-full/)
|
||||
If it displays an **H810 Adapter D1** revision, proceed to the [H810 Full Size (D1) Guide](https://fohdeesha.com/docs/H810-D1-full/)
|
||||
If it displays an **H310 Mini**, proceed to the [H310 Mini Guide](https://fohdeesha.com/docs/H310/)
|
||||
If it displays an **H710 Mini B0** revision, proceed to the [H710 Mini (B0) Guide](https://fohdeesha.com/docs/H710-B0/)
|
||||
If it displays an **H710 Mini D1** revision, proceed to the [H710 Mini (D1) Guide](https://fohdeesha.com/docs/H710-D1/)
|
||||
If it displays an **H710 Mini D1** revision **and it's in a blade server**, proceed to the [H710 Mini (D1) Blade Guide](https://fohdeesha.com/docs/H710-D1-Blade/)
|
||||
If it displays an **H710P Mini B0** revision, proceed to the [H710P Mini (B0) Guide](https://fohdeesha.com/docs/H710P-B0/)
|
||||
If it displays an **H710P Mini D1** revision, proceed to the [H710P Mini (D1) Guide](https://fohdeesha.com/docs/H710P-D1/)
|
||||
If it displays an **H710 Adapter B0** revision, proceed to the [H710 Full Size (B0) Guide](https://fohdeesha.com/docs/H710-B0-full/)
|
||||
If it displays an **H710 Adapter D1** revision, proceed to the [H710 Full Size (D1) Guide](https://fohdeesha.com/docs/H710-D1-full/)
|
||||
If it displays an **H710P Adapter B0** revision, proceed to the [H710P Full Size (B0) Guide](https://fohdeesha.com/docs/H710P-B0-full/)
|
||||
If it displays an **H710P Adapter D1** revision, proceed to the [H710P Full Size (D1) Guide](https://fohdeesha.com/docs/H710P-D1-full/)
|
||||
If it displays an **H810 Adapter B0** revision, proceed to the [H810 Full Size (B0) Guide](https://fohdeesha.com/docs/H810-B0-full/)
|
||||
If it displays an **H810 Adapter D1** revision, proceed to the [H810 Full Size (D1) Guide](https://fohdeesha.com/docs/H810-D1-full/)
|
||||
|
||||
If it displays anything that doesn't exactly match the above choices, [contact me](mailto:jon@fohdeesha.com?subject=PERC-Unknown) with a screenshot. If you're impatient and pick the "closest one" instead, you'll brick your card.
|
||||
|
||||
## Extra: Disable ThirdPartyPCIFanResponse
|
||||
|
||||
>Warning: Use this at your own risk. Modifying thermal settings can cause unforeseen circumstances. If you are running your server in a warm environment, it is probably best to leave this alone.
|
||||
>Warning: Use this at your own risk. Modifying thermal settings can cause unforeseen circumstances. If you are running your server in a hot environment, it's probably best to leave this alone
|
||||
|
||||
The LSI firmware is not supported by Dell. This will cause the iDRAC to no longer keep track of the drive temperatures. This is confirmed with the error PCI3018 in the Lifecycle Log and the fans being set to a static speed of about 30%. The fan speed acts as a failsafe to prevent any disks from possibly overheating.
|
||||
iDRAC does not expect to see a PERC card running LSI firmware - this will cause the iDRAC to no longer see the drive temperatures. In some cases, this will cause the error PCI3018 in the Lifecycle Log, and the fans will be set to a static speed of about 30%. The fan speed acts as a failsafe to prevent any disks from possibly overheating.
|
||||
|
||||
To correct this behavior, you can disable the "ThirdPartyPCIFanResponse" feature by using IPMItool or RACADM. IPMItool is built into the live image so this will usually be the easiest option. If you are no longer booted into the live image, use the RACADM option instead to disable via SSH.
|
||||
If you are affected by this and would like the fan behavior to return to normal, you can disable the `ThirdPartyPCIFanResponse` feature by using IPMItool or RACADM. IPMItool is built into the live image so this will usually be the easiest option. If you don't want to use the Linux live ISO, you can use the RACADM option to disable it via SSH.
|
||||
|
||||
### Option 1: Disable ThirdPartyPCIFanResponse using IPMItool via Linux Shell
|
||||
|
||||
IPMItool is built into the live image. Otherwise, you will need to install IPMItool in a Linux environment first.
|
||||
IPMItool is built into the Linux live ISO in this guide. Otherwise, you will need to install IPMItool in a Linux environment first.
|
||||
|
||||
To disable ThirdPartyPCIFanResponse, run the following command in the Linux shell:
|
||||
```
|
||||
|
|
@ -91,7 +91,7 @@ ipmitool –I open raw 0x30 0xce 0 0x16 5 0 0 0 5 0 0 0 0
|
|||
|
||||
### Option 2: Disable ThirdPartyPCIFanResponse using RACADM via SSH
|
||||
|
||||
Connect to port 22 on your iDRAC's IP address using your preferred SSH client.
|
||||
Connect to port 22 on your iDRAC's IP address using your preferred SSH client (you may need to enable SSH in the iDRAC web menu under iDRAC settings > Network > Services tab).
|
||||
|
||||
To disable ThirdPartyPCIFanResponse, run the following command via the SSH client:
|
||||
```
|
||||
|
|
@ -108,62 +108,62 @@ If you need to enable the feature again, run this command via the SSH client:
|
|||
racadm set system.thermalsettings.ThirdPartyPCIFanResponse 1
|
||||
```
|
||||
|
||||
>Note: This information was collected from the Dell White Paper "Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers" which can be referenced here: https://fohdeesha.com/data/other/perc/ThirdPartyPCIFanResponse.pdf .
|
||||
>Note: The above commands were pulled from the following Dell White Paper: [Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers](https://fohdeesha.com/data/other/perc/ThirdPartyPCIFanResponse.pdf)
|
||||
|
||||
## Extra: Revision Info & Part Numbers
|
||||
The main difference between the B0 and D1 revisions is the D1 will link at PCIe 3.0 speeds, instead of PCIe 2.0. This will almost certainly never cause a bottleneck unless you have every SAS port on the card connected to very fast SSDs that all get hammered at the same time. Even then, you're likely to reach the card's processor limitations before the bus bandwidth limit. The difference with the *P* cards (H710P) is more cache (1GB vs 512MB), but this is totally irrelevant when running the card flashed to IT mode as the cache is not used.
|
||||
|
||||
Regardless, since they're the same price used, you may as well grab the D1 revision. Note that many ebay sellers just stick popular part numbers in the listing title, so try to verify in the actual auction images that the label states the correct part number. Note that most sellers omit the leading `0` so you'll get more results doing the same:
|
||||
|
||||
**H710 B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 017MXW
|
||||
**H710 B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 017MXW
|
||||
|
||||
**H710 D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0PX45J
|
||||
**H710 D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0PX45J
|
||||
|
||||
**H710P B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0V9RNC
|
||||
**H710P B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0V9RNC
|
||||
|
||||
**H710P D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 07GCGT
|
||||
**H710P D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 07GCGT
|
||||
|
||||
**H810 B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0HVCWY
|
||||
**H810 B0 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0HVCWY
|
||||
|
||||
**H810 D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0NDD93
|
||||
**H810 D1 Full Size Part Numbers:**
|
||||
- These full size cards are still $$$ for some reason
|
||||
- Unless you already have one just buy an actual LSI card for half the price
|
||||
- 0NDD93
|
||||
|
||||
**H710 B0 Mini Part Numbers:**
|
||||
- 0MCR5X
|
||||
- 0FRH64
|
||||
**H710 B0 Mini Part Numbers:**
|
||||
- 0MCR5X
|
||||
- 0FRH64
|
||||
|
||||
**H710 D1 Mini Part Numbers:**
|
||||
- 05CT6D
|
||||
**H710 D1 Mini Part Numbers:**
|
||||
- 05CT6D
|
||||
|
||||
**H710 D1 Mini For Blades Part Numbers:**
|
||||
- 062P9H
|
||||
**H710 D1 Mini For Blades Part Numbers:**
|
||||
- 062P9H
|
||||
|
||||
**H710P B0 Mini Part Numbers:**
|
||||
- 0TTVVV
|
||||
- 0N3V6G
|
||||
**H710P B0 Mini Part Numbers:**
|
||||
- 0TTVVV
|
||||
- 0N3V6G
|
||||
|
||||
**H710P D1 Mini Part Numbers:**
|
||||
- 0TY8F9
|
||||
**H710P D1 Mini Part Numbers:**
|
||||
- 0TY8F9
|
||||
|
||||
**Unknown:**
|
||||
- 0PK2W9
|
||||
**Unknown:**
|
||||
- 0PK2W9
|
||||
|
||||
### Contributing:
|
||||
The markdown source for these guides is hosted on [**my Github repo.**](https://github.com/Fohdeesha/lab-docu) If you have any suggested changes or additions feel free to submit a pull request.
|
||||
|
|
|
|||
Loading…
Reference in New Issue