Update ib-bonding README

Signed-off-by: Vladimir Sokolovsky <vlad@mellanox.co.il>

diff --git a/readme_and_howto/ib-bonding.txt b/readme_and_howto/ib-bonding.txt
index f3d043d807ea29ea136f087105f3944435420f03..6dc6e123759f31f3fbe1a60b8b811f953d0281e0 100644 (file)
--- a/readme_and_howto/ib-bonding.txt
+++ b/readme_and_howto/ib-bonding.txt
@@ -8,6 +8,7 @@ IB Bonding
 2.1.2 Writing network scripts under Redhhat-EL5
 2.2 Configuration with sysconfig support
 2.2.1 Writing network scripts under SLES-10
+2.2.2 Writing network scripts under SLES-11 SP1
 2.3 Configuring Ethernet slaves
 
 1. Introduction
@@ -33,7 +34,7 @@ Update 6 or Update 7) and for Redhat-EL5 and above.
 TYPE=Bonding
 MTU=<according to the slave's MTU>
 
-Example: for bond0 (master) the file is named /etc/sysconfig/network-scripts/ifcfg-bond0
+Exmaple: for bond0 (master) the file is named /etc/sysconfig/network-scripts/ifcfg-bond0
 with the following text in the file:
 
 DEVICE=bond0
@@ -49,7 +50,7 @@ MTU=65520
 
 Note: 65520 is a valid mtu value only if all IPoIB slaves operate in connected
 mode and are configured with the same value. For IPoIB slaves that work in
-datagram mode, use MTU=2044. If you don't set correct mtu or don't set mtu at
+datagram modee, use MTU=2044. If you don't set correct mtu or don't set mtu at
 all (and letting it to be set to the default value), performance of the
 interface might decrease.
 
@@ -108,7 +109,7 @@ Note: This feature is available only for SLES-10 and above.
 
 2.2.1 Writing network scripts under SLES-10 
 -----------------------------------------------
-* In the master (bond) interface script add the lins:
+* In the master (bond) interface script add the lines:
 
 BONDING_MASTER=yes
 BONDING_MODULE_OPTS="mode=active-backup miimon=<value>"
@@ -116,7 +117,7 @@ BONDING_SLAVE0=slave0
 BONDING_SLAVE1=slave1
 MTU=<according to the slave's MTU>
 
-Example: for bond0 (master) the file is named /etc/sysconfig/network/ifcfg-bond0
+Exmaple: for bond0 (master) the file is named /etc/sysconfig/network/ifcfg-bond0
 with the following text in the file:
 
 BOOTPROTO="static"
@@ -134,7 +135,7 @@ MTU=65520
 
 Note: 65520 is a valid mtu value only if all IPoIB slaves operate in connected
 mode and are configured with the same value. For IPoIB slaves that work in
-datagram mode, use MTU=2044. If you don't set correct mtu or don't set mtu at
+datagram modee, use MTU=2044. If you don't set correct mtu or don't set mtu at
 all (and letting it to be set to the default value), performance of the
 interface might decrease.
 
@@ -151,13 +152,38 @@ PRE_DOWN_SCRIPT=/etc/sysconfig/network/unenslave.sh
 After the configuration is saved, restart the network service by running:
 /etc/init.d/network restart
 
+2.2.2 Writing network scripts under SLES-11 SP1
+-----------------------------------------------
+Need to change the following parameters in ifcfg-ibX: 
+BOOTPROTO=static 
+STARTMODE=auto 
+
+Logs: 
+ifccfg-ibX 
+BOOTPROTO=static 
+STARTMODE="auto" 
+PRE_DOWN_SCRIPT=/etc/sysconfig/network/unenslave.sh 
+
+ifcfg-bondX 
+BOOTPROTO="static" 
+BROADCAST=195.168.80.255 
+IPADDR=195.168.80.12 
+NETMASK=255.255.255.0 
+NETWORK=195.168.80.0 
+REMOTE_IPADDR="" 
+STARTMODE=auto 
+BONDING_MASTER=yes 
+BONDING_MODULE_OPTS="mode=active-backup miimon=100" 
+BONDING_SLAVE0=ib0 
+BONDING_SLAVE1=ib1 
+
 2.3 Configuring Ethernet slaves
 -------------------------------
-It is not possible to have a mix of Ethernet slaves and IPoIB slaves under the
+It is not possible to have a mix of Ethernt slaves and IPoIB slaves under the
 same bonding master. It is possible however that a bonding master of Ethernet
-slaves and a bonding master of IPoIB slaves will co-exist in one machine.
+slaves and a bonding master of IPoIB slaves will co-exist in one machne.
 To configure Ethernet slaves under a bonding master use the following
-instructions (depending  on the OS)
+instructios (depending  on the OS)
 
 * Under Redhat-AS4
 
@@ -178,7 +204,7 @@ No special instructions are required.
 
 * Under SLES10
 
-When using both type of bonding under, it is necessary to update the
+When using both type of bonding under, it is neccessary to update the
 MANDATORY_DEVICES  environment variable in /etc/sysconfig/network/config with the names
 of the InfiniBand devices ( ib0, ib1, etc. ). Otherwise, bonding devices will be created 
 before InfiniBand devices at boot time.