JIRA:IPVSIX-29

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

3 files changed, 16 insertions, 6 deletions

diff --git a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst
index 8d0cd9c..0868178 100644
--- a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst
+++ b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst
@@ -41,8 +41,11 @@ Because we need to manually create networks/subnets to achieve the IPv6 vRouter,
 ``NEUTRON_CREATE_INITIAL_NETWORKS=False`` in ``local.conf`` file. When this flag is set to False,
 ``devstack`` does not create any networks/subnets during the setup phase.
 
-Now we have to move the public network from physical network interface to ``br-ex``,
-including moving the public IP address and setting up default route.
+Now we have to move the physical interface (i.e. the public network interface) to ``br-ex``,
+including moving the public IP address and setting up default route. **Please note that this step
+may already have been done when you use a different installer to deploy OpenStack because that installer
+may have already moved the physical interface to** ``br-ex`` **during deployment**.
+
 In OpenStack Controller Node ``opnfv-os-controller``, ``eth1`` is configured to provide external/public connectivity
 for both IPv4 and IPv6 (optional). So let us add this interface to ``br-ex`` and move the IP address, including the
 default route from ``eth1`` to ``br-ex``.
diff --git a/docs/setupservicevm/5-ipv6-configguide-scenario-1-native-os.rst b/docs/setupservicevm/5-ipv6-configguide-scenario-1-native-os.rst
index 00667bb..d020521 100644
--- a/docs/setupservicevm/5-ipv6-configguide-scenario-1-native-os.rst
+++ b/docs/setupservicevm/5-ipv6-configguide-scenario-1-native-os.rst
@@ -161,6 +161,9 @@ configuration parameters.
 **OS-NATIVE-SEC-3**: After updating the settings, you will have to restart the
 ``Neutron`` and ``Nova`` services.
 
+**Please note that the commands of restarting ``Neutron`` and ``Nova`` would vary depending on the installer.
+Please refer to relevant documentation of specific installers**
+
 *********************************
 Set Up Service VM as IPv6 vRouter
 *********************************
@@ -197,8 +200,10 @@ the following command may be used for some other installers:
 
     glance image-create --name 'Fedora22' --disk-format qcow2 --container-format bare --file ./Fedora-Cloud-Base-22-20150521.x86_64.qcow2
 
-**OS-NATIVE-SETUP-4**: Now we have to move the public network from physical network
-interface to ``br-ex``, including moving the public IP address and setting up default route.
+**OS-NATIVE-SETUP-4**: Now We have to move the physical interface (i.e. the public network interface)
+to ``br-ex``, including moving the public IP address and setting up default route. **Please note that this step
+may already have been done when you use a different installer to deploy OpenStack because that installer
+may have already moved the physical interface to** ``br-ex`` **during deployment**.
 
 Because our ``opnfv-os-controller`` node has two interfaces ``eth0`` and ``eth1``,
 and ``eth1`` is used for external connectivity, move the IP address of ``eth1`` to ``br-ex``.
diff --git a/docs/setupservicevm/scenario-3-4-ipv6-configguide-servicevm.rst b/docs/setupservicevm/scenario-3-4-ipv6-configguide-servicevm.rst
index 6595cc6..5be5228 100644
--- a/docs/setupservicevm/scenario-3-4-ipv6-configguide-servicevm.rst
+++ b/docs/setupservicevm/scenario-3-4-ipv6-configguide-servicevm.rst
@@ -36,8 +36,10 @@ Please **NOTE** that the method of sourcing tenant credentials may vary dependin
 
     glance image-create --name 'Fedora22' --disk-format qcow2 --container-format bare --file ./Fedora-Cloud-Base-22-20150521.x86_64.qcow2
 
-**SCENARIO-3-SETUP-4**: Now we have to move the public network from physical network
-interface to ``br-ex``, including moving the public IP address and setting up default route.
+**SCENARIO-3-SETUP-4**: Now we have to move the physical interface (i.e. the public network interface)
+to ``br-ex``, including moving the public IP address and setting up default route. **Please note that this step
+may already have been done when you use a different installer to deploy OpenStack because that installer
+may have already moved the physical interface to** ``br-ex`` **during deployment**.
 
 Because our ``opnfv-os-controller`` node has two interfaces ``eth0`` and ``eth1``,
 and ``eth1`` is used for external connectivity, move the IP address of ``eth1`` to ``br-ex``.