diff options
| author | Adrian Calianu <adrian.calianu@enea.com> | 2019-01-31 10:07:38 +0100 |
|---|---|---|
| committer | Sona Sarmadi <sona.sarmadi@enea.com> | 2019-02-08 10:30:33 +0100 |
| commit | 3cbe167b1ca6c4bbeaf6e7c28b6aca05de1bd440 (patch) | |
| tree | ef8916f585408e1644e137f0909e5d1233d2e17c | |
| parent | 31aba7550b5bf6ceefbde1b88877936d5a7fd339 (diff) | |
| download | nfv-access-documentation-3cbe167b1ca6c4bbeaf6e7c28b6aca05de1bd440.tar.gz | |
getting started: Add demo use case for in-band management
Change-Id: I713c1cf1718e2f915875e0e25699b54cfabb9822
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
| -rw-r--r-- | doc/book-enea-nfv-access-getting-started/doc/demo_usecases.xml | 303 | ||||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br.png | bin | 0 -> 7778 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br2.png | bin | 0 -> 13517 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_dpdk_int_bind.png | bin | 0 -> 6872 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fg_instantiation.png | bin | 0 -> 23383 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fortigate_onboard.png | bin | 0 -> 7298 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_lanbr.png | bin | 0 -> 12255 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution.png | bin | 0 -> 100793 bytes | |||
| -rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution_test.png | bin | 0 -> 134590 bytes |
9 files changed, 302 insertions, 1 deletions
diff --git a/doc/book-enea-nfv-access-getting-started/doc/demo_usecases.xml b/doc/book-enea-nfv-access-getting-started/doc/demo_usecases.xml index 1686427..35d72af 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/demo_usecases.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/demo_usecases.xml | |||
| @@ -1894,4 +1894,305 @@ Run: tail -f /opt/testpmd-out</programlisting> | |||
| 1894 | </note> | 1894 | </note> |
| 1895 | </section> | 1895 | </section> |
| 1896 | </section> | 1896 | </section> |
| 1897 | </chapter> | 1897 | |
| 1898 | <section id="inband_management"> | ||
| 1899 | <title>In-band Management</title> | ||
| 1900 | |||
| 1901 | <para>In the case of an NFV Access device installed on a network with | ||
| 1902 | limited access, In-band management can be a solution to manage the device | ||
| 1903 | and to pass data traffic (through only one physical interface). This demo | ||
| 1904 | use-case will show how to enable the In-band management on the NFV Access | ||
| 1905 | device and to access a VNF on the same physical interface.</para> | ||
| 1906 | |||
| 1907 | <figure> | ||
| 1908 | <title>NFV Access In-band management solution setup</title> | ||
| 1909 | |||
| 1910 | <mediaobject> | ||
| 1911 | <imageobject> | ||
| 1912 | <imagedata align="center" fileref="images/uc_ibm_solution.png" | ||
| 1913 | scale="50" /> | ||
| 1914 | </imageobject> | ||
| 1915 | </mediaobject> | ||
| 1916 | </figure> | ||
| 1917 | |||
| 1918 | <para>Setup uses the following network configuration:</para> | ||
| 1919 | |||
| 1920 | <itemizedlist> | ||
| 1921 | <listitem> | ||
| 1922 | <para>1 x Network Interface for WAN and management.</para> | ||
| 1923 | </listitem> | ||
| 1924 | |||
| 1925 | <listitem> | ||
| 1926 | <para>1 x Network Interface for LAN.</para> | ||
| 1927 | </listitem> | ||
| 1928 | </itemizedlist> | ||
| 1929 | |||
| 1930 | <para>For prerequisites and further details, please see <xref | ||
| 1931 | linkend="inband_management" /> and <xref | ||
| 1932 | linkend="vnf_fortigate" />.</para> | ||
| 1933 | |||
| 1934 | <section id="mg_activation"> | ||
| 1935 | <title>In-band management activation for FortiGate VNF | ||
| 1936 | Instantiation</title> | ||
| 1937 | |||
| 1938 | <para>In-band management activation is done by creating a special bridge | ||
| 1939 | which manages all traffic from the WAN interface. The active physical | ||
| 1940 | port of the device (used by the device manager to communicate with the | ||
| 1941 | uCPE Manager) will be connected to the In-band management bridge. Once | ||
| 1942 | the In-band management bridge is activated, communication to the uCPE | ||
| 1943 | Manager will be reactivated, passing through the bridge.</para> | ||
| 1944 | |||
| 1945 | <note> | ||
| 1946 | <para>No other physical port for In-band management can be | ||
| 1947 | used.</para> | ||
| 1948 | </note> | ||
| 1949 | |||
| 1950 | <orderedlist> | ||
| 1951 | <listitem> | ||
| 1952 | <para>Create an In-band management WAN Bridge:</para> | ||
| 1953 | |||
| 1954 | <itemizedlist> | ||
| 1955 | <listitem> | ||
| 1956 | <para>Select the <literal>Device</literal> menu.</para> | ||
| 1957 | </listitem> | ||
| 1958 | |||
| 1959 | <listitem> | ||
| 1960 | <para>In the Configuration tab select | ||
| 1961 | <literal>OpenVSwitch.</literal></para> | ||
| 1962 | </listitem> | ||
| 1963 | |||
| 1964 | <listitem> | ||
| 1965 | <para>Select <literal>Bridges</literal> and click | ||
| 1966 | <literal>Add</literal>.</para> | ||
| 1967 | </listitem> | ||
| 1968 | |||
| 1969 | <listitem> | ||
| 1970 | <para>Use <literal>dpdkWAN</literal> as the | ||
| 1971 | <literal>ovs-bridge-type</literal>.</para> | ||
| 1972 | </listitem> | ||
| 1973 | </itemizedlist> | ||
| 1974 | |||
| 1975 | <figure> | ||
| 1976 | <title>Create In-band management WAN bridge</title> | ||
| 1977 | |||
| 1978 | <mediaobject> | ||
| 1979 | <imageobject> | ||
| 1980 | <imagedata align="center" fileref="images/uc_ibm_br.png" | ||
| 1981 | scale="75" /> | ||
| 1982 | </imageobject> | ||
| 1983 | </mediaobject> | ||
| 1984 | </figure> | ||
| 1985 | </listitem> | ||
| 1986 | |||
| 1987 | <listitem> | ||
| 1988 | <para>Bind the physical port which will be used for LAN access to | ||
| 1989 | <literal>dpdk</literal>:</para> | ||
| 1990 | |||
| 1991 | <itemizedlist> | ||
| 1992 | <listitem> | ||
| 1993 | <para>Select the <literal>Device</literal> menu.</para> | ||
| 1994 | </listitem> | ||
| 1995 | |||
| 1996 | <listitem> | ||
| 1997 | <para>In the Configuration tab select | ||
| 1998 | <literal>OpenVSwitch</literal>.</para> | ||
| 1999 | </listitem> | ||
| 2000 | |||
| 2001 | <listitem> | ||
| 2002 | <para>Select the <literal>Host Interfaces</literal> menu and | ||
| 2003 | click <literal>Add</literal>.</para> | ||
| 2004 | </listitem> | ||
| 2005 | |||
| 2006 | <listitem> | ||
| 2007 | <para>Use <literal>dpdk</literal> as the | ||
| 2008 | <literal>ovs-bridge-type</literal>.</para> | ||
| 2009 | </listitem> | ||
| 2010 | </itemizedlist> | ||
| 2011 | |||
| 2012 | <figure> | ||
| 2013 | <title>Bind LAN physical port to dpdk</title> | ||
| 2014 | |||
| 2015 | <mediaobject> | ||
| 2016 | <imageobject> | ||
| 2017 | <imagedata align="center" | ||
| 2018 | fileref="images/uc_ibm_dpdk_int_bind.png" | ||
| 2019 | scale="75" /> | ||
| 2020 | </imageobject> | ||
| 2021 | </mediaobject> | ||
| 2022 | </figure> | ||
| 2023 | </listitem> | ||
| 2024 | |||
| 2025 | <listitem> | ||
| 2026 | <para>Create a LAN Bridge:</para> | ||
| 2027 | |||
| 2028 | <itemizedlist> | ||
| 2029 | <listitem> | ||
| 2030 | <para>Select the <literal>Device.</literal></para> | ||
| 2031 | </listitem> | ||
| 2032 | |||
| 2033 | <listitem> | ||
| 2034 | <para>In the Configuration menu select | ||
| 2035 | <literal>OpenVSwitch.</literal></para> | ||
| 2036 | </listitem> | ||
| 2037 | |||
| 2038 | <listitem> | ||
| 2039 | <para>Open the <literal>Bridges</literal> menu and click | ||
| 2040 | <literal>Add.</literal></para> | ||
| 2041 | </listitem> | ||
| 2042 | </itemizedlist> | ||
| 2043 | |||
| 2044 | <figure> | ||
| 2045 | <title>Create LAN bridge</title> | ||
| 2046 | |||
| 2047 | <mediaobject> | ||
| 2048 | <imageobject> | ||
| 2049 | <imagedata align="center" fileref="images/uc_ibm_lanbr.png" | ||
| 2050 | scale="75" /> | ||
| 2051 | </imageobject> | ||
| 2052 | </mediaobject> | ||
| 2053 | </figure> | ||
| 2054 | |||
| 2055 | <para>At this step the following bridges should exist:</para> | ||
| 2056 | |||
| 2057 | <figure> | ||
| 2058 | <title>Bridges</title> | ||
| 2059 | |||
| 2060 | <mediaobject> | ||
| 2061 | <imageobject> | ||
| 2062 | <imagedata align="center" fileref="images/uc_ibm_br2.png" | ||
| 2063 | scale="65" /> | ||
| 2064 | </imageobject> | ||
| 2065 | </mediaobject> | ||
| 2066 | </figure> | ||
| 2067 | |||
| 2068 | <note> | ||
| 2069 | <para>The WAN port of the very first VNF instantiated on the | ||
| 2070 | device must be connected to the <literal>ibm-wan-br | ||
| 2071 | bridge</literal>. All other VNFs must be connected in chain with | ||
| 2072 | the first VNF.</para> | ||
| 2073 | </note> | ||
| 2074 | </listitem> | ||
| 2075 | |||
| 2076 | <listitem> | ||
| 2077 | <para>Onboard the first VNF and instantiate it on the device:</para> | ||
| 2078 | |||
| 2079 | <itemizedlist> | ||
| 2080 | <listitem> | ||
| 2081 | <para>Select the <literal>Device.</literal></para> | ||
| 2082 | </listitem> | ||
| 2083 | |||
| 2084 | <listitem> | ||
| 2085 | <para>Select the <literal>VNF</literal> menu.</para> | ||
| 2086 | </listitem> | ||
| 2087 | |||
| 2088 | <listitem> | ||
| 2089 | <para>In the <literal>Descriptors</literal> menu, choose the | ||
| 2090 | <literal>VNF Package</literal> option.</para> | ||
| 2091 | </listitem> | ||
| 2092 | |||
| 2093 | <listitem> | ||
| 2094 | <para>Browse and select the Fortigate bundle you require, before | ||
| 2095 | pressing the <literal>Send</literal> button.</para> | ||
| 2096 | </listitem> | ||
| 2097 | </itemizedlist> | ||
| 2098 | |||
| 2099 | <figure> | ||
| 2100 | <title>Onboard Fortigate VNF</title> | ||
| 2101 | |||
| 2102 | <mediaobject> | ||
| 2103 | <imageobject> | ||
| 2104 | <imagedata align="center" | ||
| 2105 | fileref="images/uc_ibm_fortigate_onboard.png" | ||
| 2106 | scale="50" /> | ||
| 2107 | </imageobject> | ||
| 2108 | </mediaobject> | ||
| 2109 | </figure> | ||
| 2110 | </listitem> | ||
| 2111 | |||
| 2112 | <listitem> | ||
| 2113 | <para>Add the VNF instance:</para> | ||
| 2114 | |||
| 2115 | <itemizedlist> | ||
| 2116 | <listitem> | ||
| 2117 | <para>Select the <literal>Device.</literal></para> | ||
| 2118 | </listitem> | ||
| 2119 | |||
| 2120 | <listitem> | ||
| 2121 | <para>Select the <literal>VNF</literal> menu.</para> | ||
| 2122 | </listitem> | ||
| 2123 | |||
| 2124 | <listitem> | ||
| 2125 | <para>Choose the <literal>Instances</literal> option, select the | ||
| 2126 | VNF configuration you desire and press | ||
| 2127 | <literal>Add.</literal></para> | ||
| 2128 | </listitem> | ||
| 2129 | |||
| 2130 | <listitem> | ||
| 2131 | <para>Browse and select the Fortigate bundle you require, before | ||
| 2132 | pressing the <literal>Send</literal> button.</para> | ||
| 2133 | </listitem> | ||
| 2134 | </itemizedlist> | ||
| 2135 | |||
| 2136 | <figure> | ||
| 2137 | <title>Instantiate Fortigate VNF</title> | ||
| 2138 | |||
| 2139 | <mediaobject> | ||
| 2140 | <imageobject> | ||
| 2141 | <imagedata align="center" | ||
| 2142 | fileref="images/uc_ibm_fg_instantiation.png" | ||
| 2143 | scale="65" /> | ||
| 2144 | </imageobject> | ||
| 2145 | </mediaobject> | ||
| 2146 | </figure> | ||
| 2147 | </listitem> | ||
| 2148 | </orderedlist> | ||
| 2149 | |||
| 2150 | <para>Once the VNF is instantiated, the setup is complete and ready for | ||
| 2151 | testing. Connect the test machine to the LAN port. It will receive an IP | ||
| 2152 | address from the Fortigate VNF and be able to access the | ||
| 2153 | internet.</para> | ||
| 2154 | </section> | ||
| 2155 | |||
| 2156 | <section id="test_fortvnf_inband"> | ||
| 2157 | <title>Testing the Fortigate VNF In-band management activation</title> | ||
| 2158 | |||
| 2159 | <figure> | ||
| 2160 | <title>Test setup</title> | ||
| 2161 | |||
| 2162 | <mediaobject> | ||
| 2163 | <imageobject> | ||
| 2164 | <imagedata align="center" | ||
| 2165 | fileref="images/uc_ibm_solution_test.png" scale="50" /> | ||
| 2166 | </imageobject> | ||
| 2167 | </mediaobject> | ||
| 2168 | </figure> | ||
| 2169 | |||
| 2170 | <para>At this stage, three types of traffic are passing through the WAN | ||
| 2171 | port on the same IP address: </para> | ||
| 2172 | |||
| 2173 | <itemizedlist> | ||
| 2174 | <listitem> | ||
| 2175 | <para>Device management traffic from uCPE Manager.</para> | ||
| 2176 | </listitem> | ||
| 2177 | |||
| 2178 | <listitem> | ||
| 2179 | <para>Fortigate management interface traffic from a web | ||
| 2180 | browser.</para> | ||
| 2181 | </listitem> | ||
| 2182 | |||
| 2183 | <listitem> | ||
| 2184 | <para>Data traffic from the LAN to the internet.</para> | ||
| 2185 | </listitem> | ||
| 2186 | </itemizedlist> | ||
| 2187 | |||
| 2188 | <para>Having access from the uCPE Manager to the device as shown above, | ||
| 2189 | demonstrates that device management traffic passes through the in-band | ||
| 2190 | management WAN bridge successfully.</para> | ||
| 2191 | |||
| 2192 | <para>To access the management interface of the VNF, connect from a web | ||
| 2193 | browser to the public IP address of the device e.g. | ||
| 2194 | <literal>https://<IP></literal>. From a Test machine connected on | ||
| 2195 | LAN port, try a test ping to the internet e.g. "ping 8.8.8.8".</para> | ||
| 2196 | </section> | ||
| 2197 | </section> | ||
| 2198 | </chapter> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br.png new file mode 100755 index 0000000..f28678b --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br2.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br2.png new file mode 100755 index 0000000..72f8178 --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_br2.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_dpdk_int_bind.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_dpdk_int_bind.png new file mode 100755 index 0000000..ea1fef7 --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_dpdk_int_bind.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fg_instantiation.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fg_instantiation.png new file mode 100755 index 0000000..9b4d020 --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fg_instantiation.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fortigate_onboard.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fortigate_onboard.png new file mode 100755 index 0000000..6fa40bd --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_fortigate_onboard.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_lanbr.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_lanbr.png new file mode 100755 index 0000000..18e074e --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_lanbr.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution.png new file mode 100755 index 0000000..10ed27d --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution.png | |||
| Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution_test.png b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution_test.png new file mode 100755 index 0000000..7006068 --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/uc_ibm_solution_test.png | |||
| Binary files differ | |||
