mirror of
https://github.com/Fohdeesha/lab-docu.git
synced 2025-03-11 13:12:09 +01:00
fix relative links v8473
This commit is contained in:
Jon Sands
parent
35aa91fcfb
commit
fb9060642c
@ -11,7 +11,7 @@ The EEPROM would contain a magic string of letters and numbers, and when the swi
|
||||
|
||||
## 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.
|
||||
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/32830778075.html?spm=a2g0o.productlist.0.0.649966f7REdDov) 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.
|
||||
|
||||
@ -19,8 +19,7 @@ You can also buy a cheap [EEPROM Programmer](https://www.amazon.com/gp/product/B
|
||||
|
||||
**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 Unlock Strings
|
||||
@ -101,22 +100,22 @@ reset
|
||||
|
||||
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](store/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:
|
||||
|
||||
|
||||
|
||||
|
||||
In the following prompt, select **Browse my computer for driver software**:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In the following prompt, browse to the folder you extracted from the ZIP, then select the Driver folder within it, then click OK/next:
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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](store/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:
|
||||
|
||||
@ -71,7 +71,7 @@ On PowerPC models (FCX, ICX6610) it is more complicated, as they do not run linu
|
||||
|
||||
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:
|
||||
|
||||
|
||||
|
||||
|
||||
There's our license string, starting with `*B` as always. So, extracted, it looks like this (again, not a real license):
|
||||
```
|
||||
|
||||
@ -70,7 +70,7 @@ dumpimage -T flat_dt -p 3 -i trimmed.bin ramdisk.zip
|
||||
```
|
||||
The above example extracts the ramdisk from the above firmware file, which is the main filesystem for the switch. If you open up the resulting `ramdisk.zip` with 7zip or similar, you'll be able to explore the switch filesystem, including the interesting init scripts under `/etc/`:
|
||||
|
||||
|
||||
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ FCX3(config)#dm
|
||||
```
|
||||
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.
|
||||
**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](store/FastIron-Hidden.txt) for a full list of these commands. Many of these might delete your config, your licenses, lock the switch up, etc.
|
||||
|
||||
## Hidden OS Console
|
||||
This only works over a serial connection. It will not work over telnet/ssh/etc. Connect to a FastIron device over serial, and once it's fully booted and running, press ```ctrl+y```, let go, then press ```m```. Then hit enter. It should drop you down to the OS console:
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
## Upgrading The Software
|
||||
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](fcx.md).
|
||||
|
||||
However you're not done yet!
|
||||
|
||||
@ -41,5 +41,5 @@ There should no longer be any ```stack-trunk``` commands, or any commands refere
|
||||
## Port Layout
|
||||
Keep in mind two of the rear ports are 4x 10gbE breakout only, and the remaining two are 40gbE only. The two 40gbE-only ports will NOT run at 10gbE (for instance with a QSFP to SFP+ adapter), so use these two for 40gbE links only. The extremely professional diagram below shows the port config and their associated port numbers in the OS:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user