Connecting to the VTEP

Use this procedure to connect MidoNet to a hardware VTEP. This step is required before any Neutron networks can be bound to port-VLAN pairs on that VTEP.

  1. Refer to the documentation of your switch to enable VXLAN on it, then configure it as a VTEP with all the required parameters.

    MidoNet will expect that the Physical_Switch table on the VTEP contains a record with the management IP, management port and tunnel IP of this VTEP. Keep these details at hand as they will be needed to configure the VTEP and any bindings to Neutron networks. Use the following command to dump the contents of this table:

    vtep-ctl list Physical_switch

    Make sure that your VTEP also registers all the physical ports. You can verify this by examining the Physical_Ports table in the VTEP. Only ports present in this table will be available for binding to a Neutron network, Use the following command would display all physical ports, replacing <vtep-name> with the name assigned to the Physical_Switch (you can check this using the previous vtep-ctl list Physical_Switch command).

    vtep-ctl list-ports <vtep-name>
  2. After setting up the VTEP you might need to test connectivity to both the tunnel and management interfaces. Both should be up.

    To test the connection to the management database, you can run:

    $ telnet <management-ip> <management-port>
    Trying <management-ip>...
    Connected to <management-ip>
    Escape character is '^]'.

    At this point, paste this on the console:

    {"method":"list_dbs","id":"list_dbs","params":[]}

    And you should see this reply:

    {"id":"list_dbs","error":null,"result":["hardware_vtep"]}

    This just verified that the OVSDB server that holds the configuration of this VTEP is active and handling connections. If you did not get a similar reply, please review the configuration of the VTEP.

  3. The VXLAN service in Midonet is enabled by default. However, if the service has been previously disabled, you can enable it by typing the following command and restarting at least one cluster instance in order to become the VXLAN coordinator:

    $ echo "cluster.vxgw.enabled=true" | mn-conf set -t default
  4. Having ensured that the VTEP has been properly configured, now you’re ready to add the VTEP to the MidoNet configuration.

    For information, see the section called “Adding a VTEP”.

    [Important]Important

    Apart from the information on the VLAN-port assignment, and VTEP management interface IP and port, you will also need the identifier of a TunnelZone of type vtep. All the hosts running MidoNet Agent daemons that you want to create VXLAN tunnels with the VTEP should be members of this tunnel zone, using the local IP that each host uses as a VXLAN tunnel endpoint.

After you successfully add a VTEP to the MidoNet configuration, the API Server connects to its (VTEP’s) management interface and collects all the required information for creating a Logical Bridge. For more information, see the "Logical Bridge" section.

Questions? Discuss on Mailing Lists or Chat.
Found an error? Report a bug.


loading table of contents...