JIRA:IPVSIX-29

Change-Id: I4804fbd30e18e2ccf23b980eac8c0e09e92e8fc5
Signed-off-by: Bin Hu <bh526r@att.com>

1 files changed, 28 insertions, 22 deletions

diff --git a/docs/reldoc/index.rst b/docs/reldoc/index.rst
index 00caa43..932f429 100644
--- a/docs/reldoc/index.rst
+++ b/docs/reldoc/index.rst
@@ -264,21 +264,7 @@ would be as shown as follows:
     VM1 would have the following IPv6 address: 2001:db8:0:2:f816:3eff:fe33:3333/64
     VM2 would have the following IPv6 address: 2001:db8:0:2:f816:3eff:fe44:4444/64
 
-**OPNFV-NATIVE-SETUP-17**: Now we can ``SSH`` to ``vRouter``.
-
-Please **NOTE** that in case of HA (High Availability) deployment model where multiple controller
-nodes are used, ``ipv6-router`` created in step **OPNFV-NATIVE-SETUP-5** could be in any of the controller
-node. Thus you need to identify in which controller node ``ipv6-router`` is created in order to
-enter the ``ipv6-router`` namespace. The following command in Neutron will display the
-controller on which the ``ipv6-router`` is spawned.
-
-.. code-block:: bash
-
-    neutron l3-agent-list-hosting-router ipv6-router
-
-Then you login to that controller.
-
-To ``SSH`` to ``vRouter``, you can execute the following command.
+**OPNFV-NATIVE-SETUP-17**: Now we can ``SSH`` to VMs. You can execute the following command.
 
 .. code-block:: bash
 
@@ -708,19 +694,39 @@ interface of ``vRouter`` automatically configures an IPv6 SLAAC address.
 Testing to Verify Setup Complete
 --------------------------------
 
-Now, let us ``ssh`` to one of the VMs, e.g. VM1, to confirm that it has successfully configured the IPv6 address
-using ``SLAAC`` with prefix ``2001:db8:0:2::/64`` from ``vRouter``.
+Now, let us ``SSH`` to those VMs, e.g. VM1 and / or VM2 and / or vRouter, to confirm that
+it has successfully configured the IPv6 address using ``SLAAC`` with prefix
+``2001:db8:0:2::/64`` from ``vRouter``.
 
-Please note that you need to get the IPv4 address associated to VM1. This can be inferred from ``nova list`` command.
+We use ``floatingip`` mechanism to achieve ``SSH``.
 
-**SETUP-SVM-31**: ``ssh`` VM1
+**SETUP-SVM-31**: Now we can ``SSH`` to VMs. You can execute the following command.
 
 .. code-block:: bash
 
-    ssh -i /home/odl/vRouterKey cirros@<VM1-IPv4-address>
+    # 1. Create a floatingip and associate it with VM1, VM2 and vRouter (to the port id that is passed).
+    neutron floatingip-create --port-id $(neutron port-list | grep -w eth0-VM1 | \
+    awk '{print $2}') ext-net
+    neutron floatingip-create --port-id $(neutron port-list | grep -w eth0-VM2 | \
+    awk '{print $2}') ext-net
+    neutron floatingip-create --port-id $(neutron port-list | grep -w eth1-vRouter | \
+    awk '{print $2}') ext-net
+
+    # 2. To know / display the floatingip associated with VM1, VM2 and vRouter.
+    neutron floatingip-list -F floating_ip_address -F port_id | grep $(neutron port-list | \
+    grep -w eth0-VM1 | awk '{print $2}') | awk '{print $2}'
+    neutron floatingip-list -F floating_ip_address -F port_id | grep $(neutron port-list | \
+    grep -w eth0-VM2 | awk '{print $2}') | awk '{print $2}'
+    neutron floatingip-list -F floating_ip_address -F port_id | grep $(neutron port-list | \
+    grep -w eth1-vRouter | awk '{print $2}') | awk '{print $2}'
+
+    # 3. To ssh to the vRouter, VM1 and VM2, user can execute the following command.
+    ssh -i ~/vRouterKey fedora@<floating-ip-of-vRouter>
+    ssh -i ~/vRouterKey cirros@<floating-ip-of-VM1>
+    ssh -i ~/vRouterKey cirros@<floating-ip-of-VM2>
 
-If everything goes well, ``ssh`` will be successful and you will be logged into VM1. Run some commands to verify
-that IPv6 addresses are configured on ``eth0`` interface.
+If everything goes well, ``ssh`` will be successful and you will be logged into those VMs.
+Run some commands to verify that IPv6 addresses are configured on ``eth0`` interface.
 
 **SETUP-SVM-32**: Show an IPv6 address with a prefix of ``2001:db8:0:2::/64``