Changes between Version 5 and Version 6 of Internal/OpenFlow/QuantaSetup

Timestamp:

Jan 6, 2011, 6:55:19 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/QuantaSetup

@@ -29 +29 @@
 
 === 2.2 updating u-boot ===
-This step is comprised of two steps:
+This step is comprised of the following steps:
  1. change network settings of switch
- 2. update u-boot via tftp
+ 2. update u-boot
+ 3. upload kernel, root filesystem, and device tree to flash
+ 4. modify boot parameters
 
+=== 2.2.1. change network settings ===
 The network settings are hard-wired into the switch via environment variables. The default settings statically set the switch's IP to a 192.168.X.X address block, which you might want to change depending on your network setup. This can be done using command `setenv`. While all environment variables can be viewed with `printenv`, the four variables of our interest are:
 
@@ -40 +43 @@
  * netmask (self-explanatory) 
 
-These variables should correspond to those for the network you're attaching the switch to. In our case, we set the switch's Ip to 10.50.0.40, and cut out the hassle of setting the gateway IP by just directly pointing the switch to think the tftp server is the gateway:    
+These variables should correspond to those for the network you're attaching the switch to. In our case, we set the switch's IP to 10.50.0.40, and cut out the hassle of setting the gateway IP by just directly pointing the switch to think the tftp server is the gateway:    
 
 {{{
@@ -47 +50 @@
 => setenv netmask 255.255.0.0
 => setenv serverip 10.50.0.42
-=> save
+=> saveenv
 }}}
 
-once the variables are set, you can start copying the necessary files to the switch using `copy`:
+=== 2.2.2. updating u-boot/copying files to flash ===
+Once the networking variables are set, you can start copying the necessary files to the switch using `copy`. `copy` uses tftp to fetch the images:
+
 {{{
 => copy -b tftp://10.50.0.42/u-boot.bin
+=> copy -k tftp://10.50.0.42/uImage
 => copy -r tftp://10.50.0.42/uInitrd2m
 => copy -d tftp://10.50.0.42/LB9A.dtb
-=> copy -k tftp://10.50.0.42/uImage
 }}}
-and reboot the switch. if all goes well, you should be at the Linux shell prompt once the thing starts up.
+
+The first line updates u-boot. The next three fetch the kernel image, root filesystem, and device tree, respectively. 
+
+=== 2.2.3. modifying boot parameters ===
+in addition, you want to modify `flash_bootcmd` so that it tells the linux kernel to mount the root filesystem read-write:
+{{{
+=> setenv flash_bootcmd 'setenv bootargs root=/dev/ram console=ttyS0,$baudrate rw; bootm ffd00000 ff000000 ffee0000'
+=> saveenv
+}}}
+
+and reboot the switch. if all goes well, you should be at the Linux shell prompt once the switch starts up.
 
 == 3. Configuration ==
@@ -64 +79 @@
  * The ssh server (dropbear) is enabled by default. Telnet can be started by invoking telnetd. In either case the default username is `root`, and password is `OpenFlow`. 
 
-=== 3.1. Key files ===
+=== 3.1. Using the !OpenFlow CLI (OF-BCM) ===
+OF-BCM is the !OpenFlow command line supplied with the image. It can be started manually:
+{{{
+# /sbin/of-bcm-cli
+Broadcom Command Monitor: Copyright (c) 1998-2008 Broadcom Corporation
+Release: sdk-xgs-robo-5.6.6 built 20100905 (Sun Sep  5 23:01:38 2010)
+Stanford OpenFlow Monitor
+Platform: LB9A_MPC8541
+OS: Unix (Posix)
+PCI unit 0: Dev 0xb538, Rev 0x11, Chip BCM56538_B0, Driver BCM56634_B0
+rc: unit 0
+
+...
+
+OF-BCM.0>
+}}}
+
+=== 3.2. Key files ===
  The !OpenFlow components of the switch rely on the following:
  * `/etc/rc.sh` - system startup script: bring up `lo`, mounts filesystems, loads kernel modules, ect