w1kl4s/quanta-brocade
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add SFP+ information, formatting cleanup

Browse Source
This commit is contained in:
BuildTools
2017-12-22 00:53:49 -05:00
parent 6f8d1ccce7
commit 2035a06ad5
2 changed files with 39 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
documentation/config.md
View File

@@ -18,23 +18,25 @@ Everything can be shortened as long as it doesn't match another command, so the
conf t
```
You also have tab completion so if you're ever curious about a command, type it and hit tab, it'll give you a list of all arguments. You can also just hit tab with no text and it'll show you all commands available at the current level.
Now we need to tell it to start generating our keys, so we can enable SSH:
```
crypto key generate
```
give the switch a name/hostname:
Give the switch a name/hostname:
```
hostname blinkenmaschine
```
To give the switch an IP that's accessible via the normal ports, we need to a assign a virtual interface to the VLAN you'd like it to be accessible on, and give it an IP. That virtual interface is configurable just like a normal physical interface. At it's config level you can set jumbo frames, IP addr, etc. This is also how you enable inter-VLAN routing, you just give multiple VLAN's a router interface with an IP like below, and that's it.
Enter the config level for a vlan:
```
vlan 1
```
assign it a virtual interface. The number doesn't have to match the vlan, you could give it ve 10, but it's easier to keep track of if they match:
Assign it a virtual interface. The number doesn't have to match the vlan, you could give it ve 10, but it's easier to keep track of if they match:
```
router-interface ve 1
```
@@ -47,7 +49,8 @@ exit
```
interface ve 1
```
NOTE: The above command will give you an error if the VLAN it is assigned to has no ports. So if you're setting up VLAN 2 for example, give it a port member while you're at it's config level, and you won't encounter the error.
(NOTE: the above command will give you an error if the VLAN it is assigned to has no ports. So if you're setting up VLAN 2 for example, give it a port member while you're at it's config level, and you won't encounter the error.)
Now we just give that VE interface an IP. Note, addresses for VE's cannot be in the same subnet you've assigned to your out of band management port, for obvious reasons:
```
ip address 192.168.1.2/24
@@ -105,7 +108,7 @@ snmp-server community public ro
##Default Route & DNS
If you'd like the switch to be able to get out to the internet (For example, NTP or ping commands to external hosts or hostnames), do the following:
If you'd like the switch to be able to get out to the internet (For example, NTP or ping commands to external hosts or hostnames), do the following, substituting your gateway IP:
```
ip dns server-address 192.168.1.1
@@ -133,7 +136,7 @@ write memory
```
That's enough to get you going. Some more useful general commands:
show a table of all interfaces:
Show a table of all interfaces:
```
show interface brief
```
@@ -151,7 +154,7 @@ show interface brief ethernet 1
exit
```
To remove commands from your config, just put no in front of them:
To remove commands from your config, just put ```no``` in front of them:
```
interface ethernet 1
no port-name

43
documentation/index.md
View File

@@ -5,7 +5,7 @@
We are not responsible for any damaged devices or property resulting from this guide. This guide assumes you own a legitimate Brocade TurboIron and therefore have rights to the firmware & its use.
Two things will also change due to hardware differences:
* The SFP+ activity/status LEDs stop doing anything. The copper ports and chassis LEDs continue to work as normal. We believe the Brocade lights use an I2C I/O expander with a different I2C address than that of the Quanta's, or even a different set of I/O on the chipset entirely. Only an aesthetic change, everything else functions as normal.
* The SFP+ activity/status LEDs stop doing anything. The copper ports and chassis LEDs continue to work as normal. We believe the Brocade lights use a different I2C I/O expander configuration, or even a different set of I/O on the chipset entirely. Only an aesthetic change, everything else functions as normal.
* The Brocade only has one Out Of Band management port. Your #2 OOB port will no longer do anything. You'll still have OOB management as usual on mgmt #1, and of course in-band management on all the normal ports.
@@ -25,7 +25,7 @@ Connect to the serial console port on the switch and open a terminal window (96
##Flash Preparation
Reboot the switch while watching the serial output, it should prompt you to hit any key to interrupt boot and drop you into the u-boot console, which should look like this:
Reboot the switch while watching the serial output, it should prompt you to hit any key (do so) to interrupt boot and drop you into the u-boot console, which should look like this:
```
=>
@@ -52,11 +52,11 @@ fff80060: 800e171c 7dc07214 480020dd 3c600002 ....}.r.H. .<..
fff80070: 60631200 7c600124 4c00012c 48002065 c..|.$L..,H. e
```
If the output on your switch does not match this exactly, **STOP!** Pastebin your switches output and get in touch with us on [ServeTheHome](https://forums.servethehome.com/index.php?threads/turbocharge-your-quanta-lb6m-flash-to-brocade-turboiron.17971/) - we'll help you figure it out.
If the output on your switch does not match this exactly, **STOP!** Pastebin your switches output and get in touch with us on [ServeTheHome](https://forums.servethehome.com/index.php?threads/turbocharge-your-quanta-lb6m-flash-to-brocade-turboiron.17971/).
Carrying on, assuming your ```md``` output matched ours: It's time to load in the Brocade bootloader to a safe temporary location in RAM. You also need to set a temporary IP for the switch, as well as set the IP of your tftp server destination:
Give the switch a temporary unique IP, as well as the IP of your tftp server:
Give the switch a unique IP (it will only be used for this bootloader session), as well as the IP of your tftp server:
```
setenv ipaddr 192.168.1.50
setenv serverip 192.168.1.49
@@ -103,7 +103,7 @@ If it doesn't match, **STOP**. You can safely reboot back to Quanta by typing ``
##Erasing and replacing the bootloader
You now have the Brocade bootloader we need stored in RAM. We need to erase the existing bootloader, then copy the Brocade loader from that RAM address to the bootloader address. It doesn't need saying that from here on, be incredibly careful, and follow the commands exactly.
You now have the Brocade bootloader we need stored in RAM. We need to erase the existing bootloader, then copy the Brocade loader from that RAM address to the bootloader address. From here on, be incredibly careful, and follow the commands exactly.
Disable the flash write protection:
@@ -137,19 +137,19 @@ fff80060: 00000000 00000000 00000000 00000000 ................
fff80070: 00000000 00000000 00000000 00000000 ................
```
If it matches, continue on to **Booting Brocade** below - the scary part is over. However if it doesn't, stay calm. Does it match the output you got earlier when you ran ```md 0xfff80000 20``` at the beginning of this guide? If so, that means the Quanta bootloader is still there. Either you didn't properly disable write protection, or something else has gone wrong. You can reboot into Quanta like normal, and contact us on the forums.
If it matches, continue on to **Booting Brocade** below - the risky part is over. However if it doesn't, don't panic. Does it match the output you got earlier when you ran ```md 0xfff80000 20``` at the beginning of this guide? If so, that means the Quanta bootloader is still there. Either you didn't properly disable write protection, or something else has gone wrong. You can reboot into Quanta like normal, and contact us on the forums.
However if it matches neither, something has failed. We have yet to see this, but just in case you do - be sure you're running the exact commands here, and do the guide again from ```tftpboot 0x100000 brocadeboot.bin``` and onwards until you get the bootloader where it should be. If you follow the commands, it should work.
**Do not reboot or pull power until this is resolved.** If there is not a valid bootloader in that location, it will not boot itself. As a last resort you can try flashing the quanta bootloader back by substituting the uboot.bin in the recovery folder in all the commands mentioning brocadeboot.bin - just use uboot.bin instead. If successful, the output of ```md 0xfff80000 20``` should match the example at the beginning of this guide, then you can reboot.
##Booting Brocade##
You now have the Brocade bootloader in the bootloader section of the PowerPC flash. Now we just need to reboot!
##Booting Brocade
You now have the Brocade bootloader in the proper section of the PowerPC flash. Now we just need to reboot!
```
reset
```
It will now reboot into the Brocade bootloader. In the Brocade software over serial or telnet, you need to use shift+backspace to backspace. You can remedy this by changing your Putty/terminal settings to "Control+H" for backspace method under Terminal>Keyboard and backspace won't require shift. Once you get it up and running, you can also configure SSH which uses normal backspaces.
It will now reboot into the Brocade bootloader. In the Brocade software, over serial or telnet, you need to use shift+backspace to backspace. You can remedy this by changing your Putty/terminal settings to "Control+H" for backspace method under Terminal>Keyboard and backspace won't require shift. Once you get it up and running, you can also configure SSH which uses normal backspaces.
Firstly boot the OS image via tftp. You need to first give the bootloader a temporary unique IP, then boot the firmware file using the IP address of your tftp server:
```
@@ -157,7 +157,7 @@ ip address 192.168.1.50/24
boot system tftp 192.168.1.49 brocadeimage.bin
```
It will now boot into the full Brocade firmware, however we still need to actually flash it to the device flash as well as fix flash permissions by re-flashing the bootloader using Brocade's official bootloader flashing routine.
It will now boot into the full Brocade firmware, however we still need to actually flash it to the device flash as well as fix flash permissions by re-flashing the bootloader using Brocade's official flashing routine.
First give the management interface an address so it can contact your tftp server:
```
@@ -192,7 +192,9 @@ It now perfectly matches a stock Brocade TurboIron. Reboot and it will come up o
reload
```
That's it! You can ditch the serial cable and telnet to the management IP. If you want to use SSH, you'll need to enable it - follow the included Brocade docs or the Quick Guide on the left. Some commands to check out your new system:
That's it! This first official boot will take a few minutes as it copies the primary image to the backup secondary image partition. You can ditch the serial cable and telnet to the management IP. If you want to use SSH, you'll need to enable it - follow the included Brocade docs or the Quick Guide on the left.
Some commands to check out your new system:
```
show version
@@ -200,7 +202,22 @@ show flash
show chassis
show media
```
This is the full layer 3 image that has all the layer 2 and layer 3 features, so please follow the included guides in the Documentation folder to configure your new switch. A quick guide is available on the left, but this site is not a substitute for learning Brocade's documentation.
This is the full layer 3 image that ships with all features enabled, so please follow the included guides in the Documentation folder to configure your new switch. A quick guide is available on the left, but this site is not a substitute for learning Brocade's documentation.
##SFP+ 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.
So if you want to see information like this :
```
telnet@Route2(config)#sh optic 5
Port Temperature Tx Power Rx Power Tx Bias Current
+----+-----------+--------------+--------------+---------------+
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.
@@ -213,4 +230,4 @@ This is the full layer 3 image that has all the layer 2 and layer 3 features, so
###Contributing:
The markdown source for these guides is hosted on [**our Github repo.**](https://github.com/Fohdeesha/quanta-brocade) If you have any suggested changes or additions feel free to submit a pull request.
```Documentation version: v1.2 (12-21-17)```
```Documentation version: v1.3 (12-22-17)```