summaryrefslogtreecommitdiffstats
path: root/book-enea-nfv-core-installation-guide/doc/tor_config_req.xml
blob: 5afc26c68dc87a03ef6d3d4c96aa97b31eb28b7a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="tor-config-req">
  <title>Top of the Rack (TOR) Configuration Requirements</title>

  <para>The switching infrastructure provides connectivity for the ENFV Core
  infrastructure operations, tenant networks (East/West) and provider
  connectivity (North/South). It also provides needed connectivity for the
  Storage Area Network (SAN).</para>

  <para>To avoid traffic congestion, it is strongly encouraged that 3
  physically separated networks be used: 1 physical network for administration
  and control, 1 physical network for tenant private and public networks, and
  1 for SAN. The switching connectivity can (but does not need to) be fully
  redundant, in such case it comprises a redundant 10GE switch pair for each
  of the 3 networks.</para>

  <para>The physical TOR switches are not automatically configured from the
  Fuel ENFV reference platform. All networks involved in the ENFV Core
  infrastructure as well as the provider networks and the private tenant VLANs
  need to be manually configured.</para>

  <para>Manual configuration of the ENFV Core 1.0 hardware platform should be
  carried out according to the <ulink
  url="https://wiki.opnfv.org/display/pharos/Pharos+Specification">ENFV Core
  Pharos specification</ulink>.</para>
</chapter>