diff --git a/README.md b/README.md index 4488afd..a3f3a5d 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,11 @@ # Lab-Docu -Documentation used by [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/) & [FBOM](http://fbom.club/) for various network and server gear +Documentation used by [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/) & [FBOM](http://fbom.club/) for various network and server gear Mostly consists of hard to find Foundry / Brocade / Ruckus switch information and easter eggs -The raw markdown source in this repo is intended to be built using [MkDocs](http://www.mkdocs.org/) - not displayed on GitHub. +The raw markdown source in this repo is intended to be built using [MkDocs](http://www.mkdocs.org/) - not displayed on GitHub. -The built guide is available here: [fohdeesha.com](https://fohdeesha.com/docs/) +The built guide is available here: [fohdeesha.com](https://fohdeesha.com/docs/) Pull requests welcome diff --git a/docs/64nix.md b/docs/64nix.md index d0a0e54..6c9ff63 100644 --- a/docs/64nix.md +++ b/docs/64nix.md @@ -21,7 +21,7 @@ The next IP after this, `2620:57:e000:e::12`, will be given to the server. enable conf t ipv6 route 2620:57:e000:400::/56 2620:57:e000:e::12 -``` +``` The destination is your chosen `2620:57:e000:400::/56` subnet, the next-hop is the server end of the transit subnet, `2620:57:e000:e::12` @@ -39,14 +39,14 @@ iface eth1 inet6 static autoconf 0 ``` -### Assign an entire /56 to a linux server +### Assign an entire /56 to a linux server -Run the below command to assign the entire /56 to the server's loopback interface: -**Note:** this uses Linux's [AnyIP](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab79ad14a2d51e95f0ac3cef7cd116a57089ba82) feature: +Run the below command to assign the entire /56 to the server's loopback interface: +**Note:** this uses Linux's [AnyIP](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab79ad14a2d51e95f0ac3cef7cd116a57089ba82) feature: `ip -6 route add local 2620:57:e000:400::/56 dev lo` -Your server will now respond to any address in the entire /56 - however most applications and daemons will complain when you try to bind them to an address in this block, since they're not *technically* assigned to any real linux interface. To solve this, enable the `net.ipv6.ip_nonlocal_bind` sysctl: +Your server will now respond to any address in the entire /56 - however most applications and daemons will complain when you try to bind them to an address in this block, since they're not *technically* assigned to any real linux interface. To solve this, enable the `net.ipv6.ip_nonlocal_bind` sysctl: `sysctl -w net.ipv6.ip_nonlocal_bind=1` @@ -56,7 +56,7 @@ Applications can now bind to any IP address in the /56. To make this permanent s Add the following line and then save it: -`net.ipv6.ip_nonlocal_bind = 1` +`net.ipv6.ip_nonlocal_bind = 1` The `ip -6 route` command we ran earlier to assign the /56 will also disappear on reboot, to make it persist reboots, add it as a `pre-up` command to our network interfaces file, under your transit subnet interface: @@ -75,7 +75,7 @@ iface eth1 inet6 static ### Finding all the /64s to bind to If your application needs to be bound to each /64, stick our `2620:57:e000:400::/56` subnet into [this calculator](https://subnettingpractice.com/ipv6_subnetting.html), and choose /64s from the dropdown then press calculate: -![calculator](../../data/other/brocade/64nix-1.png) +![calculator](../../data/other/brocade/64nix-1.png) Then simply bind each of your application instances to the first address in each /64 - For instance: diff --git a/docs/H310.md b/docs/H310.md index e3ef975..6509837 100644 --- a/docs/H310.md +++ b/docs/H310.md @@ -2,13 +2,13 @@ Instructions for flashing the H310 Mini Mono. Full credits for this guide go to [fourlynx](mailto:fourlynx@phoxden.net) and his original [H310 Mini guide](https://doku.phoxden.net/pages/viewpage.action?pageId=7208964). As we were working on these H710 guides together and building a convenient live ISO, we figured we might as well add an easy H310 mini script to it. ## Linux Time -Boot into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +Boot into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -26,7 +26,7 @@ H310 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back @@ -58,10 +58,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710-B0-full.md b/docs/H710-B0-full.md index b9916af..f5128e2 100644 --- a/docs/H710-B0-full.md +++ b/docs/H710-B0-full.md @@ -12,7 +12,7 @@ Product Name : PERC H710 Adapter ChipRevision : B0 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ B0-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710-B0.md b/docs/H710-B0.md index c71e29d..9e9fac9 100644 --- a/docs/H710-B0.md +++ b/docs/H710-B0.md @@ -12,7 +12,7 @@ Product Name : PERC H710 Mini ChipRevision : B0 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ B0-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710-D1-Blade.md b/docs/H710-D1-Blade.md index 2b37ed5..36f5ba5 100644 --- a/docs/H710-D1-Blade.md +++ b/docs/H710-D1-Blade.md @@ -12,7 +12,7 @@ Product Name : PERC H710 Mini ChipRevision : D1 SAS Address : xxxx (will differ) ``` -**Note:** The system you are using & flashing should also be a blade model! For instance PERC Minis in an M420, M620, M820 etc. If you're not sure what that means, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +**Note:** The system you are using & flashing should also be a blade model! For instance PERC Minis in an M420, M620, M820 etc. If you're not sure what that means, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. Next, you need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -44,9 +44,9 @@ Now we run the flashing script. Issue the following command to begin the process ``` D1-H710 ``` -It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. +It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back @@ -78,10 +78,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710-D1-full.md b/docs/H710-D1-full.md index 6661bba..25fbd38 100644 --- a/docs/H710-D1-full.md +++ b/docs/H710-D1-full.md @@ -12,7 +12,7 @@ Product Name : PERC H710 Adapter ChipRevision : D1 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ D1-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710-D1.md b/docs/H710-D1.md index 27ebf39..3a65c37 100644 --- a/docs/H710-D1.md +++ b/docs/H710-D1.md @@ -12,7 +12,7 @@ Product Name : PERC H710 Mini ChipRevision : D1 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -44,9 +44,9 @@ Now we run the flashing script. Issue the following command to begin the process ``` D1-H710 ``` -It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. +It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back @@ -78,10 +78,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710P-B0-full.md b/docs/H710P-B0-full.md index 9e1863d..fedb406 100644 --- a/docs/H710P-B0-full.md +++ b/docs/H710P-B0-full.md @@ -12,7 +12,7 @@ Product Name : PERC H710P Adapter ChipRevision : B0 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ B0-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710P-B0.md b/docs/H710P-B0.md index 93fe3b1..ca86574 100644 --- a/docs/H710P-B0.md +++ b/docs/H710P-B0.md @@ -12,7 +12,7 @@ Product Name : PERC H710P Mini ChipRevision : B0 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ B0-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back @@ -79,10 +79,10 @@ info Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710P-D1-full.md b/docs/H710P-D1-full.md index 6ee6693..002fd2c 100644 --- a/docs/H710P-D1-full.md +++ b/docs/H710P-D1-full.md @@ -12,7 +12,7 @@ Product Name : PERC H710P Adapter ChipRevision : D1 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ D1-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H710P-D1.md b/docs/H710P-D1.md index 0cae09b..2c55868 100644 --- a/docs/H710P-D1.md +++ b/docs/H710P-D1.md @@ -12,7 +12,7 @@ Product Name : PERC H710P Mini ChipRevision : D1 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ D1-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back @@ -78,10 +78,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H810-B0-full.md b/docs/H810-B0-full.md index 36d5817..dbd6651 100644 --- a/docs/H810-B0-full.md +++ b/docs/H810-B0-full.md @@ -12,7 +12,7 @@ Product Name : PERC H810 Adapter ChipRevision : B0 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ B0-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/H810-D1-full.md b/docs/H810-D1-full.md index 26ea726..6061d69 100644 --- a/docs/H810-D1-full.md +++ b/docs/H810-D1-full.md @@ -12,7 +12,7 @@ Product Name : PERC H810 Adapter ChipRevision : D1 SAS Address : xxxx (will differ) ``` -If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. +If so, continue on! If not, stop and go back to the [introduction page](https://fohdeesha.com/docs/perc/) and get on the right guide. You also need to note the SAS address of the card from the above output so we can program it back later. Take a screenshot of the console, or otherwise note down the address so you can write it back at the end of the guide. It's not a huge deal if you lose it, but it's easiest to program back the original address instead of generating a new one. @@ -27,13 +27,13 @@ reboot ``` ## Linux Time -You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** +You should now be booted into the Linux ISO from the ZIP. Use the following credentials to login: **user/live** We highly recommend SSH'ing to the live ISO so you can copy/paste commands and not have to use the iDRAC virtual console. To do so, run the following to find the IP of the install: ``` ipinfo ``` -It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. +It should spit out an IP. SSH to it, using the same **user/live** credentials. This is not required and you can continue on using the iDRAC (or physical) console, but it will be slightly more inconvenient. ## Flashing IT Firmware Now, still in Linux, we need to change to the root user: @@ -46,7 +46,7 @@ D1-H710 ``` It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. -**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. +**Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well. ## Programming SAS Address Back Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier: @@ -77,10 +77,10 @@ info Board Assembly : N/A Board Tracer Number : N/A ``` -Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. +Unless you also need to flash boot images for booting off the card, you can now ditch all the live images and reboot back into your normal system, and enjoy your IT mode card. ## Optional: Boot Images ->Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! +>Note: flashing these can add up to 2 minutes to server boot time if you have a lot of drives. Be sure you need them! If you need to boot from drives connected to this adapter, you'll need to flash a boot image to it. Otherwise, skip it. This is what gives you the "press blahblah to enter the LSI boot configuration utility" text when the server boots. To flash the regular BIOS boot image: ``` diff --git a/docs/eeprom.md b/docs/eeprom.md index 486d5d0..7636d8e 100644 --- a/docs/eeprom.md +++ b/docs/eeprom.md @@ -2,22 +2,22 @@ # EEPROM Unlocks -## Information -Before software licensing came around, during the Foundry and early Brocade days, the older FastIron switches used hardware licensing in the form of optional 16kbit EEPROM chips in a socket on the switches mainboard. These were either installed from factory, or you could purchase them and install them yourself. +## Information +Before software licensing came around, during the Foundry and early Brocade days, the older FastIron switches used hardware licensing in the form of optional 16kbit EEPROM chips in a socket on the switches mainboard. These were either installed from factory, or you could purchase them and install them yourself. The EEPROM would contain a magic string of letters and numbers, and when the switch OS saw this it knew to unlock said features. These products are now very old, have not been sold for a decade, and the below license EEPROMs are impossible to buy as the company no longer exists (Foundry is gone). I am providing the strings here to give these old pieces of hardware a little more life. -**Note:** All FastIron devices had two EEPROMs - a soldered in main EEPROM that contained chassis data like MAC address, serial number, manufacture date, etc. Then the second optional EEPROM in a removable socket: this is the EEPROM that contains the magic string. Some devices shipped with a blank EEPROM already in the slot that you can program from the bootloader, others came with none. +**Note:** All FastIron devices had two EEPROMs - a soldered in main EEPROM that contained chassis data like MAC address, serial number, manufacture date, etc. Then the second optional EEPROM in a removable socket: this is the EEPROM that contains the magic string. Some devices shipped with a blank EEPROM already in the slot that you can program from the bootloader, others came with none. ## Programming Information If the switch didn't come with a blank EEPROM already in the socket, you need to purchase one. They need to be `AT24C164` chips, the later revision `24LC16B` will not work. All US vendors I could find are out of these as they are old, [this](https://www.aliexpress.com/item/new-100-24C164-AT24C164-DIP-8/32858414375.html) is the only place I could find to order some. They will take 3 to 4 weeks to arrive, but they work. -For programming the strings into the EEPROM, it's possible to do it from the v7 bootloaders with the `i2cWriteByte` command, but it involves multiple commands. +For programming the strings into the EEPROM, it's possible to do it from the v7 bootloaders with the `i2cWriteByte` command, but it involves multiple commands. -You can also buy a cheap [EEPROM Programmer](https://www.amazon.com/gp/product/B013Q5P3ES) - see the EEPROM Programmer guide at the bottom of this page. +You can also buy a cheap [EEPROM Programmer](https://www.amazon.com/gp/product/B013Q5P3ES) - see the EEPROM Programmer guide at the bottom of this page. -**Note:** These are raw HEX bytes (not ASCII) to be written starting at the beginning of the EEPROM. So your EEPROM programmer/contents should look like this: +**Note:** These are raw HEX bytes (not ASCII) to be written starting at the beginning of the EEPROM. So your EEPROM programmer/contents should look like this: ![eeprom](https://fohdeesha.com/data/other/eepromguide/eeprom.png) @@ -26,7 +26,7 @@ You can also buy a cheap [EEPROM Programmer](https://www.amazon.com/gp/product/B ## EEPROM Unlock Strings ### FCX Advanced Routing -The Brocade FCX was the last switch to use EEPROM based licensing - in fact, in the middle of its sales life, they added software based licensing. This means the FCX can be unlocked via an EEPROM, or via software license. The nice thing is every FCX seems to have come with a blank EEPROM in the socket already, so if you own one you can reboot into the bootloader and run the below to fully unlock it. +The Brocade FCX was the last switch to use EEPROM based licensing - in fact, in the middle of its sales life, they added software based licensing. This means the FCX can be unlocked via an EEPROM, or via software license. The nice thing is every FCX seems to have come with a blank EEPROM in the socket already, so if you own one you can reboot into the bootloader and run the below to fully unlock it. **Note:** Make sure you are running the latest bootloader, `grz10100` - earlier bootloaders had different I2C addresses and the below command would not work. @@ -99,24 +99,24 @@ reset ## Using the CH341A EEPROM Writer -If you want to burn blank EEPROM chips yourself, you can pick up a $10 [EEPROM Programmer](https://www.amazon.com/gp/product/B013Q5P3ES). This will be a brief guide on using it under Windows. +If you want to burn blank EEPROM chips yourself, you can pick up a $10 [EEPROM Programmer](https://www.amazon.com/gp/product/B013Q5P3ES). This will be a brief guide on using it under Windows. -First download [this ZIP](https://fohdeesha.com/data/other/EEPROM.zip) which contains the driver, software, and EEPROM dumps. Extract the ZIP to an easy to find location like your desktop. +First download [this ZIP](https://fohdeesha.com/data/other/EEPROM.zip) which contains the driver, software, and EEPROM dumps. Extract the ZIP to an easy to find location like your desktop. -Put your EEPROM chip into the programmer socket - it should have a little picture silkscreened on the PCB showing you which direction to insert it. Once inserted, plug in the EEPROM Writer to a USB port - it will show up as an unrecognized device, you need to install the driver. Open up Device Manager and find it - it will be an Unknown Device with a yellow icon - then right click and hit update driver: +Put your EEPROM chip into the programmer socket - it should have a little picture silkscreened on the PCB showing you which direction to insert it. Once inserted, plug in the EEPROM Writer to a USB port - it will show up as an unrecognized device, you need to install the driver. Open up Device Manager and find it - it will be an Unknown Device with a yellow icon - then right click and hit update driver: ![eeprom](https://fohdeesha.com/data/other/eepromguide/eeprom%20install1.png) -In the following prompt, select **Browse my computer for driver software**: +In the following prompt, select **Browse my computer for driver software**: -![eeprom](https://fohdeesha.com/data/other/eepromguide/eeprom%20install2.png) +![eeprom](https://fohdeesha.com/data/other/eepromguide/eeprom%20install2.png) -In the following prompt, browse to the folder you extracted from the ZIP, then select the Driver folder within it, then click OK/next: +In the following prompt, browse to the folder you extracted from the ZIP, then select the Driver folder within it, then click OK/next: ![eeprom](https://fohdeesha.com/data/other/eepromguide/eeprom%20install3.png) -It should successfully install the driver, and you're good to go. Now launch the EEPROM programming software - in the **CH341A Programmer 1.29** folder, double click the executable named **Run Me**, and it will launch the software. Now just follow the instructions in the image below to program the EEPROM. When done, just close the program and remove the EEPROM writer from your PC. +It should successfully install the driver, and you're good to go. Now launch the EEPROM programming software - in the **CH341A Programmer 1.29** folder, double click the executable named **Run Me**, and it will launch the software. Now just follow the instructions in the image below to program the EEPROM. When done, just close the program and remove the EEPROM writer from your PC. ![eeprom](https://fohdeesha.com/data/other/eepromguide/eepromguide.png) diff --git a/docs/extract.md b/docs/extract.md index 87ff095..1dc151b 100644 --- a/docs/extract.md +++ b/docs/extract.md @@ -2,10 +2,10 @@ **Note:** This is intended for those who are curious, or who have licenses you legitimately own installed on a switch, but have lost the original license files. This is for the ICX6xxx series and is unnecessary on the ICX7xxx series with honor-based licensing (no license files to lose). -When licenses are purchased and used to unlock a switch, the license string is stored on the switch. To extract licenses from a switch back to a license file, follow the below. +When licenses are purchased and used to unlock a switch, the license string is stored on the switch. To extract licenses from a switch back to a license file, follow the below. ## For ARM Models -Thankfully on ARM architecture Brocade devices (ICX6430, ICX6450, any ICX7xxx or newer), you can extract any applied licenses without special JTAG hardware. Just use the **Accessing Linux** guide to boot into linux. +Thankfully on ARM architecture Brocade devices (ICX6430, ICX6450, any ICX7xxx or newer), you can extract any applied licenses without special JTAG hardware. Just use the **Accessing Linux** guide to boot into linux. Now that you're booted into a linux shell: There is a `system` file in the `/fast_iron/sys/` directory which contains the license strings if the switch has been licensed: ``` @@ -31,7 +31,7 @@ tftp -p -l system 192.168.1.8 ``` >Note: if you are running your TFTP server on linux, you need to create an empty file with this filename (system) in your tftp root directory, and chmod it with 777 so the switch can write to said empty file. Otherwise the switch will give a "file not found" error. -Open the downloaded file on your desktop with something like NotePad++, and it should look like [This](https://fohdeesha.com/data/other/system.png). License strings start with `*B ` and are followed by a string (note, there must be a space after `*B`), and the license string ends where the `NUL` characters begin. +Open the downloaded file on your desktop with something like NotePad++, and it should look like [This](https://fohdeesha.com/data/other/system.png). License strings start with `*B ` and are followed by a string (note, there must be a space after `*B`), and the license string ends where the `NUL` characters begin. So applying this knowledge, we can extract the following two licenses from that system file in the screenshot. You'll need to remove the newline after the `*B`, so the `*B` and then the string are on the same line. Make sure to leave a space between `*B` and the string as well: @@ -63,11 +63,11 @@ Now you just need to stick those strings in an XML file, like `newlicense.xml` - ``` -Now you have a backup of your legitimate license file just as you would receive from Brocade. +Now you have a backup of your legitimate license file just as you would receive from Brocade. ## For PowerPC Models -On PowerPC models (FCX, ICX6610) it is more complicated, as they do not run linux. These units store the license strings directly on raw system flash in random locations. To extract these strings, you pretty much have to open the switch, attach a JTAG unit (such as a BDI2000) to the JTAG header, and dump the entire switch flash to a file, then open it in a hex editor. +On PowerPC models (FCX, ICX6610) it is more complicated, as they do not run linux. These units store the license strings directly on raw system flash in random locations. To extract these strings, you pretty much have to open the switch, attach a JTAG unit (such as a BDI2000) to the JTAG header, and dump the entire switch flash to a file, then open it in a hex editor. Once you have a file containing a dump of the entire onboard flash, and have opened it in a hex editor, you search it for the characters `*B` - you will eventually come across the license string(s) like so: @@ -77,15 +77,15 @@ There's our license string, starting with `*B` as always. So, extracted, it look ``` *B 8:n,UyAs6b9TXB3sowQ81lk,oLxLdkH:L:SIhdOko0lOEoIeSMl4dspO898E::LlSdEutafAA,bvuzxlr2so2Uks92ObyrkMyI5:rAd25Edr29ICgkqd3a,iv:bukvbO:,eO ``` -Interestingly, on PPC platforms, when a user deletes licenses from the switch, it does not remove these strings - it just moves them to another part of flash. I have purchased ICX6610's on ebay where the previous owner deleted all licenses, so it boots up unlicensed. However after dumping the flash via JTAG, I found perfectly legitimate license strings still in flash that I was able to extract. +Interestingly, on PPC platforms, when a user deletes licenses from the switch, it does not remove these strings - it just moves them to another part of flash. I have purchased ICX6610's on ebay where the previous owner deleted all licenses, so it boots up unlicensed. However after dumping the flash via JTAG, I found perfectly legitimate license strings still in flash that I was able to extract. #### PowerPC Models, Desperate Edition -If you have a non-linux based switch (eg ICX6610) and you REALLY want to extract the licenses, but have no JTAG unit, there's still a way to extract them. You need to connect to the switch over serial, and get into the bootloader. Use a program like putty, and configure it to log the serial session (in Putty, Session > Logging > select a filename/location and choose the "printable output" option). +If you have a non-linux based switch (eg ICX6610) and you REALLY want to extract the licenses, but have no JTAG unit, there's still a way to extract them. You need to connect to the switch over serial, and get into the bootloader. Use a program like putty, and configure it to log the serial session (in Putty, Session > Logging > select a filename/location and choose the "printable output" option). Now run the following in the bootloader: ``` -dd f4000000 8388608 +dd f4000000 8388608 ``` -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. +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. \ No newline at end of file diff --git a/docs/fcx.md b/docs/fcx.md index 1a6ffd3..b879be6 100644 --- a/docs/fcx.md +++ b/docs/fcx.md @@ -3,15 +3,15 @@ **Note:** This page is for the FCX & ICX6610. If you have a different model, choose it from the lefthand menu. ## Updating The Software -Download the ZIP below, which contains the firmware files and documentation you'll need. +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). + +**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). You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. @@ -28,7 +28,7 @@ Now we can update the bootloader. Replace the IP with the IP of your tftp server copy tftp flash 192.168.1.49 grz10100.bin boot ``` -After a few seconds it should finish, then we can flash the main OS. Replace the IP with the IP of your tftp server, and change the filename to match if necessary: +After a few seconds it should finish, then we can flash the main OS. Replace the IP with the IP of your tftp server, and change the filename to match if necessary: ``` copy tftp flash 192.168.1.49 FCXR08030t.bin primary @@ -44,7 +44,7 @@ reset #only follow this section if factory set-default did not work reset #hit b a bunch so it drops into the bootloader again -#now it's booted the latest bootloader, so the command will work: +#now it's booted the latest bootloader, so the command will work: factory set-default reset #let it fully boot like normal and move to the next section @@ -63,7 +63,7 @@ Now that it's booted into the full OS you may get ***TFTP timed out*** errors in ``` show version ``` -Towards the top of the output, it should say ```SW: Version XX.X.XXX``` - it should be the v8 version you flashed. +Towards the top of the output, it should say ```SW: Version XX.X.XXX``` - it should be the v8 version you flashed. Now to make any changes we must enter the enable level: ``` @@ -134,7 +134,7 @@ ip ssh permit-empty-passwd yes ``` ## If Access Protection IS Required (or WEB-UI Access) -If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. +If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. To secure the switch, we need to create an account - "root" can be any username string you wish: ``` @@ -146,7 +146,7 @@ aaa authentication login default local aaa authentication enable default local aaa authentication web default local ``` -If you wanted to use the WEB UI, you can now log into it using the credentials you created above. +If you wanted to use the WEB UI, you can now log into it using the credentials you created above. You should enable authentication for telnet access as well: ``` @@ -164,7 +164,7 @@ If you have followed the above to set up authentication, and also wish to disabl ip ssh key-authentication yes ip ssh password-authentication no ``` -Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. +Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. Copy the public key file to your TFTP server. Then use the following command to import it into your switch: ``` @@ -177,9 +177,9 @@ Whenever you make changes (like above) they take effect immediately, however the ``` write memory ``` -Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. +Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. -Some more useful general commands: +Some more useful general commands: Show chassis information like fan and temperature status: ``` @@ -218,11 +218,11 @@ no hostname beefbox ``` ## Noise Info (ICX6610) -The ICX66610 power supply bricks came in 3 revisions: A, B, and C. These will have an affect on how loud the switch is. Generally with an A revision PSU anywhere, even combined with a B or C revision in the other PSU slot, the PSU fans will run louder. +The ICX66610 power supply bricks came in 3 revisions: A, B, and C. These will have an affect on how loud the switch is. Generally with an A revision PSU anywhere, even combined with a B or C revision in the other PSU slot, the PSU fans will run louder. -The switch will be much quieter if you can find and run B and/or C revision bricks. There's no difference noise wise between B and C. Most sellers do not list the revision so you have to check the ebay pictures [for the revision marking.](https://fohdeesha.com/data/other/brocade/psu-rev.jpg) +The switch will be much quieter if you can find and run B and/or C revision bricks. There's no difference noise wise between B and C. Most sellers do not list the revision so you have to check the ebay pictures [for the revision marking.](https://fohdeesha.com/data/other/brocade/psu-rev.jpg) -Also, it seems the PSU and fan tray position also affect fan speed. If you are running 1 PSU and fan tray, position them in the furthest left slots, when looking at the switch from the rear. If you have 2 PSUs and 1 fan tray, position the fan tray in the furthest left fan tray slot when looking at the rear of the switch. +Also, it seems the PSU and fan tray position also affect fan speed. If you are running 1 PSU and fan tray, position them in the furthest left slots, when looking at the switch from the rear. If you have 2 PSUs and 1 fan tray, position the fan tray in the furthest left fan tray slot when looking at the rear of the switch. ## Tips @@ -269,7 +269,7 @@ write memory ``` ## SFP/Optics Information -Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. +Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. So if you want to see information like this : @@ -284,10 +284,10 @@ You'll need to pick up some official Brocade or Foundry optics on ebay, or buy s ### Thanks: -[**Fohdeesha**](https://fohdeesha.com/) +[**Fohdeesha**](https://fohdeesha.com/) ### 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. +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. -```Documentation version:``` [ v2.1 (08-14-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.1 (08-14-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/firmware.md b/docs/firmware.md index f83e76b..5c96192 100644 --- a/docs/firmware.md +++ b/docs/firmware.md @@ -62,7 +62,7 @@ Created: Fri Jun 7 00:19:54 2019 -----trimmed----- ``` -Choose a part to extract to a separate file, putting the image number after the `-p` argument. +Choose a part to extract to a separate file, putting the image number after the `-p` argument. **Note:** The `-T` argument must always be set to `-T flat_dt`, even if you are extracting a different image type, only change the `-p` number: ``` @@ -72,7 +72,7 @@ The above example extracts the ramdisk from the above firmware file, which is th ![7zip](https://fohdeesha.com/data/other/7zip.png) -**Note:** Notice `FastIron.xz` - this is the FastIron binary that gets uncompressed and ran after Linux boots, and this is what provides the FastIron interface you're used to. +**Note:** Notice `FastIron.xz` - this is the FastIron binary that gets uncompressed and ran after Linux boots, and this is what provides the FastIron interface you're used to. ## Packaging Modifications With the appropriate tools (such as `mkimage`) you can modify the filesystem/ramdisk, kernel, etc after extraction, and repackage them for flashing back to the switch. You will most likely need to update the checksum for the new FIT package in the brocade metadata. More info on packaging FIT images [here.](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842374/U-Boot+Images) diff --git a/docs/hidden.md b/docs/hidden.md index d008aaf..5dd3691 100644 --- a/docs/hidden.md +++ b/docs/hidden.md @@ -1,5 +1,5 @@ # Hidden Brocade Dev Stuff -This is a collection of hidden tools, modes, and commands buried inside Brocade FastIron products. +This is a collection of hidden tools, modes, and commands buried inside Brocade FastIron products. ## Hidden Commands @@ -24,7 +24,7 @@ FCX3(config)#dm cpld-reg-dump Dump the CPLD register --More-- ``` -There's hundreds of options. These are low level debug commands, so if you don't know what they do you can easily break your switch. +There's hundreds of options. These are low level debug commands, so if you don't know what they do you can easily break your switch. **Note:** There's around ~700 commands that are completely hidden, they will not even show up using tab autocomplete like the above `dm` commands do. [Click here](https://fohdeesha.com/data/other/brocade/FastIron-Hidden.txt) for a full list of these commands. Many of these might delete your config, your licenses, lock the switch up, etc. @@ -55,7 +55,7 @@ You'll note the options are nearly identical to what's available in the bootload ## Hidden Bootloader Modes -All the newer switches that run linux (ICX6450, ICX6650, ICX7xxx) use u-boot as the bootloader. However it runs in a very locked down mode with only a few commands available. Thankfully after contacting Arris (who own Ruckus, who now owns Brocade), they published their u-boot [source code](https://sourceforge.net/arris/wiki/Projects/). +All the newer switches that run linux (ICX6450, ICX6650, ICX7xxx) use u-boot as the bootloader. However it runs in a very locked down mode with only a few commands available. Thankfully after contacting Arris (who own Ruckus, who now owns Brocade), they published their u-boot [source code](https://sourceforge.net/arris/wiki/Projects/). From analyzing their u-boot source, we are able to find some hidden routines that will force the switch to boot into fully unlocked u-boot. To do so, run the following in the bootloader: diff --git a/docs/icx64xx.md b/docs/icx64xx.md index 6d92733..07bc195 100644 --- a/docs/icx64xx.md +++ b/docs/icx64xx.md @@ -1,33 +1,33 @@ # Setting up Brocade ICX6450 -## Preparation -Download the ZIP below, which contains the firmware files and documentation you'll need. +## 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). -You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. +You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. -Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX64XX-boot>>` . If you missed the prompt and it boots the OS instead, pull power and try again. +Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX64XX-boot>>` . If you missed the prompt and it boots the OS instead, pull power and try again. Now at the boot prompt, we tell the switch to clear all current configs and old keys, so it boots into a fresh state: ``` factory set-default ``` -To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. +To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. Now just tell the switch to reboot: ``` reset ``` -It will boot into the full OS and you can continue to the next section. +It will boot into the full OS and you can continue to the next section. **Note:** If you get an error stating `factory set-default` is not a valid command, this means your switch has a very old bootloader. To clear the existing passworded config in this case, do the following: ``` @@ -35,8 +35,8 @@ It will boot into the full OS and you can continue to the next section. no password boot #it will boot the OS. Once booted: -enable -erase startup-config +enable +erase startup-config reload #it will boot fresh with a clear config, then you can move to the next section ``` @@ -97,11 +97,11 @@ write mem Now that the switch has an IP address, we can TFTP in the new images, then reload: ``` exit -copy tftp flash 192.168.1.8 kxz10105.bin bootrom +copy tftp flash 192.168.1.8 kxz10105.bin bootrom copy tftp flash 192.168.1.8 ICX64R08030t.bin primary reload ``` ->Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. +>Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. The switch will reload, loading the new software. Continue on to the **Configuration Details** section below. @@ -150,7 +150,7 @@ ip ssh permit-empty-passwd yes ``` ## If Access Protection IS Required (or WEB-UI Access) -If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. +If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. To secure the switch, we need to create an account - "root" can be any username string you wish: ``` @@ -162,7 +162,7 @@ aaa authentication login default local aaa authentication enable default local aaa authentication web default local ``` -If you wanted to use the WEB UI, you can now log into it using the credentials you created above. +If you wanted to use the WEB UI, you can now log into it using the credentials you created above. You should enable authentication for telnet access as well: ``` @@ -180,7 +180,7 @@ If you have followed the above to set up authentication, and also wish to disabl ip ssh key-authentication yes ip ssh password-authentication no ``` -Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. +Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. Copy the public key file to your TFTP server. Then use the following command to import it into your switch: ``` @@ -193,9 +193,9 @@ Whenever you make changes (like above) they take effect immediately, however the ``` write memory ``` -Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. +Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. -Some more useful general commands: +Some more useful general commands: Show chassis information like fan and temperature status: ``` @@ -277,7 +277,7 @@ write memory ``` ## SFP/Optics Information -Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. +Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. So if you want to see information like this : @@ -288,13 +288,13 @@ telnet@Route2(config)#sh optic 5 5 32.7460 C -002.6688 dBm -002.8091 dBm 5.472 mA Normal Normal Normal Normal ``` -You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. +You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. ### Thanks: -[**Fohdeesha**](https://fohdeesha.com/) +[**Fohdeesha**](https://fohdeesha.com/) ### 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. +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. -```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/icx6650.md b/docs/icx6650.md index 0543091..5731603 100644 --- a/docs/icx6650.md +++ b/docs/icx6650.md @@ -1,33 +1,33 @@ # Setting up Brocade ICX6650 -## Preparation -Download the ZIP below, which contains the firmware files and documentation you'll need. +## 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. +**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. -You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. +You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. -Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX6650-boot>>` . If you missed the prompt and it boots the OS instead, pull power and try again. +Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX6650-boot>>` . If you missed the prompt and it boots the OS instead, pull power and try again. Now at the boot prompt, we tell the switch to clear all current configs and old keys, so it boots into a fresh state: ``` factory set-default ``` -To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. +To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. Now just tell the switch to reboot: ``` reset ``` -It will boot into the full OS and you can continue to the next section. +It will boot into the full OS and you can continue to the next section. **Note:** If you get an error stating `factory set-default` is not a valid command, this means your switch has a very old bootloader. To clear the existing passworded config in this case, do the following: ``` @@ -35,8 +35,8 @@ It will boot into the full OS and you can continue to the next section. no password boot #it will boot the OS. Once booted: -enable -erase startup-config +enable +erase startup-config reload #it will boot fresh with a clear config, then you can move to the next section ``` @@ -83,7 +83,7 @@ ip addr 192.168.1.55/24 Now that the switch has an IP address, we can TFTP in the new images, then reload: ``` exit -copy tftp flash 192.168.1.8 fxz10101.bin bootrom +copy tftp flash 192.168.1.8 fxz10101.bin bootrom copy tftp flash 192.168.1.8 ICXR08030t.bin primary reload ``` @@ -92,7 +92,7 @@ The switch will reload, loading the new software. Continue on to the **Configura ## Configuration Details -Your switch should now be freshly booted with the latest layer 3 firmware image and bootloader. You will note we did not save our previous management interface configuration before rebooting, so it is now gone. If you plan on using the management port for access in production, just repeat those commands from the previous section to re-assign an IP to the dedicated management port. +Your switch should now be freshly booted with the latest layer 3 firmware image and bootloader. You will note we did not save our previous management interface configuration before rebooting, so it is now gone. If you plan on using the management port for access in production, just repeat those commands from the previous section to re-assign an IP to the dedicated management port. However if you would like to assign an in-band IP address to the switch so you can access it from any of the regular ports, do the following. By default, all ports are in VLAN 1, so it will behave like a typical switch. First we need to give VLAN 1 its own virtual interface: ``` @@ -129,7 +129,7 @@ ip ssh permit-empty-passwd yes ``` ## If Access Protection IS Required (or WEB-UI Access) -If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. +If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. To secure the switch, we need to create an account - "root" can be any username string you wish: ``` @@ -141,7 +141,7 @@ aaa authentication login default local aaa authentication enable default local aaa authentication web default local ``` -If you wanted to use the WEB UI, you can now log into it using the credentials you created above. +If you wanted to use the WEB UI, you can now log into it using the credentials you created above. You should enable authentication for telnet access as well: ``` @@ -159,7 +159,7 @@ If you have followed the above to set up authentication, and also wish to disabl ip ssh key-authentication yes ip ssh password-authentication no ``` -Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. +Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. Copy the public key file to your TFTP server. Then use the following command to import it into your switch: ``` @@ -172,9 +172,9 @@ Whenever you make changes (like above) they take effect immediately, however the ``` write memory ``` -Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. +Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. -Some more useful general commands: +Some more useful general commands: Show chassis information like fan and temperature status: ``` @@ -256,7 +256,7 @@ write memory ``` ## SFP/Optics Information -Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. +Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However optical monitoring information is disabled unless it sees Brocade or Foundry optics. So if you want to see information like this : @@ -267,13 +267,13 @@ telnet@Route2(config)#sh optic 5 5 32.7460 C -002.6688 dBm -002.8091 dBm 5.472 mA Normal Normal Normal Normal ``` -You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. +You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. ### Thanks: -[**Fohdeesha**](https://fohdeesha.com/) +[**Fohdeesha**](https://fohdeesha.com/) ### 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. +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. -```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/icx7150.md b/docs/icx7150.md index 4528aa0..863fb4b 100644 --- a/docs/icx7150.md +++ b/docs/icx7150.md @@ -4,36 +4,36 @@ # Setting up Brocade ICX7150 -## Preparation -Download the ZIP below, which contains the firmware files and documentation you'll need. +## 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). +**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). -**Note:** Aside from the usual RJ45 serial port, the ICX7150 also has a USB-C port. On this port, it has a built in USB to serial adapter, so you can plug the USB-C port directly into your PC, and it will then show up as a serial port. You will need to install the serial adapter driver from the `USB-C Serial Driver` folder. +**Note:** Aside from the usual RJ45 serial port, the ICX7150 also has a USB-C port. On this port, it has a built in USB to serial adapter, so you can plug the USB-C port directly into your PC, and it will then show up as a serial port. You will need to install the serial adapter driver from the `USB-C Serial Driver` folder. -You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. +You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](http://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. -Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX7150-Boot>` . If you missed the prompt and it boots the OS instead, pull power and try again. +Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX7150-Boot>` . If you missed the prompt and it boots the OS instead, pull power and try again. Now at the boot prompt, we tell the switch to clear all current configs and old keys, so it boots into a fresh state: ``` factory set-default ``` -To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. +To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. Now just tell the switch to reboot: ``` reset ``` -It will boot into the full OS and you can continue to the next section. +It will boot into the full OS and you can continue to the next section. ## Initial Configuration & update @@ -84,11 +84,11 @@ write mem Now that the switch has an IP address, we can TFTP in the new images, then reload: ``` exit -copy tftp flash 192.168.1.8 mnz10114.bin bootrom +copy tftp flash 192.168.1.8 mnz10114.bin bootrom copy tftp flash 192.168.1.8 SPR08080e.bin primary reload ``` ->Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. +>Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. The switch will reload, loading the new software. Continue on to the **Configuration Details** section below. @@ -135,7 +135,7 @@ ip ssh permit-empty-passwd yes ``` ## If Access Protection IS Required (or WEB-UI Access) -If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. +If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. To secure the switch, we need to create an account - "root" can be any username string you wish: ``` @@ -147,7 +147,7 @@ aaa authentication login default local aaa authentication enable default local aaa authentication web default local ``` -If you wanted to use the WEB UI, you can now log into it using the credentials you created above. +If you wanted to use the WEB UI, you can now log into it using the credentials you created above. You should enable authentication for telnet access as well: ``` @@ -165,7 +165,7 @@ If you have followed the above to set up authentication, and also wish to disabl ip ssh key-authentication yes ip ssh password-authentication no ``` -Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. +Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. Copy the public key file to your TFTP server. Then use the following command to import it into your switch: ``` @@ -190,16 +190,16 @@ reload The switch will reload, and the 10gbE ports and everything else will now be functional. ## Saving & Conclusions -Whenever you make changes (like above) they take effect immediately, however they are not saved to onboard flash. So if you reboot the switch, they will be lost. To permanently save them to onboard flash, use the `write memory` command. To do so, you must be at the `enable` level or higher. +Whenever you make changes (like above) they take effect immediately, however they are not saved to onboard flash. So if you reboot the switch, they will be lost. To permanently save them to onboard flash, use the `write memory` command. To do so, you must be at the `enable` level or higher. **Note:** Since you did a `write memory` in the previous section before reloading the switch, there are no changes to save. But just for practice: ``` enable write memory ``` -Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. +Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. -Some more useful general commands: +Some more useful general commands: Show chassis information like fan and temperature status: ``` @@ -281,7 +281,7 @@ write memory ``` ## SFP/Optics Information -Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However by default, optical monitoring information is disabled unless it sees Brocade or Foundry optics. +Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However by default, optical monitoring information is disabled unless it sees Brocade or Foundry optics. So if you want to see information like this : @@ -292,7 +292,7 @@ telnet@Route2(config)#sh optic 5 5 32.7460 C -002.6688 dBm -002.8091 dBm 5.472 mA Normal Normal Normal Normal ``` -You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. +You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. **Note:** Starting in v8080 firmware, Ruckus added a command that enables optical monitoring details (like the above example) for non-brocade branded optics. It's not guaranteed to work with all optics, but should with most that conform to SFF-8472. Run the following to enable this: @@ -305,10 +305,10 @@ write mem ``` ### Thanks: -[**Fohdeesha**](https://fohdeesha.com/) +[**Fohdeesha**](https://fohdeesha.com/) ### 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. +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. -```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/icx7250.md b/docs/icx7250.md index 2f6c5a1..918f7da 100644 --- a/docs/icx7250.md +++ b/docs/icx7250.md @@ -1,33 +1,33 @@ # Setting up Brocade ICX7250 & ICX7450 -## 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. +## 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). -You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](https://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. +You need to set up a temporary TFTP server - I recommend [Tftpd32 Portable Edition](https://www.tftpd64.com/tftpd32_download.html) if you're on Windows and don't want to install anything. Point the server to an empty folder to serve files from. From the ZIP, copy the bootloader from the ```Boot``` folder into your tftp server directory. Then, from the ```Images``` folder, copy over the OS image to the same place. If you have a PoE model, copy over the PoE firmware from the `PoE Firmware` folder to your TFTP directory as well. -Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX7250-Boot>` . If you missed the prompt and it boots the OS instead, pull power and try again. +Power on the switch while watching your serial terminal - start smashing the `b` key until you're dropped into the bootloader prompt, which looks like `ICX7250-Boot>` . If you missed the prompt and it boots the OS instead, pull power and try again. Now at the boot prompt, we tell the switch to clear all current configs and old keys, so it boots into a fresh state: ``` factory set-default ``` -To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. +To confirm this action, you must send CAPITAL `Y` - sending a lowercase `y` will just make it abort. Now just tell the switch to reboot: ``` reset ``` -It will boot into the full OS and you can continue to the next section. +It will boot into the full OS and you can continue to the next section. ## Initial Configuration & update @@ -78,11 +78,11 @@ write mem Now that the switch has an IP address, we can TFTP in the new images, then reload: ``` exit -copy tftp flash 192.168.1.8 spz10114.bin bootrom +copy tftp flash 192.168.1.8 spz10114.bin bootrom copy tftp flash 192.168.1.8 SPR08080e.bin primary reload ``` ->Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. +>Note: if you skipped to this section because your switch had layer 2 firmware on it and a note in the previous section instructed you to, go back above and go through the whole **Initial Configuration & update** section once the switch finishes rebooting. The switch will reload, loading the new software. Continue on to the **Configuration Details** section below. @@ -102,7 +102,7 @@ crypto key generate rsa ## Update PoE Firmware -If your switch is the PoE model, you need to update the PoE controller firmware. If it's a non-PoE model, skip this step. Assuming you completed the previous section and the switch now has in-band network access, just do the following: +If your switch is the PoE model, you need to update the PoE controller firmware. If it's a non-PoE model, skip this step. Assuming you completed the previous section and the switch now has in-band network access, just do the following: ``` exit inline power install-firmware stack-unit 1 tftp 192.168.1.8 icx7xxx_poe_02.1.1.b002.fw @@ -129,7 +129,7 @@ ip ssh permit-empty-passwd yes ``` ## If Access Protection IS Required (or WEB-UI Access) -If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. +If you do want to secure access to the switch, or use the (limited) web UI, follow this section. If not, skip it. To secure the switch, we need to create an account - "root" can be any username string you wish: ``` @@ -141,7 +141,7 @@ aaa authentication login default local aaa authentication enable default local aaa authentication web default local ``` -If you wanted to use the WEB UI, you can now log into it using the credentials you created above. +If you wanted to use the WEB UI, you can now log into it using the credentials you created above. You should enable authentication for telnet access as well: ``` @@ -159,7 +159,7 @@ If you have followed the above to set up authentication, and also wish to disabl ip ssh key-authentication yes ip ssh password-authentication no ``` -Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. +Now we have to generate our key pair with [puttygen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on windows or ```ssh-keygen -t rsa``` on linux. The default settings of RSA @ 2048 bits works without issue. Generate the pair and save out both the public and private key. Copy the public key file to your TFTP server. Then use the following command to import it into your switch: ``` @@ -198,16 +198,16 @@ The switch will reload, then the new features will now be fully functional. ## Saving & Conclusions -Whenever you make changes (like above) they take effect immediately, however they are not saved to onboard flash. So if you reboot the switch, they will be lost. To permanently save them to onboard flash, use the `write memory` command. To do so, you must be at the `enable` level or higher. +Whenever you make changes (like above) they take effect immediately, however they are not saved to onboard flash. So if you reboot the switch, they will be lost. To permanently save them to onboard flash, use the `write memory` command. To do so, you must be at the `enable` level or higher. **Note:** Since you did a `write memory` in the previous section before reloading the switch, there are no changes to save. But just for practice: ``` enable write memory ``` -Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. +Your switch now has a basic configuration, as well as an IP address you can telnet or SSH to for further configuration. -Some more useful general commands: +Some more useful general commands: Show chassis information like fan and temperature status: ``` @@ -289,7 +289,7 @@ write memory ``` ## SFP/Optics Information -Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However by default, optical monitoring information is disabled unless it sees Brocade or Foundry optics. +Brocade does not restrict the use of optics by manufacturer, they'll take anything given it's the right protocol. However by default, optical monitoring information is disabled unless it sees Brocade or Foundry optics. So if you want to see information like this : @@ -300,7 +300,7 @@ telnet@Route2(config)#sh optic 5 5 32.7460 C -002.6688 dBm -002.8091 dBm 5.472 mA Normal Normal Normal Normal ``` -You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. +You'll need to pick up some official Brocade or Foundry optics on ebay, or buy some flashed optics from FiberStore. **Note:** Starting in v8080 firmware, Ruckus added a command that enables optical monitoring details (like the above example) for non-brocade branded optics. It's not guaranteed to work with all optics, but should with most that conform to SFF-8472. Run the following to enable this: @@ -313,10 +313,10 @@ write mem ``` ### Thanks: -[**Fohdeesha**](https://fohdeesha.com/) +[**Fohdeesha**](https://fohdeesha.com/) ### 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. +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. -```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.0 (01-03-2020)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/index.md b/docs/index.md index af185e3..b064430 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,5 +1,5 @@ # 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 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. Other documentation I have written or contributed to: diff --git a/docs/jtag.md b/docs/jtag.md index 7a33f2f..a45c214 100644 --- a/docs/jtag.md +++ b/docs/jtag.md @@ -1,23 +1,23 @@ # PowerPC JTAG Recovery (LB6M) -This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (LB6M) using a BDI2000. +This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (LB6M) using a BDI2000. ## Preparation Start by downloading [this ZIP](https://fohdeesha.com/data/other/jtag-recovery.zip). Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at the address you specified before the unit was shipped - make sure said TFTP server is running with above files before powering the BDI2000. -**Note:** If you are attempting this with your own BDI2000 and need the appropriate MPC85xx BDI firmware, contact me via [GitHub](https://github.com/Fohdeesha) or [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/). +**Note:** If you are attempting this with your own BDI2000 and need the appropriate MPC85xx BDI firmware, contact me via [GitHub](https://github.com/Fohdeesha) or [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/). If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary. ## Connections -If you are outside the US, please plug the power brick into the wall first WITHOUT CONNECTING IT TO THE BDI2000! This is to test the power adapter, if it blows up from 220 volts, it won't take the BDI2000 with it. +If you are outside the US, please plug the power brick into the wall first WITHOUT CONNECTING IT TO THE BDI2000! This is to test the power adapter, if it blows up from 220 volts, it won't take the BDI2000 with it. -If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). +If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). Now plug in the power supply to the BDI2000. Be gentle and make sure the key on the plug is facing the correct way - I had to hack up that power supply out of parts as it did not come with one. -Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. +Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with the IP you specified before shipping - You should get output like the below, saying it's waiting for a target: @@ -27,31 +27,31 @@ TARGET: waiting for target Vcc TARGET: waiting for target Vcc ``` -Now you must connect the BDI2000 to the LB6M. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. +Now you must connect the BDI2000 to the LB6M. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. -Plug in the cable so pin #1 is on the left side, like this: +Plug in the cable so pin #1 is on the left side, like this: ![bdi-pins](https://fohdeesha.com/data/other/bdipins.jpg) -On an LB6M, the connection should look like this: +On an LB6M, the connection should look like this: ![bdi-lb6m](https://fohdeesha.com/data/other/bdilb6m.jpg) -Now that everything is plugged in and the BDI2000 is powered, power up the switch. +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 When the switch powers up, you should get some new output in your telnet connection to the unit, similar to the below: ``` -- TARGET: resetting target passed -- TARGET: processing target startup .... +- TARGET: resetting target passed +- TARGET: processing target startup .... - TARGET: processing target startup passed ``` Make sure you got `processing target startup passed` at the end, this means the CPU is successfully halted. Test the JTAG session by reading the beginning bootloader area of flash: @@ -67,12 +67,12 @@ fff80020: 00030030 0004ffff ffffffff 00000000 ...0............ fff80030: 4e6ab6ae 07030000 74727a30 37333030 Nj......trz07300 ``` -If you get something similar to above, the JTAG session is working. +If you get something similar to above, the JTAG session is working. Now we tell it to copy the corrupted flash bootloader to a file on your TFTP server named `badboot.bin` - this is an important step as it will let me see exactly what in the bootloader got corrupted: ``` dump 0xfff80000 0x00080000 badboot.bin -``` +``` >Note: if you get an error here, it is most likely related to TFTP permissions (it can't write the file on your TFTP server). See the intro paragraph for linux TFTP permission information. Once that finishes, we can write the new bootloader. First we must erase the bootloader section of flash properly before we can write to it: @@ -87,17 +87,17 @@ When that finishes, connect a serial console cable to the LB6M switch (while it ``` reset run ``` -The switch should boot normally and you should see it's usual boot text in your serial console. ->If you don't see any text in your serial window and the switch seems like it's still bricked, Unplug the switch power, then plug it back in, then follow the above erasing and flashing steps again as you must have skipped something. +The switch should boot normally and you should see it's usual boot text in your serial console. +>If you don't see any text in your serial window and the switch seems like it's still bricked, Unplug the switch power, then plug it back in, then follow the above erasing and flashing steps again as you must have skipped something. Once you have confirmed it has booted succesfully - unplug/power off the switch - do not run it for very long with the top off - once the ASIC is initialized it gets VERY hot without any airflow being forced over it. ->This is not an issue when initially booting the switch with JTAG, as the CPU is halted before it has a chance to bring the ASIC online. It is only once the switch boots successfully in which it will begin heating. +>This is not an issue when initially booting the switch with JTAG, as the CPU is halted before it has a chance to bring the ASIC online. It is only once the switch boots successfully in which it will begin heating. 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. diff --git a/docs/jtag6610.md b/docs/jtag6610.md index f7ddd3f..489a1c7 100644 --- a/docs/jtag6610.md +++ b/docs/jtag6610.md @@ -1,23 +1,23 @@ # PowerPC JTAG Recovery (ICX6610) -This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (ICX6610 or FCX) using a BDI2000. +This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (ICX6610 or FCX) using a BDI2000. ## Preparation Start by downloading [this ZIP](https://fohdeesha.com/data/other/jtag-recovery-6610-fcx.zip). -Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at the address you specified before the unit was shipped - make sure said TFTP server is running with above files before powering the BDI2000. +Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at the address you specified before the unit was shipped - make sure said TFTP server is running with above files before powering the BDI2000. -**Note:** If you are attempting this with your own BDI2000 and need the appropriate MPC85xx BDI firmware, contact me via [GitHub](https://github.com/Fohdeesha) or [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/). +**Note:** If you are attempting this with your own BDI2000 and need the appropriate MPC85xx BDI firmware, contact me via [GitHub](https://github.com/Fohdeesha) or [STH](https://forums.servethehome.com/index.php?threads/brocade-icx-series-cheap-powerful-10gbe-40gbe-switching.21107/). If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary. ## Connections -If you are outside the US, please plug the power brick into the wall first WITHOUT CONNECTING IT TO THE BDI2000! This is to test the power adapter, if it blows up from 220 volts, it won't take the BDI2000 with it. +If you are outside the US, please plug the power brick into the wall first WITHOUT CONNECTING IT TO THE BDI2000! This is to test the power adapter, if it blows up from 220 volts, it won't take the BDI2000 with it. -If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). +If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). Now plug in the power supply to the BDI2000. Be gentle and make sure the key on the plug is facing the correct way - I had to hack up that power supply out of parts as it did not come with one. -Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. +Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with the IP you specified before shipping - You should get output like the below, saying it's waiting for a target: @@ -27,33 +27,33 @@ TARGET: waiting for target Vcc TARGET: waiting for target Vcc ``` -Now you must connect the BDI2000 to the ICX6610. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. +Now you must connect the BDI2000 to the ICX6610. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. -Plug in the cable so pin #1 is on the left side, like this: +Plug in the cable so pin #1 is on the left side, like this: ![bdi-pins](https://fohdeesha.com/data/other/bdipins.jpg) -On an ICX6610, the connection should look like this: +On an ICX6610, the connection should look like this: ![bdi-6610](https://fohdeesha.com/data/other/bdi6610.jpg) -**Note:** The above picture is a 48 port ICX6610. The 24 port ICX6610 will have a slightly different board layout, and I believe the JTAG connector is on the opposite side. +**Note:** The above picture is a 48 port ICX6610. The 24 port ICX6610 will have a slightly different board layout, and I believe the JTAG connector is on the opposite side. -Now that everything is plugged in and the BDI2000 is powered, power up the switch. +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 When the switch powers up, you should get some new output in your telnet connection to the unit, similar to the below: ``` -- TARGET: resetting target passed -- TARGET: processing target startup .... +- TARGET: resetting target passed +- TARGET: processing target startup .... - TARGET: processing target startup passed ``` Make sure you got `processing target startup passed` at the end, this means the CPU is successfully halted. Test the JTAG session by reading the beginning bootloader area of flash: @@ -69,12 +69,12 @@ Depending on how corrupt your bootloader area is, you should see something that 0_fff80030 : 52b166af 0a010000 67727a31 30313030 R.f.....grz10100 ``` -If you get something similar to above, the JTAG session is working. +If you get something similar to above, the JTAG session is working. Now we tell it to copy the corrupted flash bootloader to a file on your TFTP server named `badboot.bin` - this is an important step as it will let me see exactly what in the bootloader got corrupted: ``` dump 0xfff80000 0x00080000 badboot.bin -``` +``` >Note: if you get an error here, it is most likely related to TFTP permissions (it can't write the file on your TFTP server). See the intro paragraph for linux TFTP permission information. Once that finishes, we can write the new bootloader. First we must erase the bootloader section of flash properly before we can write to it: @@ -89,17 +89,17 @@ When that finishes, connect a serial console cable to the switch (while it is st ``` reset run ``` -The switch should boot normally and you should see it's usual boot text in your serial console. ->If you don't see any text in your serial window and the switch seems like it's still bricked, Unplug the switch power, then plug it back in, then follow the above erasing and flashing steps again as you must have skipped something. +The switch should boot normally and you should see it's usual boot text in your serial console. +>If you don't see any text in your serial window and the switch seems like it's still bricked, Unplug the switch power, then plug it back in, then follow the above erasing and flashing steps again as you must have skipped something. Once you have confirmed it has booted succesfully - unplug/power off the switch - do not run it for very long with the top off - once the ASIC is initialized it gets VERY hot without any airflow being forced over it. ->This is not an issue when initially booting the switch with JTAG, as the CPU is halted before it has a chance to bring the ASIC online. It is only once the switch boots successfully in which it will begin heating. +>This is not an issue when initially booting the switch with JTAG, as the CPU is halted before it has a chance to bring the ASIC online. It is only once the switch boots successfully in which it will begin heating. 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. diff --git a/docs/linux.md b/docs/linux.md index 9a9ebe1..b3f29d4 100644 --- a/docs/linux.md +++ b/docs/linux.md @@ -1,12 +1,12 @@ # Accessing Linux -This only applies to the newer architecture switches - the ICX6450, ICX6650, and the ICX7xxx series. The older models (GS, FCX, ICX6610, etc) run a proprietary bootloader and OS, so there is no Linux to access. +This only applies to the newer architecture switches - the ICX6450, ICX6650, and the ICX7xxx series. The older models (GS, FCX, ICX6610, etc) run a proprietary bootloader and OS, so there is no Linux to access. -Some time after the ICX6610 design, they moved to using the popular u-boot bootloader, which then boots good old linux. The linux system then launches a monolithic FastIron binary. This is of course all transparent, all you will see is the normal FastIron interface - except now it's an application being ran on top of linux. +Some time after the ICX6610 design, they moved to using the popular u-boot bootloader, which then boots good old linux. The linux system then launches a monolithic FastIron binary. This is of course all transparent, all you will see is the normal FastIron interface - except now it's an application being ran on top of linux. After some poking around in a dump of a running switches RAM, I stumbled upon the INIT script used to start the linux system. Of interest were these statements (trimmed for brevity): ``` -#If noautostart is set in uboot, stop at linux prompt +#If noautostart is set in uboot, stop at linux prompt cat /proc/cmdline |grep "noautostart" 1>/dev/null 2>&1 if [ $? -eq 0 ] then START_FI_AUTO=0 #If enabletelnet is set in uboot, then start telnet daemon @@ -18,14 +18,14 @@ It's looking at the boot arguments passed by the bootloader for a `noautostart` ## Method 1: Disable FastIron AutoStart -This method tells the switch not to boot the Fastiron app, and drops you right into linux. You will only have serial access to the switch, the usual networking software will NOT be loaded. +This method tells the switch not to boot the Fastiron app, and drops you right into linux. You will only have serial access to the switch, the usual networking software will NOT be loaded. Get into the bootloader like usual (hit `b` during boot), then run the following: ``` setenv extra_bootargs noautostart boot ``` ->note: this only sets this argument once and does not save it. So on subsequent reboots or power-ons, the string will be gone and it will boot normally. +>note: this only sets this argument once and does not save it. So on subsequent reboots or power-ons, the string will be gone and it will boot normally. It will begin booting like normal, but eventually you'll land in a shell: @@ -37,8 +37,8 @@ Enter 'help' for a list of built-in commands. ``` **Note:** If your ICX7xxx series switch asks for a root password, it's `wYbRaMWrYIJgg` - 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`. - + 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`. + Check out the filesystem: ``` @@ -52,9 +52,9 @@ In the `fast_iron` directory, you'll find the startup configs you save from the ## Method 2: Enable Hidden Telnet Server -This method tells the switch to start a hidden telnet server attached to the underlying Linux OS. It's only accessible via the management port (this is the only networking port Linux can see as it's off the management CPU, not the switching ASIC). The IP for Linux (where the telnet server will be) is set by a bootloader variable. +This method tells the switch to start a hidden telnet server attached to the underlying Linux OS. It's only accessible via the management port (this is the only networking port Linux can see as it's off the management CPU, not the switching ASIC). The IP for Linux (where the telnet server will be) is set by a bootloader variable. -The upside of this method is that FastIron will still start, so you'll still have a normal functioning switch. There will just be an (unsecure) telnet daemon running on the management port with raw access to the underlying Linux OS - great for live debugging. +The upside of this method is that FastIron will still start, so you'll still have a normal functioning switch. There will just be an (unsecure) telnet daemon running on the management port with raw access to the underlying Linux OS - great for live debugging. Get into the bootloader like usual (hit `b` during boot), then run the following. For the IP, choose an IP that is not in use anywhere else, especially on the switch. If you have a management IP assigned to the switch, this is separate from that and needs to be a different IP: ``` @@ -62,7 +62,7 @@ setenv extra_bootargs enabletelnet setenv ipaddr 192.168.1.57 boot ``` ->note: this only sets this argument once and does not save it. So on subsequent reboots or power-ons, the string will be gone and it will boot normally. +>note: this only sets this argument once and does not save it. So on subsequent reboots or power-ons, the string will be gone and it will boot normally. The switch will boot as normal, except now the underlying Linux OS has launched a telnet server at the specified IP, and is accessible via the management port only. When you telnet to it (default telnet port), you will have a full Linux CLI: @@ -70,7 +70,7 @@ The switch will boot as normal, except now the underlying Linux OS has launched Welcome to FastIron Board's Telnet session _ _ | ||_| - | | _ ____ _ _ _ _ + | | _ ____ _ _ _ _ | || | _ \| | | |\ \/ / | || | | | | |_| |/ \ |_||_|_| |_|\____|\_/\_/ diff --git a/docs/perc.md b/docs/perc.md index 3937e57..3b24bec 100644 --- a/docs/perc.md +++ b/docs/perc.md @@ -1,4 +1,4 @@ -# H310/H710/H710P/H810 Mini & Full Size IT Crossflashing +# H310/H710/H710P/H810 Mini & Full Size IT Crossflashing This guide allows you to crossflash 12th gen Dell Mini Mono & full size cards to LSI IT firmware. Mini Mono refers to the small models that fit in the dedicated "storage slot" on Dell servers. Because iDRAC checks the PCI vendor values of cards in this slot before allowing the server to boot, the generic full-size PERC crossflashing guides do not apply. This guide however solves that issue. [Technical explanation](https://github.com/marcan/lsirec/issues/1#issuecomment-574971959) for those curious. The following cards are currently supported (if you have a model not listed, [contact me](mailto:jon@fohdeesha.com?subject=PERC-Unknown)): @@ -10,32 +10,32 @@ 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 -There's two main reasons to do this, assuming you don't need the hardware RAID functionalities of the stock firmware: +There's two main reasons to do this, assuming you don't need the hardware RAID functionalities of the stock firmware: **Better Performance:** the plain LSI IT firmware in this guide drastically increases the max [queue depth](https://www.settlersoman.com/what-is-storage-queue-depth-qd-and-why-is-it-so-important/) of the adapter. For instance on the H310 Mini, it goes from 25 with the stock Dell RAID firmware to 600 with the LSI IT firmware. This can mean drastic improvements in IOPS with heavy SSD configurations for example. **Different Driver:** The stock Dell firmware (MegaRAID-based) uses the MegaRAID driver in Linux/FreeBSD/etc. In some distributions this can cause issues, for example FreeNAS has issues pulling SMART data from drives connected to a MegaRAID controller. After crossflashing to IT mode, the card is used by the OS via the much simpler mpt3sas driver. ## Preparation -Ensure there is only one LSI-based adapter in your system. If there are others besides the adapter you intend to flash, remove them! Also in the server BIOS settings, under Integrated Devices, ensure both `SR-IOV Global Enable` and `I/OAT DMA Engine` are **disabled**. They are disabled by default, so unless you've changed them in the past you should be good. +Ensure there is only one LSI-based adapter in your system. If there are others besides the adapter you intend to flash, remove them! Also in the server BIOS settings, under Integrated Devices, ensure both `SR-IOV Global Enable` and `I/OAT DMA Engine` are **disabled**. They are disabled by default, so unless you've changed them in the past you should be good. **Remove the RAID battery** from the adapter. The IT firmware has no cache for the battery to back, in fact the IT firmware will have no clue the battery is there if you leave it connected. To make matters worse, in rare cases some people observed the battery holding old Dell code in the card's RAM and it made their crossflash process a pain. Just unplug/remove the battery and store it somewhere in case you return to Dell firmware. -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. +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. +>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. ## Finding Your Card Revision @@ -47,18 +47,18 @@ 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. @@ -66,7 +66,7 @@ If it displays anything that doesn't exactly match the above choices, [contact m >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. -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. +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. 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. @@ -115,57 +115,57 @@ The main difference between the B0 and D1 revisions is the D1 will link at PCIe 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. +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. -```Documentation version:``` [ v2.4 (02-23-2021)](https://github.com/Fohdeesha/lab-docu/commits/master) +```Documentation version:``` [ v2.4 (02-23-2021)](https://github.com/Fohdeesha/lab-docu/commits/master) diff --git a/docs/stack-ports.md b/docs/stack-ports.md index f75e338..2e60e03 100644 --- a/docs/stack-ports.md +++ b/docs/stack-ports.md @@ -1,9 +1,9 @@ # ICX6610 Stack Ports ## Upgrading The Software -Thankfully in FastIron release 08.0.10 and up, Brocade quietly removed the "stack-only" restriction on the rear 40gbE ports. +Thankfully in FastIron release 08.0.10 and up, Brocade quietly removed the "stack-only" restriction on the rear 40gbE ports. -This means the first step is to update to the latest release. This link has instructions and a ZIP of the latest images - [FastIron Upgrade & Config Guide](https://fohdeesha.com/docs/fcx/). +This means the first step is to update to the latest release. This link has instructions and a ZIP of the latest images - [FastIron Upgrade & Config Guide](https://fohdeesha.com/docs/fcx/). However you're not done yet!