diff --git a/LustreOperations.xml b/LustreOperations.xml
index 27f2c95..92b42f9 100644
--- a/LustreOperations.xml
+++ b/LustreOperations.xml
@@ -324,8 +324,7 @@ osc.myth-OST0004-osc-ffff8800376bdc00.cur_grant_bytes=33808384</screen>
   </section>
   <section xml:id="dbdoclet.50438194_41817">
     <title><indexterm><primary>operations</primary><secondary>failover</secondary></indexterm>Specifying NIDs and Failover</title>
-    <para>If a node has multiple network interfaces, it may have multiple NIDs, which must all be
-      identified so other nodes can choose the NID that is appropriate for their network interfaces.
+    <para>If a node has multiple network interfaces (ie. multi-homed server), it may have multiple NIDs, which must all be identified so other nodes can choose the NID that is appropriate for their network interfaces.
       Typically, NIDs are specified in a list delimited by commas (<literal>,</literal>). However,
       when failover nodes are specified, the NIDs are delimited by a colon (<literal>:</literal>) or
       by repeating a keyword such as <literal>--mgsnode=</literal> or
@@ -333,6 +332,20 @@ osc.myth-OST0004-osc-ffff8800376bdc00.cur_grant_bytes=33808384</screen>
     <para>To display the NIDs of all servers in networks configured to work with the Lustre file
       system, run (while LNET is running):</para>
     <screen>lctl list_nids</screen>
+
+    <para>This example will setup multi-homed servers without failover. Servers <literal>mds0</literal> and <literal>oss0</literal> each have two network interfaces, an Ethernet (tcp0 NID) plus an Infiniband interface (o2ib NID). The are two lustre clients, <literal>client1</literal> uses ethernet access while <literal>client2</literal> uses infiniband to access the MDT and OST targets.
+</para>
+<para>
+The lustre networking for multi-homed servers lnet module setup should following description in <xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="configuringlnet"/>. The Ethernet address for <literal>mds0</literal> is 192.168.10.1 and the Infiniband address is 10.13.24.1. The Ethernet address for <literal>oss0</literal> is 192.168.10.20 and the Infiniband address is 10.13.24.20. The combined MGS/MDT and OST targets are configured to accept connections on both interfaces.
+<screen>
+mds0# mkfs.lustre --fsname=testfs --mdt --mgs --servicenode="10.13.24.1@o2ib,192.168.10.1@tcp0" /dev/sda1
+mds0# mount -t lustre /dev/sda1 /mnt/test/mdt 
+oss0# mkfs.lustre --fsname=testfs --ost --index=0 --mgsnode="10.13.24.1@o2ib,192.168.10.1@tcp0" --servicenode="10.13.24.20@o2ib,192.168.10.20@tcp0" /dev/sdb
+oss0# mount -t lustre /dev/sdb /mnt/test/ost0
+client1# mount -t lustre 192.168.10.1@tcp0:/testfs /mnt/testfs
+client2# mount -t lustre 10.13.24.1@o2ib:/testfs /mnt/testfs
+</screen></para>
+
     <para>In the example below,  <literal>mds0</literal> and <literal>mds1</literal> are configured
       as a combined MGS/MDT failover pair and <literal>oss0</literal> and <literal>oss1</literal>
       are configured as an OST failover pair. The Ethernet address for <literal>mds0</literal> is