From bcd2e6455dbdd86b52e51bdecd194d75fa09426a Mon Sep 17 00:00:00 2001 From: Bin Hu Date: Fri, 8 Jan 2016 22:27:13 -0800 Subject: JIRA:IPVSIX-29 Change-Id: Iadb01d1dd79e1da05003bbc524040c03d20abe88 Signed-off-by: Bin Hu (cherry picked from commit 987aa5e0d106068f6c4887ba21bcd4321cb7f203) --- docs/setupservicevm/4-ipv6-configguide-servicevm.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/setupservicevm/4-ipv6-configguide-servicevm.rst') diff --git a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst index fb9f450..8212c1e 100644 --- a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst +++ b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst @@ -266,6 +266,12 @@ Spawn ``RADVD`` in ``ipv6-router`` Let us manually spawn a ``radvd`` daemon inside ``ipv6-router`` namespace to simulate an external router. First of all, we will have to identify the ``ipv6-router`` namespace and move to the namespace. +Please **NOTE** that in case of HA (High Availability) deployment model where multiple controller +nodes are used, ``ipv6-router`` created in step **SETUP-SVM-11** could be in any of the controller +node. Thus you need to identify in which controller node ``ipv6-router`` is created in order to manually +spawn ``radvd`` daemon inside the ``ipv6-router`` namespace in steps **SETUP-SVM-24** through +**SETUP-SVM-30**. + **SETUP-SVM-24**: identify the ``ipv6-router`` namespace and move to the namespace .. code-block:: bash -- cgit 1.2.3-korg