diff options
| author |   Bin Hu <bh526r@att.com> | 2016-01-10 16:10:49 -0800 |
|---|---|---|
| committer | Bin Hu <bh526r@att.com> | 2016-01-10 16:10:49 -0800 |
| commit | cfccf3fc03a1b2846d14cd762bda4e5bd63bd658 (patch) | |
| tree | a31f9ae1e74c79bcfa8591b2984b4794059698a2 | |
| parent | 65838a2c8bf59035136bc7be7256d90ba22f05e8 (diff) | |
JIRA:IPVSIX-29
Change-Id: I4e923f3bc68909b1fa91c2d4ebad6cbcf42b2a8f
Signed-off-by: Bin Hu <bh526r@att.com>
| -rw-r--r-- | docs/setupservicevm/4-ipv6-configguide-servicevm.rst | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst index 8212c1e..61412e1 100644 --- a/docs/setupservicevm/4-ipv6-configguide-servicevm.rst +++ b/docs/setupservicevm/4-ipv6-configguide-servicevm.rst @@ -270,7 +270,15 @@ Please **NOTE** that in case of HA (High Availability) deployment model where mu 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-30**. 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 and execute steps **SETUP-SVM-24** +through **SETUP-SVM-30** **SETUP-SVM-24**: identify the ``ipv6-router`` namespace and move to the namespace |