Changes between Version 11 and Version 12 of Internal/OpenFlow/QuantaSetup

Timestamp:

Jan 20, 2011, 11:46:21 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/QuantaSetup

@@ -90 +90 @@
 
 === 2.2.4. Using NFS with DHCP. ===
-Reference article: http://www.openflow.org/wk/index.php/IndigoQuickStartLB4G#NFS
+Reference articles: 
+ * http://www.openflow.org/wk/index.php/IndigoQuickStartLB4G#NFS
+ * http://www.openflowswitch.org/wk/index.php/IndigoQuickStart3290
 [[BR]][[BR]]
-Here, we assume that the switch will be assigned an IP address via DHCP. It will use the assigned IP address for fetching necessary images from an NFS server, and once booted into Linux, the variable DEV_ADDR.
+Here, we assume that the switch will be assigned an IP address via DHCP. It will use the assigned IP address for 1) booting via NFS, and once booted into Linux, 2) the value assigned to DEV_ADDR and the management interface eth0. It is also assumed that you have a working NFS server with the following line in /etc/exports:
+
+{{{
+/config   10.19.0.0/255.255.0.0(rw,sync,insecure,no_subtree_check)
+}}}
 
 1. DHCP setup in u-boot:  
@@ -101 +107 @@
 => setenv autoload no
 }}}
-The fiirst two commands blank out any previously assigned IP addresses and boot arguments. The next two enable DHCP. You can test if DHCP works via the command `dhcp`:
+The first two commands blank out any previously assigned IP addresses and boot arguments. The next two enable DHCP. You can test if DHCP works via the command `dhcp`:
 {{{
 => dhcp
@@ -112 +118 @@
 2. Set the startup script variable:
 {{{
-=> setenv dn_boot 'dhcp; setenv bootargs root=/dev/nfs ip=$ipaddr:$nfsip::$netmask:$hostname:$netdev \
-console=$consoledev,$baudrate nfsroot=$nfsip:$rootpath rw DEV_ADDR=$ipaddr ETH0_IP=$ipaddr $extra_boot_args; \ 
-bootm ffd00000'
+=> setenv dn_boot 'dhcp; nfs ff000000 $nfsip:$rootpath/uInitrd2m; \
+setenv bootargs root=/dev/ram console=ttyS0,$baudrate DEV_ADDR=$ipaddr \
+ETH0_IP=$ipaddr $extra_boot_args rw; bootm ffd00000 ff000000 ffee0000'
 }}}
-`dhcp` invokes the DHCP client we configured earlier, which sets $ipaddr. Next, bootargs are set so that u-boot pulls the desired filesystem from a NFS . The next few parameters, `ip`,`console`,`$baudrate`, and `nfsroot` set the networking, standard I/O, and NFS parameters. 'rw' set mount parameters for the root FS. Both DEV_ADDR and ETH0_IP are variables used by Linux once the system boots into it; They are both set to the DHCP assigned IP address. $extra_boot_args can be set to additional variables using "`setenv extra_boot_args '<VARS>'`" (It's essentially a dummy variable). Finally, `bootm` is used to load the linux kernel stored on flash.   
+`dhcp` invokes the DHCP client we configured earlier, which sets $ipaddr. Next, the necessary image(s) are loaded via NFS. Then, bootargs are set so that the OS knows where to locate the root FS (in /dev/ram). 'rw' set mount parameters for the root FS. Both DEV_ADDR and ETH0_IP are variables used by Linux once the system boots into it; They are both set to the DHCP assigned IP address. $extra_boot_args can be set to additional variables using "`setenv extra_boot_args '<VARS>'`" (It's essentially a dummy variable). Finally, `bootm` is used to load the linux kernel, filesystem, and device tree stored on flash.   
 
 3. Set additional variables. Make sure all the variables required by the startup script are defined. You may also want the set the bootcmd to boot using the new script. 
@@ -123 +129 @@
 => setenv hostname sw-sb9-da
 => setenv netmask 255.255.0.0
-=> setenv rootpath /config/
+=> setenv rootpath /config
 }}}